ELEVGRID / PROCUREMENT REFERENCE
Standards &
Compliance
Define the requirement.
Agree the evidence.
Start your enquiry with the applicable standards, editions, project specifications and destination requirements. Confirm the compliance scope for the specific product and contract before treating it as agreed.
Share your requirementsReview the planning checklist
- 01Define
Product · destination · standard edition
- 02Resolve
Document precedence · gaps · deviations
- 03Record
Agreed scope · review · supporting evidence
Review framework only. Requirements and deliverables depend on the product, project, contract and destination.
02 / REQUIREMENT REVIEW
Confirm the Applicable Standard Early
Keep five different questions visible. None should be treated as a substitute for the others.
- Standard requirements
- The technical requirements in the identified standard and applicable parts. Record the designation, edition and amendments relevant to the equipment.
- Product design conformity
- The assessment of a specific offered design against agreed requirements, supported by relevant technical documents. A standards reference alone does not establish conformity.
- Project technical specification
- The buyer’s or utility’s requirements for the actual duty, interfaces, performance and acceptance. Identify revisions, additions and conflicts.
- Testing & FAT
- Verification activities with an agreed scope and acceptance criteria. A test record supports the matters tested; FAT does not establish every aspect of compliance.
- Certificates & third-party evidence
- Separate evidence with a defined issuer, scope and equipment coverage. Availability, validity and acceptance must be checked for the project.
03 / REQUIREMENT REVIEW
IEC, IEEE/ANSI and Project-specific Requirements
IEC references
Identify the relevant IEC standard and part for the product. For example, IEC 60076-1 addresses general requirements for power transformers within its defined scope; it is not a blanket reference for every item in a supply package.
IEEE / ANSI references
Specify the exact document, not only “ANSI compliant.” For example, IEEE C57.12.00 addresses general requirements for liquid-immersed distribution, power and regulating transformers. ANSI does not itself certify products.
Project-specific requirements
Provide utility specifications, employer’s requirements, datasheets and interface documents. Identify additional requirements and review conflicts with the cited standards before agreement.
These are reference examples, not a declaration that any offered product complies with them. Applicable documents and editions must be confirmed for each product and project.
04 / REQUIREMENT REVIEW
Standard Edition and Project Specification Hierarchy
Make the baseline explicit
Record the standard number, part, publication year, edition and applicable amendments or corrigenda. Include any required national adoption and its identifier.
Avoid leaving “latest edition” undefined. Agree the reference date and review the effect of a later revision before changing the contract baseline.
There is no universal order of precedence between project documents. Confirm it in writing. A contractual agreement cannot waive a mandatory destination requirement.
PRECEDENCE REVIEW / NOT A FIXED RANKING
Destination obligations
Identify applicable mandatory requirements and the responsible authority.
Document order
Agree how contract specifications, utility documents, datasheets and referenced standards relate.
Revisions & exceptions
Link agreed editions to approved clarifications and permitted deviations.
05 / REQUIREMENT REVIEW
Destination-market and Utility Requirements
Check destination requirements alongside the technical specification. Depending on the equipment and market, the review may include efficiency, safety, environmental, installation and marking requirements.
Identify the destination
Provide the country or region, installation location, intended service and equipment category. Local requirements may depend on these details.
Provide utility conditions
Share utility standards, connection rules, approved equipment requirements and review contacts where applicable. Confirm whether project or vendor approval is required.
Allocate responsibility
Agree who identifies applicable obligations, prepares submissions, obtains approvals and reviews evidence. Confirm any language, marking or document-format requirements.
06 / REQUIREMENT REVIEW
Evidence and Document Requirements
Agree the document register before commitment: document or evidence type, equipment scope, issuer, revision, submission stage, reviewer and acceptance basis.
- Design documents
- Agreed datasheets, drawings and relevant design substantiation, where required. Match each submission to the offered equipment and controlled revision.
- Compliance response
- A requirement-by-requirement response where agreed, identifying supporting documents, exclusions, deviations and open points. A response matrix is not third-party certification.
- Test records
- Reports relevant to the required tests and equipment. Check test basis, identity, date, results and acceptance criteria; confirm any use of representative-design evidence.
- Third-party evidence
- Where required, confirm the issuer, report or certificate identifier, covered model and scope, applicable standard edition, validity or status, and destination acceptance. Verify through the issuing body where possible.
- Declarations & final records
- Any declaration, marking documentation or final dossier is subject to the applicable product and market requirements and the agreed contract deliverables.
Evidence availability and disclosure must be confirmed. This page is a procurement guide and does not present a certificate register or verified product approvals.
07 / REQUIREMENT REVIEW
Deviations and Clarification
Resolve exceptions before commitment
Identify missing inputs, conflicting clauses and proposed alternatives during the enquiry review. Describe the affected requirement and the technical or commercial effect; do not treat silence as acceptance.
Acceptance must come from the authorized project party and cannot override mandatory obligations. Keep unresolved items visible until a written disposition is recorded.
SUGGESTED CLARIFICATION RECORD
- Reference
- Document · revision · clause · equipment
- Proposal
- Required condition · proposed alternative · reason
- Impact
- Design · evidence · interfaces · cost / schedule, if affected
- Disposition
- Owner · written decision · date · affected baseline revision
08 / REQUIREMENT REVIEW
Relationship Between Compliance, Design Review and FAT
Use one agreed baseline across the stages. This page defines the requirements and evidence to discuss; detailed test planning belongs in the separate Testing & FAT scope.
Compliance basis
Defines what applies and what evidence is required for the product, project, contract and destination.
Design review
Checks the proposed technical solution against that basis and records comments or approval conditions. Review does not remove other applicable obligations.
Testing & FAT
Verifies the agreed test scope against defined criteria and produces relevant records. Test execution, witnessing and release arrangements are agreed separately.
Carry the same requirement references and equipment revisions through each stage. A design approval or successful FAT does not, by itself, prove all destination approvals or certifications.
09 / REQUIREMENT REVIEW
Buyer Standards Checklist
Use this list to prepare your enquiry. Mark unknown items “To be confirmed” so they remain visible during review.
- 01
Equipment & duty
Identify the product, ratings, installation conditions and supply interfaces.
- 02
Standards & editions
List exact designations, parts, years and applicable amendments.
- 03
Project documents
Provide specifications, datasheets and utility requirements with revisions.
- 04
Document precedence
State the agreed order or flag conflicts for clarification.
- 05
Destination & approvals
Identify the country, utility and known approval or marking requirements.
- 06
Evidence & acceptance
List required records, certificates or third-party involvement and the review criteria.
- 07
Deviations & open points
Identify proposed exceptions, missing information and decision owners.
- 08
Submission responsibilities
Agree who supplies and reviews documents, in which language and at which stage.
Requirement / Review / Evidence
Connect requirements with project controls.
Quality & Project Control
Record the agreed technical baseline, document revisions and review responsibilities.
Define verificationTesting & Factory Acceptance
Clarify how the applicable requirements will be checked and recorded.
Review a product reference35kV Oil-Immersed Power Transformer
Use a published transformer reference to prepare product-specific questions, not as proof of certification.
10 / REQUIREMENT REVIEW
Bring Your Standards into the Enquiry
Share your specification, required standard editions, destination and evidence expectations through the existing RFQ.
Submit project requirements Explore product requirementsFinal applicability, design conformity, evidence availability and any approval obligations are to be confirmed for the specific product, project, contract and destination.