MyEvolution® ACME Supermarket Site: Loja Lisboa ▾ M. Dias · Client Manager

Dashboard

Statistics are client-only (FR-RPT-01). Phase 1 ships curated dashboards + filters, not a self-serve builder (D-06). Charts aggregate immutable records across modules.
€1,240
Theft value (month)
▼ 12% vs last
3
Keys outstanding
▲ 1 today
2
KO readings
▲ urgent
96%
Task compliance
▲ 2%
48
Visitors today

Thefts by category

Spirits 45% Cosmetics 27%
Razors 16% Other 12%

Thefts by hour

10h · 12h · 14h · 16h · 18h · 20h

Energy consumption

kWh / day — trending down after the LEITURAS alerts

Records

Full history (client). Every line is a guard's immutable, attributed record — read-only; the only change is a linked correction (UC-CC-02). Browse a guard's stream by Day or Week. Paired events (pickup/return) show as one row (D-13).
Day Week
TimeModuleAuthorSummaryState

AVISOS

Two-way messaging to guards. Sends nag the device until read; you get a read receipt with the reader's name + time (UC-CC-08). Checklists aren't authored here — guards run them as Shift plan duties (UC-AVI-03/04); edit their task content in Templates.

Compose

Sent — delivery status

“Reforçar ronda piso -1”read A. Silva · 14:05
“Verificar arcas às 16h”delivered R. Lima

Templates

The configurable engine. Templates are organised by Topic — the same Topic → Form Template spine the guard sees as menu tiles (e.g. CONTROLOS → CHAVES / VIATURAS / MATERIAL / SELOS). Pick one to edit, + add a template under a topic, or add a new topic. You self-publish (D-05); publishing mints a new immutable version and past records keep their pinned version (FR-ENG-06). Rules use a bounded, safe set (D-04).
Editing: CONTROLOS · Key Handover Published v3

Fields

⌨ Text
#️⃣ Number
⏱ Datetime (system)
🔘 Tri-state
🔎 Lookup → catalog
👤 Person
✍️ Signature
📷 Media
🔢 QR / barcode
🧮 Computed
☑ Checklist

Click a field to add it. New field types are engineering-owned; you compose from these.

Key Handover — fields

+ click a field in the palette to add it here

Shift plans

A per-shift playbook of duties the guard follows — an orchestration template referencing existing checklists, patrol routes and readings; no new field types (D-16). This is the library; you place plans onto a timetable and staff them in Schedule. The patrol duty here is a default — the actual route binds per block in the schedule (D-23).
06:00–14:00 · Mon–Sat · 1 guard
#DutyKind → referenceWhen
1📋 Read prior handoverhandover-readat startmandatory
2🧭 Opening roundpatrol → patrol.opening@1by 06:30mandatory
3☑ Daily taskschecklist → checklists.daily-tasks@4during shiftmandatory
4🌡️ Temperatures (all cold stores)recurring → readings.temperature@1every 2hmandatory
5🔢 Article countsrecurring → counts.article@1start + endoptional
6🗒️ Daily reportone-off → reports.daily@2by 13:45mandatory
7📝 File handoverhandover-write → shift.handover@1by 14:00mandatory

Shift plan · Retail — Day

06:00 – 14:00 · Mon–Sat
1 guard · post: Loja Lisboa
7 (5 mandatory)
shift.handover@1 — outstanding keys/visitors/alerts + notes
Missed mandatory duty → alert + escalation (reuses patrol-miss, UC-PAT-01)

Each duty references a template that already exists. Completing it creates the normal immutable record and ticks the duty (no duplication).

Schedule

The timetable that combines a shift plan with a patrol route. Each block binds a time window → Shift plan + Patrol route (the route binds here, so one plan can pair with different routes across the day, D-23). Plan the coverage first (what), then assign guards (who) — each at day / week / month granularity (D-24).
Phase
Coverage (blocks) Assign guards
Granularity

Guards

Guard management — the pool the Schedule draws from. Only active guards with the block's required site and certifications are offered when assigning (D-24 · UC-SHIFT-06). Ownership can be delegated to the security company (D-21).
GuardRoleStatusSitesContractedCertifications
A. SilvaVigilanteactiveLoja Lisboa40h/wkBasic · Fire
R. LimaVigilanteactiveLoja Lisboa40h/wkBasic · First-aid
M. TavaresVigilante (night)activeLoja Lisboa · Armazém40h/wkBasic · Night
J. SousaVigilante (relief)on-callLoja LisboaflexibleBasic
P. AntunesVigilanteinactiveBasic

Inactive / off-site / under-certified guards are filtered out of assignment (UC-SHIFT-06 · E1/E2).

Catalogs

Master data is editable (you curate it). Transactional records snapshot the values they used, so editing a catalog never rewrites history (D-08).
Key registryMetersArticles Authorized peopleVehicle types
IDLabelLocation
key_A42LibraryA42Biblioteca
key_B07Loading bayB07Cais
key_C15Server roomC15Piso 1

Patrol routes

Phase 1 module (D-10). Define ordered NFC/QR checkpoints + schedule; missed/late scans raise alerts (UC-PAT-01). Published routes go live with no app release.

Route · Night rounds

1🏷 Entrance (NFC)every 2h
2🏷 Piso -1 cold store (QR)every 2h
3🏷 Loading bay (NFC)every 2h
4🏷 Roof access (NFC)02:00 only

Schedule

22:00 – 06:00
Every 2 hours
Alert + escalate after 15 min

Settings

Per-tenant configuration set at onboarding & adjustable by the Tenant Admin.

Branding

acme-logo.png
Default (grayscale)

Delivery

23:30 daily
Email + push

Alerts & thresholds

max 4°C
15 min

Data & access

Guard 12d · Security Co. 30d fixed (D-15)
Per data class · crypto-erasure on request (D-11)
PT · EN · FR · ES

Live operations

Phase 1.5
Real-time guard location + geofence (UC-LOC-01 · D-10). Worker-tracking consent / labour rules apply; location data under crypto-erasure & retention (D-11 · LOC-A).
Loja Lisboa — geofenced 🟢A. Silva 🟢R. Lima 🏷🏷🏷

On shift now

Piso -1 · on route
Entrada · idle 6 min
A. Silva left zone 23:40
3 / 4 checkpoints this round

Security company — limited view

Data-safeguard role: access limited to the last 30 days, no statistics (UC-RPT-03 · D-15). Records stay read-only & immutable.
TimeModuleAuthorSummaryState
14:02🔑 CONTROLOSA. SilvaKey A42 — pickup→returnClosed
16:40🌡️ LEITURASR. LimaArca Nº12 — 9°CKO
— older than 30 days —not accessible to this role
📊 Statistics are client-only — not available to the security company.