Skip to main content

Currently Skimming:


Pages 27-38

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 27...
... Chapter 4: An Approach to Evaluating CMMS Software This section introduces a suggested evaluation approach to choosing a CMMS. This approach does not begin with looking at the software packages available on the market, but starts with identifying the requirements for a CMMS.
From page 28...
... • A pavement inventory with dimensions, locations, and maintenance history of the airport's paved surfaces. • An inspection schedule with detailed annual assessments and monthly drive-by observations.
From page 29...
... Figure 4-1 Step 1 – Determining and Prioritizing Assets Step Two. Decide How To Manage the Selected Assets in the CMMS After identifying the asset categories in Step One, now in Step Two an airport should identify how the airport wants to use the CMMS to manage the assets.
From page 30...
... • Reliability and cost history (Track outages and costs by work order; by machine; by department) • Resource scheduling • Reporting, with rollups by system and/or by facility • Mobile applications For example, if an airport decides to manage passenger-loading bridges with its CMMS, it should then determine which of the functions in the list are required to manage the passenger-loading bridges at the airport.
From page 31...
... inventory into the system. Integration with a purchasing system can trigger generation of a purchase request when spare parts inventory reaches a minimum level, based on the requirement requisition of a part on a work order.
From page 32...
... identified in the original procurement to preclude difficulties with a chosen CMMS in the later phase. It is important to list integrations as future enhancements in the original procurement documents for that reason.
From page 33...
... Figure 4-2 Analyze Existing Workflows Each of the identified workflows should be analyzed for potential for automation in a CMMS. Some workflow automations that might benefit the airport include: • FAR Part 139 inspections, reporting and record-keeping • NOTAM and field condition reporting • Internal and external safety reporting procedures • Requisitions based on inventory levels • Scheduling preventive maintenance • Sign replacement procedures (see Figure 4-3 below for an example)
From page 34...
... There is no question that automating workflow in a CMMS can bring efficiencies and benefits to any airport. There is really no question of whether to automate in a CMMS.
From page 35...
... Two of the case study reports presented in Appendix B have a similar process for Part 139 discrepancy reporting. Each airport has implemented the automation in the way that is most useful to them.
From page 36...
... The examples are given to help the airport understand the options available for automation. Although automation of workflow will be accomplished in implementation and configuration of the CMMS, during this evaluation process the airport will decide the requirements for the CMMS.
From page 37...
... A detailed checklist, providing individual features and functionalities for each of the items in the list above is provided in Appendix D The checklist should be used by the airport not only to define its requirements but also be utilized in the development of an RFP or specifications document for the development of a CMMS.
From page 38...
... Evaluation Tool Overview The CMMS Evaluation Tool ("Tool") provides a step-by-step guide through the selection process, including selection of modules and/or features of CMMS for implementation using prioritization and budget.

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.