Attach an I/O schedule to your multi-pump control panel RFQ. Give each signal a name, direction relative to the panel, source, destination and expected behavior on signal loss.
Separate pump points from shared signals
Start with one row for each function. Repeat command, status and fault points for each pump. List shared pressure and low-level inputs once per physical sensor. Identify whether every point is wired, on a network, or available by both paths.
Example schedule for a duty/standby pair
| Point | What to specify in the RFQ |
|---|---|
| P1/P2 run request | Origin of each request and which controller has command authority in each operating mode. |
| P1/P2 running and fault feedback | Separate status and fault points, with display text and the agreed response to lost communication. |
| Discharge pressure | Sensor type, pressure range and units, signal scaling and response to invalid feedback. |
| Low-water permissive | Input source, normal state, agreed behavior on loss and authority for restart. |
| Plant alarm / BMS link | Alarm groups, equipment identification, protocol and who delivers and tests the point list. |
Agree how the points will be tested
Ask the panel integrator for the revised I/O list, terminal or network reference, and the responsibility for factory and site tests. Include an acceptance check for failed pressure feedback and a duty pump fault. Have the responsible engineer approve the expected behavior and applicable safety functions.
