# Site page text > Static main content from the indexed pages. Follow each URL for interactive results and source references. ## About AceEngineer | Engineering analysis and AI automation URL: https://www.aceengineer.com/about.html Description: Houston engineering analysis and AI automation. Contact us to discuss a separately agreed scope; inspect the public code and pinned catalogue. # Engineering analysis and AI automation AceEngineer is a Houston engineering firm that runs its analysis as automated, checked workflows. AI automation and agentic workflows are topics for discussion under a separately agreed scope. The engineering code is public: of 196 modules in digitalmodel, worldenergydata and assetutilities, 35 pass their cited checks (catalogue run 2026-10-17). The pinned catalogue records the evidence available for its classifications. 35 of 196 Modules passing cited checks Catalogue run 2026-10-17 15 DNV-RP-C203 classes Air, CP, free corrosion 8 Design Codes DNV, API, ABS, BS, Norsok 245 Curated Datasets BSEE, metocean, production, HSE ## The AceEngineer Story Analytical & Computational Engineering was founded in 2010 in Houston, Texas, with a clear mission: eliminate the repetitive manual work that consumes offshore engineering teams. 25+ years of deepwater engineering—spanning the Gulf of Mexico, North Sea, and global projects—a pattern became clear. The same OrcaFlex sensitivity studies, the same fatigue calculations, the same standards lookups were being repeated project after project, consuming hundreds of engineer-hours that could be spent on actual engineering judgment. AceEngineer was built to solve this. The public repositories contain code for recurring engineering workflows. The catalogue records 35 of 196 modules passing their cited checks. The result: engineering firms send a design matrix and receive batch results with recorded inputs for engineering review. ## How We Work AI and agentic workflows: contact us to discuss a separately agreed scope. ### 1. You Define the Scope Send your design matrix, baseline models, and analysis requirements. We establish the parameter space and acceptance criteria together. ### 2. We Automate the Execution Our automation pipelines generate models, run batch analyses (50+ configurations overnight), extract results, and compile standardized deliverables with recorded analysis inputs. ### 3. You Review the Results You receive results and recorded inputs for engineering review, with standards references and methodology documented where applicable. ## Who We Serve ### Offshore Engineering Firms Mid-market firms (10-50 engineers) who run OrcaFlex and AQWA manually for every project. We eliminate the repetitive analysis bottleneck so your senior engineers focus on engineering judgment. ### EPC Contractors Installation and fabrication contractors who need rapid weather window analysis, lift studies, and installation pre-engineering without dedicated in-house scripting capability. ### Classification Societies Organizations exploring digital verification services who need computational tools with documented inputs, standards references and methodology for engineering review. ### Drilling Contractors Riser analysis and operability envelopes for drilling risers are provided for drilling contractors. The client receives the riser analysis and operability envelope for the stated scope. ## Technology AceEngineer's engineering platform is built on industry-standard tools: OrcaFlex API for marine dynamic analysis, AQWA for hydrodynamics, Python and Polars for high-performance data processing, and open-source computational libraries for reproducible engineering. The public repositories contain engineering analysis, data processing and reporting workflows. The catalogue distinguishes the checks recorded for each module. ## Module checks 35 of 196 modules pass their cited checks (catalogue run 2026-10-17). OUTWARD requires source class CHECKED, an original clean module run and a passed cited-file receipt. These catalogue classifications do not establish a service qualification or delivery commitment. Source: specialists catalogue, criteria revision 2026-10-17-third-review-engineering-reference, pinned revision ba4f4bd3fd0eec07281643d4c8accbed923945a4, preserved by the merged catalogue update. Count and source summary. ## How we run AI agents on engineering work The methodology pages describe planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. Orchestrator and worker agents Independent review Enforced checks Multi-agent parity Compound engineering Compliance dashboard Work so far · AI automation · Small-business automation ## Founder Vamsee Achanta, P.E., Principal Engineer — 25+ years of offshore and deepwater engineering experience spanning riser design, mooring systems, fatigue analysis, and structural integrity assessment. Vamsee founded AceEngineer to bridge the gap between engineering expertise and computational automation, turning deep domain knowledge into scalable, repeatable workflows. ## Standards We Work With The applicable standards and scope are stated for each analysis. DNV-RP-C203 API RP 2A BS 7608 ABS Norsok IEC 61400-3 ASME B31.8 API RP 2RD Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## AI automation and agentic workflows | AceEngineer URL: https://www.aceengineer.com/ai-automation/ Description: AI automation and agentic workflows: planning, checks and public code to inspect. Engineering and small-business topics for a separately agreed scope. # AI automation and agentic workflows AI automation and agentic workflows for engineering and small-business administration. Contact us to discuss a separately agreed scope. ## Work on your own computer We can do the work and set everything up on your own computer, or deliver the workflow to your computer, so your information stays confidential on your side. ## Planning, tests and review We agree the inputs, scope and acceptance criteria, divide the work into focused tasks, and check the results with tests and independent review. ## How we run AI agents on engineering work The methodology pages describe planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. Orchestrator and worker agents Independent review Enforced checks Multi-agent parity Compound engineering Compliance dashboard ## Work so far digitalmodel contains offshore analysis and calculation workflows. worldenergydata contains public energy-data processing and reports. assetutilities contains reusable data-processing and administrative automation tools. Published datasets are available through Hugging Face. ## Module checks 35 of 196 modules pass their cited checks (catalogue run 2026-10-17). Read the criteria and pinned source revision. Engineering workflows · Small-business automation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## AI-Native Structural Analysis | AceEngineer Engineering Blog URL: https://www.aceengineer.com/blog/ai-native-structural-analysis.html Description: Explore AI-native structural analysis and how machine learning is transforming traditional FEA. Compare computational performance and understand why this matters for engineering decisions. # AI-Native Structural Analysis: Why Traditional FEA is Changing Published: January 12, 2025 | By: Vamsee Achanta, P.E. | Reading Time: 8 minutes | Category: Computational Methods Abstract: Finite Element Analysis (FEA) has been the gold standard for structural engineering for nearly 50 years. But a new paradigm—AI-native structural analysis—is emerging. This article explores what AI-native means, why it matters for engineering decisions, real-world applications, and how it differs fundamentally from traditional approaches. ## The Problem with Traditional FEA Traditional finite element analysis has served the engineering industry well, but it comes with well-known limitations: Computational Cost: Complex models with high fidelity require significant computational resources (days or weeks) Expert Dependency: Requires highly trained engineers for mesh generation, boundary condition definition, and result interpretation Iterative Inefficiency: Design optimization requires running multiple simulations sequentially Validation Uncertainty: Model accuracy depends on assumptions that may not reflect reality Knowledge Silos: Historical simulation data and insights are difficult to systematically apply to new problems For complex problems—like multi-physics simulations, fatigue prediction, or design optimization under uncertainty—traditional FEA becomes prohibitively expensive in both time and resources. ## What is AI-Native Structural Analysis? AI-native structural analysis uses machine learning and advanced algorithms as the primary computational approach, with traditional physics-based methods as validation tools rather than the primary solver. Key characteristics: Data-Driven: Learns patterns from existing simulations, experiments, and operational data Fast Inference: Can predict structural behavior in milliseconds to seconds Uncertainty Quantification: Provides confidence intervals and probability distributions, not just point estimates Implicit Knowledge Capture: Encodes decades of engineering experience and validated methodologies Continuous Improvement: Models improve with new data and feedback Important Distinction: AI-native doesn't mean "no physics." Rather, physics-based validation becomes the test, while machine learning becomes the efficient solver. This is fundamentally different from purely black-box AI approaches. ## Real-World Applications ### 1. Offshore Platform Structural Analysis Traditional approach: Months of detailed FEA for complex platform designs, with dozens of design iterations requiring reanalysis. AI-native approach: Train models on existing platform designs and simulation databases. New designs can be analyzed in minutes, with uncertainty quantification built-in. Optimization across 100+ design parameters becomes computationally feasible. Results: 10-50x faster analysis time Better exploration of design space Quantified confidence in predictions Validation against known good designs and experimental data ### 2. Fatigue Life Prediction Predicting fatigue failure requires understanding stress cycles, material properties, environmental factors, and complex failure mechanisms. Traditional methods rely on empirical curves and safety factors. AI-native approach: Machine learning models trained on experimental fatigue data can predict life with higher accuracy while accounting for interactions between variables. New materials and conditions can be incorporated as data becomes available. Results: Higher accuracy fatigue predictions Faster assessment of new materials Better handling of combined loading conditions Continuous improvement as test data accumulates ### 3. Design Optimization Optimizing designs under multiple constraints (weight, strength, cost, manufacturability) typically requires thousands of FEA runs—prohibitively expensive with traditional methods. AI-native approach: Surrogate models trained on a small set of FEA runs can explore the design space efficiently. Gradient-based and evolutionary optimization algorithms can navigate complex design spaces rapidly. Results: 10-100x reduction in required FEA runs Better global optimization (not just local minima) Multi-objective optimization becomes practical Exploration of unconventional designs ## Comparison: Traditional FEA vs AI-Native Aspect Traditional FEA AI-Native Analysis Analysis Speed Hours to weeks per model Milliseconds to seconds Design Iterations 10-20 iterations practical 1,000+ iterations possible Optimization Limited by compute cost Computationally feasible for 100+ parameters Uncertainty Safety factors (conservative estimates) Probability distributions (quantified risk) New Materials/Conditions Requires new model setup Can incorporate new data incrementally Knowledge Reuse Limited to documented past projects Automatically learns from all historical data Scalability Limited by mesh quality and solver capacity Scales with data, not model complexity Validation Experimental correlation required Validated against FEA + experiments + field data ## Validation and Industry Standards The critical question from engineering evaluators: "How do you validate AI predictions?" Our validation approach uses three-tiered verification: Analytical Verification: Compare AI predictions against known analytical solutions and benchmark problems Numerical Validation: Correlate predictions with detailed FEA on subset of representative problems Experimental Correlation: Compare model predictions to actual experimental data and field measurements This approach ensures compliance with industry standards (API 579, DNV-GL, ISO, ASME) while providing higher accuracy than traditional methods alone. Why This Matters: Traditional FEA cannot be run on every design variant. AI-native methods enable continuous validation across the entire design space while providing quantified confidence metrics. ## Addressing Skepticism Engineering leaders often ask: "Can we really trust AI for critical structures?" The answer: When properly validated and deployed, AI-native methods are not less trustworthy—they're differently trustworthy. They quantify uncertainty explicitly, rather than hiding it in safety factors. Key trust-building practices: Transparent Methodology: Document the data, training process, validation tests, and assumptions Open-Source Tools: Where possible, make code and models publicly available for peer review Industry Validation: Submit methods to independent validation through industry bodies Continuous Monitoring: Track prediction accuracy on new data and update models as needed Failure Analysis: When predictions diverge from reality, investigate and improve models ## The Future of Structural Analysis AI-native methods are not a replacement for traditional FEA—they're a complementary approach that solves different problems: Design Exploration: AI-native (fast, exploratory) Final Validation: Traditional FEA (detailed, physics-based verification) Uncertainty Quantification: AI-native (statistical framework) Novel Problems: Traditional FEA (when data insufficient) The future is hybrid: AI-native for rapid iteration and design exploration, traditional methods for final validation and novel scenarios. This combination provides both speed and confidence. ## What This Means for Engineering Teams If you're evaluating engineering consultants or building internal capabilities: Ask about AI expertise: Do they understand machine learning? Can they validate models rigorously? Request transparency: Can they explain their methods and show validation evidence? Look for industry collaboration: Are they working with standards bodies or universities to validate approaches? Evaluate code quality: Do they publish open-source tools? This indicates confidence and enables peer review Check track record: Have they successfully applied AI methods to problems similar to yours? ## Next Steps We're building open-source tools and publishing detailed case studies on AI-native structural analysis. Visit our GitHub to explore our implementations, or contact us to discuss how AI-native methods could benefit your projects. ### About the Author Vamsee Achanta, P.E. is an engineer specializing in computational methods, machine learning applications in engineering, and open-source tools. With experience in offshore, subsea, and energy infrastructure projects, he focuses on making advanced analytical methods accessible and transparent. Read more about AceEngineer or view code on GitHub ### Interested in AI-Native Engineering Methods? We're building tools and documentation for computational engineering. Subscribe to our blog for new articles, follow our GitHub for code examples, or contact us to discuss your specific challenges. Back to Blog Get in Touch ## CFD for Offshore Engineering: From Wave Loading to VIV Analysis | AceEngineer Engineering Blog URL: https://www.aceengineer.com/blog/cfd-offshore-engineering.html Description: Practical guide to computational fluid dynamics (CFD) for offshore engineering. Covers wave loading, VIV analysis, current modeling, and AI-enhanced approaches for platforms and subsea systems. # CFD for Offshore Engineering: From Wave Loading to VIV Analysis Published: January 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 14 minutes | Category: Computational Methods Computational Fluid Dynamics (CFD) has become essential for offshore engineering challenges that empirical formulas cannot address. From complex wave-structure interactions to vortex-induced vibration prediction, CFD provides the detailed flow field information needed for reliable design. This practical guide covers when and how to apply CFD effectively in offshore projects. ## When CFD Adds Value Not every hydrodynamic problem requires CFD. Morison's equation handles many wave loading calculations adequately, and empirical VIV predictions work well for standard configurations. CFD becomes valuable when: Complex geometry: Multi-member structures with significant wave diffraction and shielding Flow regime uncertainty: Keulegan-Carpenter numbers where empirical coefficients are unreliable Current-wave interaction: Coupled environments where superposition doesn't capture physics Novel configurations: Geometries outside the empirical database (floating wind foundations, subsea templates) Detailed flow features: Wake characterization, free surface effects, green water loading VIV in complex flows: Sheared currents, tandem arrangements, variable geometry ### CFD Decision Framework Use empirical methods when: Standard jacket/platform geometry, well-characterized flow regimes, preliminary design Use CFD when: Complex geometry, regulatory scrutiny on specific loads, novel configurations, VIV mitigation design ## Key Application Areas ### Wave Loading Diffraction around large members Wave run-up on columns Green water on decks Air gap exceedance ### Current Loading Drag on complex frames Wake interference effects Shielding coefficients Current blockage ### VIV Analysis Lock-in prediction Multi-mode response Suppression device design Fatigue damage assessment ### Operational Analysis Vessel approach/departure Crane operations Offloading operations Installation analysis ## CFD Fundamentals for Offshore Applications ### Governing Equations Offshore CFD typically solves the Reynolds-Averaged Navier-Stokes (RANS) equations with turbulence closure: Continuity: div(u) = 0 Momentum: du/dt + (u . grad)u = -grad(p)/rho + nu*laplacian(u) + g + f_turbulence ### Turbulence Modeling Turbulence model selection significantly affects results accuracy and computational cost: Model Best Applications Limitations Relative Cost k-epsilon Steady flows, attached boundary layers Poor separation prediction 1x (baseline) k-omega SST Separated flows, adverse pressure gradients Requires fine near-wall mesh 1.2x DES/DDES VIV, wake-dominated flows Time-dependent, mesh-sensitive 10-50x LES Research, detailed turbulence Very high resolution required 100-1000x For most offshore engineering applications, k-omega SST provides the best balance of accuracy and cost. Detached Eddy Simulation (DES) is increasingly used for VIV studies where wake dynamics dominate. ## Vortex-Induced Vibration (VIV) Analysis VIV remains one of the most challenging problems in offshore engineering. CFD provides detailed insight into the underlying physics that empirical methods cannot capture. ### The VIV Challenge When current flows past a cylindrical structure, vortices shed alternately from each side, creating oscillating lift forces. If shedding frequency approaches a structural natural frequency, resonance (lock-in) amplifies vibrations dramatically: Strouhal Relationship: f_s = St x U / D Lock-in occurs when: f_s approximately equals f_n (structural natural frequency) where St is approximately 0.2 for circular cylinders in subcritical flow ### CFD Approach for VIV VIV CFD requires capturing the two-way coupling between fluid and structure: #### Step 1: Structural Model Define structural properties (mass, stiffness, damping) and natural frequencies. For risers, this typically requires modal analysis of the full system. #### Step 2: Flow Simulation Setup Create 2D or 3D domain around cylinder section. Use DES or LES turbulence modeling to capture wake dynamics. Mesh must resolve boundary layer (y+ less than 1). #### Step 3: Fluid-Structure Coupling Implement moving mesh or overset grid to accommodate cylinder motion. Update mesh each timestep based on structural response. #### Step 4: Response Extraction Run simulation through multiple vortex shedding cycles. Extract displacement amplitudes, lock-in ranges, and fatigue-relevant stress cycles. ### VIV Suppression Device Design CFD excels at optimizing VIV suppression devices where empirical data is limited: Device Type Mechanism CFD Value Typical Reduction Helical strakes Disrupts coherent vortex shedding Optimize pitch, height, number of starts 70-90% Fairings Streamlines wake, reduces drag Optimize profile, weathervaning behavior 80-95% Splitter plates Stabilizes wake, prevents alternating shedding Optimize length, attachment 50-70% Surface roughness Promotes early transition, reduces lift Optimize pattern, coverage 30-50% ## Practical Implementation Guidance ### Software Selection Software Strengths Typical Applications OpenFOAM Open-source, customizable, waves2Foam library Research, wave loading, custom physics STAR-CCM+ Integrated workflow, overset meshing, VIV tools Industry standard, VIV, FSI ANSYS Fluent Established solver, dynamic meshing General purpose, wave-structure interaction OrcaFlex + CFD Coupled time-domain, line dynamics Risers, moorings with CFD coefficients ### Verification and Validation CFD results require systematic V&V before use in design: Mesh convergence: Demonstrate grid-independent results using Richardson extrapolation Timestep study: Verify temporal resolution captures relevant physics Benchmark validation: Compare against experimental data for similar configurations Code-to-code: Cross-check results between different CFD packages #### Validation Data Sources MARIN experiments: Wave basin tests on platforms and vessels SINTEF Ocean: VIV model tests and field data OTC papers: Published experimental campaigns JIP results: Industry joint projects (with access) ## Conclusion CFD has matured into a reliable tool for offshore engineering challenges that exceed empirical method capabilities. The key to successful application is knowing when CFD adds value, selecting appropriate modeling approaches, and rigorously validating results against available data. AI-enhanced workflows are expanding CFD accessibility, enabling rapid parametric studies and uncertainty quantification that support reliability-based design. As computational power continues to increase, expect CFD to play an expanding role in offshore engineering practice. ### Related Resources AI-Native Structural Analysis Machine Learning for Fatigue Life Prediction Digital Twins for Offshore Asset Integrity Navigating Offshore Engineering Standards S-N Curve Fatigue Life Calculator ### About the Author Vamsee Achanta, P.E., is a structural engineer specializing in computational methods for offshore and marine engineering. With experience in CFD, FEA, and AI-enhanced analysis, he helps organizations apply advanced simulation techniques to complex engineering challenges. Read more about AceEngineer or view code on GitHub ## Digital Twins for Offshore Asset Integrity: From Concept to Implementation - AceEngineer URL: https://www.aceengineer.com/blog/digital-twins-offshore-assets.html Description: How digital twins transform offshore asset integrity management. Learn practical approaches to creating physics-based digital replicas for structural monitoring, predictive maintenance, and life extension. # Digital Twins for Offshore Asset Integrity: From Concept to Implementation By Vamsee Achanta, P.E. | January 14, 2026 | 12 min read | Digital Engineering Digital twins have evolved from marketing buzzword to essential technology for offshore asset integrity management. This article explores what constitutes a genuine physics-based digital twin, how to implement one effectively, and the real-world benefits for structural monitoring, predictive maintenance, and life extension decisions. ## What Is a Digital Twin? (And What It Is Not) The term "digital twin" has been applied to everything from simple 3D models to complex AI systems. For offshore structural engineering, a useful definition focuses on three essential characteristics: ### Essential Digital Twin Characteristics Physics-Based Foundation: The model captures actual structural behavior through validated engineering principles, not just geometric representation Data Integration: Real-time or near-real-time connection to measured data from sensors, inspections, and operational systems Predictive Capability: The ability to forecast future states, remaining life, and failure probabilities based on integrated physics and data A static 3D CAD model is not a digital twin. A database of inspection reports is not a digital twin. Even a sophisticated finite element model, without data integration and predictive updating, is not a digital twin in the operational sense. ### The Digital Twin Maturity Spectrum Organizations typically progress through maturity levels when implementing digital twins: 1 Digital Model: Static representation of as-designed or as-built geometry. No data connection. Manual updates only. 2 Digital Shadow: One-way data flow from physical asset to digital model. Historical data visualization. No predictive capability. 3 Digital Twin: Bi-directional data flow. Physics-based models updated with measured data. Predictive analytics for remaining life and maintenance planning. 4 Autonomous Digital Twin: Self-calibrating models with machine learning. Automated anomaly detection. Decision support with uncertainty quantification. ## Architecture of an Offshore Digital Twin A functional digital twin for offshore asset integrity requires several integrated layers: ### Digital Twin Architecture Layers User Interface Layer Dashboards, Alerts, Reports, Decision Support Analytics Layer ML Models, Anomaly Detection, Remaining Life Prediction Physics Engine Layer FEA Models, Fatigue Analysis, Load Calculation, Corrosion Models Data Integration Layer Sensors, SCADA, Inspection Records, Metocean Data ### Analytics Layer The analytics layer adds intelligence to physics-based results: #### Anomaly Detection Identify sensor drift, unusual loading events, or structural changes that deviate from expected behavior patterns. #### Remaining Life Prediction Combine fatigue damage accumulation with probabilistic methods to forecast when maintenance or replacement is needed. #### Model Updating Bayesian calibration of model parameters based on measured data to reduce prediction uncertainty over time. #### What-If Scenarios Evaluate impact of operational changes, extreme weather events, or life extension scenarios. ## Implementation Considerations ### Starting Point: Where to Begin A common mistake is attempting to build a comprehensive digital twin from day one. More successful implementations start with a focused use case: Identify the critical decision: What question needs better data? Examples: "When should we inspect this joint?" or "Can we extend platform life by 5 years?" Map data requirements: What data is needed to answer the question? What is already available? What gaps exist? Define minimum viable model: What is the simplest physics model that provides useful insight? Avoid over-engineering. Establish validation approach: How will model predictions be verified against reality? Plan for iteration: Build in mechanisms to improve the model as more data becomes available. #### Common Implementation Pitfalls Sensor proliferation without purpose: Installing sensors without clear use cases leads to data overload and maintenance burden Model complexity outpacing data: Sophisticated models are meaningless without data to calibrate and validate them Ignoring uncertainty: Digital twin predictions must include confidence bounds to support risk-based decisions Vendor lock-in: Proprietary platforms can limit flexibility and long-term value ## Business Value and ROI Digital twin implementations must demonstrate tangible value. Key benefit categories include: ### Inspection Optimization Risk-based inspection planning guided by digital twin predictions can reduce inspection scope while improving coverage of high-risk areas. Typical results: 20-40% reduction in inspection costs with improved defect detection. ### Maintenance Planning Predictive maintenance based on actual condition rather than calendar schedules. Moving from time-based to condition-based maintenance can reduce unplanned downtime by 30-50%. ### Life Extension Decisions Quantified remaining life estimates support informed decisions about continued operation, required modifications, or decommissioning timing. For aging assets, this can enable years of additional production. #### ROI Example: Jacket Platform Digital Twin A North Sea jacket platform implemented a fatigue-focused digital twin with 12 strain gauges and integrated metocean data. Results over 3 years: Inspection scope reduced 35% through risk-based prioritization Two critical joints identified for proactive reinforcement before failure Life extension case supported with quantified remaining fatigue life Estimated NPV benefit: $4.2M against implementation cost of $800K ## Conclusion Digital twins represent a genuine advancement in offshore asset integrity management, but only when implemented with engineering rigor. The key is starting with physics-based models, integrating quality data, and maintaining focus on decisions that matter. The technology is mature enough for production deployment on offshore structures. The challenge is not technical capability but organizational readiness: establishing data infrastructure, developing internal expertise, and integrating digital insights into established decision-making processes. For operators managing aging offshore assets, the question is not whether to implement digital twins, but how to do so in a way that delivers reliable value while building toward more sophisticated capabilities over time. ### About the Author Vamsee Achanta, P.E. is an engineer specializing in offshore structural analysis, asset integrity management, and computational engineering. With experience implementing structural monitoring systems and predictive maintenance strategies for fixed and floating offshore structures, he focuses on practical digital twin applications that deliver measurable value. Read more about AceEngineer | Try our Fatigue Calculator | View code on GitHub ### Related Articles Machine Learning for Fatigue Life Prediction Navigating Offshore Engineering Standards Python Engineering Automation View All Blog Posts ## Energy Data Automation Pipelines | AceEngineer Blog URL: https://www.aceengineer.com/blog/energy-data-automation-pipelines.html Description: Energy data automation pipelines organise manual collection and data-quality checks. Python ETL architecture, data quality monitoring, and ROI calculation for oil and gas data workflows. # Energy Data Automation Pipelines: From Manual Workflows to Reproducible Analysis Author: Vamsee Achanta, P.E. | Published: February 2026 | Reading Time: 16 minutes | Category: Data Engineering Abstract: Energy companies spend millions annually on manual data collection, processing, and quality control—yet still face data delays, errors, and reproducibility challenges. Automated data pipelines combine collection, quality checks and repeatable processing. This article presents the business case for automation, practical ETL architecture patterns, Python implementation examples, and data quality monitoring frameworks for oil and gas data workflows. ## The Hidden Cost of Manual Data Workflows A typical energy company's data workflow involves analysts manually: Downloading data: Logging into 5-10 different portals (BSEE, state agencies, operator websites) to download monthly files Copying and pasting: Transferring data from PDFs, spreadsheets, and databases into analysis templates Reformatting: Standardizing units, column names, and date formats across sources Quality checking: Manually identifying outliers, missing values, and inconsistencies Documenting: Emailing spreadsheets with version numbers and change descriptions For a mid-sized energy company, this manual work translates to: Activity Hours/Month Annual Cost (FTE @ $120k) Production data collection (BSEE, states) 40 $28,800 Well data updates (permits, completions) 30 $21,600 Pricing and market data compilation 20 $14,400 HSE incident data aggregation 15 $10,800 Data quality fixes and reconciliation 35 $25,200 Total 140 hours/month $100,800/year Business Reality: The true cost includes opportunity cost—analysts spending 30-40% of their time on data wrangling can't focus on high-value analysis, decision support, or process improvement. Automation doesn't just save money; it unlocks strategic capacity. ## ETL Pipeline Architecture ### Three-Layer Architecture Production energy data pipelines follow a standardized three-layer pattern: ┌─────────────────────────────────────────────────────────┐ │ Layer 1: Extraction (Data Sources) │ │ • BSEE public data portal (monthly ZIP files) │ │ • State regulatory APIs (Texas RRC, Louisiana DNR) │ │ • Operator portals (via web scraping or API) │ │ • Third-party vendors (IHS, S&P, Wood Mackenzie) │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ Layer 2: Transformation (Data Processing) │ │ • Schema standardization │ │ • Unit conversions (MCF → MMBTU, bbl → m³) │ │ • Quality validation and outlier detection │ │ • Entity resolution (lease matching, well correlation) │ │ • Feature engineering (water depth class, play type) │ └─────────────────────────────────────────────────────────┘ ↓ ┌─────────────────────────────────────────────────────────┐ │ Layer 3: Loading (Data Storage) │ │ • Raw data lake (Parquet, object storage) │ │ • Relational database (PostgreSQL, analytics) │ │ • Data warehouse (Snowflake, reporting) │ │ • Time-series database (InfluxDB, real-time metrics) │ └─────────────────────────────────────────────────────────┘ ### Orchestration Framework Automated pipelines require orchestration for scheduling, dependency management, and error handling: from prefect import flow, task from datetime import datetime import pandas as pd @task(retries=3, retry_delay_seconds=300) def extract_bsee_production(year, month): """ Extract BSEE production data with automatic retry. Handles transient network errors and rate limiting. """ # Implementation from previous article pass @task def validate_data_quality(df, rules): """ Validate data against quality rules. Returns validation report and clean DataFrame. """ issues = [] # Check for required columns required_cols = rules['required_columns'] missing_cols = set(required_cols) - set(df.columns) if missing_cols: issues.append({ 'severity': 'critical', 'message': f"Missing columns: {missing_cols}" }) # Check for null values in critical fields for col in rules['no_nulls']: null_count = df[col].isna().sum() if null_count > 0: issues.append({ 'severity': 'warning', 'column': col, 'message': f"{null_count} null values in {col}" }) # Check for outliers for col, bounds in rules['outlier_bounds'].items(): outliers = ( (df[col] < bounds['min']) | (df[col] > bounds['max']) ).sum() if outliers > 0: issues.append({ 'severity': 'warning', 'column': col, 'message': f"{outliers} outliers in {col}" }) return df, issues @task def load_to_database(df, table_name, db_url): """ Load DataFrame to PostgreSQL with upsert logic. """ from sqlalchemy import create_engine engine = create_engine(db_url) # Upsert: update existing, insert new df.to_sql( table_name, engine, if_exists='append', index=False, method='multi' ) return len(df) @flow(name="BSEE Production ETL") def bsee_production_pipeline(year, month): """ Complete ETL pipeline for BSEE production data. Orchestrates extraction, validation, and loading with error handling and logging. """ # Extract df_raw = extract_bsee_production(year, month) # Transform and validate quality_rules = { 'required_columns': ['LEASE_NUMBER', 'PROD_DATE', 'OIL_PROD'], 'no_nulls': ['LEASE_NUMBER', 'PROD_DATE'], 'outlier_bounds': { 'OIL_PROD': {'min': 0, 'max': 1_000_000}, 'GAS_PROD': {'min': 0, 'max': 50_000_000} } } df_clean, issues = validate_data_quality(df_raw, quality_rules) # Log quality issues if issues: print(f"Data quality issues found: {len(issues)}") for issue in issues: print(f" [{issue['severity']}] {issue['message']}") # Load db_url = "postgresql://user:pass@localhost:5432/energy_data" records_loaded = load_to_database( df_clean, "bsee_production", db_url ) return { 'records_loaded': records_loaded, 'quality_issues': len(issues), 'timestamp': datetime.now() } ## Data Quality Monitoring ### Automated Quality Checks Production pipelines implement continuous quality monitoring: class DataQualityMonitor: """ Automated data quality monitoring for energy datasets. Tracks quality metrics over time and alerts on degradation. """ def __init__(self, historical_baseline): self.baseline = historical_baseline def check_completeness(self, df, required_fields): """ Measure data completeness (% non-null values). """ completeness = {} for field in required_fields: if field in df.columns: pct_complete = (1 - df[field].isna().mean()) * 100 completeness[field] = round(pct_complete, 2) else: completeness[field] = 0.0 return completeness def check_consistency(self, df): """ Check for logical consistency violations. Examples: - Oil production > 0 but no production date - Water depth < 0 - Future production dates """ violations = [] # Production without date if 'OIL_PROD' in df.columns and 'PROD_DATE' in df.columns: invalid = (df['OIL_PROD'] > 0) & (df['PROD_DATE'].isna()) if invalid.sum() > 0: violations.append({ 'rule': 'production_requires_date', 'count': invalid.sum() }) # Negative physical quantities for col in ['OIL_PROD', 'GAS_PROD', 'WATER_DEPTH']: if col in df.columns: invalid = df[col] < 0 if invalid.sum() > 0: violations.append({ 'rule': f'no_negative_{col.lower()}', 'count': invalid.sum() }) # Future dates if 'PROD_DATE' in df.columns: future = df['PROD_DATE'] > pd.Timestamp.now() if future.sum() > 0: violations.append({ 'rule': 'no_future_dates', 'count': future.sum() }) return violations def check_timeliness(self, df, date_column): """ Measure data freshness (lag from current date). """ if date_column not in df.columns: return None max_date = df[date_column].max() lag_days = (pd.Timestamp.now() - max_date).days return { 'latest_date': max_date, 'lag_days': lag_days, 'fresh': lag_days <= 90 # 90-day threshold } def generate_report(self, df, dataset_name): """ Generate comprehensive quality report. """ report = { 'dataset': dataset_name, 'timestamp': datetime.now(), 'record_count': len(df), 'completeness': self.check_completeness( df, ['LEASE_NUMBER', 'PROD_DATE', 'OIL_PROD', 'GAS_PROD'] ), 'consistency_violations': self.check_consistency(df), 'timeliness': self.check_timeliness(df, 'PROD_DATE') } # Compare to baseline if self.baseline: report['quality_trend'] = self._compare_to_baseline(report) return report def _compare_to_baseline(self, current_report): """ Detect quality degradation vs. historical baseline. """ alerts = [] # Completeness degradation for field, pct in current_report['completeness'].items(): baseline_pct = self.baseline.get('completeness', {}).get(field, 100) if pct < baseline_pct - 5: # 5% threshold alerts.append( f"Completeness degradation in {field}: " f"{baseline_pct}% → {pct}%" ) return alerts Quality Threshold Tuning: Overly strict quality rules cause alert fatigue; too loose and errors propagate. Start conservative (e.g., 95% completeness) and adjust based on 3-6 months of operational data. ## ROI Calculation for Automation ### Cost-Benefit Analysis Justifying automation investment requires quantifying current costs and projected savings: Cost/Benefit Category Manual Process Automated Pipeline Annual Savings Data collection labor $60,000 $5,000 (monitoring) $55,000 Quality control labor $25,000 $3,000 (alert triage) $22,000 Data error correction $15,000 $2,000 $13,000 Infrastructure costs $5,000 (manual tools) $12,000 (cloud, DB) -$7,000 Net Annual Benefit $83,000 Implementation Cost (Year 1) $60,000 Payback Period 8.7 months ### Hidden Benefits Beyond direct cost savings, automation delivers strategic advantages: Faster decision-making: Real-time data enables daily optimization vs. monthly reviews Improved accuracy: Validation of schema, completeness and expected ranges Reproducibility: Auditable data lineage and transformation logic Scalability: Reuse extraction and validation steps when adding data sources Analyst retention: Less tedious work improves job satisfaction and reduces turnover ## Implementation Roadmap ### Phase 1: Pilot (Months 1-2) Select single high-value data source (e.g., BSEE production) Build basic ETL pipeline with manual validation Run in parallel with manual process to validate accuracy Establish quality baseline metrics ### Phase 2: Production (Months 3-4) Automate scheduling and monitoring Implement data quality alerting Train team on pipeline operation and troubleshooting Retire manual process for pilot source ### Phase 3: Expansion (Months 5-12) Add 2-3 additional data sources per quarter Build unified data warehouse for cross-source analytics Develop self-service BI dashboards on automated data Measure and report ROI to stakeholders ### Technology Stack Recommendations Component Small Team (<5 analysts) Large Team (>20 analysts) Orchestration Prefect (open-source) Airflow or Prefect Cloud Storage PostgreSQL + Parquet files Snowflake or Databricks Quality Monitoring Custom Python scripts Great Expectations or Monte Carlo BI/Reporting Jupyter notebooks + Plotly Tableau or Power BI Infrastructure AWS EC2 + S3 AWS ECS/Fargate + RDS ## Best Practices and Lessons Learned ### Start Simple, Iterate Fast Don't try to automate everything at once. Focus on: Highest-volume data sources (most manual time) Most error-prone processes (quality improvement) Most time-sensitive data (business impact) ### Involve Data Consumers Early Analysts using the data should validate pipeline outputs and define quality rules. Technical perfection means nothing if the data doesn't meet business needs. ### Plan for Data Source Changes Regulatory agencies change data formats without notice. Build pipelines with: Schema validation before processing Fallback to manual processing when validation fails Version-controlled transformation logic Alerting on unexpected schema changes Maintenance Reality: Automated pipelines are not "set and forget." Budget 10-15% of implementation time annually for maintenance, schema updates, and data source changes. Under-budgeting maintenance leads to pipeline degradation and eventual abandonment. ## Conclusion Energy data automation transforms data collection from a cost center into a strategic capability. The practical approaches in this article demonstrate: Cost reduction: Repeatable data collection and processing ETL architecture: Three-layer extraction, transformation, loading pattern Quality monitoring: Automated validation, consistency checking, and alerting ROI evaluation: Compare implementation and maintenance costs with the measured time saved Organizations still relying on manual data workflows face increasing competitive disadvantage—slower decision-making, higher error rates, and inability to scale analysis with growing data volumes. Automation is no longer a "nice to have"; it's table stakes for modern energy data analytics. See the energy data workflows for related analysis methods and public-data tools. ### About the Author Vamsee Achanta, P.E. is the founder of Analytical & Computational Engineering (AceEngineer), specializing in energy data automation and analytics infrastructure. With experience processing terabytes of regulatory and operator data, Vamsee helps organizations eliminate manual workflows and build scalable, reproducible data pipelines. Learn more about AceEngineer → ### Ready to Automate Your Energy Data Workflows? Contact us to discuss energy-data collection, ETL workflows and data-quality checks under a separately agreed scope. Get in Touch More Articles ### Related Articles Energy Sector Consulting - AceEngineer Gulf of Mexico Production Data Access Marine Safety Incident Analysis NPV Analysis for Deepwater Field Development ## Gulf of Mexico Production Data Access | AceEngineer Blog URL: https://www.aceengineer.com/blog/gulf-of-mexico-production-data-access.html Description: Access Gulf of Mexico production data programmatically using BSEE public datasets and Python APIs. Learn ETL strategies, data quality handling, and automated pipeline development for oil and gas production analysis. # Gulf of Mexico Production Data Access: Programmatic Access to BSEE Production Datasets Author: Vamsee Achanta, P.E. | Published: February 2026 | Reading Time: 16 minutes | Category: Energy Data Abstract: The Bureau of Safety and Environmental Enforcement (BSEE) maintains comprehensive production datasets for Gulf of Mexico offshore operations, but accessing and processing this data programmatically requires navigating complex file formats, inconsistent structures, and data quality challenges. This article provides practical Python-based approaches for automated data retrieval, ETL pipeline development, and handling common data quality issues in BSEE production datasets. ## Why Gulf of Mexico Production Data Matters The Gulf of Mexico produces approximately 15% of U.S. crude oil and 2% of natural gas, representing critical national energy infrastructure. Production data from BSEE provides unprecedented transparency into offshore operations, enabling: Field development planning: Historical production trends inform reservoir performance models and decline curve analysis Economic analysis: Production histories are essential for NPV calculations and reserve valuations Regulatory compliance: Operators must report monthly production, creating auditable records Market intelligence: Understanding regional production trends and operator performance However, BSEE data is published in formats designed for government recordkeeping, not computational analysis. Manual downloads and spreadsheet processing are time-consuming, error-prone, and impossible to scale across thousands of leases and decades of history. Key Insight: Programmatic access transforms BSEE data from a compliance burden into a strategic asset. Automated pipelines enable daily updates, historical backtesting, and integration with proprietary analysis tools—all while maintaining reproducibility and audit trails. ## BSEE Production Data Sources ### Available Datasets BSEE publishes production data through multiple channels, each with different update frequencies and data granularity: Dataset Granularity Update Frequency Format Best Use Case OGOR-A (Oil & Gas Operations Report) Monthly, per lease Monthly (60-day lag) ZIP/CSV Time series analysis, decline curves Production Summary Annual, per lease Annually ZIP/CSV Long-term trends, cumulative totals Platform Production Monthly, per platform Monthly ZIP/CSV Infrastructure-level analysis Well Production Monthly, per well Monthly ZIP/CSV Well-level performance, EUR estimation Public Data Repository (PDR) Varies Continuous Mixed (PDF, Excel, CSV) Specialized reports, historical data ### Data Access Points BSEE provides data through several portals: Data Center Downloads: Bulk ZIP files updated monthly at data.bsee.gov Public Data Repository: Document-centric archive with search functionality API Access: Limited JSON endpoints for recent data (undocumented, subject to change) Freedom of Information Act (FOIA): Requests for non-public or historical data Important: BSEE does not provide a formal API with versioning or SLA guarantees. Data formats change without notice, requiring defensive programming and validation logic in production pipelines. ## Python-Based Data Access ### Basic Download Automation The simplest approach downloads monthly ZIP files and extracts CSV data: import requests import zipfile import pandas as pd from pathlib import Path from io import BytesIO def download_bsee_production(year, month, data_dir="data/bsee"): """ Download and extract BSEE monthly production data. Args: year: Four-digit year (e.g., 2024) month: Two-digit month (e.g., "01" for January) data_dir: Local directory for downloaded data Returns: DataFrame with production records """ # BSEE data center URL pattern base_url = "https://www.data.bsee.gov/Production/Files" filename = f"ogor{year}{month}.zip" url = f"{base_url}/{filename}" # Download ZIP file response = requests.get(url, timeout=60) response.raise_for_status() # Extract CSV from ZIP with zipfile.ZipFile(BytesIO(response.content)) as z: # BSEE ZIPs typically contain single CSV csv_name = [f for f in z.namelist() if f.endswith('.csv')][0] # Read directly into pandas with z.open(csv_name) as csv_file: df = pd.read_csv(csv_file, low_memory=False) # Cache locally output_path = Path(data_dir) / f"production_{year}_{month}.parquet" output_path.parent.mkdir(parents=True, exist_ok=True) df.to_parquet(output_path, index=False) return df ### Handling Data Quality Issues BSEE data contains common quality problems that must be handled programmatically: def clean_bsee_production(df): """ Standardize and clean BSEE production data. Handles: - Missing/invalid production values - Water depth encoding inconsistencies - Lease number formatting variations - Date parsing across different schemas """ df_clean = df.copy() # Standardize column names (BSEE uses inconsistent casing) df_clean.columns = df_clean.columns.str.upper().str.strip() # Parse production date (multiple formats exist) if 'PROD_DATE' in df_clean.columns: df_clean['PROD_DATE'] = pd.to_datetime( df_clean['PROD_DATE'], errors='coerce' ) elif 'PRODUCTION_DATE' in df_clean.columns: df_clean['PROD_DATE'] = pd.to_datetime( df_clean['PRODUCTION_DATE'], format='%Y%m', errors='coerce' ) # Clean numeric production values prod_cols = ['OIL_PROD', 'GAS_PROD', 'COND_PROD', 'WATER_PROD'] for col in prod_cols: if col in df_clean.columns: # Replace common invalid values df_clean[col] = pd.to_numeric( df_clean[col].replace(['NA', 'NULL', '-'], None), errors='coerce' ) # Zero fill missing values (reported as no production) df_clean[col] = df_clean[col].fillna(0) # Standardize lease numbers (remove leading zeros) if 'LEASE_NUMBER' in df_clean.columns: df_clean['LEASE_NUMBER'] = df_clean['LEASE_NUMBER'].astype(str).str.lstrip('0') # Water depth classification if 'WATER_DEPTH' in df_clean.columns: df_clean['DEPTH_CLASS'] = pd.cut( df_clean['WATER_DEPTH'], bins=[0, 400, 1000, 5000, 12000], labels=['Shelf', 'Deepwater', 'Ultra-Deepwater', 'Frontier'] ) return df_clean Data Quality Reality: Approximately 3-5% of BSEE production records contain data quality issues: negative production values, impossible dates, missing lease identifiers, or encoding errors. Production pipelines must handle these gracefully without failing entire batches. ## Building Production-Grade ETL Pipelines ### Pipeline Architecture A robust BSEE data pipeline includes extraction, transformation, validation, and storage layers: from dataclasses import dataclass from typing import List, Dict import logging @dataclass class BSEEPipeline: """Production-grade BSEE data pipeline.""" start_year: int end_year: int output_format: str = "parquet" # or "sqlite", "postgresql" validate: bool = True def run(self): """Execute complete ETL pipeline.""" logger = logging.getLogger(__name__) # 1. Extract - download all months in range raw_data = [] for year in range(self.start_year, self.end_year + 1): for month in range(1, 13): try: df = download_bsee_production(year, f"{month:02d}") raw_data.append(df) logger.info(f"Downloaded {year}-{month:02d}: {len(df)} records") except requests.HTTPError as e: logger.warning(f"Missing data for {year}-{month:02d}: {e}") continue # 2. Transform - concatenate and clean df_all = pd.concat(raw_data, ignore_index=True) df_clean = clean_bsee_production(df_all) # 3. Validate - check data quality if self.validate: issues = self._validate_data(df_clean) if issues['critical']: raise ValueError(f"Critical validation errors: {issues['critical']}") if issues['warnings']: logger.warning(f"Data quality warnings: {len(issues['warnings'])}") # 4. Load - write to output format self._save_data(df_clean) return df_clean def _validate_data(self, df) -> Dict[str, List]: """Validate cleaned data against business rules.""" issues = {'critical': [], 'warnings': []} # Critical: must have production date and lease number if df['PROD_DATE'].isna().any(): issues['critical'].append("Missing production dates detected") if df['LEASE_NUMBER'].isna().any(): issues['critical'].append("Missing lease numbers detected") # Warning: negative production (data error, not critical) neg_oil = (df['OIL_PROD'] < 0).sum() if neg_oil > 0: issues['warnings'].append(f"{neg_oil} records with negative oil production") # Warning: unrealistic production spikes if 'OIL_PROD' in df.columns: q99 = df['OIL_PROD'].quantile(0.99) outliers = (df['OIL_PROD'] > q99 * 10).sum() if outliers > 0: issues['warnings'].append(f"{outliers} extreme outliers detected") return issues ### Incremental Updates Production systems should download only new data to minimize bandwidth and processing time: def incremental_update(existing_db_path, output_path): """ Update existing production database with new monthly data. Detects last available month and downloads only new releases. """ # Read existing data df_existing = pd.read_parquet(existing_db_path) # Find last complete month last_date = df_existing['PROD_DATE'].max() last_year = last_date.year last_month = last_date.month # Download new months (BSEE has 60-day reporting lag) today = pd.Timestamp.now() target_month = today - pd.DateOffset(months=2) new_data = [] current = pd.Timestamp(year=last_year, month=last_month, day=1) while current <= target_month: current += pd.DateOffset(months=1) year = current.year month = current.month try: df = download_bsee_production(year, f"{month:02d}") new_data.append(df) except requests.HTTPError: # Data not yet available break if new_data: # Merge with existing df_new = pd.concat(new_data, ignore_index=True) df_combined = pd.concat([df_existing, df_new], ignore_index=True) df_combined = df_combined.drop_duplicates( subset=['LEASE_NUMBER', 'PROD_DATE'], keep='last' ) df_combined.to_parquet(output_path, index=False) return len(df_new) return 0 ## Integration with Analysis Tools ### Decline Curve Analysis Integration Production data feeds directly into reservoir engineering workflows: Analysis Type Required Data BSEE Source Typical Workflow Single-well EUR Monthly production by well Well Production dataset Arps hyperbolic decline fit Field-level reserves Lease-aggregated production OGOR-A dataset Multi-well type curve analysis Platform economics Platform-allocated volumes Platform Production dataset NPV with infrastructure costs Regional trends Area/basin aggregates Production Summary Play-level opportunity screening ### Example: Automated Decline Analysis from scipy.optimize import curve_fit import numpy as np def arps_hyperbolic(t, qi, Di, b): """Arps hyperbolic decline equation.""" return qi / ((1 + b * Di * t) ** (1 / b)) def fit_decline_curve(lease_number, bsee_data): """ Fit Arps decline curve to BSEE production history. Returns forecast parameters and EUR estimate. """ # Filter to specific lease df_lease = bsee_data[ bsee_data['LEASE_NUMBER'] == lease_number ].sort_values('PROD_DATE') # Convert to monthly time index df_lease['MONTHS'] = ( (df_lease['PROD_DATE'] - df_lease['PROD_DATE'].min()) / pd.Timedelta(days=30.44) ).astype(int) # Fit hyperbolic decline t = df_lease['MONTHS'].values q = df_lease['OIL_PROD'].values # Initial guesses: qi=max rate, Di=10%/year, b=0.5 p0 = [q.max(), 0.10/12, 0.5] try: params, _ = curve_fit( arps_hyperbolic, t, q, p0=p0, bounds=([0, 0, 0], [q.max()*2, 1.0, 2.0]) ) qi, Di, b = params # Forecast 30 years t_forecast = np.arange(0, 360) q_forecast = arps_hyperbolic(t_forecast, qi, Di, b) # EUR calculation (cumulative to economic limit) eur = np.trapz(q_forecast, dx=1) # Monthly barrels return { 'qi': qi, 'Di': Di, 'b': b, 'eur': eur, 'forecast': q_forecast } except RuntimeError: return None # Fit failed ## Best Practices and Gotchas ### Common Pitfalls Reporting lag: BSEE data is 60-90 days delayed; don't expect real-time updates Lease vs. well vs. platform: Ensure you're aggregating at the correct level for your analysis Shut-in periods: Zero production may indicate temporary shutdown, not well exhaustion Unit conversions: BSEE reports oil in barrels (BBL), gas in MCF; check your formulas Confidentiality periods: Some recent data may be withheld for competitive reasons ### Performance Optimization Performance Tip: BSEE production datasets span 50+ years and millions of records. Use Parquet or DuckDB for local storage instead of CSV—query times improve 10-100x for typical analyses. ### Validation Checklist Verify total GoM production matches EIA reported values (within 5%) Check for duplicate records after merging monthly downloads Validate water depth classification against lease maps Cross-reference major field names with operator press releases Test pipeline on historical data before deploying to production ## Conclusion Programmatic access to BSEE production data transforms Gulf of Mexico analysis from manual, error-prone spreadsheet work into automated, reproducible pipelines. The investment in building robust ETL infrastructure pays dividends through: Speed: Daily updates instead of quarterly manual downloads Scale: Analyze all 3,500+ active leases simultaneously Reproducibility: Auditable data lineage and transformation logic Integration: Seamless connection to decline analysis, economics, and visualization tools The code examples in this article provide a starting point for production pipelines. Real-world implementations should add monitoring, error handling, data quality dashboards, and integration with your organization's data infrastructure. For energy sector consulting projects requiring Gulf of Mexico production analysis, we've developed comprehensive ETL frameworks that handle BSEE, state regulatory data, and operator reporting—delivering clean, analysis-ready datasets with full documentation. ### About the Author Vamsee Achanta, P.E. is the founder of Analytical & Computational Engineering (AceEngineer), specializing in energy data automation and offshore engineering analytics. With experience processing multi-terabyte energy datasets, Vamsee helps organizations transition from manual data workflows to automated, reproducible pipelines. Learn more about AceEngineer → ### Need Help with Energy Data Automation? We build production-grade ETL pipelines for BSEE, state regulatory data, and proprietary energy datasets—transforming manual workflows into automated, reproducible analysis infrastructure. Get in Touch More Articles ### Related Articles Energy Sector Consulting - AceEngineer NPV Analysis for Deepwater Field Development Energy Data Automation Pipelines: From Manual to Automated Workflows ## Engineering and automation articles | AceEngineer URL: https://www.aceengineer.com/blog/ Description: Articles on engineering analysis, open energy data, AI automation and agentic workflows. Read the newsletter archive and explore the public code. # Engineering Blog Technical articles on computational engineering methods, automated workflows, and industry insights. ## Energy Data Automation Pipelines: From Manual to Automated Workflows Published: February 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 16 minutes Energy companies spend millions annually on manual data collection, yet face delays, errors, and reproducibility challenges. Automated pipelines reduce collection costs by 60-80% while improving quality and enabling real-time analytics. This practical guide covers the cost of manual workflows, ETL architecture patterns, Python implementation examples, data quality monitoring, and ROI calculation for oil and gas data automation. Read Article ## Marine Safety Incident Analysis: Cross-Database Correlation Published: February 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 14 minutes Marine safety incidents are reported to multiple regulatory databases—BSEE, USCG, and IMO—each with different identifiers, classification schemes, and reporting standards. Cross-database correlation is essential for comprehensive risk analysis. This article presents practical Python approaches for entity resolution, temporal correlation, regulatory compliance analysis, and integrating heterogeneous marine safety datasets for offshore operations. Read Article ## NPV Analysis for Deepwater Field Development Published: February 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 15 minutes Deepwater projects require $2-10 billion investments with 20-30 year lifecycles. Net Present Value and Internal Rate of Return analysis are fundamental for investment decisions, but deepwater introduces unique complexities. This guide covers NPV/IRR fundamentals for offshore economics, Python code for decline curves and DCF modeling, sensitivity analysis, Monte Carlo simulation, and Gulf of Mexico economic evaluation examples. Read Article ## Gulf of Mexico Production Data Access: Programmatic BSEE Data Published: February 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 16 minutes BSEE maintains comprehensive Gulf of Mexico production datasets, but accessing this data programmatically requires navigating complex file formats, inconsistent structures, and data quality challenges. This practical guide covers BSEE data sources, Python-based automated retrieval, ETL pipeline development, data quality handling, and integration with decline curve analysis and field development economics. Read Article ## CFD for Offshore Engineering: From Wave Loading to VIV Analysis Published: January 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 14 minutes Computational Fluid Dynamics (CFD) has become essential for offshore engineering challenges that empirical formulas cannot address. From complex wave-structure interactions to vortex-induced vibration prediction, CFD provides detailed flow field information needed for reliable design. This practical guide covers when CFD adds value, wave loading analysis with free surface modeling, VIV prediction and suppression device optimization, computational surrogate models, and verification approaches for offshore applications. Read Article ## Risk-Based Inspection for Offshore Structures: AI-Enhanced Approaches Published: January 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 14 minutes Offshore inspection programs face a fundamental tension: inspect too little and risk catastrophic failures; inspect too much and waste resources. Risk-based inspection (RBI) resolves this by focusing efforts where they matter most. AI-enhanced approaches enable dynamic prioritization based on operational data and predictive models. This guide covers probability of failure modeling, consequence assessment, inspection effectiveness integration, Bayesian updating after inspections, and practical implementation strategies for API 580/581 and DNV-RP-G101 compliant programs. Read Article ## Digital Twins for Offshore Asset Integrity: From Concept to Implementation Published: January 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 15 minutes Digital twins promise to transform offshore asset management, but implementation remains challenging. Many organizations struggle with sensor integration, physics model calibration, and demonstrating ROI. This practical guide cuts through the marketing hype to examine what digital twins really are, how they work, and when they make engineering and business sense. We explore the digital twin maturity spectrum, architectural layers from data acquisition to decision interfaces, sensor deployment strategies, Bayesian model updating for fatigue estimation, and frameworks for evaluating digital twin investments on offshore platforms and wind turbines. Read Article ## Navigating Offshore Engineering Standards: DNV, API, and Beyond Published: January 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 15 minutes Offshore engineering projects must comply with multiple international standards that govern design, fabrication, installation, and operation. DNV-RP-C203, API RP 2A, BS 7608, and ISO 19901 represent different regulatory frameworks with varying requirements, safety factors, and methodologies. This comprehensive guide covers how different standards apply to different project phases, automated approaches to multi-standard compliance verification, and practical tips for navigating complex regulatory requirements on global offshore projects. Read Article ## Open-Source Engineering Tools: Building Transparent Computational Methods Published: January 2025 | Author: Vamsee Achanta, P.E. | Reading Time: 10 minutes When an engineering consultant delivers analysis results, how do you know the calculations are correct? Traditional approaches rely on trust and credentials. Open-source engineering tools offer something better: complete transparency into the computational methods behind the results. This article explores why open-source matters for engineering software, introduces our GitHub repositories for fatigue analysis and FEA post-processing, and explains how engineers can use and contribute to these tools. Read Article ## AI-Native Structural Analysis: Why Traditional FEA is Changing Published: January 2025 | Author: Vamsee Achanta, P.E. | Reading Time: 8 minutes Finite Element Analysis (FEA) has been the cornerstone of structural engineering for decades. But computational approaches combining surrogate models with traditional methods are changing how we analyze, validate, and optimize complex structures. This article explores what this means, why it matters, and how it differs from traditional FEA. We'll examine real-world applications in offshore engineering, compare computational performance, discuss validation methodologies, and show why technical evaluators should care about this shift. Read Article ## Machine Learning for Fatigue Life Prediction: Beyond S-N Curves Published: January 2025 | Author: Vamsee Achanta, P.E. | Reading Time: 12 minutes Traditional fatigue analysis relies on S-N curves derived from standardized test specimens. But real-world structures experience complex loading histories, environmental degradation, and manufacturing variations that laboratory conditions can't fully capture. Machine learning offers a path forward. This article explores how ML models trained on operational data can improve fatigue life predictions by 15-40% compared to traditional methods, with practical implementation guidance and validation approaches. Read Article ## Python Engineering Automation: From Manual Workflows to Reproducible Analysis Published: January 2025 | Author: Vamsee Achanta, P.E. | Reading Time: 12 minutes Every engineer knows the pain: running the same analysis with slightly different parameters, manually copying results into spreadsheets, reformatting reports for each project. Python automation changes this equation fundamentally. This practical guide covers FEA post-processing automation, report generation, and building complete analysis pipelines with real code examples you can adapt for your workflows. Read Article ## Coming Soon Articles cover: Machine Learning for Engineering - Fatigue prediction, optimization, and anomaly detection Computational Methods - FEA, CFD, and coupled physics simulations Open-Source Tools - Engineering software and libraries we're developing Industry Standards - API, DNV, ISO, and ASME compliance Case Studies - Analysis methods and lessons learned Best Practices - Software engineering for computational methods ## The Deckhand Chronicle Read every issue in the newsletter archive. reply to any issue to subscribe or stop Or write to support@aceengineer.com. ## Machine Learning for Fatigue Life Prediction | AceEngineer Blog URL: https://www.aceengineer.com/blog/machine-learning-fatigue-prediction.html Description: How machine learning transforms fatigue life prediction in engineering. Learn about data-driven approaches that outperform traditional S-N curve methods for offshore and subsea structures. # Machine Learning for Fatigue Life Prediction: Beyond Traditional S-N Curves Author: Vamsee Achanta, P.E. | Published: January 12, 2025 | Reading Time: 12 minutes | Category: Computational Engineering Abstract: Traditional fatigue life prediction relies on S-N curves derived from limited experimental data, often leading to overly conservative designs or unexpected failures. This article explores how machine learning approaches can capture complex material behavior, environmental effects, and loading history—delivering more accurate predictions while maintaining the safety margins required for critical infrastructure. ## The Fatigue Challenge in Engineering Fatigue failure remains one of the most common and dangerous failure modes in engineering structures. From offshore platforms to aircraft components, cyclic loading gradually damages materials until catastrophic failure occurs—often with little warning. The traditional approach to fatigue assessment relies on S-N curves (stress-life curves) developed from laboratory testing. While these curves have served the industry for decades, they have significant limitations: Limited data: S-N curves are typically derived from small sample sizes under idealized conditions Single-variable focus: Traditional curves don't capture interactions between stress, temperature, corrosion, and loading frequency Conservative factors: Uncertainty leads to large safety factors, resulting in heavier, more expensive designs Poor extrapolation: Predictions outside the tested range are unreliable Machine learning offers a fundamentally different approach: instead of fitting simplified curves to limited data, ML models can learn complex patterns from comprehensive datasets—including operational data from real structures. ## How Traditional Fatigue Assessment Works ### The S-N Curve Approach The standard S-N curve relates stress amplitude (S) to the number of cycles to failure (N). The relationship typically follows Basquin's equation: S = A × N^b Where: S = Stress amplitude (MPa) N = Number of cycles to failure A = Fatigue strength coefficient b = Fatigue strength exponent (typically -0.05 to -0.15) ### Design Code Implementation Industry standards like DNV-RP-C203 and API RP 2A provide S-N curves for different material categories and environments. Engineers select the appropriate curve and apply safety factors based on: Consequence of failure (safety critical vs. non-critical) Inspection accessibility Design fatigue factor (DFF) typically 2-10 The Problem: These safety factors are applied uniformly, regardless of how well the specific conditions match the S-N curve's test conditions. A joint operating in benign conditions gets the same penalty as one in severe service. ### Miner's Rule for Damage Accumulation For variable amplitude loading, fatigue damage is typically calculated using Miner's cumulative damage rule: D = Σ (n_i / N_i) Where: D = Cumulative damage (failure at D = 1.0) n_i = Number of cycles at stress level i N_i = Cycles to failure at stress level i (from S-N curve) While simple and widely used, Miner's rule assumes damage accumulation is linear and sequence-independent—both assumptions that contradict experimental evidence. ## The Machine Learning Approach Machine learning transforms fatigue prediction from curve-fitting to pattern recognition. Instead of assuming a mathematical relationship, ML models discover the underlying patterns from data. ### Key Advantages of ML for Fatigue Aspect Traditional S-N ML Approach Input Variables Stress amplitude only Multiple: stress, temperature, frequency, environment, loading history Interaction Effects Ignored or simplified Automatically captured Sequence Effects Not considered Can be modeled with RNNs/LSTMs Uncertainty Quantification Fixed safety factors Probabilistic predictions with confidence bounds Updating with New Data Requires new curve fitting Continuous learning from operational data ### ML Model Architectures for Fatigue #### 1. Gradient Boosting for Tabular Data For structured fatigue data with multiple features, gradient boosting methods (XGBoost, LightGBM) excel at capturing non-linear relationships: # Example: XGBoost for fatigue life prediction import xgboost as xgb import numpy as np # Features: [stress_amp, mean_stress, temperature, frequency, # R_ratio, surface_roughness, environment_code] X_train = np.array([...]) # Training features y_train = np.array([...]) # Log(cycles to failure) model = xgb.XGBRegressor( n_estimators=500, max_depth=6, learning_rate=0.05, subsample=0.8 ) model.fit(X_train, y_train) # Predict with uncertainty (using quantile regression) predictions = model.predict(X_test) #### 2. Neural Networks for Complex Patterns Deep neural networks can capture highly non-linear relationships and are particularly effective when combined with physics-informed constraints: # Physics-Informed Neural Network for Fatigue import torch import torch.nn as nn class FatigueNet(nn.Module): def __init__(self, input_dim): super().__init__() self.network = nn.Sequential( nn.Linear(input_dim, 128), nn.ReLU(), nn.Dropout(0.2), nn.Linear(128, 64), nn.ReLU(), nn.Linear(64, 32), nn.ReLU(), nn.Linear(32, 1) ) def forward(self, x): # Output: log(N) - ensures positive cycle predictions return self.network(x) def physics_loss(self, stress, pred_cycles): # Enforce: higher stress → fewer cycles stress_gradient = torch.autograd.grad( pred_cycles, stress, grad_outputs=torch.ones_like(pred_cycles), create_graph=True )[0] # Penalize positive gradients (physics violation) return torch.relu(stress_gradient).mean() #### 3. Recurrent Networks for Loading History LSTM networks can capture sequence-dependent damage accumulation—something Miner's rule fundamentally cannot do: Key Insight: Research shows that high-low loading sequences cause more damage than low-high sequences at the same stress levels. LSTMs can learn these sequence effects directly from data, eliminating the need for sequence correction factors. ## Case Study: Offshore Riser Fatigue Consider fatigue assessment for a steel catenary riser (SCR) in deepwater operations. Traditional methods use S-N curves with environmental correction factors, but real operational data reveals significant complexity: ### Data Available 10 years of wave and current monitoring data Strain gauge measurements at critical locations Temperature and salinity profiles Inspection records from similar risers Laboratory test data for the specific steel grade ### ML Model Development Step Activity Outcome 1. Data Integration Combine operational, test, and inspection data 50,000+ data points with 15 features 2. Feature Engineering Create fatigue-relevant features (rainflow counts, load ratios) 25 engineered features 3. Model Training Train ensemble of XGBoost + Neural Network R² = 0.94 on validation set 4. Validation Compare against known failures and inspections 95% predictions within factor of 2 ### Results Comparison Metric Traditional S-N (DNV) ML Ensemble Improvement Prediction Accuracy (RMSE) 0.45 log(cycles) 0.18 log(cycles) 60% reduction False Alarm Rate 35% 8% 77% reduction Missed Detections 2% 1% 50% reduction Inspection Cost Impact Baseline -40% Optimized scheduling Business Impact: The ML model's improved accuracy enabled condition-based maintenance scheduling, reducing inspection costs by 40% while maintaining the same safety level. The reduced false alarm rate meant fewer unnecessary repairs and less unplanned downtime. ## Validation and Industry Acceptance For ML-based fatigue predictions to be accepted in safety-critical applications, rigorous validation is essential: ### Validation Framework Analytical Benchmarks: Verify model recovers traditional S-N behavior under standard conditions Cross-Validation: K-fold validation with stratified sampling by failure mode Out-of-Distribution Testing: Test on conditions not seen during training Physical Consistency: Verify predictions respect known physical constraints Comparison with Failures: Validate against documented failure cases ### Industry Standards Compliance ML models for fatigue can be integrated with existing standards: DNV-RP-C203: Use ML predictions as input to standard fatigue assessment procedures API 579: ML-enhanced fitness-for-service evaluations BS 7910: Probabilistic fatigue assessment with ML-derived distributions Regulatory Path: Rather than replacing code-based methods, ML predictions can be used to reduce conservatism where justified by data. The base safety factor remains, but additional penalties for uncertainty can be reduced when ML models demonstrate high confidence. ## Implementing ML Fatigue Prediction ### Data Requirements Successful ML fatigue models require comprehensive data: Minimum: 500+ fatigue test results with consistent documentation Recommended: 5,000+ data points spanning target operational range Essential features: Stress amplitude, mean stress, temperature, environment, frequency Valuable additions: Loading history, surface condition, microstructure data ### Model Selection Guidelines Scenario Recommended Model Rationale Structured data, clear features Gradient Boosting (XGBoost) Interpretable, robust, handles missing data Complex interactions, large data Deep Neural Network Captures highly non-linear patterns Sequence-dependent loading LSTM / Transformer Models temporal dependencies Limited data, need uncertainty Gaussian Process Built-in uncertainty quantification Production deployment Ensemble of above Robustness and reliability ### Deployment Considerations Model versioning: Track model versions and training data Monitoring: Detect data drift and model degradation Fallback: Maintain traditional methods as backup Documentation: Full traceability for regulatory review ## The Future of Fatigue Assessment Machine learning is not just improving fatigue prediction—it's enabling entirely new approaches: ### Digital Twins for Fatigue Monitoring Real-time ML models integrated with sensor data can provide continuous fatigue damage estimation, enabling true predictive maintenance. ### Transfer Learning Across Assets Models trained on one fleet can be adapted to new assets with limited data, accelerating deployment across organizations. ### Physics-Informed Machine Learning Combining ML flexibility with physics constraints ensures predictions remain physically meaningful even in extrapolation. Looking Ahead: The convergence of sensor technology, cloud computing, and machine learning is creating opportunities for fatigue management that were impossible just a decade ago. Organizations that embrace these methods will have significant advantages in asset reliability and maintenance optimization. ## Conclusion Machine learning offers a powerful complement to traditional fatigue assessment methods. By learning from comprehensive datasets rather than simplified laboratory tests, ML models can: Capture complex interactions between multiple variables Account for sequence-dependent damage accumulation Provide probabilistic predictions with meaningful uncertainty bounds Continuously improve as new operational data becomes available The key is not to replace traditional methods but to enhance them—using ML to reduce unnecessary conservatism where data supports it while maintaining the safety margins that protect lives and assets. For organizations managing fatigue-critical structures, the question is no longer whether to adopt ML-based methods, but how quickly they can build the data infrastructure and technical capabilities to do so effectively. ### About the Author Vamsee Achanta, P.E. is the founder of Analytical & Computational Engineering (AceEngineer), specializing in computational methods for structural engineering challenges. With extensive experience in offshore and subsea engineering, Vamsee focuses on applying data-driven methods to improve engineering analysis accuracy while maintaining industry standard compliance. Learn more about AceEngineer → ### Interested in ML-Enhanced Fatigue Assessment? We help engineering teams implement machine learning approaches for fatigue prediction while maintaining compliance with industry standards. Get in Touch More Articles ### Related Articles AI-Native Structural Analysis: Moving Beyond Traditional FEA ## Marine Safety Incident Analysis | AceEngineer Blog URL: https://www.aceengineer.com/blog/marine-safety-incident-analysis.html Description: Cross-database correlation for marine safety incident analysis. Data sources from BSEE, USCG, and IMO. Python code for entity resolution, temporal correlation, and regulatory compliance analysis. # Marine Safety Incident Analysis: Cross-Database Correlation and Regulatory Compliance Author: Vamsee Achanta, P.E. | Published: February 2026 | Reading Time: 14 minutes | Category: Marine Safety Abstract: Marine safety incident analysis requires integrating data from multiple regulatory databases—BSEE offshore incidents, USCG marine casualties, and IMO casualty reports. Each database uses different identifiers, classification schemes, and reporting standards, creating significant challenges for cross-database correlation. This article presents practical Python-based approaches for entity resolution, temporal correlation, and regulatory compliance analysis across heterogeneous marine safety datasets. ## The Challenge of Fragmented Safety Data Marine safety incidents are reported to different regulatory authorities depending on location, vessel type, and incident severity: BSEE (Bureau of Safety and Environmental Enforcement): Offshore oil and gas incidents in U.S. waters USCG (U.S. Coast Guard): Marine casualties involving vessels in U.S. navigable waters IMO (International Maritime Organization): Global casualty database for international shipping NTSB (National Transportation Safety Board): Major maritime accident investigations Flag State authorities: Country-specific incident databases No single database provides comprehensive coverage. A platform supply vessel collision in the Gulf of Mexico may appear in BSEE records (if near a platform), USCG reports (vessel casualty), and potentially IMO databases (if internationally flagged)—but with different incident IDs, dates, and descriptions. Key Insight: Cross-database correlation is essential for comprehensive risk analysis. Single-source analyses systematically undercount incidents, misidentify root causes, and fail to capture industry-wide trends—leading to incomplete risk assessments and ineffective safety interventions. ## Marine Safety Data Sources ### Database Comparison Database Coverage Update Frequency Access Method Key Limitations BSEE Incident Investigations U.S. offshore O&G Quarterly Public download (data.bsee.gov) Excludes vessel-only incidents BSEE Incident of Non-Compliance (INC) U.S. offshore O&G Monthly Public download Regulatory violations only USCG Marine Information for Safety and Law Enforcement (MISLE) U.S. navigable waters Real-time FOIA requests, limited API Restricted access, FOIA delays IMO GISIS Casualty Database Global (IMO member states) Continuous Web portal (registration required) Voluntary reporting, quality varies NTSB Marine Accident Database Major U.S. incidents Per investigation Public website, reports Only major incidents investigated ### Data Quality Challenges Each database presents unique data quality issues: Vessel name variations: "M/V OCEAN CAPTAIN" vs. "OCEAN CAPTAIN" vs. "MV OCEAN CAPT" Date discrepancies: Incident date vs. report date vs. investigation completion date Location encoding: Lat/lon vs. lease numbers vs. geographic descriptions Severity classification: Non-standardized severity scales across databases Missing data: 20-40% of records have incomplete vessel identifiers or incident details Important: USCG MISLE data requires FOIA requests and can take 30-90 days to obtain. Plan data acquisition timelines accordingly for time-sensitive projects. ## Entity Resolution and Record Linkage ### Vessel Name Matching Fuzzy matching resolves vessel name variations across databases: from fuzzywuzzy import fuzz import pandas as pd def normalize_vessel_name(name): """ Standardize vessel names for matching. Handles: - Prefix removal (M/V, MV, MT, etc.) - Case normalization - Special character removal - Common abbreviations """ if pd.isna(name): return "" name = str(name).upper().strip() # Remove common prefixes prefixes = ['M/V ', 'MV ', 'MT ', 'M.V. ', 'M.T. ', 'S/V ', 'SV '] for prefix in prefixes: if name.startswith(prefix): name = name[len(prefix):] # Remove special characters name = ''.join(c for c in name if c.isalnum() or c.isspace()) # Normalize whitespace name = ' '.join(name.split()) # Expand common abbreviations abbreviations = { 'CAPT': 'CAPTAIN', 'STR': 'STAR', 'SERV': 'SERVICE', 'SUPP': 'SUPPLY' } for abbr, full in abbreviations.items(): name = name.replace(abbr, full) return name def match_vessels(df_source, df_target, threshold=85): """ Match vessels between two databases using fuzzy matching. Args: df_source: DataFrame with 'vessel_name' column df_target: DataFrame with 'vessel_name' column threshold: Minimum fuzzy match score (0-100) Returns: DataFrame with matched pairs and match scores """ # Normalize names df_source['vessel_normalized'] = df_source['vessel_name'].apply( normalize_vessel_name ) df_target['vessel_normalized'] = df_target['vessel_name'].apply( normalize_vessel_name ) matches = [] for idx_src, row_src in df_source.iterrows(): name_src = row_src['vessel_normalized'] if not name_src: continue best_match = None best_score = 0 for idx_tgt, row_tgt in df_target.iterrows(): name_tgt = row_tgt['vessel_normalized'] if not name_tgt: continue # Fuzzy ratio score = fuzz.ratio(name_src, name_tgt) if score > best_score and score >= threshold: best_score = score best_match = idx_tgt if best_match is not None: matches.append({ 'source_idx': idx_src, 'target_idx': best_match, 'source_name': row_src['vessel_name'], 'target_name': df_target.loc[best_match, 'vessel_name'], 'match_score': best_score }) return pd.DataFrame(matches) ### IMO Number Matching IMO numbers provide definitive vessel identification when available: def match_by_imo(df_bsee, df_uscg, df_imo): """ Match incidents across databases using IMO vessel numbers. IMO numbers are unique, permanent vessel identifiers assigned by the International Maritime Organization. Args: df_bsee: BSEE incident data df_uscg: USCG casualty data df_imo: IMO casualty data Returns: DataFrame with cross-referenced incidents """ # Extract IMO numbers (format: IMO1234567) for df in [df_bsee, df_uscg, df_imo]: if 'imo_number' in df.columns: df['imo_clean'] = df['imo_number'].astype(str).str.extract( r'(\d{7})' )[0] # Merge on IMO number df_merged = df_bsee.merge( df_uscg, on='imo_clean', how='outer', suffixes=('_bsee', '_uscg') ) df_merged = df_merged.merge( df_imo, on='imo_clean', how='outer', suffixes=('', '_imo') ) # Flag which databases contain the incident df_merged['in_bsee'] = df_merged['incident_id_bsee'].notna() df_merged['in_uscg'] = df_merged['case_number_uscg'].notna() df_merged['in_imo'] = df_merged['casualty_id_imo'].notna() return df_merged Data Quality Reality: Only 40-60% of offshore support vessels have IMO numbers in incident databases. Smaller vessels (under 500 GT) are not required to have IMO numbers, necessitating fuzzy name matching as a fallback strategy. ## Temporal Correlation Analysis ### Time-Window Matching Match incidents occurring within a defined time window at similar locations: from datetime import timedelta from scipy.spatial.distance import cdist def temporal_spatial_match(df_bsee, df_uscg, time_window_days=7, distance_threshold_km=50): """ Match incidents using temporal and spatial proximity. Args: df_bsee: BSEE incidents with [incident_date, latitude, longitude] df_uscg: USCG casualties with [casualty_date, lat, lon] time_window_days: Maximum days between incident dates distance_threshold_km: Maximum distance for spatial match Returns: DataFrame with potential cross-database matches """ matches = [] # Convert dates to datetime df_bsee['incident_date'] = pd.to_datetime(df_bsee['incident_date']) df_uscg['casualty_date'] = pd.to_datetime(df_uscg['casualty_date']) for idx_bsee, row_bsee in df_bsee.iterrows(): # Time window filter time_delta = timedelta(days=time_window_days) df_uscg_window = df_uscg[ (df_uscg['casualty_date'] >= row_bsee['incident_date'] - time_delta) & (df_uscg['casualty_date'] <= row_bsee['incident_date'] + time_delta) ] if len(df_uscg_window) == 0: continue # Spatial distance calculation (Haversine) for idx_uscg, row_uscg in df_uscg_window.iterrows(): distance_km = haversine_distance( row_bsee['latitude'], row_bsee['longitude'], row_uscg['lat'], row_uscg['lon'] ) if distance_km <= distance_threshold_km: matches.append({ 'bsee_idx': idx_bsee, 'uscg_idx': idx_uscg, 'time_diff_days': abs( (row_uscg['casualty_date'] - row_bsee['incident_date']).days ), 'distance_km': distance_km, 'match_confidence': calculate_match_confidence( time_diff_days=abs((row_uscg['casualty_date'] - row_bsee['incident_date']).days), distance_km=distance_km ) }) return pd.DataFrame(matches) def haversine_distance(lat1, lon1, lat2, lon2): """Calculate great-circle distance in kilometers.""" from math import radians, sin, cos, sqrt, atan2 R = 6371.0 # Earth radius in km lat1, lon1, lat2, lon2 = map(radians, [lat1, lon1, lat2, lon2]) dlat = lat2 - lat1 dlon = lon2 - lon1 a = sin(dlat/2)**2 + cos(lat1) * cos(lat2) * sin(dlon/2)**2 c = 2 * atan2(sqrt(a), sqrt(1-a)) return R * c def calculate_match_confidence(time_diff_days, distance_km): """ Calculate match confidence score (0-100). Perfect match: same day, same location (100) Weak match: 7 days apart, 50km distance (~40) """ time_score = max(0, 100 - (time_diff_days * 14)) # -14 pts per day distance_score = max(0, 100 - (distance_km * 2)) # -2 pts per km # Weighted average confidence = 0.6 * time_score + 0.4 * distance_score return round(confidence, 1) ## Cross-Database Analysis Patterns ### Incident Severity Comparison Standardize severity classifications across databases: def standardize_severity(df, source_db): """ Map database-specific severity codes to unified scale. Unified scale: 1 = Minor (no injury, minimal damage) 2 = Moderate (medical treatment, equipment damage) 3 = Serious (lost time injury, significant damage) 4 = Major (fatality, total loss) Args: df: Incident DataFrame source_db: 'bsee', 'uscg', or 'imo' Returns: DataFrame with 'severity_unified' column """ severity_maps = { 'bsee': { 'NON-INJURY': 1, 'FIRST AID': 1, 'MTC': 2, # Medical Treatment Case 'RWC': 2, # Restricted Work Case 'LWC': 3, # Lost Workday Case 'FATALITY': 4 }, 'uscg': { 'MINOR': 1, 'MODERATE': 2, 'SERIOUS': 3, 'MAJOR': 4, 'CASUALTY': 4 }, 'imo': { 'Less Serious': 1, 'Serious': 3, 'Very Serious': 4 } } if source_db not in severity_maps: raise ValueError(f"Unknown database: {source_db}") severity_col = { 'bsee': 'injury_severity', 'uscg': 'casualty_class', 'imo': 'severity_description' }[source_db] df['severity_unified'] = df[severity_col].map( severity_maps[source_db] ) # Handle unmapped values df['severity_unified'] = df['severity_unified'].fillna(2) # Default moderate return df ### Root Cause Aggregation Root Cause Category BSEE Term USCG Term IMO Term Human Error Personnel Error Human Factors Human Element Equipment Failure Equipment Failure Material Failure Technical Failure Weather/Environment Environmental Weather External Factors Procedural Procedure Violation Operational Operational/Procedural Design/Engineering Design Deficiency Design Design Related ## Regulatory Compliance Reporting ### Multi-Jurisdiction Reporting Requirements Offshore incidents often trigger reporting obligations to multiple authorities: def determine_reporting_requirements(incident): """ Identify which regulatory authorities must be notified. Args: incident: Dict with keys [location, water_depth, vessel_flag, injury_count, spill_volume, damage_cost] Returns: List of required reports """ required_reports = [] # BSEE reporting (30 CFR 250.188) if incident['location'] == 'OCS': # Outer Continental Shelf if (incident['injury_count'] > 0 or incident['spill_volume'] > 1 or # barrels incident['damage_cost'] > 25000): # USD required_reports.append({ 'authority': 'BSEE', 'regulation': '30 CFR 250.188', 'deadline': '15 minutes (verbal) + 2 hours (written)', 'form': 'Incident of Non-Compliance (INC)' }) # USCG reporting (46 CFR 4.05) if incident['injury_count'] > 0: required_reports.append({ 'authority': 'USCG', 'regulation': '46 CFR 4.05-1', 'deadline': 'Immediately', 'form': 'CG-2692 (Marine Casualty Report)' }) # IMO reporting (SOLAS Chapter V) if incident['vessel_flag'] == 'international': if incident['injury_count'] > 0 or incident['damage_cost'] > 100000: required_reports.append({ 'authority': 'IMO', 'regulation': 'SOLAS V/21', 'deadline': 'Within 7 days', 'form': 'IMO Casualty Report' }) # EPA reporting (40 CFR 110) if incident['spill_volume'] > 0: required_reports.append({ 'authority': 'EPA/NRC', 'regulation': '40 CFR 110.6', 'deadline': 'Immediately', 'form': 'National Response Center notification' }) return required_reports Legal Note: Reporting requirements vary by jurisdiction and incident type. This code provides general guidance only—consult legal counsel for specific compliance obligations. Late or incomplete reporting can result in significant penalties. ## Conclusion Cross-database marine safety incident analysis transforms fragmented regulatory data into comprehensive risk intelligence. The Python-based approaches in this article enable: Entity resolution: Fuzzy matching and IMO number correlation across databases Temporal correlation: Time-window and spatial proximity matching Standardized severity: Unified classification across regulatory schemes Regulatory compliance: Multi-jurisdiction reporting requirement identification Organizations managing offshore operations face increasing regulatory scrutiny and reporting complexity. Automated cross-database correlation provides defensible incident tracking, comprehensive root cause analysis, and proactive risk identification—transforming compliance obligations into strategic safety intelligence. For energy sector consulting projects requiring HSE data integration, we've developed comprehensive incident tracking systems that correlate BSEE, USCG, OSHA, and EPA datasets—delivering unified safety dashboards with automated regulatory reporting workflows. ### About the Author Vamsee Achanta, P.E. is the founder of Analytical & Computational Engineering (AceEngineer), specializing in marine safety analytics and offshore regulatory compliance. With experience integrating multi-agency safety databases, Vamsee helps operators transform fragmented incident data into actionable risk intelligence. Learn more about AceEngineer → ### Need Help with Marine Safety Data Integration? We build automated incident correlation systems that integrate BSEE, USCG, IMO, and proprietary safety databases—transforming regulatory compliance into strategic risk management. Get in Touch More Articles ### Related Articles Energy Sector Consulting - AceEngineer Energy Data Automation Pipelines Gulf of Mexico Production Data Access ## NPV Analysis for Deepwater Field Development | AceEngineer Blog URL: https://www.aceengineer.com/blog/npv-analysis-deepwater-field-development.html Description: NPV and IRR analysis fundamentals for deepwater field development. Python code for decline curves, DCF modeling, sensitivity analysis, and Gulf of Mexico economic evaluation with real examples. # NPV Analysis for Deepwater Field Development: Economics and Python Implementation Author: Vamsee Achanta, P.E. | Published: February 2026 | Reading Time: 15 minutes | Category: Energy Economics Abstract: Deepwater field development requires capital investments of $2-10 billion with project lifecycles spanning 20-30 years. Net Present Value (NPV) and Internal Rate of Return (IRR) analysis are fundamental tools for investment decisions, but deepwater projects introduce unique complexities: multi-phase development, production sharing agreements, and high operating cost sensitivity. This article presents practical Python-based approaches for deepwater economics, from production forecasting to probabilistic sensitivity analysis. ## The Economics of Deepwater Development Deepwater oil and gas projects are among the most capital-intensive industrial undertakings. A typical Gulf of Mexico development includes: Subsea infrastructure: $500M-$1.5B for wells, trees, manifolds, and flowlines Floating production system: $1B-$3B for FPSO, TLP, or spar platform Drilling campaigns: $100M-$200M per well at 5,000+ ft water depth Export pipelines: $500M-$1B depending on distance to shore These massive upfront costs must be recovered through production revenue over decades, making accurate NPV modeling critical for: Investment decisions: Which fields to develop, in what sequence Concept selection: FPSO vs. TLP vs. subsea tieback economics Portfolio optimization: Allocating capital across multiple opportunities Financing: Demonstrating project viability to lenders and partners Key Insight: Deepwater projects are highly sensitive to oil price assumptions—a $10/bbl change can swing NPV by $500M+ for a 100 MMbbl field. Sensitivity analysis and probabilistic modeling are not optional; they're essential for understanding project risk. ## NPV and IRR Fundamentals ### Net Present Value (NPV) NPV discounts future cash flows to present value, accounting for the time value of money: NPV = Σ [Cash Flow_t / (1 + r)^t] - Initial Investment Where: Cash Flow_t = Revenue - Operating Costs - Taxes (in year t) r = Discount rate (typically 8-12% for oil & gas) t = Time period (years) A positive NPV indicates the project creates shareholder value; a negative NPV destroys value. ### Internal Rate of Return (IRR) IRR is the discount rate at which NPV equals zero—representing the project's effective rate of return: 0 = Σ [Cash Flow_t / (1 + IRR)^t] - Initial Investment IRR provides an intuitive comparison metric: if IRR exceeds the company's hurdle rate (required return), the project is economically attractive. ### Comparison: NPV vs. IRR Metric NPV IRR Meaning Absolute value created ($ millions) Rate of return (%) Decision Rule Accept if NPV > 0 Accept if IRR > hurdle rate Scale Consideration Reflects project size Size-independent (can mislead) Multiple Solutions Always unique Can have multiple values (rare) Industry Preference Preferred for final decisions Common for initial screening Important: IRR can be misleading when comparing projects of different scales. A small project with 25% IRR may create less value than a large project with 15% IRR—NPV captures this difference. ## Production Forecasting for DCF Analysis ### Decline Curve Analysis Deepwater wells typically follow hyperbolic or harmonic decline patterns: import numpy as np import pandas as pd def arps_hyperbolic_decline(qi, Di, b, time_months): """ Arps hyperbolic decline equation. Args: qi: Initial production rate (bbl/month) Di: Initial decline rate (fraction/month) b: Hyperbolic exponent (0 to 2, typically 0.3-0.8) time_months: Array of months since first production Returns: Array of production rates """ return qi / ((1 + b * Di * time_months) ** (1 / b)) def forecast_production(qi, Di, b, years=20, economic_limit=50): """ Generate monthly production forecast until economic limit. Args: qi: Initial rate (bbl/day) Di: Annual decline rate (e.g., 0.25 = 25%/year) b: Hyperbolic exponent years: Maximum forecast period economic_limit: Minimum economic rate (bbl/day) Returns: DataFrame with monthly production forecast """ # Convert to monthly parameters qi_monthly = qi * 30.44 # bbl/month Di_monthly = Di / 12 # Generate forecast months = np.arange(0, years * 12) q_monthly = arps_hyperbolic_decline(qi_monthly, Di_monthly, b, months) # Truncate at economic limit limit_monthly = economic_limit * 30.44 mask = q_monthly >= limit_monthly q_monthly = q_monthly[mask] months = months[mask] df = pd.DataFrame({ 'month': months, 'year': months / 12, 'oil_bbl_month': q_monthly, 'oil_bbl_day': q_monthly / 30.44 }) return df ### Multi-Well Type Curves Field-level forecasts aggregate individual well profiles with phased drilling: def field_development_forecast(well_schedule, well_params): """ Aggregate production from multi-well development. Args: well_schedule: DataFrame with columns [well_id, start_month, qi, Di, b] well_params: Dict with economic_limit, max_years Returns: Monthly field production forecast """ max_months = well_params['max_years'] * 12 field_production = np.zeros(max_months) for _, well in well_schedule.iterrows(): # Generate well-specific forecast df_well = forecast_production( qi=well['qi'], Di=well['Di'], b=well['b'], years=well_params['max_years'], economic_limit=well_params['economic_limit'] ) # Add to field profile starting at well's start month start = well['start_month'] for _, row in df_well.iterrows(): month_idx = start + int(row['month']) if month_idx < max_months: field_production[month_idx] += row['oil_bbl_month'] return pd.DataFrame({ 'month': range(max_months), 'year': np.arange(max_months) / 12, 'field_oil_bbl_month': field_production }) ## Discounted Cash Flow (DCF) Model ### Complete NPV Calculation def calculate_npv(production_forecast, economic_params): """ Calculate NPV and IRR for field development. Args: production_forecast: DataFrame with monthly production economic_params: Dict with oil_price, opex_per_bbl, capex_schedule, royalty_rate, tax_rate, discount_rate Returns: Dict with npv, irr, and annual cash flows """ # Aggregate to annual df = production_forecast.copy() df['year_int'] = df['year'].astype(int) df_annual = df.groupby('year_int').agg({ 'field_oil_bbl_month': 'sum' }).reset_index() df_annual.rename(columns={'field_oil_bbl_month': 'oil_bbl_year'}, inplace=True) # Calculate revenue oil_price = economic_params['oil_price'] df_annual['revenue'] = df_annual['oil_bbl_year'] * oil_price # Operating expenses opex_per_bbl = economic_params['opex_per_bbl'] df_annual['opex'] = df_annual['oil_bbl_year'] * opex_per_bbl # Capital expenses (from schedule) capex_schedule = economic_params['capex_schedule'] # Dict: {year: amount} df_annual['capex'] = df_annual['year_int'].map( lambda y: capex_schedule.get(y, 0) ) # Royalties and taxes royalty_rate = economic_params['royalty_rate'] tax_rate = economic_params['tax_rate'] df_annual['royalty'] = df_annual['revenue'] * royalty_rate df_annual['taxable_income'] = ( df_annual['revenue'] - df_annual['royalty'] - df_annual['opex'] - df_annual['capex'] # Simplified: assume full expensing ) df_annual['tax'] = df_annual['taxable_income'].clip(lower=0) * tax_rate # Net cash flow df_annual['cash_flow'] = ( df_annual['revenue'] - df_annual['royalty'] - df_annual['opex'] - df_annual['capex'] - df_annual['tax'] ) # NPV calculation discount_rate = economic_params['discount_rate'] df_annual['discount_factor'] = 1 / (1 + discount_rate) ** df_annual['year_int'] df_annual['pv_cash_flow'] = df_annual['cash_flow'] * df_annual['discount_factor'] npv = df_annual['pv_cash_flow'].sum() # IRR calculation (using numpy_financial if available) try: import numpy_financial as npf irr = npf.irr(df_annual['cash_flow'].values) except ImportError: # Fallback: manual IRR search irr = find_irr(df_annual['cash_flow'].values) return { 'npv': npv, 'irr': irr, 'cash_flows': df_annual, 'total_production': df_annual['oil_bbl_year'].sum(), 'total_revenue': df_annual['revenue'].sum(), 'total_capex': df_annual['capex'].sum() } def find_irr(cash_flows, max_iter=100, tol=1e-6): """Manual IRR calculation using Newton-Raphson.""" irr_guess = 0.1 # Start with 10% for _ in range(max_iter): npv = sum(cf / (1 + irr_guess) ** i for i, cf in enumerate(cash_flows)) npv_derivative = sum( -i * cf / (1 + irr_guess) ** (i + 1) for i, cf in enumerate(cash_flows) ) if abs(npv) < tol: return irr_guess irr_guess -= npv / npv_derivative return None # Failed to converge ## Sensitivity Analysis ### Tornado Diagram Analysis Identify which parameters have the greatest impact on NPV: def sensitivity_analysis(base_params, production_forecast, variables): """ Calculate NPV sensitivity to key variables. Args: base_params: Base case economic parameters production_forecast: Production forecast DataFrame variables: Dict of {param_name: [low_value, high_value]} Returns: DataFrame with sensitivity results for tornado diagram """ results = [] # Base case NPV base_result = calculate_npv(production_forecast, base_params) base_npv = base_result['npv'] # Test each variable for var_name, (low_val, high_val) in variables.items(): # Low case params_low = base_params.copy() params_low[var_name] = low_val npv_low = calculate_npv(production_forecast, params_low)['npv'] # High case params_high = base_params.copy() params_high[var_name] = high_val npv_high = calculate_npv(production_forecast, params_high)['npv'] results.append({ 'variable': var_name, 'base_npv': base_npv, 'npv_low': npv_low, 'npv_high': npv_high, 'swing': abs(npv_high - npv_low), 'downside_risk': base_npv - npv_low, 'upside_potential': npv_high - base_npv }) df_sensitivity = pd.DataFrame(results) df_sensitivity = df_sensitivity.sort_values('swing', ascending=False) return df_sensitivity ### Example: Gulf of Mexico Deepwater Field Parameter Low Case Base Case High Case NPV Swing (±$MM) Oil Price ($/bbl) 60 75 90 ±625 EUR (MMbbl) 80 100 120 ±510 CAPEX ($B) 2.0 2.5 3.0 ±380 OPEX ($/bbl) 18 22 26 ±220 First Oil Delay (months) 0 6 12 ±145 Business Insight: Oil price and EUR dominate project economics—efforts to de-risk reserves (additional appraisal wells, pilot production) can dramatically reduce NPV uncertainty even if CAPEX increases moderately. ## Probabilistic Analysis (Monte Carlo) ### Monte Carlo Simulation Combine uncertainties probabilistically to generate NPV distributions: def monte_carlo_npv(production_forecast_base, base_params, distributions, n_iterations=10000): """ Monte Carlo simulation for NPV uncertainty quantification. Args: production_forecast_base: Base production forecast base_params: Base economic parameters distributions: Dict of {param: (dist_type, params)} e.g., {'oil_price': ('normal', [75, 10])} n_iterations: Number of Monte Carlo draws Returns: DataFrame with NPV distribution and statistics """ npv_results = [] for _ in range(n_iterations): # Draw random parameters mc_params = base_params.copy() for param, (dist_type, dist_params) in distributions.items(): if dist_type == 'normal': value = np.random.normal(*dist_params) elif dist_type == 'lognormal': value = np.random.lognormal(*dist_params) elif dist_type == 'triangular': value = np.random.triangular(*dist_params) else: raise ValueError(f"Unknown distribution: {dist_type}") mc_params[param] = value # Calculate NPV for this draw result = calculate_npv(production_forecast_base, mc_params) npv_results.append(result['npv']) # Statistical analysis npv_array = np.array(npv_results) stats = { 'mean': npv_array.mean(), 'median': np.median(npv_array), 'std': npv_array.std(), 'p10': np.percentile(npv_array, 10), 'p50': np.percentile(npv_array, 50), 'p90': np.percentile(npv_array, 90), 'prob_positive': (npv_array > 0).mean(), 'values': npv_array } return stats Decision Framework: If P90 NPV is positive, the project has strong economics even under pessimistic scenarios. If P50 NPV is negative, the project likely fails to meet hurdle rates even in base case. ## Best Practices for Deepwater Economics ### Model Validation Checklist Verify total EUR matches reservoir engineering estimates Check that peak facility throughput doesn't exceed design capacity Ensure CAPEX schedule aligns with project execution plan Validate tax calculations against fiscal regime (PSA vs. concession) Cross-check NPV against analogous field developments ### Common Pitfalls Optimistic decline curves: Conservative b-factors (0.3-0.5) are more realistic than aggressive (0.8+) Ignoring abandonment costs: Deepwater P&A can cost $50-100M; include in cash flow Static oil prices: Use forward curves or price scenarios, not single point estimates Underestimating OPEX: Deepwater operating costs increase over field life due to water handling Regulatory Note: Gulf of Mexico projects must comply with BSEE royalty reporting and MMS valuation rules. Ensure your economic model correctly calculates royalty basis (wellhead vs. sales point). ## Conclusion Deepwater field development economics demand rigorous NPV and IRR analysis due to massive capital requirements and long project lifecycles. The Python-based approaches in this article provide: Production forecasting: Arps decline curves for individual wells and field-level aggregation DCF modeling: Complete NPV and IRR calculation with CAPEX, OPEX, royalties, and taxes Sensitivity analysis: Identifying key value drivers and quantifying risks Probabilistic modeling: Monte Carlo simulation for uncertainty quantification These tools enable rapid scenario testing, portfolio optimization, and defensible investment decisions. For organizations developing deepwater assets, implementing reproducible economic models transforms ad-hoc spreadsheets into strategic decision support systems. Our energy sector consulting practice has developed comprehensive field development economic models for Gulf of Mexico, West Africa, and Brazil deepwater projects—integrating reservoir engineering, facility design, and fiscal regime analysis into unified NPV frameworks. ### About the Author Vamsee Achanta, P.E. is the founder of Analytical & Computational Engineering (AceEngineer), specializing in field development economics and computational reservoir engineering. With experience evaluating multi-billion dollar deepwater projects, Vamsee helps operators and investors assess project economics using reproducible, auditable methodologies. Learn more about AceEngineer → ### Need Help with Field Development Economics? We build comprehensive NPV models for deepwater field development—from production forecasting to fiscal regime compliance, delivering defensible economics for investment decisions and partner negotiations. Get in Touch More Articles ### Related Articles Energy Sector Consulting - AceEngineer Gulf of Mexico Production Data Access Energy Data Automation Pipelines ## Navigating Offshore Engineering Standards: DNV, API, and Beyond | AceEngineer Engineering Blog URL: https://www.aceengineer.com/blog/offshore-engineering-standards.html Description: Navigate offshore engineering standards including DNV-RP-C203, API RP 2A, BS 7608, and ISO 19901. Learn how automated approaches streamline multi-standard compliance for global offshore projects. # Navigating Offshore Engineering Standards: DNV, API, and Beyond Published: January 13, 2026 | By: Vamsee Achanta, P.E. | Reading Time: 15 minutes | Category: Industry Standards Abstract: Offshore engineering projects must comply with multiple international standards that govern design, fabrication, installation, and operation. DNV-RP-C203, API RP 2A, BS 7608, and ISO 19901 represent different regulatory frameworks with varying requirements, safety factors, and methodologies. This article provides a practical guide to navigating these standards, understanding when each applies, and how automated computational approaches can streamline multi-standard compliance verification for global offshore projects. ## The Standards Landscape: Why Multiple Standards Exist Offshore engineering operates in a complex regulatory environment where geographic location, client requirements, insurance considerations, and classification society preferences all influence which standards apply. Unlike onshore structures governed primarily by local building codes, offshore installations often fall under multiple jurisdictional frameworks simultaneously. Key factors driving standard selection: Geographic Region: Gulf of Mexico projects typically follow API standards, while North Sea installations adhere to DNV or BS frameworks Classification Society: DNV, ABS, Lloyd's, and Bureau Veritas each recognize different standards as primary references Operator Requirements: Major operators often specify preferred standards based on their global fleet consistency Insurance and Liability: Underwriters may require specific standards for coverage compliance National Regulations: Some jurisdictions mandate specific standards through legislation Practical Reality: Most offshore projects require demonstrating compliance with multiple standards simultaneously. A floating production system in West Africa might need to satisfy API requirements for the U.S.-based operator, DNV standards for the classification society, and local regulatory frameworks for the host country. ## Overview of Key Offshore Engineering Standards ### DNV-RP-C203: Fatigue Design of Offshore Steel Structures #### DNV-RP-C203 (2021 Edition) Scope: Fatigue assessment of welded and non-welded steel structures in offshore applications Key Features: S-N curves based on extensive laboratory testing and field experience from North Sea installations Design Fatigue Factors (DFF) ranging from 1.0 to 10.0 depending on structural criticality and inspection accessibility Detailed guidance on stress concentration factors (SCFs) for tubular joints Thickness correction factors for plates exceeding 25mm reference thickness Environmental effects including cathodic protection and free corrosion conditions S-N Curve Categories: B1, B2, C, C1, C2, D, E, F, F1, F3, G, W1, W2, W3, T Typical Applications: Fixed platforms, jackets, topsides, risers, mooring systems, subsea structures DNV-RP-C203 provides the most comprehensive treatment of offshore fatigue analysis, with detailed guidance for complex joint geometries common in tubular steel structures. The standard distinguishes between "as-welded" and "improved" weld conditions, acknowledging that post-weld treatments like grinding, hammer peening, or TIG dressing can significantly extend fatigue life. ### API RP 2A-WSD: Planning, Designing, and Constructing Fixed Offshore Platforms #### API RP 2A-WSD (22nd Edition, 2014) Scope: Complete design guidance for fixed offshore platforms using Working Stress Design methodology Key Features: Working Stress Design (WSD) approach with explicit safety factors on allowable stresses X and X' S-N curves for tubular connections derived from Gulf of Mexico experience Simplified SCF equations (Kuang, Wordsworth/Smedley, Efthymiou) Punching shear methodology for joint capacity assessment Comprehensive environmental loading criteria including wave, wind, current, and seismic Design Philosophy: Allowable stress = Yield stress / Safety factor (typically 0.6 for tension) Typical Applications: Fixed steel platforms in Gulf of Mexico and similar shallow water environments API RP 2A remains the dominant standard for fixed platform design in the Americas, with decades of successful application history. The companion API RP 2A-LRFD provides Load and Resistance Factor Design alternatives, while API RP 2MET addresses metocean criteria. ### BS 7608: Fatigue Design and Assessment of Steel Structures #### BS 7608:2014+A1:2015 Scope: General fatigue design methodology for steel structures including offshore applications Key Features: Classification system based on structural detail categories (B through W) Probability-based approach with mean minus two standard deviation (mean-2SD) S-N curves Variable amplitude loading assessment using Palmgren-Miner cumulative damage rule Guidance on assessment of existing structures and remaining life evaluation Consideration of size effects and thickness penalties Statistical Basis: S-N curves represent 97.7% survival probability (mean - 2 standard deviations) Typical Applications: Bridges, cranes, offshore structures, pressure vessels, general steel fabrications BS 7608 provides broader applicability than offshore-specific standards, making it valuable for components that might be used in multiple industries. The standard's classification system aligns closely with European standards and Eurocode 3 fatigue provisions. ### ISO 19901 Series: Petroleum and Natural Gas Industries #### ISO 19901: Offshore Structures Standards Suite Scope: Comprehensive framework for offshore structural design, construction, and operation Key Parts: ISO 19901-1: Metocean design and operating considerations ISO 19901-2: Seismic design procedures and criteria ISO 19901-3: Topsides structure design ISO 19901-4: Geotechnical and foundation design ISO 19901-5: Weight management ISO 19901-6: Marine operations ISO 19901-7: Station-keeping systems for floating structures ISO 19902: Fixed steel offshore structures (incorporating API RP 2A concepts) Design Philosophy: Harmonized international approach incorporating best practices from regional standards Typical Applications: International projects requiring standardized methodology across multiple regions ISO 19901 represents an effort to harmonize offshore engineering practice globally. ISO 19902, in particular, incorporates much of API RP 2A-LRFD while adding international consensus modifications. Many operators now specify ISO standards for new projects to ensure consistency across their global portfolio. ## Comparing Standards: Key Technical Differences Aspect DNV-RP-C203 API RP 2A BS 7608 ISO 19902 Design Philosophy Limit state with DFF Working stress (WSD) or LRFD Allowable stress with partial factors Limit state (LRFD) S-N Curve Basis Mean minus 2 std dev Mean minus 2 std dev Mean minus 2 std dev Mean minus 2 std dev Reference Thickness 25mm (penalty for thicker) 16mm (implicit) 16mm (explicit correction) 25mm (aligned with DNV) SCF Methodology Efthymiou equations Multiple options (Kuang, Efthymiou) General guidance Efthymiou (preferred) Corrosion Treatment Explicit curves for different environments Implicit through S-N selection General guidance Aligned with DNV approach Weld Improvement Credit Detailed guidance with factors Limited guidance General principles Follows DNV approach Damage Accumulation Miner's rule (D ≤ 1/DFF) Miner's rule (D ≤ 1.0) Miner's rule with guidance Miner's rule with factors Critical Warning: S-N curves from different standards are NOT directly interchangeable, even when they appear similar. Differences in reference thickness, statistical basis, stress definitions (nominal vs. hot-spot), and environmental assumptions mean that mixing curves from different standards can produce non-conservative or overly conservative results. ## Conclusion: Standards as Engineering Foundation Offshore engineering standards represent decades of accumulated industry experience, research, and lessons learned from both successes and failures. Navigating multiple standards effectively requires understanding not just what the codes say, but why they differ and when each is most appropriate. Automated computational approaches do not replace engineering judgment-they amplify it. By automating routine compliance checks and enabling rapid multi-standard comparison, engineers can focus on the complex interpretive decisions where human expertise is essential. For global offshore projects, multi-standard compliance is not optional-it's a fundamental requirement. The question is whether that compliance is achieved through manual, error-prone processes or through systematic, validated computational workflows. ### About the Author Vamsee Achanta, P.E. is an engineer specializing in offshore structural analysis, fatigue assessment, and automated computational methods. With experience applying DNV, API, ISO, and BS standards to fixed and floating offshore structures, he focuses on making rigorous standards compliance accessible through transparent, validated computational tools. Read more about AceEngineer or view code on GitHub ### Need Multi-Standard Compliance Support? We help engineering teams navigate complex standards requirements for offshore projects. Whether you need fatigue analysis per DNV-RP-C203, API RP 2A compliance verification, or multi-standard comparison studies, we can help. Back to Blog Discuss Your Project ## Open-Source Engineering Tools: Building Transparent Computational Methods - AceEngineer URL: https://www.aceengineer.com/blog/open-source-engineering-tools.html Description: Why open-source engineering tools matter for transparency, validation, and trust. Explore the aceengineer GitHub organization and how engineers can use and contribute to computational methods. # Open-Source Engineering Tools: Building Transparent Computational Methods Author: Vamsee Achanta, P.E. | Published: January 2025 | Reading Time: 10 minutes | Category: Open-Source Engineering When an engineering consultant delivers analysis results, how do you know the calculations are correct? Traditional approaches rely on trust, credentials, and spot-checking sample calculations. Open-source engineering tools offer something better: complete transparency into the computational methods behind the results. This article explores why open-source matters for engineering software, introduces our GitHub repositories for structural analysis and fatigue assessment, and explains how engineers can use and contribute to these tools. Whether you're evaluating engineering consultants or looking to improve your own computational workflows, understanding the open-source advantage is increasingly important. ## Why Open-Source Matters in Engineering Engineering software has traditionally been proprietary. Commercial FEA packages, fatigue analysis tools, and structural design software come as compiled binaries with closed source code. You input parameters, run the analysis, and receive results—but the actual calculations remain hidden in a black box. This creates several problems: Validation challenges: How do you verify that a commercial tool correctly implements the equations in your design code? You can run benchmark problems, but you can't examine the implementation directly. Debugging difficulties: When results look suspicious, you can't trace through the calculation logic to find where things went wrong. Vendor lock-in: Your analysis workflows become dependent on specific commercial tools. Switching vendors means revalidating everything. Limited customization: If the tool doesn't support your specific use case, you're stuck waiting for the vendor to add features. Open-source engineering tools address all of these issues. The source code is available for inspection, modification, and improvement. When you see suspicious results, you can trace the exact calculation path. When you need custom functionality, you can add it yourself. ## The Trust Problem in Engineering Consulting Consider the perspective of an engineering manager evaluating consultants for a critical offshore structure analysis. The consultant delivers a fatigue assessment report showing adequate design life. How do you evaluate the quality of that work? The Trust Gap: Traditional consulting relationships rely heavily on credentials and reputation. But even experienced consultants can make errors, use outdated methods, or misapply design codes. Without access to the underlying calculations, clients must accept results on faith. Open-source methodologies change this dynamic. When a consultant uses open-source tools and publishes their calculation scripts, clients can: Review the exact algorithms used in the analysis Verify compliance with design codes and standards Run independent checks using the same methodology Identify assumptions and limitations in the analysis Reproduce results with different inputs for verification This transparency doesn't replace engineering judgment—it enables it. When you can see exactly how a result was calculated, you can apply your own expertise to evaluate whether the approach is appropriate for your specific situation. ## Our GitHub Organization We maintain several open-source repositories for computational engineering on GitHub. These tools reflect our production methodologies—the same code we use for client projects is available for inspection and use. ### fatigue-analysis A Python library for fatigue life assessment of welded structures. Implements S-N curve methods per DNV-RP-C203, rainflow cycle counting, stress concentration factors for common joint types, and cumulative damage calculations using Miner's rule. Hot spot stress extraction from FEA results Rainflow counting for variable amplitude loading Multiple S-N curve options (DNV, BS, API) Thickness correction and environmental factors Automated report generation View the fatigue module ### fea-postprocessing Tools for automating FEA post-processing workflows. Reads results from common formats (CSV exports from ANSYS, Abaqus, etc.), performs code checks, and generates structured output for reporting. Multi-format result file parsing Automated stress categorization (membrane, bending, peak) Code compliance checking (API, ASME, DNV) Interactive visualization with Plotly Batch processing for parameter studies ### engineering-calcs A collection of validated engineering calculations for common structural problems. Each calculation includes derivation references, validation against hand calculations or published examples, and unit tests. Beam and plate stress calculations Pressure vessel formulas (ASME Section VIII) Connection design checks Marine structure calculations (hydrostatics, stability) Environmental loading (wind, wave, current) View Repository ## Open-Source vs. Proprietary: A Comparison Let's compare open-source and proprietary approaches across several dimensions that matter for engineering work: Criterion Proprietary Software Open-Source Tools Transparency Black box calculations Full source code visibility Validation Trust vendor testing Review implementation directly Customization Limited to vendor features Modify for specific needs Cost License fees (often $10K+/year) Free (development time investment) Support Vendor helpdesk Community + consultants Longevity Depends on vendor viability Code persists indefinitely Integration Often limited APIs Full programmatic access The Real Trade-off: Proprietary tools often have polished interfaces and extensive feature sets developed over decades. Open-source tools require more technical skill to use but offer complete control and transparency. For organizations with Python capability, the combination is powerful: use commercial FEA for meshing and solving, then open-source tools for post-processing and reporting. ## How to Use Our Tools Getting started with our engineering tools requires basic Python knowledge. Here's a typical workflow for fatigue analysis: ### Installation # Clone the repository git clone https://github.com/vamseeachanta/fatigue.git cd fatigue # Install dependencies pip install -r requirements.txt # Run tests to verify installation pytest tests/ ### Basic Usage Example from fatigue import SNAnalysis, RainflowCounter from fatigue.standards import DNV_RP_C203 # Load stress history from FEA results stress_history = load_stress_time_series("stress_results.csv") # Perform rainflow counting counter = RainflowCounter() cycles = counter.count(stress_history) # Configure S-N curve per DNV-RP-C203 sn_curve = DNV_RP_C203.get_curve( joint_type="tubular_t_butt", environment="seawater_cathodic_protection", thickness=25.0 # mm ) # Calculate fatigue damage analysis = SNAnalysis(sn_curve=sn_curve) damage = analysis.calculate_damage(cycles) print(f"Cumulative fatigue damage: {damage:.4f}") print(f"Predicted design life: {1/damage:.1f} years") ### Validation and Testing Every function includes unit tests with documented validation cases. For example, our S-N curve implementation is validated against: Hand calculations from DNV-RP-C203 examples Published benchmark problems from industry papers Cross-validation with commercial fatigue software Sensitivity studies for numerical accuracy def test_dnv_c203_example_5_1(): """ Validates against DNV-RP-C203 Example 5.1: Fatigue assessment of a tubular joint. Reference result: D = 0.127 """ sn_curve = DNV_RP_C203.get_curve("tubular_t_butt") cycles = [(180, 1e5), (120, 5e5), (80, 2e6)] damage = calculate_miner_damage(cycles, sn_curve) assert abs(damage - 0.127) < 0.005 # Within 0.5% of reference ## Contributing to the Tools We welcome contributions from the engineering community. Whether you find a bug, want to add a feature, or have a better implementation of an existing function, contributions improve the tools for everyone. ### Ways to Contribute Bug reports: Found incorrect results? Open an issue with a minimal reproducible example. Documentation: Improve docstrings, add examples, or fix typos. New features: Propose additions via GitHub issues before implementing. Validation cases: Add test cases from published benchmarks or standards examples. Code review: Review open pull requests and provide feedback. ### Contribution Process # Fork the repository on GitHub, then: git clone https://github.com/YOUR_USERNAME/fatigue.git cd fatigue git checkout -b feature/your-feature-name # Make changes, add tests # ... # Run tests locally pytest tests/ # Commit and push git add . git commit -m "Add feature: description of changes" git push origin feature/your-feature-name # Open a pull request on GitHub All contributions require tests. For calculation functions, tests must include validation against published references or analytical solutions. We maintain a high bar for accuracy—these tools are used in safety-critical applications. ## The Future of Engineering Software The engineering software landscape is shifting. Several trends favor open-source approaches: Python adoption: Python has become the de facto language for scientific computing. Engineers increasingly have the skills to use and contribute to open-source tools. Cloud computing: Browser-based tools and cloud execution make it easier to deploy open-source software without local installation hassles. Regulatory pressure: Some jurisdictions now require transparency in computational methods for safety-critical applications. AI/ML integration: Machine learning models require transparent training pipelines. Open-source tools integrate naturally with modern ML frameworks. We don't expect open-source to replace commercial FEA solvers—the development investment in those tools is measured in hundreds of engineer-years. But for post-processing, reporting, code checking, and specialized calculations, open-source tools offer compelling advantages. ## Conclusion Open-source engineering tools represent a fundamental shift in how computational methods are developed, validated, and shared. Transparency builds trust. Validation becomes verifiable. Custom requirements become achievable. For engineering decision-makers evaluating consultants, ask about their computational methods. Do they use proprietary black boxes exclusively, or do they employ transparent methodologies that can be independently verified? The answer reveals something about their commitment to quality and accountability. For practicing engineers, consider contributing to open-source tools in your domain. The collective benefit of shared, validated computational methods far exceeds the individual investment. When the next engineer validates your implementation against a new benchmark problem, they strengthen the tools that everyone uses. Explore our repositories on GitHub. Try the tools on your own problems. Open issues when you find problems. Submit pull requests when you have improvements. Together, we can build engineering software that's as transparent as the calculations it performs. ### About the Author Vamsee Achanta, P.E. is the founder of Analytical & Computational Engineering (AceEngineer), specializing in computational engineering solutions for the energy industry. With 25+ years of experience in offshore and subsea engineering, he develops open-source tools for structural analysis, fatigue assessment, and engineering automation. Contact for consulting inquiries | GitHub | LinkedIn ### Related Articles AI-Native Structural Analysis: Why Traditional FEA is Changing Machine Learning for Fatigue Life Prediction: Beyond S-N Curves Python Engineering Automation: From Manual Workflows to Reproducible Analysis ← Back to Blog ## Python Engineering Automation: From Manual Workflows to Reproducible Analysis - AceEngineer URL: https://www.aceengineer.com/blog/python-engineering-automation.html Description: How Python automation transforms engineering workflows. Learn practical approaches to automate FEA post-processing, report generation, and data analysis with real code examples. # Python Engineering Automation: From Manual Workflows to Reproducible Analysis Author: Vamsee Achanta, P.E. | Published: January 2025 | Reading Time: 12 minutes | Category: Engineering Automation Every engineer knows the pain: running the same analysis with slightly different parameters, manually copying results into spreadsheets, reformatting reports for each project. These repetitive tasks consume hours that could be spent on actual engineering judgment. Python automation changes this equation fundamentally. This isn't about replacing engineering expertise with code—it's about amplifying that expertise. When you automate the mechanical parts of your workflow, you free cognitive resources for the decisions that actually require engineering judgment. The result is faster turnaround, fewer errors, and reproducible analyses that can be audited and improved over time. ## The Hidden Cost of Manual Workflows Consider a typical structural analysis workflow. You run an FEA model, export results to CSV, open Excel, create plots, copy values into a Word template, format tables, and generate a PDF. This might take 2-4 hours for a routine analysis. Now imagine a design iteration requires re-running the analysis with modified loads. You repeat the entire process. Parameter study with 10 variations? That's 20-40 hours of mechanical work. The Real Problem: Manual workflows don't just waste time—they introduce errors. Each manual step is an opportunity for copy-paste mistakes, formula errors, or inconsistent formatting. These errors are hard to catch and harder to audit. Python automation addresses both problems simultaneously. A well-designed automation script runs in seconds, produces consistent output, and creates an auditable record of exactly how results were generated. ## Building Your First Engineering Automation Let's start with a practical example: automating FEA post-processing. Assume you have stress results exported from your FEA software as CSV files. ### Step 1: Reading and Processing FEA Results import pandas as pd import numpy as np from pathlib import Path def load_fea_results(filepath: str) -> pd.DataFrame: """ Load FEA stress results from CSV export. Handles common export formats from ANSYS, Abaqus, and similar tools. """ df = pd.read_csv(filepath) # Standardize column names column_mapping = { 'Node': 'node_id', 'S11': 'stress_xx', 'S22': 'stress_yy', 'S33': 'stress_zz', 'S12': 'stress_xy', 'S_MISES': 'von_mises', 'S_MAX_PRINCIPAL': 'max_principal' } df = df.rename(columns=column_mapping) return df def calculate_stress_metrics(df: pd.DataFrame) -> dict: """ Calculate key stress metrics for reporting. """ return { 'max_von_mises': df['von_mises'].max(), 'mean_von_mises': df['von_mises'].mean(), 'max_principal': df['max_principal'].max(), 'nodes_above_yield': len(df[df['von_mises'] > YIELD_STRENGTH]), 'stress_ratio': df['von_mises'].max() / ALLOWABLE_STRESS } ### Step 2: Automated Visualization Static matplotlib plots are fine for exploration, but engineering reports need consistent, professional visualizations. Here's how to generate them automatically: import plotly.graph_objects as go import plotly.express as px def create_stress_distribution_plot(df: pd.DataFrame, output_path: str): """ Generate interactive stress distribution plot. """ fig = go.Figure() fig.add_trace(go.Histogram( x=df['von_mises'], nbinsx=50, name='Von Mises Stress Distribution', marker_color='#428bca' )) # Add vertical lines for key thresholds fig.add_vline(x=YIELD_STRENGTH, line_dash="dash", line_color="red", annotation_text="Yield") fig.add_vline(x=ALLOWABLE_STRESS, line_dash="dash", line_color="orange", annotation_text="Allowable") fig.update_layout( title='Stress Distribution Analysis', xaxis_title='Von Mises Stress (MPa)', yaxis_title='Node Count', template='plotly_white' ) fig.write_html(output_path) return fig def create_contour_plot(df: pd.DataFrame, x_col: str, y_col: str, stress_col: str, output_path: str): """ Generate 2D contour plot for spatial stress visualization. """ fig = go.Figure(data=go.Contour( x=df[x_col], y=df[y_col], z=df[stress_col], colorscale='Viridis', colorbar=dict(title='Stress (MPa)') )) fig.update_layout( title=f'{stress_col} Contour Plot', xaxis_title='X Position (m)', yaxis_title='Y Position (m)' ) fig.write_html(output_path) return fig ### Step 3: Automated Report Generation The final piece is generating professional reports automatically. Using Jinja2 templates with HTML output gives you flexibility and consistency: from jinja2 import Environment, FileSystemLoader from datetime import datetime def generate_analysis_report( project_name: str, results: dict, plots: list, output_path: str ): """ Generate HTML analysis report from template. """ env = Environment(loader=FileSystemLoader('templates')) template = env.get_template('stress_analysis_report.html') report_data = { 'project_name': project_name, 'date': datetime.now().strftime('%Y-%m-%d'), 'analyst': 'Vamsee Achanta', 'results': results, 'plots': plots, 'pass_fail': 'PASS' if results['stress_ratio'] < 1.0 else 'FAIL', 'utilization': f"{results['stress_ratio']*100:.1f}%" } html_content = template.render(**report_data) with open(output_path, 'w') as f: f.write(html_content) return output_path ## Scaling to Complex Workflows Individual automation scripts are useful, but the real power comes from composing them into complete workflows. Here's a pattern we use for production engineering automation: from dataclasses import dataclass from typing import List, Optional import yaml @dataclass class AnalysisConfig: """Configuration for automated analysis run.""" project_id: str input_files: List[str] material_properties: dict load_cases: List[str] output_directory: str report_template: str @classmethod def from_yaml(cls, filepath: str) -> 'AnalysisConfig': with open(filepath) as f: data = yaml.safe_load(f) return cls(**data) class AnalysisPipeline: """ Orchestrates complete analysis workflow. """ def __init__(self, config: AnalysisConfig): self.config = config self.results = {} self.plots = [] def run(self) -> str: """Execute complete analysis pipeline.""" # Step 1: Load and validate inputs self._validate_inputs() # Step 2: Process each load case for load_case in self.config.load_cases: self._process_load_case(load_case) # Step 3: Generate comparative analysis self._comparative_analysis() # Step 4: Generate report report_path = self._generate_report() return report_path def _process_load_case(self, load_case: str): """Process single load case through analysis pipeline.""" # Load FEA results results_file = f"{self.config.input_files}/{load_case}_results.csv" df = load_fea_results(results_file) # Calculate metrics metrics = calculate_stress_metrics(df) self.results[load_case] = metrics # Generate plots plot_path = f"{self.config.output_directory}/{load_case}_stress.html" create_stress_distribution_plot(df, plot_path) self.plots.append(plot_path) ## Essential Python Libraries for Engineering Building effective engineering automation requires the right tools. Here are the libraries we use daily: Category Library Use Case Data Processing pandas, numpy Tabular data, numerical arrays, time series Visualization plotly, matplotlib Interactive plots, publication figures Scientific Computing scipy, sympy Optimization, symbolic math, signal processing Report Generation jinja2, weasyprint HTML templates, PDF generation Configuration pyyaml, pydantic Config files, data validation FEA Integration meshio, pygmsh Mesh I/O, mesh generation Units & Standards pint, uncertainties Unit conversion, error propagation ## Real-World Impact: A Case Study We recently automated the fatigue assessment workflow for an offshore platform leg structure. The original manual process took approximately 16 hours per load case combination—loading results, extracting hot spot stresses, calculating SCFs, running rainflow counting, computing fatigue damage, and generating the assessment report. The automated pipeline reduced this to 12 minutes. More importantly, it enabled a 200-case parameter study that would have been impractical manually. The study revealed an unexpected loading combination with high fatigue damage that wasn't in the original design basis—a finding that led to a design modification before fabrication. Time Savings: 16 hours → 12 minutes per analysis (80x faster) Error Reduction: Zero manual transcription errors Scope Expansion: 200-case study vs. planned 5-case spot check ## Best Practices for Engineering Automation ### 1. Configuration Over Code Put project-specific parameters in YAML configuration files, not in code. This makes it easy to run the same analysis with different inputs without modifying scripts. # project_config.yaml project_id: "OFFSHORE-2024-001" material: yield_strength: 355 # MPa allowable_stress: 236.7 # MPa (0.67 * Fy per API) youngs_modulus: 210000 # MPa load_cases: - "operating_wave" - "storm_wave" - "earthquake" output: report_template: "templates/api_stress_check.html" output_directory: "results/stress_analysis" ### 2. Validate Inputs Early Use Pydantic or similar libraries to validate inputs at the start of your pipeline. Fail fast with clear error messages rather than producing garbage output. from pydantic import BaseModel, validator class MaterialProperties(BaseModel): yield_strength: float allowable_stress: float youngs_modulus: float @validator('allowable_stress') def check_allowable_vs_yield(cls, v, values): if v >= values.get('yield_strength', float('inf')): raise ValueError('Allowable stress must be less than yield') return v ### 3. Log Everything Engineering analyses need audit trails. Use Python's logging module to record what was computed, with what inputs, and when. import logging logging.basicConfig( filename='analysis.log', level=logging.INFO, format='%(asctime)s - %(levelname)s - %(message)s' ) logger = logging.getLogger(__name__) def run_stress_check(load_case: str, config: dict): logger.info(f"Starting stress check for {load_case}") logger.info(f"Using allowable stress: {config['allowable_stress']} MPa") # ... analysis code ... logger.info(f"Stress check complete. Utilization: {utilization:.1f}%") logger.info(f"Result: {'PASS' if utilization < 100 else 'FAIL'}") ### 4. Version Control Your Automation Treat automation scripts like production code. Use Git, write tests, and document your functions. When a client asks "how was this calculated?" you should be able to show them the exact code version used. ## Getting Started If you're new to Python automation, start small: Identify your pain point: What repetitive task costs you the most time? Prototype manually: Work through the automation logic in a Jupyter notebook Extract functions: Convert working notebook cells into reusable functions Add configuration: Move hardcoded values to a config file Add logging and validation: Make it production-ready We publish open-source engineering automation tools on our GitHub. The digitalmodel library provides a foundation for building engineering analysis pipelines. ## Conclusion Python automation isn't about replacing engineering judgment—it's about removing the barriers that prevent you from applying that judgment effectively. When routine tasks run in seconds instead of hours, you can explore more design alternatives, catch more edge cases, and deliver more thorough analyses. The investment in learning automation pays compound returns. Each script you write saves time on every future project. Each pattern you develop becomes a building block for more sophisticated workflows. And the reproducibility of automated analyses builds trust with clients and regulators. Start with one workflow. Automate it completely. Then move to the next. Within a few months, you'll wonder how you ever worked any other way. ### About the Author Vamsee Achanta, P.E. is the founder of Analytical & Computational Engineering (AceEngineer), specializing in computational engineering solutions for the energy industry. With 25+ years of experience in offshore and subsea engineering, he develops open-source tools for structural analysis, fatigue assessment, and engineering automation. Contact for consulting inquiries | GitHub | LinkedIn ### Related Articles Open-Source Engineering Tools: Building Transparent Computational Methods AI-Native Structural Analysis: Why Traditional FEA is Changing Machine Learning for Fatigue Life Prediction: Beyond S-N Curves ← Back to Blog ## Risk-Based Inspection for Offshore Structures: AI-Enhanced Approaches | AceEngineer Engineering Blog URL: https://www.aceengineer.com/blog/risk-based-inspection-planning.html Description: Learn how AI-enhanced risk-based inspection (RBI) optimizes offshore inspection programs. Covers probability of failure modeling, consequence assessment, and inspection scheduling strategies. # Risk-Based Inspection for Offshore Structures: AI-Enhanced Approaches Published: January 2026 | Author: Vamsee Achanta, P.E. | Reading Time: 14 minutes | Category: Structural Integrity Offshore inspection programs face a fundamental tension: inspect too little and risk catastrophic failures; inspect too much and waste resources while potentially introducing handling damage. Risk-based inspection (RBI) resolves this tension by focusing inspection efforts where they matter most. AI-enhanced approaches take this further, enabling dynamic prioritization based on operational data, environmental conditions, and predictive models. ## The Case for Risk-Based Inspection Traditional time-based inspection schedules treat all components equally. Every joint gets inspected on the same calendar cycle regardless of its criticality, loading history, or degradation mechanisms. This approach has significant drawbacks: Resource inefficiency: 80% of inspection effort may go to components with minimal failure probability Coverage gaps: High-risk components may not receive adequate attention within standard intervals False confidence: Passing inspections on low-risk components doesn't address actual failure modes Operational disruption: Blanket inspection campaigns maximize platform downtime RBI inverts this approach. By quantifying both the probability and consequence of failure for each component, inspection resources concentrate on high-risk items while safely extending intervals for low-risk components. ### Typical RBI Results 20-40% reduction in overall inspection scope Improved detection of actual degradation in critical areas Extended intervals for low-risk components (often 2-3x standard) Reduced operational impact through focused campaigns ## RBI Framework: The Fundamentals Risk-based inspection follows a structured methodology defined in industry standards. The core equation is deceptively simple: Risk = Probability of Failure (PoF) x Consequence of Failure (CoF) The challenge lies in quantifying both terms rigorously for offshore structures with multiple degradation mechanisms, uncertain loading histories, and complex failure modes. ### Consequence of Failure Assessment Consequence assessment considers multiple impact categories: #### Safety Consequences Personnel injury/fatality potential Evacuation requirements Emergency response demands #### Environmental Consequences Hydrocarbon release volume Spill trajectory and impact Sensitive receptor proximity #### Economic Consequences Production loss duration Repair/replacement costs Regulatory penalties #### Reputational Consequences Media visibility Stakeholder relationships License to operate ### Risk Matrix Application Combining PoF and CoF yields risk rankings that drive inspection prioritization: PoF \ CoF Low Medium High Very High Very High Medium Medium-High High High High Low Medium Medium-High High Medium Low Low Medium Medium-High Low Low Low Low Medium ## AI-Enhanced RBI: Beyond Static Assessment Traditional RBI assessments are periodic snapshots. AI-enhanced approaches enable continuous risk updating based on real-time data streams. This transforms RBI from a planning exercise into a dynamic decision support system. ## Conclusion Risk-based inspection transforms offshore integrity management from calendar-driven compliance to risk-informed decision-making. AI enhancement enables dynamic updating, better prediction, and more efficient resource allocation. The key is rigorous methodology, quality data, and transparent validation. For organizations managing aging offshore assets, AI-enhanced RBI offers a path to improved safety outcomes at reduced cost. The technology is mature enough for deployment but requires careful implementation with appropriate engineering oversight. ### Related Resources Machine Learning for Fatigue Life Prediction Digital Twins for Offshore Asset Integrity Navigating Offshore Engineering Standards S-N Curve Fatigue Life Calculator Case Study: Offshore Platform Fatigue Assessment ### About the Author Vamsee Achanta, P.E., is a structural engineer specializing in computational methods for offshore and marine engineering. With experience in fatigue analysis, structural integrity management, and automated workflows, he helps organizations leverage data-driven approaches to improve engineering outcomes. Read more about AceEngineer or view code on GitHub ## Decline Curve & EUR Calculator (Arps) - AceEngineer URL: https://www.aceengineer.com/calculators/decline-curve.html Description: Arps decline curve and EUR calculator. Exponential, hyperbolic, and harmonic decline with closed-form cumulative production to an economic limit, plus interactive rate-vs-time forecast. # Decline Curve & EUR Calculator Arps decline (exponential / hyperbolic / harmonic) with closed-form EUR to an economic limit Arps Decline EUR Production Forecast ## Input Parameters Initial Rate qi Initial production rate (generic rate units, e.g. bbl/d or Mscf/d). Rate Unit Per day (rate x 365 for annual volume) Per year (cumulative in rate × year) Di is always a nominal ANNUAL decline. Per-day rates are multiplied by 365 so EUR is in the rate's own volume unit. Initial Nominal Decline Di (% per year) Entered as percent per year (e.g. 10 = 0.10 /yr). b-exponent 0 = exponential, 0 tref with the class exponent k Environment In Air Seawater with Cathodic Protection Seawater, Free Corrosion Curves per DNV-RP-C203 (2011) Table 2-1 (air), Table 2-2 (cathodic protection) and Table 2-3 (free corrosion) Calculate Fatigue Life S-N Curve Parameters (DNV-RP-C203): log(a1) = 12.164, m1 = 3, log(a2) = 15.606, m2 = 5 Calculated Fatigue Life -- cycles ### Calculation Details Thickness Correction Factor 1.000 Environment Curve In-air curve Corrected Stress Range -- MPa S-N Curve Regime -- log(N) -- S-N Curve Equation: log(N) = log(a) - m x log(S) Thickness Correction: Scorrected = S x (t/tref)^(k) for t > tref, where tref = 25 mm (32 mm for the T curve) and k is the class exponent (DNV-RP-C203 section 2.4.3) Note: In air and in seawater with cathodic protection this calculator uses the two-slope S-N curves of DNV-RP-C203: slope m1 changes to m2 = 5 at N = 10^7 cycles in air and N = 10^6 cycles with cathodic protection. Free-corrosion curves are single slope, m = 3. Below 10^5 cycles, air and cathodic-protection lives are capped at the B1 curve of the same environment. ## About S-N Curve Fatigue Analysis S-N curves (also called Wohler curves) describe the relationship between applied stress range and the number of cycles to failure for a given structural detail. The fatigue life N at a constant amplitude stress range S is calculated using: N = a / S^(m) or in logarithmic form: log(N) = log(a) - m x log(S) Where: N = Number of cycles to failure S = Stress range (MPa) a = S-N curve intercept (material/detail dependent) m = S-N curve slope (typically 3 for high-cycle fatigue) ### S-N Curve Classifications The S-N curve classification (B1 through W3, plus T for tubulars) represents the fatigue strength of different weld geometries and structural details. Key classifications include: B1-B2: Base material and ground butt welds (highest fatigue strength) C-C2: Butt welds with different finishing quality D: Most common for fillet welded offshore structures E-F3: Attachments and details with geometric stress risers G: Partial penetration welds W1-W3: Weld root details (most critical) T: Tubular joint hot-spot stress method ### Thickness Correction For plates thicker than the reference thickness tref, a thickness correction is applied to account for increased probability of defects and stress gradient effects: Scorrected = S x (t/tref)^(k) The correction applies only for t > tref. Per DNV-RP-C203 (2011) section 2.4.3, tref = 25 mm for welded connections other than tubular joints and 32 mm for tubular joints (T curve). The exponent k depends on the curve class (Tables 2-1 to 2-3): k = 0 for B1 and B2 (no correction), 0.15 for C, C1 and C2, 0.20 for D and E, and 0.25 for F to W3. For the T curve, k = 0.25 for SCF ≤ 10 and 0.30 for SCF > 10; this calculator has no SCF input and assumes SCF ≤ 10 (k = 0.25). The correction reduces the allowable fatigue life for thicker sections. ### Environment Effects Seawater environment significantly affects fatigue performance: In Air: Baseline S-N curve applies Seawater with CP: Approximately 2-3x reduction in fatigue life Free Corrosion: Approximately 3-4x reduction (avoid in design) ### Limitations This calculator provides preliminary estimates based on constant amplitude loading. For actual design: Variable amplitude loading requires rainflow counting and damage accumulation (Miner's rule) Stress concentration factors may need to be applied for hot-spot stress method Mean stress effects may be significant for high R-ratios Final design should be verified by qualified engineers Disclaimer: This calculator is for educational purposes only. All final engineering calculations should be performed by qualified engineers and verified against the applicable design codes. ## Need Professional Fatigue Analysis? For complex fatigue assessments involving variable amplitude loading, FEA-based hot-spot stress analysis, or advanced fatigue prediction, we offer professional consulting services. Discuss Your Project View Fatigue Case Study Learn About ML for Fatigue ## S-N Curve Fatigue Calculator - AceEngineer URL: https://www.aceengineer.com/calculators/fatigue-sn-curve.html Description: Interactive S-N curve fatigue calculator. Calculate fatigue life using DNV, API, BS 7608, and other international standards. Engineering tool. # S-N Curve Fatigue Calculator Calculate fatigue life using industry-standard S-N curves from DNV, API, BS 7608, and more. Interactive visualization with instant results. DNV-RP-C203 API RP 2A BS 7608 Eurocode 3 ## Input Parameters S-N Curve Standard DNV-RP-C203 (2021) API RP 2A (WSD) BS 7608 (2014) Eurocode 3 (EN 1993-1-9) S-N Curve Class Environment In Air Seawater with Cathodic Protection Seawater Free Corrosion Stress Range (MPa) Typical range: 10 - 300 MPa Number of Cycles (optional) Leave blank to calculate allowable cycles only Stress Concentration Factor (SCF) Default: 1.0 (no concentration) Calculate Fatigue Life ### Calculation Results ## S-N Curve Visualization ### About DNV-RP-C203 S-N Curves DNV-RP-C203 provides S-N curves for fatigue analysis of offshore steel structures. The curves account for different weld details, environments, and thickness effects. This is the most widely used standard for offshore fatigue assessment. ## S-N Curve Equation Basic S-N Relationship: N = a / (S^(m)) Where: N = Number of cycles to failure S = Stress range (MPa) a = S-N curve intercept (log scale) m = Negative inverse slope Fatigue Damage (Miner's Rule): D = n / N Where: D = Cumulative fatigue damage n = Applied number of cycles N = Allowable cycles from S-N curve Failure when D >= 1.0 Engineering Disclaimer This calculator is provided for educational and preliminary estimation purposes only. Actual fatigue assessments must consider load spectra, thickness effects, mean stress corrections, weld quality, inspection intervals, and other factors. Always consult the full standard documentation and qualified engineers for critical applications. ## Need Comprehensive Fatigue Analysis? Regression tests cover the 15 DNV-RP-C203 S-N classes in air, seawater with cathodic protection and free corrosion. Discuss Your Project View Case Studies ## Engineering Calculators - AceEngineer URL: https://www.aceengineer.com/calculators/ Description: Interactive engineering calculators for pipeline stability, wall thickness, fatigue analysis, and field economics. Based on DNV, ASME, API, and BS standards. # Engineering Calculators Interactive tools for structural analysis, fatigue assessment, and engineering calculations. Based on industry standards. ## Drilling Rig Selector NEW Application: Rig Selection, Well Planning | Data: 180 rigs — contractor spec sheets (Noble, Transocean, Valaris, Seadrill, Borr, Shelf) Shortlist offshore drilling rigs by the numbers that decide selection: water depth rating, hookload, moonpool envelope, jackup leg length and cantilever reach. Sortable table with a provenance link to every rig's published specification sheet. Open Selector ## On-Bottom Stability Calculator NEW Application: Subsea Pipeline Engineering | Method: DNV-RP-F109 Absolute Stability Calculate on-bottom stability for subsea pipelines using DNV-RP-F109. Includes hydrodynamic drag, inertia, and lift forces, submerged weight calculation with coating and contents, and lateral stability utilisation ratio with interactive velocity sweep visualization. DNV-RP-F109 Pipeline Stability Subsea Engineering Open Calculator ## Pipeline Wall Thickness Calculator NEW Application: Pipeline Engineering | Method: ASME B31.4 Burst & Collapse Checks Calculate minimum wall thickness and verify burst and collapse resistance for pipelines per ASME B31.4. Includes Barlow formula burst check with corrosion allowance, elastic collapse check, and minimum wall thickness calculation with interactive visualization. ASME B31.4 Pipeline Design Barlow Formula Open Calculator ## Mooring Line Fatigue Calculator NEW Application: Offshore Mooring (FPSO, FOWT, Semi) | Method: DNV-OS-E301 T-N Curve Screen Single-stress-range fatigue screen for mooring chain using the DNV-OS-E301 T-N curve. Converts a tension range to nominal stress, computes cycles to failure (N = a_D · S^-m), annual damage, and fatigue life for studless or studlink chain, with an interactive tension-range sweep. DNV-OS-E301 T-N Curve Mooring Chain Open Calculator View Mooring Demo ## Dynamometer Card Signature Screen NEW Application: Artificial Lift, Rod-Pump Diagnostics | Method: Pump-card geometry against twenty named failure-mode signatures Read a sucker-rod pump (downhole) card: pump fillage on the plunger stroke, card fill ratio, bounding-box corner clearances, branch slopes, downstroke transfer width and trace texture — then a ranked shortlist of the twenty named signatures with the measurements behind every match. Select a reference signature or paste your own card. No accuracy figure is quoted for the method, and the page states why. Dynamometer Card Sucker-Rod Pump Pump Fillage Open Calculator See the twenty signatures Read the method ## Decline Curve & EUR Calculator NEW Application: Production Forecasting, Reserves | Method: Arps Decline (Exponential / Hyperbolic / Harmonic) Forecast production and estimate ultimate recovery (EUR) with the Arps decline equations. Closed-form cumulative production to an economic limit or fixed horizon, time-to-limit, explicit per-day/per-year unit handling, and an interactive rate-vs-time forecast chart. Arps Decline EUR Production Forecast Open Calculator NPV Calculator ## S-N Curve Fatigue Calculator NEW Application: Offshore Structures, Wind Turbines, Marine Equipment | Method: S-N Curve Analysis with Interactive Plotting Calculate fatigue life using 40+ S-N curve classes from four major standards. Interactive Plotly visualization, multiple environments (air/seawater), SCF support, and real-time damage calculation. Our most comprehensive fatigue tool. DNV-RP-C203 API RP 2A BS 7608 Eurocode 3 Open Calculator Learn About Fatigue Analysis ## NPV Field Development Calculator NEW Application: Oil & Gas Field Development, Project Economics | Method: Discounted Cashflow Analysis Calculate net present value (NPV), internal rate of return (IRR), and payback period for field development projects. Features production decline modeling, price escalation, tax/royalty calculations, and interactive cashflow visualization with Plotly. DCF Analysis Production Decline Economic Metrics Open Calculator View Economics Case Study ## Basic Fatigue Life Calculator Application: Offshore Structures, Marine Equipment | Method: S-N Curve Analysis Simple fatigue life calculator for welded steel joints using DNV S-N curves. Quick estimates for preliminary fatigue assessments. For more comprehensive analysis with multiple standards and interactive plotting, use the S-N Curve Calculator above. DNV-RP-C203 Open Calculator ## About These Calculators These calculators are provided as educational tools for preliminary engineering estimates. They implement industry-standard methods from recognized codes and standards including: DNV-RP-F109: On-Bottom Stability Design of Submarine Pipelines ASME B31.4: Pipeline Transportation Systems for Liquids and Slurries DNV-RP-C203: Fatigue Design of Offshore Steel Structures API RP 2A: Recommended Practice for Planning, Designing and Constructing Fixed Offshore Platforms BS 7608: Code of Practice for Fatigue Design and Assessment of Steel Structures ASME BPVC: Boiler and Pressure Vessel Code Disclaimer: These calculators are for educational and preliminary assessment purposes only. Final engineering calculations should be performed by qualified engineers using validated software and verified against applicable codes and standards. AceEngineer accepts no liability for results obtained from these tools. ## Need More Advanced Analysis? For complex fatigue assessments, FEA-based stress analysis, or advanced engineering solutions, we offer professional consulting services with validated methodologies. Discuss Your Project View Case Studies ## Mooring Line Fatigue Calculator (DNV-OS-E301) - AceEngineer URL: https://www.aceengineer.com/calculators/mooring-fatigue.html Description: Mooring line fatigue calculator for mooring chain per DNV-OS-E301. T-N curve screen: nominal stress range, cycles to failure, annual damage and fatigue life for studless and studlink chain. # Mooring Line Fatigue Calculator Single-stress-range fatigue screen for mooring chain using the DNV-OS-E301 T-N curve DNV-OS-E301 T-N Curve Mooring Chain ## Input Parameters Chain Type Studless (m=3.0, a_D=6.0e10) Studlink (m=3.0, a_D=1.2e11) DNV-OS-E301 T-N curve class. Studlink has ~2x the fatigue capacity of studless. Chain Bar Diameter d (mm) Nominal chain bar diameter. Nominal area = 2 x (pi/4 x d^2) (two bars carry the load). Tension Range ΔT (kN) Representative peak-to-trough tension range for the screen. Cycles per Year (cycles/yr) Number of stress cycles applied per year at this tension range. Design Life (years) Target service life to check against. Safety Factor on Damage (-) Default 1.0. DNV-OS-E301 applies a Design Fatigue Factor (typically 3-10 depending on consequence/inspectability); enter a higher value to reflect it. Calculate Fatigue Life -- Fatigue Life (years) ### Calculation Details Nominal Cross-Section Area -- mm2 Nominal Stress Range (S) -- MPa Cycles to Failure (N) -- cycles Annual Damage -- Fatigue Life -- yr Status -- Standard Reference: DNV-OS-E301 "Position Mooring". T-N fatigue curve N = a_D · S^(-m). Studless chain: m = 3.0, a_D = 6.0e10. Studlink chain: m = 3.0, a_D = 1.2e11. (S in MPa.) Single-stress-range screen: This tool applies ONE representative tension range to the whole cycle count. A real fatigue analysis sums Miner's-rule damage over a full rainflow-counted tension-range histogram from the mooring time-domain response. Treat the result as a first-pass screen, not a design value. Disclaimer: This calculator is for educational and illustrative purposes only. Final engineering calculations should be performed by qualified engineers using validated software and verified against applicable codes and standards. ## About This Calculator Mooring lines on floating offshore units (FPSOs, semi-submersibles, spars, and floating wind platforms) accumulate fatigue damage from the cyclic tension induced by waves, low-frequency vessel motions, and the platform's mean offset. Chain links are a common fatigue-critical component, and DNV-OS-E301 "Position Mooring" provides a tension-range vs. cycles (T-N) curve to estimate their fatigue capacity. ### Method The tension range is first converted to a nominal stress range by dividing by the chain's load-bearing cross-section. A chain link is built from two parallel bars that together carry the load, so the nominal area is: A = 2 × (π/4 × d²) where d is the chain bar diameter. The nominal stress range is then S = ΔT / A (with ΔT in newtons and A in mm², S comes out in MPa). The cycles to failure at that stress range come from the DNV-OS-E301 T-N curve: N = aD · S^(−m) with curve parameters (per DNV-OS-E301): studless chain m = 3.0, aD = 6.0×10^(10); studlink chain m = 3.0, aD = 1.2×10^(11) (S expressed in MPa). The annual damage is the cycles applied per year divided by N, and the fatigue life is the reciprocal of the annual damage (divided by any safety factor on damage). A fatigue life at least equal to the design life passes the screen. ### Limitations Single representative tension range only — real analysis uses a rainflow histogram + Miner summation. No mean-load (mean tension) correction or thickness/size effect. The default safety factor is 1.0; DNV applies higher Design Fatigue Factors based on consequence and inspectability. Corrosion, out-of-plane bending (OPB), and proof-load effects are not modelled. ## Need Professional Mooring Fatigue Analysis? For full time-domain mooring analysis, rainflow-counted fatigue with histograms, OPB/IPB assessment, and Design Fatigue Factor application, we offer professional consulting services with validated methodologies. Discuss Your Project View Mooring Demo ## NPV Field Development Calculator - AceEngineer URL: https://www.aceengineer.com/calculators/npv-field-development.html Description: Interactive NPV calculator for oil and gas field development. Calculate net present value, IRR, and payback period with real-time cashflow visualization. Engineering tool. # NPV Field Development Calculator Calculate net present value, IRR, and payback period for oil and gas field development. Interactive cashflow visualization with instant economic metrics. ## Input Parameters Initial Production Rate (bbl/day) Typical range: 1,000 - 50,000 bbl/day Annual Decline Rate (%/year) Typical range: 10% - 25% for offshore fields Project Duration (years) Typical range: 15 - 30 years Oil Price ($/bbl) Current market price or long-term forecast Price Escalation (%/year) Annual price growth assumption Total CAPEX ($M) Total capital expenditure (wells, facilities, infrastructure) Annual OPEX ($M) Annual operating expenditure OPEX Escalation (%/year) Annual OPEX cost increase Discount Rate (%) Weighted average cost of capital (WACC) Tax Rate (%) Corporate income tax rate Royalty Rate (%) Government royalty (18.75% typical for GOM) Calculate Economics ### Economic Results ## Cashflow Visualization ### About NPV Field Development Analysis Net Present Value (NPV) is the cornerstone of field development economics, representing the present value of all future cashflows discounted at the project's cost of capital. This calculator uses industry-standard exponential decline curves and discounted cashflow analysis to evaluate project viability. ## Economic Formulas Production Decline: Q(t) = Q0 × (1 - D)^(t) Where: Q(t) = Production rate in year t Q0 = Initial production rate D = Annual decline rate (fraction) t = Time in years Net Present Value: NPV = Σ [CFt / (1 + r)^(t)] Where: CFt = Net cashflow in year t r = Discount rate (fraction) t = Year number (0 to N) NPV positive indicates viable project Revenue Calculation: Rt = Q(t) × Pt × 365 × (1 - Royalty) Where: Rt = Revenue in year t Pt = Oil price in year t Royalty = Government royalty rate Internal Rate of Return: NPV = 0 when r = IRR IRR is the discount rate at which NPV equals zero. Calculated numerically using bisection method. IRR > discount rate indicates viable project. Engineering Disclaimer This calculator is provided for educational and preliminary estimation purposes only. Actual field development decisions must consider reservoir uncertainty, drilling schedules, facility capacity constraints, regulatory requirements, environmental factors, and detailed financial modeling. Always consult qualified petroleum engineers and financial analysts for investment-grade economics and development planning. ## Need Comprehensive Field Development Economics? Our field development analysis includes reservoir simulation integration, probabilistic economics, multi-phase development planning, and automated BSEE data integration. Discuss Your Project View BSEE Economics Case Study ## On-Bottom Stability Calculator (DNV-RP-F109) - AceEngineer URL: https://www.aceengineer.com/calculators/on-bottom-stability.html Description: On-bottom stability calculator for subsea pipelines per DNV-RP-F109. Calculate hydrodynamic loads, submerged weight, and lateral stability utilisation ratio. # On-Bottom Stability Calculator Calculate pipeline lateral stability using DNV-RP-F109 absolute stability method DNV-RP-F109 Pipeline Stability Subsea Engineering ## Input Parameters Seawater Density (kg/m3) Seawater density (typical: 1025 kg/m3) Pipe Outer Diameter (m) Outer diameter including any concrete coating Wall Thickness (m) Steel pipe wall thickness Steel Density (kg/m3) Steel density (typical: 7850 kg/m3) Coating Density (kg/m3) Coating material density (e.g., polypropylene ~900 kg/m3) Coating Thickness (m) External coating thickness Contents Density (kg/m3) Density of pipe contents (e.g., oil ~800, gas ~100, water ~1000 kg/m3) Current Velocity (m/s) Steady-state near-bed current velocity Wave Acceleration (m/s2) Maximum wave-induced water particle acceleration at pipe level Drag Coefficient (-) Hydrodynamic drag coefficient (typical: 0.7-1.2) Inertia Coefficient (-) Hydrodynamic inertia coefficient (typical: 2.0-3.29) Lift Coefficient (-) Hydrodynamic lift coefficient (typical: 0.5-0.9) Soil Friction Coefficient (-) Lateral pipe-soil friction coefficient (sand ~0.6, clay ~0.2-0.4) Calculate Stability -- Utilisation Ratio ### Calculation Details Hydrodynamic Drag Force (F_H) -- N/m Lift Force (F_L) -- N/m Submerged Weight (W_s) -- N/m Lateral Resistance -- N/m Utilisation Ratio --% Status -- Standard Reference: DNV-RP-F109 Rev. 2021, Section 3 (Hydrodynamic Forces) and Section 4 (Absolute Stability). This calculator implements the simplified absolute stability method (Eq 4.1). Disclaimer: This calculator is for educational and illustrative purposes only. Final engineering calculations should be performed by qualified engineers using validated software and verified against applicable codes and standards. ## About This Calculator On-bottom stability (OBS) assessment is a critical step in the design of subsea pipelines. When a pipeline rests on the seabed, it is subjected to hydrodynamic forces from waves and currents that can cause it to move laterally. The pipeline must be heavy enough, or sufficiently restrained by soil friction, to resist these forces and remain stable on the seabed throughout its design life. This calculator implements the absolute stability method from DNV-RP-F109 (On-Bottom Stability Design of Submarine Pipelines), which is the most widely used industry standard for pipeline stability assessment. The absolute stability method ensures that the pipeline remains stationary under the design environmental conditions by checking that the soil resistance exceeds the applied hydrodynamic forces at all times. ### Hydrodynamic Forces A subsea pipeline on the seabed experiences three main hydrodynamic force components: Drag force (F_D): Acts in the direction of flow, proportional to the square of the flow velocity. Calculated using the Morison equation with a drag coefficient C_D that depends on pipe roughness, Reynolds number, and proximity to the seabed. Inertia force (F_I): Proportional to the water particle acceleration. Significant in wave-dominated conditions where acceleration is high. Uses the inertia coefficient C_M, which accounts for the added mass effect of the pipe displacing water. Lift force (F_L): Acts vertically upward due to asymmetric flow around the pipe near the seabed. Reduces the effective weight of the pipe and therefore its resistance to lateral movement. The lift coefficient C_L is particularly important for pipelines with low submerged weight. ### Utilisation Ratio The utilisation ratio is the key output of an absolute stability check. It compares the horizontal hydrodynamic force demand to the available lateral resistance: Utilisation = F_H / [mu x (W_s - F_L)] Where F_H is the combined horizontal force (drag + inertia), mu is the soil friction coefficient, W_s is the submerged weight per unit length, and F_L is the lift force. A utilisation ratio less than or equal to 1.0 indicates that the pipeline is stable. Values above 1.0 indicate that the pipeline may move laterally and additional measures are needed, such as concrete weight coating, trenching, rock dumping, or mattress placement. ### Limitations This calculator implements a simplified absolute stability check. For detailed design, engineers should consider additional factors including: Generalized stability analysis (allowing limited lateral displacement) Dynamic time-domain simulation of pipe response Soil liquefaction and scour effects Multi-directional wave and current loading Span assessment for uneven seabed conditions Temperature and pressure induced pipeline walking ## Need Professional Pipeline Stability Analysis? For complex scenarios including soil liquefaction, span assessment, seabed intervention, and multi-directional wave loading, we offer professional consulting services with validated methodologies. Discuss Your Project View OBS Case Study ## Pipeline Wall Thickness Calculator (ASME B31.4) - AceEngineer URL: https://www.aceengineer.com/calculators/wall-thickness.html Description: Wall thickness calculator for pipelines per ASME B31.4. Burst and collapse checks with corrosion allowance. Compare minimum wall thickness across design codes. # Pipeline Wall Thickness Calculator Burst and collapse wall thickness checks per ASME B31.4 with corrosion allowance and design factor ASME B31.4 Pipeline Design Barlow Formula ## Input Parameters Pipe Outer Diameter (m) Nominal outer diameter of the pipe Wall Thickness (m) Nominal wall thickness to be checked Specified Min Yield Strength (MPa) SMYS of pipe material (e.g., API 5L X65 = 450 MPa) Internal Pressure (MPa) Maximum allowable internal pressure (design pressure) External Pressure (MPa) External hydrostatic pressure at installation depth Corrosion Allowance (m) Corrosion allowance for wall thickness reduction over design life Design Factor (-) Per ASME B31.4 S403.2.1 (typically 0.72 for liquid pipelines) Young's Modulus (MPa) Elastic modulus of steel (typical: 207,000 MPa) Poisson's Ratio (-) Poisson's ratio for steel (typical: 0.3) Calculate Wall Thickness -- Burst Utilisation -- Collapse Utilisation -- Minimum Wall Thickness (mm) ### Calculation Details Effective Wall Thickness (t_eff) -- mm Burst Pressure (P_burst) -- MPa Net Internal Pressure (delta_P) -- MPa Collapse Pressure (P_collapse) -- MPa Minimum Required Wall Thickness -- mm Standard Reference: ASME B31.4 S403.2.1 (Burst), Timoshenko elastic collapse formula. Design factor per ASME B31.4 Table A403.2.1-1. Disclaimer: This calculator is for educational and illustrative purposes only. Final engineering calculations should be performed by qualified engineers using validated software and verified against applicable codes and standards. ## About This Calculator Pipeline wall thickness design is one of the most fundamental steps in pipeline engineering. The wall thickness must be sufficient to contain internal pressure (burst resistance), resist external hydrostatic pressure (collapse resistance), and provide adequate corrosion allowance over the design life of the pipeline. This calculator implements the primary design checks required by ASME B31.4 (Pipeline Transportation Systems for Liquids and Slurries), which is the governing code for liquid pipeline design in North America. ### Burst Check (Barlow Formula) The burst check verifies that the pipe wall can withstand the maximum internal pressure. The allowable burst pressure is calculated using the modified Barlow formula: P_burst = 2 x SMYS x t_eff x df / D Where SMYS is the Specified Minimum Yield Strength of the pipe material, t_eff is the effective wall thickness (nominal minus corrosion allowance), df is the design factor (typically 0.72 for liquid pipelines per ASME B31.4), and D is the pipe outer diameter. The burst utilisation ratio compares the net internal pressure (P_internal - P_external) to the allowable burst pressure. A utilisation ratio less than or equal to 1.0 confirms that the wall thickness is adequate for burst resistance. ### Collapse Check (Timoshenko Formula) For deepwater pipelines or during installation, external hydrostatic pressure may exceed the internal pressure, creating a net external pressure that can cause the pipe to collapse. The elastic collapse pressure is calculated using the Timoshenko formula: P_collapse = 2E / (1 - nu^2) x (t/D)^3 Where E is Young's modulus and nu is Poisson's ratio. This formula gives the critical elastic buckling pressure for a thin-walled cylinder under uniform external pressure. The collapse utilisation ratio compares the external pressure to the collapse pressure. ### Corrosion Allowance The corrosion allowance accounts for material loss over the pipeline's design life due to internal corrosion, external corrosion, or erosion. Typical values range from 1.5 mm to 6 mm depending on the transported fluid, coating system, and cathodic protection design. The effective wall thickness used in burst calculations is the nominal wall thickness minus the corrosion allowance. ### Design Factors ASME B31.4 specifies design factors that reduce the allowable stress to provide a safety margin. The standard design factor of 0.72 applies to most liquid pipeline segments. Higher design factors (up to 0.80) may apply in specific locations per ASME B31.4 Table A403.2.1-1. Other codes such as ASME B31.8 (gas pipelines) and API 1111 (offshore pipelines) use different design factor approaches. ### Limitations This calculator provides simplified burst and collapse checks. A complete wall thickness design should also consider: Combined loading (bending + pressure + axial force) Propagation buckling resistance Manufacturing tolerance and ovality Thermal stress and strain-based design Installation loads (laying, reeling, J-tube pull-in) Hydrotest pressure requirements ## Need Professional Pipeline Design? For complex scenarios including combined loading analysis, deepwater collapse assessment, installation engineering, and multi-code wall thickness comparison, we offer professional consulting services with validated methodologies. Discuss Your Project View Wall Thickness Case Study ## Digital Model Parametric Atlases — AceEngineer Capabilities URL: https://www.aceengineer.com/capabilities/atlas-explorer.html Description: Standard-traceable parametric result grids — mooring fatigue (S-N), synthetic-rope fatigue (T-N), and riser code-check utilisation — from digitalmodel's validated reduced-order atlases. Digital Model # Digital Model Parametric Atlases Standard-traceable parametric result grids — mooring fatigue (S-N), synthetic-rope fatigue (T-N), and riser code-check utilisation — from digitalmodel's validated reduced-order atlases. Refresh to latest ## Mooring Fatigue (DNV-RP-C203 S-N) S-N Curve Stress MPa N Cycles Damage B1 11 10,000 0 B2 11 10,000 0 C 11 10,000 0 C1 11 10,000 0 C2 11 10,000 0 D 11 10,000 0 E 11 10,000 0 F 11 10,000 0 B1 11 100,000 0 B2 11 100,000 0 C 11 100,000 0 C1 11 100,000 0 C2 11 100,000 0 D 11 100,000 0 E 11 100,000 0 F 11 100,000 0 B1 11 1,000,000 0 B2 11 1,000,000 0 C 11 1,000,000 0 C1 11 1,000,000 0 C2 11 1,000,000 0 D 11 1,000,000 0 E 11 1,000,000 0 F 11 1,000,000 0 B1 14 10,000 0 B2 14 10,000 0 C 14 10,000 0 C1 14 10,000 0 C2 14 10,000 0 D 14 10,000 0 E 14 10,000 0 F 14 10,000 0 B1 14 100,000 0 B2 14 100,000 0 C 14 100,000 0 C1 14 100,000 0 C2 14 100,000 0 D 14 100,000 0 E 14 100,000 0 F 14 100,000 0 B1 14 1,000,000 0 B2 14 1,000,000 0 C 14 1,000,000 0 C1 14 1,000,000 0 C2 14 1,000,000 0 D 14 1,000,000 0 E 14 1,000,000 0 F 14 1,000,000 0 B1 18 10,000 0 B2 18 10,000 0 Showing 50 of 312 rows — full table on Hugging Face. ## Synthetic Rope Fatigue (DNV-OS-E301 T-N) Tension Range kN N Cycles MBL kN Damage 200 10,000 5,000 0 200 10,000 10,000 0 200 10,000 20,000 0 200 10,000 35,000 0 200 10,000 50,000 0 200 100,000 5,000 0 200 100,000 10,000 0 200 100,000 20,000 0 200 100,000 35,000 0 200 100,000 50,000 0 200 1,000,000 5,000 0 200 1,000,000 10,000 0 200 1,000,000 20,000 0 200 1,000,000 35,000 0 200 1,000,000 50,000 0 200 10,000,000 5,000 0 200 10,000,000 10,000 0 200 10,000,000 20,000 0 200 10,000,000 35,000 0 200 10,000,000 50,000 0 400 10,000 5,000 0 400 10,000 10,000 0 400 10,000 20,000 0 400 10,000 35,000 0 400 10,000 50,000 0 400 100,000 5,000 0 400 100,000 10,000 0 400 100,000 20,000 0 400 100,000 35,000 0 400 100,000 50,000 0 400 1,000,000 5,000 0 400 1,000,000 10,000 0 400 1,000,000 20,000 0 400 1,000,000 35,000 0 400 1,000,000 50,000 0 400 10,000,000 5,000 0 400 10,000,000 10,000 0 400 10,000,000 20,000 0 400 10,000,000 35,000 0 400 10,000,000 50,000 0 700 10,000 5,000 0 700 10,000 10,000 0 700 10,000 20,000 0 700 10,000 35,000 0 700 10,000 50,000 0 700 100,000 5,000 0 700 100,000 10,000 0 700 100,000 20,000 0 700 100,000 35,000 0 700 100,000 50,000 0 Showing 50 of 120 rows — full table on Hugging Face. ## Riser Code Check (API-RP-2RD) Outer Diameter Wall Thickness Effective Tension kN Bending Moment kN·m SMYS Utilisation 0.2 0.02 0 0 359,000,000 0 0.2 0.02 0 0 448,000,000 0 0.2 0.02 0 0 552,000,000 0 0.2 0.02 0 80 359,000,000 0.65 0.2 0.02 0 80 448,000,000 0.52 0.2 0.02 0 80 552,000,000 0.42 0.2 0.02 0 160 359,000,000 1.29 0.2 0.02 0 160 448,000,000 1.04 0.2 0.02 0 160 552,000,000 0.84 0.2 0.02 0 240 359,000,000 1.94 0.2 0.02 0 240 448,000,000 1.55 0.2 0.02 0 240 552,000,000 1.26 0.2 0.02 0 320 359,000,000 2.59 0.2 0.02 0 320 448,000,000 2.07 0.2 0.02 0 320 552,000,000 1.68 0.2 0.02 0 400 359,000,000 3.23 0.2 0.02 0 400 448,000,000 2.59 0.2 0.02 0 400 552,000,000 2.1 0.2 0.02 400 0 359,000,000 0.19 0.2 0.02 400 0 448,000,000 0.15 0.2 0.02 400 0 552,000,000 0.12 0.2 0.02 400 80 359,000,000 0.67 0.2 0.02 400 80 448,000,000 0.54 0.2 0.02 400 80 552,000,000 0.44 0.2 0.02 400 160 359,000,000 1.31 0.2 0.02 400 160 448,000,000 1.05 0.2 0.02 400 160 552,000,000 0.85 0.2 0.02 400 240 359,000,000 1.95 0.2 0.02 400 240 448,000,000 1.56 0.2 0.02 400 240 552,000,000 1.27 0.2 0.02 400 320 359,000,000 2.59 0.2 0.02 400 320 448,000,000 2.08 0.2 0.02 400 320 552,000,000 1.69 0.2 0.02 400 400 359,000,000 3.24 0.2 0.02 400 400 448,000,000 2.59 0.2 0.02 400 400 552,000,000 2.11 0.2 0.02 800 0 359,000,000 0.38 0.2 0.02 800 0 448,000,000 0.31 0.2 0.02 800 0 552,000,000 0.25 0.2 0.02 800 80 359,000,000 0.75 0.2 0.02 800 80 448,000,000 0.6 0.2 0.02 800 80 552,000,000 0.49 0.2 0.02 800 160 359,000,000 1.35 0.2 0.02 800 160 448,000,000 1.08 0.2 0.02 800 160 552,000,000 0.88 0.2 0.02 800 240 359,000,000 1.98 0.2 0.02 800 240 448,000,000 1.58 0.2 0.02 800 240 552,000,000 1.29 0.2 0.02 800 320 359,000,000 2.61 0.2 0.02 800 320 448,000,000 2.09 Showing 50 of 2,700 rows — full table on Hugging Face. Source: aceengineer/digitalmodel-atlas-explorer on Hugging Face · pipeline Snapshot: Rendered from a cached snapshot on 2026-11-16; the upstream dataset may have moved since. Use “Refresh to latest” for current data. Data limits: Synthetic parametric sweeps generated from the cited standards (DNV-RP-C203, DNV-OS-E301, API-RP-2RD) and validated to under 10% max relative error against held-out samples. For screening and capability demonstration — not a substitute for a project-specific engineering check. ## Corrosion Control — Anode Sizing and Galvanic Index Screening — AceEngineer Capabilities URL: https://www.aceengineer.com/capabilities/corrosion-control.html Description: Screening-level sacrificial-anode sizing to DNV-RP-B401 (2021 edition as implemented) for two reference geometries, plus anodic-index screening categories for metal pairs. Screening only: not a project CP design, not a material-compatibility finding, and not qualified for client delivery. Digital Model # Corrosion Control — Anode Sizing and Galvanic Index Screening Screening-level sacrificial-anode sizing to DNV-RP-B401 (2021 edition as implemented) for two reference geometries, plus anodic-index screening categories for metal pairs. Screening only: not a project CP design, not a material-compatibility finding, and not qualified for client delivery. Refresh to latest ## Anode sizing Structure Climate Coating Design Life Years Anode Mass Kg Anode Count Current Mean A Current Final A 4-leg jacket temperate bare 10 12,692.3 64 260.8 312.4 4-leg jacket temperate bare 15 19,038.4 96 260.8 312.4 4-leg jacket temperate bare 20 25,384.5 127 260.8 312.4 4-leg jacket temperate bare 25 31,730.7 159 260.8 312.4 4-leg jacket temperate bare 30 38,076.8 191 260.8 312.4 4-leg jacket temperate bare 35 44,422.9 223 260.8 312.4 4-leg jacket temperate bare 40 50,769.1 254 260.8 312.4 4-leg jacket temperate aged-coating 10 11,898 60 244.48 292.6 4-leg jacket temperate aged-coating 15 17,847 90 244.48 292.6 4-leg jacket temperate aged-coating 20 23,796 119 244.48 292.6 4-leg jacket temperate aged-coating 25 29,745.1 149 244.48 292.6 4-leg jacket temperate aged-coating 30 35,694.1 179 244.48 292.6 4-leg jacket temperate aged-coating 35 41,643.1 209 244.48 292.6 4-leg jacket temperate aged-coating 40 47,592.1 238 244.48 292.6 4-leg jacket temperate good-coating 10 11,103.8 56 228.16 272.8 4-leg jacket temperate good-coating 15 16,655.7 84 228.16 272.8 4-leg jacket temperate good-coating 20 22,207.6 112 228.16 272.8 4-leg jacket temperate good-coating 25 27,759.5 139 228.16 272.8 4-leg jacket temperate good-coating 30 33,311.4 167 228.16 272.8 4-leg jacket temperate good-coating 35 38,863.2 195 228.16 272.8 4-leg jacket temperate good-coating 40 44,415.2 223 228.16 272.8 4-leg jacket temperate premium-coating 10 7,424.6 38 152.56 181.9 4-leg jacket temperate premium-coating 15 11,136.9 56 152.56 181.9 4-leg jacket temperate premium-coating 20 14,849.2 75 152.56 181.9 4-leg jacket temperate premium-coating 25 18,561.5 93 152.56 181.9 4-leg jacket temperate premium-coating 30 22,273.8 112 152.56 181.9 4-leg jacket temperate premium-coating 35 25,986 130 152.56 181.9 4-leg jacket temperate premium-coating 40 29,698.3 149 152.56 181.9 4-leg jacket tropical bare 10 9,013.1 46 185.2 236.8 4-leg jacket tropical bare 15 13,519.6 68 185.2 236.8 4-leg jacket tropical bare 20 18,026.1 91 185.2 236.8 4-leg jacket tropical bare 25 22,532.7 113 185.2 236.8 4-leg jacket tropical bare 30 27,039.2 136 185.2 236.8 4-leg jacket tropical bare 35 31,545.7 158 185.2 236.8 4-leg jacket tropical bare 40 36,052.3 181 185.2 236.8 4-leg jacket tropical aged-coating 10 8,446.6 43 173.56 221.68 4-leg jacket tropical aged-coating 15 12,669.9 64 173.56 221.68 4-leg jacket tropical aged-coating 20 16,893.2 85 173.56 221.68 4-leg jacket tropical aged-coating 25 21,116.5 106 173.56 221.68 4-leg jacket tropical aged-coating 30 25,339.8 127 173.56 221.68 4-leg jacket tropical aged-coating 35 29,563 148 173.56 221.68 4-leg jacket tropical aged-coating 40 33,786.3 169 173.56 221.68 4-leg jacket tropical good-coating 10 7,880.1 40 161.92 206.56 4-leg jacket tropical good-coating 15 11,820.2 60 161.92 206.56 4-leg jacket tropical good-coating 20 15,760.2 79 161.92 206.56 4-leg jacket tropical good-coating 25 19,700.3 99 161.92 206.56 4-leg jacket tropical good-coating 30 23,640.3 119 161.92 206.56 4-leg jacket tropical good-coating 35 27,580.4 138 161.92 206.56 4-leg jacket tropical good-coating 40 31,520.4 158 161.92 206.56 4-leg jacket tropical premium-coating 10 5,295.9 27 108.82 138.16 Showing 50 of 112 rows — full table on Hugging Face. ## Galvanic index screening Environment Metal A Metal B Verdict Delta V Allowable Delta V Environment Label Metal A Label Metal A Anodic Index V Metal B Label Metal B Anodic Index V Rank Anodic Member harsh_marine gold gold OK 0 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Gold 0 0 — (same index) harsh_marine gold silver OK 0.15 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Silver 0.15 0 Silver harsh_marine gold nickel PROTECT 0.3 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Nickel 0.3 2 Nickel harsh_marine gold monel_nickel_copper PROTECT 0.3 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Monel (Ni-Cu) 0.3 2 Monel (Ni-Cu) harsh_marine gold copper PROTECT 0.35 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Copper 0.35 2 Copper harsh_marine gold cupronickel PROTECT 0.35 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Cupronickel 0.35 2 Cupronickel harsh_marine gold brass PROTECT 0.4 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Brass 0.4 2 Brass harsh_marine gold bronze PROTECT 0.45 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Bronze 0.45 2 Bronze harsh_marine gold stainless_316_passive PROTECT 0.5 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 316 SS (passive) 0.5 2 316 SS (passive) harsh_marine gold stainless_304_passive PROTECT 0.5 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 304 SS (passive) 0.5 2 304 SS (passive) harsh_marine gold carbon_steel PROTECT 0.85 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Carbon steel 0.85 2 Carbon steel harsh_marine gold cast_iron PROTECT 0.85 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Cast iron 0.85 2 Cast iron harsh_marine gold aluminum_alloy PROTECT 0.9 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Aluminum alloy 0.9 2 Aluminum alloy harsh_marine gold cadmium_plated PROTECT 0.95 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Cadmium (plated) 0.95 2 Cadmium (plated) harsh_marine gold zinc PROTECT 1.25 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Zinc 1.25 2 Zinc harsh_marine gold magnesium PROTECT 1.75 0.15 Harsh / marine (allowable ΔV = 0.15 V) Gold 0 Magnesium 1.75 2 Magnesium harsh_marine silver gold OK 0.15 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Gold 0 0 Silver harsh_marine silver silver OK 0 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Silver 0.15 0 — (same index) harsh_marine silver nickel OK 0.15 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Nickel 0.3 0 Nickel harsh_marine silver monel_nickel_copper OK 0.15 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Monel (Ni-Cu) 0.3 0 Monel (Ni-Cu) harsh_marine silver copper MARGINAL 0.2 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Copper 0.35 1 Copper harsh_marine silver cupronickel MARGINAL 0.2 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Cupronickel 0.35 1 Cupronickel harsh_marine silver brass PROTECT 0.25 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Brass 0.4 2 Brass harsh_marine silver bronze PROTECT 0.3 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Bronze 0.45 2 Bronze harsh_marine silver stainless_316_passive PROTECT 0.35 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 316 SS (passive) 0.5 2 316 SS (passive) harsh_marine silver stainless_304_passive PROTECT 0.35 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 304 SS (passive) 0.5 2 304 SS (passive) harsh_marine silver carbon_steel PROTECT 0.7 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Carbon steel 0.85 2 Carbon steel harsh_marine silver cast_iron PROTECT 0.7 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Cast iron 0.85 2 Cast iron harsh_marine silver aluminum_alloy PROTECT 0.75 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Aluminum alloy 0.9 2 Aluminum alloy harsh_marine silver cadmium_plated PROTECT 0.8 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Cadmium (plated) 0.95 2 Cadmium (plated) harsh_marine silver zinc PROTECT 1.1 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Zinc 1.25 2 Zinc harsh_marine silver magnesium PROTECT 1.6 0.15 Harsh / marine (allowable ΔV = 0.15 V) Silver 0.15 Magnesium 1.75 2 Magnesium harsh_marine nickel gold PROTECT 0.3 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Gold 0 2 Nickel harsh_marine nickel silver OK 0.15 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Silver 0.15 0 Nickel harsh_marine nickel nickel OK 0 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Nickel 0.3 0 — (same index) harsh_marine nickel monel_nickel_copper OK 0 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Monel (Ni-Cu) 0.3 0 — (same index) harsh_marine nickel copper OK 0.05 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Copper 0.35 0 Copper harsh_marine nickel cupronickel OK 0.05 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Cupronickel 0.35 0 Cupronickel harsh_marine nickel brass OK 0.1 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Brass 0.4 0 Brass harsh_marine nickel bronze OK 0.15 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Bronze 0.45 0 Bronze harsh_marine nickel stainless_316_passive MARGINAL 0.2 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 316 SS (passive) 0.5 1 316 SS (passive) harsh_marine nickel stainless_304_passive MARGINAL 0.2 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 304 SS (passive) 0.5 1 304 SS (passive) harsh_marine nickel carbon_steel PROTECT 0.55 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Carbon steel 0.85 2 Carbon steel harsh_marine nickel cast_iron PROTECT 0.55 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Cast iron 0.85 2 Cast iron harsh_marine nickel aluminum_alloy PROTECT 0.6 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Aluminum alloy 0.9 2 Aluminum alloy harsh_marine nickel cadmium_plated PROTECT 0.65 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Cadmium (plated) 0.95 2 Cadmium (plated) harsh_marine nickel zinc PROTECT 0.95 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Zinc 1.25 2 Zinc harsh_marine nickel magnesium PROTECT 1.45 0.15 Harsh / marine (allowable ΔV = 0.15 V) Nickel 0.3 Magnesium 1.75 2 Magnesium harsh_marine monel_nickel_copper gold PROTECT 0.3 0.15 Harsh / marine (allowable ΔV = 0.15 V) Monel (Ni-Cu) 0.3 Gold 0 2 Monel (Ni-Cu) harsh_marine monel_nickel_copper silver OK 0.15 0.15 Harsh / marine (allowable ΔV = 0.15 V) Monel (Ni-Cu) 0.3 Silver 0.15 0 Monel (Ni-Cu) Showing 50 of 768 rows — full table on Hugging Face. Source: aceengineer/digitalmodel-corrosion on Hugging Face · pipeline Snapshot: Rendered from a cached snapshot on 2026-11-16; the upstream dataset may have moved since. Use “Refresh to latest” for current data. Data limits: Reference geometries only (a 4-leg jacket and an XL monopile) — no client or vessel-specific data. Anode sizing follows DNV-RP-B401 across 2 structures x 2 climates x 4 coating conditions x 7 design lives. Galvanic verdicts are anodic-index screening categories for all 16x16 metal pairs, including a metal against itself; they indicate where to look, and are not a substitute for a project-specific CP design. Environment allowable dV spans 0.15 V (harsh marine) to 0.5 V (controlled indoor). ## Field D&C Days QA/QC — AceEngineer Capabilities URL: https://www.aceengineer.com/capabilities/dc-days-qaqc.html Description: Bore-by-bore drilling & completion days behind the World Oil April 2026 reconciliation — 253 wellbores across 11 Gulf of Mexico developments, with drilling-day stability proven across data vintages. Browse the interactive drill-down: /capabilities/dc-drilldown.html World Energy # Field D&C Days QA/QC Bore-by-bore drilling & completion days behind the World Oil April 2026 reconciliation — 253 wellbores across 11 Gulf of Mexico developments, with drilling-day stability proven across data vintages. Browse the interactive drill-down: /capabilities/dc-drilldown.html Refresh to latest ## Reconciliation Matrix Development Bores Wed Drilling Days Completion Days Dc Days Wed Dc Days Article Delta Days Status Bores Article Producers Wed Producers Article Anchor 17 821 1,004 1,825 1,825 0 exact 17 3 3 Buckskin 25 1,043 1,013 2,056 2,004 52 recovered — +1 bore / +52 days vs article (was missing entirely) 24 — 4 Cascade Chinook 14 1,205 1,262 2,467 2,467 0 exact 14 3 3 Jack St Malo 73 3,065 3,982 7,047 6,928 119 open — +119 days, suspect post-TD completion over-count (#846) 73 24 24 Julia 9 802 885 1,687 1,687 0 exact 9 4 4 Kaskida 7 556 285 841 841 0 exact 7 — 0 North Platte 23 675 296 971 971 0 days exact; +3 zero-day sidetracks 20 — 0 Shenandoah 23 1,363 1,007 2,370 2,346 24 resolved — +24 recompletion-accounting days (frozen V30 was −357) 23 4 4 Stones 22 1,457 1,168 2,625 2,625 0 exact vs article; +20 post-cutoff well-servicing days 22 10 10 Tiber 2 214 36 250 250 0 exact 2 — 0 Big Foot 38 1,235 2,030 3,265 — — WED-only — excluded from the article's Table 1 — 8 — ## Per-Well Listing Development Api12 Spud Td Date Drilling Days Completion Days Dc Days Sidetrack Producer Bore Lease Name Lease Num Note Water Depth ft Max Md ft Max TVD ft Max Mud ppg Vintage Category Anchor 608114062100 2014-03-16 2014-05-17 62 15 77 false false 001 Anchor G31752 — 5,080 15,356 15,356 17 unchanged Anchor 608114062101 2014-05-28 2014-06-14 17 59 76 true false 001 Anchor G31752 — 5,080 25,800 25,797 17 unchanged Anchor 608114063500 2014-08-12 2014-11-28 108 65 173 false false 002 Anchor G31752 — 5,080 33,750 33,749 16.8 unchanged Anchor 608114063501 2015-07-09 2015-07-28 19 19 38 true false 002 Anchor G31752 — 5,080 33,400 33,397 16.2 unchanged Anchor 608114063502 2015-08-14 2015-09-11 28 36 64 true false 002 Anchor G31752 — 5,080 35,210 34,094 16.6 unchanged Anchor 608114066100 2016-01-26 2016-02-11 16 17 33 false false 001 Anchor G31751 — 5,080 11,249 11,249 17 unchanged Anchor 608114066101 2016-02-26 2016-06-18 113 49 162 true false 001 Anchor G31751 — 5,080 34,022 33,910 18.5 unchanged Anchor 608114067300 2016-09-17 2016-11-07 51 34 85 false false 003 Anchor G31752 — 5,080 28,642 28,359 16.8 unchanged Anchor 608114067301 2016-12-04 2017-01-24 51 33 84 true false 003 Anchor G31752 — 5,080 33,660 33,046 16.6 unchanged Anchor 608114072800 2019-11-19 2019-11-26 7 2 9 false false SB001 Anchor G31752 — 5,080 5,441 5,441 12.1 unchanged Anchor 608114075000 2021-12-08 2022-03-14 96 260 356 false true AP001 Anchor G31752 — 5,080 33,550 33,399 19.1 unchanged Anchor 608114075100 2022-11-16 2023-02-06 82 139 221 false true AP002 Anchor G31752 — 5,080 33,683 33,367 17.5 unchanged Anchor 608114077400 2023-11-26 2024-05-15 171 276 447 false false BP003 Anchor G31751 — 5,080 34,184 33,539 19 unchanged Anchor 608114076100 — — 0 0 0 false false AP004 Anchor G31752 — 5,080 — — — unchanged Anchor 608114076101 — — 0 0 0 true true AP004 Anchor G31752 — 5,080 — — — wed_only Anchor 608114076900 — — 0 0 0 false false AP005 Anchor G31752 — 5,080 — — — unchanged Anchor 608114079600 — — 0 0 0 false false BP006 Anchor G31751 — 5,080 — — — wed_only Buckskin 608084001600 2008-09-03 2008-11-25 83 5 88 false false 001 Buckskin G25823 — 6,800 28,404 28,403 16.5 wed_only Buckskin 608084001601 2008-11-26 2009-01-20 55 16 71 true false 001 Buckskin G25823 — 6,800 29,404 29,402 16.5 wed_only Buckskin 608084002100 2011-05-16 2011-09-13 120 45 165 false false 001 Buckskin G25806 — 6,800 28,000 27,999 16.9 wed_only Buckskin 608084003100 2013-03-26 2013-08-26 153 20 173 false false 001 Buckskin G25814 — 6,800 11,579 11,579 17 wed_only Buckskin 608084003101 2013-09-10 2013-10-10 30 31 61 true false 001 Buckskin G25814 — 6,800 17,520 17,519 17 wed_only Buckskin 608084003102 2013-11-06 2013-11-25 19 41 60 true false 001 Buckskin G25814 — 6,800 19,292 19,287 17.2 wed_only Buckskin 608084003103 2013-12-31 2014-01-06 6 27 33 true false 001 Buckskin G25814 — 6,800 20,458 20,451 17 wed_only Buckskin 608084003104 2014-01-30 2014-02-08 9 43 52 true false 001 Buckskin G25814 — 6,800 19,637 19,630 17 wed_only Buckskin 608084003105 2014-03-21 2014-05-15 55 52 107 true false 001 Buckskin G25814 — 6,800 29,415 28,483 17 wed_only Buckskin 608084003106 2014-07-02 2014-09-09 69 36 105 true false 001 Buckskin G25814 — 6,800 29,387 28,283 16.6 wed_only Buckskin 608084004700 2014-09-02 2014-10-22 50 11 61 false false 002 Buckskin G25806 — 6,800 13,610 13,610 16 wed_only Buckskin 608084004701 2014-10-27 2014-12-13 47 8 55 true false 002 Buckskin G25806 — 6,800 20,562 20,386 16.4 wed_only Buckskin 608084006000 2018-01-20 2018-03-14 53 11 64 false false 002 Buckskin G25814 — 6,800 27,690 27,039 16.6 wed_only Buckskin 608084006100 2018-01-21 2018-05-24 123 10 133 false false 003 Buckskin G25814 — 6,800 26,313 24,342 16.6 wed_only Buckskin 608084006001 2018-03-22 2018-03-28 6 159 165 true false SS002 Buckskin G25814 — 6,800 29,320 26,488 16.4 wed_only Buckskin 608084006101 2018-05-31 2018-06-03 3 175 178 true false SS003 Buckskin G25814 — 6,800 28,800 26,698 16.4 wed_only Buckskin 608084006700 2021-09-20 2021-09-29 9 4 13 false false 001 Buckskin G25814 — 6,800 13,073 13,066 16.6 wed_only Buckskin 608084006701 2021-10-01 2021-10-23 22 64 86 true false 001 Buckskin G25814 — 6,800 21,900 21,895 16.6 wed_only Buckskin 608084006702 2021-12-22 2022-01-13 22 107 129 true false SS001 Buckskin G25814 — 6,800 28,586 28,100 16.6 wed_only Buckskin 608084007000 2022-10-18 2022-11-25 38 14 52 false false 002 Buckskin G32650 — 6,800 29,632 28,782 16.6 wed_only Buckskin 608084007300 2023-07-28 2023-09-03 37 7 44 false false 004 Buckskin G25806 — 6,800 19,992 19,988 16.6 wed_only Buckskin 608084007301 2023-09-04 2023-10-08 34 127 161 true false SS004 Buckskin G25806 — 6,800 28,725 26,749 16.4 wed_only Buckskin 608084007200 — — 0 0 0 false false SS005 Buckskin G25806 — 6,800 — — — wed_only Buckskin 608084007700 — — 0 0 0 false false 001 Buckskin G25823 — 6,800 — — — wed_only Buckskin 608084007701 — — 0 0 0 true false 003 Buckskin G25823 — 6,800 — — — wed_only Cascade Chinook 608124000800 2002-01-31 2002-04-14 73 9 82 false false 001 Cascade G16965 — 8,200 26,710 26,685 — unchanged Cascade Chinook 608124000801 2002-04-23 2002-05-16 23 22 45 true false 001 Cascade G16965 — 8,200 27,929 27,908 — unchanged Cascade Chinook 608124001000 2003-01-13 2003-06-19 157 27 184 false false 001 Chinook G16997 — 8,900 27,652 27,626 16.15 unchanged Cascade Chinook 608124001600 2005-03-19 2005-05-29 71 140 211 false false 002 Cascade G16965 — 8,200 30,213 28,000 14.5 unchanged Cascade Chinook 608124001601 2005-10-09 2005-11-24 46 60 106 true false 002 Cascade G16965 — 8,200 28,565 26,575 16.8 unchanged Cascade Chinook 608124003800 2008-11-06 2009-06-03 209 245 454 false false CA003 Cascade G16965 — 8,200 27,019 26,804 15.6 unchanged Cascade Chinook 608124004700 2009-11-25 2012-03-28 176 18 194 false false 004 Cascade G16965 — 8,200 19,400 19,348 16.4 unchanged Cascade Chinook 608124004600 2009-11-27 2009-12-22 25 19 44 false false 002 Chinook G16997 — 8,900 21,695 21,671 16.5 unchanged Showing 50 of 253 rows — full table on Hugging Face. ## Vintage Diff (Drilling Stability) Dev Api12 Category Drill V30 Drill Wed D Drill D Compl Compl V30 Compl Wed Spud Wed Anchor 608114062100 unchanged 62 62 0 0 15 15 03/16/2014 Anchor 608114062101 unchanged 17 17 0 0 59 59 05/28/2014 Anchor 608114063500 unchanged 108 108 0 0 65 65 08/12/2014 Anchor 608114063501 unchanged 19 19 0 0 19 19 07/09/2015 Anchor 608114063502 unchanged 28 28 0 0 36 36 08/14/2015 Anchor 608114066100 unchanged 16 16 0 0 17 17 01/26/2016 Anchor 608114066101 unchanged 113 113 0 0 49 49 02/26/2016 Anchor 608114067300 unchanged 51 51 0 0 34 34 09/17/2016 Anchor 608114067301 unchanged 51 51 0 0 33 33 12/04/2016 Anchor 608114072800 unchanged 7 7 0 0 2 2 11/19/2019 Anchor 608114075000 unchanged 96 96 0 0 260 260 12/08/2021 Anchor 608114075100 unchanged 82 82 0 0 139 139 11/16/2022 Anchor 608114076100 unchanged 0 0 0 0 0 0 — Anchor 608114076101 wed_only 0 0 0 0 0 0 — Anchor 608114076900 unchanged 0 0 0 0 0 0 — Anchor 608114077400 unchanged 171 171 0 0 276 276 11/26/2023 Anchor 608114079600 wed_only 0 0 0 0 0 0 — Big Foot 608124001900 unchanged 2 2 0 0 9 9 07/26/2005 Big Foot 608124002000 unchanged 115 115 0 0 37 37 08/09/2005 Big Foot 608124002001 unchanged 14 14 0 0 7 7 01/01/2006 Big Foot 608124002002 unchanged 2 2 0 0 11 11 01/15/2006 Big Foot 608124002003 unchanged 35 35 0 0 38 38 03/23/2006 Big Foot 608124002004 unchanged 7 7 0 0 21 21 06/03/2006 Big Foot 608124002005 unchanged 38 38 0 0 30 30 11/25/2008 Big Foot 608124002300 unchanged 92 92 0 0 14 14 11/03/2006 Big Foot 608124002301 unchanged 34 34 0 0 21 21 10/15/2007 Big Foot 608124002302 unchanged 41 41 0 0 22 22 12/04/2007 Big Foot 608124005900 unchanged 0 0 0 0 0 0 — Big Foot 608124006000 unchanged 76 76 0 0 138 138 12/10/2011 Big Foot 608124006001 unchanged 15 15 0 0 156 156 03/10/2019 Big Foot 608124006200 unchanged 126 126 0 0 265 265 04/03/2012 Big Foot 608124006300 unchanged 0 0 0 0 0 0 — Big Foot 608124006301 unchanged 0 0 0 0 0 0 — Big Foot 608124006302 unchanged 13 13 0 0 168 168 07/11/2024 Big Foot 608124006400 unchanged 0 0 0 0 0 0 — Big Foot 608124006401 unchanged 0 0 0 0 0 0 — Big Foot 608124006402 unchanged 0 0 0 0 0 0 — Big Foot 608124006403 unchanged 0 0 0 0 0 0 — Big Foot 608124006404 late_data 0 28 28 123 0 123 05/06/2025 Big Foot 608124006500 unchanged 63 63 0 0 86 86 05/23/2012 Big Foot 608124006600 unchanged 112 112 0 0 38 38 04/12/2012 Big Foot 608124006601 unchanged 0 0 0 0 22 22 01/04/2020 Big Foot 608124006602 unchanged 11 11 0 0 17 17 01/19/2020 Big Foot 608124006603 servicing_accrual 18 18 0 35 224 259 02/12/2020 Big Foot 608124006700 unchanged 98 98 0 0 102 102 05/17/2012 Big Foot 608124006800 servicing_accrual 118 118 0 46 164 210 01/22/2013 Big Foot 608124006900 unchanged 0 0 0 0 0 0 — Big Foot 608124007000 unchanged 0 0 0 0 0 0 — Big Foot 608124007100 unchanged 66 66 0 0 22 22 04/13/2012 Big Foot 608124007101 unchanged 7 7 0 0 16 16 02/05/2021 Showing 50 of 253 rows — full table on Hugging Face. Source: aceengineer/worldenergydata-explorer on Hugging Face · pipeline Snapshot: Rendered from a cached snapshot on 2026-11-16; the upstream dataset may have moved since. Use “Refresh to latest” for current data. Data limits: Drilling days = spud to total depth; completion days = ALL post-TD rig time including later recompletion and servicing (the open worldenergydata#846 boundary question). Known caveat: the extractor mixes calendar days (spans under ~250 d) with WAR-union rig-days (longer spans), so batch-drilled wells undercount drilling days — disclosed rather than corrected pending resolution. Producer markers cover the seven core Lower-Tertiary fields only. ## D&C Drill-Down — Field ▸ Block ▸ Bore | AceEngineer URL: https://www.aceengineer.com/capabilities/dc-drilldown.html Description: Interactive drill-down through 253 Gulf of Mexico wellbores — field to block to bore, with drilling and completion days at every level. BSEE WAR rig-days · Lower Tertiary · Gulf of Mexico # D&C Drill-Down Start from a field or a block, drill to its bores, then to a single wellbore's full record — and on to that field's life-cycle, economics, and engineering pages. Every level is deep-linkable. Reconciled to the article — completion-boundary rule (#846) open Fields 11 developments Blocks 23 OCS leases Bores 253 incl. sidetracks D&C days 25,404 12,436 drilling · 12,968 completion By field By block Reading the data Drilling days (spud → TD) Completion days (all post-TD rig time) Reconciled / producer Open accounting question ## D&C Days QA/QC — Report Hub | AceEngineer URL: https://www.aceengineer.com/capabilities/dc-qaqc-hub.html Description: QA/QC hub for the World Oil April 2026 drilling and completion days reconciliation across 11 Gulf of Mexico developments. Capabilities▸D&C Days QA/QC BSEE WAR rig-days · World Oil April 2026 Table 1 · Lower Tertiary # D&C Days QA/QC One entry point to the whole reconciliation — the field-level matrix, the bore-by-bore listing, the drilling-days resolution, and the revision lineage. Everything below is reachable from this page, and every number traces to committed extractor output. Reconciled to the article — completion-boundary rule (#846) open Basis V50 = wed · WAR 2026-02-19 Universe 253 bores · 11 developments Total 25,404 D&C days Article 211 bores · 21,944 days Drilling stability 0/253 bores changed drilling days across vintages Matrix agreement 7/10 developments tie the article to the day Open delta +119days Jack St Malo — two late bores + #846 boundary Recovered 25bores Buckskin, missing from the article's shelf extract ## Δ vs the article, by development Total D&C days, wed minus World Oil Table 1 — seven exact, three explained. Jack St Malo Buckskin Shenandoah Stones Anchor Cascade Chinook 4 others +119 · open +52 · recovered bore +24 · recompletion 0 · exact 0 · exact 0 · exact 0 · exact 0 +100 days wed − article, total D&C days The report set ## How it holds together Five report roles, grouped by how deep you're going. Start with the reconciliation narrative, drill into the bore-level data, then follow the one open accounting question. Each card carries an evidence badge so you always know what weight the page can bear. Understand NarrativeReconciled ### Validation & Matrix The field-level D&C reconciliation against the article as published, plus the article errata hand-back. 7 exact · Shenandoah +24 resolved · Buckskin recovered Post-cutoff delta isolated: +53 days, all servicing BOEM cross-check and change log Open → NarrativeVerification ### Revision Lineage V30 → V50 → wed, field by field — the canonical-basis story behind every number on these pages. V50 = wed to the day, every field What changed at each revision and why The bug corrections, documented Open → Explore the data Interactive253 bores ### Drill-Down Browse by field or OCS block, drill to the bores, then to a single wellbore’s full record. 11 fields · 23 blocks · 253 bores Every level deep-linkable Out to life-cycle, economics, assets Open → Bore-level index253 bores ### Per-Well Listing One row per wellbore behind every matrix cell — the "listing" the QA/QC review asked for. Spud, TD, drilling / completion split per bore Producer and sidetrack markers Article comparison columns per development Open → Vintage diffBasis caveat ### Drilling-Days Resolution Frozen V30 vs wed, per bore — drilling days never change once TD is reached; all movement is data arrival. 0 of 253 bores changed drilling days 7 late-data bores · 5 servicing-accrual bores Known caveat: two bases in one column — calendar ≤250 d, WAR-union beyond; batch-drilled wells undercount (PS004: 44 d at 28,692 ft) Open → The open question Diagnostic · per borePR #897 pending ### JSM D&C Diff The +234-day frozen-vs-candidate difference localized to two producer bores — every boundary rule tested regresses another field's pins. 608124015400 · +48 drill / +71 compl 608124015504 · +68 drill / +47 compl Rule sensitivity table → owner decision Open PR → Frozen benchmarkLike-for-like ### Frozen Verification The like-for-like check against the article's own frozen V30 universe — 217 wells, matched-9 within −2.5%. 22,478 wed vs 21,944 article D&C days Same universe, same vintage, same rules The WO_APRIL_2026_ARTICLE pinned benchmark Open → Source Committed extractor outputProvenance ### Data & Provenance ↗ The canonical per-bore extract (253 rows) and the vintage diff (dc_vintage_diff.csv), both committed and pinned by tests — every number on these pages traces back here. github.com/vamseeachanta/worldenergydata → ### Guided reading path If you'd rather be walked through it, follow the reconciliation in the order it was built. STARTMatrix→ DRILL INPer-well→ RESOLVEVintage diff→ DECIDE#846 rule Evidence badges Reconciled / like-for-like Verification / caveat retained Bore-level index Pending / provenance ## Field Economics Sensitivity — AceEngineer Capabilities URL: https://www.aceengineer.com/capabilities/field-economics-sensitivity.html Description: Field-economics sensitivity sweep — how life-to-date pretax NPV moves with WTI price and discount rate, on public BSEE production. World Energy # Field Economics Sensitivity Field-economics sensitivity sweep — how life-to-date pretax NPV moves with WTI price and discount rate, on public BSEE production. Refresh to latest ## Price × Discount-Rate Sweep Field WTI Price Multiplier Discount Rate NPV Musd Breakeven Multiplier Basis jack_st_malo 0.8 0.08 -1,485.2 1.11 life_to_date_pretax_npv jack_st_malo 0.9 0.08 -1,007.3 1.11 life_to_date_pretax_npv jack_st_malo 1 0.08 -529.5 1.11 life_to_date_pretax_npv jack_st_malo 1.1 0.08 -51.6 1.11 life_to_date_pretax_npv jack_st_malo 1.2 0.08 426.2 1.11 life_to_date_pretax_npv jack_st_malo 0.8 0.1 -1,469 1.24 life_to_date_pretax_npv jack_st_malo 0.9 0.1 -1,136.8 1.24 life_to_date_pretax_npv jack_st_malo 1 0.1 -804.5 1.24 life_to_date_pretax_npv jack_st_malo 1.1 0.1 -472.2 1.24 life_to_date_pretax_npv jack_st_malo 1.2 0.1 -139.9 1.24 life_to_date_pretax_npv jack_st_malo 0.8 0.13 -1,350.9 1.43 life_to_date_pretax_npv jack_st_malo 0.9 0.13 -1,137.1 1.43 life_to_date_pretax_npv jack_st_malo 1 0.13 -923.3 1.43 life_to_date_pretax_npv jack_st_malo 1.1 0.13 -709.5 1.43 life_to_date_pretax_npv jack_st_malo 1.2 0.13 -495.7 1.43 life_to_date_pretax_npv julia 0.8 0.08 -747.8 1.31 life_to_date_pretax_npv julia 0.9 0.08 -601 1.31 life_to_date_pretax_npv julia 1 0.08 -454.2 1.31 life_to_date_pretax_npv julia 1.1 0.08 -307.4 1.31 life_to_date_pretax_npv julia 1.2 0.08 -160.6 1.31 life_to_date_pretax_npv julia 0.8 0.1 -712.7 1.42 life_to_date_pretax_npv julia 0.9 0.1 -597.8 1.42 life_to_date_pretax_npv julia 1 0.1 -482.8 1.42 life_to_date_pretax_npv julia 1.1 0.1 -367.9 1.42 life_to_date_pretax_npv julia 1.2 0.1 -252.9 1.42 life_to_date_pretax_npv julia 0.8 0.13 -658 1.57 life_to_date_pretax_npv julia 0.9 0.13 -572.5 1.57 life_to_date_pretax_npv julia 1 0.13 -487.1 1.57 life_to_date_pretax_npv julia 1.1 0.13 -401.7 1.57 life_to_date_pretax_npv julia 1.2 0.13 -316.3 1.57 life_to_date_pretax_npv Source: aceengineer/worldenergydata-explorer on Hugging Face · pipeline Snapshot: Rendered from a cached snapshot on 2026-11-16; the upstream dataset may have moved since. Use “Refresh to latest” for current data. Data limits: Life-to-date pretax NPV at various discount rates, computed on public BSEE production — a sensitivity to WTI price (via wti_price_multiplier) and discount rate, NOT full-cycle economics or forward projections. Because it reflects value realized to date, mature fields can show a negative life-to-date NPV. The basis travels with each value (economics_basis). A multi-dimensional field × price × rate grid, honestly shown as a table rather than a single headline number. ## World Energy Field Explorer — AceEngineer Capabilities URL: https://www.aceengineer.com/capabilities/field-explorer.html Description: Global offshore field drill-down — fields, wells, and country rollups built from BSEE and public regulatory filings. World Energy # World Energy Field Explorer Global offshore field drill-down — fields, wells, and country rollups built from BSEE and public regulatory filings. Refresh to latest ## Fields Name Operator Region Status Wells API° Cum oil (MMbbl) Uptime % ID Current Phase Tree Type Formation HPHT Class Pressure psi Temp F TVD ft Equip Rating psi EUR (MMbbl) Avg Decline Pct Yr Concept Type Play Host HPHT Flag HPHT Label Decommission Label N Leases Lease Operator Provenance NPV ($MM) Breakeven WTI ($/bbl) NPV sensitivity ($MM/$) Economics Status Basis EUR Confidence EUR Source Anchor Chevron Green Canyon 807 · US Gulf of Mexico Producing 3 — 18.6 88.1 anchor operate wet Paleocene Wilcox (Wilcox 1–4) ultra-HPHT 25,000 275 30,000 20,000 440 0 Semisub FPU Lower Tertiary Wilcox Semisubmersible FPU true ultra-HPHT · 25k vs 20k psi (+25%) — 2 Chevron Primary facts (operator, working interests, capex $5.6B, plateau 75 mbopd, GOR 1100 scf/bbl, opex $15/boe, first oil 2024-08, data through 2024-12-31) from in-repo anchor.yml. Life-cycle dates corroborated by public sources: discovery well Anchor-2 drilled 2014 (Green Canyon 807, ~5,180 ft), FID December 2019 (~$5.7B sanction), first oil August 2024 — world's first 20,000-psi HPHT deepwater development on a semisubmersible FPU, Lower Tertiary Wilcox play. Working interests (Chevron 62.5% / Equinor 25% / TotalEnergies 12.5%) per YAML; note older Offshore Technology page still lists pre-Equinor split (Chevron 62.86% / Total 37.14%). water depth ~5,180 (block-level estimate). projected end-of-production and lease year not confidently sourced; no notable incident. — — — early_life life_to_date_pretax_npv_at_10pct high 440+ MMboe recoverable (Chevron sanction press release, 2019) Big Foot Chevron Walker Ridge 29 (G16942) · US Gulf of Mexico Producing 8 — 78.7 88.2 big_foot operate dry Wilcox / Paleogene (Lower Tertiary) — — — — — 200 17.2 eTLP Wilcox / Lower Tertiary Extended Tension-Leg Platform (eTLP) false — Decommission ~$43.2M 1 Chevron Data: big_foot.yml + Chevron public disclosures + BSEE (dates to be reconciled in #375) — — — early_life life_to_date_pretax_npv_at_10pct high 200+ MMboe recoverable (Chevron factsheet) Cascade/Chinook MP Gulf of Mexico LLC (Murphy EXPRO) Walker Ridge 206/250 (Cascade), 425/469 (Chinook) · US Gulf of Mexico Producing 3 — 39.7 94.6 cascade_chinook operate wet Wilcox 1 (Eocene) / Wilcox 2 (Paleocene) HPHT 19,500 260 25,600 — — 35.9 FPSO Lower Tertiary (Wilcox) FPSO (BW Pioneer) with subsea tieback true HPHT · 19.5k psi — 2 MP Gulf of Mexico LLC (Murphy EXPRO) Life-cycle dates and ownership from public sources (Offshore Technology, Offshore Magazine, OGJ, Heerema, Rigzone); economics (capex $2.9B, plateau 75 mbopd, GOR 1400 scf/bbl, opex $18/boe) and data through from in-repo YAML. IMPORTANT: two YAML values were overridden as demonstrably wrong vs. well-documented public record — YAML first oil "2021-08" corrected to 2012-02 (Cascade first oil Feb 2012, Chinook Sep 2012; BW Pioneer was the first FPSO in the US GoM), and YAML operator/WI "TotalEnergies 60% / Equinor 40%" corrected to current MP Gulf of Mexico LLC (Murphy EXPRO 80% operator, Petrobras America 20%; originally Petrobras-operated with Total 33.33% in Chinook). LOW CONFIDENCE: FID year (sanction ~mid-2000s, no firm public citation — not available), lease year and projected end-of-production (not available); water depth 8,200 ft is the Cascade value (Chinook ~8,600 ft); capex is a YAML assumption not independently verified. — — — early_life life_to_date_pretax_npv_at_10pct none no field-specific published recoverable EUR; only play-wide figures Jack/St. Malo Chevron Walker Ridge 678 (St. Malo) / 758-759 (Jack) · US Gulf of Mexico Producing 24 — 438.8 89.7 jack_st_malo operate wet Wilcox (Lower Tertiary) HPHT 19,374 224 26,500 — 500 18.4 Semisub FPU Lower Tertiary (Wilcox) Semisubmersible FPU true HPHT · 19.4k psi Decommission ~$80M (FPSO base) 6 Chevron Facts from in-repo YAML (operator, WI Chevron 51%/Equinor 24.5%/Suncor 24.5%, capex $7.5B, opex $15/boe, plateau 94 mbopd, GOR 1200, status producing, data through 2024-12-31). Life-cycle dates from public sources: St. Malo discovered Oct 2003 and Jack Jul 2004 (discovery year=2003, earliest of pair); FID/sanction Oct 2010; first oil per Chevron press release Dec 2014 ("2014-12") — this OVERRIDES the YAML's first oil "2014-02-01", which appears erroneous. Water depth ~7000 ft at the FPU (Jack WR758/759 ~7000 ft, St. Malo WR678). host = Semisubmersible FPU. projected end-of-production not confidently estimable. lease year not available; no schedule-driving incident. -804.5 79 52.3 surfaced life_to_date_pretax_npv_at_10pct high 500+ MMboe recoverable, combined development (original) Julia ExxonMobil Walker Ridge 627 (WR 540/583/584/627/628) · US Gulf of Mexico Producing 4 24.7 77.5 96.3 julia operate wet Wilcox (Lower Tertiary) HPHT 13,500 — 30,000 15,000 — 12.2 Subsea tieback Lower Tertiary Wilcox Subsea tieback to Jack/St. Malo semisubmersible FPU (Chevron) true HPHT · subsea system 13.5k / 15k-psi trees — 1 ExxonMobil Primary facts (capex $4.7B, plateau 34 mbopd, GOR 1000, opex $18/boe, first oil, WI 50/50) from in-repo julia.yml; first oil = BSEE OGOR-A first production (2016-03) per YAML — note ExxonMobil press release states production start April 2016. Operator corrected to ExxonMobil (YAML flagged its "Equinor" operator field as disputed; public record = ExxonMobil-operated, Equinor/Statoil 50% partner). Discovery 2007, FID May 2013, water depth 7000+ ft, Walker Ridge blocks, and Jack/St. Malo tieback from Offshore Technology and operator/trade press. lease year and projected end-of-production not confidently sourced. -482.8 95 17.2 surfaced life_to_date_pretax_npv_at_10pct none no published recoverable EUR (only ~6 Bbbl resource IN-PLACE, != EUR) Kaskida BP Keathley Canyon 292 · US Gulf of Mexico Under construction 0 — — — kaskida execute wet Wilcox / Paleogene ultra-HPHT 20,000 — — 20,000 — — Semisub FPU Lower Tertiary (Wilcox) Semisubmersible FPU (20,000 psi) true ultra-HPHT · 20k vs 20k psi (0%) — 2 BP Discovery 2006 (Keathley Canyon 292, Lower Tertiary Wilcox), FID/sanction July 30 2024 (BP 100%, Devon's original 30% exited), first oil targeted 2029 but left blank as no oil has flowed and the Aug-2025 BOEM DPP rejection likely pushes it out. Public sanctioned figures used over YAML where they diverge: plateau/nameplate 80 mbopd (YAML said 120) and capex ~$5bn for Phase 1 (<$5B per BP; YAML total CAPEX 10000 = $10bn is a full-field/multi-phase estimate). GOR 1000 scf/bbl and data through 2024-12-31 from YAML. Water depth ~6,000 ft, 20,000-psi semisubmersible FPU. Low-confidence: capex (phase-1 vs full-field ambiguity), water depth (rounded), lease year unknown, opex unknown. — — — — — — — North Platte (renamed Sparta) Shell Garden Banks 959 (straddles GB 915/916/958/959) · US Gulf of Mexico Under construction 0 — — — north_platte execute wet Wilcox (subsalt Paleogene) ultra-HPHT — — — 20,000 — — Semisub FPU Wilcox (Lower Tertiary / Paleogene) Newbuild Semisubmersible FPU true ultra-HPHT · 20k-psi equipment — 2 Shell Basis: in-repo YAML (superseded TotalEnergies pre-FID case) reconciled against current public record. North Platte was discovered 2012 (Cobalt/Total, Garden Banks). TotalEnergies (then 60% op, Equinor 40%) withdrew Feb 2022; Shell bought 51% and took operatorship from Equinor (49%), redesigned and renamed the project "Sparta." Shell took FID Dec 2023; first oil projected 2028 (left blank — not yet producing). Water depth ~4,265 ft, subsalt Wilcox, newbuild semisubmersible FPU (8 subsea wells) with ~90,000 boe/d peak (~75 mbopd oil plateau; GOR 1100 scf/bbl from YAML). LOW-CONFIDENCE: capex — YAML's $6B reflects the abandoned TotalEnergies ~$5-7B concept, not Shell's simplified Sparta scope (not publicly disclosed), so not available; opex and projected COP year not publicly defensible. — — — — — — — Shenandoah Beacon Offshore Energy Walker Ridge 52 (blocks 51, 52, N/2 53) · US Gulf of Mexico Producing 4 — 21.2 80.2 shenandoah operate wet Inboard Wilcox (Lower Wilcox) ultra-HPHT 22,000 200 30,000 20,000 332 5.4 Semisub FPU Wilcox (Lower Tertiary) Semisubmersible FPU (FPS, 20,000-psi) true ultra-HPHT · 22k vs 20k psi (+10%) — 2 Beacon Offshore Energy Base facts (operator, capex, plateau, GOR, data through) from in-repo YAML; discovery 2009 (Anadarko Shenandoah-1, WR52), FID/sanction Aug 2021 (Beacon+Navitas), and actual first oil (first of 4 wells online 25 Jul 2025; ramped to 100 kbopd plateau Oct 2025) from public sources — first oil corrected to 2025-07 vs YAML's placeholder 2025-10. Current WI (Beacon 31% op / Navitas 49% / HEQ 20%) post-2021 restructuring. CAPEX 1.8 is YAML-stated and largely reflects pre-development E&A spend (LOW CONFIDENCE for full development cost); OPEX and projected end-of-production, not available (not defensibly sourced); water depth ~5,800 ft. — — — early_life life_to_date_pretax_npv_at_10pct high 332 MMbbl oil 2P (Netherland Sewell independent report, YE2023) Stones Shell Walker Ridge 508 · US Gulf of Mexico Producing 10 — 89 76.9 stones operate wet Paleogene Wilcox (turbidite) HPHT — — 26,500 — 250 21.4 FPSO Lower Tertiary Wilcox FPSO (Turritella / Stones FPSO, disconnectable) true HPHT Decommission ~$80M (FPSO base) 1 Shell Capex ($3.8bn), plateau (50 mbopd), GOR (850 scf/bbl), opex ($15/boe), first oil (2016-09) and status from in-repo stones.yml (Shell FPSO development config). Discovery (2005), FID/sanction (May 2013, Shell 100% owner-operator), Walker Ridge Block 508, ~9,500 ft water depth, and Turritella/Stones FPSO host (world's deepest FPSO) confirmed via Offshore Technology, Offshore Magazine, and NS Energy public sources. lease year and projected end-of-production unknown; no notable schedule-driving incident identified. — — — early_life life_to_date_pretax_npv_at_10pct med_high 250+ MMboe recoverable, Phase 1 (NOT the >2 Bboe in-place) Tiber BP Keathley Canyon 102 · US Gulf of Mexico Under construction 0 — — — tiber execute wet Paleogene Wilcox ultra-HPHT 20,000 — 28,000 20,000 — — Semisub FPU Wilcox (Lower Tertiary / Paleogene) Semisubmersible FPU (single-lift topsides, Kaskida-derived design) true ultra-HPHT · 20k vs 20k psi (0%) — 1 BP Basis: in-repo tiber.yml (operator BP, plateau 80 mbopd, GOR 900 scf/bbl, data through 2024-12-31) plus public sources. BP discovered Tiber Sept 2009 in Keathley Canyon 102, 4,132 ft water. BP reached FID on the combined Tiber-Guadalupe hub 29 Sep 2025 (FID year=2025); Seatrium awarded FPU EPCC. Ownership is now 100% BP (original discovery split BP 62% / Petrobras 20% / ConocoPhillips 18% no longer reflects current WI). Status: execution (post-FID, construction underway). capex set to the sanctioned public figure of $5.0bn for the Tiber-Guadalupe project (YAML's $8bn was a pre-FID Tiber-only planning assumption); note $5bn covers both fields. first oil left blank — oil has not flowed; projected first production is 2030. OPEX, not available (not publicly disclosed; the "$3/bbl below Kaskida" figure is development cost, not opex). projected end-of-production and lease year (not confidently sourced). — — — — — — — ## Wells API Field Cum oil (MMbbl) Uptime % Status Completion Rig Days Drilling Rig Days First Oil Max TVD ft Mud Weight ppg Slot Spud Date Td Date N Workovers 608114075000 anchor 8.4 93.3 producing 260 96 2024-08-01 33,399 — AP001 2021-12-08 2022-03-14 0 608114075100 anchor 9.9 94.3 producing 139 82 2024-11-01 33,367 — AP002 2022-11-16 2023-02-06 0 608114076101 anchor 0.3 76.7 producing — — 2026-04-01 — — w6101 — — 0 608124006200 big_foot 14.9 94.6 producing 265 126 2018-11-01 23,187 16.4 A001 2012-04-03 2012-08-07 1 608124006800 big_foot 4.7 92.4 producing 164 118 2022-07-01 21,801 17 A008 2013-01-22 2021-12-02 1 608124006001 big_foot 32.2 93.7 producing 156 15 2019-06-01 22,253 16.4 A004 2019-03-10 2019-03-25 1 608124006603 big_foot 21.3 92.2 producing 224 18 2020-09-01 21,395 16.4 A006 2020-02-12 2020-03-01 1 608124007102 big_foot 0.9 55.1 producing 129 90 2021-07-01 22,424 — A011-7102 2021-02-21 2021-05-22 2 608124007103 big_foot 1.1 87.4 producing 69 14 2023-12-01 22,969 — A011-7103 2023-09-18 2023-10-02 0 608124006302 big_foot 1.5 96.3 producing 168 13 2025-01-01 21,830 14 A002 2024-07-11 2024-07-24 0 608124006404 big_foot 2 93.9 producing 0 0 2025-10-01 — — A003 — — 0 608124004602 cascade_chinook 5 94.8 producing 90 13 2012-09-01 26,222 — CH002 2010-02-11 2010-02-24 0 608124008300 cascade_chinook 10.4 94.3 producing 128 222 2014-01-01 26,969 — CA006 2013-01-01 2013-08-11 0 608124009700 cascade_chinook 24.3 94.7 producing 311 94 2018-07-01 26,263 — CH004 2014-12-07 2015-03-11 0 608124005000 jack_st_malo 24.7 94.4 producing 245 95 2014-12-01 28,264 — PS005-5000 2011-11-13 2012-02-16 1 608124005300 jack_st_malo 19.3 96.3 producing 116 72 2014-12-01 28,093 — PN001 2011-11-21 2012-10-16 1 608124005400 jack_st_malo 31.8 97.2 producing 80 61 2016-06-01 28,076 — PN002 2011-11-22 2015-07-07 0 608124005600 jack_st_malo 23.4 75.8 producing 248 111 2012-08-01 28,049 — PS003-5600 2011-11-26 2012-03-16 1 608124005700 jack_st_malo 34 96.8 producing 122 82 2015-02-01 28,367 — PS001-5700 2011-12-03 2013-05-04 0 608124005800 jack_st_malo 39.7 96.9 producing 105 44 2016-04-01 28,195 — PS004-5800 2011-12-05 2015-09-21 0 608124005103 jack_st_malo 39.5 95.1 producing 102 32 2015-07-01 28,201 — PS004-5103 2012-06-02 2012-07-04 0 608124001701 jack_st_malo 25.4 78.7 producing 89 22 2013-01-01 27,940 — PS002-1701 2012-10-05 2012-10-27 0 608124010701 jack_st_malo 30.9 96.7 producing 94 29 2016-08-01 28,318 — PN007 2015-11-27 2015-12-26 0 608124005203 jack_st_malo 1.1 15.6 producing 66 30 2017-01-01 28,344 — PS001-5203 2016-10-30 2016-11-29 0 608124011400 jack_st_malo 37.3 96.9 producing 87 57 2017-05-01 28,265 — PS002-1400 2016-12-17 2017-02-12 0 608124011504 jack_st_malo 25.9 92.1 producing 140 38 2017-11-01 28,371 — PS007-1504 2017-04-23 2017-05-31 1 608124011801 jack_st_malo 17.2 96.8 producing 113 81 2018-01-01 28,536 — PS005-1801 2017-06-15 2017-09-04 0 608124012200 jack_st_malo 19.2 95.8 producing 105 47 2018-06-01 28,533 — PS007-2200 2018-01-05 2018-02-21 0 608124011606 jack_st_malo 14.2 96 producing 103 7 2018-12-01 27,998 — PS008-1606 2018-08-31 2018-09-07 1 608124012500 jack_st_malo 10.3 96.4 producing 171 49 2020-05-01 28,547 — PS006-2500 2018-12-23 2019-02-10 0 608124012601 jack_st_malo 2 91.6 producing 174 36 2019-08-01 28,525 — PS003-2601 2019-04-19 2019-05-25 1 608124012804 jack_st_malo 10.8 96.7 producing 132 4 2022-03-01 28,973 — PS009 2019-11-28 2019-12-02 0 608124013202 jack_st_malo 8.9 96 producing 125 81 2021-02-01 28,656 — PN005 2020-07-11 2020-09-30 0 608124013600 jack_st_malo 9.9 94.3 producing 71 46 2021-08-01 28,590 — PS006-3600 2021-04-11 2021-05-27 0 608124014600 jack_st_malo 4.5 95.5 producing 70 55 2023-09-01 28,589 — PS011 2023-04-21 2023-06-15 0 608124015100 jack_st_malo 6.5 96.1 producing 56 38 2024-02-01 28,015 — PS008-5100 2023-10-14 2023-11-21 0 608124015504 jack_st_malo 1.6 92.2 producing 0 0 2025-06-01 — — PS012 — — 0 608124015400 jack_st_malo 0.6 72.2 producing 0 0 2025-12-01 — — PS014 — — 0 608124009400 julia 14.7 96.1 producing 143 116 2016-05-01 30,685 — DC101 2014-07-10 2014-11-03 0 608124003301 julia 12.6 96.2 producing 173 37 2016-03-01 30,453 — JU102 2015-01-20 2015-02-26 0 608124010800 julia 30.9 95.7 producing 130 138 2017-11-01 30,310 — JU104 2016-02-13 2016-06-30 0 608124012701 julia 19.4 97.3 producing 96 19 2020-02-01 29,185 — JU106 2019-10-29 2019-11-17 0 608124014100 shenandoah 5.5 88.5 producing 175 117 2025-07-01 30,780 — SA008 2022-11-22 2023-03-19 0 608124014400 shenandoah 6.4 58.6 producing 186 165 2025-02-01 31,085 — SA009 2022-11-28 2023-05-12 0 608124014003 shenandoah 5.7 93 producing 0 0 2025-08-01 — — SA007 — — 0 608124013900 shenandoah 3.5 80.6 producing 0 0 2025-08-01 — — SA010 — — 1 608124009500 stones 18.7 88.1 producing 152 155 2016-09-01 28,307 — SN105 2014-07-24 2014-12-26 0 608124009900 stones 16.6 85.5 producing 101 79 2016-09-01 28,333 — SN109 2015-03-18 2015-06-05 0 608124010400 stones 2.9 65.9 producing 117 88 2017-05-01 27,326 — SN208 2015-08-07 2017-02-20 0 608124011001 stones 0.2 5.9 producing 112 23 2016-12-01 27,228 — SN110 2016-08-16 2016-09-08 0 Showing 50 of 56 rows — full table on Hugging Face. ## Countries USA333UK308Norway302Australia192Brazil98Angola75Malaysia65Indonesia62Ireland39Denmark33Thailand30China29Egypt29Viet nam29Nigeria28 fields by country (top 15) Country Fields Facilities Badge Module Albania 2 0 SAMPLE offshore_assets (reference) Angola 75 24 SAMPLE offshore_assets (reference) Argentina 3 3 SAMPLE offshore_assets (reference) Australia 192 50 SAMPLE offshore_assets (reference) Azerbaijan 3 9 SAMPLE offshore_assets (reference) Bangladesh 4 1 SAMPLE offshore_assets (reference) Brazil 98 58 ROADMAP brazil_anp Brunei Darussalam 5 0 SAMPLE offshore_assets (reference) Bulgaria 5 3 SAMPLE offshore_assets (reference) Cameroon 4 0 SAMPLE offshore_assets (reference) Canada 22 8 ROADMAP canada China 29 32 SAMPLE offshore_assets (reference) Colombia 2 0 SAMPLE offshore_assets (reference) Congo 12 5 SAMPLE offshore_assets (reference) Congo, The Demo. Rep. of the 3 1 SAMPLE offshore_assets (reference) Croatia 1 2 SAMPLE offshore_assets (reference) Cuba 1 0 SAMPLE offshore_assets (reference) Cyprus 1 0 SAMPLE offshore_assets (reference) Denmark 33 15 SAMPLE offshore_assets (reference) Egypt 29 20 SAMPLE offshore_assets (reference) Equatorial Guinea 16 7 SAMPLE offshore_assets (reference) Falkland Islands (Malvinas) 21 0 SAMPLE offshore_assets (reference) Faroe Islands 4 0 SAMPLE offshore_assets (reference) French Guiana 1 0 SAMPLE offshore_assets (reference) Gabon 17 8 SAMPLE offshore_assets (reference) Gambia 1 0 SAMPLE offshore_assets (reference) Ghana 22 2 SAMPLE offshore_assets (reference) Greece 3 2 SAMPLE offshore_assets (reference) Greenland 4 0 SAMPLE offshore_assets (reference) Guinea 3 0 SAMPLE offshore_assets (reference) Guinea-Bissau 3 0 SAMPLE offshore_assets (reference) Guyana 2 0 SAMPLE offshore_assets (reference) India 12 6 SAMPLE offshore_assets (reference) Indonesia 62 30 SAMPLE offshore_assets (reference) Iran 2 1 SAMPLE offshore_assets (reference) Ireland 39 4 SAMPLE offshore_assets (reference) Israel 14 2 SAMPLE offshore_assets (reference) Italy 10 4 SAMPLE offshore_assets (reference) Japan 1 1 SAMPLE offshore_assets (reference) Kazakhstan 2 4 SAMPLE offshore_assets (reference) Kenya 11 0 SAMPLE offshore_assets (reference) Liberia 8 0 SAMPLE offshore_assets (reference) Libya 5 6 SAMPLE offshore_assets (reference) Madagascar 1 0 SAMPLE offshore_assets (reference) Malaysia 65 48 SAMPLE offshore_assets (reference) Malta 1 0 SAMPLE offshore_assets (reference) Mauritania 6 1 SAMPLE offshore_assets (reference) Mexico 15 6 ROADMAP mexico_cnh Morocco 13 0 SAMPLE offshore_assets (reference) Mozambique 13 0 SAMPLE offshore_assets (reference) Showing 50 of 84 rows — full table on Hugging Face. Source: aceengineer/worldenergydata-explorer on Hugging Face · pipeline Snapshot: Rendered from a cached snapshot on 2026-11-16; the upstream dataset may have moved since. Use “Refresh to latest” for current data. Data limits: Coverage is primarily US Gulf of Mexico deepwater (BSEE) plus selected international basins; not a complete global census. Published fields emphasize operational, geological, production, and provenance attributes. Economics are intentionally absent from this table while the upstream economics configuration is being republished and reviewed. ## Capabilities — Live, Data-Backed | AceEngineer URL: https://www.aceengineer.com/capabilities/ Description: Live engineering and energy-data capabilities from AceEngineer — each backed by a public Hugging Face dataset you can explore and download. Live & data-backed # Capabilities, backed by live data Each capability below is powered by a public Hugging Face dataset that we publish from our engineering and energy-data pipelines. The numbers are the real published records — explore or download them directly. New algorithms are added here automatically as we ship them. ## Live capabilities World Energy ### World Energy Field Explorer Global offshore field drill-down — fields, wells, and country rollups built from BSEE and public regulatory filings. 10 Fields56 Wells84 Countries Coverage is primarily US Gulf of Mexico deepwater (BSEE) plus selected international basins; not a complete global census. Published fields emphasize operational, geological, production, and provenance attributes. Economics are intentionally absent from this table while the upstream economics configuration is being republished and reviewed. View capability →Dataset on Hugging Face ↗ Digital Model ### Digital Model Parametric Atlases Standard-traceable parametric result grids — mooring fatigue (S-N), synthetic-rope fatigue (T-N), and riser code-check utilisation — from digitalmodel's validated reduced-order atlases. 312 Mooring Fatigue (DNV-RP-C203 S-N)120 Synthetic Rope Fatigue (DNV-OS-E301 T-N)2,700 Riser Code Check (API-RP-2RD) Synthetic parametric sweeps generated from the cited standards (DNV-RP-C203, DNV-OS-E301, API-RP-2RD) and validated to under 10% max relative error against held-out samples. For screening and capability demonstration — not a substitute for a project-specific engineering check. View capability →Dataset on Hugging Face ↗ World Energy ### Field Economics Sensitivity Field-economics sensitivity sweep — how life-to-date pretax NPV moves with WTI price and discount rate, on public BSEE production. — data pending publication Follow progress → World Energy ### Field D&C Days QA/QC Bore-by-bore drilling & completion days behind the World Oil April 2026 reconciliation — 253 wellbores across 11 Gulf of Mexico developments, with drilling-day stability proven across data vintages. Browse the interactive drill-down: /capabilities/dc-drilldown.html 11 Reconciliation Matrix253 Per-Well Listing253 Vintage Diff (Drilling Stability) Drilling days = spud to total depth; completion days = ALL post-TD rig time including later recompletion and servicing (the open worldenergydata#846 boundary question). Known caveat: the extractor mixes calendar days (spans under ~250 d) with WAR-union rig-days (longer spans), so batch-drilled wells undercount drilling days — disclosed rather than corrected pending resolution. Producer markers cover the seven core Lower-Tertiary fields only. Drill-down (field ▸ block ▸ bore) →QA/QC report hub →View capability →Dataset on Hugging Face ↗ Digital Model ### Tank Sloshing CFD OpenFOAM VOF sloshing analysis for partially filled tanks — free-decay validation against closed-form theory, a forced-roll period sweep, and the connected twin-tank U-tube exchange mode with its inter-tank mass shift and roll moment. 57 accepted cases106 metrics9,933 response samples Source-neutral reference geometry only — no vessel-specific dimensions are published here. Free-decay frequency matches closed-form theory to 0.30%. The exchange natural period is 14.31 s, measured by phase; the 22-24 s figure previously carried is the amplitude peak, which is loss-controlled and moves with roll amplitude. Damping is quadratic, so equivalent damping is a function of both period and roll amplitude (0.10 to 0.71 across the measured grid) and is not a tank constant. The inertia law predicts the exchange period to +/-3% across conduit areas 3.4-13.5 m2 and fills 25-70%; the loss law reproduces 35 cases to 8.6% rms; the tank moment is closed form to 4.3% rms for periods of 20 s and above, below which the legs' own sloshing modes participate. The former x1.45 magnitude residual is resolved, not carried: it is the weight moment of the whole fluid mass about the roll axis plus the within-leg free surface. Three of 57 cases are published accepted_with_exception for exceeding the 2% cycle-change limit. View capability →Immutable release 1034bb4efc5d Digital Model ### Pipeline Wall Thickness — Six Codes Compared Wall-thickness screening for a reference pipe across six design codes — utilisation and the governing check at each thickness, so the codes are directly comparable. 369 Utilisation by code Reference pipe geometry only (323.9 mm OD) — no client or project-specific data. One row per (code, wall thickness). Utilisation above 1.0 means the check is not satisfied at that thickness; those rows are retained deliberately, because the sweep exists to show where each code turns. The per-check columns are sparse by design — codes do not share a check set, so a null means the code defines no such check, not a missing value. Screening only, not a project design check. View capability →Dataset on Hugging Face ↗ Digital Model ### Corrosion Control — Anode Sizing and Galvanic Index Screening Screening-level sacrificial-anode sizing to DNV-RP-B401 (2021 edition as implemented) for two reference geometries, plus anodic-index screening categories for metal pairs. Screening only: not a project CP design, not a material-compatibility finding, and not qualified for client delivery. 112 Anode sizing768 Galvanic index screening Reference geometries only (a 4-leg jacket and an XL monopile) — no client or vessel-specific data. Anode sizing follows DNV-RP-B401 across 2 structures x 2 climates x 4 coating conditions x 7 design lives. Galvanic verdicts are anodic-index screening categories for all 16x16 metal pairs, including a metal against itself; they indicate where to look, and are not a substitute for a project-specific CP design. Environment allowable dV spans 0.15 V (harsh marine) to 0.5 V (controlled indoor). View capability →Dataset on Hugging Face ↗ Digital Model ### Wall Thickness under Tension and Bending — Nine Codes Wall-thickness utilisation swept over three axes — thickness, effective tension and bending moment — across nine design codes, showing where combined loading rather than pressure becomes the governing limit state. 354,609 Utilisation over tension and moment Reference pipe only — 323.9 mm OD, X65, internal 20 MPa / external 10 MPa. Tension and moment are swept from zero to 60% of capacity at the 18 mm reference wall (T_max 4.65 MN, M_max 355.6 kN·m), a range chosen from first-yield capacity rather than for appearance. Utilisation above 1.0 is retained deliberately: the sweep exists to show where each code turns, so filtering the failures would hide the answer. Per-check columns are sparse by design — the nine codes do not share a check set, so a null means that code defines no such check, not a missing value. Screening only; not a substitute for a project-specific design check. View capability →Dataset on Hugging Face ↗ ## How this works We publish analysis results as versioned datasets on Hugging Face, then this site renders them at build time — so what you see is the same data our tools produce, with provenance and honest coverage notes. Data is refreshed as pipelines run. ## Pipeline Wall Thickness — Six Codes Compared — AceEngineer Capabilities URL: https://www.aceengineer.com/capabilities/pipeline-wall-thickness.html Description: Wall-thickness screening for a reference pipe across six design codes — utilisation and the governing check at each thickness, so the codes are directly comparable. Digital Model # Pipeline Wall Thickness — Six Codes Compared Wall-thickness screening for a reference pipe across six design codes — utilisation and the governing check at each thickness, so the codes are directly comparable. Refresh to latest ## Utilisation by code max 28 wall_thickness_mm across standard Standard Wall Thickness MM Utilisation Governing Check Safe Check Pressure Containment Check Collapse Check Propagation Buckling Check Combined Loading Od MM Grade Check Burst Check Propagation Check Hoop Check Hoop Stress DNV-ST-F101 8 8.71 propagation_buckling false 0.6 2.04 8.71 1.56 323.9 X65 — — — — DNV-ST-F101 8.5 7.48 propagation_buckling false 0.56 1.71 7.48 1.31 323.9 X65 — — — — DNV-ST-F101 9 6.49 propagation_buckling false 0.53 1.45 6.49 1.11 323.9 X65 — — — — DNV-ST-F101 9.5 5.67 propagation_buckling false 0.5 1.24 5.67 0.95 323.9 X65 — — — — DNV-ST-F101 10 4.98 propagation_buckling false 0.47 1.07 4.98 0.82 323.9 X65 — — — — DNV-ST-F101 10.5 4.41 propagation_buckling false 0.45 0.93 4.41 0.71 323.9 X65 — — — — DNV-ST-F101 11 3.93 propagation_buckling false 0.43 0.82 3.93 0.63 323.9 X65 — — — — DNV-ST-F101 11.5 3.51 propagation_buckling false 0.41 0.73 3.51 0.56 323.9 X65 — — — — DNV-ST-F101 12 3.16 propagation_buckling false 0.39 0.65 3.16 0.5 323.9 X65 — — — — DNV-ST-F101 12.5 2.85 propagation_buckling false 0.38 0.58 2.85 0.45 323.9 X65 — — — — DNV-ST-F101 13 2.59 propagation_buckling false 0.36 0.53 2.59 0.41 323.9 X65 — — — — DNV-ST-F101 13.5 2.35 propagation_buckling false 0.35 0.49 2.35 0.37 323.9 X65 — — — — DNV-ST-F101 14 2.15 propagation_buckling false 0.34 0.45 2.15 0.34 323.9 X65 — — — — DNV-ST-F101 14.5 1.97 propagation_buckling false 0.32 0.42 1.97 0.32 323.9 X65 — — — — DNV-ST-F101 15 1.81 propagation_buckling false 0.31 0.39 1.81 0.3 323.9 X65 — — — — DNV-ST-F101 15.5 1.67 propagation_buckling false 0.3 0.37 1.67 0.28 323.9 X65 — — — — DNV-ST-F101 16 1.54 propagation_buckling false 0.29 0.35 1.54 0.27 323.9 X65 — — — — DNV-ST-F101 16.5 1.43 propagation_buckling false 0.28 0.33 1.43 0.25 323.9 X65 — — — — DNV-ST-F101 17 1.32 propagation_buckling false 0.27 0.32 1.32 0.24 323.9 X65 — — — — DNV-ST-F101 17.5 1.23 propagation_buckling false 0.27 0.3 1.23 0.23 323.9 X65 — — — — DNV-ST-F101 18 1.15 propagation_buckling false 0.26 0.29 1.15 0.22 323.9 X65 — — — — DNV-ST-F101 18.5 1.07 propagation_buckling false 0.25 0.28 1.07 0.22 323.9 X65 — — — — DNV-ST-F101 19 1 propagation_buckling false 0.24 0.27 1 0.21 323.9 X65 — — — — DNV-ST-F101 19.5 0.94 propagation_buckling true 0.24 0.26 0.94 0.2 323.9 X65 — — — — DNV-ST-F101 20 0.88 propagation_buckling true 0.23 0.26 0.88 0.2 323.9 X65 — — — — DNV-ST-F101 20.5 0.83 propagation_buckling true 0.22 0.25 0.83 0.19 323.9 X65 — — — — DNV-ST-F101 21 0.78 propagation_buckling true 0.22 0.24 0.78 0.18 323.9 X65 — — — — DNV-ST-F101 21.5 0.74 propagation_buckling true 0.21 0.23 0.74 0.18 323.9 X65 — — — — DNV-ST-F101 22 0.69 propagation_buckling true 0.21 0.23 0.69 0.17 323.9 X65 — — — — DNV-ST-F101 22.5 0.66 propagation_buckling true 0.2 0.22 0.66 0.17 323.9 X65 — — — — DNV-ST-F101 23 0.62 propagation_buckling true 0.2 0.22 0.62 0.17 323.9 X65 — — — — DNV-ST-F101 23.5 0.59 propagation_buckling true 0.19 0.21 0.59 0.16 323.9 X65 — — — — DNV-ST-F101 24 0.56 propagation_buckling true 0.19 0.21 0.56 0.16 323.9 X65 — — — — DNV-ST-F101 24.5 0.53 propagation_buckling true 0.19 0.2 0.53 0.16 323.9 X65 — — — — DNV-ST-F101 25 0.5 propagation_buckling true 0.18 0.2 0.5 0.15 323.9 X65 — — — — DNV-ST-F101 25.5 0.48 propagation_buckling true 0.18 0.19 0.48 0.15 323.9 X65 — — — — DNV-ST-F101 26 0.46 propagation_buckling true 0.17 0.19 0.46 0.15 323.9 X65 — — — — DNV-ST-F101 26.5 0.44 propagation_buckling true 0.17 0.19 0.44 0.14 323.9 X65 — — — — DNV-ST-F101 27 0.42 propagation_buckling true 0.17 0.18 0.42 0.14 323.9 X65 — — — — DNV-ST-F101 27.5 0.4 propagation_buckling true 0.16 0.18 0.4 0.14 323.9 X65 — — — — DNV-ST-F101 28 0.38 propagation_buckling true 0.16 0.18 0.38 0.13 323.9 X65 — — — — DNV-ST-F201 8 0.6 pressure_containment true 0.6 — — — 323.9 X65 — — — — DNV-ST-F201 8.5 0.56 pressure_containment true 0.56 — — — 323.9 X65 — — — — DNV-ST-F201 9 0.53 pressure_containment true 0.53 — — — 323.9 X65 — — — — DNV-ST-F201 9.5 0.5 pressure_containment true 0.5 — — — 323.9 X65 — — — — DNV-ST-F201 10 0.47 pressure_containment true 0.47 — — — 323.9 X65 — — — — DNV-ST-F201 10.5 0.45 pressure_containment true 0.45 — — — 323.9 X65 — — — — DNV-ST-F201 11 0.43 pressure_containment true 0.43 — — — 323.9 X65 — — — — DNV-ST-F201 11.5 0.41 pressure_containment true 0.41 — — — 323.9 X65 — — — — DNV-ST-F201 12 0.39 pressure_containment true 0.39 — — — 323.9 X65 — — — — Showing 50 of 369 rows — full table on Hugging Face. Source: aceengineer/digitalmodel-integrity on Hugging Face · pipeline Snapshot: Rendered from a cached snapshot on 2026-11-16; the upstream dataset may have moved since. Use “Refresh to latest” for current data. Data limits: Reference pipe geometry only (323.9 mm OD) — no client or project-specific data. One row per (code, wall thickness). Utilisation above 1.0 means the check is not satisfied at that thickness; those rows are retained deliberately, because the sweep exists to show where each code turns. The per-check columns are sparse by design — codes do not share a check set, so a null means the code defines no such check, not a missing value. Screening only, not a project design check. ## Wall Thickness under Tension and Bending — Nine Codes — AceEngineer Capabilities URL: https://www.aceengineer.com/capabilities/wall-thickness-tension-moment.html Description: Wall-thickness utilisation swept over three axes — thickness, effective tension and bending moment — across nine design codes, showing where combined loading rather than pressure becomes the governing limit state. Digital Model # Wall Thickness under Tension and Bending — Nine Codes Wall-thickness utilisation swept over three axes — thickness, effective tension and bending moment — across nine design codes, showing where combined loading rather than pressure becomes the governing limit state. Refresh to latest ## Utilisation over tension and moment Code Wall Thickness MM Effective Tension N Bending Moment Nm Utilisation Governing Check Is Safe Burst Utilisation Collapse Utilisation Combined Utilisation Combined Loading Utilisation Hoop Utilisation Hoop Stress Utilisation Pressure Containment Utilisation Propagation Utilisation Propagation Buckling Utilisation DNV-ST-F101 8 0 0 8.71 propagation_buckling false — 2.04 — 1.56 — — 0.6 — 8.71 DNV-ST-F101 8 0 11,853.03 8.71 propagation_buckling false — 2.04 — 1.56 — — 0.6 — 8.71 DNV-ST-F101 8 0 23,706.07 8.71 propagation_buckling false — 2.04 — 1.56 — — 0.6 — 8.71 DNV-ST-F101 8 0 35,559.1 8.71 propagation_buckling false — 2.04 — 1.56 — — 0.6 — 8.71 DNV-ST-F101 8 0 47,412.13 8.71 propagation_buckling false — 2.04 — 1.57 — — 0.6 — 8.71 DNV-ST-F101 8 0 59,265.17 8.71 propagation_buckling false — 2.04 — 1.57 — — 0.6 — 8.71 DNV-ST-F101 8 0 71,118.2 8.71 propagation_buckling false — 2.04 — 1.58 — — 0.6 — 8.71 DNV-ST-F101 8 0 82,971.23 8.71 propagation_buckling false — 2.04 — 1.59 — — 0.6 — 8.71 DNV-ST-F101 8 0 94,824.27 8.71 propagation_buckling false — 2.04 — 1.6 — — 0.6 — 8.71 DNV-ST-F101 8 0 106,677.3 8.71 propagation_buckling false — 2.04 — 1.61 — — 0.6 — 8.71 DNV-ST-F101 8 0 118,530.33 8.71 propagation_buckling false — 2.04 — 1.62 — — 0.6 — 8.71 DNV-ST-F101 8 0 130,383.37 8.71 propagation_buckling false — 2.04 — 1.63 — — 0.6 — 8.71 DNV-ST-F101 8 0 142,236.4 8.71 propagation_buckling false — 2.04 — 1.64 — — 0.6 — 8.71 DNV-ST-F101 8 0 154,089.43 8.71 propagation_buckling false — 2.04 — 1.66 — — 0.6 — 8.71 DNV-ST-F101 8 0 165,942.47 8.71 propagation_buckling false — 2.04 — 1.67 — — 0.6 — 8.71 DNV-ST-F101 8 0 177,795.5 8.71 propagation_buckling false — 2.04 — 1.69 — — 0.6 — 8.71 DNV-ST-F101 8 0 189,648.53 8.71 propagation_buckling false — 2.04 — 1.71 — — 0.6 — 8.71 DNV-ST-F101 8 0 201,501.57 8.71 propagation_buckling false — 2.04 — 1.72 — — 0.6 — 8.71 DNV-ST-F101 8 0 213,354.6 8.71 propagation_buckling false — 2.04 — 1.74 — — 0.6 — 8.71 DNV-ST-F101 8 0 225,207.63 8.71 propagation_buckling false — 2.04 — 1.76 — — 0.6 — 8.71 DNV-ST-F101 8 0 237,060.67 8.71 propagation_buckling false — 2.04 — 1.78 — — 0.6 — 8.71 DNV-ST-F101 8 0 248,913.7 8.71 propagation_buckling false — 2.04 — 1.81 — — 0.6 — 8.71 DNV-ST-F101 8 0 260,766.73 8.71 propagation_buckling false — 2.04 — 1.83 — — 0.6 — 8.71 DNV-ST-F101 8 0 272,619.77 8.71 propagation_buckling false — 2.04 — 1.85 — — 0.6 — 8.71 DNV-ST-F101 8 0 284,472.8 8.71 propagation_buckling false — 2.04 — 1.87 — — 0.6 — 8.71 DNV-ST-F101 8 0 296,325.83 8.71 propagation_buckling false — 2.04 — 1.9 — — 0.6 — 8.71 DNV-ST-F101 8 0 308,178.87 8.71 propagation_buckling false — 2.04 — 1.92 — — 0.6 — 8.71 DNV-ST-F101 8 0 320,031.9 8.71 propagation_buckling false — 2.04 — 1.95 — — 0.6 — 8.71 DNV-ST-F101 8 0 331,884.93 8.71 propagation_buckling false — 2.04 — 1.98 — — 0.6 — 8.71 DNV-ST-F101 8 0 343,737.97 8.71 propagation_buckling false — 2.04 — 2 — — 0.6 — 8.71 DNV-ST-F101 8 0 355,591 8.71 propagation_buckling false — 2.04 — 2.03 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 0 8.71 propagation_buckling false — 2.04 — 1.56 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 11,853.03 8.71 propagation_buckling false — 2.04 — 1.56 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 23,706.07 8.71 propagation_buckling false — 2.04 — 1.56 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 35,559.1 8.71 propagation_buckling false — 2.04 — 1.57 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 47,412.13 8.71 propagation_buckling false — 2.04 — 1.57 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 59,265.17 8.71 propagation_buckling false — 2.04 — 1.57 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 71,118.2 8.71 propagation_buckling false — 2.04 — 1.58 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 82,971.23 8.71 propagation_buckling false — 2.04 — 1.59 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 94,824.27 8.71 propagation_buckling false — 2.04 — 1.6 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 106,677.3 8.71 propagation_buckling false — 2.04 — 1.61 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 118,530.33 8.71 propagation_buckling false — 2.04 — 1.62 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 130,383.37 8.71 propagation_buckling false — 2.04 — 1.63 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 142,236.4 8.71 propagation_buckling false — 2.04 — 1.64 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 154,089.43 8.71 propagation_buckling false — 2.04 — 1.66 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 165,942.47 8.71 propagation_buckling false — 2.04 — 1.67 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 177,795.5 8.71 propagation_buckling false — 2.04 — 1.69 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 189,648.53 8.71 propagation_buckling false — 2.04 — 1.71 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 201,501.57 8.71 propagation_buckling false — 2.04 — 1.73 — — 0.6 — 8.71 DNV-ST-F101 8 154,992.2 213,354.6 8.71 propagation_buckling false — 2.04 — 1.74 — — 0.6 — 8.71 Showing 50 of 354,609 rows — full table on Hugging Face. Source: aceengineer/digitalmodel-integrity on Hugging Face · pipeline Snapshot: Rendered from a cached snapshot on 2026-11-16; the upstream dataset may have moved since. Use “Refresh to latest” for current data. Data limits: Reference pipe only — 323.9 mm OD, X65, internal 20 MPa / external 10 MPa. Tension and moment are swept from zero to 60% of capacity at the 18 mm reference wall (T_max 4.65 MN, M_max 355.6 kN·m), a range chosen from first-yield capacity rather than for appearance. Utilisation above 1.0 is retained deliberately: the sweep exists to show where each code turns, so filtering the failures would hide the answer. Per-check columns are sparse by design — the nine codes do not share a check set, so a null means that code defines no such check, not a missing value. Screening only; not a substitute for a project-specific design check. ## Illustrative Field Economics | AceEngineer URL: https://www.aceengineer.com/case-studies/bsee-field-economics.html Description: Illustrative field economics with synthetic production and assumed costs. Saved NPV and cash flows are illustrative; IRR remains a placeholder. # Illustrative Field Economics ## Illustrative Example This example describes the field economics generator, its saved metrics and saved cash flows. The production profile is synthetic and the financial inputs are assumed. No BSEE records are imported by this generator, and no client engagement or investment decision is represented. ## Production and Financial Basis The script constructs a 180-month profile with a 12-month ramp-up, a 24-month plateau at 100,000 barrels per day and exponential decline using an assumed annual rate of 8%. Monthly production uses an assumed 30.4 days per month. Fixed financial assumptions are $75/bbl oil price, $18/bbl operating cost, $3.5 billion capital expenditure spread across the first 24 months, 18.75% royalty and a 10% annual discount rate. These are script inputs, not calibrated field data. ## Saved Deterministic Outputs Quantity Saved illustrative value Basis NPV (million USD) 6,078.1 Discounted monthly cash flows at the assumed discount rate Production (million bbl) 373.5 Synthetic profile total Payback index (month, zero-based) 32 First positive cumulative cash flow; index 32 is the 33rd modeled month IRR Placeholder; correction pending The attempted NumPy calculation falls back to a hard-coded value on error Table 1. Saved example outputs; these values do not establish investment viability. ## Limitations and Next Step Monte Carlo simulation is not implemented. The generator evaluates one fixed set of assumptions; it does not import lease records or perform sensitivity sweeps. A validated IRR is not established, and a calibrated rebuild is pending. Project use would require qualified production and cost inputs, a corrected return calculation and validation against the governing investment criteria. Analysis duration, consulting cost reductions and investment outcomes are not claimed. ## Related methods Marine Safety Import Coverage Pipeline On-Bottom Stability Assessment ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Engineering and data analysis methods | AceEngineer URL: https://www.aceengineer.com/case-studies/ Description: Method notes on engineering analysis and data workflows: fatigue, FEA post-processing, risers, wall thickness, stability, energy economics and safety data. # Case studies: analysis methods Methods for engineering analysis and data processing. ## Illustrative Field Economics Calculation steps, workflow and technical references. ## Marine Safety Import Coverage Calculation steps, workflow and technical references. ## Multi-Code Wall Thickness Comparison Calculation steps, workflow and technical references. ## Offshore Platform Fatigue Assessment Methods Calculation steps, workflow and technical references. ## OrcaFlex Riser Sensitivity Automation Calculation steps, workflow and technical references. ## Pipeline On-Bottom Stability Assessment Calculation steps, workflow and technical references. ## Automated FEA Post-Processing Pipeline for Subsea Equipment Qualification Calculation steps, workflow and technical references. ## Wind Turbine Foundation Analysis Methods Calculation steps, workflow and technical references. ## Tank sloshing CFD reports Published study methods and release data. Browse the release · Validation fixture · Study method CFD case method · CFD analysis · Tank summary Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Marine Safety Import Coverage | AceEngineer URL: https://www.aceengineer.com/case-studies/marine-safety-correlation.html Description: Marine safety import record: TSB Canada and MAIB UK counts total 53,261 incidents. Cross-source matching performance is not established by the import record. # Marine Safety Import Coverage ## Recorded Import Coverage The Phase 2 marine safety import record reports 47,385 incidents from the Transportation Safety Board of Canada (TSB) and 5,876 from the UK Marine Accident Investigation Branch (MAIB). These recorded source counts sum to 53,261 incidents at the cited revision; they are not a current live database count. The geographic scope stated in the record is North America + UK waters. The counts below cover TSB Canada and MAIB UK only. Source Recorded incidents Recorded date range TSB Canada 47,385 1975-2025 MAIB UK 5,876 2018-2024 Table 1. Source counts and periods reported in the cited import record. ## Identity and Matching Limitations The same record states that MAIB rows lack vessel names and IMO numbers. TSB records include vessel details, but older records can lack location coordinates. The record also notes vessel-creation errors requiring correction. The import counts do not establish cross-source incident matches, a deduplicated cross-jurisdiction total, operator coverage, analyst time savings or matching accuracy. Name-based and IMO-based matching cannot be claimed for MAIB rows without the missing identifiers. ## Sample Visualization Data The sample visualization generator writes fixed example distributions and correlation statistics to sample JSON. It does not rerun the recorded imports or measure correlation results. Its additional authority entries and matching statistics do not establish imported coverage or observed performance. ## Basis for Further Analysis A correlation analysis would require qualified source identifiers, documented matching rules and a retained set of reviewed candidate matches. Source-count arithmetic alone does not establish incident identity or a risk-assessment outcome. ## Related methods Illustrative Field Economics Offshore Platform Fatigue Assessment Methods ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Multi-Code Wall Thickness Comparison | AceEngineer URL: https://www.aceengineer.com/case-studies/multi-code-wall-thickness-comparison.html Description: Analysis method: Multi-Code Wall Thickness Comparison. Workflow, calculation steps and technical references for a separately agreed scope. # Multi-Code Wall Thickness Comparison Method notes for engineering and data workflows. ## The challenge Organise the inputs, calculations and reporting into a repeatable workflow with checks. ## Solution Approach ### Systematic Parameter Sweep The automated analysis evaluated a comprehensive matrix of design parameters: 5 pipe outer diameters (8, 10, 12, 14, and 16 inch), 3 candidate wall thicknesses per OD, design pressures from 5,000 to 10,000 psi, and water depths from 500 to 2,500 m. Each combination was evaluated against all 3 codes simultaneously. ### Governing Code Identification For each pipe size and water depth combination, the automated comparison identified which code governed the minimum wall thickness. The comparison records the governing code for each pipe diameter and water depth. ### Technical References Standard Reference ASME B31.4 S403.2.1 burst, S403.2.2 collapse API 1111 Sec 4 design requirements DNV-ST-F101 Sec 5 wall thickness design ### Tools digitalmodel wall thickness module (Python): Core calculations for ASME B31.4, API 1111, and DNV-ST-F101 aceengineer.com Wall Thickness Calculator: Interactive demo for single-code assessments ## Related methods Pipeline On-Bottom Stability Assessment Automated FEA Post-Processing Pipeline for Subsea Equipment Qualification ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Offshore Platform Fatigue Assessment Methods | AceEngineer URL: https://www.aceengineer.com/case-studies/offshore-platform-fatigue-optimization.html Description: Offshore platform fatigue assessment methods: structural inputs, stress recovery, cycle counting and machine-learning surrogate model checks. # Offshore Platform Fatigue Assessment Methods This page describes the method; it reports no project results. ## Assessment Challenge The assessment links variable environmental and operational loading to fatigue damage at structural connections. ## Assessment Inputs Structural geometry, material properties and connection details Environmental loading, operating history and monitoring data where available Inspection records and the fatigue criteria applicable to the structure ## Assessment Workflow A project assessment would screen source data, recover stresses at the connections of interest, count stress cycles and calculate fatigue damage against the governing criteria. Monitoring and inspection records would need documented quality checks before comparison with model predictions. A machine-learning surrogate model would require retained training inputs, a defined range of use and independent prediction checks against the reference structural model. Those records are needed before a surrogate could be used to reconstruct operational stresses or support a fatigue-life conclusion. ## Evidence Required for an Outcome An outcome would require retained load histories, stress-recovery settings, fatigue calculations and independent model and inspection comparisons against documented acceptance criteria. API RP 2A-WSD and DNV-RP-C203 are reference topics for fixed-platform structural and fatigue assessment. A standards reference does not establish compliance or acceptance of a project. ## Further Reading The fatigue prediction tutorial provides general background on the method. ## Related methods Automated FEA Post-Processing Pipeline for Subsea Equipment Qualification Wind Turbine Foundation Analysis Methods ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## OrcaFlex Riser Sensitivity Automation | AceEngineer URL: https://www.aceengineer.com/case-studies/orcaflex-riser-sensitivity-automation.html Description: Analysis method: OrcaFlex Riser Sensitivity Automation. Workflow, calculation steps and technical references for a separately agreed scope. # OrcaFlex Riser Sensitivity Automation Method notes for engineering and data workflows. ## The challenge Organise the inputs, calculations and reporting into a repeatable workflow with checks. ## Our Solution: OrcaFlex Batch Automation ### Parametric Model Generation Python scripts read the design matrix Excel file and automatically generated all 50 OrcaFlex model files with correct geometry, buoyancy distribution, and environmental loading combinations. ### Batch Processing Simulations are queued for batch execution. ### Automated Results Extraction Post-processing scripts extracted all required outputs (max stress, fatigue damage, effective tension, curvature) and populated standardized comparison tables automatically. ### Report Generation Final deliverable compiled automatically with sensitivity plots, optimization recommendations, and configuration comparison matrix ready for client review. ### Automation Workflow # Batch OrcaFlex Sensitivity Analysis import orcaflex_batch as ofx # Load design matrix from Excel design_matrix = ofx.load_matrix("sensitivity_matrix.xlsx") # Generate model configurations for config in design_matrix: model = ofx.generate_model( base_model="SCR_baseline.dat", tdp_offset=config['tdp_offset'], hangoff_angle=config['hangoff_angle'], buoyancy_length=config['buoyancy_length'], current_profile=config['current'] ) ofx.queue_simulation(model) # Run overnight batch ofx.run_batch(parallel_jobs=8) # Extract results and generate report results = ofx.extract_all_results() ofx.generate_sensitivity_report(results) ## Technical Details ### Output Parameters Extracted Maximum von Mises stress at critical locations Effective tension envelope along riser length Minimum bend radius and curvature Dynamic amplification factors Touch-down point excursion range Hang-off angle variation Fatigue damage at welds (per DNV-RP-C203) ### Technical References API RP 2RD DNV-OS-F201 DNV-RP-C203 API 17B ## Related methods Pipeline On-Bottom Stability Assessment Computational Fatigue Assessment for Offshore Platform ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Pipeline On-Bottom Stability Assessment | AceEngineer URL: https://www.aceengineer.com/case-studies/pipeline-on-bottom-stability-assessment.html Description: Analysis method: Pipeline On-Bottom Stability Assessment. Workflow, calculation steps and technical references for a separately agreed scope. # Pipeline On-Bottom Stability Assessment Method notes for engineering and data workflows. ## The challenge Organise the inputs, calculations and reporting into a repeatable workflow with checks. ## Solution Approach ### Methodology DNV-RP-F109 Generalized Stability Method (absolute stability) applied systematically using digitalmodel's on_bottom_stability module. The method evaluates pipeline stability by comparing hydrodynamic loads from wave and current action against the soil resistance, accounting for pipe weight, buoyancy, and seabed friction. ### Technical Implementation #### Parameter Definition Input parameters were organized into three categories: pipe properties (outer diameter, wall thickness, concrete coating thickness and density), environmental parameters (significant wave height Hs, peak period Tp, current velocity, water depth at each KP station), and soil properties (friction coefficients per DNV-RP-F109 Table 3-2 for clay, sand, and mixed soil zones). #### Automated Sweep Each KP station along the route was evaluated against the load cases. The automated sweep systematically combined environmental conditions with local seabed properties to produce a complete stability map of the pipeline route. #### Result Classification Results were classified by utilisation ratio: green (ratio < 0.8, stable with margin), yellow (ratio 0.8–1.0, marginally stable), and red (ratio > 1.0, unstable, remediation required). This classification enabled rapid identification of problem spans without reviewing individual calculation sheets. ### Technical References Standard Reference DNV-RP-F109 Generalized stability Eq 3.1–3.6 DNV-ST-F101 Pipeline design basis ### Tools digitalmodel OBS module (Python): Core stability calculations per DNV-RP-F109 aceengineer.com OBS Calculator: Interactive demo for single-point assessments ## Related methods Multi-Code Wall Thickness Comparison OrcaFlex Riser Sensitivity Automation ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Automated FEA Post-Processing Pipeline for Subsea Equipment Qualification | AceEngineer URL: https://www.aceengineer.com/case-studies/subsea-fea-automation.html Description: Analysis method: Automated FEA Post-Processing Pipeline for Subsea Equipment Qualification. Workflow, calculation steps and technical references for a separately agreed scope. # Automated FEA Post-Processing Pipeline for Subsea Equipment Qualification Method notes for engineering and data workflows. ## The challenge Organise the inputs, calculations and reporting into a repeatable workflow with checks. ## Our Approach 1 ### Workflow Analysis & Requirements Gathering Define the post-processing workflow, data extraction patterns, code check calculations and reporting requirements. Record the input formats and equipment types before implementing the extraction steps. 2 ### NASTRAN Parser Development Built a robust Python parser for NASTRAN .f06 and .op2 output files. The parser handles multiple solution sequences (SOL 101, 103, 106), extracts element stresses, nodal displacements, and reaction forces with automatic unit handling. 3 ### Code Check Engine Implementation Implemented automated code checks for API 17D and DNV-OS-F101 requirements, including von Mises stress allowables, linearized stress calculations for pressure vessels, and fatigue screening assessments. All calculations are fully traceable with intermediate results documented. 4 ### Interactive Report Generation Developed HTML report templates with Plotly-based interactive stress contour plots, tabular results with conditional formatting, and executive summaries with pass/fail indicators. Reports include all calculation backup for regulatory review. 5 ### Integration & Deployment The pipeline uses a command-line interface to read a NASTRAN output folder and assemble reports. ## Technical Implementation ### Pipeline Architecture The automation pipeline follows a modular architecture designed for maintainability and extensibility: subsea-fea-pipeline/ -- parsers/ | -- nastran_f06.py # Text output parser | -- nastran_op2.py # Binary output parser | -- result_mapper.py # Element-to-component mapping -- code_checks/ | -- api_17d.py # API 17D stress allowables | -- dnv_os_f101.py # DNV pipeline code checks | -- linearization.py # Stress linearization routines -- reporting/ | -- html_generator.py # Report assembly | -- plotly_viz.py # Interactive plots | -- templates/ # Jinja2 report templates -- main.py # CLI entry point ### Key Technical Features Multi-format support: Handles both text (.f06) and binary (.op2) NASTRAN outputs for flexibility across different solver configurations Automatic unit conversion: Detects input units and converts to consistent output units (SI or US customary) based on project settings Component grouping: Maps finite elements to named components using property ID or element set definitions for organized reporting Stress linearization: Implements through-thickness stress linearization per ASME Section VIII Division 2 for pressure vessel assessments Batch processing: Processes multiple load cases and components in parallel using Python multiprocessing ### Code Check Implementation Standard Check Type Implementation API 17D Primary stress limits von Mises vs. allowable based on material grade and temperature API 17D Local stress limits Peak stress evaluation at geometric discontinuities DNV-OS-F101 Burst capacity Hoop stress check with safety factors per location class DNV-OS-F101 Collapse capacity External pressure check with ovality effects Combined Fatigue screening Stress range extraction for fatigue assessment triggering ### Report Features Generated HTML reports include: Executive summary: Pass/fail status for all code checks with critical locations highlighted Interactive stress plots: Plotly-based contour plots with hover data and zoom capability Tabular results: Maximum stresses per component with utilization ratios and conditional formatting Calculation backup: Full calculation trail with intermediate values for regulatory review Load case summary: Applied loads and boundary conditions for traceability Material properties: Temperature-dependent allowables used in code checks ## Technologies & Tools FEA Software: MSC NASTRAN, NX NASTRAN Programming: Python 3.10+ Data Processing: pandas, numpy, scipy Visualization: Plotly for interactive charts and contour plots Reporting: Jinja2 templates for HTML generation Binary Parsing: pyNastran for .op2 file handling Deployment: PyInstaller for standalone executable distribution ## Related methods Computational Fatigue Assessment for Offshore Platform Multi-Code Wall Thickness Comparison ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Wind Turbine Foundation Analysis Methods | AceEngineer URL: https://www.aceengineer.com/case-studies/wind-turbine-foundation-analysis.html Description: Offshore wind foundation assessment methods: load characterization, soil-structure interaction, fatigue calculations and machine-learning surrogate model checks. # Wind Turbine Foundation Analysis Methods This page describes the method; it reports no project results. ## Method Scope This overview identifies the inputs and checks needed to analyse offshore wind foundations. ## Analysis Inputs Foundation geometry, material properties and geotechnical investigation data Environmental conditions and turbine operating and transient load cases Load histories and the design criteria applicable to the foundation ## Assessment Workflow A project assessment would combine load characterization, soil-structure interaction, stress recovery and fatigue damage calculations. Candidate geometries would be checked against the selected fatigue, strength and serviceability criteria. A machine-learning surrogate model would require traceable training data and independent checks against reference simulations across the intended design range before its predictions could support a design decision. ## Evidence Required for Design Use Design use would require the source loads, model configuration, calculation outputs, validation cases and documented acceptance criteria. DNV-ST-0126, DNVGL-RP-C203 and IEC 61400-3-1 are reference topics for support structures and fatigue assessment. Their mention does not establish compliance or certification of a design. ## Further Reading The fatigue prediction tutorial provides general background on the method. ## Related methods Offshore Platform Fatigue Assessment Methods OrcaFlex Riser Sensitivity Automation ## Summary Review the inputs, assumptions and calculation results for the stated scope. Engineering workflows · Technical articles Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Contact AceEngineer | Engineering and AI automation help URL: https://www.aceengineer.com/contact.html Description: If you want help with any work, whether it is automation, AI automation or workflows, let us know. Write to support@aceengineer.com. # Let's discuss your work If you want help with any work, whether it is automation, AI automation or workflows, let us know. Engineering analysis, data work and small-business administration are all welcome. ## Send Us a Message Your Name * Email Address * Company Subject * Select a topic... OrcaFlex Automation Project FEA Post-Processing Automation Fatigue Analysis Services Offshore Platform/Riser Analysis Offshore Wind Engineering EPC Project Support Energy Data Services AI automation or agentic workflow Small-business automation (tax, contracts, administration) General Inquiry Project Type (optional) Select analysis type... Pipeline Stability (OBS) Wall Thickness Design Fatigue Assessment Riser/Mooring Analysis Full Engineering Study Data/Analytics Other Project Details * Send Message ### Get in Touch #### Email support@aceengineer.com #### Telephone +1 713-306-9029 #### Location Houston, TX, USA Serving clients worldwide #### Working Hours Monday - Friday: 9:00 AM - 5:00 PM CST ### Or Choose Your Project Type #### OrcaFlex Automation Batch processing for riser analysis, mooring studies, and sensitivity studies with overnight execution. #### FEA Post-Processing Automated extraction and reporting from NASTRAN, ANSYS, or ABAQUS analysis results. #### Fatigue Analysis S-N fatigue assessment workflows referencing DNV-RP-C203, API RP 2A and BS 7608. 25+ Years Experience 35 of 196 Modules passing cited checks · 2026-10-17 catalogue API/DNV Standards references ## Twenty Pump Card Signatures, Drawn and Measured - AceEngineer URL: https://www.aceengineer.com/demos/dynacard.html Description: The twenty characteristic sucker-rod pump card signatures drawn side by side — fluid pound, gas interference, gas lock, worn barrel, parted rod, pump tagging up and down and the rest — each with the measurement that separates it from its neighbours. # Twenty Pump Card Signatures, Drawn and Measured What each sucker-rod pump condition does to the pump card — and the one measurement that separates it from the conditions it resembles These are pump (downhole) cards, and they are synthetic. Each is drawn at the centre of its condition's parameter range from published signature descriptions, so the geometry a screen looks for is written down and inspectable. They are not measurements from anyone's wells, and they are not a substitute for a labelled field card library. A real card is messier than every one of these. ## How to read these A pump card is a closed loop of load against plunger position over one stroke. Its four corners are the four events of the pump cycle: the standing valve closing and the fluid load transferring onto the travelling valve at the bottom, the plunger lifting the column, the travelling valve opening and the load transferring back at the top, and the plunger falling through the fluid to the bottom again. On every plot below, the dashed rectangle is the card's bounding box — the reference the corner clearances are measured against — and the orange marker is the bottom-right corner, where the travelling valve finishes opening. Net plunger travel is measured to that corner, and pump fillage is net plunger travel over gross plunger travel, on the plunger stroke, never on the surface stroke. An ideal card is a rectangle and no real one is: fluid-load transfer is not instantaneous and it straddles the stroke turnaround, so a healthy card's corners are visibly cut away. Watch what happens to those corners. Nearly every signature below is a corner that has been gouged out, a corner the card now reaches that it should not, or — for a few of them — nothing to do with shape at all. The signatures are grouped by which measurement separates them, because that is the honest grouping: modes inside a family look alike, and modes in different families are rarely confused. Full method, equations and limits are on the dynamometer card method page; to run these against a card of your own, use the signature screen. ## Family 1 — fluid load shed late on the downstroke All four gouge the card's lower-right corner: the rods keep carrying fluid load past the top of the stroke and shed it lower down. The width of that transfer window is what separates them. Fluid pound pump cardLoad against plunger position: full fluid load carried into the downstroke, then collapsing almost vertically part-way down. ### Fluid pound What the card does. Full fluid load is held into the downstroke and then collapses almost vertically. The upstroke also droops slightly as the stroke proceeds. Mechanism. The barrel is only part filled, so the plunger falls through empty space carrying the whole fluid column until it slaps the fluid surface. A starved barrel also lets fluid slip past the plunger for the whole upstroke, which is the droop. What separates it. The collapse is abrupt — under about a fifth of the stroke, against better than 0.4 of it for gas interference. That width is the whole difference between the two. Gas interference pump cardLoad against plunger position: fluid load bleeding off gradually down a long slanted lower branch. ### Gas interference What the card does. Load bleeds off over a long slanted lower branch instead of dropping at the top of the stroke. The lower-right corner is rounded away and the lower branch slopes upward with position. Mechanism. Free gas in the barrel has to be compressed back up to discharge pressure before the travelling valve can open, and compression is gradual. What separates it. Transfer width, and the upward slope of the lower branch. A fluid pound collapses; gas interference bleeds. Standing-valve leak pump cardLoad against plunger position: load shed slowly down the downstroke while the top of the card stays square. ### Standing-valve leak What the card does. Load sheds slowly down the downstroke while the top of the card stays square. Mechanism. Fluid bypasses the standing valve, so it cannot take the fluid column back off the rods at the top of the stroke; the rods keep carrying part of it until the plunger is moving down fast enough to out-run the leak. What separates it. The shelf carries much less load than a fluid pound's, and it is held nearly to the bottom of the stroke rather than released part-way down. Pump tagging up cardLoad against plunger position: an impact spike at maximum position standing clear of the upstroke plateau. ### Pump tagging up What the card does. A distinct impact spike at maximum position, standing clear of the upstroke plateau, on a card body that is otherwise recognisable. Mechanism. The plunger strikes the top of the barrel or the pull tube. While it is jammed there the fluid load has nowhere to go, so it does not transfer at the turnaround at all — it comes off as the plunger backs away, which also opens the lower-right corner. What separates it, and the repair. Peak-load prominence at the top of the stroke. Space the pump down. ## Family 2 — load picked up late on the upstroke Both round away the card's top-left corner while the lower-right stays square — the mirror image of family 1. Travelling-valve leak pump cardLoad against plunger position: load building slowly up the first third of the upstroke. ### Travelling-valve leak What the card does. Load builds slowly up the first third of the upstroke instead of arriving at the turnaround. The top-left corner is rounded away; the lower-right stays square. Mechanism. Fluid bypasses the travelling valve at a rate set by the pressure across it, while the rate the plunger displaces fluid is set by its velocity — which is zero at the turnaround. Near the bottom of the upstroke the leak wins outright and no load develops. What separates it. Which corner is missing. This one loses the top-left; family 1 loses the bottom-right. Delayed travelling-valve closure cardLoad against plunger position: an exponential load pickup confined to the very start of the upstroke. ### Delayed travelling-valve closure What the card does. An exponential load pickup confined to the very start of the upstroke, and then a normal card. Mechanism. A weak or fouled valve spring closes the travelling valve late. What separates it — and where it fails. The curvature of the pickup, over a short window. When the delay is short the affected window is a tenth of the stroke and the card is otherwise healthy, at which point this signature is genuinely lost. It is one of two modes this method will read as normal. ## Family 3 — fluid load lost part-way up the upstroke Both take load off the upstroke before it reaches the top. A cliff or a decay — that is the difference. Plunger out of barrel cardLoad against plunger position: the upstroke falling off a cliff mid-stroke and running flat and low to the top. ### Plunger out of barrel What the card does. The upstroke falls off a cliff mid-stroke and runs flat and low to the top. The top-right corner is missing entirely. Mechanism. The pump is spaced so long that the plunger leaves the top of the barrel before the upstroke ends, dumping the fluid load the moment it clears. What separates it, and the repair. Top-right corner clearance, which is several times a normal card's. Space the pump down. Worn barrel cardLoad against plunger position: upstroke load decaying progressively away from the plateau. ### Worn barrel What the card does. Upstroke load decays progressively away from the plateau; card area is lost gradually. Mechanism. A worn plunger-to-barrel fit slips more as the fluid column builds. What separates it. Gradual decay, not a cliff. The upstroke branch slope is negative and the top-right corner is soft rather than absent. ## Family 4 — mechanical contact at one end of the stroke These two were one label until it was noticed that they are opposite mechanisms with opposite repairs. Collapsing them loses the only thing the diagnosis is for. Pump tagging down cardLoad against plunger position: load dipping sharply below the downstroke line at minimum position. ### Pump tagging down What the card does. Load dips sharply below the downstroke line at minimum position. The card reaches its own bottom-left corner, which a healthy card never does. Mechanism. The plunger strikes the standing valve or the bottom of the barrel and the rods go into compression, so minimum load coincides with minimum position. What separates it, and the repair. Bottom-left corner clearance near zero, and the stroke position of the load minimum. Space the pump up — the opposite of tagging up, which is why the two are separate classes. ## Family 5 — the card's scale, not its shape A normalised card shape cannot see these at all. They are read off absolute load and absolute travel, which is why a card must arrive in real units to be screened for them. Rod parting cardLoad against plunger position: an ordinary-looking loop at a small fraction of working load. ### Rod parting What the card does. A perfectly ordinary-looking loop — at a small fraction of the load a working string carries. Load range collapses against mean load. Mechanism. Below the break nothing is lifted, so the surviving string carries only its own buoyant weight plus friction and inertia. That still traces a closed loop: friction opens it, and rod inertia tilts both branches upward with position. What separates it. Absolute load, not shape. Read the axis, not the outline. Gas lock cardLoad against plunger position: a low-load loop with almost no enclosed area. ### Gas lock What the card does. A low-load loop with almost no enclosed area — the valves never open. Mechanism. Gas trapped in the barrel is compressed and expanded without ever reaching discharge pressure. This is gas interference past the point where the card still has corners to gouge. What separates it. Card area at low absolute load. A parted rod string draws a proper loop; a gas-locked pump draws barely any. Stuck pump cardLoad against plunger position: a tiny collapsed card over a near-zero position range at working load. ### Stuck pump What the card does. Near-zero position range; a tiny collapsed card at working load. Mechanism. Debris, scale or a mechanical obstruction stops the plunger while the surface unit keeps stroking. What separates it. Plunger travel of a few inches at loads that are otherwise normal. Gas lock has the travel and not the load; this has the load and not the travel. ## Family 6 — stroke length against the expected stroke These three differ only in absolute plunger travel. Under a normalised card shape they are literally the same measurement — which is why a screen that works on shape alone cannot separate them, and one that keeps real units can. Normal pump cardLoad against plunger position: a full card with tight corners and flat branches. ### Normal What the card does. Full expected plunger travel, tight corners, flat branches, high fill ratio. The corners are cut away slightly — that is the valve-transfer window, not a fault. Mechanism. The reference case: the pump fills, lifts, transfers and falls as designed. What separates it. Nothing distinguishes a healthy card except the absence of every other signature — which is exactly why absence of a signature is weak evidence. Tubing movement cardLoad against plunger position: an elongated card with a load slope across the loop. ### Tubing movement What the card does. An elongated card — plunger travel longer than the pump geometry accounts for — with a load slope across the loop. Mechanism. Unanchored tubing stretches and contracts with the fluid load through the stroke. What separates it, and the repair. Absolute stroke length against the expected plunger stroke. Consider a tubing anchor. Plunger undertravel cardLoad against plunger position: a correctly shaped card over a badly truncated position range. ### Plunger undertravel What the card does. A correctly shaped card over a badly truncated position range. Mechanism. The plunger never travels the stroke the surface unit is making — rod stretch, tubing movement, or a spacing problem. What separates it. Absolute stroke length again, in the other direction. On a normalised plot this card and a healthy one are indistinguishable. ## Family 7 — loop thickness and load bias Neither is a valve or fillage problem. Both change what the loop encloses rather than which corner it keeps. Excessive friction cardLoad against plunger position: a thick loop with the upstroke carrying extra load and the downstroke less. ### Excessive friction What the card does. A thick loop: the upstroke carries extra load and the downstroke carries less, opening the card and squaring its corners. Mechanism. Rod-on-tubing drag, a tight stuffing box, or a deviated hole. What separates it. Fill ratio approaching one with corner clearances near zero — a card squarer than valve transfer permits. Bent barrel cardLoad against plunger position: load biased with position, shifting the card's centroid off centre. ### Bent barrel What the card does. Load biased with position, shifting the card's centroid off centre. The bias runs in either direction. Mechanism. A bent barrel binds at one end of the stroke — which end depends on the bend, so this one fault draws two mirror-image cards. Both are carried as reference signatures for exactly that reason. What separates it. Branch slopes of the same sign on both branches, with the loop otherwise intact. ## Family 8 — the texture of the trace Roughness alone cannot separate these: sand and vibration both spoil a clean trace. Periodicity does — vibration is a wave, sand is scatter. Sand abrasion cardLoad against plunger position: a jagged, aperiodic load trace over a slightly slanted card. ### Sand abrasion What the card does. A jagged, aperiodic load trace over a slightly slanted card. Mechanism. Grains passing through the plunger-barrel fit; the fit itself wears open, which adds the slant, because a worn fit slips at a rate that follows the differential across the plunger. What separates it. High roughness with low periodicity. The jaggedness is grain-by-grain and therefore not a wave. Excessive vibration cardLoad against plunger position: a regular high-frequency oscillation riding on an otherwise normal card. ### Excessive vibration What the card does. A regular high-frequency oscillation riding on an otherwise normal card. Mechanism. Mechanical resonance or imbalance in the surface unit — not a pump condition at all, which is worth establishing before anyone pulls a pump. What separates it. High roughness with high periodicity: the residual autocorrelates because it is a wave. Paraffin restriction cardLoad against plunger position: concave dents in the trace plus a raised friction signature. ### Paraffin restriction What the card does. Concave dents in the trace plus a raised friction signature on an otherwise normal card. Mechanism. Paraffin narrows the tubing and grabs the rods intermittently. What separates it — and where it fails. Dent count and depth. When the dents are shallow this card is a normal card with a little noise on it, and the signature is genuinely lost. It is the other of the two modes this method will read as normal. ## What these examples are not They are not field cards. Every plot on this page is synthetic, drawn at the centre of a published parameter range. A real card carries measurement noise, a rod string that does not match the model, and often more than one fault at once. Matching a shape is not a diagnosis. Several conditions here draw nearly the same card: gas interference, fluid pound and a standing-valve leak all gut the lower-right corner, and two of them are told apart by the width of one transition that measurement noise can move. Two of the twenty can read as normal. A shallow paraffin restriction and a briefly delayed valve closure both sit on an otherwise healthy card body. Absence of a signature is not evidence of a healthy pump. No accuracy figure is published for this method, deliberately. Checking synthetic cards against their own generators measures self-consistency, not field performance. A number belongs here only when there is a benchmark against labelled real cards to put behind it. Nothing here predicts production. Fillage and displacement give an inferred rate for the stroke recorded; what a well would make after an intervention is not on the card. ## Where these come from The shapes are drawn from published sucker-rod pump signature descriptions and from the geometry of the pump cycle itself — the valve-transfer window that rounds a healthy card's corners, the compression of free gas that slants a lower branch, the rod inertia that tilts both branches of a parted string. Each card is generated deterministically, so the same condition always draws the same reference card and the measurements underneath it are reproducible rather than asserted. The signature screen runs the same generators and the same measurements against a card of your own, and the method page carries the wave equation, the fillage and pressure relationships, and the full limits. Open the signature screen Read the method Run this on your own cards ## AceEngineer — Freespan / VIV Screening URL: https://www.aceengineer.com/demos/freespan.html Description: DNV-RP-F105 simplified freespan VIV screening for pipelines and jumpers — whether vortex-induced vibration governs the span and what span length is allowable. digitalmodel — Engineering Intelligence # DNV Freespan / VIV Screening Analysis ~680 parametric cases across 3 pipe sizes and rigid jumpers 680 parametric cases analysed overnight Generated 2026-04-15 04:03 UTC · demo_01 Live walkthrough — DNV-RP-F105 freespan VIV screening across 680 parametric cases (3 pipe sizes × 8 spans × 5 currents × 4 gap ratios + jumper variants). Download Capability Summary (PDF, 1 page) ## Methodology This analysis implements DNV-RP-F105 simplified VIV screening for pipeline and jumper freespans. The methodology evaluates whether vortex-induced vibrations will develop under steady current loading, using the reduced velocity parameter VR = V / (fn × D). ### Screening Steps Natural frequency — beam-on-elastic-foundation model with pinned-pinned boundary conditions (conservative). fn = Cn/(2π) × √(EI / meffL^(4)) Reduced velocity — VR = Vcurrent / (fn × D) VIV onset check — in-line onset at VR = 1.0, cross-flow onset at VR = 3.0, lock-in range 4.0–8.0 Gap ratio correction — seabed proximity (e/D < 1) delays VIV onset Response amplitude — simplified A/D estimation for screening ### Parameter Matrix Pipelines: 8", 12", 16" × 8 spans (10–80 m) × 5 currents (0.2–1.0 m/s) × 4 gap ratios = 480 cases Jumpers: 8" rigid × 8 spans (5–40 m) × 5 currents × 5 gap ratios (incl. mid-water) = 200 cases ### Screening Criteria PASS — no VIV expected (VR < 1.0) INLINE_ONLY — in-line VIV only (1.0 ≤ VR < 3.0), typically acceptable FAIL_CF — cross-flow VIV onset (VR ≥ 3.0), detailed analysis needed FAIL_LOCKIN — lock-in regime (4.0 ≤ VR ≤ 8.0), critical condition ### Applicable Codes & Standards DNV-RP-F105 (2017) — Free Spanning Pipelines DNV-RP-C205 (2010) — Environmental Conditions and Loads DNV-OS-F101 (2013) — Submarine Pipeline Systems ## Screening Results Summary Pass rate includes PASS + INLINE_ONLY (acceptable for most applications). Type Size Cases PASS INLINE_ONLY FAIL_CF FAIL_LOCKIN Acceptable % Pipeline 8in 160 4 17 131 8 13% Pipeline 12in 160 12 20 112 16 20% Pipeline 16in 160 21 17 102 20 24% Jumper 8in-jumper 200 31 35 99 35 33% ### Take This Analysis Live During Operations This report used design sea states to screen parametric cases overnight. During the actual operation, digitalmodel can feed your vessel's measured motion data — VMMS, IMMS, MRU — directly into the same engineering models for real-time go/no-go decisions. Instead of relying on forecasted Hs limits, freespan VIV screening updates continuously with measured current profiles from ADCPs and vessel-mounted sensors updates continuously with actual crane tip motions, hook loads, and dynamic amplification factors measured on your vessel. Schedule a Technical Demo → ## Assumptions & Limitations Pinned-pinned boundary conditions (conservative — actual supports provide partial fixity) Steady uniform current perpendicular to pipe axis (worst case orientation) No wave-induced loading considered (current-only screening) Effective axial force = 0 (no temperature/pressure-induced axial load data) Added mass coefficient Ca = 1.0 (potential flow theory) Content density = 800 kg/m3 (oil-filled, conservative for empty pipe) Coating thickness from pipe catalog (3LPP or FBE) Thinnest available wall thickness used per pipe size (worst case for VIV) No soil-pipe interaction stiffness modelled (free span only) Single-mode response only (higher modes may be excited at very high V_R) Chart 1: Natural Frequency vs Span Length Log-scale frequency showing how longer spans reduce f_n. Jumper's thicker wall gives higher frequency at same OD. Chart 2: VIV Onset Screening Map Span-current screening at e/D = 1.0. Green = safe, yellow = inline only, orange/red = VIV concern. Chart 3: Max Allowable Span Heatmap Maximum freespan before cross-flow VIV onset at e/D = 1.0. Chart 4: Pass/Fail Screening Matrix Full parametric screening results for all pipeline sizes at e/D = 1.0. Chart 5: Jumper vs Pipeline Comparison Allowable current envelope: 8in pipeline (Sch 40) vs 8in jumper (Sch 120). Thicker jumper wall extends safe operating envelope. These results are preliminary engineering estimates generated by automated parametric analysis. All outputs require review by a qualified engineer before use in design or operational decisions. References: DNV-RP-F105 (2017) — Free Spanning Pipelines · DNV-RP-C205 (2010) — Environmental Conditions and Loads · DNV-OS-F101 (2013) — Submarine Pipeline Systems © 2026 digitalmodel · aceengineer.com ## Overnight Parametric Engineering Demos - AceEngineer URL: https://www.aceengineer.com/demos/ Description: Overnight parametric engineering demos. See 680 freespan cases, 72 wall thickness checks, 180 installation scenarios, and more — all computed overnight with auditable Python code. # Overnight Parametric Engineering Send a design matrix; one batch run returns hundreds of validated, auditable results. Every calculation traces to its international standard. Powered by digitalmodel — open-source Python for offshore engineering. 992+ Parametric cases + Ballymore worked example 5 Engineering disciplines 6 International standards < 8 hrs Compute time per demo batch Download Capability Summary (PDF, 1 page) ## Live Engineering Demos Each demo runs a real parametric analysis, generates validated results, and produces an auditable HTML report. DEMO 01 ### Pipeline Freespan / VIV Screening DNV-RP-F105 • DNV-RP-F110 Automated screening of pipeline freespans for vortex-induced vibration and static stress. Parametric sweep across 3 pipe sizes, 5 current velocities, and multiple gap ratios — including in-line and cross-flow response. 680 parametric cases Run this on your data View detailed report View case studies DEMO 02 ### Pipeline Wall Thickness — Multi-Code Comparison ASME B31.4 • ASME B31.8 • DNV-OS-F101 Burst and collapse wall thickness checks across 6 pipe sizes, 3 design codes, and 4 operating pressures. Automated comparison highlights code-to-code differences and governing cases. 72 parametric cases Run this on your data View detailed report Try the calculator DEMO 03 ### Deepwater Mudmat Installation DNV-RP-H103 • OrcaFlex time-domain Time-domain installation analysis for subsea mudmat foundations. Full factorial sweep of 2 vessels, 6 water depths, 3 mudmat sizes, and 5 sea states — with crane tip motions, sling tensions, and operational weather windows. 180 parametric cases Run this on your data View detailed report View case studies DEMO 04 ### Shallow Water Pipeline Installation (S-lay) DNV-OS-F101 • OrcaFlex time-domain S-lay pipeline installation analysis with stinger geometry, vessel RAOs, and departure angle optimisation. Sweep of 2 lay vessels, 5 pipe sizes, and 6 water depths — with sagbend strain, stinger tip departure, and lay tension extraction. 60 parametric cases Run this on your data View detailed report View case studies DEMO 05 ### Subsea Jumper Installation DNV-RP-H103 • OrcaFlex time-domain Deepwater rigid jumper lift and installation analysis. Full factorial sweep across 2 vessels, 6 water depths, 5 jumper lengths, and 5 sea states — with crane utilisation, sling tension, and operational limits for each combination. Ballymore worked example · 81 tests · 27 sections Run this on your data View detailed report DEMO 06 ### Mooring & Station-Keeping Screening DNV-OS-E301 • API RP 2SK • quasi-static + frequency-domain Mooring concept screening across catenary, taut, and hybrid arrangements. Quasi-static stiffness and frequency-domain response trends for early-FEED concept ranking. Page values are illustrative public-reference until a project run is commissioned. Demo template — awaiting project values Run this on your data View detailed report DEMO 07 ### Sucker-Rod Pump Card Signatures API RP 11L • API 11E • Gibbs wave-equation diagnostics The twenty characteristic dynamometer card signatures of a rod-lifted well — fluid pound, gas interference, gas lock, pump tagging up and down, valve leaks, a parted rod string — drawn side by side, each with the one measurement that separates it from the signatures it resembles. Cards are synthetic reference shapes; no accuracy figure is published for the method, and the page says why. Reference signatures — synthetic, deterministic Open the signature screen View detailed report ## Cross-Demo Comparison Side-by-side view of the 5 fully rendered overnight demo runs — scope, parametric dimensions, case counts, and automation value at a glance. Demo 06 (mooring) is a template; its parametric run is generated per prospect on submission. Demo 07 (rod-pump card signatures) is a reference-signature library rather than a parametric run, so it is not in the matrix. ## How It Works Every demo follows the same auditable, repeatable pipeline. ### 1. Declarative Input You provide a YAML spec with your design matrix — pipe sizes, water depths, sea states, vessel data. No code changes required. ### 2. Automated Analysis digitalmodel runs the parametric sweep overnight: code-checked calculations, OrcaFlex batch runs, post-processing, and validation against international standards. ### 3. Auditable Output Results arrive as interactive HTML reports with plotted data, governing cases highlighted, and full traceability to the standard clause. Compound engineering Enforcement Orchestrator-worker Knowledge parity View engineering services View case studies Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## AceEngineer — Subsea Jumper Installation Analysis Demo URL: https://www.aceengineer.com/demos/jumper-installation.html Description: Deepwater subsea jumper installation analysis — Excel lift calculations rebuilt as auditable Python with 81 validated tests. # Subsea Jumper Installation Analysis Automated deepwater jumper lift engineering — from Excel workbook calculations to auditable Python code with 81 validated tests. 1007module lines 81/81tests passing 27OrcaFlex sections 46.0tonne lift weight Live walkthrough — Ballymore manifold-to-PLET jumper lift, automated OrcaFlex model generation, 81/81 tests passing. Download Capability Summary (PDF, 1 page) ## Ballymore Manifold-to-PLET Jumper Parameter Value Source Pipe OD 10.75 in (273.05 mm) Bare pipe!C4 Wall Thickness 1.79 in (45.47 mm) Bare pipe!C6 Bend Radius 50 in (1.27 m) Bare pipe!C7 Total Pipe Length 71.64 m GA!D32 Steel Linear Weight 255.18 kg/m Bare pipe!H4 Insulated Linear Weight 337.01 kg/m Bare pipe (derived) Buoyancy Modules 22 x 583.77 kg Bouyancy!C8 Strake Modules 2 x 17.24 kg Strake!C8 Grand Total (insulated) 46,032 kg (46.0 Te) Weight Check!C27 Pipe Segments 7 (A-G) with 6 bends GA!C5:C11 ## Crane Utilisation Check Crane Radius SWL Dynamic Cap Status SZ (Saipem 7000) 18 m 77.5 Te 100.75 Te Go PASS DZ Configuration 12 m 100.0 Te 130.0 Te Go PASS ## OrcaFlex Line Sections (27 segments) Section Line Type Length (m) Connector-start OCS 200-V 1.30 A-straight 10.75"Jumper_wCoat 7.26 B-straight 10.75"Jumper_wCoat 1.52 C-bare-start 10.75"Jumper_wCoat 1.04 C-strake-1 10.75"Jumper_wCoat_wStrake 2.16 C-buoy 10.75"Jumper_wCoat_wBuoy 2.03 — 20 additional sections elided for brevity; full 27-row schedule ships with the project deliverable — ## Code Pipeline spec.yml (declarative input) | v jumper_lift.run_jumper_analysis(JumperConfig) |-- compute_pipe_properties() # Steel, insulation, linear weights |-- compute_buoyancy_module() # Buoyancy hydrostatics |-- compute_strake_module() # VIV suppression properties |-- compute_pipe_geometry() # GA: A-G segments + bends |-- compute_rigging() # Sling stiffness + spreader bar |-- compute_crane_check() # SZ + DZ crane utilisation |-- compute_weight_tally() # Grand total weight + COG |-- compute_orcaflex_sections() # 27 line-type segments | v generate_orcaflex_line_sections_yaml() → model.yml | v OrcaFlex analysis → post-processing → report ## GTM Value Metric Before After Calculation audit Hours of manual review 81 automated tests INSTANT Variant analysis Copy spreadsheet, risk errors New JumperConfig params MINUTES OrcaFlex model gen Manual line section entry 27-section YAML auto SECONDS Version control Which Excel is latest? Git-tracked, reviewed AUDITABLE Source: Ballymore MC-651, GOM. Validated against Jumper_Input_Ballymore_Manifold-PLET V2.xlsx — all 81 tests pass. ## AceEngineer — Mooring & Station-Keeping Screening URL: https://www.aceengineer.com/demos/mooring.html Description: Mooring and station-keeping screening for pre-FEED decision gates — catenary, taut and hybrid concepts checked for restoring stiffness, tension margin against MBL and vessel offset. digitalmodel — Engineering Intelligence # Mooring & Station-Keeping Screening Analysis ~120 parametric cases across catenary, taut, and hybrid concepts Demo template — values illustrative until project run Pre-FEED / early-FEED screening · MoorPy quasi-static + RAFT frequency-domain · API RP 2SK / DNV-OS-E301 reference basis ## Methodology This screening evaluates whether a candidate floater-mooring concept is fit-for-purpose at a pre-FEED / early-FEED decision gate. The workflow uses MoorPy quasi-static stiffness analysis to characterise restoring behaviour, then RAFT-based frequency-domain response screening to flag concepts whose surge, heave, or pitch periods sit too close to the wave-energy band. The standards basis is API RP 2SK (stationkeeping system design and analysis) and DNV-OS-E301 (position mooring), which set the safety-factor and analysis-tier expectations the screening is meant to feed. Each candidate concept (catenary, taut, hybrid) is screened for restoring stiffness, line tension margin against minimum breaking load (MBL), vessel offset against the typical 10% water-depth band, and sensitivity of those trends to a ±20% sweep on mooring stiffness assumptions. A concept whose ranking flips under that sweep is flagged for coupled time-domain follow-on rather than declared acceptable. The tier is intentionally screening-grade — quasi-static plus frequency-domain — and is the layer that decides whether the more expensive coupled analysis is worth running. ### Applicable Codes & Standards API RP 2SK — Stationkeeping Systems for Floating Structures DNV-OS-E301 — Position Mooring DNV-OS-E302 / E304 — Offshore Mooring Chain & Steel-wire reference RAFT (NREL) — frequency-domain floating response, screening-tier MoorPy — quasi-static mooring analysis, screening-tier ## Parameter Matrix Illustrative parametric envelope: 3 platforms × 4 mooring concepts × 5 water depths × 2 sea states = 120 cases. The matrix is sized for one batch screening sweep; on a real engagement, axes are replaced with the project's actual platform, candidate spreads, site water depth, and operating / survival metocean. Axis Range Notes Platform Semi-submersible, spar, FPSO-class Public-reference floater archetypes Mooring concept 3-line catenary, 4-line catenary, taut polyester, chain-polyester hybrid 120° or 90° spread depending on concept Water depth 200, 500, 1000, 1500, 2000 m Spans intermediate to deepwater Sea state Operating (1-yr), Survival (100-yr) Hs / Tp pair per state Anchor strategy Drag-embedment, suction pile (downstream of concept) Geotechnical handoff at next gate Pre-tension Set to bring quasi-static surge offset under environmental loading inside the 10% water-depth band Per-line pretension is a result, not a free axis Note: all ranges in this template are illustrative envelope values. A project run replaces them with the actual floater mass / hydrostatic input, candidate spreads, site water depth, and project-specific metocean. ## Screening Results Summary PASS / MARGIN / FAIL distribution by concept and condition. Pass = quasi-static offset inside 10% water-depth band, line tension below API RP 2SK / DNV-OS-E301 intact safety factor, and surge / heave / pitch natural periods clear of the wave-energy band. Margin = at least one of those checks within 10% of the limit or sensitive to the ±20% stiffness sweep. Fail = limit exceeded or rank-flip under sensitivity. All numbers below are illustrative. They show the shape of the screening output, not project-specific results. Per-prospect numbers come from a project run on the prospect's vessel and station-keeping data. Concept Cases PASS MARGIN FAIL Acceptable % Dominant flag 3-line catenary 30 21 6 3 90% Offset margin at 2000 m, survival 4-line catenary 30 25 4 1 97% Tension margin in survival sea state Taut polyester 30 18 8 4 87% Surge period drift under stiffness sweep Chain-polyester hybrid 30 22 6 2 93% Anchor footprint at shallow depths Pass-rate column includes PASS only; MARGIN cases require either tightened assumptions or escalation into coupled time-domain analysis before they can be cleared. ## Concept Comparison Chart Quasi-static restoring stiffness kxx by concept (kN/m, illustrative public-reference order of magnitude only): Concept kxx (kN/m, illustrative) Restoring character 3-line catenary ~80 Soft, geometry-driven; gentle offset growth, large footprint 4-line catenary ~110 Symmetric restoring, redundancy on line failure Chain-polyester hybrid ~140 Tunable via polyester axial stiffness, smaller footprint Taut polyester ~220 Stiff, axial-driven; small footprint, sensitive to pre-tension Reading guide: the chart above is a directional ordering, not a quantitative claim about a specific project. The screening method gives the project's actual k-matrix once mass, hydrostatic, and metocean inputs are loaded; expect the order of magnitude to track the table above, but expect the ratios to shift with floater scale and water depth. ## Where this stops This is a screening-tier deliverable. It is intentionally not, and ACE will not represent it as: Detailed time-domain coupled analysis (OrcaFlex / OpenFAST coupled runs across the full DLC matrix). Full IEC 61400-3-2 design load case execution for a floating wind turbine, including controller-coupled DLCs. Geotechnical anchor capacity design or site-specific foundation engineering — those scopes go to specialist consultants once the screening clears the gate. Final fatigue verification of mooring components for life-cycle signoff or class / certifier submission. What this screening is for: ranking concepts, finding first-order red flags, and deciding whether a concept is mature enough to spend coupled-analysis or geotechnical budget on. It is not a substitute for that follow-on work. ## GTM Value Activity Before After Mooring concept selection Weeks of bespoke setup before any concept is ranked ~120 cases screened in one batch run, then a decision-grade memo Sensitivity check Manual rerun of bespoke models per axis ±20% stiffness sweep baked into the workflow Anchor strategy framing Late-stage hand-off, often after concept locked Anchor implications surfaced at concept gate Escalation gate Implicit, often missed Explicit gap register: which concepts need coupled time-domain follow-on, which do not Reviewer audit trail Spreadsheet provenance Git-tracked Python + YAML, reviewable by a third party Composite of the five shipped overnight runs. The mooring screening above will be replaced with a per-prospect parametric run on submission of vessel and station-keeping data, following the same procedure used for the other demos. Reviewing ACE for early-stage mooring or station-keeping work? Start with the one-page capability summary. Download Capability Summary (PDF, 1 page) ## AceEngineer — Deepwater Mudmat Installation URL: https://www.aceengineer.com/demos/mudmat.html Description: Deepwater mudmat installation screened across a parametric matrix of vessels, water depths, structure sizes and sea states. digitalmodel — Engineering Intelligence # Deepwater Mudmat Installation Analysis 180 parametric cases: 2 vessels x 6 depths x 3 mudmats x 5 sea states 180 parametric cases analysed overnight Generated 2026-04-15 04:04 UTC · demo_03 Live walkthrough — deepwater mudmat installation across 180 parametric cases (DNV H103-coupled, OrcaFlex-driven, vessel-RAO sensitivity). Download Capability Summary (PDF, 1 page) ## Methodology This analysis screens deepwater mudmat installations across a parametric matrix of vessels, water depths, structure sizes, and sea states. Each case evaluates five installation phases per DNV-RP-H103 and DNV-ST-N001 methodology. ### Phase 1: Lift-off Hook load = massair × g × DAFlift (1.10). Checked against crane SWL at operating radius via interpolation of the crane capacity curve. ### Phase 2: In-air Transit Tilt check for 4-point lift with spreader beam. CoG offset / hook height gives tilt angle, checked against 5° limit. Symmetric mudmats always pass. ### Phase 3: Splash Zone (Critical) Slamming force: Fslam = 0.5 × ρ × Cs × Ap × vrel^(2), where vrel = vlowering + vwave. Additional varying buoyancy and drag forces. DAFsplash = 1.30. This phase typically governs for large mudmats in higher sea states. ### Phase 4: Lowering through Water Column Cable tension = Wsub + Wcable(depth) + snap load. Snap load from dynamic cable response using vessel heave RAO. Checked against 85% of wire MBL. Becomes critical at extreme depths due to cable self-weight. ### Phase 5: Landing Bearing pressure = Wsub / Abase. Checked against 50 kPa soft clay bearing capacity. Rarely governs for typical mudmat proportions. ### Go/No-Go Criteria GO: All phases pass AND max utilisation < 0.85 MARGINAL: All phases pass AND max utilisation in [0.85, 1.00] NO-GO: Any phase fails (utilisation > 1.00) ### Applicable Codes & Standards DNV-RP-H103 (2011) — Modelling and Analysis of Marine Operations DNV-ST-N001 (2021) — Marine Operations and Marine Warranty DNV-RP-C205 (2010) — Environmental Conditions and Environmental Loads ## Installation Screening Summary All cases at Hs = 2.0 m reference sea state Vessel Structure Depth (m) Max Util. Governing Phase Status Large CSV Mudmat-S-50te 500 24.7% Landing GO Large CSV Mudmat-M-100te 500 21.5% Landing GO Large CSV Mudmat-L-200te 500 20.6% Splash zone GO Large CSV Mudmat-S-50te 1000 24.7% Landing GO Large CSV Mudmat-M-100te 1000 21.5% Landing GO Large CSV Mudmat-L-200te 1000 20.6% Splash zone GO Large CSV Mudmat-S-50te 1500 24.7% Landing GO Large CSV Mudmat-M-100te 1500 21.5% Landing GO Large CSV Mudmat-L-200te 1500 20.6% Splash zone GO Large CSV Mudmat-S-50te 2000 24.7% Landing GO Large CSV Mudmat-M-100te 2000 21.5% Landing GO Large CSV Mudmat-L-200te 2000 20.6% Splash zone GO Large CSV Mudmat-S-50te 2500 24.7% Landing GO Large CSV Mudmat-M-100te 2500 21.5% Landing GO Large CSV Mudmat-L-200te 2500 20.6% Splash zone GO Large CSV Mudmat-S-50te 3000 24.7% Landing GO Large CSV Mudmat-M-100te 3000 21.5% Landing GO Large CSV Mudmat-L-200te 3000 20.6% Splash zone GO Medium CSV Mudmat-S-50te 500 24.7% Landing GO Medium CSV Mudmat-M-100te 500 34.8% Splash zone GO Medium CSV Mudmat-L-200te 500 71.5% Splash zone GO Medium CSV Mudmat-S-50te 1000 24.7% Landing GO Medium CSV Mudmat-M-100te 1000 34.8% Splash zone GO Medium CSV Mudmat-L-200te 1000 71.5% Splash zone GO Medium CSV Mudmat-S-50te 1500 24.7% Landing GO Medium CSV Mudmat-M-100te 1500 34.8% Splash zone GO Medium CSV Mudmat-L-200te 1500 71.5% Splash zone GO Medium CSV Mudmat-S-50te 2000 24.7% Landing GO Medium CSV Mudmat-M-100te 2000 34.8% Splash zone GO Medium CSV Mudmat-L-200te 2000 71.5% Splash zone GO Medium CSV Mudmat-S-50te 2500 24.7% Landing GO Medium CSV Mudmat-M-100te 2500 34.8% Splash zone GO Medium CSV Mudmat-L-200te 2500 71.5% Splash zone GO Medium CSV Mudmat-S-50te 3000 24.7% Landing GO Medium CSV Mudmat-M-100te 3000 34.8% Splash zone GO Medium CSV Mudmat-L-200te 3000 71.5% Splash zone GO ### Take This Analysis Live During Operations This report used design sea states to screen parametric cases overnight. During the actual operation, digitalmodel can feed your vessel's measured motion data — VMMS, IMMS, MRU — directly into the same engineering models for real-time go/no-go decisions. Instead of relying on forecasted Hs limits, the installation screening updates continuously with actual crane tip motions, hook loads, and dynamic amplification factors measured on your vessel. Schedule a Technical Demo → ## Assumptions & Limitations Crane SWL evaluated at maximum capacity radius (most favourable position) DAF lift-off = 1.10, DAF splash zone = 1.30 per DNV-ST-N001 JONSWAP peak period approximation: Tp = 4 * sqrt(Hs) Slamming coefficient Cs = 5.0 for flat-bottom structures per DNV-RP-H103 Table 4-1 Added mass coefficient Ca = 1.0, drag coefficient Cd = 2.0 for flat plate geometry Wire rope MBL safety factor = 0.85 (max tension / MBL) Bearing capacity limit = 50 kPa (soft clay, undrained) Vessel heave at crane tip uses simplified single-frequency RAO peak No current loads or wind loads on structure during lowering Rigging weight excluded from hook load calculations Seabed assumed flat — no slope corrections for landing Seawater density = 1025 kg/m3 throughout water column Chart 1: Go/No-Go Installation Matrix Side-by-side vessel comparison at Hs = 2.0 m reference sea state. Chart 2: Crane Utilisation vs Water Depth Max utilisation across all phases. Solid = Large CSV, dashed = Medium CSV. Chart 3: Phase Utilisation vs Water Depth — Splash & Lowering Shows how splash zone dominates shallow cases while lowering governs at depth. Chart 4: Operability Envelope — Max Hs vs Structure Weight Maximum sea state where all depths pass. Defines weather window requirements. Chart 5: Vessel Head-to-Head — Structures Installable per Depth Number of mudmat sizes (out of 3) each vessel can install at Hs = 2.0 m. These results are preliminary engineering estimates generated by automated parametric analysis. All outputs require review by a qualified engineer before use in design or operational decisions. References: DNV-RP-H103 (2011) — Modelling and Analysis of Marine Operations · DNV-ST-N001 (2021) — Marine Operations and Marine Warranty · DNV-RP-C205 (2010) — Environmental Conditions and Environmental Loads © 2026 digitalmodel · aceengineer.com ## AceEngineer — Shallow Water Pipelay URL: https://www.aceengineer.com/demos/pipelay.html Description: Shallow-water S-lay pipeline installation screened across a parametric matrix of vessels, pipe sizes and water depths. digitalmodel — Engineering Intelligence # Shallow Water Pipeline Installation Analysis 60 parametric S-lay cases: 2 vessels x 5 pipe sizes x 6 water depths 60 parametric cases analysed overnight Generated 2026-04-15 04:05 UTC · demo_04 Live walkthrough — shallow water pipelay across 60 parametric cases (vessel-RAO and sag-bend tension sensitivity, sea-state envelope). Download Capability Summary (PDF, 1 page) ## Methodology This analysis screens shallow water S-lay pipeline installations across a parametric matrix of vessels, pipe sizes, and water depths. Each case solves the catenary mechanics to find the minimum horizontal tension and evaluates five installation checks per DNV-ST-F101 and API RP 1111 methodology. ### S-lay Catenary Theory During S-lay, the pipe forms a catenary curve from the vessel stinger tip down to the seabed touchdown point (TDP). The catenary is characterised by parameter a = H / wsub, where H is horizontal tension and wsub is submerged weight per unit length. Arc length: s = a × sinh(x/a) Height above TDP: y = a × (cosh(x/a) - 1) Pipe angle: θ = arctan(sinh(x/a)) ### Check 1: Stinger Departure Angle The required departure angle at the stinger tip must fall within the vessel's adjustable range. Large PLV: 2°-8°, Barge: 3°-12°. ### Check 2: Top Tension Tension at stinger departure: Ttop = H × cosh(xdep/a). Must not exceed vessel tensioner capacity (600 te or 250 te). ### Check 3: Sagbend Stress (Critical for Shallow Water) At the TDP, curvature κ = wsub / H gives the tightest bend radius. Combined bending + axial stress: σ = E × OD / (2R) + H / Asteel. Must satisfy σ ≤ 0.72 × SMYS per DNV-ST-F101 installation allowable. ### Check 4: Overbend Stress Pipe bending over the stinger: Rob = Lstinger / sin(θdep). Overbend stress must also satisfy the 0.72 × SMYS limit. ### Check 5: Vessel Capability Pipe diameter must be within vessel's handling range and water depth within operational envelope. ### Go/No-Go Criteria GO: All checks pass AND max utilisation < 0.85 MARGINAL: All checks pass AND max utilisation in [0.85, 1.00] NO-GO: Any check fails (utilisation > 1.00) ### Applicable Codes & Standards DNV-ST-F101 (2021) - Submarine Pipeline Systems API RP 1111 (2015) - Design, Construction, Operation, and Maintenance of Offshore Hydrocarbon Pipelines DNV-OS-F101 (2013) - Submarine Pipeline Systems ## Installation Screening Summary All 60 parametric cases — 2 vessels x 5 pipe sizes x 6 water depths Vessel Pipe WT (mm) Depth (m) T_top (te) Depart. Angle Sagbend Util Max Util. Gov. Check Status Large PLV 8" 8.18 7 2.7 8.0 deg 10% FAIL vessel_capability NO-GO Large PLV 8" 8.18 10 3.9 8.0 deg 7% 7.0% overbend GO Large PLV 8" 8.18 15 5.8 8.0 deg 5% 7.0% overbend GO Large PLV 8" 8.18 20 7.7 8.0 deg 3% 7.0% overbend GO Large PLV 8" 8.18 25 9.6 8.0 deg 3% 7.0% overbend GO Large PLV 8" 8.18 30 11.5 8.0 deg 2% 7.0% overbend GO Large PLV 12" 9.53 7 59.9 8.0 deg 15% FAIL vessel_capability NO-GO Large PLV 12" 9.53 10 85.6 8.0 deg 10% 14.3% tension GO Large PLV 12" 9.53 15 128.4 8.0 deg 7% 21.4% tension GO Large PLV 12" 9.53 20 171.2 8.0 deg 5% 28.5% tension GO Large PLV 12" 9.53 25 214.0 8.0 deg 4% 35.7% tension GO Large PLV 12" 9.53 30 256.7 8.0 deg 3% 42.8% tension GO Large PLV 16" 9.53 7 77.3 8.0 deg 18% FAIL vessel_capability NO-GO Large PLV 16" 9.53 10 110.4 8.0 deg 13% 18.4% tension GO Large PLV 16" 9.53 15 165.6 8.0 deg 9% 27.6% tension GO Large PLV 16" 9.53 20 220.8 8.0 deg 6% 36.8% tension GO Large PLV 16" 9.53 25 276.0 8.0 deg 5% 46.0% tension GO Large PLV 16" 9.53 30 331.2 8.0 deg 4% 55.2% tension GO Large PLV 20" 9.53 7 92.3 8.0 deg 23% FAIL vessel_capability NO-GO Large PLV 20" 9.53 10 131.9 8.0 deg 16% 22.0% tension GO Large PLV 20" 9.53 15 197.8 8.0 deg 11% 33.0% tension GO Large PLV 20" 9.53 20 263.7 8.0 deg 8% 44.0% tension GO Large PLV 20" 9.53 25 329.7 8.0 deg 6% 54.9% tension GO Large PLV 20" 9.53 30 395.6 8.0 deg 5% 65.9% tension GO Large PLV 24" 9.53 7 122.9 8.0 deg 27% FAIL vessel_capability NO-GO Large PLV 24" 9.53 10 175.6 8.0 deg 19% 29.3% tension GO Large PLV 24" 9.53 15 263.4 8.0 deg 13% 43.9% tension GO Large PLV 24" 9.53 20 351.3 8.0 deg 10% 58.5% tension GO Large PLV 24" 9.53 25 439.1 8.0 deg 8% 73.2% tension GO Large PLV 24" 9.53 30 526.9 8.0 deg 6% 87.8% tension MARGINAL Shallow Water Barge 8" 8.18 7 1.2 12.0 deg 22% 22.4% sagbend GO Shallow Water Barge 8" 8.18 10 1.7 12.0 deg 16% 18.3% overbend GO Shallow Water Barge 8" 8.18 15 2.6 12.0 deg 10% 18.3% overbend GO Shallow Water Barge 8" 8.18 20 3.4 12.0 deg 8% 18.3% overbend GO Shallow Water Barge 8" 8.18 25 4.3 12.0 deg 6% 18.3% overbend GO Shallow Water Barge 8" 8.18 30 5.1 12.0 deg 5% 18.3% overbend GO Shallow Water Barge 12" 9.53 7 26.7 12.0 deg 33% 33.2% sagbend GO Shallow Water Barge 12" 9.53 10 38.1 12.0 deg 23% 27.0% overbend GO Shallow Water Barge 12" 9.53 15 57.2 12.0 deg 15% 27.0% overbend GO Shallow Water Barge 12" 9.53 20 76.2 12.0 deg 12% 30.5% tension GO Shallow Water Barge 12" 9.53 25 95.3 12.0 deg 9% 38.1% tension GO Shallow Water Barge 12" 9.53 30 114.3 12.0 deg 8% 45.7% tension GO Shallow Water Barge 16" 9.53 7 34.4 12.0 deg 42% 41.6% sagbend GO Shallow Water Barge 16" 9.53 10 49.2 12.0 deg 29% 33.9% overbend GO Shallow Water Barge 16" 9.53 15 73.8 12.0 deg 19% 33.9% overbend GO Shallow Water Barge 16" 9.53 20 98.3 12.0 deg 15% 39.3% tension GO Shallow Water Barge 16" 9.53 25 122.9 12.0 deg 12% 49.2% tension GO Shallow Water Barge 16" 9.53 30 147.5 12.0 deg 10% 59.0% tension GO Shallow Water Barge 20" 9.53 7 41.1 12.0 deg 52% 52.0% sagbend GO Shallow Water Barge 20" 9.53 10 58.7 12.0 deg 36% 42.4% overbend GO Shallow Water Barge 20" 9.53 15 88.1 12.0 deg 24% 42.4% overbend GO Shallow Water Barge 20" 9.53 20 117.5 12.0 deg 18% 47.0% tension GO Shallow Water Barge 20" 9.53 25 146.8 12.0 deg 15% 58.7% tension GO Shallow Water Barge 20" 9.53 30 176.2 12.0 deg 12% 70.5% tension GO Shallow Water Barge 24" 9.53 7 54.8 12.0 deg 62% 62.4% sagbend GO Shallow Water Barge 24" 9.53 10 78.2 12.0 deg 44% 50.8% overbend GO Shallow Water Barge 24" 9.53 15 117.3 12.0 deg 29% 50.8% overbend GO Shallow Water Barge 24" 9.53 20 156.4 12.0 deg 22% 62.6% tension GO Shallow Water Barge 24" 9.53 25 195.5 12.0 deg 17% 78.2% tension GO Shallow Water Barge 24" 9.53 30 234.7 12.0 deg 15% 93.9% tension MARGINAL ### Take This Analysis Live During Operations This report used design sea states to screen parametric cases overnight. During the actual operation, digitalmodel can feed your vessel's measured motion data — VMMS, IMMS, MRU — directly into the same engineering models for real-time go/no-go decisions. Instead of relying on forecasted Hs limits, the pipeline installation screening updates continuously with actual crane tip motions, hook loads, and dynamic amplification factors measured on your vessel. Schedule a Technical Demo → ## Assumptions & Limitations All pipes are X65 grade (SMYS = 448 MPa, E = 207 GPa) Catenary solution assumes no current loading on the suspended span Sagbend and overbend stresses use simplified elastic beam theory Combined stress is conservative additive (bending + axial) per DNV-ST-F101 Sec 5 Stinger radius approximated as R_ob = L_stinger / sin(theta_dep) No dynamic amplification applied — quasi-static installation assumed Pipe submerged weight includes anti-corrosion coating and CWC where applicable Seabed assumed flat at each water depth — no slope corrections Seawater density = 1025 kg/m3 throughout water column Installation stress limit factor = 0.72 per DNV-ST-F101 (2021) Chart 1: Go/No-Go Installation Matrix Side-by-side vessel comparison across all pipe sizes and water depths. Chart 2: Sagbend Stress Utilisation Heatmap Sagbend utilisation as percentage of 0.72 x SMYS (X65 = 448 MPa). Green = low, red = critical. Chart 3: Required Top Tension vs Water Depth Solid = Large PLV, dashed = Barge. Horizontal lines show tensioner capacity limits. Chart 4: Stinger Departure Angle vs Water Depth Required departure angle with vessel stinger range bands. Shows where stinger geometry governs. Chart 5: Vessel Head-to-Head — Max Pipe Size at Each Depth Maximum installable pipe diameter for each vessel at each water depth. These results are preliminary engineering estimates generated by automated parametric analysis. All outputs require review by a qualified engineer before use in design or operational decisions. References: DNV-ST-F101 (2021) - Submarine Pipeline Systems · API RP 1111 (2015) - Design, Construction, Operation, and Maintenance of Offshore Hydrocarbon Pipelines · DNV-OS-F101 (2013) - Submarine Pipeline Systems © 2026 digitalmodel · aceengineer.com ## AceEngineer — Pipeline Wall Thickness URL: https://www.aceengineer.com/demos/wall-thickness.html Description: Minimum pipeline wall thickness compared across three subsea design codes, showing how each code's philosophy changes the governing result. digitalmodel — Engineering Intelligence # Pipeline Wall Thickness — Multi-Code Comparison 72 parametric cases across 6 pipe sizes, 3 design codes, and 4 operating pressures 72 parametric cases analysed overnight Generated 2026-04-15 04:03 UTC · demo_02 Live walkthrough — pipeline wall thickness across 72 parametric cases under three pressure-design codes simultaneously. Download Capability Summary (PDF, 1 page) ## Methodology This analysis compares minimum wall thickness requirements across three widely-used subsea pipeline design codes. Each code uses a different philosophy: ### DNV-ST-F101 (2021) Uses Load and Resistance Factor Design (LRFD) with partial safety factors on both loads and resistance. The most granular approach with separate factors for safety class (Low/Medium/High), material resistance (γm=1.15), and condition (γSC varies by safety class). Performs four limit state checks: pressure containment, collapse, propagation buckling, and combined loading. ### API RP 1111 (2015) Uses Working Stress Design (WSD) with single design factors applied to material strength. The burst check uses a Barlow-based approach with fd=0.72. Collapse uses an elastic-plastic transition formula. Generally the least conservative of the three codes for typical offshore conditions. ### PD 8010-2 (2015) Also uses Working Stress Design (WSD) based on British Standards tradition. Similar design factor approach (fd=0.72 for hoop stress) with an additional Von Mises equivalent stress check (σe ≤ 0.9 × SMYS). Includes collapse and propagation checks similar to API. ### Common Parameters Grade: API 5L X65 (SMYS = 448 MPa, SMTS = 531 MPa) Water depth: 500 m (external pressure ≈ 5.02 MPa) Internal pressures: 10, 15, 20, 25 MPa Corrosion allowance: 1 mm Safety Class: Medium (DNV), standard factors (API, PD 8010-2) ### Applicable Codes & Standards DNV-ST-F101 (2021) — Submarine Pipeline Systems API RP 1111 (2015) — Offshore Hydrocarbon Pipelines (Limit State Design) PD 8010-2 (2015) — Code of Practice for Pipelines – Part 2: Subsea Pipelines API 5L (2018) — Line Pipe (material grades) ## Summary: Minimum Wall Thickness by Pipe Size and Code At 20 MPa internal pressure, 500m water depth, X65 grade, Safety Class Medium Pipe Size OD (mm) Code Min WT (mm) Governing Check Status 6" 168.3 DNV-ST-F101 8.51 Propagation Buckling PASS 6" 168.3 API RP 1111 7.62 Propagation PASS 6" 168.3 PD 8010-2 8.57 Propagation PASS 8" 219.1 DNV-ST-F101 10.79 Propagation Buckling PASS 8" 219.1 API RP 1111 9.90 Propagation PASS 8" 219.1 PD 8010-2 10.90 Propagation PASS 10" 273.1 DNV-ST-F101 13.19 Propagation Buckling PASS 10" 273.1 API RP 1111 12.30 Propagation PASS 10" 273.1 PD 8010-2 13.30 Propagation PASS 12" 323.9 DNV-ST-F101 15.47 Propagation Buckling PASS 12" 323.9 API RP 1111 14.58 Propagation PASS 12" 323.9 PD 8010-2 15.58 Propagation PASS 16" 406.4 DNV-ST-F101 19.14 Propagation Buckling PASS 16" 406.4 API RP 1111 18.31 Propagation PASS 16" 406.4 PD 8010-2 19.31 Propagation PASS 20" 508.0 DNV-ST-F101 23.65 Propagation Buckling PASS 20" 508.0 API RP 1111 22.87 Propagation PASS 20" 508.0 PD 8010-2 23.87 Propagation PASS ### Take This Analysis Live During Operations This report used design sea states to screen parametric cases overnight. During the actual operation, digitalmodel can feed your vessel's measured motion data — VMMS, IMMS, MRU — directly into the same engineering models for real-time go/no-go decisions. Instead of relying on forecasted Hs limits, wall thickness verification updates continuously with actual crane tip motions, hook loads, and dynamic amplification factors measured on your vessel. Schedule a Technical Demo → ## Assumptions & Limitations All analyses use API 5L X65 grade (SMYS = 448 MPa, SMTS = 531 MPa) Water depth fixed at 500 m for all cases (P_ext ≈ 5.02 MPa) Corrosion allowance = 1.0 mm internal, 0.0 mm external (intact coating assumed) Fabrication tolerance = 12.5% (DNV default for seamless pipe) Ovality = 0.5% (Dmax-Dmin)/Dnom — conservative for good-quality pipe Seamless pipe fabrication (α_fab = 1.0 for DNV, no UOE derating) Temperature derating not applied (operating temperature < 50°C assumed) Safety Class Medium used for DNV (typical for production pipelines) Lifecycle phases use simplified bending moments and tensions No dynamic loading or fatigue effects considered Wall thicknesses from standard pipe schedules per ASME B36.10M Chart 1: Lifecycle Utilisation by Design Code Max utilisation across limit states for each lifecycle phase. Use dropdown to select pipe size. Chart 2: Minimum Required Wall Thickness vs Pipe Size At 20 MPa internal pressure, 500m water depth, X65 grade. Shaded band shows code penalty. Chart 3: Utilisation Heatmap — Pipe Size × Internal Pressure Each cell uses the minimum standard WT from the pipe catalog. Green = safe, Red = overstressed. Chart 4: Steel Weight Penalty — Code Conservatism Cost Difference in required WT between most and least conservative code, at 20 MPa. Chart 5: Governing Limit State Distribution Which limit state governs across all parametric cases, broken down by code. These results are preliminary engineering estimates generated by automated parametric analysis. All outputs require review by a qualified engineer before use in design or operational decisions. References: DNV-ST-F101 (2021) — Submarine Pipeline Systems · API RP 1111 (2015) — Offshore Hydrocarbon Pipelines (Limit State Design) · PD 8010-2 (2015) — Code of Practice for Pipelines – Part 2: Subsea Pipelines · API 5L (2018) — Line Pipe (material grades) © 2026 digitalmodel · aceengineer.com ## Energy Solutions - AceEngineer URL: https://www.aceengineer.com/energy.html Description: Explore AceEngineer's energy solutions, including field development, engineering simulations, and decommissioning. # Energy Solutions The various areas of solutions are below. 📊 See the data behind the work: our live capabilities are each backed by a public Hugging Face dataset you can explore and download. ## Field Development Field economics analysis and development decision support using public production data where available and industry-standard financial modeling. Interactive NPV Calculator - Calculate net present value, IRR, and payback period for field development projects with real-time cashflow visualization Illustrative Field Economics - Deterministic cash-flow example with synthetic production and assumed costs; IRR is a placeholder and a calibrated rebuild is pending ## Design Engineering design A lifecycle digital twin package to help perform design, engineering, operations, and decommissioning. A pipe capacity package to help perform load calculations on pipes. ## Engineering Physics-based animations ## Drilling Day-to-day drilling-related algorithms in near real-time. ## Operations and Production Day-to-day operations and production-related algorithms in near real-time. Fitness for Service (FFS) analysis utilizing API 579 (2016) and BS7910 standards. ## Intervention Intervention or work-over activities. ## Decommission End-of-life or decommissioning engineering. ## Marine Safety Data Integration Cross-database incident correlation and risk intelligence for maritime operations. Marine Safety Import Coverage - The cited Phase 2 import record reports 53,261 incidents from TSB Canada (47,385) and MAIB UK (5,876); those counts do not establish cross-source matching performance Contact us for help: use the contact form or write to support@aceengineer.com. ## Engineering workflow automation | AceEngineer URL: https://www.aceengineer.com/engineering.html Description: OrcaFlex and AQWA batch runs, FEA post-processing and fatigue checks turned into automated, checked workflows. Houston, Texas. # Engineering workflows, automated and checked AceEngineer provides riser, hydrodynamic, asset integrity, cathodic protection and marine installation analysis for offshore engineering firms, EPC contractors and drilling contractors. We run that work as automated, checked workflows, with AI agents doing the repeat steps and an engineer signing the result, and we bring the same approach to independent contractors and small and medium-sized businesses (SMBs). OrcaFlex and AQWA batches, FEA post-processing and fatigue checks are topics for discussion under a separately agreed scope. Contact us for help Explore Live Data ## Core Automation Capabilities Pre-built automation modules ready to integrate with your existing OrcaFlex, AQWA, and ANSYS workflows. ### OrcaFlex Batch Processing Automated model generation from design matrices Parametric sensitivity studies (50-100+ configurations) Results extraction to standardized reports VIV analysis and fatigue post-processing ### AQWA Hydrodynamic Automation Batch vessel motion analysis for multiple sea states RAO processing and response statistics Operability window calculations Multi-body interaction studies ### Fatigue Analysis Library S-N curve lookup and fatigue assessment DNV-RP-C203, API RP 2A, BS 7608, ABS, Norsok Automated SCF calculation and damage assessment Batch processing for 200+ joints ### Mooring & Riser Design SALM and CALM buoy system design Catenary analysis and anchor verification SCR and SLWR configuration optimization Installation engineering support ## For Offshore Engineering Firms Mid-market engineering consultancies with 10-50 engineers serving operators and contractors ### Your Pain Points Manual Iteration Hell: Sensitivity studies require 50+ model variations, each taking 30 min setup + 30 min extraction Standards Review Burden: DNV, API, ABS requirements constantly evolving; maintaining S-N curve libraries is tedious Knowledge Concentration: Can't afford dedicated OrcaFlex scripting expert; expertise concentrated in 1-2 senior engineers ### Our Solution 50 manual OrcaFlex runs → Batch processing overnight S-N curve lookup errors → DNV-RP-C203 calculator curves Results extraction tedium → Automated report generation Knowledge concentration → Documented, repeatable workflows Discuss Your OrcaFlex Workflow ## For Offshore Wind Developers Project teams entering the offshore wind market with foundation and cable design needs ### Your Pain Points Foundation Fatigue Complexity: Monopile/jacket fatigue requires 200+ joints; offshore standards (DNV) unfamiliar to onshore wind teams Cable & Export Route Analysis: Subsea cable installation analysis, route optimization, seabed interaction modeling Talent Shortage: Offshore structural engineers in high demand; can't hire fast enough for project schedules ### Our Solution 200+ fatigue joints → Batch analysis with S-N curves DNV unfamiliarity → Calculations with standards references Cable installation → AQWA/OrcaFlex automation Staff shortage → Engineering capacity on-demand "Offshore engineering expertise without hiring offshore engineers." Discuss Your Wind Project ## For EPC Contractors Installation and fabrication contractors where analysis bottlenecks delay operations ### Your Pain Points Weather Window Analysis: Vessel operability requires 100+ sea states Installation Pre-Engineering: Lift analysis for multiple equipment pieces; motion allowables for offshore transfers; last-minute scope changes Contractor Deliverable Review: Checking sub-contractor analysis packages; reviewing standards references; tight review timelines ### Our Solution Weather window analysis → Real-time operability tool Lift analysis iterations → Parametric model generation Deliverable review → Automated validation checks "Don't let analysis be the reason you miss your weather window." Discuss Your Installation Schedule ## Engineering Calculators Try our methodology. Interactive tools for preliminary engineering assessments. ### S-N Curve Fatigue Calculator Calculate fatigue life using the listed DNV-RP-C203 S-N classes. Regression tests cover these classes in air, seawater with cathodic protection and free corrosion. Try Calculator ### Stress Concentration Factor Automated SCF calculation for tubular joints per DNV-RP-C203 and API RP 2A methodologies. Coming Soon ### Pressure Vessel Calculator ASME Section VIII calculations for cylindrical and spherical pressure vessel design. Coming Soon View All Calculators ### Standards & Software Integrations Standards referenced by the workflows DNV RP-C203 API RP 2A BS 7608 OrcaFlex API Automation AQWA Integration ### Related Technical Articles #### Python Engineering Automation From manual workflows to reproducible analysis #### Fatigue Life Prediction Beyond S-N curves with data-driven methods #### Offshore Standards Guide DNV, API and BS standards references #### CFD for Offshore Wave loading, VIV analysis, and practical guidance ## Analysis methods Read the engineering and data workflow methods. AI automation · Small-business automation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## FAQ - AceEngineer URL: https://www.aceengineer.com/faq.html Description: Frequently Asked Questions about AceEngineer's engineering automation services, including OrcaFlex automation, fatigue analysis, and computational workflows. # Frequently Asked Questions How does AceEngineer automate engineering workflows? We replace manual, repetitive engineering workflows with automated pipelines. The workflow can include model setup, batch execution, results extraction and report compilation. Inputs, checks and engineering review are agreed for the stated scope. What standards do you support? Standards referenced by the modules include: Fatigue: DNV-RP-C203, API RP 2A, BS 7608, ABS, Norsok Riser/Pipeline: API RP 2RD, API STD 2RD, DNV-OS-F201 Offshore Wind: IEC 61400-3, DNV-ST-0126 Pressure Vessels: ASME B31.8, API 579 Regression tests cover the DNV-RP-C203 classes listed in the public fatigue calculators, in air, seawater with cathodic protection and free corrosion. What software tools do you integrate with? Our primary integrations are: OrcaFlex: Full Python API integration for batch model generation, simulation, and post-processing AQWA: Hydrodynamic model generation, RAO processing, and operability analysis NASTRAN/ANSYS: FEA post-processing automation and report generation Python/Polars: High-performance data processing for large engineering datasets What are the typical engagement models? Per-project: a defined deliverable for an agreed scope Annual retainer: ongoing automation runs and support Custom development: Time and materials for bespoke automation pipelines How is intellectual property handled? Data is completely abstracted from the computational methods. Client-specific configurations and results remain confidential. Where practical and not constrained by IP, our core engineering libraries are open-source for transparency and validation. Client-specific automation scripts are delivered via private repositories. What engineering quality practices do you follow? All code follows production software engineering standards: Test-Driven Development (TDD) with comprehensive unit and integration tests Version-controlled, documented, and peer-reviewed code Recorded inputs and results for engineering review Regression tests for the listed DNV-RP-C203 calculator classes in air, seawater with cathodic protection and free corrosion Have a question not answered here? Contact Us Contact us for help: support@aceengineer.com ## AceEngineer | Engineering analysis and AI automation URL: https://www.aceengineer.com/ Description: AceEngineer provides riser, hydrodynamic, asset integrity, cathodic protection and marine installation analysis for offshore engineering firms, EPC contractors and drilling contractors. Engineering analysis, AI automation and agentic workflows | Houston, Texas # Engineering analysis that is practical, dependable and repeatable. AI automation and agentic workflows are topics for discussion under a separately agreed scope. Start with our public data and code: digitalmodel, worldenergydata and assetutilities on GitHub, and our datasets on Hugging Face. Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com Latest issue: The Deckhand Chronicles, issue 1 · Newsletter archive Founded 2010 Houston, Texas 25+ years of experience Principal engineer, offshore and marine Public, checked code 35 of 196 modules pass their cited checks (catalogue run 2026-10-17) ## Services AceEngineer provides riser, hydrodynamic, asset integrity, cathodic protection and marine installation analysis for offshore engineering firms, EPC contractors and drilling contractors. We run that work as automated, checked workflows, with AI agents doing the repeat steps and an engineer signing the result, and we bring the same approach to independent contractors and small and medium-sized businesses (SMBs). ### Asset integrity and fitness-for-service Client receives: a remaining-strength calculation report with a stated decision: accept, re-rate, take more measurements, or escalate sample report in preparation ### Riser analysis Client receives: an operability envelope and a riser analysis calculation report. Riser analysis and operability envelopes for drilling risers. sample report in preparation ### Hydrodynamics and vessel motions Client receives: a vessel motions calculation report. Wave diffraction and radiation analysis, with diffraction results compared between two solvers. sample report in preparation ### Cathodic protection screening Client receives: screening calculations, subject to qualified inputs and an engineer-of-record check. Sacrificial-anode screening to DNV-RP-B401 and DNV-RP-F103. sample report in preparation ### Marine installation screening Client receives: utilisation by phase and an operability limit on significant wave height. Lifting and lowering operations screened by phase. sample report in preparation ### Offshore energy data and field analytics Client receives: drilling and completion durations; per-well drilling and completion-day listings. Well, lease and production analysis for the United States Gulf of Mexico. sample report in preparation ### AI automation and agentic workflows AI automation and agentic workflows for engineering and small-business administration. Contact us to discuss a separately agreed scope. ### AI and automation help for small businesses From tax to analysis to contract negotiation to improvements, construction ideas or any administrative automation work. Module count: catalogue date, criteria and revision ## Contact Vamsee Achanta, P.E., Principal Engineer support@aceengineer.com +1 713-306-9029 ## Compliance Dashboard - AceEngineer URL: https://www.aceengineer.com/methodology/compliance-dashboard/ Description: How ACE Engineering measures and reports workflow compliance across every project deliverable. # The Compliance Dashboard How we measure whether engineering work actually followed the workflow it was supposed to follow. ACE Engineering MethodologyQuality assurance • Workflow auditingClient-facing publication The methodology pages describe AI agents working on planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. ## On this page What the Dashboard Measures How Compliance Is Calculated Enforcement Levels The Audit Trail Why This Matters for Clients Integration With Project Delivery ## Compliance Dashboard: Trust, but Verify Engineering policies that are not measured are policies that are not followed. The compliance dashboard converts our delivery workflow from aspiration into auditable evidence. ## What the Dashboard Measures Every engineering deliverable produced through our workflow is supposed to follow the same path: plan, independent review, implement, independent review, ship. The compliance dashboard answers a simple question: did it actually happen? For any window of work — the last 24 hours, the last week, an entire project — the dashboard scans every commit, classifies which ones required review, and checks whether review evidence exists for each. The output is a single number: the percentage of reviewable work that received independent review. ### Why the Question Matters Without measurement, workflow compliance drifts. Reviewers get busy, deadlines compress, and "we'll review the next one" becomes the default. We saw this directly in our own historical data: when we first instrumented the dashboard, compliance was running at 4 percent. That number was a wake-up call. It has since climbed past the 80 percent threshold and stayed there because the dashboard makes drift visible the day it happens, not the quarter after. ## How Compliance Is Calculated The calculation is deliberately transparent so that any client or auditor can reproduce it from the underlying repository: Scan recent commits over a configurable window (default: 24 hours). Classify each commit by its purpose. Documentation, formatting, sync, and merge commits are skipped — they do not require independent review. Feature work, fixes, refactors, performance changes, and security work are flagged as reviewable. Check each reviewable commit for review evidence. Evidence sources include approved plan markers, recorded review files in the planning archive, formal review reports, and review keywords in commit messages. Calculate the rate: reviewed commits divided by reviewable commits, expressed as a percentage. Compare against the threshold: 80 percent by default, configurable per project. ### Example Output ============================================================ Compliance Report — Last 24h ============================================================ Total commits: 42 Skipped (docs/etc): 19 Reviewable: 23 Reviewed: 1 Unreviewed: 22 -------------------------------------------- Compliance rate: 4% (threshold: 80%) Verdict: FAIL This is the actual output from an early audit run. The verdict line is what made the problem actionable: not a 60-page report, but a one-line score that anyone on the team could read in three seconds. ## Enforcement Levels The dashboard is one half of the compliance story; gates that block out-of-policy work are the other. We operate at two enforcement levels depending on project criticality: Level Behavior When We Use It Advisory Prints warnings, allows the work through Early-stage exploration, internal tooling Hard Blocks the operation until the policy is satisfied Client deliverables, regulated work, production projects For client engagements, we default to hard enforcement. The cost of letting one undetected unreviewed change slip into a deliverable is higher than the cost of a five-minute review pause. ## The Audit Trail Behind the dashboard's single compliance number sits a structured log trail that makes every claim verifiable: Log What It Tracks Daily compliance metrics One JSON file per day capturing the full report Plan-gate events Every block or pass at the planning gate Review-gate bypass log Any attempt to bypass review, with user and branch attribution Review-gate latency log Execution timing so the gate stays fast Pattern log Repeated drift signals worth investigating Each log is append-only and timestamped. If a regulator, partner, or client asks "did your team follow your stated review process on project X between dates A and B?", the answer is reconstructable from the logs alone — we are not relying on memory or after-the-fact reconstruction. ## Why This Matters for Clients Three concrete benefits flow from running this dashboard on every project: Defensible deliverables. When we hand over an analysis, we can show that every reviewable change passed through independent review. The audit trail is part of the deliverable, not separate from it. Early drift detection. Compliance dropping from 90 percent to 70 percent over a week is a leading indicator that something has changed in how the team is working. We see it immediately rather than discovering it during a delivery review. Accountability without ceremony. The dashboard does not require status meetings or compliance officers to function. The numbers update automatically, the gates fire automatically, and the logs accumulate automatically. The team's energy stays on engineering work. ## Integration With Project Delivery For client engagements, the compliance dashboard runs nightly via scheduled jobs. When the rate drops below the threshold, the system automatically opens an internal ticket capturing the affected commits, the missing evidence, and the responsible reviewers. By the time the next workday starts, the gap is already on someone's queue. For high-criticality work — safety-relevant analyses, structural assessments backing regulatory submissions, or anything labeled engineering-critical — we track a separate, stricter compliance rate. This rate has its own threshold and its own escalation path. The principle: not every change carries equal weight, and the measurement should reflect that. ## Key Takeaway The compliance dashboard is what turns a stated workflow into a verifiable workflow. We do not ask clients to take our word for whether our engineering process was followed. The number is published, the logs are auditable, and the gates fire on every commit regardless of who is at the keyboard. That is the difference between a quality system and a quality slogan. Want auditable engineering with measurable workflow compliance built in? Contact ACE Engineering to learn how this dashboard pattern integrates with your project governance. ## Engineering you can audit We instrument every project with the compliance signals you need to verify our process — not just trust it. Talk to ACE EngineeringDownload Capability Summary (PDF, 1 page) ## Compound Engineering Framework - AceEngineer URL: https://www.aceengineer.com/methodology/compound-engineering/ Description: Systematic engineering delivery that improves with every project. # Compound Engineering Framework Systematic engineering delivery that improves with every project. ACE Engineering MethodologyOffshore • Structural • Pipeline DeliveryClient-facing publication The methodology pages describe AI agents working on planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. ## On this page What Compound Engineering Means The Compound Loop The Five Lessons Lesson 1: Enforcement Over Instruction Lesson 2: Orchestrator-Worker Separation Lesson 3: Compound Learning Loop Lesson 4: Multi-Agent Knowledge Parity Lesson 5: Independent Cross-Review How the Five Lessons Reinforce Each Other What This Means for Your Projects For Engineering Managers For Quality Assurance Teams ## Compound Engineering: A Framework for Continuous Improvement Every completed project makes the next one faster, more reliable, and less expensive. This is not a theory — it is an operational methodology running in production. ## What Compound Engineering Means Compound engineering is the practice where every completed task leaves the engineering system better than it found it. When a project encounters a pitfall — say, an analysis tool returning frequencies in an unexpected unit order — the fix does not stay in that project. It gets captured into a reusable knowledge base, committed to version control, and is immediately available to every engineer and every tool on every machine. The next project that touches the same analysis tool never hits the same problem. ### The Compound Loop Project encounters a technical pitfall --> Pitfall is documented in a reusable knowledge entry --> Version control makes it available across the organization --> Next project avoids the pitfall entirely --> Saved time is reinvested in new engineering work --> New work encounters new edge cases --> Cycle continues, compounding over time After 12+ months of running this methodology in production, the compound effect is substantial: 690+ reusable knowledge entries spanning 48 engineering categories cover most recurring patterns Nightly learning pipelines automatically extract session learnings, sync team knowledge, and validate existing entries Cross-team knowledge bridges ensure that what one engineer or tool discovers, everyone knows by the next workday ## The Five Lessons Compound engineering rests on five operational principles. Each one was discovered through production experience, not designed in advance. ### Lesson 1: Enforcement Over Instruction Text-based rules degrade over time. We measured 4% compliance when relying on written instructions alone. Technical enforcement — automated gates, pre-commit hooks, CI checks — achieves near-100% compliance on critical quality controls. The principle: If you can express a rule as a pass/fail check, automate it. If it must fire on every deliverable, make it a mandatory gate. ### Lesson 2: Orchestrator-Worker Separation Complex engineering tasks degrade when a single person or tool tries to plan, implement, review, and deliver in one continuous session. Context overload sets in. The original plan gets fuzzy. Work begins addressing problems that do not exist. The solution: One role maintains the plan and delegates focused tasks. Workers execute in isolation and return results. The orchestrator verifies each result against the original specification. ### Lesson 3: Compound Learning Loop The core mechanism of the methodology. Every project writes back to the shared knowledge base: Pitfall documentation: When an edge case is discovered, it gets a permanent entry. Over 220 known pitfalls are now documented. Cross-cutting knowledge: Engineering lessons covering tool quirks, debugging protocols, and domain-specific patterns. Automated pipelines: Nightly extraction and validation ensures knowledge stays current and accurate. ### Lesson 4: Multi-Agent Knowledge Parity When multiple tools and team members work on the same codebase, knowledge silos are expensive. One engineer discovers a configuration requirement; another spends hours rediscovering the same thing independently. The mandate: Corrections discovered anywhere must propagate everywhere. The repository is the single source of truth. Version control is the sync mechanism. ### Lesson 5: Independent Cross-Review Three independent reviewers examine every plan and every deliverable. This is not optional — it is enforced at the tooling level. Each reviewer catches different failure modes: implementation bugs, architectural drift, and scope creep. ## How the Five Lessons Reinforce Each Other These are not independent practices. They form a system where each element strengthens the others: Enforcement ensures that cross-review actually happens Cross-review generates learnings captured by the compound loop The compound loop improves knowledge used across the organization via parity Knowledge parity enables workers to operate with full context Workers execute work that enforcement gates for quality Remove any one element, and the others degrade. Without enforcement, reviews get skipped. Without reviews, quality drops and learnings are shallow. Without the learning loop, institutional knowledge stagnates. ## What This Means for Your Projects ### For Engineering Managers This methodology means that ACE Engineering projects get faster over time, not slower. The first mooring analysis we run for your asset benefits from every mooring analysis we have ever completed. Known pitfalls are avoided automatically. Best practices are embedded in the workflow, not in a dusty procedures manual. ### For Quality Assurance Teams Every quality gate is technically enforced, not aspirationally documented. Compliance does not depend on individual discipline — it is built into the delivery pipeline. When we say "every deliverable is independently reviewed," we mean the system will not allow delivery without review evidence. ### For Technical Directors The orchestrator-worker pattern means complex multi-discipline analyses run in parallel without context degradation. A riser analysis, a mooring assessment, and a structural evaluation can proceed simultaneously, each with focused attention, coordinated by a master plan that maintains coherence across all workstreams. ## Measurable Outcomes Metric Value Reusable knowledge entries in production 690+ Engineering categories covered 48 Automated enforcement gates active 28 Quality governance checkpoints 7 Cross-review compliance (with enforcement) Near 100% Knowledge propagation time Next session start ## Our Approach to Every Project Compound engineering is not about having the best tools. It is about building a system where every project — regardless of size or complexity — leaves the engineering practice better than it found it. The five lessons are the operational foundation that makes this work. They were not designed in a whiteboard session; they emerged from doing real engineering work for over a year and continuously asking: "How do we make sure this never happens again?" Want to see how compound engineering applies to your project? Contact ACE Engineering to discuss how our systematic methodology delivers reliable, improving results for offshore and structural engineering challenges. ## Apply this methodology to your project We use these delivery patterns to reduce rework, improve traceability, and keep complex engineering programs moving. Talk to ACE EngineeringDownload Capability Summary (PDF, 1 page) ## 3-Agent Cross-Review - AceEngineer URL: https://www.aceengineer.com/methodology/cross-review/ Description: How three independent reviewers catch engineering failures that self-review structurally cannot. # 3-Agent Cross-Review How independent reviewers catch failures that self-review structurally cannot. ACE Engineering MethodologyQuality assurance • Adversarial reviewClient-facing publication The methodology pages describe AI agents working on planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. ## On this page The Problem: Single-Reviewer Blindness Three Independent Reviewers The Two-Stage Review Model Why Different Reviewers Catch Different Things How the Workflow Is Enforced Review Verdicts What Cross-Review Actually Catches Key Takeaway ## 3-Agent Cross-Review: Independent Eyes on Every Deliverable Running in production since early 2025 — before "adversarial review" became standard terminology in the AI engineering community. ## The Problem: Single-Reviewer Blindness An engineer reviewing their own work is structurally incapable of catching certain classes of error. This is not a quality issue with any individual reviewer; it is a property of the review context being contaminated by the authoring context. When the same person who built the analysis turns around to review it: The reasoning that justified each decision is still in their head, so the decisions look obviously correct Assumptions made during authoring feel like established facts Missing requirements are invisible because they were never considered in the first place Edge cases the author did not think of remain unconsidered This is the engineering equivalent of a developer reviewing their own code. They might catch typos. They almost never catch architectural misalignment. ### The Evidence Before we enforced cross-review on our own work, the failure pattern was consistent: plans shipped with unstated assumptions; implementations diverged from plans because the same person rationalized the drift; the few self-reviews that did happen caught surface issues but missed structural problems. Independent review compliance was running at 4 percent. With cross-review enforced, that number is now consistently above 80 percent — and the issues caught are qualitatively different. ## Three Independent Reviewers For every plan and every deliverable, we engage three independent reviewers. Each operates in a fresh context, without access to the authoring session's reasoning or rationalizations. Reviewer Role Primary Focus Review Strengths Orchestrator-reviewer Task framing and plan coherence Scope verification, cross-file consistency, convention alignment Implementation-reviewer Code and analysis correctness Off-by-one errors, test coverage, file-path verification, diff analysis Adversarial reviewer Architecture and completeness Missing edge cases, requirement gaps, large-context structural review The key word is independent. A reviewer operating in the same session as the author is not independent — they share the same context contamination. Cross-review works because each reviewer starts with only the artifact and the specification, not the authoring session's history of dead ends, retries, and rationalizations. ## The Two-Stage Review Model Cross-review happens at two distinct stages, not just one. Skipping either stage produces predictable failure modes. ### Stage 1: Plan Review Author creates implementation plan | v Implementation-reviewer reviews plan --> finds execution concerns | "This approach won't handle concurrent access" v Adversarial reviewer reviews plan --> finds architectural concerns | "This duplicates logic already in the existing toolchain" v Author updates plan based on both reviews | v Client / project lead approves the updated plan ### Stage 2: Artifact Review Implementation-reviewer's plan is executed | v Orchestrator-reviewer checks against plan | "The plan called for 7 checkpoints; only 5 are present" v Adversarial reviewer checks architecture | "This component should follow the same protocol as its peer" v Issues resolved --> deliverable ships Both stages are mandatory. Plans receive adversarial review before approval. Code, analysis output, and deliverable artifacts receive adversarial review before completion. There is no path to ship that bypasses either stage. ## Why Different Reviewers Catch Different Things Different review perspectives have characteristic blind spots and strengths. These are not random — they are consistent enough to be exploited deliberately. Failure Mode Best Caught By Why Plan-implementation drift Orchestrator-reviewer Maintains the plan context, can cross-reference Off-by-one errors in code or formulas Implementation-reviewer Strong at line-level analysis Missing edge cases in plan Adversarial reviewer Large context window, good at "what about..." questions Scope creep Any independent reviewer Fresh context = no investment in existing approach Incorrect file or reference paths Implementation-reviewer Good at verifying paths exist where claimed Architectural inconsistency Adversarial reviewer Holds the entire repo structure in context Unstated assumptions Any independent reviewer Author's assumptions are not in the reviewer's context The probability that all three reviewers miss the same issue is far lower than the probability that any single one misses it. That is the structural reason cross-review works. ## How the Workflow Is Enforced Cross-review is not voluntary. It is enforced at the strongest level we operate — technical gates that block operations rather than warnings that suggest review. Gate Trigger What It Enforces Plan-execution gate Implementation start Blocks execution without plan review PR creation gate Pull request opened Blocks if no review evidence is present Pre-push review gate Push to shared branches Blocks feature commits lacking review Ship gate Final delivery Blocks without test pairing and review The gates check four evidence sources: review results files, recorded reviews in the planning archive, formal review reports, and review keywords in commit messages. If any source has evidence for the change in question, the gate passes. If none do, the gate blocks — regardless of who initiated the operation or what deadline pressure exists. ## Review Verdicts Reviews resolve to one of three explicit verdicts: Verdict Meaning Action APPROVE No issues found Proceed to ship MINOR Small issues, non-blocking Fix recommended; not required MAJOR Significant issues found Must fix before shipping MAJOR findings require resolution and re-review. They do not count as passing evidence on their own — only resolution + re-review closes the gate. ## What Cross-Review Actually Catches Real examples from production engagements: Configuration mismatches between policy and implementation. A review caught a threshold configured at one value in policy but a different value in the enforcing hook — a silent drift that would have made our own configuration misleading. Default-mode misalignment. A reviewer noticed that the "advisory" mode was the default for a strict-by-stated-intent enforcement script. The contradiction was caught and corrected before it shipped to clients. Concurrency failure modes that only appear at scale. Reviewers identified file-locking races, file-handle issues, and policy hooks blocking final writes — failure modes that would only have surfaced under client load, where they would have been far costlier. None of these were caught by self-review. All were caught by an independent reviewer with no investment in the original approach. ## Key Takeaway Cross-review works because it exploits a structural property: independent reviewers have non-overlapping blind spots. A deliverable reviewed through three different lenses, with three different sets of assumptions, in three fresh contexts, has been examined more thoroughly than any single review can achieve. The enforcement is what makes it real. Without technical gates, review compliance was 4 percent. With gates, every shippable artifact is examined. The combination of independent reviewers and automatic enforcement creates a quality floor that no single reviewer can produce alone. Want engineering deliverables with three layers of independent review built into the workflow? Contact ACE Engineering to learn how this pattern applies to your project governance. ## Three reviewers. Every deliverable. No exceptions. Cross-review is not a checklist. It is enforced at every shipping gate so that the work you receive has already been adversarially examined. Talk to ACE EngineeringDownload Capability Summary (PDF, 1 page) ## Enforcement Over Instruction - AceEngineer URL: https://www.aceengineer.com/methodology/enforcement/ Description: Why technically enforced quality gates outperform written process alone. # Enforcement Over Instruction Why technically enforced quality gates outperform written process alone. ACE Engineering MethodologyOffshore • Structural • Pipeline DeliveryClient-facing publication The methodology pages describe AI agents working on planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. ## On this page The Core Insight Why Instructions Fail The Evidence The Enforcement Gradient What We Enforce and How Mandatory Gates (Level 3) Automated Checks (Level 2) The Review Gate in Practice Gradual Rollout: How We Got Here Emergency Overrides The Architectural Principle Key Takeaway ## Enforcement Over Instruction: Why We Automate Quality Gates Text-based rules degrade over time. Technical enforcement does not. Based on measured compliance data from production engineering operations. ## The Core Insight Telling an engineer to follow a review process is like telling a developer to write tests. Sometimes it happens. Often it does not. You do not rely on good intentions for test coverage — you have CI gates. The same principle applies to every quality-critical step in an engineering workflow. The difference between a quality aspiration and a quality guarantee is whether the system allows work to proceed without meeting the standard. ## Why Instructions Fail Written rules have a half-life. They work well when first introduced, then compliance decays as workload pressure mounts and the instruction fades in relative importance: Each successful shortcut reinforces the pattern The team learns that rules are suggestions, not requirements Task urgency ("just get the deliverable out") dominates process discipline ("do it right") Longer projects amplify the effect — standards established in week one are forgotten by week twelve This is not a failure of any individual. It is a structural property of any system where the executor has discretion about whether to follow process. ### The Evidence The moment that crystallized this lesson was a compliance audit of our own workflow: Review compliance: 4% 42 deliverables produced 1 independently reviewed 22 unreviewed items in a single 24-hour period This happened with written instructions present at every level: Documented review requirements in project standards Explicit review procedures in team conventions Detailed review checklists loaded into every work session Direct reminders in project briefs All four forms of written instruction were present. Compliance was 4%. ## The Enforcement Gradient The solution is not better instructions. It is technical enforcement that cannot be bypassed by choosing to skip a step. Level Mechanism Reliability When to use 0 — Written guidance Procedures manual, project brief Lowest — only effective if actively followed Broad guidance, preferences 1 — Checklist Stage-specific checklist, loaded at task start Medium — guaranteed to appear, not guaranteed to be completed Stage-specific requirements 2 — Automated check Script that verifies compliance High — auditable, testable, consistent Binary checks: did/didn't 3 — Mandatory gate Automated block that prevents progress without compliance Strongest — fires automatically, cannot be bypassed Must-never-miss requirements The migration path: When a written rule can be expressed as a pass/fail check, automate it. When it must fire on every deliverable, promote it to a mandatory gate. ## What We Enforce and How ### Mandatory Gates (Level 3) These fire automatically on every operation. Work cannot proceed without meeting the requirement. Gate What it enforces Plan approval Implementation cannot begin without an approved plan Cross-review Deliverables cannot be finalized without independent review evidence Session governance Work sessions pause at defined checkpoints for human verification Configuration protection Critical configuration files cannot be accidentally modified ### Automated Checks (Level 2) These run at defined points in the workflow and produce clear pass/fail results: Check Purpose Plan approval verification Pre-delivery check for approved plan markers Review evidence verification Pre-delivery check for review artifacts Cross-review completeness Delivery check for review documentation from multiple reviewers Test pairing Check that engineering changes have paired validation Compliance dashboard Generates daily compliance metrics from delivery history ## The Review Gate in Practice Our review enforcement demonstrates the full lifecycle: Classify work items: Each deliverable is analyzed to determine if it requires review. Routine items (documentation updates, formatting) are excluded. Substantive items (new analysis, design changes, methodology updates) require review. Check evidence: Multiple evidence sources are checked — review reports, review documentation in project records, and reviewer sign-off in delivery notes. Verdict: If all substantive items have review evidence, work proceeds. If any lack evidence, the gate blocks delivery with a clear message about what is missing. Logging: Every gate execution is logged with timestamp, verdict, and details. Every override is logged separately with justification. ## Gradual Rollout: How We Got Here Going strict on day one breaks workflows. The proven rollout sequence: Phase Change Measured Result Phase 1 Review requirements documented (Level 0) Compliance: 4% Phase 2 Automated review gate added (Level 2+3) Delivery gated on review evidence Phase 3 Plan approval gate added (Level 3) Implementation without approved plan blocked Phase 4 Review gate set to strict by default (Level 3) Delivery without review blocked Phase 5 CI pipeline enforcement (planned) Automated rejection of unreviewed deliverables Each phase was implemented incrementally with testing. The 4% compliance rate from Phase 1 motivated the entire enforcement investment. ## Emergency Overrides Every enforcement gate has a documented override mechanism. Overrides exist because real engineering has genuine emergencies. But every override is: Logged with timestamp, user, and justification Auditable in daily compliance reports Visible as an exception in metrics dashboards Frequent overrides indicate a gate that needs adjustment, not removal. If a gate is being bypassed regularly, either the gate is miscalibrated or the team needs better tooling to meet the standard. ## The Architectural Principle The enforcement gradient is not specific to AI-augmented workflows. It applies to any system where the executor has discretion about whether to follow process: Human engineering teams: Code review requirements, branch protection, required sign-offs Automated analysis pipelines: Health checks, validation gates, convergence criteria Quality management systems: Hold points, witness points, inspection gates The common principle: if compliance is optional, it will degrade over time. Make the desired behavior the path of least resistance, and the undesired behavior require explicit override. ## Key Takeaway Text-based rules have a half-life. They work when introduced, then compliance decays as pressure mounts. Technical enforcement does not decay. An automated gate that checks for review evidence has the same compliance rate on day 1 as on day 100. The enforcement gradient (written guidance to checklist to automated check to mandatory gate) is the migration path from aspirational rules to reliable guarantees. Every quality requirement that matters should be on a trajectory toward mandatory enforcement. If it is still a written guideline after a month, either it does not matter or the team has not prioritized it. See our enforcement-backed review process in action. Contact ACE Engineering to learn how our technically enforced quality gates deliver consistently reviewed, validated engineering deliverables. ## Apply this methodology to your project We use these delivery patterns to reduce rework, improve traceability, and keep complex engineering programs moving. Talk to ACE EngineeringDownload Capability Summary (PDF, 1 page) ## Multi-Agent Knowledge Parity - AceEngineer URL: https://www.aceengineer.com/methodology/multi-agent-parity/ Description: How shared knowledge eliminates redundant discovery across tools and teams. # Multi-Agent Knowledge Parity How shared knowledge eliminates redundant discovery across tools and teams. ACE Engineering MethodologyOffshore • Structural • Pipeline DeliveryClient-facing publication The methodology pages describe AI agents working on planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. ## On this page The Problem: Knowledge Silos Why This Is Expensive The Anti-Patterns The Solution: Repository as Single Source of Truth How It Works How Each Tool Accesses Shared Knowledge The Knowledge Sync Model The Sync Flow Cross-Machine Parity Why Skills Over Documentation Knowledge Parity in Practice Example: Analysis Tool Unit Convention ## Multi-Agent Knowledge Parity: Eliminating Redundant Discovery How we ensure every tool and team member operates with full organizational knowledge. Based on running multiple AI-augmented engineering workflows in production simultaneously. ## The Problem: Knowledge Silos When multiple engineers, tools, or workflows operate on the same project, each one discovers things independently. One workflow learns that a particular analysis tool returns frequencies in an unexpected unit convention. Another workflow encounters the same confusion and spends time resolving it from scratch. A third has never seen the issue and will waste time on it next week. ### Why This Is Expensive Workflow A spends 20 minutes resolving a configuration issue --> solved Workflow B encounters the same issue next session --> solved again Workflow C has never seen it --> will spend 20 minutes next time Workflow D resolved it a month ago but the fix is in local notes --> invisible to others With multiple engineering tools and team members operating simultaneously, redundant discovery is a direct waste of project budget and delivery time. The principle is straightforward: corrections discovered anywhere must propagate everywhere. Zero waste. ### The Anti-Patterns Anti-pattern What happens Cost Knowledge in session notes only Lost when the session ends Rediscovery every session Fixes documented in one tool only Only that tool benefits Other workflows rediscover Corrections communicated verbally Stays in conversation Every new session starts uninformed Local workarounds not shared One team member knows, others do not Inconsistent quality across deliverables ## The Solution: Repository as Single Source of Truth All engineering knowledge lives in version-controlled files. Not in individual memory. Not in a proprietary database. Not in email threads. In structured, versioned files that every tool and team member reads at the start of every work session. ### How It Works Shared Knowledge Repository ├── Skills Library (690+ entries, 48 categories) │ ├── Engineering (analysis tools, modeling, design criteria) │ ├── Software Development (automation, testing, debugging) │ ├── Coordination (project planning, routing, dispatch) │ └── ... (48 total categories) ├── Cross-Team Memory │ ├── Machine/environment conventions │ ├── Team profile and workflow rules │ ├── Engineering lessons and tool-specific knowledge │ └── Topic-specific reference files ├── Standards and Governance │ └── Review policies, enforcement configuration └── Multi-Agent Conventions └── Tool roles, routing, synchronization rules ### How Each Tool Accesses Shared Knowledge Every tool in the engineering workflow reads from the same knowledge base: Tool Access Method Primary AI assistant Direct file access to the skills library Secondary AI tools Adapter configurations that reference the shared library Automation agent External directory configuration pointing to the shared library Human team members Standard file browsing and search The critical design decision: all knowledge goes to the shared repository, not to tool-specific storage. When a new engineering lesson is learned, it is committed to the repository. Every tool reads from the repository. Every `git pull` on any machine synchronizes the entire knowledge base. ## The Knowledge Sync Model Knowledge travels with the repository through version control. No proprietary sync protocol. No cloud service dependency. Standard `git pull` on any machine gets the latest everything. ### The Sync Flow 1. Engineering session discovers a tool behavior or pitfall | 2. Knowledge is captured in a structured file (skill entry or knowledge note) | 3. File is committed and pushed to version control | 4. Any machine pulling the latest version has the updated knowledge | 5. Every tool reading from the repository has the correction | 6. No future session encounters the same issue uninformed ### Cross-Machine Parity The system operates across multiple machines with different operating systems and tool configurations: Machine Key Differences Primary workstation (Linux) Full tool suite, all automation agents Secondary workstation (Windows) Subset of tools, different runtime conventions Both machines achieve knowledge parity through the repository. The Linux machine may have additional automation agents that the Windows machine lacks, but the knowledge base is identical. Tool-specific differences (like which Python command to use) are documented in the shared knowledge base so every tool respects the local convention. ## Why Skills Over Documentation Skills are the primary knowledge carrier in our methodology. Not general documentation, not meeting notes, not tribal knowledge. Structured skill entries. Knowledge Carrier Persistence Discoverability Reach Actionability Session notes Session only Low 1 person Medium Individual memory Cross-session for that person Medium 1 person Medium Engineering lessons file Permanent (versioned) High (loaded at start) Everyone Medium Skill entry Permanent (versioned) Highest (searchable by name/tag) Everyone Highest General documentation Permanent (versioned) Low (must be searched) Everyone Low Skill entries win because they are: Structured: Consistent format with name, description, version, tags, and related entries Discoverable: Searchable by category, tag, or keyword Actionable: Include step-by-step procedures, not just facts Versionable: History shows how understanding evolved over time Testable: Can be validated to confirm they produce correct guidance ## Knowledge Parity in Practice ### Example: Analysis Tool Unit Convention An engineering session discovers that a wave analysis tool returns frequencies in Hz (descending order), not in rad/s (ascending order) as documentation suggests Lesson is captured in the engineering knowledge base and in the relevant tool skill entry Committed to version control Every future session involving that tool starts with the correct understanding Zero engineering sessions will make this unit conversion error again ### Example: Runtime Environment Convention A user corrects one tool: "Always use the isolated Python environment, not the system Python" The correction is committed to the shared conventions file Every tool on every machine reads the updated convention at next session start Time from correction to universal adoption: the next `git pull` (seconds to hours) ### Example: Recurring Configuration Problem A tool configuration keeps reverting to an incorrect default (occurred 3 times before capture) The correct configuration and the reason for the reversion are documented in the knowledge base After capture: zero recurrences Every tool and team member can see the known issue and its resolution ## The Nightly Parity Pipeline Three automated processes maintain knowledge parity: ### 1. Comprehensive Learning Pipeline Runs nightly. Pulls latest state, syncs knowledge across tools, validates existing entries, commits updates back to version control. ### 2. Memory Bridge Syncs tool-specific learnings into the shared knowledge base. Reads from tool-specific storage, extracts facts, deduplicates, and injects into the shared repository. ### 3. Cross-Tool Knowledge Sync Deeper cross-pollination. Categorizes knowledge entries (environment facts, conventions, project knowledge, preferences), produces structured indices, and merges into a unified reference. ## What Breaks Parity (and How to Fix It) Breakage Symptom Fix Knowledge captured in session only Next session does not know what this one learned Write to shared knowledge file, commit to version control Knowledge in tool-specific storage only Only one tool benefits Move to shared repository Tool memories diverge One tool "knows" things others do not Run the knowledge bridge sync Stale repository on secondary machine Secondary machine uses outdated knowledge Pull latest before starting work Sync pipeline fails silently Knowledge not propagated Monitor pipeline logs, check timestamps ## The Parity Checklist For teams adopting this methodology: [ ] All tools read from a shared knowledge directory [ ] No tool stores critical knowledge outside the shared repository [ ] New knowledge goes to the shared repository immediately [ ] Corrections trigger file updates, not just verbal acknowledgment [ ] Knowledge sync runs on schedule (nightly or more frequent) [ ] Multi-tool conventions document is current [ ] Cross-tool knowledge index is being generated and updated ## Key Takeaway Multi-agent knowledge parity is not about making all tools identical. It is about ensuring that no tool or team member operates with less context than any other. When one workflow discovers a critical engineering fact, every tool and every team member should know it from the next session forward. The mechanism is deliberately simple: version-controlled files in a shared directory structure. No proprietary sync protocol, no tool-specific knowledge databases, no cloud sync service. Git is the sync mechanism. The repository is the shared brain. The result for our clients: consistent engineering quality regardless of which tool or team member touches their project. No knowledge falls through the cracks. No lesson learned is forgotten. No pitfall is encountered twice. See how our multi-tool knowledge parity delivers consistent engineering quality. Contact ACE Engineering to discuss how our methodology eliminates redundant discovery and ensures every analysis benefits from our full institutional knowledge. ## Apply this methodology to your project We use these delivery patterns to reduce rework, improve traceability, and keep complex engineering programs moving. Talk to ACE EngineeringDownload Capability Summary (PDF, 1 page) ## How we run AI agents on engineering work | AceEngineer URL: https://www.aceengineer.com/methodology/orchestrator-worker/ Description: The methodology pages describe planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. # Orchestrator-Worker Delivery Model Why separating planning from execution improves complex engineering delivery. ACE Engineering MethodologyOffshore • Structural • Pipeline DeliveryClient-facing publication The methodology pages describe AI agents working on planning, focused tasks and independent review. Contact us to discuss a separately agreed scope. ## On this page The Problem: Context Overload Why Self-Review Fails The Solution: Orchestrator + Workers Why This Works How We Apply This in Practice Multi-Discipline Project Delivery Provider and Tool Allocation Contention Avoidance Pattern Variants Variant 1: Delegated Subtasks Variant 2: Isolated Workspaces Variant 3: Staged Cascade ## Orchestrator-Worker: Separating Planning from Execution Why context isolation is a prerequisite for reliable complex engineering. Based on 12+ months of production multi-discipline project delivery. ## The Problem: Context Overload Complex engineering projects degrade predictably when a single team member or workflow tries to plan, implement, review, and deliver in one continuous session. As work progresses, the accumulated detail overwhelms the original plan: Single-Session Workflow (4+ hours) Hour 1: Plans the analysis (reads specifications, creates approach) --> Plan is clear, context is fresh Hour 2: Begins implementation (modeling, debugging, reading references) --> Plan details start to fade under operational detail Hour 3: Continues work (error resolution, refinement, iteration) --> Working from current state, not from original specification Hour 4: Reviews own work (checks what was built, not what was planned) --> Cannot recall original requirements clearly Result: Drift between specification and deliverable, self-review is ineffective This pattern is not about individual capability. It is a property of bounded attention applied over extended periods. The more complex the project, the faster context overload sets in. ### Why Self-Review Fails An engineer reviewing their own analysis is like a developer reviewing their own code. They built it, so it looks correct. The reasoning that justified each decision is still fresh. Blind spots are invisible precisely because they are the analyst's blind spots. Independent review catches what self-review cannot — not because the reviewer is smarter, but because they approach the work without the accumulated assumptions of the person who created it. ## The Solution: Orchestrator + Workers Orchestrator: Maintains the master plan, delegates focused tasks, verifies results against specification. Workers: Execute focused tasks with fresh context, return results without accumulated baggage. Orchestrator ├── Reads requirements, creates detailed plan ├── Designs focused task briefs (each self-contained) ├── Assigns Worker 1: Mooring analysis with relevant specs only ├── Assigns Worker 2: Riser assessment with relevant specs only ├── Collects results from both workers ├── Verifies each result against the original specification └── Delivers or sends back with specific feedback Worker 1 (fresh context) ├── Receives: Analysis scope + relevant specifications ├── Executes only what the brief specifies ├── Validates results against acceptance criteria └── Returns: Analysis results + summary of findings Worker 2 (fresh context) ├── Receives: Assessment scope + relevant specifications ├── Executes only what the brief specifies ├── Validates results against acceptance criteria └── Returns: Assessment results + summary of findings ### Why This Works Challenge Single Session Orchestrator-Worker Context overload Grows with project duration Each worker starts fresh Plan drift Specification forgotten as details accumulate Orchestrator maintains specification throughout Parallel work Sequential only Workers proceed in parallel Self-review bias Same person reviews their own work Independent review by different team members Failure recovery Must reconstruct lost context Restart worker with the same brief Session duration 4+ hours with degrading quality 1-2 hours per worker with sustained quality ## How We Apply This in Practice ### Multi-Discipline Project Delivery For projects involving multiple engineering disciplines — mooring analysis, riser assessment, structural evaluation — the orchestrator-worker pattern is essential. The orchestrator: Triages the project scope into independent analysis packages Designs self-contained briefs for each discipline, with full context embedded (no cross-references that require chasing) Maps deliverable boundaries to ensure no two workers modify the same output Launches workers in parallel across disciplines Reviews results against the original project specification, not against what was convenient to produce ### Provider and Tool Allocation Different analysis tools and team members have different strengths. Our allocation pattern emerged from hundreds of project deliveries: Workstream Best Suited For High-context synthesis Architecture review, cross-discipline coordination, specification development Bounded analysis Focused numerical analysis with defined inputs and outputs Documentation and audit Staleness scanning, report generation, compliance documentation Pipeline development Automation scripts, data integration, toolchain work This allocation is not arbitrary. It emerged from observing which approaches succeed at which tasks across extensive production experience. ### Contention Avoidance When multiple workstreams operate on the same project simultaneously, coordination failures are the primary risk. Our contention avoidance rules: No two workers modify the same deliverable. No exceptions. No two workers operate in the same output directory when possible. Negative boundaries: Each worker brief includes explicit lists of deliverables they must NOT produce (owned by other workers). Synchronization checkpoints before integration points. Staggered delivery if output overlap is unavoidable. ## Pattern Variants ### Variant 1: Delegated Subtasks For work that can be subdivided within a single session: Lead engineer (orchestrator role) ├── Subtask: "Complete the metocean data analysis" │ Context: Project spec section 2.1 + relevant data files ├── Subtask: "Run the fatigue assessment for riser section 3" │ Context: Project spec section 2.2 + structural model └── Lead verifies each subtask result against master specification ### Variant 2: Isolated Workspaces For work that cannot share a single project environment: Each worker gets an independent workspace - Complete isolation from other workstreams - Orchestrator reviews outputs from each workspace - Integration happens at defined merge points ### Variant 3: Staged Cascade For projects with mandatory approval gates: Planning workers (stage 1): Each produces one analysis plan or assessment brief. No implementation. Approval gate: Plans reviewed and approved before execution begins. Execution workers (stage 2): Convert approved plans into deliverables. Review workers (stage 3): Independent review of each deliverable. This cascade respects hard-stop workflow gates while maximizing parallel throughput. ## Common Pitfalls Workers creating their own plans. This defeats the purpose. Workers should receive plans, not create them. Plan-approval enforcement prevents this. Orchestrator implementing directly. Context overload returns immediately. If the orchestrator starts doing analysis work, they stop being an orchestrator. No verification step. The orchestrator must verify worker output against the specification, not trust it. Workers optimize for task completion, not specification adherence. Stale context in worker briefs. Workers must get the current specification version. If the spec was updated after the brief was written, the worker produces the wrong deliverable. Missing handoff documentation. If a worker cannot complete their task, the next person must pick up from where work stopped. Handoffs require explicit status documentation. ## Performance Comparison Metric Single Session Orchestrator-Worker Time to complete complex project 4+ hours 1-2 hours per worker Attention span utilization Degrades linearly Flat per worker Plan drift frequency Common after hour 2 Rare (orchestrator maintains plan) Review effectiveness Low (self-review) High (independent review) Parallel throughput 1x 3-5x (limited by available workers) ## Key Takeaway Context isolation is not a nice-to-have. It is a prerequisite for reliable complex engineering. The orchestrator-worker pattern works because it converts one hard problem — maintaining coherence over a 4+ hour project session — into multiple easier problems: focused workers executing well-defined tasks in 30-90 minutes each. Every complex project we deliver uses some variant of this pattern. The result for our clients: faster delivery, higher quality, and better adherence to original project specifications. The orchestrator always knows the plan. The workers always have fresh attention. The deliverable always gets independent review. Our AI-augmented orchestrator-worker workflow delivers better results for complex engineering projects. Contact ACE Engineering to learn how this methodology applies to your offshore, structural, or pipeline engineering challenges. ## Apply this methodology to your project We use these delivery patterns to reduce rework, improve traceability, and keep complex engineering programs moving. Talk to ACE EngineeringDownload Capability Summary (PDF, 1 page) ## The Deckhand Chronicles | AceEngineer newsletter URL: https://www.aceengineer.com/newsletter/ Description: Short issues on engineering analysis, open energy data, AI automation and agentic workflows, each linked to the public reports behind it. # The Deckhand Chronicles Short issues on engineering analysis, open energy data, AI automation and agentic workflows, each linked to the public reports behind it. ## Issues ### Tank sloshing CFD study with open source software OpenFOAM (Deckhand newsletter, issue 1) 12 November 2026 · Issue 1 · Energy Street · Version 1.2 ### Engineering evolution with AI (Deckhand newsletter, issue 2, Main Street) 4 November 2026 · Issue 2 · Main Street ### Sacrificial anodes needed for six offshore structures on each edition of DNV-RP-B401 and DNV-RP-F103 (Deckhand newsletter, issue 2) 4 November 2026 · Issue 2 · Energy Street ### Gulf of Mexico well permits by rig type: a public US data file (Deckhand newsletter, issue 2) 4 November 2026 · Issue 2 · Public data ### Jack-up site-specific analysis (Deckhand newsletter, issue 2) 4 November 2026 · Issue 2 · Energy Street ### The Deckhand Chronicles: Energy Street, Issue 1 27 October 2026 · Deckhand: Make Engineering Enjoyable Again RSS feed ## Subscribe or stop Subscribe to Energy Street. Or write to support@aceengineer.com. Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## The Deckhand Chronicles: Energy Street, Issue 1 URL: https://www.aceengineer.com/newsletter/issue-001-energy-street/ Description: A sloshing CFD check within about 0.30 % of linear theory, and a motion-forecast demo on synthetic data. VOL. I · NO. 1 · Energy Street edition # The Deckhand Chronicles October 27, 2026 · Launch issue Energy Street is AceEngineer's edition for offshore and energy engineering. Deckhand is our AI-assisted way of working. This issue: one engineering calculation checked against theory and a published benchmark with a working demo. To get each issue by e-mail, write to support@aceengineer.com with the subject "Subscribe Energy Street". To stop, use the subject "Stop". Tank sloshing Schematic of a two-dimensional rectangular tank in section, partly filled with water and rolled so that its top leans to the left, away from the Deckhand logo. A curved arrow shows the roll direction. The free surface is drawn in the first sloshing mode, higher at the low wall and lower at the high wall, with small arrows for the water motion and a dashed true-horizontal line for the still-water level. A straight, taut rope runs from a lug on the tank wall to the Deckhand bollard. Text: 2D tank, partial fill; OpenFOAM; first-mode frequency within about 0.30 % of theory, small amplitude. Schematic, not to scale. Tank sloshing 2D tank, partial fill|OpenFOAM still-water level First-mode frequency within about 0.30 % of theory, small amplitude Schematic, not to scale. Illustration: the rope is a metaphor for Deckhand supporting the engineer, not a model of tank damping. ## Tank sloshing CFD study with open source software OpenFOAM The sloshing computational fluid dynamics (CFD) study reproduced the tank's small-amplitude first-mode frequency within about 0.30 % of linear theory across the tested fill levels. Sloshing matters in tanks on floating vessels. Near resonance, the liquid runs up the tank walls and strikes them. A partly filled tank tuned near a vessel's roll period can also act as an anti-roll damper. Read the study. The analysis results for the two-dimensional tank are compared to the available public literature to sense-check/benchmark the results. Parametric analysis for other tank dimensions, fill levels and forcing can be constructed and rerun by extending the same scripts. This study is extended to assess a U-tube style anti-roll arrangement: two connected tanks with invented geometry. This study is an analytical screening model calibrated on CFD assessment. The calibration uses 35 archived computational fluid dynamics (CFD) cases, published as aggregate results only, on a different connected-tank geometry, so its transfer to the invented geometry is an assumption. Based on the benchmarked single tank analysis, analysis is extended to build the connected model. Read the dual-tank study A separate screening estimate, with a public U-tube reference tank, gives the roll of a generic hull. The result depends mainly on hull damping and on how large the tank's water moment is compared with the hull's own roll stiffness. That ratio is called alpha: the tank's quasi-static free-surface moment stiffness divided by the hull's roll restoring. At an 18 s hull roll period, alpha 0.05 and conduit area 6.8 m², peak roll reduction is 46.1 % at 2 % hull damping. At 5 % hull damping it is 23.3 %. Both cases lie below the 20 s band of the tank fit, and no real-vessel test backs them. Read the roll estimate A working demo of vessel-motion forecasting on a simulated sea state is given below. This demo requires live motion-sensor input to provide useful go/no-go decisions. Demo: short-horizon motion forecast with an illustrative go / caution / no-go call ## One place to work We now use AI assistants for many tasks: in a chat window or an app, on a phone, and on personal and work computers. AI assistants use language models that do not always give the same answer. We are running into the familiar territory of "the answer can change from one run to the next, and with the wording of the question." When we dealt with IT and programmers, many a times, we faced a related frustration: "oh.. but it works on my machine." This answer was so familiar for administrative tasks such as opening a Microsoft word file or crash). Equally, the same experience when we ran a script not able to run let alone getting same result. We now meet a similar problem in everyday AI use: one person gets a result that another cannot repeat. One of the solutions is to keep each job in one folder, with its files, its tools, its prompts and its record of changes. Let your AI assistant work through this created set environment. The AI assistants we use keep a record of each session. To check a result, or run it again, you need its prompt, its inputs and that record. So the home for this data matters. The article shows how this grows from one engineer to a team and then to the company. In our experience, it takes a few (> 10-20) reasonably sized sessions to realize these benefits; we have not measured this. Treating AI assistants as loyal team members who need help will get us a long way. Similar to training your employee team, training this single work storage place will make immense difference. Read the full article Note: the dual-tank results are screening estimates on invented geometry, not design values; the statements on AI sessions are our experience, not measurements. ## About AceEngineer AceEngineer provides engineering analysis and calculation workflows for an owner, operator, engineering firms or contractor. We plan later issues on engineering workflows, their automation and the use of AI assistants for everyday engineering. The newsletter takes its name from Deckhand. ## Future issues Future issues are planned on cathodic protection and vessel diffraction analysis; asset integrity (fitness-for-purpose), riser and installation topics may follow. ## The date book ADIPEC: November 2–5, 2026, Abu Dhabi. OTC 2027: Monday–Wednesday, May 3–5, 2027, Houston. Footnote: Dates checked October 22, 2026. Vamsee Achanta, P.E. ## Tank sloshing CFD study with open source software OpenFOAM (Deckhand newsletter, issue 1) URL: https://www.aceengineer.com/newsletter/issue-001-tank-sloshing/ Description: The closed-form formula for a tank's first sloshing frequency holds at small roll: our two-dimensional OpenFOAM model matches it within 0.30 % at four fill levels. At 8° roll, the resonance at 30 % and 70 % fill sits about 11 to 13 % or more below the formula. The Deckhand newsletter · Issue 1 · Energy Street # Tank sloshing CFD study with open source software OpenFOAM The Deckhand Chronicles is AceEngineer's newsletter. We help build AI into everyday engineering work. Energy Street · Tank sloshing. Energy Street covers offshore engineering. The closed-form formula for a tank's first sloshing frequency holds at small roll: our two-dimensional OpenFOAM model matches it within 0.30 % at four fill levels. At 8° roll, the resonance at 30 % and 70 % fill sits about 11 to 13 % or more below the formula. An anti-roll tank tuned from the formula alone needs a check at the vessel's own roll angle and roll axis. Version 1.2, prepared 12 Nov 2026, from issue 1 of 27 Oct 2026. Full study: https://vamseeachanta.github.io/digitalmodel/cfd/sloshing-cfd-study.html In this article: The formula and the CFD agree at small roll The resonance moves with roll angle and roll axis Tank damping has an optimum Run time on one workstation ## The formula and the CFD agree at small roll Sloshing matters in tanks on floating vessels. Near resonance, the liquid runs up the tank walls and strikes them. A partly filled tank tuned near a vessel's roll period can also act as an anti-roll damper. Both uses start from the tank's first sloshing frequency, the frequency at which the liquid swings most easily from wall to wall. This article gives that frequency from a closed-form formula and from open-source computational fluid dynamics (CFD). It shows how far the resonance moves at larger roll angles, and it names two checks, the roll angle and the roll axis, to apply to a sloshing study of your own tanks. The study ran two-dimensional cases in OpenFOAM v2312 (December 2023; interFoam, volume of fluid). The benchmark tank is rectangular, 1 m long and 1 m high. In each free-decay run, a small first-mode wave rings down in the still tank, and its frequency is read from the record. Fill is the still-water depth as a share of the tank height. The analysis results for the two-dimensional tank case are compared to the available public literature. At fills of 15, 30, 50 and 70 %, the largest difference from linear theory is 0.30 %, at 30 % fill, where CFD is below theory. Refining the mesh from 1,600 to 25,600 cells moves that difference only from 0.326 % to 0.296 %. It comes mainly from the finite height of the starting wave, not from the mesh. ## The resonance moves with roll angle and roll axis Forced-roll runs drive a 0.9 m tank at 1 to 8° roll over a range of periods. They find the resonance from the phase of the tank's response (Bäuerlein and Avila 2021). At 30 % and 70 % fill, the resonant frequency falls as roll grows: about 1 to 4 % below the formula at 2°, and about 11 to 13 % below at 8°. These shifts come from runs of six roll cycles, which the study reads as lower bounds: a 12-cycle run gives a larger shift. At 15 % fill the resonance sits above the formula instead: 7.5 % above at 1°, and 1.2 % above at 8°, which is within the sweep's resolution. There the water crosses the tank as a breaking bore and runs up the wall to about three times its still depth at 8°. Where the roll axis sits below the tank, for example for a tank high in the hull, the tank is also pushed sideways as it rolls (Kapsenberg and Carette 2023). At 70 % fill and 4° roll, rolling the tank about its own floor puts the resonance about 10 % below the formula, in a 12-cycle run; the 6-cycle point for 70 % fill and 4° in the chart below reads 8 %. With the axis half a tank length below the floor, the resonance sits about 16 % below; with the axis one tank length below, about 20 % below. The study quotes these shifts to the nearest percent. Peak wall run-up is about 15 % higher with the axis below the floor. ## Tank damping has an optimum The forced-roll runs at 4° also give each fill's equivalent damping ratio: 0.095 at 30 % fill, 0.18 at 50 % and 0.305 at 70 %. These feed a screening step with the classic tuned-absorber equations used for anti-roll tanks (Moaleji and Greig 2007), at a tank-to-vessel mass ratio of 0.05, with perfect tuning and no hull damping. The best damping ratio is then 0.13. At 30 % fill the tank is under-damped and splits the vessel's roll response into two peaks. At 70 % fill it is over-damped and the peak grows again. The 50 % fill gives the lowest roll peak of the three. ## Run time on one workstation Each case runs on one core. A batch of 48 forced-roll cases ran 14 at a time on one 32-core workstation in 34.7 min, against an estimated 247 to 336 min one at a time. Read the full study: https://vamseeachanta.github.io/digitalmodel/cfd/sloshing-cfd-study.html ## Charts and data The first chart compares the CFD frequencies with linear theory. Its x-axis, labelled "fill / slenderness ratio h / L", is the fill depth h over the tank length L. The benchmark tank is square, so h/L equals the fill. First-mode frequency, CFD against linear theory, two-dimensional tank. Differences, CFD minus theory: +0.28 % at 15 % fill, −0.30 % at 30 %, 0.00 % at 50 % and 70 %. Data: sloshing-cfd-benchmark.json (Appendix A). Chart values: fig1-sloshing-cfd-vs-theory.csv. The second chart shows how far the resonance moves as roll grows, at three fills. Resonant-frequency shift against roll amplitude, 0.9 m tank, OpenFOAM v2312. Data: sloshing-backbone.json and sloshing-shallow-refine.json (Appendix A). Chart values: fig3-resonance-shift-with-roll.csv. The animation shows one tank at 70 % fill, with forced roll on the left and none on the right. Open the animation Forced roll against no roll, OpenFOAM v2312 free-surface fields. The motion-forecast demo runs in a browser. It forecasts vessel motion 65 s ahead on a simulated sea state and gives an illustrative go, caution, hold or no-go call; useful calls need live motion-sensor input. The animation steps the significant wave height from 1.0 to 4.0 m. Try the demo: https://vamseeachanta.github.io/digitalmodel/hydro/short-horizon-motion-forecast.html Open the animation Motion forecast demo, crane lift, peak wave period 9.0 s, significant wave height 1.0 to 4.0 m. Illustrative calls. To try it out or adapt the analysis, see reusable prompt. If you have run your own analysis, see a way to improve this one, or have an idea for a future issue, write to support@aceengineer.com. We read every reply and credit the ideas we use and provide results we obtained. Prepared: Analyst Deckhand · Checked: Editor Deckhand · Approved: Vamsee Achanta (12 Nov 2026). Deckhand roles are AI assistants on the AceEngineer team: they ran the analysis and prepared and checked this edition. Version 1.2, prepared 12 Nov 2026. ## References Project references AceEngineer, Tank sloshing CFD study with OpenFOAM, study page. https://vamseeachanta.github.io/digitalmodel/cfd/sloshing-cfd-study.html AceEngineer, The Deckhand Chronicles: Energy Street, Issue 1, 27 Oct 2026. https://www.aceengineer.com/newsletter/issue-001-energy-street/ External references Bäuerlein, B. and Avila, K. (2021), Phase lag predicts nonlinear response maxima in liquid-sloshing experiments. Journal of Fluid Mechanics 925, A22. Kapsenberg, G. and Carette, N. (2023), A consistent method to design and evaluate the performance of anti-roll tanks for ships. Ship Technology Research 70(2), 117-145 (online 21 Sep 2022). DOI 10.1080/09377255.2022.2117496. Moaleji, R. and Greig, A.R. (2007), On the development of ship anti-roll tanks. Ocean Engineering 34(1), 103-121. Web references OpenFOAM v2312 (December 2023), OpenCFD Ltd, GPL v3 licence. https://www.openfoam.com/ ## Appendix A Reusable prompts This prompt lets your team, or any assistant, recompute the theory side of our sloshing benchmark, compare it with our published CFD values, and read the resonance shifts at 8° roll from our archived data. With OpenFOAM, it also reruns a CFD case. To have a study of your own tanks done for you instead, see below. ### What you need to run this Data required: None to reproduce the benchmark; Data required to adapt: tank length, fill depth and shape, your vessel's roll period, the roll angle of interest and the roll axis height. Paid or behind an account: nothing. OpenFOAM is free, open-source software. Changes over time: nothing. The CFD outputs are archived at a fixed commit. ### Reproduce the published result Give this prompt to your assistant: Using the study at https://vamseeachanta.github.io/digitalmodel/cfd/sloshing-cfd-study.html and our public code repository https://github.com/vamseeachanta/digitalmodel at commit 705857af62385a4567c96be99a129cdff3051a52 (MIT licence), with Python 3.11: 1. Recompute the theory side and compare with our published CFD values. For a two-dimensional rectangular tank of length L and fill depth h, linear theory gives the first-mode frequency as Omega1 = omega1 * sqrt(L / g) = sqrt(pi * tanh(pi * h / L)). Compute it at h/L = 0.15, 0.30, 0.50 and 0.70. Compare it with the published CFD values 1.1779, 1.5164, 1.6974 and 1.7508, archived in docs/api/structural/sloshing-cfd-benchmark.json at that commit. Report each difference in %, signed: (CFD - theory) / theory. Check: theory 1.1746, 1.5210, 1.6974 and 1.7508; differences +0.28 %, -0.30 %, 0.00 % and 0.00 % (CFD is below theory at h/L = 0.30). 2. Read docs/api/structural/sloshing-backbone.json at that commit. Report detuning_pct at 8 deg roll for h/L = 0.30 and 0.70. Check: -10.81 % and -13.25 %. 3. Only if I have OpenFOAM v2312 on Linux, rerun the free-decay cases (about 10 min per case) at that commit: git clone --filter=blob:none https://github.com/vamseeachanta/digitalmodel cd digitalmodel git checkout 705857af62385a4567c96be99a129cdff3051a52 source /usr/lib/openfoam/openfoam2312/etc/bashrc uv venv --python 3.11 uv pip install --no-sources -e . .venv/bin/python scripts/cfd/run_sloshing_benchmark.py free-decay --work-dir ./sloshing-work The run rewrites docs/api/structural/sloshing-cfd-benchmark.json, so compare its new values with the step 1 check values above, not with the file itself. ### Adapt it to your project Before you start, ask me for: my tank length, fill depth and shape; my vessel's roll period; the roll angle of interest; the roll axis height below the tank floor. These checks still apply when my result differs: the closed form holds for a rectangular tank at small amplitude; the four published cases still reproduce; any resonance is reported with the roll angle and roll axis used. Public data set: the archived OpenFOAM v2312 outputs, sloshing-cfd-benchmark.json, sloshing-backbone.json and sloshing-shallow-refine.json, at commit 705857af of our public code repositories (MIT licence, fixed). Code: our public code repositories, https://github.com/vamseeachanta/digitalmodel (MIT licence). To have a study of your own tanks done for you, write to support@aceengineer.com. Questions: support@aceengineer.com · AceEngineer · © 2026 AceEngineer · 11511 Piping Rock Dr., Houston, TX 77077 Deckhand: Make Engineering Enjoyable Again ## Sacrificial anodes needed for six offshore structures on each edition of DNV-RP-B401 and DNV-RP-F103 (Deckhand newsletter, issue 2) URL: https://www.aceengineer.com/newsletter/issue-002-energy-street/ Description: A subsea export pipeline sized with 9 bracelet anodes on DNV-RP-F103 2010 needs 34 on the 2019 edition; five other structures change by one anode or none across four DNV-RP-B401 editions. The Deckhand newsletter · Issue 2 · Energy Street # Sacrificial anodes needed for six offshore structures on each edition of DNV-RP-B401 and DNV-RP-F103 Prepared: Corrosion Deckhand (AI assistant) · Checked: Editor Deckhand · Approved: Vamsee Achanta · 3 November 2026 Deckhand is the name of the assistants on our team; Corrosion Deckhand prepared this study. Sacrificial-anode cathodic protection (CP) protects offshore steel from corrosion with anodes that corrode in its place. DNV sets out CP design in two recommended practices: DNV-RP-B401 for offshore structures and DNV-RP-F103 for subsea pipelines. A subsea export pipeline sized with 9 bracelet anodes (half-shell anodes clamped around the pipe) on the 2010 edition of DNV-RP-F103 needs 34 on the 2019 edition, 277.8 % more, with every other input held fixed. Each structure is run in the cathodic protection module of the open-source digitalmodel library (MIT licence). In that library, the 2019 edition raises the mean coating breakdown factor for fusion-bonded epoxy, a factory-applied pipe coating, over a 30-year life from 0.0145 to 0.045 (2010 edition, Table A.1; 2019 edition, Table A-1). The coating breakdown factor is the share of the bare-steel current that the coated pipe still needs. For a line carrying fluid at 60 °C, the 2019 edition also raises the mean current density, the current that each square metre of bare steel needs, from 0.060 to 0.075 A/m² (2010 edition, Table 5-1; 2019 edition, Table 6-2). The mean current demand of the 1.5 km section goes from 1.33 A to 5.15 A. Anode mass governs on both editions: the alloy mass needed for the design life sets the count (218.1 kg against 846.1 kg). The count rises 277.8 % and the mass 287.9 %, because each count is rounded up to whole 25 kg bracelets (8.72 to 9, and 33.84 to 34). Sweep: Design lifeFluid temperature Figure 1 - Bracelet anodes required for the 1.5 km export pipeline, DNV-RP-F103 2010 against 2019, swept over design life (fluid at 60 °C) or fluid temperature (30-year life). Each marker is one run of 30 October 2026; the ringed markers are the recorded edition runs (9 and 34). Hover for the anode mass and the current density. Data: energy-fig1-pipeline-sweep.csv. On the 2019 edition, nine bracelets cover a 10-year design life; on 2010 the same nine cover 30 years. The 2019 count also steps up above 25 °C and above 50 °C fluid temperature, where its current density bands change; the 2010 count steps once, above 50 °C. The coating breakdown factor does most of the work: changed alone, it raises the anode mass for a 30-year life by 210.3 %, against 25.0 % for the current density alone (the build-up, Figure 2 below). The other five structures change little (Figure 3 below). Four need the same anode count on all four DNV-RP-B401 editions from 2005 to 2021. The hybrid riser needs one fewer on 2021 (25 against 26, −3.8 %), because the library's 2021 route (its set of values for that edition) sets the closed-circuit potential of aluminium anodes in sediment, the potential of the anode while it delivers current, at −1.00 V against −0.95 V (measured against a silver/silver chloride reference electrode in seawater, Ag/AgCl/seawater). The riser is the only one of the six structures with anodes in seabed sediment, on its suction-pile foundation, so it is the only one that this value changes. Try it out: find the edition your pipeline's CP design used. If it is DNV-RP-F103 2010, re-check it on the 2019 edition with the same inputs before the next CP potential survey. The public data set for this study is the platform structures register of the US Bureau of Safety and Environmental Enforcement (BSEE) for the US Gulf of Mexico (US federal government data, retrieved 29 October 2026). Of the 1,301 platform structures still standing in US federal waters of the Gulf of Mexico, 1,124 were installed before 2005, the year of the oldest DNV-RP-B401 edition the library runs; their median installation year is 1983. The register and its map are in Figure 4 below. ## Full study Each structure is one input file in the library. The 84.1 m jacket takes its areas, current densities and anode size from Xu (2023); its other inputs are based on previous project experience. The 60 m wind jacket takes its geometry from Mroczek and others (2023). Every structure is run on every edition route its code accepts, with the anode type, size and alloy, the design life and every other input held fixed. The count is the largest of three checks: anode mass for the design life, current output of new anodes, and current output at end of life. Structure Code Anodes required on each edition route (-) Newest against oldest route (%) Export pipeline, bracelet anodes DNV-RP-F103 9 on 2010; 34 on 2019 +277.8 % Hybrid riser DNV-RP-B401 26 on 2005, 2010 and 2017; 25 on 2021 −3.8 % Jacket, 84.1 m water depth (areas, current densities and anode size: Xu, 2023) DNV-RP-B401 575 on all four 0.0 % Wind jacket, 60 m water depth (published geometry: Mroczek et al., 2023) DNV-RP-B401 424 on all four 0.0 % Monopile DNV-RP-B401 48 on all four 0.0 % Subsea manifold DNV-RP-B401 64 on all four 0.0 % Table 1 - Anodes required by structure and edition route, runs of 29 October 2026. Four more structures were run and are not shown. A synthetic jacket needs 173 anodes on all four editions. A phased riser base needs the same count on all four, although the final check of its anodes in mud fails on the 2005 to 2017 routes and passes on 2021. A temporary frame gives the same values on all four. A mixed-zone structure runs only on the 2021 route, because the older routes have no anode values at 60 °C. ### Export pipeline inputs The export pipeline's inputs are those of its case file in the library (Table 2). The anode design values, such as the electrochemical capacity, come from the tables of the edition run. Input Value Outer diameter 0.3239 m (12.75 in) Wall thickness 15.9 mm Section length 1,500 m Burial Not buried: the line lies on the seabed Fluid temperature 60 °C (swept from 5 to 80 °C in Table 4) Design life 30 yr (swept from 10 to 40 yr in Table 3) Linepipe coating Fusion-bonded epoxy (FBE) Concrete weight coating None: not set in the case file, so the library default (none) applies Anode type and net alloy mass Bracelet, 25 kg each; 0.2 m long, 0.04 m thick Anode alloy Aluminium; the alloy grade is not given in the case file Anode utilisation factor 0.80 (DNV-RP-F103 2019 [6.4.2]; DNV-RP-B401 2010 Table 10-8) Anode electrochemical capacity From the edition run: DNV-RP-B401 2010 Table 10-6 for the 2010 runs; DNV-RP-F103 2019 Table 6-3 for the 2019 runs Table 2 - Export pipeline inputs, from the library's pipeline case file (References). ### What drives the pipeline change The coating breakdown factor does most of the work. Changed alone, it raises the anode mass for a 30-year life by 210.3 %, from 9 to 28 bracelets. The current density alone adds 25.0 %, from 9 to 11 bracelets. The two multiply, so together they raise the mass by 287.9 %, to 34 bracelets. Design life: 10 yr15 yr20 yr25 yr30 yr35 yr40 yr Figure 2 - Build-up of the 2010 to 2019 change for the 1.5 km export pipeline, fluid at 60 °C: anode mass on the 2010 edition, with only the 2019 mean coating breakdown factor, with only the 2019 mean current density, and on the 2019 edition. Labels give the bracelets required (25 kg each). The two middle bars are derived from the recorded runs: the anode mass is proportional to the product of the two factors, which holds to within 0.001 % on all 14 distinct recorded run pairs: the seven design lives of Table 3 and the eight fluid temperatures of Table 4, each run on the 2010 and the 2019 edition (the 30-year, 60 °C pair is in both). Hover for the factor values. Data: energy-fig2-buildup.csv. Figure 3 - Anodes required on the newest edition route as a percentage of the count on the oldest route of the same code (2021 against 2005 for DNV-RP-B401; 2019 against 2010 for DNV-RP-F103). The 100 % line is a design sized on the oldest route. Runs of 29 October 2026. Data: energy-fig3-structures.csv. Tables 3 to 5 - the pipeline sweep behind Figure 1 (above) and the build-up behind Figure 2 Design life (yr) Bracelets, 2010 (-) Bracelets, 2019 (-) Anode mass, 2010 (kg) Anode mass, 2019 (kg) 10 3 9 57.7 219.4 15 4 15 92.1 352.5 20 6 21 130.4 501.4 25 7 27 172.4 665.9 30 9 34 218.1 846.1 35 11 42 267.6 1,042.0 40 13 51 320.9 1,253.5 Table 3 - Pipeline sweep over design life, fluid at 60 °C, 25 kg net aluminium bracelets. Fluid temperature (°C) Bracelets, 2010 (-) Bracelets, 2019 (-) Mean current density, 2010 (A/m²) Mean current density, 2019 (A/m²) 5 8 23 0.050 0.050 20 8 23 0.050 0.050 30 8 28 0.050 0.060 40 8 28 0.050 0.060 50 8 28 0.050 0.060 60 9 34 0.060 0.075 70 9 34 0.060 0.075 80 9 34 0.060 0.075 Table 4 - Pipeline sweep over fluid temperature, 30-year design life. Design life (yr) Mean coating breakdown factor, 2010 / 2019 (-) Bracelets, 2010 (-) Bracelets, 2019 breakdown factor only (-) Bracelets, 2019 current density only (-) Bracelets, 2019 (-) 10 0.0115 / 0.035 3 8 (+204.3 %) 3 (+25.0 %) 9 (+280.4 %) 15 0.01225 / 0.0375 4 12 (+206.1 %) 5 (+25.0 %) 15 (+282.7 %) 20 0.013 / 0.04 6 17 (+207.7 %) 7 (+25.0 %) 21 (+284.6 %) 25 0.01375 / 0.0425 7 22 (+209.1 %) 9 (+25.0 %) 27 (+286.4 %) 30 0.0145 / 0.045 9 28 (+210.3 %) 11 (+25.0 %) 34 (+287.9 %) 35 0.01525 / 0.0475 11 34 (+211.5 %) 14 (+25.0 %) 42 (+289.3 %) 40 0.016 / 0.05 13 41 (+212.5 %) 17 (+25.0 %) 51 (+290.6 %) Table 5 - Build-up behind Figure 2, fluid at 60 °C, mean current density 0.060 A/m² on 2010 and 0.075 A/m² on 2019. Percentages are the change in anode mass against the 2010 run. ### Public data set: BSEE platform structures, US Gulf of Mexico Source: BSEE Data Center, raw data downloads (Platform Structures). The register lists 7,091 platform structures in US federal waters of the Gulf of Mexico, with type, water depth, location and installation and removal dates; 1,301 have no removal date recorded and are counted as still standing. Of those 1,301, 980 are fixed jackets. By installation year, 849 of the 1,301 were installed before 1993 and 1,124 before 2005 (the 849 are among the 1,124). The register gives installation years, not the CP code edition each structure was designed to. In US practice, the US Code of Federal Regulations lists NACE RP0176-2003, Corrosion Control of Steel Fixed Offshore Structures Associated with Petroleum Production, among the standards that platform plans must conform to, as appropriate (30 CFR 250.901(a)(21)). Its current form is NACE SP0176, kept by AMPP (Association for Materials Protection and Performance); edition to be confirmed. View: MapInstallation year Figure 4 - The 1,301 platform structures still standing in US federal waters of the Gulf of Mexico, coloured by installation before 2005 or from 2005 on; the installation-year view marks the code edition years 1993, 2005, 2010, 2017 and 2021. Source: BSEE Platform Structures raw data, retrieved 29 October 2026 10:17Z. Operator names are left out. Hover for type, water depth and installation year. Data: energy-fig4-platforms-standing.csv. Our open-source digitalmodel library runs DNV-RP-B401 editions available. Of the platform structures still standing in US federal waters of the Gulf of Mexico, 1,124 were installed before 2005. This study leaves open how far, if at all, their anode design falls short of the current DNV-RP-B401 edition. ## Reusable prompts Run the six structures of Table 1 on every DNV-RP-B401 and DNV-RP-F103 edition with every other input held fixed, sweep the export pipeline over design life and fluid temperature, compare your counts with Tables 1, 3 and 4, and redraw Figure 4 from the BSEE platform structures register. Data: The six structure input files of the digitalmodel library (MIT licence), in tests/fixtures/cathodic_protection/workflow_inputs: pipeline, multi_component_riser, published_jacket_84m, reference_jacket_60m_members, monopile and manifold. BSEE Platform Structures raw data (Bureau of Safety and Environmental Enforcement, US Department of the Interior), PlatStrucRawData.zip on the BSEE raw data page, US federal government data, listed as updated daily. Counted copy retrieved 29 October 2026 10:17Z, SHA-256 bde13c85717ec4ad164f6b95fe0c18758f163dd33efb4d66d949c032b9bc5b52. Recounted from the file of 2 November 2026 (retrieved 3 November 2026 02:28Z, SHA-256 fa24a50febfe689db8446ffa17dd4c29474fbd700fb44ef4ff80c6f78f759b19) with the same counts: 7,091 structures, 1,301 still standing, 980 fixed jackets, 849 installed before 1993, 1,124 before 2005, median installation year 1983. Code: the cathodic protection module on GitHub (digitalmodel, src/digitalmodel/cathodic_protection, MIT licence); the commit of the study runs is given in References. Readers are welcome to share their own counts at support@aceengineer.com. ## References Codes: DNV-RP-B401 (2005 with 2008 amendments, October 2010, June 2017 as DNVGL-RP-B401, May 2021); DNV-RP-F103 (October 2010; September 2019 as DNVGL-RP-F103, amended May 2021); NACE RP0176-2003, Corrosion Control of Steel Fixed Offshore Structures Associated with Petroleum Production (current form NACE SP0176, AMPP, edition to be confirmed). Regulations: US Code of Federal Regulations, 30 CFR 250.901, "What industry standards must your platform meet?", eCFR, current to 30 October 2026, ecfr.gov. Software: digitalmodel, cathodic protection module, commit 09089a1, https://github.com/vamseeachanta/digitalmodel; pipeline case file at that commit, pipeline.yml. Other references: D. Xu (2023), Engineering Advances 3(3), 241-245, DOI 10.26855/ea.2023.06.017; M. M. Mroczek, S. R. Arwade and M. A. Lackner (2023), Wind Energy Science 8, 807-817, DOI 10.5194/wes-8-807-2023. Questions: support@aceengineer.com · AceEngineer · © 2026 AceEngineer · 11511 Piping Rock Dr., Houston, TX 77077 Deckhand: Make Engineering Enjoyable Again ## Jack-up site-specific analysis (Deckhand newsletter, issue 2) URL: https://www.aceengineer.com/newsletter/issue-002-jackup-method/ Description: What a site-specific assessment of a jack-up or liftboat checks, the site and unit data it needs, and the codes and US regulations that apply. The Deckhand newsletter · Issue 2 · Energy Street # Jack-up site-specific analysis Prepared: Analyst Deckhand (AI assistant) · Checked: Editor Deckhand · Approved: Vamsee Achanta · 3 November 2026 On 24 October 2026, a jack-up drilling unit sank offshore Gabon. Of the 115 people on board, 110 were accounted for and brought ashore [1, 2]. Press reports of the dead and missing differ and await official confirmation [1, 2]. Our thoughts are with everyone affected, and with their families and colleagues. Gabon's Ministry of Petroleum and Gas has ordered a technical investigation [1, 2]. The rig owner, Borr Drilling, said on 25 October 2026 that "preliminary information indicates that the rig experienced a punch through event during preload activities" [18]. The investigation's findings are awaited. Apart from the rig owner's statement, nothing in this piece bears on the cause of the loss. This piece is to demonstrate and progress complex engineering methods and workflows. We would like to use this opportunity to develop reusable engineering for the jack-up and the liftboat, in a bid to learn and also to help with future site studies for similar structures. ## 1 Public facts on the loss offshore Gabon Each statement on the loss is entered in a register with its source and date (Table 1). The register is checked against its sources again on the day the page is published. Id Statement Source F1 A jack-up drilling unit sank offshore Gabon on 24 October 2026. [1], [2] F2 115 people were on board; 110 were accounted for and brought ashore. [1], [2] F3 Press reports of the dead and missing differ (World Oil, citing Reuters; Marine Insight, citing the Gabonese authorities) and await official confirmation. [1], [2] F4 The Ministry of Petroleum and Gas ordered a technical investigation, to determine the circumstances of the sinking. [1], [2] F5 The rig owner, Borr Drilling, said on 25 October 2026 that "preliminary information indicates that the rig experienced a punch through event during preload activities". [18] Table 1 - Public facts register for the loss offshore Gabon. Sources dated 25 and 28 October 2026, read again on 3 November 2026; [18] read on 4 November 2026. Figure 1 shows where the loss happened, as reported. No position has been published, so the whole country is shaded. Figure 1 - October 2026, offshore Gabon (location as reported; cause under investigation) [1, 2]. The sections below use no data from this loss. They apply to any jack-up or liftboat at any site. ## 2 Jack-ups, liftboats and wind installation jack-ups all stand on legs A drilling contractor's annual report counts 494 jack-ups in the global fleet at the end of 2025 [9]. On 1 August 2022, 77 US-flagged liftboats were in active service [10]. We found no public world count of liftboats or of wind installation jack-ups. The three types of unit work in the same way: A jack-up is a mobile unit with a floating hull and legs that it lowers to the seabed. It then raises the hull clear of the sea. A liftboat is an offshore supply vessel with movable legs capable of raising its hull above the surface of the sea [7]. It has three or four legs and its own propulsion, and it serves oil platforms and wind turbines [10]. Wind installation jack-ups, or wind turbine installation vessels, are "self-propelled heavy-lift jack-up vessels designed for the installation of offshore wind turbines" [11]. All three preload their legs to test the soil before they raise the hull to its working height [4; 12; 13, p. 77]. ## 3 Serious jack-up and liftboat accidents, 1999 to 2022: 35 events in three public sources Liftboats and wind installation jack-ups have an accident record like that of drilling jack-ups. A 2019 review of self-elevating platform incidents finds liftboat incidents "identical to Jack-up incidents" [12]. For wind installation jack-ups, the 2010 MMS report states: "Much can be anticipated about incidents and accidents by looking at the track record of jack-ups in the North Sea and liftboats in Gulf of Mexico" [13]. Figure 2 shows all 35 serious accidents in three public sources, by year and initiating hazard [10, 13 to 17]. The MMS report lists 14 accidents of jack-up construction vessels (construction jack-ups below), mostly at wind farms, from 1999 to 2008. The 2021 review lists 17 of the worst drilling jack-up accidents from 2012 to mid-2021. Four NTSB reports cover one liftboat each. By our count of Table 2, 17 events are on drilling jack-ups, 13 on construction jack-ups and 5 on liftboats. By our hazard grouping (Note 1), 4 start with storm or weather, 11 with punch-through or foundation, and 4 with leg, jacking or structural failure. Another 4 happen in transit or tow, and 12 are other or not stated. By yearBy hazard Figure 2 - Serious accidents of jack-ups and liftboats in three public sources, 1999 to 2022, by year and initiating hazard, or counted by hazard. Filled markers: NTSB investigation reports. Open markers: compiled lists, not investigations. They are the MMS report, compiled from an industry database with some rows quoting press, and the 2021 review, from DNV's WREC accident database. Markers of the same year and hazard are set apart vertically. Data: jackup-accidents.csv (Table 2). Note 1: the hazard groups are ours. An event under tow or in transport is transit or tow. Other events follow the source's cause code or wording; where the source states no hazard, the event is other or not stated. Each source covers its own scope and period, so the chart dates these events; the rates below come from the 2021 review. Over a longer span, that review counts 90 liftboat losses, with 56 deaths [14]. It puts the liftboat loss rate at 2 to 3 times that of drilling jack-ups [14]. On jack-ups, deaths per operating rig-year fell from 0.07 to 0.007 over 61 years of records [14]. Table 2 - the 35 accidents behind Figures 2 and 3, with the source of each Year Unit Unit type Location What happened (source wording, shortened) Initiating hazard (our grouping) Source 1999 Aarsleff Jack construction jack-up Horns Rev, Denmark (wind-farm centroid) Overturned other or not stated Compiled list: MMS report, Table 1 [13] 2000 Wijslift 6 construction jack-up Blyth, UK (wind-farm centroid) Hull dropped other or not stated Compiled list: MMS report, Table 1 [13] 2003 Excalibur (ex Wijslift 6) construction jack-up North Hoyle, UK (wind-farm centroid) Broken leg leg, jacking or structural failure Compiled list: MMS report, Table 1 [13] 2003 MEG-JB1 construction jack-up North Hoyle, UK (wind-farm centroid) Crane collapse other or not stated Compiled list: MMS report, Table 1 [13] 2003 Skate II construction jack-up Gunfleet, UK (wind-farm centroid) Punch-through: hull dropped punch-through or foundation Compiled list: MMS report, Table 1 [13] 2004 Skate III construction jack-up Brighton, UK (town anchor) Wrecked other or not stated Compiled list: MMS report, Table 1 [13] 2005 A2Sea Ocean Ady (now Sea Energy) construction jack-up Scroby Sands, UK (wind-farm centroid) Leg damage leg, jacking or structural failure Compiled list: MMS report, Table 1 [13] 2006 Octopus construction jack-up Orkney, UK (islands anchor) Ran aground during tow transit or tow Compiled list: MMS report, Table 1 [13] 2007 JB-104 construction jack-up Milford Haven, UK (town anchor) Capsize, 1 fatality; alongside the dock, not in wind farm service other or not stated Compiled list: MMS report, Table 1 [13] 2007 Smit Lisa construction jack-up Robin Rigg, Solway Firth, UK (wind-farm centroid) Punch-through: hull dropped punch-through or foundation Compiled list: MMS report, Table 1 [13] 2008 Dredging barge construction jack-up Mallorca, Spain (island anchor) Abandon ship by helicopter operations other or not stated Compiled list: MMS report, Table 1 [13] 2008 Jakup construction jack-up Teesside, UK (town anchor) Wrecked other or not stated Compiled list: MMS report, Table 1 [13] 2008 Russell W. Peterson liftboat about 14 miles off Rehoboth Beach, Delaware, USA (town anchor) Wrecked, 1 fatality, in a May 2008 nor'easter (press quoted in the report) storm or weather Compiled list: MMS report, Table 1 [13], quoting press; US Coast Guard report not found 2008 Titan 1 construction jack-up Atlantic (position not public) Lost overboard from a heavy lift vessel transit or tow Compiled list: MMS report, Table 1 [13] 2011 Trinity II liftboat Bay of Campeche, about 15 miles offshore, north of Frontera, Mexico, 84 ft water (position estimated from the NTSB text) Elevated in hurricane-force conditions; stern jacking leg failed, vessel listed; 4 died storm or weather NTSB investigation report NTSB/MAR-13/01 [15] 2012 Hercules 2502 drilling jack-up Gulf of Mexico (position not public) Under tow: mat badly damaged by poor cribbing alignment on the barge for a dry tow; rig retired, declared a total loss in 2019 transit or tow Published review: 2021 review, Appendix A [14]; cause code S (structural) 2013 Hercules 265 drilling jack-up South Timbalier 220, Gulf of Mexico (position not public) Gas blowout; fire in derrick; beams supporting derrick and rig floor collapsed other or not stated Published review: 2021 review, Appendix A [14]; cause code O (blowout) 2013 Perro Negro 6 drilling jack-up Congo River mouth, Angola, 40 m water (anchor: Soyo town) Capsized after punch-through, with 103 on board punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B (punch-through) 2013 Trident 15 drilling jack-up Moragot 19, Thailand (position not public) Port leg punch-through giving 7° list; many braces damaged punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B (punch-through) 2014 Aquamarine Driller 5 drilling jack-up off Miri, Sarawak, Malaysia (anchor: Miri town) Serious punch-through (plus possible heavy-weather damage under tow) punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B (punch-through) 2014 Ensco 104 drilling jack-up Malaysia (position not public) 2 crew killed when a lifeboat fell 150 ft to the sea during maintenance other or not stated Published review: 2021 review, Appendix A [14]; cause code N (falling object) 2014 Menadrill 1 drilling jack-up Akal field, Gulf of Mexico (anchor: Cantarell field) Fire in shale shakers or motor generator room other or not stated Published review: 2021 review, Appendix A [14]; cause code F (fire) 2014 Rowan Louisiana drilling jack-up Vermilion 366, Gulf of Mexico (position not public) Well control problem during wiper trip; all non-essential crew evacuated other or not stated Published review: 2021 review, Appendix A [14]; cause code O (blowout) 2015 COSLGift drilling jack-up South-east Asia (position not public) Serious punch-through punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B (punch-through) 2015 Rigmar 152 drilling jack-up South Atlantic (position not public) Sank under tow from Brazil to Gabon transit or tow Published review: 2021 review, Appendix A [14]; cause code K (flooding) 2015 Rumailah drilling jack-up Al Shaheen field, Qatar (field centroid) Punch-through; 3 legs broken punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B (punch-through) 2015 Troll Solution drilling jack-up Caan Alfa well, Gulf of Mexico (anchor: Cantarell field) Probable punch-through and tilt when positioning for maintenance on a well punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B (punch-through) 2016 SAR 201 drilling jack-up beside Safaniya platform, Saudi Arabia (field centroid) Punch-through (or jack failure) on port leg; deck at port stern dropped to nearly sea level; evacuated; 3 missing punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B/M (punch-through or jacking system) 2017 Maersk Interceptor drilling jack-up Tambar field, Norway (field anchor) Sling lifting a pump broke; 2 drilling staff injured, 1 then went overboard, was recovered and died other or not stated Published review: 2021 review, Appendix A [14]; cause code L (lifting) 2017 West Titania drilling jack-up Manick 100-1A, Gulf of Mexico (position not public) Jacking system failure; trim by stern and slight list; flooding of starboard stern main deck leg, jacking or structural failure Published review: 2021 review, Appendix A [14]; cause code M (jacking system) 2018 KS Java Star drilling jack-up next to Camar Seagull jacket, SE of Bawean Island, Indonesia (anchor: Bawean) Rapid penetration of starboard leg when preloading; gas well fire on adjacent platform leg, jacking or structural failure Published review: 2021 review, Appendix A [14]; cause code M (jacking system) 2019 Kristin Faye liftboat Main Pass Block 64, about 18 nm east of Venice, Louisiana, USA, 35 ft water Elevated liftboat overturned in under a minute after a crane boom was raised; NTSB: punch-through of one of three legs punch-through or foundation NTSB investigation report NTSB MAB-20/36 [16] 2021 SEACOR Power liftboat about 7 nm off Port Fourchon, Louisiana, USA, about 50 ft water Capsized while under way in a severe thunderstorm; 13 died storm or weather NTSB investigation report NTSB MIR-22/26 [10] 2021 Velesto Naga 7 drilling jack-up Salam-3 well, offshore Sarawak, Malaysia (anchor: Miri town) Punch-through; fully submerged punch-through or foundation Published review: 2021 review, Appendix A [14]; cause code B (punch-through) 2022 L/B Robert liftboat 80 nm SE of Lake Charles, Louisiana, USA, 217 ft water Unmanned and elevated: gale winds and waves above the air gap moved the vessel; a leg slid into an adjacent can hole; vessel tilted storm or weather NTSB investigation report NTSB MIR-23-28 [17] Table 2 - Serious jack-up and liftboat accidents in three public sources, 1999 to 2022, with the source of each. Locations in brackets give the reference point used on the map in Figure 3. ## 4 Past accidents on the map: 26 of the 35 events Figure 3 places the 26 accidents with a public reference position on a world map. They lie off northern Europe and Mallorca, the United States and Mexico, West Africa, Qatar and Saudi Arabia, and South-east Asia. The other 9 have no public position; Table 2 gives only a sea area, country, field, lease block or well for them. WorldNorthern EuropeGulf of Mexico Figure 3 - Locations of the past accidents of Figure 2, by unit type. NTSB positions are those of its reports. Other markers are reference points for the named field, wind farm, island or town; the Trinity II marker is estimated from the NTSB text. Drag to pan; scroll or pinch to zoom. Data: jackup-accidents.csv. ## 5 What a site-specific assessment covers Before a jack-up works at a new location, a site-specific assessment checks the unit at that location [3, 4]. The assessment covers: The foundation: how the seabed at that location carries the footings at the foot of each leg (spudcans). SNAME 5-5A lists foundation hazards that include punch-through, settlement or bearing failure, sliding, scour and seafloor instability [4, Table 3.1]. In a punch-through, a leg breaks through a strong soil layer into weaker soil below and drops quickly. The structure: the strength of the legs, the hull and the holding system, the machinery that holds the hull at its height on the legs. Overturning and sliding: whether the whole unit stays upright and in place in the assessment storm, the extreme storm that the unit is checked against at that site. The air gap: the clearance between the hull and the highest wave crest. The moves: the stability of the unit while it floats, under tow or under its own power. For a jack-up, this follows the stability chapter of the IMO code for mobile offshore drilling units (MODUs) [6]; for a liftboat, the US Coast Guard rules [8]. In US federal waters, Title 30 of the US Code of Federal Regulations (30 CFR) covers the use of a MODU in section 250.713 [5]. Under 250.713(a), the operator must show the unit's capability at the proposed location, including the minimum air gap. Under 250.713(b), the operator must also show that the site-specific soil and oceanographic conditions can support a bottom-founded unit, one that stands on the seabed [5]. For a liftboat, we apply the foundation, structure and air gap checks as for a jack-up. Its overturning check must also meet the US Coast Guard's special rules for liftboats, sections 174.240 to 174.260 of Title 46 of the CFR [8]. For a liftboat in restricted service, 46 CFR 174.255(c) sets on-bottom stability: a continuous downward force on each footing under waves, currents and 70-knot winds in normal operation, and 100-knot winds in a severe storm [8]. The same sections set its stability afloat and its freeboard [8]. ## 6 Site and unit data A site study needs two groups of data: data on the site and data on the unit (Table 3). Data group What the study needs Public sources Water depth and seabed Water depth at each leg position; a seabed survey for obstructions and debris Regional bathymetry (charted water depths), for example the GEBCO grid (General Bathymetric Chart of the Oceans); the site survey is held by the operator Soil Borings or cone penetration tests at the location, with the soil strength with depth Rarely public; held by the operator or its survey contractor Metocean Wind, waves, current and water level for the assessment storm, and for the weather windows of a move Buoy records, for example the NOAA National Data Buoy Center; hindcasts (model reconstructions of past weather), for example ERA5 Unit Leg and hull geometry, spudcan size, weights, the capacity of the holding system, and the stability booklet Rig data sheets and classification society records, in part; the full data are held by the rig owner Table 3 - Data for a jack-up or liftboat site study, and where public sources exist. ## 7 How the methods serve future site studies Each site study starts from the same data list (Table 3). Each input is entered with its source and date, so a later study can see what was measured and what was assumed. Jack-ups and liftboats both raise their hulls on legs, so the checks of section 5 are set out for both; section 5 gives the checks that carry over to a liftboat and the US Coast Guard rules that add to them. The accident record of section 3 is kept beside the data list. Each new site study can then be read against the events seen on similar units. The inputs and results of each site study are kept with its prompt, for the next study of a similar structure. Try it out: for your next jack-up or liftboat move, list each input to the site assessment with its source and date. This piece leaves open which checks of a jack-up site study need changes before they apply to a liftboat. ## Reusable prompts Set out a site-specific assessment of a jack-up or liftboat at a new location: list the site and unit data it needs (Table 3), set out each check of section 5 with the edition and clause of each code it uses, and mark every input with its source. Then count the jack-ups and liftboats in service from public operator filings and investigation reports. Chart past serious accidents of all kinds by year, initiating hazard and unit type, and on a world map, each with its source. Name no cause for any event still under investigation. Data: the public data sets for each input, such as the GEBCO grid, the NOAA National Data Buoy Center records and ERA5, are named in Table 3. The accident data set behind Figures 2 and 3 is jackup-accidents.csv. It holds 35 public events, each with year, unit type, location, position, hazard group and source. The sources are the MMS report, the 2021 review and four NTSB investigation reports [10, 13 to 17]. The fleet counts are from [9] and [10]. Readers are welcome to share their own site study results at support@aceengineer.com. ## References [1] World Oil, citing Reuters, 25 October 2026, news report on the jack-up loss offshore Gabon. [2] Marine Insight, 28 October 2026, news report on the search and rescue offshore Gabon. [3] ISO 19905-1:2023, Site-specific assessment of mobile offshore units, Part 1: Jack-ups. [4] SNAME T&R Bulletin 5-5A, Recommended Practice for Site Specific Assessment of Mobile Jack-Up Units, Rev 3, August 2008. [5] US Code of Federal Regulations, 30 CFR 250.713, "What must I provide if I plan to use a mobile offshore drilling unit (MODU) for well operations?", eCFR, current to 30 October 2026, ecfr.gov. [6] IMO resolution A.1023(26), Code for the construction and equipment of mobile offshore drilling units, 2009 (2009 MODU Code), Chapter 3, stability. [7] 46 CFR 125.160, Definitions, "Liftboat", eCFR, current to 30 October 2026, ecfr.gov. [8] 46 CFR Part 174, Subpart H, Special rules pertaining to liftboats, eCFR, current to 30 October 2026, ecfr.gov. References [9] to [17] were read on 4 November 2026. [9] Valaris Ltd, Form 10-K for the year 2025, filed 20 February 2026, sec.gov. [10] NTSB, Marine Investigation Report MIR-22/26, capsizing of the liftboat SEACOR Power, adopted 18 October 2022, section 1.1.1, ntsb.gov. [11] NREL, Offshore Wind Market Report: 2024 Edition, NREL/TP-5000-90525, docs.nlr.gov. [12] van der Kraan, "Self Elevating Platform (Incl. Liftboat) Incidents", Jack-up Conference 2019, conference paper. [13] Sharples, "Damage and Critical Analysis of Accidents ... Offshore Wind Farms on the OCS", MMS TA&R Project 633, May 2010, Table 1 and p. 77, bsee.gov. [14] Jack, Hoyle and Hunt, "Jack-up Accident Statistics - Yet Another Update", Jack-up Conference 2021, Appendix A, conference paper. [15] NTSB, Marine Accident Report NTSB/MAR-13/01, liftboat Trinity II, ntsb.gov. [16] NTSB, Marine Accident Brief MAB-20/36, liftboat Kristin Faye, ntsb.gov. [17] NTSB, Marine Investigation Report MIR-23-28, liftboat L/B Robert, ntsb.gov. [18] Borr Drilling Limited, "Borr Drilling Limited - Prospector 5 Rig Incident", press release, Hamilton, Bermuda, 25 October 2026, distributed by PR Newswire, read 4 November 2026, prnewswire.com; copy at placera.se. Questions: support@aceengineer.com · AceEngineer · © 2026 AceEngineer · 11511 Piping Rock Dr., Houston, TX 77077 Deckhand: Make Engineering Enjoyable Again ## Engineering evolution with AI (Deckhand newsletter, issue 2, Main Street) URL: https://www.aceengineer.com/newsletter/issue-002-main-street/ Description: What AI has taken in law, radiology, customer support and coding, and a good and a bad scenario for engineering. The Deckhand newsletter · Issue 2 · Main Street # Engineering evolution with AI In law, radiology, customer support and coding, AI takes the first-pass work and a named person still signs. On 15 public simulation problems, the best AI agent came within 10 % of the known answer on one. Prepared: Analyst Deckhand (AI assistant) · Checked: Editor Deckhand · Approved: Vamsee Achanta · 3 November 2026 In FEABench, a test of AI agents on physics problems in a commercial simulation tool, 88 % of the best agent's commands to the solver ran, yet only one of 15 problems with known correct answers was solved within 10 %, and the authors doubt even that one (Google Research and Harvard, April 2025). NCEES, the US body that sets the engineering licensing exams, says the licensed engineer keeps responsibility and must check AI output independently (Position Statement 6.10, 2025). AI takes the drafting, searching and first-pass work. People keep the decision wherever a court, a regulator or a signature holds a named person to account. Our hypothesis: AI has cooked coding, and it is now cooking many other areas, such as finance and legal. In each of them, AI has democratised the work, so that more people can now do it. Engineering will be democratised in the same way: with a basic understanding, anyone will be able to take on engineering problems. The future of the engineer then lies in engineering judgement. The question is whether engineering is pretty much cooked. We test it here, on the Deckhand journey, our series that takes real-world cases, builds the engineering behind them and gives it to the industry to reuse and build on. On today's evidence, engineering work still needs the engineer. This article sets out that evidence, field by field, then two ways it could go for engineering. They are scenarios to argue about. ## Law, radiology and customer support In law, AI drafts and searches, but lawyers must review its output before relying on it (American Bar Association, Formal Opinion 512, July 2024). A public database lists 2,231 court decisions involving AI-invented content, 880 of them involving lawyers (Charlotin, 28 October 2026). The lawyer signs the filing. In 2016, Geoffrey Hinton predicted that radiologists would be replaced. Today 76.2 % of the AI-enabled devices on the US Food and Drug Administration list are for radiology (Complizen count, September 2026), yet US radiologist numbers have grown about 10 % over the past ten years (Fortune, May 2026). The physician still signs the report. In customer support, Klarna said in 2024 that its AI assistant did the work of 700 agents (Klarna, February 2024). In May 2025, Klarna's chief executive cited lower quality and the company began hiring people again (Bloomberg, via Entrepreneur, May 2025). ## Coding: jobs, AI use, speed and code review Coding is where AI arrived first and where the change is loudest. US tech companies cut more than 191,000 jobs in 2023, about 127,000 in 2025 and at least 94,046 from January to August 2026 (Crunchbase, October 2026). The reason given has changed. AI was cited in 33 % of tech layoff events in 2026, up from 1 % in 2024 (Layoffs.fyi, via Crunchbase News, September 2026). Figure 1. US tech jobs cut each year, 2022 to August 2026 Crunchbase count of US-based tech companies (tracker updated 28 October 2026; 2026 to August from Crunchbase News, 25 September 2026). 2022 and 2023 are given as "more than", 2025 as "around". Data: fig1-us-tech-layoffs.csv. Use is now near universal, and trust is not. In Google's DORA (DevOps Research and Assessment) survey of nearly 5,000 technology professionals, 90 % use AI at work and 30 % have little or no trust in the code it writes (Google Cloud, September 2025). In the Stack Overflow survey, 84 % of developers use or plan to use AI tools; 45.7 % distrust its accuracy and 32.7 % trust it (Stack Overflow, July 2025). The speed gain depends on who measures it. On one simple lab task, developers with an AI assistant finished 55.8 % faster (Peng and others, February 2023). Across three company field experiments, developers completed 26 % more tasks, with the largest gains for less experienced staff (Cui and others, 2025). In a randomised trial, experienced open-source developers took 19 % longer with AI while believing they were about 20 % faster (METR, Model Evaluation and Threat Research, a non-profit research group, July 2025). Figure 2. Measured and believed change in developer speed with AI, by study Measures differ by study: time on one set task (lab), tasks completed (field), time on real tasks (randomised trial). The diamond is what the trial's developers believed. Sources: Peng and others 2023; Cui and others 2025; METR 2025. Data: fig2-ai-coding-speed.csv. Review is still the bottleneck. In over 456,000 GitHub pull requests, a pull request being a proposed code change, people merged 76.8 % of human changes but 38 % to 65 % of those from five coding agents (Li and others, July 2025). The jobs picture is upheaval, not collapse. US software postings rose almost 15 % from February 2025 to June 2026 while all postings fell about 7 %, yet they remain about 27.5 % below February 2020 (Indeed Hiring Lab, July 2026). The US Bureau of Labor Statistics (BLS) splits the outlook by task, not by field. It projects jobs for computer programmers to fall 7 % from 2025 to 2035, and jobs for software developers, quality assurance analysts and testers to grow 10 % (Figure 3). Figure 3. US employment projections for 2025 to 2035 split by task, not by field US Bureau of Labor Statistics, Occupational Outlook Handbook, pages modified 27 August 2026. The BLS cites AI automation for computer programmers. Data: fig3-us-job-projections.csv. ## What AI takes and who still signs, by field Field What AI takes Who still signs Evidence Law Drafting and search The lawyer, on the filing 880 court decisions on lawyers' AI-invented content Radiology Image screening The physician, on the report Radiologists up about 10 % in ten years Customer support First-line chats A person, again, after a quality drop Klarna rehired in 2025 Coding Writing and changing code The reviewer who merges the change Agent changes merged less often than human ones Engineering Set-up, runs, first drafts The licensed engineer, on the seal See below ## Engineering: the evidence so far On today's evidence, engineering is not cooked, for three reasons. Results on problems with known answers. FEABench, at the top of this article, shows that code that runs is not the same as a right answer. Its 15 problems and their target values are public as FEABench Gold (Google Research on GitHub, Apache 2.0 licence, retrieved 29 October 2026); details are in Reusable prompts at the end. EngDesign, a set of 101 engineering design tasks, saw the best model pass about a third (NeurIPS conference, 2025). Both used 2024 to 2025 models, so we keep measuring. Codes and the seal. NCEES Position Statement 6.10, at the top of this article, keeps responsibility with the licensed engineer. The North Carolina board adds that the engineer must be "capable of reproducing the output independently from any AI program" (July 2025). The BLS notes that a licensed Professional Engineer (P.E.) may approve design plans and sign off on projects, and it projects civil engineering jobs to grow 6 % from 2025 to 2035 (BLS, Civil Engineers, August 2026). Poor data. Project data such as metocean (wind, wave and current) records, vessel motions and soil data is often scarce, or held by the client or under confidentiality terms. Training data that does not represent the real case is one of the named challenges for machine-learning models in structural engineering (Zaker Esteghamati and others, April 2024). In NSPE Case 24-2, putting a client's information into an open AI tool without the client's permission was found unethical. A model trained on cases unlike the project, and not given the project's own site data, cannot check a design against that site, so finding and judging that data stays with the engineer. Our own team is one case. Its members include AI assistants, such as the Analyst Deckhand and the Editor Deckhand named at the top; they prepare and queue solver runs, check each other's work and draft reports. The analysts do the heavy specialist work, thus providing resource for the engineer to review; the engineer sets the method and the acceptance criteria, judges the results and signs. This article is one example. Vamsee Achanta set its question. The assistants found the sources, checked each figure against its source, built the charts and drafted the text. He reviewed the drafts, changed the title and approves the article. That first pass is where young engineers have always learned. Across the wider economy, the first rung is narrowing. In payroll data, employment for workers aged 22 to 25 in the most AI-exposed jobs is 19 % below where it would be had it kept pace with less-exposed peers (Stanford, August 2026). Only 4.5 % of Indeed US software postings in the first quarter of 2026 were entry level (Indeed Hiring Lab, July 2026). ## Two scenarios for engineering The other professions show two paths, and engineering could take either. Each step below is drawn from something already seen in another field. The scenarios are ours, to argue about. Both pathsGood pathBad path Good path: engineers who check Bad path: output nobody can check First-pass work AI drafts, sets up and runs; engineers check more options per study. Drawn from: Radiology: 76.2 % of AI devices, radiologists up about 10 %. Firms cut the people who did the first pass, then quality drops. Drawn from: Customer support: Klarna's 700 agents, then rehiring in 2025. The entry rung Juniors learn by checking AI first passes against hand calculations. Drawn from: Field experiments: largest gains for less experienced staff. Entry hiring dries up, so few people learn to check. Drawn from: Software: 4.5 % of postings entry level; ages 22 to 25 down 19 %. The seal The named engineer checks and can reproduce the work. Drawn from: NCEES 6.10 and the North Carolina board require independent checks. Plans are sealed after a cursory look at AI output. Drawn from: NSPE Case 24-2, where the Board found it unethical to seal AI-drafted plans after a cursory review; 880 court decisions on lawyers' AI-invented content. Right answers Problems with known answers become the routine check. Drawn from: FEABench Gold: 15 public problems with target values. Code that runs is taken as a right answer. Drawn from: FEABench: 88 % of commands ran, 1 of 15 within 10 %. Speed Measured gains go into harder problems and more checking. Drawn from: Field study: 26 % more tasks completed. Felt speed replaces measured speed; delivery stability (how often changes fail and must be fixed) slips. Drawn from: METR: 19 % slower while feeling 20 % faster; DORA 2025: lower delivery stability with AI use. Figure 4. Two scenarios for engineering, each step drawn from something that has already happened in another profession Our scenarios. Each "Drawn from" line names a source in the list at the end. The difference between the two paths is who learns to check. In the good path, the first pass becomes training. In the bad path, it becomes a gap that shows only when the senior engineers retire. The models change too. Each new model may do more of the engineering well, as advances in mathematics and physics are taken into the main model through further training. Engineering that once had to be written out for a model then becomes something it knows unaided. In our own work, the code once had to spell out the catenary equation for a hanging line; a frontier model (one of the most capable AI models of the day) now knows that equation without being given it. Figure 5 shows this direction in three stages. In the good path above, the check stays with the engineer at every stage. Illustration of a direction, not measured data Stage 1: Written out in your own code. The engineer's files spell out the method and its equations.Stage 1Written out in your own codeStage 2: Given to the model in files. The model knows the method; the design code's edition and clauses, and the firm's own choices, come from files.Stage 2Given to the model in filesStage 3: Known to the model unaided. The model knows the method itself; the engineer still checks it against a known answer.Stage 3Known to the model unaided Next model generation: further training may take in more mathematics and physics.Next model generation: further training may take in more mathematics and physics. Each new model generation may take in more mathematics and physics through further training Example: the catenary equation for a hanging line. Our code once had to spell it out; a frontier model now knows it unaided (from our own work). once written out in our code now known to a frontier model Example: the catenary equation (hanging line) In the good path of Figure 4, the engineer checks the work against a known answer and signs it at every stage. Good path, at every stage: the engineer checks against a known answer, and signs Figure 5. How the next model may take in engineering: an illustration of a direction, not measured data Stages are in order only. The catenary example is from our own work. Hover a stage or the example for detail. AI does the first-pass work that once trained engineers thus democratizing engineering. If so, engineers likely will evolve the judgement part. ## Sources American Bar Association, Formal Opinion 512, "Generative Artificial Intelligence Tools", 29 July 2024. https://www.americanbar.org/content/dam/aba/administrative/professional_responsibility/ethics-opinions/aba-formal-opinion-512.pdf Brynjolfsson, Chandar and Chen, "Canaries in the Coal Mine? Six Facts about the Recent Employment Effects of AI", Stanford Digital Economy Lab, revised 12 August 2026. https://digitaleconomy.stanford.edu/publications/canaries-in-the-coal-mine Charlotin, AI Hallucination Cases database, updated 28 October 2026. https://www.damiencharlotin.com/hallucinations/ Complizen, "FDA has cleared 1,614 AI medical devices", count of the FDA AI-enabled device list, September 2026. https://www.complizen.ai/post/fda-has-cleared-1614-ai-medical-devices Crunchbase News, "The Crunchbase Tech Layoffs Tracker", US-based tech companies, updated 28 October 2026. https://news.crunchbase.com/startups/tech-layoffs/ Crunchbase News (Azevedo), "Tech Layoffs Outpace 2025 As Big Companies Shift Spending To AI", citing Layoffs.fyi, 25 September 2026. https://news.crunchbase.com/?p=94113 Cui, Demirer, Jaffe, Musolff, Peng and Salz, "The Effects of Generative AI on High-Skilled Work", Management Science, 2025. https://pubsonline.informs.org/doi/10.1287/mnsc.2025.00535 Entrepreneur, citing a Bloomberg interview, "Klarna is hiring customer service agents after AI couldn't cut it", May 2025. https://www.entrepreneur.com/business-news/klarna-ceo-reverses-course-by-hiring-more-humans-not-ai/491396 Fortune, on Geoffrey Hinton's 2016 radiology prediction, 4 May 2026. https://fortune.com/article/ai-godfather-radiologists-obsolete-salaries-up-to-571k-demand-growing/ Google Cloud, "Announcing the 2025 DORA Report", 23 September 2025. https://cloud.google.com/blog/products/ai-machine-learning/announcing-the-2025-dora-report Google Research, FEABench code and data release (FEABench Gold, 15 problems), Apache 2.0 licence, last updated 7 May 2025, retrieved 29 October 2026. https://github.com/google/feabench Guo and others, "Toward Engineering AGI: Benchmarking the Engineering Design Capabilities of LLMs" (EngDesign), NeurIPS 2025. https://arxiv.org/abs/2509.16204 Indeed Hiring Lab (Gallacher), "AI and Job Postings: From Destruction to Creation?", 8 July 2026. https://hiringlab.indeed.com/2026/07/08/ai-and-job-postings-from-destruction-to-creation/ Indeed Hiring Lab, "The Labor Market Is Tilting Toward Seniority", 23 July 2026. https://hiringlab.indeed.com/2026/07/23/the-labor-market-is-tilting-toward-seniority/ Klarna, press release on its AI assistant, 27 February 2024. https://www.klarna.com/international/press/klarna-ai-assistant-handles-two-thirds-of-customer-service-chats-in-its-first-month/ Li, Zhang and Hassan, "The Rise of AI Teammates in Software Engineering (SE) 3.0", Table 5, 20 July 2025. https://arxiv.org/abs/2507.15003 METR, "Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity", 10 July 2025. https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/ Mudur and others (Google Research, Harvard), "FEABench: Evaluating Language Models on Multiphysics Reasoning Ability", 8 April 2025. https://arxiv.org/abs/2504.06260 NCEES, Position Statement 6.10, "Responsible Use of AI in Engineering and Surveying", 2025, as circulated by the Idaho licensing board, 23 January 2026. https://dopl.idaho.gov/wp-content/uploads/2026/01/IPELS-AI-Statement.pdf North Carolina Board of Examiners for Engineers and Surveyors, "Guidelines on the Use of AI in Engineering and Surveying Services", 16 July 2025. https://www.ncbels.org/wp-content/uploads/2025/07/Guidelines-on-the-Use-of-Artificial-Intelligence-in-Engineering-and-Surveying-Services-FINAL.pdf NSPE Board of Ethical Review, Case 24-2, "Use of AI in Engineering Practice". https://www.nspe.org/sites/default/files/24-2-Artificial-Intelligence-in-Engineering-Practice.pdf Peng, Kalliamvakou, Cihon and Demirer, "The Impact of AI on Developer Productivity: Evidence from GitHub Copilot", February 2023. https://arxiv.org/abs/2302.06590 Stack Overflow, Developer Survey 2025, AI section, July 2025. https://survey.stackoverflow.co/2025/ai US Bureau of Labor Statistics, Occupational Outlook Handbook: Civil Engineers, modified 27 August 2026. https://www.bls.gov/ooh/architecture-and-engineering/civil-engineers.htm US Bureau of Labor Statistics, Occupational Outlook Handbook: Computer Programmers, modified 27 August 2026. https://www.bls.gov/ooh/computer-and-information-technology/computer-programmers.htm US Bureau of Labor Statistics, Occupational Outlook Handbook: Software Developers, Quality Assurance Analysts and Testers, modified 27 August 2026. https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm Zaker Esteghamati, Bean, Burton and Naser, "Beyond development: Challenges in deploying machine learning models for structural engineering applications", 18 April 2024. https://arxiv.org/abs/2404.12544 ## Reusable prompts From the sources listed above, compare who does the first pass and who still signs in law, radiology, customer support and coding; test the engineering case against FEABench Gold and the licensing boards' statements; and write a short article that states the hypothesis, with the charts and the two scenarios shown here. Data: the public data set for this article is FEABench Gold. It holds 15 physics and engineering simulation problems, each with its target quantity, units, a plain-language model specification and the reference solution code for a commercial multiphysics solver. It is the set behind the "one of 15" result above. Source: Google Research, in the FEABench code and data release on GitHub (https://github.com/google/feabench, file data/benchmark.zip). Public status: public, Apache 2.0 licence. Date: last updated 7 May 2025; retrieved 29 October 2026. A reader can pose any of the 15 problems to the tool of their choice and compare its answer with the target value. The numbers behind Figures 1 to 3 are in the CSV files named under each figure. Readers are welcome to share their own results with the FEABench Gold problems, or data that would improve this comparison, at support@aceengineer.com. Questions: support@aceengineer.com · AceEngineer · © 2026 AceEngineer · 11511 Piping Rock Dr., Houston, TX 77077 Deckhand: Make Engineering Enjoyable Again ## Gulf of Mexico well permits by rig type: a public US data file (Deckhand newsletter, issue 2) URL: https://www.aceengineer.com/newsletter/issue-002-public-data/ Description: Counts from a raw data file of the US Bureau of Safety and Environmental Enforcement (BSEE): new-well permits in the US Gulf of Mexico by rig type, 2005 to 2026, with water depths. The Deckhand newsletter · Issue 2 · Public data # Gulf of Mexico well permits by rig type: a public US data file Prepared: Analyst Deckhand (AI assistant) · Checked: Editor Deckhand · Approved: Vamsee Achanta · 3 November 2026 In 2005, 234 of the 322 permits to drill a new well in US federal waters of the Gulf of Mexico named a jack-up rig and 15 a drillship (Application for Permit to Drill raw data of the US Bureau of Safety and Environmental Enforcement, BSEE). In 2025, 44 of the 47 named a drillship and 1 a jack-up. The BSEE Data Center is the bureau's public data service. This page counts the records in one of its raw data files, the Application for Permit to Drill file, and sets out what it holds. The file is listed as updated daily. The counts here are from the file of 2 November 2026. ## Well permits by rig type The permit file holds each application for a permit to drill in US federal waters. Each record gives the permit type, the requested spud date (the date drilling is to start), the water depth, the rig name and the rig type. Here each well is counted once, at its first New Well permit in the Gulf of Mexico region. It is counted in the year of its requested spud date, with the rig type that permit names. From 2005 to 2026, 2,895 wells are counted this way. The rule leaves out each well's later permits, and the 10 wells whose first New Well permit gives no requested spud date. The year 2026 runs only to the file of 2 November 2026; later files can differ, because BSEE updates the files daily. The counting script names six rig types: jack-up, drillship, semisubmersible, DP semisubmersible (dynamically positioned, held on station by its thrusters), platform rig and submersible. Barge, barge rig and well intervention vessel (19 permits) are grouped as other. Figure 1 shows the new-well permits each year by rig type. Figure 1 - New-well permits by rig type, Gulf of Mexico, 2005 to 2026, by year of requested spud date. One permit per well. 2026 runs to the file of 2 November 2026. Source: BSEE Application for Permit to Drill raw data. Data: fig-p1-new-well-permits-by-rig-type.csv. Every permit counted records a water depth. Table 1 gives the permits of each rig type from 2005 to 2026 with the water depths they record. Rig type New-well permits, 2005 to 2026 (-) Median water depth, ft (m) Water depth range (ft) Jack-up 1,333 101 (31) 9 to 395 Drillship 758 5,187 (1,581) 1,296 to 9,808 Semisubmersible 282 3,233 (985) 407 to 9,356 DP semisubmersible 260 5,263.5^(a) (1,604) 470 to 10,139 Platform rig 162 392 (119) 11 to 4,428 Submersible 81 40 (12) 12 to 72 Other 19 12 (4) 10 to 5,422 All 2,895 Table 1 - New-well permits and water depths by rig type, Gulf of Mexico, 2005 to 2026. Source: BSEE Application for Permit to Drill raw data, file of 2 November 2026. a. The 260 permits are an even number, so the median is the mean of the two middle water depths. Each count here takes the rig type named in a well's first permit. This page leaves open how often a different type of rig drilled the well. ## Reusable prompts Recount the new-well permits by rig type from the BSEE Application for Permit to Drill raw data file, and redraw Figure 1 and Table 1. Data: the public data set for this page is one file from the BSEE Data Center raw data page (US Department of the Interior). It is US federal government data, listed as updated daily and dated 2 November 2026 on that page, and was downloaded on 3 November 2026. Application for Permit to Drill, APDRawData.zip, SHA-256 b4ab66063de5a95c78d0e4d33d220ea806ef07f114bd2add6efa9e8561d299c0: permits with permit type, requested spud date, water depth, rig name and rig type. Code: the counting script on GitHub (worldenergydata, examples/bsee/rawdata_fact_check). It applies the counting rule above and prints the counts; its README sets out the rule and the values to check against. Readers are welcome to share their own counts at support@aceengineer.com. Questions: support@aceengineer.com · AceEngineer · © 2026 AceEngineer · 11511 Piping Rock Dr., Houston, TX 77077 Deckhand: Make Engineering Enjoyable Again ## One place to work | AceEngineer URL: https://www.aceengineer.com/newsletter/topics/one-place-to-work/ Description: We now use AI assistants for many tasks: in a chat window or an app, on a phone, and on personal and work computers. # One place to work Summary: We now use AI assistants for many tasks: in a chat window or an app, on a phone, and on personal and work computers. AI assistants use language models that do not always give the same answer. We are running into the familiar territory of "the answer can change from one run to the next, and with the wording of the question." When we dealt with IT and programmers, many a times, we faced a related frustration: "oh.. but it works on my machine." This answer was so familiar for administrative tasks such as opening a Microsoft word file or crash). Equally, the same experience when we ran a script not able to run let alone getting same result. We now meet a similar problem in everyday AI use: one person gets a result that another cannot repeat. One of the solutions is to keep each job in one folder, with its files, its tools, its prompts and its record of changes. Let your AI assistant work through this created set environment. The AI assistants we use keep a record of each session. To check a result, or run it again, you need its prompt, its inputs and that record. So the home for this data matters. The article shows how this grows from one engineer to a team and then to the company. In our experience, it takes a few (> 10-20) reasonably sized sessions to realize these benefits; we have not measured this. Treating AI assistants as loyal team members who need help will get us a long way. Similar to training your employee team, training this single work storage place will make immense difference. Engineering work often lives in many places: e-mail attachments, personal and shared drives, chat threads, and spreadsheets or scripts on one engineer's laptop. Each copy changes on its own. The risk is a result that goes out from an out-of-date input, and nobody can say which input was used. AI assistants make this more important. Answers can differ from one run to the next. Keep the prompt, the inputs and the assistant's record in the job folder, with the result. Some AI assistants can now change files, not only read them; this article calls them AI agents. An agent can only work on the files it can read, and it can change those files. So the questions are: where are the files, what may the agent touch, and how do you see what it did? ## What "one place" means One place is one folder for each job. The folder holds the job's files and tools, its prompts and the assistant's records, and its record of changes. You ask your AI assistant from the chat or tool you already use, and it works only in that folder. The result comes back to you, and the change goes into the folder's record. Three layers keep this under control: Data. The agent reads only the files in the job's scope: the folders it is allowed to see. Other files are not visible to it. Execution. One harness: the same tools, the same instructions and the same guardrails for every job. Guardrails are fixed limits: the agent cannot delete files or overwrite history. It proposes each change for a person to review, and every action goes into a log (an audit trail). Results. The result comes back to the place where you asked, with a record of what changed and why. At level 1 you set most of this up yourself. Open the AI tool only in the job folder, and review each change before you keep it. At levels 2 and 3, the system's permissions enforce the limits, not the instructions to the AI. ## The ladder One person. You keep each job in one folder, with one set of tools and one instruction file for your AI assistant. The instruction file is a short text note: what the job is, the units, the design code and edition, and how to rerun the calculation. Start on public material, such as a textbook example, while you learn how the assistant behaves. Keep client data out of the AI tool until your firm allows it. The team. The team shares one place, with one scope for each job. The calculation tools and checklists sit in the shared harness, so each new job starts from the team's best version. When a checklist is corrected, the team keeps one copy. The reviewer sees each proposed change before it is accepted. The organisation. The same place sits inside the organisation's own chat or workspace, and uses the staff's existing sign-ins. Each project has one scope and one audit trail. The system's permissions enforce the guardrails. Outside partners work in a separate place, with their own scope. You can start at level 1 on your own. Levels 2 and 3 need the team or the company to agree, and the company's IT and security staff to approve. ## Old way against one place Step Old way (in our experience) One place Where the files are E-mail, personal and shared drives, chat One folder for each job What an AI tool can see Whatever file someone pastes in Only the files in the job's scope How a change is made Someone edits a copy The agent proposes a change; a person reviews it How a reviewer finds the input Asks, then searches Reads the folder's record of changes How a new engineer starts Copies files from a colleague Uses the same place and harness from the first day ## For a small company A small company does not need a large platform for this. Start with the work the team repeats: a calculation package, a quote, a drawing set, a test report. Turn one of these into a small tool, for example a spreadsheet template or a short script that builds the package from one input file. Run it on your own computer, with the software and data you already have. Put the tool, its inputs and its record in one place. We work this way ourselves. Our engineering code, scripts and AI-agent instructions are in repositories: folders that keep every version. Our agents' changes arrive as pull requests (proposed changes), and they are reviewed before they are merged. ## An example (invented for this article) A small engineering firm does beam and frame checks. The firm and its people are invented for this example. Level 1: one engineer keeps each job in one folder, with her check spreadsheet, a record of changes and an instruction file. She opens her AI assistant only in that folder and reviews each change it proposes. Level 2: the firm's three engineers share one place, with one scope for each job. A second engineer asks the assistant to rerun her check, and reviews the result. Level 3: the firm adds a second team. Each project gets its own scope and audit trail. A partner firm works on one project, in a separate place. ## What this does not show This article gives no measured time saving. Setting up the place takes effort, and habits take time to change. Some files must stay where they are: files under document control, and files in the client's own system. List them in the job folder with their location, and do not move them. ## Try it Monday Choose one current job, and check your firm's rules on copying its files. Make one folder with four sub-folders: inputs, calculations, results and report. Copy your own working files for that job into the folder. From now on, work on this job only from this folder. List the files that must stay elsewhere, and where they are. Start a change log: a text file with one line for each new result and its input. Write an instruction file: the job, the units, the design code and how to rerun it. Before you open an AI tool on the folder, check that your firm allows it. How this article was made: an AI assistant drafted it from the author's material and his description. Vamsee Achanta, P.E., AceEngineer: https://www.aceengineer.com/about.html If you want help with any work (automation, AI automation or workflows), let us know: support@aceengineer.com. Read issue 1 of The Deckhand Chronicles, Energy Street edition. ## Why the model you use matters: test each new AI model on your own problems URL: https://www.aceengineer.com/newsletter/topics/why-the-model-you-use-matters/ Description: A newer AI model can solve problems that an older one may get confidently wrong. Test each new model on problems you know. # Why the model you use matters In my experience, an older model often does not say "I cannot solve this". It gives an answer that looks correct. Our hypothesis: AI models improve in steps. A new model can solve problems that the model before it could not. ## Frontier and behind A frontier model is one of the most capable AI models available on a given date. A model one or two releases behind may cost less or respond faster for some workloads. Cost and speed depend on the models, workload and current pricing. Test whether the cheaper model meets your task's requirements, even for a summary, format change or first draft of a letter. In my experience, the difference shows on problems where a common simplification is wrong, or where the problem is too large for the model. The model then often takes a shortcut and does not say so. A small gain can be a step change. Suppose many of your problems sit just beyond what a model two releases behind can do. Suppose, too, that a newer model scores only 1 to 2 % higher on public benchmarks (a hypothetical figure). It could then solve a whole group of your problems that the older model got wrong. For that group, the result is not 1 to 2 % better: it is a right answer in place of a wrong one. The schematic shows the idea; it is not a measurement. A small capability gain can be a step change (illustrative schematic, not data, not to scale) Illustrative schematic with no measured values. The share of your problems a model solves correctly rises steeply where many of your problems sit just beyond what models can do. Two close vertical lines mark a model two releases behind and a frontier model, a hypothetical 1 to 2 % apart in capability; across that small gap the share of your problems solved jumps from low to high. A small capability gain can be a step change Illustrative schematic, not data and not to scale where many of your problems sit (difficulty) step change step change in problems solved model two releases behind frontier model say, 1 to 2 % apart (hypothetical) Model capability on general tests (illustrative) Share of your problems solved (illustrative) Illustrative schematic, not data and not to scale. When many of your problems sit near the edge of what models can do, a small gain in capability can move a whole group of them from wrong to right. ## A share of your problems, area by area One way to think about a model: in each area of your work, it solves some share of your real problems correctly. Structural checks are one area. Report writing is another. A newer model can raise that share. Public league tables (benchmarks) test general problems, not yours. You can only find the share for your own work by testing the model on your own problems. In my experience, our code once had to spell out the catenary equation for a hanging line. A frontier model now knows that equation without being given it. Our hypothesis: a newer model may also take on more engineering itself, as more mathematics and physics are trained into it. Engineering that once had to be written out for a model then becomes something it knows unaided. The illustration shows this direction in three stages. Where the engineer keeps the check, the work is checked against a known answer at every stage and then signed. A problem set with known answers, described below, is that check. How the next model may take in engineering (illustration of a direction, not measured data) Illustration: engineering moves from the engineer's own code, to files given to the model, to knowledge inside the model, as each new model may take in more through further training; where the engineer keeps the check, the engineer checks at every stage. Example: the catenary equation, once written out in our code, now known to a frontier model. Illustration of a direction, not measured data Stage 1: Written out in your own code. The engineer's files spell out the method and its equations.Stage 1Written out in your owncode Stage 2: Given to the model in files. The model knows the method; the design code's edition and clauses, and the firm's own choices, come from files.Stage 2Given to the model infiles Stage 3: Known to the model unaided. The model knows the method itself; the engineer still checks it against a known answer.Stage 3Known to the modelunaided Next model generation: further training may take in more mathematics and physics (our hypothesis). Next model generation: further training may take in more mathematics and physics (our hypothesis). Each new model generation may take in more mathematics and physics through further training Example: the catenary equation for a hanging line. Our code once had to spell it out; a frontier model now knows it unaided (the author's experience). once written out in our code now known to a frontier model Example: the catenary equation (hanging line) Where the engineer keeps the check, the work is checked against a known answer and signed at every stage. Where the engineer keeps the check, at every stage: checks against a known answer, and signs How the next model may take in engineering: an illustration of a direction, not measured data (note 1). Stages are in order only. The catenary example is the author's experience. Hover a stage or the example for detail. Note 1. Three frontier labs state that, depending on the user's settings, conversations in their consumer apps may be used to improve their models (OpenAI, Google and Anthropic; see Sources). Our hypothesis: frontier labs keep gaining user workload and research data, so each next model improves most where that work concentrates. ## A worked example: a confident shortcut This example is an illustration of the kind of error, not a test result. It is invented for this article, uses textbook theory, and contains no client work. The problem: find the first sloshing frequency of a rectangular tank, 1.0 m long, filled to 0.15 m. The full linear-theory answer (small motions) includes the fill depth. For the first mode of a two-dimensional rectangular tank: L = 1.0 m tank length in the direction of sloshing h = 0.15 m fill depth g = 9.81 m/s^2 gravity k = pi / L = 3.14 per m (wave number of the first mode) tanh(k h) = tanh(0.471) = 0.439 (hyperbolic tangent; it tends to 1 for a deep fill) w^2 = g k tanh(k h) -> w = 3.68 rad/s (w: angular frequency) f = w / (2 pi) = 0.586 Hz A shortcut drops the tanh term. That form is for deep liquid: w^2 = g k -> w = 5.55 rad/s, f = 0.884 Hz The shortcut answer is about 51 % too high. It looks plausible: it has the right units, a clean formula and a confident tone. At a deep fill the two forms almost agree: at 0.70 m fill the difference is about 1 %. A check at a deep fill does not find the error. Only a check at the shallow fill shows it. A frontier model can make the same mistake. In my experience it does so less often, and it more often states the assumption it made. ## Frontier model against a model two releases behind Table 1 is illustrative. It sets the worked example above beside the author's experience; it is not a measured test, and it names no model or vendor. The cost row is our hypothesis. Table 1. Frontier model against a model two releases behind (illustrative, not a measured test) No. What to compare Frontier model Model two releases behind (N-2) Source 1 Worked example: formula in the answer Full answer, with tanh(k h) Shortcut, without tanh(k h) Worked example above (illustrative) 2 Worked example: first sloshing frequency, f (Hz) 0.586 0.884 Worked example above (illustrative) 3 Worked example: error against the full answer (%) 0 +51 Worked example above (illustrative) 4 Confident but wrong answers Less often More often Author's experience 5 States the assumption it made More often Often does not say it took a shortcut Author's experience 6 Cost per task May be a bit more May be less Our hypothesis 7 Checking and rework Fewer wrong answers to find More answers to find and redo Author's experience Cost and speed depend on the models, the workload and current pricing. Either model can make the shortcut in the worked example; Table 1 shows which answer is more likely, in the author's experience. ## Model, provider and harness: the paths a typical user takes The same comparison applies to the provider. A model reaches you through a harness: the software around the model. The harness sets the model's instructions and the tools it may use, such as reading files, running code or searching. It also sets how much text the model keeps in view and how long it may work on a step. The same model can sit in a different harness at each provider. Our hypothesis: on the same model, a weak harness can leave you the equivalent of two releases behind. Table 2 lists the paths a typical user goes through, and what to check on each with your problem set. Table 2. Typical paths to a model, and what to check on each No. Path What you get What to check with your problem set 1 The model maker's own app or assistant, on its newest model The model in the harness its maker built for it Use it as the reference for the other paths 2 The same model through another provider: a cloud platform, an editor plug-in or a company chat tool The same model; its instructions, tools, text kept in view and working time may differ Run the same problems on both; a difference comes from the harness 3 A default or automatic choice: a free plan, a company default or an "auto" setting A model chosen for you, which may be older or smaller Which model answered, then the same problems 4 An older model kept on purpose, for cost, an approval or a fixed workflow Known behaviour, which may cost less The same problems at each new release 5 A small, fast, low-cost model Quick answers at a low cost per task Whether it passes the problems for this task 6 An open-weight model (its trained parameters are published), run on your own machines Your data stays in-house; capability depends on the model and on the harness you build The same problems, as for any provider Note to Table 2. The rows are the author's list of common paths; each check uses your own problem set (see "Keep your future problem sets"). The table is guidance, not a measured comparison, and names no model or vendor. Match the model to the task ("horses for courses"). A small, fast, low-cost model can sometimes do the same job as a frontier model. Examples are the summary, format change and first letter draft named under "Frontier and behind". Your problem set shows which path and which model suits each task. ## Cost, speed and checking A frontier model may cost more per task or run more slowly for a given workload. Compare the available models using that workload and the current pricing. Capability alone does not determine cost, speed or suitability. A frontier model is still not always right. Check every answer that a decision depends on. Check the inputs and the units. Then check one case where you know the answer and where a shortcut would break: here, the shallow fill. If you know the full formula, or have the textbook open, the hand check above takes a few minutes. ## Conclusion: cost and the long term Treat your AI workspace like a group of employees you are training. In my experience, a frontier model returns fewer wrong answers to find and redo. Our hypothesis: a frontier model may cost a bit more per task; depending on the situation it costs more in the long run or pays back over the long term, and using a model that is behind compromises the training of your workspace. Your problem set shows whether it pays back for your work. ## Keep your future problem sets Keep your future problem sets: the problems you would most like a model to solve. They are your dreams for your work. Dream big. When you get access to a new model, run the set on the first day. Compare each answer with the known answer, or check it the way you planned. Keep some money or spare usage ready for this test. When a dream is not realised with this model, keep it for the next one. Raise the complexity of the set step by step as each model solves more. There is always a second route: break the problem down. With more time spent splitting a problem into smaller steps, each with a known answer, today's model may solve it. The other route is to wait for the next frontier model. Balance the effort now against the work later, by what is needed now. The set shows you, on your own work, what the new model can now do. It also shows which checks you must still do by hand. The worked example was recomputed independently before publication. Prepared: Analyst Deckhand (AI assistant) · Checked: Editor Deckhand · Approved: Vamsee Achanta · 4 November 2026 ## Sources Faltinsen, O. M. and Timokha, A. N., Sloshing, Cambridge University Press, 2009, section to be confirmed: first-mode natural frequency of a rectangular tank, linear potential-flow theory. OpenAI, "Data controls in ChatGPT", OpenAI Help Center: https://help.openai.com/en/articles/7730893-data-controls-in-chatgpt, retrieved 4 November 2026 (note 1). Google, "Gemini Apps Privacy Hub", Gemini Apps Help: https://support.google.com/gemini/answer/13594961, retrieved 4 November 2026 (note 1). Anthropic, "Updates to Consumer Terms and Privacy Policy", 28 August 2025: https://www.anthropic.com/news/updates-to-our-consumer-terms, retrieved 4 November 2026 (note 1). ## Appendix A. Reusable prompts Prompt: "Here is my problem set, one problem per line, each with its known answer or the check I will apply. Solve each problem and state every assumption you make. Mark each problem you cannot solve, or solve only by a simplification, and name the simplification." Run the same prompt and set on each new model and each provider you use. Compare the answers with the known answers. Data set: your own problem set; the worked example uses the textbook in Sources. About the author: https://www.aceengineer.com/about.html For help with automation, AI automation or workflows, use the contact page: https://www.aceengineer.com/contact.html Read issue 1 of The Deckhand Chronicles, Energy Street edition. ## AceEngineer — FOWT Mooring Screening (OC4-DeepCwind Worked Example) URL: https://www.aceengineer.com/outreach/fowt-mooring-screening.html Description: Worked example of a floating offshore wind mooring screening deliverable at pre-FEED stage, with the scope boundaries stated up front. AceEngineer — Floating Offshore Wind # FOWT Mooring Screening — Worked Example OC4-DeepCwind semi-sub reference, catenary 3-line concept Screening-tier deliverable, not certification-grade Pre-FEED / early-FEED mooring screening · OC4-DeepCwind public reference ## Scope and Boundary This worked example shows the shape of an ACE FOWT mooring screening deliverable at pre-FEED / early-FEED stage. The intent is to help a wind contractor or developer rank floater-mooring concepts, find first-order red flags, and decide whether the design is mature enough to escalate into coupled aero-hydro-servo-elastic verification with a partner. ACE leads on mooring concept selection, anchor strategy framing, quasi-static stiffness, frequency-domain response trends, and tow-out / hook-up logic transferred from offshore oil-and-gas practice. ACE does not deliver certification-grade IEC design-load-case execution, controller co-design, or full time-domain coupled simulation in this scope. Those workstreams are explicitly handed off to OpenFAST / WEIS partners or to specialist geotechnical consultants when the project clears the screening gate. Positioning: screening-tier engineering review based on RAFT (frequency-domain) and MoorPy (quasi-static) workflows, anchored to API RP 2SK and DNV-OS-E301 stationkeeping references. ## Reference Platform: OC4-DeepCwind Semi-Sub The OC4-DeepCwind semi-submersible (Robertson et al., NREL/TP-5000-60601, 2014) is the canonical public floating-wind reference platform paired with the NREL 5 MW baseline turbine. We use commonly cited public values to demonstrate the screening shape; on a real engagement these are replaced with the project's mass, hydrostatic, and metocean inputs. Parameter Public reference value Notes Reference turbine NREL 5 MW baseline Public coupled reference Platform displacement ~13,470 t Including ballast water Operating draft 20.0 m Below SWL Water depth 200 m OC4 reference site Number of columns 3 outer + 1 main Semi-submersible Mooring concept 3-line catenary 120° spread Source: OC4 Phase II definition, NREL/TP-5000-60601. Values are cited to illustrate the screening method; final-design analyses use project-specific inputs. ## Mooring Concept Screened Three-line catenary spread at 120°, fairleads at the column bases, anchors at 837 m radius (OC4 reference). Each line is a chain–polyester–chain composite to manage axial stiffness and seabed footprint. Pre-tension is set to bring quasi-static surge offset under environmental loading inside the typical 10% water-depth screening band. Element Reference value Screening intent Line count 3 (120° spread) Symmetric restoring Top chain (fairlead) ~120 mm studless, ~80 m Wear / fairlead interface Mid section Polyester rope Compliance, weight relief Ground chain (anchor) ~120 mm studless, ~100 m Seabed abrasion margin Anchor radius ~837 m from platform CG OC4 baseline Pre-tension (per line) ~1.1 MN (illustrative) Replace with project values ## Screening Outputs ### (a) Quasi-static stiffness MoorPy quasi-static evaluation produces a restoring matrix the project team can use to sanity-check surge / sway / yaw stiffness against floater displacement. Illustrative public-reference values only — replace with project values before any decision: for an OC4-class catenary, kxx ≈ kyy typically fall in the 70–90 kN/m band and kyaw in the order of 1.0×10^(8) N·m/rad. The screening flags any concept where stiffness is dominated by a single line or where pre-tension drift would push offset outside the operability envelope. ### (b) Frequency-domain response trends RAFT-based frequency-domain runs give surge / heave / pitch RAOs and natural-period estimates the team can compare against the wave-energy band. Screening looks for surge natural period sitting cleanly above the wind-sea peak, heave and pitch periods avoiding the swell band, and sensitivity of those trends to a ±20% change in mooring stiffness assumptions. A concept whose response trends move materially under that sensitivity sweep is flagged for coupled time-domain follow-on rather than declared acceptable. ### (c) Installation and operability flags Screening also surfaces marine-operations red flags: tow-out draft and stability margin, hook-up sequence on the three lines under expected weather windows, anchor installation method consistent with the pre-tension target, and inspection access for the chain–polyester transitions. Items here are decision-support inputs, not procurement specifications. ## Where this stops The screening above intentionally does not cover, and ACE will not represent it as covering: Full IEC 61400-3-2 design load case set, including the certification-grade DLC matrix. Controller co-design or controls-sensitive optimization of the turbine-platform-mooring system. Time-domain coupled aero-hydro-servo-elastic simulation (OpenFAST / WEIS scope). Geotechnical anchor capacity design and site-specific foundation engineering. Final fatigue verification of mooring components for life-cycle signoff. Class / certifier submission packages and final-design procurement specifications. If the screening passes the decision gate, ACE hands these scopes to OpenFAST / WEIS partners or specialist consultants and stays engaged as the offshore-mooring and marine-operations technical reviewer. ## Engagement model A real engagement starts with a 1-hour intake to capture floater concept, site metocean, mooring layout candidates, and the decision the screening must support. ACE then runs the screening using RAFT + MoorPy with the project's actual inputs and produces a decision-grade memo covering scope, assumptions, screening outputs, red flags, and the explicit gap register. A review session walks the contractor or developer through the result and the recommended escalation path. This follows the prospect-demo SOP already used for other ACE screening deliverables. Reviewing ACE for early-FEED FOWT mooring work? Start with the one-page capability summary. Download Capability Summary (PDF, 1 page) ## AceEngineer — Outreach Hub for Installation Contractors & Wind Developers URL: https://www.aceengineer.com/outreach/ Description: Five overnight parametric installation engineering demos, two contractor-targeted briefs and a 1-page capability summary. # Engineering Demos & Outreach Resources Five overnight parametric installation engineering demos, two contractor-targeted briefs, and a 1-page capability summary. Everything below is meant to be sent directly to a prospective client. ## Briefs by audience Pick the brief that matches your audience and pair with one or two of the demos below. For vessel installation contractors ### Heavy-lift, pipelay, PLSV, FOWT-installation 1-screen brief on installation engineering screening, operability envelopes, and contractor-specific tooling. Built for procurement & engineering managers. 2-min read · vessel installation contractors For floating offshore wind ### FOWT mooring screening — OC4 worked example Pre-FEED / early-FEED mooring concept screening on the OC4-DeepCwind public reference. Explicit screening-tier scope; no IEC over-claim. 3-min read · wind-developer engineering managers For small & marginal operators ### Stripper wells — card diagnosis, field triage, keep-or-plug economics Onshore rod lift. Dynamometer cards read on plunger stroke, field ranked by health, and the keep/workover/shut-in/plug decision priced with the plugging liability carried in every case. 3-min read · owner-operators & production engineers ## Demos to attach Each demo is one parametric overnight run with a 30-second walkthrough GIF embedded. Send the URL directly or paste the GIF into a follow-up. Demo 1 · pipeline integrity ### DNV freespan / VIV screening 680 parametric cases across 3 pipe sizes & rigid jumpers. DNV-RP-F105 simplified VIV with seabed-gap correction. Demo 2 · pipeline design ### Pipeline wall thickness — multi-code 72 parametric cases under ASME B31.4/B31.8, DNV-OS-F101, API 1111 simultaneously. Conservative governing-code ranking. Demo 3 · subsea installation ### Deepwater mudmat installation 180 cases across vessel RAO, sea state, mudmat geometry. DNV H103 coupled with OrcaFlex screening. Demo 4 · marine operations ### Shallow water pipelay 60 parametric cases. Vessel-RAO and sag-bend tension sensitivity across the sea-state envelope. Demo 5 · subsea installation ### Subsea jumper lift — Ballymore Manifold-to-PLET jumper. 27 OrcaFlex line sections auto-generated; 81/81 validated tests. Demo 6 · station-keeping (template) ### Mooring & station-keeping screening Catenary, taut, and hybrid mooring concept screening. Quasi-static stiffness and frequency-domain response trends. Page values are illustrative public-reference until a project run is commissioned. ## One-page capability summary The shortest answer to "what does AceEngineer do?" — one page, sendable as an attachment. Download Capability Summary (PDF, 1 page) ## Talk to us To start a parametric run on your data, email the vessel or structure type, the location, and one or two design questions. The canonical models are already built, so the work goes into the run, not the setup. Email us ## Small-Operator Brief — AceEngineer URL: https://www.aceengineer.com/outreach/small-operator-brief.html Description: Well-by-well production engineering for small and marginal operators — dynamometer card diagnosis, field triage, and keep/workover/shut-in/plug economics with the plugging liability carried. For Operators of Stripper & Marginal Wells # Which wells to work over, which to leave, and which to let go. Well-by-well production engineering for fields where a workover has to pay for itself. Send one dynamometer card file and get back a real diagnosis — including which parts of the card are not trustworthy enough to diagnose on. This list did not come from a market study. It came from reading what operators running shallow, conventional wells wrote about their own fields — the cards they pulled, the bearings they lost, the parts they could not find. We work rod lift and production engineering as software: physics that runs on your well data, not a dashboard subscription. Where we can help, this page says so plainly. Where we cannot, it says that too. ## Three things we do well ### Read the card properly Full surface-to-downhole conversion, fillage computed on plunger stroke rather than surface stroke, failure mode with a confidence figure — and an explicit statement of which segments of the derived card carry enough numerical confidence to diagnose on. ### Rank the field Nobody holds 150 wellbores in their head, so the marginal ones stay invisible until they fail loudly. We score every well you send and return one ordered list: which to drive to this week, and why. No new hardware on the lease. ### Price the decision Keep, work over, shut in, or plug — scored on one basis, with the plugging liability carried in every case. Leave P&A out of the sum and every answer quietly tilts toward "keep pumping". ## What we keep hearing The well pumps off in five minutes and there is no controller on it. "Set a shutdown below 65–75% fillage" assumes hardware the well does not have, and is not tuned to your pump, rod string or inflow. The right setpoint is a calculation. Is that noise on the card real, or is it the instrument? On an accelerometer-based dyno, position is integrated twice from acceleration, so error accumulates across a stroke. Some of what looks like a pump tag is arithmetic. The low-volume wells get no attention until a neighbour calls. Not an equipment problem — a ranking problem. The walking beam left and took the saddle bearing with it. Torque and gearbox loading against the unit's actual rating finds the units running outside their envelope before the structure tells you. Repeated tubing splits, never the same joint. Fluid pound puts the lower rods into compression on the downstroke; buckled rods bear on tubing. If that holds, the pump-off fix is also the tubing fix, and rotators are treating a symptom. One missing seat nipple idles a rig day. A rod-lift workover bill of materials is something every operator in a basin holds a partial copy of. "Workovers will add 30 BOPD" — will they? A capital partner asks which wellbores, how much, and what the error bars are. That is inflow and field-health work, and it is the number that a flat claim cannot defend. ## Worked example — the plugging bill is deferred, not avoided A marginal well is not competing against zero. It is competing against paying the plugging bill today, and deferral has real time value. That is why a well can lose money every month and still be worth holding — and why "shut in" is sometimes right when both producing and plugging are wrong. Well Month-1 operating cash Breakeven oil price Way forward 8 BOPD, 30 BWPD +$9,412 $18.38/bbl Keep 4 BOPD, 60 BWPD +$3,154 $33.76/bbl Keep — 127 months left 1.5 BOPD, 90 BWPD −$1,014 $91.79/bbl Shut in 0.6 BOPD, 120 BWPD −$2,953 $260.03/bbl Shut in Illustrative cost deck — $65 oil, $45k plugging, 12.5% royalty, $0.75/bbl water, 8%/yr decline, 10% discount. Not any real operator's numbers. Note the bottom two: producing them destroys value, yet shutting in still beats plugging by roughly $16,000 each, purely from deferring the plugging bill. An example of the kind of thing we will tell you. Preparing a card review this month we found a defect in our own fillage calculation: past a certain pump-off severity it reported a pounded-off pump as full. Severe, fast pump-off is exactly the regime a controller setpoint exists to catch, and it failed toward "healthy". It is fixed, with a regression test, and the four vendor-analysed reference wells still agree to within 0.85 fillage points. We mention it because a firm that never reports finding anything wrong with its own tools is not checking. ## How to start Send one well's card file — whatever your dyno or handheld exports. No install, no telemetry, no account. You get back the downhole card, fillage stroke by stroke, the diagnosis with a confidence figure, and the parts of the card we do not trust. If you also send a full-pump card from the same well, we calibrate the fillage scale first — a "shut down at 75%" rule means something different against a scale that does not top out at 100%. If it is useful, send the field. If it is not, you have lost an email and we have learned something about your wells. What we do not do: find you money, or advise you on your bonding or plugging obligations. We are engineers, not a placement agent, and the obligation is a question for your counsel. We model the cost. ## Send one card. See what comes back. Get in touch Other briefs AceEngineer · support@aceengineer.com ## Vessel Contractor Brochure — AceEngineer URL: https://www.aceengineer.com/outreach/vessel-contractor-brochure.html Description: Parametric installation engineering for vessel contractors — heavy-lift, pipelay, PLSV, FOWT. Batch go/no-go screening, P.E.-stamped, custom runs on your data. For Heavy-Lift, Pipelay, PLSV & FOWT Contractors # Parametric Installation Screening. P.E.-Stamped, Code-Ready. Send us your vessel data and a design matrix, and we run a parametric go/no-go screen — DNV/API/ISO compliant, audit-trail traceable, and ready to defend to your client and the marine warranty surveyor. Why we wrote this: contractor engineering teams are losing tenders to screening bottlenecks. Three weeks of manual Excel for vessel selection means the bid window closes on partial coverage. We codified two decades of subsea installation engineering practice into parametric tools that run hundreds of cases overnight — so your team can defend vessel choice with data, not tribal knowledge. Founder: linkedin.com/in/vamseeachanta. ## What we do for vessel contractors ### Installation-engineering screening Vessel-structure-seastate matrices run overnight. Heavy-lift to splash-zone slamming, jumper VIV to mudmat lowering. Go/no-go heatmaps with the governing load case identified per cell — DNV-RP-H103, DNV-ST-N001, API RP 2A. ### Operability-envelope analysis Weather windows, RAO-driven operability, and seastate-limited execution logic for tow-out, hook-up, S-lay, and PLSV operations. Identifies where your real operating envelope is wider — or narrower — than the standard rule of thumb. ### Contractor-specific tooling Your vessels, your structures, your metocean — not generic examples. We benchmark against your in-house tools first. Re-runs at marginal cost when inputs change. Outputs match the format your engineering manager already presents to clients. Parametric installation-engineering methods: freespan VIV, wall thickness, mudmat installation, pipelay and jumper installation. ## Niches we serve Subsea jumper and spool installation (lift loads, VIV, orientation sensitivity) Pipeline freespan and VIV screening (allowable span maps, soil sensitivity) Mudmat and PLET installation (deepwater, splash-zone slamming) S-lay pipelay and tensioner screening (catenary, sagbend, overbend) Deepwater mooring concept screening (catenary vs. taut, anchor strategy) FOWT mooring transfer from O&G (RAFT + MoorPy screening, tow-out) LNG berth operability and FSRU transfer-interface screening Multi-code wall-thickness comparison (DNV-ST-F101, API RP 1111, PD 8010-2) ## How a custom screening run works Send three things — vessel name or class, structure type and weight range, water-depth range. We pull or use your RAO data, configure the parametric sweep against your project metocean, and return a full screening report: heatmaps, governing load case per scenario, and seastate operability limits in the same format as our published demos. ## Get the one-page capability summary Download Capability Summary (PDF, 1 page) Or email us directly: support@aceengineer.com ## The Platform — digitalmodel Engineering Engine | AceEngineer URL: https://www.aceengineer.com/platform.html Description: The digitalmodel platform: engineering analysis and calculation workflows. Library-first, importable, deterministic. Library reference and calculator support. # The platform The published calculators reference digitalmodel — an open-source library of engineering analysis and calculation workflows. Library-first, importable, deterministic. 35 of 196 modules pass their cited checks · catalogue run 2026-10-17 ## What it computes ### Structural & Fatigue S-N fatigue (DNV-RP-C203 calculator classes) Spectral fatigue (Dirlik, Wirsching-Light) Rainflow counting, SCF ### Asset Integrity / FFS API 579 Level 1/2 (GML, LML) B31G remaining strength Cathodic protection (DNV-RP-B401) ### Subsea Pipeline On-bottom stability (DNV-RP-F109) Wall thickness (DNV-ST-F101) Burst, collapse, combined loading ### Hydrodynamics Wave spectra (JONSWAP, Bretschneider…) RAO processing, seakeeping OrcaWave / AQWA bridges ### Mooring, Riser & OrcaFlex Catenary & lazy-wave risers VIV and free-span screening OrcaFlex model generation from YAML ### Energy Data & Economics BSEE production data & reporting Arps decline curves, EUR NPV / MIRR / IRR field economics ## Where it is — and where it's going We're specific about what's production-ready today versus on the roadmap. Today ### Engineering engine Typed functions with worked examples and tests from real standard clauses. Same inputs, same outputs. Next ### Assessment scope Project inputs, governing methods and limitations require engineering review. Later ### Design iteration Brief → calculation package → checks → refinement. On the roadmap, not claimed as shipped. ## Library-first, not locked in a UI The calculations are functions, not a SaaS login. The library can be imported directly; project use requires qualified inputs and review of the applicable method. View digitalmodel on GitHub ## Work so far | AceEngineer URL: https://www.aceengineer.com/proof.html Description: Public work in engineering analysis, energy data and administrative automation, with links to the code, methodology and dated module-check criteria. # Work so far ## Public code and data digitalmodel contains offshore analysis and calculation workflows. worldenergydata contains public energy-data processing and reports. assetutilities contains reusable data-processing and administrative automation tools. Published datasets are available through Hugging Face. The catalogue records 35 of 196 modules passing their cited checks (run 2026-10-17). Count, criteria and pinned revision. The methodology pages describe planning, focused tasks, tests and independent review. Read how we work. Analysis methods · Newsletter archive Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Diffraction Analysis Reports — Methods and Source Review | AceEngineer URL: https://www.aceengineer.com/reports/diffraction/ Description: Hydrodynamic diffraction analysis methods, response amplitude operators and comparison methods. Numerical results are withheld pending source review. Diffraction methods · source review # Hydrodynamic Diffraction Analysis Reports Results without a public source were removed pending source review. ## Analysis method Potential-flow diffraction analysis describes a floating hull's six-degree-of-freedom motion response amplitude operators (RAOs) across wave frequency and heading: surge, sway, heave, roll, pitch and yaw. Amplitude and phase require consistent units and phase conventions. ## Model basis and interpretation A report basis identifies geometry, mass, loading condition, restoring properties, mesh, water depth, wave headings, frequency grid and damping treatment. Each input requires a public source or an explicitly generic definition before results can be published here. Radiation damping alone excludes external or viscous roll damping. Roll-resonance response depends on damping treatment; an undamped potential-flow peak is not an operability prediction. Frequency-band coverage and mesh resolution constrain interpretation. The long-period check compares translational response with wave-following limits and rotational response with wave-slope limits. In the long-wave limit in deep water, surge follows the cosine of wave heading and sway follows its sine; heave approaches wave elevation. Roll and pitch approach the corresponding wave-slope components, while yaw tends toward zero. A finite-period comparison requires the stated heading, units and convergence criterion. Reliability flags identify response bands that require review. Flagged rows are excluded from automatic summary statistics. Phase conventions require alignment before cross-tool comparison. ## Comparison method Magnitude comparisons use the overlapping period band at common headings, with linear interpolation of the second series onto the first series' period grid. Peak differences compare each series' own peak within that band. Maximum absolute differences and root-mean-square differences summarize the overlapping response. Percentage differences use the first series as the reference and are suppressed where its magnitude is below 5 % of its peak, to avoid ratios dominated by near-zero values. Rows with unresolved reliability flags are excluded from comparison statistics. Comparisons require consistent hull geometry, loading, restoring properties, damping, phase conventions and wave conditions. Comparisons between different hulls require separate interpretation of geometry and loading effects. Changes in damping treatment are assessed as damping sensitivity. ## Publication basis No numerical analysis results are presented on this index. Publication requires traceable public input particulars and sources, or a documented generic geometry and analysis basis. Related: hull hydrodynamics & diffraction methods · capabilities. ## Public Engineering Reports | AceEngineer URL: https://www.aceengineer.com/reports/ Description: Public engineering reports and report views, with content revision dates, formats and links to the published evidence and limitations. # Public Engineering Reports Read each report for its inputs, method, evidence and limits. Interactive report views may require a case selection to show results. Dates below are the last content source commit dates recorded in the public report register. They are content revision dates, not publication dates. Shared template and data changes are not included. ## Report register Published reports and report views Title Content revision date Format Diffraction Analysis Reports — Methods and Source Review 2026-10-17 HTML Tank Sloshing CFD QA Analysis 2026-10-14 HTML Tank Sloshing CFD Case Report 2026-10-14 HTML Tank Sloshing Evidence Summary 2026-10-14 HTML Tank Sloshing CFD Case Analysis 2026-10-17 HTML Browse Tank Sloshing CFD Results 2026-10-14 HTML Tank Sloshing CFD Comparison 2026-10-14 HTML Damping & Sizing — Tank Sloshing CFD 2026-10-14 HTML Dual Connected Tanks — Tank Sloshing CFD 2026-10-14 HTML Tank Sloshing CFD Analysis Summary 2026-10-17 HTML Tank Sloshing CFD Study 2026-10-14 HTML Tank Sloshing CFD Validation Fixture 2026-10-17 HTML The site guide lists indexed pages. The full text file contains their static main content. ## Tank Sloshing CFD QA Analysis — AceEngineer URL: https://www.aceengineer.com/reports/sloshing-cfd-analysis.html Description: Source-neutral CFD input, mesh-quality, visual-evidence, and QA analysis for published tank-sloshing cases. Numerical assurance · model inputs · field evidence # Tank Sloshing CFD QA Analysis Can the selected result be trusted for its stated purpose? This report connects setup, mesh, solver behavior, visual evidence, and an explicit disposition. Case-specific QA values require JavaScript. No private geometry or unpublished solver artifact is embedded in this page. Loading the reviewed public release… Published CFD case CFD caseLoading… Loading conditionLoading… PeriodLoading… MeshLoading… ThemeLightHigh contrast Line weightNormalHeavy MarkersShownHidden Reset report 01 · QA verdict ## Numerical assurance at a glance Loading…Selected case QA verdict. Loading the independent audit… 02 · Model definition ## Input data Status Loading… Values are bounded public metadata, not raw case files or private tank dimensions. 03 · Discretization ## Mesh and numerical-quality inputs Status Loading… 04 · Field evidence ## Reviewed animation or snapshot No reviewed animation preview is published for this case. Representative 1080p videos are available for T16, T22, T26, and fine T24. They show the actual final 2.5-second saved-field window beside synchronized complete-run response graphs; no temporal interpolation is used. Visual media appears only when a committed, source-neutral asset and SHA-256 provenance record exist in the public release. ## Detailed CFD QA results Published QA metrics and dispositions for the selected caseQuantity Value Unit Statistic QA status Configured limit exceeded is retained visibly; it is not silently converted to a passing result. ## Scope boundary This report does not publish private geometry, raw solver paths, or unpublished animation frames. Open detailed response histories · Open normalized cross-case summary ## Tank Sloshing CFD Case Report — AceEngineer URL: https://www.aceengineer.com/reports/sloshing-cfd-case.html Description: Interactive, source-neutral tank-sloshing CFD case report with published evidence and provenance. Individual loading condition · reviewed CFD evidence # Tank Sloshing CFD Case Report A case-level engineering record: setup, response histories, load envelopes, QA disposition, and traceable limitations. Interactive case selection requires JavaScript. The methodology and publication boundaries remain available below. Loading the reviewed public release… Published case selection CFD caseLoading… Loading conditionLoading… PeriodLoading… MeshLoading… ThemeLightHigh contrast Line weightNormalHeavy MarkersShownHidden Export PNGExport SVGReset report 01 · Case reading ## Engineering disposition Loading…Selected case Case verdict. Loading the reviewed evidence… Only accepted, de-identified CFD evidence from the pinned public release is selectable. Verification-only records remain outside accepted-result controls. 02 · Resolved response ## Detailed response histories ### Pressure probes No reviewed pressure-probe series is published for this case. ### Aggregate wall forces No reviewed aggregate-force series is published for this case. ### Aggregate wall moments No reviewed aggregate-moment series is published for this case. ### Wall-pressure envelope by height No reviewed pressure envelope is published for this case. ## Accessible chart data Values represented in the selected chartQuantity Value Unit 04 · Interpretation ## How to use this case ### Decision use Compare time histories, extrema, harmonic response, and pressure envelopes within the published loading condition. ### QA use Confirm the forcing definition, mesh state, solver audit, and synchronized field evidence in the analysis report. ### Boundary No synthetic placeholder, private geometry, sectional-load inference, or vessel-level anti-roll benefit claim is presented. Open the CFD QA analysis report ## Tank Sloshing Evidence Summary — AceEngineer URL: https://www.aceengineer.com/reports/sloshing-tank-summary.html Description: Interactive summary of published tank-sloshing CFD, analytical targets, and convergence evidence. CFD study · OpenFOAM · free surface + forced roll # Tank Sloshing — Engineering Evidence Report What the completed runs establish, where the response is strongest, and which conclusions remain bounded by the published evidence. Reviewed public release24 accepted cases · analytical verification · forced-roll response · mesh QA Interactive curve controls require JavaScript. The methodology and publication boundaries remain available below. Loading the reviewed public release… Summary display and print controls Reference caseLoading… Loading conditionLoading… PeriodLoading… MeshLoading… ThemeLightHigh contrast Line weightNormalHeavy MarkersShownHidden DensityComfortableCompact Select published curves Loading curve controls… Export PNGExport SVGReset report 01 · Executive reading ## What this study establishes The free-decay cases test the numerical model against the analytical first-mode frequency. The forced-roll sweep then measures the response across loading periods; mesh comparison and solver audit qualify how strongly those results may be used. Loading…Study evidence Engineering verdict. Loading the reviewed evidence… 02 · Response evidence ## Where the forced-roll response peaks Use the curve controls to compare absolute response, response normalized per degree of roll, and the free-decay analytical target. Curves retain their evidence class and are not blended into a single validation claim. Accepted CFDMethodology onlyVerification only ## Accessible chart data Values represented in the selected summary chartQuantity Value Unit 04 · Interpretation boundary ## What the evidence does—and does not—support ### Supported Frequency agreement, period-dependent forced-roll response with 21–25 s refinement, normalized response comparisons, aggregate and sectional loads, complete-cycle field evidence, and the published numerical QA disposition. ### Not yet supported Three-dimensional end-wall and local impact effects, private geometry reconstruction, or a vessel-level anti-roll benefit claim. ### Measurement update The 22–24 s region is the amplitude peak for the published 5° sweep, not the natural or tuning period. Phase puts the exchange natural period at 14.31 s; the measured amplitude peak moves from 20 s to 40 s across 2.5°–10° roll. ## Tank Sloshing CFD Case Analysis — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/analysis.html Description: Individual tank-sloshing CFD case analysis with published histories, envelopes, metrics, QA and provenance. Individual loading condition · reviewed CFD evidence # Tank Sloshing CFD Case Analysis A bookmarkable case record: published basis, response histories, load envelopes, engineering disposition, and evidence boundary. Interactive case selection requires JavaScript. Loading the reviewed public release… Published case selection CFD caseLoading…Loading conditionLoading…PeriodLoading…MeshLoading…ThemeLightHigh contrastLine weightNormalHeavyMarkersShownHidden Export PNGExport SVGReset report 01 · Case reading ## Engineering disposition Loading…Selected case Case verdict. Loading the reviewed evidence… Evidence depth and media availability are independent. Open the case browser to see the catalog classification. 02 · Resolved response ## Detailed response histories ### Pressure probes No reviewed pressure-probe series is published for this case. ### Aggregate wall forces No reviewed aggregate-force series is published for this case. ### Aggregate wall moments No reviewed aggregate-moment series is published for this case. ### Wall-pressure envelope by height No reviewed pressure envelope is published for this case. 03 · Published metrics ## Accessible case data Published metrics for the selected caseQuantity Value Unit 04 · Review paths ## Complete the evidence review Validation fixture · Mesh, inputs, media and QA · Compare cases · Release manifest No synthetic placeholder, private geometry, sectional-load inference, or vessel-level anti-roll benefit claim is presented. ## Browse Tank Sloshing CFD Results — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/browse.html Description: Browse every published tank sloshing CFD case by evidence depth, loading, mesh, media, and QA status. Tank sloshing · complete public catalog # Browse all CFD cases Filter the reviewed release, inspect evidence maturity, and open a stable case or media link for subject-matter review. JavaScript is required to load the pinned case catalog. Loading the reviewed catalog… Evidence depthAll tiersDetailedStandardSimple LoadingAll loading MeshAll meshes MediaAny mediaVideo availableImage availableNo case media QA statusAll QA states Find a case Reset filters 0 cases ## How evidence depth is assigned Detailed Inputs, mesh QA, histories, derived metrics, selected-case visual, and detailed field sequence. Standard Inputs, numerical results, derived metrics, and a selected-case snapshot. Simple Reviewed summary metrics without a complete selected-case field record. Video availability is displayed independently. A retained final-window video is not a full-cycle animation and does not upgrade an incomplete engineering record. ## Tank Sloshing CFD Comparison — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/comparison.html Description: Compare any two published tank-sloshing CFD cases with compatibility warnings, common metrics, normalized deltas and traceable provenance. Case comparison · compatibility-aware · pinned evidence # Tank Sloshing CFD Comparison Compare two published cases without confusing period, mesh, timestep, loading, or evidence-depth differences with solver validation. Loading the reviewed release… Select two accepted cases Case ALoading…Case BLoading… The selected case IDs are stored in the URL for review and sharing. 01 · Comparison qualification ## Are these cases comparable? Selected case basisBasis Case A Case B 02 · Common evidence ## Published metric comparison Only quantities published for both cases with matching units are compared. Percentage deltas are suppressed where the Case A value is effectively zero. Common metrics and Case B minus Case A deltasQuantity Unit Case A Case B Δ Δ% 03 · Interpretation ## How to describe the difference Loading comparison type… ### Mesh sensitivity Same loading and period with a different mesh supports a discretization comparison. ### Period response Same family and mesh with a different forcing period supports a response-curve comparison. ### Validation Free-decay cases compare measured frequency with the analytical fixture; completion alone is not validation. 04 · Provenance ## Data contract Open the stable validation fixture · Browse all cases ## Damping & Sizing — Tank Sloshing CFD — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/damping-and-sizing.html Description: Measured exchange-mode damping surface for connected sloshing tanks, the validated inertia and loss laws, and the conduit area that maximises roll reduction. Source-neutral reference geometry. Connected-tank study · damping surface · conduit sizing # Damping & Sizing A connected-tank roll device is decided by two numbers: where its exchange mode sits, and how heavily that mode is damped. Both are now measured across a grid rather than inferred from a single case, and both feed a closed-form model that predicts the conduit area which maximises roll reduction. Geometry is the source-neutral dm1528 reference; no client data appears here. DispositionDesign-grade for conduit sizing on this geometry family. The inertia law predicts the exchange period to ±3 % across a four-fold conduit-area range and 25–70 % fill; the loss law reproduces 35 measured cases to 8.6 % rms; the tank moment is closed form to 4.3 % rms for periods of 20 s and above. The damping surfaceConduit sizingDual tanks 01 · What changed ## The exchange period is 14.31 s, not the response peak Earlier work on this capability read the exchange period off the amplitude peak of a forced-roll sweep, at about 23 s. That is not the natural period. Phase settles it without ambiguity: the lag through the exchange mode crosses 90° exactly at resonance whatever the damping, and it does so at 14.31 s. The amplitude peak is a different quantity — it is loss-controlled, and it moves. The distinction is not academic. An effective conduit length calibrated to the response peak absorbs a damping-induced shift into an inertia parameter, and will not transfer to another conduit area or fill. 14.31 sexchange period, from phase n = 2.14conduit-area exponent of the loss 8.6%loss law, rms over 35 cases 4–6 m²conduit area at maximum roll reduction 02 · The measured surface ## Equivalent damping over period and roll amplitude Twenty-one forced-roll CFD cases, one per cell, identical geometry, mesh and solver settings throughout. Damping is not a property of the tank alone: it rises steeply with roll amplitude at every period, which is what a quadratic conduit loss does and a linear-viscous one cannot. roll 10 deg, period 10 s: zeta_eq = 0.711roll 10 deg, period 13 s: zeta_eq = 0.682roll 10 deg, period 16 s: zeta_eq = 0.705roll 10 deg, period 20 s: zeta_eq = 0.669roll 10 deg, period 23 s: zeta_eq = 0.625roll 10 deg, period 26 s: zeta_eq = 0.568roll 10 deg, period 40 s: zeta_eq = 0.37410°roll 5 deg, period 10 s: zeta_eq = 0.446roll 5 deg, period 13 s: zeta_eq = 0.587roll 5 deg, period 16 s: zeta_eq = 0.527roll 5 deg, period 20 s: zeta_eq = 0.441roll 5 deg, period 23 s: zeta_eq = 0.389roll 5 deg, period 26 s: zeta_eq = 0.326roll 5 deg, period 40 s: zeta_eq = 0.1885°roll 2.5 deg, period 10 s: zeta_eq = 0.258roll 2.5 deg, period 13 s: zeta_eq = 0.437roll 2.5 deg, period 16 s: zeta_eq = 0.306roll 2.5 deg, period 20 s: zeta_eq = 0.269roll 2.5 deg, period 23 s: zeta_eq = 0.216roll 2.5 deg, period 26 s: zeta_eq = 0.176roll 2.5 deg, period 40 s: zeta_eq = 0.1002.5°10131620232640forcing period (s)0.20.40.6equivalent damping ζroll amplitude → roll 2.5° roll 5° roll 10° Equivalent damping ratio ζ of the exchange mode. Each ridge is one roll amplitude; each marker is one CFD case. Hover a marker for its value. Equivalent damping ζ over the measured grid — one CFD case per cell, 21 cellsroll 10 s 13 s 16 s 20 s 23 s 26 s 40 s 2.5° 0.258 0.437 0.306 0.269 0.216 0.176 0.100 5° 0.446 0.587 0.527 0.441 0.389 0.326 0.188 10° 0.711 0.682 0.705 0.669 0.625 0.568 0.374 ζ is a linearisation of a quadratic loss and is valid at the amplitude it was measured at — it is not a material constant. The 13 s column is the least reliable: it sits closest to resonance, where the extraction is numerically ill-conditioned. 03 · What the grid proves ## The natural period does not move; the response peak does A single-amplitude sweep cannot separate these two. The grid can, and the separation is decisive: the exchange period is an inertial property and holds to under 2 % across a four-fold change in roll amplitude, while the amplitude peak doubles over the same range. Natural period against amplitude peak, by roll amplitude roll amplitude natural period (90° phase) amplitude peak peak amplification 2.5° 14.15 s 20 s ×1.539 5° 14.31 s 23 s ×1.269 10° 14.41 s 40 s ×1.099 The 10° peak sits at the edge of the tested period range, so its amplification is a lower bound. 04 · The laws, and what tested them ## Predictions made before the runs, not fitted after Two numbers are fitted, both at one conduit area and one fill: an effective conduit length, and a loss coefficient. Everything else is geometry. The cases below were then placed where the resulting predictions are falsifiable — at the predicted resonance of conduit areas and fills the model had never seen. Exchange period: predicted before the run, measured after case predicted measured error phase lag at the predicted period conduit area 3.4 m² 19.73 s 19.27 s +2.4 % 88.3° conduit area 13.5 m² 10.64 s 10.97 s -3.0 % 95.0° fill 25 % 13.95 s 13.45 s +3.7 % 85.4° fill 70 % 14.59 s 14.38 s +1.4 % 88.3° The loss law needed correcting by this test, and the correction is instructive. Derived as a form drag it scales as 1/Ac, which reproduced the calibration area but failed in opposite directions either side of it — under by 55 % at the smaller conduit, over by 108 % at the larger. Fitting the exponent rather than assuming it gives n = 2.14, and rms error over 35 cases at three conduit areas falls from 36.5 % to 8.6 %. Tank roll moment, closed form against CFD (5° roll, validated band) period measured closed form error 20 s 9.103 MN·m 8.570 MN·m -5.9 % 22 s 9.498 MN·m 9.040 MN·m -4.8 % 23 s 9.606 MN·m 9.181 MN·m -4.4 % 24 s 9.673 MN·m 9.279 MN·m -4.1 % 26 s 9.683 MN·m 9.342 MN·m -3.5 % 40 s 9.206 MN·m 9.075 MN·m -1.4 % 60 s 8.807 MN·m 8.763 MN·m -0.5 % The moment adds two static terms the redistribution estimate omits — the weight moment of the whole fluid mass about the roll axis, and the within-leg free surface. Below about 20 s the closed form degrades, and the cause is not established. An earlier note here attributed it to the legs’ own sloshing modes; that is withdrawn. Roll tilts the surface across the leg width, so the roll-coupled mode is the 2.79 s transverse one, whose undamped magnification at 10 s forcing is 1.08 against the 1.72 the residual requires — far too remote. The 6.25 s longitudinal mode would give 1.64, close enough to have looked explanatory, but it is orthogonal to uniform roll forcing and is not excited. Deriving the properly coupled correction moves all-case rms 16.74 % → 16.68 %, i.e. not at all. The band is empirical. 05 · Conduit sizing ## Roll reduction against conduit area With every link validated, the chain runs from geometry to roll response, and the design question becomes answerable: for a given hull, which conduit area returns the most roll reduction? superseded sizing 13–22 m²0%25%50%75%optimum: A_c 5.0 m2, 50.8 % reduction (roll 18 s, hull zeta 0.02)optimum: A_c 6.0 m2, 25.2 % reduction (roll 18 s, hull zeta 0.05)optimum: A_c 4.5 m2, 46.1 % reduction (roll 21 s, hull zeta 0.02)optimum: A_c 5.0 m2, 22.6 % reduction (roll 21 s, hull zeta 0.05)251015202530conduit area Ac (m²)peak roll reduction roll period 18 s roll period 21 s solid = hull ζ 0.02 · dashed = hull ζ 0.05 Peak roll reduction against conduit area, tank authority α = 0.05. Filled markers are the optimum for each hull. Hover any optimum for its values. Optimum conduit area by hull roll period hull ζ optimum Ac tank period tuning ratio peak reduction 18 s 0.02 5.0 m² 16.47 s 0.915 50.8 % extrapolated 18 s 0.05 6.0 m² 15.15 s 0.841 25.2 % extrapolated 21 s 0.02 4.5 m² 17.30 s 0.824 46.1 % 21 s 0.05 5.0 m² 16.47 s 0.784 22.6 % Two results matter more than the peak value. The optimum is deliberately detuned — the tank period sits below the roll period, which is correct for a heavily damped absorber. And the optimum is broad: 5 and 6 m² are within one percent of each other, so the as-built routing uncertainty that worries a tuned device is survivable here. Sensitivity to conduit area (roll 18 s, hull ζ = 0.02) conduit area tank period peak reduction 3.0 m² 20.94 s 33.3 % 4.0 m² 18.28 s 43.1 % 5.0 m² 16.47 s 50.8 % 6.0 m² 15.15 s 50.0 % 8.0 m² 13.31 s 43.1 % 10.0 m² 12.07 s 33.9 % 13.5 m² 10.64 s 20.2 % 18.0 m² 9.48 s 9.8 % 22.0 m² 8.79 s 5.1 % 25.0 m² 8.39 s 3.0 % Hull damping roughly halves the benefit at every conduit area. It is a property of the vessel, not of the tank, and it moves the answer by more than any sizing choice does. 06 · Limits ## What this does not establish One geometry family. Conduit area is validated over 3.4–13.5 m² and fill over 25–70 %; the loss exponent rests on two off-calibration conduit areas and should be treated as provisional until a third tests it. The closed-form moment is validated for forcing periods of 20 s and above. Where the coupled peak falls just below that, the table says so. A connected tank worsens long-period roll through the free-surface penalty it imposes. That is present in the same model and is not a small effect. Nothing here is a vessel result. The hull enters only as roll period, hull damping and tank authority; applying it to a ship requires that vessel’s own values. ### Provenance Every case and derived value on this page is published in the immutable release — digest 1034bb4efc5d9b39…, pinned dataset revision 51ba5ddbca8d…. That release grew from 24 to 57 cases and 133 to 441 derived metrics to carry this work, and all 47 declared source files resolve on the pinned revision. Three of the 33 new cases are flagged, not clean. fill-f25-t12-a5, fill-f25-t13p95-a5 and grid-t10-a10 exceed the declared 2 % exchange cycle-change limit (2.25 %, 2.30 % and 3.24 %). They are published with status accepted_with_exception and counted in the release’s dispositions table rather than dropped, because they are real runs and because where they fall is informative: the two lowest-fill cases and the largest-amplitude shortest-period cell are the most nonlinear conditions in the set, and the slowest to settle. Statistics that assume every cell is equally converged should exclude them. No time series were published. The samples table stands at 9,933 rows against a declared limit of 10,000, so adding series would breach the release’s own limit; the raw histories stay in the pinned private source. Generated by scripts/generate_sloshing_damping_page.py, which regenerates this page from the reviewed analysis files — no value here is hand-transcribed, and --check fails the build if the page drifts from its sources. Sources: review_output/damping/response_surface.json review_output/damping/prediction_checks.json analytical/loss_scaling.json analytical/moment_model.json analytical/design_sweep.json ## Dual Connected Tanks — Tank Sloshing CFD — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/dual-connected-tanks.html Description: Source-neutral dual connected-tank sloshing analysis: the connected U-tube exchange mode, inter-tank mass shift, and roll moment, from a closed-form model validated against the dm1528 twin-tank CFD. Connected-tank study · U-tube exchange · analytical + CFD # Dual Connected Tanks Two tanks joined by a bottom conduit behave as one coupled system. This page resolves the connected exchange (U-tube) mode, the inter-tank mass shift, and the roll moment it produces — from a closed-form model checked against the resolved twin-tank CFD. Geometry is the source-neutral dm1528 reference; no client data appears here. DispositionValidation-grade for the connected-exchange mechanism: the analytical model matches CFD independently on single-tank frequency, exchange period, and the conduit-area scaling law. The mass shift and roll moment follow from the CFD-measured level difference. Two claims here are superseded: the exchange period is 14.31 s (23 s is the amplitude peak), and the ×1.45 residual is resolved in closed form rather than being dynamic amplification — see the note below. See the exchange modeMass shift & rollBack to capability Superseded in part · 2026-07-28Two statements on this page have since been corrected by a measured (period × roll amplitude) grid. The 23 s figure below is the amplitude peak, not the exchange natural period — phase puts the natural period at 14.31 s, and the amplitude peak moves with roll amplitude while the natural period does not. Consequently the effective conduit length calibrated to that peak absorbs a damping-induced shift into an inertia parameter. The ×1.45 residual is also now resolved in closed form: it is the weight moment of the whole fluid mass about the roll axis plus the within-leg free surface, terms the redistribution estimate omits. See Damping & sizing. 01 · Why connect the tanks ## The coupling lives in the exchange mode Roll excites transverse sloshing, but a single tank's first sloshing mode is far faster than the vessel roll period, so on its own it moves almost quasi-statically with the ship. Connecting two tanks through a bottom conduit adds a new, slow mode: water exchanging between the legs, like a U-tube. That exchange mode can be tuned near the roll period, which is exactly what makes connected tanks matter for roll — and it is the mode this page quantifies. 14.31 sexchange natural period (phase); 23 s is the amplitude peak 67.9 tinter-tank mass shift (amplitude) 9.67 MN·mroll moment, governing case (CFD) 0.00%free-decay frequency check 02 · Single tank first ## Single-tank modes (verification anchor) Linear first-mode sloshing, ω² = (πg/L)·tanh(πh/L), on the source-neutral reference. The 1 m free-decay tank reproduces the closed-form target exactly and matches the CFD to ~0.30%, anchoring the method before it is applied to the connected system. Single-tank first-mode results (50% fill unless noted)Case Direction / length Analytical Check Free-decay 1 m tank transverse, L = 1 m, h/L = 0.30 0.758054 Hz 0.000% vs closed form; ~0.30% vs CFD Twin leg — longitudinal L = 20 m T = 6.25 s matches CFD framework (6.251 s) Twin leg — transverse W = 6 m T = 2.79 s roll-excited direction Both single-tank modes (2.8–6.3 s) sit well above the roll band — confirming a single tank is off-resonance and the useful coupling must come from the connected exchange mode below. 03 · The connected exchange mode ## U-tube exchange period Modelling the two legs joined by the bottom conduit as a U-tube (q = transferred volume; stiffness K = 2ρg/As, inertia M = ρ(ℓc/Ac + 2h/As)) gives the exchange natural period directly. Calibrating the effective conduit length to the CFD response peak was the original approach here; it is superseded. The response peak is loss-controlled and sits well above the natural period, so anchoring an inertia parameter to it is not valid — the calibration is now anchored to the measured natural period instead. Exchange-mode natural period, dm1528 reference (As = 120 m², Ac = 6.8 m², h = 5 m)Conduit length ℓc Basis Exchange period Note 10.0 m geometric (centroid-to-centroid) 19.4 s uncorrected geometric-path comparison 5.20 m calibrated to the measured natural period 14.31 s 0.520× geometric; 90° phase crossing Key finding. The connected exchange natural period is 14.31 s, identified by the 90° phase crossing. The 22–24 s plateau in the 5° forced-roll sweep is the loss-controlled amplitude peak, not the exchange resonance or tuning period; it shifts from 20 s to 40 s across the measured 2.5°–10° roll-amplitude range. 04 · Mass shift & roll moment ## What the exchange does to roll For the published 24 s, 5° forcing case, the CFD level-difference amplitude (1.1037 m) fixes the volume exchanged between legs. The 6.66 MN·m redistribution estimate omits two static contributions to the total roll moment: the weight moment of the whole fluid mass about the roll axis and the within-leg free surface. Published 24 s, 5° forcing case: analytical vs resolved CFDQuantity Analytical CFD Agreement Exchange volume swing 132.4 m³ 132.45 m³ exact Transferred volume (amplitude) 66.2 m³ — = As·Δlevel/2 Inter-tank mass shift (amplitude) 67.9 tonne — ρ · transferred volume Roll moment — hydrostatic 6.66 MN·m — 2ρg·V·arm (arm = 5 m) Roll moment — total 6.66 MN·m redistribution-only estimate 9.67 MN·m ×1.45 static-term residual; resolved in closed form These quantities are derived from the CFD-measured level difference (1.1037 m), so this is a derivation cross-check, not an independent prediction: the hydrostatic mass-shift moment captures the static physics, and the ×1.45 factor was previously read as resonant dynamic amplification. It is not: it is present at quasi-static forcing, where inertia cannot contribute, and is now resolved in closed form as two omitted static terms. The page's independent analytical↔CFD validations are the single-tank frequency, the exchange period, and the conduit-area scaling law below. 05 · Conduit-area sensitivity ## Tuning the connection — the design knob Three twin-tank CFD runs — recovered from raw post-processing that had never been reduced, and now published in the release — vary the connecting conduit area Ac at a fixed 6.25 s forcing period, well off-resonance for the 14–27 s exchange modes they produce. They give the model an independent test: does it predict how exchange scales with the size of the connection? It does — to ~1–2%, with no per-case calibration. Conduit-area sensitivity — analytical U-tube vs CFD (forcing 6.25 s, geometric conduit length)Conduit area Ac Exchange period CFD exchange amp Analytical Scaling ratio, CFD / analytical 3.4 m² 27.0 s 7.91 m³ 5.92 m³ 1.00 / 1.00 6.8 m² 19.4 s 16.30 m³ 12.17 m³ 2.06 / 2.06 13.5 m² 14.1 s 34.60 m³ 25.58 m³ 4.38 / 4.32 The conduit-area scaling law matches to ~1–2% (ratio columns). The previously applied ×1.34 absolute-magnitude factor must not be interpreted as resonant dynamic amplification; the basis for reconciling absolute exchange magnitude remains unverified — needs owner. Design reading: a larger connection raises both the exchange amplitude and its natural frequency, so Ac is the knob that places the exchange mode relative to roll. 06 · Validation & provenance ## What is established, and what is next ### Established Single-tank first mode validated to 0.000% (closed form) / ~0.30% (CFD) Connected exchange natural period is 14.31 s from the 90° phase crossing Conduit-area scaling law validated to ~1–2% across Ac = 3.4–13.5 m² Inter-tank mass shift derived from the CFD level difference; the former ×1.45 roll-moment residual is resolved as two omitted static terms Entirely source-neutral reference geometry ### Staged / bounded Purpose-built coupled dual-tank CFD confirmation (licensed-run host) The ×1.34 reconciliation of absolute exchange magnitude is unverified and needs owner review; it is not established as dynamic amplification Client-vessel geometry handled privately; only abstracted results here ReproducibilityAnalytical model: dm1528-analytical/0.1 (assumption register A1–A16, results.json). Conduit-area validation: dm1528-ac-validation/0.1 (three off-resonance forced-roll CFD runs, reduced from post-processing and published as cases twin-conduit-a3p4, twin-conduit-a6p8, twin-conduit-a13p5). CFD anchors: immutable release 1034bb4efc5d9b390d51d4d546800c5a25bf6673af824e07ed5265da038ec30b, extending pinned Hugging Face revision 51ba5ddbca8dcfa8faeb6de5c592f342f32cfe2d. 07 · Continue ## Related evidence Screening ### Interactive study Verification and forced-response curves for the twin-tank campaign. Open study → Verification ### Validation fixture The free-decay natural-frequency check this analysis is anchored to. Open fixture → All cases ### Browse results Every published twin-tank case, with evidence depth. Browse cases → ## Tank Sloshing CFD Analysis Summary — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/ Description: Engineering summary of the published tank-sloshing CFD campaign: analytical verification, forced-roll response, mesh sensitivity, visual evidence, conclusions and limitations. Engineering summary · OpenFOAM VOF · free decay + forced roll # Tank Sloshing CFD Analysis The completed campaign verifies the first sloshing mode against theory, resolves the forced-roll response from 16–26 seconds, adds a stationary baseline and sectional wall loads, and publishes complete-cycle fields plus pressure-resolved QA near the response maximum. Overall dispositionUseful for response screening, numerical verification, and aggregate/sectional load review. Not yet a vessel-level anti-roll assessment. Read the findingsReview validationBrowse all 21 cases 01 · Study question ## What was analyzed? A partially filled rectangular tank was evaluated with VOF CFD. Seven free-decay cases test mesh and timestep sensitivity against the analytical first-mode frequency. Thirteen forced-roll records cover 16–26 seconds, targeted 21–25 second refinement, medium/fine comparison, pressure QA, and sectional loads. One no-roll run establishes the numerical baseline. 21accepted CFD cases 7free-decay verification cases 13forced-roll records 7case-specific 1080p videos 02 · Executive findings ## What the results establish 1 ### The first-mode frequency is reproduced consistently Across the published mesh and timestep cases, measured frequency differs from the analytical target of 0.758054 Hz by 0.2964–0.3264%. The finest 25,600-cell case gives 0.755807 Hz. Use: this supports the VOF model for natural-frequency prediction. The convergence sequence is monotonic but not demonstrably asymptotic, so the residual should not be represented as a formal high-order grid-convergence result. 2 ### Refinement resolves a local medium-mesh peak at 23 seconds for 5° roll At 5° roll, normalized liquid-level response increases from 0.190 m/deg at 16 s through 0.22071 at 22 s to 0.22119 m/deg at 23 s, then decreases to 0.22074 at 24 s, 0.21946 at 25 s, and 0.217 at 26 s. The fine 24 s case gives 0.22145 m/deg, confirming mesh sensitivity is comparable to the small period-to-period differences. Use: treat 22–24 seconds as the broad amplitude-peak region for this 5° sweep, not as the natural or tuning period. The exchange natural period is 14.31 s, and the amplitude peak moves with roll amplitude. 3 ### Aggregate roll moment remains high through 24–26 seconds Roll-moment amplitude normalized by roll angle rises from 1.49 MN·m/deg at 16 s to approximately 1.94 MN·m/deg at 24–26 s. The level-response maximum and moment maximum therefore need not occur at exactly the same period. Use: period selection depends on the response quantity governing the engineering decision. 4 ### The 24 second fine mesh changes response modestly At 24 seconds, the medium and fine cases give liquid-level amplitudes of 1.1037 m and 1.1124 m, while aggregate roll moment changes from 9.673 MN·m to 9.815 MN·m. Use: response magnitude is relatively stable across the published medium/fine comparison, but this single comparison does not replace a full asymptotic convergence study. 03 · Forced-roll response ## Published period sweep The principal result is present directly in the page, so it remains visible without JavaScript or external data loading. 0.2220.1850.22119 m/deg · 23 s161820222426forcing period (s) · shaded band = 22–24 s broad maximum Normalized liquid-level response (harmonic amplitude per roll degree). The sampled medium-mesh maximum is at 23 s within a broad 22–24 s plateau; aggregate roll moment keeps rising through 24–26 s (see table below). Final-three-cycle harmonic response normalized by forcing roll amplitudePeriod Level response Roll-moment response Engineering reading 16 s 0.190 m/deg 1.495 MN·m/deg Lower end of published response band 18 s 0.205 m/deg 1.687 MN·m/deg Response increasing 20 s 0.216 m/deg 1.821 MN·m/deg Approaching broad maximum 21 s 0.21882 m/deg 1.86463 MN·m/deg Targeted refinement 22 s 0.22071 m/deg 1.89958 MN·m/deg Broad plateau 23 s 0.22119 m/deg 1.92120 MN·m/deg Sampled medium-mesh level maximum 24 s 0.22074 m/deg 1.93463 MN·m/deg Fine, pressure, and sectional comparisons available 25 s 0.21946 m/deg 1.94061 MN·m/deg Level response descending 26 s 0.217 m/deg 1.937 MN·m/deg Level response reduces; moment remains high Values are derived from the immutable release’s final-three-cycle harmonic metrics. Open the interactive study to select curves and export plots. 04 · Visual evidence ## Representative completed cases These are case-specific CFD snapshots and synchronized response graphs. The new 22 s and fine 24 s media cover one complete final forcing cycle with no temporal interpolation; legacy 16 s and 26 s media remain shorter final-window context. 16 s · medium meshCase-specific CFD evidence · open 1080p video 22 s · medium meshComplete final forcing cycle · no interpolation 24 s · fine mesh · Co 0.25 targetComplete cycle · pressure and Courant QA 26 s · medium meshCase-specific CFD evidence · open 1080p video 05 · Validation and QA ## Why the result is qualified rather than simply marked “passed” ### Frequency verification The mesh and timestep series remains within approximately 0.3% of the analytical target. This is the strongest validation statement supported by the public release. Open validation → ### Courant refinement The new pressure-resolved fine case reduced the observed maximum Courant number from 0.478 to 0.326. It completed and converged, but still exceeded its tighter configured target of 0.25. Open detailed QA → ### Evidence coverage Inputs, QA, bounded histories, complete-cycle media, pressure envelopes, and sectional loads are published where case-specific evidence exists. Simpler validation cases remain intentionally concise. Review coverage → 06 · Conclusions and limits ## Engineering disposition ### Supported First-mode frequency verification Period-dependent forced-roll response and 21–25 s refinement Medium/fine response comparison at 24 s Stationary numerical baseline Aggregate and left/right sectional loads Complete-cycle fields and detailed pressure evidence for representative cases ### Not established Three-dimensional end-wall and local impact effects beyond the disclosed model Response across other fill levels or roll amplitudes Vessel-level anti-roll performance Private geometry reconstruction Measurement updateThe 22–24 s region is the amplitude peak for the published 5° sweep, not the exchange natural period. The measured natural period is 14.31 s, while the amplitude peak moves from 20 s to 40 s across the 2.5°–10° roll-amplitude grid. 07 · Navigate the evidence ## One place to reach every report The same reviewed campaign is published two ways: interactive pages to explore, and standalone report pages to read or print. Every destination below is also on the navigation bar of every page. Understand Screening ### Interactive study Campaign structure, verification and forced-response curves; select and export. Open study → Verification ### Validation fixture The free-decay natural-frequency check and its retained numerical caveat. Open fixture → Explore the data All cases ### Browse results Filter every published case by evidence, loading, mesh, QA, and media. Browse cases → Side by side ### Compare cases Compare two comparable cases with explicit compatibility warnings. Compare cases → Connected system ### Dual connected tanks The U-tube exchange mode, inter-tank mass shift, and roll moment — analytical, validated against CFD. Open dual tanks → Per-case detail Interactive ### Case analysis A single case: histories, envelopes, metrics, QA and provenance. Open case analysis → Report view ### Individual CFD report The standalone, print-styled individual case report. Open report → Courant caveat ### CFD QA analysis Numerical assurance: mesh quality, Courant health, reviewed preview. Open QA → Read as a report Printable ### Summary report The standalone, print-styled engineering evidence summary of this page. Open summary → Provenance ### Data & provenance The immutable release files this site publishes, listed with their checksums in the release manifest. Open the release manifest → ## Tank Sloshing CFD Study — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/study.html Description: Engineering study across the published tank-sloshing CFD campaign: analytical verification, forced-roll response, convergence, loads, QA and limitations. CFD study · OpenFOAM · free surface + forced roll # Tank Sloshing — the Published CFD Study From analytical first-mode verification to period-dependent forced-roll response: what the completed cases establish, where the evidence is strongest, and what remains outside the present model. Reviewed public release24 accepted cases · immutable dataset revision · source-neutral evidence Interactive curves require JavaScript. Study scope and interpretation remain readable below. Loading the reviewed public release… 01 · Decision question ## What do the completed runs tell us? The campaign asks two linked questions. First, does the VOF model reproduce the rectangular tank’s analytical first-mode frequency under free decay? Second, how do liquid-level response and aggregate roll moment change across the published forced-roll periods and mesh levels? Loading…Study evidence Engineering verdict. Loading the reviewed evidence… 02 · Analysis basis ## Campaign structure ### Free decay Mesh and timestep cases compare measured first-mode frequency with the linear analytical target. This is the numerical validation fixture. ### Forced roll Thirteen forced-roll records cover 16–26 s with targeted 21–25 s refinement, a medium/fine comparison at 24 s, sectional wall loads, and a stationary no-roll baseline. ### Detailed pressure cases The fine 24 s pressure runs publish wall probes, aggregate loads, mesh QA, solver audit, complete-cycle fields, and a tightened Courant-target refinement. Study curves and report styling Reference caseLoading…Loading conditionLoading…PeriodLoading…MeshLoading…ThemeLightHigh contrastLine weightNormalHeavyMarkersShownHiddenDensityComfortableCompact Select published curves Loading curve controls… Export PNGExport SVGReset report 03 · Quantified evidence ## Verification and forced-response curves Absolute and roll-normalized quantities remain separate. The analytical free-decay target is a verification reference, not a forced-response prediction. Accepted CFDAnalytical verification 04 · Traceable values ## Selected-case evidence Published metrics for the selected reference caseQuantity Value Unit 05 · Interpretation and limits ## Engineering use ### Supported First-mode frequency agreement, period-dependent forced-roll response with 21–25 s refinement, normalized cross-case comparisons, aggregate and sectional loads, complete-cycle field evidence, and published numerical QA. ### Qualified The refined pressure case reduced the observed maximum Courant number from 0.478 to 0.326, but still exceeded its tighter configured target of 0.25. The exception remains visible in the QA report. ### Not established Three-dimensional end-wall and local impact effects, response at other fill levels or roll amplitudes, private geometry reconstruction, and vessel-level anti-roll benefit are not claims of this release. Practical consequence. Use the period sweep to identify the strongest published loading region and the validation fixture to qualify frequency prediction. Do not treat the current aggregate-wall, two-dimensional results as a final design-load or vessel-performance assessment. 06 · Measurement update and remaining gaps ## Separate the natural period from the amplitude peak The 22–24 s region is the amplitude peak for the published 5° sweep, not the natural or tuning period; phase places the exchange natural period at 14.31 s, and the amplitude peak moves with roll amplitude. Close the residual Courant exceedance below the configured 0.25 target. Add local impact-resolution where design decisions require peak pressures. Extend realistic vessel excitation beyond tank-local roll where the application requires combined motion. Browse every published case · Review the validation fixture · Compare two cases ## Tank Sloshing CFD Validation Fixture — AceEngineer URL: https://www.aceengineer.com/reports/sloshing/validation.html Description: Stable validation fixture for the published tank-sloshing CFD study: analytical frequency agreement, timestep and mesh evidence, and numerical QA boundaries. ## Engineering disposition The published solver reproduces the rectangular-tank first-mode frequency within 0.2964–0.3264% across seven accepted free-decay cases. The stationary baseline, refined forced-roll sweep, complete-cycle fields, and sectional reconstruction support comparative screening within the published model and loading envelope. This is verification evidence, not full vessel validation. ## Validation fixture at a glance 0.758054 HzAnalytical first-mode target 0.2964–0.3264%Published frequency-error range 7 casesFree-decay mesh and timestep fixture 0.783862%Two-case forced-roll exchange-amplitude mesh change ## Review checks and acceptance meaning ### Analytical agreement Measured free-decay frequencies span 0.755580–0.755807 Hz against the 0.758054 Hz linear-wave target. All seven metric records are marked pass. ### Timestep sensitivity The 0.001 s and 0.004 s cases return 0.755717 Hz and 0.755702 Hz. This supports timestep stability for the measured frequency in this benchmark. ### Mesh evidence Five free-decay meshes from 1,600 to 25,600 cells remain close to the analytical target. The release deliberately classifies the convergence study as non_asymptotic_caution. ### Forced-roll confirmation The 20,480-cell and 69,120-cell T = 24 s cases provide a two-level mesh comparison. The published exchange-amplitude change is 0.783862%. ## Numerical caveat retained and reduced The original pressure follow-on configured a maximum Courant number of 0.35 but observed 0.47841479. The new fine rerun tightened the target to 0.25 and reduced the observed maximum to 0.32648391, with 0.00280% volume drift and final-cycle changes below 0.08%. It completed and converged, but still exceeded its configured target; both records therefore retain publish_with_courant_caveat. ## Evidence matrix Question Published fixture Use Boundary Is the natural frequency reproduced? Seven free-decay cases vs. 0.758054 Hz analytical target First-mode frequency verification Linear rectangular-tank theory only Is the result stable with timestep? 0.001 s and 0.004 s free-decay cases Frequency sensitivity check Two timestep levels Is mesh dependence quantified? Five free-decay meshes; two forced-roll meshes at 24 s Screening-grade mesh evidence No demonstrated asymptotic convergence order Is the pressure follow-on numerically qualified? Original and tighter-Courant completion, conservation, cycle-change, and Courant audits Qualified comparative use Configured Courant target remains exceeded Are sectional loads internally consistent? 24 s left/right wall-patch histories reconstruct the 9.677 MN·m aggregate harmonic amplitude Sectional load review within the disclosed patch split Not a structural stress or local impact-pressure validation ## What this fixture does not validate It does not establish full-scale vessel behavior, structural stress, air-entrainment fidelity, local impact-pressure convergence, response at other fill levels or amplitudes, or anti-roll performance. Those require purpose-specific experimental or field benchmarks and additional numerical qualification. ## Traceability Source dataset record: aceengineer/digitalmodel-sloshing at revision 51ba5ddbca8dcfa8faeb6de5c592f342f32cfe2d. The release files are published on this site: release manifest. Website release digest: 1034bb4efc5d9b390d51d4d546800c5a25bf6673af824e07ed5265da038ec30b. Primary fixture tables: cases.csv, metrics.csv, derived_metrics.csv, studies.csv, and qa_audit.csv. This page is intentionally static and revision-pinned so its URL remains a consistent review fixture while interactive browsers and case selectors evolve. ## Asset integrity and fitness-for-service | AceEngineer URL: https://www.aceengineer.com/services/asset-integrity.html Description: Remaining-strength assessment of corroded components to API 579-1 and B31G, with a stated decision: accept, re-rate, take more measurements, or escalate. # Asset integrity and fitness-for-service ## The problem Whether equipment with damage is still fit to operate. ## What you receive Client receives: a remaining-strength calculation report with a stated decision: accept, re-rate, take more measurements, or escalate Remaining strength and the allowable pressure, with the assumptions traced. ## Method and codes Remaining-strength assessment of corroded components to API 579-1 and B31G. API 579-1 ## Sample sample report in preparation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Cathodic protection screening | AceEngineer URL: https://www.aceengineer.com/services/cathodic-protection.html Description: Sacrificial-anode cathodic protection screening to DNV-RP-B401 and DNV-RP-F103, subject to qualified inputs and an engineer-of-record check. # Cathodic protection screening ## What you receive Client receives: screening calculations, subject to qualified inputs and an engineer-of-record check ## Method and codes Sacrificial-anode screening to DNV-RP-B401 and DNV-RP-F103. DNV-RP-B401 ## Sample sample report in preparation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Hydrodynamics and vessel motions | AceEngineer URL: https://www.aceengineer.com/services/hydrodynamics.html Description: Wave diffraction and radiation analysis of floating hulls, compared between two solvers and delivered as a vessel motions calculation report. # Hydrodynamics and vessel motions ## The problem How a floating hull responds to waves. ## What you receive Client receives: a vessel motions calculation report ## Method and codes Wave diffraction and radiation analysis, with diffraction results compared between two solvers. ## Sample sample report in preparation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Marine installation screening | AceEngineer URL: https://www.aceengineer.com/services/marine-installation.html Description: Lifting and lowering operations screened by phase, reported as utilisation by phase and an operability limit on significant wave height. # Marine installation screening ## What you receive Client receives: utilisation by phase and an operability limit on significant wave height ## Method and codes Lifting and lowering operations screened by phase, reported as utilisation by phase and an operability limit on significant wave height. ## Sample sample report in preparation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Offshore energy data and field analytics | AceEngineer URL: https://www.aceengineer.com/services/offshore-energy-data.html Description: Well, lease and production analysis for the United States Gulf of Mexico from public regulatory filings, with drilling and completion durations per well. # Offshore energy data and field analytics ## What you receive Client receives: drilling and completion durations; per-well drilling and completion-day listings ## Method and codes Well, lease and production analysis for the United States Gulf of Mexico from public regulatory filings. ## Sample sample report in preparation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Riser analysis | AceEngineer URL: https://www.aceengineer.com/services/riser-analysis.html Description: Riser analysis and operability envelopes for drilling risers to API RP 16Q and API STD 2RD, with vortex-induced vibration screening and DNV-RP-C203 fatigue. # Riser analysis ## What you receive Client receives: an operability envelope and a riser analysis calculation report ## Method and codes Riser analysis and operability envelopes for drilling risers to API RP 16Q. Analysis against API STD 2RD, and vortex-induced vibration screening with fatigue on DNV-RP-C203 curves. API RP 16Q — Design, Selection, Operation, and Maintenance of Marine Drilling Riser Systems DNV-RP-C203 — Fatigue design of offshore steel structures ## Sample sample report in preparation Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Small-business AI and workflow automation | AceEngineer URL: https://www.aceengineer.com/small-business/ Description: Help from tax to analysis to contract negotiation to improvements, construction ideas or any administrative automation work. Houston, Texas. # AI and automation help for small businesses AI and automation help for small businesses: from tax to analysis to contract negotiation to improvements, construction ideas or any administrative automation work. Contact us for help: support@aceengineer.com. We do not prepare tax returns; that work is referred to a preparer with a PTIN. Contract support is not legal advice. ## Start with the work Tell us which steps you repeat, which inputs you use and what you need to receive. We can discuss data preparation, analysis, document workflows and administrative automation under a separately agreed scope. We can do the work and set everything up on your own computer, or deliver the workflow to your computer, so your information stays confidential on your side. ## Work so far digitalmodel contains offshore analysis and calculation workflows. worldenergydata contains public energy-data processing and reports. assetutilities contains reusable data-processing and administrative automation tools. Published datasets are available through Hugging Face. AI automation and agentic workflows · Newsletter archive Use our data that is available. If you want help with any work, whether it is automation, AI automation or workflows, let us know. Contact us support@aceengineer.com ## Codes, Standards & Maritime Law | AceEngineer Solutions URL: https://www.aceengineer.com/solutions/codes-standards-maritime-law.html Description: Codes, standards & maritime law advisory channel: standards interpretation across DNV, API, ASME, ISO and ABS, code-compliance gap reviews, and maritime liability questions. Solutions › Advisory # Codes, Standards & Maritime Law Interpreting the codes, finding the compliance gaps, and the maritime-law questions that sit alongside them — grounded in our standards knowledge base. All solutions ## Bring questions like Which clause of DNV / API / ASME / ISO / ABS governs this, and what does it require? A compliance-gap review of a calculation note or specification against a named standard. Reconciling conflicting requirements across two codes for the same component. Maritime-law and liability framing for an offshore incident or contract question. How this channel works. Advisory: an engineer engages with your question, grounded in our standards knowledge base. It is guidance, not a substitute for the governing standard or for legal advice. Runnable, standards-traced calculations live in the Subsea, Floating & Marine and Wells channels. ## Ask a standards question Explore the capabilities, then bring us the clause or compliance question you're wrestling with. Explore capabilities → ## Design & CAD | AceEngineer Solutions URL: https://www.aceengineer.com/solutions/design-cad.html Description: Design & CAD advisory channel: CAD modelling, drawing production, and parametric design automation for offshore and marine components. Solutions › Advisory # Design & CAD Turning engineering intent into models and drawings — and automating the repetitive parts. Describe the design task and an engineer engages. All solutions ## Bring questions like 3D modelling and general-arrangement drawings for an offshore or marine component. Parametric models that regenerate as inputs change — less manual redraw. Design automation linking CAD geometry to the engineering calculation behind it. Drawing-set clean-up, standardisation, and revision control. How this channel works. Advisory: bring the design task and an engineer scopes it. Where geometry ties to a calculation, it connects to the same standards-traced engine behind our runnable channels — Subsea, Floating & Marine and Wells. ## Describe a design task Explore the capabilities, then tell us what you need modelled or automated. Explore capabilities → ## Field-Development Screening & Layout | AceEngineer URL: https://www.aceengineer.com/solutions/field-development-screening.html Description: Deterministic field-development screening: layout over terrain and bathymetry, engineering screening behind the visuals, ranked historical analogs, and a small API that makes an iteration cheap. Concept selection & screening # Field-development screening and layout A client brings well locations and what they expect from the prospect. We return a laid-out field over the real terrain or bathymetry, engineering-screened, rendered as visuals, with the engineering exposed through a small API. Onshore first, then offshore. It is built to sit before the high-end tools, not instead of them — the deterministic screening pass that tells you which concepts are worth the expensive analysis. ## What it does ### Layout over real ground Assets are placed over terrain or bathymetry from verified public sources, with routing that respects the surface. Wells, manifolds, trees, jumpers, flowlines, pipelines, umbilicals and the host all live in one declarative model — so the picture and the engineering read from the same file rather than drifting apart. ### Engineering behind the visuals The screening pass runs deterministic checks, not decoration: cable sizing to IEC, erosional velocity limits per API RP 14E, and pipe-size sweeps, each emitting a one-page summary per layout iteration. Every figure traces back to the same layout model the visuals are drawn from. ### Historical analogs, ranked Past field developments are queryable as a ranked analog set — by region, water depth and asset type — so a concept can be positioned against what has actually been built rather than against an assumption. ### Iteration that stays cheap Four entry points — layout, screen, visualize, analogs — over a YAML model with overrides. Change the configuration, re-screen, re-render. Concept selection typically runs five or six models per prospect with ten to twenty iterations shown; the cost of one more iteration is what decides whether that is comfortable or painful. ### Renewables in the same model Wind turbines, offshore substations, and array and export cables use the same schema as the oil-and-gas assets, so a mixed or converted development is one model rather than two. ## What has actually been built Onshore, deepwater-FPSO and floating-wind demonstration fields all run end to end — layout, screening, scene export and animation — and are render-verified on a headless pipeline, so they regenerate reproducibly rather than existing as saved pictures. The engine is open source and MIT licensed. The terrain, bathymetry and past-project sources are public and catalogued with provenance, so the inputs can be checked as readily as the outputs. ## Honest limits This is a screening tier. It is designed to narrow a field of concepts quickly and defensibly, and it is not a substitute for detailed flow assurance, dynamic analysis or certified design. A screening estimate is not a certified deliverable, and nothing here is presented as one. The historical analog set currently covers the Gulf of Mexico with provenance enforced on every record; other regions are being added, and the coverage is stated rather than implied. Where the public data cannot support a conclusion, the output says so — that admission is the point, not a caveat bolted on afterwards. ## Floating & Marine Systems Analysis | AceEngineer URL: https://www.aceengineer.com/solutions/floating-marine.html Description: Floating & marine systems assessment topics: mooring fatigue, FPSO spread mooring, vessel seakeeping & stability, OCIMF wind/current loads, and hydrodynamics (OrcaWave / AQWA). Standards-traceable, deterministic. Solutions › Reference # Floating & Marine Systems Mooring, motions and hydrodynamics for FPSOs, floaters and vessels. This page describes the associated assessment topics. Work so far ## Assessment topics Mooring fatigue. Estimate the fatigue life of a chain or wire mooring line from its tension cycles. FPSO spread mooring. Screen a spread-mooring system for line safety factors, or run the full environmental-load equilibrium. Synthetic rope mooring. Screen a polyester fibre-rope mooring for service life — fatigue, creep and minimum tension. Vessel motions. Estimate a vessel's motions, natural periods and motion comfort (seakeeping). Stability. Check a floating platform's intact stability — GM, righting arm, wind heel. OCIMF loads. Work out wind and current mooring loads on a moored tanker. Hydrodynamics. Set up a diffraction and radiation model for a floating hull (OrcaWave / AQWA prep). Riser analysis and operability envelopes for drilling risers are assessed to API RP 16Q — Design, Selection, Operation, and Maintenance of Marine Drilling Riser Systems. The client receives an operability envelope and a riser analysis calculation report for the stated drilling-riser scope. ## Standards & methods it works to Explore the topic and review the published capability scope. OCIMF MEG4 API RP 2SK Mooring fatigue Synthetic rope Seakeeping IMO stability Diffraction (OrcaWave/AQWA) All standards See the platform engine ## Bring a real mooring or hull The floating and marine capabilities are public — open the data behind them and bring your own project numbers. Explore capabilities → ## Solutions by Domain | AceEngineer URL: https://www.aceengineer.com/solutions/ Description: Engineering reference topics by domain, with links to published capability scope and project enquiries. # Solutions by domain Reference topics by engineering domain. Published capability pages describe current scope; contact AceEngineer for project enquiries. ## Engineering reference topics Explore the assessment topics and applicable standards. REFERENCE ### Subsea, Pipelines & Integrity Wall thickness, on-bottom stability, free-span / VIV, fitness-for-service, cathodic protection. Explore REFERENCE ### Floating & Marine Systems Mooring fatigue, FPSO spread mooring, vessel seakeeping & stability, OCIMF loads, hydrodynamics. Explore REFERENCE ### Wells & Subsurface Production forecasting & decline, field NPV / economics, nodal analysis, rod-pump diagnostics. Explore ## Project enquiries Contact AceEngineer to discuss project scope and requirements. ADVISORY ### Power, Electrical & Controls Power-system studies, protection, generator & microgrid controls. Explore ADVISORY ### Codes, Standards & Maritime Law Standards interpretation, compliance gaps, maritime liability. Explore ADVISORY ### Design & CAD CAD modelling, drawings, parametric design automation. Explore ADVISORY ### Manufacturing & Fabrication Fabrication sequencing, weld/NDT planning, manufacturability. Explore Looking for something else? See how we engage (services & automation) or the energy data platform. ## Review published capabilities Review current scope or contact AceEngineer about an engineering assessment. Explore capabilities → ## Manufacturing & Fabrication | AceEngineer Solutions URL: https://www.aceengineer.com/solutions/manufacturing-fabrication.html Description: Manufacturing & fabrication advisory channel: fabrication sequencing, weld and NDT planning, and manufacturability review for offshore and marine structures. Solutions › Advisory # Manufacturing & Fabrication Getting a design built — sequencing, welding, inspection, and the manufacturability checks that save rework. Describe the scope and an engineer engages. All solutions ## Bring questions like Fabrication sequencing and build strategy for a structure or skid. Weld procedure and NDT planning aligned to the governing code. Manufacturability review — where a design will be hard or costly to build. Tolerance, fit-up and dimensional-control questions on an assembly. How this channel works. Advisory: bring the fabrication scope and an engineer scopes it. Runnable, standards-traced calculations live in the Subsea, Floating & Marine and Wells channels. ## Describe a fabrication scope Explore the capabilities, then tell us what you’re building. Explore capabilities → ## Power, Electrical & Controls | AceEngineer Solutions URL: https://www.aceengineer.com/solutions/power-electrical-controls.html Description: Power, electrical & controls advisory channel: power-system studies, protection coordination, generator and microgrid controls, and electrical area classification for offshore and energy facilities. Solutions › Advisory # Power, Electrical & Controls An advisory channel for offshore and energy electrical systems — power studies, protection, and controls. Describe the problem and an engineer engages. All solutions ## Bring questions like Power-system load flow, short-circuit and protection-coordination studies. Generator, switchgear and microgrid control philosophy and EMS logic. Electrical area classification and equipment suitability for hazardous zones. Standards alignment (IEC / IEEE / NFPA) for an offshore electrical scope. How this channel works. This is an advisory channel: you bring the problem, an engineer scopes it, and where it fits we turn it into a deliverable. Runnable, standards-traced workflows for this domain are on the roadmap — the runnable channels today are Subsea, Floating & Marine and Wells. ## Start a conversation Explore the capabilities, then describe your electrical or controls problem. Explore capabilities → ## Subsea, Pipelines & Integrity Analysis | AceEngineer URL: https://www.aceengineer.com/solutions/subsea-pipelines-integrity.html Description: Subsea, pipeline and integrity reference topics: wall thickness, on-bottom stability, free-span VIV, fitness-for-service and cathodic-protection screening. Solutions › Reference topics # Subsea, Pipelines & Integrity Reference topics for line sizing and end-of-life integrity, with cathodic-protection screening subject to qualified inputs and engineering review. Work so far ## Analysis topics Wall thickness. Screen a pipeline wall across the design codes (DNV-ST-F101, ASME B31, PD 8010) and get a one-page report. On-bottom stability. Check stability of a subsea line in waves and current (DNV-RP-F109). Free-span / VIV. Screen a free span for vortex-induced vibration and allowable length (DNV-RP-F105). Lateral & upheaval buckling. Check a line for snake buckling under pressure and temperature, and the cover a buried line needs. Fitness-for-service. Assess a corroded line from wall-thickness readings against its design pressure. Cathodic protection (screening). Sacrificial-anode demand and mass screening for offshore structures (DNV-RP-B401) and pipeline bracelet anodes (DNV-RP-F103). Project use requires qualified inputs and an engineer-of-record check; it does not establish that an installed system is protected. Fitness-for-service assessment covers remaining strength from wall-thickness readings against the design pressure. The client receives a calculation report with a stated decision: accept, re-rate, take more measurements, or escalate. ## Related standards Explore the standard and the published capability data. DNV-ST-F101 DNV-RP-F109 DNV-RP-F105 API 579 DNV-RP-B401 DNV-RP-C203 API RP 2RD / OS-F201 Catenary riser Lateral buckling Upheaval buckling (DNV-RP-F110) ASME B31.4 / B31.8 PD 8010 All standards Calculators ## Bring a real line The subsea and pipeline capabilities are public — open the data behind them and check it against your own methods. Explore capabilities → ## Wells & Subsurface Analysis & Economics | AceEngineer URL: https://www.aceengineer.com/solutions/wells-subsurface.html Description: Wells & subsurface assessment topics: production forecasting and decline (Arps), field-development economics (NPV / IRR / payback), nodal analysis, and sucker-rod-pump diagnostics. Built on public production data. Solutions › Reference # Wells & Subsurface Decline curves, field economics and well-performance assessment topics, with public production-data references. Energy data ## Assessment topics Decline & EUR. Forecast a well's decline and estimate ultimate recovery (Arps). Field economics. Run a field-development case — net present value, rate of return, payback — and a price / rate sensitivity. Nodal analysis. Find a well's operating point from inflow and outflow. Rod-pump diagnostics. Diagnose a sucker-rod pump from its dynamometer card and get a report. Production summaries. Summarise lease, well and field production from public data (BSEE, Texas RRC, SODIR), and compare wells across a block. ## Data & methods it works to Explore the method and review the published capability scope. Arps decline NPV / IRR Nodal analysis Dynamometer card BSEE (Gulf of Mexico) Texas RRC SODIR (Norway) All standards NPV calculator ## Bring a real well or field The wells, production and economics capabilities are public — open the data behind them and check it against your own. Explore capabilities → ## API 579-1 / ASME FFS-1 — Fitness-for-service assessment of in-service equipment | AceEngineer URL: https://www.aceengineer.com/standards/api-579-fitness-for-service.html Description: API 579-1 / ASME FFS-1: Fitness-for-service assessment of in-service equipment. Engineering reference scope and assessment topics. Standards › Asset integrity # API 579-1 / ASME FFS-1 Fitness-for-service assessment of in-service equipment This page describes fitness-for-service assessment of in-service equipment and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Run a Level 1 / Level 2 general and local metal-loss assessment from wall-thickness readings against the design pressure. Estimate remaining strength and the maximum allowable working pressure. State the assumptions and where a Level 3 (detailed) assessment would be needed. ## Related standards API 579-1 ASME FFS-1 Fitness-for-service Metal loss Remaining strength Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What is fitness-for-service? A quantitative check of whether equipment with damage — corrosion, cracks, dents — is still fit to operate. API 579-1/ASME FFS-1 gives the assessment levels and acceptance criteria. What assessment outputs are described? General and local metal loss at Levels 1 and 2 from wall-thickness readings against the design pressure, returning the remaining strength and the allowable pressure, with the assumptions traced. ## Discuss a API 579-1 / ASME FFS-1 assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Arps decline — Production forecasting and decline (Arps) | AceEngineer URL: https://www.aceengineer.com/standards/arps-decline-curve.html Description: Arps decline: engineering assessment reference topics and scope. Standards › Production # Arps decline Production forecasting and decline (Arps) This page describes Production forecasting and decline (Arps) and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Decline curve & EUR calculator ## Assessment topics Fit a well's history to an Arps model — exponential, hyperbolic or harmonic. Forecast future rate and estimate ultimate recovery (EUR). Report the decline parameters and the forecast assumptions. ## Why it matters Reservoir, production and asset engineers forecast estimated ultimate recovery (EUR) and remaining reserves one well at a time from rate history. Doing it consistently across a whole field — picking the decline exponent b, fitting the same way every time, and reconciling the forecast to an economic cut-off — is repetitive and easy to do subjectively. A standards-traceable Arps fit gives every well the same defensible treatment with the parameters and assumptions written down. ## The method — governing equations Arps decline-curve analysis fits the rate history to one of three empirical models and integrates to recovery at the economic rate: Rate–time (general / hyperbolic, 0 < b < 1): q(t) = qi / (1 + b · Di · t)^(1/b) Exponential (b = 0): q(t) = qi · e^(−Dit) Harmonic (b = 1): q(t) = qi / (1 + Di · t) Cumulative to an economic rate qab: Exponential: Np = (qi − qab) / Di Hyperbolic: Np = qi^(b) / ((1−b)Di) · (qi^(1−b) − qab^(1−b)) Harmonic: Np = (qi / Di) · ln(qi / qab) where qi is the initial rate, Di the initial nominal decline rate, b the decline exponent and qab the economic abandonment rate. The parameters qi, Di and b are fitted by regression to the history; EUR is the cumulative produced to date plus Np from the current rate to qab. These are the standard Arps relationships. No numeric example is shown here. ## What a screening check covers — and what it does not ### Covers Single-well, single-phase boundary-dominated (depletion) decline fits. Exponential, hyperbolic and harmonic models with fitted qi, Di, b. Forward rate forecast and EUR to a user-supplied economic rate. A parameter report with the fit assumptions stated. ### Does not cover Transient / early-time flow before boundary-dominated decline, where Arps over-forecasts. Modified-Arps terminal decline or multi-segment fits unless specified. Rate-transient, material-balance or numerical-simulation methods. Well interference, workovers, choke changes, commingled allocation, or economics and pricing. The screening assumes the history reflects established decline under roughly constant operating conditions; wells in transient flow or with operational changes need a method-of-record review. ## Related standards Arps decline EUR Exponential / hyperbolic / harmonic Decline curve Production forecast Part of Wells & Subsurface · see the platform engine ## Questions What is Arps decline-curve analysis? The standard empirical method for forecasting oil and gas production decline — exponential, hyperbolic or harmonic — and estimating ultimate recovery from the rate history. What assessment outputs are described? The fitted decline parameters, a forward rate forecast, and the estimated ultimate recovery with the assumptions stated. ## Run Arps decline on your own inputs Every capability is public — open the published dataset behind the check and read the numbers yourself. Explore capabilities → ## BSEE production data — Gulf of Mexico production data (BSEE) | AceEngineer URL: https://www.aceengineer.com/standards/bsee-gom-production-data.html Description: BSEE production data: Gulf of Mexico production data (BSEE). Engineering reference scope and assessment topics. Standards › Production # BSEE production data Gulf of Mexico production data (BSEE) This page describes gulf of mexico production data (bsee) and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Summarise lease and well oil and gas production from the public BSEE data. Compare well production across a field or block. Pull the history into a forecast or economics case. ## Related standards BSEE Gulf of Mexico Production data Lease / well Public data Part of Wells & Subsurface · see the platform engine ## Questions What is the BSEE data? The US Bureau of Safety and Environmental Enforcement publishes Gulf of Mexico lease and well production data; What can I do with it? Summarise a lease or well, compare wells across a block, and feed the history into a decline forecast or a field-economics case. ## Discuss a BSEE production data assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Catenary riser — Catenary riser shape, layback and top tension | AceEngineer URL: https://www.aceengineer.com/standards/catenary-riser.html Description: Catenary riser: Catenary riser shape, layback and top tension. Engineering reference scope and assessment topics. Standards › Riser # Catenary riser Catenary riser shape, layback and top tension This page describes catenary riser shape, layback and top tension and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Work out the catenary shape, layback and touchdown point of a riser or line. Compute the top tension and the bottom tension. Screen how shape and top tension move with weight, depth or current. ## Related standards Catenary Steel catenary riser (SCR) Top tension Layback Touchdown Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What does a catenary calculation give me? The static shape of a riser or line hanging as a catenary — the layback, the touchdown point, and the top and bottom tensions — for a given submerged weight and water depth. What is it used for? First-pass sizing of steel catenary risers and similar lines, and a sanity check before a full dynamic analysis. ## Discuss a Catenary riser assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## DNV-RP-B401 — Cathodic protection design — sacrificial anodes | AceEngineer URL: https://www.aceengineer.com/standards/dnv-rp-b401-cathodic-protection.html Description: DNV-RP-B401 sacrificial-anode screening scope, project-input qualification requirements and excluded calculation routes. Standards › Asset integrity # DNV-RP-B401 Cathodic protection design — sacrificial anodes DNV-RP-B401 is the recommended practice for sacrificial-anode cathodic-protection design. This page describes screening scope and project-use qualification requirements. Explore capabilities → ## Screening scope Work out current demand from surface areas, coating breakdown and design life. Size the sacrificial-anode mass and number, and check the final-current capacity. Screen offshore galvanic CP (DNV-RP-B401, 2021 edition as implemented): current demand, anode mass and final-current capacity for a stated configuration and coating condition. ## Related standards DNV-RP-B401 DNV-RP-F103 Cathodic protection Sacrificial anodes Coating breakdown Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What does DNV-RP-B401 cover? The design of sacrificial-anode cathodic-protection systems for offshore structures — current-density demand, coating breakdown factors, anode mass and current-capacity checks over the design life. What is the screening scope? Offshore galvanic sizing (DNV-RP-B401) and pipeline bracelet anodes (DNV-RP-F103, 2019 edition as implemented) are conditionally implemented calculation routes. They are screening tools until a project's inputs are qualified, the configuration is frozen and a named engineer checks the result. Terminal anode banks and attenuation, monopile interiors and buried zones, ICCP and current-distribution modelling are not offered. ## Explore the published screening data Every capability is public — open the published dataset behind the check and read the numbers yourself. Explore capabilities → ## DNV-RP-C203 — Fatigue design of offshore steel structures | AceEngineer URL: https://www.aceengineer.com/standards/dnv-rp-c203-fatigue.html Description: DNV-RP-C203: Fatigue design of offshore steel structures. Engineering reference scope and assessment topics. Standards › Fatigue # DNV-RP-C203 Fatigue design of offshore steel structures This page describes fatigue design of offshore steel structures and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities S-N fatigue calculator ## Assessment topics Pick the correct S-N curve for a detail (in air, seawater with or without cathodic protection) and estimate fatigue damage from a stress history. Apply stress-concentration and thickness corrections and report the governing detail. Compare a detail against DNV-RP-C203, API RP 2A and BS 7608 side by side. ## Related standards DNV-RP-C203 API RP 2A-WSD BS 7608 S-N curves Miner's rule Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What does DNV-RP-C203 cover? It is the recommended practice for fatigue design of offshore steel structures — S-N curves for welded, base-material and bolted details, stress-concentration factors, thickness effect, and the environment classes (air, seawater with and without cathodic protection). Which S-N curve should I use? The curve depends on the detail geometry, the loading direction, the environment, and whether the weld is ground or as-welded. Can you compare fatigue across standards? Yes — the same stress history can be assessed by DNV-RP-C203, API RP 2A-WSD or BS 7608 and the results shown together, so you can see how the governing curve changes. ## Discuss a DNV-RP-C203 assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## DNV-RP-F105 — Free spanning pipelines — VIV and fatigue | AceEngineer URL: https://www.aceengineer.com/standards/dnv-rp-f105-free-span-viv.html Description: DNV-RP-F105: engineering assessment reference topics and scope. Standards › Pipelines # DNV-RP-F105 Free spanning pipelines — VIV and fatigue This page describes Free spanning pipelines — VIV and fatigue and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Explore capabilities → ## Assessment topics Estimate a span's natural frequencies and screen it for cross-flow and in-line vortex-induced vibration. Work out the allowable free-span length for the seabed and flow conditions. Flag where a span needs intervention (rock dump, supports) to control fatigue. ## Why it matters Every ROV or AUV survey of an in-service pipeline returns a list of free spans where the line crosses seabed depressions. Most are harmless, but each one is a potential vortex-induced-vibration (VIV) fatigue hotspot, and rectification — rock dump or supports — is expensive vessel time. The bottleneck for an integrity engineer is triage: deciding which spans are clearly acceptable, which are clearly not, and which need a full assessment. A standards-traceable screening check against DNV-RP-F105 turns a survey span list into a ranked action list. ## The method — governing relationships RP-F105 screens a span by comparing the current-driven vortex-shedding excitation against the span's natural frequencies, then accumulating fatigue from the resulting stress cycles. The screening forms are: Natural frequency (first mode): f1 ≈ C1 · √[ (1 + CSF) · EI / (me · Leff^(4)) · (1 + Seff/Pcr + C3(δ/D)^(2)) ] Reduced velocity (VIV onset parameter): VR = Uc / (f1 · D) Fatigue damage (Miner's rule against a DNV S-N curve): Dfat = Σi ni / Ni · life = Tdesign / Dfat where C1, C3 are boundary-condition coefficients, EI the bending stiffness, me the effective mass (including added mass), Leff the effective span length, CSF the concrete-coating stiffness factor, Seff the effective axial force, Pcr the Euler buckling load, δ the static deflection and D the outer diameter. Cross-flow VIV is screened around VR ≈ 3–4 and in-line VIV at lower VR; the stress range follows from the predicted amplitude (A/D) and a unit-stress factor. Symbols and notation follow DNV-RP-F105; the relationships above are the screening forms, not the full response models. No numeric example is shown here. ## What a screening check covers — and what it does not ### Covers Single, isolated free spans on a known seabed profile. First-mode cross-flow and in-line VIV screening from steady plus wave-induced current. An allowable free-span length estimate for the given flow and support conditions. A pass / detailed-assessment / intervention flag per span with the assumptions shown. ### Does not cover Multi-span interaction or modal coupling between adjacent spans. Calibrated soil–pipe dynamic stiffness, trenching or partial-burial effects beyond simple factors. Full time-domain VIV fatigue or large-wave (Morison) direct-force fatigue. Combined loading with pressure, temperature and third-party interaction. Spans flagged near a limit should go to a full RP-F105 / finite-element assessment — the screening narrows where that effort is worth spending. ## Related standards DNV-RP-F105 Free span Vortex-induced vibration Span fatigue Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions Why are free spans a problem? Where a pipeline crosses a depression it spans unsupported; current over the span sheds vortices that make it vibrate, and the cyclic stress accumulates fatigue. DNV-RP-F105 is the recommended practice for assessing it. What is the allowable span length? The longest unsupported length that keeps vortex-induced vibration and the resulting fatigue within limits for the seabed and flow conditions. ## Run DNV-RP-F105 on your own inputs Every capability is public — open the published dataset behind the check and read the numbers yourself. Explore capabilities → ## DNV-RP-F109 — On-bottom stability design of submarine pipelines | AceEngineer URL: https://www.aceengineer.com/standards/dnv-rp-f109-on-bottom-stability.html Description: DNV-RP-F109: On-bottom stability design of submarine pipelines. Engineering reference scope and assessment topics. Standards › Pipelines # DNV-RP-F109 On-bottom stability design of submarine pipelines This page describes on-bottom stability design of submarine pipelines and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities On-bottom stability calculator ## Assessment topics Work out hydrodynamic loads on a pipeline from a sea state and current and the submerged weight it needs. Run the absolute-stability and the generalised (allowed-displacement) checks. Report the stability utilisation and the concrete-coating or weight needed to pass. ## Related standards DNV-RP-F109 On-bottom stability Hydrodynamic loads Submerged weight Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What is on-bottom stability? Whether a subsea pipeline stays put on the seabed under wave and current loads, rather than being lifted or pushed sideways. DNV-RP-F109 is the recommended practice for designing it. What drives the result? The sea state and current, the pipe's submerged weight (including any concrete coating), the seabed friction, and the allowed displacement. What governs the coating assessment? Coating and submerged-weight requirements depend on the stated stability criterion, sea state, current and seabed conditions. Project use requires qualified inputs and engineering review. ## Discuss a DNV-RP-F109 assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## DNV-ST-F101 — Submarine pipeline systems — pressure containment & wall thickness | AceEngineer URL: https://www.aceengineer.com/standards/dnv-st-f101-wall-thickness.html Description: DNV-ST-F101: Submarine pipeline systems — pressure containment & wall thickness. Engineering reference scope and assessment topics. Standards › Pipelines # DNV-ST-F101 Submarine pipeline systems — pressure containment & wall thickness This page describes submarine pipeline systems — pressure containment & wall thickness and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities Wall-thickness calculator ## Assessment topics Size a pipeline wall for design pressure (pressure containment) with fabrication and corrosion allowances. Check system collapse and propagation buckling, and combined-loading utilisation. Screen the same line across DNV-ST-F101, ASME B31 and PD 8010 in one report. ## Related standards DNV-ST-F101 ASME B31.4 / B31.8 PD 8010 Pressure containment Collapse Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What does DNV-ST-F101 govern? It is the standard for submarine pipeline systems — design, materials, construction and operation. The most-asked part is wall-thickness design — pressure containment, local buckling/collapse, and combined loading. How is the minimum wall thickness determined? From the design pressure and the pipe grade for pressure containment, plus fabrication tolerance and corrosion allowance, then verified against collapse and combined-loading limits. Can you compare design codes? Yes — wall thickness can be screened across DNV-ST-F101, ASME B31 and PD 8010 together so the code difference is explicit. ## Discuss a DNV-ST-F101 assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Dynamometer card — sucker-rod pump diagnostics | AceEngineer URL: https://www.aceengineer.com/standards/dynacard-diagnostics.html Description: Dynamometer card diagnostics for sucker-rod (beam) pumped wells: what a dynacard is, how the surface card becomes a pump card, how card signatures map to twenty named failure modes, and where the method stops being valid. Standards › Production # Dynamometer card Sucker-rod pump diagnostics from the dynamometer card Load against plunger position over one stroke — and the twenty pump conditions that draw distinguishable shapes on it. Open the signature screen See the twenty signatures ## Assessment topics Convert a measured surface (polished-rod) card to a pump card by solving the rod-string wave equation. Read pump fillage, fluid load, net and gross plunger travel off the pump card. Rank the pump card against the twenty named failure-mode signatures and show which measurements drove the match. Compute pump intake and discharge pressure, and inferred production from displacement, fillage and the runtime recorded with the card. Flag rod compression, which is where a buckling check belongs rather than a card reading. ## Why it matters Rod lift runs the long tail of onshore production — the stripper and mature wells that individually make little and collectively make a great deal. Each one carries a pumping unit whose card is recorded routinely and read rarely, because reading it well is a specialist skill and there are thousands of wells per specialist. The cost of not reading it is not subtle: a pump that has been tagging for a month is wearing a barrel out, a rod string that parted last week is producing nothing while the motor keeps turning, and a well pumped off against a starved inflow is pounding fluid into its own rods. What makes the card worth automating is that the physics is well posed. The rod string is a known elastic member with known geometry; the wave equation that governs it has been the standard treatment since Gibbs published it in 1963. Given the surface card, the rod string and the stroke rate, the pump card is computable rather than a matter of opinion — and the pump card is where the shapes live. Method, not this page's tool. The wave-equation treatment above is how a surface card is converted to a pump card. The signature screen on this site does not run it: it works on a pump card you supply or select, and compares its geometry against reference signatures. Where this page describes the method and where it describes the browser tool are different things, and the tool is the narrower of the two. ## What a dynamometer card is A dynamometer card is a closed loop of load against position over one complete pump stroke. Position runs from the bottom of the stroke to the top and back; load is the tension carried at the point of measurement. One stroke, one loop, and the loop's enclosed area is the work done on that stroke. There are two of them, and conflating them is the most common way to read a card wrong: The surface card is measured at the polished rod, between the carrier bar and the stuffing box. It is what a field dynamometer records. Its shape is dominated by the rod string — several thousand feet of steel that stretches under the fluid load, carries its own weight, has inertia, and rubs on the tubing all the way down. The pump's own behaviour is in there, superimposed on all of that. The pump card, or downhole card, is load against plunger position at the pump itself. It is not measured; it is computed. Its four corners correspond to the four events of a pump cycle: the standing valve closing and the fluid load transferring onto the travelling valve at the bottom, the plunger lifting the column to the top, the travelling valve opening and the load transferring back at the top, and the plunger falling through the fluid to the bottom again. Every failure-mode name in this method — fluid pound, gas lock, a parted rod string — describes a condition at the pump, and the shape it names is the shape it makes on the pump card. Handing a pump card to a surface-to-downhole solver is a category error: the rod string has already been taken out of it. An ideal pump card is a rectangle, and no real one is. Fluid-load transfer is not instantaneous, and it straddles the stroke turnaround — rod stretch has to be taken up while the polished rod is still decelerating. That is why a healthy card's corners are visibly cut away rather than square. A card with genuinely square corners is a modelling artefact, not a well. ## The method — governing equations ### 1. Surface card to pump card The rod string is treated as a damped elastic bar. The one-dimensional wave equation with viscous damping governs axial displacement u(x, t) along the string: ρA · ∂²u/∂t² = EA · ∂²u/∂x² − c · ∂u/∂t + Fgravity + Ffriction Wave speed: a = √(E/ρ) ≈ 16,300 ft/s for steel rods Gibbs frequency-domain solution, surface (x = 0) to pump (x = L): γ(ω) = √(−ω² + iωc) / a Upump(ω) = Usurf(ω) · cosh(γL) − Fsurf(ω) / (EAγ) · sinh(γL) The surface position and load traces are decomposed by FFT, each frequency component is propagated down the string by the expression above, and the result is transformed back to the time domain. The alternative treatment solves the same PDE directly on a spatial grid by explicit finite difference, marching from the surface to the pump at each time step; it costs more and handles tapered strings and transients better. Both are implementations of the same physics and should be run against each other on any card whose reading matters. ### 2. Fluid load and pump fillage Fluid load: F0 = (mean load, upstroke branch) − (mean load, downstroke branch) Gross plunger travel: Sgross = max(position) − min(position) — on the pump card Net plunger travel: Snet = position at the bottom-right corner − min(position) Pump fillage: Φ = 100 · Snet / Sgross Fillage is computed on the plunger stroke, never on the surface stroke. The polished rod and the plunger do not travel the same distance: rod stretch under the fluid load and rod-string overtravel put them apart by feet, not inches, on a deep well. A fillage taken against the surface stroke is wrong by the rod-string deflection, and it is wrong in the unhelpful direction — it makes a starved pump look better filled than it is, which is exactly the well you did not want to miss. The bottom-right corner is the one that matters and the one that moves. It marks where the travelling valve finishes opening on the downstroke, and on a poorly filled pump it sits well below maximum position. It is located as the point on the downstroke branch that maximises (retained stroke − remaining load) in normalised coordinates — the knee where the plunger has covered ground but the load has already gone. Read this before the next two formula blocks. Everything below depends on F0, the fluid load, which is an absolute downhole load. In a typical implementation — including the one behind this method — downhole load is scaled from surface load by a calibration factor rather than propagated through the wave equation the way position is. So pressures and inferred production inherit that calibration: on a well far from the calibration set, treat them as indicative and trust the card’s shape before its absolute load. This is restated under Named limits; it is repeated here because it qualifies the equations that follow. ### 3. Pump pressures Oil specific gravity: SGo = 141.5 / (°API + 131.5) Tubing gradient: TG = 0.433 · [SGw · WC + SGo · (1 − WC)] psi/ft Pump discharge pressure: PDP = THP + TG · hpump Pump intake pressure: PIP = PDP − F0 / Aplunger ### 4. Inferred production Gross displacement: qgross = (π/4) · D² · Sgross · N · 1440 / 9702 bbl/d Net displacement: qnet = qgross · Φ/100 Inferred production: q = qnet · (runtime hours / 24) D is the plunger diameter in inches, Sgross the gross plunger travel in inches, N the stroke rate in strokes per minute; 9,702 cubic inches make a barrel. The runtime term is not a detail: a well that cycles but is assumed to run twenty-four hours is overstated by exactly its duty factor. Runtime must come from the record taken with the card, not from a well test that may predate it by months, and where it has been assumed rather than measured that assumption belongs on the result. No worked numeric example is shown here on purpose. The signature screen computes the card measurements from a card you choose or paste, and the worked examples draw each signature with the measurements that identify it, so every figure on this site is reproducible rather than asserted. ## How signatures map to failure modes Twenty pump conditions are named in this method. They are grouped below by which measurement on the card separates them, because that grouping is the honest one: modes inside a family look alike and are told apart by one number, while modes in different families are rarely confused. ### Family 1 — fluid load shed late on the downstroke All four gouge the card's lower-right corner: the rods keep carrying fluid load past the top of the stroke and only shed it lower down. The width of that transfer window is what separates them. Mode What the card does Mechanism, and what separates it Fluid pound Full fluid load held into the downstroke, then collapsing almost vertically. The upstroke also droops slightly as the stroke proceeds. The barrel is only part filled, so the plunger falls through empty space carrying the full load until it slaps the fluid surface. The collapse is abrupt — under about a fifth of the stroke. Gas interference Load bleeds off over a long slanted lower branch; the lower-right corner is rounded away and the lower branch slopes upward with position. Free gas in the barrel must be compressed back to discharge pressure before the travelling valve can open, and compression is gradual — better than 0.4 of the stroke. Standing-valve leak Load sheds slowly down the downstroke while the top of the card stays square. Fluid bypasses the standing valve, so it cannot take the column back off the rods at the top; the rods carry part of it until the plunger out-runs the leak. Pump tagging up Same late transfer, plus a distinct impact spike at maximum position standing clear of the upstroke plateau. While the plunger is jammed against the barrel top the load cannot transfer at all; it comes off as the plunger backs away. ### Family 2 — load picked up late on the upstroke Both round away the card's top-left corner while the lower-right stays square — the mirror image of family 1. Mode What the card does Mechanism, and what separates it Travelling-valve leak Load builds slowly up the first third of the upstroke instead of arriving at the turnaround. Fluid bypasses the travelling valve at a rate set by the pressure across it, while the plunger displaces fluid at a rate set by its velocity — which is zero at the turnaround, so the leak wins outright there. Delayed travelling-valve closure An exponential pickup confined to the very start of the upstroke, then a normal card. A weak or fouled valve spring closes late. The affected window can be short enough that the card is otherwise indistinguishable from a healthy one — see the limits below. ### Family 3 — fluid load lost part-way up the upstroke Mode What the card does Mechanism, and what separates it Plunger out of barrel The upstroke falls off a cliff mid-stroke and runs flat and low to the top. The top-right corner is missing entirely. The pump is spaced so long that the plunger leaves the top of the barrel before the upstroke ends, dumping the fluid load the moment it clears. Worn barrel Upstroke load decays progressively away from the plateau; card area is lost gradually rather than at a step. A worn plunger-to-barrel fit slips more as the fluid column builds. Gradual decay, not a cliff, is what separates it from the mode above. ### Family 4 — mechanical contact at one end of the stroke These two were one label until it was noticed that they are opposite mechanisms with opposite repairs. Collapsing them loses the only thing the diagnosis is for. Mode What the card does Mechanism, and the repair Pump tagging up Load spike at maximum position, standing clear of the upstroke plateau. The plunger strikes the top of the barrel or the pull tube. Space the pump down. Pump tagging down Load dips sharply below the downstroke line at minimum position — the card reaches its own bottom-left corner, which a healthy card never does. The plunger strikes the standing valve or the bottom of the barrel and the rods go into compression. Space the pump up. ### Family 5 — the card's scale, not its shape A normalised card shape cannot see these at all. They are read off absolute load and absolute travel, which is why a card must arrive in real units to be screened for them. Mode What the card does Mechanism, and what separates it Rod parting A perfectly ordinary-looking loop — at a small fraction of the load a working string carries. Load range collapses against mean load. Below the break nothing is lifted, so the surviving string carries only its own buoyant weight plus friction and inertia. Absolute load, not shape, is the tell. Gas lock A low-load loop with almost no enclosed area: the valves never open. Gas trapped in the barrel is compressed and expanded without ever reaching discharge pressure. Extreme gas interference, past the point where the card has corners to gouge. Stuck pump Near-zero position range; a tiny collapsed card at working load. Debris, scale or mechanical obstruction stops the plunger while the unit keeps stroking. ### Family 6 — stroke length against the expected stroke These three differ only in absolute plunger travel. Under a normalised card shape they are literally the same measurement, which is why a screen that works on shape alone cannot separate them and a screen that works on real units can. Mode What the card does Mechanism, and what separates it Normal Full expected plunger travel, tight corners, flat branches. The reference case. Tubing movement An elongated card — plunger travel longer than the pump geometry accounts for, with a load slope across the loop. Unanchored tubing stretches and contracts with the fluid load. Consider a tubing anchor. Plunger undertravel A correctly-shaped card over a badly truncated position range. The plunger never travels the stroke the surface unit is making. ### Family 7 — loop thickness and load bias Mode What the card does Mechanism, and what separates it Excessive friction A thick loop: the upstroke carries extra load and the downstroke carries less, opening the card and squaring its corners. Rod-on-tubing drag, a tight stuffing box, or a deviated hole. Bent barrel Load biased with position, shifting the card's centroid off centre. The bias runs in either direction. A bent barrel binds at one end of the stroke — which end depends on the bend, so this one fault draws two mirror-image cards. ### Family 8 — the texture of the trace Roughness alone cannot separate these: sand and vibration both spoil a clean trace. Periodicity does — vibration is a wave, sand is scatter. Mode What the card does Mechanism, and what separates it Sand abrasion A jagged, aperiodic load trace over a slightly slanted card. Grains passing through the plunger-barrel fit; the fit itself wears open, which adds the slant. The jaggedness is grain-by-grain and therefore not periodic. Excessive vibration A regular high-frequency oscillation riding on an otherwise normal card. Mechanical resonance or imbalance in the surface unit — not a pump condition at all, which is worth knowing before anyone pulls a pump. Paraffin restriction Concave dents in the trace plus a raised friction signature on an otherwise normal card. Paraffin narrows the tubing and grabs the rods intermittently. The dents can be shallow enough to be lost — see the limits below. ## Where the method stops being valid ### Covers Vertical or near-vertical sucker-rod (beam) pumped wells with a steel rod string. Surface-to-pump card conversion by the damped wave equation, in the frequency domain or by finite difference. Fillage, fluid load, net and gross plunger travel, pump intake and discharge pressure from the pump card. A ranked shortlist of the twenty named signatures, with the measurements that drove the ranking shown. Inferred production from displacement, fillage and runtime, with the runtime source reported. ### Does not cover Any lift method that is not rod lift — ESP, gas lift, PCP and plunger lift are different instruments and different diagnostics. Fibreglass or composite rod strings, and highly deviated or horizontal wellbores, where the rod-string model above no longer describes the string. Confirming a fault. A signature narrows candidates; a valve check, a fluid shot and a runtime record confirm one. Predicting what production would be after an intervention. Rod, tubing or pumping-unit design, and gearbox or structural rating checks, which are separate calculations against API 11E and API RP 11L. ### Named limits, stated plainly The conversion carries empirical calibration. The damping coefficient in the frequency-domain solution is a fixed calibrated constant rather than a per-well measurement, and the downhole load is scaled by a calibration factor rather than propagated through the wave equation the way position is. On a well far from the calibration set, the pump card's shape is more trustworthy than its absolute load. Different faults draw the same card. Gas interference, fluid pound and a standing-valve leak all gut the lower-right corner. Two of them are told apart by the width of one transition, which measurement noise can move. A screen should return a shortlist; a single confident answer from a single card is a claim the card cannot support. Small, local signatures are the ones that get lost. A paraffin restriction whose dents are shallow, and a valve closure delayed over only the very bottom of the upstroke, both sit on an otherwise normal card body and can read as normal. Absence of a signature is not evidence of a healthy pump. Faults co-occur; the method assumes one at a time. A gassy well that is also pounding, or a worn barrel on a string with excessive friction, produces a card that is not any single reference signature. Stroke-length modes need the card in real units. Normal, tubing movement and plunger undertravel are indistinguishable on a normalised card shape. A card that arrives without units, or normalised for plotting, cannot be screened for them. Inferred production is only as good as the runtime. The runtime recorded with the card, not a runtime carried over from an older well test, and never a silent assumption of twenty-four hours. No accuracy figure is published for this method, deliberately. The signature library it is checked against is synthetic. Checking generated exemplars against their own generators measures self-consistency, not field performance, and quoting it as an accuracy would be a claim the evidence does not support. A number will appear here when there is a benchmark against labelled real cards to put behind it, and not before. ## References Gibbs, S. G. — “Predicting the Behavior of Sucker-Rod Pumping Systems”, Journal of Petroleum Technology, 1963. The wave-equation treatment the surface-to-pump conversion rests on. API RP 11L — Recommended Practice for Design Calculations for Sucker Rod Pumping Systems. API 11E — Specification for Pumping Units. API 11B — Sucker rods: material properties for the rod-string model. ## Related standards Dynamometer card Sucker-rod pump Fluid pound Gas interference Pump fillage Artificial lift Part of Wells & Subsurface · Arps decline · Well nodal analysis · see the platform engine ## Questions What does a dynamometer card show? Load against position over one complete pump stroke. A surface card is measured at the polished rod and is dominated by the rod string. A pump (downhole) card is what the plunger sees, and it is the card pump conditions actually draw shapes on. Why does the surface card have to be converted before it is read? The rod string is an elastic member thousands of feet long. Its stretch, inertia and damping are superimposed on whatever the pump is doing. Converting the surface card to a pump card by solving the rod-string wave equation removes the rod string so the remaining shape is the pump's. How is pump fillage calculated? Fillage is net plunger travel divided by gross plunger travel, both taken from the pump card. It is never computed on the surface stroke: rod stretch and overtravel make the polished-rod stroke a different length from the plunger stroke, and using it flatters a starved pump. Can a card signature identify a fault on its own? No. A signature narrows the candidates; it does not confirm a fault. Different faults leave the same mark — a gutted lower-right corner is drawn by gas interference, fluid pound and a standing-valve leak alike — and confirmation needs pump context such as fluid level, intake pressure, runtime and a valve check. Is there a published accuracy figure for the diagnosis? No, and that is deliberate. The signature library is synthetic, so checking it against itself measures self-consistency rather than field performance. Publishing that as an accuracy would overstate what the evidence supports. ## Read a card yourself The signature screen runs entirely in your browser on a card you select or paste, and shows every measurement it used to reach its ranking. Open the signature screen → ## Field economics (NPV / IRR) — Field-development economics — NPV, IRR, payback | AceEngineer URL: https://www.aceengineer.com/standards/field-economics-npv.html Description: Field economics (NPV / IRR): Field-development economics — NPV, IRR, payback. Engineering reference scope and assessment topics. Standards › Economics # Field economics (NPV / IRR) Field-development economics — NPV, IRR, payback This page describes field-development economics — npv, irr, payback and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities NPV field-development calculator ## Assessment topics Run a field case for net present value, internal rate of return and payback. Apply a discount rate, CAPEX/OPEX profile and a production forecast. Run a price and production-rate sensitivity on the economics. ## Related standards NPV IRR MIRR Payback Field economics Part of Wells & Subsurface · see the platform engine ## Questions What does a field-economics assessment include? A field-development case returning net present value, internal rate of return, MIRR and payback from a CAPEX/OPEX profile, a discount rate and a production forecast. Can it run sensitivities? Yes — a price and production-rate sensitivity shows how the economics move with the key uncertainties. ## Discuss a Field economics (NPV / IRR) assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## API RP 2SK — FPSO spread mooring — strength and utilisation | AceEngineer URL: https://www.aceengineer.com/standards/fpso-spread-mooring-api-rp-2sk.html Description: API RP 2SK: FPSO spread mooring — strength and utilisation. Engineering reference scope and assessment topics. Standards › Mooring # API RP 2SK FPSO spread mooring — strength and utilisation This page describes fpso spread mooring — strength and utilisation and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Screen a spread-mooring system for line tensions and safety factors (API RP 2SK). Run the environmental-load static equilibrium of the moored system. Report the most-loaded line and its utilisation against the criterion. ## Related standards API RP 2SK DNV-OS-E301 Spread mooring FPSO Line safety factor Part of Floating & Marine Systems · see the platform engine ## Questions What does API RP 2SK cover? The design and analysis of station-keeping (mooring) systems for floating structures — line tensions, safety factors, and the intact and damaged conditions. What assessment outputs are described? Line tensions and safety factors for a spread-mooring layout, the static equilibrium under environmental load, and the governing line and its utilisation. ## Discuss a API RP 2SK assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Hull diffraction — Hull hydrodynamics — diffraction, radiation and RAOs | AceEngineer URL: https://www.aceengineer.com/standards/hull-hydrodynamics-diffraction.html Description: Hull diffraction: Hull hydrodynamics — diffraction, radiation and RAOs. Engineering reference scope and assessment topics. Standards › Hydrodynamics # Hull diffraction Hull hydrodynamics — diffraction, radiation and RAOs This page describes hull hydrodynamics — diffraction, radiation and raos and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Prepare a diffraction and radiation model for a floating hull (OrcaWave / AQWA). Check added-mass and damping coefficients and their causality. Build the wave spectrum and tabulate the motion RAOs across frequency. ## Related standards Diffraction OrcaWave AQWA Added mass / damping Wave spectra Part of Floating & Marine Systems · see the platform engine ## Questions What is a diffraction analysis for? It computes how a floating hull responds to waves — added mass, damping, wave loads and the motion RAOs — the foundation for mooring, seakeeping and operability work. Which modelling tools are referenced? It sets up the input for boundary-element diffraction solvers (OrcaWave or AQWA) and checks the resulting coefficients and RAOs. ## Discuss a Hull diffraction assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Engineering Standards Reference | AceEngineer URL: https://www.aceengineer.com/standards/ Description: Engineering standards reference — DNV, API, ASME and more. Each page describes assessment topics and scope. # Engineering standards Each page below describes a standard or engineering method and its assessment topics. ## Fatigue DNV-RP-C203 ### Fatigue design of offshore steel structures Open ## Pipelines DNV-ST-F101 ### Submarine pipeline systems — pressure containment & wall thickness Open DNV-RP-F109 ### On-bottom stability design of submarine pipelines Open DNV-RP-F105 ### Free spanning pipelines — VIV and fatigue Open Lateral buckling ### Pipeline lateral (snake) buckling — DNV-RP-F110 Open Upheaval buckling ### Pipeline upheaval buckling and required cover — DNV-RP-F110 Open ## Asset integrity API 579-1 / ASME FFS-1 ### Fitness-for-service assessment of in-service equipment Open DNV-RP-B401 ### Cathodic protection design — sacrificial anodes Open ## Mooring Mooring line fatigue ### Mooring line fatigue (API RP 2SK / DNV-OS-E301) Open API RP 2SK ### FPSO spread mooring — strength and utilisation Open Synthetic rope mooring ### Synthetic (polyester) fibre-rope mooring service life Open OCIMF MEG4 ### Wind and current mooring loads on a moored tanker Open ## Hydrodynamics Vessel seakeeping ### Vessel seakeeping — motions, natural periods, comfort Open Hull diffraction ### Hull hydrodynamics — diffraction, radiation and RAOs Open ## Stability IMO intact stability ### Intact stability — GM, righting arm, wind heel Open ## Production Arps decline ### Production forecasting and decline (Arps) Open Nodal analysis ### Well nodal analysis — inflow and outflow operating point Open Dynamometer card ### Sucker-rod pump diagnostics from the dynamometer card Open BSEE production data ### Gulf of Mexico production data (BSEE) Open ## Economics Field economics (NPV / IRR) ### Field-development economics — NPV, IRR, payback Open ## Riser API RP 2RD / DNV-OS-F201 ### Riser combined-loading utilisation Open Catenary riser ### Catenary riser shape, layback and top tension Open ## Discuss an assessment Contact AceEngineer to discuss the applicable standard and project scope. Contact AceEngineer ## IMO intact stability — Intact stability — GM, righting arm, wind heel | AceEngineer URL: https://www.aceengineer.com/standards/intact-stability-imo.html Description: IMO intact stability: Intact stability — GM, righting arm, wind heel. Engineering reference scope and assessment topics. Standards › Stability # IMO intact stability Intact stability — GM, righting arm, wind heel This page describes intact stability — gm, righting arm, wind heel and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Compute metacentric height (GM) and the righting-arm (GZ) curve. Check wind-heel and area-ratio criteria against the IMO intact-stability rules. Report the governing criterion and the margin. ## Related standards IMO IS Code GM Righting arm (GZ) Wind heel Intact stability Part of Floating & Marine Systems · see the platform engine ## Questions What governs intact stability? The IMO Intact Stability (IS) Code criteria — minimum GM, righting-arm area ratios and a wind-heel check — adapted for offshore floaters and MODUs. What assessment outputs are described? GM, the GZ curve, the wind-heel and area-ratio checks, and the governing criterion with its margin. ## Discuss a IMO intact stability assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Mooring line fatigue — Mooring line fatigue (API RP 2SK / DNV-OS-E301) | AceEngineer URL: https://www.aceengineer.com/standards/mooring-line-fatigue.html Description: Mooring line fatigue: engineering assessment reference topics and scope. Standards › Mooring # Mooring line fatigue Mooring line fatigue (API RP 2SK / DNV-OS-E301) This page describes Mooring line fatigue (API RP 2SK / DNV-OS-E301) and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Mooring fatigue calculator ## Assessment topics Estimate fatigue life of a chain or wire mooring line from its tension-cycle history. Apply T-N / S-N data for the component and report the damage and the safety factor. Flag the governing line and where life falls short of the design service life. ## Why it matters A station-keeping engineer on a floating system — FPSO, FPS or semi — has to show that every mooring line survives its design service life with the code safety factor. The tension histories come out of time-domain analysis across many sea states, and the fatigue bookkeeping then runs per component: chain, wire and connector each have their own T-N data, and the line that governs is rarely obvious by inspection. A standards-traceable screening check turns a pile of tension cycles into a damage number, an implied life and a clearly identified governing segment. ## The method — governing relationships API RP 2SK and DNV-OS-E301 accumulate fatigue from the tension-range spectrum of each line against component T-N (tension–cycles-to-failure) data using Miner's rule: Tension-range counting (rainflow, per sea state): ni at tension range ΔTi, weighted by sea-state probability pj T-N curve (tension normalised by reference breaking strength): Ni = aD · (ΔTi / RBS)^(−m) Miner's-rule damage, life and acceptance: Dfat = Σi ni / Ni · life = Tservice / Dfat · accept if Dfat · FDF ≤ 1 where aD and m are the component-specific T-N intercept and slope (chain, wire rope or connector), RBS the reference breaking strength, Tservice the design service life and FDF the fatigue design factor set by the code according to component type and inspectability. The governing line or segment is the one with the highest accumulated damage. Symbols and notation follow API RP 2SK / DNV-OS-E301. No numeric example is shown here. ## What a screening check covers — and what it does not ### Covers Damage and implied life per segment from a supplied tension-cycle histogram or time series. Component T-N data for chain, wire and connectors with Miner summation. Identification of the governing line and segment. Comparison against design service life × fatigue design factor, assumptions shown. ### Does not cover The global hydrodynamic / mooring time-domain analysis that produces the tensions (upstream). Out-of-plane bending of chain at fairleads and connectors unless an OPB model and contact data are supplied. Corrosion and wear knock-downs beyond a user-supplied factor. VIV of taut lines, installation transients and thermal effects. The screening assumes the tension input represents the design environment; lines flagged near a limit warrant a full code fatigue analysis with the upstream model. ## Related standards API RP 2SK DNV-OS-E301 Mooring fatigue T-N curves Tension cycles Part of Floating & Marine Systems · see the platform engine ## Questions How is mooring fatigue estimated? From the line's tension-cycle history and the component T-N (or S-N) data, accumulating damage by Miner's rule against the design service life. Which codes apply? Offshore station-keeping codes — API RP 2SK and DNV-OS-E301 — govern mooring strength and fatigue; the component fatigue data depends on chain, wire or connector type. ## Run Mooring line fatigue on your own inputs Every capability is public — open the published dataset behind the check and read the numbers yourself. Explore capabilities → ## OCIMF MEG4 — Wind and current mooring loads on a moored tanker | AceEngineer URL: https://www.aceengineer.com/standards/ocimf-meg4-mooring-loads.html Description: OCIMF MEG4: Wind and current mooring loads on a moored tanker. Engineering reference scope and assessment topics. Standards › Mooring # OCIMF MEG4 Wind and current mooring loads on a moored tanker This page describes wind and current mooring loads on a moored tanker and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Compute wind and current load on a moored tanker from the OCIMF coefficients. Resolve longitudinal, lateral and yaw load components for a heading and environment. Feed the loads into a mooring or berthing check. ## Related standards OCIMF MEG4 Wind load Current load Moored tanker Berthing Part of Floating & Marine Systems · see the platform engine ## Questions What is OCIMF MEG4 used for? The OCIMF Mooring Equipment Guidelines give standard wind and current load coefficients for tankers, used to work out environmental mooring loads at a berth or on a moored vessel. What assessment outputs are described? The longitudinal, lateral and yaw wind and current loads for the heading and environment, ready to feed a mooring or berthing assessment. ## Discuss a OCIMF MEG4 assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Lateral buckling — Pipeline lateral (snake) buckling — DNV-RP-F110 | AceEngineer URL: https://www.aceengineer.com/standards/pipeline-lateral-buckling.html Description: Lateral buckling: Pipeline lateral (snake) buckling — DNV-RP-F110. Engineering reference scope and assessment topics. Standards › Pipelines # Lateral buckling Pipeline lateral (snake) buckling — DNV-RP-F110 This page describes pipeline lateral (snake) buckling — dnv-rp-f110 and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Screen a line's susceptibility to global lateral (snake) buckling under HP/HT. Estimate buckle spacing and the feed-in into a buckle. Flag where mitigation (sleepers, buoyancy, snaking) is needed. ## Related standards DNV-RP-F110 Lateral buckling HP/HT Global buckling Feed-in Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What is lateral buckling? A high-pressure/high-temperature line wants to expand; where it is unrestrained on the seabed it relieves that load by snaking sideways into lateral buckles. DNV-RP-F110 governs the global-buckling design. What assessment outputs are described? A susceptibility screen, an estimate of buckle spacing and feed-in, and a flag where mitigation is needed. ## Discuss a Lateral buckling assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Upheaval buckling — Pipeline upheaval buckling and required cover — DNV-RP-F110 | AceEngineer URL: https://www.aceengineer.com/standards/pipeline-upheaval-buckling.html Description: Upheaval buckling: Pipeline upheaval buckling and required cover — DNV-RP-F110. Engineering reference scope and assessment topics. Standards › Pipelines # Upheaval buckling Pipeline upheaval buckling and required cover — DNV-RP-F110 This page describes pipeline upheaval buckling and required cover — dnv-rp-f110 and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Screen a buried line for upheaval buckling from an imperfection under temperature and pressure. Work out the download (cover/rock) needed to restrain it. Report the required cover height and where rock dump is needed. ## Related standards DNV-RP-F110 Upheaval buckling Buried pipeline Cover height Rock dump Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What is upheaval buckling? A buried high-temperature line at a vertical imperfection (an overbend) can push up through its cover; the design provides enough download — soil cover or rock dump — to hold it down. DNV-RP-F110 governs it. What assessment outputs are described? An upheaval susceptibility screen and the required cover/download to restrain the line, flagging where rock dump is needed. ## Discuss a Upheaval buckling assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## API RP 2RD / DNV-OS-F201 — Riser combined-loading utilisation | AceEngineer URL: https://www.aceengineer.com/standards/riser-combined-loading.html Description: API RP 2RD / DNV-OS-F201: Riser combined-loading utilisation. Engineering reference scope and assessment topics. Standards › Riser # API RP 2RD / DNV-OS-F201 Riser combined-loading utilisation This page describes riser combined-loading utilisation and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Run a combined tension-and-bending utilisation check (API RP 2RD, working stress). Run the LRFD combined-loading utilisation check (DNV-OS-F201). Report the governing load case and the utilisation against the allowable. ## Related standards API RP 2RD DNV-OS-F201 Riser Combined loading Utilisation Part of Subsea, Pipelines & Integrity · see the platform engine ## Questions What is a riser combined-loading check? A check that a riser's combined effective tension and bending stays within the allowable — by the API RP 2RD working-stress method or the DNV-OS-F201 load-and-resistance-factor (LRFD) method. Which method should I use? API RP 2RD is the working-stress approach; DNV-OS-F201 is the LRFD approach. ## Discuss a API RP 2RD / DNV-OS-F201 assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Synthetic rope mooring — Synthetic (polyester) fibre-rope mooring service life | AceEngineer URL: https://www.aceengineer.com/standards/synthetic-rope-mooring.html Description: Synthetic rope mooring: Synthetic (polyester) fibre-rope mooring service life. Engineering reference scope and assessment topics. Standards › Mooring # Synthetic rope mooring Synthetic (polyester) fibre-rope mooring service life This page describes synthetic (polyester) fibre-rope mooring service life and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Screen a polyester fibre-rope mooring for fatigue, creep and minimum-tension limits. Estimate service life and flag the governing failure mode. Apply the fibre-rope stiffness behaviour (upper/lower bound) to the check. ## Related standards API RP 2SM DNV-OS-E301 Polyester rope Creep Minimum tension Part of Floating & Marine Systems · see the platform engine ## Questions Why are fibre-rope moorings checked differently? Polyester rope has non-linear, time-dependent stiffness and creep, so service life is governed by fatigue, creep and minimum-tension limits rather than a single break-load check. Guidance such as API RP 2SM applies. What assessment outputs are described? A service-life screen with the governing mode — fatigue, creep or minimum tension — and the assumptions on rope stiffness bounds. ## Discuss a Synthetic rope mooring assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Vessel seakeeping — Vessel seakeeping — motions, natural periods, comfort | AceEngineer URL: https://www.aceengineer.com/standards/vessel-seakeeping.html Description: Vessel seakeeping: Vessel seakeeping — motions, natural periods, comfort. Engineering reference scope and assessment topics. Standards › Hydrodynamics # Vessel seakeeping Vessel seakeeping — motions, natural periods, comfort This page describes vessel seakeeping — motions, natural periods, comfort and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Estimate vessel motions and accelerations from its RAOs and a sea state. Report roll, pitch and heave natural periods. Screen motion comfort and operability for the operation. ## Related standards Seakeeping RAOs Natural periods Motion comfort Operability Part of Floating & Marine Systems · see the platform engine ## Questions What does a seakeeping screen tell me? How a vessel moves in a sea state — motions, accelerations and natural periods — and whether motion comfort and operability limits are met for the operation. What inputs are needed? The vessel's response amplitude operators (RAOs) and the sea state (wave height, period, spectrum). ## Discuss a Vessel seakeeping assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Nodal analysis — Well nodal analysis — inflow and outflow operating point | AceEngineer URL: https://www.aceengineer.com/standards/well-nodal-analysis.html Description: Nodal analysis: Well nodal analysis — inflow and outflow operating point. Engineering reference scope and assessment topics. Standards › Production # Nodal analysis Well nodal analysis — inflow and outflow operating point This page describes well nodal analysis — inflow and outflow operating point and the associated engineering assessment topics. Project use requires qualified inputs and engineering review. Published capabilities ## Assessment topics Build the inflow (IPR) and outflow (VLP) curves for a well. Find the operating point where they intersect. Screen how the operating point moves with a change in the design. ## Related standards Nodal analysis IPR VLP Operating point Well performance Part of Wells & Subsurface · see the platform engine ## Questions What is nodal analysis? A method that finds a well's producing rate by intersecting its inflow performance (reservoir into wellbore) with its outflow performance (wellbore to surface) at a chosen node. What assessment outputs are described? The IPR and VLP curves, the operating point, and how it shifts when a design parameter changes. ## Discuss a Nodal analysis assessment Contact AceEngineer to discuss inputs, assessment scope and project requirements. Contact AceEngineer ## Engineering Methods and Assessment Scope | AceEngineer URL: https://www.aceengineer.com/vision.html Description: Engineering methods, calculation records and project-scope qualification at AceEngineer. # Where this is going Engineering assessments require qualified inputs, applicable methods and explicit limitations. Published reference pages describe the topics; project acceptance requires engineering review. ## Engineering review A calculation record identifies the governing method, source inputs and assumptions. Engineering review checks the result against the applicable criteria and stated scope. ## Assessment process Assessment scope and input quality govern the result. Define the scope — identify the engineering question and governing criteria. Qualify inputs — record sources, assumptions and limitations. Review the result — compare the assessment against the governing case and criteria. ## What we're building toward We're specific about what's real today versus on the road ahead. Today ### The engine Engineering-library reference topics and published calculation examples. Next ### More of the work, more domains Current assessment scope is described on the published capability pages. Ahead ### Design iteration From a brief to a calculation package, the checks, and the refinements — with a human engineer in the loop. ## What we won't trade away ⚖ ### Traceable Every result maps to a standard clause. 🔢 ### Deterministic Same input, same output — audit-ready. 📝 ### Shows its work Assumptions and scope on every deliverable. 🔒 ### Governed Scope, input qualification and engineering review. ## Review the published scope Published capability pages describe current scope and limitations. Explore capabilities → Or explore the platform and the work so far.