Collectors and OT Bridge
Use collectors and OT Bridge to browse sources, validate signal quality, and move approved industrial data into DataOps context.
Before you start
Controls engineers, data engineers, and implementation teams connecting operational sources.
- 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.
Move through the connected record.
- 01
Inventory the source
Identify the protocol, server, topic, table, historian path, file drop, or API endpoint that will become the first source in DataOps.
- 02
Browse and sample values
Use source browsing or protocol tools to inspect nodes, tags, values, units, timestamps, and quality indicators before mapping.
- 03
Register the source
Create the source record in DataOps, assign ownership, capture source health expectations, and keep credentials inside approved customer access paths.
- 04
Map tags to assets
Bind tags and topics to assets, systems, namespaces, and standard profiles so modules can reuse the same context.
- 05
Monitor and iterate
Use source and pipeline monitoring to catch stale signals, missing values, unit mismatches, and mapping gaps before operational use.
Open your workspace.
Sign in with your TwinEdge account to access your enabled modules.
Continue the workflow.
Build it around your operation.
Ask for help when source ownership, network access, or protocol setup is not clear.