Venue
Coordination: doodle poll by 28/11
Date: 10 Dec 2018 1400-1530
Locationwebex link: Webex meeting https://eurocontrol-conferences.webex.com/join/wvanhamm | 706 775 248 Input documents: if any248
Agenda
| Item | Title | startTime | duration | |
|---|---|---|---|---|
| 1 | Welcome | 14:00 | 10' | |
| 2 | Feedback from F2F meeting | 14:10 | 15' | |
| 3 | Confluence tool | 14:25 | 15' | |
| 4 | Current tasks | 14:40 | 15' | |
| 5 | Introduce Change Request | 14:55 | 15' | |
| 6 | Tasks & Priorities | 6 | Discuss Change Request15:10 | 15' |
| 7 | Next stepsmeetings | 15:25 | 5' | |
| 8 | Any other business | 9 | Close |
Invitation: [SWIM Service Community of Interest] - Project meeting
Agenda ...
Input material
- Sup Mat: initial pages!
- SCOI pages
Do: Needs & FAQ
| 15:30 | - | ||
| 9 | Close | 15:30 | - |
Agenda Items
| Table of Contents | ||
|---|---|---|
|
Welcome
Objectives of this meeting are:
- progress on the handbook (incl feedback F2F, tooling, content)
- discuss start discussing Change Request on the specification
Feedback from 2018-10-03 SSCONE F2F
CoI name
SSCONE SSCONE (SWIM Service Community of Inttererestst).
Structure of the Handbook
Approved. Alignment between SSCONE & SITCOM in 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
Fictitious example common for the 3 SWIM specs: Donlon TOBT Setting exampleDecision 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 ... XML Schema ... (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.
the1) the space on SWIM Supporting Material
spaceSpace dedicated to the Supporting Material for the SWIM foundational specifications.
The space is available to all in read mode (fully public)The space contains the supporting material as approved by the SWIM CoIs. In particular the , such as the SWIM Service Description Handbook v1.0 from SSCONE.
the.
The space is available to all in read mode (fully public).
SWIM CoI members can add review comments.
2) the space on SWIM Community of Interest
spaceSpace dedicated to the SWIM CoI.
The space is internal to the SWIM CoI, available to all SWIM CoIs members in read mode, and to authors in write mode.The space contains working material needed by the SWIM CoI, such as meetings, tasks, or draft supporting material. In particular etc. See for instance the SSCONE - SWIM Service Community of Interest pages.
The space is internal to the SWIM CoI, available to all SWIM CoIs members in read mode, and to authors in write mode.
This page exists in that space.
As a SSCONE member, you should have received a mail inviting to join that space.
ACTION: You need to request access. HOW?Outcome: People generally can access. Note: access requires an OST account.
Managing material underwork
Material underwork should not be accessible to public.
Such material couldwould
- either be stored in the SWIM CoI space nad 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 .
This depends how far practical. Will need be tried.
Currest Tasks
Initial handbook pages
review and confirm
Restrict access to pages where no agreement yet.
the Donlon example
(see as well Info Defn)
More examples from your side?
Priorities
Q: Scott / Dennis: need expressed to discuss compliance (what is our position?)- members).
Depending on practicalities, either option might be used.
Current tasks
| Task | Description | Status | Priority |
|---|---|---|---|
| /wiki/spaces/SCOI/pages/59606295 | Get an initial version of the handbook approved for publication |
| |
| /wiki/spaces/SCOI/pages/59606173 | Review according to a series of viewpoints |
| |
| /wiki/spaces/SCOI/pages/59606068 | Identify topics according needs and requests expressed | Done. | |
| /wiki/spaces/SCOI/pages/59606015 | Analyse 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.
Priorities & Next steps
content
: what to address
meetings
: webex and F2F (and when)
next year any wayTasks & Priorities
source = Consultation ; FAQ - Service descriptions ; /wiki/spaces/SCOI/pages/59606159 ; and needs expressed during meetings
| Task | Description | Status | Priority |
|---|---|---|---|
| individual requirements | requirements for which supporting material is needed | ||
| req xxx | xxx | ||
| general subjects | subjects 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 specs | Make a clear picture of the how the 2 other SWIM specs relate to the SWIM Serv desc spec | ||
| FAQ | Meeting 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 compliance | requires 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.
- Action Former user (Deleted): issue webex invitation
Next F2F
- Around end Mar -beg Apr 2019?
- Back-to-back with SITCOM?
Outcome: back to back; beg Apr.
- Action Former user (Deleted): issue doodle for F2F