Defining an Approval Flow

Information

You can quickly reach the relevant topic with the help of navigation on the right side.

Defining Approval Flow User Help Document

1.Approval Flow Identification Process

In all Modules with Qdms, the Approval Flow Definition process is done in the same way. In the approval process, the Role Definition process is performed for the relevant module in the Role definition menu. In the role definition, a user group or a staff member is written in the menu of the SQL queries discovery method field and the approval process is provided to the defined user group or personnel in the flow. Or with the help of the Bimser Support Team, the desired custom role can be written in the SQL Query Discovery Method field and approved in the Role flow written in the SQL query. After the role definition process, the Flow definition process is performed for the relevant Module in the Flow Definition process and the Role defined in the Role definition menu to be used in the flow is assigned in the same menu. In the Flow Definition process, the approval policy is determined by matching the Flow in the Sub-Module of the relevant Module and the operation of the flow phase is ensured. As an example, the process steps of assigning the "DÖF Open Approval" flow to a role of the staff in a role and the "DÖF Open Action Approval" flow to a user Group in the DÖF Module and the operation of the flow will be shown.

1.1.Defining the Approval Flow of the DÖF Module

In the process of defining the Approval Flow, the DÖF module is used in the modules. In the process of defining the approval flow in the DÖF Module, the Role to be used in the approval flow is first defined in the Role definition menu. In the role definition menu, the role to be used as the approval flow is assigned as a user or user group and the information about which role to go to is defined. In the SQL query to select the role definition as a staff member to be assigned the role, the registration number information of the persole is written in quotation marks. For example, for an employee with registration number=bguner, an SQL query is written as follows.

SQL Query for Staff:

SELECT SICIL_NO FROM BSAT001 WHERE SICIL_NO='bguner'

If a Role assignment is to be made as a user group, the Role definition process is done by typing the code of the user group in quotes in the SQL query. User Group For System Administrators For a group of users with Group Code=001, the SQL query is written as follows.

SQL Query for User Group:

SELECT SICIL_NO FROM BSAT009A WHERE GRUP_KODU='001'

After the Role Definition process, the Flow Definition process is done in the Flow definition menu for the flow to be used in the Module. Role assignment is made to be used in defining the flow. After the flow definition process is done, the approval policy is determined by matching the flows in the Sub-Module Definition menu and the approval flow of the module is designed and the approval process is done.

1.1.1.Approval Flow Steps for Personnel Selected Role in SQL Query in Module DÖF

In order to perform the approval flow process steps in the DÖF module, the "DÖF Opening Approval" flow is applied as an example. In order to assign which Role the flow will go to in the DÖF module, first of all, the relevant Role definition process is done for the flow in the Role definition menu. In the role definition process, a staff member is used in the SQL query. To write the SQL query for the Personnel, the Personnel registration number defined in the Personnel Identification menu is enclosed in quotation marks in an SQL query for the flow defined for the DÖF module, ensuring that the approval flow goes to that Personnel.

1.1.1.1.Role Identification

Menu: System Infrastructure Definitions/ BSAT/ Configuration Settings/ Role Definition

The approval flow of the DÖF Module goes to the role definition menu, which is the menu where the "DÖF Open Approval" flow is defined as the information about which role will go as the approver for the approval flows used in the modules for a staff member to go. In this menu, it is possible to define a Role for each module. When you want to change roles or define a new role, support can be obtained from the Bimser Solution Team. The definition of "DÖF Opener" for the Personnel that we define to be assigned a Role in the approval flow is made in the Role definition menu for a role definition.

With the help of the buttons on the screen;

: A new role definition is made.

: Correction / change / update is made for the role definition selected in the list.

: The role definition currently selected in the list is deleted.

: Search by filtering records.

: The data is exported to Excel.

To define the Role with the definition of "DÖF Açan", click ! Clicking the (new) button opens the Define Role/ New Registration screen.

The corresponding fields are defined in the screen that opens:

Module:The area for which the module is determined to select the Defined Role.

Role ID: The field in which the Role ID of the defined Role is automatically assigned by the system.

Discovery Method: The field in which the SQL query for the defined Role is written.

Role Type: This is the area where the role type options are selected in the options such as Personnel, Corporate Customer, Individual Customer, Supplier, and Other.

On the Role Definition-New Registration screen, Corrective and Preventive Actions Module is selected as the Module in the Module section. No role is granted automatically on the system side. The role definition information is written as "DÖF Açan". The Discovery method field is written to the SQL query. Role identification is made for Personnel by typing the registration number of the Personnel defined in the Personnel identification menu in quotation marks in the SQL query. A SQL query for the staff member is made in Role Definition.

Identified Personnel: DÖF Açan

Personnel Registration number: fbas

The SQL query defined for the staff member is written as follows.

SELECT SICIL_NO FROM BSAT001 WHERE SICIL_NO='fbas'

After the required fields are filled, click the ! By clicking the (save) button, the Role definition registration process is performed.

After the Role Definition process, go to the Flow Definition menu where the Flow Definition process will be performed.

1.1.1.2. Defining a Flow

Menu Name: System Infrastructure Definitions/ BSAT/ Configuration Settings/ Flow Definition

It is the menu that contains the definitions of the approval flows used in the modules. To define a new Flow, go to the Flow definition menu. The flow definition for each Module in the system is the available menu

With the help of the buttons on the screen;

: A new flow definition is made.

: Correction / change / update is made for the flow definition selected in the list.

: The flow definition selected in the list is deleted.

: The data is exported to Excel.

To define the Flow named "DÖF Opening Confirmation" in the upper right corner of the screen ! Clicking the (new) button opens the Stream Identification/ New Recording screen.

The corresponding fields are defined in the screen that opens:

Module:** The field for which the module is defined is selected.

Flow ID: The area where the Flow ID of the defined flow is automatically given by the system.

Approver ID: The field in which the approver gives the sequence number of the order in which the approver will give approval.

Must Approve: This is the field that specifies what must be approved. When a user is assigned a role as a group, entering "0" in the Must approve field requires everyone in the user group to approve. Entering "1" in the required to approve field in the user group is sufficient for 1 person in the user group to perform the approval process. "1" is written because there is an approving person for the staff.

Sequence No: The field in which the validator sequence number information is written. Multiple approver assignments are performed. The Sequence No information works in reverse. An assertion of 0,1,2 in the hierarchy continues to be followed by a 2,1, 0 approval sequence first. Confirmation is done so that zero is the final approver.

With the help of buttons on the screen;

: Role added.

: The record currently selected in the list is deleted.

In the Module section, the Corrective and Preventive Actions Module is selected as the Module. Flow No information is given automatically on the system side. The Flow Definition is written as "DÖF Open Confirmation".

When the Add button is clicked, the roles in the role definition are opened. The appropriate role is selected and saved. For example, by selecting "DÖF Opener" defined in the Role Definition, the assignment process is performed to that Role in the "DÖF Open Approval" flow.

Multiple Flow approvers can be defined. On the screen, the sequence number indicates the order in which the approver will give the approval. Hierarchy is done. Sequence numbers such as 0, 1, 2 can be used to come to the last zeroth validator. The SQL defined in the example as Staff is determined so that one person in the query needs to give consent.

After the required fields are filled, click the ! By clicking the (save) button, the Flow definition recording process is performed.

Once the appropriate role for flow identification has been selected, the sub-module definition menu should also be checked. Otherwise, if the definition in the submodule is not appropriate, the flow may not be provided appropriately or the desired flow may not work. After the Flow Identification, the matching process approval policy of the flow is determined in the Definition menu in the submodule.

1.1.1.3.Submodule Identification

Menu Name: System Infrastructure Definitions/ BSAT/ Configuration Settings/ Sub-Module Identification

The flows used for opening, realizing, delaying, closing approvals existing in the modules are introduced to the modules; approval is the menu with which the request, notification and rejection messages are associated. Go to the Sub-Module definition menu to define the approval policy in the Sub-Module of the defined flow.

With the help of the buttons on the screen;

: Correction / change / update is made for the sub-module definition selected in the list.

: The data is exported to Excel.

By clicking the (Modify) button, changes are made to the sub-module identification.

The corresponding fields are defined in the screen that opens:

Submodule No: This is the area where the Submodule Number is automatically delivered on the system side.

Submodule Definition: This is the area where the Submodule Definition is given automatically by the system.

Flow Definition:This is the area where the flow defined in the system can be selected.

Approval Request Message: It is the field where the Approval Request Message can be selected from the message options defined in the system. In the System Infrastructure Definitions/BSAT/Definitions/Message Body Definition menu, Approval Request Message is defined.

Confirmation OK Message: This is the area where the Confirmation OK Message can be selected from the message options defined in the system. In the System Infrastructure Definitions/BSAT/Definitions/Message Body Definition menu, Confirmation Tamper Message is defined.

Approval Rejection Message: It is the field where the Approval Rejection Message can be selected from the message options defined in the system. In the System Infrastructure Definitions/BSAT/Definitions/Message Body Definition menu, the Approval Rejection Message is defined.

If the Approver is the Initiator, the Approval Should Not Be Passed: When the relevant check box is checked, the personnel who enter the data into the system and send it for approval are the approver himself, bypassing the approval process and moving the flow process to the next step.

After coming to the Submodule definition menu, click on the corresponding module definition By clicking the (Change) button, "DÖF Opening Confirmation" is selected as the flow definition, and the associations of approval request message, approval complete message, approval rejection message are made. If the "Do Not Pass the Flow If the Approver Initiates" check box is checked, if the personnel who enter the data into the system and send it for approval are the approvers themselves, they skip the approval process and pass the flow process to the next step.

1.1.2.Approval Flow Steps for User Group Selected Role in SQL Query in Module DÖF

In the DÖF module, the "DÖF Action Opening Approval" flow is applied as an example to perform the approval flow process steps for the User Group selected Role. In order to assign which Role the flow will go to in the DÖF module, first of all, the relevant Role definition process is done for the flow in the Role definition menu. Role definition is done so that a group of users is used in the SQL query. To write the SQL query for the user group, define a user group for the flow defined for the AS module on the User Group menu, and then type the code for that user group in quotation marks in the SQL query to add the code of that user group to that user group.

it's made to go.

1.1.2.1. User Group Identification

It is the menu where the user groups to be used in the system are defined. It provides ease of use in flow definitions. The process of defining a user group for the "DÖF Action Open Confirmation" flow is clicked on the User Group Identification menu.

With the help of the buttons on the screen;

: A new user group is defined.

: Corrections/ changes/ updates are made for the user group selected in the list. Code information cannot be changed.

: Duplicate by copying the user group selected in the list. If the contacts in an existing group will be used again with another group name, the group copy operation is performed with the copy button.

: Group rules are created in various categories. (If HR Integration is available)

: The user group currently selected in the list is deleted.

: Search by filtering records.

: The data is exported to Excel.

: The personnel information within the User Group is exported to Excel.

"DÖF Team Members" is the user group in the upper right corner of the screen to define the ! Clicking the (new) button opens the User Group Definition/ New Registration screen.

After the required fields are filled, click the ! By clicking the (Save) button, the user group identification registration process is performed.

After the User Group definition process, the Role Definition process is done for the "DÖF Action Open Confirmation" flow.

1.1.2.2.Role Identification

After the user group definition process for the DÖF Module, the System Infrastructure Definitions/ BSAT/ Configuration Settings/ Role Definition menu is clicked to go to the role definition menu, which is the menu where the information about which role to go to as the approver for the approval flows used in the modules is defined.

On the screen that opens, click on the top right corner of the screen to define the Role named "DÖF Team Members"! Clicking the (new) button opens the Define Role/ New Registration screen.

On the Role Definition-New Registration screen, Corrective and Preventive Actions Module is selected as the Module in the Module section. No role is granted automatically on the system side. The role definition information is written as "DÖF Team Members". The Discovery method field is written to the SQL query. Role definition is made for the user group by typing the group code information of the user group defined in the User Groups Definition menu in quotation marks in the SQL query. A SQL query for the group is made in Role Definition.

User Group Defined: DÖF Team Members

User Group Code:DF.001

SELECT SICIL_NO FROM BSAT009A WHERE GRUP_KODU='DF.001'

After the required fields are filled, click the ! By clicking the (save) button, the Role definition registration process is performed.

After the Role Definition process, go to the Flow Definition menu where the Flow Definition process will be performed.

1.1.2.3. Defining a Flow

To define the "DÖF Action Opening Approval" Flow, click on System Infrastructure Definitions/ BSAT/ Configuration Settings/ Flow Definition menu.

On the screen that opens, click on the top right corner of the screen to define the Flow named "DÖF Action Opening Confirmation"! Clicking the (new) button opens the Stream Identification/ New Recording screen.

With the help of buttons on the screen;

: Role added.

: The record currently selected in the list is deleted.

In the Module section, the Corrective and Preventive Actions Module is selected as the Module. Flow No information is given automatically on the system side. The Flow Description is written as "DÖF Action Opening Approval".

When the Add button is clicked, the roles in the role definition are opened. The appropriate role is selected and saved. As an example, by selecting "DÖF Team Members" defined in the Role Definition, role assignment is performed to the "DÖF Action Opening Approval" flow.

In the example, the user group is set to "1" in the Must approve field, which is sufficient for someone in the group to give approval. If "0" is written in the field that must be approved as a user group, all the people in the group must approve.

After the required fields are filled, click the ! By clicking the (save) button, the Flow definition recording process is performed.

Once the appropriate role for flow identification has been selected, the sub-module definition menu should also be checked. Otherwise, if the definition in the submodule is not appropriate, the flow may not be provided appropriately or the desired flow may not work. After Flow Identification, in the Definition menu in the Submodule, the approval policy is defined, which is the matching process of the flow.

1.1.2.4.Submodule Identification

To set the approval policy of the "DÖF Action Opening Approval" flow, click on the System Infrastructure Definitions/ BSAT/ Configuration Settings/ Sub-Module Definition menu to go to the Sub-Module definition menu.

By clicking the (Modify) button, changes are made to the sub-module identification.

After coming to the Submodule definition menu, click on the corresponding module definition By clicking the (Change) button, flow definition, approval request message, approval okay message, approval rejection message associations are made. If the "Do Not Pass the Flow If the Approver Is the Initiator" box is checked, if the personnel who enter the data into the system and send it for approval are the approvers themselves, they skip the approval process and pass the flow process to the next step.

"DÖF Open Approval" and "DÖF Action Opening Approval" in DÖF Module The infrastructure definitions to display in the DÖF Module for the operation of the flow setup, which are the DÖF Root Cause, DÖF process Source and Nonconformance Categories Identification processes are defined in the System Infrastructure Definitions section in the DÖF Module. After these definitions are made in the infrastructure, a new DÖF record is opened in the DÖF Operations menu by going to the Integrated Management System section to open a new DÖF record.

1.1.3. How Approval Flows Work in the DÖF Module

1.1.3.1.DÖF Operations

It is the menu where a new Döf record is opened and the opened Döf records are listed. To go to the DÖF Operations menu, click on the Integrated Management System / Corrective and Preventive Actions / DÖF Operations menu.

With the help of the buttons on the screen;

: It is the button used when entering a new DÖF into the system.

: Used to make changes to an existing record if there is authorization.

: Used to display all the information of any OF.

: If there is a Customer Complaint related to the selected DÖF, it will be taken to the relevant record.

: It is the registry maintenance button used for corrections in the DÖF detail.

: It is the button to be used if you want to delete the DÖF Record. It appears in System Administrators. It is not visible to edge users.

: It is a parametric button and appears on the System Administrators screen. Used to cancel LAFs. It is a different process than deletion. The operation of the DÖF stops, but the system continues to be registered. It works within the framework of an approval flow. For this, it is necessary to define the flow in the infrastructure. (To determine which role will approve or reject the DÖF records to be canceled, go to the SAT/ BSAT/ Configuration Settings/ Flow Definition menu. DÖF Cancellation Confirmation Flow ! Connects to the role with the button.)

: It is the button that allows to print according to any stage of the DÖF. To which stage the report is desired to be taken, by making a choice! Click the (Print) button. The report for the selected record is pulled to the computer.

: It is the button used if we want to output the DÖFs as Excel.

: It is used when you want to make selections from the Search tab and filter.

To Open the New DÖF Registration Clicking the New button will bring you to the DÖF Transactions / New Registration screen.

On the DÖF tab, under the DÖF Detail heading, the process source, the department where the nonconformity is, the workplace, the definition of nonconformity, the nonconformity detail and the nonconformity category are determined. If desired, the personnel to be added to the information are selected from the relevant management system list from the management systems drop-down menu after the workplace, process and item number are selected.

If parametric fields have already been created for the DÖF Module, these fields are filled in by switching to the Detail Information tab.

If not, the DÖF Solution Team is defined by clicking the Solution Team tab. On the DÖF Solution Team screen, the solution team leader and the responsible department are selected. Team members are selected from the staff list. In addition, the deadline for writing the Progress Report is determined.

By switching to the Additional Files tab, it is possible to add the desired files in formats such as document, audio, image etc. to the DÖF record if desired.

When saved with the Save button, if a flow is set up for the approval of the DÖF opening, the Team Leader is tasked with writing a Progress Report if it is not set up for the approval of the relevant role. After the new DÖF is entered When you press the (Save) button, the system sends the new record for approval.

The approver had identified it as the "DÖF Opener" Role in the Role definition. The SQL Query defined for Staff for this Role was written as SELECT SICIL_NO FROM BSAT001 WHERE SICIL_NO='fbas'. Since the registration number of the personnel who are Furkan Baş in the Personnel Identification menu is "fbas", the DÖF record is sent to this user for approval. While the system sends an e-mail to the person in the approval, it is also displayed that it has dropped the work in the form of "Pending Approval DÖF list".

1.1.3.1.1.DÖF Confirmation

After the DÖF is sent for opening approval, the person concerned comes to the Pending Works and sees the DÖF that he will approve to open under the name of "Pending Approvals" List. Clicking on the DO ID displays the list of Pending Approval ODs.

With the help of the buttons on the screen;

: Used when you want to view the corresponding DO record.

: It is used if it is requested to make changes with the relevant DÖF record. If the request is a DÖF, the system will not allow us to make the approval process without filling in the required fields.

: Used to perform the DÖF confirmation process. After approval, the relevant OF record is placed before the Team Leader.

: If the information entered in the DÖF is not appropriate, it is used to reject the DÖF. The rejected can be sent to the person who opened it with the reason for rejection. When refusing can be rejected for detailed information rejection or cancellation of registration, you should select the corresponding option accordingly.

: The confirm button is clicked. The DÖF registration is approved by writing a confirmation note.

1.1.3.1.2.Progress Report

After approval, it falls to the pending work of the Team Leader to write a progress report. The team members/ team leader will come to the Pending Jobs tab and click on the relevant OF NO under the "List of Progress Reports to Write" tab to the screen with the DÖF information.

The team leader shall indicate the immediate measures taken and the progress of the work of the DO in the Progress report. If the DÖF clicks the Save the Finalization time by attaching the attachment file if you have your team, the next stage is passed

The Progress Report is saved with the Save button.

1.1.3.1.3.Root Causes

After the progress report is written, the Root Causes tab is active. You will be brought to the Root Cause Analysis screen.

With the help of the buttons on the screen;

: It is the button used to add a new root cause.

: It is the button used if you want to make changes or updates to the root cause entered.

: It is the button used to delete the root causes entered incorrectly.

Clicking the New button brings you to the root cause add screen.

: It is the button used to add the root cause analysis report file to the system.

On the screen that opens, the desired root causes are selected and the description information is entered. Afterward! By clicking the save button, the root cause is recorded and the relationship with the DÖF is established.

1.1.3.1.4.Actions

After the root causes are determined, the process continues with the planning of the DÖF Actions. The Actions tab is brought down. Here, the actions to be taken regarding the DÖF are planned and assigned as work.

With the help of the buttons on the screen;

: It is the button used to add a new action.

: It is the button used to see the content of the action.

: It is the button used if you want to make changes or updates about the action entered.

: The button used to copy the action.

: Button to export the action list to Excel.

: This is the button used when we want to delay the deadline of the planned action.

Clicking the New button brings you to the Actions-New Recording screen.

On the screen that opens, the person responsible for the action and the person who will perform the action are selected from the list, the action information is entered, the planned end date of the action is determined, standard item numbers related to the action can be added, reference documents and root reasons, if any, related to the action are added. Again, if desired, additional files, documents, etc. related to the Action can be added from the Additional Files section.

After the action information is entered! With the (save) button, the action is planned and sent to the person who will do the work as an information via e-mail.

The approver had identified it as the "DÖF Team Members" Role in the Role definition. The SQL Query defined for the User Group for this Role was written as SELECT SICIL_NO FROM BSAT009A WHERE GRUP_KODU='DF.001'. Because the code of the user group that is "DÖF Team Members" in the User Group Definition menu is "DF.001", the "DÖF Action Opening confirmation" flow is sent to the people in this user group for approval. While the system sends e-mail to the people in the approved user group, at the same time the pending jobs are in the form of "List of DÖF Actions Pending Opening Approval". Since the flow definition is set so that it is sufficient for 1 person in the user group to approve, when 1 person approves, the flow process continues at the other stage. Any 1 person in the "DÖF Team Members" group, which is a user group, is selected and approved.**

It is displayed in the action list and the task "List of DÖF Actions Pending Opening Approval" is dropped in the Pending Jobs of the people who will perform the action.

Pending Jobs are clicked on DÖF-Action No by coming under the DÖF Actions List Waiting for Approval. The Döfler Pending Approval screen is reached.

With the help of the buttons on the screen;

: Used when you want to view the corresponding DO record.

: Used to confirm the DÖF Action Open. After approval, the relevant OF record is placed before the Team Leader.

: If the information entered in the DÖF is not appropriate, the DÖF is used to reject the approval to open the action. The rejected can be sent to the person who opened it with the reason for rejection. When refusing can be rejected for detailed information rejection or cancellation of registration, you should select the corresponding option accordingly.

: The confirm button is clicked. A confirmation note is written and the "DÖF Action Open" registration is confirmed.

It is displayed in the action list and is specified under the "Actions to be Performed" list in the Pending Jobs of the person who will perform the action.

From Pending Jobs, click on DöF-Action No by going under the DöF Actions List. The DÖF information screen is reached.

You will be brought to the Action tab. (Perform action) button will be used to enter Action Execution Information. On the Performing Action screen, the information about the action being performed and the date of execution are entered. In addition, if desired, additional files can be added to the action execution phase.

On the Performing Action screen, the information about the action being performed and the date of execution are entered. In addition, if desired, additional files can be added to the action execution phase. After the work done and the additional file, if any, is added! When we click the (save) button, it is sent to users for confirmation to perform an action.

Related persons are deducted from the Pending Jobs as "Pending Realization Approval DÖF Actions List".

From the Pending Jobs, go under the "DÖF Actions List Pending Realization Approval" and click on DÖF-Action No. The Döfler Pending Approval screen is reached.

With the help of the buttons on the screen;

: Used when you want to view the corresponding OF OD record.

: Used to perform DÖF Actions Awaiting Execution . After approval, the relevant OF record is placed before the Team Leader.

: If the information entered in the DÖF is not appropriate, it is used to reject the approval of the DÖF Actions Pending Fulfillment . The rejected can be sent to the person who opened it with the reason for rejection. When refusing can be rejected for detailed information rejection or cancellation of registration, you should select the corresponding option accordingly.

The Confirm button is clicked. A confirmation note is written and the "DÖF Actions Pending Realization Approval" record is approved.

1.1.3.1.5.Final Report

After the actions are planned and carried out, the process continues with the writing of the final report. The Team Leader/Member comes to the Pending Jobs and sees the relevant DÖF under the "List of DÖFs to be Written Final Report" tab and clicks on the DÖF number to the screen with the DÖF information.

The final report is a report that includes the final measures taken regarding the DÖF and the solution proposals. It is the final report prepared for the person who will give the Closure approval as a summary of all the transactions made during the DÖF Transactions.

On the screen that opens, the Final Report is written. Additional files that are desired to be included in the Result Report can be added. Afterward! With the (save) button, the Final Report is saved and the DÖF goes to the closure confirmation.

Once the process of writing the final report has been recorded, the predetermined DÖF will be assigned to the closure officer as "List of DEPs to be Closed"** as their pending work.

1.1.3.1.6.Shutdown

Displays the relevant DEP under the "List of EAFs to Close" tab.

Clicking on the DO number brings up the "Pending Approval ODs" screen.

With the help of the buttons on the screen;

: It is the button used to display all information about the DF.

: When the person who will approve the closure decides that the actions taken are not sufficient, it is the button used to identify the missing actions.

: It is the button used when it is desired to be given the task of writing a report by monitoring the adequacy, effectiveness or proper performance of the actions taken by a different person.

: It is the button used for filtering the DÖFs to be approved for closure

Clicking the Shutdown button brings you to the Closing the DÖF screen.

On the screen that opens, qualification information is entered. In addition, additions can be made to the nonconformance category field if desired. Again, if desired, additional files can be added to the shutdown phase. After the required fields are filled in! By clicking the (save) button, the information is saved and the DÖF is turned off.