We had a phenomenon occur in our DeltaV Operate Configuration Library back in January.
We did a ‘quick fix’ to address the immediate problem, but we have not found the root cause to close our deviation associated with it, and thus have not had any luck finding a solution to prevent it.
Below is the rundown of what happened.
On 01/18/23, during the implementation of ITCC2-22-018, when integrating the custom dynamo into the display, it was observed that the dynamo did not prompt a module allocation [Dynamo Properties window did not appear for module selection].
Upon further investigation, the same error was identified pertaining to other custom dynamos implemented into displays.
Section II. Root Cause Analysis
Why were there an absence of prompts during the implementation of the dynamo for assignment of the module to the dynamo?
These dynamos were previously set up and qualified as part of ITCC2-22-012 (October 2022), with the IQ-Graphics and OQ-Class (which included a step in which the dynamos assignment to a module was performed) protocols performed successfully.
If the dynamo was IQ and OQ’d successfully, why were the prompts to assign a module to the dynamo not present?
When investigating the dynamo structure within the CILdynamo dynamo set within the DeltaV Operate Configure library, it was observed that the order (hierarchy) of the dynamo components [“frsDynamoInfo…”, the dynamo subgroup(s), and the “ps_DataSource…”] was not in the same order for the deviant dynamos when compared to the working dynamos.
Additionally, the option to view the “Custom…” configuration associated with the highest level of the dynamo hierarchy was not available for the deviant dynamos as it is for the working dynamos (which when selected opens the “Dynamo Properties” window associated with the module selection).
When investigating the dynamos further, the VBA script of the dynamo (associated with the opening of the “Dynamo Properties” window) was found to be missing when compared to the working dynamos.
Background
Version Control/Audit Trail (VCAT) is not enabled within the DeltaV Operate Configure software, so no evidence is available to review the dynamo library between October and the erroneous current state
Why are abnormalities being observed between the working and deviant dynamos?
No one knows… potential corrupt dynamo set ???
Root Cause: … [HELP]
On a related subject, I reached out and put in a global ticket to Emerson for multiple issues we were seeing
If anyone has any insight I would appreciate it :)
Andre Dicaire
I am tempted to suggest if you have a backup of those dynamos, however this is a validated system that there is a bigger process before something is to be changed/restored in the configuration. You may want to get help from the graphic configuration supplier if you can still contact them. In case the supplier can no longer be reached, you may want to contact another company that does DeltaV configuration work on validated systems. This company may offer a complete package and they can resolve the graphics issue and handle the necessary documentations and process needed to comply with regulations. In this forum we can provide technical advices but configuration issues on validated and regulated systems is different since additional tasks is required like proper documentations and tracking.