1    Configuration of the "Read from database" dialogue

This document describes the options that can be configured via the "Read from database" dialogue. The available options are a sub-set in the database configuration dialogue "Options".

Configurations in the "Read from database" dialogue

Dialogue "Options" in
File | Configurations | Databases | Options (Database configuration).

Most of the options can be configured directly in the "Read from database" dialogue (assuming the necessary authorisation):

Some options can only be configured by a database administrator with the user group right "database administration" and per measured value database.

This document explains which options this applies to.

It has been written for the "process capability analysis" module. Separate chapters deal with the special features of other modules.

This document gives instructions on how to use the individual options and how to allocate configurations. In order to improve clarity and comprehensibility, some options are described in separate FAQ documents. A link is provided where a FAQ document exists for them.

1.1     "Display" Menu

1.1.1     Expand "All parts" immediately

If this option is selected, the tree under "All parts" is automatically expanded when the "Read from database" dialogue is opened, and the "maximum number of parts" is displayed. This is also the case when a filter is applied.

This may be convenient for a small number of parts. However, if the amount of data increases, it is recommended not to use this option and instead to expand the tree manually after filtering has been completed:

1.1.2     Expand parts with subordinate test plans immediately

If this option is selected, the subordinate test plans for parent-child structures are automatically expanded in the "Part selection" window.

Without this option, only the master test plans are shown.

1.1.3     Maximum number of parts

The number specified here is displayed when the tree "All parts" is expanded. If more parts are available, you will be asked whether all or x number of parts should be displayed. If you select "Yes", x number of parts will be added to the view, if you select "All", the tree will be expanded completely, and all parts will be displayed.

1.1.4     Takeover last filter configuration

When this option is selected, the filter (Quick filter or Simple filter only) that was open the last time the dialogue was closed is applied again.

1.1.5     Display fields as table

All K fields configured for this window are displayed in the part selection. By default, these are the K fields K1001, K1002 and K1004.

If this option is not selected, all fields per part are displayed side by side in a space-saving but confusing manner with "/" as a separator:

With the option selected, the information is displayed as a table. The longest entry of a K field defines the width of the column.

1.1.6     Open data directly

This option determines how previously saved Quick filters are opened. When it is selected and a saved Quick filter is opened, it is no longer first shown through the "Read from database" dialogue. Instead, the entire filter result is loaded directly.

1.1.7     Show preliminary selection for "Select values"

This option affects the function "Select part values" and the options in the dialogue "Select values":

When this option is deactivated, alphanumeric additional data fields will NOT be listed in the "Select values" dialogue (i.e., they will no longer be read from the selected data set); in the case of catalogue-based additional data, all entries available in the catalogue will be listed, regardless of whether the selected data set contains this additional data. In the following example, the data set with part number "4711" has three different entries in the additional data field "Cavity" and seven different entries in the additional data field "Machine".

Without the option set, all catalogue entries are shown.

With the option set, only those entries are shown which are also contain in the marked data set. For machine (K0010), entries were also recorded that are not in the catalogue (entry 33). This is also shown because its not listed in the catalogue; however, it is only listed as a running number.

1.1.8     Highlight filtered parts

By default, no parts are highlighted after a filter has been applied; they have to be highlighted manually to be opened. With this option set, all parts that match the filter criteria are highlighted after a filter has been applied and can be loaded directly:

1.1.9     Parts in queries are selected by default

If this option is set, all parts of the query are automatically marked for loading when queries are expanded.

1.1.10  Select characteristics by default

If this option were deactivated, the characteristics of a data set would be disabled after highlighting it:

After selecting a test plan, the user can then select the desired characteristics manually:

Only the characteristics marked with the green tick will be loaded:

1.1.11  Filter types selection

Only a database administrator, i.e., a user with the user group right "database administration", can restrict filter levels in database options. Especially when the amount of data increases, it is recommended to deactivate the simple filter for users:

It is then no longer available.

1.1.12  Show hints for part and characteristic fields

Without this option, only part information is highlighted when hovering over a part:

With this option, the part information is shown in tabular form and displays the K field information in the form of hints:

1.1.13  Highlight parts with changed tolerance limits

Even without an amendment history enabled, changes to specification and control chart limits are logged in the database. If this option is set, it is possible to see which part has already had such changes of limits:

1.1.14  Highlight parts with own window lists

For each data set, a window layout that deviates from the standard can be saved. With this option enabled, an additional icon is displayed for data sets with their own window layout:

1.2        Load" Menu

This is one of the most important options that can be set for user groups. Whether a user can edit a data set after reading it is defined within this section. In a properly set up data flow system, it can be important to remove the authorisation to change data from "regular evaluators". There are three options to choose from:

         Read data only

         Data editable but not storable

         Data editable and storable

The main option fields determine which mode is preselected as default in the "Read from database" dialogue.

With the sub-options, editable and storable data can additionally be offered to users for modes with limited functionality. When selecting a sub-option in the "Read from database" dialogue, it is only valid for the current loading process; it is selected temporarily, so to speak. The next time the "Read from database" dialogue is loaded, the main option is preselected.

1.2.1     Read data only

If the option "Read data only" is selected, the test plan is displayed write-protected, and it is not locked in the database.

After highlighting a test plan, the set option is also visible in the dialogue:

1.2.2     Data editable but not storable

The option "Data editable but not storable" is a special case.

It is shown in the "Read from database" dialogue:

The loaded data set can be edited:

If, however, the data set is then saved with the standard option "Save",

you will be asked for a file name, because saving does NOT involve re-saving the original data set; instead, a copy is saved:

If "Save to database" were activated as default in the saving options, a copy of the data set would be saved to the database:

This option should therefore only be set if the initial saving of a new data set is configured to be "file-based" in order not to create copies of the data pool in the database. Rather, the purpose of this option is to create a copy of an existing data set for further editing where its data should not falsify the original data set in the database.

1.2.3     Data editable and storable

The option "Data editable and storable" is set by default.

This allows the user to edit and save an open data set. For users in the field of data recording (procella), this is of course a basic requirement. When evaluating, however, this has the consequence that the evaluator locks the data set in the database for other users.

1.2.4     Using sub-options

If the additional option "Activate editability, if required" is selected,

the user can activate the 2nd option temporarily (for this loading process) in the Read from database dialogue.

If the option "Function to restore data may be activated, if required" is set additionally (or on its own),

then this option is also (or only) available to the user for temporary activation (for this loading process):

1.2.5    Reset "Read data only" manually

If data is loaded from the database with the "Read data only" option, but the person responsible subsequently has to make a change to the data, the entire data pool does not have to be reloaded. The "read data only" mode can be cancelled retrospectively.

A data set is loaded with "Read data only":

In the course of analysis, however, it becomes clear that the data set needs to be modified. The "Read data only" setting can be cancelled by clicking "Release loaded data for storage". The part is locked in the database for this user and saving back to the database is allowed.

1.2.6     Differencing (2 parts)

With this option, the differences between two parts with exactly the same number of characteristics and measured values can be determined. The basic prerequisite is the same number of characteristics, characteristics in the same sequence, and the same number of measured values.

As an example, the parts with part numbers "4711" and "4712" from the standard database have been reduced to three characteristics:

If these two parts are loaded with the "Differencing" option set, a virtual third part is added:

The measured values of the third part are a combination of the values of part 1 values of part 2:

The specification limits of the virtual difference part are converted in the same way as the measured values; the tolerance zone is doubled.

The order of calculation (part A part B) is not done by the highlighting of parts, but according to the sequence in the part selection. Upper part lower part:

If the formula is to be reversed, the sort order of the parts must be reversed:

1.2.6.1      Sub-option "Calculation of absolute value"

With the sub-option "Calculation of absolute value", instead of doubling the tolerance zone, the original tolerance width is used as the upper specification, and 0 as the lower specification with a natural boundary.

1.2.7     Group parts

This option is described in a separate FAQ document, "Group parts".

1.2.8     Show superordinate test plans even if only subordinate test plans meet filter conditions

This option is described in a separate FAQ document, "Subordinate test plans".

1.2.9     When superordinate test plans are opened, automatically open all subordinate plans and combine into one test plan.

This option is described in a separate FAQ document, "Subordinate test plans".

1.2.10  When double-clicking a part the data will be loaded

Without this option, parts are no longer loaded by double-clicking, but only highlighted. Data can only be loaded by clicking "OK" after selecting them.

1.2.11  Reducing database fields

Reducing the database fields can increase the performance of the software. Unused fields from the database are no longer read while loading.

Database fields can only be created by users with the user group right "database administration":

In this example, a new list "reduced_list_01" is created. K fields K1004, K1005 and K1007 are removed:

Reduced field lists can also only be selected in the database options and not directly in the "Read from database" dialogue:

The reduced field list has NO influence on the display of the part selection when "reading from the database". Here, for example, K1004 is still shown:

When loading a data set, however, it is no longer populated.

1.2.12  Only load the test plan containing the latest measurement

This option means that regardless of the selected number of parts, whether via queries, filters or manual selection, only the test plan with the latest measured values is loaded.

As an example, all parts of a test database are highlighted:

After the software has determined the most current value, it loads only this test plan:

The option is usually of little significance. However, for queries / online updates it can be used to show the most recent test plan currently in production.

1.3     "Load (characteristics)" menu

1.3.1     Load all characteristics deactivated

With this option, all characteristics are in a deactivated state when the data set is loaded:

If inactive characteristics are to be evaluated subsequently, they can be activated for evaluation via the parts / characteristics list:

The activated state of a characteristic is only valid while the data set is loaded, i.e., it is temporary and not saved back to the database. The entire data pool is loaded while evaluation is limited to the active characteristics. There are hardly any performance advantages. Therefore, this option is not recommended. In this case, it would make more sense to filter the data pool beforehand.

1.3.2     Do not load deactivated characteristics

Sometimes characteristics are deactivated in test plans and the inactive state is saved. Reasons for this could be characteristics that are no longer included in the measurement and are no longer tested or measured, and which should be excluded from the evaluation.

If such deactivated characteristics are contained in the database, this option causes them not to be loaded. They are also highlighted as not to be loaded in the characteristics selection:

Only the active characteristics are loaded.

1.3.3     Automatically load superordinate characteristics

Superordinate characteristics include all characteristics that have been grouped in some way, such as position tolerances:

If a filter would now only find subordinate axes,

loading a position tolerance without the superordinate characteristic would falsify the evaluation:

With this option set, the superordinate element is automatically loaded, even though this characteristic does not meet the filter criteria.

1.3.4     Automatically load subordinate characteristics

A reverse example is when only the position deviation amount is filtered:

This option causes the subordinate characteristics, here the axes, to be loaded automatically as well:

1.3.5     Load subordinate characteristics only if their superordinate characteristics or groups are loaded as well

Consider a data set with groups:

The group name "Group_01" is filtered:

Only the group that matches the filter criteria is loaded. All other characteristics are also loaded, but without the existing group allocation:

If this option is selected, the characteristics to which the filter does not apply are neither listed in the "Read from database" dialogue nor loaded:

1.3.6     Open characteristics only if they contain at least x measured values

With this option, characteristics are not loaded if they have less than a chosen number of measured values. This example shows a part which has only 10 measured values for some characteristics:

The option is set to load only characteristics with at least 11 measured values.

As the number of measured values is still unknown in the characteristics selection, these characteristics are still displayed in the "Read from database" dialogue.

Once the number of existing values has been determined, however, they are not loaded:

1.3.7     Load groups only if they contain subordinate characteristics

In the above example, a group without characteristics was loaded. To prevent this, empty groups are not loaded when this option is selected:

1.3.8     Only load parts if they include characteristics or groups

Depending on the type of filter, it can happen that parts which are opened no longer contain any groups or characteristics. This option can be used to avoid opening empty parts without characteristics.

1.3.9     Automatic selection

This option is described in a separate FAQ document, "Automatic selection".

1.4     "Load (measured values)" Menu

1.4.1     Complete series of measurements based on

The option "Complete series of measurements based on" makes it possible to search for an item "A" in the database at the value level, to list an item "B" within the additional data of this data pool, and to load all values of the corresponding characteristics although they do not correspond to criterion "A".

A practical example, which was also the reason for this development:

Take a data set with 6 characteristics and 95 measured values for each.

In additional data, the subgroup ID K0080 and K0081 are included due to collection with procella. Occasional events were entered due to alarms occurring:

Now the following requirement existed: only the values with events should be opened.

Only characteristics with measured values for which at least one event has been recorded are opened:

However, the following problem was detected: The software assumes a sample size of 5. But the measured values are now mixed across different samples:

With the option "Rearrange subgroups (K0080, K0081)" under File | Configurations | General Settings | General Settings 2, the subgroups can be subsequently sorted and neatly displayed in the value mask:

Due to the missing measured values, i.e., the incompletely loaded measured value series, information is also missing from the QCC. If the QCC did trigger an alarm, it would not give the reason for the triggered event.

If the option "Subgroup ID (K0080)" is also activated, the measured value series are also loaded based on the subgroup ID when a data set is opened.

Thus, all measured values whose subgroup ID was found in the filtered data pool are now reloaded:

1.5     "Sort" Menu

1.5.1     Sort parts

1.5.1.1      Sort displayed parts in descending order

In part selection, parts are sorted alphanumerically by the displayed fields. With this option, the part selection can be sorted in descending order.

1.5.2     Sort characteristics

1.5.2.1      Load characteristics in original sequence

The following options concern the sequence of characteristics. The default setting is "Load characteristics in original sequence". This is the order in which the characteristics were initially created.

1.5.2.2      Takeover changes to the characteristics sort sequence made by the user (reading and saving)

A common problem is the subsequent insertion of a characteristic into the data set. If a characteristic is inserted between two existing characteristics in a test plan that was taken from a DFQ file, it is also physically inserted at this position in the DFQ file. When reading from the database, an inserted characteristic always appears at the end, i.e., it would not be at the position that the user intended.

This is what the option "Takeover changes to the characteristics sort sequence made by the user (reading and saving)" is for.

The sequence created by the user is also saved to the database and therefore read again.

Using the additional option "Quick characteristic sorting by drag & drop", a shift of structure can be carried out directly in the "Read from database" dialogue in characteristics selection:

1.5.2.3      Sort down characteristics after the displayed fields

With these two options, characteristics can be sorted in ascending or descending order in the "Read from database" dialogue via the "characteristics selection" window

The sorting order is alphanumeric according to the displayed fields. By default, these are characteristic number (K2001) and characteristic description (K2002).

As an example, K field K2005 (characteristic class) is shown for a data set with groups in the "Read from database" dialogue and placed at the beginning:

The data set contains groups. The group structure is not changed; sorting is done per group:

1.5.3     Sorting measured values

1.5.3.1      Sorting

With the sorting option, the filtered data pool in the measured value area can be sorted according to additional data criteria. There are 3 levels to choose from, and each can also be sorted in descending order:

In this example, the date of the fifth last measured value is changed to the year 2017, the rest of the data is from 2018:

Then the last 10 measured values are filtered. The option "Sort by date/time" is enabled.

Up to approx. version 10, the measured value with the date of 2017 was included in the loaded data pool, then sorted. In the new versions, the software recognises that the order of the values in the database does not correspond to the chronological order when the filter "last n values" is set and the sorting option is set according to date and time. First the content of the data set to be loaded is sorted and then the last x values are loaded. This ensures the chronological order.

If you choose to sort in descending order, the data pool of the database is first sorted in ascending order, then its last x values are filtered and displayed in descending order.

1.5.3.2      Sort and fill in by serial number

With these options, data sets can be sorted in the correct rows across all characteristics by using an additional data field with a unique serial number.

Two data sets are used as an example for the following options:

To optimise the presentation, the measured values are equal to the additional data.

1.5.3.2.1     Field used as serial number:

After enabling "sort and fill in by serial number", it is necessary to specify in which K field at the additional data level the unique identifier is located. The database key (if the part measurement was used in the Q‑DM upload) or all alphanumeric additional data fields that are active in the database (except K0080/K0081 due to their special use) can be selected:

If the first data set is opened in one of these ways, the values are sorted by serial number (here: K0006), line by line, and all gaps are shown:

Special feature of the result in characteristic 2:

         The missing batch number "001" is represented by a placeholder.

         The repeating batch number "002" is only displayed for the first value found.

1.5.3.2.2     Apply last found information when the information occurs several times.

This option can be set if repeat measurements have been made and the last existing value per serial number is to be used.

If the first data set is loaded using this option, the last value is displayed for the repeating batch number "002" in characteristic 2.

Special feature of the result in characteristic 2:

The missing batch number "001" is represented by a placeholder.

The repeating batch number "002" is only displayed for the first value found.

1.5.3.2.3     Complete additional data for empty measured values

By default, gaps which are then displayed, do not contain any additional data. With this option, the empty value fields also get the same serial number, which helps with the display in reports and the analysis of missing values:

1.5.3.2.4     Sort and fill in across part limits

Sometimes the same part type has several test plans in the database. This could be various different measuring sites, production locations, and the like.

This option can be selected if more than 1 part is loaded and the sorting by serial number is to be done for all loaded parts. As an example, both parts are loaded together with this option:

The filling of empty additional data fields is only done for each part.

1.5.3.2.5     Sort values subsequently after the following additional data field

If the alphanumeric sorting of the serial number does not show the desired order of the values and another field is to serve for sorting, this can subsequently be activated here. This option only becomes active when "Complete additional data for empty measured values" is also enabled.

The default sorting for measured values, as described in chapter Sorting, no longer applies.

1.6     "Numerical Sorting" Menu

The contents of alphanumeric fields are normally sorted alphanumerically. However, if the alphanumeric fields only contain numeric contents, the required field can be configured for numeric sorting.

In this case, the user must be sure that there really are only numeric contents in the alphanumeric fields.

A frequently used example is the characteristic number. Consider a standard data set from the database, characteristics 1 to 15, numbered in the same way in K2001:

Now the option to sort after the displayed fields is used (see also chapter "Sort" Menu):

Number sorting is alphanumeric and results in the following:

By adding leading zeros in K2001, alphanumeric sorting can be used to sort numbers in numerical order.

In the following example, characteristics "1" and "2" are renamed "01" and "02":

K field K2001 (characteristic number) is defined for numerical sorting:

Now the sorting order of the characteristics corresponds to the numerical sorting of the numbers 1 to 15:

1.7     "Filter" Menu

1.7.1     Settings for simple filters and Quick filter

These options concern working with the simple filter and the Quick filter. They are described in a separate FAQ document.

1.7.2     Apply value filter from "Select values for all parts" to parts

This option applies to the function "select values for all parts" and the filtering of additional data configured in the "Select values" dialogue.

If the function "Select values for ALL parts" is used:

And a filtering of additional data is selected:

This has no influence on the data sets that are listed in part selection by default:

When this option is used, the data sets in the part selection window are filtered directly and the listing is limited accordingly:

1.7.3     Shifts

Only a database administrator, i.e., a user with the user group right "database administration", can create shifts in the database options.

Shifts can be used with various filters to separate the measured values of the shifts and evaluate them individually.

After entering the first shift number, the shift start, and shift end are filled automatically in advance.

The shift start can subsequently be adjusted. The shift end can NOT be edited (for the time being):

After entering the second shift, the end of the first shift is taken over as the start of the second shift (one second later):

The start of the second shift defines the end of the first shift:

This approach ensures that all 24 hours are included.

1.7.4    Filter of the Configurationuser

These two options are explained in the FAQs on filters. They can only be set by the ConfigurationUser in database options.

         Filters of the ConfigurationUser are usable by all users

         Quick filters stored by the ConfigurationUser are also available to all users.

1.7.5    Behaviour of a filter when you drag & drop it on a selection or when you (de)select characteristics

This option is explained in the FAQs on advanced filters and queries.

2          Configuration deviations in different Q-DAS products

The configuration of the "Read from database" dialogue described in this document mainly refers to the application in the qs‑STAT module Process Capability Analysis.

The functions and options available for the configuration of the "Read from database" dialogue may differ in other Q-DAS products and modules.

2.1        Special feature in the Q-DAS Q-EMPB (ISR) product

The following options are main differences between Q-EMPB (ISR) and qs-STAT Process Capability Analysis.

         Open file directly
Not available in Q- EMPB (ISR).

         Show preliminary selection for "Select values"
Not available in Q- EMPB (ISR).

         Differencing
The two options for differencing are not available in Q- EMPB (ISR).

         Display ISR only
Only available in Q- EMPB (ISR). The option "Display ISR only" is located in the Load tab. With this option, only data sets that have actually been opened in the ISR module and that are linked to an ISR version are displayed.

Special features in the Q- EMPB (ISR)"Field Selection" menu

2.2     Special feature in the Q-DAS product solara.MP

Various options are also unavailable in Q-DAS solara.MP (measurement system analysis). Basically, its the options that could change the order of measured values. This is because the order of measured values is of fundamental importance in measurement system analysis.

It applies especially to the menu items "Load" and "Sort". The following example compares the "Load" menu item in qs-STAT process capability analysis with solara.MP