Smart Building Specificationbedrockstandards.com/wp-content/uploads/2017/01/...resource file for the device. For each BACnet device, the device supplier must provide a PICS document

Smart Building Specification

Revised January 1, 2017

TABLE OF CONTENTS PROCESS SUMMARY …...………………………………………….……………………………..………...1 INSTALLER AND INTEGRATOR SCOPE (REV. 1.0, 1/1/2017) .................................................... 2 FIELD CONTROL SYSTEM (FCS) (REV. 2.2, 1/1/17) ............................................................. 10 LIGHTING (REV. 2.1, 10/23/14) ........................................................................................ 18 PANEL, WIRING, AND INSTALLATION STANDARDS (REV. 3.5, 1/1/17) ................................... 14 FIRE SYSTEMS MONITORING (REV. 1.3, 1/1/2017) ............................................................. 18 GENERATOR MONITORING ................................................................................................ 21 ELECTRICAL AND SUB METERING (REV. 4.6, 1/1/17) ........................................................... 22 LIFTING DEVICES (REV. 2.1, 10/23/14) ............................................................................. 26 POINT TAGGING CONVENTIONS ......................................................................................... 27

Process Summary

1. Bedrock Smart Building Specification must be reviewed prior to writing or releasing specifications for any project and be referenced in engineered drawings of record. All engineers/architects and relevant trades must receive this document for review as soon as possible. Any unapproved variation from this document will not be accepted.

2. Bedrock Engineering and Integration teams must be contacted and alerted of all upcoming

projects and included in every phase of the design and construction process.

3. “Specification Integration Checklist” must be completed by the assigned Engineer/Architect and submitted to Bedrock Detroit Integration Team. Attached with the checklist must be all project specifications and drawings. This must take place prior to any release of design/bid drawings. The integration checklist must obtain signed approval by a representative of Bedrock prior to release of any specifications and design/bid/permit drawings.

4. “Integration Checklist” and “Electrical Metering Checklist” must be completed and submitted to Bedrock Detroit for all projects. This document must have signed approval by a representative of Bedrock prior to any work being performed.

5. Each unique piece of equipment must have its own “Integration Checklist” form. Include all serial numbers with equipment description and location on a separate sheet if sufficient room is not provided.

6. Accurate cut sheets, point mapping/schedules, and shop drawings are mandatory and must be received prior to build and approved by a Bedrock representative. Detailed network drawings are also mandatory. Accurate ‘As-Builts’ must be submitted in all closeout packages.

7. Any changes to the items listed above after receiving initial approval (i.e. tenant improvement, value engineering, etc.) must receive written approval by the Bedrock representative who originally approved before any changes are to be released.

8. A minimum monthly meeting including Temperature Control Contractor, Master Integrator, and Bedrock Controls team is mandatory for all projects.

INSTALLER AND INTEGRATOR SCOPE (REV. 1.0, 1/1/2017)

SUMMARY The following defines the responsibilities of the installing contractors and the Master Integrator on all projects of all sizes involving integrated systems. These are the minimum required responsibilities and projects will not be accepted until contractor meets the minimum portion of the scope as listed.

Installing Contractor Scope:

1. Provide completed integration checklists and detailed project submittals to Bedrock Detroit Controls Team and Integration Contractor for review and approval.

a. Controls and related peripherals must not begin to be installed until Integration Checklists and submittals are approved by Bedrock Controls Team and Master Integrator.

2. Install systems and control panels as designed, specified and approved by project engineer and Bedrock Controls Team.

3. Provide cabling/wiring, add devices into existing network, and/or home-run devices to identified demark and/or JACE location.

4. Provide JACE level integration (Device and point discovery, naming, etc.) 5. Structure JACE architecture to match Bedrock Standard (Ref. Appendix A). 6. Confirm proper communication and operation of all devices and points. 7. Tag all points as per Haystack Tagging Conventions. 8. Provide complete and accurate as-built/close-out documentation.

** Note: If installer does not have qualified/certified personnel on staff to perform any items 3-7, they must have Master Integrator or Temperature Control Contractor complete. If Temperature Control

Contractor is installing the designated JACE panel as part of their scope of work, they shall be the responsible party for JACE level integration.**

Master Integrator Scope:

1. Review Integration Checklist’s as provided by installing contractor. Provide IP addresses, device addresses and instance ID’s, and username/password for JACE integration.

2. Where JACE is contractor-provided, confirm proper driver set and licensing has been ordered and available on JACE. Confirm JACE is licensed “Open”.

3. Configure Server connections to JACE and directly integrated devices. 4. Verify proper network and demark location following standards and utilizing proper protocols. 5. Verify each piece of integrated equipment has been integrated to the specified JACE controller. 6. Verify all points have been integrated with all required points and tagged properly. 7. Verify JACE structure matches Bedrock Standard. 8. Test all equipment and points for read/write capability. 9. Eliminate any standalone schedules. 10. Provide Graphical Interface. 11. Provide Alarm logic, dashboards, and communication following “Alarming Standards” as listed

in Section 1.7 of this document. 12. Provide Trending and Historical Records as per Section 1.4 in this document. 13. Configure required system scheduling, including standard Bedrock Detroit portfolio-wide

schedules and local tenant schedules. 14. Provide user access as required by Bedrock Detroit. 15. Verify close-out documentation and provide as accessible files via Bedrock Integration platform

and shared on a “cloud-hosted” server.

Note: Any deficiencies identified must be documented via RFI or the GC/Constructor’s requested method of communication and provided to Bedrock Detroit Controls Team.

Note: Minimum monthly meeting between Bedrock Controls Team, Installing Contractor, and Master

Integrator is required on all projects.

FACILITY MANAGEMENT CONTROL SYSTEM (FMCS) (REV. 2.3, 1/1/17)

SUMMARY

A. Furnish all labor, materials, equipment, and service necessary for a complete and operating Temperature Control System (TCS) and Facility Management system (FMCS), utilizing Direct Digital Controls as shown on the drawings and as described herein. Drawings are diagrammatic only.

B. All labor, material, equipment and software not specifically referred to herein or on the plans, that is required to meet the functional intent of this specification, shall be provided without additional cost to the Owner.

C. The contractor shall provide a unique username and password on all installed devices for Bedrock Detroit Controls Team with “Superuser” or unlimited/unrestricted access.

D. Bedrock Detroit shall be the named license holder of all software associated with any and all incremental work on the project(s). All configuration software must be included as a leave-behind tool with enough license capability to support the installation plus 10%.

SYSTEM DESCRIPTION

REFER TO APPENDIX A FOR SYSTEM ARCHITECTURE REPRESENTATION

The entire Temperature Control System (TCS) shall be comprised of a network of interoperable, stand-alone digital controllers communicating via BACnet™ communication protocols to a Network Area Controller (NAC). Temperature Control System products shall be by approved manufacturers.

The Facility Management and Control System (FMCS) shall be comprised of Network Area Controller or Controllers (NAC) within each facility. The NAC shall connect to the local Smart Building Network or. Access to the system, either locally in each building, or remotely from a central site or sites, shall be accomplished through standard Web browsers, and Apple IPAD, via the Internet and/or local area network. Each NAC shall communicate to LonMark™/LonTalk™ (IDC) and/or BACnet™ (IBC) controllers and other open protocol systems/devices provided under Division 15 or Division 16.

The FMCS shall provide automated alarming software capable of sending messages to email compatible cellular telephones and pagers via the owner’s e-mail service. The email alarm paging system shall be able to segregate users, time schedules, and equipment, and be capable of being programmed by the owner.

A. It is preferable that any dedicated configuration tool required for controller configuration have the capability to be launched from within the applicable Network Management Software. If the configuration tool(s) cannot be launched from the Network Management Software, any software required for controller configuration shall be included as a leave-behind tool with enough license capability to support the installation + 10%.

B. The contractor shall provide the appropriate quantity of legal copies of all software tools, configuration tools, management tools, and utilities used during system commissioning and installation. All tools shall be generally available in the market. No closed and/or unavailable tools will be permitted. Contractor shall convey all software tools and their legal licenses at project close out.

PREAPPROVED MANUFACTURERS

A. Basis-of-Design: Tridium Niagara J600 AXTM. Subject to compliance with requirements, provide either the product named or an alternate product by one of the other manufacturers specified.

1. Vykon 2. Johnson Controls 3. Honeywell

OPEN, INTEROPERABLE, INTEGRATED ARCHITECTURES

A. The intent of this specification is to provide a peer-to-peer networked, stand-alone, distributed control system with the capability to integrate ANSI/ASHRAE Standard 135-2001 BACnet™, LonWorks™ technology, MODBUS ™, OPC, and other open and proprietary communication protocols into one open, interoperable system.

B. The supplied computer software shall employ object-oriented technology (OOT) for

representation of all data and control devices within the system. In addition, adherence to industry standards including ANSI / ASHRAE™ Standard 135-2001, BACnet and LonMark to assure interoperability between all system components is required. For each LonWorks device that does not have LonMark certification, the device supplier must provide an XIF file and a resource file for the device. For each BACnet device, the device supplier must provide a PICS document showing the installed device’s compliance level. Minimum compliance is Level 3; with the ability to support data read and write functionality.

C. BACnet devices shall be via Ethernet (BACnet Ethernet/IP,) and/or RS-485 (BACnet MSTP) as

specified.

D. All components and controllers supplied under this Division shall be true “peer-to-peer” communicating devices. Components or controllers requiring “polling” by a host to pass data shall not be acceptable.

E. The supplied system must incorporate the ability to access all data using standard Web

browsers and Smart Devices (Apple iPad, Samsung Galaxy, etc.) without requiring proprietary operator interface and configuration programs. Systems requiring proprietary database and user interface programs shall not be acceptable.

F. A hierarchical topology is required to assure reasonable system response times and to manage

the flow and sharing of data without unduly burdening the customer’s internal Intranet network. Systems employing a “flat” single tiered architecture shall not be acceptable.

1. Maximum acceptable response time from any alarm occurrence (at the point of

origin) to the point of annunciation shall not exceed 5 seconds for local network connected user interfaces.

2. Maximum acceptable response time from any alarm occurrence (at the point of origin) to the point of annunciation shall not exceed 60 seconds for remote or dial-up connected user interfaces.

G. The Network Area Controller (NAC) shall provide the interface between the LAN or WAN and the

field control devices, and provide global supervisory control functions over the control devices connected to the NAC. It shall be capable of executing application control programs to provide:

1. Calendar functions

2. Scheduling

3. Trending

4. Alarm monitoring and routing

5. Time synchronization

6. Integration of LonWorks controller data and BACnet controller data

7. Network Management functions for all LonWorks and/or BACnet based devices

H. The Network Area Controller shall provide the following hardware and driver features as a minimum:

1. One Ethernet Port – 10/100 Mbps

2. One RS-232 port

3. One LonWorks Interface Port – 78KB FTT-10A with Lon Driver.

4. One RS-485 port with BACnet MS/TP Driver.

5. Battery Backup

6. Flash memory for long term data backup (If battery backup or flash memory is not supplied, the controller must contain a hard disk with at least 1 gigabyte storage capacity)

7. Where the option for expanded memory is available for the NAC, it must be supplied.

8. Power module must be a 24VAC or DC with 34 point of input or output.

NETWORKS

A. The Local Area Network (LAN) shall be a 100 Megabit/sec Ethernet network supporting BACnet, Java, XML, HTTP, and SOAP for maximum flexibility for integration of building data with enterprise information systems and providing support for multiple Network Area Controllers (NACs), user workstations and, if specified, a local server.

B. Local area network minimum physical and media access requirements:

1. Ethernet; IEEE standard 802.3

2. Cable; 100 Base-T, UTP-8 wire, category 5

3. Minimum throughput; 100 Mbps

TRENDING STANDARDS

A. All physical points with the system are to be setup with a history and to use the following variables:

Analog Inputs

POINT TYPE HISTORY SETTING COV TOLERANCE

SAMPLE PERIOD

Temperature Input COV (Change of Value) 0.5 of °F N/A

Humidity Input COV (Change of Value) 1.0 % Humidity N/A

Setpoint Adjust Input COV (Change of Value) 0.5 of °F N/A

Voltage Input COV (Change of Value) 0.2 N/A

Volume Input COV (Change of Value) 0.2 N/A

Analog Variables


SAMPLE PERIOD

Temperature Setpoint Variable

COV (Change of Value) 0.5 of °F N/A

Humidity Setpoint Variable

COV (Change of Value) 1.0 % Humidity N/A

Analog Outputs


SAMPLE PERIOD

0-100 Modulated Point Sample Period N/A Every 5 min

Digital Inputs


SAMPLE PERIOD

Digital Input COV (Change of Value) Change of State N/A

Digital Outputs


SAMPLE PERIOD

Digital Output COV (Change of Value) Change of State N/A

ALARMING STANDARDS (Revised 1/1/2017)

A. Minimum standards for alarming are as follows. All alarms must have a clear description, including equipment name, location, and alarm sequence. For alarms to have emails generated, the description of the alarm must also include equipment name, location, sequence for alarm to occur, and priority level of the alarm. Alarm notifications shall only send when event becomes active or after a time delay, if applicable. A Bedrock Controls Team representative must sign off on all alarming procedures not included in this specification before alarming is to be implemented:

A. Alarm Classifications

HVAC Alarms: HVAC Alarms must be classified into 4 subcategories/priority levels:

1. FDD Alarm – This alarm is non-harmful to building patrons and the building envelope, but is alarmed to notify of equipment inefficiencies that may cause energy inefficiencies.

2. Level 3 HVAC Alarm – This alarm is non-harmful to building patrons and/or the building envelope, but is alarmed to notify of equipment inefficiencies that may cause tenant/patron discomfort.

3. Level 2 HVAC Alarm – This alarm is non-harmful to building patrons and/or the building envelope, but is alarmed to notify of equipment inefficiencies that may cause tenant/patron discomfort. These are alarmed points for major mechanical equipment only.

4. Level 1 Critical HVAC Alarm – This alarm is mostly non-harmful to building patrons, but can have severe impact to building operations.

Infrastructure Alarm: These alarms are generated by miscellaneous sensors and devices that will alert based on a condition that may be harmful to the building structure or occupants. Examples are water detection, sump failure, etc. loss of communication to a piece of equipment of device.

Communication Alarm: These alarms are generated by a loss of communication to a controller, a device, or JACE.

Fire Alarms: These are alarms are generated from Fire System integration and require immediate response from building personnel.

Generator Alarms: These are alarms generated from Generator integration and require immediate response from building personnel.

B. Point Alarming Standards

Status Alarming – A status failure alarm must be associated with the start stop command of the device status. All device status alarms must have a 5-minute delay from the original alarm state enable to the alarm notification time.

Off Setpoint Alarming – Off Setpoint alarms are associated with a room or unit setpoint and alarm when the parent value is + or – 5% off its associated setpoint. All Off Setpoint alarms must have a 10-minute delay from the original alarm state enable to the alarm notification time.

Communication Alarming – All communication alarms must have a 10-minute delay from the original loss of controller heart beat to the alarm notification time.

Low/High Value Alarming - Low/High Value alarms are associated with an analog value that has upper and or lower fixed limits. All Low/High Value alarms must have a 10-minute delay from the original alarm state enable to the alarm notification time.

Off Normal Alarming – Off Normal alarms are associated with a monitored Boolean value that stays in a normal state until triggered to create an off normal alarm.

C. Equipment Alarming Standards

-The following items are only the minimum alarming required and not all inclusive. Chillers Point Name Alarm Type Class

Chiller Alarm Off Normal Level 1 Critical HVAC

Chilled & Condenser Water Pump Status/Drive Failure

Status Level 1 Critical HVAC

Chilled & Condenser Water DP Low Off Setpoint Level 2 HVAC

Chilled Water LWT High Off Setpoint Level 2 HVAC

Boilers/Hot Water Systems Point Name Alarm Type Class

Boiler Alarm Off Normal Level 1 Critical HVAC

Emergency Stop Status Level 1 Critical HVAC

Hot Water Pump Status/Drive Failure Status Level 1 Critical HVAC

Hot Water Temperature High Off Setpoint Level 1 Critical HVAC

Hot Water Temperature Low Off Setpoint Level 2 HVAC

Hot Water DP Low Off Setpoint Level 2 HVAC

Cooling Towers/Glycol Fluid Coolers Point Name Alarm Type Class

Fan Failure Status Level 1 Critical HVAC

Distribution Pump Failure Status Level 1 Critical HVAC

Spray Pump Failure Status Level 1 Critical HVAC

Low Basin Temperature Low/High Value Level 1 Critical HVAC

Low/High Basin Fluid Level Off Normal Level 2 HVAC

Glycol Basin Low Alarm Off Normal Level 2 HVAC

Loop Differential Pressure Low Off Setpoint Level 2 HVAC

Major Air Handling Equipment (AHU, VFMU, ERV, MAU, etc.) Point Name Alarm Type Class

Fan Failure (Supply, Return, Exhaust, etc.) Status Level 1 Critical HVAC

Limit Switch Trip (High Static, Low Static, Freeze Stat, etc.)

Off Normal Level 1 Critical HVAC

General Alarm Off Normal Level 2 HVAC

DX Cooling Stage Failure Status Level 2 HVAC

Filter Differential Pressure High Low/High Value Level 2 HVAC

Discharge Air Pressure Low Off Setpoint Level 3 HVAC

Discharge Air Temp High/Low Off Setpoint Level 3 HVAC

CO2 High Off Setpoint Level 3 HVAC

VRV/VRF Systems Point Name Alarm Type Class

General Alarm (Condensing Unit Level) Off Normal Level 1 HVAC

Zone-Level Equipment (VAV, FPB/TU, FCU, etc.) Point Name Alarm Type Class

Fan Failure Status Level 3 HVAC

Zone Temperature Alarm (+/- 2 Deg.) Off Setpoint FDD

Critical Zone/VIP Temperature Alarm (+/- 2 Deg.)

Off Setpoint Level 2 HVAC

Infrastructure Alarms Point Name Alarm Type Class

Water/Leak Detection Off Normal Infrastructure

Sump Failure Off Normal Infrastructure

Domestic Water Pump Failure/General Alarm Off Normal Infrastructure

Communication Alarms Point Name Alarm Type Class

Device/Controller Status FDD

JACE Status Communication Level 1

Alarm Type Class Email Enabled

Personnel That Receives Email

HVAC Level 1 Yes LE, BE, CT

HVAC Level 2 Yes LE, BE, CT

HVAC Level 3 No N/A

HVAC FDD No N/A

Infrastructure Yes EM, LE, BE, CT, DBS, DT, RSCC, PM, APM

Communication Level 1 Yes CT, DBS

Communication FDD No N/A

Fire Yes EM, LE, BE, CT, DBS, DT, RSCC, PM, APM

Generator Yes EM, LE, BE, CT, DT, RSCC, PM, APM

****EM = Engineering Manager, LE = Lead Engineer, BE = Building Engineer, CT = Controls Team, DBS = Director of Building Systems, DT = Director of Triage, RSCC = Rock Security

Command Center, PM = Property Manager, APM = Assistant Property Manager.****

FIELD CONTROL SYSTEM (FCS) (REV. 2.2, 1/1/17) ADVANCED UNITARY CONTROLLER The controller platform shall be designed specifically to control HVAC ventilation, filtration, heating, cooling, humidification, and distribution. Equipment includes: constant volume air handlers, VAV air handlers, packaged RTU, heat pumps, unit vents, fan coils, natural convection units, and radiant panels. The controller platform shall provide options and advanced system functions, programmable and configurable using Niagara AX Framework™, that allow standard and customizable control solutions required in executing the “Sequence of Operation” as outlined in Section 4. Unitary control of individual offices and boardrooms are to have dedicated zone control with an adjustable thermostat with display that is like kind and quality to a JCI – NS-BTB7003-0. Preapproved Manufacturers:

1. Johnson Controls Facility Explorer Minimum Requirements:

1. The controller shall be fully programmable with full functionality on any Niagara AX brand platform a. Support downloads to the controller from any brand of Niagara AX platform b. Support uploads from the controller to any brand of Niagara AX platform c. Support simulation/debug mode of the controller d. Maintain native GUI e. Native function-block programming within the Niagara AX environment f. Manufacturer programmed and installed controllers that meet the following:

a. Designed specifically for the piece of equipment that it will be controlling. b. Factory installed. c. Bedrock Director of Building Systems or VP of Engineering approval. d. Meets all other requirements established in this section.

2. The controller shall be capable of either integrating with other devices or stand-alone operation

3. The controller shall have sufficient on-board inputs and outputs to support the application

a. Analog outputs (AO) shall be capable of being configured to support 0-10 V, 2-10 V, or 4-20

mA devices

b. Analog outputs (AO) shall be capable of being configured to support 0-10 V, 2-10 V, or 4-20 mA devices

c. Triac outputs shall be capable of switching 30 Volts at 500 mA.

d. Input and Output wiring terminal strips shall be removable from the controller without

disconnecting wiring. Input and Output wiring terminals shall be designated with color coded labels.

e. Universal inputs shall be capable of being configured as binary inputs, resistive inputs,

voltage inputs (0-10 VDC), or current inputs (4-20 mA).

4. The controller shall provide “continuous” automated loop tuning with an Adaptive Integral Algorithm Control Loop.

5. The controller platform shall have standard HVAC application programs that are modifiable to

support both the traditional and specialized “sequence of operations”

6. The controller should be installed with enough points available to have 10% extra at completion of the installation for future expansion. Example a controller was installed with a total of 34 hardwired points, there must be a minimum 4 points available at the end of the installation.

VARIABLE AIR VOLUME CONTROLLER The controller platform shall be designed specifically for room-level VAV control – pressure independent air flow control, pressure dependent damper control, supply and exhaust pressurization/ de-pressurization control; temperature, humidity, complex CO2, occupancy, and emergency control. Equipment includes: VAV terminal unit, VAV terminal unit with reheat, Series fan powered terminal unit, Parallel fan powered terminal unit, Supply and Exhaust air volume terminals, and Constant volume dual-duct terminal unit. The controller platform shall provide options and advanced system functions, programmable and configurable using Niagara AX Framework™, that allow standard and customizable control solutions. Preapproved Manufacturers:

1. KMC Controls 2. Johnson Controls Facility Explorer 3. Vykon Dealership Level

Minimum Requirements: 1. The controller shall be fully programmable with full functionality on any Niagara AX brand platform.

a. Support downloads to the controller from any brand of Niagara AX platform

b. Support uploads form the controller to any brand of Niagara AX platform

c. Support simulation debug mode of the controller

d. Maintain native GUI

e. Native function-block programming within the Niagara AX environment

f. Manufacturer VAV controllers will not be acceptable without approval from Bedrock Director of Building Systems or VP of Engineering.

2. The controller shall be capable of either integrating with other devices or standalone room-level control operation. 3. The controller shall have sufficient on-board inputs and outputs to support the application.

a. Analog outputs (AO) shall be capable of being configured to support 0-10 V, 2-10 V or 4-20 mA devices.

b. Triac outputs shall be capable of switching 30 Volts at 500 mA c. Input and Output wiring terminal strips shall be removable from the controller without

disconnecting wiring. Input and Output wiring terminals shall be designated with color coded labels

d. Universal inputs shall be capable of being configured as binary inputs, resistive inputs, voltage inputs (0-10 VDC), or current inputs (4-20mA)

4. The controller shall provide continuous automated loop tuning with an Adaptive Integral Algorithm Control Loop. 5. The controller shall have a loop execution response time of 1 second.

a. The controller platform shall have standard HVAC application programs that are modifiable to support both the traditional and specialized “sequence of operations”

REMOTE & EXPANDED I/0 The controller platform shall be designed specifically for the Tridium Niagara Platform. The controller platform shall provide options and advanced system functions, programmable and configurable using Niagara AX Framework™, that allow standard and customizable control solutions. These types of devices must not be utilized as the sole controlling device on major/critical pieces of HVAC equipment (AHUs, VAVs, MAUs, etc.). Minimum Requirements:

1. The controller shall be fully configurable with full functionality on any Niagara AX brand platform a. Support downloads to the controller from any brand of Niagara AX platform b. Support uploads from the controller to any brand of Niagara AX platform c. Support simulation/debug mode of the controller

d. Acceptable expanded I/O communications are:

- Bacnet IP or MS/TP - RDIO RS-485.

e. The Expanded I/O should be installed with enough points available to have 10% extra at

completion of the installation for future expansion. Example a Expanded I/O was installed with a total of 34 hardwired points, there must be a minimum 4 points available at the end of the installation.

VARIABLE FREQUENCY DRIVES

1. The selected VFD (Variable Frequency Drive) should have the ability for read & write integration using one of the following protocols. If one of the following protocols is not available on an existing VFD hard wired monitor & controlling points must be supplied. - BACnet IP - BACnet MS/TP An integration information document is to be completed and supplied with the initial submittal documents for approval.

Minimum Requirements: 2. The VFD shall be fully configurable through a password protected user interface.

a. The VFD must be started and verified by a factory representative.

b. Full startup documentation is to be supplied to Bedrock in an electronic format. c. Preapproved brands are limited to ABB and Schneider Electric. Any alternate must be

approved by engineer of record and Bedrock Controls Team/Director of Building Systems and VP of Engineering.

NETWORK/JACE STRUCTURE (NEW, 1/1/17)

DEMARK/TERMINATION LOCATIONS (Ref. Appendix A)

A. RS-232/485 Communication (Ex. BACNet MS/TP, Modbus RTU, etc.) - All RS232/485 Communication shall be routed directly to a port on the Jace.

Exceptions are for communication buses that are terminated on a conversion-type router.

B. LON FT-10 Communication

- All LON FT-10 Communication shall be routed directly to a port on the Jace.

C. IP/TCP/Ethernet Communication - All communication over IP/TCP/Ethernet shall be terminated at the designated

Bedrock network switch. - If an IP device is located inside a Jace panel, the managed switch inside the Jace panel

may be used.

D. EMON Meters - EMON meters must be on a separate, dedicated communication bus.

JACE Structure (Ref. Appendix A)

A. All programming logic shall be contained in folders and located in a folder named “Programming” under “Config”. - Wire Sheet programming must not be located at the individual device.

B. All Writable Variables that control NDIO points shall be located in a folder

named “Variables” under “NDIO Network”.

PANEL, WIRING, AND INSTALLATION STANDARDS (REV. 3.5, 1/1/17)

SECTION 1 – Panel Requirements JACE/Demark/Custom Control Panels Panels not matching the preapproved part numbers listed in this specification must have complete submittal including all internal components, drawing of internal panel layout, and proof of UL listing. All documentation must be submitted and obtain written approval from Bedrock Director of Building Systems prior to installation and acceptance. Any variance from this process will result in panel not being accepted. All Panels must be UL508A Rated and Approved. See Appendix B for preapproved layout drawing. PREAPPROVED PANELS AVAILABLE FROM: COCHRANE SUPPLY (HTTP://WWW.COCHRANESUPPLY.COM) THE PANEL SHOPPE (HTTP://THEPANELSHOPPE.COM) JACE Panel PART NO: BRMGT-3624-P-N3-J6-DA-34T

• 36"x24"x6" Panel • 120Vac to 24Vac 100VA Transformer with Convenience Outlets / Additional 24Vac

Secondary Fusing / Terminal Strip • 5 Port Managed Network Switch / B&B Electronics Smart Worx ESW-508 / 1' Pink Patch

Cable • JACE-600E - Controller / 5' Pink Patch Cable • Drivers & Extras

o NPM-256MB - Memory Expansion License From 128MB to 256MB o NPB-LON - LON Option Card o DR-LONDRIV-AX - LONWorks Driver Over Twisted Pair FT10 Network o NPB-2X-RS485 - Dual Port RS-485 Option Card o DR-MSTP-AX - MS/TP BACNet Communications Via RS-485 Port o DR-BACNET-AX - BACNet IP Server & Client Driver Over Ethernet o DR-MDB-RTU-AX - Modbus RTU over RS-232 or RS-485 o DR-MDB-TCP-AX - Modbus TCP Over Ethernet

• IO-34 - 16 Universal Input / 10 Digital, 8 Analog Output Module With Input/Output Terminal Strip

Demark Panels/Custom Control Panels BRMGT-1816-P-N3-XT-XBACRX – Demark Panel


Secondary Fusing / Terminal Strip • 8 Port Managed Network Switch / 1' Pink Patch Cable • BACNet MS/TP to IP Router / / 1' Pink Patch Cable • LON/BACNet/MODBus Termination Terminal Strip (If Applicable)

http://www.cochranesupply.com/

http://thepanelshoppe.com/

Demark Panels/Custom Control Panels (Continued) BRMGT-2024-P-N3-XT-XBACRX – Demark Panel


Secondary Fusing / Terminal Strip • 8 Port Managed Network Switch / 1' Pink Patch Cable • BACNet MS/TP to IP Router / / 1' Pink Patch Cable • LON/BACNet/MODBus Termination Terminal Strip (If Applicable)

Bare Panels: BRMGT-1816-P - 18"x16"x6" Bare Panel with 120Vac to 24Vac 100VA Transformer with Convenience Outlets & 24Vac Terminal Strip

BRMGT-2024-P - 20"x24"x6" Bare Panel with 120Vac to 24Vac 100VA Transformer with Convenience Outlets & 24Vac Terminal Strip BRMGT-3624-P - 36"x24"x6" Bare Panel with 120Vac to 24Vac 100VA Transformer with Convenience Outlets & 24Vac Terminal Strip SECTION 2 – Installation Specifications

A. Conduit Installation • EMT Conduit fittings must be of steel set screw type.

• EMT Conduit must be run parallel to all building lines.

• EMT Conduit is to be used outside with steel rain tight fittings.

• PVC Conduit is NOT be used unless written approval from Bedrock is obtained.

• EMT Conduit is NOT to be connected directly to end devices.

• A junction and or pull box must be installed when bending EMT conduit and the

degrees bent equals 270°.

• Liquid Tight conduit must be used to connect to end devices. No more than 3 meters is allowable.

• ALL CONDUITS MUST BE INSTALLED ACCORDING TO LOCAL ELECTRICAL CODES AND REGULATIONS.

B. Free Wire Installation- • Wire must be run parallel to all building lines.

• Tie wraps must be used for the installation of free wire to ensure cable is not

sagging, and aid in the installation of parallel to building lines.

• Tie wraps must NOT be installed in a fashion that will pinch the cable and create a resistance in communication and signal loss.

• NO T-TAPS, STUBS, STARS, and SPURS of any length are allowed in

communication wiring.

• Always use point-to-point, daisy chain wiring. Including inside the panel cabinets.

• In noisy (High EMI) environments avoid wire runs parallel to noisy power cables, or

lines containing lighting and or dimmers switches. At least 12 inches of separation must be maintained between noisy lines and communication and signal cables.

• Strapping and or tie wrapping cable/wire to sprinkler pipe will not be accepted.

• All free wire must be installed in the attempt to be out of the sight of eye, and any

possible damaging situations.

C. Wire & Terminations- • NO T-TAPS, STUBS, STARS, and SPURS of any length are allowed in

communication wiring.

• Always use point-to-point, daisy chain wiring. Including inside the panel cabinets.

• Any transformer installed must be on a dedicated breaker within the panel.

• Panel label and breaker number must be written on the top left inside of the Building Automation Panel Cabinet in which it serves.

• All 120vac transformer and power connections are to be completed outside the

panel in a 6x6 junction box. This item is only bypassed if an integrated transformer, fuse, and plug unit is used.

• All 24vac transformer negative connections must be grounded at the terminal

block within the Building Automation Panel Cabinet in which it serves. • All wall mounted control devices shall be mounted with a low voltage ring.

Mounting direct to drywall with anchors is not acceptable.

D. WIRE SPECIFICATIONS: • All devices must use a 2 wire or 3 wire cable. If 4+ conductors are required, written

approval from Bedrock Project Manager and Bedrock Director of Building Systems must be granted prior to installation.

• All wire must be clearly labeled within 1/4” of the wire termination on both ends with

the object name provided. • Wire must be properly rated for application.

• Wire jacket must be factory colored and not dyed.

Ethernet • Pink Jacket

• Cat6 Solid Plenum Rated • Terminations must meet Cat6 UTP Standards

Ethernet Patch Cables

• Pink Jacket • Cat6 Stranded Plenum Rated • Terminations must meet Cat6 UTP Standards • Patch cable must be manufacturer tested and verified

AI (2 Wire Device) • Red - Positive (+) • Black - Negative (-) • 18 Gage Cable Required

AI (3 Wire Device) • Red - Positive (+) • Black - Negative (-) • White – Control Signal • 18 Gage Cable Required

AO (2 Wire Device) • Red - Positive (+) • Black - Negative (-) • 18 Gage Cable Required

AO (3 Wire Device) • Red – Positive (+) / Power • Black - Negative (-) • White - Control Signal (0-5, 0-10 Volts or 4-20 ma) • 18 Gage Cable Required

DO • Red Positive (12Vdc or 24Vac) • Black – Common • 18 Gage Cable Required

24Vac • Red or Blue – 24Vac • Black or Yellow – Common • 18 Gage Cable Required

BACnet • IP: Ref. “Ethernet” • MS/TP: Yellow Jacket • Red - Positive (+) • Black - Negative (-) • White – Shield/Ground • Drain – Twisted Together Wrapped Around Cable and Taped • 22 Gage Minimum Shield Cable Required • ** All BACNet cable must meet ASHRAE BACnet

Guidelines** Modbus • IP: Ref. “Ethernet”

• RTU: Green • Red - Positive (+) • Black - Negative (-) • White – Shield/Ground • Drain – Twisted Together Wrapped Around Cable and Taped • 22 Gage Minimum Shield Cable Required

LON • White with Orange Stripe or Solid Orange Jacket • White Blue (+) Blue (-) • 22 Gage Cable • ** All LON cable must meet Echelon guidelines**

Proprietary Communications

• White with Blue Stripe Jacket • Refer to manufacture specifications in regards to wire gauge,

numbers of conductors, and shielding requirements.

LIGHTING (REV. 2.2, 1/1/17)

SECTION 1 - Integration Requirements The selected lighting control system must have the ability for read and write integration using one of the following protocols while connecting to a standalone lighting panel.

- BACnet IP - BACnet MS/TP - LonWorks FT-10

Lighting Control Systems must provide native communication without the use of a 3rd party conversion device. Systems that require a standalone server will not be accepted. An integration information document is to be completed and supplied with the initial submittal documents for Bedrock approval.

C. Integration Control - Ability for individual zone control and scene selection of each lighting node. - Ability to see the status of each lighting node. - Signage requires addition of current transducer for status monitoring.

D. Integration Demark Requirements

- The selected integration protocol is to be demarked to the selected integration demark location within the facility by the installing contractor.

- The demark location termination shall be landed and terminated with protocol identified and applicable addressing information by the installing contractor.

E. Graphical Display – Completed by Master System Integrator

- Graphic s must represent a floor plan layout and display the known status of the lighting circuit.

- Graphics must allow for adjustment of a single circuit or grouping of lighting schedule to be adjusted.

- Graphics must allow for manual timed overrides of a single circuit or grouping of lighting.

F. System Programming Requirements - The selected lighting system is to have full modification capabilities through the

integration, including the modification of lighting zones and scenes. - If the above is non-compliant the system configuration tools are to be supplied to

Bedrock. - Configuration tools are to be updated across the enterprise portfolio to the latest

installed version when a new system is added to the portfolio. - The configuration software is to be installed Bedrock supplied Jump Box.

SECTION 2 – Light Up Detroit and Exterior Retail Signage The lighting control system shall be properly zoned for the individual and separate control of the perimeter lighting zones and any interior lightings zones. All retail signage must be controlled and integrated to Bedrock FCMS. Retail signage integration must include proof of status via CT Switch or Transmitter. Spaces that are deemed to be event spaces must have the preliminary design signed off by Bedrock Event Staff.

FIRE SYSTEMS MONITORING (REV. 1.3, 1/1/2017) SECTION 1 - Integration Requirements The selected and or existing fire monitoring system including fire pumps should have the ability for a read only integration using one of the following protocols. The only acceptable time for a Field Server to be used for Fire Integration is on pre-existing systems. New installations must be self discoverable and native Bacnet or Lon. If one of the following protocols is not available on an existing fire panel, hard wired monitor points or a compatible Field Server device must be supplied.

- BACnet IP - BACnet MS/TP - LonWorks FT-10 - Modbus RTU - Field Server

An integration information document is to be completed and supplied with the initial submittal documents for Bedrock approval.

A. Integration Control - Ability to monitor all available points through the integration. Monitor points should

include but not limited to the following:

B. Integration Demark Requirements - The selected integration protocol is to be demarked to the selected integration

demark location within the facility by the installing contractor. - The demark location termination shall be landed and terminated with protocol

identified and applicable addressing information by the installing contractor.

C. Graphical Display - Graphics must represent all available information in a fire panel format. - If the system is a addressable system a floor plan must be completed to represent

device location and device status. (Only applicable if Integration allows for it) - All points pertaining to this device must be trended with COV (Change of Value). - All points should be setup to alarm in an off-normal state and generate a high priority

e-mail. - Discovered and or hard wired monitor points should be, but not limited to the

following: o Fire Panel Fault o Fire Panel Short o Fire Panel Comm Fault o Fire Panel Eeprom Bad o Fire Panel Acknowledge o Fire Panel Alarm Test o Fire Panel Battery Test o Fire Panel Alarm o Fire Panel Trouble o Fire Panel Trouble Acknowledge o Fire Panel Alert o Fire Panel Fire Pump Status

D. Approved Field Server Fire Panel Integration Portals

Notifier by Honeywell Company/ Protocol Fire Alarm

Integration Developer/ Vendor

Comments

Notifier (Honeywell) 1010/2020 Notifier (Honeywell) AFP

200/300/400/600

Notifier (Honeywell) CEI-ABI Notifier (Honeywell) INA Notifier (Honeywell) Italia AM6000 Notifier (Honeywell) NCA2 and NFS2

3030

Notifier (Honeywell) NCA Notifier (Honeywell) NFS Onyx 640 Notifier (Honeywell) NFS 3030

GENERATOR MONITORING

SECTION 1 - Integration Requirements The selected and or existing Generator emergency back-up system should have the ability for read only integration using one of the following protocols. If one of the following protocols is not available on an existing generator hard wired monitor points must be supplied.

- BACnet IP - BACnet MS/TP - LonWorks FT-10 - Modbus RTU

An integration information document is to be completed and supplied with the initial submittal documents for approval.

A. Integration Control - Ability to monitor all available points through the integration. Monitor points should

include but not limited to the following: o Generator Running o Not In Automatic Start Mode o Low Fuel o Utility Power Failure o Low Engine Temperature o Common Alarm o Low Battery Voltage o Battery Charger Failure o Overspeed o Overcrank o High Engine Temperature o Low Oil Pressure o Low Coolant Level

B. Integration Demark Requirements - The selected integration protocol is to be demarked to the selected integration

demark location within the facility. - The demark location termination shall be landed and terminated with protocol

identified and applicable addressing information.

C. Graphical Display - Graphics must represent a graphical rendition of the generator room showing all

related devices. - All points pertaining to this device must be trended with COV (Change of Value). - All points should be setup to alarm in an off-normal state and generate a high priority

e-mail.

ELECTRICAL AND SUB METERING (REV. 4.6, 1/1/17)

PART 1 - EQUIPMENT SECTION 1 – SUMMARY All contractors responsible for electrical meter install must complete and submit “Integration Checklist” and “Electrical Meter Integration Checklist”. These checklists must be approved by Bedrock Director of Building Systems prior to installation. Meter installer is responsible for installation of communication wiring and coordination with Master Integration contractor. Preapproved Models E-Mon Class 5000 Meter Advanced kWh/Demand meter model E50-XXXXXX-R03-KIT-DT (where XXX-XXX is voltage followed by amperage) and EIDR-8-R03ST-DT as indicated Alternate models must receive written approval from Bedrock Director of Building Systems and meet and/or exceed the below requirements:

A. An integration information document is to be completed and supplied with the initial submittal documents for Bedrock approval.

B. This section includes electronic sub-metering and building integration. C. Advanced meter 4-line LCD display including:

1. kWh 2. Power factor per phase 3. Amps per Phase 4. kW demand (with peak date & Time) 5. Real-time load in kW 6. Volts per phase 7. Two external meter inputs for water, gas or BTU 8. On-board set-up option for:

a. IP address b. Meter date/time c. ID codes for BACnet IP and BACnet MS/TP

D. Meter location as indicated on drawings 1. Meter location as indicated on drawings. 2. Outdoor NEMA 4X polycarbonate enclosure (standard) with padlocking hasp &

mounting flanges for indoor/outdoor installation (stand-alone) with one 1 1/16” KO on bottom on enclosure.

E. 0-2 volt output split-core current sensors provide enhanced safety during installation and testing.

1. Current sensors allow remote mounting up to 500 feet from meter without power interruption.

F. Onboard installation diagnostics provide verification of correct system installation. G. Meters and current sensors comply with Michigan Public Service Commission Rider 4. H. RS-485 Protocol will include

1. BACnet MS/TP (RS-485 Port) 2. BACNET IP (Ethernet Port)

I. Meter will record kWh and kVARh delivered, kWh and kVARh received in first 4 channels. Data stored in 15-min. intervals for up to 72 days or 5-minute intervals for up to twenty-four days. Maintains interval data storage in a first-in, first-out format.

J. Meter voltage configuration as indicated on drawing 1. Meter will be designed for use on 3-phase, 3-wire (delta) and 3-phase, 4-wire

(wye) circuits.

SECTION 2 – EQUIPMENT

A. Meter standards 1. Meter will be UL/CUL Listed. 2. Meter will be certified by an independent test lab to ANSI C12.20 national

accuracy standards. (+/- 0.2% from 1% to 100% of rated load)

B. Meter specifications 1. Meter shall be fully electronic with 4-line by 20 character backlit LCD display

showing kWh, kW demand (with peak date and time), power factor per phase, real-time load in kW, Amps per phase and Volts per phase.

2. Meter shall utilize 0-2 volt AC output current sensors to allow paralleling and/or mounting up to 500 feet from the meter. Sensors shall be of split-core configuration to allow installation without disconnecting cabling, etc. Sensors shall be available from 100 amp to 3200 amp.

3. Meter shall be field programmable for IP address, meter date/time and ID code for communication options.

4. Meter shall provide current sensor installation diagnostics indicator, phase error indicator and phase angle diagnostics on display.

5. Meter enclosures as indicated on drawings i. Meter shall be enclosed in a NEMA 4X polycarbonate enclosure

(standard) with padlocking hasp & mounting flanges for indoor/outdoor installation (stand-alone) with one 1 1/6” KO on bottom of enclosure.

6. Meter shall provide non-volatile memory to maintain reading during power outages.

7. Meter shall store interval data for kWh and kVARh for up to 72 days in first-in first-out format.

8. Meter shall be available with the following communication protocols reading: i. BACnet IP (Ethernet)

ii. BACnet MS/TP (RS-485 Port) 1. Third-party EMS/BMS/BAS system and system integration by

others. 9. Meter shall provide optional 5th and 6th channel for logging dry contact pulse

inputs from third-party metering devices including; gas, water, BTU, etc. Both channels provide interval data logging that can be read via BACnet.

C. IDR (Interval Data Recorder) specifications 1. Reads and records up to 8 meters location as indicated on drawings. 2. Internal data storage –72 days of 15-minute intervals. Maintains last 72 days of

data. 3. Selectable baud rate up to 19200 bps. 4. EIDR requires a separate 120 V power source. 5. Maintains data in case of power failure. 6. Enclosure as indicated on drawings

i. Industrial-grade JIC steel enclosure with padlocking hasp and mounting flanges. Three 1 1/16” KO (3/4” cond.) on bottom of enclosure.

7. External EIDR meter input dry contact pulse inputs from third-party metering devices including; gas, water, BTU, electric, etc.

8. Reads kWh (kilowatt-hours) and reads kW (Demand) in 15, 30 or 60 minute kW periods.

9. Read meters individually or in groups. SECTION 3 – BUILDING MANAGEMENT INFORMATION

A. BACnet Object Descriptors

Instance

ID BACnet Object

Description Units BACnet Property

1 Analog Input Energy delivered kWh Present Value 2 Analog Input Energy received kWh Present Value 3 Analog Input Reactive energy delivered kVARh Present Value 4 Analog Input Reactive energy received kVARh Present Value 5 Analog Input Real power kW Present Value 6 Analog Input Reactive power kVAR Present Value 7 Analog Input Apparent power kVA Present Value 8 Analog Input Power factor % PF Present Value 9 Analog Input Peak demand kW Present Value

10 Analog Input Current average Amps Present Value 11 Analog Input Voltage line-neutral Volts-N Present Value 12 Analog Input Voltage line-line Volts-L Present Value 13 Analog Input Frequency Hz Present Value 14 Analog Input Phase angle Degree Present Value 15 Analog Input Real power phase A kW Present Value 16 Analog Input Real power phase B kW Present Value 17 Analog Input Real power phase C kW Present Value 18 Analog Input Reactive power phase A kVAR Present Value 19 Analog Input Reactive power phase B kVAR Present Value 20 Analog Input Reactive power phase C kVAR Present Value 21 Analog Input Apparent power phase A kVA Present Value 22 Analog Input Apparent power phase B kVA Present Value 23 Analog Input Apparent power phase C kVA Present Value 24 Analog Input Power factor phase A % PF Present Value 25 Analog Input Power factor phase B % PF Present Value 26 Analog Input Power factor phase C % PF Present Value 27 Analog Input Current phase A Amps Present Value 28 Analog Input Current phase B Amps Present Value 29 Analog Input Current phase C Amps Present Value 30 Analog Input Voltage line-neutral phase A-N Volts-N Present Value 31 Analog Input Voltage line-neutral phase B-N Volts-N Present Value 32 Analog Input Voltage line-neutral phase C-N Volts-N Present Value 33 Analog Input Voltage line-line phase A-B Volts-L Present Value 34 Analog Input Voltage line-line phase B-C Volts-L Present Value 35 Analog Input Voltage line-line phase C-A Volts-L Present Value 36 Analog Input Phase angle phase A Degree Present Value 37 Analog Input Phase angle phase B Degree Present Value 38 Analog Input Phase angle phase C Degree Present Value 39 Analog Input Reserve A No

Units Present Value

40 Analog Input Reserve B No Units

Present Value

41 Analog Input Reserve C No Units

Present Value

42 Analog Input External Input 1 Pulse Present Value 43 Analog Input External Input 2 Pulse Present Value

B. BACnet Object Descriptors

Instance ID BACnet Object BACnet Property

BAC Device ID Device Object identifier BAC Device ID Device Object name

BAC Device ID Device Object type BAC Device ID Device System status BAC Device ID Device Vendor name BAC Device ID Device Vendor identifier BAC Device ID Device Model name BAC Device ID Device Firmware revision BAC Device ID Device Application software version BAC Device ID Device Location BAC Device ID Device Description

SECTION 4 - WARRANTY

A. METER WARRANTY

1. Five (5) year repair and replace.

PART 2 – METER FIELD CONFIGURATION AND SOFTWARE INTEGRATION

SECTION 1 – POWER METER (FIELD) CONFIGURATION, SOFTWARE INTEGRATION AND STARTUP FORMS

A. Installing contractor responsible for completing Electrical Meter Integration Checklist and emailing to appropriate Bedrock parties for approval. Approval must be received prior to installation of meter.

B. Start-up and Commissioning Requirements - The Installing contractor is responsible for supplying a certified installer for the

purpose of start-up and verification. If a certified installer is not available it is then the responsibility of the installing contractor to have a manufacturer’s rep, who will be required to verify installation and start-up.

C. Integration Demark Requirements - The selected integration protocol is to be demarked to the selected integration

demark location within the facility by the installing contractor. - The demark location termination shall be landed and terminated with protocol

identified and applicable addressing information completed by the installing contractor.

D. Installing Contractor in conjunction with Master Integrator is responsible for

configuring each meter via display board push button switches including: Date & Time, Device ID, IP Settings, BACnet Settings, Reset KW/KWH Read.

E. Installing Contractor is responsible for providing completed ‘as built’ and close out documents to Bedrock Management.

F. Installing Contractor must provide “First Read” information from meter, available on “Bedrock Electrical Meter Integration Checklist”.

LIFTING DEVICES (REV. 2.1, 10/23/14)

SECTION 1 - Integration Requirements The selected and or existing Lifting Device systems in a facility should have the ability for read and write integration using one of the following protocols. If one of the following protocols is not available on an existing Lifting Device a Liftnet interface will be required to monitor and control the required Lifting Devices.

- BACnet IP - BACnet MS/TP - LonWorks FT-10 - Modbus RTU - OPC

An integration information document is to be completed and supplied with the initial submittal documents for approval.

G. Integration Control Ability to monitor and control all available points through the integration. Liftnet can integrate to the below systems that do not have an available protocol. If the Liftnet is supplied it must have the Bacnet IP communication available.

- Computerized Elevator Controls (CEC) - Delta - Elevator Controls Co. - Fujitec - GAL - Kone / Montgomery - Mid-American - Motion Control Engineering (MCE) - Northern - O'Thompson - Otis - Schindler (SEC) - Smartrise - ThyssenKrupp (TKE) / Dover - Vertitron Midwest

H. Integration Demark Requirements - The selected integration protocol is to be demarked to the selected integration

demark location within the facility. - The demark location termination shall be landed and terminated with protocol

identified and applicable addressing information.

I. Graphical Display by Master Systems Integrator - Graphics must represent a graphical rendition of the building showing all related

lifting cars. - All points pertaining to this device must be trended with COV (Change of Value). - All points should be setup to alarm in an off-normal state and generate a high priority

e-mail.

POINT TAGGING CONVENTIONS

SECTION 1 – SUMMARY All integrated points must be properly tagged by the Temperature Control contractor on the JACE using Haystack Tagging Conventions. Visit http://project-haystack.org for more information. SECTION 2 – Standards and Examples

AHU

The ahu tag is used model air handling equipment designed to heat or cool air. Packaged units use the ahu tag, but should also specify the rooftop tag:

ahu // any type of air handler unit (built-up or RTU)

ahu and rooftop // only packaged rooftop units (RTUs)

ahu and not rooftop // only built-up custom AHUs

Tags

AHUs should always be marked as equip. The following HVAC specific tags are used on AHU

records:

• hvac: always specified to mark as an HVAC asset

• rooftop: if the AHU is a packaged rooftop unit (RTU)

• dualDuct: if the AHU has separate cold air and hot air ductwork. Dual duct AHUs should

have two sets of discharge points identified with the coldDeck and hotDeck tags

• boilerPlantRef: to associate the AHU with the boiler plant supplying its hot water or steam

• chillerPlantRef: to associate the AHU with the chiller plant supplying its chilled water

Sections

Most points in an AHU are associated with one of the following sections of the unit:

• discharge: air exiting the unit to be supplied to the zones

• return: air returning from the zone back into the unit

• outside: fresh, outside air entering the unit for air quality and economizing

• exhaust: air exiting the unit back outside

• mixed: return and outside air mixed together before passing through the heating/cooling

elements

http://project-haystack.org/

• cool: cooling elements/coils

• heat: heating elements/coils

• zone: conditioned space associated with the unit

The follow diagram shows the logical flow of air through an AHU:

Points

The following lists points commonly used with an AHU:

Discharge

• discharge air temp sensor

• discharge air humidity sensor

• discharge air pressure sensor

• discharge air flow sensor

• discharge air fan cmd

• discharge air fan sensor

Return

• return air temp sensor

• return air humidity sensor

• return air pressure sensor

• return air flow sensor

• return air co2 sensor

• return air fan cmd

• return air damper cmd

Mixed

• mixed air temp sensor

Zone

• zone air temp sensor

• zone air humidity sensor

• zone air co2 sensor

• zone air temp effective sp

• zone air temp cooling sp

• zone air temp heating sp

Outside

• outside air temp sensor

• outside air humidity sensor

• outside air pressure sensor

• outside air flow sensor

• outside air flow sp

• outside air damper cmd

Exhaust

• exhaust air fan cmd

• exhaust air damper cmd

Conditioning

• cool stage cmd

• heat stage cmd

• humidifier cmd

• filter sensor

Misc

• freezeStat sensor

• heatWheel cmd

• faceBypass cmd

A chiller plant is composed of multiple pieces of equipment used to generate chilled water. The

entire plant is modeled as an equip with its own plant-level points. Sub-equipment such as chillers

and cooling towers are also modeled as equip contained by the plant via the equipRef tag.

The follow diagram shows the terminology used for logical flow of water through a chiller plant:

Note that the terminology for sensors/setpoints is based on the perspective of the equipment. The

condensed water exiting the chiller is the condensed water entering the cooling tower.

Chiller Plants

We model the entire plant using the chillerPlant tag. The plant is modeled as an equip and it will

define its own plant level points:

Chilled water to/from AHUs

• chilled water leaving temp sensor

• chilled water leaving temp sp

• chilled water leaving flow sensor

• chilled water leaving pressure sensor

• chilled water entering temp sensor

• chilled water entering flow sensor

• chilled water entering pressure sensor

• chilled water delta temp sensor

• chilled water delta flow sensor

• chilled water delta pressure sensor

• chilled water delta pressure sp

• chilled water bypass valve cmd

Condensed water between Chillers/Cooling Towers

• condensed water delta pressure sensor

• condensed water bypass valve cmd

Note: not every combination of sp is listed, just most common setpoints.

Chillers

Chiller equips are marked with the chiller tag. Equip level tags:

• equipRef must reference parent chillerPlant

• waterCooled or airCooled

• absorption or if vapor compression: reciprocal, screw, or centrifugal

• coolingCapacity

Points associated with chiller equip:

Chilled water to/from AHUs


• chilled water leaving temp sp

• chilled water leaving flow sensor

• chilled water leaving pressure sensor


• chilled water entering flow sensor

• chilled water entering pressure sensor

• chilled water delta temp sensor

• chilled water delta flow sensor

• chilled water delta pressure sensor

• chilled water valve isolation cmd

Condensed water to/from cooling towers

• condensed water leaving temp sensor

• condensed water leaving flow sensor

• condensed water leaving pressure sensor

• condensed water entering temp sensor

• condensed water entering pressure sensor

• condensed water entering flow sensor

• condensed water valve isolation cmd

Misc Internal

• efficiency

• condenser cmd

• condenser refrig temp sensor

• condenser refrig pressure sensor

• evaporator refrig temp sensor

• evaporator refrig pressure sensor

Note: not every combination of sp is listed, just most common setpoints.

Cooling Towers

Cooling towers equips are marked with the coolingTower tag. Equip level tags:


• openLoop or closedLoop

Points associated with cooling tower equip:


• condensed water leaving temp sp

• condensed water leaving flow sensor

• condensed water leaving pressure sensor

• condensed water entering temp sensor

• condensed water entering pressure sensor


• fan cmd

• fan sensor

Heat Exchangers

Heat exchangers are tagged with heatExchanger. Equip level tags:


Points associated with heat exchanger equip:





The general problems addressed by the energy tags are:

• modeling meters

• modeling submeters and their relationships

• modeling equip and point loads on meters

Design Pattern

A given project may model many different meter types:

• electricity meters

• fuel gas meters

• water meters

• steam meters

For each class of meter we define a meter type such as elec, gas, or water. Each meter is indicated by

a marker tag "<type>Meter". Top-level main meters for each site are tagged with the siteMeter tag

and submeters are defined with the submeterOf tag. Equip and point loads on a meter are tagged

with "<type>MeterLoad".

Meter Type Meter Tag Load Tag

elec elecMeter elecMeterLoad

gas gasMeter gasMeterLoad

water waterMeter waterMeterLoad

steam steamMeter steamMeterLoad

Example Model

Let's take a simple example. Let's assume we want to model this "tree" of meters and loads:

Main Elec Meter

+- LightsGroup (equip load)

+- Lights-ZoneX (point load)

+- Lights-ZoneY (point load)

+- HVAC Elec Submeter

+- RTU-1 (equip load)

+- Fan (point load)

+- DischargeTemp (not a load)

+- RTU-2 (equip load)

+- Fan (point load)

+- DischargeTemp (not a load)

The entities and their tags would look like this:

id:A, dis: "Main Elec Meter", elecMeter, siteMeter, equip

dis: "Main Elec Meter Demand", elecKw, equipRef: A, point, ...

dis: "Main Elec Meter Consumption", elecKwh, equipRef: A, point, ...

id:B, dis: "Lights", equip, elecMeterLoad:A, lightsGroup

dis: "Lights ZoneX", equipRef:B, elecMeterLoad:A, lights, point, ...

dis: "Lights ZoneY", equipRef:B, elecMeterLoad:A, lights, point, ...

id:C, dis: "HVAC Elec Submeter", elecMeter, submeterOf:A, equip

dis: "HVAC Elec Submeter Demand", elecKw, equipRef: C, point, ...

dis: "HVAC Elec Submeter Consumption", elecKwh, equipRef: C, point, ...

id:D, dis: "RTU-1", equip, elecMeterLoad:C, ahu

dis: "RTU-1 Fan", equipRef: D, elecMeterLoad:C, fan, point, ...

dis: "RTU-1 DA Temp", equipRef: D, dischargeTemp, point, ...

id:E, dis: "RTU-2", equip, elecMeterLoad:C, ahu

dis: "RTU-2 Fan", equipRef: E, elecMeterLoad:C, fan, point, ...

dis: "RTU-2 DA Temp", equipRef: E, dischargeTemp, point, ...

In the example above we have a top-level main electrical meter with the id A. Note it is tagged as

elecMeter for the meter type elec. It is also tagged as siteMeter to indicate it’s the main site-level

meter. It has two associated points for kW and kWh.

Then under the main meter, we have a HVAC submeter with the id C. Note it is tagged as elecMeter

but not siteMeter, instead it is associated as a submeter of the main meter using the submeterOf

tag. You can model submeter trees of arbitrary depth (submeters of submeters). It also has two

points for kW and kWh.

Lastly we have three electrical equipment loads defined. The two RTUs are associated with HVAC

submeter via elecMeterLoad which references the HVAC submeter via id. Since we don't have a

lighting submeter, the lighting load references the main meter directly via its elecMeterLoad tag.

We also tag one or more points under the equipment which are meaningful for the load. Actuators

would often be tagged as loads since they draw energy, but sensors would typically not be

considered loads.

Elec Meter

Electricity meters are probably the most common type of meters modeled. The elecMeter tag is

used model an electricity meter asset with the following points:

• kw sensor

• kwh sensor

• current sensor

• current phase sensor

• volt sensor

• volt phase sensor

• pf sensor

• pf phase sensor

• freq sensor

Flow Meters

With the exception of electricity meters, most meters measure flow of a liquid or gas. By

convention the following points are defined:

• flowRate: rate of volume flowing through the meter which provides the "demand" of the

meter

• flowConsumption: total volume consumption of the meter

Lighting Points

The lightsGroup tag is used to model the equip level of the lighting system and should follow all the

standard rules for equip entities.

lighting points to match the standardized site+equip+point model for navigation and analytics.

Lighting groups may model a single light switch, room, physical circuit, lighting panel, or logical

grouping of lights. The lighting group purpose is primarily to organize one or more The following

are the standard point types under lighting group:

• lights: primary actuator point indicating whether the lights are commanded on/off. The

lights point must be either a binary point (on/off) or a numeric point if dimmable (0% to

100%). A lightsGroup must have one or more of these points.

• lightLevel: sensor indicating current lighting level measured in "lux" or "lumen". A

lightsGroup can have zero or more of these points.

• occupancyIndicator: sensor indicating whether room is currently occupied. Point must be

Bool where true indicates occupied and false indicates unoccupied. A lightsGroup can have

zero or more of these points.

All number tag values can be annotated with an optional unit. In addition, it is strongly required to

annotate each point with the unit tag. In both cases, the unit must be an identifier defined by the

standard unit database.

Unit System

As a general principle, all the data associated with a given site should exclusively use either the SI

metric system or the US customary system. Mixing unit systems within one site will cause serious

headaches for analytics which require temperature/pressure constants or correlation of variables

of different units.

Database

This database was originally based on the oBIX specification, but has since been expanded to allow

multiple aliases to be used for each unit.

Each unit of measurement has a full name and zero or more symbols which are used as aliases for

that unit. For example "square_meter" is the full name and the symbol alias is "m²". Some units

might have multiple symbols, for example "hour" has the symbols "hr" and "h". Some units like

"day" have no symbols.

All unit identifiers are limited to the following characters:

• any Unicode char over 128

• ASCII letters a - z and A - Z

• underbar _

• division sign /

• percent sign %

• dollar sign $

By convention the symbol is the preferred notation. If there are multiple symbols, then the last

symbol defined by the database is the preferred one.

Common Units

Below are some commonly used units.

Misc

• percent, %

Area

• square_meter, m²

• square_foot, ft²

Currency

• australian_dollar, AUD

• british_pound, GBP, £

• canadian_dollar, CAD

• chinese_yuan, CNY, 元

• euro, EUR, €

• us_dollar, USD, $

Energy

• kilowatt_hour, kWh

Power

• kilowatt, kW

Pressure

• kilopascal, kPa

• pounds_per_square_inch, psi

• inches_of_water, inH₂O

• inches_of_mercury, inHg

Temperature

• fahrenheit, °F

• celsius, °C

Temperature differential

• fahrenheit_degrees, Δ°F

• celsius_degrees, Δ°C

Time

• millisecond, ms

• second, sec

• minute, min

• hour, hr, h

• day

• week, wk

• julian_month, mo

• year, yr

Volumetric Flow

• liters_per_second, L/s

• cubic_feet_per_minute, cfm

The vav tag is used to model variable air volume assets. VAVs are responsible for controlling the air

flow from an AHU into a zone.

Tags

VAVs should always be marked as equip. The following HVAC specific tags are used on AHU

records:

• hvac: always specified to mark as an HVAC asset

• dualDuct: if the VAV has separate cool deck and hot deck ductwork. Dual duct VAVs should

have two sets of discharge points identified with the coldDeck and hotDeck tags

• ahuRef: to associate the VAV with its supply AHU

Points

The following lists points commonly used with a VAV:

• zone air temp sensor

• zone air temp effective sp

• zone air temp cooling sp

• zone air temp heating sp

• zone air humidity sensor

• zone air co2 sensor

• discharge air temp sensor

• discharge air pressure sensor

• discharge air flow sensor

• discharge air fan cmd

• discharge air fan sensor

• discharge air damper cmd

• heat cmd

• perimeterHeat cmd

APPENDIX A

FCMS Structure Example

JACE Structure Example

APPENDIX B

1 of 49

FILENAME: BRMGT-1816-P - Shop Drawings - February 29, 2015.vsd

PROJECT

Project Manager

REVISION DATA

No Date Description By

Project Engineer Job Number

0 Submittal10/02/14 JJH

BRMGT Smart Building Panel – Shop DrawingsMarine City , MI

As Prepared By: Jeremy Houck

1

2

3

6221 King Rd.Marine City, MI

48039www.ThePanelShoppe.com

Phone: 1-810-689-0600

Engineer:

Joe PattenaudeDirector of Building Systems

O.: 1-313-782-9708M: 1-313-236-4158

Email: [email protected]

JOB NO.: 4/12/2016Certification

6221 King Rd, Marine City, MI 48039

Contractor: The Panel Shoppe

Installation DetailsShop Drawings

Drawn By: JJH

2 of 4

1.2.3.4.

Title PageTable of ContentsPanel Layout DiagramPanel Material List





Drawn By: JJH

3 of 4

Note:1. All connection to transformers located within the panel must have ½” conduit connected directly through the panel and into the transformer.

2. All 1" conduit must be installed 1.5" to center from the back edge of the panel.

Panel- TBDCircuit- TBD

10" x 10" x 6"Device Box

1'’ EMT

Panel FrontDetails

Interior EquipmentDetails

18"

16"

+

1/2'’ EMT – Conduit To Be Connected Directly Through

Panel And Into Power Supply.

120 VAC Feed From Panel

-

18"

16"





Drawn By: JJH

4 of 4

Model Number Description1816 Panel-

TPS13-18N1606LPTPS13-18N16MPDin RailPanduit - Wire DuctPanduit - Wire Duct CoverMisc Wire

‐P Power Terminal Strip-Functional Devices - PSH100AGrey 2 Conductor Terminal BlockOrange End PlateEnd Stop Adjacent 10-Way Jumper BarTerminal Block LabelsCC Fuse BlockEdison Fuses - EDCC3

1 of 49

FILENAME: BRMGT-1816-P-N3-XT-XBACRX - Shop Drawings - February 29, 2015.vsd

PROJECT

Project Manager

REVISION DATA






1

2

3



Phone: 1-810-689-0600

Engineer:


O.: 1-313-782-9708M: 1-313-236-4158






Drawn By: JJH

2 of 4

1.2.3.4.






Drawn By: JJH

3 of 4





1'’ EMT

Panel FrontDetails


18"

16"

+




-

18"

16"

LON BACNet MODBus

ESW-508 BASRT-B





Drawn By: JJH

4 of 4




‐N3 Network-B&B Electronics Ethernet Switch ESW508Din Rail Punch Down With SidesCAT5e Blue Keystone JackCable Exchange - 1' Pink CAT5E Patch Cable

‐XT Input/Output Module & Terminal Strip-

LON-Grey 2 Conductor Terminal BlockOrange End PlateEnd Stop

BACNet-Grey 2 Conductor Terminal BlockOrange End PlateEnd Stop

MODBus-Grey 2 Conductor Terminal BlockOrange End PlateEnd Stop

‐XBACRX Input/Output Module & Terminal Strip-1' Pink CAT5E Patch CableContempoaray Controls - BAS Router BACNet Multi-Network Router

1 of 49


PROJECT

Project Manager

REVISION DATA






1

2

3



Phone: 1-810-689-0600

Engineer:


O.: 1-313-782-9708M: 1-313-236-4158






Drawn By: JJH

2 of 4

1.2.3.4.






Drawn By: JJH

3 of 4





1'’ EMT

Panel FrontDetailsInterior Equipment

Details

20"

24"

+




-

20"

24"





Drawn By: JJH

4 of 4




1 of 49


PROJECT

Project Manager

REVISION DATA






1

2

3



Phone: 1-810-689-0600

Engineer:


O.: 1-313-782-9708M: 1-313-236-4158






Drawn By: JJH

2 of 4

1.2.3.4.






Drawn By: JJH

3 of 4


1'’ EMT

Panel FrontDetails

24"

36"


24"

36"

+







-





Drawn By: JJH

4 of 4

Model Number Description‐3624 Panel-

TPS13-36N2406LP - EnclousreTPS13-36N24MP - SubpanelDin RailPanduit - Wire DuctPanduit - Wire Duct CoverMisc Wire

‐P Power Terminal Strip-Functional Devices - PSH100AGrey 2 Conductor Terminal BlockOrange End PlateEnd StopAdjacent 10-Way Jumper BarTerminal Block LabelsCC Fuse BlockEdison Fuses - EDCC3

1 of 49

FILENAME: BRMGT-3624-P-N3-J6-DA-34T - Shop Drawings - February 25, 2015.vsd

PROJECT

Project Manager

REVISION DATA






1

2

3



Phone: 1-810-689-0600

Engineer:


O.: 1-313-782-9708M: 1-313-236-4158






Drawn By: JJH

2 of 4

1.2.3.4.






Drawn By: JJH

3 of 4


1'’ EMT

Panel FrontDetails

24"

36"


24"

36"

+







UI-1

UI-2

UI-3

UI-4

UI-5

UI-6

UI-7

UI-8

UI-9 UI- 10 UI- 11 UI- 12 UI- 13 UI- 14 UI- 15 UI- 16 AO-1

AO-2

AO-3

AO-4

AO-5

AO-6

AO-7

AO-8

DO

-1

DO

-2

DO

-3

DO

-4

DO

-5

DO

-6

DO

-7

DO

-8

DO

-9 D O - 1 0

-





Drawn By: JJH

4 of 4

Model Number Description‐3624 Panel-

TPS13-36N2406LP - EnclousreTPS13-36N24MP - SubpanelDin RailPanduit - Wire DuctPanduit - Wire Duct CoverMisc Wire

‐P Power Terminal Strip-Functional Devices - PSH100AGrey 2 Conductor Terminal BlockOrange End PlateEnd StopAdjacent 10-Way Jumper BarTerminal Block LabelsCC Fuse BlockEdison Fuses - EDCC3

‐N3 Network-B&B Electronics Ethernet Switch ESW508Din Rail Punch Down With SidesCAT5e Blue Keystone Jack1' Pink CAT5E Patch Cable

‐J6 Controller-Vykon - JACE-600E3' Pink CAT5E Patch CableEnd Stop

‐DA Software Drivers & Extras-NPM-256MB - MEMORY EXPANISON LINCENSE FROM 128MB to 256MB NPB-LON - LON Option CardDR-LONDRIV-AX - LONWORKS DRIVER OVER TWISTED PAIR FT10 NETWORKNPB-2X-RS485 - DUAL PORT RS-485 OPTION CARD FOR WEB-600 CONTROLLERDR-MSTP-AX - MSTP BACnet communications via RS-485 portDR-BACNET-AX - BACNET IP SERVER & CLIENT DRIVER OVER ETHERNETDR-MDB-RTU-AX - Modbus RTU over RS-232 or RS-485DR-MDB-TCP-AX - Modbus TCP over Ethernet

‐34T Input/Output Module & Terminal Strip-Vykon - IO-34 Grey Triple Deck Terminal BlockOrange End PlateEnd StopAdjacent Jumper Bar

Model Number

BRMGT-

181620243624

-P-NPWR

-NRPWR

-N1-N2-N3-NX

-J3-J6

-JPC-CX

-D#-DA-D1-D2-D3-D4-D5-D6-D7-D8-DX

-16-34

-16/34-NR161-NR162-NR163-NR164

-16T-34T

-16/34T-NR161T-NR162T-NR163T-NR164T

-XP-XDCPX-XN1X-XN2X-XN3X-XNX

-X1PCX-X5PCX

-XBACRX-XEPX

BRMGT- 3624 -P -N1 -J6 -DA -34 -XP

Ordering Information

Input/Output Module & Terminal Strip

Model Number

PanelTPS-18N1606NK-TTPS-20N2406NK-T

DR-MDB-RTU-AX - Modbus RTU over RS-232 or RS-485

List Below

JACE-300E - Controller / 5' Pink Patch CableJACE-600E - Controller / 5' Pink Patch CableJEC-334 - Plant Controller / 5' Pink Patch CableCustom Controller Options

Custom Network Option

Controller

TPS-36N2406NK-T

Power Options

24V AC/DC Power Supply Module - NPB-PWR

Network

90 - 263 Vac Power Supply Module - NPB-PWR-UN

100VA Transformer / Additional 24Vac Secondary Fusing / Terminal Strip

5 Port Unmanaged Network Switch / Din Rail Keystone Network Termination / 1' Pink Patch Cable8 Port Unmanaged Network Switch / Din Rail Keystone Network Termination / 1' Pink Patch Cable8 Port Managed Network Switch / Din Rail Keystone Network Termination / 1' Pink Patch Cable

Drivers & Extras-

Complete List

DR-BACNET-AX - BACNet IP Server & Client Driver Over Ethernet

DR-MDB-TCP-AX - Modbus TCP over Ethernet

NPM-256MB - Memory Expansion License From 128MB to 256MB NPB-LON - LON Option CardDR-LONDRIV-AX - LONWORKS DRIVER OVER TWISTED PAIR FT10 NETWORKNPB-2X-RS485 - Dual Port RS-485 Option Card DR-MSTP-AX - MS/TP BACNet Communications Via RS-485 Port

Electric Analog Signal To Pneumatic Pressure Converter (2nd X Denotes Quantity)BAS Router BACnet Multi-Network Router / 1' Pink Patch Cable (2nd X Denotes Quantity)5' Pink CAT5E Patch Cable (2nd X Denotes Quantity)

Custom Driver Options

IO-16 - 8 Universal Input / 4 Digital, 4 Analog Output Module

IO-16 - 8 Universal Input / 4 Digital, 4 Analog Output ModuleIO-34 - 16 Universal Input / 10 Digital, 8 Analog Output ModuleIO-16 - 8 Universal Input / 4 Digital, 4 Analog Output Module & IO-34 - 16 Universal Input / 10 Digital, 8 Analog Output Module

T Indicates Input/Output Terminal Strip Is Required

IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *

Din Rail Keystone Network Termination (2nd X Denotes Quantity)1' Pink CAT5E Patch Cable (2nd X Denotes Quantity)

8 Port Unmanaged Network Switch (2nd X Denotes Quantity)8 Port Managed Network Switch (2nd X Denotes Quantity)

5 Port Unmanged Network Switch (2nd X Denotes Quantity)

500VA Power Supply with Five 100VA Class 2 Outputs, 480/277/240/120 Vac to 24 VacAC to DC Voltage Converter (2nd X Denotes Quantity)

Misc & Extra Devices

IO-34 - 16 Universal Input / 10 Digital, 8 Analog Output Module

IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *IO-16 - 8 Universal Input / 4 Digital, 4 Analog Output Module & IO-34 - 16 Universal Input / 10 Digital, 8 Analog Output Module

Example:

Your Part Number:

IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *

IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *IO-16-485 - Remote 8 Universal Input / 4 Digital, 4 Analog Output Module (Number Denotes Quantity) *

Jeremy Houck The Panel Shoppe 4/15/201611:26 AM

APPENDIX C


Integration Checklist

Project Name: ________________________________

Property: __________________________________

Contractor Name: ________________________________

Contact Name: __________________________________

Contact Phone #: ________________________________

Email: __________________________________

Device Manufacturer: ________________________________

Model #: __________________________________

Type of Device � HVAC System/Equipment � Lighting Control � Utility Metering � Domestic Water Systems � Power Monitoring � Electrical (Separate

� Booster Pumps � Switch Gear checklist mandatory) � Sump Monitoring � Transfer Switches � Gas (Pulse) � Water/Leak Detection � UPS Systems � Water (Pulse) � Fire System � Back-Up Generator � BTU

Communication Protocol � BACnet � MODBUS � LON � Pulse � I/O � Other

� MS/TP �RTU � FT-10 1 Pulse = � IP �TCP/IP ______________ __________

Demark Location Device Location ____________________________ ____________________________

# of IP’s Required # of MAC Addresses Required ____________________________ ____________________________

Shop drawings with point mapping and network layout must be attached. If network is existing, “previous” and “next” devices must be indicated in documentation. Device

cut sheets with model number specified must also accompany this checklist for approval.

Checklist must be submitted for each unique piece of equipment.

Notes:

Below this line to be completed by Hepta Systems and approved by Bedrock:

IP Address Assigned MAC Address Assigned Instance ID Assigned

Integration Checklist Acceptance

_____________________________ ____/____/_____ Joe Pattenaude Date [email protected] (313) 782-9708

mailto:[email protected]


Electrical Meter Integration Checklist

Property Name:______________________ Tenant Name: ________________________ Contractor Name: ____________________

Contact Name: _______________________

Contact Phone #: _____________________

Email: ______________________________

Selected Protocol � LON � BACnet MS/TP � Modbus RTU � I/O � FT-10 � BACnet IP � Modbus TCP/IP

Electrical Meter Information

Device Manufacturer: __________________ Model #: ____________________________

Serial #: ____________________________ Location: ___________________________

Panel: ______________________________ Meter Multiplier: _____________________

Load: Lighting Receptacle Data HVAC Other:________________________________

New Meter Replacement Meter Last Reading: ___________ Startup Reading _________

Date of Installation: ______/______/______ Date of Start Up: _______/_______/_______


Serial #: ____________________________ Location: ___________________________






Serial #: ____________________________ Location: ___________________________







Serial #: ____________________________ Location: ___________________________





Device Manufacturer: -______________________

Model #: -________________________________

Serial #: -_________________________________

Location: ________________________________

Panel: ___________________________________

Meter Multiplier: -________________________________

Load: Lighting Receptacle Data HVAC Other: -________________________________________

New Meter Replacement Meter Last Reading: _________ Startup Reading _______


Device Manufacturer: -______________________

Model #: -________________________________

Serial #: -_________________________________

Location: ________________________________

Panel: ___________________________________

Meter Multiplier: -________________________________

Load: Lighting Receptacle Data HVAC Other: _______________________________

New Meter Replacement Meter Last Reading: _______ Startup Reading _________


Device Integration Notes: Device Integration Acceptance Sign Off

___________________________________ ______/____/_____ Joe Pattenaude Date

Documents

Smart Building Specificationbedrockstandards.com/wp-content/uploads/2017/01/...resource file for the device. For each BACnet device, the device supplier must provide a PICS document