GSARegion4BuildingAutomationSystemRequirementsv6.pdf

GSA Region 4 Building Automation System Requirements v6.0

1) GENERAL

a) The system shall operate stand alone at the field network level, building network level, and building supervisor network level. The system shall be networked on a

WAN to a remote GSA server; however, in the event of a WAN network failure, or server failure, such condition shall not affect the ability to operate the building from stand alone condition on a non-volatile flash memory platform described herein. The field level unitary controllers shall fail in last know command state until network connection resumes.

b) More than one communication protocol such as Lon, BACnet, or Modbus shall not be used in the same building automation system nor in the same building without written consent from GSA. Wireless technology shall not be used in on a

GSA project nor in a GSA facility without written consent from GSA Region 4

FMSP Operations Director after review from GSA IT Department.

c) All 100% of the physical and virtual points shall be exposed to the either a non-proprietary LON communication network bus OR non-proprietary BACnet communication network bus for integration or expansion for the JACE. Both protocols shall not be used in the same building automation system in the same building without written consent from GSA.

d) The BAS architecture shall be designed and installed to allow for independent integrator support.

e) No BAS supervisory or master controllers are allowed. The exception to this are

‘master controllers’ that are installed typically with major HVAC equipment such as Chillers and Boilers, whose manufacturers’ programming automatically modulates and sequences this equipment to maintain the demand placed on the equipment (ie, setpoint adjustment through BAS), and to equalize equipment runtimes.

f) As a minimum, each floor of a multi-story building shall have a separate IP-to-control-wire router. The vertical run shall be IP.

g) Gateways shall not be used unless specifically authorized in writing. Gateways shall be limited to integrating previously-existing legacy systems where applicable. Acceptance of gateways is at the sole discretion of the owner.

h) The control system shall be designed such that mechanical equipment will be able to operate under stand-alone control. Functional methodology such as scheduling, trending, and alarming shall be outlined fully in the submittal documentation. Methodology must follow pertinent and applicable guidelines.

Controllers that require a master computer or controller to perform basic functions are not acceptable. In the event of a network communication failure, or the loss of any other controller on the network, the control system shall continue to independently operate under control of the resident program stored in nonvolatile memory as detailed herein.

i) Field (tenant) temperature sensors, or similar devices, shall not include any capability for the occupant to provide a manual offset for setpoint adjustment.

Override buttons shall not be included on such devices to allow the user to manually request overtime space temperature control.

j) If a dedicated configuration tool is provided it shall be capable of being launched from within the applicable Network Management Software. A tool required for controller configuration shall be included as a leave-behind tool with enough license capability to support the installation.

k) The network infrastructure shall conform to the LonMark/BACnet published guidelines for network wiring and system architecture. Wire type, distance, termination, and use of routers shall strictly conform to the wiring standards. The number of nodes per channel shall be no more than 80% of the defined segment

(logical or physical) limit in order to provide future system enhancement with minimal infrastructure modifications. See reference to the Junction Box and

Wiring Guidelines.

l) No repeaters on the BAS network are allowed.

m) REMOTE ACCESS:

i) The owner shall provide an appropriate connection to the Internet to enable remote system access.

ii) The Contractor shall be required to attain HSPD-12 security clearance and attain clearance for access to GSA IP network.

iii) Controllers shall have the ability of being reprogrammed without being direct connected, and of having their program reloaded utilizing only the common Network Management Software (such as LonMaker for Windows

Network Management Software (or similar LNS tool)). For instance, controllers shall be capable of being programmed from a remote location via the Internet and the web interface. Any controller requiring 3rd party software, for the reloading or replacement of a controller will be disallowed.

n) VIRTUAL SERVER:

i) General - A virtual server shall provide web services for the BAS; the virtual server shall be government furnished equipment (GFE). End-users will access the system for day-to-day operation via a Web Browser such as Internet Explorer.

ii) The web services server shall be integrated with existing GSA enterprise server where applicable, such that the building access will be connected as a new site within the existing enterprise server software suite.

iii) Functionality - Note that the local BAS must fully operate in normal operation upon loss of communication with the BAS. This local operation mode must include all alarm, scheduling, graphics, overrides, optimal start, and related functions. The virtual Web server shall provide the interface between the LAN or WAN and the field control devices, and provide global supervisory control functions over the control devices connected to the Web Servers. It shall be capable of executing application control programs to provide the following:

(1) Hosting of the graphical HTML pages

(2) Calendar functions

(3) Scheduling, including temporary (if no other means available)

(4) Optimum Start (if no other means available)

(a) An optimal start program shall sense the indoor and outdoor air temperatures and reset the programmed start-up times to bring the buildings up to the proper temperature by occupancy time

(b) A minimum of five (5) separate optimal start schedules shall be assignable to different areas of building. The desired space temperatures at occupancy shall be assignable by the operator.

(5) Data Logging (if no other means available)

(6) Alarm monitoring and routing (if no other means available)

(7) Time synchronization (if no other means available)

(8) Soap/XML interface

(9) Static or Dynamic IP addressing

(10) SNVT access via web pages and via XML interface

(11) SMTP Server for alarm email notification

(12) Messages and message management

iv) Software licensee - The Software License for the Web Server(s) must be open and enable any Systems Integrator to engineer, change or modify the application once the project is complete. Restrictive engineering access to the Web server will not be acceptable.

v) Event alarm notification and actions

(1) The Web Server shall provide alarm recognition, storage, routing, management, and analysis to supplement distributed capabilities of equipment or application specific controllers.

(2) The Web Server shall be able to route any alarm condition to any defined user location whether connected to a local network or remote via dial-up, telephone connection, or wide-area network.

(3) Alarm generation shall be selectable for annunciation type and acknowledgement requirements.

(4) Control equipment and network failures shall be treated as alarms and annunciated.

(5) Alarms shall be annunciated via email notification to specific, configurable email address.

(6) Alarms shall be visually identified via the HTML graphics pages.

Overrides and setpoint changes shall be configured via the HTML interface.

(7) Alarms shall be annunciated in all of the following manners, selected and defined per user:

(a) Screen message text

(b) Pagers via paging services that initiate a page on receipt of email message

(c) Graphic with flashing alarm object(s)

(8) Alarms shall be logged for a period of no less than 1 week.

(9) Alarm logs shall be able to be transferred from the web server to a host.

(10) The following shall be recorded by the Web Server for each alarm (at a minimum):

(a) Time and date

(b) Location (building, floor, zone, office number, etc.)

(c) Equipment (air handler #, access way, etc.)

vi) Data logging and storage

vii) The web server shall have the ability to collect data for any object and store this data for future use. Data logging shall be performed either by a dedicated logger on the control network, via a combined web server/data logger, or by a central host PC attached to the network. Data logging must:

(1) Store data logs for at least 1 week before being overwritten

(2) Automatically update the host storage PC that the logs are approaching their full level

(3) Data logs shall be able to be exported from the web server to a common file format (such as comma separated values, etc)

(4) Be easily able to append a new log to a previously saved log

viii) Security and user administration

ix) Communications between the Web Server and Web Browser are to adopt proven ‘Secure User Authentication’ employing 128-bit industry standard

MD5 digital signatures. All transactions to/from the Web Server are to adopt the MD5 security procedures as a minimum to ensure the data on the system is protected from unauthorized access.

x) Individual web graphics pages shall have their own password protection.

Groups of pages may have the same password for the same level of user. Provide at least 3 levels of user access.

xi) Web browser clients

xii) The system shall be capable of supporting a minimum of 10 simultaneous client connections using a standard Web browser such as Internet

Explorer™, Firefox™, or Chrome™. Systems requiring additional software (to enable a standard Web browser) to be resident on the client machine, or manufacturer-specific browsers shall not be acceptable.

Java and Flash are the exceptions.

xiii) The Web browser software shall run on any operating system and system configuration that is supported by the Web browser. Systems that require specific machine requirements in terms of processor speed, memory, etc., in order to allow the Web browser to function with the FMCS, shall not be acceptable.

xiv) The Web browser shall provide a view of the system, in terms of graphics, schedules, calendars, logs, etc. Systems that require different views or that require different means of interacting with objects such as schedules, or logs, shall not be permitted. For high-point count pages, a single Flash or similar component shall be used. Even with high-point counts, these pages need to display their data completely in a few seconds, which can occur if a single component is used to load all points at once on each graphic page as specified here. Example graphic display pages must be demonstrated for GSA approval before they can be considered completed. Provide the following graphics as a minimum:

(1) Index Page

(2) Complete schematic of each air handling unit showing all temperatures, pressures, humidities, damper status, valve status, humidifier status and equipment status.

(3) Summary of building AHU’s

(4) Summary of building terminal box data in tabular data per floor.

As a minimum, include: occupancy, global or master setpoint, setpoint offset (slide-stat) actual setpoint, box load, fan, heat point, cfm setpoint, actual cfm, damper control output.

(5) Central plant data

(6) Floor plan graphics showing all space temperatures, space humidity,ventilation, such as exhaust, main outside air

(7) Auxiliary equipment.

xv) Also see Attachment 1 “R4 Sample BAS Pages” for sample required graphics’ capabilities and formats.

xvi) The Web browser client shall support as a minimum, the following functions:

(1) User log-on identification and password shall be required. If an unauthorized user attempts access, a blank web page shall be displayed. Security using Java authentication and encryption techniques to prevent unauthorized access shall be implemented.

(2) Storage of the graphical screens shall be in the Web Server, without requiring any graphics to be stored on the client machine.

Systems that require graphics storage on each client are not acceptable.

(3) Real-time values displayed on a Web page shall update automatically without requiring a manual “refresh” of the Web page.

xvii) The system shall provide the capability to specify a user’s (as determined by the log-on user identification) home page. Provide the ability to limit a specific user to just their defined home page. From the home page, links to other views, or pages in the system shall be possible, if allowed by the system administrator.

o) Network Servers, Routers, Bridges and Transceivers

i) An Internet Information Server will provide browser-based access to monitor system information and change system setpoints from anywhere in the controls network, anywhere on the facility LAN/WAN, or from the

Internet. The system shall be configured such that a failure of the

Supervisory System shall not impair access to the BAS via a web browser. A failure of the web browser system shall not impair the

Supervisory System.

ii) Equip each Internet server, router and bridge with a network transceiver on each network port (inbound and outbound) as dictated by the network type

iii) The network router shall be designed to route messages from a segment, sub-net, or domain in full duplex communication mode.

iv) The routers and bridges shall be capable of DIN rail or panel mounting and be equipped with status LED lights for Network traffic and power.

v) All communication cabling shall adhere to all requirements mentioned herein in Reference documents. Communication cabling (both control cabling and Ethernet) will be installed with unconventionally-colored cable jackets for straightforward identification. Ie, cabling in white, blue or yellow jackets are not permissible.

p) OPERATOR’S WORKSTATIONS

i) Each operator workstation shall be government furnished equipment

(GFE); provide (1) workstation at a desk and (1) portable workstation (i.e.

laptop).

ii) Each operator’s workstation shall be a PC equipped with Microsoft ®

Windows [most current operating system] as the user terminal operating software.

iii) System configuration and monitoring will be performed via the operator’s workstations. Under no circumstances shall an operator’s workstation be used as a control device for the network. It can be used for storage of data, network management, and as a GUI. If an operator’s workstation is taken off line, the control system shall continue to operate fully.

iv) Each operator’s workstation software is installed to provide basic operator interface (i.e., non-facility management/color graphics) and shall use pull down menu navigation as the basis of program execution, operating feature penetration, and local or remote site access.

v) Manual Database Save and Restore. A system operator with the proper password clearance shall be able to archive the database and store on electronic, magnetic, or optical media.

vi) Security. Each operator shall be required to log on to the system with a user name and password in order to view, edit, add, or delete data.

System security shall be selectable for each operator. The system supervisor shall have the ability to set passwords and security levels for all other operators.

q) ENTERPRISE LEVEL SOFTWARE

i) The BAS enterprise level software shall be installed on a GSA-provided, virtual server.

ii) The General User Interface (GUI) shall use openly available software packages that are nonexclusive. No closed software will be accepted.

Software must be generally available on the market from multiple sources.

iii) The BAS front-end software shall NOT have any capability to do network management.

iv) The language shall be English language oriented and be based on the syntax of programming languages such as BASIC. It shall allow for free form or fill-in-the-blank programming. Alternatively, the programming language can be graphically-based using function blocks as long as blocks are available that directly provide the functions listed below, and custom or compound function blocks can be created.

v) A full screen character editor/programming environment shall be provided. The editor shall be cursor/mouse-driven and allow the user to insert, add, modify, and delete code from the custom programming. It shall also incorporate word processing features such as cut-paste and find/replace.

vi) The programming language shall allow independently executing program tasks to be developed.

vii) The editor/programming environment shall have a debugging/simulation capability that allows the user to step through the program and to observe any intermediate values and/or results. The debugger shall also provide error messages for syntax and execution errors.

viii) The programming language shall support conditional statements

(IF/THEN/ELSE/ELSE-IF) using compound Boolean (AND, OR and NOT) and/or relations (EQUAL, LESS THAN, GREATER THAN, NOT EQUAL) comparisons.

ix) The programming language shall support floating-point arithmetic using the following operators: +, -, /, x, square root, and x^y. The following mathematical functions shall also be provided: absolute value and minimum/maximum value from a list of values.

x) The programming language shall have pre-defined variables that represent clock time, day of the week, and date. Variables that provide interval timing shall also be available. The language shall allow for computations using these values.

xi) The programming language shall have the ability to pre-define variables representing the status and results of the System Software, and shall be able to enable, disable, and change the values of objects in the system.

xii) On-Line Help. Provide a context sensitive, on-line help system to assist the operator in operation and editing of the system. On-line help shall be available for all applications and shall provide the relevant data for that particular screen.

xiii) Historical data logging, alarm monitoring and management, and scheduling shall be accessible and managed via the GUI. The system may utilize specific controllers to perform these functions or it may be performed by a host computer, or a combination of both.

xiv) See Appendix for GSA Region 4 requirements for BAS graphical pages and reports.

r) GSA IT REQUIREMENTS

i) The BAS shall be available for remote access through a secure GSA network circuit for approved users. Ensure installation is completed in compliance with all GSA IT requirements; coordinate fully with GSA PBS

CIO. I.T. supporting documentation: PBS CIO’s Building Technologies

Technical Reference Guide, PBS CIO’s Telecommunications Distribution

Design Guide, and Technology Policy for PBS-Owned Buildings

Monitoring & Control Systems

ii) A sample of each type of device installed on the GSA I.P. network shall be provided to GSA I.T. for vulnerability testing prior to installation.

iii) Provide all integration, configuration, and programming required in order to provide a complete and fully functional B.A.S. and for the system to operate on a virtual environment. After work is complete, verify proper communication of B.A.S., including GSA virtual server with building

B.A.S. Verify remote access is provided and is fully functional.

iv) Provide completed Server Documentation Form (provided by GSA) to

PBS Systems Support that documents all programs, files, links, and drive locations of regular backups necessary for complete replacement of the

BAS Server in the event of catastrophic failure.

v) A protocol analyzer log summary for each control channel for a minimum of 24 hours showing system performance shall be provided at the conclusion of the project. The statistical summary shall show that all bandwidth utilization and error limits are within acceptable ranges and that there are no network traffic problems, node communication problems, or system sizing problems. Limits are based on the configuration of the network, the media type etc. For a bus-topology on FT-10, the acceptable limits per lonworks channel are 52 nodes (80% capacity) and

150 packets/sec.

2) PROTOCOL

The system shall be a “Fully Open BAS” provided from either a LonWorks protocol or for

BACnet protocol, as specified below:

a) LonWorks Architecture:

i) LonMark Certified LNS LonWorks architecture shall consist of a flat, open architecture that utilizes the ANSI/CEA 709.1 (LonTalk™) Protocol as the common communication protocol between all controlled and controlling devices. The system shall have a web interface provided by an open architecture front-end utilizing a direct LonWorks LNS driver for seamless integration to the network. Where necessary or desired, LonTalk packets may be encapsulated into TCP/IP messages to take advantage of existing infrastructure or to increase network bandwidth. Hierarchal systems consisting of master or global controllers that poll and/or control less intelligent unitary controllers on a secondary bus will not be considered.

ii) The entire system network shall be a Local Operating Network (LON). All nodes shall communicate with each other utilizing ANSI/CEA 709. There will be no consideration given to any network which does not use

LonWorks as the primary communications network. Controllers shall be capable of sharing standard network variable data with other LON-based devices.

iii) Use of ANSI/CEA-852 layer 3 transparent routers is the only acceptable method spanning multiple channels and is the recommended method for system scalability. These components shall share common software for network communications, configuration, time scheduling, alarm handling, history logging, and custom programming. Any routers required by the system shall be supplied and commissioned as part of this specification.

iv) System Monitoring shall be provided through the installation of a graphical web browser that supports a direct driver to the LonWorks database. The browser shall provide complete access to any point in the system at any time. A complete and fully commissioned LNS database must be delivered for use with the browser interface as a specific deliverable as defined on the project schedule. This database must include ALL node definitions, ALL channel and subnet definitions, all router definitions, and all bindings etc.

v) All LonWorks devices (controllers, sensors, actuators, etc) shall be integrated into one common network infrastructure utilizing a common network management tool and creating a single LNS network database.

vi) The system shall utilize LonMark defined standard network and command messaging for all system data.

vii) In general, only LonMark certified devices will be accepted on this control network. Each device must be LonMark certified version [3.2] or higher. In those instances in which LonMark devices are not available, provide

LonWorks devices with application source code, device resource files, and external interface definitions 2 weeks prior to bid date. Any controller that does not meet this requirement must be stated and submitted with specific reason why it is not LonMark certified. LonMark compatible, LonMark compliant, LonMark “ish” controllers are not acceptable.

Exceptions may be granted for programmable controllers utilizing a custom programming software tools. These programmable controllers must meet all LonMark requirements for interoperability and shall utilize standard variable and configuration properties (SNVTs, SCPTs) as defined by LonMark. Any custom software required for controller programming shall be included as a leave-behind tool with enough license capability built into the bid to support the installation.

viii) Provide FTT-10A LonTalk routers as required to combine different communication channels onto a central field bus or as required to segment groups of Intelligent Devices and/or Control Units.

ix) Internet or IP connectivity is required, all devices connecting to the LAN shall use the TCP/IP protocol stack. Any LAN to LonWorks routers shall use the ANSI/CEA-852 standard layer 3 transparent routing protocol.

Specific IP interconnectivity shall follow IT standards for security, firewalls, address, etc. published in separate documents (if appropriate).

The Contractor shall make the internet (IP connection).

x) Controllers shall implement the full ANSI/CEA 709.1 “LonTalk” protocol.

Controllers must meet all of the requirements of this standard and must adhere to all of the protocol definition set forth by ANSI. All controllers shall be able to co-exist and interoperate on the LonWorks network without interfering or limiting other controller’s functionality. Controllers shall be able to be installed by any standard LonWorks Network Services

(LNS) based network management tool.

xi) All system controllers shall utilize a peer-to-peer communications scheme to communicate with each other and with the PC-type monitoring computer(s). All controllers shall utilize Standard Network Variable Types

(SNVTs) as defined by LonMark International. Controllers shall implement

LonMark device profiles as appropriate. All devices shall be provided with an LNS plug-in configuration utility. If an LNS plug-in is not available for a device, all device resource and program files, XIF and APB files, and points list shall be provided.

xii) Controllers from multiple manufactures are acceptable, and must be

LonMark Certified.

xiii) A central LonWorks Network Services (LNS) based operating system and database residing on a Server computer (locally or remotely as directed by GSA) will maintain a common database of network device configurations and provide a network management system that allows multiple client applications to access network data and perform network management functions. The network tools shall access the network and the network operating system either locally on the network media or remotely via TCP/IP.

xiv) Routers and bridges shall utilize LonTalk protocol transport, network, and session layers to transparently route messages bound for a node address in another sub-net or domain exclusively.

xv) Routers and bridges shall be fully configurable and permit a systems integrator to define message traffic, destination, and other network management functions utilize LonWorks Devices used for routing or bridging.

b) BACnet Architecture:

i) The BAS shall use native BACnet MS/TP, BACnet TCP/IP architecture and be in strict accordance with ASHRAE Standard 135. All controllers shall be BACnet Testing Labs (BTL) Certified. All BACnet points shall only use native BACnet BTL Certified standardized PICS (Protocol

Implementation Conformance Statement) and BIBBS (BACNET

Interoperability Building Blocks). 100% of the physical and virtual points shall be programmed as BACnet Objects and Events without any exceptions.

ii) 100% of Unitary Controllers for DDC HVAC Automation, Lighting Control, and Metering shall be fully programmable from a Niagara Framework

Wizard engineering tool. Third party engineering tools and drivers are prohibited. Niagara Framework Engineering tools shall be embedded on the site JACEs and used during site integration.

iii) All 100% of the command able physical points shall be exposed from all field level network control devices up to the JACE level communications bus for 100% Fully Open BAS integrations, two-way communication, and modification/expansion to the system architecture.

iv) The BAS JACE front end shall be capable of expansion to encompass the entire facility. The intent of this project is to provide all hardware and software required to accommodate the future expansion of the BAS by multiple vendors.

v) At the end of the construction warranty period, 100% of the DDC unitary field level controllers shall have 20% spare capacity for growth and expansion and DDC Niagara supervisory controllers shall have 30% spare capacity for growth and expansion.

vi) The BAS JACE front end shall employ FIPS 140-2 encryption licensing on

100% of the JACEs. FIPS 140-2, level 1 conformance licenses which activate encryption are available from most Niagara vendors. It is incumbent of the controls contractor to choose a vendor that supplies

FIPS 140-2 licenses for the Niagara JACEs.

vii) The communication network between general purpose digital field controllers shall be BACnet over Ethernet or BACnet over ARCNET. The communication network between unitary or terminal unit controllers shall be BACnet MS/TP over EIA-485 or BACnet over LonTalk. BACnet Point-

To-Point may be used for communication between the network and modems, line drivers or other data communication equipment.

viii) The BAS software shall be based on a server/thin-client architecture, designed around the open standards of web technology. The BAS server shall communicate using the ASHRAE BACnet/IP protocol, and in addition, offer concurrent support over the same data-link of the following protocols: LonWorks, MODBUS, and SNMP. The Server shall be accessed using a web browser.

ix) The intent of the thin-client architecture is to provide the operator(s) complete access to the BAS via a web browser. The thin-client web browser Graphical User Interface (GUI) shall support Microsoft and browser (8.x or later versions), and Windows 7/8 Operating System. No special software shall be required for the PC’s used to access the BAS via a web browser. Graphical User Interface (GUI) shall support software current versioning of software languages such as JAVA, XML, HTTP.

x) The web browser GUI shall provide a completely interactive user interface and must offer the following features as a minimum:

(1) Trending

(2) Scheduling

(3) Downloading Memory to field devices.

(4) Real time “live” Graphic Programs

(5) Tree Navigation

(6) Parameter change of properties

(7) Set point Adjustments

(8) Alarm / Event information

(9) Configuration of operators

(10) Execution of global commands

xi) Each component of the system, including the LANs and software, shall be in full compliance with ASHRAE Standard 135, commonly referred to as

BACnet. The BAS shall use native BACnet MS/TP, BACnet TCP/IP architecture and be in strict accordance with ASHRAE Standard 135. All controllers shall be BACnet Testing Labs (BTL) Certified. All BACnet points shall only use native BACnet BTL Certified standardized PICS

(Protocol Implementation Conformance Statement) and BIBBS (BACNET

Interoperability Building Blocks). All physical and virtual points shall be programmed as BACnet Objects and Events without any exceptions.

xii) JACE Installations: Comply with all of the following where JACE devices are installed:

(1) JACE License Forms: Submit with final shop drawings.

(2) Engineering Tools: Workbench version 4.0 or higher and all Field

Level programming tools shall be installed on the GSA

Government Laptop designated for the site. The contractor shall provide the appropriate quantity of legal copies of all software tools, configuration tools, management tools, and utilities used during system commissioning and installation. All tools shall be generally available in the market. No closed and/or unavailable tools will be permitted. Contractor shall convey all software tools and their legal licenses at project close out.

(3) JACE Programming Files: All programming files associated with each JACE shall be backed up and neatly organized by the floor number/site designation number for easy recognition on the

Government Laptop.

(4) Proprietary and Non-Proprietary Programming Files: All programming files associated with each field level device shall be backed up and neatly organized by equipment item for easy recognition on the Government Laptop.

(5) Backup Disks: Provide labeled backup disks (1ea copies) of

Workbench version 4.0 or higher and Field Level programming tools licensed to GSA. Provide (3ea copies) labeled JACE

Programming Files, and Site Field Level Programming files. Upon job completion provide all drawings, product information, complete and functional LNS databases, resource files, configuration files, etc on standard recordable media (CD, DVD).

(6) Supervisory controllers will perform the BAS function as the front end at the building level.

(7) Where a JACE is utilized, Controls contractor shall provide

Niagara 4, JACE 8000 as the supervisory controllers.

(8) All JACE software licenses shall have the “accept.station.in=*”;

“accept.station.out=*” and “accept.wb.in=*” and “accept.wb.out=*” section of the software licenses. The intent is to insure that the installed JACE products may be completely "open" for integrations. The GSA shall be free to direct the modification of any software license, regardless of supplier. In addition, GSA shall receive ownership of all job specific software configuration documentation, data files, and application-level software developed for the project. This shall include all custom, job specific software code and documentation for all configuration and programming that is generated for a given project and /or configured for use within Niagara Framework (JACE) based controllers and/or servers and any related GSA Intranet and

Internet connected routers and devices. Any and all required Ids and passwords for access to any component or software program shall be provided to GSA.

(9) Contractor will furnish Enterprise Web Supervisor software; utilize the standard Work Place toolbox for graphic development to promote consistency across the region. Any reutilization of existing graphics will not be permitted. GSA Operations Branch will provide graphics examples that shall be used as a standard design for BAS graphics. Supervisor engineering tool software shall be licensed to GSA and installed on the GSA provided laptop. Engineering tool back-up disks shall be turned over to

GSA as a deliverable.

(10) Graphics files shall be stored on the JACE locally at the building and stored/ provisioned as a 15- day FIFO cycle on the

GSA Region 7 web supervisor server for backup/ redundancy.

The implemented BAS solution shall operate stand alone at the building and shall not be reliant on the GSA WAN Wide Area

Network for GUI (Graphical User Interface) operation.

(11) GSA will provide an up to date desktop PC to be used to access the BAS as Government furnished property. After scanning/hardening/imaging, GSA IT will ship the PC to the project management on site and will be available for BAS integrator. An up to date laptop will be furnished as Government

Property to be used as the primary programming tool for the BAS.

The laptop shall be turned over to the GSA property manager at the end of the project. All programming software (engineering tools) and complete, neatly organized programming files shall be left on the laptop for easy modification and changes to the programming of the BAS. Software updates shall be updated at the end of the warranty period at no additional expense to the

Government.

xiii) General Purpose Digital Controllers shall use BACnet as the native communications protocol between controllers, which shall as a minimum, support the following BIBBs:

Data Sharing Alarm Event Schedule Trend Device Man.

DS-RP-A, B AE-N-B SCHED-B T-VMT-B DM-DDB-A, B

DS-RPM-B AE-ACK-B T-ATR-B DM-DOB-B

DS-WP-A, B AE-ASUM-B DM-DCC-B

DS-WPM-B DM-TS-B

DS-COVU-A, B DM-UTC-B

DM-RD-B

xiv) The Unitary Controllers shall use BACnet as the native communications protocol between controllers on the unitary controller network and must, as a minimum, support the following BIBBs:

Data Sharing Device Man.

DS-RP-B DM-RD-B

DS-WP-B DM-PT-B

xv) Communication Speed: Controllers shall communicate at a minimum of

150 Kbps using Ethernet or ARCNET implemented over EIA-485, using an unshielded twisted pair at the Data Link Layer.

xvi) The controller network shall use BACnet as its native communication protocol. Network bridges and routers must be of a modular design to ensure reliability and system performance. Routers and bridges must be used between system LANs and between the system and third party devices requiring interfaces.

xvii) BACnet Router: The central system shall use the building’s Local Area

Network (LAN) for communication. The communication between the central server and the controllers shall be BACnet/IP. A router shall be provided as required to bridge BACnet/IP and the data link used between controllers (BACnet Ethernet, BACnet ARCNET, and BACnet MS/TP).

Proprietary networks and proprietary protocols are not acceptable.

(1) BACnet Building Interoperability Building Blocks (BIBBs): BACnet routers must use BACnet as the native communication protocol and must, as a minimum, support the following BIBBs:

Data Sharing Alarm Event Schedule Trend Device Man. Network Man.

DS-RP-A, B AE-N-B SCHED-B T-VMT-B DM-DBB-A, B NM-RC-A

DS-RPM-B AE-ACK-B T-ATR-B

DS-WP-A, B AE-ASUM-B DM-DOB-B

DS-WPM-B DM-DCC-B

DS-WPM-B

DS-COVU-A, B

xviii) Unitary Controller Router

(1) A router shall be provided as required to bridge between the unitary controller network and the main controller network.

(2) BACnet BIBBs: The unitary controller router shall use BACnet as the native communications protocol between controllers on the unitary controller network and must, as a minimum, support he following BIBBs:

Data Sharing Alarm Event Schedule Trend Device Man.

DS-RP-A, B AE-N-B SCHED-B T-VMT-B DM-DDB-A, B

DS-RPM-B AE-ACK-B T-ATR-B DM-DOB-B

DS-WP-A, B AE-ASUM-B DM-DCC-B

DS-WPM-B DM-TS-B

DS-COVU-A, B DM-UTC-B

DM-RD-B

xix) Firmware Updates: The BACnet routers shall utilize flash memory to allow firmware upgrades to be performed remotely.

3) PRODUCTS

a) Only software tools and control products and associated programming tools that are available for purchase by government or any systems integrator or controls contractor are acceptable for this project. Products that can only be sold, installed or programmed by manufacturer, manufacturer branch offices or authorized representatives are not acceptable.

b) No exclusive or non-open integration tools, devices, or host software shall be used as part of this open system.

c) Controllers shall contain non-volatile memory for storage of control programs, configuration, and setpoints. All such data shall be retained in the event of a power failure. At least one controller shall have an on-board (battery or “super cap”-backed) real-time clock to ensure correct time-of-day operation following a power failure. Controllers that are not backed-up in the event of a power failure and that require time based operation (VAV’s, heat pumps, etc..) shall be peers on the network and be able to obtain time synchronization from a power fail protected controller and/or controllers upon network power restore.

d) Controllers shall use a software mechanism for network addressing and identification. It shall not be required to set physical network address switches on each controller.

e) SUBMITTALS

i) The Contractor shall submit a proposed network architecture diagram to

GSA PBS CIO for review and approval; provide both a hard copy and digital copy (either AutoCAD or Visio file). Diagram shall be in riser format and include all new I.P. devices, including manufacturer and model # for each device. Indicate wiring requirements, including wiring length and type (e.g. Cat 6, etc.) for each new segment. Indicate the IP Address for each IP device, and its physical location

ii) The Contractor shall submit the following BAS Compliance Checklist

(completed) as part of the submittals:

BAS Compliance Checklist ✓ C heck

Architecture: Flat Peer to Peer Lon w/ Layer 3 routing only

Communication Protocol:

LonTalk (ANSI/CEA 709.1)

Transceiver: ANSI/CEA 709.1a FTT-10 Free Topology Transceiver

Processor: Implements full

ANSI/CEA 709.1

protocol

Network Operating

System/Datab ase Standard:

LonWorks Network Services(LNS)

Message Tags: LonMark Defined Standard Network Variable Types

(SNVT) &

Standard Configuration Property Types

(SCPT)

Use of Gateways: Pre-approved Only.

For converting proprietary to LON Only

Network Management/ Commissionin g Tool:

LNS Based

Contractor Certification:

Training certification requirements

Product Certification:

LonMark Certified [3.2] or better

Media Type: Project specific – FTT, Powerline, Fiber

Twisted Pair Wiring

Bus Topology, Polarity Insensitive

Topology:

Other

Consideration s:

Must provide external interface file (XIF files) and device resource files for each device

4) INSTALLATION

a) Immediately prior to project closeout, the system integrator shall provide a protocol analyzer log summary for each channel for a minimum of 24 hours showing system performance. The statistical summary shall show that all bandwidth utilization and error limits are within acceptable ranges and that there are no network traffic problems, node or router communication problems, or system sizing problems.

b) Contractor Qualifications

i) The Contractor must be regularly engaged in the service and installation of LonWorks based systems as described herein, and must have been so for a minimum of three (3) years.

ii) The Contractor must be a certified LonWorks Integrator and shall submit resumes with the proposal indicating passing certificates as proof of approved training. Such proof must include summary of coursework and indicate both written and laboratory requirements of training. Certificates of training completion shall be for currently active employees.

c) Hardware and Software Component Manufacturer Qualifications

i) The manufacturer(s) of the hardware and software components as well as its subsidiaries must be a member in good standing of LonMark

International and/or LonMark Americas. Exception must be approved by the government. The government or government representative shall have full access to support and technical bulletins as any other integrator or authorized distributor.

ii) The manufacturer(s) of the hardware and software components must have no less than three (3) similar projects, which have LonWorks based

Facility Automation Systems as described herein installed by the authorized representative referenced above. These projects must be on-line and functional such that the Owners/Users representative can observe the system in full operation.

iii) Acceptable hardware and software manufacturers - See list of LonMark manufacturers at www.lonmark.org.

d) Reference Standards - Control system components shall conform to the following applicable standards for products specified:

i) Systems must be made up of LonMark-certified devices and LNS-Based tools.

ii) All controllers must be based on ANSI/CEA 709.1 LonTalk Protocol

iii) All routing must be via ANSI/CEA 852 LonWorks to IP Routing

e) BAS COMMISSIONING

i) Provide BAS commissioning (Cx) services prior to project closeout.

Submit Cx plan to GSA Energy Branch for review and approval prior to performing Cx work.

ii) Verify 2-way communication between controller level devices and enterprise server lever devices and software.

iii) Verify server-failure testing, such that upon loss of communication to the

GSA network and/or BAS server, the BAS controller or device has onboard, built-in occupancy schedules to allow the controlled equipment to continue to operate during normal occupancy hours, Monday through

Friday.

iv) Verify the local (on-site) BAS workstations are fully operational; pages should be displayed for BAS alarms, trends, equipment summary pages, individual equipment pages, etc.

v) Confirm that the BAS is configured to send emailed alarms to building personnel (e.g. building manager, O&M contractor) as appropriate.

vi) Prior to sequence of operation testing, provide point-to-point checkout sheets of all hardware points to GSA for review and approval.

vii) Verify each equipment’s sequence of operation. Demonstrate each equipment’s sequence with GSA personnel present for witnessing.

viii) BAS Cx services may be integrated with the overall project’s Cx plan, if appropriate.

ix) Cx Agent services shall be performed by a 3rd party Contractor; the BAS contractor may assist the Cx agent as needed.

f) TRAINING

i) All training schedules will be coordinated with the GSA Energy Group and

Service Center to insure all necessary personnel are available on the day(s) of training on the BAS, and the separate training for the onsite operations and maintenance of the HVAC and BAS control equipment.

Attendance sheets of the trainees will be recorded for each session, approved by attending GSA representative.

ii) Contractor shall provide factory-trained experienced personnel to provide

8-hour BAS system training, hosted at GSA Regional office. Training shall review operations of system through virtual server, workstation, and portable laptop. Normal BAS operator duties will be taught from the

Front-End, including adding alarms and trends, overriding points, and modifying schedules etc. Training shall cover remote access to the system, and instructions for backup operations in case of server failure.

PBS CIO and Regional Energy Team shall be invited to session. Training shall be recorded and formally edited, to be delivered in MP4 electronic format to GSA for future personnel’s training purposes. Provide a bound operations and maintenance manual with tabbed sections that provides step-by-step guidance how to perform typical system tasks as outlined in the training plan. This manual shall provide direction to future maintenance staff to perform daily operations without the need to reference the training video. Two (2) manual hard copies shall be submitted to Government, (3) for local operators and another for the

Service Center. A digital copy in .doc format of manual shall be loaded on the server and delivered to GSA as reference material and for backup.

iii) A minimum of three days of onsite training is required for our building operations / maintenance (O & M) staff and the GSA - COTR / CM on controls, all HVAC equipment installations, and system operations.

Training plan outlining topics and components shall be provided by contractor to GSA for review and approval prior to scheduling training.

Provide a hard copy of the training manual to each attendee. A digital copy in .doc format of manual shall be loaded on the server and delivered to GSA as reference material and for backup.

g) BAS DOCUMENTATION AND BACKUP FILES

i) Upon job completion provide programming’s BAS Sequences of

Operation which describes all system HVAC programming in detail, including variable names and constants, identified identically to how they are applied in the programming. Also, provide all as-built drawings

(including current network diagram), product information and operation manuals, complete and functional LNS databases, resource files, device

.XIF and .APB files, as-built tuned system parameters and configuration files, graphical symbol library files (including uncompiled source files) for web pages, etc on standard recordable media (CD, DVD). The drawings and sequences of operation files shall be provided in formats that are easily editable with standard office programs, such as MS Word and/or

Visio. Sequence of Operations Performance Testing Reports for the BAS operation verification shall be provided also.

ii) The above mentioned network architecture riser diagram shall be updated at the conclusion of the project to include all new I.P. devices, including manufacturer and model # for each device. Indicate wiring and installation details for each segment, including wiring length, color, and type (e.g. Cat 6, etc.), IP Addresses, location of device (floor number, closet, etc), number of nodes per channel, and terminators shown as necessary. Provide both a hard copy and digital copy (either AutoCAD or

Visio file).

iii) Provide as-built BAS wiring control drawings, laminated for protection, in each individual system’s respective control panel for straightforward reference and troubleshooting.

iv) A protocol analyzer log summary for each lonworks channel for a minimum of 24 hours showing system performance shall be provided at the conclusion of the project. The statistical summary shall show that all bandwidth utilization and error limits are within acceptable ranges and that there are no network traffic problems, node communication problems, or system sizing problems. Limits are based on the configuration of the network, the media type etc. However, for a bus-topology on FT-10, the acceptable limits per lonworks channel are 52 nodes (80% capacity) and

150 packets/sec.

v) Provide completed Server Documentation Form (provided by GSA) to

PBS Systems Support that documents all programs, files, links, and drive locations of regular backups necessary for complete replacement of the

BAS Server in the event of catastrophic failure.

vi) The contractor shall provide legal copies of all software tools, configuration tools, management tools, and utilities used during system commissioning and installation; one copy of each shall be provided for each desktop workstation, each portable workstation, and each server. All tools shall be generally available in the market. No closed and/or unavailable tools will be permitted. Contractor shall convey all software tools and their legal licenses at project close out.

vii) Provide accurate and current LNS Database of the control network to

Architect/Engineer of Record. Any changes made on the network shall be incorporated into the LNS database and an updated database shall be provided ensuring the Architect/Engineer of Record always has the correct and current database for the control system.

viii) Provide documentation on all point naming conventions to the

Architect/Engineer of Record/ for incorporation into the GUI.

ix) Provide a CD backup of the LNS database upon ANY changes or updates to the database.

h) WARRANTIES

i) All software upgrades for all PC and control network operating systems, the supervisory system, web browser, programming/binding tools, etc., without limitation shall be provided at no additional charge for a period of one year after Substantial Completion of the BAS.