Skip to guide content

Subsea FAT Qualification — Multi-Hold Campaigns

FAT — comparison sessions & PDF packs

How to run a subsea tree FAT or qualification campaign in one browser session—multi-file import, per-test windows, and PDF export options for test-pack evidence.

9 min readEngineer · Technician · Witness / QA

Procedure first

API 17D defines factory acceptance testing requirements for subsea production systems. PressureTrend does not run a full FAT sequence manager, witness workflow, or certificate generator.

Your qualification procedure lists each hold, acceptance criteria, and required evidence. Use this guide to organise logger exports and PDF reports after each hold—or batch several holds in one session when your procedure allows.

Who this is for

  • Test-house and OEM engineers running subsea tree or SURF component qualification campaigns.
  • QA teams comparing several sequential hydrostatic holds from Crystal nVision or Keller loggers.
  • Contractors building operator FAT packs with chart evidence and pass/fail for each hold.

Typical qualification pattern

FAT and qualification campaigns often include many sequential holds at different pressures or on different ports—body tests, seat tests, and functional steps with recorded pressure traces for each.

Each hold produces a logger export. PressureTrend treats each export as one test in a comparison session (up to 10 files per session), with its own window, criteria, and report fields.

  • Import holds in procedure order when possible—use the test switcher in the header to move between tests.
  • Keep procedure codes and component descriptions consistent in report fields for traceability.
  • Use session defaults or template export to reuse report text across similar holds in the same campaign.

Multi-file import

Drop several CSV or Excel files at once, or add tests with the import control in the header. Keller and Crystal layouts are auto-detected per file.

Each test retains independent settings: test window, criteria %, checkpoint count, and report metadata. Switching tests does not overwrite another test’s window.

Per-hold analysis

  • Set the hold window on each test before sign-off—qualification holds vary in duration and stabilization time.
  • Apply the criteria % from your FAT procedure (including API 16C-style dual limits where applicable—see the API 16C hold criteria guide).
  • Review delta checkpoints when the procedure requires proof that drop did not accelerate during the hold.
  • Fill gauge serial, cal due, and component identification fields from each logger export or procedure sheet.

PDF export for FAT packs

When more than one test is loaded, the PDF menu offers export for the active test only, separate PDFs for every test, or one combined PDF. Choose the option your operator test pack expects.

Suggested filenames include date, procedure, description, pressure, duration, and criteria—useful when archiving dozens of holds from one campaign. Optional PDF with data points adds tabular appendix evidence for auditors.

  • Active test only: one chart and report per PDF—typical when each hold is a separate record in the FAT pack.
  • Separate PDFs per test: batch export after reviewing all holds in the session.
  • Combined PDF: single document with multiple tests—confirm with your QA process before using.

Compared with spreadsheet workflows

Excel campaigns suffer from version drift, inconsistent chart scales, and manual drop formulas across many files. PressureTrend keeps pass/fail logic and chart capture consistent while still parsing everything in the browser.

See the Excel comparison guide for a fuller trade-off; for single-hold WHST work, see the WHST workflow guide.

Privacy

Qualification files stay in your browser for analysis. Export project JSON to move a full session to another machine; pair session templates with the same source files when sharing settings only.

Related guides