What needs attention

Who can do this

device-stock:read. Stock Overview.

Four things should not stay true for long, and TPAS counts them against thresholds an administrator sets (The thresholds). Each tile names its own threshold underneath the count.

Exception	What it means
Dispatches not confirmed	Devices were sent and nobody has signed for them. They do not work in the meantime.
Expired and still held	A card or OBU is past its validity and still with a contractor. Renew it, extend it, or get it back.
Returns not acknowledged	A contractor sent devices back and nobody at TotalEnergies has received them.
Overdue at the repairer	A device has been away with no outcome recorded.

The same four counts appear on the dashboard's Stock needing attention panel, and the Stock exceptions report in Reports lists the rows behind them. A contractor sees a fifth framing of the same thing — Awaiting your confirmation — because that is the only one they can act on.

The weekly chase

The Overdue reminders panel emails whoever is holding something up. Its own description is the most accurate summary of what it does:

"This runs on its own every night — pressing it only brings tonight's run forward. Each item is chased at most once a week, so if this week's reminder has already gone, nothing new is sent."

Note — Send reminders now (device-stock:manage) is idempotent within the week and returns no count. A quiet result does not mean it failed; it usually means everything overdue has already been chased.

The thresholds

Who can do this

A TotalEnergies administrator, setting:update. Administration → Settings.

The four day-counts are settings, not fixed numbers, and take effect immediately — no redeploy, no restart:

Setting	Default	What it governs
Dispatch acknowledgement	7 days	How long a dispatch may wait for confirmation.
Expired return	30 days	How long an expired device may stay with a contractor.
Return acknowledgement	7 days	How long a return may wait for TotalEnergies.
Repair	30 days	How long a device may stay at a repairer.

The tiles, the nightly chase and the exceptions report all read the same row, so changing it here changes every one of them at once. Every role can see the thresholds — they are printed under each tile — but only setting:update can change them, which is why Settings is not in a contractor's sidebar.

Where a device has been

Every step of the round trip writes to the device's history — issued, dispatched, received, returned, repaired, lost — with who did it, when, and the note number. Open it from a device row here, or from the badge or OBU row in Registry.

That history is the answer to the question this module exists for. Given a card reference, you can say where it is, who has it, and how it got there.