...
This was released on 23rd January 2021 and includes the following new features and enhancements to improve your user experience within the system.
List of release items:
|
1. Introducing a new dataset to capture Incident Review data |
A new dataset ‘Incident_Review_STND’ is introduced to capture the data from the review tab of an incident.
All fields configured within the review object is included in this dataset.
Field Name | Data Type | Remarks |
|---|---|---|
INCIDENTID | Unique Identifier | This field can be used to link with other datasets |
Incident Title | Text | The title of the incident |
Review Frequency | Text | The frequency type of the incident |
Last Reviewed By | Text | The person who last reviewed the incident |
Last Reviewed Date | DateTime | The date which the incident was last reviewed |
Next Review Date | DateTime | The next review date of the incident |
Review Comment | Text | The review comment |
Incident Review Status | Text | The review status of the incident |
...
The below table shows you the default relationship which you can set up as a System Administrator.
Join Type | Data Object | Join Field | Foreign Data Object | Join Field | |
|---|---|---|---|---|---|
LEFT | Incident_IncidentDetails_STND | INCIDENTID | = | Incident_Review_STND | INCIDENTID |
...
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
2. Introducing a new dataset to capture the Scorecard details |
A new dataset ‘Planning_ScorecardDetails_STND’ is introduced to capture the details of a scorecard.
The following fields will include in the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
SCORECARDID | Unique Identifier | This field can be used to link with other datasets |
Name | Text | The name of the scorecard |
Description | Text | The description of the scorecard |
Responsible Officer | Text | Name of the responsible officer of the scorecard |
Scorecard Area | Text | The assigned area of the scorecard |
Scorecard Group | Text | The assigned group of the scorecard |
Target | Numeric | Target value of the scorecard |
Variance | Numeric | Variance value of the scorecard |
...
3. Introducing new datasets to capture the recurring actions data in Camms.Compliance |
Two new standard datasets are introduced to capture the recurring actions' progress update data, within a Compliance.
...
If the compliance action is recurring, this new dataset will capture the data from the 'Action Progress Update' tab. The following fields are captured via this new dataset:
Field Name | Datatype | Remarks |
|---|---|---|
ACTIONID | Unique ID | This is a unique identifier for each Compliance Action and can be used to link with other datasets |
Action Name | Text | Title of the action |
COMPLIANCEID | Unique ID | This is a unique identifier for each compliance record and can be used to link with other datasets |
Compliance Title | Text | Title of the compliance |
Review Frequency | Text | Review frequency for the particular action |
Review Recurrence End By | DateTime | Date when the next review will end |
Last Reviewed By | Text | Person who last reviewed the action |
Last Reviewed Date | DateTime | When the action was last reviewed |
Next Review Date | DateTime | Date of the next review |
...
This dataset will capture the data for each review period of the action. Therefore, records will be retrieved for each period containing the data, for the following fields of an action:
Field Name | Datatype | Remarks |
|---|---|---|
ACTIONID | Unique ID | This is a unique identifier for each compliance action and can be used to link with other datasets |
Action Name | Text | Title of the action |
COMPLIANCEID | Unique ID | This is a unique identifier for each compliance record and can be used to link with other datasets |
Compliance Title | Text | Title of the compliance |
Review Period | Text | Review period based on the frequency the user has selected |
Status | Text | The status of the review for the corresponding period |
Percentage Completed | Numeric | Percentage value of completion |
Comment | Text | Comment for the corresponding review period |
...
The below table shows you the default relationship which you can set up as a System Administrator.
Join Type | Data Object | Join Field | Foreign Data Object | Join Field | |
|---|---|---|---|---|---|
LEFT | Compliance_Actions_STND | COMPLIANCEID | = | Compliance_ActionProgressUpdate_STND | COMPLIANCEID |
LEFT | Compliance_Actions_STND |
| = |
|
|
...
Data Model/Relationships - Camms.Support Documentation - Confluence (atlassian.net)
4. Modified Task Details Current Phase dataset to capture the latest baseline dates |
The ‘Project_TaskDetailsCurrentPhase_STND’ dataset is modified with the inclusion of two new fields, to capture the latest baseline data. These fields will capture the start and end date for each task of the latest baseline.
The following new fields are added to the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
Latest Baseline Start Date | DateTime | The start date of the task, captured from the latest baseline |
Latest Baseline End Date | DateTime | The end date for the task, captured from the latest baseline |
...
5. Modified KPI datasets to extract historical values for KPIs |
The following datasets are to be modified to capture historical values for KPIs. With this additional fields to the datasets, you will be able to report on the previous year’s performance data. The previous year is detected based on the period you selected via the parameters for each of these datasets.
...
The following new fields are added to the dataset:
Field Name | Data Type | Remarks |
|---|---|---|
Last Period Actual | Numeric | KPI Actual value for the immediate last year’s period |
Last Period Target | Numeric | KPI Target value for the immediate last year’s period |
Last Period YTD Actual | Numeric | KPI YTD Actual value for the immediate last year’s period |
Last Period YTD Target | Numeric | KPI YTD Target value for the immediate last year’s period |
...