Capability 05 · Enterprise Reporting · the Reports module

The paperwork writes itself, sealed and signed.

A plant is rarely short of data. It is short of documents — a sheet with a window, an author, a number and a seal, that reads the same a year from now as it did the day it was filed.

What leaves this plant is a record, not a dashboard. Say what one paper is about and the moment it should go out, and from then on it exists: on the clock, on a batch, on a plant condition, or on a maintenance job that has just closed.

Every sheet the plant needs, and what makes it appear.

the designer
the timing card
the condition
the maintenance job card
the plant floor
the runs pane

You want	What SOP does	Where
The shift handover on the desk when the next crew walks in	Every shift, delivered as soon as it ends, on the site's own shift plan	`set once in the designer, read on the plant floor`
Yesterday's line on your desk before the morning meeting	Every day, handed over at the hour you name	`the designer, the delivery time`
The week reviewed and out on the day you choose	Every week, delivered on the day you name	`the designer, the delivery day`
The month closed and filed	Every month, delivered on a day the calendar always has	`the designer, the delivery day of the month`
A certificate born with every batch	The batch is the window; the paper exists the moment the batch closes	`the designer, the timing card`
One sheet for a whole production order	The order is the window, the same way	`the designer, the timing card`
A signed record every time a maintenance job closes	The job is a period too: its checklist, its readings, its parts and its signature on one sheet	`the maintenance job card, at its foot`
A record of each wash, run or charge	One report per cycle of a condition you name, out at the stop	`the designer, the condition`
What led up to a trip or a spill	The stretch before the condition fired, and you set how far back it reaches	`the designer, the condition`
Everything since the last delivery, refill or batch	Gap free, fired as the next one begins	`the designer, the condition`
A sheet for a window nobody's calendar names	A range you type, stamped honestly as a fixed range and run on request	`the plant floor, above the sheet`
The audit sheet for the machines the auditor names	The line review narrowed to that machine list, and nothing else changes	`the designer, the machines row`
Last month's copy back exactly as it was, or the numbers in a spreadsheet	Every run ever filed, one press away, and one export carrying every table in the run	`the plant floor, the runs pane`

A report is born covering every shift and going out to nobody, so it exists and holds its design until somebody says where it should go.

01/07

A reporting engine

A reporting engine, not a report server.

What the class sells as a separate report server — its own designer, its own store, its own licence and a seat for everyone who only reads — is an organ of this platform.

Design a sheet once against the tags the line already reads; the platform computes it, seals it, signs it and delivers it, with nobody watching.

Design once, and the paper writes itself:

The designer — the blocks, the live preview and the named timing cards.

01 DesignBlocks bound to real tags: headline tiles against the plant's own plan tag, period tables, trends carrying their alarm limits, alarm journals, consumption and cost, the performance cascade, the maintenance sheets.
02 ComputeOn the server, in the site's own clock: every shift, day, week or month; every batch or production order; every maintenance job; or the moment a plant condition fires. Nobody presses anything.
03 SealFrozen on arrival, given a document number, sealed with a hash. Run it again and a second document is filed beside the first — never a refresh.
04 SignBy name and by the capacity the signer answers in, proved with their own password, bound to the seal, never edited and never withdrawn.
05 DeliverPrinted on the plant's own letterhead in three languages, posted to a list, filed as a PDF, exported when somebody wants to work the numbers.
0 report serversThe engine runs on the backend the plant already installed; a small worker beside it draws the sheet and posts it to the list.
0 third-party licencesNo reporting product, no rendering licence, no designer bought separately — it is inside the platform.
A blank certificate is refusedA report that would print a blank certificate is refused while it is still being designed.

Seen in the product

The editor on a batch certificate — the blocks, the live preview, the name in three languages, the timing.

The same record as the plant prints it, on paper.

02/07

Bound to the tag, never typed

A report is a stack of blocks, and every block points at a real signal on the line.
Even the target a tile prints against is read off the plant's own plan tag, so there is no second copy of the plan to keep in step.

Everything the plant otherwise rebuilds in a spreadsheet: headline tiles with targets read off the plant's own plan tags · the period table · trends carrying their own alarm limits · bar, donut and scatter charts · gauges scaled from the tag's own range · heatmaps · machine timelines · alarm journals and rankings · consumption priced from a dated rate book · the performance cascade · and the maintenance blocks that put the plant's work orders on a sheet.

Say which tag a block reads, and what to ask of it:

The headline tile rowThe number, the plan and the gap on one line, from the plant's own two signals; the target is read off the plant's own plan tag, never typed.
The period tableThe tags down the side, the periods across, the statistic named in each cell; the sheet already filled, with its totals, and no spreadsheet to maintain.
The trend with its alarm limitsThe curve with the limit lines on it, inside the certificate — proof a tank never left its band.
The alarm journal and its rankingWhat raised and when it was acknowledged during the window, and the worst offenders in order beside it.
Consumption and costEach medium metered and costed bucket by bucket, priced from the plant's dated rate book; a tariff that changed inside the window is honoured, not averaged.
The performance cascade and the loss rankingWhere the hours went: the losses in time, in units and in money, on paper, from the figures the screen already shows — and the losses ordered beside it.
Charts, gauges, heatmaps, machine timelinesThe plant's own figures drawn on the sheet; gauges scaled from the tag's own range; the window read as a grid; each machine's window drawn end to end.
The maintenance blocksThey put the plant's work orders on a sheet.
Every block points at a real signalThe statistic is named per cell, at the bind-an-element door and the statistic menu.
A tag with no history is called outWhile you are still designing, not when the paper comes out empty.

Seen in the product

The door that says which element a block reads.

The statistic menu, and a target read from a tag, never typed in.

03/07

Compute, seal and sign

Never edited. Never withdrawn.

Nobody presses anything.

Two questions, asked once: the stretch of time one paper is about, and the moment it leaves.
Six named cards write both, and a plain sentence reads the whole setting back before you save.

Each run is computed once, frozen the moment it arrives, given a document number and sealed with a hash.
A signature adds a person's name, the capacity they sign in and their own password, bound to that seal.

Two questions, asked once:

The named cards, the read-back sentence and the next delivery.

Per shiftThe handover files itself as the shift closes, on the site's own shift plan.
Daily digest, delivery time 06:00The day that ended, handed over at the hour you set; the clock chooses the delivery, never the window.
Per batchNo calendar at all: the record is the period, and the paper goes out as the batch closes — for a batch or a whole production order.
Per cycle, then the conditionOne report per wash, start to stop, arriving as the wash ends (example setting: signal CIP pump run flag, running means 1).
On excursion, then the conditionThe stretch before the crossing, delivered minutes after it happens (example setting: signal tank level, above 95, reaching 120 minutes back).
Since it last ranDelivery to delivery, gap free, arriving as the next one begins (example setting: on the unloading pump's start).
A short grace past the edgeThe report waits a short grace so late readings still make the paper.
A switched-off condition says soWhile a condition is switched off nothing fires, and the report says so wherever it is seen.

the ruler: what a report covers, and when it goes out — the ruler, taught once: the shaded stretch is what the paper covers, the flag is when it leaves

Never edited. Never withdrawn:

The provenance strip above the first block.

Computed once, frozen, numbered, sealedEach run is computed once, frozen the moment it arrives, given a document number and sealed with a hash.
Read the filed run, not a live screenOne frozen document with a number, reading the same a year from now — so two people cannot quote different figures for the same shift.
Run it again after a correctionA second document filed beside the first and numbered in sequence; the original is never overwritten.
Sign — name, capacity, own passwordThe name, the capacity and the moment printed on the sheet and bound to the seal.
Two signatures, one capacity eachBoth print; the same person may sign in more than one capacity, never twice in the same one — an author and a reviewer on the same sheet.
The seal is checkable outside the buildingThe document number and the full hash print on the sheet, and a printed warning appears the day the numbers stop matching it.
No signing door on a shared stationA signature names a person, not a device; sign from your own session.
What a signature leaves behindThe signer's name, the capacity, the moment and the site's own time zone, printed above the end marker and bound to the seal, with the note they chose to leave.
A signature cannot be withdrawnIt cannot be undone, and it cannot be quietly withdrawn.
No ruled blank to sign by handAn unsigned sheet prints none, so a document is either signed properly or it is not signed at all.

the seal chain: computed once, frozen, numbered, sealed, signed — the seal chain: computed once · frozen · numbered · sealed · signed — and, from frozen, a second document filed beside the first

Seen in the product

The three doors a filed run offers, signing among them.

The product's own timing guide, teaching the same ruler.

04/07

The plant's letterhead, three languages

One design prints English, French and Arabic, right to left included, on the letterhead of the site that owns it.
It leaves by mail to a list, is filed as a PDF by a small worker beside the backend, and comes out as a spreadsheet when somebody wants to work the numbers.

What the paper carries: A4 on the letterhead of the site that owns it, page x of y on every sheet, an end marker that says the set is complete, a document number, and a hash anyone can check outside the building.

It leaves, and it comes back:

The last sheet of a document: the end marker, page x of y, the document number.

Mail to a listThe sheet lands in their mail as the shift closes, through the plant's own mail server.
Filed by the workerThe A4 in the plant's own store moments after the run, with nobody watching.
Export the numbersOne file carrying every table in the run, copied from the frozen document, never recomputed.
Three languages from one designEnglish, French and Arabic, right to left included, each reader in their own language — the same sheet, the same figures.
The plant's own letterheadA4 on the letterhead of the site that owns it.
Page x of y, and an end markerPage x of y on every sheet and an end marker that says the set is complete.
Reprint from the archiveThe sheet it was issued on, page x of y, the end marker, and the document number it was born with — three years later.
Only self-firing runs post themselvesA run somebody pressed by hand is sent from the archive by hand, on purpose.

Seen in the product

One filed run in the archive, its stored sheet one press away.

A daily production sheet as the engine files it — the headline tiles, then the period tables by shift.

05/07

The sheets a plant runs on

The reports a plant needs already exist as designs you can open and change: the shift handover, the batch certificate, the maintenance record, the audit sheet for critical equipment, the excursion report and the monthly review.

Each one asks which tag on your line is which, then lands in the designer as an ordinary report.

Ready made and yours to change:

Pick a design that already works, then answer the one question it asks.

The shift handoverThe classic sheet: what the shift made, what stopped it, and what the crew wrote down.
The batch certificateWhat the batch was, what went in, how it ran against its plan, and a line for the person who releases it.
The maintenance recordOne job: its checklist, every reading judged against its band, the parts it used, and the signature that closed it.
The audit sheet for critical equipmentThe line review narrowed to that machine list: the same numbers as the whole line's review, turned into a machine dossier.
The excursion investigationThe trace, the alarms and the stops around a bad hour, with a line for what the plant thinks happened.
The maintenance reviewPlanned against done, what broke, what it cost, and who did the work.
Each ready-made asks one questionWhich tag on your line is which — then it lands in the designer as an ordinary report.
Blocks that contradict the period are refusedRefused while it is being designed, so a certificate that would print blank never reaches a customer.

Seen in the product

The step that asks which tag on this line is which.

One job's record as the plant prints it — each reading judged against the band it had to fall inside.

06/07

In the hand

Read it, print it, sign it, from a phone.

The record is not a second application: the same console opens on a phone with nothing installed, and the person who has to act on the sheet reads it where the plant is.
The supervisor who signs the handover signs it on the floor.

The sheet is the record, not a copy of one.

The same console, sized for a hand:

The filed sheet as it was filed, with its document number and its seal.

No second applicationNo viewer application to install, no second licence, no separate rights.
The same consoleThe report list, the window chips, the sheet itself and its three doors are the ones the desk sees, in the reader's own language.
Read the filed sheet on the phoneThe handover as it was filed, with its document number and its seal.
The picker is the runPick the batch above the sheet and the pick itself computes and files that batch's certificate — nothing else to press, nothing to type.
Sign from the phoneThe signature on the sheet, bound to the seal, taken where the line is.
Print or save from the same runThe A4 on the plant's letterhead, sent from where you stand.
On the floorThe supervisor who signs the handover signs it where the line is, not at a desk on the way out of the building.
The technician's own recordA job closed on the phone prints its own record from the card: the checklist, the readings, the parts it used and the signature that closed it.
One security model reaches the sheetWhat a person may not see on the line, they may not read on the paper — the same rule, the same session, whichever screen.

Seen in the product

The job behind the record, on the same phone.

The reader on the plant floor — the window it covers, the number and the seal.

07/07

Energy

Each medium metered and costed, from the plant's own rate book.

Consumption priced from a dated rate book

Energy is not a product bought beside the plant's software: it is read by Equipment Performance System and by Enterprise Reporting, on the same rows as everything else.
Each medium is metered and costed bucket by bucket, priced from the plant's dated rate book.

A tariff that changed inside the window is honoured, not averaged.
The meter is a tag like any other: every block points at a real signal on the line, and the statistic is named per cell.

What a sheet can say about a medium:

Consumption and cost — Each medium metered and costed bucket by bucket, priced from the plant's dated rate book; a tariff that changed inside the window is honoured, not averaged.
The period table — The tags down the side, the periods across, the statistic named in each cell; the sheet already filled, with its totals.
What the losses cost — The performance cascade puts the hours on paper in time, in units and in money, from the figures the screen already shows.

Gauges and heatmaps — Gauges scaled from the tag's own range; the window read as a grid.
The cycle a medium is spent on — One report per wash, run or charge, out at the stop, from a condition you name.

What ships with it

Where	What ships
On the line	The designer in a browser, the reader on every screen and every phone, and an archive that keeps every run for as long as the plant keeps anything.
On paper	Your own letterhead in three languages, page x of y on every sheet, an end marker, a document number and a seal anyone can check.
Around it	The manuals, a flight-test document per module a validation team can follow, and a demonstration line to try a sheet on before it goes near a customer.

And what no other platform does like us

A filed report as the plant floor reads it.

A reporting engine, not a report serverWhat the class sells as a separate product with its own designer, its own store and its own licence is an organ of this platform.
Bound to the tag, never typed inEvery block points at a real signal on the line, and even the target a tile prints against is read off the plant's own plan tag.
Nobody presses anythingTwo questions asked once, six named cards, and the paper leaves by itself: on the clock, on a batch, on a plant condition, or on a maintenance job that has just closed.
Never edited. Never withdrawn.Computed once, frozen on arrival, numbered and sealed; a signature cannot be undone and cannot be quietly withdrawn.
A seal anyone can check outside the buildingThe document number and the full hash print on the sheet, and a printed warning appears the day the numbers stop matching it.
The plant's own letterhead, in three languagesEnglish, French and Arabic, right to left included, from one design — the same sheet, the same figures.
What a person may not see on the line, they may not read on the paperThe same rule, the same session, whichever screen it is opened on.
One clock, one key, one archiveThe same shift on every module; a tag keeps one identity from the register in the controller to the printed sheet; the handover, the certificate, the job record and the review are filed side by side, and none can be edited or removed.

A released maintenance job books a window the performance engine already honours, and the sheet that proves the job prints from the engine that prints the handover. There is no export, no nightly copy and no mapping table between them. Nothing to connect, because there is nothing to connect.

Contact

Write to us.

Start with one word so it reaches the right desk: PARTNER · PLANT · PRESS · INVEST. Tell us the country, what the line or machine produces, and which controllers are already on it. We reply from a person, never a queue.