1. ISO/IEC SC 25 WG 1 Ron Ambrosio Presentation subtitle: 20pt Arial Regular, teal R045 | G182 | B179 Recommended maximum length: 2 lines Confidentiality/date line: 13pt Arial Regular, white Maximum length: 1 line Information separated by vertical strokes, with two spaces on either side Disclaimer information may also be appear in this area. Place flush left, aligned at bottom, 8-10pt Arial Regular, white IBM logo must not be moved, added to, or altered in any way. Indications in green = Live content Indications in white = Edit in master Indications in blue = Locked elements Indications in black = Optional elements Presentation title: 28pt Arial Regular, black Recommended maximum length: 2 lines Group name: 17pt Arial Regular, white Maximum length: 1 line Copyright: 10pt Arial Regular, white Template release: Oct 02 For the latest, go to http://w3.ibm.com/ibm/presentations Interoperability Update Ron Ambrosio Dritan Kaleshi

2. Ron Ambrosio2 Agenda  Scope and Definition of Interoperability  Approaches to Interoperability  Assumptions & Requirements  Product-level Interoperability  Application-level Interoperability  Open Questions

3. Ron Ambrosio3 Scope and Definition of Interoperability  Addresses the requirements of two communities: Product developers System integrators  Product-level interoperability Focuses on syntactic issues – data and protocol interfacing to specific products in a multi-system installation  Application-level interoperability Focuses on semantic issues – describing the application interactions between products in a multi-system installation

4. Ron Ambrosio4 Approaches to Interoperability  Adopt a single system as the agreed-upon universal standard Minimizes ability for product differentiation between manufacturers May not adequately address specific regional differences/requirements OR  Develop system-to-system translations between all target systems Could easily degenerate into an n 2 translation situation Dependence on protocol translation can make the interoperability framework “brittle” – very sensitive to minor changes in underlying systems OR  Define a meta-framework to facilitate multi-system solutions without requiring specific system-to-system protocol translations Address unambiguous data mapping/translation Adopt an approach that is independent of the underlying protocols

5. Ron Ambrosio5 Assumptions & Requirements  Goal is to support multi-system installations Must address product-level interoperability between specific products/systems and the Interoperability Framework Requirement for the interoperability framework to establish unambiguous data translation/mapping Must address application-level interoperability so that multi-system applications can be described Example: support an installation in a home that contains products from a mixture of systems such as KNX and IGRS, or EchoNet and LonTalk, etc. Requirement for the interoperability framework to be protocol- independent

6. Ron Ambrosio6 Product-level Interoperability  Kaleshi will review example(s) of possible data and protocol translation processes in detail

7. Ron Ambrosio7 Application-level Interoperability  Our basic approach is to describe the interaction between products in a multi-system installation  Must capture enough information to enable an implementation of the interoperability framework to automatically determine which product parameters need to be transported across the interoperability event bus as a single unit – i.e., to assemble the event message payloads dynamically This effectively breaks the tight association between individual product APIs and their associated protocol definitions for various product functions

8. Ron Ambrosio8 Application (7) Network (3) Data Link (2) Physical (1) Presentation (6) Session (5) Transport (4) Application Network Data Link Physical La yer M g mt Sys. Mgmt. Interop Application Application Network Data Link Physical La yer M g mt Syst. Mgmt. Interop Application Application Presentation RGIP Application Presentation RGIP RGIB System A connection (CEBus, Konnex, EchoNet, Echelon …) System B connection (CEBus, Konnex, EchoNet, Echelon …) IW Function Interop Residential Gateway Interoperability specification domain Manufacturer-provided interworking Function HomeGate specification domain Interoperability Framework

9. Ron Ambrosio9 IWF-AIWF-B Network A Network B Interoperability Domain Event Bus Object 1-A LightSwtich Object 2-B LightLamp Object 1 event/data logical bus Object 2 Standardized event passing interface for “Interworking functions” Application-level Interoperability

10. Ron Ambrosio10 Interoperability Domain Object 1 Object 2 Application-level Interoperability

11. Ron Ambrosio11 Open Questions  Completion of lexicon  Management (of binding and other processes)  Support and proofs of concept University of Bristol IBM Research Others?

12. ISO/IEC SC 25 WG 1 Ron Ambrosio Presentation subtitle: 20pt Arial Regular, teal R045 | G182 | B179 Recommended maximum length: 2 lines Confidentiality/date line: 13pt Arial Regular, white Maximum length: 1 line Information separated by vertical strokes, with two spaces on either side Disclaimer information may also be appear in this area. Place flush left, aligned at bottom, 8-10pt Arial Regular, white IBM logo must not be moved, added to, or altered in any way. Indications in green = Live content Indications in white = Edit in master Indications in blue = Locked elements Indications in black = Optional elements Presentation title: 28pt Arial Regular, black Recommended maximum length: 2 lines Group name: 17pt Arial Regular, white Maximum length: 1 line Copyright: 10pt Arial Regular, white Template release: Oct 02 For the latest, go to http://w3.ibm.com/ibm/presentations Backup

13. ISO/IEC SC 25 WG 1 Ron Ambrosio Presentation subtitle: 20pt Arial Regular, teal R045 | G182 | B179 Recommended maximum length: 2 lines Confidentiality/date line: 13pt Arial Regular, white Maximum length: 1 line Information separated by vertical strokes, with two spaces on either side Disclaimer information may also be appear in this area. Place flush left, aligned at bottom, 8-10pt Arial Regular, white IBM logo must not be moved, added to, or altered in any way. Indications in green = Live content Indications in white = Edit in master Indications in blue = Locked elements Indications in black = Optional elements Presentation title: 28pt Arial Regular, black Recommended maximum length: 2 lines Group name: 17pt Arial Regular, white Maximum length: 1 line Copyright: 10pt Arial Regular, white Template release: Oct 02 For the latest, go to http://w3.ibm.com/ibm/presentations Interoperability Design

14. Ron Ambrosio14  Software representations of abstract control system objects (control loops, sensors, actuators)  Provide a necessary level of homogeneity across disparate control environments  Allow identification and capture of meta-information (such as latency requirements, data freshness requirements, etc.)  Establish data-typing framework JAVA com.ibm.idacs.algorithm.NullControlAlgorithm PIDTemperatureControl.wsdl Object Schemas

15. Ron Ambrosio15 XML Schema: Data Point, Type and Physical Unit DataPoint AnalogPointDigitalPoint Length Mass SIMultiple OnOff-State Occupancy SIUnit UnitMultiple Time Temperature ElectricCurrent SubstanceAmount LuminousIntensity Motor-Speed RelativeHumidity TranslationalSpeed AngularSpeed ElectricVoltage Frequency Force Pressure Energy EnergyPower HeatCapacity baseTypes.xsd derivedTypes.xsd industryTypes.xsd PhysicalPointLogicalPoint DataVector DataUncertainty... CustomerSat $/BTU

16. Ron Ambrosio16 XML Schema: Control Model Object example

17. Ron Ambrosio17 Programming Framework and Runtime  Establishes the conceptual framework for instantiating and binding together systems of control objects  Performs type- consistency and other types of validation on binding operations  Manages the multinode distributed nature of the system

18. Ron Ambrosio18 Runtime control model object

19. Ron Ambrosio19 Mapping to a distributed environment One example could be a distributed gateway Gateway device A Gateway device B Gateway device C Interoperability Domain