NP-PF-14 · Bundled Fare Product Management

📊

Process Flow Diagram (BPMN)

📋

L4 Process Steps

Step	Step Name	Role / Swim Lane	System	Input	Output	KPI	Dec?	Exc?
Phase 1 1.1	Benchmark competitor bundle structures	Revenue Analyst	OAG Schedule Analyser	Competitor fare filings, ATPCO branded fare data, OAG market intelligence	Competitor bundle benchmarking report with component matrix	Coverage of top 10 competing carriers ≥100%; refresh cycle ≤30 days	N	N
1.2	Analyse ancillary revenue by product category	Revenue Analyst	AWS Redshift	Ancillary sales transactions, EMD issuance data, booking class mix reports	Ancillary revenue heatmap by route, cabin, and product type	Ancillary revenue per passenger ≥$28; data completeness ≥98%	N	N
1.3	Model bundle demand & willingness-to-pay scenarios	Pricing Analyst	PROS RM	Ancillary revenue heatmap, competitor benchmark, customer survey data	WTP model with recommended bundle price bands per tier and market	Model R² ≥0.85; scenario output covers ≥3 price points per tier	N	N
1.4	Approve bundle business case for launch	Director of Pricing	Tableau	WTP model output, incremental revenue projection, implementation cost estimate	Signed business case approval with target launch date and bundle tier scope	Projected ancillary revenue uplift ≥12% within 6 months of launch	Y	N
Phase 2 2.1	Define bundle tier hierarchy and component matrix	Pricing Analyst	Amadeus Altéa PSS	Approved business case, ancillary service catalogue, cabin class mapping	Bundle tier design document: tier names, included services, exclusions, upgrade rules	Component matrix covers ≥3 distinct tiers (e.g. Basic, Standard, Flex)	N	N
2.2	Assign fare basis codes per bundle tier and cabin	Pricing Systems Analyst	ATPCO	Bundle tier design document, existing fare basis code registry	Fare basis code matrix mapped to each bundle tier, cabin, and market group	Zero duplicate fare basis code conflicts; code assignment completed within 3 business days	N	N
2.3	Configure EMD-A ancillary service codes in PSS	Pricing Systems Analyst	Amadeus Altéa PSS	Fare basis code matrix, IATA PADIS service type codes, bundle component list	EMD-A service definitions activated in Altéa, linked to fare basis codes	100% of bundle ancillary components mapped to valid IATA PADIS service codes; zero orphaned EMD records	N	Y
2.4	Validate bundle configuration in Altéa staging	QA Analyst	Amadeus Altéa PSS	EMD-A service definitions, fare basis codes, test booking scenarios	Staging validation report: pass/fail per test case, defect list	Test pass rate ≥95% before promotion to production; critical defects = 0	Y	Y
Phase 3 3.1	File bundle fares and conditions in ATPCO	Tariff Analyst	ATPCO	Validated fare basis codes, price points from WTP model, market scope	ATPCO fare filing submission: fare amounts, Cat 1–35 conditions, market applicability	Filing submission-to-activation time ≤24 hrs; zero rejected categories on first submission	N	Y
3.2	Configure branded fare rule categories in ATPCO	Tariff Analyst	ATPCO	Bundle tier names, service inclusions/exclusions, brand attributes	ATPCO branded fare programme records with attribute icons and tier labels	Branded fare attributes display correctly in ≥95% of GDS certified pricing responses	N	N
3.3	Validate GDS fare display and auto-pricing accuracy	Tariff Analyst	Sabre GDS	Filed ATPCO fares, branded fare records, GDS test booking scripts	GDS fare display validation report across Sabre, Travelport, and Amadeus GDS	Pricing accuracy ≥99.9% vs. filed fare; branded attribute display rate ≥95% across all three GDS	Y	Y
Phase 4 4.1	Build NDC offer templates with bundle attributes	NDC Developer	NDC API Gateway	Bundle tier design, IATA NDC 21.3 offer schema, fare basis code matrix	NDC OfferItem definitions with BundleAttributeList populated per tier	NDC offer response time ≤800 ms (p95); bundle attributes present in 100% of eligible offer responses	N	Y
4.2	Configure bundle merchandising on direct booking channel	Digital Product Manager	NDC API Gateway	NDC offer templates, brand asset library, A/B test configuration	Direct channel bundle upsell flows live in staging: tier comparison UI, bundle highlights	Bundle comparison widget load time ≤1.2 s; A/B test variant coverage ≥20% of eligible sessions	N	N
4.3	Execute end-to-end booking regression tests	QA Analyst	Amadeus Altéa PSS	Staging NDC offer templates, direct channel UI, GDS test scripts	Regression test report: full booking-to-ticket flow per tier across all channels	Zero P1/P2 defects in booking-to-ticket flow; regression suite ≥150 test cases	Y	Y
Phase 5 5.1	Activate bundle offer across all channels	Revenue Manager	Amadeus Altéa PSS	Signed go-live approval, regression test sign-off, change management notice	Bundle tiers live in production: ATPCO fares active, NDC offers published, GDS updated	Channel activation completed within 4-hour go-live window; rollback plan tested	N	Y
5.2	Monitor bundle attach rate and incremental revenue	Revenue Analyst	AWS Redshift	Live booking transactions, EMD-A issuance feed, channel attribution data	Daily bundle performance dashboard: attach rate by tier, channel, market, and cabin	Bundle attach rate ≥18% within 30 days of launch; incremental ancillary revenue uplift ≥12%	N	N
5.3	Review bundle performance vs. targets at 30/60/90 days	Director of Pricing	Tableau	Bundle performance dashboard, competitive intelligence update, customer NPS data	Performance review memo: targets met/missed, root cause analysis, recommended actions	Review cadence: D+30, D+60, D+90; action items assigned within 5 business days of review	Y	N
5.4	Adjust bundle composition or pricing based on performance	Pricing Analyst	PROS RM	Performance review memo, updated WTP model, revised competitive benchmark	Change order: updated ATPCO filing, revised NDC offer templates, amended EMD-A config	Change cycle time from decision to live ≤10 business days; pricing adjustments within ±15% of original price points without full re-approval	N	N

📋

Process Attributes

Identification

Process IDNP-PF-14

L1 DomainNetwork Planning & Scheduling

L2 ProcessPricing & Fare Management

L3 NameBundled Fare Product Management

L4 Steps18 across 5 phases

Decision Gates5 (all with iteration loops)

Exceptions7 documented

Swim Lanes (Roles)

Revenue Analyst

Pricing Analyst

Director of Pricing

Pricing Systems Analyst

QA Analyst

Tariff Analyst

NDC Developer

Digital Product Manager

Revenue Manager

Systems & Tools

OAG Schedule AnalyserAWS RedshiftPROS RMTableauAmadeus Altéa PSSATPCOSabre GDSNDC API Gateway

Key Performance Indicators

Benchmark competitor bundle structuresCoverage of top 10 competing carriers ≥100%; refresh cycle ≤30 days

Analyse ancillary revenue by product categoryAncillary revenue per passenger ≥$28; data completeness ≥98%

Model bundle demand & willingness-to-pay scenariosModel R² ≥0.85; scenario output covers ≥3 price points per tier

Approve bundle business case for launchProjected ancillary revenue uplift ≥12% within 6 months of launch

Define bundle tier hierarchy and component matrixComponent matrix covers ≥3 distinct tiers (e.g. Basic, Standard, Flex)

Assign fare basis codes per bundle tier and cabinZero duplicate fare basis code conflicts; code assignment completed within 3 business days

Configure EMD-A ancillary service codes in PSS100% of bundle ancillary components mapped to valid IATA PADIS service codes; zero orphaned EMD records

Validate bundle configuration in Altéa stagingTest pass rate ≥95% before promotion to production; critical defects = 0

Airline-Specific Risks & Pain Points

ATPCO branded fare data can lag 48–72 hrs post-filing; indirect bundle components (lounge, hotels) not visible in GDS fare displays

EMD-A revenue attributed to originating flight only; connecting itinerary ancillary splits require custom Redshift query logic

PROS WTP modelling requires minimum 12 months of ancillary transaction history; new routes have insufficient training data

Approval cycles involving Revenue Management, IT, and Distribution teams average 3–5 weeks; misaligned incentives between RM (yield) and Pricing (volume) can stall sign-off

Altéa PSS service catalogue constraints limit ancillary bundling to pre-defined EMD-A service types; custom inclusions (e.g. lounge access) require workaround fare conditions text

ATPCO fare basis codes limited to 8 alphanumeric characters; encoding tier, cabin, and market group within this constraint requires strict naming convention governance

Inputs / Outputs

Primary InputCompetitor fare filings, ATPCO branded fare data, OAG market intelligence

Primary OutputChange order: updated ATPCO filing, revised NDC offer templates, amended EMD-A config

←PreviousNP-PF-13 · Competitive Fare Intelligence NextNP-PF-15 · Low Fare Guarantee Program Management→