baan iv enterprise modeler

BAAN IV b Enterprise Modelerfor Microsoft Windows NT

A publication of:

Baan Development B.V.P.O.Box 1433770 AC BarneveldThe Netherlands

Printed in the Netherlands

Baan Development B.V. 1996.All rights reserved.

The information in this documentis subject to change withoutnotice. No part of this documentmay be reproduced, stored ortransmitted in any form or by anymeans, electronic or mechanical,for any purpose, without theexpress written permission ofBaan Development B.V.

Baan Development B.V.assumes no liability for anydamages incurred, directly orindirectly, from any errors,omissions or discrepanciesbetween the software and theinformation contained in thisdocument.

Document number: U7037A US

i Table of contents

Part 1 The module in perspectiveThe business objects

1 The Enterprise Modeler module in perspective 1.1

The Enterprise Modeler module within BAAN IV 1.1The Enterprise Modeler module in relation to other modules 1.1The Enterprise Modeler concept 1.1The business objects of the BRG module 1.4Master data and prerequisites 1.6

2 The Master Data business object 2.1The place and function of Master Data 2.1Mandatory sessions 2.2Maintain Versions (tgbrg1100m000) 2.3Maintain Current Version by User (tgbrg1110m000) 2.7Maintaining version authorizations 2.7Business Function Repository Editor (tgbrg2101m000) 2.8Maintain Business Processes in Repository (tgbrg5100m000) 2.12Maintain Rules (tgbrg7102s000) 2.18Maintain Static Conditions (tgbrg5180m000) 2.20Wizards (tgwzr1100m000) 2.21Maintain Roles (tgbrg8110m000) 2.26Maintain Parameters (tgbrg9100m000) 2.27Other sessions 2.27Copy Version Data to Other Version (tgbrg1200m000) 2.27Delete Components (tgbrg1210m000) 2.28Export Version Dump (tgbrg1235m000) 2.28Import Version Dump (tgbrg1240m000) 2.28Change Password for Version Authorizations (tgbrg1160m000) 2.28Maintain Responsibility Codes (tgbrg8130m000) 2.29Maintain AO Documents (tgbrg8100m000) 2.29Maintain Business Process Activity Categories (tgbrg5125m000) 2.29Maintain Utilities (tgbrg5170m000) 2.30Maintain Templates (tgbrg1170m000) 2.30Maintain Display Identifications (tgbrg1120m000) 2.30

ii

Print Differences between Models (tgbrg1450m000) 2.31Print Where Used 2.31Maintain Runtime Resources (ttdsk3160s000) 2.31Syntax Checker in the Business Process Repository Editor 2.32

3 The Reference Models business object 3.1The place and function of Reference Models 3.1Mandatory sessions 3.2Maintain Reference Models (tgbrg3100m000) 3.2Business Function Model Editor (Reference Model) (tgbrg3101m000) 3.3Maintain Organization Diagrams by Reference Model (tgbrg6104s000) 3.6Maintain Business Processes by Reference Model (tgbrg3160s000) 3.10Maintain Companies by Reference Model (tgbrg3110s000) 3.14Maintain Values by Parameter, Company, and Model (tgbrg9110s000) 3.14Other sessions 3.18Import Model 3.18Check Reference Model Consistency (tgbrg2220m000) 3.18Syntax Checker in the Business Process Model Editor (Reference Model) 3.19

4 The Project Models business object 4.1The place and function of Project Models 4.1Mandatory sessions 4.2Maintain Project Models (tgbrg4100m000) 4.3Import Model 4.3Maintain Employees by Project Model (tgbrg8140s000) 4.4Maintain Optimization Phases by Project Model (tgbrg4130s000) 4.6Business Function Model Editor (Project Model) (tgbrg4101m000) 4.6Maintain Organization Diagrams by Project Model (tgbrg6102s000) 4.11Maintain Business Processes by Project Model (tgbrg4160s000) 4.15Maintain Companies by Project Model (tgbrg4110s000) 4.20Maintain Values by Parameter, Company, and Model (tgbrg9110s000) 4.21Generate User Dialog (tgbrg4250s000) 4.23Other Sessions 4.25Check Project Model Consistency (tgbrg4220m000) 4.25Syntax Checker in the Business Process Model Editor (Project Model) 4.25

iii

Part 2 The Functional Processes

5 The Master Data process 5.1

The Master Data process and its result 5.1The steps in the Master Data process 5.1

6 The Reference Modeling process 6.1

The Reference Modeling process and its result 6.1The steps in the Reference Modeling process 6.1

7 The Project Modeling process 7.1The Project Modeling process and its result 7.1The steps in the Project Modeling process 7.1

Appendix A The Functional Processes A.1

Toolbar in the Business Function Editor A.1Toolbar in the Business Process Editor A.2Toolbar in the Organization Model Editor A.3

vPart OneChapter 1 places the module in the perspective of BAAN IV by describing boththe module and the relationships with other modules. The business objects arelisted, after which the flow between them is described. Finally, the prerequisitesand the master data needed to run this module are listed.

Chapters 2 through 4 describe the business objects by explaining the flow of themandatory steps within each separate business object. An explanation of theoptional steps concludes each chapter.

Part Two

The chapters in this part describe the functional processes of the EnterpriseModeler (BRG) module, by providing a detailed explanation of the flow of eachfunctional process.

About this document

Part 1 The module in perspectiveThe business objects

Part 1 The module in perspective The business objects

1 - 1

This chapter describes the main functions and objectives of the EnterpriseModeler module. Information is given about the modules function within BAANIV and how the module is related to other modules. Additionally, this chapterpresents the modules business objects, then closes with the global set-uprequirements for the module.

The Enterprise Modeler module within BAAN IVThis heading contains a description of the relationships between the EnterpriseModeler module and other parts of the BAAN IV application. In addition, anexplanation is given of the concept of the Enterprise Modeler.

The Enterprise Modeler module in relation to othermodulesUnlike the application packages of BAAN IV, the Enterprise Modeler modulecan be used before the information system is operational.

When a company is thinking about implementing a new information system usingBAAN IV applications, BAAN Target must be used to structure the selectionprocess as well as the actual implementation and optimization of the informationsystem. This is done using the following three corresponding phases of BAANTarget:

1 Selection phaseThis phase is used to develop a vision on implementation and optimization ofthe components of BAAN IV

2 Implementation phaseThis phase is used to implement the vision made in the selection phase

3 Optimization phaseThis phase is used to optimize the operational information system that wasaccomplished using the implementation phase

1 The Enterprise Modeler module inperspective

1 The Enterprise Modeler module in perspective

1 - 2

During these three different phases of Target, the Enterprise Modeler (BRG)module plays the following three roles:

1 The BRG module can function as a decision support system when developinga vision on how to functionally structure an organization, how to organize thebusiness processes of the organization, and how to integrate the informationsystem with these business processes.

2 The BRG module can assist during the implementation of the components ofthe information system based on the vision which was developed by means ofthe BRG module.

3 After the information system has been implemented, the BRG module can beused to monitor the critical success factors of an organization.

Here an explanation is given about how the three roles of the BRG module areused and accomplished in the three different phases of BAAN Target.

During the selection phase, the BRG module can function as a decision supportsystem by visualizing the effects of decisions on the information system and itsusers. For example, decisions on business functions, business processes or theorganization diagram may affect the number of sessions and other (manual)activities that must be implemented. In turn, this will affect the workload of theresponsible employees.

During the implementation phase, the BRG module can be used to support anyadditional decisions. In addition, the BRG module can also be used to assist theactual implementation of the BAAN IV applications by setting the BAAN IVparameters, by generating the BAAN IV users who are going to work with theBAAN IV packages based on the employees which were defined in the BRGmodule, and by creating the user dialogs and session authorizations for theemployees. User dialogs are screens from which the sessions can be activated,that are needed by the employees to accomplish the tasks for which they areresponsible as defined in the BRG module.

During the optimization phase, the BRG module is not only used to assist inmaking additional decisions regarding the BAAN IV components that must beoptimized but also to assist in the actual implementation of the requiredoptimizations. In addition, the BRG module is used to monitor the current statusof the critical success factors of the organization working with the newlyimplemented information system. The values of these critical success factors aredisplayed by means of performance indicators which can be linked to differentbusiness functions or business processes.


1 - 3

The following table visualizes the use of the Enterprise Modeler in the differentphases of BAAN Target:

The three roles of the BRG module in the phases of BAAN TargetRole of theBRG module

SelectionPhase

ImplementationPhase

OptimizationPhase

Decision supportsystem

X X X

Assistingimplementation

X X

Monitoring criticalsuccess factors

X

Based on the roles of the Enterprise Modeler module, four relationships can bedistinguished between the BRG module and other parts of BAAN IV (see Figure1-1). First, there is a relationship between the BRG module and all BAAN IVapplication packages, since the BRG module can be used to set the parameters ofthese packages. Second, there is a relationship between the BRG module and theUser Management functionality of BAAN IV Tools in which the BAAN IV usersare defined. Third, there is a relationship between the BRG module and the MenuManagement functionality of BAAN IV Tools in which the user dialogs arestored. Fourth, there is a relationship between the BRG module and theEnterprise Performance Manager (EIS) module of the BAAN IV Enterprisepackage in which the performance indicators are stored.

BAAN IVTools

Modules inBAAN IV

MCS

ILC

. . .

FRM

PDM . . .

ITM

BAAN IVEnterpriseModeler

BRG

BAAN IVEnterprise

EIS

Menus

User Data

Figure 1-1 The BRG module in BAAN IV


1 - 4

The Enterprise Modeler conceptAs described previously, the BRG module has three roles, namely functioning as adecision support system, assisting in implementation, and monitoring the criticalsuccess factors. The main objective of the Enterprise Modeler is to fulfill one ormore of these roles for a specific organization. This can be done by entering allkinds of data representing the (desired) situation of an organization. Basically, amodel of the (desired) situation of an organization is created from scratch each timea model is to be created for a different organization. The concept of the EnterpriseModeler, however, is that it is more efficient and effective to first create a modelrepresenting a certain type of organization, after which this model can be modifiedto create a more specific model for one organization in particular.

In fact, a number of models have been created representing the best-practicesituation of certain organization typologies. These models are used as a startingpoint in creating organization-specific models based on the differences betweenthe organizations specific situation and the best-practice situation. This is a moreefficient way of working since the only data which must be entered is the datathat differs not all the from the best-practice situation. In addition, this way ofworking is more effective since a comparison can be drawn between the currentand desired situation of a company on the one hand and the best-practicesituation within the corresponding organization typology on the other hand. Thiscomparison can be used during the business re-engineering process.

The business objects of the BRG moduleThe Enterprise Modeler module comprises the following business objects: Master Data Reference Models Project ModelsThese business objects must be used in a certain order to work according to theconcept behind the Enterprise Modeler.

Before any models representing organization typologies (reference models) orspecific organizations (project models) can be made, some master data must beentered. First, a version must be defined for which a model is to be created.Based on this model, the desired BAAN IV components will be selected, theparameters will be set, the user dialogs will be created, and the performanceindicators will be monitored. Second, the components that are used in the modelsmust be defined as master data.


1 - 5

This data includes such components as business functions, business processes,and rules. This master data is placed in a so-called repository, which contains thebuilding blocks for the models that will be created.

Next, the reference models representing the best-practice situation oforganizations with a certain organization typology must be created. Eachreference model consists of a business function model, an organization model,and a business process model. These models describe the business functions in anorganization, the (hierarchical) structure of the organization, and the workingorder of the activities needed to fulfill the business functions. The businessfunction models and business process models of the reference models are built bycopying functions and processes from the repository in which these componentswere predefined.

Finally, the project models representing the situation of a specific organizationcan be created. These models are similar to reference models, except for the factthat they are specific to one organization in particular. In project models, it is alsopossible to define business function variants representing different ways ofaccomplishing a business function. For these variants, optimization relationshipscan be defined, which represent the recommended paths that must be followedwhen switching from one way of working to a more optimized manner. Thebusiness function models and business process models of the project models arebuilt by copying functions and processes from the repository in which thesecomponents must have been predefined. Figure 1-2 shows the relationshipsbetween the three business objects of the Enterprise Modeler module.Lines 1 through 3 show the described order. Line 4 shows an option which isused if a newly created project model describes the best-practice situation withina certain organization typology so accurately that the project model can be usedas a reference model in the future.

1 Reference models consist of a number of components available in therepository (as specified in the Master Data business object).

2 Project models are often based on reference models.3 Project models consist of a number of components available in the repository

(either newly included or indirectly by means of the reference model).4 Reference models can be based on project models.


1 - 6

3

1

4

Master Data

Reference Models

Project Models

2

Figure 1-2 The flow between the business objects in the BRG module

Master data and prerequisitesFor the Enterprise Modeler, the use of a monitor with a resolution of at least 1024by 768 pixels is recommended, although monitors with less resolution will alsowork.

2 - 1

This chapter describes the Master Data business object and gives informationabout the business objects functions. In addition, the chapter identifies andexplains the mandatory and other sessions related to the business object.

The place and function of Master DataThe Master Data business object is used to define version and attach users to acurrent version. in addition, this business object is used to enter such master dataas business functions, business processes, and rules in the repository. This data isused in the reference models and project models.Prior to creating or maintaining a reference model or project model, the requiredmaster data, such as business functions, business processes, and rules, must bedefined in the repository. It is also possible to add the master data whilemodeling, but the idea is that the data used in the models must be defined asmaster data in the repository. This does not mean that, each time a referencemodel is created, new master data must be entered. On the contrary, this meansthat master data which has been defined can be used in an unlimited number ofmodels.

2 The Master Data business object


2 - 2

Mandatory sessions

Maintain Roles(tgbrg8110m000)

Maintain Parameters(tgbrg9100m000)

Maintain StaticConditions

(tgbrg5180m000)

Maintain Versions(tgbrg1100m000)

Maintain Current Versionby User

(tgbrg1110m000)

Business FunctionRepository Editor(tgbrg2101m000)

Business ProcessRepository Editor(tgbrg5100m000)

Maintain Rules(tgbrg7102m000)

Maintain VersionAuthorization by User

(tgbrg1150m000)

Maintain User Authorizationfor all Versions

(tgbrg1140m000)

Maintain UserAuthorization by Version

(tgbrg1155m000)

The three sessions aboveare optional, but it is recom-mended to use at least one of them to set the correct version authorizations.

Wizards(tgwzr1100m000)

Figure 2-1 The mandatory sessions in the Master Data business object


2 - 3

Maintain Versions (tgbrg1100m000)Reference models, project models, and related components must be uniquelyidentifiable. This is done by means of a version code. Considering the fact thatversions can be derived from other versions, it is possible to create a user-specificversion of a business model or model component or to modify an existing modelwith user-specific components.

The derived-from structure indicates that a new version which is derived from asource version includes all the models and components of the source versionwithout actually copying them to the new version. This means that anymodifications in the source version (even after the derived-from structure hasbeen defined) will apply to the new version. Modifications in the new version,however, only apply to that version.

The following table shows the version-dependent components as well as theversion-independent components:

Version dependency of componentsVersion-dependent components Version-independent componentsbusiness functions rolesbusiness processes responsibilitieswizards AO documentsreference models business function categoriesproject models business process categoriesstatic conditions business process activity categoriesrules organization component typesutilitiesemployees (through project models)roles by employee (through projectmodels)

The Maintain Versions (tgbrg1100m000) session is used to name new versionsand to define such data as the version from which the new version was derived (ifapplicable), the status, and the owner.If a new version is inserted, BAAN IV will ask whether or not the authorizationmechanism should be used for this new version. If the answer is Yes, the personwho created this new version is authorized for this version. If the answer is No,version authorizations are not generated at this point in time.


2 - 4

At a later moment authorizations can still be generated. For more information onversion authorizations see Maintaining version authorizations.

The version of the models and their components is not related to the differentversions, releases, and customizations of the different BAAN IV softwarepackages.

As explained in chapter 1, reference models and project models are created usinglinks to the business functions and business processes as defined in the respectiverepositories of a given version. This means that if, for example, a description of abusiness function referred to as One which is used in one reference model mustbe changed, this can only be done in the repository. Unfortunately this also meansthat if this business function is already used in a number of other reference orproject models, and the description is changed in the repository, this change willautomatically be implemented in the reference and project models of the sameversion. This situation is displayed in Figure 2-2.

In this example, if One were to be changed into Ten, this change will beimplemented in both reference models, whereas this change should only beimplemented in reference model 1. The dotted lines indicate that the descriptionsof business functions in reference (and project) models are retrieved from therepository.

BusinessFunction

Repository

One

Two

Three

Four

Business Function Modelin Reference Model 1

ThreeTwo

One

Business Function Modelin Reference Model 2

Three Four

One

Version 1

Figure 2-2 Changing the repository without version management

The problem described above is solved through version management. In theexample, a new version must be defined which is derived from the version thatwas being used.

NOTE


2 - 5

After this version has been defined, the components of the previous version(including the repositories, reference models, and project models) can be used,although they are not physical copies but only available through a link. In theexample, the descriptions and the places of the business functions in therepository of Version 2 are retrieved from the repository of Version 1. Thedescriptions of the business functions in both reference models of Version 2 arealso retrieved from the repository of Version 2, which means they are indirectlyretrieved from Version 1 as result of the derived-from structure. The place of thebusiness functions in the reference models of Version 2 are derived from thereference models of Version 1. This means that nothing is stored in Version 2,except for the link to Version 1.

This situation is displayed in Figure 2-3, The dotted circles in the repository ofVersion 2 indicate that they cannot be modified, since they are physically onlyavailable in Version 1. In the real business function repository editor, thebusiness functions that are derived-from other versions are dimmed.

O ne

Tw o

Three

Four

ThreeTw o

O ne

Three Four

O ne

Version 2derived from

Version 1

BusinessFunction

Repository

O ne

Tw o

Three

Four

Business Function M odelin R eference M odel 1

ThreeTw o

O ne


Three Four

O ne

Version 1

Figure 2-3 Creating a derived-from version


2 - 6

After a new version has been created, the description of the business function canbe changed. In this example, the description One in Reference Model 1 must bechanged to Ten. Before the description can be changed, it must first be copied tothe current version since it should not be changed in Version 1. Copying to thecurrent version means placing a physical copy of the business function in therepository of Version 2 and breaking the link with the business function in theprevious version. After the description in the business function repository ofVersion 2 has been changed to Ten, the business function in both referencemodels will also automatically be changed, since these models use thecomponents as defined in the repository of Version 2. The advantage of thisapproach is clarified by means of Figure 2-4 which indicates that ReferenceModel 2 should not be used in Version 2 but in Version 1. Figure 2-4 shows thesituation after the description has been copied to the current version and after thedescription has been changed in the repository. Business function Ten (or Onebefore the description was changed) is now physically available in Version 2.

Use th is one !

Ten

Tw o

Three

Four

Version 2derived from

Version 1

ThreeTw o

Ten

Three Four

TenCopied to

current ve rsion

BusinessFunction

Repository

O ne

Tw o

Three

Four


ThreeTw o

O ne


Three Four

O ne

Version 1

Do not use !

Figure 2-4 Changing the repository using version management


2 - 7

This may seem a lot of work for simply changing a description. It may even seemthat it would be easier to define a new business function Ten in the repository, butfor other components such as business processes, or even reference or projectmodels, the same example applies. This places the creation of a new version in abroader perspective, because the components do not have to be created fromscratch. Instead, only the changes must be implemented and stored.

Maintain Current Version by User (tgbrg1110m000)This session is used to change the current version of the user on the basis ofwhich the model modifications and additions are made. Whenever a version-dependent session is activated, while the current version is not set, the user isnotified of this by means of a message dialog. If the user clicks on the OK buttonin the dialog, the Maintain Current Version by User (tgbrg1110m000) session isactivated to specify the current version.

If a component must be modified in a version that is derived from a previousversion, the component must be copied to the current version before modificationscan be made. This is done using the corresponding menu item from the Applicationmenu, or the corresponding button. If the component is not copied to the currentversion, a message dialog will notify the user of this.

After the component has been copied to the current version, the component isactually available in the new version whereas before there was only a link fromthe current version to the component in the previous version.See also Figure 2-4.

Maintaining version authorizationsAs mentioned before, it is necessary to specify whether the authorizationmechanism should be used if a new version is being defined. If so, BAAN IVautomatically creates the authorization for the user for that version. However, it isalso possible to set version authorizations using one or more of the three sessionsdiscussed in this section. Before these sessions are discussed, it is important toknow that if not one user has been authorized for a specific version, all users areallowed to use that version. A result of this is that using one or more of thesethree sessions is optional, but still recommended.

NOTE


2 - 8

Maintain User Authorization for all Versions (tgbrg1140m000)This session can be used to quickly authorize one or more users for all versions,by only specifying the user names. Whenever a user is included in this session, heor she can access all versions, including versions which are created after the userwas entered into this session.

In the light of the fact that not authorizing a user for a version, results in all usersbeing able to use that version, it is important to know that setting authorizationsusing this session, is not seen as specifically authorizing a user for a version. Thismeans that if only this session is used to (implicitly) authorize users for thisversion, all other users are still allowed to use the version.

Maintain Version Authorization by User (tgbrg1150m000)This session can be used to authorize a specific user for one or more versions.Whenever this is done for one user only, all other users can not use the specifiedversions (anymore).

Maintain User Authorization by Version (tgbrg1155m000)This session can be used to authorize a number of users for a specific version.Whenever this is done, it means that all other users can not use the specifiedversion (anymore).For the people responsible for setting the version authorizations, it is important toknow that the check on authorization is done only when changing a users currentversion. This means that if, before setting the authorizations for a version, thecurrent version of a user has already been set to that version, the user cancontinue to work with this version until the current version is changed. Afterchanging the version, it will not be possible to set the current version back to theprotected version.

Business Function Repository Editor (tgbrg2101m000)In the Enterprise Modeler, business functions are used to define relevant businessissues within organization typologies or within specific organizations, and tospecify in which implementation/optimization phases these are to be used. Thepresence or absence of these business functions during the implementation phaseand/or the optimization phase(s) will later on be used to select and configure thebusiness processes and to set the parameters of the BAAN applications for eachphase.

NOTE

NOTE


2 - 9

Whenever the BAAN application is configured for one of theseimplementation/optimization phases, only the sessions that are used in theactivated (parts of the) business processes are available for the users.This session is used to add new business functions to the repository or to modifyexisting business functions in the repository. Afterwards these business functionscan be used as a basis for reference models and project models. Filling therepository is not a goal in itself, but is only needed to define the building blocksfor the business function models in the reference and project models.The business function repository is divided in versions in which the businessfunctions are stored. This means that new business functions that are to be addedto a new version can also be copied from other versions. This is done by meansof the Copy Version Data to Other Version (tgbrg1200m000) session.A business function model can only be edited by one user at the same time.

Business functions can be defined in a hierarchical structure which means that afunction may have subfunctions. This structure is used as an aid while definingthe business functions and does not have to be maintained in the reference modelsand project models. For example, a function A can be defined in the repositorywith subfunctions A1 and A2. In a reference model, these three businessfunctions could be used to create a function A2 with a subfunction A with asub(sub)function A1.Commands in the Business Function Repository EditorA number of commands are available in the Business Function Repository Editorwhich can be used while editing in the repository. Most commands can beactivated from the toolbar or the menu bar although some of the commandsbelow are only available through the menu bar. For more information on thetoolbar of the Business Function Editor, see Appendix A.

1 Adding business functions Business functions are added by means of the Add button and clicking on

the place where the business function must be located. To deactivate thepossibility to add business functions, click on the Arrow button. To deletecomponents, use the Delete button.

NOTE


2 - 10

2 Linking performance indicators Existing predefined performance indicators (PIs) can be linked to business

functions by clicking on the business function and selecting the Add PIbutton to activate the Display Performance Indicators (tgeis0511s000)session. This session can be used to link one or more PIs to the businessfunction. To link two or more PIs at once, press the key whileselecting the remaining PIs.

To view which PIs have been linked to a certain business function, clickon the PI icon located under the business function, which opens a dialogbox with currently linked PIs. To close this dialog box, click on the buttonin the right upper corner of the box.

To modify the descriptions of PIs or to link text to the PIs, the MaintainPerformance Indicators by Business Function (tgbrg2130s000) session canbe activated by clicking on the button in front of the PI which must bemodified. From within this session, the Maintain Performance Indicators(tgeis0111m000) session can be activated to create new performanceindicators.

To view the values of PIs, select a PI by clicking on the description in thedialog box, select the Performance Indicator menu item from the Viewmenu to activate the Chart Manager which displays the selected PI.

To remove a PI from a business function, select a PI by clicking on thedescription in the dialog box and click on the Delete button.

3 Navigating through the business function structure Double-click on a business function to be able to go to a lower level,

where subfunctions can be added. This level can also be accessed bymeans of the Zoom In button. To go back to the main function the ZoomOut button can be used. The different levels can also be selected using thebox in the left bottom corner of the screen, which contains the descriptionsof the different levels that are available.

4 Adding help text Help text can be linked to a business function by selecting the business

function and clicking on the Text button in the toolbar. The link can beremoved by clicking on the T icon underneath the business function andselecting the Disconnect option from the File menu in the Text Editor. Thehelp text created in the repository is referred to as a (general) businessfunction help text.


2 - 11

5 Modifying business function basic data The basic data of business functions is modified in the Maintain Business

Functions (tgbrg2100s000) session, which is activated by clicking on abusiness function and clicking on the Change button. This session can alsobe used to link categories to a business function. Before a function can becategorized, the categories must have been defined in the MaintainBusiness Function Categories (tgbrg2120s000) session, which can beactivated using the Categories button. By means of this session, it ispossible to define the different categories that are needed, including thecategories that will be linked to other business functions. A wizard canalso be attached to a business function. In the project model, the wizardsmust be used to set parameter values. These wizards must have beendefined in the Wizards (tgwzr110m000) session.If a business function is only present through the derived-from versionstructure, the Copy to Curr. V. button can be used to make a copy of thebusiness function which is then physically placed in the users currentversion. This functionality is required because data can only modifiedwhen the components are of the same version as the users current version.

6 Viewing processes linked to business functions For some business functions, relationships with business processes have

been defined using rules. By selecting a business function and selectingthe Processes option from the View menu, the processes (if any) whichhave been linked to the selected business function are listed. The businessprocesses can be displayed by selecting one of the listed processes.Normally speaking, business processes are only linked to the next-to-lowest level of business functions. The reason for this is that this level isused to select processes while the lowest level of business functions isused to configure business processes. See Figure 2-5.


2 - 12

?

Processes are se lectedbased on the

next-to-low est level o fbusiness functions

S tatic conditions are se tbased on the lowest leve l of

business functions

Business Function M odel Business P rocess

Figure 2-5 Relationship between business functions and business processes

7 Viewing business functions in tree style versus bubble style After opening the business function repository, the business functions are

shown by means of bubbles, which are defined over a number of levels.These levels can be reached by zooming in and zooming out. It is alsopossible to display the functions by means of a tree structure, which showsthe codes and descriptions of the business functions by means of a list. Inthis list, the different levels are represented by means of indented text. Totoggle between these two ways of displaying the business functions, selectthe Bubbles option or the Tree option from the View menu.

8 Modifying rules By choosing the Rules option from the Rules menu, it is possible to

activate the Maintain Rules (tgbrg7102s000) session.

Business Process Repository Editor (tgbrg5100m000)Based on the presence or absence of business functions in the business functionmodel, business processes can be selected and configured for eachimplementation/optimization phase. If the BAAN application is configured forone of these phases, only the sessions used in the activated (parts of the) businessprocesses can be used. To define these business processes this session can beused, which is activated by selecting the Business Process Repository Editoroption in the Menu Browser.

This session is used to add new business processes to the repository, or to modifyexisting business processes in the repository. These business processes can beused as a basis for the reference models and project models. Filling the repository


2 - 13

is not a goal in itself, but is necessary to define the building blocks for thebusiness process models in the reference and project models.The first form of this session is used to insert new data or to modify existing datarelated to business processes in the repository. In addition to being used as abasis for the reference and project models, it is possible to link text (process workinstructions) to these business processes. The second form of this session can beused to categorize the business process selected on the first form as well as toattach a utility to that process. Processes can be categorized to group them basedon such aspects of the process as the level or type of the process. Before aprocess can be categorized on this form, the categories must have been defined inthe Maintain Business Process Categories (tgbrg5105s000) session, which can beactivated using the Categories button on the second form. By means of thissession, it is possible to define the different categories that are needed, includingthe categories that will be linked to other processes.

The second form can also be used to attach a utility to the process. A utilitycontains one or more BAAN IV sessions that can be used while executingactivities in processes. Before a utility can be attached to a process, the utilitymust have been defined in the Maintain Utilities (tgbrg5170s000) session, whichcan be activated using the Utilities button on the second form.

The business process repository is divided in different versions in which thebusiness processes are stored. This means that if new business processes are to beadded to the repository, they can be copied from other versions by means of theCopy Version Data to Other Version (tgbrg1200m000) session.The buttons that can be selected in the Business Process Repository Editor(tgbrg5100m000) session are mainly used to maintain four groups of data relatedto business processes. A fifth button, however, is used to view the businessprocesses listed in this session in a graphical and structured way. A sixth button isused to check the syntax of a range of business processes. The use of these sixbuttons is explained below.


2 - 14

Button Activated sessionEditor Business Process Repository Editor (tgbrg5101m000)View Repository Business Process Repository BrowserRules Maintain Rules (tgbrg7102s000)Static Cond. Maintain Static Conditions (tgbrg5180s000)Dynamic Cond. Maintain Dynamic Conditions (tgbrg5140s000)Check Syntax Syntax Check Business Processes (tgbrg5210s000)

Business Process Repository Editor (tgbrg5101m000)This session is used to edit the business processes based on the Petri net method.This means that activities, states, control activities, conditions, and relationshipsmust be defined in this session.

Commands in the Business Process Repository EditorA number of commands are available in the Business Process Repository Editorwhich can be used while editing in the repository. Most commands can beactivated from the toolbar or the menu bar although some of the commandsbelow are only available through the menu bar. For more information on thetoolbar of the Business Process Editor, see Appendix A.

Four of the buttons in the editor and the bottom six options of the Add option ofthe Edit menu can be used, but are not explained in this module description. Thereason for this is that, even though they can be used for modeling, BAAN IVbdoes not use them functionally. In a later version, BAAN IV will actually workwith these options, which will therefore be explained in another version of thismodule description.

1 Adding business process components The components of business processes are added by selecting the button

corresponding to the type of component that must be added, and clickingon the place where the component must be located.

NOTE


2 - 15

To deactivate the possibility to add components, click on the Arrowbutton. If components are added, the editor will take the Petri net rulesinto account. This means that, for example, it is not possible to directlylink two activities without defining a state between the activities.Based on these Petri net rules, the editor also anticipates the fact that astate must be defined after an activity. This means that, after an activityhas been added using the Add Activity button and clicking on the desiredlocation, clicking on the defined position will result in the editor adding astate. Next, it is possible to select the position of the next componentwhich will automatically be an activity. This means that it is not necessaryto continue selecting the button corresponding to the type of componentthat is to be added. This anticipation by the editor only works if theAutomatic Relation option has been selected from the Options menu.

2 Modifying component basic data The basic data of the components can be modified by double-clicking on a

component. Depending on the type of component, this will activate one ofthe following sessions:

Maintain Business Process States (tgbrg5130m000)This session is used to define the basic data of the states.

Maintain Business Process Activities (tgbrg5122m000)This session is used to define the basic data of activities, including controlactivities.

Maintain Conditions (tgbrg5145m000)This session is used to define the conditions related to the relationships(arrows) leaving control activities. Conditions are used to specify when anarrow must be active and when not. This is done by specifying the static ordynamic condition influencing this arrow and by specifying if the arrowmust be followed when the value of the condition is set to Yes or when thevalue is set to No. From this session, the Maintain Static Conditions(tgbrg5180s000) and the Maintain Dynamic Conditions (tgbrg5140s000)sessions can be activated to define the static and dynamic conditions to beused in the Maintain Conditions (tgbrg5145m000) session.


2 - 16

3 Adding help text Help text can be linked to activities, states, and control activities by

selecting an activity, state or control activity and clicking on the Textbutton. The link can be removed by double-clicking on the T icon next tothe component and choosing the Disconnect option from the File menu inthe text editor. These help texts are referred to as activity workinstructions.

Business Process Repository BrowserThis session is used to list the business processes in the repository in a graphicalway based on their structure. The way in which they are listed can be comparedto the Menu Browser. Instead of listing the business processes underneath eachother without any indication of the relationships between them (as done in theBusiness Process Repository Editor (tgbrg5100m000) session), the BusinessProcess Repository Browser shows the business processes based on the structurethat is created by including the subdiagrams in a higher level business process.Figure 2-5 shows the difference between the two ways of listing businessprocesses.

Maintain Rules (tgbrg7102m000)This session is used to define the rules that are needed to work with theEnterprise Modeler.

Maintain Static Conditions (tgbrg5180s000)This session is used to define the static conditions used in the EnterpriseModeler.

Maintain Dynamic Conditions (tgbrg5140s000)This session is used to define dynamic conditions. Since dynamic conditions arenot yet used in the Enterprise Modeler of BAAN IVb, this session will not bediscussed in this book.

Syntax Check Business Processes (tgbrg5210s000)This session is used check a range of business processes on the correct use of thePetri net syntax. As a result any loops, deadlocks or unconnected states will bedetected.


2 - 17

AboveThe Maintain BusinessProcesses in Repository(tgbrg5100m000) session isused to maintain the businessprocesses belonging to thecurrent version. Only thebusiness process numbers canbe used to indicate the structureof the processes.

LeftThe Business ProcessRepository Browser is used todisplay the business processesbelonging to the current version.The structure of the processesis displayed graphically.

Figure 2-6 Difference between the two ways of listing business processes

Maintain Rules (tgbrg7102s000)This session is used to define the rules that are needed to work with theEnterprise Modeler. After this session has been activated, it is necessary tospecify which of the following types of rules must be inserted or maintained:

1 ConsistencyThis type of rule is used to check consistency between business functions orbetween business processes.


2 - 18

2 Set ParametersThis type of rule is used to determine the value of parameters, depending onthe business functions that are to be used.

3 TransformationThis type of rule is used to select certain business processes based on thebusiness functions that are to be used.

4 Set Static ConditionsThis type of rule is used to choose between the arrows leaving the controlactivities. If the defined rule evaluates to true, the static conditions based onthis rule are set to Yes. Upon leaving a control activity, some arrow(s) must befollowed if the static condition is set to Yes, while the other arrow(s) must befollowed if the static condition is set to No. The conditions are static becausethe rules relate to implementation decisions, which are usually made when anew implementation/optimization phase is started (static), and not each time aprocess is executed (dynamic).

For each rule, a condition must be defined (the IF clause) as well as a set ofactions which must be done if the condition is met (the THEN clause). For rulesof type Consistency, the IF clause and the THEN clause are entered in the texteditor. For the other three types of rules, the rule condition must be defined in thetext editor while the THEN clause is specified in a subsession, which is openedautomatically underneath the Maintain Rules (tgbrg7102s000) session. In the texteditor, a certain syntax must be used to define the rules. For more information onthis syntax, see the related help text.

A zoom session can be activated from the Options menu in the text editor, whichcan be used to zoom to lists of business functions, business processes, and staticconditions. This zoom session can also be used to automatically insert statements.

Entering rules of type ConsistencyIf a rule of type Consistency is inserted or maintained, both the IF clause and theTHEN clause must be entered by means of the same text editor. This editor isactivated by clicking on the Rule Condition button.

Entering rules of type Set ParametersIf a rule of type Set Parameters is inserted or maintained, only the IF clause mustbe entered by means of the text editor. This editor is activated by clicking on theRule Condition button. The THEN clause must be entered in the ParameterSetting by Rule (tgbrg7117s000) session, which is activated automatically. This

NOTE


2 - 19

session is used to define the parameters and parameter values that must be set ifthe condition of the rule is met.

Entering rules of type TransformationIf a rule of type Transformation is inserted or maintained, only the IF clause mustbe entered by means of the text editor. This editor is activated by clicking on theRule Condition button. The THEN clause must be entered in the Select BusinessProcesses by Rule (tgbrg7127s000) session, which is activated automatically.This session is used to define the business processes that are to be selected if thecondition of the rule is met.

Entering rules of type Set Static ConditionsIf a rule of type Set Static Conditions is inserted or maintained, only the IF clausemust be entered by means of the text editor. This editor is activated by clickingon the Rule Condition button. The THEN clause must be entered in the Set StaticConditions by Rule (tgbrg7137s000) session, which is activated automatically.This session is used to insert the static conditions for which the value mustchange as well as the value to which the static condition must change (Yes or No)if the condition of the rule is met.

If rules of type Set Static Conditions must be defined, the static conditions musthave been previously defined. Therefore, if a rule must be created for a new staticcondition, the Maintain Static Conditions (tgbrg5180m000) session, must be usedfirst.

If the rules and static conditions that are used to determine which arrow must befollowed leaving a control activity are defined, two possibilities can bedistinguished.

Two of these possibilities are plausible, as long as only one of these is used at atime, namely:1 by default, a static condition is set to No. If a rule related to that static

condition is met, the static condition is set to Yes. Since this method has beenused for the models in BAAN IV, the default values of the static conditions isalways No while the Set Static Conditions by Rule (tgbrg7137s000) sessiononly includes the conditions that must be set to Yes.

2 by default, a static condition is set to Yes. If a rule is met, the static conditionis set to No. In this case the default values of the static conditions is alwaysYes and the Set Static Conditions by Rule (tgbrg7137s000) session onlyincludes the conditions that must be set to No. Although this is a plausiblepossibility, the first possibility is used as a standard.

NOTE 1

NOTE 2


2 - 20

Maintain Static Conditions (tgbrg5180m000)Each of the control activities in the business process editor represents a questionthat must be answered. The answer is placed in a variable referred to as acondition (either static or dynamic). By default, the value of these conditions isset to No. Rules are required to change this value to Yes depending on thesituation. Before any rules can be defined to change the value of conditions, theseconditions must be defined by means of this session.

The static conditions defined in this session are used throughout the EnterpriseModeler. Static conditions are used to determine which arrow(s) must befollowed upon leaving the control activities in the processes. Some arrow(s) mustbe followed if the static condition is set to Yes, while the other arrow(s) must befollowed if the static condition is set to No. The value of static conditions isdetermined by means of rules The conditions are static because the rules that areused to choose between arrows relate to implementation decisions, which areusually only made when a new implementation/optimization phase is started(static), and not every time that the process is executed (dynamic).The default values of the conditions as defined in this session are used todetermine the value of a static condition when the rule does not evaluate to true,or does not evaluate at all. As a standard, the default value must be set to No,while only the rules that change the value of static conditions to Yes must bedefined.

To find out where certain static conditions are used, the Print Where Used StaticConditions (tgbrg5481s000) session can be activated by clicking on the WhereUsed button.

Wizards (tgwzr1100m000)Wizards are a special form of user assistance for automating tasks throughdialogs with users. In the Enterprise Modeler, wizards can be linked to businessfunctions, and are used to set the values of the parameters.

The combination of the wizards described in this section and the parameter rulesas discussed in the preceding section, is used to set the values of all the BAANIV parameters. Parameter rules are only used to set parameters if the relationbetween a business function and a parameter is evident. In all other cases wizardsare used to set the parameters.


2 - 21

This session can be used to create new wizards, to modify existing wizards, andto delete wizards. The first form of this session lists the wizards in the currentversion. The second form of this session can be used to define data such as thewizard category, whether the wizard is mandatory or optional, and which image isdisplayed in the wizard dialog box. The buttons within this session can be used tostart related sessions to modify data of the selected wizard or to execute thewizard. These related sessions, listed in the table below, are discussed here.

A wizard is used to group a number of wizard steps. The wizard itself does notcontain any questions, but it only shows a dialog box with an introductory textand, after finishing, a dialog box with an end text. The wizard steps are used toask the questions and to receive input.

Button Activated sessionWizard Steps Maintain Wizard Steps (tgwzr2100s000)Start Text Text editor to define the wizard start textEnd Text Text editor to define the wizard end textHelp Text Text editor to define the wizard help textCategories Maintain Wizard Categories (tgwzr5100s000)Execute Wizard Executes the wizard

Maintain Wizard Steps (tgwzr2100s000)Wizard steps are those sections of a wizard that accomplish the dialog with theuser. This session is used to create new wizard steps, to modify existing steps,and to delete steps.

NOTE


2 - 22

The first form of this session lists the steps of the selected wizard. The secondform of this session can be used to modify additional data related to the wizardsteps selected on the first form. The data fields that are not self-explanatory arediscussed here.

The Zoom/Browse Session field can be used to set parameters by selectingexisting data that is available through the BAAN IV subsession specified in thisfield. This session can only be a display session. If this is done, then the ReturnField field and the Show Field field must be defined as well. The Return Fieldfield is the value that is returned to the parameter, for example, the employeecode 1234. The Show Field field is the field that is displayed in the dialog box toclarify the return field, for example, Mr. John Doe.

The Domain field is used to specify the domain of the data that must be returnedto the parameter. A domain determines some characteristics of the return field,such as data type (like string or integer), the length of the field, and allowedvalues. This field cannot be modified if answers are defined manually.

The Session to Start field can be used to define a BAAN IV session that can bestarted from the wizard step. This session should be a maintain session, whichcan be used to enter new data.

The Business Process to Start field can be used to define a business process thatcan be started from the wizard step. This business process can be used to enterdata by working through the activities included in the business process.

The buttons in the Maintain Wizard Steps (tgwzr2100s000) session can be usedto activate related sessions to modify data of the selected wizard step, or toexecute the step. These related sessions, listed in the table below, are discussedhere.


2 - 23

Button Activated sessionQuestion Text Text editor to define the wizard step question textImport Para. Display Parameters (tgbrg9500s000)

Answers Maintain Wizard Step Answers (tgwzr2120s000)Wizard Constr. Text editor to define the wizard constraintsApply Constr. Text editor to define apply constraintsHint Text Text editor to define the wizard step hint textHelp Text Text editor to define the wizard step help textFunctions Maintain DLL Functions used in Constraints (tgwzr3100m000)Execute Step Executes the wizard step

1 Question Text The Question Text button in the Maintain Wizard Steps (tgwzr2100s000)

session, can be clicked to start the text editor to define the question textthat is displayed in the wizard step dialog box.

2 Import Parameters The Import Para. button in the Maintain Wizard Steps (tgwzr2100s000)

session, can be clicked to select the parameters that must be set throughone or more wizard steps. Next, a wizard step is created for each selectedparameter, and for each wizard step the data is defined automaticallywhich, if necessary, can be modified. If this option is used, BAAN IVenters the data for the Description field, the Domain field, the DefaultAnswer field, the Mandatory check box, the question text, the applyconstraints, and the help text.

- It is recommended to use this user-friendly option to create consistent andcorrect wizard steps efficiently.

3 Maintain Wizard Step Answers (tgwzr2120s000) This session is used to manually define answers for the wizard step. Since

answers are automatically based on the defined domain, this session canonly be used when the Domain field is empty. If a certain answer results insetting several parameters, it is impossible to define just one domain forthis step. Therefore, the field should be left empty, which means that thereare no answers either.

NOTE


2 - 24

If it is desired to make a wizard step to set several parameters, this sessionmust be used to define the answers. The Apply Constr. button must beused to define what needs to be done for each possible answer. Becausethe Domain field in the Maintain Wizard Steps (tgzwr2100s000) session isempty, the domains for the parameters must be included in the applyconstraint.

4 Wizard Constraints The Wizard Constr. button in the Maintain Wizard Steps (tgwzr2100s000)

session can be clicked to activate the text editor to define the wizardconstraints of the step. Wizard constraints are used to define which (non-standard) actions must be taken based on certain conditions. For example,it is possible to define that. If, for example, a certain question in a step isanswered with Yes, another nested wizard must be executed.

Functions needed in the wizard constraints can be included by means ofthe Start Zoom Session option in the Options menu in the text editor.

5 Apply Constraints The Apply Constr. button in the Maintain Wizard Steps (tgwzr2100s000)

session, can be clicked to activate the text editor to define the applyconstraints of the step. Apply constraints are used to define what must bedone when the user has worked through the steps and chooses to apply theanswers. Wizard step answers can be applied in the business functionmodel in the project model. There the wizards are executed, and whenthey are finished the question is asked whether the answers must beapplied based on certain conditions.

The apply constraints are created automatically when wizard steps arecreated by importing parameters. In all other cases the constraints must bedefined manually.

Functions needed in the apply constraints can be included by means of theStart Zoom Session option in the Options menu in the text editor.

6 Hint Text Clicking the Hint Text button in the Maintain Wizard Steps

(tgwzr2100s000) session activates the text editor to define the hint textwhich can be opened in the wizard step dialog box. Other than help text,which gives a direct explanation, hint text directs users to the answer, byreferring to examples from evident common practice.


2 - 25

7 Help Text Clicking the Help Text button in the Maintain Wizard Steps

(tgwzr2100s000) session activates the text editor to define the help textthat can be opened in the wizard step dialog box. Help text is used toexplain the question in more detail, or to place the question in perspectiveto (parts of) the reference or project model. This is different from hinttext, which advises about possible answers.

8 Maintain DLL Functions used in Constraints (tgwzr3100m000) The Functions button can be clicked to activate the Maintain DLL

Functions used in Constraints (tgwzr3100m000) session. This sessionmust be used to define the dynamic link library (DLL) functions that areused in the wizard constraints and apply constraints. A dynamic linklibrary is a piece of program script that can be used by several programs.Each DLL contains one or more functions to accomplish a certain task.Amongst others, these functions can be used in a constraint in order tocheck the answers given by a user against certain conditions, to check onthe presence of a business function in the business function model, to readparameters, or to read wizard step answers.

In this session, the first field is used to specify the function to include fromthe DLL specified in the third field. Because it is not possible to zoom onthe function field (since the functions are included in the DLLs) the easiestway to include the needed functions is to automatically import thefunctions that are included in the specified DLL by means of the ImportDLL Functions (tgwzr3101s000) session, which is activated by clickingthe Import DLLs button. This always includes all functions within theDLL. Next, it is possible to delete the functions that are not needed, fromthe Maintain DLL Functions used in Constraints (tgwzr3100m000)session. The Maintain DLLs button can be used to activate the MaintainLibraries (ttadv2131m000) session in which the DLLs can be defined.This session is not further explained, because it is described in the moduledescriptions of BAAN IV Tools.

- The functions included in the Maintain DLL Functions used in the WizardConstraints (tgwzr3100m000) session are only related to the currentversion, and not to one specific wizard or wizard step. Always import theDLL tgwzr001, in which a number of predefined functions are present,like a function to read wizard step answers and a function to check thepresence of a business function.

NOTE


2 - 26

9 Execute Step The last button in the Maintain Wizard steps (tgwzr2100s000) session,

can be used to execute the selected wizard step in order to test if it isworking correctly.

Start TextThe Start Text button in the Wizards (tgwzr1100m000) session activates the texteditor to define the wizard start text. The start text explains the function of thewizard, but does not ask any questions, because that is done in the wizard steps.If no start text has been defined, the window related to the wizard is skipped, andthe window of the first wizard step is directly shown.

End TextThe End Text button in the Wizards (tgwzr1100m000) session activates the texteditor to define the wizard end text. The end text explains the result of thewizard. It does not ask any questions, because that is done in the wizard steps.

Help TextThe Help Text button in the Wizards (tgwzr1100m000) session activates the texteditor to define the wizard help text. The help text is a more detailed explanationof the wizard. It often only contains a link to a relevant part of the already presenton-line help.

Maintain Wizard Categories (tgwzr5100s000)The Categories button in the Wizards (tgwzr1100m000) session activates theMaintain Wizard Categories (tgwzr5100s000) session, which can be used todefine the categories that can be linked to the wizards. By means of this session,it is possible to define the different categories that are needed, including thecategories that will be linked to other wizards.

Execute WizardThe last button in the Wizards (tgwzr1100m000) session, can be used to executethe selected wizard in order to test if it is working correctly.

Maintain Roles (tgbrg8110m000)Roles are used to group different employees with the same responsibilities. Rolescan be linked to business functions, business processes, and activities. As a result,employees are linked to those components, which means that the employees areresponsible for and authorized to use those components. This session is used todefine the roles to which employees can be linked.


2 - 27

To find out where certain roles are used, the Print Where Used Roles(tgbrg3441s000) session can be activated by clicking on the Where Used buttonin the Maintain Roles (tgbrg8110m000) session.

Maintain Parameters (tgbrg9100m000)This session is used to insert the parameters that will be linked to referencemodels and project models. After the parameters have been linked to a referencemodel or project model, the parameters can automatically be given specificvalues, based on the function and process models.

It is possible to enter the parameters manually using the Insert and Zoomcommands of BAAN IV. However, it is also possible to import the parametersautomatically by means of the Import Range of Parameters (tgbrg9200s000)session is needed, which can be activated by means of the Fill Parameters button.In this session, the range of packages and modules must be defined for which theparameters are to be imported. The actual import is initiated by means of theContinue button. After the import, the control is returned to the MaintainParameters (tgbrg9100m000) session in which the imported parameters are listed.To access the help information of a specific parameter, click on the ParameterHelp button, after selecting a parameter.

To find out where certain parameters are used, the Print Where Used Parameters(tgbrg9401s000) session can be activated by clicking on the Where Used button.

Other sessions

Copy Version Data to Other Version (tgbrg1200m000)If new master data, new reference models or new project models must be createdbased on the different components from another version, this session is used tocopy that versions data to the new version. This type of copy action can becompared to normal copy and paste actions since an actual copy is created. Thiscan also be done if the versions are not linked in any way through the derived-from structure.


2 - 28

Delete Components (tgbrg1210m000)This session can be used to delete selected components for the selected versions.The data is deleted according to the defined structure For example, if a businessfunction is deleted, the links to that business function are also deleted. It may benecessary to delete if excess version data has been copied to another versionusing the Copy Version Data to Other Version (tgbrg1200m000) session. It isrecommended to first use the Print Complete Version Data (tgbrg1430m000)session to view the data which is to be deleted.

Export Version Dump (tgbrg1235m000)This session can be used to export the data of a specified version, which makes itpossible to import the version into a different system or (data) company. As aresult of the derived-from structure of versions, it is also possible to include thedata of previous versions. This only applies to data that was not changed in thespecified version and is, therefore, only present in the previous versions. Sincedump files are often very large, it is also possible to specify that the file must becompressed. On the second form of this session, it is possible to specify whichcomponents must be exported.

Import Version Dump (tgbrg1240m000)This session can be used to import the dump that was created in the ExportVersion Dump (tgbrg1230m000) session. The data can only be imported for thesame version as the export. If that version does not yet exist in the target system,the system will ask the user whether or not the version must be createdautomatically. If the answer is no, the import is not executed. The second form ofthis session can be used to specify the components that must be imported.

Change Password for Version Authorizations(tgbrg1160m000)To activate the Maintain User Authorization for all Versions (tgbrg1140m000)session, the Maintain Version Authorization by User (tgbrg1150m000) session,or the Maintain User Authorization by Version (tgbrg1155m000) session, apassword must be entered. For security reasons, it is recommended to change thedefault password to a custom password. This is done by means of this session.


2 - 29

Maintain Responsibility Codes (tgbrg8130m000)Responsibility codes are codes that can be linked to roles whenever roles arelinked to business functions, business processes or activities. This means thatemployees that are linked to a role are also linked to the responsibility codeslinked to that role, indicating the responsibilities for the corresponding functions,processes or activities. In this session, a code must be defined, a description mustbe entered, while it is also possible to indicate whether or not the code means thatthe employee may execute the activity. By setting the value of the ExecuteActivity field to Yes or No, it is possible to indicate whether or not, employeescan activate the sessions from their start-up screen.

Maintain AO Documents (tgbrg8100m000)This session can be used to define references to existing AO documents,containing formal administrative organization rules regarding the execution ofprocesses. Since the text editor can be activated to create or modify help text foreach AO document, it is possible to view the help text related to a documentwhen executing a process to which the AO document is linked.

AO document references can be linked to business process activities by means ofthe Maintain Business Processes Activities (tgbrg5122m000) session, which isactivated from the Business Process Repository Editor (tgbrg5101m000) session.This session is used to store the help texts related to the use of the AOdocuments, and not to store the AO documents themselves.

Maintain Business Process Activity Categories(tgbrg5125m000)This session can be used to define the categories for the activities that are definedin the Business Process Repository Editor (tgbrg5101m000) session. Thesecategories can be used to group activities based on such aspects, as the activitytype.

To determine where certain business process activity categories are used, thePrint Where Used Business Process Activity Categories (tgbrg5426s000) sessioncan be activated by clicking on the Where Used button.

NOTE


2 - 30

Maintain Utilities (tgbrg5170m000)This session can be used to define the utilities which can be attached to processactivities. A utility contains one or more BAAN IV sessions that can be used tosupport employees in the execution of their activities. These sessions are referredto as utilities, because they can be used as optional sessions in the execution ofactivities in processes. For example, display and print sessions. A utility can belayered, which means that a utility can contain other utilities.

Creating a utility structure means adding sessions to utilities, and/or addingutilities to utilities. This can be done by means of the Maintain Sessions byUtility (tgbrg5160s000) session which can be activated by means of the Sessionsbutton. In this session, utilities and sessions are linked to a utility by manuallyinserting them. It is also possible to import sessions based on a user-definedrange. This range of sessions can be specified using business objects, sessioncodes, and session use in business objects.To find out where certain utilities are used, the Print Where Used Utilities(tgbrg5471s000) session can be activated by clicking on the Where Used button.The BAAN IV sessions included in the utilities are supplementary to the mainBAAN IV session attached to a business process activity. This means that anactivity of type BAAN Session comprises one main session and any number ofutilities.

Maintain Templates (tgbrg1170m000)This session can be used to define templates for the different texts in theEnterprise Modeler. These templates can be used to ensure a text standard is usedto build texts in the Enterprise Modeler. The Enterprise Modeler includes anumber of default templates for each type of text, which can be modified in otherversions than the standard.

Maintain Display Identifications (tgbrg1120m000)This session can be used to define the display identifications of the EnterpriseModeler. These display identifications depend on different sizes and resolutionsof the available monitors. As a result of this session, the size and resolution of theeditor screens in the Enterprise Modeler are set to the type of monitor that isused.

NOTE


2 - 31

Print Differences between Models (tgbrg1450m000)This session can be used to print the differences between two reference models,two project models, or a reference and a project model.

Print Where UsedThe Master Data business object contains some Print Where Used sessions thatare used to find out where certain software components are used, namely:

Print Where Used Roles (tgbrg3441s000) Print Where Used AO Documents (tgbrgr8405s000) Print Where Used Business Process Activity Categories (tgbrg5426s000) Print Where Used Utilities (tgbrg5471s000) Print Where Used Parameters (tgbrg9401s000) Print Where Used Static Conditions (tgbrg5481s000)

Print Wizards and Where Used Wizards (tgwzr1400s000) Print Where Used Sessions (in Enterprise Modeler) (tgbrg5461m000)To print where certain roles, AO documents, utilities, process activity categories,parameters, static conditions, wizards, or sessions are used, the correspondingPrint session can be used. The first seven Where Used sessions are activated fromwithin the Maintain sessions of the related components, the last session isactivated directly from the Menu Browser. In these sessions, a range must bedefined for which the search should take place after which the place in which thesearch must take place must be specified. Finally, the components which must beprinted must be specified.

Maintain Runtime Resources (ttdsk3160s000)This session can be activated in all editors of the Enterprise Modeler. To activatethis session, the Resource Settings option must be selected from the Optionsmenu in the editors. This session, which edits the runtime resources, can also beactivated by means of the Desktop Management utilities in BAAN IV Tools.

The session can be used to specify user-specific runtime resource settings for theEnterprise Modeler, such as fonts, colors, sizes of editor components, and defaultoptions.


2 - 32

The runtime resources for the Enterprise Modeler have been divided in thefollowing four groups:

1 Organizer resources, relating to the complete Enterprise Modeler2 Organization resources, relating to the Organization Model Editor3 Process resources, relating to the Business Process Model Editor4 Function resources, relating to the Business Function Model Editor

The display identification as defined in the Maintain Display Identifications(tgbrg1120m000) session is one of the resource settings of the Organizer group.

Syntax Checker in the Business Process RepositoryEditorMistakes may occur when data is entered in the business process repository bymeans of the Business Process Repository Editor (tgbrg5101m000) session.These mistakes may include such simple things as forgetting to connect certaincomponents, or loops in processes (recursive relationships). To check whetherthere are any mistakes in the current business process, the Syntax option can beselected from the Options menu. Based on the Petri net method, this commandchecks the syntax of the current business process. Only checks for loops in lowersubprocesses go beyond the level of the current business.

NOTE:

3 - 1

This chapter describes the Reference Models business object and givesinformation about the business objects functions. In addition, the chapteridentifies and explains the mandatory and other sessions related to the businessobject.

The place and function of Reference ModelsThe Reference Models business object is used to define organization typologyspecific models of the business functions, the organization, and the businessprocesses.

If a reference model must be created or maintained, the components that areused in that reference model must be included in the repository of the masterdata. If a project model must be created or maintained, it is recommended tobase the project model on a reference model by copying the reference model tothe project model before the project-specific modifications are made. Since thisis done according to the concept behind the Enterprise Modeler, this businessobject is used to define the reference models, which is most often done by Baanand its partners.

3 The Reference Models businessobject

3 The Reference Models business object

3 - 2

Mandatory sessions

Business Function ModelEditor (Reference Model)

(tgbrg3101m000)

Maintain OrganizationDiagrams by ReferenceModel (tgbrg6104s000)

Maintain Business Processesby Reference Model

(tgbrg3160s000)

Maintain Companies byReference Model(tgbrg3110s000)

Maintain Values by Parameter, Company, and

Model (tgbrg9110s000)

MaintainReference Models(tgbrg3100m000)

Figure 3-1 The mandatory sessions in the Reference Models business object

Maintain Reference Models (tgbrg3100m000)

This is the only main session included in the Reference Models business object.The first form of this session displays the reference models that are available inthe current version and can be used to insert new models or to delete existingmodels. The second form is used to define the detailed data of the model thathas been selected on the first form.

This session is also used to enter the data related to reference models. This isdone by means of the buttons on the first form, sometimes preceded by selectinga model. These buttons, described in the table below, can be used to activate thelast five mandatory sessions shown in Figure 3-1. The first button can be used toactivate an optional session. For more information on this optional session andthe related button, see Chapter 3 Other Sessions.


3 - 3

Button Activated session

Import Model Display Project Models (tgbrg4500s000) (optional)

Function Model Business Function Model Editor (Reference Model)(tgbrg3101m000)

Organiz. Model Maintain Organization Diagrams by Reference Model(tgbrg6104s000)

Process Model Maintain Business Processes by Reference Model(tgbrg3160s000)

Companies Maintain Companies by Reference Model (tbrg3110s000)

Parameters Maintain Values by Parameter, Company, and Model(tgbrg9110s000)

Business Function Model Editor (Reference Model)(tgbrg3101m000)

This session is used to edit the business function model of a reference model andcan be activated by selecting a reference model and clicking on the FunctionModel button.

This session is used to structure the business functions (defined in therepository) according to the business functions used in a certain organizationtypology. In addition, this session is used to define the optimizationrelationships, which indicate that a certain business function variant is anoptimization of another business function variant.

In the Business Function Model Editor (Reference Model) it is not possible tomodify business function data, since this can only be done in the businessfunction repository. It is possible to copy business functions from the repositoryand paste them into the Business Function Model Editor (Reference Model).

A business function model can only be edited by one user at the same time.

Business functions can be defined in the repository in a hierarchical structurewhich means that a function may have subfunctions. This structure is used as anaid while defining the business functions and does not have to be maintained inthe reference models. For example, a function A can be defined in the repositorywith subfunctions A1 and A2. In a reference model, these three businessfunctions could be used to create a function A2 with a subfunction A with asub(sub)function A1.

NOTE 1

NOTE 2

NOTE 3


3 - 4

Commands in the Business Function Model Editor (Reference Model)A number of commands are available in the Business Function Model Editorwhich can be used while editing in the repository. Most commands can beactivated from the toolbar or the menu bar although some of the commandsbelow are only available through the menu bar. For more information on thetoolbar of the Business Function Editor, see Appendix A.

1 Adding business functions- Business functions are added by means of the Copy and Paste commands

by means of which the business functions that are to be used in thereference model can be copied from the repository and pasted into thereference model. If the Business Function Model Editor is activated for areference model, the corresponding Business Function Repository Editoris also activated and can be accessed by selecting the Business FunctionRepository Editor option from the Model drop down menu. Use theDelete button to delete components. The hierarchical structure ofbusiness functions as defined in the repository does not have to beapplied in the reference model.

2 Adding optimization relationships- Optimization relationships are added to business function variants, by

clicking on the Optimization Relationship button, and by clicking on thefirst business function variant, and the other business function variant. Amain business function can have one or more variants underneath it.

- Optimization relationships are removed by selecting the correspondingarrow and clicking on the Delete button.

3 Linking performance indicators- Existing predefined performance indicators (PIs) can be linked to

business functions by selecting the business function and clicking on theAdd PI button. This button activates the Display Performance Indicators(tgeis0511s000) session in which one or more PIs can be linked to thebusiness function. To link more than one PI at the same time, press the key while selecting the second and following PIs.

- The PIs that have been linked to a certain business function can beviewed by clicking on the PI icon underneath the function. This iconopens a dialog box with the currently linked PIs. To close this dialog box,click on the button in the right upper corner of the dialog box.


3 - 5

- To modify the descriptions of PIs or to link text to them, the MaintainPIs by Business Function by Reference Model (tgbrg3180s000) sessioncan be activated by clicking on the button in front of the PI which mustbe modified.

- To view the values of PIs, select a PI by clicking on the description in thedialog box, and selecting the Performance Indicator option from theView menu. This option activates the Chart Manager showing theselected PI.

- To remove a PI from a business function, select the appropriate PI in thedialog box by clicking its description, and clicking on the Delete button.

4 Adding roles-- Existing predefined roles are linked to business functions by selecting the

business function and clicking on the Add Role button. This buttonactivates the Display Roles (tgbrg8510s000) session in which one ormore roles can be linked to the business function. To link more than onerole at a time, press the key while selecting the remaining roles.

-- To view which roles have been linked to a certain business function,click on the Role icon underneath the business function. This icon opensa dialog box with the currently linked roles. To close this dialog box,click on the button in the right upper corner of the dialog box.

-- To add responsibility codes to roles, to link text to roles, and to definewhether the role must be included or excluded from the businessfunction, the Maintain Roles by Business Function by Business Model(tgbrg3120s000) session can be activated by clicking on the button infront of the role which must be modified.

-- To remove a role from a business function, select the appropriate role inthe dialog box and click on the Delete button.

5 Navigating through the business function structure-- Double-click on a business function to go to a lower level, where

subfunctions can be added. This level can also be accessed by means ofthe Zoom In button. To go back to the previous level, click on the ZoomOut button. The different levels can also be selected using the box in theleft bottom corner of the screen, which contains the descriptions of thedifferent levels that are available.


3 - 6

6 Adding help text-- Help text can be linked to a business function by selecting the business

function and clicking on the Text button in the toolbar. The link can beremoved by clicking on the T icon underneath the business function andselecting the Disconnect option from the File menu in the Text Editor.The help text created here is referred to as (specific) business functionhelp text, which is created in addition to the business function (general)help text which is linked to the business functions in the repository.

-- Optimization (help) text can be linked to an optimization relationship byselecting the optimization relationship and clicking on the Text button inthe toolbar. The link can be removed by clicking on the T icon on thearrow representing the optimization relationship, and selecting theDisconnect option from the File menu in the Text Editor.

7 Modifying business function basic data-- The basic data of business functions cannot be modified in the reference

model, since this data has already been defined in the repository. Instead,the Maintain Business Functions by Reference Model (tgbrg3170m000)session can be activated by selecting a business function and clicking onthe Change button. In this session, it is possible to modify the externalcode of a busines

baan iv enterprise modeler

Documents

import model

reference model tgbrg6104s000

reference model tgbrg3160s000

reference model tgbrg3110s000

model tgbrg9110s000

business processes

function of reference

project models business