25 10 10.00 24.pdf

Bangor P-907 TPP Pier 217069

SECTION 25 10 10.00 24

UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION

(NAVFAC NW)

NAVFAC NW Version 3.2; issued 11/27/2018

PART 1 GENERAL

1.1 SUMMARY

The Utility Monitoring and Control System (UMCS) shall perform supervisory monitoring and supervisory control of base-wide building control systems and utility control systems using Niagara Framework with Fox protocol as specified and shown. The UMCS shall interface with local building or other control systems installed per other Sections.

Version 3.2 Appendices A - F referenced throughout this UFGS can be found on the Whole Building Design Guide web page for this spec ( https://www.wbdg.org/ffc/navy-navfac/regional-specifications/ nfgs-25-10-10-00-24 ._ Click on the hyperlink next to the words "Related Materials" for "UMCS Front-End Integration (NAVFAC NW) APPENDICES A-Fv3.2" (PDF file).

1.1.1 System Requirements

Provide a UMCS as specified and shown, and in accordance with the following characteristics:

The Control System consists of a high-speed, peer-to-peer network of workstations, servers, routers, network switches and stand-alone supervisory controllers. This network provides the capability to integrate BACnet, LonWorks, MODBUS, OPC and other open and proprietary communication protocols into one open, interoperable system.

A web based controller and server with a network interface card gathers data from this system and generates web pages accessible through an Internet Explorer™ web browser on each workstation connected to the network. Operators are able to perform normal and expanded operator functions through this web browser interface.

The system installed in this project, including all associated equipment and accessories, shall tie into the existing Niagara-based Control System.

Each SC shall communicate to other open and legacy protocol systems/devices installed in the facility.

The UMCS is comprised of supervisory controllers which are based on a hierarchical architecture incorporating Niagara Framework™ ("Niagara").

All new and replacement equipment shall be compliant with the NiagaraFramework.

1.1.1.1 General System Requirements

a. The system shall perform supervisory monitoring and control functions including Scheduling, Alarm Handling, Trending, Overrides, Report Generation, and Electrical Demand Limiting as specified.

b. The system shall include a Graphical User Interface which shall allow for graphical navigation between systems, graphical representations of

SECTION 25 10 10.00 24 Rev 1 Page 1 October 26, 2020 systems, access to real-time data for systems, ability to override points in a system, and access to all supervisory monitoring and control functions. See Appendices B and C for additional information.

c. All software used by the UMCS and all software used to install and configure the UMCS shall be licensed to and delivered to the NAVFAC NW

CIO.

d. All software used by the UMCS shall be compatible with 64-bit (x64) versions of Windows operating system.

e. All necessary documentation, configuration information, configuration tools, programs, drivers, and other software shall be licensed to and otherwise remain with the Government such that the Government or their agents are able to repair, replace, upgrade, and expand the system without subsequent or future dependence on the Contractor. Software licenses shall not require periodic fees and shall be valid in perpetuity.

f. Provide sufficient documentation and data, including rights to documentation and data, such that the Government or their agents can execute work to repair, replace, upgrade, and expand the system without subsequent or future dependence on the Contractor.

g. The UMCS shall interface directly to BACnet ( ASHRAE 135), LonwWorks ( CEA-709.1-D ), Modbus, OPC DA, and Niagara Framework field control systems as specified.

h. For UMCS systems with Monitoring and Control Software functionality implemented in Monitoring and Control (M&C) Controller Hardware, provide sufficient additional controller hardware to support the full capacity requirements as specified.

i. All Niagara Framework components shall have an unrestricted interoperability license with a Niagara Compatibility Statement (NiCS) following the Tridium Open NiCS Specification and shall have a value of "ALL" for "Station Compatibility In", "Station Compatibility Out", "Tool Compatibility In" and "Tool Compatibility Out". Note that this will result in the following entries in the license.dat file:

"accept.station.in=*" "accept.station.out=*" "accept.wb.in=*" "accept.wb.out=*"

1.1.1.2 Niagara Framework Requirements

The UMCS shall use the Niagara Framework and shall communicate with Niagara Framework field control systems using the Fox protocol and HTTP over the Government furnished IP network. Extend the Government's IP network as indicated in the project documents.

1.1.2 General Cybersecurity Requirements

Cybersecurity for the system shall be addressed in accordance with 25 50 00.00 20 CYBERSECURITY OF FACILITY-RELATED CONTROL SYSTEMS and the following requirements.

SECTION 25 10 10.00 24 Rev 1 Page 2 October 26, 2020

1.1.2.1 Cyber Security

Prior to initiating any work on site pertaining to the UMCS each contractor employee who will work on programming or existing UMCS infrastructure shall:

a. Complete the SAAR-N form and the NAVFAC NW CS IA Addendum (provided by NAVFAC NW and included as Appendix F) and provide to Contracting Officer;

b. Complete the annual Department of Defense Information Assurance Awareness training;

c. Have proof of a clean background investigation with a least a Facility Access Determination (FAD)

Contractor should plan on the clearance activities listed above taking 12 weeks for personnel not already holding a Government security clearance.

Clearance activities can take longer than 12 weeks for individuals found to have clearance issues during their background check.

Admin Rights: Contractors will not be granted full admin rights to any government-owned computer. Local accounts on government computers are not allowed; contractors whose personnel who have submitted their forms and have a proper background check or clearance will be granted access for the duration of the project.

USB 'thumb' drives are prohibited on Government equipment.

Government-supplied USB hard drives are acceptable and can be checked out from CIO.

The Contractor shall not connect contractor owned computer equipment to the regional Controls System network, nor leave behind any telecommunication infrastructure (i.e., cellular modems) that allows remote access into installed equipment. All points of ingress and egress will be authorized and maintained by NAVFAC NW CIO and only after all required network ports and protocols are identified and documented.

The Contractor will be allowed to check out UMCS laptops for field use.

Laptops for field use while on-site may be checked out from the UMCS laptop pool managed by NAVFAC NW CIO at NBK-Bangor, WA. Laptop check-out reservations should be scheduled at least one week in advance ensuring availability.

Provide secure password protection for each device/system; provide all integration necessary to incorporate centralized authentication i.e.

ensuring single sign on leveraging Lightweight Directory Access Protocol (LDAP) provided by NAVFAC NW supported Active Directory Architecture.

Password information shall be need-to-know, and the Contractor shall not disclose it to others. Password information shall be submitted via hard copy correspondence or CD to the Contracting Officer's Representative.

Passwords shall not be conveyed by e-mail or 3rd party means, except encrypted email is acceptable.

If at any of the above security requirements are violated, the individual(s) will have (at a minimum) their Government computer access privileges revoked. All IT related possessions may be confiscated pending an investigation.

SECTION 25 10 10.00 24 Rev 1 Page 3 October 26, 2020

1.1.3 Symbols, Definition and Abbreviations

Symbols, definitions, and engineering unit abbreviations used in displays, submittals and reports shall be as currently used in the existing CS graphical user interface unless noted otherwise. See Appendix B for more information.

1.1.4 System Units and Accuracy

Displays, print-outs and calculations shall be performed in English (inch-pound) units. Calculations shall have accuracy equal to or exceeding sensor accuracy as specified in Section 23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC. Displays and printouts shall present values to at least one significant figure.

1.1.5 Data Packages/Submittal Requirements

Technical data packages consisting of computer software and technical data (meaning technical data which relates to computer software) which are specifically identified in this project and which may be defined/required in other specifications shall be delivered strictly in accordance with the CONTRACT CLAUSES and in accordance with the Contract Data Requirements List, DD Form 1423. Data delivered shall be identified by reference to the particular specification paragraph against which it is furnished. All submittals not specified as technical data packages are considered shop drawings under the Federal Acquisition Regulation Supplement (FARS) and shall contain no proprietary information and shall be delivered with unrestricted rights.

1.2 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2016) BACnet—A Data Communication Protocol for Building Automation and Control Networks

CONSUMER ELECTRONICS ASSOCIATION (CEA)

CEA-709.1-D (2014) Control Network Protocol Specification

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE 1815 (2015; CORR 2016) Exchanging Information Between Networks Implementing IEC 61850 and IEEE Std 1815 Distributed Network Protocol (DNP3)

IEEE C62.41 (1991; R 1995) Recommended Practice on Surge Voltages in Low-Voltage AC Power Circuits

SECTION 25 10 10.00 24 Rev 1 Page 4 October 26, 2020

LONMARK INTERNATIONAL (LonMark)

LonMark SNVT List (2014) LonMark SNVT Master List; Version 15

LonMark XIF Guide (2001) LonMark External Interface File Reference Guide; Revision 4.402

MODBUS ORGANIZATION, INC (MODBUS)

Modbus (2006) Modbus Application Protocol Specification; Version 1.1b and Modbus Messaging on TCP/IP Implementation Guide;

Version V1.0b

NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)

NEMA 250 (2014) Enclosures for Electrical Equipment (1000 Volts Maximum)

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 262 (2019) Standard Method of Test for Flame Travel and Smoke of Wires and Cables for Use in Air-Handling Spaces

NFPA 70 (2017; ERTA 1-2 2017; TIA 17-1; TIA 17-2;

TIA 17-3; TIA 17-4; TIA 17-5; TIA 17-6;

TIA 17-7; TIA 17-8; TIA 17-9; TIA 17-10;

TIA 17-11; TIA 17-12; TIA 17-13; TIA

17-14; TIA 17-15; TIA 17-16; TIA 17-17 )

National Electrical Code

OPC FOUNDATION (OPC)

OPC DA (Ver 3.0; Errata) OPC Data Access (DA)

TELECOMMUNICATIONS INDUSTRY ASSOCIATION (TIA)

TIA-568-C.1 (2009; Add 2 2011; Add 1 2012) Commercial Building Telecommunications Cabling Standard

TIA-606 (2017c) Administration Standard for the Telecommunications Infrastructure

TIA-607 (2011b) Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises

TRIDIUM, INC (TRIDIUM)

Niagara Framework (2012) NiagaraAX User's Guide

Tridium Open NiCS (2005) Understanding the NiagaraAX Compatibility Statement (NiCS)

U.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)

FCC EMC (2002) FCC Electromagnetic Compliance

SECTION 25 10 10.00 24 Rev 1 Page 5 October 26, 2020

Requirements

FCC Part 15 Radio Frequency Devices (47 CFR 15)

UNDERWRITERS LABORATORIES (UL)

UL 1778 (2014; Reprint Sep 2017) UL Standard for Safety Uninterruptible Power Systems

UL 60950 (2000; Reprint Oct 2007) Safety of Information Technology Equipment

1.3 DEFINITIONS

The following list of definitions may contain terms not found elsewhere in this Section but are included here for completeness. Some terms are followed with a protocol reference in parenthesis (for example: (BACnet)) indicating to which protocol the term and definition applies.

1.3.1 Access Switch

An access switch has one or two trunk port connections. An access switch permits access to primarily end devices and not to other switches.

1.3.2 Alarm Generation

The process of comparing a point value (the point being alarmed) with a pre-defined alarm condition (e.g. a High Limit) and performing some action based on the result of the comparison.

1.3.3 Alarm Handling

See Alarm Routing

1.3.4 Alarm Routing

Alarm routing is M&C software functionality that starts with a notification that an alarm exists (typically as the output of an Alarm Generation process) and sends a specific message to a specific alarm recipient or device.

1.3.5 BACnet (BACnet)

The term BACnet is used in two ways. First meaning the BACnet Protocol Standard - the communication requirements as defined by ASHRAE 135 including all annexes and addenda. The second to refer to the overall technology related to the ASHRAE 135 protocol.

1.3.6 BACnet Interoperability Building Blocks (BIBBs) (BACnet)

A BIBB is a collection of one or more BACnet services intended to define a higher level of interoperability. BIBBs are combined to build the BACnet functional requirements for a device in a specification. Some BIBBs define additional requirements (beyond requiring support for specific services) in order to achieve a level of interoperability. For example, the BIBB DS-V-A (Data Sharing-View-A), which would typically be used by an M&C client, not only requires the client to support the ReadProperty Service, but also provides a list of data types (Object / Properties) which the client must be able to interpret and display for the user.

SECTION 25 10 10.00 24 Rev 1 Page 6 October 26, 2020

1.3.7 BACnet Testing Laboratories (BTL)(BACnet)

Established by BACnet International to support compliance testing and interoperability testing activities and consists of BTL Manager and the BTL Working Group (BTL-WG). BTL also publishes Implementation Guidelines.

1.3.8 BACnet Testing Laboratories (BTL) Listed (BACnet)

A device that has been certified by BACnet® Testing Laboratory. Devices may be certified to a specific device profile, in which case the certification indicates that the device supports the required capabilities for that profile, or may be certified as "other".

1.3.9 Binary

A two-state system or signal; for example one where an "ON" condition is represented by a high signal level and an "OFF" condition is represented by a low signal level. 'Digital' is sometimes used interchangeably with 'binary'.

1.3.10 Broadcast

Unlike most messages, which are intended for a specific recipient device, a broadcast message is intended for all devices on the network.

1.3.11 Building Control Network (BCN)

The network used by the Building Control System. Typically the BCN is a BACnet ASHRAE 135 or LonWorks CEA-709.1-D network installed by the building control system contractor.

1.3.12 Building Control System (BCS)

One type of Field Control System. A control system for building electrical and mechanical systems, typically HVAC (including central plants) and lighting. A BCS generally uses Direct Digital Control (DDC) Hardware and generally does NOT include its own local front end.

1.3.13 Building Point of Connection (BPOC)

A FPOC for a Building Control System. (This term is being phased out of use in preference for FPOC but is still used in some specifications and criteria.)

1.3.14 Clearance

Security Clearance

1.3.15 Control Logic Diagram

A graphical representation of control logic for multiple processes that make up a system.

1.3.16 Facility Point Of Connection (FPOC)

The FPOC is the point of connection between the UMCS IP Network and the field control network (either an IP network, a non-IP network, or both).

The hardware at this location which provides the connection is generally

SECTION 25 10 10.00 24 Rev 1 Page 7 October 26, 2020 one of a control protocol router, a control protocol gateway, or an IT device such as a switch, IP router, or firewall.

In general, the term "FPOC Location" means the place where this connection occurs, and "FPOC Hardware" means the device that provides the connection. Sometimes the term "FPOC" is used to mean either and its actual meaning (i.e. location or hardware) is determined by the context in which it is used.

1.3.17 Field Control Network

The network used by a field control system.

1.3.18 Field Control System (FCS)

A building control system or utility control system.

1.3.19 Fox Protocol (Niagara Framework)

The protocol used for communication between components in the Niagara Framework. By default, Fox uses TCP port 1911

1.3.20 Gateway

A device that translates from one protocol to another. Devices that change only the transport mechanism of the protocol - "translating" from LonWorks over TP/FT-10 to LonWorks over IP for example - are not gateways as the underlying protocol (data format) does not change. Gateways are also called Communications Bridges or Protocol Translators.

1.3.21 Control System (CS or now moving to calling it "UMCS")

The NAVFAC NW Control System (CS) is an integration of SCADA (Supervisory Control And Data Acquisition - for Utility System control) and DDC (Direct Digital Control - for Facility mechanical and electrical control) devices and the individual control systems, networks, field equipment, sensors and actuators that provide monitoring and control function for mechanical and electrical systems, and Advanced Metering Infrastructure. All control systems are part of the UMCS, whether part of a utility or a facility.

Advanced Metering Infrastructure (AMI) is part of the CS program, but is not covered by this guide specification.

1.3.22 JACE (Niagara Framework)

Java Application Control Engine. See "Niagara Framework Supervisory Gateway". Note: The Niagara Framework parent corporation Tridium's product line of supervisory controllers are called "JACE" so the term "JACE" should be avoided when discussing supervisory controllers/gateways generally as it appears to refer to a proprietary product.

1.3.23 LDAP

Lightweight Directory Access Protocol. LDAP is used to authenticate supervisory controllers and computers to the NAVFAC CS Windows Domain.

1.3.24 Master-Slave/Token Passing (MS/TP)(BACnet)

Data link protocol as defined by the BACnet standard. Multiple speeds (data rates) are permitted by the BACnet MS/TP standard.

SECTION 25 10 10.00 24 Rev 1 Page 8 October 26, 2020

1.3.25 Monitoring and Control (M&C) Software

The UMCS 'front end' software which performs supervisory functions such as alarm handling, scheduling and data logging and provides a user interface for monitoring the system and configuring these functions.

1.3.26 NAVFAC NW CIO (CIO)

NAVFAC NW CIO (CIO) is the authority having jurisdiction over all CS IT (Information Technology) and OT (Operational Technology).

1.3.27 Network or CS Network

The CS is composed of Ethernet TCP/IP router-switch-and-cable network running over copper and fiber media, and serial networks running over a variety of media.

1.3.28 Niagara AX (Also called "Niagara")

A version (release) of the Niagara Framework used by NAVFAC NW. While it is often used to refer to just the front end, it includes all components of the Niagara Framework. NAVFAC NW (along with the Navy enterprise-wide) is moving to Niagara 4 via inclusion in the enterprise Authority to Operate.

1.3.29 Niagara Framework (Niagara Framework)

A set of hardware and software specifications for building and utility control owned by Tridium Inc. and licensed to multiple vendors. The Framework consists of front end (M&C) software, web based clients, field level control hardware, and engineering tools. While the Niagara Framework is not adopted by a recognized standards body and does not use an open licensing model, it is sufficiently well-supported by multiple HVAC vendors to be considered a de-facto Open Standard.

1.3.30 Niagara Framework Supervisory Gateway (Niagara Framework)

DDC Hardware component of the Niagara Framework. A typical Niagara architecture has Niagara specific supervisory gateways at the IP level and other (non-Niagara specific) controllers on field networks (TP/FT-10, MS/TP, etc.) beneath the Niagara supervisory gateways. The Niagara specific controllers function as a gateway between the Niagara framework protocol (Fox) and the field network beneath. These supervisory gateways may also be used as general purpose controllers and also have the capability to provide a web-based user interface. NAVFAC NW has called these devices "Supervisory Controllers" in the past, but is aligning with enterprise-wide terminology and will now use the term "gateway".

1.3.31 Override

To change the value of a point outside of the normal sequence of operation where this change has priority over the sequence. An override can be accomplished in one of two ways: the point itself may be Commandable and written to with a priority or there may be a separate point on the controller for the express purpose of implementing the override.

Typically this override is from the Utilities Monitoring and Control System (UMCS) Monitoring and Control (M&C) Software. Note that this

SECTION 25 10 10.00 24 Rev 1 Page 9 October 26, 2020 definition is not standard throughout industry.

1.3.32 Point, Calculated

A value within the M&C Software that is not a network point but has been calculated by logic within the software based on the value of network points or other calculated points. Calculated points are sometimes called virtual points or internal points.

1.3.33 Point, Network

A value that the M&C Software reads from or writes to a field control network.

1.3.34 Polling

A requested transmission of data between devices, rather than an unrequested transmission such as Change-Of-Value (COV) or Binding where data is automatically transmitted under certain conditions.

1.3.35 Property (BACnet)

A BACnet Property - a data element associated with an Object. Different Objects have different Properties, for example an Analog Input Object has a Present_Value Property (which provides the value of the underlying hardware analog input), a High_Limit Property (which contains a high limit for alarming), as well as other properties.

1.3.36 Protocol Implementation Conformance Statement (PICS)(BACnet)

A document, created by the manufacturer of a device, which describes which potions of the BACnet standard are implemented by a given device.

1.3.37 Repeater

A device that connects two control network segments and retransmits all information received on one side onto the other.

1.3.38 Router (BACnet)

A device that connects two or more BACnet networks and controls traffic between the networks by retransmitting signals received from one network onto another based on the signal destination. Routers are used to subdivide an internetwork and to control bandwidth usage.

1.3.39 SAAR-N Form (SAAR)

A System Authorization Access Request - Navy form and any required addendums. These forms are used to request UMCS access and validate that an individual has the appropriate security clearance in place prior to performing any work related to the UMCS. A SAAR form is also used to request a domain account for a new user.

1.3.40 Segment

A 'single' section of a control network that contains no repeaters or routers. There is generally a limit on the number of devices on a segment, and this limit is dependent on the topology/media and device type. For example, a TP/FT-10 segment with locally powered devices is

SECTION 25 10 10.00 24 Rev 1 Page 10 October 26, 2020 limited to 64 devices, and a BACnet MS/TP segment is limited to 32 devices.

1.3.41 Service (BACnet)

A BACnet Service. A defined method for sending a specific type of data between devices. Services are always defined in a Client-Server manner, with a Client initiating a Service request and a Server Executing the Service. Some examples are ReadProperty (a client requests a data value from a server), WriteProperty (a client writes a data value to a server), and CreateObject (a client requests that a server create a new object within the server device).

1.3.42 Standard BACnet Object/Property/Service (BACnet)

BACnet Objects, Properties, or Services that are standard Objects, Properties, or Services enumerated and defined in ASHRAE 135. Clause 23 of ASHRAE 135 defines methods to extend ASHRAE 135 to non-standard or proprietary information. Standard BACnet Objects/Properties/Services specifically exclude any vendor specific extensions.

1.3.43 Supervisory Controller (also called "SC")

A controller implementing a combination of supervisory logic (global control strategies or optimization strategies), scheduling, alarming, event management, trending, web services or network management. Note this is defined by use; many supervisory controllers have the capability to also directly control equipment. Supervisory controllers can also be gateways and typically are in a Niagara Framework-based UMCS. See "Niagara Framework Supervisory Gateway" definitiona above. NAVFAC NW is moving away from the term "supervisory controller" to describe the controller that contains the Niagara Framework and using "gateway" instead.

1.3.44 Supervisory Gateway

A device that is both a supervisory controller and a gateway, such as a Niagara Framework Supervisory Gateway.

1.3.45 Transport Switch

Switch with more than two trunk port connections and acts as WAN (wide area network) connectivity.

1.3.46 Trunk Port Connection

A port that is assigned to carry traffic for all the VLANs that are accessible by a specific switch, a process known as trunking. This is typically a switch-to-switch connection.

1.3.47 VLAN

A virtual LAN is a group of hosts with a common set of requirements that communicate as if they were attached to the same broadcast domain, regardless of their physical location. A VLAN has the same attributes as a physical LAN, but it allows for end stations to be grouped together even if they are not located on the same network switch. The UMCS IP network is divided into multiple VLANs, which include Administration, Utility systems, Facility systems and metering systems, printers, each type of server, workstations internal to the Operations Center, workstation external to Operations Center and more. Multiple VLANs are in use, and

SECTION 25 10 10.00 24 Rev 1 Page 11 October 26, 2020 are subject to change by CIO.

1.4 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control approval. Submittal with a "G-CIO" designation shall be routed to NAVFAC NW CIO for approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES and TABLE 1: PROJECT SEQUENCING

Provide one copy of required paper and electronic submittals.

Limit submittal information to only that required by this specification.

Do not package product data, design drawings, wiring/network diagrams, or other submittals required by building automation field control systems into the UMCS submittals. Doing so could result in immediate rejection.

Drawings:

Provide review drawings as PDF compatible files e-mail and optical disk and each drawing on 11" x 17" paper.

SD-02 Shop Drawings

CS Contractor Design Drawings; G-CIO

CS Contractor Design Drawings on optical disk in PDF and AutoCAD format.

Draft As-Built Drawings; G-CIO

Draft As-Built Drawings on optical disk in PDF and AutoCAD v2010 format.

Final As-Built Drawings; G-CIO

Final As-Built Drawings in hard copy and on optical disk in PDF and AutoCAD v2010 format.

Graphics; G-CIO

Provide graphics pages for the project at actual graphics resolution and format, including all common pieces of equipment, page backgrounds, and menu structures.

Also provide the entire station copy (including images, px pages, and the *.bog file) of the graphical user interface along with the administrative credentials.

SD-03 Product Data

Product Data Sheets; G-CIO

Copies of all manufacturer catalog cuts and specification sheets for all products (equipment) specified in PART 2 and supplied under this contract. When manufacturer's product data sheets apply to a product series rather than a specific product, clearly indicate applicable model selected and options selected by highlighting or by other means.

SECTION 25 10 10.00 24 Rev 1 Page 12 October 26, 2020

Include in the product data sheet submittal a single page with the list price value for each product (do not provide a single lump sum amount) in PART 2 supplied on this project. The itemized list must include all switches, supervisory controllers, data cabling/wiring, software (including drivers or other software added to the switches and supervisory controllers), UPS, and locked rack or enclosure (including intrusion detection). Provide only material costs (not labor) and provide a total sum for the project at the bottom of the list.

Software; G-CIO

Manufacturer OEM support (includes license).

Network UMCS Hardware and Software Inventory; G-CIO

Submit approved switches to NAVFAC NW CIO for configuration.

SD-05 Design Data

Project UMCS Plan; G-CIO

SD-06 Test Reports

Existing Conditions Report; G-CIO

One electronic copy of the Existing Conditions Report.

Password Logs; G-CIO

Provide a preliminary list of all passwords created in executing the work of this contract.

FPT Report; G

One electronic copy of the FPT Report.

SD-10 Operation and Maintenance Data

Operation and Maintenance (O&M) Instructions; G

Only provide O&M information for the supervisory controller.

SD-11 Closeout Submittals

Password Log; G-CIO

Provide a final, complete list of all passwords (and associated software, device or system) created in executing the work of this contract.

Warranty (ethernet switch); G-CIO

Key(s) to Locked Enclosure; G-CIO

Final Supervisory Controller Station; G-CIO

Programming Code Files; G

SECTION 25 10 10.00 24 Rev 1 Page 13 October 26, 2020

1.5 PROJECT SEQUENCING

TABLE I: PROJECT SEQUENCING specifies the sequencing of submittals as specified in paragraph SUBMITTALS (denoted by an 'S' in the 'TYPE' column) and activities as specified in PART 3: EXECUTION (denoted by an 'E' in the 'TYPE' column).

a. Sequencing for submittals: The sequencing specified for submittals is the deadline by which the submittal must be initially submitted to the Government. Following submission there will be a Government review period as specified in Section 01 33 00 SUBMITTAL PROCEDURES. If the submittal is not accepted by the Government, revise the submittal and resubmit it to the Government within 14 working days of notification that the submittal has been rejected. Upon re-submittal there will be an additional Government review period. If the submittal is not accepted, the process repeats until the submittal is accepted by the Government.

b. Sequencing for Activities: The sequencing specified for activities indicates the earliest the activity may begin.

c. Abbreviations: In TABLE I the abbreviation AAO is used for 'after approval of' and 'ACO' is used for 'after completion of'.

d. The Cybersecurity Hygiene Checklist submittal referenced in Table I below is from 25 50 00.00 20 CYBERSECURITY OF FACILITY-RELATED CONTROL SYSTEMS. It is included here for clarity regarding the overall process of connecting to the UMCS IP network.

e. The Network UMCS Hardware and Software Inventory form is detailed in 25 50 00.00 20 CYBERSECURITY OF FACILITY-RELATED CONTROL SYSTEMS, but is a submittal in this specification.

TABLE I. PROJECT SEQUENCING

ITEMTYPE DESCRIPTION SEQUENCING

1 Notice to proceed

2 E Contractor requests existing network topology. Allow 15 working days for NAVFAC NW CIO response.

3 S CS Contractor Design Drawings and Existing Conditions Report;

Project UMCS Plan

60 days after #1

4 S Product Data Sheets 30 days AAO #3

5 S Network Hardware and Software Inventory; Contractor shall deliver to NAVFAC NW CIO all transport and access switches to be installed.

AAO #4

SECTION 25 10 10.00 24 Rev 1 Page 14 October 26, 2020

TABLE I. PROJECT SEQUENCING

ITEMTYPE DESCRIPTION SEQUENCING

6 E Contractor picks up submitted switches.

15 days AAO #5

7 S Graphics AAO #3

8 E Install CS AAO #6

9 S Cybersecurity Hygiene Checklist turned into CIO; Computer Software; Draft As-Built Drawings; Preliminary Password Log

ACO #8

10 S Request physical connection;

Close-out Password Log

10 days after Government AAO #9 (iterative process)

11 E Government authorized personnel will make physical connection.

14 days after #10

12 E UMCS IP NetworkFunctional Performance Testing

AAO #10 and #11

13 S Functional Performance Testing Report

30 days ACO #12

14 S O&M Instructions AAO #13

1.6 QUALITY CONTROL (QC)

1.6.1 Contractor's Qualifications

The Contractor or subcontractor that will perform the work shall have completed at least three systems installations of the same type and design specified and that have successfully operated the required sequence of operation for at least one year. The installer shall be a Niagara AX Contractor-Partner.

Control System Integrator shall exclusively be in the regular and customary business of design, installation and service of networked, computerized building controls systems similar in size and complexity to this project. The Control System Integrator shall be the manufacturer of the primary system components or shall have been the authorized representative for the primary DDC components manufacturer for at least 5 years.

The programmer responsible for programming the gateways shall have a

SECTION 25 10 10.00 24 Rev 1 Page 15 October 26, 2020 minimum of 2 years of experience in programming gateways for similar systems of the same manufacturer. Programmer shall have successfully completed the Niagara AX Certification Training Course (or more current) and be certified. The programmer shall also have attended a NAVFAC NW Front-End Integration Training since this version of the Front-End Integration specification was issued. Contact NAVFAC_NW_PW_ICS_OPS@navy.mil for upcoming training dates and times.

(Note: The date (MM/YY) that this specification was issued can be found immediately under the specification title header at the beginning of this Section.)

1.6.2 Support

Certified local technical support shall exist within 50 miles of the site.

1.6.3 Commissioning

The Government has retained the services of a Commissioning Authority to commission the UMCS and other systems as specified in 01 91 00.00 24 TOTAL

BUILDING COMMISSIONING (NAVFAC NW).

1.7 DELIVERY, STORAGE, AND HANDLING

Stored products shall be protected from the weather, humidity and temperature variations, dirt and dust, and other contaminants, within the storage condition limits published by the equipment manufacturer.

1.8 OPERATION AND MAINTENANCE (O&M) INSTRUCTIONS

The UMCS Operation and Maintenance Instructions shall include:

a. Procedures for the CS system start-up, operation and shut-down.

b. Final As-Built drawings.

c. Routine maintenance checklist. The routine maintenance checklist shall be arranged in a columnar format. The first column shall list all installed devices, the second column shall state the maintenance activity or state no maintenance required, the third column shall state the frequency of the maintenance activity, and the fourth column for additional comments or reference.

d. Qualified service organization list including points of contact with phone numbers.

e. Start-Up and Start-Up Testing Report.

f. Functional Performance Test (FPT) Procedures and Reports.

1.9 RECOMMENDED DIVISION OF WORK

The Division 23, 26, and 33 contractors (when separate from the UMCS contractor) shall be responsible for all controllers, control devices, control panels, controller programming, controller programming software, controller input/output and power wiring and controller network wiring.

The design and installation of these systems are covered in Division 23, 26 and 33 UFGS' .

The UMCS contractor shall be responsible for the SC, software and

SECTION 25 10 10.00 24 Rev 1 Page 16 October 26, 2020 programming of the SC, the graphical user interface, development of all graphical screens, Web browser pages, setup of schedules, alarms, LonWorks network management and connection of the gateway into the UMCS IP network. The UMCS contractor shall integrate all data, monitoring and control provided by the Division 23, 26 and 33 contractor devices and make it available onto the UMCS IP network.

PART 2 PRODUCTS

2.1 EQUIPMENT REQUIREMENTS

2.1.1 Standard Products

Provide components and equipment that are "standard products" of a manufacturer regularly engaged in the manufacturing of products that are of a similar material, design and workmanship. "Standard products" is defined as being in satisfactory commercial or industrial use for 2 years before bid opening, including applications of components and equipment under similar circumstances and of similar size, satisfactorily completed by a product that is sold on the commercial market through advertisements, manufacturers' catalogs, or brochures. Products having less than a 2-year field service record are acceptable if a certified record of satisfactory field operation, for not less than 6000 hours exclusive of the manufacturer's factory tests, can be shown. Provide equipment items that are supported by a service organization.

2.1.2 Product Certifications

Computing devices, as defined in FCC Part 15 , supplied as part of the UMCS shall be certified to comply with the requirements of Class B computing devices.

2.1.3 Product Sourcing

Contractor supplied units of the same type of equipment shall be products of a single manufacturer. Each major component of equipment shall have the manufacturer's name and the model and serial number in a conspicuous place. Materials and equipment shall be new standard unmodified products of a manufacturer regularly engaged in the manufacturing of such products.

The Contractor shall select software, materials and equipment that are compatible with the existing UMCS system. If the Contractor incorporates equipment or devices which require software and programming tools different than those currently in use, the Contractor shall provide compatible software for every server, laptop and desktop workstation in the existing UMCS, any specialized training, and all UMCS modifications or specialized programming needed to support the unique equipment.

Contractor shall utilize as few unique pieces of equipment as possible.

Wherever possible, the Contractor shall utilize a typical piece of equipment in numerous locations.

2.1.4 Ownership of Proprietary Material

Project-specific software and documentation shall become the Government's property. This includes, but is not limited to: software, graphics, record drawings, database(s), application of programming code, station copies, and documentation.

SECTION 25 10 10.00 24 Rev 1 Page 17 October 26, 2020

2.1.5 General Requirements

Provide components that meet the following requirements:

a. Portions of the data communications equipment system installed in unconditioned spaces shall operate properly in an environment with ambient temperatures between +32 and 120 degrees F and ambient relative humidity between 10 percent and 90 percent noncondensing.

Special temperature and/or humidity requirements for specific equipment is provided in Part 2 of this Specification.

b. Components shall accept 100 to 125 volts AC (Vac), 60 Hz, single phase, three wire with a three-pronged, dedicated circuit outlet or be provided with a transformer to meet the component's power requirements. The only exception to this are products in a SCADA or substation environment in which power can be supplied at direct current. The requirement for devices to unplug remains.

c. The equipment shall meet the requirements of NFPA 70 , UL 60950 , NFPA 262 , FCC EMC, and FCC Part 15 .

2.1.6 Nameplates

Nameplates shall be laminated plastic and shall identify the function, network address, if applicable, and identifier of the device. Laminated plastic shall be at least 0.125 inch thick, white with black center core.

Nameplates shall be a minimum of 1 by 3 inch with minimum 0.25 inch high engraved block lettering.

2.1.7 Product Data Sheets

For all products (equipment) specified in PART 2 and supplied under this contract, submit copies of all manufacturer catalog cuts and specification sheets to indicate conformance to product requirements.

2.2 MANAGED UMCS ETHERNET SWITCH

2.2.1 General

Provide Cisco WS-C3850-245-S managed Ethernet switches. Notwithstanding any other provision of this contract, no other product will be acceptable. Provide with the following features:

a. Configurable session timeouts for each service such as (but not limited to) SSH, Telnet, TFTP, and Web console sessions

b. Multi-level user passwords; support authentication for console access

c. SSH version2/SSL (128-bit encryption) connections

d. Support SNMPv3 with SHA Authentication Protocol and AES Privacy

e. Support SNMPv3 with SHA Authentication Protocol and AES Privacy

f. Support enabling/disabling of ports

g. Support MAC based port security

h. Support VLAN (802.1Q) to segregate and secure network traffic

i. Support RADIUS centralized password management utilizing AAA authentication

j. Console timeout must be configurable

k. FIPS 140-2 compliant (all four levels)

l. Support multiple NTP server to synchronize time

m. Compatible with network performance monitoring; can tie into a

SECTION 25 10 10.00 24 Rev 1 Page 18 October 26, 2020 security incident event management system (SIEM)

n. Configurable login banner

o. 56-bit encryption

p. Ability to create and rename local accounts

q. Create SNMP accounts separate from local accounts

r. Have integral power plug and cord.

SOHO or SMB class switches are prohibited.

Provide five year manufacturer's warranty (ethernet switch).

2.2.2 Software

Operating System Software shall allow plug and play operation and have automatic learning, negotiation and crossover detection and shall support MSTP 902.1Q-2005, RSTP (802.1w) and Enhanced Rapid Spanning Tree network fault recover (<5ms), SNMPv3 SHA Authentication Protocol, AES Privacy Protocol, Quality of Service (802.1p) for real time traffic, VLAN (802.1Q) with double tagging and GVRP support, Link aggregation (802.3ad), IGMP Snooping for multicast filtering, and provide port configuration, status, statistics, mirroring, and security.

2.2.3 Ports

Ports shall be non-blocking, store and forward switching, with long haul optics allow Gigabit distance up to 70km and multiple connector types.

Gigabit fiber ports shall be configured for small form-factor pluggable (SFP), and the Contractor shall provide an SFP transceiver for each SFP port.

Fiber ports for all planned connections can be in a fixed configuration.

2.2.4 Types of Managed UMCS Switches

2.2.4.1 Switches serving a Substation

Switch shall be ruggedized to support immunity to EMI and heavy electrical surges and the temperature and humidity environment commonly found in substation installations. Specifically switches shall comply with the following industry standards: IEEE 1613 Class 2 (electric utility substations) and IEC 61850-3 (electric utility substations).

2.2.4.2 Switches Located in Unconditioned Enclosures in Ambient Conditions

Switch shall be ruggedized to withstand -40 to 125 degrees Fahrenheit operating temperatures.

2.2.4.3 UMCS Transport Switch

Switch shall have trunk port connections at 1000 megabits per second (MPS) or greater.

Spare ports:

a. Provide enough ports to support a total of 25% of the ports to be unused, or "spare", at the conclusion of the project.

b. Two of the spare ports provided above shall be RJ-45 copper connections capable of speeds 100 MPS or greater, one of which is to

SECTION 25 10 10.00 24 Rev 1 Page 19 October 26, 2020 be dedicated to technician laptop access.

c. The remaining spare ports must be a user-replaceable SFP module that supports fiber and copper transceivers capable of 1000 MPS or greater. If the prevailing fiber media to the location is limited to slower speeds, due to distance or other conditions, 100 MPS are permissible with prior approval of NAVFAC NW CIO.

d. At least two of the remaining spare ports in "c" above shall be populated with the appropriate SFP transceiver for use with 1000LX SMF

LC.

2.2.4.4 UMCS Access Switch

Switch shall have trunk port connections at 1000 megabits per second (MPS) or greater.

Switch shall have minimum of six (6) RJ-45 copper ports capable of speeds 100 MPS or greater.

Spare ports:

a. Provide enough ports to support a total of 20% of the ports to be unused, or "spare", at the conclusion of the project.

b. Two of the spare ports provided above shall be RJ-45 copper connections capable of speeds 100 MPS or greater, one of which is to be dedicated to technician laptop access.

2.3 CONTROL HARDWARE

2.3.1 Control Protocol Gateways

The Control Protocol Gateway shall perform bi-directional protocol translation between Fox protocol and one of the following protocols:

CEA-709.1-D , ASHRAE 135, Modbus, and OPC DA.

a. All software required for gateway configuration shall be provided and licensed to the Government.

b. Gateways shall retain their configuration after a power loss of an indefinite time, and shall automatically return to their pre-power loss state once power is restored.

c. Gateways shall, in addition, meet all requirements specified (in the following subparagraphs) for each of the two protocols it translates.

2.3.1.1 Gateway for CEA-709.1

In addition to the requirements for all gateways, Gateways that use CEA-709.1-D shall meet the following requirements:

a. It shall allow bi-directional mapping of data in the Gateway to Standard Network Variable Types (SNVTs) according to the LonMark SNVT List .

b. Gateways shall not communicate CEA-709.1-D over an IP network.

c. It shall allow of its standard network variables (SNVTs) and support

SECTION 25 10 10.00 24 Rev 1 Page 20 October 26, 2020 transmitting data using the "min, max, and delta" (throttling and heartbeat) methodology.

d. It shall provide the ability to label SNVTs.

e. It shall supply a LonMark external interface file (XIF) as defined in the LonMark XIF Guide for use with LNS tools and utilities.

f. It shall provide a configurable self-documenting string.

2.3.1.2 Gateway for ASHRAE 135

In addition to the requirements for all gateways, Gateways that use ASHRAE 135 shall meet the following requirements:

a. It shall allow bi-directional mapping of data in the Gateway to Standard Objects as defined in ASHRAE 135.

b. All ASHRAE 135 Objects shall have a configurable Object_Name Property.

c. It shall be BTL Listed.

d. Gateways shall not communicate ASHRAE 135 over an IP network.

e. Gateways communicating ASHRAE 135 to a field control systems shall support the DS-RP-A (Data Sharing–Read Property–A) BIBB and the DS-WP-A (Data Sharing–Write Property–A) BIBB.

2.3.1.3 Gateway for Modbus

In addition to the requirements for all gateways, Gateways that use Modbus shall allow bi-directional mapping of data in the Gateway to Modbus registers using the four standard Modbus register types (Discrete Input, Coil, Input Register, and Holding Register). Gateways communicating Modbus to the M&C Software shall communicate via Modbus over TCP/IP.

2.3.1.4 Gateway for OPC

In addition to the requirements for all gateways, Gateways that use OPC DA shall allow bi-directional mapping of data in the Gateway using OPC DA tags and shall communicate over an IP network in accordance with OPC DA.

2.3.1.5 Gateway for DNP3

In addition to the requirements for all gateways, Gateways that use DNP3 shall allow bi-directional mapping of data in the Gateway to DNP3 object groups and variations as defined by IEEE 1815 . Gateways communicating DNP3 over an IP network shall communicate in accordance with the LAN/WAN Networking volume of IEEE 1815 .

2.3.1.6 Niagara Framework Supervisory Controller (Gateway)

Niagara Framework Supervisory Controller Hardware shall:

a. be direct digital control hardware.

b. have an unrestricted interoperability license and its Niagara Compatibility Statement (NiCS) shall follow the Tridium Open NiCS Specification.

SECTION 25 10 10.00 24 Rev 1 Page 21 October 26, 2020

c. manage communications between a field control network and the Niagara Framework Monitoring and Control Software and between itself and other Niagara Framework Supervisory Controller. Niagara Framework Supervisory Controller Hardware shall use Fox protocol for communication with other Niagara Framework Components.

d. be fully programmable using the Niagara Framework Engineering Tool and shall support the following:

(1) Time synchronization, Calendar, and Scheduling using Niagara Scheduling Objects

(2) Alarm generation and routing using the Niagara Alarm Service

(3) Trending using the Niagara History Service and Niagara Trend Log Objects

(4) Integration of field control networks using the Niagara Framework Engineering Tool

(5) Configuration of integrated field control system using the Niagara Framework Engineering Tool

e. meet the following minimum hardware requirements:

(1) Two 10/100 Mbps Ethernet Ports

(2) One port compatible with the field control system to be integrated using this product.

(3) Central Processing Unit of 1000 Mhz or higher.

(4) Embedded QNX operating system.

(5) 1 GB of SDRAM.

(6) Capacity: Under normal working conditions the gateway's central processing unit processor usage percentage shall not exceed 80% and memory usage should not exceed 85% of total memory.

(7) Two RS-485 serial ports.

(8) One RS-232 serial port

(9) One NDIO port

(10) Two communication card option slots

(11) Niagara 4.1 (or later) compatible with current Niagara Supervisor version on NW regional servers.

f. provide access to field control network data and supervisory functions via web interface and support a minimum of 16 simultaneous users

g. Required Data Storage

(1) Store data at 15 minute intervals for all hardware input data and output commands for digital outputs for a minimum of 36 hours.

SECTION 25 10 10.00 24 Rev 1 Page 22 October 26, 2020

See Appendix E for trending data specifics.

(2) All stored data shall be automatically…