Enterprise Models and Enterprise Management Models and Enterprise Management Architecture

1
Enterprise Models andEnterprise Management
ModelsandEnterprise Management Architecture
2
E/EM Models and EM Architectures

• Enterprise Meta Model
• Basic questions answered
• What is the enterprise doing?
• How is it doing what it does?
• What information needs the enterprise to do what
  it does?

EMM
3
E/EM Models and EM Architectures

• Enterprise Meta Model
• Enterprise Model
• Enterprise Management Model
• Enterprise Management Architecture

EMM
4
E/EM Models and EM Architectures

• Business Actions as the Common Denominator

5
E/EM Models and EM Architectures

• Business Actions
• Business Actions are the means to express
• what enterprises are doing
• how enterprises do what they intend to do

Actions
6
E/EM Models and EM Architectures

• E Model
• What Business Actions are are performed in an
  enterprise
• EM Model
• How must Business Actions be performed to meet a
  business objective
• EM Architecture
• A denotation of the
• Business Actions of Concern and of how the
  Business Actions will be performed

Actions
7
E/EM Models and EM Architectures

• Business Actions
• Business Actions are conducted to meet a business
  objective
• Business Action can be conducted only if
  resources are made available to them.
• Business Actions require Information Resources
  and other Resources (not of concern for our
  models)

R
IR
IR
...
A
IP
IP
...
P
8
E/EM Models and EM Architectures

• Business Actions
• Business Actions produce, when conducted,
  products.
• The products produced in Business Actions may be
  either Information Products or other Products
  (not of concern for our models).

R
IR
IR
...
BA
IP
IP
...
P
9
E/EM Models and EM Architectures

• Business Actions
• Products produced in the conducting of Business
  Actions may be Resources for other Business
  Actions

R
IR
IR
...
BA
IP
IP
...
P
BA
10
E/EM Models and EM Architectures

• Business Actions
• Business Actions may be related with each other.
• Relationships may be defined as
• logical orders
• temporal orders
• any other kind of dependency

R
R
IR
IR
IR
IR
...
...
BA
BA
IP
IP
IP
IP
...
...
P
P
11
E/EM Models and EM Architectures

• Business Actions
• Business Actions encompass Organizations/Actors
  Processes/Tasks Products/Product
  Components Business Objectives/Business
  Functions Infrastructures /Infrastructure
  Componentsin their proper?

12
E/EM Models and EM Architectures

• Business Actions
• Sample Business Actions are Procurement Prod
  uction Development Projects Supply
  Management Customer Relationship
  Management or any Sub-Business Action of the
  Business Actions above.

13
E/EM Models and EM Architectures

• Information Supply and Demand to Business
  Actions

14
E/EM Models and EM Architectures

• Information Resources for Business Actions
• Business Actions may be either
• Information Provider
• or
• Information Recipients
• or
• Information Provider and Information Recipients

Provider
I
Recipient
I
15
E/EM Models and EM Architectures

• Information Resources for Business Actions
• Business Actions may supply information to
  other Receiving Business Actions.
• Receiving Business Actions may demand
  information from other Providing Business
  Actions.

Provider
I
Recipient
I
16
E/EM Models and EM Architectures

• Information for Business Actions
• Business Actions need to have information for
  their orderly execution.
• Business Actions must provide information to
  other Business Actions to enable their orderly
  execution.

R
IR
IR
...
A
IP
IP
...
P
17
E/EM Models and EM Architectures

• Information for Business Actions
• Providing Business Actions may supply
  information to Receiving Business Actions.
• Receiving Business Actions may demandinformatio
  n from Providing Business Actions.

R
IR
IR
...
A
IP
IP
...
P
18
E/EM Models and EM Architectures

• Information for Business Actions
• Information required in the conduct of a Business
  action may be demanded by the Business Action
  from the providing Business Action (Information
  Pull)orInformation required in the conduct of
  a Business Action may be supplied by the
  providing Business Action without prior demand
  (Information Push).

A
Supply
Demand
A
Supply
A
19
E/EM Models and EM Architectures

• Information for Business Actions
• Transient Information
• Information will be transientto a Business
  Action if it is
• demanded by the Business Action
• supplied by a Providing Business Action
• and demanded from and supplied to another
  Receiving Business Action
• or consumed by the Business Action

A
TI
A
TI
A
20
E/EM Models and EM Architectures

• Information for Business Actions
• Persistent Information
• Information will be persistentto a Business
  Action if it is kept by the Business Action for
  its multiple use by the Business Action or by
  other Business Actions.

TI
TI
A
PI
TI
TI
A
21
E/EM Models and EM Architectures

• Information for Business Actions
• Information Creation
• Information will be createdby a Business
  Action.
• The created information is subsequently available
  for the creating Business Action or for any other
  Business Action.

A
IR
22
E/EM Models and EM Architectures

• Information for Business Actions
• Information Consumption
• Information supplied to a Receiving Business
  Action may be consumedby the Receiving
  Business Action and will not be available any
  longer after its consumption.

IR
IR
IR
IR
23
E/EM Models and EM Architectures

• Information for Business Actions
• Information Recording
• Information will be recordedby a Business
  Action.
• The recorded information will subsequently be
  available as persistent information for the
  recording Business Action or for other Business
  Actions.

A
PI
24
E/EM Models and EM Architectures

• Information for Business Actions
• Information Acquisition
• A desired information will be demanded from
  Providing Business Actions.
• The information will be acquiredfrom the
  Providing Business Actions.
• The Providing Business Actions are known in
  advance to the Receiving Business Actions.

A
A
IR
IR
A
25
E/EM Models and EM Architectures

• Information for Business Actions
• Information Search
• A desired information will be demanded from
  Providing Business Actions.
• The information will be searchedin the
  persistent information of the Providing Business
  Actions.
• The Providing Business Actions are known in
  advance to the Receiving Business Actions.

A
PI
A
26
E/EM Models and EM Architectures

• Information for Business Actions
• Information Solicitation
• A desired information will be demanded from
  Providing Business Actions.
• The information will be solicitedfrom the
  Providing Business Actions.
• The Providing Business Actions are not known in
  advance to the Receiving Business Action.

A
27
E/EM Models and EM Architectures

• Information for Business Actions
• Information Distribution
• Information is demanded by Receiving Business
  Actions.
• The information will be distributedto the
  Receiving Business Actions.
• The Receiving Business Actions are known in
  advance to the Providing Business Action.

A
I
A
A
28
E/EM Models and EM Architectures

• Information for Business Actions
• Information Dissemination
• Information is made available by a Providing
  Business Action.
• The Information will be disseminatedto
  Receiving Business Actions.
• The Receiving Business Action are not known in
  advance to the Providing Business Action.

A
I
29
E/EM Models and EM Architectures

• Business Action Models as Enterprise Models

30
E/EM Models and EM Architectures

• MET/MERT Models
• A model is a network created of Model Entity
  Typesand adjacent Model Entity Relationship
  Types
• A MET/MERT - network represents a template for
  the establishment of ME/MER models

...
MET
MET
...
MET
MER
...
...
31
E/EM Models and EM Architectures

• ME/MER Models
• A model is a network created of
• Model Entities
• and
• Model Entity Relationships

...
ME
ME
MER
MER
MER
MER
...
ME
ME
MER
MER
MER
MER
...
...
32
E/EM Models and EM Architectures

• Business Action Models
• Business Action Models are
• one or a number of networks of Action Entity
  Relationshipsand adjacent Action Entities
• Business Action Models can be built by using any
  one of the common modeling concepts like UML.

AE
AE
AER
AE
AER
AER
AE
AE
AER
AE
33
E/EM Models and EM Architectures

• Business Action Models
• Business Action Entities are all actions relevant
  to an enterprise like
• office actions
• management actions
• customer related actions
• supplier related actions

AE
AE
AER
AE
AER
AER
AE
AE
AER
AE
34
E/EM Models and EM Architectures

• Business Action Entity Relationships
• Business Action Entities Relationships are all
  relationships between Business action Entities
  relevant to the enterprise like
• superior/subordinate
• contains
• prior/after

AE
AE
AER
AE
AER
AER
AE
AE
AER
AE
35
E/EM Models and EM Architectures

• Business Action Entity and Business Action
  Entity Relationships
• Business Action Entities are particular Business
  Action Entities.
• Business Action Entity Relationships are
  particular Business Action Entity Relationships.

AE
AE
AER
AE
AER
AER
AE
AE
AER
AE
36
E/EM Models and EM Architectures

• Business Action Entity Types and Business Action
  Entity Relationship Types
• Business Action Entities Types are collections of
  Business Action Entity Types with common
  properties.
• Business Action Entity Relationship Types are
  collections of Business Action Entity
  Relationships with common properties.

AE
AE
AER
AE
AER
AER
AE
AE
AER
AE
37
E/EM Models and EM Architectures

• Business Action Entity Types
• Business Action Entity Types can
  be Procurement Business Entity
  Types Production Business Entity
  Types Development Business Entity
  Types Supply Business Entity Types
  or any Sub-Business Action Entity Type of the
  Business Entity Types above.

AE
AE
AER
AE
AER
AER
AE
AE
AER
AE
38
E/EM Models and EM Architectures

• Business Action Entities
• Business Action Entities can be any particular
  instance of the Business Action Entity
  Typesintroduced before. Since models will always
  be provided for particular enterprises the
  distinction between Business Action Entity Types
  and Business Action Entities becomes irrelevant.
  They will both be called simply business Action
  Entities.

39
E/EM Models and EM Architectures

• Business Action Units in Business Action
  Models
• Business Action Units are subnetworks of the
  Business Action entity/Business Action Entity
  Relationship network that represents a part
  of the Business Action Model or subnetworks of
  the Business action Entity Type/Business Action
  Entity Relationship Type Network
  that represents a part of the Business Action
  Model

AE/T
AE/T
AE/T
U2
AE/T
AE/T
U1
AE/T
40
E/EM Models and EM Architectures

• Business Action Entities
• Business Action Entities act as
• Information Provider
• and
• Information Recipients
• Business Action Entity Relationships characterize
  the
• demand for information from Providing Business
  Action Entities
• and
• supply of information to Receiving Business
  Action entities as they have been explained for
  Business Actions in general

AE
AER
AE
41
E/EM Models and EM Architectures

• Business Action Management Modelsas Enterprise
  Management Models

42
E/EM Models and EM Architectures

• Business Action Management Models
• Business Action Management Models deal with the
  question "Which Business Action Entities
  demand/supply to which other Business Action
  Entities, what Information Entity Type, in
  which logical order, and in which time order?"

?
43
E/EM Models and EM Architectures

• Business Action Management
• Business Action Management aims at the supply of
  the right information at the right
  time to the right Receiving Business
  Actionsaccording to their need to know
  and right to know

AE
AE
AER
IET
IET
AER
AER
IERT
AE
AE
AER
44
E/EM Models and EM Architectures

• Business Action Management
• Business Action Management will be described in
  terms of communication patternsthat denote
  Business Action Entities Information
  Entity Types Business Action Entity
  Relationships Information Entity Relationship
  Types Demand/Supply Orders

AE
AE
AER
IET
IET
AER
AER
IERT
AE
AE
AER
45
E/EM Models and EM Architectures

• Patterns in Business Action Management Models
• Each Business Action Entity may supply and
  demand an arbitrary number of Information
  Entity Types or an arbitrary number of
  information units.

AE
AE
AER
IET
IET
AER
AER
IERT
AE
AE
AER
46
E/EM Models and EM Architectures

• Patterns in Business Action Management
  Models
• Patterns are a denotation for the Demand/Supply
  orders required in coordinated demand/supply.
• They determine what Information Entity Type is
  supplied by which Business Action Entity and what
  Information Entity Type is demanded by which
  Business Action Entity.

AE
AE
AER
IET
IET
AER
AER
IERT
AE
AE
AER
47
E/EM Models and EM Architectures

• Patterns in Business Action Management
  Models
• Patterns are also a denotation for the time
  order in the execution of Business Actions that
  are related over an Business Action Entity
  Relationship.

AE
AE
AER
IET
IET
AER
AER
IERT
AE
AE
AER
48
E/EM Models and EM Architectures

• Patterns in Business Management Models
• Patterns may be depicted as extended UML message
  sequence charts that denote
• Business Action Entities
• Information Entity Types they demand and supply
• time orders for the execution of the Business
  Actions.

AE
AET
...
...
IET
IET
IET
IET
IET
t
49
E/EM Models and EM Architectures

• Business Action Management Models
• Business Action Management Models are subject to
  change through changes of
• the pattern in the Business Action Management
  Model
• or through changes of
• the Business Action Model.

AE
AE
AER
IET
IET
AER
AER
IERT
AE
AE
AER
50
E/EM Models and EM Architectures

• Business Action Management Architectures
  asEnterprise Management Models

51
EIM Architectures

• EIM Architectures
• EIM Architectures are denotations of the
  structural and behavioral properties of
  Model Entities/Model Entity Types and Model
  Entity Relationships/ Model Entity Relationship
  Typesfor any one of the EIM Architecture Models

52
EIM Architectures Basic Definitions

• Architectures are Models
• EIM Architectures denote networks of
  Architecture Entity Relationships and
  adjacent Architecture Entities

AE
AE
AER
53
E/EM Models and EM Architectures

• Business Action Management Architectures
• Business Action Management Architectures deal
  with the following questions Which Business
  Action Management Architecture Entities demand
  and/or supply information to which other
  Business Action Management Architecture
  Entity?

54
E/EM Models and EM Architectures

• Business Action Management Architectures
• A Business Action Management Architecture
  denotes
• Action Management Architecture Entities
• Action Management Architecture Entity
  Relationships
• Information Entities

AMA-E
IE
AMA-ER
AMA-E
55
E/EM Models and EM Architectures

• Business Action Management Architectures
• A Business Action Management Architecture denotes
  an
• Business Action Management Model
• and a
• Communication Model

AE
AE
AER
IE
IE
AER
AER
AER
AE
AE
AER
56
E/EM Models and EM Architectures

• Business Action Management Architectures are
  defined to encompass the Business Action
  Management Architecture Entity Types
• Organization
• Processes
• Products
• Infrastructure
• Business Objectives

57
E/EM Models and EM Architectures

• Business Action Management Architectures are
  defined to encompass the Business Action
  Management Architecture Entity Relationship
  Types
• determines
• supports
• creates and executes
• delivers

58
E/EM Models and EM Architectures

• Business Action Management Architecture Entity
  Types represent with respect to the role in an
  Enterprise concrete or abstract or real or
  virtualinstitutions. Institutions are able to
  act and react and hence to supply and demand
  information.

59
E/EM Models and EM Architectures

• Communication between Business Action
  Management Architecture Entity Types
• Organizations
• supply information to Processes
• demand information from Processes
• demand information from Business Objective
• supply information to Business Objective
• supply information to Infrastructure
• demand Information from Infrastructure

60
E/EM Models and EM Architectures

• Communication between Business Action
  Management Architecture Entity Types
• Processes
• supply and demand information to/from
  Organization
• supply and demand information to/from Product
• supply and demand information to/from Business
  Objective
• supply and demand information to/from
  Infrastructure

61
E/EM Models and EM Architectures

• Communication between Business Action
  Management Architecture Entity Types
• Products
• supply and demand information to/from Processes
• supply and demand information to/from Business
  Objective
• supply and demand information to/from
  Infrastructure

62
E/EM Models and EM Architectures

• Communication between Business Action
  Management Architecture Entity Types
• Business Objectives supply and demand
  information
• to/from Organizations
• to/from Processes
• to/from Products

63
E/EM Models and EM Architectures

• Communication between Business Action
  Management Architecture Entity Types
• Infrastructures supply and demand information
• to/from Organizations
• to/from Processes
• to/from Products

64
E/EM Models and EM Architectures

• Communication Modes

65
E/EM Models and EM Architectures

• Communication Modes
• Communication Modes refer to the communication
  between different Business Action Management
  Architecture Entities in terms
• which Architecture Entity communicates with which
  other Architecture Entity
• logical and time orders in the communication
  between Architecture Entities

AE
AE
IE
IE
IE
IE
66
E/EM Models and EM Architectures

• Communication Modes
• Communication Modes will be specified with
  extended UML-Message Sequence Charts that also
  allow to specify the Information Entities passed
  in the communication between Architecture Entity
  Types

AE
AE
IE
IE
IE
IE
67
E/EM Models and EM Architectures

• Communication Modes
• Push A1 pushes I1 of A1 to A2Pull A2 pulls I2
  of A1 from A1Pull A1 pulls I3 of A2 from A2
• with
• I1 (A1) I2 (A2)I2 (A1) I1 (A2)I3 (A1)
  I2 (A2)

A1
A2
I2
I3
I1
I2
I1
I3
68
IC/ICM Models and ICM Architectures

• Communication Modes
• Time Slots
• Time Slots represent a certain elapsing time
  (i.e. they have a duration).
• Time Slots represent mile stones in a schedule.
• Time slots represent synchronization points in a
  schedule.

A1
A2
I2
I3
I1
I2
I1
I3
Time Slot 1
Time Slot 2
69
E/EM Models and EM Architectures
Sample Communication Mode
EM-B
EM-O
EM-Pr
EM-P
EM-I
...
...
...
...
...
IE
IE
IE
IE
IE
IE
IE
IE
IE
IE
t
70
E/EM Models and EM Architectures

• Communication Modes
• Communication Entities/Entities may communicate
  with each other in two different modes push
  mode and pull mode as it will be depicted
  in a push-pull matrix

71
E/EM Models and EM Architectures

• Push-Pull Matrix
• Push-pull matrixes denote all AE's that push
  IE's AE's that pull IE'sand all IE's as
  they get pushed or pulled by the respective AE

P U L L
AE
AE
AE
AE
PUSH
IE
IE
IE
IE
AE
IE
IE
IE
IE
AE
IE
IE
IE
IE
72
E/EM Models and EM Architectures

• Push-Pull Matrix
• AE1 is an information provider and no information
  recipient
• AE2 is an information provider and an information
  recipient
• AE3 is an information provider and an information
  recipient

P U L L
AE1
AE2
AE3
AE1
PUSH
IE1
IE2
AE2
IE3
IE4
AE3
IE5
73
E/EM Models and EM Architectures

• Sample Push/Pull Matrix
• Push/Pull Matrix for refined (decomposed) Action
  Entitieswith one refinement level.

AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
74
E/EM Models and EM Architectures

• Sample Push/Pull Matrix
• Push/Pull Matrix for refined (decomposed) Action
  Entitieswith two refinement levels.

AE
. . .
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
AE
. . .