25 09 00 - Systems Integration.pdf

Louis Stokes Cleveland VA Medical Center Expand MRI Suite Project No. 541-CSI-103

Systems Integration 25 09 00 - 1

SECTION 25 09 00

SYSTEMS INTEGRATION

PART 1 - GENERAL

1.1 RELATED DOCUMENTS

A. Drawings and general provisions of the Contract, in cluding General and

Supplementary Conditions and Division 1 Specificati on Sections, apply to this Section.

1.2 SUMMARY

A. Furnish and install integrated automation systems, materials, equipment, and accessories in accordance with the s pecifications and drawings.

B. Provide completely functioning integrated automatio n system.

C. This section describes the Systems Integration scop e of work for the project. This section also coordinates the respons ibilities of the

Mechanical and Electrical trade contractors pertain ing to control products or systems, furnished by each trade, that will be integrated by this Division.

D. All labor, material, equipment and software not spe cifically referred to herein or on the plans, which are required to me et the functional intent of this specification, shall be provided wit hout additional cost to the VA.

1.3 SYSTEMS INTEGRATION CONTRACTOR

A. The Master Systems Integrator (MSI) shall connect t he building stakeholders with their building control systems an d provide useful, meaningful and important information and control ca pabilities. The MSI is responsible for the integration of building cont rol services such as

HVAC, Life Safety, Electrical Distribution, Lightin g Control, Security, CCTV, Data Centers and other controlled assets as s hown in the systems architecture. The MSI shall provide a unified data base and graphical user interface tools by collaboration with the owne rs building control needs.

B. Roles & Responsibilities: Services required but no t limited to:

1. Provide and configure all associated network device s.

2. Provide Tridium Vykon Niagara N4 hardware, devices and software.

3. Jointly develop integrated software plan with the o wners building team and vendors to make sure all systems will comm unicate properly.

25 09 00 - 2

4. Reviews and meets with owner’s building team to ens ure the building control system information will be accessi ble and useful.

5. Develop the software layer responsible for integrat ion, aggregation and communications to the building cont rol and metering systems.

6. Create and maintain graphical controls, monitors an d dashboards as defined by the functional requirements of this p roject.

7. Configure alarm interface / controls, scheduling an d user management capabilities.

8. Configure system analytics package as specified.

9. Commission connected systems for usability and sust ainability

(all the software tools should be incorporated).

10. Document software maintenance strategy and upgrade procedures.

C. Qualifications: A company and individual qualificat ion package must be submitted within 15-days of award. Provide client references for projects described within this package.

COMPANY REQUIREMENTS:

1. Shall have an in-place facility within 150 miles of the project site with technical staff, and necessary testing an d diagnostic equipment to support the proposed project.

2. Experience in implementing Niagara N4 framework in similar size and scope as this project.

3. Must have a successful history in the design and in stallation of

Niagara AX and N4 Framework.

4. Must have five (5) years consecutive licensing capa bilities with the Niagara Framework.

5. Must have minimum of three (3) employed individuals who meet

“Specific Requirements: per individual”.

6. Firms shall have specialized in and be experienced with the installation and integration of the Niagara Framewo rk. Provide the following project examples. Provide at least f ive (5) projects that are in similar size and complexity as this proposed project in the submitted qualification package:

a. List and describe a Niagara Enterprise (more than o ne building) integration project that your company ins talled and integrated in the last three (3) years.

25 09 00 - 3

b. List and describe a Niagara integration project inv olving multiple communication protocols or databases that your company installed and integrated in the last three (3) years.

c. List and describe a Niagara integration project inv olving multiple platforms such as HVAC, Lighting Control, Security, Life Safety, Utilities and other building control and or monitoring systems that your company install ed and integrated in the last three (3) years.

7. Network shall be configured and tested by a network design professional with a Cisco Certified Design Professi onal (CCDP) certification or higher.

INDIVIDUAL PERSONNEL REQUIREMENTS:

1. Must have three (3) years experience with the Niaga ra N4 and AX framework.

a. Proof of Niagara AX Certification.

b. Proof of Niagara N4 Certification.

c. Proof of Niagara 4, Level 2 Certification (On-site

Integration Lead).

2. Must have five (5) years or greater experience with Network

Design and Installation.

a. Proof of Cisco Certified Design Professional (CCDP) certification or higher.

b. Resume showing required network design and installa tion experience with references and reference contact information.

1.4 APPROVED MASTER SYSTEMS INTEGRATORS

A. AGM Energy Services

2305 E. Aurora Rd.

Suite A-7

Twinsburg, OH 44087

Attn: Andre Goosby

PH: 330-998-6695

Email: agoosby@agmenergyservices.com

25 09 00 - 4

B. Enterprise Controls Group, LLC

2305 E. Aurora Rd.

Suite A-6

Twinsburg, OH 44087

Attn: Jerry Gray

PH: 216-533-8447

Email: jgray@entcontrols.com

1.5 SYSTEM DESCRIPTION

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

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

(N4) shall connect to the VA’s local or wide area n etwork, depending on configuration. Access to the system, either locall y in each building, or remotely from a central site or sites, shall be accomplished through standard Web browsers, via the Internet and/or loca l area network. Each

JACE (N4) shall communicate to BACNet (IBC) control lers provided under

Division (230923) Temperature Controls Contractor.

B. The Cleveland VAMC has an existing dedicated IP net work for smart building technology systems. All new system integr ation equipment shall connect directly to this existing network. T he systems integrator shall coordinate with the assigned VA CO R to obtain IP addresses and other required network information.

C. The Cleveland VAMC has an existing Tridium Niagara server with enterprise licensing. All new system integration s hall be performed utilizing the Tridium Niagara N4 framework.

1.6 SUBMITTAL

A. Submittal shall consist of a JACE detail drawing de picting communications network and protocols between the JA CE and new BACNet control system and smart building technology system s IP network locations with a description of the communication t ype, media and protocol.

B. Upon completion of the work, provide a complete set of ‘as-built’ JACE detail drawings and application software on USB fla sh drive or compact disk. Drawings shall be provided as AutoCAD™ compa tible files. Eight copies of the ‘as-built’ drawings shall be provided in addition to the documents on USB flash drive or compact disk. Divi sion (230923)

Temperature Controls Contractor (TCC) and (260000) Electrical Systems

Contractor (ESC) shall provide as-builts for their portions of work.

25 09 00 - 5

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

1.7 SPECIFICATION NOMENCLATURE

A. Acronyms used in this specification are as follows:

FMCS Facility Management and Control System

TCS Temperature Control System

JACE Java Application Control En gine

IBC Interoperable BACNet Controller

GUI Graphical User Interface

WBI Web Browser Interface

POT Portable Operator’s Terminal

PMI Power Measurement Interface

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.8 DIVISION OF WORK

A. The Division (230923) Temperature Controls Contract or shall be responsible for all controllers (IBC), control devi ces, control panels, controller programming, controller programming soft ware, controller input/output and power wiring and controller networ k wiring.

B. The Division (250900) Systems Integration Contracto r shall be responsible for the Java Application Control Engine (JACE), software and programming of the JACE (N4), graphical user in terface software

(GUI), development of all graphical screens, Web Br owser pages, setup of schedules, logs and alarms, and network manageme nt as required to interface the JACE (N4) to the TCC network, global supervisory control applications, system integration and coordination a nd connection of the

JACE (N4) to the local or wide area network.

1.9 RELATED WORK SPECIFIED ELSEWHERE

A. Division (230923) Temperature Controls Contractor;

25 09 00 - 6

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

a. Interoperable BACNet Controllers and programming

b. Control panels, devices and wiring

c. Local controller and control device networks

d. Network Management for TCC system

e. Network connections to the JACEs

B. Division (260000) Electrical:

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

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

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

C. Division (280000) Fire Alarm:

1. Provide fire alarm devices, wiring, and programing.

2. Provide inputs and outputs tied into the temperatur e control system.

1.10 AGENCY AND CODE APPROVALS

A. All products of the FMCS shall be provided with the following agency approvals. Verification that the approvals exist fo r all submitted products shall be provided with the submittal packa ge. Systems or products not currently offering the following appro vals are not acceptable.

1. UL-916; Energy Management Systems

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

1.11 SOFTWARE LICENSE AGREEMENT

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

B. It shall be possible to ensure the VA can prevent u nauthorized partners from accessing the system for engineering changes.

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

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

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

ALL.

25 09 00 - 7

E. The contractor shall furnish to the VA the manufact urer's software and firmware license. Such license shall grant use of all programs and application software to VA as defined by the manufa cturer's license agreement, but shall protect manufacturer's rights to disclosure of trade secrets contained within such software.

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

1.13 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 Work and that of other crafts in equipment location, pip e, duct and conduit runs, electrical outlets and fixtures, air diffuser s, and structural and architectural feature.

PART 2 - MATERIALS

2.1 GENERAL

A. The Facility Management Control System (FMCS) shall be comprised of a network of interoperable, stand-alone digital contr ollers, a computer system, graphical user interface software, printers , network devices and other devices as specified herein.

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

2.2 OPEN, INTEROPERABLE, INTEGRATED ARCHITECTURES

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

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

(OOT) for representation of all data and control de vices within the system. In addition, adherence to industry standar ds including ANSI /

ASHRAE™ Standard 135-1995, BACNet and Tridium to as sure interoperability between all system components is r equired. For each device that does not have BACNet certification, the device supplier

25 09 00 - 8 must provide an XIF file for the device. For each BACNet device, the device supplier must provide a PICS document showin g the installed device’s compliance level. Minimum compliance is L evel 3; with the ability to support data read and write functionalit y. Physical connection of BACNet devices shall be via Ethernet/ Ethernet IP and

MS/TP. All points must be open and discoverable.

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

D. The supplied system must incorporate the ability to access all data using standard Web browsers without requiring propr ietary operator interface and configuration programs. This data sh all reside on the existing server for all database access. Systems r equiring proprietary database and user interface programs shall not be a cceptable.

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

1. Maximum acceptable response time from any alarm occ urrence (at the point of origin) to the point of annunciation s hall not exceed 5 seconds for network connected user interfa ces.

2. Maximum acceptable response time from any alarm occ urrence (at the point of origin) to the point of annunciation s hall not exceed 60 seconds for remote or dial-up connected u ser interfaces.

2.3 NETWORKS

A. The Local Area Network (LAN) shall be a 10/100 Mega bits/sec Ethernet network supporting BACNet, Java, XML, HTTP, and COR BA IIOP for maximum flexibility for integration of building data with e nterprise information systems and providing support for multi ple Java Application

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

B. Local area network minimum physical and media acces s 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

25 09 00 - 9

A. Remote Access.

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

2.5 JAVA APPLICATION CONTROL ENGINE (JACE)

A. The 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) Temperatu re Controls and

(260000) Electrical Systems. It is the responsibil ity of the Systems

Integration Contractor to coordinate with the Divis ion (230923)

Temperature Controls Contractor and (260000) Contra ctors to determine the quantity and type of devices.

B. The Java Application Control Engine (JACE) shall be universal Tridium and BACNet IP. It shall provide the interface betw een the LAN or WAN and the BACNet IP DDC System, and provide global su pervisory control functions over the control devices connected to the JACE (N4). JACE shall include Tridium licenses for each required po int plus an additional 50% for future expansion, programming an d graphics. Must be unlocked and open. 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 Universal Tridium and BACNet IP cont roller data

7. Network management functions for all Modbus based d evices

8. Storage capacity shall store trend data for 500 dat a points at 15 minute intervals for 14 days.

C. The Java Application Control Engine (JACE) must pro vide the following hardware features as a minimum:

1. Two Ethernet Ports – 10/100 Mbps

2. Two RS-232 port

25 09 00 - 10

3. One RS-495 non-isolated port

4. Two optional card slots

5. One BACNet interface port

6. One LonWorks Interface Port – 78KB FTT-10A

7. Provide Modbus Capability

8. Integral UPS with Battery Backup

9. Flash memory for long term data backup. (1 gigabyt e storage capacity)

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

0 to 55°C

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

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

E. The shall turn over to the VA the following JACE to ols:

1. Controller configuration tools.

2. JACE programming tools

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

Intranet/Internet.

G. 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-ar ea network.

3. Alarm generation shall be selectable for annunciati on type and acknowledgement requirements including but limited to:

a. To alarm

b. Return to normal

c. To fault

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

security, HVAC, Fire, etc.

25 09 00 - 11

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

6. Provide alarm generation from binary object “runtim e” and /or event counts for equipment maintenance. The user s hall be able to reset runtime or event count values with appropr iate password control.

H. Control equipment and network failures shall be tre ated as alarms and annunciated.

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

1. Screen message text

2. Email of the complete alarm message to multiple rec ipients.

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 ala rm printer

6. Audio messages

J. The following shall be recorded by the JACE for eac h 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 acknowl edgement.

5. Number of occurrences since last acknowledgement.

K. Alarm actions may be initiated by user defined prog rammable objects created for that purpose.

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

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

N. Provide a “query” feature to allow review of specif ic alarms by user defined parameters.

25 09 00 - 12

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

P. 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 objec ts, resident in the

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

1. Designating the log as interval or deviation.

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

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

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

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

C. All log data shall be stored in a relational databa se in the JACE and the data shall be accessed from a server (if the sy stem 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 XM L 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.

25 09 00 - 13

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

1. Archive on time of day

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

3. Archive when log has reached it’s user-defined capa city 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 a ctivities performed on the UNC. Provide the ability to specify a buffe r size for the log and the ability to archive log based on time or whe n 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 follo wing data:

1. Time and date

2. User ID

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

2.8 DATABASE BACKUP AND STORAGE

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

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

B. Copies of the current database and, at the most rec ently saved database shall be stored in the JACE. The age of the most r ecently 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 fo rmats are acceptable as well as long as XML format is supported.

2.9 GRAPHICAL USER INTERFACE SOFTWARE

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

It shall include a tree view (similar to Windows Ex plorer) for quick viewing of, and access to, the hierarchical structu re of the database.

In addition, menu-pull downs, and toolbars shall em ploy buttons, commands and navigation to permit the operator to p erform tasks with a minimum knowledge of the HVAC Control System and ba sic computing skills. These shall include, but are not limited t o, forward/backward buttons, home button, and a context sensitive locat or line (similar to

25 09 00 - 14 a URL line), that displays the location and the sel ected object identification.

B. Real-Time Displays: The GUI, shall at a minimum, s upport the following graphical features and functions:

1. Graphic screens shall be developed using any drawin g package capable of generating a GIF, BMP, or JPG file forma t. Use of proprietary graphic file formats shall not be accep table. In addition to a graphic background, the GUI shall sup port the use of scanned pictures.

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

3. Graphics shall support layering and each graphic ob ject shall be configurable for assignment to one a layer. A mini mum of six layers shall be supported.

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

a. Schedule times will be adjusted using a graphical s lider, without requiring any keyboard entry from the opera tor.

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

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

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

C. System Configuration: At a minimum, the GUI shall p ermit the operator to perform the following tasks, with proper passwor d access:

1. Create, delete or modify control strategies.

2. Add/delete objects to the system.

3. Tune control loops through the adjustment of contro l loop parameters (If exposed in controller to LON or BACN et).

25 09 00 - 15

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

LON or 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 a nd initiate the recording of values automatically.

D. 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 sh all provide the relevant data for that particular screen. Addition al help information shall be available through the use of hypertext. Al l system documentation and help files shall be in HTML forma t.

E. Security: Each operator shall be required to log o n to that system with a user name and password in order to view, edi t, 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 oper ator password shall be able to restrict the operators’ access for viewi ng and/or changing each system application, full screen editor, and ob ject. 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.

F. System Diagnostics: The system shall automatically monitor the operation of all workstations, printers, modems, ne twork connections, building management panels, and controllers. The f ailure of any device shall be annunciated to the operator.

G. Alarm Console:

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

2. When the Alarm Console is enabled, a separate alarm notification window will supersede all other windows on the desk top and shall not be capable of being minimized or closed by the operator.

This window will notify the operator of new alarms and un-

25 09 00 - 16 acknowledged alarms. Alarm notification windows or banners that can be minimized or closed by the operator shall no t be acceptable.

2.10 WEB BROWSER CLIENTS

A. The system shall be capable of supporting an unlimi ted number of clients using a standard Web browser. Systems requ iring additional software (to enable a standard Web browser) to be r esident on the client machine, or manufacture-specific browsers sh all not be acceptable.

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 p rocessor 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 pro vide the same interface methodology as is provided by the Graphic al User Interface.

Systems that require different views or that requir e 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 re quired. 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 th e same screens used for the Web browser client. Any animated grap hical objects supported by the GUI shall be supported by the Web browser interface.

3. HTML programming shall not be required to display s ystem graphics or data on a Web page. HTML editing of the Web pag e shall be allowed if the user desires a specific look or form at.

4. Storage of the graphical screens shall be in the Ja va Application

Control Engine (JACE), and the N4 server.

25 09 00 - 17

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

6. Users shall have administrator-defined access privi leges.

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

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

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

2. Holidays shall be set by using a graphical calendar , without requiring any keyboard entry from the opera tor.

b. Commands to start and stop binary objects shall be done by right-clicking the selected object and selecting th e 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.

2.11 SUPERVISORY SOFTWARE AND HARDWARE

A. An existing central server located at the VETERANS AFFAIRS MEDICAL

CENTER Building, Cleveland, Ohio; shall be utilized . The server shall support all Java Application Control Engine (JACE) connected to the customer’s network whether local or remote.

B. Local connections shall be via an Ethernet LAN. Re mote 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

25 09 00 - 18 accessed from a remote Graphical User Interface (GU I) or from a standard Web browser (WBI) by connecting to the ser ver.

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

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

2. Distributed Control: The server shall provide the a bility 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 implement the BACNet Command Prior itization scheme (16 levels) for safe and effective contentio n resolution of all commands issued to Java Application Control Engine (JACE).

5. Each Java Application Control Engine (JACE) support ed by the server shall have the ability to archive its log da ta, alarm data and database to the server, automatically. Archiv ing options shall be user-defined including archive tim e and archive frequency.

6. The server shall provide central alarm management f or all Java

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

a. Routing of alarms to display, printer, email and pa gers.

b. View and acknowledge alarms.

c. Query alarm logs based on user-defined parameters.

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

Network Area Controllers Java Application Control E ngine (JACE) supported by the server. Log data shall include pr ocess logs, runtime and event counter logs, audit logs and erro r 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.

2.12 SYSTEM PROGRAMMING

A. The Graphical User Interface software (GUI) shall p rovide the ability to perform system programming and graphic display e ngineering as part of a complete software package. Access to the prog ramming functions

25 09 00 - 19 and features of the GUI shall be through password a ccess as assigned by the system administrator.

B. A library of control, application, and graphic obje cts shall be provided to enable the creation of all applications and user interface screens. Applications are to be created by selecti ng the desired control objects from the library, dragging or pasti ng 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 cre ated 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 obj ect property may be connected to display its current value on a user di splay. Systems requiring separate software tools or processes to c reate applications and user interface displays shall not be acceptable .

C. Programming Methods

1. Provide the capability to copy objects from the sup plied libraries, or from a user-defined library to the us er’s application. Objects shall be linked by a graphica l linking scheme by dragging a link from one object to anothe r. 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 posit ioned on the page and shall show link identification for links t o objects on other pages for easy identification. Links will va ry in color depending on the type of link; i.e., internal, exte rnal, hardware, etc.

2. Configuration of each object will be done through t he object’s property sheet using fill-in the blank fields, list boxes, and selection buttons. Use of custom programming, scri pting language, or a manufacturer-specific procedural lan guage 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 dia gnosis of the logic execution. When off-line (debug), the monito r mode shall

25 09 00 - 20 allow the user to set values to inputs and monitor the logic for diagnosing execution before it is applied to the sy stem.

4. All programming shall be done in real-time. Systems requiring the uploading, editing, and downloading of database obj ects 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 duplicatio n.

2.13 TRIDIUM NETWORK MANAGEMENT

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

Tridium N4 networks. These tools shall manage a dat abase for all

Tridium devices by type and revision and shall prov ide a software mechanism for identifying each device on the networ k. These tools shall also be capable of defining network data conn ections between other devices, known as “binding”. Systems requiri ng the use of third party Tridium network management tools shall not be accepted.

B. Network management shall include the following serv ices: device identification, device installation, device configu ration, device diagnostics, device maintenance and network variabl e binding.

C. The Network configuration tool shall also provide d iagnostics 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 BACN et devices and newly added devices are part of a single network manageme nt database.

E. The network management database shall be resident i n the Java

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

2.14 OBJECT LIBRARIES

25 09 00 - 21

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 bei ng copied and pasted into the user’s database and shall be organized acc ording to their function. In addition, the user shall have the cap ability 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 her e, the supplier of the system shall maintain an on-line accessible (ov er the Internet) library, available to all registered users to provi de new or updated objects and applications as they are developed.

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

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

1. Scheduling Object: The schedule must conform to th e schedule object as defined in the BACNet specification, prov iding 7-day plus holiday & temporary scheduling features and a minimum of 10 on/off events per day. Data entry to be by graphic al 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, prov iding 12-month calendar features to allow for holiday or special e vent data entry. Data entry to be by graphical “point-and-cli ck” selection.

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

3. Duty Cycling Object: Provide a universal duty cycl e object to allow repetitive on/off time control of equipment a s an energy conserving measure. Any number of these objects ma y be created to control equipment at varying intervals

4. Temperature Override Object: Provide a temperature override object that is capable of overriding equipment turn ed off by other energy saving programs (scheduling, duty cycl ing etc.) to maintain occupant comfort or for equipment freeze p rotection.

5. Start-Stop Time Optimization Object: Provide a sta rt-stop time optimization object to provide the capability of st arting

25 09 00 - 22 equipment just early enough to bring space conditio ns to desired conditions by the scheduled occupancy time. Also, allow equipment to be stopped before the scheduled un-occ upancy time just far enough ahead to take advantage of the buil ding’s

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

6. Demand Limiting Object: Provide a comprehensive de mand-limiting object that is capable of controlling demand for an y selected energy utility (electric, oil, and gas). The objec t shall provide the capability of monitoring a demand value and predicting (by use of a sliding window prediction a lgorithm) the demand at the end of the user defined interval peri od (1-60 minutes). This object shall also accommodate a uti lity 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 loa ds or modify equipment set points to effect the desired energy r eduction. If the list of sheddable equipment is not enough to re duce the demand to below the set point, a message shall be d isplayed 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 t o be shed in either a fixed or rotating order to control which e quipment is shed the most often. Upon suitable reductions in d emand, the demand-limiting object shall restore the equipment that was shed in the reverse order in which it was shed. Each sh eddable 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 f ollowing functions.

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

BACNet specification.

1. Analog Input Object: Minimum requirement is to com ply 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 - 23 filter property to prevent nuisance alarms caused b y temporary excursions above or below the user defined alarm li mits.

2. Analog Output Object: Minimum requirement is to co mply with the

BACNet standard for data sharing.

3. Binary Input Object: Minimum requirement is to com ply 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 i n 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 co mply with the

BACNet standard for data sharing. Properties to en able minimum on and off times for equipment protection as well a s interstart delay must be provided. The BACNet Command Priorit ization priority scheme shall be incorporated to allow mult iple control applications to execute commands on this object wit h the highest priority command being invoked. Provide sixteen le vels of priority as a minimum. Systems not employing the BA CNet 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 individ ual property must be adjustable as well as to be disabled to all ow proportional control only, or proportional with int egral control, as well as proportional, integral and derivative co ntrol.

6. Comparison Object: Allow a minimum of two analog o bjects to be compared to select either the highest, lowest, or e quality between the two linked inputs. Also, allow limits t o be applied to the output value for alarm generation.

7. Math Object: Allow a minimum of four analog object s to be tested for the minimum or maximum, or the sum, difference, or average of linked objects. Also, allow limits to be applied t o 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 def ine object

25 09 00 - 24 behavior. Provide a library of functions including math and logic functions, string manipulation, and e-mail as a min imum. 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 equipme nt. An example is to link the return fan to the supply fan such th at when the supply fan is started, the return fan object is als o started automatically without the user having to issue sepa rate commands or to link each object to a schedule object. In ad dition, the control loops, damper objects, and alarm monitoring (such as return air, supply air, and mixed air temperature o bjects) will be inhibited from alarming during a user-defined pe riod after startup to allow for stabilization. When the air h andler is stopped, the interlocked return fan is also stopped , the outside air damper is closed, and other related objects wit hin the air handler unit are inhibited from alarming thereby el iminating nuisance alarms during the off period.

10. Temperature Override Object: Provide an object whos e purpose is to provide the capability of overriding a binary ou tput to an

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

11. Composite Object: Provide a container object that allows a collection of objects representing an application t o be encapsulated to protect the application from tamper ing, or to more easily represent large applications. This obj ect must have the ability to allow the user to select the appropr iate 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 E ngine (JACE). At a

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

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

Provide BACNet manufacturer-specific objects to fac ilitate simple integration of these devices. All network variable s defined in the BACNet profile shall be supported. Information (type and function) regarding network variables not defined i n the BACNet profile shall be provided by the device manufacture r.

2. For devices not conforming to the LonMark standard, provide a dynamic object that can be assigned to the device b ased on network variable information provided by the device manufacturer.

Device manufacturer shall provide an XIF file and d ocumentation for the device to facilitate device integration.

3. For BACNet devices, provide the following objects a t a minimum:

a. BACNet AI

b. BACNet AO

c. BACNet BI

d. BACNet BO

e. BACNet Device

4. For each BACNet object, provide the ability to assi gn the object a BACNet device and object instance number.

5. For Modbus devices, provide the ability to interfac e to specific

“data registers” as documented and supplied by the equipment vendor. Such as;

a. Modbus GenericBI

b. Modbus GenericBO

c. Modbus GenericAI

d. Modbus GenericAO

e. Modbus 6xRecord

f. Modbus BitsToRegister

g. Modbus PresetCoil

h. Modbus PresetRegister

i. Modbus RegisterToBits

2.15 DDE DEVICE INTEGRATION

A. The Java Application Control Engine (JACE) shall su pport the integration of device data via Dynamic Data Exchang e (DDE), over the

25 09 00 - 26

Ethernet Network. The Java Application Control Eng ine (JACE) shall act as a DDE client to another software application tha t functions as a DDE server.

B. Provide the required objects in the library, inc luded with the

Graphical User Interface programming software, to s upport the integration of these devices into the FMCS. Object s 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.

PART 3 - EXECUTION

3.1 INSTALLATION

A. All work described in this section shall be perform ed by system integrators or contractors that have a successful h istory in the design and installation of integrated control systems. Th e installing office shall have a minimum of five years of integration e xperience and shall provide documentation in the submittal package veri fying the company's experience.

B. Install system and materials in accordance with man ufacturer’s…