New and Improved Features

Product Level change

• PMP-50639 As a 56372 As an end user I would like to see 12-month rolling Rate Trend on Home Page

Configurable

• PMP-68583 As an end user I want to have IMS module view in Home page

Configurable

• PMP-64056 As 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 an end user I 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-68712 As an end user I do not want to use Contractor Text field for Near Miss
• PMP-61480 As an end user I would like to map Incident Action Item to Investigation Root Causethe ability to select Employee Name in Investigation Question screen

Anchor
PMP-

...

56372 PMP-

...

56372

PMP-

...

56372 As an end user I

...

would like to see 12-month rolling Rate Trend on Home Page

Configurable: No

• Title: NA
• Public/Private: NA
• Default: NA

Existing System: 

• Does not have a dedicated view that shows quick statistics related to Incidents

Purpose: Create Incident statistics system view 

Enhanced System:

• Has system view for IMS module showing quick statistics.

...

• There is no widget to give 12-month rolling or YTD rate data for different metrics of IMS

Purpose: Provide Rates data with 12-month rolling and YTD option  

Enhanced System:

• Has a widget that allows users to view Incident Metrics by 12-month rolling, YTD or Monthly distribution

Impacts: No Impact

Image Added  Image Added

Back to top

Anchor
PMP-68583 PMP-68583

PMP-68583 As an end user I want to have Year in Incident ID to be in Fiscal Year format

Configurable: Yes

• Title: DynamicFiscalYearInternalID
• Public/Private: Public
• Default: Disabled

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

Image Added

Back to top

Anchor
PMP-

...

68374 PMP-

...

68374

PMP-

...

68374 As an end user I want to have

...

additional Personnel Types along with Contractor mapping

Configurable: NoYes, through back-end table

• Title: NA
• Public/Private: NA
• Default: NA

Existing System: 

• Does not have

  a dedicated view that shows quick statistics related to Incidents

...

• 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 system view for IMS module showing quick statistics.

...

• additional Personnel Types "Offroll" and "Subcontractor" which has similar behavior and business rules as Supervised Contract Employee
• For these two personnel types 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 two personnel types will not be available as column in Hours and Head Count Import tool

Impacts: Mobile, Feed, Reports, BI

Image Added

Back to top

Anchor
PMP-4132 PMP-4132

PMP-4132 As an end user I should be able to control Investigation requirement based on Incident Severity

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: 

• There is no way to control investigation requirement for ENV, PD and Vehicle Incident types based on an 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 severe Incidents
• If this question is turned on, then Investigation requirement will be driven by this question first 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

Image Added

Back to top

Anchor
PMP-

...

68370 PMP-

...

68370

PMP-

...

68370 As an end user I want to

...

identify initial RCA while reporting incident

Configurable: NoYes

• Title: NADisplay FROI Root Cause
• Public/Private: NAPrivate
• Default: NADisabled

Existing System: 

• Does not have a dedicated view that shows quick statistics related to Incidents

...

• the 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 system view for IMS module showing quick statistics.

...

• 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

Image Added

Back to top

Anchor
PMP-

...

68712 PMP-

...

68712

PMP-

...

68712 As an end user I do not want

...

to use Contractor Text field for Near Miss

Configurable: Yes

• Title: NM - Display Contractor Involved
• Public/Private: Public
• 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

Image Added

Back to top

Anchor
PMP-61480 PMP-61480

PMP-61480 As an end user I would like the ability to select Employee Name in Investigation Question screen

Configurable: Yes. Back-end configuration

• Title: NA
• Public/Private: NA
• Default: NA

Existing System: 

• Does not have option to provide a dedicated view that shows quick statistics related to Incidents

Purpose: Create Incident statistics system view 

Enhanced System:

• Has system view for IMS module showing quick statistics.

...

• question that allows to select Employees configured in Employee Management

Purpose: Provide ability to select Employee name in Investigation Question

Enhanced System:

• Has a new control type that provides ability to select an employee from the existing Employee Data base
• This will not impact existing customers
• If any customer want to have a question in Investigation Details section to identify Employee, this questions should be configured via a TA request
• Field level permission is applied to this fields as well

Impacts: Reports, BI

Image Added

Back to top