Intermittent Supervisory Trouble After Heavy Rain
During an annual preventive maintenance visit, you find a repeating supervisory trouble on a detection loop that runs 250 m underground in conduit to a gatehouse. The trouble appears only after heavy rain, clears on reset, and has been logged 11 times in three months. The site's response each time has been to reset the panel and, twice, to disable the gatehouse portion of the loop overnight. A 500 V insulation test reads 1.2 MΩ to ground on one leg; the site's own commissioning specification calls for at least 1 MΩ, so the maintenance supervisor argues the reading is "in spec" and wants the loop disabled again until summer. The gatehouse is unoccupied at night but contains records storage.
1. Is the 1.2 MΩ reading sufficient grounds to accept the loop as healthy? Explain what the reading does and does not tell you.
Read the worked answer
- A passing insulation resistance figure shows the fault is not a hard short at the moment of testing, in dry conditions. It does not show the loop is healthy.
- The fault is moisture-driven and intermittent. Testing in dry weather measures the healthy state, not the failure state; 1.2 MΩ when dry may fall to well under the limit when water bridges the conductor.
- Insulation testing on a connected loop also has limits: devices and surge protection can influence the result, and a single point-to-point reading does not localise anything.
- The supervisor's "in spec" argument uses a threshold as a conclusion. The threshold matters, but the logged pattern of 11 weather-correlated events is the stronger evidence.
Conclusion: the loop is not healthy; it is intermittently faulty and the reading was taken at the wrong time.
2. Describe how you would isolate the fault and what you would refuse to do.
Read the worked answer
- Split the loop at the gatehouse to determine which side the fault is on, then halve again - a bisection approach on a loop is far faster than walking 250 m.
- Inspect the underground pull points and the conduit low point for standing water, damaged gaskets, or a missing drain; look for splice failures at the first point where the trouble appears.
- Re-test insulation while the fault is present - after rain, or with the suspect section wetted and isolated.
- Confirm the circuit is truly isolated and devices removed before insulation testing, so the test voltage does not reach electronics.
I would refuse to:
- Leave the loop disabled indefinitely as a workaround - that removes detection from the gatehouse without a controlled impairment.
- Raise the trouble threshold or mask the point to silence the log.
- Accept a dry-weather reading as closure of the fault.
3. The supervisor insists on disabling the gatehouse section again tonight. What is the correct handling?
Read the worked answer
- Treat it as a formal impairment, not a routine reset: written notice to the owner, the affected area, the start and expected end time, and the mitigation (e.g. temporary detection or a fire watch if the area is occupied or the risk warrants it).
- Notify the monitoring provider so they do not interpret the resulting signals as a fault or a real alarm.
- Record the repeated impairment history in the maintenance log - 11 events plus two overnight disables is a pattern that should escalate the repair priority, not normalise it.
- Set a defined repair date and record who accepted the risk.
Reasoning: the technical fix is straightforward once the water entry is found. The judgement issue is that repeated informal disabling quietly becomes a permanently unprotected building, and the paper trail is the only thing that stops it.