Subscribe
Commissioning

Reading a Functional Performance Test Script

A test script is a recipe for proving a system works, and once you know its parts it is easy to follow.

Key takeaways

  • Every step in a script has an action, an expected result and a recorded outcome.
  • Pass and fail criteria should be clear before testing starts, not argued afterward.
  • The best scripts test normal operation and the ways a system is meant to fail safely.

A functional performance test, often called an FPT, checks that a system does what the design says it should. The test is written down as a script. Scripts can look dense at first, but they follow a simple pattern, and reading one is a useful skill whether you own the building or build it.

The parts of a script

Most scripts share the same layout. Names vary by team, but you will usually find:

  • Purpose. What system is being tested and why.
  • Prerequisites. What must be true before starting, such as completed installation checks, calibrated instruments and the right people present.
  • Safety notes. Hazards, lockout steps and who may operate equipment.
  • Steps. The numbered actions to perform, in order.
  • Expected result. What should happen after each step.
  • Actual result and sign off. What did happen, and who witnessed it.

Reading a single step

Take a step such as: simulate loss of utility power and observe the backup response. A good script states the action, then lists what to watch. For example, the generator should start, the transfer should complete within a stated time, and critical loads should stay energized. Each of those is a point that can be checked, which is what makes the step measurable.

Pass and fail criteria

Criteria come from the design documents, equipment ratings and the owner's requirements. Good criteria are specific. A phrase like "works properly" is hard to judge. A phrase like "supply temperature holds within the stated range for the stated time" can be recorded as yes or no. Teams usually agree on criteria in advance so that no one has to debate them in the middle of a test.

What happens on a failure

A failed step is not a disaster. It is the reason testing exists. The usual path is to record exactly what happened, stop if there is any risk, find the cause, correct it and repeat the step. The script should say whether a repeat covers only that step or a wider section. Deviations from the plan should be written down, not remembered.

What to look for as a reader

  1. Are the steps in a logical order, from simple operation to stress and failure cases?
  2. Is every expected result measurable, with units and tolerances?
  3. Does the script test alarms and controls, not only the equipment?
  4. Does it include returning the system to normal at the end?
  5. Are the witnesses and approvers named by role?

Questions for the project team

  • Who wrote the script, and who reviewed it for the owner?
  • How were the pass and fail criteria chosen?
  • What happens to the schedule if a key step fails?
  • How will results be stored so operators can find them later?

The finished, signed script is more than paperwork. It is a record of how the system behaved on day one, and it gives operators a baseline to compare against for years to come.

Found this useful? Pass it on.

This article is general information for public education. It is not legal, tax, financial or engineering advice. Rules and conditions differ by location, so check with qualified local professionals. Spot an error? Write to info@datacenteroutreach.com and we will correct it.

Have news, a project or a question?Send a press release, your company details, a data center project or a question. We read everything.
Send it in