Fort_Benning_Niagara_AX_Programming_and_Graphics_Standard_Rev_0.pdf

Fort Benning EMCS DDC

NiagaraAX Control System

Graphics and Programming Standards

Revision 0

February 19, 2013

Prepared by:

Michael L. Aident, P.E., CEM

Approved by:

Mickey Livingston – Tiya EMCS Shop Lead

Danny Leonard – Tiya Utility Manager

Graphics and Programming Standards

Table of Contents

Section Title Page

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 2/19/2013ii

1.0 Introduction and Overview 1

2.0 Color Pallet for Screen Graphics 1

2.1 Default Colors 1

2.2 General Information 2

2.3 Process Status and Data 2

2.4 Point Status 3

2.5 Alarms 3

2.6 Set points 3

2.7 Occupancy Schedule 4

2.8 Override Values 4

2.9 Headers 4

2.10 HOA Switch 4

2.11 Air Flow Arrows 4

3.0 Fonts and Font Size 5

4.0 Standard Building Graphics Screens 5

5.0 Screen Titles - Header 5

6.0 Standard Buttons 5

6.1 Niagara Main Menu 5

6.2 Building Summary 6

6.3 As Built Drawings 6

6.4 Navigation Buttons 6

7.0 Equipment Operational Status 6

8.0 Building Summary Screen 7

9.0 Occupancy Schedules 8

10.0 Schedule Status 9

11.0 Outside Air Temperature 9

12.0 Screen Graphic Text Descriptions 9

13.0 Air Handler Status and Controls 9

13.1 Fan Command 9

13.2 Fan Status 9

13.3 Fan Override Status 9

14.0 Pump Status and Controls 10

14.1 Pump Command 10

14.2 Pump Status 10

14.3 Pump Override 10

15.0 UMCS Operator Override Capabilities 10

16.0 Alarms 12

16.1 Summary Screen - Supply Air Fan Status Alarm 12

16.2 Summary Screen – Sensor Alarms 12

16.3 Summary Screen Filter Alarm 13

Graphics and Programming Standards

Table of Contents

Section Title Page

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 2/19/2013iii

16.4 Freeze Stat Alarm 13

16.5 Smoke Sensor Alarm 13

16.6 Detail Mechanical Screen Alarms (Air handlers, Chillers, Boilers) 14

17.0 VAV Data 14

18.0 Freeze Protection 15

19.0 Point Naming and Numbering Convention 15

20.0 Drawings and Documentation 16

21.0 Floor Plans 16

22.0 Photocell Operated Lights 18

Attachments

A – General list of abbreviations and acronyms.

B – Glossary of Terms from UFC 3-401-01 (November 19, 2008).

C – Default Building Occupancy Schedule.

D – Standard for Screen Graphic Abbreviations.

E – NiagaraAX Control System Point Naming Convention.

Graphics and Programming Standards

List of Acronyms

AHU (AHU1, AHU-2, etc.) – Air handler unit

CO – Carbon monoxide

CO2 – Carbon dioxide

DDC – Direct Digital Control

EMCS – Energy Management Control System

HOA – Hand-off-auto

IWC (iwc) – Inches of water column

MAT – Mixed air temperature

NOx – Nitrogen oxides

O&M – Operation and Maintenance

PPM (ppm) – Parts per million

RAT – Return air temperature

SAT – Supply air temperature

SPAT – Space air temperature

UMCS – Utility Management Control System

VAV – Variable air volume

VSD – Variable speed drive

VVT – Variable volume and temperature

Fort Benning UMCS Standards Graphics and Programming

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 1 2/19/2013

Fort Benning EMCS DDC NiagaraAX Control System

Graphics and Programming Standards

1.0 Introduction and Overview

These standards are intended to describe the minimum requirements for the NiagaraAX control system screen graphics and programming as implemented at Fort Benning, Columbus, Georgia.

When a change to the implementation of these standards is required (i.e., delete a program feature from the graphics) or a feature is not addressed in this standard and needs to be added, the contractor shall request written authorization from Tiya prior to making the change.

These standards shall be implemented for all graphics developed using NiagaraAX version 3.5 or later and shall apply to anyone implementing projects that require operator screen graphics and/or programming using NiagaraAX. The contractor shall apply these standards to the greatest extent possible for earlier versions of NiagaraAX, Niagara R2, and other control system graphics packages deployed at Fort Benning.

The Contractor shall develop the operator screen graphics and control system programming so that the look and feel of the graphics is consistent with this standard and the example screen graphic figures included in this standard.

2.0 Color Pallet for Screen Graphics

2.1 Default Colors

All color selections shall be the NiagaraAX default standard unless specifically called out below.

Default Background Color – Silver (Tridium color code: #cbc8c8) except for status, setpoint, alarm, and other data cells.

Default Text – Black

Alarms – Red background (Tridium color code: #ffff0000) background with black text (no flashing).

Operator Override (Active) – Burnt orange (Tridium color code: #ff8000) background with black text

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 2 2/19/2013

Operator Override (Not Active) – White (Tridium color code: #ffffff) background with black text

Figure 1 – Example Air Handler Screen Graphic

2.2 General Information

General information includes descriptions or names of points such as Mixed Air Temp, Cold Water Valve, Return Air CO2, etc. This information shall be shown as back text on a silver background (Tridium color code: #cbc8c8). Upper and lower case text shall be used with the first letter in each word capitalized. Examples of this are shown in Figure 1.

2.3 Process Status and Data

Process information and data includes temperatures, concentrations, status, and other process parameters that the operator cannot set or override. This process information shall be black text on a white background. The process data cells shall have a black border. All temperatures shall

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 3 2/19/2013 be reported with 1 decimal point. For example the temperature would be displayed as 72.6ºF.

All CO2 sensor values shall be displayed with no decimal point. For example the CO2 concentration would be displayed as 537 ppm. All percentages shall be displayed with 1 decimal point. For example, a valve would be 100.0%. All supply air pressures that are measured in inches of water column shall be displayed with 2 decimal points. For example, 3.51 iwc.

2.4 Point Status

The NiagaraAX colors for point status shall be the standard default for the system as listed below.

Point Status Background Color (Tridium color code)

Foreground Color (Tridium color code)

Alarm Red (ffff0000) Black

Disabled Light gray (dddddd) Coalish gray

Fault Orangish (ffaa26) Black

Down Yellow (ffff00) Black

Stale Reddish gray (dbcbae) Black

Null Clear Clear

Unacknowledged alarm Clear Clear

2.5 Alarms

All alarms shall be shown as black text on a Red background. (Note: Red is not used in screen graphics except to designate an alarm condition.) Where the alarm box includes text, the text is black. No other colors are used for alarms. Alarms do not flash. Alarms shall be shown with a black outline. See Return Fan Command in Figure 1.

2.6 Set points

All set points that the operator can adjust are shown as black text on a white background, similar to all other process data. The border of the setpoint cell changes to yellow when the mouse pointer scrolls over the cell. Once an override value is entered for the setpoint the background color shall change to a burnt orange with black text. The cell containing the override value shall have a black border. See cold water valve override in Figure 1.

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 4 2/19/2013

2.7 Occupancy Schedule

The button used to access the building occupancy schedule is shown as black text on a white background. The cell shall have a black border. See AHU 1 Schedule in Figure 1. The background color of this cell will change to cyan (Tridium color code #ff00ffff) indicating the operator can change or adjust this parameter.

2.8 Override Values

All fields that contain an active override value have black text on a burnt orange background.

The cell shall have a black border. Examples of this are shown for the Return Fan Override and Cold Water Valve overrides in Figure 1.

2.9 Headers

The colors used in the headers shall be as shown in Figure 1. The top header that includes the building number and name shall be light blue (Tridium color code: #c0c0ff) background with white text. The other header that includes quick links to other screen graphics shall be light grey (Tridium color code: #e0e0e0) background with black text.

2.10 HOA Switch

The local hand-off-auto (HOA) switch for air handlers, fans, pumps, etc. shall be connected to the DDC to show the position of this switch. The screen graphics colors to use for the HOA switch are listed below:

Hand – Magenta (Tridium color code: #ffff00ff) background with black text, with black border.

Off – White (Tridium color code: #ffffff) background with black text, with black border.

Auto – Green (Tridium color code: #40ff40) background with black text, with black border

Examples of the possible HOA indications is shown in Figure 1 for the Return Fan HOA Status (OFF) and for the Supply Fan HOA Status (HAND).

2.11 Air Flow Arrows

The flow direction of the air on the air handler screen graphic shall be indicated via green arrows. An example of the arrows indicating the air flow direction is provided in the Figure 1 example air handler screen graphic.

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 5 2/19/2013

3.0 Fonts and Font Size

The fonts used to create the graphics shall be as listed below:

Main Headings – Aerial 18 point (white)

All other Text – Tahoma 12 point (black)

4.0 Standard Building Graphics Screens

The standard screen graphics for each building shall include the following (where appropriate).

- Building Summary Screen

- Air Handler Summary Screen (s)

- Air Handler Screen (s)

- Boiler Screen

- Chiller Screen

- VAV Summary Screen

- VAV Screen (s)

- Floor Plan Screen (s)

5.0 Screen Titles - Header

Each screen graphic shall display the building number and name. It is not required to display “Fort Benning” on each screen graphic. Additionally the screen title should include for example the air handler and its zone. If no distinct zone is identified for the air handler it is not required to include this information in the title. An example header is shown in Figure 1 for Building 101.

6.0 Standard Buttons

Each screen graphic will be programmed to include “standard” buttons (where appropriate) to quickly navigate to other graphic screens associated with that building. These standard buttons shall be located in the secondary header near the top of the screen graphic.

6.1 Niagara Main Menu

This button will display a summary of all buildings that are integrated into the UMCS control system. The “Niagara Main Menu” is a summary screen that shows all of the buildings that are tied into the UMCS DDC (Building name and number) along with an icon with web link that when selected will bring up the summary page screen graphic for that building. Note: The Niagara Main Menu will be located on the NiagaraAX server when available.

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 6 2/19/2013

6.2 Building Summary

This button will bring up the summary screen for this building. The summary screen shall include key information about the building’s mechanical systems. The building summary will differ from building to building based on the mechanical systems in that building.

6.3 As Built Drawings

This button provides a link to the as-built drawings files for this building. The as-built drawings will be stored as PDF files on the Niagara R2 server until the NiagaraAX server is installed and operational.

6.4 Navigation Buttons

Navigation buttons shall be programmed into the secondary header to access other screens associated with the building such as VAVs, Boilers, Chillers, etc.

7.0 Equipment Operational Status

In general the operational status of equipment shall be displayed on the screen graphics using standard NiagaraAX animations. Text and text status blocks shall not be used to display the equipment status unless an operational animation is not available for the equipment. On summary screens where there are no depictions of the equipment, the operational status will be displayed as described in the summary screen section of this standard.

Animations should be used for the following equipment items to display status.

1. Fans (supply and return)

2. Pumps

3. Cooling Towers

4. Chillers

5. Dampers (Outside Air, Return Air, Exhaust/Relief, Mixed Air, Bypass/Face, Zone, Zone Hot Deck/Cold Deck)

6. Valves/Coils (Cooling, Heating, Dual Temperature, Preheat, Reheat, Hot Deck/Cold Deck)

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 7 2/19/2013

The building summary screen will indicate via colors, the status of the air handler systems. A colored circle in front of the air handler ID indicates the operational status of that air handler.

Green – air handler is ON (not in alarm)

Grey – air handler is OFF (not in alarm)

Red – air handler is in Alarm (status is different from command)

8.0 Building Summary Screen

A summary screen shall be provided for each Building. Layout and content of the summary screen should be similar to the Building 101 summary screen. The order in which the information and data is to be presented on the summary screen is important and shall be as listed below and not be rearranged without approval. Items at the top of the list should appear before items beneath it. Note that not all information listed below will apply to every air handler. Note also that the actual condition (temperature, pressure, etc.) appears in the summary before the set point for that condition. Multiple summary screens may be necessary for certain buildings due to their size. Clicking on the air handler ID will bring up the screen graphic for that air handler.

Because of space limitations, the contractor shall use judgment to determine which information to show on the summary screen but the order in which the information is listed in the summary table shall be in accordance with the listing below.

Supply Air Fan Status (colored circles) Air handler ID (AHU-1, AHU-2, etc.)

HOA Status Freeze Stat Status Smoke Sensor Status CO2 Concentration Supply Fan Command Supply Air Temperature Supply air Temperature Set Point Space Air Temperature Space Air Temperature Set Point Return Air Fan Command Return Air Fan Status

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 8 2/19/2013

Return Air Temperature Return Air Temperature Set Point Static Pressure Static Pressure Set Point Dual Temperature Valve Position Chilled Water Valve Position Hot Water Valve Position Filter Status

Figure 2. Example Building Summary Screen Graphic

9.0 Occupancy Schedules

A separate occupancy schedule shall be programmed for each air handler in a building (unless otherwise directed by the IJO Project Coordinator). A button shall be programmed in the upper right corner of the air handler screen graphic that will take the operator to the schedule input screen. The text shall be black on a white background with a black border as shown below. The rollover color for the background shall be cyan (Tridium color code #ff00ffff).

The occupancy schedules shall be programmed in accordance with the default occupancy schedule as listed in Attachment C to this standard unless otherwise directed in writing from the IJO Project Coordinator.

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 9 2/19/2013

10.0 Schedule Status

The occupancy schedule status of the air handler will be shown on the screen graphic for the air handler in the upper right corner of the screen, just below the “Air Handler Occupancy Schedule” button. The text shall be labeled “Occupancy Status”. The schedule options text (“Occupied” or Unoccupied”) shall be displayed either adjacent to or directly beneath the “Occupancy Status” as shown in Figure 1.

11.0 Outside Air Temperature

The outside air temperature shall be displayed in the upper left corner of the screen graphic. The text shall be “Outside Air Temp. The temperature value shall be black text on a white background with a black border.

12.0 Screen Graphic Text Descriptions

In general, abbreviations should not be used on the screen graphics. Where because of space limitations a word must be abbreviated the abbreviation must be in accordance with the approved abbreviation list. All text descriptions shall be consistent (avoid using synonyms) and in accordance with the approved list. A copy of the approved screen graphics abbreviations list is provided in Attachment D.

13.0 Air Handler Status and Controls

The air handler screen graphics should be programmed and displayed similar to the examples shown in Figure 1 for the supply air fan and return air fan.

13.1 Fan Command

The fan command text will be either “ON” or “OFF”. If the fan command is different from the fan status, the Fan Command field will be in alarm (black text with red background). If not in alarm the fan command field will be black text with a white background.

13.2 Fan Status

The fan status is displayed graphically with the rotating fan wheel and the fan discharge air movement. When the fan status is off the graphic will indicate no fan movement.

13.3 Fan Override Status

The fan can be overridden to either ON or OFF. Therefore the override status will be either:

True – indicating that the fan is in override (ON or OFF) or

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 10 2/19/2013

False – indicating that the fan is not in override (ON or OFF).

When the fan is in Override the background color will be burnt orange as shown for the return air fan in Figure 1. Right clicking on the fan mode status field will bring up a pop-up window with the standard NiagaraAX override options.

14.0 Pump Status and Controls

All pump screen graphics should be programmed and displayed similar to an air handler (fan) with the following three fields:

Pump Command

Pump Override

Pump HOA Status

14.1 Pump Command

The pump command will be either “ON” or “OFF”. If the pump command is different from the pump status, the Pump Command field will be in alarm (black text with red background). If not in alarm the fan command field will be black text with a white background.

14.2 Pump Status

The pump status is displayed graphically with the rotating pump impeller. When the pump status is off the graphic will indicate no pump movement.

14.3 Pump Override

The pump can be overridden to either ON or OFF. Therefore the override status will be either:

True – indicating that the pump is in override or

False – indicating that the pump is not in override.

When the pump is in Override the background color will be burnt orange as shown for the return air fan in Figure 1. Right clicking on the pump mode status field will bring up a pop-up window with the standard NiagaraAX override options.

15.0 UMCS Operator Override Capabilities

The screen graphics will be programmed to allow the operator to override certain operating parameters. For those operating parameters where the operator can access and override, the cell

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 11 2/19/2013 background color will change to cyan (Tridium color code #ff00ffff) when the mouse pointer scrolls over the cell. Once an override value is entered for the setpoint the background color shall change to a burnt orange with black text and a black border. Those parameters that the operators may override are listed below.

1. Occupancy Schedule

2. Dampers (Outside Air, Return Air, Exhaust/Relief, Mixed Air, Bypass/Face, Zone Hot Deck/Cold Deck, Zone)

3. Damper Operating Mode (Economizer, Minimum Outside Air)

4. Supply Air Temperature Set Points

5. Return Air Temperature Set Points

6. Space Air Temperature Set Points

7. Zone Space Temperature Set Points

8. VAV Space Temperature Set Points

9. Global Zone Space Temperature Set Points

10. Global VAV Space Temperature Set Points

11. Hot Deck Temperature Set Points

12. Cold Deck Temperature Set Points

13. Boiler/Chiller Enable Set Points

14. Dual Temp Heating Set Points

15. Hot Water Return Set Points

16. Static Pressure Set Points

17. Economizer Set Points

18. Summer/Winter Change Over

19. Outside Air Flow Set Points

20. DX unit

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 12 2/19/2013

21. Chiller System Enable Override

22. Boiler System Enable Override

23. Valves (Dual Temp, Cooling, Heating, Preheat, Reheat, Hot Deck/Cold Deck, Loop Bypass, Loop, Chiller/Boiler Flow Valves)

24. Fans (Supply, Exhaust, Return)

25. Supply/Return Fan VFD Commands

26. Domestic Hot Water Boiler Commands

27. Chiller Commands

28. Boiler Commands

29. Fan Overrides/Damper Overrides

30. Steam Boiler Commands

31. VFD/VSD Speed Commands

32. Pumps (Chilled Water, Hot Water, Dual Temperature, Domestic Hot Water, Booster, Runaround Pump)

33. Schedules (Building, Air Handler Unit, School Crossing Lights, Field Lights)

34. School Crossing Lights

35. Field Lights

36. Fan Mode/Air Handler Mode

37. Air Handler Schedule Mode (Building/AHU)

38. VAV (Min, Max, Fan Flow Set Points for Heating/Cooling)

16.0 Alarms

16.1 Summary Screen - Supply Air Fan Status Alarm

The Building Summary Screen will indicate when an air handler is in alarm. This alarm will be indicated when the fan command is different from the fan status and will be shown as a red circle in front of the AHU. See section 7.0.

16.2 Summary Screen – Sensor Alarms

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 13 2/19/2013

The alarm is indicated for that temperature sensor on the screen graphic (black text on red background). Other colors shall also be used to indicate status conditions of the temperature sensor as provided for in Section 2.4 of this standard. These point status conditions include disabled, fault, down, stale, and null. Similar alarms and status conditions of all sensors (temperature, pressure, humidity, CO2, etc) shall be provided on the screen graphics.

Alarms shall be provided for control loops in accordance with the following criteria unless otherwise directed by the sequence of operations or IJO Project Coordinator:

Temperature: Greater than +/- 3.0°F from setpoint.

Air pressure: Greater than +/- 0.30 iwc from setpoint

Water pressure: Greater than +/- 5.0 psi from setpoint

Humidity: Greater than +/- 10% RH from setpoint

16.3 Summary Screen Filter Alarm

The filter status will be shown on the graphics. The text label for the filter status shall be “Filter Status”. The text for the filter status will be either “Clean” or “Dirty”. An example (non-alarm) filter status is shown in Figure 1.

Clean – Black text, white background with black border.

Alarm – Black text, red background, black border.

16.4 Freeze Stat Alarm

The freeze stat will be shown on the graphics. The text label for this alarm shall be “Freeze Stat”. The text for the freeze stat status will be either “Normal” or “Alarm”. An example (non-alarm) freeze stat is shown in Figure 1.

Normal – Black text, white background with black border.

Alarm – Black text, red background, black border.

16.5 Smoke Sensor Alarm

The smoke sensor will be shown on the graphics similar to a freeze stat. The text label for this alarm shall be “Smoke Sensor”. The text for the smoke sensor status will be either “Normal” or “Alarm”.

Normal – Black text, white background with black border.

Alarm – Black text, red background, black border.

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 14 2/19/2013

16.6 Detail Mechanical Screen Alarms (Air handlers, Chillers, Boilers) Similar alarms and point status information shall be provided on the detail mechanical screens for the air handlers, pumps, boilers, chillers, VAVs, etc. as was described for the Building Summary Screen graphic in Section 17.2.

17.0 VAV Data

The following information shall be provided on the screen graphic for each VAV. An example VAV summary screen graphic is shown in Figure 2.

Space Temperature

Space Temperature Set point

Supply Air Temp (from air handler)

Flow Set point

Actual Flow

Flow Minimum

Flow Maximum

Damper % Open

Reheat

Figure 3. Example VAV Summary

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 15 2/19/2013

18.0 Freeze Protection

All buildings integrated into the EMCS shall be programmed to prevent the building plumbing from freezing. Freeze protection shall be accomplished by the DDC using the unoccupied night setbacks preprogrammed functions in the control system. This function will turn on the air handler and maintain the space temperature to the night setback temperature setpoint which shall be no less than 55°F.

The screen graphics shall be configured to provide indication to the UMCS operator when the air handler is in the freeze protection mode. When in the freeze protection mode the screen graphics shall display the unoccupied night setback temperature set point.

19.0 Point Naming and Numbering Convention

All points that are tied into the NiagaraAX control system shall be in accordance with the Fort Benning Niagara AX Point Naming Convention. A listing of the point names, abbreviations and facets for the points is provided in Attachment E. The point naming convention shall be as listed below:

Building Number-JACE Number-Point Name-Point Number

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 16 2/19/2013

XXXXX-XX-xxxxxx-XXX

Point Number – (3 digits) – XXX

Point Name (variable alpha numeric string) – in accordance with the point names listed in Attachment E.

JACE Number (2 digits) – XX

Building number (5 digits) – XXXXX

An example point name/number would be for JACE 2 in Building 4, AHU-2.

00004-02-AHU-002

An example point name/number for the return air temperature for AHU-1 in building 5500 (note there is only one JACE in this building).

05500-01-RAT-001

20.0 Drawings and Documentation

The building summary screen graphic shall have a button in the header titled “As Built” that is programmed to load a PDF file of the building control schematics. The PDFs will eventually be stored on the NiagaraAX server but until this server is installed and operational, the as-built drawings will be stored on the Niagara R2 server.

21.0 Floor Plans

Floor plans shall be developed for each building that allows the EMCS operator to view pictorially the building floor plan. The floor plan shall be appropriate to the type building and building function. Links between the room and it’s associated air handler or VAV shall be configured into the floor plan graphic. The floor plan shall clearly depict the following information:

Room numbers or names Thermostat locations Air handler locations Mechanical rooms

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 17 2/19/2013

Where the building is zone controlled, the floor plan shall indicate by colors, each zone. This includes using colors to different the zones controlled by each air handler and/or by each VAV.

The intent of this requirement is to allow the operator to identify on the floor plan the location of the temperature problem and then to be able to click on the floor plan affected area which would then be linked from the floor plan graphic web page to the related VAV or AHU screen graphic web pages. An example floor plan showing the building 1680 layout along with names, room numbers, and colors representing different VAV zones is shown below. The floor plan graphic shall also show the location of all space temperature sensors (thermostats) along with the temperature being measured by the sensor.

Figure 4. Example Floor Plan Screen Graphics

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 18 2/19/2013

Note that the floor plan screen shall have the same headers and buttons as all other screens.

22.0 Photocell Operated Lights

Buildings that are equipped with light circuits that can be controlled from the DDC and that have local light control photocells shall have the following information displayed on the screen graphics:

When the lights are directed to be on from the DDC the screen graphic shall show

“ON”.

When the lights are directed to be off from the DDC the screen graphic shall show

“OFF”

When the lights are controlled from the local photo cell the screen graphic shall show “PHOTOCELL”. Each light circuit shall be identified on the screen graphic. The yellow shown in the lighting control column indicates that the operator has override capability for these fields.

A burnt orange color indicates the light circuits that are in override. The status of the photocell (night or day shall also be shown on the light control screen graphic. The following is an example of how the screen graphic for light controls should be designed:

Revision 0 February 1, 2013

Fort Benning Niagara AX Graphics Standards - Rev 0_3DF3B592.doc 19 2/19/2013

Figure 5. Example Building Photocell Lights Screen

Note that the lighting control screen shall have the same headers and buttons as all other screens.

A-1

Attachment A Acronyms and Abbreviations

A/E architect/engineer AFB Air Force Base ANSI American National Standards Institute ASC Application Specific Controller BAS Building Automation System BPOC Building Point Of Connection BRAC Base Realignment and Closure CEERD U.S. Army Corps of Engineers, Engineer Research and Development Center CERL Construction Engineering Research Laboratory CO Contracting Officer COE Chief of Engineers COL Colonel DDC Direct Digital Control DHCP Dynamic Host Configuration Protocol DIACAP Department of Defense Information Assurance Certification and Accreditation Process

DITSCAP DoD Information Technology Security Certification and Accreditation Process DOIM Directorate of Information Management DPW Directorate of Public Works DX Directory of Expertise ECIP Energy Conservation Investment Program EIA Electronic Industries Alliance EMCS Energy Management Control System ERDC Engineer Research and Development Center ERDC-CERL Engineer Research and Development Center, Construction Engineering Research

Laboratory ESPC Energy Savings Performance Contract FAQ Frequently Asked Questions (FAQs) FMD Facilities Maintenance Division GPPC General Purpose Programmable Controller (GPPC) GUI graphical user interface HNC Huntsville Center HQ headquarters HQ-IMCOM Headquarters, Installation Management Command HTML hypertext markup language HVAC heating, ventilating, and air conditioning I/O input/output

IANA Internet Assigned Numbers Authority

A-2

IATO Interim Authority To Operate (IATO) ID/IQ indefinite delivery indefinite quantity IDC Indefinite Delivery Contract IDG Installation Design Guide IL Illinois IM instant messaging IP Internet protocol IT Information Technology JCI Johnson Controls, Inc.

JOC Job Order Contract LAN Local Area Network LCS LONWORKS® Control Station LDP local display panel LNS LONWORKS® Network Services MCX Mandatory Center of Expertise MILCON Military Construction MIPR Military Interdepartmental Purchase Request MOU memorandum of understanding MS Microsoft®

NC North Carolina NCT Network Configuration Tool NTP Notice To Proceed OI operator interface OMA Operations and Maintenance, Army OMD Operations Maintenance Division OSI Open Systems Interconnection OWS Operator WorkStation PC personal computer PDA personal digital assistant PDF Portable Document Format POC point of contact

PROSPECT Proponent Sponsored Engineer Corps Training PVT Performance Verification Test QC quality control QV Quality Verification RFP request for proposal SAS Savannah District SI Systeme Internationale (the “Metric System”) SNMP Simple Network Management Protocol

SNVT Standard Network Variable Type SOW statement of work TCP Transmission Control Protocol

A-3

TP/FT twisted-pair/free topology TR Technical Report UDP User Datagram Protocol UESC Utility Energy Services Contract UFGS Unified Facilities Guide Specification UMCS Utility Monitoring and Control System URL Universal Resource Locator USACE U.S. Army Corps of Engineers VLAN Virtual Local Area Network VPN Virtual Private Network WWW World Wide Web XIF eXternal Interface File XML Extensible Markup Language

A-4

B-1

Attachment B Glossary of Terms from UFC 3-401-01

(November 19, 2008)

10Base-T 100Base-T 100Base-FX 1000Base-T 1000Base-SX 1000Base-LX 10GBase-T

Ethernet media and communication speeds. The number is communication speed in Megabits per second (Mbps) or Gigabits per second (Gbps). “T” is twisted pair wire usually Cat-5 or better), while “FX”, “SX”, and “LX” are fiber optic cable. Note that 10 Gigabit Ethernet is (as of 2006) an IEEE standard and 100 Gigabit Ethernet is in development.

AGC

Application Generic Controller. A controller that comes from the factory with a limited built-in application. It is programmed for the application (VAV box, fan coil, etc.). It can be programmed through an LNS plug-in. It can be thought of as a cross between an ASC and GPPC. These controllers should be certified by Lon Mark. An AGC has a fixed program ID.

ASC

Application Specific Controller. A controller that has a built-in, fixed program to execute a sequence for a specific hardware system, e.g. a VAV box controller. An ASC has a fixed program ID.

BPOC

The Building Point of Connection (BPOC) is the point of connection between the UMCS network backbone (an IP network) and the building control network backbone. The hardware at this location that provides the connection is referred to as the BPOC Hardware. In general, the term "BPOC Location" means the place where this connection occurs, and "BPOC Hardware" means the device that provides the connection. Sometimes the term "BPOC" is used to mean either and its actual meaning (i.e. location or hardware) is determined by the context in which it is used.

Closed

The opposite of Open. A standard/protocol/specification where important details of its implementation are not available to all interested parties. Closed standards are closely controlled by the developing party and implementation of devices based on them is generally limited to a small number of vendors.

Device A piece of hardware. See also 'Node'

DDC

Direct Digital Control, defined as control consisting of microprocessor based controls with the control logic performed by software.

DDE

Dynamic Data Exchange, an inter-process communication (IPC) system built into the Macintosh®, Microsoft® Windows®, and OS/2® operating systems. DDE enables two running applications to share the same data.

DHCP

Dynamic Host Configuration Protocol is a protocol for automatically assigning IP configuration information to clients from a central server.

B-2

FTP File Transfer Protocol is a common protocol used on the Internet for sending files.

Gateway

A device (usually a combination of software and hardware) that connects networks using different communication protocols so that information can be passed from devices on one network to the other.

Gateways perform protocol conversion to translate this information from one protocol to another.

GPPC

General Purpose Programmable Controller. A controller that can be programmed to run any (within hardware limits) sequence and can be set up as a controller for different hardware systems. Changes to the program result in a different Program ID.

GUI

Graphical User Interface. A program interface that takes advantage of the computer's graphics capabilities to make the program easier to use. A true GUI includes formats for representing text and graphics.

HMI Human-Machine Interface. The means by which an operator interacts with an automation system, often a GUI.

HTTP

HyperText Transfer Protocol, is the underlying protocol used by the World Wide Web. HTTP defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands.

Interoperability The ability to integrate products from multiple vendors into flexible, functional systems without the need to develop custom hardware, software, or tools.

Interoperable

This is closely related to Open standards and refers to the level of difficulty of integrating components (or systems) from multiple vendors into a single system. Interoperability needs to be considered from the perspective of hardware installation (will the parts physically fit and interconnect?), communications (do the devices “speak the same language”?), configuration and programming (is the same software tool used for different vendor components?), maintainability (do the components have similar maintenance procedures and requirements?), and operation (do the components have similar functionality/ sequences and utilize the same operator interface?).

Open standards enhances/encourages interoperability because it allows multiple vendors to utilize a common standard. A caveat: In many (if not all cases), when vendors use the term interoperable, they do not mean interchangeable (in the sense of swapping out a VAV box for an identical VAV box).

IP

Internet Protocol. IP is a protocol on the Internet and is concerned with addressing and routing of data packets from their origin to the destination. Many other protocols are used in the Internet (TCP, HTTP, etc), but IP is the key protocol the others run on top of.

LAN Local Area Network, is a network for transferring data between computers or other digital devices.

B-3

LNS®

LonWorks Network Service, is the database architecture that resides on the computer attached to the LonWorks Network that is used to install and manage the Network. LNS is a database that can be accessed by any LNS-based Network Configuration Tool and by multiple users simultaneously.

LON Local Operating Network. Also used as a shorthand reference to the term LonWorks.

LonTalk® A networking protocol developed by Echelon Corporation and recognized by ANSI/CEA as ANSI/CEA-709.1-B. LonTalk implements layers 1-6 of the OSI reference model.

LonWorks® A networking platform (created by Echelon Corporation) that provides solutions to numerous problems of designing, building, installing, and maintaining control networks.

LonWorks Router A piece of equipment that allows ANSI/CEA-709.1-B communication and routing of network variables over an ANSI/CEA-709.1-B network. See “Router”.

LonWorks LON to IP Router

A piece of equipment that allows ANSI/CEA-709.1 communication and routing of network variables over IP. Also known as an ANSI/CEA-852 router. See “Router”.

Network A group of devices (computers, controllers, or other digital units) that are connected by communication facilities, such as twisted-pair cabling, coaxial cable, fiber-optic cable, or wireless means

Network Configuration Tool

Software used to perform network management functions such as adding, removing or relocating devices and establishing communication between devices.

Neuron® C A derivative of the C programming language specifically designed for developing applications for the Neuron chip.

Neuron® chip A chip that implements the ANSI/CEA-709.1 protocol. This chip is used by most LonWorks devices for communication on the network.

Many LonWorks devices also use this chip for control functionality.

Node

A device (such as a computer or a controller) on a network that is capable of communicating with other network devices via a networking protocol such as NSI/CEA-709.1.

Open system An Open system is characterized by the ability for any qualified third party entity to readily modify, operate, upgrade, and perform retrofits on the system.

OWS

Operator Work Station, a type of computer-based GUI. An OWS is designed for use by an operator whereas a technician or maintenance worker might have a different computer and GUI with a different “look and feel”.

Peer-to-Peer A type of network where each node has equivalent capabilities and responsibilities for network communication.

Plug-in Software used to configure an ASC that is run/executed from within a Network Configuration Tool.

B-4

Proprietary Privately owned and controlled. Proprietary is the opposite of public domain.

Proprietary – Government procurement

In Government procurement regulations, a proprietary product is one that requires sole source procurement.

Router A device that connects two or more LANs. Routers are devices that provide network-independent packet filtering and forwarding. They may also include bridge functionality.

SNMP Simple Network Management Protocol

SNVT

Standard Network Variable Type; Pronounced 'snivet'. A standard format type (maintained by LonMark International) used to define data information transmitted and received by the individual LonWorks nodes. The term SNVT is used in two ways. Technically it is the acronym for Standard Network Variable Type, and is sometimes used in this manner. However, it is often used to indicate the network variable itself (i.e. it can mean "a network variable of a standard network variable type"). In general, the intended meaning should be clear from the context.

SOAP

Simple Object Access Protocol: A lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined data types, and a convention for representing remote procedure calls and responses.

SQL

Structured query language, defined as a standardized query language for requesting information from a database. There is an ANSI standard for SQL

Standard, De-facto

De-Facto standards are ‘standards of fact’, that is, standards that have been adopted by an industry or a market. An example of a de-facto standard is Microsoft Word. While it has not been adopted by a recognized standards organization, its market dominance makes it the de-facto standard for word processing. Gray areas arise here over market share and industry recognition.

Standard, De-jurie

De-Jurie standards (literally, ‘standards of law’) are those that have been adopted and approved by some recognized standards organization, such as ASHRAE, IEEE, ASTM, ISO, etc. ANSI/CEA-

709.1 is an example of a de-jurie standard. Gray areas can arise here over what constitutes a standards body.

B-5

Standard, Proprietary

Proprietary standards are those that are owned and controlled by an organization not generally recognized as a 'legitimate' standards body (they are often owned by a for-profit organization). They frequently are considered to be, or to contain, intellectual property of value to the owning body. Proprietary standards may be Open, closed, or somewhere in between, though they tend to be more closed. The Microsoft Word document format (.doc files) is an example of a closed proprietary standard

Transceiver A component or circuit that enables a hardware device to communicate on a network.

VLAN

Virtual Local Area Network. A common means of keeping different networks separate while existing on the same basewide LAN. Most modern Ethernet switches support VLANs where the different ports on the switch are divided into separate logical groupings. Ports in the same group can communicate with each other, while ports in separate groups can’t. The ports in a common group form a VLAN within the larger physical network. A single physical network may support many distinct VLANs.

C-1

Attachment C Default Building Occupancy Schedule

(Per Mark Fincher – December 18, 2012)

The following occupancy schedules shall be programmed into the EMCS DDC unless otherwise directed by the building occupants.

Building Use Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Administrative 0730-1800 0730-1800 0730-1800 0730-1800 0730-1800 By Appointment By Appointment

DFAC 0600-2000 0600-2000 0600-2000 0600-2000 0600-2000 0600-2000 0600-2000

Rec Facilities 0530-2130 0530-2130 0530-2130 0530-2130 0530-2130 0530-2130 0530-2130

Ranges By Appointment By Appointment By Appointment By Appointment By Appointment By Appointment By Appointment

Barracks Heating

0600-1700 65°F

1700-0600 72°F

Cooling

0600-1700 80°F

1700-0600 74°F

Heating

0600-1700 65°F

1700-0600 72°F

Cooling

0600-1700 80°F

1700-0600 74°F

Heating

0600-1700 65°F

1700-0600 72°F

Cooling

0600-1700 80°F

1700-0600 74°F

Heating

0600-1700 65°F

1700-0600 72°F

Cooling

0600-1700 80°F

1700-0600 74°F

Heating

0600-1700 65°F

1700-0600 72°F

Cooling

0600-1700 80°F

1700-0600 74°F

Heating

0600-1700 65°F

1700-0600 72°F

Cooling

0600-1700 80°F

1700-0600 74°F

Heating

0600-1700 65°F

1700-0600 72°F

Cooling

0600-1700 80°F

1700-0600 74°F

Passenger Terminal By Appointment By Appointment By Appointment By Appointment By Appointment By Appointment By Appointment

2/19/2013D-1

Attachment D Screen Graphic Abbreviations

The following abbreviation convention should be used for all screen graphics where appropriate.

- Supply Air Temperature – SAT

- Supply Air Temperature Set Point – SAT SP

- Supply Air Flow - SAF

- Space Air Temperature – SPAT

- Space Air Temperature Set Point – SPAT SP

- Set Point – SP

- Occupancy Status – OS

- Air Handler Unit – AHU

- Outside Air – OA

- Outside Air Temperature – OAT

- Direct Expansion – DX

- Domestic Hot Water – DHW

- Boiler – BLR

- Hot Water – HW

- Hot Water Valve – HWV

- Chilled Water – CHW

- Chilled Water Valve – CHWV

- Fan Command – FAN CMD

- Fan Status – FAN STAT

- Fan Override – FAN OVRD

- Set Point Override – SP OVRD

- Freeze Protection – FREZ PROT

- Hot Water Supply Temperature – HWST

2/19/2013D-2

- Hot Water Return Temperature – HWRT

- Chilled Water Supply Temperature – CHWST

- Chilled Water Return Temperature – CHWRT

- Command – CMD

- Status – STS

- Fan Start/Stop Control Switch – FAN S/S

- Temperature – Temp

E- 1

Attachment E. Fort Benning NiagaraAX Point Naming Convention

Point Name Abbr Facets

Actual Cooling Setpnt ACSP units=˚F precision=1

Actual Htg Setpnt AHSP units=˚F precision=1

Air Handling Unit AHU units=null precision=0

Air Quality AirQ units=ppm,precision=2,min=0.0,max=5000.0

Air Quality Flag AirQStatus truetext=On falsetext=Off

Airflow AirFlw units=cfm precision=1

Airflow Setpoint AirSet units=cfm precision=1

Alarm Alm truetext=true falsetext=false

Auxillary Space Temp AuxSpaceT units=˚F precision=1

Auxillary Temp AuxTemp units=˚F precision=1

Auxillary Temp AuxT units=˚F precision=1

Average Temperature AvgT units=˚F precision=1

Average Zone Temperature AvgZnT units=˚F precision=1

Bearing Oil Return Temp (# if needed) BrngOilRT(#) units=˚F precision=1

Bearing Oil Supply Temp BrngOilST units=˚F precision=1

Bldg Bldg units=null precision=0

Bldg Diff Press BDP units=psi precision=1

Bldg Flow (#) BldgFlow (# if needed) units=gpm precision=1

Bldg Static Press BStcPr units=in/wc precision=2

Bldg Static Press Setpoint BldStatPrSp units=in/wc precision=2

Boiler Blr units=null precision=0

Boiler Alarm BlrAlm truetext=true falsetext=false

Boiler Command BlrCmd truetext=true falsetext=false

E- 2

Point Name Abbr Facets

Boiler Flame Fail BlrFlameFail truetext=true falsetext=false

Boiler Flow Switch BlrFlowStat truetext=true falsetext=false

Boiler Modulating Valve BlrVlv units=% precision=0

Boiler Plant Enable BlrPlantEna truetext=true falsetext=false

Boiler Pump Status BlrPStatus truetext=true falsetext=false

Boiler Status BlrStatus truetext=true falsetext=false

Boiler Supply Temp BlrST units=˚F precision=1

Boiler Valve BlrVlv truetext=true falsetext=false

Boiler Water Temp BlrWT units=˚F precision=1

Boilers Enabled Status BlrPlantStat truetext=true falsetext=false

Booster Pump Speed BostrPO

Booster Pump Status BostrPStatus

Box Supply Temp DAT units=˚F precision=1

Building Differential Pressure BDP

Building Differential Pressure High Limit BDPHL

Building Differential Pressure Low Limit BDPLL

Building Pump # (number) Status BP#Status truetext=true falsetext=false

Building Pump Flow Switch BFlwStat truetext=true falsetext=false

Building Water Return Temp BldgRT units=˚F precision=1

Building Water Supply Temp BldgST units=˚F precision=1

Bypass Valve Command BypVlv truetext=true falsetext=false; units=% precision=0

Calculated Cooling Setpoint ClgStPnt units=˚F precision=1

Charge GPM ChrgFlow

E- 3

Point Name Abbr Facets

Chemical Treatment # Alarm ChemTrt#Alm

Chilled Water CHW

Chilled Water Bypass Valve CHWBypVlv units=% precision=0

Chilled Water Bypass Valve Output CHWBypVlvO units=% precision=0

Chilled Water Differential Pressure CHWDP units=psi precision=0

Chilled Water Differential Pressure Average CHWDPAvg units=psi precision=0

Chilled Water Differential Pressure Setpoint CHWDPSetP units=psi precision=0

Chilled Water Pump # VFD CHWP#VFDO units=% precision=0

Chilled Water Pump Cmd CHWPCmd truetext=true falsetext=false

Chilled Water Pump Status CHWPStat truetext=true falsetext=false

Chilled Water Return Flow CHWRFl units=gal/min precision=1

Chilled Water Return Temp CHWRT units=˚F precision=1

Chilled Water Setpnt CHWSP units=˚F precision=1

Chilled Water Setpnt (Leaving) LvCHWSetP units=˚F precision=1

Chilled Water Supply Flow CHWSFl units=gal/min precision=1

Chilled Water Supply Temp CHWST units=˚F precision=1

Chilled Water Valve CHWVlv units=% precision=0

Chiller CH truetext=true falsetext=false

Chiller # Chilled Water Differential Pressure CH#CHWDP units=psi precision=0

Chiller # Chilled Water Differential Pressure Switch CH#CHWDPSw truetext=true falsetext=false

Chiller Alarm CHAlm truetext=true falsetext=false

Chiller Amps CHAmps units=ampere (A) precision=2

E- 4

Point Name Abbr Facets

Chiller Cmd CHCmd truetext=true falsetext=false

Chiller Cond Press CHCndPr units=psi precision=1

Chiller Enable CHEna truetext=true falsetext=false

Chiller KW CHKW units=kW precision=1

Chiller Plant Enable CHPlantEna truetext=true falsetext=false

Chiller Setpoint Reset CHWStPntRst units=null precision=0

Chiller Status CHStatus truetext=true falsetext=false

Chiller Volts CHVolts units=volt (V) precision=2

CO Level COLvl units=ppm precision=1

CO2 Alarm CO2Alm units=ppm precision=1

CO2 Level CO2Lvl units=ppm precision=1

Cold Deck ColdDeck

Cold Deck Humidity ColdDeckHum units=%RH precision=0

Cold Deck Temp ColdDeckT units=˚F precision=1

Coldest Zone Temp ColdestZnT units=˚F precision=1

Common Setpoint (Base) CmnStPnt units=null precision=0

Communication Lost Alarm CommLostAlm truetext = Comm Lost falsetext=Comm Normal

Communication Lost Alarm CommAlm truetext=Comm Lost falsetext=Comm…