# Open Points

Tracked open points and their timelines, generated from every `## Open Points` section in the wiki. Grouped open-first; each links to the host page, which carries the citations. Generated — do not edit.

## Open (10)

### MDE device procurement
host: [MDE — Mobile Data Capture](../abbreviations/mde-mobile-data-capture.md) · updated 2025-06-30 · id: op-mde-device-procurement
- 2024-03-19: Steering committee approved procurement of 180 replacement MDE devices (decision LA-2024-03); Procurement to complete the tender by April 2024, with deliveries staggered per site ahead of each cutover. Jörn Albers asked that the SEAGULL pilot's units reach Bremen-Walle with enough lead time for the team to practice under live operation.
- 2025-06-30: Petra Vogelsang reported that delivery of the replacement MDE devices for three follow-up sites had slipped on the supplier side. Procurement, together with Sabine Krüger, is to hold an escalation conversation with the MDE supplier about delivery reliability in July 2025.

### Customs interface certification
host: [Projekt LEUCHTFEUER](../projects/projekt-leuchtfeuer.md) · updated 2026-03-20 · id: op-customs-interface-certification
- 2025-06-30: Certification of the customs interface by the responsible authority remains outstanding and, per current information, is not expected before autumn 2025; Marek Duszek owns monthly follow-up reporting to the committee on it.
- 2026-03-20: With the full estate live and every go/no-go gate cleared without a waiver, Vogelsang's go-live announcement retrospectively counts "the quarter we gave the customs certification" among the corrections that turned out to be worth it — suggesting certification is now in place, though the announcement gives no explicit certification date.

### Portal built on QUAYSTONE
host: [Projekt LEUCHTFEUER](../projects/projekt-leuchtfeuer.md) · updated 2026-04-08 · id: op-portal-on-quaystone
- 2026-03-20: Vogelsang's go-live announcement says the company will discuss what it builds "on top of" QUAYSTONE once operations have settled; customer-facing staff's rumours of a portal are "roughly right," with more detail due in April 2026 from the team that owns it.
- 2026-04-08: The rumoured portal materialises as SEAGULL, Blauwal's new customer self-service portal programme, constituted by a Geschäftsführung decision of 24 March 2026 and kicked off on 8 April 2026 under product owner Yasmin Okafor — a separate initiative from Projekt LEUCHTFEUER, with its own mandate, budget line, and team, that reuses the pilot's released codename.

### Label-printing carrier-format follow-up
host: [SEAGULL (2024-25 QUAYSTONE Pilot)](../projects/seagull-2024-25-quaystone-pilot.md) · updated 2025-03-03 · id: op-label-printing-carrier-format-follow-up
- 2025-03-03: The label-printing interface needed one configuration follow-up for a carrier format that appears only in month-end volumes; Gezeitenwerk was testing the fix against a recorded batch, not live traffic, and targeted having it in place before month-end.

### Lessons-learned workshop
host: [SEAGULL (2024-25 QUAYSTONE Pilot)](../projects/seagull-2024-25-quaystone-pilot.md) · updated 2025-03-03 · id: op-lessons-learned-workshop
- 2025-03-03: Tomás Iglesias offered to bring the lessons-learned workshop to Bremen in the last week of March 2025, pending the steering committee's scheduling decision; from Gezeitenwerk's side nothing stood in the way of the April hold-point review.

### Pilot customer agreements
host: [SEAGULL](../projects/seagull.md) · updated 2026-04-08 · id: op-pilot-customer-agreements
- 2026-04-08: Action SG-AP-1 — pilot customer agreements to go to countersignature; owner Yasmin Okafor; due May 2026.

### API coverage gap analysis
host: [SEAGULL](../projects/seagull.md) · updated 2026-04-08 · id: op-api-coverage-gap-analysis
- 2026-04-08: Action SG-AP-2 — gap analysis of portal use cases against current QUAYSTONE API endpoints; owner Marek Duszek; due 12 May 2026.

### Operations liaison
host: [SEAGULL](../projects/seagull.md) · updated 2026-04-08 · id: op-operations-liaison
- 2026-04-08: Action SG-AP-3 — operations liaison to be named from the Bremen-Walle crew; owner Sabine Krüger; due 20 April 2026.

### KOMET estate assessment
host: [KOMET](../systems/komet.md) · updated 2024-03-19 · id: op-komet-estate-assessment
- 2024-03-05: Marek Duszek gave a first, deliberately verbal sketch of the KOMET estate and asked for two weeks to put together a proper written assessment enumerating the sites, interfaces, and local customisations, so that Projekt LEUCHTFEUER's planning rests on counted facts rather than estimates (action AP-2, owner Marek Duszek, due 15 March 2024).
- 2024-03-12: Duszek delivered the written assessment three days ahead of the deadline — 34 pages on the project share (folder "AP-2"), with section 2 (interfaces) and section 5 (customisations) flagged as required reading before the 19 March steering committee.
- 2024-03-19: Duszek summarised the assessment for the steering committee, which accepted it approvingly and asked that the interface list be kept as a living document on the project drive (decision LA-2024-01).

### KOMET operating-cost audit
host: [KOMET](../systems/komet.md) · updated 2026-04-15 · id: op-komet-operating-cost-audit
- 2026-04-15: Heike Brandt formally retracted her 10 June 2024 memorandum "KOMET operating costs (provisional figures)" after the final 2024–2025 operations audit found its downtime-cost estimate's methodology unsound — it had double-counted renegotiated contractual penalties and extrapolated a peak-season pattern across the whole year. The memorandum was withdrawn from the project record and its figures are not to be relied on, quoted, or restated; corrected figures are held separately, under restricted access.

## Done (3)

### Article master data cleansing
host: [Projekt LEUCHTFEUER](../projects/projekt-leuchtfeuer.md) · updated 2025-06-30 · id: op-article-master-data-cleansing
- 2024-03-05: Sabine Krüger flagged the state of the article master data as the operational risk she loses sleep over — years of parallel maintenance in KOMET have left duplicate article records across the sites, and migrating duplicates would multiply them. The meeting agreed the master data must be cleansed before the pilot cutover, not patched afterwards (action AP-1, owner Sabine Krüger).
- 2024-03-19: Cleansing is under way; the scope of duplicates has proven considerable and has grown over years, especially where sites created articles in parallel. It remains a mandatory precondition for the pilot cutover, and Sabine Krüger now reports progress to the steering committee monthly with KPIs — a priority the committee underlined unanimously.
- 2025-01-20: Revision B reconfirms that cleansing has progressed but remains a hard precondition for the pilot cutover, tracked monthly until closed.
- 2025-02-10: Cleansing stands at roughly two thirds complete, with the remainder concentrated in the two sites with the oldest parallel maintenance history; the trajectory supports the pilot date. The committee kept AP-1 open with its monthly reporting rhythm and renewed its status as a hard precondition.
- 2025-06-30: Reported complete — the remaining duplicate stock from the two oldest sites is cleared, and new article records are now centrally reviewed so duplicates cannot recur. Action AP-1 is closed and dropped from monthly reporting; the Lenkungsausschuss thanked Sabine Krüger explicitly, noting the point had been the programme's most persistent for over fifteen months.

### Cutover strategy for remaining sites
host: [Projekt LEUCHTFEUER](../projects/projekt-leuchtfeuer.md) · updated 2024-05-07 · id: op-cutover-strategy
- 2024-03-05: Left open whether the sites after the SEAGULL pilot follow one at a time or in a single coordinated cutover. Petra Vogelsang will circulate a written cutover-strategy proposal in early April 2024 (action AP-3) for the steering committee to decide.
- 2024-03-19: Reconfirmed as a task: Petra Vogelsang is to bring the cutover strategy to the steering committee for decision at the May meeting.
- 2024-04-02: Petra Vogelsang circulated her written cutover-strategy proposal (action AP-3) ahead of the steering committee. She argues a single, big-bang cutover of the whole estate would be reckless for the company (see Petra Vogelsang for her full reasoning). Her concrete proposal: SEAGULL sails first exactly as already decided, then a hold point during which no second site is touched until the pilot has run stably and its lessons are documented; the remaining sites then migrate in convoys of at most two, each gated by its own go/no-go decision on data readiness, trained crew, and interface tests, with an unready site deferred to the next convoy; and the cutover date follows the readiness of the sequence rather than a fixed calendar. Comments on the proposal were due in writing by 12 April 2024, with the decision remaining the steering committee's.
- 2024-05-07: Resolved — the Lenkungsausschuss adopted Vogelsang's proposal: the rollout is phased warehouse by warehouse, SEAGULL first, then a hold point, then the remaining sites in small groups with individual go/no-go decisions on data readiness, trained staff, and interface test results.

### Hypercare and cutover-weekend defects
host: [SEAGULL (2024-25 QUAYSTONE Pilot)](../projects/seagull-2024-25-quaystone-pilot.md) · updated 2025-06-30 · id: op-hypercare-and-cutover-weekend-defects
- 2025-03-03: One week after cutover, the hypercare crew remained on site for the agreed two weeks, and three low-priority defects from the cutover weekend were logged in the tracker with fixes scheduled inside the hypercare window.
- 2025-06-30: Hypercare closed on schedule after two weeks; the three low-priority cutover-weekend defects are fixed and signed off.
