revision-dcl.md — Revision Control Dialog¶
File: revision.dcl
Version: v3.60
Category: Dialog Definitions
Size: 6.2 KB (188 lines)
Note
Drawing Revision Management
Track drawing revisions including revision clouds, delta symbols, revision blocks, and change history for quality control and documentation.
Functional Purpose¶
Revision Control - Manages drawing revision process including markup, tracking, approval, and documentation of all design changes.
Key Functions:
Revision marking (clouds, triangles, revision symbols)
Revision block (table on drawing with revision history)
Change tracking (what changed, why, when)
Approval workflow (review and sign-off)
Revision numbering (sequential tracking)
Distribution control (who received revised drawings)
Typical Workflow¶
1. Design change required (field issue, engineer direction)
2. User opens revision-dlg
3. User creates new revision:
• Revision: B (previous was A)
• Date: 1/20/2026
• Description: "Increased window opening 2'"
4. User draws revision cloud around changed area
5. User places delta symbol: "?B"
6. System updates revision block on drawing:
| Rev | Date | Description | By |
|-----|----------|------------------------|-----|
| A | 1/15/26 | Issued for approval | JD |
| B | 1/20/26 | Increased window 2' | JD |
7. Drawing reissued with revision marks
8. Fabricator receives revised drawing
9. Old revision superseded (archived)
Control Semantics¶
Revision Information:
rev_number- Revision identifier:Letters: A, B, C… (most common)
Numbers: 1, 2, 3…
Dates: 2026-01-20
rev_date- Revision daterev_desc- Change description (brief)rev_by- Who made change (initials)rev_checked- Who reviewed (QC initials)rev_approved- Engineer approval (stamp/seal)
Revision Marking Tools:
rev_cloud- Draw revision cloud:Freehand cloud shape
Surrounds changed area
Auto-closes shape
rev_delta- Place delta symbol:Triangle: ?
With revision letter: ?B
Points to changed item
rev_note- Add revision note:Text explaining change
References detail/section
Revision Block:
rev_block- Update revision table:Location: Lower right corner typical
Auto-numbered revisions
Date stamp automatic
Columns: Rev, Date, Description, By
Revision Types:
rev_type- Change classification:Minor (non-structural, clarification)
Major (dimensional, structural change)
Addendum (adds new information)
Correction (fixes error)
Revision Marking Standards¶
Revision Cloud¶
Appearance:
??????????
?? ??
?? CHANGED ?? ? Surrounds changed area
?? AREA ??
??????????
?B ? Delta symbol with revision letter
Purpose:
Highlights what changed
Quick visual identification
Clear for field personnel
Delta Symbol¶
Placement:
?A - First revision
?B - Second revision
?C - Third revision
Placed near:
- Changed dimensions
- Modified details
- New notes
Revision Block¶
Standard Format:
???????????????????????????????????????????
? REVISIONS ?
???????????????????????????????????????????
? Rev ? Date ? Description ? By ?
???????????????????????????????????????????
? - ? 1/10/26 ? Issued for ? JD ?
? ? ? approval ? ?
???????????????????????????????????????????
? A ? 1/15/26 ? Revised window ? JD ?
? ? ? size per owner ? ?
???????????????????????????????????????????
? B ? 1/20/26 ? Added weld ? JD ?
? ? ? plate at door ? ?
???????????????????????????????????????????
Revision Workflow¶
Change Request Process¶
1. Change identified:
• Field condition
• Owner request
• Engineer correction
• Code requirement
2. Engineer evaluates:
• Structural impact?
• Cost impact?
• Schedule impact?
• Approval required?
3. Design change made:
• Update panel design
• Regenerate drawing
• Mark changes with cloud/delta
4. Revision documentation:
• Create revision record
• Update revision block
• Increment revision letter
5. Review and approval:
• QC check
• Engineer review
• Stamp/seal if required
6. Distribution:
• Reissue drawing
• Track who received
• Supersede old revision
7. Implementation:
• Fabricator updates work
• Field crew notified
• Closeout documentation
Revision Numbering Systems¶
Letter System (Most Common)¶
- (Dash) = Preliminary/Not for construction
A = First revision
B = Second revision
...
Z = 26th revision (rare!)
Advantages:
? Simple, universal
? Easy to identify sequence
? Industry standard
Number System¶
0 = Issued for approval
1 = First revision
2 = Second revision
...
Used when:
- Many expected revisions (>26)
- Computer system preference
Date System¶
2026-01-15 = First issue
2026-01-20 = First revision
2026-01-25 = Second revision
Used when:
- Few revisions expected
- Date tracking critical
Integration¶
Called By: Drawing tools, revision menu Updates: Revision block, drawing metadata, project log Archives: Previous revisions (version control)
Data Tracked:
Revision history per drawing
Cumulative project changes
Approval status
Distribution list
Best Practices¶
Revision Marking:
? Cloud all changed areas (complete coverage)
? Use delta symbols consistently (same location scheme)
? Clear descriptions (specific, concise)
? Date stamp all revisions (track timing)
Revision Control:
? Sequential numbering (no skipping letters)
? Archive superseded drawings (version history)
? Track distribution (who has what revision)
? Major changes = new drawing (not revision Z!)
Common Mistakes:
? Missing revision cloud (change not obvious)
? Vague description (“Revised per RFI” - what changed?)
? Wrong revision letter (skipped B, went A ? C)
? Old revision still in circulation (confusion!)
Change Order Coordination¶
Revision + Cost:
Revision B: Increased window opening 6"
Impact:
- Material: +$200 (larger frame)
- Labor: +$150 (more cutting)
- Schedule: +2 days
Total Change Order: +$350
Revision links to CO-005 (change order tracking)
Documentation Metadata¶
Enhancement Status: ? COMPREHENSIVE - ENHANCED [16/23 v3.60 remaining]
End of Document