INTEGRATION GOVERNANCE BJRN WALLIN In this session Bjrn

INTEGRATION GOVERNANCE BJÖRN WALLIN

In this session Björn Wallin will talk about the importance of a governed approach to integration. He will highlight governance to enable progress in the integration maturity model and Center For Enablement (C 4 E) as means for even further progression to a business driven level. Examples of instruments such as guidelines, API-strategy, documentation concerns etc will be given. ICSS Program

MATURITY MODEL Integration Digital Platform AD HOC IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • Individual initatives(Shadow IT) Re-active, built by accident None supportable Digital strategy Open Platform 3. 0 Devops culture Technology-enabled business model. Digital Ecosystems Outside – in approach IT DRIVEN GOVERNED BUSINESS DRIVEN • • • Individual initatives(Shadow IT) Solutions emerges when need arises. Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) Evolution of new business models AI and Analytic Influences Predictive and corrective INTELLIGENCE & INNOVATION DRIVEN • • • New services availible New delivery models KPIs metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Single person initiative API Capabilty Information management. Micro-services Containerization Serverless computing Inside-Out Approach AD HOC Cloud – Hybrid integration Traditional Integration DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B 2 B Driver API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • File transfers One-off integrations Person dependent. Builds technical debt Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

MATURITY MODEL Integration Digital Platform AD HOC IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • Sprawling Individual initatives(Shadow IT) Solutions emerges when need arises. initatives Digital strategy Open Platform 3. 0 Devops culture Technology-enabled business model. Digital Ecosystems Outside – in approach IT DRIVEN GOVERNED BUSINESS DRIVEN • • • Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) Evolution of new business models AI and Analytic Influences Predictive and corrective INTELLIGENCE & INNOVATION DRIVEN • • • New services availible New delivery models KPIs metrics Builds technical debt Lack of overview Single person initiative BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • API Capabilty Information management. Re-active, built by accident None supportable Micro-services Containerization Serverless computing Inside-Out Approach AD HOC Cloud – Hybrid integration Traditional Integration AD HOC Individual initatives(Shadow IT) DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED - What? - File transfers Why? Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B 2 B Driver API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • One-off integrations Person dependent. Builds technical debt - How? - Value? Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

MATURITY MODEL Integration Digital Platform IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • Individual initatives(Shadow IT) Re-active, built by accident None supportable Individual initatives(Shadow IT) Solutions emerges when need arises. Cloud – Hybrid integration Containerization Serverless computing Inside-Out Approach Integration platform / ESB IT DRIVEN • • Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related API-Gateway Digital strategy Open Platform 3. 0 Devops culture Technology-enabled business model. Digital Ecosystems Outside – in approach GOVERNED BUSINESS DRIVEN • • • Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) Evolution of new business models AI and Analytic Influences Predictive and corrective INTELLIGENCE & INNOVATION DRIVEN • • • New services availible New delivery models KPIs metrics Monitor technology ICC – Centralized Internal focus BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Single person initiative API Capabilty Information management. IT-driven Micro-services AD HOC Traditional Integration DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED API Gateway focused Cost control Implemented Self service Re-imaging core processes API Strategy API Economy B 2 B Driver API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • File transfers One-off integrations Person dependent. Builds technical debt Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

MATURITY MODEL Integration Digital Platform IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • Individual initatives(Shadow IT) Re-active, built by accident None supportable Micro-services Containerization Serverless computing Inside-Out Approach Open Platform 3. 0 Devops culture Strategies Reference Cloud strategies & roadmap Cloud integration strategies architecture Dev-ops Technology-enabled business model. Digital Ecosystems Outside – in approach AD HOC IT DRIVEN GOVERNED BUSINESS DRIVEN • • • Individual initatives(Shadow IT) Solutions emerges when need arises. Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related Faster time market Cost efficient/pay as you go models Elastic(scalable) Evolution of new business models AI and Analytic Influences Predictive and corrective INTELLIGENCE & INNOVATION DRIVEN • • • New services availible New delivery models KPIs metrics Dev-ops and Automation Monitor data flows Implemented BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Single person initiative API Capabilty Information management. Governance! Digital strategy AD HOC Cloud – Hybrid integration Traditional Integration DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED Internal focus API Gateway focused Self service Re-imaging core processes API Strategy API Economy B 2 B Driver API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • File transfers One-off integrations Person dependent. Builds technical debt Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

MATURITY MODEL Integration Digital Platform IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • Individual initatives(Shadow IT) Re-active, built by accident None supportable Micro-services Containerization Serverless computing Inside-Out Approach Digital strategy Open Platform 3. 0 Devops culture Digital Ecosystems Outside – in approach AD HOC IT DRIVEN GOVERNED Goverance as enablement BUSINESS DRIVEN • • • Individual initatives(Shadow IT) Solutions emerges when need arises. Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) C 4 E / Distributed Evolution of new business models AI and Analytic Influences Predictive and corrective INTELLIGENCE & INNOVATION DRIVEN • • • New services availible New delivery models KPIs metrics API Economy BASIC IT DRIVEN GOVERNED • • • Single person initiative API Capabilty Information management. Business driven! Technology-enabled business model. AD HOC Cloud – Hybrid integration Traditional Integration DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED Internal focus API Gateway focused Implemented Self service Application BUSINESS DRIVEN network / resuse • Re-imaging core processes • • • API Strategy API Economy B 2 B Driver Time to market INTELLIGENCE DRIVEN • • API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • File transfers One-off integrations Person dependent. Builds technical debt Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

MATURITY MODEL Integration Digital Platform IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • Individual initatives(Shadow IT) Re-active, built by accident None supportable Micro-services Containerization Serverless computing Inside-Out Approach Digital strategy Open Platform 3. 0 Devops culture Technology-enabled business model. Digital Ecosystems Outside – in approach AD HOC IT DRIVEN GOVERNED BUSINESS DRIVEN • • • Individual initatives(Shadow IT) Solutions emerges when need arises. Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) AI and Analytic Influences Predictive and corrective New business and delivery models INTELLIGENCE & INNOVATION DRIVEN • • • New services availible KPIs and metrics New delivery models KPIs metrics Analytics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Single person initiative API Capabilty Information management. Intelligence driven! Evolution of new business models AD HOC Cloud – Hybrid integration Traditional Integration DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B 2 B Driver API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • File transfers One-off integrations Person dependent. Builds technical debt Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

INTEGRATION GOVERNANCE What is it all about? § Applying strategies, polices and guidelines as instruments to get the right things done in a proper and effective way. § Assure architectural alignment, quality and security § Reduce complexity, cost and technical debt § Getting synergies and making reuse happen, speeding up § And the classical: Bridging the gap between IT/technology and enterprise/business

INTEGRATION GOVERNANCE How to make it happen? § Organisation that clearly defines responsibility and mandate for integration governance § Typically an Integration Competency Center (ICC) § Aka Center Of Excellence (COE) § Different ICC operating models (derived from Schmidt & Lyle) o Offering expertise and best practices is the foundation o More or less (de)centralized o Small/big, may include developers and development resources o More or less oriented towards self service, Center For Enablement (C 4 E) at a high maturity level Central services Shared services / Distributed Self service C 4 E

INTEGRATION GOVERNANCE ICC § Lead and support integration projects and/or provides expertise and guidance § Provides best practices, polices and guidelines for integration § Assess and select integration technology and approaches § Have a holistic perspective and pay attention to synergies, conflicts and system life cycles to optimize integration investments § Big company = big ICC, small company small ICC (one person!? ) § Business and technology insight § Potential risks/limitations: o Centralization can make information less accessible o Becomes development bottleneck o Becomes to rigid

INTEGRATION GOVERNANCE C 4 E § Shift of focus to enablement and evangelism § API-driven § Promotes the consumption and reuse of projects and assets § Provides tools, API: s and templates shared via portals for self service § Encourages not only to utilize assets but to add and improve them as well, scaling the network effect. § Intended output: o Improves speed in development/integration as well as in best practices o Enables decentralization and integration projects driven by line of business o Faster time to market o More reusable assets o Improved business value by taking advantage of network of assets

Borrowed from Mulesoft Requires API: s for system access More asset consumers Decentralized Self service

Borrowed from Mulesoft

Borrowed from Mulesoft Application network – continuously more and better API: s and applications

MATURITY MODEL Integration Digital Platform IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • Individual initatives(Shadow IT) Re-active, built by accident None supportable Micro-services Containerization Serverless computing Inside-Out Approach Digital strategy Open Platform 3. 0 Devops culture Digital Ecosystems Outside – in approach AD HOC IT DRIVEN GOVERNED Goverance as enablement BUSINESS DRIVEN • • • Individual initatives(Shadow IT) Solutions emerges when need arises. Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) C 4 E / Distributed Evolution of new business models AI and Analytic Influences Predictive and corrective INTELLIGENCE & INNOVATION DRIVEN • • • New services availible New delivery models KPIs metrics API Economy BASIC IT DRIVEN GOVERNED • • • Single person initiative API Capabilty Information management. Business driven! Technology-enabled business model. AD HOC Cloud – Hybrid integration Traditional Integration DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED Internal focus API Gateway focused Implemented Self service Application BUSINESS DRIVEN network / resuse • Re-imaging core processes • • • API Strategy API Economy B 2 B Driver Time to market INTELLIGENCE DRIVEN • • API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • File transfers One-off integrations Person dependent. Builds technical debt Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

API ECONOMY APIs Asset Owner Information Products Provides access to assets End Consumer Use applications and artifact and provide value to developers, APIs and assets APPs Delivers rich customer experience Data Consumers

API ECONOMY API Slow Speed ------- API RENOVATE -------------- INNOVATE Fast Speed

API MANAGEMENT § C 4 E and API Economy - Recapitulate: o Requires API: s for system access o More asset consumers o Self service § Requires API Management!

API MANAGEMENT SOLUTION API Developer portal API Management API Gateway • Customer engaging • Self enrollment • Self service • Easy to use and find • Self explanatory • Design • Development (HL) • Publishing • Scalability • Monitoring • Analysis • Monetization • The Runtime • Enforcing security • Executing policies (eg Rate Limiting) • Doing mediation • Facilitates Logging

In this session Björn Wallin will talk about the importance of a governed approach to integration. He will highlight governance to enable progress in the integration maturity model and Center For Enablement (C 4 E) as means for even further progression to a business driven level. Examples of instruments such as guidelines, API-strategy, documentation concerns etc will be given. ICSS Program

INTEGRATION GOVERNANCE Instruments - Best practices, guidelines, etc § Integration strategy § Goals § Organization § Economy § On prem / Hybrid / Cloud § Reference architecture § Service registry / API Catalog (API-mgmt) § Developer portals (API-mgmt) § Information models § Masterdata model

MATURITY MODEL Integration Digital Platform AD HOC IT-Driven ORGANIZED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • Individual initatives(Shadow IT) Re-active, built by accident None supportable Digital strategy Open Platform 3. 0 Devops culture Technology-enabled business model. Digital Ecosystems Outside – in approach IT DRIVEN GOVERNED BUSINESS DRIVEN • • • Individual initatives(Shadow IT) Solutions emerges when need arises. Cost control (TCO) Service initiative (Saa. S/i. Pass) Hybrid setup IT Strategy related Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) Evolution of new business models AI and Analytic Influences Predictive and corrective INTELLIGENCE & INNOVATION DRIVEN • • • New services availible New delivery models KPIs metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Single person initiative API Capabilty Information management. Micro-services Containerization Serverless computing Inside-Out Approach AD HOC Cloud – Hybrid integration Traditional Integration DEFINED DEVELOPING INITIAL OPTIMIZED MANAGED Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B 2 B Driver API Analytics KPIs and metrics BASIC IT DRIVEN GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • • • File transfers One-off integrations Person dependent. Builds technical debt Centralised (ICC) Integration Platform centric High ceremony Documentation driven Process and template oriented Monitors technology • • Monitored and governance Reference architecture Integration demand delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C 4 E rather than ICC Low ceremony, good enough KPIs Metrics AD HOC ESTBLISHED GOVERNED BUSINESS DRIVEN INTELLIGENCE DRIVEN • • • Ad-hoc projects Data retreived from various sources • Information Model Organisation around Information Management Policies Information Management Strategy Stewardship Documented standards and policies Technical platform • Workflow created Holistic approach to Info Man. Integrated information and business silos Continuous improvement of data quality • Strategy and standards aligned within the entire org. Data analytic

INTEGRATION GOVERNANCE Instruments - Best practices, guidelines, etc § Guidelines § API-design § Naming conventions § Message formats § Integration patterns § Security § Logging & Monitoring § Testability § Continuous integration § Automated test and deploy § Etc. .

INTEGRATION GOVERNANCE Integration and/or API catalogs - Documentation concerns § Need an overview of all integrations and API: s § Dependencies § Support different stakeholders: o Consumers o Owners o Developers § Different tools: o Word documents (please, no) o Wiki (much better) o Integration landscape tools (e. g. Nodinite, Pryorit) or Graph databases (e. g. Node 4 J) § Define the documentation model o What is an integration? o Distinguish between API and implementation

INTEGRATION GOVERNANCE So, what do we mean with “one integration”? § Let’s start simple: if we connect two systems we have one integration

INTEGRATION GOVERNANCE So, what do we mean with “one integration”? § Two integrations

INTEGRATION GOVERNANCE So, what do we mean with “one integration”? § But now?

INTEGRATION GOVERNANCE So, what do we mean with “one integration”? § Data type/function and data flow directions are other aspects

INTEGRATION GOVERNANCE So, what do we mean with “one integration”? § API: s is yet another aspect

INTEGRATION GOVERNANCE Not affected So, what do we mean with “one integration”? Client § And we need to distinguish between API Client and implementation (application) Stable API Changeble Implementation System API/Interface Implementation System Add/remove/update

INTEGRATION GOVERNANCE API vs Implementation § Different purpose and audience o API-documentation = interface specification üInitially for developers of implementation üPrimarily and over time, for users/consumers of the API o Application documentation = Technical description üFor developers/maintenance § Versions of API and application is not (doesn’t have to) be synchronized o Version 2. 3. 1 of the application may still implement version 1. 0 of the API

INTEGRATION GOVERNANCE Integration and/or API catalogs - Documentation concerns § Need to cover o Integrations (flows) üDefine what it means and granularity üShows the dependencies o API: s / Interfaces o Implementations § Decide a manageable level of complexity and coverage!

Together To The Top #TTTT