Skip to content

Management and connectivity

Industrial integrations

We connect Autech with your ERP, your machines and your systems, in phases and without replacing them.

Autech connects what the plant already hasillustrative example
  • ERP

    orders and finished goods · e.g. Microsoft Dynamics

  • PLCs and sensors

    machine signals · via an industrial gateway

  • Scales

    sample weights · direct reading

Autech

one data model

  • Cameras

    counts and events · processed on site

  • Forms

    floor records · phone and tablet

  • Sheets and BI

    exports · for finance

The problem

Each system tells its own story

Orders live in the ERP, output on sheets, machines have their own screens and nobody connects them. The result is double entry and discrepancies argued over at month end.

In development

Sound familiar?

  • Orders are copied by hand from the ERP to the floor.
  • Finished goods are recorded twice.
  • Machine data nobody looks at.
  • Differences between system and physical inventory.

What we ask first

Before proposing anything, we understand what happens on your line today.

  • Which information is entered twice today, on the floor and in the system?
  • When a figure doesn't match between floor and ERP, who discovers it and who fixes it?
  • Which systems and interfaces does your IT team have available?

How we approach it

We integrate in phases, starting with what gives the most value with the least risk: usually reading production orders. Each integration is designed around the system, its interfaces and your IT team's permissions.

  1. 1. We survey existing systems

    ERP (for example, Microsoft Dynamics), machines, PLCs, scales and databases.

  2. 2. We start by reading

    Orders and products are read first; writing back to the ERP comes later, once plant data is validated.

  3. 3. We connect the floor

    Machine and PLC signals through an industrial gateway, when they add useful information.

  4. 4. We validate with your IT team

    Access, security and responsibilities are agreed in writing.

What it takes

Software

  • Connectors to the ERP and databases based on their interfaces
  • Sync of orders, products and finished goods
  • Log of every data exchange
The full platform →

Plant equipment

  • Industrial gateway to read PLCs or machines, where applicable
  • Industrial network and managed switch on the floor
  • Edge computer to concentrate signals when needed
How we select hardware →

Each integration requires its own engineering and scoping depending on the system and its interfaces; it is defined during technical design together with your IT team.

Who uses the information

IT
Keeps control over access and over which data is exchanged.
Planning
Sees on the floor the same orders as in the ERP.
Finance
Receives finished goods that match what was produced.

Decisions it supports

  1. 01Which system is the official source for each data point.
  2. 02Which integration to do first based on value and risk.
  3. 03When to stop entering the same information twice.

How value is measured

We measure before and after, on your line. Value is shown with your data, not promises.

Duplicate entries removed
An inventory of double entries before and after each phase.
Differences between floor and ERP
Reconciled periodically during integration.
Time for an order to be available on the floor
From its creation in the ERP to the line.
Estimate the value of this problem

Let's start with one problem.

Tell us what's costing you most today. We review it with you, show how we'd solve it and estimate its value together.