Introduction



-233045986790Field Surveillance Incident Inspection List ComplaintCSV Layout DocumentOctober 201800Field Surveillance Incident Inspection List ComplaintCSV Layout DocumentOctober 2018Alberta Energy RegulatorField Surveillance Incident Inspection List ComplaintLayout DocumentOctober 2018Published byAlberta Energy RegulatorSuite 1000, 250 – 5 Street SWCalgary, AlbertaT2P 0R4Telephone: 403-297-8311Inquiries (toll free): 1-855-297-8311E-mail: inquiries@aer.caWebsite: aer.caContents TOC \o "1-3" \h \z \t "Appendix,1" Contents PAGEREF _Toc531593658 \h i1Introduction PAGEREF _Toc531593659 \h 11.1Overview PAGEREF _Toc531593660 \h 11.2Problem Resolution PAGEREF _Toc531593661 \h 11.3Confidentiality PAGEREF _Toc531593662 \h 11.4Disclaimer PAGEREF _Toc531593663 \h 12File Description PAGEREF _Toc531593664 \h 23File Format PAGEREF _Toc531593665 \h 1IntroductionOverviewThis document describes the characteristics and data contents of the Field Surveillance Incident Inspection List_Complaint comma delimited (CSV) file. This file contains a comprehensive listing of all complaints stored in the AER database in CSV format.Problem ResolutionIf problems are encountered with this product please email informationrequest@aer.ca. Available FormatThis product is available as a comma delimited (CSV), PDF and shapefile formats.ConfidentialityThe file is processed to exclude confidential data. Data are made available once they have been released from confidential status.DisclaimerThe AER makes no representation, warranties, or guarantees, expressed or implied, for the fitness of the data file with respect to intended use; ?accepts no responsibility for any inaccuracies, errors, or omissions in the data file; ?accepts no responsibility for any costs incurred by a company to convert, install, or improve the data file; and?makes no guarantee to the continuing availability of any data or the consistency of the format of transferred data. File DescriptionFile NameFIS_EDD_COMPLAINT_REPORT.CSVAvailabilityMonthlyFile FormatASCII file in comma delimited (CSV) formatNotes● The first line in the CSV file contains the header names● Each remaining line in the CSV file contains data for one complaint● A comma separates each valueFile FormatThe first line of the CSV file contains the header names regardless of whether the field is optional or required. Each remaining line in the file contains the data for one complaint. A comma separates each value.OrderHeader NameFormatType (Max. Length)Mandatory/OptionalDescription1Incident NumberNumeric(8)MThe unique record number2Incident Typetext (20)MThe Incident Type will always be Complaint.3LocationQTR/LSD-SEC-TWP-RGWMERtext (14)MThe Dominion Land System (DLS) designation of the location of the complaint. The complaint location may be specified at a quarter section or at the LSD. 4Location Quarternumeric (1,0)OComplaint location Quarter5Location LSDnumeric (2,0)OComplaint location LSD6Location Sectionnumeric (2,0)MComplaint location Section7Location Townshipnumeric (3,0)MComplaint location Township8Location Rangenumeric (2,0)MComplaint location Range9Location Meridiannumeric (1,0)MComplaint location Meridian10Licence Numbertext (9)OThe number of the licence issued by the AER that is associated with the complaint.11Licence Typetext (256)OThe type of licence issued by the AER, such as well, facility, or pipeline.12Incident DateDD MMM YYYYdate (11)MThe date of the complaint.13Incident Notification DateDD MMM YYYYdate (11)MThe date the AER was notified of the complaint.14Incident Complete DateDD MMM YYYYdate (11)OThe date that all the information required to effectively capture the complaint has been entered and saved in the AER database. All information about a complaint is not required when the complaint is first created and saved, but it must be subsequently entered for the complaint to be considered complete. If there is no Incident Complete Date (i.e. the Incident Complete Date is blank), the complaint information saved in the AER database is preliminary.15Source text (256)OThe AER Field Surveillance description of the installation associated with the complaint.16Cause Categorytext (20)OThe complaint cause category such as equipment failure, flaring, venting, operator error, procedural or design, etc.17Cause Typetext (20)OThe complaint cause type such as defect, emergency, vandalism, theft, etc.18Strike Areatext (8)OThe strike area for the licence.19Field Centretext (20)MThe AER Field Center having jurisdiction over the complaint.20Licensee IDtext (4)OThe licensee code on the licence at the time of the complaint.21Licensee Nametext (56)OThe current licensee name on the licence.22Source in Compliancetext (3)OIndicates whether the source of the complaint was in compliance with AER regulations.23Concern Categorytext (20)MThe category of the complaint concern, such as health, odours, etc.24Concern Typetext (40)MThe type of the complaint concern such as wildlife, seismic, H2S, etc.25Concern Categorytext (20)OThe category of the complaint concern, such as health, odours, etc.26Concern Typetext (40)OThe type of the complaint concern such as wildlife, seismic, H2S, etc.27Concern Categorytext (20)OThe category of the complaint concern, such as health, odours, etc.28Concern Typetext (40)OThe type of the complaint concern such as wildlife, seismic, H2S, etc.29Concern Categorytext (20)OThe category of the complaint concern, such as health, odours, etc.30Concern Typetext (40)OThe type of the complaint concern such as wildlife, seismic, H2S, etc.31Concern Categorytext (20)OThe category of the complaint concern, such as health, odours, etc.32Concern Typetext (40)OThe type of the complaint concern such as wildlife, seismic, H2S, etc. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download