During audit execution user is able to export the audit criterion requirements to fill them out, when user is off-line. The resulting spreadsheet will have some data regarding requirements and hints and the evaluation values already filled out. After the spreadsheet has been filled out, user can import it. A pre-import screen will be available, to verify the modifications that have been made to data and content.
The association of occurrence with requirements during their evaluation was restructured, enabling user to inform an isolated action through SE Action plan besides the existing objects: occurrences, incidents, problems and action plans.
The screen has been restructured, improving navigation and data viewing. A timeline, filters and methods to highlight records were added.
During audit planning and execution user can add those interviewees who have not been registered in SE Suite.
User can configure the system so that auditors, lead auditor and audit team receive notifications at the end of each audit step.
▪Product: Allows to associate products from SE PDM with the audit scope. It also allows to configure the system so that the result can be entered by product.
▪Process activity: Allows to associate process activities from SE Process with the audit scope of the 1st party, 2nd party - from customer and 3rd party. It also allows to configure the system, so that the result can be informed by process activity.
A widget that has a chart was developed for analysis of conformity percentage, regarding first level requirements of audit criteria. An audit criterion can be selected to analyze the conformity percentage average of its requirements, grouping such criteria based on periods such as years, months and weeks. Some filters allow to restrict analyzed audits and to select the desired requirements. Some options to configure charts and the way they display as a radar are available now.
Two new widgets to track audit progress were developed.
▪My audits widget displays open audits in which logged user belongs to the audit responsible team.
▪In occurrence tracking user can see open occurrences of closed audits in which logged user is part of the tracking responsible team. Such occurrences may be action plans and isolated actions of SE Action plan, incidents of SE Incident, problems of SE Problem and occurrences of SE Action.