Pipeline Survey Processing
A pipeline hydraulic or integrity model needs an elevation profile. The profile
almost always starts life as a survey file: thousands of rows of KP, depth to top
of pipe, seabed depth and coordinates, produced by a different discipline, in a
different datum, with null markers, duplicated stations, sections that belong to a
neighbouring line, and a handful of points that are simply wrong.
The step from that file to a usable profile is where the numbers are decided, and
it is normally done by hand in a spreadsheet with no record of what was done. This
skill makes that step explicit and repeatable: every filter, sign flip, projection
and rejection is written into a processing log that travels with the result, so a
reviewer can see how the profile in front of them was produced.
It stops at the profile. Free spans and burial intervals are reported as geometric
candidates for a qualified assessment - it does not perform modal, VIV, fatigue
or stability analysis.
When to Use
- A survey or inspection export must become a pipeline elevation profile for a
NeqSim pipe model.
- Erroneous points, null markers or duplicated stations need to be identified
before a profile is trusted.
- Only part of a surveyed line is in scope, and the section between two
structures must be extracted with the trim recorded.
- Free-span or cover candidates need to be located along KP as input to a
DNV-RP-F105 or DNV-RP-F114 assessment.
- Two surveys of the same line, taken years apart, need a like-for-like change
comparison.
- The survey lacks outer diameter and a value has to be supplied manually with
the override recorded as a data gap.
When Not to Use
- As a free-span assessment. Span candidates here are geometry only; modal
response, VIV screening and fatigue belong to DNV-RP-F105 and to a qualified
pipeline engineer.
- As a positioning or datum authority. This skill normalises a sign convention
and projects coordinates for screening; it does not perform geodetic datum
transformation and must not be used to reconcile survey datums.
- To conclude that a pipeline has moved. A change between surveys can be datum,
tide, or survey uncertainty as easily as real movement.
- On confidential survey files in a public workspace. Inputs must be public,
synthetic, or approved for open-source use.
Inputs
| Input |
Meaning |
records |
Survey rows, each a mapping with depth_to_top_m and either kp_m or a coordinate pair |
depth_to_top_m |
Depth to top of pipe, positive-down or negative-up - the convention is detected and normalised |
seabed_depth_m |
Optional seabed depth at the same station; required for span and cover screening |
easting_m / northing_m |
Optional projected coordinates; used to derive KP when it is absent |
latitude_deg / longitude_deg |
Optional geographic coordinates; swapped column order is detected and corrected, then projected |
outer_diameter_m (row or argument) |
Pipe outer diameter, from the survey or supplied as a user override |
pipeline_id, survey_id |
Identifiers carried into the result for traceability |
start_kp_m, end_kp_m |
Optional section trim, for example between a flowline end and a hot-tap |
minimum_kp_spacing_m |
Resolution filter; closer stations are dropped |
outlier_threshold |
Robust sigma multiple above which a point is flagged as erroneous |
minimum_residual_m |
Physical floor on the flagging residual, so survey noise is never flagged |
smoothing_window |
Odd rolling-median window used as the smoothing reference |
span_gap_threshold_m |
Gap above seabed at which a station counts towards a span candidate |
change_threshold_m (compare) |
Depth change above which a repeat-survey interval is reported |
Outputs
| Output |
Contents |
SurveyProfileResult.points |
Retained, ordered, sign-normalised survey points |
smoothed_depth_m |
Rolling-median reference used for outlier detection |
flagged_points |
Erroneous points with KP, depth, residual and reason |
kp_profile_m / elevation_profile_m |
The profile itself, elevation being negated depth |
route_length_m, max_slope_deg, slope_warning |
Section length and slope screening (ok, watch, high) |
span_candidates |
Free-span candidates with start/end KP, length, max and mean gap |
exposed_length_m, longest_span_m |
Roll-up of the span candidates |
buried_intervals, minimum_cover_m |
Cover/burial intervals and the controlling minimum cover |
outer_diameter_m, outer_diameter_source |
Diameter and whether it came from survey, user_override or is missing |
depth_convention |
positive-down or negative-up as detected in the input |
raw_point_count, retained_point_count, rejected_point_count |
Filtering audit counts |
processing_log |
Every operation performed, in order |
data_gaps |
Missing evidence that a reviewer must close |
SurveyComparisonResult |
Common KP grid, per-station depth change, max lowering and lifting, changed intervals |
to_neqsim_elevation_profile |
Evenly spaced leg_positions_m and elevation_profile_m for a NeqSim pipe model |
Engineering Method
Sign convention before anything else. Survey depths appear both as positive
metres below sea level and as negative elevations. The convention is inferred from
the sign of every depth in the file and normalised to positive-down; mixed signs
are refused rather than guessed, because a silent sign error inverts every slope
in the profile.
Validity, then order, then resolution. Non-finite values and the common survey
null markers (-999, -999.25, -9999, 9999) are removed first. Rows are then
sorted on KP and non-increasing stations dropped, so the profile is strictly
monotonic. Only then is the resolution filter applied, keeping the first station
of every minimum_kp_spacing_m window plus both endpoints - decimating before
sorting would delete real stations and keep duplicates.
Erroneous points by robust residual. The depth series is compared against a
rolling median, and a point is flagged when its residual exceeds
outlier_threshold times a robust sigma derived from the median absolute residual
(1.4826 x MAD). A median reference and a MAD scale are used rather than a mean
and a standard deviation because a cluster of bad points would inflate both and
hide itself. Points within half a smoothing window of each end sit on a truncated
window, so their residual carries the local trend rather than an error; they are
excluded from assessment instead of being flagged. Flagged points are reported,
never silently deleted - a run of flags in one area is usually a survey-quality
signal, not noise - but they are excluded from the span and cover geometry,
because a depth that has been called wrong must not then be used to measure a gap.
Coordinates. Latitude/longitude columns are checked for swapped order, which
is detectable because a latitude cannot exceed 90 degrees, then projected onto a
local equirectangular frame about the first point. That is adequate for deriving
KP and screening geometry over a flowline and explicitly not adequate for
positioning work.
Spans and cover from one signed quantity. With both depths present,
cover = depth_to_top - seabed_depth in the positive-down frame. Positive cover
means the pipe top sits below the seabed and the station belongs to a burial
interval; negative cover is a gap, and consecutive stations whose gap exceeds
span_gap_threshold_m are grouped into a span candidate with its length, maximum
and mean gap. Grouping consecutive stations, rather than counting points, is what
makes the output comparable to a span list.
Repeat surveys on a common grid. Two processed surveys rarely share stations,
so both are linearly interpolated onto a common KP grid over their overlap and
differenced. Positive change means the pipe top sits deeper in the repeat survey.
Intervals exceeding change_threshold_m are grouped and labelled lowering or
lifting; the skill deliberately does not call this movement, because datum and
tide differences produce the same signature.
Python Usage Pattern
from pipeline_survey_processing import PipelineSurveyProcessor
processor = PipelineSurveyProcessor(
minimum_kp_spacing_m=5.0,
outlier_threshold=4.0,
minimum_residual_m=0.1,
smoothing_window=11,
span_gap_threshold_m=0.05,
)
records = [
{"kp_m": 0.0, "depth_to_top_m": -298.4, "seabed_depth_m": -298.2},
{"kp_m": 5.0, "depth_to_top_m": -298.2, "seabed_depth_m": -298.0},
{"kp_m": 10.0, "depth_to_top_m": -999.25}, # null marker, removed
{"kp_m": 15.0, "depth_to_top_m": -240.0, "seabed_depth_m": -297.7}, # flagged
{"kp_m": 20.0, "depth_to_top_m": -297.5, "seabed_depth_m": -297.3},
]
result = processor.process(
records=records,
pipeline_id="1192-Y-101",
survey_id="2010-survey",
start_kp_m=0.0,
end_kp_m=20.0,
outer_diameter_m=0.3239, # survey had no OD; recorded as a data gap
)
print(result.depth_convention) # negative-up
print(result.rejected_point_count)
print([point.kp_m for point in result.flagged_points])
print(result.span_candidates)
for entry in result.processing_log:
print(entry)
# Handoff into a NeqSim pipe model
handoff = PipelineSurveyProcessor.to_neqsim_elevation_profile(result, section_count=20)
# from neqsim import jneqsim
# pipe = jneqsim.process.equipment.pipeline.TwoFluidPipe("flowline", stream)
# pipe.setElevationProfile(handoff["elevation_profile_m"])
# Repeat-survey comparison
older = processor.process(records=records, pipeline_id="1192-Y-101", survey_id="2006-survey")
change = processor.compare(baseline=older, repeat=result, change_threshold_m=0.2)
print(change.max_lowering_m, change.max_lifting_m, change.changed_intervals)
Validation Checklist
- The depth convention reported by the result matches the survey report.
rejected_point_count is explainable: nulls, duplicates and resolution
filtering account for it, and no unexpected bulk rejection occurred.
- Flagged points have been inspected rather than deleted, and clusters of flags
are explained by a survey-quality note.
- The section trim matches the two structures the study is scoped to, and no
neighbouring line is included.
outer_diameter_source is survey, or the override is traced to a line list
or pipe class entry.
- Every entry in
data_gaps is closed or carried into the report as an open item.
- Span candidates are handed to a DNV-RP-F105 assessment before being quoted as
free spans.
- A repeat-survey change is reconciled against datum, tide and positioning basis
before it is described as pipeline movement.
- The processing log is stored with the profile in the task evidence.
Common Mistakes
- Decimating or smoothing before sorting on KP, which keeps duplicates and drops
real stations.
- Detecting outliers with a mean and standard deviation, so a cluster of bad
points raises the threshold and hides itself.
- Flagging on a robust sigma with no physical floor, so a smooth section reports
centimetre-level noise as erroneous.
- Treating flagged points as noise to delete; they are frequently the finding.
- Flagging on a robust sigma with no physical floor, so a very smooth section
reports centimetre-level survey noise as erroneous.
- Mixing positive-down depth and negative-up elevation in one file and letting
the model average across the sign change.
- Reporting the count of stations above the gap threshold as the number of spans
instead of grouping consecutive stations into intervals.
- Letting a point that has been flagged as erroneous set the maximum gap or the
minimum cover.
- Using the projected coordinates from this skill for positioning or datum work.
- Comparing two surveys station by station without interpolating onto a common
grid, so a KP offset appears as a depth change.
- Quoting a geometric span candidate as an acceptable or unacceptable span.
Limitations
- Screening only; it is not an as-built integrity assessment and it does not
establish adequacy or compliance.
- No geodetic datum transformation, tide correction or positioning-uncertainty
treatment.
- The smoothing reference is a rolling median, not the vendor spline that a
survey processing package applies; residuals will differ in detail.
- Points within half a smoothing window of each end are not assessed for
outliers, so an error at the very start or end of a section will not be flagged.
- A gap that spans a single station reports a length of zero, because span length
is measured between the first and last gap station.
- Span candidates carry no modal, VIV, fatigue or stability content.
- Embedment is inferred from cover only; no soil model, lay-effect or remoulding
is applied.
- The skill performs no file or network access; records are supplied by the caller.
References
- NeqSim: https://github.com/equinor/neqsim
- NeqSim Community Skills: https://github.com/equinor/neqsim-community-skills
- Companion skills:
neqsim-pipe-route-profile, neqsim-bathymetry-profile-screening,
neqsim-subsea-layout-geometry, neqsim-pressure-drop-screening
- NeqSim Java handoff:
neqsim.process.equipment.pipeline.PipeBeggsAndBrills,
neqsim.process.equipment.pipeline.TwoFluidPipe.setElevationProfile,
neqsim.process.engineering.calculation.DnvRpF105FreeSpanScreeningKernel,
neqsim.process.engineering.calculation.DnvRpF109OnBottomStabilityKernel,
neqsim.process.engineering.calculation.DnvRpF114PipeSoilInteractionScreeningKernel
- Public standards for the downstream assessment: DNV-RP-F105 (free spanning
pipelines), DNV-RP-F109 (on-bottom stability), DNV-RP-F114 (pipe-soil
interaction).
1---2name: neqsim-pipeline-survey-processing-33calculation_basis: "hybrid"4version: "0.1.0"5description: "Educational as-built pipeline survey processing: raw KP/depth/seabed/coordinate rows to a cleaned, sign-normalised pipeline profile with flagged points, free-span and cover candidates, repeat-survey comparison, processing log and a NeqSim-ready elevation profile. USE WHEN: a task needs a screening-level pipeline profile from survey or inspection data before DNV-RP-F105, F109, F114 or NeqSim thermal-hydraulic analysis."6last_verified: "2026-08-10"7requires:8 python_packages: []9 java_packages: []10 env: []11 network: []12metadata:13 source: https://skillmd.com/skills/equinor/neqsim-pipeline-survey-processing-314---1516# Pipeline Survey Processing1718A pipeline hydraulic or integrity model needs an elevation profile. The profile19almost always starts life as a survey file: thousands of rows of KP, depth to top20of pipe, seabed depth and coordinates, produced by a different discipline, in a21different datum, with null markers, duplicated stations, sections that belong to a22neighbouring line, and a handful of points that are simply wrong.2324The step from that file to a usable profile is where the numbers are decided, and25it is normally done by hand in a spreadsheet with no record of what was done. This26skill makes that step explicit and repeatable: every filter, sign flip, projection27and rejection is written into a processing log that travels with the result, so a28reviewer can see how the profile in front of them was produced.2930It stops at the profile. Free spans and burial intervals are reported as geometric31*candidates* for a qualified assessment - it does not perform modal, VIV, fatigue32or stability analysis.3334## When to Use3536- A survey or inspection export must become a pipeline elevation profile for a37 NeqSim pipe model.38- Erroneous points, null markers or duplicated stations need to be identified39 before a profile is trusted.40- Only part of a surveyed line is in scope, and the section between two41 structures must be extracted with the trim recorded.42- Free-span or cover candidates need to be located along KP as input to a43 DNV-RP-F105 or DNV-RP-F114 assessment.44- Two surveys of the same line, taken years apart, need a like-for-like change45 comparison.46- The survey lacks outer diameter and a value has to be supplied manually with47 the override recorded as a data gap.4849## When *Not* to Use5051- As a free-span assessment. Span candidates here are geometry only; modal52 response, VIV screening and fatigue belong to DNV-RP-F105 and to a qualified53 pipeline engineer.54- As a positioning or datum authority. This skill normalises a sign convention55 and projects coordinates for screening; it does not perform geodetic datum56 transformation and must not be used to reconcile survey datums.57- To conclude that a pipeline has moved. A change between surveys can be datum,58 tide, or survey uncertainty as easily as real movement.59- On confidential survey files in a public workspace. Inputs must be public,60 synthetic, or approved for open-source use.6162## Inputs6364| Input | Meaning |65|---|---|66| `records` | Survey rows, each a mapping with `depth_to_top_m` and either `kp_m` or a coordinate pair |67| `depth_to_top_m` | Depth to top of pipe, positive-down or negative-up - the convention is detected and normalised |68| `seabed_depth_m` | Optional seabed depth at the same station; required for span and cover screening |69| `easting_m` / `northing_m` | Optional projected coordinates; used to derive KP when it is absent |70| `latitude_deg` / `longitude_deg` | Optional geographic coordinates; swapped column order is detected and corrected, then projected |71| `outer_diameter_m` (row or argument) | Pipe outer diameter, from the survey or supplied as a user override |72| `pipeline_id`, `survey_id` | Identifiers carried into the result for traceability |73| `start_kp_m`, `end_kp_m` | Optional section trim, for example between a flowline end and a hot-tap |74| `minimum_kp_spacing_m` | Resolution filter; closer stations are dropped |75| `outlier_threshold` | Robust sigma multiple above which a point is flagged as erroneous |76| `minimum_residual_m` | Physical floor on the flagging residual, so survey noise is never flagged |77| `smoothing_window` | Odd rolling-median window used as the smoothing reference |78| `span_gap_threshold_m` | Gap above seabed at which a station counts towards a span candidate |79| `change_threshold_m` (compare) | Depth change above which a repeat-survey interval is reported |8081## Outputs8283| Output | Contents |84|---|---|85| `SurveyProfileResult.points` | Retained, ordered, sign-normalised survey points |86| `smoothed_depth_m` | Rolling-median reference used for outlier detection |87| `flagged_points` | Erroneous points with KP, depth, residual and reason |88| `kp_profile_m` / `elevation_profile_m` | The profile itself, elevation being negated depth |89| `route_length_m`, `max_slope_deg`, `slope_warning` | Section length and slope screening (`ok`, `watch`, `high`) |90| `span_candidates` | Free-span candidates with start/end KP, length, max and mean gap |91| `exposed_length_m`, `longest_span_m` | Roll-up of the span candidates |92| `buried_intervals`, `minimum_cover_m` | Cover/burial intervals and the controlling minimum cover |93| `outer_diameter_m`, `outer_diameter_source` | Diameter and whether it came from `survey`, `user_override` or is `missing` |94| `depth_convention` | `positive-down` or `negative-up` as detected in the input |95| `raw_point_count`, `retained_point_count`, `rejected_point_count` | Filtering audit counts |96| `processing_log` | Every operation performed, in order |97| `data_gaps` | Missing evidence that a reviewer must close |98| `SurveyComparisonResult` | Common KP grid, per-station depth change, max lowering and lifting, changed intervals |99| `to_neqsim_elevation_profile` | Evenly spaced `leg_positions_m` and `elevation_profile_m` for a NeqSim pipe model |100101## Engineering Method102103**Sign convention before anything else.** Survey depths appear both as positive104metres below sea level and as negative elevations. The convention is inferred from105the sign of every depth in the file and normalised to positive-down; mixed signs106are refused rather than guessed, because a silent sign error inverts every slope107in the profile.108109**Validity, then order, then resolution.** Non-finite values and the common survey110null markers (`-999`, `-999.25`, `-9999`, `9999`) are removed first. Rows are then111sorted on KP and non-increasing stations dropped, so the profile is strictly112monotonic. Only then is the resolution filter applied, keeping the first station113of every `minimum_kp_spacing_m` window plus both endpoints - decimating before114sorting would delete real stations and keep duplicates.115116**Erroneous points by robust residual.** The depth series is compared against a117rolling median, and a point is flagged when its residual exceeds118`outlier_threshold` times a robust sigma derived from the median absolute residual119(`1.4826 x MAD`). A median reference and a MAD scale are used rather than a mean120and a standard deviation because a cluster of bad points would inflate both and121hide itself. Points within half a smoothing window of each end sit on a truncated122window, so their residual carries the local trend rather than an error; they are123excluded from assessment instead of being flagged. Flagged points are reported,124never silently deleted - a run of flags in one area is usually a survey-quality125signal, not noise - but they are excluded from the span and cover geometry,126because a depth that has been called wrong must not then be used to measure a gap.127128**Coordinates.** Latitude/longitude columns are checked for swapped order, which129is detectable because a latitude cannot exceed 90 degrees, then projected onto a130local equirectangular frame about the first point. That is adequate for deriving131KP and screening geometry over a flowline and explicitly not adequate for132positioning work.133134**Spans and cover from one signed quantity.** With both depths present,135`cover = depth_to_top - seabed_depth` in the positive-down frame. Positive cover136means the pipe top sits below the seabed and the station belongs to a burial137interval; negative cover is a gap, and consecutive stations whose gap exceeds138`span_gap_threshold_m` are grouped into a span candidate with its length, maximum139and mean gap. Grouping consecutive stations, rather than counting points, is what140makes the output comparable to a span list.141142**Repeat surveys on a common grid.** Two processed surveys rarely share stations,143so both are linearly interpolated onto a common KP grid over their overlap and144differenced. Positive change means the pipe top sits deeper in the repeat survey.145Intervals exceeding `change_threshold_m` are grouped and labelled `lowering` or146`lifting`; the skill deliberately does not call this movement, because datum and147tide differences produce the same signature.148149## Python Usage Pattern150151```python152from pipeline_survey_processing import PipelineSurveyProcessor153154processor = PipelineSurveyProcessor(155 minimum_kp_spacing_m=5.0,156 outlier_threshold=4.0,157 minimum_residual_m=0.1,158 smoothing_window=11,159 span_gap_threshold_m=0.05,160)161162records = [163 {"kp_m": 0.0, "depth_to_top_m": -298.4, "seabed_depth_m": -298.2},164 {"kp_m": 5.0, "depth_to_top_m": -298.2, "seabed_depth_m": -298.0},165 {"kp_m": 10.0, "depth_to_top_m": -999.25}, # null marker, removed166 {"kp_m": 15.0, "depth_to_top_m": -240.0, "seabed_depth_m": -297.7}, # flagged167 {"kp_m": 20.0, "depth_to_top_m": -297.5, "seabed_depth_m": -297.3},168]169170result = processor.process(171 records=records,172 pipeline_id="1192-Y-101",173 survey_id="2010-survey",174 start_kp_m=0.0,175 end_kp_m=20.0,176 outer_diameter_m=0.3239, # survey had no OD; recorded as a data gap177)178179print(result.depth_convention) # negative-up180print(result.rejected_point_count)181print([point.kp_m for point in result.flagged_points])182print(result.span_candidates)183for entry in result.processing_log:184 print(entry)185186# Handoff into a NeqSim pipe model187handoff = PipelineSurveyProcessor.to_neqsim_elevation_profile(result, section_count=20)188# from neqsim import jneqsim189# pipe = jneqsim.process.equipment.pipeline.TwoFluidPipe("flowline", stream)190# pipe.setElevationProfile(handoff["elevation_profile_m"])191192# Repeat-survey comparison193older = processor.process(records=records, pipeline_id="1192-Y-101", survey_id="2006-survey")194change = processor.compare(baseline=older, repeat=result, change_threshold_m=0.2)195print(change.max_lowering_m, change.max_lifting_m, change.changed_intervals)196```197198## Validation Checklist199200- The depth convention reported by the result matches the survey report.201- `rejected_point_count` is explainable: nulls, duplicates and resolution202 filtering account for it, and no unexpected bulk rejection occurred.203- Flagged points have been inspected rather than deleted, and clusters of flags204 are explained by a survey-quality note.205- The section trim matches the two structures the study is scoped to, and no206 neighbouring line is included.207- `outer_diameter_source` is `survey`, or the override is traced to a line list208 or pipe class entry.209- Every entry in `data_gaps` is closed or carried into the report as an open item.210- Span candidates are handed to a DNV-RP-F105 assessment before being quoted as211 free spans.212- A repeat-survey change is reconciled against datum, tide and positioning basis213 before it is described as pipeline movement.214- The processing log is stored with the profile in the task evidence.215216## Common Mistakes217218- Decimating or smoothing before sorting on KP, which keeps duplicates and drops219 real stations.220- Detecting outliers with a mean and standard deviation, so a cluster of bad221 points raises the threshold and hides itself.222- Flagging on a robust sigma with no physical floor, so a smooth section reports223 centimetre-level noise as erroneous.224- Treating flagged points as noise to delete; they are frequently the finding.225- Flagging on a robust sigma with no physical floor, so a very smooth section226 reports centimetre-level survey noise as erroneous.227- Mixing positive-down depth and negative-up elevation in one file and letting228 the model average across the sign change.229- Reporting the count of stations above the gap threshold as the number of spans230 instead of grouping consecutive stations into intervals.231- Letting a point that has been flagged as erroneous set the maximum gap or the232 minimum cover.233- Using the projected coordinates from this skill for positioning or datum work.234- Comparing two surveys station by station without interpolating onto a common235 grid, so a KP offset appears as a depth change.236- Quoting a geometric span candidate as an acceptable or unacceptable span.237238## Limitations239240- Screening only; it is not an as-built integrity assessment and it does not241 establish adequacy or compliance.242- No geodetic datum transformation, tide correction or positioning-uncertainty243 treatment.244- The smoothing reference is a rolling median, not the vendor spline that a245 survey processing package applies; residuals will differ in detail.246- Points within half a smoothing window of each end are not assessed for247 outliers, so an error at the very start or end of a section will not be flagged.248- A gap that spans a single station reports a length of zero, because span length249 is measured between the first and last gap station.250- Span candidates carry no modal, VIV, fatigue or stability content.251- Embedment is inferred from cover only; no soil model, lay-effect or remoulding252 is applied.253- The skill performs no file or network access; records are supplied by the caller.254255## References256257- NeqSim: https://github.com/equinor/neqsim258- NeqSim Community Skills: https://github.com/equinor/neqsim-community-skills259- Companion skills: `neqsim-pipe-route-profile`, `neqsim-bathymetry-profile-screening`,260 `neqsim-subsea-layout-geometry`, `neqsim-pressure-drop-screening`261- NeqSim Java handoff: `neqsim.process.equipment.pipeline.PipeBeggsAndBrills`,262 `neqsim.process.equipment.pipeline.TwoFluidPipe.setElevationProfile`,263 `neqsim.process.engineering.calculation.DnvRpF105FreeSpanScreeningKernel`,264 `neqsim.process.engineering.calculation.DnvRpF109OnBottomStabilityKernel`,265 `neqsim.process.engineering.calculation.DnvRpF114PipeSoilInteractionScreeningKernel`266- Public standards for the downstream assessment: DNV-RP-F105 (free spanning267 pipelines), DNV-RP-F109 (on-bottom stability), DNV-RP-F114 (pipe-soil268 interaction).