Iconic CAD Workflow Specification

Purpose

Iconic CAD Automation intends to democratize basic and advanced design capacity by allowing anyone to design anything in a matter of hours of study. This is done by converting technology into components represented graphically by icons. One then manipulates these icons, and with AI assist, produces technically correct CAD at LOD 500 finishing level.

Example

We will start with the framing for a house as an example of how we use modular icons to design the framing for a house, and generate:

1. All the technical drawings
2. Build instructions for each module
3. Admissible parts specfication for each module, and admissible tooling specification for each module
4. Part list or callout for parts for each module included in the technical drawing
5. Quality Control requirements included in each technical drawing
6. Fastener schedules called out for each module
7. Overall assembly cost and weight
8. Overall assembly callouts by module number
9. Each technical drawing providing both a simple number, and a full description of module
10. Complete bill of materials for the entire wall framing including fasteners and consumables
11. A shadowboard design for a 24-person team build, and 48 person team build
12. Workflow instructions for the overall assembly, based on 24 people.

Meta

1. For each module, role allocation based on name database (24 or 48)

Scope

Method developed for Seed Eco-Home first, then for all machines.

For the home:

• 1000 parts. List here - https://chatgpt.com/share/69a8e9ac-709c-8010-86b5-e25a36d512fb
• 1000 modules
• 1000 tools
• 1000 skills

Basic Taxonomy of Part Library Assets Generated

• Icon - for iconic design
• Thumbnail of actual CAD. Later to be developed into stylized
• CAD
• Schema. Part, assembly, system, ecosystem.

Icon Specification

• SVG
• Human modifiable in SVG graphics program for passing new parameters from icon. Implemented by CAD parsing of icon and its human editable attributes.
• Icon attributes can also be modified in schema

Process Specification

• Based on explicit taxonomy of assets, published on the wiki
• Process is designed for automation with AI, leveraging library-scale development that can be distributed
• Schemas are then post-processed to wiki libraries and documentation
• Versions of schema and process are maintained via git or other version control

Schema Outcomes

• Generation of modifications
• Library icon in svg - for part libraries on wiki, parsing SVG images for iconic CAD automation
• BOM
• Technical Drawing. For full assembly - full building plan check package
• Exploded part diagram
• Build procedure
• Costing
• 3D print file
• Calculations - weight of assembly, strength, thermal, fluid flow, etc.

House Taxonomy

• Use moduletype_part_attributes.fileextension - etc
  • Moduletypes corresponds to the 20-30 trades involved: foundation, framing, electrical, plumbing, cabinets, etc.
  • Part is the name of part (a wire, pvc fitting, piece of lumber)
  • Attributes - includes things like size. Version is its specific identity such as size, etc. For example, a plumbing fitting can be 1/2" or 3/4" etc. Library contains all of them, and to be universal, whole library is used in any given task

Super-Schema Outcomes

• Part library generation for wiki - code for creating library, including correct part naming.
• Part library generation - image uploads

CAD Schema Specification

• Technical Drawing
• BOM information
• QC information
• Build Procedure information
• Includes source links
• Includes labor estimation based on industry standards per unit (square footage per hour, etc)
• Includes ports - how other modules and parts connect to this

Post-Processor Compilers

• Library Generators (CAD, schema, icon, thumbnail)
• Stylized graphics can be produced such as for LAIs
• Full package submitted to building department
• Exploded part diagrams
• Build instructionals - above module level