The bottom line — approval rule: Corning fiber patch cord alternatives are not approved by similarity alone. The project needs written substitution authority, an exact Corning source record, candidate-specific evidence, a disposition for every deviation, defined sample and production hold points, a warranty decision where relevant, and change-control rules. An incomplete record means the candidate is still pending.
There is no universal replacement for a Corning part number. Approval applies to one identified source part, one candidate configuration, and one defined project scope. The person or role authorized by the project must accept the evidence and any remaining conditions.
This page covers that approval task. Connector, polish, fiber, construction, jacket, and length selection belong in the BWNFiber fiber patch cord category and specification guide. Keeping those subjects separate prevents a controlled substitution review from turning into a generic patch-cord tutorial.
By BWNFiber Technical Content Team. Updated for publication on August 30, 2026.
In this guide
- Approval rule and 30-second screen
- Permission and decision owners
- Controlling Corning source record
- Evidence index, deviations, standards, and warranty
- Sample and production hold points
- Requalification triggers
- Supplier comparison and commercial release
- International project localization
- Final approval pack and worksheet
- BWNFiber candidate response
- Inquiry input
- Approval FAQ
What does a Corning fiber patch cord alternative need for approval?
A supplier cross-reference starts a review; it does not complete one. Before procurement treats a candidate as purchase-ready, the approval file should answer five questions:
- Does the contract or project specification permit a substitute?
- Who has written authority to approve it?
- Which exact Corning record controls the comparison?
- Which candidate differences remain, and who has disposition authority?
- Which later changes would reopen the approval?
Mark the candidate pending whenever an answer is missing. Resolve the record before using "equivalent" in a commercial release.
Procurement summary
For a procurement team, the review begins with the exact Corning part number and the project clause that permits alternatives. The candidate must then be tied to a controlled drawing, current datasheet, required test records, and a deviation log. Compare price and lead time only after technical status is clear. A passed sample does not release production unless the approved identity, test scope, labels, records, purchase-order conditions, and change-notification rules remain aligned. The project owner—not the supplier—decides whether the recorded evidence supports approval for the stated scope.
How to evaluate an alternative in six controlled steps
- Confirm that the governing project record permits a substitute and names the approval authority.
- Freeze the exact Corning part number, source document, revision, application, and mandatory project clauses.
- Identify one exact candidate part and map candidate-specific documents to every controlling requirement.
- Classify each field as matched, deviation, unknown, or not applicable; obtain written disposition for every open item.
- Release samples, pilots, or tests only against an approved plan, then link the accepted sample to the production identity.
- Carry the approval scope, conditions, records, receiving checks, and change-notification triggers into the quotation and purchase order.
30-second procurement screen
| Status | Minimum record state | Procurement action |
|---|---|---|
| Stop | The project does not permit a substitute, the exact Corning source is unknown, or no approval owner is identified | Do not request a production quote or sample as an approved equal |
| Pending | Substitution may be reviewed and exact source and candidate records exist, but evidence, deviation, sample, warranty, or authority questions remain open | Assign each gap, due date, and disposition; keep price separate from approval status |
| Ready for controlled commercial comparison | The candidate has an approved or conditionally approved scope, traceable evidence and sample status, a warranty decision where relevant, and defined release/change controls | Compare normalized quotations and carry every condition into the PO and receiving plan |
Five conclusions to retain
- Matching connector names or a supplier cross-reference does not establish equivalence.
- A standard defines only the interface, method, or requirement within its scope; it does not prove the offered candidate meets an exact source part.
- A passed sample covers only the approved sample plan and identity; it does not automatically release production.
- Technical acceptance and third-party system-warranty eligibility require separate recorded decisions.
- A change to the candidate part, component source, construction, process, test method, site, label, record, or project scope can reopen approval.
Preparing a controlled substitution request? Send the source part number, current source datasheet, governing project clause, quantity, and required approval format. Ask BWNFiber whether it can provide a candidate-specific evidence review for the offered configuration. A usable reply should mark each requested record as available, different, unknown, not available, or still required. The project's authorized approver retains the final decision.
Can the project accept a substitute, and who decides?
The wording around the named brand determines whether an alternative may be evaluated. The governing document also determines who may accept it.
Project language and the required route
| Project language or condition | Procurement meaning | Required action |
|---|---|---|
| Corning part number with no substitution language | The document identifies an item but does not establish a substitution route | Ask the document owner whether a formal deviation is allowed before requesting samples |
| "Corning or approved equal" | A candidate may be reviewed, but it is not accepted in advance | Obtain the required evidence, workflow, and signatory in writing |
| Performance-based specification | The stated requirements may control even when a brand is used as a reference | Map each mandatory requirement to candidate evidence and log every exception |
| Registered system or extended-warranty project | Technical acceptance and program eligibility may require separate decisions | Ask the program owner or qualified installer about the exact component and retain the dated response |
| Maintenance spare for an installed asset | The asset owner's compatibility and spares policy may control | Confirm the installed interface, asset record, service procedure, and approval owner |
This is a procurement-control framework, not legal advice. Contract interpretation remains with the project owner and its authorized advisers.
Decision owners
Approval should identify a person or controlled role, not a note that says only "engineering approved."
| Decision | Possible project owner | Record to retain |
|---|---|---|
| Permission to evaluate a substitute | Project owner, consultant, engineer of record, or customer-designated approver | Name or role, governing clause, and written decision |
| Technical acceptance | Network, optical, or cabling engineer | Requirement set, deviations, acceptance method, and result |
| System-warranty impact | Program owner, authorized installer, or brand representative | Program, geography, registration status, component decision, and response date |
| Commercial release | Procurement | Approved candidate part number, scope, price basis, and conditions |
| Incoming and production acceptance | Buyer QA or designated inspection owner | Inspection plan, record format, disposition authority, and retention period |
| Candidate evidence | Supplier | Candidate datasheet, drawing, declarations, records, and change-notification commitment |
The supplier is responsible for describing its candidate and supporting the claim with records. It cannot approve that candidate on behalf of the customer, consultant, warranty program, or government specification.
Which Corning source record controls the comparison?
Do not begin with a shortened description such as "LC-LC Corning cord." Freeze the source identity first:
- original manufacturer and full part number;
- source datasheet title, revision, and retrieval date;
- RFP, BOM, drawing, submittal, or asset-record location;
- applicable project clause and approved-equal language;
- original application and installed-system context;
- mandatory documents and acceptance records;
- warranty or approved-vendor program, if applicable.
Corning's official Cable Assemblies Configurator creates part numbers from multiple attributes. Its fiber-optic cable assembly portfolio also separates indoor, outdoor, single-fiber, two-fiber, and multifiber families. These sources are useful for source identification, but the project still needs the controlling document for the exact part under review.
If that document is unavailable, request it from the project owner, Corning, or an authorized source. A distributor description, old screenshot, jacket color, or partial BOM line does not establish the source requirement. Record the missing information as unknown until the project defines a controlling record.
Does the source and candidate belong to the same approval class?
Classify the source and candidate before comparing details. This is not a generic product-selection exercise; it is a check that the review route covers the actual assembly being offered.
| Assembly class | Approval implication |
|---|---|
| Conventional single-fiber or duplex patch cord | Compare both interfaces, polish, fiber, cable construction, length, jacket, labels, optical acceptance, and records for the exact parts |
| Hybrid-ended or uniboot assembly | Add end-A/end-B identity, duplex orientation, polarity or reversibility, boot and clip details, and equipment-side fit to the evidence index |
| Multifiber or MPO/MTP assembly | Use a separate multifiber review that identifies fiber count, gender, key orientation, polarity method, end-to-end map, and transceiver or cassette context |
| Hardened, lockable, keyed, FTTA, or outdoor assembly | Treat mechanical interface, sealing, environmental construction, mating hardware, installation method, and any required listing as separate evidence fields |
| Pre-terminated trunk, breakout, or fanout assembly | Do not reduce the review to a patch-cord description; control fiber count, breakout, fanout, pulling method, length, protection, end mapping, and installation acceptance |
If no documented candidate matches the required class, move the request to a controlled custom-design route. Approve the candidate drawing, evidence plan, sample scope, and production controls before describing the custom assembly as an alternative.
How should the approval file be built?
Build the file from traceable requirements, not from two marketing descriptions placed side by side.
Four evidence statuses
- Matched: candidate evidence answers the controlling requirement without an identified difference.
- Deviation: the candidate differs; the difference needs an owner and written disposition.
- Unknown: evidence is missing, ambiguous, expired, or not tied to the offered candidate.
- Not applicable: the requirement does not apply, and the reason is recorded.
Evidence-index fields
| Evidence-index field | Required entry | Control purpose |
|---|---|---|
| Requirement ID | Clause, BOM line, drawing note, or source-datasheet location | Keeps the review tied to the controlling record |
| Source requirement | Exact requirement or concise traceable restatement | Shows what the candidate must answer |
| Candidate document | Title, revision, date, and candidate part number | Ties evidence to the offered item |
| Status | Matched, deviation, unknown, or not applicable | Exposes unresolved items |
| Difference or gap | Specific description without "similar" or "equivalent" | Defines the decision that remains |
| Owner and due date | Named project or supplier role | Keeps an open item visible through quotation and release |
| Disposition | Accept, reject, test, clarify, or revise | Records the required action |
| Approval evidence | Signature, controlled workflow record, or written authorization | Identifies who accepted the final state |
Interface, optical, construction, listing, labeling, documentation, and program conditions should be taken from the source and project records. For the underlying patch-cord specification fields, use the BWNFiber patch cord guide instead of recreating that selection content here.
Technical evidence fields for the offered assembly
The evidence index needs enough technical detail to show whether the source and candidate are the same, different, or still unknown. Record only what the controlling documents require; do not fill a blank with a typical market value.
| Technical evidence field | What to record for the source and candidate | Unsafe inference to avoid |
|---|---|---|
| Fiber designation | Single-mode or multimode; the exact OS or OM category and the exact ITU-T designation when stated, such as G.652.D, G.657.A1/A2, OM3, OM4, or OM5 | Do not treat OS2 and an ITU-T fiber designation as interchangeable labels, or assume that different OM categories are equivalent |
| Optical interface | Connector style, interface or keying, polish, fiber count, polarity, and pin or gender condition when applicable | Do not infer the complete interface from connector color, a family name, or "LC-LC" alone |
| Optical acceptance | Source requirement for attenuation or insertion loss, return loss, test wavelength, method, reference method, equipment, limit, and sample scope | Do not copy a fiber attenuation value into an assembly insertion-loss field or accept "tested" without a method and limit |
| Assembly construction | Cable construction, outside diameter, buffer or subunit type, including tight-buffered construction when stated, strength member, jacket, minimum bend radius, and tensile or crush requirement when the source record makes them relevant | Do not borrow construction or mechanical values from a nearby part number |
| Environment and listing | Indoor or outdoor use, route, temperature, flame or listing requirement, jacket material, LSZH claim, UV exposure, water ingress, rodent protection, and armor when applicable | Do not treat LSZH, flame performance, UV resistance, water blocking, rodent protection, and armor as equivalent claims |
| Identification and records | Drawing revision, label, length tolerance, serial or lot traceability, packaging, inspection record, and test-record format | Do not approve a sample whose identity cannot be tied to the production record |
| Standards evidence | Exact standard, edition, clause or category, test or declaration, and candidate part to which it applies | Do not accept a supplier's standards list as part-specific evidence |
Corning's assembly portfolio includes single-mode designations such as G.657.A1 and G.652.D and multimode categories through OM5 across different assembly families. That variety is a reason to copy the exact source designation, not a basis for assuming that one category can replace another. The current ITU-T G.652 and ITU-T G.657 Recommendations define different single-mode fiber characteristics; the project still decides which designation the candidate must meet.
Record the actual application, such as data center, enterprise, central office or headend, or FTTH/FTTP, because it determines which project conditions matter. The application name does not prove that a candidate is equivalent.
ADSS, duct, direct-burial, loose-tube, and general drop-cable selection normally belong to optical-cable design, not to a standard patch-cord substitution review. Bring those entities into this file only when the exact Corning source part is an outdoor, hardened, armored, or drop cable assembly and the governing record makes those properties mandatory. Otherwise, route the engineering question to the relevant cable guide, such as the armored and outdoor fiber patch cord guide.
Illustrative review example, not a BWNFiber customer case: If the source record specifies G.657.A1 and the candidate drawing says only "OS2," the fiber requirement remains unknown until candidate-specific evidence identifies the fiber designation accepted by the project. If a jacket is described only as LSZH, any separate flame, UV, water-ingress, or rodent-protection requirement also remains open until its own evidence is supplied.
What can each document prove?
Not every document has the same evidentiary weight. Use the strongest record available for each requirement, and state what the record does not establish.
| Document or record | What it can support | What it cannot establish by itself |
|---|---|---|
| Current source-part datasheet or controlled drawing | The documented attributes of the identified Corning source part | The candidate's construction, performance, listing, or approval |
| Current candidate-part datasheet or controlled drawing | The supplier's documented description of the exact offered candidate | That the stated values were measured on the submitted sample or accepted by the project |
| Candidate-specific test report | Results for the identified sample, method, conditions, equipment, limits, and date stated in the report | Production consistency, another revision, or a requirement the test did not examine |
| Declaration, certificate, or listing record | The stated scope, standard, facility, product, date, and status when those identifiers are present | Unlisted attributes, another product family, or project approval outside its scope |
| Product-family page, configurator, or ordering matrix | Available attributes and a route to identify a source or candidate configuration | The complete requirement or compliance state of an exact part unless the record identifies it |
| Supplier cross-reference or equivalence letter | The supplier's proposed mapping and the claims that need review | Independent acceptance, warranty eligibility, or permission to substitute |
| Approved sample | The characteristics examined under the approved sample plan | Untested characteristics, a different lot or revision, or unrestricted production release |
| Written project approval | Acceptance of the identified candidate for the recorded scope and conditions | Transfer to another part, application, quantity, project, or changed configuration |
When two records conflict, keep the requirement open and ask the document owners to identify the controlling revision. Do not select the more favorable value without a documented basis.
Have both controlled records? Send the exact source and candidate part numbers, document revisions, and open evidence fields to BWNFiber. Ask for a written statement of which candidate-specific records can be supplied and which requirements remain different or unknown. Keep the candidate pending until the project closes those gaps.
The deviation log
Classify a difference as a deviation until the authorized approver accepts, rejects, tests, clarifies, or removes it through a revised offer.
| Deviation-log field | What to record |
|---|---|
| Requirement reference | Exact clause, BOM line, drawing note, or source-record field |
| Source state | What the controlling record requires |
| Candidate state | What the candidate document or sample shows |
| Affected process or risk | The approval, installation, operation, maintenance, traceability, or warranty question created by the difference |
| Proposed disposition | Clarification, revised offer, defined test, conditional acceptance, or rejection |
| Decision owner | Named person or controlled project role |
| Final status | Open, accepted with conditions, rejected, or closed by revised evidence |
Where standards fit
Standards may define an interface, test method, performance framework, or inspection criterion. They are not automatic proof that a candidate satisfies the named source part and project.
- IEC 61754-1:2013 provides general information and guidance for fiber-optic connector interfaces; the applicable interface-family part still has to be identified.
- IEC 61753-1:2018+A1:2020 gives general guidance for passive-component performance standards. The relevant scope, edition, category, and candidate evidence still need to be identified.
- IEC 61300-3-4:2023 describes methods for measuring attenuation of optical components.
- IEC 61300-3-6:2008 presents procedures for measuring return loss of a fiber-optic device under test.
- IEC 61300-3-35:2022 addresses connector end-face visual inspection and states that visual inspection does not replace performance measurements such as attenuation and return loss.
- ANSI/TIA-568.3-E and ISO/IEC 11801-1:2017, including Amendment 1:2025 where applicable, may be relevant to premises cabling requirements when the governing project invokes them. None of these citations replaces the exact candidate record or project clause.
For each cited standard, record its edition, the requirement it supports, the test or declaration supplied, and the offered part to which that evidence applies. A standards list on a marketing page is not a candidate approval record.
A separate system-warranty decision
Technical acceptance does not establish system-warranty eligibility. Corning's EMEA Network of Preferred Installers, for example, describes a regional extended-warranty program involving qualified installers and covered Corning components. That page demonstrates why the applicable program, geography, registration status, and component decision must be checked rather than generalized.
Record the program, region, party consulted, exact substitution question, written response, and date. Include any change in coverage in the commercial comparison. Avoid blanket statements that third-party cords always void coverage or that a standardized interface makes coverage irrelevant.
How do H0-H4 hold points control samples and production?
The H0-H4 model below is proposed for project control. It is not part of an IEC standard or a Corning approval system. The model separates permission, document review, sample acceptance, pilot acceptance, and production release so that a sample cannot silently become an unlimited approval.
| Hold point | Entry condition | Exit evidence | Release authority |
|---|---|---|---|
| H0: Substitution permitted | Governing project record identified | Written permission to evaluate a candidate | Project owner or designated approver |
| H1: Document review complete | Source record and candidate evidence index available | Unknowns exposed; deviations assigned or candidate rejected | Technical approver |
| H2: Sample accepted | Sample plan, method, limits, and identification approved | Recorded physical, optical, documentation, and fit results | Technical approver and QA, as defined |
| H3: Pilot accepted | Representative application and failure criteria defined | Pilot disposition and unresolved-item closure | Project or operational owner |
| H4: Production released | Candidate identity, approved sample, drawing, records, and PO controls aligned | Signed release and incoming-acceptance plan | Procurement plus designated technical or QA owner |
The project must supply the actual measurements, limits, wavelengths, sample quantity, equipment, reference method, and failure rules. They cannot be inferred from the phrase "approved equal."
What should the sample plan test?
The sample plan should follow the open requirements in the evidence index. Depending on the source and project records, it may cover:
- candidate identity, drawing revision, dimensions, interface fit, and keying;
- connector end-face inspection under the specified method;
- attenuation or insertion loss and return loss at the required wavelengths and reference condition;
- polarity, fiber count, labels, length, packaging, and traceability;
- bend, tensile, crush, temperature, flame, UV, water, or other construction checks only when they are mandatory for the offered assembly;
- delivery-record format and the link between the sample ID and the production part.
"OTDR tested" is not a complete acceptance statement. If the project calls for OTDR, record the installed-link or event question it is intended to assess, the method, launch and receive conditions where applicable, and the acceptance rule. Do not use an OTDR trace to replace a separately required component attenuation, insertion-loss, return-loss, or end-face inspection result.
When to stop before sampling
Pause or reject the candidate when:
- the project does not permit an alternative and has no deviation route;
- the source part number or controlling record cannot be identified;
- a proprietary, keyed, lockable, hardened, or ecosystem-specific interface remains unvalidated;
- a mandatory listing, declaration, or program condition is missing;
- the supplier will not identify the candidate part, drawing, revision, or production site;
- candidate evidence covers a family but not the offered part;
- required change notification is refused;
- the project owner will not accept an unresolved contract or warranty risk.
What a passed sample covers
Sample acceptance applies only to what the approved plan examined on the identified sample. It does not transfer automatically to:
- another Corning source part number;
- another candidate part or drawing revision;
- a different connector, fiber, cable, jacket, label, or document package;
- a material, component-source, process, test-method, or production-site change;
- a quantity or application outside the approved scope.
The production release should reference the sample identifier, candidate part, drawing revision, evidence index, deviation log, acceptance plan, and label format. If the delivered item cannot be tied to those records, the approved identity has not been demonstrated.
Which changes trigger patch cord requalification?
Reopen the approval when a change may affect a requirement, evidence record, approved sample, or project condition.
| Change category | Example trigger | Required action |
|---|---|---|
| Product identity | Candidate part number or drawing revision changes | Reopen the evidence index and identify affected requirements |
| Optical interface components | Connector, ferrule, polish process, boot, latch, or keying source changes | Technical review and any affected inspection or tests defined by the buyer |
| Fiber or cable construction | Fiber family or grade, cable design, diameter, strength member, jacket, or listing changes | Review source requirements and repeat affected evidence |
| Manufacturing control | Termination process, test method, acceptance equipment, or production site changes | QA and technical disposition before shipment |
| Documentation | Datasheet, declaration, label, serial, packaging, or test-record format changes | Document-control review and approval |
| Project or program | Application, installed equipment, governing standard, contract, or warranty program changes | New scope decision; prior approval may not transfer |
| Supplier continuity | Subcontractor or component source changes | Stop release until identity and impact are evaluated |
State the notification trigger, decision owner, required notice, and shipment status in the purchase order or quality agreement. Do not leave change notification as an informal supplier courtesy.
What belongs in the commercial release?
The engineering review and the purchase order should point to the same controlled candidate.
Purchase-order references
- source part number and controlling requirement record;
- approved candidate part number and drawing revision;
- evidence index and closed deviation log;
- approval signatures or controlled workflow record;
- sample and pilot disposition, where required;
- acceptance plan and required delivery records;
- labeling, traceability, and packaging record;
- warranty or program decision;
- change-notification and requalification clause.
A purchase order that says only "Corning equivalent" does not preserve the scope, evidence, or conditions accepted during review.
Technical status in the commercial comparison
| Status | Commercial treatment |
|---|---|
| Approved | Compare the offer within its stated approved scope |
| Approved with conditions | Carry every named deviation and open action into the release |
| Pending | Record price if useful, but do not treat the offer as purchase-ready |
| Rejected | Exclude the candidate from a like-for-like purchase comparison |
For candidates with a defined disposition, procurement can compare price, qualification effort, documentation, freight, operational risk, spares impact, and warranty-program effect. A general percentage-saving claim is not reliable across different part numbers, quantities, channels, and project conditions.
How should qualified supplier offers be compared?
Compare suppliers only against the same frozen requirement set. A lower quote is not like for like when another offer excludes evidence, testing, labeling, packaging, change control, or a required commercial term.
| Supplier-comparison criterion | Question the buyer should answer | Evidence to retain |
|---|---|---|
| Candidate identity | Is one exact offered part and drawing revision named? | Quotation, controlled drawing, and document revision |
| Requirement mapping | Does the response address every mandatory source and project field without copying source values into candidate blanks? | Completed evidence index and deviation log |
| Evidence scope | Are datasheets, declarations, listings, and test records tied to the offered part, sample, site, method, and date where applicable? | Candidate-specific records with identifiers and scope |
| Sample and pilot control | Can the submitted sample be traced to the quoted candidate and later production release? | Sample ID, lot, drawing, plan, results, and disposition |
| Production and change control | Are production identity, traceability, notification triggers, shipment holds, and requalification actions defined? | Quality agreement, PO clause, or signed supplier response |
| Warranty or program handling | Does the supplier separate technical evidence from third-party program eligibility? | Written program decision from the authorized party |
| Commercial completeness | Are price basis, quantity, schedule assumptions, inclusions, exclusions, freight basis, and validity explicit? | Comparable quotation schedule |
| Operational fit | Are labels, packing, spares, receiving checks, installation records, and document retention aligned with the project? | Approved release and incoming-acceptance plan |
What should the quotation state about price and delivery?
Request the commercial response against the controlled candidate record, not against a shortened description. The quotation should state:
- exact candidate part number and drawing revision;
- technical status: approved, approved with conditions, pending, or rejected;
- quantity and unit-price basis, including any quantity breaks or MOQ if applicable;
- currency, quotation validity, payment terms, shipping basis, destination, and freight, duties, or tax inclusions and exclusions;
- sample or pilot cost and schedule, where required;
- production lead-time assumption, the event that starts the clock, and dependencies such as drawing, sample, material, or document approval;
- testing, inspection, test-record, labeling, packaging, or special-document charges and inclusions;
- every proposed substitution, exception, or still-open commercial assumption.
Do not insert a standard lead time, MOQ, or savings percentage into the approval file unless it appears in the quotation for the exact configuration and scope. If two suppliers use different schedule start points or shipping bases, normalize those terms before comparing offers.
Common approval mistakes that make a comparison unusable
| Mistake | Why the record fails | Corrective action |
|---|---|---|
| Comparing two family descriptions without freezing exact part numbers | Family options can differ in fiber, interface, construction, listing, test limits, or region | Identify the source and candidate part, drawing, revision, and project clause before comparison |
| Copying a Corning value into an empty candidate field | A source requirement is not evidence of candidate performance | Mark the candidate field unknown and request part-specific evidence |
| Treating jacket labels as interchangeable | LSZH, flame rating, plenum or riser listing, UV, water, rodent, and armor claims answer different requirements | Record and verify each mandatory property separately |
| Testing a sample that is not tied to the offered part and drawing | The result cannot be transferred reliably to the quotation or production record | Identify the sample, candidate part, drawing revision, lot, and test record before testing |
| Accepting a pass/fail report without the method, conditions, and limit | The buyer cannot determine what was measured or whether the project criterion was used | Request the test method, wavelength, reference condition, equipment, limit, result, and sample scope |
| Treating interface compatibility as proof of warranty eligibility | Technical mating and program coverage are separate decisions | Obtain a written, dated program response for the exact project and component |
| Comparing price while the candidate is still pending | The commercial comparison is not yet like for like | Keep the offer pending until deviations, evidence gaps, and conditions have a defined disposition |
| Leaving change notification outside the purchase order or quality agreement | The approved candidate can change without reopening the review | State notification triggers, notice timing, shipment status, owner, and requalification action in the release record |
How should an international project localize the approval record?
Do not approve a candidate against a market label such as "North America," "Europe," or "Middle East." Freeze the country, project location, installed environment, authority, contract, document language, delivery destination, and exact candidate first. Climate and regional practice define questions to investigate; they do not prove a fiber assembly's construction or compliance.
| Market or project location | Questions to add to the approval file | Candidate evidence or decision to retain |
|---|---|---|
| North America | Which country, state or province, authority having jurisdiction, customer standard, premises-cabling requirement, fire-rating requirement, warranty program, and unit or label convention apply? | Exact project clauses; applicable code or standard edition; candidate listing or declaration where required; English/French or other contract language; written warranty-program decision |
| Europe | Is the exact product and intended construction use covered by an applicable harmonised technical specification or European Technical Assessment, and what does the destination country require? | Applicable OJEU-cited reference where relevant; candidate Declaration of Performance and CE information when legally required; declared performance scope; destination-country language and project acceptance record |
| Middle East | Which country, operator, consultant, civil-defense or other authority, tender clause, document language, import marking, and actual indoor/outdoor condition control the project? | Country- and project-specific approvals; candidate records for any stated heat, dust, UV, water, flame, or mechanical requirement; required Arabic/English or other controlled documents |
| Southeast Asia | Which country, telecom or project owner, local authority, building or tender rule, language, and actual humidity, flood, indoor, outdoor, or route condition apply? | Exact tender and operator requirements; candidate-specific environmental and construction evidence only where invoked; required labels, import records, packing, and acceptance documents |
| Latin America | Which country, operator, contract language, local code or tender, customs requirement, destination, and maintenance model apply? | Spanish, Portuguese, or other approved documents as required; candidate declarations and test records; customs/label data; approved spares and receiving plan |
| Africa ISP/FTTH projects | Which country, regulator or operator, donor/EPC tender, inland route, installation environment, document language, spares plan, and receiving capability apply? | Exact tender clauses; candidate-specific heat, dust, humidity, water, UV, or mechanical evidence only when required; robust packing specification, document set, sample disposition, and local receiving plan |
For European construction-product questions, first determine whether the exact product and intended use fall within the applicable framework. The European Commission explains that a Declaration of Performance and CE marking apply to construction products covered by a harmonised standard or an issued European Technical Assessment; that rule cannot be transferred to every patch cord or every intended use by assumption. Use the current European Commission construction-product guidance and the project's legal or compliance owner for the final decision.
Which international commercial terms must be frozen?
Separate production time from international transit and import time. The quotation and PO should identify:
- the agreed delivery rule or shipping basis, named place or port, and edition where applicable;
- who arranges carriage, insurance, export clearance, import clearance, duties, taxes, and destination handling;
- sample, drawing, document, and production approval dates that start or stop the schedule;
- shipping method, destination, packing, moisture or impact protection, labels, carton marks, and pallet or reel requirements;
- commercial invoice, packing list, origin, test, declaration, and other project/import documents actually required;
- partial-shipment, inspection, document-revision, delay-notification, and receiving rules.
The International Chamber of Commerce's Incoterms® 2020 overview explains that the chosen rule allocates tasks, costs, and risks; the contract still needs the precise named place and project-specific terms. Do not quote a delivery period until the production start event, transport scope, and destination responsibilities are explicit.
For distributor, framework, bulk, private-label, OEM, or ODM requests, add the approved drawing revision, label and artwork, barcode or serial format, inner and outer packing, quantity basis, repeat-order identity, and change-notification rules. These are RFQ fields, not proof that any supplier can deliver the requested program.
What should the final approval pack contain?
The final pack should let another reviewer reconstruct what was compared, what was tested, who decided, what was released, and which later change would reopen the decision.
| Approval-pack item | Minimum content | Completion owner or evidence |
|---|---|---|
| Approval cover sheet | Source part, candidate part, project, application, quantity or scope, status, conditions, approver, and date | Project approval owner |
| Source-record set | Current source datasheet or drawing, retrieval date, governing clause, and any approved submittal or asset reference | Project document owner |
| Candidate evidence index | Candidate drawing and datasheet revisions, declarations, test records, labels, and status against each requirement | Supplier plus technical reviewer |
| Deviation log | Every difference or unknown, risk, owner, due date, disposition, and closure evidence | Technical approver |
| Sample and pilot record | Sample identity, plan, methods, limits, results, failures, conditions, and disposition | QA and project-defined approver |
| Warranty or program record | Program, geography, registration status, exact question, consulted party, response, and date | Program owner or authorized party |
| Production-release record | Approved candidate and drawing, sample link, incoming plan, required delivery records, labels, packaging, and PO conditions | Procurement plus technical or QA owner |
| Change and requalification record | Notification triggers, notice period, shipment hold rule, impact review, decision owner, and requalification result | Supplier and buyer's change-control owner |
If any mandatory item remains missing, the pack should show the candidate as pending rather than hide the gap in an email chain.
Download the blank approval worksheet
Use the Controlled Corning Fiber Patch Cord Alternative Approval Worksheet (PDF) to record the source identity, candidate evidence, deviations, sample and pilot scope, supplier comparison, commercial basis, approval owner, and requalification triggers.
The worksheet is a blank project-control template. It is not a BWNFiber datasheet, test report, equivalence certificate, legal opinion, warranty decision, or project approval. The project owner must define the actual requirements, methods, limits, documents, and signatories. Do not enable the website link until the approved PDF is uploaded to the exact path and tested.
What should BWNFiber confirm before its candidate enters the submittal?
The current BWNFiber fiber patch cord page provides a route for buyers to submit application, interface, fiber, construction, acceptance, quantity, and schedule inputs for configuration review. That route is a starting point, not evidence that a BWNFiber candidate is equivalent to a named Corning part. Ask whether BWNFiber can perform the candidate-evidence gap review required for the offered configuration before relying on that service in the project workflow.
For a Corning-referenced request, ask BWNFiber to return a written candidate-evidence response with the following fields:
| Response field | Required BWNFiber response | Buyer action |
|---|---|---|
| Offered identity | Exact candidate part, drawing title, revision, date, and applicable production identity | Reject a family-only or unnamed offer from the approval comparison |
| Source-to-candidate map | Candidate record for each requested source or project requirement | Mark unsupported fields unknown; do not copy source values |
| Deviations and exclusions | Every known difference, excluded service, unavailable record, and unresolved assumption | Assign a project owner and disposition before release |
| Available evidence | Candidate-specific datasheet, drawing, declaration, listing, sample, test, label, traceability, or packing record that BWNFiber can actually provide | Check identifiers, scope, edition, sample link, and validity |
| Sample or pilot path | Whether a sample or pilot is available, its identity, prerequisites, record set, commercial basis, and proposed schedule | Approve the plan before testing; do not infer production release |
| Change control | Proposed notification triggers, notice, shipment status, and requalification support for the offered candidate | Put accepted controls into the PO or quality agreement |
| Commercial response | Quantity and price basis, lead-time assumptions, schedule start event, inclusions, exclusions, shipping basis, and quote validity | Compare only after technical status and commercial bases align |
| Open or unavailable items | Records or capabilities BWNFiber cannot confirm for that configuration | Keep mandatory gaps pending or reject the candidate |
Treat a BWNFiber candidate as review-ready only when its response separates available, different, unknown, and not available. That evidence discipline is more useful to the project than a one-line "equivalent" claim. BWNFiber can describe only the candidate and records it controls; the project's authorized owner decides acceptance.
What should you send to request a candidate-evidence response?
Provide one controlled package:
- exact Corning part number and current source datasheet;
- RFP, BOM, drawing, or approved-submittal reference;
- clause that permits or governs alternatives;
- project application and quantity;
- required evidence index, deviation, test, label, and approval-record format;
- registered-system or approved-vendor constraint;
- target sample or pilot decision date;
- name or role of the customer's approval authority.
The requested review output should identify available candidate evidence, deviations, unknowns, unavailable documents, and the next approval step. It should not reduce the decision to a one-line equivalence declaration.
Request a candidate-evidence response. Submit the source part and governing project record through the BWNFiber project inquiry page. Ask first whether an exact candidate is available and which candidate-specific deliverables BWNFiber can supply. A form submission is a request for review, not an approval, quotation commitment, or promise that every requested record is available.
After mandatory gaps have a project disposition, request the applicable model datasheet or drawing and a traceable sample where required. Request a quote against the controlled candidate record, with the price basis, schedule start event, lead-time assumptions, inclusions, exclusions, and validity stated in writing.
Frequently asked questions
What does "Corning or approved equal" require?
It permits a candidate review when the governing document says so. Approval still needs a named authority, controlling requirements, candidate evidence, deviation handling, and a written disposition.
Who has authority to approve a substitute?
The governing project documents assign that authority. It may belong to the customer, consultant, engineer of record, network owner, qualified installer, warranty-program owner, or another named role. The supplier does not inherit that authority.
Can a supplier declare its own cord equivalent?
A supplier can state candidate characteristics and provide supporting records. The project's authorized decision-maker determines approved-equal status for the defined scope.
What if the current Corning datasheet is unavailable?
Request the controlling datasheet or approved record from the project owner, Corning, or an authorized source. If it remains unavailable, keep the affected requirements unknown until the project defines a performance-based replacement record or another acceptable basis.
Does a passed sample approve the production order?
No. Production release must tie the sample to the candidate part, drawing revision, evidence index, deviations, acceptance plan, labels, records, and change controls.
Can one approved substitute cover several Corning part numbers?
Only when the approver defines that scope and the evidence addresses every affected source requirement. A shared connector family or product name does not transfer approval.
Which differences require a formal deviation?
Record every difference from a mandatory source or project requirement. The authorized project role decides whether to accept, test, clarify, or reject it.
When should a candidate be rejected before sample testing?
Pause or reject it when substitution is not permitted, the source identity is unknown, a mandatory record is missing, a special interface is unresolved, evidence is not tied to the offered part, or required change control is refused.
How should system-warranty impact be recorded?
Record the program, geography, registration status, party consulted, exact question, written response, and date. Keep the result separate from technical acceptance.
What must be attached to the purchase order?
Reference the approved candidate part and drawing, evidence index, closed deviations, sample or pilot disposition, acceptance records, labels, warranty decision, and change-notification requirements.
Which supplier changes trigger requalification?
Review changes to product identity, connector or ferrule source, fiber or cable construction, jacket or listing, production site, termination or test process, acceptance method, labels, records, and applicable project or program rules. The buyer sets the final trigger list.
What should the final approval record contain?
It should identify the source part, candidate part, governing requirement, evidence reviewed, deviations, sample or pilot scope, warranty decision, conditions, approver, date, approved application or quantity scope, and requalification triggers.
Related BWNFiber resources
- Fiber Patch Cord category and specification guide
- Fiber Optic Jumper terminology and product range
- Pre-Terminated Fiber Cable Assemblies Guide
- Fiber Optic Adapter category
- BWNFiber project inquiry page
Disclaimer: This guide is a procurement and evidence-control reference. It is not a guarantee of equivalence, project approval, performance, warranty eligibility, price, availability, MOQ, or lead time. The governing contract, source record, candidate documents, approved test plan, and written project decision control each substitution.
