Discovery · Systems handbook

Systems handbook

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.

AuftragsPlaner

Every statement carries an evidence label, so you can see what we checked and what remains open.

Purpose and users

  • Observed

    The AuftragsPlaner schedules every production order across 22 machines. 14 planners and foremen use it daily.

  • Observed

    Orders arrive from the ERP every 15 minutes; confirmed dates are written back.

Architecture

  • Validated

    Desktop application with a central SQL database on the plant server; each workstation runs its own copy of the program.

  • Validated

    Three integrations: ERP (orders in, confirmations out), file server (machine times in), and a nightly export used by the capacity sheets.

Build and release

  • Validated

    Releases are built by hand and copied to a network share; workstations pick up the new version on start.

  • Validated

    The build requires a component library licence registered to Mr Brandt personally (see finding F1).

  • Inferred

    Roughly six releases a year, based on the files on the share; no release notes exist.

Operations

  • Observed

    If the tool stops, planners call Mr Brandt directly. There is no other escalation path.

  • Validated

    Nightly database backup; restore never tested (finding F4).

Known risks

  • Validated

    Single person able to build and release (F1).

  • Validated

    Planning rules only in code (F2).

  • Validated

    Direct writes into ERP tables (F3).

Knowledge gaps

  • Unverified

    How the tool behaves at year-end changeover; Mr Brandt recalls a manual step but could not remember it exactly.

  • Unverified

    Whether any workstation still runs an older version.

Evidence labels

Observed
We saw it, or it was shown or told to us directly.
Validated
We checked it against code, configuration, logs, or a test.
Inferred
A reasoned conclusion from what we saw, not yet checked.
Unverified
Reported to us, but we could not confirm it.

← Back to the guided tour