API RP 11S1:1997(R2013) pdf download.Recommended Practice for Electrical Submersible Pump Teardown Report
1 Scope
This recommended practice covers a recommended electri- cal submersible pump teardown report form. It also includes equipment schematic drawings which may provide assistance in identifying equipment components. It should be noted that these schematics are for generic equipment components, and there may be differences between manufacturers on the exact description or configuration of the assemblies.
2 Additional Information
In order to properly interpret the information gathered using this API recommended practice, the following data also should be provided: a. Equipment amp charts. b. Production data prior to failure. c. Information on any unusual conditions such as sand or scale production, power interruptions, bad weather or storms, changes in chemical treatments, etc. d. Equipment pull and run reports, service reports, and equipment test records.
This appendix provides recommended teardown observa- tion codes to facilitate the transfer and storage of electrical submersible pump teardown reporting in relational databases. The main purpose of this section is to provide a common foundation for electronic teardown reporting. Alternative methods may exist for storage that could be superior to those shown in this recommended practice. Provi- sions to read and write to files in a common format, as shown in this appendix, are recommended to permit ease in transfer- ring teardown data between software systems. Recommended table structures and data relationships are also provided, but these are not as critical to data transfer as the observation codes. Appendix B shows examples of the many potential reports that could be generated using a teardown report database by manufacturers and producers to: 1) improve ESP run lives, 2) identify operational problems, and 3) compare equipment performance.
The pertinent data have two purposes. The first is to uniquely link the equipment teardown report to a well. This same unique (primary) key can relate the teardown data to data in other data- bases. A unique well identifier (UWI) and a pull date can uniquely define a teardown as an event. This pair uniquely iden- tifies two teardowns from the same well or two ESP teardowns pulled on the same date at different locations. When used with a serial number, the ESP equipment is also uniquely identified. Secondly, pertinent data should provide information that is useful in the teardown analysis, but not normally contained or easily accessible from other databases. Much of this pertinent data regarding the well completion, production rate, and the ESP equipment are valuable to both the oil company and ESP manufacturers in determining the cause of a failure. Unfortu- nately, these external databases are not usually shared. Following a recognized standard database format allows compatibility between different database systems. This allows downloading data into a teardown database or upload- ing teardown data into larger database platforms. This standard can be either PPDM or POSC. It is left up to the program developer to decide which standard to use, since a teardown database will probably be coupled with an exist- ing database. The suggested data for proper teardown report- ing are summarized in Figures A-3 through A-5, while the relationships between the tables are shown in Figure A-1.
API RP 11S1:1997(R2013) pdf download
PS:Thank you for your support!
