Discovery · Outcome roadmap

Outcome roadmap

Musterwerk Antriebstechnik GmbH

Situation
The one person who knows the system is leaving
Access
Tier B
Prepared by
Aleph Engineering GmbH
Version
1.0, reviewed by a second engineer

Scope and limits

Systems examined
ERP, AuftragsPlaner, Shop-floor data, File server
Context only
Customer portal, Nightly sync, EDI link, Document archive, Quality system, HR and payroll, Drive and Sheets, Excel workbooks, Shared mailboxes
Period
10 business days
Access
Tier B, read-only technical inspection: Approved read-only access to named repositories, configuration, build and deployment setup, or infrastructure views.
Exclusions
No production data, no changes to any system, no security testing beyond configuration review.
Confidence
High for how the tool is built, released, and connected. Runtime behaviour, such as performance, is inferred.

Options and decision points

Ordered by dependency, not by date. Each option names the decision that is yours to make.

  1. R2

    Operate the tool with a clear service boundary

    Application Managed Services

    Incident handling, monitoring of the ERP interface, routine updates, and small fixes through an agreed change process.

    Depends on
    R1
    Your decision
    Agree response times and which changes need your approval.
  2. R3

    Prepare the ERP interface for the upgrade

    Modernization

    Replace direct table writes with the ERP's own interface, protected by tests.

    Depends on
    R1
    Your decision
    Decide together with the ERP upgrade timeline.
  3. R4

    Replace the AuftragsPlaner

    New product development

    Considered and not recommended now: the tool does its job, and the planning rules must be understood before anything can replace it.

    Depends on
    R1, R2
    Your decision
    Revisit after a year of operation, with the documented rules as the starting point.

← Back to the guided tour