User Guide

Resources / User Guide / Getting Started

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.

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

Before you start

What to have ready

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.

Usage workflow

How to use TwinEdge OS

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.

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.

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.

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.

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.

Need help?

Get implementation guidance

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

Talk to TwinEdge