The cell project is verified — before the hardware arrives
You bring a STEP assembly and a program; the cell is assembled in the twin, the logic passes a run, on site only binding sensors and axes remains.
Less work on site
- A mechanism from your STEP assemblyThe assembly structure becomes a kinematic tree; from you — joint type, axis and limits.
- Logic in IEC 61131-3SFC or ST; ready programs are brought as .st and PLCopen XML files.
- A run before the hardware arrivesLogic errors are found at the desk, not at the machine.
- Units of different manufacturers — one cellLinks between units — tags on one project graph.
- The project — in AutomationMLISA-88 roles, PackML tags, links — for exchange with engineering systems.
The implementation is an R&D stage on your cell
- Unit or cellAssembly, program, drives — whatever the project has.
- Twin and runRemotely, in the development cloud; tests — on the test bench or at the customer.
- Test protocolTarget figures from the implementation specification.
Input data and result
| You bring | What the platform does with it |
|---|---|
| A STEP assembly of the unit or cell | A subassembly becomes a link, its position a joint; from you — joint type, axis and limits |
| A program in ST or PLCopen XML | The compiler checks it in full; the lab shows inputs, outputs and state |
| The set of drives and I/O | Compatibility is checked at the start of the implementation and fixed in the specification |
| Customer requirements | Target figures go into the implementation specification, verification — into tests |
One scene for you and the customer
Showing in the browser
The customer sees the same cell and the same test run as your team — without installing software.
Working remotely
Programs are written and checked in the development cloud; drive tests — on the test bench or at the customer.
The twin — together with the line
After start-up the same twin shows the line by the facts; the line description goes to the customer in AutomationML.
Partnership terms are discussed individually.
Integrator questions
Is a site visit needed for the implementation?
The twin, programs and runs are done remotely. Tests need access to the machine or line for the time of testing; drive tests can start on our test bench.
Will the customer’s equipment fit?
Drives on an open industrial bus are needed — for example, EtherCAT with the CiA 402 profile. Compatibility of specific units is checked at the start of the implementation; if a unit needs separate work, that is part of the research.
Can we start with one unit?
Yes: a one-unit implementation on your drives. The whole line — as the next stage based on the protocol.
Discuss an implementation
Describe the unit or line — we will tell you what we will verify and in what time. Target indicators are fixed in the implementation specification.
Request access