Digital twin instance (DTI)

A digital twin instance (DTI) is the digital counterpart of one specific physical product, machine, vehicle, or running line after it exists. Academy writing ties the instance to its physical twin for the rest of that asset's life. Data about that unit updates the instance. Decisions about that unit use the instance. A design file that never met a serial number or a live hall is still a prototype, not an instance.

In a factory, instances show up as a tagged forklift with a history, a cell with live PLC and sensor context, or an operational view of one hall that refreshes with the shift. Aggregating many instances for fleet learning is a later step: the digital twin aggregate.

Key Components

Identity - A link to one physical unit, bay, or hall.

Life-cycle data - Operating history, faults, moves, or quality events for that unit.

Ongoing sync - Refresh from the floor at a rate the use case needs.

Applications in Manufacturing and Logistics

Asset health on a critical machine, location and utilization on one mover, or live state on one production line. Logistics optimization across a fleet needs many instances sharing one hall model.

Benefits and Challenges

The benefit is decisions about the unit that actually runs, not the slide that approved it. The challenge is plants that stop at one prototype hall and never stand up instances for the assets that burn money every shift.

Related Terms

See digital twin prototype, digital twin aggregate, and digital shadow.

Frequently Asked Questions

Is one 3D plant model an instance? Only if it stays linked to the live hall. A frozen export is closer to a prototype or a plain digital model.

Do we need an instance per forklift? For fleet utilization and empty travel, yes: each tagged mover is an instance on a shared map.