Reports

TurbineX produces Certifier-grade PDF reports straight from completed studies. Reports are configurable: you pick the sections, metadata, and revision history, get a live preview, then click Generate. The output is a typeset PDF you can hand to a certification engineer, a customer, or your own archive.

What a report contains

Every report is built from a section tree. The catalog is organised into four areas:

• Front matter — cover, revision history, authors, approvers, document control.
• Configuration — turbine summary, site or IEC class, DLC matrix, sweep axes (parametric), solver settings.
• Engineering content — load rankings, envelopes, fatigue DELs, time-series excerpts for key cases, power-curve and Cp/Ct plots, mass and frequency tables.
• Verification and certification — IEC partial-safety-factor application, exception narratives, model verification annex (see Model verification).

Toggle sections on or off in the Report tab. The right pane shows live counts: number of sections, estimated page count, estimated build time on the report worker.

Report metadata

Set the metadata in the Report tab header. Stored on the report record (and stamped into the PDF cover page):

• Revision — free-form (e.g. 0.3, B, 2026-06-issue).
• Issued for — Draft, For approval, or Final. Drives the watermark and the cover-page banner.
• Authors / approvers— free-text. We don't gate on these matching org members so external partners are easy to credit.
• Revision history — a stack of (date, revision, issuer, notes) rows. Each generation appends a row by default; you can hand-edit to fix a typo.

Generating

Click Generate. The Report tab polls the report queue until the build flips to completed (usually under two minutes; longer for large parametric campaigns). The PDF loads in an inline iframe; an external Download button lives next to the preview.

Every generation produces a new report record — old reports stay attached to the study so you can show a customer both the For approval rev and the Final side-by-side.

Freshness signals

If you re-run a study after generating a report, the report list shows a stale indicator on every report produced before the new submission. This is a visual flag, not an enforcement: the stale PDFs still open and are still downloadable, but you know at a glance which ones predate the latest data. Generating a new report after the re-run clears the indicator.

Single-simulation reports

Single Simulation studies don't get the full certification section tree — they get a one-page executive summary (configuration, key channels, headline statistics) as a quick share asset. Useful for posting a smoke-test result in chat.

Parametric reports

Parametric studies add a Sweep results section that embeds the sweep matrix, the X-Y plots you bookmarked under Results, and a small commentary block per axis. The same section catalog is otherwise reused, so a parametric report can carry an IEC envelope alongside a power-curve sensitivity study.

Tips

• Generate a Draft first at a small section set and skim the PDF before committing to the full one — most fixes (a wrong revision number, a missing approver) are one field edit and a re-generate.
• Pin large studies to a specific solver build if you're going to re-generate over weeks. The Advanced tab on the study records the OpenFAST version that produced the data; mismatches show up as warnings in the report worker log.
• Hand the report engineer the JSON config too. The report includes the study's structured config as an appendix, so anything they need to reproduce is in the PDF.

Limitations

• The report builder runs single-threaded per study; two parallel generations on the same study are queued, not interleaved.
• Reports use TurbineX's house typesetting; brand-skinning (logo, color palette) is on the roadmap, not in v1.
• The PDF is a static snapshot. We don't embed the raw .outb — fetch those via the export tools.

Next steps

Run a small certification campaign (guide), generate a Draft report, then move to For approval. If you want Zeph to pre-fill the Report tab metadata, ask it in chat — see Zeph, your AI assistant.