1. Adopting CSPA and CORE in Istat: the role of Enterprise Architecture Mauro Bruno, Monica Scannapieco, Marco Silipo Istituto Nazionale di Statistica - Istat

2.  CORE, CSPA and the Enterprise Architecture  CSPA compliance of CORE services  Scenarios for CORE usage  Istat current experience  Lessons learned  Enterprise Architecture enabling CSPA/CORE adoption  Conclusions CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve Outline

3. CORE & CSPA CSPA Common Statistical Production Architecture Reference architecture based on: i) existing standard models, such as GSBPM and GSIM, as shared vocabulary ii) the “plug and play” approach in designing, implementing and sharing statistical software solutions ESSNet CORAESSNet CORE 200920102011201220132014 2015 CSPA specification CSPA implementation 2016 Enterprise Architecture (EA) CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve CORE Common Reference Environment Environment for: i) executing standard statistical processes ii) defining processes in terms of abstract statistical services iii) mapping services to specific IT tools Enterprise Architecture (EA) : the role of the EA in the adoption of CORE-CSPA standards

4. Istat modernization program Started in January 2015 Istat re-organized as a process-oriented organization:  Overcome stove-pipes  Integration of data and processes  Adoption of standards CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve Adoption of an Enterprise Architecture approach Enterprise architecture approach «theorized» by Management Information Systems literature

5. CORE Services CORE has been designed as a platform to orchestrate statistical services: compliant with statistical standards (GSBPM, GSIM) Service definition Definition of a service at a conceptual level in terms of GSBPM subprocess, of the business function, of GSIM input/output. Tool Sas … Pl/sql CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve CORE services are compliant with CSPA principles Service implementation Definition of a service at a physical level. A service definition can have one or more implementations

6. Scenarios for CORE usage Scenario 1: CORE for the design and deployment of «easy» services workflow CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve Statistical process in CORE platform: 2. Configure: physical design of a process, starting from a conceptual process bind each service definition to an implementation 1. Compose: compose a process with available service definitions 3. Execute: run your process!

7. Scenarios for CORE usage Scenario 2: CORE: service and process design ESB: deployment and runtime CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve 2. Deploy: deploy service implementations on the ESB 1. Compose: compose a process with available service definitions 4. Execute: run your process! RPl/sqlJava CORE design ESB runtime 3. Bind: bind each service definition to an implementation

8. Istat current experience COE (foreign trade survey) Frame SBS (structural business statistics) CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve Different statistical surveys have been taken into account as possible candidates to be completely re-engineered in CORE. The following surveys have been selected as a first case study:

9. COE (Foreign trade survey)  Description: scope of the project was the analysis of the “as-is” process and the design of the “to-be” architecture, compliant with EA standards  Achievements so far: Prototype of CORE used to automate the data collection pipeline (file acquisition, loading of data in relational database and basic error correction) Etherogeneous technologies have been wrapped: shell scripts, sql- loader, pl/sql stored procedures.  Next steps: Use of CORE to automate the error correction and imputation phase. SDMX tools for preparation of files in SDMX format should be wrapped as CORE-CSPA services. CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve

10. COE (Foreign trade survey) CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve

11. Frame SBS  Description: analysis of the FRAME software architecture (“as-is” ) and design of the “to-be” architecture, compliant with EA standards  Achievements so far: First release of CORE. CORE was used to automate part of the process pipeline «duplicate elimination» Technologies wrapped: SAS (SAS inline editor, SAS tool launcher)  Next steps: Use of CORE to fully automate the process pipeline. Improve the first release of CORE according to CSPA principles and to EA standards. CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve

12. Frame SBS CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve CORE allows editing tool scripts (R, Sas, Pl/sql, shell) stored on the server, through an editing panel

13. Lessons learned Strong mandate needed to overcome stove-pipe mentality and to move towards a process-oriented approach Statistical business cases not always fit with CORE-CSPA approach:  not always possible to automate every process phase  strong interaction with survey data  many iterations Need to find adequate ESB platforms for complex statistical processes to pair with CORE CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve

14. The role of EA Need to «prepare» the context : EA!  to push re-engineering solutions,  to spread standards,  define global level principles CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve Organizational solution EA dedicated division tightly working with IT directorate acting as a bridge with production Technical solution Standardized process design/deployment CSPA CORE ESB

15. EA in action CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve CSPA service / EA building-block Define Business case Compose Standard runtime environment (ESB) Scenario 1: Business case implementing new EA building-block Scenario 2: Business case using available EA building blocks 1 1 2 2 3 3 4 4 CORE(conceptual) / ESB (physical) EA building-block repository 1 1 2 2 3 3

16. Conclusions Prepare the context for innovative solutions for process industrialization  if you do not want to be in prototype phase for ever :-) EA has a key role to support the adoption of such solutions CORE-CSPA, Mauro Bruno – June 23, 2016 Geneve