What is the problem?
During a Regeneron BOM review, a series of sub-assemblies was found with names beginning with FAS. According to the Fab Lead, the names originated in the project’s wireframe and were then retained by the 3D modeling team when the wireframe was used as a reference. The prefix was intended to identify fascia plate assemblies.
However, FAS is reserved for the fastener part category. Reusing it for sub-assemblies makes the name communicate the wrong object type and can cause downstream BOM, classification, extraction, and automation rules to treat an assembly as a fastener. Rules that depend on codification boundaries cannot reliably distinguish the intended meaning after the reserved prefix has been reused.
How could it be improved?
Require Fab Leads to verify wireframe and sub-assembly names against the approved codification standard before those names are adopted by the 3D modeling team or used in downstream operations. Keep FAS exclusive to fastener parts, and assign fascia plate sub-assemblies through the approved sub-assembly naming convention rather than creating a second meaning for the prefix.
Add a naming-compliance check to the assembly BOM preflight so that a reserved part prefix used on a sub-assembly is reported before release. Existing exceptions should be identified and corrected through a controlled naming update; downstream classifiers should not be broadened to treat FAS as both fastener and fascia assembly.
Current Position
RND-0001 has been reviewed and accepted as the executable codification baseline: FAS identifies the fastener category. The Regeneron observation does not weaken or create an exception to that taxonomy. It identifies an upstream execution error in which a wireframe name that did not conform to the approved code meaning was carried into the 3D model.
Downstream rules that interpret FAS as fastener are behaving consistently with the approved input contract. The corrective direction is therefore an upstream information-QC process that reviews and corrects naming before wireframe identifiers are adopted by the 3D modeling team. A later BOM review may detect a missed error, but it is a secondary safety net rather than the primary control point.
Follow-up Reviews
2026-08-13 — Upstream QC and relationship boundary
Review context: The original intake was reviewed to distinguish an approved codification rule from a project-level failure to follow that rule. The reported origin of the Regeneron names remains attributed to the Fab Lead’s account and has not been independently reconstructed from the wireframe history.
Refined understanding: This Opportunity concerns conformity review at the wireframe-to-model information handoff. It does not call for FAS to acquire a second meaning, and it does not require the approved taxonomy or downstream classifiers to accommodate the nonconforming name.
Current direction: Establish a review gate before a wireframe or sub-assembly identifier becomes an accepted 3D model name. The review should compare the object type with the approved code meaning, return mismatches to the information source for correction, and propagate an approved correction through affected project information in a controlled manner. The specific reviewer, trigger, tooling, affected-file scope, and correction procedure remain to be defined.
Relationship impact: RND-0001 remains the direct relationship because it provides the reviewed classification baseline used by this QC opportunity. CASE-0001 is a downstream dimension-normalization effort that consumes the same baseline but does not own upstream naming correction. OPP-0011 is a downstream BOM-structure and description check; it may provide later detection but is not the same review scope. Neither record is retained as a formal direct relationship. The upstream-information-qc category is provisional pending a broader controlled category vocabulary for the Opportunity Register.