The Safety Score allows a grace period for incidents, giving managers time to verify incident information and prepare a close-out before the Safety Score is affected.
Vetting rules still apply to the incident as normal. This means that incidents with an active grace period will still be taken into account by the vetting rules, albeit not impacting the Safety Score and DOC Subscore.
Duration of the Grace Period:
The grace period begins at the time the incident is created in the Platform. The duration of the grace period depends on whether the vessel DOC is a non-RightShip customer or a RightShip customer. Non-RightShip customers receive a 7-day grace period, while RightShip customers receive a 14 day grace period, excluding the waiting time for RightShip to review the incident.
Impact on the Safety Score and DOC Subscore:
During the grace period, the incident does not affect the Safety Score and DOC Subscore. However, to indicate that there is an incident with an active grace period, a clock symbol is displayed next to the Safety Score and DOC Subscore.
Visibility of Incidents with an active grace period:
While the grace period is in effect, incidents with an active grace period will be visibly displayed on the vessel timeline and activities similar to incidents without an active grace period. The incident Severity category will not show on the incident overview while the grace period is active.
Expiration of the Grace Period:
Once the grace period duration expires, the incident will impact the Safety Score and DOC Subscore based on the incident severity category. Completion of an incident review will also mark the expiration of the grace period.
Grace Period Logic:
-
The "Grace Period" is defined as:
-
14 days for RightShip full subscribing customers, and customers subscribed to a pre-defined number of vessels will get 14 days Grace for the vessels they are subscribed to.
-
7 days for non-subscribing customers,
-
Can also be manually overridden to any value for days (in the incident).
-
-
The "Total Time Accumulated" is defined as the time since the Incident Created date.
-
The "Nominal Handling Time" is defined as the “Total Time Accumulated” minus the total time the Incident is in Status “Review Required” plus one day for each time the Incident Status is in “Review Required”.
-
The "Elapsed Grace Period" is defined as the minimum of the “Total Time Accumulated” and the “Nominal Handling Time”.
-
The "Remaining Grace Period" is defined as the “Grace Period” minus the “Elapsed Grace Period”.
-
When the “Remaining Grace Period” is positive, the incident “Safety Score grace period” value should display as follows:
a. The ‘Valid for days’ = Remaining Grace Period
b. The Date = Date/time now + Remaining Grace Period
c. Format should be: Valid for x days (DD Mmm YYYY) -
When the remaining Grace Period is negative (i.e., the grace period has expired), or the incident Status is “Closed”, “Misreported” or “Cancelled” the "Safety Score grace period" value should display as a double dash: - -
-
When an Incident is created regardless of the incident source the ‘Safety Score grace period’ begins (therefore the Incident created date/time should equal the ‘Safety Score grace period’ start time)
-
When an incident is created (when the ‘Safety Score grace period’ begins) ‘Active in Safety Score’ should = No
-
When an incident Safety Score grace period is active (not expired) ‘Active in Safety Score’ should be blocked from changing to ‘Yes’ (A user should not be able to select the Override option ‘Incident should affect vessel’s Safety Score')
-
Given the remaining Grace Period becomes negative (i.e., the grace period has expired)
When Meets Safety Score Definition = Yes and (Severity = Category A or Category B or Category C)
Then ‘Active in Safety Score’ should = ‘Yes’ (should not show as an override) and the vessel Safety Score should recalculate
Logic above is from: [DEL-14825] GP 1 - Incident Overview - Field 'Grace Period' Logic - JIRA (atlassian.net)