NP-PF-02 · Fare Distribution & Publishing

📊

Process Flow Diagram (BPMN)

📋

L4 Process Steps

Step	Step Name	Role / Swim Lane	System	Input	Output	KPI	Dec?	Exc?
Phase 1 1.1	Extract approved fare constructs from RM system	Pricing Analyst	Amadeus Revenue Management (NRM)	Approved fare change request from Pricing Strategy team	Fare constructs with cabin, booking class, and route scope ready for tariff formatting	Fare extraction accuracy ≥99.5%; extraction completed ≥48 hrs before effective date	N	N
1.2	Map fares to ATPCO fare basis codes & rule categories	Tariff Analyst	ATPCO	Approved fare constructs, existing tariff structure and fare family definitions	ATPCO-formatted fare records covering Categories 1–35 (advance purchase, min stay, penalties, sales restrictions)	Fare basis code mapping accuracy ≥99%; Category rule coverage ≥95% automated	N	N
1.3	Validate rule consistency, combinability & blackout dates	Tariff Analyst	ATPCO Automated Pricing and Quality Assurance (APQC)	Mapped ATPCO fare records	Pre-submission validation report; list of rule conflicts or blackout date clashes	Pre-submission validation error rate <2%; all errors resolved before ATPCO filing cutoff	Y	Y
Phase 2 2.1	Submit fare tariff records to ATPCO before cutoff	Tariff Analyst	ATPCO	Validated ATPCO fare records; applicable effective and discontinue dates	ATPCO submission receipt with transaction IDs and filing timestamp	Submission success rate ≥99%; filed ≥24 hrs before effective date; zero late filings during peak sale events	N	Y
2.2	Monitor ATPCO acknowledgment and error correction queue	Tariff Analyst	ATPCO	ATPCO submission receipt and transaction IDs	Clean acknowledgment confirmation or itemised error correction list for resubmission	ATPCO acknowledgment received within 2 hrs of submission; error correction resubmitted within 1 hr of error receipt	Y	Y
Phase 3 3.1	Verify fare pickup and display in Sabre GDS	Distribution Analyst	Sabre GDS	ATPCO acknowledgment confirmation and effective date/time	Sabre GDS fare availability test confirmed; mismatches logged for escalation	Sabre fare pickup within 4 hrs of ATPCO effective time; display accuracy ≥99.9%	Y	Y
3.2	Verify fare pickup in Travelport GDS channels	Distribution Analyst	Travelport GDS	ATPCO acknowledgment confirmation	Fare availability confirmed across Travelport Apollo and Galileo subscriber segments	Travelport fare pickup within 4 hrs of ATPCO effective time; consistent display across Apollo and Galileo ≥99%	N	Y
3.3	Verify fare pickup in Amadeus GDS	Distribution Analyst	Amadeus GDS	ATPCO acknowledgment confirmation	Fare availability confirmed in Amadeus GDS; cache refresh status noted	Amadeus fare pickup within 4 hrs of ATPCO effective time; zero stale-cache bookings at effective date boundary	N	Y
3.4	Activate fares for live sale across all GDS channels	Distribution Manager	Amadeus Altéa PSS	Pickup confirmations from Sabre, Travelport, and Amadeus GDS	Fares activated for live booking across all GDS channels; channel activation log created	Channel parity — all GDS channels display identical fares within 30 min of activation; activation completion ≥99.8%	Y	Y
Phase 4 4.1	Publish approved fares via NDC API Gateway	NDC Integration Engineer	NDC API Gateway	Approved fare constructs; GDS activation confirmation; NDC offer schema mapping	NDC AirShopping and AirPrice offer responses reflecting new fares with branded fare family attributes	NDC offer response latency <500ms at p99; NDC fare coverage parity with GDS ≥98%; NDC go-live within 2 hrs of GDS activation	Y	Y
4.2	Validate fare display on direct.com and mobile app	E-commerce Analyst	Amadeus Altéa PSS	NDC offer API responses; direct channel pricing engine configuration	Validated fare display on airline website and mobile app with correct ancillary bundling	Direct channel fare accuracy ≥99.9%; page load including fare display <2 seconds; zero ghost-fare bookings post-filing	N	Y
Phase 5 5.1	Run automated fare audit against ATPCO live filing	Pricing Quality Analyst	ATPCO Automated Pricing and Quality Assurance (APQC)	Live GDS fare quotes from Sabre/Travelport/Amadeus; NDC offer responses; ATPCO filed tariff records	Fare audit report with pass/fail by O&D pair; mismatch list with severity classification	Fare audit pass rate ≥99.8% of sampled O&D pairs; P1 mismatch detection within 30 min of effective time	Y	Y
5.2	Resolve fare display or combinability errors and refile	Tariff Analyst	ATPCO	Fare audit mismatch report; GDS error details	Corrected ATPCO filing or GDS override instruction; incident log with root cause	P1 fare display error resolution within 4 hrs; P2 within 24 hrs; zero repeat errors from same root cause within 30 days	N	Y
Phase 6 6.1	Monitor real-time fare parity across distribution channels	Revenue Management Analyst	Amadeus Revenue Management (NRM)	Real-time fare quotes from GDS, NDC, OTA scrape feeds, and metasearch platforms	Channel parity dashboard; automated parity breach alerts with breach severity and channel identified	Best Available Rate (BAR) parity compliance ≥97% across all monitored channels; parity breach alert-to-resolution SLA <2 hrs for P1 breaches	N	Y
6.2	Archive fare filing records to data lake for compliance	Tariff Analyst	AWS S3 / Redshift	All filed ATPCO records, GDS activation logs, NDC publication logs, and audit reports from current cycle	Archived fare filing records with timestamp, version history, and channel confirmation — retained 7 years per DOT and IATA requirements	Audit trail completeness 100% per filing cycle; archive job SLA <1 hr post-activation; retrieval latency <15 min for DOT audit requests	N	N

📋

Process Attributes

Identification

Process IDNP-PF-02

L1 DomainNetwork Planning & Scheduling

L2 ProcessPricing & Fare Management

L3 NameFare Distribution & Publishing

L4 Steps15 across 6 phases

Decision Gates6 (all with iteration loops)

Exceptions12 documented

Swim Lanes (Roles)

Pricing Analyst

Tariff Analyst

Distribution Analyst

Distribution Manager

NDC Integration Engineer

E-commerce Analyst

Pricing Quality Analyst

Revenue Management Analyst

Systems & Tools

Amadeus Revenue Management (NRM)ATPCOATPCO Automated Pricing and Quality Assurance (APQC)Sabre GDSTravelport GDSAmadeus GDSAmadeus Altéa PSSNDC API GatewayAWS S3 / Redshift

Key Performance Indicators

Extract approved fare constructs from RM systemFare extraction accuracy ≥99.5%; extraction completed ≥48 hrs before effective date

Map fares to ATPCO fare basis codes & rule categoriesFare basis code mapping accuracy ≥99%; Category rule coverage ≥95% automated

Validate rule consistency, combinability & blackout datesPre-submission validation error rate <2%; all errors resolved before ATPCO filing cutoff

Submit fare tariff records to ATPCO before cutoffSubmission success rate ≥99%; filed ≥24 hrs before effective date; zero late filings during peak sale events

Monitor ATPCO acknowledgment and error correction queueATPCO acknowledgment received within 2 hrs of submission; error correction resubmitted within 1 hr of error receipt

Verify fare pickup and display in Sabre GDSSabre fare pickup within 4 hrs of ATPCO effective time; display accuracy ≥99.9%

Verify fare pickup in Travelport GDS channelsTravelport fare pickup within 4 hrs of ATPCO effective time; consistent display across Apollo and Galileo ≥99%

Verify fare pickup in Amadeus GDSAmadeus fare pickup within 4 hrs of ATPCO effective time; zero stale-cache bookings at effective date boundary

Airline-Specific Risks & Pain Points

NRM fare constructs occasionally contain rule exceptions (e.g. negotiated corporate overrides) not natively expressible in ATPCO Category 15 — requires manual tariff analyst workaround adding 2–4 hrs

ATPCO Category 25 (penalty) and Category 15 (sales restriction) rules require manual authoring — automation covers only ~70% of rule types, increasing tariff analyst workload during peak fare events

Blackout date conflicts with advance purchase minimum rules cause ATPCO pre-validation rejection — affects ~5% of seasonal filings and forces same-day reruns against tight submission deadlines

ATPCO submission cutoff (typically 0001Z day prior to effective date) is frequently missed during peak pricing events (holiday flash sales, competitor matching) — missed cutoff delays fare availability by 24 hrs, ceding revenue to competitors

ATPCO batch processing delays during high-volume industry filing periods (US public holidays, IATA fare sales coordination windows) push acknowledgment beyond 4 hrs — creates uncertainty on whether fares will be live for next-day sale open

Sabre GDS fare filing propagation latency can exceed 6 hrs during high-volume pricing events — creates booking windows where incorrect legacy fares are sold, triggering ADM disputes and customer compensation claims

Inputs / Outputs

Primary InputApproved fare change request from Pricing Strategy team

Primary OutputArchived fare filing records with timestamp, version history, and channel confirmation — retained 7 years per DOT and IATA requirements

←PreviousNP-PF-01 · Fare Construction & Filing NextNP-PF-03 · Promotional Fare Design→