The moment a device connects, Duplex knows what it is and what it can do.
Step 1 of 5: Identity
A device signs in with its own identity.
A device signs in with its own identity and capabilities.
Integration and portability. It runs When a device connects.
The devices you know get in, and an unknown one stays out.
Every device signs in under its own name when it connects. A device your team has set up is in from its first sign-in, and one that cannot show who it is stays out.
Step 1 of 3: A known one
The labelling machine on line 2 signs in under its own name, and it is in.
Every device introduces itself.
At sign-in, a device says who it is, what it can read and what it can do, so Duplex knows from the start what its readings mean and what it can be asked to do.
Step 1 of 4: Who it is
First, who it is: the controller on packing line 3.
One identity for a device’s whole working life.
A device signs in as the same device every time. When what it can do changes, it says so at its next sign-in.
Step 1 of 4: Installed
March: the controller is installed on line 3, and signs in for the first time.
Works on devices and at the edge.
Devices make the decisions they are allowed to make locally, and send the rest back.
- A device signs in with its own identityA device signs in with its own identity and capabilities.
- Device readings, taken in orderReadings from a device update what Duplex knows about it, in order.
- Which devices are connectedYour team knows which devices are online, and which have gone quiet.
- What each device may decide locallyEach device knows exactly which decisions it may make locally.
See it on your own work.
From your own assistant to every agent your company runs, a pilot puts Duplex on your own work, with the measures agreed before it begins.