wrong meter

Terrylw1

That's a reflection of the supplier your company is contracted to read for.

Its not the same with the ones I've had experience of. I've written processes for back office operations and managed teams that deal with these issues. It sometimes depends on systems though.

For example, if you take a read and mark it as a time switch fault, the read comes in and bills/enters consumption, etc. It should also pop out as a timeswitch investigation due to the data item marked as such due to what you inputted into the handheld. SAP systems are getting built to do this very thing but older systems may not have coped as well. Suppliers tend to rely on a specific data flow that flags a potentially faulty meter, the D0001. This flow means somethings wrong and will except out for investigation.

The D0001 covers faulty timeswitch, stopped meters, broken displays, blanks, accuracy issues, everything really.

So, I wonder if your Data Collector is sending them?

The suppliers should pick it up off your readings as well but to be honest, I can say that older ex regional systems were not built to do it, so its kind of a failure by the nationalised side to prepare for it. We've been battling this failure every since.

I know what you mean about seals. No one cares if the supplier reports it either. The only time they seem to care is when something is sent out about a persistent offender operating in the region i.e. dodgy developers, as they are interested in a prosecution and recovering costs.

utility_csa

Terry, it all depends if the mop is bothering to action the D1.

Also huge factor as you say is if the DC is even bothering to report the D1. We took over a major contract with a high profile customer and once we took over their meters we got hundreds of D1s in for flag alerts from our preferred DC. Guess the old DC must have just been removing the alerts from their data to make it appear clean and everything good.

Tighter auditing really needs to be put in place.

[Deleted User]

I work for just about the biggest, Brit Gas, and also EDF. They ve never taken notice of anything flagged up on the handheld fault codes I have asked management for a dedicated phone number for Brit Gas to no avail. I ve decided to just call customer services in my own time now as the only way to at least stop the blank screen fiasco. some customers have twigged if their electric is not being monitored ( they get an estimate ) they can let rip and heat with it, keeping the gas bill down. I ll be calling cust services today with my usual 3 or 4 blank screens per week. As for missing seals , not enough time in the day for a couple of hundred calls
you could be right about the handheld not sending all these faultsto them properly, or no ones checking at the other end.

Terrylw1

utility_csa wrote: »

Terry, it all depends if the mop is bothering to action the D1.

Also huge factor as you say is if the DC is even bothering to report the D1. We took over a major contract with a high profile customer and once we took over their meters we got hundreds of D1s in for flag alerts from our preferred DC. Guess the old DC must have just been removing the alerts from their data to make it appear clean and everything good.

Tighter auditing really needs to be put in place.

Totally agree with you.

I've noticed that some DC's don't send the D0001 to the supplier, they send it to the MOP where they are the same company/group. So, the supplier isn't even aware of the meter faults and if the MOP wants to cover it up, they can.

Tighter controls certainly needed, like with processes in general. Whilst Elexon are far better than Ofgem in terms of monitoring...they focus on big issues which leaves all these problems out there with people acting any way they want.

Terrylw1

sacsquacco wrote: »

I work for just about the biggest, Brit Gas, and also EDF. They ve never taken notice of anything flagged up on the handheld fault codes I have asked management for a dedicated phone number for Brit Gas to no avail. I ve decided to just call customer services in my own time now as the only way to at least stop the blank screen fiasco. some customers have twigged if their electric is not being monitored ( they get an estimate ) they can let rip and heat with it, keeping the gas bill down. I ll be calling cust services today with my usual 3 or 4 blank screens per week. As for missing seals , not enough time in the day for a couple of hundred calls
you could be right about the handheld not sending all these faultsto them properly, or no ones checking at the other end.

Then they are in breach of BSCP514 6.4.1 Investigate Inconsistencies.

If you punch that into Google, you will get the links to them.

I know that handheld software has been a problem with readers regarding energisation and some other codes. I recall in one situation, a stripped down list of codes had been added.

The codes are under Meter Reading Reason Code (MRRC) and Site Visit Check Code (SVCC) in the D0010 data flow that the Data Collector sends out. Click on them in the Data Items section to be taken to the list you should be able to flag up.

http://dtc.mrasco.com/DataFlow.aspx?FlowCounter=0010&FlowVers=1&searchMockFlows=False

Bgas's Elexon Operational Support Manager (OSM) is here.

http://www.elexon.co.uk/bsc-related-documents/bsc-signatories-qualified-persons/?signatory_id=b

EDF's is here.

http://www.elexon.co.uk/bsc-related-documents/bsc-signatories-qualified-persons/?signatory_id=e

The OSM's are Elexon account manager/compliance manager for the party. Other Elexon's members also contact/visit the party but the OSM is involved.

There is an official Whistleblowers policy that Ofgem operate as well.

You may also be interested to know that every year there is an external independent audit commissioned by Elexon but usually actioned by PriceWaterhouseCoopers. Part of tgis audit normal has a key data flows section which could include the D0001. I know it was 2 years ago.

[Deleted User]

Have emailed Ofgem about the minimum inspection period on prepays being disregarded and surprisingly got a reply asking me for permission to publish " in the public domain " .,not sure what they meant by that, but as an example, late this afternoon got into a terraced house with a brand new occupier (young lady with child ) to find the electric prepay meter bypassed, will find out later how long thats been going off..This sort of thing will be happening all over the country in certain areas.Thanks for that info

utility_csa

Terrylw1 wrote: »

Totally agree with you.

I've noticed that some DC's don't send the D0001 to the supplier, they send it to the MOP where they are the same company/group. So, the supplier isn't even aware of the meter faults and if the MOP wants to cover it up, they can.

Tighter controls certainly needed, like with processes in general. Whilst Elexon are far better than Ofgem in terms of monitoring...they focus on big issues which leaves all these problems out there with people acting any way they want.

Hmm, i wasn't even aware the D1 needed to be reported to the Supplier as well. I do know if their is an issue reading the meter a D4 should be sent to supplier once every billing period to push the supplier into making the Mop attend site.

Also sending it to supplier and mop who are within the same company is useless how many mops and suppliers use the same MPID but are completely different companies.

Have you ever seen how the D1s work on half hourly? almost perfect that way.

Terrylw1

utility_csa wrote: »

Hmm, i wasn't even aware the D1 needed to be reported to the Supplier as well. I do know if their is an issue reading the meter a D4 should be sent to supplier once every billing period to push the supplier into making the Mop attend site.

Also sending it to supplier and mop who are within the same company is useless how many mops and suppliers use the same MPID but are completely different companies.

Have you ever seen how the D1s work on half hourly? almost perfect that way.

I don't think its needs to go to the supplier but can. The process has 2 starting steps and in the 2nd one it allows for the DC to report it to the MOP.

I know that the old YELG/NEEB process was DC to MOP but in other regions, especially MIDE, they operated it DC to supplier.

I prefer it getting to supplier since they are there customers and need to control the MOP, but the supplier could drag their feet and it is the MOP's area to correct so can it it from the DC end. Both ways have advantages and disadvantages but if it was sent to both the supplier could just monitor for a follow up action and work with the MOP. The supplier also has more chance of entry if inside as processes would allow for customer contact.

From a suppliers point of view, they could also be charged for DC errors...if they aren't watching their invoices.

The trouble with D0004's is they used to be ignored by some suppliers. In working closer with agents like YELG/NEEB it meant D0004's are important as you say but its something which takes years to sort out in the supplier end as they are huge volumes and just not resourced.

Not seen the HH version as I've never been in that end. Its looks similar in the BSCP but has proving methods.

Its not too bad in NHH, its just the differences between agents that weren't know at start up. Same with the D0139 where I know 2 agents totally disagree on their usage on a meter change, 1 sends the other argues the status is already in the D0150. Put it to Elexon in the past and they didn't seem too interested! Its a right pain when you find volumes if D0150's set to E and D0139's set to D sent in the same batch as you don't know which way round they are in MOP and supplier automation into MPAS becomes a concern.

Terrylw1

sacsquacco wrote: »

Have emailed Ofgem about the minimum inspection period on prepays being disregarded and surprisingly got a reply asking me for permission to publish " in the public domain " .,not sure what they meant by that, but as an example, late this afternoon got into a terraced house with a brand new occupier (young lady with child ) to find the electric prepay meter bypassed, will find out later how long thats been going off..This sort of thing will be happening all over the country in certain areas.Thanks for that info

Suggest you check this first to protect yourself as you will annoy some people in your company and the contracting suppliers.

http://www.ofgemjobs.co.uk/freedom-of-information

If more people did this I think Ofgem would be swamped.

If they publish it, the supplier will "circle its wagons" so surely they should investigate and take appropriate action?...:doh::wall::think::whistle:

utility_csa

Terrylw1 wrote: »

I don't think its needs to go to the supplier but can. The process has 2 starting steps and in the 2nd one it allows for the DC to report it to the MOP.

I know that the old YELG/NEEB process was DC to MOP but in other regions, especially MIDE, they operated it DC to supplier.

I prefer it getting to supplier since they are there customers and need to control the MOP, but the supplier could drag their feet and it is the MOP's area to correct so can it it from the DC end. Both ways have advantages and disadvantages but if it was sent to both the supplier could just monitor for a follow up action and work with the MOP. The supplier also has more chance of entry if inside as processes would allow for customer contact.

From a suppliers point of view, they could also be charged for DC errors...if they aren't watching their invoices.

The trouble with D0004's is they used to be ignored by some suppliers. In working closer with agents like YELG/NEEB it meant D0004's are important as you say but its something which takes years to sort out in the supplier end as they are huge volumes and just not resourced.

Not seen the HH version as I've never been in that end. Its looks similar in the BSCP but has proving methods.

Its not too bad in NHH, its just the differences between agents that weren't know at start up. Same with the D0139 where I know 2 agents totally disagree on their usage on a meter change, 1 sends the other argues the status is already in the D0150. Put it to Elexon in the past and they didn't seem too interested! Its a right pain when you find volumes if D0150's set to E and D0139's set to D sent in the same batch as you don't know which way round they are in MOP and supplier automation into MPAS becomes a concern.

HH version of D1s are chased by supplier and dc all the time, all updates must be sent via D0005s, even email updates have to be sent this way. Suppliers and DC push for resolution really hard, some suppliers are brilliant at this.

Dont get me started on the D139 and D150, i've been having endless fights about this, took it higher up and the D139 doesnt mean the D150 needs to be updated other than to E. MSMTD does not change. EDF annoy me to hell with this. Half of these issues are caused by DNOs not sending D139 after energisation. UKPN either dont send them or send them with no info so Wheatley never updates.... :cool: