GSA_R8_Open_Protocol_Implementation_Guide_-_BACnet_-_v1_0_0_FINAL.pdf

GENERAL SERVICES ADMINISTRATION

PUBLIC BUILDINGS SERVICE

FACILITIES MAINTENANCE & SERVICES PROGRAM

Region 8

Open Protocol Implementation Guide: BACnet

August 19, 2014

Prepared by: Mike Grush (McKinstry)

GSA R8 Master Systems Integrator (MSI) michael.grush@gsa.gov

SENSITIVE BUT UNCLASSIFIED (SBU)

PROPERTY OF THE UNITED STATES GOVERNMENT

FOR OFFICIAL USE ONLY

Do not remove this notice

Properly destroy or return documents when no longer needed

SENSITIVE SECURITY INFORMATION

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 1

GSA Public Building Service Facility Maintenance & Services Program

Open Protocol Implementation Guide: BACnet

DOCUMENT DESCRIPTION

The following document outlines the implementation requirements for ANSI/ASHRAE Standard 135: BACnet.

Revision Date Author Description

0.0.1 5/13/2014 Mike Grush Draft

1.0.0 8/21/2014 Mike Grush Revised appendices, modified content

INTRODUCTION

A. Purpose:

1. Ensure that all new building automation systems (BAS), as well as systems affected by major upgrades and retrofits, utilize a standardized open protocol.

2. Ensure that protocol parameters are properly managed to avoid risk associated with compatibility and communications issues.

3. Ensure that technology systems will enable the GSA to achieve interoperability, integration, and data acquisition goals.

B. Scope:

1. All BMC, EMCS, and lighting systems, devices, and software shall conform to this specification.

2. Integration devices and systems, when joining or interacting with any GSA BACnet internetwork, shall conform to this specification.

CONTENTS

Section Title

I BACnet Definitions

II Documenting BACnet in Proposals, Submittals, and As-Builts

III BACnet Services

IV BACnet Devices

V BACnet Gateways (B-GW)

VI BACnet Parameters

VII IT Network

VIII BACnet Implementation

IX BACnet Commissioning & Acceptance

A Appendix A: BACnet Device & Network ID Standards

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 2

Facility Maintenance & Services Program

B Appendix B: UDP Port Assignments

C Appendix C: BACnet Device BIBB Requirements Table

I. BACNET DEFINITIONS

a. BACnet: ANSI/ASHRAE Standard 135-2012

b. BACnet Device Types:

i. BACnet Router (B-RTR): A device that connects two BACnet networks, permitting information exchange between them.

ii. BACnet Building Controller (B-BC): A general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks. Typically controls major equipment and/or provides supervisory control.

iii. BACnet Advanced Application Controller (B-AAC): A fully-programmable controller.

iv. BACnet Application Specific Controller (B-ASC): A controller intended for use in a specific application with limited programmability. Typically controls minor equipment such as VAV terminal units.

v. BACnet Smart Sensor (B-SS): A simple sensing device intended for a specific application.

vi. BACnet Smart Actuator (B-SA): A simple control device intended for a specific application.

vii. BACnet Advanced Work Station (B-AWS): Used to monitor the performance of a system and to modify parameters that affect the operation of a system.

viii. BACnet Operator Work Station (B-OWS): Used for monitoring and basic control of a system.

ix. BACnet Operator Display (B-OD): A basic operator interface with limited capabilities.

x. BACnet Gateway (B-GW): A device that connects a BACnet network to a dissimilar network or device, permitting information exchange between them.

xi. BACnet Broadcast Management Device (BBMD): A device that propagates BACnet broadcast services from one network to another network.

c. BACnet Client: A BACnet device requesting information from and/or sending supervisory commands to a

BACnet Server or BACnet Servers.

d. BACnet Server: A BACnet device that responds to requests and/or supervisory commands from a BACnet

Client device.

e. BACnet Interoperability Building Blocks (BIBBs): Standard technical functionality blocks used to describe the capability of a device to interact with BACnet services. Each BIBB has a client version (A) and a server version (B). A single BACnet device can support both A and B versions of a BIBB.

f. BACnet Protocol Implementation Conformance Statement (PICS): Document that describes in technical detail the BACnet implementation applied to a device, including which BACnet Interoperability Building

Blocks (BIBBs) apply to the device.

g. Native-BACnet: A controller that uses BACnet as the primary communication protocol, and does not require the use of a gateway or translator to be BACnet-compliant.

h. BACnet Testing Laboratory (BTL): A laboratory that tests and certifies BACnet devices for conformance

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 3

Facility Maintenance & Services Program to the BACnet standard.

i. Bounded/Unbounded: An unbounded broadcast refers to a BACnet broadcast that is sent to all BACnet device IDs on the entire internetwork. A bounded broadcast is sent only to a subset of device IDs.

Unbounded confirmed broadcast messages can result in BACnet storms. Bounded confirmed broadcast services mitigate the risk of storms by reducing the scope of the communications to only those devices that are specified, which limits the number of potential responses.

II. DOCUMENTING BACNET IN PROPOSALS, SUBMITTALS, AND AS�BUILTS

A. Clear communication regarding BACnet is essential. Therefore, all documentation and literature shall refer to BACnet topics and concepts using standardized terminology. Refer to ANSI/ASHRAE Standard

135 for proper terms.

B. In all cases where literature, proposals, submittals, or as-built documentation are transmitted, an electronic version shall be included.

C. Any documentation that does not meet the terminology requirements or fails to include the required information will be rejected.

D. All considered proposals shall include:

a. BAS architecture diagram including:

i. Basic logical network topology

ii. Representative devices for each device type proposed

b. Product data sheets for products proposed

c. Technical literature for product line(s) outlining functionality and capabilities

d. Listing of all BACnet broadcast services required for the proposed system to function and meet interoperability requirements

e. BACnet PICS for products proposed

E. All approved BAS system submittals shall include all pertinent information relating to BACnet including:

a. BAS architecture diagram specific to the planned installation (no generic diagrams) including:

i. Logical network topology for all networks

ii. Nomenclature to identify each device and network matching nomenclature in controller schedule

b. Product data sheets for all products provided

c. O&M manuals for all products provided

d. Technical manuals for all products provided

e. Controller schedule including all BAS controllers to be used; include an electronic spreadsheet including:

i. Controller name/description

ii. Device model number

iii. BACnet device type (i.e.: B-BC, B-AAC, B-ASC, etc.)

iv. BACnet network type (BACnet/IP or BACnet MS/TP)

v. Host controller (for MS/TP devices, where applicable)

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 4

Facility Maintenance & Services Program

f. BACnet PICS for each product included in design

g. Device and object names shall conform to the latest version of the GSA Smart Building

Technology Device & Object Naming Standard, available from GSA PBS FMSP.

h. Request for information (RFI) regarding IT and BACnet parameters required for configuration of devices. Logical diagram and controller schedule must be updated incorporating this information and re-submitted for approval.

F. All accepted BAS system as-built documentation shall include all pertinent information relating to

BACnet including:

a. Submittal schedules, diagrams, and drawings updated with IT and BACnet parameters obtained from GSA PBS CIO and FMSP

b. Updated architecture diagram including IT network details and BACnet parameter details

G. PICS shall include at minimum:

a. BACnet Standard Application Services Supported: This table confirms the BACnet services supported by the device.

b. Standard Object Types Supported: This table lists the device’s supported object types. It also indicates if the object is dynamically creatable, dynamically delete-able, optional supported properties, and writable properties.

c. Data Link Layer Options: Describes the network types supported for communications, e.g., Ethernet, ARCNET, or MS/TP.

d. Special Functionality: Describes any special exceptions the device may have to the BACnet protocol in order to perform any specific functions.

e. Property Range Restrictions: Indicates, among other things, the number of characters allowed for the various text properties, such as Object_Name and Description.

f. The project technical specifications should act as the submittal review criteria. The information provided by the PICS should be compared to the technical specifications to ensure the device will function in the system as intended by the design.

III. BACNET SERVICES

A. Normal Services (directed to a specific BACnet device)

B. Broadcast Services (directed to multiple BACnet devices)

a. Who-is?

i. The Who-is? service is to be used in limited ways to avoid BACnet storms:

1. Unbound discovery is prohibited; use bounded Who-is? messages to limit responses.

2. Who-is? shall not be required for daily operation of the BAS or integration system; Who-is? is a discovery tool only. System devices are required to cache device discovery information and use directed communications to achieve interoperation.

3. Any system or device incapable of controlling and/or disabling Who-is?

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 5

Facility Maintenance & Services Program broadcast services it is capable of initiating will not be accepted.

b. Who-has?

i. The Who-has? service shall not be used in normal day-to-day operation; system devices are required to cache object locations and use directed communications to achieve interoperation.

1. A device may use Who-has? to initially gain access to a network object, but thereafter this information shall be cached.

2. System devices shall not re-issue Who-has? on a return from power failure or other system disruption. Device or system backups shall retain cached object locations. Who-has? is permitted only in cases of programming changes.

3. The system must be capable of disabling the Who-has? service.

4. The system must be capable of configuring the Who-has? service to limit and bound its use.

5. Any system or device incapable of controlling and/or disabling Who-has?

broadcast services it is capable of initiating will not be accepted.

c. Time synchronization

i. The Time-sync broadcast service must be configurable; only bounded time broadcasting is permitted. Directed Time-sync communications is preferred.

d. Broadcasting on IP Networks

i. General Broadcasting Guidelines:

1. Broadcast services of any kind must not be used except where absolutely necessary.

2. Where broadcast services are used, testing must be performed to ensure that the broadcasts and/or the responses do not cause system instability or loss of performance.

3. Unbounded broadcast services are strictly prohibited. Any system that requires the use of unbounded broadcast services, or is unable to be configured to use bounded broadcast services, shall not be accepted.

e. Multicasting

i. Systems that require multicasting will not be accepted.

f. BBMDs

i. Systems that require BBMDs will not be accepted. The use of BBMDs, where that functionality might be desirable, shall be regulated at the discretion of GSA. Any device capable of BBMD functionality must have that functionality disabled until GSA expressly approves the functionality for each specific device.

g. Foreign Devices

i. BBMD-capable devices must also support foreign device registration.

IV. BACNET DEVICES

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 6

Facility Maintenance & Services Program

A. All BACnet devices shall be BTL-certified.

B. BACnet networks:

a. The following controllers shall be BACnet/IP:

i. B-RTR

ii. B-BC

iii. B-AAC

iv. B-AWS

v. B-OWS

vi. B-GW

b. BACnet MS/TP is permitted for the following controllers:

i. B-ASC

ii. B-SS

iii. B-SA

iv. B-OD

c. BACnet/Ethernet is not permitted, and this functionality must be disabled prior to connection to any GSA network.

d. ARCnet/ARCNET is not permitted, and this functionality must be disabled prior to connection to any GSA network.

e. LonWorks-protocol devices are in no way compatible with BACnet devices.

LonWorks/LonTalk/LON is not permitted at this time.

f. BACnet devices and networks must be configured optimally for high-performance and low response latency. Serial networks (MS/TP) must be sized to perform without latency issues, regardless of the traffic imposed on them to support control, monitoring, and trending functions.

C. Required BIBBs

a. Refer to table in Appendix C.

V. BACNET GATEWAYS (B�GW)

A. BACnet gateways are approved for use to connect to existing legacy devices only. Any other use must be individually and expressly approved by RFI to GSA PBS FMSP for each specific application and instance.

B. BACnet gateways shall not be used to connect new non-BACnet controllers or other devices unless specifically approved by RFI to GSA PBS FMSP.

C. Where possible/available, when BACnet gateways are used, they shall be configured to facilitate all available BACnet functionality. Devices connected using a gateway shall support the following BIBBs at minimum: DS-RP-B, DS-WP-B, DM-DDB-B, DM-DOB-B, DM-DCC-B, DM-RD-B. Objects made available using a gateway shall support the following BIBBs at minimum: DS-RP-B, DS-WP-B (DS-WP-B where

“write” function applies).

D. Any device or network connected to the BACnet internetwork via a BACnet gateway is considered part

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 7

Facility Maintenance & Services Program of the BACnet internetwork, and all requirements that apply to the BACnet internetwork extend to the devices and networks connected via BACnet gateways. High-performance communications and interoperability is required, and BACnet gateway solutions shall meet these requirements.

VI. BACNET PARAMETERS

A. BACnet parameters must be configurable.

B. BACnet parameters include:

a. Device ID (see Appendix A)

b. Network number (see Appendix A)

c. UDP port (see Appendix B)

i. UDP ports are assigned based on BMS/EMCS vendor/product. Other building systems, such as lighting control systems, will typically use the same UDP port as the host

BMS/EMCS at the facility. These will be assigned to produce an overall architecture that ensures proper interoperability.

d. BBMD feature settings (disabled unless specifically permitted by GSA)

C. BACnet parameters shall be obtained from GSA PBS FMSP.

a. BACnet parameters are managed by the Regional FMSP BAS Specialist.

D. Automatically-generated BACnet parameters must be configured to avoid duplication of object, device, or network instances. Automatically-generated BACnet parameters must be capable of being manually configured; devices that only support automatically-generated BACnet parameters are not permitted.

VII. IT NETWORK

A. TCP/IP parameters will be obtained from GSA PBS CIO:

a. IP address

i. GSA currently uses IPv4 addressing.

b. Subnet mask

c. Default gateway

d. DNS

i. GSA currently does not support DNS.

B. Ports

a. BACnet UDP port will be obtained from GSA PBS FMSP.

b. Other ports required for BAS operation must be submitted for approval.

C. Physical infrastructure

a. No IT gear is permitted except as provided by or pre-approved by GSA PBS OCIO.

b. IT network design shall be provided and approved by GSA PBS OCIO. Separate networks for BAS devices shall not be permitted; the GSA PBS OCIO IT infrastructure shall be leveraged to support

BAS devices.

c. IP network switch topology shall be ring or star, and must be pre-approved by GSA PBS OCIO.

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 8

Facility Maintenance & Services Program

All end devices must connect directly to a managed switch; no unmanaged switches or hubs shall be permitted.

VIII. BACNET IMPLEMENTATION

A. During the execution phase of the project, coordination with GSA PBS FMSP is required to avoid or plan for potential system disruption. A risk and impact assessment must be performed prior to any activity that might disrupt existing system functionality. System outages must be planned three (3) weeks prior to work being performed.

B. Activities that may impact existing system performance include (but are not limited to):

a. Adding a new controller to the network

b. Removing a controller from the network

c. Re-addressing existing controllers

d. Modifying existing programming

e. Changing device BBMD settings

f. Altering router tables

g. Altering BBMD tables

h. Altering foreign device settings

C. Where possible when adding new devices, the new internetwork segment(s) shall be isolated and screened for proper configuration prior to being added to the existing internetwork.

D. After new devices, networks, programming modifications, or configuration settings have been added to the existing network, network diagnostics must be performed and documented to ensure that the changes have not adversely affected the system. Any changes found to be having negative effects shall be reported to GSA PBS FMSP and immediately reverted until such time that the issue can be resolved.

Resolution of the issue shall be coordinated with GSA PBS FMSP to minimize the impacts to facility operations.

IX. BACNET COMMISSIONING & ACCEPTANCE

A. BACnet Parameter Commissioning

a. To ensure that all BACnet parameters have been configured correctly, each new device must be certified to have the parameters submitted and approved prior to project execution.

Additionally, the BACnet internetwork must be free from errors; after all work has been completed, the vendor must submit a diagnostic report that reflects a properly-functioning

BACnet internetwork.

b. BACnet PICS must be submitted for each device model supplied as part of the project. All new devices must be BTL-certified.

c. GSA PBS FMSP reserves the right to use a third-party contractor of its choosing to evaluate and commission the BACnet configuration, and may reject the system based on the recommendations of that third-party.

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 9

Facility Maintenance & Services Program

A. APPENDIX A: BACNET DEVICE & NETWORK ID STANDARDS (REGION 8)

A. BACnet Device Object ID Parameters:

a. Description:

i. BACnet permits the interconnection of up to 4,194,303 devices.

ii. Each device is referenced by its device Object_ID property.

iii. Each device shall have a value for the Object_ID property that is unique across GSA

Region 8 facilities, including existing devices.

iv. No device shall have an Object_ID with an instance number less than 1000.

v. No device shall have an Object_ID with an instance number greater than 3,999,999.

vi. Device Object_ID parameters shall be obtained from GSA PBS FMSP through the RFI process as outlined in the Change Control Process.

B. BACnet Network Number Parameters:

a. Description:

i. The BACnet permits the interconnection of up to 65,535 networks.

ii. Each network must have a Network Number that is unique across GSA Region 8 facilities, including existing networks.

iii. No network shall have a Network Number less than 1000.

iv. Network Number 65,535 shall not be used.

C. BACnet MS/TP MAC Addressing:

a. Master devices use token-passing.

b. Slave devices reply to requests only. They do not support the Who-is? service, and therefore cannot be automatically discovered.

c. MS/TP (Master Slave/Token Passing) addressing consists of 256 (0-255) addresses:

i. 0 shall be reserved for the BACnet Router (B-RTR) serving the MS/TP segment.

ii. 0-127 may be used for master or slave devices.

iii. 128-254 are reserved for slave devices only.

iv. 255 is reserved for broadcasting.

d. MS/TP networks shall be limited to ~30 slave devices to prevent network latency.

e. MAC addresses on a network shall be consecutive starting with 0 (B-RTR). (Some products reserve addresses 0, 1, 2 & 3. In cases like this, the addresses must be as nearly consecutive as possible.)

f. The “Max Master” parameter for all applicable devices associated with an MS/TP network shall be set to the address of the highest-addressed master device.

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 10

Facility Maintenance & Services Program

B. APPENDIX B: BACNET UDP PORT ASSIGNMENTS (REGION 8)

� UDP Ports:

a. UDP 47808: Reserved – do not use

b. UDP 47809-47992: Reserved – no not use

c. UDP 47993: Johnson Controls, Inc.

d. UDP 47994: Siemens Building Technologies, Inc.

e. UDP 47995: SensorSwitch

f. UDP 47996: Honeywell

g. UDP 47997: Alerton

h. UDP 47998: Baseline

i. UDP 47999: Automated Logic

j. UDP 48000: TAC (Schneider)

k. UDP 48001: Trane

l. UDP 48002: Delta Controls

m. UDP 48003: Lutron

n. UDP 48004: Reliable Controls

o. UDP 48005: KMC Controls

p. UDP 48006: Invensys (Schneider)

q. UDP 48007: Andover Controls (Schneider)

r. UDP 48008: NiagaraAX BACnet Devices

s. UDP 48009: Reserved – no not use

t. UDP 48010: Reserved – no not use

u. UDP 48011: Reserved – no not use

v. UDP 48012: Reserved – no not use

w. UDP 48013: Reserved – no not use

x. UDP 48014: Reserved – no not use

y. UDP 48015: Reserved – no not use

z. UDP 48016: Reserved – no not use

aa. UDP 48017 and greater: Reserved – no not use

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 11

Facility Maintenance & Services Program

C. APPENDIX C: BACNET DEVICE BIBB REQUIREMENTS TABLE

Alarm and Event Management

NAME TITLE

B-

AWS

B-

OWS

B-

RTR

B-

GW

B-

BC

B-

AAC

B-

ASC

B-

SA

B-

SS

B-

OD

AE-ACK-A Acknowledgement ● ● ● ● ●

AE-ACK-B Acknowledgement ● ●

AE-ASUM-A Alarm Summary ● ● ● ●

AE-ASUM-B Alarm Summary ● ●

AE-ESUM-A Enrollment Summary ● ● ● ●

AE-ESUM-B Enrollment Summary ● ●

AE-INFO-A Information ● ● ● ● ●

AE-INFO-B Information ● ●

AE-LS-A Life Safety ● ●

AE-LS-B Life Safety

AE-N-A Alarm and Event Notification ● ● ● ●

AE-N-E-B Notification – External Device ●

AE-N-I-B Notification – Internal ● ●

AE-VM-A View and Modify Some Parameters ● ●

AE-AVM-A View and Modify All Parameters ●

AE-VN-A Notification - View Some Info ● ●

AE-AVN-A Notification - View All Info ●

AE-ELVM-A Event Log - View and Modify ●

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 12

Facility Maintenance & Services Program

Data Sharing

NAME TITLE

B-

AWS

B-

OWS

B-

RTR

B-

GW

B-

BC

B-

AAC

B-

ASC

B-

SA

B-

SS

B-

OD

DS-COV-A Change of Value ● ●

DS-COV-B Change of Value ● ●

DS-COVP-A Change of Value – Property

DS-COVP-B Change of Value – Property

DS-COVU-A Unsolicited COV ● ●

DS-COVU-B Unsolicited COV ● ●

DS-RP-A Read Property ● ● ● ● ●

DS-RP-B Read Property ● ● ● ● ● ● ● ●

DS-RPC-A Read Property Conditional

DS-RPC-B Read Property Conditional

DS-RPM-A Read Property Multiple ● ● ●

DS-RPM-B Read Property Multiple ● ● ● ●

DS-WP-A Write Property ● ● ● ● ●

DS-WP-B Write Property ● ● ● ● ● ●

DS-WPM-A Write Property Multiple ●

DS-WPM-B Write Property Multiple ● ●

DS-V-A Read Commonly Used Properties ●

DS-V-B Read Commonly Used Properties

DS-AV-A Read Any Standard Property ●

DS-AV-B Read Any Standard Property

DS-M-A Modify Commonly Used Properties ●

DS-M-B Modify Commonly Used Properties

DS-AM-A Modify Any Standard Property ●

DS-AM-B Modify Any Standard Property

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 13

Facility Maintenance & Services Program

Device Management

NAME TITLE

B-

AWS

B-

OWS

B-

RTR

B-

GW

B-

BC

B-

AAC

B-

ASC

B-

SA

B-

SS

B-

OD

DM-ADM-A Discover All Objects in Any Device ● ●

DM-ANM-A Discover all Devices on the Network ● ●

DM-BR-A Backup and Restore ●

DM-BR-B Backup and Restore ● ● ●

DM-DCC-A Communication Control ●

DM-DCC-B Communication Control ● ● ●

DM-DDB-A Dynamic Device Binding ● ● ● ●

DM-DDB-B Dynamic Device Binding ● ● ● ● ● ● ●

DM-DOB-A Dynamic Object Binding ● ●

DM-DOB-B Dynamic Object Binding ● ● ● ● ● ● ●

DM-LM-A List Manipulation ●

DM-LM-B List Manipulation ● ●

DM-OCD-A Object Creation and Deletion ●

DM-OCD-B Object Creation and Deletion ● ●

DM-PT-A Private Transfer

DM-PT-B Private Transfer

DM-R-A Restart ●

DM-R-B Restart ●

DM-RD-A Reinitialize ●

DM-RD-B Reinitialize ● ● ●

DM-TM-A Text Message

DM-TM-B Text Message

DM-TS-A Time Synch – Local Time ● ● ●

DM-TS-B Time Synch – Local Time ● ● ●

DM-UTC-A Time Synch – UTC ● ● ●

DM-UTC-B Time Synch – UTC ● ● ●

DM-VT-A Virtual Terminal ● ●

DM-VT-B Virtual Terminal

Network Management

B-

AWS B-OWS

B-

RTR

B-

GW

B-

BC

B-

AAC

B-

ASC

B-

SA

B-

SS

B-

OD

NM-CE-A Connection Establishment ●

NM-CE-B Connection Establishment ●

NM-RC-A Router Configuration ●

NM-RC-B Router Configuration ●

Network Security

B-

AWS B-OWS

B-

RTR

B-

GW

B-

BC

B-

AAC

B-

ASC

B-

SA

B-

SS

B-

OD

NS-ED Supports Encryption

NS-KS Key Server

GSA PBS FMSP Open Protocol Implementation Guide: BACnet – v1.0.0 14

Facility Maintenance & Services Program

Scheduling

NAME TITLE B-AWS B-OWS

B-

RTR

B-

GW

B-

BC

B-

AAC

B-

ASC

B-

SA

B-

SS

B-

OD

SCHED-A Scheduling ● ●

SCHED-B Scheduling

SCHED-VM-A View and Modify ● ● ●

SCHED-VM-B View and Modify

SCHED-AVM-A Create, View, and Modify ● ●

SCHED-AVM-B Create, View, and Modify

SCHED-ELVM-A View and Modify Event Log ●

SCHED-ELVM-B View and Modify Event Log

SCHED-E-A Scheduling - External ●

SCHED-E-B Scheduling - External ● ●

SCHED-I-A Scheduling - Internal ●

SCHED-I-B Scheduling - Internal ● ●

SCHED-WS-A Weekly Schedule

SCHED-WS-B Weekly Schedule

Trending

B-

AWS B-OWS

B-

RTR

B-

GW

B-

BC

B-

AAC

B-

ASC

B-

SA

B-

SS

B-

OD

T-ATR-A Automated Trend Retrieval ●

T-ATR-B Automated Trend Retrieval ● ●

T-V-A Display Trend Values ● ●

T-V-B Display Trend Values

T-AVM-A Modify All Trend Configuration ●

T-AVM-B Modify All Trend Configuration

T-VMT-A View and Modify Trends ● ● ● ●

T-VMT-E-B View and Modify Trends External ●

T-VMT-I-B View and Modify Trends Internal ● ●