13402_EMCS_System_revised.pdf

Energy Monitoring and Control System Ph 2 FA4626-18-R-0013 Malmstrom AFB NZAS 14-3000 Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 1

SECTION 13402

EMCS SYSTEM

PART 1 - GENERAL

1.1 WORK INCLUDED

A. This Section specifies the requirements necessary to provide the Energy Management and Control System (EMCS) including necessary hardware, software programming and commissioning.

B. Provide EMCS system hardware necessary for continuous operation including all servers and operator workstations.

C. Provide all EMCS system software including necessary licenses and operating system software.

D. Provide configuration and programming for a complete and operable system.

E. Provide installation, testing and commissioning required to ensure a fully functional system.

1.2 RELATED WORK

A. Use this Section in conjunction with the following other specifications and related Contract Documents to establish the total requirements for referenced software.

1. The Contract.

2. Division 1 Sections included in the Project Specifications.

3. Section 15903 - Direct Digital Control Systems.

4. System Drawings.

B. CAUTION: Use of this Section without including the above-listed items results in omission of basic requirements.

1.3 SYSTEM DESCRIPTION

A. The Energy Management Control System (EMCS) system consists of data servers connected by an Ethernet network along with local and remote Operator Workstations which enable users to monitor and control HVAC equipment. This system is considered as a separate entity from the individual building DDC control systems which are described elsewhere.

B. The EMCS system will be required to monitor and control systems connected to the various DDC building controllers. There will be a variety of manufacturers’ equipment but all of the building controllers will communicate with the EMCS system via BACnet.

C. The EMCS system will provide the following functions:

1. Graphical visualization and control of the HVAC equipment in the buildings connected to the system.

2. Centralized alarm and event management.

3. Reporting capability.

4. Centralized data acquisition system for storage and retrieval of HVAC, utilities metering and environmental data, to allow comparison of current and historical data for maintenance and energy management purposes.

D. EMCS System Users: The system shall be capable of supporting five concurrent users, generally located in the control room of Building 471. These users can be connected to the system as full clients or through a web server. The ability to add additional clients at other locations will be requested in the future. An architecture that can accommodate these future users is required.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 2

E. EMCS System Capacity: The EMCS system shall be designed for monitoring and control of the 33 buildings included in this project as well as the 27 existing buildings being monitored. The system shall be capable of expansion to include the entire site (i.e. approximately 179 buildings).

Provide servers, workstations and software licenses in accordance with these requirements.

F. Network communications and architecture: The EMCS system will utilize a distributed client/server system architecture. All Ethernet network functions including managed switches in accordance with ETL 11-1 Section 8.1.7, fiber and copper cabling will be provided per the telecom system specification sections, in Division 16.

1.4 QUALIFICATIONS

A. The Contractor must have directly comparable experience for projects of similar scope and size.

B. A minimum of 5 years of experience in design, fabrication, installation testing and commissioning of EMCS systems is required.

1.5 DEFINITION OF ACCEPTANCE

A. System acceptance is defined as that point in time when the following requirements have been fulfilled:

1. Submittals and documentation have been submitted, reviewed, and approved.

2. The Contractor has successfully completed testing requirements cited herein.

3. Training programs have been completed.

4. System punch list items have been resolved and accepted by the Government.

1.6 WARRANTY

A. Warrant supplied hardware and software as follows, unless specifically stated otherwise:

1. Warrant against defects in materials and operation for a period of 1 year (minimum) following the system acceptance by the Government.

2. Warrant as merchantable and suitable for the purpose intended and provide the results required by the Drawings, Sequence of Operations (SOOs), system block diagram and specifications.

3. Provide repairs and replacements necessitated by defects in hardware and software.

1.7 QUALITY ASSURANCE

A. Formal and documented quality assurance (QA) is required. Provide a QA program that monitors the quality and conformance of each completed function.

B. Provide the selected manufacturer’s latest standard, fully supported version of EMCS software.

C. Provide technical bulletin subscription for notification of hardware/software issues and patches.

D. All binary or machine executable public domain software products and other software products with limited or no warranty such as those commonly know as freeware or shareware are not used in DOd information systems unless they are necessary for mission accomplishment and there are no alternative IT solutions available.

1.8 SUBMITTALS

A. Refer to the Submittal Schedule at the end of Part 3 for a list of submittal requirements for this Section.

1.9 PROJECT RECORD DOCUMENTS

A. Provide product documentation of sufficient quality to allow the Government to modify, add, delete, or reconfigure the software system displays, reports, logs, data base, calculations, displays and system parameters.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 3

B. Provide EMCS operating and maintenance (O&M) manuals. Provide five electronic copies (burned CD) of the latest version of project configuration, screens, I/O point database and all other documents maintained and updated on the development server as follows:

1. Network configuration files.

2. EMCS configuration files.

3. EMCS screens.

4. EMCS tag to I/O address cross-reference.

5. As-built SOO documents.

6. Redlined P&ID Drawings.

PART 2 - PRODUCTS

2.1 EMCS HARDWARE

A. Provide two (2) semi-ruggedized portable laptop computers to be turned over to the Government equivalent to a Dell latitude 14 Rugged and all necessary software to access, troubleshoot and maintain and in general provide full functionality for the building DDC systems minimum hardware requirements.

1. 2.0 GHz Quad Core processor with 8 GB of RAM.

2. Supported operating system (e.g Windows software.)

3. Serial port, parallel port.

4. 2 PCMCIA slots or 2 USB slots

5. 10/100 MBS Ethernet network interface.

6. 256 GB solid state hard disk.

7. 24X DVD/CD-RW drive.

8. Touchpad mouse functionality.

9. Extended life batteries, power supply and carrying case.

10. Provide Desk top docking stations.

11. Software Requirements: In general the software requirements for a laptop are identical to those for an operator workstation.

B. JACE (Java Application Control Engine) – The interface between the building control system and the central control system via the network. The JACE shall provide connectivity and transfer of information between the building systems (HVAC, metering, etc…) via the Niagara framework. The JACE shall provide data transfer over the network using BACnet over IP protocol to the existing established base-wide central control system.

The JACE shall have an embedded Graphical Engineering Tool allowing setup and edits to be performed from an Internet browser without any additional software at the PC, except for initial commissioning of the JACE. With network connectivity and Webserving capability, the JACE controller shall provide integrated control, supervision, data logging, history, alarming, scheduling and network management. It shall allow streaming of data and rich graphical displays to a standard Web browser via an Ethernet, or remotely over the local network.

The JACE controller shall have standard drivers along with optional IO and field bus expansion modules for flexibility and expandability. The JACE controller shall operate with Niagara 4, the latest version of the Niagara Framework®.

1. Processor: TI AM3352: 1GHz, ARM® Cortex™-A8, or equal

2. 1GB DDR3 SDRAM

3. Removable micro-SD card with 4GB flash total storage/2GB user storage

4. USB type A connector

5. Back-up and restore support

6. (2 each) isolated RS-485 with selectable bias

7. (2 each) 10/100MB Ethernet ports

8. Secure boot, software IP protection

9. 24VAC/DC power supply

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 4

10. Runs Niagara 4.1 and later

11. Real time clock

12. Battery-less

C. Software Requirements:

1. The following software with license agreements shall be provided.

a. Laptops:

1) Microsoft Windows 7 Enterprise or newer (coordinate with controls software).

2) Microsoft Office Professional Edition (latest version).

3) DDC System Operator Workstation Application(s) (latest version).

4) Any other software required to deliver the specified performance.

5) Anti-virus software in accordance with ETL 11-1 requirements.

2. All IT systems must be configured per DISA Security Implementation and Security Guides (STIGs)

3. Recovery procedures and technical system features exist to ensure that recovery from system backups are done in a secure and verifiable manner. Circumstances that can inhibit a trusted recovery are documented and appropriate mitigating procedures have been put in place.

D. EMCS Hardware:

1. Laptop Acceptable Manufacturers:

a. Hewlett Packard.

b. Dell.

c. Others with government contracting officer approval by submittal.

2.2 EMCS SOFTWARE

A. Software Updates:

1. Provide yearly updates of EMCS software, BACnet controllers, and JACE devices for a period of no less than 5 years.

2. All controllers and devices requiring integration shall be updated to latest version as part of project.

3. DDC controls installed in building shall be installed with software versions matching existing EMCS software versions at the time of construction. Addition of devices to EMCS system shall not require update of software versions to existing devices.

4. Comprehensive set of procedures is implemented that tests all patches, upgrades, and new AIS applications prior to deployment.

5. Web application auditing needs to be configured and web security implementation guides (STIGs) need to be applied.

6. All new building controllers shall be software compatible with existing server and operator workstation software and shall enable all the functions outlined in this Section.

B. Laptops:

1. Hardware Communication Function:

a. The Operator Work Station (OWS) shall extract data from the hardware environment and move the data to the data server and/or present the data to the presentation system.

b. The OWS shall extract data from the data server and present the data to the data presentation system.

c. The OWS shall track operator actions at the presentation system and write a record of activities to the data server.

2. BACnet Compliance:

a. The OWS shall be able to initiate a “Who Is” request to the network.

b. The OWS shall respond to a “Who Is” request from another BACnet device with an “I

Am” response.

c. The OWS shall be able to read binary and analog data from BACnet devices that support the reading of data.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 5

d. The OWS shall be able to write binary and analog data to BACnet devices that support the writing of data from a BACnet OWS.

e. The OWS shall be able to receive alarm messages from BACnet devices that export alarm messages.

f. The OWS shall be able to acknowledge alarms from BACnet devices.

g. The OWS shall be able to edit time schedule parameters in BACnet devices that support the editing of time schedule parameters from a BACnet OWS.

h. The OWS shall be able to retrieve a collection of trend samples from a BACnet device that stores the data and permits the export of that data to a BACnet OWS.

i. The OWS shall be able to initiate time synchronization commands to all BACnet devices that support the receipt of time synchronization commands from a BACnet

OWS.

3. Data Presentation: Data shall be presented in the following formats.

a. Points lists with dynamic presentation of data. The operator shall be able to create custom point lists with data that originates from multiple devices. A point may be dynamic data from a controller or a configuration parameter to be written to a controller by the operator.

b. Graphic pages with dynamic presentation of data on a visual diagram that represents a building, a floor plan, a cross section of a mechanical system or a table of data.

c. Graphical presentation of historical trend log data plotted against time.

d. Graphical presentation of real time trend data plotted against time.

e. Alarm Presentation:

1) Unless restricted by a reduction in viewing authority, an operator shall be able to view alarms for all systems in a single alarm list.

2) Custom alarm views configured for select categories of alarms shall present only the alarms specified.

3) Alarm messages shall include identifying information and the signal value or state at the time of the alarm.

f. Event Presentation:

1) Unless restricted by a reduction in viewing authority, an operator shall be able to view an event log that chronologically captures all activity created by the system and operator actions.

2) Custom event views for select categories of events shall present only the events specified.

g. Time Schedules:

1) Each time schedule shall have the ability to issue a minimum of 10 start and

10 stop commands for the week. The requirements for start and stop commands may be different for each day of the week.

2) Each time schedule shall also include a holiday component where a holiday is identified by the date and duration (1 day, 2 days, etc.). The time schedule shall support a unique set of start and stop commands for each holiday. The time schedule shall support a minimum of 20 holidays per year. Holiday schedules shall take precedence over standard schedules during the holiday period. Holidays that are date specific shall roll over from year to year without operator programming action.

3) There shall be a mechanism to link a master time schedule editor at an OWS to multiple time schedules in various Building Controllers. Once linked, whenever the master time schedule is changed at an OWS, the new time schedule parameters shall be downloaded to all of the linked time schedules. This concept shall apply to both standard schedules and holiday schedules.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 6

4) Time schedule data will be stored locally in the building or lower level controllers.

An operator or technician connecting to these controllers will be able to see the time schedule data for monitoring and troubleshooting purposes. If a change is made at the local level, this must be accessible and viewed at the EMCS level and vice versa. The schedules and programs shall stay in the last state they were edited and not be automatically overwritten.

h. The system shall support a configuration that:

1) Causes the system to go into standby mode (user is logged out but the current screen is still displayed) after a specific period of inactivity.

2) Automatic system logout after a specific period of inactivity.

4. Operator Access and Privileges:

a. There shall be a minimum of four privilege levels.

1) System Administrator:

a) No limitations.

b) Only level that can assign or delete users and assign or modify privileges.

2) Engineer:

a) View data in any format.

b) Acknowledge alarms.

c) Inhibit alarms.

d) Exercise control actions.

e) Edit the presentation of data.

f) Modify the system.

3) Operator:

a) View data in any format.

b) Acknowledge alarms.

c) Exercise control actions.

4) Viewer:

a) View data in any format.

b. The level assigned to a specific user shall be the maximum level that can be used anywhere in the system. The software shall provide the capability to reduce a user’s level from his or her maximum level to a lower level on a per building or system basis.

This may be accomplished on a per object basis within the database or by the application of additional security levels beyond the basic four levels.

c. Signing on to the system shall require a user name and password. When the password is typed in, it shall not be shown on the screen. Password shall be per ETL 11-1 para 8.1.3.

1) Access is denied after 3 unsuccessful login attempts.

2) The number of access attempts is limited over a period of time.

3) A time delay control system is employed.

d. The software shall provide the capability to establish groups of users with the same privileges. Once assigned to the group, the user shall automatically have the maximum privileges and the selectively reduced privileges assigned to the group. Access procedures enforce the principles of separation of duties and “least privilege.” Access to the privileged accounts shall be limited to privileged users in accordance with control ECLP-1 DoDI 8500.2.

e. The software shall provide the capability to set user profiles that enable assigning a specific home graphic page, alarm view, and event view.

f. DoD approved warning banner shall be used so that all users are warned that they are entering a Government information system, and are provided with appropriate privacy and security notices to include statements informing them that they are subject to monitoring, recording and auditing.

5. Operator Actions:

a. Given the appropriate authority, an operator from an operator workstation shall be able to:

1) View all data that is presented in the forms described previously.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 7

2) Acknowledge alarms.

3) Manually control both physical input and physical output points.

4) Edit both independent and master time schedules.

5) Initiate real time trend logging.

6) Manually initiate reports.

7) Initiate system backups for the database and trend log data.

8) Customize the layout of the operator workstation presentation which shall then be the default for that user.

b. The operator shall be able to execute the above tasks on data from any of the operator workstations.

c. The system shall support the use of Electronic Signature system wide or on a per user basis.

d. Microsoft Office Professional Edition, latest edition.

e. Any other software required to deliver the specified performance.

f. All of the operator workstations shall be operable simultaneously.

6. Engineering Actions:

a. The software shall, as a minimum, enable the following engineering functions from each of the operator workstations:

1) Create graphic pages for the presentation of dynamic data on visual images of buildings or equipment.

2) Create reports for the presentation of historical data in an organized format.

3) Create time schedules.

4) Create trend logs in any of the field level devices and assign a dynamic variable from a field bus device to be trended.

5) Setup long term storage of trend log data on the data server computer and the automatic transfer of the trend log data to the data storage tables in the SQL database.

6) Configure the system to create backups of the database and all application and supporting databases on a scheduled basis.

7) Setup user groups and individual users and establish authority levels for each group and individual user.

8) Any additional tasks defined later in this document or required to deliver a fully functional system.

b. Microsoft Office Professional Edition, latest edition.

c. Any other software required to deliver the specified performance.

C. Web Server Software (If Required):

1. Web Servers may be used to provide the additional operator workstations required for this project. If this technology is used, the web server will be restricted to the certain clients identified by the Government and Engineer.

2. This software shall enable operators to access the system from remote computers using only browser software. The software shall allow for a minimum of five concurrent users. Once connected to the system the operators shall be able to execute the following tasks:

a. View dynamic data in a real time environment in both point list format and in a graphical page format.

b. View and acknowledge alarms.

c. Adjust time schedule parameters.

d. View historical trend data in table and graph formats.

e. View dynamic real time trends in graph format.

f. Run established reports.

g. Manually adjust application parameters.

h. Manually override physical inputs (sensor values) and force a specific value as an input to control logic.

i. Manually override physical outputs (end devices) and force a specific value regardless of the command from the control logic.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 8

D. Graphic Page Creation and Editing:

1. The Graphics Editor portion of the Engineering Software shall provide the following minimum capabilities:

a. Create and save symbols.

b. Create and save pages.

c. Group and ungroup symbols.

d. Modify an existing symbol.

e. Modify an existing graphic page.

f. Rotate and mirror a symbol.

g. Place a symbol on a page.

h. Place analog dynamic data in decimal format on a page.

i. Place binary dynamic data using state descriptors on a page.

j. Create motion through the use off gif, jpeg or bmp files.

k. Place test mode indication on a page.

l. Place manual mode indication on a page.

m. Place links using a fixed symbol or flyover on a page.

1) Links to other graphics.

2) Links to notes.

3) Links to time schedules.

n. Assign a background color.

o. Assign a foreground color.

p. Place alarm indicators on a page.

q. Change a symbol color as a function of an analog variable.

r. Change a symbol color as a function of a binary state.

s. Change symbols as a function of a binary state.

t. All symbols used by the Contractor in the creation of graphic pages shall be saved to a library file for use by the Owner.

E. Event Logging:

1. The system shall maintain a log of all operator activity, system messages, alarms, and alarm acknowledgments.

2. Operator activity is defined as any action by an operator such as changing the value of an application parameter, modifying a program, acknowledging an alarm, logging on, logging off, etc. Any change in the system caused by operator action shall be part of the log. The log shall include the event, the time of the event, the part of the system affected, and an identification of the operator and the OWS from which the change was made.

3. When the event deals with a value change, both the original and new values shall be part of the event record.

4. The Event Log shall be exportable to a report format that is printable.

5. The System Administrator shall be able to archive the event log.

6. The Event Log shall have a search function with assignable criteria to identify subsets of the event log such as all points placed under manual control, etc.

F. Alarm Generation and Processing:

1. Alarm creation is a two-part process. The creation of a binary alarm indication is accomplished in a field level device where a binary state of zero shall indicate a normal condition and a binary state of one shall indicate an alarm condition. The binary alarm condition is read within a Building Controller. The Building Controller shall assign a descriptive message, a category or priority number and a date and time stamp to the alarm and forward the information to the OWS in accordance with an alarm routing table.

2. Alarm parameters such as high limits, low limits, time to state, binary alarm conditions are setup within the programming of the field level devices. These parameters shall be viewable and editable in point lists and on configuration graphic pages.

3. The alarm message shall be descriptive.

a. Building identification.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 9

b. System identification.

c. Device identification.

d. Date.

e. Time to the second.

f. Nature of the Alarm:

1) High value.

2) Low value.

3) Fail to start.

g. Value or state at the time of the alarm.

4. When the operator acknowledges the alarm, there shall be an opportunity to enter a message that becomes a permanent part of the alarm record recorded in the event log.

5. The system shall support the association of graphic pages, trend charts, reports and text documents with specific alarms.

a. The operator shall have the ability to configure the system to auto-launch a specific graphic page when the alarm occurs.

b. The system shall support the assignment of wav files to alarm signals on graphic pages.

c. The operator shall have the ability to launch a specific trend chart from the alarm window when the alarm occurs.

d. The operator shall have the ability to launch a specific text document when the alarm occurs.

e. An associated report shall automatically execute and write to the hard disk on the OWS when the alarm occurs. Configurations options shall include overwriting the previous report or creating a new file.

6. The system shall use selectable multiple colors on alarm messages for each of the following conditions:

a. Alarm condition exists and has not been acknowledged.

b. Alarm condition has returned to normal but was never acknowledged.

c. Alarm condition exists and has been acknowledged.

7. When an alarm condition no longer exists and has been acknowledged, it shall no longer be displayed in the alarm viewer but it shall be permanently recorded in the event list.

8. The Alarm Routing Table shall support the following:

a. Multiple workstations at any time.

b. Specific workstations at particular times (to include all of the time as one choice).

c. Pagers.

d. Email addresses via simple mail transfer protocol (SMTP; RFC 821).

e. Permanent comprehensive system wide alarm file.

f. Specific alarm file based on a building or equipment identification.

g. One or more alarm printers at any time.

h. Specific alarm printers at specific times.

i. Rerouting of alarms to a backup receiver when an acknowledgement has not been entered into the system within a specified time.

9. The system shall have a default audible indicator generated by the computer when an alarm is received.

10. Once an alarm is acknowledged at one OWS, it shall display as acknowledged at all operator workstations.

11. An operator shall be able to select multiple alarms for single action acknowledgement.

12. There shall be the ability to disable alarms.

13. The OWS alarm viewer shall be able to display the last 100 active alarms. If there are more than 100 active alarms, as alarms are acknowledged and removed from the viewer, older alarms shall be viewable to keep the viewer showing the last 100 active alarms until there are less than 100 active alarms.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 10

G. Trends:

1. Real Time Trends:

a. At each OWS the operator shall be able to initiate a real time trending instance of up to 20 variables simultaneously.

b. The polling interval setting shall be adjustable down to a rate of every second.

c. The data for each instance shall be presented on a single graphical display that automatically updates with each new data collection cycle.

d. The graphical presentation shall plot the variables on the Y axis and time on the X axis.

e. A minimum of two Y axis scales shall be available.

f. The operator shall have the ability to set the range on each Y axis scale or let the scales auto range to cover the range of the values being trended.

g. Each element of data on the graphical display must be labeled by name or by a unique color. If color is used, a color legend must be included on the graph.

h. The operator shall be able to open up to five instances simultaneously for a total of 100 points being trended at one time.

i. An operator shall be able to print an instance of real time data.

j. The system shall be capable of trending any variable in the system.

k. The operator shall be able to save pre-configured instances of real time trending that can be initiated with simple point and click actions.

2. Historical Data Collection:

a. Historical trend data shall be collected by field level devices and periodically uploaded to the data server.

b. The trend log objects in the field level devices shall have the capacity to store 300 samples per variable. When the 301st sample is collected, the 1st sample shall be discarded.

c. The field level devices shall be configured to request an upload of data when the number of samples is not greater than 180. Uploads may be configured to occur at a greater frequency.

d. Initiation of historical data collection shall be configurable.

1) By manual operator intervention in a point and click manner.

2) By a user adjustable time schedule or date.

3) Triggered by a binary status variable (when the fan status is on, start the trend of the mixed air temperature).

4) The system shall be capable of trending any variable in the system.

e. The status and capacity of the trend logs in the field devices shall be viewable from the operator workstation.

3. Historical Data Presentation:

a. An OWS shall have the capability to present the historical data for a variable in a tabular presentation of the values along with the date and time of the sample. The time period for the values to be presented shall be user adjustable.

b. An OWS shall have the capability to present the historical data for a variable in a graphical presentation of the values plotted against time and date.

c. The graphical presentation capabilities for historical trends shall equal those described above for real time trends.

d. The operator shall be able to save pre-configured instances of historical trending that can be initiated with simple point and click actions.

e. The operator shall be able to print the tabular presentations and graphical presentations of historical trend data.

4. The data collection, storage, retrieval and presentation system shall provide the features necessary for the Government to achieve certification under 21 CFR Part 11. The key issue is the integrity of the data, the ability to verify that the data has not been modified after collection by the system.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 11

H. Report Creation:

1. The operators shall be able to extract historical data from the data collection files and present the data in a Microsoft Excel format. All of the data in the log shall be exportable to include the date, time and values.

2. The number of trend logs that can be inserted into a single Excel Workbook shall not be limited by the EMCS software.

3. The operators shall be able to pre-configure reports for manual execution or automated execution.

4. The OWS shall be able to auto execute any report based on:

a. A time schedule.

b. An alarm trigger.

c. The status of a binary point (state=1, execute the report).

5. The operators shall be able to pre-configure the destination of the report:

a. OWS screen.

b. Write to file on the hard drive.

c. Send to a printer.

6. The generation of a report shall not interrupt the use of the OWS by the operator, that is, it shall execute in the background.

7. The following reports (at a minimum) shall be generated for all buildings tied to new EMCS system on an individual building basis by OWS at initial setup:

a. Monthly utility consumption (see building points list for all building utilities monitored).

b. System generated alarms.

I. EMCS Software:

1. Acceptable DDC Manufacturers:

a. Delta.

b. Honeywell.

c. Tridium.

PART 3 - EXECUTION

3.1 GENERAL

A. Configure and program software in a professional manner, utilizing trained personnel skilled in the field.

B. Coordinate work with the Government and other contractors to avoid conflicts, errors, delays, and unnecessary interference with the operation of equipment during construction.

C. Implement a comprehensive set of procedures to test all patches, upgrades and new AIS applications prior to deployment.

3.2 INSTALLATION

A. All required software for fully functional systems shall be installed and configured. The Contractor shall coordinate with the Base Mechanical Engineer for IP naming convention and standard. Contractor shall provide the IP connections.

3.3 PROGRAMMING

A. Configure, download and program the system as required to meet the project schedule, coordinating with the Government and other contractors.

B. Participate in field checkout activity by assuring point mapping is correct on EMCS screens including engineering units and ranges.

C. Participate in final test activity by assuring process functionality as required by the redlined documents.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 12

3.4 OPERATOR WORKSTATIONS

A. Dynamic Data Display:

1. Points lists shall be organized on a per field device basis.

2. If the software provides for the sub-division of point data within a field device, the data shall be organized by physical sub-system as a minimum (fan section, mixed air section, etc.).

3. The workstation shall be configured to automatically update values without any action by the operator.

4. Value updates in points lists shall be configured to update at least once every 5 seconds when actively viewed at OWS, otherwise value update in points shall occur on a scheduled basis. Scheduled updates should be such that all buildings are not updated simultaneously.

5. Binary data shall be configured to display state descriptors (OFF, ON; OPEN, CLOSED, etc.) and not the states of 0 and 1.

6. Analog data displays shall include engineering units.

B. Graphic Pages:

1. Hierarchy:

a. The organization of graphic pages shall be from a global level down to a very detailed level through a series of links.

b. Linking shall allow the operator to move down the hierarchy, up the hierarchy and laterally within the hierarchy.

2. Hierarchy Outline:

a. Site Plan Page: A visual representation of the site (map). One page or multiple linked pages depending on the size of the site plan.

1) Link to individual building graphic pages.

2) Display outdoor weather conditions.

b. Utility Management Page: A summary of data on the utility consumption for the site.

1) Link up to the site plan.

2) Display:

a) Utility consumption data.

b) Demand data.

c) Voltages, currents and power factors.

d) Demand control actions currently in effect.

3) Presenting the utility management data may require more than one graphic page to effectively report the data from multiple meters.

c. Building Graphic Page: Typically a picture of the building. One page per building.

1) Link to floor plans within the building.

2) Link to central plant graphics where the plant serves the entire building.

3) Link to delivery systems if the delivery system serves the entire building.

4) Link up to the site plan.

5) Link to Building Utility Consumption Reports and real-time monitoring.

d. Floor Plan Page: This will be a two dimensional plan of a floor area. A minimum of one (1) page per floor per building is required. Where floor plans are large, multiple linked pages are required. For each control zone the value of the controlled parameters shall be displayed.

1) Link up to the Building page.

2) Link up to the Site Plan page.

3) Link to any delivery system that serves the floor plan area (air handling unit is typical).

4) Link to time schedules that affect the systems that serve the area.

5) Link to a Terminal Unit Summary page where multiple zones on the floor are served by unitary control devices such a VAVs or fan coil units.

6) Individual control zones shall be identified.

7) The location of terminal equipment serving each zone shall be shown.

8) The location of sensors installed in the occupied space shall be shown.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 13

9) Where room numbers are available, they shall be shown.

e. Central Plant Page: A graphical representation of the equipment that makes up the plant such as chillers, pumps, boilers, towers etc. If the plant is small, this graphic will display the values of process variables and commands to end devices. If the plant is complex, this graphic will just contain links to equipment graphics. A page for each plant is required.

1) Link up to the Building page.

2) Link up to the Site Plan page.

3) Link to Central Plant Equipment Component page (chiller, pumps, tower, etc.).

4) Display:

a) Process variables.

b) Commands to end devices.

c) Status of end devices.

d) Alarm points if this is the only central plant graphic.

e) Plant status (enabled/disabled).

f) Demand control status.

g) Link to any time schedules that affect the operation of the plant.

h) Link to any pre-configured trend charts associated with the performance of the plant.

i) Link to a Central Plant Configuration page.

f. Central Plant Equipment Component: A graphical representation of an element of equipment such as a chiller, pumps, boiler or tower or some combination of all of these.

A page for each primary equipment item per plant is required.

1) Link up to the Central Plant page.

2) Link up to the Building page.

3) Link up to the Site Plan page.

4) Display:

a) Process variables.

b) Commands to end devices.

c) Status of end devices.

d) Alarm points.

e) Equipment status (enabled/disabled).

f) Demand control status.

5) Link to any time schedules that affect the operation of the equipment component.

6) Link to any pre-configured trend charts associated with the performance of the equipment component.

7) Link to a Central Plant Configuration page.

g. Central Plant Configuration Page: On this page the operator is given access to the configuration parameters for the entire plant or a piece of equipment in the plant.

Typically, this page presents data in a tabular format. The type of data on this page is not changed frequently, but the operator may wish to view it frequently. One page per plant for small plants and one page per primary equipment item per plant for larger plants are required.

1) Setpoints.

2) Tuning parameters.

3) Calibration parameters.

4) Timing parameters.

5) Application parameters.

6) Reset schedules.

7) Lead lag information.

8) Time schedules.

9) Link up to the Equipment or Central Plant page.

10) Link up to the Building page.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 14

h. Delivery System Page: A graphical representation of an air or water delivery system such as an air handling unit, roof top air handling unit, computer room air conditioning unit. One page for each delivery system.

1) If the Delivery System serves a specific floor area, link up to the Floor Area page.

2) Link up to the Building page.

3) Link up to the Site Plan page.

4) Link to the Central Plant page if the Delivery System is served by a Central Plant.

5) If the Delivery System supplies multiple terminal devices, link to a Terminal Unit

Summary page.

6) Link to a Delivery System Configuration page.

7) The graphical representation of the equipment shall be three dimensional and represent the true physical characteristics of the installed system.

8) Display:

a) Process variables.

b) Commands to end devices.

c) Status of end devices.

d) Status of different modes (economizer on/off, mechanical cooling enabled/disabled, occupied/unoccupied).

e) Alarm points.

9) Link to any time schedules that affect the system operation.

10) Link to any pre-configured trend charts for the system.

i. Delivery System Configuration Page: On this page the operator is given access to the configuration parameters for the delivery system. Typically this page presents data in a tabular format. The type of data on this page is not changed frequently but the operator may wish to view it frequently. One page per delivery system is required.

1) Display:

a) Setpoints.

b) Tuning Parameters.

c) Calibration Parameters.

d) Timing Parameters.

e) Application parameters.

f) Reset Schedules.

g) Lead Lag Information.

h) Time Schedules.

2) Link up to the Delivery System page.

3) Link up to the Building page.

4) Link up to the Site Plan page.

j. Terminal Equipment Summary Page: On this page, the dynamic data and setpoints that are associated with multiple terminal units are presented in a tabular format. The objective is to present a summary of terminal unit performance for an area of the facility. One page is required for each group of terminal units. In the tabular data, do not use less than 12-point font size. Multiple linked pages may be used if there are a large number of terminals served by one delivery system.

1) Display in the Table:

a) Process variables.

b) Setpoints for each process.

c) Command to each end device.

d) Status of each end device.

e) Load factors such as terminal load for a VAV terminal unit.

f) Link to the page for each Terminal Unit.

g) Link up to the Delivery System page.

h) Link up to the Floor Plan page.

i) Link up to the Building page.

j) Link up to the Site Plan page.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 15

k. Terminal Unit Page: A graphical representation of a terminal unit such as a VAV terminal or fan coil terminal. One page for each terminal unit.

1) Link up to the Terminal Summary page.

2) Link up to the Floor Plan page.

3) Link up to the Building page.

4) Link up to the Site Plan page.

5) The graphical representation of the equipment shall be three dimensional and shall represent the actual installed terminal unit (if the VAV does not have a fan, a fan should not be shown, etc.).

6) Display:

a) Process variables.

b) Command to end devices.

c) Status of end devices.

d) Setpoints for each process.

e) Modes (auto, heat, cool, etc.).

f) Capacity indicators (terminal load, %heat, %cool, etc.).

g) Reset schedules.

h) Occupancy commands and status.

i) Alarm points.

3. For all points on a graphic page that are subject to being under manual or test mode, the display shall indicate when test mode or manual mode has been applied to the point.

4. Graphic Page Requirements:

a. The sequence of control defines the buildings and all of the equipment items for which graphic pages shall be constructed as described above.

b. The Contractor shall develop similar additional graphic pages to be defined during the construction period as follows:

1) Up to 5 additional pages per building.

2) Up to 20 additional global pages.

C. User Groups:

1. The Contractor shall configure four users groups, one for each level of security. The group names shall be similar to:

a. Administrators.

b. Engineers.

c. Operators.

d. Viewers.

2. The Contractor shall configure two users in each user group.

D. Alarm Processing:

1. All alarms required by the sequence of control shall be fully configured for delivery to the operator workstations and the alarm files.

2. A common alarm file shall be established to receive alarms from all of the field devices.

3. A separate alarm file shall be established on a per building basis to receive just the alarms from that building.

4. The alarm messages shall be descriptive and include as a minimum:

a. System identification.

b. Date.

c. Time to the second.

d. Nature of the alarm such as high value, low value, or fail to start.

5. The system shall be configured to send an alarm message on return to normal.

6. All users shall receive all alarms.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 16

E. Reports:

1. The sequence of control includes the requirements for variables to be trended. The data server is setup to collect all of this data. The operators have the ability to look at the historical trend data on a log by log basis or in a graphical format as needed. It can be very beneficial to the Government for performance assessments or energy management to have a set of standard reports that analyzes the data and puts it in a format to drive management decisions. Typical examples are:

a. Run time reports on equipment.

b. Performance deviation reports that compare actual performance with specified performance. An example would be the average deviation from setpoint for space temperatures, discharge air temperatures on air handling units, etc.

c. Equipment efficiency reports such as measurements on the KW per TON for a chiller over time.

d. Energy consumption as reported utility metering equipment with reports commonly generated such as 15 minute demand and consumption throughout a month, monthly meter reads for facilities for billing purposes, etc.

3.5 PERFORMANCE VERIFICATION TESTING

A. Key tasks to be executed and documented in the Performance Verification testing of the EMCS system include:

1. Performance Verification for operator tasks from an OWS such as the following.

a. Graphics navigation.

b. Trend data collection and presentation.

c. Alarm handling, acknowledgement, and routing.

d. Time schedule editing.

e. Application parameter adjustment.

f. Manual control of external points.

g. Report execution.

h. Automatic backups.

2. The Contractor shall schedule the performance verification testing with the Government and Engineer 2 weeks in advance. The Government and Engineer shall observe the testing unless they inform the Contractor in writing to proceed without observation.

3. The Contractor shall provide all personnel and equipment required for executing the tests.

This shall include but not be limited to tools, instruments, ladders, lifts, computers, software, cables etc. The Contractor personnel must be competent with and knowledgeable of all project specific systems, hardware and software.

4. All failures to meet the project requirements shall be documented in the performance verification test report along with the corrective actions taken by the Contractor. Errors that are corrected on the spot to the satisfaction of the Government and Engineer do not have to be documented in the report.

5. Errors that require re-work that do not occur on the spot shall require retesting once corrective action has been taken.

6. The Contractor shall provide 2 weeks notice for retesting of corrected errors.

3.6 TRAINING

A. The Contractor shall provide at least two training programs for the Government’s personnel.

1. System Operator Training.

2. System Administrator Training.

B. System Operator Training:

1. Training shall be provided for up to 10 individuals.

2. The training will not be scheduled prior to system acceptance by the Government.

a. The objective of this session is a thorough review of the installed system.

1) Review system architecture.

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 17

2) Review point naming concepts.

3) Access point data from multiple controllers.

4) Review the graphics navigation scheme.

5) View historical trend logs.

6) View real time trend logs.

7) Review process for adjusting application parameters.

8) Review process for adjusting time schedule parameters.

9) Review report presentation system.

10) Review levels of user authority.

11) Respond to questions and answers.

C. System Administrator Training:

1. Training shall be provided for up to four individuals. The Owner will confirm the number to the Contractor one month in advance of the training.

2. The Contractor in the submittal of the course material shall identify the course length.

3. Learning Objectives:

a. Schedule and maintain system backups.

b. Archive trend log data.

c. Set up user groups.

d. Set up users.

e. Set up alarm groups.

f. Set up alarm users.

3.7 SUPPORT

A. Provide telephone customer support 24 HRS per day, 7 days per week. Provide local support as required to assist in the installation and trouble shooting of EMCS software. Local is defined as within 50 miles of project site.

3.8 SUBMITTAL SCHEDULE

Item No. Submittal Requirement With Bid

No. of Weeks After Award

As Indicated

13402-001 Server and workstation hardware descriptions.

Include at a minimum hard drive, RAM, CPU and network interface details.

13402-002

EMCS and related software list with version numbers.

13402-

5 level Topology drawing showing ICS network topology, interconnections, data flow, components and external connections

13402-004 Architecture diagram showing proposed hardware and software to be installed.

13402-005 Exception list, if any, to this specification. 3

13402-006 Three references of installed users include:

Company name, contact name and phone number, number of tags and software version.

X

13402-007 Operation manuals and application notes for 4

Revised 11 Jul 2018

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

EMCS SYSTEM

13402 - 18 software to be supplied.

13402-008 EMCS and DDC controller database According to project schedule.

13402-009 Graphics screens and navigation According to project schedule.

END OF SECTION