This article contains:
|
1. Overview of CAMMS Product Suite Structure |
CAMMS product suite consists of a number of products that is built atop a common database (i.e. all CAMMS products use 1 database in the backend per organisation).
...
A change done in one place, affects all others for above elements (e.g. staff name changed in strategy will reflect in project and risk).
2. Summary View of Linkages between Products |
...
3. Links from |
...
Camms.Strategy |
3.1 Actions
– An action can be linked to a Project (then Action’s Tasks will sync with Project’s Tasks).
– Risks created in the ‘Risks’ tab of an action becomes a ‘Project Risk’ in cammsrisk.
3.2 Tasks
– A task can be linked to a Project.
3.3 KPIs
– KPIs can be linked to Projects and Risks (however updates to KPIs always happens via cammsstrategy).
3.4 Environmental Analysis/SWOT
– All SWOT items (at strategy or corporate planning) can be converted to risks, and their solutions into risk actions.
4. Links from |
...
Camms.Project |
4.1 Project
– A project can be linked to an existing Action in cammsstrategy or a new one created (through ‘Interplan Link’ object).
...
Action Responsible Person = Field mapped as ‘interplan responsible person’ in Project Positions.
Action Start & End Date = Project Start and End Date.
Action % Complete = Project % Complete.
Action Progress Comment = Project Progress Comment.
Action Status = Project Status.
5. Links from |
...
Camms.Risk |
5.1 Risks
– Updates to Project Risks within cammsrisk will update the relevant project risk in cammsproject.
...
–Updates to Strategy Risks linked to Environmental Analysis items and Operational Risks linked to SWOT items, changes done to those risks and risk actions will reflect in cammsstrategy.
...
6. In- |
...
depth look at |
...
Camms.Risk (full solution) |
...