A raw data export gives you numbers, but a manager or a regulator usually wants a document: a titled, dated, laid-out page that reads the same every time. A scheduled PDF report is that document, rendered automatically from historian data on a fixed timer and produced as a finished, page-formatted file rather than a spreadsheet. This guide explains how the report engine turns stored tag values into a branded PDF, what goes into the layout, and why pixel-fidelity output is a different job from a raw data dump.
Scheduled PDF Report in one line: A scheduled PDF report is a formatted document - a daily production sheet, a shift summary, a compliance page - that a SCADA report engine renders from historian data on a schedule and outputs as a fixed-layout PDF. Unlike a CSV export it carries a designed template with headers, tables, and embedded trend charts, so the page looks the same and prints the same every time it runs.
A scheduled PDF report starts from a template that a person designs once. The template defines the page: a header band with a company logo and the report title, the reporting period, a body split into tables and charts, and a footer with page numbers and a generation timestamp. Placeholders in the template point at tags, calculations, and time ranges rather than at fixed numbers. When the schedule fires, the engine reads the historian for the requested period, resolves every placeholder to a real value, and paints them into the layout.
The rendering step is what separates a PDF report from a data export. The engine has to lay out text into columns, wrap long tables across page breaks, size and place embedded trend charts, and keep headers and footers on every page. The result is a fixed-layout file: the position of every element is baked in, so the report a manager opens on a phone looks identical to the one that prints on the wall of the control room. That fidelity is the whole point of choosing PDF over a spreadsheet.
Embedded charts are usually rendered by the engine at generation time rather than linked to a live dashboard. A daily production report might include a 24-hour trend of tank levels drawn as a static image inside the page, a table of hourly flow totals, and a summary row of the day's total volume. Because the chart is rendered into the document, it stays correct forever - reopening last month's report shows last month's trend, not today's live data.
The template engine gives a report a consistent identity. Fonts, column widths, section order, logo placement, and color are set in the template and reused on every run, so a shift summary produced on Tuesday is visually indistinguishable from one produced three months later except for the numbers. This matters when reports leave the company - a regulator or a partner receiving a compliance sheet expects a stable, professional document, and a well-branded PDF signals that the data is being handled carefully.
Fixed layout also protects the meaning of the report. A spreadsheet can be re-sorted, columns can be hidden, and a formula can be edited after the fact, which makes a raw export a poor record of what was actually reported. A rendered PDF is a snapshot: the numbers, the layout, and the timestamp are frozen at generation. That immutability is why compliance and production reports are so often delivered as PDF even when the same data is also available for download in a machine-readable form.
The trade-off is that a PDF is designed for a human to read, not for another system to parse. That is why the two output styles coexist: a pixel-perfect PDF for people and records, and a raw export for downstream analysis. A mature report engine can produce both from the same scheduled run, so the finance team gets a clean page while an engineer gets the underlying rows.
In a cloud SCADA the historian, the template engine, and the scheduler all sit in the same platform, so a scheduled PDF report is generated on the server and delivered without anyone opening the application. A daily production report can fire at six each morning, render itself from the previous day's logged values, and land in inboxes before the first person logs in. Nobody has to remember to pull it, and because it runs on the server the report is produced even on days when no operator visits the site.
This automation is most valuable where reporting is a recurring obligation. Field operations that owe a daily volume sheet to an office, a shift summary to the next crew, or a periodic compliance page to an agency benefit from a report that assembles itself the same way every time. Removing the manual step also removes a class of errors - transcription mistakes, forgotten sends, and inconsistent formatting - that creep in when a person builds the same document by hand each day.
Because the engine works from stored history rather than from a live screen, a scheduled PDF report can also be regenerated for a past period if a template changes or a report is lost. The data was logged; the template describes how to present it; so the same day's report can be produced again months later and will match the original. That reproducibility is part of what makes rendered reports suitable as a durable business and compliance record.
A CSV export delivers raw rows of tag values for a machine or a spreadsheet to process, with no layout, branding, or charts. A scheduled PDF report renders those values into a designed, fixed-layout page with headers, tables, and embedded trend charts meant for a person to read or file. Many platforms produce both from the same run, since one serves analysis and the other serves records and communication.
Yes. The report engine can render a trend chart as a static image inside the page - for example a 24-hour tank-level curve on a daily production report. Because the chart is drawn at generation time from the period's historian data, it stays fixed in the document, so reopening an old report shows that period's trend rather than current live data.
A PDF is a frozen snapshot: its numbers, layout, and timestamp cannot be re-sorted or quietly edited after generation, which makes it a stronger record for production and compliance use. It also renders identically on any device and printer, so the version a manager reads matches the one filed or sent to a regulator. Spreadsheets remain useful for downstream analysis, which is why both formats are often produced together.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.