Test media must suit the detector: controlled heated air for heat detectors (radiant heat not recommended), a non-contaminating particulate for smoke detectors, a suitable gas for carbon monoxide detectors, and aerosols that do not foul aspirating pipes. Point heat detectors: yearly functional test of a representative 20% per circuit, including the last detector (or the one nearest the end-of-line device on collective circuits), so all are tested in five years; non-resettable types are proven by simulating an alarm at the end of line. Linear heat detectors: heat test at a random, changing location if resettable. Point smoke detectors: functional test in situ of at least 50% per circuit each year so all are covered in two years; sensitivity tested in situ with calibrated equipment after 10 years from installation and every five years after, or read yearly where the detector or CIE reports out-of-range sensitivity, failing which, at 10 years every smoke detector is swapped for a new one or one that has been cleaned and recalibrated. Beam detectors: yearly test with neutral density filters for alarm and near-opaque blockage for fault (60% direct, 30% reflected where no data). Aspirating detectors: smoke at the last sampling point of each pipe run with transport time no more than 10% or 5 s (the larger) away from the recorded value and not over 120 s, capillary sampling points 20% a year, and sensitivity verified after 10 years and every five years. Flame detectors: yearly function test and coverage check, sensitivity every five years from installation. Carbon monoxide detectors: 50% a year functionally and sensitivity within 25% of the listed range by the maker's interval and no later than 10 years from manufacture. Multi-sensor and combined detectors are tested by the type installed or each sensor as required. If a detector fails, at least 10 more on that circuit are tested, and a further failure means the whole circuit is tested; failed detectors and items past their service life are replaced.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.