SECTION 25 0000 - Stanford Universityweb.stanford.edu/group/lbre_apps_forms/maps/fdg/fdg_documents_pdf/25_12_23_Client...C. Stanford University Niagara 4 Standards. Latest version

Stanford University – Facilities Design Guidelines

February 2019 Page 1 of 33 2020 FDG Section 25 12 23

SECTION 25 12 23

CLIENT-SERVER INFORMATION / DATABASE INTEGRATION

PART 1 - GENERAL

1.1 SUMMARY

A. Section includes the database generation and integration for the DDC system.

B. This section defines the specific Niagara database generation and integration requirements for the equipment or devices defined in project Scope of Work. This can include new DDC hardware and devices furnished by Controls Contractor; vendor- specific third-party equipment furnished by other Contractors; and existing controls systems or devices.

C. Related Sections: 1. Stanford FDG 01810 Commissioning 2. 25 00 00 Integrated Automation 3. 25 11 19 Building Controls Systems Server 4. 25 12 19 Integration Protocols 5. 25 15 23 Graphics

1.2 REFERENCES

A. Refer to 25 00 00 Integrated Automation

B. Object Naming and Tags Spreadsheet. Latest version furnished to Contractor by Stanford FAC.

C. Stanford University Niagara 4 Standards. Latest version furnished to Contractor by Stanford FAC.

1.3 DEFINITIONS

A. Refer to 25 06 11 Integrated Automation Definitions

1.4 SYSTEM DESCRIPTION

A. The integration of the systems as specified or as shown on construction documents throughout the facility using protocols specified in section 25 1219.

B. Remote read/write capabilities of Integrated Automated Systems using open and industry standard protocols.

C. Scope includes but not limited to: 1. Data collection 2. Database generation. 3. Graphics generation. 4. Scheduling generation. 5. Trending and storage of all points 6. Alarm generation and management. 7. Reports generation 8. Coordination of integration activities.

1.5 SUBMITTALS

A. Refer to 25 0000 Integrated Automation



B. All programming and configuration, including graphics, directory structure, Tagging, Hierarchies Templates and point naming in Building Control System Server, Building Level Controllers, Local Control Units and any additional devices included in the project scope of work, must be submitted for approval of FAC before Contractor may proceed with work. Contractor assumes all responsibility for required submissions. Failure to submit any required submittal does not alleviate Contractor’s responsibility to implement Owner’s corrections, at no additional cost to Owner and with no slippage of installation schedule.

C. All modifications to Owner-furnished Stations, programming code and Stanford Standard graphics must be described in writing and submitted for approval of FAC before Contractor may proceed with work. Failure to submit any required submittal does not alleviate Contractor’s responsibility to implement Owner’s corrections, at no additional cost to Owner and with no slippage of installation schedule.

D. All Contractor modifications to Owner-furnished Stations, programming code and Stanford Standard graphics that are not described in writing and submitted for approval of FAC shall be corrected by the Contractor to the satisfaction of Owner, at no additional cost to Owner and with no slippage of installation schedule.

1.6 QUALITY ASSURANCE

A. Refer to 25 0000 Integrated Automation

B. Each copy of Tridium Niagara software shall include a 5 year Niagara Software Maintenance Agreement.

PART 2 - PRODUCTS

2.1 NOT USED.

PART 3 - EXECUTION

3.1 Use of Owner-furnished Stations, programming code and Stanford Standard graphics.

A. To ensure consistency of programming, consistency of database structure, and consistency of “Look and Feel” of User Interface, Stanford University FAC provides Niagara 4 template stations for new or AX-upgraded Niagara installations. These station templates are named BuildingWS.ntpl and BuildingJace.ntpl for new N4 projects and for projects that migrate existing AX sites to N4. Each include several preconfigured components key to a successful implementation of Stanford N4 Standards, namely; a Stanford Kerberos Authentication Scheme, Stanford Categories, Stanford Standard Prototypes and Roles, and a Stanford Tag Dictionary. Preconfigured objects also include Data Modeling examples in the form of Hierarchies typically used for a Stanford site, sample graphics for common equipment types, and a sample navigation scheme with core site pages, Alarm Classes, and representative alarm messages with correct Bformatting; one Modbus JACE station with representative Modbus points configured, and representative gfx code for each type of Distech controller.

B. The term “representative’ shall mean it is understood that the Stations, graphics and gfx code are copied from a project that is very close to, but may not exactly match, the requirements of this project. Upon receipt of Stations, graphics and gfx code, Contractor shall have 30 business days to thoroughly review and study the furnished Stations, graphics, Niagara wiresheets and gfx code, and to list, in writing, any reason why the furnished material cannot be adapted to this project. For each reason, Contractor shall include a proposed solution that is consistent with Stanford Standards and will not adversely impact the project schedule. Owner shall be the final judge of acceptance of proposed alternative programming solutions.



C. After 30 business days to thoroughly review and study the furnished Stations, graphics, wiresheets and gfx code, Contractor shall inherit full responsibility for the functionality and performance of the furnished Stations, graphics, wiresheets and gfx code.

D. Contractor is completely responsible for successfully passing all Functional Performance Testing (FPT) prior to project close out. The fact that Contractor is using a code template that was furnished to them, or the fact that code passed FPT at the beginning of the project, will not be considered acceptable reasons for failure to pass any commissioning FPT at project close out.

3.2 Compliance to Owner’s Computing and Security policies.

A. The Contractor shall at all times fully comply with all Stanford University Computer Policies.

B. Be forewarned that Stanford University Computer Policies are constantly evolving and may change to be increasingly restrictive during the execution of this contract. The Contractor shall at all times fully comply with all Stanford University Computer Policies – immediately as the policies become effective.

C. Owner does not guarantee that Contractor will have remote (off-campus) access to the controls system.

D. Violation of Stanford University Computer Policies may result in revocation of User access to the Stanford University Computer Network and/or computing equipment physically removed from the Stanford University Computer Network.

E. Examples of controls system security policies include: 1. Minimum password length. 2. User access credentials cannot be shared. Each user accessing system must have unique

credentials. 3. User credentials may not be transmitted by email or text message. User credentials inside a

password-protected zip file may be transmitted via email. 4. Deleting, restricting access to, or modifying operating system or control system log files is not

permitted. 5. Contractor passwords shall be unique to Stanford site – passwords used at any other site are

not acceptable. Ubiquitous “Branch” passwords are not acceptable. 6. Contractor to apply all software updates and security patches immediately (within 72 hours) as

they become available. 7. Owner shall, at all times, have at least 1 Windows Operating System administrator account on

all servers, Niagara Super User Station accounts for all JACEs and Supervisor Stations, all Niagara Pass Phrases and credentials for access to all Platforms.

8. Any and all required IDs and passwords, including hardware locks for access to any component or software program shall be immediately provided to the Owner upon request, at no additional cost to Owner.

3.3 SYSTEM ACCESS

A. Operator specific password access protection shall be provided for each application to allow the administrator to limit access to point control, display and data base manipulation capabilities as deemed appropriate for each user, based upon an assigned password. There shall be 6 access levels as defined below. 1. Super User – No restriction. Can set or override adjustable setpoints on graphics. 2. Administrator – Full WebUI and Workbench access to Station except to files that can

potentially corrupt database. Can set or override adjustable setpoints on graphics. Can set passwords and add users.

3. Integrator - WebUI and Workbench access to Station. Same access level as Administrator except cannot set passwords and add users. Can set or override adjustable setpoints on graphics. Can change own user name, password and email address



4. Programmer – WebUI and Workbench access to Station. Same access level as Administrator except cannot set passwords and add users. Can set or override adjustable setpoints on graphics. Can change own user name, password and email address.

5. Operator – WebUi access only. View all graphics and override points only, no set point access, can acknowledge alarms. Can override adjustable setpoints on graphics. Can change own user name, password and email address.

6. Read Only – Read only WebUI access. Can change own user name, password and email address.

7. Scheduler – Read only WebUI access with ability to modify equipment schedules as required. Can change own user name, password and email address.

8. Owner will furnish a written matrix of Categories, Permissions and Roles that must be followed exactly.

9. As directed by Owner, Contractor shall remove all User Accounts created by Contractor.

3.4 DATA COLLECTION:

A. Provide mapping of points from various control systems. Provide the ability to read and display any value of any used property of any object from any networked device including properties available and supported optional properties, as well as proprietary extensions.

B. Unless otherwise specified trend points simultaneously no longer than every 15 minutes.

C. Timestamp all data.

D. Normalize data points shown in contract documents for ease of database management, graphic displays, readability, and simple identification.

3.5 DATABASE GENERATION:

A. Develop database of data objects, time stamps, events, alarms, and transactions.

B. Archive all data points, graphics, reports, alarms, trends, events, and transactions. 1. Store a minimum of 2 years of data on Building Control System Server. 2. Schedule and synchronize trend point data collected on the building level controller to be

archived to the building control systems server to allow enough capacity in the building level controller to hold data if first sync fails.

C. Develop databases including: 1. Applications 2. Configuration 3. Trending of historical Data 4. Event (operator actions / alarming etc) storage

D. Provide an electronic copy of the installed/commissioned database in the Building Control Systems Server, every building level controller; and every local control unit for emergency recovery.

3.6 Collection and Analysis of Historical Data

A. Provide trending capabilities that allow the user to easily monitor and preserve records of system activity over an extended period of time. Any system point may be trended automatically at time-based intervals or change of value, both of which shall be user-definable. Trend data may be stored on hard disk for future diagnostics and reporting. Additionally, trend data may be archived to network drives or removable disk media for future retrieval.

B. Trend data reports shall be provided to allow the user to view all trended point data. Reports may be customized to include individual points or predefined groups of at least six points. Provide additional functionality to allow predefined groups of trended points to be easily transferred on-line



to Microsoft Excel. Contractor shall provide up to four custom designed spreadsheet reports for use by Owner to track energy usage and cost, equipment run times, equipment efficiency, and/or building environmental conditions. Contractor shall provide setup of up to four custom reports including creation of data format templates for monthly or weekly reports.

C. Provide additional functionality that allows the user to view real-time trend data on trend graph displays. Ten points may be graphed, regardless of whether they have been predefined for trending. The dynamic graphs shall continuously update point values. At any time the user may redefine sampling times or range scales for any point. In addition, the user may pause the graph and take "snapshots" of screens to be stored on the workstation disk for future recall and analysis. Exact point values may be viewed and the graphs may be printed.

D. Histories shall utilize Hierarchies to facilitate easy and logical navigation to histories in History Viewer,. Histories shall no longer utilize obsolete History Groups to facilitate navigation to histories .

E. On each History Extension, the History Name shall be correctly bFormatted to automatically prepend the Point Display Name, with JACE Name and Controller Name, in the format: JACEName_ControllerNAme_PointName.

F. Contractor shall demonstrate History Hierarchy navigation structure to Owner’s Representative for written approval prior to creating History Extensions.

G. All trending shall reside in the Station of the Building Level Controller that directly supervises the controllers that are on a LON network connected to that Building Level Controller. Trends stored in the JACE shall be archived in the Supervisor Station a maximum of every 2 hours.

3.7 DATABASE BACKUP

A. Provide automatic weekly backup of all building level controllers and local control unit databases to a location on the Building Control Systems Server. Backups will be limited to a maximum of 52 backups, at which time newest backup shall overwrite oldest backup. Each backup shall be written with a file name that includes a date code for date of backup or a unique folder with a folder name that includes a date code and shall not overwrite or append previous backup files. Owner shall have the ability to restore the database in the building level controller or local control unit using a backup from a “known good” database at any previous week necessary.

B. Owner will automate the backup of the building control system server to the campus master DDC server.

3.8 POINTS LIST

A. Adjustable points fall into 1 of 3 categories: 1. Points adjustable from the Supervisor Station using Niagara Workbench (WBS-Adj.).

a. WBS-Adj. point shall be a dedicated Niagara Numeric Writable Point. Hard coding the value into a calculation block is not acceptable.

b. The Niagara Numeric Writable Point shall be the same object name for every instance of same WBS-Adj. point to facilitate batch editing of WBS-Adj. points.

c. WBS-Adj. point shall be adjustable from Workbench on the Supervisor Station by anyone with Programmer or higher level of access.

2. Points adjustable from a JACE using Niagara Workbench (WBJ-Adj.). a. WBJ-Adj. point shall be a dedicated Niagara Numeric Writable Point. Hard coding the

value into a calculation block is not acceptable. b. The Niagara Numeric Writable Point shall be the same object name for every instance of

same WBJ-Adj. point to facilitate batch editing of WBJ-Adj. points.



c. WBJ-Adj. point shall be adjustable from Workbench by anyone with Programmer or higher level of access.

3. Points adjustable from Graphic Page (GR-Adj.). a. GR-Adj. points shall be adjustable from Graphic Page. Adjustability shall be based on

operator’s access level.

B. Submit points list for Owner Approval, prior to database generation.

C. The VAV with Reheat Coil terminal unit controller shall monitor and trend the following points as specified in the table below. The VAV with Reheat Coil terminal unit graphic shall display points as specified in the table below. 1. Note: additional AHU points may be mapped via Modbus to be displayed on VAV graphic.

D. Contractor shall include any additional points required to meet specification section 25 1523 Graphics.

E. Contractor shall include any additional points required to meet specification section 25 3528 Control Sequences.



Point Hardware Points

Software Points

From DeltaV

Cx Trend (1)

Cont. Trend (2)

Show On Graphic

Adjustable

Zone Temperature AI × 15 min. ×

Zone Setpoint Adjustment AI × COV ×

Airflow AI × 15 min. ×

Discharge Air Temperature AI × 15 min. ×

Zone Damper Position AO × 15 min. × GR-Adj.

Reheat Valve Position AO × 15 min. × GR-Adj.

Zone Occupancy Override BI × COV × WBS-Adj.

Airflow Setpoint AV × 15 min. ×

Max Cooling Airflow AV × COV × GR-Adj.

Min Cooling Airflow AV × COV × GR-Adj.

Max Heating Airflow AV × COV × GR-Adj.

Min Heating Airflow AV × COV × GR-Adj.

Zone Setpoint AV × COV × GR-Adj.

Occupied Heating Setpoint AV ×

Occupied Cooling Setpoint AV ×

Standby Heating Setpoint AV ×

Standby Cooling Setpoint AV ×

Un-Occupied Heating Setpoint AV × WBS-Adj.

Un-Occupied Cooling Setpoint AV × WBS-Adj.

Effective Heating Setpoint AV × 15 min. ×

Effective Cooling Setpoint AV × 15 min. ×

Zone Criticality (Reset Weighting) AV × GR-Adj.

Occupancy Mode AV × 15 min. × GR-Adj.

Terminal Load (Heating/Cooling Demand) AV × 15 min. ×

Cooling Request AV × 15 min. ×

Cooling Request Hi & Lo Setpoints AV WBJ-Adj.

Reheat Valve Request AV × 15 min. ×

RH-V Request Hi & Lo Setpoints AV WBJ-Adj.

Damper Request AV × 15 min. ×

Damper Request Hi & Lo Setpoints AV WBJ-Adj.

Cooling Satisfied AV × 15 min. ×

Cooling Satisfied Hi & Lo Setpoints AV WBJ-Adj.

Reheat Valve Satisfied AV × 15 min. ×

RH-V Satisfied Hi & Lo Setpoints AV WBJ-Adj.




Software Points

From DeltaV

Cx Trend (1)

Cont. Trend (2)

Show On Graphic

Adjustable

Damper Satisfied AV × 15 min. ×

Damper Satisfied Hi & Lo Setpoints AV WBJ-Adj.

Box Size String WBS-Adj.

Box Type String WBS-Adj.

AHU SAT AV × × 15 min. ×

AHU SAT Setpoint × × 15 min. ×

AHU Occupancy Status AV × × 15 min. ×

AHU Name or Number × × 15 min. ×

AHU Duct Static Pressure AV × × 15 min. ×

AHU Duct Static Pressure Setpoint × × 15 min. ×

Outside CO2 AV × × 15 min. ×

Global Occupied Heating Offset AV ×

Global Occupied Cooling Offset AV ×

Global Standby Heating Offset AV ×

Global Standby Cooling Offset AV ×

Totals

AI – Analog Input; AO – Analog output; BI – Binary Input; BO – Binary output; AV – Analog Value; BV – Binary Value

(1) Cx Trend requirements: 5 minute interval, 1 month duration,

(2) Continuous Trend requirements: Either 15 minute interval or COV as specified above, 24 hour duration



G. The Cooling Only VAV terminal unit controller shall monitor and trend the following points as specified in the table below. The Cooling Only VAV terminal unit graphic shall display points as specified in the table below.

H. Contractor shall include any additional points required to meet specification section 25 1523 Graphics.

I. Contractor shall include any additional points required to meet specification section 25 3528 Control Sequences.




Software Points

From DeltaV

Cx Trend (1)

Cont. Trend (2)

Show On Graphic

Adjustable



Airflow AI × 15 min. ×


Zone Damper Position AO × 15 min. × GR-Adj.

Zone Occupancy Override BI × COV × WBS-Adj.

Airflow Setpoint AV × 15 min. ×

Max Cooling Airflow AV × COV × GR-Adj.

Min Cooling Airflow AV × COV × GR-Adj.

Zone Setpoint AV × COV × GR-Adj.

Occupied Heating Setpoint AV

Occupied Cooling Setpoint AV ×

Standby Heating Setpoint AV

Standby Cooling Setpoint AV ×

Un-Occupied Heating Setpoint AV WBS-Adj.

Un-Occupied Cooling Setpoint AV × WBS-Adj.



Zone Criticality (Reset Weighting) AV × GR-Adj.

Occupancy Mode AV × 15 min. × GR-Adj.

Terminal Load (Heating/Cooling Demand) AV × 15 min. ×

Cooling Request AV × 15 min. ×

Cooling Request Hi & Lo Setpoints AV WBJ-Adj.

Reheat Valve Request AV × 15 min. ×

RH-V Request Hi & Lo Setpoints AV WBJ-Adj.

Damper Request AV × 15 min. ×

Damper Request Hi & Lo Setpoints AV WBJ-Adj.

Cooling Satisfied AV × 15 min. ×

Cooling Satisfied Hi & Lo Setpoints AV WBJ-Adj.

Reheat Valve Satisfied AV × 15 min. ×

RH-V Satisfied Hi & Lo Setpoints AV WBJ-Adj.

Damper Satisfied AV × 15 min. ×

Damper Satisfied Hi & Lo Setpoints AV WBJ-Adj.

Box Size String WBS-Adj.




Software Points

From DeltaV

Cx Trend (1)

Cont. Trend (2)

Show On Graphic

Adjustable

Box Type String WBS-Adj.

AHU SAT AV × × 15 min. ×

AHU SAT Setpoint × × 15 min. ×

AHU Occupancy Status AV × × 15 min. ×

AHU Name or Number × × 15 min. ×

AHU Duct Static Pressure AV × × 15 min. ×

AHU Duct Static Pressure Setpoint × × 15 min. ×

Outside CO2 AV × × 15 min. ×

Global Occupied Heating Offset AV ×

Global Occupied Cooling Offset AV ×

Global Standby Heating Offset AV ×

Global Standby Cooling Offset AV ×

Totals






K. The Fan Coil Unit controller shall monitor and trend the following points as specified in the table below. The Fan Coil Unit graphic shall display points as specified in the table below.

L. Contractor shall include any additional points required to meet specification section 25 1523 Graphics.

M. Contractor shall include any additional points required to meet specification section 25 3528 Control Sequences.


Software Points

From DeltaV

Cx Trend (1)

Cont. Trend (2)

Show On Graphic

Adjustable




Valve Position AO × 15 min. × WBS-Adj.

Zone Override BI × COV × WBS-Adj.

Fan Status BI × COV ×

Fan Start/Stop BO × COV × WBS-Adj.

Zone Setpoint AV × COV × WBS-Adj.

Occupied Heating Setpoint AV × GR-Adj

Occupied Cooling Setpoint AV × GR-Adj

Standby Heating Setpoint AV × WBS-Adj

Standby Cooling Setpoint AV × WBS-Adj



Critical Zone AV × GR-Adj.

Occupied Mode BV × 15 min. × GR-Adj.

Terminal Load AV × 15 min. ×

Totals






O. The VAV Exhaust System controller shall monitor and trend the following points as specified in the table below. The VAV Exhaust System graphic shall display points as specified in the table below.

P. Contractor shall include any additional points required to meet specification section 25 1523 Graphics.

Q. Contractor shall include any additional points required to meet specification section 25 3528 Control Sequences.


Software Points

From Cx Cont. Trend

(2)

Show On

Graphic Adjustable

DeltaV Trend (1)

Exhaust duct pressure AI × 15 min. ×

Exhaust fan start stop DO × COV × GR-Adj.

Exhaust fan speed control AO × 15 min. × GR-Adj.

Exhaust fan run status DI × COV ×

Make-up air damper control AO × 15 min. × GR-Adj.

Exhaust pressure set point AV × COV × GR-Adj.






S. The VAV Air Handler controller shall monitor and trend the following points as specified in the table below. The VAV Air Handler graphic shall display points as specified in the table below.

T. Contractor shall include any additional points required to meet specification section 25 1523 Graphics.

U. Contractor shall include any additional points required to meet specification section 25 3528 Control Sequences.


Software Points

From Cx Cont. Trend

(2)

Show On

Graphic Adjustable

DeltaV Trend (1)

Return air temperature AI × 15 min. ×

Outside air temperature AI × 15 min. ×

Mixed air temperature AI × 15 min. ×

Supply air temperature AI × 15 min. ×

Supply duct static pressure AI × 15 min. ×

Building static pressure AI × 15 min. ×

Outside air damper Command AO × 15 min. × GR-Adj.

Return air damper command AO × 15 min. × GR-Adj.

Exhaust air damper Command AO × 15 min. × GR-Adj.

Supply fan start stop DO × COV × GR-Adj.

Return fan start stop DO × COV × GR-Adj.

Supply fan run status DI × COV ×

return fan run status DI × COV ×

Supply fan speed control AO × 15 min. × GR-Adj.

return fan speed control AO × 15 min. × GR-Adj.

HW coil control valve AO × 15 min. × GR-Adj.

CHW coil control valve AO × 15 min. × GR-Adj.

Supply air set point AV × 15 min. × GR-Adj.

Preheat set point AV × 15 min. × GR-Adj.

Duct static set point AV × 15 min. × GR-Adj.

Building static set point AV × 15 min. × GR-Adj.






3.9 OCCUPANCY/EQUIPMENT SCHEDULING AND OVERRIDES

A. Coordinate initial occupancy and equipment schedules requirements with owner.

B. Program initial occupancy and equipment schedules per owner request.

C. Install and configure Stanford custom 25Live driver to automatically control equipment serving 25Live spaces, as directed by Owner.

D. Occupancy and/or Equipment schedules may change during the course of this project. Contractor shall modify programing to meet any Occupancy and/or Equipment schedules revised by Owner, until project is accepted by Owner, at no additional cost to Owner.

E. Contractor accepts that programming the occupancy schedule of a Terminal Unit, may also require programming the occupancy schedule of other Terminal Units served by the same Air Handler, or other equipment schedules,

F. Schedules reside in the Building Level Controller(s) to ensure time scheduling when Supervisor PC is off-line, Supervisor PC is not required to execute time scheduling.

G. Define schedule capabilities either by floor or by air handler.

H. Override options include room sensor integrated pushbutton or hardwired switch in common area.

I. Define areas that have standby & 24/7 occupancy.

3.10 ALARM MANAGEMENT

A. Provide alarms including: 1. All alarms shown in tables below. 2. Contractor shall include any additional alarms required to meet specification section 25 1523

Graphics. 3. Contractor shall include any additional alarms required to meet specification section 25 3528

Control Sequences. 4. Contractor shall include any additional alarms depicted on control system drawings.

B. Niagara Bformatting shall be utilized in all To offNormal Text, To Fault Text and To Normal Text. For example, instead of “Space Temp Too High”, use the following Bformatting: %alarmData.sourceName% is at %alarmData.presentValue%, which is above the High Limit of %alarmData.highLimit%.

C. For alarms not listed in this schedule, use the following guidelines. The device name(s), present value(s) and alarm threshold(s) or condition(s), shall be expressed in Bformatting. Hard coded values shall not be acceptable.

D. All Bformatting subject to approval of FAC.



E. On each Alarm Extension, the Alarm Source Name shall be correctly bFormatted to automatically prepend the Point Display Name, with JACE Name (Station Name if alarm extension resides in Supervisor) and Controller Name, in the format: JACEName_ControllerNAme_PointName, in both the Source and Message Text fields of each alarm record as it appears in any alarm console.

F. Alarm values shall be adjustable from a JACE using Niagara Workbench (WBJ-Adj.). 1. Any WBJ-Adj. value, that is not integral to an alarm extension, i.e. external setpoint or alarm

differential, shall be a dedicated Niagara Numeric Writable Point. Hard coding the value into a calculation block is not acceptable.

2. The Niagara Numeric Writable Point shall be the same object name for every instance of same WBJ-Adj. point to facilitate batch editing of WBJ-Adj. points.

3. WBJ-Adj. point shall be adjustable from Workbench by anyone with Programmer or higher level of access.

G. Use of Boolean Alarm extensions, on analog (Numeric) values, is not acceptable.

H. Provide alarms per project I/O table. Coordinate with Owner points requiring DDC alarming and include the following: 1. Point Name and Description 2. Alarm differentials (automatically adjust with setpoints) 3. Units 4. Coordinate settings (limits or state) with Owner 5. Instrument tag 6. Priority 7. Message

I. Include the following Communication alarms:

Point Description

Alarm if: Delay Time

Inhibit Time

Priority Level

Alarm Class Alarm Text To Normal Text

Niagara Network Heath Alarm

Any Niagara Station Offline > 5 min. (WBJ-Adj.)

5 min 10 Communication Prepend with bFormatting: BuildingName_StationName:

Prepend with bFormatting: BuildingName_StationName:

LON Network Heath Alarm

Any LON Device Offline > 5 min. (WBJ-Adj.)

5 min 10 Communication Prepend with bFormatting: JACEName_DeviceName:

if multiple LON trunks on JACE JACEName_LONtrunkID_DeviceName:

Prepend with bFormatting: JACEName_DeviceName:

Modbus Network Health Alarm

Modbus missing timing pulse > 5 min. (WBJ-Adj.)

5 min

10 Communication Prepend with bFormatting: BuildingName_StationName:

Prepend with bFormatting: BuildingName_StationName:



J. Include the following alarms for all VAV boxes with Reheat Coil:

Point Description


Inhibit Time

Priority Level

Alarm Class

Alarm Text To Normal Text

Space Temperature

>4°F (WBJ-Adj.) above Cooling SP

20 min 2 hrs 200 Trouble-shooting

Offnormal Algorithm, High Limit Text:

%alarmData.sourceName% is at %alarmData.presentValue%, which is above the High Limit of %alarmData.highLimit%

%alarmData.sourceName% is at %alarmData.presentValue% which is below the High Limit of %alarmData.highLimit%.

>4°F (WBJ-Adj.) below Heating SP


Offnormal Algorithm, Low Limit Text:

%alarmData.sourceName% is at %alarmData.presentValue%, which is below the Low Limit of %alarmData.lowLimit%

%alarmData.sourceName% is at %alarmData.presentValue% which is above the Low Limit of %alarmData.lowLimit%

>95°F (WBJ-Adj.)

150 Critical Temps




<55°F (WBJ-Adj.)

150 Critical Temps




Special Space Temperature

>3°F (WBJ-Adj.) above setpoint over 4 hours (WB-Adj.)

150 Trouble-shooting





> 3°F (WBJ-Adj.) below setpoint over 4 hours (WB-Adj.)






>82°F (WBJ-Adj.)

5 min 150 Critical Temps





<63°F (WBJ-Adj.)







Critical Airflow

Actual Airflow <80% (WBJ-Adj.) of Minimum Airflow SP in Lab Zone

20 min 30 Critical Offnormal Algorithm, Low Limit Text:


%alarmData.sourceName% has returned to a Normal value of %alarmData.presentValue%, which is above the Low Limit of %alarmData.lowLimit%

Terminal Load

100% (WBJ-Adj.)

4 hrs 200 Trouble-shooting




Terminal Load

-100% (WBJ-Adj.)





Damper Position

100% (WBJ-Adj.)




%alarmData.sourceName% has returned to a Normal value of %alarmData.presentValue%, which is below the High Limit of %alarmData.highLimit%

Discharge Air Temperature (DAT)

> DAT SP + 5°F (WBJ-Adj.)

20 min 200 Trouble-shooting





< DAT SP – 5°F (WBJ-Adj.)





Valve Alarm DAT > AHU SAT + 8°F (WBJ-Adj.); while reheat valve position = 0% (WBJ-Adj.)



%alarmData.sourceName% is at %alarmData.presentValue%, which is above the High Limit of %alarmData.highLimit% while the HW Valve is Closed

%alarmData.sourceName% has returned to a Normal value of %alarmData.presentValue%, which is below the High Limit of %alarmData.highLimit% while the HW Valve is Fully Closed

Valve Alarm DAT < 72°F (WBJ-Adj.); while reheat valve position = 100% (WBJ-Adj.)


Offnormal Algorithm, low Limit Text:

%alarmData.sourceName% is at %alarmData.presentValue%, which is below the Low Limit of %alarmData.lowLimit% while the HW Valve is 100% Open

%alarmData.sourceName% has returned to a Normal value of %alarmData.presentValue%, which is above the Low Limit of %alarmData.lowLimit% while the HW Valve is 100% Open

Reheat Valve Position

100% (WBJ-Adj.)

4 hrs 2 hrs 200 Trouble-shooting






Actual Air Flow

>120% (WBJ-Adj.) of Air Flow SP





Actual Air Flow

<80% (WBJ-Adj.) of Air Flow SP





Damper Position

Damper Position = 0% (WBJ-Adj.); while airflow is greater than 50 (WBJ-Adj.) CFM



%alarmData.sourceName% is at %alarmData.presentValue%, while airflow is greater than 50 CFM.

%alarmData.sourceName% has returned to a Normal value of %alarmData.presentValue%, which is above the Low Limit of %alarmData.lowLimit%, while airflow is greater than 50 CFM.

Damper Position

Damper position = 100% (WBJ-Adj.); while airflow is less than 50 CFM (WBJ-Adj.)


%alarmData.sourceName% is at %alarmData.presentValue%, while airflow is less than 50 CFM. Check Damper Position.

CO2 (1) > 1000 ppm (WBJ-Adj.)





CO2 (2) < 300 ppm (WBJ-Adj.)





CO2 (3) >2,500 ppm (WBJ-Adj.)

20 Life Safety


%alarmData.sourceName% is at %alarmData.presentValue%, which is above the Unsafe High Limit of %alarmData.highLimit%

%alarmData.sourceName% has returned to a Safe Level of %alarmData.presentValue%, which is below the Unsafe High Limit of %alarmData.highLimit%



K. Include the following alarms for all Cooling Only VAV boxes:

Point Description


Inhibit Time

Priority Level

Alarm Class


Space Temperature











>95°F (WBJ-Adj.)

150 Critical Temps




<55°F (WBJ-Adj.)

150 Critical Temps

















>82°F (WBJ-Adj.)






<63°F (WBJ-Adj.)







Critical Airflow





Terminal Load

100% (WBJ-Adj.)





Damper Position

100% (WBJ-Adj.)

















Actual Air Flow






Actual Air Flow






Damper Position






Damper Position

Damper position = 100% (WBJ-Adj.); while airflow is less than 50 (WBJ-Adj.) CFM





CO2 (1) > 1000 ppm (WBJ-Adj.)





CO2 (2) < 300 ppm (WBJ-Adj.)





CO2 (3) >2,500 ppm (WBJ-Adj.)

20 Life Safety


%alarmData.sourceName% is at %alarmData.presentValue%, which is above the Unsafe High Limit of %alarmData.highLimit%

%alarmData.sourceName% has returned to a Safe Level of %alarmData.presentValue%, which is below the Unsafe High Limit of %alarmData.highLimit%



L. Include the following alarms for all FCU’s.

Point Description


Inhibit Time

Priority Level

Alarm Class


Heating Control Signal

100% (WBJ-Adj.) 4 hrs 2 hrs 200 Trouble-shooting

Offnormal Algorithm, High Limit Text: %alarmData.sourceName% is at %alarmData.presentValue%, which is above the High Limit of %alarmData.highLimit%


Valve Position

100% (WBJ-Adj.) 4 hrs 2 hrs 200 Trouble-shooting



Discharge air temperature (DAT)

>110°F (WBJ-Adj.) 20 min 200 Trouble-shooting



DAT Leaking Valve

DAT > Zone Temperature + 5°F (WBJ-Adj.); while valve position = 0% and fan status is on. (For hot water fan coil units only)


Offnormal Algorithm, High Limit Text: %alarmData.sourceName% is at %alarmData.presentValue% (VAV DAT), which is above the High Limit of %alarmData.highLimit%, while the Reheat Valve Position is at 0 %, and the Fan Status is ON. Leaking Valve ?

%alarmData.sourceName% has returned to a normal value of %alarmData.presentValue% , which is below the High Limit of %alarmData.highLimit%, while the Reheat Valve Position is at 0 %, and the Fan Status is ON.

DAT No Heating

DAT < Zone Temperature + 5° (WBJ-Adj.) F; while the valve position is greater than 30% (WBJ-Adj.) and the fan status is on and the heating hot water pump is on. (For hot water fan coil units only)


Offnormal Algorithm, Low Limit Text: %alarmData.sourceName% is at %alarmData.presentValue%, which is below the low Limit of %alarmData.lowLimit%, while the valve position is greater than 30% and the fan status is on and the heating hot water pump is on. No Heating ?

%alarmData.sourceName% has returned to a normal value of %alarmData.presentValue% which is above the low Limit of %alarmData.lowLimit% , while the valve position is greater than 30% and the fan status is on and the heating hot water pump is on.

Fan Fail Alarm

Status is off while Command is on.


To Offnormal Text: %alarmData.sourceName% is %alarmData.presentValue%, while the Fan Command) is ON - Fan Failure? Check Belts and HOA Switch.

%alarmData.sourceName% has Returned to Normal %alarmData.presentValue%, while the Fan Command is ON.

Fan In Hand Alarm

Status is on while Command is off.


To Offnormal Text: %alarmData.sourceName% is %alarmData.presentValue% , while the Fan Command is OFF - Return to Automatic

%alarmData.sourceName% has Returned to a Normal Status, %alarmData.presentValue , while the Fan Command is OFF.



M. Include the following alarms for all Lab Supply Air Valves / Exhaust Valves / Hoods:

Point Description


Inhibit Time

Priority Level

Alarm Class


Space Temperature











>95°F (WBJ-Adj.)

150 Critical Temps




<55°F (WBJ-Adj.)

150 Critical Temps

















>82°F (WBJ-Adj.)






<63°F (WBJ-Adj.)







Critical Airflow





Terminal Load

100% (WBJ-Adj.)





Terminal Load

-100% (WBJ-Adj.)





Damper Position

100% (WBJ-Adj.)

















Valve Alarm DAT > AHU SAT + 8°F (WBJ-Adj.); while reheat valve position = 0% (WBJ-Adj.)



%alarmData.sourceName% is at %alarmData.presentValue%, which is above the High Limit of %alarmData.highLimit% while the HW Valve is Closed

%alarmData.sourceName% has returned to a Normal value of %alarmData.presentValue%, which is below the High Limit of %alarmData.highLimit% while the HW Valve is Fully Closed

Valve Alarm DAT < 72°F (WBJ-Adj.); while reheat valve position = 100% (WBJ-Adj.)


Offnormal Algorithm, low Limit Text:

%alarmData.sourceName% is at %alarmData.presentValue%, which is below the Low Limit of %alarmData.lowLimit% while the HW Valve is 100% Open

%alarmData.sourceName% has returned to a Normal value of %alarmData.presentValue%, which is above the Low Limit of %alarmData.lowLimit% while the HW Valve is 100% Open

Reheat Valve Position

100% (WBJ-Adj.)

4 hrs 2 hrs 200 Trouble-shooting






Actual Air Flow






Actual Air Flow






Damper Position






Damper Position

Damper position = 100% (WBJ-Adj.); while airflow is less than 50 CFM (WBJ-Adj.)



Exhaust Air Terminal CFM Reading

>115% (WBJ-Adj.) of CFM SP





Exhaust Air Terminal CFM Reading

<90% (WBJ-Adj.) of CFM SP





Air Flow Differential

>110% (WBJ-Adj.) of Scheduled Differential SP





Air Flow Differential

<95% (WBJ-Adj.) of Scheduled Differential SP







Fume Hood Face Velocity

>115% (WBJ-Adj.) of Scheduled SP 100 FPM During Normal Operation. 60 FPM During Not In Use Periods

5 min 30 Critical Offnormal Algorithm, High Limit Text:



Fume Hood Face Velocity

<85% (WBJ-Adj.) of Scheduled SP 100 FPM During Normal Operation. 60 FPM During Not In Use Periods




Sash Height Above Maximum Sash Position





Sash Height At Maximum Sash Position For >24 Hours

24 hour

30 Critical Offnormal Algorithm, High Limit Text:



Sash Height Below Minimum Sash Position





Hood Alarms Hood in Alarm 30 Critical %alarmData.sourceName% is in Alarm %alarmData.sourceName% has returned to Normal



N. Include the following alarms for all Generator Rooms:

Point Description


Inhibit Time

Priority Level

Alarm Class


CO level in Engine Room

>35 PPM (WBJ-Adj.)

1 min 1 Critical_1




O. All VAV box alarms shall be inhibited while the AHU serving those boxes is non-functional.

P. Include the following Critical Callout Alarms: 1. All Leak alarms must indicate the room number that the leak originates from in the alarm

message string. 2. Owner to determine Alarm Class, i.e. Critical_1 (24/7 Technician callout) or Critical_2 (daytime

Technician callout). 3. All Critical Callout Alarms require a hyperlink to Callout Instructions.

BMS

BMS Main Power BMS Battery Power Loss of Network Communication

Automatic Transfer Switch ATS Emergency Power ATS Loss of Normal Power

Generator Fuel Oil Level (Low Fuel) Fuel Oil Leak Detection (High Fuel/Leak) Generator Trouble/Not in Auto Run Status

Room Leak (Elevator Pit, Mechanical Rooms, Lab Spaces, etc..) Tracetec Leak Tracetec Trouble

Sump Pump Start Lag Pump High Level Alarm Power Failure

Sewer Pump Start Lag Pump High Level Alarm Power Failure

Fire Alarm Status



TGO Alarm Status Status

PCW or HHW Makeup Water Water Flowrate Alarm

Air Handler Unit Fan Status Supply Pressure Motor Frequency Supply Temperature Filter DeltaP

Exhaust Fan Fan Status Pressure Motor Frequency

Parking Garage CO Level NoX Level

Critical Room Temperature and Humidity (VAV or FCU) Room Temperature Room Humidity

VAV and FCU Secondary Containment Alarm Status

Compressor Compressor Trouble Air Compressor Dew point Air Compressor Pressure Compressor Running Time

Vacuum Pump Vacuum Pump Trouble Vacuum Pump Pressure Vacuum Pump Running Time

Constant Temperature Box Constant Temperature Box (Outside Range) Constant Temperature Box Humidity (Outside Range) Constant Temperature Box Status

DI/RO Loop Resistivity Below (TBD) mohm Pump Status Tank Level (High/Low) System Pressure Skid Status Other Parameters (TOC, Bacteria, UV, etc…)

PCW



PCW Pressure PCW Supply Temperature Start Lag Pump PCW Loss of Power

Specialty Gas (CO2, N2, O2, etc…) Dewar Tank Pressure Dewar Tank Alarm

Bulk Chemicals (HF, ETC…) High Level Overflow Acid Line Leak

Fume Scrubber Status

Inverter/UPS Battery Status

Chemical Waste Neutralization Tank Level Sump Level PH Secondary Containment Leak Detection Bulk Treatment Chemicals

Fire Damper Actuator Status

Smoke Detector Status

Vivarium Room Differential Humidity Temp

Condensate Transfer Unit Fault

HHW HHW Discharge temp below 100 Lead Pump Status Lag Pump Status

CHW Pump Status

Domestic Water Pump Status Tank Temperature below 100



Q. Configure the following priority level scheme:

Alarms report to: Type Priority

Level Niagara Alarm Class Name

Local Supervisor Station Alarm Console

Local Supervisor Station Critical Alarms Console

facAlarmCon Campus DDC Alarm Servers

24/7 Callout 1 Critical_1 Yes Yes Yes Yes Daytime Callout 2 Critical_2 Yes Yes Yes Yes Communication (Not Ping Alarms)

10 Communication Yes No No Yes

Life Safety (Obsolete. Use Critical_1)

20 LifeSafety NO No No No

DDC Critical 30 Critical Yes No No Yes Central Plant 40 CentralPlant Yes No No Yes Main Air Handlers Limited

50 AHU Yes No No Yes

Building Hydronics

100 Hydronics Yes No No Yes

HVAC General 120 HVAC_General Yes No No No Important Temperatures

150 Critical_Temps Yes No No Yes

Troubleshooting 200 Troubleshooting Yes No No No Remainder, including all Ping Alarms

254 Default Alarm Class

Yes No No No

R. Coordinate and implement alarm notifications and routing with the Owner. Include: 1. Paging 2. Email 3. Text Messaging 4. Group and network notifications 5. Alarm acknowledgement. 6. Filter and route alarms based on user log in. 7. Alarm reports and messages will be directed to a user defined list of operator devices.

S. Provide hardware or interface required to implement alarm notification and routing.

T. Provide state-based alarming to prevent alarms during specific equipment states. 1. Interlock equipment status and/or modes to lock out associated alarms during shutdowns. 2. Interlock acknowledgement to lock out associated alarm for limited adjustable time period.

U. Provide continuous monitoring of network connectivity for the all networks. Generate alarm upon any communication failure.

V. Alarms shall be inhibited for a specified time period after a change in occupancy or for AHUs that are off.



W. Contractor shall ensure that alarms passed to any remote Station Recipient shall retain alarm class and priority level.

X. Contractor shall use only the exact Niagara alarm class names listed above to ensure compatibility with remote station recipients. Alarm Class Mapping is not acceptable. Note: Niagara object naming conventions do not permit spaces.

Y. Alarms report to LocalHost Alarm Console on building control systems server. If project scope does not include a building control systems server, alarms report to Alarm Console in building level controller.

Z. Alarm Source Name shall prepend with the following B-Formatting: %parent.parent.parent.displayName%_%parent.displayName% or as required to produce the format: StationName_ControllerNAme_PointName

AA. Only the toOffnormal and toFault events require the alarms to be acknowledged.

BB. toNormal and toAlert events shall not require the alarms to be acknowledged.

3.11 REPORTS

A. Coordinate report requirements with owner.

B. Schedule initial reports printouts monthly per owner request including: 1. Utilities or Energy Management 2. Diagnostic or system status 3. Equipment runtime

3.12 Database Point Names

A. All Niagara Database point names shall match naming of the sample Stations furnished to Contractor by Stanford FAC.

B. All Niagara Database point names shall match Object Naming and Tags Spreadsheet furnished to Contractor by Stanford FAC.

C. All Niagara Database point names shall be submitted to Stanford FAC for approval. Approval of Submitted Point Name does not constitute approval of the programming that uses the Submitted Point Name.

Any additional Niagara Database point names are subject to approval by Owner.

D. Any Niagara Database point names, that are created or modified without approval of Owner, may be required to be renamed, at no additional cost to Owner and without affecting Project Construction Schedule.

END OF SECTION



THIS PAGE INTENTIONALLY BLANK

Documents

SECTION 25 0000 - Stanford Universityweb.stanford.edu/group/lbre_apps_forms/maps/fdg/fdg_documents_pdf/25_12_23_Client...C. Stanford University Niagara 4 Standards. Latest version