THE RECORD CROSSES THE DOCK.
Digimesh lets a 3PL, its clients and their carriers act on the same recorded facts under separate permissions, instead of mailing copies to each other.
/DIGIMESH
THREE THINGS IT DOES.
Digimesh is the cross-organization layer of DigiOS: the contracts that let a cargo owner, a 3PL and a carrier act on one record without handing over copies.
ONE RECORD, MANY SLICES.
The 3PL and each client read one ledger through their own scope. A client sees its items, orders, stock and documents and nothing else.
EXCHANGE THAT CARRIES PROOF.
A document that leaves cites the recorded facts it came from; a document that arrives is kept as evidence with its sender and a fingerprint. A dispute is settled by following citations, not by comparing spreadsheets.
AUTOMATIONS WITH A NAME.
When a client's act triggers a consequence in the warehouse, the consequence carries the client's name and stays inside the limits that client could exercise itself.
- /CARRIER · DESIGNEDits own systems
- /3PL · OBSERVEDholds the record
- /CLIENT · DESIGNEDreads its own slice
/LEVELS
THREE LEVELS.
Only the first two are needed to run a 3PL. The third is planned, and not offered.
- /LEVEL C · PLANNEDcompany to company
- /LEVEL B · DESIGNEDoutside systems
- /LEVEL A · DESIGNEDinside one 3PL
INSIDE ONE 3PL.
Clients of one 3PL read their own slice of the 3PL's record.
WITH OUTSIDE SYSTEMS.
Documents and events move between the 3PL and systems it does not run.
COMPANY TO COMPANY.
Two organizations that each run DigiOS exchange records under agreements. Planned, not offered.
/CLIENT LINK
ONE CLIENT, ONE LINK.
Client Link is the hosted exchange between a 3PL and one client's systems: the documents a warehouse and its client send each other, and one queue for whatever does not match.
THE PALLET IS THE KEY.
The pallet identifier, the SSCC, ties a shipment's label, advice and events together across every format.
- /CLIENT SYSTEMS · DESIGNEDERP, OMS or API
- /CLIENT LINK · DESIGNEDdocuments with evidence
- /DIGIWAREHOUSE · OBSERVEDthe same recorded facts
| DOCUMENT | WHAT IT DOES | LANDS IN DIGIOS AS | STATE |
|---|---|---|---|
| X12 940 | A client's orders arrive as X12 940 or by API and land as orders opened, amended or cancelled. | orders.Open · orders.Amend · orders.CancelCommitment | DESIGNED |
| X12 943 · X12 856 | A client's advance notice arrives as X12 943, X12 856 or by API and lands as an expected receipt on an order. | orders.Open, matched by orders.MatchReceipt | DESIGNED |
| X12 944 | A receipt advice goes back to the client as X12 944 or by API, from the matched receipt. | The matched receipt, and inventory.Receive | DESIGNED |
| X12 945 | A shipment advice goes back as X12 945 or by API once the load closes, with carrier, tracking and pallet marks. | documents.ProjectShipmentNotice, after work.CloseLoad | DESIGNED |
| X12 947 | Adjustments, holds and write-offs go to the client as X12 947 or by API, so its stock matches the 3PL's. | Facts from inventory.Adjust · inventory.WriteOff · inventory.Restrict | DESIGNED |
| X12 846 | An inventory snapshot goes to the client as X12 846 or by API. | inventory.Availability or inventory.LedgerBalance | DESIGNED |
| X12 997 · X12 999 | Every document received is acknowledged or refused with a reason, by X12 997, X12 999 or an API response. | The link itself: an acknowledgment, or a refusal with its reason | DESIGNED |
| EXCEPTION QUEUE | What does not match waits in one exception queue for a person, with the evidence that raised it. | capture.ExceptionQueue, with the evidence that raised each item | DESIGNED |
/EVIDENCE
EXCHANGE THAT CARRIES PROOF.
Every document is a claim until it can be checked. Digimesh keeps each one next to the facts it came from, so a dispute is settled by following citations.
- 01
A DOCUMENT ARRIVES
It is recorded as evidence with its issuer, a digest and its control number.
DESIGNED - 02
IT OPENS AN ORDER
The order cites the document it came from, and the gateway checks the citation before the cell decides.
OBSERVED - 03
WORK IS RECORDED
Receipts, moves and loads are stored as facts naming who acted and under which scope.
OBSERVED - 04
AN ADVICE LEAVES
It is built from those facts and keeps a reference to each of them.
DESIGNED - 05
DELIVERY IS A FACT
Sent, acknowledged or refused is recorded as its own fact, not assumed from the send.
DESIGNED - 06
A RESEND CREATES NOTHING
A document delivered twice is recognised by its key and does not open a second order.
DESIGNED
/STANDARDS
STANDARDS, NOT LOGOS.
Cells in Departure Mono, each with its state. There are no marks here, because no mark would be ours to show.
- X12 940WAREHOUSE SHIPPING ORDERDESIGNED
- X12 945WAREHOUSE SHIPPING ADVICEDESIGNED
- X12 943TRANSFER SHIPMENT ADVICEDESIGNED
- X12 944TRANSFER RECEIPT ADVICEDESIGNED
- X12 947INVENTORY ADJUSTMENT ADVICEDESIGNED
- X12 846INVENTORY ADVICEDESIGNED
- X12 856SHIP NOTICEDESIGNED
- X12 997FUNCTIONAL ACKNOWLEDGMENTDESIGNED
- EPCIS 2.0EVENT VOCABULARY, ALIGNEDDESIGNED
- GS1 DIGITAL LINKIDENTIFIER RESOLUTIONPLANNED
- REST + WEBHOOKSAPI EXCHANGEPLANNED
- OPC UAMACHINE DATAPLANNED
EDI translation is embedded as a service behind the link; DigiOS owns the mapping, the evidence and the exception handling.
/WHO SEES WHAT
WHO SEES WHAT.
A client does not need DigiOS to be part of this. What it gets depends on whether it signs in or exchanges documents.
| WHAT | A CLIENT WITH A LOGIN | A CLIENT WITHOUT DIGIOS |
|---|---|---|
| HOW IT CONNECTS | Signs in and reads its own slice of the record.DESIGNED | Sends and receives the standard documents over EDI or an API.DESIGNED |
| WHAT IT SEES | Its own items, orders, stock and documents, dated, and nothing of another client.OBSERVED | The documents we send it, each citing the facts behind it.DESIGNED |
| WHO ACTS FOR IT | A person inside its scope, or an operator who names it.OBSERVED | Our client service, naming the client it acts for.OBSERVED |
A document that arrives is a claim. Most systems file it and move on, and the argument starts later. Cited is the difference between a document that arrived and one that can be checked.
/FAQ
QUESTIONS WE GET.
DO MY CLIENTS NEED DIGIOS?
No. A client without DigiOS sends and receives the standard documents over EDI or an API. A client you invite gets its own sign-in and sees its own slice.
CAN ONE CLIENT SEE ANOTHER CLIENT'S STOCK?
No. Each client's items, orders and stock are scoped to that client. A lookup that touches another client's pallet is refused without saying whose it is.
WHICH DOCUMENT FORMATS DO YOU SPEAK?
The warehouse set: X12 940, X12 945, X12 943, X12 944, X12 947, X12 846 and X12 856, acknowledged with X12 997. REST with webhooks sits beside it. EPCIS 2.0 export is a second wire format we expect to add.
WHAT IF A DOCUMENT IS REJECTED OR NEVER ARRIVES?
It lands in a shared exception queue with the reason. Redelivery carries an idempotency key, so a resend cannot create a second order.
IS THIS A NETWORK WE HAVE TO JOIN?
No. The first level is inside one 3PL, the second exchanges documents with outside systems, and company-to-company exchange between two DigiOS tenants is planned and not offered.
DO YOU HANDLE CARRIER TENDERING?
Not in the first scope. Load tendering and carrier status messages are outside what Client Link carries today. The carrier is drawn on the diagram so you can see where it would attach.
BRING ONE CLIENT'S FEED.
One client's order feed. One inventory export. We load both and open that client's view beside yours, so you see what the client would.