What Dispensing Process Data Should Buyers Require Suppliers to Retain?

Retain evidence for decisions, not data for its own sake

A machine can generate thousands of values per second. Keeping everything forever may be expensive and still fail a complaint investigation if data cannot map to product. Start from decisions the buyer may need to make: isolate affected stock, verify cure, evaluate a process change, release a recovery lot or defend a customer response.

For each decision, identify the minimum data, resolution and genealogy link. Ratio sampled once per shift may be insufficient for a short transient. Pressure sampled every millisecond may be unnecessary if only validated shot-level summaries and alarm excursions matter. Engineering and risk should determine granularity.

Keep an identity and genealogy layer

The record must identify part number and revision, serial or lot, production order, machine, fixture, recipe version, operator or shift, material lots, date/time, cure batch, inspection and shipment. Without these links, technical values become anonymous.

Record material refills, partial containers and kit pairing for 2K systems. If component A and B can come from different lots, preserve both identities and the interval in which the pairing was active. Include primer, cleaner or other consumables when they can affect adhesion or cure.

• Use synchronized clocks or documented offsets across systems.
• Keep unit, lot and container identifiers unambiguous.
• Record rework, split lots and merged containers.
• Preserve status changes and release authority.
• Link external warehouses and subcontractors.

Retain recipe and critical process variables

Store recipe identifier, revision, checksum or equivalent control, effective date, authorized changes and the actual recipe used. Critical values may include ratio, shot mass or volume, pressure, temperature, flow, vacuum, dispense height, robot speed, bead geometry, fill level, open time and cure profile.

Record units and scaling. A value 鈥?5鈥?is useless later if nobody knows whether it means psi, kPa, 掳C or a controller percentage.

Keep complete alarm, override and restart history

Alarm records should include type, timestamp, state, acknowledgement, user, affected interval, disposition and restart verification. Preserve overrides and disabled alarms. A system showing only active alarms cannot explain an event after it has been cleared.

Link machine downtime, manual mode and maintenance to product status. If parts continued through an alarm, the record should show how they were identified and released. Screenshot-only evidence is weak when the underlying event history can be exported.

Retain inspection and measurement evidence

Keep raw or sufficiently detailed results for deposit mass, bead geometry, fill height, void inspection, cure, hardness, adhesion, leak, electrical or thermal testing as applicable. Identify equipment, calibration status, method revision, inspector, acceptance limits and retests.

For visual checks, preserve boundary standards, image settings and inspector qualification. For automated vision, store program revision and reject decision, plus representative images where risk and storage permit. Do not overwrite failed results after rework; keep original and final disposition.

Application scenario matrix

Define retention duration by risk and obligation

There is no universal period for every dispensing record. Consider contractual terms, product life, warranty, expected time to failure discovery, regulatory requirements, customer-specific rules and the supplier鈥檚 ability to retrieve archived formats. Critical safety or long-life products may require substantially longer retention than short-life noncritical goods.

Document the rule by record class instead of saying 鈥渜uality records retained per policy.鈥?The supplier quality agreement should state minimum periods or reference a controlled schedule.

Protect data integrity and availability

Control user access, recipe edits, deletion, clock settings and manual corrections. Preserve who changed what and when. Use backups that are separate from the production machine and test restoration periodically. A backup that has never been restored is only an assumption.

Plan for controller replacement, software obsolescence and supplier transfer. Export data in documented, readable formats with units and field definitions. Hashes, checksums or controlled signatures may support integrity for critical files, but governance and access control remain necessary.

• Role-based access and unique user identity
• Audit trail for changes, overrides and deletions
• Time synchronization across machine, MES and quality systems
• Scheduled backup with monitored failures
• Test restoration and archive readability
• Secure disposal after the approved period

Audit retrieval, not only the retention policy

Select a finished unit and ask the supplier to retrieve the complete process history. Then select a material lot or alarm and trace all affected product forward. Measure elapsed time, missing fields, manual workarounds and quantity differences. The companion guide explains how to run a dispensing supplier traceability drill.

Include archived records older than the normal online window. Current data may be easy to retrieve while backup media, renamed files or retired software make older evidence unusable. Record retrieval failures as system risks and repeat the test after correction.

Put requirements into the supplier agreement

Define record classes, content, granularity, retention, retrieval time, confidentiality, audit rights and notification before disposal or system migration. Require preservation holds when a complaint, claim or investigation is open. The article on the supplier quality agreement after a dispensing complaint provides the broader contract structure.

During closure, index the retained evidence in the complaint closure package. Do not attach every raw file to one document; identify controlled storage locations and access owners.

Evidence and limits

ISO 9001:2015 provides a quality-management framework relevant to documented information, identification, traceability and control of externally provided processes. Industry-specific standards, contracts, privacy rules and regulations may impose additional retention and integrity requirements. Use purchased standards and qualified compliance advice for the applicable product and market.

Frequently asked questions

Should suppliers retain every high-frequency machine sample?

Not automatically. Define granularity from failure mechanisms and decisions, while preserving excursions and useful raw trends.

Is a PDF production report sufficient?

It may support review, but critical investigations often need raw data, revisions and event history behind the summary.

Who owns dispensing process data?

Ownership and access depend on the contract, confidentiality and law. The buyer should secure adequate evidence rights before a complaint.

Should failed inspection results be deleted after rework?

No. Preserve original failure, rework action, retest and final disposition.

How should records be handled during a machine replacement?

Export, validate, index and test retrieval before retiring the old controller or software.

What should buyers send OBO Precision?

Send the application, material, current data map, machine records, retention rules and known investigation gaps.