Understanding what coding complete means, when it can be overridden and what the risks are.
PM8 performs automatic tracking of a system status, and when any number of a range of events occur (e.g. add key, add door, change keying, etc) then the system is flagged to indicate that coding is required.
Then, before a job may be manufactured, you must open the coding window, perform any coding tasks required and then perform successful Calculate coding and errors.
Many systems imported from legacy applications, and often large historically paper-based systems, will have errors. When systems are imported into PM8 from legacy applications, they are flagged internally to indicate that horrendous errors may exist and to allow such errors to be ignored, then PM8 provides the facility to flag the system as being OK despite these errors.
Systems that are created in PM8 are not flagged as needing operator override on 'Coding complete', so the menu option Mark system as coding complete is not available for them.
This is not a once-only process. Each time you make a system change that PM8 knows will affect coding integrity, it flags the system as coding not complete, and even though you want to override this, you must still enter the coding window, perform Calculate coding and errors (which may not be successful). Then, to accept the system errors and enable the manufacturing processes, you must then follow this process.
Coding menu, choose Mark system as coding complete.OK.During coding calculation, the coding for each door is calculated.
Checks are performed to:
If the system has a few phantoms, and these are expected because of the coding such as a common entry with many keys operating the door where you have replaced keys that still will operate the door, the best thing to do is accept that these phantoms cannot be avoided and assign the phantoming key to the door.
If a phantom it unavoidable, it a much better to accept that opening by assigning the key to the door. This will eliminate the key as a phantom, and it will no longer stop the system achieving 'coding complete'.
In the situation where there are many phantoms and you do not want to assign the phantoming keys to the doors, then you might use the coding complete override. Be aware of the risks outlined below.
When coding is finished but has problems, either coding problems or phantoms, the system is in an unfinished state.
If you are confident that the door calculations are OK, and the only problem is the phantoming keys and you are happy with this, then sure use the coding complete override.
However, if there are other problems that have stopped the coding from finishing successfully, and you then use the coding complete override, you run the risk that you begin manufacturing a system that has critical errors (e.g. the keyway for a door could not be calculated, so calculations stopped and the result is that door and any subsequent doors have not been calculated correctly).
Overriding coding complete flags the system as complete, regardless of the reason why coding was not completed automatically.
When using the coding complete override, you take on the risk of system errors.
If there are just a few phantoms and you cannot resolve them, it is always better to assign each phantoming key to the door. You may wish to record a note in the
Design notesexplaining what the phantoms were (Each door/key combination) and why you could not resolve the coding problem.