- Home
- :
- All Communities
- :
- Products
- :
- ArcGIS Utility Network
- :
- ArcGIS Utility Network Ideas
- :
- Make Update Subnetwork smarter about dirty areas i...
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Follow this Idea
- Printer Friendly Page
- Report Inappropriate Content
Make Update Subnetwork smarter about dirty areas it encounters
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When a subnetwork fails to update due to inconsistent subnetwork names, a dirty area is placed on each subnetwork controller device. This impedes the ability for other subnetworks to update, even if they are perfectly fine themselves, simply due to order of operations.
Example A: an gas isolation subnetwork fails and all the valves are marked with dirty areas. A cathodic trace (in a different tier group) now fails because it cannot trace through that valve, even though it doesn't affect anything in the cathodic network.
Example B: a gas isolation subnetwork fails and all the valves are marked with dirty areas. It is adjacent to two different subnetworks. One is involved in the failure. But on a different side there is a subnetwork that is defined accurately. It would be updated if the first subnetwork hadn't attempted its update first. Changes in this accurately defined subnetwork are not propagated due to the problems with the adjacent subnetwork.
Idea: allow a subnetwork to attempt to update if it encounters a dirty area of status 32 (subnetwork error)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.