SyncTwinTECHNOLOGIES
Security and data

Data — with you, control — with the equipment

The platform runs inside the enterprise perimeter. You decide what goes to the cloud; motion and protection stay on site.

Diagram of the data and control boundary The enterprise perimeter covers the controller, drives, line data and the hardware safety circuit; only what the customer has chosen crosses the boundary to the cloud: the program and the run and stop commands. ENTERPRISE PERIMETER controller and drives line data machine panel safety circuit Cloudby yourchoice
Data

What stays with you

  • Line model, programs and data — inside your perimeterThe platform is installed on your servers; the model opens in the browser inside your network.
  • What you choose goes to the cloudThe scope of exchange is fixed in the implementation specification.
  • The box works without the cloudControl stays on site; the cloud is for remote development and tests. The box is installed with one command and a binding code; its identity is kept on reinstall.
  • Intent crosses the boundary, not gesturesThe program and the «run» and «stop» commands; jogging stays with the equipment.
  • Data from the request formProcessed under the personal data policy and not shared with third parties.
Equipment

Protection — on site

  • The safety circuit is a separate hardware circuitEmergency stop, doors and light curtains are not replaced by links between units; the program only reads them.
  • Hardware emergency stop and software interlockCell safety categories — per the cell design and its standard protective devices.
  • Torque to the drives — only within a motion stepTorque removal is confirmed by measurement, not by the command's reply.
  • Input forcing — for debugging onlyIt is cleared on emergency stop and never goes to production.
Where things are stored

Data map

DataWhereWho changes it
Machine and unit twins, programs, line projectsPlatform server — inside your perimeter or in the cloud, as you chooseEngineers in the browser
Control configurationGenerated from the twin at start and sent to the boxNobody by hand: an edit on the test bench disappears at the next start
Drive parametersDrive: RAM, to permanent memory — with a separate buttonCommissioning engineer at the equipment
Run log, axis factsThe platform; taken from the test benchRecorded by the platform from the test bench frame
Control

Who owns the equipment at which moment

Only one party holds the bus

Commissioning, machine mode or automation cycle. If it is taken, the platform names by whom.

Tests are locked while a program runs

The oscilloscope is visible, but commissioning test buttons do not work while a program runs.

Demos — read-only

An attempt to save into a demo program is refused with a link to its copy.

  • Mode change — with confirmationSwitching between virtual axes and drives on a running machine restarts control from the twin and resets axis homing.

The platform does not claim certification under ISO 13849 and IEC 61508: the safety categories of a cell are provided by its design and its standard protective devices. Offline updates and diagnostics without remote login are built into the installation design and verified in the implementation.

Next step

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

Implementation →

Request access