Professional Documents
Culture Documents
Charles Betz
Speaker bio
Charlie Betz is Director of Strategy and Innovation (aka Chief Architect) for a major US telecom and ecommerce
hosting provider, currently assigned to large enterprises in the retail and healthcare sectors.
Representative to the IT4IT Strategy Board, a new Open Group standard for the business of IT
Previously he was Research Director for IT Portfolio Management at Enterprise Management Associates. He spent 6
years at Wells Fargo as VP and Enterprise Architect for IT Portfolio Management and Systems Management. He has
held architect and application manager positions for Best Buy, Target, and Accenture, specializing in IT
management.
He is sole author of The Architecture of IT Management (formerly Architecture and Patterns for IT) and co-author of
several works with Lean collaborators and for ISACAs COBIT.
Why IT4IT?
Overview and positioning of IT4IT
IT4IT governance
IT4IT content
IT4IT Agile workstream
Getting involved
3
Who is this man
and what does he want?
Complete transparency
Complete traceability
What are the DETAILED INVENTORY and FINANCIAL COSTS of
the IT systems supporting a given BUSINESS CAPABILITY?
Whats the BUSINESS PURPOSE of this byte on this disk on
this array in this data center?
What are the BUSINESS CONSEQUENCES of this component
failing?
Metadata
& IT
11/18/2014 Service5
Manageme
Demand/portfolio perspective
7
Build perspective
What is the current status of
the software development lifecycle
across & within projects?
What major changes are upcoming?
What is the current overall pace of change in my systems?
Am I working to minimize large, risky batches of work?
I need to upgrade service or system X
What is its complete bill of materials?
Top to bottom interdependencies & their nature?
What systems use data element Y?
What does it mean?
What is its lineage?
What security/privacy/retention policies apply to it?
10
Solving problems that every enterprise has
Building a reference architecture that allows IT to be a business innovation center
Why create a customer consortium
History of every new initiative reinventing IT foundations
Issues are industry independent
Policy Requirement Defect Problem Incident
Management Management Management Management Management
Proposal
Management
(Investment)
IT Contract
Project
Delivery
Management
IT Project
Test
Management
Test Case
Catalog
Management
Offer
Service Catalog
Subscription
Management
Subscription
Billing &
Chargeback
Chargeback
Record
Diagnostics &
Remediation
Runbook
Event
Management
Event
What and next steps
Entry
Business
Architecture
Management
Business
Architecture
Demand
Management
Demand
Service
Development
Management
Source
Build
Management
Deployment
Package
Request &
Routing
Management
Fulfillment
Request
Usage
Management
Usage Record
Service
Monitoring
Service
Monitor
End-to-end business service lifecycle for existing/future paradigms
IT
Architecture
Management
Service
Portfolio
Management
Service
Design
Management
Design Package
Release
Management
Release Package
Deployment
Management
Service
Change
Management
Configuration
Management
Open standardization process
Release Desired
Conceptual Conceptual Service CIs
Service Blueprint Logical Service Blueprint RFC
IT Architecture Blueprint Service Release Actual Service CIs
IT Value Chain
Proposal Project Test Cat al og Subscript ion Bil l ing & Di agnost ics & Event
Management Del i very Management Management Management Chargeback R emedi at ion Management
(Invest ment ) Management Of f er
IT Cont ract IT Pr oject Test Case Subscr ipt i on Char geback Runbook Event
Servi ce Cat al og Record
Ent ry
Business Demand Ser vice Buil d Request & U sage Ser vice
Archi t ect ure Management Devel opment Management Rout ing Management Moni t oring
Management Management Management
Busi ness Demand Sour ce Depl oyment Ful f il l ment Usage Record Servi ce
Ar chit ect ure Pack age Request M onit or
IT Ser vice Ser vice Rel ease Depl oyment Change Conf igurat ion
Archi t ect ure Por t f ol io D esi gn Management Management Management Management
Management Management Management
Design Package Rel ease Package Servi ce
Rel ease Desir ed
Concept ual Concept ual Servi ce CIs
Servi ce Bl uepr int Logi cal S er vice Bl uepr int RFC
IT Ar chit ect ure Bl uepr int Servi ce Rel ease Act ual Ser vice CIs
Service
Architecture
Enterprise
Architecture
IT4IT Reference Architecture v1.2
Key Functional Components and underpinning Key Artifacts
Knowledge &
Policy Requirement Defect Shop / Buy / Pay / Manage Problem Incident
Collaboration
Shopping
Cart
Knowledge Problem /
Policy Requirement Defect Incident
Item Known Error
Usage Service
Demand Source Build Run Book
Record Monitor
Strategy to
Requirement to Deploy Request to Fulfill Detect to Correct
Portfolio
Detect to Correct functional model RFC
RFC
Service
Event Event Incident Incident Problem Problem RFC Change Control
Monitoring
Interaction
Problem,
Service n:m Incident Known Error
Monitor Event
1:n n:m n:m 1:n RFC
n:m
1:n Run book
Service n:m
Monitor Service Discovery Knowledge Item
CI Run book Run book
V.1.2, Mar 20th 2014
n:m This wor k is based upon material
Actual developed and publ ished by t he
Fulfillment Execution
Desired Service Diagnostics & Knowledge & Collaboration IT4IT Consort ium
Fulfillment Service CIs CMDB Remediation Functional Component - Key
Request Model n:m Functional Component - Auxiliary
1:n 1:1 n:m Runbook
Knowledge Conversation Service Model
Actual Service CIs Item Data Artifact Key
Request to Fulfill Request to Fulfill Data Artifact Auxiliary
CMMI
SAFe
Narrative
Conceptual
ANSI 09001
TOGAF
ITIL
GAAP
COBIT
Platform
VCOR
SCOR
Degree of Prescriptiveness
independent
Logical
ANSI/ISA-95
Key detail
where
IT4IT
necessary
eTOM
BIAN
NRF ARTS
ACORD
Syntactically
precise
HR-XML
Interoperable
MDDL
XBRL
EDI
Exhaustive
detail (e.g. all
conceivable
data attributes)
Topic Scope
Supply Chain
Finance
HR
Marketing
Retail
Insurance
IT
Banking
Telco
Manufacturing
Multi-industry
Archi
Mate
ITIL
TOGAF
IT4IT ITIL
Prescriptive Descriptive
Architectural origins and focus. Structured consistently with TOGAF and Primarily narrative
Archimate. Value stream, capability, data, system views
Fundamental focus on the end to end flow of IT value streams across IT Oriented to deep discussion of individual silo functions. Beyond overall
capabilities. Specified as a conceptual data model for IT4IT and a set of lifecycle, little emphasis on cross capability/function flows
functional system needed to maintain the data model
Mutually exclusive and comprehensive, rigorously avoiding ambiguity Ambiguous and overlapping terminology in places
and overlap in its architectural catalogs
Precise representation of data and integration patterns in complex IT Limited utility to planners and architects attempting to integrate IT
management domain management infrastructure.
When standardized, will have agile and iterative, open development Long term history of proprietary ownership, not transparent. Multi-year
process. revision cycle
Key point: IT4IT does not specify capabilities
18
IT4IT Governance
Shell Munich Re
HP Achmea
British Petroleum Capgemini
PwC AT&T
Univ. S. Florida Logicalis
Accenture UMBRiO
Origin Energy Atos
Microsoft Arismore
Agile Enablement Workstream
IT4IT Consortium
22
Positioning
Service Development Component (Source Build Management Component Release Design Component
Control)
Build package
Artifact reconciliation
Stores package
Defect Management Component
Test Management Component
26
Continuous deployment w/rollback
application Scenario 4
Rollback Rollback
authorized Rollback
requested
invoked
Event Management
Incident Management Change Control Component
Component Deployment Management
Component
Systems
Business rule
Alert Prioritization
management
Aggregation Tracking
Platform Specific
Svcs
Event
Target System
27
KANBAN & QUEUING
WHAT is Kanban?
In manufacturing, a visible
signal (e.g. return of an
empty parts bin) that a
work area needs to pull
more work.
In IT services development
and operations, an
adaptable, shared visual
model that makes demand
and supply explicit
The challenge
Incident
A given teams Kanban board SR
may encompass Requirements, Work Order
Changes, Service Requests,
TODO DOING DONE
Work Orders, and even
Incidents and Problems.
Issue
Change
Release
Kanban impact on IT4IT
33
How do I get involved?
35
ADDITIONAL MATERIAL
36
IT4IT Core Metamodel
Level 3: Vendor independent Architecture
*
Value Stream
*
* Attribute
* * 1
Capability * * 1 1..*
Functional Component Artifact
Discipline
2 2
1 1 *
1
1..* Relationship
1
FC Function
1..*
* * *
1..*
* 0..1
* Essential * * SoR
Scenario
Service Integration
Use cases identified and together with SoR Integrations drive identification of Service Endpoints / Essential services for IT
Attributes needed for SoR integrations and Use cases are indentified
The Class model is mapped to ArchiMate concepts and the IT4IT specification is capture in ArchiMate
Class model for IT4IT Reference Architecture
Level 3: ArchiMate Notation Guide
L3 Element Representation L3 Element Representation
Component
IT4IT Content
Value Reference
Why it Deeper High level Detailed
Stream Overview KPIs Components Architecture
matters dive flow Architecture
Context Context
Strategy to Portfolio value stream
IT Value Chain
Plan Build Deliver Run Efficiency
Reference Architecture &
Finance & assets Agility
Sourcing & vendor
Intelligence & reporting
Resource & project
Governance, risk and compliance
% of new investment
Innovation vs maintenance
Demand By source and type
% satisfied customers
Capital % CapEx vs OpEx Usage per service
Deficiencies in security
Costs % planned vs actual Compliance policies and standards
Exploring Strategy to Portfolio
Enterprise Service
Demand Proposal
Architecture Portfolio
Reference Architecture
Strategy to Portfolio Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise
Architecture
Ser vice
Architectur e
Knowledge &
Policy Requirement Defect Shop / Buy / Pay / Manage Problem Incident
Shopping
Collaboration
Functional
Cart
Poli cy Requirement Defect
Kno wle dge
Item
Pro blem/
Kno wn Err or
Inci dent component
Entity relationship
Record fabric Integration
Engagement dataflow
Current practice
Requirement to Deploy value stream
IT Value Chain
Plan Build Deliver Run Efficiency
Reference Architecture &
Finance & assets Agility
Sourcing & vendor
Intelligence & reporting
Resource & project
Governance, risk and compliance
% of project tasks or
On time cycles on time Change % of emergency changes
Exploring Requirement to Deploy
Service Service
Test Fulfillment
Design Development
Build
Requirements
Release Design
Reference Architecture
Strategy to Portfolio Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise
Architecture
Ser vice
Architectur e
Knowledge &
Policy Requirement Defect Shop / Buy / Pay / Manage Problem Incident
Shopping
Collaboration
Functional
Cart
Poli cy Requirement Defect
Kno wle dge
Item
Pro blem/
Kno wn Err or
Inci dent component
IT Project
IT Contract Source Build RFC
1:n 1:n
Strategy to Portfolio
1:n n:m
IT Project n:m
RFC
Release Package
Service Design 1:n
Release
Fulfillment Execution
Service Portfolio Service Release Fulfillment
Package Desired Service 1:1
Design 1:1 1:1 Model Request
Conceptual Service Package Design
Blueprint
1:n 1:n 1:n 1:n 1:n
Logical Service Service Service
Strategy to Portfolio Blueprint Release Release Blueprint Request to Fulfill
1:n
n:m
Request to Fulfill
Requirements Test Defect
Defect
Policy
Policy n:m 1:n 1:n 1:1
Requirement Test Case Defect
Strategy to Portfolio V.1.2, Mar 20 th 2014
This wor k is based upon material
developed and publ ished by t he
1:1
Demand IT4IT Consort ium
Entity relationship
Record fabric Integration
Engagement dataflow
Current practice
Request to Fulfill value stream
IT Value Chain
Plan Build Deliver Run Efficiency
Reference Architecture &
Finance & assets Agility
Sourcing & vendor
Intelligence & reporting
Resource & project
Governance, risk and compliance
% self-service % of subscriptions
Costs requests
Satisfaction requiring an incident
Exploring Request to Fulfill
Chargeback /
Showback
Reference Architecture
Strategy to Portfolio Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise
Architecture
Ser vice
Architectur e
Knowledge &
Policy Requirement Defect Shop / Buy / Pay / Manage Problem Incident
Shopping
Collaboration
Functional
Cart
Poli cy Requirement Defect
Kno wle dge
Item
Pro blem/
Kno wn Err or
Inci dent component
Knowledge &
Self Service
Shopping Cart Collaboration Knowledge
Shop / Buy / Pay / Manage Item Support
n:m
1:n
Conversation
Composite/Compound
n:m 1:n Request
Service Catalog
V.1.2, Mar 20th 2014
Entry (Unbound) This wor k is based upon material
developed and publ ished by t he
Release IT4IT Consort ium
Package 1:1 Service
1:1 Functional Component - Key
Actual Monitor
1:n Release Design Service Functional Component - Auxiliary
1:n Release Request Usage Incident
1:n RFC CIs Service Model
Service Package
Service Release Data Artifact Key
Release Blueprint Data Artifact Auxiliary
1:n Bill/Invoice
Requirement to Deploy Entity relationship
1:n Record fabric Integration
Engagement dataflow
Request
Current practice
Request 1:1
IT Value Chain
Plan Build Deliver Run Efficiency
Reference Architecture &
Finance & assets Agility
Sourcing & vendor
Intelligence & reporting
Resource & project
Governance, risk and compliance
% of automated event
Costs & incident resolutions
Satisfaction % of first call resolution
Exploring Detect to Correct
Service
Event Incident Remediation
Monitoring
Configuration
Reference Architecture
Strategy to Portfolio Requirement to Deploy Request to Fulfill Detect to Correct
Enterprise
Architecture
Ser vice
Architectur e
Knowledge &
Policy Requirement Defect Shop / Buy / Pay / Manage Problem Incident
Shopping
Collaboration
Functional
Cart
Poli cy Requirement Defect
Kno wle dge
Item
Pro blem/
Kno wn Err or
Inci dent component
Service
Event Event Incident Incident Problem Problem RFC Change Control
Monitoring
Interaction
Problem,
Service n:m Incident Known Error
Monitor Event
1:n n:m n:m 1:n RFC
n:m
1:n Run book
Service n:m
Monitor Service Discovery Knowledge Item
CI Run book Run book
V.1.2, Mar 20th 2014
n:m This wor k is based upon material
Actual developed and publ ished by t he
Fulfillment Execution
Desired Service Diagnostics & Knowledge & Collaboration IT4IT Consort ium
Fulfillment Service CIs CMDB Remediation Functional Component - Key
Request Model n:m Functional Component - Auxiliary
1:n 1:1 n:m Runbook
Knowledge Conversation Service Model
Actual Service CIs Item Data Artifact Key
Request to Fulfill Request to Fulfill Data Artifact Auxiliary