Lynxby DOMINION
← Back to modules

INVENTORY MODULE · TOOLS & JOBS Every tool, which job it is on and what it has cost.

The grinder went out to a site five months ago. Nobody remembers which one, and that site has already closed.

Inventory · Tools & jobs is the Lynx module with two inventories in one: tools, individualized by serial number; consumables, by quantity. It follows the whole dispatch-and-return cycle, keeps unit-level traceability and charges the cost to the job that incurred it.

Tools by serial number · consumables by quantity

Request a demo →

Add to the platform →

lynxplatform.cloud/inventario/panel

Two inventories, one module Tools and consumables are not managed the same way

The module keeps two separate planes, each with its own model, workflow and screen, on top of a shared product catalogue standardized by make, model, type and use.

  • Tools and equipmentUnits individualized by serial number, each with its state, availability, hierarchical bin code and history.
  • ConsumablesQuantity tracking: stock per warehouse, reserved quantity, available quantity and a reorder point per product.
  • Shared catalogueA single product master with unit of measure and categorization by type and by use, so items can be grouped and compared across makes.

Job workflow From request to closure, with states and roles

This is not a check-in/check-out log: it is a workflow with explicit states and a responsible role at each step. The project manager requests the material the job needs; the warehouse manager approves, adjusts and creates the shipments; the storekeeper prepares the material, picks the specific units and disposes of the return piece by piece.

  1. requested
  2. approved
  3. prepared
  4. on site
  5. return pending
  6. received
  7. completed
lynxplatform.cloud/inventario/obras · solicitud
  • The unit is picked when preparing, not when requesting

    The request says «an angle grinder». The storekeeper sees the available units of that model, picks one, it becomes reserved and the delivery note that travels with the material is generated.

  • Several shipments in each direction

    Material may go out in two shipments and come back in three, and one lorry may carry material for several jobs. Each shipment records what it carries, with its date, haulier and contact.

  • Closure has a gate

    A request cannot be completed while returned tools remain unchecked. On completion, whatever did not come back is written off as lost, consumables with no return declared count as consumed, and the cost is charged.

Today that flow is an email, a paper delivery note and the foreman’s memory. Which is why the grinder still has not turned up.

A demo with your tools →

Cost per job Three components, and only three

Every movement is understood as a dispatch to a job and its return, so the cost is charged to the job that incurred it. The breakdown can be recalculated on demand and every line traces back to the movement that produced it.

lynxplatform.cloud/inventario/obras · coste
  • Consumable usage

    Quantity consumed times the product unit cost. Whatever went out and was not returned counts as consumed when the request is closed.

  • Tool time on site

    Days each unit spent on site times its daily rate. The days are not declared: they come from the unit state history.

  • Damage cost

    Repair of a tool that came back faulty, or replacement of one written off, charged to the job where it happened.

Unit-level traceability Every unit carries its own history

Where it has been, what broke, which part and on which job. The life cycle is explicit —operational, on site, returned, out of service, under repair, written off— and every transition opens a span with its reason, its job and its dates. Returning a repaired unit to stock is a user action, not an automatism: the unit becomes available again when somebody vouches for it.

  • State and disposition kept apartOn return, each piece is disposed of one by one: returned or not; and if returned, unchecked, operational or faulty, with reason, broken part and job.
  • Filtered by whatever you are afterBy state, by text and by date range, both on the unit list and on the state-change history.
lynxplatform.cloud/inventario/unidades

Alerts What needs attention right now

A single window with everything pending, computed on the inventory itself. There are no rules to configure: all six follow from the state of the stock and the dates committed to.

  • Reorder point

    A consumable whose stock has dropped below its minimum, editable per product.

  • Overdue return

    Material that should have come back from a job on a date that has passed.

  • Returned unchecked

    Tools back in the warehouse that nobody has checked yet.

  • Shipment not received

    A return shipment that left the job and has not been closed in the warehouse.

  • Unresolved fault

    A faulty unit whose planned resolution date has passed.

  • Certificates expiring

    Equipment calibrations and certificates approaching their expiry date.

Lynx by Dominion

Your tool fleet, with the cost of every site

We prepare a demo with one of your sites: what goes out, what comes back and in what condition, and the cost left charged to it once it closes.

Request a demo →

Or write to us directly at support.dt@dominion-global.com

← Back to modules