SoluDyne QIS

QIS Quality Improvement System

Continous Quality Improvement for Both Large and Small Business

The Quality improvement module is designed to handle all types of observations: improvement proposals, observations, deviations, applications for exemptions, audit findings, HSE and other types of events.

The system focuses on the important principles of the ISO standard and ensures an approach to quality that should be preventive and not corrective.

Net Account

Best Practices & Other Governing Elements

05 - QIS

01 - Basic QIS Understanding

B-12899 - Report Type Group

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the Report Type Group functionality in SoluDyne.

01 Description
Report Type Group must be set by the Originator when reporting a QIR. The Report Type Group is a group containing Report Types.

Several Report Type Groups can add an extra level for tailoring the Quality Improvement Process in SoluDyne. Result: Finetuning of statistics and routing of the QIRs when case prosecuting.

02 Example
Report Type Group - Report Type

  1. Energy Pro Ltd
    1. HSEQ
    2. Non-Conformance
  2. Energy Pro Administration
    1. HSEQ
    2. Non-Conformance
  3. Energy Pro Manufacture
    1. HSEQ
    2. Non-Conformance
  4. Energy Pro Engineering
    1. HSEQ
    2. Non-Conformance

B-12900 - Report Type

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the Report Type functionality in SoluDyne.

01 Description
Report Type must be set by the Originator when reporting a QIR. The Report Type is loaded when Originator choose a Report Type Group.

Several Report Type can add an extra level for tailoring the Quality Improvement Process in SoluDyne. Result: Finetuning of statistics and routing of the QIRs when case prosecuting.

02 Example
  1. HSE
  2. Fault Reporting
  3. Observation
  4. Process Non-Conformance
  5. Product Non-Conformance
  6. Improvement Suggestion
  7. Audit

B-16374 - QIS on the Homepage

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes how QIS can be accessed from the Home Page.

01 Description
A QIS tab can be activated on the homepage to make navigation easy for the end user.

For more information on homepage set-up, see B-11791 - Customizing QIS Links on Homepage.

 
Figure 01: QIS Tab on the Homepage

B-16375 - QIS Gadgets

00 Overview
01 Description
02 Example

00 Overview
A shortcut to QIS reports and statistics can be made accessible through the users Gadget Panel.

01 Description
Quality Improvement System Reports

The QIS reports gadget provides a shortcut to QIS reports and statistics from the users workque. The gadget needs to be activated in order to be viewed. For more information on the Gadget Panel, see B-10560 - Using SoluDyne Gadgets.

For more information on administering/setting-up gadgets, see B-10560 - Using SoluDyne Gadgets.

  
Figure 1: QIS Reports Gadget.

Quality Improvement Process

A gadget for the users QIP's can also be set-up to be an active shortcut in the gadget panel. This is a seperate gadget for viewing QIP's. Active reports going through the improvement process steps will still appear in the workqueue.

 
Figure 2: QIP - Quality Improvement Process Gadget.

B-16380 - QIS in the Workqueue

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes QIRs in the users workqueue.

01 Description
When a user makes a Quality Improvement Report, this triggers a Quality Improvement Process which is visible in their workqueue.

The originator will have a link in their workqueue in the form of a receipt until they sign this out.

As the report is signed through the different phases it will move to the workqueue's of those associated users linked to the corresponding roles in the overall process.

  
Figure 1: A Quality Improvement Process on step 1 showing in the user's workqueue.

B-16381 - The QIR Button

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes the functionality of the QIR button on the toolbar.

01 Description
A Quality Improvement Report can be generated from anywhere in the system using the QIR icon in the SoluDyne toolbar.

The Report will automatically tie to whichever node the user is on at the time (eg. a flowchart). This makes it easier and faster for users to generate observations for anything in the system. This is easily overridden if the QIR does not concern the present node.

Overview of the QIR Button on the SoluDyne Toolbar

 

  1. By clicking the Quality Improvement Report button, a report can be generated from anywhere in the system.  

 

  1. Once the user clicks the QIR button, a pop-up will appear asking whether the user would like to start a new Quality Improvement Process. Click OK.

  

The report will appear in the editor window. In this example, the system is set-up so that the originator, entry date and time are automtically entered into the system.

  1. Write a suitable title for the QIR Report in the Title field.
  2. Choose the requested Report Type Group from the dropdown menu.
  3. Choose a suitable Report Type from the dropdown menu.

  

  1. In this example, the user has chosen Dispensation as the Report Type.
  2. Fill in the form that appears below. The form will vary depending on the Report Type chosen.
  3. After completed the QIR Report, sign the form in the Signature field.

02 - Reporting

B-12844 - QIR - Audit

Overview

This Best Practice describes how to fill out a QIR for the Report Type Audit in SoluDyne. The Report Type for Audit is used during internal or external process compliance audits.

Prerequisites

N/A

Description

 

  1. Select the Quality Improvement Report button on the SoluDyne toolbar and click OK to create a new QIS Report.

  

  1. Write a suitable title in the Title field.
  2. Select the relevant Report Type Group.
  3. Select the relevant Report Type. In this case, Audit.

  

  1. Audit is chosen as Report Type. The report fields will vary depending on the chosen Report Type.
  2. Ensure that the correct Recipient is chosen.
  3. Write a description.
  4. Add file, if relevant.
  5. Sign the QIR Report in the Signature field.
  6. Click on Send Report. 

Reports can also be saved by using the Save Draft button, or cancelled using the Cancel Report button. If saved, the report will stay in the Originator's workqueue until it is signed.

B-12845 - QIR - HSE Occurences

Overview

This Best Practice describes how to fill out a QIR for the Report Type HSE Occurance in SoluDyne. The Report Type for HSE Occurrences is used to describe incidents related to personnel, equipment or the environment.


Prerequisites

N/A

Description

  

  1. Select the QIR button on the SoluDyne toolbar and click OK to create a new QIR Report.

   

  1. Give the report a title. 
  2. Select the relevant Report Type Group.
  3. Select the relevant Report Type. In this case, HSE Occurences. The report fields will vary depending on the chosen Report Type.
  4. Add additional information. Fields marked with a blue bullet are mandatory to fill out.

     

  1. Add files, if relevant.
  2. Sign the QIR Report in the Signature field.
  3. Click on Send Report.

Reports can also be saved by using the Save Draft button, or cancelled using the Cancel Report button. If saved, the report will stay in the Originator's workqueue until it is signed.

B-12846 - QIR - Fault Report

Overview

This Best Practice describes how to fill out a QIR for the Report Type Fault in SoluDyne. The Report Type for Fault Reporting is used for specifying faults in systems or equipment. 

Prerequisites

N/A

Description

  

  1. Select the QIR button on the SoluDyne toolbar and click OK to create a new QIR Report.

   

  1. Give the QIR a title.
  2. Select the relevant Report Type Group.
  3. Select Fault Reporting in the drop down menu for Report Type. 

   

  1. Fault Reporting is chosen as the Report Type. The report fields will vary depending on the chosen Report Type.
  2. Add additional information. Fields marked with a blue bullet are mandatory to fill out.

 

  1. Continue to add additional information, if required.
  2. Add files, if relevant.
  3. Sign the report in the Signature field.
  4. Click on Send report.

Reports can also be saved by using the Save Draft button, or cancelled using the Cancel Report button. If saved, the report will stay in the Originator's workqueue until it is signed.

B-12847 - QIR - Improvement Suggestion

Overview

This Best Practice describes how to fill out a QIR for the Improvement Suggestion category in SoluDyne. Improvement suggestions allow employees to contribute an improvement suggestion about anything in their work environment.


Prerequisites

N/A

Description

  

  1. Select the Quality Improvement Report button on the SoluDyne toolbar and click OK to create a new QIS Report. 

     

  1. Write a suitable title in the Title field.
  2. Select the relevant Report Type Group.
  3. Select the relevant Report Type. In this case, Improvement Suggestion.

    

  1. Improvement Suggestion is chosen as Report Type. The report fields will vary depending on the chosen Report Type.
  2. Write a description.
  3. Add file, if relevant.
  4. Sign the QIR Report in the Signature field.
  5. Click on Send Report. 

Reports can also be saved by using the Save Draft button, or cancelled using the Cancel Report button. If saved, the report will stay in the Originator's workqueue until it is signed.

B-12848 - QIR - Operations Support

Overview

This Best Practice describes how to fill out a QIR for the Reporty Type Operations Support in SoluDyne. The Operations Support QIR is used to report deviations in systems or equipment affecting operations.

Prerequisites

N/A

Description

  

  1. Select the Quality Improvement Report button on the SoluDyne toolbar and click OK to create a new QIS Report.

  

  1. Write a suitable title in the Title field.
  2. Select the relevant Report Type Group.
  3. Select the relevant Report Type. In this case, Operation Support.

  

  1. Operation Support is chosen as Report Type. The report fields will vary depending on the chosen Report Type.
  2. Fill in the form. Fields marked with a blue bullet are mandatory to fill out.
  3. Add file, if relevant.
  4. Sign the QIR Report in the Signature field.
  5. Click on Send Report. 

Reports can also be saved by using the Save Draft button, or cancelled using the Cancel Report button. If saved, the report will stay in the Originator's workqueue until it is signed.

B-12849 - QIR - Process Non-Conformance

Overview

This Best Practice describes how to fill out a QIR for the Report Type Non-Conformance in SoluDyne. The Report Type for Process Non-Conformance is used for specifying non-conformances or deviations in a particular process. 

If the user is standing on a process node at the time of making the report, and they select process non-conformance as the Report Type, the information field for what the deviation applies to will be updated automatically with that process.

Prerequisites

N/A

Description

 

  1. Select the Quality Improvement Report button on the SoluDyne toolbar and click OK to create a new QIS Report.

  

  1. Write a suitable title in the Title field.
  2. Select the relevant Report Type Group.
  3. Select the relevant Report Type. In this case, Process Non-Conformance.

  

  1. Process Non-Conformance is chosen as Report Type. The report fields will vary depending on the chosen Report Type.
  2. Write a description.
  3. Add file, if relevant.
  4. Sign the QIR Report in the Signature field.
  5. Click on Send Report. 

Reports can also be saved by using the Save Draft button, or cancelled using the Cancel Report button. If saved, the report will stay in the Originator's workqueue until it is signed.

B-12898 - Quality Improvement Report Types

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the standard Quality Improvement Report - QIR - Types used in SoluDyne.

01 Description
There can be many different Quality Improvement Report types in the system. These can be tailored to suit the Company needs.

Different QIR types are used to easily route the QIRs to the right casehandler based upon the report type. Different report types also allow the report form to be tailored and contain only valid information on the specific report type.

02 Example
Examples of standard QIR report types are:

  1. HSE Occurences
  2. Fault Reporting
  3. Operations Support 
  4. Process Non-Conformance  
  5. Improvement Suggestion
  6. Audit 

03 - Case Handling

B-16391 - Example - Quality Improvement Report - Originator

Overview
This Best Practice describes how to create and fill in a QIR Report. All employees can create a QIR Report.

Prerequisites
The Quality Improvement Process is triggered when the originator signs a Quality Improvement Report.

Description

   

  1. Select the Quality Improvement Report button on the SoluDyne toolbar and click OK to create a new QIS Report.

    

  1. Write a suitable title in the Title field.
  2. Select the relevant Report Type Group.
  3. Select the relevant Report Type. In this case, HSE Occurences is used as an example.

     

  1. Here, HSE Occurences is chosen as the Report Type. The form below will vary depending on the chosen Report Type.
  2. Fill in the form that appears with relevant information. Describe the incident as detailed as possible in the Description field.
    • Fields marked with a blue bullet is mandatory to fill in.

    

  1. Fill in the Improvement Suggestions / Recommendations field, if relevant.
  2. Add file, if relevant.
  3. Sign the QIR Report in the Signature field.
  4. Click on Send Report.

Reports can also be saved by using the Save Draft button, or cancelled using the Cancel Report button. If saved, the report will stay in the Originator's workqueue until it is signed.

 

  1.  A receipt will appear on the screen after the report has been signed. The 01e Receipt: Action Taken will also be visible in the Originator's Workqueue.
  2. Click on Close Receipt to sign the receipt out of the workqueue. 

B-16393 - Example - QIP Classification Step

00 Overview
01 Description
02 Example

00 Overview
The purpose of the classification step is to determine whether or not further action is required.

01 Description
Classification Step

  1. The user linked to the classification role will receive the QIR in their workqueue.
  2. After reading the content added by the originator, the classifier will add a classification comment, and select whether for action is required or not.
  3. To send the report further, the classifier adds their signature and saves.

If no further action is required, the case is closed and the originator will receive a completion receipt.

 
Figure 1: The QIR appears in the workqueue of the classifier on the classification step.

 
Figure 2: The classifier fills in a classification comment. 

  
Figure 3: The classifier indicates whether further action is required and signs the report further.

B-16394 - Example - QIP Allocate Resources and Set Due Date Step

00 Overview
01 Description
02 Example

00 Overview
The purpose of the Allocate Resources and Set Due Date step is to assign an analyst to the case, and determine a deadline.

01 Description
Allocate Resources and Set Due Date Step

  1. The user linked to the Responsible - Analysis role will receive the Quality Improvement Report in their workqueue.
  2. After reading the content added by the originator, the analyst will determine a deadline for the investigation, and allocate personnel resources for further investigation and implementation.
  3. To send the report further, the analyst adds their signature and saves.

 
Figure 1: The Quality Imporvement Report will arrive in the workqueue of the user linked to the analyst role.

 
Figure 2: The analyst fills in the required fields for the allocation step:

  1. Select the Analysis Due Date
  2. Select an Investigator
  3. Select an Implementor
  4. The user signs the report to send it to the next step.

B-16396 - Example - QIP Analysis Step

00 Overview
01 Description
02 Example

00 Overview
The purpose of the Perform Analysis step is to investigate the case.  

01 Description
QIP Analysis Step

  1. The QIR will arrive in the workqueue of the user assigned to perform the analysis in the previous step.
  2. The analyst will add information in the Analyse / Investigate field.
  3. The output of the analysis is to determine whether a change in governing documentation is required, and whether or not there is a need for implementation.
  4. If implementation is required, the analyst will allocate an implementor.
  5. To send the report to the next step, the user will sign the QIR.

 
Figure 1: The analyst reviews the case information documented by the originator.

  1. The anayst scrolls down to add the results of their analysis to the activity.

 
Figure 4: The Analyst provides information in the Analyse / Investigate field.

  1. Analysis comment - free text field.
  2. Links to Risk Analysis.
  3. Link to Risks.
  4. Drop down menu for adding Root Causes.

 
Figure 3: The analyst add the output information of their analysis by specifying:

  1. Whether a change to Governing Documentation is required or not.
  2. Whether or not implementation is required.
  3. If implementation is required, the analyst will allocate an implementor.
  4. The activity is signed to be sent to the next step.

B-16397 - Example - QIP Corrective and Preventive Actions Step

00 Overview
01 Description
02 Example

00 Overview
The Preventive and Corrective Actions Step is part of the overall systematic process for the purpose of identifying, correcting, and preventing quality issues.

01 Description
Preventive and Corrective Actions Step

In this step, the implementor will create a plan to address (correct and prevent) the observations logged by the originator from happening again.

  1. Activities for addressing the particular items can be made directly in the Quaity Improvement Report.
  2. When the plan established, the Implementor signs it to the next step.

 
Figure 1: The QIR will arrive in the workqueue of the user who is linked to the Implementation role.

 
Figure 2: The Implementor adds preventive and corrective actions by clicking on the links in the Corrective and Preventive Actions Field.

  
Figure 3: An activity is linked directly to the QIR for handling preventive actions.

  1. The activity node can be entered by clicking the activity number.

B-16399 - Example - QIP Implement CAPA Plan Step

00 Overview
01 Description
02 Example

00 Overview
The purpose of this step is to document implementation of the CAPA plan.

01 Description
Implement CAPA Plan Step

  1. The QIR will be sent to the workque of the implementor.
  2. The implementor fills in an implementation comment and confirms implementation by checking the implemenation box.
  3. The implementor signs the QIR to the next step.

 
Figure 1: The QIR arrives in the workqueue of the implementor.

 
Figure 2: The Implementor fills out the Implementation comment and checks the box to confirm implementation.

B-16400 - Example - QIP Verification Step

00 Overview
01 Description
02 Example

00 Overview
The purpose of this step is to verify that the actions have been implemented and taken effect.

01 Description
Verification Step

  1. The QIR will arrive in the workqueue of the person or job function linked to the verifier role or set to the verification step.
  2. The verifier adds a verification comment, and checks the verification box.
  3. To close the QIR, the verifier signs the report.

 
Figure 1: The QIR in the workqueue of the verifier.

 
Figure 2: The verification comment field to be filled out by the user.

B-16401 - Example - Completion Receipt

00 Overview
01 Description
02 Example

00 Overview
This Best Practice descripes the feedback to the originator on a QIR.

01 Description
When the Quality Improvement Report has been sent through all relevant steps, the originating user receives a completion receipt.

  
Figure 1: Completion Receipt.

B-16402 - Example - QIP Change Governing Documentation Step

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes how to use the QIR and changing the governing documentation.

01 Description
The purpose of the Change Governing Documentation Step is to trigger a comment change process to address the required changed.

Change Governing Documentation Step

 
Figure 1: The Perform Change QIR will appear in the workqueue of the implementor.

 
Figure 2: A comment/change can be added directly in the QIR.

  1. Add Comment/Change. Fill out required information.
  2. Save.


Figure 3: The comment change can be entered directly from the QIR for adding additional information.

  
Figure 4: Reviewers can be added to the Change Package through the add links function under Name.

 
Figure 5: To send the Comment/Change and QIR further, the implementor signs in the signature field.

04 - Reports and Statistics

B-12852 - Report: Weekly Overview QIS

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the weekly overview of QIS reports in SoluDyne.

01 Description

The weekly overview QIS report drilldown gives an overview of all reports submitted during the current week. It is possible to select other weeks / months using the filter function.

These can be filtered by:

  • Report Type Group
  • Year
  • Month
  • Week
  • Case Number
  • Title
  • Report Type
  • Organization
  • Organizational Unit
  • Performer

02 Example

 

Navigate to the QIS Report overview under CAR in the main menu.

  1. Select Report: Weekly Overview QIS
  2. Select Show Filter.

  

  1. The item at the top of the list is the default filter item.

 

  1. To change the default filter option, drag any filter item to the top of the list. The filter result will update to include QIR's filtered by the top category. In this example, all performers who have submitted QIR's in the current week will appear in the list.

 

  1. Select the required filter result.
  2. The report will appear in the main window to the left.

 

Example of a Drilldown by Performer.

  

Example of a Drilldown by Deviation Category.

B-12853 - Report: All QIR's - Details

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the drilldown report for all QIR's with a detailed filter functionality in SoluDyne.

01 Description

The detailed report for all QIR's provides a filter function and report drilldown with a high level of detail.

02 Example

 

Navigate to the QIS Report overview under CAR in the main menu.

  1. Select Report: All QIR's - Details.
  2. Select Show Filter.  

 

  1. The Report: All QIR's - Details contains a large filter with multiple options for filtering results.

 

Example of a detailed report drilldown.

B-12854 - Report: All QIR's

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the All QIR's report function in SoluDyne.

01 Description

The All QIR's report provides a drilldown of all QIR's in the system with more general detail and a smaller filter result.

For additional filter options and more more detail, see B-12853 - Report - All QIR's - Details.

02 Example

 

Navigate to the QIS Report overview under CAR in the main menu.

  1. Select Report: All QIRs.
  2. Select Show Filter.

 

  1. Use the drag and drop function to order the filter results. 
  2. Select the filtered result. 

  

Example of a drilldown report for all QIR's.

B-12855 - Report: Status QIR's

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the status QIR functionality in SoluDyne.

01 Description

QIS reports can be viewed in a report with information structured according to the status of the QIR. Status refers to which step the QIR is currently on. For example, classification, analysis, implementation etc.

02 Example

 

Navigate to the QIS Report overview under CAR in the main menu.

  1. Select Report: Status QIR's.
  2. Select Show Filter if required.

 

  1. Use the drag and drop function to order the filter results. 
  2. Select the filtered result. 

 

Example of the status ordered QIS report drilldown.

NOTE: In this example, the week was selected as a filter result. Therefore all QIR's, on all different steps logged in week 43 are visible in the report. There was only one in the example above.

B-12856 - Report: Overdue QIR's

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the overdue QIS reports functionality in SoluDyne.

01 Description

The overdue report drilldown shows all QIR's that have not been handled in accordance with the set deadlines.

02 Example

  

Navigate to the QIS Report overview under CAR in the main menu.

  1. Select Report: Overdue QIR's.
  2. When "No Hits" appears, this indicates there are no overdue QIR's in the system.

B-12857 - QIS Statistics

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the QIS statistics functionality in SoluDyne.

01 Description

Statistics on the Quality Improvement System can viewed from different data perspectives.

It is possible to view statistics on QIS according to:

  • Non-conformance Cost pr Month
  • Reports pr Deviation Category
  • Reports pr Deviation Category (Cake)
  • Reports pr Month
  • Reports pr Month
  • Reports pr Org. Unit
  • Reports pr Org. Unit - Top 10
  • Reports pr Org. Unit 2
  • Reports pr Product
  • Reports pr Root Cause
  • Reports pr Supplier
  • Top 10 Cost based on Cost report
  • Top 10 Cost based on Hrs

02 Example

 

Navigate to the statistics register.

  1. Expand SoluDyne QIS.

 

  1. Select the desired data option.

NOTE: The statistics will appear on the right hand side in the main field.

 

Example of the Reports pr Deviation Category view.

 

Example of the Reports pr Deviation Category Cake view.

B-16405 - Navigating to QIS Reports

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes where to find QIS Reports in SoluDyne.

01 Descripton
QIS Report Drilldowns are found under CAR in the SoluDyne main menu.

   

  1. Open the expanding menu.
  2. Select CAR.

 

B-16410 - Navigating to Statistics

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes where to find statistics for SoluDyne QIS.

01 Description
An overview of various statistics in SoluDyne can be found under SoluDyne Designer in the main menu - Statistics Register.

  

  1. Open the SoluDyne expanding menu.
  2. Select SoluDyne Designer.

 

  1. Select Statistics Register.
  2. Expand Statistics Register in the sub-menu.

Example of a list of options for statistics reports.

05 - QIS System Administration

Administration

B-16314 - QIS Home Page Icons

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes the available standard QIS Home Page Icons.

01 Description
Available icons/images that can be used on custom QIS Home Page tab:

 

Icons/images is located in SoluDyne web folder under \Images\HomePage\QIS\

Audit

B-12843 - Creating a Plan Register

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to create a plan register in SoluDyne.

01 Description

Plan registers are used to group different categories of plans.

02 Example

Quality Improvement Reports

B-11791 - Customizing QIS Links on Homepage

The following steps should be performed to override links of QIS tab on HomePage:.

  1. Log in to the system and open SoluDyne Designer section of left Expanding Menu;

     
  2. Create Subform under Config Class Holder in SoluDyne Designer and open Subform Form Editor tab;

     
  3. Turn editor mode to HTML using HTML button on the Floating Toolbar;
  4. Copy the following HTML and put it into Subform HTML on Subform Form Editor;

    <TABLE style="WIDTH: 100%" border=0><TR vAlign=top>
    <TD style="WIDTH: 1%"><A id=newQir-1-1 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=700058517&amp;FieldID1=77800303&amp;Value1=700058377" target=right><IMG src="Images/HomePage/QIS/Health.png"></A>&nbsp;<BR></TD>
    <TD>
    <P><FONT style="FONT-FAMILY: Arial; FONT-SIZE: 16px"><STRONG><A id=newQir-1-2 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=700058517&amp;FieldID1=77800303&amp;Value1=700058377" target=right>Health</A></STRONG> - <FONT style="FONT-FAMILY: Arial; FONT-SIZE: 11px">Report Health related HSE occurrences or situations by clicking on the Health icon to the left.</FONT></FONT></P></TD>
    <TD><A id=newQir-2-1 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=700058450&amp;FieldID1=77800303&amp;Value1=700058377" target=right><IMG src="Images/HomePage/QIS/Environment.png"></A>&nbsp;</TD>
    <TD>
    <P><FONT style="FONT-FAMILY: Arial; FONT-SIZE: 16px"><STRONG><A id=newQir-2-2 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=700058450&amp;FieldID1=77800303&amp;Value1=700058377" target=right>Environment</A></STRONG>&nbsp;- <FONT style="FONT-FAMILY: Arial; FONT-SIZE: 11px">Report Environment related occurrences or situations by clicking on the Environment Icons to the left.</FONT></FONT></P></TD></TR>
    <TR vAlign=top>
    <TD style="WIDTH: 1%">&nbsp;</TD>
    <TD>&nbsp;</TD>
    <TD>&nbsp;</TD>
    <TD>&nbsp;</TD></TR>
    <TR vAlign=top>
    <TD style="WIDTH: 1%"><A id=newQir-3-1 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=702113006&amp;FieldID1=77800303&amp;Value1=" target=right><IMG src="Images/HomePage/QIS/Safety.png"></A>&nbsp;<BR></TD>
    <TD>
    <P><FONT style="FONT-FAMILY: Arial; FONT-SIZE: 16px"><STRONG><A id=newQir-3-2 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=702113006&amp;FieldID1=77800303&amp;Value1=" target=right>Safety</A></STRONG>&nbsp;- <FONT style="FONT-FAMILY: Arial; FONT-SIZE: 11px">Report Safety related HSE occurrences or situations by clicking on the Safety icon to the left.</FONT></FONT></P>&nbsp;</TD>
    <TD><A id=newQir-4-1 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=702398617&amp;FieldID1=77800303&amp;Value1=" target=right><IMG src="Images/HomePage/QIS/Audit%20findings.png"></A>&nbsp;</TD>
    <TD>
    <P><FONT style="FONT-FAMILY: Arial; FONT-SIZE: 16px"><STRONG><A id=newQir-4-2 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=702398617&amp;FieldID1=77800303&amp;Value1=" target=right>Audit findings</A></STRONG>&nbsp;- <FONT style="FONT-FAMILY: Arial; FONT-SIZE: 11px">Report Audit findings by clicking on the Audit finding icon to the left.</FONT></FONT></P></TD></TR>
    <TR vAlign=top>
    <TD style="WIDTH: 1%">&nbsp;</TD>
    <TD>&nbsp;</TD>
    <TD>&nbsp;</TD>
    <TD>&nbsp;</TD></TR>
    <TR vAlign=top>
    <TD style="WIDTH: 1%"><A id=newQir-5-1 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=704882417&amp;FieldID1=77800303&amp;Value1=704882416" target=right><IMG src="Images/HomePage/QIS/Improvement%20suggestions.png"></A>&nbsp;</TD>
    <TD>
    <P><FONT style="FONT-FAMILY: Arial; FONT-SIZE: 16px"><FONT style="FONT-FAMILY: Arial; FONT-SIZE: 16px"><STRONG><A id=newQir-5-2 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=704882417&amp;FieldID1=77800303&amp;Value1=704882416" target=right>Improvement Suggestion</A></STRONG>&nbsp;- <FONT style="FONT-FAMILY: Arial; FONT-SIZE: 11px">Report Improvement suggestions by clicking on the Improvement suggestion icon to the left.</FONT></FONT></P></FONT></TD>
    <TD><A id=newQir-6-1 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=701851488&amp;FieldID1=77800303&amp;Value1=" target=right><IMG src="Images/HomePage/QIS/Non-Conformances.png"></A>&nbsp;</TD>
    <TD>
    <P><FONT style="FONT-FAMILY: Arial; FONT-SIZE: 16px"><STRONG><A id=newQir-6-2 class=INTHYPERLINK href="Newnode.aspx?C=7780&amp;TreeID=0&amp;P=2982956&amp;G=0&amp;FieldID=77808592&amp;Value=701851488&amp;FieldID1=77800303&amp;Value1=" target=right>Non-Conformances</A></STRONG>&nbsp;- <FONT style="FONT-FAMILY: Arial; FONT-SIZE: 11px">Report Non-conformances by clicking on the Non-conformance icon to the left.</FONT></FONT></P></TD></TR></TABLE>
    <SCRIPT type=text/javascript>
        var devCatGroupUids = [
            700058377,
            700058377,
            "",
            "",
            704882416,
            ""
        ]

        var devCatUids = [
            700058517,
            700058450,
            702113006,
            702398617,
            704882417,
            701851488
        ]

        function setNewQirHrefs() {
            for (var i = 0; i < devCatGroupUids.length; i++) {
                for (var j = 0; j < 2; j++) {
                    var elem = document.getElementById("newQir-" + (i + 1) + "-" + (j + 1));
                    elem.href = makeNewQirHref(devCatGroupUids[i], devCatUids[i]);
                }
            }
        }
       
        function makeNewQirHref(devCatGroupUid, devCatUid) {
            return 'Newnode.aspx?C=7780&TreeID=0&P=' + SDNodeData.UID + '&G=0&FieldID=77808592&Value=' + devCatUid + '&FieldID1=77800303&Value1=' + devCatGroupUid;
        }

        window.attachEvent("onload", setNewQirHrefs);
    </SCRIPT>

  5. Replace the bold text with real WSUIDs in the HTML code and press Save button on Floating Toolbar;

       
  6. Press Create Subform button on the form;
  7. Press Publish button on the Floating Toolbar;
  8. Perform Update Config to accept changes made for QIS tab on HomePage;
  9. Ensure that QIS tab corrected on HomePage.

B-11793 - Delete QIRs

The following steps should be performed to delete created QIRs as admin:

1. Navigate to CAR - QIS Report Register under SoluDyne Expanding Menu.

 

Figure 1. Navigate to QIS Report Register under CAR.

2. Click on QIS Report Register and navigate to the QIR that shall be deleted in the Tree.
3. When standing in the required QIR, right-click with the mouse to get the actions menu. Click Delete Node.

 

Figure 2. Right-click on requested QIR and chose Delete Node from Actions menu.

B-11795 - Customize QIR email subject

The following describes how to customize the subject of QIR emails:

  1. Create new Template node under SoluDyne Designer - Config Menu;
  2. Set Title to QIPEmailSubject.
  3. Add new subject text into Template Field.
  4. Publis template.
  5. Perform Update an update config.

Text in the template supports various replacements, like those shown in the table below.

# Field name Parameter Description
1 Form Title / Step View Current step of the QIP Report.
2
Title
Title of the QIP Report.
3
Deviation Category Group
Deviation Category Group chosen for the QIP Report.
4
Deviation Category
Deviation Category chosen for the QIP Report.
5
Entry Date
Entry Date of the QIP Report.
6
Entry Time
Entry Time of the QIP Report.
7
Due Date
Due Date of the QIP Report.
8
Occurrence Date
Occurrence Date set for the QIP Report.
9
Occurrence Time
Occurrence Time set for the QIP Report.

  
Figure 1: Default template for Email subject.

B-11827 - Link to a new QIR Report

The link to a new QIR Report to be used on intranet is:

<APPLICATIONURL>
Default.aspx?Content=newnode.aspx%3FP%3D0%26C%3D7780
Where <APPLICATIONURL> - is URL to SoluDyne system, finished with "/" symbol. See figure 1;


Figure 1 - URL to SoluDyne application.

B-11973 - QIS Reporting and Statistics with MS Excel

Navigate to the drilldown Reports: All QIRs Non-Conformances. 

Use the Filter to filter out the data required for the report.
 
Click on the required data grouping item in the drilldown tree.

A gridlist will be shown on the right hand side.

Scroll to the bottom of the gridlist and click on the MS Excel icon. If MS Office Web Components have been installed; the data will open inline in the MS Excel Component.

  
Figure 1. Reports: All QIRs Non-Cons with data open inline in the MS Excel Component.

Click on the MS Excel icon on the toolbar in the MS Excel Component to open the data in MS Excel.

Select Insert Pivot Table.

Drag Row field into the Row Labels, Column field into Column Labels and Value field into Values.

 
Figure 2. Pivot table in MS Excel.

Select Pivot area and select Insert Chart.

 
Figure 3. Chart in MS Excel.

B-12096 - QIS Reports

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes the various reports that can be activated in SoluDyne QIS.

01 Description:
Definition: Quality Improvement Report: QIR, a report that can be an non-conformance or improvement suggestion.

There are many Drilldown reports that can be used in SoluDyne QIS in order for Case Responsible and Users to get status, feedback and create statistics based on QIRs reported in the system.

02 Example

  1. My QIS Reports
    This class is a drill-down class that shows Quality Improvement Reports that the user has created.
    Only open Quality Improvement Reports are shown.

    Filter options; Year, Month, Week, Date From/Date To, Step, Deviation Category, Case Number, Title, Performer.
  2. Report: Weekly Overview QIS
    This class is a Drill-Down class that shows QIR Reports per week.

    Filter options; Deviation Category Group, Year, Month, Week, Case Number, Title, Deviation Category, Organization, Org. Unit, Performer. Also completed QIR Reports is shown.
  3. Report: All QIRs
    This class is a Drill-Down class that shows all QIS Reports.

    Filter options; Deviation Category Group, Year, Week, Case Number, Title, Deviation Category, Organization, Org.Unit, Process, Safety Related - Orig.

  4. Report: All QIRs - Details
    This class is a Drill-Down class that shows all Non-Conforance QIS Reports.

    Filter options; Organization, Year, Month, Week, Deviation Category Group, Deviation Category, Customer, Supplier, Location, Org.Unit, Title, Reported By, Orccurence Date From/Occurence Date To, Site, Project No, Product, Medical Assistance Required?, Total Cost, Root Cause, Implemented, Verified.

  5. Report: All QIRs - Originator
    This class is a Drill-Down class that shows all Quality Improvement Reports and the name of the originator, ie who has registered the report.

    Filter options; Deviation Category Group, Year, Week, Case Number, Title, Deviation Category, Organization, Org.Unit, Process, Originator.

  6. Report: Status QIRs
    This class is a Drill-Down class that shows on what step a Quality Improvement Report is on.

    Filter options; Deviation Category Group, Deviation Category, Year, Quarter, Week, Case Number, Title, Organization, Org.Unit, Step, Performer.

  7. Report: QIR Overview
    This class is a Drill-Down class that shows performer on registered Quality Improvent Reports.

    Filter options; Deviation Category Group, Deviation Category, Year, Quarter, Week, Case Number, Title, Organization, Org.Unit, Step, Performer.

  8. Report: Overdue QIRs
    This class is a Drill-Diown that shows all Quality Improvement Reprots that has passed the due date for processing the report.

    Filter options; Deviation Category Group, Deviation Category, Case Number, Title, Organization, Org.Unit, Step, Due Date From/Due Date To, Performer.

  9. Report : Open Quality Improvement
    This class is a Drill-Down class that shows open Quality Improvement Reports, ie where there exists active steps that are not Receipts . The Drill-Down shows Quality Improvement Reports for the users Organization based on the Organization field on the QIR form. This class is part of the Net Account Functionality.

    Filter options; Requires Immediate Supervision, Step, Deviation Category, Case Number, Title, Date From/Date To.

  10. Report : Closed Quality Improvement
    This class is a Drill-Down class that shows closed Quality Improvement Reports. The Drill-Down shows Quality Improvement Reports for the users Organization based on the Organization field on the QIR form. This class is part of the Net Account Functionality.

    Filter options; Year, Month, Week, Date From/Date To, Deviation Category, Case Number, Title.

  11. Report : Activity Overview
    This class is a Drill-Down class that shows Activities where the users Organization is the Customer under which the Activity has been created. This class is part of the Net Account functionality.

    Filter options; Order, Plan, Step, Activity ID, Activity No, Activity Title, Priority, Progress, Start From/Start To, End From/End To
    WI.

B-12129 - QIS Statistics

  1. Non-conformance Cost pr Month
    Shows the cost of non-conformances per month.
  2. Reports pr Deviation Category
    Shows the total number of reports that has been sent per deviation category.
  3. Reports pr Deviation Category (Cake)
    Shows the total number of reports that has been sent per deviation category as Cake diagram.
  4. Reports pr Month
    Shows the total number of reports per month.
  5. Reports pr Org. Unit
    Shows the total number of reports grouped by the Org Unit report applies to, with totals above the bars.
  6. Reports pr Org. Unit 2
    Shows the total number of reports grouped by the Org Unit report applies to, without totals above bars.
  7. Reports pr Product
    Shows the total number of reports grouped by the product they apply to.
  8. Reports pr Root Cause
    Shows the total number of reports grouped by their Root Cause.
  9. Reports pr Supplier
    Shows the total number of reports grouped by the Supplier the apply to.
  10. Top 10 Cost based on Cost Report
    Shows the top 10 reports based on the cost.
  11. Top 10 Cost based on Hrs
    Shows the top 10 reports based on hours spent.

B-12137 - Linking to QIP Workflow Roles

01 Introduction

The Quality Improvement Process will send reports to the users defined in the Deviation Category, but there are cases when the system is not able to find users matching the distribution set in the Deviation Category. For example if a user who has no Job Function sends a report and the distribution is set to manager, the system is unable to find any users that match the distribution.

In all these cases the system will instead send the report to the Workflow Role as defined by the flowchart behind the workflow. Users linked to a Workflow Role will get any report sent to that Workflow Role in their WorkQueue.

02 Linking To Workflow Role

  1. Login to SoluDyne as a user with administrator permisisons.
  2. Open Expanding Menu and click on System and select SoluDyne WorkFlow Register. See figure 1.
     
    Figure 1 - Click on SouDyne WorkFlow Register
  3. Click to expand the root node and then expand 102 - QIP - Quality Improvement Process - 7780. See figure 2.
  4. Right click on any of the Workflow Roles and select Add Link. See figure 2.

    Figure 2 - Right-click on Workflow Role and select Add Link.
  5. Clicking on Add Link will open the Link Dialog window as seen in figure 3.

    Figure 3 - Link Dialog window (Full version)
  6. Add and/or remove links to Employees as appropriate.

Clicking on a Workflow Role will open the Workflow Role and shows what users are linked to the role. See figure 4.

 
Figure 4 - Workflow Role showing the Employees linked to it.

B-12180 - Set up Deviation Category Group

01 Valid for Organization

Valid for Organization Form of Deviation Category Group is used to filter what Deviation Category Groups are applicable to what Organizations. When new QIR Report is created appropriate Deviation Category Group will appear in the list of available Deviation Category Groups only if Report Originator Organization is selected on Valid for Organization Form of this Deviation Category Group or if no any Organizations selected at all. Therefore Organization to be selected on all Deviation Category Groups (using Valid for Organization Form) this Organization plans to use (or there should not be any Organizations selected on the Categories desired for all Organizations).

02 Default Values

Competence Group Default Values are managed on the separate Form of Deviation Category Group and applicable to all Deviation Categories under this Group. Following Default Values may be specified on this Form:

  • Organization
  • Org. Unit
  • Customer
  • Supplier
  • Applies To

When New QIR Report is created and Deviation Category is specified for it, Default Values are taken from appropriate Deviation Category Group if appropriate Values are shown on Form for this Deviation Category and not settled by User explicitly. If User specified some original Value on QIR Report Form, appropriate Default Value from Deviation Category Group is just ignored.

03 Case Responsible List

Case Responsible List Form of Deviation Category is quite similar to Valid for Organization Form on Deviation Category Group. The only difference is it allows filtering Organization Units, not Organizations. Particular Deviation Category will be available in new QIS Report only if Originator Organization Unit is selected on Case Responsible List Form or if there are no any Organization Units selected on this Form at all.

04 Parent

Define parent for new reports by specifying Parent by defining a QIS Report Register and QIS Report Group. 

B-12183 - Deleting QIRs as Admin user

00 Overview
01 Description

02 Sample Session

00 Overview

This Best Practice describes how to delete QIRs logged in as the user "Admin" in SoluDyne. The user "Admin" has all workflow items in the workqueue as default.

01 Description
Admin user is a 'special' user which has access to all workflow items for all users in SoluDyne e.g QIR or Comment/Change.
 
02 Sample Session
  1. Log in as Admin from the SoluDyne Expanding Menu.
  2. Check that you are logged in as admin and that the workqueue is populated with QIRs.
  3. Navigate to Expanding Menu - CAR - Report: Status QIRs.
  4. Filter results as needed and click results to get the report.
  5. Open or rightclick to open the chosen QIRs and press Delete button on SoluDyne toolbar.

 

Figure 1. Step 1.

 

Figure 2. Step 2.

 

Figure 3. Step 5.

B-12465 - Customizing QIS Report form

00 Overview

This Best Practice describes which fields in a QIS Form that SoluDyne can customize depending on the customer's request.


01 Description

A QIS Form consists of three sections: the header, the sub form and the footer.  The header and footer is standard.  Figure 01 illustrates this division and highlights which fields that can be customized.

The field Deviation Category will decide the layout of the sub form of the QIS Form. The different categories can be seen in Figure 02.

Mandatory fields are marked with a bullet  in front of the text field. It is possible to change which fields that should be mandatory to fill out or not. This can be performed in Userconfig, see Figure 03. 

The customer can also decide if the signature field shall be shown or not.

Figure 04 shows the form used as a sample of the standard QIS Form.

Figure 05 illustrates how to predefine default values.

The next step of the QIS is described in the following Best Practice: B-12466 - Customizing QIS Classification form 

02 Example

 
Figure 01: QIS Form with the three main sections

   
Figure 02: The different Deviation Categories

 
Figure 03: Illustration from Userconfig

  
Figure 04: Standard QIS Form

  
Figure 05: Illustration of Default Values

B-12466 - Customizing QIS Classification form

00 Overview

This Best Practice describes how the QIS Classification Form looks and how SoluDyne can customize the form according to the costumer's request.

01 Description

The QIS Classification form consists of two sub forms: Classification and Case Handling. See Figure 01.

When entering into the step 03-Classification of the QIS, the first sub form has already been filled out in the previous step. See B-12465 - Customizing QIS Report form for more information about the 01-Reporting step. In the 03-Classification step, it is possible to change what has been filled out in the Reporting step.

The field Deviation Category in first sub form will decide the layout of the Case Handling Form. Example of categories can be seen in Figure 02.

Mandatory fields are marked with a bullet  in front of the text field. It is possible to change which fields that should be mandatory to fill out or not. This can be performed in Userconfig, see Figure 03.

The customer can also decide if the signature field shall be shown or not.

02 Example

    
Figure 01: Overview of the two sub forms in the Classification form.

 
Figure 02: Example of Deviation Categories

 
Figure 03: Illustration from Userconfig

Report Type Register

B-12831 - Creating a New Report Type Group

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to create a new Report Type Group in SoluDyne.

01 Description

The SoluDyne system is delivered with a standard Report Type Register containing predefined groups and categories. For more information, see L-16373 - The Deviation Category Register 

In many cases, Organizations require a tailored approach to the set-up of their Quality Improvement System module in SoluDyne. This can be achieved through adding or removing groups and categories in the Register.

02 Example

 

  1. Navigate to the Deviation Category Register. It is found under CAR in the main menu.

 

  1. Right click the Deviation Category Register.
  2. Select New Node.
  3. Select Deviation Category Group.

 

  1. Fill in the title;
  2. Fill in the location if required;
  3. Add an Owner and Responsible. 
  4. Save. 

 

  1. Select the tab "Valid for Organization".
  2. Use the multiple choice to menu to select organisations or departments that the category group will be active for.
  3. Check the "Active" box to activate the Category Group.
  4. Scroll down the page if required.

 

  1. Select which companies or departments the group will be a default QIR for if required.
  2. Save.

  

  1. Select the "Default Values" tab.
  2. Add the default values by using the drop down menus.
  3. Publish.

NOTE: These are the items that will automatically appear on the QIR form when generated by the user.

B-12832 - Creating a New Report Type

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to create a new Report Type in SoluDyne.

01 Description

Report Types are placed under Report Type Groups. For more information on setting up a Report Type Group, see B-12831 - Creating a New Deviation Category Group

02 Example

 

  1. Navigate to the Deviation Category Register.
  2. Right click on the relevant Deviation Category Group. 
  3. Select New Node.
  4. Select Deviation Category. 

  

  1. Fill in title.
  2. The owner and responsible are inherited from the parent node (Deviation Category Group) but can be changed if required.
  3. Add a description if required.

 

  1. Check the required boxes for fields which should display on the report.

  

  1. Set the Type for the different roles in the process. In this example, Job Function.

 

  1. Set the Responsible Role through navigating in look-up menu.

NOTE: In this case, the Organisation chart is default because the type was set to Job Function. If the type is set to Employee for example, the Personnel Register becomes default.

 

  1. If notifications by e-mail are required, check the e-mail notification box.
  2. Select "Add Deviation Category E-Mail". This will open an item where the step and recipient can be specified. When the QIR is signed to the relevant step, the specified recipient will be notified by e-mail.

  

  1. To set an alarm limit, check the box for "Alarm Limit Flag".  The number of occurances and days can be set by typing the numbers in the fields below.

NOTE: If enabled, this means that the QIS report will not be sent on unless the alarm criteria is satisfied.

   

  1. Select the Case Responsible List tab.
  2. Expand the organisation chart.
  3. Select those employees involved in the case handling for the Deviation Category.
  4. Publish when completed.

B-12833 - Deleting a Report Type

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to delete a Report Type in SoluDyne.

01 Description

As the System is delivered with pre-existing Report Types, some might not be required by a specific organisation. In this case, it is possible to delete the category for ease of use.

To restore a deleted node, refer to B-12108 - Restore Deleted Nodes from Recycle Bin.

02 Example

 

  1. Navigate to the relevant Deviation Category and select it.
  2. Select the Delete button on the editor toolbar.

 

  1. Select OK on the pop-up.

B-16373 - The Report Type Register

00 Overview
01 Description
02 Example

00 Overview
This Best Practice describes the Report Type Register in SoluDyne QIS.

01 Description
A standard Report Type Register comes as part of the SoluDyne system. It is located in the main menu under QIS.

It contains categories for:

  • Audit
  • Dispensation
  • Fault Recording
  • HSE Occurances
  • Improvement of Work Processes
  • Improvement Suggestions
  • Operations Support
  • Other Occurances
  • Process Non-Conformance

 

Figure 1: Deviation Category Register showing the standard categories.

Repott Type Default values

B-12316 - Report Type Group - Default Values

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the Default Values tab functionality on Report Type Group in SoluDyne.

01 Description

On the Report Type Group, one can set different values in the Default Values tab:

Organization
Org. Unit
Customer
Supplier
Applies To

The Default Values are shown when creating a new QIR so that the originator doesn't need to fill in this information.

02 Example

    

Figure 1. Setting Default Values under Report Type Group.

B-12326 - Report Type Group - Valid for Organization

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes the Valid for Organization on Report Type Group functionality in SoluDyne.

01 Description

On the Report Type Group, one can set different values in the Valid for Organization tab:

1. Valid for Organization
Selecting specific organization/organization units that the Report Type Group shall be active for.

NOTE: One has to manually set values for newly created organizationunits under an active organization.

2. Default for Organization
Selecting specific organization/organization units that loads the chosen Report Type Group as default when creating a new QIR.

02 Example

   

Figure 1. Setting values for Valid for Organization and Default for Organization under Report Type Group.

Risk Register

B-12837 - Establishing a Risk Register

00 Overview
01 Description

02 Example
02.01 - Creating a New Risk Register
02.02 - Linking a Risk Matrix


00 Overview

This Best Practice describes how to establish a Risk Register in SoluDyne.

01 Description

When a new Risk Register is established, it needs to be linked to a Risk Matrix. The Risk Matrix is where the registers can be customised (Title, Owner, Case Handler, Colour etc.). For more information on setting up a Risk Matrix see B-12272 - Risk Matrix.

User permissions for the Risk Register can be adjusted. For more information on setting user permissions, see B-12458 - Administrate user access to ROS analyses.

02 Example

02.01 - Creating a New Risk Register

 

  1. Select the "New" button on the SoluDyne toolbar.
  2. Select "New Register".
  3. Scroll down and select "Risk Register".

 

  1. Fill-in the title.
  2. Add the Owner and Responsible.
  3. Add a description if required.

02.02 - Linking a Risk Matrix

 

  1.  To add the Risk Matrix, select the "Add Links" under the tab "References - Links".

 

  1. Navigate to the applicable Matrix Register in the pop-up.
  2. Select the required Risk Matrix.
  3. The Risk Matrix will appear in the links list field at the bottom of the pop-up. When this is visible, the link is in place.
  4. Close the window when you are finished.

NOTE: Risk Matrices are found under "CAR - Matrix Register".

 

  1. The link is now visible under "References - Links".
  2. Publish the Register.

 

  1. The Risk Register is now visible under "CAR" in the main menu.

B-12838 - Establishing a Risk Group

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to establish a Risk Group in SoluDyne.

01 Description

Risk Groups are established under Risk Registers. It is possible to create groups below groups. 

A Risk Group can be used to divide the following:

  • Main processes
  • Sub processes
  • Product Groups
  • Organization Units 

For more information on setting up the Risk Register, see B-12768 - Best Practice for Establishing a Risk Register.

02 Example

 

  1. Open the SoluDyne Menu.
  2. Open "CAR".
  3. Select the  Risk Register under which the Risk Group will be placed.

  

  1. Right click on the Risk Register.
  2. Select "New Node".
  3. Select "Risk Group."

 

  1. Fill in all the required information.
  2. Save or publish.

NOTE: Owner and Responsible are automatically inherited from the parent node, but can be changed as required.

B-12839 - Establishing a Risk Analysis

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to establish a Risk Analysis in SoluDyne.

01 Description

Risk Analyses are established under Risk Group(s). For more information on establishing a Risk Group, see B-12769 - Best Practice for Establishing a Risk Group.

On the Trend tab it is possible to monitor change in risk over time.

02 Example

 

Risk Analysis can be added in two ways:

  1. Right Click on the Risk Group, select "New Node", Select "Risk Analysis".
  2. Select "Add Risk Analysis" under the Risk Analysis Tab in the main window view.

 

  1. Fill-in all the required information (The ID is generated automatically, but can be edited if required).
  2. Add as many Risk Analyses as required.
  3. Save or publish.  

 

  1. Example of the Trend view, where it is possible to monitor change in risk over time.

B-12840 - Establishing a Risk

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to establish a Risk in SoluDyne.

01 Description

Risks are added under Risk Analysis. For more information on establishing a Risk Analysis, see B-12770 - Best Practice for Establishing a Risk Analysis.

02 Example

 

Risks can be added in two ways:

  1. Right click on the Risk Analysis and select "New Node" - "Risk".
  2. Select "Add Risk" under the Risks Tab in the main window view.

 

  1. Fill out all required information.

 

  1. The Risk Level will update automatically based on the inputs. (Colours and Levels are customised when setting up the Risk Matrix, see B-12272 - Risk Matrix.)
  2. Save intermittently.

 

  1. Publish the Risk when all information is added.

 

  1. Additional Risks are added in the same way.
  2. When all Risks are added, publish the Risk Analysis.

  

  1. Example of a published Risk.

NOTE: For more information on linking risks to processes, see B-12758 - Best Practice for Linking Risk(s) to Processes.

B-12841 - Linking a Process from a Risk Node

00 Overview
01 Description

02 Example
02.01 - Linking a Flowchart from a Risk Analysis Node
02.02 - Linking a Flowchart from a Risk Node


00 Overview

This Best Practice describes how to link risks to processes in SoluDyne.

01 Description

Linking risk(s) to processes helps the organisation manage the associated risk by:

  • Emphasising the need for the user's attention to the risk elements of the process;
  • Differentiating the training frequency requirements of the processes using risk. In other words, high risk processes require more frequent training.

Linking risk to processes can be done either from the risk or process node. For more information on linking a risk from a flowchart node, see B-12773 - Best Practice for Linking a Risk from a Flowchart.

Both risk analyses and single risks can be linked to a sub process, a flowchart, or an activity within a flowchart.

For more information on establishing risk analyses and risks, see B-12759 - Best Practice for Establishing a Risk Analysis

For more information on establishing a flowchart, see B-12493 - Best Practice for Modeling Flowchart with Roles

02 Example

02.01 - Linking a Flowchart from a Risk Analysis Node

In this case, the entire risk analysis (including all associated risks) will be linked to the process.

 

  1. Navigate to the required Risk Analysis.
  2. Ensure that the Risk Analysis is in edit-mode.

 

  1. In the "Applies To" field, type the process ID or key words for the required process.
  2. Select the process from the list of drop down related search results.  

 

  1. Publish when completed.  

NOTE: Risk Analyses do not appear as traffic lights on processes.

02.02 - Linking a Flowchart from a Risk Node

In this case, the single risk will be linked to the process. This is typically used where only one or two risks in a risk analysis apply to a particular process.

  

  1. Navigate to the required Risk.
  2. Ensure that the Risk is in edit-mode.

 

  1. In the "Applies To" column, type the process ID or key words for the required process.
  2. Select the process from the list of drop down related search results.  

 

  1. Publish when completed.  

 

  1. Navigate to the linked process.
  2. Control that the risk has appeared.

NOTE: Single Risks will automatically appear as a traffic light on the process, with the traffic light colour indicating the risk level.

B-12842 - Linking a Risk from a Flowchart

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to link risks from a flowchart in SoluDyne.

01 Description

Linking risk(s) to processes helps the organisation manage the associated risk by:

  • Emphasising the need for the user's attention to the risk elements of the process;
  • Differentiating the training frequency requirements of the processes using risk. In other words, high risk processes require more frequent training.

Linking risk to processes can be done either from the risk or process node. For more information on linking flowcharts from the risk node, see B-12772 - Best Practice for Linking a Process from a Risk Node 

Both risk analyses and single risks can be linked to a sub process, a flowchart, or an activity within a flowchart.

02 Example

 

  1. Navigate to the required flowchart.
  2. Ensure that the flowchart is in edit-mode.
  3. Turn to page 2 on the flowchart.

 

  1. Select "Add Links" under "References - Add Links".

 

  1. Navigate to the location of the Risk Analysis in the pop-up window.
  2. Select the required Risk Analysis.
  3. The selected Risk Analysis will appear in the links window at the bottom of the pop-up once selected.
  4. Close the pop-up window.

 

  1. The risk will now appear under "References - Add Links".

 

  1. Navigate to page 1 of the flowchart.
  2. Publish the flowchart.

 

  1. Control that the Risk Traffic Light appears on the process and indicates the risk level.

Root Cause Register

B-12835 - Adding a Root Cause Register

00 Overview
01 Description

02 Example

00 Overview

This Best Practice describes how to add a new Root Cause Register in SoluDyne.

01 Description

For more information on the Root Cause Register, see L-16382 - The Root Cause Register.

02 Example

 

  1. Select "New" on the SoluDyne toolbar.
  2. Select "New Register".
  3. Scroll down and select "Root Cause Register.

 

The register will now appear in the main window view.

  1. Give the Register a title.
  2. Publish.

  

  1. Open CAR in the main menu.
  2. The new register will appear in the list.  

07 - Audit

B-12802 - Audit / Revision Functionality and Workflow

00 Overview
01 Description

02 Example

00 Overview
This Best Practice describes the Audit/Revision functionality and workflow in SoluDyne.

01 Description

01.01 Audit Register / Plan Register
An Audit register is created by going to the New button and clicking New Register. Of the available options, choose Plan Register.
Fill in all the applicable fields, save and publish.

01.02 Audit Group / Plan Group
In order to create an Audit Group, open the Audit Register created earlier and go to the New Button. Click on it and select New Child Node and Plan Group (Audit Group). Fill in all the relevant fields, save and publish.

01.03 Plan
To add an Audit Plan to the Audit Group, Open the Audit Group and click on the New Button. Select New Workflow Item and choose Plan from the available alternatives. A Plan is created and located under the Audit Group. Fill in the relevant fields, save and sign the plan to the Implementation step.

01.04 Audit Activity
An Audit Activity is created by opening the Audit Plan created earlier. Click on the Activity Button under the Description Field. An Add Activity button now appears. Click on it and a new activity is created. Fill out all the relevant fields and save.

01.05 Audit Checklist
During the execution of the audit, The Audit Checklist consists of one or several Audit Items that can be added to the Audit Activity. The results are registered in the Audit Items.
To add an Audit Item, click on the Audit Button under the Description Field. This makes the Add Audit Item Button appear. Clicking on the Add Audit Item Button creates an Audit Item in which the audit item can be specified in the description field.

01.06 Audit Workflow
The activities of the Audit/Revision are divided into these possible steps
- Create activity / checklist
- Prepare audit / revision
- Inform the auditee
- Perform the audit / revison
- Evaluate / Control / Approve the result
- Follow up unsolved items
- Verify closing of findings

01.07 Findings
When findings occur, they are reported as QIS reports under the Findings on the Audit Item form.

01.08 Printing Audit Reports
To print Audit Reports, open the Audit Report to be printed. Use the Print Button and click Print This Form.

01.09 Dashboards and statistics
To get statistics on the Audit Plan, go to the Audit Plan and click on Plan Status. A Dashboard opens, showing the phases, an audit activity gant diagram, performance indicators and cost.

02 Example
Audit Register is created from the New Button, see Figure 1.
Fill in the relevant fields of Audit Register and publish, see Figure 2.
Create an Audit Group from the New Button, see Figure 3.
Fill in the relevant fields of Audit Group and publish, see Figure 4.
Create new Audit Plan from the New Button, see Figure 5.
Fill in the relevant fields of the new Audit Plan and sign, see Figure 6.
Create new Audit Activity from the Add Activity Button, see Figure 7.
Open the new Audit Activity on the Audit Plan, see Figure 8.
Fill in the relevant fields of the Audit Activity and save, see Figure 9.
Create a new Audit Item by clicking on Add Audit Item, see Figure 10.
Open the new Audit Item on the Audit Activity, see Figure 11.
Fill in the relevant fields on the Audit Item, see Figure 12.
An Audit Report is opened from a QIS Report Register, see Figure 13.
Click on the Print Button and Print This Form to generate a printed audit report, see Figure 14.
The printed audit report, see Figure 15.
To get statistics on the Audit Plan, click Plan Status, see Figure 16.
A Dashboard opens showing the statistics of the Audit Plan, see Figure 17.

 
Figure 1 - Audit Register created from the New Button.

 
Figure 2 - Fill in the relevant fields of Audit Register and publish.

 
Figure 3 - Create an Audit Group from the New Button.

 
Figure 4 - Fill in the relevant fields of Audit Group and publish.

 
Figure 5 - Create new Audit Plan from the New Button.

 
Figure 6 - Fill in the relevant fields of the new Audit Plan and sign.

 
Figure 7 - Create new Audit Activity from the Add Activity Button.

 
Figure 8 - Open the new Audit Activity on the Audit Plan.

 
Figure 9 - Fill in the relevant fields of the Audit Activity and save.

 
Figure 10 - Create a new Audit Item by clicking on Add Audit Item.

 
Figure 11 - Open the new Audit Item on the Audit Activity.

 
Figure 12 - Fill in the relevant fields on the Audit Item.

 
Figure 13 - An Audit Report is opened from a QIS Report Register.

 
Figure 14 - Click on the Print Button and Print This Form to generate a printed audit report.

 
Figure 15 - The printed audit report.

 
Figure 16 - To get statistics on the Audit Plan, click Plan Status.

 
Figure 17 - A Dashboard opens showing the statistics of the Audit Plan.











Save