1. First SEG AAL Meeting, Brussels 11 th to 12 th 20.05.2014, Janina Laurila-Dürsch (DKE) 1/10

2. IEC System Evaluation Group 5 “AAL” (SG 5) on IEC level SEG held its first meeting on 2014-03-10 to 12 in Brussels Participants from CN, BE, DE, JP, KR, NL, NZ, UK, US The next meeting of the SEG (or the committee succeeding the SEG) is planned on 2014-09-08 to 09, in Bucharest, Romania (in conjunction with AAL-Forum) 2/10

3. SEG AAL Meeting 11 th to 12 th (1)  IEEE presentation on Ethernet standards Series 802 and AAL  Continua Health Alliance presentation on the latest developments  Continua Health Alliance has expressed their interest in working with IEC on the standardization of their interoperability guidelines and IEC SEG AAL would like to progress on this topic before the final set-up of the IEC System Committee for AAL  (Supplement: there was a Meeting between Continua and IEC SEG AAL on May the 9 th in Berlin)  IEC SEG AAL recommends to establish the liaison with the Continua Health Alliance. Both organizations could profit from the liaison and cooperation.  IEC SEG AAL recommends that the IEC CO, IEC TC 62 and IEC TC 100 are involved in the discussions of where appropriate work should be progressed at the initial stage. 3/10

4. SEG AAL Meeting 11 th to 12 th (2)  The final report was reviewed: each sub-group reported to SG5 so the final report was completed and finally approved  The reports from the Modeling Team and the Security Team were already reviewed during the October 2013 SG5 meeting. The Status Team report was now ready and could also be reviewed during the March meeting by the SG5- AAL Members  Furthermore during the meeting a workshop session has been organized to deal with the specific issues of the recommendations to submit for the future SYC scope, structure, and Chairman profile  The final version of the report has been drafted and circulated to the SEG members and was reviewed during a webmeeting on the 28 th of April. After this it will be submitted to SMB for approval 4/10

5. The work done to forward interoperability The Status Team found out, which standards are already existing, which IEC TCs are working on AAL and which stakeholders need to be involved in the future. This team also collected a list of terms and definitions. The Modeling team was inspired by the work of SG3 and former SG1 to develop a tool to map use cases to indentify gaps in standardization. They invented a template together with the TC100 and collected use cases to proof the functionality of the tool. The Data Security Team reviewed the different regulations in regards to data security/privacy and assessed the needs of AAL products in regards of reliability and safety. Safety and reliability is a well known playground for IEC, but data security is something that needs to be treated special. 5/10

6. © 2011 DIN e. V. No interoperability – many barriers 6/10

7. Conclusion 7/10  Interoperability is a key requirement for the success of AAL solutions on the market  The AAL systems include a whole chain of products, services and required infrastructure  Especially the responsibility for the complete chain has to be established  The need for a better approach to AAL standardization to ensure the interoperability of devices and systems

8. Thank you! Any questions? DKE German Commission for Electrical, Electronic & Information Technologies of DIN and VDE Contact: Janina Laurila-Dürsch Division 8 Phone: +49 69 6308 378 janina.laurila-duersch@vde.com 8/10

9.  The Status Team created a list of standards and noted the TCs in- and outside of IEC and the fora and consortia to be involved in the future work  Furthermore essential fora outside of IEC indicated their intention to transfer their standards to IEC to be adopted as international standards  A recommendation of SG 5 will be to establish a group to coordinate the work in and outside of IEC and to be the single point of contact for the AAL- market The Status Team – in detail 9/17

10.  The Modeling Team in SG 5 developed a template, collected use-cases and evolved a Use Case model  The Use Case Model structures a Use Case Example in different Planes. It analyzes the Use Case with respect to functionality and interoperability of the components in different Planes. Furthermore the Use Case Model provides an insight in required standards, specifications and TC/SC  The Plane presents the relation between domains and the enabler. One Plane includes:  Domain: Single domains of a complex AAL-system.  Enabler (elementary / abstract enabling functions ): Elementary / abstract enabling functions are the basis of any AAL-system.  This Use Case Model should not define any Model of some Reference architecture but maps the standards of the functionality of products and their interfaces The Modeling Team – in detail 10/17

11. a) Daily life support Denotes all techniques and systems which help and support the user during the daily life (like a managing system, a calendar or reminder or other support systems). b) Safety, security and privacy at home Denotes all technical support including fall detection and prevention, ambient sensors or actuators, alarm systems and localization. c)Healthcare and wellness Encompasses medicine compliance as well as telemonitoring (system) aspects and teleconsultation as well as prevention and motivation aspects. d) Active aging Denotes all topics concerning the agile and active aging e.g. learning, the work environment and processes, exercises and information needed for an active aging. e) Mobility Encompasses all systems which are useful for mobile processes e.g. mobility aid, safety and security on the move, transport or information of outdoor conditions. f) Social interaction Denotes all systems for social connections and networking as well as the possibility for knowledge transfer. List of categories 11/17

12. ii) a) i) iv) c) d) e) f) g) h) i) b) iii) v) Domain Enabler interfaces and format The Use Case Model – The Framework 12/17 Information Layer Component Layer System A System B Semantic Layer Communication Layer

13. The domains - x-Axis encompasses 5 domains: Global (Example: in a train, at the country side, on a ship, in a park, on the street.) Public buildings (Example: At an airport, in a shopping centre, in the city hall, in a metro station.) Personal vehicle (Example: cars, motor cycles, cycles or vehicles designed for elderly people, whether hand- operated (stability aids) or engine powered (electrical bicycles and scooters).) Home (Example: Includes infrastructure and devices (including mainstream solutions) such as home wireless networks, routers, gateways and concentrators, audio-video aids (microphones, cameras, screens, speakers, head sets, headphones, etc.), in-house only vehicles and walking / moving aids, in-house only appliances and robots, connected TVs, monitoring and security means, medical aids (e.g. blood pressure devices).) Body and Personal (Aura) (Example: tablet, smartphone, step counter, blood pressure sensor, personal alarm button.) The Use Case Model – the domain 13/17

14. The Enabler - y-Axis encompasses 9 functions: a) Interaction with humans (Monitoring) (Denotes all direct interaction of or through AAL system elements with humans ) b) Social Participation ( Denotes all audio-visual interaction and personal care.) … f) Data aggregation and storage (Denotes all content-agnostic data handling.) g) Defined function control and support (Denotes all digital and physical activity in immediate support of any given single AAL function.) … i) Integral service programs (Denotes all overall level coordination necessary to perform composed groups of services over longer time spans in a meaningful manner.) The Use Case Model – the enabling functions 14/17

15.  The Security Team reflected different international views on the aspects of data security, safety and reliability and found out that the view of privacy differs from region to region.  Cyber security and privacy are issues which need to be closely analyzed. Collaboration with ISO is required (ISO/IEC 27032:2012).  A recommendation is to call for a guide to advice committees how to deal with private data as well as data security so that every IEC TC can handle the private data with the same care. The Security Team – in detail 15/17