DC Surge Protective Devices · Comparison
Type 1 vs Type 2 DC SPD: Classification and Evidence Boundaries
Compare Type 1 and Type 2 DC SPD classification roles without transferring AC assumptions or unsupported ratings. A useful buyer review connects the project requirement to one exact orderable product and preserves the evidence used for approval.
This comparison explains classification and evidence boundaries. It does not assign a Type 1 or Type 2 SPD to a project, reproduce a test standard or transfer an AC classification, rating or diagram to a DC product.
Decision Inputs at a Glance
| Review field | Buyer must define | Evidence to request |
|---|---|---|
| Classification | Exact declared type and referenced document | Product marking plus datasheet |
| System side | DC source, voltage architecture and earth relationship | Approved project record |
| Installation location | Exposure and protection-zone context defined by project | Surge protection design |
| Other SPD parameters | Continuous voltage, protection level and discharge declarations | Same exact model row |
| Coordination | Backup protection, upstream/downstream SPD relationship and leads | Manufacturer instructions |
Classification Labels Describe Tested Roles
Type 1 and Type 2 are not simple quality grades. They identify different declared surge-protection roles and test contexts within the applicable product documentation. A buyer should read the classification beside the exact standard reference, product marking and manufacturer data rather than assuming that the larger number is better or newer.
The project decision begins with the expected surge environment and installation location. Those inputs belong to the system design. The product evidence then shows whether a particular DC SPD is declared for that role. This article does not replace that design step.
Do Not Transfer an AC Assumption to the DC Side
AC and DC circuits can differ in source behavior, voltage architecture, conductor relationships and interruption considerations. A familiar AC SPD label or diagram does not automatically answer a photovoltaic, battery or industrial DC requirement. Use documentation that explicitly covers the proposed DC product and system arrangement.
Even when classification terminology looks similar, compare the supporting values and diagrams within the same exact DC model row. Never combine a type declaration from one variant with a continuous-voltage rating, protection level or pole arrangement from another.
Location and Exposure Shape the Requirement
Record whether the SPD is considered at an incoming boundary, downstream distribution point, equipment interface or another defined location. Add the project lightning and surge-protection assumptions, upstream devices and cable route context. These are inputs for the responsible designer, not attributes that procurement should guess.
A Type 1 versus Type 2 comparison is incomplete when it ignores location. Two quotations carrying different classifications may be answering different design positions. Ask suppliers to state the intended location and evidence basis for the proposed device.
Read All Declared Parameters Together
Classification should be reviewed with the maximum continuous operating voltage or PV equivalent, declared protection level, discharge-current information, pole arrangement and any remote indication or replaceable module. Each parameter has a distinct role. None can be inferred from the classification name alone.
Compare values only when definitions and test conditions align. A higher headline discharge value does not resolve an unsuitable voltage declaration or topology. Likewise, a suitable classification does not prove coordination with the rest of the system.
Demand an Exact Evidence Chain
The approval pack should contain the project requirement, selected location, topology record, full SPD order code, datasheet, product marking and exact connection instructions. If the declaration comes from a certificate or test report, confirm its scope and that the quoted model is included.
Marketing phrases such as heavy duty or lightning protection are not substitutes for this chain. They can introduce a product family, but the engineering approval must remain attached to traceable declarations for the candidate device.
Use Comparison to Expose Assumptions
Place each offer in a table that separates project facts, supplier claims, supporting documents and unresolved items. If one supplier quotes Type 1 and another quotes Type 2, do not immediately compare price. First establish whether both used the same location, topology and protection concept.
Where evidence is incomplete, keep the quotation technically open. The correct response is a clarification request, not an editorial guess. This preserves both safety and commercial comparability.
Build an Exact-Model Evidence File
Create one approval record for the proposed DC SPD order code. Put each project requirement beside the supplier document that answers it. Preserve the exact datasheet, drawing, table, instruction or selection output used, including its revision or retrieval date. A category page can establish family context, but it cannot prove an exact rating, terminal arrangement or system combination.
Check that every accepted statement describes the same orderable item. Similar housings can contain different circuits, supplies, terminals, accessories or functions. Do not combine a family maximum from one variant, a diagram from another and an optional feature from a third. Mark unresolved fields explicitly so they remain visible in the commercial review.
Keep Project Inputs Separate From Product Evidence
The project team defines the application: source, load, duty, environment, controls, mechanical limits and required functions. The supplier identifies an exact DC SPD and supports it with exact documents. Neither side should fill a gap by inference from appearance, a shared family name or one matching headline value.
Freeze the application record while quotations are being compared. If the topology, source, load, environment, enclosure or required output changes, issue a revised record and ask each supplier to reconfirm the candidate. Otherwise apparently comparable quotations may be answering different technical requirements.
Common Procurement Errors
Avoid selecting a DC SPD from one headline value while the application context remains incomplete. Do not use a circuit, curve, terminal drawing or performance claim from a neighboring model. A product photograph and a family page can support discovery, but neither is exact technical evidence.
Also avoid assuming that an accessory, communication function, protection role or coordinated result is included unless it appears in the quotation and exact-model documents. A substitute requires the same topology, rating, mounting and evidence review as the original candidate.
How to Compare Supplier Offers
Normalize every DC SPD offer to the same application record. Keep document revisions, stated conditions, included accessories and open questions beside each value. This makes differences in delivered scope visible and prevents a lower-cost but narrower offer from appearing equivalent to a complete solution.
Stop the comparison when a critical application input is unknown, the quoted model is ambiguous, a required claim is supported only by another manufacturer or order code, or the installation falls outside the available evidence. These are engineering gaps, not editorial details.
Control Revisions and Substitutions
Give the approved DC SPD record a revision identifier and keep it with the project file. If the supplier changes the order code, accessory, firmware, drawing or stated operating condition, identify the change before accepting it. A substitution is a new technical proposal even when its price, housing or product-family name looks familiar.
Repeat only the affected checks, but do not waive them. Confirm that the revised candidate still answers the frozen application, that every referenced document belongs to it and that all open exceptions have an owner. This small change-control step prevents a technically reviewed selection from being replaced by an unreviewed commercial equivalent.
Decision Workflow
- Freeze the application and system record before choosing a catalog code.
- Identify the exact function and every interface that requires evidence.
- Request one complete order code with its current datasheet and drawings.
- Map each project requirement to a specific manufacturer statement.
- Record deviations, accessories, document revisions and unresolved questions.
- Repeat the review whenever the application or proposed product changes.
Use this workflow as a procurement and evidence discipline. It does not replace qualified design, installation instructions or the responsible engineer's approval for the DC SPD application.
RFQ Preparation Checklist
A practical type 1 vs type 2 dc spd should be concise enough for a supplier to answer and complete enough to prevent silent assumptions. Identify unknown values as questions rather than allowing them to become undocumented selections.
- Classification: Exact declared type and referenced document.
- System side: DC source, voltage architecture and earth relationship.
- Installation location: Exposure and protection-zone context defined by project.
- Other SPD parameters: Continuous voltage, protection level and discharge declarations.
- Coordination: Backup protection, upstream/downstream SPD relationship and leads.
- Exact product code, included accessories and documentation revision
- Quantity, destination, required approvals and commercial scope
Request the exact scope of any classification, compatibility, coordination or performance claim. Record quantity and destination after the technical inputs so commercial terms do not obscure unresolved engineering questions.
Frequently Asked Questions
Is Type 2 automatically better than Type 1?
No. The labels describe different declared roles and test contexts, not a simple ranking.
Can an AC Type 2 SPD be assumed suitable for DC?
No. Suitability must be documented for the exact DC product and system.
Does classification confirm every surge rating?
No. Review each declared parameter and its test conditions separately.
Related RITOKS Products and Guidance
These links provide product-family context only. A contextual link does not claim interchangeability, compatibility or an approved system combination.
Technical References
These manufacturer sources support only the general engineering concepts described below. Their product ratings, circuit diagrams, approvals and coordination results do not transfer to RITOKS products.
Schneider Electric, Surge Protection Devices: Electrical Installation Guide
Supports the distinction between SPD classification, continuous-voltage, protection-level and discharge-current roles. Schneider values and diagrams do not transfer to RITOKS products.
Phoenix Contact, Surge Protection for Photovoltaic Systems
Supports treating PV DC surge protection as a system-location and topology question. Phoenix Contact ratings and arrangements are not RITOKS evidence.
Request an Exact-Model Review
Send the application requirements, exact-document questions, quantity and destination through the RITOKS contact form. An RFQ requests an exact-model review; this guide does not approve a circuit, installation or automatic substitute.