Configuration Management
Configuration Management within Sage EMS stores market configuration data sourced from MSATS and meter configuration data sourced from MDFF and/or internal meter reading systems.
It is assumed that configuration data sourced from MSATS is sourced from an existing MSATS replica database, as most existing participants already have a well integrated MSATS replica database available. However, for participants without an adequate MSATS replica, the optional MSATS Local DBOR component provides a full MSATS replica service for both Sage EMS and external systems.
Configuration data is used to determine:
- NMI Relationships
- For retailers: Won, Lost, Retained, Wholesale, Non-Registered
- For Integrated LNSPs: Tier 1, Tier 2
- For all LNSPs: FRMP
- NMI Status
- Active, Energised
- Inactive, De-Energised
- Extinct, Greenfields
- Data Stream Status
- Active
- Inactive
- Inconsistent (between MDFF and Market).
- Meter Status
- Connected, Removed
- Active, Inactive
- Register Status
- Connected, Removed
- Billable / Non Billable
- Tariff
Extensive reconciliation between MSATS and MDFF supplied configuration is supported to identify issues that need to be resolved by the MDP and or MPB/MPC via the RP. Reporting identifies discrepancies, and reports are available in a format for provision to internal departments or third parties.
This component provides a full MSATS local replica, and acts as the database of record for MSATS configuration data.
It replicates MSATS configuration data by processing CR records, and provides full support for C1, C4 and snapshot extracts to provide for both initial population and ongoing maintenance. The following features are included:
- MSATS Snapshot support allows initial configuration data to be loaded via a NEMMCO provided snapshot report.
- CATS Change Requests are processed, and used to update the internal MSATS standing data replica.
- Discrepancies detected between the internal replica and external indicators of MSATS configuration are used to self-heal the internal replica. For example:
- A NMI referred to in a NEMMCO Settlement may appear with a different TNI compared to internal standing data. In this case, a C4 report request will be automatically issued to determine if a change has occurred in MSATS that has not been propagated via Change Requests, and based on the result of the C4 request, internal standing data will be updated.
- Invoice details NMI contained in a NUoS invoice may indicate that the NSP issuing the invoice is using a different set of standing data compared to that available in the local MSATS replica. Based on the results of an automatically issued C4 request, the invoice line item can either be paid automatically, or disputed automatically.
- Changes resulting from the receipt of C1, C4 and CR data can be propagated to downstream systems based on their requirements and interface contracts.
This component adds the following capabilities to Configuration Management:
- Importing meter configuration from asset management systems.
- CATS Change Request generation for meter configuration changes.
- CATS Change Request generation for standing data changes – such as ADL.