Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Venue

  •  Coordination: doodle link

Date: nn Dec 2018

Timing: < 2 hours

Location: Webex meeting Webex LINK

Documentation: if any

 10 Dec 2018  1400-1530

webex link: https://eurocontrol-conferences.webex.com/join/wvanhamm   |  706 775 248     

Agenda

Item

Title

Time
startduration
1Welcome14:0010'
2
feedback
Feedback from F2F meeting14:1015'
3Confluence tool14:2515'
4
Initial handbook pages
Current tasks14:4015'
5
Discuss 8Close
Introduce Change Request14:5515'
6Tasks & Priorities15:1015'
7Next meetings15:255'
8Any other business
7Next steps
15:30-
9Close15:30-

Agenda Items

Table of Contents
maxLevel2

 


Welcome

Objectives of this meeting are:

Review the materials after first month of being “live”
  • Look at next set of work to be done
  • Feedback from F2F meeting

    Summarising what was discussed and decided

    CoI name

    ...

    example

    ..
    • progress on the handbook (incl feedback F2F, tooling, content)
    • start discussing Change Request on the specification

    Feedback from 2018-10-03 SSCONE F2F

    CoI name 

    SSCONE (SWIM Service Community of Interest).

    Structure of the Handbook

    The structure is approved. Seeking further alignment between SWIM Service Description Handbook v1.0 and SWIM Information Definition Handbook v1.0 in style and structure.

    Example

    Decision to use a common fictitious example (Donlon TOBT Setting example) for the supporting material of the 3 SWIM specifications.

    Material from SWIM Governance Implementation Project

    Sharing of material developed in the context of that project. As restrictions apply, the XML Schema is sent to those requesting it.

    Airspace Management (ASM) system perspective

    The presentation from Dominique Guillerm on the move to SOA for the Airspace Management systems generated much interest.

    Roles

    Currently, members prefer bringing ideas and reviewing, rather than authoring.

    Confluence tool

    The SWIM instance of the Confluence tool is not fully working. It contains 2 spaces for our use.

    the 

    1) the space on SWIM Supporting Material

     space

     

    Space dedicated to the Supporting Material to for the SWIM foundational specifications.

    The space contains the supporting material as approved by the SWIM CoIs, such as the SWIM Service Description Handbook v1.0 from SSCONE.

    The space is available to all in read mode (fully public)The space contains the supporting material as approved by the SWIM CoIs

    SWIM CoI members can add review comments.

    2) the space on SWIM Community of Interest 

    Space dedicated to the SWIM CoI.

    The space contains in particular the SWIM Service Description Handbook as approved by the SSCONE.

    the SWIM Community of Interest space

    Space dedicated to the SWIM CoIsworking material needed by the SWIM CoI, such as meetings, tasks, etc. See for instance the SSCONE - SWIM Service Community of Interest pages.

    The space is internal to the SWIM CoIsCoI, available to all SWIM CoIs members in read mode, and to authors in write mode.

    The space contains working material needed by the CoI, such as meetings, tasks, or draft supporting material.

    The space contains in particular the SSCONE - SWIM Service Description Community of Interest pages.

    ACTION: You need to request access. HOW?

    Initial handbook pages 

    review and confirm

    main page
    the structure
    the context page
    Donlon example (see as well Info Defn)This page exists in that space.

    As a SSCONE member, you should have received a mail inviting to join that space.

    Outcome: People generally can access. Note: access requires an OST account.

    Managing material underwork

    Material underwork should not be accessible to public.

    Such material would

    • either be stored in the SWIM CoI space and be moved to SWIM Supporting Material when ready for publication
    • or be stored in the SWIM Supporting Material space, with specific naming and access restricted to the SWIM CoI members).

    Depending on practicalities, either option might be used.

    Current tasks 

    TaskDescriptionStatusPriority
    /wiki/spaces/SCOI/pages/59606295Get an initial version of the handbook approved for publication
    •  Action (all): provide review comments by 5/3/19

    /wiki/spaces/SCOI/pages/59606173Review according to a series of viewpoints
    •  Action (all): provide review comments by 5/3/19

    /wiki/spaces/SCOI/pages/59606068Identify topics according needs and requests expressedDone.
    /wiki/spaces/SCOI/pages/59606015Analyse and provide advice on approach for handling the CR

    Note: To be closed by next F2F.


    The status of active tasks is maintained in SSCONE Tasks.

    Discuss Change Request

    Consulting the CoI in how to best handle the CR 168/1.

    See /wiki/spaces/SCOI/pages/59606015.

    Tasks & Priorities

    Next steps

    content

    : what to address

    meetings

    : webex and F2F (and when)source = Consultation ; FAQ - Service descriptions ; /wiki/spaces/SCOI/pages/59606159 ; and needs expressed during meetings


    TaskDescriptionStatusPriority
    individual requirementsrequirements for which supporting material is needed

    req xxxxxx





    general subjectssubjects not related to an individual

    Conformance assessment


    Helping assessing conformance to the spec. See Conformance assessment report and /wiki/spaces/SCOI/pages/59605260

    What is actually needed and why? How is conformance assessed?

    Meeting comment: Explain conformance, verification, compliance. (could / should be sharable with SITCOM and SWIM-TEC). If different, explain why


    yes
    Clarify links with other SWIM specsMake a clear picture of the how the 2 other SWIM specs relate to the SWIM Serv desc spec

    FAQMeeting comment: valuable source
    yes




    Outdside spec's scope


    Basic steps for new services

    checklist with all steps for new services

    This could be based on the following grouping of activities: Service Identification, Service Design, Service Implementation, and Service Deployment.

    Meeting comment: Interesting. Give confidence feeling.


    yes

    Describing non-implemented services

    This has alsready been started in -non-implemented service

    Harmonising service design

    Possible re-use of output from SESAR 1. See eg /wiki/spaces/BOK/pages/59409240, /wiki/spaces/BOK/pages/59408902



    SWIM compliancerequires coordination with SWIM Governance Implementation Project

    The status of potential tasks is maintained in SSCONE Tasks.

    Outcome: See expressed interest in priority column.

    Next meetings

    Options for Webexes

    • fixed agenda (see for instance the example of SITCOM, with a webex every 6 weeks) vs 
    • ad hoc with doodle

    Outcome: fixed schedule, on Monday 1400-1530 every 6 weeks.

    Next F2F

    • Around end Mar -beg Apr 2019? 
    • Back-to-back with SITCOM? 

    Outcome: back to back; beg Apr.

    Any other business


    Close meeting