Station Field Descriptions (Coordinator)
Menu: Administration > Station > Management > select each screen from drop-down list
The workflow to create a new station is described in Manage WorldTracer Stations.

Field | Description |
---|---|
Handled Information |
Only used if another airline or handler handles your airline at this station. The Effective Date/Effective Time fields are used to add or update a station when a handling agreement begins at a future date. The airline or handler code you enter must be a valid WorldTracer customer, and cannot be a dummy airline or handler code. An airline or handler code in this field authorizes this airline or handler to create files for your airline at this station. To return a handled station to self-handling, remove the code in this field and click Update. |
Customer Participancy | The WorldTracer modules. Set to Active to activate a module at the station. |
Matches and Prompts Delivery Attributes |
Where and when matches and delivery prompts should be sent. For each type of message, you may specify:
|
Station Default Address |
The address or addresses that should receive all system prompts, user-generated broadcast messages, and messages from the Station or Headquarters Inbox. Inbox messages are sent at the end of seven days. You may specify a teletype address, an email address, or both. |
LZ Processing |
Select if you contract a third-party company to manage your headquarters office. In WorldTracer terminology, this is called an LZ handler. The purpose of this field is to direct the delivery of Forward On-Hand and Request On Hand messages to the company you designated as your LZ handler. Selecting this field causes these messages to be delivered to the address listed in the Send matches to field. That address must include the code of the company you have listed on the Call Center / LZ screen as your LZ handler. |
SITA generates File References |
Keep the default value of Yes. If set to No, agents cannot create new files at this station. This setting can be used as a preliminary step when deactivating a station, to allow agents to complete existing files but not allow them to create new ones. |

Field | Description |
---|---|
On-Hand Bag inventory acknowledgment | Applies to WorldTracer native users only — leave blank for WorldTracer Desktop. |
Tag number match to the action area inbox | |
Use file reference mandatory elements |
For airlines only. If you select this option, any airline or handling company that creates Delayed Bag or On-Hand Bag Files for you at this station must enter your airline’s mandatory elements in the file. This applies to all Codeshare, Call Center, and LZ Handling relationships. You should contact your handling agent before making this change to confirm that their front-end systems can handle this requirement (the Master Record Mandatory Elements screen shows all the airlines you handle). |
Use file reference mandatory passwords |
Any airline, station, or handling company that creates Delayed Bag or On-Hand Bag Files for you at this station must enter your airline’s mandatory passwords in the file. This applies to all Codeshare, Call Center, and LZ Handling relationships. You should contact your handling agent before making this change to confirm that their front-end systems can handle this requirement. (The Master Record Mandatory Elements screen shows all the airlines you handle.) |
Secondary Reason for Loss |
For airlines only. Requires the use of secondary RL codes, rather than a primary RL code, at this station. This option is enforced for Delayed and Damaged Bag Files created by the airline, their handlers, codeshare, and reciprocal partners at that station, and in Forward Bag transactions. This option is not validated on files created by handlers for airlines that are not members of WorldTracer. |
Action File menu | Applies to WorldTracer native users only — leave blank for WorldTracer Desktop. |
Expanded Action File | |
Station Inbox Local Manager area to user/ Teletype Address |
Inbox messages addressed to the Local Manager folder of a station action file are delivered based on the following:
|
Allow automated SMS |
Activates the sending of automated SMS messages from files with this station in the file reference. Activates the sending of automated SMS messages from files with this station in the file reference. The text and trigger for the message must be activated in the Administration > Airline/Handler > Electronic Messages > Auto/SMS screen. You can enter codeshare and handling exceptions for the station in the Administration > Station > Short Message screen. |
Allow automated Email |
Activates the sending of automated email messages from files with this station in the file reference. The text and the trigger for the message must be activated in the Administration > Airline/Handler > Electronic Messages > Auto/Email screen. |
Allow preformatted SMS |
Allows the agent to send fixed-text messages as an SMS using the Notify Passenger transaction. The text in the messages must be activated in the Administration > Airline/Handler > Electronic Messages > Manual/SMS screen. |
Allow manual SMS | Allows the agent to send free-format text messages as an SMS using the Notify Passenger transaction. |
Allow preformatted Email |
Allows the agent to send fixed-text messages as email using the Notify Passenger transaction. The text in the messages must be activated in the Administration > Airline/Handler > Electronic Messages > Manual/Email screen. |
Allow manual Email | Allows the agent to send free-format messages as an email using the Notify Passenger transaction. |
Use file reference airline system prompts | System prompts are delivered to the file reference airline rather than the handler. |
Performance Targets |
You can set performance targets for the airline/handler, region, and station. They indicate the objectives for the maximum number of mishandled bags per 1,000 passengers per month. Controllable values refer to mishandlings with Reason for Loss codes 10–50, which are mishandlings that can be controlled by the airline. Total values refer to mishandlings with Reason for Loss codes 10-79. See IATA Reason for Loss Codes. Performance targets are included in the following Fault Station reports:
Note: The number of passengers boarded must also be entered for WorldTracer to make the calculations in these reports. |
Send call center / headquarters prompts to Station/Airline | The station and company code where you want to send L (Headquarters handler) or C (call center) prompts listed in your Master User Record Prompts screen. |
Quick On-Hand Bag File Life | Determines how long Quick On-Hand Bag Files remain in your system. Select a Duration using the drop-down menu. The default is 48 hours. |
Hard Copy Teletype Address | A teletype address to receive Handled Airline Copies by teletype. |
Hard Copy Email Address | An email address to receive Handled Airline Copies by email. |
Reports | Sends automated Management Inputs Report (MRI), Activity Status Report (MRS), and Station Log Report for All Files (MLS/A) reports for handled airlines to an email or teletype address. |

For your company and the airlines you handle. Text to include in the PIR.
You enter details for both Delayed Bag and Damaged Bag PIRs. The design of the PIR is the same, but you can specify different values for each type of PIR.
Field | Description |
---|---|
Default Language | Select the default language for both Delayed and Damaged Bag PIRs |
Header | Text in displayed at the top of each PIR generated. You may enter up to five lines of header text, and each line may include up to 60 characters. Example: Company name, address, email. |
Disclaimer Language | Select the language used for the disclaimers in the following Disclaimer fields. |
Disclaimer | Text in displayed at the bottom of each PIR generated. You may enter up to five lines of disclaimer text, and each line may include up to 60 characters. Example: legal disclaimer. |
Passenger's Signature? | When Yes, a line for the passenger's signature is printed at the bottom of each PIR. |
Agent's Signature? | When Yes, a line for the agent's signature is printed at the bottom of each PIR. |
Tip:
The Delayed Bag header displays on a Damaged Bag Property Irregularity Report when you have text in the header or disclaimer fields of the Delayed Bag section but blank fields in the header and disclaimer sections of the Damaged Bag section.
To prevent the same text showing for both reports, enter different headers and disclaimers for each section.

Text to include in the Property Irregularity Report (PIR) of Delayed and Damaged Bag Files for non-participant, non-tracing, and codeshare airlines.
Disclaimer Default to IATA Standard?
Select Yes to print the IATA standard disclaimer at the bottom of a PIR. If No, a disclaimer is not printed.
Tip:
This screen also creates the default PIR format for airlines that do not have headers or disclaimers configured in the Basic PIR screen.

To change the settings, such has the header and disclaimer, for a PIR to immediately take effect at a future date, use the Scheduled PIR screen.
You can specify a new header and disclaimer and set a date for the change. The existing PIR elements stay in place until the date and time you specify. After that they are copied into the Basic PIR screen.
Click Pre-fill from Basic to transfer the values from the Basic PIR screen to save time.

Prevents an airline or handler from sending automated SMSs to passengers. Automated SMSs will not be sent for any airline or handler codes specified in the Airline/Handler fields. If automated SMSs are not active for your company, you don't need to fill in this screen.

Use this screen to configure code share processing exceptions for a station. You can:
-
Allow code share authority at a specific station to airlines not listed in your company's Code Share Agreements screen.
-
Define where system matches are delivered at this station for files created by specified code share partners.
-
Prohibit code share code partners that are listed in your company's Code Share Agreements screen from managing your files at the station.
Example: