The vendor required to provide computerized maintenance management software (CMMS) application that can effectively address its current and future needs for all-inclusive asset maintenance management including, but not limited to asset management, data management and accuracy, audit trails, record keeping and preventive maintenance, data within the laws of the guidance.
- Disparate systems and integration points, including:
• provide a cloud-based software as a service (SaaS) product that aligns with the county’s operating model and that satisfies the requirements conveyed.
• Provide complete implementation and testing of the proposed solution.
• Complete implementation and testing shall involve configuring the system to meet the specific needs of the county, with a focus on use of best practice processes up to and following go live.
• The successful offeror shall work closely with the county's staff throughout the phased implementation stages to ensure a smooth transition and full adoption by the end users.
• Provide ongoing technical support.
• After the system is live, the successful offeror shall provide ongoing technical support, system maintenance and software upgrades. the success solution shall possess a robust support model capable of delivering timely and effective assistance to the county as required. the solution service level agreement and fee structure for these services must be provided with the proposal.
• Adopt as many out-of-the-box processes as possible, fully leveraging the system’s built-in capabilities.
• Provide expertise and guidance to assist the county with the redesign of business processes, leveraging industry’s best practice.
• Integrate with existing systems and allow for easy migration of data between systems.
• Support the organization through the deployment of functionality now and in the future as needs and requirements evolve.
• Deliver a robust reporting functionality that is flexible, intuitive, and configurable.
- Back-end functional support
• usability: ability to deliver consistent user-experience with an easy to use and intuitive graphic user interface that enables the user to quickly navigate the CMMS.
• The ability to integrate into all modern-day Os systems to support ease of access.
• Mobility: provide mobile architecture and reference model to support application mobility for utilities end users.
• Reporting and data analytics (data and data access): the CMMS must provide a suite of solutions that allows end users to access the data including, but not limited to, reporting, analytics tools, dashboards, and data extraction tools.
• The future, utilities intend to establish a data lake and is interested in learning about the data integration capabilities that would allow the export of CMMS data into the lake.
• Workflow management: capability to generate, assign, and track individual work items for staff processing and route work items to the required staff processors and approvers, ensuring all procedures and quality checks are performed.
• They are verifiable through audit logs.
• Integrations: the CMMS should provide robust and modern integration technologies that allow seamless integration with other modern systems.
• This integration should be done in real-time and should include data validation rules to improve the reliability of the data transferred between systems.
- Integration requirements
1. GIS:
• the solution shall tightly integrate with the county’s GIS (Esri utility network data model) so that data managed in the GIS is available to users in the CMMS and mobile application and so that CMMS information (e.g., service requests, work orders, etc.) for horizontal assets can be identified and viewed spatially.
2. ERP:
• The solution must include an API capable of integrating with commonly used enterprise resource planning (ERP) systems.
• The integration will be established as part of the future ERP implementation, but CMMS proposals must include access to an API that will support the eventual integration with the selected ERP.
• The CMMS integration architecture, supported API standards (e.g., rest, soap), and its flexibility to interface with a range of commonly used ERP systems.
• Offerors should expect to work closely with the county to define integration requirements between the eventual ERP and the CMMS to support all purchasing and warehousing functions.
- Contract Period/Term: 5 years
- Questions/Inquires Deadline: December 22, 2025
