Engineer K Project Success Notification Flood Control System Functionality

O · Obligation Individual
http://proethica.org/ontology/case/4#Engineer_K_Project_Success_Notification_Flood_Control_System_Functionality
Properties
Instance of
ProjectSuccessNotificationObligation
http://proethica.org/ontology/intermediate#ProjectSuccessNotificationObligation
Case context
The BER noted that any non-functional design brings into play the obligation to advise a client or employer if a project will not be successful under Code section III.1.b, in the context of Engineer K's flood control system design.
Compliance status
unclear
Confidence
0.85
Importance
medium
Obligated party
Engineer K
Obligation statement
Engineer K was obligated to advise the City if the proposed flood control system design would not be successful — including not only structural and economic success but also safety outcomes for the public — consistent with NSPE Code III.1.b.
Temporal scope
Throughout design development and upon identification of any design deficiency that would render the system non-functional or unsafe
Source Evidence
Source text
Certainly, the system should be functional; any non-functional design brings into play the obligation to advise a client or employer if a project will not be successful under Code section III.1.b.

Text references
Certainly, the system should be functional; any non-functional design brings into play the obligation to advise a client or employer if a project will not be successful under Code section III.1.b.
TTL
@prefix case4: <http://proethica.org/ontology/case/4#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix proeth: <http://proethica.org/ontology/intermediate#> . @prefix proeth-core: <http://proethica.org/ontology/core#> . @prefix prov: <http://www.w3.org/ns/prov#> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . case4:Engineer_K_Project_Success_Notification_Flood_Control_System_Functionality a proeth:ProjectSuccessNotificationObligation, owl:NamedIndividual ; rdfs:label "Engineer K Project Success Notification Flood Control System Functionality" ; proeth-core:defeasibleUnder case4:City_Refusal_to_Mitigate_Underserved_Community_Risk ; proeth:casecontext "The BER noted that any non-functional design brings into play the obligation to advise a client or employer if a project will not be successful under Code section III.1.b, in the context of Engineer K's flood control system design." ; proeth:compliancestatus "unclear" ; proeth:conceptCategory "Obligation" ; proeth:confidence "0.85" ; proeth:derivedFromPrinciple case4:Public_Welfare_Paramount_Invoked_in_Flood_Control_System_Design ; proeth:discoveredincase "4" ; proeth:discoveredinpass "2" ; proeth:discoveredinsection "discussion" ; proeth:firstdiscoveredat "2026-02-24T14:37:31.489601+00:00" ; proeth:firstdiscoveredincase "4" ; proeth:generatedattime "2026-02-24T14:37:31.489601+00:00" ; proeth:importance "medium" ; proeth:obligatedparty "Engineer K" ; proeth:obligationclass "Project Success Notification Obligation" ; proeth:obligationstatement "Engineer K was obligated to advise the City if the proposed flood control system design would not be successful — including not only structural and economic success but also safety outcomes for the public — consistent with NSPE Code III.1.b." ; proeth:sourcetext "Certainly, the system should be functional; any non-functional design brings into play the obligation to advise a client or employer if a project will not be successful under Code section III.1.b." ; proeth:temporalscope "Throughout design development and upon identification of any design deficiency that would render the system non-functional or unsafe" ; proeth:textreferences "Certainly, the system should be functional; any non-functional design brings into play the obligation to advise a client or employer if a project will not be successful under Code section III.1.b." ; proeth:wasattributedto "Case 4 Extraction" ; prov:generatedAtTime "2026-02-24T14:47:31.438066"^^xsd:dateTime ; prov:wasGeneratedBy "ProEthica Case 4 Extraction" .
Metadata
Type
Individual
Last Updated
2026-05-28 16:25
Discovered in case
4
Discovered in pass
2
Discovered in section
discussion
First discovered
2026-02-24T14:37:31.489601+00:00
First case
4
Generated
2026-02-24T14:37:31.489601+00:00
Attributed to
Case 4 Extraction
Generated
2026-02-24T14:47:31.438066
Generated by
ProEthica Case 4 Extraction