1 / 27

Target State Architecture TSA

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

ramona
Download Presentation

Target State Architecture TSA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Target State ArchitectureTSA Presented by Dawn Michels Enterprise Information Architect Andersen Corporation Feb 15, 2006 For Dama Minnesota

  2. 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.

  3. 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

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

  5. 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

  6. 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

  7. 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

  8. 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.

  9. A picture is worth a 1000 words • Identify a framework that you can rally around • Examples • Business Strategy • Architecture • Vision Directed • Business/IT directed

  10. Business Information Solutions Infrastructure Business Business Business (used with permission)

  11. An Architecture Framework

  12. A pictorial representation

  13. FEA Reference Models

  14. Prioritize and define transition state Identify Current State Assess what the business needs Identify Target State 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

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

  16. Time for a break • Come back for a live example

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

  18. 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

  19. 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

  20. 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

  21. Key Issues & Performance current state • List of specific current business pains and performance

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

  23. Transition State – 3-Year Recommendation transition state

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

  25. 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 People Local technology experts Technology Architects & (EA) Enterprise Architects Fully developed enterprise & Technology architects,Architects in the business Process Defined process for localized efforts Evolve Enterprise Processes Standardize enterprise and local processes Technology AD Hoc & locally chosen application technology Standardized application technologies Streamlined and lean application technologies Loose Infrastructure Architected Infrastructure Optimized Infrastructure Results Business Unit Independent un-integrated Silos Integrated applications &Shareable business processes Lean and Standardized Technical and business processes

  26. 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

  27. 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 • Dawn.michels@Andersencorp.com • 651-264-7985

More Related