Fare Construction & Filing
Network Planning & Scheduling › Pricing & Fare Management · 16 L4 steps · 6 phases · 7 decision gates · Updated 2026-03-18 19:23
📊
Process Flow Diagram (BPMN)
📋
L4 Process Steps
| Step | Step Name | Role / Swim Lane | System | Input | Output | KPI | Dec? | Exc? |
|---|---|---|---|---|---|---|---|---|
Phase 1 1.1 |
Extract Competitive Fare Data from GDS | Pricing Analyst | Sabre AirVision Network & Schedule | GDS published fares, OAG Schedule Analyser competitive feeds | Competitor fare matrix by O&D, cabin, and advance purchase window | Competitive data refresh latency ≤24 hours | N | N |
| 1.2 | Analyse O&D Demand & Price Elasticity | Pricing Analyst | Amadeus SkyCAST | Historical booking curves, O&D traffic reports, demand signal matrix | Price elasticity model by market segment and booking window | Elasticity model R² ≥0.85 | N | N |
| 1.3 | Confirm Market Opportunity & Pricing Mandate | Director of Pricing | Amadeus SkyCAST | Elasticity model, competitive fare matrix, revenue target by route | Pricing mandate document — target position vs. market (premium, match, or undercut) | Time-to-mandate ≤2 business days from competitive trigger | Y | N |
Phase 2 2.1 |
Define Fare Basis Codes & Fare Families | Pricing Analyst | ATPCO | Pricing mandate, existing fare basis code library | Fare basis code list per cabin with fare family mapping (Economy Light, Standard, Flex, Business) | Fare basis code uniqueness — zero duplicate FBC conflicts per filing batch | N | N |
| 2.2 | Set Fare Ladder by Cabin & Booking Class | Pricing Analyst | Amadeus Revenue Management (NRM / AltéaRM) | Fare family definitions, RM booking class inventory map, target revenue contribution | Fare ladder table — fare amounts by booking class (Y/B/M/H/Q/V/L/G/W) for each O&D | Average fare premium over lowest competitor ≥5% in protected markets | N | N |
| 2.3 | Validate Fare Ladder Against RM Inventory | Revenue Management Analyst | Amadeus Revenue Management (NRM / AltéaRM) | Proposed fare ladder, current RM class availability settings | Reconciled fare-to-class mapping; conflict report if misalignment detected | Zero booking class conflicts at time of filing; reconciliation completed within 4 hours | Y | N |
Phase 3 3.1 |
Code Advance Purchase & Minimum Stay Rules | Pricing Analyst | ATPCO | Approved fare structure, regulatory requirements, market seasonality calendar | ATPCO Category 5 (Advance Purchase) and Category 6 (Minimum Stay) rule records | Rule coding error rate ≤0.5% per 1,000 fare rule records filed | N | N |
| 3.2 | Define Change & Cancellation Fee Structures | Pricing Analyst | ATPCO | Commercial policy (fee schedule), fare family service attribute matrix | ATPCO Category 16 (Penalties) rule records; fee table by fare family | Fee structure consistency — 100% of fare families have documented penalty rules before filing | N | Y |
| 3.3 | Set Combinability & Routing Rules | Senior Pricing Analyst | ATPCO | Interline agreements, codeshare partner list, ticketing authority records | ATPCO Category 10 (Combinations) and Category 25 (Fare by Rule) records | Routing rule coverage — 100% of marketed O&Ds with codeshare have valid combination rules | Y | Y |
Phase 4 4.1 |
Submit Fare Records to ATPCO | Pricing Analyst | ATPCO | Validated fare basis codes, amounts, and rule records; effective date schedule | ATPCO filing batch confirmation; fare record IDs | Filing lead time: fares effective ≥T+24 hours from ATPCO submission; zero rejected records per batch | N | Y |
| 4.2 | Distribute Fares to GDS Channels | Distribution Analyst | Sabre GDS | ATPCO fare records (published), Travelport and Amadeus GDS distribution agreements | GDS fare tables populated in Sabre, Travelport, and Amadeus GDS; EDIFACT ATPCO push confirmed | GDS distribution lag ≤2 hours post-ATPCO publication | N | N |
| 4.3 | Publish NDC Offers via API Gateway | Distribution Analyst | NDC API Gateway | Fare structure JSON, fare family service attributes, ancillary offer catalogue | NDC Offer Response payload; fare published in NDC-connected OTA and TMC channels | NDC offer availability within 1 hour of ATPCO activation; API error rate ≤0.1% | Y | Y |
Phase 5 5.1 |
Execute End-to-End Fare Shopping Test | QA / Pricing Analyst | Amadeus Altéa PSS | Filed fare effective date, test O&D pairs, booking class list | Fare shopping test report — fare display, priceable itineraries, tax calculation | QA pass rate ≥99.5% of tested fare/class combinations before go-live | Y | Y |
| 5.2 | Validate Fare Display Across All GDS Channels | Distribution Analyst | Travelport GDS | Fare shopping test results, GDS fare display screens (Sabre, Travelport, Amadeus) | Cross-channel fare parity report; exception list for mis-displayed fares | Fare parity across all three GDS channels within 2 hours of ATPCO activation; zero parity breaches at go-live | N | Y |
Phase 6 6.1 |
Monitor Filed Fare Performance vs. Revenue Targets | Revenue Management Analyst | Amadeus Revenue Management (NRM / AltéaRM) | Live booking data, fare mix report, yield-per-passenger by fare family | Fare performance dashboard; revenue alert if yield drops >5% below target | Revenue per available seat mile (RASM) within ±3% of plan at T+7 post-filing | Y | N |
| 6.2 | Track Competitor Fare Changes & Trigger Re-filing | Pricing Analyst | OAG Schedule Analyser | Competitor ATPCO fare change alerts, GDS fare monitor feeds | Competitive response recommendation; re-filing ticket if action required | Competitive response time ≤4 hours for primary O&Ds; ≤24 hours for secondary markets | Y | N |
📋