Tags: NSPE ethics, confidentiality engineering, competitor proposal access, autonomous vehicle ethics, driverless car ethics, trolley problem engineering, Case 16-12, Case 16-5, ENGR 216, public health safety welfare, engineering risk assessment
These two NSPE cases address confidentiality obligations and the engineer's paramount duty to protect public health, safety, and welfare. Case 16-12 examines what an engineer must do when a subconsultant obtains a competitor's confidential proposal. Case 16-5 tackles the ethical dimensions of programming autonomous vehicle crash algorithms, including who the system should protect when harm is unavoidable.
Confidentiality obligation
The duty under the NSPE Code (Section III.4) to avoid disclosing confidential information concerning the business affairs or technical processes of any present or former client or employer without consent.
Subconsultant
A firm engaged by the primary engineering firm to contribute specialised work to a larger project. In Case 16-12, Firm Y is a subconsultant to Firm X.
Proprietary proposal information
Design concepts, pricing, methodology, and strategic approaches contained in an engineering proposal. Treated as confidential intellectual property of the firm that prepared it.
Unfair competitive advantage
A benefit gained through access to a competitor's confidential information rather than through independent merit. Using a competitor's proposal to refine your own is a textbook example.
Public health, safety, and welfare (paramount obligation)
NSPE Fundamental Canon I: engineers shall hold paramount the safety, health, and welfare of the public. This is the overriding principle in the Code and takes precedence over other obligations.
Risk assessment team
A group of engineers assigned to identify, evaluate, and recommend responses to potential hazards. In Case 16-5, this team is evaluating crash scenarios for autonomous vehicles.
Trolley problem (applied engineering variant)
The classic ethical dilemma applied to autonomous vehicle programming: when a crash is unavoidable, should the system prioritise passenger safety, minimise total harm, or follow some other logic? Not an NSPE term, but widely used in discussion of Case 16-5.
Utilitarian approach (least total harm)
An ethical framework that seeks the outcome producing the least overall harm across all affected parties. One of the options being considered in Case 16-5.
Passenger-priority approach
An alternative framework where the vehicle's system always acts to protect its own occupants first, even if that causes greater harm to others.
The setup
Engineer A is the principal owner of Firm X.
Firm X is preparing an engineering proposal for a private project for Client M.
The proposal involves preliminary design information and subproposals from team members, including subconsultant Firm Y.
One day before Firm X's presentation to Client M, Firm Y tells Engineer A that it has obtained (through a third party) a copy of a competing proposal, prepared and presented by Firm Z for the same project.
Engineer A and Firm X are presenting their proposal to Client M the following day.
The ethical question
What are Engineer A's ethical obligations under these circumstances?
Relevant NSPE Code provisions
Section I.5 (Fundamental Canon): Engineers shall avoid deceptive acts.
Section II.5: Engineers shall not promote their own interest at the expense of the dignity and integrity of the profession.
Section III.4: Engineers shall not disclose confidential information without consent.
Section III.9: Engineers shall give credit for engineering work to those to whom credit is due.
Section III.10: Engineers shall not engage in conduct involving fraud, deceit, or misrepresentation.
Core reasoning points for exam discussion
Engineer A must not review the competitor's proposal. Even though Firm Y obtained it (not Engineer A directly), using it would constitute gaining an unfair competitive advantage through confidential information.
The ethical obligation applies regardless of how the proposal was obtained. The fact that a "third party" leaked it does not make it fair game.
Engineer A should instruct Firm Y to return or destroy the document and not share its contents with anyone on the Firm X team.
Engineer A has an obligation to proceed with the presentation to Client M based solely on Firm X's independent work.
There is a secondary question about whether Engineer A should inform Client M or Firm Z about the breach. The NSPE Code's provisions on avoiding deceptive acts and upholding the dignity of the profession suggest disclosure may be warranted, though the primary obligation is to refuse to use the information.
If Firm Y has already shared the contents with Engineer A or others on the team, the situation becomes more complex. Engineer A must still refuse to incorporate any of that knowledge and should document the steps taken to quarantine the information.
Key takeaway
The temptation to "just take a look" is the exam trap. The ethical answer is clear: do not review, do not use, and take affirmative steps to prevent contamination of your own proposal.
The setup
Engineer A is a PE working as a consultant to an automobile manufacturer developing a driverless/autonomous vehicle operating system.
Engineer A sits on an engineering risk assessment team evaluating potential hazard scenarios.
The team is considering this scenario: in an unavoidable crash, should the vehicle's software:
(a) Choose the outcome safest for the vehicle's passengers, or
(b) Choose the outcome that causes the least total harm to anyone involved (which might mean steering into a stationary object, causing serious but non-fatal injuries to passengers, rather than striking and potentially killing a pedestrian, cyclist, or motorcyclist)?
The ethical question
What are Engineer A's ethical obligations?
Relevant NSPE Code provisions
Section I.1 (Fundamental Canon): Engineers shall hold paramount the safety, health, and welfare of the public.
Section II.1: Engineers shall undertake services only in areas of their competence.
Section II.2: Engineers shall perform services only when satisfied that the services are accomplished with due care.
Section III.2.a: Engineers shall seek opportunities to participate in civic affairs and work for the advancement of the safety, health, and well-being of their community.
Core reasoning points for exam discussion
The paramount obligation (Canon I.1) is to the public, not to the product's buyer. This is the single most important point in the analysis. The NSPE Code does not permit engineers to prioritise one group's safety over another solely because that group is the customer.
The utilitarian approach (least total harm) aligns more closely with the public welfare mandate than the passenger-priority approach, because it treats all human life as worthy of protection rather than privileging the vehicle's occupants.
However, the problem is not straightforward:
A pure utilitarian algorithm requires the system to make split-second judgements about the relative severity of outcomes, which involves uncertainty and probability.
There is a question of whether consumers will purchase vehicles that may sacrifice their safety for others, and whether manufacturers can be transparent about this.
Regulatory frameworks may not yet exist to guide these decisions.
Engineer A's obligations include:
Raising the public safety dimension clearly within the risk assessment team.
Advocating for the approach that best protects public welfare, even if it creates commercial tension with the manufacturer.
Ensuring the team's analysis is thorough, documented, and considers edge cases.
If the manufacturer overrides the team's recommendation in a way that compromises public safety, Engineer A may have a duty to escalate or, in extreme cases, withdraw from the project (Section II.1.d).
This case connects directly to broader conversations about algorithmic ethics, AI decision-making, and the engineer's responsibility when designing systems that make life-and-death choices autonomously.
⚠️ Case 16-12 is a "what would you do" scenario that tests integrity under pressure. The night-before timing is deliberate: it maximises temptation. Expect exam questions that test whether you recognise the obligation to refuse the information entirely, not merely to "use it carefully."
⚠️ In Case 16-12, the subconsultant (Firm Y) is the one who obtained the proposal, but the ethical obligation falls on Engineer A as the principal. You cannot delegate away ethical responsibility.
⚠️ Case 16-5 is one of the most discussed modern engineering ethics scenarios. The NSPE's paramount obligation to the public is the anchor of the analysis. If you remember one thing: the engineer serves the public first, the client second.
⚠️ A common exam mistake in Case 16-5 is treating the trolley problem as unsolvable and therefore not the engineer's responsibility. The NSPE Code requires the engineer to engage with the problem and advocate for public safety, even when no perfect answer exists.
⚠️ Both cases test the relationship between legal exposure and ethical obligation. Something can be legally ambiguous and ethically clear, or vice versa.
Q: In Case 16-12, Engineer A did not personally obtain the competitor's proposal. Does this relieve Engineer A of ethical responsibility?
A: No. The NSPE Code's obligations apply to Engineer A regardless of who obtained the confidential document. As the principal of Firm X, Engineer A has a duty to ensure the proposal is not reviewed or used by anyone on the team, and to take corrective action such as instructing Firm Y to return or destroy it.
Q: What should Engineer A do if Firm Y has already summarised the key points of Firm Z's proposal verbally?
A: Engineer A should still refuse to incorporate any of that information into Firm X's proposal. The presentation to Client M should proceed based entirely on Firm X's independent work. Engineer A should document what happened and consider whether disclosure to Client M or Firm Z is warranted under the circumstances.
Q: In Case 16-5, which approach to the crash algorithm is most consistent with the NSPE Code, and why?
A: The least-total-harm (utilitarian) approach is more consistent with the NSPE Code because Canon I.1 requires engineers to hold paramount the safety, health, and welfare of the public as a whole, not just the vehicle's occupants. Prioritising passengers over bystanders would privilege the customer's safety at the expense of the broader public.
Q: What obligation does Engineer A have if the automobile manufacturer decides to programme the vehicle to always protect its passengers first?
A: Engineer A should formally raise objections through the risk assessment team and document the concern. If the manufacturer persists with an approach that Engineer A believes compromises public safety, Engineer A may need to escalate to higher management, regulatory authorities, or, as a last resort, withdraw from the project. The NSPE Code does not require engineers to remain silent when their professional judgement on public safety is overridden.
Q: Why is Case 16-5 considered more complex than a standard application of the "paramount obligation" principle?
A: Because the scenario involves probabilistic outcomes (no certainty about who will be harmed or how severely), because the decision is made by an algorithm rather than a human in the moment, because consumer acceptance and commercial viability are real factors, and because regulatory frameworks for autonomous vehicles are still developing. The ethical principle is clear; its application requires careful engineering judgement.
NSPE confidentiality, competitor proposal ethics, unfair competitive advantage engineering, autonomous vehicle ethics, driverless car trolley problem, NSPE Canon I paramount obligation, public health safety welfare, engineering risk assessment, algorithmic ethics, AI decision-making engineering, Case 16-12, Case 16-5, ENGR 216 ethics, engineering proposal confidentiality, subconsultant ethical duty, Texas A&M ENGR 216