Baanboard.com

Go Back   Baanboard.com > BaanERP Tutorial

User login

Frontpage Sponsor

Main

Poll
When will you move your ERP to the cloud?
We are on the cloud already!
24%
Next year
10%
from 2-3 years
5%
from 4-5 years
17%
Never!
44%
Total votes: 41

Baanboard at LinkedIn


Reference Content

Book Navigation

 
Enterprise Modeler
By patvdv at 19 Feb 2008 - 23:45

The Enterprise Modeler assists in developing a vision on:

  • How to functionally structure an organization
  • How to organize the business processes of the organization
  • How to integrate the information system with these business processes

In addition, the Enterprise Modeler can also be used to assist in the actual implementation of the Baan applications by:

  • Setting parameters in BaanERP.
  • Creating BaanERP users, based on the role and employee data of the Enterprise Modeler.
  • Creating the menus and session authorizations for users.

A reference model represents a line of business or business typology and can be built from libraries (repositories) of the following enterprise-modeler components:

  • Business control diagrams
  • Business function models
  • Business process models
  • Organization models

A reference model can serve as a basis for an organization-specific project model.

 

A project model is an organization-specific model that can also be built from a library (repository) of Enterprise Modeler components, and can be based on a reference model.

 

An enterprise-structure model is graphically represented by a map, on which all the participants (enterprise units) in the supply chain are graphically represented at organization/enterprise level. An enterprise-structure model can be used for determining currencies and transaction types between enterprise units.

 

Unlike business functions and business processes, organization diagrams are not a mandatory part of DEM. There is no enforced interdependency between business processes or business functions on the one hand and organization diagrams on the other hand. Nevertheless, it may be useful to define an organization diagram to visualize the organization structure and the roles and responsibilities of departments and employees.

 

In the project model, employees can be linked to the roles that have been defined for the reference-model specific organization diagram. The link between a role and an employee transforms a line-of-business oriented diagram into a company-specific (organization-specific) diagram.

 

Roles and Authorization Types

You can link roles and responsibilities to the following components:

  • Reference models
  • Project models
  • Business processes
  • Business process activities
  • Organization units

You must first define roles as part of a reference model or of a project model before you can link those roles to any of the other components above. Assume that you link roles and responsibilities to business processes and activities. If for a certain process one role carries all the responsibilities for all activities, it is sufficient to link the role and the responsibilities to the process.

 

Examples of roles are: Manager and Secretary. Examples of responsibilities are: maintain data, inform manager, check data.

 

Rules

There are four different types of rules.

 

Consistency rule

An expression containing a combination of business functions on the basis of which one or more other business functions must also be included in a reference or project model.

 

Example:

IF <BF,5> AND <BF,12> THEN <BF,9>

Explanation: If business function 5 and business function 12 are part of a reference model or a project model, business function 9 must also be part of the reference model or the project model.

 

Parameter-setting rule

An expression that determines the value of one or more parameters in a reference model or project model. The value is determined on the basis of a combination of business functions, business processes, and/or static conditions.

 

Example:

IF <BF,1> OR <BF,3> THEN
Parameter: tttld000.user User jjohnson

Explanation: If business function 1 or business function 3 is part of the reference model or the project model, the value of the User parameter is jjohnson.

 

Transformation rule

An expression imposing a unilateral dependency of business processes in relation to business functions. If specific business functions are present in a reference or project model, business processes are automatically incorporated in that reference model or project model.

 

Example:

IF <BF,1> AND <BF,3> THEN
DPL081 MRP Purchase Orders

Explanation: If business functions 1 and 3 are part of the reference model or the project model, business process DPL081 must also be part of the reference model or the project model and can therefore be incorporated automatically.

 

Static-condition

An expression, containing a combination of business functions and/or business processes on the basis of which the value of static conditions is set in a reference or project model.

 

Example:

IF <BF,1> OR <BF,3> THEN
LTC LTC implemented Yes

Explanation: If business function 1 or 3 is part of the reference model or project model, the value of the LTC static condition is Yes.

 

Enterprise-structure modeling

An enterprise-structure model is graphically represented by an enterprise-structure diagram, in which the supply chain at enterprise level is modeled. All agents in the supply chain are graphically represented on a map. Example of agents are:

  • Customers
  • Sales offices
  • Distribution centers
  • Assembly sites
  • Manufacturing sites
  • Suppliers
  • Central planning/purchasing sites

Between enterprise units all kinds of relationships can exist in term of material flows, financial flows, and information flows. The enterprise units from this specific enterprise-structure model are the direct link between the BaanERP application data, such as a warehouse or an entity on the one hand and the model on the other hand. As opposed to business processes, and business-function diagrams and so on, an enterprise-structure diagram is not part of a business model (reference model or project model). A business model, on the contrary, is linked to an enterprise unit, which is part of an enterprise-structure diagram.

 

The enterprise-structure model is the top level of an enterprise model. One level below the enterprise-structure model you find business models (reference or project models). Business models can be linked to enterprise units. This implies that the enterprise unit is the indirect link between an enterprise-structure model and multiple business models.

 

Because a business model is used to set parameters at BaanERP company level, only one business model must be used to represent one BaanERP company. Therefore, different enterprise units must be associated with different (logistic) companies.

 

You cannot directly create an operational enterprise-structure model. First you must create one or more enterprise-structure models, after which you can specify one of those models as the operational model. At runtime the operational enterprise-structure model is used by the BaanERP applications to determine prices and currencies when goods are transferred from one enterprise unit to another.

 

There are two different types of enterprise-structure models:

  • Reference enterprise-structure model: A generic enterprise-structure model that represents a certain branch of industry.
  • Enterprise-structure model: A model that is built for one specific company.

You can directly create a (specific) enterprise-structure model or base it on a (more generic) reference enterprise-structure model.

 


0
No votes yet


All times are GMT +2. The time now is 04:24.


©2001-2017 - Baanboard.com - Baanforums.com