Engineering / Project story
The device is replaced. The work isn’t over.
At a previous job at an oil-and-gas production facility, I worked with measuring instruments, maintenance, and verification records. One device replacement meant updating several disconnected records. I built a bot prototype to connect the work and its data — and found my way into software engineering.
AI reconstruction of my story01 / The work I wanted to change
Replace once. Update four records.
Identify the position and device
Why this step?
Find what is installed, then check its card and verification date in another record.
Hands-on work: 4Record work: 0Illustrative effort · person-minutes
Inspect the example records · 0 / 2
A · verification due
Position 01 · A installed
B · available
Job identified
The work was real. So was the time it took.


AI-generated reconstructions based on my story, including my likeness. These are not archival photographs of my former workplace.
02 / My contribution
I knew the route. I wanted to change the routine.
The work behind the equipment
As an instrumentation engineer, I first organised Excel around real inspection routes and verification dates. A busier area exposed the bigger problem: the same event scattered across several records.
A workflow that follows the technician
Give the device and its installation position separate identities. Use QR codes and guided actions to capture what happened, then reuse that information in stock, history, and documents.
My first working software system
I taught myself Python, built the Telegram prototype and its data model, and learned to keep users’ conversations independent. Then I began separating the backend so other interfaces could follow.
03 / The workflow I was building toward
Record once. Reuse everywhere.
Identify the position and device
Why this step?
Scan the position and the device. Keep their identities separate, with the relevant record at hand.
Hands-on work: 0Record work: 0Illustrative effort · person-minutes
One connected backendExplore the example state
Equipment, assignments, stock, and verification belong to one relational data model. They aren’t separate spreadsheets to maintain.
- Physical instruments
- A · Installation
B · Stock - Installation position 01
- Device A
- Available stock
- A 0 B 1
- Verification of A
- Due
This cycle’s action history 0
04 / What the change could buy back
Keep the maintenance. Reduce the repeated entry.
An illustrative full-cycle workload: 30 minutes of hands-on work and 120 minutes of record work, summed across people. Adjust the documentation-time target.
Hands-on work: 0.5 person-hours / Record work: 2 person-hours
Hands-on work: 0.5 person-hours / Record work: 0.5 person-hours
Record-work time reclaimed per cycle
75% · Less copying and reconciliationScenario, not a measured result. The 70–80% range is a design target for documentation effort only. Required checks, signatures, and lab work remain; lab processing and waiting time are excluded.
See the example time budget
| Operation | Hands-on work | Fragmented workflow: Record work | Proposed workflow: Record work |
|---|---|---|---|
| Find the job | 4 | 8 | 2 |
| Replace | 12 | 32 | 8 |
| Send to lab | 5 | 24 | 6 |
| Verification | 0 | 16 | 4 |
| Receive | 6 | 20 | 5 |
| Restock | 3 | 8 | 2 |
| Report | 0 | 12 | 3 |
| Total | 30 | 120 | 30 |
Technical side / The logical architecture
From a scan in the field to one shared system.
Follow the paths. Hover or tap an object to explore its role in the overall idea.
05 / What actually happened
A working prototype. A new direction for me.
The bot worked
Authentication, equipment lookup, QR identification, and guided actions in a Telegram prototype.
One connected workflow
The full lifecycle and time savings shown here were the goal. They weren’t validated in operational deployment.
I became a software engineer
I left the industrial role to build software professionally. Without the live workplace, I eventually closed the project.
I wanted to give people their time and energy back — so their skill could go into work they were proud of, instead of being spent copying the same facts.