Discovery · Technical assessment

Technical assessment

Musterwerk Antriebstechnik GmbH

Situation
Spreadsheets, silos, and a wish for AI
Access
Tier A
Prepared by
Aleph Engineering GmbH
Version
1.0, reviewed by a second engineer

Scope and limits

Systems examined
ERP, AuftragsPlaner, Drive and Sheets, Excel workbooks, Shared mailboxes
Context only
Customer portal, Nightly sync, EDI link, Shop-floor data, File server, Document archive, Quality system, HR and payroll
Period
10 business days
Access
Tier A, context-led: Interviews, the documentation you supply, demonstrations, and limited non-invasive review.
Exclusions
No production data, no changes to any system, no security testing beyond configuration review.
Confidence
Medium for the process and the root causes, which we observed in five real offers. Low for the inner workings of the macros and the ERP data, which we could not inspect. We recommend a short read-only inspection before committing to a larger change.

Summary

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

Findings

F1

Prices exist in three places, and they disagree

HighObserved
System
Excel workbooks
Finding
Base prices are maintained in the ERP, a Google Sheet, and the calculation workbook. In the five offers we followed, two used an outdated price.
Evidence
Observed in the five offers and the supplied files.
Recommended control
Make the ERP the single source for base prices; spreadsheets read from it, never the other way round.
F2

Surcharge rules live in macros only two people understand

HighInferred
System
Excel workbooks
Finding
Material and batch-size surcharges are calculated by macros with no documentation. The two senior calculators adjust results by hand when something looks wrong.
Evidence
Inferred from the workbook and the interviews; the macros were not fully traced at this tier.
Recommended control
Document the surcharge rules with the calculators and move them into one tested calculation.
F3

Lead times are guessed, not taken from planning

MediumObserved
System
AuftragsPlaner
Finding
Offers state delivery times from a capacity sheet that is updated weekly by hand from the AuftragsPlaner.
Evidence
Observed in the interviews and the capacity sheet.
Recommended control
Feed available capacity from planning into the calculation automatically.
F4

Requests arrive in a shared mailbox with no tracking

MediumObserved
System
Shared mailboxes
Finding
There is no record of when a request arrived, who works on it, or why it was lost.
Evidence
Observed in the mailbox walkthrough.
Recommended control
Register every request in the ERP or a simple tracker when it arrives.
F5

An AI offer assistant would currently amplify the errors

MediumInferred
System
Drive and Sheets
Finding
An assistant can draft offer text and read requests well. Without one correct source of prices and rules, it would produce confident offers with wrong numbers, as the trainee's test showed.
Evidence
Inferred from F1 and F2 and the trainee's test.
Recommended control
Fix the price and rule sources first; then pilot an assistant on request intake and offer text, with prices always calculated, never generated.
F6

Sheet sharing is broader than intended

LowUnverified
System
Drive and Sheets
Finding
Staff believe some price sheets are shared with anyone who has the link.
Evidence
Reported in interview; we did not have access to check sharing settings.
Recommended control
Review sharing settings for all price-related sheets.

← Back to the guided tour