It's too slow, not workable. When the number of items and the number of instances is increasing the performance is not what you would expected.
Guest
|
Idea business value
An equipment update can take up to several hours. Compared to customized tooling this is way too long. For instance a (Dutch) tunnel can have up to 50 different equipment types. Number of items varies between a dozen and a few hundred. The number of instances depends on the length of the tunnel and the number of tubes. Can be a several hundreds of instances. |
|
| Idea priority | 5 – Critical to my company |
Hi All. This has now been corrected and fixed with significant speed improvements in Plant SCADA 2023 July Update 7. This is looking to be backported into the PS2020 line in a future service pack. It will also be included on the main branch for the PS2023R2 release.
I agree fully.
My understanding is that ODBC queries are being used to update the DBF records directly, to be able to respect manual adjustments that were made. This is the correct way, but it has a horrible performance rate.
Better would be to cache the dbf data in RAM first, perhaps even in a proprietary format. Then perform all the generation queries and write it back to disk as a dbf.
And if there have been no manual adjustments, just build a new file from scratch. This way a task that currently takes hours, can be done in seconds.
For a longer term solution: replace the dbf files with a fast configuration database.
it seems to me that a lot of the inefficiencty comes from the fact that it accomodates an incremental update so that any manual tweaks to the generated tags can be maintained. Personally I create my templates so that all customisations are kept in the templates themselves and so if tags etc were corrupted, they could be regenerated. Also it is thenpossible to see all relevant details for a piece of equipment in the eq editor rather than having to parse every single generated item an analyse its impact. So if this is the case, generation should be a much simpler proposition. If a project meets this criteria, then the generator should have an option to do a once through generation and this should be much quicker.
This has been reported to Tech Support as well, and currently under investigation and working towards a fix to this solution. More information coming soon on this topic.