Drawing Error Detection System¶
Source files:
Architechture & Research/RapidDraft/Technical Architecture/Engineering Drawing Error Detection.docxLast synthesized: March 2026
Overview¶
RapidDraft includes a comprehensive drawing error detection engine that identifies and categorizes technical, compliance, and manufacturing-critical issues in engineering drawings and CAD models. The system operates as a rules-based framework with deterministic logic and optional AI-assisted confidence scoring.
Types of Drawing Errors Detected¶
1. Dimensional Completeness Errors¶
- Missing dimensions on critical features
- Incomplete datum reference frames for GD&T calls
- Missing thread specifications on holes or inserts
- Undefined surface finishes on functional surfaces
- Tolerance stack-up issues and missing tolerance combinations
2. Specification and Callout Errors¶
- Conflicting tolerance specifications (over-constrained dimensions)
- Invalid tolerance combinations for stated material and process
- Mismatched or missing material callouts
- Incorrect heat treatment or surface finish specifications
- Non-standard abbreviations or undefined technical symbols
3. Geometric and Feature Errors¶
- Undercut conditions that conflict with manufacturing process
- Sharp internal corners specified without blend radius
- Datum feature selection errors (datum face geometry incompatible with usage)
- Missing profile or contour dimensions on complex surfaces
- Inconsistent feature references across views
4. Assembly and Relationship Errors¶
- Undefined edge treatments at assembly interfaces
- Missing clearance or interference dimensions
- Inconsistent hole patterns across mating parts
- Undefined orientation or alignment callouts for multi-view assemblies
5. Drawing Format and Compliance Errors¶
- Missing or incomplete title block information
- Undefined drawing projection method or view convention
- Missing revision tracking or approval sign-offs
- Non-compliant with stated drawing standard (ISO, ASME, DIN, etc.)
- Missing or incorrect scale notation
- Undefined coordinate systems or measurement origins
6. Manufacturing Constraint Violations¶
- Feature specifications incompatible with stated manufacturing process
- Tolerance class too tight for stated manufacturing capability
- Surface finish requirement incompatible with process (e.g., Ra 0.4 on cast surface)
- Thin wall thickness relative to material and feature depth
- Hole aspect ratio outside normal machining envelope
Technical Detection Mechanism¶
Detection Pipeline¶
The error detection system operates in three stages:
Stage 1: CAD Model Analysis - Extract geometric features (extrusions, holes, pockets, fillets, etc.) - Parse feature parameters (diameter, length, depth, angle, etc.) - Identify faces, edges, and adjacency relationships - Build topology graph (Part → Features → Bodies → Faces → Edges) - Extract surface finish and material attributes from CAD annotations
Stage 2: Drawing Extraction and OCR - Parse 2D drawing views and projections - Use vision/OCR to extract visible callouts, dimensions, and notes - Match extracted dimensions to CAD feature parameters - Identify datum references and their corresponding geometry - Detect missing dimensions by comparing drawn views to extracted feature set
Stage 3: Rules Engine Evaluation - Apply deterministic check rules against extracted geometry and drawing content - Score rule results (pass/fail/warning/info) - Aggregate related errors into meaningful check categories - Optionally apply AI-assisted context scoring to raise confidence on uncertain detections - Output error report with geometry references and remediation guidance
Integration with CAD Data¶
RapidDraft leverages NXOpen (NX integration) and standard CAD formats (STEP/IGES) to extract: - Feature tree structure and build history - Expression-based parametric relationships - PMI (Product and Manufacturing Information) attached to geometry - User attributes and custom properties - Sketch constraints and dimensional relationships
For native NX integration, the system queries:
- Part.Features for feature list and properties
- Body.GetFaces() / Body.GetEdges() for topology
- Feature.GetBodies() for feature-to-geometry mapping
- Expression system for parametric relationships
- NX's GD&T/PMI layer for attached annotations
Check Categories¶
Checks are organized into five primary packs, each targeting a specific domain:
Pack A: Drawing Spec and Compliance (Mandatory)¶
Ensures drawings conform to stated standards and contain required metadata. - Title block completeness - Projection method consistency - View labeling and scale notation - Drawing standard compliance (ISO, ASME, DIN) - Revision and approval tracking
Pack B: Dimensional Completeness (Foundation)¶
Identifies missing or incomplete dimensions critical to part definition. - All features dimensioned in at least one view - Datum reference frames defined for GD&T callouts - Material, heat treatment, and surface finish specified - Thread specifications on all fastening holes - Coordinate dimensions or edge conditions on functional surfaces
Pack C: Tolerance and GD&T Logic (Advanced)¶
Validates geometric dimensioning and tolerance callouts for correctness and manufacturing feasibility. - Datum priority and accessibility rules - Tolerance zone interpretation (bilateral, unilateral, profile) - Feature control frame syntax and symbol validity - Material condition modifiers correctly applied (RFS, MMC, LMC) - Tolerance stack-up and worst-case analysis
Pack D: Manufacturing Feasibility (DFM)¶
Flags design features that conflict with stated manufacturing process or capability. - Feature sizes achievable with stated process - Surface finish specification matches process capability - Thin walls, aspect ratios, and material flow concerns - Undercut, draft, and draft angle specifications - Tool access and fixturing implications
Pack E: Assembly and Interface Logic¶
Ensures multi-part relationships and assembly interfaces are fully specified. - Mating surface definitions and contact areas - Clearance and interference dimensions on mating features - Alignment callouts for multi-view assemblies - Edge treatment and burr specifications at interfaces - Fastener hole patterns and orientation references
Error Taxonomy¶
Errors are classified by severity and impact domain:
By Severity¶
| Level | Definition | Action |
|---|---|---|
| Critical | Missing or incorrect dimension that makes part unmfg or causes assembly failure | Block release; requires engineer correction |
| High | Specification that conflicts with process or creates cost driver | Flag for review; allow release with justification |
| Medium | Incomplete or ambiguous callout that adds interpretation burden to manufacturing | Recommend correction; track for future reference |
| Low | Minor format or style inconsistency; no impact to manufacturability | Suggest best practice; informational only |
By Domain¶
- Dimensional: dimension presence, value consistency, and completeness
- Tolerance: GD&T syntax, feature control frame validity, and tolerance logic
- Process: manufacturing capability and feature feasibility
- Standards: compliance with stated drawing standards and conventions
- Assembly: multi-part relationships and interface specifications
By Scope¶
- Local: errors affecting a single feature or dimension
- Part-level: errors that affect overall part definition or classification
- Assembly-level: errors affecting relationships between multiple parts
- System-level: errors that block bill-of-materials generation or release workflows
Output and Reporting¶
Each detected error is reported with: 1. Check ID – unique identifier for the rule that triggered the error 2. Error Category – which pack (A–E) and domain the error belongs to 3. Severity – critical, high, medium, or low 4. Feature Reference – which feature(s) in the CAD model are involved 5. Geometry Pointer – face, edge, or coordinate location in the 3D model 6. Description – plain-language explanation of the issue 7. Remediation Guidance – suggested correction or reference to standard 8. Evidence – reference to dimension value, feature parameter, or drawing view
Reports are generated as: - Inline drawing markup (highlights on PDF or screenshot) - Structured report (JSON/CSV) for programmatic processing - Review decision log (tied to specific geometry and revision)
Confidence and Human-in-the-Loop¶
For vision-based or AI-assisted checks, the system scores confidence: - High confidence (>95%) – deterministic checks, measured values, explicit specifications - Medium confidence (75–95%) – pattern-based rules, manufacturing process inference - Low confidence (<75%) – context-dependent checks requiring engineer judgment
Low-confidence findings are tagged as "suggestions" and require engineer approval before inclusion in release documentation.
Integration with RapidDraft Workflows¶
The error detection system feeds into: 1. Drawing Memory – captured check outcomes are stored and re-applied on model revisions 2. Review Decision Capture – engineer resolutions to flagged errors become reusable decisions 3. Manufacturing Release Checks – pack A–E checks are run before each release milestone 4. AI-Assisted Dimensioning – detected missing dimensions inform where the AI should suggest placement
This creates a feedback loop where repeated manufacturing feedback informs future check precision and severity tuning.