CS-VUE Update – Condition Data Uniformity
With a continued focus on providing best practice methodologies, CS-VUE have enhanced the system to capture data and ensure data uniformity when adding consent conditions.
Please login to the members only area on the right, using your CS-VUE Login to view the rest of this post.
[private]
Within CS-VUE we have the ability to assign each condition:
1. To a Project phase, if the condition requires an Activity to be done during a particular phase of a project (design, pre-construction, construction, post-construction, operational).
2. As an Action type condition (either a single or multiple event), if the condition requires an activity to be done on a particular date or dates.
3. As a General type condition, if there is no activity specified which needs to be carried out by the consent holder (e.g. advice notes). Therefore, these do not need signing off.
The latest enhancement to the system provides further rigor around the input of consent condition data in the following scenarios:
1. When adding a condition:
– the user must enter a condition type (it cannot be left as unassigned)
– the user will only be presented with the action date fields for completion when adding an Action type condition.
2. When Snoozing a condition (for example, when the user is unable at present to carry out an activity due to poor weather conditions):
– a warning message will be displayed if the user is attempting to snooze a condition well into the future (for multiple Action type conditions, the warning period depends on the event frequency).
– if it is a multiple Action type condition, the user will only be able to snooze the condition until the next scheduled action date. For example, for a yearly action scheduled for 1st August 2007, you will only be able to snooze up until 1st August 2008.
[private]
