Obsigen · Use cases · on your computer (Obsigen Runtime)
Maintenance
A maintenance engineer who prepares a weekly line downtime report for the team briefing.
1Input
An export from the production system (start, stop, cause, line) and a photo of the motor nameplate.
2Process
- reads the spreadsheet and the photo; when a column is missing, it asks instead of guessing
- calculates downtime frequency and repair time with code - on your computer, in the OS sandbox
- draws a chart of downtime by cause and checks it before handing it over
- prepares the briefing note - every number points to the spreadsheet row it comes from
- saves the report and the chart in your folder; running code requires consent on the device
For engineers
- input:
downtime_line3.csv+nameplate.jpg; a follow-up question when something is unclear - MTBF / MTTR computed by code in an isolated environment with a closed network; chart and a docx note
- output:
downtime-report.docx+chart.pnginObsigen/<date>/via Obsigen Runtime; consent in a dialog on the device
3Result
Report and chart in your folder - on your computer (Obsigen Runtime).
4Where the data is
The spreadsheet and the photo are stored in a folder on your computer; the model receives what the task requires. Consent to run code is given in a dialog on your device.
where it runs spreadsheet, code and chart: your computer · model: provider in the EEA · report: your folder
5Company glossary
Terms from this process and how Obsigen remembers them - sample entries in the company glossary:
- Line 3
- a production-line name, not a row number - Obsigen does not confuse it with row 3 of the spreadsheet
- MTTR
- measured from the failure report, not from the stoppage - as you define it
- briefing
- Monday 7:30 a.m.; the note fits on one page
This process in a demo
We show it on an example you bring (line downtime spreadsheet + photo of the nameplate) - no confidential data, online, in 45 minutes. Then a quote and deployment on dedicated infrastructure.