18.3 IMS Release Notes
New and Improved Features
Product Level change
- PMP-41274 As an end user should be able to save an incident as Draft
- PMP-47608 As an end user I would like to generate OSHA 300A CSV file for multiple locations
- PMP-53376 As a end user want to view Days/Hours since last incident (by incident type) in Home Screen
- PMP-53374 As a end user want to view "Days/Hours Since Last recordable" on Home page
- PMP-54221 As an end user I want to see Incident Count by Status in Home page
- PMP-53385 As a end user want to view count of Incidents by sub types in Home Screen
- PMP-53379 As an end user want to view Near Miss Incident Trend on home page
- PMP-53476 As an end user I would like to see existing IMS widgets at Level
- PMP-54206 As an end user I would like to see Yearly counts in Incident Count Widget
- PMP-52322 Make CAPA completion date field Mandatory in Incident Reporting screen
Configurable
- PMP-53352 As a System Admin I would like to configure different Investigation requirement by Inj/Ill Case Classification
- PMP-43534 As an Admin should be able to hide Work shift field in Near Miss reporting screen
- PMP-39299 As a System Admin want to make "Agency Notified" question Mandatory in PD Reporting screen
PMP-41274 As an end user should be able to save an incident as Draft
Configurable: No
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- Users do not have the ability to save Incident as draft i.e. without filling all Mandatory fields
- This causes delay in reporting Incidents
Purpose:
- In most cases when Incident happens the reporter does not have all details of the Incident. In this case they cannot make an entry in the system until they have all details. With Draft status they would be able to make an entry with Minimal information
Enhanced System:
- Allows to save an Incident with Minimal information with Draft status
- Displays Incidents in list screen as Draft and users can complete the detail report later
- Incident status will remain as Draft until all mandatory fields are filled.
- If all mandatory fields are filled in the first time Save the Incident will not be saved as Draft, the status would be "Detail Report Incomplete"
- No change in Mandatory fields or their indication
- Injury/Illness Incidents with Draft Status will not go to Metrics. For other Incident Types counts would be updated as it happens currently for respective Metrics
- All notifications triggered through a field would continue to behave as it is. Notifications would trigger when respective field is filled
- Detail Report Status and Investigation Report Status are removed and replaced with Incident Status column. The new column would display below statues:
- Draft
- Detail Report Incomplete (Hyperlink)
- Detail Report Completed / Investigation Report Incomplete (Hyperlink)
- Investigation Report Completed
- FROI question is moved to "Employee/Individual Details" section to align it with Multiple Injury screen and Mobile Pro.
- As in current system, the field is dependent on Personnel Type selection
Impacts: Mobile, Feed, Cognos
PMP-47608 As an end user I would like to generate OSHA 300A CSV file for multiple locations
Configurable: No
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- Does not a way to generate CSV file for multiple locations at a time
- Does not show a list of Locations where OSHA 300A has been saved for a Year
Purpose:
- Make OSHA 300A e-submission more effective by providing an interface to generate CSV file with multiple establishment data
Enhanced System:
- When a Level is selected the OSHA 300A screen turns into a List screen showing list of location where OSHA 300A has been saved for previous year
- Allows to select required rows and generate CSV file with those rows
- Allows to change the view filter to see data from different years
- Same permissions are applied to display Generate CSV Button as applied at location
- Displays only "Allow Roll Up=No" records as per logged-in user's scope
Impacts: None
PMP-53376 As a end user want to view Days/Hours since last incident (by incident type) in Home Screen
Configurable: No
- Title: NA
- Public / Private: NA
- Default: NA
Existing System:
- Does not show time since the last incident was reported for the Location/Level
Purpose:
- This is a useful information for Location users/Corporate Admins that indicates how safe is their work place
Enhanced System:
- Has a widget displaying Day/Hours since last Incident was reported
Impacts: None
PMP-53374 As a end user want to view "Days/Hours Since Last recordable" on Home page
Configurable: NA
- Title: NA
- Public / Private:NA
- Default: NA
Existing System:
- Does not show time since the last recordable incident was reported for the Location/Level
Purpose:
- This is a useful information for Location users/Corporate Admins that indicates how safe is their work place
Enhanced System:
- Has a widget displaying Day/Hours since last recordable Incident was reported
Impacts: None
PMP-54221 As an end user I want to see Incident Count by Status in Home page
Configurable: NA
- Title: NA
- Public / Private:NA
- Default: NA
Existing System:
- Does not a give a quick statistics of Incidents with different statuses
Purpose:
- To provide a quick statistics of Incidents pending different actions. This would help admins do quick follow ups and take required actions
Enhanced System:
- Has a widget that shows statistics of Incidents pending different actions
- Detail Report Incomplete
- Investigation Report Incomplete - Does not include Incidents where investigation is not Mandatroy
- Case Not Classified
- Claim Not Submitted
- If there is no Incident in the system for a specific Incident Type, it will not appear as a row in the Widget
- This would avoid questions from Customers as to why they are seeing an Incident Type they are not utilizing
Impacts: None
PMP-53385 As a end user want to view count of Incidents by sub types in Home Screen
Configurable: NA
- Title: NA
- Public / Private:NA
- Default: NA
Existing System:
- Does not have widgets showing Incident count breakup by the Sub type
Purpose:
- To provide break-up of Incident counts to the granular level for better analysis
Enhanced System:
- Has a new widget for each Incident type (except GL) showing counts by sub type
Impacts: None
PMP-53379 As an end user want to view Near Miss Incident Trend on home page
Configurable: NA
- Title: NA
- Public / Private:NA
- Default: NA
Existing System:
- Does not have a widget showing Near Miss Incident reporting trend at location/level
Purpose:
- Provide a view for user to see the Near Miss Incident reporting trend compared to previous year
Enhanced System:
- Has a widget that displays Number of Near Miss Incidents YTD and indicates the trend compared to previous year YTD
Impacts: None
PMP-53476 As an end user I would like to see existing IMS widgets at Level
Configurable: NA
- Title: NA
- Public / Private:NA
- Default: NA
Existing System:
- Does not display IMS widgets at Level making it less useful for Corporate Users
Purpose:
- Make it for useful for Corporate users by showing data by level.
Enhanced System:
- Displays rolled up data at every level for every Widget.
Impacts: None
PMP-54206 As an end user I would like to see Yearly counts in Incident Count Widget
Configurable: NA
- Title: NA
- Public / Private:NA
- Default: NA
Existing System:
- Has filter options for 30, 60 and 90 days
- Does not show counts by Year
Purpose:
- Make it more useful for Admin users to see statistics for Year
Enhanced System:
- Has Calendar Year and Fiscal year filter options
Impacts: None
PMP-52322 Make CAPA completion date field Mandatory in Incident Reporting screen
Configurable: NA
- Title: NA
- Public / Private:NA
- Default: NA
Existing System:
- Let's users make the CAPA completion date field blank and save the Incident
Purpose:
- Avoid issues in Action Item Detail page if CAPA Completion date is saved blank
Enhanced System:
- The field is made mandatory so that users cannot save the CAPA without completion date
Impacts: Mobile
PMP-53352 As a System Admin I would like to configure different Investigation requirement by Inj/Ill Case Classification
Configurable: Yes (No Custom Setting)
- Title: Configured through a configuration table
- Public / Private:NA
- Default: NA
Existing System:
- Does not have the ability to configure investigation requirement for Injury/Illness Incident based on the severity
Purpose:
- Provide system admins ability to configure different Investigation requirement based on Injury/Illness severity
- Save investigation time by adjusting Investigation requirement based on Severity of Injury/Illness
Enhanced System:
- Has option to configure Investigation section requirements in below four categories:
- Not Classified
- Recordable (Other Recordable, Restricted Work, Lost Time, Fatality) - Configuration will be same for all these classifications
- Not Recordable (Report Only, First Aid)
- Not Work Related
Impacts: Mobile, Feed
Note:
- The configuration would be applied depending on Most Severe case and not current case
- Configuration is available only to make different Investigation steps Mandatory/Optional.
- If no configuration by Case Classification is done, the current configurations would be applicable
- Configurations would be managed in IMS back-end and Customers need to contact ProcessMAP support for managing it
PMP-43534 As an Admin should be able to hide Work shift field in Near Miss reporting screen
Configurable: Yes
- Title: NM - Work shift
- Public / Private: Public
- Default: Disabled
Existing System:
- In existing system Work Shift/ Job Shift is a mandatory field in general details of Near Miss reporting screen
- For other incident types Work Shift/ Job Shift has configuration to show and hide
Purpose:
- Have a configuration so that it is consistent with other Incident types
Enhanced System:
- Has separate configuration to hide work-shift field for Near Miss Incident type
Impacts: Mobile, RC, Reports
PMP-39299 As a System Admin want to make "Agency Notified" question Mandatory in PD Reporting screen
Configurable: Yes
- Title: PD - Agency Notified
- Public / Private: Public
- Default: Disabled
Existing System:
- The field in Damage Summary section is not mandatory and System admin do not have flexibility to make it mandatory
Purpose:
- Provide flexibility for system admin to make the field mandatory
Enhanced System:
- Has a configuration for system admins to make the field mandatory
Impacts: Mobile
© 2018 ProcessMAP Corporation, All Rights Reserved Confidential, may not be disclosed without the express permission of ProcessMAP Corporation