• Abstract and Figures
• Public Full-text

Denver Regional Transportation District Commuter Rail Network Request For Amendment (RFA) to PTC Implementation Plan (PTCIP) Revision 1.3 – January 21, 2016 Submitted in fulfillment of 49 CFR Part 236, Subpart I, 236.1021 (d) RTD PTCIP – RFA Revision History Version Date By Summary 1.3 January 21, 2016 Xorail Original Revision 1.3 1 RTD PTCIP – RFA Table of Contents 1. INTRODUCTION ........................................................................................................................ 3 1.1 Overview and Purpose ................................................................................................................... 3 1.2 Scope ................................................................................................................................................ 3 2. PROPOSED PTC IP MODIFICATIONS (§ 236.1021 (D) (2)) ................................................... 4 3. REASONS FOR THE PROPOSED IP MODIFICATIONS (§ 236.1021 (D) (3)) ....................... 7 4. CHANGES TO THE PTCIP (§ 236.1021 (D) (4)) ...................................................................... 7 5. MODIFICATIONS EFFECT ON PTC SYSTEM SAFETY (§ 236.1021 (D) (5)) ........................ 7 6. TIMETABLE FOR FILING UPDATED PTCIP ........................................................................... 7 Attachments Attachment A: Redlined version of the updated RTD IP Attachment B: Clean version of the updated RTD IP Revision 1.3 2 RTD PTCIP – RFA 1. INTRODUCTION 1.1 OVERVIEW AND PURPOSE In accordance with 49 Code of Federal Regulations (CFR) Part 236 Subpart I, the Denver Regional Transportation District (RTD) is filing the following Request For Amendment (RFA) of its provisionally approved Positive Train Control Implementation Plan (PTCIP). 49 CFR § 236.1021 (a) & (a)(1) provides that: (a) No changes, as defined by this section, to a PTC system, PTCIP, PTCDP, or PTCSP, shall be made unless: (1) The railroad files a Request For Amendment ("RFA") to the applicable PTCIP, PTCDP, or PTCSP with the Associate Administrator; The purpose of this document is to provide the required RFA to the FRA-approved RTD PTC Implementation Plan (IP), Version “Final” dated 5/22/2013. This RFA encompasses changes based on: • Incorporating edits based on responses to informal FRA comments, • Updates based on the current state of the Project to account for recent decisions and Project progress including the addition of a Mainline Track Exclusion Addendum (MTEA), • Adding information required by the Positive Train Control Enforcement and Implementation Act of 2015, and • General edits for readability and document organization. 1.2 SCOPE This RFA includes all information required by § 236.1021 (d): (1) The information listed in § 235.10 of this chapter and the railroad provides FRA upon request any additional information necessary to evaluate the RFA (see § 235.12), including: (2) The proposed modifications; (3) The reasons for each modification; (4) The changes to the PTCIP, PTCDP, or PTCSP, as applicable; (5) Each modification's effect on PTC system safety; Revision 1.3 3 RTD PTCIP – RFA (6) An approximate timetable for filing of the PTCDP, PTCSP, or both, if the amendment pertains to a PTCIP; and (7) An explanation of whether each change to the PTCSP is planned or unplanned. Specifically, each of these requirements is considered as follows: • § 236.1021 (d) (1) – Information required per § 235.10 is not directly applicable to this RFA as this RFA is not a discontinuance nor material modification that will affect installed systems. • § 236.1021 (d) (2) – The proposed PTC IP modifications are defined in this document. • § 236.1021 (d) (3) – The reasons for the proposed modifications are defined in this document. • § 236.1021 (d) (4) – Refer to § 236.1021 (d) (2). • § 236.1021 (d) (5) – The proposed IP modification have no effect upon safety. • § 236.1021 (d) (6) – Regarding filing timetable for the RTD DP and SP: o DP – RTD is utilizing the I-ETMS PTC DP which was previously a granted Type Approval by FRA-TA-2011-02-C. It is noted that per FRA direction, RTD provided an updated Concept of Operations (ConOps) document in the RTD PTC Test Request which supersedes the ConOps included in the previously noted I-ETMS PTC DP. The RTD PTC Test Request, including the updated ConOps, was approved by the FRA letter: Robert C. Lauby to Walt Stringer dated December 17, 2015. o SP – The RD PTC SP filing is anticipated to be in before December 31, 2016 or as advised by the FRA. • § 236.1021 (d) (7) – As this RFA does not pertain to a PTC SP, this requirement does not apply. 2. PROPOSED PTC IP MODIFICATIONS (§ 236.1021 (D) (2)) This section identifies the proposed modifications and the reasons for each as required by §236.1021(d)(2) & (3). It is noted that changes of an editorial nature to increase readability which do not affect the technical content of the PTC IP have been made which are not included in this description. These changes can be seen in the redlined version of the proposed PRC IP update in Appendix A herein. 1. Section 1 was modified to include reference to the MTEA which was added to Section 14. “Buried” reference documents have been relocated to Section 2.0 “Applicable Documents” and reference numbering added for clarity and document compactness. Text to the effect “a Revision 1.3 4 RTD PTCIP – RFA mainline track exclusion addendum will be filed” has been deleted as the IP now includes the MTEA. A statement to the effect that any differences between the RTD PTC System and that described in the referenced I-ETMS PTC DP will be accounted for in the RTD PTC SP. The note that the Employee Timetable will be provided when available has been deleted as the IP now includes the timetable as an Appendix. A note has been added referencing that the information required by the Positive Train Control Enforcement and Implementation Act of 2015 is included in Appendix 7. 2. Section 1.1 (East Corridor text) was modified to correct the number of stations, grade crossings, control points, etc., to agree with the actual as-built conditions. The 40th/Airport and Peña station name was corrected. Figures 1.1.1 and 1.1.3 were updated to include the Peña station. Text pertaining to the Northwest Electrified Segment was updated to account for the as-built number of at-grade crossings. Text pertaining to the Denver Union Station was updated to delete reference to the ski train, delete the DUS track layout (updated layout is included in Appendix 5), and for general readability. 3. Section 1.3 was modified to delete text to the effect “a mainline track exclusion addendum will be filed” as the IP now includes the MTEA. 4. Section 1.5.1 was modified to update the IP to the latest project schedule. The Figure containing the project schedule was also updated to reflect current project status. 5. Section 1.6 was modified to delete text to the effect “a mainline track exclusion addendum will be filed” as the IP now includes the MTEA. The Table in this section was updated to add a reference to the MTEA in the IP. 6. Section 2 was modified to update the referenced documents to agree with the IP text and to correct reference numbering. 7. Section 3.2 was modified to note that the referenced Type Approved PTC DP will be complied with except as identified, per FRA direction, in the RTD PTC ConOps provided as part of the RTD PTC Test Request. As further noted, and remaining differences between the RTD PTC implementation and the referenced Type Approved PTC DP will be accounted for in the RTD PTC SP. A technical note regarding interfacing the PTC onboard equipment was deleted as that information is not germane to the intent of a PTC IP. 8. Section 3.2.1 was modified to note that the cellular communications system is a backup to the PTC data radio. 9. Section 3.3 was modified to clarify that RTD will not be seeking a PTC Type Approval variance, per FRA direction. 10. Section 4.2 was modified to clarify the PTC DP which will be referenced by the RTD PTC system. 11. Section 5 was modified to note the inclusion of a MTEA in this version of the RTD PTC IP. 12. Section 7.2 was modified to clarify the Method of Operation to be used by RTD in the DUS (Traffic Control) and other railroads (Operating rules including restricted speed operation). Revision 1.3 5 RTD PTCIP – RFA 13. Section 8.1 was modified to correct to the number of EMUs being procured for RTD from 50 to 54. 14. Section 8.2 was modified to more accurately reflect current project revenue service target dates (e.g., the East Corridor was changes from “January 2016” to “2nd Quarter 2016”). 15. Section 9 was modified to include roadway crossing equipment in the list of wayside equipment and to delete a reference to Table 2 in Section 11 as that table has been deleted. 16. Section 9.3 was deleted to since defect detectors will not be used. 17. Section 9.3 (new numbering after the deletion of original 9.3 above, old section 9.4) was modified to add Peña station to the table. 18. Section 9.4 (new numbering after the deletion of original 9.3 above, old section 9.5) was modified to add Peña station to the table. 19. Section 10 was modified to replace text to the effect “a mainline track exclusion addendum will be filed” with a reference the MTEA details located in Section 14. 20. Section 11 was modified to delete the Table which had provided construction completion estimated dates. This information was redundant as this information has already been provided in Section 1.5.1. A reference to the data in Section 1.5.1 was added. 21. Section 13 was modified to reference the PTC DP in the reference section instead of having the specifics of the referenced document buried in the text. The date by which the RTD PTC SP will be filed was changed from March 2015 to before December 31, 2016.

Load more

  184

Copy Link