APIS , Advance Passenger Information System is an information of passengers and crew onboard an aircraft. Some countries require this message to be send prior to the departure of the flight.
Different formats are used for APIS, N-OC currently support messages to USA, UK, Canada, Cuba, CHINA, Mexico, Denmark and Italy
Getting started
There is a User right called 'APIS'. This gives access to the APIS icon under 'N-OC / Human Resource / APIS'.
The status and missing data information is displayed in Automation Factory / APIS tab.
Sleipner handles the message generation / Master Crew List updates.
Template and setup data for the creation and sending of MCL and FCM data associated with APIS TEMPLATE transmissions. This window displays the current list of defined APIS TEMPLATE types. To locate an existing APIS TEMPLATE type enter the name (or partial name) in the dialogue box and select Search. All matching results will be displayed. | |
Create New APIS TEMPLATE type Select the NEW radio button to create a new APIS TEMPLATE type. The following window is displayed. APIS Fields: | | Name: | Mandatory, max. 100 characters. | Format: | PLAIN TEXT, USA, UK, Canada, Cuba, CHINA, Mexico, Denmark, Italy, Free text, APPv4 as appropriate to the recipient of the APIS messages. | Country: | Name of the country that will be the recipient of the email messages. | Activity filter: | Aircraft filter that selects the relevant flight legs for the APIS messages. | Cargo filter: | If cargo flights are to be included in the APIS transmissions select the aircraft filter that selects cargo flights | Pre Departure: | specify the value in minutes that a FCM message should be sent prior to the departure of a flight. | Pre Departure 2: | Resend the FCM x mins before departure (needed for Cuba) | Post Departure: | Specify the value in minutes that a FCM message should be sent after the departure of a flight if any amendments have been made. | Message size: | The maximum number of characters that may be include in a single message (relates to SITA messages only). | Cancel Filter: | Filter that removes cancelled flights | Contact: | The name of the person in the airline who is designated as the point of contact. | Phone: | The telephone number of the person in the airline who is designated as the point of contact. | Fax: | fax number of the person in the airline who is designated as the nominated individual. | Email: | The email address of the person in the airline who is designated as the nominated individual. | UNBSender: | Mandatory Interchange header. The name of the airline sending the APIS messages. | Code: | Two-letter IATA code of the airline sending the APIS message. | UNB Recipient: | SITA address of the authority or agency receiving the APIS messages (relates to APIS messages sent via SITA only | Code: | SITA priority code to be used in the sending of the message (relates to APIS messages sent via SITA only | UNGSender: | Functional Group header(conditional). The UNG segments are used only if the transmission carries several groups of messages of different types. EDItEUR strongly recommends that a transmission should be limited to carrying only one group of messages of a single type. The UNG segments are not, therefore, used in EDItEUR practice | Code: | Two-letter IATA code of the airline sending the APIS message. | UNG Recipient: | SITA address of the authority or agency receiving the APIS messages (relates to APIS messages sent via SITA only | UNHSender: | Message header, Mandatory for messages to Italy | Human Resource filter: | The filter name that includes crew to be included in the MCL and FCM messages. | Passport: | The document name that is the crew members passport to be used for the APIS country concerned. | Licence: | The document name that is the crew members license to be used for the APIS country concerned. | Allow empty Expiry: | If Pilot licence is ticked you have access to define countries that allow Licence data without an expiry date. | Address: | The Address Type name that specifies the crew members place of residence to be used for the APIS country concerned. | Roster Designator for not active crew | Crew with the selected Roster designator will be ignored when sending FCM | CR1 filter: | The name of the HR Filter that specifies cockpit crew. | CR2 filter: | The HR Filter that specifies cabin crew. | CR3 filter: | The HR Filter that specifies instructors (if required). | CR4 filter: | The HR Filter that specifies cargo non-cockpit crew. | CR5 filter: | The HR Filter that specifies pilots who are deadheading. | Active: | Select Active if the APIS TEMPLATE type is to be used. | Use Master Crew List: | Send MCL master crew list. Master crew list is normally send the day before. | Pilot licence: | Check box if pilot license information is required to be sent. | Include Address: | Check box if address information is required to be sent. | Include Crew Status: | Check box if the crew status is required to be indicated. | Attach: | If you send APIS by email and want the message to go in an attachment and not in the actual email body | Sender/Recipient code: | This control if you include the two letter airline code | MiddelName without separator: | First name and middel name will not be separated. | | |
Once the parameters are defined, select the SAVE radio button and the information is committed to the database and the new entry will appear in the existing list of items. To discard a new item prior to save select the Cancel radio button and the information will be removed and the window closed. | |
Individual APIS Message It is possible to create an individual APIS message. When you select "Free Text" a new dialog will open. You can configure the HEADER, CREW and FOOTER section. Tick the elements you want to include in the message. You can use the default template or you can create your own template in the Integration Factory. Each segment is one line in the message. | |
Header Configuration The header can contain one of the following segments: UNA UNB UNG UNH BGM RFF NAD COM TDT LOC1 DTM1 LOC2 DTM2 | |
Crew Configuration Crew data - repeatable for each crew member; containing segmetns: NAD ATT DTM LOC1 LOC2 LOC3 LOC4 LOC5 EMP NAT DOCP DTMP LOCP DOCL DMTL LOCL | |
Footer Configuration Footer - one footer containing segments: CNT UNT UNE UNZ | |
Preview Click Preview to see the output | |
Edit Existing APIS TEMPLATE type
Once a APIS TEMPLATE type is added to the list it can be amended using the following procedure.
Indicate the APIS TEMPLATE type (s) to be amended by selecting the tick box to the left of the APIS TEMPLATE type name and select the Edit radio button. The APIS TEMPLATE type details will appear in a new window and can be edited as required. If more than one APIS TEMPLATE type is selected then each item will appear in a separate window and can be edited in turn. Once the required amendments have been made select the Save radio button to commit the changes to the database.
Copy Existing APIS TEMPLATE type
A APIS TEMPLATE type can be copied to create a new APIS TEMPLATE type using the following procedure.
Indicate the APIS TEMPLATE type that is to be copied by selecting the tick box to the left of the document name and select the Copy radio button. The EDIT dialogue window is displayed and the new parameters can be entered. Once the parameters have been defined select the Save radio button to commit the changes to the database type. The changes can be discarded by selecting the Cancel radio button and the parameters will not be committed to the database type.
Delete Existing APIS TEMPLATE type
APIS TEMPLATE types that are no longer required can be deleted using the following procedure.
Indicate the APIS TEMPLATE type that is to be copied by selecting the tick box to the left of the document name and select the Delete radio button. The APIS TEMPLATE type is removed from the database type and is no longer visible in the list of available types.
