1. Scope and Purpose of API TR 755-1-2010
API TR 755-1-2010, issued by the American Petroleum Institute, is a critical Technical Report that provides comprehensive guidance for planning a structural monitoring program specifically aimed at fatigue assessment. Unlike prescriptive design codes such as API RP 2A, which dictate how a structure should be built, this Technical Report focuses on verifying the fatigue performance of an existing floating structure through direct in-service measurement.
The primary scope of API TR 755-1-2010 covers ship-shaped hulls (FPSOs, FSOs, drillships), column-stabilized units (semi-submersibles), and other floating facilities like spars and tension leg platforms (TLPs). Its purpose is to bridge the inherent gap between conservative design fatigue calculations and actual operational loading, enabling operators to make informed decisions regarding life extension, inspection scheduling, and structural repairs.
API TR 755-1-2010 is widely regarded by classification societies and regulatory bodies as a cornerstone of best-practice Structural Integrity Management (SIM). Adherence to its recommendations provides high-fidelity evidence of due diligence when managing the fatigue life of aging assets in deepwater and harsh environments.
2. Key Technical Requirements and Methodology
The technical framework of API TR 755-1-2010 mandates a rigorous screening and planning process. The operator must identify all fatigue-critical details (hot spots) throughout the hull and topsides structure. The standard requires that the monitoring plan be tailored to the specific vessel design, operational profile, and environmental conditions of the field.
Core Elements of the Structural Monitoring Plan
- Hot Spot Screening: Rigorous review of global and local finite element models to identify the top fatigue-sensitive weld details.
- Sensor Selection & Placement: Defining the type (strain gauges, accelerometers, wave radars) and precise location of sensors to capture representative stress spectra.
- Data Acquisition Strategy: Specifying sampling rates, recording durations, and trigger events (e.g., storm conditions, high loading events).
- Environmental Correlation: Correlating structural response with metocean data (wave height, period, direction).
| Component | Monitoring Parameter | Primary Sensor | Objective (per API TR 755-1-2010) |
| Hull Girder (Amidships) | Vertical bending moment | Strain gauge array | Validate global wave load predictions |
| Side Shell Longitudinals | Local hot spot stress | Weldable strain gauges | Direct fatigue damage calculation (Rainflow) |
| Deck Structure / Brackets | Complex stress state | Rosette strain gauges | Assess multiaxial fatigue contributions |
| Mooring / Hull Interface | Low-frequency motions | Accelerometer / MRU | Correlate with mooring line fatigue |
A common pitfall in applying API TR 755-1-2010 is inadequate sensor density. Monitoring only a single cross-section (e.g., amidships) can miss critical fatigue damage occurring at bow quarters or underdeck longitudinals. The report recommends a distributed network capturing vertical bending, horizontal bending, and torsional loading simultaneously.
3. Implementation Highlights and Data Analysis
Implementing a monitoring program per API TR 755-1-2010 follows a phased lifecycle. The process begins with a feasibility and planning study, followed by sensor installation (often during a scheduled dry-docking), commissioning, and long-term operational data collection. The data analysis is centered on the Rainflow counting algorithm, which extracts closed stress cycles from the raw strain time history.
The resulting stress range histograms are applied to the appropriate S-N curves (from API RP 2A or applicable class rules) to compute a “monitoring-based” fatigue damage accumulation rate. This rate is compared against the original design assumptions. If a significant deviation is observed, the design finite element model must be recalibrated against the measured data.
Phased Approach Summary
- Screening: Identify all critical fatigue locations.
- Planning: Design the sensor suite and data management system.
- Installation & Commissioning: Deploy sensors and validate baseline readings.
- Long-term Operation: Continuous data collection and periodic analysis.
- Validation & Model Update: Recalibrate FEM based on 1-2 years of measurement data.
When designing the data acquisition system under API TR 755-1-2010, engineers should plan for intermittent rather than continuous recording to manage data volume. “Storm triggering” combined with daily 20-minute snapshots provides statistically significant fatigue data without overwhelming storage and analysis resources, while still capturing the high-damage events.
4. Compliance Notes and Regulatory Integration
As a Technical Report, API TR 755-1-2010 does not impose statutory requirements by standing alone. However, it is critically important for demonstrating compliance with regulatory frameworks such as BSEE’s 30 CFR 250 requirements for Structural Integrity Management (SIM). A monitoring plan aligned with this TR provides the highest fidelity data for annual and five-year SIM assessments.
Furthermore, international classification societies (ABS, DNV, Lloyd’s Register) frequently require monitoring data in accordance with API TR 755-1-2010 to grant extensions to classification surveys or to authorize life extension beyond the original 20-year design life. The report provides the standardized framework and documentation that class surveyors expect to review in a “Fatigue Re-assessment” or “Continued Service” package.
Neglecting to implement a structured monitoring plan based on API TR 755-1-2010 can severely limit operational flexibility. Without validated fatigue data, regulators and class societies may impose strict operational restrictions—such as reduced cargo capacity or seasonal weather bans—or require extensive and costly dry-dock close-up inspections to prove structural integrity for life extension.
Frequently Asked Questions
Q: What is the main difference between API TR 755-1-2010 and API RP 2A?
A: API RP 2A provides the design rules, S-N curves, and safety factors for new structures. API TR 755-1-2010 specifically provides the guidance on how to instrument an existing floating structure to verify whether the fatigue design assumptions made using RP 2A are accurate for actual in-service operating and environmental conditions.
Q: Is API TR 755-1-2010 applicable to fixed offshore platforms (jackets)?
A: No, the scope is explicitly limited to floating structures (ship-shaped hulls, semi-submersibles, TLPs, and spars). Fixed jacket structural monitoring for fatigue is governed by different industry documents and established historical practices.
Q: How does the report address corrosion and coating degradation in the fatigue assessment?
A: The report focuses on capturing the stress history. Corrosion effects are applied analytically during the post-processing phase by selecting the appropriate S-N curve (e.g., free-corrosion vs. CP-protected curves per API RP 2A). The monitoring data provides the stress spectrum; the analyst applies the relevant environmental fatigue factor.