LHG:SARA Project: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
Stefanseiler (talk | contribs)
No edit summary
Stefanseiler (talk | contribs)
 
(128 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Phase 1 - SARA Fundamental ==
== Phase 1 - SARA Fundamental ==
=== 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 10: 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 35: 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" |
!
!100%
|
|-
|-
|Kickoff / Initially planned discovery
|Kickoff / Initially planned discovery
|
|
| Def
|
|
| style="text-align:center; background-color:#ADD8E6" |Def
|
|
|
|
Line 49: Line 63:
|
|
|
|
!
|
|
|
|
Line 60: 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.
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Discovery
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
| 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
!QA
!Dev
! colspan="2" |QA
!
!
!
!
| style="text-align:center; background-color:#96F97B" |
| colspan="3" |Dev
! colspan="2" |
| colspan="3" style="text-align:center; background-color:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Q&A
!Dev
!Q&A
! colspan="7" |
!
!
!70%
!85,0%
!
!
|-
|-
|Definition / Discovery
|Definition / Discovery
|
|
|
|Def
|Def
|
| colspan="3" |Dev
|
| colspan="3" style="text-align:center; background-color:#FFCCCB" |Re-Discovery
|
| colspan="3" |Discovery
|
|
|
|
|
Line 100: Line 138:
|
|
|
|
|L
|100%
|100%
|
|
|-
|-
|[[Carrier Admininistration Tools|LH Admininistration Tools]]
|[[Carrier Admininistration Tools|LH Admininistration Tools]]
|Mixed
|Mixed
|
|
|
|
|
Line 113: Line 151:
|
|
| colspan="3" |Dev
| colspan="3" |Dev
|Q&A
|QA
|
|
|
|
Line 125: Line 163:
|
|
|L
|L
|80%
|100%
|
|
|-
|-
|[[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|[[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|Mixed
|Mixed
|
|
|
|
|
Line 139: Line 176:
|
|
| colspan="3" |Dev
| colspan="3" |Dev
|Q&A
|QA
|
|
|
|
Line 149: Line 186:
|
|
|
|
|XL
|L
|40%
|100%
|
|
|-
|-
|Minor extensions during further discovery
|SLHs ([[Dev:SLH - TravelCarrierDataDistribution|TravelCarrierDataDistribution]] & OperationCenterPAXExchange
|Mixed
|BE
|
|
|
|
Line 163: Line 200:
|
|
|
|
| colspan="2" |Dev
|QA
|
|
|
|
|
|
|
|
|Dev
|Q&A
|
|
|
|
Line 174: Line 211:
|
|
|
|
|
|L
|
|100%
|S
|✅ {{Gray-Tag|Text=Ticket size changed over time}}
|0%
|
|-
|-
! 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="5" style="text-align:center; background-color:#96F97B" |Dev
!
!
!
!
!
!
!
!
!30%
!
|-
|Finishing Documentation & Inter-Digital Architecture
|Arch
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
Line 215: Line 227:
|
|
|
|
| colspan="2" |Dev
|QA
|
|
|
|
Line 222: Line 236:
|
|
|
|
|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 237: Line 252:
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|
|
|Dev
|
|
|
|
Line 248: Line 263:
|
|
|
|
|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 264: Line 279:
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|Dev
|QA
|
|
|
|
Line 273: Line 289:
|
|
|
|
|
|S
|L
|100%
|0%
|
|PAX Portal Digitals <-> Passenger Digitals, Travel Partner Digitals
|-
|-
|[[Dev:SLH - TravelServiceManagementEcosystem|SLH - TravelServiceManagementEcosystem]]
|Automation Engine Admin
|BE
|Mixed
|
|
|
|
Line 289: Line 304:
|
|
|
|
|
|
| colspan="3" |Dev
|
|
|
|
|
|
|
|
|Dev
|
|
|Dev
| colspan="2" |QA
|
|
|
|
|L
|L
|0%
|15%
|Travel Service Operation Center <-> Passenger Digitals, Delivery Partner Digitals
|{{Yellow-Tag|YellowText=Repriorized}}
|-
| colspan="25" |
|-
|-
! style="text-align:left;" |'''[[SARA.PAXPortal]]'''
! 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
!
!
!
!
Line 316: Line 332:
!
!
!
!
!10%
!90,9%
!
!
|-
|-
|LH PAX Portal
|[[PAX.Portal|PAX funcationality in PAX.Portal for LH]]
|FE & BE
|FE & BE
|
|
|
|
|
Line 330: Line 345:
|
|
| colspan="4" |Dev
| colspan="4" |Dev
|Q&A
|QA
|
|
|
|
Line 340: Line 355:
|
|
|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 354: Line 369:
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|Dev
|Conf
|Q&A
|
|
|
|
Line 366: Line 379:
|
|
|
|
|M
|L
|0%
|100%
|TravelID / Travelagent-Login
|
|-
|-
|Discover PAX Portal
|[[PAX.Portal|Full PAX.Portal for Discover]]
|FE
|FE
|
|
|
|
|
Line 386: Line 398:
|
|
| colspan="2" |Dev
| colspan="2" |Dev
| colspan="2" |Q&A
| colspan="2" |QA
|
|
|
|
Line 392: Line 404:
|
|
|M
|M
|0%
|90%
|
|-
|[[Dev:PAX.Portal feature tree|TP-Employee features]]
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|Dev
|Conf
|QA
|
|
|
|
|
|M
|60%
|{{Yellow-Tag|YellowText=Delayed}}
|-
|-
! 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
| colspan="5" style="text-align:center; background-color:#96F97B" |Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Q&A
! colspan="5" |
!
!
!20%
!
!
!54,0%
!{{Yellow-Tag|YellowText=Delayed}} (2 weeks?)
|-
|-
|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]]
|
|
|
|
Line 426: Line 469:
|
|
|
|
|XL
|80%
|{{Red-Tag|Text=main reason for delay}}
|-
|SARA App Development
|FE/BE
|
|
|
|
|S
|100%
|✅
|-
|Full SAM process discovery
|Mgmt
|
|
|
|
| colspan="6" style="text-align:center; background-color:#FFCCCB" |Discovery
|
|
|
|
Line 441: Line 485:
|
|
|
|
| colspan="5" |Dev
|
|
|
|
Line 450: Line 493:
|
|
|XL
|XL
|0%
|100%
|✅ {{Gray-Tag|Text=Additional project phase}}
|-
|UI/UX Iteration
|MgMt
|
|
|
|-
|[[SARA.ProcessAutomationEngine]]
|BE
|
|
|
|
Line 461: Line 506:
|
|
|
|
| colspan="2" |Dev
|
|
|
|
|
|
|
|
| colspan="4" |Dev
| colspan="2" |Q&A
|
|
|
|
Line 472: Line 516:
|
|
|
|
|XL
|0%
|
|
|M
|100%
|✅ {{Gray-Tag|Text=Additional project phase}}
|-
|-
|LH EntraID
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core App Development]]
|BE
|Mixed
|
|
|
|
|
|
|
|
|
Line 483: Line 533:
|
|
|
|
| colspan="6" |Dev
|
|
|
|
|
|
|
|
|XXL
|40%
|status update
|-
|[[Dev:SLH - TravelServiceManagementEcosystem|SLH - TravelServiceManagementEcosystem]]
|BE
|
|
|
|
| style="text-align:center; background-color:#ADD8E6" |Conf
|
|
|
|
Line 496: Line 552:
|
|
|
|
|
|
| colspan="6" |Dev
|
|
|
|
|
|
|S
|0%
|
|
|XL
|45%
|status update
|-
|-
![[SARA.DeliveryPartnerPortal]]
|[[SARA.ProcessAutomationEngine]]
!
|BE
!
!
! colspan="2" |Discovery
! colspan="2" |
! colspan="3" |Discovery
! colspan="4" |
| colspan="2" |Dev
| colspan="2" |Q&A
!
!
!
!
!
!20%
!
|-
|Definition
|MgMt
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
| colspan="3" |Discovery
|
|
|
|
Line 539: Line 579:
|
|
|
|
| colspan="2" |Dev
|QA
|
|
|
|
|M
|100%
|
|
|XL
|0%
|{{Yellow-Tag|YellowText=Ticket size changed}}
|-
| colspan="25" |
|-
! style="text-align:left;" |SARA.DeliveryPartnerPortal
!8
!
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Discovery
!
!
!
!
!
!
!
!
!
!
| style="text-align:center; background-color:#96F97B" |Dev
| style="text-align:center; background-color:#FFFFE0" |QA
!
!
!
!
!
!25,0%
!
|-
|-
|Delivery Partner Portal
|[[SARA.DeliveryPartnerPortal|Delivery Partner Portal]]
|Mixed
|Mixed
|
|
| colspan="3" |Discovery
|
|
|
|
Line 558: Line 628:
|
|
|
|
|
|Dev
|
|QA
| colspan="2" |Dev
| colspan="2" |Q&A
|
|
|
|
Line 567: Line 635:
|
|
|M
|M
|10%
|25%
|
|status update
|-
| colspan="25" |
|-
|-
! style="text-align:left;" |Interface Development
! 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="3" style="text-align:center; background-color:#ADD8E6" |Discovery
| colspan="2" style="text-align:center; background-color:#FFFFE0" |QA
! colspan="7" |
| colspan="4" |Dev
! colspan="2" |Q&A
! colspan="2" |
! colspan="2" |
!
!
!15%
!43,3%
!
!
|-
|-
|Definition / Discovery
|Initial Definition / Discovery
|BE
|BE
|
|
|
| colspan="2" |Discovery
|
| colspan="3" |Discovery
|
|
|
|
Line 599: Line 665:
|
|
|
|
| colspan="2" |Discovery
|
|
|
|
Line 606: Line 673:
|
|
|S
|S
|60%
|100%
|
|ONERES bookings over API
|-
|-
|ONERES
|[[LHG:ONERES Interface|Interface to ONERES]] (API bookings)
|BE
|BE
|
|
|
|
|
Line 625: Line 693:
|
|
| colspan="2" |Dev
| colspan="2" |Dev
| colspan="2" |Q&A
| colspan="2" |QA
|
|
|
|
|
|
|L
|L
|0%
|40%
|LH Int Ready, Req BTeam
|{{Yellow-Tag|YellowText=Delayed}} not on critical path
|-
|-
|SIRAX
|[[LHG:DAS Interface|Interface DAS via Kafka]]
|BE
|BE
|
|
|
|
|
Line 652: Line 717:
|
|
| colspan="2" |Dev
| colspan="2" |Dev
| colspan="2" |Q&A
| colspan="2" |QA
|
|
|
|
|S
|M
|0%
|20%
|LH Int Ready, Req BTeam
|{{Gray-Tag|Text=Additional work}}
|-
| colspan="25" |
|-
|-
! style="text-align:left;" |LH Partner Creation Portal
! style="text-align:left;" |LH Partner Creation Portal
!
!8
!
! colspan="15" |
! colspan="15" |
!Dev
| colspan="2" |Q&A
!
!
!
!
| style="text-align:center; background-color:#96F97B" |Dev
!0%
| style="text-align:center; background-color:#FFFFE0" |QA
! colspan="3" |
!20%
!
!
|-
|-
|[[SARA.PartnerCreationPortal]]
|[[Dev:Partner creation processes]]
|Mixed
|Mixed
|
|
Line 690: Line 755:
|
|
|Dev
|Dev
| colspan="2" |Q&A
|QA
|
|
|
|
|L
|L
|0%
|20%
|
|{{Green-Tag|Text=Preponed}}  (Add capacity)
|-
|-
| colspan="26" |
| colspan="25" |
|-
|-
!Full project
!Full project
!
!100
!
| colspan="7" style="text-align:center; background-color:#ADD8E6" |Discovery & Dev preparations
| colspan="7" style="text-align:center; background-color:#ADD8E6" |Discovery & Dev preparations
| colspan="6" style="text-align:center; background-color:#96F97B" |Core Dev
| colspan="7" style="text-align:center; background-color:#96F97B" |Core Dev
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Core Q&A
| colspan="2" style="text-align:center; background-color:#FFFFE0" |Core QA
| colspan="3" style="text-align:center; background-color:#ADD8E6" |Integration Testing
| colspan="2" style="text-align:center; background-color:#ADD8E6" |Integration Testing
| style="text-align:center; background-color:#FFCCCB" |Golive
| style="text-align:center; background-color:#FFCCCB" |Golive
!
!
!
!
!59,2%
!
|-
| colspan="25" |
|-
!Additional steps
!
! colspan="21" |
!
!
!
!
|}
=== Milestones ===
<u>Phase 1.1: Get a non MEDA-Case up and running (SVAN)</u>
{| class="wikitable"
!No
!Date
!Goal
!Focus
!Test plan
|-
|-
|1.1
|Full test servers in NUE with new B-Op-Infra
|Admin
BE
|
|
|
|
|
|
|
|
|
|
|Presentation of LH and MOC administration tools, definition of preparatory work
| [[Carrier Admininistration Tools|Core Admininistration Tools]], [[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|
|
|
|
|
| colspan="2" |Deployment
|
|
|
|
|
|M
|80%
|06.01.2026 - new
|-
|-
|1.2
|Login&Registration Extensions for PAX & Botprotection
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|LH PAX Portal visible with SVAN service and a couple of other simple services. Ability to create a request as PAX
|[[SARA.PAXPortal]]
|
|
|
|
|M
|?
|{{Yellow-Tag|YellowText=Additional work}}, Spec done 27.11.
|-
|-
|1.3
|[[LHG:ONERES Interface|Interface to ONERES]] (GAV)
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|Create SVAN case on LH PAX Portal (US Case), Tranfered & Visible in new SARA
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.PAXPortal]], [[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]
|
|
|
|S
|5%
|{{Yellow-Tag|YellowText=Additional work}} {{Gray-Tag|Text=Next project phase !?}}
|-
|-
|1.4
|[[LHG:Interface to SIRAX|Interface to SIRAX]]
|Mixed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|SARA: PAX request for more information by communication template (EU Case), PAX delivers info, Processual approval in SARA, automatic Fit-To-Fly prepared, review and send out
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.PAXPortal]], [[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]
|
|
|M
|0%
|{{Gray-Tag|Text=Next project phase !?}}
|-
|-
|1.5
|[[LHG:SHED-Connect|SCHED-Connect]] Specification
|
|
|
|
|SARA: Manual creation case (SVAN)
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]
|
|
|-
|1.6
|
|
|Cover all other simple NON-MEDA cases (information service communication, general inquiries)
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.PAXPortal]], [[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]
|
|
|}
<u>Phase 1.2. Increase PWD complexity (Wheelchair / NON-MEDA)</u>
{| class="wikitable"
!No
!Date
!Goal
!Focus
!Test plan
|-
|2.1
|
|
|Wheelchair on PAX portal (non MEDA), Simple flow
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.PAXPortal]], [[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]
|
|
|-
|2.2
|
|
|Wheelchair with Intermodal (non MEDA), Some communication with PAX over SARA and Portal
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.PAXPortal]], [[SARA.Core (Special Assistance Request Management Suite)|SARA.Core]]
|
|
|-
|2.3.
|
|
|Travel Partner group request on Portal,
|
|
|
|
|}
Phase 1.3. Simple MEDA case (Sitting Case)
{| class="wikitable"
!No
!Date
!Goal
!Focus
!Test plan
|-
|1.1
|
|
|Presentation of LH and MOC administration tools, definition of preparatory work
| [[Carrier Admininistration Tools|Core Admininistration Tools]], [[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|
|
|}
Phase 1.4. POXY
{| class="wikitable"
!No
!Date
!Goal
!Focus
!Test plan
|-
|1.1
|
|
|Presentation of LH and MOC administration tools, definition of preparatory work
| [[Carrier Admininistration Tools|Core Admininistration Tools]], [[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|
|
|}
Phase 1.5. STRETCHER
{| class="wikitable"
!No
!Date
!Goal
!Focus
!Test plan
|-
|1.1
|
|
|Presentation of LH and MOC administration tools, definition of preparatory work
| [[Carrier Admininistration Tools|Core Admininistration Tools]], [[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|
|
|}
Phase 1.6. STRETCHER AND WENOLL
{| class="wikitable"
!No
!Date
!Goal
!Focus
!Test plan
|-
|1.1
|
|
|Presentation of LH and MOC administration tools, definition of preparatory work
| [[Carrier Admininistration Tools|Core Admininistration Tools]], [[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|
|
|}
|S
Phase 1.6. Billing & Reporting
{| class="wikitable"
!No
!Date
!Goal
!Focus
!Test plan
|-
|1.1
|
|
|Presentation of LH and MOC administration tools, definition of preparatory work
| [[Carrier Admininistration Tools|Core Admininistration Tools]], [[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|
|
|-
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!8
!20,6%
!
|}
|}


== 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 20:47, 7 January 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 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 85,0%
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 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 54,0% Delayed (2 weeks?)
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 40% status update
SLH - TravelServiceManagementEcosystem BE Dev XL 45% status update
SARA.ProcessAutomationEngine BE Dev QA XL 0% Ticket size changed
SARA.DeliveryPartnerPortal 8 Discovery Dev QA 25,0%
Delivery Partner Portal Mixed Discovery Dev QA M 25% status update
Interface Development 4 Discovery Dev QA 43,3%
Initial Definition / Discovery BE Discovery Discovery S 100% ONERES bookings over API
Interface to ONERES (API bookings) BE Dev QA L 40% Delayed not on critical path
Interface DAS via Kafka BE Dev QA M 20% Additional work
LH Partner Creation Portal 8 Dev QA 20%
Dev:Partner creation processes Mixed Dev QA L 20% Preponed (Add capacity)
Full project 100 Discovery & Dev preparations Core Dev Core QA Integration Testing Golive 59,2%
Additional steps
Full test servers in NUE with new B-Op-Infra Admin

BE

Deployment M 80% 06.01.2026 - new
Login&Registration Extensions for PAX & Botprotection Mixed M ? Additional work, Spec done 27.11.
Interface to ONERES (GAV) Mixed S 5% Additional work Next project phase !?
Interface to SIRAX Mixed M 0% Next project phase !?
SCHED-Connect Specification S
8 20,6%

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