Attachment 20 FRCS-AppendixL.pdf

DEPLOYMENT CENTER / FLIGHT DINING / AAFES AT TYNDALL AIR FORCE BASE

PN: XLWU203031

CADDCODE: MEF20036

Appendix L

APPENDIX L

FRCS GUIDE

This Page Left Intentionally Blank

APPENDIX L CONTENTS

01 Tyndall Rebuild – Facility Related Control System (FRCS)

Technology Summary

02 ICEE Naming Standard

This Page Left Intentionally Blank

Tyndall Rebuild - Facility Related Control Systems (FRCS)

Technology Summary

This document is intended as an overarching guide to how Tyndall Air Force Base will utilize FRCS technology to create a connected and data driven Installation.

Tyndall’s application of FRCS technology must align with the Base of the Future (BoT) concept, with the FRCS design and implementation focusing on development of a smart connected facility with a people-focused platform to optimize facility operations and energy resiliency. All systems described herein shall be contractor furnished contractor installed (CFCI) by the USACE awarded building contractor unless noted otherwise. The systems shall be complete and operational with no expectation of equipment being furnished by others. All equipment purchased for these systems shall meet the J&A requirements as stated in the USACE J&A Control No: SAM 20-0005. Refer to Project solicitation documents for facility specific requirements. Any open design criteria items or project scope clarifications should be directed to the USACE COR and documented per the prescribed RFI process during bidding.

Per USACE J&A Control No: SAM 20-0005, Siemens USA has been identified as the sole-source provider of the FRCS and Industrial Control Systems (ICS) programmable building controllers (excluding HVAC controllers) described herein. Siemens or a Siemens-certified installer is required to perform the FRCS scope of each project where required by vendor or UFC requirements unless otherwise stated herein or as described in the solicitation documents.

Contractor to submit an RFI for any questions related to the guidance herein or the solicitation package.

Any changes or deviations are to be coordinated with the 325th COR, Fred Wassil, through the USACE

COR.

1. FRCS Implementations Overview General overview and the intent of using FRCS for BoT.

1.1. Applicable Guidelines and Criteria

The following is the list of related United Facility Criteria (UFC) and United Facility Guide Specifications (UFGS) related to this project. Note all applicable UFC are required for the project, and nothing in this document negates any UFC requirements. All applicable UFGS must be tailored by the designer of record (DOR) with coordination of USACE and Tyndall Air Force Base.

United Facilities Criteria:

� UFC 3-410-01 - Heating, Ventilating, and Air Conditioning Systems � UFC 3-410-02 - DDC for HVAC and other Building Control Systems � UFC 4-010-06 - Cybersecurity of Facility-Related Control Systems � UFC 3-470-01 - Utility Monitoring and Control System (UMCS) Front End and Integration � UFC 3-530-01 – Interior and Exterior Lighting Systems and Controls � UFC 3-600-01 – Fire Protection Engineering for Facilities � UFC 4-021-01 – Design and O&M: Mass Notification Systems � UFC 4-021-02 – Electronic Security Systems

United Facility Guide Specifications

� UFGS 23 09 00 – Instrumentation and Control for HVAC � UFGS 23 09 13 – Instrumentation and Control Devices for HVAC � UFGS 23 09 23.02 – BACnet Direct Digital Control for HVAC and Other Building Control Systems � UFGS 23 09 93 - Sequences of Operations for HVAC Controls � UFGS 25 05 11 – Cybersecurity for Facility-Related Control Systems � UFGS 23 08 10 – Utility Monitoring and Control System Testing � UFGS 25 10 10 – Utility Monitoring and Control System (UMCS) Front End and Integration � UFGS 28 31 76 Interior Fire Alarm and Mass Notification System, Addressable

Air Force Requirements:

� AFGM 2020-32-01 – Civil Engineer Control Systems Cybersecurity

1.2. Facility Related Control Systems – General Requirements

The intent of the FRCS is to allow monitoring at the operations level. Operations level is defined as the operations center, but will include the Utility Operations Center (UOC), Installation Communications Center (ICC), and Base Defense Operations Center (BDOC) separately. The ICC acts as the primary location for use of the installation wide Utility Monitoring and Control System (UMCS), locally referred to as the Environmental Management Control System (EMCS) – Siemens Desigo CC, and provides the visibility and functionality as described in this document. The names of the operations centers are subject to change.

FRCS must have the ability to be viewable at any operations center based on installation requirements outlined in the Interface Schedule to be developed by the DOR and as defined in this document.

1.3. System Integration/Interface Requirements

The following control systems, which are a subset of FRCS identified in 10 USC 2867, are to be integrated in to the UMCS in accordance with UFGS 25 10 10 and UFC 3-470-01.

� Heating, Ventilation, and Air Conditioning (HVAC) � Lighting � Domestic Hot Water � Submetering � Utility Metering (Water, Gas, Electrical) � Fire Protection System � Fire Detection System

These systems are to be integrated into the UMCS and the UMCS Front End utilized as the only front end for the system. Licensing are to be provided for all systems within each building sufficient to cover the integration of that building into Siemens Desigo CC. Building level user interfaces, such as Local Display Panels, may be provided for these systems if requested by the installation.

� The HVAC control system and the Domestic Hot Water control system will utilize BACnet from the Front End to the last networked device. Equipment is to be provided with BACnet cards and integrated into the UMCS front end.

� Lighting control system is required to utilize BACnet from the Front End to either the last networked device, or to a gateway to a field control system or subsystem using another protocol.

Integrate all facility-related Power Distribution and Utility Metering Systems into Tyndall AFB’s UMCS Front End. Power distribution and metering systems may utilize appropriate protocols such as DNP 3.0, Modbus, or IEC-61850 as appropriate to the systems and their integration with the UMCS Front End.

Each of the following control systems are to provide a single basewide front end for the system and interface to the basewide UMCS at the basewide system level unique to that system:

� Electronic Security System (Front end capable only) � Intrusion Detection System (IDS) (Front end capable only) � Gunshot Detection System

1.4. Integrated Control Systems

All control systems described in this section must have the ability to use sensor data from the other control systems. For example, an occupancy sensor point signal used for lighting must be available for use in the HVAC control system.

The following design submittals are required for every integrated control system:

� Point Schedule, as defined in UFC 3-410-02:

o The design must include Points Schedules which are fully completed for design as indicated in the UFC for all systems controlled by BACnet devices, including requirements on view ability, override capability, configurability, trending, and alarming for every point. All BACnet devices must be addressed on a Points Schedule.

o For systems using non-BACnet protocols and with a gateway to BACnet, provide Points Schedule for the BACnet side of the gateway.

o For systems using non-BACnet protocols and their own front end, provide Points Schedules for the entire non-BACnet system. Points Schedules must be as complete as possible for the protocol in use, with additional protocol information columns added as needed. If a system will require a separate frontend, it must be approved by the contracting officer.

o The design package specifications must include a requirement for Points Schedules to be included in as-built drawings for all systems, regardless of whether they use BACnet or another protocol. For non-BACnet devices Points Schedules must be as complete as possible for the protocol in use, with additional protocol information columns added as needed.

These requirements must be reviewed with the installation on a system by system basis.

� System Interface Schedule: For each system interfacing with the UMCS at the base wide system level, provide an interface schedule documenting the interface and showing at a minimum:

o Protocol used for communication o Points shared between the system Point Name Point Description Point Source/Origin System Point permissions (read, read/write) o Any additional information necessary to establish communication between the systems or to create/modify the information shared between the systems.

� Graphical User Interface plan incorporating all operationally relevant points into a 3-dimensional floorplan graphic. The plan must also integrate the facility into the installation-level perspective view.

� Network Architecture (Riser Diagram) � Sequence of Operations – Provide a narrative on the step by step instruction on control system � operations, including unoccupied periods.

� Occupancy and Thermostat Sensor Schedule

All FRCS trending data must be stored at the facility for a minimum of two weeks in the event of communication failure between the operations center and the building to ensure consistent trending.

1.4.1. Integrated FRCS Specific Use Cases

The following use cases are required functionality built into the FRCS being installed at each building and facility, unless otherwise specified. All design submittals described in the integrated control system section are required for use case as well and labeled as for the use cases if they are submitted as a part of another FRCS submittal. Submittals include, with the same requirements as described above:

� Point Schedule � System Interface Schedule � Network Architecture (Riser Diagram) � Proposed System Information � Commissioning and Performance Verification Testing (PVT) procedures and requirements

Additional submittals are required for the following use cases:

� Proposed System Information – if there is a specific proprietary product to be used to meet the use case, provide all informational documents and data sheets of the product for review and approval.

� Commissioning and Performance Verification Testing (PVT) procedures and requirements – provide commissioning and PVT documentation for review and approval. The CES must be incorporated into commissioning to ensure system-wide interoperability.

� Calibration Plan – provide calibration plan for all proposed sensors in FRCS use cases � Training Requirements – provide training recommendations and requirements for review and approval for each use case solution. Training must occur and have the intent to provide the installation the knowledge and tools to maintain the design conditions of the system.

The communication protocol for the use case control system must be BACnet IP, BACnet MS/TP, or hardware I/O (4-20 mA, 0-10 V or binary). If a waiver to utilize a proprietary control system has been approved, a BACnet gateway must be used to connect the non-BACnet control hardware to the BACnet system and integrated to the building level supervisor where the BACnet supervisory gateway does not have the capability of communicating in that devices native protocol.

1.4.1.1. Building Control System (BCS)/Utility Monitoring and Control Systems (UMCS)

Building Control Systems (direct digital controls) shall be Siemens Apogee. The contractor programming controllers on this system must licensed by Siemens. All BCS/UMCS will integrate into the Siemens Desigo front end. The contractor programming Desigo must be licensed by Siemens. Existing Tri-Service unified facility criteria and guide specifications on HVAC controls have been in place for many years.

These documents, however, require tailoring for communication protocol and rely on several designer decisions to account for site and project-specific needs. While robust DoD controls criteria is currently limited to HVAC controls (also known as Direct Digital Controls or DDC), the criteria does heavily detail the process for open integration of those controls into a base-wide Utility Monitoring and Control System (UMCS) front-end in a way that can serve as a model for other Building Control System (BCS) integration.

1.4.1.1.1. Requirements

Applicable Guidelines and Criteria includes facility design criteria and guide specifications for BCS and UMCS. The following list of TAFB BCS and UMCS requirements must be included in all TAFB design and construction projects as part of specification tailoring and inclusion of site preferences into contract documents:

� Protocols:

o Tailor the following BCS specifications for BACnet protocol only with no use of Niagara

Framework:

UFGS 23 09 00 – Instrumentation and Control for HVAC UFGS 23 09 23.02 – BACnet Direct Digital Control for HVAC and Other

Building Control Systems UFGS 25 10 10 – Utility Monitoring and Controls System (UMCS) Front End and Integration

� Submittals: For all submittals required by UFGS 23 09 00 – Instrumentation and Control for HVAC and UFGS 25 10 10 – Utility Monitoring and Control System (UMCS) Front End and Integration, use the following criteria:

o Every submittal shall be provided in both hard-copy and CD-ROM formats o Provide a minimum of four hard copies of each submittal for distribution to POCs listed in below Submittal Distribution list o Provide a minimum of four CD-ROM copies of each submittal for distribution to POCs listed in below Submittal Distribution list o BCS contractor must develop and provide Control Logic Diagrams (CLDs) using format, symbols, consistency, and related conventions as described in UFC 3-410-02 - DDC for HVAC and other Building Control Systems

� Devices:

o Provide all DDC controllers located in mechanical rooms in lockable enclosures o Ethernet switches:

Aside from Ethernet switches integral with controllers to allow “daisy chaining” of IP controllers, do not provide Ethernet switches.

IP controllers (an IP networks using controllers with built-in switches) must to the Air Force provided switch.

If the Air Force provided switch is not available at the time of control system installation, a temporary Ethernet switch may be installed at or near the location of the future switch to allow for the control system installation, start-up, and testing activities.

If the temporary switch is not located in the same location at the future Air Force provided switch, all network cabling must be of sufficient length to allow for future connection to Air Force provided IP switch.

As-built (including “design” as-builts and draft as-builts) must include the number of required Ethernet ports for connection at the Air Force provided switch.

o Coordinate with USACE Contracting Officer for switch locations.

o Coordinate with below site POC info for all coordination and approval associated with Device

IDs, Network Numbering, and IP Addresses o Configure and provide Local Display Panels (LDPs) as required by Points Schedules for all central and terminal DDC equipment and collocate in mechanical rooms spaces as indicated on drawings o Hand-of-Auto (HOA) functionality must be provided as follows:

on all analog and binary BCS outputs other than terminal units either through local display panel or DDC controller hardware 0 to 100% required for all analog outputs

HOA feedback must be provided on all HVAC damper, HVAC valves, and HVAC motor commands other than for terminal units o Each terminal unit including thermostats must have a wall network interface jack accessible within the boundaries of the thermal zone, consistently located and limited within the building, and shown on plans o DDC thermostat or non-DDC space sensor modules must be configured with the following functionality and represented on design Temperature Control Module schedules:

a temperature indicating device a User Input Device which must adjust a temperature setpoint output a User Input Momentary Contact Button and an output to the control system indicating zone occupancy.

o Gateways:

require waiver approved by the contracting officer use Points Schedule requirements for integration of non-BACnet field control systems (eg, Modbus, chiller, boiler, or VFD interface) and determination of points to map, share, trend, display, or alarm provide capacity for mapping an additional 10% of points more than what is indicated on Point

Schedule drawings o Media:

IP network furnished by contractor as required to deliver BCS and UMCS complete functionality described If using MS/TP communication, 3-wire media is required.

� UMCS Feature Options:

o Scheduling:

Group terminal units into common zone-level schedules based on design zone type Provide capability and licensing to support a minimum of 200 user-definable schedules o Report generation:

Provide equipment reports and other usage reports as required in the FDD portion of this document o Graphics:

Provide 3-dimenstional representation of individual pieces of equipment Display all units in IP with consistent display accuracy per unit type Provide Graphical User Interface plan incorporating all operationally relevant points into a 3-D floorplan. The plan must also integrate the facility into the installation-level perspective view.

o Trends:

Initial interval required for analog values is 5 minutes Software must support a minimum of 8,000 simultaneous trends o Alarms:

no less than 10,000 ASHRAE 135 alarm event notifications follow existing TAFB UMCS alarm group conventions; if none exist, provide the following groups/levels:

• Level 1: Life-safety message

• Level 2: Critical equipment message

• Level 3: Urgent message

• Level 4: Normal message

� Testing:

o Performance Verification Testing Endurance Testing must be for a minimum 10 consecutive days � Training Details:

o Obtain approval of the training schedule from the Government at least 60 days prior to the first day of training.

o Minimum training criteria as follows for each building:

Minimum 8 hours and 10 operating staff members for UFGS 23 09 23.02 BACnet Direct Digital

Control for HVAC and Other Building Control Systems � Controls Maintenance and Warranty:

o No network maintenance required o Provide Semi-annual Maintenance, Software/Firmware Updates, and related Maintenance

Procedures as described in UFGS 25 10 10 – Utility Monitoring and Control System (UMCS) Front End and Integration over the warranty period.

� Sequences:

o Include warm-up/cool-down sequences on all air-side systems and thermal zones o Include chiller optimization sequences on all chiller systems o For hydronic system enables, monitor zones served by the hydronic system enable status and enable the hydronic system whenever:

More than 5 zones served AND 5% of all zones served become enabled Critical zones and units as assigned by TAFB CES staff become enabled o Electric demand-limiting sequences as described in UFGS 25 10 10 – Utility Monitoring and Control System (UMCS) Front End and Integration with notifications as described by FDD requirements

� Hardware Input/Output:

o Provide all BCS sensors using the highest accuracy designer option available in UFGS 23 09

13 – Instrumentation and Control Devices for HVAC o Tailor all enclosure designer options in UFGS 23 09 13 – Instrumentation and Control

Devices for HVAC and UFGS 23 09 00 – Instrumentation and Control for HVAC based on location of the enclosures. Locate all BCS away from hazardous areas, such as indoors and not underneath potentially leaking hydronic systems o Provide all HVAC control dampers and valves using the most stringent leakage rating available in UFGS 23 09 13 – Instrumentation and Control Devices for HVAC

� Commissioning Specification: Cite UFGS 01 91 00.15 Total Building Commissioning as a related work commissioning specification in UFGS 23 09 00 Instrumentation and Control for HVAC and in any other specification instances requiring commissioning requirement references

� POCs:

o Submittal Distribution: for all UFGS 23 09 00 and UFGS 25 10 10 hard copies:

CES – two copies TAFB Program Management Office – one copy USACE Mobile Project Office – one copy o Submittal Distribution: for all UFGS 23 09 00 and UFGS 25 10 10 CD-ROMs:

CES – one copy TAFB Program Management Office (PMO) – one copy USACE Mobile Project Office Copy – one copy USACE Mobile District Copy – one copy o Coordinate with CES into total building commissioning planning process.

o Coordinate TAFB UMCS Submittal Review, Points Schedule Naming Review, and Device

ID/Network Number Coordination with CES o Coordinate TAFB System Admin POC with CES o Coordinate TAFB Training with CES

Additional tailoring options and designer decisions required or allowed by these specifications must be coordinated with TAFB CES staff as part of BCS/UMCS design and specification input:

� Point Naming Conventions must follow ICEE convention:

o Part 1: TAFB Building # (e.g., “B430” for building #430) o Part 2: Real Property Unique Identifier or System Name (e.g., “AHU1”) o Part 3: Device description to describe signal source (e.g., “MA” for mixed air) o Part 4: Measured variable or controlled device (e.g., “T” for temperature) o Part 5: When applicable, a modifier to indicate some limit, command type, or enable signal

(e.g., “LL” for low limit) o Part 6: When applicable, an additional modifier to indicate additional information about the signal (e.g. “SP” for setpoint) o Use “_“ separators between point name parts, with exception between parts 3 and 4 (for this example, the entire point name would be “430_AHU1_MAT_LL_SP”) o Use other conventions and examples from UFC 3-410-02 - DDC for HVAC and other

Building Control Systems Appendix E to ensure consistent point naming across TAFB buildings and projects

� Features:

o Alarming: provide additional alarm level-specific features intended to streamline notification processes and limit nuisance messages:

Entry Delay: alarms must have user-adjustable time delays prior to triggering with the following default values:

• Level 1: 1 second at TRUE condition

• Level 2: 10 seconds at TRUE condition

• Level 3: 1 minute at TRUE condition

• Level 4: 5 minutes at TRUE condition

Exit Hysteresis: alarms must meet exit hysteresis conditions prior to a return to normal:

• User-adjustable time-based hysteresis, default 5 seconds

• User-adjustable percent-of-limit hysteresis for analog alarms, default 0%

Latching: alarm levels 1 and 2 must require physical or digital acknowledgement from operators before a return to normal

Post-exit Suppression: alarms must have adjustable suppression periods to prevent specific instances of alarms retriggering until the post-exit suppression time amount has elapsed with the following as default values:

• Level 1: 0 seconds

• Level 2: 5 minutes

• Level 3: 24 hours

• Level 4: 7 days

Hierarchical Alarm Suppression: provide alarm functionality that suppresses interrelated level 2-4 alarm messages that are “downstream” of equipment in some failure alarm state, examples include:

For cooling tower system failure or setpoint deviation, suppress “downstream” chiller, AHU, and zone setpoint deviation alarms

For boiler system failure, suppress all setpoint deviation alarms for equipment served by the hot water system including AHU coils and terminal equipment

For terminal equipment in alarm state, suppress al zone-level alarms such as CO2, temperature, or relative humidity setpoint deviation for that zone only

Maintenance Mode: operators must have the ability to place any BCS system in or out of a Maintenance Mode such that:

• Level 2-4 alarms will be suppressed when the system is in Maintenance Mode

• A Level 3 alarm will be issued daily to indicate the system’s status as active in Maintenance

Mode o Sequences: include the following additional BCS sequence of operation features:

HVAC setpoint resets must be provided for the following sequences of operations through trim-and-response control with weighted factors for critical or high-volume zones and separate user-adjustable trim and respond rates:

• Primary or secondary hot water and chilled water supply temperature setpoint

• Condenser water temperature setpoint

• Duct static pressure setpoint

• Zone and system-level minimum ventilation flow setpoint

Provide additional sequences for:

• Chilled water system optimization

• Building-level global command of terminal equipment for balancing purposes

• Default controller-level values for schedule and global temperature when network data is unavailable or out-of-range � Graphics:

o Provide 3-dimensional HVAC system-level graphics with “untangled” representations of piping and ductwork such that order of connection and HVAC controls hardware locations are accurate, but pipe and duct runs are simplified for simplicity and ease of graphics comprehension o Provide floorplans which integrate all operationally relevant points within each building.

� BCS/UMCS Training:

o BCS or UMCS Training may occur on non-consecutive days with prior written approval from Tyndall CES staff from POC info in this document o Up to 25% of any BCS or UMCS training may be administered remotely or through online access to vendor-specific training with prior approval, provided that prior approval is also granted in writing and all remote or online content is captured and delivered as part of training submittals

� Additional Documentation:

o Laminated 11”x17” control schematics, logic block diagrams, sequences of operation, points schedules, and ladder diagrams attached to every BCS control panels or nearby accessible wall space via Velcro o All project as-builts, manuals, and completed Performance Verification Test (including endurance test results) must be accessible to UMCS users via front-end web pages or links.

� Non-HVAC UMCS Requirements:

o Represent additional FRCS integrations into the UMCS using UFC 3-410-02 - DDC for

HVAC and other Building Control Systems approaches and conventions. This includes backup generation equipment.

o For spaces greater than 500SF and with a design occupancy density greater than 25 people per 1,000 square feet of conditioned zone space, provide digital lighting controls with at least 3 configurable scene lighting scenarios and integrate into the BCS/UMCS o Collect building-level energy (electrical and natural gas) and water metering data using BCS o Collect sub-metered electrical data for all major building systems including central HVAC systems (pumps, chillers, cooling towers, boilers, and air handling units) data centers or other building-level IT loads > 5 kW, overall building-level lighting systems, and specialty or high-wattage lighting systems (such as aircraft hangar lighting or exterior lighting > 5kW).

Equipment that is capable of transmitting its own consumption data (e.g., VFD gateway) may be used in lieu of separate sub-metering provided the gateway usage meets criteria requirements and usage data is provided per Points Schedule drawings.

o Collect sub-metered electrical data for all remote generator tie-in locations to provide status and information for potential backup generator

1.4.1.1.2. Applicability and Data Output

BCS/UMCS requirements apply to all HVAC but to the greatest extent possible must be extended to lighting and metering system requirements and any use cases that can be supported by the BCS via open protocol. Additional requirements include the following systems and their points; however, others may be required to specific sequences of operation, monitoring, or FDD functionality. At a minimum, represent the following points and all applicable type, protocol, and interface feature information on Points Schedule documentation using UFC 3-410-02 - DDC for HVAC and other Building Control Systems approaches and conventions:

� Typical Chiller points:

o Chiller status, enable, start-stop command, alarm state, and alarm description o Compressor power, run status, oil temperature, and high/low oil pressures o Evaporator pressure, water flow rate, inlet/outlet temperatures, pump start request/status, and refrigerant temperature/pressure o Condenser pressures, inlet/outlet temperature, pump/fan start request/status, flow, and refrigerant temperature/pressure o Electrical voltage, current, and power for each chiller phase o System setpoints, reset information, cooling load, and additional diagnostics points

� Typical Boiler points:

o Enable command, flame, flow switch, boiler/fan/pump status, and alarm contacts/codes o Firing rate, flue temperature, inlet temperature, outlet temperature, and cascade info o Reset setpoints, external tank temperatures (if applicable)

� Typical VFD Points o Operational, frequency, enable, and setpoint commands o Output frequency, voltage, current, power, and drive energy o Control method, acceleration/deceleration time, and drive runtime o Drive status, hardware error, external fault, fuse blown, overvoltage/overamperage, and other fault data � Typical Central AHU Points:

o System mode command and unit status o Supply air pressure/flow, fan command/minimum/status, temperature/setpoint o Return air flow, flow different setpoint, fan command/minimum/status, temperature

Coil discharge temperature/setpoint, valve position/feedback o Outside air flow/setpoint, damper command/feedback, and temperature o Smoke, low limit setpoints, supply pressure limit setpoints, and system reset button o System night stat/low limit, air filter pressure or switch, CO2 setpoints, reset ranges

� Typical Thermal Zone Points:

o System scheduler, zone input, and effective occupancy points o Zone temperature, zone occupied/unoccupied/stand-by zone temperature setpoints o Zone CO2, relative humidity values and setpoints o Terminal equipment valve/fan/damper commands/feedback and airflow values/setpoints

� Typical Lighting Zone Points:

o System scheduler, zone input, effective occupancy, run hours, and timeout setting points o Zone lighting command and status o Photo sensor value, dimming/level command, as applicable o Scene settings, as applicable o Consumption data, as applicable

� Typical Energy and Water Metering Points:

o Volts, Amps, power, frequency, power factor, and reactive power for each electrical metering phase o Total power, total energy, peak demand (user-adjustable time period), and average line frequency for electrical metering o Flow rate and total flow for natural gas and water metering

1.4.1.1.3. Outcomes

� Energy efficient operations � Strategic use of UMCS features like alarms and graphics � Provides model for FRCS integration and facilitates FDD

1.4.1.1.4. Capabilities

This use-case will enable the following capabilities:

� Automated open HVAC and other BCS operation � UMCS Interface features for training operator staff � Data to drive both operator alarms and FDD analysis

1.4.1.2. Fault Detection & Diagnostics

The purpose of the FDD system is to analyze data produced by utility meters and building systems in order to provide action-oriented information to maintenance, energy management, and command staff on building-level faults, trends, anomalies, and opportunities for improved performance and reduced energy use in the operation of facility equipment systems.

The Contractor is responsible for providing Fault Detection and Diagnostics (FDD) functionality with automated analytics scenarios, dashboard summary graphics, and advanced notification capabilities. FDD systems will integrate into Siemens Desigo through the Siemens Apogee BCS/UMCS system.

1.4.1.2.1. Description

In order to ensure effective procurement, customization, testing, and integration of FDD systems, adapt applicable design approaches and requirements from UFC 3-470-01 UMCS Front End and Integration and UFGS 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration including:

� Performance Verification Test (PVT) requirements for all FDD scenarios including endurance testing and documentation of all FDD parameter calibration performed

� Points schedule approach to link FDD functionality to specific Building Control System point data and incudes documentation of all FDD parameters (assumed sensor errors, rolling average time quantities, etc.)

� Consistent use of engineering units and precision; graphics and navigation conventions; point naming or tagging approaches; display terminology; and other graphics standards as defined and based on Tyndall AFB CE staff preferences

� FDD-specific drawings including FDD schedules to link analytics functionality to specific building systems, FDD notification groups/level schedules, FDD shop drawings, and equipment schedules for any FDD-specific hardware � Submittal requirements including PVT procedures and reports, product data, license information, and O&M data.

� Approaches to permission levels and password/account management � Electrical, water, HVAC equipment, and other usage report requirements � Preventative Maintenance Work Plan for FDD systems including calibration requirements, seasonal checks, and data backups � Service support requirements from FDD contractor � User-specific training approaches including tiered basic, advanced, and refresher training requirements

1.4.1.2.2. Applicability and Data Output

To the greatest extent possible, FDD systems must use data generated from BACnet integration of equipment installed under the project. Any additional data required for FDD functionality must be provided through open protocol communication or secured API connections. All buildings must include FDD functionality as applicable to installed building systems. Minimal FDD functionality must include:

� Usage Dashboard, Reports, and Notifications: use a tiered user-specific approach to provide energy, water, and equipment use reports at fixed intervals. Usage data must be provided a building and base roll-up levels. Intervals shall be user-configurable with an initial default configured at one-month intervals.

o Energy and water consumption data must provide information on total usage compared to previous year’s same time period; usage intensity/index (based on building square footage); projected end-of-year usages; comparison to benchmark goals and peer-group Tyndall AFB buildings; normalization for weather and occupancy; highlights for spikes or dips in usage; and recommended actions for TAFB CES staff to pursue.

o Equipment usage reports must be provided for all major building systems including central HVAC systems (pumps, chillers, cooling towers, boilers, and air handling units) data centers or other building-level IT loads > 5 kW, overall building-level lighting systems, and specialty or high-wattage lighting systems (such as aircraft hangar lighting or exterior lighting > 5kW). Equipment usage reports must include information on equipment runtime, sub-metered or calculated energy usage, energy intensity (in appropriate units such as power use index, kW or Btuh per air/water flow units, or kW per space square footage served), energy efficiency factors (such as chiller average kW per ton or boiler combustion efficiency), information on efficiency factor degradation based on historical or benchmark levels, alarm counts, end-of-interval status, O&M actions needed, and predictive maintenance projections such as filter replacement scheduling, refrigerant charging, boiler tuning, coil cleaning, or hydronic water quality issues.

� Flow Leakby: automated notifications for TAFB CES when any central or terminal HVAC valve, damper, or energy recovery wheel is identified by FDD systems as showing signs via temperature or flow measurements of air or water leak-by.

Provide specific equipment location as part of notifications with recommendations for appropriate inspection, replacement, cleaning, or adjustment tasks necessary.

Provide an energy cost penalty estimate and associated priority for each fault. Suppress downstream supply or zone temperature deviation faults when this fault is triggered.

� Simultaneous Heating & Cooling: automated notifications for prolonged instances within or across HVAC systems that results in simultaneous heating and cooling operations. Air handler or terminal reheat following dehumidification processes must not be handled by FDD systems as automatic fault, however excessive reheat associated with overventilation, inconsistent setpoints, or reduced occupancy must provide faults to CE staff. Provide an energy cost penalty estimate and associated priority for each fault

� Controller/Network Failure: automated notifications to identify all sustained losses in communication or overall controller failure. Faults must roll-up communication issues into single fault (e.g., single alert for 8 controllers with loss of communication vs 8 separate simultaneous alarms). This fault must include notifications for loss in overall UMCS network and thus cannot rely solely on UMCS network infrastructure to accomplish fault transmission for overall network loss.

� Failed or Improperly calibrated Sensor: define out-of-range conditions and automated analysis processes of historic trends to provide notifications when Building Control System sensors are completely failed, out-of-range, drifting, or otherwise inaccurate given operational circumstances. At a minimum, this fault must be included for all central HVAC system sensors used in sequences of operation or being monitored as part of FDD functionality as well as for all building sensors with industry-established accuracy or drift issues including relative humidity sensors, CO2 sensors, and air or water flow sensors.

� Signal Tuning Needs: monitor all HVAC system analog and floating output commands and using configurable thresholds automatically notify when persistent signal output issues including hunting, overshooting, over dampening, wind-up, or improper loop enabling has been identified.

� High Minimum Setpoints: automatically notify when excessive ventilation, reheat, or variable speed motor commands occur for any HVAC system relative during low load conditions as defined by outside air temperatures or occupancy levels.

� Restricted Setpoint Reset: automatically notify when all HVAC setpoint resets including those used for pressure, temperature, and flow setpoints are persistently limited by rouge zone or are otherwise unresponsive to overall load condition changes. Provide an energy cost penalty estimate and associated priority for each fault.

� Unoccupied Runtimes and Enable Issues: Use meter, submeter, or BCS data to automatically notify when building systems are operating during periods where buildings are unoccupied such as for federal holidays, training days, nights, weekends, or other periods when building-level occupancy data shows no people present. This fault must not be triggered during warm-up or cool-down sequences of operation unless these sequences result in consecutive days when warm-up or cool-downs cause equipment enable times that undershoot setpoints by a configured amount or reach setpoint prior to occupied times by a configurable amount of time. Provide an energy cost penalty estimate and associated priority for each fault.

� High Pressure Drops: for all HVAC filters, recovery wheels, and strainers, provide automated notifications to TAFB CES when measured pressure drops exceed configured thresholds for a prolonged period. Provide an energy cost penalty estimate and associated priority for each fault.

� Electrical Power Demand Limiting: notify specific CE staff responsible for UMCS management when periods of demand reduction are expected within the next 24-48 hours based on weather service data including projected temperatures approaches or exceeding 1% design conditions and hurricane or other severe storm watch conditions. Notifications must include recommended actions including specific non-critical electrical circuits to disable, specific air handling unit ventilation rates to adjust based on live or calculated occupancy usage factors, and specific building or zone-level temperature setpoints to adjust.

� Additional FDD Features: provide additional notifications for start-up reports, end-of-day reports, and equipment trip conditions reports for specific TAFB CES staff managing specific buildings and buildings systems. For user-specific dashboards, provide prioritized tables of O&M tasks required from FDD faults and visualization for alarm/fault counts, normalized smoothed performance profiles, and aggregated equipment operation data for specific buildings sets.

1.4.1.2.3. Outcomes

� Decrease energy usage.

� Improved building equipment performance.

� Reduced work order requests and tenant complaints.

� Improved capital equipment lifespan.

� Improved insight into building equipment performance.

1.4.1.2.4. Capabilities

� Deploy Fault Detection and Diagnostics (FDD) to improve operational efficiency.

� Use information from BCS and energy data to proactively schedule maintenance efforts.

� Provide ongoing commissioning to help maintain building performance.

� Customizable and user-configured fault conditions and visualization options

1.4.1.3. Kiosks

The Contractor is responsible for providing kiosks strategically placed in the building allow occupants to engage with their buildings and take action within their areas of responsibility to positively affect building operations. These devices, however, can display a multitude of possible BCS, FRCS, UMCS or other building data and without proper configuration and operation these devices may become burdened by communication errors and display no meaningful data. The following descriptions are intended to help promote the former.

1.4.1.3.1. Description

Kiosks must rely on BCS-level communication, with a waiver granted by the contracting officer if other communication is required. Where kiosks connect at the BACnet field network, these devices must be classified as Local Display Panels (LDPs) and meet all related specification requirements. Where kiosks are provided as tablet machines, these devices must meet the BCS/UMCS workstation requirements in this document. Regardless of device type, create design Points Schedules following the format of UFC 3- 410-02 - DDC for HVAC and other Building Control Systems.

Kiosks must either be touch-screen, navigable via menu buttons, or configured to share slideshows of user-specific data. Contractor must provide licensed configuration software to ensure long-term capability for TAFB O&M. Install all kiosks at a height of 48” or 60” from the finished floor.

Kiosks displays must include the following minimum data:

� Energy and water usage with related costs: this month, previous month, and previous year with peer group comparisons

� Electric demand information, weather status and minimum 3-day projections, and demand reduction status

� TAFB CES logo, description, and contact info � Pre-defined but selectable best practices for user navigation or auto slideshow during period of inactivity

1.4.1.3.2. Applicability and Data Output

All buildings must include kiosk functionality with the following criteria:

� For offices, provide kiosks within 20 feet of main entrance but not in vestibules.

For other facility types, locate kiosks in common areas

� For buildings with multiple floors, provide additional kiosks within 20 feet of each floor’s elevator area

� For lodging buildings, kiosks must be provided in common areas for each floor or for each separate organizational area of responsibility (whichever is larger)

� Computer kiosks must be a minimum resolution of with 1920 x 1080; LDP kiosks must be a minimum 32-inch diagonal display

� Kiosks may be location on walls or standing � Show kiosk locations on plans � All kiosks must be endurance tested to show no communication drop-out prior to acceptance

1.4.1.3.3. Outcomes

� Promote and inspire - Enhance the story of your building’s performance and green features by communicating the unique story of energy efficiency technologies employed by your facility

� Engagement - Create a dynamic and interactive experience that engages occupants and fosters collaboration through real-time energy and water use reduction comparisons

� Educate - Provide insight into how electricity is billed, spent, and consumed, as well as provide green tips on how to conserve

� Inform - Improve the dissemination of information by including convenient, current, and accurate information via announcements, notifications, events, etc.

1.4.1.4. Hydronic and Gas Leak Detection

Water and gas leaking are a primary concern for any installation and can cause harm to occupants and buildings if not fixed in a timely manner. Leak detection sensors will integrate into Siemens Desigo through the Siemens Apogee BCS/UMCS system.

1.4.1.4.1. Description

Hydronic and gas leak detection must be a quick alarm to operations center personnel of a potential leak in a building. It must provide an alarm to maintenance personnel of any leaks in the building before visible indicators have appeared.

1.4.1.4.2. Applicability and Data Output

� Alarming and notifications sent to the proper personnel depending on type of leak.

� Personnel notification and alarming must be customizable by a control system administrator.

1.4.1.4.3. Outcomes

� Real-time data of water and natural gas for buildings to determine if there is a leakage available at the operations level.

� Allow building maintenance to respond before extensive damage or potential occupant harm has occurred.

1.4.1.4.4. Capabilities

� Provide CES with alarm of leaking before visual indicators for quick response.

� Prevent damage to buildings and facilities with early warning system.

� Provide data and alerts to deploy repair efforts quickly and efficiently.

1.4.1.5. Moisture Detection

The installation is located in ASHRAE Zone 2A, which has a high risk of mold growth based on humidity from outside air. Mold in buildings has the potential to cause a lot of damage and extensive repair, particularly in the installation’s climate. Moisture detection sensors will integrate into Siemens Desigo through the Siemens Apogee BCS/UMCS system.

1.4.1.5.1. Description

Provide a system that monitors humidity conditions in conditioned and unconditioned area, and alert when conditions in the space could begin to grow mold.

1.4.1.5.2. Applicability and Data Output

� Alarming and notifications sent to the proper personnel.

� Personnel notification and alarming must be customizable by a control system administrator.

1.4.1.5.3. Outcomes

� Give maintenance the ability to act before mold begins to grow.

� Provide guidance on where mold may begin to grow

1.4.1.5.4. Capabilities

� Alert operations of mold conditions, before mold begins to grow.

� Provide a general location of mold conditions in a building.

� Provide data visualization for constant monitoring by operations and maintenance.

1.4.1.6. Occupancy Analysis

The Air Force does a yearly space management study, where teams perform assessments on how buildings are utilized. This process takes a significant amount of time; and automating the process will save time and resources. The ability to do an occupancy analysis will also allow for demand control ventilation for the HVAC system, and scheduling for the lighting system. The Contractor will utilize the Siemens’ Total Room Automation (TRA) solution and the KNX open protocol room bus to provide occupancy data for analysis and integration. The contractor programming controllers on this system must be licensed by Siemens. All TRA solutions will integrate into Siemens Desigo through the Siemens Apogee BCS/UMCS system. The contractor programming Desigo must be licensed by Siemens.

1.4.1.6.1. Description

The occupancy analysis must provide data of the true utilization of office buildings, conference centers, auditorium, and any other administration space. Spaces include offices, desk areas, conference rooms, and other places where people congregate and work.

Provide an occupancy analysis floor plan graphical representation, and exportable report displaying the occupancy analysis of any single building, breaking down by the space.

Space utilization metrics must be customizable by the user, allowing them to run the report when requirements change.

The occupancy sensors must be integrated into the building automation system. The HVAC system can use the data to have demand-controlled ventilation with the system.

The lighting control system must be able to use the data as well for scheduling purposes.

Provide data visualization for individual spaces for maintenance to compare the scheduling of the building with the occupancy.

1.4.1.6.2. Applicability and Data Output

� Individual offices spaces can use a binary sensor.

� Offices spaces (such as “cube farms”) must have a total count of people occupying the space by occupancy “zones”.

� Spaces that have a designed occupancy density of 25 people/1000 ft2 and greater than 500 ft2 of conditioned floor space, such as conference rooms and auditoriums, must have a total count of people occupying the space.

� An output of the control system is a metric of people/1000 ft2 � All occupancy data requires data visualization on individual rooms showing an occupancy analysis of when throughout the day the office is occupied � Only binary sensors without photographic capabilities can be used in secure designated spaces.

1.4.1.6.3. Outcomes

� Increased situational awareness of building utilization.

� Provide the Air Force of occupancy metrics, allowing the metric to be changed if required.

� Provide related FRCS with data for increased performance and energy saving measures.

1.4.1.6.4. Capabilities

� The system must not use personally identifiable information (PII) as a part of the analysis.

� Provide the installation the ability to do occupancy analysis on a consistent basis;

and have the ability to provide an occupancy analysis dashboard and report with customizable metrics.

� Graphically represented analysis on the EMCS and at the operations center.

� Customizable report generation for communication.

� Inform scheduling and operations of HVAC, lighting, and any other control system that could schedule based on occupancy.