Codeshare & Interline Schedule Planning
Network Planning & Scheduling › Schedule Planning · 16 L4 steps · 5 phases · 6 decision gates · Updated 2026-03-18 17:45
📊
Process Flow Diagram (BPMN)
📋
L4 Process Steps
| Step | Step Name | Role / Swim Lane | System | Input | Output | KPI | Dec? | Exc? |
|---|---|---|---|---|---|---|---|---|
Phase 1 1.1 |
Identify codeshare & interline partner candidates | Alliance & Partnership Manager | OAG Schedule Analyser | Network gap analysis, O&D demand data, commercial strategy brief | Ranked partner shortlist with O&D overlap scores | Min 5 candidate partners assessed per planning cycle | N | N |
| 1.2 | Analyse partner O&D network overlap and revenue potential | Network Planning Analyst | Amadeus SkyCAST | Partner SSIM schedule, OAG market share data, own O&D traffic database | Revenue opportunity model: incremental pax and yield per route | Projected incremental load factor contribution ≥3 ppts on thin O&D routes | N | N |
| 1.3 | Verify IIA and SPA agreement status with legal | Interline Agreements Specialist | SAP S/4HANA Finance (FI/CO) | Partner carrier code, IATA IIA registry extract | Agreement status confirmation (IIA active / SPA in place / none) | Agreement status verified within 2 business days of partner selection | Y | Y |
Phase 2 2.1 |
Request SSIM schedule data feed from partner airline | Schedule Coordination Analyst | Amadeus SkyWORKS | Partner carrier approval, IATA SSIM Chapter 7 format specification | Received partner SSIM file imported into SkyWORKS schedule database | SSIM file received and validated within 5 business days of partner agreement | N | Y |
| 2.2 | Validate connection times against airport MCT tables | Schedule Coordination Analyst | Amadeus SkyWORKS | Partner SSIM flights, own schedule, IATA MCT database per airport | MCT compliance report: list of connections meeting/failing minimum connect time | 100% of proposed connect itineraries MCT-compliant before GDS loading | Y | Y |
| 2.3 | Resolve schedule conflicts via SSIM SCR negotiation | Schedule Coordination Analyst | Amadeus SkyWORKS | MCT non-compliance list, partner contact, SSIM SCR message format | Revised partner or own schedule achieving MCT compliance | Schedule conflicts resolved within 10 business days; <5% of proposed connections requiring rescheduling | N | Y |
| 2.4 | Confirm aligned codeshare schedule and flight numbering | Network Planning Manager | Amadeus SkyWORKS | MCT-compliant schedule, codeshare designator allocation (IATA two-letter code) | Confirmed codeshare flight number series filed in SkyWORKS | Codeshare flight numbers registered with IATA within 7 days of schedule confirmation | N | N |
Phase 3 3.1 |
Configure block-space or free-sale inventory allocation | Revenue Management Analyst | Amadeus Altea PSS | Confirmed codeshare schedule, capacity agreement (block vs free-sale terms) | Inventory allocation rules loaded into Altéa PSS for codeshare flight numbers | Block-space utilisation target ≥70% within 30 days of schedule launch | N | Y |
| 3.2 | File interline prorate and SPA agreements via ATPCO | Interline Agreements Specialist | ATPCO | Bilateral prorate formula, revenue split percentage, SPA effective date | Published ATPCO prorate agreement record accessible by all GDS and PSS | ATPCO filing effective within 24 hours of D-1 activation date; 0 unpriced itineraries at launch | N | Y |
| 3.3 | Validate fare combinability and through-fare rules in PSS | Fares & Pricing Analyst | Amadeus Altea PSS | ATPCO prorate records, own published fares, partner fare tariff | Validated combinability matrix: list of valid fare combinations per O&D | 100% of marketed O&D pairs have at least one priceable interline itinerary at launch | Y | Y |
Phase 4 4.1 |
Load codeshare designators into GDS participant tables | Distribution & GDS Analyst | Sabre GDS | Confirmed codeshare flight numbers, operating carrier codes, effective/discontinue dates | Codeshare flights live in Sabre, Travelport, and Amadeus GDS participant tables | GDS loading complete ≥14 days before first codeshare departure | N | Y |
| 4.2 | Validate end-to-end booking and ticketing path in GDS | Distribution & GDS Analyst | Travelport GDS | Live GDS participant table entries, test PNR scenario set | UAT sign-off: booking, pricing, and ticketing confirmed for all O&D pairs | Zero pricing errors in UAT across 100% of marketed O&D pairs before go-live | Y | Y |
| 4.3 | Activate NDC API connection for partner direct-channel booking | Digital Distribution Manager | NDC API Gateway | Partner NDC Level 3 certification status, API credential exchange | Live NDC offers including codeshare itineraries available via partner direct channel | NDC channel contributing ≥10% of codeshare bookings within 90 days of launch | N | Y |
Phase 5 5.1 |
Brief operations and customer service on interline procedures | Ground Operations Manager | SITA Airport Management System (AMS) | Codeshare operating procedures manual, baggage interline agreement, reaccommodation policy | Briefed airport teams; interline baggage rules loaded into SITA AMS | 100% of affected airport stations briefed ≥7 days before first codeshare departure | N | N |
| 5.2 | Monitor codeshare booking ramp-up and yield metrics | Revenue Management Analyst | Amadeus Revenue Management (NRM) | Daily PNR booking data, codeshare flight segment reports from Altéa | Weekly performance dashboard: pax volume, yield, load factor by O&D and partner | Codeshare load factor ≥70% by week 4 post-launch; interline yield within 5% of target prorate | Y | N |
| 5.3 | Conduct 90-day post-launch performance review | Network Planning Manager | Amadeus SkyCAST | 90-day pax and revenue actuals, prorate settlement statements, partner capacity data | Performance review report with recommendations: expand, renegotiate, or discontinue | Incremental revenue per ASK (RASK) contribution ≥2% above baseline on target O&D pairs | Y | N |
📋