# Production data that used to stop at the panel.

> At DORTEK (dortek.com.tr), the production line already knew its own output, downtime and cycle times — but nothing above it did. Signals from the PLC units now travel through a gateway into the cloud, where they become dashboards and feed the stock and planning decisions behind them.

- **Email:** hello@zhajmohamad.com
- **URL:** https://zhajmohamad.com/projects/industrial-automation

## What was built.

PLC lines to a gateway, gateway to the cloud, cloud to the dashboard and the stock record — with the reading side kept strictly out of the control logic.

- **Reading the line** — Tags and counters read from the PLC units at the rate the process actually changes, without writing anything back into the control logic.
- **The gateway** — A device between the plant network and the internet that buffers locally, so a dropped link delays the data instead of losing it.
- **Dashboards for two audiences** — A live view for the floor and a period view for planning — the same data, different questions.
- **Into stock and planning** — Production counts feeding the systems that decide what to make next, so the recorded number and the produced number are the same number.

## The situation.

The information existed. It simply had no route out of the building.

- **Counted by hand at shift end** — Numbers arrived the next morning, too late to change anything about the day they described.
- **Downtime was a memory, not a record** — Nobody could say how long a stop lasted or how often the same cause repeated.
- **Stock and production drifted apart** — Corrections meant a physical count, and the count was already out of date when it finished.
- **The plant network was never meant to leave** — Getting the data out safely was as much of the problem as reading it.

## Related systems.

- **Edip Saat (edipsaat.com)** — Machine-read input replacing manual entry, so the record is created where the event happens.
- **Frankenspalter (frankenspalter.ch)** — The same integration discipline applied where both ends are software.

## Questions people ask.

**Does this interfere with the production line?**
No. The integration reads and never writes back into the control logic, and the gateway sits alongside the plant network rather than inside the control path. That separation is what makes it safe to add to a line that is already producing.

**What makes this different from a SCADA screen?**
A SCADA screen shows the process to the operator standing in front of it. This carries the same data out to the systems that make commercial decisions — stock, planning and reporting — which is an integration problem rather than an automation one.

## Related specialisms.

- [Industrial IoT & PLC integration](https://zhajmohamad.com/industrial-iot)
- [Business process automation](https://zhajmohamad.com/business-automation)
- [Custom API & system integration](https://zhajmohamad.com/system-integration)
- [Custom e-commerce development](https://zhajmohamad.com/ecommerce)

---

Tell me what you are trying to build, automate or scale. You get a straight answer on fit within a day — and a name to call if it is not me.