Enture Edge OS¶
Overview¶
Enture Edge OS is an industrial edge-layer operating environment designed to bridge field devices, PLCs, CNC machines, and industrial systems with the Enture Cloud Platform. It acts as the managed middleware layer at each site — collecting data from connected OT hardware, processing and normalizing that data locally, and maintaining reliable synchronization with the cloud.
All configuration and governance of the Edge OS — including OT connector setup, data mapping, protocol parameters, and forwarding rules — is managed exclusively through the Enture Cloud Platform. There is no local configuration interface on the Edge OS itself.
Architecture¶
Enture Edge OS sits in the middle of a three-tier industrial data architecture:
Industrial Devices & Systems
↓
Enture Edge OS
Collect · Process · Store · Sync
↓
Enture Cloud Platform (Primary)
Third-Party Systems (Optional)
The Enture Cloud Platform is the authoritative upstream system. Third-party data forwarding is an additional capability layered on top of this primary relationship. This architecture lets organizations build scalable, hardware-agnostic, and remotely manageable industrial data infrastructure without custom per-device integration work.
Relationship with the Enture Cloud Platform¶
The Enture Cloud Platform is the central governing authority for all Edge OS deployments, covering the full operational lifecycle of every edge node.
Configuration & Governance Every aspect of Edge OS behaviour — connector setup, data mapping, protocol parameters, forwarding rules, and operational policies — is defined, deployed, and updated from the Enture Cloud Platform. No local configuration interface exists on the Edge OS.
Identity & Authentication The Enture Cloud Platform acts as the identity provider. Device authentication uses JWT-based tokens issued by the Platform, ensuring only authorized and registered edge nodes can communicate with the cloud.
Telemetry Synchronization Under normal connectivity conditions the Edge OS maintains continuous telemetry synchronization with the Platform. All processed and normalized data is streamed to the Platform as the primary destination.
Remote Operations Through the Platform, operators can perform the following without physical access to the edge node:
- Push configuration changes to OT connectors
- Run remote diagnostics and health monitoring
- Deploy updated processing workloads
- Apply software updates and maintenance
Key Capabilities¶
Data Acquisition & Connectivity¶
Enture Edge OS connects to OT systems, field devices, and CNC machine tools through two dedicated connector families:
- Enture OT Connectors — Modbus, OPC UA, MQTT, S7Comm, EtherNet/IP
- Enture CNC Connectors — Direct integration with CNC controllers (FANUC FOCAS2, Heidenhain LSV2, Siemens S7/OPC UA)
Supported device classes include PLCs, CNC machines, sensors, meters, SCADA systems, and special-purpose industrial equipment.
See OT Connectors for the full protocol reference.
Edge Processing¶
Processing workloads run locally at the edge — normalization, aggregation, filtering, and transformation — reducing dependency on cloud compute for time-sensitive or high-frequency operations. All workloads are defined and deployed centrally via the Platform.
Data Homogenisation & Normalisation¶
Industrial environments produce data in a wide variety of proprietary formats and protocols. The Edge OS standardizes this into a unified structure, enabling consistent interoperability across devices, OEMs, and downstream systems regardless of origin or manufacturer.
Offline Resilience & Automatic Sync¶
The Edge OS continues to operate autonomously during internet connectivity loss — collecting and processing data locally without interruption.
- Local data retention: up to 1 month of data stored locally during downtime.
- Automatic sync on reconnect: all buffered data is synchronized with the Platform once connectivity is restored; no data is lost during the outage.
Third-Party Data Forwarding¶
In addition to the primary Platform sync, the Edge OS can forward normalized data to external systems. Supported destinations include:
- Data lakes and data warehouses
- Message brokers (AWS IoT, Azure IoT Hub, HiveMQ, and others)
- MES and ERP systems
- Industrial historians
- Analytics platforms
- Customer-owned or third-party systems
Distributed Workload Management¶
Multiple edge nodes across different sites, plants, regions, or geographies are all managed centrally from the Enture Platform, making the Edge OS a viable foundation for enterprise-scale industrial deployments.
Security¶
| Attribute | Detail |
|---|---|
| Transport Security | TLS 1.2+ for all cloud communication channels |
| Device Authentication | JWT-based; tokens issued by the Enture Platform |
| Security Model | Zero-trust — explicit verification required for every connection |
| Access Control | Role-based and permission-based governance via the Enture Platform |
| Local Configuration Exposure | None — no local configuration interface |
| Compliance Alignment | Designed in alignment with ISO 27001 |
Deployment¶
Enture Edge OS can be deployed on the following infrastructure:
| Deployment Medium | Supported |
|---|---|
| Industrial Computers | ✓ |
| Desktop PCs | ✓ |
| Virtual Machines (VMs) | ✓ |
Once deployed, all configuration and management is handled exclusively through the Enture Cloud Platform. The hardware-agnostic model lets organizations use existing infrastructure or provision purpose-built edge hardware based on site requirements.
Typical Use Cases¶
- Manufacturing telemetry collection across machines, lines, and cells
- Multi-OEM machine and PLC integration into a unified data layer
- CNC machine tool data collection and operational telemetry
- Industrial IoT (IIoT) program infrastructure
- Remote monitoring and diagnostics for distributed assets
- OT-to-cloud synchronization with offline resilience
- Edge analytics and pre-processing pipelines
- Smart factory and Industry 4.0 data infrastructure