Skip to content
DigiOS.
LOGINREQUEST A SESSION
/CELLS

NINE MODULES. ONE SUBSTRATE.

The module library of DigiWarehouse. Each module owns its cells and its facts, and each has a board a person lands on.

/MODULES

THE MODULE LIBRARY.

Nine modules, each with the cells it owns, the board a person lands on and the state of its claim.

/PRODUCTSOBSERVED

Items, packs and barcodes, kept per client.

OWNS · TypeCatalog · TypeIndex

HOME BOARD · products.TypeIndex

/IDENTIFIERSOBSERVED

Pallets, plates and serials, unique across the tenant.

OWNS · Binding · ClassBinding · PrefixAuthority · Allocator · OpenBindings · ClassBindingIndex

HOME BOARD · identifiers.OpenBindings

/LOCATIONSOBSERVED

The warehouse map and the rules that guard it.

OWNS · FacilityLayout · HoldingsShard · Contents · ShardRouting

HOME BOARD · locations.Contents

/INVENTORYOBSERVED

Each client's book: on hand, held, reserved.

OWNS · Ledger · Intake · Availability

HOME BOARD · inventory.Availability

/ORDERSOBSERVED

Orders, notices and dock appointments as one kind of record.

OWNS · Commitment · CommitmentView

HOME BOARD · orders.CommitmentView

/WORKOBSERVED

Tasks a person can pick up and a system can check.

OWNS · Task · Load · Release · Capacity · TaskBoard

HOME BOARD · work.TaskBoard

/CAPTUREOBSERVED

Scans, counts and readings, including those taken offline.

OWNS · DeviceSession · ObservationLog · Station · ReadPoint · RegionObserve · SessionBoard · ExceptionQueue · ObservationFeed · RegionBoard

HOME BOARD · capture.ExceptionQueue

/DOCUMENTSOBSERVED

Labels and print jobs, with what printed and what did not.

OWNS · Document · Printer · TemplateCatalog · DigestClaim · TrackingClaim · SerialPrintClaim · DocumentIndex · PrinterQueue

HOME BOARD · documents.DocumentIndex

/APPROVALSOBSERVED

A drafted change, a named approver, one dispatch.

OWNS · Proposal · ProposalStatus · PendingApprovals

HOME BOARD · approvals.PendingApprovals

ILLUSTRATIVE: THE LIT CELLS ARE A DRAWING, NOT DATA.

/ONE RECORD

HOW MODULES SHARE ONE RECORD.

Nine modules do not mean nine databases. They write one log of facts, and a few rules connect them.

  1. 01

    ONE LOG OF FACTS

    Every module appends its facts to the same log, each with its own type, version and scope, so what capture recorded can be read by inventory.

    OBSERVED
  2. 02

    POLICIES CONNECT THEM

    Confirming a task step posts the move in locations. Closing a load issues the stock and fulfils the order. A count that disagrees can adjust the inventory book.

    OBSERVED
  3. 03

    BOARDS ARE VIEWS

    Each module's home board is built from its facts. It may lag; the cell that owns the figure is the authority.

    OBSERVED
  4. 04

    SCOPE RUNS THROUGH ALL OF THEM

    The owner is part of the key or the stamp in every module, so a client's slice is the same slice everywhere.

    OBSERVED
Nine modules on one substrateTwo eight by eight plates stacked. The upper plate has every module's cells lit in its own corner of the grid. The lower plate has a single strip of cells brightening to the right: the one fact log all nine modules write to.
/MODULES · OBSERVEDnine, each owns its cells
/FACTS · OBSERVEDone log they all write to
  • /MODULES · OBSERVEDnine, each owns its cells
  • /FACTS · OBSERVEDone log they all write to
FIG · NINE MODULES ON ONE PLATE, ONE LOG BENEATH

/LIMITS

WHAT A MODULE IS NOT.

The names are plain and the scope of each is narrower than a name can say. These are the edges we know of.

— NOT CLAIMED

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

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

A path for a customer's own people to author a workflow. Today our engineers compose one with you from the task kinds and rules the engine already has.

/NEXT

FOLLOW THE RECORD OR PICK A SUITE.

See the modules at work on one container, or see how DigiWarehouse groups them into jobs a person does.

N-01

RECORD

One inbound container, with the operation and the fact behind every step.

N-02

DIGIWAREHOUSE

Eighteen product areas in six groups, each with the board a person lands on.

/SESSION

OPEN THE MODULE YOU CARE ABOUT.

Tell us which module your operation leans on hardest, and we'll start the session there.

REQUEST A SESSION