Attachment 5 - GSA R8 Graphics Standard for Niagara N4 v2.pdf

GSA Public Buildings Service Office of Facilities Management - Facility Technologies

General Services Administration Master Specification

Graphics Standard for Niagara N4

Graphics Standard for Niagara N4 systems applicable to all building automation contractors working for the General

Services Administration in Region 8. This standard covers requirements related to the creation of graphics on the GSA

Region 8 Niagara N4 platform including graphics representations and all associated supporting configurations. All GSA graphics for Niagara N4 will be required to follow the standards as stated in this document.

Document Change Log

Date Revision Comment By

02/02/2021 1.0 1. Document published for use. SClark

10/14/2021 2.0 1. Removed requirement to host graphics at the supervisor and the JACE. Graphics to be hosted at the JACE only

2. Removed the requirements for pop-ups and other links located directly on the graphic page

3. Updated details regarding the use of the Niagara Network

4. Updated Niagara alarming requirements

5. Updated homepage graphic requirements

6. Updated Nav file requirements

7. Added Niagara reporting requirements

8. Added Niagara chart requirements

9. Added Niagara user management requirements

10. Replaced various screenshots with updated copies

11. Cleanup of formatting and other errors

SClark

Table of Contents Graphics Standard for Niagara N4 0

Document Change Log 0

General Graphic Standards 4

Standard Graphic Layouts 4

Equipment Graphics 4

Navigation Graphics 5

Locating Standard Graphics Files 5

Active Graphics File Locations 5

BACnet Devices 6

BACnet Points 7

BACnet Notifications 7

BACnet Trending 7

BACnet Schedules 8

Implementing a Standard Graphic 9

Create Graphic Folder 9

Using Equipment Graphic Standard 9

Graphic Folder Mappings 9

Niagara Devices 10

Graphic Header 10

Graphic Footers 11

Graphic Images 11

Graphic Points and Labels 12

Spectrum Setpoint Binding 13

Niagara Alarming 14

Console Alarms 14

ReNo (Remote Notification) Alarms 14

Niagara Schedules 17

Niagara Reporting 17

Niagara Charts (Trend Views) 18

Niagara Navigation Trees 19

BACnet devices & Control Points 19

Graphics & Links 19

Niagara User Account Management 20

Categories 20

Roles 20

User Prototypes 21

Niagara Network User Sync Settings 21

Equipment Graphic Specifications 21

Air Compressor 22

Air Handling Systems 22

Boiler Graphic (BACnet card) 23

Building Hot Water Circulation Graphic 23

Building Heat Exchanger Graphic 24

Chilled Water Plant Graphics 25

Chiller Summary Graphic (BACnet card) 25

Cooling Tower(s) Graphic (BACnet card) 26

CRAC Units 26

Deionized Water System Graphics 27

Domestic Water Systems 27

Emergency Generator 28

Exhaust Fans 28

Fan Coil Unit 29

Hot Water Plant / Steam Boiler Plant 30

Lab Systems 31

Radiant Heat 31

Solar Systems 32

Unit Ventilators 32

Terminal Units and Zones 33

VFD Summary 33

Window Systems 34

Main Graphic Specifications 35

AHU Summary Graphics 35

Terminal Unit Summary 35

Exhaust Fan Summary 35

Other Equipment Summary (Fan Coil Unit, Unit Heater, Baseboard Radiation, Etc) 36

Floorplan - HVAC/Detail 36

Floorplan - Lighting 37

Floorplan – Navigation 37

Building Home Page Graphic 38

Lab System Equipment Summary 39

Lighting Summary Graphics 39

Lighting Panel Summary Graphics 39

Utility Summary Graphics 40

General Graphic Standards

● All graphics will be created and stored on Niagara JACEs located on the facility’s local area network.

● State and Regional Niagara supervisors will be used as common login points, and will only host summary style graphics and links out to each facility’s JACE.

o State & Regional supervisors will serve as long-term repositories for trend & alarm data, and will administer user accounts

● Any drivers or images used in graphics need to be installed on the local JACE(s).

● Graphics need to be organized into the file structures as outlined in this standard on all N4 systems. This is true even if other graphics previously were not stored in this manner.

● Controllers need to be organized into a standardized folder structure, as stated in this standard.

● Graphics shall be rendered as N4 HTML 5 views. Any graphic pages that in any way depend on browser-side-applets are not permitted.

● Applicable portions of a graphic should be animated. Static graphics for mechanical equipment are prohibited.

● BACnet device & object names will remain unchanged, and Proxy points will be named and organized as described in this standard. All graphic bindings will be bound to the proxy point names.

● Any hyperlinks outside of the GSA firewall are prohibited from being added to any Niagara graphics.

● Vendor names, logos, or other vendor identification or promotion are not permitted on the graphics.

● Creating new folders or alteration of any of the files in the R8_Standards folder is prohibited.

● Objects, graphics, and anything needed to create new graphics using this Standard Implementation Guide will be available on the GSA R8 Niagara N4 supervisor.

Standard Graphic Layouts Graphics are defined as equipment graphics, summary graphics, or navigation graphics. Each graphic type has prebuilt background graphics. Graphic types are described below.

Equipment Graphics Equipment graphics consist of a Graphics background from the

R8_Standards > Backgrounds folder. These backgrounds have pre-built tab panes (each with its own px include), a px include for a header graphic, and a footer bar. This will be used for all graphics with exception of navigation graphics (including home pages) and summary graphics.

Equipment graphic backgrounds include the following pre-built tabs:

● Graphic tab – Includes a PX Include to add in the detail graphic for the system

● Setpoints tab – Section intended for all setpoints and other information that is not included in the PX include standard graphic. This will be built from standard PX includes and pallets included to keep graphics consistent across systems and buildings.

● Schedule tab – Includes a Schedule object to be linked to the system specific schedule. If there is no system specific schedule required for the graphic, the visibility property for this tab will be set to false.

● New tab – Included as a pre-formatted additional tab to be used in scenarios that require another tab. This tabs visibility property, by default, is set to false.

Summary Graphics

Summary graphics consist of a Summary background from the R8_Standards > Backgrounds. These backgrounds have a px include for a header, and a footer bar. This will be used for all required summary graphics. Each of the summary graphics will be built with pre-built px includes and pre-built headers to allow for consistent information and design on each of the summary graphics.

If the information for a summary graphic does not fit on a single px, then multiple summary graphics will be created.

Each summary graphic will be linked to the next and previous summary graphic in the footer allowing for graphical flow between all the corresponding summary graphics.

Navigation Graphics Navigation graphics consist of a Navigation background from the R8_Standards > Backgrounds. These backgrounds have a px include for a header, and a footer bar. Home pages are considered navigation pages, and requirements for these are detailed in the Graphic Specifications section. Other navigation pages will be specified by the GSA R8 BAS team.

Locating Standard Graphics Files All standard graphics for Niagara N4, including px pages, images, and tools will be organized in the GSA R8 Niagara N4 Supervisor file structure. The standardized organization of the File structure for R8_Standards is illustrated as follows:

● _NewBuildingTemplate – A pre-built folder structure to be copied into the

R8_Graphics folder adding graphics for a new building.

● Backgrounds – Includes folders for all the required backgrounds for building a graphic with this standard, includes various sizes for Graphics, Navigation, and Summary graphics.

● Headers – Includes the standard headers formatted and sized to match background sizes. These are also included in the _NewBuildingTemplate folder, and will be formatted per building once copied into the R8_Graphics folder.

● Images – Includes all the standard image files used in any of the standard graphics, headers, buttons, etc. This does not include building specific images, which are saved in the building folders. Any non-building specific images are stored in this file.

● Palettes – Includes all the standard palettes with the pre-formatted points, buttons, objects, etc. as outlined in this graphic standard.

● pxIncludes – Includes all the px files to be added to the background graphics. These are organized into folders by system type, and have multiple versions to select from, matching the configuration of the system. There are text files in each system folder with detailed information about the graphics in the folder.

Active Graphics File Locations All graphics being used in the JACE are classified as active graphics. Active graphics and all corresponding images, navigation files, etc. will be organized and stored in the

R8_Graphics folder in the File structure of the corresponding JACE.

Any graphics, images, or other files that are not active due to controllers being removed or newer graphics being used, are to be removed. Do not leave unused files on the JACE.

All active graphics in each JACE will be organized in a master folder named using the GSA building code and name. Even if a JACE serves only one building, the graphics will be organized by building so that they can be utilized by and/or referenced from associated supervisor stations seamlessly.

The standardized organization of each individual building file structure is illustrated as follows:

● Building Alarms - Every building will have an alarms page displaying the

Niagara alarm console for the building. That graphic will reside in this folder.

● Equipment – All graphics, unless stated otherwise, will be organized in this folder. This folder will also include all equipment specific documents, charts, etc. Each equipment with unique graphics will have a folder matching the equipment name. For equipment that share a multiple graphic, a folder will be created referencing the equipment type. See details for naming in the

Graphic Specification section.

● Floorplans – Floorplan graphics, as outlined in this standard, will be organized into the Floorplans folder.

● Headers – Every building will have a pre-formatted set of headers. These headers will be stored in this Headers folder.

● Images – All images used in a specific building that are not part of a palette will be stored in the Images folder. This folder also includes a Floorplans subfolder that will include all the approved and pre-formatted floorplan image files for the building.

● Navigation – Any navigations files created for the building will be stored in the Navigation folder, including the header graphic.

● RemoteNotifications - Every building will have a RemoteNotifications page to allow the user to add and remove remote notification recipients for the building. That graphic will reside in this folder.

● Reports - Every building will have a Reports page with pre-built report templates for equipment in the building.

The main report page and all individual report pages will reside in this folder.

● Schedules - Every building will have a Schedules page that displays a summary view of all the schedules in the building. That graphic and any related px files will reside in this folder.

● Setpoints - Every equipment graphic will have a Setpoints tab that displays setpoints and alarms for that piece of equipment. The standard setpoint and alarm px files that are references from each of these setpoint tabs will reside in this folder.

● TrendsViews - Every building will have a TrendViews page with pre-built trend views for equipment in the building. The main TrendViews page and all individual trend view pages will reside in this folder.

BACnet Devices All BACnet devices in each JACE will be organized in a master folder named using the

GSA building code and name. Even if a JACE serves only one building, the BACnet devices will be organized by building so that they can be utilized by and/or referenced from associated supervisor stations seamlessly.

BACnet device names will remain unchanged from discovery unless otherwise specified by the GSA R8 BAS Team.

BACnet Points All points will be proxied from the device directly into the points folder under the corresponding device. Once the points are organized into system and equipment folders following the standard organization layouts detailed in the Graphic

Specification section, the building and equipment indicator will be removed from the object name for graphic implementation.

Each device will have folders created underneath it’s Points Folder for each system it hosts points for. The system graphic will be applied to the corresponding system folder that has the primary or predominant control of that system.

Any time there are points from a different building than the device predominantly controls, the building indicator for the unmatching building will be added to the equipment folder name.

Summary graphics and other building graphics that encompass objects and devices in multiple panels will be done under the BACnet building folder and outside of the field panel devices.

BACnet Notifications BACnet notifications will be routed to a Niagara Alarm Class for the building at the JACE, and then passed up to the state supervisor station over the Niagara network. Each BACnet device will be configured to route the alarms to the building alarm class (Example CO0518_DFC44_Alarms).

This also includes controller communication failure alarms. See more information on alarming and additional alarm requirements in the

Niagara Alarming section.

BACnet Trending All trending will be mapped into Niagara as BACnet trend objects from the BACnet devices directly. Trends will be mapped into the JACE and then passed to both the state supervisor station and the R8 supervisor station over the

Niagara network. Trending will be set to import from the devices into the JACE every fifteen (15) minutes, and to roll after 500 entries. For the State Supervisor Station, all trending will be set to import once (1) daily, and will roll after

75,000 entries. For the Region 8 Supervisor Station, all trending will be set to import once (1) daily, and will have unlimited storage.

Metadata tagging will be added to each trend discovered in the supervisor. These tags will be as follows:

● State – This will be the state that the facility resides in (Colorado)

● Building – This will be the building number/name matching the folder structure naming convention (Example

CO0518_DFC44)

● System – This will match the folder name into which the equipment is organized (Example AirHandlingSystems)

● Equipment – This will match the main equipment name, for terminal units, this will be the name of the serving air handling unit or systems.

● Subequipment – This is for equipment that has a different equipment name. This includes terminal units, which will have the air handling unit as the Equipment tag, and the Subequipment tag will match the name of the VAV.

Unless pre-approved by the GSA BAS team, no trending will be created as Niagara trend objects, and no trends will be mapped between Niagara platforms.

BACnet Schedules All schedules will be mapped over as BACnet schedule objects from the BACnet controller directly. This will be done through the Schedule Export Manager. Niagara schedules matching the type and facets of the device schedule will be created in the equipment, system, or building folder, depending on what type the schedule is for. This schedule will be set as the Supervisor Ord in the device exported schedules.

Building & equipment specific schedules will be mapped to the JACE in the building, and will reference centralized holiday and exception calendars from the state supervisor.

Implementing a Standard Graphic When creating new graphics by using the standards graphics, follow these steps:

Create Graphic Folder

● In the R8_Graphics, in the Equipment folder for the Building in which the equipment is located, create a folder structure for the equipment. The folder structure is described in the Graphic Details section.

Using Equipment Graphic Standard

● Look for an existing standard in R8_Standards folder for a graphic as close to the equipment system configuration required.

o Graphics are organized by system type o In each system type folder (e.g. Air Handling Units > Multi Deck Units), reference the Sumary.txt file(s) for a summary of the system configuration for each px file.

● Copy the selected equipment standard graphic for the graphics body to the equipment folder created in R8_Graphics. Do not rename this file.

● After identifying the size of the body px, select the corresponding background graphic size from the R8_Standards Background folder, copy it to the new equipment folder and name the graphic to match the equipment (folder) name.

● Points or images not required for the graphic for this specific equipment type can be deleted in the copied graphics. Nothing will be deleted or changed in the versions stored in R8_Standards.

● New sensors, points, links, etc can be added as needed to the copied graphic as necessary.

● New graphic standards are required when the system does not exist, or there is a significant difference in equipment, piping, etc. from the closest existing standard drawing. All new graphic standards are to be created by the GSA R8 BAS team.

Graphic Folder Mappings All graphics for BACnet controllers will be mapped to a folder as follows:

● Equipment specific graphics controlled predominantly by a single device will be mapped to the folder matching the device name under points. See the BACnet Devices section for folder references.

● Equipment controlled by multiple devices or summary graphics will be mapped to a folder created under the building folder in the BACnet network folder. See the Main Graphics Specification section for more detail on folder naming and mapping.

● All folders with graphic mappings utilizing a px include header will require the addition of two slots (Title and Description) for the header graphic. All points in the graphic will be relativized after the appropriate graphic is applied to the folder.

Niagara Devices All JACEs will be mapped into the State Supervisor Station running on the corresponding supervisor. This connection will be used primarily for automated station backups, alarm routing, trend data, and user management. Select points to be used on summary pages on the supervisor station will be mapped as Niagara points from the JACEs into the supervisor.

JACEs will be organized in the Niagara Driver folder by state and by building with folder structures and naming following the same standard as laid out in the BACnet Controllers section.

Graphic Header Each main graphic requires a header matching the size of the background graphic canvas.

There are template graphics for each header size (Small, medium, and large) located in the

R8_Standards folder that will need to be copied into each JACE and customized for the building. The customized cipes for each building should be placed in the R8_Graphcis folder under the Headers folder.

Button description and actions are as follows (All links are completed with bajaui:Value Binding):

1 – Preconfigured BackButton from the kitPx palette

2 – Campus Home button (Included in R8_Standards.palette) with a link to the Home.px main campus page located in R8_Graphics _Main folder.

3 – Building Home page to be linked to the homepage for the building, different on every set of header templates.

4 – Link to the schedules page showing an overview of all the schedules for the building.

5 – Preconfigured LogoffButton from the kitPx palette.

6 - Preconfigured ForwardButton from the kitPx palette.

7 – The unbound text fields set up on BoundLabel objects.

For non-building navigation graphics – The top line is set to “General Services Administration” and the bottom line is set to “Home Page”.

For all other graphics - The top line is for the campus or state and city (If no campus name exists) and the bottom line is for the building name, and following in parentheses, the building code.

8 – A BoundLabel object with ord set to the slot:Title.

9 – A BoundLabel object with ord set to the slot:Description.

10 – A BoundLabel object with a Bound Label Binding with the ord set to null. The test is animated to “Current

Time: %time()%” allowing the current time to be displayed.

11 – A set of BoundLabels. These are to have the kitPx:Bound Label Binding properties ord set to the weather channel corresponding to the city location of the building. The top line is the current temperature, and the bottom line is the current humidity.

Graphic Footers Graphic footers are required whenever an additional link is required outside of the hyperlinks/actions in the header, and the links on the graphic specific to the graphic contents.

Pre-built footers are included in the R8_Standards folder. However, if any changes are necessary, all preconfigured buttons/links (listed here) are available in the standards palette and on graphic templates.

● Schedule – Link to the schedule, no special graphic, just the schedule itself

● Floorplan - Link to the associated floorplan

● Trends – Link to trends folder for equipment, see more information in the Trending section

● TU Summary - Link to the associated terminal unit summary graphic

● AHU Summary - Link to the associated AHU summary graphic

● Hot Water System - Link to the associated hot water system graphic

● Chilled Water System - Link to the associated chilled water system graphic

● Sequence – Link to a PDF of the sequence saved on the GSA R8 Niagara N4 supervisor in the R8_Graphics folder.

● Link to Parent Graphic – Link to the parent graphic, as stated in the Graphic Details section.

Graphic Images

● All active graphics must be generated using one of the following palettes:

o kitPxGraphics o webChart o bajaui

● If additional pallets are desired for graphical generation, they must be approved by the GSA R8 team prior to implementation.

● All palette images from the palettes above must remain in the default px folder in the file structure. This folder is prohibited from being altered in any way.

● All palette images Value Binding properties, unless otherwise noted, must be set as follows:

o hyperlink to null o summary to null o popupEnable to false

● All images not from a palette must be in an Image object and are not permitted to be in a Label object.

● All images must be saved in Image folder on the JACE or Supervisor that the image is being used on.

● All images must be formatted to a size matching the Picture object and must have the scale set to None. Scaling of images is not permitted.

Graphic Points and Labels All graphical points and labels will need to be configured to match the GSA standards. All pre-formatted labels and points are available in the standard palettes on the R8 N4 Niagara Supervisor. All hardwired, controlled setpoints, and alarms will be visible on main graphics. All other points, including lockout points, configuration points, gain values, and detailed alarms will be available on the setpoints tab of the graphic.

There are three different label options for body graphics (Not including headers) as follows:

● Points Label – Used for all point name labeling

● Equipment Label – For sub equipment labeling

● Table Label – Headers for all table data in summary graphics

There are three different bound label options as follows:

● Write points – For all points that have a set or an override option

● Read points – For all points that do not have a set or an override option.

● Spectrum Points – For all points that require spectrum-built colorization.

All points will be configured as followed:

● Writeable points that are intended for override only will have the SET action flag hidden

● All writable points will have their Emergency Override and Emergency Auto action flags hidden.

● All writable points will have a facet to limit the max override time to (8) hours, with exception of court houses with a max of (12) hours override time.

● All space temperature setpoints will have a limit of 70°F minimum and 75°F maximum, with exception of court houses with a minimum of 65°F.

● All points that have an available trend will have the points hyperlink property set to the corresponding trend.

Numeric points, if not already configured in the controller, will have the units and precisions set to the following standards:

Category Engineering Unit Abbrev Precision

Electrical Voltage Alternating Current Volts VAC 0.1

Electrical Current Amperes A 0.1

Thermal Energy British Thermal Unit BTU 0.1

Natural Gas Volume Cubic Feet CF 0.1

Air Flow Volume Cubic Feet per Minute cfm 1

Electrical Voltage Direct Current Volts VDC 0.1

Temperature Fahrenheit °F 0.1

Air Flow Velocity Feet per minute fpm 0.1

Water Volume Gallons Gal 1

Electrical Power (Real) Gigawatt GW 1

Time Hours h 0.1

Natural Gas Volume Hundred Cubic Feet CCF 1

Air Pressure Inches of Water Column inWC 0.01

Air Pressure Differential Inches of Water Column inWCD 0.01

Electrical Energy (Apparent) Kilovolt-ampere-hour kVAh 1

Electrical Power (Apparent) Kilovolt-amperes kVA 1

Electrical Power (Real) Kilowatt kW 1

Electrical Energy (Real) Kilowatt-hour kWh 1

Electrical Power (Real) Megawatt MW 1

Electrical Current Milliamps mA 0.1

Thermal Energy Million BTU MMBTU 1

Electrical Voltage Millivolts mV 0.1

Time Minutes m 0.1

Electrical Energy (Real) MW-hour MWh 1

Carbon Dioxide (CO2) Parts per Million ppm 1

Carbon Monoxide (CO) Parts per Million ppm 1

Volatile Organic Compound (VOC) Parts per Million ppm 1

Relative Humidity Percentage % 0.1

Modulating Command / Feedback Percentage (Open/Closed) % 1

Water Pressure Pounds per Square Inch psiG 0.1

Water Pressure Differential Pounds per Square Inch Differential psiD 0.1

Time Seconds s 1

Thermal Energy Thousand BTU MBTU 1

Natural Gas Volume Thousand Cubic Feet MCF 1

Thermal Energy Tons of Cooling Tons 0.1

Electrical Energy (Apparent) Volt-ampere-hour Vah 0.1

Electrical Power (Apparent) Volt-amperes VA 0.1

Electrical Power (Real) Watt W 0.1

Electrical Energy (Real) Watt-hour Wh 0.1

Boolean points, if not already configured in the controller, will have the following TRUE/FALSE values:

● Commands – Start / Stop

● Enables – Enable/Disable

● Alarms – Alarm / Normal

● Status (With exceptions to actuators) – On/Off

● Actuator Status – Open/Closed

● Resets – Reset/Off

Spectrum Setpoint Binding For floorplan and summary graphics, all setpoints will require spectrum point and setpoint bindings for colorization.

These objects can be found pre-configured in both the corresponding graphic standards, and in the standard palettes.

Niagara Alarming Each building will have two Niagara alarm classes built

(ConsoleAlarms & ReNoAlarms) and the alarms will be routed accordingly. Each building will have its own alarm console named after the building (Ex. CO0518_DFC44_AlarmConsole) that will be linked to the alarms link button on the building home page graphic.

Each building will also have a total number of alarms counted for both the Console and ReNo alarms linked to a numeric point for each building footer to depict the total number of active alarms (Ex CO0518_DFC44_AlarmCount)

The alarms will be organized into the two classes discussed above according to the following requirements:

Console Alarms All BACnet alarms that come from the devices will be routed to the “ConsoleAlarms” alarm class in the JACE. This will be done by setting each BACnet device to route it’s alarms to that alarm class in the Alarms menu of the device.

Once this setting has been configured all alarms coming from this device should be routed to the “ConsoleAlarm” class and then should be displayed on the building’s alarm console for alarm management by the facilities team.

ReNo (Remote Notification) Alarms Niagara alarm extensions will be created for alarms that are classified by the GSA as requiring Remote Notification

(ReNo) to the facility team(s). These will be duplicate alarms to the default alarms, and therefore will only be routed to an email recipient rather than to the alarm console. Each ReNo alarm that is created using a Niagara alarm extension will have the alarm class changed to match the correct building and ReNo alarm class.

A Remote Notifications email recipient will be built for each building, and will be named using the GSSA building code, building name and

Remote Notification designations (Ex.

CO0518_DFC44_RemoteNotifications). The email recipient will be configured as shown in the screenshot to the right. The “to” property of this email recipient will be exposed on the

“RemoteNotifications” graphic for each building to allow the users of the system to add/remove facility operators to this email recipient as needed.

To ensure that the console alarms and remote notification alarms stay in sync with each other, all Niagara alarm management will be done using the BACnet alarm properties of the alarmable object (not using properties of a Niagara alarm extension). These properties must be discovered along with the objects from the BACnet device, and will be organized underneath the corresponding object in the device points folder. For example, the temperature object shown below has had the deadband, eventState, highLimit, lowLimit & timeDelay BACnet properties discovered and added to

Niagara to allow the user to manage all alarm properties from the graphics.

To generate the remote notification alarms, a custom built Niagara Alarm extension called “ReNo Ext”will be used for all remote notification objects and will be added to the BACnet “eventState” property of the alarmable object. The “ReNo

Ext” is available in the pallets provided in the R8_Standads folder and is configured as shown below:

Once the custom “ReNo” alarm extension has been added to the object as described above, a templated pxinclude can be placed on the associated graphic’s setpoint tab to expose these BACnet alarm properties as well as check boxes for the user to choose if/when the system will generate the remote notification to the remote notification email recipient list previously discussed.

The following list is alarming that the GSA requires as “Remote Notification” alarms wherever applicable

● BACnet Device Communication Failure

● JACE Communication Failure

● Supervisor Communication Failure

● Chiller Failure – When any chiller command is true, and the status is false after an appropriate time delay

● Chilled Water Pump Failure – When any chilled water pump command is true, and the status is false after an appropriate time delay

● Condenser Water Pump Failure – When any condenser water pump command is true, and the status is false after an appropriate time delay

● Cooling Tower Fan Motor Failure – When any cooling tower fan command is true, and the status is false after an appropriate time delay

● Boiler Failure – When any boiler command is true, and the status is false after an appropriate time delay

● Hot Water Pump Failure – When any hot water pump command is true, and the status is false after an appropriate time delay

● AHU Fan Motor Failure – When any air handling fan command is true, and the status is false after an appropriate time delay

● High Sump Pump Pit Level Alarm – When any high sump pump pit level indicator is true

● Fire Alarm – When any fire alarm indicator is true

● Chillers and Boiler running simultaneously – When a building has both a chilled water plant and a hot water plant enabled at the same time

● Chiller / Boiler Excessive Run Time – When a Chiller or Boiler has been running more than 12 hours in a day on a weekend or holiday.

● Data Center / Server Critical Alarm – When any critical alarm point proxied from a CRAC unit is indicating the unit is in alarm.

● Fume Hood Low Flow Alarm – When any fume hood flow is below the flow setpoint for at least 5 minutes.

Niagara Schedules All schedules will be mapped over as BACnet schedule objects from the BACnet controller directly. These will be mapped into the JACE in the building, and will reference centralized holiday and exception calendars from the state supervisor.

On the JACE, a Niagara schedule matching the BACnet schedule type will be created and linked to the BACnet schedule in the device through the niagara schedule export manager to export the schedule to the controller every 15 minutes. For all building level schedules, the Niagara schedules will be created in a BuildingSchedule folder created under the building folder.

Each schedule will be linked to the equipment graphic that it corresponds to as well as to the schedule summary page that is linked in the header of each graphic.

Niagara Reporting Standard reports will be configured on each JACE to allow the user to easily access commonly needed data and information about system status. A “Reports” page will be created for each building, and all reports for that building will be available on that page. This page will also allow the user to edit the recipient list of a Niagara email recipient named after the building (Ex.

CO0519_DFC45_ReportsRecipient).

The following reports will be available for each building:

● Overrides - Report showing any control point in that building that has a status of “overridden”

● ReNo - Report showing and points that are configured to send remote notifications

● DeviceStatus - Report showing the status of all BACnet devices that communicate to that JACE

● FailedDevices - Report showing any BACnet devices that communicate to that JACE with a status of “failed”

● FailedPoints - Report showing any control points that communicate to that JACE with a status of “failed”

These standard reports for each building will have options to View, Email or Schedule the report as desired. Selecting one of these options should perform the following action:

● View - Open a Px Page on the JACE to display the report contents

● Email - Send an email to the “ReportsRecipient” list containing the report contents

● Schedule - Open a schedule editor that allows the user to schedule the report to run and email out

In addition to the standard reports defined above, a separate report for each system within the building will be built to display all points associated with that system. This report type will display the following information

● Building - The GSA building code for the building

● System - The name of the system (Ex. A01)

● Point Name - The proxy point name of the control point in Niagara

● Value - The current value of the point

● Status - The current status of the point showing the override priority if applicable

These system points reports for will have options to View orEmail. Selecting one of these options should perform the same actions as described above.

All Niagara reports will be built using component grids. Report templates for all report types are available on the Region

8 Niagara system that can be referenced to create new reports.

Niagara Charts (Trend Views) Customizable Niagara charts will be configured on each JACE to allow the user to easily access commonly viewed trend data for each system in the building. A “Trend Views” page will be created for each building, and all customizable Niagara charts for that building will be available on that page. Links to system specific charts will also be placed on the associated system graphic to allow the user to get to the same chart.

Each niagara chart should be populated with important system trend information such as temperatures & damper positions to start, and should allow the user to customize what is on the chart for themselves so they can create a view that they prefer.

Chart templates that are formatted as required by this standard are available on the Region 8 Niagara system that can be referenced to create new charts.

Niagara Navigation Trees Each JACE with graphics will require a graphical navigation tree. An example navigation tree is available in the standard graphics on the GSA R8 Niagara N4 supervisor.

All graphics, floorplans, alarm consoles, trends, charts, and documents available on the JACE will be included in the nav file. Additionally, a device based navigation to view BCAnet field devices and their associated control points will be included in the root of the building’s nav file titled

“BACnet Devices”. This NAV file will be named “Navigation” and will reside on the JACE in the

“nav” folder under the files.

BACnet devices & Control Points This view will be structured to show each BACnet device that is integrated to the JACE and all associated control points. The links in this section of the nav file will take the user to the AX

Property Sheet view of each BACnet device and subsequent points folder. The folder organization and naming of this nav tree section should match the organization and naming of the BACnet driver.

Graphics & Links This view will be structured to show all of the graphics and links that the user has access to. The links in this section will take the user to the graphical depiction of the system, chart, graph, report, etc associated with the system it represents.

An example of the final nav tree structure is shown in the screenshot below:

The naming and the organization of the navigation tree components for each system type is laid out in the “Equipment Graphic Specifications” & “Main Graphic Specifications” sections. The icons for the navigation tree will be matched to the example navigation tree in the graphic standards.

Each graphic component in the navigation tree will be represented with a folder that links you to the graphic, and will include the following components if applicable and components exist:

● Trends – Linked to a blank AX trend builder view containing the trends for that piece of equipment (This should link to the same place that the footer Trends link does)

● Schedule – Linked to the schedule for the corresponding equipment.

● Sequence – Linked to the PDF of the sequence for the corresponding equipment (if applicable).

Niagara User Account Management All Niagara users will be administered through the Region 8 Niagara Supervisor Station and passed down to the appropriate stations (State supervisors & JACEs) throughout the region over the Niagara network. This will be accomplished by configuring the following items at each JACE and Supervisor station:

● Categories

● Roles

● User Prototypes

● Niagara network User Sync Settings

Once the above items are configured as specified below, new users can be added in one place at the Region 8 Supervisor

Station and distributed automatically to other stations.

Categories Categories will be configured in a standard way across the regional Niagara system so that the administration of user accounts is seamless as users move between Niagara stations. All stations (Supervisors & JACEs) will have the following 3 categories as standard:

1. OM - Short form “Operations & Maintenance” this category will provide read, write & invoke access to the day-to-day operational aspects of each station

2. Contractor - This category will provide read, wite & invoke access to the the majority of the station and will be used by ant contractors working on the system

3. GSA - This category will provide read & wite access (no invoke) to the whole station and will be used by GSA teams such as energy teams

The remaining categories on each station (Supervisors & JACEs) will be used to assign access rights to different facilities or groups of facilities served by a single station. The exact configuration of these categories will vary between stations based on what that station serves. An example is below:

4. Colorado - This category would provide access to all facilities in Colorado

5. DFC - This category would provide access to all facilities on the Denver Federal Center Campus

6. DFC_TeamXX - This category would provide access to all facilities that a certain O&M Team has

7. CO0518_DFC44 - This category would provide access to only that facility

Existing category assignments that follow this standard are available on the Region 8 Niagara system that can be referenced to create new assignments.

Roles Roles for each desired access level will be created at each Niagara station. Any given role will typically consist of 2 category assignments:

● One for the user type (OM, GSA, or Contractor)

● One for the facility assignment (Colorado, DFC, DFCTeam02, Etc)

The roles will receive read, write & invoke access as follows:

● OM - Will get Operator read, write & invoke as well as Admin Read (rwiR)

● Contractor - Will get Operator read, write & invoke as well as Admin read, write & invoke (rwiRWI)

● GSA - Will get Operator read & write as well as Admin read & write(rwRW)

Existing role assignments that follow this standard are available on the Region 8 Niagara system that can be referenced to create new assignments.

User Prototypes User prototypes must be configured at each Niagara station to support the synchronization of users over the Niagara network. Each new user built at the Region 8 Niagara Supervisor will be assigned a prototype, and that user will then be automatically synchronized to any other station on the Niagara network that contains that same prototype. Prototype names must match exactly between stations for synchronization to work. All prototypes will follow the structure as defined below:

User Prototype Naming Structure: R8_AA_BBB_CCCC

● R8 - Standard prefix for all Region 8 users

● AA - Designator for the state that the prototype should sync to (All, CO, UT, SD, ND, Etc)

● BBB - The campus, group or facility (DFC, DFCTeam02, CO0518_DFC44)

● CCCC - The user’s Role assignment (SuperUser, Contractor, GSA, OM, Etc)

Each prototype will be assigned a Nav file, a Role assignment, Default Web Profile settings & Mobile Web Profile settings at each niagara Station as appropriate to grant the desired access rights to that user type.

Existing User Prototype assignments that follow this standard are available on the Region 8 Niagara system that can be referenced to create new assignments.

Niagara Network User Sync Settings Once all of the other Niagara User Management settings (categories, roles & user prototypes) have been configured, the Niagara network user sync settings can be configured to allow users to be passed between stations as desired. The User Sync settings must be configured both at the

Supervisor station and at the JACE in a corresponding fashion.

The Region 8 supervisor station will be set to sync out to all of the state supervisors, and all of the state supervisor stations will be set to sync out to all of the JACEs in that state. Configuration of user syncing will require the use of a local niagaranetworkuser account that the Region 8 BAS Team will administer.

Existing user sync setting assignments that follow this standard are available on the Region 8

Niagara system that can be referenced to create new assignments.

Equipment Graphic Specifications The equipment graphic specifications include details that must be included for each equipment graphic built in the system. For each of these graphics, reference the standard graphics and standards palette for formatting of shapes, labels, and points.

The following parameters are specified for each graphic type in this section:

● Point Folder Org – How the points are organized in the device tree

● Filed Folder Org – How the graphics are organized and named in the file tree

● Navigation Tree Configuration - How the equipment will be referenced in a navigation tree file

● Footer Links – Required links to be included in the footer and the order

● Metadata Tagging – How the trending is tagged

● Home Page Reference – How the equipment is referenced on the navigation home page of the building

Air Compressor

Point Folder Org Under building folder in device folder named AirCompressors.

File Folder Org Equipment > AirCompressors with a folder named the same for each piece of equipment associated with this system.

Navigation Tree Configuration In root of building nav file with component named Air Compressor.

Footer Links

● Floorplan with location to Air Compressor.

Metadata Tagging

● Building = Approved building identification code

● System = AirCompressors

● Equipment = Equipment identification code in object naming

● Subequipment = NA

Home Page References

● Air Compressor Status

● Control Air Pressure

● Local Air Compressor Alarm

Air Handling Systems

Point Folder Org Under building folder in device folder named AirHandlingSystems.

Filed Folder Org Equipment > AirHandlingSystems with a folder named for each unique air handling unit equipment layout associated with this system, matching the equipment identifier in the object name.

Navigation Tree Configuration In an Air Handling Systems folder with name matching the equipment name.

Footer Links

● Zone Summary of muli-zone systems

● Equipment link to any shared air handling unit

● Recovery unit if separate graphic.

● Hot water plant or building heat exchanger if hot water coil.

● Steam boiler plant if steam coil.

● Chilled water plant if chilled water coil.

● Air compressor if pneumatic controls.

● VFD information graphics.

Metadata Tagging

● Building = Approved building identification code

● System = AirHandlingSystems

● Equipment = Equipment identification code in object naming

● Subequipment = NA

Home Page References

● If multiple air handling units per building, only reference if informed to do so for specific critical units

● For critical or single-unit buildings:

o System command o Schedule command linked to schedule o Discharge air temperature o Discharge air setpoint o Static Pressure o Static Pressure setpoint o Local equipment alarm

Boiler Graphic (BACnet card)

Point Folder Org Under building folder in device folder named HotWaterSystems

Filed Folder Org Equipment > HotWaterSystems with a folder named the same for each unique boiler associated with this system.

Navigation Tree Configuration In Hot Water System of building nav file with component named Boiler xx matching the boiler identification code.

Footer Links

● Hot water system / steam boiler plant graphic

● VFD for boiler circulation pump

Metadata Tagging

● Building = Approved building identification code

● System = HotWaterSystems

● Equipment = Equipment identification code in object naming

● Subequipment = NA

Home Page References

● Boiler Status

● Local Boiler Alarm

Building Hot Water Circulation Graphic

Point Folder Org Under building folder in device folder named HotWaterSystems, graphic on folder names CircSystem

Filed Folder Org Equipment > HotWaterSystems > CircSystem with a folder named the same for each for each unique circulation system layout associated with this system.

Navigation Tree Configuration In Hot Water System of building nav file with component named Circulation System.

Footer Links

● Hot water system / steam boiler plant graphic

● VFD information graphics.

Metadata Tagging

● Building = Approved building identification code

● System = HotWaterSystems

● Equipment = Equipment identification code in object naming

● Subequipment = Equipment identification code in object naming

Home Page References

● Building Hot Water Supply Temperature

● Building Hot Water Supply Temperature Setpoint

● Building Hot Water Differential Pressure

● Building Hot Water Differential Pressure Setpoint

Building Heat Exchanger Graphic

Point Folder Org Under building folder in device folder named HotWaterSystems, ChilledWaterSystems, or DomesticWaterSystem

(Whichever the heat exchanger is servicing) graphic on folder name matching heat exchanger equipment name.

Filed Folder Org Equipment > HotWaterSystems (Or whichever corresponding system) with a folder named the same for each for each unique layout associated with this system.

Navigation Tree Configuration In Hot Water System (Or whichever corresponding system) of building nav file with component named Heat

Exchanger xx matching the heat exchanger identification code.

Footer Links

● Hot water system / steam boiler plant graphic.

● Circulation pump graphics

● VFDs for associated pumps

Metadata Tagging

● Building = Approved building identification code

● System = HotWaterSystems

● Equipment = Equipment identification code in object naming

● Subequipment = NA

Home Page References

● System command

● Schedule command

● Primary heat exchanger supply temperature

● Secondary heat exchanger supply temperature

● Secondary heat exchanger supply temperature setpoint

● Secondary heat exchanger return temperature

Chilled Water Plant Graphics

Under building folder in device folder named ChilledWaterSystems, graphic on folder matching plant name.

Filed Folder Org Equipment > ChilledWaterSystems with a folder named the same for each for each unique system layout.

Navigation Tree Configuration In Chilled Water System of building nav file with component named matching the plant name.

Footer Links

● Cooling tower graphics

● VFDs for associated pumps

● Building chilled water graphics

● Air compressor if pneumatic control

● Major equipment or minor equipment summary pages utilizing chilled water

Metadata Tagging

● Building = Approved building identification code

● System = ChilledWaterSystems

● Equipment = Equipment identification code in object naming

● Subequipment = NA

Home Page References

● Chilled Water System Command

● Chilled Water Schedule Command

● Chilled Water Supply Temperature

● Chilled Water Supply Temperature Setpoint

● Chilled Water Supply Pressure or Chilled Water Differential Pressure where applicable

Chiller Summary Graphic (BACnet card)

Point Folder Org Under building folder in device folder named ChilledWaterSystems.

Filed Folder Org Equipment > ChilledWaterSystems with a folder named the same for each unique chiller associated with this system.

Navigation Tree Configuration In Chilled Water System of building nav file with component named Chiller xx matching the chiller identification code.

Footer Links

● Chilled water system

● VFD for chiller circulation pump

Metadata Tagging

● Building = Approved building identification code

● System = ChilledWaterSystems

● Equipment = Equipment identification code in object naming

● Subequipment = NA

Home Page References

● Chiller Status

● Local Chiller Alarm

Cooling Tower(s) Graphic (BACnet card)

Point Folder Org Under building…