IT4IT™: managing the business of IT - Vivit-Germany„¢ is an IT integration model industry standard to run the business of IT in a digital enterprise IT Value Chain – Manage

IT4IT™: managing the business of ITusing a new reference architecturePeter Scheffczyk, IT4IT Customer Success Architect

27-Sep-2016

IT4IT™ is a trademark of The Open Group

The digital business transformation fundamentally changes IT

2

This shift is triggered by technology disruptions(e.g. cloud, mobility…) and can be realized by transitioning “people, process and technology.” A prescriptive recipe for IT will provide consistency to the journey.

This shift is driven by business disruptions (e.g. digital enterprise) and is forcing a new way of running IT. The journey requires transformation—a new collaborative culture, structure (operating model) along with the prescriptive design guide for service brokering in a multi-supplier environment.

Traditional IT(Technology provider)

Plan

Build

Run

Industrialized IT(Service provider)

Plan Build

DeliverRunNew Tech.

IT as a digital enterprise Accelerator (Service broker)

Plan Source

OfferManage

New Style

D2CR2FR2DS2P

IT4IT™ is an IT integration model industry standardto run the business of IT in a digital enterprise

IT Value Chain

– Manage IT as a value chain– It’s about the end user consumption experience – It’s not about the technology!

IT Reference Architecture

– Tightly manage the data and functions across the service life cycle

– This is an industry first!

3

“normative”“guidance”describes the structure of IT management prescribes the functional & information architecture


D2CR2FR2DS2P

Background and journey to The Open Group IT4IT™ standard

4

FallThe Open Group launches the IT4IT Forum

Year roundERP4IT consortium attracts enterprise customers, partners and vendors to contribute to v 1.0

FallHP hosts 1st ever ERP4IT consortium offsite

SpringTOG releasesIT4IT People Certification

2012 2013 2014 2015 2016

>6000 downloads of the standard

opengroup.org/it4it

FallThe Open Group releases theIT4IT Reference Architecturestandard to thepublic


IT4IT Value Chain

Requirementto

Deploy

Strategyto

Portfolio

Requestto

Fulfill

Detectto

Correct

Plan Build Deliver Run

NextIT4IT Reference Architecture standard v2.1• L3 attributes

for incident• ITFM and ITAM

integration

>15k downloads of the standard

D2CR2FR2DS2P

IT use cases

The need for IT4IT™IT must effectively deliver digital business outcomes

5

IT use cases

Many un-aligned Software Products

ToFromPlan Build Deliver Run

IT4ITsimplifies

IT solutions


IT4IT aligned Software Solutions

D2CR2FR2DS2P

Efficiency&

AgilityFinance & Assets

Intelligence & Reporting

Resource & Project

Governance, Risk and Compliance

Sourcing & Vendor

IT V

alue

Cha

in

Plan Build Deliver Run

Leveraging business value chain success in ITDesigned by customer like you since 2012 using real world use cases

Based on Michael Porter’s value chain methodology and lean manufacturing value stream concepts

6

Reference Architecture

D2CR2FR2DS2P

Value Streams – Martin– Lean / 6-sigma concepts– Multi-Process Oriented– Customer focused results

Value Chains – Porter– Competitive Analysis– Strategic Concepts– Value Creation– Activity cost to profit

margin analysis

Meet the IT value streams

7

End-to-end integrated Reference Architecture

Proactively detect issues

and take actions to correct them.

Run

Define your strategy to balance and broker your portfolio.

Plan

Prioritize every requirement to build/source the

best services and deploy them.

Build

Handle each request by

streamlining the process

to fulfill it.

Deliver

D2CR2FR2DS2P

Yourobjective

IT4ITprescription

Four value streams interconnected through the service model

8

Service life cycle—on a repeatable, predictable, coherent and future safe reference architecture

Strategy to Portfolio

– Align strategy– Rationalize

portfolio– Prioritize backlog– Manage

investment

Requirement to Deploy

– Plan & design– Develop– Test– Deploy

Request to Fulfill

– Define & publish– Subscribe– Fulfill– Measure

Detect to Correct

– Detect– Diagnose– Change– Resolve

D2CR2FR2DS2P

The service model

9

Conceptual Service Model

– Demand– Policy– Portfolio

Logical Service Model

– IT project– Requirement– Release

PhysicalService Model

– Event– Incident– Change

The service model – assuring IT service transparency

Detectto Correct

Requestto Fulfill

Requirementto Deploy

Strategyto Portfolio

Business PMO IT EngineerEnterprise Architect

Developers Testers IT Operations Users

D2CR2FR2DS2P

IT4IT™ reference architecture level 1

10

PolicyComponent

RequirementComponent

TestComponent

Offer Consumption Component ProblemComponent

Incident Component

ProposalComponent

Source Control

Component

BuildComponent

Offer ManagementComponent

Request Rationalization

Component

Chargeback/Showback

Component

Service LevelComponent

Event Component

PortfolioDemand

Component

ProjectComponent

Build Package

Component

CatalogCompositionComponent

Change Control

Component

UsageComponent

Diagnostics &RemediationComponent

Service Monitoring

Component

Enterprise Architecture Component

DefectComponent

ServicePortfolio

Component

ServiceDesign

Component

ReleaseCompositionComponent

Configuration Management

Component

Fulfillment Execution

Component

Strategy toPortfolio Requirement to Deploy Request to Fulfill Detect to Correct


Auxiliary data objectKey data objectService model object

Entity relationshipKey functional component

This diagram is based on material developed by the IT4IT™ Forum of The Open Group – Oct 2015

D2CR2FR2DS2P


11

PolicyComponent


TestComponent


Incident Component

ProposalComponent

Source Control

Component

BuildComponent



Component

Chargeback/Showback

Component


Event Component

PortfolioDemand

Component

ProjectComponent

Build Package

Component


Change Control

Component

UsageComponent


Service Monitoring

Component


DefectComponent

ServicePortfolio

Component

ServiceDesign

Component



Component


Component

Policy Require-ment

TestCase

Problem/KnownError

Incident

ScopeAgree-ment

SourceCharge-

backContract

Build OfferSubscrip-

tion

ServiceContract Event

PortfolioBacklog

Item

ITInitiative

BuildPackage

ServiceCatalog

Entry

RFC

UsageRecord

RunBook

ServiceMonitor

ServiceArchitec-

tureDefect

Request

Fulfill-ment

Request

ShoppingCart

Con-ceptualService

LogicalService

Blueprint

ServiceReleaseBlueprint

ActualService

CIs

DesiredServiceModel

ServiceRelease

Con-ceptualService

Blueprint






D2CR2FR2DS2P


12

PolicyComponent


TestComponent


Incident Component

ProposalComponent

Source Control

Component

BuildComponent



Component

Chargeback/Showback

Component


Event Component

PortfolioDemand

Component

ProjectComponent

Build Package

Component


Change Control

Component

UsageComponent


Service Monitoring

Component


DefectComponent

ServicePortfolio

Component

ServiceDesign

Component



Component


Component

Policy Require-ment

TestCase

Problem/KnownError

Incident

ScopeAgree-ment

SourceCharge-

backContract


tion


PortfolioBacklog

Item

ITInitiative

BuildPackage

ServiceCatalog

Entry

RFC

UsageRecord

RunBook

ServiceMonitor

ServiceArchitec-

tureDefect

Request

Fulfill-ment

Request

ShoppingCart

Con-ceptualService

LogicalService

Blueprint


ActualService

CIs

DesiredServiceModel

ServiceRelease

Con-ceptualService

Blueprint






D2CR2FR2DS2P


13


Component

Service Monitoring

Component

Event Component

Incident Component

Change Control

Component



ProblemComponent

UsageComponent

Chargeback/Showback

Component


Component


Component



Offer Consumption Component


Build Package

Component

BuildComponent

TestComponent

DefectComponent

ServiceDesign

Component

ProjectComponent

Source Control

Component


ServicePortfolio

Component

PortfolioDemand

Component

ProposalComponent

PolicyComponent


Require-ment

TestCase

Problem/KnownError

Incident

SourceCharge-

backContract


tion


PortfolioBacklog

Item

ITInitiative

BuildPackage

ServiceCatalog

Entry

RFC

UsageRecord

RunBook

ServiceMonitor

Defect

Request

Fulfill-ment

Request

ShoppingCart

Con-ceptualService

LogicalService

Blueprint


ActualService

CIs

DesiredServiceModel

ServiceRelease

Con-ceptualService

Blueprint

ScopeAgree-ment

Policy

ServiceArchitec-

ture






D2CR2FR2DS2P

Detect to Correct

14

Phases for each value stream

15





investment



Request to Fulfill


Detect to Correct


D2C

Detect to Correct phases and activities

16

– 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

Detect Diagnose Change Resolve

D2C

IT4IT™ Detect to Correct reference architectureAnticipate and resolve business execution issues

17

ProblemComponent

Incident Component


Event Component

Change Control

Component


Service Monitoring

Component


Component

Problem/KnownError

Incident


RFC

RunBook

ServiceMonitor

ActualService

CIs

D2C


Deployed service monitors create events

Service monitors and events are linked to CIs

CIs are created through fulfillment and service discovery

Run books are tied to CIs and used in their context

After additional diagnostics some events get resolved through remediation, others turn into incidents

Monitoring data is used to evaluate and audit service levels

Every change is handled in a central, authoritative system of record

Incidents are created through: events, interaction with end users, and self service support and are linked to CIs

Run books are used for diagnosing and resolving incidents and problems

Knowledge items and run books are used for solving problems and documenting known errors

Unsolved problems lead to defects and backlog items in the portfolio demand

IT4IT™ Detect to Correct value stream level 2

18

Self Service Support

Defect Component


Defect

Portfolio Demand Component


Portfolio BacklogItem

IncidentEvent

Actual Service CIs

RFCService Monitor

1:n

1:n n:m

n:m

Problem, Known Error

n:m

n:m

n:m

Event Incident

RFC

RFC

Problem RFC

Incident

Request to Fulfill

Fulfillment Execution Comp.

PortfolioBacklog

Item

n:m

Usage

1:n

Runbook

Run book

Run book

n:m

Service DiscoveryActual Service CIs

Defect

Knowledge & Collaboration Component

Knowledge Item

n:m

1:n

1:n

Supportive Function

ServiceMonitor Knowledge ItemRun book

Interactionn:m

Desired Service Model

1:1

1:1

Usage Component

Request to Fulfill

Defect

1:11:1


Request to Fulfill

Status

Service Monitoring Component

Incident Component

Change Control Component

ProblemComponent

Diagnostics & Remediation Comp.

Configuration Management Component

Event Component

RFC

1:n

Request to Fulfill

Actual Service

CIsFulfillment Request

Service Contract

Service Level Component

KPI

n:m

Release Composition Component

Requirementto Deploy

Service Release Bluepr int

n:m

Offer Mgmt.Component

Service Contract (Template)ServiceContract

(Template)

Service Level Status

Business / ITMeasurement Business Measurement

(Incident)

Request to Fulfill

1:1


Component

Request to FulfillSubscription

Service Contract

(Instance)

1:1

n:m

Conversation

n:1

D2C


Entity RelationshipRecord Fabric IntegrationEngagement Data FlowCurrent Practice

Functional Component – KeyFunctional Component – Auxiliary

Service Model

Data Object – Key

Data Object – Auxiliary

This diagram is based on material developed by the IT4IT™ Forum of The Open Group – November 2015

Detect Diagnose Change Resolve

HPE Software product mapping – Detect to Correct

June 2016 19

HPE IT Business Analytics

HPE Ops Analytics

HPE Security Intelligence (ArcSight)

HPE Operations Orchestration

HPE Service Manager, Service Anywhere

HPE Business Service Management (APM + OMi)

D2C

HPE Universal CMDB, Universal Discovery

Reference Implementationusing Detect to Correct as an example

20

The HPE reference implementation program and its goalsMaking IT4IT real using the HPE SW portfolio

21

Prove that it works

Install and configure holistic environments in order to test end-to-end use cases.

Show how to do it

Provide prescription and best practices to the field and HPE customers.

Improve our solutions

Continuously assess the HPE SW solutions and their integrations and provide feedback to R&D.

Contribute to IT4IT

Provide real-life feedback for future versions of the IT4IT reference architecture.

D2CR2FR2DS2P

HPE reference implementation: Detect to CorrectInstantiate customer use cases aligned to IT4IT using the HPE SW portfolio

22

use case 2 Closed loop incident management

use case 3 Change and release control

IT service managementuse case 1 Product versions

– ALM 12.20, 12.21, 12.50– BSM 9.25, 9.26– Diag 9.26– NNMi 10.01, 10.10– OMW 9.0– Omi 10.01, 10.10– OO 10.21, 10.22, 10.50,

10.51– RC 9.21– SM 9.40, 9.41– UCMDB 10.20, 10.21,

10.22– SAW– RUM 9.25, 9.26– SiS 11.30, 11.31

Integration #’s

– 546 UCMDB-CA CMDB– 744 OMi –HP SIM– 701 OMi-Oracle

Enterprise Mgr.– 201 SM-SAP Solution Mgr– 459 UCMDB-BMC

Remedy– 545 UCMDB-Troux– 757 SM-SAW– 682 SM-ALM– 683 CDA-OMU– 673 BSM-OO– 619 SM-UCMDB– 498 RUM-BSM– 448 SA-UCMDB

…and many more

Discover more (use your HPE passport):D2C reference implementation information: https://softwaresupport.hpe.com/km/KM01887189

D2C specific reference implementation details: https://softwaresupport.hpe.com/km/KM02142369

D2C

IT4IT™ Detect to Correct HPE product mapping

23IT4IT™ is a trademark of The Open Group

D2C

HPE reference implementation: Detect to Correct

24

D2C

Data Collectors, Monitors

SM 9.40

BSM 9.25

SiteScopeBPM

OM L/U/W

#648 (W), #198 (U)

#337 Event to Incident

Ops Agents

#328 CIs & Relationship Sync

UD

Discovered CI Data& Topologies

UCMDB 10.20

OO 10.21

#811 Run-Book Invocation

#375, 408 Run-Book Invocation

#118Impact Analysis Based

on UCMDB Relationships & Dependencies

#122Update Ticket with Results

#403RFC Sync & Analysis

Change CalendarSuggested Timeframe

for RFCs

ALM 12.20

#682 Create Defect

#101 CIs & Relationships Sync

NNMi

Diag.

#679 (BSM), #810 (OMi)Downtime

#460

RUM

#498

OM SPIs SOM

CSA / CODAR 4.21

#797Monitoring automation

OperationsAnalytics

#705 CI collection (RTSM)#704 Events (OMi)

#789

ArcSightLogger

#686

#344 Events, #812 UI Launch

#157 NNMi-RUM

Monitors dataTo Ops

Analytics:#702, #703, #706, #720, #721, #725, #726, #832

#412

#858 Topology

SAW

#757ICE

#865 Event to IncidentOMi 10

#867Run-BookInvocation

#821 CIs & Relationship Sync

#381 Launch Business Service Impact Report#243, #245 Federated

Data: Incidents & RFCs

#808 Storage events

RC

#864CIs push

#131 Topology

IT4IT landing page at hpe.com/software/it4it and forum at hpe.com/forum/it4it

New public IT4IT web page– One stop shop– Customer examples

(Shell)– Relevant products and

services

New expert community– Engage in discussions– Get answers– Find information– Share your experience

25

D2CR2FR2DS2P

Questions?

26

IT4IT™ and ITIL, COBIT & Co.IT4IT, yet another industry standard?


IT4IT™: yet another IT industry standard?

– One of the top three asked questions when introducing IT4IT is:“We just had our whole organization ITIL trained and certified. Does IT4IT replace this? “How do I now explain to my management that we need ‘yet another standard’ in our IT?”

– How does IT4IT relate to other IT industry standards, such as ITIL, COBIT, TOGAF, PRINCE2,…?– IT4IT is based on value chains, a concept that is well understood in businesses (outside of IT)– IT4IT is end2end and not tied to specific views (audit/governance) or focusing on specific aspects only (service

management)– IT4IT is data driven, detailed and prescriptive and does not just name things or is descriptive– IT4IT complements other standards, it does not compete with or replace them!


Goals

Model landscape graphical overview

29

COBIT

IT4I

T R

efer

ence

Impl

emen

tatio

ns

(ven

dor-s

peci

fic)

DeliverPlan Build Run

ITILTOGAF, PRINCE2, PMI, …

Pro

cess

es

Systems

IT4IT Reference Architecture Level 1 V.2.0


Summary of the models

30

Plan/Build/Run IT Value Chain IT Infrastructure Library (ITIL V3) COBIT

ShortDescription

High Level Model of IT Manage-ment focused on organizational aspects – a cultural adoption by many organizations

Focus on the IT supply chain from user to provider – a global standard

Detailed process model for all processes needed to operate IT – a collection of best practices

Governance/management framework for Enterprise IT – a global standard

Coverage Spans from strategy to operations. Focused on Roles and Responsibilities

Model that integrates the infor-mation, system and governance perspectives to provide insight for decision making end-to-end across Plan, Build, Deliver, Run

Focusing on process view in detail, governance and systems view is covered only high level. Skewed to “Run” with shallow support for “Plan” and “Build”

Focus on governance and goals perspective end-to-end with underpinning high-level process framework

Advantages Easy to understand and widespread in the IT world.

Comprehensive, data-driven life cycle view and end-to-end view. Integrates with IT models like ITIL, COBIT, TOGAF, etc. Refines abstract models such as Plan/Build/Run

Widespread and implemented in the IT world. High level life cycle view

Goals cascade/alignment of business and IT goals. Compliance perspective. Often used by auditors and auditing companies as the underlying framework in the area of GRC

Dis-advantages

Too high level as a guide for ITSM as the process and systems view is missing. Encourages “waterfall” thinking and misses critical guidance on delivery and consumption aspects

Framework is in an early stage of its life cycle

No guidance on where the best practice processes meet the tools for real world execution. Financial management and supplier management is only covered in fractions

Provides guidance about what to do, less about how to do it. Limited coverage of information and systems perspectives. Too generic for complex, hybrid IT eco-systems and bi-modal IT


Thank [email protected]

31

Appendixslides on the other three value streams that were not covered in the presentation at the Vivit conference

32


33


34





investment



Request to Fulfill


Detect to Correct


S2P

Strategy to Portfolio phases and activities

35

– Define objectives– Align business and

IT roadmaps– Set up standards

and policies

– Enterprise architecture

– Service 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

Align Strategy Rationalize Portfolio Prioritize Backlog Manage Investment

S2P

IT4IT™ Strategy to Portfolio value stream level 2

36

Requirement Component


1:n

n:1

PortfolioBacklog

Item

Portfolio BacklogItem (rationalized/

Prioritized)

Competency(availability)

Assets(availability)

Policy

Portfolio Backlog Item

Policy

Requirement

1:n

ConceptualService

Blueprint

PortfolioBacklog

Item

Conceptual Service

Conceptual Service

Blueprint

n:m

Project Component

IT Initiative

Scope Agreement

1:n Scope Agreement

Service Design ComponentLogical Service

Blueprint1:n


Service Portfolio Component

n:m

Business Process

Portfolio Backlog Item

n:1Policy

Component

Proposal Component



IT Asset Management

BusinessStrategy

Labor Management

Problem Component

Problem, Known ErrorDetect to Correct

Service Architecture


n:m

1:1

Portfolio Backlog

Supportive Function

IT Investment Portfolio Component

ITFM Supportive Function

IT Budget

n:m

n:1

Cost Modeling Component

ITFM Supportive Function

IT Cost Modeln:1

S2P




Service Model

Data Object – Key



AlignStrategy

Rationalize Portfolio

PrioritizeBacklog

Manage Investment

HPE Project & Portfolio ManagementHPE Application Portfolio Management

HPE Enterprise Maps


HPE Software product mapping – Strategy to Portfolio

November 2015 37

S2P

HPE reference implementation: Strategy to PortfolioInstantiate customer use cases aligned to IT4IT using the HPE SW portfolio

38

use case 2 Translate strategic initiative into proposals

use case 3 Update architecture and service roadmaps

Service alignment to strategic initiativeuse case 1 Product versions

– PPM 9.31, 9.32– UCMDB 10.20, 10.21,

10.22– EM 2.0, 3.0

Integration #’s

– 370 Retrieve Service List (PPM – UCMDB)

– 730 Traceability between business objects, requirements and architecture (EM to PPM)

– 731 Align physical CIs to architecture elements (EM to UCMDB)

– 732 Align project and demand to architecture elements (EM to PPM)

– Data exchange between EM and 3rd party SparxEA

use case 4 Monitor compliance

S2P

Discover more (use your HPE passport):S2P reference implementation information: https://softwaresupport.hpe.com/km/KM01888066

S2P specific reference implementation details: https://softwaresupport.hpe.com/km/KM01888074

IT4IT™ Strategy to Portfolio HPE product mapping


S2P

HPE reference implementation: Strategy to Portfolio

40

S2P

EM

PPM

Demand

UCMDB

3rd Party:Sparx EA

#370 Retrieve Service List

3rd Party:SharePoint

Policy Content

#732Align PPM project and demand

to architecture elements

#731Align physical CIs

To architecture elements

#730Traceability between business

objectives, requirementsand architecture

As-is architecture

To-be architecture

EEM Devenvironment

UDCI Discovery

APM Project Portfolio


41


42





investment



Request to Fulfill


Detect to Correct


R2D

Requirement to Deploy phases and activities

43

– 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

Plan & Design Develop Test Deploy

R2D

IT4IT™ Requirement to Deploy value stream level 2

44


Strategy to PortfolioPortfolio Backlog Item

Proposal Component

Service Portfolio Component

Policy Component

Source Control Component

Problem Component

Detect to Correct

IT Initiative

Requirement

1:n

1:n

Source

1:n

Defect

1:n

RFC (Normal)

1:n

Service Design

Package

Policy

Defect

Defect1:n

n:m

RFC

n:m

Requirement Component

Test Case

Test Component

Incident Component

Detect to Correct


Conceptual ServiceBlueprint

Project Component Change ControlComponent

1:n 1:n 1:n

1:1

Scope Agreement

1:n 1:1Logical Service Blueprint

Service Release

Release Package

Scope Agreement


Defect Component

Problem, Known Error

1:1

n:1

1:n

Defect

1:1

Incident

IT Initiative

Requirement

Defect

1:1

Service Design Component

Catalog Composition Component

Service Catalog Entry

Request to Fulfill

Fulfillment Request

Release Package

ReleaseComposition Comp.


Service Catalog Entry (Unbound)

1:n

RFC

1:n

Service Release Blueprint

Service Contract (Template)

n:m

Fulfillment Execution Comp.


Request to Fulfill

Fulfillment Request

1:n

Build Component

Build

Build PackageComponent

Build Package

n:1n:m

n:m

Detect to Correct

Service Contract

1:n

n:m

1:n


R2D




Service Model

Data Object – Key



Plan & Design Develop Test Deploy

HPE Software product mapping – Requirement to Deploy

November 2015 45

R2D

HPE Service Manager, Service AnywhereHPE Unified Functional

Testing


HPE Application Lifecycle Management (Quality Center)

HPE Agile Manager

HPE LoadRunner, Performance Center,

StormRunner

HPE Application Lifecycle Intelligence

HPE Mobile Center

HPE Service Virtualization, Network Virtualization

HPE Application Security (Fortify)

HPE Codar

HPE Cloud Service Automation

HPE reference implementation: Requirement to DeployInstantiate customer use cases aligned to IT4IT using the HPE SW portfolio

46

use case 2 Build software

use case 3 Deploy software to dev/test

End-to-end service deliveryuse case 1 Product versions

– PPM 9.30– SM 9.32– UCMDB 10.10, 10.20– Codar 1.0, 1.5– CSA 4.20– ALM 12.01– AGM on SaaS– UFT 12.01, 12.02– OO 10.10, 10.20, 10.21– BSM 9.24, 9.25– BPM 9.25– LR 12.02– PC 12.01– SiS 11.30

Integration #’s

– 19 Application Lifecycle Management - RFC to Requirement/Defect (PPM - QC)

– 101 CI sync and actual state federation (UCMDB to SM)

– 255 Create RFC from work plan,PPM-SM

– 328 UCMDB-BSM Platform synchronization (UCMDB – BSM)

– 370 Retrieve Service List (PPM – UCMDB)

– 408 Launch OO Flow from SM RFC

– 482 CSA Direct Integration to Operations Orchestration

– 596 Enabling Performance Center capabilities in HP ALM (ALM – PC)

– 633 View Project Quality (PPM -ALM)

– 634 Agile Integration Solution (PPM - Agile Manager)

…and more

use case 4 Deploy software to staging/production

R2D

Discover more (use your HPE passport):R2D reference implementation information: https://softwaresupport.hpe.com/km/KM01888068

R2D specific reference implementation details: https://softwaresupport.hpe.com/km/KM01888076

IT4IT™ Requirement to Deploy HPE product mapping


R2D

HPE reference implementation: Requirement to Deploy

48

R2D

AgM

OO UCMDB

#633View Project

Quality

#19 Request (Demand) to Requirement/Defect (MAC)

#634View

ReleaseInfo

3rd Party:Eclips,

Jenkins, Git#255

Create RFC from Work Plan

#370Retrieve Service

List

#101CI Synch

#408Launch Flow

from RFC

#751, #758Releases,

Requirements and Defects synch

#682Problem/Defect

Exchange

UFT

ALI

Codar

Deploy Build From Jenkins

Site Scope

Test Execution from Jenkins

BSM

PC/LR

BPM

#777Script

Execution

CSA

#610 PAL

#749CI & Relationships

#482Launch

OO Flows

OO Engine

#328CI & Relationships

IBM Rational (ClearQuest, RequisitePro)

SAP SolManMicrosoft TFS

NV

#714, #717NV for PC, LR

#707SV in UFT

SV

#662 Load testing

#596 PC capabilities

#597, #586SV in PC,LR

#678Req Synch

#47, #48Req/Defect

Synch

#669Req

Synch

#670Defect Synch

#719Test Exe.

Mobile Center

#664 API and

GUI testing

#778

#779 #780

Sprinter For Mobile

Fortify

Storm Runner

ALM

Req

DefectALI Test

SprinterRelease

PPMProject

#685OO content for Fortify

#762BPCA

#708Share SV resources

In ALM

Code Issues

#794Integration

Pack (via OO)

SM Change

Incident KnowledgeProblem

Request to Fulfill

49


50





investment



Request to Fulfill


Detect to Correct


R2F

Request to Fulfill phases and activities

51

– 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

– Service usage measurement

– Chargeback/showback

– Cost transparency– Surveys and ratings

Define & Publish Subscribe Fulfill Measure

R2F

IT4IT™ Request to Fulfill value stream level 2

52

Project Component

Actual Service CIsDetect to Correct

Configuration Management Component

ReleaseComposition Component

1:n

Service Release Blueprint


Request Rationalization Component

Usage Record

Chargeback Contract

Bill/Invoice

Service Catalog Entry (Unbound)

Usage

Usage

Subscription

1:n

Request

Offer Catalog

n:m

Offer

User Profile

n:m

1:1

Shopping Cart

Chargeback Contract

n:m

Fulfillment Request

1:n

1:n

Subscription

Service Monitor

Offer Mgmt. Component

Request

Knowledge Item

Incident

Status1:n

Service Catalog Entry

n:m

Fulfillment ExecutionComponent

RFC

1:1

Detect to Correct

Catalog Composition Component

UsageComponent

Chargeback / Showback

Component

RFC Request

Change Control Component

Composite/Compound Request

IT Supplier (External to IT)

1:n

Engagement Experience Portal

1:n

1:1

IT Financial Management

Service MonitoringComponent

FulfillmentEngine & Deploy/Provision Systems

Detect to Correct

Knowledge & Collaboration

Supportive Function Detect to Correct

Incident Component



n:m

1:n

Request

1:n

n:1

Service Catalog Entry (Bound)

Actual Service

CIs1:nRelease Package

IT Asset Management

Supportive Function

FulfillmentRequest


Supportive Function


Detect to Correct

ServiceContract

(Template)

ServiceLevelStatus

Service Contract

1:1Service Contract (Instance)

Self Service SupportKnowledge Collaboration

Conversation

Service Catalog

Shopping Cart

R2F


Functional Component – Key

Functional Component – Auxiliary

Service Model

Data Object – Key

Data Object – AuxiliaryEntity RelationshipRecord Fabric IntegrationEngagement Data FlowCurrent Practice


Define & Publish

Subscribe Fulfill Measure

HPE Software product mapping – Request to Fulfill

November 2015 53

HPE Operations Orchestration


HPE Propel

HPE Cloud Service Automation, Codar

HPE DB, Middleware & Application Automation

HPE Network, Storage & Server Automation

HPE Asset Manager

R2F

HPE Service Manager, Service Anywhere

HPE reference implementation: Request to FulfillInstantiate customer use cases aligned to IT4IT using the HPE SW portfolio

54

use case 2 Order new employee laptop

use case 3 Employee onboarding bundle

Request and fulfill SaaS online business serviceuse case 1 Product versions

– HP Propel 1.10, 1.11– CSA 4.10, 4.20– SM 9.32, ... , 9.40– UCMDB 10.01– OO 10.10, 10.11, 10.20– AM 9.40, 9.41, 9.50– Connect-IT 9.50– SA 10.01, 10.02, 10.10,

10.20, 10.21– Database & Middleware

Automation 10.21, 10.22, 10.30

Integration #’s

– 101 UCMDB-SM– 122 OO-SM– 247 OO-SA– 307 AM-UCMDB– 375 SM-OO– 408 SM-OO– 415 AM-SM– 482 CSA-OO– 616 UCMDB-AM– 676 AM-CSA– 696 DMA-SA– 715 OO-DMA– 765 Propel-SM

R2F

Discover more (use your HPE passport):R2F reference implementation information: https://softwaresupport.hpe.com/km/KM01888064

R2F specific reference implementation details: https://softwaresupport.hpe.com/km/KM01888078

IT4IT™ Request to Fulfill HPE product mapping


R2F

HPE reference implementation: Request to Fulfill

56

R2F

Propel

SM

UD

#122Create/Update RFC

#415- PPT Sync

#101 CIs & Relationships Sync

KM

Propel Marketplace Portal (CCUE)

Incident

CSA

#616CI Push

#307CI Population

UCMDBCIs & Relationships(via OO)

AM

SA

OO

Cloud Service Requests

Req. M.

Expose Knowledge Search

ChM

#247Launch SA Automation

#482Launch

OO Flows

#676Cloud Billing Management

(Subscription Related Information)

IM#375, 408 Run-Book Invocation

SSKSST

Connect-It#676

Cloud Billing Management(Subscription Related Information)

Cat. M.

Propel SX

Asset/License Request

Incident

Propel Aggregated Catalog

Aggregate CSA Catalog

Aggregate SM Catalog

Expose Aggregated

Catalog

ITSM Service Requests

DMA

#715Launch DMAAutomation

#696DB & Middleware

Provisioning via SA

Offer Catalog

All Service/Subscription Requests & Status Updates

Discovered CI Data & Topologies

Documents

IT4IT™: managing the business of IT - Vivit-Germany„¢ is an IT integration model industry standard to run the business of IT in a digital enterprise IT Value Chain – Manage