--- alias: user-guide-rework-material description: "This documentation outlines the process of sending material to rework, including preconditions, steps, and associated data collection and checklist procedures" --- # Rework Material :lock: Material.**Rework** :lock: Material.**ReworkOverride** ## Overview This transaction is used to send **Material** to Rework. When a **Material** is send to Rework, once the Rework is complete, it returns to a pre-defined processing point in the **Material** current **Flow**. The decision to rework a **Material** is normally the result of an inspection in metrology steps, test results or quality gates. ## Setup No special setup is required other than to meet the preconditions of the transaction. Remember that there must be at least one Off-Flow Reason applicable to Rework for the Current **Material** Step and a Rework path defined for the **Material** Flow Path. For more information on how to create a **Flow**, refer to the [[user-guide-flow-index]] section. ## Preconditions * **Material** is Active, is not In Transit and not On Hold. * The **Material** is not On Hold and not In Transit. * The Experiment Lock Id of the **Material** is empty or set to Track-In. * The **Material** State is Processed or Queued. * The new Flow Path must be valid. * There is a next **Step** defined for the **Material** in the current **Flow** and the next **Step** exists in the current **Material Facility** or, if there is no next **Step** defined, the **Material** is In Rework or Off-Flow and there is a Return Flow Path defined. * If the **Step** is being changed, there are no active **Protocol Instances** that contain the **Material** being moved and that have the property Inhibit Move From Step set to `true`. * There are Rework Paths defined for the **Material** current processing point (immediate parent **Flow** and **Step**). * Selected Rework Flow (Go To Flow Path) exists, is Active and Enabled. * Selected Rework Reason exists, is active and is currently assigned to the current **Material** **Step** and classified as applicable to Rework. * If the **Product** of the **Material** has any of these properties set to `true`, Apply Global Rework Limit, Apply Step Rework Limits or Apply Reason Rework Limits, then you must take the limits that were set into account, and there must be a **Reason** for the **Rework** of the **Material**. * If the next **Step** has different Primary or Secondary Units, there must be Product Units Conversion Factors defined for the current **Material** **Product** (and all **Sub-Material** **Products**). * There must not be any **Material** Time Constraint violated for the **Material** at the current context and transaction. * There must not be any required Future Action for the **Material**. ## Preconditions for Bulk !!! note All Materials will be sent to the same Temporary Off-Flow / Step and with the same Rework Reason. * All **Materials** must: * Be at the same Flow Path. * Have the same System State. * If a **Checklist** is required, all **Materials** must require the same **Checklist**. !!! note If the Checklist is Long Running, different Checklist Instances will be created. Additionally, if the Checklist is Immediate, it must not contain any conditional item. * If a **Data Collection** is required, all **Materials** must require the same **Data Collection** with the same Data Collection Limit Set and Data Collection Type. !!! note If the Data Collection Type is not Long Running After Track-In, no Data Collection Parameter must have the Sample Id set to Material Id. * Resolved **Documents** must be the same for all Materials. ## Sequence Of Steps ### Step 1: Rework Reason 1. Select the **Off-Flow** button on the top ribbon and select **Rework**. 2. In the Rework Material wizard, select a **Reason** which is applicable to **Rework**. 3. If a Go To and Return Flow Paths are associated with that **Reason**, they are automatically pre-selected, otherwise the system will pre-select the **Step** where the **Material** is currently located. In any case, the Return Flow Path can be overriden. The **Material** will be sent to the Go To Flow Path and, once it reaches the last **Step** in that **Flow**, it will return to the Return Flow Path. !!! info Changing the configured Return Flow Path is only allowed if the `Material.ReworkOverride` security feature is enabled. Reworks can also be performed within existing Reworks. Depending on the Future Hold configuration, the Material may be put on hold. 4. Optionally, enter a Comment. 5. Select **Rework** to continue. ![Screenshot showing a form field labeled "Rework Reason" with options for input.](images/rework_material_reason.png) !!! warning When a Rework operation is performed while the Material is in a non-sequential block, the system will discard the information about which of the steps have already been performed in that same non-sequential block. Upon returning to the non-sequential block, those steps must be repeated or alternatively marked as optional and skipped. ### Step 2: Documents This step is used to display **Documents** which are associated with the transaction context. To open any **Document** it is only necessary to select a **Document** and choose **View**. ![Screenshot showing a list of documents, including "Rework Material Documents", associated with the transaction context.](images/rework_material_documents.png) !!! note This step will only appear if there are Documents linked to the Material or the current Step. Documents can be configured either through the [[materialdocumentcontext-st]] smart table or directly in the Step Context View. For more information, see [[user-guide-create-document]]. ### Step 3: Data Collection This screen is used to collect data from a pre-defined **Data Collection**. 1. If the **Material** has a Long Running or Immediate **Data Collection** configured, a screen will be displayed where it is possible to fill out the **Data Collection** data. If the **Data Collection** is Long Running, data can be filled out later (partially or completely). If the **Data Collection** is Immediate, it must be filled out completely. ![Screenshot showing a UI for filling out Data Collection details.](images/rework_material_datacollection.png) !!! note This step is visible only when a Data Collection is associated with the current Material Context and when the Material is Top-Most. Configure Data Collections through the [[materialdatacollectioncontext-st]] Smart Table or directly in the Step Context View. For more information, see [[create-data-collection]]. A Data Collection may be configured to send data to SPC, in which case one or more SPC Charts will appear. ### Step 4: Checklist This screen is used to complete a pre-defined **Checklist** associated with the Track-In. 1. The **Checklist** is Immediate and must be filled out completely. ![Screenshot showing a rework material checklist with incomplete and illegible entries.](images/rework_material_checklist.png) !!! note This step will only appear if there is a Checklist associated with the current Material or Step Context.Checklists can be configured either in the [[materialchecklistcontext-st]] Smart Table or directly in the Step Context View. For more information, see [[user-guide-create-checklist]]. It is possible to link an Immediate Checklist to a Data Collection. This means that when filling out the Checklist, you can also fill out the Data Collection, and the following is observed: * If all the parameters of the Data Collection belong to the Checklist, the Data Collection step will not be shown. * If only some parameters of the Data Collection belong to the Checklist, both steps must be shown so you can fill out every item you need.