Introduction to TAHI IFRS

1. Introduction to TAHIIFRS Alistair Munro, Stephen PattendenTAHI IFRS Team 2010

2. Assumptions – the Market There will continue to be professional systems Procured, designed, installed under commercial terms Operated under service level agreements Public spaces and buildings, factories, offices But most systems will be owned by consumers Focus on purpose and value of the system What it does, not how Changed, moved, upgraded – ad-hoc Expectation that it will not get even more difficult to do this Significant role for external connectivity with service providers This is happening now – smart metering

3. Assumptions – Technical • Applications carrying out any function in any market sector in the home space are made up of “Things” or “objects” which work with one another. • “Things” or objects may comprise equipment, devices, sensors, networks, applications, processes, systems and any entity (tangible, intangible or virtual)* • All of these “Things” or objects require identification, description, must be discoverable and as appropriate, support management & configuration, in order to be used in applications. • The IFRS is written to make these requirements specific for any interoperability to take place *See work from DG INFSO Future Internet Enterprise Cluster on FInERs (Future Internet Enterprise Resources) – in their forthcoming Roadmap.

4. The Technical Issues Products and systems do not work together Even when they implement the same standards Convergence on a single standard is unlikely The most likely candidate is IP but it stops at TCP/UDP ports It takes care of diverse systems below the internetwork layer, but: It does not make products interoperate Some facilitators do exist, e.g. UPnP, but they address only part of the problem Heterogeneity and autonomy will increase There is no uniform collection of device functions The quality/grade of service demanded depends on the application Security, privacy and safety needs are individual Applications must coexist with one another, respecting priority and resolving conflicts according to their users’ needs

5. Interoperability Framework - Requirements What, when and why, not how Howis defined by individual standards The requirements are defined by conformance clauses The conformance clauses are defined within the framework of four groups of function

6. Who Is It For? Installers Understand the technical details Service providers State requirements for product interoperability Consumers Look only at the level of compliance Set expectations Test and certification organisations What to test and how to test it

7. 3 Issues Various systems work successfully in the same environment – they do not share anything Co-existence Two system types adapt to each other’s protocols and share resources for a specific application HBES 2 HBES 1 Interworking Specific Interworking Function Many systems and many applications work together successfully sharing resources Interoperability

8. Interoperability Framework – 7 Levels CONFORMANCE TO IFRS

9. IFRS External Communication • At almost all Levels identified, there will be communication with external systems (in and beyond the WAN). • For the lowest Interoperability Levels particular applications will carry out their own communication using routers, gateways etc. • For higher Levels, the communication will be integrated and shared. • For the IFRS Levels 4-6, there is likely to be communication to management, monitoring and resources in the Internet (eg. The Cloud). • This communication is required at IFRS Level 6. • The IFRS has no recommendation for the means of any communication (but expects IP conformance).

10. Smart Metering System Power Supply (IFRS) INTEROPERABILITY LEVEL 0- separate system(s) – operate in 1 application domain – multiple systems at Level 0 may not co-exist Any Level 0 systems operating in this space are independent of one another Security System Lighting System

11. Smart Metering System Power Supply (IFRS) INTEROPERABILITY LEVEL 0- separate system(s) – have 1 application – multiple systems at Level 0 may not co-exist Security System Lighting System • Stand alone system(s) • Each system uses one HBES technology and runs in a single application domain (Energy management, security, etc..) • Multiple service contracts • Structure and interconnect is fixed • Functions are duplicated and may not work consistently • No interoperability between systems • Multiple controllers and user interfaces • Confidence that separate systems will work provided they co-exist • but co-existence is not guaranteed.

12. Smart Metering System HBES 1 HBES 1 HBES 1 HBES 2 Power Supply (IFRS) INTEROPERABILITY LEVEL 1- operating across one or more application domains (eg a well defined KNX system). Verified coexistence is expected Security System Application domains share information under single HBES Heating System Lighting System

13. Smart Metering System Power Supply (IFRS) INTEROPERABILITY LEVEL 1- operating across multiple application domains (eg a well defined KNX system). Verified coexistence is expected • All application domains use one HBES technology • Structure and interconnect is fixed • Functions are shared and should work consistently • No interoperability between systems – eg not connected to Smart Meter • If Heating System used another HBES it would coexist but not Interoperate Security System Heating System Lighting System • Confidence that the HBES system will work • Co-existence is required.

14. Dedicated Interworking interface between HBES 1 and HBES 2 Dedicated Interworking interface between HBES 2 and HBES 3 (IFRS) INTEROPERABILITY LEVEL 2 - Multiple Level 1 systems that interwork to exchange information and interoperate across specification and application domains verified by the suppliers using conformance specifications agreed by each HBES / specification used Smart Metering System Application domains share information between HBESs using gateway or bridge via specific function Security System Heating System Appliance System Lighting System Application domains share information under single HBES HBES 1 HBES 2 HBES 3 HBES 3 HBES 1 Power Supply

15. Dedicated Interworking interface between HBES 1 and HBES 2 Dedicated Interworking interface between HBES 2 and HBES 3 (IFRS) INTEROPERABILITY LEVEL 2 - Multiple Level 1 systems that interwork to exchange information and interoperate across specification and application domains verified by the suppliers using conformance specifications agreed by each HBES / specification used Smart Metering System Security System Heating System • Application domains using number of HBES types • Specific HBES to HBES Interworking Functions and Bridges connect different pairs of HBES allowing applications to share resources • Functions are shared and should work consistently • All systems have some interoperability Appliance System Lighting System HBES 1 HBES 2 • Confidence that each HBES system will work • Confidence that pairs of HBES will interwork. Possibility that all HBES and their applications will interwork. • Co-existence is required. HBES 3 HBES 3 HBES 1 Power Supply

16. Proprietary mixture of interworking functions, HBES related interoperability functions providing overall interoperability (IFRS) INTEROPERABILITY LEVEL 3 - As Level 2, the interoperability is verified with respect to international standards Smart Metering System Security System Heating System Appliance System Lighting System HBES 1 HBES 2 HBES 3 HBES 3 HBES 1 Power Supply

17. Proprietary mixture of interworking functions, HBES related interoperability functions providing overall interoperability (IFRS) INTEROPERABILITY LEVEL 3 - As Level 2, the interoperability is verified with respect to international standards Smart Metering System Security System Heating System • Proprietary interoperability across number of HBES types • Each installation has to be engineered by highly qualified engineers • Any change will require the attentions of highly qualified engineers • Applications, functions, resources and communications are shared • All systems interoperate Appliance System Lighting System HBES 1 HBES 2 • Confidence that all systems work together • One Installation and maintenance contract • Co-existence is required. HBES 3 HBES 3 HBES 1 Power Supply

18. Levels 0 – 3 • In discussing Interoperability Levels 0 – 3 we have really been covering what is available already. These levels provide a foundation to the IFRS. • there are plenty of Home and Building Electronic Systems, • they can be made to work together by highly skilled installers and practitioners, • they are only reliable if those practitioners can deliver regular maintenance of the systems, • they are inflexible – change requires almost as much effort and cost as the initial system, • in the case of a problem, the responsible party may not be identifiable.

19. Levels 4 – 6 Interoperability • TAHI’s IFRS has been prepared in order to remove the issues of inflexibility and accountability and it sets requirements to ensure that objects (devices, appliances and systems) that conform to Interoperability Levels 4 - 6 interoperate reliably. • There are requirements that ensure any application can: • Discover, identify and find out what something (object, device) does • Configure, operate and manage an object subject to access rights • Flag up security, safety, access and priority of control of an object • Use accepted methods of documentation in order to provide traceability

20. Smart Metering System Interoperability applications conforming to IFRS Power Supply IFRS INTEROPERABILITY LEVEL 4- As Level 3, but conforming to IFRS Security System Heating System Appliance System Lighting System

21. Smart Metering System Interoperability applications conforming to IFRS Power Supply IFRS INTEROPERABILITY LEVEL 4- As Level 3, but conforming to IFRS Security System Heating System Appliance System Lighting System • IFRS Conformant Interoperability across number of HBES types • Standard IFRS tool set for installation, management and operation • Requires engineer with proper IFRS equipment to set up and modify • Standard compliance to IFRS makes management easy • Applications, functions, resources and communications are shared • All systems interoperate • All systems work together – proven by compliance • One contract but competitive due to IFRS standard

22. Smart Metering System Interoperability applications conforming to IFRS Power Supply IFRS INTEROPERABILITY LEVEL 5- As Level 4, but changes of application and devices will be done automatically (effectively plug and play) Security System Heating System Appliance System • IFRS Conformant Interoperability across number of HBES types • Standard IFRS tool set for installation, management and operation • May need engineer with proper IFRS equipment to set up • Most additions to system and changes are managed automatically • Standard compliance to IFRS makes management easy • Applications, functions, resources and communications are shared • All systems interoperate Lighting System • All systems work together – proven by compliance • One contract but competitive due to IFRS standard

23. Smart Metering System Interoperability applications conforming to IFRS Power Supply IFRS INTEROPERABILITY LEVEL 6- As Level 5, with remote management, diagnostics and maintenance Security System Heating System Appliance System • IFRS Conformant Interoperability across number of HBES types • Standard IFRS tool set for installation, management and operation • May need engineer with proper IFRS equipment to set up • Most additions to system and changes are managed automatically • System is remotely monitored and managed • Standard compliance to IFRS makes management easy • Applications, functions, resources and communications are shared • All systems interoperate Lighting System • All systems work together – proven by compliance • One contract but competitive due to IFRS standard

24. So, What Got Better? Greater scope for interconnect Wider choice of standards Interworking of technologies – convergence? Coexistence of applications Possible to use familiar consumer devices Reconfigurable and programmable

25. And What Got Worse? Interoperability failures Coexistence problems But... This happens when there are multiple technologies at every layer Convergence and uniformity helps at lower layers But not for functions outside the communications system

26. Therefore... A framework for interoperability is needed Requirements for complying with it must be clear, especially the technical communications functions They must be presented in a standard form They should be the same for discovery, configuration and management and some aspects of application operation They will be different from application to application, according to purpose

27. How to Comply? The IFRS includes a Conformance Statement Proforma Should be part of every International Standard IICS (Interoperability Implementation Conformance Statement) is in two parts Catalogue of objects and known interoperability successes Layer-by-layer compliance statement, especially for gateways where systems interwork Needs a companion test configuration specification

28. Thank you for your attention – Questions? Alistair Munro, Stephen PattendenTAHI IFRS Team 2010