Energy Select is experienced at setting up and maintaining Embedded Networks.
The principal characteristics of an embedded network include:
- consumers have a choice of retailer, subject to the necessary conveyance agreement in place between the energy trader and the embedded network owner; and
the network is not directly connected to the grid.
An embedded network exists when all of the following are true:
- all consumers, that are switchable, are allocated an ICP on the registry by the embedded network owner (or its agent), and these ICPs are managed in accordance with the Rules;
- the embedded network owner has had a Network Supply Point (NSP) created for the point of connection between that network and either:
- the parent network; or
- another embedded network. All ICPs on the embedded network refer to this NSP in the registry;
- the parent network owner has established loss factors for each of the NSPs connected to its network, and has included these with the loss category codes and loss factors published in the loss factor table on the registry;
- the parent network owner has had an ICP identifier created for the point of connection to the embedded network. This ICP is to have a price category code, and a loss category code that will represent the losses assigned by the parent network owner between the point of connection of the embedded network, and the parent NSP to that embedded network;
- there is a Rules compliant half-hour (HH) meter at the embedded network NSP;
- for the purposes of clearing and settlement, the embedded network owner (or its agent) has obtained the appropriate certification under the Rules for collection and submission of information to the reconciliation manager (RM) for the NSP half-hourly metered volumes in accordance with the Rules;
- the embedded network owner has established loss factors for ICPs within the embedded network, has published these in the loss factor table on the registry, and populated the loss category code against each ICP within the embedded network on the registry;
- any UML is managed within the registry (rule 13 of part E and rule 2.11 of schedule E1 of part E of the Rules);