please find below: • the link toward the video recording ... · ctm (cooperative traffic...
TRANSCRIPT
The presentation to Externals of the NM21.5 Release via video-conference took place on the 11th of September 2017.
Please find below: • The link toward the video recording of this presentation: https://youtu.be/1HmiJ8BzPI0
• The slides used during the Presentation. • The link toward the NM21.5 Release Notes: http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/nm-release-notes-current.pdf Any questions: [email protected] This document is available for Externals (as a pdf file) at: https://www.eurocontrol.int/lists/publications/network-operations-library?title=&field_term_publication_type_tid=252&year%5bvalue%5d%5byear%5d=
EUROCONTROL – Network Manager Directorate 11/09/2017
v1.2 Classification TLP : White (Public)
Presentation of NM21.5 to Externals
3
Welcome to the Presentation of NM21.5 to Externals
Agenda 1- Introduction and interface set-up 2- NM21.5 Release presentation: 2.1- Important notifications related to NM21.5 migration OPT (operational testing) session 2.2- FBs (Functional Blocks) presentation 3- Way forward toward NM21.5 migration
4
1- Introduction: Recording
Presentation is recorded; recording (audio and slides) will be available on the Eurocontrol public website in a few days: http://www.eurocontrol.int/lists/publications/network-operations-library?type=3317&keyword= (URL available in §1 of the NM Release Notes)
1- Introduction
5
• Goals of the presentation: • Present the new features of the Release NM21.5. • Operational Project Managers will present their Functional Block. • Enable you to assess the impacts on your procedures or systems. • Ask questions (today or by eMail at [email protected]).
• Why doing the presentation now? ⇒ SHOM2 Gate (Software Hand-Over Meeting) is passed. ⇒ System testing and Operational Acceptance testing are still on-
going, so Release content may slightly change until the Release migration.
6
1- Introduction: Webex interface set-up
To be done now: 1- Click on the blue tab in the middle-top of the screen:
2- Click on « Participants »
3- Click on « Chat »
1- Introduction: How to ask questions - by chat
7
1- Type your question in the Chat window 2- Select « Everyone » and click on « Send » 3- The presenter will read the question and reply to it orally 4- If at the end of the answer you still need clarifications, please type them in the Chat window. You can type your question during the presentation
Questions may be asked: By chat (preferred) or orally. At the end of each Functional Block presentation.
How to ask a question by chat:
1- Introduction: How to ask questions – orally
8
2- When the micro icon is grey: you can ask your question; start with your name and company name
3- At the end of the exchange: - Mute your micro (shall be in red) - Click on « Lower hand »
1- Click on « Raise hand » and wait
If for any reason you did not get the floor, click on the micro and speak
0- Go to the participant list
2.1- NM21.5: Important notifications The NM Release Notes
10
• The NM Release Notes contains the latest information on Releases: • OPT (Operational Testing) Session information, OPT guide, etc. • Webex presentation information (including slides and recording) • Release migration plan per system and services • Releases important notifications • Release content in a structured format
• Release Notes are available at: http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/nm-release-notes-current.pdf • To receive information on the Release (including NM Release Notes updates, OPT information, presentations, etc.): subscribe to the mailing (cf. §1 of the NM Release Notes)
2.1- NM21.5: Important notifications (Release Notes §2.1)
11
• Browsers recommended in NM21.5: • Internet Explorer 11 • Firefox 52 ESR (Extended Support Release)
• Windows versions other than Windows 7 are not supported for CHMI. • NM B2B: Decommission of NM B2B NM19.5 webservice.
• NM B2B: CCAMS SSR Codes are no more available via B2B for following specific profiles:
• AO and AO Flight Filing • AIRPORT • GROUND_HANDLING
2.1- NM21.5: The OPT (Operational Testing) (Release Notes §4.1.2)
12
NM21.5 is available for testing with the OPT (operational testing) session!
NM21.5 OPT session started on the 1st of September and will finish on the 13th of
October. With the NM21.5 OPT you will be able to:
Test NM21.5 on your systems with your procedures. Download and test the new NM21.5 CHMI. Test the new NM21.5 NOP Portal. Test some new FBs (operational scenario provided in the OPT guide).
B2B: NM 21.5 will be available on PREOPS (as from 18/09/2017 26/09/2017 14:00 UTC) [Updated after the presentation]
All what you need is to have already access to NM systems. No registration required (unless you want to exchange FPL messages with OPT platform). ⇒ OPT Instructions :
http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/NM-OPT-instructions.pdf
⇒ Questions: [email protected]
2.2- NM21.5 FBs and CRs presentation
14
Only new features impacting operations and Externals are presented
CTM (Cooperative Traffic Management) FB805 Implementation measures coordination
EAIMS (European ATM Information Management Service) FB862 NM Airspace Model Evolutions
FPFDE (Flight Plan and Flight Data Evolution) FB866 Improved restriction model and ATFM processes through use of enhanced flight plan data
Operations Improvements FB864 IFPS Workload Evolutions – continuation FB827 Flight Plan processing across AIRAC cycle FB852 Airspace Data Domain improvements FB853 ATFCM Domain improvements FB895 Cross-Domain activities
FB805: Implementation measures coordination (B2B)
v1.3
Presentation of NM21.5
1- Background
Why this FB is being developed? Enable external access and usage to pre-defined measures stored in NM
systems (Scenario Repository) via B2B What is the main business objective?
To support B2B local-NM coordination and external repository access What is the problem it intends to solve?
Support to SESAR2020 VLD exercises (particularly B2B interface to local tools) in a first step
External access to scenario information via B2B
2- New B2B services: Access Scenario Repository
NM External User
SCN REP
Query attributes of scenario B2B (e.g. FMP Owner EDYY)
Query Scenario Repository List B2B
List of scenarios available in REP
List of scenarios of EDYYFMP
Query measures of scenario B2B (e.g. RR4BRU)
Regulation of RR4BRU (Id, TV description, Start time…) Rerouting of RR4BRU (Id, constraints…)
2- New B2B services: Query applicable scenarios
NM FMP
SCN REP
Query applicable scenarios from Flight List
Query applicable scenarios from TV counts
Flight List (e.g. TV MASBALL)
Counts (e.g. TV MASBALL)
List of scenarios capturing flights from Flight List
List of scenarios applicable to MASBALL • RR4BRU • FL8BRU • FL7BRU
NM
SCN REP
Using existing Flight list B2B service and Counts B2B service
2- New B2B services: Start & Stop simulation and Apply measure (regulation, rerouting)
NM FMP
SCN REP
Request Regulation Proposal via B2B
NM
SCN REP
• Apply Regulation in simulation environment via B2B • Apply Rerouting in simulation environment via B2B
Start simulation via B2B
Retrieve simulation results via B2B
Apply measures via B2B
• Flight list via B2B • Counts via B2B
Using existing service Regulation Proposal via B2B
Using existing Flight list B2B service and Counts B2B service
Perform tactical updates to the simulation via B2B
Feedback Repository NOP
Review Validation
YES YES YES New Format - PUBLISHED
YES NO YES New Format - DRAFT
NO NO NO Old Format - PUBLISHED
2- New in Scenario Management: Automatic Publication in the NOP going OPS
If no FMP feedback received on Reference Scenarios BEFORE ~10th November 2017: • Those scenarios will be
DELETED from the NOP • Corresponding TV will be
DELETED from ENV • Those scenarios CANNOT BE
USED anymore
2- New in Scenario Management: Revalidation process each AIRAC
NM Strategic team
Revalidation report Invalid Scenarios
SCN REP
• Revalidation process triggered on D-10 AIRAC shift
• NM Strategic will contact FMP if invalid Reference Scenarios
• FMP to review the Reference Scenarios and provide feedback (delete, update…)
FMPs
STEP 1
STEP 2
3- Impact of the FB805 on externals
NEW IMPROVEMENTS EXTERNAL IMPACT EXPECTED EXTERNAL ACTIONS
Scenario Repository available via B2B
No impact unless B2B services used
In-house applications to be developed by external users
Automatic publication of Scenarios in the NOP
• Change of publication format in the NOP
• No further use of scenarios for which NM has not received feedback as from 10th November 2017
FMP feedback given before 10th November 2017
Automatic Scenario revalidation process
Communication from NM Strategic Team on invalid scenarios 10 days before AIRAC shift.
Provide feedback on Scenario Updates to NM Strategic. An Operational Instruction will be published to explain the process.
FB862: NM Airspace Model Evolution
v1.1
Presentation of NM21.5
Background
FB862 constitutes the first wave of NM systems adaptations to allow
seamless data download from the EAD and eventually EAIMS All CRs in FB862 are related to the Aerodrome domain The intention is to gradually roll out changes to this and other domains in the
subsequent NM releases
Objectives Internal NM model alignment to AIXM 5.1 Improve data quality by reducing manual manipulations to the published data Part of the NM Strategic Objective No. 2 implementation
No impact on the externals
Except correct AD types will be provided to the externals via NM B2B services (to be confirmed via the Release Notes)
Some world-wide Aerodromes have neither an ICAO Location Indicator, nor an IATA Identifier; in CACD one of them is used as a primary key
Objective Ability to download all world-wide aerodromes from EAD or EAIMS
A unique CACD AD Designator is introduced = ICAO ID if not blank = IATA ID if ICAO ID is blank If both are blank, artificial 4-alphanumeric ID,
which consists of A country code – 1 or 2 characters long An alphanumeric 2 or 3 digits value is used
E.g. EB01 for Belgian AD or K123 for US AD EAD designator – an artificial 3 to 6 alphanumeric
is stored as well for compatibility
CR40552: AD with no ICAO and no IATA ID
CACD allows L, R and C as an indication of the Runway Relative Position AIXM 5.1 model allows all alphabetic characters e.g. T – for tarmac, or
G – for grass Runways
Objectives CACD contains correct values of
Runway Relative Position, as derived from the EAD
Provide correct values via NM B2B services
CR40564: Runway Relative Position
CR41043: Aerodrome type as a separate property
Currently CACD does not distinguish between AD types In CACD heliports are characterised by a unique Runway of type ‘Heli’ AIXM AD type is blank in NM B2B services export AIXM 5.1 model allows the following AD types
Aerodrome (AD) Aerodrome Heliport (AH) Heliport (HP) Landing surface (LS) OTHER
Objectives CACD contains correct AD type values, as
derived from the EAD Provide correct values via NM B2B services Allow depiction of the correct AD map
symbols for the n-CONECT map
FB866: Improved restriction model and ATFM processes through use of enhanced flight plan data (continuation)
v1.3
Presentation of NM21.5
Background
The NM release 21.0 permitted to use CNS (Communication,
Navigation, Surveillance) flight plan information on the flight plan processing.
This advanced service will satisfy ANSP requests that require to
accept and/or accommodate traffic based on local operational needs. NM release 21.5 will permit to use the following information on the
flight plan processing: Flight Status (STS) Code and Registration fields (CODE and REG) Aircraft Operator id (AOOPR/ AOARCID)
32
CR_042606 : Exempt from IFPS restrictions aircraft with a particular status (STS)
CR_042607 : Control via IFPS the presence of REG and CODE CR_042608: Use in IFPS the aircraft operator id
CR_042609 :Use in IFPS the alternate aerodrome (OUT OF SCOPE)
Scope
Use Case In the events of industrial action managed with EU Restrictions,
flights with certain STS values can be automatically exempted from restrictions.
33
2- New features CR_042606 : Exempt from IFPS restrictions
aircraft with a particular status (STS)
ALTRV SAR HEAD ATFMX HOSP HUM STATE
FFR NONRVSM MEDEVAC MARSA FLTCK HAZMAT
Item 18 sub-field STS
Use Cases ICAO EUR Regional Supplementary Procedures (Doc 7030)
provisions. It is mandatory to include the aircraft registration (REG) in FPLs for RVSM approved aircraft (‘w’ in item 10a and presence of REG/ in Item 18).
CODE and REG should be present for flight plans planning crossing the ICAO NAT Region.
Under discussion if they will be requested for all flight plans.
35
2- New features CR_042607 : Control via IFPS the presence of
REG and/or CODE
Use Case Based on aircraft operator requirements NMOC has to restrict
aircraft of certain Aircraft operators from flying to certain locations. Business Rule
AO-id condition based on recognized AO ICAO ID Crosschecked with fields AO OPR/ field of item 18 of the
ICAO flight plan (or equivalent) if present, Otherwise AO ARCID – item 7 of the ICAO flight plan If none
of them is present then the condition fails.
2- New features CR_042608 - Restrictions based on AO Id
Business Value Reduce workload. Reduce human errors. Increase safety in the FP validation. Improve the service NM offers to AOs, ANSPs and
Eurocontrol members.
2- New Features of the FB
System Impact – HMI Include STS, REG & CODE and AO ID in the Condition Tree.
The CHMI, CIFLO, CIAO, CIAM, CIREN interfaces will be
improved to re-structure and enrich the combination possibilities of the conditions defined.
3- Impact of the FB
System Impact – B2B
The change modifies the restriction model and the AIXM data consumed by B2B users will be impacted.
Note that today there are no restrictions defined in the system using the items presented under this change.
The new AIXM format and an draft of the B2B Reference Manual will be made available for external users to adapt their HMI and/or client systems accordingly.
3- Impact of the FB
Manual Updates
The IFPS User Manual will be updated accordingly
3- Impact of the FB
FB864: IFPS Workload Evolutions - continuation FL/RFL flag in hard/soft restrictions when processing flight plan messages.
v1.2
Presentation of NM21.5
1- Background
The RAD has evolved to have Requested Flight Level (RFL) specified in the textual part of the checking, whereas the IFPS software continues to validate using the calculated FL which results in incorrect errors being raised.
IFPS Staff have to manually check the RFL in the flight plan to ensure that the RFL has been set as described in the restriction.
The IFPS system should not be causing these erroneous invalid messages.
2- New features
To stop the IFPS system from presenting erroneous invalid
messages because of the use of RFL in the RAD, the model in NM backend systems will be improved to prevent this.
With this change it will be possible to set the 'FL' or 'RFL' flag in a traffic flow restriction in CACD. IFPS shall use the FL/RFL flag in a restriction when processing flight plan messages.
3- Impact of the FB
Client systems that use the eRAD via NM B2B Web Services
will be impacted by the change to add the FL/RFL flag.
Flight plan messages that were previously incorrectly sent to the IFPS invalid queue for manual processing will now pass IFPS checking automatically.
FB827: Flight Plan processing across AIRAC cycle
v1.1
Presentation of NM21.5
1- Background
Currently the validation of a Flight Plans in NM is done using the AIRAC data with the validity period that contains the EOBT/EOBD of the FPL. In case a FPL has ETOT in AIRAC and ETA in AIRAC + 1 validity periods, the part of the route estimated to be flown in the AIRAC + 1 validity period, is being wrongly validated with the previous AIRAC data.
As a consequence NM wrongly rejects valid flight plans to Airlines and distributes to ATC flight plans that do not meet restrictions on the new AIRAC.
2- New features
In IFPS and IFPUV, Flight Plans flying across change of
AIRAC cycles will be validated with the AIRAC whose validity period contains the EOBT/EOBD (referred to as AIRAC) and with the AIRAC whose validity period contains the ETA (the subsequent AIRAC, referred to as AIRAC +1).
During the validation with the AIRAC + 1 only the Restriction and Route availability errors will be reported.
3- Impact of the FB
The core IFPS processing of flight plan message will be
changed.
IFPS will correctly report the errors associated to the availability of airspaces/routes.
Airspace Users may see flight plan messages being rejected for errors found in two sets of AIRAC data.
FB852: Airspace Data domain improvements
v1.1
Presentation of NM21.5
1- Background
Short background of the FB: Improvement of the level dependency/multiple dependent applicability. For Restrictions with Dependent Applicability set to CDR(s) or RSA(s), the DA should be
considered valid even if traffic is not crossing the CDRs or RSAs used in the DA. In other words, for the purpose of reducing complexities in traffic management, RSA activation or CDR availability/unavailability should be able to re-route traffic not crossing the concerned entities.
Routes can actually be defined as nearby. But (E/E) Pts and the subsequent DCT Even if
the ANSP has implemented FUA concept there is a limitation of what can be restricted during/outside activation of Military areas, especially in FRA environments.
For objects other than route segments, OPS can say “ even if the flight profile is not
crossing the RSA, this is not available when the area is active “. And they will also be able to say “by the way, it is closed for the same level band as the RSA (s) “.
3- Impact of the FB
A restriction that have a FL dependent applicability can inherit
the FL band applicability from the referenced area or point,
FB853: ATFCM Domain Improvements
v1.2
Presentation of NM21.5
1. CR_036503 – Forbid to the user the application of XCD/FCM/RVR regulation
2. CR_042414 – ETFMS Improvements for regulation proposals
FB853 ATFCM Domain Improvements
1.1- Background CR_036503 – Forbid to the user the application of
XCD/FCM/RVR regulation ATFCM Operations Manual, section 7. Procedures in unusual circumstances
(Low visibility) When applying a Regulation with XCD/RVR value (Exceptional
Conditions/Runway Visual Range), the FCM (Flight Confirmation Message) shall not be selected.
Why? Selecting XCD/RVR triggers a FLS (Flight Suspension) if RVR is unknown
To de-suspend, AO sends FCM with sufficient RVR value Selecting FCM triggers a FLS until flight is confirmed for the Regulation
To de-suspend, AO sends FCM with confirmation REGUL Selecting combined XCD/RVR/FCM
To de-suspend, AO would need to send FCM with sufficient RVR AND confirmation REGUL
Operational problems in the past Regulation applied with XCD/RVR & FCM at the same time Suspended AOs with “unknown RVR” tried to de-suspend with FCM including the RVR
information but not the confirmation for the Regulation -> they remained suspended.
1.2 & 1.3 - New features & Impact CR_036503 – Forbid to the user the application of
XCD/FCM/RVR regulation Change: Implement system support to prevent application of XCD/FCM/RVR
Regulation In NOP Portal/B2B – not possible to select/submit a Regulation with XCD/RVR &
FCM selected at the same time Impact:
The change will ensure that operational problems resulting from application of XCD/RVR/FCM Regulation are avoided
2.1- Background CR_042414 – ETFMS Improvements for regulation proposals
Context: To optimize the Regulation via B2B service
1. Improve ETFMS processing of MCP Regulation proposals
2. Harmonize MCDM (Measure Collaborative Decision Making) approval state
3. Automatically adapt MCP Regulation proposal period
2.2 & 2.3 - New features & Impact CR_042414 – ETFMS Improvements for regulation proposals 1. Improve ETFMS processing of MCP Regulation proposals
When MCP Regulation proposal removes a flight from the list of cherry picked flights -> flight is still forced with a zero delay
Flight cannot be recalculated unless manually unforced Change
Flight will be unforced automatically -> Flight re-calculations are thus enabled 2. Harmonize MCDM (Measure Collaborative Decision Making) approval state
Change MCDM Approval state “Stand-by” (actor is reviewing the measure request) will be
renamed “Acknowledged” 3. Automatically Adapt MCP Regulation period
ATFCM Operations Manual – MCP Regulation period derived from the ETO/CTO of the cherry picked flights When a MCP Regulation proposal modifies existing MCP Regulation, the MCP
Regulation period needs to be adapted via B2B Change
When a flight with ETO outside of the MCP Regulation period is added by a MCP Regulation proposal, the MCP Regulation period will be automatically adapted
FB895: Cross-Domains activities ATFCM improvements
v2.0
Presentation of NM21.5
1- Background
FB895 provides operational improvements to the NM systems and intends to enhance the information shared:
Provision of information to external stakeholders regarding CDM departing
traffic.
Display accurate information on the delay to external stakeholders regarding the original source of ATFM delays when protected locations are used.
2- New features
CR_042339 Allow to differentiate traffic departing from CDM airports
The change will permit to differentiate CDM traffic in the CHMI.
The following traffic will be shown: Traffic departing from CDM airports that are either sequenced (T-DPI-s) or off-
blocks (A-DPI). Traffic departing from advanced ATC towers that are off-blocks (A-DPI).
This information will be made available as part of the flow services via NM
B2B.
2- New features
CR_042339 Allow to differentiate traffic departing from CDM airports
It follows the same logic used for the delay threshold mechanism in NM 21.0.
The information will appear automatically as long as flights are present in the traffic volume.
2- New features
CR_042526 - Help to identify the operational origin of the delay and the congested area when a traffic volume with a protected location is regulated
Certain traffic volumes with reference locations based on airspaces are
designed for airfield restriction purposes. In this case, the airfield for which the traffic volume is built is called protected location.
Currently, When such a traffic volume is regulated, the NM systems display its reference location as the congested area.
With NM 21.5, the NM systems will display the protected location (the aerodrome) as the congested location when a TFV with a protected location is subject to an ATFM measure.
3- Impact of the FB
The changes should assist the NM stakeholders to better discriminate the information made available: FMPs will be able to decide on ATFM measures knowing the amount of CDM
traffic in their traffic volumes. Users will be able to accurately see which are the congested areas.
No impact on current procedures.
The NM interfaces will be impacted:
Showing CDM traffic in CHMI, CIFLO, CIAO, CIAM, CIREN, ETFMS. Showing the protected location in the NOP Portal and CHMI when such a
traffic volume is regulated.
NM21.5: Way forward
Presentation of NM21.5
Way forward to NM21.5 migration
NM21.5 is available for testing with the OPT (operational testing) session!
NM21.5 OPT session started on the 1st of September and will finish on the 13th of
October. With the NM21.5 OPT you will be able to:
Test NM21.5 on your systems with your procedures. Download and test the new NM21.5 CHMI. Test the new NM21.5 NOP Portal. Test some new FBs (operational scenario provided in the OPT guide).
B2B: NM 21.5 will be available on PREOPS (as from 18/09/2017 26/09/2017 14:00 UTC) [Updated after the presentation]
All what you need is to have already access to NM systems. No registration required (unless you want to exchange FPL messages with OPT platform). ⇒ OPT Instructions :
http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/release-deployment/NM-OPT-instructions.pdf
⇒ Questions: [email protected]
Way forward to NM21.5 migration
75
NM21.5 migration is planned to start on the 17/10/2017 (last around 1 week) Detailed Release migration plan may be found in the NM Release Notes (§4.2.3). As for any release, the date of migration is subject to the output from final technical
and operational testing.
To receive information on the Release (including NM Release Notes updates, OPT information, presentations, etc.): subscribe to the mailing (cf. §1 of the NM Release Notes)
Any question related to the Release: [email protected]
