Can we build our own reports without going through IBITEK?
Yes. The software includes a report designer and a dashboard designer. Site teams build their own outputs with no development work, after training delivered at commissioning.
Yes. The software includes a report designer and a dashboard designer. Site teams build their own outputs with no development work, after training delivered at commissioning.
A stoppage describes a production loss. A breakdown is just one possible cause among others: waiting for material, a changeover, cleaning, safety, or a planned stop.
Yes. A wrong classification can be reworked with a full audit trail. History is not quietly rewritten, which keeps previously published analysis auditable.
Yes. Because detection relies on signals rather than declaration, short stoppages are logged the same way as long breakdowns. Added together, they often turn out to weigh more than expected.
The reference set is organised in stoppage types and sub-types, then cause families and detailed causes. This structure guides the operator's choice and makes classifications comparable between teams.
Stoppages are detected from the signals sent back by equipment, with no prior declaration needed. Duration and the equipment concerned are logged automatically, then classified by the operator.
Yes. Instruments are declared in the data model and their results can be picked up directly, which removes double entry and the main source of transcription error.
Yes. Results are kept and can be looked up by product, by sampling point or by date range, together with the limits that applied to them at the time of testing.
Yes. Each value is compared against the limits in the test plan currently in force. An out-of-specification result is flagged and tied to the product concerned, so you can act before it ships.
Sampling points, their frequencies and their types are defined in the site data model. Every sample logged is tied to the product, the point and the period concerned.