The setup at a glance
Overall setup, users, and how the field connects to the centre.
Setups for different situations are in Deployment examples by situation, and installation steps are in the Installation chapter.
Overall setup
Install Edge SDK on the field PCs (small edge PCs placed in the factory) and MLOps Central Platform on the central server. MLOps Central Platform provides the management screen, so staff PCs need only a web browser.
In the pictures, the chip icon marks an edge PC running Edge SDK, and the M icon marks a server running MLOps Central Platform. The pictures in Deployment examples by situation use the same icons.
| Component | Location | What it does |
|---|---|---|
| Field devices | Factory | Devices such as robot arms, PLCs and cameras produce readings and product photos |
| Edge SDK | Field PC (small edge PC) | Gathers data from several devices and runs the AI model on site for a verdict. When the link drops it keeps the data and sends it once reconnected |
| MLOps Central Platform | Central server | Stores field data and trains AI models. Decides through approval which model goes into production, and sends the models staff choose to the field. Provides the management screen |
| Web browser | Staff PC | Opens the management screen. Shows device status and handles training, approval and deployment |
Users
Centre users can use only the features their role allows.
| User | Works in | What they do | Platform role |
|---|---|---|---|
| Field worker | Factory | Handles the devices and sees AI verdicts on the field program's screen | None (does not use the platform screen) |
| Operations staff | Head office · centre | Watches device status and alerts, and deploys models to the field | Operator |
| AI developer | Head office · centre | Builds datasets, trains models and compares results | Developer |
| Approver | Head office · centre | Approves or rejects the models that go into production | Approver |
Connection principles
Both principles apply to every deployment example.
1. The field connects first
Edge SDK in the field connects to the centre, reports its status and asks for work. New models and instructions come back as the response on that connection. The centre never connects into the factory first, so no inbound path is opened in the factory firewall. The only address that must be reachable is the central server's.
A connection from inside going out is outbound; one from outside coming in is inbound.
| Where | Outbound (inside to outside) | Inbound (outside to inside) |
|---|---|---|
| Factory (field PC) | Uses one connection out to the central server | Not opened |
| Central server | Never connects to the field first | Opens only the server address so field PCs can come in |
2. Store and forward when the link drops
While the link is down, data is kept on the field PC; when the link returns, the most important data goes first. AI verdicts are made on site, so the production line keeps getting verdicts while disconnected.