Loading...
Loading...
Pradrava Product • Live in production
The operating system for an industrial gas plant. Cylinder lifecycle, sales, procurement, production, laboratory quality, machines, dispatch and Indian statutory compliance — one system, one set of live data, multi-company and multi-branch.
Most software sold to gas companies is a cylinder register with an invoice screen attached. Fluids is the full operational chain: an enquiry becomes a quotation with a versioned amendment history, becomes an order that reserves stock and allocates specific cylinders, that gets filled and tested against a method with a calibrated analyzer, that passes final inspection with photographic evidence, that clears a compliance gate on hydro-test dates, that dispatches on a challan, that invoices with the tax split verified by the database itself, and that hands the posted document to your accounts system through a queue with retry and backoff. Nothing in that sentence is re-keyed.
End to end
Order to cash
Procure to pay
Capability areas
Everything that happens to a cylinder — arriving, being checked, filled, sent out, rented, serviced and returned — with a record behind every move.
A real laboratory system rather than a checklist — certificates, calibration, sampling and corrective actions that hold up when somebody audits you.
Indian tax handled on each document as it is raised, rather than reconstructed at month end.
From raising a requisition to paying the bill, with the checks that stop money leaking out along the way.
Filling, transfilling and manufacture — and how well the equipment doing it is actually performing.
Every handover in the plant gets an owner, a deadline and somebody it goes to if it slips — set by you on a settings screen, not by us in a release.
Several companies and several branches on one system, kept apart by how the data is built rather than by anyone remembering to keep them apart.
Built against
Runs without you
The work nobody remembers to do — chasing overdue payments, billing accrued rent, reclaiming stale reservations, pushing documents to accounts — happens on a clock.
Fit
Gas only
Cylinder lifecycle, filling, quality, rental and dispatch, without the item manufacturing side. Enforced on writes, so an item line cannot be created by mistake.
Item only
Inward inspection, item production with bill of materials, servicing and dispatch of non-cylinder goods, with the same procurement and finance spine.
Combined
Cylinder and item lines on the same order, the same dispatch, the same traceability and the same analytics — the way most plants actually operate.
A profile decides which capabilities exist at all — gas sourcing, bulk storage, whether quality control is mandatory, whether servicing is offered. The company sets the ceiling; a branch may narrow it further but never widen it.
Who uses it
One live picture of the plant — where the money, the assets and the risk are, today.
Nothing sits idle and nothing moves that should not.
Every result defensible, every instrument in calibration, every deviation closed.
Books that close from live data instead of a month of chasing.
The right cylinder, in the right bay, on the right vehicle.
Buy at the contracted rate, receive what was ordered, pay what was received.
Everything below is shipped and working today. Anything still in progress is listed separately at the bottom of this page.
Depth
Every operations product demos well for twenty minutes. What separates them is what happens on the day a customer cancels an order and you are still holding their cylinders, or the day someone banks the same cheque twice. These are the answers to those days — all shipped, all working now.
Record a customer receipt against an invoice — full or part — by cash, cheque, NEFT, RTGS, UPI or card. An over-payment is refused rather than quietly parked, a receipt is voided with a stated reason rather than deleted, and the invoice balance is maintained by the database so two people banking the same cheque cannot both succeed.
You cannot delete a bottle that is customer-owned, still holding gas, committed to an order or named on a live document — and the refusal tells you which of those it is. What you can do is retire it, which keeps its inward log, service history and consumption ledger intact and is reversible.
A cancelled order leaves physical cylinders somewhere. Each one lands in a disposition queue with five outcomes, and a customer-owned bottle can only be returned to its customer — enforced in the application, in the choices offered, and by the database. The cancellation is not complete while you are still holding somebody else's cylinders.
Type the id painted on the bottle and get, in one answer: where it is standing, what is holding it, which sales order, which purchase order, which vendor it went to, on which challan, and what happens to it next. If it is on no document at all, it says so rather than showing you an empty board.
The three-way match runs on percentage and rupee tolerance bands you configure per branch, falling back to a company default. The screen tells you which of the two is actually in force — and says plainly when neither exists and it is running at zero tolerance.
Before a bottle can be sent to a third-party filler, the system checks that a fill range exists for bringing it back. Without that check a cylinder leaves the gate, gets filled, and is then refused at your own receiving bay — with the challan open and the purchase order unsettled.
Not a completeness percentage. A ranked list: 37 customers with no address, 9 capacity-and-gas pairs with no refill range, 2 addresses with no GST state code — each one saying what it will break downstream and which screen fixes it. Master data gaps fail somewhere else, weeks later, on somebody else's screen.
An administrator console over sessions, every action taken, every permission refusal, browser crashes, endpoint health and open tax discrepancies. Failed sign-ins are captured and repeated failures from one address are blocked. Log retention is a number you set on that screen, with a floor, and no setting that means delete everything.
Off by default, because in a two-person branch the same person legitimately raises and approves. Switch it on and the person who raised a requisition, created a vendor invoice or requested an order cancellation cannot be the one who approves it. An unknown creator never blocks an approval.
Every save carries a key that identifies it, so an impatient second tap, a patchy connection or two tabs open on the same form give you back the original answer instead of a second purchase order — and if a save times out, it tells you it may have gone through rather than inviting you to try again and make two.
Tanker receipts weighed gross and tare, tank level events, boil-off, and tank-to-cylinder transfer — with the tank ledger reconciling to the kilogram. A finalise that would overfill a tank is refused, and the room remaining is shown while the weights are being keyed rather than at the end.
Quotation, order, delivery challan, invoice, credit and debit note, certificate of analysis, goods receipt, purchase order and more — server-rendered to PDF with your own header, footer, terms and sections, configured per branch and per document type. Email them from the same screen, routed to the right department mailbox.
We would rather you knew. These are implemented in the product but not switched on for customers yet, usually waiting on a third-party provisioning step.
FAQ
It is a full operations system for a gas plant. Sales, procurement, inventory, production, quality, machines, dispatch and finance all run on the same data, with cylinder operations as the domain core. If you already run accounts elsewhere, Fluids hands documents over to it rather than replacing it.
It is built into the structure of the data rather than left to convention. Every table says whether it belongs to a branch, a company, a location or is genuinely shared, and the build fails if a new one is added without saying. Somebody assigned to one branch cannot read or write another branch's data by any route.
No. You can set the system to gas only, items only, or both, and it is enforced when data is saved rather than just hidden from the menu. Beyond that, your plant profile — full plant, on-site production, import-and-fill, bulk-fill — decides which capabilities exist at all, and any of 28 modules and 45 sub-modules can be switched on or off per company or per branch without a code change.
Properly, on the documents you raise. The place of supply is worked out from the supplier and recipient states and the system refuses to guess; intra-state versus inter-state, HSN/SAC, per-line rates from a table you can edit yourself, and gapless numbering per GSTIN and financial year. The tax is calculated twice by separate code and the invoice will not issue if the two disagree. E-invoice and e-way bill payloads are prepared and are connected to your GSP at go-live. Filing your returns is not something Fluids does — that is your accountant's portal, and a fuller returns capability is coming with Pradrava Accounting.
Yes, at several points. Cylinders past their hydro-test date or missing CCOE documentation are blocked by the compliance gate. Storage bays only accept the gas classes they are declared for, so a flammable cylinder is refused by an inert-only bay. Final inspection with photographs gates the dispatch board, and a delivery with no proof of delivery blocks invoicing.
They hold up. Test methods are versioned, results carry the analyst's and reviewer's electronic signatures, every edit after entry is written to a record nobody can change, an analyzer must be inside its calibration date for a result to count, and certificates are issued to ISO 6141 with ISO 6142 uncertainty per component.
No. There is a simplified full-screen mode for shop-floor stations with big touch targets and a chime for new tasks, a phone-as-scanner mode where a desktop opens a session and a phone joins it by scanning a QR code, and a companion scanner app for Android and iOS handsets that we install on your devices — it is in preview, not on the app stores.
Sixty-five points in the plant — enquiry created, cylinder assignment pending, gas test failed, refill received, requisition awaiting approval, return available and so on — raise a task for a named role with a deadline. Fifty-six of the seventy-one rules also carry an escalation, so an untouched task moves to the person you nominated without anybody chasing it. Which role, how many hours, who it goes to next, and whether the rule is on at all are settings, not code.
Yes. CSV export on the operational registers, seventeen printable document types with your own header, footer and template, and a documented API if you want to pull it programmatically.
Cloud-hosted in the Mumbai region, on managed infrastructure with a managed database. Error tracking and performance monitoring are wired in. There is nothing for you to run or maintain in the plant.
Get Started
Book a walkthrough and we will run your hardest process — the awkward rental billing, the multi-branch transfer, the quality certificate your customer keeps rejecting.