High Voltage Detector RFQ Template: Technical Schedule, Compliance Matrix, and Deviation Register
For power companies, EPC contractors, substation project procurement teams and distributors of electrical safety equipment, the most common issue when procuring high-voltage detectors is not a lack of suppliers, but rather the lack of comparability between quotations provided by different suppliers.
For example, three suppliers may all quote for a 35 kV voltage detector, but one may supply only the detector unit itself, another may include an insulated operating pole, whilst the third may employ a different detection principle or comply with different standards. If the procurement documentation merely specifies the product name and voltage rating, it becomes very difficult to make a fair technical comparison between these three quotations.
Consequently, an effective RFQ (Request for Quotation) should not merely require suppliers to provide a price, but should clearly specify the project’s electrical system, testing tasks, product configuration, applicable standards, technical documentation and requirements for reporting deviations.
This article provides a methodology for drafting a High Voltage Detector RFQ for B2B project procurement, including a Buyer’s Technical Input Form, a Supplier’s Technical Response Form, a Technical Compliance Matrix and a Deviation Register, to assist procurement teams in identifying specification discrepancies during the quotation stage and completing technical reviews prior to order confirmation.
For projects where the type of detector has not yet been determined, it is recommended to first clarify the actual testing tasks and operating conditions, and then have suppliers with the relevant technical capabilities propose solutions. This avoids locking in unsuitable product configurations too early during the RFQ stage.
Why a High Voltage Detector RFQ Needs More Than a Voltage Rating
Voltage rating is an important parameter when selecting a High Voltage Detector, but it cannot alone determine whether a product is suitable.
Procurement teams must distinguish between at least four dimensions:
| Procurement Dimensions | Key Questions to Clarify | Impact on Procurement Decisions |
|---|---|---|
| Electrical System | Is the target system AC or DC? | Determines the basic suitability criteria for the detector |
| Testing Task | Which location requires testing, and what verification procedures need to be carried out? | Impacts the testing method, contact conditions and accessory configuration |
| Product Configuration | Should a complete detector be procured, or should the probe head and insulated operating rod be procured separately? | Affects interfaces, length, accessories and scope of supply |
| Technical evidence | Which standards, test reports and project documents are required for acceptance? | Determines whether the supplier can meet technical approval requirements |
These four items of information should correspond to one another in the RFQ.
For example, if the procurement team merely specifies “35 kV High Voltage Detector”, suppliers will still be unable to determine which detection principle, contact method or operating frequency the project requires, or whether an insulated operating rod is required.
If the project involves railway traction, energy storage systems or other DC electrical installations, it must also be made clear that the target system is DC; AC detectors cannot be used as substitutes based solely on voltage values.
For large-scale substation projects, it is recommended that the RFQ for voltage detectors be incorporated into the overall procurement plan for electrical safety equipment, whilst retaining a separate technical specifications sheet and acceptance criteria. This ensures consistency across project documentation without forcing different products to adhere to a single set of technical standards that may not be applicable.
Step 1: Define the Project and Electrical System
The first section of the RFQ should describe the project background and the actual electrical system, rather than directly specifying product models.
It is recommended that the buyer provide the following information.
| RFQ Fields | Information to be provided by the purchaser | Instructions for completion |
|---|---|---|
| Project Name | Project Name | For document traceability |
| Project Location | Project country, region or site | Used to identify project requirements and environmental conditions |
| Application | Substation, transmission and distribution lines, switchgear, railway or industrial facilities | Describe the actual usage scenario |
| Electrical System | AC / DC | Must be specified clearly; should not be left to the supplier’s discretion |
| Nominal Voltage | Nominal system voltage | Enter the actual voltage information for the target system |
| Required Detection Range | Required detection range | To be determined based on the target equipment and project technical requirements |
| Frequency | Applicable frequency | To be specified for AC systems where relevant |
| Detection Point | Actual detection location | e.g. conductors, busbars or designated test interfaces |
| Verification Task | Detection tasks and on-site procedures | Specify the role of the detector within the workflow |
| Operating Environment | Indoor, outdoor and other environmental conditions | e.g. temperature, humidity, exposure to rain, etc. |
| Applicable Requirements | Project standards, client specifications or tender requirements | Please provide specific reference numbers and versions where possible |
| Required Quantity | Procurement Quantity | Distinguish between quantities of testers, control levers and accessories |
| Delivery Requirement | Delivery time and location | For quotation and delivery schedule assessment |
An important principle to note here is that if the purchaser has already determined the detection principle and standards via the project specifications, these should be explicitly stated in the RFQ; if they have not yet been determined, the purchaser may request suppliers to provide technical proposals, specifying the scope of application and any matters requiring the purchaser’s confirmation.
The mere presence of a product in a supplier’s catalogue does not imply that it is suitable for the current electrical system.
Step 2: Specify the Detector Type and Detection Method
In the RFQ, ‘Detector Type’ and ‘Detection Method’ should be listed separately.
Different voltage detectors may employ different detection principles and methods of application. The purchaser should determine requirements based on actual work tasks, approved operating procedures and applicable standards, rather than selecting solely on the basis of product name or appearance.
It is recommended that the following fields be clearly specified in the RFQ.
| Technical Fields | Information to be specified by the purchaser |
|---|---|
| Detection Principle | Specified detection principle, or a request for the supplier to propose a solution |
| Contact Requirement | Contact or non-contact requirements |
| Detection Point | Actual detection point and accessibility conditions |
| Contact Electrode | Where applicable, specify the contact electrode and related requirements |
| AC/DC Suitability | Target system type and product suitability statement |
| Indication Method | Audible, visual, digital display or other indication methods as required by the project |
| Functional Check | Methods of functional verification required on-site |
| Application Limitations | Usage restrictions that the supplier must specify |
If a contact-type voltage detector is used for the project, the actual contact points and contact conditions must be specified. If a non-contact detector is used, it must be confirmed that the device is suitable for the detection tasks required by the project.
‘Capacitive’ should not be equated directly with ‘non-contact’, nor should a detector be deemed to meet the requirements of all voltage verification scenarios merely because it features audible and visual alarms.
If the project has not yet decided on the detection principle, the supplier may be asked to list in their quotation the recommended solution, applicable conditions, technical basis and any restrictions relevant to the project requirements, for confirmation by the project’s technical lead.
For information on different detection principles and the scope of applicable standards, please refer to the article on this website: Capacitive vs Resistive High Voltage Detectors: How Buyers Should Match Application and Standard Scope.
Step 3: Define the Complete Supply Configuration
The RFQ must clearly specify exactly what the supplier is required to deliver.
If the procurement documents merely state ‘High Voltage Detector’, this may lead the supplier to assume they are only required to provide the detector unit itself, whilst the buyer actually requires a complete configuration comprising the detection head, insulated operating pole, adaptor, functional verification device and carrying case.
It is recommended to draw up a separate scope of supply table.
| Items to be supplied | Buyer’s Requirements | Supplier’s Response |
|---|---|---|
| Detector Head | Must be supplied or as per project requirements | Specify model and configuration |
| Insulating Operating Pole | Must be supplied / Already provided by the buyer / To be recommended by the supplier | Specify scope of supply |
| Pole Length | Specify length or confirm according to site requirements | Specify actual length |
| Detector Fitting | Specify interface or provide a matching solution | Specify interface model |
| Adapter | Required / Not required / To be confirmed | Specify model and quantity |
| Functional Testing Equipment | To be confirmed in accordance with project procedures | Specify compatibility and supply status |
| Power Source | To be confirmed according to product design | Specify battery or other power supply requirements |
| Carrying Case | Required / Not required | Enter model or configuration |
| User Instructions | Must be provided or as per project requirements | Specify document language |
| Spare Parts | As per project requirements | List spare parts and quantities |
In particular, the compatibility between the tester and the insulated operating rod must be clearly established.
The fact that mechanical interfaces can be connected does not imply that full technical compatibility between the two components has been confirmed. The purchaser should require the supplier to provide accurate interface model numbers, connection drawings and the corresponding compatibility specifications.
For projects requiring the separate procurement of operating handles, the length, structural design, connectors and relevant technical documentation of the operating handles should also be verified to avoid mistaking the test report for the tester unit itself as comprehensive certification for the entire combined equipment set.
For guidance on reviewing the configuration of voltage detectors and operating poles, please refer to How to Match a Voltage Detector to an Operating Pole.
Step 4: Specify Applicable Standards and Technical Documents
The RFQ should not merely state “compliant with IEC standards” or “provide test reports”.
Such wording fails to specify the exact standards, scope of application and versions, nor does it guarantee that the documentation provided by the supplier will support the actual models quoted.
It is recommended that the buyer categorise standards and technical documentation requirements into three tiers.
Tier 1: Applicable product standards.
Specify the standard number, section and version required for the project. If the project’s technical specifications have already designated applicable standards, these should take precedence. Should a supplier propose the use of other standards or solutions, any discrepancies must be reported as technical deviations and await approval.
Tier 2: Product test evidence.
Suppliers must be required to provide test reports or other agreed technical supporting documents that correspond to the quoted model, and to confirm that the reports cover the product structure, testing methods and performance scope.
Third tier: Delivery documentation.
Specify the product manuals, labelling materials, conformity documents, inspection records and product traceability information required upon final delivery.
It is recommended that the following list of documents be used in the RFQ.
| Document Name | Buyer’s Requirements | Information to be provided by the supplier |
|---|---|---|
| Technical Datasheet | Must be provided | Document number and version |
| Product Drawing | As per project requirements | Drawing number and version |
| Applicable Standard | Must be specified | Standard number, part and version |
| Test Report | As per applicable standards and project requirements | Report number, date and corresponding model |
| Product Marking Sample | As per project requirements | Marking sample or document number |
| User Instructions | As per project requirements | Document language and version |
| Certificate of Conformity | As per contract or project requirements | Document format and date of provision |
| Inspection Record | As per the procurement acceptance plan | Inspection items and record format |
| Batch / Serial Traceability | As per project requirements | Batch or serial number management method |
| Technical Deviation Schedule | Must be clearly specified | Declaration of No Deviations or a complete list of deviations |
Documentation requirements should be specified at the quotation stage, rather than being requested from the supplier at short notice only after the product has been completed.
For high-voltage testers, test reports must correspond to the specific type of tester, the applicable standards and the actual model. It is not sufficient to assume that the product complies with all procurement requirements merely because the report bears the words ‘IEC’ or ‘ASTM’.
For further information on how to review test reports, please refer to How to Read a High Voltage Detector Test Report Before Purchase.
Step 5: Create a Technical Data Schedule for Supplier Replies
This is the part of the RFQ most worthy of standardisation.
If the buyer merely sends a statement of product requirements without requiring suppliers to provide technical data item by item, quotations will often contain a large number of vague responses, such as ‘complies with requirements’, ‘can be provided’ or ‘manufactured to standard’.
These responses are insufficient to support a technical review.
It is recommended that a Technical Data Schedule be included as an annex to the RFQ, requiring suppliers to provide actual parameters, corresponding documentation and any necessary clarifications.
| Parameter Item | Buyer’s Requirements | Supplier’s Actual Response | Supporting evidence |
|---|---|---|---|
| Offered Model | Specified by the buyer or recommended by the supplier | Specify the exact model | Product specification sheet |
| Electrical System | AC / DC or as per project requirements | Specify the applicable system | Technical documentation |
| Voltage Range | Project requirements | Specify the actual test range | Product specification sheet and relevant reports |
| Frequency | Applicable frequency | Specify the actual applicable range | Technical documentation |
| Detection Principle | Specify the principle or approved scheme | Specify the detection principle | Product documentation |
| Contact Method | Project requirements | Specify contact method | Product description |
| Indication Method | Project requirements | Specify actual function | Technical documentation and relevant test evidence |
| Functional Check | Project Requirements | Specify self-test or validation method | Instructions for use and related documentation |
| Operating Pole | Scope of supply requirements | Specify model, configuration and length | Operating pole specification sheet |
| Interface / Adapter | Project Requirements | Specify specific interfaces and adapters | Drawings and compatibility specifications |
| Environmental Conditions | Project Requirements | Specify scope of application | Corresponding Technical Evidence |
| Applicable Standard | Project-specified Standard | Enter reference number, section and version | Test Report or Conformity Documentation |
| Included Accessories | Scope of Procurement | List item by item | Quotation Details |
| Delivery Time | Project Requirements | Specify actual delivery time | Commercial Quotation |
| Documentation | List of Documents | Confirm each item | List of Documents |
Suppliers should enter actual data rather than simply copying the buyer’s requirements.
If a parameter is not applicable, enter ‘N/A’ and explain the reason; if further clarification is required, enter ‘Pending Clarification’; if it differs from the buyer’s requirements, it should be recorded in the Technical Deviation Register.
This approach enables the procurement team to identify discrepancies during the technical approval stage, rather than waiting until the order has been confirmed or production has been completed.
Step 6: Use a Technical Compliance Matrix
The Technical Compliance Matrix is used to determine whether the technical proposal submitted by the supplier meets the RFQ requirements.
It is recommended that each requirement be cross-referenced with the supplier’s declaration, supporting documentation and assessment results.
| No. | Buyer’s technical requirements | Supplier’s declaration | Supporting documentation | Assessment status |
|---|---|---|---|---|
| 1 | Electrical system matches application scenario | To be completed by supplier | Product specification sheet | Compliant / Non-compliant / To be confirmed |
| 2 | Test scope meets project requirements | Supplier to specify actual scope | Specifications and relevant test evidence | Compliant / Non-compliant / To be confirmed |
| 3 | Testing principles comply with the approved scheme | To be completed by the supplier | Product technical documentation | Compliant / Non-compliant / To be confirmed |
| 4 | Connection methods meet on-site requirements | To be completed by the supplier | Product description | Compliant / Non-compliant / To be confirmed |
| 5 | Control levers and interfaces meet configuration requirements | To be completed by the supplier | Drawings and compatibility documentation | Compliant / Non-compliant / To be confirmed |
| 6 | Applicable standards and versions are correct | To be completed by the supplier | Standard declarations and relevant reports | Compliant / Non-compliant / To be confirmed |
| 7 | Test evidence matches the model specified in the quotation | To be completed by the supplier | Test report | Compliant / Non-compliant / To be confirmed |
| 8 | Product marking complies with project requirements | To be completed by the supplier | Marking sample | Compliant / Non-compliant / To be confirmed |
| 9 | Delivery documents meet procurement requirements | To be completed by the supplier | List of documents | Compliant / Non-compliant / To be confirmed |
| 10 | Scope of supply is complete | To be completed by the supplier | Quotation breakdown and configuration list | Compliant / Non-compliant / Pending confirmation |
It is recommended to use the following four statuses:
- Compliant: There is sufficient documentation to support compliance with the requirements.
- Non-compliant: It has been confirmed that the requirements are not met.
- Pending Clarification: Insufficient information; awaiting further details from the supplier.
- Not Applicable: It has been confirmed that this item does not apply to the current product or project.
For critical safety performance requirements, items lacking evidence should not be directly marked as ‘Compliant’.
Furthermore, supplier declarations and objective evidence should be recorded separately. Even if a supplier claims compliance, the status should remain ‘Pending Confirmation’ if the test reports or technical documentation for the relevant model are incomplete.
Step 7: Establish a Deviation Register Before Order Confirmation
The Technical Deviation Register is used to record discrepancies between the supplier’s proposal and the purchaser’s requirements.
In project procurement, a technical deviation does not necessarily mean that the supplier’s proposal is entirely unacceptable. Certain discrepancies may be resolved through technical clarification, configuration adjustments or project approval.
What must be avoided at all costs is the supplier failing to disclose discrepancies, or the procurement team tacitly accepting them without completing an assessment.
It is recommended that the RFQ explicitly require suppliers to disclose all deviations, using the table below.
| Deviation Number | Buyer’s Original Requirements | Supplier’s Proposed Solution | Description of Deviation | Impact on Price or Delivery Time | Review Status |
|---|---|---|---|---|---|
| DEV-001 | Supply in accordance with the specified test scope for the project | To be completed by the supplier | Describe the specific deviation | Indicate the impact | Pending review |
| DEV-002 | Provide evidence in accordance with the specified standards and versions | To be completed by the supplier | Explain discrepancies in standards or evidence | Specify impact | Pending review |
| DEV-003 | Include specified control levers and adaptors | To be completed by supplier | Explain configuration discrepancies | Specify impact | Pending review |
| DEV-004 | Submit specified technical documentation | To be completed by the supplier | Describe missing or substitute documents | Specify the impact | Pending review |
For each deviation, the following questions must be answered as a minimum:
- What are the specific differences compared to the buyer’s requirements?
- Why has the supplier proposed this solution?
- Does it affect the product’s suitability, performance or test evidence?
- Does it affect price, delivery time, accessories or maintenance requirements?
- Does the buyer accept this deviation?
- Is it necessary to update the technical specifications, drawings or order attachments?
Technical deviations that have not been approved by an authorised person should not automatically become final supply requirements.
It is recommended that the approved deviation register be included as part of the technical annex to the contract or purchase order, and that version confirmation be completed prior to production.
Step 8: Compare Supplier Quotations on an Equal Technical Basis
When multiple suppliers submit quotations, technical criteria should first be standardised before comparing commercial terms.
The following is an example of a procurement evaluation. The suppliers and evaluation results in the table are illustrative only and do not represent actual JINPOWER clients or project records.
| Evaluation Criteria | Supplier A | Supplier B | Supplier C |
|---|---|---|---|
| Product model clearly specified | Compliant | Compliant | To be confirmed |
| Testing principle matches | Complies | To be confirmed | Does not comply |
| Applicable standards clearly defined | Complies | Complies | Information missing |
| Test evidence complete | Compliant | Partially provided | Information missing |
| Control lever and accessories complete | Compliant | Partially provided | Compliant |
| Technical deviations disclosed | No deviations | Disclosed | Not specified |
| Comprehensive technical assessment | May proceed to subsequent approval | Clarification required | Not approved at this stage |
This example illustrates that quotation amounts cannot be compared in isolation from the technical specifications.
If a supplier’s price is lower but does not include necessary accessories, the test reports provided do not correspond to the actual model, or significant technical deviations have not been disclosed, then their quotation is not directly comparable with those offering a complete configuration.
The procurement team should first complete a technical compliance audit before comparing price, lead time, packaging, payment terms and other commercial conditions.
For project procurement, it is also essential to confirm that the final quotation, technical specifications, drawings and bill of materials are all based on the same version, to avoid changes to the actual order after technical approval has been granted.
How JINPOWER Supports High Voltage Detector RFQ Review
JINPOWER supplies electrical safety equipment for applications in the power sector, substations, power transmission and distribution, railways and industrial electrical maintenance.
For the procurement of voltage detectors, JINPOWER’s current product pages include the AC High Voltage Detector product range, as well as the DC Voltage Electroscope product range equipped with insulated operating rods. The voltage configurations, detection methods, operating rod lengths and technical documentation requirements for different products should be confirmed according to the specific model.
For example, JINPOWER’s currently published DC Voltage Electroscope with Insulated Operating Rod product range lists 0.75 kV, 1.5 kV, 4.8 kV and 10 kV DC configurations, and specifies that the product utilises an insulated FRP operating rod, equipped with audible and visual indicators and a Manual Self-Test function.
These configurations represent different product options and do not imply that a single electroscope automatically covers all the voltage ranges listed above. Purchasers must still confirm the appropriate model based on the actual DC system, test points, required operating distance and project requirements.
For AC electroscopes, it is similarly necessary to confirm the system voltage, testing principle, applicable standards, contact conditions and relevant test documentation based on the specific application. The parameters or standards of DC products must not be directly applied to AC products.
At the RFQ stage, it is recommended that customers, where possible, provide the following information:
- Project application scenario and target electrical system.
- AC or DC, and the actual rated voltage.
- Required testing range and test points.
- Specified testing principles or technical specifications.
- Whether an insulated operating pole is required.
- Target length, interface and accessory requirements.
- Applicable standards and versions.
- Requirements for test reports, markings and other technical documentation.
- Purchase quantities, delivery times and packaging requirements.
JINPOWER can assist in verifying technical specifications, the scope of supply and any matters requiring further clarification, based on the confirmed product configuration and project requirements. For testing methods or standards that have not yet been finalised, technical confirmation should be completed before proceeding to the final quotation and order approval.
To view the current product range, please visit JINPOWER Voltage Detector Product Categories.
Copyable High Voltage Detector RFQ Template
The template below can be used directly as a base version for a purchase enquiry document. The buyer may delete any fields that are not applicable based on the actual circumstances of the project and enter the confirmed technical requirements into the ‘Buyer Requirement’ column.
| Project | To be completed by the buyer / To be replied to by the supplier |
|---|---|
| Project Name | |
| Project Location | |
| Application | |
| Electrical System | AC / DC |
| Nominal Voltage | |
| Required Detection Range | |
| Frequency | If applicable |
| Detection Principle | Specified solution / Supplier’s recommendation |
| Contact Requirement | Contact / Non-contact / To be confirmed |
| Detection Point | |
| Indication Method | |
| Functional Check Requirement | |
| Operating Pole Required | Yes / No |
| Pole Type and Length | |
| Detector Fitting / Adapter | |
| Environmental Conditions | |
| Applicable Standard and Edition | |
| Test Report Requirement | |
| Technical Datasheet | Must be provided / Other requirements |
| Product Drawing | Must be provided / As per project requirements |
| Marking Requirement | |
| Required Accessories | |
| Quantity | |
| Delivery Requirements | |
| Packaging Requirements | |
| Language of Documentation | |
| Technical Deviations | None / See Deviation Register |
| Supplier’s Proposed Model | |
| Supplier’s Actual Specification | |
| Supplier Document References | |
| Final Compliance Status | Compliant / Non-compliant / To be confirmed |
When using this template, it should be made clear which fields must be completed by the buyer and which by the supplier. For technical parameters that the buyer is unable to determine, the supplier may be asked to propose a solution; however, this must be reviewed and confirmed by the buyer or the project’s technical lead.
This template is intended to standardise request for quotation (RFQ) information and does not replace specific product standards, design documents or on-site safety procedures.
Common Mistakes When Preparing a High Voltage Detector RFQ
Only Stating the Voltage Rating
The voltage rating alone cannot determine the detection principle, AC/DC compatibility, detection location or the full scope of supply.
Stating Only “IEC Compliant”
This fails to specify the relevant sections and versions of the applicable standards, nor does it clarify what evidence the supplier is required to submit.
Leaving the Detection Point Undefined
Different equipment configurations and detection locations may require different detection methods, interfaces or accessories.
Ignoring the Operating Pole
If the project requires the detector to be used in conjunction with an insulated operating pole, the interfaces, length, compatibility and corresponding documentation must be confirmed.
Accepting “Comply” Without Technical Values
Suppliers should provide actual parameters and the corresponding technical documentation, rather than merely repeating the buyer’s requirements.
Failing to Request a Deviation Register
Failure to list technical deviations separately may prevent a fair comparison between proposals from different suppliers.
Comparing Prices Before Technical Review
Low-cost quotations lacking necessary accessories, test evidence or a complete configuration should not be directly compared with comprehensive technical proposals.
Changing Specifications After Approval Without Revision Control
Technical specifications, drawings, test documentation and order configurations must remain consistent. Where changes occur, their impact must be reassessed and the results of approval documented.
FAQ: High Voltage Detector RFQ Requirements
What information should be included in a High Voltage Detector RFQ?
At a minimum, the project application, AC/DC system, nominal voltage, required detection range, detection principle or solution requirements, detection location, applicable standards, operating lever and accessory configuration, test documentation, quantity and delivery time should be specified. Specific fields should be adjusted according to product type and project requirements.
Should the buyer specify the detection principle or let the supplier choose?
If the project’s technical specifications have already determined the detection principle, this should be explicitly stated in the RFQ. If it has not yet been determined, suppliers may be asked to propose solutions; however, the applicable conditions, technical basis and limitations must be specified, and these must be approved by the project’s technical lead.
Is a voltage rating sufficient to compare different detector quotations?
No. It is also necessary to compare the detection principle, system type, scope of applicable standards, product configuration, control lever compatibility, technical documentation and any deviations. Only when the technical scope is broadly consistent does a comparison of quotations hold practical significance.
What is the purpose of a Technical Compliance Matrix?
It links the buyer’s requirements, the supplier’s declarations, corresponding evidence and audit status, helping the procurement team to identify non-conformities, missing documentation and matters requiring clarification.
Why should suppliers submit a Deviation Register?
The Deviation Register enables technical discrepancies to be disclosed prior to order confirmation and records the causes, impacts and approval status, thereby preventing unauthorised alternatives from entering the final supply configuration.
Should the test report be requested before or after ordering?
It is recommended that suppliers be required to provide applicable existing test evidence during the technical approval stage, whilst clearly defining the requirements for final delivery documentation. The specific report format and submission timeline should be stipulated in the RFQ, contract and inspection plan.
Does the detector test report also serve as proof for the insulated operating pole?
Not necessarily. The detector unit and the separate insulated operating pole may require separate verification against applicable standards and technical evidence.
If both are supplied as a complete assembly, interface compatibility and the scope of certification for the complete configuration should also be confirmed.
Final Recommendation: Turn the RFQ Into a Controlled Technical Document
A valid High Voltage Detector RFQ is not merely a document through which the procurement department requests quotations from suppliers; it also serves as the basis for engineering, quality, procurement and suppliers to jointly confirm technical requirements.
It is recommended that the procurement process be standardised as follows:
Project Requirements Confirmation → RFQ Technical Specification Sheet → Supplier Technical Response → Technical Compliance Matrix → Deviation Register → Technical Approval → Commercial Comparison → Order Configuration Confirmation → Acceptance of Delivery Documentation.
Within this process, the buyer is responsible for clarifying project requirements and approving standards; the supplier is responsible for providing accurate product parameters, declarations of conformity and corresponding evidence; and technical reviewers are responsible for determining whether any deviations are acceptable.
For the procurement of voltage testers by JINPOWER, it is recommended that the AC/DC specifications, test tasks, product models, joystick configurations, applicable standards and test documentation requirements be clarified at the quotation stage. Any technical options that remain undetermined should be clarified during the quotation stage, rather than being addressed only at the production or delivery stage.
The key to procurement quality lies not in the number of quotations received, but in ensuring that each quotation corresponds to clear, verifiable and traceable technical requirements.


