The document discusses mapping models of understanding from the Global Bike case study (GBI) to models of execution using the LEAD frameworks. It provides an overview of how GBI teaches both understanding and execution of ERP systems using ARIS and SAP tools. It then examines how to derive models of execution from existing GBI case studies to better integrate strategic planning and continuous improvement. The document explores mapping GBI meta objects to LEAD frameworks to improve understanding. It provides examples of mapping objects between the business, process, application and data layers of GBI and LEAD. This mapping allows online navigation between the three layers of LEAD and GBI's enterprise model using ARIS Business Publisher.

1. From Models of Understanding (ARIS
example) to Models of Execution (SAP
example)
Online Integration with LEAD for better Understanding
Presenter: Hans Scheruhn
Twitter ID: hscheruhn

2. Agenda
 Situation: Teaching “Understanding” and/or
“Execution” of ERP
 Complication : How to derive Models of Execution
from existing ERP Case Studies at Global Bike
Incorporated?
 Leading Question: Is Mapping of Models of
Understanding at GBI with LEAD Frameworks
possible?
 Answer :Check ARIS Prototype for Online Mapping
LEAD and GBI Meta Objects !
 Conclusion
 Outlook

3. Situation : Teaching ERP at German Universities
 > 90 % of German Universities teach ERP (Focus Process Execution of SAP) *
 > 70 % of German Universities teach Process Design (Focus ARIS)
 < 30 % teach entire Process Life Cycle (from Strategic Planning to Continuous
Improvement)
3
(*) Sandro Sicorello : Master Thesis, ERP Lehre an deutschen Hochschulen im Vergleich mit der Hochschule Harz, 2013 The LEADING Practise Agile Concept. 2013

4. Situation at Hochschule Harz University:
Teaching “Understanding” and “Execution” of ERP
Understanding
 Working with Demo Company Global Bike Incorporated (GBI)
 Learning Integration of all phases of Process Life Cycle at GBI
 Understanding user interaction with IT concerning different Layers of IT Integration
 Tools : ARIS Business Designer <->SAP Solution Manager
Execution
 GBI Case studies : SAP ERP MM, SAP Netweaver BI, HANA, Mobile Platform, …
 Tools : SAP Solution Manager <-> SAP ERP, SAP Netweaver BI (Business Intelligence), …
4

5. SAP University Alliances Americas, EMEA and APJ (2013)
 Over 800 universities and schools with more than 130,000 students are using SAP
University Alliances services (like GBI Case Studies) in the EMEA region supported by
the two SAP University Competence Center UCC Magdeburg and UCC Munich
APJ (QUT)Americas (CSU / UWM) EMEA

6. Execution done by Cases studies of Demo Company GBI
6
GBI-Documents

7. Setup of the Model of Understanding by definition of:
1. subject-oriented models
2. process-oriented models
3. service-oriented models
4. enterprise data models
Integration of mentioned above 4 layers into a single, overall Enterprise Information Model,
for describing an IT System and its interactions with its users (Business and IT) by definition
of relations between the different Meta Objects covered (GBI Meta Model)
Challenge : Vertical Decomposition / Composition Meta Objects of each of the four IT
Integration layers (accord. to SCOR */ SAP Solution Manager)
1. core level
2. overview level
3. detailed level
4. document level ** * [Supply Chain Council, 2012], ** (not supported by SAP Solution Manager)
Reengineering ! and ReIntegrating ! of existing GBI Case studies
Presentation
Process
Function
Data
Complication : How to get from existing GBI Case Studies to
Models of Execution ?

8. From Models of Understanding to Models of Execution
(Teaching Business and IT)
Presentation
Process
Function
Data
8
SAP GUI, WebDynpro
BPMN, EPC
SAP ERP (MM)
SAP ERP Data Model
Business Roles
Business Processes
Business Functions
Business Data
Execution (Business) Execution (IT)Understanding
 4 Level of IT Integration + 4 Levels of Decomposition/Composition + Process Life Cycle
+ 3 Tiers of Information Pyramid (Strategic, tactical, operational) :
– Models of Execution (Business and IT) integrated in a single Enterprise Information Model enable :
• Comparison of different demo Companies *
• Model Driven Implementation with SAP Solution Manager **
(*) Scheruhn, H.; Sicorello, S.; Weidner, S.: Repository-based ERP case studies: A study about chances and benefits of agile case study development in Witold Abramowicz, John Domingue, Krzysztof Wecel
(Eds.): Business Information Systems Workshops - BIS 2012 International Workshops and Future Internet Symposium, Vilnius, Lithuania, May 21-23, 2012 Revised Papers. Springer 2012
(**) Scheruhn, H.; Ackermann, D.; Braun, R.; Förster, U. : Repository-based Implementation of information pyramid: A study based on ERP case studies: HCI 2013 International 2013 Conference, Las Vegas,
USA, July 21-26, 2013 Proceedings by Springer 2013
Vision ,Mission, Strategy,
Goal, Objective, KPI
Management Processes
Management Functions
Strategic/tactical Data
Balanced Scorecard
SAP ERP
Info Cubes SAP NW BI
+

9. From Models of Understanding to Models of Execution
(detailed view)
9
1.Presentation layer
Organization Chart
Function (Role, Mask) Allocation Diagram
Company and Department Balanced Scorecard
2.Process layer
E-Business Scenario Diagram
Value added Chain Diagram
Business Rules eEPC / BPMN Process Diagram
Workflow Container Flow
3.Function layer
Business Services Tree
Objective Diagram
UML Class Diagram
4.Data layer
Info Cube, Dimension and Facts Data as Data Warehouse Structure
Diagram
Data Source Model
KPI Allocation Diagram
System Organization Customizing Diagram
Mask Diagram and WebDynpro Context

10. GBI Meta Objects / Models of Execution Matrix (extract)
Stand 27.01.2014
http://hscheruhn.hs-harz.de/forschung/Modell-Matrix_horizontale_Navigation_Sol_Man_BI.pdf

11. GBI Meta Object / Models of Execution Matrix (extract)
11

12. Blog „Online Process Management“ students project using
the Models of Execution Repository( 3855 Visitors 28.2.2014)
Online Process Management at GBI / Part 1
GBI Business Process Management Life Cycle, GBI Enterprise
Model, GBI Sustainability Balanced Scorecard
Online Process Management at GBI / Part 2
HS Harz Roadmap at SAP Solution Manager, GBI Business
Blueprint goes ARIS
Online Process Management at GBI / Part 3
Business Workflow and NW BPM as a major step towards
process automation at GBI, how the Workflow works, Workflow
Builder challenge
Online Process Management at GBI / Part 4 WebDynpro goes iPhone at GBI
Online Process Management at GBI / Part 5 (in progress)
Providing and consuming WebServices at GBI, SAP Mobile
Platform at GBI
Online Process Management at GBI / Part 6 (in progress) BI at GBI, GBI goes HANA
Online Process Management at GBI / Part 7 GBI goes Sustainable
Link ARIS Publisher

13. Blog http://scn.sap.com/community/uac/blog/2012/10/29/online-process-management-at-gbi-part-1Online Process Management at GBI / part 1 13
Blog Online Process Management at GBI / part 1

14. Question: Is Mapping of Models of Understanding
at GBI with LEAD Frameworks possible?
• Identifying Meta Objects of GBI for mapping with Meta
Objects of LEAD
• Assigning Business Vocabularies of GBI and LEAD
• Comparing Meta Model of GBI and LEAD
• Integrating existing GBI Enterprise Model (GBI
Curriculum and GBI Repository) into LEAD frameworks
• Online Navigation from 3 Layers of LEAD Framework to
GBI Enterprise Model using ARIS Business Publisher
• Better distinction between Business and IT (Model of
Execution) by keeping a good integration (model driven
implementation with SAP Solution Manager)
• Improving Model of Understanding at GBI

15. Mapping LEAD / GBI (Harz) Meta Objects (extract)
Business Lay
Integration of LEAD Object with
Harz IM Objects Type = Categorization
The Relations
between Harz
IM & LEAD IM
Objects
Vision&Mission
Strategy(StrategicBusinessObjective)
Goal(e.g.business,applicationetc)
Objective(CriticalSuccessFactor,Plan,
Forecast,Budget)PerformanceIndicatorTier:Strategic,Tactical
orOperationalValueDriver
PerformanceExpectationPerformanceDriver
OrganizationalConstructBusinessArea
BusinessGroup
BusinessFunction
BusinessResource
BusinessRoles
CompetencyType(Diff,Comp,Non-Core)
CostType(High,Mid,Low)CostFlow(incl.Input/output)Revenue
Object(Business&Information)BusinessRules
Integration of LEAD Object with
Harz IM Objects
Abstraktionsebene / Phasen 1,2,3 Harz Repository Harz Instantiation
Sicht im ARIS-Haus Organisation SolMan / ARIS ARIS / SAP ERP
English
Buchungskreis Instanz siehe unten
Type SAP System Org
Unit
2 X P (primary)
2 X S
(secondary)
P S S
Buchungskreis "GBI"
SAP System Org Unit 2 X P (primary)
2 X S
(secondary)
P S S
Vertriebsabteilung @ GBI
Organizational Unit
3 X P (primary) P P P
Vertriebsabteilung Instanz siehe oben
Organizational Unit-
Type 3 X P (primary) P P P
Vertriebsstelle @ GBI
Position
Person "Mark"
Resource
(person/actor) 1 X P P
Role "LEAD Expert" Instanz siehe oben
Role 3 X P (primary)
same as
process role
(Instance)
P
Organisations-
einheit
Organisations-
einheit
StelleStelle
Person intern Person intern
Personentyp Personentyp
SYS
Typ SAP
Systemorg.-
Einheit
SYS
SAP
Systemorg.-
Einheit
SYS
Typ SAP
Systemorg.-
Einheit
SYS
SAP
Systemorg.-
Einheit
Typ
Organisations-
einheit
Typ
Organisations-
einheit

16. Mapping LEAD Meta Object and GBI Meta Objects
Overview model “Business Layer / Value and Purpose”
16
Secondary RelationsPrimary Relations
Business
Layer
Vision and Mission
Value
and
Purpose
Strategy
Goal
Objective
Performance
Indicator
S Mission 1
S Strategy 1
2
S Vision 1
T
Critical
Success Factor 3
Value Expectation
Value Driver
Performance Expectation
Performance Driver
Value Proposition
Reporting
S Strategy 1
2
T
Critical
Success Factor 3
Source : A part of LEAD Frameworks
S Goal
(Strategic)
1
2
S Goal
(Strategic)
1
2
S
O
Key Performance
Indicator 4
S
O
Key Performance
Indicator 4
S
O
Key Performance
Indicator 4
Link ARIS Publisher
Meta Object Level
applied at GBIMeta Object Tier
applied at GBI
Meta
Object
LEAD
(Entity
Types)
Meta Object GBI
(42 different Object
Types)
LEAD Layer to be continued (Successor)
All Meta Objects
LEAD and GBI
interconnected

17. Mapping LEAD Meta Object and GBI Meta Objects
Business Vocabulary “Business Layer / Value and Purpose”
17
Link ARIS Publisher
Meta Object name LEAD Meta Object name GBI
Goal Goals (strategic)
Objective
Performance
Indicator
Critical
Success
Factors
Key Performance
Indicator
Strategy Strategy

18. Secondary RelationsPrimary Relations
Business
Layer
Business
Com-
petency
Organizational
Construct
Business
Area
Business
Group
Business Capability
Business Function
Business
Resource
Business
Roles
Competency Type
Cost Type
Cost Flow
Revenue
Object (Business &
Information)
Business Owner
Business Rules
Business Compliance
Business Channels
Business Media
Business Workflow
SYS
T
O
Typ SAP
System
Org Unit
1
2
3 SYS
T
O
SAP System
Org Unit
1
2
3
O
Organi-
zational
Unit Type
1
2
3
O
Organi-
zational
Unit
1
2
3
SYS
T
O
Typ SAP
System
Org Unit
1
2
3 SYS
T
O
SAP System
Org Unit
1
2
3
O
Organi-
zational
Unit Type
1
2
3
O
Organi-
zational
Unit
1
2
3
SYS
T
O
Typ SAP
System
Org Unit
1
2
3 SYS
T
O
SAP System
Org Unit
1
2
3
O Value Chain 1
2
O Value Chain 1
2
O
Resource
(Person/Actor)
1
2
3
O Role
2
3
O
Business
Object 3
S
T
Info Cube 2
O 3 O 3
O Money
Transaction
2
O Money
Transaction
2
O Money
Transaction
2
O
Organi-
zational
Unit
1
2
3
O
Organi-
zational
Unit Type
1
2
3
Source : A part of LEAD Frameworks
O Value Chain 1
2
O
Organi-
zational
Unit Type
1
2
3
BPMN:
Lane
Mapping LEAD and GBI meta objects
“Business Layer / Business Competency”
18
Link ARIS Publisher
LEAD
Layer
to be
continued
(Prede-
cessor)

19. Extract of LEAD Meta model “Business Competency”
19
Business
Service
Service...
Service Owner
Value Driver StrategyValue (Goal)
Value (Goal)
Objective
Value Driver Goal
Business Roles
Objective
Business
Service
(Measure)
is created by
creates/
influences
realizes through
is set by
Value (Goal)
Relationship Type
createsDrives Value (Goal)
is set by
realizes through
Responsible for
tracked against
Responsible forBusiness Service
Source : A part of LEAD Frameworks
Link ARIS Publisher

20. 20
Extract of GBI Meta model “Business Competency”
Link ARIS Publisher
Organizational
Construct
Business
Area
Business
Group
Business
Resource
Business
Roles
Is composed
of
Is composed
of
occupies
Business
Process
executes
consists
of
Application Roles
is of
type
Process Step Process Activity

21. Secondary RelationsPrimary Relations
Application
Layer
Data
Data Component
Object
(Information & Data)
Data Entity
Data Table
Data Type
Data Service
Data Flow
Data Owner
Data Rules
Data Compliance
Data Media
Data Channel
T
O
Entitytyp 3
S
T
Info Cube 2
S
T
Fact Table 2
S
T
Fact Table 2
S
T
Fact Table 2
S
T
Fact Table 2
O
Attribut
(ERM)
4 O
FK-Attribut
(ERM)
4 O
K-Attribut
(ERM)
4
O Information Carrier
2
3
O Information Carrier
2
3
Source : A part of LEAD Frameworks
O 3
BPMN:
Pool
O
BPMN:
Data
Object 3
O
BPMN:
Data
Object 3
21
Mapping LEAD and GBI Meta Objects “Application Layer /
Data”
Link ARIS Publisher

22. Mapping LEAD and GBI Meta Objects 1(2)
22
+
Presentation
Process
Function
Data
BusinessLayer
Value&Purpose
Presentation
BusinessCompetency
Process
BusinessServiceBusinessProcess
Function
ApplicationLayer
ApplicationData
Data
BusinesssLayer
Value&Purpose
Vision & Mission
Strategy (Strategic Business Objective)
Goal (e.g. business, application etc)
Objective (Critical Success Factor, Plan, Forecast, Budget)
Performance Indicator (business) Tier: Strategic, Tactical or
Operational
Value Expectation
Value Driver
Performance Expectation
Performance Driver
Value Proposition
Reporting
BusinessCompetency
Organizational Construct
Business Area
Business Group
Business Capability
Business Function
Business Resource
Business Roles
Competency Type (Diff, Comp, Non-Core)
Cost Type ( High, Mid, Low)
Cost Flow (incl. Input/output)
Revenue
Object (Business & Information)
Business Owner
Business Rules
Business Compliance
Business Channels
Business Media
Business Workflow
BusinessService
Service Construct (setup & delivery)
Service Area
Service Group
Business Service
Service Type (Main/Mgmt./Support)
Service Flow (incl. output/input)
Service Tier (Strategic/Tactical/Operational)
Object (Business & Information)
Service Measurements (Level Agreements)
Service Owner
Service Roles
Service Rules
Service Channel
BusinessProcess
Process Area (categorization)
Process Group (categorization)
Business Process
Process Step
Process Activity
Events
Gateways
Object (Business & Information & Data)
Process Type (main/mgmt./support)
Process Flow (incl. Input/output)
Process Roles
Process Rules
Process Measurement (PPI)
Process Owner
ApplicationLayer
Application
Logical Application Component
Physical Application Component
Application Module
Application Feature
Application Function
Application Task
Application Service
Application/System flow
System Measurements
Application/System Reports
Application/System Owner
Application Roles
Object (Information & Data)
Application Rules
Application Compliance
Application Channel
Application Media
Data
Data Component
Object (Information & Data)
Data Entity
Data Table
Data Type (Meta/Master/Transaction)
Data Service
Data Flow
Data Owner
Data Rules
Data Compliance (incl. Security)
Data Media
Data Channel
TechnologyLayer
Platform
Logical Platform Component
Physical Platform Component
Platform Device
Platform Function
Platform Service
Platform Owner
Platform Rules
Platform Compliance (incl. Security)
Platform Media
Platform Channel
Infrastructure
Logical Infrastructure Component
Physical Infrastructure Component
Infrastructure Device
Infrastructure Function
Infrastructure Feature
Infrastructure Service
Infrastructure Owner
Infrastructure Rules
Infrastructure Compliance (incl. Security)
Infrastructure Media
Infrastructure Channel
=

23. Explorer Structure LEAD Framework GBI Curriculum
23
Link ARIS Publisher

24. Mapping LEAD and GBI Meta Objects 2(2)
 Statistics:
– 2 (3) layers / 6 (8) sub layers / 42 (107) meta objects (Primary Relations)
– 4 (5) Meta Object Level
– 3 (3) Meta Object Tiers : (S)trategic, (T)actical, (O)perational
– 2 (3) Meta Object Types : Management, Main, Supporting
 First Conclusion:
– Meta Objects of Business (biggest fraction) and Application Layer overlap by about 60 % (Primary and
Secondary Relations of first 6 sub layers)
– GBI Process Layer dominant (BPMN covers Business Competency/ Processes/ Application/ Data Layer)
– Technology Layer not covered
– Meta Object Levels covered 80 % (applied less)
– Meta Object Tiers completely covered (applied less)
– Focus On Main and Supporting Processes
– Comparison of Meta Models : open
24

25. Enterprise Information Model Repository
GBI to-be
[ARIS BD ]
GBI to-be
[SAP Solution
Manager]
GBI to-be
[SAP ERP]
GBI to-be
[SAP NW BI]
Model structure
Level of information pyramid 1-3 3 3 1,2
Process life cycle phases 2 2-5 1-5 1
4 IT integration layers
Levels of hierarchy 4 3 4 4
1.Presentation layer
Organization Chart
Function (Role, Mask) Allocation Diagram
Company and Department Balanced Scorecard
2.Process layer
E-Business Scenario Diagram
Value Added Chain Diagram
Business Rules eEPC / BPMN Process Diagram
Workflow Container Flow
3.Function layer
Business Services Tree
Objective Diagram
UML Class Diagram
4.Data layer
Info Cube, Dimension and Facts Data as Data
Warehouse Structure Diagram
Data Source Model
KPI Allocation Diagram
System Organization Customizing Diagram
Mask Diagram and WebDynpro Context
All Model types Model types summarized (1,0) (0,3) (0,8) (0,2)
Model driven Implementation of Models of Execution
(Business and IT) with SAP Solution Manager
Legend : ◔ : available only via navigation into SAP ERP
◑ : no interconnection of objects (org structure, Flow of money/material, GUI I/O, no Business Rules, no characteristics)
◕ : incomplete ( ARIS BD Meta model restricted)

26. Conclusion
 Integrating Models of Understanding and Models
of Execution (Business and IT) can improve
teaching ERP (Entire Business Process Life Cycle)
 GBI Model of Understanding (4 IT-Layers) can be
integrated into LEAD Frameworks for better
differentiation of Business and IT view
 Online Prototype ARIS Business Publisher
provides visual experience about
 Meta Objects of Business (biggest fraction) and Application
Layer overlap by 60 % (Model of Understanding)
 42 Jump-in-Points from LEAD into GBI Model of Execution
 Meta Object Tiers completely covered (:
(S)trategic, (T)actical, (O)perational
 Meta Object Levels covered by 80 %
 Focus On Main and Supporting Process Types
http://aris-publisher-server.hs-harz.de:9090/businesspublisher/link.do?login=anonymous&password=anonymous&localeid=1033&ph=3oeq34p&modelguid=eb622ec0-8d05-11e3-3c91-
005056861d3b

27. Outlook
 Comparison of Meta Models (GBI and
LEAD)
 Investigation of better Learning of ERP by
students of Business and IT by entering GBI
Models via LEAD Online Entrance

28. Questions?
Hans-Jürgen Scheruhn
Prof. Dr.
Hochschule Harz University
+49 171 6412849
hscheruhn@hs-harz.de
Name
Title
Company
Cell
E-Mail
For more information:

29. 29

30. © Copyright note on Intellectual Capital: ALL RIGHTS RESERVED
LEADing Practice ApS respects the intellectual property of others, and we ask others to do the same. All information and materials contained in the LEAD frameworks,
methods and approaches with associated tools and templates, such as maps, matrices and models is Intellectual Capital (IC) and Intellectual Property (IP) of LEADing Practice
ApS and limitations apply to the reuse of this IC/IP. The intellectual Property Rights (IPR) consists of information, knowledge, objects, artifacts, experience, insight and/or
ideas, that are structured to enable reuse to deliver value creation and realization.
The LEADing Practice ApS, often referred to as LEAD, intellectual capital is protected by law, including, but not limited to, internationally recognized United States and
European Union IPR copyright law. Except as specifically indicated otherwise in writing, LEADing Practice ApS is the owner of the copyright in the entire LEAD Frameworks
content (including images, text and look and feel attributes) and LEADing Practice ApS reserves all rights in that regard. Use or misuse of the IPR, the trademarks, service
mark or logos is expressly prohibited and may violate country, federal and state law.
LEADing Practice ApS is an open architecture and community open source standard and therefore provides open access to all deliverables for certified LEAD practitioners,
thereby ensuring that modelling principles are applied correctly. A open architecture and open standard community has been set in place to encourage sharing, learning and
reuse of information and thereby increase knowledge among LEAD community practitioners, and with this ultimately improvement of one’s project, engagement and the LEAD
development.
Use of the LEAD frameworks, methods and approaches is restricted to certified LEAD community members in good practitioner standing, who are able to use these items
solely for their non-commercial internal use. Legal access to the detail of LEAD will be provided to you with your membership. Members are prohibited from sharing the LEAD
material in its entirety with other parties who are not members of LEAD community since the concepts and models are protected by intellectual property rights.
Guidelines for LEAD community members using the IPR material
As a LEAD member comes greater personal responsibility and the following intellectual property conditions apply:
 Can be used free of charge for LEAD certified practitioners.
 Cannot be share, copied or made available for non-community member, which are not LEAD certified practitioners.
When using any materials, it must include a source notice – either in an adjacent area or as a footnote – to indicate the source. The source should be specified the following
way : “Source: A part of the LEAD Frameworks” and possibly indicate the LEAD work product family, such as “Part of LEAD Process Framework”.
 Cannot be systematically “given away” – do not download all our content and simply hand it over to other colleagues or clients that are not trained and certified.
To ensure correct usage, any company usage of the LEAD material e.g. templates and tools has to be tailored and agreed upon by LEADing Practice ApS . LEADing Practice
ApS may, in appropriate circumstances and at its discretion, terminate the access/accounts of users who infringe the intellectual property rights and pursue legal action.
Guidelines for non-LEAD community members using the IPR material
 The following conditions apply to use of the LEAD Intellectual Property for non-community members:
 Can be used free of charge for lecturing and research at any University and Business School
Material available at www.LEADingpractice.com can be used in a non-commercial way for knowledge sharing . When using any materials, it must include a source should be
specified the following way : “Source: A part of the LEAD Frameworks” and possibly indicate the LEAD work product family, such as “Part of LEAD Process Framework”.
General guidelines that apply for all LEAD IPR material
 Any use of original texts, graphics, images, screen shots, and other materials from LEAD sources must be approved by LEADing Practice ApS .
 Any material cannot be generally distributed to colleagues, clients and or an undefined audience without written permission from LEADing Practice ApS .
 Cannot be altered or changed (the using company) in any way without explicit written permission from LEADing Practice ApS .
In most cases, the LEADing Practice ApS acts as a distribution channel for the Publisher and Authors of the material provided. LEADing Practice ApS may, in appropriate
circumstances of infringement of the intellectual property rights pursue legal action. For questions, please get in touch with us at info@LEADingPractice.com.