Resources / User Guide / Getting Started
Collectors and OT Bridge
Use collectors and OT Bridge to browse sources, validate signal quality, and move approved industrial data into DataOps context.
Controls engineers, data engineers, and implementation teams connecting operational sources.
Before you start
What to have ready
A source list with protocol, host, namespace, and access owner.
Read access to the first approved source.
A naming convention for tags, assets, units, and quality states.
A target module or data product that will consume the mapped context.
Usage workflow
How to use Collectors
Inventory the source
Identify the protocol, server, topic, table, historian path, file drop, or API endpoint that will become the first source in DataOps.
Browse and sample values
Use source browsing or protocol tools to inspect nodes, tags, values, units, timestamps, and quality indicators before mapping.
Register the source
Create the source record in DataOps, assign ownership, capture source health expectations, and keep credentials inside approved customer access paths.
Map tags to assets
Bind tags and topics to assets, systems, namespaces, and standard profiles so modules can reuse the same context.
Monitor and iterate
Use source and pipeline monitoring to catch stale signals, missing values, unit mismatches, and mapping gaps before operational use.
Product areas
Where to work in TwinEdge
Downloads
Collector, OT Bridge, and related packages.
DataOps Sources
Source registration and connector setup.
Tag Browser
Signal inspection and browsing.
DataOps Models
Asset and model mapping.
DataOps Monitor
Health, freshness, and run status.
App links require an approved TwinEdge account and the right module access.
Need help?
Get implementation guidance
Ask for help when source ownership, network access, or protocol setup is not clear.
Talk to TwinEdge