All projects

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 Mike in unbranded blue workwear and protective headgear inspecting an instrument at an industrial facilityAI reconstruction of my story

01 / The work I wanted to change

Replace once. Update four records.

Illustrated reconstruction · fictional objects and effort estimates
01 / 07

Identify the position and device

Why this step?

Find what is installed, then check its card and verification date in another record.

Effort spent so far4 / 150 min

Hands-on work: 4Record work: 0Illustrative effort · person-minutes

Inspect the example records · 0 / 2
Equipment register

A · verification due

Position table

Position 01 · A installed

Stock ledger

B · available

Documents & reports

Job identified

The work was real. So was the time it took.

Generated reconstruction of a technician in blue workwear copying instrument details between paper records beside a laptop
After the field work: the same details, entered again.
Generated reconstruction of hands carefully inspecting a pressure gauge at a metrology workbench
The skilled work I wanted people to have more time for.

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.

I noticed

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.

I designed

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.

I built

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.

Illustrated reconstruction · fictional objects and effort estimates
01 / 07

Identify the position and device

Why this step?

Scan the position and the device. Keep their identities separate, with the relevant record at hand.

Effort spent so far0 / 60 min

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.

State at this step
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.

    Target reduction in record work
    Fragmented workflow2.5 person-hours

    Hands-on work: 0.5 person-hours / Record work: 2 person-hours

    Proposed workflow1 person-hour

    Hands-on work: 0.5 person-hours / Record work: 0.5 person-hours

    1.5 person-hours

    Record-work time reclaimed per cycle

    75% · Less copying and reconciliation

    Scenario, 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
    Illustrated reconstruction · fictional objects and effort estimates · min
    OperationHands-on workFragmented workflow: Record workProposed workflow: Record work
    Find the job482
    Replace12328
    Send to lab5246
    Verification0164
    Receive6205
    Restock382
    Report0123
    Total3012030

    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.

    Built

    The bot worked

    Authentication, equipment lookup, QR identification, and guided actions in a Telegram prototype.

    Intended

    One connected workflow

    The full lifecycle and time savings shown here were the goal. They weren’t validated in operational deployment.

    Personal result

    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.

    The device is replaced. The work isn’t over. | NovaFlow