Overview
Facts Discussion
Provenance Draft

PASS 1: Contextual Framework Facts Section

Case 71: Failure To Include Information In Engineering Report

R Roles
3
Classes
4
Individuals
S States
5
Classes
9
Individuals
Rs Resources
5
Classes
4
Individuals

Extracted Ontology Entities

30 RDF entities extracted organized by concept type

R Roles

Roles Classes
3
changed
Litigation Expert Engineer
rdfs:subClassOf Roles
New C71
Definition
Extracted from facts primary
A licensed professional engineering role in which the practitioner is retained by one party in a legal or mediation proceeding to conduct independent technical investigations, prepare findings reports, and provide expert testimony or written opinions on engineering matters in dispute, bearing professional obligations of objectivity, completeness, and honest disclosure of all material facts including those that may be unfavorable to the retaining party.
Properties
Text References:
"the municipality retained Engineer B to supervise the driving of several test piles"
"Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations"
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"Engineer B did not report that the dynamic test equipment had failed"
Confidence: 0.88
Role Category: provider_client
[facts] "the municipality retained Engineer B to supervise the driving of several test piles"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: the municipality retained Engineer B to supervise the driving of several test piles; Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations; Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; Engineer B did not report that the dynamic test equipment had failed
  • roleCategory content: provider_client
  • confidence assessment: 0.88
changed
New C71
Definition
Extracted from facts primary
A licensed professional engineering role in which the practitioner is retained by a municipality to design infrastructure elements such as docks, foundations, or similar civil works, bearing primary professional accountability for the technical adequacy of the design and the accuracy of supporting engineering judgments.
Properties
Text References:
"Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles"
Confidence: 0.85
Role Category: provider_client
[facts] "Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles
  • roleCategory content: provider_client
  • confidence assessment: 0.85
changed
Independent Geotechnical Observer
rdfs:subClassOf Roles
New C71
Definition
Extracted from facts primary
A professional engineering or geotechnical consulting role in which the practitioner is retained by one party to observe and monitor testing or construction activities conducted by another party, report on procedural irregularities or equipment failures, and provide independent technical testimony on the validity of test conditions and results.
Properties
Text References:
"An independent geotechnical consultant was retained by Engineer A to observe the test"
"The geotechnical consultant testified and showed that dynamic test equipment had failed during the test"
"In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value"
Confidence: 0.82
Role Category: provider_client
[facts] "An independent geotechnical consultant was retained by Engineer A to observe the test"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: An independent geotechnical consultant was retained by Engineer A to observe the test; The geotechnical consultant testified and showed that dynamic test equipment had failed during the test; In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value
  • roleCategory content: provider_client
  • confidence assessment: 0.82
Roles Individuals
4
Engineer B Litigation Expert
LitigationExpertEngineer
New C71
Text References:
"the municipality retained Engineer B to supervise the driving of several test piles"
"Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations"
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"Engineer B did not report that the dynamic test equipment had failed"
"At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A"
Confidence: 0.91
Actor: Engineer B
Role Class: Litigation Expert Engineer
Role Category: provider_client
Case Involvement: Retained by the municipality to supervise test pile driving and produce a findings report on whether the original 90 piles met design safety factor requirements. Concluded that 19 piles were deficient but omitted material facts including pile refusal data, wave equation results, and equipment failure from the report. Did not consult Engineer A's representatives or field personnel.
License: Professional Engineer
Specialty: Geotechnical or foundation engineering
Has client: Municipality
"the municipality retained Engineer B to supervise the driving of several test piles"
Peer: Engineer A
"At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A"
[facts] "the municipality retained Engineer B to supervise the driving of several test piles"
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer B
  • attributes: {'license': 'Professional Engineer', 'specialty': 'Geotechnical or foundation engineering'}
  • relationships: {'type': 'has_client', 'target': 'Municipality', 'quote': 'the municipality retained Engineer B to supervise the driving of several test piles'}; {'type': 'peer', 'target': 'Engineer A', 'quote': "At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A"}
Literal extractions (kept for synthesis)
  • textReferences content: the municipality retained Engineer B to supervise the driving of several test piles; Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations; Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; Engineer B did not report that the dynamic test equipment had failed; At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A
  • roleClass content: Litigation Expert Engineer
  • roleCategory content: provider_client
  • caseInvolvement content: Retained by the municipality to supervise test pile driving and produce a findings report on whether the original 90 piles met design safety factor requirements. Concluded that 19 piles were deficient but omitted material facts including pile refusal data, wave equation results, and equipment failure from the report. Did not consult Engineer A's representatives or field personnel.
  • confidence assessment: 0.91
Engineer A Municipal Infrastructure Designer
MunicipalInfrastructureDesignEngineer
New C71
Text References:
"Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles"
"Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days"
"Engineer A and the municipality shared the cost of the settlement with the contractor for $300,000"
Confidence: 0.92
Actor: Engineer A
Role Class: Municipal Infrastructure Design Engineer
Role Category: provider_client
Case Involvement: Retained by the municipality to design a dock on a 90-pile foundation. Became a defendant in litigation over the contractor's extra claim and defended the adequacy of the pile design using geotechnical set-up strength arguments.
License: Professional Engineer
Specialty: Foundation and dock design
Has client: Municipality
"Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles"
Reviewed by: Engineer B
"the municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design c..."
Has provider: Independent Geotechnical Consultant
"An independent geotechnical consultant was retained by Engineer A to observe the test"
[facts] "Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles"
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Engineer A
  • attributes: {'license': 'Professional Engineer', 'specialty': 'Foundation and dock design'}
  • relationships: {'type': 'has_client', 'target': 'Municipality', 'quote': 'Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles'}; {'type': 'reviewed_by', 'target': 'Engineer B', 'quote': 'the municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements'}; {'type': 'has_provider', 'target': 'Independent Geotechnical Consultant', 'quote': 'An independent geotechnical consultant was retained by Engineer A to observe the test'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles; Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days; Engineer A and the municipality shared the cost of the settlement with the contractor for $300,000
  • roleClass content: Municipal Infrastructure Design Engineer
  • roleCategory content: provider_client
  • caseInvolvement content: Retained by the municipality to design a dock on a 90-pile foundation. Became a defendant in litigation over the contractor's extra claim and defended the adequacy of the pile design using geotechnical set-up strength arguments.
  • confidence assessment: 0.92
Geotechnical Consultant Observer
IndependentGeotechnicalObserver
New C71
Text References:
"An independent geotechnical consultant was retained by Engineer A to observe the test"
"The geotechnical consultant testified and showed that dynamic test equipment had failed during the test"
"In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value reported by Engineer B's tests"
Confidence: 0.87
Actor: Independent Geotechnical Consultant
Role Class: Independent Geotechnical Observer
Role Category: provider_client
Case Involvement: Retained by Engineer A to observe the test pile driving supervised by Engineer B. Identified procedural irregularities including equipment failure, inconsistent hammer type, and pre-record drops that would have broken pile bond, and testified on these findings to challenge the validity of Engineer B's test results.
License: Professional Engineer or Geotechnical Specialist
Specialty: Geotechnical engineering, pile dynamics
Has client: Engineer A
"An independent geotechnical consultant was retained by Engineer A to observe the test"
Reviews: Engineer B
"The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same dept..."
[facts] "An independent geotechnical consultant was retained by Engineer A to observe the test"
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Independent Geotechnical Consultant
  • attributes: {'license': 'Professional Engineer or Geotechnical Specialist', 'specialty': 'Geotechnical engineering, pile dynamics'}
  • relationships: {'type': 'has_client', 'target': 'Engineer A', 'quote': 'An independent geotechnical consultant was retained by Engineer A to observe the test'}; {'type': 'reviews', 'target': 'Engineer B', 'quote': 'The geotechnical consultant testified and showed that dynamic test equipment had failed during the test and that the test piles were not driven to the same depth of penetration'}
Literal extractions (kept for synthesis)
  • textReferences content: An independent geotechnical consultant was retained by Engineer A to observe the test; The geotechnical consultant testified and showed that dynamic test equipment had failed during the test; In the opinion of Engineer A's geotechnical consultant, this would have broken the pile bond and undervalued the skin friction value reported by Engineer B's tests
  • roleClass content: Independent Geotechnical Observer
  • roleCategory content: provider_client
  • caseInvolvement content: Retained by Engineer A to observe the test pile driving supervised by Engineer B. Identified procedural irregularities including equipment failure, inconsistent hammer type, and pre-record drops that would have broken pile bond, and testified on these findings to challenge the validity of Engineer B's test results.
  • confidence assessment: 0.87
Municipality Client
Municipal Client
Linked
Municipal Client
C71
Text References:
"Engineer A was retained by a municipality to design a dock"
"Engineer A and the municipality were both sued by the contractor"
"Engineer A and the municipality shared the cost of the settlement with the contractor for $300,000"
"the municipality retained Engineer B to supervise the driving of several test piles"
Confidence: 0.93
Actor: Municipality
Role Class: Municipal Client
Role Category: provider_client
Case Involvement: Commissioned Engineer A to design the dock and pile foundation. Later became a co-defendant in litigation with Engineer A, retained Engineer B to conduct test pile investigations, and shared the mediation settlement cost.
Type: Government municipality
License: None (non-engineer client)
Has provider: Engineer A
"Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles"
Has provider: Engineer B
"the municipality retained Engineer B to supervise the driving of several test piles"
[facts] "Engineer A was retained by a municipality to design a dock"
Field classification (triples vs literals)
Relations (structural triples)
  • actor: Municipality
  • attributes: {'type': 'Government municipality', 'license': 'None (non-engineer client)'}
  • relationships: {'type': 'has_provider', 'target': 'Engineer A', 'quote': 'Engineer A was retained by a municipality to design a dock on a supporting foundation of 90 piles'}; {'type': 'has_provider', 'target': 'Engineer B', 'quote': 'the municipality retained Engineer B to supervise the driving of several test piles'}
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A was retained by a municipality to design a dock; Engineer A and the municipality were both sued by the contractor; Engineer A and the municipality shared the cost of the settlement with the contractor for $300,000; the municipality retained Engineer B to supervise the driving of several test piles
  • roleClass content: Municipal Client
  • roleCategory content: provider_client
  • caseInvolvement content: Commissioned Engineer A to design the dock and pile foundation. Later became a co-defendant in litigation with Engineer A, retained Engineer B to conduct test pile investigations, and shared the mediation settlement cost.
  • confidence assessment: 0.93

S States

States Classes
5
Incomplete Expert Report State
rdfs:subClassOf States
Review
Incomplete Professional Report State
C71
Definition
Extracted from facts primary
State in which a professional retained as an expert or reviewer has produced a report that omits material technical findings, contradictory data, or equipment failures that would be necessary for the report to present a complete and accurate professional opinion, creating obligations of completeness, objectivity, and truthfulness in professional communications.
Inherited from IncompleteProfessionalReportState · note
State in which a professional has produced or submitted a report or analysis that omits material information, selectively presents data, or fails to investigate relevant factors, resulting in a misleading or incomplete professional work product that violates duties of objectivity, completeness, and truthfulness.
Properties
Text References:
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"Engineer B did not report that the dynamic test equipment had failed"
Confidence: 0.88
State Category: information
Persistence Type: inertial
Activation Conditions:
  • Expert or reviewing professional submits a report
  • Report omits material findings known to the professional
  • Omitted findings would materially affect the conclusions presented
Termination Conditions:
  • Supplemental report issued correcting omissions
  • Report withdrawn and replaced with complete analysis
Obligation Activation:
  • Duty to present complete and objective findings
  • Duty to disclose equipment failures or test anomalies
  • Duty to report contradictory data that bears on conclusions
Action Constraints:
  • Professional must not issue conclusions based on selectively presented data
  • Professional must not omit findings that contradict the primary conclusion
Principle Transformation: Transforms general honesty and objectivity principles into specific obligations to disclose all material technical findings, including those that undercut the professional's own conclusions.
[facts] "Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; Engineer B did not report that the dynamic test equipment had failed
  • stateCategory content: information
  • persistenceType content: inertial
  • principleTransformation content: Transforms general honesty and objectivity principles into specific obligations to disclose all material technical findings, including those that undercut the professional's own conclusions.
  • confidence assessment: 0.88
Derived (reconstructable from the graph)
  • activationConditions: Expert or reviewing professional submits a report; Report omits material findings known to the professional; Omitted findings would materially affect the conclusions presented
  • terminationConditions: Supplemental report issued correcting omissions; Report withdrawn and replaced with complete analysis
  • obligationActivation: Duty to present complete and objective findings; Duty to disclose equipment failures or test anomalies; Duty to report contradictory data that bears on conclusions
  • actionConstraints: Professional must not issue conclusions based on selectively presented data; Professional must not omit findings that contradict the primary conclusion
changed
New C71
Definition
Extracted from facts primary
State in which a professional invokes a contractually defined scope of work as justification for failing to investigate or report on material technical findings that bear on safety or accuracy, creating a tension between contractual scope compliance and the professional's independent duty of completeness and objectivity.
Properties
Text References:
"Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'"
Confidence: 0.85
State Category: conflict
Persistence Type: inertial
Activation Conditions:
  • Professional is retained under a defined scope of work
  • Material information exists outside the literal scope
  • Professional declines to investigate or report that information citing scope limitations
Termination Conditions:
  • Scope is expanded to cover the material information
  • Professional voluntarily addresses the material information despite scope limitation
  • Engagement concludes
Obligation Activation:
  • Duty to assess whether scope limitations prevent fulfillment of independent professional obligations
  • Duty to disclose scope limitations that affect completeness of conclusions
  • Duty to seek scope expansion when material safety or accuracy issues are identified
Action Constraints:
  • Professional must not use scope limitation as a shield against reporting known material findings
  • Professional must not present conclusions as complete when scope prevented full investigation
Principle Transformation: Transforms the contractual faithful-agent duty into a bounded obligation that cannot override the independent professional duty of objectivity and completeness when material findings are at stake.
[facts] "Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'
  • stateCategory content: conflict
  • persistenceType content: inertial
  • principleTransformation content: Transforms the contractual faithful-agent duty into a bounded obligation that cannot override the independent professional duty of objectivity and completeness when material findings are at stake.
  • confidence assessment: 0.85
Derived (reconstructable from the graph)
  • activationConditions: Professional is retained under a defined scope of work; Material information exists outside the literal scope; Professional declines to investigate or report that information citing scope limitations
  • terminationConditions: Scope is expanded to cover the material information; Professional voluntarily addresses the material information despite scope limitation; Engagement concludes
  • obligationActivation: Duty to assess whether scope limitations prevent fulfillment of independent professional obligations; Duty to disclose scope limitations that affect completeness of conclusions; Duty to seek scope expansion when material safety or accuracy issues are identified
  • actionConstraints: Professional must not use scope limitation as a shield against reporting known material findings; Professional must not present conclusions as complete when scope prevented full investigation
changed
New C71
Definition
Extracted from facts primary
State in which a professional conducting a review or investigation declines to consult available witnesses, records, or knowledgeable parties whose input would be material to the accuracy and completeness of the professional's conclusions, creating a condition of avoidable epistemic incompleteness and a breach of the duty of due diligence.
Properties
Text References:
"At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the a..."
"No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth."
Confidence: 0.86
State Category: information
Persistence Type: inertial
Activation Conditions:
  • Professional is conducting a review or investigation
  • Knowledgeable parties or records are available and accessible
  • Professional declines to consult those sources
  • The unconsulted sources would be material to the professional's conclusions
Termination Conditions:
  • Professional consults the available sources
  • Report is supplemented with findings from those sources
  • Engagement concludes
Obligation Activation:
  • Duty of due diligence in investigation
  • Duty to seek out material information before issuing conclusions
  • Duty to consult available knowledgeable parties
Action Constraints:
  • Professional must not issue conclusions without reasonable investigation of available sources
  • Professional must not dismiss available records without stated technical justification
Principle Transformation: Transforms the general duty of objectivity and thoroughness into a specific obligation to actively seek out and consider available material information before issuing professional conclusions.
[facts] "At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the a..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.; No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
  • stateCategory content: information
  • persistenceType content: inertial
  • principleTransformation content: Transforms the general duty of objectivity and thoroughness into a specific obligation to actively seek out and consider available material information before issuing professional conclusions.
  • confidence assessment: 0.86
Derived (reconstructable from the graph)
  • activationConditions: Professional is conducting a review or investigation; Knowledgeable parties or records are available and accessible; Professional declines to consult those sources; The unconsulted sources would be material to the professional's conclusions
  • terminationConditions: Professional consults the available sources; Report is supplemented with findings from those sources; Engagement concludes
  • obligationActivation: Duty of due diligence in investigation; Duty to seek out material information before issuing conclusions; Duty to consult available knowledgeable parties
  • actionConstraints: Professional must not issue conclusions without reasonable investigation of available sources; Professional must not dismiss available records without stated technical justification
changed
Disputed Driving Records State
rdfs:subClassOf States
New C71
Definition
Extracted from facts primary
State in which the accuracy or reliability of construction or installation records is contested between parties, creating a condition in which professional conclusions that rely on or dismiss those records carry heightened obligations of transparency, disclosure of the dispute, and independent verification before issuing findings.
Properties
Text References:
"We just did not believe the driving records"
"The driving records look suspicious."
"Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records"
Confidence: 0.82
State Category: information
Persistence Type: inertial
Activation Conditions:
  • Construction or installation records exist
  • One or more parties contest the accuracy or reliability of those records
  • Professional conclusions depend on acceptance or rejection of the records
Termination Conditions:
  • Records are independently verified or refuted
  • Dispute is resolved by agreed findings
  • Engagement concludes
Obligation Activation:
  • Duty to disclose that records are disputed when relying on or dismissing them
  • Duty to seek independent verification of disputed records
  • Duty to present the dispute as a material uncertainty in professional conclusions
Action Constraints:
  • Professional must not dismiss records without stated technical justification
  • Professional must not issue conclusions as definitive when they rest on unresolved record disputes
Principle Transformation: Transforms general objectivity principles into specific obligations to disclose record disputes and seek verification before issuing conclusions that depend on the acceptance or rejection of contested records.
[facts] "We just did not believe the driving records"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: We just did not believe the driving records; The driving records look suspicious.; Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records
  • stateCategory content: information
  • persistenceType content: inertial
  • principleTransformation content: Transforms general objectivity principles into specific obligations to disclose record disputes and seek verification before issuing conclusions that depend on the acceptance or rejection of contested records.
  • confidence assessment: 0.82
Derived (reconstructable from the graph)
  • activationConditions: Construction or installation records exist; One or more parties contest the accuracy or reliability of those records; Professional conclusions depend on acceptance or rejection of the records
  • terminationConditions: Records are independently verified or refuted; Dispute is resolved by agreed findings; Engagement concludes
  • obligationActivation: Duty to disclose that records are disputed when relying on or dismissing them; Duty to seek independent verification of disputed records; Duty to present the dispute as a material uncertainty in professional conclusions
  • actionConstraints: Professional must not dismiss records without stated technical justification; Professional must not issue conclusions as definitive when they rest on unresolved record disputes
changed
Test Methodology Deficiency State
rdfs:subClassOf States
New C71
Definition
Extracted from facts primary
State in which the testing or investigative methodology used to generate data for a professional report contains known deficiencies, including equipment failures, non-representative conditions, or procedural deviations, that materially affect the reliability of the data and the validity of conclusions drawn from it, creating obligations to disclose those deficiencies in any report relying on the data.
Properties
Text References:
"Engineer B did not report that the dynamic test equipment had failed"
"The geotechnical consultant testified and showed that dynamic test equipment had failed during the test"
"Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving"
"After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced"
Confidence: 0.87
State Category: risk
Persistence Type: inertial
Activation Conditions:
  • Testing or investigation is conducted to generate data for a professional report
  • Equipment fails or procedural deviations occur during testing
  • The deficiencies are known to the professional issuing the report
  • Conclusions in the report rely on the deficient test data
Termination Conditions:
  • Testing is repeated under corrected conditions
  • Report is amended to disclose deficiencies and qualify conclusions accordingly
  • Engagement concludes
Obligation Activation:
  • Duty to disclose equipment failures and procedural deviations in the report
  • Duty to qualify conclusions that rest on deficient test data
  • Duty to recommend retesting when deficiencies are material
Action Constraints:
  • Professional must not present conclusions as reliable when known test deficiencies undermine the data
  • Professional must not omit equipment failures from reports that rely on data from those tests
Principle Transformation: Transforms the general duty of truthfulness and objectivity into a specific obligation to disclose known test deficiencies and qualify any conclusions that depend on data generated under those deficient conditions.
[facts] "Engineer B did not report that the dynamic test equipment had failed"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B did not report that the dynamic test equipment had failed; The geotechnical consultant testified and showed that dynamic test equipment had failed during the test; Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving; After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced
  • stateCategory content: risk
  • persistenceType content: inertial
  • principleTransformation content: Transforms the general duty of truthfulness and objectivity into a specific obligation to disclose known test deficiencies and qualify any conclusions that depend on data generated under those deficient conditions.
  • confidence assessment: 0.87
Derived (reconstructable from the graph)
  • activationConditions: Testing or investigation is conducted to generate data for a professional report; Equipment fails or procedural deviations occur during testing; The deficiencies are known to the professional issuing the report; Conclusions in the report rely on the deficient test data
  • terminationConditions: Testing is repeated under corrected conditions; Report is amended to disclose deficiencies and qualify conclusions accordingly; Engagement concludes
  • obligationActivation: Duty to disclose equipment failures and procedural deviations in the report; Duty to qualify conclusions that rest on deficient test data; Duty to recommend retesting when deficiencies are material
  • actionConstraints: Professional must not present conclusions as reliable when known test deficiencies undermine the data; Professional must not omit equipment failures from reports that rely on data from those tests
States Individuals
9
Engineer B Selective Analysis Disclosure
Partial Analysis Disclosure State
Linked
Partial Analysis Disclosure State
C71
Text References:
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations,..."
Confidence: 0.88
State Class: Partial Analysis Disclosure State
Subject: Engineer B's report conclusions regarding the 19 piles
Active Period: From issuance of Engineer B's report through the period of dispute
Triggering Event: Engineer B presented a conclusion based solely on depth-of-penetration skin friction analysis while omitting the wave equation analysis showing the same piles had been driven to essential refusal with strength several multiples over design requirements
Terminated By: Not resolved within the case facts presented
Affected Parties:
  • Engineer B
  • Engineer A
  • Municipality
  • Contractor
Urgency Level: high
[facts] "Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations,..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer A; Municipality; Contractor
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal and that, applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements.
  • stateClass content: Partial Analysis Disclosure State
  • subject content: Engineer B's report conclusions regarding the 19 piles
  • activePeriod content: From issuance of Engineer B's report through the period of dispute
  • triggeringEvent content: Engineer B presented a conclusion based solely on depth-of-penetration skin friction analysis while omitting the wave equation analysis showing the same piles had been driven to essential refusal with strength several multiples over design requirements
  • terminatedBy content: Not resolved within the case facts presented
  • confidence assessment: 0.88
  • urgencyLevel assessment: high
Engineer B Incomplete Expert Report
Incomplete Professional Report State
Linked
Incomplete Professional Report State
C71
Text References:
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"Engineer B did not report that the dynamic test equipment had failed"
Confidence: 0.92
State Class: Incomplete Professional Report State
Subject: Engineer B's concluding report on the 90 pile foundation
Active Period: From issuance of Engineer B's concluding report through the period of dispute
Triggering Event: Engineer B issued a report concluding that 19 piles did not meet the required safety factor without disclosing the pile driving refusal data or the equipment failure
Terminated By: Not resolved within the case facts presented
Affected Parties:
  • Engineer B
  • Engineer A
  • Municipality
  • Contractor
  • Public users of the dock
Urgency Level: high
[facts] "Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer A; Municipality; Contractor; Public users of the dock
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; Engineer B did not report that the dynamic test equipment had failed
  • stateClass content: Incomplete Professional Report State
  • subject content: Engineer B's concluding report on the 90 pile foundation
  • activePeriod content: From issuance of Engineer B's concluding report through the period of dispute
  • triggeringEvent content: Engineer B issued a report concluding that 19 piles did not meet the required safety factor without disclosing the pile driving refusal data or the equipment failure
  • terminatedBy content: Not resolved within the case facts presented
  • confidence assessment: 0.92
  • urgencyLevel assessment: high
Engineer B Scope Limitation Justification
ScopeLimitationJustificationState
New C71
Text References:
"Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'"
Confidence: 0.88
State Class: Scope Limitation Justification State
Subject: Engineer B's refusal to review pile driving records based on scope of work
Active Period: Throughout Engineer B's investigation and report preparation
Triggering Event: Engineer B declined to review pile driving records, citing scope of work limitations
Terminated By: Not resolved within the case facts presented
Affected Parties:
  • Engineer B
  • Engineer A
  • Municipality
Urgency Level: medium
[facts] "Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'"
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer A; Municipality
Literal extractions (kept for synthesis)
  • textReferences content: Previously, Engineer B had said, 'We didn't look at the pile driving records because it was not in our scope of work.'
  • stateClass content: Scope Limitation Justification State
  • subject content: Engineer B's refusal to review pile driving records based on scope of work
  • activePeriod content: Throughout Engineer B's investigation and report preparation
  • triggeringEvent content: Engineer B declined to review pile driving records, citing scope of work limitations
  • terminatedBy content: Not resolved within the case facts presented
  • confidence assessment: 0.88
  • urgencyLevel assessment: medium
Engineer B Failure to Consult Available Sources
FailuretoConsultAvailableSourcesState
New C71
Text References:
"At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the a..."
"No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth."
Confidence: 0.91
State Class: Failure to Consult Available Sources State
Subject: Engineer B's investigation process for the pile foundation report
Active Period: Throughout Engineer B's investigation and report preparation
Triggering Event: Engineer B conducted investigation without consulting Engineer A's representatives, contractors, or workers who were available and had material knowledge
Terminated By: Not resolved within the case facts presented
Affected Parties:
  • Engineer B
  • Engineer A
  • Municipality
  • Contractor workers
Urgency Level: high
[facts] "At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the a..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer A; Municipality; Contractor workers
Literal extractions (kept for synthesis)
  • textReferences content: At no time during the development of Engineer B's report did Engineer B talk to any representative of Engineer A, even though Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records.; No effort was made by Engineer B to inquire from contractors, workers, or others on the job to verify or refute his theories about why the 19 piles met driving refusal prior to predicted depth.
  • stateClass content: Failure to Consult Available Sources State
  • subject content: Engineer B's investigation process for the pile foundation report
  • activePeriod content: Throughout Engineer B's investigation and report preparation
  • triggeringEvent content: Engineer B conducted investigation without consulting Engineer A's representatives, contractors, or workers who were available and had material knowledge
  • terminatedBy content: Not resolved within the case facts presented
  • confidence assessment: 0.91
  • urgencyLevel assessment: high
Engineer B Disputed Driving Records
DisputedDrivingRecordsState
New C71
Text References:
"We just did not believe the driving records"
"The driving records look suspicious."
"Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records"
Confidence: 0.87
State Class: Disputed Driving Records State
Subject: Pile driving records for the 90-pile dock foundation
Active Period: From the time Engineer B expressed disbelief in the driving records through the period of dispute
Triggering Event: Engineer B stated disbelief in the pile driving records and declined to rely on them without independent verification or stated technical justification
Terminated By: Not resolved within the case facts presented
Affected Parties:
  • Engineer B
  • Engineer A
  • Municipality
  • Contractor
Urgency Level: high
[facts] "We just did not believe the driving records"
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer A; Municipality; Contractor
Literal extractions (kept for synthesis)
  • textReferences content: We just did not believe the driving records; The driving records look suspicious.; Engineer A's on-site representatives were available to testify as to the accuracy of the pile driving records
  • stateClass content: Disputed Driving Records State
  • subject content: Pile driving records for the 90-pile dock foundation
  • activePeriod content: From the time Engineer B expressed disbelief in the driving records through the period of dispute
  • triggeringEvent content: Engineer B stated disbelief in the pile driving records and declined to rely on them without independent verification or stated technical justification
  • terminatedBy content: Not resolved within the case facts presented
  • confidence assessment: 0.87
  • urgencyLevel assessment: high
Engineer B Test Methodology Deficiency
TestMethodologyDeficiencyState
New C71
Text References:
"Engineer B did not report that the dynamic test equipment had failed"
"The geotechnical consultant testified and showed that dynamic test equipment had failed during the test"
"Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving"
"After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced"
Confidence: 0.9
State Class: Test Methodology Deficiency State
Subject: Test pile driving program supervised by Engineer B
Active Period: From the time of test pile driving through issuance of Engineer B's report
Triggering Event: Dynamic test equipment failed during the test pile program and procedural deviations occurred, including use of a vibratory hammer not used in original driving and pre-record hammer drops that would have broken pile bond
Terminated By: Not resolved within the case facts presented; Engineer B's report did not disclose the equipment failure
Affected Parties:
  • Engineer B
  • Engineer A
  • Municipality
  • Geotechnical consultant for Engineer A
Urgency Level: high
[facts] "Engineer B did not report that the dynamic test equipment had failed"
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Engineer A; Municipality; Geotechnical consultant for Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B did not report that the dynamic test equipment had failed; The geotechnical consultant testified and showed that dynamic test equipment had failed during the test; Driving conditions were not duplicated in driving the test piles in that a vibratory hammer was used for the test piles and not used in the original driving; After the 30 day set up, the driving hammer was dropped several times to start the hammer before the record of blow counts commenced
  • stateClass content: Test Methodology Deficiency State
  • subject content: Test pile driving program supervised by Engineer B
  • activePeriod content: From the time of test pile driving through issuance of Engineer B's report
  • triggeringEvent content: Dynamic test equipment failed during the test pile program and procedural deviations occurred, including use of a vibratory hammer not used in original driving and pre-record hammer drops that would have broken pile bond
  • terminatedBy content: Not resolved within the case facts presented; Engineer B's report did not disclose the equipment failure
  • confidence assessment: 0.9
  • urgencyLevel assessment: high
Linked
Public Safety at Risk
C71
Text References:
"Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
Confidence: 0.85
State Class: Public Safety at Risk
Subject: Structural adequacy of the 90-pile dock foundation
Active Period: From the time Engineer B's report identified 19 potentially non-conforming piles through resolution of the dispute
Triggering Event: Expert testimony and Engineer B's report raised questions about whether 19 of 90 piles met the safety factor required by design calculations
Terminated By: Not resolved within the case facts presented
Affected Parties:
  • Municipality
  • Public users of the dock
  • Engineer A
  • Engineer B
Urgency Level: high
[facts] "Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Municipality; Public users of the dock; Engineer A; Engineer B
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.
  • stateClass content: Public Safety at Risk
  • subject content: Structural adequacy of the 90-pile dock foundation
  • activePeriod content: From the time Engineer B's report identified 19 potentially non-conforming piles through resolution of the dispute
  • triggeringEvent content: Expert testimony and Engineer B's report raised questions about whether 19 of 90 piles met the safety factor required by design calculations
  • terminatedBy content: Not resolved within the case facts presented
  • confidence assessment: 0.85
  • urgencyLevel assessment: high
Engineer B Litigation Expert Relationship
Client Relationship Established
Linked
Client Relationship Established
C71
Text References:
"The municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements."
Confidence: 0.83
State Class: Client Relationship Established
Subject: Engineer B's retention by the municipality as expert
Active Period: From Engineer B's retention by the municipality through issuance of the concluding report
Triggering Event: Municipality retained Engineer B to supervise test pile driving and issue a report on pile adequacy in the context of litigation
Terminated By: Issuance of Engineer B's concluding report
Affected Parties:
  • Engineer B
  • Municipality
  • Engineer A
Urgency Level: medium
[facts] "The municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer B; Municipality; Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: The municipality retained Engineer B to supervise the driving of several test piles to see whether the piles would gain sufficient strength to meet the design calculation requirements.
  • stateClass content: Client Relationship Established
  • subject content: Engineer B's retention by the municipality as expert
  • activePeriod content: From Engineer B's retention by the municipality through issuance of the concluding report
  • triggeringEvent content: Municipality retained Engineer B to supervise test pile driving and issue a report on pile adequacy in the context of litigation
  • terminatedBy content: Issuance of Engineer B's concluding report
  • confidence assessment: 0.83
  • urgencyLevel assessment: medium
Engineer A Geotechnical Competence
Unquantified Risk Awareness State
Linked
Unquantified Risk Awareness State
C71
Text References:
"One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirement..."
"Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements."
Confidence: 0.8
State Class: Unquantified Risk Awareness State
Subject: Engineer A's awareness of potential pile adequacy concerns prior to and during litigation
Active Period: From initial pile driving through mediation and test pile program
Triggering Event: Pile driving records showed many piles did not meet initial driving resistance requirements, creating an unresolved question about long-term load capacity
Terminated By: Test pile program confirmed set-up strength gain, though dispute about 19 piles remained
Affected Parties:
  • Engineer A
  • Municipality
  • Contractor
  • Public users of the dock
Urgency Level: medium
[facts] "One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirement..."
Field classification (triples vs literals)
Relations (structural triples)
  • affectedParties: Engineer A; Municipality; Contractor; Public users of the dock
Literal extractions (kept for synthesis)
  • textReferences content: One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirements of the design calculations.; Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements.
  • stateClass content: Unquantified Risk Awareness State
  • subject content: Engineer A's awareness of potential pile adequacy concerns prior to and during litigation
  • activePeriod content: From initial pile driving through mediation and test pile program
  • triggeringEvent content: Pile driving records showed many piles did not meet initial driving resistance requirements, creating an unresolved question about long-term load capacity
  • terminatedBy content: Test pile program confirmed set-up strength gain, though dispute about 19 piles remained
  • confidence assessment: 0.8
  • urgencyLevel assessment: medium

Rs Resources

Resources Classes
5
Expert Witness Report Resource
rdfs:subClassOf Resources
New C71
Definition
Extracted from facts primary
A formal written report prepared by a retained expert witness for use in litigation, mediation, or dispute resolution, presenting technical findings, opinions, and conclusions on matters within the expert's professional competence. Such reports carry professional accountability obligations and serve as primary evidentiary knowledge sources in legal and quasi-legal proceedings.
Properties
Text References:
"Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"Additionally, Engineer B did not report that the dynamic test equipment had failed."
Confidence: 0.83
Resource Category: expert_interpretation
Authority Source: Retained professional engineers acting as expert witnesses
Extensional Function: Provides authoritative technical findings and professional opinions that ground factual determinations in disputes, establishing the evidentiary basis on which legal and ethical judgments are made.
Usage Context:
  • Litigation support
  • Mediation proceedings
  • Technical dispute resolution
[facts] "Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.; Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; Additionally, Engineer B did not report that the dynamic test equipment had failed.
  • resourceCategory content: expert_interpretation
  • authoritySource content: Retained professional engineers acting as expert witnesses
  • extensionalFunction content: Provides authoritative technical findings and professional opinions that ground factual determinations in disputes, establishing the evidentiary basis on which legal and ethical judgments are made.
  • usageContext content: Litigation support; Mediation proceedings; Technical dispute resolution
  • confidence assessment: 0.83
changed
Geotechnical Test Report Resource
rdfs:subClassOf Resources
New C71
Definition
Extracted from facts primary
A formal engineering report documenting the results of geotechnical field testing, such as pile load tests or dynamic testing, including methodology, equipment performance, and conclusions about soil or foundation behavior. Such reports serve as technical evidence in disputes and as professional knowledge sources grounding design adequacy determinations.
Properties
Text References:
"Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
"The geotechnical consultant testified and showed that dynamic test equipment had failed during the test"
Confidence: 0.82
Resource Category: technical_standard
Authority Source: Retained geotechnical engineering consultants and testing firms
Extensional Function: Provides empirical grounding for assessments of foundation design adequacy and serves as a primary evidentiary artifact in professional and legal disputes over structural performance.
Usage Context:
  • Foundation design review
  • Litigation and mediation support
  • Peer technical evaluation
[facts] "Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.; The geotechnical consultant testified and showed that dynamic test equipment had failed during the test
  • resourceCategory content: technical_standard
  • authoritySource content: Retained geotechnical engineering consultants and testing firms
  • extensionalFunction content: Provides empirical grounding for assessments of foundation design adequacy and serves as a primary evidentiary artifact in professional and legal disputes over structural performance.
  • usageContext content: Foundation design review; Litigation and mediation support; Peer technical evaluation
  • confidence assessment: 0.82
changed
Pile Driving Record Resource
rdfs:subClassOf Resources
New C71
Definition
Extracted from facts primary
A contemporaneous field record documenting blow counts, penetration depth, and driving resistance data collected during pile installation. These records serve as primary technical evidence for evaluating whether driven piles achieved design load-carrying capacity and are used in post-construction review, dispute resolution, and engineering analysis.
Properties
Text References:
"One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirement..."
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"We just did not believe the driving records"
"We didn't look at the pile driving records because it was not in our scope of work."
Confidence: 0.8
Resource Category: reference_material
Authority Source: On-site construction records maintained by contractors and resident engineers
Extensional Function: Provides primary field data grounding assessments of pile capacity and design compliance, enabling engineers and reviewers to evaluate whether construction met design intent.
Usage Context:
  • Foundation performance evaluation
  • Litigation and mediation support
  • Peer technical review
[facts] "One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirement..."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirements of the design calculations.; Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; We just did not believe the driving records; We didn't look at the pile driving records because it was not in our scope of work.
  • resourceCategory content: reference_material
  • authoritySource content: On-site construction records maintained by contractors and resident engineers
  • extensionalFunction content: Provides primary field data grounding assessments of pile capacity and design compliance, enabling engineers and reviewers to evaluate whether construction met design intent.
  • usageContext content: Foundation performance evaluation; Litigation and mediation support; Peer technical review
  • confidence assessment: 0.8
changed
Wave Equation Analysis Resource
rdfs:subClassOf Resources
New C71
Definition
Extracted from facts primary
A documented analytical method or calculation applying wave equation principles to pile driving data to estimate pile capacity from blow count and driving resistance records. This method is an accepted engineering technique for evaluating driven pile performance and serves as a technical knowledge source in foundation engineering practice.
Properties
Text References:
"applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements"
Confidence: 0.78
Resource Category: technical_standard
Authority Source: Geotechnical engineering professional consensus and published analytical methods
Extensional Function: Provides an accepted analytical framework for translating field driving records into pile capacity estimates, grounding professional judgments about whether piles meet design requirements.
Usage Context:
  • Pile capacity evaluation
  • Foundation design review
  • Dispute resolution technical analysis
[facts] "applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements"
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements
  • resourceCategory content: technical_standard
  • authoritySource content: Geotechnical engineering professional consensus and published analytical methods
  • extensionalFunction content: Provides an accepted analytical framework for translating field driving records into pile capacity estimates, grounding professional judgments about whether piles meet design requirements.
  • usageContext content: Pile capacity evaluation; Foundation design review; Dispute resolution technical analysis
  • confidence assessment: 0.78
changed
New C71
Definition
Extracted from facts primary
A formal report produced by a geotechnical engineering firm documenting subsurface investigation findings, soil properties, and design recommendations for foundation systems. Such reports provide the technical basis for pile design parameters including expected strength gain over time and serve as primary reference documents throughout construction and dispute resolution.
Properties
Text References:
"Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements."
Confidence: 0.8
Resource Category: reference_material
Authority Source: Licensed geotechnical engineering firms retained for subsurface investigation
Extensional Function: Grounds foundation design decisions in documented subsurface data and professional geotechnical judgment, providing the technical basis for design parameters such as anticipated pile set-up strength.
Usage Context:
  • Foundation design
  • Construction administration
  • Dispute resolution technical review
[facts] "Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements."
Field classification (triples vs literals)
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements.
  • resourceCategory content: reference_material
  • authoritySource content: Licensed geotechnical engineering firms retained for subsurface investigation
  • extensionalFunction content: Grounds foundation design decisions in documented subsurface data and professional geotechnical judgment, providing the technical basis for design parameters such as anticipated pile set-up strength.
  • usageContext content: Foundation design; Construction administration; Dispute resolution technical review
  • confidence assessment: 0.8
Resources Individuals
4
Engineer B Pile Foundation Test Report
GeotechnicalTestReportResource
New C71
Text References:
"Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"Additionally, Engineer B did not report that the dynamic test equipment had failed."
Confidence: 0.88
Resource Class: Geotechnical Test Report Resource
Document Title: Engineer B Report on Test Pile Driving and Pile Capacity Evaluation
Created By: Engineer B
Used By: Engineer B
Used In Context: Engineer B's report was the primary technical artifact at issue in the dispute, concluding that 19 of 90 piles did not meet the required safety factor. The report omitted findings about driving to essential refusal and the failure of dynamic test equipment, raising questions about completeness and objectivity.
[facts] "Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations."
Field classification (triples vs literals)
Relations (structural triples)
  • usedBy: Engineer B
Literal extractions (kept for synthesis)
  • textReferences content: Engineer B's concluding report stated that approximately 19 of the 90 piles did not meet the safety factor required by the design calculations.; Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; Additionally, Engineer B did not report that the dynamic test equipment had failed.
  • resourceClass content: Geotechnical Test Report Resource
  • documentTitle content: Engineer B Report on Test Pile Driving and Pile Capacity Evaluation
  • createdBy content: Engineer B
  • usedInContext content: Engineer B's report was the primary technical artifact at issue in the dispute, concluding that 19 of 90 piles did not meet the required safety factor. The report omitted findings about driving to essential refusal and the failure of dynamic test equipment, raising questions about completeness and objectivity.
  • confidence assessment: 0.88
Geotechnical Firm Original Design Report
GeotechnicalInvestigationReportResource
New C71
Text References:
"Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements."
Confidence: 0.85
Resource Class: Geotechnical Investigation Report Resource
Document Title: Geotechnical Firm Report on Pile Design and Expected Strength Gain
Created By: Geotechnical firm retained by Engineer A
Used By: Engineer A
Used In Context: The original geotechnical firm's report provided the design basis for expected pile set-up strength, predicting that piles would gain sufficient resistance within 30 days of initial driving to meet load-carrying requirements.
[facts] "Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements."
Field classification (triples vs literals)
Relations (structural triples)
  • usedBy: Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: Engineer A testified that the geotechnical firm's report expected that the piles would gain sufficient additional strength within 30 days to meet driving resistance requirements.
  • resourceClass content: Geotechnical Investigation Report Resource
  • documentTitle content: Geotechnical Firm Report on Pile Design and Expected Strength Gain
  • createdBy content: Geotechnical firm retained by Engineer A
  • usedInContext content: The original geotechnical firm's report provided the design basis for expected pile set-up strength, predicting that piles would gain sufficient resistance within 30 days of initial driving to meet load-carrying requirements.
  • confidence assessment: 0.85
Project Pile Driving Field Records
PileDrivingRecordResource
New C71
Text References:
"One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirement..."
"Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal"
"We just did not believe the driving records"
"We didn't look at the pile driving records because it was not in our scope of work."
Confidence: 0.87
Resource Class: Pile Driving Record Resource
Document Title: Pile Driving Records for 90-Pile Dock Foundation
Created By: On-site construction personnel and Engineer A's representatives
Used By: Engineer A
Used In Context: The pile driving records documented blow counts and penetration depths for all 90 piles. They were central to the dispute: Engineer A's representatives and geotechnical consultant relied on them to argue that 19 piles had been driven to essential refusal, while Engineer B declined to consult them, citing scope limitations and credibility concerns.
[facts] "One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirement..."
Field classification (triples vs literals)
Relations (structural triples)
  • usedBy: Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: One expert testified that the pile driving records indicated that many of the piles did not, at the time of initial driving, meet driving resistance sufficient to satisfy the load carrying requirements; Engineer B did not state anywhere in the report that these 19 piles, according to the pile driving records, had been driven to essential refusal; We just did not believe the driving records; We didn't look at the pile driving records because it was not in our scope of work.
  • resourceClass content: Pile Driving Record Resource
  • documentTitle content: Pile Driving Records for 90-Pile Dock Foundation
  • createdBy content: On-site construction personnel and Engineer A's representatives
  • usedInContext content: The pile driving records documented blow counts and penetration depths for all 90 piles. They were central to the dispute: Engineer A's representatives and geotechnical consultant relied on them to argue that 19 piles had been driven to essential refusal, while Engineer B declined to consult them, citing scope limitations and credibility concerns.
  • confidence assessment: 0.87
Wave Equation Pile Capacity Calculations
WaveEquationAnalysisResource
New C71
Text References:
"applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements"
Confidence: 0.82
Resource Class: Wave Equation Analysis Resource
Document Title: Wave Equation Analysis of Pile Driving Records
Created By: Engineer A's geotechnical consultant
Used By: Engineer A
Used In Context: Accepted wave equation calculations applied to the pile driving records indicated that the 19 disputed piles had achieved strength several multiples over the calculated load requirements, contradicting Engineer B's depth-based capacity assessment.
[facts] "applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements"
Field classification (triples vs literals)
Relations (structural triples)
  • usedBy: Engineer A
Literal extractions (kept for synthesis)
  • textReferences content: applying accepted wave equation calculations, the piles would have indicated a strength several multiples over the calculated load requirements
  • resourceClass content: Wave Equation Analysis Resource
  • documentTitle content: Wave Equation Analysis of Pile Driving Records
  • createdBy content: Engineer A's geotechnical consultant
  • usedInContext content: Accepted wave equation calculations applied to the pile driving records indicated that the 19 disputed piles had achieved strength several multiples over the calculated load requirements, contradicting Engineer B's depth-based capacity assessment.
  • confidence assessment: 0.82
Pass 1: Contextual Framework - Facts
Review extracted entities, then continue to the next step
Continue to Discussion Review

© Licensed under the GNU GPL v3 | Report Issue