Select to view content in your preferred language

Need ideas: Selectively triggering ADMS integration for "significant" network changes

75
0
Thursday
rpepato_bizpoke
Occasional Contributor

Hi team,

We have a customer (electric domain) who is planning to use ExportSubnetwork to feed their ADMS, and they've raised a good point about integration frequency.

The customer is using a single-tier configuration, with feeders extending from the breaker terminal to the service delivery points.

They understand that a subnetwork gets marked as 'Dirty' (requiring validation) after topology validation, even for minor changes (like connecting a single service point). However, they only want the ADMS to be synchronized after major network changes or a batch of minor changes (e.g., every 5 new LV residential customers). They specifically do not want to feed the ADMS for every minor edit.

Since the "Dirty" status is automatically triggered, and that is basically the initial condition of "something has changed - we need to clean the subnetwork and inform ADMS about the change", I'm wondering if there's a way to add a custom trigger/condition for the process of marking the network as Dirty without major development/customization work.

Does anyone have experience or ideas on how to handle this export request conditionally?

Thanks for your insights!

0 Kudos
0 Replies