APRIL 20249MANUFACTURING TECHNOLOGY INSIGHTSintroduction process. This has created sub-optimal utilization of resources and time in embedded software development.Prominent web-oriented software development companies have introduced software development protocols such as Agile and Scrum, which excel in creating connected products, web-based platforms, and IT infrastructure. However, they don't seamlessly align with traditional manufacturing paradigms, which create microcomputer-based products like appliances, automotive components, and medical devices. Agile and Scrum prioritize quick turnarounds and rapid issue resolution during development. In contrast, manufacturing involves extended timelines and complex interdependencies across various stages. To address this, a hybrid approach divides engineering activities into two segments: electro-mechanical and embedded software.These two segments coexist within the same engineering entity, with one focusing on mechanical aspects and the other on software advancement. The rationale behind this division is to separate the activities and progress them at different rates. The mechanical aspect, significantly impacting the manufacturing process, adheres to the well-established sequential model within the manufacturing realm. This involves identifying potential risks and customer requirements, followed by a gradual step-by-step development process. The intricate interplay between the manufacturing process and mechanical components makes accommodating alterations in mechanical design challenging.In contrast, the trajectory of software development doesn't follow a similar linear progression. The software realm has the flexibility to embrace an agile methodology, allowing for rapid integration of changes, even in the later stages of development. However, it's essential for the entire organization to understand and acknowledge the distinct nature of these two developmental cycles. The alignment between both cycles occurs at the culmination of the process (namely, volume production), not at intermediary points (design freeze, Production Part Approval, first article inspection).In the manufacturing sector, the conventional expectation is for the production team or factory to await the completion and finalization of the design before initiating the manufacturing process. This is due to the resource-intensive and time-demanding nature of configuring manufacturing setups. It's preferable to hold off on initiating the development and preparation of the production line while the engineering design remains subject to potential modifications. For instance, consider a situation where the original design for a metal box specified dimensions of three inches by five inches, resulting in the fabrication of corresponding sheet metal assemblies. If there's a subsequent need to increase its size by 10 percent, all the resources and capital invested in the existing process would be wasted.The proposed hybrid methodology introduces a contrasting approach in treating software and embedded system development compared to mechanical systems like fabricated metal or plastic parts, or electro-mechanical assemblies. This distinction arises from the fact that the long lead time steps like developing tooling, preparing supply chain, developing new material movement, establishing assembly automation, doesn't hinge on the software which goes in these products. The assembly procedure primarily involves integrating mechanical elements, whereas the software dimension lacks a direct impact on the assembly process. As a result, the long lead time steps described before are not dependent on the software.The logic underlying this differentiation lies in the capacity for the mechanical production system to prepare its operations while software engineers adopt an agile framework. This approach allows for just-in-time incorporation of software within the manufacturing line, bypassing the need to await the overall design's completion before initiating readiness tasks for the manufacturing line. Through the implementation of the hybrid approach, embedded software development can effectively leverage a larger portion of the overall project timeline, enabling the delivery of a greater number of features while optimizing resource utilization
< Page 8 | Page 10 >