Validation route
Use ARServer as a transparent engineering layer
FAT and SAT workflows need evidence. A gateway is not useful if nobody can see source value, output value, timestamp, quality, and communication state. ARServer makes these checks visible before the mapping is trusted.
What to validate
- IED association and reconnect behavior.
- Selected IEC 61850 object paths and values.
- Quality, timestamp, stale state, and diagnostics.
- Modbus address mapping and HMI interpretation.
- MQTT topic route and payload shape.
Suggested FAT/SAT sequence
- Prepare the test network and relay/simulator.
- Load or discover the IED model.
- Select only agreed test points.
- Force or simulate state changes where safe.
- Confirm ARServer value, Modbus value, and MQTT payload.
- Record exceptions before expanding the test list.
Boundary: ARServer is not a protection injection test set. Use it as a visibility, mapping, and gateway validation tool around the data path.