API Spec 11S1:1997(R2008) pdf download.Recommended Practice for Electrical Submersible Pump Teardown Report
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.
Database tables refers to all tables where data is stored within a database. A table contains a set of related data. The headings in the table are defined as the fields. The informa- tion under each heading is called a record. One of the fields should always contain a unique record. This field is defined as the PRIMARY KEY. In some cases a pair of fields form this unique record in a table. One of the fields is then defined as the SECONDARY KEY. The tables are related to each other through these keys. Descriptions of the recommended tear- down reporting for databases are split into three sections: A.3 Pertinent Data—General information related to the well and ESP. A.4 Teardown Observations—Observations by each com- ponent. A.5 Cause of the Failure—Conclusion of the primary and contributing factors resulting in the ESP failure. In Section A.3, the data not specific to the teardown obser- vations themselves have been called Pertinent Data.
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.
API Spec 11S1:1997(R2008) pdf download
PS:Thank you for your support!
