Project support

At the start of a project correct choices about the deployment of design automation tools can yield large profits in subsequent phases of the project. Here too, a good start is half the battle won.

Your challenge

Typical questions at the beginning of a project are:

  • What are the current capabilities and limitations of design tools?
  • What works well and what is not yet fully mature?
  • How do we set up our models such that in later design phases a minimum of re-work is needed?
  • How can I work simultaneously with multiple people / teams on a design?
  • How can legacy code / ip effectively be reused?

In projects with an innovative character, it is not uncommon for specifications to change. This may result in a (partial) abandoning of the chosen methodology. One may run into limitations of design tools (in terms of computing power, or functionality, features) . For engineers it is extremely time-consuming to seek work-arounds or alternative approaches on their own.


  • How can project engineers focus on their added value activities?
  • How do project engineers get the most from the tools they use, spending minimal time on the tools themselves?
  • When project objectives change, how do you alter the methodology quickly, whilst preventing unnecessary  extra work or reduced flexibility at a later stage?

The MonkeyProof solution

Project support by MonkeyProof Solutions saves your organization time, costs and aggravation in the deployment of design automation tools. MonkeyProof Solutions coaches project teams and specialists for optimal set-up and daily use of MATLAB, Simulink and related tools. Engineers can fully concentrate on design- and engineering work rather than learning to deal with tools.

Project support is possible in all phases.

Jumpstart phase (at project start)

For an optimal tool choice, taking into account:

  • Budget and project size
  • Requirements
  • Disciplines involved
  • Project-deliverables and potential follow-up projects

Infrastructure, taking into account of:

  • Requirements management
  • Configuration management
  • Concurrent engineering
  • Reporting
  • Set-up of architecture (models/code)
  • Style guides (models/code)

Project support & coaching phase (during project)

  • Code/model reviews
  • Tips & tricks
  • Work-arounds and customizations
  • Adjustments of tool usage when project goals change
  • Workshops on specific topics