Issue link: https://iconnect007.uberflip.com/i/1544155
22 SMT007 MAGAZINE I APRIL 2026 James, how do you get that perfect Tuesday, where you have a worry- free, smooth process for inputting a job that's been given to you for a quote? James Green: It sounds like a dream, doesn't it? For me, the harness engineering world is a very fragmented ecosystem. Every organization speaks a slightly differ- ent digital language. Every manufac- turer uses a slightly different format for the data. It's a big problem that we're trying to solve, and there's no quick fix. For decades, the safest way to exchange data has been in a draw- ing format, which breaks the digital chain. We're trying to rebuild that digital thread, and part of that is standardizing the data exchange framework. Vrobel: For my perfect Tuesday, I imagine an OEM engineer finishes a design and hits send. Instantly, that design is received by the manufacturer, not as a PDF image, but as rich, intelligent data. When that information is structured, it can flow through a digital pipeline. The system validates the design, identifies missing components such as terminals or seals, aligns the parts with the supply chain, and automatically generates a complete manufactur- ing bill of materials. The same data can then drive quoting, procurement, and even machine program- ming without manual entry. The manufacturer's system reads it, validates it against stock, checks for errors, and generates a precise quote within minutes of the order being placed. That same data flows directly to the cut- and-strip machines. No data entry, no interpreting the drawing, no phone tag about missing serial numbers. In this scenario, we aren't fighting fires; we are focusing entirely on creating engineering value and production velocity. This is where the rest of the electronics industry is heading, and this is the connected ecosystem we see for wire harness. Why aren't we there yet?" Excellent point. What's the ideal architecture for getting a complete digital flow for a wire harness and who's involved? How do we get to a complete digital flow? Where are the breakdowns, and what are the fixes? Singh: The starting point is stan- dardization. Standards create a common language and build trust across the supply chain, allowing information to flow more efficiently between OEMs, design teams, and suppliers. The goal is to standard- ize the inputs to the design process so that drawings, BOMs, connector definitions, wire specifications, and layout data are clearly defined. Once those inputs are structured, a digital thread can connect design, quoting, and manufacturing. Most breakdowns occur when critical information is missing. The solution is clear design-definition standards, so suppliers receive complete informa- tion from the start. How do you get standardization started? Singh: Standardization begins with education. Engineers need clear guidance on the minimum information required for design packages sent to suppliers and contract manufacturers. That includes complete drawings, BOMs, specifications, and other critical design details. At the same time, the tools used in the design process need to improve. Design systems should automatically detect missing information and alert engineers before files are released. When engi- neers are supported by both clear standards and smarter tools, the quality of design data improves, and suppliers can respond faster. This combination helps the entire ecosystem engineer and industri- alize products more efficiently. Is the education you're outlining currently avail- able, or is it being developed? Is there a gap in education? Singh: There is still a gap in education across the industry. In automotive programs, particularly in wire harness and EDS teams, many newer engineers come from mechanical engineering backgrounds rather than electrical or systems engineering. They are highly capable engineers, James Gre en