Commissioning Test Manager — FAT / SAT Point-to-Point

Turn a signal list into point-to-point test steps for the FAT or SAT, record each result as you test, attach evidence from an IEC 104 capture, follow progress per device, and print the report with the punch list and sign-off — in the browser, kept on this computer.

Point-to-point testing proves every signal from the device to the control centre: hundreds of points, each with several states, tested by different people over days. Spreadsheets lose track of what was tested, by whom and how; the punch list and the evidence are rebuilt at the end. A structured test list with the expected result for every step, filled in as you go, makes the FAT/SAT traceable and the report immediate.

Standards followed

IEC 61850-10 and IEC 61850-4 (testing and quality assurance in the engineering process)IEC 62381 (FAT, FIT and SAT for process automation systems)IEC 60870-5-104 (point addressing for the evidence check)

What it can do

Reads a signal list (CSV): the Gateway Mapping Builder export, an IEC 104 point list, or any list with tag, description, type, CA/IOA, unit and range columns.
Creates test steps by signal kind: single points (ON, OFF, invalid), double points (closed, open, intermediate/bad), analog values (injection at 0/50/100 % of range, limits, invalid), counters, commands (select/execute both ways, blocked by interlocking or local mode) and set points.
Records result, observed value, remark, tester and date per step; filters open and failed steps; progress per device.
Links evidence from an IEC 104 capture (values and confirmations seen for each CA/IOA), lists points not seen and points in the capture missing from the list; prints the report with punch list and sign-off; exports CSV; saves and opens the test file.

Example problem

The GW1 IEC 104 signal list of the S13 sample (11 points) and the sample IEC 104 capture as evidence.

33 test steps are created for the FAT.
Linking the capture finds 10 of the 11 points with values (e.g. IOA 2001 seen ON (10)); Q01_Q (IOA 3004) was never sent.
IOA 5099 appears in the capture but is not in the list — the control centre sent a command to an address the gateway does not have.

A traceable FAT record with evidence, an open item for IOA 3004 and a question for the control centre about IOA 5099.

Evidence from a capture shows that a value was transmitted; the tester still confirms that the right value appeared at the right place. The test file is stored in this browser — save it regularly and keep it with the project records.

Test project

Project

Stage

Tester (filled into each result)

Open signal list (CSV)…Open saved test file…

Result

Open a signal list or load the sample to create the test steps.

Tool guide · know before you use

What this tool is, how it works and how far to trust it

A point-to-point test manager for FAT and SAT: it turns a signal list into test steps with expected results, records the outcome of every step and prints the report with punch list, evidence and sign-off.

Read this before relying on a result. Every method, formula, assumption and limit is stated here, so you can check the answer yourself instead of accepting it blindly.

What it can do

Read a signal list CSV (tag, description, type or IEC 104 type id, CA, IOA, unit, engineering range) — the Gateway Mapping Builder export works directly.
Create the steps for each kind of signal: single point ON / OFF / invalid; double point closed / open / intermediate; analog injections at 0, 50 and 100 % of range, limits and invalid; counters; commands select-execute both ways and blocked by interlocking or local mode; set points.
Record pass, fail or not applicable with the observed value, a remark, the tester and the date; filter open and failed steps; show progress per device.
Link evidence from an IEC 104 capture: values and confirmations seen per CA/IOA, points never seen, and addresses in the capture that are not in the list.
Print the test report with punch list and signatures, export the results as CSV, and save / reopen the test file so testing can continue another day.

Why you need it

A substation has hundreds of points with several states each, tested by different people over days; spreadsheets lose track of what was really tested and how.
The punch list and the evidence are usually rebuilt at the end; recording them step by step makes the FAT/SAT traceable and the report immediate.

Understand this first

Point-to-point means end to end: the state is created at the source (the breaker, the relay input, an injection) and checked at the far end (gateway, control centre), so every link in between is proved at once.
Each signal kind has its own states to prove: a double point needs both positions and the intermediate/bad state; an analog needs the scaling at several points of the range, not only one value.
Commands are proved in both directions and also where they must be refused — interlocking, local/remote, select-before-operate timeouts.
A capture is evidence that a value really travelled on the link with the right address; it does not replace the observation at the HMI or control centre.

What you need before you start

The signal list of the device or gateway (CSV), with the IEC 104 addresses if a capture will be used as evidence.
Optionally a capture (.pcap / .pcapng) of the IEC 104 link taken during the test.
Work is kept in this browser's storage; save the test file to keep or share it.
A current browser (Chrome, Edge, Firefox or Safari). Nothing is installed and your data is never uploaded; it is processed on your own computer.

How to use it

Open the signal list (or load the sample) and enter the project, device and test stage.
Work through the steps: create the state at the source, read the far end, set the result and the observed value.
Optionally open the capture taken during the test to link evidence and see points not seen.
Save the test file at the end of the day; print the report when the stage is complete.

What you get

Test steps per point with expected result, outcome, observed value, remark, tester and date.
Progress per device, the punch list of failed and open steps, the evidence table, the printed report and a CSV of the results.

How to read the results

A point not seen in the capture: it was not tested during the capture, or the source never sent it — check the mapping and the spontaneous transmission setting.
An address in the capture that is not in the list: the control centre or gateway use a different list revision — resolve before sign-off.
A failed analog at 0 % or 100 % but correct at 50 %: scaling offset or range wrong, not the wiring.
A command executed while it should be blocked: interlocking or local/remote logic error — a safety item, never a minor punch.

Technical basis

IEC 62381 (FAT, FIT, SAT), IEC 61850-4 and -10 (engineering process and testing).
IEC 60870-5-104 type identifications, causes of transmission and addressing for the evidence check.

Limits: when not to rely on it

The tool records the test; it does not create the signals — a test set, simulator or the plant does.
Evidence is read from IEC 104 captures only; for other protocols record the observation manually.
Browser storage can be cleared by the browser: save the test file regularly.

Sample files for this tool

Download, open and compare with what the guide says you should see.

S13_IEC104_gateway_capture.pcap — IEC 104 link between control centre and gateway — capture with faults
S13_GW1_IEC104_signal_list.csv — GW1 IEC 104 signal list — for point-to-point testing

All sample files and what to expect →

For preliminary engineering use. Results must be checked by a qualified engineer against the project's standards. How results are checked · Terms & disclaimer · Privacy · Build 7cfcbe2 · 2026-11-14