Certificate of Analysis — ISO 6141
Issue a certificate against the standard your customers audit you on, with a registry of every certificate issued and the payload preserved as it was signed. Not a Word template with the numbers pasted in.
Fluids capability
This is the part of Fluids that surprises people. It is not a quality checkbox on a dispatch screen — it is a laboratory information system with certificates, uncertainty calculation, calibration control, sampling plans and an audit trail, sitting inside the same system as your orders and your invoices.
A customer's quality department rejects your certificate. An auditor asks which instrument produced a result from eighteen months ago and whether it was in calibration that day. A specification changes and you need to know which lots were released under the old one. If your answer to any of those is a folder and a phone call, this is the module that changes it.
Standards
These are the frameworks the calculations and record formats follow. Certification is yours to hold — this gives your audit something to stand on.
Capabilities
Issue a certificate against the standard your customers audit you on, with a registry of every certificate issued and the payload preserved as it was signed. Not a Word template with the numbers pasted in.
Expanded uncertainty at k=2 calculated per component of the mixture, attached to the certificate. The number your customer's quality department will ask for, computed rather than quoted.
Every analyzer registered with its calibration history and validity window. A result recorded on an out-of-calibration instrument is caught, and due dates raise alerts before they expire.
Analyst signs, reviewer countersigns. Every edit to a result after entry is written to a separate audit table that the application cannot rewrite. Test methods are versioned, so you know which SOP a two-year-old result was produced under.
Control charts and stability trending over your own results, so drift is visible as drift rather than as a run of individually acceptable numbers.
39 sampling plans seeded — inspection level II, normal severity, single sampling, AQL 1.0, 2.5 and 4.0, code letters A through N — applied to production lots with accept and reject numbers computed for the lot size. Replaceable with your own QA standard.
Non-conformances raised manually or automatically from receiving and inspection, with root cause, disposition, corrective action and closure. They feed the vendor scorecard, so a supplier's quality shows up in their next evaluation.
Cost of quality, first-pass yield and defect Pareto — the numbers that turn a quality argument into a financial one.
Test record
Consequence
A result that only lands in a report is a filing exercise. In Fluids a result moves the operation.
A failed quality check automatically raises a rework production job and creates a child re-test that carries a reference to its parent, so the chain from failure to resolution is a record rather than a memory.
Goods received that fail inspection raise a non-conformance without anyone remembering to. The vendor's scorecard reflects it at the next period close.
The pre-dispatch inspection captures photographic evidence and annotated defects, and its result drives the dispatch-readiness board — ready, partial or blocked.
Results can be batch-imported from analyzer output with a review-and-apply step, tagged by source. The endpoint already accepts PLC and SCADA sourced data for when you connect the floor.
Next
Passing quality is one gate. Correct GST on the document and gapless numbering are the next.