Use the platform
- REST APIUse assets, data, pipelines, and core functions in an authenticated manner.
- Java · Python · GoGet started with existing client libraries in your own applications.
IoT Data Hub · Extensibility
Building industrial data products—on an open foundation.
Developer tools open up the IoT Data Hub for custom applications, integrations, and reusable data logic without having to redesign the connection, context, or operation.
Part of the IoT Data Hub
Diese Fähigkeit arbeitet auf derselben Konnektivität, Semantik, Historie und Governance wie alle Data-Hub-Werkzeuge.
When Individual Data Products Become New Siloed Solutions
Developer tools clearly separate customer-specific logic from the data foundation and enable it to be operated in a controlled manner.
- 01
Each use case rebuilds its data foundation from scratch
Custom applications waste time on connection, context, and access before their actual business logic begins.
- 02
Special-purpose logic remains outside the platform's operations
Standalone scripts and isolated services are difficult to test, monitor, and roll out across multiple plants.
- 03
Proprietary extensions make upgrades more difficult
Tightly coupled changes make new platform versions risky and increase dependence on individual projects.
- 04
Reuse ends at team and project boundaries
Without defined APIs and extension points, adapters, operators, and applications are developed multiple times.
Four expansion levels—a shared platform operation
Engineering teams choose the smallest appropriate intervention: API usage, platform component, implemented logic, or scalable rollout.
Expand Data Flows
- Adapter SDKSupplement the platform with proprietary machine and system connections as platform components.
- Pipeline SDKMake specialized transformations and operators reusable.
Follow Your Own Logic
- ScriptsPerform targeted transformations directly within the controlled data flow.
- Functions & MLConnect long-running Java or Python analyses to live data.
Roll out in a scalable manner
- VersionierungContinue to develop extensions independently of the platform core.
- DeploymentReuse skills in a controlled manner across projects and works.
Three Ways to Expand the IoT Data Hub in a Targeted Manner
From reusable pipeline components to Python or Java functions that run continuously.
Which of our own capabilities should run on the shared data foundation?
Develop Operators
Bringing Your Own Skills to the Pipeline Editor
Proprietary fieldbus logic, specialized transformations, and analysis operators are provided as reusable pipeline building blocks.
Defined inputs, parameters, and validation instead of project-specific individual scripts.
Architecture and Operations
What Engineering Teams Need to Clarify Before Scaling Up
What interfaces and languages are supported?
The platform provides authenticated REST APIs as well as client libraries for Java, Python, and Go. Depending on the task, SDKs, script transformations, and functions are available for extensions.
Is it possible to develop custom pipeline modules?
Yes. Custom adapters and operators can include defined inputs, parameters, and validation rules, and can then be used like other building blocks in the pipeline editor.
How can we keep extensions manageable during upgrades?
Clear APIs and well-defined extension points minimize interference with the platform core. This allows customer-specific capabilities to be versioned independently and developed in a more controlled manner.
When is an API sufficient, and when does it make sense to use a platform extension?
An API is suitable for external applications and integrations. A custom module or function makes sense when logic needs to be executed continuously within data flows and reused as a platform capability.
Project inquiry
What industrial application would you like to build on the IoT Data Hub?
We'll review your integration or extension requirements and show you the best approach using an API, SDK, pipeline component, or function.
Initial consultation with a specific engineering context