Spec 230900 Instrumentation and Control for HVAC EMCS.pdf

FAIRCHILD AIR FORCE BASE DESIGN GUIDE 21 Sep 2022

DIVISION 23 – HEATING, VENTILATING, AND AIR-CONDITIONING (HVAC) FAIRCHILD GUIDE SPECIFICATION

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 1 OF 31

DIVISION 23 – HEATING, VENTILATING, AND AIR CONDITIONING

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC

ENERGY MANAGEMENT AND CONTROL SYSTEM (EMCS)

FAIRCHILD GUIDE SPECIFICATION

Note: NOTE: Incorporate in whole the information in this guide specification, developed by the 92d Civil Engineer Squadron Engineering Flight, to develop UFGS specifications for this section.

Brackets are used in the text to indicate designer choices or locations where text must be supplied by the designer.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC

PART 1 GENERAL

1.01 WORK INCLUDED

A. Furnish a totally native BACnet-based system based on a distributed control system in accordance with this specification. The operator’s workstation, all building controllers, application controllers, and all input/output devices shall communicate using the protocols and network standards as defined by the latest version of ANSI/ASHRAE Standard 135, BACnet. In other words, all workstations and controllers, including unitary controllers, shall be native BACnet devices. No gateways shall be used for communication to controllers installed under this section. Gateways may be used for communication to existing systems or to systems installed under other sections.

B. Provide all necessary BACnet-compliant hardware and software to meet the system’s functional specifications

C. Prepare individual hardware layouts, interconnection drawings, and software configuration from project design data.

D. Implement the detailed design for all analog and binary objects, system databases, graphic displays, logs, and management reports based on control descriptions, logic drawings, configuration data, and bid documents.

E. Design, provide, and install all equipment cabinets, panels, data communication network cables needed, and all associated hardware.

F. Provide and install all interconnecting cables between supplied cabinets, application controllers, and input/output devices.

G. Provide complete manufacturer’s specifications for all items that are supplied. Include vendor name of every item supplied.

H. Provide supervisory specialists and technicians at the job site to assist in all phases of system installation, startup, and commissioning.

I. Provide a comprehensive operator and technician training program as described herein.

J. Provide as-built documentation, operator’s terminal software, diagrams, and all other associated project operational documentation (such as technical manuals) on approved media, the sum total of which accurately represents the final system.

K. Provide new sensors, dampers, valves, and install only new electronic actuators. No used components shall be used as any part or piece of installed system. [This paragraph can be revised to re-use existing Sensors/Valves/Actuators in this paragraph. You may want to specify where to look on the attached point list for the description of new or re-used devices.]

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 2 OF 31

1.02 SYSTEM DESCRIPTION

A. Distributed logic control system complete with all software and hardware functions shall be provided and installed. System shall be completely based on the latest version of ANSI/ASHRAE Standard 135, BACnet. This system is to control all mechanical equipment, including all unitary equipment such as VAV boxes, heat pumps, fan-coils, AC units, etc. and all air handlers, boilers, chillers, and any other listed equipment using native BACnet-compliant components. Non-BACnet-compliant or proprietary equipment or systems (including gateways) shall not be acceptable and are specifically prohibited. [Add irrigation, lighting control, any other monitoring in this paragraph if desired in project to make sure it is included in project bids and delivered by contractors. Also make sure that provision and installation of these additional control products are coordinated in the other mechanical and electrical sections.]

B. Operator’s workstation software shall use the latest applicable version of Windows as the computer operating system. The Energy Management and Control System (EMCS) application program shall be written to communicate specifically utilizing BACnet protocols.

Software functions delivered on this project shall include password protection, scheduling (including optimum start), alarming, logging of historical data, full graphics including animation, after-hours billing program, demand limiting, full suite of field engineering tools including graphical programming and applications. Systems using operating systems other than that described above are strictly prohibited. All software required to program application specific controllers and all field level devices and controllers will be left with the Government.

All software passwords required to program and make future changes to the system will also become the property of the Government. All software required to make any program changes anywhere in the system along with scheduling, and trending applications will be left with the Government. All software passwords required to program and make future changes to schedules, trends and related program changes will also become the property of the Government. All software required for all field engineering tools including graphical programming and applications will be left with the Government. All software passwords required to program and make future changes to field engineering tools including graphical programming and applications will be left with the Government.

C. Building controllers shall include complete energy management software, including scheduling building control strategies with optimum start and logging routines. All energy management software and firmware shall be resident in field hardware and shall not be dependent on the operator’s terminal. Operator’s terminal software is to be used for access to field-based energy management functions only. Provide zone-by-zone direct digital logic control of space temperature, scheduling, runtime accumulation, equipment alarm reporting, and override timers for after-hours usage. All application controllers for every terminal unit (VAV, HP, UV, etc.) air handler, all central plant equipment, and any other piece of controlled equipment shall be fully programmable. Application controllers shall be mounted next to controlled equipment and communicate with building controller via BACnet LAN.

D. Room sensors with digital readouts preferred in occupied areas. Room sensors shall be provided with digital readouts that allow the user to view room temperature, view outside air temperature, adjust the room set point within preset limits and set desired override time.

Initial set point shall be pre-determined by FAFB. Provide enable/disable check box on screen with field adjustment initially disabled. Include all necessary wiring and firmware such that room sensor includes field service mode. Field service mode shall allow technician to balance VAV zones and access any parameter in zone controller without additional laptop or handheld computer. [If digital readout is not desired replace with the following: Room sensors shall be architecturally pleasing, sense temperature, allow tenant to override system and adjust temperature set point.]

1.03 APPROVED MANUFACTURERS

A. The base bid shall be the BACtalk system from Alerton. No substitutions will be allowed.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 3 OF 31

1.04 QUALITY ASSURANCE

A. [The bidder shall be regularly engaged in the design, installation and maintenance of BAS systems and shall have demonstrated technical expertise and experience in the design, installation and maintenance of BAS systems similar in size and complexity to this project. Bidders shall provide a list of at least 3 projects, similar in size and scope to this project completed within the past 3 years.]

B. The BAS system shall be designed and installed, commissioned and serviced by factory trained personnel. Manufacturer shall have an in-place support facility within 2 hours response time of the site with technical staff, spare parts inventory and necessary test and diagnostic equipment. The control contractor shall provide an experienced project manager for this work, responsible for direct supervision of the design, installation, start up and commissioning of the BAS system. All control drawings, submittal package, graphics, and programming shall be accomplished by local technicians and project managers, so that all changes will be accurately reflected, and that any modifications may be made expeditiously in the field.

C. Materials and equipment shall be the catalogued products of manufacturers regularly engaged in production and installation of automatic temperature control systems and shall be manufacturer's latest standard design that complies with the specification requirements.

D. All BAS peer-to-peer network controllers, central system controllers and local user displays shall be UL Listed under Standard UL 916, category PAZX. All electronic equipment shall conform to the requirements of FCC Regulation, Part 15, Governing Radio Frequency Electromagnetic Interference and be so labeled.

E. Control system shall be engineered, programmed and supported completely by the representative’s local office that must be within 100 miles of project site.

1.05 REFERENCE STANDARDS

A. The latest edition of the following standards and codes in effect and amended as of supplier's proposal date, and any applicable subsections thereof, shall govern design and selection of equipment and material supplied:

1. American Society of Heating, Refrigerating and Air Conditioning Engineers (ASHRAE).

2. ANSI/ASHRAE Standard 135-2001, BACnet.

3. Uniform Building Code (UBC), including local amendments.

4. UL 916 Underwriters Laboratories Standard for Energy Management Equipment. Canada and the US.

5. National Electrical Code (NEC).

6. FCC Part 15, Subpart J, Class A

7. EMC Directive 89/336/EEC (European CE Mark)

8. UL-864 UUKL listing for Smoke Controls for any equipment used in smoke control sequences

B. City, county, state, and federal regulations and codes in effect as of contract date.

C. Except as otherwise indicated the system supplier shall secure and pay for all permits, inspections, and certifications required for his work and arrange for necessary approvals by the governing authorities.

1.06 SUBMITTALS

A. Drawings

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 4 OF 31

1. The system supplier shall submit engineered drawings, control sequence, and bill of materials for approval.

2. Drawings shall be submitted in the following standard sizes: 11” x 17” (ANSI B).

3. Three complete sets (copies) of submittal drawings shall be provided.

4. All drawings shall be provided on a CD-ROM in an editable format of Visio or AutoCAD.

B. System Documentation

1. Include the following in submittal package:

a. System configuration diagrams in simplified block format.

b. All input/output object listings and an alarm point summary listing.

c. Electrical drawings that show all system internal and external connection points, terminal block layouts, and terminal identification.

d. Complete bill of materials, valve schedule and damper schedule.

e. Manufacturer's instructions and drawings for installation, maintenance, and operation of all purchased items.

f. Overall system operation and maintenance instructions—including preventive maintenance and troubleshooting instructions.

g. For all system elements—operator’s workstation(s), building controller(s), application controllers, routers, and repeaters,—provide BACnet Protocol Implementation Conformance Statements (PICS) as per ANSI/ASHRAE Standard 135-2001.

h. Provide complete description and documentation of any proprietary (non-BACnet) services and/or objects used in the system.

i. A list of all functions available and a sample of function block programming that shall be part of delivered system.

C. Project Management

1. The vendor shall provide a detailed project design and installation schedule with time markings and details for hardware items and software development phases. Schedule shall show all the target dates for transmission of project information and documents and shall indicate timing and dates for system installation, debugging, and commissioning.

D. BACnet Device Object Naming Conventions [Optional]

1. The BAS manufacturer’s representative shall submit a BACnet Device Object Naming Convention Plan (DONCP) to the Government and consulting engineer during the submittal process. The plan must be approved by the Government and consulting engineer prior to implementation. It is the responsibility of the BAS contractor to coordinate the DONCP with the Government and consulting engineer.

2. The DONCP shall be designed to eliminate any confusion between individual points in a facility/campus wide EMCS system. It will also be designed to allow for future expansion and consistency. Each device on a BACnet internetwork (including other manufacturer’s devices) must have a unique device instance. This is a major consideration when adding to an existing system or interconnecting networks. Thorough and accessible site documentation is critical.

3. A consistent object (point) naming convention shall be used to facilitate familiarity and operational ease across an eventual large campus or inventory of facilities. The following section is designed as recommendations only. It is the responsibility of the BAS contractor to coordinate the DONCP with the Government and consulting engineer.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 5 OF 31

4. BACnet requires that all devices have a Device object name that is unique throughout the entire internetwork. To comply with this requirement all BACnet devices shall be configured with a Device Object Name that is based on the naming conventions described in this section. This includes all physical devices as well as any logical BACnet devices that are represented by gateways. The vendor shall coordinate with the Government staff to ensure that the correct names are used. Device Object Name properties shall support strings of at least 50 characters in length.

1.07 WARRANTY

A. Warranty shall cover all costs for parts, labor, associated travel, and expenses for a period of one year from completion of system acceptance.

B. Hardware and software personnel supporting this warranty agreement shall provide on-site or off-site service in a timely manner after failure notification to the vendor. The maximum acceptable response time to provide this service at the site shall be 24 hours Monday through Friday, 48 hours on Saturday and Sunday.

C. This warranty shall apply equally to both hardware and software.

1.08 RELATED WORK IN OTHER SECTIONS [Use this section to spell out those other areas of the specification that the control system contractor needs to review. This should include all contractual items and all areas that will interface with the control systems like lighting, irrigation, chillers, fire alarm, etc.]

A. Refer to Division 0 and Division 1 for related contractual requirements.

B. Refer to Section 230000 for General Mechanical Provisions.

C. Refer to Section 260000 for General Electrical Provisions.

PART 2 PRODUCTS

2.01 OPERATOR’S WORKSTATION

A. General structure of workstation interaction shall be a standard client/server relationship.

Server shall be used to archive data and store system database. Clients shall access server for all archived data. Each client shall include flexibility to access graphics from server or local drive. Server shall support a minimum of 50 clients simultaneously. (Server and operator’s workstation is existing.)

B. BACnet Conformance

1. Operator’s workstation shall as a minimum support Point-to-Point (PTP) and Ethernet BACnet LAN types. It shall communicate directly via these BACnet LANs as a native BACnet device. Operator’s terminal shall comply with the requirements of a BACnet conformance class 3 device and support all BACnet services necessary to provide the following BACnet functional groups:

a. Clock Functional Group

b. Event Response Functional Group

c. Time Master Functional Group

d. Device Communications

2. Please refer to section 22.2, BACnet Functional Groups, in the BACnet standard for a complete list of the services that must be directly supported to provide each of the functional groups listed above. All proprietary services, if used in the system, shall be thoroughly documented and provided as part of the submittal data. All necessary tools shall be supplied for working with proprietary information.

3. Standard BACnet object types accessed by the workstation shall include as a minimum:

Analog Value, Analog Input, Analog Output, Binary Value, Binary Input, Binary Output, SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 6 OF 31

Calendar, Device, Event Enrollment, File, Notification Class, Program and Schedule object types. All proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. All necessary tools shall be supplied for working with proprietary information.

4. The Operator Workstation shall comply with Annex J of the BACnet specification for IP connections. This device shall use Ethernet to connect to the IP internetwork, while using the same Ethernet LAN for non-IP communications to other BACnet devices on the LAN. Must support interoperability on wide area networks (WANs), metropolitan area networks (MANs), and campus area networks (CANs). Workstation shall support Foreign Device Registration to allow temporary workstation connection to IP network.

C. Displays

1. Operator’s workstation shall display all data associated with project as called out on drawings and/or object type list supplied. Graphic files shall be created using digital, full color photographs of system installation, AutoCAD or Visio drawing files of field installation drawings and wiring diagrams from as-built drawings. Operator’s workstation shall display all data using three-dimensional graphic representations of all mechanical equipment. System shall be capable of displaying graphic file, text, and dynamic object data together on each display and shall include animation. Information shall be labeled with descriptors and shall be shown with the appropriate engineering units. All information on any display shall be dynamically updated without any action by the user.

Workstation shall allow user to change all field-resident EMCS functions associated with the project, such as set points, weekly schedules, exception schedules, etc. from any screen no matter if that screen shows all text or a complete graphic display. This shall be done without any reference to object addresses or other numeric/mnemonic indications.

2. All displays and programming shall be generated and customized by the local EMCS supplier and installer. Systems requiring factory development of graphics or programming of DDC logic are specifically prohibited.

3. Binary objects shall be displayed as “ACTIVE/INACTIVE/NULL”. Text shall be justified left, right or center as selected by the user. Also, allow binary objects to be displayed as individual change-of-state graphic objects on the display screen such that they overlay the system graphic. Each binary object displayed in this manner shall be assigned up to three graphic files for display when the point is ON, OFF or in alarm. For binary outputs, toggle the object’s commanded status when the graphic item is selected with the system mouse. Similarly, allow the workstation operator to toggle the binary object’s status by selecting with the mouse a graphic of a switch or light, for example, which then displays a different graphic (such as an “ON” switch or lighted lamp). Additionally, allow binary objects to be displayed as an animated graphic. Animated graphic objects shall be displayed as a sequence of multiple graphics to simulate motion. For example: when a pump is in the OFF condition, display a stationary graphic of the pump. When the operator selects the pump graphic with the mouse, the represented object’s status is toggled and the graphic of the pump’s impeller rotates in a time-based animation. The operator shall be able to click on an animated graphical object or switch it from the OFF position to ON, or ON to OFF. Allow operator to change graphic file assignment and also create new and original graphics online. System shall be supplied with a library of standard graphics, which may be used unaltered or modified by the operator. Systems that do not allow customization or creation of new graphic objects by the operator (or with third-party software) shall not be allowed.

4. Analog objects shall be displayed with operator modifiable units. Analog input objects may also be displayed as individual graphic items on the display screen as an overlay to the system graphic. Each analog input object may be assigned a minimum of five graphic files, each with high/low limits for automatic selection and display of these graphics. As an example, a graphic representation of a thermometer would rise and fall in response to either the room temperature or its deviation from the controlling set point.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 7 OF 31

Analog output objects, when selected with the mouse, shall be displayed as a prompted dialog (text only) box. Selection for display type shall be individual for each object.

Analog object values may be changed by selecting either the “increase” or “decrease” arrow in the analog object spinner box without using the keypad. Pressing the button on the right side of the analog object spinner box allows direct entry of an analog value and accesses various menus where the analog value may be used, such as trend logs.

5. Analog objects may also be assigned to an area of a system graphic, where the color of the defined area changes based on the analog object’s value. For example, an area of a floor-plan graphic served by a single control zone would change color with respect to the temperature of the zone or its deviation from set point. All editing and area assignment shall be created or modified online using simple icon tools.

6. A customized menu label (push-button) shall be used for display selection. Menu items on a display shall allow penetration to lower level displays or additional menus. Dynamic point information and menu label push buttons may be mixed on the same display to allow sub-displays to exist for each item. Each display may be protected from viewing unless operator has appropriate security level. A security level may be assigned to each display and system object. The menu label shall not appear on the graphic if the operator does not have the appropriate security level.

7. A mouse shall be used to move the pointer arrow to the desired item for selection of new display or to allow the operator to make changes to object data.

D. Password Protection

1. Provide security system that prevents unauthorized use unless operator is logged on.

Access shall be limited to operator’s assigned functions when user is logged on. This includes displays as outlined above.

2. Each operator’s terminal shall provide security for 200 users minimum. Each user shall have an individual User ID, User Name and Password. Entries are alphanumeric characters only and are case sensitive (except for User ID). User ID shall be 0–8 characters, User Name shall be 0–29 characters, and Password shall be 4–8 characters long. Each system user shall be allowed individual assignment of only those control functions and menu items to which that user requires access. All passwords, user names, and access assignments shall be adjustable online at the operator’s terminal.

Each user shall also have a set security level, which defines access to displays and individual objects the user may control. System shall include 10 separate and distinct security levels for assignment to users.

3. System shall include an Auto Logout Feature that shall automatically logout user when there has been no keyboard or mouse activity for a set period of time. Time period shall be adjustable by system administrator. Auto Logout may be enabled and disabled by system administrator. Operator terminal shall display message on screen that user is logged out after Auto Logout occurs.

E. Operator Activity Log

1. Operator Activity Log shall be included with system that tracks all operator changes and activities. System shall track what is changed in the system, who performed this change, date and time of system activity and value of the change before and after operator activity. Operator shall be able to display all activity, sort the changes by user and also by operation.

2. Log shall be gathered and archived to hard drive on operator workstation as needed.

Operator shall be able to export data for display and sorting in a spreadsheet.

3. Any displayed data, that is changeable by the operator, may be selected using the right mouse button and the operator activity log shall then be selectable on the screen.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 8 OF 31

Selection of the operator activity log using this method shall show all operator changes of just that displayed data.

F. Scheduling

1. Operator’s workstation shall show all information in easy-to-read daily format including calendar of this month and next. All schedules shall show actual ON/OFF times for day based on scheduling priority. Priority for scheduling shall be events, holidays and daily with events being the highest.

2. Holiday and special event schedules shall display data in calendar format. Operator shall be able to schedule holidays and special events directly from these calendars.

3. Operator shall be able to change all information for a given weekly or exception schedule if logged on with the appropriate security access.

4. System shall include a Schedule Wizard for set up of schedules. Wizard shall walk user through all steps necessary for schedule generation. Wizard shall have its own pull-down selection for startup or may be started by right clicking on value displayed on graphic and then selecting Schedule.

5. Scheduling shall include optimum start based on outside air temperature, current heating/cooling set points, indoor temperature and history of previous starts. Each and every individual zone shall have optimum start time independently calculated based on all parameters listed. User shall input schedules to set time that occupied set point is to be attained. Optimum start feature shall calculate the startup time needed to match zone temperature to set point. User shall be able to set a limit for the maximum startup time allowed.

G. Alarm Indication and Handling

1. Operator’s workstation shall provide audible, visual, and printed means of alarm indication. The alarm dialog box shall always become the top dialog box regardless of the application(s), currently running. Printout of alarms shall be sent to the assigned terminal and port.

2. System shall provide log of alarm messages. Alarm log shall be archived to the hard disk of the system operator’s terminal. Each entry shall include a description of the event-initiating object generating the alarm. Description shall be an alarm message of at least 256 characters in length. Entry shall include time and date of alarm occurrence, time and date of object state return to normal, time and date of alarm acknowledgment and identification of operator acknowledging alarm .

3. Alarm messages shall be in user-definable text (English or other specified language) and shall be entered either at the operator’s terminal or via remote communication.

4. System shall include an Alarm Wizard for set up of alarms. Wizard shall walk user through all steps necessary for alarm generation. Wizard shall have its own pull-down selection for startup or may be started by right clicking on value displayed on graphic and then selecting alarm setup.

5. System shall include the provision to e-mail and dial out alarms to pagers, cell phones, or workstations, as desired.

H. Trend log Information

1. System server shall periodically gather historically recorded data stored in the building controllers and archive the information. Archived files shall be appended with new sample data, allowing samples to be accumulated. Systems that write over archived data shall not be allowed, unless limited file size is specified. Samples may be viewed at the operator’s workstation. Operator shall be able to scroll through all trended data. All trend log information shall be displayed in standard engineering units.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 9 OF 31

2. Software shall be included that is capable of graphing the trend logged object data.

Software shall be capable of creating two-axis (x,y) graphs that display up to ten object types at the same time in different colors. Graphs shall show object values relative to time.

3. Operator shall be able to change trend log setup information. This includes the information to be logged as well as the interval at which it is to be logged. All input, output, and value object types in the system may be logged. All operations shall be password protected. Setup and viewing may be accessed directly from any and all graphics on which object is displayed.

4. System shall include a trend Wizard for setup of logs. Wizard shall walk user through all necessary steps. Wizard shall have its own pull-down selection for startup, or may be started by right clicking on value displayed on graphic, and then selecting Trend logs from the displayed menu.

5. Trend logs shall record based upon time interval or change of value, as desired.

I. Energy Log Information

1. System server shall be capable of periodically gathering energy log data stored in the field equipment and archive the information. Archive files shall be appended with new data, allowing data to be accumulated. Systems that write over archived data shall not be allowed unless limited file size is specified. Display all energy log information in standard engineering units.

2. All data shall be stored in data base file format for direct use by third-party programs.

Operation of system shall stay completely online during all graphing operations.

3. Operator shall be able to change the energy log setup information as well. This includes the meters to be logged, meter pulse value, and the type of energy units to be logged. All meters monitored by the system may be logged. System shall support using flow and temperature sensors for BTU monitoring.

4. System shall display archived data in tabular format form for both consumption and peak values. Data shall be shown in hourly, daily, weekly, monthly and yearly formats. In each format the user shall be able to select a specific period of data to view.

J. Demand Limiting

1. System shall include demand limiting program that includes two types of load shedding.

One type of load shedding shall shed/restore equipment in binary fashion based on energy usage when compared to shed and restore settings. The other type of shedding shall adjust operator selected control set points in an analog fashion based on energy usage when compared to shed and restore settings. Shedding may be implemented independently on each and every zone or piece of equipment connected to system.

2. Binary shedding shall include minimum of 5 priority levels of equipment shedding. All loads in a given priority level shall be shed before any loads in a higher priority level are shed. Load shedding within a given priority level shall include two methods. In one the loads shall be shed/restored in a “first off-first on” mode and in the other the loads are just shed/restored in a linear fashion.

3. Analog shed program shall generate a ramp that is independently used by each individual zone or individual control algorithm to raise the appropriate cooling setting and lower appropriate heating setting to reduce energy usage.

4. Status of each and every load shed program shall be capable of being displayed on every operator terminal connected to system. Status of each load assigned to an individual shed program shall be displayed along with English description of each load.

K. Tenant Activity

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 10 OF 31

1. System shall include program that monitors after-hours overrides by tenants, logs that data and generates a bill based on usage and rate charged for each tenant space.

Tenant Activity program shall be able to assign multiple zones, from a list of every zone connected to system, to a particular tenant. Every zone is monitored for after-hour override usage and that data logged in server. Operator may then generate a bill based on the usage for each tenant and the rate charged for any overtime use.

2. Configuration shall include entry of the following information for use in logging and billing.

a. Tenants contact name and address

b. One or multiple tenant zones that make up a total tenant space including a separate billing rate for each separate zone.

c. Minimum and maximum values an event duration and event limit

d. Property management information

e. Overall billing rate

f. Seasonal adjustments or surcharge to billing rate

g. Billing notification type such including, but not limited to printer, file and email

h. Billing form template

3. Logging shall include recording the following information for each and every tenant event.

a. Zone description

b. Time the event begins

c. Total override time

d. Limits shall be applied to override time

4. A tenant bill shall be generated for a specific period using all the entered configuration data and the logged data. User with appropriate security level shall be able to view and override billing information. User shall be able to select a billing period to look to view and be able to delete events from billing and be able to edit a selected tenant activity event’s override time.

L. Configuration/Setup

1. Provide means for operator to display and change system configuration. This shall include, but not be limited to, system time, day of the week, date of daylight savings set forward/set back, printer termination, port addresses, modem port and speed, etc. Items shall be modified using understandable terminology with simple mouse/cursor key movements.

M. Field Engineering Tools

1. Operator’s workstation software shall include field-engineering tools for programming all controllers supplied. All controllers shall be programmed using graphical tools that allow the user to connect function blocks on screen that provide sequencing of all control logic.

Function blocks shall be represented by graphical displays that are easily identified and distinct from other types of blocks. Graphical programming that uses simple rectangles and squares is not acceptable.

2. User shall be able to pick graphical function block from menu and place on screen.

Provide zoom in and zoom out capabilities. Function blocks shall be downloaded to controller without any reentry of data.

3. Programming tools shall include a real time operation mode. Function blocks shall display real time data and be animated to show status of data inputs and outputs when in

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 11 OF 31

real time operation. Animation shall show change of status on logic devices and countdown of timer devices in graphical format.

4. Field engineering tools shall also include a database manager of applications that include logic files for controllers and associated graphics. Operator shall be able to select unit type, input/output configuration and other items that define unit to be controlled. Supply minimum of 250 applications as part of workstation software.

5. Field engineering tool shall include Device Manager for automatic detection of devices connected anywhere on the BACnet network by scanning of the entire network. This function shall display device instance, network identification, model number and description of connected devices. It shall record and display software file loaded into each controller. A copy of each file shall be stored on the computer’s hard drive. If needed, this file shall be downloaded to the appropriate controller by selection using the mouse.

6. System shall include backup/restore function that will back up entire system to selected medium and then restore system from that media.

N. Software

1. At the conclusion of project, contractor shall leave with Government a CD ROM/DVD that includes the complete system installation and project graphics, set points, system parameters, etc. This backup shall allow the Government to completely restore the installed system in the case of a computer malfunction.

2.02 BUILDING CONTROLLER

A. General Requirements

1. Building Controller shall be approved by the BTL as meeting the BACnet Building Controller requirements.

2. Building controller shall be of scalable design such that the number of trunks and protocols may be selected to fit the specific requirements of a given project.

3. The controller shall be capable of panel-mounted on DIN rail and/or mounting screws.

4. The controller shall be capable of providing global control strategies for the system based on information from any objects in the system, regardless if the object is directly monitored by the building controller module or by another controller.

5. The controller shall be capable of running up to six (6) independent control strategies simultaneously. The modification of one control strategy does not interrupt the function or runtime others.

6. The software program implementing the DDC strategies shall be completely flexible and user-definable. All software tools necessary for programming shall be provided as part of project software. Any systems utilizing factory pre-programmed global strategies that cannot be modified by field personnel on-site, using a wide area network (WAN) or downloaded through remote communications are not acceptable. Changing global strategies using firmware changes is also unacceptable.

7. Programming shall be object-oriented using control function blocks and support DDC functions. All flowcharts shall be generated and automatically downloaded to controller.

Programming tool shall be supplied and be resident on workstation. The same tool shall be used for all controllers.

8. The programming tool shall provide means to graphically view inputs and outputs to each program block in real-time as program is executing. This function may be performed using the operator’s workstation or field computer.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 12 OF 31

9. Controller shall have 6,000 Analog Values and 6,000 Binary Values.

10. Controller IP configuration can be done via a direct USB connect with an operator’s workstation or field computer.

11. Controller shall have at a minimum a Quad Core 996Ghz processor to ensure fast processing speeds.

12. Global control algorithms and automated control functions shall execute using a 64-bit processor.

13. Controller shall have a minimum of 1 GB of DDR3 SDRAM on a 533 MHz bus to ensure high speed data recording, large data storage capacity and reliability.

14. Controller shall support two (2) on-board EIA-485 ports capable of supporting various EIA-485 protocols including, but not limited to BACnet MS/TP and Modbus.

Ports are capable of supporting various EIA-485 protocols including, but not limited to BACnet MS/TP and Modbus.

15. Controller shall support two (2) ports—each of gigabit speed—Ethernet (10/100/1000) ports.

Ports are capable of supporting various Ethernet protocols including, but not limited to BACnet IP, FOX, and Modbus.

16. All ports shall be capable of having protocol(s) assigned to utilize the port’s physical connection.

17. The controller shall have at a minimum four (4) onboard inputs, two (2) universal inputs and two (2) binary inputs.

18. Schedules

Building controller modules shall provide normal seven-day scheduling, holiday scheduling and event scheduling.

Each building controller shall support a minimum of 380 BACnet Schedule Objects and 380 BACnet Calendar Objects.

19. Logging Capabilities

Each building controller shall log as minimum 2,000 objects at 15-minute intervals. Any object in the system (real or calculated) may be logged. Sample time interval shall be adjustable at the operator’s workstation.

Logs may be viewed either on-site or off-site using WAN or remote communication.

Building controller shall periodically upload trended data to networked operator’s workstation for long-term archiving if desired.

Archived data stored in database format shall be available for use in third-party spreadsheet or database programs.

20. Alarm Generation

Alarms may be generated within the system for any object change of value or state (either real or calculated). This includes things such as analog object value changes, binary object state changes, and various controller communication failures.

Each alarm may be dialed out as noted elsewhere.

Alarm log shall be provided for alarm viewing. Log may be viewed on-site at the operator’s terminal or off-site using remote communications.

Controller must be able to handle up to 2,000 alarm setups stored as BACnet event enrollment objects, with system destination and actions individually configurable.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 13 OF 31

21. Demand Limiting

Demand limiting of energy shall be a built-in, user-configurable function. Each controller module shall support shedding of up to 1,200 loads using a minimum of two types of shed programs.

Load shedding programs in building controller modules shall operate as defined in section 2.1.J of this specification.

22. Tenant Activity Logging

Tenant Activity logging shall be supported by a building controller module. Each independent module shall support a minimum of 380 zones.

Tenant Activity logging shall function as defined in section 2.1.K of this specification.

B. BACnet MS/TP

BACnet MS/TP LAN must be software-configurable from 9.6 to 115.4Kbps

Each BACnet MS/TP LAN shall support 64 BACnet devices at a minimum.

All proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. All necessary tools shall be supplied for working with proprietary information.

C. BACnet IP

The building controller shall comply with Annex J of the BACnet specification for IP connections. This device shall use Ethernet to connect to the IP internetwork, while using the same Ethernet LAN for non-IP communications to other BACnet devices on the local area network (LAN).

Must support interoperability on WANs and campus area networks (CANs), and function as a BACnet Broadcast Management Device (BBMD).

Each controller shall support at a minimum 128 BBMD entries.

BBMD management architecture shall support 3,000 subnets at a minimum.

Shall support BACnet Network Address Translation.

All proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. All necessary tools shall be supplied for working with proprietary information.

D. Expansion Ports

1. Controller shall support two (2) expansion ports.

Combining the two on-board EIA-458 ports with fully loaded expansion ports, the controller shall support six (6) EIA-485 trunks simultaneously.

2. Expansion cards that mate to the expansion ports shall include:

Dual port EIA-485 card.

LON network card.

E. Niagara Framework

1. Controller shall utilize the Tridium Niagara Framework.

Niagara Framework shall be version 3.8 or newer.

All Niagara licensing shall be stored on a removable MicroSD card for fast in-field replacement of controller.

2. The Niagara License for the controllers shall be an open license.

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 14 OF 31

The controller shall be programmable via Niagara Workplace programming tool.

The controller shall be programmable via a Niagara embedded Workplace programming tool.

F. Power Supply

1. Input for power shall accept between 17 and 30VAC, 47 and 63Hz.

2. Optional rechargeable battery for shutdown of controller including storage of all data in flash memory.

3. On-board capacitor will ensure continuous operation of real-time clocks for minimum of 14 days.

G. Controller shall be in compliance with the following:

1. UL 916 for open energy management

2. FCC Class B

3. ROHS

4. IEC 60703

5. C-Tick Listed

H. Controller shall operate in the following environmental conditions:

1. -4 to 149 °F (-20 to 65 °C) without optional battery, or 32 to 122 °F (0 to 50 °C) with optional battery.

2. 0 to 95% relative humidity (RH), non-condensing.

2.03 CENTRAL PLANT AND AIR HANDLER APPLICATION CONTROLLERS

A. Provide one or more native BACnet application controllers for each air handler and provide native BACnet application controllers as needed for central plant control that adequately cover all objects listed in object list. All controllers shall interface to building controller through either MS/TP LAN using BACnet protocol, or Ethernet LAN using BACnet over Ethernet or BACnet TCP/IP. No gateways shall be used. Controllers shall include input, output and self-contained logic program as needed for complete control of units. Controllers shall be fully programmable using graphical programming blocks. Programming tool shall be resident on operator workstation and be the same tool as used for the building controller. No auxiliary or non-BACnet controllers shall be used.

B. BACnet Conformance

Application controllers shall be approved by the BTL as meeting the BACnet Advanced Application Controller requirements.

Please refer to section 22.2, BACnet Functional Groups, in the BACnet standard, for a complete list of the services that must be directly supported to provide each of the functional groups listed above.

All proprietary services, if used in the system, shall be thoroughly documented and provided as part of the submittal data. All necessary tools shall be supplied for working with proprietary information.

Standard BACnet object types supported shall include, as a minimum, Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Multi-state Values, Device, File, and Program object types. All proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. All necessary tools shall be supplied for working with proprietary information.

C. Application controllers shall include universal inputs with 12-bit resolution that accept 3K and 10K thermistors, 0–10VDC, Platinum 1000 ohm RTD, 0–5VDC, 4–20mA and dry contact signals. Any input on a controller may be either analog or digital with a minimum of three inputs that accept pulses.

Controller shall also include support and modifiable programming for interface to intelligent room sensor with digital display. Controller shall include binary and analog outputs on board. Analog

SECTION 230900 – INSTRUMENTATION AND CONTROL FOR HVAC EMCS PAGE 15 OF 31

outputs with 12-bit resolution shall support either 0–10VDC or 0–20mA. Binary outputs shall have LED indication of status. Software shall include scaling features for analog outputs. Application controller shall include 20VDC voltage supply for use as power supply to external sensors.

All outputs must have onboard Hand-Off-Auto (HOA) switches and a status indicator light. HOA switch position shall be monitored. Each analog output shall include a potentiometer for manually adjusting the output when the HOA switch is in the Hand position.

The position of each and every HOA switch shall be available system wide as a BACnet object property.

D. All program sequences shall be stored on board application controller in EEPROM. No batteries shall be needed to retain logic program. All program sequences shall be executed by controller up to 20 times per second (minimum of 10 times per second) and capable of multiple PID loops for control of multiple devices. All calculations shall be completed using floating-point math and system shall support display of all information in floating-point nomenclature at operator’s terminal.

The following control blocks shall be supported:

Natural Log

Exponential

Log base 10

X to the power of Y

Nth square root of X

5th Order Polynomial Equations

Astronomical Clock (sunrise/sunset calculation)

Time based schedules

E. Programming of application controller shall be completely modifiable in the field over installed BACnet LANs or remotely using modem interface. Operator shall program logic sequences by graphically moving function blocks on screen and tying blocks together on screen. Application controller shall be programmed using programming tools as described in operator’s terminal section.

F. Application controller shall include support for intelligent room sensor (see Section 2.10.B.)

Display on intelligent room sensor shall be programmable at application controller and include an operating mode and a field service mode. All button functions and display data shall be programmable to show specific controller data in each mode, based on which button is pressed on the sensor. See sequence of operation for specific display requirements at intelligent room sensor.

G. Schedules

The controller shall support a minimum of 3 BACnet Schedule Objects and have a real time clock on board with battery backup to maintain time through a power loss.

H. Logging Capabilities

Controller shall support a minimum of 50 trendlogs. Any object in the controller (real or calculated) may be logged. Sample time interval shall be adjustable at the operator’s workstation.

Controller shall periodically upload trended data to system server for long-term archiving if desired.

Archived data stored in (MS Jet…