A21)_W912PM-17-B-0011_P0003_Amendment.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

Solicitation W912PM-17-B-0011 is hereby amended as follow s:

A) See Technical Summary of Changes.

B) The date and time for receipt of bids is not extended.

C) All other terms, provisions, and conditions of the solicitation remain unchanged.

///////////////////////////////////////////////////////////LAST ITEM///////////////////////////////////////////////////////////////

1. CONTRACT ID CODE PAGE OF PAGES

J 1 2

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 16-Jun-2017

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W912PM-17-B-0011

X 9B. DATED (SEE ITEM 11)

12-May-2017

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

16-Jun-2017

CODE

U S ARMY CORPS OF ENGINEERS, WILMINGTON

WILMINGTON DISTRICT

ATTN: CONTRACTING DIVISION

69 DARLINGTON AVE

WILMINGTON NC 28403-1343

W912PM 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912PM-17-B-0011

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SECTION 00 00 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

SUMMARY OF CHANGES

(End of Summary of Changes)

W912PM-17-B-0011

Building 3-2847 Amendment 0003

Technical Summary of Changes

SPECIFICATIONS

The revised Table of Contents and Sections listed below (revised by Amendment No. 0003) are hereby added to and made a part of the solicitation.

a. TABLE OF CONTENTS – Technical Sections.

b. 01 33 00 – ATTACHMENT 1 - ENG FORM 4288 (Page 17).

c. The following section have been revised:

23 09 00

d. The following sections have been deleted

25 08 10 UTILITY MONITORING AND CONTROL SYSTEM TESTING

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

AND INTEGRATION

NOTE:

Revised or added information is underlined and deleted information is struck out. Revisions can be located in the appropriate volume of specifications by searching for an asterisk and amendment number (i.e., *3(beginning and ending of revision/addition)).

The text changes may have necessitated reformatting of subsequent text or pages. If this is the case, those pages have also been issued as amended pages but are not underlined or bold text.

DRAWINGS

The following drawing have been revised:

M-602 Coordination Note 7 has been revised

-- End of Summary of Changes- -

Encls As Stated murban Rectangle murban Rectangle murban Text Box ****Amendment 0003****

Technical Provisions 24 April 2017 ****Amendment 0001****

BUILDING 3-2847 RECONFIGURATION, JSOC

FT. BRAGG, NC Project #SC-00009-17

SECTION DESCRIPTION

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 41 16.00 10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL CABINETS

06 61 16 SOLID SURFACING FABRICATIONS

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 11 16 ALUMINUM DOORS AND FRAMES

08 14 00 WOOD DOORS

08 34 97 SCIF DOOR ASSEMBLIES

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

DIVISION 09 - FINISHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 24 23 PORTLAND-CEMENT PLASTER

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC AND QUARRY TILING

09 51 00 ACOUSTICAL CEILINGS

09 65 00 RESILIENT FLOORING

09 68 00 CARPETING

09 90 00 PAINTS AND COATINGS

DIVISION 10 - SPECIALTIES

10 14 00.20 INTERIOR SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS

DIVISION 12 - FURNISHINGS

12 21 00 WINDOW BLINDS

FOUO

FOUO

murban Rectangle murban

****Amendment 0001****

BUILDING 3-2847 RECONFIGURATION, JSOC

FT. BRAGG, NC Project #SC-00009-17

SECTION DESCRIPTION

DIVISION 21 - FIRE SUPPRESSION

21 13 00.00 40 FIRE-SUPPRESSION SPRINKLER SYSTEMS

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

22 07 19.00 40 PLUMBING PIPING INSULATION

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

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

23 01 30.41 HVAC SYSTEM CLEANING

23 03 00.00 20 BASIC MECHANICAL MATERIALS AND METHODS

23 05 15 COMMON PIPING FOR HVAC

23 05 48.00 40 VIBRATION AND SEISMIC CONTROLS FOR HVAC PIPING AND EQUIPMENT

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

CONTROL SYSTEMS

23 21 13.00 20 LOW TEMPERATURE WATER (LTW) HEATING SYSTEM

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

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

23 73 13.00 40 MODULAR OUTDOOR CENTRAL-STATION AIR-HANDLING UNITS

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 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 16.00 40 PANELBOARDS

26 51 00 INTERIOR LIGHTING

FOUO

FOUO

murban Rectangle murban Line murban Line murban Line murban Text Box murban Text Box ****Amendment 0003**** murban Text Box ****Amendment 0003**** murban

****Amendment 0001****

BUILDING 3-2847 RECONFIGURATION, JSOC

FT. BRAGG, NC Project #SC-00009-17

SECTION DESCRIPTION

DIVISION 27 - COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

ATTACHMENT A – ASBESTOS SURVEY

ATTACHMENT B – GFCI EQUIPMENT DATA

-- End of Project Table of Contents --

FOUO

FOUO

murban Rectangle murban

SUBMITTAL REGISTER (ER 415-1-10) TITLE AND LOCATION DATE

CONTRACTOR CONTRACT NUMBER

ACTIVITY

No.

TRANS-

MITTAL

No.

ITEM

No.

SPEC

PARAGRAPH

No.

DESCRIPTION OF

SUBMITTAL

TYPE OF SUBMITTAL

CLASSI-

FICATION

FIO

GA, DA,

CR, or S

REVIEWER

OFFICE / NAME

CONTRACTOR

SCHEDULE DATES

CONTRACTOR

ACTION

GOVERNMENT

ACTION

SUBMIT

NEEDED

BY

APPROVAL

NEEDED

BY

MATERIAL

NEEDED

BY

CODE

CORPS

RECEIVED

DATE

CODE

CORPS

RETURNED

DATE

Building 3-2847 Reconfiguration, JSOC

W912PM-17-B-0011 NA

06 Jun 2017

SORT : SECTION & ITEMRANGE : ALL

13 23 73 13.00 40 2.1 Spare Parts CERTIFICATES GA

14 23 73 13.00 40 3.3.1 Operation and Maintenance Manuals O&M DATA GA

15 23 73 13.00 40 1.5 Warranty CLOSEOUT SUBMTL GA

SECTION - 25 08 10 UTILITY MONITORING AND CONTROL SYSTEM TESTING

1 25 08 10 3.4 Factory Test PRECON SUBMTL GA

2 25 08 10 3.1 UMCS and Building Level DDC Testing SequTEST REPORTS FIO

3 25 08 10 3.6 Performance Verification Test TEST REPORTS GA

4 25 08 10 3.7 Endurance Testing TEST REPORTS FIO

SECTION - 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS)

1 25 10 10 3.2.3 UMCS Contractor Design Drawings SHOP DRAWINGS FIO

2 25 10 10 3.2.4 Draft As-Built Drawings SHOP DRAWINGS FIO

3 25 10 10 3.2.4 Final As-Built Drawings SHOP DRAWINGS FIO

4 25 10 10 2.1.5 Product Data Sheets PRODUCT DATA FIO

5 25 10 10 3.2.2 Certificate of Networthiness Documentati PRODUCT DATA FIO

6 25 10 10 3.2.1 UMCS IP Network Bandwidth Usage EstimateDESIGN DATA FIO

7 25 10 10 1.6 Pre-Construction QC Checklist TEST REPORTS FIO

8 25 10 10 1.6 Post-Construction QC Checklist TEST REPORTS FIO

9 25 10 10 3.1 Existing Conditions Report TEST REPORTS FIO

10 25 10 10 3.6 Start-Up and Start-Up Testing Report TEST REPORTS GA

11 25 10 10 3.7.1 PVT Phase I Procedures TEST REPORTS FIO

12 25 10 10 3.7.2 PVT Phase I Report TEST REPORTS GA

13 25 10 10 3.7.3 PVT Phase II Report TEST REPORTS GA

14 25 10 10 1.7 Operation and Maintenance (O&M) Instruct O&M DATA FIO

15 25 10 10 3.8.7.1 Preventive Maintenance Work Plan O&M DATA FIO

16 25 10 10 3.9.1 Basic Training Documentation O&M DATA FIO

17 25 10 10 3.9.1 Advanced Training Documentation O&M DATA FIO

18 25 10 10 3.9.1 Refresher Training Documentation O&M DATA FIO

19 25 10 10 1.6 Closeout QC Checklist CLOSEOUT SUBMTL FIO

SECTION - 26 05 00.00 40 COMMON WORK RESULTS FOR ELECTRICAL

1 26 05 00.00 40 2.1 Material, Equipment, and Fixture Lists PRECON SUBMTL FIO

2 26 05 00.00 40 2.1.1 Conduits and Raceways PRODUCT DATA GA

3 26 05 00.00 40 2.1.2 Wire and Cable PRODUCT DATA GA

4 26 05 00.00 40 3.2.1.5 Splices and Connectors PRODUCT DATA GA

5 26 05 00.00 40 2.1.3 Switches PRODUCT DATA GA

6 26 05 00.00 40 2.1.4 Receptacles PRODUCT DATA GA

K7EPEOAF

Cross-Out

Building 3-2847 reconfiguration, JSOC 2847RENOVATION

SC-00009-17

Section 23 09 00 Page 1

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

11/15

PART 1 GENERAL

1.1 SUMMARY

Provide a complete Direct Digital Control (DDC) system, suitable for the control of the heating, ventilating and air conditioning (HVAC) and other building-level systems as indicated and shown and in accordance with

Section 23 09 23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS and other referenced Sections.

1.1.1 System Requirements

Provide systems meeting the requirements this Section and other Sections referenced by this Section, and which have the following characteristics:

a. The system implements the control sequences of operation shown in the

Contract Drawings using DDC hardware to control mechanical and electrical equipment

b. The system meet the requirements of this specification as a stand-alone system and does not require connection to any other system.

c. Control sequences reside in DDC hardware in the building. The building control network is not dependent upon connection to a Utility

Monitoring and Control System (UMCS) Front End or to any other system for performance of control sequences. To the greatest extent practical, the hardware performs control sequences without reliance on the building network.

d. The hardware is installed such that individual control equipment can be replaced by similar control equipment from other equipment manufacturers with no loss of system functionality.

e. All necessary documentation, configuration information, programming tools, programs, drivers, and other software are licensed to and otherwise remain with the Government such that the Government or their agents are able to perform repair, replacement, upgrades, and expansions of the system without subsequent or future dependence on the

Contractor, Vendor or Manufacturer.

f. Sufficient documentation and data, including rights to documentation and data, are provided such that the Government or their agents can execute work to perform repair, replacement, upgrades, and expansions of the system without subsequent or future dependence on the

Contractor, Vendor or Manufacturer.

g. Hardware is installed and configured such that the Government or their agents are able to perform repair, replacement, and upgrades of individual hardware without further interaction with the Contractor, Vendor or Manufacturer.

Section 23 09 00 Page 2

h. All UMCS network and graphical development, inculding all integration as required and specified herein fron the building level EEA 852.C router to the existing UMCS, shall be performed by the site enterprise developer and included in the scope of work.

1.1.2 End to End Accuracy

Select products, install and configure the system such that the maximum error of a measured value as read from the DDC Hardware over the network is less than the maximum allowable error specified for the sensor or instrumentation.

1.1.3 Verification of Dimensions

After becoming familiar with all details of the work, verify all dimensions in the field, and advise the Contracting Officer of any discrepancy before performing any work.

1.1.4 Drawings

The Government will not indicate all offsets, fittings, and accessories that may be required on the drawings. Carefully investigate the mechanical, electrical, and finish conditions that could affect the work to be performed, arrange such work accordingly, and provide all work necessary to meet such conditions.

1.2 RELATED SECTIONS

Related work specified elsewhere:

a. Section 23 09 23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS

b. Section 23 09 13 INSTRUMENTAION AND CONTROL DEVICES FOR HVAC

c. Section 23 09 23 SEQUENCES OF OPERATION FOR HVAC CONTROLS

1.3 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE FUN IP (2013; Addenda and Corrigendum 2013)

Fundamentals Handbook, I-P Edition

Section 23 09 00 Page 3

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

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE C62.41 (1991; R 1995) Recommended Practice on Surge

Voltages in Low-Voltage AC Power Circuits

NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)

NEMA 250 (2014) Enclosures for Electrical Equipment

(1000 Volts Maximum)

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2017) National Electrical Code

NFPA 90A (2015) Standard for the Installation of Air

Conditioning and Ventilating Systems

UNDERWRITERS LABORATORIES (UL)

UL 5085-3 (2006; Reprint Nov 20121) Low Voltage

Transformers - Part 3: Class 2 and Class 3

Transformers

1.4 DEFINITIONS

The following list of definitions includes terms used in Sections referenced by this Section and are included here for completeness.

The definitions contained in this Section may disagree with how terms are defined or used in other documents, including documents referenced by this

Section. The definitions included here are the authoritative definitions for this Section and all Sections referenced by this Section.

1.4.1 Alarm Generation

Alarm Generation is the monitoring of a value, comparison of the value to alarm conditions and the creation of an alarm when the conditions set for the alarm are met. Note that this does NOT include delivery of the alarm to the final destination (such as a user interface).

1.4.2 Application Generic Controller (AGC)

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

1.4.3 Application Specific Controller (ASC)

Section 23 09 00 Page 4

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

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

'Digital' is sometimes used interchangeably with 'binary'.

1.4.5 Binding

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

1.4.6 Building Control Network (BCN)

The network connecting all DDC Hardware within a building (or specific group of buildings).

1.4.7 Building Point of Connection (BPOC)

A FPOC for a Building Control System. (This term is being phased out of use in preference for FPOC but is still used in some specifications and criteria. When it was used, it typically referred to a piece of control hardware. The current FPOC definition typically refers instead to IT hardware.)

1.4.8 Channel

A portion of the control network consisting of one or more segments connected by repeaters. Channels are separated by routers. The device quantity limitation is dependent on the topology/media and device type. For example, a TP/FT-10 network with locally powered devices is limited to 128 devices per channel.

1.4.9 Commandable

See Overridable.

1.4.10 Configurable

A property, setting, or value is configurable if it can be changed via hardware settings on the device, via the use of engineering software or over the control network from the front end, and is retained through (after) loss of power.

1.4.11 Configuration Property

Controller parameter used by the application which is usually set during installation/testing and seldom changed. For example, the P and I settings of a P-I control loop. Also see paragraph STANDARD CONFIGURATION PROPERTY

TYPE (SCPT).

1.4.12 Control Logic Diagram

Section 23 09 00 Page 5

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

1.4.13 Digital Controller

An electronic controller, usually with internal programming logic and digital and analog input/output capability, which performs control functions.

1.4.14 Direct Digital Control (DDC)

Digital controllers performing control logic. Usually the controller directly senses physical values, makes control decisions with internal programs, and outputs control signals to directly operate switches, valves, dampers, and motor controllers.

1.4.15 Domain

A grouping of up to 32,385 nodes that can communicate directly with each other. (Devices in different domains cannot communicate directly with each other.) See also Node Address.

1.4.16 Explicit Messaging

A non-standard and often vendor (application) specific method of communication between devices where each message contains a message code that identifies the type of message and the devices use these codes to determine the action to take when the message is received.

1.4.17 External Interface File (XIF)

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

1.4.18 Field Point of Connection (FPOC)

The FPOC is the point of connection between the UMCS IP Network and the field control network (either an IP network, a non-IP network, or a combination of both). The hardware at this location which provides the connection is generally an IT device such as a switch, IP router, or firewall.

In general, the term "FPOC Location" means the place where this connection occurs, and "FPOC Hardware" means the device that provides the connection.

Sometimes the term "FPOC" is used to mean either and its actual meaning

(i.e. location or hardware) is determined by the context in which it is used.

1.4.19 Functional Profile

A standard description, defined by LonMark, of one or more LonMark Objects used to classify and certify devices.

1.4.20 Gateway

Section 23 09 00 Page 6

A device that translates from one protocol application data format to another. Devices that change only the transport mechanism of the protocol -

"translating" from TP/FT-10 to Ethernet/IP or from BACnet MS/TP to BACnet over IP for example - are not gateways as the underlying data format does not change. Gateways are also called Communications Bridges or Protocol

Translators.

1.4.21 General Purpose Programmable Controller (GPPC)

Unlike an ASC or AGC, a GPPC is not furnished with a fixed application program and does not have a fixed ProgramID or XIF file. A GPPC can be (re-

)programmed, usually using vendor-supplied software. When a change to the program affects the external interface (and the XIF file) the ProgramID will change.

1.4.22 IEEE 802.3 Ethernet

A family of local-area-network technologies providing high-speed networking features over various media, typically Cat 5, 5e or Cat 6 twisted pair copper or fiber optic cable.

1.4.23 Internet Protocol (IP, TCP/IP, UDP/IP)

A communication method, the most common use is the World Wide Web. At the lowest level, it is based on Internet Protocol (IP), a method for conveying and routing packets of information over various LAN media. Two common protocols using IP are User Datagram Protocol (UDP) and Transmission Control

Protocol (TCP). UDP conveys information to well-known "sockets" without confirmation of receipt. TCP establishes connections, also known as

"sessions", which have end-to-end confirmation and guaranteed sequence of delivery.

1.4.24 Input/Output (I/O)

Physical inputs and outputs to and from a device, although the term sometimes describes network or "virtual" inputs or outputs. See also

"Points".

1.4.25 I/O Expansion Unit

An I/O expansion unit provides additional point capacity to a digital controller

1.4.26 IP subnet

A group of devices which share a defined range IP addresses. Devices on a common IP subnet can share data (including broadcasts) directly without the need for the traffic to traverse an IP router.

1.4.27 Local-Area Network (LAN)

A communication network that spans a limited geographic area and uses the same basic communication technology throughout.

1.4.28 Local Display Panels (LDPs)

Section 23 09 00 Page 7

A DDC Hardware with a display and navigation buttons, and must provide display and adjustment of points as shown on the Points Schedule and as indicated.

1.4.29 LonMark

See paragraph LONMARK INTERNATIONAL. Also, a certification issued by

LonMark International to CEA-709.1-D devices.

1.4.30 LonMark International

Standards committee consisting of numerous independent product developers, system integrators and end users dedicated to determining and maintaining the interoperability guidelines for LonWorks. Maintains guidelines for the interoperability of CEA-709.1-D devices and issues the LonMark Certification for CEA-709.1-D devices.

1.4.31 LonMark Interoperability Association

See paragraph LONMARK INTERNATIONAL.

1.4.32 LonMark Object

A collection of network variables, configuration properties, and associated behavior defined by LonMark International and described by a Functional

Profile. It defines how information is exchanged between devices on a network (inputs from and outputs to the network).

1.4.33 LonWorks

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

1.4.34 LonWorks Network Services (LNS)

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

1.4.35 LonWorks Network Services (LNS) Plug-in

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

1.4.36 MAC Address

Media Access Control address. The physical device address that identifies a device on a Local Area Network.

1.4.37 Monitoring and Control (M&C) Software

The UMCS 'front end' software which performs supervisory functions such as alarm handling, scheduling and data logging and provides a user interface for monitoring the system and configuring these functions.

1.4.38 Network Variable

Section 23 09 00 Page 8

See paragraph STANDARD NETWORK VARIABLE TYPE (SNVT).

1.4.39 Network Configuration Tool

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

1.4.40 Node

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

1.4.41 Node Address

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

Node ID).

1.4.42 Node ID

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

1.4.43 Operator Configurable

For LNS LonWorks systems, Operator Configurable is defined the same as

Configurable. See paragrapyh CONFIGURABLE.

1.4.44 Override

Changing the value of a point outside of the normal sequence of operation where the change has priority over the sequence and where there is a mechanism for releasing the change such that the point returns to the normal value. Overrides persist until released or overridden at the same or higher priority but are not required to persist through a loss of power.

1.4.45 Performance Verification Test (PVT)

The procedure for determining if the installed BAS meets design criteria prior to final acceptance. The PVT is performed after installation, testing, and balancing of mechanical systems. Typically the PVT is performed by the Contractor in the presence of the Government.

1.4.46 Polling

A device periodically requesting data from another device.

1.4.47 Points

Physical and virtual inputs and outputs. See also paragraph INPUT/OUTPUT

(I/O).

1.4.48 Program ID

Section 23 09 00 Page 9

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

1.4.49 Proportional, Integral, and Derivative (PID) Control Loop

Three parameters used to control modulating equipment to maintain a setpoint. Derivative control is often not required for HVAC systems (leaving

"PI" control).

1.4.50 Repeater

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

1.4.51 Router

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

1.4.52 Segment

A 'single' section of a control network that contains no repeaters or routers. There is generally a limit on the number of devices on a segment, and this limit is dependent on the topology/media and device type. For example, a TP/FT-10 network with locally powered devices is limited to 64 devices per segment.

1.4.53 Service Pin

A hardware push-button on a device which causes the device to broadcast a message (over the control network) containing its Node ID and Program ID.

1.4.54 Standard Configuration Property Type (SCPT)

Pronounced skip-it. A standard format type (maintained by LonMark

International) for Configuration Properties.

1.4.55 Standard Network Variable Type (SNVT)

Pronounced snivet. A standard format type (maintained by LonMark

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

1.4.56 Subnet

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

Section 23 09 00 Page 10

1.4.57 TP/FT-10

A Free Topology Twisted Pair network defined by CEA-709.3. This is the most common media type for a CEA-709.1-D control network.

1.4.58 TP/XF-1250

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

1.4.59 User-defined Configuration Property Type (UCPT)

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

1.4.60 User-defined Network Variable Type (UNVT)

A network variable format defined by the device manufacturer. Note that

UNVTs create non-standard communications (other vendor's devices may not correctly interpret it) and may close the system and therefore are not permitted by this specification.

1.4.61 UMCS

UMCS stands for Utility Monitoring and Control System. The term refers to all components by which a project site monitors, manages, and controls real-time operation of HVAC and other building systems. These components include the UMCS "front-end" and all field building control systems connected to the front-end. The front-end consists of Monitoring and Montrol Software (user interface software), browser-based user interfaces and network infrastructure.

The network infrastructure (the "UMCS Network"), is an IP network connecting multiple building or facility control networks to the Monitoring and Control

Software.

1.4.62 UMCS NETWORK

The UMCS Network connects multiple building or facility control networks to the Monitoring and Control Software.

1.5 PROJECT SEQUENCING

TABLE I: PROJECT SEQUENCING lists the sequencing of submittals as specified in paragraph SUBMITTALS (denoted by an 'S' in the 'TYPE' column) and activities as specified in PART 3 EXECUTION (denoted by an 'E' in the 'TYPE' column). TABLE I does not specify overall project milestone and completion dates; these dates are specified in the contract documents.

a. Sequencing for Submittals: The sequencing specified for submittals is the deadline by which the submittal must be initially submitted to the

Government. Following submission there will be a Government review period as specified in Section 01 33 00 SUBMITTAL PROCEDURES. If the submittal is not accepted by the Government, revise the submittal and resubmit it to the Government within 14 days of notification that the submittal has been rejected. Upon resubmittal there will be an

Section 23 09 00 Page 11 additional Government review period. If the submittal is not accepted the process repeats until the submittal is accepted by the Government.

b. Sequencing for Activities: The sequencing specified for activities indicates the earliest the activity may begin.

c. Abbreviations: In TABLE I the abbreviation AAO is used for 'after approval of' and 'ACO' is used for 'after completion of'.

TABLE I. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)

1 S Existing Conditions Report

2 S DDC Contractor Design Drawings

3 S Manufacturer's Product Data

4 S Pre-construction QC Checklist

5 E Install Building Control System AAO #1 thru #4

6 E Start-Up and Start-Up Testing ACO #5

7 S Post-Construction QC Checklist ACO #6

8 S Programming Software

Configuration Software

Programming Software

Configuration Software

XIF Files

LNS Plug-Ins

ACO #6

9 S Draft As-Built Drawings

Draft LNS Database

ACO #6

10 S Start-Up Testing Report ACO #6

11 S PVT Procedures before schedule start of

#12 and AAO #10

Section 23 09 00 Page 12

TABLE I. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)

12 E Execute PVT AAO #9 and #11

13 S PVT Report ACO #12

14 S Controller Application Programs

Controller Configuration Settings

Final LNS Database

AAO #13

15 S Final As-Built Drawings AAO #13

16 S O&M Instructions AAO #15

17 S Training Documentation AAO #10 and before scheduled start of #18

18 E Training AAO #16 and #17

19 S Closeout QC Checklist ACO #18

1.6 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for Contractor Quality Control approval. 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 SUBMITTAL

PROCEDURES:

SD-02 Shop Drawings

DDC Contractor Design Drawings; G

Section 23 09 00 Page 13

DDC Contractor Design Drawings as a single complete package: 4 hard copies and 2 copies on CDROM. Submit hardcopy drawings on ISO

A1 34 by 22 inchesorA3 17 by 11 inches sheets, and electronic drawings in PDF and in Microstation format. In addition, submit electronic drawings in editable Excel format for all drawings that are tabular, including but not limited to the Point Schedule and

Equipment Schedule.

Final As-Built Drawings; G

Final As-Built Drawings as a single complete package: 4 hard copies and 2 copies on CDROM. Submit hardcopy drawings on ISO A1

34 by 22 inchesorA3 17 by 11 inches sheets, and electronic drawings in PDF and in Microstation format. In addition, submit electronic drawings in editable Excel format for all drawings that are tabular, including but not limited to the Point Schedule and

Equipment Schedule.

SD-03 Product Data

Certificate of Networthiness Documentation; G

Submit Certificate of Networthiness Documentation in PDF format on CD-ROM.

Programming Software; G

Submit Programming Software on CD-ROM as a Technical Data

Package. Submit 4 hard copies of the software user manual for each piece of software.

Controller Application Programs; G

Submit Controller Application Programs on CD-ROM as a Technical

Data Package. Include on the CD-ROM a list or table of contents clearly indicating which application program is associated with each device. Submit 2 copies of the Controller Application Programs

CD-ROM.

Configuration Software; G

Submit Configuration Software on CD-ROM as a Technical Data

Package. Submit 4 hard copies of the software user manual for each piece of software.

Manufacturer's Product Data; G

Submit Manufacturer's Product Data on CD-ROM.

XIF files; G

Submit external interface files (XIF files) as a technical data package for each model of DDC Hardware provided under this specification. Submit XIF files on CD-ROM.

Draft LNS Database; G

Section 23 09 00 Page 14

Submit two copies of the fully commissioned, valid draft LNS

Database (including all LNS credits) as a Technical Data Package.

Submit each copy on a CD-ROM and clearly mark the CD-ROM identifying it as the LNS Database for the work covered under this specification and with the date of the most recent database modification.

Final LNS Database; G

Submit two copies of the fully commissioned, valid as-built LNS

Database (including all LNS credits) for the complete control network provided under this specification as a Technical Data

Package. Submit each copy on CD-ROM and clearly mark the CD-ROM identifying it as the LNS Database for the work covered under this specification and with the date of the most recent database modification.

LNS Plug-ins; G

Submit LNS Plug-ins on CD-ROM as a Technical Data Package.

Include on the CD-ROM a list or table of contents clearly indicating which files are associated with each device.

SD-06 Test Reports

Start-Up Testing Report; G

PVT Procedures; G

PVT Report; G copies of the PVT Report. The PVT Report may be submitted as a Technical Data Package.

Pre-Construction Quality Control (QC) Checklist; G copies of the

Pre-Construction QC Checklist.

Post-Construction Quality Control (QC) Checklist; G copies of the

Post-Construction QC Checklist.

SD-10 Operation and Maintenance Data

Operation and Maintenance (O&M) Instructions; G

Submit 2 copies of the Operation and Maintenance Instructions, indexed and in booklet form. The Operation and Maintenance

Instructions may be submitted as a Technical Data Package.

Training Documentation; G

Submit hardcopy training manuals and all training materials on

CD-ROM. Provide one hardcopy manual for each trainee on the Course

Attendee List and 2 additional copies for archive at the project site. Provide 2 copies of the Course Attendee List with the archival copies. Training Documentation may be submitted as a

Technical Data Package.

SD-11 Closeout Submittals

Section 23 09 00 Page 15

Enclosure Keys; G

Password Summary Report; G

Provide hardcopies of the Password Summary Report, each copy in its own sealed envelope.

Closeout Quality Control (QC) Checklist; G

Four copies of the Closeout QC Checklist.

1.7 DATA PACKAGE AND SUBMITTAL REQUIREMENTS

Technical data packages consisting of technical data and computer software

(meaning technical data which relates to computer software) which are specifically identified in this project and which may be defined/required in other specifications must be delivered strictly in accordance with the

CONTRACT CLAUSES and in accordance with the Contract Data Requirements List, DD Form 1423. Data delivered must be identified by reference to the particular specification paragraph against which it is furnished. All submittals not specified as technical data packages are considered 'shop drawings' under the Federal Acquisition Regulation Supplement (FARS) and must contain no proprietary information and be delivered with unrestricted rights.

1.8 SOFTWARE FOR DDC HARDWARE AND GATEWAYS

Provide all software related to the programing and configuration of DDC

Hardware and Gateways as indicated. License all Software to the project site. The term "controller" as used in these requirements means both DDC

Hardware and Gateways.

1.8.1 Programming Software

For each type of General Purpose Programmable Controller (GPPC), provide the programming software in accordance with Section 23 09 23.01 LONWORKS DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS.

1.8.2 Controller Application Programs

For each General Purpose Programmable Controller (GPPC), provide copies of the application program as source code compatible with the programming software for that GPPC in accordance with Section 23 09 23.01 LONWORKS

DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS. For each Application Generic Controller (AGC), provide copies of the application program as source code compatible with the programming and configuration tool LNS plug-in for that AGC in accordance with Section 23 09 23.01

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS.

1.8.3 LNS Plug-Ins

Provide LNS Plug-ins in accordance with Section 23 09 23.01 LONWORKS DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS for each

Application Specific Controller and each Application Generic Controller.

For LNS Plug-ins distributed under a license, license the Plug-In to the project site. Submit hard copy manuals, if available, for each plug-in provided as part of the LNS- Plug-Ins submittal.

Section 23 09 00 Page 16

1.8.4 Certificate of Networthiness Documentation

For all software provided, provide documentation that an Enterprise

Certificate of Networthiness exists, that a Limited Certificate of

Networthiness for the project site exists, or provide a completed

Certificate of Networthiness "Application Checklist".

1.9 QUALITY CONTROL CHECKLISTS

The QC Checklist for LNS-Based LonWorks Systems in APPENDIX A of this

Section must be completed by the Contractor's Chief Quality Control (QC)

Representative and submitted as indicated. The QC Representative must verify each item indicated and initial in the space provided to indicate that the requirement has been met. The QC Representative must sign and date the Checklist prior to submission to the Government.

1.9.1 Pre-Construction Quality Control (QC) Checklist

Complete items indicated as Pre-Construction QC Checklist items in the QC

Checklist.

1.9.2 Post-Construction Quality Control (QC) Checklist

Complete items indicated as Post-Construction QC Checklist items in the QC

Checklist.

1.9.3 Closeout Quality Control (QC) Checklist

Complete items indicated as Closeout QC Checklist items in the QC Checklist.

PART 2 PRODUCTS

Provide products meeting the requirements of Section 23 09 23.01 LONWORKS

DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS, and this

Section.

2.1 GENERAL PRODUCT REQUIREMENTS

Units of the same type of equipment must be products of a single manufacturer. Each major component of equipment must have the manufacturer's name and address, and the model and serial number in a conspicuous place. Materials and equipment must be standard products of a manufacturer regularly engaged in the manufacturing of these and similar products. The standard products must have been in a satisfactory commercial or industrial use for two years prior to use on this project. The two year use must include applications of equipment and materials under similar circumstances and of similar size. DDC Hardware not meeting the two-year field service requirement is acceptable provided it has been successfully used by the Contractor in a minimum of two previous projects. The equipment items must be supported by a service organization. Items of the same type and purpose must be identical, including equipment, assemblies, parts and components.

2.2 PRODUCT DATA

Provide manufacturer's product data sheets documenting compliance with product specifications for each product provided under Section 23 09 23.01

Section 23 09 00 Page 17

LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS,

or this Section. Provide product data for all products in a single indexed compendium, organized by product type. For each manufacturer, model and version (revision) of DDC Hardware indicate the type or types of DDC

Hardware the product is being provided as in accordance with Section 23 09

23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL

SYSTEMS.

2.2.1 XIF Files

Provide External Interface Files (XIF Files) for DDC Hardware in accordance with Section 23 09 23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS.

2.3 OPERATION ENVIRONMENT

Unless otherwise specified, provide products rated for continuous operation under the following conditions:

a. Pressure: Pressure conditions normally encountered in the installed location.

b. Vibration: Vibration conditions normally encountered in the installed location.

c. Temperature:

(1) Products installed indoors: Ambient temperatures in the range of

32 to 112 degrees F and temperature conditions outside this range normally encountered at the installed location.

(2) Products installed outdoors or in unconditioned indoor spaces:

Ambient temperatures in the range of -35 to +151 degrees F and temperature conditions outside this range normally encountered at the installed location.

d. Humidity: 10 to 95 percent relative humidity, noncondensing and humidity conditions outside this range normally encountered at the installed location.

2.4 WIRELESS CAPABILITY

For products incorporating any wireless capability (including but not limited to radio frequency (RF), infrared and optical), provide products for which wireless capability can be permanently disabled at the device.

Optical and infrared capabilities may be disabled via a permanently affixed opaque cover plate.

2.5 ENCLOSURES

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

2.5.1 Outdoors

Section 23 09 00 Page 18

For enclosures located outdoors, provide enclosures meeting NEMA 250 requirements.

2.5.2 Mechanical and Electrical Rooms

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

2.5.3 Other Locations

For enclosures in other locations including but not limited to occupied spaces, above ceilings, and in plenum returns, provide enclosures meeting

NEMA 250 Type 1 requirements.

2.6 WIRE AND CABLE

Provide wire and cable meeting the requirements of NFPA 70 and NFPA 90A in addition to the requirements of this specification and referenced specifications.

2.6.1 Terminal Blocks

For terminal blocks which are not integral to other equipment, provide terminal blocks which are insulated, modular, feed-through, clamp style with recessed captive screw-type clamping mechanism, suitable for DIN rail mounting, and which have enclosed sides or end plates and partition plates for separation.

2.6.2 Control Wiring for Binary Signals

For Control Wiring for Binary Signals, provide 18 AWG copper or thicker wire rated for 300-volt service.

2.6.3 Control Wiring for Analog Signals

For Control Wiring for Analog Signals, provide 18 AWG or thicker, copper, single- or multiple-twisted wire meeting the following requirements:

a. minimum 2 inch lay of twist

b. 100 percent shielded pairs

c. at least 300-volt insulation

d. each pair has a 20 AWG tinned-copper drain wire and individual overall pair insulation

e. cables have an overall aluminum-polyester or tinned-copper cable-shield tape, overall 20 AWG tinned-copper cable drain wire, and overall cable insulation.

2.6.4 Power Wiring for Control Devices

For 24-volt circuits, provide insulated copper 18 AWG or thicker wire rated for 300 VAC service. For 120-volt circuits, provide 14 AWG or thicker stranded copper wire rated for 600-volt service.

Section 23 09 00 Page 19

2.6.5 Transformers

Provide UL 5085-3 approved transformers. Select transformers sized so that the connected load is no greater than 80 percent of the transformer rated capacity.

PART 3 EXECUTION

3.1 INSTALLATION

Fully install and test the control system in accordance , Section 23 09

23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL

SYSTEMS, and this Section.

3.1.1 Dielectric Isolation

Provide dielectric isolation where dissimilar metals are used for connection and support. Install control system in a matter that provides clearance for control system maintenance by maintaining access space required to calibrate, remove, repair, or replace control system devices. Install control system such that it does not interfere with the clearance requirements for mechanical and electrical system maintenance.

3.1.2 Penetrations in Building Exterior

Make all penetrations through and mounting holes in the building exterior watertight.

3.1.3 Device Mounting Criteria

Install devices in accordance with the manufacturer's recommendations and as indicated and shown. Provide a weathershield for all devices installed outdoors. Provide clearance for control system maintenance by maintaining access space required to calibrate, remove, repair, or replace control system devices. Provide clearance for mechanical and electrical system maintenance; do not not interfere with the clearance requirements for mechanical and electrical system maintenance.

3.1.4 Labels and Tags

Key all labels and tags to the unique identifiers shown on the As-Built drawings. For labels exterior to protective enclosures provide engraved plastic labels mechanically attached to the enclosure or DDC Hardware.

Labels inside protective enclosures may be attached using adhesive, but must not be hand written. For tags, provide plastic or metal tags mechanically attached directly to each device or attached by a metal chain or wire.

a. Label all Enclosures and DDC Hardware.

b. Tag Airflow measurement arrays (AFMA) with flow rate range for signal output range, duct size, and pitot tube AFMA flow coefficient.

c. Tag duct static pressure taps at the location of the pressure tap

3.1.5 SURGE PROTECTION

Section 23 09 00 Page 20

3.1.5.1 Power-Line Surge Protection

Protect equipment connected to AC circuits to withstand power-line surges in accordance with IEEE C62.41. Do not use fuses for surge protection.

3.1.5.2 Surge Protection for Transmitter and Control Wiring

Protect DDC hardware against or provided DDC hardware capable of withstanding surges induced on control and transmitter wiring installed outdoors and as shown. Protect equipment againnst the following two waveforms:

a. A waveform with a 10-microsecond rise time, a 1000-microsecond decay time and a peak current of 60 amps.

b. A waveform with an 8-microsecond rise time, a 20-microsecond decay time and a peak current of 500 amperes.

3.1.6 Basic Cybersecurity Requirements

3.1.6.1 Passwords

For all devices with a password, change the password from the default password. Do not use the same password for more than one device.

Coordinate selection of passwords with government. Provide a Password

Summary Report documenting the password for each device and describing the procedure to change the password for each device.

3.1.6.2 Wireless Capability

Unless otherwise indicated, disable wireless capability (including but not limited to radio frequency (RF), infrared and optical) for all devices with wireless capability. Optical and infrared capabilities may be disabled via a permanently affixed opaque cover plate.