ELECTRICAL DESIGN PRACTICE NOTE ELECTRICAL SYSTEM REQUIREMENTS

Transcription

1 Approval Amendment Record Approval Date Version Description 12/02/ First Issue PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 1 of 6

2 Table of Contents 1 Purpose Background The Issue The Requirement/Objective Attachments... 4 PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 2 of 6

3 1 Purpose To require all parties proposing an addition or a change to the electrical systems to obtain a Systems Requirements document from the Head of Electrical/Engineering. 2 Background Projects and renewal works have been proposed without due consideration to the up stream and down stream implications of the impact on the wider electrical network. Examples include the proposal to install a new substation without early discussions with the supply companies resulting in delays and compromises to the final installation. There are now locations where the output of the traction substation is limited by the electrical protection settings and additional infrastructure will be required to operate the substation to its capacity. There are projects involving new substations where the scope of works specifically excludes changes to the electrical protection systems supplying the substations. Additional capacity has been installed in some systems without recognition that the fault carrying capacity of legacy equipment is exceeded. Compromises have been accepted in reticulation systems that have resulted in essential systems being dependent on a single electric supply. 3 The Issue The electrical networks, including substations, tiestations, 1500Vdc traction overhead and 22Kv transmission system are a system and all items associated with the system including capacity, voltage levels, fault protection, fault discrimination and redundancy under failure conditions require consideration BEFORE project or renewal scopes of works are locked down. The functional requirements as per Form MEMF also need to be included in the system documentation. Failure to address the electrical networks at the system level results in compromise with the potential to increase network risk. 4 The Requirement/Objective This Practice Note requires all persons developing projects or renewal works that impact the electrical system, to undertake a System Requirements Review (SRR), after the Preliminary Requirements Review (PRR) has been undertaken, in accordance with L3- PRJ-GDL-002 Engineering Management System Methodology. The SRR shall include a system requirements document produced and approved by the Head of Electrical/Engineering, such that the electrical network implications of the proposal are incorporated into the scope of works and potential network risks are removed. Note that the PRR stage requires a Final Impact Statement, Final Operation Statement and Project Brief, in accordance with Figures 1 and 2 of L3- PRJ-GDL-002, Attachment 1. The purchase of major electrical equipment such as rectifiers, rectifier transformers and substation high voltage circuit breakers shall not occur without a system requirements document and the consent of the Head of Electrical/Engineering. The advice from Head of Electrical /Engineering shall be written and incorporated into the project or renewal works documentation. PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 3 of 6

4 Where the proposed works involve interaction with a supply company as determined by the Head of Electrical/Engineering, the advice shall include an agreement from the supply company to the principles of the project.` 5 Attachments PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 4 of 6

5 Concept Definition & Analysis Preliminary Definition & Detailed Qualification and Fabrication System Integration, T&C and Deployment HW development CDR Detailed Fabrication of HW Product to Qualified HW Product Preliminary System/HW Reqts Analysis and Definition HW Specification(s) Development Acceptance Review System Concept Requirements PRR SRR Concept X PDR CDR X TRR X T-20 T-12 T-5 System Integration and and Commissioning Handover/ Deployment CDR Critical Review CM Configuration Management DDR Detailed Review HW Hardware PDR Preliminary Review PRR Preliminary Requirements Review SRR System Requirements Review SW Software TRR Test Readiness Review WRR Works Readiness Review Mandatory, Formal Review Optional Review System/SW Reqts Analysis and Definition SW Specification(s) Development SW development Architectural (Preliminary) Detailed DDR SW Implementation, Unit, Integration & SW Product Occupation X Works Readiness Gate Formal Gate Functional Baseline Allocated (Development) Baseline Baseline Product Baseline Informal ( Engineering ) CM Formal CM PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 5 of 6

6 Stakeholders Requirements Assessment ( SRA ) NPD, NAM, ENGINEERING, SAFETY PROPOSED APP Multiple Options POR & PIS Single, Final Option FOR & FIS Project Brief PRINTOUT MAY NOT BE UP-TO-DATE; REFER TO METRO INTRANET FOR THE LATEST VERSION Page 6 of 6