Start with the buyer requirement, controlled drawings, requested documents, commercial scope, and response format. Quotations need a common controlled baseline before their stated scope can be compared.
Read the FUERTE product family as route context only. Related evidence topics include the fuse cutout RFQ checklist and the fuse cutout receiving inspection guide.
Important: A quotation comparison does not authorize protection settings, installation, or energization; follow the owner process and qualified responsible personnel. (IEC Webstore)
Part 1. Define the comparison baseline
Start with the buyer requirement, controlled drawings, requested documents, commercial scope, and response format. A quotation cannot be compared fairly when every bidder receives a different or incomplete baseline.
Part 2. Give each bidder a separate response line
Use one line for each requirement, with fields for the offered identity, source document, stated exception, and buyer disposition. Do not allow an assumption in a catalogue attachment to replace a response against the actual line.
Part 3. Separate omissions from declared deviations
A missing answer and an explicit difference need different follow-up. Record an omission as open; record a deviation with the supplier explanation and the accountable project disposition.
Part 4. Do not convert comparison into coordination
A bid schedule can show whether a supplier addressed a request. It does not establish protection coordination, interrupting duty, installation suitability, or system approval.
Part 5. Make commercial and document scope visible
Record quantity basis, delivery assumptions, included accessories, document status, and any required clarification. Keeping these fields alongside the technical request prevents a price-only comparison.
| Deviation-register field | Buyer baseline | Bidder response |
|---|---|---|
| Requirement line | Controlled scope reference | Exact offered identity |
| Evidence source | Requested file or drawing | Revision and source cited |
| Difference status | Open or stated deviation | Explanation and limitation |
| Disposition | Responsible project path | Response date |
| ## Part 6. Use FUERTE pages as quote-context routes |
The cited product page may be used to request current model documents once a buyer has a defined line item. It does not prove that an unpublished or visually similar configuration is acceptable.
Product recommendation: use the FSC-12-3 Drop Out Fuse Cutout route only for a model-specific document inquiry after the evidence package is complete.
Part 7. Issue the deviation register with the RFQ
Include the baseline, response table, deadline, and a request for every limitation to be cited against a line. Escalate unresolved differences through the project review process before award.
For a quote-deviation review, contact FUERTE with the controlled response table, baseline documents, and named questions.
FAQ
What is a fuse cutout quote deviation schedule?
It is a line-by-line record of the buyer request, offered response, evidence source, difference, and disposition.
Why not compare quotations by price alone?
Price does not show whether the quotations describe the same documented scope.
What counts as a deviation?
A stated difference from the controlled requirement that needs a recorded review path.
How should an omission be recorded?
Keep it open and request a response; do not assume the omitted requirement is included.
Does a schedule approve protection coordination?
No. Coordination requires the responsible engineering evidence and decision.
Can a public product page replace a bid response?
No. It is route context, while the bidder must identify the exact offered configuration.
Which FUERTE page can support a document request?
Use the cited product page after the buyer has assembled a controlled inquiry.
Can this guide authorize installation?
No. Installation and energization decisions are outside a quotation comparison.
References
- IEC Webstore: vocabulary context for controlled quotation responses.
- CIGRE ELECTRA: publication context for documented bid exceptions.