DataOps Workbench
Use DataOps Workbench to turn sources, tags, files, and records into reusable asset context, canonical graph relationships, API products, and MCP-ready data.
Before you start
Data engineers, OT engineers, solution architects, and product owners preparing trusted operational context.
- At least one registered source or planned source connection.
- A target asset class, system, or operating workflow.
- Naming standards for assets, tags, units, and sites.
- A decision about which modules or APIs will consume the output.
Move through the connected record.
- 01
Register sources
Add operational sources and capture ownership, source health, connection pattern, and expected refresh behavior.
- 02
Inspect tags and records
Browse tags, topics, tables, and files to understand signal quality, units, naming, and missing context.
- 03
Map models and instances
Create asset models, bind instances, normalize fields, and connect source data to equipment, systems, and locations.
- 04
Build graph and namespace context
Use canonical graph, namespace, and standard profiles so modules and AI agents share the same operational meaning.
- 05
Publish and monitor products
Publish governed API/MCP products, run pipelines, and monitor freshness, validation, and data product health.
Open your workspace.
Sign in with your TwinEdge account to access your enabled modules.
DataOps Home
Workbench landing page.
Open in appSources
Source catalog and connector status.
Open in appTag Browser
Tag and node inspection.
Open in appModels
Model definitions.
Open in appInstances
Mapped asset instances.
Open in appCanonical Graph
Relationships and graph context.
Open in appPipelines
Pipeline builder and runs.
Open in appAPI and MCP Products
Data products for external clients and agents.
Open in appMonitor
Freshness, validation, and run status.
Open in appContinue the workflow.
Build it around your operation.
Request DataOps readiness help when mapping, standards, or source quality blocks the first workflow.