SOA in Statistics Sweden 28th of October 2015 Jakob Engdahl, Dep. Director IT

SOA History in Stat Sweden SOA pilots and projects Triton-project 2008 2010 2014 2012 2006 In Data Environment-project ”Shared production environment”

SOA Pilots 2006-2008

Outcomes from initial pilots Focus on business objects (swedish gsim-like model) Make all services speak the same language - interfaces based on business objects Process oriented business objects Interconnect the services by using a separate "communication platform" Invest in an integration platform (biztalk) Create "smart" information flows between services Let the surveys select which services should be used Let the information objects be the focal point for the orchestration mechanism Use BAM (Business activity monitoring) for supplying a process status overview Implement a combination of process-, information- and utility-oriented services Encapsulate existing process oriented systems or create new services Services is something the business side should understand (can contain applications, webservices, databases etc) Surveys configure pre-deployed services - no service release when adding surveys in the platform Use SOA principles (Thomas Erl) for design Create a process dashboard Provide capabilities for controlling and monitoring the progress Invite all people working with a specific survey and assign them roles Roles should automatically translate to the right level of access in the dashboard and the services Implement a smart quality assurance mechanism in the dashboard Invest in datawarehouse solutions for manageing data Create data warehouses for all "steady states" Cornerstone in survey harmonization program Version control on everything

Communication platform: IDE In Data Environment 2008-2009 Business case becomes more clear but.. Still focused on the SOA-approach Scanning Web Collection Authentication Printing Manual editing Communication platform: IDE (based on BizTalk) Duplicate control Selective editing … Survey 1 Survey 2 Survey 3 Survey 4 …

Main architecture components

Triton 2010-2014 Business case focus - SOA just the solution

Shared production environment 2014… End-to-end business scope Build on previous architecture – detail and improve

Looking forward 2008 2010 2014 2012 2006 SOA pilots and projects Triton-project 2008 2010 2014 2012 2006 In Data Environment-project ”Shared production environment”

Looking back Focus on business objects (swedish gsim-like model) Make all services speak the same language - interfaces based on business objects Process oriented business objects Interconnect the services by using a separate "communication platform" Invest in an integration platform (biztalk) Create "smart" information flows between services Let the surveys select which services should be used Let the information objects be the focal point for the orchestration mechanism Use BAM (Business activity monitoring) for supplying a process status overview Implement a combination of process-, information- and utility-oriented services Encapsulate existing process oriented systems or create new services Services is something the business side should understand (can contain applications, webservices, databases etc) Surveys configure pre-deployed services - no service release when adding surveys in the platform Use SOA principles (Thomas Erl) for design Create a process dashboard Provide capabilities for controlling and monitoring the progress Invite all people working with a specific survey and assign them roles Roles should automatically translate to the right level of access in the dashboard and the services Implement a smart quality assurance mechanism in the dashboard Invest in datawarehouse solutions for manageing data Create data warehouses for all "steady states" Cornerstone in survey harmonization program Version control on everything