LHG:SARA Project: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
Stefanseiler (talk | contribs)
Stefanseiler (talk | contribs)
 
(136 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Phase 1 - SARA Fundamental ==
== Phase 1 - SARA Fundamental ==
Objectives:
* [[SARA.Core (Special Assistance Request Management Suite)]]
* [[SARA.PAXPortal]] for LH und Discover
* [[SARA.DeliveryPartnerPortal]] - for secure communication with partners
* Basic process automation engine


=== Current Project Plan ===
{| class="wikitable"
{| class="wikitable"
!
!
! rowspan="2" |Dev
! rowspan="2" |Dev
Focus
Focus
! rowspan="2" |Est. Size
! colspan="2" |2024
! colspan="2" |2024
! colspan="12" |2025
! colspan="12" |2025
Line 17: Line 11:
! rowspan="2" |Est.
! rowspan="2" |Est.
Size
Size
! rowspan="2" |Progress
! rowspan="2" |Dev
Progress
! rowspan="2" |External Dep.
! rowspan="2" |External Dep.
Notes
Notes
Line 42: Line 37:
!May
!May
!Jun
!Jun
|-
| colspan="25" |
|-
!Peparatory work
!4
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Discovery
! colspan="2" |
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Discovery
! colspan="12" |
!5
!100%
|
|-
|-
|Kickoff / Initially planned discovery
|Kickoff / Initially planned discovery
|
|
| Def
|
|
| style="text-align:center; background-color:#ADD8E6" |Def
|
|
|
|
Line 56: Line 63:
|
|
|
|
!
|
|
|
|
Line 67: Line 73:
|
|
|S
|S
!100%
|100%
|3 days pre-order
|
|-
|Architecture & Shared Logic Hubs
|
|
| colspan="2" |Discovery
|
|
| colspan="3" style="text-align:center; background-color:#FFCCCB" |Re-Discovery
|
|
|
|
|
|
|
|
|
|
|
|
|XL
|100%
|✅
|-
| colspan="25" |
|-
|-
! style="text-align:left;" |Administration tools
! style="text-align:left;" |Administration tools
!
!8
!
| style="text-align:center; background-color:#ADD8E6" |Dis.
| style="text-align:center; background-color:#96F97B" |
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
| colspan="3" |Dev
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Discovery
! colspan="2" |
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Q&A
| colspan="2" style="text-align:center; background-color:#FFFFE0" |QA
| style="text-align:center; background-color:#96F97B" |Dev
| style="text-align:center; background-color:#FFFFE0" |QA
!Dev
!Dev
!Q&A
!QA
! colspan="7" |
!Dev
! colspan="2" |QA
!
!
!
!70%
!18
!85,8%
!
!
|-
|-
|Definition / Discovery
|Definition / Discovery
|
|Def
| colspan="3" |Dev
| colspan="3" style="text-align:center; background-color:#FFCCCB" |Re-Discovery
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|Def
|
|
|L
|100%
|✅
|-
|[[Carrier Admininistration Tools|LH Admininistration Tools]]
|Mixed
|
|
|
|
| colspan="3" |Discovery
|
|
|
|
|
|
|
|
| colspan="3" |Dev
|QA
|
|
|
|
Line 107: Line 162:
|
|
|
|
|L
|100%
|100%
|
|
|-
|-
|[[Carrier Admininistration Tools]]
|[[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|Mixed
|Mixed
|
|
Line 120: Line 176:
|
|
| colspan="3" |Dev
| colspan="3" |Dev
|Q&A
|QA
|
|
|
|
|
|
|
|
|
|L
|100%
|✅
|-
|SLHs ([[Dev:SLH - TravelCarrierDataDistribution|TravelCarrierDataDistribution]] & OperationCenterPAXExchange
|BE
|
|
|
|
|
|
|
|
|
| colspan="2" |Dev
|QA
|
|
|
|
Line 132: Line 212:
|
|
|L
|L
|80%
|100%
|✅ {{Gray-Tag|Text=Ticket size changed over time}}
|-
|Minor extensions during further discovery
|Mixed
|
|
|
|
|
|
|
|
|
|
| colspan="2" |Dev
|QA
|
|
|
|
|
|
|
|
|S
|100%
|✅
|-
|-
|[[Travel Service Operation Center Administration Tools]]
|SLH - TravelCDDD
|Mixed
SLH - OCPAXE extensions due to feedback
|
|
|
|
|
|
Line 145: Line 252:
|
|
|
|
| colspan="3" |Dev
|Q&A
|
|
|
|
|
|
|
|
|Dev
|
|
|
|
Line 156: Line 262:
|
|
|
|
|XL
|40%
|
|
|S
|100%
|✅
|-
|-
|Minor extensions during further discovery
|Minor extensions during feedback sessions (limitations)
|Mixed
|Mixed
|
|
|
|
|
Line 175: Line 283:
|
|
|Dev
|Dev
|Q&A
|QA
|
|
|
|
|
|S
|100%
|✅
|-
|Automation Engine Admin
|Mixed
|
|
|
|
|
|
|
|
|
|
|
Line 182: Line 308:
|
|
|
|
|Dev
|
|Dev
| colspan="2" |QA
|
|
|S
|0%
|
|
|L
|15%
|{{Yellow-Tag|YellowText=Repriorized}}
|-
| colspan="25" |
|-
|-
! style="text-align:left;" |Architecture & Shared Logic Hubs
! style="text-align:left;" |Passenger Portals
!
!28
!
! colspan="7" |
!
| colspan="4" style="text-align:center; background-color:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Discovery
| style="text-align:center; background-color:#FFFFE0" |QA
!
| colspan="2" style="text-align:center; background-color:#96F97B" |Dev
!
| colspan="2" style="text-align:center; background-color:#FFFFE0" |QA
!
| colspan="2" style="text-align:center; background-color:#FFCCCB" |Discovery
| colspan="5" style="text-align:center; background-color:#96F97B" |Dev
!
!
!
!
!
!
!
!
!
!
!
!
!30%
!11
!90,9%
!
!
|-
|-
|Finishing Documentation & Inter-Digital Architecture
|[[PAX.Portal|PAX funcationality in PAX.Portal for LH]]
|Arch
|FE & BE
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
|
|
|
|
| colspan="4" |Dev
|QA
|
|
|
|
Line 230: Line 355:
|
|
|XL
|XL
|95%
|100%  
|DB-Model, Process Aut. Engine (PAE)
|
|-
|-
|[[Dev:SLH - TravelCarrierDataDistribution|SLH - TravelCarrierDataDistribution]]
|[[Dev:SLH - PortalUsageInteraction|SLH - PortalUsageInteraction]]
|BE
|BE
|
|
Line 254: Line 379:
|
|
|
|
|
|L
|M
|100%
|0%
|
|[[Carrier digital]] <--> [[PAX Portal digitals|PAX Portal Digitals]], [[Travel assistance service operation center digitals|Travel Service Operation Center Digitals]]
|-
|-
|[[Dev:SLH - PortalUsageInteraction|SLH - PortalUsageInteraction]]
|[[PAX.Portal|Full PAX.Portal for Discover]]
|BE
|FE
|
|
|
|
Line 269: Line 393:
|
|
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|
|
| colspan="2" |Dev
| colspan="2" |QA
|
|
|
|
|
|
|
|
|M
|90%
|
|
|L
|0%
|PAX Portal Digitals <-> Passenger Digitals, Travel Partner Digitals
|-
|-
|[[Dev:SLH - TravelServiceManagementEcosystem|SLH - TravelServiceManagementEcosystem]]
|[[Dev:PAX.Portal feature tree|TP-Employee features]]
|BE
|Mixed
|
|
|
|
|
Line 298: Line 419:
|
|
|
|
| colspan="3" |Dev
|
|
|
|
|
|
|Dev
|Conf
|QA
|
|
|
|
|
|
|
|
|L
|M
|0%
|60%
|Travel Service Operation Center <-> Passenger Digitals, Delivery Partner Digitals
|{{Yellow-Tag|YellowText=Delayed}}
|-
| colspan="25" |
|-
|-
! style="text-align:left;" |'''[[SARA.PAXPortal]]'''
! style="text-align:left;" |SARA.Core
!
!40
!
| style="text-align:center; background-color:#ADD8E6" |Dis.
! colspan="7" |
| colspan="4" style="text-align:center; background-color:#96F97B" |Dev
| style="text-align:center; background-color:#FFFFE0" |Q&A
| colspan="2" style="text-align:center; background-color:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Q&A
!
!
!
!
| colspan="6" style="text-align:center; background-color:#ADD8E6" |Discovery
!
!
| colspan="6" style="text-align:center; background-color:#96F97B" |Dev
| colspan="3" style="text-align:center; background-color:#FFFFE0" |QA
!
!
!10%
!
!
!21
!59,4%
!{{Yellow-Tag|YellowText=Delayed}} (1 week?)
|-
|-
|LH PAX Portal
|Initial definition of BE (like SWISS)
|FE & BE
|Mgmt
|Def
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|S
|100%
|✅
|-
|Full SAM process discovery
|Mgmt
|
|
|
|
| colspan="6" style="text-align:center; background-color:#FFCCCB" |Discovery
|
|
|
|
|
|
|
|
| colspan="4" |Dev
|Q&A
|
|
|
|
Line 347: Line 493:
|
|
|XL
|XL
|20%
|100%
|Interaction with [[Passenger digitals|Passenger Digital]] and [[Travel partner digitals|Travel Partner Digital]]
|✅ {{Gray-Tag|Text=Additional project phase}}
|-
|UI/UX Iteration
|MgMt
|
|
|
|
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|
|
|
|
|M
|100%
|✅ {{Gray-Tag|Text=Additional project phase}}
|-
|-
|Login for Travelagents / LH TravelID
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core App Development]]
|Mixed
|Mixed
|
|
Line 356: Line 527:
|
|
|
|
|
|
|
|
|
|
| colspan="6" |Dev
|
|
|
|
|XXL
|60%
|➡️ status update
|-
|[[Dev:SLH - TravelServiceManagementEcosystem|SLH - TravelServiceManagementEcosystem]]
|BE
|
|
|
|
Line 364: Line 552:
|
|
|
|
|Dev
|Conf
|Q&A
|
|
|
|
| colspan="6" |Dev
|
|
|
|
|
|
|
|
|M
|XL
|0%
|60%
|TravelID / Travelagent-Login
|➡️ status update
|-
|-
|Discover PAX Portal
|[[SARA.ProcessAutomationEngine]]
|FE
|BE
|
|
|
|
|
Line 393: Line 580:
|
|
| colspan="2" |Dev
| colspan="2" |Dev
| colspan="2" |Q&A
|QA
|
|
|
|
|
|
|
|XL
|M
|0%
|0%
|
|
|-
|-
! style="text-align:left;" |'''[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]'''
| colspan="25" |
|-
! style="text-align:left;" |SARA.DeliveryPartnerPortal
!8
!
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Discovery
!
!
!
!
!
!
!
!
!
!
!
!
!
!
| colspan="6" style="text-align:center; background-color:#FFCCCB" |Discovery
| style="text-align:center; background-color:#96F97B" |Dev
| colspan="5" style="text-align:center; background-color:#96F97B" |Dev
| style="text-align:center; background-color:#FFFFE0" |QA
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Q&A
!
! colspan="5" |
!
!
!
!
!20%
!3
!85,0%
!
!
|-
|-
|MOC Detailed Process Analysis {{Red-Tag|Text=not planned}}
|[[SARA.DeliveryPartnerPortal|Delivery Partner Portal]]
|Mgmt
|Mixed
|
|
| colspan="3" |Discovery
|
|
|
|
| colspan="6" |[[LHG:Unplanned Discovery Sessions|Discovery]]
|
|
|
|
Line 429: Line 628:
|
|
|
|
|Dev
|QA
|
|
|
|
|
|
|
|
|XL
|L
|80%
|85%
|{{Red-Tag|Text=main reason for delay}}
|➡️ status update
|-
| colspan="25" |
|-
! style="text-align:left;" |Interface Development
!4
!
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Discovery
! colspan="9" |
| colspan="4" style="text-align:center; background-color:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |QA
! colspan="2" |
!6
!73,3%
!
|-
|-
|SARA App Development
|Initial Definition / Discovery
|FE
|BE
|
|
| colspan="2" |Discovery
|
|
|
|
Line 448: Line 664:
|
|
|
|
| colspan="5" |Dev
|
|
| colspan="2" |Discovery
|
|
|
|
Line 456: Line 672:
|
|
|
|
|XL
|S
|0%
|100%
|
|ONERES bookings over API
|-
|-
|SARA BE / PAE
|[[LHG:ONERES Interface|Interface to ONERES]] (API bookings)
|BE
|BE
|
|
Line 472: Line 688:
|
|
|
|
| colspan="4" |Dev
| colspan="2" |Q&A
|
|
|
|
|
|
|
|
| colspan="2" |Dev
| colspan="2" |QA
|
|
|XL
|0%
|
|
|L
|60%
|{{Yellow-Tag|YellowText=Changed, Delayed}} not on critical path
|-
|-
|LH EntraID
|[[LHG:DAS Interface|Interface DAS via Kafka]]
|BE
|BE
|
|
Line 496: Line 713:
|
|
|
|
| style="text-align:center; background-color:#ADD8E6" |Conf
|
|
|
| colspan="2" |Dev
| colspan="2" |QA
|
|
|M
|80%
|{{Gray-Tag|Text=Additional work}}
|-
| colspan="25" |
|-
! style="text-align:left;" |LH Partner Creation Portal
!8
! colspan="15" |
!
| style="text-align:center; background-color:#96F97B" |Dev
| style="text-align:center; background-color:#FFFFE0" |QA
! colspan="3" |
!60%
!
|-
|[[Dev:Partner creation processes]]
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
Line 505: Line 754:
|
|
|
|
|Dev
|QA
|
|
|S
|0%
|
|
|L
|60%
|{{Green-Tag|Text=Preponed}} UI Done
InterDig automation open
|-
|-
![[SARA.DeliveryPartnerPortal]]
| colspan="25" |
!
|-
!
!Full project
!
!100
! colspan="2" |Discovery
| colspan="7" style="text-align:center; background-color:#ADD8E6" |Discovery & Dev preparations
! colspan="2" |
| colspan="7" style="text-align:center; background-color:#96F97B" |Core Dev
! colspan="3" |Discovery
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Core QA
! colspan="4" |
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Integration Testing
| colspan="2" |Dev
| style="text-align:center; background-color:#FFCCCB" |Golive
| colspan="2" |Q&A
!
!
!
!
!75,60%
!
!
|-
| colspan="25" |
|-
!Additional steps
!
!
! colspan="21" |
!
!
!20%
!
!
|-
|-
|Definition
|Full test servers in NUE with new B-Op-Infra
|MgMt
|Admin
BE
|
|
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
| colspan="3" |Discovery
|
|
|
|
Line 543: Line 801:
|
|
|
|
| colspan="2" |Deployment
|
|
|
|
Line 550: Line 809:
|M
|M
|100%
|100%
|
|✅ ➡️ status update
|-
|-
|Delivery Partner Portal
|Login&Registration Extensions for PAX & Botprotection
|Mixed
|Mixed
|
|
Line 567: Line 826:
|
|
|
|
| colspan="2" |Dev
|
| colspan="2" |Q&A
|
|
|
|
|
|
Line 574: Line 834:
|
|
|M
|M
|10%
|90%
|➡️ status update, in testing
|-
|[[LHG:ONERES Interface|Interface to ONERES]] (GAV)
|Mixed
|
|
|
|-
! style="text-align:left;" |Interface Development
!
!
!
!
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Discovery
! colspan="7" |
| colspan="4" |Dev
! colspan="2" |Q&A
! colspan="2" |
!
!15%
!
|-
|Definition / Discovery
|BE
|
|
|
|
|
|
| colspan="3" |Discovery
|
|
|
|
Line 613: Line 860:
|
|
|S
|S
|60%
|5%
|{{Yellow-Tag|YellowText=Additional work}} {{Gray-Tag|Text=Next project phase !?}}
|-
|[[LHG:Interface to SIRAX|Interface to SIRAX]]
|Mixed
|
|
|
|
|-
|ONERES
|BE
|
|
|
|
Line 631: Line 881:
|
|
|
|
| colspan="2" |Dev
| colspan="2" |Q&A
|
|
|
|
|
|
|
|
|L
|M
|0%
|0%
|LH Int Ready, Req BTeam
|{{Gray-Tag|Text=Next project phase !?}}
|-
|-
|SIRAX
|[[LHG:SHED-Connect|SCHED-Connect]] Specification
|BE
|BE
|
|
Line 658: Line 906:
|
|
|
|
| colspan="2" |Dev
|
| colspan="2" |Q&A
|
|
|
|
|
|
|S
|S
|0%
|100%
|LH Int Ready, Req BTeam
|
|-
! style="text-align:left;" |LH Partner Creation Portal
!
!
! colspan="15" |
!Dev
| colspan="2" |Q&A
!
!
!
!0%
!
|-
|-
|[[SARA.PartnerCreationPortal]]
|[[LHG:SHED-Connect|SCHED-Connect]] Implementation
|Mixed
|Mixed
|
|
Line 696: Line 933:
|
|
|
|
|Dev
| colspan="2" |Q&A
|
|
|
|
|L
|
|0%
|
|M
|20%
|
|
|-
|-
| colspan="26" |
|-
!Full project
!
!
!
!
| colspan="7" style="text-align:center; background-color:#ADD8E6" |Discovery & Dev preparations
| colspan="6" style="text-align:center; background-color:#96F97B" |Core Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Core Q&A
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Integration Testing
| style="text-align:center; background-color:#FFCCCB" |Golive
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!10
!52,5%
!
!
|}
|}


== Plannungsverlauf ==
=== Step-by-Step to success ===
 
=== 18.05.2025 Aktualisierter Projektplan ===
Plan aktualisiert mit vorläufigen Erkenntnissen der Discovery-Phase
 
* Viele Details, die mit dem 2-Tages Meeting am Start einfach nicht vermittelbar waren (Es war falsch von uns, dies einfach wegverhandeln zu lassen).
* Das PAX-Portal ist 1:1 für LH verwendbar ist (wie angenommen)'''. Kern-Fehlannahme bei der Projektplanung war:''' Das PAX-Portal backend von SWISS lässt sich für LH verwenden.
* Die unplante Discovery-Phase hat diese vielen Details-Prozesse decouvriert, die die tägliche Arbeit des MOC dominieren: Viele kleine Abhängigkeiten und Sonderprozesse, die die geplante Prozess-Automation erheblich verkomplizieren und mit den existierenden Backend-Lösung für SWISS definitiv nicht abbildbar gewesen wären.
* Wenn diese Phase nicht stattgefunden hätte, so wären viele Sachen erst unterwegs gelernt worden. Der Entwicklungsprozess wäre damit um ein vielfaches verlängert oder ganz zum Scheitern gebracht worden. Abschliessend hätte dies dann sicher dazu geführt, dass das Tool architektonisch falsch aufgesetzt gewesen wäre und/oder eine so massive Prozessänderung beim LH MOC bedeutet hätte, das das Projekt komplett gescheitert wäre.
 
* Wir haben gelernt, das bei LH bestimmte Prozesse mehr Stellen involviert sind als gedacht. Von daher haben wir durch die Discovery-Phase die Wartezeit auch bestmöglich genutzt.
 
Änderung der Aufwandsabschätzung:
 
* Entwicklungs- und Testaufwand
** Statt 5 Monate Entwicklungsaufwand nun 6
** Durchschnittlich statt 1,2 Streams nun 1,4 Streams
** Entwicklungsaufwand nun '''40% höher''' (Q&A-Kapa ist proportial erhöht)
** Steigerung der Komplexität der Prozesse, viele neue Abhängigkeiten
* Discovery- & Dokumentations-Aufwand (statt 3 Tage nun 12 Tage)
 
Frage:
 
* Wie gehen wir mit dem Mehraufwand um?
* Mehraufwand, der aus unserer Sicht unabdingbar für den Projekterfolg war und ist.


<u>Outcome</u>: Definitiver Plan mit den implikationen der discovery phase wird am 26.06. präsentiert
* Starting from '''1st of July 2025,''' the core development takes place, which should be finished by end of February (30 weeks) including internal Q&A.  There are 11 development milestones, which are scheduled. See article [[LHG:SARA Project Phase 1 - Current presentation milestones]] It is not expected, that everything runs flawlessly until then, but all building blocks should be there and just rework and bugfixing should happen from there.


=== 10.02.2025 aktualisierter Plan ===
* From '''1st of March 2026''', the full integration testing should commence and non-essential development tasks are scheduled  Acceptance tests with LHG will commence with a timeframe of roughly 10 week until the system is ready for production.  
* Goal is that from '''May 2026,''' LHG can press the start button whenever they want to.


* Added discovery sessions (Feb - May)
=== Project history & updates ===


=== 01.10.2024 initialer Projektplan ===
* [[LHG:End of June - Definitive new project plan|End of June: Definitive project plan]]
* [[LHG:Mid May updated preliminary plan|Mid of may: KORDEUS has presented an updated preliminary project plan]]
* [[LHG:Dec 2024 - project focus change|Dec 2024: Additional discovery (changed Project focus)]]
* Nov 2024: The project started at the end of 2024 and was terminated to be finished in 2025.


== See also ==
== See also ==


* [[LHG:LH SARA discovery Sessions|SARA discovery Sessions]]
* [[Dev:Internal ZUGSEIL Meetings on LHG Project Phase 1|Internal ZUGSEIL Meetings on LHG Project Phase 1]]
* [[Dev:Internal ZUGSEIL Meetings on LHG Project Phase 1|Internal ZUGSEIL Meetings on LHG Project Phase 1]]
* [[Kordeus.SARA]]
* [[Protected:Co-Innovators Area]]
* [[Protected:Co-Innovators Area]]

Latest revision as of 12:09, 19 February 2026

Phase 1 - SARA Fundamental

Current Project Plan

Dev

Focus

2024 2025 2026 Est.

Size

Dev

Progress

External Dep.

Notes

Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun
Peparatory work 4 Discovery Discovery 5 100%
Kickoff / Initially planned discovery Def S 100%
Architecture & Shared Logic Hubs Discovery Re-Discovery XL 100%
Administration tools 8 Dis. Dev Discovery Dev QA Dev QA Dev QA Dev QA 18 85,8%
Definition / Discovery Def Dev Re-Discovery L 100%
LH Admininistration Tools Mixed Dev QA L 100%
MOC Administration Tools Mixed Dev QA L 100%
SLHs (TravelCarrierDataDistribution & OperationCenterPAXExchange BE Dev QA L 100% Ticket size changed over time
Minor extensions during further discovery Mixed Dev QA S 100%
SLH - TravelCDDD

SLH - OCPAXE extensions due to feedback

Dev S 100%
Minor extensions during feedback sessions (limitations) Mixed Dev QA S 100%
Automation Engine Admin Mixed Dev Dev QA L 15% Repriorized
Passenger Portals 28 Dev QA Dev QA 11 90,9%
PAX funcationality in PAX.Portal for LH FE & BE Dev QA XL 100%
SLH - PortalUsageInteraction BE Dev L 100%
Full PAX.Portal for Discover FE Dev QA M 90%
TP-Employee features Mixed Dev Conf QA M 60% Delayed
SARA.Core 40 Dis. Discovery Dev QA 21 59,4% Delayed (1 week?)
Initial definition of BE (like SWISS) Mgmt Def S 100%
Full SAM process discovery Mgmt Discovery XL 100% Additional project phase
UI/UX Iteration MgMt Dev M 100% Additional project phase
SARA.Core App Development Mixed Dev XXL 60% ➡️ status update
SLH - TravelServiceManagementEcosystem BE Dev XL 60% ➡️ status update
SARA.ProcessAutomationEngine BE Dev QA XL 0%
SARA.DeliveryPartnerPortal 8 Discovery Dev QA 3 85,0%
Delivery Partner Portal Mixed Discovery Dev QA L 85% ➡️ status update
Interface Development 4 Discovery Dev QA 6 73,3%
Initial Definition / Discovery BE Discovery Discovery S 100% ONERES bookings over API
Interface to ONERES (API bookings) BE Dev QA L 60% Changed, Delayed not on critical path
Interface DAS via Kafka BE Dev QA M 80% Additional work
LH Partner Creation Portal 8 Dev QA 60%
Dev:Partner creation processes Mixed Dev QA L 60% Preponed UI Done

InterDig automation open

Full project 100 Discovery & Dev preparations Core Dev Core QA Integration Testing Golive 75,60%
Additional steps
Full test servers in NUE with new B-Op-Infra Admin

BE

Deployment M 100% ✅ ➡️ status update
Login&Registration Extensions for PAX & Botprotection Mixed M 90% ➡️ status update, in testing
Interface to ONERES (GAV) Mixed S 5% Additional work Next project phase !?
Interface to SIRAX Mixed M 0% Next project phase !?
SCHED-Connect Specification BE S 100%
SCHED-Connect Implementation Mixed M 20%
10 52,5%

Step-by-Step to success

  • Starting from 1st of July 2025, the core development takes place, which should be finished by end of February (30 weeks) including internal Q&A. There are 11 development milestones, which are scheduled. See article LHG:SARA Project Phase 1 - Current presentation milestones It is not expected, that everything runs flawlessly until then, but all building blocks should be there and just rework and bugfixing should happen from there.
  • From 1st of March 2026, the full integration testing should commence and non-essential development tasks are scheduled Acceptance tests with LHG will commence with a timeframe of roughly 10 week until the system is ready for production.
  • Goal is that from May 2026, LHG can press the start button whenever they want to.

Project history & updates

See also