B08_Attachment_B_-_EBCS_Technical_Design_Guide.pdf

Army Reserve Enterprise Building Control System (EBCS)

Technical Design Guide

Updated Revision: August 2024 ii

Table of Contents List of Acronyms ......................................................................................................................................................... iv

Revision History........................................................................................................................................................... v

1.0. Introduction

1.1. Typical EBCS System Architecture

1.2. How To Use This Document

2.0 General Requirements

2.1. Hardware +

2.2. Software & Licensing

2.3. Equipment Naming

2.4. Point Naming

2.5. Tagging

2.6. Graphical User Interface

2.7. Users, Categories, and User Roles

3.0 Site-Level / Building-Level Integration

3.1. Hardware

3.2. JACE Hardware Installation

3.3. JACE Setup and Configuration

3.4. Building Control System Integration

3.5. Utility Meter Integration

3.6. JACE Folder Structure

3.7. QAQC

4.0 Enterprise Integration

4.1. Roles and Responsibilities

4.2. Site Readiness Assessment

4.3. System Configuration Requirements

4.4. Niagara Network / New Station Configuration

4.5. Point Names

4.6. Schedules

4.7. Alarm Extensions

4.8. Trending and Data Archiving

4.9. Analytics

4.10. Graphical User Interface

4.11. Quality Assurance / Quality Control

iii

Appendix A. Integration Ready Definition

Appendix B. DHCP Reservation

Appendix C. JACE Enclosure Layout

Appendix D. User Profiles

Appendix E. MDMS Standard Meter Data Format

Appendix F. Glossary of Terms

Attachment 1. N4 Hardening Guide

Attachment 2. Point Naming Library

Attachment 3. EBCS User Interface Design Manual

Attachment 4. Site Readiness Assessment Workbook Template

Attachment 5. Implementing Analytics

Attachment 6. QAQC Checklist iv

List of Acronyms ARNet: Army Reserve Network

BCS: building control system

DHCP: Dynamic Host Configuration Protocol

EBCS: Enterprise Building Control System

FACID: facility identification number

FOXS: secured communications protocol developed as part of the Tridium Niagara Framework

FFR: full facility revitalization

GUI: graphical user interface

HTTPS: Hypertext Transfer Protocol Secure

HVAC: heating, ventilation, and air conditioning

IC: Integration Controller

IP: Internet Protocol

JACE: Java Application Control Engine

JAR: Niagara software operations modules

MAC: Media Access Control

MILCON: military construction

MSC: Mission Support Command

NAC: Network Area Controller

NEMA: National Electrical Manufacturers Association

POC: point of contact

QAQC: quality assurance / quality check

QNX: operation system

RD: Readiness Division

RDBMS: Relational Database Management System

SOW: scope of work

SRA: site readiness assessment

TCP: Transmission Control Protocol

TLS: Transport Layer Security

UL: Underwriters Laboratories

Wi-Fi: wireless network v

Revision History Version Description Date January

Initial Version JAN

October

Design Guide: Specs updated to (1) include point naming convention for meters;

(2) requiring the integrator to send trend data to the SQL server Attachment C: Updated per FY21 SRAs Attachment H: New attachment (MDMS Standard Meter Data Format) Attachment J: (1) Removed “Logic/Sequencing” from Graphics section; (2) Updated “Logic/Sequencing” verbiage on Line 65; (3) Added “JACE Model and Niagara Version” to Line 72

OCT

May

Design Guide: Reformatted to help assist RD/MSC/Installation EBCS POCs create BCS and EBCS related SOWs.

• Building-level tasks vs Enterprise-level tasks have been more clearly defined.

• BCS contractor vs integration contractor tasks have been more clearly defined.

• Section 1.2 How to Use this Document: New section to help guide RD/MSC/Installation EBCS POCs to which sections and resources are applicable depending on what type of project they are developing.

Appendices A – F: Most of these sections were formally attachments. The supplemental files/attachments have been removed from the Design Guide package and incorporated into the main Design Guide document as appendices.

Appendix F Glossary of Terms: New section defining terms often conflicting or confusing in BCS and EBCS related projects.

Attachments 1- 6: These sections remain as supplemental files/attachments and have been renamed from using letters to now using numbers. An expanded summary for each file has been updated in the main Design Guide document.

Attachment 2 Point Naming Convention: Updated to capture a more comprehensive list of points, tags, and naming convention for equipment names and Niagara Point Folders.

Attachment 5 Implementing Analytics: New addition to Design Guide.

Attachment 6 QAQC Checklist: Updates include creating a macro-enabled workbook that performs a point-by-point QAQC analysis. Minor edits to graphics tab to condense checklist.

MAY

August

Added export tag/virtual point import process.

Reorganized some content into General Requirements section.

1.0. Introduction

The Enterprise Building Control System (EBCS) Technical Design Guide is intended to assist Army Reserve Readiness Division (RD) / Mission Support Command (MSC) / Installation EBCS points of contact (POCs) with creating scopes of work (SOWs) for building control system (BCS)-related projects and/or BCS integration to the EBCS server. The goal of this document is to help ensure BCS-related projects are executed with the near- or long-term intentions of EBCS integration.

This document is intended to be used for a variety of BCS-related projects. The sections and resources applicable for such projects are outlined in Section 1.2, “How To Use This Document.”

It is critical to understand the difference between key terms while using this document and executing BCS-related projects. Refer to “Appendix F. Glossary of Terms” for a full list of common terms and definitions.

1.1. Typical EBCS System Architecture

The EBCS architecture relies on the Tridium Niagara 4 Framework to provide seamless integration of common and accepted BCSs at the building level to communicate with a central server at the Army Reserve Enterprise level. “Building level” refers to any devices physically located in the building, as represented in Figure 1, and the “BCS contractor” is the person responsible for working on the BCS at the building level (any equipment and/or BCS devices physically located within a building). This person is not required to have access to EBCS and is not responsible for integration to the EBCS server.

The “Enterprise level” refers to the Army Reserve Network (ARNet) and EBCS server, and the “integration contractor” is the person responsible for integrating a BCS to the EBCS server. This may be the same person as the BCS contractor but with additional roles and responsibilities as the “EBCS integrator / integration contractor.”

The Java Application Control Engine (JACE) provides a firewall to allow local building controls from various vendors to connect to and communicate across the ARNet (Figure 1).

Figure 1. EBCS Simplified Architecture

The NAC-to-JACE example in Figure 1 shows building equipment (chillers, air-handlers, etc.) connected to a proprietary vendor’s device called a Network Area Controller (NAC). The NAC cannot be connected to the ARNet directly. Therefore, an Integration Controller (IC) JACE serves as a gateway to make the data and control function of the local BCS/NAC available across the network. Sometimes the NAC is also a JACE but does not meet the hardware requirements for connecting to EBCS, resulting in a JACE-to- JACE configuration. Lastly, the JACE-to-EBCS-Server configuration uses a single JACE as both the NAC (or metering JACE) and IC, this is the preferred hardware configuration for the EBCS network architecture.

All other configurations will be determined by the RD/MSC/Installation POC with support from the integration contractor.

1.2. How To Use This Document

This document provides a framework for BCSs that are intended for EBCS integration. This document can be used for various BCS-related projects at various stages while sharing the same objective of achieving an EBCS Integration Ready status and/or integration to EBCS.

Table 1. Design Guide Sections for Various BCS-Related Projects Example Project Types Design Guide Sections Responsible Parties Developing new BCS (FFR, MILCON, etc.) without EBCS integrations

Sections: 2.1 and 2.2 (including 2.2.1 – 2.2.4) Appendices: All Attachments: 1 – 3 and 6

Controls contractor Installation POC ARIMD EBCS Sustainability Configuring existing systems to be

EBCS Integration Ready Developing new BCS (MRAR/FFR, MCAR/MILCON, etc.) with EBCS integrations

Sections: 2.1, 2.2 (including 2.2.1 – 2.2.4), and 2.3 (including 2.3.1 – 2.3.4) Appendices: All Attachments: 1 – 3 and 5 – 6

Controls contractor Integration contractor Installation POC ARIMD EBCS Sustainability

Integrating stations to EBCS that are EBCS Integration Ready

Sections: 2.3 (including 2.3.1 – 2.3.4) Appendices: D and F Attachments: 2 – 3 and 5 – 6

Integration contractor Installation POC ARIMD EBCS Sustainability

Performing a site readiness assessment

Section: 2.3 Appendices: A and F Attachments: 4

Integration contractor Installation POC

MRAR/FFR is full facility revitalization; MCAR/MILCON is military construction.

2.0 General Requirements

2.1. Hardware

The Niagara Framework requires an adequate processor, hard disk, memory, and speed to run complex building models.

The Army Reserve minimum hardware requirements include:

• Operating System: Windows Server 2019 or newer, Windows 11 or newer

• Processor: 2 - Intel Pentium Core 2 Duo, 2GHz.

• RAM Memory: 16GB, with 32GB recommended.

• Hard drive space: 50GB available, 1TB additional storage for histories and station backups at supervisor.

• Ethernet 100 Mbit or 1Gbit NIC (network interface card) with TCP/IP support

• Valid license with a minimum initial 5-year SMA provided at time of installation.

2.2. Software & Licensing

Niagara software, modules, and licenses shall be in accordance with Table 2 Software and Licensing Requirements. The contractor shall provide a complete set of product licenses for systems and third-party software used in system development, including documentation for all applications, databases, browsers, communications software, etc. The United States Government (USG) shall be the only named license holder of all software.

Table 2 Software and Licensing Requirements Building-level JACE Enterprise Supervisor Required Niagara Software, Modules and Components

Niagara Framework version 4.13, or newer.

Niagara Mods REFLOW module

Niagara Framework version 4.13, or newer.

Niagara Mods REFLOW module

Required Niagara Device Licensing

Device license shall be determined by current and projected system device count plus 25% capacity. License shall be one of the following increments: 5, 25, 100, or 200. See Device Licensing Examples for guidance.

Unlimited

Required Niagara SMA 5-year 5-year Required Module Licensing Reflow Module Reflow Module Additional Modules and Licensing Required for Integration Specific Applications

Contractor shall license and install any modules required to maintain or enable communications or engineering functionality of the building control system and associated workstation (ex.

Honeywell WEBs, Johnson N2, DNP3, Veeter-Root).

Device Licensing Examples

Current and Projected System Size (Device or Point

Count) Plus 25% Capacity Recommended Device Licensing

Bracket 3 Devices +2 Devices 5 device / 250 points

17 Devices +4 Devices 25 device / 1250 points 75 Devices +19 Devices 100 device / 5000 points 99 Devices +25 Devices 200 device / 10000 points

2.3. Equipment Naming

All connected equipment shall be named in accordance with Attachment 2: Point Naming Library, Equipment Names tab. Equipment names shall match a pre-defined name in the Point Naming Library, while point numbers shall match existing field conditions. In instances where the field name varies from the EBCS standard equipment names, the field name shall be noted in the Niagara point “equipTag”. For example, if a make-up air unit is named MUA-1 in the field, the equipment shall be named MAU-1 in

Niagara (in accordance with the naming convention) and the field name MUA-1 added as the value to the point equipTag. This equipTag point shall be displayed on all equipment level graphics to note the difference in naming standards. The equipment numbering in either situation shall remain the same.

2.4. Point Naming

All points in both the JACE and supervisor levels shall use the Point Naming Library. Deviations to this point naming shall only be allowed in rare circumstances and must be approved by the EBCS Configuration Control Board.

2.5. Tagging

All equipment and points shall be tagged in accordance with Attachment 2: Point Naming Library. All mandatory tags shall be applied to each point or piece of equipment, while any tags defined as Mandatory Tags as Appropriate shall be applied when fitting of a particular equipment or system type.

Analytic tags shall be applied as defined in the Analytic Tags column in the Point Naming Library.

2.6. Graphical User Interface

A fully functional graphical user interface (GUI) shall be built at both the JACE station level and the enterprise supervisor level. Required graphical elements, consisting of various levels of navigation, system and equipment views, tables, reports, schedules, trending, and alarms shall be built at each level as outlined in Table 3: Site-level vs Enterprise-level Graphic Element Requirements, and in Table 4:

Graphical Elements Description.

Table 3: Site-level vs Enterprise Level Graphical Elements Requirements Element Site-Level Enterprise-Level National Dashboard No Yes Installation Dashboards No Yes State Navigation No Yes Site-level Dashboard Determined in SOW Yes Building-level Dashboard Yes Yes Floorplans Yes Yes Equipment Graphics Yes Yes Equipment Summary Yes Yes Schedules Yes Yes Alarm Console Yes Yes Analytics Console No Yes

Table 4: Graphical Elements Description Element Description National Dashboard The user interface shall include navigation to all subordinate installations and integrated buildings from one dashboard. The dashboard shall also include rollups of core operational data and reports.

Installation Dashboards One integrated dashboard per installation presenting roll-ups of core installation level data including alarms, energy, and system statuses. Also presents navigation to all connected buildings at the installation level.

State Navigation The user interface shall include navigation to all integrated buildings within a particular state.

Site-level Dashboard The site-level dashboard shall consist of navigational elements, data rollups, and displays of shared systems (ex. Site lighting) for all buildings at a co-located location (campus, installation, or multi-building site). The dashboard shall include links to each of the co-located buildings, alarm and analytics consoles that include data from all site buildings.

Building-level dashboard A building-level dashboard shall consist of navigational elements, links to building floorplans, equipment, system graphics, alarm console, analytics console(s), schedules, and histories for the integrated building.

Floorplans Floorplan graphics shall consist of complete graphical representations of current building floorplans rendered in 3D. Floorplans shall include all areas of the integrated building regardless of if that area has integrated equipment, and shall include room numbers, and equipment locations. All equipment tags shall include hyperlinks to the associated equipment graphical element. The floorplan shall have dynamic colored overlay that shall respond in reference to temperature deviations. The colored overlay shall accurately reflect actual HVAC zones. The contractor will implement a zone temperature deviation calculation for each zone and integrate the deviation into the floorplan widgets. The deviation scale will be set up as follows:

Green: When zone is +/- 2°F of setpoint Yellow: When zone is above setpoint by 2-4°F Orange: When zone is above setpoint by 4-6°F Red: When zone is above setpoint by more than 6°F Light blue: When zone is below setpoint by 2-4°F Blue: When zone is below setpoint by 4-6°F Dark blue: When zone is below setpoint by more than 6°F

Equipment Graphics All integrated equipment shall have an individual equipment graphic. Equipment graphics shall include all applicable points as integrated and provide the user capability to set or override control points as permissions allow. Points having history shall include one-click access to those histories. The contractor will edit the equipment-level screens to be representative of the equipment configuration and piping/ducting layout.

Equipment Summary The equipment summary graphic shall be generated for each distinct type of equipment that has more than one instance in a building. All systems with multiple pieces of equipment must have an overview page for that equipment type. Each equipment type overview page contains a table listing the equipment and the primary inputs/outputs for the equipment type (e.g., equipment name, area served, occupancy status, fan/operational status, temperatures and setpoints, damper or valve positions). The table needs to be hyperlinked to each represented piece of equipment (e.g., AHU-1 hyperlink opens the AHU-1 specific graphic).

System Graphics System graphics shall be generated for hot water, chilled water, and airside systems to show the interaction between system components. An example of a system graphic is a hot water system graphic that shows pumps, boilers, motorized valves, temperature sensors, and piping.

Schedules & Calendars All equipment schedules shall be accessible and editable through the GUI. User permissions shall determine if a user is able to edit a schedule. By default, the following three schedules shall be utilized in each building:

General Building Schedule – All HVAC equipment tied to one global schedule.

This schedule shall be a 5-day schedule by default.

Holiday Calendar – This calendar shall be configured for all federal holidays.

The holiday calendar shall override the general building schedule into unoccupied mode.

Drill Calendar – This calendar shall be updated by the system user as needed for unit events and battle assembly schedules. The calendar shall place the HVAC systems into 24-hr occupied and shall override both the general building schedule and the holiday calendar.

All schedules and calendars shall be located in the JACE serving each building.

The schedules shall be editable at both the JACE and supervisor levels using the calendar virtual object.

Alarm Console The standard Niagara alarm console shall be viewable at both the JACE and supervisor levels. At the building level, all alarms shall be relative to the building being accessed. At the supervisor level, multiple alarm consoles shall operate to group alarm objects by navigation level (ex. Viewing a site level dashboard will show the alarms for all buildings at that site into one alarm console, while viewing a building-level shall only show the alarms for that building).

Analytics Console Analytics by default operate only at the supervisor level and as such shall only be accessible from the supervisor GUI. The analytics console shall display all analytics active at a respective building and shall be grouped at the site and regional levels.

Table 5 is an overview of the roles and responsibilities for creating the GUI for the JACE. These steps are recommended regardless of whether the system is currently being integrated to EBCS and regardless of whether the JACE is intended for a BCS or metering.

Table 5. GUI Roles & Responsibilities Roles Responsibility Summary Controls or integration contractor • Set up Files system according to standardization

• Develop and edit graphics to match building using the station template and/or graphics package

• License and install Reflow module.

Installation POC • Provide station template and/or graphics package to contractor

• Provide mechanical drawings to contractor

• Provide PDF floorplans to contractor

a) The GUI package (“Attachment 3. Graphics Package & EBCS User Interface Examples”) or station sample files will provide template graphics for system and equipment level screens, including a PDF of examples of the graphics. This GUI package must be used by the contractor for both JACE and enterprise level graphics.

b) The contractor shall not load or integrate company logos or hyperlinks into the station GUI.

2.7. Users, Categories, and User Roles

A. All EBCS users are required to have a unique user account and username. The use of generic user accounts (multiple users utilizing one user account) shall not be allowed.

B. All EBCS user accounts shall be assigned by the EBCS sustainment manager when requested by a stakeholder command. It is the responsibility of the original requesting command to notify the EBCS sustainment manager when a user should no longer have access to EBCS.

C. Category Service: Category service configuration shall remain consistent with existing EBCS configuration at the JACE and supervisor levels.

D. All user accounts shall utilize one of the below pre-established roles.

User Role Category/Permissions Default System View Enterprise Administrator Admin/rwiRWI USARC Enterprise User User/r USARC Regional Administrator User/rw Regional Command Regional Operator User/r Regional Command Facility Coordinator User/rw Site Specific Controls Contractor Admin/rwiRWI Site Specific

3.0 Site-Level / Building-Level Integration

Site-level or building-level integration consists of tasks required for integration of a single system or multiple systems at a physical building or campus with the desired end-state of making the building EBCS “integration ready”.

3.1. Hardware

The IC JACE must meet the following specifications regardless of the integration configuration.

• VYKON JACE 9000 series with an open license. License version must be the latest version that is not in beta testing (visit https://www.tridium.com/us/en for the latest version details) with the Wi-Fi disabled.

• 5-year software maintenance agreement (SMA) plan.

• License should include the workbench tools to be installed on the JACE.

• Devices should be BACnet compatible with a communication preference towards BACnet/IP

• A dedicated UL-listed, Class 2, 24vac power supply with manufacturer-approved surge protection. The JACE must be powered by a dedicated breaker or off the circuit providing power to the local BCS NAC (if existing).

• Mounted in a National Electrical Manufacturers Association (NEMA) Type III enclosure with associated wiring, fusing, and mounting blocks.

o Use hole-knockout protectors and properly aligned holes, and do not leave any jagged edges.

3.2. JACE Hardware Installation

Table 5 is an overview of the roles and responsibilities for installing a JACE that meets the hardware requirements as specified above in Section 3.1, “Hardware.” This installation process is recommended regardless of whether the system is currently being integrated to EBCS and regardless of whether the JACE is intended for a BCS or metering.

https://www.tridium.com/us/en

Table 6. Installing JACE Roles & Responsibilities Roles Responsibility Summary Controls or integration contractor • Submit JACE hardware information

• Determine appropriate JACE location

• Connect JACE to ARNet with contractor-provided equipment

• Properly configure Ports 1 & 2 on JACE; Connect any local workstations

• Label JACE

Installation POC • Determine appropriate JACE location ARIMD EBCS Sustainment Manager • Record JACE hardware information; Submit DHCP reservation DHCP is Dynamic Host Configuration Protocol.

a) The JACE Media Access Control (MAC) address, serial number, QNX code, and additional information must be entered in a “Request for DHCP Reservation Form” as shown in “Appendix B. DHCP Reservation” and submitted to the Installation POC and ARIMD EBCS Sustainability Manager for DHCP reservation. A DHCP network reservation shall be received prior to the JACE being connected to the ARNET.

b) The controls and/or integration contractor shall work with the Installation POC to determine the ideal location for the JACE.

a. Mount the Jace in a NEMA Type III enclosure with associated wiring, fusing, and mounting blocks.

b. Use hole-knockout protectors and properly aligned holes, and do not leave any jagged edges.

c) The contractor will use a Cat 6E cable to plug into Port 1 of the JACE from the ARNet switch. The contractor will label this cable as “ARNet”. If there is no Cat 6E cable from an ARNet switch near the JACE location, the contractor is responsible for any cable-runs that are necessary for connecting the JACE to the ARNet. The Cat 6E cable shall be labeled at each end for purpose and destination.

d) If possible, the contractor will verify that the port is active by plugging in a ARNet computer to the cable in the mechanical room at the point where the JACE is going to be connected to the cable.

e) Port 2 will be used for local building control system field devices, operator workstation, and vendor to access the BCS. This port shall be configured for static IP. In instances where an IP address schedule has not already been assigned to field devices, it is suggested that the JACE be assigned a static IP address of 192.167.1.140.

f) Any onsite BCS computers inside the building used for control or monitoring need to be connected on the Port 2 side of the JACE and remain operational as it was before the JACE was installed. Any software tools that are needed on the computer to configure the BCS need to remain operational. If a new PC is installed for the JACE, it should be configured to monitor the BCSs through the Port 2 and with the EBCS graphics package that is installed on the EBCS JACE.

The computer should not have any other software.

g) Physically label JACE with station name and Port 1 and Port 2 MAC address. Review “Appendix C.

JACE Enclosure Layout” for further technical installation guidance on the JACE enclosure layout.

h) The contractor will submit “before and after” photos of JACE installation to the Installation POC, including closeup images of the cable connections at the JACE and at the local BCS (if existing), cable pathways, and all enclosure penetrations.

3.3. JACE Setup and Configuration

Table 3 is an overview of the roles and responsibilities for JACE setup and configuration. This setup and configuration is recommended regardless of whether the system is currently being integrated to EBCS and regardless of whether the JACE is intended for a BCS or metering.

Table 7. JACE Setup and Config Roles & Responsibilities Roles Responsibility Summary Controls or integration contractor

• Connect ARNet to JACE

• Only enable RUNTIME, UX, and WB profiles during JACE setup

• Adhere to standards for networking and TCP/IP configurations

• Only create user profiles as defined by the Installation POC

Installation POC • Create station name and provide to contractor

• Create user profiles document and provide to contractor

a) The Niagara4 Hardening Guide must be referenced to during the setup of the JACE to help strength the security of the system (see “Attachment 1. N4 Hardening Guide”).

b) The contractor will only enable the following runtime profiles:

i. RUNTIME: Module JARs having core runtime Java classes only, no user interface.

ii. UX: Module JARs having lightweight HTML5+JavaScript+CSS user interface only.

iii. WB: Module JARs having Workbench or Workbench Applet user interface classes.

c) The contractor will use a standardized station name and hostname that will be provided by the Installation POC. Station name and hostname will adhere to the following format:

FACID_FACNUM_01. Trailing number shall be incremental.

d) All communications between Niagara devices and the EBCS server will be secured with Secure Socket Layer (SSL), using the following ports.

Table 8. Communication Protocols and Ports Interface Protocol Specified Port Internet Browser HTTPS 443 Niagara Station FOXS 4911 Niagara Station TLSv1 5011

e) When configuring the JACE in the TCP/IP configuration screen, Comm 1 will be set for DHCPv4 enabled. DHCPv6 will be enabled. Configure hostname to match station name: FACID-FACNUM- 01.

f) When configuring the JACE in the TCP/IP config screen, Comm 2 on the JACE will be configured with a standardized static IP address and subnet mask to allow for a local laptop to be connected for future onsite work. The contractor will also supply and connect a standard networking switch to allow for direct connection to the JACE.

3.4. Building Control System Integration

Table 9 is an overview of the roles and responsibilities for JACE programming. These steps are recommended regardless of whether the system is currently being integrated to EBCS and regardless of whether the JACE is intended for a BCS or metering.

Table 9. JACE Programming Roles & Responsibilities Roles Responsibility Summary Controls or integration contractor • ALL points and equipment names follow naming convention

• Points required to have alarms & trends will be properly configured

• Schedules are editable and located on the JACE

a) The contractor will use a standardized point naming convention in the JACE for all data points and equipment names as listed in “Attachment 2. Point Naming Library” for heating, ventilation, and air conditioning (HVAC) and auxiliary equipment.

b) The contractor will use a standardized point naming convention for meter points in accordance with the Meter Data Management System (MDMS) variable from Table 1 in “Appendix E. MDMS Standard Meter Data Format.”

c) The contractor will add alarm extensions to the data points as designated in the “Point Naming Library.” An exception can be made if the field controller has a data point specifically for the alarm (e.g., boilerStatus does not need an alarm extension if there is already the point boilerAlarm). Alarm messages will be added to each alarm as outlined below. Alarm messaging should contain the location and nature of the alarm.

i. Out of Range (Analog Points). The message will display the current value of the point and either the high or low threshold.

ii. Command Failure (Boolean Point). The message will display the current command of the point and the current status.

iii. Change of Value (Boolean or Enumerated Points). The message will display the current value of the point.

iv. Change of Status (Niagara Components). The message will display the current value of the component.

d) The contractor will add trend extensions to the data points as designated in the “Point Naming Library.” The data types that will be used for the trend extension are outlined below.

i. Interval Trends. This trend type will be assigned to analog points that are fast changing in nature. The trend extension will be configured to record a data point every 5-15 minutes as specified.

ii. Change-of-Value Trends. This trend type will be assigned to either analog or Boolean points that are not fast changing in nature. The trend extension will automatically be configured to record a data point whenever there is a change of value in the point.

e) The trend extension configuration will be set to allow for a minimum 3-day rolling window of data, but not to exceed 1800 records per JACE.

f) All schedules must be writable on the IC JACE and accessible at the supervisor through use of virtual objects.

i. Scheduling must include the following options: Equipment, Holiday, and Special Events.

1) The equipment schedule may be one single schedule for the whole building, individual schedules for individual pieces of equipment, or a combination of both. This configuration is dependent on the existing schedules for the BCS and is under the discretion of the Installation POC.

2) All/any equipment schedules need to be properly linked to the equipment they serve and tested to ensure the equipment responds to schedule changes.

3) Holiday and special events schedules must be configured to override the equipment schedule(s) as necessary. The holiday schedule shall contain all Federal holidays by default and shall place the equipment into unoccupied mode. The special events schedule shall override all other building schedules and place equipment into occupied mode.

3.5. Utility Meter Integration

3.6. JACE Folder Structure

The Files system of the JACE will be configured in a standardized manner. The layout is as listed below.

Folders highlighted in YELLOW below need to be renamed to match the station and building location.

Additional folders can be added as needed.

i. px / PNNL / ChangeToRegionName & NationalImage / States / ChangeToStateInitials / StationName / USARC / equipment & floorplan & global

1) ChangeToRegionName options: Devens, FHL, McCoy, MSC9th, RSC63rd, RSC81st, RSC88th, RSC99th

2) ChangeToStateInitials: Change according to postal initials for state (all caps)

3) StationName: Change to station name, including the “_C01” or “_M01”

4) Equipment: Equipment folder must have subfolders for each equipment type on the system

5) Floorplan: Includes all px files and images needed for the floorplan page(s)

6) Global: Includes all menu pages (e.g., alarmMenu, equipmentMenu)

3.7. QAQC

Table 10 is an overview of the roles and responsibilities for the final steps of a JACE-based project. These steps are recommended regardless of whether the system is currently being integrated to EBCS and regardless of whether the JACE is intended for a BCS or metering.

Table 10. JACE Final Steps Roles & Responsibilities Roles Responsibility Summary Controls or integration contractor

• Test GUI functionality. Must also function properly while accessing remotely.

• Complete the QAQC tool and submit result to installation POC.

• Complete the QAQC checklist attachment and return to RD/MSC/Installation POC.

• Implement corrections within 10 days of RD/MSC/Installation review.

Installation POC • Complete QAQC checklist.

• Review contractor QAQC and compare to self-performed QAQC. Provide contractor with corrections within 10 days of receiving contractor QAQC checklist.

a) The contractor will work with the Installation POC to test and verify JACE login and GUI functionality of the new JACE. Testing and verification also needs to be satisfactory while accessing the JACE remotely. Any testing and verification of BCS and HVAC functionality is subject to the SOW for the project.

b) A QAQC checklist found in “Attachment 6. QAQC Checklist” should be used by both the contractor and Installation POC to document that the following requirements have been met by the contractor:

i. The point and equipment names follow “Attachment 2. Point Naming Library.”

(Reference Section 2.2.2, “JACE Programming.”). The contractor shall submit a report produced by the QAQC Tool that validates point names, trends, and alarms are in alignment with the EBCS Point Name Library.

ii. Points identified in “Attachment 2. Point Naming Library” for requiring alarm and trend extensions have been properly configured. (Reference Section 2.2.2, “JACE Programming.”)

iii. Schedules have been properly configured and the equipment is responsive to schedule changes. (Reference Section 2.2.2, “JACE Programming.”)

iv. All graphics and floorplans were created with the templates provided in the graphics package found in “Attachment 3. Graphics Package & EBCS User Interface Examples”.

(Reference 2.2.3, “Graphical User Interface.”)

1) Graphics and floorplans must be edited to reflect the system and layout of the building.

2) All points must be available on the graphics and writable points must be able to be editable by user.

3) GUI functionality must be in proper order with working hyperlinks, etc.

c) The contractor will submit a completed QAQC checklist to the Installation POC upon completion of the SOW for review. The Installation POC will review the contractor’s QAQC checklist and complete their own QAQC checklist to identify any issues that need to be corrected by the contractor. A list of corrections must be identified by the RD/MSC/Installation POC withing 10 business days of receiving the QAQC checklist from the contractor.

d) The contractor has 10 business days after receiving a corrections list from the RD/MSC/Installation POC to fix the issues and resubmit the checklist addressing each issue.

4.0 Enterprise Integration

A BCS is considered “EBCS Integration Ready” when the system does not require any additional work before establishing a connection and integrating to the EBCS server. Review “Appendix A. Integration Ready Definition” to determine when the system is integration ready. The primary integration steps are

(1) determining the integration configuration and verifying the JACE hardware is acceptable for EBCS integration, (2) establishing communications between the JACE and the EBCS server, (3) integrating the points and graphics, and (4) setting up the Niagara-based analytics.

The JACE must adhere to all standards of EBCS for point naming and configuration, graphics, and file structure so that the station on the EBCS server matches the point names, graphics, etc. as they exist on the JACE. This strategy helps provide a seamless experience for end users and lowers the cost of integration to the EBCS server.

4.1. Roles and Responsibilities

Table 10 is an overview of the roles and responsibilities for integrating a BCS to the EBCS server. The integration contractor is responsible for connecting the JACE to the EBCS server and integrating the station. In some cases, the integration contractor is also the controls contractor, but will solely be referred to as “integration contractor” in these integration sections.

Table 11. EBCS Integration Roles & Responsibilities Roles Responsibility Summary Integration contractor • Requests access to EBCS server from EBCS Sustainment Manager

• Connect JACE to EBCS server

• Integrate points, graphics, schedules, alarms, trends

Installation POC • Provide guidance and SOW to responsible party for making point configuration or graphics changes at the JACE

ARIMD EBCS Sustainment Manager

• Grants access to EBCS server

• Creates user accounts.

• Assist integration contractor with connecting JACE to EBCS server

4.2. Site Readiness Assessment

Prior to EBCS integration for existing systems, a site readiness assessment (SRA) should be performed by a controls or integration contractor on all facilities appropriate for integration at that site. The Installation POC will provide guidance to the contractor on which facilities require a SRA. The SRA workbook template can be found in “Attachment 4. Site Readiness Assessment Workbook Template.”

The costs reported in the SRA are only valid for 90 days. Any projects developed after 90 days of the SRA are potentially subject to higher integration costs.

An SRA is not necessary for new BCS projects such as MCAR/MILCON and MRAR/FFR.

4.3. System Configuration Requirements

All database changes, system configuration, programming, editing, and configuration of Reflow GUI shall be performed while the EBCS server is on-line without disrupting other system operations. If the contractor requires any database or software changes that require the EBCS server to reboot, such work shall be coordinated in advance with the EBCS Sustainment Manager.

All control system programming logic, air handler or other reset logic, and occupancy scheduling logic shall continue to function correctly, even if the EBCS server is offline. The EBCS server shall function as a user interface to the control system, but shall not be required for control system operation.

4.4. Niagara Network / New Station Configuration

The integration contractor will work with the ARIMD EBCS Sustainment Manager to verify the location of the station is correctly added to the EBCS server navigation tree. The station needs to be under the correct Installation with an EBCS-compliant station name (ex. FACID_FACNUM_01).

The integration contractor will add the station to the EBCS server navigation tree as a “Niagara Station” under the “Niagara Station Folder” of the appropriate Installation.

Note: Only under the approval of the ARIMD EBCS Sustainment Manager, the integration contractor may create a “Niagara Station Folder” for sites with multiple stations.

4.5. Point Names

Points on the JACE should already be in compliance with the convention in “Attachment 2. Point Naming Library.” The integration contractor needs to validate the following criteria before integrating points to the EBCS server. If any corrections need to be made on the JACE, it is the Installation POC’s responsibility to provide a resolution (i.e., Are the changes under warranty for the controls contractor to fix? Should the changes be included in the SOW for the integration contractor?).

a) All equipment points and equipment names follow the naming convention in “Attachment 2.

Point Naming Library” for all HVAC and auxiliary equipment.

b) All meter point names are in accordance with the MDMS variable from Table 1 in “Appendix E.

MDMS Standard Meter Data Format”.

c) Points marked as requiring alarm extensions in “Attachment 2. Point Naming Convention” have appropriately configured alarm extensions. An exception can be made if the field controller has a data point specifically for the alarm (e.g., boilerStatus does not need an alarm extension if there is already the point boilerAlarm).

i. Points marked as requiring trend extensions in “Attachment 2. Point Naming Convention” have appropriately configured trend extensions.

After the data points and equipment names on the JACE have been confirmed as being in compliance with the “Attachment 2. Point Naming Library,” the integration contractor will integrate all data points to the EBCS server exactly as they appear in the JACE (including matching navigation tree layout).

4.6. Schedules

All building and equipment schedules shall be in the local building JACE. Loss of network connectivity between the JACE and Supervisor shall not disrupt the ability of the local control system to operate. The integration contractor will import the schedules from the JACE to the EBCS server so that the schedules appear as virtual objects on the EBCS server. Equipment schedules shall be configured within Reflow to associate with the equipment they control.

4.7. Alarm Extensions

The integration contractor will import all alarm extensions from the JACE to the EBCS server.

The integration contractor will create an alarm console for the station in the AlarmServices of the EBCS server.

1) If there are multiple stations per FACID (site), then the integration contractor will route all corresponding alarm consoles to a single alarm console for the FACID (site).

ii. The integration contractor will edit the “alarmMenu” page to display the alarm console for the station on the EBCS server.

1) If there are multiple stations per FACID (site), then the integration contractor will edit the “alarmMenu” page to display the alarm console for the FACID (site).

iii. The integration contractor is responsible for testing the alarm imports and verifying the alarms on the JACE are being received on the EBCS server and properly displayed on the “alarmMenu” graphic for the station on the EBCS server.

4.8. Trending and Data Archiving

The integration contractor will import all trend extensions from the JACE to the EBCS server.

Trend extensions must be added to the Relational Database Management System (RDBMS) Network to be exported to the EBCS SQL Server.

1) Trend extensions must be added to the RDBMS Network station in accordance with the associated Army Reserve Division and controller type. For example, BCS trend extensions for a building in the 63rd RD will be added to the “63RD_EBCS” station.

2) A new folder must be created for the new trend extensions in the RDBMS Network station for data organization purposes.

3) Trend extensions added to any of the “_MDMS” RDBMS Network stations must be configured to export hourly for all seven days of the week starting at 12:00 AM EST.

4) Trend extensions added to any of the “_EBCS” RDBMS Network stations must be configured to export as follows:

63RD: Daily at 1:20 A.M. EST for all 7 days of the week

81RD: Daily at 2:20 A.M. EST for all 7 days of the week

88RD: Daily at 4:20 A.M. EST for all 7 days of the week

99RD: Daily at 3:20 A.M. EST for all 7 days of the week

9th MSC and Installations: at 5:20 A.M. EST for all 7 days of the week

4.9. Analytics

Table 12 is an overview of the roles and responsibilities for implementing analytics on the EBCS server for new station integrations. These steps are currently recommended only for BCS JACEs.

Table 12. Implementing Analytics Roles & Responsibilities Roles Responsibility Summary Integration contractor • Implement analytics on EBCS server and perform QAQC Installation POC • Perform QAQC on EBCS server analytics

a) Contractor will implement the analytics created by Pacific Northwest National Laboratory for each new station integrated to EBCS. “Attachment 5. Implementing Analytics” needs to be followed so the analytics function properly.

b) Analytics will only be implemented on the EBCS server and not at the IC Jace or NAC.

c) Templates for all analytic algorithms, alerts, alarms, BQL blocks, and px pages are located on the

EBCS server and must be used by the integration contractor when implementing the analytics.

The location for the templates and their implementation procedure is detailed in “Attachment

5. Implementing Analytics”.

d) The implementation of the analytics is summarized in the following steps:

i. Create new variable air volume points (if applicable).

ii. Tag points.

iii. Update the station to “Force Update Niagara Proxy Points.”

iv. Set up alerts in AnalyticService.

v. Set up alarms in AlarmService.

vi. Create a StatusHealth folder and logic.

vii. Add analytic-related graphics: “LandingPage”, “analyticAlerts”, “omAlerts”, “offlineDevices”, “overrides”, and “priorityActions.”

i. The PX page “LandingPage” will be used to replace any existing “Home” pages already in use.

viii. Perform QAQC for implementing analytics.

4.10. Graphical User Interface

After the graphics have been confirmed as being EBCS ready by using the examples in “Attachment 3.

Graphics Package & EBCS User Interface Examples,” the integration contractor will integrate and apply all graphics on the EBCS server exactly as they appear in the JACE.

The Files system of the station on the EBCS server will be configured in a standardized manner. The layout is as listed below. Folders highlighted in YELLOW below need to be renamed to match the station and building location. Additional folders can be added as needed.

1) px / PNNL / ChangeToRegionName / States / ChangeToStateInitials / StationName / USARC / equipment & floorplan & global

2) ChangeToRegionName options: Devens, FHL, McCoy, MSC9th, RSC63rd, RSC81st, RSC88th, RSC99th

3) ChangeToStateInitials: Change according to postal initials for state (all caps)

4) StationName: Change to station name, including the “_C01” or “_M01”

5) Equipment: Equipment folder must have subfolders for each equipment type on the system

6) Floorplan: Includes all px files and images needed for the floorplan page(s)

7) Global: Includes all menu pages (e.g., alarmMenu, equipmentMenu)

4.11. Quality Assurance / Quality Control

Table 12 is an overview of the roles and responsibilities for the final steps of an EBCS integration project.

These steps are recommended regardless of whether the JACE being integrated is for a BCS or metering.

Table 13. EBCS Final Steps Roles & Responsibilities Roles Responsibility Summary Integration contractor • Perform QAQC and correct any issues with the integration prior to submitting final package to RD/MSC/Installation POC

• Submit proof of QAQC to RD/MSC/Installation POC

• Correct any issues identified by the RD/MSC/Installation POC

RD/MSC/Installation POC • Perform QAQC of the integration and review the QAQC documentation submitted by the integration contractor

a) The integration contractor will work with the RD/MSC/Installation POC to test and verify GUI functionality of the new station on the EBCS server. Testing and verification also needs to be satisfactory while accessing EBCS via Niagara Workbench or through a web browser. Any testing and verification of BCS and HVAC functionality is subject to the SOW for the integration.

b) A QAQC checklist found in “Attachment 6. QAQC Checklist” should be used by both the integration contractor and RD/MSC/Installation POC to document that the following requirements have been met by the integration contractor:

a. The point and equipment names follow “Attachment 2. Point Naming Convention.”

(Reference Section 2.2.2, “JACE Programming.”)

b. Points identified in “Attachment 2. Point Naming Convention” for requiring alarm and trend extensions have been properly configured. (Reference Section 2.2.2, “JACE Programming.”)

c. Schedules have been properly configured and the equipment is responsive to schedule changes. (Reference Section 2.2.2, “JACE Programming.”)

d. All graphics and floorplans were created with the templates provided in the graphics package “Attachment 3. Graphics Package & EBCS User Interface Examples.” (Reference Section 2.2.3, “Graphical User Interface.”)

i. Graphics and floorplans must be edited to reflect the system and layout of the building.

ii. All points must be available on the graphics and writable points must be editable by user.

iii. GUI functionality must be in proper order with working hyperlinks, etc.

c) The contractor will submit a completed QAQC checklist to the RD/MSC/Installation POC upon completion of the SOW for review. The RD/MSC/Installation POC will review the contractor’s QAQC checklist and complete their own QAQC checklist to identify any issues that need to be corrected by the contractor. A list of corrections must be identified by the RD/MSC/Installation POC within 10 business days of receiving the QAQC checklist from the contractor.

The contractor has 10 business days after receiving a corrections list from the RD/MSC/Installation POC to fix the issues and re-submit the checklist addressing each issue.

Appendix A. Integration Ready Definition This appendix defines the criteria for including buildings on the ARIMD “Integration Ready” list.