Why the Report Matters

A calculation package is not optional in the tank design workflow. EPC clients, owner companies, and independent certifiers all require a traceable, clause-referenced document that a third-party engineer can review without access to the software. The TankCode 650 PDF report is built to satisfy this requirement directly — not as a printout of raw numbers, but as a structured calculation document with governing equations, input echoes, intermediate steps, and explicit API 650 clause references on every page.

Before generating the report, complete all relevant modules. Any module that has not been run will appear as "Not calculated — data not available" in the corresponding section. See the getting started guide for the recommended module sequence.

Step 1 — Fill in the Cover Page Fields

Navigate to Report → Cover Page. The following fields populate the report header and are stamped on every page footer:

  • Project Name — client project title
  • Project Number — your internal document number
  • Tank Tag — equipment tag (e.g., TK-101)
  • Prepared by — engineer name and designation
  • Checked by — reviewer name (leave blank if not yet checked)
  • Revision — document revision (0, A, B, …)
  • Date — auto-populated to today; editable
  • Client — client company name (optional)

These fields are stored with the design record in the database, so every subsequent export of the same design retains the project metadata. If you update the design and re-export, increment the revision number manually.

Step 2 — Report Section Structure

The report follows a logical design sequence from geometry through to foundation loads. Each section corresponds to a module:

SECTION API 650 REFERENCE KEY OUTPUT 1. Geometry Summary § 5.1 — 5.3 D, Hs, capacity 2. Shell Thickness § 5.6 (One-Foot / VDP) t_req per course 3. Roof & Ext. Pressure § 5.10, App. V Roof plate, stiffener 4. Wind Girder & Stability § 5.9, § 5.11 Zw, H₁(max) 5. Seismic & Anchorage App. E V, Mrw, J-ratio 6. Weights & Foundation § 5.12 Empty, operating, test loads
Report section map with API 650 14th Edition clause references and key outputs per section.

Each section includes: input echo (all parameters used), governing equations typeset with variable definitions, intermediate calculation steps, and the final result with pass/fail status where applicable.

Step 3 — Generate the PDF

Click Report → Generate PDF. The server-side PDF engine compiles all completed modules and renders the document. Generation typically takes 5–15 seconds depending on the number of modules completed. A progress bar shows compilation status.

Once generated, the PDF opens in a preview pane. From there you can:

  • Download — save the file locally (named TankCode650_[ProjectNo]_Rev[X].pdf)
  • Print — send directly to a printer or save as PDF via the browser print dialog
  • Share link — generate a time-limited secure link (valid 7 days) for sharing with reviewers who do not have app access

Version control note: Each time you click Generate PDF, a new version record is created in the app. Previous PDF versions are stored and accessible from Report → History — useful when a design has gone through multiple revisions and you need to show the audit trail of changes.

Clause References in the Report

Every equation and design check in the TankCode 650 report carries an explicit clause reference formatted as "API 650 14th Edition, § X.X.X". This is intentional — it allows a reviewer who has the standard in hand to locate the source of each formula without ambiguity.

For the shell thickness module, this means the one-foot method equation is cited as §5.6.3.1, the hydrostatic test as §5.6.1.2, and the corrosion allowance as §7.3.2. For seismic, each Appendix E equation carries its equation number (e.g., E-1, E-6, E-14).

Stamping and Certification

TankCode 650 generates the calculation document, but the professional engineer's stamp must be applied separately by the responsible designer. The cover page includes a dedicated Approved by field and a blank signature/stamp area formatted to A4 and US Letter standards.

Most reviewers and clients accept the TankCode 650 PDF as the primary calculation document, supplemented by the engineer's stamp on the cover page. If your jurisdiction or client requires calculations in a specific format or template, contact us — custom report templates are available on the Enterprise plan.

For API 650 App. V (external pressure) users: The external pressure section uses the hourly mean wind speed and buckling check equations from API 650 Appendix V. Make sure the wind speed input matches the design basis wind speed at the project site, not the 3-second gust value used in the seismic module. The two wind inputs serve different purposes and are entered separately.

Report Quality Tips

  • Run all modules before generating — a report with gaps looks incomplete to reviewers even if the missing modules are not applicable
  • For non-applicable modules (e.g., seismic in a low-hazard zone), add a one-line note in the module notes field: "Not applicable — Ss < 0.15g per ASCE 7-16 Figure 22-1." This appears in the report and closes the question for reviewers
  • Set the revision to "IFR" (Issued For Review) for first submissions and "AFC" (Approved For Construction) for the final issued revision — this is standard EPC practice
  • The design basis (liquid SG, fill height, design temperature, corrosion allowance) appears in the geometry summary. Double-check these against the data sheet before distributing

Generate Your First Report

Request access to TankCode 650 and export a complete API 650 calculation package in minutes.

Request Access