Reference
EMS LAN Glossary
Plain definitions for EMS LAN snapshot, import, reconciliation, device, and audit terms.
Use The Terms In Context
Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, EMS LAN Glossary narrows that work to plain definitions for EMS LAN snapshot, import, reconciliation, device, and audit terms. Because this is a reference page, read it as part of the EMS LAN learning path rather than as an isolated checklist.
EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.
What The Terms Are For
This is a lookup page, but the definitions still belong to real operations. Read the term, then connect it to the record, screen, file, or decision where the word appears. The intended readers are All EMS LAN users. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.
- Primary surface or service: /rego/events/manage/offline-snapshot?id=:eventId.
- Records or contracts involved: Glossary terms.
- Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
- Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.
How To Read A Definition Safely
- Find the exact term used by the system: Begin by naming the EMS LAN situation, the owner, and the exact item involved in EMS LAN Glossary.
- Read the surrounding workflow: Use /rego/events/manage/offline-snapshot?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
- Use the term consistently in notes: Keep Glossary terms in view so the work stays tied to the records or contracts it can affect.
- Ask for review when two terms sound similar: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.
Before You Use A Term In A Note
You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.
- Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
- Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
- Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.
End-to-end operator runbook
Use this numbered runbook when a term is unclear.
- Step 1 - Confirm the term or page. Find the exact word used in the dashboard, runbook, or import summary. This avoids guessing.
- Step 2 - Check the related context. Read the definition and the linked reference page. This connects the word to the workflow.
- Step 3 - Apply the guidance. Use the same term in notes and handoffs. This helps other operators find the same state later.
- Step 4 - Return to the workflow. Continue the runbook only after the term is clear. This prevents confused operations.
Core terms
| Term | Meaning |
|---|---|
| EMS LAN | Offline Event Management operation using exported event snapshots. |
| Snapshot | File containing event operating data at a point in time. |
| Export | Dashboard action that creates a snapshot file. |
| Import | Dashboard action that applies returned LAN data. |
| LAN-local state | Changes held by the onsite LAN system before import. |
| Reconciliation | Checking imported dashboard records against onsite expectations. |
| Sync history | Audit list of snapshot exports and imports. |
| Schema version | Version marker for snapshot structure. |
| Source metadata | Event and export details inside the snapshot. |
| Same-event check | Protection against importing a file into the wrong event. |
Status words
| Term | Meaning |
|---|---|
| Online | Dashboard is the trusted operating state. |
| LAN active | Offline devices are the trusted onsite operating state. |
| Imported | LAN file has been uploaded and applied. |
| Reconciled | Operators verified affected dashboard records. |
| Stale | Snapshot is older than important event changes. |