Run the work. Not the chaos.
Field Operations, Under Control.
Work orders, scheduling, dispatch, technicians, and operational records, all connected in one field operations system.
Constraint-Based Scheduling & Dispatch
Enforce real operational constraints: assign verified technicians, validate working hours and approved leave, reject double-booking, and coordinate dispatch states across teams.
Enforced Work Order Lifecycle
Maintain discrete operational integrity across separate work order, appointment, dispatch, and time-tracking axes from job creation through on-site resolution.
Multi-Location Inventory Tracking
Maintain continuous visibility into parts stock across mobile vans, field locations, and central warehouses, automatically updating balances on work order consumption.
The Day: Follow the Work
Follow work order WO-1042 through seven sequential operations, from dispatcher assignment and availability-checked scheduling to mobile execution, operational hold, and job completion. Operational audit history provides a record of work-order activity and status changes.
Scene 01: Assign Accountable Field Technician
Axis: WORK_ORDEREmergency Chiller & Air Handler Mechanical Inspection
Metro General Hospital
Main Clinical Pavilion, Mechanical Room 3B
Elena Rostova [TECH-02]
Unit: Van #04
Work order WO-1042 enters the system in OPEN status. Dispatch assigns Elena Rostova as the accountable technician. Transitioning to ASSIGNED requires an assigned technician.
Moving to ASSIGNED or to COMPLETED requires an assigned technician.
Scene 01: Assign Accountable Field Technician
Axis: WORK_ORDERWork order WO-1042 enters the system in OPEN status. Dispatch assigns Elena Rostova as the accountable technician. Transitioning to ASSIGNED requires an assigned technician.
Scene 02: Schedule Verified Appointment Window
Axis: APPOINTMENTDispatcher reserves an appointment window (08:30 to 11:30) for Elena Rostova. The scheduling engine validates working hours and approved leave exceptions through half-open interval overlap checks.
Scene 03: Dispatch Appointment to Field Resource
Axis: DISPATCHWith the schedule locked, dispatch advances the single appointment to the field. Elena Rostova receives notice of the assignment on her mobile terminal.
Scene 04: Technician Acknowledges Dispatch
Axis: DISPATCHElena Rostova reviews the job details and acknowledges the dispatch. Acknowledgment records field receipt on the dispatch axis, but is not a hard backend prerequisite for starting work.
Scene 05: Start Work and Open On-Site Time Entry
Axis: WORK_ORDERElena Rostova arrives on site and starts the work order. Starting work transitions WO-1042 to IN_PROGRESS and automatically opens an ON_SITE labor time entry on the execution axis.
Scene 06: Operational Hold and Execution Resume
Axis: WORK_ORDERA temporary operational pause places the work order on hold. The transition matrix permits moving from IN_PROGRESS to ON_HOLD and returning directly to IN_PROGRESS.
Scene 07: Work Order Completed and Motion Settled
Axis: WORK_ORDERInspection and mechanical testing conclude. Elena Rostova transitions WO-1042 to COMPLETED. The primary spine reaches its terminal state and motion stops.
System Invariants and Engine Integrity
Under Control
Operations run on verified backend rules, transactional locks, and relational constraints. Not client-side assumptions or unvalidated status flags.
Active appointments (SCHEDULED or RESCHEDULED) cannot overlap in time for the same technician. Overlaps are detected across interval boundaries and rejected inside an atomic transaction.
Scheduling validates recurring weekly working hours, approved leave or training exceptions, and active employee status. Bookings outside working hours or during approved leave are blocked.
Work order transitions strictly adhere to the locked lifecycle graph. Transitions from OPEN directly to COMPLETED are rejected as invalid. Terminal states (COMPLETED, CANCELLED) permit zero outgoing transitions.
Transitioning a work order to COMPLETED requires an assigned technician record. Work orders cannot be closed anonymously or without an accountable technician profile.
Dispatchers manage assignments and schedules but are explicitly restricted from completing work orders. Technicians act only on their assigned work orders across four permitted transitions: ASSIGNED → IN_PROGRESS, IN_PROGRESS → ON_HOLD, ON_HOLD → IN_PROGRESS, and IN_PROGRESS → COMPLETED. Owners, Admins, and Managers maintain full matrix authority.
An appointment cannot be scheduled on an unassigned work order. The technician assigned to the appointment must match the assigned technician on the parent work order. Terminal work orders cannot be scheduled.
Data Schema and Relational Topology
The System
Direct relational integrity from customer intake to financial settlement. Work orders link directly to customers and service locations, while scheduling and field assignments maintain strict referential boundaries.
Customer
Direct account relationship
ServiceLocation
Direct physical facility address
WorkOrder
Coordinates state transitions, assigned technician, dispatch appointments, parts consumption, and billing settlement.
TechnicianProfile
Anchors both job accountability and schedule booking
ScheduleAppointment
Calendar booking with overlap conflict prevention
TechnicianAssignment
Work allocation record linking via workReferenceId without hard relational database foreign key.
Invoice
Schema Verification and Referential Integrity Table
| Entity | Relation Field | Target Entity | Integrity Type |
|---|---|---|---|
| WorkOrder | customerId | Customer | Direct Foreign Key (Restrict) |
| WorkOrder | locationId | ServiceLocation | Direct Foreign Key (Restrict) |
| WorkOrder | assignedTechnicianId | TechnicianProfile | Direct Foreign Key (SetNull) |
| ScheduleAppointment | technicianId | TechnicianProfile | Direct Foreign Key (Restrict, L1367) |
| TechnicianAssignment | workReferenceId | WorkOrder / Target | Polymorphic Reference (No FK) |
| Invoice | lineItems / payments | InvoiceLineItem / Payment | Relational Child Collections |
See the Operation
Illustrative operational views based strictly on verified schema queries. Counts reconcile across visuals. No synthetic conversion rates, no unverified projections, and no vanity metrics.
workOrders.createdCount × workOrderStatus
Status distribution of 18 created work orders: 2 OPEN, 4 ASSIGNED, 5 IN_PROGRESS, 2 ON_HOLD, 5 COMPLETED.
View Accessible Table (Status Breakdown)
| Lifecycle Status | Job Count |
|---|---|
| OPEN | 2 |
| ASSIGNED | 4 |
| IN_PROGRESS | 5 |
| ON_HOLD | 2 |
| COMPLETED | 5 |
technicians.completedWorkOrderCount × technician
Completed work orders across technicians: Elena Rostova (TECH-02) 2 jobs, Marcus Vance (TECH-01) 1 job, Devon Reed (TECH-03) 1 job, Tasha Morales (TECH-04) 1 job. Reconciles to 5 total completed jobs.
View Accessible Table (Technician Completions)
| Technician | ID | Completed Jobs |
|---|---|---|
| Elena Rostova | TECH-02 | 2 |
| Marcus Vance | TECH-01 | 1 |
| Devon Reed | TECH-03 | 1 |
| Tasha Morales | TECH-04 | 1 |
WO-1042 Transition History Ledger
This ledger reflects operational event entries recorded by the server on each state transition. It is an operational log, not a chart or projection.
Product Origin
Built by Aformix
Aforden is built by Aformix, a technology company creating digital products and software systems for modern businesses.
Field Operations, Under Control.
Bring the work, the people, and the operational record into one system.