Documents
Document checks for H1Z2Z2-K solar PV cable
For H1Z2Z2-K, review the product code with the EN 50618:2014 and IEC 62930:2017 references and related records.
- H1Z2Z2-K
- Solar PV
Products
Products and families referenced
Confirming the Product Code Before Anything Else
A solar PV cable review does not start with a general label such as "solar cable" or "PV wire." It starts with confirming that the exact code printed on the document under review is H1Z2Z2-K, matched character by character against what the project specification calls for. CMK records contain related document entries for H1Z2Z2-K, and the first task for any buyer or project engineer is to verify that the file requested is tied to this code specifically, not to a similarly named product from an adjacent range.
Cable naming conventions can look close enough to cause confusion, particularly when a buyer is working from a project bill of materials that lists only a partial code or a commercial shorthand. Before a document is accepted into a submittal package, the reviewer should trace it back to the exact code on the record and confirm that no substitution occurred between families that share a prefix or a visual resemblance in the product name. This step is procedural, not technical, but skipping it is a common source of downstream rejection during project audits.
Requesting the Correct Document Type
Technical data, a certificate, and a Declaration of Performance (DoP) each carry a different purpose for H1Z2Z2-K, and a request that does not specify which one is needed often returns the wrong file for the intended use. A data sheet describes construction and general characteristics; a certificate attests to a specific test or assessment; a DoP is a formal statement tied to a defined scope. Buyers should state explicitly, in writing, which of the three documents the project requires before a document is issued.
Once a document arrives, the practical step is to read the number, the date, and the stated scope exactly as printed, rather than inferring a class or an approval scope that is not shown on the page. CMK records contain related document entries for H1Z2Z2-K linked to EN 50618:2014 and IEC 62930:2017, and confirming that the printed reference matches the project's required standard is a distinct check from confirming the product code. Neither check should be skipped or assumed from the other.
Why Two Standards Appear in the Same Product Family
Solar PV project specifications sometimes reference EN 50618:2014, sometimes IEC 62930:2017, and occasionally both, depending on which market or certification framework the project follows. EN 50618:2014 is the reference more commonly cited within European project specifications, while IEC 62930:2017 appears more often where an international or non-European certification framework governs the procurement. The reference should not be selected by publication year alone; use the standard explicitly required by the project specification and the applicable market requirements.
This is industry practice rather than a CMK-specific rule: EPCs and installers across different projects reference either document, or both, based on the certification path their project has adopted. A buyer working across multiple markets should not assume the same standard reference applies uniformly to every project and should confirm, before requesting documents, which reference their specific contract or specification actually calls for. This confirmation should happen before, not after, a document request is sent.
A Verification Checklist for DoP and Data Sheet Scope
Before a DoP or a data sheet for H1Z2Z2-K is accepted into a project file, three checks should be completed in sequence. First, confirm that the code printed on the document reads exactly H1Z2Z2-K, with no truncation, added suffix, or substitution from a related code. Second, confirm which of the two standard references, EN 50618:2014, IEC 62930:2017, or both, actually appears on the document, since a project may require one specifically and not accept the other as equivalent.
Third, confirm that the document date or version is the one relevant to the current order, since a project file may already contain a superseded version from an earlier stage of the same procurement. None of these three checks should be treated as satisfied by inference; each should be confirmed against what is printed on the document itself, without assuming content, scope, or class that is not directly shown. This sequence applies to every request, regardless of order size or project stage.
Avoiding Cross-Application Assumptions from a Code Prefix
H1Z2Z2-K belongs to a single-core solar PV cable family, and its H-prefix code should not be treated as an indicator that any other H-coded product from a different application family is automatically suitable for a solar PV project. Cable naming systems frequently produce codes that look superficially similar across entirely different applications, and a shared prefix communicates a naming convention, not an equivalence of function, construction, or intended use between two products.
A buyer or project engineer who encounters a code that resembles H1Z2Z2-K, without matching it exactly, should treat that as a distinct product requiring its own separate document review rather than as a variant of the same reference. Cross-application suitability is never established by a shared prefix or a family resemblance in the name; it can only be confirmed by checking the code, and the associated document, against the specific application the project requires.
Conclusion
For H1Z2Z2-K, a complete review means aligning three elements before a document is used in a quote or an order: the exact product code, the relevant standard reference or references shown on the document, and the specific document type requested. Confirming each of these separately, rather than assuming one from another, is the difference between a review that holds up under project audit and one that does not.