New and Improved Features
Product Level change
...
New and Improved Features
Product Level change
- PMP-70560 - Ability to Conduct Employee-Level Audits
- PMP-54398 - Introduce Audit ID to Uniquely Identify the Audit
- PMP-4619 - Enhance Notifications with the Ability to Configure Alerts and Reminders Feature for Audits as well as Findings
- PMP-68363 - Introduce a Configuration to Hide the Section Applicability feature at the Protocol Level
- PMP-68989 - Include More Fields in Audit Action Item Source Details to Uniquely Identify its Source
- PMP-71013 - Increase the Character Count of Audit Synopsis Field to 10,000 from Existing 5,000 Characters
- PMP-69620 - Enable Action item Item ID, Department and Asset field for audits action items
- PMP-73196 - Changes to Pop-Up Style in Audits Questionnaire Screen to improve the usability
- PMP-69325 - Add "Doughnut" and "Exploded Pie" to all chart widgets in Audit Management Dashboard
Configurable
- None
Configurable
- None
Anchor | ||||
---|---|---|---|---|
|
...
- Ability to
...
Conduct Employee Level Audits
Configurable: Yes from backend. backend
- Title: NA
- Public/Private: NA
- Default: NAEnabled at product level.
Existing System: Currently, we don't have this feature. feature
Purpose: To provide the ability to conduct by employee audit and by asset audit.a "By-Employee" audit
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates. Templates
- It would be available only for Site Audits and it would be a non-mandatory field. field
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected. Employee
- Users would be able to fill the questionnaire by asset or employee
Field Deprecation: Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated
...
...
Impacts: Mobile, Reports and BI.
Creating Audit:
Questionnaire Screen:
Anchor | ||||
---|---|---|---|---|
|
...
Uniquely Identify the
...
Audit
Configurable: Yes
- Title: DynamicIAuditInternalIDFormat
- Public/Private: Private
- Default: Country Code - Location Code - Audit Create Year (YY) - Audit Type (C or S) - Sequence by Location and Year
Existing System: Doesn't have any system generated IdID
Purpose: To uniquely identify an Audit
...
- Audit ID would be generated for every Audit by Location. Location
- The default format would be - Country Code - Location Code - Audit Create Year (YY) - Audit Type (C or S) - Sequence sequence by Location and Year
- System The system would support ID format configurations like Location Name/Code, Calendar/Fiscal Year, Delimiter Configuration and Audit Type Code. Code
- Audit ID would be displayed across the module in all relevant screens and Audit Header as shown in the screen shot below. below
Impacts: Mobile, Reports , BI. and BI
Display in List Screen:
Display in Audit Top Header:
Anchor | ||||
---|---|---|---|---|
|
...
Notifications with the
...
Ability to
...
Configure Alerts and Reminders Feature for Audits as well as
...
Findings
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: There is no provision to configure alerts and reminders. reminders
Purpose: To give more flexibility in notifications. notifications
Enhanced System: User would be able to create create:
- Audit Alerts and Reminders configurations would have below fields to setup
- Audit Start Date, Audit End Date, Audit Program Status configured.
- Finding Alerts and Reminders.
Impacts: No Impact
Notifications List Screen:
Existing Event Notifications Configuration:
Audit Reminders:
Audit Alerts:
Finding Reminder:
Finding Alerts:
...
- configured
- Recipients: Lead Auditors, Lead Auditor Supervisor, Team Members, User selected for Audit Status Change
- Finding Alerts and Reminders
- Due Date, Status Changed to Closed
- Recipients: Finding Owner(s) and Assigned By, Finding Responsible Person(s), Lead Auditors and Team Members
Impacts: None
Notifications List Screen:
Existing Event Notifications Configuration:
Audit Reminders:
Audit Alerts:
Finding Reminder:
Finding Alerts:
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature. feature
Purpose: To provide the ability to conduct by employee audit and by asset audit.make a section mandatory to answer
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-TypeSection Mandatory" with values - AssetYes, Employee and Department.No
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
- on the questions list screen
- For all the existing protocols, this field would default to "No" and user can update to "Yes" if required by protocol
- Once a section is mandatory, user wouldn't be able to select the option of making a question section not-applicable
- We have also given additional flexibility to user while creating a protocol to copy all questions from the selected question section
Impacts: Mobile.
Question List Screen:
Question Details Screen:
Questionnaire Screen:
Anchor |
---|
...
|
...
|
...
68989 - Include More Fields in Audit Action Item Source Details to Uniquely Identify its Source
Configurable: No Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature. have only Source ID
Purpose: To provide the ability to conduct by employee audit and by asset audit.user with greater ability to uniquely identify the source of action item
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
- Introduce a new field - "Audit Sub-Type" with values - Asset, Employee and Department.
- This new field would be available for Basic Audits, Advanced Audit and Audit Templates.
- It would be available only for Site Audits and it would be a non-mandatory field.
- On selecting the audit subtype, the user would see a picklist for him to select Department or Asset or Employee based on the subtype selected.
- Currently, we have a field "Audit By Department - Yes/No". This field would be deprecated.
- Users, would be able to fill the questionnaire by asset or employee.
Impacts: Mobile, Reports and BI.
...
Configurable: Yes from backend.
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have this feature.
Purpose: To provide the ability to conduct by employee audit and by asset audit.
Enhanced System: Changes include:
...
- Finding Action Item will have below source fields:
- Source ID: Finding ID (already available), Finding Title, Audit ID, Program
- Question Action Item will have below source fields:
- Source ID: Question ID (already available), Question Title, Audit ID, Program
- Program Action Item will have below source fields:
- Source ID: Audit ID and Program
Impacts: None
Anchor | ||||
---|---|---|---|---|
|
Configurable: No
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we allow the user to enter a maximum of 5,000 characters
Purpose: To capture additional information
Enhanced System: Changes include:
- Increase the character limit to 10,000 at a product level so that users can capture additional information
- Changes to reports to accommodate the increased field size limit
- Changes to BI models to support this change
Impacts: Mobile, Reports and BI
Anchor | ||||
---|---|---|---|---|
|
Configurable: Yes from the backend
- Title: NA
- Public/Private: NA
- Default: NA
Existing System: Currently, we don't have these fields enabled for an audits action item
Purpose: To provide the ability to add more details to an action item
Enhanced System: Changes include:
- Action Item ID to uniquely identify an action item. Sample format is: US-WESTLAKE-2020-AUD-10001
- Enable department field which would be non-mandatory
- Enable Asset field which would be non-mandatory
Impacts: Mobile, Reports and BI.