1. Preparing for A Strategy for Change Based on Previous Experiences Steve Vale Office for National Statistics, UK

2. Background SIC(92) Lessons Learned SIC(2003) Lessons Learned
Contents
Background
SIC(92) Lessons Learned
SIC(2003) Lessons Learned
Strategy for 2007

3. Discontinuities for statistical outputs
Background
Major revision of international classifications of economic activity for 2007
Discontinuities for statistical outputs
Substantial changes for statistical business registers
Transition needs to be carefully managed to maintain quality

4. Standard Industrial Classification
Hierarchical classification based on 5-digit codes
UK version of NACE
Consistent at higher levels with ISIC
Last major revision
Minor revisions late 1990s and 2003

5. SIC(92) Implementation: Approach
Clerical re-coding from recent register proving survey questionnaires
Specific register proving exercise for SIC(92) and new business register
Automatic imputation of codes for remaining small enterprises
Old and new classifications both live on the register for one year

6. SIC(92) Implementation: Lessons learned
Consistency problems when more than one classification is “live”
Quality (consistency) of coding could be improved using coding software
Burden on businesses of extra register proving survey
Avoid simultaneous major changes so that individual impacts can be analysed

7. SIC (2003) Implementation: Approach
Stored business descriptions for local units re-coded clerically
Automatic coder updated as soon as sufficient metadata available
Clerical and automatic coding results compared
Forward and backward correlation tables constructed for local units with no stored description
Local unit codes fed up to enterprise level

10. SIC(2003) Implementation: Lessons learned
Planning time for data suppliers too short – inconsistent implementation
Store business descriptions for automatic re-coding
Improve questionnaires to capture better quality business descriptions
Relevance of new codes needs testing
Re-coding can impact on register quality and bias

11. Register customers need early warning of changes
… continued
Register customers need early warning of changes
Register users need re-training, especially coding staff
Total cost > Euro (part funded by Eurostat)

12. Correlation tables for smaller units
Strategy for 2007
Increased use of stored business activity descriptions and automatic coding software
Correlation tables for smaller units
Limited clerical resource for quality assurance and impact assessment
Evaluate success afterwards

13. Time – 18 months needed between final codes and implementation to:
Key Requirements
Automatic coding tool
Time – 18 months needed between final codes and implementation to:
Update coding tool
Allow suppliers time to adapt
Re-code
Create and test correlation tables
Analyse impact
Resources – staff and money

14. Any Questions? www.statistics.gov.uk/idbr steve.vale@ons.gov.uk
Further information
Any Questions?