Home · Docs · Assets walkthrough

Day in the life — corporate assets

Collections in play: workordersin, workordersout, assets, inventory, tasks, notes, messages.
Not the center of this day: orders, rates, taxes (those are customer/sales).

Persona

How work reaches the phone. Channel emp:E-4412 (SG login jon.hale@example.com). Dispatch or Jon can create inbound jobs. Dispatch inbound is never patched. Jon may CreateWorkOrderIn (origin: field) for a walk-up inspect. He copies inbound → outbound, works offline, pushes his copy. Asset master stays pull-only.

Screen map

Timeline

sequenceDiagram
  actor Jon
  participant Phone
  participant CBL as CBL local
  participant SG as Sync Gateway
  participant Dispatch

  Dispatch->>SG: assign inspect P-12, repair P-12, move spare motor
  SG->>CBL: PULL workordersin + assets (emp:E-4412)
  Jon->>Phone: StartWork inspect
  Note over Phone: copy woin → woout, never mutate inbound or asset
  Jon->>Phone: checklist + photo + CompleteWork + SubmitWork
  Jon->>Phone: StartWork repair on same asset
  Jon->>Phone: consume valve, photos, CompleteWork
  Jon->>Phone: StartWork move — scan from/to locations
  Phone->>SG: PUSH three woout copies

06:40 — Login and Today

Demo login (EXPO_PUBLIC_AUTH_STRATEGY=demo) with Jon’s email maps to Jon. Today is work orders (workModes: assets hides the orders card). The header is a live clock and a seconds countdown (next start / late-by / end of day). Rows show number · kind, site, summary, priority stripe, time.

v1 seed board (device-local scheduled.day):

Tap a row → inbound KV. Start work is the filled button in the bottom dock (not a row cycle). Hermes has no crypto; the new woout: id uses expo-crypto.

07:00 — Inspect (WO-10470)

Tap → inbound KV (read-only kit). Start work copies to woout:. Operations (Site check, Close out) and checklist (PPE on) are outline buttons; tap fills them (status: done / done: true). On the map, pins come from local assets. Photos as blobs on outbound. CompleteWork (dock) freezes that copy; SubmitWork queues push. Asset master is not edited — findings live on the WO.

07:45 — Repair (WO-10482)

Same pump. Start copy. Basement, no radio. Photo seized valve, consume VLV-CHK-4 (inventory_tx + materials line, no stock save), lockout task, chat dispatch for a lift. Complete + submit when LTE returns. Forgotten nameplate photo → Add follow-up (CreateAmendment), not an edit of the frozen repair copy.

11:00 — Move (WO-10490)

Inbound kit: asset M-7, from geo (yard), to geo (Riverside). Start copy. Scan / confirm asset, photo on truck, photo at destination, history[] rows at both ends (lat/lon/dt). Driving between sites also writes tracking crumbs when he moves ≥ threshold. Complete. Backend owns the completed move; CMMS updates location from that document, not from Jon mutating assets.

14:00 — Reassigned leftover

WO-10460 still on his outbound list, badge Reassigned. He finishes safety work he already started, completes his copy. Priya may have her own copy. Two documents, one WO number.

16:30 — Out

Profile, sync idle, logout.

Rules this day proves

1. Company assets are pull catalogs. Work (inspect / repair / move) is workordersout.
2. Copy-on-write, freeze-on-complete, amendments, reassignment — same as the general design.
3. history[] lat/lon/time + field diffs on inspect checks, consume, move drop-off. Driving crumbs go to tracking.
4. No orders / money on this mode unless the company also enabled customer/sales.

Beat sheet

1. Login jon.hale@example.com, workModes includes assets.
2. Today shows inspect + repair + move inbound, kind visible.
3. Inspect: Start → checklist + photo → complete → inbound JSON unchanged, asset JSON unchanged.
4. Repair offline: photo, consume, complete, submit.
5. Amendment after freeze.
6. Move: from/to photos + two history[] points (and tracking crumbs in between).
7. Reassigned row still submittable.