Enterprise Asset Management System

The Vendor is required to provide enterprise asset management (EAM) systems capable of supporting a modern, data-driven, and integrated approach to transportation asset management.
- The desired EAM system should provide the following core services:
•    Centralized asset inventory: a system of record for all asset types (roads, bridges, signs, culverts, lighting, fleet, facilities, etc.), including location, condition, and historical data. Ability to customize individual record fields related to assets.
•    Lifecycle management: tools to plan, track, and optimize asset performance from acquisition through maintenance to retirement.
•    Maintenance management: scheduling and tracking of preventive, corrective, and emergency maintenance with support for work orders, labor, materials, and cost capture.
•    Inspection & condition assessment: management of inspection workflows, condition scoring, and automated triggers for maintenance actions.
•    Performance tracking: monitoring of service levels and state of good repair (SOGR) metrics in alignment with federal and state reporting requirements.
•    Capital planning & budgeting: support for investment prioritization, scenario modeling, and long-term financial planning.
•    Risk-based decision-making: assessment of asset risk and criticality to inform funding and operational priorities.
•    Geospatial integration: full integration with GIS for spatial analysis, asset visualization, and field support.
•    Mobile access: real-time, field-ready tools for inspections, data updates, and work order management.
•    Interoperability: seamless integration with financial, operational, and project management systems.
•    Reporting & analytics: configurable dashboards and reports for internal stakeholders and regulatory compliance.
•    Payroll: integration capability to interface with payroll systems, enabling automated transfer of labor hours from work orders into employee timesheets.
•    Multi-organization/multi-site capability: for example, different orgs/sites can share the same vendor records, while keeping their work-order and inventory records separate.
•    Configurable user interface (UI): the ability to adjust the layout, fields, and options visible to different users. Describe the tools available that do not require development resources.
- Hosting Environment
•    Identify the hosting provider (e.g., AWS, Azure, and Google Cloud) and hosting model (public, private, or hybrid cloud).
•    Describe the system architecture, availability, data redundancy, and failover capabilities.
•    Confirm compliance with relevant security certifications (e.g., FedRAMP, SOC 2 Type II, CJIS, HIPAA, etc.). 
- End User Hardware Requirements
•    List the minimum and recommended specifications for user devices (e.g., CPU, RAM, browser versions).
•    Specify supported operating systems and internet browsers for desktop and laptop access.
•    Identify compatible mobile devices and platforms (iOS, Android) for field access.
•    Indicate any specialized equipment required for full functionality (e.g., rugged tablets, GPS,
•    barcode/RFID readers), if applicable.
- Connectivity Requirements
•    Provide minimum and recommended internet bandwidth specifications for typical users.
•    Describe the system’s performance under low-bandwidth or offline conditions.
•    Explain offline functionality and data synchronization capabilities for mobile users.
- Mobile Access
•    Confirm availability of mobile apps or responsive web interfaces.
•    Describe available mobile features (e.g., inspections, work orders, asset updates).
•    Indicate whether mobile tools support offline use and automatic data syncing.

- Contract Period/Term: 1 year
- Questions/Inquires Deadline: December 12, 2025