Name the buyer requirement, drawing revision, issue date, and response deadline before comparing documents. A file title without its revision relationship is not a controlled project reference.
Read the FUERTE product family as inquiry-route context. For nearby evidence topics, see the VCB nameplate RFQ checklist and VCB panel specification guide.
Important: A revision register does not authorize VCB installation, protection settings, or energization. The owner process and qualified responsible personnel control those decisions. (IEC Webstore)
Part 1. Define a revision baseline
Name the buyer requirement, drawing revision, issue date, and response deadline before comparing documents. A file title without its revision relationship is not a controlled project reference.
Part 2. Link every document to the offered identity
Require the quotation, drawing, data sheet, and deviation response to identify the same offered configuration. A family image or a generic VCB label cannot establish that connection.
Part 3. Record superseded files as history
Keep prior files in the register with their superseded status, rather than mixing them with current evidence. This makes an unresolved difference visible to the responsible reviewer.
Part 4. Separate document control from breaker duty
A revision register does not confirm interrupting duty, protection coordination, interlocking, installation fit, or project approval. Those decisions need the applicable engineering evidence.
Part 5. Use a controlled document register
Give each requirement line an expected file, buyer revision, bidder source, current status, and clarification owner. This makes an omission distinguishable from a stated deviation.
| Revision-control field | Buyer record | Bidder response |
|---|---|---|
| Required file | Document title and buyer revision | Source and current revision |
| Offered identity | Quotation configuration reference | Matching record reference |
| Change status | Current, superseded, or open | Difference and limitation |
| Disposition | Responsible review path | Response date |
| ## Part 6. Route the complete record to a model inquiry |
A FUERTE product route can support a request for current documents for an identified offered model. The page is not evidence that a model matches a panel or system.
Product recommendation: use the Column Vacuum Circuit Breaker route only for a model-specific documentation inquiry after the controlled record is complete.
Part 7. Close changes before release
Send the register, project references, quantity, and open questions with the RFQ. Ask bidders to name all exceptions and identify the source document for every response.
For document revision control, contact FUERTE with the register, current project references, and unanswered lines.
FAQ
What is VCB document revision control?
It is the practice of linking each required record to a current revision and the exact offered configuration.
Can a data sheet alone control a quotation?
No. Its revision and relationship to the quotation, drawing, and requested scope must be recorded.
Why retain superseded files?
They explain the history of a change while preventing an old file from being treated as current evidence.
Does a register prove breaker duty?
No. Duty and project fit require separate engineering review.
What should an RFQ register contain?
Use requirement line, requested file, buyer revision, bidder source, status, and clarification owner.
Can a product image confirm a model?
No. Ask the bidder to identify the exact offered configuration and documentation.
Which FUERTE route supports a request?
Use the cited product page only after the buyer has a controlled document package.
Does this article approve a VCB?
No. Approval belongs to the responsible project process.
References
- IEC Webstore: vocabulary context for controlled VCB document records.
- CIGRE ELECTRA: industry publication context for document revision review.