Amendment 0004 - P995 Spec 25 10 10.pdf

P-995 Composite Repair Facility 24 December 2025 MCAS Cherry Point, NC

SECTION 25 10 10

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

02/19, CHG 1: 05/21

PART 1 GENERAL

1.1 SUMMARY

Provide a Utility Monitoring and Control System (UMCS) which performs supervisory monitoring and supervisory control of base-wide building control systems and utility control systems using one or more of:

ASHRAE 135 (BACnet), or OPC DA as indicated and shown. Integrate field control systems installed per Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS and other field control systems to the UMCS as specified.

1.1.1 System Requirements

Provide a UMCS and integration of control systems to the UMCS as specified and indicated, and in accordance with the following characteristics::

1.1.1.1 General System Requirements

a. The system performs supervisory monitoring and control functions including but not limited to Scheduling, Alarm Handling, Trending, Overrides, Report Generation, and Electrical Demand Limiting as specified.

b. The system includes a Graphical User Interface which allows for graphical navigation between systems, graphical representations of systems, access to real-time data for systems, ability to override points in a system, and access to all supervisory monitoring and control functions.

c. All software used by the UMCS and all software used to install and configure the UMCS is licensed to and delivered to the installation.

d. All necessary documentation, configuration information, configuration tools, programs, drivers, and other software is licensed to and otherwise remains 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 must not require periodic fees and must be valid in perpetuity.

e. 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.

f. The UMCS interfaces directly to ASHRAE 135, and OPC DA field control systems as specified and may interface to field control systems using other protocols via an M&C Software protocol driver or a Gateway.

g. 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

SECTION 25 10 10 Page 1 REVISED Amendment 003 - 17 APR 2026 capacity requirements as specified.

1.1.1.2 BACnet Requirements

a. The UMCS must communicate using ASHRAE 135 Annex J over the Government furnished IP network as specified.

b. All communication between the UMCS and ASHRAE 135 field control networks must be via the ASHRAE 135 protocol over the IP network.

c. All communication between the M&C Software and the field control system devices must be via standard ASHRAE 135 services other than PrivateTransfer and ConfirmedPrivateTransfer except as follows:

(1) PrivateTransfer and ConfirmedPrivateTransfer may be used for device configuration and device programming.

(2) PrivateTransfer and ConfirmedPrivateTransfer may be used for communication between the M&C Software and the field control system if and only if both the M&C Software and the field control system devices automatically (without requiring reconfiguration) revert to the use of other standard ASHRAE 135 services when one of the components is modified or replaced.

1.1.1.3 OPC Requirements

The UMCS must communicate using OPC DA over the Government furnished IP network as shown and specified.

1.1.2 Symbols, Definition and Abbreviations

Use symbols, definitions, and engineering unit abbreviations indicated in the contract drawings for displays, submittals and reports. For symbols, definitions and abbreviations not in the contract drawings use terms conforming at a minimum to IEEE Stds Dictionary and the ASHRAE FUN IP , as applicable.

1.1.3 System Units and Accuracy

Use English (inch-pound) units for displays, print-outs and calculations.

Perform calculations with an accuracy of at least three significant figures. For displays and printouts present values to at least three significant figures.

1.1.4 Data Packages/Submittals 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 must be delivered strictly in accordance with the CONTRACT CLAUSES and in accordance with the Contract Data Requirements List, DD Form 1423. Data delivered must 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 must contain no proprietary information and must be delivered with unrestricted rights.

SECTION 25 10 10 Page 2

1.2 RELATED SECTIONS

Cybersecurity requirements related to this Section are specified in a separate cybersecurity specification derived from UFGS 25 05 11. Section

25 05 11.02 CYBERSECURITY FOR HVAC/DDC FACILITY-RELATED CONTROL SYSTEM

specifies cybersecurity requirements related to this Section.

1.3 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 (2024; INT 1-3 2025; Errata 1 2025; INT 4-6 2025; Addenda CU 2025) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASHRAE FUN IP (2025) Fundamentals Handbook, I-P Edition

CONSUMER ELECTRONICS ASSOCIATION (CEA)

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

CEA-852-C (2014) Tunneling Device Area Network Protocols Over Internet Protocol Channels

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

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

IEEE Stds Dictionary (2009) IEEE Standards Dictionary: Glossary of Terms & Definitions

LONMARK INTERNATIONAL (LonMark)

LonMark Interoperability Guide (2005) LonMark Application-Layer Interoperability Guide and LonMark Layer 1-6 Interoperability Guide; Version 3.4

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 Protocol (2012) Modbus Application Protocol Specification; Version 1.1b3

MODBUS TCP/IP (2006) Modbus Messaging on TCP/IP Implementation Guide; Version V1.0b

SECTION 25 10 10 Page 3

NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)

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

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2026) National Electrical Code

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

OPC FOUNDATION (OPC)

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

TELECOMMUNICATIONS INDUSTRY ASSOCIATION (TIA)

ANSI/TIA-568.1 (2020e) Commercial Building Telecommunications Infrastructure Standard

ANSI/TIA-606 (2021d) Administration Standard for Telecommunications Infrastructure

ANSI/TIA-607 (2019d) Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises

U.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)

FCC EMC (2002) FCC Electromagnetic Compliance Requirements

FCC Part 15 Radio Frequency Devices (47 CFR 15)

UL SOLUTIONS (UL)

UL 1778 (2014; Reprint Apr 2023) UL Standard for Safety Uninterruptible Power Systems

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

1.4 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 indicating to which protocol the term and definition applies. Inclusion of protocol-specific definitions does not create a requirement to support that protocol, nor does it relax any requirements to support specific protocols as indicated elsewhere in this section.

These definitions include terms specific to LonWorks. While new UMCS Front Ends based on LonWorks are not permitted, these definitions are retained for reference as part of an integration project to an existing LonWorks based UMCS.

SECTION 25 10 10 Page 4

1.4.1 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.4.2 Alarm Handling

see Alarm Routing

1.4.3 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.4.4 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.4.5 BACnet Advanced Application Controller (B-AAC)(BACnet)

A hardware device BTL Listed as a B-AAC. A control device which contains BIBBs in support of scheduling and alarming but otherwise has limited resources relative to a B-BC. It may be intended for specific applications and supports some degree of programmability.

1.4.6 BACnet Advanced Operator Workstation (B-AWS)(BACnet)

Monitoring and Control (M&C) Software BTL Listed as an Advanced Operator Workstation and includes the ability to manage scheduling, alarming and trending in an open manner. The B-AWS is the advanced operator's window into a BACnet system. It is primarily used to monitor the performance of a system and to modify parameters that affect the operation of a system.

1.4.7 BACnet Application Specific Controller (B-ASC)(BACnet)

A hardware device BTL Listed as a B-ASC. A controller with limited resources relative to a B-AAC. It is intended for use in a specific application and supports limited programmability.

1.4.8 BACnet Building Controller (B-BC)(BACnet)

A hardware device BTL Listed as a B-BC. A general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks including control and monitoring via direct digital control (DDC) of specific systems and data storage for trend information, time schedules, and alarm data. Like the other BTL Listed controller types (B-AAC, B-ASC etc.) a B-BC device is required to support the server ("B") side of the ReadProperty and WriteProperty services, but unlike the other controller types it is also required to support the client ("A") side of these services. Communication between controllers requires that one of them support the client side and the other support the server side, so a B-BC is often used when communication between

SECTION 25 10 10 Page 5 controllers is needed.

1.4.9 BACnet Internetwork (BACnet)

Two or more BACnet networks connected with BACnet routers. In a BACnet Internetwork, there exists only one message path between devices.

1.4.10 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.

1.4.11 BACnet Operator Display (B-OD)(BACnet)

A hardware device BTL Listed as a B-OD. A basic operator interface with limited capabilities relative to a B-OWS. It is not intended to perform direct digital control. The B-OD profile could be used for wall-mounted LCD devices, displays affixed to BACnet devices; hand-held terminals or other very simple user interfaces.

1.4.12 BACnet Operator Workstation (B-OWS)(BACnet)

Monitoring and Control (M&C) Software BTL Listed as a B-OWS. An operator interface with limited capabilities relative to a B-AWS. The B-OWS is used for monitoring and basic control of a system, but differs from a B-AWS in that it does not support configuration activities, nor does it provide advanced troubleshooting capabilities.

1.4.13 BACnet Smart Actuator (B-SA)(BACnet)

A hardware device BTL Listed as a B-SA. A simple control output device with limited resources; it is intended for specific applications.

1.4.14 BACnet Smart Sensor (B-SS)(BACnet)

A hardware device BTL Listed as a B-SS. A simple sensing device with very limited resources.

1.4.15 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.4.16 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".

SECTION 25 10 10 Page 6

1.4.17 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.4.18 Binding (LonWorks)

The act of establishing communications between CEA-709.1-D devices by associating the output of a device to the input of another so that information is automatically (and regularly) sent without being requested by the recipient.

1.4.19 Broadcast

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

1.4.20 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.4.21 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.4.22 Commandable (BACnet)

A point (Object) is commandable if its Present_Value Property is writable and it supports the optional Priority_Array Property. This functionality is useful for Overrides.

1.4.23 Control Logic Diagram

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

1.4.24 Device Object (BACnet)

Every BACnet device requires one Device Object, whose properties represent the network visible properties of that device. Every Device Object requires a unique Object_Identifier number on the BACnet Internetwork.

This number is often referred to as the device instance or device ID.

1.4.25 Field Point Of Connection (FPOC)

The FPOC is part of the UMCS IP network and acts as the point of connection between the UMCS IP Network and the field control IP network.

The FPOC is an IT device such as a switch, IP router, or firewall, typically managed by the site IT staff. (Note that the field control IP network may consist of a single IP device, or that integration may require installation of a field control network IP device.)

SECTION 25 10 10 Page 7

1.4.26 Field Control Network

The network used by a field control system.

1.4.27 Field Control System (FCS)

A building control system or utility control system.

1.4.28 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.4.29 Internetwork (BACnet)

See BACnet Internetwork.

1.4.30 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.

1.4.31 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.4.32 Network (BACnet)

In BACnet, a portion of the control internetwork consisting of one or more segments of the same media connected by repeaters. Networks are separated by routers.

1.4.33 Object (BACnet)

A BACnet Object. The concept of organizing BACnet information into standard components with various associated Properties. Examples include Analog Input objects and Binary Output objects.

1.4.34 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 Utility Monitoring and Control System (UMCS) Monitoring and Control (M&C) Software. Note that this definition is not standard throughout industry.

1.4.35 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

SECTION 25 10 10 Page 8 points or other calculated points. Calculated points are sometimes called virtual points or internal points.

1.4.36 Point, Network

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

1.4.37 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.4.38 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.4.39 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.4.40 Repeater

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

1.4.41 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.4.42 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 BACnet MS/TP segment is limited to 32 devices.

1.4.43 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.4.44 Standard BACnet Object/Property/Service (BACnet)

BACnet Objects, Properties, or Services that are standard Objects, SECTION 25 10 10 Page 9

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.4.45 Supervisory Controller

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.

1.4.46 Supervisory Gateway

A device that is both a supervisory controller and a gateway.

1.4.47 UMCS Network

An IP network connecting multiple field control systems to the Monitoring and Control Software using one or more of: LonWorks ( CEA-709.1-D and CEA-852-C ), BACnet ( ASHRAE 135 Annex J), MODBUS Protocol , MODBUS TCP/IP or

OPC DA.

1.4.48 Utility Control System (UCS)

One type of field control system. Used for control of utility systems such as an electrical substation, sanitary sewer lift station, water pump station, etc. Building controls are excluded from a UCS, however it is possible to have a Utility Control System and a Building Control System in the same facility, and for those systems to share components such as the FPOC. A UCS may include its own local front-end.

1.5 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES and TABLE 1: PROJECT SEQUENCING:

SD-02 Shop Drawings

UMCS Contractor Design Drawings ; G

Draft As-Built Drawings ; G

Final As-Built Drawings ; G

SD-03 Product Data

Product Data Sheets ; G

Enclosure Keys ; G

SD-05 Design Data

UMCS IP Network Bandwidth Usage Estimate ; G

SECTION 25 10 10 Page 10

SD-06 Test Reports

Pre-Construction QC Checklist ; G

Post-Construction QC Checklist ; G

Start-Up and Start-Up Testing Report ; G

PVT Phase I Procedures ; G

PVT Phase I Report ; G

PVT Phase II Report ; G

SD-10 Operation and Maintenance Data

Operation and Maintenance (O&M) Instructions ; G

Preventive Maintenance Work Plan ; G

Basic Training Documentation ; G

Advanced Training Documentation ; G

Refresher Training Documentation ; G

SD-11 Closeout Submittals

Closeout QC Checklist ; G

1.6 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).

1.6.1 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 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.

1.6.2 Sequencing for Activities

The sequencing specified for activities indicates the earliest the activity may begin.

1.6.3 Abbreviations

In TABLE I the abbreviation AAO is used for 'after approval of' and 'ACO'

SECTION 25 10 10 Page 11 is used for 'after completion of'.

TABLE I. PROJECT SEQUENCING

ITEM TYPE DESCRIPTION SEQUENCING

(START OF ACTIVITY or

DEADLINE FOR SUBMITTAL)

1 Acceptance of Factory Test Report

2 S Design Drawings After #1

3 S Product Data Sheets After #1

4 S UMCS IP Network Bandwidth Usage Estimate

After #1

5 S Pre-construction QC Checklist After #1

6 E Install UMCS AAO #2 thru #6

7 E Start-Up and Start-Up Testing ACO #7

8 S Post-Construction QC Checklist ACO #8

9 S Computer Software ACO #8

10 S Start-Up and Start-Up Testing Report ACO #8

11 S Draft As-Built Drawings ACO #8

12 S PVT Phase I Procedures Before scheduled start of #14 and

AAO #11

13 E PVT Phase I AAO #13 and #12

14 S PVT Phase I Report ACO #14

15 S Preventive Maintenance Work Plan AAO #11

16 S O&M Instructions AAO #11

17 S Basic Training Documentation AAO #11 and before scheduled start of #19

SECTION 25 10 10 Page 12

TABLE I. PROJECT SEQUENCING

ITEM TYPE DESCRIPTION SEQUENCING

(START OF ACTIVITY or

DEADLINE FOR SUBMITTAL)

18 E Basic Training (PVT Phase II) AAO #16, #17 and #18

19 S PVT Phase II Report ACO #19

20 S Final As-Built Drawings AAO #20

21 S Advanced Training Documentation Before schedule start of #23 and

AAO #18

22 E Advanced Training ACO #19, AAO #22, and no later than 60 days ACO #19

23 S Refresher Training Documentation Before #25 and AAO #18 and #22

24 E Refresher Training ACO #19 and AAO #24

26 S Closeout QC Checklist ACO #23

1.7 QUALITY CONTROL (QC) CHECKLISTS

The Contractor's Chief Quality Control (QC) Representative must complete the QC Checklist in APPENDIX A, and must submit the Pre-Construction QC Checklist , Post-Construction QC Checklist and Closeout QC Checklist as specified. The QC Representative must verify each item in the Checklist and initial in the provided area to indicate that the requirement has been met. The QC Representative must sign and date the Checklist prior to submission to the Government.

The APPENDIX A QC Checklist is available as an editable file at https://www.wbdg.org/dod/ufgs/ufgs-25-10-10 .

1.7.1 Pre-Construction QC Checklist

Complete items indicated as Pre-Construction QC Checklist items in the QC Checklist. Submit four copies of the Pre-Construction QC Checklist.

1.7.2 Post-Construction QC Checklist

Complete items indicated as Post-Construction QC Checklist items in the QC Checklist. Submit four copies of the Pre-Construction QC Checklist.

1.7.3 Closeout QC Checklist

Complete items indicated as Closeout QC Checklist items in the QC

SECTION 25 10 10 Page 13

Checklist. Submit four copies of the Pre-Construction QC Checklist.

1.8 OPERATION AND MAINTENANCE (O&M) INSTRUCTIONS

Provide UMCS Operation and Maintenance Instructions which include:

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

b. Final As-Built drawings.

c. Routine maintenance checklist, arranged in a columnar format: The first column listing all installed devices, the second column stating the maintenance activity or stating that no maintenance required, the third column stating the frequency of the maintenance activity, and the fourth column providing any 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. Performance Verification Test (PVT) Procedures and Reports.

Submit four bound O&M Instructions and four copies of the Instructions in PDF format on optical disc. Index and tab bound instructions. Submit instructions in PDF form as a single PDF file, or as multiple PDF files with a PDF file table of contents containing links to the other files.

O&M Instructions may be submitted as a Technical Data Package.

PART 2 PRODUCTS

2.1 EQUIPMENT REQUIREMENTS

2.1.1 Product Certifications

For computing devices, as defined in FCC Part 15 , supplied as part of the UMCS provide devices which are certified to comply with the requirements of Class B computing devices.

2.1.2 Product Sourcing

For units of the same type of equipment, provide products of a single manufacturer. For each major component of equipment provide equipment with the manufacturer's name and the model and serial number in a conspicuous place. For materials and equipment, provide new standard unmodified products of a manufacturer regularly engaged in the manufacturing of such products.

2.1.3 General Requirements

Provide components that meet the following requirements:

a. Portions of the data communications equipment system installed in unconditioned spaces must 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.

b. Components must accept 100 to 125 volts AC (Vac), 60 Hz, single phase, three wire with a three-pronged, dedicated circuit outlet or be

SECTION 25 10 10 Page 14 provided with a transformer to meet the component's power requirements.

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

2.1.4 Nameplates

Provide nameplates of laminated plastic identifying the function, network address, if applicable, and identifier of the device. Laminated plastic must be at least 0.125 inch thick, white with black center core.

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

2.1.5 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. For Monitoring and Control (M&C) Software also include the PICS verifying BTL Listing as a B-AWS.

2.2 CONTROL HARDWARE

2.2.1 Control Protocol Routers

2.2.1.1 BACnet/IP Router

Provide BACnet/IP Routers which perform layer 3 routing of ASHRAE 135 packets over an IP network in accordance with ASHRAE 135 Annex J and Clause 6. The router must provide the appropriate connection to the IP network and connections to a ASHRAE 135 MS/TP network. Devices used as BACnet/IP Routers must be BTL Listed and must support the Network Management-Router Configuration-B (NM-RC-B) BIBB.

2.2.2 Monitoring and Control (M&C) Controller Hardware

Provide Monitoring and Control (M&C) Controller Hardware which is a microprocessor-based direct digital control hardware and which communicates over the UMCS IP network using one of:

a. CEA-709.1-D in accordance with CEA-852-C and using only Standard Network Variable Types (SNVTs) as defined by the LonMark SNVT List.

b. ASHRAE 135 in accordance with ASHRAE 135 Annex J and using only Standard ASHRAE 135 services.

Monitoring and Control (M&C) Controller Hardware must either meet the requirements of the LonMark Interoperability Guide or be BTL Listed.

2.2.3 BACnet Supervisory Controller Hardware

Provide BACnet Supervisory Controller Hardware which is direct digital control hardware and which:

a. is BTL Listed

b. communicates using ASHRAE 135 over an IP network in accordance with ASHRAE 135 Annex J

SECTION 25 10 10 Page 15

c. has a configurable Object_Name Property

d. supports the following BIBBS

(1) DS-RP-B (Data Sharing Read Property B) BIBB for Objects requiring read access from the M&C Software

(2) DS-WP-B (Data Sharing Write Property B) BIBB for Objects requiring write access from the M&C Software.

(3) SCHED-E-B (Scheduling-External-B)

(4) AE-N-I-B (Alarm and Event-Notification Internal-B)

(5) AE-ACK-B (Alarm and Event-ACK-B)

(6) T-VMT-I-B (Trending-Viewing and Modifying Trends-Internal-B)

(7) T-ATR-B (Trending-Automated Trend Retrieval-B)

e. has a Writable Recipient_List Property of the Notification Class Object

2.2.4 Control Protocol Gateways

Provide Control Protocol Gateways which perform bi-directional protocol translation between two of the following protocols, or between one of the following protocols and another protocol: CEA-709.1-D , ASHRAE 135, MODBUS Protocol , MODBUS TCP/IP, and OPC DA. Provide Control Protocol Gateways which also meet the following requirements.

a. Gateways must have two or more separate network connections, each appropriate for the protocol and media used. A single network connection must not be used for both protocols.

b. Gateways must be capable of being installed, configured and programmed through the use of instructions in the manual supplied by the Contractor.

c. Provide and license to the Government all software required for gateway configuration.

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

e. Gateways must provide capacity for mapping all required points as indicated plus an additional 15 percent between the two protocols it uses.

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

2.2.4.1 Gateway for CEA-709.1

For a gateways using CEA-709.1-D provide gateways which meet the following requirements in addition to the requirements for all gateways:

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

SECTION 25 10 10 Page 16

LonMark SNVT List .

b. Gateways communicating CEA-709.1-D over an IP network must communicate in accordance with CEA-852-C .

c. It must allow of its standard network variables (SNVTs) and support transmitting data using the "min, max, and delta" (throttling and heartbeat) methodology.

d. It must provide the ability to label SNVTs.

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

f. It must have a "service pin" which, when pressed, will cause the Gateway to broadcast its 48-bit NodeID and ProgramID over the network.

g. It must provide a configurable self-documenting string.

2.2.4.2 Gateway for ASHRAE 135

For gateways using ASHRAE 135 provide gateways which meets the following requirements in addition to the requirements for all gateways:

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

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

c. It must be BTL Listed.

d. Gateways communicating ASHRAE 135 over an IP network must communicate in accordance with ASHRAE 135 Annex J.

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

f. Gateways communicating ASHRAE 135 to the M&C Software or to a BACnet Supervisory Controller must support the DS-RP-B (Data Sharing Read Property B) BIBB for Objects requiring read access from the M&C Software and the DS-WP-B (Data Sharing Write Property B) BIBB for Objects requiring write access from the M&C Software

2.2.4.3 Gateway for OPC

For gateways that use OPC DA, provide gateways that meet the requirements specified for all gateways and which allow bi-directional mapping of data in the Gateway using OPC DA tags and which communicate over an IP network in accordance with OPC DA.

2.3 COMPUTER HARDWARE

For computer hardware furnished under this specification provide standard products of a single manufacturer which advertises service in all 48 contiguous states, and provide only model currently in production. Except for PCI-E cards installed into expansion slots provided in a desktop or server computer in order to meet the requirements of this specification, do not modify computer hardware from the manufacturer configuration.

SECTION 25 10 10 Page 17

2.3.1 Server Hardware

Computer Server Hardware (server) will be furnished by the Government

2.3.2 Workstation Hardware (Desktop and Laptop)

Provide a standard desktop computer or a laptop meeting the following minimum requirements for the Computer Workstation Hardware (workstation) as indicated.

2.4 UNINTERRUPTIBLE POWER SUPPLY (UPS)

Provide uninterruptible power supplies (UPS) as self contained devices suitable for installation and operation at the location of Server and Workstation hardware and sized to provide a minimum of 20 minutes of operation of the connected hardware. Equipment connected to the UPS must not be affected in any manner by a power outage of a duration less than the rated capacity of the UPS. Provide the UPS complete with all necessary power supplies, transformers, batteries, and accessories.

Provide UPS which include visual indication of normal power operation, UPS operation, abnormal operation and visual and audible indication of AC input loss and low battery power. Provide UL 1778 approved UPS. UPS powering Server Hardware must notify the server via USB interface of impending battery failure.

2.5 RACKS AND ENCLOSURES

2.5.1 Enclosures

Enclosures supplied as an integral (pre-packaged) part of another product are acceptable. Provide two Enclosure Keys for each lockable enclosure on a single ring per enclosure with a tag identifying the enclosure the keys operate. Provide enclosures meeting the following minimum requirements:

2.5.1.1 Outdoors

For enclosures located outdoors, provide enclosures meeting NEMA 250 requirements per contract documents .

2.5.1.2 Mechanical and Electrical Rooms

For enclosures located in mechanical or electrical rooms, provide enclosures meeting NEMA 250 requirements per contract documents .

2.5.1.3 Other Locations

For enclosures in other locations including but not limited to occupied spaces, above ceilings, and in plenum returns, provide enclosures meeting NEMA 250 Type 1 requirements.

2.5.2 Equipment Racks

Provide standard 19 inch equipment racks compatible with the electronic equipment provided. Racks must be either aluminum or steel with bolted or welded construction. Steel equipment racks must be painted with a flame-retardant paint. Guard rails must be included with each equipment rack and have a copper grounding bar installed and grounded to the earth.

SECTION 25 10 10 Page 18

PART 3 EXECUTION

3.1 DRAWINGS AND CALCULATIONS

3.1.1 UMCS IP Network Bandwidth Usage Estimate

Provide a UMCS IP Network Bandwidth Usage Estimate for a small, medium or large systems. In this estimate account for field control systems using all M&C required protocols and the integration of field control system via gateways. Define all assumptions used to create the estimate, including but not limited to: trending, fast trends for commissioning, schedules, alarms, display of system graphics and load shedding.

Submit Four copies of the UMCS IP Network Bandwidth Usage Estimate.

3.1.2 UMCS Contractor Design Drawings

Revise and update the Contract Drawings to include details of the system design and all hardware components, including contractor provided and Government furnished components. Details to be shown on the Design Drawing include:

a. The logical structure of the network, including but not limited to the location of all Control Hardware (including but not limited to each BACnet Supervisory Controller, Control Protocol Gateway, Control Protocol Router, and Monitoring and Control (M&C) Controller).

b. Manufacturer and model number for each piece of Computer Hardware and Control Hardware.

c. Physical location for each piece of Computer Hardware and Control Hardware.

d. Version and service pack number for all software and for all Control Hardware firmware.

Submit UMCS Contractor Design Drawings as a single complete package: 3 hard copies and 3 copies on CDROM. Submit hardcopy drawings on ISO A1 34 by 22 inchesorA3 17 by 11 inches sheets, and electronic drawings in both PDF and AutoCAD format.

3.1.3 As-Built Drawings

Prepare draft as-built drawings consisting of Points Schedule drawings for the entire UMCS, including Points Schedules for each Gateway, and an updated Design Drawing including details of the actual installed system as it is at the conclusion of Start-Up and Start-Up Testing. Provide As-Built Drawings which include details of all hardware components, including contractor provided and Government furnished components. In addition to the details shown in the design drawings, the as-built drawing must include:

a. IP address(es) and Ethernet MAC address(es) as applicable for each piece of Control Hardware (including but not limited to each BACnet Supervisory Controller, Control Protocol Gateway, Control Protocol Router, and Monitoring and Control (M&C) Controller).

b. IP address and Ethernet MAC address for each computer server, SECTION 25 10 10 Page 19 workstation, and networked printer.

c. Network identifier (name) for each printer, computer server and computer workstation.

d. List of ports, protocols and network services for each device connected to an IP network.

e. Network Addresses: ASHRAE 135 address and Object_ID of the Device Object for all Control Hardware using ASHRAE 135.

Prepare Draft As-Built Drawings upon the completion of Start-Up and Start-Up Testing and Final As-Built Drawings upon completion of PVT Phase

II.

3.1.3.1 Draft As-Built Drawings

Submit Draft As-Built Drawings as a single complete package: 3 hard copies and 3 copies on CDROM. Submit hardcopy drawings must on ISO A1 34 by 22 inchesorA3 17 by 11 inches sheets, and electronic drawings in both PDF and AutoCAD format.

3.1.3.2 Final As-Built Drawings

Submit Final As-Built Drawings as a single complete package: 3 hard copies and 3 copies on CDROM. Submit hardcopy drawings on ISO A1 34 by 22 inchesorA3 17 by 11 inches sheets, and electronic drawings in both PDF and AutoCAD format.

3.2 INSTALLATION REQUIREMENTS

3.2.1 General

Install system components as shown and specified and in accordance with the manufacturer's instructions and provide necessary interconnections, services, and adjustments required for a complete and operable system.

Install communication equipment and cable grounding as necessary to preclude ground loops, noise, and surges from adversely affecting system operation. Install Fiber Optic cables and wiring in exposed areas, including low voltage wiring but not including network cable in telecommunication closets, in metallic raceways or EMT conduit as specified in Section 26 20 00 INTERIOR DISTRIBUTION SYSTEM. Do not install equipment in any space which experiences temperatures or humidity outside of the rated operating range of the equipment.

3.2.2 Isolation, Building Penetrations and Equipment Clearance

Provide dielectric isolation where dissimilar metals are used for connection and support. Make all penetrations through and mounting holes in the building exteriors watertight. Drill or core drill holes in concrete, brick, steel and wood walls with proper equipment. Seal conduits installed through openings with materials which are compatible with existing materials. Seal openings with materials which meet the requirements of NFPA 70 and SECTION 07 84 00 FIRESTOPPING.

3.2.3 Nameplates

Provide Nameplates for all Control Hardware and all Computer Hardware.

Attach Nameplates to the device in a conspicuous location.

SECTION 25 10 10 Page 20

3.3 INSTALLATION OF EQUIPMENT

3.3.1 Wire and Cable Installation

Install system components and appurtenances in accordance with NFPA 70 , manufacturer's instructions and as indicated. Provide necessary interconnections, services, and adjustments required for a complete and operable signal distribution system. Label components in accordance with ANSI/TIA-606 . Firestop Penetrations in fire-rated construction in accordance with Section 07 84 00 FIRESTOPPING. Install conduits, outlets and raceways in accordance with Section 26 20 00 INTERIOR DISTRIBUTION SYSTEM. Install wiring in accordance with ANSI/TIA-568.1 and as specified in Section 26 20 00 INTERIOR DISTRIBUTION SYSTEM. Mark wiring terminal blocks and outlets in accordance with ANSI/TIA-606 . Do not install non-fiber-optic cables in the same cable tray, utility pole compartment, or floor trench compartment with power cables. Properly secure and install neat in appearance cables not installed in conduit or raceways.

3.3.2 Grounding

Install signal distribution system ground in accordance with ANSI/TIA-607 and Section 26 20 00 INTERIOR DISTRIBUTION SYSTEM. Connect equipment racks to the electrical safety ground.

3.3.3 Power-Line Surge Protection

Protect equipment connected to ac circuits must be protected against or withstand power-line surges. Provide equipment protection which meets the requirements of IEEE C62.41 . Do not use fuses for surge protection.

3.3.4 IP Addresses

For all Control Hardware requiring an IP address on the UMCS IP Network, coordinate with the ROICC to obtain IP addresses .

3.3.5 Computer Hardware and Software

3.3.5.1 Hardware Installation

Install Computer Hardware as specified and indicated. Power Computer Servers through a UPS, and install and configure them such that the server automatically undergoes a clean shutdown upon low battery signal from the

UPS.

3.3.5.2 Software Installation

Install software as follows:

c. BACnet Network Browser: Install the BACnet Network Browser software as indicated. Install the BACnet Network Browser on workstation hardware.

e. Monitoring and Control Software: Install the monitoring and control (M&C)software as shown. Except for M&C Software performing Point Calculations or Electrical Peak Demand Limiting, install M&C Software on server hardware. Install M&C Software performing Point Calculations or Electrical Peak Demand Limiting on either server

SECTION 25 10 10 Page 21 hardware or Monitoring and Control (M&C) Controller Hardware. Install M&C Software in a manner consistent with its B-AWS listing such that it provides all functionality of a B-AWS.

Provide sufficient computer hardware and M&C Controller Hardware and install M&C Software to support the number of points required in PART 2 (PRODUCTS), regardless of the number of points integrated under this project specification. Note that meeting this requirement may entail the installation of unused hardware or spare point licenses to accommodate the full number of required points in order to allow for integration of future field control systems.

f. M&C Controller Hardware Configuration Software: Install the M&C Controller Hardware Configuration Software on server hardware.

Where software requires connection to an IP device outside of the UMCS, coordinate with to obtain access to a Government-furnished server to provide the needed functionality. Do not connect to any device outside of the UMCS without explicit permission.

3.3.5.3 Monitoring and Control (M&C) Software Configuration

Configure the Monitoring and Control (M&C) Software as specified, as indicated and as follows:

a. Set up M&C Software user accounts and passwords. Coordinate user accounts, passwords and permissions with the Controls shop supervisor.

b. Change the default password on all accounts. Remove or disable any accounts which do not require authentication (such as guest accounts).

c. Configure e-mail capability to use a Government furnished SMTP server. Coordinate with government for SMTP server information.

d. Disable all ports, protocols, and network services other than those required or specifically permitted by this Section. Services to be disabled include but are not limited to: FTP, Telnet and SSH.

e. Install web server certificate. Coordinate with government to o btain certificate.

3.3.5.4 Control Hardware

Install Control Hardware in a lockable enclosure and as specified.

Configure Control Hardware as specified, as required to meet the functions for which the hardware is used and as follows:

a. Disable all ports, protocols, and network services other than those required or specifically permitted by this Section. Services to be disabled include but are not limited to: FTP, Telnet, SSH, and HTTP.

When disabling of ports, protocols and services is not supported by a product, obtain an exception from this requirement prior to using the product and document non-compliance on the Product Data Sheets and As-Built drawings.

b. Change the default passwords in all Control Hardware which have passwords. Coordinate new passwords with the Controls shop supervisor.

SECTION 25 10 10 Page 22

3.4 INTEGRATION OF FIELD CONTROL SYSTEMS

Fully integrate the field control systems in accordance with the following three step sequence and as specified and shown.

STEP 1: Install and configure Control Hardware as necessary to connect the field control system to the FPOC, which is part of the UMCS IP network, and to provide control protocol translation and supervisory functionality.

STEP 2: Add Field Control System to M&C Software: Perform system discovery, system database merges, or any other actions necessary to allow M&C Software access to the field control system.

STEP 3: Configure M&C Software to provide monitoring and control of the field control system, including but not limited to the creation of system displays and the configuration of scheduling, alarming, and trending.

3.4.1 Integration Step 1: Install Control Hardware

Install Control Hardware as specified at the FPOC location as shown to connect the field control system to the UMCS IP network via the FPOC and, if necessary, to provide control protocol translation and supervisory functionality. Coordinate all connections and other activities related to an FPOC. Depending on the field control system media and protocol this must be accomplished through one of the following:

a. Connect the existing field control network hardware at the FPOC location to the FPOC.

b. Install a Control Protocol Gateway connected to both the field control network and the FPOC.

c. Install a Control Protocol Router connected to both the field control network and the FPOC.

d. Install a Control Protocol Gateway connected to the field control network. Then install a Control Protocol Router connected to both the Control Protocol Gateway and the FPOC.

In addition, for integration of field control systems via ASHRAE 135, also install a BACnet Supervisory Controller as needed to implement scheduling, alarming and trending in the field control system. The BACnet supervisory controller may be the same device as the control protocol gateway or router.

3.4.1.1 Installation of Control Protocol Gateway

If the field control system uses a protocol which is not supported by the M&C Software, install a gateway to…