Interoperability: Advantages, Problems and Solutions

Fakultät Informatik Institut für Angewandte Informatik, Professur Technische Informationssysteme Interoperability: Advantages, Problems and Solutions Prof. Dr.-Ing. habil. Klaus Kabitzsch Dresden, 2018-05-29

Complexity and Economy Folie 2

Complexity in Intelligent Rooms One room many networked components Folie 3

Complexity in Intelligent Buildings One building - many networked rooms Folie 4

Complexity in the Future Internet of things vision much more networked components Folie 5

Complexity in the Future WHO can design it and HOW to design it? Folie 6

Complexity in the Future WHO can design it and HOW to design it? WHO? Computer Scientists? Craftsmen? Customers / Clients? Self-X? HOW? Programming line per line? Composition of Components? Self-X? Folie 7

Complexity in the Future WHO can design it and HOW to design it? Cost Quality WHO? Computer Scientists? Craftsmen? Customers / Clients? Self-X? HOW? Programming line per line? Composition of Components? Self-X? Folie 8

Complexity in the Future WHO can design it and HOW to design it? Cost Quality WHO? Computer Scientists? Craftsmen? Customer / Client? Self-X? Combination of different people: collaborative workflow HOW? Programming line per line? Composition of Components? Self-X? Combination: prefabrication and re-use Folie 9

Prefabrication and Re-Use Folie 10

Prefabrication, Re-Use = Component Assembly Whole buildings and their digital twins (BIM / IFC) Y Pos V_SET Stellantriebsaktor V_STA Pos PAR_CAL Construction IFC ISO 16739 HVAC VDI 3805 ISO 16757 Hardware ecl@ss IEC 61360 / ISO 13584 Software VDI 3813/14/12 {ISO 16484} Prefabricated components: from electronic catalogues Folie 11

Prefabrication, Re-Use = Component Assembly Geometry, Materials Whole buildings and their digital twins (BIM / IFC) Flows, Causalities Y Pos V_SET Stellantriebsaktor V_STA Pos PAR_CAL Construction IFC ISO 16739 HVAC VDI 3805 ISO 16757 Hardware ecl@ss IEC 61360 / ISO 13584 Software VDI 3813/14/12 {ISO 16484} Prefabricated components: from electronic catalogues Folie 12

Prefabrication, Re-Use = Component Assembly designs realised by assembles P S consultant (for client) room concepts (flow schemas) system integrator building system design (and re-use) component design (and prefabrication) re-used by search & comparison of digital twins fabricates described by stored in H vendor component digital twin component catalogue Folie 14

Prefabrication, Re-Use = Component Assembly designs realised by assembles P S consultant (for client) room concepts (flow schemas) system integrator system design (and re-use) component design (and prefabrication) re-used by composition of networked building automation components search & comparison of digital twins fabricates described by stored in H vendor component digital twin component catalogue Folie 15

Prefabrication, Re-Use = Component Assembly composition of networked building automation components Folie 17

Prefabrication, Re-Use = Component Assembly Some good data connections Folie 18

Prefabrication, Re-Use = Component Assembly Missing or insufficient data connectors Needed data flow impossible Needed automation functions impossible Folie 19

Prefabrication, Re-Use = Component Assembly Some good data connections Folie 20

Prefabrication, Re-Use = Component Assembly Missing or insufficient data connectors Needed data flow impossible Needed automation functions impossible Folie 21

Prefabrication, Re-Use = Component Assembly Some good data connections Folie 22

Prefabrication, Re-Use = Component Assembly Missing or insufficient data connectors Needed data flow impossible Needed automation functions impossible Folie 23

Prefabrication, Re-Use = Component Assembly Some good data connections Folie 24

Prefabrication, Re-Use = Component Assembly Missing or insufficient data connectors Needed data flow impossible Needed automation functions impossible Folie 25

Prefabrication, Re-Use = Component Assembly Missing or insufficient data connectors It s like a puzzle! Millions of combinations (exponential complexity) Folie 26

Prefabrication, Re-Use = Component Assembly Missing or insufficient data connectors It s like a puzzle! Millions of combinations (exponential complexity) Needs long time to find a solution Sometimes impossible to find a solution Folie 27

Interoperability Folie 29

Preconditions Interoperability of Components Definition: Two (or more) Components are interoperable, if they are able to work together in defined functions without additional effort for design or adaptation (unless produced by different vendors). bilateral (A - B) or multilateral A B in a defined environment in defined functions Folie 30

Preconditions Hierarchy of Preconditions for Fitness Interchangeable Interoperable Compatible Interconnectable Interworkable non functional plug & play Folie 31

Preconditions - Compatible Preconditions - what must be equal? Compatible Interconnectable Interworkable Interoperable Interchangeable Guarantee by... Dynamic Behavior Lay. 8 Applic. Semantics eq Knowledge Design Lay. 7 Basic Semantics Information Lay. 7 Data Structures Layer 3-6 Data Transformation Layer 1-2 Signal Standardisation Folie 32

Preconditions - Interconnectable Preconditions - what must be equal? Compatible Interconnectable Interworkable Interoperable Interchangeable Guarantee by... Dynamic Behavior Lay. 8 Applic. Semantics eq Knowledge Design Lay. 7 Basic Semantics Information Lay. 7 Data Structures Layer 3-6 Data Transformation Layer 1-2 Signal Standardisation Folie 33

Preconditions - Interconnectable How to guarantee the preconditions? www.auteras.de AUTERAS Layer 1-8 Interoperable by design (discovery, selection, composition) Niagara MBS openhabfairhair Layer 1-7 Interworkable by transformation (middleware) LON BACnet KNX ZigBee Layer 1-6 Interconnectable by standardisation (conformance test & certification) Folie 35

Preconditions - Interconnectable Conformity of Components Definition: A component C is conform to a standard S, if all properties of C are equal to S. This can be evaluated by a comparison with a standard equipment during a conformance test and confirmed by a certificate WHEN A S-Equip. Properties are equal AND B S-Equip. Properties are equal THEN A B Properties are equal A and B are interconnectable Folie 36

Preconditions - Interworkable Preconditions - what must be equal? Compatible Interconnectable Interworkable Interoperable Interchangeable Guarantee by... Dynamic Behavior Lay. 8 Applic. Semantics eq Knowledge Design Lay. 7 Basic Semantics Information Lay. 7 Data Structures Layer 3-6 Data Transformation Layer 1-2 Signal Standardisation Folie 37

Preconditions - Interworkable How to guarantee the preconditions? www.auteras.de AUTERAS Layer 1-8 Interoperable by design (discovery, selection, composition) Niagara MBS openhabfairhair Layer 1-7 Interworkable by transformation (middleware) LON BACnet KNX ZigBee Layer 1-6 Interconnectable by standardisation (conformance test & certification) Folie 39

Preconditions - Interworkable Component A in network 1 Component B in Network 2 Folie 40

Preconditions - Interworkable Component A in network 1 Component B in Network 2 All crossing information arrows between both components are part of the network interface Folie 41

Preconditions - Interworkable temperature In general unsigned long (integer) temperature for HVAC signed long (integer) 2 Byte -274 C... +6279,5 C 0,1 C 0 C 2 Byte -273,17 C... +327,66 C 0,01 C -10 C 100 C -1000 Component A in network 1 2740 10000 Component B in Network 2 All crossing information arrows between both components are part of the network interface? Different data structures on both sides of the interface Folie 42

Preconditions - Interworkable temperature In general unsigned long (integer) temperature for HVAC signed long (integer) 2 Byte -274 C... +6279,5 C 0,1 C 0 C 2 Byte -273,17 C... +327,66 C 0,01 C -10 C 100 C -1000 Component A in network 1 2740 10000 Gateway Component B in Network 2 All crossing information arrows between both components are part of the network interface Transformation of different data structures by the gateway Folie 43

Semantics Folie 45

Preconditions - Interoperable Preconditions - what must be equal? Compatible Interconnectable Interworkable Interoperable Interchangeable Guarantee by... Dynamic Behavior Lay. 8 Applic. Semantics eq Knowledge Design Lay. 7 Basic Semantics Information Lay. 7 Data Structures Layer 3-6 Data Transformation Layer 1-2 Signal Standardisation Folie 46

Same Basic Semantics temperature In general unsigned long (integer) 2 Byte -274 C... +6279,5 C 0,1 C 0 C 2740 Gateway temperature for HVAC signed long (integer) 2 Byte -273,17 C... +327,66 C 0,01 C -10 C 100 C -1000 10000 In the last example this precondition was fulfilled: Same basic semantics (temperature) on both sides transformation by a gateway is possible Folie 47

Different Basic Semantics I el. current [in Ampere] P el. power [in Watt] Gateway In this example the precondition is NOT fulfilled: Different basic semantics (current, power) on both sides transformation by a gateway is impossible Folie 48

Different Basic Sem. But Knowledge I el. current [in Ampere] U el. voltage [in Volt] Gateway application knowledge: P = I * U P el. power [in Watt] In this example the precondition is NOT fulfilled: Different basic semantics (current, power, voltage) on both sides transformation by a gateway is impossible But semantic transformation by application background knowledge is possible Folie 49

Different Basic Sem. & Insufficient Knowledge? P el.power [in Watt] Gateway I el. current [in Ampere] U el. voltage [in Volt] In this example the precondition is NOT fulfilled: Different basic semantics (current, power, voltage) on both sides transformation by a gateway is impossible missing application background knowledge semantic transformation is impossible Folie 50

Same Basic Sem. Different Application Sem. T [ o C] temperature (burner) T [ o C] temperature (outdoor) T [ o C] temperature (boiler) T [ o C] temperature (room) Gateway T [ o C] temperature (return pipe) T [ o C] temperature (chiller) T [ o C] temperature (supply) All information of same basic semantics type (temperature [ o C], But coming from different locations different application semantics transformation by a gateway is impossible Folie 52

Preconditions - Interoperable How to guarantee the preconditions? www.auteras.de AUTERAS Layer 1-8 Interoperable by design (discovery, selection, composition) Niagara MBS openhabfairhair Layer 1-7 Interworkable by transformation (middleware) LON BACnet KNX ZigBee Layer 1-6 Interconnectable by standardisation (conformance test & certification) Folie 54

Semantic Interoperability by Semantic Design Folie 55

Semantic Design Design of abstract application concept schema of semantic information flow Abstract: Neglect implementation (HW, SW, data structures) Neglect deployment into components Neglect platforms (software, network protocols, interfaces) Neglect vendor dependency Folie 56

Semantic Design designs realised by assembles P S consultant (for client) room concepts (flow schemas) system integrator building system design (and re-use) component design (and prefabrication) re-used by search & comparison of digital twins fabricates described by stored in H vendor component digital twin component catalogue Folie 57

Semantic Design designs realised by assembles P S consultant (for client) room concepts (flow schemas) system integrator building system design (and re-use) component design (and prefabrication) semantic standards VDI3813, 3814 re-used by search & comparison of digital twins fabricates described by stored in H vendor component digital twin component catalogue Folie 58

Semantic Design designs realised by assembles P S consultant (for client) room concepts (flow schemas) system integrator building system design (and re-use) component design (and prefabrication) semantic standards VDI3813, 3814 re-used by search & comparison of digital twins fabricates described by stored in H vendor component digital twin component catalogue Folie 59

Semantic Design designs realised by assembles P S consultant (for client) room concepts (flow schemas) system integrator building system design (and re-use) component design (and prefabrication) semantic standards VDI3813, 3814 re-used by search & comparison of digital twins fabricates described by stored in H vendor component digital twin component catalogue Folie 60

Semantic Puzzle designs realised by assembles P S consultant (for client) room concepts (flow schemas) system integrator building system design (and re-use) component design (and prefabrication) semantic standards VDI3813, 3814 re-used by search & comparison of digital twins fabricates described by stored in H vendor component digital twin component catalogue Folie 61

Semantic Puzzle search & comparison of digital twins Folie 62

Semantic Puzzle search & comparison of digital twins Folie 63

Semantic Puzzle search & comparison of digital twins Folie 64

Semantic Puzzle Search & comparison of digital twins in the catalogue: It s like a puzzle! Millions of combinations (exponential complexity) Folie 65

Semantic Puzzle Search & comparison of digital twins in the catalogue: It s like a puzzle! Millions of combinations (exponential complexity) Needs long time to find a solution Sometimes impossible to find a solution Cost Quality Folie 66

Interoperable Re-Use without Semantic Puzzle? Folie 67

Unified Products Yes, we can avoid semantic puzzle, if we use: Only a few concepts Unified products (e.g. from one vendor only) Yes, if we give up variety / diversity: Only a few concepts sufficient? One solution fits all clients? Folie 68

Plug & Play? Folie 71

Plug & Play What must be equal? Compatible Interconnectable Interworkable Interoperable Interchangeable Guarantee by... Dynamic Behavior Lay. 8 Applic. Semantics Lay. 7 Basic Semantics eq Knowledge Information Commissioning Design Lay. 7 Data Structures Layer 3-6 Data Transformation Layer 1-2 Signal Standardisation Folie 72

Plug & Play Dynamic behavior: Parameters for signal filters, parameters for controller tuning, timeout constants, sampling rates etc. Depend on real process, plant, location, environment Defined during installation, commissioning, operation Prefabrication is impossible All parameters (dynamic behavior) get lost during maintenance (component change) So far Plug & Play is impossible (a buzzword only)! Folie 73

Plug & Play What must be equal? Compatible Interconnectable Interworkable Interoperable Interchangeable Guarantee by... Dynamics Behavior Lay. 8 Applic. Semantics Lay. 7 Basic Semantics eq Knowledge Information Commissioning Design Lay. 7 Data Structures Layer 3-6 Data Transformation Layer 1-2 Signal Standardisation Folie 74

Schedule Today Next Presentations Today Folie 75

Schedule Today Now and in the afternoon we have presentations as follows: AUTERAS Layer 1-8 Interoperable by design (discovery, selection, composition) Niagara MBS openhabfairhair Layer 1-7 Interworkable by transformation (middleware) LON BACnet KNX ZigBee Layer 1-6 Interconnectable by standardisation (conformance test & certification) Folie 76

Schedule Today Now and in the afternoon we have presentations as follows: AUTERAS Layer 1-8 Interoperable by design (discovery, selection, composition) Niagara MBS openhab fairhair Layer 1-7 Interworkable by transformation (middleware) LON BACnet KNX ZigBee Layer 1-6 Interconnectable by standardisation (conformance test & certification) Folie 77

Discussion Later Collaboration Platform DesignServiceFlow is open for all interested Partners: http://serviceflow.ga-entwurf.de Whole buildings and their digital twins (BIM / IFC) Y Pos V_SET Stellantriebsaktor V_STA Pos PAR_CAL Construction IFC ISO 16739 HVAC VDI 3805 ISO 16757 Hardware ecl@ss IEC 61360 / ISO 13584 Software VDI 3813/14/12 {ISO 16484} Prefabricated components: from electronic catalogues Folie 78

Questions? E-Mail: Klaus.Kabitzsch@tu-dresden.de www: http://tud.de/inf/tis Collaboration Platform: http://serviceflow.ga-entwurf.de Tool: www.auteras.de Folie 79

Folie 80