User instructions

Open asset details and photographs

Connected asset workspace: identity, recorded custody and linked work

Open Asset details from Admin Inventory, use the browser asset link, or scan the item's project-specific label. The same item ID is used; nothing is verified, acknowledged, moved or saved simply by opening the page.

Find the record you need

Overview shows the asset reference, serial, inventory, recorded location, containing boxes, responsible contact, quantity and notes. The summary shows certificate records, open maintenance and accessible Tasks. Counts are limited to your permissions; they are not a completeness check or an “equipment ready” decision. Unknown quantity is not zero.

Documents & photographs links to the actual certificate records and their source files. Current records appear first; archived and superseded revisions are separately expandable. Draft, withdrawn, missing-expiry and not-yet-valid states remain explicit. Identification photographs are not work-completion evidence. In either interface choose Load identification photos; browser results show a visible success or unavailable state.

Maintenance separates open orders from completed/cancelled history. Open orders show overdue, due within seven days, scheduled or undated status. Open the work order to review its instructions, evidence and approvals. Enabled maintenance cycles create one next order after saved completion. Pending follow-ups needing review are shown separately, not buried in completed history. Existing orders remain one-off unless a manager enables a cycle.

Linked tasks shows only Tasks whose saved verification scope or explicit record link contains this item and which your current account may view. Completed/cancelled tasks are separately expandable. Opening the asset does not read a task alert. A box-only task does not automatically apply to its contents. General log issues are not guessed from names or serial numbers; review them in Logs.

Movement history loads saved changes, allocations, dispatches, receipts and placements only when requested. Browser history is inline; Admin opens the existing item-journey window. Actual event times are distinguished from saved record times. Missing events and dates are not invented.

Contents shows the direct child records of a box, with archived children separate. Open a child box for its contents or use a containing-box link to move up the hierarchy. Finding a box does not verify everything inside it.

Custody is not live positioning

In transit, the inventory location is explicitly labelled Last recorded inventory location, not the item's confirmed present position. Received items awaiting placement show their Recorded holding location. Use the authorised Fleet receipt/placement workflow; quarantine release is separate. Project workspace access alone does not grant Fleet access. Ordinary browser movement controls are not offered for archived, in-transit, awaiting-placement or quarantined items; server permission and state checks remain authoritative.

Edit, refresh and keep your evidence

Notes, low-stock settings, photograph upload, certificate creation and linked maintenance retain their existing forms and permissions. Photos are PNG/JPEG up to 20 MB within the supported pixel limit; the stored identification photo is a resized JPEG. Removing it from the gallery retains earlier audit evidence.

The browser needs the hub connection for this page and its attachments. The “records loaded/checked” time is a successful read, not a saved change. Failed asset loads remove previous summaries rather than presenting them as current; failed history and photographs show unavailable with a retry/refresh path. Admin reads the local project. This is not a general offline asset cache.

Chosen upload files are not offline drafts: keep originals until upload succeeds. Supported metadata forms retain their existing device drafts. Never clear unsent work. Full project backups/history-bearing transfers preserve asset profiles, files and links; narrow current-item inventory packages do not. Review private data and dependencies before sharing a project transfer.