Download SECTION 23 09 00 HVAC INSTRUMENTATION AND CONTROLS for
WORD | RTF | Text | Word Perfect
Find over 500 more CSI Sections
on Arcat.com
Switch to Masterformat 95
 
SECTION 23 09 00
HVAC INSTRUMENTATION AND CONTROLS
 
 
Copyright 2010 - 2017 ARCAT, Inc. - All rights reserved
** NOTE TO SPECIFIER ** Alerton, Div. of Honeywell International Inc.;. HVAC instrumentation and controls.
This section is based on the products of Alerton, Div. of Honeywell International Inc., which is located at:
6670 185th Ave. N. E.
Redmond, WA 98052
Phone: 425-869-8400
Fax: 425-869-8445
Email: sales@alerton.com
Web Site: www.alerton.com
Alerton is totally committed to helping you get the best performance from your buildings. We are a pioneer and an industry leader in providing building management solutions for heating, ventilation and air-conditioning equipment for types and sizes of buildings. We also help simplify building management by integrating fire, life safety, lighting, access management and other building systems. You'll find our proven solutions in thousands of buildings around the world. Our dealers are part a global independent dealer network, providing solid service and support that is second to none.
Our global network of more than 150 local dealers plays a vital role in making sure you and your people get the most from your building control system. Our clients appreciate knowing there is someone there to help throughout planning, installation and beyond. Alerton has led the way in developing products based on a standard open communication protocol to give building owners flexibility in their building solutions. We were the first to: Pioneer Direct Digital Controls (DDC) technology; Offer a Windows(R)-based operator's workstation; Offer an intelligent zone sensor-the Microset(TM); Offer a top-to-bottom native BACnet(R) system.
As part of Honeywell International Inc's Automation and Controls group, Alerton retains its entrepreneurial and pioneering spirit while gaining the additional financial and technological resources of a multinational Fortune 100 corporation. Our business excellence starts with superb local dealer and factory support backed by the power of Honeywell.
Our vision statement "Mastering Real Time Building Economics Together" demonstrates our commitment to collaboration and providing customized solutions tailored to your building's unique needs in the most economical way. of our products are designed to lead the industry in being cost-effective as well as dramatically improving energy efficiency and tenant comfort. In addition, we design our products to be easy to install, use, maintain, and service. These factors help ensure that you've made the best financial decision when you choose Alerton. We are experts at your building's economics. From installation to commissioning, of our building control solutions run your facility using the least amount energy and generate the maximum return on your investment.
 
PART 1 GENERAL
 
1.1
SECTION INCLUDES
A.
Scope of Work Covered by this Section:
1.
Furnish a totally native BACnet-based system, including a Microsoft Vista compatible operator's workstation. The operator's workstation, building controllers, application controllers, and input/output devices shall communicate using the protocols and network standards as defined by ANSI/ASHRAE Standard 135-2008, BACnet. In other words, 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.
2.
Provide necessary BACnet-compliant hardware and software to meet the system's functional specifications. Provide Protocol Implementation Conformance Statement (PICS) for Windows-based control software and every controller in system, including unitary controllers.
3.
Prepare individual hardware layouts, interconnection drawings, and software configuration from project design data.
4.
Implement the detailed design for analog and binary objects, system databases, graphic displays, logs, and management reports based on control descriptions, logic drawings, configuration data, and bid documents.
5.
Design, provide, and install equipment cabinets, panels, data communication network cables needed, and associated hardware.
6.
Provide and install interconnecting cables between supplied cabinets, application controllers, and input/output devices.
7.
Provide and install interconnecting cables between operator's terminals and peripheral devices supplied under this section.
8.
Provide complete manufacturer's specifications for items that are supplied. Include vendor name of every item supplied.
9.
Provide supervisory specialists and technicians at the job site to assist in phases of system installation, startup, and commissioning.
10.
Provide comprehensive operator and technician training program as described herein.
11.
Provide as-built documentation, operator's terminal software, diagrams, and other associated project operational documentation (such as technical manuals) on approved media, the sum total of which accurately represents the final system.
12.
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.
1.2
RELATED SECTIONS
 
** NOTE TO SPECIFIER ** Include sections of the specification that the control system contractor is required to review. This should include all contractual items and all areas that will interface with the control systems such as lighting, irrigation, chillers, fire alarm, etc. Delete any sections below not relevant to this project; add others as required.
 
A.
Section 23 05 00 - Common Work Results for HVAC.
B.
Section 26 05 00 - Common Work Results for Electrical.
1.3
SYSTEM DESCRIPTION
A.
A distributed logic control system complete with software and hardware functions shall be provided and installed. System shall be completely based on ANSI/ASHRAE Standard 135-2008, BACnet and achieved listing under the BACnet Testing Laboratories BACnet - Advanced Workstation Software (B-AWS). This system is to control mechanical equipment, including but not limited to unitary equipment such as VAV boxes, heat pumps, fan-coils, AC units, 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.
B.
Operator's workstation software shall use Microsoft Windows XP Professional, Microsoft Vista "Ultimate Enterprise" editions, or Microsoft Windows 7 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, and a full suite of field engineering tools including graphical programming and applications. Systems using operating systems other than that described above are strictly prohibited. Software required to program application specific controllers and field level devices and controllers will be left with the owner. Software passwords required to program and make future changes to the system will also become the property of the owner. Software required to make any program changes anywhere in the system, along with scheduling and trending applications, will be left with the owner. Software passwords required to program and make future changes to schedules, trends and related program changes will also become the property of the owner. Software required for field engineering tools including graphical programming and applications will be left with the owner. Software passwords required to program and make future changes to field engineering tools, including graphical programming and applications will be left with the owner. In addition, provide the monitoring of the following systems:
 
** NOTE TO SPECIFIER ** Edit the following paragraphs as applicable to the project.
 
1.
Irrigation monitors.
2.
Lighting control monitors.
3.
Building systems monitors as scheduled or required.
C.
Building controllers shall include complete energy management software, including scheduling building control strategies with optimum start and logging routines. 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.
 
** NOTE TO SPECIFIER ** Delete the following paragraph if digital readout for room sensors is not desired.
 
D.
Room sensors shall be provided with digital readout that allow the user to view room temperature, view outside air temperature, adjust the room setpoint within preset limits and set desired override time. User shall also be able to start and stop unit from the digital sensor. Include necessary wiring and firmware such that room sensor includes field service mode. Field service mode shall allow a technician to balance VAV zones and access any parameter in zone controller directly from the room sensor. Field service mode shall have the ability to be locked out.
 
** NOTE TO SPECIFIER ** Delete the following paragraph if paragraph above is retained, and digital readout for room sensors is not desired.
 
E.
Room sensors shall be architecturally pleasing, sense temperature, allow tenant to override system and adjust temperature setpoint, and include a jack that allows the service technician to adjust any zone parameter. Include wiring for sensor and field service tool.
F.
Application controllers for every terminal unit (including but not limited to VAV, HP, UV) air handler, 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 through BACnet LAN.
 
** NOTE TO SPECIFIER ** 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. Update based upon project. Delete references from the list below that are not actually required by the text of the edited section or alter as applicable.
 
1.4
REFERENCE STANDARDS
A.
American Society of Heating, Refrigerating and Air Conditioning Engineers (ASHRAE):
B.
ANSI/ASHRAE Standard 135-2008, BACnet.
C.
Uniform Building Code (UBC), including local amendments.
D.
National Electrical Code (NEC).
E.
FCC Part 15, Subpart J, Class A.
F.
EMC Directive 89/336/EEC (European CE Mark).
G.
Underwriters Laboratories, Inc. (UL):
1.
UL 864 - Control Units and Accessories for Fire Alarm Systems.
2.
UL 916 - Energy Management Equipment.
1.5
SUBMITTALS
A.
Submit under provisions of Section 01 30 00 - Administrative Requirements.
B.
Product Data: Manufacturer's data sheets on each product to be used, including:
1.
Preparation instructions and recommendations.
2.
Storage and handling requirements and recommendations.
3.
Installation methods.
C.
Drawings:
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 inch (ANSI B).
3.
Eight complete sets (copies) of submittal drawings shall be provided.
4.
Drawings shall be available on CD-ROM.
D.
System Documentation: Include the following in submittal package:
1.
System configuration diagrams in simplified block format.
2.
Input/output object listings and an alarm point summary listing.
3.
Electrical drawings that show system internal and external connection points, terminal block layouts, and terminal identification.
4.
Complete bill of materials, valve schedule and damper schedule.
5.
Manufacturer's instructions and drawings for installation, maintenance, and operation of purchased items.
6.
Overall system operation and maintenance instructions - including preventive maintenance and troubleshooting instructions.
7.
For system elements-operator's workstations, building controllers, application controllers, routers, and repeaters-provide BACnet Protocol Implementation Conformance Statements (PICS) as per ANSI/ASHRAE Standard 135.
8.
Provide complete description and documentation of any proprietary (non-BACnet) services and/or objects used in the system.
9.
A list of functions available and a sample of function block programming that shall be part of delivered system.
E.
Project Management: Vendor shall provide detailed project design and installation schedule with time markings and details for hardware items and software development phases.
1.6
QUALITY ASSURANCE
A.
The Building Automation System (BAS) system shall be designed, installed, commissioned, and serviced by manufacturer authorized and trained personnel. System provider 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.
B.
The contractor shall provide full-time, on-site, experienced project manager for this work, responsible for direct supervision of the design, installation, start-up and commissioning of the BAS system.
C.
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 10 projects, similar in size and scope to this project completed within the past 3 years.
D.
Materials and equipment shall be manufacturer's latest standard design that complies with the specification requirements.
E.
BAS peer-to-peer network controllers, central system controllers and local user displays shall be UL Listed under Standard UL 916, category PAZX.
F.
Electronic equipment shall conform to the requirements of FCC Regulation, Part 15, Governing Radio Frequency Electromagnetic Interference and be so labeled.
G.
Control system shall be engineered, programmed and supported completely by representative's local office that shall be within 100 miles (161 km) of project site.
1.7
DELIVERY, STORAGE, AND HANDLING
A.
Deliver, store and handle materials and products in strict compliance with manufacturer's instructions and recommendations and industry standards.
B.
Store materials in manufacturer's original sealed, labeled packaging until ready for installation and in accordance with manufacturer's instructions. Protect from damage.
1.8
PROJECT CONDITIONS
A.
Maintain environmental conditions (temperature, humidity and ventilation) within limits recommended by manufacturer for optimum results. Do not install products under environmental conditions outside manufacturer's absolute limits.
1.9
WARRANTY
A.
Warranty shall cover costs for parts, labor, associated travel, and expenses for a period of one year from completion of system acceptance. 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 and 48 hours on Saturday and Sunday. Warranty shall apply equally to both hardware and software.
PART 2 PRODUCTS
 
2.1
MANUFACTURERS
A.
Acceptable Manufacturer: Alerton Inc., which is located at: 16201 25th Ave. W.; Lynnwood, WA 98087; Tel: 425-921-4900; Fax: 425-921-4872; Email: request info (Sales@Alerton.com); Web: www.alerton.com
 
** NOTE TO SPECIFIER ** Delete one of the following two paragraphs; coordinate with requirements of Division 1 section on product options and substitutions.
 
B.
Substitutions: Not permitted.
C.
Requests for substitutions will be considered in accordance with provisions of Section 01 60 00 - Product Requirements.
 
** NOTE TO SPECIFIER ** Delete article if not required.
 
2.2
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 archived data. Each client shall include flexibility to access graphics from server or local drive. Server shall support a minimum of 50 simultaneous clients.
B.
BACnet Conformance:
1.
Operator Work Station shall be approved by the BTL as meeting the BACnet Advanced Work Station requirements.
2.
Please refer to Section 22.2, BACnet Functional Groups, in the BACnet standard, for a complete list of the services that shall be directly supported to provide each of the functional groups listed above. Proprietary services, if used in the system, shall be thoroughly documented and provided as part of the submittal data. 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, Calendar, Device, Event Enrollment, File, Notification Class, Program, and Schedule object types. Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
4.
The operator's workstation shall comply with Annex J of the BACnet specification for IP connections. Shall support remote connection to server using a thick client application. 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. Shall support interoperability on wide area networks (WANs) 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 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 data using three-dimensional graphic representations of 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. Information on any display shall be dynamically updated without any action by the user. Workstation shall allow user to change field-resident EMCS functions associated with the project, such as setpoints, weekly schedules, exception schedules and other functions, from any screen, no matter if that screen shows text or a complete graphic display. This shall be done without any reference to object addresses or other numeric/mnemonic indications.
2.
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 or with customized text such as Hand-Off-Auto. 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, for example, a graphic of a switch or light, 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 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 setpoint. 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 trendlogs.
5.
Analog objects may also be assigned to a system graphic, where the color of the defined object changes based on the analog object's value. For example, graphical thermostat device served by a single control zone would change color with respect to the temperature of the zone or its deviation from setpoint. 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 pushbuttons 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.
The BAS displays shall have the ability to link to content outside of the BAS system. Such content shall include but is not limited to: Launching external files in their native applications (for example, a Microsoft Word document) and launching a Web browser resolving to a specified Web address.
8.
The BAS system shall have the ability to run multiple, concurrent displays windows showing continuously updated 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 a minimum of 200 users. 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, menu items, and user specific system start display, as well restricted access to discrete BACnet devices to which that user requires access. Passwords, user names, and access assignments shall be adjustable online at the operator's terminal. Users shall have the capability to be assigned to specific user type "groups" that can share the same access levels to speed setup. Users who are members of multiple "groups" shall have the ability to activate/deactivate membership to those groups while using BAS (without logout). Users shall also have a set security level, which defines access to displays and individual objects 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.
4.
The system shall permit the assignment of an effective date range, as well as an effective time of day, that the User IDs are permitted to authenticate.
E.
Operator Activity Log
1.
Operator Activity Log that tracks operator changes and activities shall be included with system. 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 activity, sort the changes by user and also by operation. Operator shall be able to print the Operator Activity log display.
2.
Log shall be gathered and archived to hard drive on operator's 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. Selection of the operator activity log using this method shall show operator changes of just that displayed data.
F.
Scheduling:
1.
Operator's workstation shall show information in easy-to-read daily format including calendar of this month and next. 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 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 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 setpoints, indoor temperature and history of previous starts. Each and every individual zone shall have optimum start time independently calculated based on parameters listed. User shall input schedules to set time that occupied setpoint is to be attained. Optimum start feature shall calculate the startup time needed to match zone temperature to setpoint. User shall be able to set a limit for the maximum startup time allowed.
6.
Any displayed data that is changeable by the operator may be selected using the right mouse button and the schedule shall then be selectable on the screen. Selection of the schedule using this method shall allow the viewing of the assigned schedule or launch the Schedule Wizard to allow the point to be scheduled.
G.
Alarm Indication and Handling:
1.
Operator's workstation shall provide audible, visual, printed, and email means of alarm indication. The alarm dialog box shall always become the top dialog box regardless of the applications currently running. Printout of alarms shall be sent to the assigned terminal and port. Alarm notification can be filtered based on the User ID's authorization level.
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 delivered either to the operator's terminal, client or through remote communication using email (Authenticated SMTP supported).
4.
System shall include an Alarm Wizard for set up of alarms. Wizard shall walk user through 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.
Any displayed data that is changeable by the operator may be selected using the right mouse button and the alarm shall then be selectable on the screen. Selection of the alarm using this method shall allow the viewing of the alarm history or launch the Alarm Wizard to allow the creation of a new alarm.
H.
Trendlog Information:
1.
System server shall periodically gather historically recorded data stored in the building controllers and store the information in the system database. Stored records shall be appended with new sample data, allowing records to be accumulated. Systems that write over stored records shall not be allowed unless limited file size is specified. System database shall be capable of storing up to 50 million records before needing to archive data. Samples may be viewed at the operator's workstation. Operator shall be able to view trended records, both stored and archived. Trendlog records shall be displayed in standard engineering units.
2.
Software that is capable of graphing the trend logged object data shall be included. Software shall be capable of creating two-axis (X, Y) graphs that display up to 10 object types at the same time in different colors. Graphs shall show object values relative to time. Each trendlog shall support a custom scale setting for the graph view that is to be stored continuously. System shall be capable of trending on an interval determined by a polling rate, or change-of-value.
3.
Operator shall be able to change Trendlog setup information. This includes the information to be logged as well as the interval at which it is to be logged. Input, output, and value object types in the system may be logged. Operations shall be password protected. Setup and viewing may be accessed directly from any and graphics on which object is displayed.
4.
System shall include a Trend Wizard for setup of logs. Wizard shall walk user through 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 Trendlogs from the displayed menu.
5.
System shall be capable of using Microsoft SQL as the system database.
6.
Any displayed data that is changeable by the operator may be selected using the right mouse button and the trendlog shall then be selectable on the screen. Selection of the trendlog using this method shall allow the viewing of the trendlog view or launch the Trendlog wizard to allow the creation of a new trend.
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 energy log information in standard engineering units.
2.
Data shall be stored in database file format for direct use by third-party programs. Operation of system shall stay completely online during 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. 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, 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 setpoints 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 five priority levels of equipment shedding. 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 "first off-last on" (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 loads assigned to individual shed programs shall be displayed along with English description of each load.
K.
Tenant Activity:
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 following information for use in logging and billing:
a.
Tenant's 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 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 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 view and be able to delete events from billing and edit a selected tenant activity event's override time.
L.
Reports:
1.
System server shall be capable of periodically producing reports of trendlogs, alarm history, tenant activities, device summary, energy logs, and override points. The frequency, content, and delivery are to be user adjustable.
2.
Reports shall be capable of being delivered in multiple formats including text- and comma-separated value (CSV) files. The files can be printed, emailed, or saved to a folder, either on the server hard drive or on any network drive location.
M.
Configuration/Setup: 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. Items shall be modified using understandable terminology with simple mouse/cursor key movements.
N.
Field Engineering Tools:
1.
Operator's workstation software shall include field engineering tools for programming controllers supplied. Controllers shall be programmed using graphical tools that allow the user to connect function blocks on screen that provide sequencing of 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 select a 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 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 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 using the mouse.
6.
System shall automatically notify the user when a device that is not in the database is added to the network.
7.
System shall include backup/restore function that will back up entire system to selected medium and then restore system from that media. The system shall be capable of creating a backup for the purpose of instantiating a new client PC.
8.
The system shall provide a means to scan, detect, interrogate, and edit 3rd party BACnet devices and BACnet objects within those devices.
O.
Workstation Hardware:
1.
Provide operator's workstations at locations noted on the plans.
2.
Workstation/server computer minimum requirements
a.
PC Processor of 2 GHz dual-core or better.
b.
2 GB RAM or better.
c.
80GB hard disk or better.
d.
High-performance graphics adapter.
e.
Ethernet 10/100 network interface card.
f.
Keyboard, monitor, mouse, USB port and CD-ROM.
g.
Windows XP Professional; Vista Business, Ultimate, or Enterprise; Server 2003; or Windows 7.
h.
Modem, 56Kbm Minimum.
i.
Color printer (inkjet, color dye or laser).
 
** NOTE TO SPECIFIER ** Add processing power as required for specific job.
 
P.
Software: At the conclusion of project, contractor shall leave with owner a CD ROM that includes the complete software operation system and project graphics, setpoints, system parameters, and other components. This backup shall allow the owner how to completely restore the system in the case of a computer malfunction.
 
** NOTE TO SPECIFIER ** Delete article if not required. The advanced workstation is to be specified when utilizing Compass Software v1.5
 
2.3
OPERATOR'S ADVANCED 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. Thick and web clients shall access server for all archived data.
B.
BACnet Conformance:
1.
Operator workstation shall be approved by the BTL as meeting the BACnet Advanced Work Station (AWS) requirements.
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 AWS shall include as a minimum: Analog Value, Analog Input, Analog Output, Binary Value, Binary Input, Binary Output, 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 AWS shall comply with Annex J of the BACnet specification for IP connections. Must support remote connection to server using a thick client application. 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) and campus area networks (CANs). AWS shall support Foreign Device Registration to allow temporary workstation connection to IP network.
C.
Data Displays:
1.
Data displays shall render 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.
2.
Data displays shall render all data using iconic 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.
3.
Data display frame shall allow user to change all field-resident AWS functions associated with the project, such as setpoints, 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.
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.
5.
All displays and programming shall be generated and customized by the local use energy management and control system (EMCS) supplier and installer. Systems requiring factory development of graphics or programming of DDC logic are specifically prohibited.
6.
AWS shall be supplied with a library of standard graphics, which may be used unaltered or modified by the operator. AWS shall include a library of equipment graphic components to assemble custom graphics. Systems that do not allow customization or creation of new graphic objects by the operator (or with third-party software) shall not be allowed.
7.
Data display frame shall include customizable and persistent tree navigation for building, equipment and system diagnostic centric display organization.
8.
Each display may be protected from viewing unless operator credentials have the appropriate access level. An access 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.
9.
Data displays shall have the ability to link to content outside of the EMCS system. Such content shall include, but is not limited to launching external files in their native applications (for example, a Microsoft Word document) and launching a web browser resolving to a specified web address.
10.
The AWS shall have the ability to support 20 concurrent web clients.
11.
Summary Page Display Shall Support:
a.
A minimum of 1,024 points on the Summary page.
b.
Updating 10 data points from 20 different controllers in under 8 seconds with fresh live data.
c.
Sortable columns.
d.
Multi-point selection and edit for commanded points within the same column.
e.
Supports a graphic image that is user collapsible for point reference.
12.
Data Displays Shall Support:
a.
Graphic items with custom geometry that offer both color gradient shading and variable opacity in scale to system variables and range setpoints.
b.
Clear and custom geometry navigation buttons to provide intuitive navigation.
c.
Graphic files in JPG, PNG, and GIF file types.
d.
Viewing of 1,024 system data points in a single screen.
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.
AWS shall provide security for a minimum of 200 users. 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.
3.
Each user shall be allowed individual assignment of only those control functions, menu items, and user-specific system start display, as well as restricted access to discrete BACnet devices to which that user requires access.
4.
All passwords, user names, and access assignments shall be adjustable online at the operator's terminal.
5.
Users shall also have a set access level, which defines access to displays and individual objects the user may control. System shall include 10 separate and distinct access levels for assignment to users.
6.
The 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.
7.
The system shall permit the assignment of an effective date range, as well as an effective time of day, that the User IDs are permitted to authenticate.
8.
Support Active Directory Integration using LDAP for remote User Access control.
a.
Enforce Minimum password length.
b.
Enforce Combination of 3:
1)
Upper Case letters.
2)
Lower Case letters.
3)
Base 10 digits (0-9).
4)
Non-alphanumeric characters.
5)
Password expiration.
6)
User lockout after "x" failed attempts, where "x" is adjustable by the administrator.
E.
Operator Activity Log:
1.
An Operator Activity Log that tracks all operator changes and activities shall be included with AWS. 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. Operator shall be able to print the Operator Activity Log display.
2.
Log shall be gathered and archived to a hard drive on AWS as needed. Operator shall be able to export data for display and sorting in a spreadsheet.
F.
Scheduling:
1.
AWS and web client 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 access privileges.
4.
AWS 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 setpoints, 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 setpoint is to be attained. Optimum start feature shall calculate the startup time needed to match zone temperature to setpoint. User shall be able to set a limit for the maximum startup time allowed.
6.
Schedule list shall show all schedules currently defined. This list shall include all standard, holiday and event schedules. In addition, user shall be able to select a list that shows all scheduled points and zones.
7.
Display of all three schedules must show all ON times for standard, holiday and event schedules in different colors on a given day. In addition, OFF times for each must also be shown in additional colors. User shall be able to select from standard calendar what days are to be scheduled and same display shall show all points and zones affected. User shall be able to set time for one day and select all days of the week that shall be affected as a recurrence of that same schedule for that given day.
8.
Any displayed data that is changeable by the operator may be selected using the right mouse button and the schedule shall then be selectable on the screen. Selection of the schedule using this method shall allow the viewing of the assigned schedule allow the point to be scheduled.
9.
Schedule editor shall support drag-n-drop events and holidays onto the schedule calendar.
10.
Schedule editor shall support drag-n-drop events default to a two-hour period, which can then be adjusted by the user.
11.
Schedule editor shall support drag-n-drop holidays default for OFF all day and can be edited for multiple-day holidays.
12.
Schedule editor shall support the view of affected zones when adding or editing timed events of a schedule.
G.
Alarm Indication and Handling:
1.
AWS shall provide visual, printed, and email means of alarm indication. Printout of alarms shall be sent to the assigned network printer. Alarm notification can be filtered based on the User ID's authorization level.
2.
Alarm Manager shall provide log of alarm messages. History of alarm occurrences shall be archived to the data storage of the AWS or a SQL data base. 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, identification of operator acknowledging alarm, a comment form the operator who acknowledged the alarm, and the number of alarm occurrences.
3.
Alarm Manager shall provide a means to filter all alarms that have been configured in the system for alarm description, current alarm state, default and customer date range, disabled/enabled, and priority level.
4.
Alarm Manager shall provide a means to disable alarms for the purpose of performing maintenance without creating concern with unneeded alarm notifications.
5.
Alarm messages shall be in user-definable text (English or other specified language) and shall be delivered either to the AWS user interface or through remote communication using email (Authenticated SMTP supported).
6.
Alarm Manager shall provide the permissioned ability to Clear alarms occurrences from the Alarm Manager table while retaining the alarm in the AWS database for reporting purposes.
7.
Alarm Manager shall provide the permissioned ability to Purge alarm occurrences from the both the Alarm Manager table and the AWS database.
8.
Alarm Manager shall provide a user customizable navigation link from the Alarm message to the data display or template to the equipment associated with the alarm.
9.
Alarm Manager shall provide a context menu that will allow for navigation to Schedule, Trendlog, Object Property display, or System (user) Activity from the Alarm points live data value.
10.
AWS 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.
11.
User can silence audible annunciation for the current session.
12.
User can disable auto-refresh of alarm annunciation for current session.
13.
Any displayed data that is changeable by the operator may be selected using the right mouse button and the alarm shall then be selectable on the screen. Selection of the alarm using this method shall allow the viewing of the alarm history or allow the creation of a new alarm.
14.
Alarm Priority Levels (0-127) shall be definable in number and name. Alarms can be assigned to any of the priority levels defined.
15.
The following Alarm data shall be displayed in the Alarm Management User Interface:
16.
Number of times the alarm has occurred.
17.
Average Alarm Duration for the Following Transitions:
a.
Active to Normal.
b.
Active to Acknowledgement.
c.
Acknowledgement to Normal.
18.
Live data point of point alarmed.
19.
Navigation link to a user-selected display or URL.
20.
User Comment text can be input upon acknowledgement of an Alarm. The comment history is stored in the system data base and a user cannot edit or delete a comment after it has been submitted in the system.
21.
Alarm Performance: An alarm annunciation shall appear on the AWS user interface within 8 seconds, and appear in the Alarm manager and data base within 10 seconds of a triggered alarm.
H.
Trendlog Information:
1.
AWS shall periodically gather historically recorded data stored in the building controllers and store the information in the system database. Stored records shall be appended with new sample data, allowing records to be accumulated. Systems that write over stored records shall not be allowed unless limited file size is specified. System database shall be capable of storing up to 50 million records before needing to archive data. Samples may be viewed at the web client. Operator shall be able to view all trended records, both stored and archived. All trendlog records shall be displayed in standard engineering units.
2.
AWS shall be capable of trending on an interval determined by a polling rate, or change-of-value.
3.
AWS shall be able to change trendlog setup information. This includes the information to be logged as well as the interval at which it is to be logged. All operations shall be password protected. Viewing may be accessed directly from any and all graphics on which a trended object is displayed.
4.
AWS shall include a Trendlog 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 Trendlogs from the displayed menu.
5.
AWS shall be capable of using Microsoft SQL as the system database.
6.
Any displayed data that is changeable by the operator may be selected using the right mouse button and the trendlog shall then be selectable on the screen. Selection of the trendlog using this method shall allow the viewing of the trendlog view.
7.
Trendlog viewer shall provide:
a.
Software that is capable of graphing the trend-logged object data shall be included.
b.
Access and ability to create, edit and view are restricted to users by user account credentials
c.
Specific and repeatable URL defines the trendlog(s) that comprise the view.
d.
Call out of trendlog value at intersection of trend line and mouse-over vertical axis.
e.
Trendlog and companion logs can be configured to display on one of two independent vertical scales.
f.
Click zoom for control of data set viewed along either graph axis.
g.
User-specifiable start and end dates as well as a fast scroll features that supports click zoom of macro scale view of the data for quickly finding data set based on visual signature.
h.
User export of the viewed data set to MS Excel.
i.
Web browser-based help.
j.
Optional min/max ranges (Upper Control Limits, Lower Control Limits) for each value.
I.
Energy Log Information:
1.
AWS 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 database file format for direct use by third-party programs. Operation of system shall stay completely online during all graphing operations.
3.
AWS 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.
AWS 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.
AWS 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 setpoints 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 five (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 "first off-last on" (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.
AWS shall be able to display the status of each and every load shed program. Status of each load assigned to an individual shed program shall be displayed along with English description of each load.
K.
Tenant Activity:
1.
AWS 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-hours override usage and that data logged in AWS. 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.
Tenant's 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 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 view and be able to delete events from billing and edit a selected tenant activity event's override time.
L.
Reports:
1.
AWS shall be capable of periodically producing reports of trendlogs, alarm history, tenant activities, device summary, energy logs, and override points. The frequency, content, and delivery are to be user adjustable.
2.
All reports shall be capable of being delivered in multiple formats including text- and comma-separated value (CSV), and PDF files. The files can be printed, emailed, or saved to a folder, either on the server hard drive or on any network drive location.
3.
SQL Server Reporting Services can be used to create custom report templates.
M.
Configuration and 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.
N.
Field Engineering Tools:
1.
AWS 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 select a 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 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 detection of devices connected anywhere on the BACnet network by scanning 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 using the mouse.
6.
AWS shall automatically notify the user when a device that is not in the database is added to the network.
7.
AWS shall include backup/restore function that will back up entire system to selected medium and then restore system from that medium. The system shall be capable of creating a backup for the purpose of instantiating a new client PC.
8.
The system shall provide a means to scan, detect, interrogate, and edit third-party BACnet devices and BACnet objects within those devices.
O.
Workstation Hardware:
1.
Provide operator's workstation(s) at location(s) noted on the plans.
2.
AWS Server:
a.
64-bit OS.
b.
Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2012.
c.
2 GHz (or better), one or more dual-core or quad-core processors.
d.
8 GB RAM or higher.
e.
3 GB of hard drive space required for base installation without application data.
f.
Network interface card (100/1000 Mbps).
 
** Note to Specifier ** Review regularly, add processing power as required for specific job.
 
P.
Software:
1.
At the conclusion of the project, contractor shall leave with owner a CD-ROM that includes the complete software operation system and project graphics, setpoints, system parameters, etc. This backup shall allow the owner to completely restore the system in the case of a computer malfunction.
Q.
Web Client:
1.
EMCS supplier shall provide an HTML5-based browser access to the AWS as part of standard installation. User must be able to access all displays of real-time data that are part of the AWS using a standard web browser. Web browser shall tie into the network through owner-supplied Ethernet network connection. The AWS must be able to support 20 concurrent web client users.
2.
Browser shall be standard version of Microsoft Internet Explorer v10.0 or later, Firefox v19.0 or later and Chrome v24.0 or later. No special vendor-supplied software shall be needed on computers running browser. Data shall be displayed in real-time and update automatically without user interaction.
3.
Web pages shall be automatically generated using HTML5 from the data display files that reside on the AWS. Any system that requires use of an HTML editor for generation of web pages shall not be considered.
4.
Access through web client or thick client shall utilize the same hierarchical security scheme as the AWS. User shall be asked to log on once the client makes connection to the AWS. Once the user logs on, any and all changes that are made shall be tracked by the AWS. The user shall be able to change only those items he or she has authority to change. A user activity report shall show any and all activity of the users who have logged on to the system, regardless of whether those changes were made using a web client, thick client or through the AWS.
2.4
WEB INTERFACE
A.
General: BAS supplier shall provide Web-based access to the system as part of standard installation. User shall be able to access displays of real-time data that are part of the BAS using a standard Web browser. Web browser shall tie into the network through owner-supplied Ethernet network connection. Web page host shall be a separate device that resides on the BAS BACnet network, but is not the BAS server for the control system. BAS server shall be a separate computer from the Web page host device to ensure data and system integrity. The Web page software shall not require a per-user licensing fee or annual fees. The Web page host shall be able to support on average 50 simultaneous users with the ability to expand the system to accommodate an unlimited number of users.
B.
Browser Technology: Browser shall be standard version of Microsoft Internet Explorer v6.0 or later, Firefox v2.0 or later and Safari v2.0 or later (on Mac OS X). PDA browser connection shall be Pocket PC 2003, Windows Mobile 5.0, or Blackberry. No special vendor-supplied software shall be needed on computers running browser. Displays shall be viewable and the Web page host shall directly access real-time data from the BAS BACnet network. Data shall be displayed in real-time and update automatically without user interaction. User shall be able to change data on displays if logged in with the appropriate user name and password.
C.
Communications:
1.
Web page host shall include two Ethernet network connections. One network connection shall be dedicated to BAS BACnet network and shall be used to gather real-time data from the BACnet devices that form the BAS. This network shall communicate using BACnet, allowing the Web page host to gather data directly from units on the local LAN or from other projects connected over a WAN. This network shall also provide the connection to the BAS server for Web page generation.
2.
The second Ethernet connection shall provide the physical connection to the Internet or an IP-based WAN. It shall be the port that is used for the browser to receive Web pages and data from the Web page host. The Web page host shall act as a physical barrier between BAS network and the WAN or Internet connection that allows browser to receive Web pages and data. The two separate network connections provide for a physical barrier to prevent raw BACnet traffic being exposed on IP network.
3.
The Web page host shall provide for complete isolation of the IP and BACnet networks by not routing networking packets between the two networks.
4.
BAS BACnet Ethernet network shall be provided and installed by the BAS supplier. Owner shall provide and incur any monthly charges of WAN/Internet connection.
D.
Display of Data:
1.
Web page graphics shown on browser shall be replicas of the BAS displays. User shall need no additional training to understand information presented on Web pages when compared to what is shown on BAS displays. Web page displays shall include animation just as BAS displays. Fans shall turn, pilot lights shall blink, coils shall change colors, and so on.
2.
Real-time data shall be shown on browser Web pages. This data shall be directly gathered using the BACnet network and automatically updated on browser Web page displays without any user action. Data on the browser shall automatically refresh as changes are detected without re-drawing the complete display.
3.
It shall be possible for user from browser Web page to change data if the user is logged on with the appropriate password. Clicking on a button or typing in a new value shall change digital data. Using pull-down menus or typing in a new value shall change analog data.
4.
Data displays shall be navigated using pushbuttons on the displays that are simply clicked on with the mouse to select a new display. Alternatively, the standard back and forward buttons of the browser can be used for display navigation.
E.
Time Schedule Adjustment:
1.
Web access shall allow user to view and edit schedules in the system. This includes standard, holiday and event schedules as described in BAS specification. Display of schedules shall show interaction of schedules on a single display so user sees an overview of how work together. User shall be able to edit schedules from this display.
2.
Display of three schedules shall show ON times for standard, holiday and event schedules in different colors on a given day. In addition, OFF times for each shall also be shown in additional colors. User shall be able to select from standard calendar what days are to be scheduled and same display shall show points and zones affected. User shall be able to set time for one day and select days of the week that shall be affected as a recurrence of that same schedule for that given day.
3.
Schedule list shall show schedules currently defined. This list shall include standard, holiday and event schedules. In addition, user shall be able to select a list that shows scheduled points and zones.
F.
Logging of Information: User shall use standard browser technology to view trendlogs in system. User shall be able to view logged data in tabular form or graphical format. User shall be able to adjust time interval of logged data viewed and shall be able to adjust Y axis of data viewed in graphical format. User shall also be able to download data through the Web interface to local computer. Data shall be in CSV format.
G.
Alarm Handling: Web interface shall display alarms as they occur. User shall be able to acknowledge alarms using browser technology. In addition, user shall be able to view history of alarm occurrence over a user-selected time frame. In addition, those alarms may be filtered for viewing per user-selected options. A single selection shall display alarms that have not been acknowledged.
H.
Web Page Generation: Web pages shall be automatically generated from the BAS displays that reside on the BAS server. User shall access Web page host through the network and shall initiate a Web page generation utility that automatically takes the BAS displays and turns them into Web pages. The Web pages generated are automatically installed on the Web page host for access using any computer's standard browser. Any system that requires use of an HTML editor for generation of Web pages shall not be considered.
I.
Password Security and Activity Log: Access through Web browser shall utilize the same hierarchical security scheme as BAS system. User shall be asked to log on once the browser makes connection to Web page host. Once the user logs in, any and changes that are made shall be tracked by the BAS system. The user shall be able to change only those items he or she has authority to change. A user activity report shall show any and activity of the users who have logged in to the system, regardless of whether those changes were made using a browser or through the BAS workstation.
J.
BACnet Communication: Web server shall directly communicate to devices on BAS network using BACnet protocol. No intermediate devices are necessary for BACnet communication.
2.5
BUILDING CONTROLLER
A.
General Requirements:
1.
BACnet Conformance:
a.
Building Controller shall be approved by the BTL as meeting the BACnet Building Controller requirements.
b.
Please refer to section 22.2, BACnet Functional Groups, in BACnet standard, for a complete list of the services that shall be directly supported to provide each of the functional groups listed above. Proprietary services, if used in the system, shall be thoroughly documented and provided as part of submittal data. Necessary tools shall be supplied for working with proprietary information.
2.
Building controller shall be of modular construction such that various modules may be selected to fit the specific requirements of a given project. At a minimum, modules shall consist of a power supply module, a BACnet Ethernet-MS/TP (master slave token passing) module, a BACnet MS/TP-only module, and a modem module for telephone communication. Those projects that require special interfaces may use Modbus modules as needed. However, Ethernet communications and controllers-including central plant controllers, advanced application controllers and unitary controllers-supplied by BAS manufacturer shall utilize the BACnet protocol standard.
3.
Modules shall be selected to fit the particular project application. Up to seven modules powered by a single power supply module. Modules shall be panel-mounted on DIN rail for ease of addition and shall be interconnected using a simple plug-in cable. Module in middle shall be replaceable without removing any other modules.
4.
Modules 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. The software program implementing these strategies shall be completely flexible and user-definable. 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 WAN or downloaded through remote communications are not acceptable. Changing global strategies using firmware changes is also unacceptable.
5.
Programming shall be object-oriented using control function blocks, and support DDC functions, 1000 Analog Values and 1000 Binary Values. 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 controllers.
6.
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.
7.
Controller shall have sufficient memory to ensure high performance and data reliability. Battery shall provide power for orderly shutdown of controller and storage of data in nonvolatile flash memory. Battery backup shall maintain real-time clock functions for a minimum of 20 days.
8.
Global control algorithms and automated control functions shall execute using 32-bit processor.
B.
Schedules:
1.
Each building controller module shall support a minimum of 80 BACnet Schedule Objects and 80 BACnet Calendar Objects.
2.
Building controller modules shall provide normal seven-day scheduling, holiday scheduling and event scheduling.
3.
Logging Capabilities:
a.
Each building controller shall log as minimum 320 values. Any object in the system (real or calculated) may be logged. Sample time interval shall be adjustable at the operator's workstation.
b.
Logs may be viewed both on-site or off-site using WAN or remote communication.
c.
Building controller shall periodically upload trended data to networked operator's workstation for long-term archiving if desired.
d.
Archived data stored in database format shall be available for use in third-party spreadsheet or database programs.
C.
Alarm Generation:
1.
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.
2.
Each alarm may be dialed out as noted elsewhere.
3.
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.
4.
Controller shall be able to handle up to 320 alarm setups stored as BACnet event enrollment objects, with system destination and actions individually configurable.
D.
Demand Limiting:
1.
Demand limiting of energy shall be a built-in, user-configurable function. Each controller module shall support shedding of up to 200 loads using a minimum of two types of shed programs.
2.
Load shedding programs in building controller modules operate as defined herein.
E.
Tenant Activity Logging:
1.
Tenant Activity logging shall be supported by building controller module. Each independent module shall support a minimum of 80 zones.
2.
Tenant Activity logging shall function as defined in this specification.
F.
Ethernet - MS/TP Module:
1.
Ethernet - MS/TP Module shall support every function as listed under paragraph A, General Requirements, of this section and the following.
2.
Communication with operator's workstation and application controllers shall be through BACnet. Building controller Ethernet - MS/TP module shall incorporate as a minimum, the functions of a 2-way BACnet router. Controller shall route BACnet messages between the high-speed LAN (Ethernet 10/100MHz) and MS/TP LAN. Ethernet - MS/TP module shall also route messages from other building controller modules onto the BACnet Ethernet network.
a.
MS/TP LAN shall be software-configurable from 9.6 to 76.8Kbps.
b.
The RJ-45 Ethernet connection shall accept either 10Base-T or 100Base-TX BACnet over twisted pair cable (UTP).
3.
BACnet Conformance:
a.
Ethernet - MS/TP module shall, as a minimum, support MS/TP and Ethernet BACnet LAN types. It shall communicate directly using these BACnet LANs as a native BACnet device and shall support simultaneous routing functions between supported LAN types. Global controller shall be approved by the BACnet Testing Laboratory (BTL) as meeting the BACnet Building Controller requirements.
b.
Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
c.
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 LAN. Shall support interoperability on WANs and CANs and function as a BACnet Broadcast Management Device (BBMD).
G.
MS/TP Module:
1.
MS/TP Module shall support every function as listed under paragraph A, General Requirements, of this section and the following.
2.
Building controller MS/TP module communications shall be though BACnet MS/TP LAN to advanced application and application-specific controllers. MS/TP module shall also route messages to Ethernet - MS/TP module for communication over WAN.
a.
MS/TP LAN shall be software configurable from 9.6 to 76.8Kbps
b.
Configuration shall be through RS-232 connection.
3.
BACnet Conformance:
a.
MS/TP module shall be approved by the BTL (BACnet Testing Laboratory) as meeting the BACnet Building Controller requirements. MS/TP module shall as a minimum support MS/TP BACnet LAN type. It shall communicate directly using this BACnet LAN as a native BACnet device and shall support simultaneous routing functions between supported LAN types.
b.
Standard BACnet object types supported shall include, as a minimum, Analog Value, Binary Value, Calendar, Device, File, Group, Notification Class, Program, and Schedule object types. Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
H.
Power Supply Module:
1.
Power supply module shall power up to seven building controller modules. Input for power shall accept between 17-30VAC, 47-65Hz.
2.
Power supply module shall include rechargeable battery for orderly shutdown of controller modules including storage of data in flash memory and for continuous operation of real-time clocks for minimum of 20 days.
I.
Modem Module:
 
** NOTE TO SPECIFIER ** If communication through telephone modem to remote site is desired, include this section. Delete if not required.
 
1.
Provide functions that will allow remote communications using modem module to off-site locations. Modem module shall integrate directly into modular controller without any special software or hardware. Include one modem module along with cabling necessary for installation for the system.
2.
Provide off-site computer that allows operator to view and change information associated with system on color graphic displays. Operator shall be able to change parameters in this section from off-site location, including programming of building controllers and programmable application controllers including terminal unit controllers.
3.
Building controller shall have capability to automatically call out alarm conditions. If desired, controller may also send encoded message to digital pager. If an alphanumeric pager is in use by the operator, building controller shall be capable of sending a text or numeric string of alarm description. Building controllers connected to the local LAN shall be capable of calling out alarm messages through one or more shared modems connected to one or more of the building controllers on the local LAN.
4.
Building controller shall have capability to call a minimum of 20 different phone numbers. Numbers called may be controlled by type of alarm or time schedule.
5.
Owner provides standard voice-grade phone line for remote communication function.
6.
Building controller and internal modem shall be capable of modem-to-modem baud rates of 33.6 Kbps minimum over standard voice-grade phone lines. Lower baud rates are selectable for areas where local phone company conditions require them.
J.
TUX Module:
1.
TUX Module shall support every function as listed under Paragraph A, General Requirements, of this section and the following.
2.
Building controller TUX module communications shall be through Alerton TUX trunk to up to 64 Alerton TUXs. TUX module shall convert TUX data into BACnet objects and create virtual BACnet devices for every TUX connected to the TUX module. TUX module shall also route messages to Ethernet - MS/TP module for BACnet Ethernet communication over WAN.
a.
TUX module shall support TUX communication at 4800 and 9600 baud.
b.
Configuration shall be through RS-232 connection.
3.
BACnet Translation:
a.
TUX data shall be automatically translated into BACnet objects by the TUX module. No configuration by user is necessary. Predefined BACnet objects shall be automatically assigned for each type of TUX controller connected.
b.
Every TUX controller shall become a virtual BACnet device for ease of use with the BACnet workstation for configuration and operation.
c.
Standard BACnet object types supported shall include, as a minimum, Analog Value, Binary Value, Calendar, Device, File, Group, Notification Class, Program and Schedule object types. Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
2.6
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 objects listed in object list. 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:
1.
Application controllers shall be approved by the BTL as meeting the BACnet Advanced Application Controller requirements.
2.
Please refer to section 22.2, BACnet Functional Groups, in the BACnet standard, for a complete list of the services that shall be directly supported to provide each of the functional groups listed above. Proprietary services, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
3.
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. Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. 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 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.
1.
Outputs shall 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.
2.
The position of each and every HOA switch shall be available system wide as a BACnet object property.
D.
Program sequences shall be stored on board application controller in EEPROM. No batteries shall be needed to retain logic program. 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. Calculations shall be completed using floating-point math and system shall support display of information in floating-point nomenclature at operator's terminal.
1.
The following control blocks shall be supported:
a.
Natural Log.
b.
Exponential.
c.
Log base 10.
d.
X to the power of Y.
e.
Nth square root of X.
f.
5th Order Polynomial Equations.
g.
Astronomical Clock (sunrise/sunset calculation).
h.
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. Display on intelligent room sensor shall be programmable at application controller and include an operating mode and a field service mode. 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:
1.
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.
2.
Controller shall periodically upload trended data to system server for long-term archiving if desired. Archived data stored in (MS Jet Database or SQL) database form and shall be available for use in third-party spreadsheet or database programs.
I.
Alarm Generation:
1.
Alarms may be generated within the controller for any object change of value or state (either real or calculated). This includes things such as analog object value changes, and binary object state changes.
2.
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.
3.
Controller shall be able to handle up to 25 alarm setups stored as BACnet event enrollment objects, with system destination and actions individually configurable.
J.
The controller processor shall be a 32-bit processor.
K.
The packaging of the controller shall provide operable doors to cover the terminals once installation is complete. The housing of the controller shall provide for DIN rail mounting and also fully enclose circuit board.
 
** NOTE TO SPECIFIER ** The following is only applicable to projects where expandable/standalone central plant and AHU controllers are required. Delete if not required.
 
2.7
EXPANDABLE CENTRAL PLANT APPLICATION CONTROLLERS
A.
General:
1.
Expandable application controller shall be capable of providing control strategies for the system based on information from any or connected inputs. The program that implements these strategies shall be completely flexible and user-definable. Any systems utilizing factory pre-programmed global strategies that cannot be modified by field personnel on-site though simple download are not acceptable. Changing global strategies using firmware changes is also unacceptable. Program execution of controller shall be a minimum of once per second.
2.
Programming shall be object-oriented using control program blocks. Controller shall support a minimum of 500 Analog Values and 500 Binary Values. Each and every analog and binary value shall support standard BACnet priority arrays. Programming tool shall be provided with system and shall be the same tool that is used to program the building controller. Flowcharts shall be generated and automatically downloaded to controller. No re-entry of database information shall be necessary.
3.
Provide means to graphically view inputs and outputs on each program block in real-time as program is executing. This function may be performed using the operator's terminal or field computer.
4.
Controller shall have adequate data storage to ensure high performance and data reliability. Battery shall retain static RAM memory and real-time clock functions for a minimum of 1.5 years (cumulative). Battery shall be a field-replaceable (non-rechargeable) lithium type. Unused battery life shall be 10 years.
5.
The onboard, battery-backed real-time clock shall support schedule operations and trendlogs.
6.
Global control algorithms and automated control functions shall execute using 32-bit processor.
7.
Controller shall include both onboard 10Base-T/100Base-TX Ethernet BACnet communication over UTP and shall include BACnet IP communication. In addition, controller shall include BACnet Point-to-Point (PTP) connection port.
8.
The base unit of the controller shall host up to 8 expansion modules with various I/O combinations. These inputs and outputs shall include universal 12-bit inputs, binary triac outputs, and 8-bit switch-selectable analog outputs (0-10V or 0-20mA). Inputs shall support 3K and 10K thermistors, 0-5VDC, 0-10VDC, 4-20mA, dry contacts and pulse inputs directly.
9.
Outputs shall 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.
10.
The position of each and every HOA switch shall be available system wide as a BACnet object. Expandable central plant controller shall provide up to 176 discreet inputs/outputs per base unit.
B.
BACnet Conformance:
1.
Central plant/AHU controller shall, as a minimum, support PTP, MS/TP and Ethernet BACnet LAN types. It shall communicate directly through these BACnet LANs as a native BACnet device and shall support simultaneous routing functions between supported LAN types. Controllers shall be approved by the BTL as meeting the BACnet Advanced Application Controller requirements.
2.
Please refer to Section 22.2, BACnet Functional Groups, in the BACnet standard, for a complete list of the services that shall be directly supported to provide each of the functional groups listed above. Necessary tools shall be supplied for working with proprietary information.
3.
Standard BACnet object types supported shall include, as a minimum, Analog Input, Binary Input, Analog Output, Binary Output, Analog Value, Binary Value, Device, File, Group, Event Enrollment, Notification Class, Program, and Schedule object types. Necessary tools shall be supplied for working with proprietary information.
4.
The 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 LAN. Shall support interoperability on WANs and CANs, and function as a BBMD.
C.
Schedules:
1.
Each central plant/AHU controller shall support a minimum of 50 BACnet Schedule Objects.
D.
Logging Capabilities:
1.
Each controller shall support a minimum of 200 trendlogs. Any object in the system (real or calculated) may be logged. Sample time interval shall be adjustable at the operator's workstation.
2.
Controller shall periodically upload trended data to system server for long-term archiving if desired.
3.
Archived data stored in database format shall be available for use in third-party spreadsheet or database programs.
E.
Alarm Generation:
1.
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.
2.
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.
3.
Controller shall be able to handle up to 200 alarm setups stored as BACnet event enrollment objects, with system destination and actions individually configurable.
2.8
TERMINAL UNIT APPLICATION CONTROLLERS (HEAT PUMPS, AC UNITS, FAN-COILS)
A.
Provide one native BACnet application controller for each piece of unitary mechanical equipment that adequately covers objects listed in object list for unit. Controllers shall interface to building controller through MS/TP LAN using BACnet protocol. No gateways shall be used. Controllers shall include input, output and self-contained logic program as needed for complete control of unit.
B.
BACnet Conformance:
1.
Application controllers shall, as a minimum, support MS/TP BACnet LAN types. They shall communicate directly using this BACnet LAN at 9.6, 19.2, 38.4 and 76.8 Kbps, as a native BACnet device. Application controllers shall be approved by the BTL as meeting the BACnet Application Specific Controller requirements and support BACnet services necessary to provide the following BACnet functional groups:
a.
Files Functional Group.
b.
Reinitialize Functional Group.
c.
Device Communications Functional Group.
2.
Please refer to Section 22.2, BACnet Functional Groups in the BACnet standard, for a complete list of the services that shall be directly supported to provide each of the functional groups listed above. Proprietary services, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
3.
Standard BACnet object types supported shall include, as a minimum, Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Device, File, and Program Object Types. Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
C.
Application controllers shall include universal inputs with 10-bit resolution that can accept 3K and 10K thermistors, 0-5VDC, 4-20mA, dry contact signals and a minimum of 3 pulse inputs. Any input on controller may be either analog or digital. Controller shall also include support and modifiable programming for interface to intelligent room sensor. Controller shall include binary outputs on board with analog outputs as needed.
D.
Program sequences shall be stored on board controller in EEPROM. No batteries shall be needed to retain logic program. Program sequences shall be executed by controller 10 times per second and shall be capable of multiple PID loops for control of multiple devices. Programming of application controller shall be completely modifiable in the field over installed BACnet LANs or remotely through 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 same programming tools as building controller and as described in operator workstation section. Programming tools shall be provided and installed as part of system.
E.
Application controller shall include support for intelligent room sensor. Display on room sensor shall be programmable at controller and include an operating mode and a field service mode. 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.
 
** NOTE TO SPECIFIER ** The following section is only needed for projects where wireless MS/TP is required. Use the AZW-5000 to meet the requirement of this section. Delete if not required.
 
2.9
WIRELESS MS/TP TRANSCEIVER
A.
BACnet Conformance:
1.
Wireless MS/TP Transceiver shall meet BACnet Addendum q of ANSI/ASHRAE 135-2008 requirements.
2.
Support multiple BACnet Application Specific Controllers (B-ASC) to a Transceiver MS/TP trunk.
3.
Support multi-transceiver mesh wireless network topology
4.
Wireless MS/TP Transceiver shall, at a minimum, support MS/TP BACnet LAN types. They shall communicate directly through this BACnet LAN at 9.6, 19.2, 38.4 and 76.8 Kbps, as a B-ASC BACnet device.
5.
Standard BACnet object types supported shall include, as a minimum, Analog Value, Binary Value, Device, File, and Program Object Types.
6.
Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
B.
Wireless MS/TP Transceiver hardware shall:
1.
Include a 32 Bit processor.
2.
Include two selectable internal antennae with perpendicular orientation.
3.
Support external antenna using industry standard SMA connector type.
4.
Support connection to 2.4 GHz (IEEE Std 802.15.4 compliant) Wireless Wall Sensors (Battery powered).
5.
Meet the requirements of Listed Underwriters Laboratory for Open Energy Management Equipment (PAZX) under the UL Standard for Safety 916.
6.
Meet the requirements of EMC Directive (European CE Mark) EN 60950.
7.
Meet the requirements for FCC Part 15, Class B.
8.
Meet the requirements for EU Wireless: EN300328-1 2.4 GHz Spread Spectrum, EN301489-1 Standard.
9.
Be powered by 24VAC power.
C.
Wireless MS/TP Transceiver firmware shall:
1.
Configuration and point data shall be stored on board transceiver in Flash Memory.
2.
No batteries shall be needed to retain configuration data.
3.
Configuration of Wireless MS/TP Transceiver shall be completely modifiable in the field over installed BACnet LANs or remotely using modem interface.
4.
Wireless MS/TP communication shall be encrypted to 128 bit AES encryption standard.
D.
Wireless wall sensors shall be supported by the Wireless MS/TP Transceiver.
1.
Support up to Fifty (50) wireless wall sensors simultaneously.
2.
Wireless wall sensors shall operate in the 2.4 GHz (IEEE Std 802.15.4 compliant) radio frequency
3.
Support temperature, temperature and humidity, and temperature, setpoint and after-hours override wireless wall sensor types.
4.
Wireless communication shall be encrypted to 128 bit AES encryption standard.
E.
Wireless Wall Sensor:
1.
Wireless wall sensor shall use solid-state sensors and shall be packaged in aesthetically pleasing enclosure.
2.
Sensor shall provide override function, warmer/cooler dial for set point adjustment. Override time shall be stored in controller and be adjustable on a zone-by-zone basis. Adjustment range for warmer/cooler lever shall also be stored in EEPROM on controller.
3.
There shall be a mechanical means the lock the wall sensor to the base to prevent theft and vandalism.
4.
The wireless range in open air shall meet or exceed 300 ft. The strength of the wireless signal shall be indicated at the wireless sensor to aid in placement and trouble shooting.
5.
The receiver shall have a wireless communications received light that indicates the proper communication is occurring.
6.
The wireless wall sensor and receiver shall be paired in an addressable mean to facilitate easy replacement and reassignment.
7.
Temperature shall be accurate to +/- 0.5 degree Celsius from 12 - 30 degrees Celsius.
8.
Humidity sensor shall be accurate to +/-3 percent RH from 11-89 percent RH.
9.
Shall run on two AA Lithium batteries; providing a minimum battery life of 5 years. Low battery power shall be indicated on the unit via an LED and also readable as a BACnet Object.
10.
Shall use 2.4 GHz radio frequency (IEEE Std 802.15.4 compliant).
11.
Wireless communication shall be encrypted to 128 bit AES encryption standard.
2.10
VAV BOX CONTROLLERS - SINGLE DUCT
A.
Provide one native BACnet application controller for each VAV box that adequately covers objects listed in object list for unit. Controllers shall interface to building controller through MS/TP LAN using BACnet protocol. No gateways shall be used. Controllers shall include on board CFM flow sensor, inputs, outputs and programmable, self-contained logic program as needed for control of units.
B.
BACnet Conformance:
1.
Application controllers shall, at a minimum, support MS/TP BACnet LAN types. They shall communicate directly through this BACnet LAN at 9.6, 19.2, 38.4 and 76.8 Kbps, as a native BACnet device. Application controllers shall be approved by the BTL as meeting the BACnet Application Specific Controller requirements.
2.
Please refer to Section 22.2, BACnet Functional Groups, in the BACnet standard, for a complete list of the services that shall be directly supported to provide each of the functional groups listed above. Proprietary services, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
3.
Standard BACnet object types supported shall include, as a minimum, Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Device, File, and Program Object Types. Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
C.
Application controllers shall include universal inputs with 10-bit resolution that can accept 3K and 10K thermistors, 0 - 5 VDC, and dry contact signals. Inputs on controller may be either analog or digital. Controller shall also include support and modifiable programming for interface to intelligent room sensor with digital display. Controller shall also include binary outputs on board. For applications using variable speed parallel fans, provide a single analog output selectable for 0-10 V or 0-20 mA control signals. Application controller shall include microprocessor driven flow sensor for use in pressure independent control logic. Boxes shall be controlled using pressure-independent control algorithms and flow readings shall be in CFM (LPS if metric).
D.
Program sequences shall be stored on board application controller in EEPROM. No batteries shall be needed to retain logic program. Program sequences shall be executed by controller 10 times per second and shall be capable of multiple PID loops for control of multiple devices. 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 the same programming tool as Building Controller and as described in operator's workstation section. Programming tools shall be provided as part of system.
E.
Application controller shall include support for intelligent room sensor. Display on room sensor shall be programmable at application controller and include an operating mode and a field service mode. 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 operations for specific display requirements for intelligent room sensor.
F.
On board flow sensor shall be microprocessor-driven and pre-calibrated at the factory. Pre-calibration shall be at 16 flow points as a minimum. Factory calibration data shall be stored in non-volatile memory. Calibration data shall be field adjustable to compensate for variations in VAV box type and installation. Calibration parameters shall be adjustable through intelligent room sensor. Operator's workstation, portable computers, and special hand-held field tools shall not be needed for field calibration.
G.
Provide duct temperature sensor at discharge of each VAV box that is connected to controller for reporting back to operator's workstation.
 
** NOTE TO SPECIFIER ** The following section is only needed for projects where VLD-362, VLD-362-FF or VLD-362W controllers are required. Use the VLD-362W and appropriate sensors to meet the requirements of the wireless section. Delete if not required.
 
2.11
TOUCH SCREEN COMMUNICATING THERMOSTAT
A.
BACnet Conformance:
1.
Touch screen communicating thermostats shall be approved by the BTL as meeting the BACnet Application Specific Controller requirements.
2.
Touch screen Communicating Thermostats shall, at a minimum, support MS/TP BACnet LAN types. They shall communicate directly through this BACnet LAN at 9.6, 19.2, 38.4 and 76.8 Kbps, as a native BACnet device.
3.
Standard BACnet object types supported shall include, as a minimum, Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Device, File, and Program Object Types.
4.
Proprietary object types, if used in the system, shall be thoroughly documented and provided as part of the submittal data. Necessary tools shall be supplied for working with proprietary information.
B.
Touch screen Communicating Thermostat hardware shall:
1.
Include a 32 Bit processor.
2.
Include a backlit touch screen for the user interface, buttons are not allowed.
3.
Include 3 universal inputs with 12-bit resolution that can accept 3K and 10K Type II thermistors, 0-10VDC, 0 - 5 VDC, 4-20mA, and dry contact signals. Inputs on controller may be either analog or digital.
4.
Include built-in temperature sensor.
5.
Include built-in humidity sensor.
6.
Include 6 relay outputs on board.
7.
Include 2 analog outputs with 12-bit resolution. Each auto-detecting for 0-10 V or 4-20 mA control signals.
8.
Meet the requirements of Listed Underwriters Laboratory for Open Energy Management Equipment (PAZX) under the UL Standard for Safety 916.
9.
Meet the requirements of EMC Directive (European CE Mark) EN 60950.
10.
Meet the requirements for FCC Part 15, Class B.
11.
Be powered by 24VAC power.
 
** NOTE TO SPECIFIER ** The following paragraph should be deleted for VLD-362-FF. Leave Section C for VLD-362 and VLD-362W.
 
C.
Touch screen Communicating Thermostat programming shall:
1.
Program sequences shall be stored on board application controller in Flash Memory.
2.
No batteries shall be needed to retain logic program.
3.
Program sequences shall be executed by controller 10 times per second and shall be capable of multiple PID loops for control of multiple devices.
4.
Support internal schedule with real time clock.
5.
Support Peer-to-Peer programming.
6.
Support lockout of touch screen with a pass code.
7.
Programming of application controller shall be completely modifiable in the field over installed BACnet LANs or remotely using modem interface.
8.
Operator shall program logic sequences by graphically moving function blocks on screen and tying blocks together on screen.
9.
Application controller shall be programmed using the same programming tool as Building Controller and as described in operator's workstation section. Programming tools shall be provided as part of system.
 
** NOTE TO SPECIFIER ** The following paragraph is only needed for projects where VLD-362W controllers are required. You will need to use the VLD-362W and appropriate sensors to meet the wireless section. Delete for other projects.
 
D.
Wireless sensors shall be supported by the Touch screen Communicating Thermostat:
1.
Support up to 8 magnetic contact switches with CR2032-battery powered wireless transmitter.
2.
Support up to 3 passive infrared (PIR) motion detectors with 140 degree detection angle and AAA battery-powered wireless transmitter.
3.
Meet the requirements for FCC Part 15, Class B.
4.
Individual wireless sensor inputs can be used by fully programmable DDC to create custom sequence of operations in controller.
5.
Sensors operate in the 433.92 MHz wireless frequency with 50 foot range.
2.12
AUXILIARY CONTROL DEVICES
A.
Temperature Sensors: Temperature sensors to be solid-state electronic, interchangeable with housing appropriate for application. Wall sensors to be installed as indicated on drawings. Mount 48 inches above finished floor. Duct sensors to be installed such that the sensing element is in the main air stream. Immersion sensors to be installed in wells provided by control contractor, but installed by mechanical contractor. Immersion wells shall be filled with thermal compound before installation of immersion sensors. Outside air sensors shall be installed away from exhaust or relief vents, not in an outside air intake, and in a location that is in the shade most of the day.
B.
Intelligent Room Sensor with LCD Readout:
1.
Sensor shall contain a backlit LCD digital display and user function keys along with temperature sensor. Controller shall function as room control unit and allow occupant to raise and lower setpoint, and activate terminal unit for override use - within limits as programmed by building operator. Sensor shall also allow service technician access to hidden functions as described in sequence of operation.
2.
The intelligent room sensor shall simultaneously display room setpoint, room temperature, outside temperature, and fan status (if applicable) at each controller. This unit shall be programmable, allowing site developers the flexibility to configure the display to match their application. The site developer shall be able to program the unit to display time-of-day, room humidity and outdoor humidity. Unit shall have the capability to show temperatures in degrees Fahrenheit or Centigrade.
3.
Override time may be set and viewed in half-hour increments. Override time countdown shall be automatic, but may be reset to zero by occupant from the sensor. Time remaining shall be displayed. Display shall show the word "OFF" in unoccupied mode unless a function button is pressed.
4.
See sequence of operation for specific operation of LCD displays and function keys in field service mode and in normal occupant mode. Provide intelligent room sensors as specified in point list.
5.
Field service mode shall be customizable to fit different applications. If intelligent room sensor is connected to VAV controller, VAV box shall be balanced and air flow parameters shall be viewed and set from the intelligent room sensor with no computer or other field service tool needed.
C.
Wall Sensor: Standard wall sensor shall use solid-state sensor identical to intelligent room sensor and shall be packaged in aesthetically pleasing enclosure. Sensor shall provide override function, warmer/cooler lever for set point adjustment and port for plug-in of Field Service Tool for field adjustments. Override time shall be stored in controller and be adjustable on a zone-by-zone basis. Adjustment range for warmer/cooler lever shall also be stored in EEPROM on controller. Programmable variables shall be available to field service tool through wall sensor port.
D.
Wireless Wall Sensor:
1.
Wireless wall sensor shall use solid-state sensor and shall be packaged in aesthetically pleasing enclosure. Sensor shall provide override function, warmer/cooler dial for set point adjustment. Override time shall be stored in controller and be adjustable on a zone-by-zone basis. Adjustment range for warmer/cooler lever shall also be stored in EEPROM on controller. Programmable variables shall be available to field service tool through wall sensor port. There shall be a mechanical means the lock the wall sensor to the base to prevent theft and vandalism.
2.
Wireless wall sensor shall have a battery life of 5 year with alkaline batteries and 7.5 years with lithium batteries. A low battery indication shall be signaled to the controller prior to the battery being exhausted. The wireless sensor shall run on industry standard AA style batteries.
3.
The wireless range in open air shall meet or exceed 300 ft. The strength of the wireless signal shall be indicated at the wireless sensor to aid in placement and trouble shooting. The receiver shall have a wireless communications received light that indicates the proper communication is occurring.
4.
The wireless wall sensor and receiver shall be paired in an addressable mean to facilitate easy replacement and reassignment.
 
** NOTE TO SPECIFIER ** Delete optional LCD operator terminal if not required.
 
E.
LCD Operator Terminal;
1.
The LCD operator terminal is a small wall- or panel-mounted operator's terminal that connects directly to the MS/TP communications trunk.
2.
Provide LCD operator terminals in the locations shown on the drawings.
 
** NOTE TO SPECIFIER ** Requires addition of Microview for BACtalk.
 
F.
Field Service Tool:
1.
Field service tool shall allow technician to view and modify setpoints and tuning parameters stored in application controller. In addition, technician shall be able to view status of inputs and outputs on digital readout. Each piece of data shall have a data code associated with it that is customizable.
2.
Field service tool shall plug into wall sensor and provide the specified functionality. Operator workstation shall include the capability to disable operation of the field service tool.
 
** NOTE TO SPECIFIER ** Insert number required.
 
3.
Provide ___ Field Service Tools for this project.
G.
Network Connection Tool:
1.
Network connection tool shall allow technician to connect a laptop to any MS/TP network or at any MS/TP device and view and modify information throughout the entire BACnet network. Laptop connection to tool shall be through Ethernet or PTP.
2.
Provide quick connect to MS/TP LAN at each controller. Tool shall be able to adjust to MS/TP baud rates specified in the BACnet standard.
 
** NOTE TO SPECIFIER ** Insert number required.
 
3.
Provide ___ Network Connection Tools for this project.
 
** NOTE TO SPECIFIER ** The following are sample requirements. Modify or delete if not required.
 
2.13
ELECTRONIC ACTUATORS AND VALVES
A.
Quality Assurance for Actuators and Valves:
1.
UL Listed Standard 873 and C.S.A. Class 4813 02 certified.
2.
NEMA 2 rated enclosures for inside mounting, provide with weather shield for outside mounting.
3.
Five-year manufacturer's warranty. Two-year unconditional and three-year product defect from date of installation.
B.
Execution Details for Actuators and Valves:
1.
Furnish a Freeze-stat and install "Hard Wire" interlock to disconnect the mechanical spring return actuator power circuit for fail-safe operation. Use of the control signal to drive the actuators closed is not acceptable.
2.
Each DDC analog output point shall have an actuator feedback signal, independent of control signal, wired and terminated in the control panel for true position information and troubleshooting. Or the actuator feedback signal may be wired to the DDC as an analog input for true actuator position status.
3.
VAV box damper actuation shall be floating type or analog (2 - 10VDC, 4 - 20mA).
4.
Booster-heat valve actuation shall be floating type or analog (2 - 10vdc, 4 - 20ma).
5.
Primary valve control shall be analog (2 - 10VDC, 4 - 20mA).
C.
Actuators for damper and control valves 0.5 - 6 inches shall be electric unless otherwise specified, provide actuators as follows:
1.
UL Listed Standard 873 and Canadian Standards association Class 481302 shall certify actuators.
2.
NEMA 2 rated actuator enclosures for inside mounting. Use additional weather shield to protect actuator when mounted outside.
3.
Five-year manufacturer's warranty. Two-year unconditional and Three year product defect from date of installation.
4.
Mechanical spring shall be provided when specified. Capacitors or other non-mechanical forms of fail-safe are not acceptable.
5.
Position indicator device shall be installed and made visible to the exposed side of the actuator. For damper short shaft mounting, a separate indicator shall be provided to the exposed side of the actuator.
6.
Overload Protection: Actuators shall provide protection against actuator burnout by using an internal current limiting circuit or digital motor rotation sensing circuit. Circuit shall insure that actuators cannot burn out due to stalled damper or mechanical and electrical paralleling. End switches to deactivate the actuator at the end of rotation are acceptable only for butterfly valve actuators.
7.
A Pushbutton gearbox release shall be provided for non-spring actuators.
8.
Modulating actuators shall be 24VAC and consume 10VA power or less.
9.
Conduit connectors are required when specified and when code requires it.
D.
Damper Actuators:
1.
Outside air and exhaust air damper actuators shall be mechanical spring return. capacitors or other non-mechanical forms of fail-safe are not acceptable. The actuator mounting arrangement and spring return feature shall permit normally open or normally closed positions of the damper as required.
2.
Economizer actuators shall utilize analog control 2 - 10VDC, floating control is not acceptable.
3.
Electric damper actuators (including VAV box actuators) shall be direct shaft-mounted and use a V-bolt and toothed V-clamp causing a cold weld effect for positive gripping. Single bolt or set-screw type fasteners are not acceptable.
4.
One electronic actuator shall be direct shaft-mounted per damper section. No connecting rods or jackshafts shall be needed. Small outside air and return air economizer dampers may be mechanically linked together if one actuator has sufficient torque to drive both and damper drive shafts are both horizontal installed.
5.
Multi-section dampers with electric actuators shall be arranged so that each damper section operates individually. One electronic actuator shall be direct shaft-mounted per damper section.
E.
Valve Actuators 0.5 - 6 inches:
1.
Mechanical spring shall be provided on actuators for pre-heat coil and actuators for AHU heating or cooling coil when units are mounted outside. See plans for fail-safe flow function: Normal Open or Normal Closed. Capacitors or other non-mechanical forms of fail-safe are not acceptable.
2.
Zone service actuators shall be non-spring return unless otherwise specified.
3.
The valve actuator shall be capable of providing the minimum torque required for proper valve close-off for the required application.
4.
Control valves actuators shall have an attached 3-foot cable for easy installation to a junction box.
5.
Override handle and gearbox release shall be provided for non-spring return valve actuators.
F.
Control Dampers:
 
** NOTE TO SPECIFIER ** Pick either BAS or sheet metal contractor by deleting the first or second subparagraph below.
 
1.
The sheet metal contractor shall furnish and size automatic control dampers unless provided with packaged equipment. The sheet metal contractor shall install dampers unless provided with packaged equipment.
2.
Dampers used for modulating service shall be opposed blade type and arranged for normally open or normally closed operation as required. The damper is to be sized so that, when wide open, the pressure drop is a sufficient amount of its close-off pressure drop for effective throttling.
3.
Dampers used for two-position or open-close control shall be parallel blade type arranged for normally open or closed operation as required.
4.
Damper linkage hardware shall be constructed of aluminum or corrosion-resistant zinc and nickel-plated steel and furnished as follows:
5.
Bearing support bracket and drive blade pin extension shall be provided for each damper section. Sheet metal contractor shall install bearing support bracket and drive blade pin extension. Sheet metal contractor shall provide permanent indication of blade position by scratching or marking the visible end of the drive blade pin extension.
6.
Drive pin may be round only if V-bolt and toothed V-clamp is used to cause a cold weld effect for positive gripping. For single bolt or set-screw type actuator fasteners, round damper pin shafts shall be milled with at least one side flat to avoid slippage.
7.
Damper manufacturer shall supply alignment plates for multi-section dampers.
G.
Control Valves 0.5 - 6 inches:
1.
The BAS contractor shall furnish specified motorized control valves and actuators. BAS contractor shall furnish control wiring to actuators. The plumbing contractor shall install valves. Equal percentage control characteristic shall be provided for water coil control valves. Linear valve characteristic is acceptable for 3-way valves that are 2.5 inches and above.
2.
Characterized control valves shall be used for hydronic heating or cooling applications and small to medium AHU water-coil applications to 100GPM. Actuators are non-spring return for terminal unit coil control unless otherwise noted. If the coil is exposed to the outside air stream, see plans for spring return requirement.
a.
Leakage is aero percent, close-off is 200psi, maximum differential is 30psi; rangeablity is 500:1.
b.
Valves 0.5 - 2 inches shall be nickel-plated forged brass body, NPT screw type connections.
c.
Valves 0.5 - 1.25 inches shall be rated for ANSI Class 600 working pressure. Valves 1.5 and 2 inches shall be rated for ANSI Class 400 working pressure.
d.
The operating temperature range shall be 0 - 250 degrees F.
e.
Stainless steel ball and stem shall be furnished on modulating valves.
f.
Seats shall be fiberglass reinforced Teflon.
g.
Two-way and three-way valves shall have an equal percentage control port. Full stem rotation is required for maximum flow to insure stable BTU control of the coil.
h.
Three-way valve shall be applicable for both mixing and diverting.
i.
The characterizing disc is made of TEFZEL and shall be keyed and held secure by a retaining ring.
j.
The valves shall have a blow-out proof stem design.
k.
The stem packing shall consist of 2 lubricated O-rings designed for on-off or modulating service and require no maintenance.
l.
The valves shall have an ISO type, 4-bolt flange for mounting actuator in any orientation parallel or perpendicular to the pipe.
m.
A non-metallic thermal isolation adapter shall separate valve flange from actuator.
n.
One fastening screw shall secure the direct coupling of the thermal isolation adapter between the actuator and the valve. This will prevent lateral or rotational forces from affecting the stem and its packing O-rings.
3.
Globe valves 0.5 - 2 inches shall be used for steam control or water flow applications.
a.
Valves shall be bronze body, NPT screw type, and shall be rated for ANSI Class 250 working pressure.
b.
Valves 0.5 inches (DN15) through 2 inches (DN50) with spring return actuators shall close off against 50 psi pressure differential with Class III leakage (0.1 percent).
c.
The operating temperature range shall be 20 - 280 degrees F.
d.
Spring loaded TFE packing shall protect against leakage at the stem.
e.
Two-way valves shall have an equal percentage control port.
f.
Three-way valves shall have a linear control and bypass port.
g.
Mixing and diverting valves shall be installed specific to the valve design.
4.
Globe Valve 2.5 - 6 inches:
a.
Valves 2.5 inches (DN65) through 6 inches (DN50) shall be iron body, 125 lb. flanged with Class III (0.1 percent) close-off leakage at 50 psi differential.
b.
Valves with spring return actuators shall close off against 50 psi pressure differential with Class III leakage (0.1 percent).
c.
Flow type for two-way valves shall be equal percentage. Flow type for three-way valves shall be linear.
d.
Mixing and diverting valves shall be installed specific to the valve design.
H.
Butterfly Valves:
1.
Butterfly valves shall be sized for modulating service at 60 - 70 degree stem rotation. Isolation valves shall be line-size. Design velocity shall be less than 12 feet per second when used with standard EPDM seats.
a.
Body is cast iron.
b.
Disc is aluminum bronze standard.
c.
Seat is EPDM standard.
d.
Body Pressure is 200 psi, -30 - 275 degrees F.
e.
Flange is ANSI 125/250.
f.
Media Temperature Range is -22 - 240 degree F.
g.
Maximum Differential Pressure is 200 psi for 2- to 6- inch size.
I.
Butterfly Valve Industrial Actuators:
1.
Actuators shall be approved under Canadian Standards Association or other Nationally Recognized Testing Laboratory to UL standards. CSA Class 4813 02 or equal. Enclosure shall be NEMA 4 (weatherproof) enclosure and will have an industrial quality coating.
a.
Actuator shall have a motor rated for continuous duty. The motor shall be fractional horsepower; permanent split capacitor type designed to operate on a 120VAC, 1pH, 60Hz supply. Two adjustable cam-actuated end travel limit switches shall be provided to control direction of travel. A self-resetting thermal switch shall be imbedded in the motor for overload protection.
b.
Reduction gearing shall be designed to withstand the actual motor stall torque. Gears shall be hardened alloy steel, permanently lubricated. A self-locking gear assembly or a brake shall be supplied.
c.
Actuator shall have a 6 ft wiring harness provided for ease in field wiring (above 1500 in-lbs). Two adjustable SPDT cam-actuated auxiliary switches, rated at 250VAC shall be provided for indication of open and closed position. Actuator shall have heater and thermostat to minimize condensation within the actuator housing.
d.
Actuator shall be equipped with a hand wheel for manual override to permit operation of the valve in the event of electrical power failure or system malfunction. Hand wheel shall be permanently attached to the actuator and when in manual operation electrical power to the actuator will be permanently interrupted. The hand wheel will not rotate while the actuator is electrically driven.
e.
The actuator shall be analog, floating, or two position as called out in the control sequence of operation. Analog valves shall be positive positioning, and respond to a 2 - 10VDC, 4 - 20mA, or adjustable signal as required. Analog actuators shall have a digital control card allowing any voltage input for control and any DC voltage feedback signal for position indication.
2.
Performance Verification Test:
a.
Control loops shall cause productive actuation with each movement of the actuator and actuators shall modulate at a rate that is stable and responsive. Actuator movement shall not occur before the effects of previous movement have affected the sensor.
b.
Actuator shall have capability of signaling a trouble alarm when the actuator Stop-Go Ratio exceeds 30 percent.
3.
Actuator mounting for damper and valve arrangements shall comply to the following:
a.
Damper actuators: Shall not be installed in the air stream
b.
A weather shield shall be used if actuators are located outside. For damper actuators, use clear plastic enclosure.
c.
Damper or valve actuator ambient temperature shall not exceed 122 degrees F through any combination of medium temperature or surrounding air. Appropriate air gaps, thermal isolation washers or spacers, standoff legs, or insulation shall be provided as necessary.
d.
Actuator cords or conduit shall incorporate a drip leg if condensation is possible. Water shall not be allowed to contact actuator or internal parts. Location of conduits in temperatures dropping below dew point shall be avoided to prevent water from condensing in conduit and running into actuator.
e.
Damper mounting arrangements shall comply to the following:
1)
The ventilation subcontractor shall furnish and install damper channel supports and sheet metal collars.
2)
No jack shafting of damper sections shall be allowed.
3)
Multi-section dampers shall be arranged so that each damper section operates individually. One electronic actuator shall be direct shaft mounted per section.
f.
Size damper sections based on actuator manufacturer's specific recommendations for face velocity, differential pressure and damper type. In general:
1)
Damper section shall not exceed 24 ft-sq. with face velocity > 1500 FPM.
2)
Damper section shall not exceed 18 ft-sq. with face velocity > 2500 FPM.
3)
Damper section shall not exceed 13 ft-sq. with face velocity > 3000 FPM.
g.
Multiple section dampers of two or more shall be arranged to allow actuators to be direct shaft mounted on the outside of the duct.
h.
Multiple section dampers of three or more sections wide shall be arranged with a 3-sided vertical channel (8 inches wide by 6 inches deep) within the duct or fan housing and between adjacent damper sections. Vertical channel shall be anchored at the top and bottom to the fan housing or building structure for support. The sides of each damper frame shall be connected to the channels. Holes in the channel shall allow damper drive blade shafts to pass through channel for direct shaft-mounting of actuators. Open side of channel shall be faced downstream of the airflow, except for exhaust air dampers.
i.
Multiple section dampers to be mounted flush within a wall or housing opening shall receive either vertical channel supports as described above or sheet metal standout collars. Sheet metal collars (12-inch minimum) shall bring each damper section out of the wall to allow direct shaft-mounting of the actuator on the side of the collar.
4.
Valve Sizing for Water Coil:
a.
On/Off control valves shall be line size.
b.
Modulating control valve body size may be reduced, at most, two pipe sizes from the line size or not less than half the pipe size. The BAS contractor shall size water coil control valves for the application as follows:
1)
Booster-heat valves shall be sized not to exceed 4 - 9psi differential pressure. Size valve for 50 percent valve authority. Valve design pressure drop is equal to sum of coil drop plus the balance valve drop.
2)
Primary valves shall be sized not to exceed 5 - 15psi differential pressure. Size valve for 50 percent valve authority. Valve design pressure drop is equal to sum of coil drop plus the balance valve drop.
3)
Butterfly valves shall be sized for modulating service at 60 - 70 degree rotation. Design velocity shall be 12 feet per second or less when used with standard EPDM seats.
c.
Valve mounting arrangements shall comply to the following:
1)
Unions shall be provided on ports of two-way and three-way valves.
2)
Install three-way equal percentage characterized control valves in a mixing configuration with the "A" port piped to the coil.
3)
Install 2.5 inches and above, three-way globe valves, as manufactured for mixing or diverting service to the coil.
2.14
ENCLOSURES
A.
Controllers, power supplies and relays shall be mounted in enclosures.
B.
Enclosures may be NEMA 1 when located in a clean, dry, indoor environment. Indoor enclosures shall be NEMA 12 when installed in other than a clean environment.
C.
Enclosures shall have hinged, locking doors.
D.
Provide laminated plastic nameplates for enclosures in any mechanical room or electrical room. Include location and unit served on nameplate. Laminated plastic shall be 0.125 inches (3 mm) thick and appropriately sized to make label easy to read.
PART 3 EXECUTION
 
3.1
EXAMINATION
A.
Prior to starting work, carefully inspect installed work of other trades and verify that such work is complete to the point where work of this Section may properly commence.
B.
Notify the owner's representative in writing of conditions detrimental to the proper and timely completion of the work.
C.
Do not begin work until unsatisfactory conditions are resolved.
3.2
INSTALLATION (GENERAL)
A.
Install in accordance with manufacturer's instructions.
B.
Provide miscellaneous devices, hardware, software, interconnections, installation, and programming required to ensure a complete operating system in accordance with the sequences of operation and point schedules.
3.3
LOCATION AND INSTALLATION OF COMPONENTS
A.
Locate and install components for easy accessibility; in general, mount 48 inches above floor with minimum 3 feet (1 m) of clear access space in front of units. Obtain approval on locations from owner's representative prior to installation.
B.
Instruments, including but not limited to switches and transmitters, shall be suitably wired and mounted to protect them from vibration, moisture, and high or low temperatures.
C.
Identify equipment and panels. Provide permanently mounted tags for panels.
D.
Provide stainless steel or brass thermowells suitable for respective application and for installation under other sections, and sized to suit pipe diameter without restricting flow.
3.4
INTERLOCKING AND CONTROL WIRING
A.
Provide interlock and control wiring. Wiring shall be installed neatly and professionally, in accordance with Specification Division 16 and national, state and local electrical codes.
B.
Provide wiring as required by functions as specified and as recommended by equipment manufacturers, to serve specified control functions. Provide shielded low capacitance wire for communications trunks.
C.
Control wiring shall not be installed in power circuit raceways. Magnetic starters and disconnect switches shall not be used as junction boxes. Provide auxiliary junction boxes as required. Coordinate location and arrangement of control equipment with the owner's representative prior to rough-in.
D.
Provide auxiliary pilot duty relays on motor starters as required for control function.
E.
Provide power for control components from nearest electrical control panel or as indicated on the electrical drawings; coordinate with electrical contractor.
F.
Control wiring in the mechanical, electrical, telephone and boiler rooms to be installed in raceways. Other wiring to be installed neatly and inconspicuously per local code requirements. If local code allows, control wiring above accessible ceiling spaces may be run with plenum-rated cable (without conduit).
3.5
DDC OBJECT TYPE SUMMARY
A.
Provide database generation.
B.
Displays: System displays shall show analog and binary object types within the system. They shall be logically laid out for easy use by the owner. Provide outside air temperature indication on system displays associated with economizer cycles.
C.
Run Time Totalization: At a minimum, run time totalization shall be incorporated for each monitored supply fan, return fan, exhaust fan, hot water and chilled water pumps. Warning limits for each point shall be entered for alarm and or maintenance purposes.
D.
Trendlog: Binary and analog object types (including zones) shall have the capability to be automatically trended.
E.
Alarm: Analog inputs (High/Low Limits) and selected binary input alarm points shall be prioritized and routed (locally or remotely) with alarm message per owner's requirements.
F.
Database Save: Provide backup database for standalone application controllers on disk.
3.6
FIELD SERVICES
A.
Prepare and start logic control system under provisions of this section.
B.
Start up and commission systems. Allow sufficient time for startup and commissioning prior to placing control systems in permanent operation.
C.
Provide the capability for off-site monitoring at control contractor's local or main office. At a minimum, off-site facility shall be capable of system diagnostics and software download. Owner shall provide phone line for this service for one year or as specified.
D.
Provide owner's representative with spare parts list. Identify equipment critical to maintaining the integrity of the operating system.
 
** NOTE TO SPECIFIER ** Insert requirements.
 
3.7
AS-BUILT DOCUMENTATION REQUIRED
A.
As-Built Documentation: _______________
3.8
TRAINING
A.
Provide application engineer to instruct owner in operation of systems and equipment.
B.
Provide system operator's training to include (but not be limited to) such items as the following: modification of data displays, alarm and status descriptors, requesting data, execution of commands and request of logs. Provide this training to a minimum of three persons.
C.
Provide on-site training above as required, up to 16 hours as part of this contract.
D.
Provide tuition for at least one individual to attend for a one-week factory training class. If applicable, costs for travel, lodging and meals will be the responsibility of the owner.
3.9
SEQUENCE OF OPERATIONS / DEMONSTRATION
A.
Demonstrate complete operating system to owner's representative.
B.
Provide certificate stating that control system has been tested and adjusted for proper operation.
C.
Provide a complete and operational temperature control and building automation system based on the following points and sequence of operation. The system shall be complete as to sequences and standard control practices. The determined point list is the minimum amount of points that are to be provided. If additional points are required to meet the sequence of operation, they will be provided.
D.
BACnet Object List:
1.
The following points as defined for each piece of equipment are designated as follows:
a.
Binary Out (BO): Defined as any two-state output.
b.
Binary In (BI): Defined as any two-state input (alarm, status), or other.
c.
Analog In (AI): Defined as any variable input (temperature) (position), or other.
d.
Analog Out (AO): Defined as any electrical variable output. 0-20mA, 4-20mA and 0-10VDC are the only acceptable analog outputs. The driver for analog outputs shall come from both hardware and software resident in the controllers. Transducers will not be acceptable under any circumstance.
e.
Analog Value (AV): Hardware points, software points, graphed and totaled as standard with manufacturer.
1)
Hardware Points: AI, AO, BI, BO.
2)
Software Points: AV, BV, Sched, Trend, Alarm.
3)
Show on graphic.
END OF SECTION