Rail Safety Cloud Incident Management System

The vendor is required to provide rail safety cloud incident management system (RS-CIMS) to modernize and streamline its safety and incident management processes.
- The desired application must be future-proof, scalable, and cost-efficient, enabling seamless adaptation to evolving rail safety requirements, emerging technologies, dynamic cloud environments, and government compliance mandates.
- The RS-CIMS is essential to enhance the rail safety department’s capabilities, including real-time incident reporting, advanced analytics, and improved situational awareness.
1. Fundamental technical
•    The system should provide a cloud-based solution for documenting and tracking reported hazards. b. the system should align with the requirements of federal transit administration (FTA) 49 cfr part 673.75 safety risk management. 
•    The system should establish a comprehensive internal employee reporting system. 
•    The system should provide a management utility for review of safety issues. 
•    The system should allow real time reporting and analysis. 
•    The system should contain safety risk assessment functionality. 
•    The system should contain safety communication functionality. 
•    The system should produce visual data charts. 
•    The system shall call out trends on visual data charts to assist safety analysis.
•    The system should establish a comprehensive safety identification system. 
•    The system should measure safety performance information through mts. 
•    The system should allow manual risk score calculations in accordance with risk scoring system detailed in ATT 3 - hazard management master, in the assessment tab. 
•    The system should inform employees of safety actions taken in response to submitted reports. 
•    The system should convey safety risk and hazard information to stakeholders. 
•    The system should provide QR codes, web form, webapp, mobile app, and other common quick access reporting utilities. 
•    The system should provide online data access and information entry capabilities to users. 
•    The system should provide the capability to upload, store and review photos, data, and various file types. 
•    The system should provide the capability to create, delete and modify safety workflows 
•    The system should provide detailed workflows and customizations to meet the requirements of various workflows as demonstrated in ATT 2 - hazard assessment form. 
•    The system should be account based for roles listed.
•    The system should be collaborative in nature. 
•    The system should use common technical file formats and data stores (including but not limited to pdf, email, word, excel, ppt, jpg, PNG, etc.). 
•    The system should allow easy data parsing by departments, responsible parties, hazards and other filters. 
•    The system should call out who is responsible for mitigating the hazards and the mitigation plans 
•    The system should integrate with mts technology including but not limited to microsoft 365, intranet, sap, GTFs, GPS, ArcGIS and Esri.
2. Basic setup
•    Setup should allow flexibility to create company specific named locations. 
•    Setup should facilitate creation of new users and assignment of roles. 
•    Setup should allow editing, deleting, and updating user information. 
•    System should also allow setting up basic user preferred configurations. 
•    Setup should allow management of administrative tasks. 
•    Setup should allow for user workspace or dashboard to be customizable and configurable on the fly. 
•    Setup should allow user workspace or dashboard to have various filter capabilities for easily parsing data. 
•    Setup should allow mts to configure business rules and workflows. 
•    Setup should allow mts to configure detailed reporting of safety status.
3. User management
•    System should allow the functionality to create, view, update and delete users.
•    System should allow assignment of different roles to the system users.
•    System employs user access control to prevent access to accounts
•    System should allow users to login to the system after required authentication.
•    System should be able to limit the user privileges based on the user role and assigned group in the application.
•    A logged in user should be able to see his personal data and assigned role.
4. GEO location
•    System should provide capability to understand geo tagging and file location data.
•    System should communicate where an image was captured, or the location data is pointing.
•    System should integrate with standard ArcGIS, Esri systems and GPS data.
•    System should offer store and forward technology for areas with limited reception.
•    System should provide the ability to enter intersections, grade crossings, mile markers, train numbers, vehicle numbers and types of various equipment.
5. Mobile and web app integration
•    Mobile and web application should require authentication from users defined before he can use the application.
•    Mobile and web application web application should not require users defined as “mts internal employees” in to login.
•    Mobile and web application should offer “mts internal employees” anonymous reporting capabilities.
•    Mobile and web application should offer “mts internal employees” follow up capabilities if the employee files a report with the employee’s email included. 
•    Mobile and web application should show data in accordance with the role of the logged in user.
•    Mobile and web application should have the capability to work in both online and offline modes, whereby online mode is defined as connectivity to the server is available for mobile app. 
•    On the other hand, offline mode is defined when server and internet connectivity is not available.
•    Mobile and web application should allow technical support user to add, update and delete server information data. 
•    Mobile and web application should support multilingual operation. 
•    It should allow the user to select one of the desired language options. 
•    Mobile and web application should also show assets in geographical map mode where markers or icons shall indicate asset locations on the map. 
•    Mobile application should be available to users through the google play or apple app store.
6. Cloud-native safety application
•    The system is deployed and managed using continuous integration and continuous delivery pipelines (CI/CD). 
•    Separate test, training and production cloud tenants and environments.
•    Self-service configuration management. 
•    Change and release management. 
•    Advanced release notice with release notes including new features and changes.
•    Product feature update and defect fix history. 
•    Gated feature and change deployments with traffic control. 
•    Cloud services will utilize a high availability service like azure. 
•    Offline capabilities, allowing the user to continue their work in a cached state that will automatically sync once they are back online. 
•    Offline capabilities, allowing users to use the application as intended without having access to network services.

- Contract Period/Term: 3 years
- Pre-Proposal Meeting and Site Visit Date: October 16, 2025
- Questions/Inquires Deadline: October 24, 2025