Locked NVM

[frenchman]

Hi chaps, just wondering what are your views on locking panel ? I can't really see any reasons other than making the next installer's life difficult. I have had the case recently when the panel had to be replaced but the client was never consulted or told about it. Anyone know what the regs are ?

[PeterJames]

There are no rules on NVM locking its down to personal preference.

[al-yeti]

42 minutes ago, frenchman said:

Hi chaps, just wondering what are your views on locking panel ? I can't really see any reasons other than making the next installer's life difficult. I have had the case recently when the panel had to be replaced but the client was never consulted or told about it. Anyone know what the regs are ?

I lock every panel since I moved to hkc and every higher end texecom I find is also locked 

 

It's all good best way 

Also happy to release to an installer 

[james.wilson]

Its better to lock to protect the company and insurer etc. Plus the programming belongs to the maintainer.

eg SIA lock all but do default on request. If the ex client doesnt want to pay for the default, boards are defaulted foc at the office.

Issues with gear is how they are programmed, passwords used in onvif, how systems are setup etc. Plus incoming company should always default to know it is programmed to their requirements with the client that may have changed. Had a conversation recently regarding this and there is the potential for liability issues for the outgoing company 'if' the incoming company can prove they didnt change xyz option.

Always better to default on leaving and incoming

[MrHappy]

14 hours ago, frenchman said:

Anyone know what the regs are ?

 

there ain't none, however there are a set of big boys rules....

 

when taking other peoples tat over you either have to the product knowledge of how to over come any lock or quirks of the product 

 or have enough £ in the job to put your own stuff in from either the start or retain the subscriber for enough years to make it pay..

 

confiture demain, as you might say ?

 

Sadly a few hundred quid for new control can be a problem as the subscribers can be living had to month with the latest I-Phones, Range Rovers & shirt sponsoring the local professional sports team... taking priority 

Edited August 4, 2021 by MrHappy

[PeterJames]

20 hours ago, MrHappy said:

or have enough £ in the job to put your own stuff in from either the start or retain the subscriber for enough years to make it pay..

If you have neither then its probably not worth taking over

[MrHappy]

16 hours ago, PeterJames said:

If you have neither then its probably not worth taking over

 

I believe the VAT man makes a better profit than I & he's doesn't even foot the ladders 

[frenchman]

Surely the panel belongs to the client so you would need his approval to potentially refrain him from using it as he wishes ?

[al-yeti]

1 hour ago, frenchman said:

Surely the panel belongs to the client so you would need his approval to potentially refrain him from using it as he wishes ?

So what about your 

 

Smart TV

Car

Washing machine

 

The list can go on , and sure you can get sometimes odd password turn up on internet but your talking about a"security" device 

 

Simply put if the sub wants the eng code then he should know that you hold no responsibility for the system and nothing is warranteed you would have to be crazy to do it 

 

If they already have code it's difficult to take it from them, but if you have contract of service to provide them , I wonder does it comply when you have a contract that sub has access to main settings?

 

Alarm monkeys? Does it matter to your efficacy insurance that you allow the sub to keep the engineer code ?  Or I am looking at it the wrong way ?

[james.wilson]

1 hour ago, al-yeti said:

Alarm monkeys? Does it matter to your efficacy insurance that you allow the sub to keep the engineer code ?

your not covered

 

Also a panel can be defaulted etc when its got a support contract on it, reprogrammed and the maintainer has all the liability without any control of how its programmed.

I do agree that systems (all programmable devices) should be defaulted on maintainer change. As above this can be foc or a site visit. I suppose its similar with locked phones.

 

An installer has invested in training, support and even how to make x work with y. That information and knowledge belongs to that person/company. The bit of kit belongs to whoever bought it and can be used how they see fit.

 

A lot of equipment now also has other passwords, security questions etc stored in it, remote codes all sorts. All this needs defaulting once the maintainer has lost control of it.