A Model Driven Implementation Approach

1
A Model Driven Implementation Approach
2
The Basic Value of Modelling
Picture
1000 words
Model
10000s words
3
The Basic Value of Modelling
System implementation challenge
System Specs
Business Reqs
System Config
These specifications are so large that they make
War Peace feel like light reading and we are
supposed to arrive at these specifications by
Analysing the business
4
The Basic Value of Modelling

• Modelling models
• Elements in the model must have clearly defined
  relationships to other elements in the model
• Room for interpretation is greatly reduced
• Simplifying communication to the person reading
  the model

5
The Basic Value of Modelling

• Looking at a very simple example

• Object B interacts or has a relationship to
  object A
• Objects each have the following attributes
• Colour
• Shape
• Number of sides
• Size
• In context of the model domain defined, there are
  only 2 objects types
• The objects in this model domain do not interact
  with any other objects.
• Without knowing the rules of the diagram, we
  could even say that object A is on a higher level
  to object B
• You decide, which is easier the explanation...
  The 96 words above or the simple model....

6
Out with the Old... In with the new...
The Ideal ERP Implementation Life-Cycle
Sales
Understand the Business Requirements
Design the Process Requirements
Design the System Requirements
Build the Solution
Implement solution (System delivered what
business required)
Pre-Sales
NO Compromise on the original requirements.
Project delivered at time of business need)
more realistic
The Ideal
ERP Implementation Life-Cycle
Negotiate on original requirements
Understand the GAP System ? Business Requirements
Design the System Requirements
Design the Process Requirements
Understand the Business Requirements
Customise customise the system
Deliver a highly customised solution (Late with
60 buy in)
IT Business are not the biggest friends
Implementation period 9 18 Months
Business Value from month 9-18
7
Breaking the traditional implementation
paradigms...
Pick a technical (ERP) solution
Business Model the technical Solution End-2-End
Match the solutions current ability with the
business requirements
Add work-arounds to processes
Implement the model based solution
Enhance system based on BU\System Module
process requirements
Implementation period 4 Months
Business Value from month 4
A couple of principles assumptions for this
kind of Rapid implementation

• The approach is a model driven approach...?

• The technical solution chosen is a world class
  solution...
• The approach is a model driven approach
• The technical solution does match some of the
  basic business requirements
• The business is willing to temporarily live
  with some work-arounds
• Your focus is on finding a rapid solution to the
  business needs.

Model Overview
Vs. a...
8
Solution Architecture
9
Getting one source of the Truth
Inside
Solution Element
Model
Change one element know what the impact is...
10
All aspects of your Business Solution are
interrelated through a Meta Model
11
Your model architecture should support all the
dimensions of the Meta Model
12
Drive everything from the Models
13
Everything has to come from one source of the
truth
14
Training
Meta Model
2
Flash Cards
1
2
Instructors Guide
3
4
4
1
5
3
6
7
Help Desk
8
8
Drill Practise
JDE Training DB
JDE Live DB
5
6
7
15
Combating the resource challenge using Modelling
Patterns...
No. Of resources
No. Of yrs experience
Move the implementation experience to model
patterns
16
Creating Repeatable patterns for Implementation
Success...
Bus Unit1
Fin Services
Bus Unit2
Product Line A
Meta Models
Construction
Bus Unit3
Retail
Bus Unit4
Manufacturing
Bus Unit5
Bus Unit6
Create Repeatable patterns for Implementation
Success...
17
So exactly what has been achieved...

• Moving towards a model driven architecture (MDA2)
• Primary source of information is not word
  documents with no relationship to one another,
  but interrelated models that
• Give a clearer understanding of Business,
  Processes Systems,
• Speed up understanding of business requirements
  or solutions,
• Enable a better quality of related work done,
• Speed up implementation times for new
  implementations and upgrades,
• Reduce dependency on the short supply for
  experienced ERP consultants,
• Reduce cost to implement and upgrade,
• Move companys IP from the minds of individuals
  to a central repository,
• Have a Central change management repository for
  all changes, whether they are at the Business,
  the Process or the System level,
• Reduction of risk with anything to do with
  Business , Process and Systems

18
What Next

• Have you had a return on investment on your
  Oracle implementation?
• Has the Business truly adopted and integrated it
  in what they do and how they do it?

19
Why a Model Driven Approach?

• Process Streamlining
• Tighter integration of business and system
  process
• To become process orientated enabling you to
  duplicate the processes in multiple businesses
  and business units
• Automation
• Aid with the transition to becoming service based
• Cost reduction
• IP retention in a business repository that is the
  single source of the truth for information
• Informed decision making
• Common Understanding of how things work

20
Questions suggestions...