DISCUS vs. Designcenter Inspector (NX Inspector) vs. SOLIDWORKS Inspection vs. QA-CAD: Which FAI Software Should You Use?
First article inspection can appear deceptively simple.
Take the engineering drawing, place numbered balloons beside every requirement, measure the manufactured part and record the results on the required forms.
That description leaves out most of the difficulty.

A complex aerospace drawing may contain hundreds of dimensions, geometric tolerances, material requirements, process specifications and notes. Some requirements appear directly on the drawing. Others reside in referenced specifications, CAD models, parts lists or separate documents. A missed note can matter just as much as a missed dimension.
The completed First Article Inspection Report must prove that the manufacturing process produced a part conforming to the complete engineering definition—not merely that someone measured a convenient selection of features.
That is why aerospace suppliers use specialized first article inspection software.
These tools can automate ballooning, extract dimensions and tolerances, create a bill of characteristics, populate AS9102 forms, capture measurement results and help maintain the connection between a design requirement and the evidence that the manufactured part satisfies it.
However, the software products do not all begin at the same point in the process.
- DISCUS approaches FAI as the organization and analysis of an entire technical data package.
- NX Inspector begins inside the native NX model and turns product manufacturing information into managed, traceable characteristics.
- SOLIDWORKS Inspection combines CAD integration with a practical standalone workflow for drawings, PDFs and inspection results.
- Guthrie QA-CAD concentrates on affordable, on-premises ballooning and report creation from conventional drawing files.
The best choice therefore depends less on which product has the longest feature list and more on what problem the manufacturer is actually trying to solve.
What Is First Article Inspection?
First article inspection, commonly abbreviated as FAI, is a formal verification that a production process can manufacture a part or assembly that meets its engineering requirements.
Despite the name, the process does not necessarily mean examining the literal first item that comes off a machine.
The “first article” is a representative item produced using the intended production materials, tooling, equipment, programs, processes and personnel. The inspection verifies both the physical result and the production process used to create it.
Aerospace organizations commonly perform FAI when:
- A part is produced for the first time
- A design change affects fit, form or function
- Manufacturing moves to a different facility
- Tooling or production methods change
- A long interruption in production occurs
- A supplier or customer requires a new inspection
- A previous FAI is no longer considered fully representative
The resulting First Article Inspection Report, or FAIR, establishes traceable evidence that the product requirements have been accounted for and verified.
FAI is not the same as ordinary incoming inspection or checking a few critical dimensions. It is intended to account for the complete design definition relevant to the manufactured product.
Why FAI Becomes Difficult So Quickly
The physical measurement is only one part of the job.
Before inspectors can enter results, someone must identify every requirement that needs to be verified. This can include:
- Dimensions
- Dimensional tolerances
- Geometric dimensioning and tolerancing
- Surface-finish requirements
- Material specifications
- Heat treatment
- Coatings and finishes
- Special processes
- Drawing notes
- Referenced specifications
- Part-marking requirements
- Functional tests
- Customer-specific requirements
- Key or critical characteristics
Traditionally, an engineer or quality specialist reviews the drawing, draws a balloon around each requirement and manually transfers the information into a spreadsheet.
That creates several opportunities for failure.
A characteristic can be overlooked. A nominal value can be mistyped. A tolerance can be interpreted incorrectly. Two balloons can receive the same number. A drawing revision can change without the inspection plan being updated. A note can be missed because it does not look like a conventional dimension.
FAI software reduces this clerical burden, but the products differ significantly in how much of the process they control.
The Most Important Difference: Drawing-Based FAI or Model-Based Quality?
The four products in this comparison fall along a spectrum.
At one end are tools built primarily to convert drawings into ballooned inspection documents and report forms.
At the other end are systems intended to make quality characteristics part of the authoritative digital product definition.
This is more than a technical distinction.
A drawing-based workflow typically asks:
How can we create this inspection report more quickly and accurately?
A model-based workflow asks:
How can we define each quality characteristic once, preserve its relationship to the design and allow manufacturing, quality and metrology systems to consume it downstream?
Both are valid problems. Many aerospace manufacturers must solve both.
DISCUS: Best for Managing the Complete Technical Data Package
DISCUS is one of the better-known specialized products in aerospace first article inspection.
Its central strength is that it treats the FAI as more than a ballooned drawing.
DISCUS Desktop is designed to organize and analyze the technical data package, or TDP. Users can identify requirements from drawings and related specification documents, create ballooned records and build an accountability checklist. Additional modules extend the workflow into 3D model interrogation, results capture, CMM data, inspection planning and supplier FAI management.
That technical-data-package orientation matters in aerospace because the complete definition of a part may not reside on a single drawing.
A note may refer to a material specification. That specification may invoke a testing requirement. Another document may define a special process. An inspection system focused only on recognizing dimensions in a PDF can accelerate part of the process without necessarily ensuring that every requirement in the package has been considered.
Where DISCUS Is Strongest
DISCUS is particularly well suited to organizations that:
- Receive technical data from many customers
- Work with mixed CAD and drawing formats
- Must review specifications in addition to drawings
- Produce AS9102 documentation for multiple aerospace primes
- Need customer-specific report formats
- Manage complex supplier FAI packages
- Want a dedicated quality-engineering environment rather than a CAD add-in
- Need to reuse extracted characteristics for process or inspection planning
DISCUS supports both 2D and 3D workflows, although its 3D capability is offered as an additional module rather than being inseparable from the base desktop product. The broader product family includes DISCUS Desktop, IDA automated ballooning, Results, CMM, Planner, 3D and Connect.
This modularity can be an advantage for an aerospace supplier whose needs extend beyond creating a report.
It can also make evaluation more complicated. A prospective buyer must determine which DISCUS modules are needed to reproduce the company’s complete workflow.
DISCUS IDA and Automated Ballooning
DISCUS IDA applies automation to the identification and ballooning of requirements in 2D PDFs and 3D models. DISCUS says its system can create ballooned drawings and FAI forms while maintaining an accountability checklist that keeps identified requirements aligned with the inspection sheet.
As with any automated extraction tool, users should still review the output.
Automation reduces repetitive work. It does not transfer responsibility for requirement completeness from the quality organization to the software.
The Main Limitation of DISCUS
DISCUS is not the native design environment.
That independence is valuable when a supplier receives data from Boeing, Airbus, Lockheed Martin, an engine manufacturer and several lower-tier customers. It is less seamless when a company wants characteristics to originate inside its own authoritative CAD model and remain associatively connected to design changes throughout PLM.
DISCUS is strongest as a specialized FAI and manufacturing-quality platform.
It is not trying to be NX, Teamcenter or the company’s complete product lifecycle backbone.
NX Inspector: Best for NX-Centered Model-Based Quality
NX Inspector enters the problem from the opposite direction.
It is an add-on within NX that allows users to create and manage model-based characteristics directly in the CAD environment.
Siemens describes NX Inspector as the first CAD-native implementation of the Digital Metrology Standards Consortium’s Model-Based Characteristics standard. It converts PMI into individually managed manufacturing and quality characteristics, preserves direct associativity to the source PMI and supports downstream use through Teamcenter and Teamcenter Quality.
This makes NX Inspector strategically important, but it also creates confusion about what the product actually replaces.
Naming update — October 2026: Siemens now uses the name Designcenter Inspector on its aerospace engineering pages, describing it as an add-on for first article inspection and characteristics management. Earlier Siemens documentation calls the product NX Inspector, and some technical materials still use that name. Both names are relevant when researching Siemens’ model-based inspection capabilities. For more information, see our explanation of NX Inspector and Designcenter Inspector
NX Inspector Is More Than Ballooning—but Not Necessarily a Complete FAIR System by Itself
NX Inspector can:
- Create characteristics from NX PMI
- Automatically balloon supported PMI
- Assign unique identities to individual characteristics
- Add information not contained in the original PMI
- Distinguish key or critical characteristics
- Update characteristics when associated PMI changes
- Export characteristic information through QIF or PLMXML
- Manage the bill of characteristics through Teamcenter
- Feed characteristics into Teamcenter Quality inspection planning
- Support automation through NX Open
These capabilities address a major weakness in traditional inspection workflows: the inspection characteristic is often recreated downstream as disconnected data.
With NX Inspector, the characteristic can remain associated with the design requirement from which it originated. Siemens uses unique identifiers to support traceability across the digital thread.
That is a substantial advantage for an aerospace manufacturer operating NX and Teamcenter as its primary engineering platform.
However, Siemens’ own product descriptions emphasize characteristic definition, accountability and downstream consumption more than the creation and completion of an entire supplier-facing AS9102 package.
NX Inspector helps establish the digital source of the inspection requirements. Teamcenter Quality can then use those characteristics for inspection planning. Other Siemens manufacturing and quality applications may participate further downstream.
That is a broader enterprise architecture, not merely a replacement for a standalone ballooning package.
Where NX Inspector Is Strongest
NX Inspector is best suited to organizations that:
- Use NX as an authoritative design system
- Have mature model-based-definition practices
- Already use Teamcenter
- Want characteristics associated directly with PMI
- Need change traceability from engineering into quality
- Want QIF-based interoperability
- Are building a model-based enterprise
- Need quality requirements to become structured lifecycle data
It is particularly compelling for an OEM that controls the source model.
A supplier receiving flattened PDFs from several customers may gain far less from NX Inspector because the supplier does not control the original NX PMI or Teamcenter environment.
The Main Limitation of NX Inspector
Its greatest strength is also its greatest limitation: it is centered on the NX ecosystem.
For companies that primarily receive customer drawings, scanned documents, PDFs or mixed CAD formats, purchasing an NX-based characteristic-authoring system may be an unnecessarily large answer to a smaller documentation problem.
NX Inspector also represents a newer approach than the long-established standalone FAI products. Companies evaluating it should verify precisely how their complete AS9102 forms, measured results, supplier submissions and customer-specific requirements will be handled—not assume that automated ballooning alone completes the FAIR.
What Does Siemens Actually Want Customers to Use?
The confusing answer is: it depends on where the customer begins and how much of the Siemens stack it owns.
Siemens currently presents several inspection-related offerings:
- NX Inspector for CAD-native model-based characteristics
- Teamcenter Quality for quality planning and lifecycle management
- Designcenter Solid Edge Inspector for ballooning, bills of characteristics and inspection reports within Solid Edge
- Opcenter capabilities for executing and documenting production inspections
- InspectionSuite, a Siemens ecosystem application from neoapps for automated ballooning and inspection-report creation in an NX-oriented workflow
Siemens describes InspectionSuite as a tool that can generate ballooned drawings and inspection reports from 2D drawings or 3D models with PMI. The product is presented through Siemens’ neoapps ecosystem rather than as the core NX Inspector module.
Solid Edge Inspector goes further than the current public description of NX Inspector in explicitly promoting configurable FAI reports and AS9102-oriented templates. It can balloon dimensions, produce a bill of characteristics, generate inspection reports and connect inspection data with Teamcenter and downstream quality applications.
Opcenter Execution Discrete also added support for identifying production inspections as first article inspections and producing a printable report based on an AS9102-aligned template.
This overlap does not necessarily mean Siemens lacks a strategy.
The likely strategy is to place quality data across the digital thread:
- Define the product requirement in CAD.
- Characterize it through NX Inspector.
- Manage and plan quality through Teamcenter.
- Execute production and inspection through manufacturing systems.
- Preserve results and traceability across the lifecycle.
But that architecture is considerably harder to explain than:
Buy this application to balloon your drawing and create an AS9102 report.
For a smaller aerospace supplier, Siemens’ portfolio can therefore look less like one FAI solution and more like several partially overlapping paths.
Before purchasing NX Inspector, a company should ask Siemens or its reseller to demonstrate the entire FAIR workflow, not only characteristic creation inside NX.
That demonstration should begin with the customer’s real input files and end with the exact report package the customer must submit.
SOLIDWORKS Inspection: Best Balance of CAD Integration and Standalone Flexibility
SOLIDWORKS Inspection occupies the middle ground.
It is available as both an embedded SOLIDWORKS add-in and a standalone application. The standalone option can work with legacy and non-SOLIDWORKS data, while the add-in can extract characteristics directly from SOLIDWORKS drawings, parts and assemblies.
This makes it attractive to small and midsized manufacturers that use SOLIDWORKS internally but still receive PDFs and drawings from customers using other CAD systems.
SOLIDWORKS Inspection Standard
The Standard package focuses on creating inspection documentation.
Its capabilities include:
- Automated ballooning
- Extraction from SOLIDWORKS files
- PDF and TIFF support
- DXF and DWG support
- Optical character recognition
- Bill-of-characteristics creation
- Drawing and model revision comparison
- Custom inspection reports
- AS9102 and PPAP Excel templates
- CSV and XML export
- Direct publication to Net-Inspect
- Integration with SOLIDWORKS PDM
The OCR capability can identify nominal dimensions, tolerances, GD&T, notes, hole callouts and other drawing information from supported PDF and image files.
SOLIDWORKS Inspection Professional
The Professional package extends the workflow into measured results.
Users can enter inspection values manually, collect them using supported digital measuring devices or import CMM results. The software can then indicate whether characteristics pass, fail or approach their tolerance limits.
This separation between document creation and results capture makes the packaging relatively understandable:
- Standard helps create the inspection project and documentation.
- Professional adds execution and result-management capabilities.
Where SOLIDWORKS Inspection Is Strongest
SOLIDWORKS Inspection is a strong option for organizations that:
- Design primarily in SOLIDWORKS
- Need both an integrated and standalone workflow
- Receive many PDF or TIFF drawings
- Want OCR-assisted extraction
- Need AS9102 and PPAP reporting
- Use SOLIDWORKS PDM
- Want to enter measurement results or import CMM data
- Need to publish FAIR data to Net-Inspect
- Do not require a large enterprise PLM implementation
It may provide the most approachable compromise among the products in this comparison.
It is more directly focused on complete inspection documentation than NX Inspector, more tightly integrated with a mainstream CAD system than DISCUS and more extensive in workflow depth than basic ballooning software.
The Main Limitation of SOLIDWORKS Inspection
Its native advantages are greatest within the SOLIDWORKS environment.
The standalone application reduces dependence on SOLIDWORKS file formats, but a manufacturer with an NX-and-Teamcenter enterprise architecture may prefer characteristics created and controlled directly in that ecosystem.
Likewise, an aerospace supplier with exceptionally complex technical data packages and numerous customer-specific requirements may find DISCUS more specialized for its environment.
Guthrie QA-CAD: Best for Affordable, On-Premises Drawing-Based FAI
Guthrie CAD/GIS Software’s FAI product is called QA-CAD.
Its website looks less polished than those of the large engineering-software vendors. That should not automatically be confused with a lack of practical capability.
QA-CAD is aimed squarely at companies that need to balloon drawings, extract requirements and create inspection reports without purchasing an enterprise quality platform.
It supports:
- PDFs
- Raster images
- DWG and DXF files
- Automated ballooning
- OCR-based extraction
- Dimensions and tolerances
- GD&T symbols
- Drawing notes
- Custom tolerance tables
- AS9102 Rev. C reports
- PPAP reports
- Custom Excel templates
- Measurement entry
- CMM-result import
- Revision replacement
- Excel, Word and CSV output
- Perpetual and network licensing
Guthrie says QA-CAD operates on the customer’s own infrastructure and can be deployed offline in restricted or air-gapped environments. It explicitly notes that using the software does not, by itself, make an organization compliant with ITAR, CMMC or NIST requirements; compliance depends on the customer’s complete security program.
That is a refreshingly important distinction.
Where QA-CAD Is Strongest
QA-CAD is best suited to organizations that:
- Work primarily from 2D drawings and PDFs
- Want a lower-cost perpetual license
- Need an on-premises or offline system
- Handle customer-controlled technical data
- Do not want a cloud-based platform
- Need AS9102 forms without enterprise PLM
- Have a relatively straightforward inspection-document workflow
- Want to trial the software before purchasing it
Guthrie publishes pricing, which is unusual in engineering software. At the time reviewed, its site listed a 14-day trial, a standard perpetual license beginning at $1,195 per user and a network license beginning at $1,585 per concurrent user. Pricing and licensing terms can change, so prospective buyers should verify current details directly with the vendor.
The Main Limitation of QA-CAD
QA-CAD is primarily a document-centered tool.
It does not present the same enterprise digital-thread ambitions as NX Inspector and Teamcenter. It also lacks the broader modular technical-data-package environment promoted by DISCUS.
For many machine shops, however, those limitations may be irrelevant.
A supplier asked to balloon customer PDFs and submit accurate AS9102 forms may not need its FAI application to become the foundation of a model-based enterprise.
Side-by-Side Comparison FAI Software
| Capability | DISCUS | Designcenter/NX Inspector | SOLIDWORKS Inspection | Guthrie QA-CAD |
|---|---|---|---|---|
| Primary approach | Technical data package and FAI management | CAD-native model-based characteristics | CAD-integrated and standalone inspection documentation | Affordable drawing-based FAI |
| Native CAD environment | Independent, with optional 3D tools | NX | SOLIDWORKS | Independent |
| 2D PDF workflow | Yes | Not its primary purpose | Yes | Yes |
| OCR extraction | Available through DISCUS automation capabilities | Not the central workflow | Yes | Yes |
| Native PMI associativity | Through 3D workflows, but not native CAD authoring | Strong | Strongest with SOLIDWORKS data | Limited |
| Automated ballooning | Yes | Yes | Yes | Yes |
| AS9102 report workflow | Yes | Requires evaluation of the broader Siemens workflow | Yes | Yes |
| Technical data package management | Strong | Through the wider NX/Teamcenter environment | Moderate | Basic |
| Measurement-result capture | DISCUS Results and related modules | Through downstream Siemens quality systems | Professional package | Yes |
| CMM integration | Separate DISCUS capabilities | Downstream metrology and quality workflow | Import supported | Import supported |
| PLM integration | Integration-dependent | Strong with Teamcenter | SOLIDWORKS PDM; other exports | Limited |
| Mixed-customer data environment | Strong | Less ideal | Strong | Strong for common 2D formats |
| Model-based enterprise strategy | Moderate to strong | Very strong | Moderate | Limited |
| Public pricing | Configuration dependent | No | Generally reseller-based | Yes |
| Best fit | Aerospace suppliers with complex FAIR packages | NX/Teamcenter enterprises | SOLIDWORKS manufacturers and mixed-data shops | Small shops needing practical, local FAI |
Which FAI Software Should an Aerospace Company Choose?
Choose DISCUS When the Technical Data Package Is the Problem
DISCUS is the strongest candidate when the organization must collect and account for requirements distributed across drawings, specifications and customer documents.
It is particularly appropriate for aerospace suppliers serving multiple primes and producing large numbers of customer-specific FAI packages.
Choose NX Inspector When the Digital Thread Is the Objective
NX Inspector makes the most sense when the company owns the NX models and wants inspection characteristics to originate within the authoritative product definition.
It should be evaluated as part of an NX, Teamcenter and quality-management architecture—not merely as a faster way to draw balloons.
Choose SOLIDWORKS Inspection for the Most Practical Middle Ground
SOLIDWORKS Inspection is likely the best fit for a manufacturer that uses SOLIDWORKS but also receives drawings and files from other systems.
Its combination of native CAD access, standalone operation, OCR, report templates, measurement capture and Net-Inspect publishing covers a broad portion of the real-world FAI workflow.
Choose QA-CAD When Simplicity, Data Control and Price Matter Most
QA-CAD is worth serious evaluation by smaller suppliers that need accurate drawing ballooning and AS9102 documentation without buying into a large platform.
It may not offer the deepest digital thread, but not every supplier needs one.
Questions to Ask During an FAI Software Trial
A polished demonstration using a vendor’s perfect sample drawing reveals very little.
The trial should use actual company data, including at least one difficult drawing and one revision.
Ask each vendor to demonstrate:
- How does the software identify drawing notes and referenced specifications?
Capturing dimensions alone is not complete requirement accountability. - What happens when the drawing changes?
The software should identify revision differences without forcing users to rebuild the entire inspection project. - Can it produce the customer’s exact AS9102 package?
“AS9102 support” may mean anything from an Excel template to a controlled supplier-submission workflow. - How are partial and delta FAIs handled?
Not every change requires repeating every portion of the original inspection. - Can the software import CMM and other measurement results?
- Can characteristics be traced back to their source requirement?
- Does it support PDFs, scanned drawings and native CAD data actually received from customers?
- Where is controlled technical data stored?
- What modules or additional products are required?
A seemingly simple FAI product may depend on CAD, PLM, quality-management or results-capture licenses. - Can completed data be exported if the company later changes systems?
- How are customer-specific templates maintained?
- Can suppliers and customers exchange the inspection package without purchasing the same software?
FAI Software Does Not Approve the Part
Every product in this comparison can reduce manual work.
None eliminates the need for engineering and quality judgment.
OCR can misread a dimension. Automated ballooning can miss an unusual note. PMI can be incomplete. A CAD model can be authoritative and still contain an engineering mistake. A perfectly populated AS9102 form can document a process that was not actually followed.
FAI software improves accountability by helping users identify, organize and trace requirements.
It does not decide whether the evidence is technically sufficient.
The organization submitting the FAIR remains responsible for its accuracy, and the customer retains responsibility for reviewing and accepting it under the applicable quality process.
The Real Choice Is Not Between Four Products
At first glance, DISCUS, NX Inspector, SOLIDWORKS Inspection and QA-CAD seem to compete for the same purchase.
In reality, they reflect four different priorities:
- DISCUS: Understand and control the complete inspection package.
- NX Inspector: Make quality characteristics part of the model-based digital thread.
- SOLIDWORKS Inspection: Combine CAD integration with flexible inspection documentation.
- QA-CAD: Produce accurate ballooned drawings and FAI reports without enterprise complexity.
For a large aerospace OEM using NX and Teamcenter, NX Inspector may represent the future.
For a supplier serving many OEMs, DISCUS may better reflect the complicated reality of customer data.
For a SOLIDWORKS-centered manufacturer, SOLIDWORKS Inspection provides the most natural workflow.
For a smaller machine shop working from PDFs, QA-CAD may solve the actual problem at a fraction of the cost and disruption.
The best FAI system is not the one with the most ambitious digital transformation story.
It is the one that can account for every applicable requirement, survive a design revision, accept trustworthy measurement results and produce the exact evidence the customer requires—without creating a second quality problem in the process.
Frequently Asked Questions About FAI Software
What is first article inspection software?
First article inspection software helps manufacturers identify product requirements, create ballooned drawings, build bills of characteristics, record inspection results and generate reports such as AS9102 forms.
Is NX Inspector (designcenter inspector) a complete AS9102 reporting solution?
NX Inspector primarily defines and manages model-based characteristics within NX and connects them to Teamcenter and downstream quality processes. Companies should ask Siemens to demonstrate how their full AS9102 reporting, measurement and supplier-submission workflow will be completed using the required Siemens products.
Is DISCUS only for aerospace?
No. DISCUS also supports manufacturing and quality workflows in industries including automotive, medical products and heavy machinery, although it is particularly well known for aerospace FAI and AS9102 use.
Can SOLIDWORKS Inspection work without SOLIDWORKS CAD?
Yes. SOLIDWORKS Inspection is offered as a standalone application as well as an integrated SOLIDWORKS add-in. The standalone application can work with supported PDFs, images and other CAD formats.
Does QA-CAD support AS9102 Rev. C?
Guthrie states that QA-CAD supports exports for AS9102 Rev. C as well as PPAP and configurable inspection-report templates.
Is automated ballooning reliable enough to use without review?
No automated extraction process should be accepted without human review. The quality organization remains responsible for confirming that all applicable dimensions, notes, specifications and other requirements have been identified correctly.
Which FAI software is best for a small aerospace machine shop?
A shop working mainly from customer PDFs should consider QA-CAD, SOLIDWORKS Inspection and DISCUS Desktop. The best option depends on technical-data complexity, required customer formats, security needs, measurement integration and budget.
Which FAI software is best for an NX and Teamcenter company?
NX Inspector (Designcenter Inspector) is the most directly integrated option for defining model-basedcharacteristics in NX and managing them through Teamcenter. The company should still evaluate the broader process for report generation, measured results and supplier collaboration.
