ATTACHMENT 4 SPECS REPAIR BUILDING 51 FJRP112701 dated 20 July 2022 Vol 4 of 4 444 pages.pdf

North Carolina Air National Guard

Charlotte/Douglas International Airport

145 Airlift Wing

Repair Maintenance Hangar

Building 51

Project Number: FJRP112701

Contract Number: W9133L-16-D-0007

July 20, 2022

Type B3 Submittal

Specifications

Volume 4 of 4

Prepared by

M&H Project No.: 3258000-181469.01

This page intentionally left blank.

NC ANG-CHARLOTTE

FJRP112701

REPAIR MAINTENANCE HANGAR BUILDING 51

TYPE B3 SUBMITTAL - 20 JUL 2022

PROJECT TABLE OF CONTENTS Page 1

PROJECT TABLE OF CONTENTS

VOLUME 1

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 30 00 ADMINISTRATIVE REQUIREMENTS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 33 00A SUBMITTAL REGISTER

01 33 29 SUSTAINABILITY REQUIREMENTS AND REPORTING

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.00 10 QUALITY CONTROL

01 45 35 SPECIAL INSPECTIONS

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19 TEMPORARY ENVIRONMENTAL CONTROLS

01 74 19 CONSTRUCTION WASTE MANAGEMENT AND DISPOSAL

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

01 91 00.15 10 TOTAL BUILDING COMMISSIONING

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

DIVISION 03 - CONCRETE

03 30 00 CAST-IN-PLACE CONCRETE

DIVISION 04 - MASONRY

04 20 00 UNIT MASONRY

DIVISION 05 - METALS

05 05 20.00 27 POST-INSTALLED CONCRETE AND MASONRY ANCHORS

05 05 23.16 STRUCTURAL WELDING

05 12 00 STRUCTURAL STEEL

05 21 00 STEEL JOIST FRAMING

05 30 00 STEEL DECKS

05 40 00 COLD-FORMED METAL FRAMING

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 51 00 METAL STAIRS

05 51 33 METAL LADDERS

05 52 00 METAL RAILINGS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 41 16.00 10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL CABINETS

06 61 16 SOLID SURFACING FABRICATIONS

REPAIR MAINTENANCE HANGAR BUILDING 51

PROJECT TABLE OF CONTENTS Page 2

VOLUME 2

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 21 13 BOARD AND BLOCK INSULATION

07 21 23 LOOSE FILL THERMAL INSULATION

07 22 00 ROOF AND DECK INSULATION

07 24 00 EXTERIOR INSULATION AND FINISH SYSTEMS

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 27 19.01 SELF-ADHERING AIR BARRIERS

07 27 26 FLUID-APPLIED MEMBRANE AIR BARRIERS

07 27 36 SPRAY FOAM AIR BARRIERS

07 42 13 METAL WALL PANELS

07 54 19 POLYVINYL-CHLORIDE ROOFING

07 60 00 FLASHING AND SHEET METAL

07 72 10 ROOFTOP FALL ARREST SYSTEM

07 72 33.13 ROOF HATCH RAIL SYSTEM

07 81 00 SPRAY-APPLIED FIREPROOFING

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 11 16 ALUMINUM DOORS AND FRAMES

08 14 00 WOOD DOORS

08 31 00 ACCESS DOORS AND PANELS

08 33 23 OVERHEAD COILING DOORS

08 34 16.10 STEEL SLIDING HANGAR DOORS

08 36 13 SECTIONAL OVERHEAD DOORS

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 60 45 TRANSLUCENT PANELS

08 62 23 TUBULAR DAYLIGHTING DEVICE

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL WALL AND DOOR LOUVERS

DIVISION 09 - FINISHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC TILING

09 51 00 ACOUSTICAL CEILINGS

09 65 00 RESILIENT FLOORING

09 67 23.16 FUEL RESISTIVE RESINOUS FLOORING, 5-COAT SYSTEM

09 68 00 CARPETING

09 84 20 ACOUSTICAL WALL PANELS

09 90 00 PAINTS AND COATINGS

09 97 13.27 HIGH PERFORMANCE COATING FOR STEEL STRUCTURES

DIVISION 10 - SPECIALTIES

10 11 00 VISUAL DISPLAY UNITS

10 14 00.10 EXTERIOR SIGNAGE

10 14 00.20 INTERIOR SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 26 00 WALL PROTECTION

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS

10 51 13 METAL LOCKERS

REPAIR MAINTENANCE HANGAR BUILDING 51

PROJECT TABLE OF CONTENTS Page 3

DIVISION 11 - EQUIPMENT

11 24 29 FALL PROTECTION SYSTEMS

DIVISION 12 - FURNISHINGS

12 21 00 WINDOW BLINDS

12 24 13 ROLLER WINDOW SHADES

12 48 13 ENTRANCE FLOOR MATS AND FRAMES

VOLUME 3

DIVISION 21 - FIRE SUPPRESSION

21 13 13 WET PIPE SPRINKLER SYSTEMS, FIRE PROTECTION

21 30 00 FIRE PUMPS

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

22 07 19.00 40 PLUMBING PIPING INSULATION

22 15 14.00 40 GENERAL SERVICE COMPRESSED-AIR SYSTEMS, LOW PRESSURE

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)

23 05 15 COMMON PIPING FOR HVAC

23 05 48.19 BRACING FOR HVAC

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC

23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS

23 09 93 SEQUENCES OF OPERATION FOR HVAC CONTROL

23 09 93A APPENDIX - SEQUENCES OF OPERATION FOR HVAC CONTROL

23 11 20 FACILITY GAS PIPING

23 21 23 HYDRONIC PUMPS

23 23 00 REFRIGERANT PIPING

23 25 00 CHEMICAL TREATMENT OF WATER FOR MECHANICAL SYSTEMS

23 30 00 HVAC AIR DISTRIBUTION

23 35 19.00 20 INDUSTRIAL VENTILATION AND EXHAUST

23 52 00 HEATING BOILERS

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 CHILLED, CHILLED-HOT, AND CONDENSER WATER PIPING SYSTEMS

23 80 20.00 10 GAS-FIRED HEATING EQUIPMENT

23 81 00 DECENTRALIZED UNITARY HVAC EQUIPMENT

VOLUME 4

DIVISION 25 - INTEGRATED AUTOMATION

25 08 10 UTILITY MONITORING AND CONTROL SYSTEM TESTING

25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND

INTEGRATION

REPAIR MAINTENANCE HANGAR BUILDING 51

PROJECT TABLE OF CONTENTS Page 4

DIVISION 26 - ELECTRICAL

26 05 00.00 40 COMMON WORK RESULTS FOR ELECTRICAL

26 05 02 ELECTRICAL DEMOLITION AND ALTERATION

26 09 23.00 40 LIGHTING CONTROL DEVICES

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 23 ADJUSTABLE SPEED DRIVE (ASD) SYSTEMS UNDER 600 VOLTS

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

27 51 16 PUBLIC ADDRESS SYSTEMS

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM,

ADDRESSABLE

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 19.61 SEALING OF JOINTS IN RIGID PAVEMENT

32 05 33 LANDSCAPE ESTABLISHMENT

32 11 23 AGGREGATE BASE COURSES

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 16 19 CONCRETE CURBS, GUTTERS AND SIDEWALKS

32 17 23 PAVEMENT MARKINGS

32 31 13 CHAIN LINK FENCES AND GATES

DIVISION 33 - UTILITIES

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

DIVISION 41 - MATERIAL PROCESSING AND HANDLING EQUIPMENT

41 22 13.55 BRIDGE CRANES, UNDER RUNNING, AIRCRAFT HANGAR

41 22 23.19 MONORAIL HOISTS

-- End of Project Table of Contents --

NC ANG-CHARLOTTE REPAIR MAINTENANCE HANGAR BUILDING 51

FJRP112701 TYPE B3 SUBMITTAL - 20 JUL 2022

SECTION 25 08 10

UTILITY MONITORING AND CONTROL SYSTEM TESTING

PART 1 GENERAL

1.1 DEFINITIONS

In addition to the definitions provided in this Section, 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC and 25 10 10 UTILITY MONITORING AND CONTROL (UMCS) FRONT END AND INTEGRATION contain definitions related to this Section.

1.1.1 Algorithm

A set of well-defined rules or procedures for solving a problem or providing an output from a specific set of inputs.

1.1.2 Analog

A signal that can take on continuous (as opposed to discrete) values.

Sensors (e.g. temperature, pressure, flow) typically provide analog signals as outputs to represent the measured variable. Within the UMCS, analog signals are generally represented by either 0-10 volt or a 4-20 milliamp signal.

1.1.3 Binary

A two-state system where an "ON" condition is represented by a high signal level and an "OFF" condition is represented by a low signal level.

1.1.4 Change-Of-Value (COV)

A type of data transmission over the network where the point value is transmitted over the network only when its value changes. COV is an efficient use of network bandwidth.

1.1.5 Control Wiring

This includes conduit, wire, and wiring devices to install complete HVAC control systems, including motor control circuits, interlocks, sensors, PE and EP switches, and like devices. This also includes all wiring from node to node, and nodes to all sensors and points defined in the I/O summary shown on drawings or specified herein, and required to execute the sequence of operation. Does not include line voltage power wiring.

1.1.6 Demand

The maximum rate of use of electrical energy averaged over a specific interval of time, usually expressed in kW.

1.1.7 Graphical User Interface (GUI)

Human-machine interfacing allows the operator to manage, command, monitor, and program the system.

SECTION 25 08 10 Page 1

1.1.8 Integration

Establishing communication between two or more systems to create a single system.

1.1.9 Protocol

In control systems, "protocol" is generally shorthand for "communication protocol"; a defined method by which digital information is exchanged electronically. Often more than one protocol is used in a BAS, for example, a typical BACnet system will use at a minimum (in addition to BACnet/IP and BACnet MS/TP) IP, UDP, ARP, Ethernet, and RS-485 protocols (and this does not include any protocols used internally in the front end or for communication with front end client workstations).

1.2 ADMINISTRATIVE REQUIREMENTS

1.2.1 Sequencing

Performance Verification Testing required by this Section must be proceeded by successful and accepted "contractors field testing" or "start-up and start-up testing" of the control system to be tested.

1.2.2 Scheduling

Coordinate testing schedules with the Government and with work in other Sections performed on the components or systems to be tested.

1.3 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:

SD-06 Test Reports

PVT Plan; G

PVT Phase I Report; G

PVT Phase II Report; G

SD-07 Certificates

Test Instrumentation Calibration Certificates; G

1.4 TEST EQUIPMENT

Provide all test equipment unless otherwise noted in the contract documents. Use only test equipment with current calibration traceable to the National Institute of Science and Technology (NIST). For each test instrument, submit Test Instrumentation Calibration Certificates demonstrating calibration traceable to NIST. Use test equipment and test methods such that the overall accuracy of the test method, including all test instrumentation and any errors inherent in the test procedure, is at least 50 percent better than the accuracy specified for the sensor. For example, if a temperature sensor has an accuracy requirement of plus or minus 1 degree Farenheit degree overall accuracy of the test method, must

SECTION 25 08 10 Page 2 be 0.5 degree Farenheit or better.

When validating sensor accuracy, the test instrument is treated as if it is perfectly accurate; that is, the measured value from the test instrument must lie within the bounds of the specified accuracy of the sensor.

Expressed mathematically:

Given:

Sensor accuracy: Plus or minus X Sensor reading: Y Test equipment reading: Z Where X, Y and Z are real numberts.

Then Sensor passes if: (Y-X) <= Z <= (Y+X) otherwise, sensor fails

PART 2 PRODUCTS

Not applicable

PART 3 EXECUTION

3.1 PERFORMANCE VERIFICATION TEST (PVT)

Perform a Performance Verification Test (PVT) to demonstrate that the installed control system meets all requirements of the project specifications. Coordinate scheduling of the PVT with the Government, and do not begin the PVT until the PVT Plan submittal is accepted.

3.1.1 PVT PLAN

Provide a PVT Plan including system documentation and PVT Procedures.

3.1.1.1 PVT Plan System Documentation

Include the following system documentation in the PVT Plan:

a. Copies of the most recent as-built drawings for the system, including but not limited to one-line drawings and Points Schedules as specified in Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC showing device address, point descriptions, network point names and types, hardware point types, settings and ranges including units.

b. Copies of manufacturer's product data sheets when needed to demonstrate compliance with project requirements. In particular, provide data sheets showing that surge protection requirements have been met.

c. Operation or user manuals for all software and all DDC Hardware to be tested.

d. List of test equipment.

3.1.1.2 PVT Equipment List

Include in the PVT procedures a control system performance verification test equipment list that lists the equipment to be used during performance verification testing. For each piece of equipment include manufacturer name, model number, equipment function, the date of the latest calibration, SECTION 25 08 10 Page 3 and the results of the latest calibration

3.1.1.3 PVT Procedures

Develop PVT procedures using the test procedures in this Section, modifying the procedures and adding tests as appropriate to develop procedures that test all requirements of the project specifications. The test procedures must consist of detailed instructions for test setup, execution, and evaluation of test results.

When developing additional procedures, provide the same information and fields as shown in the Test Template.

3.1.2 PVT Phases

Conduct PVT testing in two phases:

I. Field testing for devices, components, subsystems and the overall system using the approved PVT Procedures.

II. A one-week endurance test during which the system is operated continuously.

3.1.2.1 PVT Phase I (Field Tests)

Demonstrate compliance of the control system with the contract documents.

Using test plans and procedures approved by the Government, demonstrate all physical and functional requirements of the project. Show, step-by-step, the actions and results demonstrating that the control systems fully and correctly implement the sequences of operation. PVT for surge protection is not required to include introducing a surge to the equipment; surge protection may instead be demonstrated through product documentation.

Do not start the performance verification test until after receipt of written permission by the Government, based on Government approval of the PVT Plan and Draft As-Builts and completion of balancing of the HVAC System. Do not conduct tests during scheduled seasonal off periods of base heating and cooling systems. At the completion PVT Phase I and in accordance with the project schedule and project sequencing provide a PVT Phase I Report documenting all PVT testing including all approved test procedures with test results indicated on the procedures, and a record of all actions taken to address PVT test failures.

3.1.2.2 PVT Phase II (Endurance Test)

Complete an endurance test as part of the PVT in which the system is operated contuinuously for one-week without failure. During the endurance test trend all points shown as requiring a trend on the Points Schedule for the entire duration of the endurance test. If insufficient buffer or storage capacity exists to trend the entire endurance test, offload trend logs during the course of the endurance test to ensure that no trend data is lost. If the control system specification includes bandwidth requirements for bandwidth usage on a non-IP network, measure and record the network bandwidth usage on each non-IP channel during the endurance test.

If the system experiences any failures during the endurance test portion of the PVT, repair the system and repeat the endurance test portion of the PVT until the system operates continuously and without failure for the

SECTION 25 08 10 Page 4 specified endurance test period. At the completion of PVT Phase II and in accordance with the project schedule and project sequencing provide a PVT Phase II Report documenting failures and repair actions taken during PVT Phase II.

3.1.2.2.1 Temporary Trending Capability

Unless trending capability exists, either within the building control system or through a connected Utility Monitoring and Control System (UMCS) Front End, temporarily install hardware on the building control network to perform trending during the endurance test as indicated. Remove the temporary hardware at the completion of all testing and commissioning activities.

3.2 FACTORY TEST

Perform a Factory Test to demonstrate the capability of the proposed control system solution to meet the requirements of project specifications. Coordinate scheduling of the Factory Test with the Government, and do not begin the Factory Test unil the Factory Test Plan submittal is accepted.

3.2.1 Factory Test Setup

Design the Factory Test Setup to represent the system as it will be fielded and to demonstrate the capability of the system to meet the requirements of the project specification. At a minimum:

a. Include at least one of each model of DDC hardware, instrumentation and control device to be used on the project.

b. Include at least one network of each type to bue used on the project.

c. Include a programmable controller programmed as it will be installed, or, if no programmable controller is to be installed on the project, include a programmable controller with a sample application.

d. Include sample hardware to provide a mock field control system for the front end to communicate with if the project requires a front end but does not require a field control system.

3.2.2 Factory Test Plan

Provide a Factory Test Plan documenting the test setup and procedures.

3.2.2.1 Factory Test Plan Setup Documentation

Include the following information, at a minimum, to document the factory test setup:

a. System one-line block diagram of equipment used in the factory test identifying computers (servers and workstations), network hardware, DDC hardware, and other instrumentation including, but not limited to, sensors, actuators, test signal generators, and meters.

b. System hardware description used in the factory test.

c. System software description used in the factory test.

SECTION 25 08 10 Page 5

d. Points Schedules for each controller showing the configuration to be used during the test. Points Schedules must be as specified in Section

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC.

e. Required passwords for each operator access level.

f. List of other test equipment.

3.2.2.2 Test Procedures

Develop factory test procedures using the Test Procedures in this Section, modifying the procedures and adding tests as appropriate to develop test procedures that test all requirements of the specification. The test procedures must consist of detailed instructions for test setup, execution, and evaluation of test results. Factory test procedures must include testing of surge protection by introducing a surge to the equipment and demonstrating that the equipment survives.

When developing additional procedures, provide the same information and fields as shown in the Test Template.

3.2.3 Factory Test Report

Upon completion of the Factory Test provide a complete test report, consisting of a short summary of the factory test, a copy of the Factory Test Plan, and copies of the executed test procedures separated by test.

For each test, include date performed and identify the Government representative who witnessed and approved the test.

If a portion of any test failed, document the failure and corrective action.

3.2.4 Fatory Test Execution

Conduct the Factory Test at a location and time approved by the Government.

The Government will witness the factory test.

If the system fails a portion of a test, the Government will determine whether the entire test or only the portion that failed must be repeated.

3.3 TEST PROCEDURES

Develop test procedures using the template procedure in the Appendix. A test template and sample test procedures in electronic format are available at the Whole Building Design Guide page for this section:

https://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-25-08-10 Refer to the Sample Test Procedures Table to view the existing sample tests.

Sample Test Procedures

Test No. Test Title

1 System Equipment Verification

2 System Start-up

3 Monitoring and Control (M&C) Software Passwords

SECTION 25 08 10 Page 6

Sample Test Procedures

Test No. Test Title

4 Graphic Display of Data

5 Graphic Navigation Scheme

6 Command Functions

7 Command Input Errors

8 Special Functions

9 Software Editing Tools

10 Scheduling

11 Alarm function

12 Trending

13 Demand Limiting

14 Report Generation

15 Uninterruptable Power Supply (UPS) Test

16 Routers and Repeaters

17 Gateways (Building Level)

18 Gateways (Device Level)

19 Local Display Panel (LDP)

20 Open Network Point Verification

21 Custom Test Template

SECTION 25 08 10 Page 7

APPENDIX A

TEST NUMBER: <TEST NUMBER>

TEST TITLE: <TEST TITLE>

OBJECTIVE: <STATE TEST OBJECTIVE>

INITIAL REQUIREMENTS/CONDITIONS

1. Submittals: <LIST REQUIRED SUBMITTALS>

2. Equipment: <LIST EQUIPMENT REQUIRED FOR TEST>

3. Reference Documentation: <LIST REQUIRED REFERENCE DOCUMENTATION>

Date of Test: __________ Time of Test: __________ Contractor's Representative: ____________________ Government's Representative: ____________________

Specification References for this verification:

<LIST SECTIONS REFERENCED FOR THIS TEST>

TEST PROCEDURES: <USE THE FOLLOWING FORMAT FOR TEST PROCEDURES, EXPAND AS

NECESSARY TO CAPTURE ALL TEST ITEMS>

Item Action Expected Results Approved

SECTION 25 08 10 Page 8

Item Action Expected Results Approved

Notes:

-- End of Section --

SECTION 25 08 10 Page 9

THIS PAGE INTENTIONALLY LEFT BLANK

SECTION 25 08 10 Page 10

SECTION 25 10 10

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

PART 1 GENERAL

1.1 SUMMARY

Integrate ASHRAE 135 (BACnet) field control systems installed per Section

23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING

CONTROL SYSTEMS as specified. The existing base UMCS is Alerton.

1.1.1 System Requirements

The existing UMCS is manufactured and provide by Alerton. All components provided and installed with this section and as referenced by this section to be compatible with the base-wide system. In general, requirements for a UMCS are 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 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 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.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.

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.

SECTION 25 10 10 Page 2

AMERICAN NATIONAL STANDARDS INSTITUTE (ANSI)

ANSI INCITS 154 (1988; R 2004) Office Machines and Supplies - Alphanumeric Machines - Keyboard Arrangement

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

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

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

CONSUMER ELECTRONICS ASSOCIATION (CEA)

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

CEA-709.3 (1999; R 2015) Free-Topology Twisted-Pair Channel Specification

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

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE 802.11 (2020) Information Technology-Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks-Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications

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

INTERNET ENGINEERING TASK FORCE (IETF)

IETF RFC 7465 (2015) Prohibiting RC4 Cipher Suites

RFC 821 (2001) Simple Mail Transfer Protocol (SMTP)

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

SECTION 25 10 10 Page 3

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

NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)

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

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2020; ERTA 20-1 2020; ERTA 20-2 2020; TIA

20-1; TIA 20-2; TIA 20-3; TIA 20-4)

National Electrical Code

NFPA 262 (2019) 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)

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 (2015c; Addendum 1 2017) 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)

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

SECTION 25 10 10 Page 4 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.

1.3.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.3.2 Alarm Handling

see Alarm Routing

1.3.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.3.4 Application Generic Controller (AGC)(LonWorks)

A device that is furnished with a (limited) pre-established application that also has the capability of being programmed. Further, the ProgramID and XIF file of the device are fixed. The programming capability of an AGC may be less flexible than that of a General Purpose Programmable Controller

(GPPC).

1.3.5 Application Specific Controller (ASC)(LonWorks)

A device that is furnished with a pre-established built in application that is configurable but not re-programmable. An ASC has a fixed factory-installed application program (i.e Program ID) with configurable settings.

1.3.6 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.7 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.3.8 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

SECTION 25 10 10 Page 5 system and to modify parameters that affect the operation of a system.

1.3.9 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.3.10 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 controllers is needed.

1.3.11 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.3.12 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.3.13 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.3.14 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.3.15 BACnet Smart Actuator (B-SA)(BACnet)

A hardware device BTL Listed as a B-SA. A simple control output device with

SECTION 25 10 10 Page 6 limited resources; it is intended for specific applications.

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

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

1.3.17 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.18 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.19 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.20 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.3.21 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.22 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.23 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.24 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. When it was used, it typically referred to a piece of control hardware. The current FPOC definition typically refers instead to IT hardware)

SECTION 25 10 10 Page 7

1.3.25 Channel (LonWorks)

A portion of the control network consisting of one or more segments connected by repeaters. Channels are separated by routers. The device quantity limitation is dependent on the topology/media and device type.

For example, a TP/FT-10 network with locally powered devices is limited to 128 devices per channel.

1.3.26 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.3.27 Configuration Property (LonWorks)

Controller parameter used by the application which is usually set during installation/testing and seldom changed. For example, the P and I settings of a P-I control loop. Also see 'Standard Configuration Property Type

(SCPT)'

1.3.28 Control Logic Diagram

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

1.3.29 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.3.30 Explicit Messaging (LonWorks)

A non-standard and often vendor (application) specific method of communication between devices.

1.3.31 External Interface File (XIF) (LonWorks)

A file which documents a device's external interface, specifically the number and types of LonMark objects, the number, types, directions, and connection attributes of network variables, and the number of message tags.

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

1.3.33 Field Control Network

The network used by a field control system.

SECTION 25 10 10 Page 8

1.3.34 Field Control System (FCS)

A building control system or utility control system.

1.3.35 Fox Protocol (Niagara Framework)

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

1.3.36 Functional Profile (LonWorks)

A standard description, defined by LonMark International, of a LonMark Object used to classify and certify devices.

1.3.37 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.38 General Purpose Programmable Controller (GPPC) (LonWorks)

Unlike an ASC or AGC, a GPPC is not furnished with a fixed application program and does not have a fixed ProgramID or XIF file. A GPPC can be (re-)programmed, usually using vendor-supplied software. When a change to the program affects the external interface (and the XIF file) the ProgramID will change.

1.3.39 Internetwork (BACnet)

See BACnet Internetwork.

1.3.40 JACE (Niagara Framework)

Java Application Control Engine. See Niagara Framework Supervisory Gateway

1.3.41 LonMark Object (LonWorks)

A collection of network variables, configuration properties, and associated behavior defined by LonMark International and described by a Functional Profile. It defines how information is exchanged between devices on a network (inputs from and outputs to the network).

1.3.42 LNS Plug-in (LonWorks)

Software which runs in an LNS compatible software tool, typically a network configuration tool. Device configuration plug-ins provide a 'user friendly' method to edit a device's configuration properties.

1.3.43 LonMark (LonWorks)

See LonMark International. Also, a certification issued by LonMark International to CEA-709.1-D devices.

1.3.44 LonMark International (LonWorks)

Standards committee consisting of independent product developers, system

SECTION 25 10 10 Page 9 integrators and end users dedicated to determining and maintaining the interoperability guidelines for LonWorks. Maintains guidelines for the interoperability of CEA-709.1-D devices and issues the LonMark Certification for CEA-709.1-D devices.

1.3.45 LonWorks (LonWorks)

The term used to refer to the overall technology related to the CEA-709.1-D protocol (sometimes called "LonTalk"), including the protocol itself, network management, interoperability guidelines and products.

1.3.46 LonWorks Network Services (LNS) (LonWorks)

A network management and database standard for CEA-709.1-D devices.

1.3.47 LonWorks Network Services (LNS) Database (LonWorks)

The standard database created and used by LonWorks Network Services (LNS) compatible tools, such as LNS Network Configuration tools.

1.3.48 Modbus

A basic protocol for control network communications generally used in utility control systems. The Modbus protocol standard is maintained by The Modbus Organization.

1.3.49 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.3.50 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.51 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.3.52 Network Variable (LonWorks)

See 'Standard Network Variable Type (SNVT)'.

1.3.53 Network Configuration Tool (LonWorks)

The software used to configure the control network and set device configuration properties. This software creates and modifies the control network database (LNS Database).

1.3.54 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

SECTION 25 10 10 Page 10 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.55 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-browser based user interface.

Note that different vendors refer to this component by different names.

The most common name is "JACE"; other names include "EC-BOS", "FX-40", and

"UNC".

1.3.56 Node (LonWorks)

A device that communicates using the CEA-709.1-D protocol and is connected to a CEA-709.1-D network.

1.3.57 Node Address (LonWorks)

The logical address of a node on the network, consisting of a Domain number, Subnet number and Node number. Note that the "Node number" portion of the address is the number assigned to the device during installation and is unique within a subnet. This is not the factory-set unique Node ID (see Node ID).

1.3.58 Node ID (LonWorks)

A unique 48-bit identifier assigned (at the factory) to each CEA-709.1-D device. Sometimes called the Neuron ID.

1.3.59 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.3.60 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.3.61 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 11 points or other calculated points. Calculated points are sometimes called virtual points or internal points.

1.3.62 Point, Network

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

1.3.63 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.64 Program ID (LonWorks)

An identifier (number) stored in the device (usually EEPROM) that identifies the node manufacturer, functionality of device (application & sequence), transceiver used, and intended device usage.

1.3.65 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.66 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.67 Repeater

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

1.3.68 Router (LonWorks)

A device that connects two channels and controls traffic between the channels by retransmitting signals received from one subnet onto the other based on the signal destination. Routers are used to subdivide a control network and to control bandwidth usage.

1.3.69 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.70 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 limited to 64 devices, and a BACnet MS/TP segment is limited to 32 devices.

SECTION 25 10 10 Page 12

1.3.71 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.72 Service Pin (LonWorks)

A hardware push-button on a device which causes the device to broadcast a message containing its Node ID and Program ID. This broadcast can also be initiated via software.

1.3.73 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.74 Standard Configuration Property Type (SCPT) (LonWorks)

Pronounced 'skip-it'. A standard format type (maintained by LonMark International) for Configuration Properties.

1.3.75 Standard Network Variable Type (SNVT) (LonWorks)

Pronounced 'snivet'. A standard format type (maintained by LonMark International) used to define data information transmitted and received by the individual nodes. The term SNVT is used in two ways. Technically it is the acronym for Standard Network Variable Type, and is sometimes used in this manner. However, it is often used to indicate the network variable itself (i.e. it can mean "a network variable of a standard network variable type"). In general, the intended meaning should be clear from the context.

1.3.76 Subnet (LonWorks)

Consists of a logical grouping of up to 127 nodes, where the logical grouping is defined by node addressing.