Prototypes vs. Routine Engineering

By Adria Jesus and Elaine Silva, from the R&D (Research, Development & Innovation) Department.

The Informatics Law, regulated by Decree No. 10.521/2020, aims to promote technological and industrial development in the Western Amazon region and in the State of Amapá.

One of its main objectives is to provide tax incentives and support for innovation in the fields of information and communication technology (ICT). In this context, the concept of process prototypes plays a strategic role, particularly regarding the development of new products and the improvement of processes.

It is essential to distinguish between process prototypes and routine engineering, as both perform distinct functions within a company’s innovation and improvement strategies.

Process Prototype or Routine Engineering?

Although both process prototypes and routine engineering involve improving and optimizing operations, their methods, objectives, and applications are very different. Thus, there are fundamental differences between Process Prototypes and Routine Engineering.

Process prototypes fall under experimental development, serving as initial or experimental models of new production or operational processes.

Under the Informatics Law, these prototypes may include testing new production methods, integrating innovative technologies, or implementing significant changes in how a company uses its resources.

In contrast, routine engineering seeks to optimize and maintain already established processes. These are continuous and stable activities, associated with managing existing or customized processes, with the goal of ensuring operational efficiency and reducing costs within established standards.

The main difference between process prototypes and routine engineering lies in the level of innovation and the purpose of the activities.

Process Prototypes:

• Significant innovations (new technologies, new business models, or new methodologies).

• Testing of new technologies.

• Higher risk (radical or experimental changes).

  
  

Routine Engineering:

• Aims at stability — maintaining existing processes.

• Focused on efficiency and gradual improvement without introducing new concepts.

• Does not involve technological challenges.

  
  

Some Tips for the R&D Team!

To ensure full compliance with current legislation:

Software, Systems, or Hardware Development

Projects may aim to improve existing products or processes, as long as they demonstrate technological challenges and scientific complexity.

Rigorous Documentation

It is essential to document every stage of prototype development, clearly recording technical uncertainties, tests performed, and results obtained.

Define Clear Objectives

Set consistent and measurable goals that demonstrate the problem or technical challenge the project intends to solve.

Focus on Proof of Concept

Ensure that prototype development addresses significant technical problems and challenges, with a clear focus on innovation and industrial transformation.

These practices help ensure that R&D projects are fully aligned with the Informatics Law and the tax incentive requirements of the Manaus Free Trade Zone (ZFM).