S02. Specs - 250900 Systems Integration AGM_Amended (4-30-21).pdf

Louis Stokes Cleveland VAMC Renovate Radiation Therapy

Project No. 541-20-102

Systems Integration

25 09 00 - 1

SECTION 25 09 00

SYSTEMS INTEGRATION

(PROVIDED FOR REFERENCE IN COORDINATION WITH THE SYSTEMS INTEGRATOR)

PART 1 - GENERAL

1.1 RELATED DOCUMENTS

A. Drawings and general provisions of the Contract, including General and

Supplementary Conditions Specification Sections, apply to this Section.

B. The VAMC’s Owner’s Project Requirement (OPR) documents provide additional graphical schematics to delineate responsibilities for

Technical Services provided by the VAMC’s Systems Integrator (SIP) and the Design-Builder’s Installation teams.

1.2 SUMMARY

A. This section describes the Systems Integration & Integrated

Commissioning Services scope of work for the project. This section also coordinates the responsibilities of the Mechanical and Electrical trade

(D-B Team) contractors pertaining to control products or systems, furnished by each trade that will be integrated by this Services

Provider.

B. All labor, material, equipment and software not specifically referred to herein or on the plans, which are required to meet the functional intent of this specification, shall be provided without additional cost to the VAMC.

1.3 SYSTEMS INTEGRATION CONTRACTOR

A. AGM Energy Services, the VAMC’s Systems Integrator, will be covered under separate contract with Veterans’ Affairs Medical Center in conjunction with the Design-Build Contractor. This section is provided for reference and coordination of the Scope of Work.

1.4 SYSTEM DESCRIPTION

A. The Facility Management and Control System (FMCS) shall be comprised of

Java Application Control Engine(s) (JACE) within each facility. The

JACE (N4) shall connect to the VAMC’s local or wide area network, depending on configuration. Access to the system, either locally in each building, or remotely from a central site or sites, shall be accomplished through standard Web browsers, via the Internet and/or local area network. Each JACE (N4) shall communicate to BACnet (IBC) components provided under Division (230923) Temperature Controls

25 09 00 - 2

Install Contractor & associated HVAC/Electrical Equipment specification sections (Integrations to Unitary Controllers).

B. The Cleveland VAMC has an existing dedicated IP network for smart building technology systems. All new system integration equipment shall connect directly to this existing network. The systems integrator shall coordinate with the assigned VA COR to obtain IP addresses and other required network information.

C. The Cleveland VAMC has an existing Tridium Niagara 3.8 server with enterprise licensing. All new system integration shall be performed utilizing the Tridium Niagara AX 3.8 framework.

1.5 SUBMITTAL

A. Submittal shall consist of a JACE detail drawing depicting communications network and protocols between the JACE and HVAC

Equipment, generators, lighting controllers, power monitoring modules and VAMC internet bridge locations with a description of the communication type, media and protocol.

B. Upon completion of the work, provide a complete set of ‘as-built’ JACE detail drawings and application software on flash disk media or compact disc. Drawings shall be provided as AutoCAD™ or Visio™ compatible files. Eight copies of the ‘as-built’ drawings shall be provided in addition to the documents on flash disk media or compact disc.

Division (230923) Temperature Controls Contractor (TCC) and effective

(26) Electrical Systems Contractor (ESC) shall provide as-builts for their portions of work, via the Design- Build contract. Division

(250900) Systems Integration Provider (SIP) Contractor shall be responsible for as-builts pertaining to overall FMCS architecture and network diagrams.

1.6 SPECIFICATION NOMENCLATURE

A. Acronyms used in this specification are as follows:

FMCS Facility Management and Control System

TCS Temperature Control System

JACE (AX) Java Application Control Engine (AX)

IBC Interoperable BACNet Controller

GUI Graphical User Interface

WBI Web Browser Interface

POT Portable Operator’s Terminal

PMI Power Measurement Interface

25 09 00 - 3

DDC Direct Digital Controls

LAN Local Area Network

WAN Wide Area Network

OOT Object Oriented Technology

PICS Product Interoperability Compliance

Statement

TCC Temperature Control Contractor

1.7 DIVISION OF WORK

A. The Division (230923) Temperature Controls Contractor shall be responsible for all ancillary control devices, applied control panels, controller input/output and power wiring and controller/ control network communication wiring.

B. The Division (250900) Systems Integration Contractor shall be responsible for the Application Control Engine (JACE) hardware, software and programming of the JACE (N4), graphical user interface software (GUI), development of all graphical screens, Web Browser pages, setup of schedules, logs and alarms, BacNet™ network management as required to interface the JACE (N4) to the TCC network, global supervisory control applications, system integration and coordination and connection of the JACE (N4) to the local or wide area network.

1.8 RELATED WORK SPECIFIED ELSEWHERE

A. Division (230923) Temperature Controls Contractor:

1. Providing control devices and systems including but not limited to:

a. Applied Control panels, devices and wiring

b. Local controller and control device networks required for coordinated interface to unitary controllers provided by the Mechanical Contractor via the Design- Builder.

c. TCC BACnet network connections to the JACE (N4)’s

B. Division 26, Electrical:

1. Providing motor starters and disconnect switches (unless otherwise noted).

2. Power wiring and conduit (unless otherwise noted).

3. Provision, installation and wiring of smoke detectors (unless otherwise noted).

25 09 00 - 4

4. Providing labor and material for; generator network, lighting controller network and power monitoring network connections to the JACE (unless noted in other equipment sections)

5. Providing labor and material for; intranet, internet, BACnet, Modbus, etc. networking to the JACE from other systems or facility or global wide area networks.

1.9 AGENCY AND CODE APPROVALS

A. All products of the FMCS shall be provided with the following agency approvals. Verification that the approvals exist for all submitted products shall be provided with the submittal package. Systems or products not currently offering the following approvals are not acceptable.

1. UL-916; Energy Management Systems

2. FCC, Part 15, Subpart J, Class A Computing Devices

1.10 SOFTWARE LICENSE AGREEMENT

A. Software licensing for the JACE or Supervisor shall give the VAMC the capability to control their system and determine which contractors can bid and engineer within their system.

B. It shall be possible to ensure the VAMC can prevent unauthorized partners from accessing the system for engineering changes.

C. Software licensing shall have the freedom to individually manage authorized parties and independent parties.

D. The software licensing shall have no restrictions on which brand of

JACE, Supervisor or System Programming tools can interact with the system. Station Compatibility must = ALL and Tool Compatibility must =

ALL.

E. The VAMC shall accept the manufacturer's standard software and firmware licensing agreement as a condition of this contract. Such license shall grant use of all programs and application software to VAMC as defined by the manufacturer's license agreement, but shall protect manufacturer's rights to disclosure of trade secrets contained within such software.

1.11 DELIVERY, STORAGE AND HANDLING

A. Provide factory-shipping cartons for each piece of equipment and control device. Maintain cartons through shipping, storage, and handling as required to prevent equipment damage. Store equipment and materials inside and protected from weather.

25 09 00 - 5

1.12 JOB CONDITIONS

A. Cooperation with Other Trades: Coordinate the Work of this section with that of other sections to insure that the Work will be carried out in an orderly fashion. It shall be this Contractor's responsibility to check the Contract Documents for possible conflicts between his/her

Work and that of other crafts in equipment location, pipe, duct and conduit runs, electrical outlets and fixtures, air diffusers, and structural and architectural feature.

PART 2 - PRODUCTS

2.1 GENERAL

A. The Facility Management Control System (FMCS) shall be comprised of a network of interoperable, stand-alone digital controllers, a computer system, graphical user interface software, printers, network devices and other devices as specified herein. Focus of the system will be to serve the specific building/facility where installed, but be OPEN connected via the VAMC’s network for global access & management.

B. The installed system shall provide secure password access to all features, functions and data contained in the overall FMCS.

2.2 OPEN, INTEROPERABLE, INTEGRATED ARCHITECTURES

A. The intent of this specification is to provide a peer-to-peer networked, stand-alone, distributed control system with the capability to integrate both the ANSI/ASHRAE Standard 135-1995 BACnet technology communication protocols in one open, interoperable system.

B. The supplied computer software shall employ object-oriented technology

(OOT) for representation of all data and control devices within the system. In addition, adherence to industry standards including ANSI /

ASHRAE™ Standard 135-1995, BACnet to assure interoperability between all system components is required. For each BACnet device, the device supplier must provide a PICS document showing the installed device’s compliance level. Minimum compliance is Level 3; with the ability to support data read and write functionality. Physical connection of

BACnet devices shall be via Ethernet/Ethernet IP and MS/TP.

C. All components and controllers supplied under this contract shall be true “peer-to-peer” communicating devices. Components or controllers requiring “polling” by a host to pass data shall not be acceptable.

D. The supplied system must incorporate the ability to access all data using standard Web browsers without requiring proprietary operator

25 09 00 - 6 interface and configuration programs. An Open DataBase Connectivity

(ODBC) or Structured Query Language (SQL) compliant server database is required for all system database parameter storage. This data shall reside on a supplier-installed server for all database access. Systems requiring proprietary database and user interface programs shall not be acceptable.

E. A hierarchical topology is required to assure reasonable system response times and to manage the flow and sharing of data without unduly burdening the customer’s internal Intranet network. Systems employing a “flat” single tiered architecture shall not be acceptable.

1. Maximum acceptable response time from any alarm occurrence (at the point of origin) to the point of annunciation shall not exceed 5 seconds for network connected user interfaces.

2. Maximum acceptable response time from any alarm occurrence (at the point of origin) to the point of annunciation shall not exceed 60 seconds for remote or dial-up connected user interfaces.

2.3 NETWORKS

A. The Local Area Network (LAN) shall be a 10/100 Megabits/sec Ethernet network supporting BACNet, Java, XML, HTTP, and CORBA IIOP for maximum flexibility for integration of building data with enterprise information systems and providing support for multiple Java Application

Control Engine (JACE), user workstations and, if specified, a local server.

B. Local area network minimum physical and media access requirements:

1. Ethernet; IEEE standard 802.3

2. Cable; 10 Base-T, UTP-8 wire, category 5

3. Minimum throughput; 10/100 Mbps

2.4 NETWORK ACCESS

A. Remote Access.

1. For Local Area Network installations, provide access to the LAN from a remote location, via the Internet. The VA shall provide a connection to the Internet to enable this access via high-speed cable modem, asynchronous digital subscriber line (ADSL) modem, ISDN line, T1 Line or via the customer’s Intranet to a corporate server providing access to an Internet Service Provider (ISP).

2.5 JAVA APPLICATION CONTROL ENGINE (JACE)

25 09 00 - 7

A. The Division (250900) Systems Integration Contractor shall supply one or more Java Application Control Engine (JACE), as part of this contract. Number of area controllers required is dependent on the type and quantity of devices provided under Divisions (230923) Temperature

Controls and (26) Electrical Systems. It is the responsibility of the

Division (250900) Systems Integration Contractor to coordinate with the

Division (230923) Temperature Controls Contractor and (26) Contractors to determine the quantity and type of devices.

B. The Java Application Control Engine (JACE) 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 JACE (N4). It shall be capable of executing application control programs to provide:

1. Calendar functions

2. Scheduling

3. Trending

4. Alarm monitoring and routing

5. Time synchronization

6. Integration of BACnet controller data

C. The Java Application Control Engine (JACE), Vykon N4 platform must provide the following hardware features as a minimum, or as appropriate for the application:

1. Two Ethernet Port – 10/100 Mbps.

2. One RS 485 port (BACnet MSTP compatible).

3. One USB port.

4. NRIO port (RS485 and/or IO16 or IO34 module local IO compatibility).

5. Designed for DIN rail mounting.

6. Standard drivers include BacNet™.

7. Provide Modbus Capability.

8. SRAM data / memory backup.

9. Flash memory for long term data backup (If battery backup or flash memory is not supplied, the controller must contain a hard disk with at least 1 gigabyte storage capacity).

10. The JACE must be capable of operation over a temperature range of

0 to 60°C.

25 09 00 - 8

11. The JACE must be capable of withstanding storage temperatures of between 0 and 70°C.

12. The JACE must be capable of operation over a humidity range of 5 to 95% RH, non- condensing.

13. JACE must have up to 4 expansion modules attached.

D. The JACE shall provide multiple user access to the system and support for ODBC or SQL. A database resident on the JACE shall be an ODBC-compliant database or must provide an ODBC data access mechanism to read and write data stored within it.

E. The JACE shall support standard Web browser access via the

Intranet/Internet.

F. Event Alarm Notification and actions

1. The JACE shall provide alarm recognition, storage; routing, management, and analysis to supplement distributed capabilities of equipment or application specific controllers.

2. The JACE 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 including but limited to:

a. To alarm

b. Return to normal

4. Provide for the creation of a minimum of eight of alarm classes for the purpose of routing types and or classes of alarms, i.e.:

security, HVAC, Fire, etc.

5. Provide timed (schedule) routing of alarms by class, object, group, or node.

6. Provide alarm generation from binary object “runtime” and /or event counts for equipment maintenance. The user shall be able to reset runtime or event count values with appropriate password control.

G. Control equipment and network failures shall be treated as alarms and annunciated.

H. Alarms shall be annunciated in any of the following manners as defined by the user:

1. Screen message text

25 09 00 - 9

2. Email of the complete alarm message to multiple recipients.

Provide the ability to route and email alarms based on:

a. Day of week

b. Time of day

c. Recipient

3. Pagers via paging services that initiate a page on receipt of email message

4. Graphic with flashing alarm object(s)

5. Printed message, routed directly to a dedicated alarm printer

6. Audio messages

I. The following shall be recorded by the JACE for each alarm (at a minimum):

1. Time and date

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

3. Equipment (air handler #, accessway, etc.)

4. Acknowledge time, date, and user who issued acknowledgement.

5. Number of occurrences since last acknowledgement.

J. Alarm actions may be initiated by user defined programmable objects created for that purpose.

K. Defined users shall be given proper access to acknowledge any alarm, or specific types or classes of alarms defined by the user.

L. A log of all alarms shall be maintained by the JACE and/or a server (if configured in the system) and shall be available for review by the user.

M. Provide a “query” feature to allow review of specific alarms by user defined parameters.

N. A separate log for system alerts (controller failures, network failures, etc.) shall be provided and available for review by the user.

O. An Error Log to record invalid property changes or commands shall be provided and available for review by the user.

2.6 DATA COLLECTION AND STORAGE

A. The JACE shall have the ability to collect data for any property of any object and store this data for future use.

B. The data collection shall be performed by log objects, resident in the

JACE that shall have, at a minimum, the following configurable properties:

1. Designating the log as interval or change of value.

25 09 00 - 10

2. For interval logs, the object shall be configured for time of day, day of week and the sample collection interval.

3. For change of value logs, the object shall be configured for the deviation of a variable to a fixed value. This value, when reached, will initiate logging of the object.

4. For all logs, provide the ability to set the maximum number of data stores for the log and to set whether the log will stop collecting when full, or rollover the data on a first- in, first-out basis.

5. Each log shall have the ability to have its data cleared on a time-based event or by a user-defined event or action.

C. All log data shall be stored in a relational database in the JACE and the data shall be accessed from a server (if the system is so configured) or a standard Web Browser.

D. All log data, when accessed from a server, shall be capable of being manipulated using standard SQL statements.

E. All log data shall be available to the user in the following data formats:

1. HTML

2. XML

3. Plain Text

4. Comma or tab separated values

F. Systems that do not provide log data in HTML and XML formats at a minimum shall not be acceptable.

G. The JACE shall have the ability to archive its log data either locally

(to itself), or remotely to a server or other JACE on the network.

Provide the ability to configure the following archiving properties, at a minimum:

1. Archive on time of day

2. Archive on user-defined number of data stores in the log (buffer size)

3. Archive when log has reached its user-defined capacity of data stores

4. Provide ability to clear logs once archived.

2.7 AUDIT LOG

A. Provide and maintain an Audit Log that tracks all activities performed on the JACE. Provide the ability to specify a buffer size for the log

25 09 00 - 11 and the ability to archive log based on time or when the log has reached its user-defined buffer size. Provide the ability to archive the log locally (to the JACE), to another JACE (N4) on the network, or to a server. For each log entry, provide the following data:

1. Time and date

2. User ID

3. Change or activity: i.e., Change setpoint, add or delete objects, commands, etc.

2.8 DATABASE BACKUP AND STORAGE

A. The JACE shall have the ability to automatically backup its database.

The database shall be backed up based on a user-defined time interval.

B. Copies of the current database and, at the most recently saved database shall be stored in the JACE. The age of the most recently saved database is dependent on the user-defined database save interval.

C. The JACE database shall be stored, at a minimum, in XML format to allow for user viewing and editing, if desired. Other formats are acceptable as well, as long as XML format is supported.

2.9 GRAPHICAL USER INTERFACE SOFTWARE

A. Operating System: The GUI shall run on Microsoft Windows 7.

B. The GUI shall employ browser-like functionality for ease of navigation.

It shall include a tree view (similar to Windows Explorer) for quick viewing of, and access to, the hierarchical structure of the database.

In addition, menu-pull downs, and toolbars shall employ buttons, commands and navigation to permit the operator to perform tasks with a minimum knowledge of the HVAC Control System and basic computing skills. These shall include, but are not limited to, forward/backward buttons, home button, and a context sensitive locator line (similar to a URL line), that displays the location and the selected object identification.

C. Real-Time Displays. The GUI, shall at a minimum, support the following graphical features and functions:

1. Graphic screens shall be developed using any drawing package capable of generating a GIF, BMP, or JPG file format. Use of proprietary graphic file formats shall not be acceptable. In addition to, or in lieu of a graphic background, the GUI shall support the use of scanned pictures.

25 09 00 - 12

2. Graphic screens shall have the capability to contain objects for text, real-time values, animation, color spectrum objects, logs, graphs, HTML or XML document links, schedule objects, hyperlinks to other URL’s, and links to other graphic screens.

3. Graphics shall support layering and each graphic object shall be configurable for assignment to one a layer. A minimum of six layers shall be supported.

4. Modifying common application objects, such as schedules, calendars, and set points shall be accomplished in a graphical manner.

a. Schedule times will be adjusted using a graphical slider, without requiring any keyboard entry from the operator.

b. Holidays shall be set by using a graphical calendar, without requiring any keyboard entry from the operator.

5. Commands to start and stop binary objects shall be done by right-clicking the selected object and selecting the appropriate command from the pop-up menu. No entry of text shall be required.

6. Adjustments to analog objects, such as set points, shall be done by right-clicking the selected object and using a graphical slider or text entry to adjust the value.

D. System Configuration. At a minimum, the GUI shall permit the operator to perform the following tasks, with proper password access:

1. Create, delete or modify control strategies.

2. Add/delete objects to the system.

3. Tune control loops through the adjustment of control loop parameters (If exposed in controller to BacNET).

4. Enable or disable control strategies (If exposed in controller to

BacNET).

5. Generate hard copy records or control strategies on a printer.

6. Select points to be alarmable and define the alarm state.

7. Select points to be trended over a period of time and initiate the recording of values automatically.

E. 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. Additional help information

25 09 00 - 13 shall be available through the use of hypertext. All system documentation and help files shall be in HTML format.

F. Security. Each operator shall be required to log on to that 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 administrator shall have the ability to set passwords and security levels for all other operators. Each operator password shall be able to restrict the operators’ access for viewing and/or changing each system application, full screen editor, and object. Each operator shall automatically be logged off of the system if no keyboard or mouse activity is detected. This auto log-off time shall be set per operator password. All system security data shall be stored in an encrypted format.

G. System Diagnostics. The system shall automatically monitor the operation of all workstations, printers, modems, network connections, building management panels, controllers, temperature control devices, energy monitoring, lighting controls, and other BAS specific devices.

The failure of any device shall be annunciated to the operator.

H. Alarm Console

1. The system will be provided with a dedicated alarm window or console. This window will notify the operator of an alarm condition and allow the operator to view details of the alarm and acknowledge the alarm. The use of the Alarm Console can be enabled or disabled by the system administrator.

2. When the Alarm Console is enabled, a separate alarm notification window will supercede all other windows on the desktop and shall not be capable of being minimized or closed by the operator. This window will notify the operator of new alarms and un-acknowledged alarms. Alarm notification windows or banners that can be minimized or closed by the operator shall not be acceptable.

2.10 WEB BROWSER CLIENTS

A. The system shall be capable of supporting an unlimited number of clients using a standard Web browser such as Internet Explorer™.

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

25 09 00 - 14

B. 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.

C. The Web browser shall provide the same view of the system, in terms of graphics, schedules, calendars, logs, etc., and provide the same interface methodology as is provided by the Graphical User Interface.

Systems that require different views or that require different means of interacting with objects such as schedules, or logs, shall not be permitted.

D. The Web browser client shall support at 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. Graphical screens developed for the GUI shall be the same screens used for the Web browser client. Any animated graphical objects supported by the GUI shall be supported by the Web browser interface.

3. HTML programming shall not be required to display system graphics or data on a Web page. HTML editing of the Web page shall be allowed if the user desires a specific look or format.

4. Storage of the graphical screens shall be in the Java Application

Control Engine (JACE), without requiring any graphics to be stored on the client machine. Systems that require graphics storage on each client are not acceptable.

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

6. Users shall have administrator-defined access privileges.

Depending on the access privileges assigned, the user shall be able to perform the following:

a. Modify common application objects, such as schedules, calendars, and set points in a graphical manner.

25 09 00 - 15

i. Schedule times will be adjusted using a graphical slider, without requiring any keyboard entry from the operator.

ii. Holidays shall be set by using a graphical calendar, without requiring any keyboard entry from the operator.

b. Commands to start and stop binary objects shall be done by right-clicking the selected object and selecting the appropriate command from the pop-up menu. No entry of text shall be required.

c. View logs and charts

d. View and acknowledge alarms

e. Setup and execute SQL queries on log and archive information

7. 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.

8. Graphic screens on the Web Browser client shall support hypertext links to other locations on the Internet or on Intranet sites, by specifying the Uniform Resource Locator (URL) for the desired link.

2.11 SUPERVISORY SOFTWARE AND HARDWARE

A. A central server located at the designated VAMC Facility in Cleveland, Ohio shall be provided/upgraded/integrated to with each application brought on-line into the VAMC OPEN Network. The server shall support all Java Application Control Engine(s) (JACE) connected to the customer’s network whether local or remote.

B. Local connections shall be via an Ethernet LAN. Remote connections can be via ISDN, ADSL, or T1 connections.

C. It shall be possible to provide access to all Java Application Control

Engine (JACE) via a single connection to the server. In this configuration, each Java Application Control Engine (JACE) can be accessed from a remote Graphical User Interface (GUI) or from a standard Web browser (WBI) by connecting to the server.

D. The server shall provide the following functions, at a minimum:

25 09 00 - 16

1. Global Data Access: The server shall provide complete access to distributed data defined anywhere in the system.

2. Distributed Control: The server shall provide the ability to execute global control strategies based on control and data objects in any JACE in the network, local or remote.

3. The server shall include a master clock service for its subsystems and provide time synchronization for all Java

Application Control Engine (JACE)

4. The server shall accept time synchronization messages from trusted precision Atomic Clock Internet sites and update its master clock based on this data.

5. The server shall provide scheduling for all (JACE) and their underlying field control devices.

6. The server shall provide demand limiting that operates across all

Java Application Control Engine (JACE). The server must be capable of multiple demand programs for sites with multiple meters and or multiple sources of energy. Each demand program shall be capable of supporting separate demand shed lists for effective demand control.

7. The server shall implement the BACnet Command Prioritization scheme (16 levels) for safe and effective contention resolution of all commands issued to Java Application Control Engine (JACE).

8. Each Java Application Control Engine (JACE) supported by the server shall have the ability to archive its log data, alarm data and database to the server, automatically. Archiving options shall be user-defined including archive time and archive frequency.

9. The server shall provide central alarm management for all Java

Application Control Engine (JACE) supported by the server. Alarm management shall include:

a. Routing of alarms to display, printer, email and pagers.

b. View and acknowledge alarms.

c. Query alarm logs based on user-defined parameters

10. The server shall provide central management of log data for all

Network Area Controllers Java Application Control Engine (JACE) supported by the server. Log data shall include process logs, 25 09 00 - 17 runtime and event counter logs, audit logs and error logs. Log data management shall include:

a. Viewing and printing log data.

b. Exporting log data to other software applications.

c. Query log data based on user-defined parameters

E. Server Hardware Requirements (For Reference Only, already provided) The server hardware platform shall have the following requirements:

1. The computer shall be equal to a Dell 2600 series PowerEdge series computer with the following specifications:

a. Intel Xeon 3.06GHz processor.

b. 400MHz side Buss.

c. 512K L2 cache.

d. 6 DDR SDRAM DIMM sockets supporting 6GB of main memory.

e. 7 expansion slots 2x64-bit/133MHz PCI-X, 4x64-bit/100MHz

PCI-X, 1x32- bit/33MHz PCI.

f. LSI Logic 53C1030 Dual Integrated PCI Ultra320 LVD SCSI controller.

g. Raid Controllers – PERC4/Di, PERCC3/DC, PERC3/QC.

h. Drive Bays – Standard internal hard drive bays to support up to six 1” or Ultra320 SCSI hard drives.

i. 2X Combo CD-RW/DVD-ROM Drive.

j. 3.5” 1.44MB drive.

k. Hard Drives Up to 8x1 hot plug SCSI Drives, 10,000 and

15,000 PRM (Future).

l. Provide Internal Storage 1.168TB Internal Storage in Bid.

m. Internal Tape Backup PowerVault 100T DDS.

n. Dual Universal Serial Bus (USB) Ports.

o. 20” Flat Monitor 2000FP

2. The server operating system shall be current/best Microsoft

Windows Professional and Include current Microsoft Internet

Explorer.

3. Connection to the FMCS network shall be via an Ethernet network interface card, 10/100 Mbps.

4. For dedicated alarm printing, provide a compatible ink jet type printer, either 80 or 132 column width. The printer shall have a parallel port interface.

2.12 SYSTEM PROGRAMMING

25 09 00 - 18

A. The Graphical User Interface software (GUI) shall provide the ability to perform system programming and graphic display engineering as part of a complete software package. Access to the programming functions and features of the GUI shall be through password access as assigned by the system administrator.

B. A library of control, application, and graphic objects shall be provided to enable the creation of all applications and user interface screens. Applications are to be created by selecting the desired control objects from the library, dragging or pasting them on the screen, and linking them together using a built in graphical connection tool. Completed applications may be stored in the library for future use. Graphical User Interface screens shall be created in the same fashion. Data for the user displays is obtained by graphically linking the user display objects to the application objects to provide “real-time” data updates. Any real-time data value or object property may be connected to display its current value on a user display. Systems requiring separate software tools or processes to create applications and user interface displays shall not be acceptable.

C. Programming Methods

1. Provide the capability to copy objects from the supplied libraries, or from a user- defined library to the user’s application. Objects shall be linked by a graphical linking scheme by dragging a link from one object to another. Object links will support one- to-one, many-to-one, or one-to-many relationships. Linked objects shall maintain their connections to other objects regardless of where they are positioned on the page and shall show link identification for links to objects on other pages for easy identification. Links will vary in color depending on the type of link; i.e., internal, external, hardware, etc.

2. Configuration of each object will be done through the object’s property sheet using fill-in the blank fields, list boxes, and selection buttons. Use of custom programming, scripting language, or a manufacturer-specific procedural language for configuration will not be accepted.

3. The software shall provide the ability to view the logic in a monitor mode. When on- line, the monitor mode shall provide the ability to view the logic in real time for easy diagnosis of the

25 09 00 - 19 logic execution. When off-line (debug), the monitor mode shall allow the user to set values to inputs and monitor the logic for diagnosing execution before it is applied to the system.

4. All programming shall be done in real-time. Systems requiring the uploading, editing, and downloading of database objects shall not be allowed.

5. The system shall support object duplication within a customer’s database. An application, once configured, can be copied and pasted for easy re-use and duplication. All links, other than to the hardware, shall be maintained during.

2.13 TRIDIUM NETWORK MANAGEMENT

A. The Graphical User Interface software (GUI) shall provide a complete set of integrated Tridium network management tools for working with

Tridium AX networks. These tools shall manage a database for all

Tridium devices by type and revision, and shall provide a software mechanism for identifying each device on the network. These tools shall also be capable of defining network data connections between other devices, known as “binding”. Systems requiring the use of third party Tridium network management tools shall not be accepted.

B. Network management shall include the following services: device identification, device installation, device configuration, device diagnostics, device maintenance and network variable binding.

C. The Network configuration tool shall also provide diagnostics to identify devices on the network, to reset devices, and to view health and status counters within devices.

D. These tools shall provide the ability to “learn” an existing BACNet network, regardless of what network management tool(s) were used to install the existing network, so that existing BACNet devices and newly added devices are part of a single network management database.

E. The network management database shall be resident in the Java

Application Control Engine (JACE), ensuring that anyone with proper authorization has access to the network management database at all times. Systems employing network management databases that are not resident, at all times, within the control system, shall not be accepted.

2.14 OBJECT LIBRARIES

25 09 00 - 20

A. A standard library of objects shall be included for development and setup of application logic, user interface displays, system services, and communication networks.

B. The objects in this library shall be capable of being copied and pasted into the user’s database and shall be organized according to their function. In addition, the user shall have the capability to group objects created in their application and store the new instances of these objects in a user-defined library.

C. In addition to the standard libraries specified here, the supplier of the system shall maintain an on-line accessible (over the Internet) library, available to all registered users to provide new or updated objects and applications as they are developed.

D. All control objects shall conform to the control objects specified in the BACNet specification.

E. The library shall include applications or objects for the following functions, at a minimum:

1. Scheduling Object. The schedule must conform to the schedule object as defined in the BACNet specification, providing 7-day plus holiday & temporary scheduling features and a minimum of 10 on/off events per day. Data entry to be by graphical sliders to speed creation and selection of on-off events.

2. Calendar Object. . The calendar must conform to the calendar object as defined in the BACNet specification, providing 12-month calendar features to allow for holiday or special event data entry. Data entry to be by graphical “point-and-click” selection.

This object must be “linkable” to any or all scheduling objects for effective event control.

3. Duty Cycling Object. Provide a universal duty cycle object to allow repetitive on/off time control of equipment as an energy conserving measure. Any number of these objects may be created to control equipment at varying intervals

4. Temperature Override Object. Provide a temperature override object that is capable of overriding equipment turned off by other energy saving programs (scheduling, duty cycling etc.) to maintain occupant comfort or for equipment freeze protection.

5. Start-Stop Time Optimization Object. Provide a start-stop time optimization object to provide the capability of starting

25 09 00 - 21 equipment just early enough to bring space conditions to desired conditions by the scheduled occupancy time. Also, allow equipment to be stopped before the scheduled un-occupancy time just far enough ahead to take advantage of the building’s

“flywheel” effect for energy savings. Provide automatic tuning of all start / stop time object properties based on the previous day’s performance.

6. Demand Limiting Object. Provide a comprehensive demand-limiting object that is capable of controlling demand for any selected energy utility (electric, oil, and gas). The object shall provide the capability of monitoring a demand value and predicting (by use of a sliding window prediction algorithm) the demand at the end of the user defined interval period (1-60 minutes). This object shall also accommodate a utility meter time sync pulse for fixed interval demand control. Upon a prediction that will exceed the user defined demand limit (supply a minimum of 6 per day), the demand limiting object shall issue shed commands to either turn off user specified loads or modify equipment set points to effect the desired energy reduction. If the list of sheddable equipment is not enough to reduce the demand to below the set point, a message shall be displayed on the users screen (as an alarm) instructing the user to take manual actions to maintain the desired demand. The shed lists are specified by the user and shall be selectable to be shed in either a fixed or rotating order to control which equipment is shed the most often. Upon suitable reductions in demand, the demand-limiting object shall restore the equipment that was shed in the reverse order in which it was shed. Each sheddable object shall have a minimum and maximum shed time property to effect both equipment protection and occupant comfort.

F. The library shall include control objects for the following functions.

All control objects shall conform to the objects as specified in the

BACNet specification.

1. Analog Input Object - Minimum requirement is to comply with the

BACNet standard for data sharing. Allow high, low and failure limits to be assigned for alarming. Also, provide a time delay

25 09 00 - 22 filter property to prevent nuisance alarms caused by temporary excursions above or below the user defined alarm limits.

2. Analog Output Object - Minimum requirement is to comply with the

BACNet standard for data sharing.

3. Binary Input Object - Minimum requirement is to comply with the

BACNet standard for data sharing. The user must be able to specify either input condition for alarming. This object must also include the capability to record equipment run-time by counting the amount of time the hardware input is in an “on” condition. The user must be able to specify either input condition as the “on” condition.

4. Binary Output Object - Minimum requirement is to comply with the

BACNet standard for data sharing. Properties to enable minimum on and off times for equipment protection as well as interstart delay must be provided. The BACNet Command Prioritization priority scheme shall be incorporated to allow multiple control applications to execute commands on this object with the highest priority command being invoked. Provide sixteen levels of priority as a minimum. Systems not employing the BACNet method of contention resolution shall not be acceptable.

5. PID Control Loop Object - Minimum requirement is to comply with the BACNet standard for data sharing. Each individual property must be adjustable as well as to be disabled to allow proportional control only, or proportional with integral control, as well as proportional, integral and derivative control.

6. Comparison Object - Allow a minimum of two analog objects to be compared to select either the highest, lowest, or equality between the two linked inputs. Also, allow limits to be applied to the output value for alarm generation.

7. Math Object - Allow a minimum of four analog objects to be tested for the minimum or maximum, or the sum, difference, or average of linked objects. Also, allow limits to be applied to the output value for alarm generation.

8. Custom Programming Objects - Provide a blank object template for the creation of new custom objects to meet specific user application requirements. This object must provide a simple

BASIC-like programming language that is used to define object

25 09 00 - 23 behavior. Provide a library of functions including math and logic functions, string manipulation, and e-mail as a minimum. Also, provide a comprehensive on-line debug tool to allow complete testing of the new object. Allow new objects to be stored in the library for re-use.

9. Interlock Object - Provide an interlock object that provides a means of coordination of objects within a piece of equipment such as an Air Handler or other similar types of equipment. An example is to link the return fan to the supply fan such that when the supply fan is started, the return fan object is also started automatically without the user having to issue separate commands or to link each object to a schedule object. In addition, the control loops, damper objects, and alarm monitoring (such as return air, supply air, and mixed air temperature objects) will be inhibited from alarming during a user-defined period after startup to allow for stabilization. When the air handler is stopped, the interlocked return fan is also stopped, the outside air damper is closed, and other related objects within the air handler unit are inhibited from alarming thereby eliminating nuisance alarms during the off period.

10. Temperature Override Object - Provide an object whose purpose is to provide the capability of overriding a binary output to an

“On” state in the event a user specified high or low limit value is exceeded. This object is to be linked to the desired binary output object as well as to an analog object for temperature monitoring, to cause the override to be enabled. This object will execute a Start command at the Temperature Override level of start/stop command priority unless changed by the user.

11. Composite Object - Provide a container object that allows a collection of objects representing an application to be encapsulated to protect the application from tampering, or to more easily represent large applications. This object must have the ability to allow the user to select the appropriate parameters of the “contained” application that are represented on the graphical shell of this container.

G. The object library shall include objects to support the integration of devices connected to the Java Application Control Engine (JACE). At a

25 09 00 - 24 minimum, provide the following as part of the standard library included with the programming software:

1. BACNet devices. These devices shall include, but not be limited to, devices for control of HVAC, lighting, access, and metering.

Provide BACNet manufacturer-specific objects to facilitate simple integration of these devices. All network variables defined in the BACNet profile shall be supported. Information (type and function) regarding network variables not defined in the BACNet profile shall be provided by the device manufacturer.

2. For BACNet devices, provide the following objects at a minimum:

a. BACNet AI

b. BACNet AO

c. BACNet BI

d. BACNet BO

e. BACNet Device

f. For each BACNet object, provide the ability to assign the object a BACNet device and object instance number.

g. For Modbus devices, provide the ability to interface to specific “data registers” as documented and supplied by the equipment vendor. Such as;

h. Modbus GenericBI

i. Modbus GenericBO

j. Modbus GenericAI

k. Modbus GenericAO

l. Modbus 6xRecord

m. Modbus BitsToRegister

n. Modbus PresetCoil

o. Modbus PresetRegister

p. Modbus RegisterToBits

2.15 DDE DEVICE INTEGRATION

A. The Java Application Control Engine (JACE) shall support the integration of device data via Dynamic Data Exchange (DDE), over the

Ethernet Network. The Java Application Control Engine (JACE) shall act as a DDE client to another software application that functions as a DDE server.

B. Provide the required objects in the library, included with the

Graphical User Interface programming software, to support the

25 09 00 - 25 integration of these devices into the FMCS. Objects provided shall include at a minimum:

1. DDE Generic AI Object.

2. DDE Generic AO Object.

3. DDE Generic BO Object.

4. DDE Generic BI Object.

2.16 POWER MONITORING INTERFACE

A. General: Each Power Measurement Interface (PMI) device shall include the appropriate current and potential (voltage) transformers. The PMI shall be certified under UL-3111. The PMI shall perform continuous true

RMS measurement based on 32 samples-per-cycle sampling on all voltage and current signals. The PMI shall provide outputs to the FMCS based on the measurement and calculation of the following parameters: (a) current for each phase and average of all three phases, (b) kW for each phase and total of all three phases, (c) power factor for each phase and all three phases, (d) percent voltage unbalance and (e) percent current unbalance. These output values shall be hard-wired inputs to the FMCS or shall be communicated to the FMCS over the open-protocol

LAN (BacNet or Modbus).

2.17 WATER FLOW METERS

A. General: Water flow meters shall be ultrasonic-type or axial turbine style flow meters which translate liquid motion into electronic output signals proportional to the flow sensed for input into the temperature control system (TCS). Flow sensing turbine rotors shall be non-metallic and not impaired by magnetic drag. Flow meters shall be either; in-line or ‘insertion’ type as supplied by the local utilities. Accuracy shall be +/- 2% of actual reading from 0.4 to 20 feet per second flow velocities. Ultrasonic Flow Meters shall be non-insertion/clamp-on setups using Doppler technology to transmit sensor signals to the

JACE/Facility Management Control System (FMCS).

2.18 DIGITAL LIGHTING CONTROL SYSTEMS

A. General: Provide factory-fabricated Pre-Engineered Digital Lighting

Relay Panels and Components to allow FMCS integration to lighting circuits. Serial Communication protocol: BacNET™ (preferred) or Modbus™.

PART 3 - EXECUTION

3.1 INSTALLATION

25 09 00 - 26

A. All work described in this section shall be performed by system integrators or contractors that have a successful history in the design and installation of integrated control systems.