Keywords and Labels (v10.xx)

Keywords and Labels (v10.xx)

As users navigate through the application, they will encounter various drop-down lists of choices. The values found in these lists are configured during the setup of the software in the ‘Keywords & Labels’ setup document.


General tab


Project types


The values defined in the ‘Project types’ list appear in the [Project Description document-> Categorization tab -> [Type] field].
The ‘Type’ field can be used as a filter criterion when generating reports.



Project status



The [Project status] field is located in the header of the ‘Project description’ document. Its value is selected during the creation of a new project and can be updated throughout the project lifecycle.

The application is set up with a list of default statuses, which can have their labels modified, and additional statuses can be added:

  1. Stand-by#0
  2. In Progress#2
  3. Completed#10
  4. Cancelled#12
  5. Template#01


Syntax: StatusLabel#StatusCode
  1. The StatusLabel may be modified without affecting functionality.
  2. The StatusCode must not be changed, as it is used programmatically to identify statuses.
Key rules:
  1. Projects with StatusCode #0 : Always considered inactive.
  2. Projects with a StatusCode #1 to #9: Active projects; tasks can be worked on, and time can be reported.
  3. Projects with StatusCode #10: Completed projects.
  4. Projects with a StatusCode of #11 and higher: Cancelled projects; modifications can no longer be made directly to the project through the 'Project' database or indirectly through timesheets.

Notes:

  1. None of the default StatusCodes (#0, #2, #10, #12, #01) must be deleted.
  2. The statuses with these codes must exist.
  3. It is not allowed to use a default label on another StatusCode (e.g., "In Progress#3" is not allowed).
  4. It is possible to assign different labels to all existing and new StatusCodes (e.g., "Online#2" is possible).



Document types


In Cerri Project, all project ‘records’ are referred to as 'documents'. These include standard Cerri Project documents such as:
  1. Project descriptions
  2. Plans
  3. Tasks
  4. Assignments
  5. Deliverables

In addition to the standard documents, organizations can create a library of unique document types and define them in the 'Document Types' section of the ‘Keywords & Labels’ setup document.

Once the document types are created and defined:

  1. Corresponding documents will be generated per type.
  2. Templates and workflows can be created to align with the organization's project management processes.


Cost types


A cost is typically a non-labour related expense budgeted into a project, such as:
  1. Materials
  2. Travel
  3. Advertising, etc.
Costs are identified in:
  1. ‘Inv. & Exp.’ section of project budgets


  1. Project ‘Cost’ documents


Cost types are configured and defined in the ‘Keywords & labels’ setup document.



Activity types




Activity types are used to categorize tasks. Project leaders can group tasks by activity type for:

  1. Budgeting
  2. Invoicing
  3. Reporting


A task's activity type is defined in the ‘Task’ document.


To change the activity type in a Gantt Plan, open the General Tab from a Task.



Activity types are also used for multi-rates management. If a resource’s billable rate depends on activity type, organizations can assign different rates by activity type.


A resource’s rate by activity type is found in their profile document in the ‘Rates’ tab.


Note: Activity types for multi-rates management must match those defined in the General setup document of the 'Resources' database.


Activity types can also be used to break down the labor costs in detailed project budgets.



Origins of Issues


Cerri Project's issue management section allows project managers to log and track problems encountered during a project's lifecycle. This helps anticipate future issues and incorporate mitigation plans into upcoming projects.


The ‘Origins of issues’ section in the Keywords & Labels setup document is where organizations list typical issues. Once the list is defined, project managers and team members can create issue reports specifying the appropriate origin.



Roles


Roles are used to assign unique responsibilities to different users on a per-project basis. Once created, roles are applied to document revision and approval workflows, ensuring that only users assigned to a specific role can perform certain actions.


To begin, an organization must identify the roles required, such as: budget approver, contract approver, etc. These roles should be created in the Roles section of the Keywords & Labels setup document.



To add a new role:
  1. Click on the icon and add the role name to the list.
  2. Add the necessary role(s) to the relevant projects.