Since Discovery Note 02 first opened, the Milkfed Verka engagement has moved from an initial workflow review into a mapped operational architecture and a scoped pilot. This update describes how the procurement flow now connects end to end — at an architecture level, ahead of any live deployment.
How does milk move from society to plant today?
The picture traces milk from farmer and cooperative society collection, through Bulk Milk Coolers and Milk Chilling Centres (BMC / MCC), tanker movement to plant, plant reception and weighbridge entries, QA and lab testing for Fat / SNF, and the SAP / ERP records that close the procurement loop. Each is a system of record today; none of them talks to the others.
What does the orchestration model do?
It collapses those separate records into one model. The sources rise into a single unified representation — society, collection, tanker trip, plant batch, and QA sample as connected entities — which a deviation-intelligence layer reads to surface quantity variance, Fat / SNF signals, route anomalies, and reconciliation gaps. Resolutions flow back out as alerts, review items, auto-reconciliation, and reports.
What is the working hypothesis?
That a meaningful share of procurement deviation is already latent in existing operational data, and becomes visible when those signals are modelled together rather than read in isolation. The hypothesis is unchanged from the first note but better evidenced. Connecting the existing signals is the work — not adding new hardware.
How invasive is the integration?
It is designed not to be. We do not replace Verka’s existing systems; we map them, model the relationships between the entities that move through them, and prepare a decision surface that can sit on top of the stack. Camera, RFID, or sensor integrations remain out of scope until the data-only signals are proven.
What this note does not claim
This remains a pilot-scoping engagement. What is shown here is designed architecture and a scoped pilot — not a live production rollout, and not a signed commercial contract. No real production figures, society identities, or operational data are represented in this note. It will be updated as the pilot scope is confirmed and the first live use case enters build.