With more than 30 years of experience, the Dana Plymouth team offers end-to-end Product Development solutions for global OEMs and Tier 1 suppliers. Always striving to help customers overcome technology constraints, resource crunches and tight product development budgets.
The Dana Plymouth team follows a rigorous industry standard APQP process when undertaking Product Development projects, whether that's creating a new hardware target for the OpenECU™ range of embedded controllers, or delivering a cost and package optimized controller to meet a specific customer need. At each stage of development, appropriate process is employed to ensure the quality of the end product meets expectations for its intended use. The Dana Plymouth team has many years of experience in all aspects of Product Development, such as design analysis through DFMEA, and Product Validation.
Learn More about DFMEA Learn More about Product ValidationDana provides engineering services for complete product development utilizing the V-model development process. Through our experience in developing products we can reuse existing OpenECU hardware or software components translating to time and cost saving for customers.
Every project begins by understanding the customer’s requirements of the project. This includes deep-dive technical discussions, and through requirements workshops.
Read more >Analysis of a system during development of a custom electronics solution focuses both on the ability of the system to deal with random hardware failures and for the development process to eliminate systematic sources of error.
Dana focuses on various failure mode analysis techniques for System and Safety Analysis.
Read more >The final requirements are assembled from analysis and elicited requirements from earlier phases. These requirements are broken down for the intended architecture of the system.
Read more >Hardware requirements start at the system level and provide hardware architectural details. In this stage decomposition of system level requirements into hardware and software implementable requirements is performed.
Read more >The high-level software requirements are derived from the system and safety requirements. These requirements are analyzed to determine the software architecture design and are the basis for deriving the low-level requirements.
Read more >Hardware analysis encapsulates electronic and mechanical design and serves to minimize project risk while maximizing confidence in pending hardware build and verification efforts. Multiple analysis methods are utilized and often enhanced with simulations.
Read more >The goal of requirements analysis is to ensure that the requirements are complete and consistent and that OpenECU fully understands the customer's needs and expectations through the different phases of development.
Read more >A functional requirement defines a function of a system or its component (software unit or software feature).
Read more >Using concept designs and physical modeling of mechanical packaging and electronics hardware architecture is brought into physical embodiment.
Read more >OpenECU implements software in both C and Simulink. Implementation follows internal guidelines for style and architecture based on MISRA for C and MAAB for Simulink.
Read more >Hardware build from rapid prototyping with modifications to volume production with quick turn and cost optimization.
Read more >Hardware integration testing is the high-level collection of hardware test activities encapsulating requirement- based design verification testing. The formal test activities consist of functional testing, bench testing, fault insertion testing and Design Verification and Production Verification (DV & PV) testing.
Read more >Unit testing provides the necessary assurance that the software is operationally correct and behaves well at boundary and edge conditions.
Read more >Hardware or software integration testing verifies that the hardware or software interfaces have been correctly specified and implemented.
The goal of Vehicle Integration is to ensure that when the ECU is introduced to the vehicle environment, all of the inputs and outputs of the system are supported and operating as expected in the new vehicle environment.
Read more >System Integration involves the introduction of the developed controller to the other components like sensors and actuators in order to perform overall testing of a complete system comprised of multiple components or elements.
Read more >Item integration testing of the control software is performed in diverse ways. Software unit tests are the most common activity including the Item Integration Testing Plan.
Read more >
OpenECU utilizes the V-Model Development Process to develop your Custom ECU. All development projects will generate a Quality Plan to clearly define the project deliverables and set the framework for the project. The process can be tailored to meet customer specific requirements.
Accessibility