DRAFT SOW_ICS Upgrade_1.docx

Statement of Work

Industrial Control System Upgrade

1.0 GENERAL

The Colorado River Agency, Electrical Services (CRA-ES) operates and manages the Headgate Rock Dam (HGRD) in Parker, Arizona. The existing Industrial Control System (ICS) at HGRD has reached its end-of-life and requires upgrade. Within the past several years the HGRD has experienced loss of generation due to failures with ICS relay, server, computer, and control systems.

CRA-ES requires a new turnkey ICS system to manage and control river operations, electrical power generation, debris removal, climate control, supervisory control and data acquisition, alarm notification, and reporting. The new ICS will also be required to reduce the overall size of the existing Balance of Plant Control Center.

Where all possible all software and hardware shall be Open Standard, Scalable and new Commercial Off the Shelf (COTS) products. If custom/proprietary products are suggested or required, justification shall be submitted to the Contracting Officer (CO). Acceptance shall be required from the CO prior to any design or implementation. The finalized ICS Solution shall have a maintenance/service agreement that covers all hardware/software.

2.0 BACKGROUND

Owned and operated by the Bureau of Indian Affairs (BIA), the Headgate Rock Dam and Hydro Electric Generation Station (HGR-GS) is located on the lower Colorado River, about 15 miles downstream of Parker Dam near the town of Parker, Arizona. The dam, which impounds a body of water known as Lake Moovalya, has 10 radial gates. Radial gates #1-7 act as spillway gates and pass Colorado River flow without generating any power. Radial gates #8-10 sit immediately upstream from the power plant’s three hydroelectric generation units.

The hydroelectric power plant was retrofitted to the Head Gate Rock Dam (HGRD) circa 1992. It was designed as a low head, axial flow turbine powering the generation units to nearly 19.5 Mega Watt (MW) of power serving the Colorado River Indian Tribes (CRIT) Reservation. Somewhat rare, the hydroelectric generation units are installed horizontally because of the low head design. The turbines are manufactured by Voight and the generation units are manufactured by Villares.

The current ICS for HGRD controls the water levels of Moovalya Lake and the Colorado River. A water flow schedule is set by the Bureau of Reclamations (BOR); the water flow schedule allows HGRD to operate as a run of the river hydroelectric generation station. The existing ICS at HGRD was initially installed in 1994 and completed installation was finalized in 2002. The existing ICS for HRGD is controlled and monitored via RTU’s, Allen Bradley PLC’s, and associated IED’s from Woodward, ABB, etc. HGRD still incorporates many antiquated electro mechanical contactor relays. The existing ICS for HGRD is islanded except for the single output to the Bureau of Reclamations Hoover Dam Operations Center. HGRD has an existing agreement with Hoover Dam for off-hour monitoring. Alarms and generator status are sent over an encrypted serial link to Hoover’s iFix system.

HGRD is comprised of;

· Three (3) 6.5 MVA (Mega Volt Amps) Generators

· Three (3) Kaplan Turbines

· Three (3) Governor Units

· Three (3) Static Excitation Systems

· Three (3) 7.5 MVA 4.16 / 69 kV (kilo Volts) Transformers

· Seven (7) Spillway Gates

· Three (3) Intake Radial Gates

· One (1) Irrigation Canal Gate

3.0 OBJECTIVE

This Design-Build (D-B) Contract will cover the planning, design, engineering, research, integration, build, installation and test, and certifying, documentation preparation of all items and tasks identified in this SOW. The end product delivered shall be a new turnkey ICS at HGRD.

4.0 SCOPE

4.1 The only approved external communication from and to HGRD shall come from the already existing connection to Hoover Dam.

4.1.1 Any and all external communications, except for the existing connection to Hoover Dam, shall require written approval from the Contracting Officer and the Regional IT Manager.

4.1.2 Intent is to limit external communications to and from HGRD to the bare minimum required for proper plant operations, testing and maintenance.

4.2 The new ICS solution shall not connect to the Department of the Interior (DOI) Indian Affairs (IA) network by any means. The ICS solution shall be a standalone system that is independent of all DOI networks.

4.3 Contractor shall provide a turnkey ICS solution that is safe, scalable, robust, manageable, double modular redundant voting control, cost effective and retains all the same functionality of the existing HGRD ICS system while also upgrading and or replacing with new modern equipment current RTU’s at both HGRD and Headgate Rock Substation, Excitation System, Excitation Power Transformers, Governor Control System, trash rake control, servers, controls, balance of plant control center (BPCC), Master Control Center, climate control and monitoring, metering, relays, monitoring devices, emergency personnel call-outs, reports, and operations.

4.4 A fully functional and complete system satisfying the intent of the listed specifications shall be provided even if all components are not specifically called out. Provide all necessary materials and labor for a complete and functioning system satisfying the intent of the specifications, even if all components are not specifically called out.

4.5 Where all possible all software / hardware shall be Open Standard, Scalable and new Commercial Off the Shelf (COTS) products. If custom/proprietary products are suggested or required, justification shall be submitted to the CO. Acceptance shall be required from the CO prior to any design or implementation.

4.5.1 The Contractor shall deliver software that is vendor supported and not end-of-life.

4.5.2 The Contractor shall harden any computer systems by removing or disabling any software components that are not required for system operation and/or maintenance. If components cannot be removed or disabled, the Contractor shall document specific technical justification and provide risk mitigation recommendations. Components to be removed and/or disabled shall include, but not be limited to:

· Games

· Device drivers for product components not procured/delivered

· Messaging services (e.g., email, instant messenger, peer-to-peer file sharing)

· Source code

· Software compilers in user workstations and servers

· Software compilers for unused programming languages

· Unused administrative utilities, diagnostics, network management, and system management functions

· Backups of files, databases, and programs used only during system development

4.5.3 The Contractor shall provide documentation of all software/firmware and identify versions, revisions, and/or patch levels, as delivered.

4.5.4 The Contractor shall provide a list of all ports and authorized services required for normal operation, emergency operation, or troubleshooting.

4.5.5 The Contractor shall disable all services and ports that are not required for normal operation, emergency operations, or troubleshooting.

4.5.6 The Contractor shall provide documentation of disabled ports, connectors, and interfaces.

4.5.7 The Contractor shall disclose the existence of all known methods for bypassing computer authentication in the procured product, often referred to as backdoors, and provide written documentation that all such backdoors created by the Contractor have been permanently removed from the system.

4.5.8 The Contractor shall provide summary documentation of the security features and instructions on product maintenance, support, and reconfiguration of default settings.

4.6 The finalized ICS solution shall have a maintenance/service agreement that covers all hardware/software for the terms specified in section 5.8.2.

4.7 As a requirement for the Process Control System (PCS), preferences are for a process automation system; one that combines the best attributes of pure Distributed Control System (DCS), such as the graphical capabilities, control algorithms and single object oriented database, but also the scalability, distributed I/O and sequencing speed advantages of a controller. A non-DCS based system is not acceptable.

4.8 The control system shall consist of centralized controller modules and decentralized input and output modules.

4.9 The system shall be scalable, to cover all possible applications from single user system (single station) to distributed client server architectures. Servers for operation can be redundant to offer a high availability.

4.10 The system shall be flexible and sustainable, enabling the user to expand an existing installation by a simple license upgrade.

4.11 The system will support a wide range of controllers thus enabling selection from smaller controller for simple applications to high end redundant controller for complex and critical applications. It must be possible to use all these controllers simultaneously in an application.

4.12 Control of any part of the ICS systems shall be prohibited while offsite of Government property.

4.12.1 Notification of alarms and or messages may be sent through text message and or voice messaging to phone numbers designated by CRA-ES.

4.13 Provide system monitoring and reporting to CRA-ES main office.

4.13.1 System monitoring and reporting to CRA-ES main office shall meet or exceed standards and requirements set forth by North American Electric Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) Plan (see section 4.14).

4.14 Cybersecurity is paramount. The ICS system provided must be capable of facilitating compliance with applicable published standards:

· Achilles Level 2 Certification IEC 62443 for monitoring and controlled access

· Federal Information Security Management Act (FISMA)

· DOI Security Control Standard for Contingency Planning, version 1.3

· NIST SP 800-53

· NIST SP 800-37

4.14.1 HGRD’s gross plant/facility aggregate nameplate rating is less than 75 MVA.

4.14.2 HGRD’s Gross individual nameplate rating is less than 20 MVA.

4.14.3 HGRD’s Transformers primary terminal operate at less than 100 kV.

4.14.4 HGRD does not have Blackstart Resources.

4.14.5 HGRD is excluded from NERC Bulk Electric System (BES). As such HGRD has No impact of the NERC BES. Only applicable CIP standards will be required and implemented.

4.15 CRA-ES has the goal of reducing the size of the current Balance of Plant Control Center (BPCC) to a more compact package. The current BPCC is thirty six feet in length by eight foot high. The objective is to relocate all required controls, meters, and HMI’s to a more compact so as to free up room and provide secure access to the BPCC.

4.16 CRA-ES has the goal of increasing the operation output of the existing Villares generators from 7.5 Mega Watts (MW) to 10 MW’s per unit. The Contractor will option a package to exam the existing water flows, turbine and generator configurations, health/status of the turbines and generators. After examination if the current system configuration is found capable of increased MW output then the new ICS system shall be designed and configured to meet the new MW output. If optioned contractor will also be responsible for completing all documentation verifying the MW increase and preform an Arc Flash Hazard Analysis and labeling so as to identify the new hazards with the MW increase and properly configure all relays, breakers and safety settings.

5.0 REQUIREMENTS AND TASKS

In order to support CRA-ES’s mission and ICS system upgrade requirements, the Government requires technical design, analysis, professional installation and testing of the system identified under this SOW. The following section of the SOW describe the requirements and tasks that shall be completed by the Contractor.

5.1 REQUIREMENTS

The Contractor shall be directly responsible for ensuring the accuracy, timeliness and completion of tasks assigned under this contract.

The Contractor shall provide all Personnel, Supervision, Mobilization, Tools, Equipment, Vehicles, Materials, Supplies, Lodging, Travel, Meals and other direct cost to accomplish all tasks identified in this SOW.

At the contractor’s expense, repairs made due to any damage to existing installations due to the contractor’s operations or the contractor’s failure to provide proper protection shall be completed by the Contactor. Any repairs completed shall be accepted by the government prior to completion.

The contractor is responsible for removal and disposal of equipment and waste products produced under this SOW

The Contractor shall create a schedule notating periods where water flows and power generation will be impacted and notify CRA-ES personnel 90 days before impact.

Government Furnished Facilities at HGRD

· Electrical Power – Existing single phase, 60 Hz, 120/240 VAC

· Water

5.1.1 With the Contractors proposal the Contractor shall demonstrate three (3) successfully completed projects similar in scope or project type. Corporate experience shall be submitted in tabular form identifying,

· Project Customer

· Project Number

· Project Name

· Site Location

· Summary of Scope (200 Words or Less)

5.1.2 With the Contractors proposal the Contractor shall demonstrate through resume both the Contractor’s Project Manager (PM) and Contractor supplied SME’s experience as related to this project’s scope. Resumes shall be submitted in tabular form identifying most current five (5) years’ experience. Resumes shall include,

· Yes/No Check Box, Identifying Person as Key Personnel

· Name

· Project Role

· Company Job Title

· Company Affiliation

· Company Address

· Contact Phone Number

· Contact Email

· Professional Qualification/Certifications

· Work Experience

· Company Name

· Project Role

· Company Position

· Year

5.1.2.1 The Contractor’s Project Manager (PM) shall have at minimum 5 years’ experience performing project management duties as related to,

· Planning

· Team Leadership

· Execution

· Time Management

· Budget Management

· Documentation

· Creation

· Submission

· Project Maintenance and Recovery

5.1.2.2 The Contractor’s supplied SME’s shall demonstrate at minimum 5 years’ experience as related to their assigned roll on this project.

5.1.3 Included in the Contractors proposal the Contractor shall provide a tabular list of proposed devices, items, hardware, and services to be provided to successfully complete each task identified in this SOW.

· The list provided does not have to be a comprehensive list detailing every aspect or product to be utilized but should contain all major components and services to complete each task identified in this SOW. The tabular lists will provide a clear understanding of the products and services to be provided and a clear understanding of how the Contractor plans to meet the objects stated in this SOW.

· Tabular which details products, and or components list shall contain the following,

· Manufacturer

· Model Number

· Quantity

· Description (200 Words or Less)

· Justification for Use (200 Words or Less)

· URL Link to Manufacture webpage detailing specifications and product info

· Optionally or if Manufactures’ webpage is unavailable the Contractor may submit with the proposal product cutsheets, diagrams, and product information.

· If no URL link is available or the Contractor chooses to optionally provide product cutsheets, diagrams, and product information with their proposal. Under the URL Link column in the products table the Contractor shall note where the information is located in their proposal.

· Tabular which details of services to be provided shall contain the following,

· Title Service to be Provided

· Description of the Service (200 Words or Less)

5.2 SPECIFIC TASKS

The contractor shall provide all the services, products and personnel needed to upgrade the ICS system at HGRD. These services will require interaction with Government staff to collect/gather the required information to perform the ICS upgrade. Additional interaction and coordination with Government staff will be required so to as properly coordinate equipment de-energization and Lock-Out-Tag-Out procedures.

The contractor shall provide management and technical services within the scope of this contract to support the following tasks.

Design-Build Tasks:

Table 1 - Task

5.2 Project Management:

Work efforts performed in support of this SOW shall require management expertise, oversight, control, communications, time management, quality assurance and quality control and management, procedure development, risk management, configuration management, cost management, and system implementation. Using state-of-the-art knowledge, skills, tools, and techniques, the contractor shall:

5.2.1.1 Assemble and identify a project lead to coordinate with CRA-ES personnel on matters pertaining to the contract.

5.2.1.1.1 The project lead shall develop a schedule with both short term, overall goals and deadlines to represent any and all essential features of the project.

5.2.1.1.1.1 The schedule shall be presented as a MS Project file and MS Excel Spreadsheet, denoting critical path, milestones and critical elements to the Contracting Officer (CO) and Contract Officers Representative (COR) upon request.

5.2.1.1.2 During the initial information gathering the project the project lead shall schedule, with the COR, a meeting to update status, guide, and evaluate the performance of the contractor and matters pertaining to the contract.

5.2.1.1.3 During the implementation and deployment phase of the project the project lead shall schedule, with the COR, a meeting or more often as required to update status, coordinate outages, and evaluate the performance of the contractor and matters pertaining to the contract.

5.2.1.2 Contractor shall provide an effective labor and skill mix to accomplish all tasks identified in this SOW.

5.2.1.2.1 Effectively address changes in work priorities and staffing and notify the CO and COR accordingly.

5.2.1.2.2 Ensure proper staffing and skill set coverage at all times.

5.2.1.2.3 Ensure deliverable quality and timeliness.

5.2.1.2.4 Provide informational, technical, and management briefings and presentations to COR, Contracting Officer Technical Representative (COTR) and to other technical staff as requested by COR on all aspects of the work being performed and devices being installed and configured.

5.2.2 Kickoff Meeting

The Contractor shall prepare and present as part of the bid package a Project Management Plan describing the technical approach, organizational resources and management controls to be employed to meet the cost, performance and schedule requirements for this effort. The Project Management Plan shall detail the products, methods for developing the products, allocation of staff and other resources necessary to produce the products and a revised timeline for producing the products, if necessary. The CO and COR shall receive the revised Project Management Plan in both hard copy and electronic form, Microsoft Word. Based on the Project Management Plan, the CO will provide approval to move forward on activities planned. The Contractor shall request prior approval on all activities not included in the plan or any modification to the plan after approval has been given (draft due with proposal/final due 10 days after award).

5.2.3 Design Meetings

The stages of design review shall be 10%, 30%, 60%, 90%, 100%. Contractor shall be responsible taking meeting minutes for all phases of the Design Meetings. Meeting minutes shall be submitted to both the CO and the COR in electronic form, Microsoft Word.

5.2.3.1 10% Design Meeting (Conceptual Design)

At the 10% design level the design will show a conceptual design toward a coordinated plan set which includes a preliminary list of technical specifications and preliminary equipment list. Review the design package to assess the basic design concepts and how it meets the project objectives, design assumptions and suitability of information available. If the design team determines that the design does not meet the objectives or solve the problem, it is appropriate for the project manager, CO and COR to discuss identified issues and redraft the conceptual design. At this phase of the project all deliverables will be submitted as soft MS Word and or Adobe .pdf documents for review.

10% Design Deliverables:

· D-B process

· Discovery Results

· ICS Overview

· Conceptual/Functional Design

· Process Flow

· Points of Failure

· Preliminary Schematic Drawings

· Site Plan

· Floor Plans

· Mechanical Drawings

· Electrical Drawings

· Security Drawings

· Instrumentation and Control Drawings

· Technical Specifications

· Data Model

· Cybersecurity Overview

· Process Flow

· Hardened Devices

· Software

· Security Policies

· Network Security

· Access

· Firewalls

· Controlled Access Overview

5.2.3.2 Design Meetings - 30% Design Meeting (Preliminary Design) The 30% design plans are a compilation of plan sheets that explain the major elements of the project to understand how the design will meet the project objectives. At this phase of the project all deliverables will be submitted as soft MS Word and or Adobe .pdf documents for review.

30% Design Deliverables:

· Design Technical Memo

· Summarize technical criteria and assumptions used for the accepted design presented at the 10% Design Meeting. Include an evaluation of safety considerations for equipment access and facility access.

· General Drawings

· Drawing Index that reflects the drawings anticipated for the project

· General Symbols, Legends, and abbreviations that allow for verification of data presented in drawings

· Design Data and Criteria

· Basis of Design Plan Sheet

· Civil/Site Work Drawings

· Site Plan

· Structural Drawings

· Floor Plans

· Mechanical Drawings

· Electrical Drawings

· Bill of Material

· Security Drawings

· Identify Security and Communication items and locations

· Instrumentation and Control Drawings

· Technical Specifications

· Draft copies of specifications or cut sheets of major elements

· Preliminary Equipment List

· Data Dictionary (Logical)

· Relationship Diagram

· Cybersecurity

· Process Flow

· Auditing

· Continuous Monitoring

· Hardened Devices

· Software

· Security Policies

· Network Security

· Access

· Firewalls

· Controlled Access Plans

· Identified Major Conflicts

5.2.3.3 Design Meetings - 60% Design Meeting (Preliminary Design) The 60% design plans are a substantially developed project design that includes a plan and profile view of all major facilities. This design plan will begin looking like a final design package. All design features will be identified and located. Cross sections are shown at critical locations. Major conflicts shall be resolved before 60% design submission. Any minor conflicts must be identified during this phase. At this phase of the project all deliverables will be submitted as soft MS Word and or Adobe .pdf documents for review.

60% Design Deliverables:

· General Drawings

· Drawing Index that reflects the drawings anticipated for the project

· General Symbols, Legends, and abbreviations that allow for verification of data presented in drawings

· Design Data and Criteria

· Basis of Design Plan Sheet

· Civil/Site Work Drawings

· Site Plan

· Structural Drawings

· Floor Plans

· Mechanical Drawings

· Electrical Drawings

· Bill of Material

· Security Drawings

· Identify Security and Communication items and locations

· Instrumentation and Control Drawings

· Technical Specifications

· Draft copies of specifications or cut sheets of major elements

· Preliminary Equipment List

· Data Dictionary (Logical)

· Data Dictionary (Physical)

· Database Schema

· Cybersecurity

· Process Flow

· Auditing

· Continuous Monitoring

· Hardened Devices

· Software

· Security Policies

· Network Security

· Access

· Firewalls

· Controlled Access Plans

· Identified Minor Conflicts

5.2.3.4 Design Meetings - 90% Design Meeting (Final Design)

The 90% submittal shall reflect review comments from the 60% submittal along with subsequent meetings and design decisions, including a control strategy and commissioning requirements. Minor conflicts shall be resolved before 90% design submission. The submittal shall reflect coordination between all design disciplines and be free from typographical, formatting, labeling, and other errors that would lead to misinterpretation of the design documents. Submittal will reflect coordination between all design disciplines and will require only detailed level corrections. At this phase of the project all deliverables will be submitted as soft MS Word and or Adobe .pdf documents for review.

90% Design Deliverables:

· General Drawings

· Drawing Index that reflects the drawings anticipated for the project

· General Symbols, Legends, and abbreviations that allow for verification of data presented in drawings

· Design Data and Criteria

· Basis of Design Plan Sheet

· Civil/Site Work Drawings

· Site Plan

· Structural Drawings

· Floor Plans

· Mechanical Drawings

· Electrical Drawings

· Bill of Material

· Security Drawings

· Identify Security and Communication items and locations

· Instrumentation and Control Drawings

· Technical Specifications

· Draft copies of specifications or cut sheets of major elements

· Preliminary Equipment List

· Data Model

· Data Schema

· Data Dictionary (Logical)

· Data Dictionary (Physical)

· Relationship Diagram

· Cybersecurity

· Process Flow

· Auditing

· Continuous Monitoring

· Hardened Devices

· Software

· Security Policies

· Network Security

· Access

· Firewalls

· Controlled Access Plans

· Contingency Plan

5.2.3.5 Design Meetings - 100% Design Meeting (Final Design)

The drawings, including details and specifications, are complete. The 100% submittal shall reflect review comments from the 90% submittal along with subsequent meetings and design decisions, including a control strategy and commissioning requirements. All conflicts shall be resolved before 100% design submission. The submittal shall reflect coordination between all design disciplines and be free from typographical, formatting, labeling, and other errors that would lead to misinterpretation of the design documents. This submittal shall reflect coordination between all design disciplines. At this phase of the project all deliverables will be submitted as both hard and soft copies. All soft copies shall be submitted as either MS Word, Adobe .pdf, AutoCad .dwg. All Drawings and Bill of Materials shall be submitted as .dwg file types. One (1) complete hard copy submittal package shall be delivered to CRA-ES and one (1) complete soft copy submittal package shall be delivered to the Contracting Officer.

100% Design Deliverables:

· General Drawings

· Drawing Index that reflects the drawings anticipated for the project

· General Symbols, Legends, and abbreviations that allow for verification of data presented in drawings

· Design Data and Criteria

· Basis of Design Plan Sheet

· Civil/Site Work Drawings

· Site Plan

· Structural Drawings

· Floor Plans

· Mechanical Drawings

· Electrical Drawings

· Bill of Material

· Security Drawings

· Identify Security and Communication items and locations

· Instrumentation and Control Drawings

· Technical Specifications

· Draft copies of specifications or cut sheets of major elements

· Preliminary Equipment List

· Data Model

· Data Schema

· Data Dictionary (Logical)

· Data Dictionary (Physical)

· Relationship Diagram

· Cybersecurity

· Process Flow

· Auditing

· Continuous Monitoring

· Hardened Devices

· Software

· Security Policies

· Network Security

· Access

· Firewalls

· Controlled Access Plans

· Contingency Plan

5.2.4 Status Review Meetings

Status review meetings shall be held at minimum once per month. At minimum the status review meetings shall address;

· Task Updates

· Milestones

· Action Items

· Quality/Scope Updates

· Current Issues

· Anticipated Issues

· Next Steps

Contractor shall be responsible taking meeting minutes for all Status Review Meetings. Meeting minutes shall be submitted to both the CO and the COR in electronic form, Microsoft Word.

5.3 Configuration

5.3.1 PAC – Hybrid DCS

As a requirement for the Process Control System (PCS), preferences are for a process automation system; one that combines the best attributes of pure Distributed Control System (DCS), such as the graphical capabilities, control algorithms and single object oriented database, but also the scalability, distributed I/O and sequencing speed advantages of a controller. A non-DCS based system is not acceptable.

The control system shall consist of centralized controller modules and decentralized input and output modules.

The Contractor shall deliver software that is vendor supported and not end-of-life.

The system shall be scalable, to cover all possible applications from single user system (single station) to distributed client server architectures. Servers for operation can be redundant to offer a high availability.

The system shall be flexible and sustainable, enabling the user to expand an existing installation by a simple license upgrade.

The system will support a wide range of controllers thus enabling selection from smaller controller for simple applications to high end redundant controller for complex and critical applications. It must be possible to use all these controllers simultaneously in an application.

The operator interface shall employ native Client / Server architecture. The architecture shall promote the use of multiple server and multiple client configurations.

The system shall promote portability of applications between computers without any redevelopment or modification.

The system shall promote multi-platform along the lifecycle without modifications of the logical control projects.

The system shall support late binding or late mapping.

The system shall provide the ability to test and simulate the application without any reference to the hardware.

The system shall be based on multiple independent networks: As a minimum one for Control and one for Operation. Both networks will be based on Ethernet, as the most standard and used reference. In case of a small system, it shall be possible to merge them in one communication network.

The control network shall enable to welcome third party controllers in the PCS architecture.

The System Server hardware shall be based on standard commercial off-the-shelf hardware that can be purchased from any reputable computer manufacturer; System Servers shall use Long Term Service Channel (LTSC) to maximize the lifecycle of Windows 10.

System Servers perform centralized processing of the system information, including as a minimum, the following task:

· Centralized System Data Base including all Engineering data Operation Servers perform centralized processing of the system information, including as a minimum, the following tasks:

· Data Server to facilitate communications to the various controllers and devices in the system

· Alarm Server to enable the monitoring, alerting, distribution and acknowledgement of alarms

· Trend Server to enable the collection, storing and distribution of historical trends

· Report Server for processing, storing and distribution of reports

· It must be possible to combine all the task of System Server and Operation Servers onto a single workstation, or separate the functionality onto different workstations Additionally, each of the System/Operation Server tasks shall be capable of taking advantage of multi-CPU computers to load share across the CPUs and improve the overall performance of the system.

The Engineering and operator Workstation hardware shall be based on standard commercial off-the-shelf hardware that can be purchased from any reputable computer manufacturer; Engineering Workstations shall use most recent Windows Operating Systems Windows 10.

Operator workstation shall support:

· Screen resolution of up to 4000 x 4000 pixels.

· Multiple monitors on one workstation, with either multiple desktops or extended desktop.

It must be possible to add operating workstations while the system is running without affecting the running system.

Operator Workstations are connected to the Operation network and accessible to the Operation Server/s.

It must be possible to add engineering workstations while the system is running without affecting the running system.

Engineering workstations shall support multiple monitors on one workstation, with either multiple desktops or extended desktop.

Engineering Workstations are connected to the System Server. Operation network and Control network to download the projects on the Operation Servers / Clients and Controllers.

The servers are connected on both networks. They will acquire data on the Control network and distribute data to the Operator Interfaces on the Operation network.

5.3.1.1 Logging and Auditing

The Contractor shall implement audit logging or the ability to support the Government’s existing logging requirements. Logging capabilities provided by the Contractor shall be configurable by the Government and support the Government’s security auditing requirements. As specified by the Government, the procured product shall cover the following events, at a minimum (as appropriate to their function):

Successful and unsuccessful authentication and access attempts

· Account management changes

· Administrative/privileged account use

· Application start-up and shutdown

· Application failures

· Major application configuration changes

The Contractor shall implement the following minimum set of log data content.

· Time stamp

· Source address

· Destination address

· User/process identifier

· Event description

· Success/failure indications

· Filenames involved

The Contractor shall provide standard time synchronization in the procured product or an authoritative time source, and configure all system components to synchronize to the authoritative time source.

The Contractor shall provide confidentiality and integrity security protection of log files.

The Contractor shall implement an approach for collecting and storing (e.g., transfer or log forwarding) security log files.

The Contractor shall provide a list of all log management capabilities that the procured product is capable of generating and the format of those logs. This list shall identify which of those logs are enabled by default.

5.3.1.2 Control Network

The Contractor shall recommend guidance on the design and configuration of network security zones within the procured product.

The Contractor shall provide information on all communications (e.g., protocols) required between network security zones, whether inbound or outbound, and identify each network component of the procured product initiating communication.

The Contractor shall provide a method to restrict communication traffic between different network security zones. The Contractor shall provide documentation on any method or equipment used to restrict communication traffic.

The Contractor shall verify and document that disconnection points are established between the network security zones and provide the methods to isolate the zones to continue limited operations.

The Contractor shall provide a means to document that network traffic is monitored, filtered, and alarmed (e.g., alarms for unexpected traffic through network security zones) and provide filtering and monitoring rules.

If firewalls are provided by the Contractor, the Contractor shall provide documentation on the firewalls and their firewall rule sets for normal and emergency operations. The basis of the firewall rule sets shall be “deny all,” with exceptions explicitly identified by the Contractor.

If network switches are provided by the Contractor they must have the capability to configure, manage and monitor network traffic.

The Contractor shall provide the Government with access, including administrative as needed, to network components of the procured product, including firewalls.

The Contractor shall document all remote access entry pathways and ensure that they can be enabled or disabled by the Government as needed.

The Contractor shall verify that the procured product allows use of unique routable network address spaces (i.e., address spaces other than 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8 must be supported) that work within the Government’s network.

The Contractor shall not implement remote access capabilities into the system and/or network unless explicitly authorized by the Government.

The Contractor shall not implement connections to the Department of Interior network and/or the Internet unless explicitly authorized by the Government.

The Control network shall be an Ethernet network where all network resident devices will use TCP/IP based communications with a minimum bandwidth of 100Mbit/sec.

The control network Ethernet card shall be Achilles Level 2 compliant.

The system shall have the option to continuously monitor and control communications between the stations on the Control Network and shall have optional diagnostic capabilities with the ability to detect and identify causes and consequences of communications failures.

Failure events shall be reported to the operator via the Operator Station, and it shall be possible to repair/replace faulty sections of the Control Network without affecting the overall system operation.

It shall be possible to synchronize all the nodes across the entire control network to within +/- 10 milliseconds. IRIG-B will be required.

When the infrastructure requires Ethernet switches, theses switches must be provided as part of a standard product offering. These switches shall satisfy the following requirements:

· The Managed Ethernet Switches must be designed to operate in industrial environments with specifications and MTBF figures that are consistent with the rest of the system.

· The system must support a range of Managed Ethernet Switches that includes models that have 4 Ethernet ports up to models that include 24 Ethernet ports. The basic models of the Switches will support for communications over copper cable distance up to 100 meters.

· The range must include models that have Fiber Optic communication ports supporting Multimode fiber optic cable lengths up to 5000m for multi-mode or single mode fiber optic cables lengths up to 30,000m, for long distances and for use in high electrical noise environments.

· Faulty device replacement, with a centralized storage of the configuration and the ability to automatically restore the switch configuration.

· Capability for user to configure security (port security, SNMP security)

· Embedded diagnostics (i.e., hardware or port failures, communication errors)

5.3.1.3 Virtual Private Networks

The Contractor shall provide or utilize an existing security-isolated environment outside the control network (e.g., using a demilitarized zone [DMZ] or an equivalent or a superior form of security isolation) for the communications tunneling server to reside in.

The Contractor shall use different authentication credentials from those used for in- network communications when establishing control network access using communication tunneling.

The Contractor shall configure the communication tunneling components of the procured product (e.g., connectors, filters, and concentrators) to provide end-to-end encryption that is FIPS 140-2 compliant.

5.3.1.4 Networking Components

The Contractor shall provide a method for managing the network components of the procured product and changing configurations, including hardware and software configurations (e.g., addressing schemes).

The Contractor shall verify and provide documentation that the network configuration management interface is secured.

The Contractor shall provide Access Control Lists (ACLs) for monitoring network components (e.g., port mirroring and network tap) of the procured product.

5.3.1.5 Network Documentation

The Contractor shall provide a complete System Architecture Diagram to include all control system and maintenance components. The diagram must include labels of device type (e.g., workstation, server, PLC, etc.), manufacturer/model, operating system and version number.

The Contractor shall provide a complete Network Diagram that shows all of the devices on the control network that communicate via TCP/IP protocol. Any VLAN segregation of the devices must be indicated on the diagram.

The Contractor shall provide a Data Flow Diagram that indicates the normal system communications between devices on the network, including the ports and protocols utilized for communications.

The Contractor shall provide electronic versions of the network documentation in Microsoft Visio and PDF formats.

5.3.1.6 Configuration Management

The Contractor must provide a comprehensive inventory of all hardware (Servers, network devices, PLCs, RTUs, etc.) that includes the following minimum attributes.

· Manufacture

· Model Number

· Firmware Version Number (where applicable)

· Host Name (if applicable)

· Device description (if applicable)

· IP Address

· MAC Address

· Location

The Contractor must apply Security Technical Implementation Guides (STIGs) furnished by the Government.

The Contractor shall document specific technical justification and provide risk mitigation recommendations for STIG settings that cannot be applied due to technical infeasibility.

The Contractor shall implement the System Use Notification banner furnished by the Government on all technically feasible components.

The Contractor must provide the capability to create full and incremental backups of system components.

The Contractor must provide complete initial configuration backups of each component prior to final delivery, and the backups must be tested and verified as functional for restoring the system.

5.3.1.7 Malware Detection and Protection

The Contractor shall provide, or specify how to implement, the capability to automatically scan any removable media that is introduced to the product being acquired.

Provide a host-based malware detection capability that quarantines (instead of automatically deleting) suspected infected files.

The Contractor shall validate that cybersecurity services running on the procured product (e.g., virus checking and malware detection) do not conflict with other such services running on the procured product.

5.3.1.8 Wireless Technologies

Wireless technologies refer to any technology (e.g., radio, microwave, infrared, and ZigBee) that allows analog and digital communication without the use of wires.

The Contractor shall document specific protocols and other detailed information required for wireless devices to communicate with the control network, including other wireless equipment that can communicate with the Contractor-supplied devices.

The Contractor shall document use, capabilities, and limits for the wireless devices.

The Contractor shall coordinate through Indian Affairs the desired frequency band, document the operation of the wireless devices and verify that the communications meet the needs of the Government’s proposed deployment and reduce the possibility of signal interception and interference from outside the designated security perimeter.

The Contractor shall document the power and frequency requirements of the wireless devices (e.g., VHF, UHF, microwave and satellite devices meet the frequency requirements of the Radio Frequency Authorization assigned, and Generic Requirements [GR]-63 Network Equipment Building System [NEBS] and GR-1089).

The Contractor shall document that the wireless technology and associated devices comply with standard operational and security requirements specified in applicable wireless standard(s) or specification(s) (e.g., applicable IEEE standards, such as 802.11).

The Contractor shall demonstrate—through providing summary test data—that known attacks (e.g., those documented in the Common Attack Pattern Enumeration and Classification [CAPEC] list, such as malformed packet injection, man-in-the middle attacks, or denial-of-service attacks) do not cause the receiving wireless devices to crash, hang, be compromised, or otherwise malfunction.

The Contractor shall document the configuration control options that enable varying of the security level of the devices.

5.3.1.9 Controllers (General Requirements)

By design the controllers shall be capable of operating in a harsh industrial environment without special requirement for heating, cooling or electrical filtering. All components of the controllers shall be capable of continuous operation at least at ambient temperatures of 5-60°C and humidity of 5-95%. For more severe conditions that may lead to corrode the boards, conformal coating shall be available as part of the offer as an option.

Controllers shall have a maximum scan time of 150ms after configuration has been implemented; Controllers shall be able to perform high speed process control loops in no more than 10ms.

All modules, except processor (CPU) and single power supply module in the backplane, must be hot-swappable, i.e. they can be inserted and removed while powered up. This will not, under any circumstances, cause unpredictable behavior in the system.

The control program shall be safeguarded in non-volatile memory so that a power failure will not cause the program to be erased.

It must be possible to maintain the outputs or set them to fallback position when the controller switches to STOP mode via channel by channel parameter entry.

The controller shall support modules that have LEDs for module and channel diagnostics.

All Controllers shall support Modbus TCP/IP communications.

The controllers used in the PCS shall be able to control machines, so that these machines can be handled as part of the system (single database, diagnostic). Hence it is necessary to integrate a range of controllers with motion control modules as part of the PCS controllers.

Redundancy must be modular and based on two separate controllers on the same IO rack.

The controller must be Achilles Level II certified.

5.3.1.10 Controllers (Power Supply)

All controller hardware shall accept voltage fluctuations up to ±30% for short periods.

Power supplies shall meet IEEE472 surge withstand test requirements.

A redundant Power Supply functionality shall be available.

High Performance controllers shall support power supplies that can be summed together to increase rack capacity and availability; these power supply modules shall be hot swappable while the controller is online without disturbing the process.

5.3.1.11 Controllers…