Target State Architecture TSA Presented by Dawn Michels

Target State Architecture TSA Presented by Dawn Michels Enterprise Information Architect Andersen Corporation Feb 15, 2006 For Dama Minnesota

What is a TSA? o o 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… o Assess n n n o Organize n n o Develop principles and values Develop specific list of architectures Document n n o Understand assess key business strategies and business unit plans Evaluate current business models, high levelgaps between business process and technology offerings Identify IT organizational implications Identify specific opportunities & pain points Document current and target states of specific architectures Prioritize n n Prioritize business needs/intersection with IT capabilities List specific initiatives that would move us in the right direction

Who Participated o o o Executive Leadership Business Management Sr. IT Management Enterprise Architects Business/IT Liaisons

Assess o o 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 o o o 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 o o 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 n n n Identifying scope of effort Resources & costs estimates Iterative steps / roadmap to achieve Target State

Prioritize o o 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 o o Identify a framework that you can rally around Examples n n Business Strategy Architecture Vision Directed Business/IT directed

Business Infrastructure Solutions Information Business (used with permission)

An Architecture Framework Principle or Value Business Model Inventory Guidelines / Standards Information Needed Business Function Technical Platform People Resources

A pictorial representation

FEA Reference Models

So what is in a TSA Document? o o o Objectives Opportunities Gaps Key Issues & Performance – Current State Key Requirements – Target State 3 -5 Year Recommendation – Transition State Assess what the business needs Identify Current State Identify Target State Prioritize and define transition state

Keep it simple – 1 -2 pages each Opportunities GAPS Target State Objectives Current State (Picture if Possible) Transition Process

Time for a break o Come back for a live example

<< Business or I. T. Name of Process > Target State Architecture

Outline o o o 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 o Bullet 1 n o Bullet 2 n o The bullets on this page are to emphasize the business or technology challenges you are trying to impact Should be specific, in business terms and measurable Bullet 3

Name of Process Architecture Opportunities o o 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

current state Key Issues & Performance o List of specific current business pains and performance

target state Key Requirements (Specific examples of requirements) Ex: o o Reduce number of originating sources Define information authority / stewardship Cease proliferation of new data streams Explore methods to support corporate Information library.

transition state Transition State – 3 -Year Recommendation Deliverable Cost Benefit (H/M/L) o. Upgrade to Application X, Estimated FTEs: 1. 5 Estimated Time (months) 9 Estimated Capital Customer Sat. M Economic Impact L Complexity M Strategic Alignment L Y, Z from n. Hardware: none n. Software: none o. Consolidated Reporting Estimated FTEs: 5 Estimated Time (months): 6 Estimated Capital Customer Sat. H Economic Impact M Complexity H Strategic Alignment M o. Partnering w/LMN project Estimated FTEs: 2 Estimated Time (months): 24 Estimated Capital: NA Customer Sat. H Economic Impact H Complexity H Strategic Alignment H

Transition State – 1+ Yr recommendation 2005 2 H 05 2006 1 H 06 Initial Product Data Inventory Define Product Governance 2007 2 H 06 1 H 07 2008 2 H 07 1 H 08 2 H 08 Quality: Standard Repository Governance: Establish Product Data Ownership and Stewardship Decommission Legacy Systems Build Corporate Product Catalog/ Data Dictionary Quantity: Reducing number of product sources Quality: Provide a single authoritative source of product information (metadata) Target State – 3 -5+ Yr recommendation (can use similar diagramming tool)

Architecture Long Range Plan Developing architectural capabilities of an IT organization takes sustained effort over a long period of time. 2006 2008 2010 2012 2014 Fully developed enterprise & Technology architects, Architects in the business People Local technology experts Technology Architects & (EA) Enterprise Architects Process Defined process for localized efforts Evolve Enterprise Processes Standardize enterprise and local processes AD Hoc & locally chosen application technology Standardized application technologies Streamlined and lean application technologies Loose Infrastructure Architected Infrastructure Optimized Infrastructure Business Unit Independent un-integrated Silos Integrated applications & Shareable business processes Lean and Standardized Technical and business processes Technology Results

Additional References / Info o o o Putting Data back into Data Architecture, by Jane Carbone, TDan online newsletter http: //www. tdan. com/i 021 hy 04. htm See also the DAMA Presentation that Jane did for Dama - Seattle, June 2005, http: //www. drmaseattle. org/JCJune 2005. ppt Where the Target Application Architecture TAA Rubber meets the Road , Bureau of Land Management, http: //www. blm. gov/ba/spotlights/spotlight 10. 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! u Dawn Michels u u u u Enterprise Information Architect Past Pres DAMA MN Past VP Chapter Services DAMA-I Adjunct Faculty Member, College of St. Catherine Passionate Data Architect Dawn. michels@Andersencorp. com 651 -264 -7985