1. How to make EA-work impact everyday-work – the Statistics NZ story? Workshop on the Modernisation of Statistical Production April 2015

2. Topics Do we need to consider EA everyday? What is influencing Statistics NZ and our Enterprise Architecture Statistics NZ’s Enterprise Architecture - Simplified Framework The scope of Enterprise Architecture Our focus areas Thoughts re current activity - Who we are working with What is a Statistical Architecture Economic Social Data Data everywhere Other issues Key focus areas 2

3. Do we need to consider EA everyday? The strategic refresh is opening our minds to rethinking our future state in a range of new scenarios The government has increasing expectations related to the proactive use of our expertise and capabilities in a world of increasing data and information The world around us continues to evolve, offering new challenges and opportunities Our current Enterprise and Statistical Architectures (economic and social) need to be reviewed and possibly integrated. This will also include the newly developed Methodology Architecture. 3

4. What is influencing Statistics NZ and our Enterprise Architecture? 4 International Standardisation and Collaboration NZ Government Enterprise Architecture Better Public Services Vision and Strategy Open Networks Cloud Services Future State opportunities and drivers Government ICT Strategy and Action Plan

5. Statistics NZ’s Enterprise Architecture Simplified Framework Framework A methodology, or toolkit with guidance for helping achieve consistent and optimal outcomes across the organisation By having consistent and optimal architecture we –ensure we focus on the conceptual model (operating model first) –clearly understand ALL our deliverables –Clearly understand the dependencies between our work streams –avoid the “technology first” trap (which constrains transformational change) 5 Context - why Vision Strategic goals Benefit realisation Conceptual - what Operating model Activity model (GAMSO) Information model (GSIM) Business services Capability reference architecture Logical - how Process models (gBPM or GSBPM (Int’l)) Information architecture Data architecture Integration architecture Security architecture Solution architecture Industry Reference Architecture (CSPA) Physical – with Organisation structure Skills/Capability Applications/Software Infrastructure Data

6. The scope of Enterprise Architecture Enterprise Architecture is wide and inclusive in scope – but the Enterprise Architecture team does not ‘do’ everything, nor does it do anything alone. It seeks to provide an aligned and integrated view across all of these areas, developing roadmaps and options to support great decision making. 6

7. The defined business architecture areas. EA for everyday – The business architecture needs to be the primary focus 7

8. Our current activity (everyday) 8 Strategic Refresh Customer Focus Project Enterprise Collection Project Administrative Data First Project (EDA Advice) 2018 Census (EDA Advice) Strategic Refresh Customer Focus Project Data Futures Forum Govt ICT Action Plan Strategic Refresh People Strategy Refresh Social Statistics Architecture Statistical Architecture (economic) Business Optimisation Methodology Architecture Administrative Data First Project Operating Model - Processing

9. High level description of how we will process/organise/ manage our data to meet customer needs International frameworks and standards influence it Explains how we will integrate survey and admin data We currently have separate social and economic statistical architectures. Do we need an integrated one? 9 What is Statistical Architecture Customer Requirements Conceptual Frameworks Data Availability

10. Approved in 2007 Shift from a Survey Paradigm to Admin Data paradigm with Surveys filling the gaps Unit Record data research was a key driver Business Register to integrate data MEP developed to support the Architecture Introduced automated data processing Research is mostly complete, so we are ready for the full implementation 10 Economic Statistical Architecture

11. Completed in 2010, but more tentative Social is much harder to do than economic Confirmed three survey vehicle Big issue to be resolved: should we move from a survey model supported by admin data to a an admin data model supported by surveys. Future census research is clarifying this issue Property data frame being developed. IDI has grown faster than expected. 11 Social Statistics Architecture

12. Data Data Everywhere 12

13. Customer focus activities will adjust requirements Methodology Architecture Quality Management Framework Business optimisation Business Improvement Operating Model for Processing End-to-end view 13 Other Issues to be Integrated

14. Enterprise Architecture Focus Areas – to be useful in every day work 14 Keep the focus on the strategic outcomes Control the scope (work in capabilities not monoliths) Don’t do ICT for the sake of ICT Successful Transformation Customer expectations are being set by accelerating advances in technology and their experiences with the private sector Customers expect immediate access to our services via any channel and any device The expectations and needs of our customers are changing Shift in focus: from monolithic big-bang implementation to iterative capability development Services orchestration over systems replacements Right Size Enterprise Architecture Apply agile methodology and techniques to EA delivery Key components include partitioning, architecture sprints, close customer collaboration and national and international collaboration and integration Lean Enterprise Architecture In order to embrace agile EA combine top-down strategic architectures with bottom- up capability architectures Top-down and Bottom-up Architectures

15. 15 Thank You