From raw material to dispatch, every step on record.

A monthly subscription; the price varies with how many stations get a terminal and which modules are switched on. Installation is a separate one-off item. Because you can start with a single line, the entry cost is lower than equipping the whole factory. We give a firm written quote during the demo call.

Your data stays with you: a single SQLite database file on your factory's computer, backed up every six hours, with the last 30 backups kept. Fourteen days after the subscription ends, only adding new stations and personnel is switched off; scanning, production records and Excel and PDF reports keep working. The subscription check runs offline; the system never needs to reach us.

If you want to, yes: the management screens open from a single authenticated address. No port is opened; only the e-mail addresses you allow get in, with a one-time code. Tablets do not use this route. It is not required and can stay closed.

Yes. The server is inside the factory; dashboards open over the local network. Even if the network drops, the terminal holds the scan on itself and sends it once the connection returns. The internet is needed only for optional extras: reports by e-mail, the view from outside and, if you want it, sending events to another system.

No, we attach nothing to the machine. Values such as temperature are read off the machine's own display and entered on the terminal — the same number that goes into the logbook today, except that it no longer gets lost. Nothing changes on the warranty or calibration side.

They are imported. Your product, station, route, personnel and work order lists are brought in from Excel; reports still come out as Excel and PDF. Nobody has to learn a new file layout.

The main path is one touch: when the step ends, “done”. Entering quantity and waste is optional, on the same screen. A batch's cases are grouped on one line; forty cases do not mean forty taps.

The batch production record (raw materials, steps, CCP and OPRP measurements, cleaning and dispatch in one document), the recall report, the traceability document and the period summary — as PDFs with signature fields. The document is produced from the very record on the screen.

In the EU, Article 18 of Regulation (EC) No 178/2002 requires food businesses to be able to identify their suppliers and the businesses they supply — one step back, one step forward; the recall report shows that link from supplier to customer.

Which clause, which record

Yes: iMES is an AI we built ourselves, but it is not a black box. It learns normal from your data, looks for deviation on four time scales and, when a manager asks, re-tunes its threshold from your feedback. Because it uses no neural network, it shows on screen what every alert is based on; in an audit, the answer to “what did you base that on?” is ready.

No. The application's screens and documents are in Turkish today. If you are outside Türkiye, the first conversation takes place remotely, and we will tell you plainly whether a system with Turkish screens suits your line.

It looks at two signals per machine: are stops getting more frequent, are stops getting longer — comparing the last seven days with the three weeks before. If both light up, the risk shows as high along with what it is based on. It gives no date; you decide when to do the maintenance.

It depends on your line: the number of stations, the product range and the lists you already have. We confirm the timeline after the survey, once we have seen your line. Installation runs alongside production; the line does not stop. After that we stay with your line for the first month, on site or remotely; the anomaly thresholds settle on your own data during that month.

We stay with your line for the first month. After that, signed updates are loaded from the management panel's update tab: unsigned files are refused, a backup is taken first, and a version that fails to start cleanly is rolled back automatically. With your permission we can reach the management screens remotely through an authenticated address; tablets never use it.

No. The batch number can be typed in by hand on the terminal; the number typed is valid on the station terminal too, and the batch drops into the next station's list by itself. A scanner speeds things up but is not required — you can decide by looking at the “unrecognised number” rate in the first month.

It does not. When the terminal cannot reach the server it holds the scan on itself and sends it once the connection returns. The server is a service that starts at boot; after a power cut it comes back up on its own. Backups are taken automatically and also written to the second disk given at setup.

Alerts land on the dashboards and the bell: the foreman and the manager see them on their own screens, and the same dashboard opens on the phone; at shift handover an open alert is written to the person taking over. The weekly production report arrives by e-mail as a PDF every week for any manager who asks for it.

No. The core is on in every facility; the HACCP vocabulary, CIP cleaning, planned maintenance, dispatch and scheduling are switched on or off per facility. A module that is off shows neither its screen nor its data endpoint.

Operator training happens inside the shift, at the line; production does not stop. Because the main path is one touch, there is a single screen for the operator to learn. Dashboards and role-based permissions for the manager and supervisor are set up separately, together with you. A new operator can be brought up to speed by the foreman.

Through a file bridge. Work orders are read automatically from the file your ERP drops into a folder; the end-of-day production list is written to the same folder as CSV or xlsx. Product, station, route, personnel and work order lists come in from Excel. If you want, selected events go, signed, to an address you give, and a read-only API key can be issued for Power BI or Excel. There is deliberately no live ERP connection; the installation does not wait for one.

Each plant is installed with its own server and its own definitions; station names, routes and control points differ per plant. The data stays inside the plant. If you want to compare plants on a single screen, that is a separate piece of work and is not part of the product today.