You will be able to define a custom project coding system which will automatically increment the project code when new projects are added.
You can either define a general project coding system or a project coding system for each project type by following the steps below;
Defining a general coding system
STEP 1: Go to Framework> Project Settings> Project Code
STEP 2: Select the 'General' option from the 'Project code is based on' dropdown list.
STEP 3: Enter the required data as described below and click 'Save'.
Field | Description/Instructions | Mandatory/Optional |
|---|---|---|
Prefix | This will act as the first set of code used for all project codes | Optional |
Enter Start Number | This will kick off the auto number which will automatically increment when new projects are being added | Optional |
Suffix | This will act as the last two characters of the project code. Ideally this can be used to differentiate project from the date of creation. | Optional |
This numbering will be applied to all new projects created from the Project Details object.
2. Project coding based on project type
STEP 1: Go to Framework> Project Settings> Project Code
...
STEP 2: Select the "Project Type" option from the 'Project code is based on' dropdown list. Then you will be able to view a grid with the below columns;
Project Type: Shows the project types in the system
Prefix: Allows you to enter a ‘prefix’ for the project code. ‘Prefix’ will act as the first set of code used for project codes.
Suffix: Allows you to enter a ‘suffix’ for the project code. ‘Suffix’ will act as the last set of code used for project codes.
Start Number: Allows you to enter a start number to kick off the auto number, which will automatically increment when new projects of the respective project type are being created.
...
STEP 3: Enter the requisite data and click 'Save'.
For example, if the admin does the following configurations for the project type ‘Major Projects’, the projects of that type will have a project code such as “MP-1-20/21”.
Prefix: MP-
Suffix: -20/21
Start Number: 1
The system will assign the following default values for each project type. You can change the default configurations, if needed.
Prefix: The first letters of each word in the name of the project type will be capitalized and be set as the prefix. For example, prefix for the project type ‘Major Projects’ will be “MP”. If there are project types that have the same first letters in their names, a number will automatically be added next to the prefix to make the prefix for the respective project type unique.
Suffix: “-“ followed by the current reporting year (i.e. “-20/21”) will be set as the suffix
Start Number: “1” will be the set as the start number.
When you create a new project, the system will automatically assign a code for that project based on the ‘Prefix’, ‘Suffix’ and ‘Start Number’ configured for the respective project type from Project Settings> Project Code.
...
| Info |
|---|
Note: Once the above feature is activated, the new codes will only be applied to the new projects created. Hence, the project codes of the existing projects will remain unchanged. Please contact Camms Support, if you wish to apply the above feature to the existing projects. |
Project Types & Workflow Links
Project Types must be configured so you can categorise their projects according to the project type. The project type will appear within the 'Project Type' drop down list when defining a new project.
STEP 1: Go to Framework> Project Settings > Project Types and Workflow
STEP 2: Click 'Add new Project Type'.
...
STEP 3: Enter a title.
STEP 4: Select a workflow to be linked to the Project Type. A project type must be linked to a workflow which is what determines the internal structure of any project. Thus, you cannot delete a project type which has already been associated with a project via the workflow link..
STEP 5: By selecting 'Allow Period Values', the administrator can determine if monthly budgeting should be activated. This functionality gives the flexibility for the administrator to categorize which types of projects needs monthly budgeting.
If selected, budget values in Preliminary Budget object will be displayed by month. If un-selected, budget values will be displayed by year (default will be yearly).
STEP 7: Click INSERT. You can use the edit/delete icons to modify or remove an existing project type as required.
IPM List System Positions
System Positions page facilitates the Camms.Project administrator to assign responsible system positions to manage Camms.Project/IPM Lists.
Existing project positions are not used since those are defined for project levels and custom lists are managed outside the project level.
Standard system roles: Administrator, Project Manager and Project Creator positions are included as default in this area. For each system position, 'Can View', 'Can Add', 'Can Edit' and 'Can Delete' permissions are given.
IPM Administrator is a Super Role with all permissions, hence, aforesaid check-boxes are ticked and greyed-out.
When 'Can View' permission is un-ticked, rest of the permissions will become un-ticked and disabled.
...
In order to add a new System Position (only Administrators can add new entries):
First click on 'Add New System Position' icon.
Enter the position name and click insert.
...
Project Position
Project Position defines the level of security for each user of the system within a project. For example, the IPM Administrator has full security rights whereas a normal user has only limited security rights. As project positions are assigned to users on a per project basis, user security levels can vary from project to project.
STEP 1: Go to Framework> Project Settings> Project Position.
...
STEP 2: Click Add new Project Position.
...
STEP 3: Enter a title and a description for the position.
STEP 4: Administrator to link a position for a project type. A project position can be linked to multiple project types. This allows the project team to formulate the team from a unique set of project positions that are linked to the project type.
...
STEP 5 : You can choose to designate this position to the default Responsible Position by ticking the box. This enables the staff member in that position to be synchronised with the action which the project is linked to.
STEP 6 : Navigate to the Permissions tab, and select the permissions you want to apply to this position. You can select varying combinations of add, edit, delete and finish/signoff permissions on a per object basis. Please note that some objects can be configured in a way that makes certain fields invisible or read-only regardless of your Project Position.
...
Title / Object | Can View | Can Add | Can Edit After Sign Off | Can Edit | Can Delete | Can Finish / Sign Off |
|---|---|---|---|---|---|---|
Project Details | In default, ‘can view’ will be ticked for all objects, meaning all objects can be viewed by the position holder.
If a certain project position(s) should be restricted viewing certain objects, then administrator can do so by un-ticking the ‘can view’ tick box against the object for the particular position.
| Can add data to any field in this object. |
If ticked relevant position will be able to edit the object after sign off
| Can modify data present within any field in this object. | Can remove the data in any field in this object. | Can click the FINISH button within the Finish tab at the end of this object.
|
Project Board (refers to ALL instances of Project Board and Team Object) | Can assign new project board members. | Can modify current project board members. | Can remove current project board members. | |||
Project Linkage | Can create a project linkage. | Can edit existing project linkage. | Can remove existing project linkage. | |||
Interplan Linkage | Can create a linkage between an action or a task with the project | Can edit existing linkage | Can remove existing linkage | |||
Project Budget Implementation | Can add data to any field in this object. | Can modify data present within any field in this object. | Can remove the data in any field in this object. |
| ||
Project Budget Preliminary | Can add data to any field in this object. | Can modify data present within any field in this object | Can remove the data in any field in this object. | |||
Assessment (refers to Assessment Model Object) | Can conduct a new project assessment. | Can modify an existing project assessment via re-assessment. | ||||
Task (refers to Task Planning Object) | Can add new data to Gantt chart. | Can modify existing data present within the Gantt chart. | Can delete existing data from the Gantt chart. | |||
Task Progress (refers to Task Update Object) | ||||||
Evaluation (refers to Evaluation Assessment Object) | Can conduct a new project assessment. | Can modify an existing project assessment via re-assessment. | ||||
Sign Off (refers to ALL Sign Off Objects) | Can approve, reject or defer | Can modify an approval status already set. | Can reset the sign off status | N/A | ||
Close Project | Can select a staff member from the dropdown list and tick the checkbox. | Can reopen a closed project. | Can click the FINISH button within the Finish tab at the end of this object | |||
KPIs | Can add KPI comments. | Can modify KPI comments. | Can delete KPI comments. | |||
Risk Assessment | Can create new risk assessments. | Can edit existing risk assessments. | Can delete existing risk assessments. | |||
Business Case | Can create new business cases. | Can modify existing business cases. | Can delete existing business cases. | |||
Project Outputs | Can add data to this object. | Can modify data present within this object. | Can remove the data present within this object. | |||
Stakeholder Analysis | Can carry out new stakeholder analyses. | Can modify existing stakeholder analyses. | Can delete existing stakeholder analyses. | |||
Issue Register (refers to ALL instances of Issue Register Object) | Can add new issues. | Can modify existing issues. | Can delete existing issues. | |||
Attach Document (refers to ALL instances of Attach Document Object) | Can upload new documents and attach new URLs. | Can replace existing documents and URLs with different ones. | Can delete existing documents and URLs. | |||
Lessons Learned | Can add data to this object. | Can modify data present within this object. | Can remove the data present within this object. | |||
Assess Project Result | Can add data to this object. | Can modify data present within this object. | Can remove the data present within this object. | |||
Objectives Assessment | Can rate and provide comments for the objectives set. | Can modify existing ratings and comments. | Can delete existing ratings and comments. | |||
Project Scope (refers to Project Scope/Notes Object) | Can add data to any field in this object. | Can modify data present within any field in this object. | Can remove the data in any field in this object. | |||
Custom Object (refers to ALL instances of Custom Object) | Can add data to any field in this object. | Can modify data present within any field in this object. | Can remove the data in any field in this object. | |||
Quick Update (refers to Quick Update page) | N/A | Can modify existing progress information only - status, percent complete and comments. | N/A | N/A | ||
Business Rules
The Final Approval object's security is automatically taken from the Signoff Object's securities. Planning Link Object's security is automatically taken from Project Linkage object securities. Thus there is no separate security option for the above two objects.
There are certain fields which are Disabled for certain objects (i.e. Can Add is disabled for the Details object) and these will be disabled for all positions for that object (which means for the Details object none of the Board and Team members can add)
STEP 7: Select the permissions that are suited for the new position, and click 'Insert'.
Use the adjacent buttons to edit or delete a saved record.
A spell check button is also available at the top right corner.
STEP 8: Use the up/down arrows if you need to re-order the list of positions which will be visible within a Project's Board and Team object.
...