15903_Direct_Digital_Controls_revised.pdf

Energy Monitoring and Control System Ph 2 FA4626-18-R-0013 Malmstrom AFB NZAS 14-3000

134-240464 Malmstrom Air Force Base Design of Energy Management Control Systems (EMCS) – Phase 2 -

DIRECT DIGITAL CONTROL SYSTEM

15903 - 1

SECTION 15903

DIRECT DIGITAL CONTROL SYSTEM

PART 1 - GENERAL

1.1 SYSTEM DESCRIPTION

A. Furnish all labor, materials, equipment, service, and training necessary for a complete, operational and fully commissioned direct digital control system for the facilities identified on the Contract Drawings.

Requirements include but are not limited to HVAC system control, and utility monitoring. The system shall use the BACnet protocol at the field bus level of the Architecture and at the TCP/IP level.

B. The Work consists of a complete direct-digital temperature control and monitoring system with all sensors, controllers, I/O operator devices, valves, dampers, damper motors, relays, control cabinet, etc. to perform the functions as specified in the sequence of control.

C. Furnish all labor, materials, equipment, service and training necessary to integrate the existing direct digital control systems into the new energy management and control system. The field bus and TCP/IP protocol for the existing system is BACnet.

D. All control wiring required for the temperature control system and which is not indicated on Contract Drawings to be furnished under Division 16, shall be included in this Section of the Specifications.

Wiring shall be in accordance with the National Electrical Code and Division 16 of these Specifications.

Wiring and conduit, for Section 15903 systems, installed under Division 16 shall be fully coordinated by the Contractor.

1.2 RELATED DOCUMENTS

A. Drawings and general provisions of the Contract, including General and Supplementary Conditions and Division 1 apply to this Section.

1.3 CODES, STANDARDS AND REFERENCES:

A. The publications listed below form a part of this Specification to the extent referenced. The publications are referred to within the text by the basic designation only.

1. Air movement and control association (AMCA).

2. American national standards institute (ANSI).

3. American society of heating, refrigeration and air-conditioning engineers (ASHRAE).

a. ASHRAE 135 BACnet Standard - Latest Version at time of bid.

4. Federal Communications Commission (FCC).

5. Institute of Electrical and Electronics Engineers (IEEE).

6. International Organization for Standardization (ISO).

7. National Electrical Manufacturers Association (NEMA).

8. National Fire Protection Association (NFPA).

9. Underwriters Laboratories (UL).

10. U.S. National Archives and Records Administration (NARA).

11. Engineering Technical Letter (ETL) 11-1.

12. Unified Facilities Guide Specifications (UFGS) 25 10 10

1.4 SUBMITTALS

A. Shop Drawings and Product Data shall meet the requirements of Section 01340.

B. Shop Drawings shall be 22 IN by 34 IN, landscape, bound on the left edge. They shall be produced with AutoCAD version 2008. System Drawings shall be complete in all respects, bound together, consecutively numbered, dated and initialed or signed by the designer. The Drawings shall include title blocks on each sheet bearing the project title, a legend of all symbols used and schedules listing all equipment to be installed. All devices, instruments and equipment to be installed shall be shown on the Drawings. Provide a copy of complete submittal on CD.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 2

C. Equipment booklets shall include data for each item shown on the drawings. Each item shall be identified in the booklet with the same tag number or abbreviation that appears on the system Drawings and schedules. The specific size and model of each item to be installed shall be clearly indicated.

D. Organize the packages by building.

E. All text based documents and product data sheets shall be 8-1/2 IN by 11 IN format bound on the left edge. To the maximum extent possible, Adobe Acrobat shall be used to produce the documents in a portable document format (PDF).

F. Software files shall be submitted on fully labeled CDs that shall include a table of contents file in PDF format that provides a description of all of the files on the CD.

G. Submittals Prior To Construction:

1. Shop Drawings:

a. Five level topology drawing showing interconnections, data flow, components and external connections.

b. System Architecture Design Diagram:

1) BACnet point addressing scheme. With number ranges defined.

2) This is a riser diagram that shall show the IP layer and all of the field bus layers.

3) It shall show each computer, printer, router, repeater, controller, and protocol translator that is connected to either the IP layer or any of the field busses.

4) This diagram shall include the existing control system that is to be integrated into the common enterprise level system.

5) Each component that is shown shall have a name that is representative of how it will be identified in the completed database and the manufacturer’s name and model number.

6) The physical relationship of one component to another component shall reflect the proposed installation.

a) Example: If AHU1 controller is the closest controller to the Building Controller on the field bus, then this device shall be shown as the first device on the riser diagram just below the Building Controller.

7) This diagram shall not include power supplies, sensors or end devices.

c. Layout Design Drawing for each control panel:

1) The layout drawing shall be to scale with all devices shown in their proposed positions.

2) All control devices shall be identified by name.

3) All terminal strips and wire channels shall be shown.

4) All control transformers shall be shown.

5) All 120 Vac receptacles shall be shown.

6) All IP connection points shall be shown.

d. Wiring Design Diagram for each control panel.

1) The control voltage wiring diagram shall clearly designate devices powered by each control transformer. If the control devices use half wave power, the diagram shall clearly show the consistent grounding of the appropriate power connection. All wire identification numbers shall be annotated on the diagram.

2) The Field Bus wiring diagram shall clearly show the use of the daisy chain wiring concept, the order in which the devices are connected to the Field Bus, and the location of end of segment termination devices. All wire identification numbers shall be annotated on the diagram.

3) If shielded communication wiring is used, the grounding of the shield shall be shown.

4) The terminal strip wiring diagram shall identify all connections on both sides of the terminal strip. Wiring label numbers for all wiring leaving the control panel shall be annotated on the diagram.

e. Wiring Design Diagram for individual components (controllers, protocol translators, etc.): The wiring diagram for each component shall identify all I/O, power, and communication wiring and the locations on the terminal blocks to which the wires are landed.

1) Example: Fan Status sensor is wired from terminals 5/6 on the controller to terminals 17 and 18 on the terminal strip.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 3

f. Installation Design Detail for each I/O device.

1) A drawing of the wiring details for each sensor and/or end device.

2) For devices with multiple quantities, a standard detail may be submitted.

g. A System Flow Design Diagram for each controlled system.

1) A two-dimensional cross sectional diagram showing key components such as fans, coils, dampers, valves, pump, etc.

2) Identify the locations and names of all sensors and end devices that are associated with the control system. Label the panel name and terminal numbers where the connections are landed.

3) A legend shall be provided for all symbols used.

2. Data:

a. BACnet Compliance Documentation:

1) The Protocol Implementation Conformance Statement for each component. A complete

Protocol Implementation Conformance Statement (PICS) that shall clearly define the communication transport, devices, BACnet Interoperability Building Blocks (BIBBS), services, objects, and object properties supported by the system will be provided to the Contracting Officer’s Representative for review during the approval process.

2) The Protocol Implementation Conformance Statement for the Work Station.

b. Direct Digital Control System Hardware Technical Data.

1) A complete bill of materials of equipment to be used indicating quantity, manufacturer, and model number.

2) Manufacturer’s description and technical data for each unique device to include performance curves, product specification sheets, and installation instructions. When a manufacturer’s data sheet refers to a series of devices rather than a specific model, the data specifically applicable to the project shall be highlighted or clearly indicated by other means.

3) This requirement applies to:

a) Controllers.

b) Transducers/Transmitters.

c) Sensors.

d) Actuators.

e) Valves.

f) Relays and Switches.

g) Control Panels.

h) Power Supplies.

i) Batteries.

j) Operator Interface Equipment.

c. An Instrumentation List for each controlled system.

1) The list shall be in a table format.

2) Include name, type of device, manufacturer, model number, and product data sheet number.

d. Sequence of Control: A sequence of control for each system being controlled. Include the following as a minimum.

1) Process control sequence for each end device.

2) Supervisory logic sequence of control for each system.

3) The impact of each global application program on the sequence of control (Example:

Demand Control).

4) A list of all physical inputs and outputs associated with each sequence.

5) Within the sequence of control, all application parameters that are to be user adjustable from an OWS shall be annotated with (adj) after the name of the parameter. This shall include set points, reset schedule parameters, calibration offsets, timer settings, control loop parameters such as gain, integral time constant, sample rates, differentials, etc.

6) Within the sequence of control, all calculated values that are to be viewable at the OWS shall be annotated with (rpt) after the name.

7) All points that shall be subject to manual control from an operator workstation.

8) A list of all alarm points, a description of the alarm and a description of the alarm criteria.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 4

9) A list of all variables for which historical trending will be applied, the sample rates and any criteria used to start and stop the historical trending.

e. Data Flow Map:

1) A list of the device to device data flow. This shall not include the flow of data from devices to the presentation system.

2) Include in Microsoft Excel format:

a) Description of the variable.

b) Sending device.

c) Receiving device.

f. Graphic Pages: Submit a sample graphic page for each type of page described in the specification section on graphic pages.

3. A minimum of two (2) submittals shall be required. The first set shall be preliminary, which shall be reviewed jointly by the controls Contractor and the Contracting Officer’s Representative at the site.

The final submittals shall be prepared following the joint review.

H. Submittals During Construction:

1. Training Manuals for each Training Course:

a. Submit the following 6 weeks in advance of the training:

1) List of training objectives.

2) Outline of the course with time allocations per topic.

3) Training presentation material (slides, word documents, etc.).

4) Copy of training reference material (product manuals to be used, etc.).

5) Schematic of the training equipment to be used with model numbers on each component.

6) A description of the measurement devices to measure training effectiveness (quizzes, programming exercises, course exam).

7) Instructor’s name and resume with an emphasis on experience in presenting training programs.

b. Submit the following within 3 weeks of training completion:

1) List of attendees.

2) Performance scores on the assessment devices.

2. Startup Testing Plan: Submit a start up testing plan for each unique system.

a. The purpose of a startup test is to demonstrate the “completeness” of the physical tasks associated with installation and the physical performance of the components.

b. For each task on the startup test checklist, the plan shall require the technician to enter his or her initials and the date the test was completed along with any recorded data such as voltages, offsets, or tuning parameters. Any deviations from the submitted installation plan shall also be recorded.

c. Required elements of the startup testing include:

1) Measurement of voltage sources, primary and secondary.

2) Verification of proper controller power wiring.

3) Verification of component inventory when compared to the submittals.

4) Verification of labeling on components and wiring.

5) Verification of connection integrity and quality (loose strands and tight connections).

6) Verification of bus topology, grounding of shields and installation of termination devices.

7) Verification of point checkout.

a) Each I/O device is landed per the submittals and functions per the sequence of control.

b) Analog sensors are properly scaled and a value is reported.

c) Binary sensors have the correct normal position and the state is correctly reported.

d) Analog outputs have the correct normal position and move full stroke when so commanded.

e) Binary outputs have the correct normal state and respond appropriately to energize/de-energize commands.

8) Documentation of analog sensor calibration (measured value, reported value and calculated offset).

9) Documentation of Loop tuning (sample rate, gain and integral time constant).

d. Submit at least 4 weeks prior to any scheduled start-up tests.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 5

3. Startup Testing Report.

a. Startup testing reports shall be submitted on a per system basis.

b. Startup testing reports shall be the documented results of the executed startup testing plans.

4. Performance Verification Testing Plan: Submit a verification plan for each system.

a. The purpose of a performance verification test is to ensure that the system performs in accordance with the sequence of control. For each end device that is controlled, there shall be a series of step by step cause and effect tests to verify each aspect of the sequence of control. A sample sequence of control with corresponding performance verification test is included as Appendix B.

b. PVT Procedures: The performance verification test procedures shall explain, step-by-step, the actions and expected results that will demonstrate that the control system performs in accordance with the sequences of operation, and other contract documents. The PVT Procedure shall describe a methodology to measure and trend the network bandwidth usage on the network backbone and compare it to the Bandwidth Usage Calculation submittal. A control system performance verification test equipment list shall be included that lists the equipment to be used during performance verification testing. The list shall include manufacturer name, model number, equipment function, the date of the latest calibration, and the results of the latest calibration.

c. A performance verification test shall also be defined for the operator interaction with the system.

Test elements shall be written to require the verification of all operator interaction tasks including but not limited to the following:

1) Login and user settings.

2) Graphics navigation.

3) Trend data collection and presentation.

4) Alarm handling, acknowledgement, and routing.

5) Time schedule editing.

6) Application parameter adjustment.

7) Manual control.

8) Report execution.

9) Automatic backups.

10) Web Client access.

d. Submit at least 4 weeks prior to the scheduled execution of the test.

I. Submittals after Construction:

1. The following is a list of post construction submittals that shall be updated to reflect any changes during construction and re-submitted as “As-Built”.

a. System Architecture Drawing.

b. Layout Drawing for each control panel.

c. Wiring diagram for each control panel.

d. Wiring diagram for individual components.

e. System flow diagram for each controlled system.

f. Instrumentation list for each controlled system.

g. Sequence of control.

h. Detailed points list.

i. Binding map.

2. Operation and Maintenance Manuals:

a. Operations and Maintenance Manuals shall consist of two (2) parts. The information shall be in three ring binders with tabs and a table of contents. Diagrams shall be on 11 IN by 17 IN foldouts. If color has been used to differentiate information, the printed copies shall be in color.

1) Part I: Information common to the entire system. This shall include, but not be limited to the following:

a) Product manuals for the key software tasks.

(1) Operating the system.

(2) Administering the system.

(3) Engineering the operator workstation.

(4) Application programming.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 6

(5) Engineering the network.

(6) Setting up the web server.

(7) Report creation.

(8) Graphics creation.

b) System architecture diagram.

c) List of recommended maintenance tasks associated with the system servers, operator workstations, data servers, web servers, and web clients.

(1) Define the task.

(2) Recommend a frequency for the task.

(3) Reference the product manual that includes instructions on executing the task.

d) Names, addresses, and telephone numbers of installing Contractors and service representatives for equipment and control systems.

e) Licenses, guarantees, and warranty documents for equipment and systems.

f) Submit one (1) copy for each building, plus two (2) extra copies.

2) Part II: Information common to the systems in a single building.

a) System architecture diagram for components within the building annotated with specific location information.

b) As-built drawing for each control panel.

c) As-built wiring design diagram for each control panel.

d) As-built wiring design diagram for all components.

e) Installation design details for each I/O device.

f) As-built system flow diagram for each system.

g) Sequence of control for each system.

h) Binding map for the building.

i) Product data sheet for each component.

j) Installation data sheet for each component.

k) Submit two (2) copies for each building and two (2) extra copies.

3. Software:

a. Submit a copy of all software installed on the servers and workstations.

b. Submit all licensing information for all software installed on the servers and workstations.

c. Submit a copy of all software used to execute the project even if the software was not installed on the servers and workstations.

d. Submit all licensing information for all of the software used to execute the project.

e. All software revisions shall be as installed at the time of the system acceptance.

4. Firmware Files:

a. Submit a copy of all firmware files that were downloaded to or pre-installed on any devices installed as part of this project.

b. This does not apply to firmware that is permanently burned on a chip at the factory and can only be replaced by replacing the chip.

c. Submit a copy of all application files that were created during the execution of the project.

d. Submit a copy of all graphic page files created during the execution of the project.

e. Submit a copy of all secondary graphic files such as bitmaps, jpegs, etc. that were used in the creation of the graphic pages.

5. PVT Report: Contractor shall prepare a PVT report documenting all tests performed during the PVT and their results. The PVT report shall include all tests in the PVT Procedures and any other testing performed during the PVT. Failures and repairs shall be documented with test results.

1.5 OWNERSHIP OF PROPRIETARY MATERIAL

A. The Government shall retain all rights to software for this project.

B. The Government shall sign a copy of the manufacturer’s standard software and firmware licensing agreement as a condition of this Contract. Such license shall grant use of all programs and application software to the Government as defined by the manufacturer’s license agreement, but shall protect the manufacturer’s rights to disclosure of Trade Secrets contained within such software.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 7

C. The licensing agreement shall not preclude the use of the software by individuals under contract to the Government for commissioning, servicing, or altering the system in the future. Use of the software by individuals under contract to the Government shall be restricted to use on the Government’s computers and only for the purpose of commissioning, servicing, or altering the installed system.

D. All project developed software, files and documentation shall become the property of the Government.

These include but are not limited to:

1. Server and Workstation software.

2. Application Programming Tools.

3. Configuration Tools.

4. Addressing Tools.

5. Application Files.

6. Configuration Files.

7. Graphic Files.

8. Report Files.

9. Graphic Symbol Libraries.

10. All Documentation.

1.6 QUALIFICATIONS

A. Bids by wholesalers, distributors, mechanical Contractors and non-franchised Contractors shall not be acceptable. The Control Contractor shall represent a recognized national manufacturer, installer and service provider of Building Management Systems and HVAC direct digital control systems.

B. The Control System Contractor shall be the primary manufacturer-owned branch office or factory authorized representative that is regularly engaged in the engineering, programming, installation and service of total integrated Temperature Control Systems.

C. All work described in the plans and specifications shall be installed, wired and commissioned by factory certified technicians qualified for this work and in the regular employment of the control system manufacturer’s local office.

D. A local office is defined as a corporate branch office or an independently owned office with a current contractual agreement with the system manufacturer that allows the office to purchase, install, and service the manufacturer’s products.

E. The local office shall be a full service facility within 50 miles of the project site. The local office shall be staffed with Engineers and technicians trained on the installation, commissioning, and service of direct digital control systems based on the BACnet technology. The local office shall provide complete maintenance and support services on a 24 HR, 7-day-a-week basis.

F. As evidence and assurance of the Contractor’s ability to support the Government's system with service and parts on hand, the Contractor must have been in the temperature controls business for at least the last 5 years and have successfully completed total projects of at least two (2) times the value of this contract in each of the preceding 5 years.

1.7 QUALITY ASSURANCE

A. All work, materials, and equipment shall comply with the rules and regulations of all codes and ordinances of the local, state, and federal authorities. Such codes, when more restrictive, shall take precedence over these plans and specifications. As a minimum, the installation shall comply with the current editions in effect 30 days prior to receipt of bids for all of the Codes and Standards listed in Section 1.3 of this Specification.

B. Performance criteria for components, collections of components, communications, and system performance are described in Section 2.0, Products.

C. Key quality assurance programs shall include the following which are described in Section 3.0, Execution.

1. Startup Testing.

2. Performance Verification Testing.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 8

3. System Performance Testing.

1.8 APPROVED MANUFACTURERS

A. Systems shall be limited to Delta, Honeywell, Tridium or Distech or approved equal.

1.9 DEFINITION OF TERMS

A. This document contains a list of terms and/or abbreviations with their definitions. These terms are used throughout this document.

B. Additional definitions of terms or acronyms are included on the contract drawings and in other sections of this Specification.

C. In the preparation of submittals and reports, the Contractor shall use these definitions and abbreviations.

Any terms or abbreviations used by the Contractor in submittals and reports that have not been defined in this section shall be defined by the Contractor in the first section of the submittal or report prior to their use.

1. (adj): This acronym is used for the word “adjustable”. It is used in conjunction with the definition of an application parameter that resides in a Building Controller, Advanced Application Controller or Application Specific Device.

a. Example: The hot water set point shall vary as a function of the outside air temperature. When the outside air temperature is 0 DegF (adj), the hot water set point shall be 180 DegF (adj).

When the outside air temperature is 60 DegF (adj), the hot water set point shall be 100 DegF (adj). In this example, four (4) variables have been defined as adjustable. When so defined, these variables must be exposed to the field bus as BACnet objects for viewing by a BACnet

OWS.

2. Actuator: Control device to provide motion of a valve or damper in response to a control signal.

3. A/D Converter Resolution: The resolution of an analog to digital converter is the voltage range of the A/D divided by 2 to the X power where X is the number of bits for the A/D converter.

4. Advanced Application Controller: A controller with provisions for all of the physical inputs and physical outputs associated with a single mechanical component such as a terminal unit, air-handling unit, chiller or boiler. The controller shall also have embedded in it all of the control logic that is associated with the physical inputs to the physical outputs. A process controller may or may not have data management features such as time schedules, trend data storage and alarm message generation capabilities. These features may be provided by the Building Controller.

5. AI: Analog Input.

6. Alarm Handling: The process by which the existence of an alarm condition results in the dispatch of an editable message to one or more operator workstations.

7. Algorithm Execution Sample Rate: How often a mathematical algorithm in a controller generates a new output value.

8. Analog: Continuously variable state over a stated range of values.

9. Analog Calibration Offsets: For all analog input measured variables, there is a requirement to adjust the value measured by the hardware based analog input point to match the value reported by a certified test instrument. An analog calibration offset is a parameter that can be added or subtracted from the raw value measured by the sensor to produce a calibrated value that will be use by the control logic and reported to the operator workstations. The initial value of this parameter is set at zero and it is adjusted when the calibration process is executed. This adjustment is referred to as a single point calibration. These offset values are configuration parameters and as such shall be written to EEPROM. It shall be possible to change the value of these parameters without re-downloading the program to the controller.

10. AO: Analog Output.

11. Application Programming Tool (APT): A software tool used to create control logic for use in a

Building Controller or Advanced Application Controller (Process Controller or Supervisory Logic Controller). Application programming tools are unique to each vendor. Example: The Honeywell application programming tool cannot be used to create an application for downloading to a TAC programmable process controller. The use of open protocols does not impact this definition.

12. Application Specific Controller (ASC): A subset of application specific devices (ASD).

DIRECT DIGITAL CONTROL SYSTEM

15903 - 9

13. Application Specific Device (ASD): A sensor, controller, or end device that is pre-programmed by the vendor. It may have physical inputs and physical outputs. The control logic, while not programmable, may be configurable through the use of configuration parameters. The application may require input network variables and may send output network variables onto the network.

14. Archive: Long term storage of historical data. Archived data may be on the hard drive or relocated to disk or tape.

15. ATS: Automatic Time Schedules. Automatic time schedule software measures time and executes start and stop commands based on operator created requirements that are based on the day of the week or the date.

16. AWG: American Wire Gauge – Standard trade sizes of conductors.

17. B-AAC: BACnet Advanced Application Controller.

18. B-ASC: BACnet Application Specific Controller.

19. B-BC: BACnet Building Controller.

20. B-OWS: BACnet Operators Workstation.

21. B-SA: BACnet Smart Actuator.

22. B-SS: BACnet Smart Sensor.

23. BACnet: Building Automation and Control Networks.

24. BIBBS: BACnet Interoperability Building Blocks.

25. Broadcasting: The propagation of data from a device to the control network. Software objects that broadcast data to the network may include the following parameters:

a. Send on Delta: An adjustable parameter that defines a requirement to broadcast when the data generated by the software object changes by an amount that exceeds this parameter’s value. For binary data, this parameter defaults to a change of state. The broadcast of data is initiated when this criteria and the minimum send time requirement have been met. Also referred to as a “Change of Value”.

b. Minimum Send Time: An adjustable parameter that defines a mandatory time period during which no broadcasting of data will occur. Once this time period has been exceeded without a broadcast, the send on delta parameter or the maximum send time parameter shall determine when a broadcast is initiated.

c. Maximum Send Time: An adjustable parameter that defines the maximum time period between broadcasts of a software object’s data to the network. Should the value of a software object remain constant over an extended period of time, the value will be rebroadcast once every maximum time period.

26. Building Controller: A device that includes IP to Field Bus router, automatic time scheduling, trend logging, alarm handling, and supervisory logic control functionality. Sometimes referred to as a BACnet Building Controller or B-BC.

27. Bus Topology: A term used to describe the sequential connection of devices on a LON segment.

The communication cable runs from device to device with no tees or stubs from the main communication cable to a device. Also referred to as daisy chain wiring.

28. CAT: Category 5 Cable or Category 6 Cable – is an ANSI/EIA Standard 568 that specifies categories of twisted pair cabling systems (wire, junctions, and connectors) in terms of the data rates that they can sustain.

29. CFM: Cubic Feet per Minute.

30. Configuration Parameter: An input variable to a device that is written to EEPROM.

Configuration parameters can be changed from the OWS periodically but are not changed routinely as a function of control logic.

31. Data Server: A personal computer with a Microsoft’s Sequel database for the storage of historical data. The historical data is sent to the data server by the system servers.

32. Data Storm: A data storm is the uncontrolled transmission of data from a controller to the network.

It can consume bandwidth and prevent necessary data from getting through. It is typically caused by poorly written applications that do not use event driven communication with minimum send times, send on delta (change of value), and maximum send time parameters.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 10

33. Dead Zone: With respect the performance of a PID algorithm, the dead zone is the range of an input variable to the PID above and below the set point for which the output of the PID algorithm shall not be changed. Once the input variable gets within the dead zone, it is fruitless to attempt changes to get the input variable any closer to the set point. Assigning a dead zone to a PID loop improves stability and reduces wear and tear on the actuator.

34. DI: Digital Input. Also referred to as a binary input or discrete input.

35. Discrete: Binary or digital state.

36. DO: Digital Output. Also referred to as a binary output or discrete output.

37. Drift: When a sensor calibration is checked after a defined period of time (typically one year), the difference between the reported value and the measured value is defined as the drift. This measurement assumes that the sensor was calibrated at the beginning of the time period. If the measurement at the end of the time period is at a different value than the measurement at the beginning of the time period, an allowance for the conformity rating must be included.

38. Dynamic Data: Data in a field level device that periodically changes values due to the measurements from the physical environment or the execution of control logic.

39. EEPROM: Electrically Erasable Programmable Read-Only Memory (ROM) that can be erased and reprogrammed (written to) repeatedly through the application of higher than normal electrical voltage.

40. Electronic Signature: Electronic signature is a feature that supports certification under 21 CFR Part 11. When an operator that is signed onto a system takes an action such as changing a set point, the system requires the user name, password and a documented reason for the action before the action is allowed to take affect.

41. Enforced Acknowledged Response: When an alarm is acknowledged, the entry of the cause of the alarm, action taken to resolve the alarm state, and additional comments are required.

42. Event Driven Communication: A term used to describe the propagation of data from a device to the network based on broadcasting rather than polling. The send on delta (change of value) parameter is used to define the event and the data propagation is further controlled by the minimum and maximum send time parameters.

43. FC: Failed close position of a control device or actuator. The device shall move to the closed position on a loss of the control signal or energy source.

44. Firmware: There are two types of software associated with a hardware device. The first element of software provides the underlying core functionality of the device. The second element is the application program that allows the device to execute a specific sequence of control. The first core element is typically revision sensitive and may be updated from time to time by the vendor to improve performance. This first element of software is called firmware.

45. Floating Control: Floating control is a control loop algorithm used for fast responding airside and waterside pressure and flow control loops. Defining a set point and a neutral zone creates a “floating” analog zone in units of the process variable. The neutral zone is split half above the set point and half below the set point. Whenever the process variable is within the “floating” zone, the actuator is left unchanged (stationary for tri-state actuators and at the current percent stroke for analog devices). The process variable is measured and the algorithm executed once for each sample rate. For tri-state devices, the sample rate is always 1 second. For analog devices, the sample rate will vary from 2 to 10 seconds (a tuning requirement). During the execution of the algorithm, if the process variable is above or below the “floating” zone, the instructions to the end device are changed.

For tri-state devices they are put into motion. For analog devices, their percent stroke signal is either increased or decreased by a set amount (called the bump rate). One sample rate later the process is repeated. If the process variable has returned to within the “floating zone,” a tri-state actuator is instructed to cease motion and an analog device will hold at the new percent signal sent on the last sample. If the process variable remains outside the “floating” zone, a tri-state device will continue in motion and an analog device will receive another “bump”. With pressure based control loops, it is usually required to set the position of the control device to a fixed level for a period of time when the system is started. This will preclude a pressure spike in the first few minutes of operation. This is not required for flow control loops.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 11

46. Flyover: When the linking object is “transparent”, information about the link is viewable only when the operator moves the pointer over the transparent linking object. This process is called a “flyover”.

A transparent linking object might be placed over a bitmap picture of a piece of equipment. When the operator moves the pointer over the picture of the piece of equipment the link is viewable and clicking on the link takes the operator to the graphic page for the piece of equipment.

47. Free Topology: A data wiring topology supported by LON that allows for loops, tees, y-connections, etc. When this topology is used, only one terminator of a specific design is required and allowable cable lengths are significantly reduced. Guidelines on the application of this concept are available from Echelon.com.

48. Gain: A term used with proportional control. Gain is 100 divided by the specified throttling range.

See also the definition for throttling range. This term is sometimes referred to as the proportional gain.

49. Graphic Page: A graphic page is a visual presentation in the operator workstation that allows the operator to view a collection of data in an organized manner. The data on a single view can come from multiple field devices. The data can be organized in a table format within the view. The data can be displayed on a visual representation of a mechanical system. Both visual equipment displays and columns of data can be displayed on single view. Links to other graphical pages can be displayed. Links to IP addresses can be displayed on a graphic page. A graphic page can be static such as a site map or picture with no dynamic data only links to other graphic pages.

50. Graphical Programming: Graphical programming is a concept where mathematical and logical algorithms are represented by graphical objects. Control logic is laid out by placing objects on a palate and connecting the output of one object to the input of the next object. Once completed, the object oriented diagram is compiled and checked for errors, and when all errors have been eliminated, the program can be downloaded to a controller.

51. High Volume Accumulator: Given the physical difficulty in measuring the static pressure of the outside air, the static pressure sensor is installed in a fabricated device that is made of a section of PVC piping. The pipe as multiple holes drilled in it to allow the interior of the pipe section to represent the static pressure without the effects of wind pressures. The sensor is installed in one end and the holes are drilled at all angles near the opposite end of the pipe. Both ends are capped.

52. HOA: Hand-Off-Auto.

53. HVAC: Heating, Ventilating and Air Conditioning.

54. HZ: Hertz, a unit of frequency. It is synonymous with cycles per second.

55. I/O: Input and Output.

56. IEEE: Institute of Electrical and Electronics Engineers.

57. Initial Value (IV): An initial setting for a parameter that can subsequently be changed by the operator without re-compiling and downloading the program.

58. Instance Number: A unique number in the range of 0 to 4.194,302 assigned to each device in a

BACnet system. A conflict in the instance number between two devices can be problematic. This is part of the BACnet addressing scheme for devices.

59. Interstitial Space: The space above a ceiling and below the above floor. Ductwork, piping and electrical cables are typically run in this space.

60. ISA: Instrumentation, System and Automation Society.

61. Historical Trend Data: Trend data is a collection of values from a specific variable in a field bus level device such as the mixed air temperature on an air-handling unit. The collection of this data may be accomplished whenever the AHU is operating and then once every 5 minutes. This collected data is then stored in a database on a data collection computer. Once the data is removed from the device and placed in the database, it is considered to be Historical Trend Data.

62. Inch-Pound Units: A system of units used in the United States as contrasted with the SI system of units. See the ASHRAE Handbook of Fundamentals for a complete list of engineering units under this system of units.

63. Inhibit Alarms: To inhibit an alarm is to stop the transmission of the alarm message to the OWS.

This may be done on chilled water plant during the winter or during major maintenance on a system when the alarms no longer have any real significance. Also referred to as disabled alarms.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 12

64. Latch: A term used in describing control logic where a state change by a binary variable causes another point in the logic to change states and remain at the new state even though the initiating variable reverts to its original state. Latching functions include a reset function that allows the latched variable to revert to its original state when the reset input is toggled.

65. Line Programming: Line programming based application programming tools use line code that is similar to FORTRAN, Basic or C+ programming. Master programs and subroutines are created to meet a sequence of control. The program is then compiled and downloaded to a controller.

66. Links: A link is a mechanism by which the system operator can change the operator workstation view from one part of the system to another part of the system or from one graphic page display to another graphic page display.

67. Logic Generated Application Parameter: An application parameter for a control process that is generated by secondary or supporting logic. Example: A proportional plus integral (PI) control loop is used to control a chilled water coil in an Air Handling Unit. The process variable is the discharge air temperature. The set point for the PI control loop is a function of the maximum terminal load from all of the terminals being supported by the AHU. The PI control loop set point is a Logic Generated Application Parameter. If in the sequence of control, a Logic Generated Application Parameter is appended with (rpt), the value of the Logic Generated Application Parameter shall be an output network variable from the control device.

68. Manual Control: A concept where the operator, from the operator workstation, takes control of an end device and forces a specific position or state. From a software perspective, the value produced by the control logic is not allowed to affect the position or state of the end device. The manual mode and the desired manual position or state, are parameters that are set by the operator.

69. Maximum Send Time Parameter: A parameter used to ensure the periodic update of network data.

If a time period equal to the value of this parameter has expired without a broadcast of the variable, are-broadcast of the current value shall be executed. See also send on delta (change of value) and minimum send time parameter definitions.

70. Minimum Send Time Parameter: A parameter used to control unnecessary broadcasting of data onto the network. A broadcast of an updated value shall not occur unless a time period equal to the value of this parameter has expired. The expiration of the time period does not mandate a re-broadcast. See also send on delta and maximum send time parameter definitions.

71. Modulating: Movement of a control device through an entire range of values proportional to an infinitely variable input value.

72. Multiple Controller Integrated Control (MCIC): A concept where multiple controllers with I/O are used to control a single mechanical system such as an air-handling unit. Under this concept, the mechanical system is sub-divided into a collection of processes to be controlled such as the fan start stop circuit, the fan variable speed drive, the mixed air section, the cooling coil section, etc.

73. NC: Normally Closed. Refers to the position of a switch or end device when the control signal is removed. Switch or device shall be closed.

74. Network Number: Each unique element of the system architecture is assigned a network number as part of the addressing scheme for a BACnet system. The IP layer has a network number. Each field bus has a network number.

75. NO: Normally Open. Refers to the position of a switch or end device when the control signal is removed. Switch or device shall be open.

76. Owner: Malmstrom Air Force Base.

77. OWS: Operator Workstation. With BACnet systems and operator workstation is also referred to as a BACnet OWS.

78. P: Proportional only control.

79. PI: Proportional plus integral control.

80. PICS: Protocol Implementation Conformance Statements.

81. PID: Proportional plus integral plus derivative control.

82. Process Control: Process Control consists of a control loop such as PID that requires a process variable (measured by a sensor), the logic of control (PID) and an end device to be commanded. The logic of control may require numerous application parameters that may be fixed, adjustable from the OWS, or the output of secondary control logic.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 13

83. Process Control Sample Rate: The time between updates of a newly calculated command to an end device.

84. Process Variable Sample Rate: The time between updates of measured values as measured by physical sensors.

85. Real Time Trend Data: Trend data is a collection of values from a specific variable in a field bus level device such as the mixed air temperature on an air-handling unit. An operator workstation may poll for the value from the field device and immediately present the data in a graphical format for system troubleshooting. This type of trend data collection and presentation is called Real Time Trend Data. It is a temporary form of data collection used for periodic troubleshooting of a system problem. It is not used on a continuous basis, as excessive polling from a workstation is a poor steward of network bandwidth.

86. Repeater: A physical device used to connect two segments. A repeater does not filter any message traffic. A repeater does isolate physical problems such as short circuits to a single segment and is typically required to allow the use of additional devices or additional cable length.

87. Rolling Average: An algorithm that eliminates spikes in a variable. Parameters required for a rolling average are the specified time period and the sample rate of the algorithm. When the rolling average variable is updated, the previously calculated rolling average value is multiplied by the time period less the sample rate and then added to the current value of the process variable times the sample rate. This sum is then divided by the time period. The result is the new rolling average value.

88. (rpt): An acronym indicating data to be reported for viewing at the OWS.

89. Sample Rate Support: The term, sample rate, refers to how often an algorithm is executed. An engineer may wish that a PID algorithm controlling the mixed air damper calculate a new command to the damper once every 25 seconds. The 25 seconds is the sample rate. Sample Rate Support refers to the ability to control the sample rate for any given algorithm.

90. SI Units: A system of units based on the metric system. See the ASHRAE Handbook of Fundamentals for a complete list of engineering units in this system.

91. SCFM: Standard cubic feet per minute.

92. Send on Delta Parameter (Change of Value): A parameter used to control unnecessary broadcasting of data onto the network. A broadcast of an output variable shall not occur unless the output variable has changed by an amount equal to or greater than the value of this parameter and the minimum send time has expired since the last broadcast. See also minimum send time and maximum send time parameter definitions. For binary data, the send on delta parameter is assumed to be a change of state. Logic to support the send on delta concept may be imbedded in the configurable structure of an output point or programmed as part of the logic.

93. SQL: Structured Query Language. A standard interactive and programming language for getting information from and updating a database via queries.

94. Stand-Alone Controller: A stand-alone controller has provisions for all of the physical inputs and physical outputs associated with a single mechanical component such as a terminal unit, air handling unit, chiller or boiler. The controller shall also have embedded in it all of the control logic that associated the physical inputs to the physical outputs. A stand-alone controller will also have data management features such as time schedules, trend data storage and alarm message generation capabilities.

95. State Descriptors: DDC devices work in the world of binary numbers. When a binary value is displayed at the OWS, state descriptors can be appended to the data such that the operator shall see the English words rather than the binary values. Example: 0= OFF, 1= ON or 0= STOP, 1= START.

96. Supervisory Logic: Control logic that does not directly rely on physical inputs or physical outputs as does process control. Supervisory Logic uses data from multiple process control loops, applies defined logic to the collection of data and generates instructions to process control loops. Example:

Collect the damper positions from 25 VAV controllers. Determine the highest value. When the highest value is at 50 percent, send a static pressure set point of 1.0 IN of water (adj) to the air handling unit controller. When the highest damper position is at 90 percent, send a static pressure set point of 1.5 IN of water (adj) to the air handling unit controller. Supervisory Logic may be executed in Building Controllers or Advance Application Controllers.

DIRECT DIGITAL CONTROL SYSTEM

15903 - 14

97. System Messages: A message in the event log or alarm viewer that is generated within the OWS and not from a binary indicator broadcast from a controller.

98. TCP/IP: Transmission Control Protocol/Internet Protocol. A basic communications protocol in a private network, either an intranet or an extranet.

99.…