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 beginning is half the battle.

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, at the start, set up our models such that in subsequent phases a minimum of re-design needed?
• How can I work simultaneously with multiple people / teams on a design?
• What are reporting options?
• How can legacy code / ip effectively be reused?

During projects with an innovative character is not uncommon for specifications for the project to change. This may result in a (partial) abandoning of the elected methodology. It also may happen that one runs into limits (in terms of computing power, or functionality, features) of design tools in use. For engineers it is very time-consuming to seek work-arounds or alternative approaches themselves.
So:

• How can project engineers optimally focus on their added value activities?
• How do project engineers get the most from the tools they use without spending more time than strictly necessary on the tools themselves?
• How do you change the approach, when project objectives change, as quickly as possible without having to pay an unnecessary price later on in the project in the form of extra work or reduced flexibility?

To effectively deploy design automation tools requires specialist and up-to-date knowledge. MonkeyProof Solutions has this knowledge and experience and can help your organization in preparatory phase and during projects in the form of Project Support.

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. They can fully concentrate on their design and engineering work rather than learning to deal with tools. So, decisions on the usage of design tools are well founded. Moreover, a very time efficient and targeted transfer of knowledge happens which is preserved for future projects.

Project support is possible in all phases. Below an overview

Jumpstart (at project start)

• Optimal tool choice, taking into account:
  • Budget and project size
  • Requirements
  • Disciplines involved
  • Project deliverables and potential follow-up projects
• Infrastructure, taking into account:
  • Requirements management
  • Configuration management
  • Concurrent engineering
  • Reporting
• Set-up of architecture (models/code)
• Style guides (models/code)
• Workshops on specific topics

Project support & Coaching (during project)

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