Skip to end of banner
Go to start of banner

21.2 IMS Release Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 7 Next »

New and Improved Features

Product Level Change

Configurable

PMP-58743 As an end-user, I need a quick view of the current status of the Incident in the Summary screen

Configurable: No

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

Existing System

  • Does not show the Incident workflow and the status of different sections in the Incident Summary screen
  • The user has to scroll down to different sections to view the status
  • The user does not know which section to go to after completing the Incident report

Purpose: 

  • Provide a quick view of Incident workflow by showing the different steps and respective status

Enhanced System:

  • Displays the Incident workflow and respective status at the top of the summary screen
  • Guides users to the next step they need to complete
  • Provides navigation to the respective section in the summary screen
  • When hovering over with their mouse, the user sees additional details as a tool tip

Impacts: No Impacts

Back to top

PMP-54645 As an end-user, I would like to group body parts into larger categories for Data Trending

Configurable: No

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

Existing System

  • Does not have the flexibility to map individual body part look-up values to Body Part diagram

Purpose: 

  • Provide a widget for better data analysis

Enhanced System:

  • Has the flexibility to map the body part look-up value to body part diagram
  • As of now, the option is available only from the backend
  • In a future version, a UI will be provided so that users can view and manage the mapping on their own
  • Existing look-up value
    • One-time mapping has been done for all customers' existing body part look-up values
    • Any lookup value which could not be mapped on the body part diagram has been mapped to a value named Other
    • Customers can view the mapping details from Cognos for now

Impacts: Reports, Cognos

Back to top

PMP-70213 As an end-user, I want to see the incident count by body part on the Body Diagram

Configurable: No

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

Existing System

  • Does not have a widget to show the Incident Count by body part on the Body Diagram

Purpose: 

  • Better representation on the Incident count to indicate the most affected body part

Enhanced System:

  • Has a widget that displays Body Part diagram and shows the Incident count for each Body Part group
  • When hovering over with their mouse, the user sees the break down of counts by each body part look-up value mapped to the Body Part group
  • As of now, there is no navigation on this widget

Impacts: No Impacts

Back to top

PMP-73225 As an end-user, I want to see NM Incident Rate in the Metrics screen

Configurable: No

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

Existing System

  • Does not have any rate metric for Near Miss Incident

Purpose: 

  • Leading Indicator

Enhanced System:

  • Has "Near Miss Incident Rate" metric in Corporate and Country Metrics screen under Near Miss section
  • Formula is "Number of Near Miss Incidents (existing metric)*200000/Total Hours worked" where Number of Near Miss Incident counts every Near miss incident irrespective of detail report status

  • Personnel type filter will not be applicable in Metric screen on this Metric

Impacts: Report Central (Safety Metrics Report), Data Mart and Cognos

Back to top

PMP-77339 Vehicle Incident Outbound API

Configurable: No

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

Existing System

  • Does not have a  way to extract Vehicle Incidents data along with all other sections

Purpose: 

  • Provide export option

Enhanced System:

  • Similar to existing Injury/Illness incident type, standard Outbound API for Vehicle Incident Type is developed
  • It can be used to extract Vehicle Incident Type data along with all other sections by location

Impacts: No Impacts

Back to top

PMP-77340 Environmental Incident Outbound API

Configurable: No

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

Existing System

  • Does not have a  way to extract Environmental Incidents data along with all other sections

Purpose: 

  • Provide export option

Enhanced System:

  • Similar to existing Injury/Illness incident type, standard Outbound API for Environmental Incident Type is developed
  • It can be used to extract Environmental Incident Type data along with all other sections by location

Impacts: No Impacts

Back to top

PMP-70513 As an end-user, I want the ability to identify involved asset for an Incident

Configurable: Yes

  • Title: Display Asset Field
  • Public/Private: Private
  • Default: Hidden
  • Title: Was Asset Involved Mandatory
  • Public/Private: Public
  • Default: Optional


Existing System

  • Cannot identify involved asset for an incident

Purpose: 

  • Ability to identify involved asset in the incident 

Enhanced System:

  • Has fields in Report New Incident screen, General Details section to identify involved asset 
  • Multiple assets can be selected, if required
  • These fields will be available only if customer has subscribed for Asset registry component
  • Based on selected assets Incident count will be displayed in the existing Asset widget

Impacts: Notification, Mobile, Reports, Congos

  

Back to top


  • No labels