Identify the configuration
An electrical or electronic product is defined by more than its external model name. Construction, components, power supply, software or firmware and installation conditions may affect the evidence needed. Configuration changes should be visible in the technical record.
Technical documentation
Questions may concern the consistency of specifications, design records, instructions, declarations and reports. The technical file should allow the evaluated configuration and intended use to be traced through the evidence rather than inferred from isolated documents.
Standards and test evidence
A test report should identify its object, method, conditions and results. Its relevance depends on the actual configuration and scope, including any exclusions. An edition reference or test mark alone is insufficient to determine coverage.
Scope and delivery
A scoped activity may examine document consistency, evidence relevance or a defined quality question. If laboratory testing or a statutory procedure is required, the delivery body and activity are stated expressly. A documentary review is not described as testing.
Changes and limitations
The effect of a component substitution, software revision or altered intended use requires consideration against the original basis of evaluation. A prior report should not be extended to changed configurations without an appropriate technical basis.
Related work
Product quality methods help define the object and conclusion. Supplier quality methods address purchasing controls and changes affecting the evidence chain.
Discuss the technical scope
Identify the model, configuration, intended function and relevant markets. State the question to be answered and the reports or specifications already available.
