Project 03

EDC Operation Management System

A bilingual, offline-capable operations platform that replaces manual truck timesheets with geofence-validated field events, approval workflows, and locked vendor billing outputs.

Operational ManagementAdmin/Vendor web · Supervisor/Driver mobile

Oilfield Fleet Attendance, Compliance & Billing

The EDC Operation Management System digitises truck operations across oilfield sites and rigs. A supervisor scans a driver or truck QR code in the field, the system captures time and GPS evidence, validates the event against the active geofence, and converts accepted operational activity into auditable attendance and billing data.

The platform serves four roles through purpose-built web and Flutter interfaces. It supports disconnected field work, approval-controlled exceptions, truck movement tracking, document expiry monitoring, vendor self-service, immutable audit history, and Excel timesheet export without hard-deleting operational records.

Audience
System administrators, vendors, rig supervisors, and drivers
Operational scope
Oilfield sites, rigs/primas, vendors, trucks, and drivers
Delivery
Admin/Vendor web · Supervisor/Driver mobile
154 trucksSeeded operational fleet
40 daysDemo operational history
4 rolesAdmin, vendor, supervisor, driver
AR / ENBilingual web and mobile

A connected operational experience.

01

Geofence-validated attendance

Supervisor scans capture GPS and timestamps. Accepted check-in and check-out events create one attendance unit per truck and business day under defined business rules.

02

Offline-first field operations

Hive-backed queues preserve check-ins, violations, manual entries, and half-day requests without connectivity, then synchronise and revalidate against original event times.

03

Approvals and violations

Violations, manual entries, adjustments, and half-day requests move through Sys Admin approval. Vendor-visible deductions appear only after approval.

04

Truck movement control

Site-to-site, rig-to-rig, initial assignment, and correction movements track expected arrival, current state, arrival, cancellation, and operational notifications.

05

Auditable timesheets

Readiness checks expose unresolved issues before generation. Generated timesheets lock covered truck and date combinations and export to Excel with one worksheet per truck.

06

Versioned geofences

Each rig/prima geofence is maintained through versioned polygons and validity windows, preserving the spatial rule applied to historical events.

07

Vendor and fleet management

Administrators oversee vendors, sites, rigs/primas, categories, price history, trucks, drivers, supervisors, assignments, and operational states.

08

Vendor self-service

Vendors access only their trucks, drivers, movements, violations, documents, notifications, and timesheets through an isolated portal.

09

Documents and review queues

Expiry heat maps identify expired or soon-to-expire files, while suspicious offline or conflicting events enter a review queue before billing.

10

Notifications, audit, and settings

Contextual bilingual notifications support each role. Every state change is recorded in the audit log and configurable business parameters are centrally managed.

Designed around the way work actually happens.

01

Daily attendance

  1. 01

    Driver presents the assigned truck QR

  2. 02

    Supervisor scans at the rig and captures GPS

  3. 03

    Backend validates the active geofence

  4. 04

    Check-in and later check-out events are recorded

  5. 05

    The truck receives its attendance unit for the business day

02

Offline synchronisation

  1. 01

    Supervisor records work with no connection

  2. 02

    Events remain in the local Hive queue

  3. 03

    The app synchronises when connectivity returns

  4. 04

    Backend revalidates original timestamps and geofence evidence

  5. 05

    Conflicts become review items for Sys Admin

03

Violation to billing

  1. 01

    Supervisor creates a field violation

  2. 02

    Sys Admin reviews and enters a required deduction

  3. 03

    Approval makes the deduction effective

  4. 04

    The deduction enters the next eligible timesheet

  5. 05

    Vendor sees the approved financial impact

04

Timesheet generation

  1. 01

    Select scope and date period

  2. 02

    Run readiness checks for pending or missing data

  3. 03

    Resolve blockers

  4. 04

    Generate and lock truck/date combinations

  5. 05

    Export the auditable Excel workbook

05

Truck movement

  1. 01

    Create a site or rig movement order

  2. 02

    Set the truck to In Transit with expected arrival

  3. 03

    Confirm arrival through field activity or administration

  4. 04

    Update the current operational assignment

  5. 05

    Notify stakeholders about delays or cancellation

Technology selected for geospatial performance and operational reliability.

Clean Architecture separates a React operations suite, Flutter mobile workflows, an ASP.NET Core API, and PostgreSQL persistence. Optimistic concurrency, audit records, role isolation, offline queues, and test coverage support reliable operational behaviour.

  • ASP.NET Core 8
  • EF Core 8
  • PostgreSQL 16
  • JWT
  • React 18
  • Vite
  • TypeScript 5
  • Tailwind CSS
  • shadcn/ui
  • TanStack Query
  • Flutter 3
  • Riverpod
  • Hive
  • QR generation and scanning
  • xUnit
  • Vitest
  • Playwright
  • Docker Compose
  • React i18next
  • Flutter ARB