W912QR24R0009_Specs_Vol4-0000.pdf

Solicitation For USARC - Ops Building Ft. Buchanan, Guaynabo, PR

P2: 481867

Design-Bid-Build

Specifications - Vol. 4 of 4 (Div. 25-33) Certified Final Design

22 November 2023

W912QR24R0009

ARIMS: 200A Disposition: Maintain for 15yrs after construction.

W912QR24R0009_Specs_Vol4-0000

USARC – Ops Building

Ft Buchanan

Guaynabo, Puerto Rico

Specifications (Vol IV of IV)

Certified Final Submittal

Contract Number: W912QR21D0023; P2#: 481867

27 October 2023

300 West Vine Street, Suite 1500, Lexington, KY 40507 | 859.252.9980

Louisville District

07/22/202007/27/202011/6/202012-4-202005/04/202107/22/202108/25/202102/14/202202/15/202207/13/202207/21/202205/24/202310/27/2023

10/27/2023 10/27/23

10/27/2023

10/27/2023

10/27/2023 10/27/2023

CERTIFIED FINAL

P2#: 481867 USARC - Ops Building Guaynabo, Puerto Rico

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 80 00.00 06 04/21 SPECIAL PROVISIONS

DIVISION 01 - GENERAL REQUIREMENTS

01 32 01.00 06 07/18 PROJECT SCHEDULE

01 33 00 08/18, CHG 4: 02/21 SUBMITTAL PROCEDURES

01 33 29.00 06 11/17 SUSTAINABILITY REPORTING

01 35 26.00 06 GOVERNMENT SAFETY REQUIREMENTS

01 42 00 02/19 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.15 10 11/16, CHG 2: 08/19 RESIDENT MANAGEMENT SYSTEM CONTRACTOR

MODE (RMS CM)

01 45 04.10 06 CONTRACTOR QUALITY CONTROL

01 45 35 11/20 SPECIAL INSPECTIONS

01 46 00.10 06 08/17 TOTAL BUILDING COMMISSIONING

(INDEPENDENT CxA)

01 50 00 11/20 TEMPORARY CONSTRUCTION FACILITIES AND

CONTROLS

01 52 10 03/18 CONTRACTING OFFICER'S FIELD OFFICE

01 57 19.00 06 04/20 TEMPORARY ENVIRONMENTAL CONTROLS AND

PERMITS

01 74 19 02/19, CHG 2: 08/21 CONSTRUCTION WASTE MANAGEMENT AND

DISPOSAL

01 78 23 08/15, CHG 2: 08/21 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 08/22 DEMOLITION

DIVISION 03 - CONCRETE

03 30 00 02/19, CHG 2: 05/21 CAST-IN-PLACE CONCRETE

03 45 00 05/16, CHG 1: 05/21 PRECAST ARCHITECTURAL CONCRETE

DIVISION 05 - METALS

05 12 00 08/18, CHG 2: 05/21 STRUCTURAL STEEL

05 21 00 05/15, CHG 1: 08/18 STEEL JOIST FRAMING

05 30 00 05/15, CHG 2: 08/18 STEEL DECKS

05 50 13 05/17, CHG 1: 08/18 MISCELLANEOUS METAL FABRICATIONS

05 51 33 02/16, CHG 2: 02/18 METAL LADDERS

05 52 00 02/18, CHG 1: 02/20 METAL RAILINGS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 08/16, CHG 2: 11/18 ROUGH CARPENTRY

06 20 00 08/16, CHG 2: 11/18 FINISH CARPENTRY

06 61 16 08/20 SOLID SURFACING FABRICATIONS

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 05 23 08/19 PRESSURE TESTING AN AIR BARRIER SYSTEM

FOR AIR TIGHTNESS

07 21 13 02/16, CHG 2: 08/20 BOARD AND BLOCK INSULATION

07 21 16 11/11, CHG 4: 08/18 MINERAL FIBER BLANKET INSULATION

07 22 00 02/16, CHG 3: 11/18 ROOF AND DECK INSULATION

PROJECT TABLE OF CONTENTS Page 1

07 27 10.00 10 08/19, CHG 1: 02/20 BUILDING AIR BARRIER SYSTEM

07 27 19.01 05/17, CHG 2: 08/20 SELF-ADHERING AIR BARRIERS

07 27 36 05/17, CHG 2: 08/20 SPRAY FOAM AIR BARRIERS

07 52 00.00 48 10/10 SBS-MODIFIED BITUMINOUS MEMBRANE

ROOFING SYSTEM

07 62 00.00 48 10/10 FLASHING AND SHEET METAL

07 84 00 05/10, CHG 1: 08/13 FIRESTOPPING

07 92 00.00 48 10/10 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 08/20 STEEL DOORS AND FRAMES

08 11 16 05/17, CHG 2: 11/18 ALUMINUM DOORS AND FRAMES

08 14 00 08/16, CHG 1: 08/18 WOOD DOORS

08 31 00 05/17, CHG 1: 08/18 ACCESS DOORS AND PANELS

08 33 13 05/09, CHG 2: 11/12 COILING COUNTER DOORS

08 33 23 08/20 OVERHEAD COILING DOORS

08 34 59 08/08, CHG 1: 11/12 VAULT DOORS AND DAY GATES

08 36 13 08/20 SECTIONAL OVERHEAD DOORS

08 51 14.00 48 03/06 ALUMINUM AND ENVIRONMENTAL CONTROL

ALUMINUM WINDOWS

08 71 00 02/16, CHG 3: 08/20 DOOR HARDWARE

08 81 00.00 48 09/06 GLAZING

08 91 00 08/20 METAL WALL LOUVERS

DIVISION 09 - FINISHES

09 22 00 02/10, CHG 2: 08/18 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 08/16, CHG 4: 02/20 GYPSUM BOARD

09 30 10 08/20 CERAMIC, QUARRY, AND GLASS TILING

09 51 00 08/20 ACOUSTICAL CEILINGS

09 65 00 08/10, CHG 3: 08/18 RESILIENT FLOORING

09 67 23.13 11/19 STANDARD RESINOUS FLOORING

09 90 00 02/21 PAINTS AND COATINGS

09 96 00 11/14 HIGH-PERFORMANCE COATINGS

DIVISION 10 - SPECIALTIES

10 11 00 08/20 VISUAL DISPLAY UNITS

10 14 00.10 08/17, CHG 1: 11/18 EXTERIOR SIGNAGE

10 14 00.20 08/20 INTERIOR SIGNAGE

10 21 13 08/20 TOILET COMPARTMENTS

10 22 13.00 48 01/11 WIRE MESH PARTITIONS

10 22 26.00 48 08/04 OPERABLE PARTITIONS

10 26 00 08/20 WALL AND DOOR PROTECTION

10 28 00.00 48 04/06 TOILET AND BATH ACCESSORIES

10 44 13.00 48 04/06 FIRE EXTINGUISHERS AND CABINETS

10 51 26.64 08/15 PLASTIC LOCKERS AND BENCHES

10 56 13.00 48 10/05 METAL STORAGE SHELVING

10 71 13.13 04/06 STORM SHUTTERS

10 90 00.00 48 04/06 MISCELLANEOUS SPECIALTIES (PARTIAL

OMAR FUNDED)

DIVISION 11 - EQUIPMENT

11 46 01.00 48 12/09 KITCHEN EQUIPMENT

DIVISION 12 - FURNISHINGS

PROJECT TABLE OF CONTENTS Page 2

12 24 13 08/20 ROLLER WINDOW SHADES

12 48 13 08/17 ENTRANCE FLOOR MATS

DIVISION 21 - FIRE SUPPRESSION

21 13 13 08/20 WET PIPE SPRINKLER SYSTEMS, FIRE

PROTECTION

21 21 03.00 10 02/09 WET CHEMICAL FIRE EXTINGUISHING SYSTEM

DIVISION 22 - PLUMBING

22 00 00.00 48 2/07 PLUMBING, GENERAL PURPOSE

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

23 05 48.19 05/18, CHG 2: 08/20 SEISMIC BRACING FOR HVAC

23 05 93.00 06 08/16 TESTING, ADJUSTING, AND BALANCING

(TAB) OF HVAC

23 07 00 02/13, CHG 7: 05/20 THERMAL INSULATION FOR MECHANICAL

SYSTEMS

23 09 00 02/19, CHG 3: 05/21 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 11/15, CHG 2: 05/21 INSTRUMENTATION AND CONTROL DEVICES

FOR HVAC

23 09 23.02 02/19, CHG 1: 02/20 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS

23 23 00 10/07 REFRIGERANT PIPING

23 30 00 05/20 HVAC AIR DISTRIBUTION

23 64 00.00 48 01/07 LIQUID CHILLERS

23 64 26.00 48 01/07 CHILLED, CHILLED-HOT, AND CONDENSER

WATER PIPING SYSTEMS

23 82 02.00 48 04/06 UNITARY HEATING AND COOLING EQUIPMENT

DIVISION 25 - INTEGRATED AUTOMATION

25 05 11.01 05/21 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS (HVAC ONLY)

25 05 11.02 05/21 CYBERSECURITY FOR FACILITY-RELATED

CONTROL SYSTEMS - FAMNS

25 08 10 05/21 UTILITY MONITORING AND CONTROL SYSTEM

TESTING

25 10 10 02/19, CHG 1: 05/21 UTILITY MONITORING AND CONTROL SYSTEM

(UMCS) FRONT END AND INTEGRATION

DIVISION 26 - ELECTRICAL

26 05 48.00 10 10/07 SEISMIC PROTECTION FOR ELECTRICAL

EQUIPMENT

26 08 00 08/08, CHG 1: 02/15 APPARATUS INSPECTION AND TESTING

26 12 19.10 05/19, CHG 1: 11/19 THREE-PHASE, LIQUID-FILLED PAD-MOUNTED

TRANSFORMERS

26 20 00 08/19, CHG 2: 05/21 INTERIOR DISTRIBUTION SYSTEM

26 28 01.00 10 10/07 COORDINATED POWER SYSTEM PROTECTION

26 29 23 02/20, CHG: 1 - 05/21 ADJUSTABLE SPEED DRIVE (ASD) SYSTEMS

UNDER 600 VOLTS

26 31 00 11/21 FACILITY-SCALE SOLAR PHOTOVOLTAIC (PV)

SYSTEMS

26 41 00 11/13 LIGHTNING PROTECTION SYSTEM

26 51 00 05/20, CHG 1: 05/21 INTERIOR LIGHTING

PROJECT TABLE OF CONTENTS Page 3

DIVISION 27 - COMMUNICATIONS

27 05 13.43 05/20 TELEVISION DISTRIBUTION SYSTEM

27 05 28.36 48 04/20 CABLE TRAYS FOR COMMUNICATIONS SYSTEMS

27 10 00.00 48 10/20 BUILDING TELECOMMUNICATIONS CABLING

SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 13 00.00 48 01/11 PHYSICAL ACCESS CONTROL SYSTEM

28 31 76 08/20 INTERIOR FIRE ALARM AND MASS

NOTIFICATION SYSTEM, ADDRESSABLE

DIVISION 31 - EARTHWORK

31 00 00.00 06 07/18 EARTHWORK

31 05 19.13 02/21 GEOTEXTILES FOR EARTHWORK

31 11 00 11/18 CLEARING AND GRUBBING

31 31 16.13 08/16 CHEMICAL TERMITE CONTROL

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 19.61 11/19 SEALING OF JOINTS IN RIGID PAVEMENT

32 05 33 08/17 LANDSCAPE ESTABLISHMENT

32 11 20 08/17 BASE COURSE FOR RIGID PAVING

32 13 13.06 05/20 PORTLAND CEMENT CONCRETE PAVEMENT FOR

ROADS AND SITE FACILITIES

32 16 19 05/18 CONCRETE CURBS, GUTTERS AND SIDEWALKS

32 17 23 08/16, CHG 5: 11/18 PAVEMENT MARKINGS

32 92 19 08/17 SEEDING

32 92 23 04/06, CHG 1: 08/21 SODDING

32 93 00 08/17 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 11 00 02/18 WATER UTILITY DISTRIBUTION PIPING

33 30 00 05/18 SANITARY SEWERAGE

33 40 00 02/10, CHG 6: 02/19 STORM DRAINAGE UTILITIES

33 46 16 05/18 SUBDRAINAGE PIPING

33 71 01 05/19, CHG 1: 11/19 OVERHEAD TRANSMISSION AND DISTRIBUTION

33 71 02 02/15, CHG 1: 11/19 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00.00 48 04/20 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 4

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:

CEA-709.1-D (LonWorks) with LonWorks Network Services (LNS), ASHRAE 135 (BACnet), MODBUS Protocol , MODBUS TCP/IP, OPC DA, or the Niagara Framework with Fox protocol as indicated and shown. 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.

1.1.1 System Requirements

Provide a 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, CEA-709.1-D , MODBUS Protocol , MODBUS TCP/IP, OPC DA, and Niagara Framework 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.

SECTION 25 10 10 Page 1

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

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 FACILITY-RELATED CONTROL SYSTEMS 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 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

ASHRAE FUN SI (2017) Fundamentals Handbook, SI 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 754 (2008) Floating-Point Arithmetic - IEEE Computer Society

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 1815 (2015; CORR 2016) Exchanging Information Between Networks Implementing IEC 61850 and IEEE Std 1815 Distributed Network Protocol (DNP3)

SECTION 25 10 10 Page 3

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

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO)

ISO 8601 (2004) Data Elements and Interchange Formats - Information Interchange - Representation of Dates and Times

ISO 8859-1 (1998) Information Technology - 8-Bit Single-Byte Coded Graphic Character Sets - Part 1: Latin Alphabet No. 1

INTERNET ENGINEERING TASK FORCE (IETF)

IETF RFC 4361 (2006) Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)

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

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 (2018) 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

SECTION 25 10 10 Page 4

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

TRIDIUM, INC (TRIDIUM)

Niagara Framework (2012) NiagaraAX User's Guide

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

U.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)

FCC EMC (2002) FCC Electromagnetic Compliance 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.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.

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.

SECTION 25 10 10 Page 5

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 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.4.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.4.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.4.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.4.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 system and to modify parameters that affect the operation of a system.

1.4.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.4.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

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

SECTION 25 10 10 Page 7

1.4.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.4.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.4.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.4.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.4.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.4.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.4.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)

1.4.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.4.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

SECTION 25 10 10 Page 8 is useful for Overrides.

1.4.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.4.28 Control Logic Diagram

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

1.4.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.4.30 Explicit Messaging (LonWorks)

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

1.4.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.4.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.4.33 Field Control Network

The network used by a field control system.

1.4.34 Field Control System (FCS)

A building control system or utility control system.

1.4.35 Fox Protocol (Niagara Framework)

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

1.4.36 Functional Profile (LonWorks)

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

SECTION 25 10 10 Page 9

1.4.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.4.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.4.39 Internetwork (BACnet)

See BACnet Internetwork.

1.4.40 JACE (Niagara Framework)

Java Application Control Engine. See Niagara Framework Supervisory Gateway

1.4.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.4.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.4.43 LonMark (LonWorks)

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

1.4.44 LonMark International (LonWorks)

Standards committee consisting of independent product developers, system 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.4.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.4.46 LonWorks Network Services (LNS) (LonWorks)

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

SECTION 25 10 10 Page 10

1.4.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.4.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.4.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.4.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.4.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.4.52 Network Variable (LonWorks)

See 'Standard Network Variable Type (SNVT)'.

1.4.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.4.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 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.4.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.

SECTION 25 10 10 Page 11

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.4.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.4.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.4.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.4.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.4.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.4.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 points or other calculated points. Calculated points are sometimes called virtual points or internal points.

1.4.62 Point, Network

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

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

SECTION 25 10 10 Page 12

1.4.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.4.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.4.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.4.67 Repeater

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

1.4.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.4.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.4.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.

1.4.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.4.72 Service Pin (LonWorks)

A hardware push-button on a device which causes the device to broadcast a

SECTION 25 10 10 Page 13 message containing its Node ID and Program ID. This broadcast can also be initiated via software.

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

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

1.4.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.4.76 Subnet (LonWorks)

Consists of a logical grouping of up to 127 nodes, where the logical grouping is defined by node addressing. Each subnet is assigned a number which is unique within the Domain. See also Node Address.

1.4.77 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.78 Supervisory Gateway

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

1.4.79 TP/FT-10 (LonWorks)

A Free Topology Twisted Pair network (at 78 kbps) defined by CEA-709.3 .

This is the most common media type for a CEA-709.1-D control network.

1.4.80 TP/XF-1250 (LonWorks)

A high speed (1.25 Mbps) twisted pair, doubly-terminated bus network defined by the LonMark Interoperability Guide lines. This media is typically used only as a backbone media to connect multiple TP/FT-10 networks.

SECTION 25 10 10 Page 14

1.4.81 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.82 User-defined Configuration Property Type (UCPT) (LonWorks)

Pronounced 'u-keep-it'. A Configuration Property format type that is defined by the device manufacturer.

1.4.83 User-defined Network Variable Type (UNVT) (LonWorks)

A network variable format defined by the device manufacturer. Note that UNVTs create non-standard communications (other vendor's devices may not correctly interpret it) and may close the system and therefore are not permitted by this specification.

1.4.84 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 information only. When used, a code following the "G" classification identifies the office that will review the submittal for the Government.

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

UMCS Contractor Design Drawings as a single complete package: 2 hard copies and 2 copies on CDROM. Submit hardcopy drawings on A3 17 by 11 inches sheets, and electronic drawings in both PDF and AutoCAD format.

Draft As-Built Drawings ; G

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

Final As-Built Drawings ; G

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

SECTION 25 10 10 Page 15

SD-03 Product Data

Product Data Sheets ; G

Computer Software ; G

The most recent versions of all computer software provided under this specification delivered as a Technical Data Package. Submit the user manuals for all software delivered for this project with the software.

Enclosure Keys

SD-05 Design Data

UMCS IP Network Bandwidth Usage Estimate ; G

Four copies of the UMCS IP Network Bandwidth Usage Estimate.

SD-06 Test Reports

Pre-Construction QC Checklist ; G

Four copies of the Pre-Construction QC Checklist.

Post-Construction QC Checklist ; G

Four copies of the Post-Construction QC Checklist.

Factory Test Procedures ; G

Four copies of the Factory Test Procedures. The Factory Test Procedures may be submitted as a Technical Data Package.

Factory Test Report

Four copies of the Factory Test Report. The Factory Test Report may be submitted as a Technical Data Package.

Existing Conditions Report ; G

Four copies of the Existing Conditions Report.

Start-Up and Start-Up Testing Report ; G

Four copies of the Start-Up and Start-Up Testing Report. The Start-Up and Testing report may be submitted as a Technical Data Package.

PVT Phase I Procedures ; G

Four copies of the PVT Phase I Procedures. The PVT Procedures may be submitted as a Technical Data Package.

PVT Phase I Report ; G

Four copies of the PVT Phase I Report. The PVT Phase I Report may be submitted as a Technical Data Package.

SECTION 25 10 10 Page 16

PVT Phase II Report ; G

Four copies of the PVT Phase II Report. The PVT Phase II Report may be submitted as a Technical Data Package.

SD-10 Operation and Maintenance Data

Operation and Maintenance (O&M) Instructions ; G

Four bound O&M Instructions and 2 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.

Preventive Maintenance Work Plan ; G

Four copies of the Preventive Maintenance Work Plan. The Preventive Maintenance Work Plan may be submitted as a Technical Data Package.

Basic Training Documentation ; G

Training manuals for Basic Training delivered for each trainee on the Course Attendance List with two additional copies delivered for archival at the project site. Submit two copies of the Course Attendance List with the archival copies. The Basic Training Documentation may be submitted as a Technical Data Package.

Advanced Training Documentation ; G

One set of training manuals delivered for each trainee on the Course Attendance List with two additional copies delivered for archival at the project site. Submit two copies of the Course Attendance List with the archival copies. The Advanced Training Documentation may be submitted as a Technical Data Package.

Refresher Training Documentation ; G

One set of training manuals delivered for each trainee on the Course Attendance List with two additional copies delivered for archival at the project site. Submit two copies of the Course Attendance List with the archival copies. The Refresher Training Documentation may be submitted as a Technical Data Package.

SD-11 Closeout Submittals

Closeout QC Checklist ; G

Four copies of the Closeout QC Checklist.

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

SECTION 25 10 10 Page 17

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' is used for 'after completion of'.

TABLE I. PROJECT SEQUENCING

ITEM TYPE DESCRIPTION SEQUENCING

(START OF ACTIVITY or

DEADLINE FOR SUBMITTAL)

1 Notice to proceed

2 S Existing Conditions Report 21 days after #1

3 S Design Drawings 21 days after #1

4 S Product Data Sheets 21 days after #1

5 S UMCS IP Network Bandwidth Usage Estimate

21 days after #1

6 S Pre-construction QC Checklist 21 days after #1

7 E Install UMCS AAO #2 thru #6

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

9 S Post-Construction QC Checklist 14 days ACO #8

SECTION 25 10 10 Page 18

TABLE I. PROJECT SEQUENCING

ITEM TYPE DESCRIPTION SEQUENCING

(START OF ACTIVITY or

DEADLINE FOR SUBMITTAL)

10 S Computer Software 14 days ACO #8

11 S Start-Up and Start-Up Testing Report

14 days ACO #8

12 S Draft As-Built Drawings 21 days ACO #8

13 S PVT Phase I Procedures 21 days before scheduled start of #14 and AAO #11

14 E PVT Phase I AAO #13 and #12

15 S PVT Phase I Report 14 days ACO #14

16 S Preventive Maintenance Work Plan AAO #11

17 S O&M Instructions AAO #11

18 S Basic Training Documentation AAO #11 and 14 days before scheduled start of #19

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

20 S PVT Phase II Report 14 days ACO #19

21 S Final As-Built Drawings 14 days AAO #20

22 S Advanced Training Documentation 7 days before schedule start of #23 and AAO #18

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

24 S Refresher Training Documentation 14 days before #25 and AAO #18 and #22

25 E Refresher Training between 14 and 40 days 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

SECTION 25 10 10 Page 19 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 http://www.wbdg.org/ffc/dod/unified-facilities-guide-specifications-ufgs/ufgs-25-10-10

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.

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…