Decision memo from 29.09.2026. Captured 2 decisions and 4 actions; mentions 3 people and 2 projects.
Decisions
- Move the ERP go-live from 01.12.2026 to 11.01.2027
- BW-Classic stays available read-only until 31.12.2027 for look-ups
Actions
- Done: Reto Ammann: Agree the new go-live date with NovaERP (due 09.10.2026) · ERP migration
- Sandra Meier: Plan the 2026 year-end closing in BW-Classic (due 30.11.2026) · ERP migration
- Reto Ammann: Train the key users in NovaERP (due 18.12.2026) · ERP migration
- Done: Martina Keller: Tell all staff about the new go-live date (due 16.10.2026) · ERP migration
People mentioned
Projects
Original text
Date: 2026-09-29
Type: Decision memo
Author: Reto Ammann
Decided by: Martina Keller, Sandra Meier
Tags: #erp-migration
Situation
The plan was to go live with NovaERP on 01.12.2026. Three things make that risky:
- The clean-up of variant BOMs (see TCK-0433) is only half done.
- December has the year-end closing and the yearly stock count; finance cannot test the new system at the same time.
- The Line 3 retrofit ties up the production key users until mid-November.
Decision
Decision: Move the ERP go-live from 01.12.2026 to 11.01.2027.
Why: finance closes 2026 in BW-Classic and opens 2027 in NovaERP, so we never run two systems inside one financial year.
Why: the BOM clean-up and the third test migration need until the end of November.
Decision: BW-Classic stays available read-only until 31.12.2027 for look-ups.
Actions
- Action: @Reto Ammann agree the new go-live date with NovaERP (due 2026-10-09) (done)
- Action: @Sandra Meier plan the 2026 year-end closing in BW-Classic (due 2026-11-30)
- Action: @Reto Ammann train the key users in NovaERP (due 2026-12-18)
- Action: @Martina Keller tell all staff about the new go-live date (due 2026-10-16) (done)