P4 Software / activoHQ English

Mobile app (RFID inventory)

Mobile app (RFID inventory)

Overview

ActivoHQ Mobile is the Android app used on the floor to count Assets with an RFID reader and to run actions on an asset without going back to a computer.

With it your team can: start or resume a count session, read the Assets' RFID tags - watching live how many are Found, Missing and Unexpected - submit the reads, reconcile and review the variance; plus check out, check in and dispose of an asset from the handheld itself.

The app is offline-first: if the connection drops, actions are saved on the device and sync themselves once the signal is back.

It is available in English and Spanish and connects to the same inventory as the web application.

Requirements

Requirement Detail
Device An Android handheld; for RFID reading, a Zebra device with an integrated reader or a sled (for example MC3300R, MC3390R or a TC with RFID).
Account An ActivoHQ user with access to the company being counted.
Tenant (subdomain) Your company's identifier, the same one you use in the web address (for example acme in acme.activohq.cloud).
Connection Needed to sign in and sync; counting and actions work offline.

Without an RFID reader, the app runs in mock mode for training and testing: the count screen shows the notice MOCK RFID - no hardware reads, and the reads do not come from real hardware.

How to use it

Sign in

  1. Open ActivoHQ on the handheld.
  2. Fill in Tenant (e.g. acme), Username and Password.
  3. Tap Sign in.
  4. If your account has access to several Companies, pick one under Choose a company.
  5. The EN / ES buttons switch the app's language.

The Count sessions screen

Once in, you see Count sessions, with the company's sessions and their status. From there you can:

  • New count - opens a new session.
  • Tap an existing session to continue it.
  • Assets - search for an asset to run actions on it.
  • Reader - open the RFID reader Settings.
  • Sign out - leave the account.

An indicator shows how many actions are waiting to sync; tap it to open the Sync Queue.

Count Assets

  1. Open the count session.
  2. Under Location, scan the place's barcode or type it into Scan or type a location code.
  3. Tap Scan (or pull the handheld's trigger) to start reading tags.
  4. The counters update live:
    • Expected - Assets that should be in the location.
    • Found - read and expected.
    • Missing - expected but not seen yet.
    • Unexpected - read but not belonging to that location.
    • The footer shows the total reads.
    • With the matching option on, each tag read produces a beep and a vibration.
  5. Tap Submit reads to upload them to the server.
  6. Tap Reconcile to calculate the count's result.

Review the variance and close

Variance shows the result per asset: Found, Missing, Moved and Unexpected. When the count looks right, tap Close session.

The same information is available in the web application, under Audit > Count sessions and in the RFID Audit Variance report.

Actions on an asset

  1. From Assets, scan the asset's barcode or search for it by code or name.
  2. Open the asset: you see its Status and Availability.
  3. Run the action:
    • Check Out - hand the asset to an Employee, with an Expected return date, Notes and, optionally, a photo. If the asset's model requires it, you must tick I accept the agreement above (the EULA). Confirm with Confirm check-out.
    • Check In - take the asset back, giving the Condition, a Damage report, Notes and an optional photo. Confirm with Confirm check-in.
    • Dispose - record the disposal with a Disposal date, Retirement (no proceeds) or Proceeds, and notes. Confirm with Confirm disposal.

Working offline

If there is no connection when you run an action, the app answers Saved - will sync when back online. and queues it.

In the Sync Queue you see each pending action with its type (Check Out, Check In, Dispose), its date, its status (Pending, Synced, Failed) and the last error if there was one. Pending actions are sent automatically once the connection is back, in the order they were recorded. An action rejected by the server is left as Failed for a human to review: fix the cause and tap Retry.

Reader Settings

Under Reader Settings you can set:

Option What it is for
Connection The reader type: Integrated device, Bluetooth sled or USB.
Scan for readers Detects the available readers.
Mapped reader (name / prefix) Pins a specific reader; left blank, the first one found is used.
Power The antenna's power, as a percentage. Less power cuts down reads of Assets in adjacent rooms.
Reader ID (stamped on reads) The identifier written into each read, useful when several handhelds count at once.
Beep & vibrate on each tag Audible and tactile confirmation of each read.
Test connection Checks that the reader responds.
Language English or Spanish.

Save with Save. A count session can be resumed after leaving the app.

Notes

  • The app always works against the company chosen at sign-in; to count another company, sign out and back in.
  • Assets are identified by their RFID EPC; an asset with no EPC recorded on its record shows as Unexpected when read. Record the EPC on the asset's record in the web application.
  • Barcode scanning uses the Zebra handheld's own scanner (DataWedge).
  • Lowering the antenna's Power is the most effective way to avoid reading Assets in another room.
  • Actions run from the phone land in the asset's history exactly like those done from the web.

Troubleshooting

Symptom Likely cause Resolution
You cannot sign in. The tenant, username or password is wrong, or there is no connection. Check the company identifier (the same one as the subdomain) and your connection.
MOCK RFID - no hardware reads appears. The app is in mock mode, or no reader is connected. Use the build installed for the Zebra handheld and check the connection under Reader Settings.
No readers are detected. The wrong connection type, or missing Bluetooth permissions. Choose the right Connection, accept the permissions Android asks for, and tap Scan for readers.
Assets in another room are being read. The antenna power is too high. Reduce Power in the reader Settings.
Many Assets show as Unexpected. The Assets have no EPC recorded, or the location given is not the right one. Check the location code and record the missing EPCs on each asset's record.
An action is stuck at Failed. The server rejected the operation (the asset was already checked in by someone else, for example). Review the error message, fix the situation and tap Retry.
The pending indicator does not go down. There is no connection, or there are actions in Failed status. Check the connection and review the Sync Queue.

Related

Was this page helpful?

Previous Location transfers Next Reports