10 hours ago, al-yeti said:

You lock them yes?

Im thinking I should 

1 hour ago, PeterJames said:

Im thinking I should 

Wow your joker , you install lots compared to me I lock every single one and tell everyone I do it 

On 03/03/2020 at 23:26, james.wilson said:

Ideally it should be unique per site pod helps but is undone by clock resets etc

James, this is the setup we have and I was actually wanting to change it to one code. I guess it’s way more secure overall but it’s a bit of a pain for call outs etc. Having said that we have an easy system to remember, same 4 digits then the first two numbers of the address. My issue was that when you changed all the codes it becomes almost unmanageable. 

If the seed to make the engineer code is that easy then I wouldn't say it's worth the effort.

It's a little bit better to stop someone reading it off the panel to learn all your codes (possible but unlikely) but beyond that it's too easy to share the seed info which ideally shouldn't be known.

Unique generator based on account number and contract number is what I use. We can have 20 mixed systems on a single site, all have different engineer codes.  Far more secure this way, it’s rare but if and when a customer wants to leave for whatever reason, we issue the code on written request and if accounts are paid up as it’s no good on any other site

Edited March 6, 20206 yr by PSE

4 minutes ago, PSE said:

Unique generator based on account number and contract number is what I use. We can have 20 mixed systems on a single site, all have different engineer codes.  Far more secure this way, it’s rare but if and when a customer wants to leave for whatever reason, we issue the code on written request and if accounts are paid up as it’s no good on any other site

Agreed your right

8 hours ago, PSE said:

Unique generator based on account number and contract number is what I use. We can have 20 mixed systems on a single site, all have different engineer codes.  Far more secure this way, it’s rare but if and when a customer wants to leave for whatever reason, we issue the code on written request and if accounts are paid up as it’s no good on any other site

So how would the engineer know each code? Some kind of app that he has to enter the account and contract number?

That's the idea. The seed wouldn't be known and if the engineer left the company they wouldn't have access to it.

Agreed. I have an app that does this, custom seed based on contract number. App needs authority to load etc so fully controlled. Also can only do 3 codes an hour

Apps are fairly easy to overcome though, so you're relying on your employees at the end of the day.