API RP 5MT-2021 pdf download

API RP 5MT-2021 pdf download.Pipeline Inspection Documents for Material Traceability and Electronic Test Reports.
1 Scope This standard is for carbon and low-alloy steel pipe and components used in the compression, pumping, and transmission of crude petroleum, petroleum products, fuel gases, carbon dioxide, nitrogen, and, where applicable, covers distribution systems. This standard applies to new assets and does not retroactively apply to in-service assets. This standard provides a method for the electronic exchange of MTR inspection documents from manufacturer to purchaser to support enhanced material traceability and records for steel line pipe, and could be applied to related steel assets. Data models for each asset type/product are provided in separate annexes; annexes for new asset types will be incrementally added to this standard as necessary. The users of this standard are purchasers (operators and distributors) and manufacturers, and it is intended that all work performed in accordance with this standard either meets or exceeds its requirements. The values stated in either U.S. Customary Units (USC) or metric units (SI) are to be regarded separately as standard. Each system is intended to be used independently of the other, without combining values in any way. While this standard is comprehensive, it may not address all issues that may arise. The absence of guidance or requirements is not to be considered prohibitive to a particular activity or approach that is based upon sound engineering judgment. For example, other industry standards, reliable engineering tests and analyses, or other established industry practices may serve as useful references to establish sound engineering judgment. 2 Normative References The following referenced documents are indispensable for the application of this standard. For dated references, only the edition cited applies. For undated references, the latest edition (including any addenda or errata) applies. API Specifcation 5L, Line Pipe (46 th Edition)
4.2 Data Interchange Options 4.2.1 General Data interchange options are methods that manufacturers may use to deliver MTR inspection document data to customer. The methods provided below are general approaches that could be implemented in various software tools. These options are not comprehensive and may be appropriated to accommodate varying circumstances in data transmission requirements. The specifc data interchange method will be agreed upon between the manufacturer and customer. 4.2.2 Delimited Text File A delimited text fle stores tabular data in a plain text format. A delimited text fle contains records with felds separated by commas or another feld delimiter. Comma-separated values (CSV) fles are a common delimited text fle, and a spreadsheet is a common application used to read CSV fles. Data transferred in this way is typically emailed or uploaded to a central portal, website, or database. 4.2.3 Web Service Web services are task-oriented subsets of application programming interfaces (APIs). These act as interfaces between two diferent software applications and are common tools used by vendors to accomplish data transmission. A web service delivers data over the Internet and exchanges information through a direct application- to-application method using XML, JSON, or other payloads via common protocols, including, but not limited to, HTTPS or SFTP. XML is a data format and markup language with defned rules for encoding documents in a format that is human- and machine-readable. JSON is a data interchange format based on JavaScript. 4.2.4 Electronic Data Interchange (EDI) EDI is a computer-to-computer exchange standard for business documents; multiple standards are available for EDI, including ASC X12. EDI is a well-established method that is used as a legal and standardized method to transfer purchasing data between vendor and customers.
4.3.2 API 5L (46 th Edition) PSL 2 Pipe To conform to this standard as it relates to API 5L (46 th Edition) pipe, Annex A shall be implemented. Alternative data model approaches are permitted (e.g., relation table structures with separate tables for various pipe characteristics), providing that all the data included within the MTR as defned by 10.1.3.2 in API 5L (46 th Edition) can be displayed and referenced. Additionally, such adaptations should reconcile the data elements defned in Table A.1.