their track rights. ROCC staff use GOTRS milestones as a guide for completing the common stages of work—but ROCC personnel manage many tasks outside of the GOTRS system, such as plans for crew lineup, work site sequencing, and movement patterns. GOTRS is a custom-code enterprise application. Originally built on Microsoft Silverlight, WMATA is currently re-writing GOTRS in AngularJS, with a delivery date of mid-2019. GOTRS processes approximately 24,000 ROW requests per year by more than 300 users across several WMATA departments and offices. GOTRS does not directly interface with other WMATA software systems, such as WMATA’s enterprise asset management software, Maximo, nor WMATA’s enterprise human resource management software, PeopleSoft. Although GOTRS does not directly interface with the Rockwell Collins developed ARINC Advanced Information Management (AIM®) platform for rail operations, the GOTRS process aligns and coordinates with existing AIM capabilities. 2.5.5 United Technologies’s developed Advanced Information Management (AIM®) The ROCC uses AIM to monitor and manage the rail system, including managing wayside work during the execution phase. AIM displays rail system information to an ROCC controller in real-time, allowing the controller to regulate traffic flow, control movement, and govern communications. The ROCC can implement control strategies by pre-programming strategies that AIM will implement automatically in concert with the central control mainframe, or the ROCC can manually select and implement strategies. To implement manual control strategies, controllers can issue train to wayside communication commands, modify wayside signals and/or switches, or direct voice communication (radio calls) with train operators. Three AIM consoles, subdivided into geographical areas by Metro-line color, are designated in the ROCC to monitor and control of train movements. Additional consoles allow ROCC personnel to manage other functional areas, including Maintenance Operation Control and Customer Operations. 2.5.6 Supporting Technologies and Information WMATA’s IT infrastructure is based on the following technologies and assumptions. Modifying this suite may increase costs or operating risk. Virtualized server technologies VMS; Enterprise operating systems are Oracle Linux (First preference) and Microsoft Windows; Exadata appliances are available for large scale databases; Preferred database platforms are Oracle or MS SQL; The Rail Control System (currently AIM), Maintenance and Materials Management System (currently Maximo), and schedule control system
(currently must be in a high availability architecture with recovery times not to exceed four minutes. The scheduling and analysis systems (e.g., Optram) must be in a disaster recovery architecture that allows for recovery in not more than hours. WMATA uses IBM Jazz and the Atlassian suite (JIRA, Confluence, Bamboo, SVN, FishEye, Crucible, and Test Rail) for requirements and testing management, and as code vault and code promotion tool. The solution must permit continued use of these tools. Tool selection will be the decision of WMATA, but vendors may present reasoning for using one or the other of these tool sets. 2.6 Existing Norms for ROW and Facilities Work The following norms provide detail on how the new planning and scheduling system can best fit within WMATA’s working environment and improve our current processes. 2.6.1 Safety Safety is WMATA’s top priority. All work conducted on the ROW must comply with the Metrorail Safety Rules and Procedures Handbook and the Railroad Worker Protection guidelines. 2.6.2 Timing The overwhelming majority of work on the ROW and at WMATA facilities is conducted overnight, during Metrorail’s non-revenue service hours. However, large-scale projects may include RSAs, in which WMATA ends revenue service early or begins revenue service late to provide more work time, or single-tracking/shutdown events, in which WMATA closes one or both tracks in an area to provide extended work periods. Additionally, WMATA conducts some minor work and emergency-related work during revenue service. The current revenue-service hours are as follows: Monday-Thursday 5:00am – 11:30pm Friday 5:00am – 1:00am Saturday 7:00am – 1:00am Sunday 8:00am – 11:00pm seeks to reduce the number of required RSAs and shutdowns. Although this may not be possible for the foreseeable future, due to the large amount of capital work on the horizon, a stronger planning and scheduling process can also help capture as much useful work time as possible during non-revenue hours. 2.6.3 Maturity of the Planning Environment WMATA’s current planning environment favors flexibility over standardization. It allows individual offices to use their own methods to plan, schedule, finalize, and execute work