Lighting Up Design Blind Spots
summary
An event driven observability layer connects ECAD and MCAD with a shared schema, immutable audit logs, and Kafka broker stream processor plumbing that emits geometry hashes, variant tags and library sync events. Pilot boards cut revision lead time from 7 to 3 days, part approvals from 4 to 1.5 days and board spins from 3 to 2, while late rework costs cited as 8–10% and schedule slips of 4–6 weeks shrink. The build includes EDA library.xml sync, Kibana payload inspection, replay and backpressure and it demonstrably works at pilot scale.
AI-written summary · about
chapters (12)
- 0:00Introduction and Session Overview
- 0:32Identifying the Collaboration Gap
- 0:44Event-Driven Vision and Core Building Blocks
- 1:19Real-World Challenges and Solutions
- 2:54Event-Driven Architecture and Benefits
- 3:40Core Building Blocks: Schema, Audit, and Library Sync
- 5:44Cross-Cutting Enablers and Resilience
- 7:01Putting It All Together: Practical Implementation
- 8:05Pilot Projects and Business Impact
- 8:51Monitoring and Observability
- 9:23Phased Rollout and Best Practices
- 10:28Conclusion and Final Thoughts
related talks
50mLean Design in Practice
30mBuilding Better Products Faster
20mThe metacognitive design loop
30mJames Stanier, Winter Wi, Janet Balneaves a panel discussion at LeadDev London 2023
23mFront-End Platform Engineering
33mRefactoring with Observability
29mIn the file with
44mFission To Fusion – Boosting The Value Of Your Design Process