Scan Part

In this article:

🔧 Basic Part Scanning

The Scan Part feature allows you to capture component part numbers quickly and accurately, either by scanning a barcode or entering the part number manually using a keyboard.

📥 What It Does:

Records a part number into the production or test sequence.
Accepts input from barcode scanners (1D/2D) or manual typing.
Stores the scanned data for traceability, reporting, and validation purposes.

✅ Benefits:

Speeds up data entry and reduces manual errors.
Ensures correct components are used in the right step of the process.
Provides a traceable record of each part scanned for quality audits.

🛠️ Common Use Cases:

Logging serial numbers of components like PCBs, sensors, or mechanical parts.
Capturing batch numbers for materials or consumables.
Verifying correct part numbers before assembly or testing.

Scan Part – Unique Part Check

The Unique Part Check is an option within the Scan Part feature that ensures each part scanned is valid and has not been used more times than allowed. This helps maintain traceability and prevent reusing parts in production or test processes.

🔍 What It Does:

When enabled, the system checks the scanned part number against the database to determine if it has been previously used.
You can define a maximum number of allowed uses for each part (e.g., only once, or up to a specific number of times).
If the part has already been used more than allowed, the scan is rejected and an appropriate message is shown to the operator.

✅ Benefits:

Ensures traceability and compliance with quality processes.
Prevents duplicate use of serialized or critical components.
Helps enforce assembly or test process integrity.

⚙️ Typical Use Cases:

Limiting each serial number to a single build.
Allowing up to 3 test attempts per part before rejecting further use.
Preventing reuse of parts across production lines.

🔄 Passed Operation Check (Sub-Assemblies)

The Passed Operation Check is an advanced option within the Scan Part feature, used to validate sub-assemblies built using Tascus before they are used in a larger assembly process.

🔍 What It Does:

When enabled, the system queries the Tascus database to check if the scanned part number (sub-assembly) has previously been built and passed a specific manufacturing operation.
If the sub-assembly is found and the operation is marked as completed and passed, the scan is accepted.
If not, the scan is rejected, preventing the use of incomplete or failed sub-assemblies.

✅ Benefits:

Ensures only fully completed and verified sub-assemblies are used in final products.
Enforces build process integrity across multiple stages of production.
Reduces risk of using incomplete, untested, or failed components in downstream operations.

🛠️ Typical Use Cases:

Scanning in a pre-built PCB, sensor unit, or mechanical assembly during final assembly.
Validating that all sub-assemblies have passed required test and inspection steps before integration.
Enforcing quality checkpoints between different workstations or production bays.

⚠️ Note: This feature only works with sub-assemblies that have been built using Tascus MES, and requires the relevant operation data to be recorded and available in the system.

How to Create a Sub Assembly

The steps below will guide you to create a Sub Assembly within the Tascus Sequence Editor

Ensure you have configured the Top Level, follow the steps:

🗃️ Scan & Store

The Scan & Store option allows you to capture and save the scanned value directly into a header field within the Tascus database. This enables the scanned data to be used later in the manufacturing process for tracking, validation, or reporting purposes.

🔍 What It Does:

Extracts the scanned value (e.g., serial number, batch code).
Stores it in a predefined header custom field for the current production record.

Storing the scan results using Header Custom Field Ref 'AA'

Makes the stored data accessible later in the process, for comparison.

Later in the process comparing the scan result to the value stored in Header Custom Field 'AA'

✅ Benefits:

Supports multi-stage verification by capturing key part identifiers early in the process.
Allows for rechecking a part or serial number at a later step to ensure continuity.
Enhances traceability by linking key data to the production record.

🛠️ Typical Use Cases:

Scanning a serial number during early assembly and checking it again before final test.
Capturing a calibration device ID or tooling reference for audit purposes.
Storing a scanned label or part code for inclusion in production reports or labels.

🔧 Tip: Make sure the header field you store to is uniquely defined and clearly named to avoid confusion when reusing or referencing it later in the process.

🔍 Scan Filtering

Scan Filtering allows you to extract a specific portion of the scanned input to be used during scan evaluation or stored for later use in the manufacturing process. This is helpful when only part of a barcode or input string is relevant — such as a product variant, batch code, or revision number.

🔧 What It Does:

Applies a filter or pattern to the scanned value.
Extracts the relevant section based on the defined criteria.
The filtered result can be used for validation, comparison, or saved using the Scan & Store option.

✅ Benefits:

Handles complex or multi-part barcodes with ease.
Ensures only the relevant data is used in production steps.
Reduces risk of operator error by automating data parsing.

🛠️ Typical Use Cases:

Filtering the prefix or suffix of a serial number to identify a product type.
Extracting a batch or lot code from a longer string.
Isolating a revision number for validation against build requirements.

💡 Tip: Use Scan Filtering alongside other Scan Part options to tailor the scanning process to your specific part labelling formats.

🧪 Example Use Case: Validating PCB Lot Code Consistency

In this example, a manufacturer assembles products using multiple PCBs. Each PCB barcode includes a Lot Code embedded in the string. The goal is to ensure that all PCBs assembled together originate from the same lot.

🎯 Objective:

Ensure that PCBs 51024 and 51026 match the Lot Code from the reference PCB 51020.

🔁 Process Overview:

Step	Action	Feature Used
1	Scan reference PCB (51020) to confirm it's the correct starting part	Basic Scan + Check
2	Scan 51020 again, extract the Lot Code from the barcode using scan filtering	🔍 Scan Filtering & Store
3	Store the extracted Lot Code in a Header Custom Field called `LOT_CODE`	🗃️ Scan & Store
4	Scan PCB 51024, confirm the correct part has been selected	Basic Scan + Check
5	Extract Lot Code from 51024 barcode using scan filter	🔍 Scan Filtering
6	Compare extracted Lot Code with stored `LOT_CODE`	✅ Compare Step
7	Repeat steps 4–6 for PCB 51026	Same

✅ Result:

The operator can only proceed if all scanned PCBs have the same Lot Code as the reference PCB, ensuring quality and traceability throughout the build.

🧠 Notes:

The LOT_CODE value is stored using a Header Custom Field and is accessible throughout the full production record.
This method helps enforce consistency when using matched components, especially in high-reliability assemblies.
This logic can be adapted for supplier codes, firmware versions, or customer-specific configurations.