LHG:SARA Project: Difference between revisions
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 494: | Line 494: | ||
|XL | |XL | ||
|100% | |100% | ||
|✅ | |✅ | ||
|- | |- | ||
|UI/UX Iteration | |UI/UX Iteration | ||
| Line 519: | Line 519: | ||
|M | |M | ||
|100% | |100% | ||
|✅ | |✅ | ||
|- | |- | ||
|[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core App Development]] | |[[SARA.Core (Special Assistance Request Management Suite)|SARA.Core App Development]] | ||
| Line 772: | Line 772: | ||
| colspan="7" 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 QA | | colspan="2" style="text-align:center; background-color:#FFFFE0" |Core QA | ||
| colspan="2" style="text-align:center; background-color:#ADD8E6" | | | colspan="2" style="text-align:center; background-color:#ADD8E6" |Int. Testing | ||
| style="text-align:center; background-color:#FFCCCB" |Golive | | style="text-align:center; background-color:#FFCCCB" |Golive | ||
! | ! | ||
Revision as of 10:45, 2 April 2026
Phase 1 - SARA Fundamental
Current Project Plan
| Rel. Size | 2024 | 2025 | 2026 | Abs.
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 | 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 | 20 | 84,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 | 90% | ➡️ status update | |||||||||||||||||||
| SLH - TravelServiceManagementEcosystem | BE | Dev | XL | 90% | ➡️ status update | |||||||||||||||||||
| SARA.ProcessAutomationEngine | BE | Dev | QA | XL | 45% | ➡️ status update | ||||||||||||||||||
| SARA.DeliveryPartnerPortal | 8 | Discovery | Dev | QA | 3 | 95,0% | ||||||||||||||||||
| Delivery Partner Portal | Mixed | Discovery | Dev | QA | L | 95% | ||||||||||||||||||
| Interface Development | 4 | Discovery | Dev | QA | 6 | 83,3% | ||||||||||||||||||
| Initial Definition / Discovery | BE | Discovery | Discovery | S | 100% | ONERES bookings over API | ||||||||||||||||||
| Interface to ONERES (API bookings) | BE | Dev | QA | L | 80% | Changed, Delayed not on critical path | ||||||||||||||||||
| Interface DAS via Kafka | BE | Dev | QA | M | 80% | Additional work not on critical path | ||||||||||||||||||
| LH Partner Creation Portal | 8 | Dev | QA | 8 | 80% | |||||||||||||||||||
| Dev:Partner creation processes | Mixed | Dev | QA | L | 80% | ➡️ status update, in testing
UI Done InterDig automation open | ||||||||||||||||||
| Full project (100%) | 100 | Discovery & Dev preparations | Core Dev | Core QA | Int. Testing | Golive | 87,4% | |||||||||||||||||
| Additional work | 11 | |||||||||||||||||||||||
| Full test servers in NUE with new B-Op-Infra | Admin
BE |
Deployment | M | 100% | ✅ | |||||||||||||||||||
| Login&Registration Extensions for PAX & Botprotection | Mixed | M | 100% | ➡️ status update, in testing | ||||||||||||||||||||
| Interface to ONERES (GAV) Specification | BE | S | 100% | ✅ | ||||||||||||||||||||
| Interface to ONERES (GAV) Implementation | Mixed | S | 50% | |||||||||||||||||||||
| SCHED-Connect Specification | BE | S | 100% | |||||||||||||||||||||
| SCHED-Connect Implementation | Mixed | M | 80% | |||||||||||||||||||||
| Communication templates and implementation | Mgmt, mixed | DEV & QA | M | 50% | ➡️ status update | |||||||||||||||||||
| Task templates and implementation | Mgmt, mixed | DEV & QA | S | 0% | ||||||||||||||||||||
| Document templates and implementation | Mgmt, mixed | DEV & QA | S | 0% | ||||||||||||||||||||
| Performed work | 71,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
- End of June: Definitive project plan
- Mid of may: KORDEUS has presented an updated preliminary project plan
- 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.