ASM OIB: SMT Line Software Integration

In a modern industrial electronics factory, the value of an SMT line is not measured only by the placement speed of the pick & place machines, but also by how well those machines "talk" to each other and to the company's business systems. This is where the ASM OIB comes in: the ASMPT software platform that acts as a broker of production data, collecting the operational information from the machines on the line and making it available to MES, ERP and shop-floor systems. In this technical guide we explain what the OIB is, how it is structured, which industry standards it relies on and what the concrete use cases are. ElectrONIK Lab handles ASM OIB configuration and supports the integration of SIPLACE lines with the MES, throughout Italy. The person who does it has worked on ASMPT/SIPLACE lines since 2021: for four years as a technician at a service company, and now with ElectrONIK Lab (about us).

1. What the ASM OIB is and what it is for

The OIB is a data middleware designed for the SMT environment: it acts as the link between ASM software packages and is the intermediary that collects, normalises and correlates the production data of the machines and exposes it to the different actors on the production floor. Without a broker of this kind, every machine would be an island: it would produce valuable data (cycles, errors, material consumption, placement results) that would nevertheless stay confined inside the machine's own software, difficult to collect and correlate.

This is what the OIB is for. It exposes the machines' information in a common format and makes it available to higher-level systems — a MES that has to schedule production, a traceability system that needs to know which component ended up on which board, a dashboard that has to calculate OEE. At the same time, it receives from the business systems the information the line needs: production orders, recipes, setup data. In short, the OIB connects independent machines into a line whose data reaches the business systems.

2. Architecture: the OIB as the broker of line data

To understand the OIB it helps to picture it as an intermediate layer (middleware) placed between the machine level (OT) and the information systems level (IT). On one side it connects to the controllers and the software of the machines on the line; on the other it exposes interfaces towards MES, ERP and shop-floor applications. In between, it collects, normalises and correlates the data.

This broker architecture brings a structural advantage: it decouples those that produce the data from those that consume it. A machine does not have to know which and how many systems will use its information; it makes it available to the OIB, which in turn exposes it to the systems concerned. Adding a new consumer (a new KPI dashboard or a traceability system, for example) does not require reconfiguring every machine, but connecting to the data hub. The same applies in reverse: the commands and the data coming from the business systems reach the machines through a single, consistent connectivity point.

Role on the shop floor

The role of the OIB is therefore that of an orchestrator of line data. It concentrates in one point the connectivity that would otherwise be fragmented into dozens of point-to-point integrations, each to be developed and maintained individually. Fewer custom integrations means fewer breaking points, lower maintenance costs and greater robustness of the whole shop-floor information system.

3. Connectivity and standards: IPC-CFX and IPC-Hermes

The strength of an information broker depends on the standards it speaks. The OIB relies on the two reference standards of the modern SMT industry.

The IPC-CFX (Connected Factory Exchange) standard defines a common language for the exchange of production data between machines and systems. It is the "what" is exchanged: standardised messages on production events, material consumption, errors, maintenance and quality results. Thanks to CFX, an ASMPT pick & place machine and an AOI system from another supplier can publish their data in a format that the MES interprets in the same way, with no ad hoc translators.

The IPC-Hermes standard (based on, and the successor to, SMEMA) concerns instead "how" the boards move along the line: it is the board-to-board handshake protocol between adjacent machines. While classic SMEMA handled only electrical transfer signals, IPC-Hermes adds a digital data exchange (the board barcode, for example) that accompanies the physical product from one station to the next. This is the foundation of product traceability along the line: every machine knows exactly which board it is working on.

4. Traceability and data collection

Traceability is one of the main reasons why industrial electronics companies invest in software integration. In sectors such as automotive, medical, aerospace and critical industrial applications it is often a contractual requirement: knowing, for every board produced, which components were mounted (down to the lot and the reel), on which machine, with which process parameters and with which inspection result.

The OIB collects and correlates this data at the very moment it is generated. It knows which reel (and therefore which component lot) was loaded on which feeder at the time of placement; it links this information to the identity of the board passing through, thanks to IPC-Hermes; it aggregates the process events via IPC-CFX. The result is a complete genealogy record: the production history of every single product, reconstructable after the fact. Among other things, this enables selective recalls: if a component lot turns out to be defective, the boards that contain it can be identified exactly, without having to stop the entire production.

5. Typical use cases

OIB integration is not an abstract exercise: it translates into concrete operational functions. The most recurrent use cases are:

• Line control: coordination of the machines on the line, management of the board flow and synchronisation of the work between adjacent stations.
• Setup and changeover: automatic distribution of recipes, programs and setup data to the machines, with verification of the correct setup (reducing human error during product changeover). A topic we cover in more depth in the guide on SIPLACE Pro programming and component shape.
• Traceability: collection of the complete genealogy record for every board, as described above.
• Reporting and analysis: feeding KPI/OEE dashboards and production reports with reliable, real-time data, the basis for continuous improvement decisions.

These use cases are often the first step towards genuinely connected production: once the data flows in a structured way through the broker, it becomes possible to build more advanced automation and analysis. It is the natural bridge towards the IT/OT and MES integration of the whole shop floor.

6. Benefits for the company

The advantages of an OIB integration concentrate on three fronts. Fewer errors: automated setup and verification of the correct preparation reduce manual changeover errors, which are among the most frequent causes of scrap and rework. Reliable data: the data collected automatically by the broker is consistent, complete and real-time, unlike manual records, which are subject to omissions and mistakes; this makes the KPIs and the analyses derived from them credible. Less downtime: visibility over line data makes it possible to intercept problems before they turn into prolonged stoppages and to organise maintenance on real data, as we explain in the guide on the maintenance of ASMPT SIPLACE SMT lines.

Structured, accessible production data is also the basis for automation and AI applied to production: this is where ElectrONIK Lab's B2B AI integration and automation services come in.

7. How ElectrONIK Lab supports the company with OIB integration

Configuring the OIB is not just installing software: the integration has to be planned around the real processes of the shop floor. In the analysis phase we map the machines in place, the business systems to be integrated (MES/ERP) and the objectives (traceability, KPIs, automatic setup). Then we handle ASM OIB configuration and support for integrating SIPLACE lines with the MES: traceability, line monitoring and production data. We do the configuration together with your in-house technician: they know your line, we know the software.

The work does not end with the go-live: the integration has to be maintained. Software updates, new machines on the line, MES evolutions and new traceability requirements call for periodic configuration and verification work. We do this by remote support for a large part of the diagnostic and parameterisation activities, and on-site throughout Italy when direct intervention on the line is needed.

Frequently Asked Questions