LHG:SARA Project: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
Stefanseiler (talk | contribs)
Created page with "== 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 {| class="wikitable" ! ! rowspan="2" |Dev Focus ! rowspan="2" |Est. Size ! colspan="2" |2024 ! colspan="12" |2025 ! colspan="6" |2026 ! rowspan="2" |Est. Size ! rowspan="2" |Progress ! rowspan="2" |External Dep. Notes..."
 
Stefanseiler (talk | contribs)
 
(174 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
!Rel. Size
Focus
! rowspan="2" |Est. Size
! colspan="2" |2024
! colspan="2" |2024
! colspan="12" |2025
! colspan="12" |2025
! colspan="6" |2026
! colspan="6" |2026
! rowspan="2" |Est.
! rowspan="2" |Est-Size
Size
! rowspan="2" |Dev
! rowspan="2" |Progress
Progress
! rowspan="2" |External Dep.
! rowspan="2" |External Dep.
Notes
Notes
|-
|-
!
!
!Team
!Nov
!Nov
!Dec
!Dec
Line 42: Line 36:
!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 62:
|
|
|
|
!
|
|
|
|
Line 67: Line 72:
|
|
|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.
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
! colspan="3" |
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Discovery
| 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
!Dev
! colspan="2" |QA
!
!
!
!
!
!18
!
!85,8%
!
!
!
!
!80%
!
!
|-
|-
|[[Carrier Admininistration Tools]]
|Definition / Discovery
|Mixed
|
|Def
| colspan="3" |Dev
| colspan="3" style="text-align:center; background-color:#FFCCCB" |Re-Discovery
|
|
|
|
|
|
|
Line 99: Line 134:
|
|
|
|
| colspan="3" |Dev
|Q&A
|
|
|
|
|
|
|L
|100%
|✅
|-
|[[Carrier Admininistration Tools|LH Admininistration Tools]]
|Mixed
|
|
|
|
Line 110: Line 149:
|
|
|
|
| colspan="3" |Dev
|QA
|
|
|L
|80%
|
|
|-
|[[Travel Service Operation Center Administration Tools]]
|Mixed
|
|
|
|
Line 125: Line 161:
|
|
|
|
| colspan="3" |Dev
|L
|Q&A
|100%
|✅
|-
|[[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|Mixed
|
|
|
|
Line 134: Line 174:
|
|
|
|
| colspan="3" |Dev
|QA
|
|
|
|
|XL
|40%
|
|
|-
|Extensions during further discovery
|Mixed
|
|
|
|
Line 148: Line 185:
|
|
|
|
|L
|100%
|✅
|-
|SLHs ([[Dev:SLH - TravelCarrierDataDistribution|TravelCarrierDataDistribution]] & OperationCenterPAXExchange
|BE
|
|
|
|
Line 154: Line 197:
|
|
|
|
|Dev
|
|Q&A
|
| colspan="2" |Dev
|QA
|
|
|
|
Line 163: Line 208:
|
|
|
|
|S
|
|
|
|
|L
|100%
|✅
|-
|-
! style="text-align:left;" |Architecture & Shared Logic Hubs
|Minor extensions during further discovery
!
|Mixed
!
!
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Discovery
!
!
!
| colspan="2" style="text-align:center; background-color:#FFCCCB" |Discovery
| colspan="4" style="text-align:center; background-color:#96F97B" |Dev
!
!
!
!
!
!
!
!
!
!30%
!
|-
|Finishing Documentation & Inter-Digital Architecture
|Arch
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
Line 203: Line 226:
|
|
|
|
| colspan="2" |Dev
|QA
|
|
|
|
Line 210: Line 235:
|
|
|
|
|XL
|S
|95%
|100%
|DB-Model, Process Aut. Engine (PAE)
|
|-
|-
|[[Dev:SLH - TravelCarrierDataDistribution|SLH - TravelCarrierDataDistribution]]
|SLH - TravelCDDD
|BE
SLH - OCPAXE extensions due to feedback
|
|
|
|
|
Line 225: Line 251:
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|
|
|Dev
|
|
|
|
Line 236: Line 262:
|
|
|
|
|M
|S
|0%
|100%
|[[Carrier digital]] <--> [[PAX Portal digitals|PAX Portal Digitals]], [[Travel assistance service operation center digitals|Travel Service Operation Center Digitals]]
|
|-
|-
|[[Dev:SLH - PortalUsageInteraction|SLH - PortalUsageInteraction]]
|Minor extensions during feedback sessions (limitations)
|BE
|Mixed
|
|
|
|
|
Line 252: Line 277:
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|
|
|Dev
|QA
|
|
|
|
Line 262: Line 288:
|
|
|
|
|L
|S
|0%
|100%
|PAX Portal Digitals <-> Passenger Digitals, Travel Partner Digitals
|
|-
|-
|[[Dev:SLH - TravelServiceManagementEcosystem|SLH - TravelServiceManagementEcosystem]]
|Automation Engine Admin
|BE
|Mixed
|
|
|
|
|
Line 277: Line 302:
|
|
|
|
|
|
| colspan="2" |Dev
|
|
|
|
Line 285: Line 307:
|
|
|
|
|Dev
|
|
|Dev
| colspan="2" |QA
|
|
|
|
|L
|L
|0%
|45%
|Travel Service Operation Center <-> Passenger Digitals, Delivery Partner Digitals
|{{Yellow-Tag|YellowText=Repriorized}}
|-
|-
! style="text-align:left;" |'''[[SARA.PAXPortal]]'''
| colspan="25" |
!
|-
!
! style="text-align:left;" |Passenger Portals
!28
! colspan="7" |
! colspan="7" |
| colspan="4" style="text-align:center; background-color:#96F97B" |Dev
| colspan="4" style="text-align:center; background-color:#96F97B" |Dev
| style="text-align:center; background-color:#FFFFE0" |Q&A
| 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:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Q&A
| colspan="2" style="text-align:center; background-color:#FFFFE0" |QA
!
!
!
!
!
!
!
!
!
!10%
!11
!96,4%
!
!
|-
|-
|LH PAX Portal
|[[PAX.Portal|PAX funcationality in PAX.Portal for LH]]
|FE & BE
|FE & BE
|
|
|
|
|
Line 319: Line 344:
|
|
| colspan="4" |Dev
| colspan="4" |Dev
|Q&A
|QA
|
|
|
|
Line 329: Line 354:
|
|
|XL
|XL
|20%
|100%  
|Interaction with [[Passenger digitals|Passenger Digital]] and [[Travel partner digitals|Travel Partner Digital]]
|
|-
|-
|Login for Travelagents / LH TravelID
|[[Dev:SLH - PortalUsageInteraction|SLH - PortalUsageInteraction]]
|Mixed
|BE
|
|
|
|
Line 343: Line 368:
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|Dev
|Conf
|Q&A
|
|
|
|
Line 355: Line 378:
|
|
|
|
|M
|L
|0%
|100%
|TravelID / Travelagent-Login
|
|-
|-
|Discover PAX Portal
|[[PAX.Portal|Full PAX.Portal for Discover]]
|FE
|FE
|
|
|
|
|
Line 375: Line 397:
|
|
| colspan="2" |Dev
| colspan="2" |Dev
| colspan="2" |Q&A
| colspan="2" |QA
|
|
|
|
Line 381: Line 403:
|
|
|M
|M
|0%
|90%
|{{Yellow-Tag|YellowText=Repriorized}}
|-
|[[Dev:PAX.Portal feature tree|TP-Employee features]]
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|Dev
|Conf
|QA
|
|
|
|
|M
|90%
|{{Yellow-Tag|YellowText=Repriorized}}
|-
|-
! style="text-align:left;" |'''[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]'''
| colspan="25" |
|-
! style="text-align:left;" |SARA.Core
!40
| style="text-align:center; background-color:#ADD8E6" |Dis.
!
!
| 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
!
!
!
!
| colspan="6" style="text-align:center; background-color:#FFCCCB" |Discovery
!20
| colspan="5" style="text-align:center; background-color:#96F97B" |Dev
!98,5%
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Q&A
!{{Yellow-Tag|YellowText=Delayed}}
! colspan="5" |
!
!20%
!
|-
|-
|MOC Detailed Process Analysis {{Red-Tag|Text=not planned}}
|Initial definition of BE (like SWISS)
|Mgmt
|Mgmt
|Def
|
|
|
|
|
|
|
|
| colspan="6" |[[LHG:Unplanned Discovery Sessions|Discovery]]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|S
|100%
|✅
|-
|Full SAM process discovery
|Mgmt
|
|
| colspan="6" style="text-align:center; background-color:#FFCCCB" |Discovery
|
|
|
|
Line 416: Line 492:
|
|
|XL
|XL
|80%
|100%
|{{Red-Tag|Text=main reason for delay}}
|
|-
|-
|SARA App Development
|UI/UX Iteration
|FE
|MgMt
|
|
|
|
Line 429: Line 505:
|
|
|
|
| colspan="2" |Dev
|
|
| colspan="4" |Dev
|
|
|
|
Line 439: Line 515:
|
|
|
|
|XL
|0%
|
|
|M
|100%
|✅
|-
|-
|SARA BE / PAE
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core App Development]]
|BE
|Mixed
|
|
|
|
|
|
|
|
|
Line 450: Line 532:
|
|
|
|
| colspan="6" |Dev
|
|
|
|
|
|XXL
|100%
|✅
|-
|[[Dev:SLH - TravelServiceManagementEcosystem|SLH - TravelServiceManagementEcosystem]]
|BE
|
|
|
|
|
|
|
|
| colspan="4" |Dev
| colspan="2" |Q&A
|
|
|
|
Line 462: Line 552:
|
|
|
|
|XL
|0%
|
|
|-
| colspan="6" |Dev
|LH EntraID
|BE
|
|
|
|
|
|
|
|
|XL
|100%
|✅
|-
|[[SARA.ProcessAutomationEngine]]
|BE
|
|
|
|
Line 479: Line 571:
|
|
|
|
| style="text-align:center; background-color:#ADD8E6" |Conf
|
|
|
|
Line 487: Line 578:
|
|
|
|
| colspan="2" |Dev
|QA
|
|
|
|
|S
|0%
|
|
|XL
|90%
|➡️ status update
|-
|-
![[SARA.DeliveryPartnerPortal]]
| colspan="25" |
|-
! style="text-align:left;" |SARA.DeliveryPartnerPortal
!8
!
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Discovery
!
!
!
!
!
!
!
!
!
!
!
!
! colspan="2" |Discovery
!
! colspan="2" |
| style="text-align:center; background-color:#96F97B" |Dev
! colspan="3" |Discovery
| style="text-align:center; background-color:#FFFFE0" |QA
! colspan="4" |
| colspan="2" |Dev
| colspan="2" |Q&A
!
!
!
!
!
!
!
!
!3
!100%
!
|-
|[[SARA.DeliveryPartnerPortal|Delivery Partner Portal]]
|Mixed
|
| colspan="3" |Discovery
|
|
|
|
|
|
|
|
|
|
|Dev
|QA
|
|
|
|
|L
|100%
|
|-
| colspan="25" |
|-
! style="text-align:left;" |Interface Development
!4
!
!
!20%
| 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
!96,7%
!
!
|-
|-
|Definition
|Initial Definition / Discovery
|MgMt
|BE
|
| colspan="2" |Discovery
|
|
|
|
|
|
|
|
|
|
|
Line 518: Line 667:
|
|
|
|
| colspan="3" |Discovery
|
|
|
|
|S
|100%
|ONERES bookings over API
|-
|[[LHG:ONERES Interface|Interface to ONERES]] (API bookings)
|BE
|
|
|
|
|
|
|
|
Line 529: Line 691:
|
|
|
|
| colspan="2" |Dev
| colspan="2" |QA
|
|
|
|
|M
|L
|100%
|100%
|➡️ status update
|-
|[[LHG:DAS Interface|Interface DAS via Kafka]]
|BE
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| colspan="2" |Dev
| colspan="2" |QA
|
|
|M
|95%
|➡️ status update
|-
| colspan="25" |
|-
|-
|Delivery Partner Portal
! 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="2" |
!8
!100,0%
!
|-
|[[Dev:Partner creation processes]]
|Mixed
|Mixed
|
|
Line 550: Line 751:
|
|
|
|
| colspan="2" |Dev
| colspan="2" |Q&A
|
|
|
|
|
|
|Dev
|QA
|
|
|M
|10%
|
|
|L
|100%
|✅
|-
|-
! style="text-align:left;" |Interface Development
| colspan="25" |
|-
!Full project (100%)
!100
| colspan="7" style="text-align:center; background-color:#ADD8E6" |Discovery & Dev preparations
| colspan="7" style="text-align:center; background-color:#96F97B" |Core Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Core QA
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Int. Testing
| style="text-align:center; background-color:#FFCCCB" |Golive
!
!
!
!
!97,1%
!
!
|-
| colspan="25" |
|-
!{{Yellow-Tag|YellowText=Additional work}}
!
!
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Discovery
! colspan="20" |
! colspan="7" |
!18 {{Yellow-Tag|YellowText=+1}}
| colspan="4" |Dev
! colspan="2" |Q&A
! colspan="2" |
!
!
!15%
!
!
|-
|-
|Definition / Discovery
|Full test servers in NUE with new B-Op-Infra
|Admin
BE
|
|
|
|
|
|
|
|
|
|
|
|
|
| colspan="2" |Deployment
|
|
|
|
|
|M
|100%
|✅
|-
|Login&Registration Extensions for PAX & Botprotection
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|M
|100%
|✅
|-
|[[LHG:ONERES Interface|Interface to ONERES]] (GAV) Specification
|BE
|BE
|
|
|
|
|
|
| colspan="3" |Discovery
|
|
|
|
|
|
Line 596: Line 861:
|
|
|S
|S
|60%
|100%
|✅
|-
|[[LHG:ONERES Interface|Interface to ONERES]] (GAV) Implementation
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|S
|100%
|✅
|-
|-
|ONERES
|[[LHG:ONERES Interface|Interface to ONERES]] (GAV) SARA Implementation
|BE
|Mixed
|
|
|
|
|
|
|
Line 614: Line 908:
|
|
|
|
| colspan="2" |Dev
| colspan="2" |Q&A
|
|
|
|
|
|
|
|
|L
|S
|0%
|100%
|LH Int Ready, Req BTeam
|➡️ status update
|-
|-
|SIRAX
|[[LHG:SHED-Connect|SCHED-Connect]] Specification
|BE
|BE
|
|
Line 641: Line 933:
|
|
|
|
| colspan="2" |Dev
|
| colspan="2" |Q&A
|
|
|
|
|
|
|S
|S
|0%
|100%
|LH Int Ready, Req BTeam
|
|-
|-
! style="text-align:left;" |LH Partner Creation Portal
|[[LHG:SHED-Connect|SCHED-Connect]] Implementation
!
|Mixed
!
|
! colspan="15" |
|
!Dev
|
| colspan="2" |Q&A
|
!
|
!
|
!
|
!0%
|
!
|
|
|
|
|
|
|
|
|
|
|
|
|M
|100%
|✅
|-
|-
|Instance deployment @ [[SARA.PartnerCreationPortal]]
|[[LHG:SHED-Connect|SCHED-Connect]] SARA Implementation
|Mixed
|Mixed
|
|
Line 679: Line 986:
|
|
|
|
|Dev
| colspan="2" |Q&A
|
|
|
|
|
|
|0%
|
|
|M
|100%
|➡️ status update
|-
|Communication templates and implementation
|Mgmt, mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|DEV & QA
|
|
|M
|100%
|✅
|-
|Task templates and implementation
|Mgmt, mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|DEV & QA
|
|
|S
|100%
|✅
|-
|Document templates and implementation
|Mgmt, mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|DEV & QA
|
|
|S
|100%
|✅
|-
|-
| colspan="26" |
|Delivery Partner Portal - additional service details, multiple services, extensions for empty legs
|Mgmt, mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|DEV & QA
|
|M
|100&
|✅
|-
|-
!Full project
!Performed work
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
| 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
!
!
!
!
!
!
!87,2%
!
!
|}
|}


== Plannungsverlauf ==
=== Step-by-Step to success ===
 
=== 22.06. bis 24.06. Finalization of committed project plan with LHG ===
 
=== 09.06. bis 20.06. Rework of administration tools database structure ===
 
* Aufteilung der Admin-Tools auf [[Carrier Admininistration Tools]] und [[Travel Service Operation Center Administration Tools]]
 
=== 20.05.2025: Review mit Entwicklungsteam ===
 
* see [[Dev:Internal meeting notes with team (LH-Project)|internal meetings (LH-Project)]]
 
=== 18.05.2025 Aktualisierter Projektplan ===
Plan aktualisiert mit 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.
 
=== 10.02.2025 aktualisierter Plan ===
 
* Added discovery sessions (Feb - May)


=== 01.10.2024 initialer Projektplan ===
* 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.


* Add here
* 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 to reach Go-Live readiness in '''May 2026'''


== Related articles ==
=== Project history & updates ===


* [[Kordeus.SARA]]
* [[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]]
* [[Protected:Co-Innovators Area]]
* [[Protected:Co-Innovators Area]]

Latest revision as of 11:49, 11 June 2026

Phase 1 - SARA Fundamental

Current Project Plan

Rel. Size 2024 2025 2026 Est-Size Dev

Progress

External Dep.

Notes

Team 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%
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 45% Repriorized
Passenger Portals 28 Dev QA Dev QA 11 96,4%
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% Repriorized
TP-Employee features Mixed Dev Conf QA M 90% Repriorized
SARA.Core 40 Dis. Discovery Dev QA 20 98,5% Delayed
Initial definition of BE (like SWISS) Mgmt Def S 100%
Full SAM process discovery Mgmt Discovery XL 100%
UI/UX Iteration MgMt Dev M 100%
SARA.Core App Development Mixed Dev XXL 100%
SLH - TravelServiceManagementEcosystem BE Dev XL 100%
SARA.ProcessAutomationEngine BE Dev QA XL 90% ➡️ status update
SARA.DeliveryPartnerPortal 8 Discovery Dev QA 3 100%
Delivery Partner Portal Mixed Discovery Dev QA L 100%
Interface Development 4 Discovery Dev QA 6 96,7%
Initial Definition / Discovery BE Discovery Discovery S 100% ONERES bookings over API
Interface to ONERES (API bookings) BE Dev QA L 100% ➡️ status update
Interface DAS via Kafka BE Dev QA M 95% ➡️ status update
LH Partner Creation Portal 8 Dev QA 8 100,0%
Dev:Partner creation processes Mixed Dev QA L 100%
Full project (100%) 100 Discovery & Dev preparations Core Dev Core QA Int. Testing Golive 97,1%
Additional work 18 +1
Full test servers in NUE with new B-Op-Infra Admin

BE

Deployment M 100%
Login&Registration Extensions for PAX & Botprotection Mixed M 100%
Interface to ONERES (GAV) Specification BE S 100%
Interface to ONERES (GAV) Implementation Mixed S 100%
Interface to ONERES (GAV) SARA Implementation Mixed S 100% ➡️ status update
SCHED-Connect Specification BE S 100%
SCHED-Connect Implementation Mixed M 100%
SCHED-Connect SARA Implementation Mixed M 100% ➡️ status update
Communication templates and implementation Mgmt, mixed DEV & QA M 100%
Task templates and implementation Mgmt, mixed DEV & QA S 100%
Document templates and implementation Mgmt, mixed DEV & QA S 100%
Delivery Partner Portal - additional service details, multiple services, extensions for empty legs Mgmt, mixed DEV & QA M 100&
Performed work 87,2%

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 to reach Go-Live readiness in May 2026

Project history & updates

See also