Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
API Publ 7103 (1997): Risk Assessment for Aboveground Storage Tank Integrity — Methodology and Compliance Overview
A technical review of the pioneering risk-based inspection publication for atmospheric petroleum tanks
Introduction
API Publication 7103 (1997), titled “A Risk Assessment Approach for Evaluating the Integrity of Petroleum Product Storage Tanks”, is one of the earliest comprehensive guidelines that introduced a structured risk‑based inspection (RBI) methodology for aboveground storage tanks (ASTs). Developed by the American Petroleum Institute, this publication provides a rational framework for prioritizing inspection activities by combining the probability of failure (PoF) and the consequence of failure (CoF). Although later superseded by more detailed documents such as API RP 581 and API RP 580, API Publ 7103 remains a valuable reference for understanding the foundations of RBI for atmospheric storage tanks.
This article outlines the scope, technical requirements, implementation highlights, and compliance considerations associated with the publication. Engineers, integrity managers, and regulatory professionals will gain insight into the methodology and its role in extending tank life while maintaining safety and environmental protection.
1. Scope and Objectives
API Publ 7103 was written specifically for aboveground storage tanks storing petroleum products, crude oil, and other hydrocarbons. The document addresses tanks designed to atmospheric pressure (typically at or near ambient pressure) and constructed in accordance with API Standard 650 or API Standard 653. The key objectives of the publication are:
- To provide a systematic method for assessing the relative risk of tank failures based on design, operation, and maintenance data.
- To help operators optimize inspection intervals and resources by focusing on high‑risk tanks.
- To integrate engineering judgment with quantitative or semi‑quantitative data for decision‑making.
Tip: API Publ 7103 is intended for use as part of a broader integrity management program. It should be complemented by detailed inspection techniques such as ultrasonic testing (UT) and acoustic emission (AE).
1.1 Applicability
The publication applies to both new and existing tanks, provided sufficient data are available to perform the risk analysis. Storage vessels for non‑petroleum products (e.g., chemicals, water) are not within the original scope, although the methodology can be adapted with appropriate consequence models.
2. Technical Requirements and Methodology
The core of API Publ 7103 is a risk assessment framework that calculates a Risk Index for each tank or tank component. The index is derived from two principal factors:
- Probability of Failure (PoF): Determined by evaluating the likelihood of a leak or structural failure due to corrosion, cracking, material degradation, or external events.
- Consequence of Failure (CoF): Based on the potential impact on safety (personnel), the environment, and business operations (e.g., product loss, downtime).
2.1 Probability Factors
The PoF score considers several subcategories, each assigned a numerical rating (typically 1 to 5):
| Factor | Description | Example Inputs |
|---|---|---|
| Corrosion Rate | Internal/external corrosion rate from inspections or process data | Measured reduction in wall thickness (mm/year) |
| Design / Construction | Material of construction, design code, date of construction | Carbon steel, built to API 650 (pre‑1980s) |
| Maintenance History | Frequency and quality of previous inspections and repairs | Last internal inspection: > 10 years ago |
| Operational Conditions | Number of product‑level cycles, temperature, pressure excursions | Cycles per year, maximum operating temperature |
| Leak Detection / Protection | Presence and reliability of secondary containment, leak detection | Dike lined, no automatic leak detection |
2.2 Consequence Factors
The CoF score is built from the following categories, each weighted according to the specific site context:
| Category | Weight Range | Key Considerations |
|---|---|---|
| Product Hazard | 1 – 5 | Flash point, toxicity, persistence in the environment |
| Volume Released | 1 – 5 | Tank capacity and release rate (if leak occurs) |
| Environmental Sensitivity | 1 – 5 | Proximity to groundwater, wetlands, population |
| Safety Impact | 1 – 5 | Potential for fire, explosion, toxic exposure |
| Business / Reputation | 1 – 5 | Downtime cost, regulatory fines, public perception |
The product (PoF × CoF) yields a relative Risk Ranking that allows tanks to be sorted into categories such as Low (1–4), Medium (5–9), High (10–16), and Very High (17–25). This ranking directly informs inspection scheduling and mitigation measures.
Important limitation: API Publ 7103 uses a simplified scoring system that may not capture complex degradation mechanisms such as caustic cracking or microbiologically induced corrosion (MIC). Engineers should supplement the screening analysis with detailed mechanistic models when necessary.
3. Implementation Highlights
Applying the methodology described in API Publ 7103 involves the following key steps:
- Data Gathering: Collect tank design data, inspection records, operating history, and environmental site information. Gaps in data should be identified and addressed through targeted inspection or expert judgment.
- Risk Scoring: Use the provided worksheets (or custom software) to assign PoF and CoF scores for each tank. Ensure consistency among evaluators by using predefined criteria tables.
- Risk Ranking and Prioritization: Sort tanks by total risk score. High‑ and Very‑High‑risk tanks should be scheduled for more frequent or more detailed inspections, often within a 1–2 year horizon.
- Inspection Planning: For each tank, select appropriate NDE methods (e.g., ultrasonic thickness gauging, magnetic flux leakage for floor plates) based on the dominant failure modes indicated by the risk assessment.
- Reassessment: Update risk scores after each inspection or when significant changes in operation or condition occur. The publication recommends a full reassessment at least every 5 years.
Benefit: Facilities that adopted the API Publ 7103 approach in the late 1990s reported a 20–30% reduction in inspection costs while maintaining or improving safety integrity. The method allowed operators to “inspect smarter, not just more frequently.”
3.1 Integration with Other Standards
API Publ 7103 was designed to complement existing tank standards. It references API 653 (Tank Inspection, Repair, Alteration, and Reconstruction) for acceptance criteria and inspection frequencies. Over time, the principles were formalized in API RP 580 (Risk‑Based Inspection) and API RP 581 (RBI Technology), which provide more detailed probability and consequence models, especially for process equipment beyond storage tanks.
4. Compliance Notes
Although API Publ 7103 is a voluntary publication (not a mandatory standard), it has been recognized by several regulatory bodies as a sound engineering practice for risk‑based tank integrity programs. In the United States, for example, the EPA and state regulators have referenced RBI principles in spill‑prevention rulemakings.
- Regulatory Acceptance: Facilities that use a documented risk‑based approach conforming to the principles of API Publ 7103 may qualify for reduced inspection frequencies under some permits, provided that risk levels remain demonstrably low.
- Documentation: The publication emphasizes the importance of maintaining a written risk assessment procedure, including scoring criteria, data sources, and the rationale for any engineering overrides.
- Training: Personnel conducting risk assessments should be trained in the methodology and have a working knowledge of tank design, corrosion mechanisms, and consequence modeling.
- Lifecycle Management: The approach supports integrity management for the entire tank life, from design through decommissioning, by providing a consistent basis for decisions on repairs, retirements, and upgrades.
Caution: Relying solely on a relative risk ranking without considering absolute failure probability or specific site hazards can lead to underestimation of risk. Always cross‑validate high‑risk rankings with detailed engineering analyses.
Frequently Asked Questions (FAQs)
Q: Is API Publ 7103 still considered current by API?
A: API published the document in 1997 and has not issued a formal revision. The methodology has been largely superseded by API RP 581 (2nd/3rd editions) and API RP 580. However, many operators still use the original framework as a simple screening tool for tank fleets. API has not withdrawn the publication, but it is no longer actively promoted.
A: API published the document in 1997 and has not issued a formal revision. The methodology has been largely superseded by API RP 581 (2nd/3rd editions) and API RP 580. However, many operators still use the original framework as a simple screening tool for tank fleets. API has not withdrawn the publication, but it is no longer actively promoted.
Q: Can API Publ 7103 be applied to non‑petroleum products?
A: The publication’s consequence models are specifically tuned for hydrocarbon releases. If applied to chemicals or other fluids, the consequence factors (e.g., toxicity, environmental persistence) must be adjusted with site‑specific data. The probability assessment methodology remains generally applicable, but the weightings should be reviewed.
A: The publication’s consequence models are specifically tuned for hydrocarbon releases. If applied to chemicals or other fluids, the consequence factors (e.g., toxicity, environmental persistence) must be adjusted with site‑specific data. The probability assessment methodology remains generally applicable, but the weightings should be reviewed.
Q: How does the risk matrix in API Publ 7103 differ from the 5×5 matrix used in later API documents?
A: API Publ 7103 uses a product of the probability and consequence scores (on a 1–5 scale each) to generate a risk index, rather than a discrete categorical matrix. This allows more granular ranking. Later API standards (e.g., RP 581) adopted 5×5 matrix categories for simplicity, but both approaches yield similar prioritization when calibrated properly.
A: API Publ 7103 uses a product of the probability and consequence scores (on a 1–5 scale each) to generate a risk index, rather than a discrete categorical matrix. This allows more granular ranking. Later API standards (e.g., RP 581) adopted 5×5 matrix categories for simplicity, but both approaches yield similar prioritization when calibrated properly.
Q: Does the publication require quantitative data?
A: No. It is designed to work with semi‑quantitative data, meaning that scores can be assigned based on engineering judgment when precise measurements are unavailable. However, the accuracy of the risk ranking improves with more objective data (e.g., measured corrosion rates, ultrasonic thickness readings).
A: No. It is designed to work with semi‑quantitative data, meaning that scores can be assigned based on engineering judgment when precise measurements are unavailable. However, the accuracy of the risk ranking improves with more objective data (e.g., measured corrosion rates, ultrasonic thickness readings).