Administrators should understand that there two types of objects, compulsory objects and optional objects. Each compulsory object must be used within a workflow at least once.
Objects displayed with three dots shows that the particular object can be used multiple times within a workflow. These objects cannot however be duplicated within the same phase. Objects with one dot can only exist once within a workflow.
|
Object |
Compulsory within Workflow? |
Include Multiple Instances within one Workflow? |
Purpose |
|
Project Details |
Yes |
No |
This object captures key information about a project at its inception. More information |
|
Project Linkage |
No |
No |
This object enables the identification of linkages with organisational and planning hierarchies. A Project can be linked to Strategies and Service Profiles as well as specific Funding Partners (i.e. Agencies). |
|
Attach Document |
No |
Yes. Changes are incrementally updated |
This object enables the upload of documents and storage of web URLs. This object is independent and incremental. |
|
Preliminary Budget |
No |
Yes. Changes are incrementally updated |
This object allows users to undertake an initial budget estimate for a project. Users are able to include predefined budget lines as well as show where specific funding is coming from through the linked Funding Partners This object is independent and incremental. A user also has the ability to identify Ongoing Expenses for a project which can be taken into consideration during the approval process. |
|
Business Case |
No |
No |
This object allows users to develop business cases for a project based on a predefined form. It enables users to identify desirable objectives of the project as well its delivery mechanisms. |
|
Project Outputs |
No |
No |
Provides the users with the ability to identify the specific project outputs for the project they are creating. These are the key tangible items that will be achieved upon implementation. |
|
Project Board & Team |
Yes |
Yes. Changes are incrementally updated. |
Enables users to identify the key people involved in the initial and the implementation stages of the project. It allows access to specific areas of the project based on the allocation of roles to staff. This object is independent and incremental. |
|
Assessment Model |
No |
No |
Rates the project against a consistent set of criteria determined by the administrator. Based on the answers given a score is calculated to give the ability to compare projects against each other for final approval |
|
Evaluation Assessment |
No |
No |
Rates the project against a consistent set of criteria determined by the administrator. Based on the answers given a score is calculated to give the ability to compare projects against each other for final approval |
|
Stakeholder Analysis |
No |
Yes. Changes are incrementally updated. |
Referred to the action of analysing the attitudes of stakeholders. This can be done once or on a regular basis to track changes in stakeholder attitudes over time. This object is independent and incremental. |
|
Risk Assessment |
No |
Yes. Changes made to one instance reflected in all other instances. |
This comprises a range of steps which can be utilised to define variables and criteria in the risk assessment process. |
|
KPIs |
No |
No |
Allows a user to link KPIs currently within the planning areainterplan. The KPIs are used to assess the performance of the project and can be rated during project evaluation. |
|
InterplanPlanning Link |
No |
No |
Links tasks from within a project to tasks beneath the selected action in the planning areainterplan. |
|
Final Approval |
Yes |
No |
Used to record a formal stamp of approval (or rejection) for the continuation of the project from an authorised user. |
|
Custom Object |
No |
Yes. Changes made to one instance will NOT be reflected in all other instances. |
A generic object with a set of customisable fields
|
|
Scope / Project Notes |
No |
Yes. Changes are incrementally updated. |
A generic object with a set of 10 customisable text fields. This object is independent and incremental. |
|
Task Planning |
No |
Yes. Changes are incrementally updated. |
Permits users to enter tasks for a given project. All project task created within Task Planning area will be linked as sub tasks to the interplan action/task that the project is linked to. This object is independent and incremental. |
|
Issue Register |
No |
Yes. Changes are incrementally updated. |
Keeps a record of all issues within a project and helps users to monitor the status of issues and track the actions taken to resolve them. This object is independent and incremental. |
|
Task Update |
No |
Yes. Changes are incrementally updated. |
Functions similarly to ‘Task Planning’. You can create tasks for a project and update tasks as well. |
|
Project Implementation Budget |
Yes |
Yes |
Allows users to review the current budget information for a project. |
|
KPI Progress |
No |
Yes |
This enables users to review the performance of KPIs that have been created or linked to a project. |
|
Assess Project Result |
No |
No |
Lets users input comments on how well the project was implemented. |
|
Objectives Assessment |
No |
No |
Enables users to provide a rating against the objectives that were identified as part of the business case as well as provide textual information to justify the ratings |
|
Lessons Learned |
No |
No |
Enables users to specify any improvement that needs to be considered in future projects, highlighting the most positive things from the project. |
|
Close Project |
No |
No |
Enables authorised users to close the project. Usually placed towards the end of the workflow. |
Copyright © 2014-2015 CAMMS Online Help. All rights reserved.
Last revised: September 23, 2018