Legacy FPGA sourcing: separate lifecycle notices from replacement qualification

A discontinuation notice answers a narrow question: which ordering codes are affected by a particular manufacturer action? A maintenance team still needs to decide whether to buy the original part, qualify a listed successor, or redesign. Keep those decisions in separate evidence columns so a purchasing deadline does not become an unsupported engineering approval.

This is an original planning method for industrial equipment and long-lived FPGA boards. The worked example uses an archived manufacturer notice, not a report of a new discontinuation or a claim about present supply.

Read the affected and replacement columns separately

Xilinx notice XCN20011, version 1.0, dated September 28, 2020, covers selected FFV, FBV and SBV package ordering codes. Its tables distinguish affected parts from manufacturer-listed replacement parts. The notice describes compatibility with the corresponding G-package products; that statement belongs to the specified manufacturer scope and does not document a test of your assembled board.

Table 4 on page 2 lists XC7A200T-2FBV484C → XC7A200T-2FBG484C. Table 6 on page 4 lists XC7Z030-1FBV484C → XC7Z030-1FBG484C. These are two literal table relationships, not a rule for generating all possible suffix combinations. A part appearing in the replacement column must not inherit the affected part’s discontinuation status from this notice alone.

Original manufacturer PDF: XCN20011 v1.0, pages 1, 2 and 4. Source rechecked October 20, 2026. Retain the document revision with the decision record and check for subsequent notices before acting.

Build a decision record with three independent gates

Original review worksheet: each row needs its own evidence and owner.

Gate	Record	Evidence that does not close this gate
Identity and lifecycle	Exact BOM ordering code, manufacturer document number/revision, table/page, affected or replacement role, and any later notice found.	A similar base-device name or an adjacent row in the same table.
Engineering change	Board revision, candidate ordering code, package/pin and electrical checks, implementation files, manufacturing inputs, validation plan and unresolved issues.	A supplier quote, a product photograph, or a manufacturer relationship copied without its scope.
Supply decision	Requested quantity and delivery window; offer-specific availability, traceability records, inspection requirements and a named person responsible for acceptance.	An archived product page or a historic last-order date. Neither establishes inventory today.

The gates can progress in parallel, but do not collapse them into a single “approved replacement” checkbox. A purchasing team may have a credible offer while engineering has not closed validation. Engineering may have a qualified change while the requested delivery date remains unconfirmed.

Worked example: keep the exact code through the handoff

Assume a maintenance BOM names XC7A200T-2FBV484C. This assumption is an exercise, not a description of a customer installation. Record that exact affected code and the literal replacement row above. Next create a separate candidate record for XC7A200T-2FBG484C; do not overwrite the original BOM history.

1. Identity check: compare the entire code, including speed, package and grade. If the BOM uses a different suffix, stop this row-level match and find its own evidence.
2. Change review: attach the board revision and the package/pin documentation applicable to both selected parts. Assign owners to unresolved electrical, implementation, assembly and test questions. A missing answer stays open.
3. Supply review: request a quote for the exact code and quantity, with the traceability and inspection inputs the project needs. Treat price, stock and shipment date as unknown until supported by a current offer.
4. Release decision: preserve the reviewed evidence, unresolved risks and responsible approvers with the final BOM revision. An AI-prepared comparison is supporting material, not a human engineering sign-off.

The XC7A200T-2FBG484C parameter page is a starting point for the candidate’s documented facts. It does not replace the original notice or a board-specific qualification record. Use the BOM check tool to organize missing inputs, then retain the result with the source documents.

Choose the next action from the unresolved gate

• Original part still required: prepare an exact-code sourcing brief and identify what traceability and acceptance evidence is needed. Availability remains unconfirmed.
• Listed candidate under evaluation: keep the original and candidate records linked, with a written verification plan. Do not describe a planned test as completed.
• No supportable candidate found: open a redesign decision with interface, board, toolchain and validation work explicitly scoped. An empty replacement field is more useful than an invented match.

Use the hard-to-find component sourcing workflow for the purchasing brief and the PCBA handoff resources for manufacturing inputs. Keep source interpretation, design acceptance and the commercial offer as distinct records throughout the project.