• It is the intention of the University to have automated and control systems which meet the requirements of BACnet communication according the ASHRAE standard SPC-135A/95 at every level of the device network.
• The building automation system shall be web based with the following features as minimum:
  1. System shall provide real-time navigation through the system and auto listing of all BACNet devices on the network and their objects.
  2. System shall provide view and edit operations of most objects (I/O, variables, schedules, trend) including Auto/Manual, set point, descriptions, etc.
  3. Users shall be able to view and acknowledge active alarms.
  4. Alarm notification can be e-mailed.
  5. System shall provide the same level of security as the on-site operator's terminal.
  6. System shall allow unlimited concurrent users.
• All materials and equipment used shall be standard components, regularly manufactured for this or other systems and not custom designed.  All systems and components shall have been thoroughly tested and proven in actual use for at least two years.
• All controllers performing algorithmic calculations and control of the Air Handling and other primary mechanical equipment shall have BACnet Class 3 performance as a minimum.
• The sequence of operation for every system shall be included in the Building Automation System on the same screen showing that system graphic. There shall be a sublink on the screen to direct all users to such sequence of operation.
• Each Graphic screen shall have a text screen associated with it, and the user will be able to switch back and forth between each unit’s graphic and text screen via a hyperlink button.
• All floor plan layouts shall be included in the building automation system. Access to the floor plan shall be through a sublink on the same screen showing the graphics of the HVAC serving that space.
• Room numbers shown on graphic screens shall be dynamically linked to the description tag of the object in the Tridium database that represents that VAV serving that room.
• Building Automation Systems (BAS) performance requirements shall include the following applications:
  1. Heating, Ventilating and Air Conditioning Monitoring, Equipment and Lighting Control
  2. Energy Management Routines
  3. Future Fire Alarm connectivity through existing BAS
  4. Miscellaneous Equipment Monitoring
• Tridium Building automation system license: All tridium controllers shall be provided with a fully open license that follows the format shown below. Where a field is shown as an asterisk "*" it shall be understood to mean that parameter is open to all possible values. All features shown below shall be included in every tridium device installed. Where a feature below is shown with an expiration or limit as "never" or "none" so shall those parameters be for any license for any tridium device provided. The Tridium device shall come with the most current revision of software released by Tridium.                                                             <feature name="about" owner="UIC" project="UIC"/>
  <feature name="brand" brandId="brand" accept.station.in="*" accept.station.out="*" accept.wb.in="*" accept.wb.out="*"/>
  <feature name="bacnet" expiration="never" device.limit="none" export="true" history.limit="none" point.limit="none" schedule.limit="none"/>
  <feature name="email" expiration="never"/>
  <feature name="lonworks" expiration="never" device.limit="28" history.limit="none" point.limit="none" schedule.limit="none"/>
  <feature name="mstp" expiration="never" port.limit="4"/>
  <feature name="ndio" expiration="never" device.limit="none" history.limit="none" point.limit="none" schedule.limit="none"/>
  <feature name="niagaraDriver" expiration="never" device.limit="none" history.limit="none" point.limit="none" schedule.limit="none"/>
  <feature name="obixDriver" expiration="never" device.limit="27" export="true" foreignDevice.limit="27" foreignHistory.limit="none" foreignPoint.limit="none" foreignSchedule.limit="none" history.limit="none" point.limit="none" schedule.limit="none"/>
  <feature name="serial" expiration="never"/>
  <feature name="station" expiration="never"/>
  <feature name="web" expiration="never" ui="true" ui.wb="true"/>
  
• A trunk cable riser diagram showing Digital System Controllers/Security Digital System Controllers/Fire Digital System controllers (DSC/SDSC/FDSC) locations, and all trunk data conductors shall be furnished.
• Company shall provide programming editing tool for every project, for all databases and for programming field controllers and program shall be self-documenting by printout into either VISIO or ACAD format.
• The programming tool for field controller must be object oriented and should use a graphical interface.
• Programmer must be certified in Niagara AX product programming (since a JACE 545 is specified), and must be a resident employee from a further office within 50 miles of the job site. Temporarily importing an employee from a further office just to do programming shall be unacceptable, as it will cause warranty coverage issues.
• All BACnet devices shall include all hardware and software necessary to integrate the controls with the existing BACnet over Ethernet or IP network and meet the systems functional specification.
• Any BACnet device that exists on a common BACnet inter-network must have a unique address, referred to as its Device Instance. The Chief Plant Operating Engineers Office shall establish the Device Instance numbering system.
• The BAS shall be a computer based distribution system that shall monitor life safety, mechanical and electrical equipment status and have the capability of controlling certain mechanical, electrical and life safety system components. The architecture of the system shall be a distributed one in which the monitor/control function responsibility is located as close as possible to the monitored/controlled variable. This results in several levels of processing which can stand alone should the communication be lost to the next higher level of processing.
• The Mechanical Equipment Controller shall be connected to the system through the local network to the system backbone, for each piece of mechanical equipment, and provide all BACnet System defined functionality. The operator has direct access to all network devices at this point of entry.
• Equipment Control will be provided by programmable or application specific Controllers. All algorithms required for standalone operation of each control loop will be contained within the unique board. The controlled equipment will maintain its set points and logic regardless of centralized network communications.
• The Central Computer will provide the operator with a point of entry to view and store the data that is required for efficient system operation.
• Provisions shall be made to provide hub locations that allow for future interface of the Fire Alarm and Life Safety equipment. These hubs will be connected to the primary system backbone.
• All enclosed relays used with an indicating LED (like R.I.B’s) shall use a printed label describing its functional state, i.e. “ON to run” or “ON for alarm”.
• The Fire Digital System Controller (FDSC) shall be a device which shall monitor and control life safety devices directly connected to it.
• BAS shall monitor/control all the points and functions as listed below.
  1. Inputs monitored or alarmed and output control functions.
  2. Digital input indication signals from contacts associated with on-off, off-normal, normal or other indications initiated by making or breaking of the contacts.
  3. Digital output signals which shall be two state control outputs, except as noted, e.g., on-off, open-close, start/stop. Momentary or a maintained state shall be noted as required.
  4. Analog I/O signals which are continuously variable.
  5. The schedule shall include calculations from software of functions monitored, e.g., BTU, kilowatts, etc., if requested by the University.
  6. The schedule shall include totalization of variables within the software. This shall include totalization program requirements for on-line assignments.
• The system shall be modular to allow change of function and operation in the field by plug-in module equipment and permit software change to expand the system capacity on full on-line basis.
• The system shall include isolation, shielding, or filtering to eliminate interference from all external sources including, but not limited to radio signals, power conductors, etc.
• Networking:
  1. Each control unit shall be capable of sharing point information with other such units, such that control sequences or control loops executed at one control unit may receive input signals from sensors connected to other units within the network. If the network communication link fails or the originating control unit malfunctions, the control loop shall continue to function using the last value received from the failed control unit.
  2. Failure of one control unit shall have no other effect upon any of the other units in the network.
• The following is a list of manufacturers of materials and equipment that are known to have product that is Native BACnet at all levels of device communications. Only these manufacturers are considered acceptable. Manufacturers advocating gateways at different levels of their product line are not acceptable. Gateways and alternative methods of network communication are only considered acceptable when provided by the manufacturer of primary plant systems such as Variable Frequency Drives, Boilers, Packed Rooftop Equipment, Chillers, etc.

MATERIAL OR EQUIPMENT		MANUFACTURER
Native BACnet Temperature Control Systems		Alerton Technologies, Tridium, Automated Logic

• Each Control Panel shall be capable of independently performing the following routines as a minimum:
  1. System graphic
  2. System on/off indication
  3. System day/night mode
  4. Supply fan on/off indication
  5. Return fan on/off indication
  6. Heating coil pump on/off indication
  7. Outside air temperature indication
  8. Mixed air temperature indication
  9. Fan discharge air temperature indication
  10. Fan discharge temperature control point adjustment
  11. Supply static pressure indication
  12. Supply static pressure control point adjustment
  13. Humidity sensor
  14. Enthalpy sensor
  15. System on/off auto switch position.
  16. System day/night/auto switch position.
  17. Supply fan on/off switch position.
  18. Return fan on/off/auto switch position.
  19. Heating coil pump on/off switch position.
  20. Time of day scheduling.
  21. Start/stop time optimization.
  22. Peak demand limiting.
  23. Duty cycling (temperature and/or time based).
  24. Enthalpy optimization.
  25. Supply air reset.
  26. Chilled water reset.
  27. Hot water reset based on outdoor air temperature.
  28. Event initiated programs.
  29. Trending
• The Control Panel shall support the creation, modification or removal of control algorithms while operating. The DSC shall be programmed using a sequential, numbered-statement programming language.

• The Control Panel shall allow custom control algorithms to be created:
  1. Locally within the Control Panel.
  2. Centrally within the front end computer and downloaded.
  3. By a personal computer (IBM compatible) and downloaded.
• Front End Computer System.
  1. The software shall include a real-time multi-user operating system.
  2. Operator Interface with the system will have as a minimum the following:
     1. Operator access
     2. User control over system configuration
     3. Facility management functions
     4. Energy management control functions
  3. Each category of software shall consist of interactive software modules utilizing standard software packages available on the open market and not proprietary to any one equipment provider. Each module shall have an associated priority level and shall execute as determined by the program controller as defined in the real-time operating system.
  4. The Software shall use English language for each point identification. These shall be full English words with the option to abbreviate at the user's discretion. The system shall accept multiple English language identifiers as well as foreign language identifiers for each point on the system. These shall be known as "User Names". In addition, system formatting shall be provided which shall allow for software grouping of related points.
  5. The system shall operate on a Format basis, regardless of the manner of hardware configuration in which data is acquired. A system of points shall consist of a logical grouping of data points related to a piece of mechanical equipment, and energy distribution system, or an architectural area. For example, in some cases it may be desired to display a space temperature with its associated air handling unit, and in other cases to display all space temperatures on a floor or in a building as a single system.
  6. The Software shall allow such determinations to be made without regard to physical hardware location(s). Likewise, the system shall accommodate future changes of system grouping and operations without field hardware changes.
  7. User names, point descriptors, and engineering units shall be operator definable on a per point basis. Systems which use fixed vendor-supplied look-up tables are not be acceptable.
• User Control Over Configuration:
  1. The intent of this standard is to provide a system which shall allow the University to independently do its own modifications to the system.
  2. All changes shall be done utilizing standard procedures and must be capable of being done while the system is on-line and operational. To aid an operator, intuitive operator interfaces shall be employed. The operator shall be required to simply click on the set-point, logical point or other controlled parameter to modify the system.
  3. The system shall have the minimum capability to allow the University to do the following:
     1. Add and delete points.
     2. Modify any point parameter.
     3. Change, add or delete English language descriptors.
     4. Change, add or delete engineering units.
     5. Change, add or delete points in start/stop programs, trend logs, etc.
     6. Select analog alarm limits.
     7. Adjust analog differentials.
     8. Create custom relationships between points.
  4. The BAS software shall support an unlimited number of nodes on the communication network.
  5. Once the hardware terminal devices are installed, the operator shall be able to modify the system software to accommodate the new or reconfigured devices.
  6. It shall be possible to limit the capabilities of any console on the system.
  7. It shall be possible to further assign on a per point basis the ability to command, display or alarm a point at a specific workstation.
• Provision for facilities management functions shall be provided as a minimum.
• Provision for Energy Management Control Functions shall be provided as a minimum for the purpose of optimizing energy consumption while maintaining occupant comfort.
• Communication Software:
  1. The system shall include a software for communication between all systems. The capabilities of this software shall include program to program communication, network virtual terminal capability, file transfer, remote command/batch file submission and execution, remote resource access, downline system loading, downline task loading, and upline dumping.
  2. The software shall be consistent with ASHRAE Standard 135 and support the required BACnet system functionality as defined in the Standard.
• Digital Systems Controller (DSC):
  1. The units shall maintain the programming and algorithms necessary to control independent mechanical systems. The Digital System Controller shall communicate over a local LAN connected to the System LAN at the individual control panels.
  2. These units shall connect directly to control unit through a local area network, providing additional local digital point capacity. All control programs shall reside within the associated control unit.
  3. Digital System Network (DSN):
     1. Network Controllers shall be stand-alone, multi-tasking, multi-user, real-time digital control processors consisting of modular hardware with plug-in enclosed processors, communication controllers, power supplies and input/output point modules.
     2. Each Controller shall have sufficient memory to support its own operating system and databases, including:
        1. BAS Control processes
        2. Energy management applications
        3. Alarm management applications including custom alarm messages for each level alarm for each point in the system.
        4. Historical/trend data for points specified
        5. Maintenance support applications
        6. Custom processes
        7. Operator I/O
        8. Dial-up communications
     3. Each DDC Controller shall support any combination of industry standard inputs and outputs.
     4. As indicated in the point I/O schedule, the operator shall have the ability to manually override automatic or centrally executed commands at the DDC Controller via local, point discrete, on-board hand/off/auto operator override switches for digital control type points and gradual switches for analog control type points.
        1. Switches shall be mounted either within the DDC Controllers key-accessed enclosure, or externally mounted with each switch keyed to prevent unauthorized overrides.
     5. DDC Controllers shall provide local LED status indication for each digital input and output for constant, up-to-date verification of all point conditions without the need for an operator I/O device. Status indication shall be visible without opening the panel door.
     6. Each DDC Controller shall continuously perform self-diagnostics, communication diagnosis and diagnosis of all panel components. The DDC Controller shall provide both local and remote annunciation of any detected component failures, low battery conditions or repeated failure to establish communication.
     7. Isolation shall be provided at all peer-to-peer network terminations, as well as all field point terminations to suppress induced voltage transients consistent with IEEE Standards 587-1980, or latest edition.
     8. In the event of the loss of normal power, there shall be an orderly shutdown of all DDC Controllers to prevent the loss of database or operating system software. Non-volatile memory shall be incorporated for all critical controller configuration data and battery backup shall be provided to support the real-time clock and all volatile memory for a minimum of 72 hours.
        1. Upon restoration of normal power, the DDC Controller shall automatically resume full operation without manual intervention.
        2. Should DDC Controller memory be lost for any reason, the user shall have the capability of reloading the DDC Controller via the local port, via telephone line dial-in or from a network workstation PC.
• Data Trunk:
  1. Transmission Network:
     1. The system shall use an intelligent distributed communication network.
     2. Transmission
        1. Network communications shall be of the ASHRAE 135 Standard
• Definitions: The following abbreviations, acronyms and definitions are used in addition to those details found elsewhere in Contract Documents.

Actuator:	Control device to provide motion of valve or damper in response to control signal.
AI:	Analog Input
AO:	Analog Output
Analog:	Continuously variable state over stated range of values
ATC:	Automatic Temperature Control
Auto-Tune:	Software routine used to adjust tuning parameters based on historical data.
BAS:	Building Automation System
BCU:	Building Control Unit
CAV:	Constant Air Volume
CGS:	Color Graphic Software
DDC:	Direct Digital Control
DDCP:	Direct Digital Control Panel
Discrete:	Binary or digital state
DI:	Discrete Input
DO:	Discrete Output
EMCS:	Energy Management and Control System (Same as BAS)
FC:	Fail Closed position of control device or actuator. Device moves to closed position on loss of control signal or energy source.
FMS:	Facility Management System linking two or more BAS
FO:	Fail Open position of control device or actuator. Device moves to open position on loss of control signal or energy source.
HCP:	Host Control Panel
I/P:	Current to pneumatic transducer
Instrument:	Device used for sensing input parameters or used for actuation
LAN:	Local Area Network
LCD:	Liquid Crystal Display
LCP:	Local Control Processor
Modulating:	Movement of a control device through an entire range of values proportional to infinitely variable input values.
Motorized:	Control device with actuator.
NC:	Normally Closed position of switch after control signal is removed or normally closed position of manually operated valves or dampers.
NCP:	Network Control Processor
NO:	Normally Open position of switch after control signal is removed or normally open position of manually operated valves or dampers.
Node:	DDCP, user workstation, or other control device connected to communication's network.
Operator:	Same as actuator.
PC:	Personal Computer
Peer-to-Peer:	Mode of communication between controllers in which each device connected to network has equal status and each shares its database values with all other devices connected to network.
P:	Proportional control, control mode with continuous linear relationship between observed input signal and final controlled output element.
PHP:	Public Host Protocol
PI:	Proportional - Integral control, control mode with continuous proportional output plus additional change in output based on both amount and duration of change in controlled variable (Reset control).
PID:	Proportional - Integral - Derivative control, control mode with continuous correction of final controlled output element versus input signal based on proportional error, its time history (reset), and rate at which its changing (derivative).
Point:	Analog or discrete instrument with addressable database value.
PUC:	Programmable Unitary Controller
PUP:	Public Unitary Protocol
RAM:	Random Access Memory
RCU:	Remote Control Unit
Self-Tune:	Same as Auto-Tune
Solenoid:	Electric two-position actuator.
TCC:	Temperature Control Contractor (Same as Control Contractor)
TCP:	Temperature Control Panel
VAV:	Variable Air Volume

• The HVAC temperature control hardware will be native BACnet. Native BACnet means that the database objects in the controller can be seen by other BACnet systems, and data can be exchanged between other BACnet devices without the need for a gateway.
• The primary building local area network (LAN) will be based upon the ISO 8802-3 ethernet standard. Under no circumstances will the customer's building LAN be subject to failure and/or abuse. All BACnet devices that reside on the LAN must support the BACnet broadcast management device (BBMD) scheme. Global broadcasting will not be permitted without the use of a BBMD.
• The primary campus wide area network (WAN) is the internet at the University of Illinois at Chicago. The BACnet system will be capable of Internet Protocol (IP) communications to the main control panel, the application specific controllers and down to the room thermostat. BACnet/IP or Annex J will be considered the basis of design.
• The University of Illinois at Chicago main platform is Tridium. The user graphics shall be distributed among each building's individual JACE supervisors/controllers, with a central server used primarily for long term trend storage and as a user gateway across campus systems.  Each building may have a different approved manufacturers' field controllers as VAVs or fan controllers, etc; however these systems shall be integrated back into a tridium JACE as a supervisor and web server engine.
• Internet Protocol Address (IP) will be assigned by the University at the building location.
• All Building Automation Systems must provide for remote communications to the Central Operations Office of the Operating Engineer on both the East and West Campuses.
• All LON wiring must be 22 AWG UTP level 4.
• All BACnet wiring must be shielded 22 AWG  level 4.
• Acceptable Control Contractors:
  1. Tridium
  2. Alerton Technologies
  3. Automated Logic
• Systems Description:
  1. System shall be pneumatic, electric or electronic.
  2. Control system shall be direct digital control (DDC).
  3. Damper and valve actuators for major equipment in mechanical rooms shall be pneumatic. Actuators for remote devices located in spaces outside of mechanical rooms shall be electronic type.
  4. Control to be based on BAS architecture consisting of communication network, user workstations, modular designed DDCPs with all points addressable and modifiable from user workstations or from master DDCP user interface panels. BAS shall be fully stand-alone and shall communicate via BACnet/Ethernet/Internet communications protocol. System components shall be fully BACnet/Ethernet/Internet compliant without the use of gateways. System must be able to communicate with the main platform (Orcaview) at the University of Illinois at Chicago via Protocol Address (IP) will be assigned by the University at the building location.
  5. System shall support user workstations as specified and shall be capable of additional workstations, limited only by systems maximum node capacity.
  6. System intelligence shall be such that user workstation(s) can be used for programming controls, performing analysis on filed data, perform trending of user defined inputs, generating maintenance and operation reports, providing permanent storage for programs and data, and the ability to connect to the Internet.
  7. Safety devices shall function in both auto and hand modes on starter.
• Recommended instrument and control conductor color code shall be as follows:

Type	Color
120 VAC control signal	Red
120 VAC instrument line power	Black
120 VAC instrument line neutral	White
24 VAC control signal	Yellow
24 VAC instrument line power	Brown
24 VAC instrument line neutral	Orange
Grounds	Green
24 + VDC instrument signal	Black
24 - VDC instrument signal	White or clear
RTD V+	Black
RTD V-	White
RTD compensation	Red

• Electric signal cables from electronic transmitters to receivers and from controllers to final control elements shall be continuously shielded. Shields shall be grounded at power source end only and floated at the other end.
• BAS Network Communication Cable:
  1. BAS network communication cable shall not be spliced.

• Direct Digital Control Panels (DDCP's) shall be microprocessor based, field programmable controllers, capable of performing control and energy management functions, and shall be UL listed as Signaling Systems. Each DDCP shall include its own microprocessor, power supply, input/output modules, and termination modules as required to perform its intended function.

• DDCP shall receive discrete electrical or analog electronic field input signals, convert signals for use by controller, perform control sequences, convert controller information into output signals, and provide control output signals to actuators and field control device. All inputs and outputs, including communication connections, shall be electrically or optically isolated from controller.
• DDCP with analog input modules shall be capable of accepting any form of linear or non-linear voltage (0-5 VDC or 0-10 VDC), current (4-20 mA) or resistive input (0-1000 ohm).
• DDCP with discrete input modules shall be capable of accepting discrete inputs from any device with isolated, dry-type contacts (no grounds or no voltage) of either normally open (NO) or normally closed (NC) configuration.
• Input modules shall be capable of interfacing with pulsed output type sensors.
• DDCP shall have capability to scale, offset, and display proper analog value without field hardware modification. DDCP shall convert analog input signals to digital values (A/D conversion) and convert digital values to analog outputs (D/A conversion) for modulating control purposes.
• Failsafe operation shall be provided such that BAS failures result in immediate return to local control. If the DDCP uses database values from other DDCP and the communication network fails or malfunctions, control loop outputs shall continue to function using last value received from BAS.
• DDCP shall have ability to interface and communicate with Host Control Panel (HCP) through a dedicated network. DDCP shall be fully operable from and have all points and functions available to centrally alarm at any DDCP or PC workstation connected to a BAS network.
• Three types of DDCP's are allowed, Building Control Units (BCU's), Remote Control Units (RCU's), and Application Specific Controllers (ASC's).
• BCU's are defined as having capabilities of direct connection to high speed Local Area Network (LAN) (greater than 500 kilobaud), serve as communications hub for other BCU's on slower speed LAN, and have sufficient processor capabilities and RAM to implement all types of custom software applications. BCU's shall have serial type input/output (I/O) ports to directly support operator workstations (portable PCs), standard ASCII dumb terminals, modems, and all types of printers.
• BCU's shall have uninterrupted real time clocks capable of time of day, week, and year information to the system as needed to perform software functions. Clock shall be programmed to reset twice a year to allow for Daylight Savings Time. Clocks in multiple BCU's shall be synchronized automatically to match designated BCU or workstation. Accuracy shall be within 1 second per day minimum.
• BCU batteries shall maintain all volatile memory and real time clocks for a period of at least 72 hours during power failure. Batteries shall be maintenance free and have minimum life of 2 years. When power has been restored, the following shall occur automatically:
  1. Orderly startup of all controlled equipment (user defined).
  2. Continuation of all control algorithms.
  3. Data base revision.
  4. Log times of power interruption and restoration.
  5. Battery recharging.
• RCU's are defined as being the same as BCU's but without high-speed LAN capabilities or I/O ports. RCU's shall communicate with BCU's and other RCU's via low/medium speed network or direct serial or parallel data bus interface.
• ASC's are defined as having standard software burned into EPROM, set points in EEPROM or RAM maintained by battery, and are designed to handle specific types of control sequences. ASC's shall be capable of communicating to BAS network via low/medium speed network connected to BCU's.
• All software and hardware to be covered by site license for a minimum of 30 users. Adding to or modification of the basic system should not require additional licenses.
• BCU/RCU Software shall contain:
  1. Program modules for performing energy management control functions such as time of day change of database values (programmed start/stop, temperature setbacks, etc.), supply air temperature reset based on space load demand, economizer control, optimum start/stop based on current indoor and outdoor psychometrics, duty cycling and client tailored programs required for special applications such as VAV fan matching and supply fan control, enthalpy control, intermediate season or "dead band" control, totalizing, and holiday programming.
  2. Manufacturer's standard operating system for real time control of system interactions, including database information requests/transfers by system hardware or by operators. Operating system shall also have the following additional capabilities (given operator has appropriate security access level):
     1. Display any database (point) value including measured values, controlled variables, set points, gain factors, and any other adjustable parameter.
     2. Change or override any database value.
     3. Error detection, correction, re-transmission of database values, arithmetic or logical faults.
     4. Alarm reporting including sending alarms to remote workstations on network or by modem.
     5. Alarm buffer to retain all alarms in order of importance without losing any alarms.
     6. Creating and displaying historical trend logging any value limited only by available memory.
     7. Create new variable database values (soft points) based on arithmetic calculation (including summation or totalizing) on other database values.
     8. Add new hardware points without overall BAS shutdown.
• All hardware/software to update database in less than 1 second for fast-acting control loops such as pressure control, air or water volume control, and air handling unit temperature control, or 10 seconds or less for all other control loops.
• Graphics to be generated shall include, but not be limited to:
  1. Site Plans, including each building, building name, and status of all exterior points such as lighting, etc.
  2. Overall building plan of each building. Indicate location of mechanical rooms and areas served by each air handling unit.
  3. Voltage and current values shall be displayed for all motors 50 HP and above. Each shall be displayed next to the motor graphic on the display screens.
  4. Schematic type graphics for:
     1. Each air handling system
     2. Supply fan control loop
     3. Cooling coil control loop
     4. Heating coil control loop
     5. Humidifier control loop
     6. Damper control loops
     7. Steam system showing all components
     8. Each hot water system showing all components.

253000 INTEGRATED AUTOMATION INSTRUMENTATION AND TERMINAL DEVICES

• Wall mounted space thermostat enclosure shall have concealed sensing element and exposed set point adjustment.
• Unless otherwise stated, space thermostat covers shall be brushed aluminum or brushed nickel.
• Temperature Low Limit Switches (Freezestats):
  1. Electric 2 position type with temperature sensing element and manual reset. Controls shall be capable of opening circuit if any one foot length of sensing element is subject to temperature below setting.
  2. Sensing element shall not be less than one lineal foot per square foot of coil surface areas. Temperature switch set point is 38°F.
  3. Where multiple switches are required, each switch shall have a separate point names in the BAS. Each alarm in BAS shall indicate which temperature low limit has opened or tripped.
• Pressure Differential Switches (Air Systems):
  1. Pressure differential switches for air systems shall have pressure rating of at least 1-1/2 times the systems pressure.
• Pressure Differential Switches (Water Systems):
  1. Pressure differential switches for water systems shall be rated for 1-1/2 times system pressure. Chilled water pressure differential switches shall be provided with totally sealed vapor tight switch enclosure. Differential pressure switches to have 3-valve manifold for servicing.
• Level Switches (Ultrasonic Gap Sensor):
  1. Radio Frequency (RF) type point level probe with stainless steel probe and DPDT snap action relay contacts to meet intended use. Probe shall have a machined gap in the probe to sense presence or absence of water or other fluid. Probe length shall be determined by application.
• Analog Electronic Instrumentation: The following shall be standard off-the-shelf, commercially available and applicable for use with electronic control/monitoring systems.
  1. Space Temperature Sensors
  2. Duct Mounted, Insertion or outside Temperature Sensors
  3. Direct Insertion Temperature Sensors
  4. RTD Temperature Transmitters
  5. Space Humidity Sensors/Transmitters
  6. Duct Mounted Humidity Sensors/Transmitters
  7. Ducted Air System Static Pressure and Differential Pressure (Velocity) Transmitters
  8. Pressure/Differential Pressure Transmitter
  9. Vortex Flowmeter/Transmitter (Steam)
  10. Capacitance Type Level Transmitter
  11. Pressure (E-P) Transducers
  12. Carbon Monoxide Monitor