Working with the Process Model (Tutorial) From DB 39.5.7

Please note

• The description in this topic applies to PLANTA project versions from DB 39.5.7 to 39.5.12.
• The following table contains links to the other versions:

DB 39.5.15	go to the tutorial
DB 39.5.14	go to the tutorial
DB 39.5.13	go to the tutorial
DB 39.5.7 - DB 39.5.12	go to the tutorial
DB 39.5.0 - DB 39.5.6	go to the tutorial
< DB 39.5.0 but S 39.5.13	go to the tutorial
< DB 39.5.0 and < S 39.5.13	go to the tutorial
	go to further tutorials

Introduction

Information

• Beside the conventional way of project planning, PLANTA project enables you to plan and control projects in a process-oriented way.

Objective

• This workflow is supposed to teach users how to work with process models in the PLANTA software.

Notes

• All exercises are based on the PLANTA demo data. This data must be installed beforehand.
• Master data such as process models, resources, users, etc. has already been set up in the demo data. This tutorial does not cover how the master data is defined. (For this, see Master Data Entry). It is merely about describing procedures like the planning procedure or the creation of a new project according to one of the models available. A technical guide about how to create and control projects with the PLANTA software can be found in the Project Workflow as well as in the description of individual user modules in case of planning objects such as ideas, plans or requests.
• It is recommendable to have carried out the project workflow before the process model workflow.
• The screen shots used are merely examples of functions. The screen shot layout may deviate from the program.

Activate Process Models (R41)

Task

• The multi-project manager, Mr. Hart, has just created the new project PR-01 and he has appointed Mr. Koch (R8) as the project manager.
• To plan and control the new project, Mr. Hart would like to apply the DIN69901/1-5 (Short version) process model.

Procedure

• Start the client.
• Log on with user R41.
• Create a new project.
• Enter PR-01 for the project name.
• Appoint Mr. Koch as a project manager (manager).
• Open the Project panel of the PR-01 project.
• Click on the Process status tab at the bottom of the panel in order to open the module of the same name.
• From the Process model listbox select the DIN69901/1-5 (Short version) process model.
• Activate the Activate model button.
  • All phases of the model are loaded along with the process steps belonging to it.
    • the first phase is opened under the In process category; the individual process steps are immediately visible.
    • All other phases are displayed under the Future phases category, the individual process steps are invisible.
  • The process bar at the bottom of the module is loaded.

Edit Phase (R41)

Create Process Steps Manually

Task

• For the Initialization phase Mr. Hart wants to create the additional Define consequences of non-realization process step.
• Furthermore, the Approval process step should get a subordinated approval process step, because Mr. Hart wants to delegate the monitoring of completed process steps to the project manager before the final approval.

Information

• New process steps can be inserted manually in the existing model.
  • Project specific process steps: right-click on the process phase names Insert process step
  • Approval steps: via the context menu Create subordinated approval step
  • Process steps of the Submission class cannot be inserted manually.

Procedure

• Right-click on the Initialization process phase in the Process Status module and select the Insert process step context menu command. ( Project-specific process steps that were inserted manually are marked with "I").
• Enter the name for the new process step in the line inserted in the Process step name field.

• Save.

Delete Process Steps

Task

• After consideration, Mr. Hart does not deem the subordinated approval step necessary anymore. He now wants to delete it.

Procedure

• Right-click on the subordinated approval step in the Process status module.
• Select the Delete Process Step context menu command.

• The process step has been deleted.
• Save.

Note

• Standard process steps can only be deleted if the respective checkboxes have been activated in the Process Model Templates module.
  • If process steps must not be deleted, the The marked records could not be deleted due to process model configurations message is displayed

Deactivate Process Steps

Task

• As Mr. Hart has already appointed the project manager for the project the Clarify responsibility process step is no longer necessary.
• Mr. Hart wants to deactivate this step.

Procedure

• Activate the Not required checkbox next to the Clarify responsibility process step in the Process Status module.
• The status of this process step is automatically set to Completed.

• Save.
• The process step is now deactivated.

Note

• Process steps copied from the process model template cannot be deleted. They can only be marked as Not required.

Define Person Responsible for Process Steps

Task

• Mr. Hart now wants to define completion dates as well as a person responsible for every project-specific, submission, and approval process step (usually this is a manager or another person with modification rights).

Procedure

• Select a resource in the Resource name field in the process step line.
• Define the completion date in the Date field.
  • Outline objectives process step:
    • Person responsible: Koch, Rainer (PM)
    • Date: 29.04.11
  • Consquences of non-realization process step:
    • Person responsible: Koch, Rainer (PM)
    • Date: 02.05.11
  • Submission process step:
    • Person responsible: Koch, Rainer (PM)
    • Date: 03.05.11
  • Give approval process step:
    • Person responsible: Hart, Dieter (MPM) ( The logged-on user can only define himself/herself as the person responsible for approval when he is multi-project manager.)
    • Date: 05.05.11
  • Save.

Edit Process Steps (R8)

Execute Process Steps

Task

• Project manager Mr. Koch (R8) wants to execute the process steps for which he has been defined as the person responsible.

Procedure

• Start the client.
• Enter R8 for the project manager.
• Mr. Koch can now see the process steps he is supposed to edit in the My Activities module of the Employee Board panel in the Process step name area.
  • In the date scale (window 2) the completion dates of the assigned process steps can be viewed.
    • To do so, move the cursor to the green circle next to the required process step. The completion date is displayed in a tooltip.

• First, Mr. Koch wants to edit the Outline objectives process step.
  • Here, click on the link on the ID of the project. ( Alternatively, the project can be opened directly via the link on the ID of the project or via the Open project context menu command).
    • The Project panel of the PR-01 project is opened with the Dashboard module.
    • Open the Process Status module.
    • Click on the Focus task button next to the Outline objectives process step. (Alternatively, the task can be focused by the Focus task context menu command.
      • This function is only available if the corresponding process rules have been defined in the Process Model Templates module. This only makes sense for process steps that need a defined data entry in the system in order to be completed.

• The linked module is opened and the field that needs to be edited is focused.

• Mr. Koch can now define the objectives of the project.
• Save.
• Mr. Koch has completed the Outline objectives process step and changes the process step status in the Status field in the Process Status module from Open to Completed.
• Save.

Notes

• The process step status can also be changed in the Status field of the Process Step module, which can be opened by clicking on the Edit process step context menu command in the My Activities module.

• When a process step has the Completed status it is no longer displayed in the employee board of the corresponding employee.
• Process steps are only really completed when the Submission step is done in the Process Status module.
• The process step status of Submission and Approval classes cannot be changed manually. This happens automatically when the process step concerned is completed.

Task

• Complete the Define consequences of non-realization process step in the same way.

Notes

• The Define consequences of non-realization process step is an an individual process step which does not contain any focus to the appropriate editing module.
• But Mr. Koch as an experienced PLANTA user knows in which module he has to edit data for this step.

Procedure

• Mr. Koch opens the project panel of the PR-01 project,
• activates the Project Core Data module and
• fills the Conseq. non-realization field.
• Then he sets the status of the process step to "Completed" like described above.

Submit Phase

Task

• In the Process Status module Mr. Koch sees that all project-specific process steps of the Initialization phase have the Completed status. Now he wants to submit the process steps of the Initialization phase. To do this, he needs to complete the Submit process step.

Procedure

• Click on the link on the Submit process step in the Process Status module.

• The query whether you want to write a comment is displayed.
  • Confirm the message with No.
• If not all process steps have been completed, the Not all process steps are completed. message is output and the submission is not carried out. The status of the corresponding process step can be changed and returned to the person responsible for the process step.
• After submission, the Send Info module is opened and an info can be sent.
  • The info text is inserted automatically.
  • R41 is set as recipient by default.
  • Click on the Send button.

• After submission, completed process steps are listed in the Submitted phases category.

Approve Phase (R41)

Task

• The multi-project manager has checked the completed process steps and wants to approve the Initialization phase.

Procedure

• Log on with user R41.
• Open the project and click on the approval step in the Process Status module.
• A dialog message is displayed.

• Click on the Approve button.
• By doing so, the process step status is automatically set to Accepted.
• The Send Info module is opened and a message can be sent.
  • The info text is inserted automatically.
  • R8 is set as recipient by default.
  • Click on the Send button.

• The completed phase including its process steps is moved to the Completed phases category.
• In the process bar, the name of the completed phase is marked grey and the name of the new phase is highlighted white.
• The process steps of the next phase can be seen in the In process category.

• The progress from one phase to the next is thus completed.