Roll call held and attended list above Note do not have email for all the attendees.
Status update and submission process
MSDO AN Formal Meeting on the 19th April had to be canceled at short notice.
Main open topic for MSDO AN Formal team is we need to discuss how, or if it is possible, to share information on Work in Progress and work plans.
Next Formal meeting scheduled for 21 Jun 2021
The formal SDO representative have asked that the invites for the formal meeting are sent to the SDO as liaisons rather than distributedthrough the AN-SO email list . Reasoning is that the Formal meeting should have Formal representatives.
Ranganai Chaparadza representing IEEE outlined the industry case for identifying and defining common operating Principles.
Proposed exemplar common principle based on addressing two objectives:
Principle for how human interact with AN systems and,
Principles for how AN Systems Federate.
He also proposed how a team could create a proposal on Common Operating Principlse by analysis of the SDO table results and a work program by a few SDO that fed back in to the the Wider group.
theconclusions were that
the SDO Work items tables in SDO Completed and Planned AN Activities Tables might need to be extended to explicitly capture whcih documents address principles for human interaction and AN Systems Federation
IEEE are open to curating the material to create White Paper
These are a classified into three groups as per call on 2021-03-22
AN Introduction ( AN-I)
AN level enhancement (AN-E)
AN Maintenance (AN-M)
It is possible that the SDO Work items tables in SDO Completed and Planned AN Activities Tables might need to be extended to explicitly capture whether they address any or all of these ANs User Story categories
AP Dave MilhamLingli DengKevin McDonnell create an SDO Activity Table page providing further guidance on required inputs from SDO taking account of Common operation principle , and User Story aspects . Focus is on first three columns and creating an example
Review Multi SDO Topic Table
Kevin McDonnell thanked the organizations that have started providing inputs on what topics they would like to share information on.
Plan is to schedule these onto a future meeting agenda.
Outline of plan for joint white Papers
Kevin McDonnellMentioned that a goal at the outset was to identity what white papers we could create among SDOs . The input' collection was the first part of that process.
AP Dave MilhamKevin McDonnell Propose draft Joint white paper structure covering Landscape and roadmap, User Stories, Operational principles and analysis for discussion on next call .
Next steps
AOB
Clash with ZSM can we adjust meeting time?
Dave had been informed that the current call timeclashes with ZSM
In exchange of proposal with Christian Touche ZSM it seems that moving days will be very disruptive, so we propose to remain with current dates and time but there is an option to move forward one hour . Will re-review on the next call.
AP Dave MilhamLingli DengKevin McDonnell create an SDO Activity Table page providing further guidance on required inputs from SDO taking account of Common operation principle , and User Story aspects . Focus is on first three columns and creating an example
AP Dave MilhamKevin McDonnell Propose draft Joint white paper structure covering Landscape and roadmap, User Stories, Operational principles and analysis for discussion on next call
ALL Participants: Each participant: Fill out a sample for specification for their areas of expertise based on public SDO information.
Dave Milham Deng Lingli: Create CSP User Stories based on WP02 presentation.
Dave Milham: Create a page with the SDO activity covering function interface /reference point table based on WP02 table.
All Co-ord by email with subsequent review in meeting
Dave Milham Create a working page for a compendium of architecture diagrams (Noting that team does not think a single diagram will capture all aspects of AN for all stakeholders.)