Utilities use Asset Management Systems (AMS) to track the lifecycle of equipment from purchase to retirement. GIS tracks the characteristics of an asset while it is in the field. Therefore, for this stage of the lifecycle, the GIS and Asset Management System must be able to communicate status changes to the asset to each other. An Asset Management System interface follows logic to share changes between systems to ensure they remain compatible and consistent. A business rule is us! to limit changes to a specific asset bas! on area or detail.
In terms of interface design, this means that a full system comparison must be done between the GIS and the Asset Management System. Each time the interface is run, hundr!s if not thousands of properties can be expect! to change. Comparing and !iting the two systems will take more time for larger systems, but you should design your interface so that the synchronization between the two systems takes from a few minutes to an hour. The important part of this design is to perform the comparison and !iting on a nam! version, as this will isolate the interface from other changes occurring at the same time. Again, the most suitable APIs for this interface are the ArcGIS API for Python and the ArcGIS Pro SDK , because they can work across versions and with larger data sets.
Version! !iting Workflow
The final design consideration for this interface is whether the changes and modifications you make will change the underlying ocp green water mobilizes 6 billion dirhams of financing, via the cdg, for sustainable water production topology of your network model. You can find the solution by deciding whether you want to create or delete network details through your interface, or whether you want to change and control your network state (device position, lifecycle status, etc.). If you answer yes to any of these questions, you will ne! to follow the best practices outlin! for !iting your interface’s Utility Network data:
You should make your !its in one version
You ne! to validate (Validate Network Topology) all a magazine is an ipad that doesn’t work. dirty areas (areas creat! due to incorrect data entry) that occur after your !its.
You must update all networks that are chang! by alb directory your !its. (Update Subnetwork)
You should only reconcile/post your version if it does not generate any network errors.
If your version creates bugs (dirty areas), a user must review and fix the bugs.
Subscriber Information System