1. Overview

One of the most common sources of confusion in mechanical design is the difference between requirement, function, and structure.

Many design problems begin when these three concepts are mixed together. A customer’s request may be translated too quickly into a part shape. A machine layout may be decided before the required functions are properly defined. Or a specific mechanical structure may be treated as if it were the requirement itself.

Good mechanical design usually follows a clearer path:

Requirement → Function → Structure

Requirement → Function → Structure

Design is not simply the act of creating shapes.
It is the process of understanding what must be satisfied, defining what the machine or component must do, and then selecting a physical structure that can perform that function.

This article explains the difference between requirement, function, and structure in mechanical design, and how they should be connected in practical engineering decisions.

2. Definition

2.1 Requirement

A requirement is a condition that a machine, product, or component must satisfy.

Requirements usually come from customers, users, production processes, operating environments, regulations, cost targets, safety expectations, manufacturing limitations, or maintenance needs.

Examples of requirements include:

- The machine must process 500 kg of material per hour.
- The operator must be able to use the machine safely.
- The machine must be easy to clean.
- The installation space must be less than 1200 mm × 800 mm.
- Noise must remain below a defined level.
- A worn part must be replaceable within 10 minutes.
- The manufacturing cost must stay within the target budget

- The machine must process 500 kg of material per hour.
- The operator must be able to use the machine safely.
- The machine must be easy to clean.
- The installation space must be less than 1200 mm × 800 mm.
- Noise must remain below a defined level.
- A worn part must be replaceable within 10 minutes.
- The manufacturing cost must stay within the target budget

A requirement is the starting point of design.
However, a requirement is not yet a design solution.

A requirement tells us what must be satisfied.
It does not directly tell us how the machine should be built.

2.2 Function

A function is the role or action that a machine or component must perform in order to satisfy a requirement.

For example, if the requirement is:

The machine must process 500 kg of material per hour

The machine must process 500 kg of material per hour

This requirement may lead to several functions:

- Feed material into the machine.
- Convey material at a controlled rate.
- Cut, form, mix, or otherwise process the material.
- Discharge the processed material.
- Prevent clogging or accumulation.
- Protect the operator from hazardous motion

- Feed material into the machine.
- Convey material at a controlled rate.
- Cut, form, mix, or otherwise process the material.
- Discharge the processed material.
- Prevent clogging or accumulation.
- Protect the operator from hazardous motion

A function is not yet a specific shape or mechanism.

For example, the function “to convey material” can be realized by many different structures:

- Belt conveyor
- Screw feeder
- Chain conveyor
- Roller conveyor
- Vibratory feeder
- Pneumatic transfer system

- Belt conveyor
- Screw feeder
- Chain conveyor
- Roller conveyor
- Vibratory feeder
- Pneumatic transfer system

This means function sits between requirement and structure.

Requirement:
The material must be moved reliably from one point to another.

Function:
Move the material continuously and safely.

Structure:
Belt conveyor, screw feeder, roller conveyor, or another transfer mechanism

Requirement:
The material must be moved reliably from one point to another.

Function:
Move the material continuously and safely.

Structure:
Belt conveyor, screw feeder, roller conveyor, or another transfer mechanism

When functions are clearly defined, the designer is not forced into one structure too early.
Instead, multiple structural alternatives can be compared.

2.3 Structure

A structure is the physical arrangement used to perform a function.

Structure appears in the form of parts, assemblies, frames, shafts, bearings, covers, brackets, guides, actuators, sensors, fasteners, and machine layouts.

Examples of structures include:

- Belt conveyor assembly
- Screw feeding mechanism
- Circular blade cutting unit
- Hinged safety cover
- Welded machine frame
- Bolted service-access structure
- Linear guide and slide mechanism

- Belt conveyor assembly
- Screw feeding mechanism
- Circular blade cutting unit
- Hinged safety cover
- Welded machine frame
- Bolted service-access structure
- Linear guide and slide mechanism

Structure is the most visible outcome of design.
It is what appears in CAD models, drawings, parts lists, and manufacturing documents.

However, structure should not be decided before the requirement and function are understood.

If the designer starts by saying, “Let’s use a conveyor,” the design may become locked into one solution too early. The real requirement may simply be that material must be moved from one location to another. A conveyor is only one possible structure for achieving that function.

Therefore, structure should be selected after the requirement and function have been clarified.

3. Difference Between Requirement, Function, and Structure

The difference can be summarized as follows:

The simplest distinction is:

Requirement = condition
Function = role
Structure = implementation

Requirement = condition
Function = role
Structure = implementation

This distinction is important because unclear wording often leads to weak design decisions.

For example, the statement below is not a requirement:

A conveyor is required

A conveyor is required

A conveyor is not a requirement.
A conveyor is a structure.

A more accurate breakdown would be:

Requirement:
Material must be moved reliably from point A to point B.

Function:
Convey the material continuously.

Structure:
Use a belt conveyor

Requirement:
Material must be moved reliably from point A to point B.

Function:
Convey the material continuously.

Structure:
Use a belt conveyor

Once the problem is expressed this way, the designer can ask better questions:

Is a belt conveyor really the best option?
Would a screw feeder be more suitable?
Could a roller transfer be used?
Will the material slip, stick, scatter, or accumulate?
How will the structure affect cleaning, safety, and maintenance

Is a belt conveyor really the best option?
Would a screw feeder be more suitable?
Could a roller transfer be used?
Will the material slip, stick, scatter, or accumulate?
How will the structure affect cleaning, safety, and maintenance

Separating requirement, function, and structure is not just a matter of terminology.
It is a way to open the design space and compare better alternatives.

4. Why It Matters

Distinguishing requirement, function, and structure is essential in mechanical design for several reasons.

4.1 It Prevents Premature Structural Decisions

In practice, designers often move too quickly from a customer request to a physical structure.

For example, a customer may say:

We need a conveyor here

We need a conveyor here

The designer may immediately begin modeling a conveyor.

However, the customer may not actually need a conveyor.
The customer needs material to be transferred safely, reliably, and within the required cycle time.

The conveyor is only one possible structure.

By clarifying the requirement and function first, the designer can compare other solutions before committing to a structure.

4.2 It Makes Design Changes Easier to Trace

When a design changes, the reason for the change should be traceable.

For example, suppose the shape of a cover is changed.

The reason may be:

- To avoid interference
- To improve operator safety
- To improve cleanability
- To reduce manufacturing cost
- To make maintenance easier

- To avoid interference
- To improve operator safety
- To improve cleanability
- To reduce manufacturing cost
- To make maintenance easier

Each reason leads to a different design judgment.

A clear relationship between requirement, function, and structure makes the reason easier to explain.

Requirement:
The operator must not be able to access the hazardous area during operation.

Function:
Block access to the hazardous area.

Structure:
Use a hinged safety cover with an interlock switch

Requirement:
The operator must not be able to access the hazardous area during operation.

Function:
Block access to the hazardous area.

Structure:
Use a hinged safety cover with an interlock switch

When the design is documented this way, the structure is not just a shape.
It becomes a physical answer to a specific design requirement.

4.3 It Enables Alternative Comparison

When the function is clearly stated, multiple structures can be compared.

For example, if the function is:

Move material from one process to the next

Move material from one process to the next

Several structures may be possible:

- Belt conveyor
- Screw feeder
- Chain conveyor
- Roller conveyor
- Vibratory feeder
- Pneumatic transfer system

- Belt conveyor
- Screw feeder
- Chain conveyor
- Roller conveyor
- Vibratory feeder
- Pneumatic transfer system

Each structure has different strengths and limitations.

This comparison is only possible when the function is separated from the structure.

4.4 It Clarifies Design Intent

Good design is not only about the final shape.
It is also about why that shape was selected.

A drawing can show geometry, dimensions, and tolerances.
But it does not always explain the reasoning behind the design.

By connecting requirement, function, and structure, the designer can document the design intent more clearly.

Useful questions include:

What requirement created this structure?
What function does this structure perform?
Why was this structure selected instead of another option?
What trade-offs were accepted

What requirement created this structure?
What function does this structure perform?
Why was this structure selected instead of another option?
What trade-offs were accepted

When these questions can be answered, the design becomes easier to review, modify, explain, and defend.

5. Practical Example

Consider a simple machine that transfers a product from one position to another.

5.1 Requirement

The requirements may be:

- Move the product from position A to position B.
- Prevent damage to the product surface.
- Complete the transfer within 3 seconds.
- Allow easy cleaning and inspection.
- Keep the machine width below 800 mm

- Move the product from position A to position B.
- Prevent damage to the product surface.
- Complete the transfer within 3 seconds.
- Allow easy cleaning and inspection.
- Keep the machine width below 800 mm

At this stage, no structure has been selected.
The requirements only define what the design must satisfy.

5.2 Function

These requirements can be translated into functions:

- Support the product.
- Move the product.
- Maintain the product position.
- Prevent product damage.
- Stop the product at the target position.
- Provide access for cleaning and inspection

- Support the product.
- Move the product.
- Maintain the product position.
- Prevent product damage.
- Stop the product at the target position.
- Provide access for cleaning and inspection

At this stage, the designer should still avoid jumping directly to a belt, roller, robot, or slide mechanism.

The purpose is to clarify what the system must do.

5.3 Structure

Several structures may be considered:

Option A: Belt conveyor
Option B: Roller conveyor
Option C: Linear slide mechanism
Option D: Pick-and-place robot

Option A: Belt conveyor
Option B: Roller conveyor
Option C: Linear slide mechanism
Option D: Pick-and-place robot

Each structure satisfies the function in a different way.

The selected structure should be justified by the requirements and functions, not by habit or convenience alone.

6. Common Mistakes

6.1 Treating a Structure as a Requirement

Incorrect:

Requirement:
Use a conveyor

Requirement:
Use a conveyor

More accurate:

Requirement:
Move the product continuously from point A to point B.

Function:
Convey the product safely and reliably.

Structure:
Use a belt conveyor

Requirement:
Move the product continuously from point A to point B.

Function:
Convey the product safely and reliably.

Structure:
Use a belt conveyor

A conveyor is a structure, not a requirement.

6.2 Skipping the Function Stage

Weak design flow:

Customer request → Structure design → Drawing

Customer request → Structure design → Drawing

Better design flow:

Customer request → Requirement definition → Function definition → Structure alternatives → Drawing

Customer request → Requirement definition → Function definition → Structure alternatives → Drawing

When the function stage is skipped, the reason behind the selected structure becomes weak.

6.3 Assuming One Structure Equals One Function

One structure can perform multiple functions.
One function can also be performed by multiple structures.

For example, a cover may perform several functions:

- Block access to hazardous motion
- Prevent contamination
- Reduce noise
- Contain scattered material
- Improve appearance
- Control cleaning access

- Block access to hazardous motion
- Prevent contamination
- Reduce noise
- Contain scattered material
- Improve appearance
- Control cleaning access

Therefore, it is too narrow to say:

Cover = protection

Cover = protection

A cover is a structure.
The functions it performs depend on the design context.

6.4 Optimizing Before Requirements Are Clear

Optimization is not meaningful if the requirement is unclear.

For example, the request:

Make it stronger

Make it stronger

is not precise enough.

A better requirement should clarify:

- What is the maximum load?
- Is the load static, repeated, or impact-based?
- What deformation is acceptable?
- What is the target service life?
- What safety factor should be used

- What is the maximum load?
- Is the load static, repeated, or impact-based?
- What deformation is acceptable?
- What is the target service life?
- What safety factor should be used

The clearer the requirement, the more meaningful the function and structure become.

7. Decision Checklist

Use the following questions during design review.

7.1 Requirement Checklist

- What conditions must this design satisfy?
- Are customer requests separated from actual engineering requirements?
- Are measurable requirements expressed with numbers?
- Are safety, cost, space, maintenance, and manufacturing conditions included?
- Are there any conflicting requirements

- What conditions must this design satisfy?
- Are customer requests separated from actual engineering requirements?
- Are measurable requirements expressed with numbers?
- Are safety, cost, space, maintenance, and manufacturing conditions included?
- Are there any conflicting requirements

7.2 Function Checklist

- What roles must this machine or component perform?
- Is the function written as an action, not as a structure name?
- Are main functions and supporting functions separated?
- Is the sequence or flow of functions clear?
- Can the same function be achieved by another structure

- What roles must this machine or component perform?
- Is the function written as an action, not as a structure name?
- Are main functions and supporting functions separated?
- Is the sequence or flow of functions clear?
- Can the same function be achieved by another structure

7.3 Structure Checklist

- Does the selected structure satisfy the requirement and function?
- Were alternative structures compared?
- Were manufacturability, assembly, maintenance, safety, and cost reviewed?
- Can the reason for selecting this structure be explained?
- If the structure changes, which requirement or function will be affected

- Does the selected structure satisfy the requirement and function?
- Were alternative structures compared?
- Were manufacturability, assembly, maintenance, safety, and cost reviewed?
- Can the reason for selecting this structure be explained?
- If the structure changes, which requirement or function will be affected

8. Recommended Thinking Flow

A practical design flow can be written as follows:

1. Collect requirements.
2. Separate quantitative requirements from qualitative requirements.
3. Define the functions needed to satisfy the requirements.
4. Separate main functions from supporting functions.
5. Identify possible structures for each function.
6. Compare structural alternatives by manufacturability, assembly, cost, safety, reliability, and maintenance.
7. Record the reasoning behind the selected structure

1. Collect requirements.
2. Separate quantitative requirements from qualitative requirements.
3. Define the functions needed to satisfy the requirements.
4. Separate main functions from supporting functions.
5. Identify possible structures for each function.
6. Compare structural alternatives by manufacturability, assembly, cost, safety, reliability, and maintenance.
7. Record the reasoning behind the selected structure

Designers naturally imagine structures early.
That is not a problem.

The problem is when an early structure becomes fixed before the requirement and function are understood.

Before finalizing a structure, the designer should ask:

What requirement created this structure?
What function does this structure perform?
Is there another structure that can perform the same function better

What requirement created this structure?
What function does this structure perform?
Is there another structure that can perform the same function better

9. Related Knowledge

This topic connects to the following knowledge areas:

- Function Module in Mechanical Design
- Design Intent and Design Rationale
- One-piece vs Split-part Design
- Tolerance and Assembly Fit
- Accessibility for Assembly and Maintenance
- DFMA Checklist for Mechanical Systems

- Function Module in Mechanical Design
- Design Intent and Design Rationale
- One-piece vs Split-part Design
- Tolerance and Assembly Fit
- Accessibility for Assembly and Maintenance
- DFMA Checklist for Mechanical Systems

Understanding the difference between requirement, function, and structure makes other design topics easier to understand. Function modules, DFMA, tolerance design, maintenance access, and design review all become clearer when built on this foundation.

10. Summary

In mechanical design, requirement, function, and structure are different, but they are connected.

Requirement = What must be satisfied?
Function = What must it do?
Structure = How will it be implemented

Requirement = What must be satisfied?
Function = What must it do?
Structure = How will it be implemented

A requirement is the starting condition.
A function is the role needed to satisfy that condition.
A structure is the physical arrangement that performs the function.

When these three concepts are clearly separated, designers can compare better alternatives, trace the reason behind design changes, and explain design intent more clearly.

Good design does not start from shape alone.
Good design starts by understanding the requirement, defining the function, and selecting the structure that best delivers that function.