Skip to content

Entities & What They Require

This is the technical companion to How Everything Connects. Use it when you need to know exactly what fields are required and what prerequisite records must exist.


Site

The root container for everything. A physical building.

FieldRequired?Notes
Name✅ YesUnique within your org
Timezone✅ YesDefaults to America/Chicago if not set
Address, City, State, CountryOptionalFor display and reporting

Depends on: Nothing. This is your starting point.


System

A logical grouping of equipment within a site. Examples: HVAC, Refrigeration, Electrical.

FieldRequired?Notes
Site✅ YesWhich site this system belongs to
Name✅ YesUnique within the site
System typeOptionalUsed to match specialized service providers

Depends on: Site


Space

A named physical area inside a site. Examples: Walk-in Cooler #1, Sales Floor.

FieldRequired?Notes
Site✅ YesWhich site this space is in
Name✅ YesUnique within the site
Space typeOptionalE.g. cooler, freezer, sales area

Depends on: Site


Asset (Equipment)

An individual piece of equipment.

FieldRequired?Notes
Site✅ YesWhich site
System✅ YesWhich system group it belongs to
Name✅ YesUnique within site + system
Class✅ YesEquipment category (from dropdown)
SpaceOptionalPlaces the asset in a physical area
Asset tagOptionalQR/barcode identifier for mobile scanning — strongly recommended

Depends on: Site + System


PM Schedule

A recurring maintenance task on a specific asset.

FieldRequired?Notes
Asset✅ YesThe specific equipment to maintain
Work Order Type✅ YesUsually Preventive Maintenance or Inspection
Frequency✅ YesDays between occurrences (7, 14, 30, 90, 180, 365, or custom)
Next due date✅ YesWhen the first task should generate
TitleOptionalAuto-generated if blank
Service subtypeOptionalE.g. Filter Replacement, Oil Change
Assigned service providerOptionalPre-fills on WO creation

Depends on: Asset


Service Provider

A contractor company you hire to do work. Org-level — not tied to a specific site until you grant site access.

FieldRequired?Notes
Company name✅ Yes
EmailOptionalCompany contact
PhoneOptional
System typesOptionalSpecialties; used for filtering when assigning

Depends on: Nothing. Org-level.


Technician

An individual employee of a service provider.

FieldRequired?Notes
Service Provider✅ YesWhich company they belong to
Name✅ Yes
EmailOptionalMust match their Vigil invite email
PhoneOptional

Depends on: Service Provider


Service Provider Site Access

Grants a service provider permission to work at a specific site. Required before a technician can check in to a job at that site.

FieldRequired?
Service Provider✅ Yes
Site✅ Yes

Depends on: Service Provider + Site


Issue (Event)

A recorded problem.

FieldRequired?Notes
Site✅ YesAuto-derived from asset/space if provided
Issue type / title✅ YesShort description of the problem
Severity✅ YesLow, Medium, High, Critical
Start time✅ YesAuto-set to now
Evidence✅ YesAt least one photo, note, or document
AssetOptional (recommended)The specific piece of equipment
SpaceOptionalThe area of the building
DescriptionOptionalFull detail of the problem
Due dateOptional

At least one of asset, space, or explicit site required as location anchor.

Depends on: Site — asset and space are optional but recommended.


Work Order

An actionable task to resolve something.

FieldRequired?Notes
Work Order Type✅ YesRepair, Replacement, Preventive, Inspection, Diagnostic
Origin (exactly one of):✅ YesSee below
— IssueAn open Issue
— PM ScheduleAn active PM Schedule
— ProjectA site Project
— Detection signalAn active Early Warning signal
Service ProviderOptionalAssign on creation or later
Due dateOptional
PriorityOptionalRoutine, Normal, Urgent, Emergency
NotesOptionalInstructions for the technician

Site, asset, and space are auto-filled from the origin — you don't set them manually.

Depends on: Site (via origin) + one of Issue / PM Schedule / Project / Detection signal.


Work Order Session

A time-tracked block when a technician works on a job.

FieldRequired?Notes
Work Order✅ Yes
Check-in time✅ YesAuto-set when technician checks in
Check-out timeOptionalSet when they check out
Service ProviderOptionalAuto-filled from WO assignment
Session notesOptionalWhat the technician did
Evidence photosOptional (may be required by checkout rules)

Depends on: Work Order


Evidence

A photo, document, or note attached to a record.

FieldRequired?Notes
Evidence type✅ Yesphoto, pdf, invoice, vendor_record, note, telemetry
File / content✅ YesThe actual file or text
Captured at✅ YesAuto-set
Link target✅ YesMust be linked to an issue, asset, or work order session

Evidence is immutable — it cannot be edited or deleted after creation. This preserves the audit trail.

Depends on: Issue or Asset or Work Order Session


User / Invite

FieldRequired?Notes
Email✅ YesThe person's work email
Role✅ YesSee Roles & Permissions
Service ProviderRequired if SP roleWhich contractor company
Site accessOptional for org usersRestrict to specific sites; blank = all sites

Depends on: Service Provider (for SP roles only)