Equipment datasheets and transmittal packages, generated from the model.
Datasheets bind to model data on demand; transmittals package, issue and track what you send.
Try it with a sample plant- Equipment datasheet (PDF), per element — 11 equipment families
- Datasheet register — on screen, with a per-row PDF download; no register file yet
- Transmittal package (ZIP) with an ISO 19650 cover sheet (PDF)
- Transmittal record — issued, acknowledged, tracked
- Client comments on the package — answered, closed, or raised as an issue
What this replaces
You already have the numbers. The pump’s duty point is in the hydraulic model, its tag is on the P&ID, its manufacturer is on the bill of materials — and the datasheet still gets typed, because none of those three can print an A4 sheet.
Then the drawing goes out as an email with attachments, and nobody can say which revision the contractor is holding, whether anyone opened it, or what they were meant to do with it.
Datasheets retyped by hand for every pump and valve
No record of what was issued, to whom, or when
Drawing packages assembled by hand before every issue
A datasheet is not a document you write. It is a view of data you already have.
How it works
What you get out
- Equipment datasheet (PDF), per element — 11 equipment families
- Datasheet register — on screen, with a per-row PDF download; no register file yet
- Transmittal package (ZIP) with an ISO 19650 cover sheet (PDF)
- Transmittal record — issued, acknowledged, tracked
- Client comments on the package — answered, closed, or raised as an issue
Datasheets are assembled from your model, BOM and simulation data. A competent engineer reviews the content before it is issued.
What each of those actually is
The equipment datasheet
One PDF per tagged element: a title block, a key/value table for each section of the template, and a footer naming the source of every printed value.
That footer is the point: a reviewer sees that the pump’s duty flow came from a simulation run and its manufacturer from the BOM line, rather than take the sheet on trust.
The ISO 19650 cover sheet
The first file in every package, and the reason the package is a transmittal rather than a zip of drawings. It carries the transmittal number and project, the purpose-of-issue code and what it means, the distribution list with each recipient’s organisation and role, your covering message, and a register of every item with its revision, code and file.
An item that could not be rendered gets its own row at the end, with the reason — a failure never quietly disappears from the package.
The purpose-of-issue code
Fifteen suitability codes from BS EN ISO 19650-2: S0 to S7 for work in progress and shared information, A1 to A7 for information authorised and accepted for a named downstream use — costing, tender, contractor design, manufacture, construction.
A new transmittal defaults to S2, shared for information; an item may override it, and the code prints on the cover sheet beside its description, so “S3” is never just three characters to whoever opens it.
What it is built to
- BS EN ISO 19650-2 — the fifteen purpose-of-issue suitability codes, S0–S7 and A1–A7
- SHA256 — the package archive, every rendered file inside it, and every datasheet value snapshot
Why this is not a document register
A document register stores the file you hand it. Here the file did not exist until the model did — and it can still tell you where every number on it came from.
Every field resolves from the model, the BOM line, the simulation run or a manual entry, in an order fixed in code rather than chosen per template. Two engineers generating the same drawing get the same document.
Regeneration hashes the resolved values — every section title, field id, unit and value, plus the template version — against the hash stored on the datasheet. Equal, and the revision does not move: “rev 3” is three real changes, not three presses of a button.
An item rendered from a frozen revision snapshot and one rendered from the drawing’s live state at build time are not the same thing, and the cover sheet marks which you are holding.
What it does not do
Four things this page gets asked for and does not do. You would find them out in week one anyway.
- No WIMES specifications and no O&M manualsNeither is generated. There is no WIMES template, service or seeded content in the product, and the only O&M reference is a stage-gate rule checking whether you attached a manual produced elsewhere.
- Nothing regenerates itselfGeneration runs when you ask and at no other time — there is no hook on drawing save, so you regenerate after a revision. That is deliberate: a document should not change under a reviewer.
- The datasheet register is not a fileIt is a table on screen with a PDF download per row. There is no CSV, spreadsheet or combined PDF of the register itself yet.
- Acknowledgement is per package, not per recipientWhoever opens the share link gives their name, and that is recorded against the transmittal. A recipient row is marked acknowledged only if that person also types a matching email, which is optional.
Technical capabilities
Questions people actually ask
Do datasheets update automatically when I change the drawing?
No. Generation runs on demand and only on demand — there is no hook on drawing save. Regenerate after a revision to pick up the latest values; anything whose resolved values did not move keeps its revision number.
Which equipment can I generate a datasheet for?
Eleven families ship a template: pump, valve, tank, blower, clarifier, dosing skid, filter, instrument, mixer, screen and thickener. The family is matched from the element itself — its process-unit type, then its symbol, then a keyword — and anything matching none of them is skipped rather than guessed at.
Can I prove the package a contractor holds is the one I sent?
The SHA256 of the archive is recorded against the transmittal when it is built, and each rendered file inside carries its own hash, so a package can be checked against the record rather than against memory.
What does S2 mean, and can I change it?
“Shared for information”, the default on a new transmittal. You can set any of the fifteen BS EN ISO 19650-2 codes instead, S0 to S7 or A1 to A7, and an individual item can carry a different code from the transmittal it travels in.
Does this cover WIMES specifications or O&M manuals?
No. Neither exists in the product in any form — this page covers what is shipped: equipment datasheets and transmittal packages. If a WIMES specification decides a purchase for you, tell us, because that is the kind of thing that gets built.
Issue something you can stand behind.
Bring one drawing, generate its datasheets, and put them in a transmittal with a cover sheet. That is the whole loop.