Invention Factory Blue Print:
Perfect Invention FAQ

What are the basic principles of technical system evolution?

Technical systems evolve towards increased ideality.
Ideality is defined as the ratio of benefits to costs and harm. This means that systems tend to evolve in a way that increases benefits, decreases costs, and decreases harm.
The evolution of a technical system can be divided into three stages:

Parameter optimization: In this stage, the principle of operation and structure of the system remain constant, while the parameters are improved to reach a global extremum.
Structural optimization: Once parameter optimization reaches its limit, the system evolves towards a more rational structure while maintaining the same principle of operation. This process continues until the structure is optimized to a global extremum.
Principle of operation optimization: Finally, the system transitions to a more rational principle of operation. This process continues until the most rational principle of operation is achieved.

How do you formulate a challenge for the synthesis of new technical solutions?

Define basic needs: Identify the needs related to the methods, technical solutions, and fabrication ways within a specific field of implementation.
Gather information: Research the current state of the field, including existing methods, materials, and technical devices.
Formulate and evaluate contradictions: Identify the contradictions between the identified needs and the available means to satisfy them.

How do you objectively formulate a synthesis of new technical solutions?

A well-defined objective for synthesizing new technical solutions includes requirements for the product or system and a set of functions that fulfill those requirements. These requirements can be categorized as source requirements (from customers or stakeholders), mission or business requirements (operational context), and system/subsystem requirements (system capabilities).

Ambiguity in requirement definitions can lead to errors, increasing costs with each development stage. To ensure clarity, ask questions like "Why?", "What?", "How?", and "Who?".

How do you analyze the objectives of a technical solution?

The main function of a technical solution can be broken down into auxiliary sub-functions. There are two types of sub-functions: those ensuring the system's existence (e.g., connectivity, structural integrity, power supply) and those achieving specific goals (e.g., energy transformation, regulation, information processing).

Analyzing these functions involves:

Dividing the main function into auxiliary functions that meet the required conditions.
Breaking down each auxiliary function into partial functions.
Representing the function structure graphically.
Simplifying the function structure by removing unnecessary or unsubstantiated functions.

Do you know what strategies can be used in the quest for technical solutions?

Develop a morphological map: This table outlines various options for implementing each function within the technical system.
Examine each function independently: Identify diverse ways to execute each function. Methodologies such as TRIZ and the De Bono method can be helpful in this process.

What resources would you like to help in the quest for technical solutions?

Several resources can assist in the search for technical solutions:

TRIZ: The Theory of Inventive Problem Solving (TRIZ) offers a set of tools and principles for problem-solving and innovation.
Lateral Thinking: Developed by Edward de Bono, this method encourages exploring alternative approaches and unconventional solutions.
Software packages: Companies like Ideation International and Invention Machine offer specialized software for TRIZ implementation.
Books and publications: Many books delve into TRIZ methodology, lateral thinking, and other problem-solving techniques.

How do you analyze technical solutions?

List mandatory requirements: Define the essential requirements for each partial function's successful execution.
Eliminate unsuitable solutions: Remove any partial solutions from the morphological map that fail to meet the mandatory requirements.
Check compatibility: Use a matrix to assess the compatibility of the remaining partial solutions.
List compatible combinations: Document all viable combinations of partial solutions.

How do you select the best technical solution?

List auxiliary requirements: Identify the non-mandatory requirements for the technical system's overall performance.
Prioritize and weight requirements: Rank the auxiliary requirements by importance and assign a weight to each.
Evaluate solutions: Use a solution matrix to assess how well each technical solution fulfills the auxiliary requirements, using a scale of 0 to 10.
Calculate the selection criterion: Multiply each compliance value by its corresponding weight and sum the results for each solution. The solution with the highest total score represents the best option.

Invention Factory Blue Print: Perfect Invention FAQ