IT4IT, det er ikke en genopfindelse af hjulet. Oktober 2016,

Transcription

1 IT4IT, det er ikke en genopfindelse af hjulet Oktober 2016,

2 Hvad har vi gang i?

3 Abstract Mange metoder bliver introduceret i IT til at understøtte ting som SAFe, DevOps etc. Typisk ændrer de radikalt måden man arbejder på, og introducerer nye værktøjer for at optimerer resultatet. Hvad man har gjort med IT4IT initiativet er en gang for alle definere de komponenter der udgør en toolchain på tværs af alle IT funktioner. I dette indlæg vil vi se på hvordan IT4IT er fokuseret på informationsmodellen på tværs af IT. Der ses på det store billede og de step der skal til at skabe værdi for IT for at kunne arbejde serviceorienteret i en hybrid verden med mange leverandører

4 Most IT organizations optimizing around Process & technology silos Policy Requirement IT Project Event Subscription Business Process Model Defect Demand Physical Model RFC Asset Incident, Problem Business Leader Enterprise Developers IT Engineer IT Operations Users Architect

5 The problem IT is changing and our customers are struggling This shift is triggered by technology disruptions (eg cloud, mobility ) and can be realized by transitioning people, process and technology. A prescriptive recipe for IT would provide consistency to the journey This shift is driven by business disruptions (eg digital enterprise) and is forcing a new style of IT. The journey requires transformation - a new culture, structure (operating model) along with the prescriptive design guide for service brokering in a multi-supplier environment TRADITIONAL IT (Technology provider) INDUSTRIALIZED IT ( provider) IT as a DIGITAL ENTERPRISE ACCELERATOR ( broker) Project lifecycle governs investment Process model controls workflow NEW TECH Project lifecycle governs investment Process model expanded Agile concepts introduced NEW STYLE lifecycle governs investment Formal IT operating model to support modern workflow (agile, bi-modal, lean ) Prescriptive IT systems model to power

6 What is IT4IT? Two foundation components: Reference Architecture and IT Operating Model Reference Architecture prescribes the technology and information fabric for managing the business of IT Prescriptive guide enables end-end visibility of the service lifecycle First of its kind in IT industry (data-driven, functional focus) Process agnostic customers can employ ITIL, COBIT IT Operating Model framework describes the structure for managing the business of IT Based on industry standard business principles (Porter s Value Chain); supports Lean, Kanban Resonates with IT leaders, becomes the organizing principle for transforming to New Style of IT Fills a void in the industry (no formal IT operating model today) Methodology agnostic customers can use agile, waterfall

7 IT4IT Activities in The Open Group IT4IT Milestones: Snapshot 1.3 released October in review, ratified by October 2015 People Certification: 10 / 2015; tool Certification: about to be ready, and 3.0 work has started Related Open Group Forums TOGAF Archimate EA Framework Harmonization Capability Planning EA modeling Language Adoption within IT4IT Capability Planning Joint activities & Sub Groups Capability Based Modeling (TOGAF & Archimate) Harmonizing Archimate with UML Adopting Archimate in IT4IT IT4IT sub-groups: Lifecycle Management Agile integration to IT4IT IT Financial Management Intelligence and Reporting Adoption Workgroup

8 IT4IT How it started Five years ago Problem Insufficiently integrated toolsets to manage e2e. Inability to gain true insight, hence inability to optimize. Lack of collaboration across all IT competency centers. Immaturity to tackle trends like cloud, mobility, devops. Shell/HP partnership

9 IT4IT How it started Five years ago Problem Insufficiently integrated toolsets to manage e2e. Inability to gain true insight, hence inability to optimize. Lack of collaboration across all IT competency centers. Immaturity to tackle trends like cloud, mobility, devops. Shell/HP partnership IT4IT Customer Consortium Approach From inside-out focus to outside-in value thinking. Provide solution guidance to manage the business of IT. Prescribe data integration and insight via a model. Complement process (what) with data (how to ). 12

10 IT4IT How it started Five years ago Problem Insufficiently integrated toolsets to manage e2e. Inability to gain true insight, hence inability to optimize. Lack of collaboration across all IT competency centers. Immaturity to tackle trends like cloud, mobility, devops. Shell/HP partnership IT4IT Customer Consortium Approach From inside-out focus to outside-in value thinking. Provide solution guidance to manage the business of IT. Prescribe data integration and insight via a model. Complement process (what) with data (how to ). Requires a standard to drive market adoption Value Optimize the Business of IT with quality Insight across the complete Value Chain, driving intelligent Decisions, to deliver IT s Faster, Better, Cheaper, and with less Risk IT4IT is an official industry standard as of Oct 20 th, 2015 IT4IT The Open Group 13

11 The IT Value Chain has 4 IT Value Streams as in a stream of activities delivering value IT Value Chain Plan Build Deliver Run Model Backbone Finance & assets Sourcing & vendor Intelligence & reporting Resource & project Governance, risk and compliance Efficiency & Agility

12 S2P R2D R2F D2C Meet the IT value streams Plan Build Deliver Run Your objective Define your strategy to balance and broker your portfolio. Prioritize every requirement to build/source the best services and deploy them. Handle each request by streamlining the process to fulfill it. Proactively detect issues and take actions to correct them. IT4IT prescription End-to-end integrated Reference Architecture 16

13 S2P R2D R2F D2C Phases for each value stream life cycle on a repeatable, predictable, coherent and future safe reference architecture Strategy to Portfolio Requirement to Deploy Request to Fulfill Detect to Correct Align strategy Rationalize portfolio Prioritize backlog Manage investment Plan & design Develop Test Deploy Define & publish Subscribe Fulfill Measure Detect Diagnose Change Resolve 17

14 S2P R2D R2F D2C The service model The service model assuring IT service transparency Conceptual Model Logical Model Physical Model Demand Policy Portfolio IT project Requirement Release Event Incident Change Strategy to Portfolio Requirement to Deploy Request to Fulfill Detect to Correct Business Enterprise PMO Developers Testers IT Engineer IT Operations Users Architect 18

15 IT4IT reference architecture level 1 Strategy to Portfolio Architecture Enterprise Architecture Requirement to Deploy Request to Fulfill Detect to Correct Defect Defect Policy Requirement Test Offer Consumption Problem Incident Policy Requirement Test Case Shopping Cart Problem/ Known Error Incident Portfolio Backlog Item Proposal Portfolio Demand Source IT Initiative Source Control Project Build Build Package Build Build Package Offer Management Catalog Composition Offer Catalog Entry Request Request Rationalization Subscription Scope Agreement Chargeback Contract Usage Record Chargeback/ Showback Usage Contract Run Book Level Diagnostics & Remediation Event Monitor Event Monitoring Fulfillment Request Conceptual Portfolio Conceptual Blueprint Logical Blueprint Design Release Composition Release Release Blueprint Fulfillment Execution Desired Model RFC Change Control Actual CIs Configuration Management This diagram is based on material developed by the IT4IT Forum of The Open Group Oct 2015 Key functional component Entity relationship model object Key data object Auxiliary data object IT4IT is a trademark of The Open Group 19

16 Strategy to Portfolio phases and activities S2P Align Strategy Rationalize Portfolio Prioritize Backlog Manage Investment Define objectives Align business and IT roadmaps Set up standards and policies Enterprise architecture portfolio rationalization Create service blueprint and roadmap Consolidate demand Analyze priority, urgency, and impact Create new or tag existing demand Business value, risk, costs, benefits & resources What-if-analysis Ensure governance 20

17 Requirement to Deploy phases and activities R2D Plan & Design Develop Test Deploy IT Project plan Logical service model Requirements Functional & technical Standards & policies Development: Agile, iterative, waterfall Source & set up development environment Version control Developer testing Functional: desktop, web, mobile Performance: desktop, web, mobile Security: static, dynamic Release plan Change and configuration process Knowledge management Application and security monitors 21

18 Request to Fulfill phases and activities R2F Define & Publish Subscribe Fulfill Measure Merge catalog items from all fulfillment engines Set pricing, options and SLA Publish services Portal engagement Personalized experience Self-service Manage subscriptions Route fulfillments Automate deployment Use internal and external providers Integrate with asset, configuration and change systems usage measurement Chargeback/ showback Cost transparency Surveys and ratings 22

19 Detect to Correct phases and activities D2C Detect Diagnose Change Resolve See events, alarms and metrics across entire infrastructure Understand user issues Trace the relationship between events Enrichment Root cause Severity and business impact Defined escalation path Auto-fixed common issues Define change request Perform problem and risk analysis Approve Implement change Leverage run books Verify recovery Close records 23

20 Reference Architecture Overview

21 What does the RA look like? One model described through multiple abstraction levels (like other industry standards) Layer 1: End-to-End Overview Layer 2: Value Stream Documentation Layer 3: Vendor-independent Architecture Layer 4: Vendor-specific Refinement Architecture Layer 5: Solution Architecture Moves from generic overview to specific details Uses informal notation at Layer 1-2 Uses formal notation (Archimate + UML) at Layer 3 Useful to non-architect and architect audiences Layers 1-3 are defined/controlled by The Open Group Layers 4-5 are vendor owned/controlled for implementation and product positioning

22 IT4IT RA 2.0: A few basic concepts Problem Incident Key Data Object objects that delivers end to end traceability of what goes on in it:. Problem/ Known Error Incident Event Functional s denotes the essential components of an IT4IT infrastructure. Functional s deliver the essential service that control the contained key data objects: Event Monitor Monitoring Comp. Relationship between.key data objects Configuration Management model Data Object.is special data object that describe the service delivered by IT to its consumers Actual CIs

23 IT4IT RA 2.0: Strategy to Portfolio (S2P) Align IT portfolio with business strategy and make sound investments Strategy to Portfolio When a business has new needs (new or changed business processes), or when performing portfolio optimization, or operations has issues that cannot be handled without development, then an opportunity needs to be logged with a strategy as a new backlog item. The link between the conceptual service roadmap and the line of business that ultimately sets the goals of IT is the IT architecture for the services that business needs. Architecture Policy Portfolio Backlog Item Scope Agreement Conceptual Enterprise Architecture Policy Proposal Portfolio Demand Portfolio Conceptual Blueprint Part of strategy is to maintain a set of policies that IT must deliver on. Some of the policies relate to specific services. When IT strategy decides to make a change in IT, a scope agreement is created. The scope agreement references the associated opportunity. The Portfolio is captured as a set of conceptual service designs each with a set of associated blueprints that represent a conceptual roadmap for the service.

24 IT4IT RA 2.0: Requirement to Deploy (R2D) Source what the business needs, when it wants it Defect Defect Requirements are captured and, during a development project, requirements are associated with the project and underlying opportunity description. Which release will deliver what requirement is also planned. Note this is also true if the project is subcontracted or delivered as a COTS or external service. Requirement Test Testing and any associated defect is related to the release under Test. Requirement to Deploy Requirement Source Source Control Test Case Build Build The source for delivering a new release is controlled as a source artifact associated with the design documented in the design package and design templates. Projects deliver a set of releases. The Release package is the assembly of development artifacts that are part of a release. The IT Initiative is picked up by a development organization and managed through one or several delivery/development projects. Everything in the development domain is managed through projects. IT Initiative Logical Blueprint Project Design Build Package Release Composition Release Build Package Release Blueprint A Release package assembles all of the needed information to make a release based on specific deployment topologies and other constraints. RFC Change Control Comp. Deployment can happen in one of two ways either through a traditional Change Management process where RFCs are created based on the content of the release package or through publishing the service blueprints that R2F can use.

25 IT4IT RA 2.0: Request to Fulfill (R2F) Enable seamless consumption and monitor usage Offer Consumption Offers can be constructed based on the Catalog entries. The offer adds details on approval and cost, as well as controls what users can consume which service. Request to Fulfill catalog entries are maintained in a service catalog and represent what can be ordered from IT. A service entry is typically constructed from a Blueprint. Offer Mgmt. Catalog Composition Offer Catalog Entry Shopping Cart Request Rationalization Request Fulfillment Request Fulfillment Execution Comp. Desired Model Subscription Chargeback Contract Usage Record Chargeback / Showback Comp. Usage When a user wants a service from the catalog, a subscription is created. A subscription has an associated lifecycle. Throughout the lifecycle of a service, requests can be created against the service initially create a service, make modifications, and delete later on. The service requests are defined in the blueprint. When services are running, the system generates usage records which are summarized in chargeback/showback records associated with the subscription. Delivering a service is done through a fulfillment request which will use the same mechanism as any other deployment. This implies RFCs and Deployment packages get in action.

26 IT4IT RA 2.0: Detect to Correct (D2C) Anticipate and resolve business execution issues Problem Incident Problem or Incident Management might log a defect to later releases of services, and/or potentially request a new release. Problem/ Known Error Incident Incidents are created either by the help desk or event system, which is the center for fixing issues in operations. Detect to correct Contract Run Book Level Diagnostics & Remediation Event Monitor Event Monitoring Comp. Problems are created by an incident system to indicate issues that need deeper investigation and potential changes in the configuration. Events, Incidents, or Problem investigations use run books to diagnose and remediate issues. Based on definitions in service monitor, the event system collects and correlates events from all of the operations. SLAs are defined, designed and created vs. the service along it s lifecycle and then captured in D2C. RFC Change Control Comp. Actual CIs Configuration Management monitors are created as part of deploying services and defines what needs to be monitored in the operations domain. Everything is tied together through the Actual CIs information model for what has been deployed.

27 Level 1 High level overview of the end-end value chain using informal notation Functional Data object Entity relationship Audience: non-architects Value streams defined Functional components named Data objects and relationships described model backbone formed model backbone

28 Level 2 Detailed rendering of each value stream using informal notation Example: Strategy to Portfolio Enterprise Architecture Architecture Business Process Business Strategy Conceptual Blueprint n:m Portfolio Backlog Item Portfolio Portfolio Backlog Item Conceptual 1:n Portfolio Demand Portfolio Backlog Item Portfolio Backlog Portfolio Backlog Item n:1 Problem Detect to Correct Conceptual Blueprint 1:1 Problem, Known Error n:1 Policy n:m Portfolio Backlog Item (rationalized/ Prioritized) n:1 Competency (availability) Policy 1:n Labor Management Cost Modeling IT Cost Model ITFM Supportive Function 1:n Policy n:m Proposal Scope Agreement n:1 Assets (availability) IT Asset Management Supportive Function n:m Scope Agreement 1:n Design Logical Blueprint Requirement to Deploy Requirement Requirement Requirement to Deploy Investment Portfolio Comp. IT Budget Project IT Initiative This diagram was developed/ published by the IT4IT Forum of The Open Group ITFM Supportive Function Model Requirement to Deploy Functional - Key Functional - Auxiliary Data Artifact Key Data Artifact Auxiliary Audience: non-architects + architects Relationships between data objects defined in greater detail (eg cardinality) Functional components defined in detail Auxiliary and supporting functional components identified Entity relationship Record fabric Integration Engagement dataflow Current practice

29 Level 3 Vendor independent architecture using formal notation (ArchiMate & UML) [Value Stream] Detect to Correct [Capability Discipline] Event Management [Capability Discipline] Incident Management Essential [Essential ] Register Event [Essential ] Acknowledge Event Event Root Cause Analysis Perform Remediation [Essential ] Register Incident [Essential ] Manage Incident Incident Audience: architects Scenarios + capabilities * * Essential services [Functional ] Event [Functional ] Diagnostics & Remediation [Functional ] Incident Attributes of data objects (UML) Essential Attributes (for data objects) «ItemDefinition» Incident - GlobalId :String - State :IncidentStateEnum - Name :String - Description :String - Solution :String - CreateTime :DateTime - LastModifiedTime :DateTime - ResolutionTime :DateTime - ClosedTime :DateTime «enumeration» IncidentStateEnum new created assigned wip resolved resolution_confirmed closed

30 Level 4-5 Vendor specific architecture R2F V.2.0 May 14 th 2015 n:m 1:1 Propel Portal Engagement Experience Portal User Profile Catalog Collaboration SM, SAW Knowledge Self Support This diagram was developed/ published by the IT4IT Forum of The Open Group Contract (Template) Functional - Key Functional - Auxiliary Model Data Artifact Key Data Artifact Auxiliary Entity relationship Record fabric Integration Engagement dataflow Current practice PPM, ALM, AgM, Project SAW Requirement to Deploy Codar Release Composition Release Blueprint Requirement to Deploy BSM, SM, SAW Level Comp. Contract Detect to Correct 1:1 1:n Propel Catalogn:m Offer Mgmt. n:m Offer Catalog n:m Offer CSA, SM, AM Catalog Composition Catalog Entry Catalog Entry (Unbound) Release Package Shopping Cart Request 1:n Contract (Instance) Request 1:n 1:n 1:1 Request Rationalization 1:n Request Fulfillment Request RFC 1:n Subscription Propel SX Fulfillment Execution Detect to Correct Composite/Compound Request RFC n:1 n:m Catalog Entry (Bound) Actual CIs Desired Model 1:n Configuration Management Actual CIs Detect to Correct Monitor Subscription 1:n Request 1:n CSA + AM Chargeback / Showback Chargeback Contract Bill/Invoice Usage Usage Usage Record Chargeback Contract AM SM, SAW UCMDB CSA, SM, SA, BSM Suite Change Control IT Financial IT Supplier NA, Fulfillment SE, DMA, Management Monitoring (External to IT) Engine & Deploy/ OO IT Asset Management Supportive Function Fulfillment Request Propel 1:n 1:1 Offer Consumption Provision Systems Shopping Cart Usage Supportive Function Status Detect to Correct Level Status Conversation Knowledge Item Knowledge & Collaboration Supportive Function SM, SAW Incident Incident Detect to Correct Audience: architects, practitioners, vendors Owned/controlled by product vendors Unique vendor extensions Implementable model with product mapping (Reference Implementation)

31 IT4IT is the framework to drive HPE Transformation Areas Transform to a hybrid infrastructure Protect your digital enterprise Transform to a Broker Transform to a Integrator Enable workplace productivity Empower their data-driven organization Transform to a Supplier IT4IT sits at the centre of the 4 HPE plays and is most readily associated with Transform to a Hybrid Infrastructure Within this, every IT organization is playing a combination of 3 fundamental roles Broker, Integrator and Supplier: managed well, these 3 roles deliver true value to their business These roles function with the support of the IT4IT Value Chain

32 HPE Software supports all 3 roles with IT4IT-based solutions Broker Integrator Supplier The key roles map to the Reference Architecture through direct, indirect and associated capabilities across the value streams Our software solutions map to the Reference Architecture in such a way as to support end-to-end delivery of value to our customers in exactly the manner that the Value Streams are intended. Our Model Offices provide real, demonstrable examples of how the 3 roles are fulfilled through a series of Use Cases to show our customers the value which can be achieved through the adoption of IT4IT, irrespective of their existing technology landscape:

33 IT4IT Transformation Planning Offering Customer Journey Flowchart Customer Facing Deck (CFD) Agile Discovery (2-3 hours) Transformation Workshop Extended Agile Discovery (~1wk per value stream) Customer expression of interest Executive Briefing e.g. CIO Value of IT4IT seen? Brief Mgmt Team/ Senior Stakeholders Identify Current State & Next Steps Extend route to value for customer Detailed stakeholder interviews Map outputs to Capabilities Proceed to Transformation Planning? Discovery option Workshop Option Workshop Preparation (1-2 wks) Conduct Transformation Workshop Share Roadmap & Results with Stakeholders Capability Heatmap, & Value Roadmap Create Backlog for Agile Delivery Solution Delivery Transformation Roadmap Executive Briefing (free) Transformation Planning, 4-8 weeks, 2 FTE ($)

34 IT4IT & Other Standards

35 IT4IT vs ITIL Simple comparison IT4IT Prescriptive Architectural origins and focus. Structured consistently with TOGAF and Archimate. Value stream, capability, data, system views Solution orientation Fundamental focus on the end to end flow of IT value streams across IT capabilities. Specified as a conceptual data model for IT4IT and a set of functional system needed to maintain the data model Mutually exclusive and comprehensive, rigorously avoiding ambiguity and overlap in its architectural catalogs Precise representation of data and integration patterns in complex IT management domain Understanding of Agile and DevOps trends. Agile and iterative, open development process. ITIL Descriptive Primarily narrative Oriented to practitioner education rather than solution Oriented to deep discussion of individual silo functions. Beyond overall lifecycle, little emphasis on cross capability/function flows Ambiguous and overlapping terminology in places Limited utility to planners and architects attempting to integrate IT management infrastructure. Waterfall, top-down planning orientation. Long term history of proprietary ownership, not transparent. Multi-year revision cycle 41

36 Processes IT4IT Reference Implementations (vendor-specific) Model landscape graphical overview Plan Build Deliver Run COBIT IT4IT Reference Architecture Level 1 V.2.0 Systems Goals TOGAF, PRINCE2, PMI, ITIL 42 IT4IT is a trademark of The Open Group

37 The Open Group IT4IT standard to Run the Business of IT Original Consortium Shell Hewlett-Packard (IT & SW) Achmea MunichRe Accenture Pricewaterhouse Coopers University of South Florida AT&T Value Chain 9/2011 RA 0.5 (level 1) 8/2012 RA 1.0 (level 2) 1/2013 RA 1.2 (level 3) 3/2014 RA 1.3 (level 3) 10/2014 RA 2.0 (level 3) 7/2015 IT4IT 2.0 Std. 10/2015 Technical Standard ~5000 downloads ~800 organizations ~74 countries Pocket Guide Hot Seller ~600 downloads 02/2016

38 What makes IT4IT unique? Data-Driven Practical Needed IT standards are predominantly process (ITIL) or technology (NIST) focused. A data focus provides flexibility to support a wide variety of process and technology choices Vendor Agnostic Controlled by an independent standards organization (The Open Group) Eliminates concern over vendor lock-in / product agendas Built through collaboration of IT professionals and vendors. Designed for actual use and to be prescriptive versus being theoretical and left open to interpretation Enterprise-scale focus Proven Used successfully by/with customers to help guide transformation and to resolve tactical issues in IT execution. Customers get it and love it. There are useful standards in process and technology domains but none at the operating model and service lifecycle level which has limited progress in making IT an enabler of the digital enterprise Future proof Not designed around products or process frameworks Flexibility to accommodate for changes in technology, process, methodology or business models