API Interfaces in Production: Connected from Raw Material to Final Product

---

Introduction

Many manufacturing companies have too much data today.

You have too much disconnected data.

ERP, MES, SPS, SCADA, scales, labor, maintenance, and quality often work side-by-side. Each area has its own information. But the connection is missing.

This is exactly where API interfaces crucial.

Because modern production doesn't need another data silo. It needs a clear connection between IT and OT. From the order in the ERP, through the recipe, the scale, the PLC, and the SCADA system, to the finished product.

At OPDENHOFF, it's therefore not just about data transfer. It's about a shared truth in the value stream.

Why production facilities don't need more data silos

In many companies, important information exists but is not connected.

The ERP system knows the order.
The MES knows the production plan.
The PLC knows the procedure.
The SCADA system knows process values and alarms.
The scale knows target and actual values.
Quality has test values.
Maintenance knows maintenance data.

But who knows the whole context?

This is exactly where the problem often arises.

When systems don't communicate cleanly, media breaks, manual entries, and errors occur. Recipe data is transferred but not reliably validated. Batches are documented but not clearly linked to raw materials, scales, equipment, and products. Process data is stored but cannot be correctly interpreted later.

That costs time, quality, and trust.

API Interfaces as a Connection Between IT and OT

An API interface connects systems to each other in a controlled manner.

This isn't about transferring as much data as possible. What's crucial is that the right data is available at the right place at the right time.

Typical examples include:

• ERP transfers a production order
• Recipe data is provided digitally
• OPDPROCARE connects order, raw materials, and assets
• SPS receives released production data
• Scales provide target and actual values
• SCADA shows the ongoing process
• Charge protocols return to ERP, MES, or Quality System

This creates a continuous data flow.

The API thereby becomes the bridge between commercial planning, production control, automation, and documentation.

ERP, MES, SPS, SCADA, Scales and OPDPROCARE connect

The biggest challenge is not the individual interface.

The biggest challenge is the connection.

An order alone says nothing about the real conditions in production.
A formulation alone says nothing about the actual dosage.
A scale reading alone doesn't say anything about quality.
An alarm alone says nothing about the affected batch.

Only when this information is connected does true process knowledge emerge.

OPDPROCARE connects these levels:

• ERP and Order Data
• Formulas and production specifications
• Raw materials and batch numbers
• Silos, containers, and conveying paths
• Scales and dosages
• SPS Controls and Process Flows
• SCADA Systems and Operator Information
• Quality data and batch records
• Maintenance data and asset information

This creates a digital connection from raw material to finished product.

From raw material to finished product: A truth in the value stream

The great added value is created when API interfaces connect not just individual machines, but the entire value stream.

Then it's understandable:

• which raw material is in which product
• from which silo or container was metered
• which scale was involved
• what setpoint was specified
• What actual value was achieved
• which tolerance was active
• which mixer, extruder, calender, or process step was involved
• which batch is affected
• which process values were recorded
• What quality data is available
• which assets were needed for production

This is how transparency is created.

Not as a follow-up report, but as an active component of production.

This is especially important in industries such as the plastics industry, rubber industry, chemical industry, feed industry, and food industry. Everywhere that raw materials, recipes, batches, dosages, and quality are closely linked.

Why not every task belongs in the PLC

In the past, there were often attempts to map as much as possible in the PLC.

The PLC is strong in:

• Real-time
• Control flow
• Locks
• Security
• Machine logic
• Dossier expiration
• Signals and States

But not every task belongs in control.

Orders, recipe versions, material master data, batch information, quality, documentation, and long-term evaluations require a different level.

This is exactly where the strength of a modern IT OT architecture emerges.

The PLC remains the heart of the machine.
OPDPROCARE connects the machine to the value stream.
The API ensures controlled data exchange.

This way, each system remains in its strength.

API interfaces for formulations, orders, and batch records

API interfaces are particularly important for formulations, production orders, and batch records.

Because this is exactly where errors still occur in many companies due to manual input.

A modern system should enable:

• digital transfer of production orders
• digital handover of shared recipes
• Automatic raw material assignment
• secure transfer of setpoints
• Feedback from actual values
• Generation logs without manual rework
• Linking Quality and Production
• Feedback to ERP, MES, or Laboratory
• clear documentation of deviations

This reduces errors and builds trust.

This is especially crucial for scales and dosages. Because an incorrect recipe, an incorrect raw material, or an incorrect tolerance directly affects the product.

APIs and Scales: When Every Gram is Connected to the Order

Scales are a good example of the importance of clean API interfaces.

A scale does not simply measure weight. In the production process, this value is related to:

• Order
• Recipe
• Raw material
• Delivery batch
• File location
• Set value
• Istwert
• Tolerance
• After-run
• Shutdown point
• Production batch
• Quality release

If this information is not connected, the scale remains a single technical system.

When integrated into the value stream via PLC, SCADA, API, and OPDPROCARE, it becomes an active quality building block.

Then it can be understood what material was dosed when, where, and how.

API interfaces and OPDPROCARE

OPDPROCARE uses API interfaces to digitally map and utilize the value stream.

This is about more than just classic data collection.

OPDPROCARE connects people, machines, raw materials, orders, products, assets, and data in a common model.

The goal is:

One truth from raw material to finished product.

This allows questions to be answered such as:

• What raw materials were used for this order?
• Which scale dosed?
• What deviations were there?
• Which batch is affected?
• Which assets were involved?
• What process values belong to this product?
• What quality data is available?
• Where do recurring problems arise?

These questions are the basis for better decisions in production, quality, maintenance, and management.

The OPDENHOFF Approach: Interfaces That Work in Everyday Production

OPDENHOFF understands both sides.

We are familiar with the OT world, including control cabinet construction, PLCs, SCADA, scales, dosing, commissioning, and raw material handling.

But we are also familiar with the IT world with API interfaces, data models, digital twins, and OPDPROCARE.

This creates interfaces that not only function technically but also add value in everyday production.

Our claim is not:

We are transmitting data.

Our claim is:

We are connecting the value stream.

Data alone is not enough. Only context creates knowledge. And from knowledge comes responsibility.

Typical application areas for API interfaces in the process industry

API interfaces are particularly valuable for:

• Raw material handling
• Silo Management
• Scales and Dosing
• Mixing plants
• Extrusion
• Calendering
• Packaging
• Finished goods inventory