Job Corrections

Job Corrections enable users to modify historical production runs. Common correction scenarios include:

• Inserting completed production runs that were missed by the operators. These can be added between two previously completed production runs. However, the production run cannot be left in-progress if later production runs exist on the production line.
• Modifying the start time and end time of a production run.
• Deleting production runs that are started incorrectly.

The following corrections can be made:

• Move start time on current production runs: The start timestamp of a current production run can be moved in the forward or backward direction, provided the revised timestamp does not overlap with another production run on the same production line.
• Move start time or end time on completed production runs: The start or end timestamps for a completed production run can be modified in the forward or backward direction, as long as neither timestamp is in the future and the revised time range does not overlap with another production run on the production line.
• Delete current or completed production runs: Current or completed production runs can be deleted. When a production run is deleted, the production stop period that ended by the start of this production run is extended to fill the gap in time.
  Note: To add or move a job into a period occupied by another production run, space must be created by adjusting or removing existing production runs. Updating one production run does not automatically shift other production runs.
• Production stops: Production stop records are automatically updated when production run start or end dates are corrected. Setup and ramp-up periods are also automatically adjusted.
• Production counts, scrap counts, and process parameter records: These records are automatically reclassified when a production run correction impacts the associated period. Depending on the correction, records can be reassigned to appropriate job/material or have their job/material association removed.
• Line Information and KPI data: Cached line information and KPI data are automatically regenerated and recalculated for the impacted periods.
• Inventory creation and usage records: Inventory records are automatically adjusted when they align with the original job boundaries. Inventory creation records that fall outside the adjusted period are ignored automatically or cause an error, depending on the line setting. The same line setting also determines how these records are handled when a job is ended.