Technical Update
Technical development of the appropriate business process models, data models and interface specifications (including XML Schema) to support the Valuebill Pilots, is approved.
The Valuebill Pilots are designed to develop and test both the business case and the operational exchange of information. In support of this, the key technical components of the project deliverables focus on the requirement for electronic sharing and exchange of information between the VOA and the Local Authority Billing departments.
Latest News
- May 2006: Version 4-0 Valuebill schemas were formally moved to agreed status on GovTalk. No comments were received during the consultation period so the current V4-0 can be implemented without any further changes.
- April 2006: The Valuebill Schema has been through the formal GovTalk public consultation, which completed on 13th April. Subject to further comments, the move to agreed status is due on 11th May.
- Feb 2006: The Valuebill Schema Maintenance Release-v4-0 is now being submitted to GovTalk for consultation following assessment and comment by all Valuebill stakeholders and suppliers - this is an update on Version 3-1 released at the close of the main Project (March 2005).
- Feb 2006: The standards for Valuebill are being sustained by London Connects in consultation with the VOA and the Valuebill technical consultant. These standards can be accessed via www.govtalk.gov.uk. We will provide updates on the website on any developments or proposals for changes to the standards, as well as notifying suppliers.
- Jan 2006: The Valuebill Schema Maintenance Release-v4-0 has been sent for assessment and comment to all Valuebill stakeholders and suppliers - this is an update on Version 3-1 released at the close of the main Project (March 2005). VOA’s new system for accepting Valuebill updates is due to go ‘live’ in April/May.
Schemata
Schema version-v4-0 moved to agreed status in May 2006 and this schema can be accessed via www.govtalk.gov.uk. No comments were received during the consultation period so the current V4-0 can be implemented without any further changes.
Schema Designs
The Valuebill Pilots are designed to develop and test both the business case and the operational exchange of information. This exchange will be based upon the use of XML data for the electronic transfer of information between the pilot participants.
Draft XML schemata have been designed to facilitate the required data transfers. Analysis of the business processes indicated three main data transfer streams:
- Billing Authority reports sent to Valuation Office Agency.
- Valuation Office Agency update schedules for the Billing Authorities.
- Exchange of land and property gazetteer entities between local and national gazetteers, billing systems and the VOA property database.
Testing and validation of these schemata will continue throughout the pilot and the schemata will be refined according to results and comment received from stakeholders and their suppliers.
It should be noted that the objective of the pilot is not necessarily to replicate the existing, largely manual, processes and that the use of XML data transfers which, by their design will apply more rigour to the process, is likely to identify a need to upgrade or regularise some of the supporting business processes.
It is envisaged that, during the course of the pilot, at least some of the system suppliers will be able to upgrade their system functionality to deliver XML output that meets the requirements of the appropriate schema designs.
The design of the schemata follows the ‘e-Government Schema Guidelines for XML’ and makes use of the architectural schemata available through GovTalk. A key aspect of the Valuebill initiative is the unambiguous identification of the property about which information needs to be exchanged. The three schemata use a combination of structured address data and the Unique Property Reference Number (UPRN) to support property identification. They therefore incorporate the e-GIF architectural schemata for addresses and personal details and make particular use of the BS7666 address structures.
Technical View
