NS-HPDCA
Bring production yields, top defects, unit history and measurements together. NS-HPDCA collects and analyses the logs from your existing testers, giving production, test and quality teams access to the information behind each result.
Your testers already produce the data. NS-HPDCA collects it and makes it usable: production yields, top defects, unit history and measurements in one collection and analysis system.
Start with the production overview to see where attention is needed. Then search the records for a product, test program or serial number and examine the available test detail. This connects the reporting view with the evidence engineers need to investigate failures.
HPDCA works with your existing Flying Probe, ICT and FCT equipment. The value is in collecting and analysing its results—not replacing your testers.
The collector parses tester log files and stores results in MySQL. Automatic collection brings new results into the system as logs become available, rather than requiring operators to compile separate reports.
The analyser provides dashboards, searches and reports through web or desktop interfaces. Production teams review performance, engineers investigate test failures, and quality teams retrieve unit history.
Review test performance by product and reporting period. Compare current results with historical trends to focus investigation on affected production.
Look beyond the final pass count. Distinguish first-pass performance from results achieved after further testing, so repeat tests are not hidden by the final outcome.
Identify recurring failing steps and components. Ranked defect reports help prioritise investigations instead of reading individual log files to find repeated failures.
Find a serial number and review its recorded test history. Product, program, machine and date information provide context for investigating a unit or production run.
Examine the data behind the board-level result. Measurement and failure detail depends on what the source tester records and the configured parser extracts.
Review recorded test times across products, programs and machines. Compare periods to investigate changes in test duration alongside yield and retest behaviour.
A common collection and analysis environment for different test-log formats.
Collect and analyse Takaya test logs for production yields, recorded failures and unit history. Review the results through HPDCA rather than searching each machine’s files separately.
Collect in-circuit test results for yield reporting, failure analysis and unit history. Retain the detail provided by the tester logs for investigation beyond the overall board result.
Bring functional test logs into the same workflow. Custom parsers map each station’s output into structured records for reporting and analysis.
Compatibility is established from the log format and available fields. Send a representative anonymised log with the tester model and software version so we can confirm the existing parser fit or the custom parsing required.
Your Flying Probe, ICT or FCT system produces its test log.
The configured parser extracts the available test data.
Results are retained in a structured MySQL database.
Review dashboards, investigate failures and retrieve unit results.
Depending on the source log, records can include serial number, product, program, tester, timestamps, PASS/FAIL status, measurements and failing steps. The parser extracts what the test system records; not every format provides the same detail.
Scan a board’s serial number to retrieve its latest recorded test result and display PASS or FAIL. Operators can check the stored result without locating and opening the original test log.
This supports a result check at a quality or shipping station. The operator follows the site’s release procedure based on the displayed result.
HPDCA uses a MySQL database with Windows and web interfaces. Collection arrangements depend on where the tester writes its logs and how those files are made accessible.
During evaluation, we review source formats, log locations, reporting needs and access arrangements. Hosting and data-retention requirements can then be agreed for your environment.
Test data can support wider reporting and integration requirements. Discuss the information needed by your existing BI, MES or ERP systems so the data exchange can be scoped around your workflow.
Provide tester types, an anonymised sample log and the questions your team needs answered. The demonstration can then focus on relevant reports and collection requirements.
No. HPDCA collects and analyses logs produced by your existing test systems. The tester continues to perform its tests.
Yes. Custom parsers extend collection to additional Flying Probe, ICT and FCT systems. A representative log establishes the available data and mapping required.
No. Available fields and measurements depend on the source log and parser configuration.
Scan a serial number to retrieve the latest recorded test result and display PASS or FAIL.
Tell us which testers you use and what you need to learn from their results. We can review log compatibility and demonstrate the relevant collection and analysis workflow.