IMtech

Service

Tracking systems

We build systems in which every object — a part, a shipment, a transport request — has a status and a history: who did what to it and when. Staff record a step from their phone; the manager sees the picture in the panel straight away.

Animation: dots travel along a route between nodes — work areas and hand-over points — and a status tag lights up above each node they pass.

When you need it

Situations that bring people to us for this service.

  • You can't see where things are

    Finding out where a part, a load or a request is means phoning round and asking again.

  • Paper sheets and verbal hand-overs

    Who handed what to whom, and when, is written on paper — or not written down at all.

  • Discrepancies are spotted too late

    A mistake in a route or a dispatch is noticed only once it has become a problem.

  • No signal on the shop floor or on the road

    Staff can't record a step because the network has dropped, and data is lost or duplicated.

  • Off-the-shelf services break the process

    A ready-made solution forces you to bend your own statuses and roles to fit it.

What's included

  1. Process analysis

    Together with the people who work in the process, we define the objects, statuses, roles and hand-over points.

  2. Objects with a history

    Every object has a status and a log of states: what happened to it, who did it and when.

  3. A mobile workstation

    Staff scan a barcode or record a step from their phone and see at once whether the operation was accepted.

  4. A manager's panel

    Changes show up immediately, and notifications arrive on the phone.

  5. Discrepancies and rejections

    If a step doesn't match the route or the rules, the system records a conflict with its reason instead of quietly accepting it.

  6. Offline work

    Scans and operations are stored on the phone and sent as soon as the connection returns — none is counted twice.

  7. Role-based permissions

    Only people allowed to change a record can do so — for example, those assigned to that work area.

  8. Data exchange with your accounting system

    Staff lists, reference data and barcodes sync with the software you already run.

What you get

  • A description of objects, statuses and roles
  • A prototype of the key scenario on your data
  • A mobile app for staff
  • A web panel for managers
  • A link to your accounting system
  • A pilot on real objects, plus support

The project path

From the first conversation to daily use

Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.

  1. 01

    Getting to know the task

    You describe the process and what gets in the way. We reply by email with questions and arrange a call.

  2. 02

    Discovery

    We study the process with the people who work in it and write down what the system must change and how we will check it.

  3. 03

    Prototype

    We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.

  4. 04

    Pilot

    We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.

  5. 05

    Launch and growth

    We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.

Systems where we have already done this kind of work.

Technology in these case studies

  • Strapi
  • PostgreSQL
  • Socket.IO
  • REST API
  • JWT
  • Excel
  • PDF

Questions about this service

Why not use an off-the-shelf tracking service?

An off-the-shelf service works well when your process matches its model. When your statuses, roles and rules are your own, we build the system around them — and it answers not only “where” but also “who did it and when”.

What if there's no signal on the shop floor or on the road?

Work doesn't stop: operations are stored on the phone and sent as soon as the network is back. No scan is counted twice.

Can you connect our GPS trackers or sensors?

Exchanging data with what you already run is one of our principles. Whether your particular devices can be connected we'll say once we've seen them: in our published case studies, tracking works through scans and statuses, not GPS.

Can we start with one work area or one process?

Yes. First we build a prototype of the key scenario, then run a pilot in your environment, and only after that decide together whether to extend the system.

Have a project with no ready-made solution?

Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.

Get in touch