Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
API MPMS Chapter 17.11 (2009): Electronic Data Interchange for Marine Vessel Cargo Measurement and Sampling
Standardizing Data Exchange for Custody Transfer of Petroleum and Liquid Chemicals
Scope and Application
API MPMS Chapter 17.11 (2009) defines the requirements for the electronic exchange of measurement and sampling data associated with cargo transfers to and from marine vessels. It is a critical component of the API Manual of Petroleum Measurement Standards (MPMS) and is intended to standardize the format, content, and communication protocols for custody transfer of crude oil, petroleum products, and liquid chemicals.
The standard applies to all parties involved in a marine cargo transfer: shippers, terminal operators, vessel owners/operators, receivers, and independent inspectors. By replacing paper-based reports with a structured electronic data interchange (EDI) format, the standard aims to reduce data entry errors, improve time-to-reconciliation, and enable seamless integration with enterprise resource planning (ERP) and terminal automation systems.
Key areas covered include:
– Data elements for cargo identification, quantities, and quality parameters
– Sampling methodology and sample identification data
– Communication mechanisms (e.g., FTP, secure email)
– File structure using comma‑separated values (CSV) or fixed‑length records
– Error handling and acknowledgment procedures
Tip: Many contracts now require compliance with API MPMS 17.11 to ensure consistency across global supply chains. Verify that your software systems can generate and parse the specified file format before operations begin.
Technical Data Elements and Message Structure
The standard defines a comprehensive set of data fields organized into logical groups. The file header identifies the sender, receiver, date, and version of the standard. Each cargo batch is represented by a series of detail records that convey vessel voyage information, tank status (before and after transfer), measured quantities, and sample details.
Mandatory Data Groups
- Vessel & Voyage: IMO number, vessel name, voyage number, port, terminal, berth, arrival/departure times.
- Cargo Measurement: Product code, observed gross volume, temperature, density or API gravity, standard volume, mass, water and sediment content (BS&W).
- Sampling: Sample ID, sampling method (manual/automatic), location (line/tank), date/time, container type.
- Status Flags: Tank status (before/after), voyage leg, seal numbers, vapor recovery status.
| Field Group | Example Fields | Data Type | Required |
|---|---|---|---|
| File Header | Sender ID, Receiver ID, File Creation Date, Version | Character, Date | Yes |
| Vessel Details | IMO Number, Vessel Name, Voyage Number | Character | Yes |
| Cargo Identification | Product Code (PPDM standard), Batch ID | Character | Yes |
| Measured Quantities | Gross Observed Volume, Temperature, Density, Standard Volume, Mass | Numeric | Yes (optional for some) |
| Sampling Results | Sample ID, Sampling Point, Method, Date/Time | Character, DateTime | Conditional |
| Status & Remarks | Before/After Transfer, Seal Numbers, Remarks | Character | Optional |
File Format and Communication
The standard recommends a flat file format (CSV or fixed-length) with a specific record layout. A typical transmission consists of a header record, multiple detail records, and a trailer record containing record counts. Communication is conducted over secure channels such as SFTP, FTPS, or encrypted email. The standard also defines basic acknowledgment messages to confirm receipt and raise errors.
Warning: Pay close attention to the required field sequence and character set (ASCII). Even a single misplaced separator can cause the entire file to be rejected by the receiving party’s validation engine.
Implementation Considerations and Benefits
Adopting API MPMS 17.11 brings significant operational advantages. The machine‑readable format eliminates manual re‑entry of data from paper reports, reducing clerical errors and accelerating the custody transfer cycle. Standardized data fields also simplify the integration of measurement data into corporate systems for inventory management, loss control, and regulatory reporting.
Implementation typically involves the following steps:
- Gap Analysis: Compare current data collection practices against the standard’s field requirements.
- Mapping: Map internal database fields to the standard’s data element names and units.
- Formatting Engine: Develop or acquire software to generate files conforming to the header/detail/trailer structure.
- Testing: Conduct end‑to‑end testing with trading partners to validate file parsing and data accuracy.
- Training: Train operations personnel on file generation, manual overrides, and exception handling.
Success Story: A major crude oil terminal reported a 40% reduction in reconciliation time and a 60% drop in data‑entry discrepancies after implementing API MPMS 17.11 with all vessel suppliers.
Compliance and Regulatory Notes
While API MPMS 17.11 is a voluntary consensus standard, compliance is frequently mandated by commercial contracts and regulatory agencies. For example, the U.S. Coast Guard (USCG) and Customs and Border Protection (CBP) may require electronic submission of cargo data that mirrors the structure defined in this standard. Similarly, many terminal operators include a requirement for EDI‑compliant data in their tariff agreements.
Key compliance considerations:
- Versioning: The 2009 edition is currently the active release. Stay alert for planned updates (the standard is periodically revised to incorporate new measurement technologies and data privacy requirements).
- Audit Trails: Retain both the transmitted file and the acknowledgment receipt as part of the custody transfer documentation.
- Validation: Use a validation tool (many are available from API or third‑party providers) to check file structure before transmission.
- Interoperability: Ensure that all trading partners agree on a common version and set of optional fields to avoid misalignment.
Important: Failure to comply with contractually imposed EDI requirements can result in cargo hold releases delayed, demurrage charges, or penalties. Always verify your system’s compliance with the latest contractual stipulations.
Frequently Asked Questions
Q: Is API MPMS 17.11 mandatory for all marine vessel cargo transfers?
A: No, it is a voluntary standard. However, many commercial contracts and terminal tariffs require its use to ensure consistent, machine‑readable data exchange. Some regulatory submissions also implicitly rely on its data structure.
A: No, it is a voluntary standard. However, many commercial contracts and terminal tariffs require its use to ensure consistent, machine‑readable data exchange. Some regulatory submissions also implicitly rely on its data structure.
Q: How does API MPMS 17.11 relate to other MPMS chapters?
A: It is closely linked to Chapter 17.1 (Marine Vessel Measurement), Chapter 17.8 (Marine Vessel Sampling), and Chapter 17.12 (Electronic Data Interchange for Marine Vessel Measurement – Draft). While 17.11 focuses on EDI format and transmission, the companion chapters define measurement methods and sampling procedures.
A: It is closely linked to Chapter 17.1 (Marine Vessel Measurement), Chapter 17.8 (Marine Vessel Sampling), and Chapter 17.12 (Electronic Data Interchange for Marine Vessel Measurement – Draft). While 17.11 focuses on EDI format and transmission, the companion chapters define measurement methods and sampling procedures.
Q: What software tools support generation of API MPMS 17.11 files?
A: Several commercial terminal automation systems and custody transfer software packages include export modules compliant with the 2009 edition. Additionally, API provides a sample file specification and some third‑party validation tools.
A: Several commercial terminal automation systems and custody transfer software packages include export modules compliant with the 2009 edition. Additionally, API provides a sample file specification and some third‑party validation tools.
Q: Are there any notable differences between the 2009 edition and earlier versions?
A: The 2009 edition clarified the handling of optional fields, added provisions for safety data, and updated the sampling data elements to align with ISO 3170/3171. It also introduced a standardized acknowledgment transaction to improve error handling.
A: The 2009 edition clarified the handling of optional fields, added provisions for safety data, and updated the sampling data elements to align with ISO 3170/3171. It also introduced a standardized acknowledgment transaction to improve error handling.
Article last updated: 2026