OP
Cygnet
This is my first post on the forum so here goes! ..............................................................As it has already been said initial verification on new installations is 100% of every circuit. Periodic test and inspection is different in that it is more inspection than test. The testing scope can be influenced by the client operations and you need to get this agreed with them before you start under the limitations. You may have a situation where the client has a comms / Data room which cannot be switched off, so they may require a visual non-intrusive inspection and no testing. Flag this up on your certification. You may also have, on the day access issues to rooms etc, note these down as well under operational limitations. In most cases its what you havent done as opposed to what you have done that needs to be highlighted to the client on the paperwork. Buildings with test records I would aim to carry out a test on 20% of the final circuits, and compare readings if you find anomallies do a further 20%. I would also carry out an Insulation resistance of the whole DB Neutral to earth as a N-E fault is the most common to go undetected, you wont flag it up by doing a ELI test or even the plug in 'Martindale' tester. If you are unsure as to end user electronic equipment initially carry this out at a reduced voltage of 250V dc. Periodic testing you don't follow the same testing sequence.
If there are no test records, you need to tell the client from the outset that a full 100% test is recommended, again thay may not want you to do it, operation / cost etc so get it written down in your limitations. If they dont want it and are not going to pay for it then dont do it just cover your self on the documentation.
If there are no test records, you need to tell the client from the outset that a full 100% test is recommended, again thay may not want you to do it, operation / cost etc so get it written down in your limitations. If they dont want it and are not going to pay for it then dont do it just cover your self on the documentation.