BEGIN:VCALENDAR VERSION:2.0 PRODID:IEEE vTools.Events//EN CALSCALE:GREGORIAN BEGIN:VTIMEZONE TZID:Europe/London BEGIN:DAYLIGHT DTSTART:20180325T020000 TZOFFSETFROM:+0000 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 TZNAME:BST END:DAYLIGHT BEGIN:STANDARD DTSTART:20181028T010000 TZOFFSETFROM:+0100 TZOFFSETTO:+0000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 TZNAME:GMT END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTAMP:20180620T195430Z UID:6B8A7804-2201-40A5-B38C-784105A5FF9D DTSTART;TZID=Europe/London:20180727T153000 DTEND;TZID=Europe/London:20180729T153000 DESCRIPTION:A key concern over autonomous systems (AS) is that their operat ion must be transparent to a wide range of stakeholders\, for different re asons. (i) For users\, transparency is important because it builds trust i n the system\, by providing a simple way for the user to understand what t he system is doing and why. If we take a care robot as an example\, transp arency means the user can quickly understand what the robot might do in di fferent circumstances\, or if the robot should do anything unexpected\, th e user should be able to ask the robot 'why did you just do that?'. (ii) F or validation and certification of an AS transparency is important because it exposes the system's processes for scrutiny. (iii) If accidents occur\ , the AS will need to be transparent to an accident investigator\; the int ernal process that led to the accident need to be traceable. Following an accident (iv) lawyers or other expert witnesses\, who may be required to g ive evidence\, require transparency to inform their evidence. And (v) for disruptive technologies\, such as driverless cars\, a certain level of tra nsparency to wider society is needed in order to build public confidence i n the technology. For designers\, the standard will provide a guide for se lf-assessing transparency during development and suggest mechanisms for im proving transparency (for instance the need for secure storage of sensor a nd internal state data\, comparable to a flight data recorder or black box ).\n\nCo-sponsored by: Natasha Alvarado\n\nAgenda: \nAgenda: to follow\n\n Bristol\, England\, United Kingdom LOCATION:Bristol\, England\, United Kingdom ORGANIZER:n.alvarado@ieee.org SEQUENCE:1 SUMMARY:P7001 Test URL;VALUE=URI:https://events.vtools.ieee.org/m/174172 X-ALT-DESC:Description: <br /><p>A key concern over autonomous systems (AS) is that their operation must be transparent to a wide range of stakeholde rs\, for different reasons. (i) For users\, transparency is important beca use it builds trust in the system\, by providing a simple way for the user to understand what the system is doing and why. If we take a care robot a s an example\, transparency means the user can quickly understand what the robot might do in different circumstances\, or if the robot should do any thing unexpected\, the user should be able to ask the robot 'why did you j ust do that?'. (ii) For validation and certification of an AS transparency is important because it exposes the system's processes for scrutiny. (iii ) If accidents occur\, the AS will need to be transparent to an accident i nvestigator\; the internal process that led to the accident need to be tra ceable. Following an accident (iv) lawyers or other expert witnesses\, who may be required to give evidence\, require transparency to inform their e vidence. And (v) for disruptive technologies\, such as driverless cars\, a certain level of transparency to wider society is needed in order to buil d public confidence in the technology. For designers\, the standard will p rovide a guide for self-assessing transparency during development and sugg est mechanisms for improving transparency (for instance the need for secur e storage of sensor and internal state data\, comparable to a flight data recorder or black box).</p><br /><br />Agenda: <br /><p>Agenda: to follow< /p> END:VEVENT END:VCALENDAR