1782837Amend0004spec_P1334CDC 1-2.pdf

Naval Building P-1334 - Child Development Center 60715453

MISC. REVISIONS

SECTION 01 45 35

SPECIAL INSPECTIONS

11/20

PART 1 GENERAL

1.1 REFERENCES

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

INTERNATIONAL CODE COUNCIL (ICC)

ICC IBC (2021) International Building Code

1.2 GENERAL REQUIREMENTS

Perform Special Inspections in accordance with the Statement of Special Inspections, Schedule of Special Inspections and Chapter 17 of ICC IBC .

The Statement of Special Inspections and Schedule of Special Inspections are included as an attachment to this specification. Special Inspections are to be performed by an independent third party and are intended to ensure that the work of the Prime Contractor is in accordance with the Contract Documents and applicable building codes. Special inspections do not take the place of the three phases of control inspections performed by the Contractor's QC Manager or any testing and inspections required by other sections of the specifications.

Structural observations will be performed by the Structural Engineer of Record on the Contractor's Design-Build team . The Contractor must provide notification to the Contracting Officer , Structural Engineer of Record and Contracting Officer 14 days prior to the following points of construction to allow for structural observation:

a. Shear Wall Foundations prior to concrete placement.

b. Shear Wall Connections to Foundations and Roof Panels before they are covered.

1.3 DEFINITIONS

1.3.1 Continuous Special Inspections

Continuous Special Inspections is the constant monitoring of specific tasks by a special inspector. These inspections must be carried out continuously over the duration of the particular tasks.

1.3.2 Perform

Perform these Special Inspections tasks for each welded joint or member.

1.3.3 Observe

Observe these Special Inspections items on a periodic daily basis.

Operations need not be delayed pending these inspections.

SECTION 01 45 35 Page 1 July 9, 2025 jodi.long Polygon

1.3.4 Special Inspector (SI)

A qualified person retained by the Contractor and approved by the Contracting Officer as having the competence necessary to inspect a particular type of construction requiring Special Inspections. The SI must be an independent third party hired directly by the Prime Contractor.

1.3.5 Associate Special Inspector (ASI)

A qualified person who assists the SI in performing Special Inspections but must perform inspection under the direct supervision of the SI and cannot perform inspections without the SI on site.

1.3.6 Third Party

A Special inspector must not be an employee of the Contractor or of any Sub-Contractor performing the work to be inspected.

1.3.7 Special Inspector of Record (SIOR)

A licensed engineer in responsible charge of supervision of all special inspectors for the project and approved by the Contracting Officer. The SIOR must be an independent third party entity hired directly by the Prime Contractor.

1.3.8 Contracting Officer

The Government official having overall authority for administrative contracting actions. Certain contracting actions may be delegated to the Contracting Officer's Representative (COR).

1.3.9 Contractor's Quality Control (QC) Manager

An individual retained by the Prime Contractor and qualified in accordance with the Section 01 45 00 QUALITY CONTROL having the overall responsibility for the Contractor's QC organization.

1.3.10 Structural Engineer of Record (SER)

A registered design professional contracted by the Government as an A/E responsible for the overall design and review of submittal documents prepared by others. The SER is registered or licensed to practice their respective design profession as defined by the statutory requirements of the professional registration laws in the state in which the design professional works. The SER is also referred to as the Engineer of Record (EOR) in design code documents.

1.3.11 Statement of Special Inspections (SSI)

A document developed by the SER identifying the material, systems, components and work required to have Special Inspections. This statement is included at the end of this specification.

1.3.12 Schedule of Special Inspections (SSI)

A schedule which lists each of the required Special Inspections, the extent to which each Special Inspection is to be performed, and the required frequency for each in accordance with ICC IBC Chapter 17. This schedule is included at the end of this specification.

SECTION 01 45 35 Page 2 July 9, 2025

1.3.13 Definable Feature of Work (DFOW)

An inspection group that is separate and distinct from other inspection groups, having inspection requirements or inspectors that are unique.

1.4 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-01 Preconstruction Submittals

SIOR Letter of Acceptance; G

Special Inspections Project Manual; G

SD-06 Test Reports

Special Inspections Daily Reports

Special Inspections Biweekly Reports

SD-07 Certificates

AISC Certified Steel Fabricator

Certificate of Compliance

Special Inspector of Record Qualifications; G

Special Inspector Qualifications; G

SD-11 Closeout Submittals

Comprehensive Final Report of Special Inspections; G

1.5 SPECIAL INSPECTOR QUALIFICATIONS

Submit qualifications for each special inspector and the special inspector of record.

1.5.1 Steel Construction and High Strength Bolting

1.5.1.1 Special Inspector

a. ICC Structural Steel and Bolting Special Inspector certificate with one year of related experience, or

b. Registered Professional Engineer with three years of related experience

1.5.1.2 Associate Special Inspector

Engineer-In-Training with one year of related experience.

SECTION 01 45 35 Page 3

1.5.2 Welding Structural Steel

1.5.2.1 Special Inspector

a. ICC Structural Welding Special Inspector certificate with one year of related experience, or

b. AWS Certified Welding Inspector

1.5.2.2 Associate Special Inspector

AWS Certified Associate Welding Inspector

1.5.3 Nondestructive Testing of Welds

1.5.3.1 Special Inspector

NDT Level III Certificate

1.5.3.2 Associate Special Inspector

NDT Level II Certificate plus one year of related experience

1.5.4 Concrete Construction

1.5.4.1 Special Inspector

a. ICC Reinforced Concrete Special Inspector Certificate with one year of related experience, or

b. ACI Concrete Construction Special Inspector, or

c. Registered Professional Engineer with three years of related experience

1.5.4.2 Associate Special Inspector

a. ACI Concrete Construction Special Inspector in Training, or

b. Engineer-In-Training with one year of related experience

1.5.5 Wood

1.5.5.1 Special Inspector

a. ICC Commercial Building Inspector Certificate with one year of related experience, or

b. ICC Residential Building Inspector with on year of experience, or

c. Registered Professional Engineer with three years of related experience

1.5.5.2 Associate Special Inspector

Engineer-In-Training with one year of related experience.

SECTION 01 45 35 Page 4

1.5.6 Verification of Site Soil Condition, Fill Placement and Load-Bearing Requirements

1.5.6.1 Special Inspector

a. ICC Soils Special Inspector Certificate with one year of related experience, or

b. NICET Soils Technician Level II Certificate in Construction Material Testing, or

c. Geologist-In-Training with three years of related experience, or

d. Registered Professional Engineer with three years of related experience

1.5.6.2 Associate Special Inspector

a. NICET Soils Technician Level I Certificate in Construction Material Testing with one year of related experience, or

b. Engineer-In-Training with one year of related experience

1.5.7 Special Inspector of Record (SIOR)

Registered Professional Engineer with five years of related experience.

PART 2 PRODUCTS

2.1 FABRICATOR SPECIAL INSPECTIONS

Special Inspections of fabricator's work performed in the fabricator's shop is required to be inspected in accordance with the Statement of Special Inspections and the Schedule of Special Inspections unless the fabricator is certified by the approved agency to perform such work without Special Inspections. Submit the following certifications to the Contracting Officer for information to allow work performed in the fabricator's shop to not be subjected to Special Inspections.

AISC Certified Steel Fabricator.

At the completion of fabrication, submit a certificate of compliance, to be included with the comprehensive final report of Special Inspections, stating that the materials supplied and work performed by the fabricator are in accordance with the construction documents.

PART 3 EXECUTION

3.1 RESPONSIBILITIES

3.1.1 Special Inspector of Record

a. Supervise all Special Inspectors required by the Contract Documents and the IBC.

b. Submit a SIOR Letter of Acceptance to the Contracting Officer attesting to acceptance of the duties of SIOR, signed and sealed by the SIOR.

c. Verify the qualifications of all of the Special Inspectors.

SECTION 01 45 35 Page 5

d. Verify the qualifications of fabricators.

e. Prepare a Special Inspections Project Manual, which must cover the following:

(1) Roles and responsibilities of the following individuals during Special Inspections: SIOR, SI, ASI, General Contractor's QC Manager and SER.

(2) Organizational chart or communication plan, indicating lines of communication.

(3) Contractor's internal plan for scheduling inspections. Address items such as timeliness of inspection requests, who to contact for inspection requests, and availability of alternate inspectors.

(4) Indicate the Government reporting requirements.

(5) Propose forms or templates to be used by SI and SIOR to document inspections.

(6) Indicate procedures for tracking nonconforming work and verification that corrective work is complete.

(7) Indicate how the SIOR and SI will participate in weekly QC meetings.

(8) Indicate how Special Inspections of shop fabricated items will be handled when the fabricator's shop is not certified in accordance with paragraph FABRICATOR SPECIAL INSPECTIONS.

(9) Include a section in the manual that covers each specific item requiring Special Inspections that is indicated on the Schedule of Special Inspections. Provide names and qualifications of each special inspector who will be performing the Special Inspections for each specific item. Provide detail on how the Special Inspections are to be carried out for each item so that the expectations are clear for the General Contractor and the Subcontractor performing the work.

Make a copy of the Special Inspections Project Manual available on the job site during construction. Submit a copy of the Special Inspections Project Manual for approval.

f. Attend coordination and mutual understanding meeting where the information in the Special Inspections Project Manual will be reviewed to verify that all parties have a clear understanding of the Special Inspections provisions and the individual duties and responsibilities of each party.

g. Maintain a 3-ring binder for the Special Inspector's daily and biweekly reports and the Special Inspections Project Manual. This file must be located in a conspicuous place in the project trailer/office to allow review by the Contracting Officer and the SER.

h. Submit a copy of the Special Inspector's daily reports to the QC Manager.

SECTION 01 45 35 Page 6

i. Discrepancies that are observed during Special Inspections must be reported to the QC Manager for correction. If discrepancies are not corrected before the special inspector leaves the site the observed discrepancies must be documented in the daily report.

j. Submit a biweekly Special Inspections report until all work requiring Special Inspections is complete. A report is required for each biweekly period in which Special Inspections activity occurs, and must include the following:

(1) A brief summary of the work performed during the reporting time frame.

(2) Changes and discrepancies with the drawings, specifications that were observed during the reporting period.

(3) Discrepancies which were resolved or corrected.

(4) A list of nonconforming items requiring resolution.

(5) All applicable test results including nondestructive testing reports.

k. At the completion of the project submit a comprehensive final report of Special Inspections that documents the Special Inspections completed for the project including corrections of all discrepancies noted in the daily reports. The comprehensive final report of Special Inspections must be signed, dated and bear the seal of the SIOR.

3.1.2 Quality Control Manager

a. Maintain a rework items list that includes discrepancies noted on the Special Inspectors daily report.

3.1.3 Special Inspectors

a. Inspect all elements of the project for which the special inspector is qualified to inspect and are identified in the Schedule of Special Inspections.

b. Attend preparatory phase meetings related to the Definable Feature of Work (DFOW) for which the special inspector is qualified to inspect.

c. Submit daily reports to the SIOR.

3.2 DEFECTIVE WORK

Check work as it progresses, but failure to detect any defective work or materials must in no way prevent later rejection if defective work or materials are discovered, nor obligate the Contracting Officer to accept such work.

-- End of Section --

SECTION 01 45 35 Page 7

SECTION 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC

02/19, CHG 3: 05/21

PART 1 GENERAL

1.1 SUMMARY

Provide a complete Direct Digital Control (DDC) system, except for the Front End which is specified in Section 25 10 10 UTILITY MONITORING AND CONTROL (UMCS) FRONT END AND INTEGRATION, 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 for BACnet or Niagara BACnet systems, and other referenced Sections.

Acceptable control systems product line and manufacturers are limited to WebCTRL by Automated Logic Corporation (ALC) and Metasys by Johnson Controls International (JCI) in accordance with NAVFAC Class Justification and Approval (CJ&A) No. ML-25-30.

1.1.1 Proprietary Systems

1.1.1.1 Proprietary Systems Exempted From Open Protocol Requirements

The following systems are specifically exempted from the open protocol requirements of Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS:

a. A simple split (DX) system consisting of a single indoor unit and a single outdoor unit from the same manufacturer.

b. Systems in Table I (previously approved by the designer in accordance with UFC 3-410-02 ).

TABLE I: Systems Approved to Use Proprietary Communications

System Type (Multi-Split/VRF or Chiller/Boiler Plant)

Proprietary Multi-Split Engineering Tool Software Required (for Multi-Split/VRF only)

c. A system (not already shown Table I) of multiple boilers or multiple chillers communicating with a proprietary network for which an approved request has been obtained and for which: all units are from the same manufacturer, they are all co-located in the same room, the network connecting them is fully contained in that room, and the units are operating using a common "plant" sequence of operation which stages the units in a manner that requires operational parameters be shared between them and which cannot be accomplished with a single lead-lag command from a third-party controller.

SECTION 23 09 00 Page 1 July 9, 2025 jodi.long Polygon

1.1.1.2 Implementation of Proprietary Systems

For proprietary systems exempted from open protocol requirements, a proprietary network and DDC hardware communicating via proprietary protocol are permitted. For these systems a building control network meeting the requirements of Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS must also be provided, along with a gateway or interface to connect the proprietary system to the open building control network.

The proprietary system gateway or interface must provide the required functionaliality as shown on the points schedule. Scheduling, alarming, trending, overrides, network inputs, network outputs and other protocol related requirements must be met on the open protocol control system as specified in Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC

AND OTHER BUILDING CONTROL SYSTEMS.

1.1.1.3 Proprietary Multi-Split Engineering Tool Software

For each permitted proprietary systems in Table 1 shown as requiring Proprietary Multi-Split Engineering Tool Software, provide the software needed to replace a unit and configure the replacement. Submit hard copies of the software user manuals with the software submittal.

Submit Proprietary Multi-Split Engineering Tool Software on CD-ROM as a Technical Data Package. Submit two hard copies of the software user manual for each piece of software.

1.1.2 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

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

1.1.3 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.4 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.5 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 for BACnet systems with or without Niagara Framework .

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

c. Section 25 10 10 UTILITY MONITORING AND CONTROL SYSTEMS (UMCS) FRONT

END AND INTEGRATION

d. Section 25 05 11.01 CYBERSECURITY FOR BMS FACILITY-RELATED CONTROL

SYSTEMS

e. Section 01 91 00.15 BUILDING COMMISSIONING

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 3

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

ASHRAE 135 (2020; Interpretation 1-8 2021; Errata 1-2 2021; Addenda CD 2021; Addenda BV-CE 2022;

Interpretation 9-12 2022; Interpretation 13-17 2023; Addenda BV-CF 2023; Errata 3 2023) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASHRAE FUN IP (2021) 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 (2020) Enclosures for Electrical Equipment (1000 Volts Maximum)

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 70 (2023; ERTA 7 2023; TIA 23-15) National Electrical Code

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

U.S. DEPARTMENT OF DEFENSE (DOD)

UFC 3-410-02 (2018; with Change 2, 2021) Direct Digital Control for HVAC and Other Building Control Systems

UNDERWRITERS LABORATORIES (UL)

UL 5085-3 (2006; Reprint Jan 2022) UL Standard for Safety 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.

After each term the protocol related to that term is included in parenthesis.

1.4.1 Alarm Generation (All protocols)

Alarm Generation is the monitoring of a value, comparison of the value to

SECTION 23 09 00 Page 4 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) - see paragraph ALARM ROUTING in Section 25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS)

FRONT END AND INTEGRATION.

1.4.2 Building Automation and Control Network (BACnet) (BACnet)

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

1.4.3 BACnet Advanced Application Controller (B-AAC) (BACnet)

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

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

A hardware device BTL Listed as a B-BC. A general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks including control and monitoring via direct 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) (BACnet)

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.

1.4.7 BACnet/IP (BACnet)

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

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

SECTION 23 09 00 Page 5

1.4.9 BACnet Interoperability Building Blocks (BIBBs) (BACnet)

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)

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

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

SECTION 23 09 00 Page 6

1.4.11 BACnet Operator Display (B-OD) (BACnet)

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

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

1.4.13 BACnet Smart Actuator (B-SA) (BACnet)

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

1.4.14 BACnet Smart Sensor (B-SS) (BACnet)

A simple sensing device with limited resources.

1.4.15 BACnet Testing Laboratories (BTL) (BACnet)

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

1.4.16 BACnet Testing Laboratories (BTL) Listed (BACnet)

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 (All protocols)

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.18 Broadcast (BACnet)

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) (All protocols)

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

1.4.20 Building Point of Connection (BPOC) (All protocols)

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

SECTION 23 09 00 Page 7

1.4.21 Commandable (All protocols)

See Overridable.

1.4.22 Commandable Objects (BACnet)

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 (All protocols)

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

Note this is more stringent than the ASHRAE 135 definition.

1.4.24 Control Logic Diagram (All protocols)

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

1.4.25 Device (BACnet)

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

1.4.26 Device Object (BACnet)

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

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

1.4.27 Device Profile (BACnet)

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 (All protocols)

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) (All protocols)

Digital controllers performing control logic. Usually the controller directly senses physical values, makes control decisions with internal

SECTION 23 09 00 Page 8 programs, and outputs control signals to directly operate switches, valves, dampers, and motor controllers.

1.4.30 Field Point of Connection (FPOC) (All protocols)

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 Gateway (All protocols)

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.32 IEEE 802.3 Ethernet (All protocols)

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.33 Internet Protocol (IP, TCP/IP, UDP/IP) (All protocols)

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.34 Input/Output (I/O) (All protocols)

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.35 I/O Expansion Unit (All protocols)

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

1.4.36 IP subnet (All protocols)

A group of devices which share a defined range IP addresses. Devices on a

SECTION 23 09 00 Page 9 common IP subnet can share data (including broadcasts) directly without the need for the traffic to traverse an IP router.

1.4.37 Local-Area Network (LAN) (All protocols)

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

1.4.38 Local Display Panels (LDPs) (All protocols)

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.39 MAC Address (All protocols)

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

1.4.40 Master-Slave/Token-Passing (MS/TP) (BACnet)

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

1.4.41 Monitoring and Control (M&C) Software (All protocols)

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.42 Network Number (BACnet)

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

1.4.43 Object (BACnet)

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.44 Object Identifier (BACnet)

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.45 Object Instance (BACnet)

See paragraph OBJECT IDENTIFIER

1.4.46 Object Properties (BACnet)

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.

SECTION 23 09 00 Page 10

1.4.47 Operator Configurable (All protocols)

Operator configurable values are values that can be changed from a single common front end user interface across multiple vendor systems.

For non Niagara-based BACnet systems, a property, setting, or value in a device is Operator Configurable when it is Configurable and is either:

a. a Writable Property of a Standard BACnet Object; or

b. a Property of a Standard BACnet Object that is Writable when

Out_Of_Service is TRUE and Out_Of_Service is Writable.

1.4.48 Override (All protocols)

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.

Overrides are often used by operators to change values, and generally originate at a user interface (workstation or local display panel).

1.4.49 Packaged Equipment (All protocols)

Packaged equipment is a single piece of equipment provided by a manufacturer in a substantially complete and operable condition, where the controls (DDC Hardware) are factory installed, and the equipment is sold and shipped from the manufacturer as a single entity. Disassembly and reassembly of a large piece of equipment for shipping does not prevent it from being packaged equipment. Package units may require field installation of remote sensors. Packaged equipment is also called a "packaged unit".

Note industry may use the term "Packaged System" to mean a collection of equipment that is designed to work together where each piece of equipment is packaged equipment and there is a network that connects the equipment together. A "packaged system" of this type is NOT packaged equipment; it is a collection of packaged equipment, and each piece of equipment must individually meet specification requirements.

1.4.50 Packaged Unit (All protocols)

See packaged equipment.

1.4.51 Performance Verification Test (PVT) (All protocols)

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.52 Physical Segment (BACnet)

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

SECTION 23 09 00 Page 11

1.4.53 Polling (All protocols)

A device periodically requesting data from another device.

1.4.54 Points (All protocols)

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

1.4.55 Proportional, Integral, and Derivative (PID) Control Loop (All protocols)

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.56 Proprietary (BACnet)

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.57 Protocol Implementation Conformance Statement (PICS) (BACnet)

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.58 Repeater (All protocols)

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

1.4.59 Router (All protocols)

A device that connects two ASHRAE 135 networks 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 BACnet internetwork and to limit network traffic.

1.4.60 Segment (All protocols)

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.61 Standard BACnet Objects (BACnet)

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

SECTION 23 09 00 Page 12

1.4.62 Standard BACnet Properties (BACnet)

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.63 Standard BACnet Services (BACnet)

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

1.4.64 UMCS (All protocols)

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 Control 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.65 UMCS Network (All protocols)

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

1.4.66 Writable Property (BACnet)

A Property is Writable 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 writable when the Out of Service Property is TRUE; for purposes of this Section, Properties that are only writable when the Out of Service Property is TRUE are not considered to be Writable.

1.5 PROJECT SEQUENCING

TABLE II: 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 II does not specify overall project milestone and completion dates.

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

SECTION 23 09 00 Page 13 indicates the earliest the activity may begin.

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

TABLE II. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)

1 S DDC Contractor Design Drawings

2 S Manufacturer's Product Data

3 S Pre-construction QC Checklist

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

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

6 S Post-Construction QC Checklist ACO #6

7 S Programming Software Configuration Software

ACO #6

8 S Draft As-Built Drawings ACO #6

9 S Start-Up Testing Report ACO #6

10 S PVT Procedures before schedule start of #12 and AAO #10

11 S, E Execute PVT PVT Testing Activities AAO #9 and #11 As indicated in PART 3 of this Section

SECTION 23 09 00 Page 14

TABLE II. PROJECT SEQUENCING

ITEM

TYPE DESCRIPTION SEQUENCING (START OF

ACTIVITY OR DEADLINE FOR

SUBMITTAL)

12 S PVT Report ACO #12 As indicated in PART 3 of this Section

13 S Controller Application Programs Controller Configuration Settings

AAO #13

14 S Final As-Built Drawings AAO #13

15 S O&M Instructions AAO #15

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

17 E Training AAO #16 and #17

18 S Closeout QC Checklist ACO #18

1.6 SUBMITTALS

Government approval is required for submittals with a "G" or "S" classification. Submittals not having a "G" or "S" classification are for Contractor Quality Control approval. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES:

SD-02 Shop Drawings

DDC Contractor Design Drawings; G

Draft As-Built Drawings; G

Final As-Built Drawings; G

SD-03 Product Data

Programming Software; G

Controller Application Programs; G

Configuration Software; G

Controller Configuration Settings; G

SECTION 23 09 00 Page 15

Proprietary Multi-Split Engineering Tool Software; G

Manufacturer's Product Data; G

SD-05 Design Data

Boiler Or Chiller Plant Gateway Request

SD-06 Test Reports

Pre-Construction Quality Control (QC) Checklist; G

Post-Construction Quality Control (QC) Checklist; G

Start-Up Testing Report; G

PVT Procedures; G

PVT Report; G

Control Contractor’s Performance Verification Testing Plan; G

Equipment Supplier’s Performance Verification Testing Plan; G

Endurance Testing Results; G

Performance Verification Test Report; G

SD-10 Operation and Maintenance Data

Operation and Maintenance (O&M) Instructions; G

Training Documentation; G

SD-11 Closeout Submittals

Enclosure Keys; G

Password Summary Report; G

Closeout Quality Control (QC) Checklist; G

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.

SECTION 23 09 00 Page 16

1.8 SOFTWARE FOR DDC HARDWARE AND GATEWAYS

Provide all software related to the programming 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 Configuration Software

For each type of controller, provide the configuration tool software in accordance with Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS. Submit hard copies of the software user manuals for each software with the software submittal.

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.

1.8.2 Controller Configuration Settings

For each controller, provide copies of the installed configuration settings as source code compatible with the configuration tool software for that controller in accordance with Section 23 09 23.02 BACNET DIRECT

DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS.

Submit Controller Configuration Settings 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. Submit 2 copies of the Controller Configuration Settings CD-ROM.

1.8.3 Programming Software

For each type of programmable controller, provide the programming software in accordance with Section 23 09 23.02 BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS. Submit hard copies of software user manuals for each software with the software submittal.

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.

1.8.4 Controller Application Programs

For each programmable controller, provide copies of the application program as source code compatible with the programming software for that controller in accordance with Section 23 09 23.02 BACNET DIRECT DIGITAL

CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS.

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.

1.9 BOILER OR CHILLER PLANT GATEWAY REQUEST

If requesting the use of a gateway to a boiler or chiller plant as indicated in paragraph Proprietary Systems Exempted From Open Protocol Requirements, submit a Boiler or Chiller Plant Gateway Request describing the configuration of the boilers or chillers including model numbers for equipment and controllers, the sequence of operation for the units, and a

SECTION 23 09 00 Page 17 justification for the need to operate the units on a shared non-BACnet network.

1.10 QUALITY CONTROL CHECKLISTS

The QC Checklist for BACnet 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.10.1 Pre-Construction Quality Control (QC) Checklist

Complete items indicated as Pre-Construction QC Checklist items in the QC Checklist. Submit four copies of the Pre-Construction QC Checklist.

1.10.2 Post-Construction Quality Control (QC) Checklist

Complete items indicated as Post-Construction QC Checklist items in the QC Checklist. Submit four copies of the Post-Construction QC Checklist.

1.10.3 Closeout Quality Control (QC) Checklist

Complete items indicated as Closeout QC Checklist…