CORVANE LOGISTICS
THE 3PL. Runs the facility. Its staff hold every client as owner and name the client they act for.
What the team sees on the left. What the system writes on the right. Every name and figure here is a fictional sample.
/THE CAST
Three invented companies, one invented container and every figure on this page are samples. Nothing here is a customer, a result or a measurement.
THE 3PL. Runs the facility. Its staff hold every client as owner and name the client they act for.
THE CARGO OWNER. The client whose container arrives. Its own user holds exactly one owner scope: its own.
THE CARRIER. Delivers the container. It books a door and holds no scope inside the record.
/THE WALK
Nine steps. Each names the real operation it runs and the fact it writes; a name that is not in the catalogue yet is written in plain words, and its step is designed.
WHAT THE TEAM SEES
WHAT THE SYSTEM WRITES
WHAT THE TEAM SEES
Client service sees Halden Goods' notice appear on the order board, marked as expected.
WHAT THE SYSTEM WRITES
The notice is an order record owned by the client, not a copy in somebody's mailbox.
OPERATION · SAMPLE DATA
orders.OpenTIER · STAFF
FACT
An advance notice is opened as an order record owned by the client, with one line of twenty-four pallets.
WHAT THE TEAM SEES
The carrier books a door. The appointment sits on the order it belongs to.
WHAT THE SYSTEM WRITES
Appointment commands are scoped to the facility, not to one client.
OPERATION · SAMPLE DATA
orders.BookAppointmentTIER · STAFF
FACT
An appointment is booked on the order for a facility, a door and a window.
WHAT THE TEAM SEES
The truck arrives. The floor operator confirms the arrival on a handheld, offline if the network drops.
CONFIRM ARRIVAL AT DOOR 3
WHAT THE SYSTEM WRITES
Nothing is received yet: the container has only arrived.
OPERATION · SAMPLE DATA
capture.ObserveArrivalTIER · DEVICE OR SYSTEM
locations.RecordArrivalTIER · DEVICE OR SYSTEM
FACT
An arrival is observed at the door, and the container is recorded as arrived at the facility.
WHAT THE TEAM SEES
Each pallet label is scanned. The stock shows as received but not available until it is matched to the notice.
SCAN NEXT PALLET
WHAT THE SYSTEM WRITES
A receipt beyond tolerance would be recorded, never refused.
OPERATION · SAMPLE DATA
identifiers.RegisterContainerTIER · DEVICE OR SYSTEM
capture.RecordScanTIER · DEVICE OR SYSTEM
inventory.ObserveReceiptTIER · DEVICE OR SYSTEM
orders.MatchReceiptTIER · STAFF
inventory.ReceiveTIER · DEVICE OR SYSTEM
inventory.ReleaseTIER · STAFF
FACT
Each pallet is registered and its receipt observed, landing restricted. The receipt is matched to the notice within tolerance, the stock is received and the hold that kept it unavailable is lifted.
WHAT THE TEAM SEES
One pallet is missing. The shift lead sees a short on the exception queue. A person who holds the client's scope sees a request to close the line short, with the exact payload.
WHAT THE SYSTEM WRITES
An agent or a rule may draft the request. Only a person approves it.
OPERATION · SAMPLE DATA
capture.RecordShortTIER · DEVICE OR SYSTEM
approvals.DraftTIER · STAFF
approvals.ApproveTIER · PERSON ONLY
orders.ShortCloseLineTIER · STAFF
FACT
The shortfall is recorded. A request to close the line short is drafted, a person approves the exact payload, and the approved command is dispatched once.
WHAT THE TEAM SEES
A task sends the operator to a rack location. The confirmation is a scan.
PUT AWAY TO RACK A-01
WHAT THE SYSTEM WRITES
Confirming the task posts the move. Nobody types a stock quantity into a rack.
OPERATION · SAMPLE DATA
work.PlanTaskTIER · STAFF
capture.ClaimTaskTIER · DEVICE OR SYSTEM
work.ConfirmTIER · STAFF
locations.MoveInTIER · DEVICE OR SYSTEM
FACT
A putaway task is planned, claimed on the handheld and confirmed by a scan. Confirming it posts the move into the rack location, by policy.
WHAT THE TEAM SEES
The inventory controller reads the client's book. The client's own user reads the same record through its own login and sees nothing of any other client.
WHAT THE SYSTEM WRITES
No new fact: two reads of one record. The board names the time it is current to.
OPERATION · SAMPLE DATA
inventory.LedgerBalanceTIER · READ
inventory.AvailabilityTIER · READ
orders.CommitmentViewTIER · READ
FACT
The ledger balance is the authoritative read. The availability board is a view that may lag. The client's login carries an owner scope, so the same boards return only its own rows.
WHAT THE TEAM SEES
The 3PL sends Halden Goods a receipt advice. The client sees whether it was delivered and acknowledged.
WHAT THE SYSTEM WRITES
These names are not in the catalogue yet, so this step is designed, not observed.
OPERATION · SAMPLE DATA
documents.StoreDocumentTIER · STAFF
FACT
A receipt advice is built from the matched receipt and keeps a reference to the facts it cites. Whether it was sent, acknowledged or refused is recorded as its own fact.
WHAT THE TEAM SEES
Receiving and storage for this container are charged to the client. Billing is shown as planned: there is no charges board yet.
WHAT THE SYSTEM WRITES
One charge can be recorded today. Pricing it is the planned part.
OPERATION · SAMPLE DATA
orders.RaiseClaimTIER · PERSON ONLY
FACT
A charge is recorded against the order: one amount and a kind, such as handling or storage. Quantity, rate, billing run and invoice are planned.
Pallets, license plates and serials are registered once and are unique across the tenant; every move, hold and shipment is a recorded fact with a person or device and a time. A recall starts from those facts, not from three spreadsheets.
A charge is only as good as the recorded work behind it. The engine records receipts, moves and shipments as facts today; priced charges, rate-card revisions and client statements are planned and will cite those facts line by line.
/THE RECORD AFTER
Nine steps wrote facts in eight modules. Each module kept its own; the rows below say what, in plain words.
| MODULE | WHAT IT RECORDED | STATE |
|---|---|---|
| /ORDERS | The notice, the appointment, the match and the line closed short. | OBSERVED |
| /IDENTIFIERS | Every pallet registered once, unique across the tenant. | OBSERVED |
| /CAPTURE | The arrival, each scan and the short. | OBSERVED |
| /INVENTORY | The receipt observed, received and released, and the balance it left. | OBSERVED |
| /APPROVALS | One request drafted, approved against its exact payload and dispatched once. | OBSERVED |
| /WORK | The putaway task, planned, claimed and confirmed. | OBSERVED |
| /LOCATIONS | The arrival at the facility and the move into the rack. | OBSERVED |
| /DOCUMENTS | The receipt advice, and whether the client acknowledged it. | DESIGNED |
/WHAT IT DOES NOT SHOW
A walk through a product in build has edges. These are the ones we know about.
Home boards for six product areas that have none today: serial ranges, dock, charges, layout, release queue and loads.
A per-person task view, so a handheld shows the operator's own task first.
Rate cards, billing runs and invoices for a 3PL's clients, derived from recorded activity.
A full item master with names, descriptions, dimensions and weights. Products holds item identity and packaging only.
Load tendering and carrier status messages between a 3PL and a carrier.
Customers running DigiOS in production.
Bring one client's inbound notice and an inventory export, and we'll walk your container through the same steps.