Asset Maintenance Project Software

The vendor is required to provide from qualified transit software technology firms to implement a maintenance and asset management software (AMPS).
- The ability to provide a comprehensive solution for the software, including configuration, implementation, training, support, and maintenance.
- Asset management
• AMPS shall support a central repository to maintain and track all assets and maintain consistent, reliable, and up-to-date data on asset status, location, and condition.
• AMPS shall support creation of every asset with only basic information and the flexibility to require additional fields.
• AMPS shall support defining unique asset attribute lists for each asset class and type, displayed according to the asset being examined; attributes may include technical specifications and capacities.
• AMPS shall support specifying certain asset attributes as required or optional, unique to each asset class and asset type, during asset record creation.
• AMPS shall support assigning assets to specific employees or work groups permanently or temporarily.
• AMPS shall support providing a complete inventory of all assets used during a maintenance activity
• AMPS users shall be able to add and access digital files associated to an asset including photographs, manufacturer information, warranty information, standard operating procedures, or other documents.
• An asset or group of assets shall be selected by searching multiple data fields simultaneously including user defined data fields.
• Assets including equipment must have unique ids preventing asset duplication
• Ability to review the repair and associated operating costs on equipment and components for any series of months, quarters, years, and life cycle.
- Warranty tracking
• AMPS shall support tracking manufacturer's warranties by user‐defined criteria and links to warranty contracts and warranty claims for assets, major components, and parts.
• AMPS shall support generating a list of assets with warranty end dates approaching based on a user‐defined timeframe.
- Inventory management
• AMPS shall support a central repository to maintain and track all parts.
• AMPS shall support creation of every part with only basic information and the flexibility to add additional fields.
• AMPS shall support defining unique part attribute lists for each part class and type
• AMPS shall support specifying certain part attributes as required or optional, unique to each asset class and asset type, during part record creation.
• AMPS shall support providing a complete inventory of all parts.
• AMPS shall support recording and maintain part acquisition data including purchase date and cost. cost should be represented by the last purchase made for the particular part.
- Patches
• All software patches to applications and the operating system shall be applied concurrently with gtrans scheduled patches.
- Expandability
• All software shall be easily expandable to accommodate the anticipated growth of amps in terms of users and assets as defined in this specification.
• Reinstallation, recompilation, or replacement of the software shall not be necessary to accommodate the specified growth.
• The size and configuration of the system shall be expanded by easily modified parameters contained in centralized system parameter files.
- Modularity
• All software shall be designed with sufficient modularity to minimize the time and complexity involved in making a change to any program.
• The modularity shall include the separation of hardware interface modules from other software modules.
- Cloud solution
• A commercial off-the-shelf (COTS) high availability (HA) cloud solution using microsoft azure or amazon web services (AWS) shall be used to host amps.
• All cloud services shall be providing to meet the specification requirements including, but not limited to compute, storage, databases, analytics, networking, mobile, developer tools, management tools, IoT, security, and enterprise applications.
• AMPS shall provide a sandbox or testing environment so that changes can be tested before applying them to the production environment.
• Security controls for cloud services shall be organization and international electrotechnical commission 27001 certified, information security management system (ISMS) certified or similar.
• The cloud hosted solution shall be supported by resilient data backup and recovery processes including a secondary datacenter so that service disruptions are minimal.
- Database software
• All supplied database management system software shall not be modified or patched by the contractor in any manner that is not approved by the software’s vendor.
• The supplied database management system software shall support all functional, performance, and response requirements of amps at the ultimate requirements
- Online database
• AMPS shall include an online (i.e., continually updated and accessible) database that maintains comprehensive current and historical information on amps operating state, including, but not limited to, system status, data required for displays and reports, data entered by amps users, and data retrieved from other computer systems.
- Display generation/editing software
• The contractor shall provide means for generating new displays and editing existing displays.
the contractor's documentation shall describe the procedures required to build and integrate new displays and to modify existing displays.
• The contractor shall use this same display generation software to construct all contractor-provided displays.
- Virtual Pre-Proposal Meeting (Optional) Date: April 10, 2025
- Questions/Inquires Deadline: April 14, 2025