DUST Identity Cloud Engine (DICE)

One trusted record for every physical item.

DICE is DUST Identity's platform for tracking physical items. Every item gets an Identifier and a Thread: a living record of what it is, where it has been and who has handled it, shared securely across your supply chain.

The problem

Every item has a story. Most of it is lost.

Where was it made? Who handled it? What was replaced, inspected or repaired along the way? Today those answers live in spreadsheets, inboxes and paper files, scattered across companies.

DICE puts them in one place, bound to the item itself.

An electric bike with a path showing where it has been

How DICE works

Each item gets an Identifier and a Thread.

One scan connects the two. Everything else in DICE builds on that idea.

1

The Identifier

Every item gets an Identifier. Use a DUST marking for an identity that cannot be copied, or start with the QR codes, barcodes, data matrix codes and NFC tags you already use.

One scan binds the Identifier to the item's Thread.

A phone scans the identifier on a bike and binds it to the item's Thread
2

The Thread

A Thread is the item's digital record. Fields like serial number and specifications. Files like inspection reports, certificates and manuals. Every Identifier the item carries.

A Thread record showing fields, files, identifiers and a transaction log
3

The Transaction Log

Every event stays in the Thread's Transaction Log. Thread created. Identifier bound. Files added. Fields updated.

Nothing is overwritten, so the history is always complete.

The transaction log of a Thread listing each recorded event

Assemblies

Parts change. History stays.

Complex products are built from parts, and each part can have its own Thread. Attach them to the product's Thread to make an Assembly. When a part is replaced, the new one brings its own history and the old one keeps its record.

The same model powers Theseus, DUST's parts authentication solution for aerospace.

Motor, frame and battery pack, each with its own Thread

Step 1

Each part has a Thread

Motor, frame and battery are tracked on their own.

Part Threads attached to the e-bike's Thread as an Assembly

Step 2

Build the Assembly

Attach part Threads to the product's Thread.

A battery upgrade where the new and old battery each keep their own history

Step 3

Swap with confidence

Upgrade a part and every part keeps its own history.

Identify and verify

One scan answers two questions.

What is this item? And is it really the item it claims to be?

Scanning the bike's identifier finds its Thread

Identify

Scan any item to find its Thread. No serial number lookups. No digging through files.

Scanning confirms the identifier matches the expected value

Verify

Scan to confirm the Identifier matches the expected value. With a DUST marking, a copy cannot pass.

Partners

Built for supply chains, not single companies.

Items move between manufacturers, suppliers, distributors and customers. DICE moves their records with them, and you stay in control of what is shared.

Two organizations connected through invite, accept and confirm

1. Connection

Connect with a partner

Invite, accept, confirm. The Connection goes live on both sides.

A Shipment handing a Thread to the partner team

2. Shipment

Send Threads with the goods

A Shipment hands Threads to the partner team.

Choosing which fields, files and identifiers travel with a Shipment

3. Control

Choose what travels

Decide which fields, files and Identifiers go with each Shipment.

The partner accepts and gets a copy while the sender's Thread is marked Shipped

4. Handoff

Both sides keep a record

The partner accepts and gets their own copy. Yours stays, marked Shipped.

Building on DICE?

Read the developer documentation for the DICE API.

View the docs

See DICE in a live demo.

Book a DICE demo