Discovery · Technical assessment

Technical assessment

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.

Summary

6 findings: 2 high, 2 medium, 2 low. Severity reflects the impact on Musterwerk's operations and the likelihood of that impact, given what we could examine.

Findings

F1

The tool can only be built on one laptop

HighValidated
System
AuftragsPlaner
Finding
The build depends on a component library licence and compiler settings that exist only on Mr Brandt's personal laptop.
Evidence
Confirmed: a clean build failed until we reconstructed the settings from the project files.
Recommended control
Rebuild the build on a company-owned machine, document it, and transfer the component licence to Musterwerk before Mr Brandt leaves.
F2

Scheduling rules exist only in code

HighValidated
System
AuftragsPlaner
Finding
Around 40 planning rules (machine groups, set-up times, priority customers) are written directly into the code, not configured. They are not documented anywhere else.
Evidence
Validated: each rule located in the source code and listed in the handbook.
Recommended control
Document every rule in the handbook and protect them with tests before anyone changes the code.
F3

The ERP interface writes directly into ERP tables

MediumValidated
System
ERP
Finding
Order confirmations are written straight into the ERP database rather than through its interface. The planned ERP upgrade will very likely break this.
Evidence
Validated in the source code and the database permissions.
Recommended control
Include this interface in the ERP upgrade plan and test it before the upgrade.
F4

No tested restore of the planning database

MediumValidated
System
AuftragsPlaner
Finding
The database is backed up nightly, but a restore has never been tested.
Evidence
Validated: backup jobs present, no restore records.
Recommended control
Test a restore during the first month and repeat it every quarter.
F5

Machine data import silently skips bad files

LowValidated
System
Shop-floor data
Finding
When a terminal writes an incomplete file, the import skips it without warning. Planners see late actual times without knowing why.
Evidence
Validated in the import code; frequency not measured at this tier.
Recommended control
Log and report skipped files to the planners every morning.
F6

Peak-time slowdowns

LowInferred
System
AuftragsPlaner
Finding
Planners report the tool slows down on Monday mornings. A missing database index is the likely cause.
Evidence
Inferred from the database design; not measured.
Recommended control
Add the index after a test on a copy of the database.

← Back to the guided tour