PostMan

KISEM Detailed Energy Assessment report generator — IEA, IIT Gandhinagar.

The whole tool is one file

PostMan.html — double-click it. That is everything: the editor, the report engine, the bill reader, the charts, the exports. Nothing to install, no server, no npm install, no folder of parts.

To share it with a colleague, send them that one file. To keep a version, copy it. It opens in any modern browser and keeps your draft in that browser, so two people opening the same file each have their own work.

The same file is served online as index.html (repository https://github.com/rdudr/PostMAN, deployed by Vercel on every push). Both are built from the parts in src/ by python src/build.py.

Where the work is kept

Every keystroke is saved in the browser, as it always was, and the tool runs with no network at all. Beside that there is now a server at https://eass.eassiitgn.page — the team's own machine at IIT Gandhinagar, published through the Cloudflare tunnel already running on it. Sign in and the report is kept there too, listed for the whole team, with every earlier save behind it. The server, its API and how to put it on Oracle Cloud are in server/README.md.

Nothing is lost, and there is no gap between these four rules.

1. Every change goes into this browser at once — a local write that cannot fail for want of a network.
2. While you work, the server is kept a couple of seconds behind. A push that fails retries itself — 5s, 10s, 20s, 40s, then every minute — rather than waiting for you to type something else.
3. Closing the tab, reloading, or just switching away from it pushes what is outstanding there and then. A report is about 25 KB, so this normally finishes even as the page goes.
4. Anything rule 3 could not finish goes up the moment the app next opens, before anything else. This is the one the other three lean on: a browser being closed can never be relied upon, so nothing depends on it alone.

Everybody signs in as themselves, with their KISEM FOX username and password. No second pair to remember, and the activity trail names the person who did each thing rather than a shared account. While a report is open, PostMan watches for a colleague saving it and says so in the strip — "Rahul Patel saved v2", with one button to load their copy — long before anybody can type themselves into a clash.

Opening PostMan asks who you are — every time, on every machine. A reload, a new tab, a laptop picked up the next morning: the sign-in page comes first. Nothing is kept in the browser between sittings, so a shared plant computer holds no session for the next person to walk into. The draft is not touched by this and neither is the report it belongs to: signing in carries on with the same report rather than starting a duplicate, and whatever this browser holds and the server does not goes up the moment there is a password behind it. Within a sitting you stay in — a server that cannot be reached is not a reason to log anybody out, and the session renews itself, so a long day on site does not end in a surprise. Only a definite "that token is no longer valid" returns you to the sign-in page, with the reason on screen and the draft untouched.

Two people on one report do not overwrite each other. The second save is refused, saving pauses rather than retrying into the same wall, and the screen offers the two honest answers side by side: take theirs, or keep mine as a separate report. The editor can tell its own last save from a colleague's, so a reload is never mistaken for a clash.

What it needs from the internet

Nothing, to run. It will reach out for three optional things:

Report fonts	falls back to close matches if unavailable
Spreadsheet reader	needed to import JET-Eff / A-CMP / module workbooks
OCR reader	only for photographs of bills; downloads ~5 MB the first time

Bills supplied as PDFs are read without any of that. If the OCR reader cannot be downloaded — no internet, or a network that blocks it — the screen says so plainly and you read the figures off the bill, which is displayed full-size beside the fields.

The workflow

1. Cover & report — company, financial year, logo, gate photograph.

2. Electricity bills — built to the team's own workbook ("EB Bill & Base", sheet Report Formet): the nine yellow cells per month — month, units, bill amount, power factor, actual MD, energy rate, FPPA rate, night units, TOU units — plus the tariff header (DISCOM, consumer number, contract demand, tariff) are read off the bills; every other column is a formula or a GERC default (85 % minimum billing demand, Rs 150/260 demand slabs, TOU Rs 0.85, EHV 1 %, duty 15 %, the PF rebate/penalty bands). A Difference column reconciles the computed bill against the amount read off the bill, so a misread figure or a default that does not apply shows as red. The full analysis prints on three turned sheets in the workbook's layout — the reader turns the page clockwise — followed by the standard summary, load factors, charts, and the PF and contract-demand proposals. Rates not printed on a bill are derived from its charges and marked so. 2a. Bill capture & verify — drop in bill PDFs or photographs. A DISCOM bill that runs to three sheets stays one bill: the pages of a PDF are grouped by the month they name, the figures are read from whichever sheet carries them, and the others are a click away on the same screen. Figures are read out automatically and shown beside the bill itself; check each one and press Verify. Nothing counts until a person has looked at it. A wrong file is undone with Clear this bill, Delete this month, or Start over.

3. Import field data — one door for every workbook. JET-Eff, A-CMP, the FOX KISEM export, a PQ-analyser "PostMan export", or the module workbook you can download from that screen and take to site. The file is identified from its own contents and checked against this report's company before anything is written. 3a. Single line diagram — built from cards, not drawn: add a main input, then PCC panels under it, MCC panels and loads under those. Each card holds the rating, kW, kVA, PF, %VTHD, %ITHD and the PQ recording ID; boxes size themselves to their text, a provisional node is dashed, and a node over the IEEE-519 THD limits is outlined red. Click a box to select it and press Delete (or the card's Delete) — its children move up to its parent. 3b. Electrical distribution chapter — assembled in this order: the single line diagram; the demand study; one section per plant main input and then per PCC panel, each with Measured at the panel (the FOX figures) and Power quality analysis (the analyser recording: voltage, current, PF, THD against IEEE-519, harmonic spectrum); the PCC load summary with its charts; MCC panels; the motor load study split into clamp-meter and PQ-analyser readings, each motor marked Working OK, Acceptable, Under-loaded or Overloaded by its load factor; and the APFC panels with a stage-current chart and remarks. Every table fed by FOX carries "Last uploaded data on from ". The full measurement charts for every recording go to at the very end of the report, listed in the Contents.

Going live

The ordered list of what is left to do - start the server, point the name at it, add the accounts, back the folder up - is docs/START-HERE.md.

Also in this folder

report design\ the KISEM cover and letterhead artwork as supplied · sample bills\ test bills including a 12-month PDF · sample reports\ the three reference reports the engine was derived from · logos\ IITGN and KISEM marks.

These are source material, not part of the tool. PostMan.html does not read them; you can move them anywhere.