Integration governance

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 (C4E) 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 Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL Hur Pulsen valt att se på mognadsgraden inom integration

Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL 5 områden Info – basen för framgångsrik integration – vilken info, vad betyder begrepp, vart finns masterdata? Traditional – data från a till b, inte sällan filer API – exponera och konsumera Cloud – Digital platform – när teknologin möjliggör nya affärsmodeller och utgören integrerad del I verksamheten

Individual initatives
MATURITY MODEL Integration Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL AD HOC Sprawling Individual initatives Builds technical debt Lack of overview What? Why? How? Value? Vanligt nuläge på initial nivå: Ad hoc och spretigt Spridda enskilda initivativ Saknar överblick vad finns? vad används och av vem? – påverkas? – viktigt? kan något återanvändas?

Integration platform / ESB
MATURITY MODEL Integration Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL IT-driven Integration platform / ESB API-Gateway Monitor technology ICC – Centralized Cost control

Reference architecture
MATURITY MODEL Integration Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL Governance! Strategies Reference architecture Dev-ops and Automation Monitor data flows

Goverance as enablement
MATURITY MODEL Integration Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL Business driven! Goverance as enablement C4E / Distributed API Economy Application network / resuse Time to market

New business and delivery models
MATURITY MODEL Integration Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL Intelligence driven! New business and delivery models KPIs and metrics Analytics

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

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) Offering expertise and best practices is the foundation More or less (de)centralized Small/big, may include developers and development resources More or less oriented towards self service, Center For Enablement (C4E) at a high maturity level Central services Shared services / Distributed Self service C4E

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: Centralization can make information less accessible Becomes development bottleneck Becomes to rigid

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: Improves speed in development/integration as well as in best practices Enables decentralization and integration projects driven by line of business Faster time to market More reusable assets Improved business value by taking advantage of network of assets Org tillräckligt stor för decentralisering Kompetens/levförmåga i LOB, inhouse eller extern (Konsult)

Borrowed from Mulesoft
Requires API:s for system access More asset consumers Notera att vi måste ha API:er, alltså en bit upp mogandstrappan OCH vi får fler användare av API:er mm För med sig något, kom ihåg! Återkommer Decentralized Self service

Dra nytta av Api:er genom C4E, självförstärkande

Några viktiga punkter

Av verksamheten för verksamheten Application network – continuously more and better API:s and applications

Goverance as enablement
MATURITY MODEL Integration Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL Business driven! Goverance as enablement C4E / Distributed API Economy Application network / resuse Time to market

API Economy APIs Asset Owner Data Consumers APPs End Consumer
Information Asset Owner Products Products Provides access to assets Data Consumers APPs End Consumer API-Economy – hur API:er kan påverka org ekonomi i positiv riktning Tillgängliggör resurser som snabbt/enklet kan förfinas/anpassas till andra slutkonsumenter Inovation Use applications and artifact and provide value to developers, APIs and assets Delivers rich customer experience

API Economy Slow Speed Fast Speed RENOVATE INNOVATE API --------------
Från att renovera till att innovera RENOVATE INNOVATE

API Management C4E and API Economy - Recapitulate:
Requires API:s for system access More asset consumers Self service Requires API Management!

API Management solution
Developer portal Customer engaging Self enrollment Self service Easy to use and find Self explanatory API Management Design Development (HL) Publishing Scalability Monitoring Analysis Monetization Use a developer portal to package and manage your APIs as products—and onboard, engage, and empower developers. API Gateway 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 (C4E) 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

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

Digital Platform AD HOC Individual initatives(Shadow IT) Re-active, built by accident None supportable IT-Driven Micro-services Containerization Serverless computing Inside-Out Approach ORGANIZED Digital strategy Open Platform 3.0 Devops culture BUSINESS DRIVEN Technology-enabled business model. Digital Ecosystems Outside – in approach INTELLIGENCE DRIVEN Evolution of new business models AI and Analytic Influences Predictive and corrective Cloud – Hybrid integration Solutions emerges when need arises. IT DRIVEN Cost control (TCO) Service initiative (SaaS/iPass) Hybrid setup IT Strategy related GOVERNED Cloud strategies & roadmap Cloud integration strategies Dev-ops Faster time market Cost efficient/pay as you go models Elastic(scalable) INTELLIGENCE & INNOVATION DRIVEN New services availible New delivery models KPIs metrics API Capabilty BASIC Single person initiative Internal focus API Gateway focused Implemented Self service Re-imaging core processes API Strategy API Economy B2B Driver API Analytics KPIs and metrics Traditional Integration 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 and delivery process CI/CD Implemented(Build/Deploy) Canonical models Cost efference by reuse Distributed C4E rather than ICC Low ceremony, good enough KPIs Metrics Information management. Ad-hoc projects Data retreived from various sources ESTBLISHED 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 OPTIMIZED MANAGED DEFINED DEVELOPING INITIAL Integrationsstrategin berör alla områden I mognadstrappan Möjliggör en Digital Platform!

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 and/or API catalogs - Documentation concerns Need an overview of all integrations and API:s Dependencies Support different stakeholders: Consumers Owners Developers Different tools: Word documents (please, no) Wiki (much better) Integration landscape tools (e.g. Nodinite, Pryorit) or Graph databases (e.g. Node4J) Define the documentation model What is an integration? Distinguish between API and implementation

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

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

So, what do we mean with “one integration”? But now? Som integrationsutv så utvecklar jag en app som körs I esb:n Integrerad med två system från teknikerns synvinkel Men appen implementerar en integration från ett verksamhetsperspektiv Vilket perspektiv styr dokumentationen?

So, what do we mean with “one integration”? Data type/function and data flow directions are other aspects Integrerar med B för att utbyta ordrar Kunder är en annan integration mellan samma system (eller?)

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

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

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

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

Together To The Top #TTTT #TTTT

Integration governance

Similar presentations

Presentation on theme: "Integration governance"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Integration governance

Similar presentations

Presentation on theme: "Integration governance"— Presentation transcript:

Similar presentations

About project

Feedback