140 likes | 268 Views
Valuebill. A Local e-Government National Project. Bernard Walker Staffordshire Moorlands DC. www.newham.gov.uk/valuebill. Valuebill - Pilot Project. There is confusion between LLPG and Valuebill – so what is the difference?
E N D
Valuebill A Local e-Government National Project Bernard Walker Staffordshire Moorlands DC www.newham.gov.uk/valuebill
Valuebill - Pilot Project • There is confusion between LLPG and Valuebill – so what is the difference? • So to explain the difference, lets go back to basics starting with the LLPG. • And then we’ll discuss Valuebill
LLPG process • Select key datasets • Match them to the Highways authority Streets. • Identify unmatched streets • Attach streets • Identify those without streets • Allocate to a street. • Mount the result on an approved LLPG system • Cleanse all those Flat addresses and remove duplicates. • Then you start updating the NLPG hub on a Regular basis – which means your Authority is at Level one • This is essential for Valuebill.
Are you level one? If not why not? • So what do you do with your LLPG once you have achieved level one? • Park it in a corner and polish it? • Or try to connect other datasets to it?
Link in address based applications to the dataset • Planning, • Building Control, • Environmental Health, • GIS. • This produces a very powerful integrated planning tool. • Future development is to integrate Land Charges.
Valuebill • Provides links from LLPG to CTax and NNDR to the Valuation Office database. • The aim is to improve Local tax collection by • Identifying properties that have dropped through the local tax net, • Speeding up communications with VO • Increasing the accuracy of communications to the VO.
Hang on – didn’t we include CTax and NNDR in the original LLPG matches? • Yes, but have you checked if they are still in line? • We were horrified by how far they had drifted when we measured alignment as part of the Valuebill process.
So what is the Valuebill mechanism? Stage 1 part 1 • Extract CTax and NNDR and extract LLPG, • Then use the Valuebill Starter pack matching software to analyse all the differences. • This is an Access database that produces reports on anomalies between the two address lists. • We found mismatches: • In CTax, not in LLPG about 800 properties • In LLPG not in CTax about 800 propoerties
So what is the Valuebill mechanism? Stage 1 part 2 • Resolve these • 4 people, 3 months, 50% time • The data custodian, full time. • Tighten up key manual processes, and do many re-matches. • Re-energise BC in notifying new build properties and changes that require revaluation. • Ctax – tighten up on Flats. • Also start to tackle NNDR discrepancies – Industrial estates, etc.
Stage 2 • Submit CTax and LLPG addresses to IA • IA match the following:- • Your data to NLPG • Your data and the VO database and also to NLPG. • The VO database is held Nationally in London, so we need Intelligent Addressing because • They manage that database, • They calculate the Official Match Percentages. • IA also produce a list of further anomalies and index number mis-matches to be resolved. • At this stage we involved our VO local office to sort out these anomalies.
VO Support • Enthusiastic response from our local (Stoke) VO. • The VO were impressed by our LLPG data and its integration to the GIS. • Information transfer was not one way – VO have lots of accurate map data on Industrial estates that they made available to us. • Helped us to tidy up our own data • benefits for precise billing on NNDR.
Valuebill benefits • Faster communication with VO for band revaluations • Leads to faster identification of tax collection. • Other Authorities (Stoke and Huntingdon) have identified entire properties (flats) that have slipped through the local tax net resulting in 150k per year at Huntingdon and 18k at Stoke. • Unexpected major benefit - a firm address base for CRM – vital for CRM. • Technical: Suppliers holding LLPG addresses and UPRNs. • Reduced confusion: UPRNs on all communications, especially to the VO. • Other possibilities include • CTax addresses changes can be updated electronically • Keeping the databases synchronised!
Summary • A lot of effort • creating the database • cleansing it • ensuring that it is maintained • A lot of benefit from • Certainty of address data • Speed of data transfer • Speed of updates • Support for other functions eg CRM
Thank you • Bernard Walker