How We Built a Paperless Operations Platform for APAS Bharat Technologies

APAS Bharat Technologies is the project that started JenX Technologies. It was our first client, our first major build, and the proof-of-concept that showed us what a well-designed custom application can do for an operations-heavy business.

This is the story of what we built, why it mattered, and what we learned.

The Client and the Problem

APAS Bharat Technologies operates water treatment plants and provides environmental management services. Their day-to-day operations involved water quality monitoring, maintenance scheduling, compliance reporting, and field technician coordination.

Before working with JenX, these operations ran on paper. Every shift produced physical logbooks. Field technicians filled out paper inspection forms on-site. Maintenance records were filed manually. Compliance reports required collecting data from stacks of logbooks, transcribing it into spreadsheets, and sending it to management.

The consequences were predictable:

Data lag: Management saw operational data days after the fact, not in real time
Errors in transcription: Moving data from paper to spreadsheet introduced mistakes
No audit trail: Determining who logged what, and when, required physically tracing paperwork
Reporting burden: Producing compliance reports took significant staff hours per month
No centralised view: Operations across multiple sites had no unified visibility

The Solution: A Custom Operations Management Platform

JenX Technologies designed and built a web application that digitised the entire operational workflow — accessible from any device, including the field technicians’ mobile phones.

Core Features

Digital Logbook System Every paper logbook was replaced with a structured digital form. Field technicians log readings (pH levels, turbidity, chemical dosing, water flow) through a mobile-friendly web interface. Data is timestamped, user-attributed, and immediately available to supervisors and management.

Real-Time Operational Dashboard A management dashboard showing live operational data across all plant sites. Key metrics are visualised in charts and tables. Out-of-range readings are flagged automatically, with notifications sent to the responsible supervisor.

Maintenance Tracking and Scheduling Equipment maintenance records moved from paper files to a structured database. Technicians log maintenance activities with photos and notes. The system tracks equipment maintenance history and generates alerts when scheduled maintenance is due.

Compliance Report Generation Monthly and quarterly compliance reports — previously a multi-day manual effort — are generated automatically from logged data in minutes. Reports export in standard formats ready for regulatory submission.

User Role Management Three access levels: field technician (can log data, view their own records), site supervisor (full site visibility, can assign tasks), and management (cross-site dashboard, reporting).

Technology Stack

Layer	Technology
Frontend	React (TypeScript)
Backend	Node.js with Express
Database	PostgreSQL
Auth	JWT with role-based access
Hosting	Azure Web Apps
File Storage	Azure Blob Storage
Notifications	Email (SendGrid)

React provided the responsive, mobile-friendly interface that field technicians needed on-site. PostgreSQL’s relational model handled the structured operational data and the complex querying required for compliance reports. Azure hosting ensured reliability without requiring APAS Bharat to manage server infrastructure.

The Build Process

The project ran over 16 weeks:

Weeks 1–2 (Discovery): On-site observation of the paper-based workflow. We photographed existing logbooks, interviewed field technicians and supervisors, and mapped every data point that was being recorded on paper. The goal: understand the existing system deeply before replacing it.

Weeks 3–4 (Design): Figma prototypes of every screen. Special attention to the mobile interface for field technicians — large touch targets, offline resilience (forms that could be saved locally and synced when connectivity returned), minimal typing through dropdown selections where possible.

Weeks 5–13 (Development): Eight weeks of sprints, with weekly demos. Field technicians participated in testing from Week 7 onwards — their feedback changed several UI decisions.

Weeks 14–16 (QA and Rollout): Parallel running — both paper and digital systems operated simultaneously for two weeks to validate data accuracy. Technicians were trained on-site. Paper process formally retired at Week 16.

The Outcome

Six months after launch:

Zero paper logbooks in day-to-day operations across all sites
Real-time data access — management views operational data the moment it is logged
Compliance report time reduced from 3 days to 2 hours (from multi-day spreadsheet compilation to automated generation)
No data transcription errors — data entered once at the source, used everywhere
Full audit trail — every reading, every change, every user action is logged and queryable

The platform also surfaced patterns that weren’t visible in the paper system — seasonal variations in water quality, equipment that needed maintenance more frequently than scheduled, and site-level performance comparisons that helped management prioritise resources.

What We Learned

Start with the humans, not the technology. The most important work we did was observation — understanding how field technicians actually worked before prescribing a solution. A technically elegant app that doesn’t fit real-world workflows gets abandoned.

Offline resilience matters for field applications. Water treatment sites don’t always have reliable connectivity. Building offline form saving and background sync doubled development time but was essential for adoption.

Phased rollout reduces risk. Running paper and digital in parallel before retiring the paper system gave APAS Bharat confidence and gave us time to catch edge cases before they caused operational problems.

Automation creates value beyond the obvious. The compliance report automation was expected. The operational insights from aggregated data — something impossible with paper — were not anticipated but became one of the most valued features.

This project defined our approach: deep discovery before design, design before code, and systems built around the people who use them.

Have a similar operations challenge? Contact JenX Technologies — we’ve done this before.

freelance app development hiring 2025 trends