Attachment 1 Performance Work Statement.pdf

Version 11/15/2022

PERFORMANCE WORK STATEMENT (PWS)

Supervisory Control and Data Acquisition (SCADA) System Maintenance Service

September 30, 2025

PART 1

GENERAL INFORMATION

General: This is a non-personnel services contract to provide Supervisory Control and Data Acquisition (SCADA) System Maintenance Service. The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform Supervisory Control and Data Acquisition (SCADA) System Maintenance Service as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background:

The Bureau of Engraving & Printing (BEP) is the largest producer of security documents in the United States. The BEP prints billions of Federal Reserve notes for delivery to the Federal

Reserve System each year. These notes are produced at the Bureau’s Washington, DC and Fort

Worth, Texas Facilities. In addition to U.S. currency, the BEP produces several other security documents such as portions of the U.S. Passports, materials for Homeland Security, military identification cards and Immigration and Naturalization certificates. The Bureau of Engraving and Printing’s (BEP’s) Washington DC facility (DCF) is comprised of various building systems and process control systems to fulfill their mission to print US currency. BEP process control systems utilize various types of programmable logic controllers (PLC’s), field instrumentation, digital controllers and relay logic controls. Building systems controllers include various types of direct digital control products, pneumatic controls and solid state electronic controls. The

Bureau CIO Directorate provides management support for all of the automated systems required to support the Bureau’s Facilities Management operations and the activities that support them.

These systems include enterprise-wide financial management, Facilities Management, and production support systems, as well as localized systems that relates to or support the Bureau’s operations. The SCADA system has been online since the third quarter of FY14. In addition, it has been expanded to WCF as one large system as the new software, AVEVA

Citect/AVEVA/Plant SCADA.AVEVA Citect Most process control and building control systems are integrated to AVEVA Citect. The BEP also uses Johnson Control Metasys® and Facility

Explorer and ABB PLC for HVAC systems. All HVAC controllers integrated to AVEVA Citect

SCADA®. The SCADA project included integrations of digital controllers, meters, PLC’s and

DDC components, IoT, any devices that the software’s drivers support. The SCADA project is dividual into two different virtual local area network (VLAN), Industrial control system and the servers/Clients. The recycling wiping solution and pretreating wastewater are on the Enterprise

Network as part of the AVEVA Citect SCADA® project with its own standalone hardware to continue to operate chemical plant during a crashing of the Enterprise Network or AVEVA

Citect SCADA servers.

In FY24, the AVEVA Citect SCADA was expanded to WCF to control all the process, HVAC, and all smart Utilities meters per president executive order.

1.3 Objectives:

The main objective of this PWS is to provide technical support and programming, the ability to troubleshoot difference Industrial Control System (ICS) devices via a support services, and the associated level of these services, to support the Bureau’s current and future use of SCADA provided equipment, associated IT infrastructure, and applications software.

The contractor will be responsible for providing specialists to perform work that:

supports the design, analysis, documentation, development, modification, testing, troubleshoot, installation, integration, implementation, and support of any existing and new SCADA equipment that associated IT systems, IT applications software and ICS.

These duties include the development and support of existing and new application software services in adherence with U.S. Government and Bureau IT standards and policies. The contractor will provide these services in accordance with what is described in this statement of work.

The BEP requires SCADA features to address increasing quality demands of a maturing facilities management modernization process, which include the following:

• Interface and support with transportation between the SCADA system with the Enterprise system using Matrikon OPC, ORB and ODBC for multiple

BEP system (Flowsys, Maximo, DMM)

• Provide interfaces to trend real-time data for industrial control systems and building automation systems while improve the SCADA infrastructure.

(Graphics, program, alarm, integration of BEP current existing system)

• Provide data archiving and reports for industrial control systems and building automation systems

• Modify system to keep pace with plant adaptations, modifications, and facility renovations

• Modify and develop SCADA graphic screens for industrial control systems and building automation systems

• Provide services to ensure SCADA system functionality to include operation, maintenance, training, and documentation.

These objectives are to provide the needed services to grow the BEP facilities management processes by leveraging existing facilities investments to reduce manual processes, increase efficiency, and provide/assist in all systems that consumes AVEVA Citect SCADA data on the Enterprise Service Bus (ESB) so invest consumer can use it to improve decision-making.

1.4 Scope

The scope of this contract is the maintenance of the SCADA system, ICS hardware and software associated with it. The SCADA system includes all applications included in

AVEVA Citect SCADA and AVEVA Citect Historian as well as communication components that are integrated to AVEVA Citect SCADA residing on the Server/Client

VLAN and ICS VLAN. The SCADA system shall also include all type of communicating devices list in the SCADA SSP, and AVEVA Citect SCADA ‘s communication drivers.

The SCADA system also includes any hardware and software used to communicate to any of the components of ESB (Maximo, Flowsys, DMM) residing on the DCF and WCF enterprise VLAN. This PWS will encompass patching, updates, design, build, test, document, training, troubleshooting, management and deployments to the SCADA system.

The contractor will provide resources with the requisite capabilities necessary to provide full system life cycle support to the SCADA system. At a minimum, contractor shall have two employees certified list in section 1.7.7. In performance of this effort, the contractor will be responsible for, but not limited to the following, providing all labor, travel, parts materials, transportation, equipment, tools, training, supplies, management and supervision and all other items and services necessary to perform these services in support of SCADA equipment (and underlying SCADA subsystems) located at both the

BEP’s DCF and WCF facilities.

The BEP will provide all IT Infrastructure hardware such as network devices, laptops, computers servers, and network drops. All software used by the contractor for work associated with SCADA will be approved for use by the BEP’s Office of Critical

Infrastructure and IT Security and Office of IT Operations. If contractor purchases software, license ownership will be transferred to the BEP. Standard COTS software applications and operating systems will be provided by the BEP.

1.4 GENERAL REQUIREMENTS

1.5.1 Non-disclosure agreement

1.5.1.1 Contractor will sign a non-disclosure agreement. The agreement will state information provided by the BEP to the Contractor is deemed proprietary and/or privileged information regarding the configuration of information technology (IT) systems and IT components, IT security practices and threat countermeasures, network layout and infrastructure, data received through

SCADA’s integration to DCF subsystems and the Bureau of Engraving and

Printing’s enterprise (BEN).

1.5.2 Personnel Security Considerations:

1.5.2.1 The position sensitivity of all positions occupied by Contractor and

Subcontractor employees performing under this contract are designated as 1)

High Risk, 2) Moderate Risk, and/or 3) Low Risk in accordance with the risk designation system OPM recommends for Public Trust Positions. The risk level is assigned based on the position’s potential for adverse impact on the efficiency of the agency. A High Risk level is defined as any position with the potential for exceptionally serious impact on the integrity and efficiency of the agency; Moderate Risk level is defined as a position with the potential for moderate to serious impact on the integrity and efficiency of the agency; and

Low Risk level is defined as a position that involves duties and responsibilities of limited potential for impact upon the integrity and efficiency of the agency.

1.5.2.1.1 Persons performing HIGH RISK direct or indirect information technology labor effort on this contract shall be U.S. Citizens. Naturalized citizens shall be considered the same as native-born U.S. citizens. HIGH RISK entails work such as a system administrator, database administrator, Control Engineer, network administrator or designs security models, application integration, customizes software or hardware, configures servers or networks, is able to manipulate alter or affect the integrity accessibility or availability of IT information or records.

1.5.2.1.2 Persons performing MODERATE RISK direct or indirect information technology labor effort on this contract shall be a US Citizen (Naturalized citizens shall be considered the same as native-born U.S. citizens) or lawful

Permanent resident alien with 3+ years of US Residency. MODERATE RISK entails work such as a programmer, system analyst, or user of a system containing financial, proprietary, or privacy/personally identifiable data.

1.5.2.1.3 Persons performing LOW RISK direct or indirect information technology labor effort on this contract shall be a US Citizen (Naturalized citizens shall be considered the same as native-born U.S. citizens) or lawful Permanent resident alien. LOW RISK entails work such as email or word processing from a user perspective, any trades that require installation of equipment such as control electrician, Control technician, Mechanical installation, Project

Manager and other personnel that needs building access ONLY.

1.5.2.1.4 Contractors working on SCADA system software applications will required

High Risk background investigation to perform any SCADA duties define in this SOW. Contractor require general building access for construction, field troubleshooting and verification will only require low risk background which will be determine by non-Network access during the badging process.

1.5.2.2 The contractor will follow BEP’s Office of Critical Infrastructure and IT

Security’s and Office of IT Operations’ protocol regarding IT security, network architecture, and fire wall structure. BEP will provide direction regarding VLAN and IP addressing.

1.5.3 Cyber Security

1.5.3.1 All Cyber security work will be done in conjunction with the BEP Office of

Critical Infrastructure and IT Security. The contractor will comply with all aspects of the BEP and the Department of the Treasury IT security program, and NIST FIPS and Special Publications. NIST documents and guidance are available at http://csrc.nist.gov/publications, Systems developed, delivered, or maintained by the contractor must meet the NIST FIPS 200 minimum security requirements.

1.5.3.1.1 United States Government Configuration Baseline (USGCB)

1.5.4 CONTRACT TRANSITION

1.5.4.1 The incumbent Contractor will cooperate fully to the extent required to permit an orderly changeover and maintain mission continuity. The incumbent contractor will furnish sufficient orientation, training, and equipment/systems familiarization required by any follow-on Contractor. All official files, manuals, charts, records, drawing, software development, source codes, deliverables, and other official documentation created or obtained during the performance of this SOW are the property of the Government and shall remain on site for use by the Government or follow-on Contractor at the time of this contract’s expiration, termination, or during any period of suspension.

1.5.5 Period of Performance The Contractor shall provide all personnel, equipment (except as otherwise provided), tools, materials, vehicle, supervision, and other items and services necessary services described.

http://csrc.nist.gov/publications

1.5.6 Period of Performance: The period of performance shall be for one (1) Base

Period and four (4) 12-month option years. The Period of Performance reads as follows:

Base Period 1 June 2026 thru September 29 2026 Option Period I 30 September 2026 thru September 29 2027 Option Year II 30 September 2027 thru September 29 2028 Option Year III 30 September 2028 thru September 29 2029 Option Year IV 30 September 2029 thru September 29 2030

1.6

1.7 General Information

1.7.1 Quality Control: Quality Control is the responsibility of the contractor. The contractor is responsible for the delivery of quality services/supplies to the Government.

The Contractor shall develop, implement and maintain a “how to document” or Standard Operation procedure of all processes integrated on the SCADA system and store it in the SCADA share folder per the direction of the COR/SME.

1.7.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is a Government only document primarily focused on what the Government must do to assure that the contractor has performed in accordance with the requirements of the contract.

1.7.4 Federal Government Holidays

New Year’s Day 1st day of January Martin Luther King Jr.'s Birthday 3rd Monday of January Presidents Day 3rd Monday of February Memorial Day Last Monday of May Juneteenth June 19th Independence Day 4th day of July Labor Day 1st Monday of September Columbus Day 2nd Monday of October Veterans Day 11th day of November Thanksgiving Day 4th Thursday of November Christmas Day 25th day of December The last week in December is the facility’s Year End Shutdown (YES).

In addition to the days designated as holidays, the Government Observes the following days:

• Any other day designated by Federal Statute

• Any other day designated by Executive Order

• Any other day designated by the President’s Proclamation

It is understood and agreed between the Government and the Contractor that observance of such days by Government personnel shall not otherwise be a reason for an additional period of performance, or entitlement of compensation. In the event the Contractor's personnel work during the holiday, they may be reimbursed by the Contractor, however, no form of holiday or other premium compensation will be reimbursed either as a direct or indirect cost, other than their normal compensation for the time worked.

1.7.5 Hours of Operation: The contractor is responsible for conducting business, between the hours of 06:00 to 18:00 Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Most work will occur during weekday dayshift with the exception of server loads, patches and updates which may occur off shift and / or on weekends. Annual operator training will include evening and midnight shifts. The contract shall coordinate with the government regarding hour of operation for BEP Year End Shut Down. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.7.6 Place of Performance: The contractor shall perform the services required at both facility locations and remotely in a hybrid work environment as agreed upon by the contractor and the Bureau. The hybrid work arrangement may involve a combination of on-site presence at the facility locations and remote work, subject to the terms and conditions detailed in the Bureau’s telework policies. The contractor shall ensure seamless communication, collaboration, and deliverance of services regardless of the work location, maintaining consistent productivity and quality standards for

• District of Columbia Facility (DCF), 14th and C streets SW, Washington, DC 20228.

• Western Currency Facility (WCF), 9000 Blue Mound Road, Fort Worth, Texas 76131

1.7.7 Type of Contract: The government will award a Time and Materials contract.

1.7.8 Security Requirements: Contractor personnel (to include subcontractors) performing work under this contract must have a high risk for network access(HPSD-12) and a low risk for non-network access(Proxy) personnel at time of the proposal submission, and must maintain the level of security required for the life of the contract.

1.7.8.1 Physical Security: The Contractor shall be responsible for safeguarding all government equipment, information and property provided for Contractor use under this Contract.

This Contract requires access into the Controlled Industrial Area of the BEP. The Contractor personnel shall recognize that BEP deals with sensitive information and other proprietary information, which are valuable, special, and unique assets. All information pertinent to BEP’s information technology resources is highly sensitive and may not be released to third parties without the express, written consent of BEP. This information requires strict control procedures to preclude unauthorized disclosure or dissemination.

Information pertinent to personnel is protected from unauthorized disclosure under the provisions of the Privacy Act of 1974 (5 U.S.C. 552a). Contractor personnel shall not divulge, disclose, or communicate in any manner, any information to any third party without prior written consent of the BEP. Contractor personnel shall protect information and treat it as strictly confidential and will abide by the security requirements of BEP. A violation of this paragraph shall be a material violation of this Contract. Should the Contractor receive or suspect they have learned of sensitive or classified information, the Contractor shall identify and report suspicions to the COR. Contractor personnel performing work under this Contract shall be subjects of background investigations, conducted by BEP’s Office of Personnel Security, prior to start of work under this Contract. Each Contractor employee performing under this Contract must successfully complete the Government required background check form at time of the proposal submission, and must maintain the level of security required for the life of the Contract.

1.7.7 Special Qualifications:

• AVEVA Citect SCADA Certified Expert (CSCE) – Minimum 5 years cetified

• Niagara 4 certification

• Facility Explorer® (FX) Supervisory Controllers o Engineering and Setup course #4701 o FX MSTP Field Controller Engineering course #4714.

o Installation of Facility Explorer Energy Management system

• Knowledgeable on PLC controller configuration, programming.

o Partnerships to existing PLC controller at BEP.

• At least 15 years of experience in installing control systems.

o Knowledge and experience in a computer programming language/DDC programming

• ABB Automation Technical Application Eng Support

• Has experiences in service contracts with large organization maintaining and upgrading

Facility Explorer, PLC, and Plant SCADA system manufactured by AVEVA

• A technical interview to demonstrate an ability writing control sequence and software for air handling units serving spaces that have tightly controlled temperature and humidity without reheat process.

• Experience in integrating Facility explorer, multiple bacnet/modbus and other complex communication to Plant AVEVA SCADA system.

1.7.8 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5, Post Award Orientation. The Contracting Officer, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the Contracting Officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government

1.7.9 Contracting Officer Representative (COR): The COR will be identified by separate letter by the CO. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, and specifications; monitor Contractor's performance and notify both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.7.10 Key Personnel: The follow personnel are considered key personnel by the government:

contract manager/Alternate contract manager, Engineer, Control Technician, Electrician, installation, anybody that require to complete the Major modification project per section

1.4.5. The contractor shall provide a contract manager and a leading engineer(SME) who shall be responsible for the performance of the work. The name of this person and an alternate(SME) who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The contract manager or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The contract manager or alternate(SME) shall be available between 08:00 to 17:00, Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. Qualifications for all key personnel are listed below:

• Engineer have a o Basic knowledge of computer’s OS o Ability to upgrade patch,hotfix, and install software or license software at application level, network understanding at network level and ICS communication level.

o Meet the qualification per 1.7.7 o All personnel who works on the SCADA system will meet the certification per section 1.7.7 o 15 years or more in programming, ICS system, and troubleshooting complex system.(PLC, DDC and other misc. system)

• Experience electrician or leading electrician that is knowledge with the NEC code

• 15 years or more as ICS technician that can troubleshoot, integrate and wire up controller and identify mechanical system or sub-system of Process, HVAC, Ulitities system, Elevator BMS controller system.

• Experience Project manager that has 15 years or more of experience running multiple projects.

1.7.11 Identification of Contractor Employees: All contract personnel (to include subcontractors) attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed. All Contractor personnel shall clearly identify themselves as a Contractor and shall be required to wear identification (ID) badges in a visible location on the front of exterior clothing, above the waist, (except when safety or health reasons prevent such placement). ID badges shall be worn at all times when performing work. ID badges shall have an identification picture, and shall state the name of the individual and the company they represent. A listing of issued identification cards shall be furnished to the Contracting Officer prior to the contract performance date and updated as needed to reflect Contractor and Subcontractor personnel changes. Contractor personnel are prohibited from possessing weapons, firearms or ammunition, on themselves or within their Contractor-owned or privately owned vehicle while on BEP premises.

1.7.12 Supervision of Contractor Employees: The Government will not exercise any supervision or control over Contractor or subcontractor employees while performing work under the contract. Such employees shall be accountable solely to the Contractor, not the Government. The Contractor, in turn, shall be accountable to the Government for Contractor or subcontractor employees.

1.7.13 Data Rights The Government has unlimited rights to all documents/material/software/program produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.7.14 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.7.15 PHASE IN /PHASE OUT PERIOD: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the 30 days phase in/ phase out periods. During the phase in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

PART 2

DEFINITIONS & ACRONYMS

2 DEFINITIONS AND ACRONYMS:

2.7 DEFINITIONS:

2.7.1 References

SCADA System Control Drawings

SCADA Monthly Update Patch Standard Operating Procedures

SCADA Asset Inventory

SCADA Contingency Plan

SCADA IP Map

Aveva, (formerly Schneider Electric,) Software Entitlement Certificate for AVEVA

Citect SCADA and Historian applications

NIST Special Publication 800-82, Guide to Industrial Control Systems (ICS)

Security

NIST FIPS 200, Standards for Security Categorization of Federal Information and

Information Systems

EHS Contractor Requirements Document Control Number: 75D-07.04

EHS Contractor Requirements (WCF) 75W-08.0-02

SCADA EMS System Security Plan (SSP) Johnson Control Engineering Tool Kit

2.7.2 CONTRACT SPECIALIST. The official Government representative delegated authority by the Contracting Officer to administer a contract. This individual is normally a member of the appropriate Contracting/Procurement career field and advises on all technical contractual matters.

2.7.3 CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or services to the government. The term used in this contract refers to the prime.

2.7.4 CONTRACTING OFFICER. A person with authority to enter into, administer, and/or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.7.5 CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.7.6 DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.7.7 DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.7.8 2.1.7. Government-Furnished Property (GFP) or Government Property (GP).

Property in the possession of, or directly acquired by, the Government and subsequently made available to the Contractor.

2.7.9 KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.7.10 PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.7.11 QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are acceptable in accordance with established standards and requirements of this contract.

2.7.12 QUALITY ASSURANCE SPECIALIST. An official Government representative concerned with matters pertaining to the contract administration process and quality assurance/quality control. Acts as technical advisor to the Contracting Officer in these areas.

2.7.13 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.7.14 QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.7.15 SUBCONTRACTOR. One that enters into a contract with a prime contractor.

The Government does not have privity of contract with the subcontractor.

2.7.16 WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.7.17 WORK WEEK. Monday through Friday, except for Federal holidays unless specified otherwise.

2.2. ACRONYMS:

ACOR Alternate Contracting Officer's Representative BEP Bureau of Engraving and Printing CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTS Commercial-Off-the-Shelf FAR Federal Acquisition Regulation HIPAA Health Insurance Portability and Accountability Act of 1996 CO Contracting Officer OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs PIPO Phase In/Phase Out POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Plan TE Technical Exhibit BAS – Building Automation System BEP – Bureau of Engraving and Printing BEN – BEP Enterprise C&A – Certification and Accreditation CIO - Chief Information Officer CAB – Change Advisory Board COR – Contracting Officer’s Representative COTS – Commercial Off The Shelf DMM – Data Management Module DDC – Direct Digital Controller EAMS – Enterprise Asset Management System EMS – Energy Management System ESB – Enterprise Service Bus FIPS – Federal Information Processing Standards HMI – Human Machine Interface HVAC – Heating Ventilating and Air Conditioning ICS – Industrial Control System

IdAM – Identity and Access Management IT – Information Technology FOD – Federal on Demand MEC – Facilities Management Execution Console MSS – Facilities Management Support Suite NIST – National Institute of Standards and Technology OPC – Object Linking and Embedding (OLE) for Process Control OFS- Office Facilities Support PIV- Personal Identity Verification PLC – Programmable Logic Controller RDS – Remote Desktop Server SCADA- Supervisory Control and Data Acquisition VLAN – Virtual Local Area Network SSP – System Security Plan DAC – Desk Application Control list

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3 GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1 Facilities: The Government will provide two cubics and an office/ store space for hardware, parts and tools.

3.2 Equipment: The Government will provide BEP laptop to contractor has PIV card, network access and is actively supporting the SCADA contract more that 8 hours per week. In addition, it will be a determination on a case by case determine by the COR and SCADA SME.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4 CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

PART 5

SPECIFIC TASKS

5 Specific Tasks:

Basic Services. The contractor shall provide services for the following; maintenance of a software support contract, services hours for maintenance support per the defined hours (~960 hours-DCF and 2000 hours first two years with a reduction in total hours by

100 hours each option year - WCF) , annual training, and a means for system modifications and hardware related repairs.

5.1 MANUFACTURER SUPPORT CONTRACTS REQUIRED: Contractor shall provide and maintain manufacturer support contracts for the following:

AVEVA CITECT SCADA support contract

• The contractor will maintain support contract with AVEVA

Citect SCADA (formerly Schneider Electric,) software developer, including phone support and updates for the following licenses:

o Historian License x 1 o Historian Client License x 1 o View Only Clients x 7 or more o Redundant View Only Client x 7 or more o Control Clients x 7 or more o Redundant Control Client x 7 or more o Full Licenses Unlimited x 4 o Demo Key x 1* o BACnet® Driver (Facilities) x 2 o 1500 Point FullLicense x 1 o 500 Points full server License keys x 2

Tridium Enterprise SMA

• The contractor will provide and maintain support contract with Tridium, including phone support, provide updates and upgrades for the following licenses/devices:

o FX80 X 16 o Workbench/Server X 3

5.2 MAINTENANCE SUPPORT SERVICES: The contractor will provide 960 hours per year for DCF, and the following for WCF (2000 hours for 1st and 2nd years, 1900 for third years, 1800 for 4th years, 1700 hours for 5th years). These hours are to support both facilities (DCF and WCF) via onsite or on VPN to provide maintenance support services described in this section. Maintenance support services include software loading, programming, troubleshooting, system checks, system access, updates, patches, system modifications, report generation, software-based repairs, and configuration services. Configuration services include software configuration and existing hardware configuration. Services requiring new hardware, construction materials, and field installations are covered in the MAJOR MODIFICATIONS AND HARDWARE RELATED

REPAIRS section of the Statement of Work. Major programming changes, system upgrades, and configuration changes not requiring hardware but requiring more than

240 hours of support time shall be executed under the MAJOR MODIFICATIONS AND

HARDWARE RELATED REPAIRS section.

5.2.1 Work Planning and Reporting

• BEP and the contractor will coordinate and develop a listing of all tasks to work on regarding SCADA system changes and maintenance.

• Contractor will update the daily log, check in and out email each day per the QASP.

• Upon the conclusion of each month, the contractor will provide a report of what work was accomplished or a meeting to goes over items every two weeks.

5.2.2 The contractor will provide support to handle access management issues related to SCADA based system users. This would include the following tasks:

• Usernames and password administration. Including IdAM practices and PIV card usage and application username and password.

• User access control insuring appropriate administrative rights.

• Icon deployment and access configurations

• Remediation of access issues.

5.2.3 The contractor will adjust equipment operation schedules and run or modify reports as needed.

5.2.4 The contractor will make changes to the existing SCADA system’s architecture, graphics, trend, variable tag, alarm, schedules, and reporting for existing SCADA integrated equipment where no additional hardware or field installations are required.

5.2.5 The contractor shall insure proper operation of the following software applications installed and functioning as part of the SCADA system: Matrikon OPC connection®, OPC Redundancy, Matrikon ODBC, Workstation HDMI Card Driver, ModScan, LogOnExpert, CCT(FX&JCI), Tridium FX workbench and other, ABB, Rockwell, other

PLC, misc. software on the SCADA share folder.

• The contractor will advise when updates or patches are needed and assist the Office of IT Operations in their installation.

5.2.6 In the event the SCADA system is not operating properly, the contractor is not onsite, and the system cannot be repaired remotely, the contractor will respond onsite within one (1) workday to diagnose the problem. The contractor will also commence repairs assuming it’s not hardware related or IT related. The time onsite while conducting repairs will be included in the annual service hours under

Maintenance Service Support line item which depend on either WCF or DCF.

• Contractor will ensure all controller and gateway software programs are verify with the proper backed up. This applies to Johnson Controls

FX80,Johnson Controls FX-PCG’s®, BMS-LINK® Motion Control

Engineering (elevator controls), Accromags®, Tridium JACE®, QuickServer Modbus RS485 Gateways, EGX Gateways, EtherMeters®, PLCs and any other protocol converter, router, or gateway used in the

SCADA system.

• The contractor will be required to provide management support for

SCADA applications.

5.2.7 Ongoing Patching and Updating. Note that work may be done off shift or during weekends.

• Support during SCADA server operating system patching.

• Support database related critical patch updates.

• Monitor SCADA system software manufacturers to ensure BEP is current with patches and updates.

5.2.8 Coordinate and deploy the following:

• Software version upgrades available through AVEVA Citect’s service contract

• Software version upgrades available through Tridium SMA service contract

• Hotfixes

• Service Packs

• Driver Updates

• SCADA system software patching tasks to include planning, testing, scheduling, and deploying patches in such a way so as not to disrupt system users.

• Patching and firmware updates of underlying SCADA subsystems including Johnson Controls 80’s®, Johnson Controls FX-PCG’s®, BMS-

LINK® Motion Control Engineering (elevator controls), Accromags®, Tridium JACE ®, QuickServer Modbus RS485 Gateways, EGX Gateways, and EtherMeters® and other ICS controller devices on the ICS VLAN.

• Patch Remediation (“backing out” any patches noted above that cause breakages in any systems)

5.2.9 AVEVA Citect SCADA checks:

• Identify communication issues.

• Check SCADA system for proper server to server communication

• AVEVA CitectTest OPC server for proper operation for DMM integration.

Correct if messaging errors are on AVEVA Citect side and non-hardware related.

• Verify proper operation of 10 SCADA workstations and 2 RDS (Jump

Server) for remote workstations, 4 redundant SCADA servers, 1 SQL server, 16 or less SCADA laptops. Correct communication errors if needed unless hardware related per DCF and WCF.

5.2.10 AVEVA Citect Historian checks:

• Verify number of tags in historian is not approaching or exceeding the license limit (currently 5000 tags)

• Verify hard drive space available for SQL database

• Verify proper running condition of historian event and historian data service. Correct if needed.

5.2.10.1 SCADA System functionality checks

• Ensure that operating screens, schedules, and reports are functioning as designed.

o Verify reports that are pulling the correct data and troubleshoot where broken connections.

• All data shown in the AVEVA Citect SCADA is correctly displayed and updating properly. Correct if needed unless hardware related.

• All data shown in reports and trends is correctly displayed and updating properly. Correct if needed unless hardware related.

5.2.11 SCADA System Integrations of devices to SCADA includes the following(no

Additional Hardware or Wiring):

• Integration includes DDC associated with building systems, equipment digital controllers, field instrumentation, meters, or PLC’s controlling equipment or processes. Integrations apply to new and existing equipment.

• New integrations will include graphics, alarming, scheduling, reporting, and trending configuration.

• HVAC equipment integrations, where the contractor provides a Johnson

Control DDC device, PLC or other, will be to AVEVA Citect.

• Maintenance and troubleshoot any communications issue between

SCADA, Maximo ODBC connection and the following ESB subsystem

(Maximo, FlowSys and DMM or new subsystem) via OPC communication protocol.

• Integrations any future ESB subsystem per the direction of the BEP customer and approval from SCADA manager via currently OPC architect.

5.3 ONGOING USER TRAINING

5.3.1 Time spent to prepare and provide training shall be allocated from the 88 hours per facilities.

• User training will be scheduled as needed o Training shall be targeted for operator level users. Classroom setting for three shifts (25 users per class). Training shall include documentation. Training sessions should be approximately 60 minutes.

5.3.2 Contractor shall be notified no less than three (3) weeks prior to planned training date.

5.3.3 Training will be scheduled for WCF and DCF.

5.4 MAJOR MODIFICATIONS, SPARE PARTS, AND HARDWARE RELATED

REPAIRS

5.4.1 Amount spent on this contract line item shall not exceed

• WCF - $200,000.00 for base and 1st option year and $175,000 for Option year 3,4, and 5.

• DCF - $500,000.

• All proposals will include the fully priced list above for WCF and DCF.

• Quotes will be executed no later than 8 weeks after a written or Oral request

5.4.2 Spare parts used in the SCADA system shall be purchased under this portion of the contract. Spare parts include any electronic component associated with control. A spare part shall be purchased through this portion of the contract if it is a critical component with a lead-time in excess of 5 days or has purchasing limitations imposed by the manufacturer. The BEP will identify any spare parts required and manage the inventory.

5.4.3 Major modification and/or equipment repair of the SCADA system may be needed. Services requiring hardware, materials, and field installations such as panel fabrication and wiring as well as time for development, configuration, and programming of SCADA software applications are included in this portion of the

Statement of Work.

• In the event a software update, upgrade, or patch is required and is not included in an existing software license, service agreement, or requires more than 240 service hours, then it is considered a major modification and covered in this portion of the Statement of Work.

• In the event of a SCADA major modification and / or equipment related repair, a scope will be provided to the contractor to which the contractor will propose.

• The contractor’s proposal will include development services, installation services, hardware, and material to modify the SCADA system. Major modifications and equipment related repairs include the following:

o Changes to the existing SCADA system’s architecture, graphics, schedules, and reporting for existing SCADA integrated equipment where additional hardware and / or field installations are required.

o Integration of newly installed or existing equipment previously unintegrated to SCADA, where additional hardware and / or field installations are required.

o Repair of hardware or component replacement associated with the SCADA system.

o Contractor will show all itemized costs for material and labor in major modification or equipment related repair proposals.

5.4.4 Original equipment manufacturers’ buyback or hardware/software exchange programs to address obsolescent shall be executed under this portion of the contract.

5.4.5 Contractor will provide all connections from field device to network drop and possible the network cabinet. BEP will provide and define all connections from network switch to servers. Contractor shall connect power to panel or control device. Contractor shall coordinate power supply with BEP prior to installation.

5.4.6 Contractor will update all pertinent documentation including manuals, IT procedures, drawings, Power Distribution Database (PDD), and IP Maps.

5.4.7 Contractor will provide training to users regarding changes to SCADA system.

5.4.8 All new software will be provide to BEP and save under the SCADA share folder.

All programs or program change will be backup to SCADA share folder.

PART 6

APPLICABLE PUBLICATIONS

6 APPLICABLE PUBLICATIONS (CURRENT EDITIONS)

The Contractor (to include subcontractors) must abide by all applicable regulations, publications, manuals, and local policies and procedures.

6.3 National Electric Codes, local codes, and electrical specification, whichever is the most stringent.

6.4 Safety requirement per Environment, Health and safety or OSHA.

6.4.1 All field installations and construction related activities shall adhere to the EHS

Contractor Requirements, document control number: 75D-07.04.

6.4.2 All field installations will adhere to the National Electrical Code and control panel fabrications will adhere to UL 508A standards.

6.5 NFPA – National Fire protection association

6.6 For all work done under this contract, the contractor will certify applications are fully functional and operate correctly as intended on systems using the USGCB.

PART 7 – ATTACHMENT/TECHNICAL EXHIBIT LISING

Attachment/Technical Exhibit List:

Attachment 1/Technical Exhibit 1 – Performance Requirements Summary Attachment 2/Technical Exhibit 2 – Deliverables Schedule

TECHNICAL EXHIBIT 1 - PERFORMANCE REQUIREMENTS SUMMARY

The Contractor tasks is to follow the PWS and any request from the COR of the SCADA system.

All items will be tracked per the QASP plan.

Performance Objective

Performance Standard Performance Threshold Incentives (Positive or Negative)

Service Hours All tasks will be completed or work on through out the year.

Provide update of task in checkout email.

Demonstrate tasks are completed when requested by COR.

Provide feedback and recommendation on process to improve the system.

COR will monitor and provide feedback on all task and request.

All issues will be escalated to support contract, other resources and COR to resolve in a time manner.

System shall work at the end and operating properly for deployment any time.

• Email and phone call by the COR.

• CPAR report

• Monthly report

• Service hours will be questioned if the hours were done properly and to BEP/SCADA standard.

Trainning Session All sessions are completed

Sign in sheet will be done.

Trainning manual will be provided.

Suggestion of training topic will be provided from COR.

• CPAR report

• Feedback from the operators

Major modification change

Quote will be delivered in a timely maner per writing or oracle request.

ICS integration will follow the standard and best practice layout by COR.

All modifications will work properly and satisfy the

COR.

COR will be the approval and acceptable of the system.

Any issues will be corrected in a timely manner Any hardware failure will resolved in a timely manner.

• Continue Warranty call back to fix the issue.

• Continue call back until the project is done to BEP standard.

• Invoice will not be paid since system needs to work per…