3. Provide evidence to support your claims
Engineers are data-driven creatures. You must be able to support your assertions regarding impacts to the organization with concrete facts. Include that evidence even as you expound upon the situation’s criticality.
For a detailed example, consider the following:
“According to internal efficiency tracking statistics, the present loading procedure wastes an average of 4 minutes per part, amounting to 20 lost man-hours daily for the company. Because operators are paid $20 each hour on average, that works out to wastage of $400 daily or $146,000 annually.”
Always ensure the data in your problem statement comports with that in the bulk of your paper.
4. Recommend a solution
After you have outlined the issue and the reasons it is so essential, move on to ways you plan to solve it. The solution, like the introductory description of your problem, must be expressed simply and succinctly.
Focus on the large, crucial, tangible ideas and save the minutia for afterward. Your white paper will have plenty of space for the solution’s more minor details.
Using our ABC Company problem statement example, we can look at a high-level overview of the upgraded process without going into too much detail.
“Line C could minimize that wasted time by employing an automated loading machine which helps operators automatically load raw materials onto the conveyor efficiently.”
You can then outline the general concept of your proposed approach. Note, however, that this should constitute only a line or two of the problem statement. The real analysis will be in the body of the engineering white paper.