Workflow in the Project Database (v10.xx)

Workflow in the Project Database (v10.xx)


Several workflows are predefined in the default implementation, which you can use as-is.

For more information about workflows, see the chapter "Configure Workflows".



Navigation


Navigation within workflows has already been covered in the Portfolio section.


Risks


Cerri Project's Risk Management module enables organizations to manage potential obstacles that could impact project success throughout the project lifecycle.


The ‘Risks’ setup section is used to configure the automation of an organization’s risk management process, incorporating internal terminology and rules. This setup includes configuring the 'Risk labels' document and the risk classification hierarchy.



Risk labels setup


Only one 'Risk labels' document can exist per 'Projects' database.


Matrix tab



Number of levels

Field

Use

Number of likelihood levels

Defines the number of levels to measure the likelihood of a risk occurring.

Range: 3 to 6.
Default: 5.

Number of impact levels

Defines the number of levels to measure the impact a risk will have on a project.

Range: 3 to 6. Default value: 5.

Number of classification levels

Defines the number of levels used to classify a risk.


Range: 2 to 4.
Default value: 4.



Matrix definition

Fields

Use

Matrix Built according to the defined 'Number of likelihood' and 'Number of impact’ levels. Clicking on a cell changes its color, allowing users to define matrix zones. The color cycles with each click.


Labels tab


The values defined in the Labels tab describe the different levels set in the Matrix tab. Default values for each level are provided, but organizations can modify them to suit their internal processes and terminology.


Likelihood type


Fields

Use

Level 1 Label for likelihood level 1. Default: 'Very low'.

Level 2 Label for likelihood level 2. Default: 'Low'.

Level 3 Label for likelihood level 3. Default: 'Medium'.

Level 4 Label for likelihood level 4. Default: 'High'. (Visible only if 'Number of likelihood levels' is at least 4).

Level 5 Label for likelihood level 5. Default: 'Very high'.

(Visible only if 'Number of likelihood levels' is at least 5).

Level 6 Label for likelihood level 6. Default: 'Highest'. (Visible only if 'Number of likelihood levels' is 6).


Impact type


Fields

Use

Level 1 Label for impact level 1. Default: 'Negligible'.

Level 2 Label for impact level 2. Default: 'Minor'.

Level 3 Label for impact level 3. Default: 'Average'.

Level 4 Label for impact level 4. Default: 'Major'. (Visible only if 'Number of impact levels' is at least 4).

Level 5 Label for impact level 5. Default: 'Critical'. (Visible only if 'Number of impact levels' is at least 5).

Level 6 Label for impact level 6. Default: 'Unacceptable'.

(Visible only if 'Number of impact levels' is 6).


Risk classification


Fields

Use

Level 1

Label for risk classification level 1. Default: 'Risk nature'.

Level 2

Label for risk classification level 2. Default: 'Risk category'.

Level 3

Label for risk classification level 3. Default: 'Risk source'. (Visible only if 'Number of classification levels' is at least 3).

Level 4

Label for risk classification level 4. Default: 'Activity'. (Visible only if 'Number of classification levels' is 4).


Type of risks


Fields

Use

Before mitigation Label for risk values before mitigation.

Default: 'Original'.

After mitigation Label for risk values after mitigation.

Default: 'Actual'.


Risk classification setup


Risk classifications define how risks are categorized in the system. The classification can have multiple levels, with the number of levels and their titles set in the ‘Risk labels’ document. Categories for each level are defined within the risk classification hierarchy.




To create a risk category:


  1. Open the 'Projects' database.
  2. Navigate to the 'Setup & Administration' module -> 'Setup' tab -> ‘Risks’ view.
  3. Click on the «Create» menu and select the level for the new category.

  1. To create a level other than the first, select one of the categories in a level above it.
    1. The new category will be placed under the selected level in the classification hierarchy.
  2. The risk categorization document will open.
    1. Each of the levels above it will be listed along with a blank field where the name of the new level should be entered.


  1. Complete the risk categorization document.
  2. Save and close the document.
  3. Repeat these steps for each new category.


    • Related Articles

    • Workflow in the Project Database (v8.xx)

      There are several Workflows predefined from default implementation you can use. To perform a workflow you need at least the License Stakeholder (also possible Timesheet, Team Member or Project Manager). In the ACL you need Access as Author and ...

    • Workflow Definition (v10.xx)

      To begin, it is necessary to create a workflow definition to specify the type of workflow being created, e.g., Contract. Navigate to the [Setup & Administration] module of the 'Projects' database, [Setup] tab. Select «Workflow» from the «Setup» view. ...

    • Workflow (v10.xx)

      If a workflow is assigned to a document type used in a project template, the initial status can be applied when the document is created, depending on the workflow definition. This occurs when the property ‘Status by default’ of the first workflow ...

    • Workflow Definition (v8.xx)

      To begin it is necessary to create a workflow definition to specify the type of workflow being created, i.e. Contract. Navigate to the [Setup & Administration] module of the 'Projects' database, [Setup] tab. Select «Workflow» from the «Setup» view. ...

    • Workflow (v8.xx)

      If a workflow is assigned to a type of document used in a project template, the first status can be reached when the document is created, depending on the workflow definition. This occurs when the property ‘Status by default’ of the first workflow ...