Modelling, Analysing and Improving an ERP Architecture with ArchiMate

Transcription

1 Modelling, Analysing and Improving an ERP Architecture with ArchiMate June 25th, 2014 Heinz-Juergen Scherer, TransWare Tim Vehof, BiZZdesign

2 Agenda Introduction Enterprise Architecture ERP systems and observations ArchiMate SAP and ArchiMate Examples Roadmap development & conclusions

3 Introducing presenters Tim Vehof BiZZdesign Heinz-Juergen Scherer TransWare AG Consultant EA, BPM, BMM Trainer ArchiMate 2.1 TOGAF 9.1 BiZZdesign Architect CEO TransWare AG Sales and Marketing SAP architecture SAP NetWaever SAP BPM and EA SAP Solution Manager

4 BiZZdesign - Integrated service offering Enterprise Architecture Management Business Modeling Business Process Management Business Rules Management Consulting services Tooling Training Best practices 4

5 Clients, offices and partners worldwide Netherlands: Amersfoort, Enschede North America: Toronto, Boston Belgium: Leuven UK: London Slovakia: Bratislava France: Paris Germany: Dusseldorf Switzerland: Zurich Sweden: Stockholm Partners Latin America: Dux Diligens Mexico: Unycorp Australia: Neodata Portugal: Process Sphere 5

6 TransWare Software Solution AG Located in Germany US subsidiary TransWare America Inc. SAP Services Partner Tool-based analytic solutions and consultancy with a strong focus to ERP business processes Business process analysis (BPA) System landscape optimization (SLO) Integration of enterprise management systems Specialized for SAP Solution Manager

7 Business value Describing an ERP landscape by an Enterprise Architecture language (ArchiMate) defines a standard of a solution documentation Uncovering the complex architecture of an ERP system enables the organization to analyse and understand the real usage and customizing of the ERP architecture Managing the change and impact of projects more effective and efficient by standard Architect tool Holistic view of the ERP landscape from end user view (business processes) down to technical views (technical implementation) delivers more transparency for all participants

8 Typical questions to be answered by EA Can we get rid of all those custom ( customized ) objects? Are all these Z-reports still needed to be tested for the next upgrade? Can we replace those custom Z-transactions by standard SAP transactions, who is still using those transactions? Which application and system interfaces (IDoc, BAPI, SOAP etc.) are used? How we can control data flow by monitoring of those interfaces? Which master data is used by which business processes, who maintains the master data? Are there web services available we can use in our SOA initiative for the implementation of BPM services? Which SAP standard objects are modified and what is a possible impact when we upgrade our landscape? Who we can re-use transactions in different scope of business processes?

9 ENTERPRISE ARCHITECTURE

10 What is Enterprise Architecture? Information architecture A discipline, with the objective of steering changes? A product A design that shows the coherence between products, processes, organisation, information Application architecture supply and infrastructure, based on a vision and certain explicit starting points, principles and preferences A process Way of working Aimed at the development and use of enterprise architectures within an enterprise With people and resources Process architecture Technical architecture

11 Ingredients of an EA Approach TOGAF ArchiMate Process Viewpoints Language Enterprise Continuum, Repository, Reference Models

12 Use EA to Get a grip on business transformation and change Increase Business / IT alignment Impact analysis Project support (architecture contract) Portfolio management Communication with stakeholders Insight in the current state of affairs Not a goal in itself!

13 ERP SYSTEMS AND OBSERVATIONS

14 Development of SAP ERP architecture and complexity In-Memory Hana Cloud Mobility SOA & BPM

15 Some observations It is difficult to get a good overview of a SAP landscape SAP CC and IT are always busy with operational tasks and projects Different languages are used between business lines, architects and IT It is a high manual, repetitive effort to extract some portions of data Given its complexity and size, a SAP landscape constitutes an enterprise architecture of its own Business layer: business processes, organizational units, Application layer: modules, applications, transactions, data Technical layer: databases, servers, Including their relations and dependencies

16 Conclusion This leads to typical, EA-related questions like Which existing web services we be leveraged in our SOA initiative? Which SAP master data is used by which SAP processes and managed by which departments? How mission critical processes are supported by custom functionality? What is the business impact of a planed change in the project? Which application interfaces are impacted by a design change? ArchiMate is typically used to answer these kind of questions Other approaches focus only on some partial aspects such as ERP data dictionary or customizing of transactions

17 ARCHIMATE AN INTRODUCTION

18 ArchiMate Language for describing enterprise architecture Covers business, application and technology With relations between these layers Extensions for Motivation Migration and implementation Graphical language with formal semantics, enabling analysis and tool support Techniques for visualization and analysis, aimed at various stakeholders Open standard maintained by The Open Group

19 The ArchiMate Language High-level modelling within a domain ArchiMate language Basis for visualisations modelling relations between domains Basis for analyses

20 ArchiMate-Core language structure 20

21 ArchiMate core and extensions

22 ArchiMate + TOGAF Free download of the whitepaper Enterprise Architecture with TOGAF 9.1 and ArchiMate here: manager/download/14 22

23 TOOL SUPPORT FOR ARCHIMATE: BIZZDESIGN ARCHITECT

24 BiZZdesign Architect Tool to model, visualize, analyze and communicate architectures Easy to use with powerful functionality Delivers added value both for individual architects as for teams of architects Completely adjustable meta model, based on ArchiMate Supports many architecture frameworks, like Zachman, DYA, Tapscott, Nolan-Norton, TOGAF Architect is ArchiMate and TOGAF TM -certified

25 Main functionality of Architect Modeling business and IT-architectures conform ArchiMate 2.1 Import/export of existing architecture overviews Generating views from the repository Visualization of properties Impact-of-change analyses and querying Documenting, reporting, and publishing architectures Team support and repository support (Oracle, SQL Server) Download trial-version!

26 Examples from BiZZdesign Architect

27 SAP & ARCHIMATE

28 Profiling: Extraction of data from SAP SAP meta model Profiler for SAP Data extract SAP ERP landscape ERP, CRM, SCM, NetWeaver Application Server SAP Solution Manager Mapping BiZZdesign Repository ArchiMate meta model

29 Comprehensive view of entities building the SAP architecture and meta model Systems and technical components Data-dictionary meta-data (ERM) SAP functionality (transactions, reports, forms) Web services (RFC, BAPI, SOAP) Modules, Applications, tech. Components Interfaces (RFC, IDOC, PI, ) SAP capability maps (SAP BPR, Blueprints) Business data (document types) Usage and Customizing (Z-, Y-), 3 rd Party Tech. Org.-structures (client, company codes, plants, storage, sales, ) HR Org.-structures (Info-types) Authorizations (C/S-Roles, Profiles) and much more

30 Methodology Use a standard SAP reference model in BiZZdesign Architect and ArchiMate meta model template Modules, interfaces, services, transactions, objects, relations, etc. Based on a generic SAP ERP implementation Retrieve customer specific SAP implementation data Use Profiler for SAP from TransWare on customer implementation Creates a model of that specific SAP implementation Refine results with an incremental, iterative approach Extracting every element from SAP is not useful Adding elements, relations, and properties on demand as needed

31 General assumptions Selected information is extracted from SAP Only those objects are extracted that seem relevant Only those relations are extracted that seem relevant Only those properties are extracted that seem relevant More and other information can be extracted if necessary Information is mapped onto ArchiMate and Architect tool Mapping based on our best understanding of SAP meta model Mapping required extending/specializing ArchiMate meta model Mapping is open to improvement

32 Extraction of SAP entities in XML to load and map into the ArchiMate repository

33 Example Resulting Architect model

34 CREATING A METAMODEL FOR YOUR ORGANIZATION

35 Procedure - example Large organization, difficulties getting grip on SAP-implementation SAP knowledge ArchiMate knowledge Business stakeholders 1. Select relevant SAP-objects 2. Discuss usage and mapping 3. Create metamodel

36 Relevant SAP objects

37 Usage and mapping of objects

38 ArchiMate metamodel - relations

39 EXAMPLES

40 SAP-FI

41 SAP-FI and master data objects

42 SAP-FI: use of data objects

43 Data objects with areas

44 Application with functions and interfaces

45 Call count of interfaces

46 Application with web services

47 Capability maps - business scenario and processes enclosed

48 Business Blueprint data out of SAP Solution Manager in the Architect tool View of the SAP Blueprint BiZZdesign EA repository SAP Solution Manager Process Repository: Capability maps (Blueprint), SAP Business Process Repository (BPR)

49 FUTURE DEVELOPMENTS AND CONCLUSIONS

50 Roadmap of development Full automation of data retrieval and load into the repository Extend the export with other useful elements Based on user requirements Involve other modeling languages like BPMN for business process flows Create standard library for different SAP products (ERP, CRM, SCM, PLM, ) Support for SAP Blueprint modeling with SAP Solution Manager Analysis of SAP landscape directory

51 Summary An ERP landscape is a complex (enterprise) architecture Uncovering the complex architecture of an ERP system enables an organization to analyse the usage of the components within that architecture ArchiMate can be used fruitfully to visualize and analyze an ERP landscape and defines a standard for solution documentation Further projects will refine the mapping between SAP and ArchiMate with best practice create accelerators for analysis and visualizations

52 Contact info and more information A copy of this slides: and select webinars" General information about BiZZdesign: The website of our Academy: Our Tool, BiZZdesign Architect Blog.bizzdesign.com TOGAF series : helps you getting started with TOGAF ArchiMate series : provides an overview of ArchiMate combined with best practices TransWare Software Solution AG info@transwareag.com