(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
(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
RFI_WaysideWorkPlanningSystem_FINAL.docx