The Engineering Problem Solving Framework

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

This framework is not just for getting the right answer; it is fundamentally about communication. An engineering calculation must be completely transparent so that any other 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 steps:

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 sketch showing dimensions and forces. A diagram grounds the abstract numbers in physical reality.

3. Given (Known Information)

An explicit list of all the information provided or known before the calculation begins.

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

4. Find (The Unknowns)

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

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

5. Assumptions

This is arguably the most critical and uniquely "engineering" step of the framework. Real-world problems are too complex to model perfectly. Engineers must make simplifying assumptions to make the math solvable.

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

6. Equations / Governing Principles

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

This allows a reviewing engineer (a checker) to instantly verify that the correct theory is being applied, even before checking the arithmetic.

7. Substitution and Solution

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

The calculation is worked out step-by-step.
Units must be carried through the calculation (Dimensional Analysis) to ensure the final answer has the correct physical meaning.

8. Conclusion / Final Answer

The final result is stated clearly, usually double-underlined or placed in a summary box, complete with correct units and rounded to an appropriate number of significant figures. A brief sentence explaining the engineering implication of the result is often included (e.g., "The calculated stress is 150 MPa, which is less than the allowable 200 MPa; therefore, the design is safe.").