amelia SATA List Compliance
- Steven Parent (Unlicensed)
AmeliaRES is fully compliant with Transport Canada's No Fly List. Here's everything you need to know about how this works in amelia, the business rules and options and screenshots to help with the airline's operations document.
Business Rules: Here's the business rules that controls the SATA List
| Business Rule Number | Business Rule Name | Possible Values | Description |
|---|---|---|---|
| 402 | NOFLY | TC (for Canada) or Blank | NOFLY lists used by carrier |
| 621 | SplEnforcedOnCheckIn | N or Y | "Y" enforces SATAL checks for online check in, "N" ignores the check. NOTE: When this business rule is turned on, the SATAL and blacklist will be checked during check in. The No Fly and Blacklist business rules (402 and 423 respectively) must be turned on, or the check will be ignored. |
| 733 | DOB_Mandatory_On_SPL_Checkin | Y or N | N - Do not list passenger DoB as a mandatory field on the Passenger Protect form. Y - Require the passenger's DoB field be populated on the Passenger Protect form when checking in. NOTE: This effect requires business rule 402 to be populated. |
| 734 | Lastname_Mandatory_On_SPL_Checkin | Y or N | N - Do not list passenger last name as a mandatory field on the Passenger Protect form. Y - Require the passenger's last name field be populated on the Passenger Protect form when checking in. NOTE: This effect requires business rule 402 to be populated. |
| 736 | Override_Mandatory_On_SPL_Checkin | Y or N | Y - Admin override is required during a possible no-fly match. N - Admin override is not required |
To block a NoFly passenger from booking online, the following must be included in the settings.xml file of your IBE. Confirm this with your account manager if you have this setting:
<arwctl:NoFlySecurity GlobalNoFlyCheckin="True" LocalBlackList="True" />
Scenario 1 - Possible Match Flow (No DOB provided during booking)
Note: A possible match is when first name and last name is a close match on the list. A possible match ignores DOB and Gender and the name does not need to be an exact match.
Note: The Agent needs to enter a DOB
Scenario 2: Possible Match Flow (DOB provided during booking)
Scenario 3: Possible Match Flow (DOB provided during booking and business rule 736 is enabled)
Note: If Business Rule 736 is enabled and the Agent does not have the permission "No-Fly Override Modify", they will need to call a supervisor. If they have the permission, they need to enter their amelia credentials. If Business rule 736 is set to N, the Confirm Check-In will just work and does not check this permission.
Scenario 4: An Exact Match Flow
Note: To be able to Override, the agent must have the "No-Fly Override Modify" permission and they will receive this screen:
