New and Improved Features
Product Level
- PMP-53335 Autopopulate Report by name in Observers
- PMP-53336 View Observation Summary to Show Department Hierarchy
- PMP-53337 Provide % safe score and location/level name in the completed Print Observation Card
- PMP-4093 Behavior list to be SOA
Configurable
- PMP-44553 Module behavior library enhancement
- PMP-48262 Bulk select for "At Risk , At Safe , Feedback given ,comments ,NA" for peer to peer observation
- PMP-52368 Individual Observed picklist Field to be Mandatory /non mandatory configurationally
Autopopulate Report by name in Observers for Group Observations
Configurable : NA ,Product Level Change
Title : NA
Public / Private : NA
Existing System: Report by name field value doesn't appear in Observers field
Purpose :
- Person creating observation is mostly assumed to be an observer ,hence its relevant to display the report by name in observer field
Enhanced System:
- Report by name would appear in observer field when Observer type is user
- If Observer type is selected as Employee ,then Report by name would not appear in Observers field
- Existing Data : Report by name field value will be displayed in observer field ,when observer type is user
- Impacts : NA
- Reports : NA
- Notification : NA
- Cognos : NA
Group Observation -Report by Name in Observer
View Observation Summary to Show Department Hierarchy
Configurable : NA ,Product Level Change
Title :NA
Public / Private : NA
Default : Would appear for all the calibration equipments
Existing System: System didn't allowed to include any attachments with the calibration equipment
Purpose :User would require to upload the calibration certificate to the Equipment which current system didn't facilitate
Enhanced System:
- Existing Data :
- Impacts :
- Reports :
- Notification :
Calibration Equipment -Attachments section
Provide % safe score and location/level name in the completed Print Observation Card
Configurable : NA ,Product Level Change
Title : Some of the fields will use existing customer specific custom setting
- ShowHideSurveyField : Show
- IsTotalEmployeeExposureTimeApplicable Yes
- IsEngineeringControlsApplicableandMandatory yes
- IsAdminControlsApplicableandMandatory yes
- IsPPEApplicableandMandatory yes
Public / Private :NA
Default :Bulk upload for direct read instrument would appear
Existing System: User cannot bulk upload sample of equipment "direct read instrument" or "direct monitoring employee known"
Purpose : considering huge volume of sample creation of sample equipment type "direct read instrument / direct monitoring employee known" in application which is created only one at a time and also approved by some of our customer bulk upload for direct read instrument sample was implemented
Enhanced System:
- A new option for sample import - direct read instrument in Sample import utilities with Data Import Template and Import button similar to sample import-chemical
- User should be able to import based on permission .Similar to Sample Import CO Pump .i.e Add functionality dependency with Import utility for Direct monitoring
- Existing Data : No Change
- Impacts : Sample uploaded will appear in Sample Listing
- Reports : No
- Notification : No
- Cognos : No
Behavior list to be SOA
Configurable :Customer Specific
Title : IsVersionControlApplicable
Public / Private : Private
Default : will not appear in product
Existing System : In current system version history of a stressor is not maintained when its associated risk factors modified
Purpose :
- With no version history it was difficult for the user to differentiate between the risk level for a stressor , re-assess and reduce the risk level while conducting qualitative exposure assessment
Enhanced System:
- New section added in stressor as "Version History" .It would appear for both chemical and physical stressor
- It would have the following columns :
- Version - would show the number of times changes to stressor risk factor have been made
- Date - risk factor modification date .Format - September 10 ,2018
- Result - score and total exposure rating same as it appears in associate stressor Listing
- Each time a change made to a stressor risk factor ,system would maintain the version of the change ,date and Result (Score-Total Exposure Rating)
- By default system will considered the first record creation as version 1
- Each time the changes are made the version will get incremented by 1.(On each save button click the version will be incremented by 1)
- The changes for following risk factors will make the stressor undergo the version change : Exposure index ,Frequency index,Hazard rating ,Duration index,Dispersion
- Existing Data : version for all existing data will appear as 1
- Impacts : Associate Stressor Listing
- Reports : Qualitative Risk Assessment Details Report
- Notification : No
- Cognos : Yes
Qualitative Exposure Dashboard : New section "Version History " added
Associate Stressor Listing : New column "Version" added
Qualitative Risk Assessment Details Report
Module behavior library enhancement
Configurable :
Title :
Public / Private :
Default :
Existing System:
Purpose :
Enhanced System:
- Existing Data :
- Impacts :
- Reports :
- Notification :
Bulk select for "At Risk , At Safe , Feedback given ,comments ,NA" for peer to peer observation
Configurable :
Title :
Public / Private :
Default :
Existing System:
Purpose :
Enhanced System:
- Existing Data :
- Impacts :
- Reports :
- Notification :
Individual Observed picklist Field to be Mandatory /non mandatory configurationally
Configurable :
Title :
Public / Private :
Default :
Existing System:
Purpose :
Enhanced System:
- Existing Data :
- Impacts :
- Reports :
- Notification :