target state architecture tsa
DESCRIPTION
Target State Architecture TSA. Presented by Dawn Michels Enterprise Information Architect Andersen Corporation Feb 15, 2006 For Dama Minnesota. What is a TSA?. - PowerPoint PPT PresentationTRANSCRIPT
Target State Architecture
TSAPresented by Dawn MichelsEnterprise Information ArchitectAndersen CorporationFeb 15, 2006For Dama Minnesota
What is a TSA? A TSA (Target State Architecture) is a tool or
method for the IT and Business functions of a company to work in concert to insure that business needs are addressed using the capabilities of IT most effectively.
In addition it is written in terms that resonates with the business and is validated and approved by key stakeholders of both parts of the organization.
Our approach was to… Assess
Understand and assess key business strategies and business unit plans
Evaluate current business models, high level-gaps between business process and technology offerings
Identify IT organizational implications Organize
Develop principles and values Develop specific list of architectures
Document Identify specific opportunities & pain points Document current and target states of specific
architectures Prioritize
Prioritize business needs/intersection with IT capabilities
List specific initiatives that would move us in the right direction
Who Participated Executive Leadership Business Management Sr. IT Management Enterprise Architects Business/IT Liaisons
Assess The Enterprise architecture team reviewed
business strategies and work plans after they were crafted by the business units
Next they identified what technical capabilities were required to support these strategies
Gathered the known supporting applications Identified where IT organizational implications
might be experienced
Organize A core team of Architects and Sr. Management (both
business and IT) developed a core list of principles and value statements between both organizations
Gathered list of known supporting applications Identified where IT organizational implications
might be experienced do to potential change
Document Created a list of business, information, solution
and technical architectures Documented pain points, opportunities and
current business activities Created graphical representations where
appropriate – illustrating current state Validated with key business liaisons
Identifying scope of effort Resources & costs estimates Iterative steps / roadmap to achieve Target State
Prioritize Provided an overall synopsis to business of
requirements as well as sampling of TSA’s Asked business to prioritize which capabilities
were most important to them, and which would coincide best with expected work activities this year
Applied these needs to our own resource and staff planning
Reviewed with business and secured support from them as well as shared resources.
A picture is worth a 1000 words
Identify a framework that you can rally around
Examples Business Strategy Architecture Vision Directed Business/IT directed
e.g. DATA
ENTERPRISE ARCHITECTURE - A FRAMEWORK
Builder
SCOPE(CONTEXTUAL)
MODEL(CONCEPTUAL)
ENTERPRISE
Designer
SYSTEMMODEL(LOGICAL)
TECHNOLOGYMODEL(PHYSICAL)
DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
DATA FUNCTION NETWORK
e.g. Data Definition
Ent = FieldReln = Address
e.g. Physical Data Model
Ent = Segment/Table/etc.Reln = Pointer/Key/etc.
e.g. Logical Data Model
Ent = Data EntityReln = Data Relationship
e.g. Semantic Model
Ent = Business EntityReln = Business Relationship
List of Things Importantto the Business
ENTITY = Class ofBusiness Thing
List of Processes theBusiness Performs
Function = Class ofBusiness Process
e.g. "Application Architecture"
I/O = User ViewsProc .= Application Function
e.g. "System Design"
I/O = Screen/Device FormatsProc.= Computer Function
e.g. "Program"
I/O = Control BlockProc.= Language Stmt
e.g. FUNCTION
e.g. Business Process Model
Proc. = Business ProcessI/O = Business Resources
List of Locations in which the Business Operates
Node = Major BusinessLocation
e.g. Logistics Network
Node = Business LocationLink = Business Linkage
e.g. "Distributed System
Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics
e.g. "System Architecture"
Node = Hardware/SystemSoftware
Link = Line Specifications
e.g. "Network Architecture"
Node = AddressesLink = Protocols
e.g. NETWORK
Architecture"
Planner
Owner
Builder
ENTERPRISEMODEL
(CONCEPTUAL)
Designer
SYSTEMMODEL
(LOGICAL)
TECHNOLOGYCONSTRAINED
MODEL(PHYSICAL)
DETAILEDREPRESEN-
TATIONS (OUT-OF
CONTEXT)
Sub-
Contractor
FUNCTIONING
MOTIVATIONTIMEPEOPLE
e.g. Rule Specification
End = Sub-conditionMeans = Step
e.g. Rule Design
End = Condition
Means = Action
e.g., Business Rule Model
End = Structural AssertionMeans =Action Assertion
End = Business ObjectiveMeans = Business Strategy
List of Business Goals/Strat
Ends/Means=Major Bus. Goal/Critical Success Factor
List of Events Significant
Time = Major Business Event
e.g. Processing Structure
Cycle = Processing CycleTime = System Event
e.g. Control Structure
Cycle = Component Cycle
Time = Execute
e.g. Timing Definition
Cycle = Machine CycleTime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. Work Flow Model
People = Organization UnitWork = Work Product
e.g. Human Interface
People = RoleWork = Deliverable
e.g. Presentation Architecture
People = UserWork = Screen Format
e.g. Security Architecture
People = IdentityWork = J ob
e.g. ORGANIZATION
Planner
Owner
to the BusinessImportant to the Business
What How Where Who When Why
Copyright - John A. Zachman, Zachman International
SCOPE(CONTEXTUAL)
Architecture
e.g. STRATEGY ENTERPRISE
e.g. Business Plan
TM
Zachman Institute for Framework Advancement - (810) 231-0531
(used with permission)
Info
rmat
ion
Sol
utio
ns
Infr
astr
uctu
re
Business
Bus
ines
s
Bus
ines
s
Bus
ines
s
An Architecture Framework
Principle or Value Business Model Inventory Guidelines / Standards
Information Needed
Business Function
Technical Platform
People Resources
A pictorial representation
Business Reference Model (BRM)• Lines of Business• Agencies, customers, partners
Service Component Reference Model (SRM)• Service domains, service types• Business and service components
Technical Reference Model (TRM)• Service component interfaces, interoperability• Technologies, recommendations
Data Reference Model (DRM)• Business-focused data standardization • Cross-agency information exchanges
Busin
ess-D
riven A
ppro
ach
Busin
ess-D
riven A
ppro
ach
Performance Reference Model (PRM)
• Inputs, outputs, and outcomes• Uniquely tailored performance indicators
Com
ponent-B
ase
d A
rchite
cture
Com
ponent-B
ase
d A
rchite
cture
FEA Reference Models
So what is in a TSA Document?
Objectives Opportunities Gaps Key Issues & Performance – Current State Key Requirements – Target State 3-5 Year Recommendation – Transition State
Identify Current State
Identify Target State
Prioritize and define transition
state
Assess whatthe business
needs
Keep it simple – 1-2 pages each
Opportunities Objectives
GAPS Current State
(Picture if Possible)
Target State Transition Process
Time for a break Come back for a live example
<< Business or I.T. Name of Process >
Target State Architecture
Outline Name of Process Architecture Objectives Name of Process Architecture Opportunities Name of Process Architecture Gaps Key Issues & Performance – Current State Key Requirements – Name of Process Target 3-Year Recommendation – Transition State
Name of Process TSA Objectives
Bullet 1 The bullets on this page are to emphasize the
business or technology challenges you are trying to impact
Bullet 2 Should be specific, in business terms and
measurable Bullet 3
Name of Process Architecture Opportunities The items on this slide should be specific
projects / Initiatives coming up that would afford a change to your environment
Bullet 2 Bullet 3 etc
Key Issues & Performance
List of specific current business pains and performance
curr
en
t st
ate
Key Requirements (Specific examples of requirements)
Ex: Reduce number of originating sources Define information authority / stewardship Cease proliferation of new data streams Explore methods to support corporate Information library.
targ
et
state
Transition State – 3-Year Recommendation Deliverable Cost Benefit (H/M/L)Upgrade to Application X, Y, Z from
Estimated FTEs: 1.5
Estimated Time (months) 9
Estimated CapitalHardware: noneSoftware: none
Customer Sat. M
Economic Impact L
Complexity M
Strategic Alignment L
Consolidated Reporting Estimated FTEs: 5
Estimated Time (months): 6
Estimated Capital
Customer Sat. H
Economic Impact M
Complexity H
Strategic Alignment MPartnering w/LMN project Estimated FTEs: 2
Estimated Time (months):24
Estimated Capital: NA
Customer Sat. H
Economic Impact H
Complexity H
Strategic Alignment H
tran
siti
on
sta
te
Transition State – 1+ Yr recommendation
Build Corporate Product Catalog/ Data Dictionary
Initial Product Data Inventory
Quality: Provide a single authoritative source of product information (metadata)
2005 2006 2007 2008
1H06 2H062H05 1H07 2H07 1H08 2H08
Quality: Standard Repository
Quantity: Reducing number of product sourcesDecommission Legacy Systems
Governance: Establish Product Data Ownership and StewardshipDefine Product Governance
Target State – 3-5+ Yr recommendation
(can use similar diagramming tool)
Architecture Long Range Plan
Results
Technology
Process
2014201220102008
People
2006
Defined process for localized efforts
Developing architectural capabilities of an IT organization takes sustained effort over a long period of time.
AD Hoc & locally chosen application technology
Local technology experts Technology Architects & (EA) Enterprise Architects
Evolve Enterprise Processes
Loose Infrastructure Architected Infrastructure Optimized Infrastructure
Standardized application technologies
Streamlined and lean application technologies
Integrated applications &Shareable business
processes
Lean and Standardized Technical and business
processes
Business Unit Independent un-integrated
Silos
Fully developed enterprise & Technology architects,Architects in the business
Standardize enterprise and local processes
Additional References / Info Putting Data back into Data Architecture, by Jane Carbone, TDan online newsletter
http://www.tdan.com/i021hy04.htm See also the DAMA Presentation that Jane did for Dama - Seattle, June 2005,
http://www.drma-seattle.org/JCJune2005.ppt Where the Target Application Architecture TAA Rubber meets the Road , Bureau of Land
Management, http://www.blm.gov/ba/spotlights/spotlight10.htm Systems and Software Consortium - http://www.software.org/pub/architecture/feaf.asp Federal Enterprise Architecture Website, http://www.whitehouse.gov/omb/egov/a-1-fea.html Zachman Institute for Framework Advancement, http://www.zifa.com
Thanks for your time and interest! Dawn Michels
Enterprise Information Architect Past Pres DAMA MN Past VP Chapter Services DAMA-I Adjunct Faculty Member, College of St.
Catherine Passionate Data Architect
[email protected] 651-264-7985