User Tools

Site Tools


implementation:manufacturing:pdc_qc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

implementation:manufacturing:pdc_qc [2017/06/09 14:39] (current)
csuhaa created
Line 1: Line 1:
 +====== 2.3. Quality Controlling ======
 +Quality Controlling is a manufacturing shop-floor quality control/​assurance data collection function of Produmex Manufacturing. It supports two major processes:
 +  * QC for production order operations
 +  * QA for outsourcing deliveries
 +  ​
 +When a worker reports the (partial) completion of an operation with the PDC system (either via the mobile client or shop floor PDC wizard), a QC officer can report QA data for that operation. The QC officer can qualify an operation as rejected (repairable or un-repairable) or approved. The QA data are stored in a database (in the @BXPQAPARAMSJRNL table), and custom reports can be created by the customers or the partner. Saving QA data to that table is the only result of the quality controlling terminal; any additional steps that should be taken after the quality control process (workflow, repairing job, etc.) should be implemented separately as an addition to the quality controlling terminal.
  
 +When a delivery (Goods Receipt PO) document is created for an outsourced operation, a QC officer can enter QA data for that delivery. Based on the quality qualifications,​ the outsourced operation may be rejected.
 +
 +===== 2.3.1. Set up quality controlling =====
 +In order to set up quality control parameters for an operation, enable the //​’Production Operation Parameters’//​ option on the [[implementation:​manufacturing:​confguide#​pdc_tab|PDC tab]] of Produmex Manufacturing Settings. Next open the Operation Parameter Types form from:  Tools > User-Defined Windows.
 +
 +Here company specific reporting parameter types (dimensions) can be specified. Each operation can have multiple parameter types associated with it.
 +
 +Typically in QA these parameters are some metric of the component worked on or the result of some QC tests. In the following example four parameter types were added, that will cover all the relevant features.
 +
 +{{ :​implementation:​bxmanuf:​pdc:​qc:​operation_parameter_types.png?​direct |Operation Parameter Types}}
 +
 +Based on the value type
 +  * String: Text can be specified freely. Here it is used for a comment parameter type.
 +  * Float, Integer, Boolean: Numeric fields can be used for measurement.
 +  * Valid Values: This type can be used to create a ‘choose from list’ parameter. With a taglanguage,​ the entries in the list can be specified. The syntax is the following: ‘Value in database’:​’Description’|‘Value in database’:​’Description’|… For example in this case Y: OK|N: Defective was specified.
 +  * Date, Time: Date and time is best stored in these types.
 +
 +//Please note: It is not necessary to add timestamp to every operation, as this is automatically collected.//​
 +
 +Next open the Production > Manufacturing Operations form. Here, under the Parameters tab, the used parameters can be specified for each kind of operation. ​
 +
 +In the Type column, the previously defined parameter types can be chosen. \\
 +To use the parameters for the mobile QC terminal the value at the Quality Assurance column has to be set to true. In this example four parameters were specified.
 +
 +{{ :​implementation:​bxmanuf:​pdc:​qc:​qc_opdet.png?​direct |Production order operation details}}
 +
 +===== 2.3.2. Logging in to QC =====
 +Only employees appointed quality inspectors can log into Quality Control.
 +
 +In the next screen the employee can choose between the two mentioned functions: the in-house QC and the outsourced QC.
 +
 +Select the type of the operation on the next screen. Press the ‘In-house’ button to inspect in-house operations, or press the ‘Outsource’ button to inspect the quality of outsourced products. Press the ‘Cancel’ button to go back to the previous screen.
 +
 +{{ :​implementation:​manufacturing:​pdc:​qc:​qc_select_optype.png?​direct |Operation Type Selection}}
 +
 +===== 2.3.3. In-House QC =====
 +On the ‘In-House Operation Selection’ screen enter an operation ID. Choose a work center and the employee who performed the operation. Only operations with at least one PDC booking can be selected.
 +
 +{{ :​implementation:​manufacturing:​pdc:​qc:​qc_ih_select.png?​direct |Select operation}}
 +
 +The system will proceed to the ‘Check Results’ screen. On this screen the quality of the operation can be reported with the previously defined parameters. Add the number of the tested instances to the ‘Checked Quantity’ field. ​
 +
 +{{ :​implementation:​manufacturing:​pdc:​qc:​qc_ih_check.png?​direct |Check results}}
 +
 +To specify parameters, select the parameter from the list and press the ‘Set Value’ button. This will prompt the ‘Set Value’ form.
 +
 +The method for entering the value varies according to the value type of the parameter:
 +  * String: Enter the text to the textbox.
 +  * Float, Integer, Boolean, Date -Time: Add the value to the textbox.
 +  * Valid Values: Select a value from the list.
 +To approve the operation quality, press the ‘Good’ button. \\
 +To reject the operation, press the ‘Rejected’ button. \\
 +To register the operation as repairable, press the ‘Repairable’ button.
 +
 +===== 2.3.4. Outsourced QC =====
 +For more information about outsourced operations please see: [[implementation:​manufacturing:​outsourcing|Outsourced Manufacturing]].
 +
 +The Quality Control of an outsourced operation can be handled by selecting ‘Outsourced’ on the Operation Type Selection form. The procedure is the same as an in house operation with the one exception of the selection form.
 +
 +In the Outsourced Operation Selection window the operation can be specified and then the supplier and the instance of the delivery can be selected.
 +
 +{{ :​implementation:​manufacturing:​pdc:​qc:​qc_os.png?​direct |Select operation}}
 +
 +After this the procedure is the same as introduced in the in-house case.
 +
 +Quality Assurance entries can be seen on: Tools > User Defined Windows > QualityAssuranceJournal
implementation/manufacturing/pdc_qc.txt · Last modified: 2017/06/09 14:39 by csuhaa