Frequently Asked Questions (FAQ) on network operations

Can IFPUV provide route proposals?

Yes. For secure-access Users, a Propose Routes tool is available to find an IFPS compliant route. The tool delivers the best possible IFPS compliant routes taking into consideration some user defined constraints (e.g. via a point or airspace, avoiding a point or airspace).
To request secure-access to NOP portal or CIAO, in order to access the proposed routes and what-if functionalities, submit a NM Service Request 

Please note that the routes that are proposed by the Propose Routes are not to be considered as Network Operations recommended routes. The responsibility to ensure operational acceptance of the proposed routes before filing to IFPS is with the flight plan originator.

How can I get assistance for the errors raised on my IFPUV-validated FPL?

The IFPUV is an automated system. Unlike the IFPS operational system, there is no manual processing of FPLs validated on IFPUV.  Information relating to the errors being raised can be found in the IFPS Users Manual and the Annex to the IFPS Users Manual (Generated Errors).   Updated or temporary procedures are also published on the Flight Planning section of the Network Operations Portal (NOP) under ‘Flight Planning Documentation’

Depending on the error raised, you should also consult the following information available via the Network Operations Portal (NOP):

  • RAD Document
  • AUP/UUP
  • AIM
  • Network Headline News
  • Calendar of Events

There may be cases where a FPL is rejected by the IFPUV, but would be accepted by IFPS with manual intervention by IFPS Operators.

If you have any doubt about the correctness of the error raised, the relevant IFPS Unit can provide assistance. For further information on Network Operations Flight Planning Assistance, please refer to the Contacts & Support link on the Flight Planning section of Network Operations Portal (NOP).

How can I receive messaging/addressing on specific AFTN or SITA addresses ?

Only Aircraft operators can apply for messaging/addressing services via the web form

How can I update ENV data?

Please consult the Network Operations library and fill in the appropriate form

How do I access IFPUV?

Flight plan originators wishing to validate FPLs with the IFPUV, prior to their submission to the operational IFPS, may submit them:

  • via the NOP Portal (accessible via the NM Public website), and then selecting Flight Planning portlet in the Tactical or PreTactical phases
  • to the AFTN address EUCHZMFV or SITA address BRUEY7X
  • via B2B. Information is available in the Network Management B2B Services Leaflet contained in the online library
How to raise operational enquiries?

Users requiring immediate operational support should contact directly our operations staff via the E-helpdesk or via phone as mentioned in our Contacts page.

How to report on operational problems?

Users are invited to report on NM suspected problems which consequently had an impact on the provision of ATM (such as erroneous messages from ETFMS) or in an operational process (such as treatment of Flight Plans or allocation of slots).

  • If you have a token, the primary media for reporting an operational problem to the Network Manager Operations Centre is via the CCMS application (Central Claim Management System).
  • In case you cannot access CCMS, access can be requested via a Service Request Form.   A back-up solution for raising operational problems is to send us this NM Operational Problem Report (MS Word format) form via e-mail.

 

How will I receive a response from the system when I submit a FPL to IFPUV via NOP, AFTN or SITA?

On the IFPUV via the NOP, the result of the FPL validation appears at the bottom of the page in the validation results window either by showing the list of errors raised on the FPL or the text 'no errors'. It is possible to modify and re-validate the FPL as needed.

Via AFTN or SITA, the IFPUV system will send a Reply message in the form of an ACK (Acknowledgement) message which indicates that the test message was validated with no errors, or a REJ (Rejection) message with the list of errors indicating the reason why the message failed validation.   

In order to ensure that there is no confusion between reply messages from IFPS and IFPUV, the ACK and REJ messages from IFPUV contain the phrase "This message has been sent by a test system and must not be used operationally".

What is IFPUV?

The IFPUV is a non-operational FPL validation tool used to test flight plans prior to their submission to the operational IFPS. It is an automated system which is not manned by IFPS Operators.

Test flight plans may be submitted with a Date of Flight (DOF) up to 120 hours (5 days) in advance by means of DOF/ in Item 18. The DOF/  may be used to validate route data that becomes applicable after an AIRAC date. The airspace data for the next AIRAC cycle will normally be loaded five days in advance of the AIRAC change.

Although the IFPUV is a copy of the IFPS, it is not connected to the operational IFPS and test messages are neither distributed nor stored in the system. Any flight plan associated messages (i.e. CHG, DLA, CNL, RQP etc) are rejected by the IFPUV with the message: "ERROR: no existing filed flight plan matches this message".

Where can I find information about the NM Flight Progress Messages?

In the Flight Progress Messages document you will find a detailed description of messages from and to systems external to NM which have been identified as Flight Progress Messages, containing both messages from/to the Integrated Flight Plan Processing System (IFPS) and to the Enhanced Tactical Flow Management System (ETFMS). The intended audience is the system and software developers of ANSPs, AOs and others, who plan to implement message exchange with NM in ATM systems.

Where can I find NM user documentation?

Please go to the NM library where you will find all user documents available. They can be listed by the following sub-libraries:

  • HANDBOOK & forms
  • User guides
  • NM release & deployment information
  • Operational services documentation