AWRA OpsHub Search

AWRA Help Center

Copy link
Assets Custody Audit
01 Assets Module Guides 02 Asset Register Assets 03 Asset Labels & Scanning Assets

Asset Label Governance: Print Queue, Replacements & Label Health

Every asset label is recorded from the moment it is printed. A second label for the same asset is a replacement that someone else has to approve, so a swapped tag is noticed instead of being quietly reprinted.

When anyone can print a label at any time, a label that has worn out and a label moved onto a different laptop look exactly the same. AWRA keeps a record of each label instead: when it was printed, which label it replaced, and when it was last scanned.

First Labels: Queue, Batch, Print

  1. From the asset list or an asset page, queue a label. Queuing the same asset twice gives you the label already in the queue, not a second one.
  2. Open the Label Queue (/assets/labels/queue) and gather the queued labels into a batch. The batch keeps its print layout, so a reprint of that sheet comes out the same.
  3. Print the batch PDF, then press Mark printed. Only then do those labels become the assets' active labels, replacing any older ones. If the print failed, cancel the batch and its labels go back into the queue.

The older label sheet pages leave out any asset that already has a label in use, and anything printed from them is recorded in the queue as well, so they cannot be used to get around the rules above.

Replacements Need A Second Person

  • Once an asset has an active label, the only way to print another is a replacement request with a reason. An asset can have only one open request at a time, so asking again shows you the request already open.
  • An approver approves or rejects it, and a rejection must say why, because the requester sees that reason. The person who asked cannot approve their own request.
  • Approving puts the replacement in the print queue. The old label stays active until the new one is marked printed, so the asset is never left with no valid label.

Reporting A Problem From The Field

On the asset page or in the mobile app, report a label as unreadable, damaged, tampered or missing. The report is logged against the active label and opens a replacement request automatically, so it reaches an approver instead of getting lost in a chat thread.

Label Health

Every successful scan is counted against the active label. That lets the Label Queue and each asset page put an asset in one of these groups: Replacement pending, Not scanning, Waiting to print, No tracked label, Never scanned, Not scanned recently (no scan in 180 days) or Scanning normally. A label that has never been scanned since it was printed is usually stuck on the wrong thing, or not stuck on anything at all.

In The Mobile App

The asset screen shows the label and its health, and lets you report a problem or ask for a replacement. Approvers have a Label Replacements screen where they approve or reject requests.

Permissions

Seeing labels needs View assets. Queuing, printing, asking for a replacement and reporting a problem need Edit assets. Approving or rejecting a replacement needs Approve asset movements.

Related

See Asset Labels & Scanning and Asset Checks.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide