US9400493B2 - System and method for automatically naming objects in a building automation system - Google Patents
System and method for automatically naming objects in a building automation system Download PDFInfo
- Publication number
- US9400493B2 US9400493B2 US13/432,417 US201213432417A US9400493B2 US 9400493 B2 US9400493 B2 US 9400493B2 US 201213432417 A US201213432417 A US 201213432417A US 9400493 B2 US9400493 B2 US 9400493B2
- Authority
- US
- United States
- Prior art keywords
- name
- view node
- child
- parent
- building automation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000009877 rendering Methods 0.000 claims 1
- 230000008569 process Effects 0.000 abstract description 11
- 230000006870 function Effects 0.000 description 16
- 238000004378 air conditioning Methods 0.000 description 12
- 238000010438 heat treatment Methods 0.000 description 12
- 230000008901 benefit Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000009423 ventilation Methods 0.000 description 8
- NNBAXWAPIROUSM-UHFFFAOYSA-N 1-(4-morpholin-4-ylphenyl)pyrrole-2,5-dione Chemical compound O=C1C=CC(=O)N1C1=CC=C(N2CCOCC2)C=C1 NNBAXWAPIROUSM-UHFFFAOYSA-N 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 238000012423 maintenance Methods 0.000 description 3
- 239000000463 material Substances 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000005286 illumination Methods 0.000 description 2
- 230000005055 memory storage Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000000638 solvent extraction Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000005611 electricity Effects 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000002604 ultrasonography Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B15/00—Systems controlled by a computer
- G05B15/02—Systems controlled by a computer electric
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/23—Pc programming
- G05B2219/23255—Object oriented programming, OOP
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/26—Pc applications
- G05B2219/2614—HVAC, heating, ventillation, climate control
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/26—Pc applications
- G05B2219/2642—Domotique, domestic, home control, automation, smart house
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L2012/2847—Home automation networks characterised by the type of home appliance used
- H04L2012/285—Generic home appliances, e.g. refrigerators
Definitions
- the present invention generally relates to building systems and, more particularly, to systems, processes, and methods for efficiently communicating with a plurality of field devices in a hierarchal structure.
- a building automation system is an arrangement for monitoring, open-loop control and/or closed-loop control of process variables in complex technical systems in a building, or in a campus comprising a number of buildings.
- a building automation system typically operates heating, ventilation and air-conditioning systems, lighting and shading devices and also access control, security and fire surveillance systems.
- process variables such as room air conditioning variables or events for example—are detected, evaluated, monitored, influenced or generated, with the energy consumption of the building or campus also advantageously being optimized by the building automation system.
- a building automation system encompasses and operates a plurality of what are known as field devices, such as sensors and actuators.
- field devices such as sensors and actuators.
- typical field devices are temperature and humidity sensors, air quality sensors, pressure sensors, flow meters, electricity meters, heat meters, brightness sensors, fire alarms, intrusion alarms, alarm or sprinkler devices, drives for hot water valves, thermostat valves, ventilation flaps or blinds, light switches, smart card readers or devices for detecting biometric data.
- the building automation system typically comprises a plurality of software modules, processes or programs, and in general a number of computers or processors for their activation and also as a rule a plurality of open-loop and closed-loop control devices as well as further devices, for example devices for linking the building automation system to external communication networks, screens of devices for analysis of video signals.
- the elements (objects or field devices) of a building automation system are widely dispersed throughout a facility.
- an HVAC system includes temperature sensors and ventilation damper controls as well as other elements that are located in virtually every area of a facility.
- a security system may have intrusion detection, motion sensors and alarm actuators dispersed throughout an entire building or campus.
- fire safety systems include smoke alarms and pull stations dispersed throughout the facility.
- Electrical or wireless communication media are used in a building automation system for the exchange of data of individual devices or parts of systems, as a rule a number of communication networks exist, with cables, optical data communication channels, ultrasound connections, electromagnetic near fields or radio networks able to be used, including fiber optic networks or cellular networks for example.
- technologies or standards able to be used for the said data exchange are BACnet, LON or LonWorks® from the company ECHELON, the European Installation bus EIB, KONNEX, ZigBee or PROFIBUS defined by German standard DIN 19245.
- Building automation systems typically have one or more centralized control stations in which data from each of the elements in the system may be monitored and in which various aspects of system operation may be controlled and/or monitored.
- the control station typically includes a computer having processing equipment, data storage equipment, and a user interface.
- building automation systems often employ multi-level communication networks to communicate operational and/or alarm information between operating elements, such as sensors and actuators, and the centralized control station.
- APOGEE® INSIGHT® Workstation available from Siemens Industry, Inc. of Buffalo Grove, Ill., which may be used with the model APOGEE® building automation system, also available from Siemens Industry, Inc. (APOGEE and INSIGHT are U.S federally registered trademarks of Siemens Industry, Inc.)
- APOGEE and INSIGHT are U.S federally registered trademarks of Siemens Industry, Inc.
- several control stations connected via an Ethernet or another type of network, may be distributed throughout one or more building locations, each having the ability to monitor and control system operation. As a consequence, different people in different locations of the facility may monitor and control building operations.
- the typical building automation system (including those utilizing the APOGEE® Insight® Workstation) has a plurality of field panels and/or controllers that are in communication with a workstation.
- the building automation system also includes one or more field devices connected to the field panels and/or controllers. Each field device is typically operative to measure and/or monitor various building automation system parameters.
- each field device may include one or more sensors and/or actuators to measure and/or monitor corresponding “points” within the respective building and/or building automation system
- a “point” may be (i) any physical input or output to or from a respective controller, field device, sensor or actuator, or (ii) any virtual point associated with a control application or logic object within a controller or field panel that is measured, monitored or controlled.
- the workstation is generally used to make modifications and/or changes to one or more of the various components of the building automation system
- a field panel may also be operative to enable certain modifications and/or changes to one or more parameters of the system. This typically includes parameters such as a temperature set point or other set points in a field device controller or directly in a field device.
- the workstation may be configured to modify a control program or the like in a field panel for controlling a field device.
- Each of the individual field devices, components, and sub-components needs to be entered and manually assigned a name in the building automation system so that the building automation system can communicate with the object.
- the naming of each of the objects is time consuming and error prone for at least these reasons.
- a method for naming a plurality of building automation objects of a building automation model includes providing a building automation device; providing a building automation model including a parent view node object representing the building automation device and a child view node object logically linked to a field device, wherein the child view node object is logically linked to the parent view node object forming a hierarchical structure; assigning an object-name to the parent view node object representing a name of the building automation device; and assigning an object-name to the child view node object including the object-name of the parent view node object and a name representing the field device.
- a system for representing a hierarchal structure representing one or more building automation devices and one or more field devices includes a parent view node object representing a building automation device and logically linked to a plurality of child view node objects, wherein each of the plurality of child view node objects is logically linked to a field device; wherein the parent view node object includes an object-name, and wherein each of the plurality of child view node objects includes an object-name representing the field device to which each of the plurality of child view node objects is logically linked.
- a computer readable storage medium having stored therein data representing instructions executable by a programmed processor for iterating through a hierarchal structure representing one or more building automation devices and one or more field devices.
- the storage medium includes instructions for accessing a parent view node object; accessing a child view node object; logically linking the child view node object to the parent view node object; assigning an object-name to the parent view node object; and assigning an object-name to the child view node object representing a field device logically linked to the child view node object.
- FIG. 1 illustrates a functional block diagram of a structure of a building automation system for operating a section of a building
- FIG. 2 illustrates a functional diagram for modeling a further building section, having a number of rooms or zones, able to be operated by the building automation system;
- FIG. 3 illustrates a functional block diagram of a plurality of building automation devices together implementing a building automation model
- FIG. 4 further illustrates the functional block diagram of a plurality of building automation devices together implementing a building automation model illustrated in FIG. 3 ;
- FIG. 5 illustrates a hierarchical naming structure of a building automation model
- FIG. 6 illustrates another hierarchical naming structure of a building automation model
- FIG. 7 illustrates another hierarchical naming structure of a building automation model
- FIG. 8 illustrates another hierarchical naming structure of a building automation model
- FIG. 9 illustrates a method of inserting and naming building automation objects to form a building automation model
- FIG. 10 illustrates the partitioning of the object name and possible optional and mandatory inputs for constructing an object name.
- FIG. 11 illustrates the part field delimiters and part field length rules for constructing an object name
- FIG. 12 illustrates a graphical user interface system for defining naming rules
- FIG. 13 illustrates a graphical user interface system having naming rules applied.
- FIGS. 1-13 A more detailed description of the embodiments will now be given with reference to FIGS. 1-13 .
- like reference numerals and letters refer to like elements.
- the present disclosure is not limited to the embodiments illustrated; to the contrary, the present disclosure specifically contemplates other embodiments not illustrated but intended to be included in the claims.
- FIG. 1 illustrates a room 1 of a building section able to be operated by a building automation system by controlling and/or monitoring field devices therein.
- Assigned to the room 1 are a number of field devices, by the use of which for example a desired comfort for users and a required safety for users and infrastructure with optimized operating costs are able to be achieved.
- Typically assigned to the room 1 are a room unit 2 , a light switch 3 , an air conditioning register 4 , a heating element 5 , a heating register 6 and a blind drive 7 , although other configurations are contemplated.
- the room unit 2 serves as the user interface to the building automation system, including but not limited to, to enter a nominal room temperature range and to display the current room temperature as well as to display an order of magnitude of the costs of the energy consumed by the room 1 .
- the devices operated in the room 1 are advantageously modeled in the software of the building automation system as far as is necessary and corresponding models are preferably implemented using an object-oriented approach.
- the models are connected via input/output modules (or building automation objects, also referred to as BA objects) to field devices.
- the room unit 2 is mapped by a room unit model (or BA object) 10 , the light switch 3 by a light switch model (or BA object) 11 , the air conditioning register 4 by an air conditioning register model (or BA object) 12 , the lighting element 5 by a lighting element model 13 , the heating register 6 by a heating register model (or BA object) 14 and the blind drive 7 by a blind drive model (or BA object) 15 in the building automation system.
- the first overview node 20 is an object of the building automation system and features an overview list (also referred to as a view node item list) 21 , which has at least one semantic information unit.
- the semantic information unit identifies an automation function, which is provided in the room 1 represented by the first overview node 20 .
- the semantic information unit contains at least one identifier suitable for identification and a relation to the automation function involved.
- the name is advantageously a string data type with a fixed or variable length.
- a collection of semantic information units (also referred to a view node item list) may include a logically linked list of semantic information units to one or more parent or child nodes.
- a specific relationship between two nodes or objects of the building automation system is designated in this text by the term relation such that they form one or more parent-child relationships.
- the relation has a predefined type range which comprises at least two different relation types.
- a contacts (or connects) relation and what is known as “an owns” relation are defined or a logically linked/connected relationship.
- the contacts relation is identical here to the relation with the value “contacts” and means here that this relation is implemented such that the relation is suitable for a bidirectional data exchange between the nodes or objects concerned.
- the owns relation is identical here to the relation with the value “owns” and means here that this relation is implemented such that the relation is suitable one the one hand for a bidirectional data exchange between the nodes or objects concerned, on the other hand nodes or objects with the owns relation are advantageously existentially linked to one another such that they can only be copied, moved and deleted together, by an engineering tool for example.
- the overview list 21 has space for nine semantic information units 21 . 1 to 21 . 9 together forming a collection of semantic information units (also referred to as a view node item list).
- the semantic information in the parent item list may be taken, at least in part, from a logically linked/connected child object (e.g. its part name).
- similar sharing of information from a parent object logically connected to one or more child objects may share a number of other types of information, including but not limited to, semantic information. Accordingly, information may be shared, transferred, and reused among parent and child objects.
- a semantic information unit able to be identified by an identifier “chilled ceiling” has an owns relation 27 , which applies between the first overview node 20 and the air conditioning register model 12 .
- a semantic information unit able to be identified by an identifier “radiator” has an owns relation 29 which applies between the first overview node 20 and the air conditioning register model 14 .
- a semantic information unit able to be identified by an identifier “blind” has its own relation 9 , which applies between the first overview node 20 and the blind drive model 15 .
- HVAC heating, ventilation and air conditioning
- the second overview node 30 is an object of the building automation system and has an overview list 31 for storage of semantic information units 31 . 1 to 31 . 4 (also referred to as a view node item list).
- SS identifier
- HVAC current information on the operating state of the automation functionality
- Ts i.e. temperature setpoint value
- HVAC automation functionality
- a semantic information unit 31 . 3 able to be identified by an identifier “chilled ceiling” has a contacts relation 38 , which applies between the second overview node 30 and the air conditioning register model 12 .
- a semantic information unit able to be identified by an identifier “radiator” has a contacts relation 39 , which applies between the second overview node 30 and the heating register model 14 .
- the second overview node 30 has a further an owns relation 37 , which applies between the second overview node 30 and an open-loop and/or closed-loop control program 32 .
- the automation function required for heating, ventilation and air conditioning of the building section is programmed in the open-loop and/or closed-loop control program 32 .
- the open-loop and/or closed-loop control program 32 , the second overview node 30 and the further objects 35 and 36 , linked by an owns relations to the overview node 30 form a functional unit through the said an owns relation 37 .
- the third overview node 40 is an object of the building automation system and has an overview list 41 for storing semantic information units 41 . 1 to 41 . 4 .
- the third overview node 40 has an owns relation 47 , which applies between the third overview node 40 and an open-loop and/or closed-loop control program 42 .
- the automation function required for light control in the assigned building section is programmed in the open-loop and/or closed-loop control program 42 .
- the open-loop and/or closed-loop control program 42 and the third overview node 40 form one functional unit through the said owns relation 47 .
- the opportunity of the available relations to have an effect makes possible access for reading and writing of data, between the open-loop and/or closed-loop control program 42 on the one hand and objects connected via relations with the third overview node 40 on the other hand, indirectly via the overview node 40 .
- the described structure of the functional unit makes possible the inclusion and replacement of field devices into the building automation system, without program code in the open-loop and/or closed-loop control program 42 concerned having to be adapted for this purpose.
- the semantic information units stored in the overview list 21 , 31 or 41 are advantageously able to be identified via predefined or standardized designations. This enables operator views, for a control center or management system of the building automation system for example, to be generated in a user-friendly manner and with relatively little effort. By using predefined designations by means of the string data type for the semantic information units a currently-installed building automation system is able to be documented with relatively little effort.
- the overview list 21 , 31 or 41 is ordered or sorted in accordance with certain rules.
- Advantageously device models will be provided with a designation which is able to be evaluated on generation or checking of a relation. If for example, as shown in FIG. 1 , the semantic information unit 21 . 9 of the overview list 21 1 assigned to the room 1 is identified by the character string “blind” and also the corresponding blind drive model 15 is marked with the same identifier, the generation or checking of the owns relation 9 will be simplified and able to be automated.
- the building sections to be operated by the building automation system are typically divided into rooms with—under some circumstances—very different requirements, or by a grid with grid elements with similar or identical requirements.
- Overview nodes are advantageously used in advantageous modeling of rooms and grid elements.
- Grid elements are typically produced by an arrangement of support structures or window structures in the building section.
- Flexible modeling of the building is achieved by the use of two different types of overview node, a first type for a room and a second type for grid elements.
- Overview nodes of the type designed for a room are typically labeled “RM”, i.e. room, in the drawing, overview nodes of the type designed for grid elements are labeled “GD”, i.e. grid or grid element.
- the overview node 20 shown in FIG. 1 for room 1 is accordingly of type “RM”.
- Overview nodes of type “GD” can be linked dynamically to an overview node of type “RM”.
- FIG. 2 a building section divided into the grid is labeled 60 , having a first grid element 62 and a second grid element 61 .
- the grid structure of the building section 60 is provided here by support structures 63 for example.
- the devices assigned to the two grid elements 62 and 61 are reduced here to a minimum for the sake of simplification, since only the principle of the advantageous modeling is to be presented.
- Grid element 62 or 61 thus comprises a room unit 65 or 64 , a heating register 69 or 68 , and a blind drive 67 or 66 .
- the devices operating the grid element 62 or 61 are advantageously modeled in the software of the building automation system as far as necessary and corresponding models are advantageously implemented using an object-oriented approach.
- the models are typically connected via input/output modules to the field devices.
- the room unit 65 or 64 will be mapped by room unit model 85 or 95 respectively and the blind drive 67 or 66 by a blind drive model 86 or 96 respectively in the building automation system.
- the fourth overview node 70 has an overview list 71 for storage of semantic information units 71 . 1 , 71 . 2 , 71 . 3 and 71 . 4 which may be logically linked to one or more child view node objects (such as child view node objects 80 , 90 ).
- a semantic information unit 71 . 2 able to be identified by the identifier “HVAC”—i.e.
- heating, ventilation and air conditioning has an owns relation 75 , which is between the fourth overview node 70 and a functional unit is not shown in the diagram, through which for example the heating, ventilation and air conditioning functionality is guaranteed to the entire building section.
- the overview list 71 comprises a semantic unit 71 . 3 able to be identified with the identifier “bld-A- 1 ” and a semantic unit 71 . 4 able to be identified with the identifier “bld-A- 2 ”.
- a current grid division of the building section 60 is stored by means of semantic information units of the overview list 71 .
- the semantic information unit 71 . 3 has a contacts relation 73 which applies between the fourth overview node 70 describing the building section 60 and a fifth overview node 80 .
- the semantic information unit 71 . 4 has a contacts relation 74 which applies between the fourth overview node 70 and a sixth overview node 90 .
- the totality of the automation functions specifically available for the room 1 is listed in the fifth overview node 80
- the totality of the automation functions specifically available for the second grid element 61 in the sixth overview node 90 is listed in the fifth overview node 80
- Semantic information relating to the first grid element 62 is stored in the overview list 81 in the fifth overview node 89 .
- semantic information relating to the second grid element 61 is stored in the overview list 91 in the sixth overview node 90 .
- nodes are able to be copied during engineering, relations are able to be checked with the aid of suitable identifiers by an engineering tool or at runtime automatically; and field devices, grids and scope of the available functionality of building sections are able to be changed without modifications having to be made to the program code of open-loop and/or closed-loop control programs since the closed-loop and or open-loop control programs access field devices directly via overview nodes.
- FIG. 3 illustrates a functional block diagram of a plurality of building automation devices 304 a - 304 c together implementing building automation model 302 together forming system 300 .
- Building automation devices 304 a - 304 c include one or more view node objects 310 - 316 together comprising a collection of view node objects 308 within each building automation device 304 a - 304 c .
- some objects are illustrated as binary output objects (e.g. 310 ) and some are illustrated as binary input objects (e.g. 312 - 314 ) such that the object provides binary output or receives binary input, respectively from a respective field device or subcontroller of a respective field device (which is not illustrated in FIG. 3 ).
- Other types of inputs and outputs are contemplated, including but not limited to, analog inputs and outputs, multistate inputs and outputs, value objects, and any combination thereof from a respective field device or subcontroller of a respective field device.
- Every view node object 310 - 316 includes at least one object-name 310 a - 316 a which designates the view node objects 310 - 316 within the respective building automation device 304 a - 304 c .
- namespace of object-name 310 - 316 spans a single automation device 304 a - 304 c .
- Building automation model 302 does not impose any fixed, predefined syntactical or semantic naming schema on object-name 310 a - 316 a . Nevertheless, a free or hierarchical naming convention may be applied to automatically configure object-names during engineering.
- Every building automation device 304 a - 304 c also features a device-name 306 a - 306 c which uniquely designates building automation device 304 a - 304 c within the complete building automation model 302 .
- the namespace 308 of device-name 306 a - 306 c spans the complete building automation model 302 .
- No fixed, predefined syntactical or semantic naming schema is imposed on a device-name 306 a - 306 c . Nevertheless, a free or hierarchical naming convention may be applied to automatically configure device-names 306 a - 306 c during engineering.
- view node object 304 illustrates a technical naming designation wherein the object name follows some technical-predefined scheme.
- View node object 304 b illustrates a user designation naming criteria, wherein the name scheme is decided by a user—often time on a whim.
- View node object 304 c illustrates a free designation naming scheme wherein the name of object can be anything such that it does not adhere to any set criteria or scheme.
- object-names 310 a - 316 a may be used to reference view node objects 310 - 316 .
- object-names 310 a - 310 c of view node objects 310 - 316 as a reference may not be ensured because: (1) an object-name may be modified by engineering functions; (2) an object-name may be set-up as a standardized technical designation or as project-specific user designation; or (3) a user designation as an object-name may be set up in a late project phase or even by the end customer.
- errors such as duplications, incorrect naming format, or other problems may occur.
- FIG. 4 further illustrates a functional block diagram of a plurality of building automation devices 304 a - 304 c together implementing building automation model 302 , together forming system 300 illustrated in FIG. 3 .
- every view node object 310 - 316 features an object-identifier 310 b - 316 b which uniquely identifies view node object 310 - 316 within building automation device 304 a - 304 c .
- Every building automation device 304 a - 304 c also features a device-identifier 406 a - 406 c which identifies uniquely building automation device 304 a - 304 c within the building automation model 302 .
- Object-identifiers 310 b - 316 b and device-identifiers 406 a - 406 c may be used to reference a building automation device 304 a - 304 c .
- the integrity of each of object-identifiers 310 b - 316 b and device-identifiers 406 a - 406 c reference will be ensured, because these identifiers may not be modified by engineering functions as illustrated in FIGS. 5-7 as may be employed in an engineering tool 1400 (illustrated in FIG. 4 ) for initially configuring or commissioning the building automation devices and object identifiers for the view node objects 310 - 316 to be employed in each building automation device.
- engineering functions will assign a standardized technical designation to object-name 310 a - 310 c .
- the technical designation will be derived from the standardized engineering representation of the technical view.
- the applied namespace of the technical designations may either span one or more building automation devices (local namespace) or the complete building automation model (global namespace).
- the assigned object-name will be considered as technical view independent from the user-specified view and the namespace as local.
- a building automation device and/or the building automation model may include processing circuitry/logic configured to access and execute a control program that is stored in memory (such as random access memory, cache memory or other volatile memory storage device or computer readable media) or secondary storage (such as read only memory, non-volatile flash memory, hard drive, memory stick or other non-volatile memory storage device or computer readable media).
- the control program may be a separate program or a program module of the building automation device.
- the control program may include an operating system (such as Linux or other conventional operating system).
- the control program instructs and interacts with a hierarchy of objects representing building automation objects throughout building automation model represented as a plurality of view node objects configured in a hierarchal structure, such as one or more view node object parents and one or more view node object children, to assign a name to the object. Accordingly, the control program may iterate through the one or more parent view node objects and the one or more child view node objects logically linked to the one or more parent view node objects and read and/or write data within any object so as to communicate with one or more field devices (including but not limited to sensors and actuators) logically linked to the one or more child view node objects.
- one or more field devices including but not limited to sensors and actuators
- FIG. 5 illustrates a hierarchical naming structure 500 of a building automation model 502 including a field device corresponding to an air handling unit represented by view node object 504 .
- Building automation model 502 includes a plurality of view node objects 504 - 518 , similar to those illustrated in FIGS. 3-4 .
- the hierarchal system forms a logical tree of parent-child nodes such that each child is logically linked to its parent forming a logically linked list. Accordingly, by iterating from the parent node, each of the children, grandchildren, and so forth are able to be discovered.
- view node objects 504 - 518 are ordered in a hierarchy such that view node object 504 is a parent of view node object 506 , which is a parent of view node objects 508 - 512 , wherein view node object 512 is the parent of view node objects 514 - 518 . Accordingly, view node objects 514 - 518 are children of view node object 512 , which is a child of view node object 506 , which is a child of view node object 504 . In the example illustrated in FIG.
- object 514 is a binary output object of the pump field device identified by the view node object 512 having the object-name of AHU 1 Hcl.Pu such that it provides output data in binary format
- objects 516 - 518 are binary input objects such that they accept binary data.
- Other types of inputs and outputs are contemplated, including but not limited to, analog inputs and outputs, multistate inputs and outputs, value objects, and any combination thereof from a respective field device or subcontroller of a respective field device.
- the one or more last children in the hierarchal chain is logically linked to a field device such that data correlating to the field device, including data to operate the field device, may be read or written thereto.
- view node object 506 has an object-name of AHU 1 .Hcl, wherein AHU 1 is the name of the parent view node object 504 of child view node object 506 .
- AHU 1 designates field device air handling unit 1 ;
- Hcl designates preheating coil.
- View node object 514 has an object-name comprised of its name, the object-name of its parent view node object 512 (which comprises the object-name of its parent 506 and the object-name of its parent 504 ).
- the individual portion of a name representing a specific object may follow a naming scheme, including but not limited to: AHU 1 designating air handling unit 1 ; Hcl designating preheating coil; Pu designating pump; Cmd designating command; FrPrt designating frost protection air temperature; Vlv designating valve; Fb designating feedback; ThOvrld designating thermal overload; SuB designating supply air box; R 1 designating room control 1 ; MntSwi designating maintenance switch; RC designating room control; OccSens designating occupancy sensor; HVAC designating an HVAC device; other names of objects are contemplated and are not limited to the exemplary names illustrated herein.
- the object-name of view node object 514 is AHU 1 .Hcl.Pu.Cmd wherein AHU 1 designates air handling unit 1 (e.g. view node object 504 ); Hcl designates preheating coil (e.g. view node object 506 ); Pu designates pump (e.g. view node object 512 ), and Cmd designates command (e.g. view node object 514 ). Similar naming formats are contemplated. For example, AHU 1 .Hcl.Pu.MntSwi may designate: air handling unit 1 /preheating coil/pump/maintenance switch.
- R 1 .HVAC.SuB.Cmd may designate: room control 1 /HVAC/supply air box/command supply air.
- an air handling unit is illustrated herein, other devices are contemplated throughout the embodiments, including but not limited to other objects and functionalities, including but not limited to, lighting, shading, HVAC functions, and combinations thereof.
- FIG. 6 illustrates another hierarchical naming structure 600 of building automation model 602 having a room control with a variable air volume (“VAV”)-system logically linked to one or more field devices.
- View node object 604 representing a room control device
- view node object 606 representing an occupancy sensor
- view node object 608 representing an HVAC device
- view node object 610 representing a supply air box device
- parent of view node object 612 representing field device command supply air object.
- child view node object 612 has an object name comprised of its parent hierarchal tree structure.
- FIG. 7 illustrates another hierarchical naming structure 700 of building automation model 702 wherein view node object 718 represents an air handing unit building automation device.
- a project may require dedicated structured user designations specified by the customer.
- user designations include structured geographical and/or functional information to identify and name view node objects.
- customers may apply a naming schema based on the standards DIN 6779-12 in connection with DIN 6779-1, DIN EN 61346-1 and DIN EN 61346-2, which standardize functional, product-oriented, and geographical designators for technical objects, and documentation in the area of construction and technical building infrastructure.
- name view node objects If user designations are applied to name view node objects, engineering functions will set-up a hierarchical structured name schema and derive the user designations to name those view node objects which require a project-specific user designation.
- the applied namespace of the user designations may either span one building automation device (local namespace) or the complete building automation model (global namespace).
- the view node objects representing the standardized technical view may keep their technical designations.
- user designations may be set up in a late project phase or even by the end customer. Within such a system, however, the assigned object-name will be considered as technical view independent from the user-specified view and the namespace as local.
- building automation model 702 includes a plurality of view node objects 704 - 718 arranged in a hierarchal tree structure.
- Object 712 is named Bld 3 .Floor 2 .Pump which designates: building 3 /floor 2 /pump.
- Other naming schemes are contemplated, such as the name ++46.U1.L16.02-TL001.G01;E01 which may designate: building 46 /floor U 1 /geographical raster L 16 /room 2 /air conditioning plant 001 /supply fan 1 /binary command 1/according to DIN 6779-12, DIN 6779-1, DIN EN 61346-1 and DIN EN 61346-2.
- a similar structure may be formed for other devices, such as the VAV and room control being the parent object.
- FIG. 8 illustrates another hierarchical naming structure 800 of building automation model 802 wherein view node object 804 represents a building, view node object 806 represents an air handling unit, and view node object 808 represents a room control.
- View node objects 810 , 811 representing floor objects, are children of view node object 804 .
- View node object 812 representing a preheating coil, is a child of view node object 806 .
- View node object 814 representing an HVAC device is a child of view node object 808 .
- Each of objects 810 - 814 are logically linked to objects 816 - 828 and their children objects 830 - 832 . As illustrated in FIG.
- the hierarchical defined naming schema of user designations may be mapped during engineering to view node objects to provide a customer-tailored user view as an addition to the standardized technical view.
- a project-specific user view may be independent of the technical view and would enable the user to navigate according to the user designations. Accordingly, as illustrated in FIG. 8 , the user would view a custom-tailored view of an air handling unit with room control with a VAV system.
- Other configurations are contemplated.
- FIG. 9 illustrates a method of inserting and naming building automation objects to form a building automation model 900 as may be implemented by an engineering tool that may be used to configure and commission a building automation model for implementation in building automation devices as illustrated.
- the method starts.
- a parent building automation object is defined, such as a parent view node object and is assigned an object-name, such as one representing a building automation device.
- the object-name of the parent building object is appended to the name of the child building automation object representing a field device to which it is logically linked, forming an object-name of the child.
- the process then returns to block 906 to determine if additional children exist. If no, the process continues to block 912 where it ends.
- FIG. 10 illustrates the partitioning of the object name and possible optional and mandatory inputs for constructing an object name.
- Exemplary naming construct 1000 is expressed in Extended Backus-Naur Form (EBNF) such that brackets ([ ]) illustrate that the item is optional, and curly parenthesis ( ⁇ ⁇ ) indicate one or more (such as in the case of ⁇ character ⁇ expressing a string). As illustrated in FIG.
- EBNF Extended Backus-Naur Form
- Prefix Delimiter 1002 External Structure 1004 , Delimiter 1006 , Prefix Part Name 1008 , Delimiter 1010 , Extension Delimiter 1022 and User Defined Extension 1024 are optional, whereas Object Part Name 1016 is not.
- Prefix Part Name 1008 may comprise the Grandparent-Object-Name 1012 (e.g., the object name of the object's parent's parent thus skipping the name of the object's immediate parent); the Parent-Object-Name 1014 (thus reusing the name of the parent) or no part name at all.
- Object Part Name 1016 may comprise the Alias-Name 1018 (e.g. a user-defined name representing the part) or the Part-Name 1020 if there is no alias name defined.
- an optional Extension Delimiter 1022 and User Defined Extension 1024 may be added (e.g. to represent that the object is one of two or more).
- exemplary naming construct 1000 is defined such that:
- Delimiter character (*dedicated character, not used in names*);
- Parent-Object-Name Object-Name (*parent object is defined by owns-relation*);
- the character utilized as a delimiter is preferably one that is not utilized in any portion of the name.
- the delimiter is a period.
- Other characters are contemplated.
- FIG. 11 illustrates the part field delimiters and part field length rules for constructing an object name.
- Level 1 is the highest level of the object hierarchy, typically representing a building level, but other representations are contemplated.
- Levels 2 through N are intermediate levels, and level N+1 is the bottom most child object.
- Level 1 may represent a building
- level 2 may represent a floor in the building
- level 3 may represent a room (or grid or segment)
- level 4 may represent an application function or device
- level 5 may represent an analog input or output object (or other types, including but not limited to binary input or output, multistate inputs and outputs, value objects, and any combination thereof from a respective field device or subcontroller of a respective field device).
- each level may include a delimiter that is the same or different from any other delimiter.
- the delimiters used optional External Structure construct 1104 may be the same or different from the delimiter used in optional Prefix Delimiter 1102 , which may be the same or different from the delimiter used in optional Prefix Part Name construct 1106 , which may be the same or different from the extension delimiter used in optional User Defined Extension 1110 construct.
- a delimiter separating optional Prefix Part Name construct 1106 from required Object Part Name 1108 may be a period, whereas another delimiter utilized elsewhere may be a $.
- an optional User Defined Construct 1110 may be added (e.g. to represent that the object is one of two or more).
- Naming construct 1100 also includes variable length fields which may be defined by the operator. For example, as illustrated in FIG. 11 , Object Part Name 1108 is illustrated as having a set defined length because the maximum length is equal to the minimum length. However, Prefix Part Name must have a certain minimum length but cannot have a length longer than the maximum length.
- FIG. 12 illustrates a graphical user interface system 1200 of an engineering tool that may be used to configure and commission a building automation model for implementation in building automation devices as illustrated.
- the graphical user interface system or engineering tool 1200 is operatively configured to define and implement naming rules, such as the naming constructs illustrated in FIGS. 10-11 .
- graphical user interface 1200 includes Use Parent Name checkbox 1202 wherein a user can check the box if the user desires the object name to include the name of the parent, thus forming a naming hierarchy.
- User also may input the total name length 1204 of the naming construct.
- User may input what prefix delimiter 1208 is to be used in naming objects.
- User may also input a series of delimiters, minimum length, and maximum length for each level 1208 of the naming construct.
- the system After setting the naming construct criteria, the system automatically applies the naming criteria to a hierarchy of objects, such as that illustrated in FIG. 13 .
- FIG. 13 illustrating graphical user interface system 1300 having naming rules applied.
- Graphical user interface system 1300 includes a table 1302 of objects which includes in columns from left to right, the object type, part name, constructed object name using the method and system illustrated in FIGS. 10-12 , and a user-defined description; other column configurations and types are contemplated.
- the system generated a naming of switch 1 residing in building 1 , floor 1 , room 1 , zone UP 286 , having the part name of 3$Swi1.
- the user may type in the alias name in naming properties box 1306 illustrated in FIG. 13 .
- the user may select another option 1308 , such as reusing the parent, skipping the parent, or adding a new root.
- Other naming constructs and graphical user interfaces are contemplated.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Automation & Control Theory (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Selective Calling Equipment (AREA)
- Air Conditioning Control Device (AREA)
- Stored Programmes (AREA)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2012/069264 WO2013050308A1 (en) | 2011-10-03 | 2012-09-28 | System and method for automatically naming objects in a building automation system |
EP12769085.7A EP2764414B1 (en) | 2011-10-03 | 2012-09-28 | System and method for automatically naming objects in a building automation system |
ES12769085T ES2876010T3 (es) | 2011-10-03 | 2012-09-28 | Sistema y método para dar nomenclatura a objetos automáticamente en un sistema de automatización de edificios |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP11183684.7 | 2011-10-03 | ||
EP11183684 | 2011-10-03 | ||
EP11183684.7A EP2579113B1 (de) | 2011-10-03 | 2011-10-03 | Struktur eines Gebäudeautomationssystems |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130085588A1 US20130085588A1 (en) | 2013-04-04 |
US9400493B2 true US9400493B2 (en) | 2016-07-26 |
Family
ID=44719659
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/432,417 Active 2033-08-20 US9400493B2 (en) | 2011-10-03 | 2012-03-28 | System and method for automatically naming objects in a building automation system |
US13/432,427 Active 2033-12-19 US9625885B2 (en) | 2011-10-03 | 2012-03-28 | Application-generated function block for data exchange between control programs and building automation objects |
US13/573,669 Active 2034-05-25 US9519276B2 (en) | 2011-10-03 | 2012-10-03 | Structure and behavior of a building automation system |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/432,427 Active 2033-12-19 US9625885B2 (en) | 2011-10-03 | 2012-03-28 | Application-generated function block for data exchange between control programs and building automation objects |
US13/573,669 Active 2034-05-25 US9519276B2 (en) | 2011-10-03 | 2012-10-03 | Structure and behavior of a building automation system |
Country Status (5)
Country | Link |
---|---|
US (3) | US9400493B2 (es) |
EP (2) | EP2579113B1 (es) |
CN (1) | CN103034182B (es) |
ES (2) | ES2869875T3 (es) |
WO (2) | WO2013050308A1 (es) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150168000A1 (en) * | 2013-12-17 | 2015-06-18 | Ian Robert Dempster | Systems and methods for using a smart valve to control conditioned air |
US10248089B2 (en) | 2013-12-11 | 2019-04-02 | Siemens Schweiz Ag | Grouping for flexible room arrangements |
US11480935B2 (en) | 2020-10-30 | 2022-10-25 | Siemens Industry, Inc. | System and method for auto-tagging BMS points |
Families Citing this family (78)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110209081A1 (en) * | 2010-02-23 | 2011-08-25 | Honeywell International Inc. | Methods and systems for constructing multi-dimensional data models for distribution networks |
EP2579113B1 (de) | 2011-10-03 | 2021-02-17 | Siemens Schweiz AG | Struktur eines Gebäudeautomationssystems |
US8913058B2 (en) | 2012-01-17 | 2014-12-16 | Honeywell International Inc. | Displaying information associated with an object |
WO2013123675A1 (en) | 2012-02-24 | 2013-08-29 | Honeywell International Inc. | Providing building information modeling data |
WO2013123672A1 (en) | 2012-02-24 | 2013-08-29 | Honeywell International Inc. | Generating an operational user interface for a building management system |
US8862532B2 (en) | 2012-02-28 | 2014-10-14 | Honeywell International Inc. | Displaying information associated with an operation state of a building |
US10146891B2 (en) | 2012-03-30 | 2018-12-04 | Honeywell International Inc. | Extracting data from a 3D geometric model by geometry analysis |
US9525976B2 (en) | 2012-05-10 | 2016-12-20 | Honeywell International Inc. | BIM-aware location based application |
US9142106B2 (en) | 2012-05-23 | 2015-09-22 | Honeywell International, Inc. | Tailgating detection |
US20140022917A1 (en) * | 2012-07-17 | 2014-01-23 | Procter And Gamble, Inc. | Home network of connected consumer devices |
US9305136B2 (en) | 2012-08-02 | 2016-04-05 | Honeywell International Inc. | Determining a layout and wiring estimation for a heating, ventilation, and air conditioning system of a building |
US9070174B2 (en) * | 2012-08-20 | 2015-06-30 | Honeywell International Inc. | Providing a diagnosis of a system of a building |
US9411327B2 (en) | 2012-08-27 | 2016-08-09 | Johnson Controls Technology Company | Systems and methods for classifying data in building automation systems |
US10262460B2 (en) | 2012-11-30 | 2019-04-16 | Honeywell International Inc. | Three dimensional panorama image generation systems and methods |
US9727667B2 (en) | 2013-06-10 | 2017-08-08 | Honeywell International Inc. | Generating a three dimensional building management system |
WO2015127961A1 (en) * | 2014-02-25 | 2015-09-03 | Sca Hygiene Products Ab | Sensor data analysis for a plurality of users |
US20150355609A1 (en) * | 2014-06-06 | 2015-12-10 | Vivint, Inc. | Crowdsourcing automation rules |
US10161833B2 (en) * | 2014-08-25 | 2018-12-25 | Battelle Memorial Institute | Building environment data collection systems |
US10275563B2 (en) * | 2014-09-23 | 2019-04-30 | Crestron Electronics, Inc. | System and method for modeling a lighting control system |
WO2016050279A1 (en) * | 2014-09-30 | 2016-04-07 | Siemens Schweiz Ag | Configuring a common automation system controller |
EP3056953A1 (de) * | 2015-02-11 | 2016-08-17 | Siemens Aktiengesellschaft | Autarkes Feldgerät der Automatisierungstechnik zur Fernüberwachung |
US10534326B2 (en) | 2015-10-21 | 2020-01-14 | Johnson Controls Technology Company | Building automation system with integrated building information model |
US11947785B2 (en) | 2016-01-22 | 2024-04-02 | Johnson Controls Technology Company | Building system with a building graph |
US11268732B2 (en) | 2016-01-22 | 2022-03-08 | Johnson Controls Technology Company | Building energy management system with energy analytics |
WO2017132636A1 (en) | 2016-01-29 | 2017-08-03 | Pointivo, Inc. | Systems and methods for extracting information about objects from scene information |
CN109154802A (zh) | 2016-03-31 | 2019-01-04 | 江森自控科技公司 | 分布式建筑物管理***中的hvac装置注册 |
US10417451B2 (en) | 2017-09-27 | 2019-09-17 | Johnson Controls Technology Company | Building system with smart entity personal identifying information (PII) masking |
US11774920B2 (en) | 2016-05-04 | 2023-10-03 | Johnson Controls Technology Company | Building system with user presentation composition based on building context |
US10505756B2 (en) | 2017-02-10 | 2019-12-10 | Johnson Controls Technology Company | Building management system with space graphs |
US10684033B2 (en) | 2017-01-06 | 2020-06-16 | Johnson Controls Technology Company | HVAC system with automated device pairing |
US11900287B2 (en) | 2017-05-25 | 2024-02-13 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system with budgetary constraints |
US11994833B2 (en) | 2017-02-10 | 2024-05-28 | Johnson Controls Technology Company | Building smart entity system with agent based data ingestion and entity creation using time series data |
US11307538B2 (en) | 2017-02-10 | 2022-04-19 | Johnson Controls Technology Company | Web services platform with cloud-eased feedback control |
US11360447B2 (en) | 2017-02-10 | 2022-06-14 | Johnson Controls Technology Company | Building smart entity system with agent based communication and control |
US10095756B2 (en) | 2017-02-10 | 2018-10-09 | Johnson Controls Technology Company | Building management system with declarative views of timeseries data |
US10515098B2 (en) * | 2017-02-10 | 2019-12-24 | Johnson Controls Technology Company | Building management smart entity creation and maintenance using time series data |
US11764991B2 (en) | 2017-02-10 | 2023-09-19 | Johnson Controls Technology Company | Building management system with identity management |
US20190095518A1 (en) | 2017-09-27 | 2019-03-28 | Johnson Controls Technology Company | Web services for smart entity creation and maintenance using time series data |
WO2018175912A1 (en) | 2017-03-24 | 2018-09-27 | Johnson Controls Technology Company | Building management system with dynamic channel communication |
US11327737B2 (en) | 2017-04-21 | 2022-05-10 | Johnson Controls Tyco IP Holdings LLP | Building management system with cloud management of gateway configurations |
US10788229B2 (en) | 2017-05-10 | 2020-09-29 | Johnson Controls Technology Company | Building management system with a distributed blockchain database |
US11022947B2 (en) | 2017-06-07 | 2021-06-01 | Johnson Controls Technology Company | Building energy optimization system with economic load demand response (ELDR) optimization and ELDR user interfaces |
WO2018232147A1 (en) | 2017-06-15 | 2018-12-20 | Johnson Controls Technology Company | Building management system with artificial intelligence for unified agent based control of building subsystems |
EP3655826B1 (en) | 2017-07-17 | 2024-07-03 | Johnson Controls Tyco IP Holdings LLP | Systems and methods for agent based building simulation for optimal control |
EP3655825B1 (en) | 2017-07-21 | 2023-11-22 | Johnson Controls Tyco IP Holdings LLP | Building management system with dynamic rules with sub-rule reuse and equation driven smart diagnostics |
US20190034066A1 (en) | 2017-07-27 | 2019-01-31 | Johnson Controls Technology Company | Building management system with central plantroom dashboards |
US10962945B2 (en) | 2017-09-27 | 2021-03-30 | Johnson Controls Technology Company | Building management system with integration of data into smart entities |
US11195401B2 (en) | 2017-09-27 | 2021-12-07 | Johnson Controls Tyco IP Holdings LLP | Building risk analysis system with natural language processing for threat ingestion |
CN111279279B (zh) * | 2017-10-26 | 2024-02-20 | 西门子工业软件有限公司 | 建立和跟踪自动化工程环境 |
US10809682B2 (en) | 2017-11-15 | 2020-10-20 | Johnson Controls Technology Company | Building management system with optimized processing of building system data |
US11281169B2 (en) | 2017-11-15 | 2022-03-22 | Johnson Controls Tyco IP Holdings LLP | Building management system with point virtualization for online meters |
US11127235B2 (en) | 2017-11-22 | 2021-09-21 | Johnson Controls Tyco IP Holdings LLP | Building campus with integrated smart environment |
US11954713B2 (en) | 2018-03-13 | 2024-04-09 | Johnson Controls Tyco IP Holdings LLP | Variable refrigerant flow system with electricity consumption apportionment |
CN108664309B (zh) * | 2018-05-16 | 2021-04-06 | 成都天翼空间科技有限公司 | 一种基于Android终端的长数据展示方法及*** |
US11016648B2 (en) | 2018-10-30 | 2021-05-25 | Johnson Controls Technology Company | Systems and methods for entity visualization and management with an entity node editor |
US11927925B2 (en) | 2018-11-19 | 2024-03-12 | Johnson Controls Tyco IP Holdings LLP | Building system with a time correlated reliability data stream |
US11274843B2 (en) * | 2018-12-31 | 2022-03-15 | Johnson Controls Tyco IP Holdings LLP | Systems and methods for providing multi-dimensional load data on a dashboard |
US20200234220A1 (en) | 2019-01-18 | 2020-07-23 | Johnson Controls Technology Company | Smart building automation system with employee productivity features |
US10788798B2 (en) | 2019-01-28 | 2020-09-29 | Johnson Controls Technology Company | Building management system with hybrid edge-cloud processing |
US11362852B2 (en) * | 2019-05-08 | 2022-06-14 | Johnson Controls Tyco IP Holdings LLP | Systems and methods for configuring and operating building equipment using causal and spatial relationships |
US20210149352A1 (en) * | 2019-11-19 | 2021-05-20 | Johnson Controls Technology Company | Building management system with involvement user interface |
US12021650B2 (en) | 2019-12-31 | 2024-06-25 | Tyco Fire & Security Gmbh | Building data platform with event subscriptions |
US11824680B2 (en) | 2019-12-31 | 2023-11-21 | Johnson Controls Tyco IP Holdings LLP | Building data platform with a tenant entitlement model |
US11894944B2 (en) | 2019-12-31 | 2024-02-06 | Johnson Controls Tyco IP Holdings LLP | Building data platform with an enrichment loop |
US11537386B2 (en) | 2020-04-06 | 2022-12-27 | Johnson Controls Tyco IP Holdings LLP | Building system with dynamic configuration of network resources for 5G networks |
US11874809B2 (en) | 2020-06-08 | 2024-01-16 | Johnson Controls Tyco IP Holdings LLP | Building system with naming schema encoding entity type and entity relationships |
US11397773B2 (en) | 2020-09-30 | 2022-07-26 | Johnson Controls Tyco IP Holdings LLP | Building management system with semantic model integration |
US11954154B2 (en) | 2020-09-30 | 2024-04-09 | Johnson Controls Tyco IP Holdings LLP | Building management system with semantic model integration |
US20220138492A1 (en) | 2020-10-30 | 2022-05-05 | Johnson Controls Technology Company | Data preprocessing and refinement tool |
WO2022197964A1 (en) | 2021-03-17 | 2022-09-22 | Johnson Controls Tyco IP Holdings LLP | Systems and methods for determining equipment energy waste |
US11769066B2 (en) | 2021-11-17 | 2023-09-26 | Johnson Controls Tyco IP Holdings LLP | Building data platform with digital twin triggers and actions |
US11899723B2 (en) | 2021-06-22 | 2024-02-13 | Johnson Controls Tyco IP Holdings LLP | Building data platform with context based twin function processing |
US11796974B2 (en) | 2021-11-16 | 2023-10-24 | Johnson Controls Tyco IP Holdings LLP | Building data platform with schema extensibility for properties and tags of a digital twin |
US11934966B2 (en) | 2021-11-17 | 2024-03-19 | Johnson Controls Tyco IP Holdings LLP | Building data platform with digital twin inferences |
US11704311B2 (en) | 2021-11-24 | 2023-07-18 | Johnson Controls Tyco IP Holdings LLP | Building data platform with a distributed digital twin |
US12013673B2 (en) | 2021-11-29 | 2024-06-18 | Tyco Fire & Security Gmbh | Building control system using reinforcement learning |
US11714930B2 (en) | 2021-11-29 | 2023-08-01 | Johnson Controls Tyco IP Holdings LLP | Building data platform with digital twin based inferences and predictions for a graphical building model |
US12013823B2 (en) | 2022-09-08 | 2024-06-18 | Tyco Fire & Security Gmbh | Gateway system that maps points into a graph schema |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050275525A1 (en) * | 2004-03-25 | 2005-12-15 | Siemens Building Technologies, Inc. | Method and apparatus for graphical display of a condition in a building system with a mobile display unit |
US20050289467A1 (en) * | 2004-06-28 | 2005-12-29 | Raphael Imhof | Method and apparatus for representing a building system |
US7308118B1 (en) * | 2003-08-04 | 2007-12-11 | A. Jay Simecek | Building security, occupant safety, and emergency response |
US20090249446A1 (en) * | 2007-10-22 | 2009-10-01 | Paul Thomas Jenkins | Method and system for managing enterprise content |
US20100069035A1 (en) * | 2008-03-14 | 2010-03-18 | Johnson William J | Systema and method for location based exchanges of data facilitating distributed location applications |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6067477A (en) | 1998-01-15 | 2000-05-23 | Eutech Cybernetics Pte Ltd. | Method and apparatus for the creation of personalized supervisory and control data acquisition systems for the management and integration of real-time enterprise-wide applications and systems |
US6571140B1 (en) * | 1998-01-15 | 2003-05-27 | Eutech Cybernetics Pte Ltd. | Service-oriented community agent |
US6028998A (en) * | 1998-04-03 | 2000-02-22 | Johnson Service Company | Application framework for constructing building automation systems |
CA2332009C (en) | 1998-05-15 | 2007-08-07 | Tridium, Inc. | System and methods for object-oriented control of diverse electromechanical systems using a computer network |
US8055387B2 (en) * | 2005-08-22 | 2011-11-08 | Trane International Inc. | Building automation system data management |
US7734572B2 (en) * | 2006-04-04 | 2010-06-08 | Panduit Corp. | Building automation system controller |
US9188969B2 (en) | 2007-05-18 | 2015-11-17 | Siemens Industry, Inc. | Arrangement and method for accessing data of a building automation system component |
US20110071685A1 (en) * | 2009-09-03 | 2011-03-24 | Johnson Controls Technology Company | Creation and use of software defined building objects in building management systems and applications |
US20110087650A1 (en) * | 2009-10-06 | 2011-04-14 | Johnson Controls Technology Company | Creation and use of causal relationship models in building management systems and applications |
US8516016B2 (en) * | 2010-07-07 | 2013-08-20 | Johnson Controls Technology Company | Systems and methods for facilitating communication between a plurality of building automation subsystems |
EP2579113B1 (de) | 2011-10-03 | 2021-02-17 | Siemens Schweiz AG | Struktur eines Gebäudeautomationssystems |
-
2011
- 2011-10-03 EP EP11183684.7A patent/EP2579113B1/de active Active
- 2011-10-03 ES ES11183684T patent/ES2869875T3/es active Active
-
2012
- 2012-03-28 US US13/432,417 patent/US9400493B2/en active Active
- 2012-03-28 US US13/432,427 patent/US9625885B2/en active Active
- 2012-09-28 ES ES12769085T patent/ES2876010T3/es active Active
- 2012-09-28 CN CN201210367992.2A patent/CN103034182B/zh active Active
- 2012-09-28 WO PCT/EP2012/069264 patent/WO2013050308A1/en active Application Filing
- 2012-09-28 EP EP12769085.7A patent/EP2764414B1/en active Active
- 2012-10-01 WO PCT/EP2012/069390 patent/WO2013050333A1/en active Application Filing
- 2012-10-03 US US13/573,669 patent/US9519276B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7308118B1 (en) * | 2003-08-04 | 2007-12-11 | A. Jay Simecek | Building security, occupant safety, and emergency response |
US20050275525A1 (en) * | 2004-03-25 | 2005-12-15 | Siemens Building Technologies, Inc. | Method and apparatus for graphical display of a condition in a building system with a mobile display unit |
US20050289467A1 (en) * | 2004-06-28 | 2005-12-29 | Raphael Imhof | Method and apparatus for representing a building system |
US20090249446A1 (en) * | 2007-10-22 | 2009-10-01 | Paul Thomas Jenkins | Method and system for managing enterprise content |
US20100069035A1 (en) * | 2008-03-14 | 2010-03-18 | Johnson William J | Systema and method for location based exchanges of data facilitating distributed location applications |
Non-Patent Citations (2)
Title |
---|
Extended Backkus-Naur Form, Wikipedia , Redirected from EBNF, http://en.wikipedia.org/wiki/EBNF, Feb. 6, 2012. |
PCT Search Report and Written Opinion dated Jan. 3, 2013 for PCT Application No. PCT/EP2012/069264. |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10248089B2 (en) | 2013-12-11 | 2019-04-02 | Siemens Schweiz Ag | Grouping for flexible room arrangements |
US20150168000A1 (en) * | 2013-12-17 | 2015-06-18 | Ian Robert Dempster | Systems and methods for using a smart valve to control conditioned air |
US10119711B2 (en) * | 2013-12-17 | 2018-11-06 | Optimum Energy Llc | Air handler unit including a smart valve |
US10739021B2 (en) | 2013-12-17 | 2020-08-11 | Belimo Holding Ag | Systems and methods for using a smart valve to control conditioned air |
US11649982B2 (en) | 2013-12-17 | 2023-05-16 | Belimo Holding Ag | Systems and methods for using a smart valve to control conditioned air |
US11480935B2 (en) | 2020-10-30 | 2022-10-25 | Siemens Industry, Inc. | System and method for auto-tagging BMS points |
Also Published As
Publication number | Publication date |
---|---|
EP2579113A1 (de) | 2013-04-10 |
ES2869875T3 (es) | 2021-10-26 |
EP2764414B1 (en) | 2021-03-31 |
US9519276B2 (en) | 2016-12-13 |
US20130085719A1 (en) | 2013-04-04 |
ES2876010T3 (es) | 2021-11-11 |
CN103034182B (zh) | 2016-08-10 |
WO2013050333A1 (en) | 2013-04-11 |
EP2579113B1 (de) | 2021-02-17 |
US20130085610A1 (en) | 2013-04-04 |
EP2764414A1 (en) | 2014-08-13 |
US20130085588A1 (en) | 2013-04-04 |
WO2013050308A1 (en) | 2013-04-11 |
US9625885B2 (en) | 2017-04-18 |
CN103034182A (zh) | 2013-04-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9400493B2 (en) | System and method for automatically naming objects in a building automation system | |
US9658607B2 (en) | System, method and apparatus for grouping building automation objects for group communication within a building automation system | |
US11714390B2 (en) | Systems and methods for creating and using equipment definitions | |
Wang | Intelligent buildings and building automation | |
US20210200171A1 (en) | Systems and methods for presenting multiple bim files in a single interface | |
EP3201701B1 (en) | Configuring a common automation system controller | |
Taneja et al. | Enabling advanced environmental conditioning with a building application stack | |
DK2831680T3 (en) | SYSTEM AND PROCEDURE FOR GROUPING BUILDING AUTOMATION OBJECTS FOR GROUP COMMUNICATION IN A BUILDING AUTOMATION SYSTEM | |
US20060009862A1 (en) | Method and apparatus for accessing a building system model | |
US8782547B2 (en) | Configurable building control system display | |
CN101652978A (zh) | 使用逻辑地址的联网控制*** | |
US11139998B2 (en) | Building management system with dynamic control sequence and plug and play functionality | |
Fütterer et al. | A multifunctional demonstration bench for advanced control research in buildings—Monitoring, control, and interface system | |
Schein | An information model for building automation systems | |
AU2021278105B2 (en) | Cloud-based building management system | |
US20070016331A1 (en) | Method and system for generating combination of applications for building automation system | |
Hayduk et al. | Building management system architecture for large building automation systems | |
US11762379B2 (en) | Automatic fault detection and diagnostics in a building management system | |
Blumstein et al. | Open software-architecture for building monitoring and control | |
Fahmy | Application of Building Management System for Sustainable Buildings: Museums Case Study |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SIEMENS SCHWEIZ AG, SWITZERLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BRUN, GERHARD;MEIER, HERBERT;REEL/FRAME:029781/0347 Effective date: 20120511 Owner name: SIEMENS AKTIENGESELLSCHAFT, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIEMENS SCHWEIZ AG;REEL/FRAME:029781/0825 Effective date: 20130110 |
|
AS | Assignment |
Owner name: SIEMENS SCHWEIZ AG, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIEMENS AKTIENGESELLSCHAFT;REEL/FRAME:036409/0422 Effective date: 20150626 |
|
AS | Assignment |
Owner name: SIEMENS SCHWEIZ AG, SWITZERLAND Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S COUNTRY PREVIOUSLY RECORDED AT REEL: 036409 FRAME: 0422. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:SIEMENS AKTIENGESELLSCHAFT;REEL/FRAME:036508/0322 Effective date: 20150626 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |