SYNCHRONOUS_REQUEST_RESPONSE

Enables to activate a sector mapping: the supervisor selects a mapping (next or pre-defined mapping) that will replace the current mapping of the concerned ASTUSectorConfiguration.
The supervisor may also choose to revert back to the pre-defined default sector mapping. If not, the input parameters shall be the identifier and the state (next or pre-defined) of the origin sector mapping.
As a consequence, the parameter sectorMappingId is MANDATORY when the parameter revertToDefaultMapping is not filled or set to FALSE (but if revertToDefaultMapping is set to YES, sectorMappingId is not needed)..

Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration..

Enables to load a pre-defined mapping as being the next mapping of a given ASTUSectorConfiguration.

The input parameters shall be:
- the ATSUSectorConfigurationIdentifier,
- the identifier of the sectorMapping.
.

Allows a consumer to modify the radio frequency assigned to control responsibility(ies):
- either by selecting a new radio frequency,
- or by reverting back to the predefined value (off-line defined) of the radio frequency assigned to the given control responsibility (if it has been on-line updated before).

The input parameters shall be:
- the value of the new radio frequency and the controlResponsibility(ies) where the indicated frequency shall be assigned,
- or the controlResponsibility(ies) where the default frequency shall be assigned.

When the aim of this operation is to :
- apply a new frequency to one or several Responsibilities, frequency should be filled
- revert to default frequency for one or several Responsibilities, revertToDefaultFreq should be set to TRUE and frequency shouldn't be filled
.

Enables to unlock a previous manual ARES activation status.
The input parameters shall be the originator and the ARES name. .

Enables to update the following ARES data:
- the status (activated or deactivated),
- the comment associated to the ARES.

The input parameters shall be the originator, the ARES name and the ARES status..

Enables to unlock a previous manual CDR status.
The input parameters shall be the originator and the CDR identifier (airway name and names of the start and last points of the CDR)..

Enables to lock the CDR status to open or closed.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the CDR status..

Allows to add a timesheet into an ARES timetable to define new activation periods.
The input parameters shall be the originator, the ARES name and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity..

Allows to add a timesheet to a CDR.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the timesheet data containing an activation time period, and optionally the activation levels and/or a periodicity..

Allows to remove an existing activation periods timesheet from an ARES timetable.
The input parameters shall be the originator, the ARES name and the identifier of the timesheet to remove..

Allows to remove an existing activation periods timesheet from a CDR timetable.
The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the identifier of the timesheet to remove..

Allows to update an existing activation periods timesheet for an ARES.
The input parameters shall be the originator, the ARES name, the identifier of the timesheet to update and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity..

Allows to modify the current configuration of the runways for an aerodrome of a given Aerodrome Group.
This operation enables an eligible user (normally a supervisor) to modify the following data of a given runway or of the runway(s) of an aerodrome: landing and/or take-off rates, IAP in operation and operating mode (open or closed).
It is also possible to revert to default rate values of runway(s) if no rate value is provided in the operation..

Allows replacing the current Aerodrome Group Configuration with another given aerodrome group configuration.
The user may activate an offline predefined aerodrome group configuration, activate the one previously defined as the Next one or revert back to the default one.

When the aim of this operation is to :
- activate an offline predefined aerodrome group configuration, aerodromeGroupConfigName should be filled with the name of the configuration,
- activate the next aerodrome group configuration, aerodromeGroupConfigName should not be filled,
- revert back to the default aerodrome group configuration, aerodromeGroupConfigName should not be filled and aerodromeConfigurationOrigin should be DEFAULT.
.

Allows removing the fact that an aerodrome group configuration is identified as the next one..

Allows modifying the configuration parameters of an aerodrome.

The 3 possibilities given by this operation are :
- revert to default the aerodrome Altitude Correction
- revert to default the aerodrome Transition Level. In this case, defaultAltitudeCorrection should be set to FALSE
- modify one or several of the following parameters : transitionLevel, altitudeCorrection, modeSCapabilityState. In this case, revertToDefault should not be filled

aerodromeGroup is ignored by CCS..

This operation allows the operator to correct the erroneous fields upon the reception of a CHG or ICHG message.
Whenever a change is made to the data contained in a Flight Plan message already sent to the ATSUs concerned with the flight, they must all be notified. It is particularly important to notify changes of Flight Level or Flight Rules, whether the change is made before departure or en-route. Such notification may be done by phone or ATS/DS when possible; otherwise it must be done by means of a modification message sent to AFTN.

The following CHG fields can be corrected through this operation:
CHG content: callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), otherInformation (F18), amendments of other ICAO fields (F22), alternativeDestinationAerodromeDesignator (F16c).
In CHG, F22 should only amend F7b/c, F8, F9, F10, F13b, F14, F15, F16, F18, F19.

The following ICHG fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD),
estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an FPL or IFPL message.
The FPL message is the flight plan as filed with an ATS unit by the pilot or a designated representative, without any subsequent changes.
The following FPL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), flightRules (F8a), flightType (F8b), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), enRouteCruiseSpeed (TAS or Mach) (F15a), requestedFlightLevel (F15b), icaoRoute (F15c), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), otherInformation (F18), supplementaryInformation (F19).

The following IFPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP),
NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an IAPL message (ICAO format message APL is not applicable CCS).

The following IAPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields in the SFPL upon the reception of an IACH message (ICAO format message ACH is not applicable CCS). It is the modification message type distributed by the IFPS upon receipt and successful processing of an FNM, MFS, and AFP for which a valid associated flight plan exists in the IFPS.

The following IACH fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an ARR or IARR message. Where an Arrival message is required for an IFR/GAT flight or part thereof operating within the IFPZ, the appropriate air traffic services unit shall submit such to the IFPS for processing

The following ARR fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), destinationAerodromeDesignator and actualLandingTime (F17), date of flight in otherInformation (F18).

The following IARR fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), actualLandingTime (ATA), destinationAerodromeDesignator (ADARR)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an CNL or ICNL message. When a schedule flight or a flight for which a Flight Plan Message has been sent, is subsequently cancelled, the ATSU at the point where the flight is cancelled shall send a Cancellation Message.

The following CNL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following ICNL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an DLA or IDLA message. When a scheduled flight, or a flight for which a FPL was despatched, has not left the loading apron within 30 minutes after the scheduled or estimated time of departure; or where there is reason to believe that such a flight will not be in a position to leave within the 30 minutes due to the late arrival of the aircraft on the previous sector or for any other reason.

The following DLA fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following IDLA fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..