Glossary
Every term you'll encounter in Vigil, in plain English.
Asset A single piece of equipment at a site. Examples: Rooftop Unit 3, Scroll Compressor A, Walk-in Evaporator Coil. Assets belong to a System and can optionally be placed in a Space. Also called equipment or equip in some API references.
Asset tag A short code (e.g. HVAC-003) assigned to an asset. Used to generate QR stickers that are affixed to the physical equipment. Scanning the sticker in the mobile app instantly pulls up the asset's record.
Check in / Check out When a technician in the Service app starts work on a job, they check in (starting a Session). When they finish (or pause), they check out. The app records both times for labor tracking.
DNA Capture A mode in Vigil Mobile for org users to quickly catalog equipment — photograph nameplates and components to build an asset's record. A data-collection tool used during site onboarding, separate from the day-to-day issue/work-order flow.
Early Warning A predictive alert generated by Vigil AI when an asset's sensor data suggests a problem is developing. Can be used as a Work Order origin.
Evidence Supporting material attached to an issue or work session — photos, notes, invoices, PDFs, or sensor data. Evidence is immutable: once attached, it cannot be edited or deleted (preserves the audit trail).
FAB (Floating Action Button) The blue "+" button in the bottom-right corner of the Vigil Mobile app. Tapping it opens a speed-dial with four shortcuts: Create Issue, Create Work Order, Find Asset (QR), Create Asset.
Issue A recorded problem at a site — a broken unit, an alarm, a leak. Also called an event. Issues are the most common origin for a Work Order. An issue is filed against an asset, a space, or the whole site.
Open Book A capital project record (renovation, installation, equipment replacement). Used as a Work Order origin when the work is part of a larger project rather than a reactive repair.
Org (Organization) Your company's account in Vigil. The top-level container for all sites, users, and service providers.
Origin What triggered a Work Order. Every work order must have exactly one origin: an Issue, a PM Schedule, a Project (Open Book), or an Early Detection signal.
PM Schedule (Preventive Maintenance Schedule) A recurring maintenance task on a specific asset. Defines what work needs to be done, how often, and (optionally) which contractor should do it. Generates Work Orders when due.
Priority How urgent a Work Order is. Four levels: Routine, Normal, Urgent, Emergency.
Role A person's permission level in Vigil. Five roles exist: Org Admin, Org Operator, Org User, SP Admin, SP Technician. See Roles & Permissions.
Root cause The category logged on a Work Order to explain why the problem happened. Options: Deferred PM, Operator Error, Equipment Age, Vendor Fault, Unknown.
Service Provider A contractor company hired to perform work. Org-level — not tied to a specific site until site access is granted. Has technicians as team members.
Session A time-tracked block of work on a Work Order. Starts with a check-in, ends with a check-out. Multiple sessions per work order are supported (e.g. if a technician needs to return for parts).
Severity How serious an Issue is. Four levels: Low, Medium, High, Critical. Maps to Work Order priority (Critical → Emergency, etc.).
Site A physical building or facility. Also referred to as a store in the UI (reflecting Vigil's grocery-retail origin). Everything in Vigil — assets, issues, work orders — belongs to a site.
SLA (Service Level Agreement) A defined response/resolution time target for a service provider at a given priority or severity level. Configured per-store under Maintenance settings.
Space A named physical area within a site. Examples: Walk-in Cooler #1, Sales Floor, Rooftop. Spaces are optional but help anchor issues and assets to a location. Assets can be linked to a space.
SP Admin / SP Technician Service provider roles. SP Admins manage their company's presence in Vigil; SP Technicians do the assigned work. Both use the Vigil Service app exclusively.
Status (Work Order) The current stage of a Work Order: Open → Assigned → In Progress → Pending Review → Work Approved → Approved for Payment. Can also be Deferred or Rejected.
System A logical group of related equipment within a site. Examples: HVAC, Refrigeration, Electrical, Lighting. Every asset belongs to a system.
Technician An individual employee of a service provider. Technicians do the physical work and use the Vigil Service app.
Vigil Mobile The Expo/React Native app for org users — operators and facility managers. Works on iOS and Android.
Vigil Service The Expo/React Native app for contractors and technicians. Access is invite-only. Service providers see only work assigned to them.
Vigil Web The Next.js web app for org users. The full-featured control center for managing sites, assets, work orders, service providers, reports, and settings.
Work Order An actionable task to resolve a problem, perform maintenance, or conduct an inspection. Assigned to a service provider. Has one origin (an Issue, PM Schedule, Project, or Detection signal) and follows a defined status lifecycle.
Work Order Type What kind of work a Work Order involves: Repair, Replacement, Preventive Maintenance, Inspection, or Diagnostic.