Getting from EA to Implemented Processes


Published on

Published in: Business, Travel
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Getting from EA to Implemented Processes

  1. 1. Elizabeth Erwin Senior Consultant RP International Session Title: Getting from Enterprise Architecture To Processes Implementation
  2. 2. 2008 BUSINESS ENVIRONMENT <ul><li>GLOBAL ECONOMY </li></ul><ul><ul><li>Rapidly Changing Market Place </li></ul></ul><ul><ul><li>Greater Complexity </li></ul></ul><ul><li>COMPETITIVE EDGE requires: - </li></ul><ul><ul><li>Rapid Response to the Market Place </li></ul></ul><ul><ul><li>Higher Quality Product </li></ul></ul><ul><ul><li>Lower Price </li></ul></ul><ul><ul><li>Market Intelligence </li></ul></ul>
  3. 3. NEEDS OF THE BUSINESS <ul><ul><li>MAKING </li></ul></ul><ul><ul><li>REQUIRES </li></ul></ul><ul><ul><li>A COMPETITIVE EDGE </li></ul></ul>
  4. 4. <ul><ul><ul><li>DYNAMIC BUSINESS MODEL </li></ul></ul></ul><ul><ul><ul><li>and </li></ul></ul></ul><ul><ul><ul><li>FLEXIBLE, RESPONSIVE </li></ul></ul></ul><ul><ul><ul><li>Processes & Systems </li></ul></ul></ul><ul><ul><li>RAPID MARKET </li></ul></ul><ul><ul><li>RESPONSE </li></ul></ul><ul><ul><li>TIMELY & COST EFFECTIVE </li></ul></ul><ul><ul><li>QUALITY PRODUCT DELIVERY </li></ul></ul><ul><ul><li>REQUIRES </li></ul></ul>
  5. 5. OBJECTIVES of Enterprise Architecture <ul><li>HOW TO: - </li></ul><ul><ul><li>Support The Business Needs </li></ul></ul><ul><ul><li>Manage Complexity </li></ul></ul><ul><ul><li>Manage Change </li></ul></ul><ul><ul><li>Rapidly Assemble Solutions </li></ul></ul>
  6. 6. What Has Not Worked <ul><li>Methods </li></ul><ul><li>Tools </li></ul><ul><li>“ IT MAKES ONE WONDER IF THERE ACTUALLY IS A TECHNICAL SOLUTION TO THE PROBLEM!!!” </li></ul><ul><ul><ul><li>John Zachman </li></ul></ul></ul><ul><ul><ul><li>Enterprise Architecture Conference London June 2006 </li></ul></ul></ul>
  7. 7. Why Haven’t They Worked <ul><li>Is there anything wrong: - </li></ul><ul><ul><li>with them? Probably Not </li></ul></ul><ul><ul><li>the way they are used? Probably Yes </li></ul></ul><ul><li>Do we use them to Visualize a Real World 3D View of the Business? Probably Not </li></ul><ul><li>Can they manage COMPLEXITY </li></ul><ul><li>Probably Not </li></ul><ul><li>Are we using the Right Tool for the right Job? </li></ul><ul><li>Probably Not </li></ul>
  8. 8. What Can Help? <ul><li>The Framework for Information Architecture </li></ul><ul><li>Follow Good Engineering Practices </li></ul><ul><li>Guidelines to Manage Scope </li></ul><ul><li>Define Generic, Decomposable Business Components </li></ul><ul><li>Construct PRIMITIVE Business Models </li></ul>
  10. 10. Many Views of The Enterprise <ul><li>Your VIEW of WHAT is going on, depends on: - </li></ul><ul><ul><li>What area of the business you view it from. </li></ul></ul><ul><ul><li>What are the needs of your part of the business. </li></ul></ul><ul><ul><li>What function you need a business component to perform. </li></ul></ul><ul><ul><li>What Type of transactions you initiate. </li></ul></ul>
  12. 13. Business Entity ENTERPRISE VIEW BILLING Location Marketing Strategy External Compliance Message Product Account Finannce Network Element offered to offered by contact address is sends payment recieves bill noted as contracts for manages plans utilizes sets value requires Party
  13. 16. Good Engineering Practices <ul><li>Determine WHAT is needed before you start building it. </li></ul><ul><li>Manage Scope </li></ul><ul><li>Identify from the General to the Specific </li></ul><ul><li>Design Generic Reusable Components that support Solution Assembly </li></ul><ul><li>Generic Components will be parameter & transaction driven </li></ul><ul><li>Constantly validate against the Primitive Models Business requirements </li></ul>
  14. 17. Component Def: - Contributing to the composition of the whole <ul><li>Enterprise Component </li></ul><ul><li>Business Component </li></ul><ul><li>- multiple layers, as many as needed </li></ul><ul><li>Solution / Scenario Assembly </li></ul><ul><ul><li>WHAT satisfies the Business Requirements </li></ul></ul><ul><li>Transaction(s) </li></ul><ul><ul><li>Detail processing thru the Solution / Scenario </li></ul></ul>
  15. 18. Defining Components <ul><li>Business Components </li></ul><ul><li>= Sub Contractors </li></ul><ul><li>Focus on WHAT </li></ul><ul><li>NOT HOW </li></ul><ul><li>Maintain Function Borders </li></ul><ul><li>“ Not My JOB” </li></ul>
  16. 19. WHAT ( Engineering Practices ): - <ul><li>What is the Job ? & Not my Job concepts </li></ul><ul><li>Information I/P is required? </li></ul><ul><li>Are the Resources require? </li></ul><ul><li>Are the Deliverables ? </li></ul><ul><li>Information O/P is required? </li></ul><ul><li>MAGIC !!!! </li></ul>
  17. 20. Derived from ITIL Change Standards
  18. 21. IMPACT ASSESSMENT OBJECTIVE To ensure clear identification of all Impacted parties & network elements to support risk evaluation and customer communications RESPONSIBILITY Impact Assessment Check List: - Network / Technical Impact Assessment must be accomplished via a dialogue with the appropriate Technical Sub-Domain to ensure the most technically effective solution design. The following should be detailed for each Change: - - ID impacted: - systems, applications, services - evaluate adverse impact probability for each of the above - very high, high, medium, low, zero - ID impacted customers the adverse impact probability - Specify the type(s) of impact(s): - - including any possible mitigations, such as fail-over to resilient side - locations affected - how any customer may be impacted - or other business areas Note: - A complete a risk assessment for each specific change
  19. 23. Conclusions <ul><li>The Enterprise if Virtual & 3 Dimensional </li></ul><ul><li>Each Perspective into it sees a Different View because the are doing different work </li></ul><ul><li>Enterprise Architecture is about ENGINEERING Generic Reusable Components to support a FLEXIBLE RESPONSIVE BUSINESS </li></ul><ul><li>You can start with defining a piece of the Enterprise – Vertical Slice </li></ul>
  20. 24. SO what do I do when I get home? <ul><li>Work on Changing the way people see the business. </li></ul><ul><ul><li>Follow the WHAT not HOW rules in work shops </li></ul></ul><ul><li>Pick a small project and give it a try </li></ul><ul><ul><li>Stick to the Vertical Slice borders </li></ul></ul><ul><li>Find a Stake Holder & an experienced Mentor </li></ul><ul><li>If you have an engineer (mechanical, electrical, network) talk to them about how they build things </li></ul>
  21. 25. <ul><li>Will it be Easy? Not at First!! </li></ul><ul><li>Will it be Worth it? YES </li></ul><ul><li>Examples </li></ul><ul><ul><li>GE engine assembly project </li></ul></ul><ul><ul><li>Satellite company </li></ul></ul><ul><ul><li>Reuse of Business Knowledge </li></ul></ul>
  22. 26. You know the way forward . Thank You! <ul><li>Elizabeth Erwin </li></ul><ul><li>Senior Consultant </li></ul><ul><li>RP International </li></ul><ul><li>Contact Information: </li></ul><ul><li>+44 (0)7921-454-171 </li></ul><ul><li>[email_address] </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.