25.00.00 HVAC Controls Master Specification

7/29/2019 25.00.00 HVAC Controls Master Specification

1/119

University of Southern California Control Guide Specifications

Preface and Implementation Guidance to the Design Engineer

These Guide Specifications set forth guidelines to assist the designers of buildingmechanical systems in specifying and procuring the controls for those building systems.The intent of this document is not to require a one-size-fits-all solution because that is

simply not in the best interest of the University of Southern California nor is it a practical

approach for procuring controls given the state of the control industry now and in the

near future.

Edits to each specification section shall be performed in Microsoft WORD software. All

editing shall be performed using the Track Changes options with all changes notaccepted. This allows the Owner to review all changes proposed to the Master

Documents.

This document provides tools for the designer to specify (i) the appropriate level ofcontrol system quality; (ii) the appropriate level of installer quality; and (iii) theappropriate level of interoperability.

Decision-making guidance to the design A/E is provided throughout these documents in

the form of Editors Notes so that the A/E may make prudent decisions and specify the

most effective requirements for the system being installed and for those that have to usethem. It is ultimately the designers job to assess the systems to be controlled and the

environment in which they will be installed, commissioned and operated and utilize the

appropriate elements of this specification. No changes shall be made to specification

sections outside of items as directed by the Editors Notes without express

permission of the USC Facilities Staff.

These Guide Specifications apply the following Principles to the control systems at USC

in the order they are presented:

Principle 1 The control system must first and foremost provide effectiveand reliable control, commensurate with the systems it is controlling.

Obviously the types, complexities and the criticalities of the systems being

controlled will dictate the quality/power of the control system that should be

applied to them. The ultimate quality of the control system is primarily dictatedby the components that sense, execute logic for, actuate, and document the

systems they are controlling. These components are generally specified in Master

Sections 15951 (EMCS BASIC MATERIALS, INTERFACE DEVICES, AND

SENSORS), and 15953 (EMCS FIELD PANELS). Again, one size does not fitall and therefore guidance is provided to work toward the most cost-effective

solution. This specification applies the concept of an Application Category forcontrollers whereby the performance requirements of the controllers are grouped

into categories, and the designer must dictate what category is required for a given

system.

Principle 2 The manufacturer and installer must be highly qualified withextensive experience and must be committed/bound to thorough


2/119

Commissioning (Cx). While the control system power/quality is very important,

equally or more important is the expertise and commitment of the installingcontractor and their collaboration with the overall commissioning team.

Qualifications should insure that a quality contractor with an extensive proven

track record is specified; and that effective, thorough commissioning of the

control systems by that contractor whether or not a formal Cx process isemployed - is essential. Given this, there lies a challenge to the designer to fairly

restrict installers to those that can deliver effectively within the context of both

the construction and the service/support arenas. To deal with this, Section 15950(EMCS GENERAL) provides a template for dictating qualifications of both the

installer and manufacturers of the systems. Section 15959 (EMCS

Commissioning) dictates a high standard for the Cx of the system by the installer.

Principle 3 The control installation must be fully documented asconsistently as practical with nothing required to fully operate and maintain

the system withheld from USC. Whether proprietary or Level 3 interoperable,

the system must always be put in the context of the enterprise and implemented

and documented using standard approaches wherever possible. Point namingconventions, programming logic, network configuration, security information, etc.

must be strictly adhered to and totally documented. No essential element for the

continued operation and maintenance of the control system may be withheld inany way. No part of the installation may be considered confidential or proprietary

information. This specification requires applicable documentation throughout.

These requirements are not optional; however, certain documents are onlyapplicable for certain approaches.

Principle 4: The system must be interoperable to the appropriate level.Seamless interoperability is a high priority goal. The term Interoperability mustbe considered in the context in which it is used. As one navigates the sea of

claims of interoperability, you will find most definitively that the devil is in the

details because of the multi-dimensional nature of a modern day EMCS. The

designer must require this Level of Interoperability unless otherwise

indicated by USC. A Level number is shown simply for ease of reference

throughout the rest of the Editors Notes:

o Control Inter-Network Level Communication (Level 3): This level ofinteroperability can effectively be accomplished via proprietary control

systems at the control network level with or without gateways to a

Supervisory Enterprise Management System that will utilize an openprotocol like BACnet or LonTalk. The University of Southern California

has implemented this level of interoperability via itsHoneywellEnterpriseBuildings Integrator (EBI) system. In this context, the EBI system usesLonTalk over IP or BACnet protocol over IP to accomplish

interoperability. This context of interoperability allows multiple devices

on separate control networks to communicate with the Enterprise in real

time. The level of interoperability provides for the ability to consolidatehistorical data (trends) across the enterprise, change setpoints, variables,

establish schedules, and view all data in real time. An Enterprise in this


3/119

context consists of multiple buildings across the USC campus and possible

remote sites. It then, by definition, also allows third-party OperatorWorkstations, such as the EBI, to communicate with all control systems.

Devices, regardless of who manufactured them, can share information yet

they would in this context be allowed to be on separate control networks

or segments. Information must be formatted for BACnet or LonMarkcertified compliant controllers. Proprietary systems with a BACnet

gateway are acceptable as Level 3 systems (gateways are also acceptable

to external systems (e.g., lighting controls, elevator controls), externalbuildings with legacy systems, or to equipment with proprietary OEM

controllers. The controllers and devices would be allowed to require

different configuration and programming tools. Unless otherwise

indicated by USC, the designer must require this level of

interoperability.

Principal 5: Specify Sequence of Operations LogicThe designer must specify the logic of equipment sequences of operations. Often

sequences of operations are specified only in general, and often ambiguous, terms,with much of the sequence left to the contractors programmer. The programmers

should not be put in the position of having to complete the engineers sequence,

and often resort to sequences which are not optimal for the particular building.Therefore, logic diagrams should be included in design documents. If the project

is being done using a design-build methodology, then the design-builder must

submit logic diagrams as a design submittal in advance of programming.

Principal 6: Require Sufficient InstrumentationThe designer must require instrumentation to support both the sequence ofoperations, and the data acquisition capability to support equipment performance

monitoring and building diagnostics analysis. A listing generally establishingminimum instrumentation requirements is included with the specifications. This

identifies minimum instrumentation for common types of system. The designer is

responsible for requiring additional instrumentation as necessary to support thesequence of operations, or to supplement data acquisition capabilities when the

nature of the equipment or systems to be installed makes this sensible.

Conclusion: Application of these Principles to a given project requires the designer to

research/consider the project-specific environment and requirements and to edit thisspecification appropriately. The specific decision depends on a number of other

important variables, including the specific HVAC control applications being served, thequality and capabilities of the local installer, and operator capabilities. The designer iscautioned to apply or find the appropriate level of expertise to complete this specification

- otherwise, the result could be a specification with inadequate and contradictory

requirements that cannot be enforced.


4/119

This specification extensively references detailed control drawings, detailed sequences of

operation, point lists, binding diagrams, etc. The A/E and design team must provide andincorporate these into the design documents.

These specification sections are copyrighted by Facility Dynamics Engineering and

licensed for use for the University of Southern California facilities only.


5/119

University of Southern California Master HVAC Controls Specification

Energy Management Control System (EMCS) General 15950 - 1

SECTION 15950 - EMCS GENERAL

Note to the Design AE: The AE and project manager should discuss the project with USC.

There is a Preface document describing how to employ this and other USC controls-relatedGuide Specifications. The AE is instructed to consult the Preface document for guidance on

the nature of this specification, methods for deleting non-applicable text, and the use and

deletion of Editors Notes before proceeding to customize this specification.

Refresh the table of contents after editing section

Part I. GENERAL ................................................................................................................................................ 11.01 SECTION INCLUDES............................................................................................................................... 11.02 RELATED DOCUMENTS ........................................................................................................................ 21.03 DESCRIPTION OF WORK ....................................................................................................................... 21.04 PROCUREMENT ...................................................................................................................................... 31.05 QUALITY ASSURANCE .......................................................................................................................... 31.06 CODES AND STANDARDS .................................................................................................................... 41.07 DEFINITIONS ........................................................................................................................................... 51.08 FUNCTIONAL INTENT ........................................................................................................................... 81.09 SUBMITTALS ........................................................................................................................................... 81.10 PROJECT RECORD DOCUMENTS ...................................................................................................... 121.11 SYSTEM ARCHITECTURE ................................................................................................................... 131.12 WARRANTY MAINTENANCE ............................................................................................................. 161.13 DELIVERY, STORAGE, AND HANDLING ......................................................................................... 181.14 LISTING AND LABELING .................................................................................................................... 18

Part II. PRODUCTS ............................................................................................................................................ 182.01 MATERIALS AND EQUIPMENT .......................................................................................................... 182.02 UNIFORMITY ......................................................................................................................................... 18

Part III. EXECUTION .......................................................................................................................................... 193.01 INSPECTION ........................................................................................................................................... 193.02 INSTALLATION OF CONTROL SYSTEMS ........................................................................................ 193.03 DIGITAL CONTROL STATIONS , CONTROLLER QUANTITY AND LOCATION ........................ 193.04 SURGE PROTECTION ........................................................................................................................... 203.05 DEMOLITION AND REUSE OF EXISTING MATERIALS AND EQUIPMENT {Include ifapplicable}............................................................................................................................................................... 203.06 SEQUENCE OF WORK FOR EXISTING SYSTEMS CONVERSION ................................................. 213.07 CONTROL POWER SOURCE AND SUPPLY ...................................................................................... 223.08 EMCS START UP, COMMISSIONING AND TRAINING ................................................................... 233.09 SEQUENCE OF OPERATION ................................................................................................................ 23

PART I. GENERAL1.01 SECTION INCLUDES

A. General Requirements

2000 FACILITY DYNAMICS ENGINEERING


6/119



B. Description of WorkC. Quality AssuranceD. System ArchitectureE. Distributed Processing Units/Quantity and LocationF. Demolition and Reuse of Existing Materials and EquipmentG. Sequence of Work

1.02 RELATED DOCUMENTSA. Section {Insert Applicable Specification Section} -Basic Mechanical Requirements.B. Section 15951 Energy Management Control System (EMCS) Basic Materials, Interface

Devices, and Sensors

C. Section 15952 - EMCS Operator InterfacesD. Section 15953 - EMCS Field PanelsE. Section 15954 - EMCS Communication DevicesF. Section 15955 - EMCS Software and ProgrammingG. Section {Insert Applicable Specification Section(s)} Sequences of OperationH. Section 15959 EMCS Commissioning

1.03

DESCRIPTION OF WORK

The following paragraph applies to the Level 3 Interoperability and is not optional.

A. The distributed digital control (DDC) and Energy Management Control System (EMCS)defined in this specification shall seamlessly interface with the University of Southern

Californias Honeywell Enterprise Building Integrator (EBI), and shall utilize the

BACnet communication requirements as defined by ASHRAE/ANSI 135-2001, or

Echelon LonTalk Protocol as defined by EIA/CEA-709.1-A-1999 for all communication

between building automation systems and the EBI operator workstation directly.

Towards this end, contractor shall provide a router/gateway(s) as necessary to facilitate

all specified objects and services and have them configured/mapped as applicable.

Incorporation of these objects and services into the EBI system is required under this

project.

B. Contractor shall furnish and install a direct digital control and Energy ManagementControl System (EMCS). The new EMCS shall utilize electronic sensing,

microprocessor-based digital control, and electronic and/or pneumatic actuation of

dampers and valves to perform control sequences and functions specified. The EMCS for

this project will generally consist of monitoring and control of systems listed below.

Reference also, control drawings, sequences of operation, and points lists.



7/119



C. The systems to be controlled under work of this section basically comprise {describe thescope of the project.} The HVAC systems being controlled are {describe the

configuration of and the type of mechanical systems included in the project}. This

Section defines the manner and method by which these controls function.

1.04 PROCUREMENTA. The EMCS and digital control and communications components installed, as work of this

contract shall be an integrated distributed processing system of the following

manufacturer. No other vendors products will be considered as substitutions.

B. Acceptable Manufacturers1. Honeywell - EXCEL 5000 OPEN System2. Substitutions: None

1.05

QUALITY ASSURANCE

Use A to define any specific qualifications needed; otherwise leave Reserved

A. Reserved.The following requirement is relative to the demonstrated history of the product line they are

proposing. Edit to suit project.

B. Product Line Demonstrated History: The product line being proposed for the projectmust have an installed history of demonstrated satisfactory operation for a length of [1]

year since date of final completion in at least [10] installations of comparative [size] [and

complexity]. Submittals shall document this requirement with references.

The following requirement relates to the actual installing contractor..

C. Installer's Qualifications: Firms specializing and experienced in control systeminstallations for not less than [5] years. Firms with experience in DDC installation

projects with point counts equal to this project and systems of the same character as this

project. Experience starts with awarded Final Completion of previous projects.

Submittals must document this experience with references.

The following requirement relates to the actual installing contractors experience with the

proposed product line. This is where you specifically eliminate an experienced controls

company that just picked up the line. This requirement is not as clearly applicable as the

previous one. Edit to suit approach.

D. Installer's Experience with Proposed Product Line: Firms shall have specialized inand be experienced with the installation of the proposed product line for not less than

[one] year from date of final completion on at least [3] projects of similar size and

complexity. Submittals shall document this experience with references.

The following requirements relate to the key individuals who will be working on the project.

E. Installers Field Coordinator and Sequence Programmer Qualifications:Individual(s) shall specialize in and be experienced with control system installation for



8/119



not less than 5 years. Proposed field coordinator shall have experience with the

installation of the proposed product line for not less than [3] projects of similar size and

complexity. Installer shall submit the names of the proposed individual and at least one

alternate for each duty. Submittals shall document this experience with references. {Edit

as applicable} The proposed individuals must show proof of the following training:1. Product Line Training: Individuals overseeing the installation and configuration

of the proposed product line must provide evidence of the most advanced training

offered by the Manufacturer on that product line for installation and configuration

2. Programming Training: Individuals involved with programming the site-specificsequences shall provide evidence of the most advanced programming training

offered by the vendor of the programming application offered by the Manufacturer.

3. LonTalk Training: The LonTalk EMCS shall be furnished, engineered andinstalled by individuals who have completed the LonMark Network Design,

Installation and Maintenance Training Program. Certifications shall be provided.

F. Installers Service Qualifications: The installer must be experienced in control systemoperation, maintenance and service. Installer must document a minimum 5 year historyof servicing installations of similar size and complexity. Installer must also document at

least a one year history of servicing the proposed product line.

G. Installers Response Time and Proximity1. Installer must maintain a fully capable service facility within a [45 mile] radius of

the project site. Service facility shall manage the emergency service dispatches and

maintain the inventory of spare parts.

2. Emergency response times are listed below in this section. Installer mustdemonstrate the ability to meet the response times.

1.06 CODES AND STANDARDSA. The following codes and standard intended to apply as applicable as not all will apply to

all installations

B. American Society of Heating, Refrigeration and Air Conditioning Engineers (ASHRAE)1. ASHRAE 135-2001: BACnet - A Data Communication Protocol for Building

Automation and Control Networks. American Society of Heating, Refrigerating and

Air-Conditioning Engineers, Inc. 2001

C. Electronics Industries Alliance1. EIA-709.1-A-99: Control Network Protocol Specification2.

EIA-709.3-99: Free-Topology Twisted-Pair Channel Specification

3. EIA-232: Interface Between Data Terminal Equipment and Data Circuit-Terminating Equipment Employing Serial Binary Data Interchange.

4. EIA-458: Standard Optical Fiber Material Classes and Preferred Sizes5. EIA-485: Standard for Electrical Characteristics of Generator and Receivers for use

in Balanced Digital Multipoint Systems.

6. EIA-472: General and Sectional Specifications for Fiber Optic Cable



9/119



7. EIA-475: Generic and Sectional Specifications for Fiber Optic Connectors and allSectional Specifications

8. EIA-573: Generic and Sectional Specifications for Field Portable Polishing Devicefor Preparation Optical Fiber and all Sectional Specifications

9. EIA-590: Standard for Physical Location and Protection of Below-Ground FiberOptic Cable Plant and all Sectional Specifications

D. Underwriters Laboratories1. UL 916: Energy Management Systems.

The following rating is required only for devices used for smoke control purposes. If these arenot intended, delete.

2. UUKL 864: UL Supervised Smoke ControlE. NEMA Compliance

1. NEMA 250: Enclosure for Electrical Equipment2. NEMA ICS 1: General Standards for Industrial Controls.

F. NFPA Compliance1. NFPA 90A "Standard for the Installation of Air Conditioning and Ventilating

Systems" where applicable to controls and control sequences.

2. NFPA 70 National Electrical Code (NEC)G. Institute of Electrical and Electronics Engineers (IEEE)

1. IEEE 142: Recommended Practice for Grounding of Industrial and CommercialPower Systems

2. IEEE 802.3: CSMA/CD (Ethernet Based) LAN3.

IEEE 802.4: Token Bus Working Group (ARCNET Based) LAN

Edit the definitions below to apply for a given project.

1.07 DEFINITIONSA. Advanced Application Controller (AAC):A device with limited resources relative to

the Building Controller (BC). It may support a level of programming and may also be

intended for application specific applications.

B. Application Protocol Data Unit (APDU): A unit of data specified in an applicationprotocol and consisting of application protocol control information and possible

application user data (ISO 9545).

C. Application Specific Controller (ASC): A device with limited resources relative to theAdvanced Application Controller (AAC). It may support a level of programming and

may also be intended for application-specific applications. .

D. BACnet/BACnet Standard: BACnet communication requirements as defined byASHRAE/ANSI 135-2001.



10/119



E. BACnet Interoperability Building Blocks (BIBB): A BIBB defines a small portion ofBACnet functionality that is needed to perform a particular task. BIBBS are combined to

build the BACnet functional requirements for a device in a specification.

F.

Binding: In the general sense,binding refers to the associations or mappings of thesources network variable and their intended or required destinations.

G. Building Controller (BC): A fully programmable device capable of carrying out anumber of tasks including control and monitoring via direct digital control (DDC) of

specific systems, acting as a communications router between the LAN backbone and sub-

LANs, and data storage for trend information, time schedules, and alarm data.

H. Change of Value (COV): An event that occurs when a measured or calculated analogvalue changes by a predefined amount (ASHRAE/ANSI 135-2001).

I. Client: A device that is the requestor of services from a server. A client device makesrequests of and receives responses from a server device.

J. Continuous Monitoring: A sampling and recording of a variable based on time orchange of state (e.g. trending an analog value, monitoring a binary change of state).

K. Controller or Control Unit (CU): Intelligent stand-alone control panel. Controller is ageneric reference and shall include BCs, AACs, and ASCs as appropriate.

L. Control Systems Server (CSS): This shall be a computer (or computers) that maintainsthe systems configuration and programming database.

M. Direct Digital Control (DDC): Microprocessor-based control including Analog/Digitalconversion and program logic

N. Energy Management Control System (EMCS): The entire integrated management andcontrol system

O. Enterprise Buildings Integrator (EBI): An Enterprise-level, Intranet-based networkconnecting multiple buildings on USCs campus with a central data warehouse and

server, accessible via the host computer.

P. Functional Profile: A collection of variables required to define a the key parameters fora standard application. As this applies to the HVAC industry, this would include

applications like VAV terminal, fan coil units, and the like.

Q. Gateway (GTWY): A device, which contains two or more dissimilar networks/protocols,permitting information exchange between them (ASHRAE/ANSI 135-2001).

R. Hand Held Device (HHD): Manufacturers microprocessor based device for directconnection to a Controller.S. Host-Based Controller: A term applicable only to Lon-based controllers where the on-

board Neuron chip is used solely as the Communications Interface and a processor

independent from the Neuron chip to is used to execute Application control and I/O

processes.



11/119



T. IT LAN: Reference to the facilitys Information Technology network, used for normalbusiness-related e-mail and Internet communication.

U. LAN Interface Device (LANID): Device or function used to facilitate communicationand sharing of data throughout the EMCS

V. Local Area Network (LAN): General term for a network segment within thearchitecture. Various types and functions of LANs are defined herein.

W. Local Supervisory LAN: Ethernet-based LAN connecting Primary Controller LANswith each other and OWSs, POTs and CSSs and the LAN to which the EBI will be

interfaced. See System Architecture below. THISCAN BE THE PRIMARY LAN.

X. Master-Slave/Token Passing (MS/TP): Data link protocol as defined by the BACnetstandard. (ASHRAE/ANSI 135-2001).

Y. Open Database Connectivity (ODBC): An open standard application-programminginterface (API) for accessing a database developed. ODBC compliant systems make it

possible to access any data from any application, regardless of which databasemanagement system (DBMS) is handling the data.

Z. Operator Interface (OI): A device used by the operator to manage the EMCS includingOWSs, POTs, and HHDs.

AA. Operator Workstation (OWS): The users interface with the EMCS. As the EMCSnetwork devices are stand-alone, the OWS is not required for communications to occur.

BB. Point-to-Point (PTP): Serial communication as defined in the BACnet standard.CC. Portable Operators Terminal (POT): The users interface with the EMCS. As the

EMCS network devices are stand-alone, the POT is not required for communications to

occur. Laptop PC to be used for direct connection to a controller, remote dial upconnection and as the operator workstation.

DD. Protocol Implementation Conformance Statement (PICS): A written document,created by the manufacturer of a device, which identifies the particular options specified

by BACnet that are implemented in the device (ASHRAE/ANSI 135-2001).

EE. Primary Controlling LAN: High speed, peer-to-peer controller LAN connecting BCsand optionally AACs and ASCs. Refer to System Architecture below.

FF. Router: A device that connects two or more networks at the network layer.GG. Secondary Controlling LAN: LAN connecting AACs and ASCs, generally lower speed

and less reliable than the Primary Controlling LAN. Refer to System Architecture below.

HH. Server: A device that is a provider of services to a client. A client device makes requestsof and receives responses from a server device.

II. SQL: Standardized Query Language, a standardized means for requesting informationfrom a database.



12/119



JJ. Standard Network Variable Type (SNVT): A form of APDU specifically used to bindLonWorks control data across a LonWorks network.

KK. USC Campus LAN: USCs IT LAN located on their campus connecting multiplebuilding on the campus.

LL. XIF File: A file indicating the interface specifications for LonMark devices.MM. XML (Extensible Markup Language): A specification developed by the World Wide

Web Consortium. XML is a pared-down version of SGML, designed especially for Web

documents. It allows designers to create their own customized tags, enabling the

definition, transmission, validation, and interpretation of data between applications and

between organizations.

1.08 FUNCTIONAL INTENTA. Throughout Sections 15950 through 15955, the Sequences of Operation, and Section

15959 detailed requirements are specified, some of which indicate a means, method orconfiguration acceptable to meet that requirement. Contractor may submit products that

utilize alternate means, methods, and configurations that meet the functional intent.

However these will only be allowed with prior approval.

1.09 SUBMITTALSA. Submit under provisions of Section {Insert Appropriate Section Number}.B. Electronic Submittals: While all requirements for hard copy submittal apply, control

submittals, and O&M information shall also be provided in electronic format as follows.

1. Drawings and Diagrams: Shop drawings shall be provided on electronic media asan [AutoCAD 2000 or later version drawing file] and/or Adobe Portable DocumentFormat file. All x reference and font files must be provided with AutoCAD files

2. Graphics: All graphics shall be provided electronically adhering to USC EMSControl Graphics Standards and be directly incorporable into the selected USC EMSEnterprise software of EBI.

3. Other Submittals: All other submittals shall be provided in Adobe PortableDocument Format

C. Qualifications: Manufacturer, Installer, and Key personnel qualifications as indicatedfor the appropriate item above.

D. Product Data: Submit manufacturer's technical product data for each control device,panel, and accessory furnished, indicating dimensions, capacities, performance andelectrical characteristics, and material finishes. Also include installation and start-up

instructions.

E. Shop Drawings: Submit shop drawings for each control system, including a completedrawing for each air handling unit, system, pump, device, etc. with all point descriptors,

addresses and point names indicated. Each shop drawing shall contain the following

information:



13/119



1. System Architecture and System Layout:a) One-line diagram indicating schematic locations of all control units,

workstations, LAN interface devices, gateways, etc. Indicate network number,device ID, address, device instance, MAC address, drawing reference number,

and controller type for each control unit. Indicate media, protocol, baud rate,and type of each LAN. For LonTalk systems indicate all LonTalk nodes,

including Neuron ID and domain, sub-network and channel addresses. Indicate

media, protocol, baud rate, and type of each LAN. All optical isolators,

repeaters, end-of-line resistors, junctions, ground locations etc. shall be located

on the diagram.

b) Provide floor plans on [AutoCAD 2000 or later version drawing file] softwarelocating all control units, workstations, servers, LAN interface devices,

gateways, etc. Include all WAN and LAN communication wiring routing,

power wiring, power originating sources, and low voltage power wiring.

Indicate network number, device ID, address, device instance, MAC address,

drawing reference number, and controller type for each control unit. Indicate

media, protocol, baud rate, and type of each LAN. For LonTalk systems

provide as-built network architecture drawings showing all LonTalk nodes,

including Neuron ID and domain, sub-network and channel addresses. All

optical isolators, repeaters, end-of-line resistors, junctions, ground locations etc.

shall be located on the floor plans. Wiring routing as-built conditions shall be

maintained accurately throughout the construction period and the drawing shall

be updated to accurately reflect accurate, actual installed conditions.

2. Schematic flow diagram of each air and water system showing fans, coils, dampers,valves, pumps, heat exchange equipment and control devices. Include verbaldescription of sequence of operation.

3. All physical points on the schematic flow diagram shall be indicated with names,descriptors, and point addresses identified as listed in the point summary table.

4. With each schematic, provide a point summary table listing building number andabbreviation, system type, equipment type, full point name, point description,

Ethernet backbone network number, network number, device ID, object ID (object

type, instance number). See Section 15955 - Part III for additional requirements.

5. Label each control device with setting or adjustable range of control.6. Label each input and output with the appropriate range.7. Provide a Bill of Materials with each schematic. Indicate device identification to

match schematic and actual field labeling, quantity, actual product ordering number,

manufacturer, description, size, voltage range, pressure range, temperature range,

etc. as applicable.

8. With each schematic, provide valve and actuator information including size, Cv,design flow, design pressure drop, manufacturer, model number, close off rating,

etc. Indicate normal positions of spring return valves and dampers.

9. Indicate all required electrical wiring. Electrical wiring diagrams shall include bothladder logic type diagram for motor starter, control, and safety circuits and detailed

digital interface panel point termination diagrams with all wire numbers and

terminal block numbers identified. Provide panel termination drawings on separate



14/119



drawings. Ladder diagrams shall appear on system schematic. Clearly differentiate

between portions of wiring, which are existing, factory-installed and portions to be

field-installed.

10. Details of control panels, including controls, instruments, and labeling shown in planor elevation indicating the installed locations.

11. Sheets shall be consecutively numbered.12. Each sheet shall have a title indicating the type of information included and the

HVAC system controlled.

13. Table of Contents listing sheet titles and sheet numbers.14. Legend and list of abbreviations.15. Memory allocation projections.16. Submit along with shop drawings but under separate cover calculated and

guaranteed system response times of the most heavily loaded LAN in the system.

F. Open Protocol Information1. LonWorks Systems (Any system using LonWorks shall include the following):

a) Binding table indicating all Network Variables used in the project, Neuron IDand domain, subnet and channel address, and associated bound variables.

Clearly indicate which parameters of a functional profile are bound and can be

overridden.

b) A point binding diagram shall be provided with each control schematicdepicting all bound network variables along with the associated functional

profiles.

c) LonMark functional profile certifications.d) For Host-Based Controllers: Controller programming and configuration tool

and or plug in required for all controllers with a minimum of 3 licenses asapplicable.

e) For non-host Controllers: LonTalk Neuron C source code and/or Neuron Capplication programming interface tool (3 licenses) and associated files

required for all controllers.

f) Backup of systems configuration database on CD. This shall be provided atsubstantial completion and at the end of the warranty period.

g) Documentation of all explicit messaging.h) XIF files for all LonMark components.

2. BACnet Systems (Any system using BACnet shall include the following):a) BACnet object description, object ID, and device ID, for each I/O point.b) Documentation for any non-standard BACnet objects, properties, or

enumerations used detailing their structure, data types, and any associated lists

of enumerated values.

c) Submit PICS indicating the BACnet functionality and configuration of eachcontroller.



15/119



G. EBI Interface Information: Provide a Points List in both hard copy and in electronicformat (ODBC compliant). The Points List shall contain a listing of building number and

abbreviation, system type, equipment type, full point name, point description, Ethernet

backbone network number, network number, device ID or node number, object ID

(object type, instance number).

H. Graphics: Provide a complete set of control graphics for the building following USCControl Graphics Standards which will seamlessly incorporate into the EBI front end.

I. Framed Control Drawings: Laminated control drawings including system controlschematics, sequences of operation and panel termination drawings, shall be provided in

panels for major pieces of equipment. Terminal unit drawings shall be located in the

central plant equipment panel or mechanical room panel.

J. Control Logic Documentation1. Submit control logic program listings (for graphical programming) and logic flow

charts illustrating (for line type programs) to document the control software of all

control units.

2. Control logic shall be annotated to describe how it accomplishes the sequence ofoperation. Annotations shall be sufficient to allow an operator to relate each

program component (block or line) to corresponding portions of the specified

Sequence of Operation.

3. Include written description of each control sequence.4. Include control response, settings, setpoints, throttling ranges, gains, reset schedules,

adjustable parameters and limits.

5. Sheets shall be consecutively numbered.6. Each sheet shall have a title indicating the controller designations and the HVAC

system controlled.

7. Include Table of Contents listing sheet titles and sheet numbers8. Submit one complete set of programming and operating manuals for all digital

controllers concurrently with control logic documentation. This set will count

toward the required number of Operation and Maintenance materials specified

below and in Section {Insert Appropriate Section Number}.

K. Operation and Maintenance Materials:1. Submit documents under provisions of Section {Insert Appropriate Section

Number}. One copy of the materials shall be delivered directly to the Universitys

facilities operation staff, in addition to the copies required by other Sections.

2. Submit maintenance instructions and spare parts lists for each type of control device,control unit, and accessory.

3. Submit EMCS Users Guides (Operating Manuals) for each controller type and forall workstation hardware and software and workstation peripherals.

4. Submit EMCS advanced Programming Manuals for each controller type and for allworkstation software.



16/119



5. Include all submittals (product data, shop drawings, control logic documentation,hardware manuals, software manuals, installation guides or manuals, maintenance

instructions and spare parts lists) in maintenance manual; in accordance with

requirements of Division 1.

L. Controls contractor shall provide USC with all product line technical manuals andtechnical bulletins, to include new and upgraded products, by the same distribution

channel as to dealers or branches. This service will be provided for 5 years as part of the

contract price, and will be offered to USC thereafter for the same price as to a dealer or

branch.

M. Manufacturers Certificates: For all listed and/or labeled products, provide certificate ofconformance. Include all LonMark functional profiles certifications for systems used on

this project.

N. Product Warranty Certificates: submit manufacturers product warranty certificatescovering the hardware provided.

1.10 PROJECT RECORD DOCUMENTSA. Submit documents under provisions of Section {Insert Appropriate Section Number}.B. Record copies of product data and control shop drawings updated to reflect the final

installed condition.

C. Record copies of approved control logic programming and database on paper and onCDs. Accurately record actual setpoints and settings of controls, final sequence of

operation, including changes to programs made after submission and approval of shop

drawings and including changes to programs made during specified testing.

D. Record copies of approved project specific graphic software on CDs.E. For LonTalk systems provide as-built network architecture drawings showing all

LonTalk nodes, including Neuron ID and domain, sub-network and channel addresses.

For BACnet systems provide as-built network architecture drawings showing all BACnet

nodes including a description field with specific controller identification, description and

location information.

F. Record copies shall include individual floor plans with controller locations with allinterconnecting wiring routing including space sensors, LAN wiring, power wiring, lowvoltage power wiring. Indicate device instance, MAC address and drawing reference

number.

G. Provide record riser diagram showing the location of all controllers.H. Maintain project record documents throughout the warranty period and submit final

documents at the end of the warranty period



17/119



1.11 SYSTEM ARCHITECTUREA. The system provided shall incorporate hardware resources sufficient to meet the

functional requirements of these Specifications. The Contractor shall include all items

not specifically itemized in these Specifications that are necessary to implement,maintain, and operate the system in compliance with the functional intent of these

Specifications.

B. The system shall be configured as a distributed processing network(s) capable ofexpansion as specified below.

The EMCS high speed LAN will be a dedicated Ethernet LAN separate from the buildings IT

LAN.

C. The system architecture shall consist of an Ethernet-based, wide area network (WAN), asingle Local Area Network (LAN) or multi-leveled LANs that support BCs, AACs,

ASCs, Operator Workstations (OWS), Portable Operators Terminal (POT), and Remote

Communication Devices (RCDs) as applicable. The following indicates a functionaldescription of the EMCS structure.

This is the place where the Level 3 interoperability is specified. It should describe the options

for connecting the local LAN to the EBI as part of the EBI integration part of this scope.

1. Enterprise Building Integrator WAN: Intranet-based network connectingmultiple buildings with a central data warehouse and server. This is an existing

infrastructure and contractor is required to connect to this WAN. Contractor is

required to provide BACnet Objects and services and/or LonMark Objects at the

Local Supervisory LAN via BACnet or LonTalk over IP This Ethernet LAN will be

connected to the WAN to manage the exchange of data and alarms with the EBI

Server including, but not limited to, trends, alarms, schedules, parameters, variables,

and real time data from the local system. If the Local Supervisory LAN does notinherently use BACnet, LonTalk over IP Contractor shall provide a gateway(s),

routers, hardware, software, etc. necessary to translate and facilitate services from

the local protocol to the EBI. Refer to Section 15954 for requirements:

USC control systems must always have a 100Mbps, Ethernet Supervisory LAN. It will be

provided by the EMCS Contractor. The following paragraph assumes a dedicated EMCS-

installed LAN. Edit accordingly if use of the building IT LAN will pertain.

2. Local Supervisory LAN: The Local Supervisory LAN shall be an Ethernet-based,100 Mbps LAN connecting Primary Control LANs and OWS/POTs. The LAN

serves as the inter-BC gateway and OWS-to-BC gateway and communications path

and as the connection point for the EBI. Contractor shall provide this as a dedicated

LAN for the control system. LAN shall be IEEE 802.3 Ethernet over Fiber or

Category 5 cable with switches and routers that support 100 Mbps throughput.Power-line carrier communication shall not be acceptable for communications. The

higher level layers of this network shall be one of the following at Contractors

option:

a) BACnet Supervisory LAN: BACnet/IP as defined in Addendum A (Annex J)of the BACnet standard, and shall share a common network number for the



18/119



Ethernet backbone, as defined in BACnet. Point/Object naming conventions

are specified in 15955 - Part III.

b) LonWorks Supervisory LAN: Individual Primary control LonTalk Networksrouted over IP using LonTalk to IP routers such as I-Lon, Coactive or

equivalent. Point/Object naming conventions are specified in 15955 - Part III.

3. Primary Controller LAN (Primary LAN): High-speed, peer-to-peercommunicating LAN used to connect AACs, ASCs and Building Controllers (BCs)

and communicate exclusively control information. Network speed vs. the number of

controllers on the LAN shall be dictated by the response time and trending and other

requirements as specified in Section 15953. Acceptable technologies include:

a) Ethernet (IEEE802.3)b) ARCNET (IEEE802.4)

The following allows LonWorks Networks but specifically restricts the application to a 78 kbps

Free Topology platform. This is to be required for maximum interchangeability. A LonTalk

LAN is considered a Primary Controller LAN.

c) LonTalk: The LonTalk standalone EMCS shall be comprised of a network ofAACs and ASCs, supporting LonTalk protocol (EIA 709.1) and twisted pair,

free topology (TP/FT-10) transceivers (EIA 709.3). The secondary network

shall communicate at 78 kbps. Each secondary TP/FT-10 network may support

up to 64 communicating LonTalk devices without segmentation subject to the

requirements for response time, trending and bandwidth utilization.

d) Proprietary: Manufacturers proprietary protocol.Most systems use a tiered LAN architecture to accomplish the control network. Lower level

devices are connected to a lower powered network. This is not applicable to a LonTalk network

as it is all peer-to-peer relatively high speed, however it can be segmented by routers.

4. Secondary Controller LAN (Secondary LAN): Network used to connect AACs,or ASCs. These can be Master Slave/ Token Passing or polling, in addition to those

allowed for Primary Controller LANs. Network speed vs. the number of controllers

on the LAN shall be dictated by the response time and trending requirements.

D. Dynamic Data Access: Any data throughout any level of the network shall be available toand accessible by all other devices, Controllers and OWS/POT, whether directly

connected or connected remotely.

Coordinate the following with the needs of the facility. The browser-based requirement will

limit systems available but that list is dwindling as most manufacturers are providing some

form of browser-based access.E. Remote Data Access: The system shall support the following methods of remote access

to the building data.

1. Dial-in via minimum of a 56k modem. Dial-in connection shall allow access to allcontrol system facilities and graphics with appropriate password. The Universityshall provide and pay for the digital grade voice line to support this remote

connection.



19/119



2. DSL. All workstations shall be equipped with standard 100 megabit Ethernet cards;the University at its option may elect to use DSL or other broadband service to

access the system.

F. The communication speed between the controllers, LAN interface devices, and operatorinterface devices shall be sufficient to ensure fast system response time under any loadingcondition. Contractor shall submit guaranteed response times with shop drawings

including calculations to support the guarantee. In no case shall delay times between an

event, request, or command initiation and its completion be greater than those listed

herein. Contractor shall reconfigure LAN as necessary to accomplish these performance

requirements.:

1. 5 seconds between a Level 1 (critical) alarm occurrence and enunciation at the EBIworkstation.

2. 10 seconds between a Level 2 alarm occurrence and enunciation at the EBIworkstation.

3. 20 seconds between and a Level 3-5 alarm occurrence and enunciation at the EBIworkstation.

4. 10 seconds between an operator command via the EBI workstation to change asetpoint and the subsequent change in the controller.

5. 5 seconds between an operator command via the EBI workstation to start/stop adevice and the subsequent command to be received at the controller.

6. 10 seconds between a change of value or state of an input and it being updated onthe EBI workstation.

7. 10 seconds between an operator selection of a graphic and it completely painting thescreen and updating at least 10 points.

G. Operator Workstation (OWS) or PORTABLE OPERATOR TERMINAL (POT):This shall be a computer (or computers) that maintain the systems configuration and

programming database. It shall be integrated with the existing EBI system. It shall hold

the backup files of the information downloaded into the individual controllers and as such

support uploading and downloading that information directly to/from the controllers. It

shall also act as a control information server to non-control system based programs, and

shall be located at the building or buildings being controlled. It shall allow secure

multiple-access to the control information. Refer to Section 15952 - EMCS Operator

Interfaces for its requirements.

H. The Operator Interface shall provide for overall system supervision, graphical userinterface, management report generation, alarm annunciation, and remote monitoring.

Refer to Section 15952 EMCS Operator Interfaces.

I. The BCs, AACs, ASCs, shall monitor, control, and provide the field interface for allpoints specified. Each BC, AAC, or ASC shall be capable of performing all specifiedenergy management functions, and all DDC functions, independent of other BCs, AACs,

or ASCs and operator interface devices as more fully specified in Section 15953 - EMCS

Field Panels.

J. Systems Configuration Database: The system architecture shall support maintainingthe systems configuration database on a server or workstation on the Local Supervisory



20/119



LAN. User tools provided to the University shall allow configuring, updating,

maintaining, etc. current configurations and settings whether they are initiated at the

server or the end device.

1. Database Schema shall be published and provided to the University to facilitate easyaccess to the data.

2. Database shall be ODBC compliant or a data access driver shall be provided to actas an ODBC or OLE DB data provider.

The following is very crucial to the level of systems integrator independence. Most third-

party LonWorks configuration and management tools create/work from the LNS format (two

tier client/server). Older LonWorks systems use a single tier API database. Some popular

tools do not even use any LonWorks standard for the configuration database. The following

will eliminate those that do not use LNS.

3. For LonWorks systems the SCD and associated network services shall be LonWorksNetwork Services (LNS) (latest version) compliant. The Network Management

Application shall be LonMaker for Windows (latest released version) service tool

(including hardware, software and any peripheral devices required) and is to be usedfor commissioning and management of the LonTalk control architecture. The

network management service tool shall remain on the project as the property of the

University. A copy of the LonTalk network database shall be archived on the

service tool, documenting system bindings and node addressing. In addition all

system variables shall have a plain English language description for each variable.

This service tool shall be used for all system maintenance and expansion, so that the

network database backup remains current

K. Interruptions or fault at any point on any Primary Controller LAN shall not interruptcommunications between other nodes on the network. If a LAN is severed, two separate

networks shall be formed and communications within each network shall continue

uninterrupted.L. All line drivers, signal boosters, and signal conditioners etc. shall be provided as

necessary for proper data communication.

M. Anytime any controllers database or program is changed in the field, the controller shallbe capable of automatically uploading the new data to the CSS.

1.12 WARRANTY MAINTENANCEA. Contractor shall warrant all products and labor for a period of {Insert warranty period}

after Final Acceptance.

B. The University reserves the right to make changes to the EMCS during the warrantyperiod. Such changes do not constitute a waiver of warranty. The Contractor shallwarrant parts and installation work regardless of any such changes made by the

University, unless the Contractor provides clear and convincing evidence that a specific

problem is the result of such changes to the EMCS. Any disagreement between the

University and the Contractor on such matters shall be subject to resolution through the

contract Disputes clause.



21/119



C. At no cost to the University, during the warranty period, the Contractor shall providemaintenance services for software and hardware components as specified below:

1. Maintenance services shall be provided for all devices and hardware specified insections 15951 through {Insert Additional Specification Sections as applicable}.

Service all equipment per the manufacturers recommendations. All devices shall becalibrated within the last month of the warranty period.

The following requirements are very lax and would pertain to a non- critical office building.

AE shall edit these as applicable to a given project.

2. Emergency Service: Any malfunction, failure, or defect in any hardware componentor failure of any control programming that would result in property damage or loss

of comfort control shall be corrected and repaired following telephonic notification

by the University to the Contractor.

a) Response by telephone to any request for service shall be provided within two(2) hours of the University's initial telephone request for service.

b)

In the event that the malfunction, failure, or defect is not corrected through thetelephonic communication, at least one (1) hardware and software technician,

trained in the system to be serviced, shall be dispatched to the University's site

within eight (8) hours of the University's initial telephone request for such

services, as specified.

3. Normal Service: Any malfunction, failure, or defect in any hardware component orfailure of any control programming that would not result in property damage or loss

of comfort control shall be corrected and repaired following telephonic notification

by the University to the Contractor.

a) Response by telephone to any request for service shall be provided within eight(8) working hours (contractor specified 40 hr per week normal working period)

of the University's initial telephone request for service.

b) In the event that the malfunction, failure, or defect is not corrected through thetelephonic communication, at least one (1) hardware and software technician,

trained in the system to be serviced, shall be dispatched to the University's site

within three (3) working days of the University's initial telephone request for

such services, as specified.

4. Universitys Telephonic Request for Service: Contractor shall specify a maximumof three telephone numbers for the University to call in the event of a need for

service. At least one of the lines shall be attended at any given time. Alternatively,

pagers can be used for technicians trained in system to be serviced. One of the three

paged technicians shall respond to every call within 15 minutes.

5. Technical Support: Contractor shall provide technical support by telephonethroughout the warranty period.

6. Preventive maintenance shall be provided throughout the warranty period inaccordance with the hardware component manufacturer's requirements by fully

qualified hardware and software technicians. USC FMS shall be contacted when

any technician is performing service on site.



22/119



1.13 DELIVERY, STORAGE, AND HANDLINGA. Provide factory-shipping cartons for each piece of equipment and control device.

Maintain cartons during shipping, storage and handling as required to prevent equipmentdamage, and to eliminate dirt and moisture from equipment. Store equipment and

materials inside and protect from weather.

1.14 LISTING AND LABELINGA. The EMCS and components shall be listed by Underwriters Laboratories (UL 916) as an

Energy Management System.

NOTE: The following should only be included when it is applicable, namely when the systemis part of an engineered smoke control system or where the system will be specified to provide

the firemens override panel in the Fire Command Center which is typical for a high rise

building. Smoke control and fire alarm systems should be segregated from the EMCS in any

new installations. Note that the listing may not be available with many BACnet and LonWorks

products; in cases of retrofits where the system must perform smoke control functions,permitting a gateway to a proprietary system which has this listing may be necessitated.

Modify the applicability of this listing as appropriate.

B. The EMCS shall be listed by Underwriters Laboratories (UUKL 864) for supervisedsmoke control.

PART II. PRODUCTS2.01 MATERIALS AND EQUIPMENT

A. Materials shall be new, the best of their respective kinds without imperfections orblemishes and shall not be damaged in any way. Used equipment shall not used in any

way for the permanent installation except where drawings or specs specifically allow

existing materials to remain in place.

2.02 UNIFORMITYA. To the extent practical, all equipment of the same type serving the same function shall be

identical and from the same manufacturer



23/119


Energy Management Control System (EMCS) General 15950 - 192000 FACILITY DYNAMICS ENGINEERING

PART III. EXECUTION3.01 INSPECTION

A. Examine areas and conditions under which control systems are to be installed. Do notproceed with work until unsatisfactory conditions have been corrected in manneracceptable to Installer.

3.02 INSTALLATION OF CONTROL SYSTEMSA. General: Install systems and materials in accordance with manufacturer's instructions,

roughing-in drawings and details shown on drawings.

B. Refer to additional requirements in other sections of this specification.Digital control stations should specifically be shown on the drawings. You should select

appropriate wall/floor locations that minimize wire and tube runs and coordinate these

locations with other disciplines. If the project is a control renovation, locate spare breakersin a power panel where the control contractor can obtain 120V power and show it on the

floor plans

3.03 DIGITAL CONTROL STATIONS , CONTROLLER QUANTITY AND LOCATIONAE shall designate locations for control stations and specifically reserve wall/floor space and

indicate it on the drawings and coordinate it with other trades. If you are using LonPoint

devices, this does not necessarily apply as the point devices may be distributed. Preferably

you will have the electrical contract provide power (normal, emergency or uninterruptible as

applicable) and then delete the requirement for this contractor to provide the power.

A. Individual Digital Control Stations (DCS) are referenced to indicate allocation of pointsto each DCS and DCS location. Digital control stations shall consist of one or multiplecontrollers to meet requirements of this specification.

B. Where a DCS is referenced, Contractor shall provide at least one (1) controller, andadditional controllers as required, in sufficient quantity to meet the requirements of this

Specification. Restrictions in applying controllers are specified in Section 15953:

EMCS Field Panels. This Contractor shall extend power to the DCS from an

acceptable power panel. If the control contractor wishes to further distribute panels to

other locations, control contractor is responsible for extending power to that location

also. Furthermore, contractor is responsible for ensuring adequate locations for the

panels that do not interfere with other requirements of the project and maintain

adequate clearance for maintenance access.

The following is a critical matter for performance and functionality that is left to the

discretion of the AE. The concept of standalone boundaries of a given system has long

been a basic principle behind the requirements for a distributed system. The advent of the

Lon Smart Devices and general purpose modules blur the distinction in some peoples minds.

The question is whether you accept that the Network is the Controller, which is a concept


24/119



at the heart of a fully-distributed LON system. If you accept that principal, you can edit this

subsection to allow it accordingly and release restrictions placed on that system.

It is imperative for the AE to define the limits of standalone functionality as it pertains to thespecific systems being installed. You may do that via the control drawings and, for instance,

say that all elements of any given control schematic must be standalone (with clarifications)

or you can do that in a narrative in the specification. However it is done, it is critical thatthis not be overlooked and that it be carefully coordinated into a practical requirement.

C. Contractor shall locate DCSs as referenced. It is the Contractor's responsibility toprovide enough controllers to ensure a completely functioning system, according to the

point list and sequence of operations.

D. Contractor shall provide a minimum of the following:1. One DCS (including at least one controller) in each chilled water plant mechanical

room.

2. One controller for each air handler located in applicable mechanical room.3. One controller shall be provided for each terminal unit unless indicated otherwise.

3.04 SURGE PROTECTIONA. The Contractor shall furnish and install any power supply surge protection, filters, etc.

as necessary for proper operation and protection of all BCs, AAC/ASCS operator

interfaces, printers, routers, gateways and other hardware and interface devices. Allequipment shall be capable of handling voltage variations 10% above or below

measured nominal value, with no affect on hardware, software, communications, and

data storage.

3.05 DEMOLITION AND REUSE OF EXISTING MATERIALS AND EQUIPMENT {Includeif applicable}

Reuse of existing controls must be carefully coordinated by the AE. What stays and goes

must be clear. As applicable, expand/edit this section to indicate what is allowed for reuse.

The bottom line is assumptions will generally have to be made for bidding, but final

acceptance of an existing device will not occur until the contractor tests it.

A. Contractor shall assume that existing equipment that specifically is indicated to bereused is in good condition and is operable. Contractor, during the course of work,

shall inspect these devices and determine if any devices are in need of replacement or

repair. Contractor shall prepare an itemized list of suggested repairs/replacement. This

repair/replacement will be at the discretion of the University and will be accomplished

by expanding this contract.

B.

Existing wire, conduit, and control panel cabinets may be reused at the contractorsdiscretion, but only if such materials or equipment comply with the applicable

specification for new materials and equipment. Such materials shall not be reused if

visibly damaged or otherwise unsuitable for the intended service.

C. Where such materials are reused, the contractors shop drawings shall reflect theexisting wiring designation. If existing labeling is illegible or otherwise does not



25/119



comply with the applicable specification for labeling, wiring runs shall be relabeled in

accordance with the requirements specified elsewhere.

D. Existing pneumatic tubing located between the existing EMCS panels and thepneumatic operators shall not be reused; however, conduit for such tubing may be

reused. All other pneumatic tubing may be reused, but only if such materials comply

with the applicable specification for new materials. Materials shall not be reused ifvisibly damaged or otherwise unsuitable for the intended service. All pneumatic tubing

to be reused shall be pressure tested and all leaks shall be repaired. All reused

pneumatic tubing shall be purged with dry air or nitrogen.

E. The existing pneumatic main air supply system shall be modified as required andreused to serve existing pneumatic controls that are to remain, and shall be extended as

necessary to serve new pneumatic controls. Where existing pneumatic controls are

removed, main air piping shall be removed back to the point of connection to the main

air supply which remains in use, and shall be capped or plugged.

F. Existing valves and dampers and their operators shall be reused, except where noted tobe removed or provided as new. Contractor shall lubricate all damper linkages of

dampers being controlled under this project.

G. Other materials and equipment not specifically mentioned herein may be reused only ifspecifically allowed by indications on the drawings.

H. For HVAC systems which are indicated to receive a new EMCS, all existing materialsand equipment associated with the existing pneumatic controls and EMCS shall be

removed unless otherwise specified or indicated to remain, or unless reused in

accordance with the above requirements, except for the following: 1) conduit and

electrical boxes (but not wiring within conduit) may remain in place if not reused

(leave a pull line); 2) inaccessible pneumatic tubing may remain in place if not reused.Existing materials and equipment to be removed shall be removed subject to the

requirements in paragraph Sequence of Work. For HVAC systems, which are not to

receive a new DDC EMCS, the existing pneumatic control system shall remain fully

functional.

Include the following only when applicable. Obviously this will depend on the necessity of

continuous operations and this is only a template. This item will typically have to be

extensively customized for each project.

3.06 SEQUENCE OF WORK FOR EXISTING SYSTEMS CONVERSIONA. General: All work involving changeover of control functions from existing pneumatic

control system to the new DDC EMCS shall be performed in accordance with the

following sequence in order to minimize the duration of equipment outages. The

following descriptions are intended to indicate the sequence in which the work shall beperformed, not to define fully the scope of the work.

B. Install operators terminal, peripherals, graphic software, and LAN prior to placing anyequipment under the control of the new EMCS.



26/119



C. Work which requires shutting down a pump motor, fan motor, or chiller shall beconsidered a utility shutdown and shall be subject to the restrictions specified in

Section {Insert Appropriate Section Number}.

D. The following sequence applies to an individually controlled HVAC subsystem, suchas an air handling unit. Only one such system shall be placed under manual control (as

described below) at any given time.

1. Install controllers adjacent to (or within) existing control panel. Programmingshall be complete (except for loading and debugging) prior to installation. Install

all field devices, which do not require interruption of the existing control system.

2. Install all conduit, wiring, and pneumatic tubing which does not requireinterruption of the existing control system.

3. Provide temporary variable pressure type hand pumps at each pneumaticallycontrolled output, for temporary use by Universitys maintenance and operation

contractor personnel. Schedule this step at least 48 hours in advance with the

Building Engineer.

4. Remove existing controls including wiring, conduit, and tubing (except materialsto be reused in accordance with provisions specified elsewhere) which must beremoved to facilitate installation of new EMCS materials and equipment.

5. Remove existing digital control system points (if applicable). Install and calibrateremainder of new EMCS materials and equipment for this subsystem. Load

controller software. Connect controller(s) to LAN.

6. Perform all field testing and calibration that does not require connection ofpermanent pneumatic outputs.

7. Remove temporary hand pumps and install permanent pneumatic outputconnections. Place the system under the control of the new DDC/EMCS

equipment. Conclude field testing and submit field testing report prior to placing

the next subsystem under temporary manual control. The University shall be

given a password with a priority level that allows monitoring (but not control untilnotification of substantial completion has been approved).

8. Remove remaining existing pneumatic and digital control system materials andequipment (except materials to be reused in accordance with provisions specified

elsewhere). All existing digital controls equipment for those subsystems that have

not yet been converted shall remain intact, on-line, and fully functional.

9. Schedule work in occupied spaces 10 days in advance with the Universitysrepresentative. Scheduling shall not be required for work in equipment rooms,

electrical closets, and similar service areas.

3.07 CONTROL POWER SOURCE AND SUPPLYIt is preferable to have the Division 16 contractor supply power to DCS locations and providethe appropriate level of power of all control system components as located by the AE. For

instance, it is required to at least have emergency power (and sometimes uninterruptible

power when available) at critical controllers, control system servers, routers, workstations

etc. However, this section if mainly for retrofits where no Div 16 contractor applies.



27/119


Energy Management Control System (EMCS) General 15950 - 232000 FACILITY DYNAMICS ENGINEERING

A. Section 15950 Contractor shall extend all power source wiring required for operation ofall equipment and devices provided under Sections 15950 through 15955 and

Sequences of Operation.

The following item will have to be customized for each system and project. The

consideration is where to power controllers from. For distributed controllers that are

associated with one unit, it is convenient to power them along with the system so thecontroller can take action based on the presence of power. However on large centralized

panels, it is required to provide a reliable source of emergency power that serves the

equipment being controlled and then provide for individual monitoring of the various

systems power sources by the controller. The object here is to make a robust system that

does not interpret power failures as device failure and therefore in some instances have to

take down the unit for manual acknowledged reset. This can compromise reliability.

B. General requirements for obtaining power include the following:1. Obtain power from the electrically most proximate 120v breaker emergency power

panel. Connect to a dedicated breaker designated for use by the EMCS only.

Breaker shall be of the proper size per NEC.

2. Where control equipment is located inside a new equipment enclosure, coordinatewith the equipment manufacturer and feed the control with the same source as theequipment. If the equipments control transformer is large enough and of the

correct voltage to supply the controls it may be used. If the equipments control

transformer is not large enough or of the correct voltage to supply the controls

provide separate transformer

3. Standalone Functionality: Refer to Section 15953.

The AE shall carefully coordinate the training requirements with the needs of USCs

facilities staff. Expansions of existing systems obviously require less training than brand

new systems. The following generally outlines an on-site training session for which you

always want some basic site-specific training on-site. The more advanced training may bebetter provided off site on a case-by-case basis. Edit to suit project.

3.08 EMCS START UP, COMMISSIONING AND TRAININGA. Refer to Section 15959

3.09 SEQUENCE OF OPERATIONA. Refer to Section {Insert applicable Specification Section} - Sequences of Operation

END OF SECTION 15950


28/119


SECTION 15951 - EMCS BASIC MATERIALS, INTERFACE DEVICES, AND

SENSORS

Note to the Design AE: The AE and project manager should discuss the project with USC.There is a Preface document describing how to employ this and other USC controls-relatedGuide Specifications. The AE is instructed to consult the Preface document for guidance onthe generic BACnet nature of this specification, methods for deleting non-applicable text, andthe use and deletion of Editors Notes before proceeding to customize this specification.

Refresh the table of contents after editing section

PART I. GENERAL ............................................................................................................................................... 3

1.01 SECTIONINCLUDES .................................................................................................................................. 31.02 RELATEDDOCUMENTS ........................................................................................................................... 31.03 DESCRIPTIONOFWORK .......................................................................................................................... 31.04 WORKBYOTHERS .................................................................................................................................... 4

PART II. PRODUCTS ......................................................................................................................................... 42.01 MATERIALSANDEQUIPMENT ............................................................................................................... 42.02 CONTROL VALVES.......................................................................................................................................... 72.03 CONTROL DAMPERS ..................................................................................................................................... 112.04 ACTUATORS ............................................................................................................................................. 132.05 GENERALFIELDDEVICES ..................................................................................................................... 152.06 TEMPERATURESENSORS(TS) .............................................................................................................. 162.07 TEMPERATURE TRANSMITTERS .................................................................................................................... 172.08 HUMIDITYTRANSMITTERS .................................................................................................................. 182.09 DIFFERENTIALPRESSURETRANSMITTERS(DP) ............................................................................. 182.10 VALVE BYPASS FORDIFFERENTIAL PRESSURE SENSORS.............................................................................. 192.11 DIFFERENTIALPRESSURESWITCHES(DPS) ..................................................................................... 202.12 PRESSURESWITCHES(PS) ..................................................................................................................... 20

2.13 TRANSDUCERS .............................................................................................................................................. 202.14 CURRENT SWITCHES (CS) ............................................................................................................................ 212.15 CURRENTTRANSFORMERS(CT) .......................................................................................................... 222.16 OUTDOORAIRSTATICPRESSURESENSINGTIP ............................................................................... 232.17 CONTINUOUS LEVEL TRANSMITTERS ........................................................................................................... 232.18 ULTRASONIC FLOW METERS FOR LIQUID, STEAM AND GAS SERVICE ............................................................. 232.19 MAGNETIC FLOW METERS FORWATERSERVICE ......................................................................................... 242.20 VENTURI FLOWMETERFORWATERSERVICE .................................................................................... 262.21 AIRFLOWMEASURINGSTATIONS(AFMS) ........................................................................................ 272.22 AIRVELOCITY PRESSURE SENSORS (INSERTION TYPE) ................................................................................ 272.23 CO2SENSORS/TRANSMITTERS (CO2) ........................................................................................................... 282.24 PNEUMATICCONTROLCOMPONENTS ............................................................................................... 282.25 ELECTRICCONTROLCOMPONENTS ................................................................................................... 28

2.26 REFRIGERANT MONITOR.............................................................................................................................. 302.27 SMOKE CONTROL/FIREMANS OVERRIDE PANEL ......................................................................................... 322.28 NAMEPLATES ........................................................................................................................................... 322.29 TESTINGEQUIPMENT ............................................................................................................................. 33

PART III. EXECUTION ..................................................................................................................................... 34

3.01 INSPECTION .............................................................................................................................................. 343.02 INSTALLATIONOFCONTROLSYSTEMS ............................................................................................ 343.03 REFRIGERANT MONITOR.............................................................................................................................. 36

EMCS Basic Materials, Interface Devices, and Sensors 15951- 12000 FACILITY DYNAMICS ENGINEERING


29/119


EMCS Basic Materials, Interface Devices, and Sensors 15951- 22000 FACILITY DYNAMICS ENGINEERING

7/29/2019 25.00.00 HVAC Controls M