W912QR20R0005Specs-0002.pdf

PDF 2 MB Posted

Attached to
Scott Air Force Base Bldg. 1575 Add/Alt
Solicitation number
W912QR20R0005
Issued by

About this file

This Request for Proposal solicits construction services for an administrative addition and renovation project at Scott Air Force Base in Illinois. The scope of work includes building a 23,702 square foot addition for administrative use along with renovating 50,965 square feet of existing space into dedicated computer data center facilities. Major project elements are seismic retrofit of an existing building and raised floor system, replacement of air handling units and electrical systems, replacement of a chilled water loop, and installation of new data cabinets and furniture. The solicitation is issued by the Department of the Army Corps of Engineers Engineering District Louisville.

View the file

Other files

Show all 29

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

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 W912QR20R0005 for the Addition / Alteration of Building 1575 located at Scott Air Force Base, IL is hereby amended as follow s:

See Summary of Changes.

1. CONTRACT ID CODE PAGE OF PAGES

1 4

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

16C. DATE SIGNED

BY

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 W912QR20R0005

X 9B. DATED (SEE ITEM 11)

27-Feb-2020

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

30-Mar-2020

CODE

U. S. ARMY ENGINEER DISTRICT, LOUISVILLE

600 DR. MARTIN LUTHER KING, JR. PLACE

ROOM 821

LOUISVILLE KY 40202-2239

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912QR20R0005-0002

W912QR20R0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE (SF 30)

The following have been added by full text:

AMDT 0002 SUMMARY OF CHANGES

Building 1575

SAFB, IL

W912QR20R0005

AMENDMENT 0002

SUMMARY OF CHANGES

SF1442:

Section 00 21 00:

A. FAR Clause 52.236-27 ALT I has been revised as follows:

Due to the restrictions on size of gatherings and in an effort to practice safe social distancing, the site visits for the Add/Alt Consolidated Communications Facility project will take place over several sessions stretching two or three days. On April 7 and April 8 there will be three site visits at 0800, 1000 and 1300 (all times Central). If additional walkthroughs are needed based on responses, April 9 will also have the same time slots available. Slots will be filled as requests are received and reservations for particular time slots will not be permitted. Due to the limited number of personnel allowed at a time, a limit of 2 personnel per Company will be enforced. Deadline for requesting a time slot is 1200 central time on 3 April. No walk-ups will be permitted to participate. It must also be emphasized that proper care is taken during the site visit. Frequent hand sanitizing and social distancing must be observed. Due to the current layout of the facility, once past a certain point there is no access to restrooms for hand washing, therefore it is requested that participants take care to have hand sanitizer available. If there is any chance at all that a prospective participant has been exposed to COVID-19 or is feeling under the weather, those individuals shall not participate. Points of contact for requests are Carol.Voyles.1@us.af.mil and Sean.M.Hoben@usace.army.mil. Participants must email both Carol and Sean to get vetted by security and placed in a slot. Requests must include Full Name, License Number and State of Issue for License.

Confirmation of time slots will be sent out by close of business April 3.

Electronic Devices: No electronic devices shall be permitted on the site visit. This includes, but is not limited to cell phones, cameras, fitness watches, computers, tablets, portable music devices (ipod), etc.

Photography by prospective bidders/subcontractors will not be allowed. Prospective bidders/subcontractors shall request government personnel take photos. Photos shall be taken, and then screened for security before being posted with the solicitation.

Any unauthorized recording (photographic or sound) may result in confiscation of the device, permanently barring the individual from the project, and/or criminal prosecution

Plans and Specifications:

A. The following PLAN SHEET(S) have been replaced in their entirety:

G-003 DRAWING INDEX – CONTINUED

G-011 PROPOSED CONSTRUCTION PHASING PLAN - PHASE I

G-012 PROPOSED CONSTRUCTION PHASING PLAN - PHASE II

G-013 PROPOSED CONSTRUCTION PHASING PLAN - PHASE III

CS506 WALL SECTIONS AND DETAILS

CS507 WALL PLANS

CS508 WALL PLAN AND ELEVATION

CS509 WALL SECTIONS AND DETAILS

CS510 FOUNDATION PLANS

CS511 SECTIONS & DETAILS

CS512 SECTIONS & DETAILS

CS513 ELECTRICAL SITE PLAN

ED601 DEMO ELECTRICAL ONE-LINE-DIAGRAM

ED602 DEMO ELECTRICAL ONE-LINE-DIAGRAM

ED603 DEMO ELECTRICAL ONE-LINE-DIAGRAM

ED604 DEMO ELECTRICAL ONE-LINE-DIAGRAM

EP102A MAIN LEVEL POWER PLAN – AREA A – BASE BID

EP102D MAIN LEVEL POWER PLAN – AREA D

T-100 OVERALL TELECOM FLOOR PLAN – BASE BID

T-100A OVERALL TELECOM FLOOR PLAN – BID OPTION 1

T-509 TELECOMMUNICATIONS DETAILS

B. The following PLAN SHEET(S) have been added:

T-100B OVERALL TELECOM FLOOR PLAN – BID OPTION 8

C. The following SPECIFICATION SECTION(S) have been replaced in their entirety:

PROJECT TABLE OF CONTENTS

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

31 00 00 EARTHWORK

32 12 17 HOT MIX BITUMINOUS PAVEMENT

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

D. The following SPECIFICATION SECTION(S) have been added:

31 05 21 GEOGRID SOIL REINFORCEMENT

E. The following SPECIFICATION SECTION(S) have been deleted in their entirety:

01 45 00.00 10 QUALITY CONTROL

F. The following DOCUMENTS have been provided For Information Only:

AS-BUILT DOCUMENTATION

All other terms and conditions remain the same.

SECTION 00 21 00 - INSTRUCTIONS

The following have been modified:

52.236-27 SITE VISIT (CONSTRUCTION) (FEB 1995) – ALTERNATE I (FEB 1995)

(a) The clauses at 52.236-2, Differing Site Conditions, and 52.236-3, Site Investigations and Conditions Affecting the Work, will be included in any contract awarded as a result of this solicitation. Accordingly, offerors or quoters are urged and expected to inspect the site where the work will be performed.

(b) An organized site visit has been scheduled for--

Due to the restrictions on size of gatherings and in an effort to practice safe social distancing, the site visits for the Add/Alt Consolidated Communications Facility project will take place over several sessions stretching two or three days. On April 7 and April 8 there will be three site visits at 0800, 1000 and 1300 (all times Central). If additional walkthroughs are needed based on responses, April 9 will also have the same time slots available. Slots will be filled as requests are received and reservations for particular time slots will not be permitted. Due to the limited number of personnel allowed at a time, a limit of 2 personnel per Company will be enforced. Deadline for requesting a time slot is 1200 central time on 3 April. No walk-ups will be permitted to participate. It must also be emphasized that proper care is taken during the site visit. Frequent hand sanitizing and social distancing must be observed. Due to the current layout of the facility, once past a certain point there is no access to restrooms for hand washing, therefore it is requested that participants take care to have hand sanitizer available. If there is any chance at all that a prospective participant has been exposed to COVID-19 or is feeling under the weather, those individuals shall not participate. Points of contact for requests are Carol.Voyles.1@us.af.mil and Sean.M.Hoben@usace.army.mil. Participants must email both Carol and Sean to get vetted by security and placed in a slot. Requests must include Full Name, License Number and State of Issue for License.

Confirmation of time slots will be sent out by close of business April 3.

Electronic Devices: No electronic devices shall be permitted on the site visit. This includes, but is not limited to cell phones, cameras, fitness watches, computers, tablets, portable music devices (ipod), etc.

Photography by prospective bidders/subcontractors will not be allowed. Prospective bidders/subcontractors shall request government personnel take photos. Photos shall be taken, and then screened for security before being posted with the solicitation.

Any unauthorized recording (photographic or sound) may result in confiscation of the device, permanently barring the individual from the project, and/or criminal prosecution

(c) Participants will meet at--

Participants will meet at the shed area on the west side of the facility by the main entrance of Building 1575.

Interested parties wishing to participate in the site visit shall contact Carol Voyles at 618-256-4012 or Carol.Voyles.1@us.af.mil and Sean.M.Hoben@usace.army.mil. Participants must email both Carol and Sean to get vetted by security and placed in a slot. Requests must include Full Name, License Number and State of Issue for License.

(End of provision)

(End of Summary of Changes)

ADD/ALTER CONSOLIDATED COMMUNICATIONS FACILITY 1575

SCOTT AFB, IL

W912QR-20-R-0005

PROJECT TABLE OF CONTENTS Page 1

CERTIFIED FINAL DESIGN

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 10 00 PRICE BREAKOUT SCHEDULE

00 80 00.00 06 SPECIAL PROVISIONS

DIVISION 01 - GENERAL REQUIREMENTS

01 11 10 SUMMARY OF WORK

01 32 01.00 06 PROJECT SCHEDULE

01 33 00.00 06 SUBMITTAL PROCEDURES

01 33 29.00 06 SUSTAINABILITY REPORTING

01 35 26.00 06 GOVERNMENT SAFETY REQUIREMENTS

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

AMENDMENT 0002*************************************************************

01 45 00.00 10 DELETED

************************************************************* AMENDMENT 0002

01 45 00.15 10 RESIDENT MANAGEMENT SYSTEM CONTRACTOR MODE (RMS CM)

01 45 04.10 06 CONTRACTOR QUALITY CONTROL

01 45 35 SPECIAL INSPECTIONS

01 46 00.00 06 TOTAL BUILDING COMMISSIONING (CONTRACTOR CxA)

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19.00 06 TEMPORARY ENVIRONMENTAL CONTROLS AND PERMITS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION AND DECONSTRUCTION

02 82 13.00 10 ASBESTOS ABATEMENT

02 83 13.00 20 LEAD IN CONSTRUCTION

02 84 16 HANDLING OF LIGHTING BALLASTS AND LAMPS CONTAINING PCBs

AND MERCURY

DIVISION 03 - CONCRETE

03 11 13.00 10 STRUCTURAL CAST-IN-PLACE CONCRETE FORMING

03 20 00.00 10 CONCRETE REINFORCING

03 30 00 CAST-IN-PLACE CONCRETE

03 35 00.00 10 CONCRETE FINISHING

03 39 00.00 10 CONCRETE CURING

DIVISION 04 - MASONRY

04 01 20.70 UNIT MASONRY CLEANING AND RESTORATION

04 20 00 UNIT MASONRY

DIVISION 05 - METALS

05 05 23.16 STRUCTURAL WELDING

05 12 00 STRUCTURAL STEEL

05 12 10 STRUCTURAL CAST STEEL COMPONENTS

05 21 00 STEEL JOIST FRAMING

05 30 00 STEEL DECKS

05 40 00 COLD-FORMED METAL FRAMING

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 50 14 STRUCTURAL METAL FABRICATIONS

05 51 00 METAL STAIRS

05 51 33 METAL LADDERS

W912QR-20-R-0005

PROJECT TABLE OF CONTENTS Page 2

05 52 00 METAL RAILINGS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 20 00 FINISH CARPENTRY

06 41 16.00 10 PLASTIC-LAMINATE-CLAD ARCHITECTURAL CABINETS

06 61 16 SOLID SURFACING FABRICATIONS

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

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

BUILDING ADDITION ONLY

07 13 53 ELASTOMERIC SHEET WATERPROOFING

07 21 13 BOARD AND BLOCK INSULATION

07 21 16 MINERAL FIBER BLANKET INSULATION

07 22 00 ROOF AND DECK INSULATION

07 27 10.00 10 BUILDING AIR BARRIER SYSTEM

07 27 36 SPRAY FOAM AIR BARRIERS

07 52 00 MODIFIED BITUMINOUS MEMBRANE ROOFING

07 60 00 FLASHING AND SHEET METAL

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 14 00 WOOD DOORS

08 31 00 ACCESS DOORS AND PANELS

08 33 23 OVERHEAD COILING DOORS

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL WALL AND DOOR LOUVERS

DIVISION 09 - FINISHES

09 22 00 SUPPORTS FOR PLASTER AND GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 30 10 CERAMIC, QUARRY, AND GLASS TILING

09 51 00 ACOUSTICAL CEILINGS

09 65 00 RESILIENT FLOORING

09 68 00 CARPETING

09 69 13 RIGID GRID ACCESS FLOORING

09 84 20 ACOUSTICAL WALL PANELS

09 90 00 PAINTS AND COATINGS

DIVISION 10 - SPECIALTIES

10 11 00 VISUAL DISPLAY UNITS

10 14 00.20 INTERIOR SIGNAGE

10 21 13 TOILET COMPARTMENTS

10 21 23.13 CUBICLE CURTAINS

10 21 23.16 CUBICLE TRACK AND HARDWARE

10 22 13 WIRE MESH PARTITIONS

10 26 00 WALL AND DOOR PROTECTION

10 28 13 TOILET ACCESSORIES

10 44 16 FIRE EXTINGUISHERS

DIVISION 11 - EQUIPMENT

W912QR-20-R-0005

PROJECT TABLE OF CONTENTS Page 3

11 13 19.13 LOADING DOCK LEVELERS (STATIONARY LOADING DOCK EQUIPMENT)

DIVISION 12 - FURNISHINGS

12 24 13 ROLLER WINDOW SHADES

12 59 00 SYSTEMS FURNITURE

DIVISION 13 - SPECIAL CONSTRUCTION

13 48 00

SEISMIC BRACING FOR MISCELLANEOUS EQUIPMENT

DIVISION 21 - FIRE SUPPRESSION

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

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

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

23 03 00.00 20 BASIC MECHANICAL MATERIALS AND METHODS

23 05 48.19 SEISMIC BRACING FOR HVAC

23 05 93.00 06 TESTING, ADJUSTING, AND BALANCING (TAB) OF HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC

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

CONTROL SYSTEMS

23 11 25 FACILITY GAS PIPING

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

23 25 00 CHEMICAL TREATMENT OF WATER FOR MECHANICAL SYSTEMS

23 52 00 HEATING BOILERS

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

23 65 00 COOLING TOWERS AND REMOTE EVAPORATIVELY-COOLED CONDENSERS

23 82 00.00 20 TERMINAL HEATING UNITS

DIVISION 25 - INTEGRATED AUTOMATION

25 50 00.00 20 CYBERSECURITY OF FACILITY-RELATED CONTROL SYSTEMS

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 05 48.00 10 SEISMIC PROTECTION FOR ELECTRICAL EQUIPMENT

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 13 SWITCHBOARDS

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 36 00.00 10 AUTOMATIC TRANSFER SWITCH AND BY-PASS/ISOLATION SWITCH

26 41 00 LIGHTNING PROTECTION SYSTEM

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

27 11 16 COMMUNICATIONS RACKS, FRAMES, ENCLOSURES, AND

CONTAINMENT SYSTEMS

W912QR-20-R-0005

PROJECT TABLE OF CONTENTS Page 4

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 08 10 ELECTRONIC SECURITY SYSTEM ACCEPTANCE TESTING

28 10 05 ELECTRONIC SECURITY SYSTEMS (ESS)

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 05 19 GEOTEXTILE

AMENDMENT 0002*************************************************************

31 05 21 GEOGRID SOIL REINFORCEMENT

************************************************************* AMENDMENT 0002

31 11 00 CLEARING AND GRUBBING

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 01 19 FIELD MOLDED SEALANTS FOR SEALING JOINTS IN RIGID

PAVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 11 23 AGGREGATE BASE COURSES

32 12 17 HOT MIX BITUMINOUS PAVEMENT

32 12 36.13 ASPHALTIC SEAL AND FOG COATS

32 13 13.06 PORTLAND CEMENT CONCRETE PAVEMENT FOR ROADS AND SITE

FACILITIES

32 16 13 CONCRETE SIDEWALKS AND CURBS AND GUTTERS

32 16 15 CONCRETE BLOCK PAVEMENTS

32 17 23 PAVEMENT MARKINGS

32 92 19 SEEDING

32 93 00 EXTERIOR PLANTS

DIVISION 33 - UTILITIES

33 11 00 WATER UTILITY DISTRIBUTION PIPING

33 30 00 SANITARY SEWERS

33 40 00 STORM DRAINAGE UTILITIES

33 46 16 SUBDRAINAGE PIPING

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

DIVISION 34 - TRANSPORTATION

34 71 13.19 ACTIVE VEHICLE BARRIERS

-- End of Project Table of Contents --

ADD/ALTER CONSOLIDATED COMMUNICATIONS FACILITY 1575 W912QR-20-R-0005

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 13 INSTRUMENTATION AND CONTROL DEVICES FOR HVAC, Section

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

CONTROL SYSTEMS and other referenced Sections.

AMENDMENT 0002*************************************************************

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 , unless otherwise pre-approved by the Contracting Officer .

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, SECTION 23 09 00 Page 1

Vendor or Manufacturer.

h. All Niagara Framework components have an unrestricted interoperability license with a Niagara Compatibility Statement (NiCS) following the Tridium Open NiCS Specification and have a value of "ALL" for "Station Compatibility In", "Station Compatibility Out", "Tool Compatibility In" and "Tool Compatibility Out". Note that this will result in the following entries in the license file:

accept.station.in="*" accept.station.out="*" accept.wb.in="*" accept.wb.out="*"

i. Existing BLDG 1575 BACnet network and Johnson Controls Network Panel(s) serving existing equipment controls and the existing base-wide Johnson Controls EMCS to remain. The new control system indicated in the contract documents shall be compatible with the existing Johnson Controls Metasys Extended Architecture Systems at Building 1575 and through the base-wide EMCS.

***************************************************************AMENDMENT 0002

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

BUILDING CONTROL SYSTEMS

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

c. Section 01 46 00.00 06 CONTRACTOR CxA

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.

SECTION 23 09 00 Page 2

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

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

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

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; ERTA 1-2 2017; TIA 17-1; TIA 17-2;

TIA 17-3; TIA 17-4; TIA 17-5; TIA 17-6;

TIA 17-7; TIA 17-8; TIA 17-9; TIA 17-10;

TIA 17-11; TIA 17-12; TIA 17-13; TIA

17-14; TIA 17-15; TIA 17-16; TIA 17-17 )

National Electrical Code

NFPA 90A (2015) Standard for the Installation of Air Conditioning and Ventilating Systems

TRIDIUM, INC (TRIDIUM)

Niagara Framework (2012) NiagaraAX User's Guide

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

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

SECTION 23 09 00 Page 3 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).

In BACnet, Alarm Generation is the creation of alarm events using the Niagara Framework Alarm Service, or using Event Reporting as defined in ASHRAE 135 in one of three ways:

a. Intrinsic Alarm Generation using Intrinsic Reporting

b. Local Algorithmic Alarm Generation using Algorithmic Reporting where the referenced property is in the same device as the Event Enrollment Object

c. Remote Algorithmic Alarm Generation using Algorithmic Alarming where the referenced property is in a different device than the Event Enrollment Object.

1.4.2 Building Automation and Control Network (BACnet)

The term BACnet is used in two ways. First meaning the BACnet Protocol Standard - the communication requirements as defined by ASHRAE 135 including all annexes and addenda. The second to refer to the overall technology related to the ASHRAE 135 protocol.

1.4.3 BACnet Advanced Application Controller (B-AAC)

A hardware device BTL Listed as a B-AAC, which is required to support BACnet Interoperability Building Blocks (BIBBs) for scheduling and alarming, but is not required to support as many BIBBs as a B-BC.

1.4.4 BACnet Application Specific Controller (B-ASC)

A hardware device BTL Listed as a B-ASC, with fewer BIBB requirements than a B-AAC. It is intended for use in a specific application.

1.4.5 BACnet Building Controller (B-BC)

A hardware device BTL Listed as a B-BC. A general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks including control and monitoring via direct digital control (DDC) of specific systems and data storage for trend information, time schedules, and alarm data. Like the other BTL Listed controller types (B-AAC, B-ASC etc.) a B-BC device is required to support the server ("B") side of the ReadProperty and WriteProperty services, but unlike the other controller types it is also required to support the client ("A") side of these services. Communication between controllers requires that one of them support the client side and the other support the server side, so a B-BC is often used when communication between controllers is needed.

1.4.6 BACnet Broadcast Management Device (BBMD)

A communications device, typically combined with a BACnet router. A BBMD forwards BACnet broadcast messages to BACnet/IP devices and other BBMDs connected to the same BACnet/IP network. Each IP subnet that is part of a BACnet/IP network must have at least one BBMD. Note there are additional restrictions when multiple BBMDs share an IP subnet.

SECTION 23 09 00 Page 4

1.4.7 BACnet/IP

An extension of BACnet, Annex J, defines the use of a reserved UDP socket to transmit BACnet messages over IP networks. A BACnet/IP network is a collection of one or more IP subnets that share the same BACnet network number. See also paragraph BACNET BROADCAST MANAGEMENT DEVICE.

1.4.8 BACnet Internetwork

Two or more BACnet networks, connected with BACnet routers. In a BACnet internetwork, there exists only one message path between devices.

1.4.9 BACnet Interoperability Building Blocks (BIBBs)

A BIBB is a collection of one or more ASHRAE 135 Services intended to define a higher level of interoperability. BIBBs are combined to build the BACnet functional requirements for a device in a specification. Some BIBBs define additional requirements (beyond requiring support for specific services) in order to achieve a level of interoperability. For example, the BIBB DS-V-A (Data Sharing-View-A), which would typically be used by a front-end, not only requires the client to support the ReadProperty Service, but also provides a list of data types (Object / Properties) which the client must be able to interpret and display for the user.

In the BIBB shorthand notation, -A is the client side and -B is the server side.

The following is a list of some BIBBs used by this or referenced Sections:

DS-COV-A Data Sharing-Change of Value (A side)

DS-COV-B Data Sharing-Change of Value (B side)

NM-RC-B Network Management-Router Configuration (B side)

DS-RP-A Data Sharing-Read Property (A side)

DS-RP-B Data Sharing-Read Property (B side)

DS-RPM-A Data Sharing-Read Property Multiple (A Side)

DS-RPM-B Data Sharing-Read Property Multiple (B Side)

DS-WP-A Data Sharing-Write Property (A Side)

DM-TS-B Device Management-Time Synchronization (B Side)

DM-UTC-B Device Management-UTC Time Synchronization (B Side)

DS-WP-B Data Sharing-Write Property (B side)

SCHED-E-B Scheduling-External (B side)

SECTION 23 09 00 Page 5

The following is a list of some BIBBs used by this or referenced Sections:

DM-OCD-B Device Management-Object Creation and Deletion (B side)

AE-N-I-B Alarm and Event-Notification Internal (B Side)

AE-N-E-B Alarm and Event-Notification External (B Side)

T-VMT-I-B Trending-Viewing and Modifying Trends Internal (B Side)

T-VMT-E-B Trending-Viewing and Modifying Trends External (B Side)

1.4.10 BACnet Network

In BACnet, a portion of the control internetwork consisting of one or more segments connected by repeaters. Networks are separated by routers.

1.4.11 BACnet Operator Display (B-OD)

A basic operator interface with limited capabilities relative to a B-OWS.

It is not intended to perform direct digital control. A B-OD profile could be used for LCD devices, displays affixed to BACnet devices, handheld terminals or other very simple user interfaces.

1.4.12 BACnet Segment

One or more physical segments interconnected by repeaters ( ASHRAE 135).

1.4.13 BACnet Smart Actuator (B-SA)

A simple actuator device with limited resources intended for specific applications.

1.4.14 BACnet Smart Sensor (B-SS)

A simple sensing device with limited resources.

1.4.15 BACnet Testing Laboratories (BTL)

Established by BACnet International to support compliance testing and interoperability testing activities and consists of BTL Manager and the BTL Working Group (BTL-WG). BTL also publishes Implementation Guidelines.

1.4.16 BACnet Testing Laboratories (BTL) Listed

A device that has been listed by BACnet Testing Laboratory. Devices may be certified to a specific device profile, in which case the listing indicates that the device supports the required capabilities for that profile, or may be listed as "other".

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

SECTION 23 09 00 Page 6

1.4.18 Broadcast

Unlike most messages, which are intended for a specific recipient device, a broadcast message is intended for all devices on the network.

1.4.19 Building Control Network (BCN)

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

1.4.20 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.21 Commandable

See Overridable.

1.4.22 Commandable Objects

Commandable Objects have a Commandable Property, Priority_Array, and Relinquish_Default Property as defined in ASHRAE 135, Clause 19.2, Command Prioritization.

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

In a Niagara Framework BACnet system, a property, setting, or value is configurable if it can be changed via one or more of:

1) via BACnet services (including proprietary BACnet services)

2) via hardware settings on the device

3) via the Niagara Framework .

Note this is more stringent than the ASHRAE 135 definition.

1.4.24 Control Logic Diagram

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

1.4.25 Device

A Digital Controller that contains a BACnet Device Object and uses BACnet to communicate with other devices.

1.4.26 Device Object

Every BACnet device requires one Device Object, whose properties represent the network visible properties of that device. Every Device Object requires a unique Object Identifier number on the BACnet internetwork.

This number is often referred to as the device instance or device ID.

SECTION 23 09 00 Page 7

1.4.27 Device Profile

A collection of BIBBs determining minimum BACnet capabilities of a device, defined in ASHRAE 135. Standard device profiles include BACnet Advanced Workstations (B-AWS), BACnet Building Controllers (B-BC), BACnet Advanced Application Controllers (B-AAC), BACnet Application Specific Controllers (B-ASC), BACnet Smart Actuator (B-SA), and BACnet Smart Sensor (B-SS).

1.4.28 Digital Controller

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

1.4.29 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.30 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.31 Fox Protocol

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

1.4.32 Gateway

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.

A Niagara Framework Supervisory Gateway is one type of Gateway.

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

SECTION 23 09 00 Page 8

1.4.34 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.35 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.36 I/O Expansion Unit

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

1.4.37 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.38 JACE (Niagara Framework)

Java Application Control Engine. See paragraph NIAGARA FRAMEWORK

SUPERVISORY GATEWAY

1.4.39 Local-Area Network (LAN)

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

1.4.40 Local Display Panels (LDPs)

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.41 MAC Address

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

1.4.42 Master-Slave/Token-Passing (MS/TP)

Data link protocol as defined by the BACnet standard. Multiple speeds (data rates) are permitted by the BACnet MS/TP standard.

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

SECTION 23 09 00 Page 9

1.4.44 Network Number

A site-specific number assigned to each network. This network number must be unique throughout the BACnet internetwork.

1.4.45 Niagara Framework (Niagara Framework)

A set of hardware and software specifications for building and utility control owned by Tridium Inc. and licensed to multiple vendors. The Framework consists of front end (M&C) software, web based clients, field level control hardware, and engineering tools. While the Niagara Framework is not adopted by a recognized standards body and does not use an open licensing model, it is sufficiently well-supported by multiple HVAC vendors to be considered a de-facto Open Standard.

1.4.46 Niagara Framework Supervisory Gateway (Niagara Framework)

DDC Hardware component of the Niagara Framework. A typical Niagara architecture has Niagara specific supervisory gateways at the IP level and other (non-Niagara specific) controllers on field networks (TP/FT-10, MS/TP, etc.) beneath the Niagara supervisory gateways. The Niagara specific controllers function as a gateway between the Niagara framework protocol (Fox) and the field network beneath. These supervisory gateways may also be used as general purpose controllers and also have the capability to provide a web-based user interface.

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

The most common name is "JACE"; other names include (but are not limited to)"EC-BOS", "FX-40", "TMN", "SLX" and "UNC".

1.4.47 Object

An ASHRAE 135 Object. The concept of organizing BACnet information into standard components with various associated Properties. Examples include Analog Input objects and Binary Output objects.

1.4.48 Object Identifier

A grouping of two Object properties: Object Type (e.g. Analog Value, Schedule, etc.) and Object Instance (in this case, a number). Object Identifiers must be unique within a device.

1.4.49 Object Instance

See paragraph OBJECT IDENTIFIER

1.4.50 Object Properties

Attributes of an object. Examples include present value and high limit properties of an analog input object. Properties are defined in ASHRAE 135;

some are optional and some are required. Objects are controlled by reading from and writing to object properties.

1.4.51 Operator Configurable

For Niagara Framework Systems, a property, setting, or value is Operator Configurable when it is configurable from a Niagara Framework Front End.

SECTION 23 09 00 Page 10

1.4.52 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.53 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.54 Physical Segment

A single contiguous medium to which BACnet devices are attached ( ASHRAE 135

1.4.55 Polling

A device periodically requesting data from another device.

1.4.56 Points

Physical and virtual inputs and outputs. See also paragraph INPUT/OUTPUT (I/O).

1.4.57 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.58 Proprietary

Within the context of BACnet, any extension of or addition to object types, properties, PrivateTransfer services, or enumerations specified in ASHRAE 135. Objects with Object_Type values of 128 and above are Proprietary Objects. Properties with Property_Identifier of 512 and above are proprietary Properties.

1.4.59 Protocol Implementation Conformance Statement (PICS)

A document, created by the manufacturer of a device, which describes which portions of the BACnet standard may be implemented by a given device.

ASHRAE 135 requires that all ASHRAE 135 devices have a PICS, and also defines a minimum set of information that must be in it. A device as installed for a specific project may not implement everything in its PICS.

1.4.60 Repeater

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

1.4.61 Router

A device that connects two networks and controls traffic between the two

SECTION 23 09 00 Page 11 by retransmitting signals received from one side onto the other based on the signal destination. Routers are used to subdivide a control inter network and to control bandwidth usage.

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

1.4.63 Standard BACnet Objects

Objects with Object_Type values below 128 and specifically enumerated in Clause 21 of ASHRAE 135. Objects which are not proprietary. See paragraph PROPRIETARY.

1.4.64 Standard BACnet Properties

Properties with Property_Identifier values below 512 and specifically enumerated in Clause 21 of ASHRAE 135. Properties which are not proprietary. See Proprietary.

1.4.65 Standard BACnet Services

ASHRAE 135 services other than ConfirmedPrivateTransfer or UnconfirmedPrivateTransfer. See paragraph PROPRIETARY.

1.4.66 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.67 UMCS NETWORK

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

1.4.68 Writeable Property

A Property is Writeable when it can be changed through the use of one or more of the WriteProperty services defined in ASHRAE 135, Clause 15 regardless of the value of any other Property. Note that in the ASHRAE 135 standard, some Properties may be writeable when the Out of Service Property is TRUE; for purposes of this Section, Properties that are only writeable when the Out of Service Property is TRUE are not considered to be Writeable.

SECTION 23 09 00 Page 12

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

Niagara Framework Engineering Tool

ACO #6

SECTION 23 09 00 Page 13

TABLE I. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)

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

12 E Execute PVT AAO #9 and #11

13 S PVT Report ACO #12

14 S Controller Application Programs Controller Configuration Settings

Niagara Framework Supervisory Gateway Backups

AAO #13

15 S Final As-Built Drawings AAO #13

16 S O&M Instructions AAO #15

17 S Training Documentation AAO #10 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 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.00 06 SUSTAINABILITY REPORTING. Submit the following in accordance with Section 01 33 00.00 06 SUBMITTAL PROCEDURES:

SECTION 23 09 00 Page 14

SD-02 Shop Drawings

DDC Contractor Design Drawings; G

DDC Contractor Design Drawings as a single complete package: 2 hard copies and 2 copies on CDROM. Submit hardcopy drawings on ISO A1 34 by 22 inches or A3 17 by 11 inches sheets, and electronic drawings in PDF and in AutoCAD 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.

Draft As-Built Drawings; G

Draft As-Built Drawings as a single complete package: 2 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 AutoCAD 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: 2 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 AutoCAD 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

Programming Software; G

Submit Programming Software on CD-ROM as a Technical Data Package. Submit 2 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 2 hard copies of the software user manual for each piece of software.

Controller Configuration Settings; G

Submit Controller Configuration Settings on CD-ROM as a

SECTION 23 09 00 Page 15

Technical Data Package. Include on the CD-ROM a list or table of contents clearly indicating which files are associated with each device. Submit 2 copies of the Controller Configuration Settings

CD-ROM.

Manufacturer's Product Data; G

Submit Manufacturer's Product Data on CD-ROM.

Niagara Framework Supervisory Gateway Backups; G

Submit backups for each Niagara Framework Supervisory Gateway on CD-ROM as a Technical Data Package. Mark each backup indicating clearly the source Niagara Framework Supervisory Gateway.

Niagara Framework Engineering Tool; G

Submit the Niagara Framework Engineering Tool on CD-ROM as a Technical Data Package. Submit 2 hard copies of the software user manual for the Niagara Framework Engineering Tool.

SD-06 Test Reports

Existing Conditions Report

Four copies of the Existing Conditions Report.

Start-Up Testing Report; G

PVT Procedures; G

PVT Report; G

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

Pre-Construction Quality Control (QC) Checklist; G

Four copies of the Pre-Construction QC Checklist.

Post-Construction Quality Control (QC) Checklist; G

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

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