Mission Support Alliance - Hanford Site · Mission Support Alliance Page 4 of 15 4.3.4 Certificate of Conformance The Supplier shall provide a legible/reproducible Certification of

Mission Support Alliance

Page 1 of 15

Statement of Work

Title: Project L-801- Replace the Electrical Utilities SCADA System

Revision Number: Rev 0

Date: May 13, 2017

1.0 INTRODUCTION / BACKGROUND

The Supervisory Control and Data Acquisition (SCADA) system is used to gather information for process control and real time data of the Hanford Electrical Power Transmission and Distribution (T&D) system. Data is gathered from several different Intelligent Electronic

Devices (IED) located at the substations. The data is fed into the remote terminal units (RTU), also located at the substations, and then travels thru the SCADA Local Area Network (SLAN) into the master server computers, which are centrally located in the Dispatch Center at Substation #2. The data is processed by the SCADA software loaded on the servers before

presenting it in a timely manner to various operator (Dispatch) and view only (Engineering) workstations.

The SCADA system records and logs all events. If conditions become hazardous, the system sounds warning alarms to alert Operations personnel. The SCADA system control functions

include remote operation of high voltage substation breakers, as well as motor operated disconnects located in the substation yard. These functions allow for safe, fast, and remote operation of equipment that would otherwise place workers in a hazardous Arc Flash boundary.

The goal is to investigate options and replace the current vendor unsupported version of the

Electrical Utilities (EU) SCADA system.

2.0 OBJECTIVE

The goal of this subcontract is to obtain a definitive design and cost estimate, including a detailed list of components, for acquisition and installation of the best available technology

replacement for EU’s SCADA system.

3.0 DESCRIPTION OF WORK – SPECIFIC

The Subcontractor shall produce a design, meeting the requirements as defined in section 4.0 of

this SOW. Included with the final definitive design will be a project cost estimate for acquisition and installation of the replacement SCADA system.

This SOW will provide the definitive design and list of components needed to replace the existing SCADA system by customizing commercial-off-the shelf (COTS) to meet the

requirements as defined in section 4.0 of this SOW.

The design will detail the replacement of the following sub-systems, which comprise the complete SCADA system:


Page 2 of 15

SCADA software package (Including adding a Geographical Information System (GIS) module).

SCADA hardware (Remote Terminal Units (RTU), Logger Printer, and computer hardware if necessary).

SCADA Alarm Notification System (auto-dialer).

Dispatcher MIMIC board Lamp Driver system, located in the Dispatch Center.

4.0 REQUIREMENTS

4.1 Engineering Requirements

MSA-specific Engineering Standards applicable to the work are listed here and can be provided after award:

MSC-STD-ENG-097, MSC Engineering Design Codes, Standards and Site Specific Design

Parameters; and

HNF-14660, Offsite Vendor Instructions for Preparation and Control of Engineering Drawings.

4.2 Environment, Safety, & Health (ES&H) Requirements

The Subcontractor shall exercise a degree of care commensurate with the work and the associated hazards. The Subcontractor shall ensure that management of safety and environmental functions and activities is an integral and visible part of the Subcontractor’s work planning and execution processes. The Subcontractor shall flow down safety and environmental

requirements to the lowest tier Subcontractor performing work on the Hanford site commensurate with the risk and complexity of the work.

Prior to the subcontractor coming out to preform work, the subcontractor and MSA need to develop a Job Hazard Analysis Plan together. Subcontractors and its lower-tier subcontractors

shall be responsible to complete an Employee Job Task Analysis (EJTA) in accordance with MSC-PRO-11058 for any of the following situations:

For any subcontractor employee who will be on the Hanford Site for more than 30 days in a year.

For any subcontractor employee who may potentially be exposed to hazards (e.g. radiological, beryllium, hazardous wastes, noise) while performing in accordance with the subcontract statement of work.


Page 3 of 15

For any subcontractor employee enrolled in a medical or exposure monitoring program required by 10 CFR 851, and/or any other applicable federal, state or local regulation or other obligation.

If any of the above conditions are met, the subcontractor and its lower-tier subcontractor employee(s) is (are) to have a current approved EJTA prior to the employee(s) beginning work

on the Hanford Site.

Buyer’s Safety and Health Procedures are available on the internet at http://www.hanford.gov/pmm/page.cfm/Construction. The documents on this site are kept current and are available for Subcontractors and lower-tier Subcontractor use.

4.3 QUALITY ASSURANCE (QA) REQUIREMENTS

4.3.1 QA Standards

The work activities for this statement of work shall be performed in accordance with a NQA-1-2008 with 2009 Addenda QA Program or an equivalent ISO-9001 Program for the definitive

design of the SCADA System.

The QA Program and Implementing procedures shall be sent to the Buyer for review and approval. If an ISO-9001 program it used, current copy of ISO certificate shall also be submitted for review and approval.

Subsequent to the definitive design the vendor shall also describe in detail what life-cycle processes and/or procedures will be utilized for the development of the COTS Software life-cycle documentation.

4.3.2 Commercial Off-The-Shelf Software

The Subcontractor shall submit documentation for all engineering analysis/design, data analysis/reduction, and engineering/environmental modeling COTS software1 (application) used in the performance of work activities. Documentation shall be provided even if the applications are verified through manual verification/independent calculations and/or analyses.

4.3.3 Quality Assurance and Engineering Oversight

Subcontractor activities are subject to QA and Engineering oversight by the Buyer’s quality assurance or engineering representative at the Subcontractor’s' facility or the Subcontractor lower-tier’s service provider(s).

1 COTS software refers to an existing application which will be implemented on a standard operating system without

the need for modification of its executable/object code.

http://www.hanford.gov/pmm/page.cfm/Construction


Page 4 of 15

4.3.4 Certificate of Conformance

The Supplier shall provide a legible/reproducible Certification of Conformance. Supplier’s authorized representative responsible for quality shall sign the Certification of Conformance.

This Certification of Conformance shall, as a minimum:

1. Identify the appropriate Purchase Order/Contract Order number under which the material,

equipment, item or service is being supplied.

2. Description of the software definitive design

3. C of C shall be unique to the 100% definitive design

4. Item shipped shall be identified on the C of C.

5. The COC shall identify the specific procurement requirements to be met by the purchased item or service. The procurement requirements identified shall include any approved changes, waivers, or deviations applicable to the item or service.

6. The COC shall also identify any procurement document requirements that have not been

met together with an explanation and the means for resolving the non-conformances.

7. The COC shall be signed or otherwise authenticated by a supplier’s representative. The person signing the COC shall be the one who is responsible for this QA function and whose responsibilities and position are described in the supplier’s QA program.

4.4 DESIGN REQUIREMENTS

The new SCADA system shall meet the following design requirements upon completion of definitive design:

4.4.1 The SCADA system shall allow a minimum of 10 software installations, with the

capability to expand either with a network key or individual licensing.

4.4.2 Available to run 24 hours a day, 365 days a year and alarm operations of critical alarms.

4.4.3 Includes a server failover backup system.

4.4.4 Allow installation of software and operating system updates in the backup and test systems without affecting the production system.

4.4.5 Include a test system that mimics the production system and is capable of testing new equipment and system patches prior to their installation in the production system.


Page 5 of 15

4.4.6 At a minimum, include the following applications/modules: running log of events and alarms, trending/graphing, a database manager, and creating customizable and interactive display screens. See Figure 4 1 for an example customized SCADA display screen.

4.4.7 Capable of communication via fiber optic (DNP3 over IP).

4.4.8 Capable of alerting Operations during off-shift hours of select SCADA alarm points via telephone.

4.4.9 The Dispatcher MIMIC board breaker indication lights will function to display the state of the breaker using the colors “Red” for Closed, “Green” for Open, and

“Yellow” for Unknown.

4.4.10 A log that is continuously printed in hardcopy at the Dispatch Center.

4.4.11 Select indication points will allow for “Sequence of Event” (SOE) time-stamping.

4.4.12 A Geographical Information System (GIS) based on-screen model of the SCADA

controlled electrical utility and key components.

4.4.13 The SCADA software and hardware will be able to accept an IRIG-B signal for GPS time stamping using a BNC connection.

4.4.14 The SCADA software and hardware will be able to manage and display the data

points listed in Table 4 1 with the capability for future expansion of all types of points:

4.4.15 The system is able to support an anti-malware application

4.4.16 The system is able to log system and application activates such as success/failures of

who, what, when, where

4.4.17 The application is able to establish least privilege concept through role-based (e.g. dispatcher, administrator, engineer) commensurate with accessing logs

4.4.18 The application is able to uniquely authorize and authenticate users

4.4.19 The use of web-based connections is capable of transmitting via HTTPS

4.4.20 The use of file transfers is conducted via SFTP


Page 6 of 15

Figure -1. SCADA Display Example


Page 7 of 15

Table -1. SCADA Points List (by Substation)

Substation Point Type Number of Points

Substation # 1

Indication¹ 111 (Form A)

Control² 13

Analog³ 36 (0-1 mA)

Pulse Accumulator⁴ 22 (Form C)

Pseudo Analog⁵ 2

Substation # 2 (location of Dispatch Center)

Indication¹ 133 (Form A) Control² 37

Analog³ 51 (0-1 mA)

Pulse Accumulator⁴ 24 (Form C)

Pseudo Analog⁵ 4

Substation # 3 Indication¹ 172 (Form A)

Control² 17

Analog³ 30 (DNP 3) Pulse Accumulator⁴ 12 (DNP 3)

Pseudo Analog⁵ 15

Substation # 4 Indication¹ 36 (Form A)

Control² N/A

Analog³ 57 (DNP 3)

Pulse Accumulator⁴ N/A

Pseudo Analog⁵ N/A ¹Indication: a 2 (Form A Contact) or 3 (Form C Contact) status indication contact.

²Control: 2 (Form C Contact) usually for opening or closing Breakers, Switches, or Motor Operated Disconnects.

³Analog: 0-1 mA input signal usually from a transducer. Or digital (DNP 3) as a slave device to the RTU. ⁴Pulse Accumulator: a 2 (Form A Contact) or 3 (Form C Contact) status indication contact

⁵Pseudo Analog: Calculated from an algebraic expression using real Analog inputs in the SCADA software.

5.0 PERSONNEL REQUIREMENTS

5.1 TRAINING

All personnel performing work on this task shall have the necessary training for access to the

Hanford site and systems in accordance with this section. In addition to the Document Management Control System Overview already provided to Seller personnel, the training required to support this design effort is listed below.

HGET and MGET training will be required for the subcontractor(s) where personnel will be

visiting the site for meetings or facility tours. For vendors working strictly offsite – engineering analysis documents – Hanford Site Orientation (HSO) training may be used as an alternate. Computer Based Training may be coordinated through Vivid Learning Systems, 372-0335.


Page 8 of 15

Table 1. TRAINING REQUIREMENTS

Course Number Description

000001 HGET – Computer-Based Training (CBT)

110001 MSA General Employee Training (MGET) - CBT

5.2 Qualifications

Subcontractor personnel performing engineering services shall have appropriate training,

experience, qualification and/or certification(s) to perform the work required by this task. Design documents submitted for acceptance by MSA shall be approved/stamped by the Subcontractor’s Washington State licensed Professional Engineer (PE). Security and Badging Requirements

Subcontractor employees will be required to submit to vehicle searches and not personally carry or transport prohibited articles.

5.3 Security and Badging Requirements

For any on site work, see Special Provisions – On Site Services for details.

Subcontractor employees will be required to submit to vehicle searches and not personally carry or transport certain prohibited articles.

5.3.1 Work Location/Potential Access Requirements

Work locations and work shifts will depend on the subcontractors need for equipment walk

downs. Most work will be performed offsite at the subcontractor’s facility

5.3.2 Site Access and Work Hours

Hanford personnel at the Hanford Site work a standard 4/10 schedule. The standard work week consist of ten (10) hours of work between 6:00 am and 4:30 pm, with one-half hour designated as

an unpaid period for lunch, Monday through Thursday.

Work performed outside normal operating hours shall be coordinated and/or approved through the BTR and/or the Contract Specialist prior to performing the work.

6.0 MEETINGS

The general purpose of meetings is for the coordination, control, and direction of the Work. In addition to meetings addressed by this Section, Subcontractor may be required by other Sections and other Subcontract documents to conduct special-purpose meetings and various safety meetings and briefings.


Page 9 of 15

MSA will issue meeting notices and prepare an agenda and minutes for each meeting addressed in this Section. When applicable, minutes will identify action items, assigned actionees, and due dates.

KICKOFF MEETING - Before start of the Work, MSA will conduct a conference at a

time and Hanford Site location agreed to by Subcontractor and MSA. Invited attendees will include MSA, Subcontractor, key lower tier subcontractors and others having an interest in the Work. Purpose of the conference is the coordination of Work start up and familiarization of project participants with the Work and worksite.

PROGRESS MEETINGS - MSA will conduct progress meetings at time and Hanford Site location determined by MSA. Invited attendees will include MSA, Subcontractor and key subcontractors. The purpose of the meetings is the exchange of Work-related information.

Subcontractor shall participate in all meetings as required by the Buyer’s Technical Representative (BTR).

7.0 DELIVERABLES AND PERFORMANCE SCHEDULE REQUIREMENTS

7.1 Deliverables

Subcontract work products and services shall meet applicable standards as referenced above. Design documents submitted for acceptance by MSA shall be approved/stamped by the Subcontractor’s Washington State licensed Professional Engineer (PE).

Native files shall be provided as noted in the Master Submittal Register or as requested by the

Buyer at any point in the design process. At the Buyer’s discretion, design submittals that are not accepted may only require resubmittal of the Comment Response Form with acceptable comment dispositions to be incorporated into subsequent design submittals.

7.2 Schedule

Start Date: Within (2) Seller work days of award

Milestone #1 – Approval of Submittals 1-4 (SD+14)

Milestone #2 – Approval of Submittal 5 (SD+35)

Milestone #3 – Approval of Submittal 6 (SD+63)

Milestone #4 – Approval of Submittals 7 & 8 (SD+77)


Page 10 of 15

8.0 SPECIAL REQUIREMENTS

Communication with Hanford Site Regulatory Agencies

Under no circumstances shall the subcontractor interact directly with regulatory agencies prior to notifying and obtaining the concurrence of the Contract Specialist and the Buyer’s Technical Representative.

8.1 CONFIGURATION MANAGEMENT REQUIREMENTS

8.1.1 Design Team Task Lead Expectations

A single point of contact shall be established to fulfill the role of Task Lead (e.g., the Subcontractor’s project manager) for this task release.

8.1.2 Design Process

The subcontractor shall develop design content in accordance with their internal, qualified engineering processes.

8.1.3 Design Interfaces

Design interfaces, where present, shall be identified, documented, and controlled in a specification or on an MSA drawing and be uniquely identified.

8.1.4 Documentation

Work produced as part of this SOW and subsequent task releases shall be documented and meet

the requirements and MSA Standards listed in Section 7.7.

8.1.5 Design Reviews

Each design product shall be checked, reviewed and approved internally by the Subcontractor prior to providing the design package to MSA for review, comment, and subsequent approval.

The design review activities will be performed and documented in accordance with Section 11.

8.1.6 As-Built Process

There are no As-Built requirements associate with this scope of work.

8.2 Submittals

All deliverables associated with this task release have been identified in Appendix A of this task release. See the Attachment A--Submittal Register for details related to submittal format, type, review cycles, and etc.


Page 11 of 15

The design media expectations provided for each phase shall be, but not limited to, the following:

EJTA if required

Training Records

Commercial-off-the-shelf Software documentation for the SCADA application software.

Commercial-off-the-shelf Hardware documentation.

30% Conceptual Design: Preliminary design portion from the Subcontractor. This

includes a parts list, software list, and user documentation for both hardware and software.

90% Definitive Design: Completed design of the field connection points to the new hardware, including construction detail drawings, specifications, and layout. Any long

lead construction material is to be identified at this time. Early procurement activities to support the overall project schedule can also be started if required at this time. Drawings to be provided in AutoCAD format.

100% Final Design: Design media is anticipated to be ready for approval and release for

acquisition and installation.

Cost estimate: List of hardware and software required to implement the design along with a cost for each item.

Submittals shall be provided to MSA Document Control using the MSA Contractor Document Submittal form (A-6003-061). All submittals must be peer reviewed/quality checked to ensure completeness and accuracy prior to submittal.

Requests for Clarification/Information may be provided to MSA Document Control using

Request for Clarification or Information form (A-6003-063)


Page 12 of 15

APPENDIX A SUBMITTAL REGISTER

Submittal Register Definitions

1. Numerical submittal sequence number: Example: 1, 2, 3, 4 (or organized by topics and project assigned coding structure).

2. Number of Copies and electronic and/or hard copy: Example: E (Electronic only), 6 (Six Hard Copies), or Hard, 1: E, 1 (One Hard Copy, and Electronic).

3. Format: Describes the type of submittal required:

DWG An AutoCAD drawing using the Hanford standard formatting

(See HNF-14660, Off-Site Subcontractor Directions for the Preparation and Control of Engineering Drawings).

MFC Microsoft Format Compatible application (Word, Excel, Access, PowerPoint)

P3 A Primavera Project Planner schedule GEN General or Open Format/Media PDF Adobe Acrobat (Portable Document Format)

4. Submittal Type:

APW = Approval Required Prior to Work (Buyer must approve the Subcontractor’s submittal prior to the Subcontractor being authorized to proceed with any activity/work associated with the submittal).

AP = Approval Required (Buyer must approve the Subcontractor’s submittal,

however, work associated with the submittal may proceed prior to Buyer approval).

FIO = For Information Only (the submittal is not subject to review and/or approval).

5. Vendor Information: Mark Yes if document(s) are VI, otherwise leave blank.

6. Description / Document Title: Title or general description of the document.

7. Submittal Date: Actual date or number of Calendar Days before or after a milestone that a submittal is due from the Subcontractor: Example: June 1, 2005 or CD + 60 [60 days

after Conceptual Design Complete]

http://www.hanford.gov/pmm/page.cfm/CAD


Page 13 of 15

A Date of Award CD Conceptual Design Complete PD Preliminary Design Complete FD Final Design Complete M Mobilization

SC Start of Construction EC End of Construction

8. Buyer Review Time (Work Days): Example: 3 Days

9. Subcontract Reference: Cross reference to the Subcontract requirement that defines this

submittal: Example: SOW 3.2. 10. Reviewers: List of reviewers for each submittal. Listing is not provided on SOW copy

provided for proposals


Page 14 of 15

Submittal Register:

The Subcontractor shall meet the required schedule and provide the documents specified in accordance with the following

submittals.

Subcontract Number and Name: Project L-801- Replace the Electrical Utilities SCADA System

Revision: 0

1. No.

2. No. of

Copies*

(See End Note)

3. Format

4. Type

5. Vendor

Information

– Mark Yes if VI,

Otherwise Leave Blank

6. Description / Document Title

7. Submittal

Date

(Calendar Days)

8. Buyer

Review

Time (Work

Days)

9. Subcontract Paragraph or

Requirement Reference

10. Reviewers

1 1 MFC or

PDF APW

Employee Job Task Analyses (EJTA), as appropriate, or a document that supports why no

EJTA is needed.

SD+7 4

SOW 4.0

2 1 MFC or

PDF APW

Subcontractor personnel training qualifications/documentation

SD+7 4

SOW 4.0

3 1 MFC or

PDF AP YES Commercial-off-the-shelf Software documentation

SD+7 4

4.1.1 of SOW

4 1 MFC or

PDF AP YES

Commercial-off-the-shelf Hardware documentation

SD+7 4

4.1.1 of SOW

5 1 MFC or

PDF APW 30% Conceptual Design SD+21 8

4.1.1 of SOW

6 1 MFC or

PDF APW 90% Definitive Design

SD+49 8

4.1.1 of SOW

7 1 MCC or

PDF APW

Copy of QA Program and Implementing procedures (If ISO copy of current certificate)

5 4.3.1

8 1 MCC or

PDF AP

Vendor shall describe in detail what life-cycle processes or procedures will be utilized for the development of the COTS of the Shelf Software.

5 4.3.1

9 1 MFC or APW 100 % Final Design SD+70 4 4.1.1 of SOW


Page 15 of 15

Subcontract Number and Name: Project L-801- Replace the Electrical Utilities SCADA System

Revision: 0

1. No.

2. No. of

Copies* (See End

Note)

3. Format

4. Type

5. Vendor

Information – Mark Yes

if VI,

Otherwise Leave Blank

6. Description / Document Title

7. Submittal

Date (Calendar

Days)

8. Buyer

Review Time

(Work

Days)

9. Subcontract

Paragraph or Requirement

Reference

10. Reviewers

PDF

10 1 MFC or

PDF APW Cost estimate

SD+70 4

4.1.1 of SOW

*For electronic submittals, the number of hard copies can be negotiated with the Contract Specialist and approved by the BTR

Mission Support Alliance - Hanford Site · Mission Support Alliance Page 4 of 15 4.3.4 Certificate of Conformance The Supplier shall provide a legible/reproducible Certification of

Documents