Warning: Could not retrieve entity triples or related cases: (psycopg2.errors.UndefinedColumn) column entity_triples.subject_label does not exist
LINE 1: ...al, entity_triples.graph AS entity_triples_graph, entity_tri...
^
[SQL: SELECT entity_triples.id AS entity_triples_id, entity_triples.subject AS entity_triples_subject, entity_triples.predicate AS entity_triples_predicate, entity_triples.object_literal AS entity_triples_object_literal, entity_triples.object_uri AS entity_triples_object_uri, entity_triples.is_literal AS entity_triples_is_literal, entity_triples.graph AS entity_triples_graph, entity_triples.subject_label AS entity_triples_subject_label, entity_triples.predicate_label AS entity_triples_predicate_label, entity_triples.object_label AS entity_triples_object_label, entity_triples.subject_embedding AS entity_triples_subject_embedding, entity_triples.predicate_embedding AS entity_triples_predicate_embedding, entity_triples.object_embedding AS entity_triples_object_embedding, entity_triples.triple_metadata AS entity_triples_triple_metadata, entity_triples.created_at AS entity_triples_created_at, entity_triples.updated_at AS entity_triples_updated_at, entity_triples.temporal_region_type AS entity_triples_temporal_region_type, entity_triples.temporal_start AS entity_triples_temporal_start, entity_triples.temporal_end AS entity_triples_temporal_end, entity_triples.temporal_relation_type AS entity_triples_temporal_relation_type, entity_triples.temporal_relation_to AS entity_triples_temporal_relation_to, entity_triples.temporal_granularity AS entity_triples_temporal_granularity, entity_triples.temporal_confidence AS entity_triples_temporal_confidence, entity_triples.temporal_context AS entity_triples_temporal_context, entity_triples.timeline_order AS entity_triples_timeline_order, entity_triples.timeline_group AS entity_triples_timeline_group, entity_triples.original_llm_type AS entity_triples_original_llm_type, entity_triples.type_mapping_confidence AS entity_triples_type_mapping_confidence, entity_triples.needs_type_review AS entity_triples_needs_type_review, entity_triples.mapping_justification AS entity_triples_mapping_justification, entity_triples.entity_type AS entity_triples_entity_type, entity_triples.entity_id AS entity_triples_entity_id, entity_triples.world_id AS entity_triples_world_id, entity_triples.scenario_id AS entity_triples_scenario_id, entity_triples.character_id AS entity_triples_character_id, entity_triples.guideline_id AS entity_triples_guideline_id
FROM entity_triples
WHERE entity_triples.subject = %(subject_1)s AND entity_triples.entity_type = %(entity_type_1)s]
[parameters: {'subject_1': 'http://proethica.org/cases/138', 'entity_type_1': 'document'}]
(Background on this error at: https://sqlalche.me/e/20/f405)
NSPE Ethics Case: Conflict Interest Designbuild Project
Case Details
World: Engineering
Description
Engineer D is the Engineer of Record (EOR) as part of a design-build team led by Contractor W. Under the terms of an Agency funding grant, the project is required to have an independent peer review of the design, the design approach, compatibility with the site, and a constructability assessment related to the design approach. Engineer D prepares the design and drawings and directly hires Engineer F to perform the peer review.
The contractual relationships and roles of the many parties illustrate how a conflict of interest can go unnoticed. In this case, an independent peer review of the design was required by the Agency and the peer reviewer was in a direct contractual relationship with the EOR. Two reputable engineers can and often do disagree and they can both be right. A key question the peer reviewer needs to answer is whether the EOR did it wrong or just a different, but still acceptable, way.
In BER Case 91-2, the Client hired Engineer B to perform a review of Engineer A’s work. The Client determined that there were errors/omissions in Engineer A’s work. Engineer B’s fee is dependent on the ultimate court judgement or settlement made with Engineer A in contemplation of a suit for breach of contract. The BER concluded that Engineer B is being placed in a position of identifying errors/omissions in Engineer A’s work in order to pressure Engineer A into a settlement which would result in a fee for Engineer B. The nature of the services and the related contingency arrangement suggest a strong possibility that the engineer’s judgement could be compromised or at the very least create the appearance of being compromised.
Peer reviews are common on complicated engineering projects. The “independent” requirement in this case must withstand the scrutiny of a conflict of interest.
What does it mean to perform an independent peer review of engineering work? NSPE Position Statement No. 10-178 (Peer Review Legislation) recommends that “…peer reviewer must not be an employee, coworker, partner or subconsultant of the professional engineer whose design is being peer reviewed.”
In order to avoid any perception of a conflict of interest, an independent peer reviewer needs to be contracted directly by and compensated by the project owner (Client) and not the EOR. In the case of Design-Build teams, the lead party could potentially hire both the EOR and the peer reviewer, as long as they are different firms. A peer review performed by another office of the EOR or a subconsultant to the EOR does not meet the requirement of being independent and squarely has a conflict of interest.
In the present case, the EOR hired the peer review firm, putting the peer review firm in a similarly conflicted position of potentially disagreeing the EOR and possibly not getting compensated if their conclusions result in significant changes to the EOR’s design. The peer review engineer must be free to provide objective, unbiased professional judgements to serve the best interests of their client and not compromise integrity in pursuit of a professional fee. Contractor W should have retained Engineer F (or other engineer of Contractor W’s choice) to assure the independence of Engineer F’s review.
Engineers shall hold paramount the safety, health, and welfare of the public.
If engineers' judgment is overruled under circumstances that endanger life or property, they shall notify their employer or client and such other authority as may be appropriate.
Engineers shall undertake assignments only when qualified by education or experience in the specific technical fields involved.
Engineers shall act for each employer or client as faithful agents or trustees.
Engineers shall disclose all known or potential conflicts of interest that could influence or appear to influence their judgment or the quality of their services.
Engineers shall advise their clients or employers when they believe a project will not be successful.
On its face, the peer review was not independent, as required by the agency. Therefore, it would not be ethical for Engineer D to hire and enter into a direct contractual relationship with Engineer F to perform the peer review.
Generate Interactive Scenario
Checking...
Loading...
RDF Triple Metadata
Triples
Subject | Predicate | Object |
---|---|---|
Case:138 | rdf:type | ENG_ETHICS:EthicsCase |
Case:138 | dc:title | NSPE Ethics Case: Conflict Interest Designbuild Project |
Case:138 | belongsTo | World:1 |
World:1 | dc:title | Engineering |
Case:138 | involves:EthicalPrinciple | ENG_ETHICS:PublicSafety |
Case:138 | involves:EthicalPrinciple | ENG_ETHICS:Confidentiality |
Case:138 | involves:EthicalPrinciple | ENG_ETHICS:ConflictOfInterest |
Case:138 | involves:EthicalPrinciple | ENG_ETHICS:Competence |
Case:138 | hasConflict | ENG_ETHICS:ConfidentialityVsSafety |
Case:138 | references:Code | NSPE:CodeI.1 |
Case:138 | references:Code | NSPE:CodeII.1 |
Case:138 | references:Code | NSPE:CodeIII.4 |
Case:138 | hasDecision | Decision:Ethical |
Namespaces
Prefix | URI |
---|---|
dc |
http://purl.org/dc/elements/1.1/ |
bfo |
http://purl.obolibrary.org/obo/ |
eth |
http://proethica.org/ethics/ |
owl |
http://www.w3.org/2002/07/owl# |
rdf |
http://www.w3.org/1999/02/22-rdf-syntax-ns# |
Case |
http://proethica.org/case/ |
NSPE |
http://proethica.org/code/nspe/ |
rdfs |
http://www.w3.org/2000/01/rdf-schema# |
time |
http://www.w3.org/2006/time# |
World |
http://proethica.org/world/ |
Decision |
http://proethica.org/decision/ |
involves |
http://proethica.org/relation/ |
belongsTo |
http://proethica.org/relation/ |
ENG_ETHICS |
http://proethica.org/eng_ethics/ |
references |
http://proethica.org/relation/ |