13.14: Quick Check

Quick Check

1. State the primary ethical obligation of an engineer under the NCEES Model Rules.
2. A safety factor is reduced from 2.0 to 1.5 to save cost without additional analysis. Identify the ethical problems.
3. An engineer's model assumes linear elastic behavior but the material will yield in service. The assumption is not stated in the report. What is the ethical problem?
4. Apply the eight-step framework to: a manager asks you to approve a design by end of day; you have not had time to fully review it.
5. In the SolidWorks scenario: is there any version in which claiming current competence is ethically permissible? Explain.
6. What is the difference between meeting the letter of an NCEES rule and fulfilling the ethical obligation behind it? Use the rubber-stamping scenario.
7. In the Citicorp case, LeMessurier discovered the problem himself. Would the ethical calculus change if a subordinate had discovered it and brought it to him?
8. Explain how copying a homework calculation connects to the supervisory ethics scenario in §14.8.

Answer Examples - click to expand

1. Primary ethical obligation: An engineer's primary ethical obligation is to hold public health, safety, and welfare paramount. Client, employer, schedule, and cost pressures are important, but they do not override the engineer's duty to protect the public.
2. Safety factor reduction: Reducing a safety factor from 2.0 to 1.5 is not automatically unethical, but doing so only to save cost and without additional analysis is ethically problematic.

   The main concerns are that the engineer may be allowing cost to override safety, making an unsupported technical judgment, failing to document the basis for the change, and exposing users or the public to increased risk without justification. A reduced safety factor would need to be supported by calculations, testing, applicable standards, and professional review.

3. Unstated model assumption: The ethical problem is that the report is misleading. If the analysis assumes linear elastic behavior but the material will yield in service, then the model does not represent the actual operating condition.

   Failing to state that limitation prevents reviewers, clients, or decision-makers from understanding the risk. The ethical issue is not just a technical modeling error; it is incomplete and potentially deceptive communication.

4. Eight-step framework example:
   1. State the problem: A manager wants approval by the end of the day, but the design has not been fully reviewed.
   2. Identify stakeholders: The engineer, manager, employer, client, end users, maintenance personnel, and the public.
   3. Identify obligations: The engineer must protect public safety, be truthful about the review status, and work within their competence.
   4. Gather facts: Determine what has been reviewed, what remains unchecked, what failure modes are possible, and whether any codes or safety-critical requirements apply.
   5. Generate options: Refuse to approve, approve only the reviewed portions, request more time, escalate the concern, or issue a conditional status memo instead of approval.
   6. Evaluate consequences: Approving too early could create safety risk and professional liability. Delaying may affect schedule but preserves technical integrity.
   7. Choose and justify action: Do not approve the design as complete. Communicate that the review is incomplete and identify the remaining checks needed.
   8. Document and follow up: Send a written response documenting what was reviewed, what was not reviewed, and what is required before approval.
5. SolidWorks competence: Claiming current competence is ethically permissible only if the person can truthfully perform the required SolidWorks work at the expected professional level for that task.

   For example, it may be acceptable to say, “I have prior SolidWorks experience and can become current with review and practice before taking responsibility for production work.” It would not be acceptable to imply current professional competence if the person has not used the software recently and cannot yet complete the required tasks reliably.

6. Letter of the rule vs. ethical obligation: Meeting the letter of a rule means doing the minimum required by the written language. Fulfilling the ethical obligation means acting in the spirit of the rule: protecting the public, maintaining technical honesty, and taking responsibility for engineering judgment.

   In a rubber-stamping scenario, an engineer might try to claim they technically “reviewed” a document before signing it. But if the review was superficial and the engineer did not actually verify the work, then the ethical obligation has not been met. The issue is not just whether a signature was allowed; it is whether the engineer had sufficient knowledge and control to take responsibility for the design.

7. Citicorp subordinate scenario: The ethical calculus would not fundamentally change if a subordinate discovered the problem and brought it to LeMessurier. Once the issue was known, the obligation to investigate, disclose, and correct the risk would still exist.

   However, the situation would add supervisory responsibility. A senior engineer would need to take the subordinate's concern seriously, verify the analysis, protect the subordinate from retaliation, and ensure the concern reached the appropriate decision-makers. Ignoring or suppressing the subordinate's finding would make the ethical failure worse.

8. Homework copying and supervisory ethics: Copying a homework calculation trains the same bad habit that causes supervisory ethics failures: accepting work without understanding or verifying it.

   In school, copying may seem like a shortcut. In professional practice, relying on someone else's calculation without checking it can become rubber-stamping. Engineers are responsible for the work they submit, approve, or sign. The habit of verifying assumptions, units, methods, and results begins with student work.