PMARS LIVE

It is a QR code on the machine.

A phone scans it. The marker is only an address. The record behind that address is what changes — and who is holding the phone decides how much of that record they are allowed to see.

Open live overviewExample scan
FIELD RECEIPT

Same sticker. Different phone. Different view.

The label on the pallet jack is not the database. It is a pointer. Scan PM-000066 or PM-000071 and the phone opens the live record for that point. What happens next depends on identity, not on reprinting a different QR for every job title.

PMARS QR label PM-000066 on a Toyota pallet jack next to the emergency disconnect warning
Physical marker on the asset. The code is the address, not the whole history.
Phone scan of PMARS Live for PM-000071 showing pallet jack PJ47 in service at 2247 hours
Phone view after scan: asset ID, type, service state, displayed hours.
WHO IS HOLDING THE PHONE

One marker. Three classes of view.

The current field prototype shows the shared live record so the loop can be tested on real equipment. The operating design is not that every stranger gets a maintenance console. Role and authorization decide the payload after the scan.

Random person / visitorMinimum public facts only, if anything: this is an identified asset, it exists, maybe a status word. No hour history, no fault notes, no ability to take it out of service. A QR on a jack is not an open admin panel.
Maintenance phoneThe working record: what it is, current service state, displayed hours, last scan, and the actions a tech is authorized to take — including marking IN SERVICE / OUT OF SERVICE and attaching what they just saw.
Supervisor phoneFleet context around the same marker: who changed status, when, which units are down, hours across the set, and review — not just the one jack in front of them.
THE OPERATING PROBLEM

Physical systems lose context between people, shifts, paper, software, and time.

A machine can have a serial number, a local nickname, handwritten service notes, meter hours, parts history, operator knowledge, and a database record that never quite agree. PMARS starts by giving the physical thing a stable point of reference. Scan the marker and the current record follows the asset instead of forcing the worker to hunt for the system that contains it.

Persistent identityThe physical marker resolves to a durable record rather than encoding the entire changing record in the label.
Operational stateStatus, hours, last service, observations, maintenance needs, and supporting evidence can accumulate around the same identity.
Field-first interactionThe worker begins with the thing in front of them: find the marker, scan it, see or update the relevant record.
Authority after identityThe scan proves which asset. The signed-in role proves which slice of the record and which actions are legal.
FIELD EVIDENCE, NOT A PRODUCT CLAIM

PMARS has been exercised as a working field prototype around maintenance and physical equipment. These photographs are from that loop. They do not claim a certified production deployment, manufacturer integration, or that every scan already enforces a finished role-permission matrix.

WHY IT MATTERS TO JAPAN

A small identity primitive can connect maintenance, robotics, inspection, and knowledge continuity.

In a Japanese co-development setting, the useful experiment is deliberately bounded: choose one class of equipment or one physical workflow, establish persistent identity, capture the evidence people already use, then test whether maintenance personnel or machine systems can act with less ambiguity and better reconstructability.