Versions Compared

Version Old Version 7 New Version Current
Changes made by

Vikram Vemula

Aravind Putta

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
234
234
New and Improved Features 

Product Level Change

  • No itemsNone

Configurable

Performance

  • PMP-94436 - IMS-Autocomplete Control Performance Improvement

Technology

  • PMP-94407 - AAP Retail Calendar - DB Design & Script to load data

  • PMP-94443 - IMS-Checkmarx Version Upgrade (9.5.0)

  • PMP-94777 - IMS Datamart - SQL Server Upgrade 2019

  • PMP-93190 - IMS-SQL Server Upgrade 2019 - Feed

Anchor
94330
94330
PMP-94330 -

...

User would like to have the ability to generate and export OSHA 300-301 CSV file

Configurable: Yes

  • Title: OSHA 300/301 Case Data E-Submission

  • Public/Private: Public

  • Default: No

Existing System: DoesnCurrently,systemdoesn't have a list screen to view display OSHA 300/301 data and also generate a CSV file.

Purpose: To comply with regulatory requirements.

...

  • A new permission 'E-Submission of OSHA 300/301 Case Data' will be  is added under Work Place Incident Report - Injury/Illness > Regulatory Forms.

  • By default, it would be 'No'.

New Menu:

  • The new menu 'OSHA 300/301 Case Data' will be is shown below 'OSHA 301' menu.

  • This menu will be driven based on the permission (details given in the below section).It and data will be shown for both 'Location' and 'Level' (**only US Locations and Level).

New System Views:

  • There will be two System Views:

  • All Cases - Previous Year (Default View)

    • All Cases - Current Year

  • This screen will show the records for the following Cases i.e. similar to the implementation for 'OSHA 300' and 'OSHA 301' List screens:

    • Other Recordable

    • Restricted Duty

    • Lost Time

    • Death

Two System Views:

  • All Cases - Previous Year (Default View)

  • All Cases - Current Year

300 & 301 Review Status Display & Validation:

  • 300 & 301 Screen review status will be displayed on the list.

  • Only if all required fields are completed and saved, then 300 & 301 review is treated as complete.

  • CSV can be generated only once both screen's status turns 'Complete'.

Generate CSV :

  • There will be a 'Generate CSV' button at the top right corner of the screen.

  • *Note: There won't be any separate permission to enable/disable this button.

Impacts: Mobile, Reports, RC, Cognos, Outbound API

...

New Permission:

...

New Menu:

...

Impacts: None.

Back to top

Anchor
95310
95310
PMP-95310 - User would like to edit DOB field in OSHA 301 screen based on a configuration

Configurable: Yes

  • Title: Display Vehicle Accident Rate KPIIMSEmpDOBPrivacyInfoShowYN

  • Public/Private: Public

  • Default: No Yes

Existing System: 

  • The Vehicle Incident Metrics do not capture the 'Vehicle Accident Rate'.

Purpose: 

  • Add a new KPI 'Vehicle Accident Rate' to the 'Vehicle Incident Metrics'.

Enhanced System:

  • The new KPI 'Vehicle Accident Rate' has been added under the 'Incident rate' section.

  • Vehicle Accident Rate = (Number of Vehicle Accidents*1,000,000)/Miles Driven

Impacts: Outbound API, Cognos

Back to top

...

Configurable: Yes

  • Title: Enable Confidential Incident Feature

  • Public/Private: Public

  • Default: Yes

Existing System: 

  • Does not have the feature to hide any incident that requires privacy. So such type of incidents are deleted from the system (if already reported) and managed elsewhere to avoid disclosure.

Purpose: 

  • Introduce a new feature so as to maintain the Confidential Incidents in the application with limited access to the authorized users.

Enhanced System:

Impacts: Mobile, Reports, RC, Insight, Outbound APICurrently, DOB field in OSHA 301 screen is auto-populated from the foundation employee profile and it is non-editable in OSHA 301 screen.

Purpose: To provide flexibility to the OSHA 301 user.

Enhanced System:

  • User will be able edit DOB field in OSHA 301 based on permission and configuration.

  • The existing custom setting (Which is already in use in the reporting screen) is used in the OSHA 301 screen as well.

  • Additionally, if the user has edit OSHA 301 permission, then the DOB field would be visible and available for editing.

  • If the user only has view OSHA 301 permission, then DOB field would just show as “Privacy Information”.

Impacts: None.

...

Anchor
95710
95710
PMP-95710 - User would like to submit 300A data using the API Token

Configurable: No

  • Title: OSHA Form 300A Electronic Submission using API Token

  • Public/Private: NA

  • Default: NA

Existing System: Currently, the system doesn't have an option to submit 300A data to OSHA's ITA (Injury Tracking Application) using the new API Token process as the 300A data was previously transmitted to OSHA’s ITA by entering ITA account credentials

Purpose: To comply with regulatory requirements.

Enhanced System:

  • Enhanced the submit using OSHA API option to allow users to paste an API Token copied from OSHA’s ITA (Injury Tracking Application) in order to transfer a location's 300A data to ITA.

    Image Added

  • Added guidance information to the information pop-up.

    Image Added

Back to top