SAUG Summit 2009 - Session 9 SAP Solution Architect


Published on

Sessiondelivered at the SAUG Summit event 2009. On the role of the Solution Architect in a SAP Centric Organisation.

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Enterprise Architecture’s contribution: Clearly setting the course
  • SAUG Summit 2009 - Session 9 SAP Solution Architect

    1. 1. The Solution Architecture Process in a SAP Centric Organisation Phil Gleadhill, Principal SAP Technical Architect, Australia Post
    2. 2. Australia Post: Our Business Today Three Business Divisions Letters and associated products <ul><li>5.6 billion items of mail per year </li></ul><ul><li>15-16 million articles per day </li></ul>Parcels and Logistics <ul><li>10.2 million delivery points </li></ul><ul><li>500,000 km per day </li></ul><ul><li>>300 Processing Centres </li></ul><ul><li>27 Warehouses </li></ul>Retail and Agency Services <ul><li>4,500 retail outlets </li></ul><ul><li>187 million banking & billpay transactions per year </li></ul><ul><li>>1000 active agencies </li></ul><ul><li>1 million customers served every day </li></ul>
    3. 3. Solution Architecture @ Australia Post: Who Contributes? Business Strategy Setting the “Business” Course Business Integration Program (BIP) End to End Detailed Design Documents End to End Solution Subject Matter Expertise Program/Project resources SAP Fit/Gap Analysis, Solution Outline (SO) High Level Solution Design Solution Architects / SAP Services Business Requirements Statement (BRS) Requirements gathering and Prioritisation with Business units Business Service Units (BSU’s) (PIAF) - Post Integrated Architecture Framework Setting the “IT” Course Enterprise Architecture (EA) Artefact(s) Contribution Group
    4. 4. Key Resourcing – The People Picture Solution Architects / SAP Services Business Service Units (BSU’s) Enterprise Architecture (EA) Business Integration Program (BIP) Group 60 resources across 3 BSU’s 11 Solution Architects ~ 80 SAP Services Projects + Support 16 resources 10 resources Resources
    5. 5. Enterprise Architecture: PIAF - The IT Roadmap  Quick Snapshot
    6. 6. Enterprise Architeure - Firmly Setting The Course: Enterprise Application Function Model: For 2011+ Partner Services Product & Service Fulfilment Asset & Sourcing Mgmt. Financial Mgmt. People Mgmt. Corporate Support Customer Channels Customer Marketing & Sales Mgmt. Customer Mgmt. Business Performance Product Address Network Event Address & Network Operations Mgmt. Channel Mgmt. Business Planning & Performance Mgmt. Product & Service Mgmt. Analysis & Reporting Mail Services Infrastructure Services Transport & Logistics Services Business Performance Person/ Org. Unit Finance Supplier Contract Asset Product Customer Brand Event Address Network Partner
    7. 7. SAP Fit/Gap Analysis: Roles and Responsibilities Business Services Units Requirements & Co-ordination Strategic alignment SAP fit assessment & SAP solution components End-to-end solution SAP Services EA - Solutions Architects EA - Principals
    8. 8. SAP Fit/Gap Analysis: Responsibility Matrix $ - Initiate Phase work is funded from business as usual ^ - SAP Services will determine if SAP (the vendor) needs to be involved ^ ^ - SAP Services to complete solution outline when end-to-end solution resides within SAP Initiate Phase $ Evaluate and Plan Phases  Arrangement of feasibility funding & prioritisation  Business Requirements Specification  ^ Detailed Fit Gap Analysis and SAP solution   ^ ^ Solution Outline for end-to end solution  If SAP, high-level SAP fit assessment including licensing implications  Alignment to Future State Architecture (includes consultation with SAP Services Manager)  High Level Requirements EA Solutions Architect SAP Services EA Principal BSU Responsibility
    9. 9. The Solution Outline – Table of Contents <ul><li>3. ARCHITECTURALLY SIGNIFICANT REQUIREMENTS </li></ul><ul><li>4. SYSTEM CONTEXT </li></ul><ul><li>4.1 Involved Actors </li></ul><ul><li>4.2 Involved Systems </li></ul><ul><li>4.3 Data Flows </li></ul><ul><li>4.4 Current Systems </li></ul><ul><ul><li>4.4.1 Current Systems Architecture & Scope </li></ul></ul><ul><ul><li>4.4.2 Australia Post Systems to be replaced </li></ul></ul><ul><li>5. IT SOLUTION </li></ul><ul><li>5.1 High Level Solution Description </li></ul><ul><li>5.2 System Functions </li></ul><ul><li>5.3 Service Descriptions </li></ul><ul><li>5.4 Detailed Solution </li></ul><ul><ul><li>5.4.1 Component Responsibilities </li></ul></ul><ul><ul><li>5.4.2 Actor Component Interfaces </li></ul></ul><ul><ul><li>5.4.3 System Component Interfaces </li></ul></ul><ul><li>5.5 Solution Commentary </li></ul><ul><li>5.6 Client Configuration </li></ul><ul><li>5.7 Server Configuration </li></ul><ul><ul><li>5.7.1 Web Server </li></ul></ul><ul><ul><li>5.7.2 Application Server </li></ul></ul><ul><ul><li>5.7.3 Database Server </li></ul></ul><ul><li>5.8 Infrastructure Services </li></ul><ul><ul><li>5.8.1 Active Directory </li></ul></ul><ul><ul><li>5.8.2 MS Exchange </li></ul></ul><ul><ul><li>5.8.3 WAN </li></ul></ul><ul><ul><li>5.8.4 Enterprise Systems Management </li></ul></ul><ul><li>6. SECURITY AND PRIVACY MECHANISMS </li></ul><ul><li>7. DEPLOYMENT </li></ul><ul><ul><li>7.1 Environments </li></ul></ul><ul><ul><li>7.2 Architecture </li></ul></ul><ul><li>8. VOLUMES & PERFORMANCE METRICS </li></ul><ul><li>9. ASSUMPTIONS, RISKS AND DEPENDENCIES </li></ul><ul><li>10. OUTSTANDING ISSUES </li></ul><ul><li>11. ARCHITECTURE DECISIONS </li></ul><ul><li>12. FUTURE RECOMMENDATIONS </li></ul><ul><li>APPENDIX B: CORP SDE </li></ul><ul><li>APPENDIX B: GLOSSARY </li></ul>
    10. 10. Phil Gleadhill – Thank You!
    11. 11. Other definitions for architects <ul><li>A Solutions Architect in Enterprise Architecture is a practitioner in the field of Solution Architecture . [1] </li></ul>The role of &quot; Solutions Architect&quot; requires knowledge and skills that are both broad and deep. To be effective the Solutions Architect must have experience on multiple Hardware and Software Environments and be comfortable with complex heterogeneous systems environments . The Solutions Architect is often a highly seasoned senior technocrat who has led multiple projects through the Software development process or Systems Development Life Cycle (SDLC), and has usually performed in a variety of different roles in that life cycle. The person needs an ability to share and communicate ideas both verbally and in writing to executive staff, business sponsors, and technical resources in clear concise language that is the parlance of each group.
    12. 12. I am reminded of someone…..
    13. 13. Enterprise compared to Solution Architects ? But the job had gone A quick trawl of the job sites
    14. 14. SAP’s views on this <ul><li>Embodies principles from TOGAF </li></ul><ul><li>Documented in Solution Manager as the Enterprise Architecture Framework </li></ul>R u mature enough?
    15. 15. Per EAF in solution manager and TOGAF The focus of the Enterprise Architect is on enterprise-level business functions required. The focus of the Solution Architect is on system technology solutions .
    16. 16. And how the roles fit into the governance framework
    17. 17. There are also many example docs
    18. 18. SAP Services also has a Enterprise Architect Roles Enterprise SOA, mySAP Business Suite, specialty certification History as Principal BSA or Principal TSA 7+ yrs Deep industry and method know-how Deep expertise in enterprise SOA Deep knowledge of SAP‘s roadmaps Good knowledge of SAP solutions (strengths and weaknesses) Good knowledge of SAP‘s competitors and their solutions Architectural portfolio management of IT landscape Architectural portfolio management of IT projects Architectural definition of (bounded) change initiatives Architectural governance of change implementation In- and externally recognized as an expert in Enterprise Architecture field Principal EA See “Principal EA” See „Principal EA“ 9+ yrs See „Principal EA“ + Trusted advisor for strategic customers TCO Analysis - optimization of IT-organizations (build and run) Design large scale transformations; program mgmt Part of large scale enterprise transformations Knowledge of business processes within industry Good knowledge of application architectures Management of SAP-internal EA teams (personal, financial, content responsibility) T-shaped: broad view across several dimensions, plus deep capability to understand a specific area Chief Enterprise Architect
    19. 19. Just in case….Homer doesn’t fit the profile Homer : Operator! Give me the number for 911!
    20. 20. Thank you Questions
    21. 21. Thank You