Solutions · Automotive & parts
Keep every line on takt — and every part traceable
For car makers and their parts suppliers: Andon with escalation, plan versus actual per shift, OEE per machine, traceability per part and maintenance for robots, presses and moulds — on one platform.
- Andon with escalation
- OEE per machine
- Traceability per part
- MC Protocol, S7, Modbus, OPC UA
Live line data
Real lines, live readings
Counted and measured by the PLCs every second — not written on a board at the end of the shift
Live · MC Protocol
Live · Siemens S7
Live · Modbus · OPC UAPhotos: Unsplash. Readings are sample data.
What automotive plants deal with every shift
The customer's line waits for your parts — every stop and every claim costs money
A press or robot fault stops the whole line, and the delivery window to the car maker does not move.
Downtime, slow cycles and rejects are written down from memory, so the real losses never show.
When a claim arrives, nobody can say which shift, which station and which parameters made that part.
Weld tips, dies and moulds need care by strokes and shots, not by calendar — and the counts live in a notebook.
What AssetGrid does for your plant
Production, OEE, traceability and maintenance on one set of machine data
Production & Andon
Plan versus actual, at takt, on every line
Set up lines, shifts and breaks once. AssetGrid paces the plan to takt, counts actual and direct-OK parts from the PLC, and turns every Andon call into a timed event.
- Plan, actual and direct-OK counts per line and shift, live on the line screen and the phone
- Andon calls escalate from line leader to maintenance to the plant manager when nobody responds
- Every stop recorded with its reason, so MTBF and MTTR come from real events
OEE
OEE per machine, measured — not estimated
Assign each machine its run, count and reject signals. AssetGrid samples them and builds availability, performance and quality hour by hour.
- Planned time comes from your shifts and breaks
- Losses by machine, hour and reason: changeovers, small stops, slow cycles and rejects
- Compare lines and shifts, and export to Excel for the daily production meeting
Traceability
Every part with its serial and its process data
When a station signals that a part is done, AssetGrid records its serial number with the values you chose: torque, weld current, film thickness, oven temperature.
- Recorded on the station's done or OK signal — no scanning by the operator
- Search by serial, date or shift and answer a customer claim in minutes
- The data your quality team needs for audits, kept for as long as you need it
Maintenance
Maintenance by strokes, shots and welds
Link a machine's counter to its asset, and PM falls due by count as well as by date. Faults from Andon open work orders with the machine's history.
- PM by press strokes, mould shots, robot welds or running hours — counted from the PLC
- Similar past fixes suggested when a fault repeats
- Spare parts with suggested reorder points from real use: weld tips, nozzles, heaters, sensors
Every machine on the shop floor, in one asset register
Organised by plant, line and station — each with its QR label, history, PM plan and spare parts
- Welding & handling robots
- Presses & dies
- Injection moulding & moulds
- Paint booths & ovens
- CNC & machining
- Conveyors & AGVs
- Torque tools & testers
- Compressors & chillers
- Power meters & panels
- Jigs, fixtures & gauges
Example
Press 3 stops at 14:22 — what happens next
Called, fixed and counted before the next delivery leaves
- 01
Signal
The press PLC's fault bit and stop reason reach AssetGrid through the collector.
- 02
Andon & escalation
The line leader and maintenance are called; if nobody responds in time, it escalates to the supervisor.
- 03
Work order
A work order opens on PRS-03 with its history and the fixes that worked for similar faults.
- 04
On site
The technician scans the press's QR code, replaces the clamp sensor and records the part used.
- 05
Counted
The stop is in OEE and MTBF, and the shift's plan versus actual shows what it cost.
Works with the PLCs your lines already run
A small collector on the plant network reads the registers you choose — your PLC programs stay as they are
Mitsubishi PLCs (iQ-R, iQ-F, Q and L series) read directly over Ethernet: word and bit devices.
S7-1200 and S7-1500 data blocks and markers on the line's Siemens PLCs.
Robot controllers, power meters, VFDs, temperature controllers and RS-485 devices through a gateway.
Existing SCADA and MES servers over OPC UA; IoT sensors and test benches over MQTT.
See AssetGrid on one of your lines
Start with one line: Andon, plan versus actual and OEE from the PLC you already have, then add traceability and maintenance. Every plant is scoped and quoted on its own.
Questions from automotive plants
Do we have to change our PLC programs?
Usually not. The collector reads the registers that already hold counts, states and faults. Where a signal is missing, such as a part-done bit for traceability, your PLC engineer adds it once.
Which PLCs can it read?
Mitsubishi over MC Protocol, Siemens S7, anything with Modbus TCP, OPC UA servers and MQTT devices. One collector can read several PLCs of different makes.
Does it help with customer and IATF audits?
It keeps the records auditors ask for: maintenance history and PM compliance per machine, traceability per part, and downtime with reasons. Your quality system stays yours.
Can we start with one line?
Yes. Most plants start with one line or one machine group, see the numbers for a few weeks, then add the next lines.
What happens if the network drops?
The collector keeps reading and stores the data on its own disk, then sends it when the connection is back, so counts and traceability records are not lost.