FAQ

Can digital tools handle multi-sheet aerospace drawings for FAI?

Yes, many digital FAI tools can handle multi-sheet aerospace drawings, but it is not automatic or uniform across vendors. Whether it works well in your environment depends on how the software models drawings, how you balloon characteristics, and how tightly it is integrated with your PLM or drawing control process.

What “handling multi-sheet drawings” actually means

For AS9102 and similar first article workflows, effective support for multi-sheet drawings typically requires that the tool can:

  • Ingest and display multi-page PDFs or native CAD-derived drawings without losing sheet boundaries.
  • Associate every characteristic with sheet number and zone (and revision) to maintain traceability.
  • Maintain a single characteristic list (the “ballooned” index) across all sheets, without duplicate or skipped numbers.
  • Allow inspectors to navigate between sheets while keeping the characteristic index synchronized.
  • Export AS9102 Forms (especially Form 3) with clear sheet/zone references that match the drawing package.

Some tools do all of this natively. Others only treat each sheet as a separate document, which forces workarounds and increases risk of missing features or double-counting characteristics.

Common capabilities and where they fail

Typical digital FAI/ballooning systems in aerospace can:

  • Open a multi-page PDF from PLM or a file share.
  • Overlay balloons on each sheet, with a global characteristic sequence (e.g., 1–250 spanning all pages).
  • Capture basic metadata (sheet, zone, reference dimension, key characteristic flags) into a central list.
  • Generate AS9102-compliant outputs, often including the drawing as an attachment or embedded reference.

They often struggle when:

  • Drawings mix multiple parts, configurations, or option tables across sheets.
  • Supplemental sheets (e.g., process notes, special characteristics) are added later under a sub-revision.
  • Legacy scans are poor quality, misaligned, or missing zone grids.
  • There are frequent engineering changes that affect only some sheets, requiring partial re-ballooning.

In these situations, tools can still be used, but the quality of the workflow depends heavily on configuration, disciplined use of naming conventions, and how carefully revision and sheet changes are controlled.

Dependencies and preconditions

Effective multi-sheet support is not just a software toggle. It depends on:

  • Drawing structure: Clear sheet numbering, consistent title blocks, and stable zone grids across sheets.
  • PLM / document control: Reliable linkage between part numbers, revisions, and the full drawing set (all sheets, including aux or detail sheets).
  • FAI process maturity: Defined rules for what gets ballooned on each sheet (e.g., notes, tables, general tolerances) and how derived/secondary characteristics are handled.
  • Integration quality: If the FAI tool pulls from PLM or pushes to QMS/MES, multi-sheet context (sheet/zone/revision) must be preserved across those integrations.
  • Validation: In regulated environments, the digital FAI workflow, including multi-sheet handling, needs to be validated and periodically checked for data integrity issues.

Brownfield and coexistence considerations

In most aerospace plants, multi-sheet drawings are already used across multiple systems: PLM, PDF archives, Net-Inspect or similar portals, and local network drives. Introducing or upgrading a digital FAI tool has to coexist with this reality.

Practical implications include:

  • Multiple sources of truth: The FAI tool may be working from exported PDFs while PLM holds the native CAD and the QMS holds the approved FAI report. Misalignment across these systems is a common failure mode.
  • Legacy FAIs: You may have thousands of historical FAIs done on paper or in spreadsheets that used multi-sheet drawings with different conventions. Converting them to digital tools is rarely a one-to-one migration.
  • Incremental rollout: Fully replacing existing FAI workflows is difficult because of validation burden and qualification risk. Many plants start with new programs or subsets of parts while legacy programs continue with existing methods.
  • Downtime constraints: Changing how multi-sheet drawings are handled cannot interrupt ongoing production inspections, so parallel processes and careful change control are often required.

Typical failure modes to watch for

Even when a tool advertises multi-sheet support, issues often surface in daily use:

  • Missing or duplicated characteristics when inspectors balloon different sheets in parallel or when engineering adds a new sheet mid-stream.
  • Incorrect sheet/zone references in AS9102 Form 3 because of manual retyping or poor mapping between the drawing viewer and the FAI form generator.
  • Revision mismatch where the FAI report references sheet 1 rev C but production is building to a package that includes sheet 4 at rev D.
  • Lost context during export if the FAI output (e.g., to a customer portal) detaches the characteristic list from the original multi-sheet drawing set.

Mitigation usually requires configuration and governance, not just features: enforced characteristic numbering rules, mandatory sheet/zone fields, role-based approvals, and periodic audits of digital FAIs against the drawing package.

Tradeoffs and selection questions for multi-sheet support

When evaluating or configuring a digital FAI tool for multi-sheet drawings, some practical questions to ask are:

  • Does the tool treat a multi-page drawing as a single controlled object with a unified characteristic list?
  • Are sheet/zone references mandatory for each characteristic, and can you configure rules (e.g., sheets that must not contain unballooned notes)?
  • How are revisions to a single sheet handled? Can you re-balloon selectively and retain history and traceability?
  • Can the system integrate with your PLM so that the full drawing set (all sheets) is guaranteed correct for each part/revision?
  • What validation evidence exists for multi-sheet workflows, and how will you revalidate after configuration or integration changes?

The tradeoff is usually between sophistication and complexity: richer multi-sheet modeling and integrations can reduce manual error but add setup effort, integration work, and validation overhead.

Implications for AS9102 and customer expectations

Digital tools that handle multi-sheet drawings well can make AS9102 compliance more repeatable by enforcing consistent characteristic identification and documentation across the entire drawing set. However, they do not guarantee conformity or audit outcomes.

You still need:

  • Clear internal procedures that define how multi-sheet drawings are ballooned, reviewed, and approved.
  • Change control between engineering, PLM, and inspection so that sheet additions or revisions are reflected in the FAI plan and results.
  • Evidence that your digital process for multi-sheet FAI has been followed consistently, including for partial re-FAIs when only some sheets are affected by an engineering change.

In most aerospace environments, the most reliable path is incremental adoption: start by digitizing FAIs for new or less complex parts, validate the multi-sheet workflow, then extend to more complex assemblies and legacy programs as confidence and integration maturity improve.

Get Started

Built for Speed, Trusted by Experts

Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.