Getting Started / Guide

TwinEdge OS as an Edge Server

Use TwinEdge OS as the local edge server for protocol-rich sites that need local collection, buffering, dashboards, workflow support, and controlled sync.

Follow the workflowExplore the product
Intelligence at the equipment01 / SYSTEM VIEW
SignalsAlarmsHistoryTwinEdge AITwinEdge OSFleet contextOptional syncTwinEdge Historian · inference · dashboards
01Acquire02Store03Analyze04Synchronize
Local collection, history, and intelligence keep working offline.
Before you start

OT engineers, plant IT, controls teams, and implementation leads preparing a site-local runtime.

  • A selected edge host or approved local VM.
  • Network access to the source systems you plan to evaluate.
  • A TwinEdge account with download or customer package access.
  • A first source, asset class, or operating workflow to validate.
THE WORKFLOW

Move through the connected record.

  1. 01

    Choose the first site role

    Decide whether TwinEdge OS will run as an evaluation edge server, a no-cloud local runtime, or a hybrid node that syncs selected context to the cloud.

  2. 02

    Install and register the edge package

    Download the approved package, bring the host online, register it in the edge fleet, and confirm heartbeat, version, and update status.

  3. 03

    Attach sources through DataOps

    Use DataOps sources and tag browsing to connect OPC UA, Modbus, MQTT, historian, SQL, file, or REST sources while keeping site topology controlled by customer permissions.

  4. 04

    Validate local operation

    Confirm buffering, local dashboard access, source quality, timestamps, units, and sync status before routing the data into modules or API products.

  5. 05

    Promote the first workflow

    Move validated context into DataOps products, AssetOps EAM, Field, Water OS, Wastewater OS, analytics, or API/MCP access as appropriate.

CONTINUE IN TWINEDGE

Open your workspace.

Sign in with your TwinEdge account to access your enabled modules.

Downloads

Installers and customer package access.

Open in app

DataOps Edge Fleet

Registered edge nodes, health, and sync state.

Open in app

DataOps Sources

Source setup and connection checks.

Open in app

DataOps Monitor

Pipeline and source health monitoring.

Open in app

OTA

Update and package status where enabled.

Open in app
EXPLORE THE NEXT CONNECTION

Continue the workflow.

Collectors

Use collectors and OT Bridge to browse sources, validate signal quality, and move approved industrial data into DataOps context.

DataOps

Use DataOps Workbench to turn sources, tags, files, and records into reusable asset context, canonical graph relationships, API products, and MCP-ready data.

API and MCP

Use API and MCP products to expose governed operational context to approved applications, copilots, BI, and enterprise systems.

IMPLEMENTATION GUIDANCE

Build it around your operation.

Request implementation access when you need customer-specific package, network, or rollout guidance.

Talk to TwinEdge