DEM Authorizations

1
DEM Authorizations

• Pain or Gain?

2
Agenda

• Part I DEM (authorizations) - Why
• Part II More details about DEM Authorizations
  How
• Part III Golden Rules for DEM Authorizations
  Dos and donts
• Part IV Open Discussion

3
DEM from Strategic Perspective

• DEM. What are we talking about?

From unstructured idea (vision)
Executive Level Increase customer satisfaction
Tactical Management Bring back response time for
urgent calls under 8 hours
To a structured execution (process)
Operational Management Redesign, communicate and
train employees with improved customer support
process
4
DEM from Operational Perspective

• DEM. What are we talking about?

End-users
Dynamic Enterprise Modeling
Information Systems (i.c. Baan)
5
DEM With or Without

• With DEM
• Quickly Implement and Communicate Change in
  Business Strategy
• Deploy best-practices and standardize Procedures
  across the Organization
• Infrastructure to Continuously improve your
  Processes (new ISO regulations!)
• OR Before you can improve your processes, you
  need to know how they look like
• Without DEM..
• You must be a survivor ?

6
DEM Authorizations With or Without

• With DEM
• Less administrator work, because of
  role-decoupling (Baan IVc)
• Less processing time (downtime), because of
  dynamic desktop generation
• Better Process awareness, employees have
  visibility of process as a whole
• Without DEM..

7
Agenda

• Part I DEM (authorizations) - Why
• Part II More details about DEM Authorizations
  How
• Part III Golden Rules for DEM Authorizations
  Dos and donts
• Part IV Open Discussion

8
Part II DEM Authorization - Topics

• Basics of Authorization
• Baan IV Baan ERP Differences
• DEM Authorizations lt-gt Tools Authorizations

9
Basics of Authorization Roles
Role
End-user
10
Basics of Authorization Inheritance
Role
11
Baan IV Baan ERP Differences

• New in Baan ERP
• Authorization Types
• Roles Sub-roles
• Role link in Repository (in IV Ref/Project
  Model)
• Sub-application authorization

12
Baan ERP Authorization Types

• Authorization Type Specific definition what
  user is allowed to do in (Baan)activity (e.g.
  Insert, Modify, Print, Display)
• On Activity in Repository
• On Process Role relationship
• On Process Activity relationship

13
BaanERP Sub-Roles
Sales Manager
Sales Manager does get all authorizations from
the sub roles. This simplifies definition and
maintenance of the roles
Sales Assistant
Sales Clerk
Sales Representative
14
BaanERP Role link in Repository

• Baan IVc role is version independent
• BaanERP 5.0b role is version/project model
  dependent
• BaanERP 5.0c - role is version dependent

15
BaanERP Sub Application Authorization

• Sub Applications are sessions that can be started
  from a main session.
• Default Inherit authorization from parent
  session
• Possibility to exclude role on sub-application
• Additional sessions are created to automate part
  of this task (as off iBaan ERP 5.2) (Baan
  ERP5.0c Solution 122658)

16
Baan IV DEM Authorizations Tools
DEM Domain
Tools Domain
DEM Employee
Baan User

• Package
• Table
• Session
• Field

Role
?
?
Process Activity
Session
17
Baan IV DEM Authorizations Tools

• DEM generates Tools authorizations
• Conclusions
• Tools authorizations (package, table etc.) need
  to be granted for DEM end-users
• Refining DEM authorizations on field level can
  only be defined in Baan Tools

18
Baan IV Tips Tricks

• Grant full authorization for all users in Tools,
  only restricted by Dynamic Menu Browser
• If generation of authorization takes a long time
  take a look into log.tgbrg for error reporting
• Use option exclude lower level maintain on
  lowest (4th) level only print and display
  sessions are taken
• Dont generate desktops in business hours open
  desktops might cause integrity problems
• Or consider to migrate to Baan ERP.

19
Baan ERP DEM Authorizations Tools
DEM Domain
Tools Domain (AMS)
DEM Employee
Baan User
DEM Role
AMS Role

• Table
• Session
• Field, etc.

?
?
Process Activity
Session
Component Application
20
Baan ERP DEM Authorizations Tools

• DEM generated desktop ignores Tools session
  authorizations (not database and field
  authorization)
• Conclusion
• No interference between DEM and Tools anymore

21
Agenda

• Part I DEM (authorizations) - Why
• Part II More details about DEM Authorizations
  How
• Part III Golden Rules for DEM Authorizations
  Dos and donts
• Part IV Open Discussion

22
Part III Golden Rules

• Keep Processes simple (each end-user need to
  understand)
• Model exceptions separately
• Keep Process-Role links simple (make choice at
  which level(s) Roles are linked to Processes)
• Keep Role-structure simple (balance system
  security and complexity)
• Apply Naming conventions (like Baan reference
  models)

23
Agenda

• Part I DEM (authorizations) - Why
• Part II More details about DEM Authorizations
  How
• Part III Golden Rules for DEM Authorizations
  Dos and donts
• Part IV Open Discussion

24
(No Transcript)