Process Control System (PCS) Implementation Guidelines · programming. As custodian of PLC software...

Process Control System (PCS) Guidelines

Implementation Guidelines

Process Control System (PCS) Implementation Guidelines

Version 3

December 30, 2015



Process Control System (PCS) Implementation Guidelines Record of Revision

Revision Number

Date Of Revision

Revised Pages

Revised by

1 July 30, 2011 General 2 October 30, 2012 Various Boro Djunisijevic 3 December 30, 2015 Various Boro Djunisijevic



PCS Implementation Guidelines-V3

1-2 Dec 2015

Table of Contents

1. Introduction ......................................................................................................................... 1-4

1.1 General ..................................................................................................................................... 1-4 1.2 Scope of Guideline .................................................................................................................. 1-4 1.3 Objectives ................................................................................................................................ 1-4 1.4 Guideline ................................................................................................................................. 1-5 1.5 Definitions and Roles .............................................................................................................. 1-5

2. RFP and Engineering Services Contract Award ........................................................... 2-10

2.1 General ................................................................................................................................... 2-10 2.2 Identify PCS Requirements ................................................................................................... 2-10 2.3 Scope of Work ....................................................................................................................... 2-10 2.4 RFP ........................................................................................................................................ 2-10 2.5 RFP Evaluation ...................................................................................................................... 2-10 2.6 Engineering Services Contract Award ................................................................................... 2-11

3. Pre-Design ......................................................................................................................... 3-12

3.1 General ................................................................................................................................... 3-12 3.2 Project Commencement ......................................................................................................... 3-12 3.3 Field Verification ................................................................................................................... 3-12 3.4 Requirements Definition/50% Pre-Design ............................................................................ 3-12 3.5 75% Pre-Design ..................................................................................................................... 3-14 3.6 100% Pre-Design ................................................................................................................... 3-15

4. Detailed Design .................................................................................................................. 4-16

4.1 General ................................................................................................................................... 4-16 4.2 Tag Lists ................................................................................................................................ 4-16 4.3 50% Detailed Design ............................................................................................................. 4-17 4.4 70% Detailed Design ............................................................................................................. 4-18 4.5 Detailed Technical Specifications ......................................................................................... 4-20 4.6 Apply For Approval ............................................................................................................... 4-20 4.7 95% Detailed Design ............................................................................................................. 4-20 4.8 100% Detailed Design ........................................................................................................... 4-21

5. Construction - Equipment ............................................................................................... 5-22

5.1 General ................................................................................................................................... 5-22 5.2 Shop Drawings ...................................................................................................................... 5-22 5.3 Equipment and Panel Procurement and Fabrication .............................................................. 5-22 5.4 Test Sheets ............................................................................................................................. 5-22 5.5 Equipment and Panel FATs ................................................................................................... 5-22 5.6 Transition Plan ....................................................................................................................... 5-23 5.7 Equipment Installation and Wiring ........................................................................................ 5-23 5.8 Pre-Start Health and Safety ................................................................................................... 5-23 5.9 Entity Information Lists ......................................................................................................... 5-24




1-3 Dec 2015

6. Construction - Software ................................................................................................... 6-25

6.1 General ................................................................................................................................... 6-25 6.2 Flow Chart Development ....................................................................................................... 6-25 6.3 Software Modules .................................................................................................................. 6-25 6.4 Software Development .......................................................................................................... 6-25 6.5 FAT Plan ................................................................................................................................ 6-26 6.6 Software FAT ........................................................................................................................ 6-26

7. Construction – Testing and Commissioning .................................................................. 7-27

7.1 General ................................................................................................................................... 7-27 7.2 Hardware SAT and Training Plan ......................................................................................... 7-27 7.3 Hardware Training ................................................................................................................. 7-27 7.4 Hardware SAT ....................................................................................................................... 7-27 7.5 Software SAT and Training Plan ........................................................................................... 7-28 7.6 Software Training .................................................................................................................. 7-28 7.7 Software SAT ........................................................................................................................ 7-28 7.8 Operational Test/System Performance Test .......................................................................... 7-28 7.9 Tag Lists and PCS I/O List .................................................................................................... 7-29 7.10 As-Built Documentation ........................................................................................................ 7-29 7.11 Post Construction Warranty Period ....................................................................................... 7-29

Appendix A – Project Tasks Flowcharts

Appendix B – Project Tasks Implementation Checklists

Appendix C – Associated Guidelines

Appendix D – Associated Standards and Installation Drawings List

Field Verification Procedure Process Control Narrative P&ID Standard Symbols and Practices Colour Convention RPU Software Programming Standard Software Modules Operator Interface Programming Process Display Programming Alarming Instrument and Equipment Testing SCADA Factory Acceptance Testing SCADA Site Accecptance Testing and Commissioning PCS Documentation Training




1-4 Dec 2015

1. Introduction

1.1 General Toronto Water has implemented a Process Control System (PCS) for control and monitoring of its facilities (Water treatment plants, Wastewater treatment plants, Water supply, and Sewage pumping stations). The PCS consists of instrumentation, control devices, wiring, networking, input/output devices, control panels, local and central Human Machine Interfaces (HMIs) and Remote Processing Units (RPUs) / Programmable Logic Controllers (PLCs). Any new project in Toronto Water that has a PCS component will require integration of the new project into the existing PCS of the facility. The overall process for any project with a PCS component comprises six stages:

1. RFP development, issue, evaluation, and subsequent contract award for engineering services

2. Pre-design of the PCS component

3. Detailed design of the PCS component

4. Construction - Equipment

5. Construction – Software

6. Construction – Testing and Commissioning

Please refer to Appendix A (Flowcharts) and Appendix B (Checklists) for tools to assist with the process of integrating any new project into the existing PCS of the facility. The relationship between deliverables and project stages is not always evident for projects where the PCS component is relatively small. Some of the stages/phases mentioned in the Flowcharts and Checklists may not apply for very small PCS projects.

1.2 Scope of Guideline This guideline provides ‘high level’ information for consultants and project managers on project deliverables, phasing, and review requirements for Toronto Water projects that have a PCS component.

1.3 Objectives The guideline objective is to ensure that a clear understanding exists for City project managers and consultants as to the deliverable requirements for a PCS project or project with a PCS component, in terms of the phasing for those deliverables and services in step with various project phases from initial design stages to completion of the project, as well as defining the responsibilities for provision of information and deliverable review services.




1-5 Dec 2015

1.4 Guideline Guidance documentation for the PCS implementation comprises three separate and related documents: a series of project task flow charts illustrating the logical flow deemed necessary for successful implementation of the project (Appendix A); a checklist intended for project managers to ensure engineering services providers deliver the required services and documentation at the appropriate stage of the project (Appendix B); and the Process Control System Implementation Guideline (this document).

Flowcharts for each stage are comprehensive and are designed to ensure the deliverables, their inter-relationships, and their delivery timing is appropriate for successful implementation of PCS projects. Depending upon the project size and scope, some of the steps in the various stages may not be required.

Checklists for each stage provide a simplified review method for project managers to ensure consultant deliverables are provided at the right project stage, as well as indicate supply sources for information typically needed by the consultant and to indicate the in-house review group for all consultant technical deliverables. The checklists also indicate the flow of information and can be used as a tool by project managers to guide a PCS project. Depending upon the project size and scope, some of the steps in the various checklists may not be required. As part of the project scope development, the project manager – with assistance from the Toronto Water PCS Unit – will develop the project tasks checklists specific to the project. Once the “scope of work for a RFP” has been defined, then a “project specific checklist” shall be prepared, and provided in the RFP.

The Process Control System Implementation Guideline is intended to address how engineering services are provided, and at what stage each service and its corresponding deliverable is provided, and provides more specific, and more detailed, assistance to the engineering services provider in how PCS projects should be conducted. External references to other, more specific, guideline documents are also provided throughout this document.

1.5 Definitions and Roles The groups typically involved in PCS projects and their respective roles are detailed below.

1. City

The owner (City of Toronto) generally performs all tasks detailed below in Section 2 RFP and Engineering Services Contract Award as well as reviewing the work of the Consultant, Contractor, and Systems Integrator. The City may involve the following internal organizations, depending on the components and complexity of the project:

City’s Project Manager

The project manager is the single point of contact for all communication between the City and the Consultant for the project, unless others are designated as contacts for specific purposes. Responsibilities of the project manager include:




1-6 Dec 2015

i. Initial project planning and RFP preparation

ii. Tendering and award for consulting services

iii. Ensure timely submission of deliverables from Consultant and timely review by City staff

For more detailed information on the responsibilities of the project manager, consult the Toronto Water Project Delivery System manual.

Capital Works Delivery (CWD)

CWD is TW engineering group providing project management and advisory to the Operation Group for the various complex electrical systems projects. The CWD is custodian of TW facilities Master Single Line Diagrams (SLD)

PCS Unit (PCSU)

PCSU reffers to PCS unit within Toronto Water, Operational Support providing:

Capital Project Support Services

Toronto Water Network Services

SCADA Maintenance & Integration Services

PCSU maintains the standards and guidelines for PCS projects and technology. PCSU also maintains facilities PCS master documentation: Master P&ID, Master Process Control Narratives, SCADA Architecture Drawings, Hardware and Software Inventory Lists. As custodian of Electronic Tagging Management System (ETMS) PCSU manage tagging requests & approvals. The unit provides engineering support for review of design reports, engineering drawings, specifications and cost estimates. PCSU also assists with coordinating the various internal City organizations for purposes of deliverable review and comment.

The PCSU provides support for review of SCADA hardware and software deliverables such as servers, PLCs, networking, and all related customized programming. As custodian of PLC software modules PCSU get involved in testing and approval of any new software module, if needed.

Operation Group

The Operation Group refers to the support staff at the facility at which the project is being undertaken. They will be the principal group driving the development of the Scope of Work, and will review deliverables for operability and maintainability during the project, to ensure compatibility with existing equipment at the facility. They are also active participants in Factory and Site Acceptance Tests.

Optimized Maintenance Unit (OMU)




1-7 Dec 2015

The OMU maintains the Work Management System (WMS) databases for TW assets including all PCS related equipment in Toronto Water Facilities. Their involvement in PCS projects will typically be to review and approve WMS tagging assignments proposed by the Consultant.

2. Consultant

The Consultant is contracted by the City to perform the Scope of Work as defined in the RFP. The Consultant generally performs all tasks detailed below in Section 3 Pre-Design and Section 4 Detailed Design as well as representing the City during the Construction phase. As the City’s representative, the Consultant will review all deliverables from the Contractor and System Integrator providing comments to the City. The Consultant also participates in FAT, SAT, Commissioning and Training activities, and updating of documentation of the project.

A detailed list of the Consultant’s responsibilities follows:

Responsible for the engineering and design of the I&C and SCADA System, including integration with existing system control logic

Preparation/Updating of Process Control Narratives and P&ID

Preparation of Contract Specifications and Drawings of I&C and SCADA system

Review of the RPU and HMI configuration, as prepared by the Contractor, and ensure compliance with City’s standards

Prepare requirements for factory acceptance test (FAT) plan

Attend and witness FAT at the Contractor’s facility to ensure compliance with City’s requirements

Attend and witness testing of all field instruments and control loops performed by the Contractor

Prepare requirements for site acceptance test (SAT) plan

Attend and witness SAT on site to ensure compliance with City’s requirements

Prepare requirements for operational test/system performance test

Attend and witness operational test/system performance test

Review Operation and Maintenance Manual prepared by the Contractor for compliance with the contract specifications

Review Plant SCADA Operation Manual and submit at the specified milestones

Prepare PCS training




1-8 Dec 2015

Testing and verification of the performance of the SCADA system

Prepare As-built PCS documentation

3. Contractor

The Contractor is contracted by the City to perform the Scope of Work as defined in the tender package created by the Consultant during Detailed Design and generally performs all tasks detailed in Section 5 Construction - Equipment and Section 7 Construction – Testing and Commissioning.

A detailed list of the Contractor’s responsibilities follows:

Purchase and install all software, hardware, instrumentation and field wiring as specified

Perform Hardware FAT at the Contractor’s facility, (if possible) witnessed by the Consultants and the City’s staff

Perform field verification of all installed instruments, devices and control loops, witnessed by the Consultants and the City’s staff

Participate in Consultant’s PCS training as applicable

Perform Hardware SAT, witnessed by the Consultants and the City’s staff

Perform operational test/system performance test, witnessed by the Consultants and the City’s staff.

Hand over SCADA system to City’s staff when accepted by the City.

Provide required warranty (response within 24 hours) and guarantee of SCADA system

Respond to City for all deficiencies

Prepare I&C Operation and Maintenance Manual and submit to the Consultants for review at the appropriate milestones

4. Systems Integrator

The Systems Integrator is typically a subcontractor of the Consultant or Contractor but also could be integral part of the Consultant's/Contractor's team. In any case System Integrator generally perform all tasks detailed below in Section 6 Construction - Software and Section 7 Construction – Testing and Commissioning.

A detailed list of the System Integrator’s responsibilities follows:




1-9 Dec 2015

Configure PLC program in accordance with specified process control narratives

Configure HMI program in accordance with specified process control narratives

Submit PLC and HMI programs to Consultants for review to ensure compliance with Specifications

Participate in Consultant’s PCS training

Perform Software FAT at the System Integrator’s facility, (if possible) witnessed by the Consultants and the City’s staff

Perform Software SAT, witnessed by the Consultants and the City’s staff

Perform operational test/system performance test, witnessed by the Consultants and the City’s staff.

Hand over SCADA system to City’s staff when accepted by the City.

Provide required warranty (response within 24 hours) and guarantee of SCADA system

Respond to City for all deficiencies

Prepare SCADA Operation and Maintenance Manual and submit to the Consultants for review at the appropriate milestones




2-10 Dec 2015

2. RFP and Engineering Services Contract Award

2.1 General In general, RFP and Engineering Services Contract Award tasks are performed and/or coordinated by the City’s Project Manager. See Appendix A – Flowcharts for a concise depiction of tasks and deliverables required during this phase.

2.2 Identify PCS Requirements Conduct workshop(s) with PCSU and Operation Groupto gather requirements of the new project including input on the following:

Instrumentation

Control System Hardware

Software

Networking

Structured Cabling

Electrical

Gather input on how the proposed project will affect the current facility PCS, and what additions and changes may be required.

2.3 Scope of Work Draft a Scope of Work based on the information gathered at the workshop(s) and has it reviewed by the various groups to ensure that the PCS elements are consistent with City objectives and standards. Amend the Scope of Work as required.

2.4 RFP Draft the PCS elements of the RFP including project specific “PCS checklist” following City’s PCS Guidelines, Standards, and the Project Delivery System (PDS). Drafted RFP shall be reviewed by PCSUand Operations group.

Issue the RFP and involve PCSUand the Operation Group as required during the RFP process.

2.5 RFP Evaluation Evaluate RFP responses with input from PCSUand the Operation Group as required




2-11 Dec 2015

2.6 Engineering Services Contract Award Award the project to a Consultant with input from PCSUand the Operation Group as required.




3-12 Dec 2015

3. Pre-Design

3.1 General In general, Pre-Design tasks are performed by the Consultant and supervised by the City. See Appendix A – Flowcharts for a concise depiction of tasks and deliverables required during this phase. The Consultant shall follow Toronto Water’s PCS Guidelines and Standards throughout all phases of the project.

The purpose of the Pre-Design Report is to identify the key elements of the design to ensure that the final installation will meet the functional requirements and performance of Toronto Water. During the pre-design phase, the Consultant is expected to:

1. Visit the existing facility, or similar facility in Toronto Water, and familiarize themselves with the existing interfaces, PCS equipment including tagging, software, control strategies, and network architecture to be matched and/or upgraded.

2. Review all engineering reports and drawings for the PCS system related to the project.

3. Review previous pre-design report(s) and detailed designs prepared for the PCS system.

In general, consultants will comply with Appendix A.4 PREDESIGN ENGINEERING SERVICES of the RFP document, specifically with respect to the PCS system.

3.2 Project Commencement Conduct a Project Commencement Meeting, and invite PCSUand the Operation Group representatives. The purpose of the meeting is for the Consultant to introduce their project team and have a discussion of the general strategy and goals of the project.

3.3 Field Verification The Field Verification Procedure shall be completed on commencement of pre-design engineering to ensure that the design will meet the requirements of the facility. This will minimize potential future claims by Contractors during construction, resulting from inaccurate information portraying existing conditions. This activity will also accurately define the scope of work required for achieving the targeted level of automation.

Refer to Field Verification Procedure for more information.

3.4 Requirements Definition/50% Pre-Design The following elements should appear in the 50% submittal:




3-13 Dec 2015

1. Equipment and Instrumentation List - Design equipment and instrumentation to permit full monitoring and control capability under manual and/or automatic control. Refer to Instrumentation Design Standard. Prepare a table (example below) of all existing (reused) and proposed equipment and instrumentation (also refers as equipment, device or asset) to be installed for the project. The table should be filled in as much as possible during Pre-Design and then modification can continue through the Detailed Design and Construction phases. The table would be the source document for preparation of Tag List(s) to be created at the beginning of Detailed Design. It will also be used for Entity Information List (WMS list) initially populated by Consultant and completed by Contractor after the installation and commissioning.

Refer to General Instrumentation Requirements Standard for the list of approved instruments and manufacturers for the City’s PCS projects. The list of approved manufacturers shall be reviewed in conjunction with the staff of the affected facility. This list is part of PCS Standards and Specifications that will be made available on request at this stage of the project as well as the other required Standards and Specifications referred to further in this document (see Appendix D for the full list of PCS Standards and Specifications).

Notwithstanding the inclusion of equipment in the approved manufacturers list, the Consultant is responsible for engineering design and project performance. The Consultant shall review the existing equipment at the facility and the approved list, discuss with the City the current performance of the equipment, and in conjunction with the City provide recommendation for first named and alternate named equipment to be specified using the approved list as a base.

Make recommendations to the City if additional manufacturers are requested to be added or removed as appropriate according to Consultant experience and the specific project requirements. This list will form the basis of named and alternate named manufacturers and suppliers in the Contract Specifications.

Table 1: Equipment and Instrumentation List

Headings of Table Development Stages Predesign Detailed Design As Constructed

Equipment (Device)Tag (WMS/PCS Tag Number)

Required Required

Device (Tag) Description (WMS Asset Entity Name)

Required Required Required

P&ID Required Required

Process Required Required Required

Area Required Required Required

Unit Required Required Required

Device Type Required Required Required

Status Required Required Required




3-14 Dec 2015

Headings of Table Development Stages Predesign Detailed Design As Constructed

Comment Required Required Required

Note: Naming convention for the Equipment (Device) Tag Name (in WMS referred as Entity Name) is described in Tagging Standard: Equipment and Data Tagging.

2. Servers/PLCs/Network - Review and document all existing hardware affected by the project, and determine system capacity. Discuss capability for expansion and identify all additional hardware required for modifications so as to fully integrate the new or expanded works into the existing system. Identify all obsolete hardware that must be replaced as part of the upgrading of the existing or expansion of the process control system. Refer to SCADA Computer System and PCS Local Area Network (Appendix D) for technical detail and requirements.

3. SCADA Software - Review and document all existing software affected by the project, and identify all additional software required for modifications to the HMI, PLC and networking devices so as to fully integrate the new or expanded works into the existing system.

4. Control Wiring and Structured Cabling – Review and document all existing control wiring and network cabling, and identify all additional cabling that will be required so as to fully integrate the new or expanded works into the existing system.

5. Alarm Notification and Security – Review the existing alarm notification and security system of the facility, and document the proposed modifications and additions to provide the required services for notification of the critical PCS alarms of the project. Refer to Alarming (Appendix C) for technical details and requirements.

6. Electrical System and Emergency Power – Review the existing power supplies to the relevant areas of the facility and document the proposed modifications and additions to provide the required electrical power for the proposed upgrades.

3.5 75% Pre-Design In addition to updates to the elements of the 50% pre-design, the following should appear in the 75% submittal:

1. Process Narrative – Provide a Process Narrative or update existing for each process, clearly describing how it is to be operated in all modes of process control. Process narratives shall be written in plain English to provide a clear understanding of the relationships between the equipments and the process variables to be monitored/controlled. Note that the Narrative will not apply solely to the new processes/equipment, but will detail all interaction with existing process/equipment control (i.e., alarm triggers, process variables shared by multiple processes, report




3-15 Dec 2015

generation, etc.). Refer to Process Control Narratives (Appendix C) Section 1.3.1 for technical detail and requirements.

2. Process Flow Diagrams – Provide a Process Flow Diagram or update existing to clearly illustrate the relationships between the various affected processes and associated instrumentation.

3. Design Alternatives – The Consultant should include a section detailing any alternative designs that they feel might offer benefits to the City in terms of cost or functionality.

4. Cost Estimate – Include a cost estimate to construct the project according to the guidelines provided in the RFP.

5. Electrical Area Classification Report – If required, provide “Electrical Area classifications report” for the affected areas where electrical and instrumentation devices will be installed under the project.

3.6 100% Pre-Design The 100% Pre-Design submittal should include updates to reflect the comments made during review of the 75% submittal. City staff will review the 100% submittal and again provide comments to allow the Consultant to finalize the Pre-Design report.




4-16 Dec 2015

4. Detailed Design

4.1 General In general, Detailed Design tasks are performed by the Consultant and supervised by the City. See Appendix A – Flowcharts for a concise depiction of tasks and deliverables required during this phase.

Consultants will comply with Appendix A.5 DETAILED DESIGN ENGINEERING SERVICES of the RFP document, specifically with respect to the PCS system.

4.2 Tag Lists The City maintains a tag database known as the Enterprise Tagging Management System (ETMS). The Consultant shall have access to this database during design for the purpose of creating unique tag names and producing a Tag Lists for review by the City. If access to ETMS is not provided Consultant shall request ETMS tag report for the related facility and process(es). All equipment, equipment loops, data and local area network cabling shall be tagged in accordance with Equipment and Data Tagging Standard (Appendix D). Use of ETMS shall secure uniqueness and proper tag structure in accordance with Standards. However Consultant shall use related Master P&IDs in conjunction with ETMS/ETMS tag report in order to assure tag loop numbers follow the existing tagging logic. These tag numbers shall be used in the P&ID drawing(s) and all related project documentation for the identification of all equipment. Tags will be reserved in ETMS and could be modified during the life of Project. Any modification to the tagging should be identified by Consultant followed by request to City for approval.

Consultant shall prepare:

1. New equipment tag list. Consultant shall prepare and submit for approval new equipment tag list in particular format. "TagImportTemplate.xsl" spread sheet will be issued on requested.

2. Replace equipment tag list. This list refers to the equipment that is going to be replaced or upgraded. Equipment tag will not be changed but equipment description might (i.e. gate valve replaced with butterfly valve, valve actuator added or variable speed drive added to the pump). These types of changes are to be identified in separate "New description" column. Changes to the ETMS will be done by City once construction is completed. At that time also Entity Information List (WMS list) shall be completed in accordance with Equipment and Data Tagging (Section 3.12) for all replaced and upgraded equipment.

3. Reuse equipment tag list. This list refers to the equipment that is going to be reused in same or different capacity (function). Any changes are to be identified and to be dealt with the same way as for the "Replace equipment tag list" above.




4-17 Dec 2015

4. Reused tag list. This list refers to tags of the removed or "to be removed" equipment but there is intention to reuse (recycle) tags. Consultant should identified measures during transition if there is period where two identical tags in the field and SCADA would exist (old equipment to be removed after new equipment is commissioned). After construction is completed ETMS database should be updated. WMS data for the old equipment are to be retired. WMS data for the new equipment shall be completed in accordance with Equipment and Data Tagging Standard (Section 3.12) for all replaced and upgraded equipment.

5. Remove/Delete equipment tag list. Consultant is to identify and submit list of the equipment that will be removed. After construction is completed tags in ETMS and WMS databases will retire.

4.3 50% Detailed Design The following elements should appear in the 50% Detailed Design submittal:

1. Process Control Narrative (PCN) – The Consultant shall update the Master PCN provided by the City. Refer to Process Control Narratives (Appendix C) for details of the requirements.

2. P&IDs - The Consultant shall update the Master P&IDs provided by the City, or prepare new P&IDs (in case Master P&IDs do not exist). The City’s instrumentation symbols and control and instrumentation loop diagrams, including process and instrumentation diagrams, are generally based on the Instrument Society of America Standards ANSI/ISA-S5.1-1984 (R 1992) and ANSI/ISA-S5.4-1991, or latest revision. The ISA standards have been modified by the City to meet its own requirements. Consultants shall comply with P&ID Standard Symbols and Practices (Appendix C).

3. SCADA Architecture Drawings – The Consultant shall update the Master SCADA Architecture drawing of the facility, to show modifications and additions of equipment.

4. Typical I&C Drawings – The Consultant shall develop typical device Control Schematics and typical Instrument Wiring Diagram/Loop Drawings. Refer to Electrical Control Schematic Diagrams Standard (Appendix C) for drawings development.

5. Equipment Power Requirements – The Consultant shall provide drawings and specifications for any power supply upgrades or additions required as a result of new or modified equipment.

6. SingleLine Drawings – If the new equipment requires changes to the facility’s Master SLD, they shall be provided as part of this submission.

7. Electrical Area Classifications – These shall be updated from the classifications provided in the Pre-Design Report.

8. Cost Estimate – Provide an updated cost estimate.




4-18 Dec 2015

4.4 70% Detailed Design In addition to updates to the elements of the 50% design, the following should appear in the 70% submittal:

Equipment Layouts – The Consultant shall produce equipment and instrumentation layout drawings as required. The layouts are 'not to scale' drawings that shall show approximately position of the devices within the facility/area.

I & C Schematics – The Consultant shall produce for each device/instrument Device Control Schematics and Instrument Wiring Diagram/Loop Drawings based on the approved typical I&C drawings developed in 50% detailed design phase. Refer to Electrical Control Schematic Diagrams Standard (Appendix C) for Control Schematic development.

Control Panel Drawings – The Consultant shall provide drawings for new panels or modifications to any existing control panels. Refer to Control Panel Design (Appendix C).Control Panel Drawings should include:

1. Control Panel Layouts

2. RPU (PLC) Layout

3. Panel Power Distribution

4. I/O Modules Wiring Diagram

Refer to Electrical Control Schematic Diagrams Standard (Appendix C) for typical I/O module wiring diagrams development.

Cable Block Diagram Requirements – The Consultant shall identify requirements for development of cable block diagrams by Contractor during the construction phase. These diagrams should show all cables, as a minimum identifying: source and destination location (from-to), type, number of wires, wire size and all junction boxes between source and destination where applicable. Cable block diagrams should be included in Consultant's as built PCS drawings.

SCADA Hardware and Software Requirements – The Consultant shall create or update the Hardware and Software Inventory Lists (Server, Client, RPU and Access Closet hardware and software inventory and available capacity) for the facility, indicating what new software or hardware is required for the SCADA system

Instrument Ranges and Setpoints – As part of the Process Control Narrative, this information shall be provided at this stage.

PCS I/O tag list - Consultant shall provide PCS I/O tag list (example below), also referred as signal/data or PCS I/O point tag name, for inclusion in ETMS database upon approval from City. The list shall identify related device status: new, reuse, replace, and




4-19 Dec 2015

delete as well as intention to reuse (recycle) device tag. ETMS database will be populated in stages as described earlier (see 4.2 Tag Lists).

Alarm List - As part of the Process Control Narrative, this information shall be developed complete with Alarm Priority (High, Medium, Low, WIN911) and “Alarm Conditioning” at this stage.

iHistorian, eOPS, POMS, LIMS Requirements - As part of the Process Control Narrative, this information shall be available at this stage.

Alarm Notification and Security – Detailed Design of the alarm notification requirements that were provided in the Pre-Design Report.

Coordinate with the City’s corporate security for security related issues.

Networking and Structured Cabling - Detailed Design of the networking and structured cabling requirements that were provided in the Pre-Design Report.

Entity Information List (WMS list) – Consultant shall initially populate Entity Information List (WMS list) with design data (Tag name, description, type, location, size, range, etc.). See Equipment and Data Tagging Standard (Appendix D) for the template. The list will be further developed in Construction phase.

Equipment Physical Tag Lists - Field equipment shall be tagged in accordance with Equipment and Data Tagging. Templates are included in the Document. Provide completed Physical Tag Lists indicating details of the tag quantities and sizes.

Electrical Drawings and Requirements – Drawings showing electrical upgrades required for the project.

Identify FAT and SAT Requirements – Provide Initial FAT/SAT Check Sheet and Process Logic Test Sheet in accordance with PCS Factory Acceptance Testing and PCS Site Acceptance Testing and Commissioning (Appendix C). FAT/SAT Check and Process Logic Test Sheets are to be further developed in Construction phase.

Identify Hardware and Wiring Removal – Drawings to indicate obsolete hardware and wiring that is to be removed under the project.

Identify RPU/HMI Program/Code Removal – Produce a detailed list indicating which software tags/objects should be removed under the project.

Table 2: PCS I/O tag list

Headings of Table Development Stages Detailed Design As Constructed

PCS I/O Tag Required Required

PCS I/O Tag Description Required Required

Signal/Data Type

Physical Required Required Virtual Required Required




4-20 Dec 2015

Headings of Table Development Stages Detailed Design As Constructed

Analog Required Required Digital Required Required

Engineering Units Required Required

Signal Used

PCS Required Required

iHistorian Required Required

eOPS Required Required

POMS Required Required

LIMS Required Required

WMS Required Required

Comment Required Required

Note: PCS I/O Tag Description shall be description of the associated signal easily understandable to the Operator and shall be limited to 40 characters.

4.5 Detailed Technical Specifications The Consultants shall refer to the PCS standards listed under PCS Standards and Specifications List (Appendix D) and related Guidelines Appendices and shall use or adhere to those requirements. Consultants should obtain electronic versions of these standards and appendices related to the project from the City’s Project Manager.

The Consultants shall modify or edit the standards and appendices and create specifications to suit the project specific requirements of the contract, after getting consent from PCSU. However, where modifications are recommended, the Consultant is to highlight these proposed deviations to the City to ensure that the proposed changes do not compromise the City’s overall goal of standardizing PCS across Toronto Water facilities. The responsibility remains with the Consultant to ensure that contract specifications and drawings meet the requirements for proper project execution.

4.6 Apply For Approval Once the 70% Detailed Design package has been accepted by the City, it is expected that the Consultant will obtain approvals from agencies as required. Comments made by the approving agencies are to be incorporated into the documents for the 95% submittal to the City.





4-21 Dec 2015

1. Pre-Start Health and Safety – The Consultant shall review and report as required.

2. Electrical Area Classifications – The Consultant shall update electrical area classifications based on the detailed design

3. Updated Cost Estimate


1. Tender Document – The Consultant shall complete the preparation of the tender package.

2. Updated Cost Estimate




5-22 Dec 2015

5. Construction - Equipment

5.1 General In general, Construction – Equipment tasks are performed by the Contractor and supervised by the Consultant. See Appendix A – Project Tasks Flowcharts for a concise depiction of tasks and deliverables required during this phase.

Consultants will comply with Appendix A.6 SERVICES DURING CONSTRUCTION of the RFP document, specifically with respect to the PCS system.

As the City’s representative during construction, the Consultant will review all deliverables from the Contractor and System Integrator and solicit the City’s comments in addition to their own before returning reviewed deliverables to the Contractor.

5.2 Shop Drawings The Contractor is to submit shop drawings for all equipments and panels to be purchased for installation during the contract. The Consultant will review the shop drawings in accordance with Instrument and Equipment Testing (Appendix C). The City has the option to review shop drawings as well though the responsibility for accuracy and correctness lies with the Consultant.

5.3 Equipment and Panel Procurement and Fabrication The Contractor will procure equipment and manufacture panels as required, after approval of the shop drawings. The Consultant will monitor the progress and ensure the project schedule is maintained.

5.4 Test Sheets Contractor is to provide Pre-FAT test documentation for major equipment such as MCCs, pumps, etc.

5.5 Equipment and Panel FATs The purpose of hardware FATs is to ensure the integrity of the equipment used to control and monitor the process at the City’s facilities. It is intended to demonstrate that the system configuration will function effectively once installed on site, and limits the need for on site modifications to hardware configurations.

The hardware FAT involves the following major components:

1. Control Panels & Local Operator Interfaces

2. Networking Equipment




5-23 Dec 2015

3. Workstations

4. PLCs.

The hardware FAT is performed at the Contractor's office. These tests must be completed by the contractor and approved by the Consultants prior to any equipment being delivered to the project site. The City has the option to witness the FATs as well, though the responsibility for approval lies with the Consultant.

5.6 Transition Plan A project will typically involve installing equipment into an existing, operating facility that has an operating PCS. The Contractor shall develop a transition plan that details the progression of installation tasks such that the impact on operations is minimized and the continued safe operation of the facility is assured. The plan should take the following considerations into account:

1. Features of the facility that may impose limitations during construction. For example, certain tasks might need to be performed during non-peak operating hours.

2. To maintain continuous operation and monitoring, provisions might need to be made for temporary parallel equipment. For example, if an older model PLC is being replaced, it might need to continue operating while the new PLC is installed and wired.

3. PCS upgrades typically require re-wiring of equipment that results in a temporary loss of use of the equipment. The transition plan needs to account for operational requirements while scheduling equipment down-time. The Operation Group will provide the Contractor with their operational constraints as required.

4. If PCS networking configuration changes are involved, the Contractor should consider the impact on the ability of the Operation Group to control and monitor related equipment.

Consultant should review the transition plan prior submitting to City for approval.

5.7 Equipment Installation and Wiring

Once equipment has been approved at the FAT and the Transition Plan has been accepted, the Contractor can deliver equipment to site and commence installation. Prior starting field wiring of the equipment, instrumenatation and control pannels contractor shall prepare Cable Block Diagrams as outlined in 4.4 Detaild Design.

5.8 Pre-Start Health and Safety If a Pre-Start Health and Safety review and report are required (refer to the Toronto Water Project Delivery System Manual for details), the Consultant shall produce the report and have it approved prior to the commencement of commissioning.




5-24 Dec 2015

5.9 Entity Information Lists The Contractor shall populate with manufacturer's data and maintenance recommendations the Entity Information Lists (WMS list) initially developed by Consultant for all new and upgraded equipment in the project. See Equipment and Data Tagging Standard (Appendix D) for the template. This information is used by the OMU for WMS purposes.




6-25 Dec 2015

6. Construction - Software

6.1 General In general, Construction – Software tasks are performed by the Systems Integrator and supervised by the Consultant. See Appendix A – Flowcharts for a concise depiction of tasks and deliverables required during this phase.

Consultants will comply with Appendix A.6 SERVICES DURING CONSTRUCTION of the RFP document, specifically with respect to the PCS system.

As the City’s representative during construction, the Consultant will review all deliverables from the Contractor and System Integrator and provide their comments to the City.

6.2 Flow Chart Development The Systems Integrator shall develop logic flow charts to demonstrate their interpretation of the design documents. Refer to RPU Software Programming (Appendix C) for more detail on the development of flow charts.

6.3 Software Modules The City has developed a series of standard software modules that are to be used by programmers to implement the control functions required by the project. The goal of standard software modules is to reduce development and maintenance costs by ensuring that software deployed throughout Toronto Water facilities has a common look and logical base. Refer to Standard Software Modules (Appendix C) for more detail on the use of software modules.

In some cases, the Systems Integrator may find that a new or modified software module would be beneficial to the development of the software for the project. Modules cannot be modified without the consent of PCSU. When the PCSU approves the development or modification of a software module, the Systems Integrator shall follow the procedure found in Standard Software Modules (Appendix C).

6.4 Software Development Once it has been determined that the software modules are sufficient for the project, the Systems Integrator can begin software development according to the following Appendix C guidelines:

1. Process Display Programming

2. Operator Interface Programming

3. Alarming

4. Colour Convention




6-26 Dec 2015

5. RPU Software Programming

6. Standard Software Modules

Software is to be submitted at the 70% stage at which time the Consultant and City representatives will review the components for accuracy, adherence to standards, and compatibility with the rest of the facility PCS.

6.5 FAT Plan Prior to carrying out a Factory Acceptance Test of the software, the Systems Integrator shall prepare a detailed test plan for review by the Consultant. The test plan is to broaden the FAT Check Sheet and Process Logic Test Sheet developed by Consultant in the Design Stage. The test plan will identify all field I/O to be tested such as equipment status, control modes, and hardwired alarms. Also virtual points such as alarms (including priority and conditioning), setpoints, and operator entered parameters. The test plan will then identify automatic logic tests designed to prove that the program responds as detailed in the Process Control Narrative. The plan will also identify a “graphics review” as well as include the PCN and the contract drawings (control schematics, loop diagrams, and process and instrumentation drawings – P&IDs) as part of the test plan. The Systems Integrator shall demonstrate that the test plan fulfils the intent and requirements of the PCN and will therefore result in the successful operation of the system when installed on site.

The test plan should also include a proposed schedule and a description of the proposed testing environment (hardware setup, software utilized) for approval by the Consultant and the City. Refer to Factory Acceptance Testing (Appendix C) for details. Once the schedule and documentation have been accepted, the Systems Integrator shall submit a copy of all software components to the City (known as the “Pre-FAT” version of software).

6.6 Software FAT The Systems Integrator will host the Factory Acceptance Test according to the details presented in the schedule and FAT documentation. Refer to Factory Acceptance Testing (Appendix C) for details. Upon completion of the FAT and subsequent corrections and re-testing as required, the Systems Integrator shall submit a copy of all software components to the City (known as the “Pre-SAT” version of software).




7-27 Dec 2015

7. Construction – Testing and Commissioning

7.1 General The Consultant shall comply with Appendix A7 SITE SERVICES DURING TESTING AND COMMISSIONING, of the RFP document for the engineering services required to be provided for the project.

The Consultant shall specify in the contract document that the Contractor and Systems Integrator are required to comply with the City’s standard procedure for the testing and commissioning of PCS.

As the City’s representative during construction, the Consultant will review all deliverables from the Contractor and System Integrator providing comments to the City.

7.2 Hardware SAT and Training Plan The Contractor is to submit a SAT Plan that includes the following:

1. Schedule

2. Testing procedure for each item

3. Sign-off documentation

4. Details of City involvement, including any operational requirements such as shutdowns, communication interruptions, etc.

Refer to Instrument and Equipment Testing and Site Acceptance Testing (Appendix C) for more details.

The Training Plan should contain a schedule and detailed outline of the material to be covered. Refer to Training (Appendix C) for more details.

7.3 Hardware Training The Contractor shall perform training on the installed hardware prior to the SAT. Refer to Training (Appendix C) for more details.

7.4 Hardware SAT A Hardware SAT is to ensure the integrity of the equipment used to control and monitor the process at the City’s facilities once installed on site. Prior to the hardware SAT, the Consultant and Contractor must have jointly completed all I/O tests, loop tests, network tests, and instrumentation calibration verification sheets.




7-28 Dec 2015

The hardware SAT involves the following major components:

1. Control Panels & Local Operator Interfaces

2. Networking Equipment (as available)

3. Workstations

4. PLCs

5. Instrumentation

The hardware SAT is performed on site to ensure that the equipment has been installed wired and configured correctly. The consultant shall compile all the SAT results and submit it to the City for their review.

The testing of the networking equipment, workstations, and PLCs is intended to confirm that the network as designed, and the configuration of the hardware as specified functions as an integral network on site and in conjunction with the City’s wide area network (WAN).

7.5 Software SAT and Training Plan The Systems Integrator’s SAT Plan should include the same I/O and Logic check sheets that were used during the Software FAT. In addition to check sheets, there should also be sign-off documentation and a schedule of activities that details the City’s involvement, including any operational requirements such as shutdowns, communication interruptions, etc. Refer to Site Acceptance Testing and Commissioning (Appendix C) for more details.

The Training Plan should contain a schedule and detailed outline of the material to be covered. Refer to Training (Appendix C) for more details.

7.6 Software Training The Systems Integrator shall perform training on the new software components prior to the SAT. Refer to Training (Appendix C) for more details.

7.7 Software SAT After training has been completed, the Software SAT can be performed. It is intended to confirm that the software functions according to the Process Control Narrative and allow fine-tuning of control loops and other process variables. Refer to Site Acceptance Testing and Commissioning (Appendix C) for more details.

7.8 Operational Test/System Performance Test The operational test/system performance is a 5-day test (unless otherwise defined in RFP) of the system to simulate the operation of the system under different loading conditions. The test shall start on a Monday and will be restarted again on a Monday in the event of a failure of the system to operate as intended at any point in the 5-day period. During this period the software is to




7-29 Dec 2015

operate under Area Operator station and Central Operator station modes to simulate normal operation of the system. Where necessary, the Consultants will specify additional simulation logic to the RPU to allow the process area to be fully simulated for operational test/system performance. The provision of such simulation code is deemed to be within the scope of the Contractor services. Where necessary, the Consultant shall specify the provision of temporary piping and equipment in order to be able to carry out the simulation successfully.

7.9 Tag Lists and PCS I/O List Consultant is to finalize Tag Lists and PCS I/O list identifying all changes made throughout construction and commissioning for inclusion into the ETMS and WMS.

7.10 As-Built Documentation The Contractor and Systems Integrator shall submit As-Built documentation during this phase. Refer the PCS Documentation (Appendix C) for details. Consultant is also to submit As-Built documentation integrating all changes into documentation prepared in the Design phase of the Project.

7.11 Post Construction Warranty Period In general, the Systems Integrator shall provide all necessary services during the warranty period to update all software when deficiencies are found. Refer to the contract for specific warranty requirements.




Appendix A-1

Dec, 2015

Appendix A – Project Tasks Flowcharts




Appendix B-1

Dec, 2015

Appendix B – Project Tasks Implementation Checklists




Appendix C-1 Dec, 2015

Appendix C – Associated Guidelines The following list shows related Guideline documents for specific topics that are complementary to this document.

Document Name Drawing # Field Verification Procedure

Field Verification Log

Process Control Narrative

P&ID Standard Symbols and Practices

P&ID Standard Symbols and Practices Attachments P&ID LEGEND XXXX-P&ID-I-0101 P&ID STANDARD SYMBOLS -1 XXXX-P&ID-I-0102 P&ID STANDARD SYMBOLS -2 XXXX-P&ID-I-0103 P&ID Blocks - Gates, Valves, Pumps P&ID Block 1 P&ID Blocks - Blower, Fan, Damper P&ID Block 2 P&ID Blocks - Vortex, Chamber P&ID Block 3 P&ID Blocks - Bridge, Collector P&ID Block 4 P&ID Blocks - Centrifuge P&ID Block 5 P&ID Blocks - Generator, Communitor P&ID Block 6 P&ID Blocks - Instrumentation P&ID Block 7 Colour Convention

RPU Software Programming

Standard Software Modules

Operator Interface Programming

Process Display Programming

Alarming

Instrument and Equipment Testing

Instrument and Equipment Testing Attachments Instrument Testing Log

Field Installation Testing Log

SCADA Factory Acceptance Testing

SCADA Factory Acceptance Testing Attachments Factory Acceptance Test and Site Acceptance Test Check Sheet

Process Logic Test Sheet

SCADA Site Acceptance Testing and Commissioning

SCADA Factory Acceptance Testing Attachments Factory Acceptance Test and Site Acceptance Test Check Sheet

Process Logic Test Sheet

PCS Documentation Training




Appendix D-1

Dec, 2015

Appendix D – Associated Standards and Installation Drawings List The following list shows PCS Standards and Installation Drawings that will be made available to Consultant on the request.

SPECIFICATION # DWG. # DESCRIPTION

DIVISION 13 - PROCESS CONTROL

13000 PROCESS CONTROL

13010 Process Control - General

13040 SPECIALITIES

13040 Equipment and Data Tagging

WMS Entity Information Spread Sheet

Equipment (Asset) Tag List – Aluminum (Example)

Equipment (Asset) Tag List – Lamacoid (Example) Lamacoid Supplemental Tag List – MCC Starter Disconnect (Example)

Lamacoid Supplemental Tag List – Source of Power (Example)

Lamacoid Supplemental Tag List – Control Station (Example)

13100 INSTRUMENTATION STANDARDS

13100 Instrumentation Design

13105 General Instrumentation Requirements

13110 ANALYSIS INSTRUMENTS

13110.1 Particle Analyzer

13110.2 Turbidity Analyzer - Low Range

13110.3 Turbidity Analyzer - High Range

13110.4 Suspended Solids Meter - Insertion Type

13110.5 Suspended Solids Meter

13110.6 Sludge Density Meter, In-Line

13110.7 Sludge Density Meter, Ultrasonic

13111 Chlorine Residual Analyzer

13113 pH Analyzer

13115 Conductivity Analyzer

13116 Dissolved Oxygen Analyzer

13118 Fluoride Analyzer

13120 Streaming Current Analyzer




Appendix D-2

Dec, 2015


13121 Phosphate Analyzer

13122 Ammonia Analyzer

13125.1 Chlorine Leak and Sulphur Dioxide Monitor

13125.2 Ozone Gas Leak Detector

13125.3 Combustible Gas Detector

13125.5 Hydrogen Sulphide Monitor

13125.6 Oxygen Monitor

13125.7 Stack Gas Monitor

13125.8 Gas Detector

13125.9 Ozone Concentration Transmitter, Wet Gas

13126.1 Ozone-In-Oxygen Monitor - Low Range

13126.2 Ozone-In-Oxygen Monitor - Medium Range

13126.3 Ozone-In-Oxygen Monitor - High Range

13130 FLOW INSTRUMENTS

13130 Magnetic Flow Meter

13131 Vortex Shedding Flow Meter

13132.1 Clamp-on Ultrasonic (Doppler) Flow Meter

13132.2 Clamp-on Ultrasonic (Transit Time) Flow Meter

13133 Insertion Ultrasonic (Transit Time) Flow Meter

13134 Thermal Mass Flow Meter

13136 Coriolis Mass Flow and Density Meter

13137.1 Orifice Plate

13137.2 Pitot Tube

13137.3 Venturi

13137.4 Parshall Flume

13137.5 Flow Broad Crested Weir

13138.1 Paddle Wheel Flow Switch

13138.2 Thermal Flow Switch

13142 Open Channel Flow Meter - Submersible

13143 Open Channel Flow Meter - Radar

13150 LEVEL INSTRUMENTS

13150.1 Ultrasonic Level Transmitter

13150.3 Radar Level Transmitter - Horn Antenna

13150.4 Radar Level Transmitter- Rod Antenna

13152 Capacitance Level Transmitter

13153.1 Level-Direct Sensing DPT (Level), Flange Mounted

13153.2 Level-Submersible DPT

13157.1 Sludge Blanket Detector, Fixed




Appendix D-3

Dec, 2015


13158.1 Float Switch (Tilt)

13158.2 Ultrasonic Level Switch

13158.3 Capacitance Level Switch

13158.4 Vibration Level Switch

13158.5 Conductivity Level Switch

13160 PRESSURE INSTRUMENTS

13160 Pressure Transmitter

13161 Pressure Differential Transmitter

13166 Pressure Seal

13167 Annular Pressure Seal

13168 Pressure Switches

13169 Pressure Indicating Gauge

13170 TEMPERATURE INSTRUMENTS

13170.1 Temperature Element and Transmitter, RTD

13170.2 Temperature Element and Transmitter, Thermocouple

13171.1 Ambient Air Temperature and Humidity Transmitter

13171.2 Duct Air Temperature and Humidity Transmitter

13171.3 Ambient Air Humidity Transmitter

13171.4 Duct Air Humidity Transmitter

13176 Thermowell

13177 Temperature Switches

13178 Temperature Indicators

13180 MISCELLANEOUS INSTRUMENTS

13180 Sampler

13183 Limit Switch

13184 Motion Detector

13187 Weight Scale Hydraulic Weight Cell

13188 Weigh Scale Load Cell

13190 Smoke Detector

13191 Heat Detector

13199 Instrument Listing / Instrument Data Sheets

13300 CONTROL PANEL STANDARDS

13300 Control Panel Design

13305 Field Wiring

13310 Panel Construction

13311 Enclosures




Appendix D-4

Dec, 2015


13312 Enclosure Accessories

13320 Panel Wiring

13325 DC Power Supply

13340 Panel Services

13350 Selector Switches, Push-Buttons, and Status Lights

13351 Annunciator

13352 Single Loop Controller

13353 Dual Loop Controller

13354 LCD Digital Panel Indicator

13354.1 LED Digital Panel Indicator

13355 Paperless Chart Recorder

13360 ELECTRICAL MONITORING AND PROTECTION

13361 Power Monitor Unit

13366.1 Motor Protection Unit (469)

13367 Generator Management Relay (489)

13368 Feeder Protection Unit (750)

13369 Transformer Protection Unit (735)

13369.1 Transformer Differential Protection Unit (745)

13370 SIGNAL CONDITIONING EQUIPMENT

13370 Signal Conditioning Equipment

13371 Power Monitoring Serial to Ethernet Conversion Unit

13372 Power Monitoring Information and Relay Configuration Tool

13400 PROGRAMABLE LOGIC CONTROLLERS

13400 Programmable Logic Controllers

13500 NETWORKING

13510 Local Area Network

13520 Wide Area Network

13600 COMPUTER HARDWARE

13600 SCADA Computer System

Appendix D1: Installation Drawings

General for Instruments and Panels

G01 Instrument Stand, floor mount

G02 Instrument Wall Mounting, Pipe

G05 Instrument Sun Shield Installation Detail




Appendix D-5

Dec, 2015


G06 Instrument Purge Air

Analysis Instruments

A02 pH Sensor - In-Line Mount

A03 pH Sensor - Y Mount

A06.2 DO Probe, Hand-Rail Mount

A14.1 Suspended Solids Meter (Low Range)

A14.2 Suspended Solids Meter (Higher Concentration of Solids)

A15.1 Suspended Solids Meter - In-line

A15.2 Suspended Solids Meter – Pipe Tee Insertion

A32 Gas Detection - Conduit Mounted Sensor

A35 Chlorine Leak Sensor

Flow Instruments

F01.2 Flow - Magnetic Flow Meter (With Ultrasonic Cleaning Electrodes)

F01.3 Flow - Magnetic Flow Meter (Remote Mounted Signal Converter)

F04.1 Flow Switch (Paddle Wheel) Pipe Mounting

F05.1 Flow Switch (Thermal) Duct Mounting. Air

F07 Self Averaging Pitot, Standard

F08 Self Averaging Pitot, Hot Tap

F09 Self Averaging Pitot, Flanged

F10 Ventury Tube

F35 Parshall Flume Ultrasonic Sensor Mounting Detail

Level Instruments

L02 Ultrasonic Level, Through Concrete

L11 Ultrasonic Level, Enclosed Tank

L12.1 Radar Level, Horn Antenna, Enclosed Tank

L12.2 Radar Level, Horn Antenna, Grit Hopper/Tank

L12.3 Radar Level, Horn Antenna, Enclosed Tank Flange Mounted

L12.4 Radar Level, Horn Antenna, Open Tank, Side Mounted

L12.5 Radar Level, Horn Antenna, Scum Hopper/Tank

L12.6 Radar Level, Horn Antenna, Enclosed Tank, Floor Mounted

L13 Radar Level Transmitter - Rod

L20 Level Probe In Side Of Tank

L25 Float Switch for Sumps

L25.1 Float Switch for Sumps, Multi Level Regulator Hanger

L37 Weir –Ultrasonic Level Sensor Mounting Detail

Pressure Instruments

P01 Pressure Tap - Pipe Tee and Threadolet

P02 Pressure Tap - Tank (FRP and Steel)

P03 Pressure Tap - Pipe Saddle




Appendix D-6

Dec, 2015


P12 DPT For Flow In Overhead Process Line

P14 DPT For Flow In Lower Process Line

P15 DPT For Steam Flow

P16 DPT For Level Of Vented Tank

P18 Pressure - DPT For Filter Head Loss

P18.1 Differential Pressure Transmitter

P22 PS and PI, normal

P23 PS and PI, with diaphragm seal

P24 PS and PI, with annular diaphragm seal

Temperature Instruments

T01 Thermowells Installation

T02 Thermowells Installation

DIVISION 15 MECHANICAL

15000 MECHANICAL DESIGN STANDARDS

15110 Valves and Operators

DIVISION 16 ELECTRICAL

16000 ELECTRICAL DESIGN STANDARDS

16020 Electrical Control Schematic Diagrams

1.01 Electrical Symbols

2.01A Constant Speed Computer - Maintained, Local -Pushbuttons

2.01B Constant Speed Computer - Momentary, Local -Pushbuttons

2.01C Reversing: Computer - Maintained, Local - Pushbuttons

2.01D Reversing: Computer - Momentary, Local - Pushbuttons

2.02A Two Speed: Computer-Maintained, Local - Push-buttons

2.02B Two Speed: Computer - Momentary, Local - Push-buttons

2.03A Variable Speed Magnetic Drive: Speed - 4-20 mA

2.04A Full Open/Close Valve or Gate: Computer - Momentary, Local - Pushbuttons

2.05A Slow Moving Valve or Gate: Computer - Maintained, Local - Selector Switch

2.05B Slow Moving Valve or Gate: Computer - Momentary, Local - Pushbuttons

2.06A Modulating Valve or Gate: Computer - 4-20 mA, Local - Setpoint

2.06B Modulating Valve or Gate: Computer - Maintained, Local - Pushbuttons

16280 Uninterruptible Power Supplies and Power Conditioners




Appendix D-7

Dec, 2015


16281 Computer Room, Uninterruptible Power Supply

Process Control System (PCS) Implementation Guidelines · programming. As custodian of PLC software...

Documents

Transcript of Process Control System (PCS) Implementation Guidelines · programming. As custodian of PLC software...