23 09 23.02.pdf

1005 Michael Rd Offce Renovation 210019

SECTION 23 09 23.02

BACNET DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS

02/ 25 MCBCL

PART 1 GENERAL

1.1 REFERENCES

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

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING

ENGINEERS (ASHRAE)

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

Interpretation 9-10 2022) BACnet—A Data Communication Protocol for Building Automation and Control Networks

UNDERWRITERS LABORATORIES (UL)

UL 916 (2015; Reprint Oct 2021) UL Standard for Safety Energy Management Equipment

1.2 DEFINITIONS

For definitions related to this section, see Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

1.3 SUBMITTALS

Submit detailed and annotated manufacturer's data, drawings, and specification sheets for each item listed, that clearly show compliance with the project specifications.

Submit the following in accordance with Section 01 33 00 SUBMITTAL

PROCEDURES:

SD-03 Product Data

Direct Digital Controllers ; G

Bacnet Gateways ; G

Notebook Computer ; G

Notebook Computer Software ; G

Bacnet Operator Workstation ; G

1.4 QUALITY CONTROL

Quality Control requirements are specified in Section 23 09 00

SECTION 23 09 23.02 Page 1

INSTRUMENTATION AND CONTROL FOR HVAC.

PART 2 PRODUCTS

All products used to meet this specification must meet the indicated requirements, but not all products specified here will be required by every project. All products must meet the requirements both Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC and this Section.

2.1 DDC SYSTEM

2.1.1 Supervisory Building Controller (SBC)

ASHRAE 135 building controller that is the main interface for the building control system. Provide a JACE based on the Niagara N4 platform. The JACE (JAVA Application Control Engine) shall be minimally based on a Tridium 8000 with expanded memory and embedded "Niagara Workbench or Workplace" software. The latest software revision available at the time the PVT Report is submitted must be installed.

Any device implementing the Niagara Framework is a Niagara Framework Supervisory Gateway and must meet these requirements. In addition to the general requirements for all DDC Hardware, Niagara Framework Supervisory Gateway Hardware must:

a. Be direct digital control hardware.

b. Have an unrestricted interoperability license and its Niagara Compatibility Statement (NiCS) must follow the Tridium Open NiCS Specification.

c. Manage communications between a field control network and the Niagara Framework Monitoring and Control Software, and between itself and other Niagara Framework Supervisory Gateways. Niagara Framework Supervisory Gateway Hardware must use Fox protocol for communication with other Niagara Framework Components, regardless of the manufacturer of the other components.

d. Be fully programmable using the Niagara Framework Engineering Tool and must support the following:

(1) Time synchronization, Calendar, and Scheduling using Niagara Scheduling Objects.

(2) Alarm generation and routing using the Niagara Alarm Service.

(3) Trending using the Niagara History Service and Niagara Trend Log Objects.

(4) Integration of field control networks using the Niagara Framework Engineering Tool.

(5) Configuration of integrated field control system using the Niagara Framework Engineering Tool when supported by the field control system.

e. Meet the following minimum hardware requirements:

SECTION 23 09 23.02 Page 2

(1) Two 10/100/1000 Mbps Ethernet Port(s)

(2) One or more MS/TP ports.

(3) Central Processing Unit of 1000 Mhz or higher.

(4) Embedded operating system.

f. Provide access to field control network data and supervisory functions via web interface and support a minimum of 16 simultaneous users.

Note: implementation of this capability may not be required on all projects.

g. Submit a backup of each Niagara Framework Supervisory Gateway. The backup must be sufficient to restore a Niagara Framework Supervisory Gateway to the final as-built condition such that a new Niagara Framework Supervisory Gateway loaded with the backup is indistinguishable in functionality from the original.

2.1.1.1 Niagara Framework Engineering Tool

The Niagara Framework Engineering Tool must be Niagara Workbench or an equivalent Niagara Framework engineering tool software and must:

a. Have an unrestricted interoperability license and its Niagara Compatibility Statement (NiCS) must follow the Tridium Open NiCS Specification.

b. Be capable of performing network configuration for Niagara Framework Supervisory Gateways and Niagara Framework Monitoring and Control Software.

c. Be capable of programming and configuring of Niagara Framework Supervisory Gateways and Niagara Framework Monitoring and Control Software.

d. Be capable of discovery of Niagara Framework Supervisory Gateways and all points mapped into each Niagara Framework Supervisory Gateway and making these points accessible to Niagara Framework Monitoring and Control Software.

2.1.1.2 Supervisory Controller MCEN Network Homerun

See Section 23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC paragraph Network Communication Lines for requirements.

2.1.2 EMCS Interface

The EMCS at Camp Lejeune is comprised of two separate systems. Both of the systems communicate over the basewide Marine Corps Enterprise Network (MCEN). One uses the Johnson Controls Network Automation Engine (NAE), Network Control Engine (NCE), Supervisory Network Engine (SNE) or Supervisory Network Control Engine (SNC) to the ADX server. The second system uses a Niagara FX N4 web supervisor with a JACE in the building communicating using Fox protocol. Because of IT security and permissions, only these systems and equipment are permitted as part of the EMCS.

SECTION 23 09 23.02 Page 3

2.1.2.1 Supervisory Building Controller

Provide a JACE. This will serve as both the Supervisory Building Controller and the connection point between the buildings DDC and the EMCS. Provide a five year service license on all Supervisory Controllers.

Provide a reserve of 10% of additional points and additional devices on the Supervisory Controller license at the final project acceptance.

The contractor shall assign the BAS Owner as the owner and manager of all licenses including 3rd party drivers.

2.1.2.2 Palo Alto Firewall

For any building provided with a new Supervisory controller, contractor shall also provide a Palo Alto Firewall Model PAN-PA-220R. Contractor shall also provide a five year government support option for the Palo Alto firewall complete with all licenses.

2.1.3 Direct Digital Controllers

a. Direct digital controllers shall be UL 916 rated.

b. Field Controllers:

(1) Acceptable DDC field controllers are Facility Explorer, Metasys or Distech.

c. Except for VAV's, all direct digital controllerss shall have an on board password protected display screen pre-programmed with the device's associated points. Display screens shall only be accessible after opening an enclosure door. Display screens that are accessible from an enclosure exterior are not permitted.

d. Include BACnet PICS for each controller/device type, including smart sensors (B-SS) and smart actuators (B-SA).

2.1.3.1 I/O Point Limitation

The total number of I/O hardware points used by a single stand-alone digital controller, including I/O expansion units, shall not exceed 64, except for complex individual equipment or systems. Place I/O expansion units in the same cabinet as the digital controller. The field controller must have one spare Configurable Output and one spare Universal Input available per system upon project completion, i.e. AHU, ERU, DOAS, HW System, CHW System and other building primary systems. VAV controllers and programmable thermostats are excluded.

2.1.3.2 Environmental Limits

Controllers shall be suitable for, or placed in protective enclosures suitable for the environment (temperature, humidity, dust, and vibration) where they are located.

2.1.3.3 Stand-Alone Controllers

Provide stand-alone direct digital controllers with internal time clocks if not connected to a Supervisory Building Controller. Each piece of equipment shall be controlled by a single controller to provide stand-alone control in the event of any building communication failure.

SECTION 23 09 23.02 Page 4

All I/O points specified for a piece of equipment shall be integral to its controller and serial connected expansion modules. Provide stable and reliable stand-alone control using default values or other method for values normally read over the network.

2.1.3.4 Internal Clock

Provide internal clocks and scheduling for all Direct Digital Controllers. Provide controllers with BTL listed profiles for all BACnet Building Controllers (B-BC) and BACnet Advanced Application Controllers (B-AAC) using BACnet time synchronization services. This includes but is not limited to VAV Controllers, Fan Coil controllers, Heat Pump controllers and any terminal controllers. BACnet Application specific controllers (B-ASC) will only be accepted for dedicated small exhaust system control such as restroom and mechanical room exhaust fans.

Automatically synchronize system clocks daily from an operator-designated controller. The system shall automatically adjust for daylight saving time.

2.1.3.5 Memory

Provide sufficient memory for each controller to support the required control, communication, trends, alarms, and messages. Protect programs residing in memory with EEPROM, flash memory, or by an uninterruptible power source (battery or uninterruptible power supply). The backup power source shall have capacity to maintain the memory during a 72-hour continuous power outage. Rechargeable power sources shall be constantly charged while the controller is operating under normal line power.

Batteries shall be replaceable without soldering. Trend and alarm history collected during normal operation shall not be lost during power outages less than 72 hours long.

2.1.3.6 Immunity to Power Fluctuations

Controllers shall operate at 90 percent to 110 percent nominal voltage rating.

2.1.3.7 Transformer

The controller power supply shall be fused or current limiting and rated at 125 percent power consumption. Each transformer must singularly serve the connected load, i.e. do not wire transfomers in parallel on the load side. Transformer shall be mounted in the upper portion of the control panel to aid in heat dissipation. The 120 volt power feed must also enter in the upper portion of the cabinet - power shall not be brought in from the bottom of the panel.

2.1.3.8 Wiring Terminations

Use screw terminal wiring terminations for all field-installed controllers. Provide field-removable modular terminal strip or a termination card connected by a ribbon cable for all controllers other than terminal units.

2.1.3.9 Input and Output Interface

Provide hard-wired input and output interface for all controllers as follows:

SECTION 23 09 23.02 Page 5

a. Protection: Shorting an input or output point to itself, to another point, or to ground shall cause no controller damage. Input or output point contact with sources up to 24 volts AC or DC for any duration shall cause no controller damage.

b. Binary Inputs: Binary inputs shall monitor on and off contacts from a "dry" remote device without external power, and external 5-24 VDC voltage inputs.

c. Pulse Accumulation Inputs: Pulse accumulation inputs shall conform to binary input requirements and accumulate pulses at a resolution suitable to the application.

d. Analog Inputs: Analog inputs shall monitor low-voltage (0-10 VDC), current (4-20 mA), or resistance (thermistor or RTD) signals.

e. Binary Outputs: Binary outputs shall send a pulsed 24 VDC low-voltage signal for modulation control, or provide a maintained open-closed position for on-off control. Where appropriate, provide a method to select normally open or normally closed operation.

f. Analog Outputs: Analog outputs shall send modulating 0-10 VDC or 4-20 mA signals to control output devices.

g. Tri-State Outputs: Tri-State outputs shall provide three-point floating control of terminal unit electronic actuators.

2.1.3.10 Digital Controller BACnet Internetwork

Provide intermediate gateways, only when requested by the Government and shown on the contract drawings, to connect existing non-BACnet devices to the BACnet internetwork. Controller and operator interface communication shall conform to ASHRAE 135, BACnet. If a controller becomes non-responsive, the remaining controllers shall continue operating and not be affected by the failed controller.

2.1.3.11 Communications Ports

a. Direct-Connect Interface Ports: Provide at least one extra communication port at each local BACnet network for direct connecting a notebook computer or BACnet hand-held terminal so all network BACnet objects and properties may be viewed and edited by the operator.

2.1.3.12 BACnet Gateways

Provide BACnet communication ports, whenever available as a plant equipment OEM standard option, for DDC integration via a single communication cable. Typical BACnet controlled plant equipment includes, but is not limited to, boilers, chillers, and variable frequency motor drives. Include the following information in the submittal:

a. BACnet and workstation display information

b. Bi-directional communication ability

c. Compliance with interoperability schedule

d. Expansion capacity

SECTION 23 09 23.02 Page 6

e. Handling of alarms, events, scheduling and trend data

f. Single device capability (not depending on multiple devices for exchanging information from either side of the gateway)

Provide gateways to connect BACnet to legacy systems, existing non-BACnet devices, and existing non-BACnet DDC controlled plant equipment, only when specifically requested and approved by the Government, and shown on the Government approved BACnet Communication Architecture Schematic. Provide with each gateway an interoperability schedule, showing each point or event on the legacy side that the BACnet "client" will read, and each parameter that the BACnet network will write to. Describe this interoperability in terms of BACnet services, or Interoperability Building Blocks (BIBBS), defined in ASHRAE 135 Annex K. Provide two-year minimum warranty for each gateway, including parts and labor.

The following minimum capabilities are required:

a. Gateways shall be able to read and view all readable object properties listed in the interoperability schedule on the non-BACnet network to the BACnet network and vice versa where applicable.

b. Gateways shall be able to write to all writeable object properties listed in the interoperability schedule on the non-BACnet network from the BACnet network and vice versa where applicable.

c. Gateways shall provide single-pass (only one protocol to BACnet without intermediary protocols) translation from the non-BACnet protocol to BACnet and vice versa.

d. Gateways shall meet the requirements of Data Sharing Read Property (DS-RP-B), Data Sharing Write Property (DS-WP-B), Device Management Dynamic Device Binding-B (DM-DDB-B), and Device Management Communication Control (DM-DCC-B) BIBBs, in accordance with ASHRAE 135.

e. Gateways shall include all hardware, software, software licenses, and configuration tools for operator-to-gateway communications. Provide backup programming and parameters on CD media and the ability to modify, download, backup, and restore gateway configuration.

2.1.3.13 Digital Controller Cabinet

Provide each digital controller including gateways, in a factory fabricated locked cabinet enclosure. Lock shall accept CAT102 keys.

Cabinets located indoors shall protect against dust and have a minimum NEMA 1 rating, except where indicated otherwise. Cabinets located outdoors or in damp environments shall protect against all outdoor conditions and have a minimum NEMA 4 rating. Mechanical rooms that contain steam service or equipment including new steam boiler rooms are considered damp environments. Outdoor control panels and controllers must be able to withstand extreme ambient conditions, without malfunction or failure, whether or not the controlled equipment is running. If necessary, provide a thermostatically controlled panel heater in freezing locations, and an internal ventilating fan in locations exposed to direct sunlight. Cabinets shall have a hinged lockable door and an offset removable metal back plate, except controllers integral with terminal units, like those mounted on VAV boxes. Provide like-keyed locks for all hinged panels provided and a set of two keys at each panel, with one key inserted in the lock. All

SECTION 23 09 23.02 Page 7 devices must be mounted only to the cabinet backplane with adequate space allowed for serviceability and proper heat dissipation from devices. The Supervisory controller cabinet door position (closed/open) shall be monitored with a door switch and BACnet programmable relay such as the Functional Devices RIBTW2401B-BC. An "open" door status shall initiate an alarm to the EMCS Server.

2.1.3.14 Main Power Switch and Receptacle

Provide each control cabinet with a main external power on/off switch located inside the cabinet. Also, provide each cabinet with a separate 120 VAC duplex convenience receptacle.

2.1.4 DDC Software

2.1.4.1 Programming

Provide programming to execute the sequence of operation indicated.

Provide all programming, tools, interfaces, cables, etc. to configure and program all controllers. All software shall be licensed to Marine Corps Base, Camp Lejeune Complex for unrestricted use on Camp Lejeune Complex and reproduction for use on Camp Lejeune Complex. Software keys and "dongles" are not permitted. Provide programming routines in simple, easy-to-follow logic with detailed text comments describing what the logic does and how it corresponds to the project's written sequence of operation. All logic programming and control functions shall be closed loop, command and feedback for fault detection and alarming when status does not match the command.

a. Graphic-based programming shall use a library of function blocks made from pre-programmed code designed for BAS control. Function blocks shall be assembled with interconnecting lines, depicting the control sequence in a flowchart. If providing a computer with device programming tools as part of the project, graphic programs shall be viewable in real time showing present values and logical results from each function block.

b. Menu-based programming shall be done by entering parameters, definitions, conditions, requirements, and constraints.

c. For line-by-line and text-based programming, declare variable types (variable types include but are not limited to the following: local, global, real, and integer) at the beginning of the program. Use descriptive comments frequently to describe the programming.

d. If providing a computer with device programming tools as part of the project, provide a means for detecting program errors and testing software strategies with a simulation tool. Simulation may be inherent within the programming software suite, or provided by physical controllers mounted in a NEMA 1 test enclosure. The test enclosure shall contain one dedicated controller of each type provided under this contract, complete with power supply and relevant accessories.

2.1.4.2 Parameter Modification

All writeable object properties, and all other programming parameters needed to comply with the project specification shall be adjustable for devices at any network level, including those accessible with web-browser communication, and regardless of programming methods used to create the

SECTION 23 09 23.02 Page 8 applications.

2.1.4.3 Short Cycling Prevention

Provide setpoint differentials and minimum on/off times to prevent equipment short cycling.

2.1.4.4 Equipment Status Delay

Provide an adjustable delay from when equipment is commanded on or off and when the control program looks to the status input for confirmation.

2.1.4.5 Run Time Accumulation

Use the Elapsed Time Property to provide re-settable run time accumulation for each Binary Output Object connected to mechanical loads greater than 1 HP, electrical loads greater than 10 KW, or wherever else specified.

2.1.4.6 Timed Local Override

Provide an adjustable override time for each push of a timed local override button.

2.1.4.7 Time Synchronization

Provide time synchronization, including adjustments for leap years, daylight saving time, and operator time adjustments.

2.1.4.8 Scheduling

Provide operating schedules as indicated, with equipment assigned to groups. Changing the schedule of a group shall change the operating schedule of all equipment in the group. Groups shall be capable of operator creation, modification, and deletion. Provide capability to view and modify schedules in a seven-day week format. Provide capability to enter holiday and override schedules one full year at a time.

2.1.4.9 Object Property Override

Allow writeable object property values to accept overrides to any valid value. Where specified or required for the sequence of control, the Out-Of-Service property of Objects shall be modifiable using BACnet's write property service. When documented, exceptions to these requirement are allowed for life, machine, and process safeties.

2.1.4.10 Alarms and Events

Alarms and events shall be capable of having programmed time delays and high-low limits. When a web server is connected to the BACnet internetwork, alarms/events shall report to web server as defined by an authorized operator. Otherwise alarms/events shall be stored within a device on the BACnet network until connected to a user interface device and retrieved. Provide alarms/events in agreement with the point schedule, sequence of operation, and the BAS Owner. At a minimum, provide programming to initiate alarms/events any time a piece of equipment fails to operate, a control point is outside normal range or condition shown on schedules, communication to a device is lost, a device has failed, or a controller has lost its memory.

SECTION 23 09 23.02 Page 9

2.1.4.11 Trending

Provide BACnet trending all object present values, set points, and other parameters indicated for trending on project schedules or at the request of Camp Lejeune or commissioning agents. Trends may be associated into groups, and a trend report may be set up for each group. Trends are stored within a device on the BACnet network, with operator selectable trend intervals from 10 seconds up to 24 hours. The minimum number of consecutive trend values stored at one time shall be 100 per variable.

When trend memory is full, the most recent data shall overwrite the oldest data.

The BACnet system shall allow for Change-Of-Value (COV) subscription based trending at user defined thresholds.

The B-BC shall upload trends automatically upon reaching 3/4 of the device buffer limit (via Notification_Threshold property), by operator request, or by time schedule for archiving. Archived and real-time trend data shall be available for viewing numerically and graphically for at the workstation and connected notebook computers.

Additionally, provide daily trend on geothermal well field supply and return temperatures. Allocate sufficient memory to store 24 months data.

2.1.4.12 Device Diagnostics

Each controller shall have diagnostic LEDs for power, communication, and device fault condition. The DDC system shall recognize and report a non-responsive controller.

2.1.4.13 Power Loss

Upon restoration of power, the DDC system shall perform an orderly restart and restoration of control.

2.1.5 Notebook Computer

Provide a notebook computer for each building, complete with the project's installed DDC software, applications database, final archived field controller programs and Supervisory controller database, and graphics to fully troubleshoot and program the project's devices. Provide the notebook computer with aballistic nylon carrying case with shoulder strap, or backpack,and all necessary cables and interface hardware needed for setup and direct communication with the controllers and control system components. Direct communication shall not be through the Supervisory controller.

At a minimum the notebook computer shall include: Common Access Card Reader, Windows based operating system, minimum 2.7 GHz processor base speed with 3 MB Cache, discrete switchable graphics card with minimum 1 GB dedicated memory, 1 Terabyte hard drive, 32 GB DDR3 RAM, 2 USB 3.0 ports, 10/100/1000 network interface card, 802.11 b/g/n WLAN, 17-inch display, keyboard with numeric keypad, 6-hour battery with charger, internal or external 8X DVD+/-R/RW drive with double layer support with DVD creator software, and Microsoft Office Home and Business bundled software.

Provide all original licenses, installation media, documentation, and recovery CDs capable of restoring the original configuration. Provide a means to connect the notebook computer directly to the installed field bus. Provide the manufacturer's 3-year accidental damage protection with

SECTION 23 09 23.02 Page 10

3-day on site response for 2 year warranty with the Government listed as the warranty owner.

When submitting the notebook computer, provide itemized list indicating the following information for all components submitted with the notebook computer:

a. Description

b. Quantity

c. Manufacturer

d. Part Number

e. Serial Number

2.1.6 Notebook Computer Software

2.1.6.1 Password Protection

System shall support role based access. At a minimum, OS administrator, auditor, DDC operator and user roles must be defined. The system must be capable of enforcing role based access by location (e.g., Bob may alter operating parameters for Building 1 but not Building 2. Building 2 is Alice's responsibility).

Workstation shall be capable of DoD Common Access Card (CAC) login in addition to traditional username and password.

The lowest level only allow viewing graphics. The second level allows viewing graphics and changing space temperature setpoints. The third level allows the previous level's capability, plus changing operating schedules. The fourth level allows access to all functions except passwords. The highest level provides all administrator rights and allows full access to all programming, including setting new passwords and access levels. Provide the BAS Owner with the highest level password access.

Provide automatic log out if no keyboard or mouse activity is detected after a user-defined time delay.

2.1.6.2 Notebook Computer DDC Software

Provide the workstation software with the manufacturer's installation CDs and licenses. Configure the software according to the DDC system manufacturer's specifications, cybersecurity requirements, and in agreement with BACnet Operator Workstation (B-OWS) device standards found in ASHRAE 135, Annex L. Include BACnet PICS for Operator Workstation software.

The workstation software shall permit complete monitoring, modification, archiving, programming and troubleshooting interface with the DDC system including supervisory controller and field controllers. Software shall include, but not limited to, Niagara Workplace, FX Workbench, JCI SCT, CCT/PCT, Distech EC-gfx or any controls manufacturer Supervisory controller and field controller programming software used to program the system. The operator interface with the software shall be menu-driven with appropriate displays and menu commands to manipulate the DDC system's objects, point data, operating schedules, control routines, system configuration, trends, alarms, messages, graphics, and reports. Trends

SECTION 23 09 23.02 Page 11 shall be capable of graphic display in real time, with variables plotted as functions of time. Each alarmed point shall be capable of displaying its alarm history, showing when it went into alarm, if and when it was acknowledged, and when it went out of alarm. The modification of DDC system parameters and object properties shall be accomplished with "fill in the blank" and/or "point and drag" methods. Modifications shall download to the appropriate controllers at the operator's request.

2.1.6.3 Web-Based User Interface (UI) and Graphics

Provide web-based graphics fully compatible with Internet Explorer 9+, Safari, Firefox, and Google Chrome. Web-based user interface shall be browser agnostic and shall not rely on proprietary client side scripting to function.

Graphic displays shall have full-screen resolution when viewed on the workstation and notebook computers. Dynamic data on graphics pages shall refresh within 10 seconds using an Internet connection, or 30 seconds using a dial-up modem connection. Web-based user interface shall not rely on additional third-party browser "plug-in" software like Adobe Flash.

Java client side applets may be used if appropriately signed. If Java client side runtimes are used they shall not require deprecated or otherwise unsupported Java runtime environments.

The graphics shall show the present value and object name for each of the project's I/O points on at least one graphic page. Arrange point values and names on the graphic displays in their appropriate physical locations with respect to the floor plan or equipment graphic displayed. Graphics shall allow the operator to monitor current status, view zone and equipment summaries, use point-and-click navigation between graphic pages, and edit setpoints and parameters directly from the screens. Items in alarm shall be displayed using a different color or other obvious visual indicator.

Provide graphics with the following:

a. Graphic Types: Provide at least one graphic display for each piece of HVAC equipment, building floor, and controlled zone. Indicate dynamic point values, operating statuses, alarm conditions, and control setpoints on each display. Provide summary pages where appropriate.

(1) Building Elevation: For buildings more than one story, provide an elevation view of the building with links to each of the building's floor plans. Simulate the building's architecture and include the building number and floor numbers. If possible, use an actual photograph of the building.

(2) Building Floor Plans: Provide a floor plan graphic for each of the building's floors and roof with dynamic display of space temperature and other important data. If used, indicate and provide links to sub-plan areas. If possible, use the project's electronic drawing files for the graphic backgrounds. Provide clear names for important areas, such as "Main Conference Room."

Include room names and numbers where applicable. Include features such as stairwells, elevators, and main entrances. Where applicable, include the mechanical room, HVAC equipment, and control component locations, with corresponding links to the equipment graphics.

(3) Sub-plan Areas: Where a building's floor plan is too large to

SECTION 23 09 23.02 Page 12 adequately display on the screen, sub-divide the plan into distinct areas, and provide a separate graphic display for each area. Provide same level of detail requested in building floor plan section above.

(4) HVAC Equipment: Provide a graphic display for each piece of HVAC equipment, such as a fan coil unit, VAV terminal, or air handling unit. Equipment shall be represented by a two or three-dimensional drawing. Where multiple pieces of equipment combine to form a system, such as a central chiller plant or central heating plant, provide one graphic to depict the entire plant. Indicate the equipment, piping, ductwork, dampers, and control valves in the installed location. Include labels for equipment, piping, ductwork, dampers, and control valves. Show the direction of air and water flow. Include dynamic display of applicable object data with clear names in appropriate locations.

(5) Sequence of Operation: Provide a graphic screen displaying the written out full sequence of operation for each piece of HVAC equipment. Provide a link to the sequence of operation displays on their respective equipment graphics. Include dynamic real-time data within the text for setpoints and variables.

b. Graphic Title: Provide a prominent, descriptive title on each graphic page.

c. Dynamic Update: When the workstation is on-line, all graphic I/O object values shall update with change-of-value services, or by operator selected discrete intervals.

d. Graphic Linking: Provide forward and backward linking between floor plans, sub-plans, and equipment.

e. Graphic Editing: Provide installed software to create, modify, and delete the DDC graphics. Include the ability to store graphic symbols in a symbol directory and import these symbols into the graphics.

f. Dynamic Point Editing: Provide full editing capability for deleting, adding, and modifying dynamic points on the graphics.

PART 3 EXECUTION

3.1 INSTALLATION

3.1.1 Demolition

Demolition requirements are specified in Section 23 09 00 INSTRUMENTATION

AND CONTROL FOR HVAC.

3.1.2 BACnet Naming and Addressing

Coordinate with the BAS Owner and provide unique naming and addressing consistent with existing buildings already loaded on the EMCS server. All DDC controllers shall have a Camp Lejeune unique instance number and all Supervisory Building Controllers shall have a Camp Lejeune unique name.

Names are managed by the Government.

SECTION 23 09 23.02 Page 13

3.1.2.1 MAC Address

Every BACnet device shall have an assigned and documented MAC Address unique to its network. For Ethernet networks, document the MAC Address assigned at its creation. For MS/TP networks, assign addresses from 0-127.

Do not use the controls manufacturer reserved addresses for field controllers. This is typically 0-3. Also the BACnet Instance ID for MAC Address 127, Trunk 1, is reserved for the Supervisory controller.

Supervisory Controller Global ID and instance numbers are to be obtained from the BAS Owner to ensure duplicates do not occur.

For MS/TP, assign from 01 to 127 unless reserved by the manufacturer.

Correlate address with the provided instance number range starting with the lowest number. If there are reserved addresses, do not use the instance number that correlates to those addresses.

Example: Assigned Global ID is 600. If the first trunk address is 04, the instance number will be 158348. If the first trunk address is 05, the instance number will be 158349. If the manufacturer has reserved addresses 01-03, addresses 01-03 and instance numbers 158345-158347 shall not be used.

3.1.2.2 Network Numbering

Assign unique numbers to each new network installed on the BACnet internetwork. Provide ability for changing the network number; either by device switches, network computer, or field operator interface. The BACnet internetwork (all possible connected networks) can contain up to 65,534 possible unique networks.

3.1.2.3 Device Object Identifier Property Number

Assign unique Device "Object_Identifier" property numbers or device instances for each device on the BACnet internetwork. Provide for future modification of the device instance number; either by device switches, network computer, or field interface. Instance numbers must be field assignable. BACnet allows up to 4,194,302 possible unique devices per internetwork.

3.1.2.4 Device Object Name Property Text

Each object on the Camp Lejeune EMCS has a unique point name, which is made up of the object or short name stored in the controller and the equipment identifier, which is stored in the supervisory building controller (SBC). The long point name combines this object name with the name stored in the SBC that describes the controller or location of the object. The device object name property field shall support 32 minimum printable characters. The point name follows the general convention:

Building.Equipment.Object Name

Example: HP512.AHU-3.DA-T. See Attachments one through three for equipment names, object names, object groupings, and area names.

3.1.2.5 Object Name Property Text (Other than Device Objects)

The object name identifies the specific point. Only object names on the approved Camp Lejeune list shall be used. From the example above, the point name is: "DA-T". See Attachment for the approved Camp Lejeune list.

SECTION 23 09 23.02 Page 14

If object name is not in the approved list, then contractor shall send a Request For Information (RFI) to their COTR. The object name property field shall support 32 minimum printable characters.

3.1.2.6 Object Description

The controller shall also store an alpha numeric description of the object name. The controller shall support a minimum of 30 printable characters.

From the example above the object description is: "Discharge Air Temperature". Both short names and long names shall be populated in the database.

3.1.2.7 List of Attachments

Attachment 1 - Not Used

Attachment 2 - Object Names

Attachment 3 - NOT USED

Attachment 4 - Niagara BAS Alarms Policy

Attachment 5 - Trend (History)

3.1.3 Minimum BACnet Object Requirements

a. Use of Standard BACnet Objects in accordance with existing Camp Lejeune Standards: For the following points and parameters, use standard BACnet objects, where all relevant object properties can be read using BACnet's Read Property Service, and all relevant object properties can be modified using BACnet's Write Property Service:

(1) All device physical inputs

(2) All device physical outputs

(3) All set points

(4) All PID tuning parameters

(5) All calculated pressures, flow rates, and consumption values

(6) All alarms

(7) All trends

(8) All schedules

(9) All equipment and lighting circuit operating status

b. BACnet Object Description Property: The Object Description property shall support 32 minimum printable characters. For each object, complete the description property field using a brief, narrative, plain English description specific to the object and project application. For example: "HW Pump 1 Proof." Document compliance, length restrictions, and whether the description is writeable in the device PICS.

c. Analog Input, Output, and Value Objects: Support and provide

SECTION 23 09 23.02 Page 15

Description and Device_Type text strings matching signal type and engineering units shown on the points list.

d. Binary Input, Output, and Value Objects: Support and provide Inactive_Text and Active_Text property descriptions matching conditions shown on the points list.

e. Calendar Object: For devices with scheduling capability, provide at least one Calendar Object with ten-entry capacity that incorporates Federal Holidays. All operators may view Calendar Objects; authorized operators may make modifications from a workstation. Enable the writeable Date List property and support all calendar entry data types.

f. Schedule Object: Use Schedule Objects for all building system scheduling. All operators may view schedule entries; authorized operators may modify schedules from a workstation.

g. Loop Object or Equal: Use Loop Objects or equivalent BACnet objects in each applicable field device for PID control. Regardless of program method or object used, allow authorized operators to adjust the Update Interval, Setpoint, Proportional Constant, Integral Constant, and Derivative Constant using BACnet read/write services.

h. Setpoints: All setpoints must be BACnet exposed for auto discovery purposes if needed.

3.1.4 Minimum BACnet Service Requirements

a. Command Priorities

(1) Use commandable BACnet objects to control machinery and systems, providing the priority levels listed below. If the sequence of operation requires a different priority, obtain approval from the Contracting Officer.

Priority Level Application

1 Manual-Life Safety

2 Automatic-Life Safety

3 (User Defined)

4 (User Defined)

5 Critical Equipment Control

6 Minimum On/Off

7 (User Defined)

8 Manual Operator

9 (User Defined)

10 (User Defined)

11 Load Shedding

SECTION 23 09 23.02 Page 16

Priority Level Application

12 (User Defined)

13 (User Defined)

14 (User Defined)

15 (User Defined)

16 (User Defined)

b. Alarming

(1) Alarm Priorities: Coordinate alarm and event notification with the BAS Owner.

(2) Notification Class: Enable writeable Priority, Ack Required, and Recipient List properties of Notification Class objects.

(3) Event Notification Message Texts: Use condition specific narrative text and numerical references for alarm and event notification.

c. Updating Displayed Property Values

(1) Allow workstations to display property values at discrete polled intervals, or based on receipt of confirmed and unconfirmed Change of Value notifications. The COV increment shall be adjustable by an operator using BACnet services, and polled intervals shall be adjustable at the operator workstation.

3.1.5 Local Area Networks

Connection of new networks with existing networks will be done by the BAS Owner. Network numbers and device instance numbers shall remain unique when joining networks. Do not change existing network addressing without Government approval. See also "BACnet Naming and Addressing".

3.1.6 BACnet Routers and Protocol Gateways

Provide the quantity of BACnet routers necessary for communications shown on the BACnet Communication Architecture schematic. Provide BACnet routers with BACnet Broadcast Message Device (BBMD) capability on each BACnet internetwork communicating across an IP network. Configure BBMD tables to enable unicast forwarding of broadcast messaging across Layer-3 IP subnets.

3.1.7 Plant Controllers

Equipment such as VFD's, chillers, and boilers shall have hardwired enable(start/stop), and status points from the plant controller, VFD's shall also have a hardwired speed command. Additionally, this equipment shall have a BACnet interface for monitoring.

3.1.8 Digital Controllers

a. Install as stand alone control devices (see definitions in Section

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC).

SECTION 23 09 23.02 Page 17

b. Locate control cabinets at the locations shown on the drawings. If not shown on the drawings, install in the most accessible space, close to the controlled equipment.

c. Controllers must be installed in a manfacturer's required/recommended enclosure for each type of controller.

d. Provide a dedicated analog output to each output device, such as variable frequency driven pump motors in an alternating arrangement.

e. Equipment such as VFD's must have hardwired enable (start/stop), speed command and status points from the controller. Software points are not allowable. Additionally, this equipment shall have a BACnet interface for monitoring.

3.1.9 Wiring Criteria

Wiring criteria requirements are specified in Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

3.1.10 Accessibility

Accessibility requirements are specified in Section 23 09 00

INSTRUMENTATION AND CONTROL FOR HVAC.

3.1.11 Component Identification Labeling

Component identification labeling requirements are specified in Section

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC.

-- End of Section --

SECTION 23 09 23.02 Page 18