Moving between systems should
not call for manual work.

APIs and industrial interfaces connect the data and functions of existing applications.

An export is imported by hand, an interface delivers a new format, or the same message arrives more than once. Cases like these need unambiguous processing and traceable error paths. For a stable integration, data models, access rights and version changes have to be agreed. What also matters is how an interrupted transmission is resumed without losing information or processing it twice.

IQstruct Engineering develops APIs, clients and adapters for new architectures and for existing system landscapes. REST, GraphQL, gRPC and SOAP connect applications; OPC UA and MQTT open up industrial data. With legacy systems that are hard to reach, a protocol analysis or a retrofit can become necessary.

Start now at no cost

In a free first conversation we clarify which systems are to come together, which is the leading system and what traceability is required.

See the person in charge

Scope of services

Open up existing systems in a targeted way

Existing interfaces and documentation are checked before implementation.

Secure access appropriately

Authentication, certificates and roles are coordinated with the target systems.

Design changes to be compatible

Versioning, validation and retry strategies support reliable data handovers.

Connections for new and existing systems

IQstruct Engineering develops APIs, clients and adapters for new architectures and existing system landscapes.

REST, GraphQL, gRPC and SOAP connect applications; OPC UA and MQTT open up industrial data. In new projects, interfaces and data flows are designed to suit the architecture from the start. In existing landscapes, we first check systems, interfaces and documentation.

For proprietary or poorly documented protocols, we carry out a protocol analysis where needed. If a legacy system cannot be connected securely with reasonable effort, we design a retrofit or the replacement of outdated components.

Network switches with connected patch cables and status indicators

Interfaces

Data moves between systems without manual transfer

Machines, plants and IT systems exchange data via suitable connections, even across technical generations.

Approach in the project

  1. An architect explains an architecture diagram with components and data paths on the wall screenAi

    1

    Plan the software architecture

    Components, interfaces and data paths are defined in an architecture diagram.

  2. A developer implements an API on the screen while a colleague reads the interface specificationAi

    2

    Implement interfaces

    REST, gRPC, SOAP or identity connections are developed to suit the architecture.

  3. Two women test interface calls and responses against the target system on the screenAi

    3

    Test the integration

    Calls, authentication and error cases are tested against the target systems.

  4. A developer follows response times, error rates and server load on the screen, a server rack beside herAi

    4

    Monitor the application

    Logs, server load and status displays are reviewed together.

When a transfer fails

Timeouts and retries

Defined strategies repeat failed transfers in a controlled way.

Duplicate processing

The interface recognises repeats and processes them only once.

Versioning

Schema validation and versions allow the systems involved to evolve.

Project experience

Industrial procedures implemented in software

Route cards and technical information are kept in applications instead of on paper.

IQstruct Engineering has digitised a route card procedure that was previously handwritten and developed a tool management system for measurement records and settings. Applications like these connect the technical task with structured data storage. Interfaces and operation have to match so that information stays available within the workflow. This experience complements the development of our own products such as Aurora, in which data acquisition, processing and a web interface come together.

Frequently asked questions

We are glad to answer your detailed questions in a personal conversation.

What happens if a legacy system cannot be connected sensibly?

Then we examine a retrofit or the replacement of the outdated component as a lasting solution.

How is access secured?

Depending on the system landscape, with OAuth 2.0 or OpenID Connect, SAML, API keys, certificates or mutual TLS, supplemented by roles and rights.

Which API technologies do you implement?

REST, GraphQL, gRPC and SOAP, and for industrial data additionally OPC UA and MQTT.

First conversation

Arrange a free first conversation

Describe your task. We agree a date and discuss the possible project scope.

  1. Notebook on a desk with an open calendar and a selected appointmentAi

    1

    You request an appointment

  2. Experts at a meeting table discussing an extensive software architecture on the screenAi

    2

    We discuss your requirements

  3. Workstation with a measuring application built with graphical programming and a web interfaceAi

    3

    You receive a quotation for the agreed scope

Philipp Niemann-Stryczek
Philipp Niemann-StryczekManaging DirectorLeads the company on the commercial side and answers questions on IT/OT security, asset administration shells, compliance and research projects.
Free first conversation

Describe your task in the contact form. We come back with a proposed date.

Arrange a first conversation

Not quite what you need?

Discover further suitable services.

Protocols and interfaces

Open up machine information via OPC UA, controller adapters and other existing interfaces.

Integrating AI into existing systems

Connect assistants with ERP, office applications and existing data sources.

Backend and distributed systems

Develop backend services that connect industrial data, business logic and applications.