Variations are 'bad', right...?

Well, that depends on a range of factors.

BS5839-1:2017 is a code of practice and includes recommendations rather than requirements. A variation, previously known as ‘deviation’ (but note this latter name should no longer be used), in simple terms details where a system does not follow these recommendations.

Commentary within BS5839-1:2017 also advises that strict adherence to the standards in some instances could lead to ‘unsuitable’ or even ‘inadequate’ systems for the level of protection required.

Every variation should be agreed with all interested parties (e.g., end user, purchaser, enforcing authority or insurer) and must be clearly identified in the project documentation. This means that the variation has been identified, discussed, agreed, and listed as a known item.

Let’s look at variations another way –

What are the chances that a large-scale, complex project with 100’s of detectors, manual call points, sounders and VAD’s will be totally compliant with all recommendations from all 184 pages of BS5839-1:2017 and therefore truly has no variations?

In generating a variation, we are proficiently demonstrating knowledge of the BS5839-1:2017 standard and its application. If the process is followed correctly, it could be argued that variations are a positive addition in achieving a compliant and fully functional system.

The only ‘bad’ variations are those not identified, discussed, agreed, and listed as a known item.

For more information, please visit www.def-online.co.uk.