LHG:SARA Project: Difference between revisions

From Kordeus Wiki
Jump to navigation Jump to search
← Older editNewer edit →
VisualWikitext
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
Stefanseiler (talk | contribs)
Bureaucrats, dev-team, developer, Interface administrators, iroc-team, Suppressors, Administrators, yousee-team
1,381 edits
No edit summary
Line 103: Line 103:
|
|
|-
|-
|[[Carrier Admininistration Tools]]
|[[Carrier Admininistration Tools|LH Admininistration Tools]]
|Mixed
|Mixed
|
|
Line 128: Line 128:
|
|
|-
|-
|[[Travel Service Operation Center Administration Tools]]
|[[Travel Service Operation Center Administration Tools|MOC Administration Tools]]
|Mixed
|Mixed
|
|
Line 712: Line 712:
!
!
|}
|}
Milestones:
 
=== Milestones ===
<u>Phase 1.1: Get a non MEDA-Case up and running (SVAN)</u>
{| class="wikitable"
{| class="wikitable"
|+
!No
!Date
!Date
!GoalGoal
!Goal
!Focus
!Test plan
!Test plan
|-
|-
|1.1
|
|
|Create SVAN case on LH PAX Portal, Tranfered to SARA,  
|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]]
|
|
|-
|-
|1.2
|
|
|LH PAX Portal visible with SVAN service and a couple of other simple services. Ability to create a request as PAX
|[[SARA.PAXPortal]]
|
|
|-
|1.3
|
|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]]
|
|-
|1.4
|
|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]]
|
|-
|1.5
|
|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]]
|
|
|}
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]]
|
|
|}
|}

Revision as of 16:33, 22 June 2025

Phase 1 - SARA Fundamental

Dev

Focus

Est. Size 2024 2025 2026 Est.

Size

Progress External Dep.

Notes

Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun
Kickoff / Initially planned discovery Def S 100% 3 days pre-order
Administration tools Dev Dev Q&A Dev Q&A 70%
Definition / Discovery Def Discovery 100%
LH Admininistration Tools Mixed Dev Q&A L 80%
MOC Administration Tools Mixed Dev Q&A XL 40%
Minor extensions during further discovery Mixed Dev Q&A S 0%
Architecture & Shared Logic Hubs Discovery Discovery Dev 30%
Finishing Documentation & Inter-Digital Architecture Arch Discovery Discovery XL 95% DB-Model, Process Aut. Engine (PAE)
SLH - TravelCarrierDataDistribution BE Dev M 0% Carrier digital <--> PAX Portal Digitals, Travel Service Operation Center Digitals
SLH - PortalUsageInteraction BE Dev L 0% PAX Portal Digitals <-> Passenger Digitals, Travel Partner Digitals
SLH - TravelServiceManagementEcosystem BE Dev L 0% Travel Service Operation Center <-> Passenger Digitals, Delivery Partner Digitals
SARA.PAXPortal Dev Q&A Dev Q&A 10%
LH PAX Portal FE & BE Dev Q&A XL 20% Interaction with Passenger Digital and Travel Partner Digital
Login for Travelagents / LH TravelID Mixed Dev Conf Q&A M 0% TravelID / Travelagent-Login
Discover PAX Portal FE Dev Q&A M 0%
SARA.Core Discovery Dev Q&A 20%
MOC Detailed Process Analysis not planned Mgmt Discovery XL 80% main reason for delay
SARA App Development FE/BE Dev XL 0%
SARA.ProcessAutomationEngine BE Dev Q&A XL 0%
LH EntraID BE Conf S 0%
SARA.DeliveryPartnerPortal Discovery Discovery Dev Q&A 20%
Definition MgMt Discovery Discovery M 100%
Delivery Partner Portal Mixed Dev Q&A M 10%
Interface Development Discovery Dev Q&A 15%
Definition / Discovery BE Discovery S 60%
ONERES BE Dev Q&A L 0% LH Int Ready, Req BTeam
SIRAX BE Dev Q&A S 0% LH Int Ready, Req BTeam
LH Partner Creation Portal Dev Q&A 0%
SARA.PartnerCreationPortal Mixed Dev Q&A L 0%
Full project Discovery & Dev preparations Core Dev Core Q&A Integration Testing Golive

Milestones

Phase 1.1: Get a non MEDA-Case up and running (SVAN)

No Date Goal Focus Test plan
1.1 Presentation of LH and MOC administration tools, definition of preparatory work Core Admininistration Tools, MOC Administration Tools
1.2 LH PAX Portal visible with SVAN service and a couple of other simple services. Ability to create a request as PAX SARA.PAXPortal
1.3 Create SVAN case on LH PAX Portal (US Case), Tranfered & Visible in new SARA SARA.PAXPortal, SARA.Core
1.4 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.PAXPortal, SARA.Core
1.5 SARA: Manual creation case (SVAN) SARA.Core
1.6 Cover all other simple NON-MEDA cases (information service communication, general inquiries) SARA.PAXPortal, SARA.Core

Phase 1.2. Increase PWD complexity (Wheelchair / NON-MEDA)

No Date Goal Focus Test plan
2.1 Wheelchair on PAX portal (non MEDA), Simple flow SARA.PAXPortal, SARA.Core
2.2 Wheelchair with Intermodal (non MEDA), Some communication with PAX over SARA and Portal SARA.PAXPortal, SARA.Core
2.3. Travel Partner group request on Portal,


Phase 1.3. Simple MEDA case (Sitting Case)

No Date Goal Focus Test plan
1.1 Presentation of LH and MOC administration tools, definition of preparatory work Core Admininistration Tools, MOC Administration Tools

Phase 1.4. POXY

No Date Goal Focus Test plan
1.1 Presentation of LH and MOC administration tools, definition of preparatory work Core Admininistration Tools, MOC Administration Tools

Phase 1.5. STRETCHER

No Date Goal Focus Test plan
1.1 Presentation of LH and MOC administration tools, definition of preparatory work Core Admininistration Tools, MOC Administration Tools

Phase 1.6. STRETCHER AND WENOLL

No Date Goal Focus Test plan
1.1 Presentation of LH and MOC administration tools, definition of preparatory work Core Admininistration Tools, MOC Administration Tools

Phase 1.6. Billing & Reporting

No Date Goal Focus Test plan
1.1 Presentation of LH and MOC administration tools, definition of preparatory work Core Admininistration Tools, MOC Administration Tools

Plannungsverlauf

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.

Outcome: Definitiver Plan mit den implikationen der discovery phase wird am 26.06. präsentiert

10.02.2025 aktualisierter Plan

  • Added discovery sessions (Feb - May)

01.10.2024 initialer Projektplan

See also

Retrieved from "https://wiki.kordeus.com/index.php?title=LHG:SARA_Project&oldid=2337"