Attachment 1 - CMMS Solution Key Functional Requirements-FINAL_202610.xlsx
XLSX spreadsheet 40 KB Posted
- Solicitation number
- BPM059766
- Issued by
- Montgomery County, Maryland
About this file
This document is a Computerized Maintenance Management System (CMMS) functional requirements specification for Montgomery County Public Schools (MCPS), referenced as RFP 7923.2. The specification outlines mandatory, should-have, and nice-to-have requirements across fourteen functional categories that vendors must address in their proposals. The system must support comprehensive asset management with QR code tracking and migration of existing MCPS codes, work order management with parent-child relationships and complete audit histories, fixed asset cost allocation, inventory management with forecasting capabilities, and a contractor portal with role-based access controls. Additional requirements include property management with storage of floor plans, CAD drawings, and O&M manuals; preventive and corrective maintenance scheduling; materials tracking including hazardous materials compliance; extensive reporting and business intelligence capabilities with configurable dashboards; integrations with financial systems; independent project management tracking; requester self-service portals accessible via web and mobile devices; configurable workflows with SLA tracking; and asset lifecycle management with condition assessments and replacement forecasting. The document does not specify response dates, due dates, award dates, contract terms, renewal options, site visits, or bidders' meetings.
The functional requirements specification does not include pricing terms, set-asides, incumbent information, funding amounts or sources, or other financial details. The document focuses exclusively on defining the technical and operational capabilities required for the CMMS solution, with vendor responses categorized as compliant out-of-box, compliant with third-party solutions, compliant with customization, compliant in future releases, or non-compliant, with space for detailed vendor explanations and technical specifications for each requirement.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Funtional Requirements_20261013 Attachment 1 - CMMS Solution Key Functional Requirements - RFP 7923.2
| Req ID | Requirement Statement | Priority (Must/Should/Nice to Have) | Vendor Response: Compliant Out-of-Box | Vendor Response: Compliant w/ Third Party (Explanation Required) | Vendor Response: Compliant w/ Customization (Explanation Required) | Vendor Response: Compliant in Furture Release (Explanation Required) | Vendor Response: Non-Compliant | Vendor Explanation/ Technical Details |
| 1. Asset Management | ||||||||
| AM-1 | The system shall support asset tracking and management throughout the complete asset lifecycle. | M | ||||||
| AM-2 | The system shall allow sub-assets to be associated with parent assets for reporting and management purposes. | M | ||||||
| AM-3 | The system shall support QR code scanning for asset identification and tracking. | M | ||||||
| AM-4 | The system shall allow migration and continued use of existing MCPS QR codes. | M | ||||||
| AM-5 | The system should track asset warranties and provide automated notifications prior to warranty expiration. | S | ||||||
| AM-6 | The system shall detect duplicate QR codes. | M | ||||||
| 2. Work Order Management | ||||||||
| WO-1 | The system shall provide comprehensive work order management capabilities. | M | ||||||
| WO-2 | The system shall support parent-child work order relationships. | M | ||||||
| WO-3 | The system shall maintain a complete audit history of work order activities, updates, and actions taken. | M | ||||||
| WO-4 | The system shall support labor resource allocation, scheduling, and tracking. | M | ||||||
| WO-5 | The system shall provide scheduling capabilities for work orders, personnel, and maintenance activities. | M | ||||||
| WO-6 | The system shall provide mobile access for all users. | M | ||||||
| WO-7 | The system should identify duplicate work orders. | S | ||||||
| 3. Fixed Asset Management | ||||||||
| FA-1 | The system shall allocate and track costs by asset, facility, project, department, and other configurable categories. | M | ||||||
| FA-2 | The system should support multiple asset depreciation methodologies. | S | ||||||
| 4. Inventory Management | ||||||||
| IM-1 | The system should provide inventory item inquiry capabilities, including the ability to search, view, filter, and retrieve inventory item information in real time. | S | ||||||
| IM-2 | The system should manage spare parts inventory and availability, including tracking stock levels, locations, quantities on hand, usage history, and reorder status | S | ||||||
| IM-3 | The system should provide inventory forecasting and replenishment planning capabilities to support demand forecasting, inventory optimization, and automated or user-defined replenishment recommendations | S | ||||||
| IM-4 | The system should generate stock-out, inventory shortage, and backorder reports, including alerts and analytics to support proactive inventory management and operational decision-making. | S | ||||||
| 5. Contractor Work Order System Portal | ||||||||
| CP-1 | The system should provide a contractor portal that is separate from and securely segregated from MCPS staff access, with role-based permissions and controls to prevent unauthorized access to data and system functions | S | ||||||
| CP-2 | The system should enable contractors to receive, review, update, and complete assigned work orders through the contractor portal, including the ability to record status updates, labor hours, materials used, and completion details | S | ||||||
| CP-3 | The system should track and report labor and material costs associated with contractor-performed work, including actual, estimated, and billed costs | S | ||||||
| CP-4 | The system should measure, monitor, and report contractor performance metrics, including key performance indicators (KPIs) such as response times, completion times, work quality, and contract compliance | S | ||||||
| CP-5 | The system should provide contractor-specific dashboards and reporting views that present relevant work order, cost, performance, and operational data based on the user's assigned role and permissions. | S | ||||||
| 6. Property Management | ||||||||
| PM-1 | The system should store and manage facility floor plans, including version control, document indexing, and secure access based on user roles and permissions | S | ||||||
| PM-2 | The system should store and manage CAD drawings and associated files, including support for version tracking, retrieval, and linkage to related facilities, assets, and work orders | S | ||||||
| PM-3 | The system should store and manage Operations and Maintenance (O&M) manuals and enable users to access documentation directly from associated asset and facility records. | S | ||||||
| PM-4 | The system should store and manage equipment specifications and technical documentation and associate such information with corresponding asset records. | S | ||||||
| PM-5 | The system shall store and manage asset and facility photographs and enable users to attach, view, and retrieve images from related asset, facility, and work order records. | M | ||||||
| PM-6 | The system should store and manage warranty documentation, including warranty periods, coverage details, expiration dates, and associated asset records. | S | ||||||
| PM-7 | The system should store and manage inspection reports and related documentation, including historical records, findings, corrective actions, and supporting attachments. | S | ||||||
| PM-8 | The system should maintain a directory of labor resources and staff qualifications, including certifications, licenses, training records, skill sets, and assignment availability. | S | ||||||
| 7. Maintenance Management | ||||||||
| MM-1 | The system shall support preventive maintenance programs, including automated work order generation, compliance reporting, and completion tracking. | M | ||||||
| MM-2 | The system shall support corrective maintenance activities. | M | ||||||
| MM-3 | The system should provide configurable maintenance task templates. | S | ||||||
| MM-4 | The system shall schedule preventive, predictive, and corrective maintenance activities. | M | ||||||
| MM-5 | The system should support predictive maintenance programs and monitoring. | S | ||||||
| 8. Materials Management | ||||||||
| MM-1 | The system should track material usage and consumption, including quantities issued, quantities consumed, inventory adjustments, associated costs, and linkage to work orders, assets, and facilities. | S | ||||||
| MM-2 | The system shall maintain a complete audit trail of transactions and system activities, including the creation, modification, deletion, approval, and status changes of records, along with user identification and date/time stamps. | M | ||||||
| MM-3 | The system should track hazardous materials and associated compliance requirements, including material inventories, storage locations, Safety Data Sheets (SDS), inspection records, regulatory reporting, and applicable environmental, health, and safety compliance documentation. | S | ||||||
| 9. Reporting and BI | ||||||||
| RBI-1 | The system shall provide work order summary reports. | M | ||||||
| RBI-2 | The system shall track and report labor hours and associated costs. | M | ||||||
| RBI-3 | The system shall track and report material costs. | M | ||||||
| RBI-4 | The system shall provide operational and performance reporting capabilities. | M | ||||||
| RBI-5 | The system should provide asset failure analysis and reporting. | S | ||||||
| RBI-6 | The system should report asset costs, utilization, and lifecycle expenditures. | S | ||||||
| RBI-7 | The system shall provide configurable automated dashboards. | M | ||||||
| RBI-8 | The system shall provide executive dashboards displaying key performance indicators (KPIs), backlogs, and operational metrics. | M | ||||||
| RBI-9 | The system shall provide a public-facing dashboard displaying school-level work order information. | M | ||||||
| RBI-10 | The system shall provide school-specific performance metrics and analytics. | M | ||||||
| RBI-11 | The system shall generate performance reports. | M | ||||||
| RBI-12 | The system should support classification and categorization of inventory items. | S | ||||||
| 10. Intergrations | ||||||||
| INT-1 | The system should provide financial reporting capabilities, including standard and ad hoc reports, dashboards, and analytics for budgeting, expenditures, labor costs, material costs, asset lifecycle costs, and overall maintenance performance. | S | ||||||
| 11. Project Management | ||||||||
| PM-1 | The system shall track capital and maintenance projects independently from standard work orders. | M | ||||||
| PM-2 | The system should track warranties associated with newly installed systems and equipment. | S | ||||||
| 12. Requester Self-Service Portal | ||||||||
| SP-1 | The system shall support a hierarchical structure including district, region, building, floor, room, and asset levels. | M | ||||||
| SP-2 | The system shall allow users to submit service requests through a web-based portal. | M | ||||||
| SP-3 | The system shall allow users to submit service requests via mobile devices. | M | ||||||
| SP-4 | The system shall allow photo attachments to requests and work orders. | M | ||||||
| SP-5 | The system shall provide request and work order status tracking. | M | ||||||
| 13. Workflow and SLA | ||||||||
| WS-1 | The system shall allow all approved system users to submit service requests. | M | ||||||
| WS-2 | The system shall route requests and work orders based on school, location, trade, priority, or other configurable criteria. | M | ||||||
| WS-3 | The system shall support configurable approval workflows. | M | ||||||
| WS-4 | The system shall support configurable escalation rules and notifications. | M | ||||||
| WS-5 | The system shall support emergency, urgent, routine, and planned maintenance priority categories. | M | ||||||
| WS-6 | The system shall generate user notifications and alerts. | M | ||||||
| WS-7 | The system should track Service Level Agreement (SLA) compliance metrics. | S | ||||||
| WS-8 | The system shall track work order response times. | M | ||||||
| 14. Asset Lifecycle / Capital Planning | ||||||||
| AL/CP-1 | The system should support regulatory compliance auditing and documentation, including the maintenance of audit records, compliance reporting, inspection documentation, corrective action tracking, and retention of records required to meet applicable federal, state, and local regulations. | S | ||||||
| AL/CP-2 | The system should perform and track asset condition assessments, including the ability to record condition ratings, inspection results, deficiencies, recommendations, and supporting documentation for assets and facilities. | S | ||||||
| AL/CP-3 | The system should calculate and report the estimated remaining useful life of assets based on configurable criteria, including asset age, condition, maintenance history, utilization, and replacement cost. | S | ||||||
| AL/CP-4 | The system should forecast asset replacement needs and timelines using asset condition data, lifecycle information, risk factors, maintenance history, and user-defined planning parameters. | S | ||||||
| AL/CP-5 | The system should track deferred maintenance requirements and associated costs, including the identification, prioritization, valuation, monitoring, and reporting of deferred maintenance activities across assets and facilities. | S |
File details come from the government source that posted it. Updated .