April Welcome!

Transcription

1 Welcome!

2 WELCOME! The BACnet Interest Group Europe welcomes you to the seminar: Building Automation via BACnet

3 Agenda Welcome History and Origins BACnet on the Internet What is BACnet? Datalink Layer Objects Services Routing in Networks Network security Command Prioritization Alarming Communication Specifying PICS BIBB s Engineering Rules Testing and Tools Wireshark Compare: BACnet LON KNX Dali BACnet and Big Data

4 Regel Partners Ariën Peterse Technical assistant director Member of WG-T BIG-EU Trainer BIG-EU since the year Mobile:

5 Regel Partners Wie is Regel Partners? Onafhankelijk system integrator Meer dan 50 integratie specialisten Landelijke dekking, 3 locaties Omzet circa EUR 9 mln Aandeelhouder: Unica Groep B.V. Onderscheidend vermogen Regel Partners. Specialist in (totaal) integratie. Multi solutions benadering Systemen en/of diensten op basis van open technologie. R&D kennis in house ten behoeve van uniek oplossingen Eigen beheersorganisatie (24/7).

6 About BIG-EU Founded 1998, more than 100 members Marketing and Technique for BACnet in Europe Product testing and certification Co-operation with BACnet International Board of directors: Volker Röhl (D) Klaus Wächter (CH) Karl-Heinz Belser (D) Brad Hill (USA)

7 BACnet Europe Journal

8 Emergency Exits General Information Restrooms Schedule Please, don t use mobile phones

9 Trademarks and Brand Names Registered Trademarks In this course, we will use trademarks and product names of different companies. The following are registered trademarks of the respective organizations and will not be listed separately in this document: BACnet and ASHRAE are registered trademarks of the American Society of Heating, Refrigerating and Air-Conditioning Engineers, INC. (ASHRAE) ARCnet is a registered trademark of the Datapoint Corporation Ethernet is a registered trademark of the Digital Equipment Corporation, Intel and Xerox LonTalk is a registered trademark of Echelon, Inc.

10 Sprechen Sie deutsch? Sprechen Sie deutsch? Do you speak english?

11 History and Origins

12 H. Michael Newman Manager of the Utilities Department at Cornell University, Ithaca, New York First Chairman of the BACnet Standards Committee History and Origins

13 The Problem... History and Origins

14 The Solution... History and Origins

15 December 1995 In December 1995, this protocol is accepted by the American National Standards Institute (ANSI) as the ASHRAE/ANSI Standard History and Origins

16 1997 At the start of 1997, the ASHRAE Standard (BACnet) is accepted as the European prestandard EN V for the management level, and at the end of 1998 accepted as EN V for the automation level. History and Origins

17 1998 In the ISO TC 205 WG 3 Building Automation and Control Systems the ASHRAE/ANSI Standard (BACnet) is accepted as the initial draft for worldwide standardization. All planned amendments and certification requirements are to be incorporated into an ISO norm. History and Origins

18 Maintenance and Development SSPC 135 continuously maintains the standard and develops specifications for new applications. History and Origins

19 Living Standard! ABC BACnet Something Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec sollicitudin libero id elit. Sed euismod nonummy neque. Nam dignissim urna vel urna. Nunc aliquet. Nunc vel dui mattis magna varius condimentum. Etiam lacus enim, aliquam ultricies, luctus ut, placerat id, lectus. Vestibulum laoreet commodo tortor. Nunc eget urna. Suspendisse ac orci. Vivamus quis tortor facilisis velit interdum blandit. Mauris euismod convallis diam. Quisque turpis metus, aliquam sed, euismod sit amet, mollis a, ligula. Maecenas History and Origins

20 Werkgroup Public review remarks No Final Draft Yes Approved Yes Addendum No BACnet Standard History and Origins

21 International Norm ISO is the international norm for building automation (total 7 parts) Part 5 contains the BACnet protocol as the standard language for building automation components Part 6 contains the methods of conformance testing for BACnet products History and Origins

22 BTL Product catalog History and Origins

23 Certification The BACnet Interest Group Europe and the BACnet International are putting together the activities for testing, certifying and listing BACnet devices in order to ensure product conformance. History and Origins

24 Certificates In April 2008 certificates were applied to 14 devices according to ISO certification rules. The test was performed using the BACnet Test Framework, which allows automation of tests. History and Origins

25 Certified Product catalog History and Origins

26 Certificate History and Origins

27 BACnet on the Internet

28 BACnet on the Internet The official homepage of the BACnet Committee on the topic of BACnet. Mailing-List BACnet-L ( -List for FAQ) Homepage of ASHRAE with general information about the ASHRAE organization and its activities. BACnet on the Internet

29 BACnet Interest Groups BIG-EU BIG-France Users group in the Netherlands BIG-Finland BIG Sweden BIG-Russia Big-Poland BIG-Italy BIG-China BACnet on the Internet

30 BACnet on the Internet Homepage of the North American BACnet Interest Group with information about activities and events. BACnet on the Internet

31 BACnet on the Internet In January 2006, BIG-NA and BMA merged. The organization is now BACnet International. BACnet on the Internet

32 Pauze

33 What is BACnet?

34 Why BACnet? BACnet is designed to allow HVAC/R, lighting, life safety, access, security, power, vertical transportation and other building system control devices to work together on the same network. BACnet affords facility owners and manager's maximum flexibility and costeffectiveness, by allowing control products made by different manufacturers to be integrated into a single, uniform system. With BACnet, we re not tied to one system. What is BACnet?

35 Doelstelling van BACnet: BACnet basis informatie Met één Gebouwbeheersysteem alle disciplines bedienen en beheren. Inregelen van de installatie Aanmaken van gebruikers punten: Trends Alarmen In/uitgangen die reserve zijn Maken van backups en terug zetten in de regelaars What is BACnet?

36 What BACnet is not BACnet is (like other protocols) not a Plug-and- Play system! The use of BACnet requires an agreement about the objects, functions and network media to be used. What is BACnet?

37 What BACnet is not BACnet defines the data transmission, and not the use or the specific application. This allows manufacturers to integrate specific applications in addition to the standard data interface. What is BACnet?

38 What is BACnet?

39 BACnet stands for Building Automation and Control Network What is BACnet? BACnet is a registered trademark of ASHRAE.

40 Application Areas of Building Automation Measuring, e.g. collecting temperature and energy values Operation, e.g. blinds, windows, doors Control, e.g. heating, ventilation, air- conditioning Security systems, e.g. fire and burglar alarms Access control systems Elevators/Escalators What is BACnet?

41 What is BACnet? BACnet is a data protocol for the exchange of data between different systems and devices in building automation. BACnet specifies the standard objects of building automation. BACnet specifies access functions for these objects. BACnet supports numerous network standards and topologies, incl. the Internet Protocol (BACnet/IP).

42 What is BACnet? BACnet is a book, and neither software nor hardware. BACnet is manufacturer neutral! BACnet is license free, i.e. anyone can purchase the book and implement BACnet without any license costs.

43 Levels of Building Automation What is BACnet?

44 Do you have questions?

45 Data Link Layer

46 Agreements in communications Which, What and How... Which (communication media)? What (is communicated)? How (is it communicated)? Data Link Layer

47 BACnet Communication Media (Network) Data (Objects) Functions (Services) Data Link Layer

48 Which (communication media)? Telephone, , post, conversation... Ethernet, Internet Protocol UDP/IP, serial connection (RS232), serial network (RS485), ARCnet, LonTalk Wireless (ZIGBEE) Data Link Layer

49 BACnet in the ISO/OSI Model Data Link Layer

50 Example of a BACnet Network Management station (BACnet Client) Network 1 (e.g. 100 BASE-T) Router Gateway DDC (BACnet Server) Network 2 (e.g. MS/TP) Manufacturer specific protocol Data Link Layer

51 Do you have questions?

52 Objects

53 What (is Communicated)? Conversation topics, content of a postal item or Standard objects, mapping the properties of physical or virtual values Objects

54 BACnet Objects Every BACnet device holds objects Objects are composed of properties PROPERTIES Object_Identifier Object_Name Object_Type Present_Value Description Properties can be readable or readable and writable CONFORMANCE CODE R R R R O

55 BACnet Objects PROPERTIES CONFORMANCE CODE Object_Identifier R Object_Name R Object_Type R Present_Value R Description O Certain properties are defined to be required (R) Properties may be optionally supported (O) Some are required to be writable (W) For particular functions e.g. COV reporting (notification of a change of value) or intrinsic reporting (notification of alarms or events), certain properties are conditionally required. Objects

56 The BACnet Standard Objects Objects

57 Data Representation Analog Input Analog Output Analog Value Binary Input Binary Output Binary Value Multistate Input Multistate Output Multistate Value Accumulator Pulse-Converter Averaging Device Objects

58 Control Command Program Loop File Calendar Schedule Lighting Output Network Security Group Global Group Structured View Channel Object Trendlog Trendlog Multiple Load Control Objects

59 Alarming / Access Control Event Enrollment Notification-Class Event-Log Life Safety Point Life Safety Zone Alert Enrollment Notification Follower Access Door Access Point Access Zone Access User Access Rights Access Credential Credential Data Input Objects

60 Composition of BACnet Objects on the Example of the Analog Output Object Objects

61 Property Identifier Property Datatype Conformance Code Object_Identifier Object_Name Object_Type Present_Value Description Device_Type Status_Flags Event_State Reliability Out_Of_Service Units Min_Pres_Value Max_Pres_Value Resolution Priority_Array Relinquish_Default COV_Increment Time_Delay Notification_Class High_Limit Low_Limit Deadband Limit_Enable Event_Enable Acked_Transitions Notify_Type Event_Time_Stamps Profile_Name BACnetObjectIdentifier CharacterString BACnetObjectType REAL CharacterString CharacterString BACnetStatusFlags BACnetEventState BACnetReliability BOOLEAN BACnetEngineeringUnits REAL REAL REAL BACnetPriorityArray REAL REAL Unsigned Unsigned REAL REAL REAL BACnetLimitEnable BACnetEventTransitionBits BACnetEventTransitionBits BACnetNotifyType BACnetARRAY[3] of BACnetTimeStamp CharacterString R R R W O O R R O R R O O O R R O 1 O 2 O 2 O 2 O 2 O 2 O 2 O 2 O 2 O 2 O 2 O Objects

62 Unique identifiers Each device in the BACnet network shall be unique! Each Object Identifier (Type, Instance-Number) in a device shall be unique. Objects

63 Example: Analog Output Object Present_Value Present value Description Description DeviceType Device classification Status_Flags Object status Event_State Alarm/event status Reliability Availability of present values Out_Of_Service Physical decoupling Units Physical units Min_Pres_Value Minumum present value Max_Pres_Value Maximum present value Resolution Resolution Objects

64 Example: Analog Output Object Priority_Array Relinquish_Default Storage for Priorized values Default Value Objects

65 Example: Analog Output Object COV_Increment Threshold for notification of change of value Objects

66 Example: Analog Output Object Time_Delay Delay for notification Notification_Class Alarm object High_Limit Low_Limit Deadband Limit_Enable Event_Enable High alarm limit Low alarm limit Deadband upon return to normal range Specifies active limits Specifies which transitions are notified Objects

67 Acked_Transitions Storage for acknowledged transitions Notify_Type Example: Analog Output Object Notifies whether an event or alarm has to be generated EventTimeStamps Time-stamp of the transitions Objects

68 Example: Analog Output Object Profile_Name Name of a (non-bacnet) object profile Used for mapping of other protocols/data objects in BACnet, e.g. EIB/KNX or LonMark Objects (in progress) to BACnet Objects

69 Do you have questions? Pauze

70 Services

71 How (is it communicated)? Languages, formats (postcard, letter, parcel), HTML site Services for reading, writing, subscribing, monitoring values Services

72 Client-Server Model A server is a device that makes data available for other devices. A client is a device that requests data from a server and then processes the data. A device may be a server and a client simultaneously (peer-to-peer communication) Services

73 Addressing Unicast: directed message to a certain network participant Multicast: directed message to several network participants (BACnet/IP only, rarely used) Broadcast: message to all network participants Services

74 Transport Acknowledgement In order to make sure that a message has been received by the target device, a confirmation service can be used. In this case, the receiver sends an acknowledgement to the sender to confirm that the message has been duly received. Services

75 BACnet Services The BACnet services cover 5 areas: 1) Object access 2) File transfer 3) Alarm and event functions 4) Remote device management 5) Virtual terminal ( not used any more) Services

76 Object Access PROPERTIES Object_Identifier Object_Name Object_Type Present_Value Description CONFORMANCE CODE R R R R O Services

77 Object Access ReadProperty (read single property) ReadPropertyMultiple (read multiple properties including ALL, REQUIRED, OPTIONAL) ReadRange (read range from trendlog or eventlog object) ReadPropertyConditional (read with condition, was removed from the standard) Services

78 Object Access WriteProperty (write single property) WritePropertyMultiple (write multiple properties) CreateObject (create a new instance) DeleteObject (delete an object instance) AddListElement (add elements to a list) RemoveListElement (remove elements from a list) WriteGroup (write to channel objects) Services

79 File Transfer Services

80 File Transfer AtomicReadFile (read data atomically from a file) AtomicWriteFile (write data atomically to a file) Services

81 File Transfer Notes on File Transfer Functions: The purpose and content of the files used in BACnet applications is not specified in the standard. Though the BACnet Standard specifies the procedures how to backup and restore the content of a device. Services

82 Alarm and Event Functions Services

83 Alarm and Event Functions (COV) Subscribe for PresentValue / StatusFlags SubscribeCOV (COV=Change Of Value) UnsubscribeCOV SubscribeCOVProperty (Subscribe for other properties) Confirmed COV Notification UnconfirmedCOVNotification Services

84 Alarm and Event Functions Alarm messages Confirmed Event Notification UnconfirmedEventNotification GetEnrollmentSummary (list of alarm generating objects) GetAlarmSummary (get alarm list, rarely used) Services

85 Alarm and Event Functions GetEventInformation (get list of alarms and events) AcknowledgeAlarm (user acknowledge) Life-Safety-Operation (switch off horn, set revision, etc.) Services

86 Remote Device Management Services

87 Remote Device Management DeviceCommunicationControl (enables/disables communication) ReinitializeDevice (restart a device) Send private data over BACnet ConfirmedPrivateTransfer UnconfirmedPrivateTransfer Services

88 Remote Device Management Send text messages over BACnet ConfirmedTextMessage UnconfirmedTextMessage Synchronize clocks TimeSynchronization UTCTimeSynchronization Services

89 Remote Device Management Dynamic Device Binding Who-Is I-Am Dynamic Object Binding Who-Has I-Have Services

90 Routing in Networks The virtual way to the device Routing in Networks

91 The BACnet network number BACnet Networks may be divided into subnetworks using separate network numbers. For different data-link-layer a unique network number is required per logical subnetwork. Routing in Networks

92 BACnet network number 10 services on the networklayer (Routing-Layer Osi-Model layer 3) allow devices to obtain routing information. E.g. Who-Is-Router-To-Network or I-Could-Be-Router-To-Network Another set of 10 routing services is used for authentication when using the BACnet network security. Routing in Networks

93 Usage of the network number Who-Is- Router-To- Network 2? Network 1, e.g. BACnet/IP I-Am-Router-To-Network 2! Router Network 2, e.g. RS485 MS/TP Routing in Networks

94 Network Security Network Security

95 Network Security Since BACnet is purely a data protocol, it does not provide user queries for passwords or access authorization. This is the task of the respective applications. Data transfer across the network can be secured by using private keys or a key server. Network Security

96 Network Security Private keys are known to the participants by projecting: The transfered data is encoded by the sender and decoded by the receiver using a predefined key. A key server provides dynamic session keys, which are provided to sender and receiver upon request to encrypt a single communication. Network Security

97 Network Security The use of keys requires confirmed transmission. Unconfirmed services (e.g. Broadcast-Message) cannot be encrypted. Network Security

98 Network Security The first approach in 1995 only used 56 bit key and was broken in the specification. Addendum g adds network security to BACnet devices using todays technologies (up to 256 bit encryption). It adds a Network Security object type (for the publically visible characteristics). Network Security

99 Do you have questions? Pause

100 Command Priorization

101 Command prioritization is used to allowed certain clients higher priorities over others An example is on-site manual intrusion, e.g. maintenance work. BACnet provides 16 levels of command prioritization Command Priorization

102 A 16 level priority array is used for saving the priority. Priority Level Application Priority Level Application 1 Manual-Life Safety 9 Available 2 Automatic-Life Safety 10 Available 3 Available 11 Available 4 Available 12 Available 5 Critical Equipment Control 13 Available 6 Minimum On/Off 14 Available 7 Available 15 Available 8 Manual Operator 16 Available Command Priorization

103 The new value is entered into the place in the array that represents the specified priority. The value with the highest priority has precedence over all other values in the priority array. Command Priorization

104 If all 16 levels of priority array equal NULL, the value of the property relinquish default is taken as the Present Value. A client can remove a value from the priority array by writing the value NULL when specifying the priority. Command Priorization

105 With binary objects an additional minimum on and off time (priority 6) can be defined (e.g. for refrigerators or gas lamps). Writing to priority 6 is forbidden! Command Priorization

106 Priority Level Application Value 1 Manual-Life Safety NULL 2 Automatic-Life Safety NULL 3 Available NULL 4 Available NULL 5 Critical Equipment Control NULL 6 Minimum On/Off NULL 7 Available NULL 8 Manual Operator NULL 9 Available NULL 10 Available NULL 11 Available NULL 12 Available NULL 13 Available NULL 14 Available NULL 15 Available NULL 16 Available NULL State Automatic Output value automatic Relinquish Default 10.3 Value: 10.3 Command Priorization

107 Priority Level Application Value 1 Manual-Life Safety NULL 2 Automatic-Life Safety NULL 3 Available Available NULL 5 Critical Equipment Control NULL 6 Minimum On/Off NULL 7 Available NULL 8 Manual Operator NULL 9 Available NULL 10 Available NULL 11 Available NULL 12 Available NULL 13 Available NULL 14 Available NULL 15 Available NULL 16 Available NULL State write value on Prio 3 Output value Prio Relinquish Default 10.3 Value: 7.53 Command Priorization

108 Priority Level Application Value 1 Manual-Life Safety NULL 2 Automatic-Life Safety NULL 3 Available Available NULL 5 Critical Equipment Control NULL 6 Minimum On/Off NULL 7 Available NULL 8 Manual Operator Available NULL 10 Available NULL 11 Available NULL 12 Available NULL 13 Available NULL 14 Available NULL 15 Available NULL 16 Available NULL State write value on Prio 8 Output value Prio Relinquish Default 10.3 Value: 7.53 Command Priorization

109 Priority Level Application Value 1 Manual-Life Safety NULL 2 Automatic-Life Safety NULL 3 Available NULL 4 Available NULL 5 Critical Equipment Control NULL 6 Minimum On/Off NULL 7 Available NULL 8 Manual Operator Available NULL 10 Available NULL 11 Available NULL 12 Available NULL 13 Available NULL 14 Available NULL 15 Available NULL 16 Available NULL State write NULL on Prio 3 NULL Output value Prio 8 Relinquish Default 10.3 Value: 1.4 Command Priorization

110 Priority Level Application Value 1 Manual-Life Safety NULL 2 Automatic-Life Safety NULL 3 Available NULL 4 Available NULL 5 Critical Equipment Control NULL 6 Minimum On/Off NULL 7 Available NULL 8 Manual Operator NULL 9 Available NULL 10 Available NULL 11 Available NULL 12 Available NULL 13 Available NULL 14 Available NULL 15 Available NULL 16 Available NULL State write NULL on Prio 8 NULL Output automatic value Relinquish Default 10.3 Value: 10.3 Command Priorization

111 Demo

112 Do you have questions?

113 Alarming

114 COV Reporting (COV = Change Of Value) Alarming

115 Types of COV Reporting Unsolicited COV: Broadcast-COV, no subscriber, all devices are notified Subscribed COV: The subscribers are notified about changes of Present Value and/or Status Flags COV-Property: The subscribers are notified about changes of a single property. Alarming

116 Events and Alarms Alarming

117 Events and Alarms BACnet supports two different methods of alarming 1. Intrinsic Reporting (Alarm values are specified inside the affected object) 2. Algorithmic Change Reporting (specifies alarm detection algorithms), Event Enrollment Object observes another object s property Alarming

118 Intrinsic Reporting Object_Identifier Object_Name Object_Type Description Notification_Class 678 Priority Ack_Required Recipient_List PROPERTIES CONFORMANCE CODE Object_Identifier R Object_Name R Object_Type R Present_Value R Description O DeviceType O Status_Flags R Event_State R Reliability O Out_Of_Service R Units R Min_Pres_Value O Max_Pres_Value O Resolution O Priority_Array R Relinquish_Default R COV_Increment O Time_Delay O Notification_Class O High_Limit O Low_Limit O Deadband O Limit_Enable O Event_Enable O Acked_Transitions O Notify_Type O PROPERTIES CONFORMANCE CODE Object_Identifier R Object_Name R Object_Type R Present_Value R Description O DeviceType O Status_Flags R Event_State R Reliability O Out_Of_Service R Units R Min_Pres_Value O Max_Pres_Value O Resolution O Priority_Array R Relinquish_Default R COV_Increment O Time_Delay O Notification_Class O High_Limit O Low_Limit O Deadband O Limit_Enable O Event_Enable O Acked_Transitions O Notify_Type O Objects that generates an alarm (Present-Value) Notification Class Server Client Alarming

119 Algorithmic Change Reporting Object_Identifier Object_Name Object_Type Description Event_Type Notify_Type Event_Parameters Object_Property_Reference Event_State Event_Enable Acked_Transitions Notification_Class Event_Time_Stamps Profile_Name Object_Identifier Object_Name Object_Type Description Notification_Class 678 Priority Ack_Required Recipient_List Alarming

120 Alarm Detection (Analog) Time Alarming

121 state Alarm Detection (Binary) Time-Delay Time-Delay active TO_OFFNORMAL TO_NORMAL inactive time In this example the state active generates the alarm. Alarming

122 Types of alarm states TO_OFFNORMAL transition to non-normal state TO_NORMAL back to normal state TO_FAULT fault state, e.g. open loop, shorted loop Alarming

123 Binary / Multistate Detection In Binary objects the alarm value is specified by a separate property alarm-value. In Multistate objects the values to generate alarms is specified by the property alarm-values (list), fault values are specified by the property fault-values (list). Output objects compare the Present-value against the feedback value. Alarming

124 The Alarming Algorithms CHANGE_OF_BITSTRING CHANGE_OF_STATE CHANGE_OF_VALUE COMMAND_FAILURE FLOATING_LIMIT OUT_OF_RANGE BUFFER_READY CHANGE_OF_LIFE_SAFETY UNSIGNED_RANGE double-out-of-range signed-out-of-range unsigned-out-of-range change-of-characterstring Alarming

125 Demo

126 Do you have questions?

127 Communication

128 Communication BACnet uses a de-centralized approach. The properties of a BACnet device are made accessible to other network participants via the device object. All objects and properties can be read and written by other devices. Communication

129 Connecting to the Network Clients can use the Who-Is service to find out which BACnet servers are on the network. The BACnet servers send I-Am telegrams at startup or as a response to Who-Is (if supported). Communication

130 Connecting to the Network Communication

131 Usage of Objectnames Usage of Objectnames as a reference requires that the physical address must be obtained dynamically. For this, the service Who-Has is used, e.g. Who-Has Outside Temperature Sensor Communication

132 Demo

133 Specifiying

134 PICS Protocol Implementation Conformance Statement Specifying

135 PICS ANNEX A - PROTOCOL IMPLEMENTATION CONFORMANCE STATEMENT (NORMATIVE) BACnet Protocol Implementation Conformance Statement Date: Vendor Name: Product Name: Product Model Number: Applications Software Version: Firmware Revision: BACnet Protocol Revision: Product Description: Specifying

136 PICS BACnet Standardized Device Profile (Annex L): Workstations / Management Stations: BACnet Advanced Operator Workstation (B-AWS) BACnet Operator Workstation (B-OWS) BACnet Operator Display (B-OD) Controllers: BACnet Building Controller (B-BC) BACnet Advanced Application Controller (B-AAC) BACnet Application Specific Controller (B-ASC) BACnet Smart Sensor (B-SS) BACnet Smart Actuator (B-SA) Specifying

137 PICS List all BACnet Interoperability Building Blocks Supported (Annex K): DS-RP-A DS-RP-B etc. Segmentation Capability: Segmented requests supported Segmented responses supported Window Size Window Size Specifying

138 PICS Standard Object Types Supported: For each standard Object Type supported provide the following data: 1) Whether objects of this type are dynamically creatable 2) Whether objects of this type are dynamically deletable 3) List of the optional properties supported 4) List of all properties that are writeable where not otherwise required by this standard 5) List of proprietary properties and for each its property identifier, data type, and meaning 6) List of any property range restrictions Specifying

139 PICS Data Link Layer Options: BACnet IP, (Annex J) BACnet IP, (Annex J), Foreign Device ISO , Ethernet (Clause 7) ASTM 878.1, 2.5 Mb. ARCNET (Clause 8) ASTM 878.1, RS-485 ARCNET (Clause 8) baud rate(s) MS/TP master (Clause 9), baud rate(s): MS/TP slave (Clause 9), baud rate(s): Point-To-Point, EIA 232 (Clause 10), baud rate(s): Point-To-Point, modem, (Clause 10), baud rate(s): LonTalk, (Clause 11), medium: BACnet/ZigBee (ANNEX O) Other: Specifying

140 Networking Options: Router, Clause 6 - List all routing configurations, e.g., ARCNET- Ethernet, Ethernet-MS/TP, etc. Annex H, BACnet Tunneling Router over IP BACnet Broadcast Management Device (BBMD) Does the BBMD support registrations by Foreign Devices? Yes No Does the BBMD support network address translation? Yes No Network Security Options: PICS Non-secure Device - is capable of operating without BACnet Network Security Secure Device - is capable of using BACnet Network Security (NS-SD BIBB) Multiple Application-Specific Keys: Supports encryption (NS-ED BIBB) Key Server (NS-KS BIBB) Specifying

141 Character Sets Supported: Indicating support for multiple character sets does not imply that they can all be supported simultaneously. ISO (UTF-8)* IBM /Microsoft DBCS ISO ISO (UCS-2) ISO (UCS-4) JIS X 0208 Gateway to: Describe the gateway capabilities PICS * changed in Rev. 10, before this was the 7-bit ANSI X3.4 character set Specifying

142 BACnet Interoperability Building Blocks

143 BIBBs is the shortcut for: BACnet Interoperability Building Blocks BIBBs BACnet Interoperability Building Blocks

144 BIBBs BIBBs allow a significantly more accurate specification of the functions supported by a device. BIBBs are part of the standard BIBBs are defined in Annex K BACnet Interoperability Building Blocks

145 Services categories Data Sharing Alarms/Events Time Schedules Trend Data Trends Device Management BACnet Interoperability Building Blocks

146 BIBBs A class A device defines a user (requestor) of data and functions (client) A class B device defines a provider of data and functions (server) BACnet Interoperability Building Blocks

147 BIBBs Example (DS-RP-A) Data Sharing ReadProperty A BACnet Service Initiate Execute ReadProperty x Client Server A BACnet Interoperability Building Blocks

148 BIBBs Example (DS-RP-B) Data Sharing ReadProperty B BACnet Service Initiate Execute ReadProperty x Client Server B BACnet Interoperability Building Blocks

149 Device Profile and Interoperability Areas BACnet Interoperability Building Blocks

150 BACnet Profiles: MANAGEMENT LEVEL AWS OWS OWS Advanced Work Station (B-AWS) Operator Work Station (B-OWS) Operator Display (B-OD) AUTOMATION LEVEL BC R HMI OWS BC BC Building Controller (B-BC) FIELD LEVEL AAC AAC ASC AAC AAC ASC Advanced-Application Controller (B-AAC) Application-Specific Controller (B-ASC) Smart Sensor/Actuator (B-SS and B-SA) INPUT/ OUTPUT DEVICES S A S A BACnet Interoperability Building Blocks

151 Data Sharing A= User, B= Provider BACnet Interoperability Building Blocks

152 Alarms and Events A= User, B= Provider BACnet Interoperability Building Blocks

153 Scheduling A= User, B= Provider BACnet Interoperability Building Blocks

154 Trending A= User, B= Provider BACnet Interoperability Building Blocks

155 Device and Network Management 1 Not required if the device is a BACnet MS/TP Slave. 2 Not required for devices claiming conformance to a Protocol_Revision < 7. A= User, B= Provider BACnet Interoperability Building Blocks

156 Do you have questions?

157 Engineeringsafspraken

158 Engineeringsafspraken Algemeen In het bestek dient niet alleen het BACnet Profiel geëist te worden maar ook met welke objecten en diensten de specifieke functies worden gerealiseerd. Alle Functionaliteit moet in de regelaar en GBS worden geëngineerd met standaard BACnet objecten en diensten. Alle nieuwe installaties moeten met de nieuwst standaard worden gemaakt. De PICS moeten met de aanbieding worden meegestuurd. Alle restricties moeten worden vastgelegd: Interoperabiliteitstest uitvoeren voor opdrachtverstreking. Engineeringsafspraken

159 Engineeringsafspraken Algemeen Planning en beheer van device en netwerk nummers met B-PAT Tijdsynchronisatie via Broadcast? BBMD planning noodzakelijk Functionaliteit en beheer Alleen BACnet communicatie toestaan en geen propritaire communicatie. Engineeringsafspraken

160 Engineeringsafspraken Algemeen De klant krijgt alle systeem wachtwoorden voor ongelimiteerde toegang tot het systeem De klant krijgt een ongelimiteerde engineeringstool voor het engineeren van de onderstations De klant wordt volledig opgeleid om zelf het systeem te engineren en beheren. Wijzigingen gedaan met een B-OWS ( setpoints, en objecten aangemaakt) zullen ten alle tijden eenvoudig worden overgenomen door de engineringstools. Engineeringsafspraken

161 Engineeringsafspraken GBS Het GBS moet zelfstandig BACnet apparaten vinden en uitlezen zonder engineering Het GBS ondersteund het dynamisch aanmaken/verwijderen van objecten in alle apparaten. Het GBS ondersteund UTC tijdsynchronisatie. Alarmen: Alarmen moeten vanuit het Onderstation gestuurd worden en niet op basis van COV aan de Present Value of status_flags gekoppeld waarna er in het GBS een alarm van wordt gemaakt. Ondersteuning van intrisic en algorithmic alarming Niet automatische abonneren op alle alarmgroepen Engineeringsafspraken

162 Klokken: Trends: Engineeringsafspraken GBS Ondersteuning van meerdere typen aan/uit; setpoints;dag/nacht/eco/boost Ondersteuning van uitzonderingsprogramma s in de klok of in een kalender object. De gebruiker moet zelf trends kunnen aanmaken via het GBS in de Onderstations Historische opslag in een database. Engineeringsafspraken

163 Engineeringsafspraken DDC De controller moet volledig geëngineerd worden zodat er op het Management niveau geen additionele engineering noodzakelijk is. Status teksten, Eenheden De object naam en omschrijving moeten voldoen aan: Object Name > 30 karakters, klantspecifieke structuur Object Description > 40 karakters en schrijfbaar, Consistente opbouw: gebouw, proces, apparaat,ect. Minimum aantal COV s > 100 Welke properties schrijfbaar zijn in welke situaties. Fysieke in-/uitgangen moeten ook op BACnet in en uitgangen worden gepresenteerd en Present Value moet gelijk zijn met de werkelijke waarde. De DDC moet aanmaken en verwijderen van objecten ondersteunen voor de volgende objecten: Alarmen en Trend log Engineeringsafspraken

164 Engineeringsafspraken DDC Alarmen: Ondersteuning van intrinsic en algorithmic alarming Minmaal 3 vrij defineerbare alarmniveau s Versturen met message tekst Klokken: Ondersteuning van meerdere typen aan/uit; setpoints;dag/nacht/eco/boost Ondersteuning van uitzonderingsprogramma s in de klok of in een kalender object. Trends: Aanmaken voor alle AI,AO en berekende waarden. Dynamisch aanmaken door GBS in onderstation Engineeringsafspraken

165 Freeware tools: Testing and Tools Wireshark ( Visual Test Shell for BACnet( Tools

166 Wireshark Demo Capture Filters: udp port Filters: bacnet all BACnet trafic bvlc.function == 0x0b BACnet/IP Broadcast packets bacapp.confirmed_service == 12 BACnet ReadProperty packets bacapp.confirmed_service == 15 BACnet WriteProperty packets bacapp.unconfirmed_service == 0 BACnet I-Am packets bacapp.unconfirmed_service == 8 BACnet WhoIs packets bacapp.unconfirmed_service == 2 BACnet Unconfirmed COV Notification packets Tools

167 Positie communicatiebussen BACnet LON Dali KNX Compare

168 LON eigenschappen Local Operating Network Single Chip solution Multiple vendor system Paid per node Up to 64 nodes without repeaters Standard Netwerk Variable Types Engineeringstools for Bindings LON

169 KNX Eigenschappen 1. Internationale Standaard, dus toekomstgericht 2. Productcertificering zorgt voor interoperabiliteit & inter-working 3. PC software tool ETS kan u alle KNX-gecertificeerde producten plannen, in bedrijf nemen en configureren. 4. KNX kan gebruikt worden voor alle applicaties in huis- en gebouwcontrole KNX

170 KNX Eigenschappen 5. KNX ondersteunt verschillende communicatiemedia Twisted Pair (TP) Power Line (PL) Radio Frequentie(RF) IP/Ethernet KNX

171 KNX Eigenschappen 6. KNX is onafhankelijk van andere hard- of softwaretechnologie Fabrikanten kunnen een eigen microprocessorplatform ontwikkelen of ze kunnen gebruik maken van providers van KNXsysteemcomponenten. KNX is volledig vrij van aanvullende royalties. KNX

172 KNX Eigenschappen 7. KNX kan aan andere systemen gekoppeld worden KNX heeft vooruitstrevende gateways om andere systemen te ondersteunen en aan te vullen. Bewijzen van samenwerking met KNX zijn : Mapping met BACnet. Interface met DALI mogelijk. KNX

173 Dali Eigenschappen Maximum number of devices 64 Number of Groups 16 Number of Scenes per Group 16 Dali

174 Why should I use it? Easily reconfigure Lighting can be tailored Open protocol Simple Installation DALI allows pre-set lighting scenarios Two-way communication Queried for lamp and ballast failure Dali

175 BACnet and big data