During maintenance cycles, the sign controllers often return to service with incorrect settings for default font, default colors, stored graphics, stored messages, etc. The operations team is not notified of the controller returning to service - thus, the attempt is made to use the sign before it is properly configured. Efforts are underway to add a macro to the NTCIP Investigator to detect and correct these configuration issues. However, the Investigator is a manual tool that is deployed after the attempt to use the sign with bad configuration - a better solution would be a routine that automatically detects the sign coming back into service, checks and corrects the configuration before the sign is used.
Discussion on this has steered towards checking a few key values once comms are re-established with a sign to give an indication if configuration activities need to be performed. Email notification via NG_Delivery when configuration needs to be performed.
PaulTMS
commented
2 years ago
During maintenance cycles, the sign controllers often return to service with incorrect settings for default font, default colors, stored graphics, stored messages, etc. The operations team is not notified of the controller returning to service - thus, the attempt is made to use the sign before it is properly configured. Efforts are underway to add a macro to the NTCIP Investigator to detect and correct these configuration issues. However, the Investigator is a manual tool that is deployed after the attempt to use the sign with bad configuration - a better solution would be a routine that automatically detects the sign coming back into service, checks and corrects the configuration before the sign is used.
Discussion on this has steered towards checking a few key values once comms are re-established with a sign to give an indication if configuration activities need to be performed. Email notification via NG_Delivery when configuration needs to be performed.