SynC™

SynC · SynC Standards

Building Automation System

Rev5
IssuedAug 26, 2026
Contents

Revision history

Download
Build a datasheet from this standard Start a project with this standard already attached — one click, no setup.
Use in a project

1 Scope

NOTE This standard covers the products, network architecture, programming, integration, commissioning, and cybersecurity hardening of the building automation system (BAS) that executes and supervises control of the building's mechanical systems. (1.1)
NOTE The system is organized in four layers, and most of the decisions in this standard attach to one of them. (1.2)
  • Management layer. The server and operator clients that host graphics, the historical trend database, the alarm and event database, schedule definitions, the user account directory, and configuration backup.
  • Supervisory layer. Network controllers that perform global control logic, scheduling, alarm generation, trend collection from field controllers, and integration of subsystems that do not speak the primary protocol natively.
  • Field controller layer. Programmable and application-specific controllers at each item of mechanical equipment that execute that equipment's sequence of operations.
  • Field bus and I/O layer. Sensors, actuators, end switches, and equipment communication interfaces wired to controller inputs and outputs or networked on a field bus.
NOTE The following are outside this standard and are governed elsewhere. (1.3)
  • Sequences of operation for individual mechanical equipment, which are published on the contract drawings and in the equipment standards; this standard governs the platform that executes them.
  • Control conductors, cable, raceway, and boxes, which are governed by Conductors And CablesConductors and CablesResolves to the current adopted revision.sync/conductors-and-cables and Raceways And ConduitRaceways and ConduitResolves to the current adopted revision.sync/raceways-and-conduit; this standard governs only the electrical characteristics, separation, and termination practices specific to control and network circuits.
  • The fire alarm system itself, which is governed by Fire Alarm SystemsFire Alarm SystemsResolves to the current adopted revision.sync/fire-alarm-systems; only the interface between the two systems is addressed here.
  • Line-voltage power distribution to BAS panels upstream of the control power transformer or the branch circuit disconnecting means.
1.4 Control circuits supplied by the BAS shall be Class 2 circuits complying with NFPA 70 Article 725 unless the contract documents designate a different circuit class.
1.5 The BAS shall interface with the fire alarm system for fan shutdown, damper command, and smoke control status in accordance with NFPA 72 and the smoke control sequence on the contract drawings.

2 Referenced Standards

2.1 Equipment, materials, software, and installation shall comply with the latest adopted edition of each of the following unless a specific edition is cited.
2.2 Where the contract documents, the adopted building code, or a referenced standard conflict, the more stringent requirement shall govern unless the Engineer of Record directs otherwise in writing.
Standard Title
ANSI/ASHRAE 135 BACnet - A Data Communication Protocol for Building Automation and Control Networks
ANSI/ASHRAE 135.1 Method of Test for Conformance to BACnet
ANSI/ASHRAE Guideline 13 Specifying Building Automation Systems
ANSI/ASHRAE Guideline 36 High-Performance Sequences of Operation for HVAC Systems
ANSI/ASHRAE 223 Designation and Classification of Semantic Tags for Building Data
ANSI/ASHRAE 231 Control Description Language
ANSI/ASHRAE 62.1 Ventilation and Acceptable Indoor Air Quality
ANSI/ASHRAE 188 Legionellosis - Risk Management for Building Water Systems
ANSI/ASHRAE/IES 90.1 Energy Standard for Sites and Buildings Except Low-Rise Residential Buildings
ISO 16484-2 Building Automation and Control Systems (BACS) - Hardware
ISO 16484-3 Building Automation and Control Systems (BACS) - Functions
ISO 16484-5 Building Automation and Control Systems (BACS) - Data Communication Protocol
ISO 16484-6 Building Automation and Control Systems (BACS) - Data Communication Conformance Testing
ANSI/CTA-709.1 Control Network Protocol Specification
Modbus Application Protocol Specification Application layer protocol for Modbus serial line and Modbus TCP
NIST SP 800-82 Guide to Operational Technology (OT) Security
ISA/IEC 62443 Security for Industrial Automation and Control Systems
NFPA 70 National Electrical Code (Article 725 - Class 2 and Class 3 circuits; Article 800 - communications circuits)
NFPA 72 National Fire Alarm and Signaling Code
NFPA 90A Installation of Air-Conditioning and Ventilating Systems
UL 916 Energy Management Equipment
UL 60730-1 Automatic Electrical Controls - General Requirements
UL 50E Enclosures for Electrical Equipment, Environmental Considerations
NEMA 250 Enclosures for Electrical Equipment (1000 Volts Maximum)
IEEE 802.3 Ethernet
ANSI/TIA-568 Balanced Twisted-Pair and Optical Fiber Telecommunications Cabling Systems
ANSI/TIA-862 Structured Cabling Infrastructure Standard for Intelligent Building Systems
47 CFR Part 15 Radio Frequency Devices (Subpart B - unintentional radiators)
ASCE/SEI 7 Minimum Design Loads and Associated Criteria for Buildings and Other Structures
ISO 9001 Quality Management Systems - Requirements

3 Submittals

3.1 Action Submittals

3.1.1 The Contractor shall submit the following for the Engineer's review and return before any BAS product is procured or installed:
  • Product data for each server, supervisory controller, programmable controller, application-specific controller, gateway, network switch, sensor, and actuator, identifying manufacturer, model, protocol conformance listing, device profile, and the interoperability building blocks supported
  • Protocol Implementation Conformance Statement for every device that communicates on the primary protocol
  • System architecture diagram showing the management, supervisory, field controller, and field bus layers, every network segment, the physical media of each segment, and the boundary of every subsystem that does not communicate natively in the primary protocol
  • Network addressing plan giving device instance numbers unique across the whole system, network numbers per segment, IP addressing for routed devices, and field bus node addresses with the master node count per segment
  • Point list organized by equipment giving each point's name, object type and instance, engineering units, range, alarm limits, change-of-value increment, and origin as hardware input, calculated value, or integrated value
  • Graphics intent package with representative site, floor plan, system schematic, and equipment pages showing navigation hierarchy and dynamic value treatment
  • Schedule and alarm strategy defining schedule structure, alarm classes and priorities, suppression rules, and routing destinations by priority and time of day
  • Trend plan listing trended points, sampling method, sampling interval, retention, aggregation, and whether each trend is buffered on the controller or on the server
  • Cybersecurity plan addressing network segregation, account management, authentication, patch and firmware maintenance, removable media, remote access, and audit logging
  • Integration submittal for each subsystem that does not communicate natively in the primary protocol, giving communication parameters, the register or object map, the gateway product, and the resulting object list presented to the supervisory layer
  • Correspondence document mapping each step of each published sequence of operations to the controller program block that implements it
  • Field wiring riser diagram showing controller panel locations, cable types, segment lengths, and termination points
  • Sizing calculation for each control power transformer and each uninterruptible power supply, showing connected load and reserve capacity
Required Action Submittalscheckbox
☑ Product data for controllers, gateways, sensors, and actuators
☑ Protocol Implementation Conformance Statement for each device
☑ System architecture diagram with all network segments and media
☑ Network addressing plan
☑ Point list by equipment
☑ Graphics intent package
☑ Schedule and alarm strategy
☑ Trend plan
☑ Cybersecurity plan
☐ Integration submittal for each non-native subsystem
☑ Sequence-to-program correspondence document
☑ Field wiring riser diagram
☐ Control power and UPS sizing calculations
3.1.2 The Contractor shall submit the controller, network, point list, and integration submittals as one coordinated package.
3.1.3 Where the Engineer determines that a submittal was returned for revision because of an internal inconsistency between items that should have been coordinated before submission, the cost of the Engineer's review of the resubmittal shall be borne by the Contractor.

3.2 Informational Submittals

3.2.1 The Contractor shall submit the following for information before the pre-installation conference:
  • Qualification statement for the controls contractor listing comparable completed projects, their scope, and their completion dates
  • Certificates held by the individuals assigned as programmer, integrator, and commissioning technician for this project
  • Manufacturer's written commitment covering replacement part availability, firmware support, and software upgrade paths for the proposed platform
  • Proposed programming, tagging, and point naming conventions
  • Proposed commissioning schedule identifying the sequence of point-to-point verification, network verification, and functional testing relative to mechanical startup
Required Informational Submittalscheckbox
☑ Controls contractor qualification statement
☑ Certificates for assigned programmer, integrator, and commissioning technician
☑ Manufacturer platform support commitment
☐ Programming, tagging, and point naming conventions
☑ Proposed commissioning schedule

3.3 Closeout Submittals

3.3.1 The Contractor shall submit the following before the building automation system is accepted:
  • Operation and maintenance manuals covering the operator interface, controller programming, parameter reference, and the manufacturer's recommended preventive maintenance intervals
  • Record drawings reflecting installed panel locations, sensor and actuator locations, cable routing, and every field deviation from the reviewed submittal
  • Complete configuration backup containing controller programs, graphics, schedules, alarm definitions, trend definitions, user accounts, and the server database, in the manufacturer's native backup format
  • Point database export in a spreadsheet-readable format listing every point with its final range, engineering units, alarm limits, and final tag name
  • Calibration record for every measured sensor giving the calibration date, the reference instrument and its traceability, the as-found reading, and the as-left reading
  • Network performance report giving measured field bus token loop times per segment, measured routed traffic on the supervisory network, and any segment loading deficiency observed with its corrective action
  • Cybersecurity closeout package listing all accounts with their assigned roles, all installed firmware and software versions with their release dates, the configured backup schedule, and a signed statement that every default and vendor-supplied credential has been changed
  • Functional test records for every point and every sequence, signed by the Contractor's commissioning technician and countersigned by the Commissioning Authority where one is engaged
  • Training records identifying the personnel trained, the dates, and the topics covered
  • Restoration test record demonstrating that a full configuration backup was restored to a test platform and produced a working system
Required Closeout Submittalscheckbox
☑ Operation and maintenance manuals
☑ Record drawings
☑ Complete configuration backup in native format
☑ Point database export
☑ Sensor calibration records with as-found and as-left readings
☐ Network performance report
☑ Cybersecurity closeout package
☑ Functional test records
☑ Training records
☐ Backup restoration test record

4 Quality Assurance

4.1 Manufacturer Qualifications

4.1.1 The BAS platform shall be the product of a manufacturer that has produced direct digital control products for commercial building mechanical systems continuously for at least the period indicated in the datasheet.
Minimum Manufacturer Production Historyrange
years
3510152025
4.1.2 The manufacturer shall operate a quality management system certified to ISO 9001.
4.1.3 The manufacturer shall commit in writing to the availability of replacement parts, firmware, and software upgrade paths for the proposed platform for the period indicated in the datasheet, measured from the date of substantial completion.
Minimum Platform Support Commitmentrange
years
510152025

4.2 Controls Contractor Qualifications

4.2.1 Installation, programming, integration, and commissioning of the BAS shall be performed by a controls contractor authorized by the platform manufacturer for the proposed product line.
4.2.2 The controls contractor shall have completed installations of comparable scope and complexity for at least the period indicated in the datasheet.
Minimum Controls Contractor Experiencerange
years
2351015
4.2.3 The individuals assigned as programmer, integrator, and commissioning technician shall hold current manufacturer certification on the proposed product line.
4.2.4 The controls contractor shall maintain a service organization capable of responding on site within the response time indicated in the datasheet for the duration of the warranty period.
Maximum Warranty Service Response Timerange
hours
48244872

4.3 Protocol Conformance Listing

NOTE Protocol conformance testing is performed by an independent testing organization against the protocol's published conformance test method - for BACnet, ANSI/ASHRAE 135.1, administered through the BACnet Testing Laboratories listing program. A Protocol Implementation Conformance Statement is a vendor declaration of the same information; it is not independently verified. (4.3.1)
4.3.2 Supervisory and programmable controllers shall carry the conformance listing indicated in the datasheet for the device profile claimed in the submittal.
Conformance Listing Policy - Supervisory and Programmable Controllersradio
● Independent conformance listing required for the claimed device profile
○ Vendor Protocol Implementation Conformance Statement accepted in lieu of independent listing
○ Independent conformance listing required, with Engineer-approved exceptions accepted on written request
4.3.3 Application-specific controllers, smart sensors, smart actuators, and gateways shall carry the conformance listing indicated in the datasheet.
Conformance Listing Policy - Application-Specific Controllers and End Devicesradio
○ Independent conformance listing required for the claimed device profile
○ Vendor Protocol Implementation Conformance Statement accepted in lieu of independent listing
○ Independent conformance listing required, with Engineer-approved exceptions accepted on written request
4.3.4 Where the datasheet permits Engineer-approved exceptions, the Contractor shall submit the device's Protocol Implementation Conformance Statement and identify the specific role the device fills, and shall not install the device until the Engineer has accepted it in writing for that role.
4.3.5 The device profile claimed for each controller shall be sufficient for the functions that controller performs in this project.
Minimum Device Profile - Supervisory Controllerselect
BACnet Building Controller (B-BC)
BACnet Advanced Application Controller (B-AAC)
BACnet Advanced Operator Workstation (B-AWS)
Not applicable - primary protocol is not BACnet
Minimum Device Profile - Equipment Field Controllerselect
BACnet Building Controller (B-BC)
BACnet Advanced Application Controller (B-AAC)
BACnet Application Specific Controller (B-ASC)
BACnet Smart Actuator (B-SA)
BACnet Smart Sensor (B-SS)
Not applicable - primary protocol is not BACnet

4.4 Electrical Safety Listing

4.4.1 Controllers, power supplies, gateways, and assembled control panels shall be listed by a Nationally Recognized Testing Laboratory to UL 916 or UL 60730-1 as applicable to the product.
4.4.2 Equipment supplied from a Class 2 source shall be listed for Class 2 operation in accordance with NFPA 70 Article 725.
4.4.3 Digital equipment furnished under this standard shall comply with the unintentional radiator emission limits of 47 CFR Part 15 Subpart B for the class appropriate to the installed environment.
4.4.4 Control panels assembled off site shall bear the listing mark of the panel-shop listing under which they were built.

4.5 Single-Source Responsibility

4.5.1 The management, supervisory, field controller, and integration layers of the BAS shall be furnished, installed, programmed, and commissioned under a single controls contractor.
4.5.2 Where a controller is furnished factory-mounted on packaged mechanical equipment, or where a third-party subsystem such as a submeter, generator controller, or indoor air quality monitor is furnished under another standard, the controls contractor shall integrate that device into the BAS through the interface identified in the integration submittal.
4.5.3 The controls contractor shall demonstrate at functional testing that every point required by the point list is visible and operable at the operator workstation regardless of which trade furnished the originating device.
4.5.4 Where a factory-furnished controller does not expose a point required by the point list, the controls contractor shall notify the Engineer in writing within ten business days of discovering the deficiency and shall propose a means of obtaining the value.

4.6 Pre-Installation Conference

4.6.1 A pre-installation conference shall be held before any BAS field work begins.
4.6.2 Attendance shall include the controls contractor, the mechanical contractor, the electrical contractor, the Owner's information technology representative, and the Commissioning Authority where one is engaged.
4.6.3 The conference agenda shall cover network port and address assignment with the Owner's information technology organization, identification of the panels served from standby or uninterruptible power, field bus routing and segment boundaries, panel locations and working clearances, and the cybersecurity constraints that apply to contractor access during construction and after substantial completion.

5 Environmental and Service Conditions

5.1 Controller Ambient Ratings

5.1.1 Controllers, power supplies, and network devices shall be rated for continuous operation across the ambient temperature and humidity range present at their installed location as indicated on the contract documents.
5.1.2 Controllers installed indoors in conditioned spaces shall be rated for continuous operation over at least the temperature range indicated in the datasheet.
Minimum Rated Ambient Temperature - Indoor Conditioned Locationsrange
°F
-20143240
Maximum Rated Ambient Temperature - Indoor Conditioned Locationsrange
°F
104122131140158
Maximum Rated Relative Humidity, Non-Condensingrange
% RH
809095
5.1.3 Controllers installed in unconditioned locations shall be rated for the design ambient extremes at that location, and any enclosure heater or supplemental cooling required to achieve that rating shall be included in the submittal and in the contract price.
5.1.4 Where a controller enclosure is installed in a location where the surface temperature can fall below the dew point of the surrounding air, condensation control shall be provided.
Condensation Control for Unconditioned Enclosuresradio
○ Thermostatically controlled enclosure heater
○ Anti-condensation heater strip, continuously energized
○ Conformal-coated electronics without supplemental heat
○ Sealed enclosure with desiccant breather
○ None
NOTE Controller failures in unconditioned spaces concentrate at the seasonal changeover between heating and cooling, when warm humid air reaches surfaces still at the previous season's temperature and condenses on circuit boards and terminal blocks. (5.1.5)

5.2 Control Power and Ride-Through

5.2.1 Field controllers and end devices shall be supplied from Class 2 control power transformers in accordance with NFPA 70 Article 725.
5.2.2 The connected load on any control power transformer shall not exceed the fraction of the transformer nameplate rating indicated in the datasheet.
Maximum Control Power Transformer Loadingrange
%
5060708090100
5.2.3 Power supplies serving supervisory controllers, gateways, and network switches shall be sized with reserve capacity above the connected load as indicated in the datasheet.
Minimum Power Supply Reserve Capacityrange
%
101520253050
5.2.4 Devices sharing a control power transformer shall share a common circuit polarity, and the transformer secondary shall be grounded at one point only.
5.2.5 The server, supervisory controllers, and the network devices connecting them shall be supplied from an uninterruptible power supply sized for at least the runtime indicated in the datasheet.
Minimum Uninterruptible Power Supply Runtimerange
minutes
510153060120240
5.2.6 The branch circuits and standby power branches serving BAS panels shall be as indicated in the datasheet.
Standby Power Source for BAS Panelsradio
○ Normal power only
○ Standby generator serving panels that control life safety mechanical equipment
○ Standby generator serving all BAS panels
○ Uninterruptible power supply at the management and supervisory layers, normal power at field panels
○ Uninterruptible power supply at the management and supervisory layers, standby generator at all panels
NOTE A short utility interruption that restarts the supervisory layer costs more operating time than it costs power, because controllers return through their startup sequences, trend buffers upload out of order, and any alarm generated during the outage is annunciated on recovery. (5.2.7)

5.3 Seismic Restraint and Certification

5.3.1 BAS panels, server cabinets, and floor- or wall-mounted network enclosures shall be anchored and restrained in accordance with ASCE/SEI 7 and the adopted building code for the project Seismic Design Category.
5.3.2 Where the BAS controls mechanical equipment designated by the Engineer of Record as a designated seismic system, the controller assembly shall carry seismic certification for the required design forces.
5.3.3 Anchorage details and certification documentation shall be submitted before panel installation.

6 System Architecture and Layering

6.1 Layer Autonomy

6.1.1 Every controller shall continue to execute its assigned sequence of operations when isolated from the layer above it.
6.1.2 Loss of the supervisory network shall not interrupt control of any item of mechanical equipment by its field controller.
6.1.3 Loss of the server shall not interrupt supervisory scheduling, alarm generation, or global control logic.
6.1.4 Any single network failure shall degrade monitoring, historical collection, and cross-system coordination only, and shall not cause a loss of local mechanical control.
6.1.5 Values that a controller receives from another device across the network shall have a defined failure behavior - a last-known-good value with an expiry, a programmed default, or a defined failure mode - and that behavior shall be identified in the sequence-to-program correspondence document.
NOTE A controller that holds a stale network value forever is worse than one that fails to a default, because the failure is invisible - the loop keeps controlling to a number that stopped being true. (6.1.6)

6.2 Communication Protocol Selection

6.2.1 The open protocol used at every interface where devices from more than one manufacturer must interoperate shall be as indicated in the datasheet.
Open Protocol at Multi-Vendor Interfacesradio
● BACnet (ANSI/ASHRAE 135)
○ Control Network Protocol (ANSI/CTA-709.1)
○ Modbus (Modbus Application Protocol Specification)
○ OPC Unified Architecture (IEC 62541)
6.2.2 Every point required by the point list shall be readable and, where the sequence requires it, writable at the supervisory layer through the open protocol selected above, regardless of the protocol used inside any individual subsystem.
6.2.3 A manufacturer's proprietary protocol may be used below the supervisory layer within a single manufacturer's product family, provided the boundary of that subsystem presents the selected open protocol.
6.2.4 The operator shall not be required to use a separate application, workstation, or login to see or command any point required by the point list.
NOTE An interoperability requirement that stops at the vendor's own product line is not interoperability; the test that matters at handover is whether a second manufacturer's controller can be added to the network in year six without replacing the supervisory layer. (6.2.5)

6.3 Supervisory Network

Supervisory Network Datalinkselect
BACnet/IP over IEEE 802.3 Ethernet
BACnet Secure Connect (BACnet/SC)
BACnet over IEEE 802.3 Ethernet frames (BACnet/Ethernet)
Control Network Protocol over IP
Modbus TCP
NOTE BACnet Secure Connect carries BACnet over a TLS-protected WebSocket connection with mutual certificate authentication, which addresses two properties that BACnet/IP does not have on its own - the traffic is encrypted, and each device authenticates its peer. Where the supervisory network shares any infrastructure with traffic that is not part of the BAS, those two properties are what distinguish a segregated network from a merely separate address range. (6.3.2)
6.3.3 Where BACnet Secure Connect is selected, the certificate authority, certificate lifetime, and the renewal procedure shall be identified in the cybersecurity plan and turned over to the Owner at closeout.
6.3.4 The supervisory network topology shall be as indicated in the datasheet.
Supervisory Network Topologyselect
Star - a switch in each equipment room home-run to a central BAS switch
Redundant ring between primary switches with star drops
Redundant ring between primary switches, no star drops
Single switch serving all supervisory devices
6.3.5 The physical media of each supervisory network segment shall be as indicated in the datasheet.
Supervisory Network Physical Mediaselect
Category 6 balanced twisted pair
Category 6A balanced twisted pair
Multimode optical fiber, OM3
Multimode optical fiber, OM4
Singlemode optical fiber, OS2
Mixed copper horizontal with optical fiber backbone
6.3.6 Copper cabling, terminations, and channel lengths shall comply with ANSI/TIA-568, and the installed channel shall be tested and certified to the performance category specified.
6.3.7 Cable installed in a plenum used for environmental air shall be listed for that use in accordance with NFPA 90A and NFPA 70.
6.3.8 Network switches serving the BAS shall be managed switches capable of virtual LAN assignment, port-level access control, and log forwarding.
6.3.9 Unmanaged switches shall not be installed on the supervisory network.

6.4 Field Bus Network

6.4.1 The field bus protocol connecting equipment controllers to the supervisory layer shall be as indicated in the datasheet.
Field Bus Protocolselect
BACnet MS/TP over RS-485
BACnet/IP at each field controller
BACnet Secure Connect at each field controller
Control Network Protocol over twisted pair
Modbus RTU over RS-485
Wireless field bus per the manufacturer's published radio specification
6.4.2 The field bus data rate shall be as indicated in the datasheet, and every device on a segment shall be configured to that rate.
Field Bus Data Raterange
kbps
9.619.238.476.8115.2
6.4.3 The number of devices on any one field bus segment shall not exceed the count indicated in the datasheet.
Maximum Devices Per Field Bus Segmentrange
devices
8162432486496127
6.4.4 The measured token loop time on any segment shall not exceed the value indicated in the datasheet under full design load.
Maximum Measured Token Loop Timerange
ms
5010015020050010002000
NOTE A token-passing bus gives each master node the bus in turn, so response time at the operator workstation is bounded by how long the token takes to make one lap. Loop time rises with the number of masters and falls with the data rate, which is why segment loading and data rate are the two levers available when response is sluggish. (6.4.5)
6.4.6 Where the segment loading indicated in the datasheet is exceeded, or where the measured token loop time exceeds the specified maximum, the Contractor shall subdivide the segment at no additional cost to the Owner.
6.4.7 Field bus cable shall be as indicated in the datasheet.
Field Bus Cableradio
● 22 AWG shielded twisted pair with foil shield and drain conductor
○ 20 AWG shielded twisted pair with foil shield and drain conductor
○ 18 AWG shielded twisted pair with foil shield and drain conductor
○ Composite cable with a shielded communication pair and a control power pair
6.4.8 Field bus segments shall be wired in a daisy chain from device to device.
6.4.9 Star, branch, and spur topologies shall not be used on an RS-485 field bus segment.
6.4.10 A terminating resistor matched to the cable characteristic impedance shall be installed at each of the two physical ends of every RS-485 segment, and at no other point on the segment.
Field Bus Terminating Resistancerange
Ω
100120150
6.4.11 The total length of any single RS-485 segment shall not exceed the length indicated in the datasheet without an intervening repeater.
Maximum Field Bus Segment Lengthrange
ft
1000200030004000
6.4.12 The cable shield drain shall be continuous through every device on the segment and shall be bonded to ground at one point only.
NOTE Bonding a shield at both ends puts the two ground potentials in parallel with the drain conductor. The resulting circulating current appears as intermittent communication faults that move around the segment, which is why the symptom is usually reported as random device dropouts rather than as a grounding problem. (6.4.13)

6.5 Non-Native Equipment Integration

6.5.1 Equipment whose native communication interface is not the selected open protocol shall be integrated through a gateway that presents the equipment's points to the supervisory layer as objects of the selected open protocol.
6.5.2 The gateway implementation shall be as indicated in the datasheet.
Gateway Implementationradio
○ Gateway function embedded in the supervisory controller
○ Standalone gateway appliance
○ Gateway software hosted on the BAS server
○ Gateway module furnished with the integrated equipment
NOTE A standalone gateway keeps the integration on its own hardware, so a failure or a firmware update on the gateway does not disturb the supervisory controller's own logic; an embedded gateway removes a device, a power supply, and a network drop from the installation. The number of integrated points and the criticality of the integrated equipment usually decide between them. (6.5.3)
6.5.4 The integration submittal shall include the register or object map, the polling interval, the timeout and retry parameters, and the behavior of each integrated object when communication with the source device is lost.
6.5.5 Integrated objects shall be presented with the same naming convention, engineering units, and alarm treatment as natively communicating points.
6.5.6 Integrated points that are stale shall be marked as unreliable at the supervisory layer rather than presented as current values.
6.5.7 The Contractor shall verify with the equipment manufacturer that the register or object map submitted matches the firmware revision actually shipped with the equipment.

6.6 Device Addressing and Naming

6.6.1 Every device shall be assigned a device identifier unique across the entire system, and the assignment shall follow the addressing plan in the reviewed submittal.
6.6.2 Network numbers shall be unique across the entire internetwork, and no two segments shall share a network number.
6.6.3 Point names shall follow a single documented convention applied consistently across every controller, integrated subsystem, graphic, trend, and alarm definition.
6.6.4 The naming and tagging convention shall be as indicated in the datasheet.
Point Naming and Tagging Conventionselect
Owner's existing point naming standard
Semantic tagging per ANSI/ASHRAE 223
Project Haystack tagging
Brick schema
Controls contractor's documented convention, submitted for Engineer review
6.6.5 Where a semantic tagging convention is selected, the tag set applied to each point shall be included in the point database export at closeout.
NOTE The point name shown on the graphic, the point name in the trend definition, the point name in the alarm message, and the label on the field device shall be the same string. (6.6.6)

6.7 Time Synchronization

6.7.1 All servers, supervisory controllers, and field controllers shall be synchronized to a common time source.
6.7.2 The time source shall be as indicated in the datasheet.
Time Synchronization Sourceradio
○ Network Time Protocol server provided by the Owner's information technology organization
○ Dedicated Network Time Protocol appliance on the BAS network
○ BAS server acting as the authoritative time source for the system
○ Global navigation satellite receiver on the BAS network
6.7.3 Time drift between any controller and the system time source shall not exceed the value indicated in the datasheet.
Maximum Permitted Time Driftrange
seconds
15103060300
6.7.4 Daylight saving time transitions shall be applied automatically and consistently across every device, and the transition rule shall be configurable without a firmware change.
NOTE Trend records and alarm records from devices whose clocks disagree cannot be placed in sequence, so a fault that propagates across several controllers cannot be traced to its origin. (6.7.5)

7 Server and Operator Workstation

7.1 Server Platform

7.1.1 The BAS server shall host the operator interface, graphics, the alarm and event database, the historical trend database, schedule definitions, the user account directory, and the configuration backup repository.
7.1.2 The server hosting arrangement shall be as indicated in the datasheet.
Server Hosting Arrangementselect
Physical server on premises, furnished under this standard
Virtual machine on an Owner-provided hypervisor
Manufacturer-hosted cloud service
On-premises supervisory hardware with cloud-hosted archive and reporting
7.1.3 The server operating system shall be as indicated in the datasheet.
Server Operating Systemselect
Server-class Windows operating system, currently supported release
Linux distribution, currently supported long-term-support release
Manufacturer-furnished appliance operating system
7.1.4 The server operating system shall be a release for which the vendor is currently publishing security updates, both at the time of installation and at the time of substantial completion.
7.1.5 An operating system release that has passed its vendor end-of-support date shall not be placed in service.
7.1.6 Where the operating system release installed at the start of the project reaches end of support before substantial completion, the Contractor shall migrate the system to a supported release before acceptance at no additional cost to the Owner.
7.1.7 The Contractor shall size the server for the point count, trend volume, and retention specified for this project, and shall submit the sizing basis.
Minimum Server Spare Resource Capacity at Substantial Completionrange
%
1020253050100

7.2 Database Backup and Restoration

7.2.1 The server shall automatically back up controller programs, graphics, schedules, alarm definitions, trend definitions, user accounts, and the server database to a storage location separate from the server itself.
7.2.2 The backup destination shall be as indicated in the datasheet.
Configuration Backup Destinationcheckbox
☑ Local network attached storage on the BAS network
☐ Owner's enterprise backup platform
☐ Off-site cloud storage
☐ Standby server maintained by continuous replication
☐ Removable media held by the Owner's building engineering staff
7.2.3 The backup interval shall not exceed the value indicated in the datasheet.
Maximum Configuration Backup Intervalrange
hours
148122472168
7.2.4 Backups shall be retained for at least the period indicated in the datasheet.
Minimum Configuration Backup Retentionrange
days
7143060901803651095
7.2.5 The Contractor shall restore a full configuration backup to a test platform before substantial completion, demonstrate that the restored system operates, and submit the record of that test.
NOTE A backup that has never been restored is a hypothesis. The restoration test is the only step in a backup regime that produces evidence, and it is also the step that discovers which pieces of the configuration the backup routine was never capturing. (7.2.6)

7.3 Operator Client

7.3.1 The operator client types provided shall be as indicated in the datasheet.
Operator Client Types Providedcheckbox
☑ Web browser client requiring no installed software
☐ Manufacturer-installed application client on a dedicated workstation
☐ Mobile or tablet client for field engineering
☐ Wall-mounted operator display in the operations center
7.3.2 A browser client shall operate on the current release of at least two independent browser engines without a vendor-supplied plug-in.
7.3.3 Where a dedicated always-on workstation is provided, it shall be furnished with the display, mounting, and uninterruptible power identified in the submittal.
7.3.4 The number of concurrent operator sessions supported without additional licensing shall be as indicated in the datasheet.
Minimum Concurrent Operator Sessionsrange
sessions
125102550100
NOTE A client that requires installed software puts the Owner's information technology organization in the path of every operator addition and every workstation replacement; a browser client moves that dependency to the browser release cycle instead. Which dependency is easier to live with depends on how the Owner manages endpoints. (7.3.5)

7.4 User Accounts and Role-Based Access

7.4.1 The system shall enforce role-based access control with distinct roles for viewing, for operating, for configuring, and for administering accounts.
7.4.2 Each named individual shall be assigned an individual account.
7.4.3 Shared or generic accounts shall not be configured, except for a single break-glass administrative account whose credential is held under the Owner's documented procedure.
7.4.4 The authentication method shall be as indicated in the datasheet.
Authentication Methodradio
○ Accounts local to the BAS server
○ Directory service integration by LDAP or Active Directory
○ Federated authentication by SAML
○ Federated authentication by OpenID Connect
7.4.5 The scope of multi-factor authentication shall be as indicated in the datasheet.
Multi-Factor Authentication Scoperadio
○ Not required
○ Required for remote access sessions
○ Required for accounts holding configuration or administrative privilege
● Required for remote access sessions and for accounts holding configuration or administrative privilege
○ Required for all accounts
7.4.6 Each account shall be granted the least privilege that permits the account holder to perform that holder's function.
7.4.7 Account creation, modification, and deactivation shall follow a documented procedure that records who requested the change, who made it, and when.
7.4.8 Where a directory service is used, account deactivation in the directory shall remove BAS access without a separate action on the BAS.
NOTE An account that outlives the person's employment is the most common way a control system is reached by someone who no longer has a reason to reach it, and a system holding only local accounts has no event that triggers its removal. (7.4.9)

8 Graphics and Operator Interface

8.1 Graphic Page Hierarchy

8.1.1 The operator interface shall be organized as a navigable hierarchy from a site or building landing page, through floor plans and system schematics, to individual equipment pages.
8.1.2 Every page shall be reachable both by selecting a labeled region on the page above it and through a persistent navigation menu.
8.1.3 The path from the landing page to any equipment page shall require no more than the number of selections indicated in the datasheet.
Maximum Navigation Depth to Any Equipment Pagerange
selections
234568
8.1.4 The graphic style shall be as indicated in the datasheet.
Equipment Graphic Styleselect
Schematic line drawing with dynamic value overlays
Photorealistic equipment rendering with dynamic value overlays
Schematic terminal equipment with photorealistic central plant pages
NOTE An equipment graphic exists so a trained operator can read the state of the system - flow paths, equipment status, active values, active alarms - without reading text. Rendered detail that does not change with the system carries no state and competes for attention with the values that do, which matters most on the pages an operator opens during a callout. (8.1.5)
8.1.6 Where photorealistic rendering is used, dynamic values shall remain legible against the rendering at the display resolutions specified for the operator clients.
8.1.7 Every displayed value shall carry its engineering units.
8.1.8 Every displayed value shall indicate when it is stale, unreliable, or out of service, and shall not present the last received value as though it were current.

8.2 Required Graphic Pages

8.2.1 The Contractor shall provide, at minimum, the following graphic pages:
  • A site or building landing page showing current outdoor conditions, a system status summary, and the count of unacknowledged alarms by priority
  • A floor plan for each floor showing major equipment and control zones, with navigation regions to zone detail
  • A page for each central plant system showing every item of equipment, valve, pump, sensor, setpoint, and current reading with engineering units
  • A page for each air handling unit, energy recovery device, exhaust fan, and other central air-side equipment item showing every monitored and controlled point
  • A page or repeating template for each terminal unit showing every monitored and controlled point
  • A page for each integrated subsystem showing the integrated points and the communication status of the subsystem
  • An outdoor conditions page showing dry-bulb temperature, relative humidity, dew point, and wet-bulb temperature with a trend window
  • A schedule page listing every defined schedule, its current state, and the equipment it commands
  • An alarm page showing active alarms, recently acknowledged alarms, and a searchable alarm history
  • A network status page showing every controller, its communication state, and the time of its last successful communication

8.3 Setpoint Adjustment and Override Behavior

8.3.1 Setpoint adjustments and equipment commands issued from a graphic shall be written to the controlled object at a defined command priority.
8.3.2 Operator commands issued from a graphic shall be written at the manual operator priority.
8.3.3 Scheduled and supervisory program commands shall be written at a priority lower than the operator priority.
8.3.4 Releasing an override shall relinquish that priority slot and return the object to the highest-priority command still active.
8.3.5 Every graphic shall indicate when a displayed point is under an active override and at what priority.
8.3.6 The system shall provide a page listing every point currently held under an override, the priority of each, the account that issued it, and the time it was issued.
8.3.7 The system shall generate an alarm for any override that remains active longer than the duration indicated in the datasheet.
Maximum Override Duration Before Alarmrange
hours
1482472168720
NOTE An override left in place after a service call is indistinguishable from a control failure at the next callout, because the loop reads as if it is ignoring its own sequence. An expiry alarm converts a silent condition into a visible one. (8.3.8)

8.4 Engineering Units and Value Resolution

8.4.1 The display unit system shall be as indicated in the datasheet.
Display Unit Systemradio
● Inch-pound
○ SI
○ Selectable by operator account
8.4.2 A single graphic page shall not mix unit systems.
8.4.3 Displayed resolution shall not exceed the resolution the source device actually reports.
8.4.4 Temperature values shall be displayed to the number of decimal places indicated in the datasheet.
Displayed Decimal Places - Temperaturerange
decimal places
12
NOTE Displaying more digits than the sensor resolves invites operators to chase changes that are quantization noise, and it makes trend graphs look unstable when the measurement is not. (8.4.5)

9 Occupancy Scheduling

9.1 Schedule Structure

9.1.1 The schedule types provided shall be as indicated in the datasheet.
Schedule Types Providedcheckbox
☑ Weekly recurring schedule with a distinct daily profile for each day
☑ Holiday and exception schedules that override the weekly schedule
☑ Calendar schedule for yearly recurring events
☐ Event-driven schedule triggered by a system input
☐ Demand response schedule triggered by a utility signal
☐ Temporary occupancy schedule with an automatic expiry
9.1.2 Each schedule shall produce a discrete output object that the controllers it serves consume directly.
9.1.3 One schedule shall be capable of serving multiple controllers and multiple equipment types.
9.1.4 Schedule changes made by an operator shall be recorded in the audit log with the account, the time, and the previous value.
9.1.5 The number of independent schedules the system supports shall be at least the value indicated in the datasheet.
Minimum Independent Schedules Supportedrange
schedules
10255010025050010002000
NOTE A schedule that is copied into each controller instead of shared has to be edited once per controller, and the copies drift; a shared schedule object is edited once and the drift has nowhere to start. (9.1.6)

9.2 Optimum Start and Optimum Stop

9.2.1 Where the adopted energy code requires optimum start control, the system shall provide it for the equipment the code identifies, regardless of the datasheet selections below.
9.2.2 The scope of optimum start control shall be as indicated in the datasheet.
Optimum Start Scoperadio
○ Not applied
○ Applied to central air handling equipment
○ Applied to central air handling equipment and terminal units
○ Applied to central air handling equipment, terminal units, and central plant equipment
9.2.3 The scope of optimum stop control shall be as indicated in the datasheet.
Optimum Stop Scoperadio
○ Not applied
○ Applied to central air handling equipment
○ Applied to central air handling equipment and terminal units
○ Applied to central air handling equipment, terminal units, and central plant equipment
9.2.4 Optimum start shall determine the latest startup time that still brings each zone to its occupied setpoint by the start of occupancy, using measured indoor and outdoor conditions and an adaptive term that adjusts from the previous day's result.
9.2.5 Optimum stop shall end active heating or cooling before the end of occupancy by an interval that keeps each zone within its occupied comfort band through the remainder of the occupied period.
9.2.6 The system shall limit the optimum start interval to the maximum indicated in the datasheet.
Maximum Optimum Start Intervalrange
hours
123468
NOTE An unbounded adaptive start interval will chase an unrelated fault - a failed heating valve, a fouled coil - by starting earlier every day until the equipment effectively runs continuously, and the extra runtime hides the fault it is compensating for. (9.2.7)

9.3 Holiday and Calendar Maintenance

9.3.1 The system shall support at least the number of holiday and exception days per year indicated in the datasheet.
Minimum Holiday and Exception Days Supported Per Yearrange
days
102550100365
9.3.2 A holiday entered once shall propagate to every schedule that references the holiday calendar without per-schedule re-entry.
9.3.3 The Contractor shall load the calendar with at least the number of years of dates indicated in the datasheet before substantial completion.
Years of Calendar Dates Loaded at Substantial Completionrange
years
123510
9.3.4 Calendar maintenance beyond the loaded period is the Owner's responsibility, and the training required by this standard shall cover the procedure.

10 Alarming and Event Management

10.1 Alarm Priority Structure

10.1.1 The system shall support at least the number of distinct alarm priority levels indicated in the datasheet.
Minimum Alarm Priority Levelsrange
levels
23456810
10.1.2 Every defined alarm shall be assigned a priority and at least one routing destination.
10.1.3 The alarm strategy submittal shall state, for each priority level, the response the priority is intended to require and the time frame in which that response is expected.
10.1.4 Alarms at the highest defined priority shall remain visible on the landing page of the operator interface until acknowledged.
10.1.5 Acknowledging an alarm shall record the acknowledging account and the time in the alarm history.
10.1.6 The alarm history shall be retained for at least the period indicated in the datasheet, independent of trend retention.
Minimum Alarm History Retentionrange
days
3090180365730109518253650

10.2 Alarm Routing

10.2.1 Alarms shall be routable to the destinations indicated in the datasheet.
Alarm Routing Destinationscheckbox
☑ Operator workstation
☐ Local annunciator at the building engineering office
☑ Electronic mail to building engineering staff
☐ Electronic mail to the Owner's maintenance management system
☐ Short message or push notification to on-call staff
☐ Owner's information technology service management platform
☐ Owner's security information and event management platform
10.2.2 Routing shall be configurable independently by alarm priority and by time of day.
10.2.3 Where an alarm is routed off the BAS network, the transport shall use the mechanism approved in the cybersecurity plan.
10.2.4 The Contractor shall demonstrate each configured routing destination during functional testing by generating a live alarm at each priority.

10.3 Alarm Suppression

10.3.1 The suppression mechanisms provided shall be as indicated in the datasheet.
Alarm Suppression Mechanisms Providedcheckbox
☑ Parent-child suppression of downstream alarms when upstream equipment is commanded off
☑ Time-delay suppression of conditions shorter than a configured duration
☑ Operator-initiated maintenance mode on a selected item of equipment
☑ Startup suppression for a configured interval after an equipment start command
☐ Schedule-based suppression during unoccupied periods
10.3.2 Every suppression rule shall be documented in the alarm strategy submittal with its trigger, its scope, and its release condition.
10.3.3 Suppression applied by an operator shall have a configured expiry, after which the suppressed alarms are automatically restored.
10.3.4 The system shall provide a page listing every alarm currently suppressed, the rule suppressing it, and the time the suppression expires.
NOTE An alarm flood after a single upstream failure trains operators to dismiss the whole batch, which is how the one alarm in the batch that was not a consequence of the upstream failure gets dismissed with it. (10.3.5)

10.4 Minimum Alarm Set

10.4.1 The system shall implement, at minimum, alarms for the following conditions:
  • Loss of communication with any controller or integrated device, after a configured delay
  • Sensor input outside its configured range, or reporting a fault condition
  • Control loop deviation from setpoint beyond a configured band for a configured duration
  • Commanded equipment not proving status, and equipment proving status while commanded off
  • Filter differential pressure above its configured limit
  • Freeze protection device trip on any unit handling outdoor air
  • Duct smoke detection status received from the fire alarm system
  • Environmental conditions outside their limits in spaces designated as critical as indicated on the contract documents
  • Loss of a field bus segment at the supervisory layer
  • Configuration backup failure
  • Repeated failed authentication attempts beyond a configured threshold
  • Override active beyond its configured maximum duration
10.4.2 Alarm limits and delays shall be set to the design values before functional testing and tuned during the tuning period on the basis of observed system behavior.
10.4.3 Every alarm limit change made after acceptance shall be recorded in the audit log.

11.1 Trend Sampling

11.1.1 The sampling method for analog points shall be as indicated in the datasheet.
Trend Sampling Method - Analog Pointsselect
Change of value with a configured increment
Fixed interval polling
Change of value with a periodic fixed-interval sample
11.1.2 The sampling method for binary and multi-state points shall be as indicated in the datasheet.
Trend Sampling Method - Binary and Multi-State Pointsselect
Change of state
Fixed interval polling
Change of state with a periodic fixed-interval sample
11.1.3 Where a fixed interval is used for sampling or as a periodic sample, that interval shall be as indicated in the datasheet.
Fixed Trend Sampling Intervalrange
minutes
1510153060
NOTE Change-of-value sampling records a point only when it moves by more than its configured increment, which suits values that are steady for long periods and reduces stored volume; a periodic sample added to it produces a heartbeat that distinguishes a value that has not changed from a collection that has stopped. (11.1.4)
11.1.5 Trend data shall be buffered on the controller and uploaded to the historian, and the controller buffer shall hold at least the duration indicated in the datasheet at the specified sampling rate.
Minimum Controller Trend Buffer Durationrange
hours
148244872168
11.1.6 Trend records uploaded from a controller buffer after a communication interruption shall be inserted into the historian at their original timestamps.

11.2 Trend Retention and Aggregation

11.2.1 Trend data shall be retained at its original sampling resolution for at least the period indicated in the datasheet.
Minimum Retention at Original Resolutionrange
days
730901803657301825
11.2.2 The aggregation applied to trend data after the original-resolution retention period shall be as indicated in the datasheet.
Trend Aggregation After Original-Resolution Retentionselect
None - data is discarded after the original-resolution retention period
None - data is retained at original resolution indefinitely, capacity permitting
Aggregated to 15-minute intervals
Aggregated to hourly intervals
Aggregated to daily intervals
11.2.3 Where aggregation is applied, the aggregated data shall be retained for at least the period indicated in the datasheet.
Minimum Retention of Aggregated Datarange
years
12351020
11.2.4 Aggregated records shall retain the minimum, maximum, and mean of each interval rather than a single sampled value.
NOTE Recent high-resolution data answers questions about a specific fault; long-horizon aggregated data answers questions about consumption, degradation, and contract disputes. The two windows serve different questions, which is why the retention decision for each is made separately. (11.2.5)
11.2.6 The historian shall permit export of any trended point over any retained period in a spreadsheet-readable format without manufacturer assistance.

11.3 Minimum Trended Points

11.3.1 The following points shall be trended continuously from substantial completion forward:
  • Outdoor air dry-bulb temperature and relative humidity
  • Zone temperature and every active zone temperature setpoint for each separately controlled zone
  • Supply, return, and mixed air temperatures at each air handling unit
  • Duct static pressure and its setpoint at each variable air volume air handling unit
  • Supply and return fan speed command and status at each air handling unit
  • Outdoor, return, and relief damper position at each air handling unit
  • Chilled water and heating water supply and return temperature at each plant and at each coil served by a control valve
  • Differential pressure and its setpoint at each variable-flow hydronic system
  • Pump speed command and status at each variable-speed pump
  • Terminal unit damper position, airflow rate, and reheat output for each terminal unit
  • Chiller, boiler, and cooling tower stage or capacity command and status
  • Metered electricity, fuel, and water consumption, and the flows and temperatures required to compute energy delivered by each central plant
11.3.2 Points trended for commissioning shall be retained in the trend configuration after commissioning is complete unless the Engineer directs otherwise in writing.

12 Field Sensors

12.1 Sensor Grade and Range Selection

12.1.1 Sensors shall be of commercial or industrial grade with published accuracy, repeatability, stability, and range.
12.1.2 Sensors whose published specifications do not state accuracy over a defined operating range shall not be installed.
12.1.3 Each sensor shall be selected so that the range of conditions the application actually produces falls within the central portion of the sensor range indicated in the datasheet.
Sensor Operating Band Within Sensor Rangerange
%
4050607080100
NOTE A sensor whose range is far wider than the application loses resolution at the operating point and produces a noisy signal that the control loop then chases; a sensor whose range is too narrow saturates during system transients and returns no usable feedback exactly when the loop most needs it. (12.1.4)
12.1.5 Sensor accuracy statements shall include the transmitter, not the sensing element alone, where the two are separate devices.

12.2 Temperature Sensors

12.2.1 The temperature sensing element shall be as indicated in the datasheet.
Temperature Sensing Elementradio
● 10 kΩ negative temperature coefficient thermistor
○ 20 kΩ negative temperature coefficient thermistor
○ 1000 Ω platinum resistance temperature detector
○ 100 Ω platinum resistance temperature detector
○ 1000 Ω nickel resistance temperature detector
12.2.2 Resistance temperature detectors of 100 Ω nominal resistance shall be wired in a three-wire or four-wire configuration so that lead resistance is compensated.
12.2.3 The combined error of the sensing element, its transmitter, and the controller input shall not exceed the value indicated in the datasheet for space, supply air, return air, and hydronic temperature measurement.
Maximum Combined Temperature Measurement Errorrange
°F
0.180.30.512
12.2.4 Space temperature sensors shall be mounted on interior partitions, away from supply air discharge, away from concealed piping and ductwork, and out of direct solar exposure.
12.2.5 Space temperature sensors shall be mounted at the height above finished floor indicated in the datasheet.
Space Temperature Sensor Mounting Heightrange
in.
1518244448546066
NOTE A space sensor on an exterior wall reads a blend of room air and wall surface temperature, and the offset moves with outdoor conditions, so the resulting error cannot be trimmed out with a fixed calibration offset. (12.2.6)
12.2.7 Temperature sensors in mixed air plenums and in any duct cross-section where stratification is expected shall be averaging elements traversing the cross-section.
Averaging Element Coveragerange
ft of element per ft² of duct area
0.511.523
NOTE A single-point sensor in a mixed air plenum reports the temperature of whichever stratified layer it sits in. The result reads as a control tuning problem, because the loop is stable but is holding the wrong plenum to the right number. (12.2.8)
12.2.9 Outdoor air temperature sensors shall be installed within a ventilated radiation shield.
12.2.10 Outdoor air temperature sensors shall be located away from exhaust discharge, from equipment condenser discharge, and from surfaces that receive direct solar exposure.
NOTE An unshielded outdoor sensor in sun reads correctly at night and reads high by a wide margin during the day, which shifts economizer changeover and outdoor-air reset in the direction that costs the most energy. (12.2.11)

12.3 Humidity Sensors

12.3.1 The humidity sensing technology shall be as indicated in the datasheet.
Humidity Sensing Technologyradio
● Capacitive thin-film polymer
○ Resistive polymer
○ Chilled mirror hygrometer
12.3.2 The combined error of the humidity sensor and its transmitter shall not exceed the value indicated in the datasheet over the operating range of the application.
Maximum Combined Humidity Measurement Errorrange
% RH
1235
12.3.3 Humidity sensors serving spaces where humidity is actively controlled shall be selected for the tighter of the accuracy required by the sequence of operations and the value indicated in the datasheet.
Recommended Humidity Sensor Recalibration Intervalrange
months
61218243660
NOTE Polymer humidity elements drift with cumulative exposure to high humidity and to airborne contaminants, so a sensor that met its published accuracy at installation will not still meet it after several seasons without recalibration or replacement. (12.3.5)

12.4 Carbon Dioxide Sensors

12.4.1 Carbon dioxide sensors serving demand-controlled ventilation shall meet the sensor requirements of ANSI/ASHRAE 62.1 for that application.
12.4.2 The carbon dioxide measurement technology shall be as indicated in the datasheet.
Carbon Dioxide Measurement Technologyradio
○ Single-beam non-dispersive infrared
● Dual-beam non-dispersive infrared
○ Photoacoustic non-dispersive infrared
○ Electrochemical
12.4.3 The measurement range of each carbon dioxide sensor shall be as indicated in the datasheet.
Carbon Dioxide Sensor Measurement Range, Upper Limitrange
ppm
20003000500010000
12.4.4 The combined error of the carbon dioxide sensor and its transmitter shall not exceed the value indicated in the datasheet, or the percentage of reading indicated in the datasheet, whichever is greater.
Maximum Carbon Dioxide Measurement Error, Absolute Termrange
ppm
20305075100150
Maximum Carbon Dioxide Measurement Error, Proportional Termrange
%
123510
12.4.5 Automatic background calibration shall be configured as indicated in the datasheet.
Automatic Background Calibrationradio
○ Enabled with the manufacturer's default baseline interval
○ Enabled with the baseline interval set for the occupancy pattern of the space served
○ Disabled
NOTE Automatic background calibration assumes the sensor is exposed to near-outdoor carbon dioxide concentration at some point within each baseline interval, and it re-references the sensor to that minimum. In a space that is occupied continuously, the assumed minimum never occurs and the algorithm re-references to an elevated concentration, so the reading drifts downward over successive cycles. (12.4.6)
12.4.7 Automatic background calibration shall be disabled on sensors serving spaces that are occupied continuously, and the Contractor shall identify those sensors in the point database export.

12.5 Pressure Sensors

12.5.1 The measurement range of each differential pressure sensor used for duct static pressure control shall be as indicated in the datasheet.
Duct Static Pressure Sensor Range, Upper Limitrange
in. w.g.
0.512351020
Per drawings — as indicated on the mechanical drawings and equipment schedules
12.5.2 The measurement range of each hydronic pressure and differential pressure sensor shall be as indicated in the datasheet.
Hydronic Pressure Sensor Range, Upper Limitrange
psig
153050100150300600
Per drawings — as indicated on the mechanical drawings and equipment schedules
12.5.3 The accuracy of each pressure sensor shall not exceed the percentage of full scale indicated in the datasheet.
Maximum Pressure Sensor Error, Percent of Full Scalerange
%
0.10.250.512
12.5.4 Duct static pressure sensing taps shall be located at the position established by the sequence of operations and the reset strategy as indicated on the mechanical drawings.
12.5.5 Hydronic pressure sensors shall be installed with an isolation valve and a means of removing the sensor without draining the system.
12.5.6 Sensor tubing runs shall be as short as practical, shall be pitched to drain, and shall be supported so that they cannot be crushed or disconnected during maintenance access.

12.6 Airflow Measurement Stations

12.6.1 Where the sequence of operations requires measured outdoor airflow, an airflow measurement station shall be provided.
12.6.2 The airflow measurement technology shall be as indicated in the datasheet.
Airflow Measurement Technologyselect
Multi-point thermal dispersion array
Multi-point pitot array with differential pressure transmitter
Averaging annular pitot element with differential pressure transmitter
Vortex shedding element
Fan inlet cone differential pressure measurement
Airflow inferred from fan speed and pressure using the manufacturer's published fan performance data
12.6.3 The accuracy of each airflow measurement station shall not exceed the percentage of reading indicated in the datasheet across the range the application produces.
Maximum Airflow Measurement Error, Percent of Readingrange
%
12351015
12.6.4 Each airflow measurement station shall be installed with the upstream and downstream straight duct lengths published by its manufacturer for the mounting condition present.
12.6.5 Where the published straight-duct lengths cannot be achieved, the Contractor shall notify the Engineer before installation and shall propose either a flow conditioner or an alternative measurement location.
12.6.6 Airflow measurement stations shall be accessible for cleaning without removing ductwork.

13 Control Actuators

13.1 Damper Actuators

13.1.1 The control signal used by modulating damper actuators shall be as indicated in the datasheet.
Modulating Damper Actuator Control Signalselect
0-10 VDC analog
2-10 VDC analog
4-20 mA analog
Floating three-wire
Pulse-width modulated
Networked digital command on the field bus
Pneumatic
13.1.2 Two-position damper actuators shall be furnished for isolation and shutoff dampers whose sequence requires only open and closed positions.
13.1.3 The fail-safe mechanism for outdoor air, relief, and freeze-exposed dampers shall be as indicated in the datasheet.
Fail-Safe Mechanism - Outdoor Air, Relief, and Freeze-Exposed Dampersradio
● Mechanical spring return
○ Stored-energy electronic fail-safe
○ None - actuator holds last position on loss of power
13.1.4 The fail-safe mechanism for interior isolation and zone dampers shall be as indicated in the datasheet.
Fail-Safe Mechanism - Interior Isolation and Zone Dampersradio
○ Mechanical spring return
○ Stored-energy electronic fail-safe
● None - actuator holds last position on loss of power
13.1.5 Outdoor air dampers on units serving spaces subject to freezing conditions shall drive to the closed position on loss of control power or control signal.
13.1.6 Relief and exhaust dampers whose closure would pressurize an occupied space or a stairwell beyond its design limit shall drive to the position that relieves that pressure on loss of control power.
13.1.7 Dampers whose position is part of a smoke control sequence shall assume the position required by that sequence on loss of control power.
13.1.8 Damper actuators shall be sized for the damper's close-off torque at the maximum differential pressure the system can develop across the damper, with the margin indicated in the datasheet, and shall not be sized on running torque.
Minimum Damper Actuator Torque Margin Above Close-Off Torquerange
%
1020253350100
NOTE An actuator sized on running torque strokes correctly during commissioning and then fails to seat the last few degrees once the fan is at design static, which shows up as outdoor air leakage and coil freezing rather than as an actuator fault. (13.1.9)

13.2 Hydronic Valve Actuators

13.2.1 The control signal used by modulating valve actuators shall be as indicated in the datasheet.
Modulating Valve Actuator Control Signalselect
0-10 VDC analog
2-10 VDC analog
4-20 mA analog
Floating three-wire
Pulse-width modulated
Networked digital command on the field bus
Pneumatic
13.2.2 The fail-safe mechanism for heating coil control valves shall be as indicated in the datasheet.
Fail-Safe Mechanism - Heating Coil Control Valvesradio
● Mechanical spring return
○ Stored-energy electronic fail-safe
○ None - actuator holds last position on loss of power
13.2.3 The fail-safe mechanism for cooling coil control valves shall be as indicated in the datasheet.
Fail-Safe Mechanism - Cooling Coil Control Valvesradio
○ Mechanical spring return
○ Stored-energy electronic fail-safe
○ None - actuator holds last position on loss of power
13.2.4 Heating coil control valves on coils exposed to outdoor air below freezing shall drive to the open position on loss of control power or control signal.
13.2.5 Cooling coil control valves shall drive to the closed position on loss of control power unless the sequence of operations for that unit requires otherwise.
13.2.6 Valve actuators shall be sized to close the valve against the maximum differential pressure the pumping system can develop at the valve with all other valves closed.
NOTE Actuator close-off rating shall be verified against the pump shutoff head, not against the design differential pressure, because the differential pressure at a single valve rises as the rest of the system closes. (13.2.7)

13.3 Variable Frequency Drive Integration

13.3.1 Variable frequency drives serving equipment controlled by the BAS shall be integrated over the network interface required by HVAC Variable Frequency DrivesHVAC Variable Frequency DrivesResolves to the current adopted revision.sync/hvac-variable-frequency-drives.
13.3.2 The following points shall be available at the BAS for each integrated drive:
  • Start and stop command
  • Speed reference
  • Run status
  • Fault status with the manufacturer's fault code
  • Output frequency
  • Motor current
  • Motor power
  • Accumulated energy
  • Accumulated run hours
  • Bypass status where a bypass is furnished
  • Communication loss status
13.3.3 The BAS speed reference shall be written at a command priority that the drive's hand-off-auto selector and any hardwired safety interlock override.
13.3.4 Loss of BAS communication shall place each drive in the failure mode required by that equipment's sequence of operations, and that mode shall be configured in the drive and verified during functional testing.

14 Equipment Integration Points

14.1 Air Handling Unit Integration

14.1.1 The BAS shall execute the published sequence of operations for each air handling unit in accordance with Air Handling UnitsAir Handling UnitsResolves to the current adopted revision.sync/air-handling-units and the contract drawings.
14.1.2 The following points shall be available at the BAS for each air handling unit, except where the unit does not include the associated component:
  • Supply, return, mixed, and outdoor air temperature
  • Supply and return air humidity where humidity is controlled or monitored
  • Supply duct static pressure and its setpoint
  • Supply fan and return fan start command, speed command, speed feedback, and proven status
  • Heating and cooling coil control valve command and position feedback
  • Outdoor, return, and relief damper command and position feedback
  • Measured outdoor airflow where demand-controlled ventilation or ventilation verification is required
  • Freeze protection device status
  • Filter differential pressure and filter status
  • Smoke detection status received from the fire alarm system
  • Unit occupancy mode and the schedule commanding it
  • Every additional point named in that unit's published sequence of operations
14.1.3 The BAS shall present a per-unit summary showing the current operating mode, the active setpoints, and the controlling loop output.

14.2 Terminal Unit Integration

14.2.1 The BAS shall provide a field controller at each terminal unit furnished under Air Terminal UnitsAir Terminal UnitsResolves to the current adopted revision.sync/air-terminal-units.
14.2.2 The following points shall be available at the BAS for each terminal unit, except where the unit does not include the associated component:
  • Zone temperature
  • Occupied cooling, occupied heating, and unoccupied zone temperature setpoints
  • Primary air damper command and position feedback
  • Measured primary airflow and the active airflow setpoint
  • Reheat output command and status
  • Fan command and status on units with a terminal fan
  • Zone occupancy status from an occupancy sensor where one is provided
  • Zone carbon dioxide concentration where demand-controlled ventilation is applied to the zone
  • Every additional point named in the published terminal unit sequence of operations
14.2.3 Terminal unit controllers shall accept a zone setpoint adjustment range configured at the supervisory layer and shall enforce it locally.
Maximum Occupant Zone Setpoint Adjustment Rangerange
°F
1234510

14.3 Central Plant Integration

14.3.1 Chillers, boilers, cooling towers, pumps, heat exchangers, and other central plant equipment shall be integrated over the network interface each item provides.
14.3.2 Where an item of central plant equipment offers the selected open protocol natively, that native interface shall be used rather than a gateway.
14.3.3 The following points shall be available at the BAS for each item of central plant equipment, except where the equipment does not include the associated component:
  • Start and stop command and proven status
  • Capacity, stage, or speed command and feedback
  • Fault status with the manufacturer's fault code
  • Entering and leaving fluid temperature and pressure
  • Flow rate where a flow meter is provided
  • Energy or fuel consumption
  • Accumulated run hours and start count
  • Safety and limit device status
  • Every additional point named in that equipment's published sequence of operations
14.3.4 The BAS shall compute and trend the energy delivered by each central plant from the measured flow and temperature difference.
14.3.5 Plant equipment run hours and start counts shall be maintained across controller restarts and shall not be reset by a firmware update.

14.4 Water Treatment Controller Integration

14.4.1 The BAS shall integrate with the chemical treatment controllers furnished under HVAC Water TreatmentHVAC Water TreatmentResolves to the current adopted revision.sync/hvac-water-treatment.
14.4.2 The following points shall be available at the BAS for each treatment controller:
  • Measured conductivity and its setpoint
  • Blowdown valve status
  • Makeup water flow and accumulated volume
  • Blowdown flow and accumulated volume
  • Chemical feed status and low-level alarm for each chemical
  • Biocide cycle status
  • Treatment controller fault status
NOTE Cooling tower treatment records maintained by the BAS support the operational documentation required by a water management program under ANSI/ASHRAE 188, which asks for evidence that control limits were held rather than that a controller was installed. (14.4.3)

14.5 Balancing Agent Access

14.5.1 During the work of Testing Adjusting And BalancingTesting, Adjusting, and Balancing for HVACResolves to the current adopted revision.sync/testing-adjusting-and-balancing, the BAS shall provide the balancing agent with an account holding override authority over damper position, valve position, fan speed, and pump speed for the equipment being balanced.
14.5.2 The balancing agent's account shall be restricted from configuration changes, program editing, and account administration.
14.5.3 Every override issued under the balancing agent's account shall be recorded in the audit log.
14.5.4 At the completion of balancing, all overrides shall be released, the as-balanced values shall be recorded as the system baseline, and the balancing agent's account shall be deactivated.

14.6 Fire Alarm Interface

14.6.1 The interface between the fire alarm system and the BAS shall be by hardwired contacts at the fire alarm control unit in accordance with NFPA 72.
14.6.2 The fire alarm system shall command the fire and smoke control sequence directly.
14.6.3 The BAS shall receive the resulting status and shall mirror it at the operator interface, and shall not be relied on to execute the life safety sequence.
14.6.4 The BAS shall not be capable of overriding a fire alarm command to any item of mechanical equipment.
14.6.5 Interface wiring between the fire alarm control unit and BAS panels shall be monitored for integrity where NFPA 72 requires monitoring of that circuit.
14.6.6 Following restoration of a fire alarm condition, equipment shall return to its normal sequence only after the fire alarm system releases the condition and an operator resets the affected equipment where the sequence of operations requires a manual reset.
NOTE The interface described here is the boundary of this standard; the fire alarm system itself, including the smoke control sequence it commands, is governed by Fire Alarm SystemsFire Alarm SystemsResolves to the current adopted revision.sync/fire-alarm-systems. (14.6.7)

15 Operational Technology Cybersecurity

15.1 Baseline and Precedence

NOTE The BAS is operational technology whose availability and integrity affect occupant conditions, mechanical equipment, and energy use, and whose controllers run embedded software that is patched on a slower cycle than enterprise software. (15.1.1)
15.1.2 The cybersecurity provisions of this standard establish a minimum baseline consistent with the practices of NIST SP 800-82.
15.1.3 Where the Owner's information technology or security organization publishes requirements that exceed this standard, those requirements shall govern.
15.1.4 Where a requirement of the Owner's security organization conflicts with a requirement necessary for the mechanical system to operate safely, the Contractor shall notify the Engineer of Record in writing before implementing either, and the Engineer of Record shall make the initial determination.
15.1.5 The Contractor shall not implement a security control that disables a safety interlock, a freeze protection function, or a smoke control response.

15.2 Network Segregation

15.2.1 The segregation of the BAS network from other networks shall be as indicated in the datasheet.
BAS Network Segregation Methodselect
Physically separate cabling and switching dedicated to the BAS
Virtual LAN on shared switching with documented access control lists
Software-defined micro-segmentation on shared switching
Shared with the general data network without segregation
15.2.2 Unless the datasheet selects an unsegregated arrangement, the BAS shall not share a broadcast domain with the general data network, with guest networks, or with video surveillance networks.
15.2.3 Where the datasheet selects an unsegregated arrangement, the Contractor shall record that condition in the cybersecurity plan together with the compensating controls applied, and the Owner's security organization shall accept it in writing before energization.
15.2.4 Traffic between the BAS network and any other network shall pass a firewall configured to permit only the protocols, ports, and source addresses required for identified BAS functions.
15.2.5 Every firewall rule permitting traffic to or from the BAS network shall be documented with the function it serves and the date it was created.
15.2.6 Firewall rules shall be reviewed at the interval indicated in the datasheet, and the review shall be recorded.
Firewall Rule Review Intervalrange
months
36122436
NOTE The most common path into a control network is not an attack on the control protocol; it is a route that was opened for a legitimate reason, documented nowhere, and never closed after the reason expired. (15.2.7)

15.3 Remote Access

15.3.1 Remote access to the BAS shall be by the method indicated in the datasheet.
Remote Access Methodselect
No remote access - site-local operation only
Owner-managed virtual private network
Owner-managed jump host in a demilitarized zone with session recording
Manufacturer-hosted cloud connector
Owner-managed virtual private network with a jump host for privileged sessions
15.3.2 BAS servers, supervisory controllers, and operator client interfaces shall not be reachable directly from the public internet.
15.3.3 A manufacturer-hosted cloud connector shall not be installed unless the datasheet selects it and the Owner has accepted it in writing.
15.3.4 Where a cloud connector is installed, it shall authenticate on every session, shall log every session with the identity of the remote party, and shall be capable of being disabled by the Owner without a manufacturer service call.
15.3.5 Remote sessions by the Contractor or the manufacturer during the warranty period shall be logged and shall be available to the Owner on request.

15.4 Credential and Account Management

15.4.1 Every default and vendor-supplied credential shall be changed before the device is placed in service, on every device that has an authentication interface, including servers, supervisory controllers, programmable controllers, gateways, network switches, and uninterruptible power supplies with network management cards.
15.4.2 The Contractor shall submit at substantial completion a signed statement identifying every device whose default credentials were changed.
15.4.3 The Owner's representative may select a sample of devices for verification, and the Contractor shall demonstrate on request that the default credential no longer authenticates.
15.4.4 Where verification finds a device still holding a default credential, the Contractor shall remediate every device of that type at the Contractor's cost and shall repeat the verification.
15.4.5 The password policy shall be as indicated in the datasheet.
Password Policy Sourceselect
Owner's directory service password policy
Minimum length and complexity policy configured on the BAS server
Passphrase policy with no scheduled expiry, paired with multi-factor authentication
Owner's privileged access management platform
15.4.6 Credentials shall not be embedded in graphics, scripts, integration configuration files, or documentation turned over to the Owner.
15.4.7 Service accounts used for integration shall be distinct from named user accounts and shall hold only the privileges the integration requires.

15.5 Patching and Firmware Maintenance

15.5.1 The interval between server operating system security patch cycles shall not exceed the value indicated in the datasheet.
Maximum Server Security Patch Intervalrange
days
714306090180365
15.5.2 The controller firmware update policy shall be as indicated in the datasheet.
Controller Firmware Update Policyselect
Updated on issuance of a manufacturer security bulletin affecting installed firmware
Updated on a scheduled review interval and on issuance of a security bulletin
Updated on a scheduled review interval only
Updated only when a vulnerability affecting installed equipment is identified by the Owner
15.5.3 Where a scheduled firmware review is selected, the review interval shall be as indicated in the datasheet.
Scheduled Firmware Review Intervalrange
months
36122436
15.5.4 The Contractor shall register the Owner to receive the manufacturer's security bulletins for every installed product line and shall confirm the registration at closeout.
15.5.5 Firmware shall be verified on a controller that is not serving occupied equipment, or on the manufacturer's test arrangement, before it is deployed to the installed base.
15.5.6 A configuration backup shall be taken and verified before any firmware update is applied.
15.5.7 Firmware updates during the warranty period shall be performed by the Contractor at no additional cost where the update addresses a manufacturer security bulletin or a defect.
15.5.8 Server operating system patching shall be scheduled with the Owner's information technology organization, and the Contractor shall perform it during the warranty period.

15.6 Audit Logging

15.6.1 The system shall log the events indicated in the datasheet.
Audit Log Eventscheckbox
☑ Successful authentication
☑ Failed authentication
☑ Account creation, modification, and deletion
☑ Privilege or role change
☑ Configuration change to programs, schedules, or alarm definitions
☑ Setpoint change and override write
☐ Backup and restore operations
☑ Firmware and software update
☑ Remote access session start and end
15.6.2 Each logged event shall record the timestamp, the account, the source address where applicable, the object affected, and the previous and new values where the event changed a value.
15.6.3 Audit logs shall be retained for at least the period indicated in the datasheet.
Minimum Audit Log Retentionrange
days
309018036573010952555
15.6.4 Audit logs shall not be editable or deletable from the operator interface by any role.
15.6.5 Audit log forwarding shall be as indicated in the datasheet.
Audit Log Forwardingradio
○ Not forwarded - retained on the BAS server only
○ Forwarded to the Owner's security information and event management platform by syslog
○ Forwarded to the Owner's security information and event management platform by a manufacturer-supplied connector
○ Exported on a scheduled basis to Owner-designated storage

15.7 Removable Media

15.7.1 The removable media policy shall be as indicated in the datasheet.
Removable Media Policyradio
○ Prohibited on BAS servers, workstations, and programming devices
● Permitted only on Owner-issued media with documented authorization for each use
○ Permitted on any media after scanning by an Owner-approved tool
○ Unrestricted
15.7.2 Software, firmware images, and configuration files shall be transferred by the file transfer mechanism identified in the cybersecurity plan wherever that mechanism is available.
15.7.3 Each use of removable media on a BAS device shall be recorded with the date, the device, the account, and the purpose.
15.7.4 Programming laptops connected to the BAS network shall carry current endpoint protection and shall have been used on no network for which the Owner's security organization has not granted approval.

16 System Capacity and Expansion

NOTE The total point count drives controller hardware quantity, field bus segment count, server sizing, and, on platforms licensed by point, the license cost. It is developed from the equipment schedules and the sequences of operation, and it changes during shop drawing development as integrated equipment point lists arrive. (16.1)
16.2 The Contractor shall develop the project point count from the equipment schedules and the sequences of operation and shall submit it with the point list.
Total Active Pointsrange
points
100250500100025005000100002500050000100000
Per drawings — as indicated on the equipment schedules and sequences of operation
Hardware Input and Output Pointsrange
points
50100250500100025005000100002500050000
Per drawings — as indicated on the equipment schedules and sequences of operation
Network Integrated Pointsrange
points
50100250500100025005000100002500050000
Per drawings — as indicated on the equipment schedules and sequences of operation
16.3 The system shall be delivered with spare hardware input and output capacity of at least the percentage indicated in the datasheet, distributed across the installed controllers rather than concentrated in one panel.
Minimum Spare Hardware Input and Output Capacityrange
%
101520253050
16.4 The system shall be delivered with spare licensed point capacity of at least the percentage indicated in the datasheet above the commissioned point count.
Minimum Spare Licensed Point Capacityrange
%
1020253050100
16.5 Each field bus segment shall be delivered with spare device capacity of at least the percentage indicated in the datasheet below the specified maximum devices per segment.
Minimum Spare Field Bus Device Capacity Per Segmentrange
%
1020253050
NOTE Spare capacity is consumed by the tenant fit-outs and equipment replacements that follow occupancy. A system delivered at its licensed limit turns the first small addition into a licensing negotiation, which is a cost the Owner incurs to save a smaller cost at procurement. (16.6)

17 Panel and Field Installation

17.1 Controller Panel Installation

17.1.1 Controller panel enclosures shall carry the environmental rating indicated in the datasheet.
Controller Panel Enclosure Ratingselect
NEMA Type 1
NEMA Type 12
NEMA Type 3R
NEMA Type 4
NEMA Type 4X
17.1.2 Panels installed outdoors shall be rated NEMA Type 3R at minimum.
17.1.3 Panels installed in locations subject to washdown, hose-directed water, or persistent condensation shall be rated NEMA Type 4 or Type 4X.
17.1.4 Panels installed in locations subject to salt air, chemical exposure, or cooling tower drift shall be rated NEMA Type 4X.
17.1.5 Panels shall not be installed in classified hazardous locations unless listed for the classification present.
17.1.6 Panels shall be mounted near the equipment they serve, in locations accessible without removing other equipment and without a ladder placed on a roof edge or over equipment.
17.1.7 Clear working space in front of each panel shall be at least the dimension indicated in the datasheet, and the panel door shall open at least 90 degrees within that space.
Minimum Clear Working Space in Front of Controller Panelsrange
in.
30364248
17.1.8 Panels mounted on equipment or structures subject to vibration shall be isolated from that vibration.
17.1.9 Line-voltage and Class 2 wiring within a panel shall be separated by a barrier or routed in separate wireways.

17.2 Control Wiring Practices

17.2.1 Control and network wiring shall be installed in accordance with Conductors And CablesConductors and CablesResolves to the current adopted revision.sync/conductors-and-cables, Raceways And ConduitRaceways and ConduitResolves to the current adopted revision.sync/raceways-and-conduit, and NFPA 70 Article 725.
17.2.2 Class 2 control wiring shall not occupy the same raceway, cable tray compartment, or enclosure wireway as line-voltage conductors.
17.2.3 Where Class 2 control wiring runs parallel to line-voltage power wiring, the separation shall be at least the distance indicated in the datasheet.
Minimum Separation Between Class 2 Control Wiring and Power Wiringrange
in.
26121824
17.2.4 Where a crossing between control wiring and power wiring cannot be avoided, the two shall cross at approximately right angles.
17.2.5 Network and control cable shall be routed away from variable frequency drive output conductors for their full length.
NOTE Drive output conductors carry fast-switching pulse-width-modulated voltage, and the resulting capacitive coupling into a nearby shielded pair appears as communication errors and analog signal noise that come and go with drive speed. (17.2.6)
17.2.7 Cable shall not be spliced between the device and its termination.
17.2.8 Cable shall be supported independently of piping, ductwork, and equipment, and shall not be laid on ceiling grid or suspended from other trades' hangers.
17.2.9 Conductors shall be terminated on labeled terminal blocks, and more than the number of conductors indicated in the datasheet shall not be landed on one terminal point.
Maximum Conductors Per Terminal Pointrange
conductors
123
17.2.10 Slack shall be left at each termination sufficient to re-terminate the conductor at least twice.

17.3 Sensor and Actuator Installation

17.3.1 Sensors shall be installed in accordance with the manufacturer's published instructions and the location requirements of this standard.
17.3.2 Each measured sensor shall be compared against a reference instrument at startup, and both the as-found and as-left readings shall be recorded.
17.3.3 A sensor whose as-found reading differs from the reference by more than the specified measurement error shall be replaced rather than corrected by a software offset.
NOTE A software offset that compensates a sensor error is indistinguishable at the operator interface from a correct sensor, so the drift it hides is discovered only when the offset is large enough to affect control. It also becomes wrong at every condition other than the one at which it was set. (17.3.4)
17.3.5 Actuators shall be coupled to the damper or valve shaft in accordance with the manufacturer's instructions, with the shaft aligned and the coupling tightened to the published torque.
17.3.6 Each actuator shall be stroked from the BAS through its full travel in both directions and the resulting device position verified visually.
17.3.7 Damper actuator end positions shall be set so that the damper blades seat fully at the closed position and reach their design open position without over-travel.
17.3.8 Valve actuator end positions shall be set so that the valve closes without leakage at the design differential pressure and opens to its full rated travel.
17.3.9 Stroke verification results shall be recorded on the point-to-point verification record.

17.4 Identification and Labeling

17.4.1 The labeling method shall be as indicated in the datasheet.
Labeling Methodselect
Engraved phenolic laminate, mechanically fastened
Engraved phenolic laminate, adhesive applied
Thermal-transfer printed vinyl label rated for the service environment
Stainless steel tag on stainless wire
Brass tag on stainless wire
17.4.2 Labels shall be machine-produced.
17.4.3 Each controller panel shall carry a permanent nameplate identifying the panel designation, the equipment or zone it serves, the supervisory controller it reports to, the device identifier, and a service contact.
17.4.4 Each field-mounted sensor and actuator shall be labeled with the point name as it appears in the BAS database.
17.4.5 Each cable shall be labeled at every termination with its type, its source, and its destination.
17.4.6 Each conductor pair serving a field point shall be labeled at the controller termination with that point's name as it appears in the BAS database.
NOTE The single most common troubleshooting step at a controller panel is finding which pair belongs to the point that is misbehaving. A point name at the termination replaces a continuity trace with a glance. (17.4.7)
17.4.8 A current panel wiring diagram and point schedule shall be mounted inside each panel door in a protective pocket.
17.4.9 The panel point schedule shall be revised whenever a point is added, removed, or re-terminated.
17.4.10 A laminated system overview drawing showing the network topology, the location of each controller panel, and service contact information shall be mounted in the main mechanical room or the operator workstation room.
17.4.11 The system overview drawing shall be revised at every system change during the warranty period.

18 Testing and Commissioning

18.1 Factory Acceptance Testing

18.1.1 Factory acceptance testing shall be performed as indicated in the datasheet.
Factory Acceptance Testingradio
○ Not required
○ Required for pre-assembled plant control panels, documented by the Contractor
○ Required for pre-assembled plant control panels, witnessed by the Owner or the Commissioning Authority
○ Required for all pre-assembled panels, witnessed by the Owner or the Commissioning Authority
18.1.2 Factory acceptance testing shall verify panel assembly against the reviewed submittal, power-up of every device, communication between every device and the supervisory controller, rendering of the graphic pages associated with the tested panels, and execution of the loaded programs against simulated inputs.
18.1.3 Deficiencies found at factory acceptance testing shall be corrected before shipment.
18.1.4 Factory acceptance testing does not satisfy any part of the field functional testing requirement.

18.2 Field Functional Testing

18.2.1 The field functional testing scope shall include the activities indicated in the datasheet.
Field Functional Testing Scopecheckbox
☑ Point-to-point verification of every hardware input and output
☑ Sensor calibration verification against a reference instrument
☑ Actuator stroke verification through full travel in both directions
☑ Network verification including conformance, segment loading, and routing
☑ Sequence verification of every step of every published sequence
☑ Alarm verification of every defined alarm and every routing destination
☑ Schedule verification including holiday and exception behavior
☑ Trend verification confirming collection, buffering, and historian retrieval
☑ Failure mode verification by inducing loss of communication at each layer
☑ Cybersecurity verification of credentials, segregation, and audit logging
☐ Integrated systems test with the fire alarm system
18.2.2 Field functional testing shall be performed by the controls contractor and witnessed by the Commissioning Authority where one is engaged.
18.2.3 Each test shall produce a dated record identifying the item tested, the acceptance criterion, the observed result, and a disposition of pass, fail, or deficiency with a corrective action.
18.2.4 Failure mode verification shall demonstrate that each controller continues to execute its sequence with the layer above it disconnected, and shall demonstrate the recovery behavior when communication is restored.
18.2.5 Where a test fails, the Contractor shall correct the deficiency and repeat the test.
18.2.6 The cost of the Commissioning Authority's or the Engineer's attendance at a repeat test made necessary by a failure attributable to the Contractor's work shall be borne by the Contractor.

18.3 Network Performance Verification

18.3.1 The Contractor shall measure and record the token loop time on every field bus segment under full design load with all equipment operating.
18.3.2 The Contractor shall record the count of devices and the configured data rate on each segment.
18.3.3 The Contractor shall verify that every device identifier and every network number is unique across the system and matches the reviewed addressing plan.
18.3.4 The Contractor shall demonstrate routing between every pair of network segments that the sequences of operation require to exchange data.
18.3.5 Where a measured value does not meet the criteria of this standard, the Contractor shall correct the condition and repeat the measurement before requesting acceptance.

18.4 Sensor Calibration

18.4.1 Every measured sensor shall be calibrated at startup against a reference instrument whose accuracy is traceable as indicated in the datasheet.
Calibration Reference Traceabilityradio
● Certificate traceable to a national metrology institute, issued within the interval indicated below
○ Manufacturer factory calibration certificate issued within the interval indicated below
○ Comparison against an on-site reference instrument holding a current traceable certificate
Maximum Age of Reference Instrument Calibration Certificaterange
months
36121824
18.4.2 The reference instrument shall be at least three times more accurate than the specified measurement error of the sensor being calibrated.
18.4.3 Calibration shall be performed at conditions within the range the sensor experiences in service, and not at a single ambient condition for sensors whose service range is wider.
18.4.4 The calibration record shall identify the sensor by its system tag, the reference instrument and its certificate, the as-found reading, the as-left reading, and the technician.

18.5 Owner Training

18.5.1 The Contractor shall deliver training to Owner personnel covering navigation of the operator interface, alarm response and acknowledgement, schedule editing, override and release procedure, trend retrieval and export, backup and restoration, and the cybersecurity procedures that constrain Owner operation of the system.
18.5.2 Training shall total at least the number of hours indicated in the datasheet.
Minimum Owner Training Hoursrange
hours
481624406080
18.5.3 Training shall be delivered in at least the number of separate sessions indicated in the datasheet so that personnel on different shifts can attend.
Minimum Number of Training Sessionsrange
sessions
12346
18.5.4 At least one training session shall be delivered after the building has been through one seasonal changeover, where the warranty period extends that far.
18.5.5 Training shall be conducted on the installed system with the project's own graphics, schedules, and alarms.
18.5.6 Training materials shall include written procedures for each covered task, a recording of each session, and a quick-reference card for the tasks performed most often.
18.5.7 Training records shall identify the attendees, the dates, the topics, and the instructor.

19 Warranty

19.1 Warranty Period and Coverage

19.1.1 The Contractor shall warrant the BAS against defects in materials and workmanship under normal service for the periods indicated in the datasheet, measured from the date of substantial completion.
Warranty Period - Partsrange
years
123510
Warranty Period - Laborrange
years
1235
19.1.2 The warranty shall cover the cost of removing and reinstalling any item replaced under warranty, and the cost of repairing collateral damage caused by the failure or by the warranty repair itself.
19.1.3 Where a component is repaired or replaced under warranty, that component shall carry a new warranty of the same duration from the date of the repair, or the remainder of the original warranty period, whichever ends later.
19.1.4 Warranty response times shall meet the requirement stated under Controls Contractor Qualifications.

19.2 Post-Occupancy Tuning

19.2.1 The Contractor shall provide a tuning period following substantial completion for the duration indicated in the datasheet.
Post-Occupancy Tuning Periodrange
days
306090180365730
19.2.2 During the tuning period the Contractor shall respond to control loop instability, alarm limit adjustment, schedule adjustment, setpoint adjustment, and graphic corrections arising from operation of the building.
19.2.3 Work performed during the tuning period shall be at no additional cost to the Owner.
19.2.4 The Contractor shall record every change made during the tuning period and shall submit the record and an updated configuration backup at the end of the period.
NOTE A control system leaves the Contractor's hands before the building has run through its first full load range, so the settings at acceptance are estimates against an unoccupied building. The tuning period is where those estimates meet the loads the building actually has. (19.2.5)

19.3 Software and Firmware Support

19.3.1 The Contractor shall provide the software and firmware support indicated in the datasheet during the warranty period.
Software and Firmware Support During Warrantycheckbox
☑ Server operating system security patches
☑ BAS application software updates and security patches
☑ Controller firmware updates
☐ Graphic page changes within a defined monthly allowance
☐ Schedule and alarm definition changes within a defined monthly allowance
☐ Trend definition additions within a defined monthly allowance
☑ Annual cybersecurity configuration review
☐ Annual backup restoration test
19.3.2 Where a monthly allowance applies, the allowance shall be as indicated in the datasheet, and unused hours shall not accumulate between months.
Monthly Configuration Change Allowancerange
hours
248162440
19.3.3 Software and firmware updates applied during the warranty period shall be preceded by a verified configuration backup and shall be recorded in the audit log.

20 Spare Parts

20.1 The Contractor shall deliver the spare parts indicated in the datasheet at substantial completion.
Spare Parts Delivered at Substantial Completioncheckbox
☑ Spare hardware input and output modules of each type installed
☑ One spare controller of each model installed
☑ One spare control power transformer of each rating installed
☐ One spare network switch of each model installed
☑ Spare space temperature sensors
☐ Spare duct and immersion temperature sensors of each type installed
☐ Spare humidity sensors of each type installed
☐ Spare carbon dioxide sensors of each type installed
☐ Spare differential pressure transmitters of each range installed
☑ One spare damper actuator of each torque rating installed
☑ One spare valve actuator of each torque rating installed
☐ One spare gateway of each model installed
20.2 Spare hardware input and output modules shall be furnished in the quantity indicated in the datasheet, expressed as a percentage of the modules of that type installed.
Spare Hardware Module Quantityrange
%
510152025
20.3 Spare sensors shall be furnished in the quantity indicated in the datasheet for each sensor type selected in the spare parts list.
Spare Sensor Quantity Per Typerange
units
123510
20.4 Spare parts shall be of the same model, revision, and firmware level as the installed equipment, and the Contractor shall record the firmware level of each spare in the closeout package.
20.5 Spare parts shall be delivered in their original packaging and turned over against a written inventory signed by the Owner's representative.
20.6 Spare controllers and modules shall be stored in a conditioned location, and the storage location shall be identified in the closeout package.
NOTE Electrolytic capacitors and battery-backed memory in a controller held in storage age with temperature and humidity, so a spare kept in an unconditioned mechanical space may reach its failure point before it is ever installed. (20.7)

Edit this page

SynC Standards are reference material provided for informational purposes only and as a guide. They are not engineering, architectural, or legal advice and are not a substitute for the judgment of a licensed design professional. It is the responsibility of the user to determine the applicability of any standard to a specific project and to verify all requirements against the governing codes, manufacturer data, and project conditions. SynC does not render professional services and forms no professional relationship by publishing this content. Provided "as is," without warranty of any kind, including fitness for a particular purpose. See our Terms of Use for the complete terms. Moderation log.

This standard is published by SynC and licensed under Creative Commons Attribution-ShareAlike 4.0. You may share and adapt it, including commercially, provided you give credit, link to the license, indicate any changes, and license your adaptations under the same terms. Keep the attribution and notice below with any copy — it includes the warranty disclaimer the license requires you to retain.

Attribution & reuse notice — keep this with any copy:
"Building Automation System." SynC Standards. Licensed under CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). Source: https://synergyinconstruction.com/wiki/sync/building-automation-system — reference material only; not professional engineering advice and provided without warranty. Verify against governing codes and have a licensed professional review before use.