IT4IT - Semantische Integrationsarchitektur für die IT - Semantische Integrationsarchitektur für...
-
Upload
nguyenngoc -
Category
Documents
-
view
213 -
download
0
Transcript of IT4IT - Semantische Integrationsarchitektur für die IT - Semantische Integrationsarchitektur für...
IT4IT - Semantische Integrationsarchitektur für die IT OpenGroup Fachgruppe IT4IT
Georg Bock, Senior Director of Strategy, HP Software
1. October 2015
IT-Governance und Strategisches
Informationsmanagement“ im Öffentlichen Sektor
IT4IT – How it started four years ago…
Requires a standard to drive market adoption
• 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.
Problem
Shell/HP partnership
• 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…).
Approach
IT4IT Customer consortium
Optimize the Business of IT
with quality Insight across the
complete Value Chain,
driving intelligent Decisions,
to deliver IT Services
Faster, Better, Cheaper,
and with Less Risk
Value
IT4IT TOG Forum
The problem – IT is changing and our customers are struggling
TRADITIONAL IT
(Technology provider) INDUSTRIALIZED IT
(Service provider)
IT as a DIGITAL ENTERPRISE ACCELERATOR
(Service broker)
• Project lifecycle governs
investment
• Process model controls workflow
• Project lifecycle governs investment
• Process model expanded
• Agile concepts introduced
• Service lifecycle governs investment
• Formal IT operating model to support
modern workflow (agile, bi-modal,
lean… )
• Prescriptive IT systems model to power
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
NEW
STYL
E NEW
TECH
The New Style of
IT
IT must create the foundation for The New Style of IT
Fluid IT
Fluid approach dealing with the pace of
digital business
Greater agility
Business outcome-centric
New workloads, apps,
and experiences
Shorter cycle times
Core IT
Maintaining the rock-solid foundation
for business execution
IT outcome-centric
Conventional workloads & apps
Longer cycle times
Lower cost
Gartner calls it
Bimodal IT
The IT operating model and reference architecture for the digital enterprise
Introducing IT4IT™
• Created by IT professionals to move to the
new style of IT
• Reviewed with 100+ HP customers and
contributes directly to revenue generation
• Most of the ITOM and ADM portfolio is
aligned
• “Reference Implementations” have been
created using HP Software products
• Aligns with and supports AOT messaging
• HP Software PSO organization using it as
the blueprint for engagements
• Industry standard (official Oct 2015)
managed by The Open Group
Two foundation components: “Reference Architecture” and “IT Operating Model”
What is IT4IT™ ?
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 …
• Methodology agnostic – customers can use agile, waterfall…
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)
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
Phases for each value stream
Transformation Values
8
S2P R2D R2F D2C
Functional
Excellence
Business Priorities/ Demand Service Broker/
Consumption
Predictability Quality of Service
Time to Market
Policy/Architecture
Compliance
Efficiency
End-to-End
Excellence
Data Consistency, Traceability, Financial Visibility, Risk
Visibility, Contracts/Suppliers
Landscape
Excellence
Collaboration, Continuous Improvement,
Mapping/Rationalization
Holistic End-to-End Perspective, Service Centricity, Consumption
Focus
IT4IT™ becomes an enabler of the transformation journey
Prescriptive automation model to
create foundation (authoritative system
of record and service model for IT
Mgmt)
Prescriptive integration model to
guide orchestration (SoR fabric,
SoE foundation)
A new operating model is
needed to realize the
transformation at enterprise
scale
REFERENCE ARCHITECTURE VALUE CHAIN OPERATING MODEL
TRADITIONAL IT
(Technology provider) INDUSTRIALIZED IT
(Service provider)
IT as a DIGITAL ENTERPRISE ACCELERATOR
(Service broker)
NEW
STYL
E NEW
TECH
2
3
Trend to move from own dev to COTS and from on-premise to cloud (cost, skill) drives the need for standards around service consumption model and multi-supplier mgmt. That complexity drives the need for regulatory and security compliance, insight directly supported by the IT4IT system of record based data integrity and traceability. History has shown a considerable large amount of failed projects requiring a more structured and integrated approach to portfolio mgmt grounded in data reality.
1
Why this is of interest for the public sector
10
4
The combination of the trends requires agile projects towards cloud and SaaS connect with legacy services, hence the need for Bimodal maturity supported by IT4IT.
Approach used to define the Reference Architecture Based on the IT Value Chain, shaped by customer scenarios
• Identification and modeling of key artifacts
• Provides key control points for consistency and traceability
• Describes end-to-end user stories connecting IT capabilities
• Use value streams to design cross-process flows
• Life cycle across conceptual, logical, and physical
• Continuous assessment, integration, delivery & operations Service
Functional
Information
• Smallest component that can stand on its own
• Integration based on input and output artifacts Technology
Service model artifacts tie together end-to-end relationships Delivering predictability, traceability, and repeatability
The service model – assuring IT service transparency
Business Enterprise Architect
PMO Users Developers Testers IT Engineer
IT Operations
Conceptual
Service
Model
• Demand
• Policy
• Portfolio
Logical
Service
Model
• IT project
• Requirement
• Release
Physical
Service
Model
• Event
• Incident
• Change
Request
to Fulfill
Detect
to Correct
Strategy
to Portfolio
Requirement
to Deploy
IT4IT™ reference architecture level 1
IT4IT™ is a trademark of The Open Group
Strategy to Portfolio
Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise Architecture Component
Service Portfolio
Component
Portfolio Demand
Component
Proposal Component
Policy Component
Release Composition Component
Project Component
Source Control Component
Service Design
Component
Requirement Component
Test Component
Defect Component
Build Component
Build Package Component
Offer Consumption Component
Usage Component
Chargeback/ Showback
Component
Request Rationalization
Component
Fulfillment Execution Component
Offer Management Component
Catalog Composition Component
Problem Component
Incident Component
Service Monitoring
Component
Change Control
Component
Diagnostics & Remediation Component
Configuration Management
Component
Event Component
Service Level Component
Functional
component
V2.0 snapshot is based upon
material developed by the
IT4IT™ Forum of The Open
Group™ Key functional component
Service model artifact
Key data artifact
Auxiliary data artifact
Entity relationship
IT4IT™ reference architecture level 1
IT4IT™ is a trademark of The Open Group
Strategy to Portfolio
Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise Architecture Component
Service Portfolio
Component
Portfolio Demand
Component
Proposal Component
Policy Component
Release Composition Component
Project Component
Source Control Component
Service Design
Component
Requirement Component
Test Component
Defect Component
Build Component
Build Package Component
Offer Consumption Component
Usage Component
Chargeback/ Showback
Component
Request Rationalization
Component
Fulfillment Execution Component
Offer Management Component
Catalog Composition Component
Problem Component
Incident Component
Service Monitoring
Component
Change Control
Component
Diagnostics & Remediation Component
Configuration Management
Component
Event Component
Service Level Component
IT Initiative
Source
Require- ment
Offer
Service Catalog
Entry
Test Case
Defect
Build Event Service Contract
Build Package
Service Architec-
ture
Policy
Scope Agree- ment
Portfolio Backlog
Item
Usage Record
Fulfill- ment
Request
Subscrip- tion
Charge- back
Contract
Request
Problem/ Known Error
Incident
Service Monitor
Run Book
RFC
Shopping Cart
Service Release Blueprint
Logical Service
Blueprint
Actual Service
CIs
Con- ceptual Service
Blueprint
Con- ceptual Service
Desired Service Model
Service Release
Artifact
Functional
component
V2.0 snapshot is based upon
material developed by the
IT4IT™ Forum of The Open
Group™ Key functional component
Service model artifact
Key data artifact
Auxiliary data artifact
Entity relationship
IT4IT™ reference architecture level 1
IT4IT™ is a trademark of The Open Group
Strategy to Portfolio
Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise Architecture Component
Service Portfolio
Component
Portfolio Demand
Component
Proposal Component
Policy Component
Release Composition Component
Project Component
Source Control Component
Service Design
Component
Requirement Component
Test Component
Defect Component
Build Component
Build Package Component
Offer Consumption Component
Usage Component
Chargeback/ Showback
Component
Request Rationalization
Component
Fulfillment Execution Component
Offer Management Component
Catalog Composition Component
Problem Component
Incident Component
Service Monitoring
Component
Change Control
Component
Diagnostics & Remediation Component
Configuration Management
Component
Event Component
Service Level Component
IT Initiative
Source
Require- ment
Offer
Service Catalog
Entry
Test Case
Defect
Build Event Service Contract
Build Package
Service Architec-
ture
Policy
Scope Agree- ment
Portfolio Backlog
Item
Usage Record
Fulfill- ment
Request
Subscrip- tion
Charge- back
Contract
Request
Problem/ Known Error
Incident
Service Monitor
Run Book
RFC
Shopping Cart
Service Release Blueprint
Logical Service
Blueprint
Actual Service
CIs
Con- ceptual Service
Blueprint
Con- ceptual Service
Desired Service Model
Service Release
Service
model
Artifact
Functional
component
V2.0 snapshot is based upon
material developed by the
IT4IT™ Forum of The Open
Group™ Key functional component
Service model artifact
Key data artifact
Auxiliary data artifact
Entity relationship
IT4IT™ reference architecture level 1
IT4IT™ is a trademark of The Open Group
Strategy to Portfolio
Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise Architecture Component
Service Portfolio
Component
Portfolio Demand
Component
Proposal Component
Policy Component
Release Composition Component
Project Component
Source Control Component
Service Design
Component
Requirement Component
Test Component
Defect Component
Build Component
Build Package Component
Offer Consumption Component
Usage Component
Chargeback/ Showback
Component
Request Rationalization
Component
Fulfillment Execution Component
Offer Management Component
Catalog Composition Component
Problem Component
Incident Component
Service Monitoring
Component
Change Control
Component
Diagnostics & Remediation Component
Configuration Management
Component
Event Component
Service Level Component
IT Initiative
Source
Require- ment
Offer
Service Catalog
Entry
Test Case
Defect
Build Event Service Contract
Build Package
Service Architec-
ture
Policy
Scope Agree- ment
Portfolio Backlog
Item
Usage Record
Fulfill- ment
Request
Subscrip- tion
Charge- back
Contract
Request
Problem/ Known Error
Incident
Service Monitor
Run Book
RFC
Shopping Cart
Service Release Blueprint
Logical Service
Blueprint
Actual Service
CIs
Con- ceptual Service
Blueprint
Con- ceptual Service
Desired Service Model
Service Release
Service
model
Entity
relationship
Artifact
Functional
component
V2.0 snapshot is based upon
material developed by the
IT4IT™ Forum of The Open
Group™ Key functional component
Service model artifact
Key data artifact
Auxiliary data artifact
Entity relationship
IT4IT™ Detect to Correct value stream level 2
Self Service Support
Defect Component
Requirement to Deploy
Defect
Portfolio Demand Component
Strategy to Portfolio
Portfolio Backlog
Item
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
Interaction
n:m
Desired Service Model
1:1
1:1
Usage Component
Request to Fulfill
Defect
1:11:1
Offer Consumption Component
Request to Fulfill
Status
Service Monitoring
Component
Incident
Component
Change Control
Component
Problem
Component
Diagnostics &
Remediation Comp.
Configuration
Management
Component
Event
Component
RFC
D2C V.2.0 May 14
th 2015
1:n
Request to Fulfill
Actual
Service
CIsFulfillment
Request
Service Contract
Service Level
Component
KPI
n:m
Release Composition Component
Requirementto Deploy
Service Release Blueprint
n:m
Offer Mgmt.Component
Service Contract (Template)Service
Contract(Template)
Service Level Status
Business / ITMeasurement Business Measurement
(Incident)
Request to Fulfill
1:1
Request Rationalization
Component
Request to Fulfill
Subscription
Service Contract
(Instance)
1:1
Service Model
Data Artifact – Key
Record fabric Integration
Entity relationship
Functional Component - Key
Functional Component - Auxiliary
Data Artifact – Auxiliary
Engagement dataflow
Current practice
This diagram was developed/published by the IT4IT™ Forum of
The Open Group™
n:m
Conversation
n:1
V2.0 Snapshot is based upon material developed by the IT4IT™ Forum of The Open Group
IT4IT™ is a trademark of The Open Group
Structure of IT4IT reference material
Guidance Normative
Reference
Architecture
Repository
Scenario
documentation
Normative documentation
- Framing docs
- Value Stream docs
- …
Informative
documentation
Complementary
White Papers Explorative
documentation
Company
adoption WP’s
IT4IT Forum reviewed
Not released under IT4IT
forum consensus
Functional Component
Value Stream
IT4IT Lifecycle
Artifact
SoR
Integration
Capability
Discipline
Scenario
Relationship
Attribute
Essential
Service
Service Backbone
Artifact
RF
C
RFC
Guidance documentation explain
possible use of the RA. It also
drives the evolution of the RA
More specifically the Scenario
documentation will drive the definition
of Essential Services and Artifact
Attributes
Complementary material drives
updates and creation of new guides
Driven by customer use
cases from a diverse
membership: Shell, AT&T, HP, PwC, Accenture,
Achmea, Munich RE, Microsoft, IBM,
CapGemini,
Tata Consultancy Services, Atos, BP
Oil, ExxonMobil, Huawei
Technologies,
Oracle, Origin Energy, Philips,
Raytheon, Logicalis, Architecting-the-
Enterprise, UMBRio, and more
www.opengroup.org/it4it
The Open Group IT4ITTM emerging open standard A prescription to manage the business of IT
Why did the IT4IT forum form?
• History of every new initiative reinventing IT foundations
• Issues are universal to IT – independent of industry, dev style, tools
What are its goals?
• End-to-end business service lifecycle for existing/future paradigms
• Become an IT industry standard architecture framework
How will it deliver value?
• Broad integration to deliver higher value than silos
• Architectural foundation for process models like ITIL and COBIT
Official launch Oct 19th in Edinburgh
2
3
Software is becoming the product, the innovation engine, the differentiator in the digitization of everything
IT needs to rise to the challenge: faster, more agile, close to the business
New Style of IT bridges both Core IT and Fluid IT with one reference architecture based on the IT Value Chain
1
The bottom line for IT
22
4 IT4IT is an emerging standard that drives Bimodal IT maturity, effectively connecting Core and Fluid IT