Skip to main content

​
Introduction to the Process_Entries Table

The process_entries table is designed to store detailed records of processes performed on component instances within the Serial system. This table plays a crucial role in tracking the execution and outcomes of various manufacturing processes across different components, stations, and operators.

​
Table Structure

The process_entries table is structured to capture comprehensive information about each process execution. Here’s a detailed breakdown of its columns:
Column NameData TypeConstraintsDescription
iduuidprimary keyUnique identifier for each process entry
company_iduuidnot nullID of the company associated with the process entry
unique_identifier_iduuidnot nullID of the component instance on which the process was performed
process_iduuidnot nullID of the process that was executed
timestamptimestamp with time zonenot null, default now()Time when the process entry was created
station_iduuidnullableID of the station where the process was performed (if applicable)
is_passbooleannullableIndicates whether the process passed or failed (null if not yet determined)
operator_iduuidnullableID of the operator who performed the process (if applicable)
process_revisionbigintnullableRevision number of the process at the time of execution
upload_errorbooleandefault trueIndicates if there was an error during the upload of this entry
cycle_timenumbernullableTime taken to complete the process (if applicable)
override_user_iduuidnullableID of the user who overrode any automatic determinations (if applicable)

​
Usage and Functionality

The process_entries table is designed to be a comprehensive record of all process executions in the system. Here are some key points about its usage:
  1. Process Tracking: Each entry in this table represents a single execution of a process on a specific component instance. This allows for detailed tracking of manufacturing steps and quality control processes.
  2. Status Management: The is_pass column is used to determine the success or failure of a process. This information is crucial for quality control and can trigger status updates for component instances (e.g., marking a component as defective if a process fails).
  3. Performance Analysis: With timestamps and cycle times recorded, this table enables analysis of process efficiency and identification of bottlenecks in the manufacturing process.
  4. Error Handling: The upload_error column, defaulting to true, helps in identifying and managing issues during data upload, ensuring data integrity in the system.

​
Notes

  • A trigger function is associated with this table to automatically update the status of component instances based on new process entries: 
    CREATE TRIGGER update_component_instance_status_trigger
AFTER INSERT OR UPDATE ON process_entries
FOR EACH ROW
EXECUTE FUNCTION update_component_instance_status();
  • The table is extensively used in various database functions for retrieving process data, calculating yields, and generating reports.
By leveraging the process_entries table, the Serial application maintains a detailed and auditable record of all manufacturing processes, enabling robust quality control, performance analysis, and traceability throughout the production lifecycle.