Your challenge

Design automation is ‘hot’ when it comes to efficient development of innovative and complex high performance products. Central themes are design re-use, unambiguous communication between disciplines and between parties in the supply chain, faster design iterations and continuous verification and validation.

Commercial-of the-shelf (COTS) design automation tools are promising, but what really are the advantages? What should duly be taken into account when introducing or further implementing design automation and the tools that facilitate this?

Typical questions that arise are for example:
  • How good are those COTS tools actually – are those marketing stories really true?
  • Is it possible to retain and use existing and validated models/code/IP?
  • Our products do have very specific characteristics – are COTS tools usable and flexible enough?
  • We are not a multinational with large design teams – is there sufficient benefit for SMEs?
  • Engineers already make extensive and effective use of design automation tools, is there more to gain for our organization and if so at what costs?
  • What is the impact on the organization and where do I start?

In other words: Is there, in our particular situation, sufficient benefit to gain from COTS design automation tools? What are the (dis)advantages and which tools are we talking about? How do I quickly gain the most at limited risk and costs?

The MonkeyProof solution

MonkeyProof Solutions takes on project management for (strategic) evaluation and implementation projects related to design automation tools like MATLAB & Simulink. Clearly every project is different and therefore the approach is tailored to your organization and requirements.

Examples of projects

MATLAB standardization aimed at:

  • Facilitation of communication between individuals, teams and disciplines
  • Reduction of the number of engineering software tools in use within an organization
  • Prevention of unnecessary repeat design work
  • Expansion of usage of MATLAB & Simulink including definition of infrastructure and processes for Model Based Engineering & Development
  • Usage of automatic code generation tools for embedded applications within existing or new environments

The MonkeyProof Solutions approach generally contains the following aspects/phases:

  • Process audit through interviews focused on effective communication and reduction of the number of software tools in use
  • Code & model reviews focused on effective tool usage
  • Reporting including SWOT analysis, recommendations and brief ROI
  • Phased transition plan aimed at risk mitigation
  • Project- and interim management