UC-991
One Coil Record. Both halves, in SAP's language.
One record per coil carrying both histories, read from the existing systems, using the names SAP already uses, and changing nothing that works today.
16 weeksBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
$XXXK/yrValue
The Challenge
A coil's commercial life is in SAP and its production life is in the line systems. One says who ordered it and what it sold for. The other says what actually happened to it on the lines. Both exist. Nothing puts them side by side, so any question spanning the two takes days to answer.
How It Works
- Reads and connects the source records named in the proposal.
- One record per coil carrying both histories, read from the existing systems, using the names SAP already uses, and changing nothing that works today. A register of every plant-floor system and its
- Publishes a source-linked recommendation for Operations Head approval and records the decision.
What It Removes
- Two separate stories for one coil
- Questions that take days to answer
- Line data nobody can read later
Input Data RequirementsOperational, financial and reference records named in the agis proposal for One Coil Record. Both halves, in SAP's language..
Output FormatOne Coil Record. Both halves, in SAP's language. decision view with ranked actions, source links, confidence and a named owner.
“I can follow one coil from the heat number to the customer, in one place.”