PUBLIC STATUS
Public status: workflow disclosure
No universal inspection plan, test list, equipment list or pass result is asserted on this page. Applicable controls and deliverables must be agreed for the selected configuration and order.
PRACTICAL PROCESS
How to use this information
- Define the acceptance basis
Identify the ordered model and SKU, service conditions, applicable drawing revision, required inspections, measurable acceptance criteria and documents. Requirements that matter to project acceptance should be written into the quotation or technical agreement before production or shipment.
- Match records to the item
Check that each submitted record identifies the legal supplier, order or work reference, product identity, serial or batch where applicable, method, instrument or reference used, result, date and reviewer. A generic photograph or blank form is not order evidence.
- Review exceptions before release
Compare recorded results with the agreed criterion and document any deviation, concession, retest or corrective action. The approved disposition and release record should remain linked to the delivered configuration rather than being inferred from a general website statement.
EVIDENCE CHECKLIST
Fields to verify before relying on a record
- Product identity
- Model, SKU, configuration revision and serial or batch where assigned.
- Acceptance basis
- Approved specification, drawing, standard or customer criterion and its revision.
- Inspection or test method
- Named procedure, checkpoints, conditions and sampling basis where relevant.
- Measurement resources
- Equipment or reference identifier and current calibration status when a measured result is reported.
- Results and units
- Actual observations or values, acceptance limits and an explicit pass, fail or review disposition.
- Traceability
- Order, work, serial or batch linkage sufficient to associate the record with the delivered item.
- Approval
- Execution date, reviewer identity and documented treatment of deviations or retests.
DOCUMENT CONTROL
Which document takes priority?
- Executed contract and signed technical agreement: Controls the agreed scope, exceptions and acceptance terms for the transaction.
- Approved order confirmation and configuration datasheet: Controls the ordered model, SKU, options, quantity and order-specific deliverables.
- Current model/SKU drawing, manual, certificate or test record: Supports the applicable technical value or evidence claim when its identity, revision and scope match.
- Public webpage or sales summary: Supports discovery only and does not override an approved configuration or order document.
Important limitations
- A quality-system statement does not prove that a particular test was performed on a particular unit.
- Inspection scope, sampling, acceptance criteria and customer witness points must be agreed before they are relied on for release.
CONFIGURATION-SPECIFIC SUPPORT
Request the record that applies to your order
Send the model, SKU, process conditions, order reference and the evidence or document you need. TYCK can then confirm what is available for that specific configuration without asking you to rely on a general website statement.
EVIDENCE FAQ
Frequently asked questions
Does every TYCK instrument receive the same inspection and test sequence?
No universal sequence is stated here. The relevant checks can vary with the product family, configuration, measurement range, process connection, ordered documents and project requirements. Ask for the proposed inspection and test plan before ordering when a specific check, witness point or report is required. The resulting record should identify the delivered model or serial/batch and the acceptance basis; a test used for another configuration should not be transferred without review.
What makes a test report useful for project acceptance?
A useful report connects the item to an order or serial/batch, names the method and conditions, records actual results and units, states the acceptance criterion and identifies the date and reviewer. Where measurements depend on test equipment, the equipment or reference and its calibration status should be traceable. Project acceptance may also require customer witnessing or a specified format, so those conditions should be agreed in the order documents before the test is performed.
How should a failed or out-of-limit result be handled?
Do not replace the original result with an unexplained passing value. The record should retain the nonconformance, evaluation, authorised disposition and any repair, adjustment or retest. A retest should state what changed and use the applicable acceptance basis. Whether a deviation is acceptable belongs to the agreed quality and contract process; a website cannot approve it. Request the complete record chain when the result affects safety, compliance or project acceptance.