SoftExpert SPC general parameters
Prerequisites
- Access to the Configuration > General parameters (SP019) menu.
- Active licenses for other SoftExpert Suite components (PDM, Action plan, Asset, Workflow, Process, and Document) to perform integrations.
Introduction
The General parameters menu centralizes the configurations intended to be applied as default to different records and steps of the SPC (Statistical Process Control).
The definitions previously added in this menu optimize time, as they aid in the specification of characteristics, data collections, event logs, and charts, as well as in the integration of SPC with other SoftExpert Suite components.
See how to add these definitions in SoftExpert SPC:
Configuring the general parameters
1. Access the Configuration > General parameters (SP019) menu.
2. Parameterize the system according to the desired specifications. The following sections are available:
Integration
Use this tab to parameterize the integrations of SoftExpert SPC with other SoftExpert Suite components, such as SoftExpert Asset, SoftExpert Process, and the test method of SoftExpert Document. To do so, select the corresponding components and configure the desired options related to them:
| Parameter | Checked | Unchecked |
Assets - Gage | ||
| Verification must be up-to-date | During the collection execution, only measuring gages whose revisions are up-to-date can be used. | During the collection execution, any gages recorded in the system can be used. |
| Calibration must be up-to-date | During the collection execution, only gages whose calibrations are up-to-date can be used. | During the collection execution, gages whose calibrations are not up-to-date can be used. |
| Gage status must be "in usage" | During the collection execution, the system will not allow the gage to be used if its status is not "in usage". | During the collection execution, the system will allow for associating gages with different statuses besides "in usage". |
Assets - Machine | ||
| Verification must be up-to-date | During the collection execution, only machines whose revisions are up-to-date can be used. | Any machines recorded in the system can be used. |
| Machine status must be "in usage" | During the collection execution, the system will not allow the machine to be used if its status is not "in usage". | The system will allow for associating machines with different statuses. |
Processes | ||
| Integration with SE Process | On the collection planning screen, it will be possible to associate processes, as long as the organization has an active license for SoftExpert Process. | It will not be possible to associate processes. |
Test method | ||
| Integration with SE Document | On the data screen of attribute-type characteristics, the Test method field allows for associating test methods recorded in SoftExpert Document, if the organization has an active license for this component. | On the data screen of attribute-type characteristics, the system allows for importing a document or URL with the test method. |
Characteristics
Use this tab to configure the parameters referring to the control of object characteristics:
Fields | ||
| Analysis team | Select the team responsible for analyzing the characteristic. The team must be created in the SoftExpert PDM component. | |
| Data collection team | Select the team responsible for the characteristic data collection. The team must be created in the SoftExpert PDM component. | |
| Parameter | Checked | Unchecked |
| Control time frequency |
The frequency between collections will be controlled. To do that, select the control type that will be performed: ▪# of samples: enter the number of samples and the time unit that will be used to control the frequency. Example: 3 samples per hour. ▪Interval: enter an interval, that is, how often data collections will be performed. If a data collection is not performed in the defined interval, an event log will be automatically generated to record an occurrence. E.g.: every 1 hour, with a tolerance of (more, less, or more or less) 5 min. |
The interval in between collections will not be controlled through a pre-configured frequency, but, in the Name field, it is possible to describe the desired frequency with which data can be collected. E.g.: every two lots, every box, every change of operator, etc. |
| CMM file configuration |
Import files by: determine which configuration will be applied to the CMM file data collection: ▪Sample: during collections, only the first reading of the sample will be filled out. ▪Reading: during collections, all readings will be filled out in the sample. |
Not applicable |
| Non-conforming measurements | Prevents spelling errors through the definition of an acceptable range for input values. The system will not accept values outside the non-conforming measurements. To this end, enter the percentage considered to be outside the specification. The value that reaches or exceeds the defined variation percentage will receive a system alert during the collection. | The system will allow any value to be entered, without issuing alerts. |
Data collection configuration
Use this tab to configure the Machine, Inspector, Shift, MO, Operator, Gage, Lot, and Date and time fields on the collection execution data screen, defining those that will be enabled for editing and those that must be necessarily filled in.
| Parameter | Checked | Unchecked |
| Enable for editing | The field in question will be enabled for editing. | The field will not be displayed. |
| Required | The field in question must necessarily be filled in. | The field will be enabled, but it will not be necessary to fill it out. |
These configurations will be considered in the creation of new collections. Collections added before the configuration will remain with the parameters that were valid when they were created.
Event log
Use this tab to configure the rules referring to the SPC event log and the charts, as well as to the integration with the component responsible for handling the occurrences found during the collection of characteristic data.
| Parameter | Checked | Unchecked |
| Send e-mail when event log opens | As soon as the event log is generated, filled out and saved, a notification will be sent to the respective responsible user by e-mail. | Notification e-mails will not be sent to the responsible party. |
Integration | ||
| SE Action Plan integration | The occurrences found during the collection will be handled through the Action plan tab of the event log data screen. This tab can be used to record action plans aimed at handling the occurrences in the SoftExpert Action plan component. | The Action plan tab will not be available for the recording of action plans intended to handle the occurrences. |
| SE Workflow integration | Check this field so that it is possible to record, in the Workflow tab of the event log, the occurrences found during the collection or to associate occurrences already added in the system. To do so, the SoftExpert Workflow component must be installed. | The Workflow tab will not be available for occurrence recording. |
- Only one of the integration options can be selected for handling occurrences on the event log data screen.
- The integration can only take place if the respective component is part of the solutions acquired by the organization.
| Parameter | Checked | Unchecked |
Attribute | ||
| Replicate changes | Changed attribute configurations will be applied to all open characteristics in the system. | Open characteristics in the system will not be changed. |
Fields | ||
| Rules for characteristic |
Select and fill out the options that will compose the rules that will generate the event log for the characteristics of the attribute type:
|
|
| Rules for p chart |
Select and fill out the options that will compose the rules that will generate the event log for the p chart:
|
|
The same options are available in the Rules for np chart, Rules for c chart, and Rules for u chart fields. With one of these rules configured, the values can be replicated to another rule through the copy and paste buttons in the upper right corner of the section of each rule.
| Parameter | Checked | Unchecked |
Variable | ||
| Replicate changes | Changed configurations will be applied to all open characteristics in the system. | Open characteristics in the system will not be changed. |
Fields | ||
| Rules for characteristic |
Select and fill out the options that will compose the rules to generate the event log for the variable-type characteristics:
|
|
| Rules for average chart / individual values |
Select and fill out the options that will compose the rules to generate the event log for average charts and individual values:
|
|
The same options will be available in the Rules for range chart / moving range and Rules for standard deviation chart fields. With one of these rules configured, the values can be replicated to another rule through the copy and paste buttons in the upper right corner of the section of each rule. | ||
Event log attribute | ||
|
Default attributes will appear in the event log regardless of the characteristic that is being analyzed. Just as other attributes, they will be presented as additional information, and their values will be inserted in the event log.
See how to associate attributes with the event log:
2. Access the Event log tab and go to the Attributes for event log section. 3. Click on the 4. Fill in the Search field with the data of the desired attribute and click on 5. Locate and select the attributes that will be associated with the event logs in the list of records of the screen. | ||
button. 
.- In the third column of the list of records, the Required field is available for completion. Check this column in the row of the attribute you wish to associate with the event log only if you wish to make it mandatory to insert the attribute value.
- Use the SHIFT key on the keyboard or the check mark next to each item to select more than one record at a time.
- The toolbar also displays the options of checking or unchecking all records, as well as of marking all as required.
Control panel
Use this section to define the general configurations of the data collection and the display of the charts:
Parameterization | |
Fields | |
|
Allow user to omit a characteristic for a sample |
Allows the user to omit characteristics during data collection. In this case, the Skip characteristic button will be enabled during the data collection of both variable-type characteristics and attribute-type characteristics. If this field is not checked, all characteristics must be provided during the collection step. |
| Advanced task period | Allows for defining how many days in advance collection execution tasks will be displayed in relation to the deadline set for their execution. When this number is 0 (zero), the system will not display the record before the execution date. |
Parameterization - General data | |
| Keep general data according to the characteristic configuration | During data collection, general data such as machine, operator and shift will be maintained according to the options selected when the characteristic was configured. |
| Keep general data according to prior sample | During data collection, general data such as machine, operator and shift will be maintained according to the options selected in previous samples. |
|
Keep the general data according to the last read characteristic |
During data collection, general data such as machine, operator and shift will be maintained according to the options selected in the last read characteristic. |
Parameterization - Attribute | |
| Keep the attributes according to the characteristic configuration | The attributes associated in SPC configuration are maintained according to the options selected in the characteristic configuration. |
| Keep the attributes according to the previous sample | The attributes associated in SPC configuration are maintained according to the options selected in the previous samples. |
| Keep the attributes according to the last read characteristic | The attributes associated in SPC configuration are maintained according to the options selected in the last read characteristic. |
Chart view | |
| Number of lines | Enter the number of lines that will be displayed in the collection execution screen. Up to 3 lines can be informed. |
| Number of columns | Enter the number of columns that will be displayed in the collection execution screen. Up to 3 columns can be informed. |
| |
3. After setting all desired configurations, click on the 
button.
Conclusion
The parameterizations will be applied to all system records! Prior definitions ensure uniformity for records, greater control over collected data, and easier integration with other components, promoting a standardized management aligned with the organization's needs.