Context
VENTSIM needed a tablet-friendly interface for VentLog, allowing field users to record ventilation readings, manage stations and continue working across multiple underground locations.
← Back to case studies
Case study / VENTSIM
Offline-ready ventilation logging for mining field teams.
VENTSIM needed a tablet-friendly way to capture VentLog station readings in field conditions where connectivity could not be assumed. MT Software helped structure an offline-ready PWA with station management, guided record entry and API synchronization.
System overview
Workflow model
VentLog flow from field input to API synchronization
Input
Station readings
Tablet users capture station context, record metadata, measurement types, values and comments.
Review
Offline validation
Data is validated, stored locally and prepared for review before submission or next-location entry.
Handoff
API synchronization
When online, local stations, records and updates are synchronized with the backend.
System-level workflow representation showing how field input, local storage and backend synchronization
connect.
Overview
From field data friction to an offline-ready logging workflow.
VentLog needed to support operational data capture in mining environments where users move between stations and cannot depend on a constant connection.
Challenge
The workflow had to support authenticated users, editable station data, favorite record types, images, area calculations and local-first storage without making field entry slower.
Solution
MT Software structured a Quasar PWA backed by a Laravel API, combining multi-step data entry, IndexedDB offline storage, station management and synchronization logic.
Outcome snapshot
A reliable field workflow for station-based ventilation data.
The case focuses on structural outcomes: guided data entry, offline local storage and an authenticated path for synchronizing stations and records with the backend.
Guided record entry
Station selection, readings, comments and review were organized into a focused flow for tablet-based field capture.
Local-first data capture
IndexedDB storage allows records and stations to be handled locally before synchronizing with the API.
Backend synchronization
Authenticated Laravel endpoints support stations, records, selected record types and deployment-ready database configuration.
Solution design
A workflow designed around field continuity and synchronization.
The solution focused on keeping field entry practical: capture data on tablet, store it locally, review it clearly and synchronize it when the API is available.
Tablet entry flow
A multi-step interface guides users from station selection to record entry, comments and review.
Offline data layer
IndexedDB stores stations, records and record types locally so the PWA can keep working offline.
Station management
Users can create, edit, filter and select stations with area, image, group and level metadata.
API synchronization
Laravel endpoints and sync routines connect the PWA workflow with authenticated backend operations.
Workflow model
A system-level view of offline field capture and synchronization.
The visual model shows how station data and readings move from tablet input into local storage, then into backend synchronization when the API is available.
Offline capture
Station and record workflow.
Local storage
IndexedDB cache keeps field data available offline.
Local stores keep stations, records and selected types available for offline usage.
Sync layer
API handoff moves unsynced changes into protected backend endpoints.
Unsynced changes are pushed to protected backend endpoints when connectivity returns.
Delivery path
A practical delivery sequence for a field data PWA.
The work moved from VentLog workflow mapping to PWA implementation, API integration, synchronization logic and deployment handoff.
-
Week 01
Discovery and workflow mapping
Map VentLog’s existing data entry process, station model, record structure, field constraints and synchronization requirements.
-
Week 02–03
PWA interface and local data model
Build the tablet-friendly interface, offline IndexedDB stores, station selection and guided record entry flow.
-
Week 04–05
API, authentication and synchronization
Implement Laravel endpoints, JWT authentication, station and record CRUD, selected record types and sync logic.
-
Week 06
Deployment and handoff
Deploy the PWA/API environment, configure HTTPS and Nginx, validate installation behavior and document production setup.
Technical direction
Technical structure that supports offline field data capture.
The technical direction focused on tablet-friendly data entry, local-first storage, authenticated API access and synchronization paths designed around real field usage.
Quasar PWA
Laravel API
IndexedDB
JWT Auth
Offline sync
Field UX
Project takeaway
“The strongest value of the project was turning a field-heavy data entry process into a structured workflow that could keep working beyond the limits of connectivity.”
