IDBR Re-engineering Gail Rowles

Introduction The session will cover the following: Why re-engineer IDBR? Priorities What is the Register? Current units model Why change to a new units model? Future units model The re-engineering scope Where we are now? Expectations

Why re-engineer IDBR? Corporate platform IDBR Quality Review Growing and changing demands Better efficiency Better sub-national data Better access Reduce operational costs Corporate platform - IDBR has to migrate to a new platform (oracle) from Ingres as Ingres will no longer be supported and Oracle has been identified as the corporate platform

Priorities The register on a new corporate platform Modify the register units model Improve user front-end Better links to Lotus Notes and other systems A secure environment for electronic data collection Improve functionality to meet known customer requirements Adopt appropriate corporate tools Adaptability to new and changing sources (e.g. BT and YELL)

What is the register?

Current units model

Why change to a new units model? EU requirements Mainly for Agriculture & Enterprise Groups Classifications Regional data – increased demands for small area data including Allsopp Increased use of administrative sources To facilitate electronic data collection Business demography – European & National IDBR Re-engineering – the IDBR has to migrate to the new ONS corporate standard platform (Oracle). This provides a good opportunity to change the underlying units model. EU requirements – a new version of the EU business registers Regulation is being prepared. If this is agreed it will make holding of enterprise group data compulsory. Regional data requirements – there are growing demands for statistics at the regional level and lower boosted by the findings of the recent Allsopp Review. Increased use of administrative sources – The Allsopp review also recommends that the ONS should make better use of data from administrative sources for the production of business statistics. Electronic data collection – the main source of local unit data for the IDBR is the Business Register Survey (BRS). The survey has introduced limited electronic data collection for businesses with large numbers of local units Business demography – there is an increasing national and international demand for data on business demography based on statistical business registers. One consequence of this is that register coverage is now being increasingly defined in terms of numbers of businesses rather than just the proportion of economic activity. It is estimated that there are around 1.8 million “businesses” not on the IDBR.

Future units model

The re-engineering scope Relationship between register and Data Collection ONSide stages Situation Definition – Initial findings and recommendations Solution Shaping – Feasibility study Solution Design High Level Solution Analysis & Design Detailed Solution Analysis & Design Solution Delivery – Design & build iteration Consolidation/Transformation Preparation -Implementation Customer Relationship Management

The re-engineering scope (continued)

Timetable Deliverables Milestone Project Brief August 2005 Situation Definition ONSide phase Solution Shaping ONSide phase Sept-Dec 2005 Customer Relationship Management (CRM) prototype Oct-Nov 2005 Produce feasibility report and solution recommendations January 2006

Where we are now? Joint IDBR/Data Collection Modernisation solution shaping stage High level analysis complete Lower level analysis started including proof of concept Architecture Vision document complete

Expectations Scope IDBR – more Design April 2006 Register available June 2007 Functionality December 2007

Discussion