Ft.Lee_Specs_Vol_3_Sept_2016.pdf

US Army Corps of Engineers Norfolk District

SPECIFICATIONS

Training Support Facility

Ft. Lee, VA.

Volume 3 of 3

REQUEST FOR PROPOSAL: W91236-17-R-0002

CONTRACT NO.:

DATE Sept, 2016

THIS PAGE LEFT INTENTIONALLY BLANK

Training Support Facility, Ft. Lee, VA LEETSF

TABLE OF CONTENTS Page 1

PROJECT TABLE OF CONTENTS

VOLUME 1

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 30 00.10 50 PROJECT WORK REQUIREMENTS AND RESTRICTIONS

01 30 00.20 50 ADMINISTRATIVE REQUIREMENTS

01 31 19.00 50 PROJECT MEETINGS

01 32 01.00 50 PROJECT SCHEDULE

01 33 00.00 50 SUBMITTAL PROCEDURES

01 33 29 SUSTAINABILITY REPORTING

01 35 26.00 50 GOVERNMENTAL SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 02.00 50 QUALITY CONTROL SYSTEM (QCS)

01 45 04.00 50 CONTRACTOR QUALITY CONTROL

01 50 02.00 50 TEMPORARY CONSTRUCTION FACILITIES

01 57 19.00 20 TEMPORARY ENVIRONMENTAL CONTROLS

01 57 19.01 20 SUPPLEMENTAL TEMPORARY ENVIRONMENTAL CONTROLS

01 58 00 PROJECT IDENTIFICATION

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 02.00 50 CLOSEOUT SUBMITTALS

01 78 23.00 50 OPERATION AND MAINTENANCE DATA

01 91 00.80 COMMISSIONING

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

DIVISION 03 - CONCRETE

03 15 00.00 10 CONCRETE ACCESSORIES

03 30 00.00 10 CAST-IN-PLACE CONCRETE

03 35 43.00 10 POLISHED CONCRETE FLOOR FINISHING

DIVISION 04 - MASONRY

04 20 00 UNIT MASONRY

04 21 13.13 NONBEARING MASONRY VENEER/STEEL STUD WALLS

DIVISION 05 - METALS

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 52 00 METAL RAILINGS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 20 00 FINISH CARPENTRY

06 41 16.00 10 LAMINATE CLAD ARCHITECTURAL CASEWORK

06 61 16 SOLID POLYMER (SOLID SURFACING) FABRICATIONS

TABLE OF CONTENTS Page 2

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 05 23 PRESSURE TESTING AN AIR BARRIER SYSTEM FOR AIR TIGHTNESS

07 13 53 ELASTOMERIC SHEET WATERPROOFING

07 21 13 BOARD AND BLOCK INSULATION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 21 19 SPRAYED POLYURETHANE FOAM INSULATION

07 22 00 ROOF AND DECK INSULATION

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 31 22 LEAK BARRIER UNDERLAYMENT (Ice Damming)

07 42 13 METAL WALL PANELS

07 60 00 FLASHING AND SHEET METAL

07 61 14.00 20 STEEL STANDING SEAM ROOFING

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

Volume 2

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 11 16 ALUMINUM DOORS AND FRAMES

08 14 00 WOOD DOORS

08 33 23 OVERHEAD COILING DOORS

08 34 59 VAULT DOORS AND DAY GATES

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 44 00 CURTAIN WALL AND GLAZED ASSEMBLIES

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL LOUVERS

DIVISION 09 - FINISHES

09 06 90 COLOR SCHEDULE

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 13 CERAMIC TILING

09 51 00 ACOUSTICAL CEILINGS

09 65 00 RESILIENT FLOORING

09 66 23 RESINOUS MATRIX TERRAZZO FLOORING

09 68 00 CARPETING

09 83 13 SPRAY APPLIED FIBERGLASS - ACOUSTICAL COATING

09 90 00 PAINTS AND COATINGS

DIVISION 10 - SPECIALTIES

10 14 00.20 SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 22 40 VERTICALLY FOLDING PANEL PARTITIONS

10 26 13 WALL AND CORNER GUARDS

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS, CABINETS AND WALL BRACKETS

10 51 13 METAL LOCKERS

10 56 26 MOBILE STORAGE SHELVING UNITS (MECHANICALLY ASSISTED)

TABLE OF CONTENTS Page 3

DIVISION 11 - EQUIPMENT

11 13 20.13 LOADING DOCK SCISSOR LIFT

DIVISION 12 - FURNISHINGS

12 24 13 ROLLER WINDOW SHADES

12 48 13 ENTRANCE FLOOR MATS AND FRAMES

12 93 00 SITE FURNISHINGS

DIVISION 21 - FIRE SUPPRESSION

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

21 30 00 FIRE PUMPS

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

22 15 00.00 20 LOW PRESSURE AIR PIPING

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

23 00 00 AIR SUPPLY, DISTRIBUTION, VENTILATION, AND EXHAUST SYSTEMS

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.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS

23 11 25 FACILITY GAS PIPING

23 23 00 REFRIGERANT PIPING

23 25 00 CHEMICAL TREATMENT OF WATER FOR MECHANICAL SYSTEMS

23 52 00 HEATING BOILERS

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 CHILLED WATER PIPING SYSTEMS

23 75 13.00 10 CUSTOM PACKAGED, OUTDOOR, CENTRAL-STATION AIR-HANDLING

UNITS

23 82 02.00 10 UNITARY HEATING AND COOLING EQUIPMENT

Volume 3

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

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 00.00 40 COMMON WORK RESULTS FOR ELECTRICAL

26 08 00 APPARATUS INSPECTION AND TESTING

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 13 SWITCHBOARDS

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

TABLE OF CONTENTS Page 4

DIVISION 27 - COMMUNICATIONS

27 05 28.36 40 CABLE TRAYS FOR COMMUNICATIONS SYSTEMS

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

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 05 19 GEOTEXTILE

31 11 00 CLEARING AND GRUBBING

31 23 23 BACKFILLING-EXPANDED POLYSTYRENE (EPS) BLOCKS

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 10 00 BITUMINOUS CONCRETE PAVEMENT

32 11 16.16 BASE COURSE FOR RIGID AND SUBBASE COURSE FOR FLEXIBLE PAVING

32 11 23 AGGREGATE BASE COURSE

32 11 24 GRADED CRUSHED AGGREGATE BASE COURSE FOR PERVIOUS PAVEMENT

32 11 26.16 BITUMINOUS CONCRETE BASE COURSE

32 12 16 HOT MIX ASPHALT (HMA) FOR ROADS

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 13 43 PERVIOUS CONCRETE PAVING

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 17 24.00 10 PAVEMENT MARKINGS

32 92 19 SEEDING

32 92 23 SODDING

32 93 00 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 40 00 STORM DRAINAGE UTILITIES

33 46 13 FOUNDATION DRAINAGE SYSTEM

33 46 16 SUBDRAINAGE SYSTEM

33 51 15 NATURAL-GAS / LIQUID PETROLEUM GAS DISTRIBUTION

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

33 82 00 TELECOMMUNICATIONS OUTSIDE PLANT (OSP)

-- End of Project Table of Contents --

SECTION 25 08 10

UTILITY MONITORING AND CONTROL SYSTEM TESTING

04/06

PART 1 GENERAL

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

CONSUMER ELECTRONICS ASSOCIATION (CEA)

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

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

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

1.2 DEFINITIONS

1.2.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.2.2 Analog

A continuously varying signal value (temperature current, velocity, etc.).

1.2.3 Analog to Digital (A/D) Converter

An A/D converter is a circuit or device whose input is information in analog form and whose output is the same information in digital form.

1.2.4 CEA-709.1-D

"Control Network Protocol Specification", Standard communication protocol for networked control systems that provides peer-to-peer communications.

1.2.5 Application Specific Controller

A device that is furnished with a pre-established built in application that is configurable but not re-programmable.

1.2.6 Architecture

Architecture is the general organization and structure of hardware and software.

SECTION 25 08 10 Page 1

1.2.7 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.2.8 Building Point of Connection (BPOC)

The point of connection between the UMCS network backbone and the building network backbone. The hardware at this location, which performs/provides the connection is referred to as the BPOC Hardware.

1.2.9 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.2.10 Demand

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

1.2.11 Diagnostic Program

Machine-executable instructions used to detect and isolate system and component malfunctions.

1.2.12 Distributed Control

A system whereby all control processing is decentralized and independent of a central computer. In regards to a LonWorks based system, it also means where the control logic for a single piece of building level control resides in more than one controller (node).

1.2.13 Graphical User Interface (GUI)

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

1.2.14 Integration

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

1.2.15 Interoperable

Two devices are interoperable if installed into the same system and they communicate with each other without the use of another device (such as a gateway).

1.2.16 LonTalk(r)

Open communication protocol developed by the Echelon(r) Corporation.

SECTION 25 08 10 Page 2

1.2.17 LONWORKS(r)

The communication technology developed by Echelon(r) Corporation for control systems developed. The technology is based on the CEA-709.1-D protocol and employs interoperable devices along with the capability to openly manage these devices using a network configuration tool.

1.2.18 LONMARK(r) International (LONMARK(r) Interoperability Assoc.)

Standards committee consisting of numerous independent product developers and systems integrators dedicated to determining and maintaining the interoperability guidelines for the LONWORKS(r) industry.

1.2.19 LonMarked(r)

A device that has been certified for compliance with LonMark(r) standards by the LonMark(r) International.

1.2.20 LONWORKS(r) Application Specific Controller (ASC)

A networked device or node that contains a complete, configurable application that is specific to a particular task.

1.2.21 LONWORKS(r) General Purpose Programmable Controller

A programmable control product, that unlike an ASC, is not installed with a fixed factory-installed application program. The application in the controller is custom software produced by the integrator specifically for the project.

1.2.22 LONWORKS(r) Network Services (LNS)

The database format for addressing nodes and variable bindings node-to-node.

1.2.23 Network

A system of distributed control units that are linked together on a communication bus. A network allows sharing of point information between all control units. Additionally, a network provides central monitoring and control of the entire system from any distributed control unit location.

1.2.24 Network Configuration Tool

Software used to create and modify the control network database and configure controllers.

1.2.25 Node ID

A unique 48-bit node identification (ID) tag given to each node by Echelon Corporation.

1.2.26 Node

An intelligent LONWORKS(r) device with a node ID and communicates via CEA-709.1-D and is connected to an CEA-709.1-D network.

SECTION 25 08 10 Page 3

1.2.27 Operating System (OS)

Software which controls the execution of computer programs and which provides scheduling, debugging, input/output controls, accounting, compilation, storage assignment, data management, and related services.

1.2.28 Operator Workstation (OWS)

The OWS consists of a high-level processing desktop or laptop computer that provides a graphic user interface to network.

1.2.29 Peripheral

Input/Output (I/O) equipment used to communicate to and from the computer and make hard copies of system outputs and magnetic files.

1.2.30 Router

A device which routes messages destined for a node on another segment subnet or domain of the control network. The device controls message traffic based on node address and priority. Routers may also serve as communication links between powerline, twisted pair, fiber, coax, and RF media.

1.2.31 Standard Network Variable Type (SNVT)

A network variable of a standard format type used to define data information transmitted and receive by the individual nodes.

1.2.32 UMCS Network Media

Transmission equipment including cables and interface modules (excluding MODEMs) permitting transmission of digital information.

1.2.33 XIF

"External Interface File" contains the contents of the manufacturer's product documentation.

1.2.34 Gateway

A device that translates from one protocol to another. Gateways are also called Communications Bridges or Protocol Translators.

1.3 SYSTEM DESCRIPTION

a. The purpose of this Specification is to define generic Factory, Performance Verification, and Endurance Test procedures for Utility Monitoring and Control Systems (UMCS) and building level DDC. These tests are to be used to assure that the physical and performance requirements of UMCS and building level DDC are tested, and that the test results are adequately documented. The Government will base certain contractual decisions on the results of these tests.

b. This document covers the factory, performance verification, and endurance test procedures for the Utility Monitoring and Control System (UMCS) and Direct Digital Control for HVAC. It has been written for a host based system where the LONWORKS(r) LNS database resides on the main computer (server) and communicates over the

SECTION 25 08 10 Page 4

Ethernet (TCP/IP) connection to the field level controller nodes. The system shall be comprised of the server hardware and software, IP network hardware and software, and building point of connection (BPOC) hardware and software.

c. The contractor who provided building level DDC under Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC is responsible for testing the building level DDC. All control testing and controller tuning required under Section 23 09 00 shall be completed and approved before performing Performance Verification and Endurance Tests under this section.

d. The following UFGS: Section 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION and Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC shall be part of the contract documents.

1.3.1 Factory Test

Conduct a factory test at a company site. Perform some of the basic functions of the UMCS and building level DDC, to assure that the performance requirements of the specifications are met.

1.3.2 Performance Verification and Endurance Test

a. Shall be conducted on hardware and software installed at the jobsite to assure that the physical and performance requirements of specifications are met. Tests on network media shall include all contractor furnished media and shall include at least one type of each device installed.

b. Shall be conducted under normal mode operation, unless otherwise indicated in the initial conditions description for each test. System normal mode describes a condition in which the system is performing its assigned tasks in accordance with the contract requirements.

c. Shall utilize the operator workstation (OWS) to issue commands or verify status data.

1.3.3 Test Equipment and Setup

All test equipment calibrations shall be traceable to NIST. The accuracy of the test equipment and overall test method shall be at least twice the maximum accuracy required for the test. For example, if a temperature sensor has an accuracy of +1 degree F over the executed range, the test instrument used shall have an accuracy of at least +0.5 degree F or better. Provide all test equipment unless otherwise noted in the contract documents.

1.4 SUBMITTALS

Government approval is required for submittals with a "G" or "GA" designation; submittals not having a "G" or "GA" designation are for information only. When used, a designation following the "G" or "GA" designation identifies the office that will review the submittal for the Government. Submittals with an "S" are for inclusion in the Sustainability Notebook, in conformance to Section 01 33 29 SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01 33 00.00 50

SUBMITTAL PROCEDURES:

SECTION 25 08 10 Page 5

SD-01 Preconstruction Submittals

Factory Test

SD-06 Test Reports

UMCS and Building Level DDC Testing Sequence Performance Verification Test; G, NAB Endurance Testing

PART 2 PRODUCTS

Not Used

PART 3 EXECUTION

3.1 UMCS AND BUILDING LEVEL DDC TESTING SEQUENCE

Perform a successful factory test prior to start of installation work, as described in this section. During the installation phase, perform all required field testing requirements on the UMCS and building level DDC as specified in Sections 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION and 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC, to verify that systems are functioning and installed in accordance with specifications. Submit field test report prior to start of PVT and endurance testing. After completing all required field testing, perform a successful PVT and endurance test. All tests shall be successfully completed, and test reports received, prior to final acceptance of the UMCS and building level DDC. Perform and document Contractor field test on UMCS and building level DDC.

3.2 COORDINATION

Coordinate the testing schedule with the Government. Coordination shall include controls specified in other sections or divisions which include controls and control devices that are to be part of or interfaced to the UMCS specified in this section.

3.3 PROTECTION

Protect all work and material from damage by the work or workers. The Contractor is liable for any damage caused and responsible for the work and equipment until finally inspected, tested, and accepted. Protect the work against theft, and carefully store material and equipment received onsite that is not immediately installed.

3.4 FACTORY TEST

3.4.1 Factory Test Plan

Prior to the scheduling of the factory tests, provide the Government with a Factory Test Plan for approval, and wait to receive notification of approval of the Test Plan and Procedures before performing the tests. The plan shall include the following, as a minimum:

a. System one-line block diagram of equipment used in the factory test model, indicating servers, workstations, peripherals, network equipment, controllers, and instrumentation.

SECTION 25 08 10 Page 6

b. System hardware description used in the factory test.

c. System software description used in the factory test.

d. Listing of control and status points in the factory test model; plus a table with the following information:

(1) Input and output variables.

(2) SNVTs for each variable.

(3) Expected engineering units for each variable.

(4) Node ID.

(5) Domain & subnet addressing.

e. Required passwords for each operator access level.

f. List of other test equipment.

3.4.2 Test Procedures

Develop the factory test procedures from the generic test procedures in ATTACHMENT A. The test procedures shall consist of detailed instructions for test setup, execution, and evaluation of test results. Edit the generic test procedure for the existing UMCS and new building level DDC.

Perform a factory test on a model of the UMCS and building level DDC for the Government to verify the system will function to the requirements of the contract documents. There shall be a TCP/IP layer with two Internet Protocol (IP) to Lon routers. Below each of the routers shall be both programmable (GPPC) and application-specific controllers (ASC). One server and one workstation with printers shall be connected to the IP layer. There shall be simulated input devices connected to controllers to enable the creation of changing variables. If, during testing, the system fails a portion of a test, the Government will inform the Contractor if the entire test or only the portion that failed shall be re-performed.

Give the Government a written report of those items which failed, what the problem was, and what was done to correct it. Provide onsite technical support to perform the PVT. ATTACHMENT A presents the generic Test Procedures with the following information:

a. Test identification number.

b. Test title.

c. Objective.

d. Initial conditions (if applicable).

e. Test equipment (if required).

f. Sequence of events.

g. Expected results.

3.4.3 Test Report

Submit a factory final, complete test report after completing the test, consisting of the following, as a minimum:

a. Section one of the submittal shall be a short summary of the factory

SECTION 25 08 10 Page 7 test.

b. Section two of the submittal shall be a copy of the test plans.

c. Section three shall be the executed test procedure and shall be divided using tabs. Each tab section shall include all pertinent information pertaining to the executed and approved test, showing date and Government representative who witnessed/approved the test.

3.5 FIELD TEST REQUIREMENTS

The UMCS contractor shall perform and document contractor start-up and field tests as required by Sections 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION and 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. The field test validates that the UMCS and building level DDC are in operation without any problems or system errors prior to starting a PVT. Validate that all software along with all hardware is installed to meet or exceed the contract document requirements. This includes all LONWORKS(r) networking and monitoring hardware and all peripherals associated with the network and hardware.

Start-up and field testing shall include:

3.5.1 Start-up Testing

All testing listed in Sections 25 10 10 and 23 09 00 shall be completed.

3.5.2 Point-to-Point Testing

All point-to-point testing of end field devices through proper input/output to graphic and operator interface shall be completed and approved.

3.5.3 Field Calibration

All field calibration shall be completed and approved.

3.5.4 Detailed Functional Testing

Detailed functional tests, verified by the Government that the system operation adheres to the Sequences of Operation.

3.5.5 Alarms and InterlocksAll alarm limits and testing shall be completed.

3.5.6 System Schedules and Setpoints

All schedule start/stops and system setpoints shall be entered, operating, and approved.

3.6 PERFORMANCE VERIFICATION TEST

3.6.1 Test Plan

Prior to the scheduling of the performance verification tests, provide the Government with a Performance Verification and Endurance Test Plan and Procedures for approval, and receive notification of approval of the Test Plan and Procedures. The plan shall include the following, as a minimum:

a. Installed system one-line block diagram, indicating servers, workstations, peripherals, network equipment, controllers, and

SECTION 25 08 10 Page 8 instrumentation.

b. Installed system hardware description.

c. Installed system software description, including any software revisions made since the factory test.

d. Listing of control and status points installed in the system; plus a table with the following information:

(1) Input and output variables.

(2) SNVTs for each variable.

(3) Expected engineering units for each variable.

(4) Node ID.

(5) Domain & subnet addressing.

e. Required passwords for each operator access level.

f. List of other test equipment.

3.6.2 Test Procedures

Develop the performance verification test procedures from the generic test procedures in ATTACHMENT A. The test procedures shall consist of detailed instructions for test setup, execution, and evaluation of test results.

Edit the generic test procedure for the existing UMCS and new building level DDC. Perform a performance verification test (PVT) on the completed UMCS and building level DDC for the Government to verify the system is completely functional. If, during testing, the system fails a portion of a test, the Government will inform the Contractor if the entire test or only the portion that failed shall be re-performed. Give the Government a written report of those items which failed, what the problem was, and what was done to correct it. Provide on-site technical support to perform the PVT. ATTACHMENT A presents the generic UMCS Performance Verification Test Procedures with the following information:

a. Test identification number.

b. Test title.

c. Objective.

d. Initial conditions (if applicable).

e. Test equipment (if required).

f. Sequence of events.

g. Expected results.

3.6.3 Test Report

Submit a final, complete PVT test report, after completing the test, consisting of the following, as a minimum:

a. Section one of the submittal shall be a short summary of the performance verification test.

b. Section two of the submittal shall be a copy of the test plans.

SECTION 25 08 10 Page 9

c. Section three shall be the executed test procedure and shall be divided using tabs. Each tab section shall include all pertinent information pertaining to the executed and approved test, showing date and Government representative who witnessed/approved the test.

3.7 ENDURANCE TESTING

3.7.1 General

Endurance Test shall be designed to demonstrate the specified overall system reliability requirement of the completed system. Conduct the Endurance Test in four phases as described below. The Endurance Test shall not be started until the Government notifies the Contractor, in writing, that the Performance Verification Tests have been satisfactorily completed, training as specified has been completed, correction of all outstanding deficiencies has been satisfactorily completed, and that the Contractor has permission to start the Endurance Test. Provide an operator to man the system eight hours per day during first shift operations, including weekends and holidays, during Phase I and Phase III Endurance testing, in addition to any Government personnel that may be made available. The Government may terminate testing at any time if the system fails to perform as specified. Upon termination of testing by the Government or by the Contractor, commence an assessment period as described for Phase II and Phase IV. Upon successful completion of the Endurance Test, submit test reports to the Government explaining in detail the nature of any failures, corrective action taken, and results of tests performed, prior to acceptance of the system. Keep a record of the time and cause of each outage that takes place during the test period.

3.7.2 Phase I

During the Phase I testing, operate the system as specified for 24 hours per day, 7 days per week, for 15 consecutive calendar days, including holidays. Do not make repairs during this phase of testing unless authorized by the Government, in writing. If the system experiences no failures during the Phase I test, proceed directly to Phase III testing, after receiving written permission from the Government.

3.7.3 Phase II

In Phase II, which occurs after the conclusion of Phase I, identify all failures, determine the causes of all failures, repair all failures, and submit a test failure report to the Government. After submitting the written report, convene a test review meeting at the job site to present the results and recommendations to the Government. The meeting shall be scheduled no earlier than five business days after receipt of the report by the Government. As a part of this test review meeting, demonstrate that all failures have been corrected by performing appropriate Performance Verification Tests. Based on the Contractor's report, the test review meeting, and the Contractor's recommendation, the Government will independently determine the restart point and may require that the Phase I test be totally or partially rerun. Do not commence any required retesting until after receipt of written notification by the Government.

3.7.4 Phase III

After the conclusion of any retesting which the Government may require, repeat the Phase II assessment as if Phase I had just been completed. If

SECTION 25 08 10 Page 10 the retest is completed without any failures, proceed directly to Phase III testing, after receiving written permission from the Government.

During Phase III testing, operate the system as specified for 24 hours per day, 7 days per week, for 15 consecutive calendar days, including holidays. Do not make repairs during this phase of testing unless authorized by the Government, in writing.

3.7.5 Phase IV

In Phase IV, which occurs after the conclusion of Phase III, identify all failures, determine the causes of all failures, repair all failures, and submit a test failure report to the Government. After submitting the written report, convene a test review meeting at the job site to present the results and recommendations to the Government. The meeting shall not be scheduled earlier than five business days after receipt of the report by the Government. As a part of this test review meeting, demonstrate that all failures have been corrected by performing appropriate Performance Verification Tests. Based on the Contractor's report, the test review meeting, and the Contractor's recommendation, the Government will independently determine the restart point and may require that the Phase III test be totally or partially rerun. Do not commence any required retesting until after receipt of written notification by the Government. After the conclusion of any retesting which the Government may require, the Phase IV assessment shall be repeated as if Phase III had just been completed. The Contractor will not be held responsible for failures resulting from the following:

a. An outage of the main power supply in excess of the capability of any backup power source, provided that the automatic initiation of all backup sources was accomplished and that automatic shutdown and restart of the UMCS performed as specified.

b. Failure of a Government-furnished communications link, provided that the LON nodes and LON routers automatically and correctly operate in the stand-alone mode as specified, and that the failure was not due to contractor furnished equipment, installation, or software.

c. Failure of existing Government-owned equipment, provided that the failure was not due to contractor-furnished equipment, installation, or software.

3.7.6 Failure Reports

Provide UMCS Endurance Test Failure Reports. UMCS Test Failure Reports shall explain in detail the nature of each failure, corrective action taken, results of tests performed. If any failures occur during Phase I or Phase III testing, recommend the point at which the Phase I or Phase III testing, as applicable, should be resumed.

3.8 ATTACHMENT A

SECTION 25 08 10 Page 11

TEST PROCEDURES

TITLE: Test Index OBJECTIVE: The following is an index of tests.

NOTES: Tests one through twenty contain specific "item(s)" that apply to Sections 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION) and 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC. The following index of tests provides a summary of which "items numbers" apply to which specification.

Test No. Test Title Section 23 09 00, Section 25 10 10

DDC for HVAC

One Initial System Equipment Verification

Items 1 through 15 Items 16 through 32

Two System Start-up Items 1 through 4 Items 5 and 6

Three Monitor and Control Software

Items 1 through 5 Not Applicable

Four Graphic Display of Data Items 1 through 18 Not Applicable

Five Graphic Navigation Scheme

Items 1 and 2 Not Applicable

Six Command Functions Items 1 through 6 Not Applicable

Seven Command Input Errors Items 1 through 6 Items 1 through 6

Eight Special Functions Item 1 Not Applicable

Nine Software Editing Tools Items 1 through 42 Items 1 through 42

Ten Scheduling Items 1 through 7 Items 8 through 10

Eleven Alarm function Items 1 through 15 item 16

Twelve Trending Items 1 through 8 Not Applicable

Thirteen Demand Limiting Items 1 through 8 Not Applicable

Fourteen Report Generation Items 1 through 6 Not Applicable

Fifteen UPS Test Items 1 through 5 Not Applicable

Sixteen CEA-709.1-D to IP Router Test

Items 1 through 3 Not Applicable

Seventeen CEA-709.1-D Router and Repeater

Not Applicable Items 1 through 4

Eighteen CEA-709.1-D Gateway Test Items 1 through 5 Items 1 through 5

Nineteen Local Display Panel Not Applicable Items 1 through 5

SECTION 25 08 10 Page 12

Test No. Test Title Section 23 09 00, Section 25 10 10

DDC for HVAC

Twenty Network Configuration Tool

Items 1 through 8 Items 1 through 8

Twenty-One Custom Tests Item 1 and 2 Item 1 and 2

SECTION 25 08 10 Page 13

PVT Checklist

OBJECTIVE:

1. Inspect/test/verify that building-level DDC system is compliant with Section 23 09 00 and capable of integration with UMCS

INITIAL REQUIREMENTS/CONDITIONS

1. The following tests shall be completed and documentation shall be submitted to the Government.

2. Date of Checklist: __________

3. Time of Checklist: __________

4. Contractor's Representative: ____________________

5. Government's Representative: ____________________

CHECKLIST PROCEDURES

Expected Item Action Item Results Approved

UMCS AND DDC FOR HVAC

1 Draft or Final Drawings submitted and As-Built Drawings approved __________

Point schedule(s) showing all required UMCS SNVTs submitted __________

Point schedules(s) showing device network addresses submitted __________

Local display panel (LDP) locations indicated on drawings submitted __________

Notes: _____________________________________________________________

2 Network Bandwidth Test Test completed, accepted, Report and a report documenting results submitted __________

Notes: _____________________________________________________________

3 Programming software Most recent version of the programming software for each type of GPPC has been submitted __________

Notes: _____________________________________________________________

SECTION 25 08 10 Page 14

Expected Item Action Item Results Approved 4 XIF Files External interface files (XIF) files for each model of LONWORKS®-based DDC hardware has been submitted __________

Notes: _____________________________________________________________

5 LNS Database Copies of the LNS database for the completed control network has been submitted __________

Notes: _____________________________________________________________

6 LNS Plug-in LNS Plug-ins for each application specific controller has been submitted __________

Notes: _____________________________________________________________

7 Start-up testing report Start-up has been successfully completed and testing report submitted __________

Controller tuning has been completed and document on point schedule __________

Calibration accuracy check completed and documented in test report __________

Actuator range check completed and documented in test report __________

Functional test to demonstrate control sequence completed and documented in test report __________

Notes: _____________________________________________________________

8 Software License Software licenses received for all software on the project __________

Notes: _____________________________________________________________

SECTION 25 08 10 Page 15

Item Action Item Results Approved

End of Test

Specific Abbreviations:

Y = Yes N = No NA = Not Applicable

SECTION 25 08 10 Page 16

TEST NUMBER: One TITLE: Initial System Equipment Verification

OBJECTIVE:

1. To verify that the hardware and software components of the system provided by the Contractor are in accordance with the contract plans and specifications and all approved submittals.

INITIAL REQUIREMENTS/CONDITIONS

1. Submittals

a. Submit a detailed list of all approved hardware with Manufacturer, model number and location. This list is based on the contract plans, specifications, change orders (if any) and approved submittals which shall be available for reference purposes during the test.

b. Submit a detailed list of all approved software with revision number and purpose of software. This list is based on the contract plans, specifications, change orders (if any) and approved submittals which shall be available for reference purposes during the test.

2. Equipment

a. Verify all equipment is functional.

3. Reference Documentation

a. List user manual documentation and sections pertaining to the testing.

4. Date of Test: __________

5. Time of Test: __________

6. Contractor's Representative: ____________________

7. Government's Representative: ____________________

TEST PROCEDURES

Expected Item Action Item Results Approved

UMCS

1 The workstation hardware is installed and complies with specification paragraph titled "Workstation Hardware". ________________ __________

Notes: _____________________________________________________________

3 The fiber optic patch panel is installed and complies with specification paragraph titled "Fiber Optic Patch Panel". ________________ __________

SECTION 25 08 10 Page 17

Item Action Item Results Approved

4 The fiber optic media converter is installed and complies with specification paragraph titled "Fiber Optic Media Converter". ________________ __________

Notes: _____________________________________________________________

5 The Ethernet switch is installed and complies with specification paragraph titled "Ethernet Switch". ________________ __________

Notes: _____________________________________________________________

6 The IP router is installed and complies with specification paragraph titled "IP Router". ________________ __________

Notes: _____________________________________________________________

7 The CEA-709.1-D to IP router is installed and complies with specification paragraph titled "CEA-709.1-D to IP Router". ________________

Notes: _____________________________________________________________

8 The CEA-709.1-D gateway is installed and complies with specification paragraph titled "CEA-709.1-D Gateway". ________________

Notes: _____________________________________________________________

12 The operating system is installed and complies with specification paragraph titled "Operating System (OS)". ________________ __________

Notes: _____________________________________________________________

SECTION 25 08 10 Page 18

Item Action Item Results Approved 13 The office automation software is installed and complies with specification paragraph titled "Office Automation Software". ________________ __________

Notes: _____________________________________________________________

14 The virus protection software is installed and complies with specification paragraph titled "Virus Protection Software". ________________ __________

Notes: _____________________________________________________________

15 The configuration server is installed and complies with specification paragraph titled "CEA-852-C Configuration Server". __________ __________

Notes: _____________________________________________________________

DDC FOR HVAC

16 The CEA-709.1-D Router is installed and complies with specification paragraph titled "CEA-709.1-D Router". ________________ __________

Notes: _____________________________________________________________

17 The CEA-709.3 Repeater is installed and complies with specification paragraph titled "CEA-709.3 Repeater". ________________ __________

Notes: _____________________________________________________________

18 The TP/FT-10 network is installed in accordance with CEA-709.3, with double-terminated bus topology. ________________ __________

Notes: _____________________________________________________________

19 Network wiring extends to the location of UMCS BPOC. ________________ __________

SECTION 25 08 10 Page 19

Item Action Item Results Approved Notes: _____________________________________________________________

20 The Gateway is installed and complies with specification paragraph titled "Gateway". ________________ __________

Notes: _____________________________________________________________

21 All control valves are installed and comply with their associated specification paragraph under the section titled "Control Valves". ________________ __________

Notes: _____________________________________________________________

22 All dampers are installed and comply with their associated specification paragraph under the section titled "Dampers". ________________ __________

Notes: _____________________________________________________________

23 All sensors are installed and comply with their associated specification paragraph under the section titled "Sensors". ________________ __________

Notes: _____________________________________________________________

24 All indicating devices are installed and comply with their associated specification paragraph under the section titled "Indicating Devices". ________________ __________

Notes: _____________________________________________________________

25 All user input devices are installed and comply with their associated specification paragraph under the section titled "User Input Devices". ________________ __________

SECTION 25 08 10 Page 20

Item Action Item Results Approved

26 All output devices are installed and comply with their associated specification paragraph under the section titled "Output Devices". ________________ __________

Notes: _____________________________________________________________

27 All multifunction devices are installed and comply with their associated specification paragraph under the section titled "Multifunction Devices". ________________ __________

Notes: _____________________________________________________________

29 All ASCs are installed and comply with the specification paragraph titled "Application Specific Controller". ________________ __________

Notes: _____________________________________________________________

30 All LDPs and laptop computers are provided and comply with the specification paragraph titled "Local Display Panel". ________________ __________

Notes: _____________________________________________________________

31 All GPPCs are installed and comply with the specification paragraph titled "General Purpose Programmable Controller". ________________ __________

Notes: _____________________________________________________________

32 LNS-based system used to address nodes, bind variables, and LNS database of network exists on system. ________________ __________

Notes: _____________________________________________________________

SECTION 25 08 10 Page 21

Item Action Item Results Approved

End of Test

Specific Abbreviations:

Y = Yes N = No

SECTION 25 08 10 Page 22

TEST NUMBER: Two TITLE: System Start-up

OBJECTIVE:

1. To validate that the system properly initializes and that the GUI properly reconnects to all communicating devices.

2. To validate that both application specific and programmable devices retain all vital information upon a power cycle.

INITIAL REQUIREMENTS/CONDITIONS

1. Submittals

a. Provide a list of all software that will be used to verify point connection at field level controllers and user interface.

b. Provide a list of all software need to verify application specific and programmable controller start-up.

2. Equipment

a. All peripherals and cables shall be connected in accordance with manufacturer's requirements.

b. The workstation shall be in the off mode.

c. All controls shall be fully functional and tested.

d. A programmable and application specific controller shall be randomly selected for the test.

3. Date of Test: __________

4. Time of Test: __________

5. Contractor's Representative: ____________________

6. Government's Representative: ____________________

TEST PROCEDURES

Expected Item Action Item Results Approved

UMCS

1 Energize the workstation. The workstation will power-up and perform its start-up procedure without generating any errors or problems. __________

a) Operating system Operating system shall be latest version of windows. __________

b) Start Network The Network Configuration Configuration Tool. Tool drawing will open. __________

c) Start the System The System plug-in will Plug-in. open. __________

d) Start the Server. The Server will start. __________

e) Start the Workstation. The Workstation will start.

The operator shall now have the ability to view data from any device on the

SECTION 25 08 10 Page 23

Item Action Item Results Approved network. __________

Notes: _____________________________________________________________

2 Check the communication Within the workstation from the server to the software, when a device is controllers. selected, dynamic points lists become visible.

Dynamic data represents success. A completion event failure message represents failure. __________

Notes: _____________________________________________________________

3 Verify on-line status. All devices shall have on-line status indicated by the workstation software (green indicator). __________

Notes: _____________________________________________________________

4 View data from the When a graphics page is graphical environment. opened, the points on the page should update.

Question marks in lieu of data reflect failure. __________

Notes: _____________________________________________________________

DDC FOR HVAC

5 Verify that configuration All configuration data in application parameters should be specific controllers is accessible. __________ written to EEPROM.

a) Open the LONWORKS® Software should open plug-in. without errors. __________

b) Note several Operator is able to view parameters such as a sample of parameters temperature setpoints (data values and setpoints).

and flow settings. __________

c) Remove power from the Device should go off-line controller for a in Network Configuration minimum of 3 minutes. Tool and workstation/server. __________

d) Replace power to the Device should return to controller. on-line status. __________

e) Using the plug-in, Parameters shall not have verify that the changed.

parameters have not __________

SECTION 25 08 10 Page 24

Item Action Item Results Approved changes.

Notes: _____________________________________________________________

6 Verify that configuration data in programmable controllers is retained after a power cycle. ________________ __________

a) From the Workstation Values of the parameters view several can be viewed from the configuration tree structure.

parameters and note the values. __________

b) Remove power for a Controller will go offline minimum of 3 minutes. in workstation software. __________

c) Replace power to the Controller will return to controller. online status. __________

d) From the Workstation Parameters values shall view the same not have changed.

configuration parameters and note the values. __________

Notes: _____________________________________________________________

End of Test

Specific Abbreviations:

Y = Yes N = No

SECTION 25 08 10 Page 25

TEST NUMBER: Three TITLE: Monitor and Control (M&C) Software Passwords

OBJECTIVE:

1. To validate that the system utilizes four basic password levels

2. To validate that each password level has the specified authority

INITIAL REQUIREMENTS/CONDITIONS

1. Submittals

a. Provide documentation of M&C user password capacity in comparison with specification.

b. Provide a complete list of all users along with their passwords and user level prior to testing.

2. Equipment

a. Server and Workstation

3. Reference Documentation

a. Provide user manual documentation for setting up passwords

4. Date of Test: __________

5. Time of Test: __________

6. Contractor's Representative: ____________________

7. Government's Representative: ____________________

TEST PROCEDURES

Expected Item Action Item Results Approved

UMCS

1 Create password for new New users shall exist in users. the server Database. __________

a) Set-up 4 users. ________________ __________

b) Assign different levels to each. ________________ __________

Notes: _____________________________________________________________

2 Demonstrate level 1 authority. ________________ __________

a) Sign in as the level 1 Sign in shall be user. successful. __________

b) Attempt to view a Action shall be possible.

system graphic. __________

c) Attempt to acknowledge Action shall be denied.

an alarm. __________

d) Attempt to configure a Action shall be denied.

trend. __________

e) Attempt to configure a Action shall be denied.

report. __________

SECTION 25 08 10 Page 26

Item Action Item Results Approved

f) Attempt to override a Action shall be denied.

point. __________

g) Attempt to configure an Action shall be denied.

alarm. __________

h) Attempt to configure a Action shall be denied.

schedule. __________

i) Attempt to configure a Action shall be denied.

demand limiting parameter. __________

j) Attempt to modify a Action shall be denied.

graphic page. __________

k) Attempt to create a Action shall be denied.

custom program. __________

Notes: _____________________________________________________________

3 Demonstrate level 2 ________________ __________ authority.

a) Sign in as the level 2 Sign in shall be successful.

user. __________

b) Attempt to view a Action shall be possible.

system graphic. __________

c) Attempt to acknowledge Action shall be possible.

an alarm. __________

d) Attempt to configure a Action shall be possible.

trend. __________

e) Attempt to configure a Action shall be possible.

report. __________

f) Attempt to override a Action shall be denied.

point. __________

g) Attempt to configure an Action shall be denied.

alarm. __________

h) Attempt to configure a Action shall be denied.

schedule. __________

i) Attempt to configure a Action shall be denied.

demand limiting parameter. __________

j) Attempt to modify a Action shall be denied.

graphic page. __________

k) Attempt to create a Action shall be denied.

custom program. __________

Notes: _____________________________________________________________

4 Demonstrate level 3 authority. ________________ __________

a) Sign in as the level 3 Sign in shall be user. successful. __________

b) Attempt to view a Action shall be possible.

system graphic. __________

c) Attempt to acknowledge Action shall be possible.

an alarm. __________

d) Attempt to configure a Action shall be possible.

SECTION 25 08 10 Page 27

Item Action Item Results Approved trend. __________

e) Attempt to configure a…