Sign up to save your podcasts
Or
Share S2, E14: Transform Instead of Link: CADTALK's History and Philosophy
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
S2, E14: Transform Instead of Link: CADTALK's History and Philosophy
Jeff and Scott dive deep into CAD Talk's product evolution, exploring why most integration tools simply "throw data over the wall" while CAD Talk takes a transformational approach. Scott shares the breakthrough moment that shifted their philosophy from basic data syncing to intelligent transformation, explaining how raw materials and routing requirements revealed the fundamental differences between engineering and manufacturing bills of materials.
Key Takeaways
- Integration vs. Transformation: Most tools simply automate data silos, while true integration requires transforming engineering intent into manufacturing execution
- E-BOM ≠ M-BOM: Engineering and manufacturing bills of materials serve different purposes and shouldn't be forced into symmetry
- Beyond Import Tools: Saving keystrokes is table stakes - the real job is getting products from design to manufactured goods that generate revenue
- Holistic Problem Solving: Micro-optimizations in engineering can create macro problems downstream in manufacturing
- Data Doesn't Need to Live in CAD: Manufacturing-specific data like product codes and routings don't belong in engineering systems
Best Quote
"Until we figure out how to create anti-matter replicators like we have in Star Trek, where you literally just take the idea that you have and it just generates it out of anti-matter, somebody has to figure out how to make the darn thing. That's what the ERP does." - Scott Brickler
Episode Timestamps
- 00:07 - Introduction to CAD Talk product evolution discussion
- 02:27 - Why this story matters: positioning as AI intelligence engine vs. import tool
- 05:17 - The journey spectrum: importing is just the beginning
- 07:37 - The "linky model" problem and engineer perspective limitations
- 11:04 - Breaking down the symmetry assumption between CAD and ERP
- 17:17 - The breakthrough moment: raw materials as transformation catalyst
- 21:44 - Why linking breaks down when solving the complete problem
- 25:51 - System theory and micro vs. macro optimization examples
- 30:03 - Market confusion and problem awareness evolution
- 34:55 - Introduction to Design for Manufacturing (DFM) approach
- 37:37 - Wrap-up and preview of next DFM-focused episode
Connect with us:
Youtube - https://www.youtube.com/@cadtalk6667
LinkedIn - https://linkedin.com/company/cadtalk
Website - https://cadtalk.com/demo
Spotify - https://open.spotify.com/show/6ew1yioTzMOqMvWQxN4eZX
Scott Brickler - https://www.linkedin.com/in/scottbrickler/
Jeff Brickler - https://www.linkedin.com/in/jeff-brickler-cadtalk/
View all episodes
By CADTALK SoftwareJeff and Scott dive deep into CAD Talk's product evolution, exploring why most integration tools simply "throw data over the wall" while CAD Talk takes a transformational approach. Scott shares the breakthrough moment that shifted their philosophy from basic data syncing to intelligent transformation, explaining how raw materials and routing requirements revealed the fundamental differences between engineering and manufacturing bills of materials.
Key Takeaways
- Integration vs. Transformation: Most tools simply automate data silos, while true integration requires transforming engineering intent into manufacturing execution
- E-BOM ≠ M-BOM: Engineering and manufacturing bills of materials serve different purposes and shouldn't be forced into symmetry
- Beyond Import Tools: Saving keystrokes is table stakes - the real job is getting products from design to manufactured goods that generate revenue
- Holistic Problem Solving: Micro-optimizations in engineering can create macro problems downstream in manufacturing
- Data Doesn't Need to Live in CAD: Manufacturing-specific data like product codes and routings don't belong in engineering systems
Best Quote
"Until we figure out how to create anti-matter replicators like we have in Star Trek, where you literally just take the idea that you have and it just generates it out of anti-matter, somebody has to figure out how to make the darn thing. That's what the ERP does." - Scott Brickler
Episode Timestamps
- 00:07 - Introduction to CAD Talk product evolution discussion
- 02:27 - Why this story matters: positioning as AI intelligence engine vs. import tool
- 05:17 - The journey spectrum: importing is just the beginning
- 07:37 - The "linky model" problem and engineer perspective limitations
- 11:04 - Breaking down the symmetry assumption between CAD and ERP
- 17:17 - The breakthrough moment: raw materials as transformation catalyst
- 21:44 - Why linking breaks down when solving the complete problem
- 25:51 - System theory and micro vs. macro optimization examples
- 30:03 - Market confusion and problem awareness evolution
- 34:55 - Introduction to Design for Manufacturing (DFM) approach
- 37:37 - Wrap-up and preview of next DFM-focused episode
Connect with us:
Youtube - https://www.youtube.com/@cadtalk6667
LinkedIn - https://linkedin.com/company/cadtalk
Website - https://cadtalk.com/demo
Spotify - https://open.spotify.com/show/6ew1yioTzMOqMvWQxN4eZX
Scott Brickler - https://www.linkedin.com/in/scottbrickler/
Jeff Brickler - https://www.linkedin.com/in/jeff-brickler-cadtalk/