The Engineering Problem Solving Framework

Engineering differs from pure mathematics because it deals with real-world complexities, uncertainties, and physical constraints. When designing a bridge or sizing a chemical plant, the consequences of a calculation error can be catastrophic. Therefore, engineers rely on highly structured, formalized problem-solving frameworks.

The framework isn't just about getting the right answer; it is fundamentally about communication. An engineering calculation must be completely transparent so that another competent engineer can pick up the document, understand exactly what was done, trace every number back to its source, and verify the conclusion.

The Standard Calculation Format

While different organizations may use slightly different templates, the universally accepted framework for an engineering calculation consists of the following logical progression:

1. Problem Statement / Objective

A concise statement of what is being solved. Example: "Determine the maximum allowable pressure for the main steam pipe."

2. Diagram / Sketch

A visual representation of the problem. This could be a Free Body Diagram (FBD), a circuit schematic, or a simple dimensional sketch. A diagram grounds abstract numbers into physical reality.

3. Given / Known Information

An explicit list of all data provided or known before starting the calculation.

This includes physical dimensions, material properties, flow rates, or environmental conditions.
Every "Given" value must have its proper units attached.
In professional practice, the source of the "Given" data should be referenced (e.g., "Yield Strength from ASME B31.3 Table A-1").

4. Find / The Unknowns

A clear list of the specific variables or values this calculation intends to discover.

Example: "Find: 1) Minimum required wall thickness, 2) Total pipe weight."

5. Assumptions

This is perhaps the most critical and uniquely "engineering" step in the framework. Real-world problems are too complex to model perfectly. Engineers must make assumptions to simplify the problem so mathematical equations can be solved.

Examples: "Assume fluid is incompressible," "Assume friction in the pulley is negligible," or "Assume material behaves perfectly elastically."
Why this matters: If a calculation fails or is questioned years later, the assumptions section tells other engineers exactly why a method was chosen. If an assumption is later proven false, it is immediately obvious that the calculation must be redone.

6. Equations / Governing Principles

Before writing any numbers down, the engineer must write out the raw algebraic formulas, governing equations, or theoretical principles that will be used.

This allows a checker to immediately verify if the correct physics are being applied, before getting bogged down in arithmetic.

7. Substitution and Solution

Only at this stage are the numbers from the "Given" section plugged into the "Equations."

The arithmetic is carried out step-by-step.
Units must always be carried through the calculation (Dimensional Analysis) to ensure the final answer makes physical sense.

8. Conclusion / Final Answer

The final answer is clearly stated, usually double-underlined or boxed, with correct units, rounded to appropriate significant figures. A short sentence explaining the engineering meaning of the result is often included (e.g., "Calculated stress is 150 MPa, which is less than the allowable 200 MPa; therefore, the design is safe.").