Skip to content
DigiOS.
/RECORD

ONE CONTAINER, END TO END.

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

A FICTIONAL CONTAINER.

Three invented companies, one invented container and every figure on this page are samples. Nothing here is a customer, a result or a measurement.

C-01FICTIONAL

CORVANE LOGISTICS

THE 3PL. Runs the facility. Its staff hold every client as owner and name the client they act for.

C-02FICTIONAL

HALDEN GOODS

THE CARGO OWNER. The client whose container arrives. Its own user holds exactly one owner scope: its own.

C-03FICTIONAL

BRIGHTWATER FREIGHT

THE CARRIER. Delivers the container. It books a door and holds no scope inside the record.

/THE WALK

FROM THE DOCK TO THE CHARGE.

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.

  1. [01]

    ADVANCE NOTICE IN

    WHAT THE TEAM SEES

    Client service sees Halden Goods' notice appear on the order board, marked as expected.

    BOARD · ORDERSSAMPLE
    NOTICESAMPLE-ASN-1042
    CLIENTHALDEN GOODS (FICTIONAL)
    EXPECTED24 PALLETS
    STATEEXPECTED

    WHAT THE SYSTEM WRITES

    The notice is an order record owned by the client, not a copy in somebody's mailbox.

    Modules touched by advance notice inAn eight by eight plate with the cells of the modules this step touches lit: orders, products.

    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.

    OWNERHALDEN GOODS
    KINDADVANCE NOTICE
    LINEHG-210 × 24 PALLETS
    ENTERED BYSTAFF, API OR X12 943
    OBSERVEDDESIGNEDTHE FEED IN IS CLIENT LINK
  2. [02]

    DOCK APPOINTMENT

    WHAT THE TEAM SEES

    The carrier books a door. The appointment sits on the order it belongs to.

    BOARD · APPOINTMENTSSAMPLE
    CARRIERBRIGHTWATER FREIGHT
    DOOR3
    WINDOW09:00 TO 10:00
    ORDERSAMPLE-ASN-1042

    WHAT THE SYSTEM WRITES

    Appointment commands are scoped to the facility, not to one client.

    Modules touched by dock appointmentAn eight by eight plate with the cells of the modules this step touches lit: orders, locations.

    OPERATION · SAMPLE DATA

    orders.BookAppointmentTIER · STAFF

    FACT

    An appointment is booked on the order for a facility, a door and a window.

    FACILITYSAMPLE FACILITY NORTH
    WINDOW09:00 TO 10:00
    ON ORDERSAMPLE-ASN-1042
    OBSERVED
  3. [03]

    CHECK-IN AT THE DOOR

    WHAT THE TEAM SEES

    The truck arrives. The floor operator confirms the arrival on a handheld, offline if the network drops.

    HANDHELD · ARRIVALSAMPLE

    CONFIRM ARRIVAL AT DOOR 3

    CONTAINERSAMPLE CNT-4471
    SESSIONON LEASE

    WHAT THE SYSTEM WRITES

    Nothing is received yet: the container has only arrived.

    Modules touched by check-in at the doorAn eight by eight plate with the cells of the modules this step touches lit: capture, locations.

    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.

    CONTAINERSAMPLE CNT-4471
    DOOR3
    OBSERVED BYA HANDHELD SESSION
    OBSERVED
  4. [04]

    RECEIPT SCAN AND MATCH

    WHAT THE TEAM SEES

    Each pallet label is scanned. The stock shows as received but not available until it is matched to the notice.

    HANDHELD · RECEIVESAMPLE

    SCAN NEXT PALLET

    SCANNED23 OF 24
    IDENTIFIERSAMPLE SSCC …0023
    STOCKRESTRICTED UNTIL MATCHED

    WHAT THE SYSTEM WRITES

    A receipt beyond tolerance would be recorded, never refused.

    Modules touched by receipt scan and matchAn eight by eight plate with the cells of the modules this step touches lit: inventory, identifiers, capture, orders.

    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.

    MATCHED23 PALLETS
    OPEN1 PALLET
    TOLERANCESET ON THE ORDER
    OBSERVED
  5. [05]

    SHORT COUNT TO APPROVAL

    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.

    BOARD · EXCEPTIONSSAMPLE
    TYPESHORT
    ITEMHG-210
    QUANTITY1 PALLET
    CLIENTHALDEN GOODS
    BOARD · PENDING APPROVALSSAMPLE
    REQUESTCLOSE LINE SHORT
    PAYLOADSAMPLE 9F2C41
    ACTIONAPPROVE OR REJECT

    WHAT THE SYSTEM WRITES

    An agent or a rule may draft the request. Only a person approves it.

    Modules touched by short count to approvalAn eight by eight plate with the cells of the modules this step touches lit: capture, approvals, orders.

    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.

    SHORT1 PALLET
    DIGESTSAMPLE 9F2C41
    APPROVERA PERSON IN THE CLIENT'S SCOPE
    OBSERVED
  6. [06]

    PUTAWAY

    WHAT THE TEAM SEES

    A task sends the operator to a rack location. The confirmation is a scan.

    HANDHELD · MY WORKSAMPLE

    PUT AWAY TO RACK A-01

    PALLETS23
    CONFIRMSCAN LOCATION

    WHAT THE SYSTEM WRITES

    Confirming the task posts the move. Nobody types a stock quantity into a rack.

    Modules touched by putawayAn eight by eight plate with the cells of the modules this step touches lit: work, locations, capture.

    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.

    TASK KINDPUTAWAY
    TORACK A-01
    POSTEDBY POLICY ON CONFIRM
    OBSERVED
  7. [07]

    STOCK ON HAND, AND THE CLIENT'S VIEW

    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.

    BOARD · AVAILABILITYSAMPLE
    CLIENTHALDEN GOODS
    ON HAND23
    AVAILABLE23
    AS OF11:42
    BOARD · CLIENT LOGINSAMPLE
    YOUHALDEN GOODS
    ITEM HG-21023 ON HAND
    OTHER CLIENTSNOT VISIBLE

    WHAT THE SYSTEM WRITES

    No new fact: two reads of one record. The board names the time it is current to.

    Modules touched by stock on hand and the client's viewAn eight by eight plate with the cells of the modules this step touches lit: inventory, locations, orders.

    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.

    SCOPEOWNER: HALDEN GOODS
    BALANCE23 PALLETS
    VIEWLAGGING, DATED
    OBSERVEDDESIGNEDTHE CLIENT'S OWN LOGIN
  8. [08]

    RECEIPT ADVICE OUT

    WHAT THE TEAM SEES

    The 3PL sends Halden Goods a receipt advice. The client sees whether it was delivered and acknowledged.

    BOARD · ADVICESSAMPLE
    DOCUMENTRECEIPT ADVICE
    FORMATX12 944 OR API
    CITESRECEIPT, MATCH, SHORT
    DELIVERYSENT, AWAITING ACK

    WHAT THE SYSTEM WRITES

    These names are not in the catalogue yet, so this step is designed, not observed.

    Modules touched by receipt advice outAn eight by eight plate with the cells of the modules this step touches lit: documents, orders.

    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.

    FORHALDEN GOODS
    CITESRECEIPT AND MATCH
    CHANNELCLIENT LINK
    DESIGNED
  9. [09]

    CHARGE RECORDED

    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.

    BOARD · CHARGES · NOT BUILTSAMPLE
    RECORDED ASONE AMOUNT, ONE KIND
    RATE CARDSPLANNED
    BILLING RUNSPLANNED
    HOME BOARDNONE YET

    WHAT THE SYSTEM WRITES

    One charge can be recorded today. Pricing it is the planned part.

    Modules touched by charge recordedAn eight by eight plate with the cells of the modules this step touches lit: orders, documents.

    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.

    KINDHANDLING
    ON ORDERSAMPLE-ASN-1042
    AMOUNTSAMPLE ONLY
    PLANNEDOBSERVEDONE CHARGE CAN BE RECORDED
/TRACE

EVERY PALLET HAS A TRAIL.

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.

OBSERVED— NOT CLAIMED
/CHARGES

A CHARGE NEEDS A FACT.

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.

OBSERVEDPLANNED— NOT CLAIMED

/THE RECORD AFTER

WHAT IS NOW ON THE RECORD.

Nine steps wrote facts in eight modules. Each module kept its own; the rows below say what, in plain words.

What each module recorded during the walk
MODULEWHAT IT RECORDEDSTATE
/ORDERSThe notice, the appointment, the match and the line closed short.OBSERVED
/IDENTIFIERSEvery pallet registered once, unique across the tenant.OBSERVED
/CAPTUREThe arrival, each scan and the short.OBSERVED
/INVENTORYThe receipt observed, received and released, and the balance it left.OBSERVED
/APPROVALSOne request drafted, approved against its exact payload and dispatched once.OBSERVED
/WORKThe putaway task, planned, claimed and confirmed.OBSERVED
/LOCATIONSThe arrival at the facility and the move into the rack.OBSERVED
/DOCUMENTSThe receipt advice, and whether the client acknowledged it.DESIGNED
Every module the walk touchedAn eight by eight plate with the cells of seven modules lit: orders, identifiers, capture, inventory, approvals, work and locations.
FIG · EVERY MODULE THE WALK TOUCHED, LIT ON ONE SUBSTRATE

/WHAT IT DOES NOT SHOW

WHAT THIS DOES NOT SHOW.

A walk through a product in build has edges. These are the ones we know about.

PLANNED

Home boards for six product areas that have none today: serial ranges, dock, charges, layout, release queue and loads.

PLANNED

A per-person task view, so a handheld shows the operator's own task first.

PLANNED

Rate cards, billing runs and invoices for a 3PL's clients, derived from recorded activity.

— NOT CLAIMED

A full item master with names, descriptions, dimensions and weights. Products holds item identity and packaging only.

— NOT CLAIMED

Load tendering and carrier status messages between a 3PL and a carrier.

— NOT CLAIMED

Customers running DigiOS in production.

/SESSION

WATCH IT ON YOUR CONTAINER.

Bring one client's inbound notice and an inventory export, and we'll walk your container through the same steps.