At CADnadian, we prioritize precision, consistency, and compliance in every project. Quality Control provides product standard, client standards, and present information. Quality Assurance is the process of making sure a product or service meets quality standards before it's released. It involves planning, monitoring, and testing to prevent problems or defects. Our QA/QC standards ensure that all CAD deliverables meet industry best practices while aligning with CADnadian's unique requirements. These guidelines cover file formatting, layering, naming conventions, and deliverable specifications, ensuring seamless collaboration and top-quality results. By adhering to these standards, we maintain clarity, efficiency, and professionalism across all stages of project development.
QA / QC
GUIDELINES
QA/QC CHECKLIST
FILE FORMAT AND SETUP
-
CADnadian Electronic File Format: Adherence to the specified format.
-
CADnadian Policy on Model Space and Paper Space: Guidelines for usage and consistency.
-
CADnadian External Reference (XREFs) Policy: Rules for managing external references in drawings.
-
CADnadian Scale, Units, & Tolerances: Standardized units, scales, and tolerances.
-
CADnadian Fonts and Text Styles: Approved fonts and text styles for uniformity.
-
CADnadian Dimensioning: Standard dimensioning practices.
-
CADnadian Details/Block Definitions: Defined block libraries and details.
-
CADnadian Title Block/Cover Sheet/Size: Standardized templates for title blocks and sheets.
-
Current Date Indicated on Drawings: Drawings must display the current date for traceability.
LAYERING
-
CADnadian Standard Layering: Uniform layer standards.
-
CADnadian Layer Name Formatting: Consistency with CADnadian naming conventions.
-
General Rules about Naming and Uses: Guidelines for effective layer management.
-
Layer Attributes: Standard colors, pens, and linetypes for each layer.
​
FILE NAME CONVENTION
-
Building and Project Identification: Unique identifiers for buildings and projects.
-
Discipline Designation Codes: Codes for different disciplines.
-
Drawing Sheet Numbers: Sequential numbering for sheets.
-
Drawing File Name: Descriptive and consistent file names.
-
Door Numbering: Standardized door numbering system.
-
Area Polyline and Square Footage: Proper use of polylines for area calculations.
CAD FILE TRANSLATION POLICY
-
Full AutoCAD® Compliance: Ensure compatibility with AutoCAD standards.
-
Bound Xrefs and Images: Xrefs and images must be bound before submission.
-
Translation Testing Procedures: Validate translation, layering, and plotting accuracy.
DELIVERABLES AND CLOSE OUT
-
Progress Submittal: Drawings must be submitted at specific project phases or percentages.
-
Construction Documents: Final construction-ready documents.
-
Supplemental Drawing Revisions: Updates and revisions as required.
-
“As-Built” Documents: Final, as-built documentation reflecting the completed project.
-
AutoCAD® .dwg and .PDF Submissions: Deliverables must include both .dwg and PDF formats.
ACCOUNTABILITY
-
Representative Name & Signature: Each submission must include the printed name, signature, and date of the accountable vendor representative.
This structured QAQC guideline ensures that all CAD deliverables meet CADnadian's highest standards of quality and compliance, maintaining consistency across all projects.
Red-line Markups
Redline markups are annotations made on drawings to highlight required changes or corrections. Using color coding in this process enhances clarity and improves communication, especially in complex projects. Here's how to do redline markups effectively:
TOOL REQUIREMENT
-
Physical Markups:
-
Use colored pens or markers (red, blue, green, etc.).
-
-
Digital Markups:
-
Utilize CAD software with markup tools (e.g., AutoCAD, Bluebeam, or Revu).
-
Enable layers or color settings to distinguish changes.
-
STANDARD APPROACH
Assign specific meanings to each color to reduce confusion. A standard approach include:
-
Red: Indicates errors or corrections (e.g., dimension errors, misalignments).
-
Blue: Highlights additional information, new elements, or proposed changes.
-
Green: Used for approvals or notes on completed changes.
-
Yellow: Flags areas needing clarification or further review.
-
Black/Grey: General annotations, comments, or low-priority notes.
This scheme can be customized based on project requirements or organizational standards.
APPLYING MARKUPS
Identify Issues: Carefully review the drawing and identify errors, missing details, or inconsistencies.
-
Annotate Clearly:
-
Use arrows, symbols, and text boxes to point out specific issues.
-
Write concise notes explaining the required action (e.g., "Increase dimension to 200 mm").
-
-
Apply Colors:
-
Use the assigned color for each type of annotation.
-
Ensure the markup colors stand out against the drawing background.
-
COLLABORATION & SHARING
Share the redlined drawing with relevant team members.
-
Maintain a legend explaining the color-coding scheme for clarity.
-
Use a centralized platform for collaboration (e.g., BIM 360, SharePoint).
REVEW AND UPDATE
Response from Designers: The responsible team reviews the markups and implements the changes.
-
Verification: Conduct a follow-up review to ensure all issues were addressed correctly.
-
Approval: Use green or another designated color to mark approved changes.
BEST PRACTICE
Consistency: Use the same color scheme across all projects to avoid confusion.
-
Documentation: Keep a record of the original and revised drawings along with markup notes for future reference.
-
Training: Train team members on the color-coding system and markup procedures.
BENEFIT OF USING COLOR CODING
Improves readability and prioritization of changes.
-
Reduces errors during implementation by making annotations clear.
-
Facilitates better communication among multidisciplinary teams.