Application Area: Quality Management (Fabasoft Approve Quality)

Fabasoft Approve Quality offers you a pioneering solution for the innovative management of issues (see chapter “Issues”). The application enables extremely straightforward, intuitive and collaborative handling of issues and their processing in an 8D-Process (see chapter “8D Process”).

Subsequently, a basic process is presented that enables the efficient handling of issues (see chapter “Issues”) within this process. The system is designed not only to make the management of defects transparent and accessible, but also to promote collaborative exchange and ensure seamless integration into the overall 8D-Process (see chapter “8D Process”).

Quality Management Dashboard

After creating a quality manager configuration (see chapter “Quality Management Configuration“), a dashboard is automatically created for you and placed on the home screen. This quality manager dashboard serves as your central access point to Fabasoft Approve Quality.

Note: It is important to note that depending on your role and the previous settings made before you first accessed Fabasoft Approve Quality, certain objects and settings may vary. There may be differences in terms of user assistance. If there are any uncertainties or specific adjustments, you should contact the relevant administrators for detailed information.

Areas

The Quality Manager dashboard is divided into different areas to provide you with clear access and efficient use of Fabasoft Approve Quality. The following areas are typically available:

Sites (see chapter “Sites”)
Within the application, all Sites released for you are clearly displayed. You have the option of modifying or reading these Sites according to your individual settings and access rights. This interface allows you to customize the Sites according to your needs while ensuring easy navigation and editing.
Issues (see chapter “Issues”)
The Issues tile consists of a list that makes various Issues accessible to you based on the rights granted. You can add additional entries to this list. These actions are described in more detail below.
Actions (see chapter “Actions”)
The Actions tile also consists of a list that makes various actions available to you based on the rights you have been granted.
Search
The “Search” tile - just like the “Actions” tile - consists of a list. Based on the given rights, this list calculates various objects, which can be configured by you. There are various actions that must be carried out to enable this list configuration. These actions are described in more detail below.

Actions

Depending on the rights assigned, you can perform the following actions at dashboard level and the corresponding levels below:

Create Issue (see chapter “Issues”)
This function allows you to create a new issue and automatically add it to the corresponding list. This action greatly simplifies the process of issue management by providing a seamless and efficient way to identify, record and add new issues to the relevant list.
Refresh
This action allows you to update the given view and load possible new conditions in this scope.
Search
This action allows you to start a search. This type of option specifies the search for various objects in Fabasoft Approve Quality. These objects can be specified in the window that appears under “Selection”. You can also select whether you only want to search for objects in your own organization or also outside it.
Switch to Configuration
By executing this action, you navigate to the quality manager configuration (see chapter “Quality Management”). As a quality manager administrator, you can switch to the corresponding quality manager configuration to make configuration settings there.
Reset Search
You can use this action to reset the search you have performed. Please note that the objects that appeared during the search action will disappear again.
Save search query
If you have carried out this action, you can call up the search again and again. The objects you have searched for will also appear in the list and can be edited accordingly.
Settings
Defines general properties of the quality manager dashboard (e.g., the logo or the notification setting).
Note: If the quality manager configuration or organization management is not activated, you have limited setting options on the "User settings" and "Organization settings" tabs.

Quality Management Configuration

In the quality manager configuration, you can define general settings and authorize users to use the quality manager.

The quality manager configuration is created automatically when the quality manager is activated for your cloud organization. The owner of the cloud organization is initially stored in the quality manager configuration in the “quality manager administrator” role. As a quality manager administrator, you can switch to the quality manager configuration as follows:

Navigate to your quality manager dashboard.
Click on the “Switch to Configuration” action to switch to the quality manager configuration.

Areas

The quality manager configuration is divided into the following areas:

Sites (see chapter “Sites”)
This list shows the available Sites.
Measuring Units (see chapter “Measuring Units”)
This list shows the available Measuring Units.
Failure Locations (see chapter “Failure Locations”)
This list shows the available Failure Locations.
Failure Sub Locations (see chapter “Failure Sub Locations”)
This list shows the available Failure Sub Locations.
Failure Type (see chapter “Failure Types”)
This list shows the available Failure Types.
Failure (see chapter “Failure”)
This list shows the available Failures.
Material Classes (see chapter “Material Classes”)
This list shows the available Material Classes.
Materials (see chapter “Materials”)
This list shows the available Materials.
Customer (see chapter “Customers”)
This list shows the available Customers.
Supplier (see chapter “Supplier”)
This list shows the available Suppliers.
Lead Time Definitions (see chapter “Lead Time Definitions”)
This list shows the available Lead Time Definitions.
Equipment Types (see chapter “Equipment Types”)
This list shows the available Equipment Types.
Async Data Objects
Contains basic objects that save input data from a web service and process it in the background. If such processing is running, entries are visible in this area.
Insight Apps
Insight Apps provide aggregated access to the information in your cloud organization, tailored to your needs. You can use Insight Apps to display and highlight important information without users having to search for it explicitly.
Forms and Categories
Shows the forms and categories provided via the configuration. With the help of user-defined forms, for example, contracts can be expanded to include fields for storing customer-specific data. Categories can be assigned to objects and thus influence the behavior of the objects.
Note: Further information can be found in the white paper “Model-Based Customizing: new window”.
Processes
Shows the processes provided via the configuration. Users, organizations, organizational units and external organizations can be integrated into the processing of business objects via workflow by starting a process that can be processed via the worklist (these are usually approval and release processes).
Further information can be found in the white paper “Model-Based Customizing: new window“ and in the “Workflow: new window” chapter in the “User Help Fabasoft Cloud”.
Templates
Shows the templates provided via the configuration. The templates are displayed in the Create dialog (e.g., using the “New” context menu command). You can define contract and document templates both in the contract manager configuration and in a contract list. Templates defined in the contract manager configuration are offered for selection in all contract lists.
Note: A template can only be used once it has been released via the “Release for Usage” context menu command. Changes must be released using the “Re-release” context menu command. Sharing can also be deactivated.
Text Modules
Shows the text modules provided via the configuration that can be inserted into Word documents. Text modules can be inserted in contract documents and also in document templates. You can define text modules both in the contract manager configuration and in a contract list. Text modules defined in the contract manager configuration are available in all contract manager lists.
Reports and OData Services
Contains templates for reports and OData services. Corresponding BIRT reports, Microsoft Excel reports and OData services can be generated within this list. These reports essentially offer the possibility of data visualization and analysis. They can also be integrated into any web applications (BIRT).
Thesauri
Shows the Thesauri provided in the configuration.
Presettings
Contains default settings such as self-generated search patterns or time spans.
Failed Background Tasks
This area shows failed background tasks. You can perform the following manual actions: “Define Next Execution”, “Send Link” and “Delete”.
Note: This area is only displayed if there is at least one failed background task.

Actions

The following actions can be carried out within the configuration:

Import Translation
Imports a CSV of translations for various languages.
Export Translation
Exports a CSV of translations for various languages you can select.
Show New Events
This action opens the news of the quality manager configuration.
Settings
This action opens the quality manager configuration settings.

Settings

The following settings can be made within the quality management configuration:

Tab “General Settings”

Name
Defines the name of the configuration.
Subject
Defines the description of the configuration.
Holiday Table
Defines the public holiday table to be used in the context of the configuration (otherwise the Standard public holiday table is used).
Restrict Shortcuts Within Teamroom
Defines what type of links may be stored in the configuration. You can restrict the permitted links to objects that are assigned to the organization or to objects that are assigned to the configuration.
Restrict the Downloading or Opening of Content on the Device
Allows you to restrict the team members who are allowed to open or download content on the end device.
Roles That Are Allowed to Open or Download Content on the Device
Defines which authorizations a team member must have so that the team member can open or download content on the end device.
All Team Members May Add Members
Defines whether all team members can add users to the team or only team members with "Full Control". Members with change access may grant or revoke change access or read access to other members. Members with read access may grant or revoke read access to other members.
Restrict Team Members
Defines the organizations, organizational units, teams and external organizations whose members may be added to the Teamroom. If the list does not contain any entries, members can be added without restriction.
Main Administrator
Defines the user who receives the automatically generated e-mail messages relating to the configuration. Otherwise, all app administrators receive the e-mail messages. The user is also listed as a contact in the event of missing authorizations.
Support Coordinator
The support coordinator team has access to all support requests in the corresponding context and can perform the same actions as the submitters of the support requests.
Support Team
The support team takes over the organization-internal administration of support requests in the appropriate context.
Enable Advanced Mode
Activates a mode that allows you to work with multiple trays and manage templates and presets, among other things.
Activate Trace Output
Enables the output of information about the progress of a code execution. For example, if you are a form designer using expressions for calculation or validation, it can sometimes be difficult to identify errors in the expressions. To simplify analysis, you can have trace output written to the web browser console (cooobj.Trace("string"); resp. cooobj.Trace("string", value);).

Tab “Details”

Default Dashboard Name
This setting determines the name of the quality manager dashboard.
Default Dashboard Class
The dashboard class that is used by default for the dashboard is displayed here.
Default Dashboard Form
This setting enables the storage of a form specified in the configuration, which is derived from the dashboard class.
Manage Master Data at Site Level
This option determines whether the configuration of the individual aspects takes place at configuration level or plant level. This shifts the configurations measuring units (see chapter “Measuring Units”), Material Classes (see chapter “Material Classes”), Materials (see chapter “Materials”), Customers (see chapter “Customers”) and Suppliers (see chapter “Supplier”) inside the sites.
Default Issue Description
This text field provides a basic description of the issue (see chapter “Issues”), if no further information is provided on the issue in question.
Application Areas
Application areas can be defined here, which can be used for further classification of issues.
8D Process
This setting determines the default process setting for an issue. A standard process for an 8D process can be selected here.
Type for Measuring Devices (see chapter“Equipment Types”)
This type determines the setting of the measuring equipment.
Type for Operating Equipment (see chapter “Equipment Types”)
This type determines the setting of the operating equipment.
Correction Process (see chapter “Correction”)
This setting determines the default process setting for a correction process. A standard process for a correction process to be used can be stored here.
Corrective Action Process (see chapter “Corrective Action”)
This setting determines the default process setting for a correction action process. A standard process for a correction action process to be used can be stored here.
Preventive Action Process (see chapter “Preventive Action”)
This setting determines the default process setting for a preventive action process. A standard process for a preventive action process to be used can be stored here.
Process After Finishing Last Issue of Test Step
Starts the specified process after the last defect within a test step has been completed.

Tab “Expressions”

Expression for Determining Related Issues
Here you can provide a specific expression that is used to determine related issues.
Expression for Determining 8D Due Dates
Here you can provide a specific expression that is used to determine the 8D due dates.
Expression for Determining 8D Team
Here you can provide a specific expression that is used to determine the 8D team.
Expression for Determining Suggested Corrections
Here you can provide a specific expression that is used to determine proposals for corrections.
Expression for Determining Suggested Corrective Actions
Here you can provide a specific expression that is used to determine proposals for corrective actions.
Expression for Determining Suggested Preventive Actions
Here you can provide a specific expression that is used to determine proposals for preventive actions.
Expression for Determining Created Actions
Here you can provide a specific expression that is used to determine created actions.
Expression for Processing Extracted QR Codes
Here you can provide a specific expression that is used for processing extracted QR codes.

8D Process

The 8D process represents the further handling for the processing of an issue (see chapter “Issues”). This is based on several steps that must be carried out depending on the dimensions of the damage. “8D” stands for the eight mandatory disciplines (process steps) that are required when dealing with an issue in order to overcome the underlying problem.

General actions within the steps:
Within the individual process steps, the following actions are repeated for each individual step. These are summarized as follows:
- Open
  The issue (see chapter “Issues”) in which the current process is being executed can be opened.
- Open Properties
  The properties of the issue in which the current process is being executed can be opened.
- Finished
  This field completes the respective process step.
- Perform Risk Evaluation
  The following options are available within this process step:
  - Perform Risk Evaluation
    This option opens the issue settings and the 8D team settings via a dialog. These can be manipulated in this process.
  - Define Corrections (see chapter “Correction”)
    This option opens the list of issue specific corrections via dialog, whereby further actions can be added in the process.

The following steps describe the basic processing of an 8D based issue in more detail:

Form Team.
The following options are available within this process step:
- Schedule Deadlines
  This option opens the schedule settings of the issue (see chapter “Issues”) via dialog. The respective due dates of the dimensions must be set here. This can also be done by selecting a lead time definition.
- Form Team
  This action opens the team setting of the issue (see chapter “Issues”) via dialog. The respective teams of the dimensions must be set here if they are not selected.
Describe Problem.
The following options are available within this process step:
- Describe Problem
  Triggering this action opens a dialog box that is required for the problem description. This has several fields in which the problem can be described in more detail using location and type information.
Define Corrections.
The following options are available within this process step:
- Define Corrections (see chapter “Correction”)
  This option opens the list of issue specific corrections via dialog, whereby further actions can be added in the process.
Perform Cause Identification.
The following options are available within this process step:
- Perform Cause Identification
  A dialog box is displayed in which the corresponding cause (see chapter “Cause”) can be further specified.
Define Corrective Actions.
The following options are available within this process step:
- Define Corrective Actions (see chapter “Corrective Action”)
  Triggering this action opens a dialog box in which any information on the issue specific corrective actions can be stored. Changes can also be made to the linked cause (see chapter “Cause”).
Implement Corrective Actions.
The following options are available within this process step:
- Implement Corrective Actions (see chapter “Corrective Action”)
  The same dialog box that is displayed in the previous process step is called up to confirm the respective settings.
Define Preventive Actions.
The following options are available within this process step:
- Define Preventive Actions (see chapter “Preventive Action”)
  After pressing this action, a dialog box opens where preventive actions can be set according to the issue (see chapter “Issues”).
Further steps until process completion
First, a background task starts that checks whether the issue (see chapter “Issues”) in which the process is being executed contains open actions (see chapter “Actions”).

If this was not the case, the completion status for the issue can be set and the process for the issue can be completed accordingly.

Sites

Sites contain issues (see chapter “Issues”) and define various configuration settings. Depending on the site structure, you can define specific properties.

Areas

Sites are divided into the following areas:

Issues (see chapter “Issues”)
This list contains all issues assigned to the site.
Actions (see chapter “Actions”)
This calculated search list contains all actions that are assigned to the site and have been restricted accordingly by your further specifications.

Actions

The following actions are available for sites:

Create Issue (see chapter “Issues”)
This action creates a new issue.
Show New Events
This action shows changes and events for the current object.
Manage Follow-Ups
This action defines the Follow-Ups. In this way, you can set that a process is started or you receive a notification for the affected objects after a specified period of time has elapsed.
Templates and Presettings
This action opens the templates and presettings of the site.
Settings
This action opens the site settings.

Properties

You can define the following settings at the site:

Tab “Site”

The following settings are available in the “Site” tab:

Name
Defines the name of the site.
Default Issue Description
This text field provides a basic description of the issue (see chapter “Issues”), if no further information is provided on the issue in question.
Default Application Area
This text field provides a default application area, which have to be created in the configuration, for newly created issues.
Default Lead Time for Issues (see chapter “Issues”)
Allows you to define a specific default lead time for an issue.
Skip Risk Evaluation for Issues Created by Coordinators
This checkbox skips the risk evaluation of issues which are created by the issue coordinator.
Enabled Properties
Enables the activation of various properties on the site. Corresponding lists are displayed on the site.

Tab “Number Ranges”

The following settings are available in the “Number Ranges” tab:

Number Ranges
Allows you to specify a number range that can be stored for use in the issues (see chapter “Issues”).
Issue Number Ranges
Deposit of the number range, for use in the issues at the site concerned.

Tab “8D Team”

The following settings are available in the “8D Team” tab:

Default Issue Coordinators
Enables the deposit of a coordinator for the issues (see chapter “Issues”) at the corresponding site.
Default D1 to D8-Team
Enables the deposit of D-teams for the processing and coordination of issues at the site.

Tab “Templates & Processes”

The following settings are available in the "Templates & Processes" tab:

Templates
Templates for the corresponding object classes, contexts and languages can be stored here. These can be used within the site.
Issue 8D Process (see chapter “Issues”)
Here you can store a standard 8D process (see chapter “8D Process”) for issues at the specific site.
Correction Process (see chapter “Correction”)
Here you can define a standard correction process for issues at the specific site.
Corrective Action Process (see chapter “Corrective Action”)
Here you can define a standard corrective action process for issues at the specific site.
Preventive Action Process (see chapter “Preventive Action”)
Here you can define a standard preventive action process for issues at the specific site.
Process After Finishing Last Issue of Test Step (see chapter “Test Step”)
Here you can define a process at the specific site, which is executed after the last issue has been completed.

Create Site

To create a new site, you can proceed as follows:

Navigate into the Quality Manager Configuration (see chapter “Quality Management Configuration”).
Click on “New” within the “Sites”-List.
If templates already exist for this object class, a selection dialog is displayed. Select the desired entry from the list.
Enter a name for the new site in the field Name.
If necessary, define a default lead time for issues (see chapter “Issues”). Activate and fill out the corresponding properties that are necessary for the configuration of the site.
Switch to the Tab “Number Ranges”.
Add corresponding number ranges if necessary.
Select one of these number ranges for further processing.
Switch to the Tab “8D Team”.
Store the corresponding 8D teams.
Switch to the Tab “Templates & Processes”.
Store necessary templates and processes.
Click on “Next”.

Create Project

To create a new project in a site, you can proceed as follows:

Navigate to the “Projects” (see chapter “Projects”) list in a site.
Click on the Action “New”.
Enter an ID for the project in the field ID.
In the field Multilingual Name, enter names for the corresponding language that should then be stored in the project.
If necessary, enter a customer, which you can select in the Customer field. This customer (see chapter “Customers”) must be created first of all.
If necessary, enter an end customer, which you can select in the End Customer field. This end customer must be created first, just like the customer, if none can be selected.
Click on “Next”.

Create Incoming Goods Object

To create a new incoming goods object in a site, you can proceed as follows:

Navigate to the list of “Incoming Goods Objects” (see chapter “Incoming Goods Objects”) in the relevant site.
Click on "New" in the list of incoming goods objects in the site.
Assign an incoming goods object number in the “Number” field.
Select a supplier from the list of suppliers available there. If no supplier (see chapter “Suppliers”) exists, this must be created first of all.
If necessary, enter a posting date for the incoming goods object.
Click on “Next”.

Create Purchase Order

To create a new purchase order in a site, you can proceed as follows:

Navigate to the list of “Purchase Orders” (see chapter “Purchase Orders”) in the relevant site.
Click on “New” in the list of purchase orders in the site.
Enter a purchase order number in the “Purchase Order Number” field.
Enter an order date in the “Order Date” field.
Select a supplier from the list of suppliers found there. If no supplier (see chapter “Suppliers”) is available, this must be created first of all.
Select a purchasing group from the list of purchasers found there. If no purchaser group (see chapter “Purchaser Groups”) exists, this must be created first of all.
Enter a total value in the corresponding currency in the “Total Value” field.
Select a header text for the order.
Select a state for the order.
Click on “Next”.

Create Purchaser Group

To create a new purchasing group in a plant, you can proceed as follows:

Navigate to the list of “Purchasing groups" (see chapter “Purchaser Groups”) in the relevant site.
Click on “New” in the list of purchasing groups in the site.
Assign a purchasing group ID in the “ID” field.
Select a state for the purchasing group.
Click on “Next”.

Create Issue

To create a new issue (see chapter “Issues”) in a site, you can proceed as follows:

Click on the “Create Issue” action in the site
Select a site in the Site field. This is the referenced site for the issue. The site in which you are located is already pre-filled.
Write a short description in the Short Description field, briefly explaining the issue.
Select an issue source in the Issue Source field.
Select a supplier (see chapter “Suppliers”), if necessary. This must be created first if none can be selected.
Select a date in the Occurred on field.
Select a severity in the Severity field.
Select a PDCA state in the PDCA state field, if necessary.
Select a failure location (see chapter “Failure Locations”) in the Failure Location field. This must be created first if none can be selected.
Select a failure sub location (see chapter “Failure Sub Locations”) in the Failure Sub Location field. This must also be created first if none can be selected.
Note: If a Failure Location does not have a Failure Sub Location defined, this does not need to be filled in.
Select a failure type (see chapter “Failure Types”) if this is necessary. This must be created first if none can be selected.
Select a failure (see chapter “Failure”) if this is necessary. This must be created first if none can be selected.
Select units (see chapter “Unit”) if this is necessary. These must be created first.
Select a BOM item (see chapter “BOM”) if this is necessary. This must be created first.
Add related issues if necessary.
Switch to the Tab “8D Team”.
Select various coordinators for the issue.
Select various members for the individual D-Teams, if necessary.
Switch to the Tab “8D Schedule”.
Select a lead time definition (see chapter “Lead Time Definitions“) if necessary.
Select the corresponding D due dates for the individual dimensions. These can be set in the fields D1 Due on to D8 Due on.
Switch to the Tab “D2 – Describe Problem”.
Describe a problem summary, if necessary.
Select a failure location. This is already pre-initialized if it was selected under the “Issue” tab.
Select a failure sub location, if necessary. This is already pre-initialized if it was selected under the “Issue” tab.
Note: If a Failure Location does not have a Failure Sub Location defined, this does not need to be filled in.
Select a failure type, if necessary. This is already pre-initialized if it has been selected under the "Issue" tab.
Select a failure, if necessary. This is already pre-initialized if it was selected under the "Issue" tab.
Add attachments to the problem summary under the Attachments for problem summary field, if necessary.
Switch to the Tab “D3 – Define Corrections” (see chapter “Correction”).
Add an entry if this is necessary.
Switch to the Tab “D4 – Cause Identification”.
Describe a summary for root cause identification, if necessary.
Add a root cause identification if necessary.
Add a Direct Cause (see chapter “Cause”), if necessary. This must be created first if none can be selected.
Add a main cause, if necessary. This must also be created first if none can be selected.
Switch to the Tab “D5 & D6 – Define/Implement Corrective Actions”.
Add a Corrective Action, if necessary. This must be created first if none can be selected.
Include a summary of the corrective action determination, if necessary.
Add a summary of the anchoring of the corrective actions, if necessary.
Switch to the Tab “D7 – Define Preventive Actions”.
Add a preventive action if necessary. This must be created first if none can be selected.
Add a summary of the preventive actions, if necessary.
Switch to the Tab “D8 – Complete 8D Process”.
Fill in the text fields displayed there, if necessary.
Click on “Save”.

Create Inspection Master Plan

To create a new master test plan, you can proceed as follows:

Navigate to the Inspection Master Plans (see chapter “Inspection Master Plans”) list in the relevant site.
Click on “New” in the inspection master plans list in the site.
Write an appropriate name in the corresponding languages in the Multilingual Name field.
The "Active" field of the inspection master plan is ticked by default, but you can deactivate this.
Click on “Next”.

Create Inspection Phase

To create a new test phase, you can proceed as follows:

Navigate to the Inspection phases (see chapter “Inspection Phases”) list in the relevant site.
Click on "New" in the inspection phases list in the site.
Define an appropriate ID for the inspection phase. This is used for identification.
Write an appropriate name in the corresponding languages in the Multilingual Name field.
The "Active" field of the inspection plan is ticked by default, but you can deactivate this.
Click on “Next”.

Create Test Step

To create a new test step, you can proceed as follows:

Navigate to the test steps (see chapter “Test Step“) list in the relevant site.
Click on “New” in the test steps list in the factory.
Write an appropriate name in the corresponding languages in the Multilingual Name field.
Describe an adequate test instruction in the appropriate languages in the Instruction Text field.
Add a measurement device class, if necessary. This must be created first if none can be selected.
Add a measurement device, if necessary. This must be created first if none can be selected.
Add an operating equipment device class, if necessary. This must be created first if none can be selected.
Add an operating equipment, if necessary. This must be created first if none can be selected.
Add attachments if necessary.
Add instruction documents if necessary.
The test step is “Active” by default, but you can deactivate this.
Click on “Next”.

Create Equipment Class

To create a new equipment class (see chapter “Equipment Classes“), you can proceed as follows:

Navigate to the equipment classes list in the relevant site.
Click on “New” in the Equipment classes list in the site.
Define an appropriate ID for the inspection phase (see chapter “Inspection Phases”). This is used for identification.
Write an appropriate name in the corresponding languages in the Multilingual Name field.
Click on “Next”.

Issues

Issues contain units (see chapter “Unit”) and define various configuration settings. There is also a calendar in which various important due dates are displayed. 8D reports are an important component in the context of issues.

Areas

Issues are divided into the following areas:

Calendar
Indicates deadlines and dates for the issue.
Issue
This field shows the basic data relating to the issue.
Units
Describes a list of units that are assigned to the issue.
Description
This is the description of the issue.
D3 – Define Corrections (see chapter “Correction”)
Describes a list of corrections assigned to the issue.
D4 – Cause Identification
Describes various properties that are necessary for identifying the cause of an issue.
D5 & D6 – Define/Implement Corrective Actions (see chapter “Corrective Action”)
Describes various properties that are necessary for the corrective actions of an issue.
D7 – Define Preventive Actions (see chapter “Preventive Action”)
Describes various properties that are necessary for the prevention actions of an issue.
8D Reports
Describes a list of 8D reports that are assigned to the issue.
Attachments
Describes a list of objects, such as PDFs or WIN Word documents, that are assigned to the issue.
Related Issues
Describes a list of issues related to the current issue.
Referenced by
Describes a list of issues that reference the current issue.

Actions

The following actions can be found within an issue:

Generate 8D Report
Generates an 8D report based on the data in an issue and adds it to the 8D reports list.
Add Remark
Enables the formulation of notes to be added to an issue.
Properties
This action calls up the properties of an issue, which can be manipulated within the dialog that appears.

Properties

You can define the following properties in an issue:

Tab “Issue”

Within the "Issues" tab, there are the following settings:

Site
This field contains the site (see chapter “Sites”) where this issue occurred.
State
This field contains the current processing status of the issue.
ID
This field contains the unique ID of the issue.
Short Description
Defines the short description of the issue.
Issue Source
Specifies the source of the issue.
Supplier (see chapter “Suppliers”)
Specifies the supplier in case of issues.
Occurred on
Specifies the date on which the issue occurred.
Severity
Determines the severity of the issues.
PDCA-State
Defines the PDCA status of the issue.
Failure Location (see chapter “Failure Locations”)
Determines the failure location of the issue.
Failure Sub Location (see chapter “Failure Sub Locations”)
Defines a specific failure sub location at the issue, whereby this failure sub location is always subordinate to the failure location.
Failure Type (see chapter “Failure Types”)
Defines a specific failure type on the issue, which is relevant for the failure selection.
Failure (see chapter “Failure”)
Defines the failure that is responsible for the issue.
Units (see chapter “Unit”)
Defines several units for the issue.
BOM Item (see chapter “BOM”)
BOM items can be added to the issue here. These describe more detailed information on the issue.
Material (see chapter “Materials”)
Defines a material on which the issue has arisen. If a BOM item is selected and it contains a material, this is automatically adopted as the material for the issue.
Incoming Goods Object (see chapter “Incoming Goods Objects”)
This field contains the associated incoming goods object.
Purchase Order (see chapter“Purchase Orders”)
Defines a purchase order to be assigned to the issue.
Purchase Order Position (see chapter “Purchase Order Positions”)
Defines a purchase order position that is available in the selected order.
Reference Quantity
Defines the reference quantity.
Complaint Quantity
Defines the complaint quantity.
Description
Defines a description for the issue.
Initial State
Defines an initial state for the issue.
Target State
Defines a target state for the issue.
Attachments
In this field, you can add attachments to the issue.
Related Issues
In this field, you can add related issues to the issue. These are used for recognizability.

Tab “8D Team”

The following settings are available in the “8D Team” tab:

Coordinators
The coordinators of the issue are consulted for basic issue handling.
D1 – D8 Team
These are the respective teams that are responsible for the issue and its different areas of treatment and continue to work on the issue in terms of the team task.

Tab “8D Schedule”

The following settings are available in the “8D appointments” tab:

Lead Time Definition (see chapter “Lead Time Definitions”)
This allows you to provide an already specified lead time definition for the issue.
D1 Due on – D8 Due on
This is used to specify the due dates of the respective dimensions. These are used for further processing.

Tab “D2 – Describe Problem”

The following settings are available in the “D2 - Describe problem” tab:

Problem Summary
In terms of summarizing the problem, the respective issue-related processors have the opportunity to describe the problem in more detail.
Failure Location (see chapter “Failure Locations”)
If no failure location has been selected under the “Issues” tab, you can select a failure location here. If one has already been selected, it will be displayed here.
Failure Sub Location (see chapter “Failure Sub Locations”)
If no failure sub location has been selected under the “Issues” tab, you can select a failure sub location here. If one has already been selected, it will be displayed here.
Failure Type (see chapter “Failure Types”)
If no failure type has been selected under the “Issues” tab, you can select a failure type here. If one has already been selected, it will be displayed here.
Failure (see chapter “Failure”)
If no failure has been selected under the “Issues” tab, you can select a failure here. If one has already been selected, it will be displayed here.
Problem Summary Attachments
This field offers the option of adding various attachments to the issue that could be useful for further processing of the issue.

Tab “D3 – Define Corrections”

The following settings are available in the “D3 - Define Corrections” tab:

Corrections (see chapter “Correction”)
Corrections relating to the issues can be added within this tab.
Corrections Summary
In the sense of the summary of the corrections, the respective processor related to the issues can describe the corrections in more detail here.

Tab “D4 – Cause Identification”

The following settings are available in the “D4 - Cause detection” tab:

Cause Identification Summary
In the sense of the summary of the causes, the respective processor related to the issues can describe the causes (see chapter “Cause”) in more detail here.
Cause Identification – 5-Why
In this field, you can add corresponding 5-Whys to the issue. These are subsequently also used to identify the cause.
Direct Cause (see chapter “Cause”)
In this field you can add a direct cause to the issue, if one is known.
Root Cause
In this field you can add a root cause to the issue, if one is known.

Tab “D5 & D6 – Define/Implement Corrective Actions”

The following settings are available in the “D5 & D6 – Define/Implement corrective actions” tab:

Corrective Actions (see chapter “Corrective Action”)
In this field you can add appropriate corrective actions to the issue.
Define Corrective Actions Summary
Within this field you can summarize why a selected corrective action was felt to be correct.
Implement Corrective Actions Summary
Within this field, you can mention relevant points regarding the anchoring of corrective actions.

Tab “D7 – Define Preventive Actions”

The following settings are available in the “D7 - Define preventive actions” tab:

Preventive Actions (see chapter “Preventive Action”)
This field is used to add preventive actions associated with the issue.
Define Preventive Actions Summary
Within this field you can summarize the used corrective actions used for the issue.

Tab “D8 – Complete 8D Process”

The following settings are available in the “D8 - Completion 8D process” tab:

What happened?
How did this happen?
Why did this happen (and why was it not detected)?
What was done?
What are the Lessons Learned?

These fields are used to answer and guide the correct interpretation of an issue that has occurred. These fields should also be used to close an issue.

Failure Locations

Failure locations are assigned to an issue (see chapter “Issues”). This can be traced and organized using this failure location.

Actions

The following actions are available for failure sub locations:

Import Failure Location
This function is used to import multiple failure locations. These failure locations are imported via a CSV.

Properties

You can define the following properties for a failure location:

ID
Defines the ID for the respective failure location. This ID is used to identify the respective failure location.
Multilingual Name
The multilingual name is used to name the failure location, whereby this name can be defined in a wide variety of languages.
Definition
The definition is used to describe the failure location, whereby this definition can be defined in a wide variety of languages.
Active
This option is used to differentiate between failure locations that are active and those that can no longer be used.

Failure Sub Locations

Failure sub locations are assigned to an issue (see chapter “Issues”). This can be traced and organized using this failure sub location.

Actions

The following actions are available for failure sub locations:

Import Failure Sub Location
This function is used to import multiple failure sub locations. These failure sub locations are imported via a CSV.

Properties

You can define the following properties for a failure sub location:

ID
Defines the ID for the respective failure location. This ID is used to identify the respective failure sub location.
Multilingual Name
The multilingual name is used to name the failure sub location, whereby this name can be defined in a wide variety of languages.
Definition
The definition is used to describe the failure sub location, whereby this definition can be defined in a wide variety of languages.
Active
This option is used to differentiate between failure sub locations that are active and those that can no longer be used.

Failure Types

Failure types are assigned to an issue (see chapter “Issues”). This can be traced and organized using this failure type.

Actions

The following actions are available for failure types:

Import Failure Type
This function is used to import multiple failure types. These failure types are imported via a CSV.

Properties

You can define the following properties for a failure type:

ID
Defines the ID for the respective failure type. This ID is used to identify the respective failure type.
Multilingual Name
The multilingual name is used to designate the failure type, whereby this name can be defined in a wide variety of languages.
Definition
The definition is used to describe the failure type, whereby this definition can be defined in a wide variety of languages.
Active
This option is used to differentiate between failure types that are active and those that can no longer be used.

Failure

Failures are assigned to an issue (see chapter “Issues”). This can be traced and organized using this failure.

Actions

The following actions are available in the event of failures:

Import Failure
This function is used to import multiple failures. These failures are imported via a CSV.

Properties

In the event of a failure, you can set the following properties:

ID
Defines the ID for the respective failure. This ID is used to identify the respective failure.
Multilingual Name
The multilingual name is used to name the failure, whereby this name can be defined in a wide variety of languages.
Definition
The definition is used to describe the failure, whereby this definition can be defined in a wide variety of languages.
Active
This option is used to differentiate between failures that are active and those that can no longer be used.

Measuring Units

Measuring units can be created and used for different areas. Measuring units are quantities that are used as comparative quantities for quantitative determination.

Actions

The following actions are available for measuring units:

Import Measuring Units
This function is used to import several measuring units. These measuring units are imported via a CSV.

Properties

You can define the following properties for measuring units:

ID
Defines the ID for the respective measuring unit. This ID is used to identify the respective measuring unit.
ISO-Code
Defines the ISO code for the respective measuring unit. This ISO code is used to identify the respective measuring units.
Technical Name
The multilingual name is used for the technical designation of the measuring unit, whereby this name can be defined in a wide variety of languages.
Commercial Name
The multilingual name is used for the commercial designation of the measuring unit, whereby this name can be defined in a wide variety of languages.
Measuring Unit Text
The definition serves to describe the measuring unit, whereby this definition can be defined in a wide variety of languages.
State
This option is used to differentiate between measurement units that are active and those that can no longer be used.

Material Classes

The material classes can be assigned to the respective issues (see chapter “Issues”). The material class is used to organize any materials.

Actions

The following actions are available for material classes:

Import Material Classes
This function is used to import several material classes. These material classes are imported via a CSV.

Properties

You can define the following properties for a material class:

Short Name
This is a field that is available for the specification of any material classes.
State
This option is used to differentiate between material classes that are active and those that can no longer be used.

Materials

The materials can be assigned to the respective issues (see chapter “Issues”).

Actions

The following actions are available for materials:

Import Materials
This function is used to import multiple materials. These materials are imported via a CSV.

Properties

You can define the following properties for a material:

Number
This is the concrete identification option for a material in a specific material class.
Material Class
This is the material class that is used to group the materials.
Multilingual Name
The multilingual name is used to name the material, whereby this name can be defined in a wide variety of languages.
Measuring Unit
This field offers the option of linking a unit of measurement that describes the material in more detail.
Gross Weight
This field offers the possibility to enter the gross weight of the material.
Net Weight
This field offers the possibility to specify the net weight of the material.
Weight Unit
This field allows you to specify the weight unit for the specific material.
State
This option is used to differentiate between materials that are active and those that can no longer be used.

Customers

The customers can be assigned to the respective issues (see chapter “Issues”). This serves as a specification of the extent to which the issue has arisen.

Actions

Import Customers
This function is used to import multiple customers. These customers are imported via a CSV.

Properties

You can define the following properties for a customer:

ID
Defines the ID for the respective customer. This ID is used to identify the respective customer.
Company Name
This defines the company name of the respective customer. This also serves to identify the customer.
State
This option is used to differentiate between customers who are active and those who can no longer be used.

Suppliers

The suppliers can be assigned to the respective issues (see chapter “Issues”). This serves as a specification of the extent to which the issue has arisen.

Actions

Import Suppliers
This function is used to import multiple suppliers. These suppliers are imported via a CSV.

Properties

You can define the following properties for a supplier:

ID
Defines the ID for the respective supplier. This ID is used to identify the respective supplier.
Company Name
This defines the company name of the respective supplier. This also serves to identify the supplier.
State
This option is used to differentiate between suppliers that are active and those that can no longer be used.

Lead Time Definitions

The lead time definitions can be assigned to the respective issues (see chapter “Issues”). This serves as a specification of the lead time in which the issue should be located.

Properties

You can specify the following properties in a lead time definition:

Multilingual Name
The multilingual name is used to designate the lead time, whereby this name can be defined in a wide variety of languages.
D1 Due on (Days) – D8 Due on (Days)
This is used to specify the due dates of the respective dimensions. These are used for further processing.

Equipment Types

The equipment types can be assigned to the respective issues (see chapter “Issues”). This serves as a specification of the extent to which the issue has arisen.

Properties

You can define the following properties for an equipment type:

ID
Defines the ID for the respective equipment type. This ID is used to identify the respective equipment type.
Multilingual Name
The multilingual name is used to name the equipment type, whereby this name can be defined in a wide variety of languages.
Active
This option is used to differentiate between equipment types that are active and those that can no longer be used.

Unit

The units can be assigned to the respective issues (see chapter “Issues”). These serve as a specification of the extent to which the issue has arisen.

Areas

Units are divided into the following areas:

Unit
This is the main section of the unit properties.
BOM (see chapter “BOM”)
This list is used to add parts list items to the respective unit. These can be managed accordingly within a unit.
Attachments
This list is used to add corresponding unit-specific documents to the unit.
Inspection Plans (see chapter “Inspection Plans”)
If an inspection master plan is available, this list makes it possible to create corresponding inspection plans within a unit.
Issues (see chapter “Issues”)
Within a unit, this list offers the possibility to add issues and also set them in dependency.

Properties

You can define the following properties in a unit:

ID
Defines the ID for the respective unit. This ID is used to identify the respective unit.
Project
This is the project, which is related to the unit.
Multilingual Name
The multilingual name is used to name the unit, whereby this name can be defined in a wide variety of languages.
Active
This option is used to differentiate between units that are active and those that can no longer be used.

BOM

The parts lists are located within a unit (see chapter “Unit”), which in turn exists in a project. This BOM has several items.

Areas

BOM items are divided into the following areas:

Subordinated Items
This list is used to assign further BOM items that relate to the BOM item.
Issues (see chapter “Issues”)
This list refers to the issues that belong to the corresponding BOM item.

Properties

You can define the following properties within a BOM item:

ID
Defines the ID for the respective BOM item. This ID is used to identify the respective BOM item.
Belongs to
This setting determines the relationship or unit to which the respective BOM item belongs.
Multilingual Name
The multilingual name is used to name the BOM item, whereby this name can be defined in a wide variety of languages.
Material (see chapter “Materials”)
A material can be linked to the respective BOM here.
Required Quantity
The required quantity describes, within the BOM, how high the material quantity of the corresponding material is.

Incoming Goods Objects

The incoming goods object essentially refers to the physical or digital recording of goods that arrive in a warehouse or in a company. It can be an element in logistics processes that ensures that incoming goods are properly recorded, checked and added to the inventory.

Properties

You can define the following properties within an incoming goods object:

Number
Defines the number for the respective incoming goods object. This ID is used to identify the respective incoming goods object.
Supplier (see chapter “Suppliers”)
Defines the supplier of the incoming goods object.
State
Displays the status of the incoming goods object.
Posting Date
This field contains the posting date of the incoming goods object.

Purchase Orders

A purchase order is generally a central component of the procurement process. It also plays an important role in warehouse management, production and general business processing.

Areas

Purchase orders are divided into the following areas:

Purchase Order Positions
This list is used to assign further purchase order positions that relate to the purchase order.
Issues (see chapter “Issues”)
This list refers to the issues that belong to the corresponding purchase order.

Properties

You can define the following properties within a purchase order:

Purchase Order Number
Defines the order number for the respective purchase order. This order number is used to identify the respective purchase order.
Order Date
This field contains the date of the purchase order.
Supplier (see chapter “Suppliers”)
This field contains the supplier of the purchase order.
Purchaser Group (see chapter “Purchaser Groups”)
This field contains the purchaser group of the purchase order.
Total Value
The total value field contains a value that reflects the total costs of subordinate purchase order positions.
Header Text
The header text field contains a short summary of the purchase order.
State
This option is used to differentiate between purchase orders that are active and those that can no longer be used.

Purchase Order Positions

A purchase order position within a purchase order is a specific entry that covers a particular good or service requested by a supplier. This purchase order position contains detailed information such as the item description, quantity, unit price, etc. An issue can also occur in connection with a purchase order position if the delivered product or service does not meet the agreed specifications.

Areas

Purchase order positions are divided into the following areas:

Purchase Order Position
This list shows some properties of the purchase order position. These can also be edited.
Issues (see chapter “Issues”)
This list refers to the issues that belong to the corresponding purchase order position.

Properties

You can define the following properties within a purchase order position:

Position Number
Defines the ID for the respective purchase order position. This ID is used to identify the respective purchase order position.
Purchase order
This field shows the associated purchase order.
Supplier (see chapter “Suppliers”)
This field shows the associated supplier.
Short Description
A short description can be entered in this field.
Arrival Date
In this field, you can define the arrival date of the purchase order position.
Order Quantity
The purchase order quantity describes the quantity of material ordered.
Order Quantity Measuring Unit (see chapter “Materials “)
The purchase order measuring unit describes the measuring units of the material ordered.
Quantity in Price Unit
The quantity in price measuring unit describes the quantity of material ordered in a price measuring unit.
Price Unit Measuring Unit (see chapter “Materials”)
The price measuring unit describes the measuring unit of the material ordered, only in a different unit. This is used to calculate the purchase order position value.
Price
The price describes the price of the purchase order position.
Price Unit
The price unit is the unit of the price. This must be specified as a number.
Position Value
The position value describes the value of this purchase order position.
Material (see chapter “Materials“)
This field contains the material to which this purchase order position refers.
Material Order Text
The material order text contains additional information regarding the material of the purchase order.
Net Weight
The net weight describes the weight of the delivery without packaging.
Weight Unit (see chapter “Materials”)
The weight unit for the net weight can be entered here.
Additional Note
The additional note contains additional notes that do not match either the material order text or the delivery text.
Delivery Text
The delivery text is a short text containing additional information about the delivery.
State
This option is used to differentiate between purchase order positions that are active and those that can no longer be used.

Purchaser Groups

The purchasing groups can be assigned to the respective purchase orders (see chapter “Purchase Orders”). This serves as a specification of which purchasing group has placed the purchase order.

Areas

Purchaser Groups are divided into the following areas:

Purchaser Group
This is the metadata of the purchasing group.
Purchase Orders
These are the orders that generally belong to the purchaser group.

Properties

You can define the following properties for a purchaser group:

ID
Defines the ID for the respective purchasing group. This ID is used to identify the purchasing group.
State
This option is used to differentiate between purchasing groups that are active and those that can no longer be used.

Actions

Actions are divided into corrections (see chapter “Correction”), corrective actions (see chapter “Corrective Action”) and preventive actions (see chapter “Preventive Action”). These objects must always be created using an underlying template. Corresponding instances are required for this in the template list at configuration level (see chapter “Quality Management”).

Once this has been done, corresponding templates must be stored on the site (see chapter “Sites”). This requires a language, context, the corresponding object class and the template. Each individual action is described in more detail below.

Correction

The immediate action is the first action to be taken in the 8D process (see chapter “8D Process”). In the case of a 3D process, this must be specified.

Properties

Issue (see chapter “Issues”)
This field refers to the referenced issue within which this action was created.
State
The status describes the life cycle stage in which the corresponding correction is located.
Responsible
The person responsible for the specific action is entered in this field.
Due on
The due date for the correction can be set here.
With Feedback?
This field can be used to decide whether feedback should be sent to the person responsible.
Feedback to
If the field With Feedback? has been selected, this field must be filled in accordingly.
Short Description
This is a brief description of the correction.
Number
This is an automatically generated number for the correction. This is for the unique identification of the correction.
Description
This is the description of the correction.
Effectiveness Review?
This field is used to decide whether an effectiveness review should be carried out.
Effectiveness Review After
This field is displayed after the Effectiveness Review? field has been checked. This is a period to be set to which the effectiveness review should relate.
Effectiveness Review by
This field is displayed after the Effectiveness Review? field has been checked. This is a user to be set to whom the effectiveness review should refer.

Corrective Action

The corrective action is the second relevant action to be set in the 8D process. In the case of a D5 & D6 process, this must be specified.

Properties

D4 Cause (see chapter “Cause “)
This is a cause that must be specified in the course of D4 cause identification. This must be referenced here.
Cause
In the course of the D4 cause, a cause is selected which is subsequently linked here.
Issue (see chapter “Issues”)
This is a referenced field for the basic issue object.
State
The status describes the life cycle stage in which the corresponding corrective action currently is.
Responsible
The person responsible for the specific action is entered in this field.
Due on
The due date for the corrective actions can be set here.
With Feedback?
This field can be used to decide whether feedback should be sent to the person responsible.
Feedback to
If the field With Feedback? has been selected, this field must be filled in accordingly.
Short Description
This is a brief description of the corrective action.
Number
This is an automatically generated number for the corrective actions. This is for the unique identification of the corrective action.
Description
This is the description of the corrective action.
Effectiveness Review?
This field is used to decide whether an effectiveness review should be carried out.
Effectiveness Review After
This field is displayed after the Effectiveness Review? field has been checked. This is a period to be set to which the effectiveness review should relate.
Effectiveness Review by
This field is displayed after the Effectiveness Review? field has been checked. This is a user to be set to whom the effectiveness review should refer.

Preventive Action

The preventive actions represent the third and last relevant action to be set in the 8D process (see chapter “8D Process”). In the case of a D7 process, this must be specified.

Properties

D4 Cause (see chapter “Cause”)
This is a cause that must be specified in the course of D4 cause identification. This must be referenced here.
Cause
In the course of the D4 cause, a cause is selected which is subsequently linked here.
Issue (see chapter “Issues”)
This is a referenced field for the basic issue object.
State
The status describes the life cycle stage in which the corresponding preventive action currently is.
Responsible
The person responsible for the specific action is entered in this field.
Due on
The due date for the preventive action can be set here.
With Feedback?
This field can be used to decide whether feedback should be sent to the person responsible.
Feedback to
If the field With Feedback? has been selected, this field must be filled in accordingly.
Short Description
This is a brief description of the preventive action.
Number
This is an automatically generated number for the preventive action. This is for the unique identification of the preventive action.
Description
This is a description of the preventive action.
Effectiveness Review?
This field is used to decide whether an effectiveness review should be carried out.
Effectiveness Review After
This field is displayed after the Effectiveness Review? field has been checked. This is a period to be set to which the effectiveness review should relate.
Effectiveness Review by
This field is displayed after the Effectiveness Review? field has been checked. This is a user to be set to whom the effectiveness review should refer.

Process for Actions

The basic process for actions represents the further handling for the processing of a measure.

General actions within the steps:
Within the individual process steps, the following actions are repeated for each individual step. These are summarized as follows:
- Open
  The action in which the current process is being executed can be opened.
- Open Properties
  The properties of the action in which the current process is being executed can be opened.
- Finish
  This field completes the respective process step.
Finish Action
The following options are available within this process step:
- Open Issue (see chapter “Issues”)
  The issue related to the action or the issue affected by the action is opened.
Action Finished
The following options are available within this process step:
- Open Issue
  The issue related to the action or the issue affected by the action is opened.
- Take Note
  This field completes the “Action Finished” process step and at the same time opens a dialog box where the settings of the action can be checked and manipulated accordingly.
Further steps until process completion
First, a background task starts, which is then replaced by an effectiveness review and the corresponding upload. Once this has been completed, the task is considered finished.

Cause

The causes can be created within an issue (see chapter “Issues”) and are assigned to it accordingly. The cause can be restricted at issue level, whereby a direct cause and a root cause can be referenced.

Areas

The causes are divided into the following areas:

Corrective Actions (see chapter “Corrective Action”)
This list provides an overview of the associated corrective action, whereby corresponding corrective actions must be stored for the respective cause.
Preventive Actions (see chapter “Preventive Action”)
This list provides an overview of the associated preventive action, whereby appropriate preventive actions must be stored for each cause.

Properties

Sequence Number
The sequence number describes the cause.
Failure
The error shows the exact failure to which this cause belongs.
Issue (see chapter “Issues”)
This field holds the connection to the issue or describes the issue in which the cause is located.
Issue Description
This field describes the issue in more detail (see chapter “Issues”) or refers to the issue description in the issue.
Short Description
This field contains a brief description of the cause.
Why
This field serves as support for the cause description. The extent to which the cause occurred should be specified.
Therefore
This field also serves to support the description of the cause. It should specify what the cause is, or it is the direct formulation of causality.
Cause Area
The cause area is used to link to a failure location (see chapter “Failure Locations”). However, this failure location can only be referenced if there is an active failure sub location.
Cause Sub Area
The error sub-location mentioned above (see chapter “Failure Sub Locations”) can be referenced here if it is active.
Cause Type
This field is used to reference a failure type (see chapter “Failure Types”).
Cause
The cause serves as a reference to a failure that has been restricted by selecting a failure type.
Component Affected
This selection field enables the reference to a component. This component is expressed by the following four fields.
Affected Component (see chapter “Failure Locations”)
This field enables the reference to a failure location, whereby the affected component is present at this failure location.
Affected Sub Component (see chapter “Failure Sub Locations”)
This field enables the reference to a failure sub location, whereby the affected sub-component is present at this failure sub location.
Component Failure Type (see chapter “Failure Types”)
This field enables the reference to a failure type, describing on an abstract level how the component was damaged.
Component Failure (see chapter “Failure”)
This field enables the reference to an failure, whereby this is restricted by the selected failure type (see chapter “Failure Types”).
Remarks
This field can be used as a comment field. Any remarks on the cause can be added here.
Corrective Actions (see chapter “Corrective Action”)
This list provides an overview of the associated corrective actions, whereby corresponding corrective actions must be stored for the respective cause.
Preventive Actions (see chapter “Preventive Action”)
This list provides an overview of the associated preventive actions, whereby appropriate preventive actions must be stored for each cause.

Equipment Classes

The equipment classes can be accessed via the settings on the configuration or on the respective site (see chapter “Sites”).

At least one equipment type (see chapter “Equipment Types”) must be created in the configuration list. This can be stored under Type for measuring equipment and Type for operating equipment in the configuration settings.

Within the site (see chapter “Sites”) concerned, the corresponding properties, in this case equipment classes, must be activated.

If this has been done, an equipment class can be created in the course of the site.

Properties

ID
Defines the ID for the respective equipment class. This ID is used to identify the respective equipment class.
Multilingual Name
The multilingual name is used to name the equipment class, whereby this name can be defined in a wide variety of languages

Equipment

Equipment can be produced within an equipment class (see chapter “Equipment Classes”).

Areas

Equipment is divided into the following areas:

Attachments
This list is used to add various equipment-related documents.

Properties

ID
Defines the ID for the respective equipment. This ID is used to identify the respective equipment.
Type
The type specifies the basic type of the equipment, whereby these types were set up in the configuration.
Multilingual Name
The multilingual name is used to name the equipment, whereby this name can be defined in a wide variety of languages.
Equipment Class (see chapter “Equipment Classes”)
This is the direct link to the equipment class above.
Active
This option is used to differentiate between equipment that is active and equipment that can no longer be used.

Projects

A project can be produced within a site (see chapter “Sites”). This project serves as a reference object.

Areas

A project is divided into the following areas:

Project
This is a brief overview of the project metadata.
Units (see chapter “Unit”)
This is a list that refers to the units within a project. Units can be created within the project.
Attachments
This list is used to add various project-related documents.

Properties

You can define the following properties in a project:

ID
Defines the ID for the respective project. This ID is used to identify the respective project.
Multilingual Name
The multilingual name is used to name the project, whereby this name can be defined in a wide variety of languages.
Customer (see chapter “Customers”)
This is the linking of the customer of a project. A customer is created in the customer list at configuration level.
End User
This is the linking of the end user of a project. An end user is created in the customer list at configuration level.

Inspection Plans

The following chapter describes the subdivision of the test plans in more detail.

Inspection Master Plans

An inspection master plan can be produced within a site (see chapter “Sites”) and serves as a superordinate inspection plan (see chapter “Inspection Plans”) for all underlying inspection plans, inspection phases (see chapter “Inspection Phases”) and test steps (see chapter “Test Step”).

Areas

An inspection master plan is divided into the following areas:

Inspection Plans
These are the underlying inspection plans.
Released Revisions
These are the released revisions of the inspection plans.

Properties

You can define the following properties in an inspection master plan:

Multilingual Name
You can define the following properties in an inspection master plan:
Active
This option is used to differentiate between master inspection plans that are active and those that can no longer be used.
Site (see chapter “Sites”)
This is the representation of the site referred to.

Inspection Plans

An inspection plan can be produced within an inspection master plan and is used to structure the inspections.

Actions

The following actions are available within an inspection plan:

Create Test Step (see chapter “Test Step”)
Creates a test step within the referenced inspection plan, which also refers to the inspection plan as a result.
Create Revision
Creates a revision of the inspection plan. This revision is added at inspection master plan level.
Set Inactive
Sets the relevant inspection plan to “inactive”.

Properties

You can define the following properties in an inspection plan:

Inspection Phase (see chapter “Inspection Phases”)
This is the link to the inspection phase to be obtained.
State
This is the status currently occupied by the inspection plan.
Released Revision
This is a released revision of the inspection plan.
Sequence Number
This is the current sequence number.
Sorting Number
This is the sorting number of the inspection plan.
Multilingual Name
The multilingual name is used to name the inspection plan, whereby this name can be defined in a wide variety of languages.
Description
The description serves to formulate the inspection plan in more detail or to describe the extent to which it can be used.
ITPs
The ITPs are the display of the inspection master plans (see chapter “Inspection Master Plans”).
Template Created by
This field stores the information by whom the inspection plan was created.
Template Created on/at
This field stores the information when the inspection plan was created.

Inspection Phases

An inspection phase can be created within a site (see chapter “Sites”). This is used to further subdivide the inspection phases and test steps (see chapter “Test Step”).

Properties

You can define the following properties in an inspection phase:

ID
Defines the ID for the respective inspection phase. This ID is used to identify the respective inspection phase.
Multilingual Name
The multilingual name is used to name the inspection phase, whereby this name can be defined in a wide variety of languages.
Active
This option is used to differentiate between inspection phases that are active and those that can no longer be used.
Site
This is the superordinate work of the test phase.

Test Step

A test step can be created within an inspection phase (see chapter “Inspection Phases”), or an inspection plan (see chapter “Inspection Plans”). This serves to further subdivide the inspection plan.

Areas

The following areas exist within a test step:

Test Step
This is the metadata section of the test steps.
Attachments
This list is used to attach objects to the test step that affect it.

Properties

You can define the following properties in a test step:

ID
This ID is used to identify the respective test step.
Multilingual Name
The multilingual name is used to name the test step, whereby this name can be defined in a wide variety of languages.
Instruction Text
This is a test instruction that must be carried out in accordance with the test step.
Measuring Device Class (see chapter “Equipment Classes”)
This is the link to a measuring equipment class that is associated with the test step.
Measuring Device (see chapter “Equipment”)
This is a measuring device that is connected to the test step and is restricted accordingly by the measuring device class already selected.
Operating Equipment Class (see chapter “Equipment Classes”)
This is the link to an operating equipment class that is associated with the test step.
Operating Equipment (see chapter “Equipment”)
This is an operating equipment that is associated with the test step and is restricted accordingly by the operating equipment class already selected.
Author
This is the initial author of the test step.
Attachments
This list is used to attach objects to the test step that affect it.
Instruction Documents
These are test step-related instruction documents. These are used for further processing of the test step.
Active
This option is used to differentiate between test steps that are active and those that can no longer be used.