Mechanical development processes for mechatronic products
Mechanical SPICE 2.1 extends the Automotive SPICE® 4.0 model with development processes for mechanical engineering. Developing mechatronic components usually involves several development disciplines working together. In the typical case, these are mechanical engineering, electronics or hardware development, and software development.
We assessors call the level at which the requirements for the product — and the product itself — are described, before being broken down into the individual disciplines, the system level. Ideally, the documentation below that level is split exactly along the disciplines that actually exist within the development organization. (At a previous employer of our founder, there was a dedicated department for BLDC motor development alongside mechanical, hardware, and software engineering.)
Mechanical development often uses different terminology than software development. Here, the discussion revolves around simultaneous engineering (of the product and the production tooling), drawings, 3D models, design guidelines, installation space, prototype and production tooling, initial sample inspection reports, environmental testing, and so on. As experienced assessors with a background in development ourselves, we know these terms and can put them into context.
And yes: our founder has recently joined the INTACS® working group and is helping bring exactly these terms into focus for the next version, making life easier for other assessors and project teams. If you have projects where mechanical development needs to be included in the assessment scope, feel free to reach out. We're happy to support you with our expertise.
