She doesn't look at the machines.
She looks at the filing cabinets.
Her name is Ms. Chen.
She arrives at 9am with a rolling carry-on bag,
an iPad in a hard case,
and the specific kind of calm that belongs to people
who have seen this before.
Many times before.
The plant manager gives her a tour.
New equipment. Clean floors. Calibrated instruments.
He is proud of the production line.
He should be. It's good work.
Ms. Chen walks the line for two hours.
She says nothing.
She writes nothing on her iPad.
Then she turns to the plant manager and says:
"I'd like to see the production records. All of them. Going back eighteen months."
The plant manager smiles.
He has been preparing for this question.
He did not prepare for the answer to be complicated.
Here is what Ms. Chen finds:
The production floor: acceptable.
The equipment: calibrated, documented, within spec.
The documentation:
Batch records exist in three formats across four departments.
No single record contains the full picture of any batch.
To trace one production run from raw material to finished goods,
you would need to:
- Find the batch number in Manufacturing's daily log (Excel, by shift, by month, one file per month, stored on the shift supervisor's PC)
- Cross-reference with QA's inspection log (different Excel format, different batch number convention, stored on the QA lead's laptop)
- Find the process parameters in Engineering's test folder (password protected; the VP is in a meeting)
- Locate the material lot number in the incoming inspection binder (physical binder, shelf B3, organized by receipt date, not by lot number)
Ms. Chen does not do all of this.
She does enough of it to write, in the Notes field of her iPad:
Traceability: not demonstrated.
She meets with the CEO at 2pm.
She is direct. She is not unkind.
"Your production capability is real," she says.
"Your quality control process is real.
Your documentation system
is not a system.
It is hope organized into folders."
She opens her iPad and reads from the checklist:
- Single source of truth for production data: Not met.
- Traceability from raw material to finished goods: Not met.
- Audit trail for process parameter changes: Not met.
- Data stored in auditable, non-editable system: Not met.
"You have ninety days," she says.
"If these items are addressed at re-audit,
we proceed with the contract.
If not—"
She doesn't finish the sentence.
She doesn't need to.
The emergency meeting is Monday, 8am.
All senior managers. No exceptions.
The CEO does not raise his voice.
He doesn't need to.
He says: "Everything goes into a database. Oran is the project manager."
Then he looks at Oran.
Oran has been in this company for two years.
He has fixed the printers.
He has recovered someone's corrupted Excel file at 11pm.
He has set up the WiFi in the new warehouse.
He has never been a project manager.
He has also never wanted to be one.
But he has been taking notes since this meeting started,
and he has been thinking about this problem since the yield rate argument
three months ago,
and he knows — with the specific certainty that comes from
having already tried to do the thing the wrong way —
that there is no version of this that works
if IT just builds a database and waits for departments to fill it.
So before he says yes,
he stands up.
He writes three things on the whiteboard.
1. The timeline is IT's decision.
"The audit deadline is ninety days from today.
That does not mean the system is delivered in ninety days.
That means the system is delivered in whatever time it takes to build it correctly,
and the scope is defined by what can be done correctly,
not by what the deadline demands.
If the scope doesn't fit the timeline,
that is a conversation about scope.
Not about overtime."
The VP of Engineering shifts in his seat.
2. Resourcing is non-negotiable.
"I need two additional developers.
I need budget for tooling — database licenses, server infrastructure, testing environment.
I am one person. One person cannot build a traceability system for six product lines
in ninety days and also answer the help desk tickets
and also be in four status meetings a week."
The VP of Manufacturing starts to say something.
Oran continues.
3. Passive cooperation is not cooperation.
"Every department will have data submission deadlines.
If a department does not submit data by the agreed date,
the project is blocked.
That is documented as a management issue,
not an IT issue.
I will not absorb delays caused by other departments.
I will document them and escalate them."
He looks at the room.
"I want this in writing.
Signed.
Before the project starts."
The room is quiet for a moment.
Then the VP of QA says: "I think that's reasonable."
The VP of Engineering says nothing, which Oran writes down.
The VP of Manufacturing smiles — the specific smile of someone
who has already decided what they are going to do
and it is not what they are about to say —
and says: "Of course. We'll cooperate fully."
Oran writes that down too.
He writes the date next to it.
He puts a small star next to the VP of Manufacturing's name.
The CEO looks at Oran for a long moment.
Then he nods once.
"Ninety days," he says. "Make it work."
After the meeting, Oran walks back to his desk.
He opens his notebook to a fresh page.
At the top he writes:
Day 1.
Below it:
Things that are true:
— The system doesn't exist yet.
— The data is in twelve drawers.
— Three departments will say they're cooperating.
— Two of them mean it.
— The one who doesn't will be the most enthusiastic in every meeting.
He draws a line.
Below the line:
Things I can control:
— What I agree to.
— What I document.
— What I build.
He looks at that list for a while.
Then he opens his laptop and starts writing the schema.
The battle for the data hadn't started yet.
But Oran had just made sure that when it did,
he would not be the one who lost it alone.
Next: Ep4 — The Voluntary Table
No department wanted to think about the whole picture.
Then they sat in a room with a deadline and no escape.
Oran said nothing. That was the point.
← Ep1: The Excel Republic
← Ep2: The Big Customer
Coding Cat Oran is a serialized fiction about building real production systems inside real companies.
The audits are real. The ninety days are real. The cat is fictional.
The VP of Manufacturing is, unfortunately, also real.
By SysLayer · dev.to/syslayer
Top comments (0)