Working towards the next version of the SWIM Supporting Material
Working towards the next version of the SWIM Supporting Material
Requirement
Title | Operational needs |
Identifier | SWIM-SERV-011 |
Requirement | A service description shall
|
Rationale | Operational needs relate to the operational context in which the service is used. IERs reference the requirements that are at the origin of the service. This requirement supports decision making in terms of service suitability within a particular operational context. |
Verification | Completeness: Verify that operational needs are included; verify that the indication on whether IERs were used is included. Consistency: If IERs were used, verify that the IERs and the source(s) are included. Correctness: if a source is included, verify that the IERs are available in the referenced source. |
Examples/Notes | Example operational need:
Note: When describing operational needs, it is best practice to add a reference to an operational concept document, or contextual description. Example IERs:
|
Level of Implementation | Mandatory |
Guidance
Examples
See the Operational Needs section within the Donlon TOBT Setting Service Description.
Guidance for JSON service description
tentative JSON Guidance
Guidance for JSON service descriptions v0.0.3d integrated within the SWIM Service Description Handbook v1.0.
Schema
The guidance concerns JSON Schema v0.0.3 (see Schema releases).
Guidance
Within field operationalNeed (itself within field serviceGeneralDescription) list one or more occurrences of type OperationalNeed, such as operational context and requirements that are at the origin of the service
Operational Need - Mandatory
Rationale: Operational needs relate to the operational context in which the service is used. IERs reference the requirements that are at the origin of the service.
This information supports decision making in terms of service suitability within a particular operational context.
Guidance:
- include information about the operational needs fulfilled by the service;
- indicate whether information exchange requirements (IER) were used in the identification of the needs for the service; and if so
- include or refer to the information exchange requirements (IER).
- indicate relationship to PCP and/or SESAR Deployment Plan
attribute name | description | type | guidance | rule |
---|---|---|---|---|
name | The name of the operational requirement. | string | Provide a short name for the operational need | Mandatory |
description | Description of the operational needs fulfilled by the service. Includes or refers to information exchange requirements | string | Guidance:
| Mandatory |
Example
"serviceGeneralDescription": { "operationalNeed": [ { "name": "Operational and Business context", "description": "The context is the Airport Collaborative Decision Making (A-CDM) concept as defined in Airport CDM Implementation Manual v4. In A-CDM it is important to allow A-CDM Partners to set the value of some milestones when necessary. The classical example is to allow the Aircraft Operator or the Ground Handler to set the Target Off-Block Time (TOBT) that indicates what is the target time for the aircraft to be ready for off-block. Setting the TOBT value is possible at many stages during the A-CDM process, as early as Milestone 2 (EOBT-2hr) up to and including Milestone 11 (Boarding starts).\n\r The Business Logic may involve validations such as: not accepting values in the past; not accepting a new value too close the existing one (there is a minimum change involved); Limiting the number of changes after TSAT has been issued." }, { "name": "Information Exchange Requirements", "description": "The service is defined to satisfy two IERs, which were derived from the A-CDM Implementation Manual :\r\n[IER1] To allow the Aircraft Operator or Ground Handler to set, update or delete the value of the Target Off-Block Time of a departing flight. This is done in accordance with the operations involving Target Off-Block Time that take place between A-CDM Milestones 2 and 11 (derived from: Airport CDM Implementation Manual v4)\r\n[IER2] To allow the competent authority to set the value of the Target Off-Block Time for a given aircraft in specific circumstances. In other words, under adverse conditions or special circumstances this service allows the competent authorities to set the Target Off-Block Time value of the flight. (derived from: Airport CDM Implementation Manual v4)." } ], ... }
A complete JSON example is available in page JSON example - Donlon TOBT Setting service description.