Specs_Book_4_of_4_v1.pdf

PDF 3 MB Posted

Attached to
Renovation and Modernization of Bradley Barracks, West Point, New York
Solicitation number
W912DS19B0008
Issued by

About this file

Specs Book 4 of 4_v1

View the file

Other files

File Type Posted
Bid_Abstract.pdf PDF
W912DS19B0008-0009.pdf PDF
Amendment_0008.pdf PDF
Amendment_0008_28_50_00_Emergency_Radio_Communicaiton_Enhanced_System.pdf PDF
Amendment_0007_Q22_RFI_8134159.pdf PDF
Amendment_0007.pdf PDF
Amendment_0007_Q8_Geotechnical_Report_Bradley_Barracks.pdf PDF
Amendment_0007_Q21_Tube_Bundle_Sizing_Form.pdf PDF
Amendment_0007_Q16_corian_lav_810p_RFI_8137732.pdf PDF
Amendment_0006.pdf PDF
Amendment_0005.pdf PDF
W912DS19B0008-Amendment_00004.pdf PDF
Site_Visit_Sign_In_Sheet.pdf PDF
Specs_Book_1_of_4_v1.pdf PDF
Specs_Book_2_of_4_v1.pdf PDF
Specs_Book_3_of_4_v1.pdf PDF
Amendment_0003.pdf PDF
Amendment_0001.pdf PDF
Amendment_0002.pdf PDF
W912DS-19-B-0008_Solicitation.pdf PDF
W912DS-19-B-0008_Specs_Book_4_of_4.pdf PDF
W912DS-19-B-0008_Specs_Book_3_of_4.pdf PDF
W912DS-19-B-0008_Drawings_-_Volume_4_of_5.pdf PDF
W912DS-19-B-0008_Drawings_-_Volume_5_of_5.pdf PDF
W912DS-19-B-0008_Specs_Book_1_of_4.pdf PDF
W912DS-19-B-0008_Drawings_-_Volume_3_of_5.pdf PDF
W912DS-19-B-0008_Specs_Book_2_of_4.pdf PDF
W912DS-19-B-0008_Drawings_-_Volume_1_of_5_v1.pdf PDF
W912DS-19-B-0008_Drawings_-_Volume_2_of_5.pdf PDF
Bradley_Barracks_West_Point_Security_Manifest.xlsx XLSX spreadsheet
Show all 30

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Section 25 08 10 Page 1

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 TECHNOLOGY ASSOCIATION (CTA)

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

CTA CTA-709.3 (1999; R 2015) Free-Topology Twisted-Pair

Channel Specification

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

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.

Section 25 08 10 Page 2

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.

1.2.17 LONWORKS(r)

The communication technology developed by Echelon(r) Corporation for control systems developed. The technology is based on the CTA CTA-709.1-D protocol

Section 25 08 10 Page 3 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 CTA

CTA-709.1-D and is connected to an CTA CTA-709.1-D network.

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.

Section 25 08 10 Page 4

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. 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 file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx

Section 25 08 10 Page 5 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 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" designation;

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submittals with an "S" are for inclusion in the Sustainability eNotebook, in conformance to Section 01 33 29

SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01

33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

Factory Test; G, RO

SD-06 Test Reports

UMCS and Building Level DDC Testing Sequence; G, RO

Performance Verification Test; G, RO

Endurance Testing; G, RO file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/01%2033%2029.docx file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/01%2033%2000.docx file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/01%2033%2000.docx

Section 25 08 10 Page 6

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

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.

file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx

Section 25 08 10 Page 7

(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 provided UMCS and 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. The test architecture shall mimic a two building arrangement.

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

Section 25 08 10 Page 8

3.5 FIELD TEST REQUIREMENTS

The UMCS contractor shall perform and document contractor start-up and field tests as required by Section 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 Section 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 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.

file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx

Section 25 08 10 Page 9

(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 provided UMCS and 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.

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

Section 25 08 10 Page 10

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

Section 25 08 10 Page 11

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 12

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

Section 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 DDC for HVAC

One Initial System Equipment

Verification

Items 1 through 8 Items 9 through 24

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 Report Generation Items 1 through 6 Not Applicable

Fourteen CTA CTA-709.1-D to IP Router

Test

Items 1 through 3 Not Applicable

Fifteen CTA CTA-709.1-D Router and

Repeater

Not Applicable Items 1 through 4

Sixteen CTA CTA-709.1-D Gateway

Test

Items 1 through 5 Items 1 through 5

Seventeen Local Display Panel Not Applicable Items 1 through 5 file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx

Section 25 08 10 Page 13

Test No. Test Title Section 23 09 00 DDC for HVAC

Section 25 08 10 Page 14

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

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

Notes: _____________________________________________________________

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

3 Programming software Most recent version of the programming software for each type of GPPC has been file://coe-nannv001nyc.nan.ds.usace.army.mil/USERS/E3/e3enmazy/SPECSINTACT/Jobs/20180320BRADLEY6/prntdata/Word/23%2009%2000.docx

Section 25 08 10 Page 15

4 XIF Files External interface files (XIF) files for each model of

LONWORKS®-based DDC hardware has been submitted __________

5 Start-up testing report Start-up has been successfully completed and testing report

Controller tuning has been completed and document on point schedule __________

Calibration accuracy check completed and documented in test report __________

Actuator range check

Functional test to demonstrate control sequence

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

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

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.

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

UMCS

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

2 The Server hardware is installed and complies with specification paragraph titled "Server

Hardware". ________________ __________

Section 25 08 10 Page 17

3 The fiber optic patch panel is installed and complies with specification paragraph titled

"Fiber Optic Patch Panel". ________________ __________

4 The fiber optic media converter is installed and complies with

"Fiber Optic Media Converter". ________________ __________

5 The Ethernet switch is installed paragraph titled "Ethernet

Switch". ________________ __________

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

7 The CTA CTA-709.1-D to IP router is specification paragraph titled

"CTA CTA-709.1-D to IP Router". ________________

8 The CTA CTA-709.1-D gateway is specification paragraph titled

"CTA CTA-709.1-D Gateway". ________________

Section 25 08 10 Page 18

DDC FOR HVAC

9 The CTA CTA-709.1-D Router is installed and complies with specification paragraph titled "CTA CTA-709.1-D

Router". ________________ __________

10 The CTA CTA-709.3 Repeater is installed paragraph titled "CTA CTA-709.3

Repeater". ________________ __________

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

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

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

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

15 All dampers are installed and

Section 25 08 10 Page 19 comply with their associated section titled "Dampers". ________________ __________

16 All sensors are installed and comply with their associated section titled "Sensors". ________________ __________

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

18 All user input devices are associated specification paragraph under the section titled "User

Input Devices". ________________ __________

19 All output devices are installed and comply with their associated section titled "Output Devices". ________________ __________

20 All multifunction devices are associated specification paragraph under the section titled

"Multifunction Devices". ________________ __________

21 All compressed air equipment is

Section 25 08 10 Page 20 installed and complies with their associated specification paragraph under the section titled

"Compressed Air". ________________ __________

22 All ASCs are installed and comply with the specification paragraph titled "Application Specific

Controller". ________________ __________

23 All LDPs and laptop computers are provided and comply with the

"Local Display Panel". ________________ __________

24 All GPPCs are installed and comply with the specification paragraph titled "General Purpose

Programmable Controller". ________________ __________

Section 25 08 10 Page 21

TEST NUMBER: Two

TITLE: System Start-up

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.

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.

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

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.

Section 25 08 10 Page 22

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

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

3 Verify on-line status. All devices shall have on-line status indicated by the workstation software

(green indicator). __________

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

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

Section 25 08 10 Page 23

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

parameters have not __________ changes.

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

Section 25 08 10 Page 24

TEST NUMBER: Three

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

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

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

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.

a. Server and Workstation

a. Provide user manual documentation for setting up passwords

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

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.

Section 25 08 10 Page 25 trend. __________

e) Attempt to configure a Action shall be denied.

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

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

4 Demonstrate level 3

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

b) Attempt to view a Action shall be possible.

system graphic. __________

Section 25 08 10 Page 26

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

point. __________

g) Attempt to configure an Action shall be possible.

alarm. __________

h) Attempt to configure a Action shall be possible.

schedule. __________

i) Attempt to configure a Action shall be possible.

demand limiting parameter. __________

j) Attempt to modify a Action shall be denied.

graphic page. __________

5 Demonstrate level 4

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.

trend. __________

e) Attempt to configure a Action shall be possible.

report. __________

f) Attempt to override a Action shall be possible.

point. __________

g) Attempt to configure an Action shall be possible.

alarm. __________

h) Attempt to configure a Action shall be possible.

schedule. __________

i) Attempt to configure a Action shall be possible.

demand limiting parameter. __________

j) Attempt to modify a Action shall be possible.

graphic page program. __________

k) Attempt to create a Action shall be possible.

Section 25 08 10 Page 27

Section 25 08 10 Page 28

TEST NUMBER: Four

TITLE: Graphic Display of Data

1. To validate that floor plans and equipment can be graphically displayed through GUI.

2. To validate the proper display of alarms on GUI.

3. To validate the proper display of trend data on GUI.

a. Provide hard copies of "snap shots" of sample graphics pages prior to testing.

a. Complete all graphics.

4. Notes

a. Different types of data and states should be clearly distinguishable from each other.

5. Date of Test: __________

6. Time of Test: __________

7. Contractor's Representative: ____________________

8. Government's Representative: ____________________

Item Action Item Results Approved

1 Demonstrate the use of a Equipment shall be three dimensional represented in a three representation of a dimensional manner.

mechanical system. __________

2 Demonstrate the Dynamic real time data presentation of real time shall be presented on a data. graphics page. __________

Section 25 08 10 Page 29

3 Demonstrate the A user defined parameter presentation of user such as a setpoint shall be entered data. presented on a graphics page.

Different types of data and states should be clearly distinguishable from each other. __________

4 Demonstrate the An indication of override presentation of a point condition shall be viewable in override. on the graphic page.

Different types of data and states should be clearly distinguishable from each other. __________

5 Demonstrate the An indication of the alarm presentation of a device state shall be viewable on in the alarm state. the graphic page. Different types of data and states should be clearly

6 Demonstrate the An indication of out of range presentation of data that condition shall be viewable is out of range. on the graphic page.

Different types of data and states should be clearly

7 Demonstrate the An indication of missing data presentation of missing shall be viewable on the data (controller is graphic page. Different offline). types of data and states should be clearly distinguishable from each

Section 25 08 10 Page 30

8 Demonstrate an error An error message shall be message when the operator displayed.

attempts to execute in improper command. __________

9 Demonstrate point and click Operator shall be able to access to context sensitive easily access context help. sensitive help using the mouse. __________

10 Demonstrate point and click Operator shall be able to access to an engineering access an engineering diagram. diagram using the mouse. __________

11 Demonstrate the creation of Operator shall be able to an engineering diagram. create an engineering diagram. __________

12 Demonstrate the printing of Operator shall be able to a prepared report. print a report using the mouse. __________

13 Demonstrate the display of Operator shall be able to one or more points. request the display of one or more points. __________

14 Demonstrate the operator Operator shall be able to override of a point. override a point. __________

Section 25 08 10 Page 31

15 Demonstrate the Operator shall be able to modification of a modify a time schedule.

time schedule. __________

16 Demonstrate the execution Operator shall be able to of a report. initiate a report. __________

17 Demonstrate the Operator shall be able to presentation of an view an alarm with all of alarm to include: the required data. __________

a) Identification ________________ __________

b) Date and time ________________ __________

c) Alarm Type ________________ __________

d) Set Points ________________ __________

e) Units ________________ __________

f) Current Value ________________ __________

g) Priority ________________ __________

h) Associated message &

Secondary message ________________ __________

18 Demonstrate the Operator shall be able to presentation of view real time trend data real time trend data. as a function of time. __________

Section 25 08 10 Page 32

TEST NUMBER: Five

TITLE: Graphic Navigation Scheme

1. To validate hierarchical graphic displays from main screen to end devices.

a. Provide a hierarchical block diagram of the system network prior to

a. Have all programming completed to demonstrate graphic display.

1 Demonstrate the creation Operator shall be able to of a hierarchical tree organize point data graphic structure for the display in a hierarchical presentation of point tree structure based on any data with at least five organization desired.

levels.

A typical organization could be:

- Installation

- Building

- Building sub area

- Main System-Unit

- Terminal Unit __________

2 Demonstrate the creation Operator shall be able or of a hierarchical organize the graphical navigation structure for navigation from page to

Section 25 08 10 Page 33 the graphic pages. page using any hierarchical structure desired.

Examples:

Home page to building 1

Building 1 to AHU 1

Building 1 back to Home Page

Building 1 to 1st Floor Plan

AHU 1 back to Building 1

AHU 1 back to Home Page

AHU 1 to Terminal Unit

Summary

1st Floor Plan back to

Building 1

1st Floor Plan back to

Home Page

1st Floor Plan to Any

Terminal Device

Terminal Unit Summary back to AHU 1

Terminal Unit Summary back to Building 1

Terminal Unit Summary back to Home Page

Terminal Unit Summary to

Individual Device __________

Section 25 08 10 Page 34

TEST NUMBER: Six

TITLE: Command Functions

1. To demonstrate the functionality and ability to execute command to the end devices.

a. Provide documentation of all command functions prior to testing.

a. Have all command functions programmed and functional.

1 From the tree structure, The modified value shall be modify a parameter such as downloaded to the controller a set point. without delay and the controller performance shall be viewable by the monitoring of other dynamic points. __________

2 From a graphic page, modify The modified value shall be a parameter such as a set downloaded to the controller point. without delay and the controller performance shall be viewable by the monitoring of dynamic points. __________

Section 25 08 10 Page 35

3 From the tree structure, The analog output point place an analog output shall accept the assigned point under operator value and ignore changes override and assign a from application logic until fixed value. the point is taken out of override. __________

4 From a graphic page, place The analog output point shall an analog output point accept the assigned value and under operator override ignore changes from and assign a fixed value. application logic until the point is taken out of override. __________

5 From the tree structure, The digital output point shall place a digital output accept the assigned value and point under operator ignore changes from application override and assign a logic until the point is taken fixed value. out of override. __________

6 From a graphic page, place The digital output point shall a digital output point accept the assigned value and under operator override ignore changes from application and assign a fixed value. logic until the point is taken out of override. __________

Section 25 08 10 Page 36

TEST NUMBER: Seven

TITLE: Command Input Errors

1. To validate that the system ensures the necessary authority for command inputs

2. To validate that the system can control the range of command input values

a. Provide all command input error messages prior to testing.

a. UMCS and DDC hardware and software

1 Login using a password Login occurs. __________ with point command.

2 Request a display of a The system displays the

SNVT. controllers SNVT value. __________

3 Override the SNVT point The SNVT value override to a selected value. changes the value in the controller. __________

Section 25 08 10 Page 37

4 Release the override of The SNVT value returns to a SNVT. normal. __________

5 For an nvi to a The value will go the controller with a limit of maximum of 80.

50 to 80, command the nvi to a value of 90. __________

6 For an nvi to a The operator will be denied controller for which the the ability to command the operator only has read nvi to any value.

privileges, command the nvi to a value of 90. __________

Section 25 08 10 Page 38

TEST NUMBER: Eight

TITLE: Special Functions

1. Verify system has special integration as defined.

a. Provide documentation of all integrations prior to testing.

a. Have all UMCS and DDC hardware and software programmed, integrated, and completed.

1 Verify that a building Data from the other vendors that uses controls from a controllers shall be integrated vendor other than the one into the GUI and the same being installed can be functionality that would exist integrated into the GUI if the controllers were from without any loss of the same manufacture shall functionality. exist.

(A simulated building will be set up using an IP-L router and controllers from

Honeywell, TAC, Trane, etc.) __________

Section 25 08 10 Page 39

Section 25 08 10 Page 40

TEST NUMBER: Nine

TITLE: Software editing tools

1. To validate the performance of the M & C application programming tool for the GPPC.

2. To validate the performance of the display editing tool.

3. To validate the performance of the report generation display tool.

a. Provide documentation and a backup softcopy of the editing tool prior to testing.

b. Provide documentation of any future software upgrade versions that pertain to the software-editing tool.

a. Have working knowledge of the full capability of the software-editing tool.

UMCS and DDC for HVAC

1 Demonstrate the Operator shall be able to programming of an override use the programmed function function in a GPPC. to override an output point in a GPPC. __________

2 Demonstrate software that Operator shall be able to enables the monitoring of monitor points from a GPPC.

data from a GPPC. __________

Section 25 08 10 Page 41

3 Demonstrate timer Control logic shall honor functions within the built in timers.

applications of GPPC. __________

a) delay on ________________ __________

b) delay off ________________…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.