THE SAME RECORD, ON THE LINE.
DigiFactory is planned: the same records, scopes and approvals, aimed at work orders, routings and line floors. We are choosing design partners who run one real line and can name the system it sits beside.
/CLAIMS
WHAT WE DO NOT CLAIM.
There is no DigiFactory product, demo or release date. Registering interest tells us which operations to learn next.
DigiFactory: the suite for manufacturing operations, on the same substrate.
A DigiFactory product, demo or release date.
- /DIGIFACTORY · PLANNEDplanned, no product yet
- /SUBSTRATE · OBSERVEDthe same cells and facts
/WHAT CARRIES OVER
WHAT WOULD CARRY OVER.
The point of a substrate is that a second suite starts from the first one's rules. These are the parts we expect to reuse, and the one we would have to build.
- 01
CELLS, FACTS, SCOPES
The same single-writer cells, the same facts and the same owner scopes, with work orders and routings as new kinds of record.
PLANNED - 02
APPROVALS
A person approves the exact payload before a gated change runs, whether it is a write-off or a routing revision.
PLANNED - 03
MACHINE DATA
Line and machine readings enter through capture. This is the part that does not exist yet.
PLANNED - 04
SUPPLIERS
Suppliers read their own slice of the record, the way a 3PL's clients do.
PLANNED
DigiFactory modules run on the same cells, facts, scopes and approvals as DigiWarehouse.
Machine and line data enters through capture, with OPC UA as one source.
A manufacturer and its suppliers share records through Digimesh under separate permissions.
/WHAT WE WOULD ASK
WHAT WE WOULD ASK YOU.
Describe one line: what it makes, what records it today, and which system holds the routing. We will tell you what carries over from DigiWarehouse and what does not exist yet.
- What does the line make, and in what batches?
- What records each step today, and where does that record live?
- Which system holds the routing, and who may change it?
- Which suppliers and customers need to see part of the record?