Guidance on Successful Computer Maintenance Management System (CMMS) Selection and Practices (2015) / Chapter Skim
Currently Skimming:
Pages 39-50
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 39... ...
Chapter 5: Selection and Implementation of an Airport CMMS This chapter describes a process for selecting and implementing a CMMS at an airport. Since the CMMS impacts multiple departments or business units of the airport, this process should involve stakeholders across the entire airport and the CMMS should provide support for functions across all business units.
|
From page 40... ...
The first step in the selection process is to research available software in the market. CMMS software is widely available, so the larger issue will not be to find a software, but to narrow down candidate CMMS software based on the prioritized list of airport requirements.
|
From page 41... ...
the required functions. The airport can rate each software option based on how well it meets the functional requirements, and tally the results for a comparative score.
|
From page 42... ...
The Implementation Process At this stage, the airport will need a plan for a implementing the selected CMMS software. This section discusses how to plan that implementation process.
|
From page 43... ...
o Original project/asset costs o Features o Location o Maintenance history o Inspections o Preventive maintenance • Who are the decision makers for the assets? Identification of an executive sponsor, a project champion, a project manager, and support personnel will facilitate capture of data about the assets.
|
From page 44... ...
Asset Data Types After determining the assets that the airport wants to manage, and locating any other data sources, additional data on the assets will need to be collected and be captured in the data dictionary or data catalog. An example of the asset data that might be collected, is shown in Table 5-2.
|
From page 45... ...
The number of data attributes that an airport wants to store and maintain for assets depends on the needs of the airport. More data can help in making appropriate business decisions about life cycles of assets; unless the data is maintained it will not be useful.
|
From page 46... ...
• Who will be involved in the conversion • What the conversion strategy will include (e.g., timing of the conversion) • The effects of the conversion on the existing system (e.g., will there be a need for a system outage on the legacy system during the conversion process?
|
From page 47... ...
upgrades are released by the CMMS vendor. A CMMS that is a good fit for the airport will not require customization.
|
From page 48... ...
Integrations Integrations are not likely to be in the first phase of the airport's CMMS implementation. Integrations are likely to be in later phases, as the CMMS matures, and as users understand its features and capabilities and how they can be used to better manage assets and work at the airport.
|
From page 49... ...
associated to the work order. The mobile device should receive all information needed so that a return to the maintenance shop is not required.
|
From page 50... ...
The airport will need to dedicate resources to the ongoing maintenance and operation of the CMMS. The level of resources needed will depend on how the CMMS is implemented, whether it is a hosted solution or whether it is deployed and managed internally.
|
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.