23_09_53_Automatic_Temperature_Controls.doc

DOC document 157 KB Posted

Attached to
Install Bridge Crane B302 Federal contract opportunity
Solicitation number
FA6656-16-B-0001
Issued by
Department of the Air Force Reserve Command

About this file

Specification Section 23 09 53 Automatic Temperature Controls

View the file

Other files for this federal contract opportunity

Other files attached to Install Bridge Crane B302, newest first.
File Type Posted
Amendment_5_B302_Install_Crane.docx DOCX document
Revised_Drawing_M1.2.pdf PDF
Amendment_4_B302_Install_Crane.docx DOCX document
Amendment_3_B302_ZQEL_15-0005-041216.docx DOCX document
QandAs_B302_ZQEL_15-0005-041216.docx DOCX document
Site_Visit_Agenda_and_Attendees_B302.pdf PDF
B302amendment1.docx DOCX document
SolicitationB302.docx DOCX document
WagesAttachment1B302.docx DOCX document
ZQEL_15-0002_Drawings_11.18.15.zip ZIP file
ZQEL_15-0002_Specifications_11.18.15.zip ZIP file
SolicitationB302.docx DOCX document
ResQuesAttachment4B302.docx DOCX document
Show all 13

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

910th Airlift Wing

USAFR ZQEL 15-0002

Youngstown Air Reserve Station

Install Bridge Crane, B302

SECTION 23 09 53 – AUTOMATIC TEMPERATURE CONTROLS

PART 1 – GENERAL

1.1 RELATED DOCUMENTS

A. All work of this Division shall be coordinated and provided by the contractor’s Building Automation System (BAS) Sub-Contractor.

B. The work of this Division shall be scheduled, coordinated, and interfaced with the associated work of other trades. Reference the Division 23 Sections for details.

C. The work of this Division shall be as required by the Specifications, Drawings, and Point Schedules.

D. If the BAS Contractor believes there are conflicts or missing information in the project documents, the Contractor shall promptly request clarification and instruction from the design team.

1.2 BAS DESCRIPTION

E. The Building Automation System (BAS) shall be compatible with BACnet based Johnson Controls control system and compatible with their enterprise IT system as installed on Youngstown Reserve Base for overall coordination, monitoring and control by the BASE Engineer or his staff. Any compatible equivalent system shall be submitted 15 days in advance for Architect and Engineer and Base Project Manager’s approval, no deviation or variance 100% compliance required. This functionality shall extend to the demolition of any controls for existing Energy Recovery Unit and reuse of any controls possible and new controls for the room with new sensors and to control new Air Handling Unit provided for Rest rooms and mechanics areas, rest room exhaust/lighting based on occupancy sensor in accordance with plans and this specification. Devices residing on the automation network located in equipment rooms and similar shall be fully IT compatible devices that mount and communicate directly on the IT infrastructure in the facility. Contractor shall be responsible for coordination with the owner’s IT staff to ensure that the BAS will perform in the owner’s environment without disruption to any of the other activities taking place. No other areas of Building Controls are included in the scope. The controls contractor will ensure that new equipment added can be operated, monitored and controlled by the Base Engineer. In case of failure of communication, local controller in the buuidling shall operate the system. This is achieved by using existing server and communication cable between the base server for energy management and the building 302. This shall consist of control systems for:

F. All points of user interface shall be on standard PCs that do not require the purchase of any special software from the BAS manufacturer for use as a building operations terminal. The primary point of interface on these PCs will be a standard Web Browser.

G. Servers shall be used for the purpose of providing a location for extensive archiving of system configuration data, and historical data such as trend data and operator transactions. All data stored will be through the use of a standard data base platform: Microsoft Data Engine (MSDE).

H. The work of the single BAS Sub-Contractor shall be as defined individually and collectively in all Sections of this Division specification together with the associated Point Sheets and Drawings.

I. The BAS work shall consist of the provision of all labor, materials, tools, equipment, already licensed JCI software, software configurations and database entries, interfaces, wiring, tubing, installation, labeling, engineering, calibration, documentation, samples, submittals, testing, commissioning, training services, permits and licenses, transportation, shipping, handling, administration, supervision, management, insurance, temporary protection, cleaning, cutting and patching, warranties, services, and items, even though these may not be specifically mentioned in these Division documents which are required for the complete, fully functional and commissioned BAS.

J. Provide a complete, neat and workmanlike installation. Use only manufacturer employees who are skilled, experienced, trained, and familiar with the specific equipment, software, standards and configurations to be provided for this Project.

K. Manage and coordinate the BAS work in a timely manner in consideration of the Project schedules. Coordinate with the associated work of other trades so as to not impede or delay the work of associated trades.

L. The BAS as provided shall incorporate, at minimum, the following integrated features, functions and services:

1. Operator information, alarm management and control functions.

2. Enterprise-level information and control access.

3. Information management including monitoring, transmission, archiving, retrieval, and reporting functions.

4. Diagnostic monitoring and reporting of BAS functions.

5. Offsite monitoring and management access.

6. Energy management

7. Standard applications for terminal HVAC systems.

8. Software Analytics Solution using Panoptix

9. Indoor Air Quality monitoring and control

1.3 QUALITY ASSURANCE

M. General

1. The Building Automation System Sub-Contractor shall be the primary manufacturer-owned branch office that is regularly engaged in the engineering, programming, installation and service of total integrated Building Automation Systems.

2. The term “manufacturer” when used to identify an automatic temperature control sub-contractor/supplier, shall mean the complete system of building energy management. Components of the completed system shall include but not being limited to, hardware equipment, engineering, wiring, installation, sequence of operations, network architecture, commissioning, training, software programming and warranty.

3. The BAS Sub-Contractor shall be a recognized national manufacturer, installer and service provider of BAS.

4. Franchised dealers or HVAC Contractors installing their own controls will not be accepted. No exceptions. Any equivalent system shall be submitted prior to bidding as per specifications for approval.

5. The BAS Sub-Contractor shall have a branch facility within a 100-mile radius of the job site supplying complete maintenance and support services on a 24 hour, 7-day-a-week basis.

6. As evidence and assurance of the contractor’s ability to support the Owner's system with service and parts, the contractor must have been in the BAS business for at least the last ten (10) years and have successfully completed total projects of at least 10 times the value of this contract in each of the preceding five years.

7. The Building Automation System architecture shall consist of the products of a manufacturer regularly engaged in the production of Building Automation Systems, and shall be the manufacturer’s latest standard of design at the time of bid.

8. All control wires shall be numbered in accordance with IEEE standards and shall match the submittal drawings.

N. Workplace Safety and Hazardous Materials

1. Provide a safety program in compliance with the Contract Documents.

2. The BAS Contractor shall have a corporately certified comprehensive Safety Certification Manual and a designated Safety Supervisor for the Project.

3.

The Contractor and its employees and subtrades comply with federal, state and local safety regulations.

4.

The Contractor shall ensure that all subcontractors and employees have written safety programs in place that covers their scope of work and that their employees receive the training required by the OSHA having jurisdiction for at least each topic listed in the Safety Certification Manual.

5.

Hazards created by the Contractor or its subcontractors shall be eliminated before any further work proceeds.

6.

Hazards observed but not created by the Contractor or its subcontractors shall be reported to either the General Contractor or the Owner within the same day. The Contractor shall be required to avoid the hazard area until the hazard has been eliminated.

7.

The Contractor shall sign and date a safety certification form prior to any work being performed, stating that the Contractors’ company is in full compliance with the Project safety requirements.

8.

The Contractor’s safety program shall include written policy and arrangements for the handling, storage and management of all hazardous materials to be used in the work in compliance with the requirements of the Authority Having Jurisdiction (AHJ) at the Project site.

9.

The Contractor’s employees and subcontractor’s staff shall have received training as applicable in the use of hazardous materials and shall govern their actions accordingly.

O. Quality Management Program

1. Designate a competent and experienced employee to provide BAS Project Management. The designated Project Manger shall be empowered to make technical, scheduling and related decisions on behalf of the BAS Contractor. At minimum, the Project Manager shall:

a. Manage the scheduling of the work to ensure that adequate materials, labor and other resources are available as needed.

b. Manage the financial aspects of the BAS Contract.

c. Coordinate as necessary with other trades.

d. Be responsible for the work and actions of the BAS workforce on site.

1.4 REFERENCES

A.

All work shall conform to the following Codes and Standards, as applicable:

1.

National Fire Protection Association (NFPA) Standards.

2. National Electric Code (NEC) and applicable local Electric Code.

3. Underwriters Laboratories (UL) listing and labels.

4. UL 864 UUKL Smoke Control

5. UL 268 Smoke Detectors.

6. UL 916 Energy Management

7. NFPA 70 - National Electrical Code.

8. NFPA 90A - Standard for The Installation of Air Conditioning and Ventilating Systems.

9. American National Standards Institute (ANSI).

10. National Electric Manufacturer’s Association (NEMA).

11. American Society of Mechanical Engineers (ASME).

12. American Society of Heating, Refrigerating and Air Conditioning Engineers (ASHRAE) and ASHRAE 62 IAQ as applicable.

13. Air Movement and Control Association (AMCA).

14. Institute of Electrical and Electronic Engineers (IEEE).

15. American Standard Code for Information Interchange (ASCII).

16. Electronics Industries Association (EIA).

17. Occupational Safety and Health Administration (OSHA).

18. American Society for Testing and Materials (ASTM).

19. Federal Communications Commission (FCC) including Part 15, Radio Frequency Devices.

20. Americans Disability Act (ADA)

21. ANSI/ASHRAE Standard 195-2004 (BACnet)

B.

In the case of conflicts or discrepancies, the more stringent regulation shall apply.

C.

All work shall meet the approval of the Authorities Having Jurisdiction at the project site.

1.5

SUBMITTALS

P. Shop Drawings, Product Data, and Samples

1. The BAS contractor shall submit a list of all shop drawings with submittals dates within 30 days of contract award.

2. Submittals shall be in defined packages. Each package shall be complete and shall only reference itself and previously submitted packages. The packages shall be as approved by the Architect and Engineer for Contract compliance.

3. Allow 15 working days for the review of each package by the Architect and Engineer in the scheduling of the total BAS work.

4. Equipment and systems requiring approval of local authorities must comply with such regulations and be approved. Filing shall be at the expense of the BAS Contractor where filing is necessary. Provide a copy of all related correspondence and permits to the Owner.

5. Prepare an index of all submittals and shop drawings for the installation. Index shall include a shop drawing identification number, Contract Documents reference and item description.

6. The BAS Contractor shall correct any errors or omissions noted in the first review.

7. At a minimum, submit the following:

a. BAS network architecture diagrams including all nodes and interconnections.

b. Systems schematics, sequences and flow diagrams.

c. Points schedule for each point in the BAS, including: Point Type, Object Name, Expanded ID, Display Units, Controller type, and Address.

d. Samples of Graphic Display screen types and associated menus.

e. Detailed Bill of Material list for each system or application, identifying quantities, part numbers, descriptions, and optional features.

f. Control Damper Schedule including a separate line for each damper provided under this section and a column for each of the damper attributes, including: Code Number, Fail Position, Damper Type, Damper Operator, Duct Size, Damper Size, Mounting, and Actuator Type.

g. Control Valve Schedules including a separate line for each valve provided under this section and a column for each of the valve attributes: Code Number, Configuration, Fail Position, Pipe Size, Valve Size, Body Configuration, Close off Pressure, Capacity, Valve CV, Design Pressure, and Actuator Type.

h. Room Schedule including a separate line for each VAV box and/or terminal unit indicating location and address and room thermostat specifics.

i. Details of all BAS interfaces and connections to the work of other trades.

j. Listing of all read and or write points derived via interfaces to mechanical system components as required per project specifications, sequences of operation, points list(s), and/or required for correct systems operation and functionality. Points shall be identified as to point type (AI, BI, AO, DO, AV, DV), point source (read, write, commandable), interface type (Lon BACnet, N2, etc.) point ID in BAS and point ID in mechanical system, mechanical system source (VFD, RTU, etc.), point (object) name (% speed, fan status, cws temp, etc.) and point description (speed of motor, fan on, chilled water supply temperature, etc.)

k.

Product data sheet section with an index identifying each product utilized in the installed BAS system and product data sheet(s) for each product. The index shall individually list each product with the associated numerically sequenced page number(s) of the product data sheets. For all products including software, provide product data sheet(s) or marked catalog pages that include part number, photo, complete specifications and numerically sequenced page number(s) referenced in the index.

1.6

RECORD DOCUMENTATION

Q. Operation and Maintenance Manuals

1. Three (3) copies of the Operation and Maintenance Manuals shall be provided to the Owner's Representative upon completion of the project. The entire Operation and Maintenance Manual shall be furnished on Compact Disc media, and include the following for the BAS provided:

a. Table of contents.

b. As-built system record drawings. Computer Aided Drawings (CAD) record drawings shall represent the as-built condition of the system and incorporate all information supplied with the approved submittal.

c. Manufacturer’s product data sheets or catalog pages for all products including software.

d. System Operator’s manuals.

e. Archive copy of all site-specific databases and sequences.

f. BAS network diagrams.

g. Interfaces to all third-party products and work by other trades.

2. The Operation and Maintenance Manual CD shall be self-contained, and include all necessary software required to access the product data sheets. A logically organized table of contents shall provide dynamic links to view and print all product data sheets. Viewer software shall provide the ability to display, zoom, and search all documents.

1.7 WARRANTY

R. Standard Material and Labor Warranty:

1. Provide a one-year labor and material warranty on the BAS.

2. If within twelve (12) months from the date of final payment, upon written notice from the owner, it is found to be defective in operation, workmanship or materials, it shall be replaced, repaired or adjusted at the option of the BAS Contractor at the cost of the BAS Contractor.

3. Maintain an adequate supply of materials within 100 miles of the Project site such that replacement of key parts and labor support, including programming. Warranty work shall be done during BAS Contractor’s normal business hours.

PART 2 – PRODUCTS

A. The design basis is TRANE Controlling Roof Top Unit with air distribution as shown on drawings with Greenheck Exhaust fan interlocked with the RTU operation. TRANE Unit or approved equal manufacturer unit Controller will provide BACNet IP compatible output to communicate with existing JCI BAS System at the base and will coordinate the effort with JCI controls contractor currently under contract to operate and maintain the system. The General Contractor will ensure that complete system when delivered meets the point lists and sequence of operation and will submit documents for approval. Other than JCI and TRANE providing their respective controls, any other manufacturer submitting bids shall seek prior approval in writing and shall submit complete plans, specifications and drawings minimum 10 days prior to Bid Opening. TRANE and JCI can submit other items under Division 23 for approval. The decision of Youngstown Air Reserve Station contracting officer or his/her authorized Technical Representative for equivalent approval shall be final. Shall TRANE provide any controls beyond roof top unit, it shall ensure that Joseph M. Genova JCI representative in Youngstown, Ohio 44509 account executive of BASE SYSTEM is contacted and time is allocated for full coordination. Joseph can be reached at Tel: 330-270-4391or Cell: 330-502-5633. A wall mounted thermostat/sensor with manual override will be provided in each area where Indoor Air Quality is being improved. No other hardware for in building operation is required for this area and existing such system if any shall be used for this area including capability of graphic inter phase if available for this building. Match with the existing.

2.1 Large GENERAL DESCRIPTION

A.

The Building Automation System (BAS) shall use an open architecture and fully support a multi-vendor environment to accommodate TRANE, Daikin and others using BACNet or existing protocols. To accomplish this effectively, the BAS shall support open communication protocol standards and integrate a wide variety of third-party devices and applications. The system shall be designed for use on the Internet, or intranets using off the shelf, industry standard technology compatible with other owner provided networks.

S. The Building Automation System shall consist of the following:

1. Standalone Network Automation Engine(s)

2. Field Equipment Controller(s)

3. Input/Output Module(s)

4. Local Display Device(s)

5. Distributed User Interface(s)

6. Network processing, data storage and communications equipment

7.

Diagnostic Systems for Integrated Automation

8. Other components required for a complete and working BAS T. System architectural design shall eliminate dependence upon any single device for alarm reporting and control execution. The failure of any single component or network connection shall not interrupt the execution of control strategies at other operational devices.

U. The BAS System supplied shall be latest release of the manufacturing company that is downward compatible, where necessary for compatibility the existing software/hardware may have to be upgraded and is included in the scope of this project. The purpose is to provide 100% compatible operating system with whole base buildings operating seamlessly efficient as designed.

V. Acceptable Manufacturers

1. Basis of Design:

Johnson Controls; Contact Joe Genova @ 330-270-4391

TRANE Commercial Systems; Contact Mike Forshaw @ 614-406-6084

2.

The BAS specifications below are based on JCI specifications however TRANE Commercial Control System standard based on BACNet open protocol provided by the manufacturer and coordinated with Youngstown Air Reserve Station base engineer, their maintenance and operations contractor and or JCI that operates the system so that complete system is operated smoothly will be acceptable as long as all time for coordination is included in the costs and system submittal meets all points and sequence of operation as per drawings and specifications and is pre-approved.

2.2.

BAS Architecture

A.

Automation Network

1.

The automation network shall be based on a PC industry standard of Ethernet TCP/IP. Where used, LAN controller cards shall be standard “off the shelf” products available through normal PC vendor channels.

2.

The BAS shall network multiple user interface clients, automation engines, system controllers and application-specific controllers. Provide application and data server(s) as required for systems operation.

3.

The automation network shall be capable of operating at a communication speed of 100 Mbps, with full peer-to-peer network communication.

4.

Network Automation Engines (NAE) shall reside on the automation network.

5.

The automation network will be compatible with other enterprise-wide networks. Where indicated, the automation network shall be connected to the enterprise network and share resources with it by way of standard networking devices and practices.

B.

Control Network

1.

Network Automation Engines shall provide supervisory control over the control network and shall support the following communication protocol:

a.

BACnet Standard MS/TP Bus Protocol ASHRAE SSPC-135, Clause 9.

2.

Control networks shall provide either “Peer-to-Peer,” Master-Slave, or Supervised Token Passing communications, and shall operate at a minimum communication speed of 9600 bauds.

3.

DDC Controllers shall reside on the control network.

4.

Control network communication protocol shall be BACnet Standard MS/TP Bus Protocol ASHRAE SSPC-135.

5.

A BACnet Protocol Implementation Conformance Statement shall be provided for each controller device (master or slave) that will communicate on the BACnet MS/TP Bus.

6.

The Conformance Statements shall be submitted 10 days prior to bidding.

C.

Integration

1.

BACnet Protocol Integration – BACnet a.

The neutral protocol used between systems will be BACnet over Ethernet and comply with the ASHRAE BACnet standard 135-2003.

b.

A complete Protocol Implementation Conformance Statement (PICS) shall be provided for all BACnet system devices.

c.

The ability to command, share point object data, change of state (COS) data and schedules between the host and BACnet systems shall be provided.

2.3

USER INTERFACE

A.

Dedicated Web Based User Interface

1.

Where indicated on plans the BAS Contractor shall provide and install a personal computer for command entry, information management, network alarm management, and database management functions. All real-time control functions, including scheduling, history collection and alarming, shall be resident in the BAS Network Automation Engines to facilitate greater fault tolerance and reliability.

2.

Dedicated User Interface Architecture – The architecture of the computer shall be implemented to conform to industry standards, so that it can accommodate applications provided by the BAS Contractor and by other third party applications suppliers, including but not limited to Microsoft Office Applications. Specifically, it must be implemented to conform to the following interface standards.

a.

Microsoft Internet Explorer for user interface functions b.

Microsoft Office Professional for creation, modification and maintenance of reports, sequences other necessary building management functions c.

Microsoft Outlook or other e-mail program for supplemental alarm functionality and communication of system events, and reports.

d.

Required network operating system for exchange of data and network functions such as printing of reports, trends and specific system summaries.

1. Operating System Software

a. Windows 2000 Professional or newer.

b. Where user interface is not provided via browser, provide complete operator workstation software package, including any hardware or software keys. Include the original installation disks and licenses for all included software, device drivers, and peripherals.

c. Provide software registration cards to the Owner for all included software.

B.

Distributed Web Based User Interface

1.

All features and functions of the dedicated user interface previously defined in this document shall be available on any computer connected directly or via a wide area or virtual private network (WAN/VPN) to the automation network and conforming to the following specifications.

2.

The software shall run on the Microsoft Internet Explorer (10.0 or higher) browser.

C.

User Interface Application Components

1.

Operator Interface a.

An integrated browser based client application shall be used as the user operator interface program.

d. All Inputs, Outputs, Setpoints, and all other parameters as defined within Part 3, shown on the design drawings, or required as part of the system software, shall be displayed for operator viewing and modification from the operator interface software.

e. The user interface software shall provide help menus and instructions for each operation and/or application.

f. All controller software operating parameters shall be displayed for the operator to view/modify from the user interface. These include: setpoints, alarm limits, time delays, PID tuning constants, run-times, point statistics, schedules, and so forth.

g. The Operator Interface shall incorporate comprehensive support for functions including, but not necessarily limited to, the following:

User access for selective information retrieval and control command execution

Monitoring and reporting

Alarm, non-normal, and return to normal condition annunciation

Selective operator override and other control actions

Information archiving, manipulation, formatting, display and reporting

BAS internal performance supervision and diagnostics

On-line access to user HELP menus

On-line access to current BAS as-built records and documentation

Means for the controlled re-programming, re-configuration of BAS operation and for the manipulation of BAS database information in compliance with the prevailing codes, approvals and regulations for individual BAS applications.

h. The operation of the control system shall be independent of the user interface, which shall be used for operator communications only. Systems that rely on an operator workstation to provide supervisory control over controller execution of the sequences of operations or system communications shall not be acceptable.

2.

Navigation Trees a.

The system will have the capability to display multiple navigation trees that will aid the operator in navigating throughout all systems and points connected. At minimum provide a tree that identifies all systems on the networks.

b.

Provide the ability for the operator to add custom trees. The operator will be able to define any logical grouping of systems or points and arrange them on the tree in any order. It shall be possible to nest groups within other groups. Provide at minimum 5 levels of nesting.

c.

The navigation trees shall be “dockable” to other displays in the user interface such as graphics. This means that the trees will appear as part of the display, but can be detached and then minimized to the Windows task bar or closed altogether. A simple keystroke will reattach the navigation to the primary display of the user interface.

3.

Alarms a.

Alarms shall be routed directly from Network Automation Engines to PCs and servers. It shall be possible for specific alarms from specific points to be routed to specific PCs and servers. The alarm management portion of the user interface shall, at the minimum, provide the following functions:

Log date and time of alarm occurrence.

Generate a “Pop-Up” window, with audible alarm, informing a user that an alarm has been received.

Allow a user, with the appropriate security level, to acknowledge, temporarily silence, or discard an alarm.

Provide an audit trail on hard drive for alarms by recording user acknowledgment, deletion, or disabling of an alarm. The audit trail shall include the name of the user, the alarm, the action taken on the alarm, and a time/date stamp.

Provide the ability to direct alarms to an e-mail address or alphanumeric pager. This must be provided in addition to the pop up window described above. Systems that use e-mail and pagers as the exclusive means of annunciating alarms are not acceptable.

Any attribute of any object in the system may be designated to report an alarm.

b.

The BAS shall annunciate diagnostic alarms indicating system failures and non-normal operating conditions c.

The BAS shall annunciate application alarms at minimum, as required by Part 3.

4.

Reports and Summaries a.

Reports and Summaries shall be generated and directed to the user interface displays, with subsequent assignment to printers, or disk. As a minimum, the system shall provide the following reports:

All points in the BAS All points in each BAS application

All points in a specific controller

All points in a user-defined group of points

All points currently in alarm

All points locked out

All BAS schedules

All user defined and adjustable variables, schedules, interlocks and the like.

b.

Summaries and Reports shall be accessible via standard UI functions and not dependent upon custom programming or user defined HTML pages.

c.

Selection of a single menu item, tool bar item, or tool bar button shall print any displayed report or summary on the system printer for use as a building management and diagnostics tool.

d.

The system shall allow for the creation of custom reports and queries via a standard web services XML interface and commercial off-the-shelf software such as Microsoft Access, Microsoft Excel, or Crystal Reports.

5.

Schedules a.

A graphical display for time-of-day scheduling and override scheduling of building operations shall be provided. At a minimum, the following functions shall be provided:

Weekly schedules

Exception Schedules

Monthly calendars.

b.

Weekly schedules shall be provided for each group of equipment with a specific time use schedule.

c.

It shall be possible to define one or more exception schedules for each schedule including references to calendars d.

Monthly calendars shall be provided that allow for simplified scheduling of holidays and special days for a minimum of five years in advance. Holidays and special days shall be user-selected with the pointing device or keyboard, and shall automatically reschedule equipment operation as previously defined on the exception schedules.

e.

Changes to schedules made from the User Interface shall directly modify the Network Automation Engine schedule database.

Schedules and Calendars shall comply with ASHRAE SP135/2003 BACnet Standard.

f.

Selection of a single menu item or tool bar button shall print any displayed schedule on the system printer for use as a building management and diagnostics tool.

2. Password

a. Multiple-level password access protection shall be provided to allow the user/manager to user interface control, display, and database manipulation capabilities deemed appropriate for each user, based on an assigned password.

b. Each user shall have the following: a user name (24 characters minimum), a password (12 characters minimum), and access levels.

c. The system shall allow each user to change his or her password at will.

d. When entering or editing passwords, the system shall not echo the actual characters for display on the monitor.

e. A minimum of five levels of access shall be supported individually or in any combination as follows:

Level 1 = View Data

Level 2 = Command

Level 3 = Operator Overrides

Level 4 = Database Modification

Level 5 = Database Configuration

Level 6 = All privileges, including Password Add/Modify

f. A minimum of 100 unique passwords shall be supported.

g. Operators shall be able to perform only those commands available for their respective passwords. Display of menu selections shall be limited to only those items defined for the access level of the password used to log-on.

h. The system shall automatically generate a report of log-on/log-off and system activity for each user. Any action that results in a change in the operation or configuration of the control system shall be recorded, including: modification of point values, schedules or history collection parameters, and all changes to the alarm management system, including the acknowledgment and deletion of alarms.

3. Screen Manager - The User Interface shall be provided with screen management capabilities that allow the user to activate, close, and simultaneously manipulate a minimum of 4 active display windows plus a network or user defined navigation tree.

4. Dynamic Color Graphics

a. The graphics application program shall be supplied as an integral part of the User Interface that is compatible with BASE existing system. Browser or Workstation applications that rely only upon HTML pages shall not be acceptable.

b. The graphics applications shall include a create/edit function and a runtime function. The system architecture shall support an unlimited number of graphics documents (graphic definition files) to be generated and executed.

The graphics shall be able to display and provide animation based on real-time data that is acquired, derived, or entered.

c. Graphics runtime functions – A maximum of 16 graphic applications shall be able to execute at any one time on a user interface or workstation with 4 visible to the user. Each graphic application shall be capable of the following functions:

All graphics shall be fully scalable

The graphics shall support a maintained aspect ratio.

Multiple fonts shall be supported.

Unique background shall be assignable on a per graphic basis.

The color of all animations and values on displays shall indicate if the status of the object attribute.

d. Operation from graphics – It shall be possible to change values (setpoints) and states in system controlled equipment by using drop-down windows accessible via the pointing device

e. Graphic editing tool – A graphic editing tool shall be provided that allows for the creation and editing of graphic files. The graphic editor shall be capable of performing/defining all animations, and defining all runtime binding.

The graphic editing tool shall in general provide for the creation and positioning of point objects by dragging from tool bars or drop-downs and positioning where required.

In addition, the graphic editing tool shall be able to add additional content to any graphic by importing backgrounds in the SVG, BMP or JPG file formats.

f. Aliasing – Many graphic displays representing part of a building and various building components are exact duplicates, with the exception that the various variables are bound to different field values. Consequently, it shall be possible to bind the value of a graphic display to aliases, as opposed to the physical field tags.

5. Historical trending and data collection

a. Each Automation Engine shall store trend and point history data for all analog and digital inputs and outputs, as follows:

Any point, physical or calculated, may be designated for trending. Two methods of collection shall be allowed:

Defined time interval

Upon a change of value

Each Automation Engine shall have the capability to store multiple samples for each physical point and software variable based upon available memory, including an individual sample time/date stamp. Points may be assigned to multiple history trends with different collection parameters.

b. Trend and change of value data shall be stored within the engine and uploaded to a dedicated trend database or exported in a selectable data format via a provided data export utility. Uploads to a dedicated database shall occur based upon one of the following: user-defined interval, manual command, or when the trend buffers are full. Exports shall be as requested by the user or on a time scheduled basis.

c. The system shall provide a configurable data storage subsystem for the collection of historical data. Data can be stored in either Microsoft Access or SQL database format.

6. Trend data viewing and analysis

a. Provide a trend viewing utility that shall have access to all database points.

b. It shall be possible to retrieve any historical database point for use in displays and reports by specifying the point name and associated trend name.

c. The trend viewing utility shall have the capability to define trend study displays to include multiple trends

d. Displays shall be able to be single or stacked graphs with on-line selectable display characteristics, such as ranging, color, and plot style.

e. Display magnitude and units shall both be selectable by the operator at any time without reconfiguring the processing or collection of data. This is a zoom capability.

f. Display magnitude shall automatically be scaled to show full graphic resolution of the data being displayed.

g. Trend studies shall be capable of calculating and displaying calculated variables including highest value, lowest value and time based accumulation.

2.4

NETWORK AUTOMATION ENGINES (NAE)

A.

Network Automation Engine (NAE 55series)

1.

The Network Automation Engine (NAE) shall be a fully user-programmable, supervisory controller. The NAE shall monitor the network of distributed application-specific controllers, provide global strategy and direction, and communicate on a peer-to-peer basis with other Network Automation Engines. If NAE is existing for the building and can be expanded to control replaced/additional equipment that should be used, if not, new NAE may be required.

2.

Automation network – The NAE shall reside on the automation network and shall support a subnet of system controllers.

3.

User Interface – Each NAE shall have the ability to deliver a web based User Interface (UI) as previously described. All computers connected physically or virtually to the automation network shall have access to the web based UI.

a.

The web based UI software shall be imbedded in the NAE. Systems that require a local copy of the system database on the user’s personal computer are not acceptable.

b.

The NAE shall support up a minimum of four (4) concurrent users.

c.

The web based user shall have the capability to access all system data through one NAE.

d.

Remote users connected to the network through an Internet Service Provider (ISP) or telephone dial up shall also have total system access through one NAE.

e.

Systems that require the user to address more than one NAE to access all system information are not acceptable.

f.

The NAE shall have the capability of generating web based UI graphics. The graphics capability shall be imbedded in the NAE.

g.

Systems that support UI Graphics from a central database or require the graphics to reside on the user’s personal computer are not acceptable.

h. The web based UI shall support the following functions using a standard version of Microsoft Internet Explorer:

Configuration

Commissioning

Data Archiving

Monitoring

Commanding

System Diagnostics

i. Systems that require workstation software or modified web browsers are not acceptable.

j. The NAE shall allow temporary use of portable devices without interrupting the normal operation of permanently connected modems.

4.

Processor – The NAE shall be microprocessor-based with a minimum word size of 32 bits. The NAE shall be a multi-tasking, multi-user, and real-time digital control processor. Standard operating systems shall be employed. NAE size and capability shall be sufficient to fully meet the requirements of this Specification.

5.

Memory – Each NAE shall have sufficient memory to support its own operating system, databases, and control programs, and to provide supervisory control for all control level devices.

6.

Hardware Real Time Clock – The NAE shall include an integrated, hardware-based, real-time clock.

7.

The NAE shall include troubleshooting LED indicators to identify the following conditions:

a.

Power - On/Off b.

Ethernet Traffic – Ethernet Traffic/No Ethernet Traffic c.

Ethernet Connection Speed – 10 Mbps/100 Mbps d.

FC Bus A – Normal Communications/No Field Communications e.

FC Bus B – Normal Communications/No Field Communications f.

Peer Communication – Data Traffic Between NAE Devices g.

Run – NAE Running/NAE In Startup/NAE Shutting Down/Software Not Running h.

Bat Fault – Battery Defective, Data Protection Battery Not Installed i.

24 VAC – 24 VAC Present/Loss Of 24VAC j.

Fault – General Fault

k. Modem RX – NAE Modem Receiving Data

l. Modem TX – NAE Modem Transmitting Data

8.

Communications Ports – The NAE shall provide the following ports for operation of operator Input/Output (I/O) devices, such as industry-standard computers, modems, and portable operator’s terminals.

a.

Two (2) USB port b.

Two (2) URS-232 serial data communication port c.

Two (2) RS-485 port

d. One (1) Ethernet port

9.

Diagnostics – The NAE shall continuously perform self-diagnostics, communication diagnosis, and diagnosis of all panel components. The Network Automation Engine shall provide both local and remote annunciation of any detected component failures, low battery conditions, or repeated failures to establish communication.

10.

Power Failure – In the event of the loss of normal power, The NAE shall continue to operate for a user adjustable period of up to 10 minutes after which there shall be an orderly shutdown of all programs to prevent the loss of database or operating system software.

a.

During a loss of normal power, the control sequences shall go to the normal system shutdown conditions. All critical configuration data shall be saved into Flash memory.

b.

Upon restoration of normal power and after a minimum off-time delay, the controller shall automatically resume full operation without manual intervention through a normal soft-start sequence.

7. Certification – The NAE shall be listed by Underwriters Laboratories (UL).

8. Controller network – The NAE shall support the following communication protocols on the controller network:

a. The NAE shall support BACnet Standard MS/TP Bus Protocol ASHRAE SSPC-135, Clause 9 on the controller network.

A BACnet Protocol Implementation Conformance Statement shall be provided for each controller device (master or slave) that will communicate on the BACnet MS/TP Bus.

The Conformance Statements shall be submitted 10 day prior to bidding.

The NAE shall support a minimum of 100 control devices.

2.5 DDC SYSTEM CONTROLLERS

A.

Field Equipment Controller (FEC X610)

1.

The Field Equipment Controller (FEC) with display shall be a fully user-programmable, digital controller that communicates via BACnet MS/TP protocol.

2.

The FEC shall employ a finite state control engine to eliminate unnecessary conflicts between control functions at crossover points in their operational sequences. Suppliers using non-state based DDC shall provide separate control strategy diagrams for all controlled functions in their submittals.

3.

Controllers shall be factory programmed with a continuous adaptive tuning algorithm that senses changes in the physical environment and continually adjusts loop tuning parameters appropriately. Controllers that require manual tuning of loops or perform automatic tuning on command only shall not be acceptable.

9. The FEC shall be assembled in a plenum-rated plastic housing with flammability rated to UL94-5VB.

10. The FEC shall include a removable base to allow pre-wiring without the controller.

11. The FEC shall include troubleshooting LED indicators to identify the following conditions:

a. Power On

b. Power Off

c. Download or Startup in progress, not ready for normal operation

d. No Faults

e. Device Fault

f. Field Controller Bus - Normal Data Transmission

g. Field Controller Bus - No Data Transmission

h. Field Controller Bus - No Communication

i. Sensor-Actuator Bus - Normal Data Transmission

j. Sensor-Actuator Bus - No Data Transmission

k. Sensor-Actuator Bus - No Communication

12. The FEC shall accommodate the direct wiring of analog and binary I/O field points.

13. The FEC shall support the following types of inputs and outputs:

a. Universal Inputs - shall be configured to monitor any of the following:

Analog Input, Voltage Mode

Analog Input, Current Mode

Analog Input, Resistive Mode

Binary Input, Dry Contact Maintained Mode

Binary Input, Pulse Counter Mode

b. Binary Inputs - shall be configured to monitor either of the following:

Dry Contact Maintained Mode

Pulse Counter Mode

c. Analog Outputs - shall be configured to output either of the following

Analog Output, Voltage Mode

Analog Output, current Mode

d. Binary Outputs - shall output the following:

24 VAC Triac

e. Configurable Outputs - shall be capable of the following:

Analog Output, Voltage Mode

Binary Output Mode

14. The FEC shall have the ability to reside on a Field Controller Bus (FC Bus).

a. The FC Bus shall be a Master-Slave/Token-Passing (MS/TP) Bus supporting BACnet Standard protocol SSPC-135, Clause 9.

b. The FC Bus shall support communications between the FECs and the NAE.

c. The FC Bus shall also support Input/Output Module (IOM) communications with the FEC and with the NAE.

d. The FC Bus shall support a minimum of 100 IOMs and FEC in any combination.

e.

The FC Bus shall operate at a maximum distance of 15, 00 Ft. between the FEC and the furthest connected device.

15. The FEC shall have the ability to monitor and control a network of sensors and actuators over a Sensor-Actuator Bus (SA Bus).

a. The SA Bus shall be a Master-Slave/Token-Passing (MS/TP) Bus supporting BACnet Standard protocol SSPC-135, Clause 9.

b. The SA Bus shall support a minimum of 10 devices per trunk.

c. The SA Bus shall operate at a maximum distance of 1,200 Ft. between the FEC and the furthest connected device.

16. The FEC shall have the capability to execute complex control sequences involving direct wired I/O points as well as input and output devices communicating over the FC Bus or the SA Bus.

17. The FEC shall support, but not be limited to, the following:

a. Hot water, chilled water/central plant applications

b. Rooftop units for special applications

Terminal units d.

Special programs as required for systems control

2.6

FIELD DEVICES

A.

Input/Output Module (IOM X710) 1.

The Input/Output Module (IOM) provides additional inputs and outputs for use in the FEC.

2.

The IOM shall communicate with the FEC over either the FC Bus or the SA Bus using BACnet Standard protocol SSPC-135, Clause 9.

3.

The IOM shall be assembled in a plenum-rated plastic housing with flammability rated to UL94-5VB.

4.

The IOM shall have a minimum of 4 points to a maximum of 17 points.

5.

The IOM shall support the following types of inputs and outputs:

a.

Universal Inputs - shall be configured to monitor any of the following:

Analog Input, Voltage Mode

Analog Input, Current Mode

Analog Input, Resistive Mode

Binary Input, Dry Contact Maintained Mode

Binary Input, Pulse Counter Mode

c. Binary Inputs - shall be configured to monitor either of the following:

Dry Contact Maintained Mode

Pulse Counter Mode

d. Analog Outputs - shall be configured to output either of the following

Analog Output, Voltage Mode

Analog Output, current Mode

e. Binary Outputs - shall output the following:

24 VAC Triac

f. Configurable Outputs - shall be capable of the following:

Analog Output, Voltage Mode

Binary Output Mode

6.

The IOM shall include troubleshooting LED indicators to identify the following conditions:

a.

Power On b.

Power Off c.

Download or Startup in progress, not ready for normal operation d.

No Faults e.

Device Fault

g. Normal Data Transmission

h. No Data Transmission

i. No Communication

B.

Network Sensors (NS-XXX700X)

1.

The Network Sensors (NS) shall have the ability to monitor the following variables as required by the systems sequence of operations:

a.

Zone Temperature b.

Zone humidity

c. Zone setpoint

2.

The NS shall transmit the zone information back to the controller on the Sensor-Actuator Bus (SA Bus) using BACnet Standard protocol SSPC-135, Clause 9.

3.

The Network Sensors shall include the following items:

a.

A backlit Liquid Crystal Display (LCD) to indicate the Temperature, Humidity and Setpoint.

b.

An LED to indicate the status of the Override feature.

c.

A button to toggle the temperature display between Fahrenheit and Celsius.

d.

A button to initiate a timed override command

4.

The NS shall be available with either screw terminals or phone jack.

5.

The NS shall be available in either surface mount or wall mount styles.

2.7

INPUT DEVICES

A.

General Requirements

1.

Installation, testing, and calibration of all sensors, transmitters, and other input devices shall be provided to meet the system requirements.

B.

Temperature Sensors

1.

General Requirements:

a.

Sensors and transmitters shall be provided, as outlined in the input/output summary and sequence of operations.

b.

The temperature sensor shall be of the resistance type, and shall be either two-wire 1000-ohm nickel RTD, or two-wire 1000-ohm platinum RTD.

c.

The following point types (and the accuracy of each) are required, and their associated accuracy values include errors associated with the sensor, lead wire, and A to D conversion:

Point Type
Accuracy
Room Temp
+ .5(F.
Duct Temperature
+ .5(F.
All Others
+ .75(F.

Room Temperature Sensors a.

Room sensors shall be constructed for either surface or wall box mounting.

b.

Room sensors shall have the following options when specified:

Setpoint reset slide switch providing a +3 degree (adjustable) range.

Individual heating/cooling setpoint slide switches.

A momentary override request push button for activation of after-hours operation.

Analog thermometer.

3.

Room Temperature Sensors with Integral Display a.

Room sensors shall be constructed for either surface or wall box mounting.

b.

Room sensors shall have an integral LCD display and four button keypad with the following capabilities:

Display room and outside air temperatures.

Display and adjust room comfort setpoint.

Display and adjust fan operation status.

Timed override request push button with LED status for activation of after-hours operation.

Display controller mode.

Password selectable adjustment of setpoint and override modes.

4.

Outside Air Sensors

Outside air sensors shall be designed to withstand the environmental conditions to which they will be exposed. They shall also be provided with a solar shield.

Sensors exposed to wind velocity pressures shall be shielded by a perforated plate that surrounds the sensor element.

Temperature transmitters shall be of NEMA 3R construction and rated for ambient temperatures.

5.

Duct Mount Sensors

Duct mount sensors shall mount in an electrical box through a hole in the duct, and be positioned so as to be easily accessible for repair or replacement.

Duct sensors shall be insertion type and constructed as a complete assembly, including lock nut and mounting plate.

For outdoor air duct…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .