New and Improved Features
...
Configurable
...
- PMP-68583 As an end user I want to have Year in Incident ID to be in Fiscal year format
- PMP-68374 As an end user I want to have additional Personnel Types along with Contractor mapping
- PMP-4132 As a end user should be able to control Investigation requirement based on Incident Severity
- PMP-68370 As an end user I want to identify initial RCA while reporting incident
- PMP-61480 68712 As an end user I would like the ability to select Employee Name do not want to use Contractor Text field for Near Miss
- PMP-61480 As an end user I would like the ability to select Employee Name in Investigation Question screen
...
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- There is no widget to give 12 month rolling or YTD rate data for different Metrics of IMS
...
Impacts: No Impact
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
68583 As an end user I
...
want to have Year in Incident ID to be in Fiscal year format
Configurable: Yes
- Title: NM - Display Contractor InvolvedDynamicFiscalYearInternalID
- Public / Private: Public
- Default: EnabledDisabled
Existing System:
- There is no configuration available to hide the field "Is Contractor Involved?" in Near Miss reporting screen
- With the new personnel types being introduced having dedicated DDW Contractor field above field with is redundant and causes confusion among end users
...
- to change year format in Incident ID
Purpose: Flexibility to display Year or Fiscal Year in Incident ID
Enhanced System:
- "Is Contractor Involved?" in Near Miss reporting screen can be hidden with the custom setting
Impacts: Mobile, Reports
...
Configurable: Yes
- Title: DynamicFiscalYearInternalIDThere is a configuration to display Incident ID in format "CountryCode-LocationCode-FiscalYear-Module-Sequence" (US-OAKLAND, CALIF-19_20-I-0012) instead of "CountryCode-LocationCode-Year-Module-Sequence" (US-OAKLAND CALIF-20-I-0012)
- This is done for all screens where Incident ID, Case ID and Claim ID etc... are displayed
Impacts: Mobile
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: Yes, through back-end table.
- Title: NA
- Public / Private: PublicNA
- Default: DisabledNA
Existing System:
- There is no configuration to change year format in Incident ID
Purpose: Flexibility to display Year or Fiscal Year in Incident ID
Enhanced System:
- There is a configuration to display Incident ID in format CountryCode-LocationCode-FiscalYear-Module-Sequence (US-OAKLAND, CALIF-19_20-I-0012) instead of CountryCode-LocationCode-Year-Module-Sequence (US-OAKLAND CALIF-20-I-0012)
- This is done for all screens where Incident ID, Case ID and Claim ID etc are displayed
Impacts: Mobile
...
Does not have possibility of having additional Personnel type and map employee records to Contractors.
Purpose: Provide additional personnel types similar to Supervised Contract Employee along with option to map with Contractor
Enhanced System:
- Has additional Personnel Types "Offroll" and "Subcontractor" which has similar behavior and business rules as Supervised Contract Employee
- For these two personnel type there is one additional field provided named "Contractor". This field is auto-populated based on the contractor mapping available in Employee Profile
- Exclusions:
- Metrics, Dashboards or Widgets are not updated to include counts of Incidents with above personnel types
- These 2 personnel types will not be available as column in Hours and Head Count Import tool
Impacts: Mobile, Feed, Reports, BI
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
4132 As
...
a end user
...
should be able to control Investigation requirement based on Incident Severity
Configurable: Yes, through back-end table.
- Title: NADisplay ENV Incident Severity Question, Display PD Incident Severity Question, Display Vehicle Incident Severity Question
- Public / Private: NAPublic
- Default: NA
- Product - Enabled
- Customers - Disabled
Existing System:
- Does not have possibility of having additional Personnel type and map employee records to Contractors.
Purpose: Provide additional personnel types similar to Supervised Contract Employee along with option to map with Contractor
Enhanced System:
- Has additional Personnel Types "Offroll" and "Subcontractor" which has similar behavior and business rules as Supervised Contract Employee
- For these two personnel type there is one additional field provided named "Contractor". This field is auto-populated based on the contractor mapping available in Employee Profile
- Exclusions:
- Metrics, Dashboards or Widgets are not updated to include counts of Incidents with above personnel types These 2 personnel types will not be available as column in Hours and Head Count Import toolnot a way to control investigation requirement for ENV, PD and Vehicle Incident types based on a Incident's Severity
- Admins can configure the requirement based on Incident Type only and in this case even for a non-significant Incident Investigation is required
Purpose: Avoid investigation process for less significant Incidents
Enhanced System:
- Admins can define investigation requirement for Severe Env, PD and Vehicle Incidents
- Skip the investigation process for not sever Incidents
- If this question is turned on then Investigation requirement will be driven by this question 1st and later configuration of other fields will be considered
- If the question is answered No, the Investigation will be optional including Action Item and Management Review (user should be able to perform Management review without Investigation)
- If the question is answered Yes, the Investigation will be applicable as configured for the Incident Type or Severity field/Case Classification field
Impacts: Mobile, Feed, Reports, BI, Notification
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
68370 As
...
an end user
...
I want to identify initial RCA while reporting incident
Configurable: Yes
- Title: Display ENV Incident Severity Question, Display PD Incident Severity Question, Display Vehicle Incident Severity Question
- Public / Private: Public
- Default:
- Product - Enabled
- Customers - Disabled
Existing System:
- Does not a way to control investigation requirement for ENV, PD and Vehicle Incident types based on a Incident's Severity
- Admins can configure the requirement based on Incident Type only and in this case even for a non-significant Incident Investigation is required
Purpose: Avoid investigation process for less significant Incidents
Enhanced System:
- Admins can define investigation requirement for Severe Env, PD and Vehicle Incidents
- Skip the investigation process for not sever Incidents
- If this question is turned on then Investigation requirement will be driven by this question 1st and later configuration of other fields will be considered
- If the question is answered No, the Investigation will be optional including Action Item and Management Review (user should be able to perform Management review without Investigation)
- If the question is answered Yes, the Investigation will be applicable as configured for the Incident Type or Severity field/Case Classification field
Impacts: Mobile, Feed, Reports, BI, Notification
...
- Display FROI Root Cause
- Public / Private: Private
- Default: Disabled
Existing System:
- Does not have option to identify Root Cause while reporting incident
Purpose: Provide option for the user reporting the incident to identify initial Root Cause
Enhanced System:
- Has a new section in Report New Incident screen which is same as Root Cause screen (except for GL)
- This can be enabled only if Investigation RCA is turned off and Root Cause field in Action Item screen is hidden
- Comment field will not be available in case of Near Miss
Impacts: Mobile, Reports
| Anchor | ||
|---|---|---|
|
...
|
...
|
...
68712 As an end user I do not want to
...
use Contractor Text field for Near Miss
Configurable: Yes
- Title:Display FROI Root Cause NM - Display Contractor Involved
- Public / Private: Private
- Default: Disabled
Existing System:
- Does not have option to identify Root Cause while reporting incident
Purpose: Provide option for the user reporting the incident to identify initial Root Cause
Enhanced System:
- Has a new section in Report New Incident screen which is same as Root Cause screen (except for GL)
- This can be enabled only if Investigation RCA is turned off and Root Cause field in Action Item screen is hidden
- Comment field will not be available in case of Near MissPublic
- Default: Enabled
Existing System:
- There is no configuration available to hide the field "Is Contractor Involved?" in Near Miss reporting screen
- With the new personnel types being introduced having dedicated DDW Contractor field, above field is redundant and causes confusion among end users
Purpose: Avoid redundancy
Enhanced System:
- "Is Contractor Involved?" in Near Miss reporting screen can be hidden with the custom setting
Impacts: Mobile, Reports
| Anchor | ||||
|---|---|---|---|---|
|
Configurable: Yes. Back-end configuration
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- Does not have option to provide a question that allows to select Employees configured in Employee Management
...