• Introduction
• Functionality
• Vendor Summaries
• Compare Products
• Software Aspects
• General CMMS Vendor/Package Information
• Implementation
• Integration
• Multi-site Support
• Global Attributes
• Security and Data Integrity
• User Interface
• Look-ups and Searches
• Data Entry
• Help Features
• Workflow and Business Logic
• Analysis and Reporting
• Work Order Control
• Preventive and Condition-Based Maintenance
• Safety
• Priorities
• Planning and Scheduling
• Inventory Control and Purchasing
• Budgeting and Cost Reporting
• Equipment History
• Mobile Technology
• HR Management
• Fleet Maintenance
• Infrastructure Maintenance
• Service and Technology Asset Management
• Calibration
• Engineering Design to Maintenance
• Sustainability
• Other Specialized Modules

Equipment History

206. Is production downtime distinguished from equipment breakdown, and are both tracked? Yes Yes, with configuration Yes, with 3rd party integration No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

207. Are problem, cause and action codes grouped, nested and hierarchical? Yes, as above but also relevant action codes are shown pertaining to the selected cause code, i.e., fully nested and hierarchical Yes, as above but also relevant cause codes are displayed for the selected problem code Yes, some nesting/hierarchy, but only certain problem codes are shown for a given component/equipment Some grouping, i.e., relevant problem, cause & action codes are displayed for a given asset class No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

208. Is there a troubleshooting database (i.e., based on analysis of problem, cause and action codes) to assist in diagnosing equipment repair problems? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

209. Can a user create, analyze and track failure records? Comprehensive (ie can create a failure record and link to work order, incident or condition indicator; can track potential, partial or full failure; CMMS will track “failure avoidance savings”; links to suggested action) Some advanced failure analysis features Configurable 3rd party No (ie, failure recorded on each work order) Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

210. Does the CMMS track service life percentage? Comprehensive (ie for a given moment in the life of an asset, based on expected life of asset, date commissioned, number of failures to date, average failures per year, when failures occurred, failure frequency as life decreases) Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

211. Does the CMMS support Root Cause Failure Analysis (RCFA or RCA)? Comprehensive (ie can record a cause record and link to failures, work orders, incidents, or condition indicators; SWOT analysis; Fishbone diagram; link to FMEA and RCM) Some Configurable 3rd party No (ie, only simple Pareto analysis of cause codes or use of descriptive fields) Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

212. Does the CMMS support Failure Modes and Effects Analysis (FMEA)? Comprehensive (ie can define failure modes for each asset or component and link to condition indicators, triggers, job plans, and notifications) Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

213. Does the CMMS support Reliability-Centred Maintenance (RCM)? Comprehensive (ie can define all the asset functions, operating context for the asset such as ambient or coolant temperature range, functional failures, and failure modes or root cause for any asset or component; can define probable failure effects or impacts for each failure mode, can define the appropriate maintenance policy such as condition-based maintenance, use-based maintenance or fail-based maintenance; can define maintenance tasks for each failure mode based on failure history, probability, and costs to compare financial and technical feasibility of maintenance policy actions (eg, monitor asset performance and reliability to determine most appropriate actions/tasks) Most Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

214. Does the CMMS support Weibull, Monte Carlo Simulation, Laplace, and Crow/AMSAA analysis for reliability programs? Comprehensive (ie full analysis built into CMMS) Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

215. Does the CMMS support determining the optimal maintenance policy (ie, fail-based, use-based or condition-based maintenance)? Comprehensive (ie compare cost of failure with cost of prevention using historical data or by entering data manually for a user defined period; simulation mode; considers labour, material, contract costs) Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

216. Can you create an operators log book for a given asset, separate from work orders, to determine things like failure info, downtime info, conditions, applicable, work order references, and line stops (ie, when equipment stops for a few minutes and operator makes a minor fix, can actually record what happened electronically)? Yes, all of the above Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

217. Will the system track the full impact of each incident or work order (other than maintenance costs such as labor, materials, contractors, etc) including a. Cost of operational downtime Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important b. Environmental impact code (e.g., severity or type code) Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important c. Cost of environmental impact Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important d. Quality impact code (e.g., severity or type such as scrap or returns) Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important e. Cost of quality impact Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important f. Safety impact code (e.g., lost time) Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important g. Cost of safety impact Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important h. Other (user-definable) impact code Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important i. Cost of other impact Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important j. Total impact cost Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

218. Does the CMMS report on: a. Mean-time-between-failures? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important b. Mean-time-between-failures for a specific root cause? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important c. Mean-time-between-failure for a given failure mode (eg, valve leak)? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important d. Mean-time-to-repair (MTTR)? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important e. Mean-wait-time (MWT) or response time? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important f. 'Time since last failure' trend for any problem code? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important g. 'Time since last failure' trend for any cause code? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important h. 'Time since last failure' trend for any action code? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important i. 'Time since last failure' trend from the last checkpoint? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important j. Lifecycle cost for a given asset or group of assets? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

219. Does the CMMS analyze, not just report on, relative frequencies and probabilities of the following (i.e., using Pareto analysis, predictive trending, root cause analysis, correlation, forecasting, etc.): a. Complaints? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important b. Root causes? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important c. Actions taken? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important d. Idle or delay time? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important e. Work order status history? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important f. Asset availability? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important g. Asset utilization (i.e., available and used)? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important h. Asset performance (e.g. speed)? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important i. Product quality impact (e.g., asset causing rework, etc.)? Yes Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

220. Does the CMMS provide archiving capability (ie, ability to view archived data from within the CMMS, automatic storage based on conditions other than time like asset status, easy and fast restoration)? Yes, comprehensive Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

221. Does the CMMS support a PAS 55 framework (ie, future ISO 55001)? Comprehensive (ie, can record strategies, objectives, missions, etc. as per PAS55 framework; can collect and monitor data against this framework; can analyze data against the framework and make adjustment to maintenance program and/or PAS 55 strategies, objectives, missions, etc.) Some Configurable 3rd party No Rank the importance of this attribute: Very Important Important Somewhat Important Slightly Important Not Important

You have allocated a total of 0% of your total scoring allowance. Input the percentage you wish to weight this section for your final product comparison. A weight of 0% will indicate that this section is not to be scored. Scoring weight: % (Minimum 0%, maximum 100%)

Copyright © 2004 - 2023 Plant Services All rights reserved.
P: 630-467-1300 | 1501 E. Woodfield Rd. Suite 400N Schaumburg, IL. 60173 webmaster@putman.net