v1.0
Home Network Planning & Scheduling ⭐ GitHub
📊

Process Flow Diagram (BPMN)

NP-SD-13 BPMN diagram
📋

L4 Process Steps

StepStep NameRole / Swim LaneSystem InputOutputKPIDec?Exc?
Phase 1
1.1
Extract sales transactions from PSS and GDS feeds Sales Data Engineer Amadeus Altéa PSS Daily booking, ticketing, and revenue transactions from Altéa Raw sales transaction file (PNR, fare basis, channel, O&D) Data extraction completeness ≥99.5% of daily transactions N N
1.2 Ingest GDS booking and yield data via settlement files Sales Data Engineer Sabre GDS Sabre PRISM BSP settlement files and Travelport agency booking reports Consolidated GDS channel dataset with agency, fare, and yield fields GDS data ingestion within 4 hours of BSP file receipt N Y
1.3 Validate data quality and apply cleansing rules Sales Data Analyst AWS Glue Raw PSS and GDS transaction datasets Quality-scored dataset; rejected records quarantine file Data quality score ≥98% (nulls, duplicates, invalid fare codes <2%) Y Y
1.4 Load cleansed data to analytics data warehouse Sales Data Engineer AWS Redshift Validated and cleansed sales transaction dataset Populated sales_fact and channel_dim tables in Redshift Load completion within 2 hours of data quality sign-off; zero load failures N Y
Phase 2
2.1
Configure KPI targets and alert thresholds in BI platform Sales Analytics Manager Tableau Annual commercial plan targets (revenue, load factor, yield by route/channel) Configured KPI thresholds and RAG alert rules in Tableau 100% of approved KPI targets loaded before reporting cycle open N N
2.2 Build channel and revenue performance dashboards Sales Analytics Manager Tableau Redshift sales_fact tables; KPI threshold configuration Channel performance dashboard (GDS, NDC, direct, corporate) and revenue dashboard Dashboard refresh latency ≤15 minutes from data load completion N N
2.3 Validate dashboard figures against source system totals Sales Data Analyst SAP S/4HANA Finance (FI/CO) Tableau dashboard revenue totals; SAP AR revenue recognition ledger Reconciliation sign-off report; variance log if delta >0.5% Dashboard-to-SAP revenue variance ≤0.5% before stakeholder distribution Y Y
Phase 3
3.1
Analyse GDS channel yield and cost-per-booking Distribution Analytics Analyst Sabre GDS GDS segment dataset; published GDS booking fee schedule Cost-per-booking report by GDS (Sabre / Travelport / Amadeus) and market GDS net yield ≥$0.08/RPM after distribution cost deduction N N
3.2 Assess NDC and direct channel conversion rates Distribution Analytics Analyst NDC API Gateway NDC API search-to-book funnel data; direct website booking data NDC/direct conversion funnel report with drop-off analysis NDC channel conversion rate ≥2.8%; direct web conversion ≥4.5% N N
3.3 Review corporate and TMC account performance vs contract Corporate Sales Manager Sabre GDS Sabre PRISM corporate account booking volumes; contracted revenue commitments Corporate account scorecard; list of accounts below commitment threshold ≥90% of corporate accounts at or above 80% of contracted volume target Y Y
Phase 4
4.1
Analyse fare class mix and RASK by route and market Revenue Analytics Analyst Amadeus Revenue Management (NRM) Closed booking data by fare basis and O&D from Altéa NRM Fare mix report: premium vs discount share, RASK by route Average RASK ≥$0.145; premium fare class share ≥22% of total revenue N N
4.2 Monitor load factor and yield trends vs prior year Revenue Analytics Analyst AWS Redshift Current period and prior year sales_fact data from Redshift Load factor and yield trend report; YoY variance by route, season, and channel Load factor ≥83%; yield variance to prior year within ±5% N N
4.3 Identify routes and segments below revenue performance target Network Revenue Manager Tableau RASK and load factor report; network revenue target thresholds from commercial plan Underperformance flag list: routes with RASK <target for ≥2 consecutive periods Zero routes with RASK <80% of target unaddressed beyond two consecutive reporting cycles Y Y
Phase 5
5.1
Produce budget variance and forecast deviation analysis Sales Finance Analyst SAP S/4HANA Finance (FI/CO) Actuals from SAP AR; approved budget and rolling forecast from SAP CO Variance analysis pack: actual vs budget vs forecast by revenue line Variance commentary complete for all lines deviating >±3% from budget N N
5.2 Compile executive management reporting pack Sales Analytics Manager Power BI Channel performance, fare mix, RASK, load factor, and variance reports Monthly sales performance deck with KPI scorecards and narrative commentary Management pack distributed by business day 5 of the following month N N
5.3 Assess exceptions and determine escalation requirement VP Sales & Distribution Power BI Management reporting pack; KPI RAG status from Tableau Escalation decision: confirmed exception list for board or commercial committee 100% of Red-rated KPIs reviewed within 24 hours of report distribution Y N
5.4 Distribute reports and archive reporting cycle artefacts Sales Data Analyst AWS S3 Final approved management pack and all source reports Reports distributed to stakeholders; artefacts archived in S3 with version tag 100% of reports archived within 1 business day; distribution list accuracy ≥99% N Y
📋

Process Attributes

Identification

Process IDNP-SD-13
L1 DomainNetwork Planning & Scheduling
L2 ProcessSales & Distribution
L3 NameSales Performance Reporting & Analytics
L4 Steps17 across 5 phases
Decision Gates5 (all with iteration loops)
Exceptions7 documented

Swim Lanes (Roles)

Sales Data Engineer
Sales Data Analyst
Sales Analytics Manager
Distribution Analytics Analyst
Corporate Sales Manager
Revenue Analytics Analyst
Network Revenue Manager
Sales Finance Analyst
VP Sales & Distribution

Systems & Tools

Amadeus Altéa PSSSabre GDSAWS GlueAWS RedshiftTableauSAP S/4HANA Finance (FI/CO)NDC API GatewayAmadeus Revenue Management (NRM)Power BIAWS S3

Key Performance Indicators

Extract sales transactions from PSS and GDS feedsData extraction completeness ≥99.5% of daily transactions
Ingest GDS booking and yield data via settlement filesGDS data ingestion within 4 hours of BSP file receipt
Validate data quality and apply cleansing rulesData quality score ≥98% (nulls, duplicates, invalid fare codes <2%)
Load cleansed data to analytics data warehouseLoad completion within 2 hours of data quality sign-off; zero load failures
Configure KPI targets and alert thresholds in BI platform100% of approved KPI targets loaded before reporting cycle open
Build channel and revenue performance dashboardsDashboard refresh latency ≤15 minutes from data load completion
Validate dashboard figures against source system totalsDashboard-to-SAP revenue variance ≤0.5% before stakeholder distribution
Analyse GDS channel yield and cost-per-bookingGDS net yield ≥$0.08/RPM after distribution cost deduction

Airline-Specific Risks & Pain Points

Altéa feed latency can delay T+1 reporting; GDS interline sales require separate reconciliation from Sabre and Travelport settlement files
Sabre PRISM and Travelport use different file formats requiring dual ETL pipelines; mismatched PNR cross-references cause ~2% of records to fail automatic join
ATPCO fare basis code changes not always reflected in Altéa within same reporting cycle, causing mis-classification of fare families
Redshift cluster contention during concurrent ETL and BI query windows causes load job timeouts; workload management (WLM) tuning needed per reporting cycle
Mid-year target revisions require manual threshold updates across multiple Tableau workbooks; no automated sync from SAP S/4HANA budget module
NDC API Gateway booking data lacks full itinerary detail compared to GDS PNRs, creating reporting asymmetry between channels that distorts yield comparisons

Inputs / Outputs

Primary InputDaily booking, ticketing, and revenue transactions from Altéa
Primary OutputReports distributed to stakeholders; artefacts archived in S3 with version tag
PreviousNP-SD-12 · Metasearch & Comparison Site ManagementNextNP-SD-14 · Distribution Cost Optimization