{"Data":[{"CodeArray":null,"CodesCriteria":"Avoid very long file names, and use only alphanumeric characters, hyphens (-), or underscores (_).","Description":"The name of a specific file included in an EDT submittal.","FieldFormat":"Avoid very long file names, and use only alphanumeric characters, hyphens (-), or underscores (_).","Obsolete":false,"MinRequired":false,"FieldName":"AttachmentFileName","ID":11730,"Identifier":"20.0020","Length":255,"RegistryFieldNumber":20.0020,"Section":"Document","Type":"Alphanumeric","XMLTag":"AttachmentFileName"},{"CodeArray":null,"CodesCriteria":"","Description":"Title or brief description of the document. If the document does not have an obvious title or one is not provided, the title can be expressed as the type of document followed by some other piece of identifying information unique to the document such as its date or author (e.g., \"Facility Site Plan Map, January 5, 2011\").","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"DocumentTitle","ID":11734,"Identifier":"20.0021","Length":255,"RegistryFieldNumber":20.0021,"Section":"Document","Type":"Alphanumeric","XMLTag":"DocumentTitle"},{"CodeArray":null,"CodesCriteria":"","Description":"Optional field to provide a more extended description of the document beyond the document title.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"DocumentDescription","ID":11735,"Identifier":"20.0022","Length":500,"RegistryFieldNumber":20.0022,"Section":"Document","Type":"Alphanumeric","XMLTag":"DocumentDescription"},{"CodeArray":null,"CodesCriteria":"","Description":"Date the document was released, published, sent, etc. Normally this value would be the date shown on the document itself.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"DateAuthored","ID":11736,"Identifier":"20.0023","Length":null,"RegistryFieldNumber":20.0023,"Section":"Document","Type":"Date","XMLTag":"DateAuthored"},{"CodeArray":null,"CodesCriteria":"Format as scheme name (http, ftp), a colon, then scheme-specific portion; encode spaces as %20.","Description":"The publically-available Uniform Resource Identifier to a submitted document.","FieldFormat":"Format as scheme name (http, ftp), a colon, then scheme-specific portion; encode spaces as %20.","Obsolete":false,"MinRequired":false,"FieldName":"Public Internet URI","ID":11737,"Identifier":"20.0024","Length":1000,"RegistryFieldNumber":20.0024,"Section":"Document","Type":"Alphanumeric","XMLTag":"PublicInternetURI"},{"CodeArray":null,"CodesCriteria":"","Description":"Date a facility owner/operator provided a document to a regulator. Facility owner/operators must have already previously gained approval to provide this type of document directly to the regulator.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"DateProvided","ID":11738,"Identifier":"20.0025","Length":null,"RegistryFieldNumber":20.0025,"Section":"Document","Type":"Date","XMLTag":"DateProvided"},{"CodeArray":null,"CodesCriteria":"","Description":"CERS ID where the document is stored. Facility owner/operators must have already previously gained approval from their regulators to store this type of document on-site.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"CERSID","ID":11739,"Identifier":"1a","Length":9,"RegistryFieldNumber":10.0011,"Section":"Document","Type":"Numeric","XMLTag":"CERSID"},{"CodeArray":null,"CodesCriteria":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301 ","Description":"A CERS-generated Universally Unique Identifier (UUID) for a specific XML submission/transaction. ","FieldFormat":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301 ","Obsolete":false,"MinRequired":false,"FieldName":"TransactionKey","ID":11753,"Identifier":"20.0002","Length":36,"RegistryFieldNumber":20.0002,"Section":"CMESubmittal","Type":"Alphanumeric","XMLTag":"TransactionKey"},{"CodeArray":null,"CodesCriteria":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301 ","Description":"A CERS-generated Universally Unique Identifier (UUID) for a specific XML submission/transaction.","FieldFormat":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301 ","Obsolete":false,"MinRequired":false,"FieldName":"TransactionKey","ID":11754,"Identifier":"20.0002","Length":36,"RegistryFieldNumber":20.0002,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"TransactionKey"},{"CodeArray":null,"CodesCriteria":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301. ","Description":"A submittter-generated Universally Unique Identifier (UUID) for a specific XML submission/transaction. The identifier must be globally unique in both the submitter\u0027s and CERS data systems. ","FieldFormat":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301. ","Obsolete":false,"MinRequired":true,"FieldName":"RegulatorTransactionKey","ID":11755,"Identifier":"20.0003","Length":36,"RegistryFieldNumber":20.0003,"Section":"CMESubmittal","Type":"Alphanumeric","XMLTag":"RegulatorTransactionKey"},{"CodeArray":null,"CodesCriteria":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301","Description":"A submitter-generated Universally Unique Identifier (UUID) for a specific XML submission/transaction. The identifier must be globally unique in both the submitter\u0027s and CERS data systems.  ","FieldFormat":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301","Obsolete":false,"MinRequired":true,"FieldName":"RegulatorTransactionKey","ID":11756,"Identifier":"20.0003 ","Length":36,"RegistryFieldNumber":20.0003,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"RegulatorTransactionKey"},{"CodeArray":null,"CodesCriteria":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301. ","Description":"A Universally Unique Identifier (UUID) assigned by the local regulator to identify a single submittal element for a facility (e.g., Inventory, UST, etc.) CERS will generate this number for submittals performed in the CERS user interface.","FieldFormat":"Represented as a 36-character hexadecimal string, such as 3F2504E0-4F89-11D3-9A0C-0305E82C3301. ","Obsolete":false,"MinRequired":true,"FieldName":"SubmittalElementRegulatorKey","ID":11757,"Identifier":"20.0004","Length":36,"RegistryFieldNumber":20.0004,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmittalKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A timestamp indicating when a regulator took an action which sets/changes the SubmittalAction field. In general this field should reflect the specific date/time a regulator made a determination about a submittal element, not the date the submittal element is uploaded into CERS (which may occur after the determination). \r\n\r\nIn the specific scenario when a regulator receives facility submittals via their own web portal and wishes to transmit to CERS a Submittal Element with a SubmittalAction value of \"Submitted\", they should set this field to the date/time the user submitted the element into the regulator\u0027s web portal (this would be the same value as SubmittedDateTime field).","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"SubmittalActionOn","ID":11888,"Identifier":"20.0006","Length":null,"RegistryFieldNumber":20.0006,"Section":"FacilitySubmittal","Type":"Date","XMLTag":"SubmittalActionOn"},{"CodeArray":null,"CodesCriteria":"","Description":"The full name (first and last) of the regulator who set/changed the SubmittalAction field. This field along with SubmittalActionAgentEmail is present to allow a facility owner/operator and the general public to know the contact information of the regulator who acted upon their submittal element. \r\n\r\nIn the specific scenario when a regulator receives facility submittals via their own web portal and wishes to transmit to CERS a Submittal Element with a SubmittalAction value of \"Received\", they should set this field to the string \"Initially Received\" and update the value with an actual agent name if/when a regulator makes a later determination changing the SubmittalAction field.\r\n\r\nFor Modified Submissions originating out of local data systems, the field should either be the name of the specific regulator who performed the modification(s), or the following value: “Staff of”","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"SubmittalActionAgentName","ID":11889,"Identifier":"20.0007","Length":80,"RegistryFieldNumber":20.0007,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmittalActionAgentName"},{"CodeArray":null,"CodesCriteria":"","Description":"The email address of the regulator who set/changed the SubmittalAction field. This field along with SubmittalActionAgentName is present to allow a facility owner/operator and the general public to know the contact information of the regulator who acted upon their submittal element. \r\n\r\nIn the specific scenario when a regulator receives facility submittals via their own web portal and wishes to transmit to CERS a Submittal Element with a SubmittalAction value of \"Submitted\", they should set this field to some specific or generic email address the business/public could send questions to, and then update the value with a more specific email address as necessary if/when a regulator makes a later determination changing the SubmittalAction field.\r\nFor Modified Submissions originating out of local data systems, the field should either be the email address of the regulator who performed the modifications in the local data system, or a generic public access email address for the agency.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"SubmittalActionAgentEmail","ID":11890,"Identifier":"20.0008","Length":240,"RegistryFieldNumber":20.0008,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmittalActionAgentEmail"},{"CodeArray":null,"CodesCriteria":"","Description":"An optional field for the regulator to provide any comments related to the action they take on a submittal element. Would typically be used to offer an explation of why a regulator set the SubmittalAction status to \"Not Acceptable\" or \"Not Applicable\".","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"SubmittalActionComments","ID":11891,"Identifier":"20.0009","Length":1500,"RegistryFieldNumber":20.0009,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmittalActionComments"},{"CodeArray":null,"CodesCriteria":"","Description":"The timestamp when the facility owner/operator provided a submittal element to the regulator. For regulators with portals, this would be the timestamp when a facility owner/operator submits an element for regulator review (SubmittalAction=\"Received\"). ","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"SubmittedOn","ID":11892,"Identifier":"20.0010","Length":null,"RegistryFieldNumber":20.0010,"Section":"FacilitySubmittal","Type":"Date","XMLTag":"SubmittedOn"},{"CodeArray":null,"CodesCriteria":"","Description":"The first name of the facility/organzation representative who provided the submittal element to the regulator. ","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"SubmitterFirstName","ID":11893,"Identifier":"20.0011","Length":80,"RegistryFieldNumber":20.0011,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmitterFirstName"},{"CodeArray":null,"CodesCriteria":"","Description":"The last name of the facility/organzation representative who provided the submittal element to the regulator. ","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"SubmitterLastName","ID":11894,"Identifier":"20.0012","Length":80,"RegistryFieldNumber":20.0012,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmitterLastName"},{"CodeArray":null,"CodesCriteria":"","Description":"The email address of the facility/organzation representative who provided the submittal element to the regulator.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"SubmitterEmail","ID":11895,"Identifier":"20.0013","Length":240,"RegistryFieldNumber":20.0013,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmitterEmail"},{"CodeArray":null,"CodesCriteria":"","Description":"A permanent 9 digit, CERS-generated code used to identify an organization responsible for one or more regulated facilities. The first digit of every OrganizationCode begins with a 9 (e.g., 900000011). Every facility/CERSID is actively associated with only one organization. When a regulator wishes to add a new facility to CERS, they should determine if the facility belongs to an organization already in CERS, and provide its OrganizationCode as part of the new facility\u0027s initial submittal.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"OrganizationCode","ID":11896,"Identifier":"20.0015","Length":9,"RegistryFieldNumber":20.0015,"Section":"FacilitySubmittal","Type":"Numeric","XMLTag":"OrganizationCode"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier required for each inspection record submitted into CERS. Used both for associating violations with a single inspection and for allowing regulators to submit updates to an inspection record at a later date. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. If not provided during initial entry in the CERS user interface, CERS will autogenerate a UUID which will become the permanent, non-editable regulator key.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"InspectionRegulatorKey","ID":11897,"Identifier":"20.0045","Length":36,"RegistryFieldNumber":20.0045,"Section":"CMESubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"InspectionRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier required for each violation record submitted into CERS. Used both for associating violations with enforcement actions and for allowing regulators to submit updates to a violation record at a later date. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged.  If not provided during initial entry in the CERS user interface, CERS will autogenerate a UUID which will become the permanent, non-editable regulator key.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"ViolationRegulatorKey","ID":11898,"Identifier":"20.0046","Length":36,"RegistryFieldNumber":20.0046,"Section":"CMESubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"ViolationRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier required for each enforcement record submitted into CERS. Used both for associating violations with enforcement actions and for allowing regulators to submit updates to an enforcement record at a later date. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged.  If not provided during initial entry in the CERS user interface, CERS will autogenerate a UUID which will become the permanent, non-editable regulator key.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"EnforcementRegulatorKey","ID":11900,"Identifier":"20.0047","Length":36,"RegistryFieldNumber":20.0047,"Section":"CMESubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"EnforcementRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier required for each record associating one violation record with one enforcement record (EnforcementViolation). Used for allowing regulators to submit updates to an EnforcementViolation record at a later date. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. If not provided during initial entry in the CERS user interface, CERS will autogenerate a UUID which will become the permanent, non-editable regulator key.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"EnforcementViolationRegulatorKey","ID":11901,"Identifier":"20.0048","Length":36,"RegistryFieldNumber":20.0048,"Section":"CMESubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"EnforcementViolationRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify a specific instance of Business Activities fields in a Facility Information submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"BizActivitiesRegulatorKey","ID":11902,"Identifier":"20.0050","Length":36,"RegistryFieldNumber":20.0050,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"BizActivitiesRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify a specific instance of Owner/Operator fields in a Facility Information submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"OwnerOperatorRegulatorKey","ID":11903,"Identifier":"20.0051","Length":36,"RegistryFieldNumber":20.0051,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"OwnerOperatorRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify a specific instance of locally-collected fields in a Facility Information submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"FacilityInformationLocalFieldsRegulatorKey","ID":11904,"Identifier":"20.0052","Length":36,"RegistryFieldNumber":20.0052,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"FacilityInformationLocalFieldsRegulatorKey"},{"CodeArray":null,"CodesCriteria":"REQUIRED","Description":"A locally-generated unique identifier used to identify a specific chemical record in a Chemical Inventory submittal element. This particular local regulator key is REQUIRED to support meaningful diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":"REQUIRED","Obsolete":false,"MinRequired":true,"FieldName":"ChemicalRegulatorKey","ID":11905,"Identifier":"20.0053","Length":36,"RegistryFieldNumber":20.0053,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"ChemicalRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify UST Facility fields in a UST submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"USTFacilityInformationRegulatorKey","ID":11906,"Identifier":"20.0054","Length":36,"RegistryFieldNumber":20.0054,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"USTFacilityInformationRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify UST Tank fields in a UST submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"USTTankRegulatorKey","ID":11907,"Identifier":"20.0055","Length":36,"RegistryFieldNumber":20.0055,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"USTTankRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify UST Monitoring Plan fields in a UST submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"USTMonitoringPlanRegulatorKey","ID":11908,"Identifier":"20.0056","Length":36,"RegistryFieldNumber":20.0056,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"USTMonitoringPlanRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify UST Certification of Installation/Modification fields in a UST submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"USTCertificationOfInstallationModificationRegulatorKey","ID":11909,"Identifier":"20.0057","Length":36,"RegistryFieldNumber":20.0057,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"USTCertificationOfInstallationModificationRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify Onsite Hazardous Waste Treatment Notification/Facility fields in a HazWaste/TP  submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"HWFacilityRegulatorKey","ID":11910,"Identifier":"20.0058","Length":36,"RegistryFieldNumber":20.0058,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"HWFacilityRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify Onsite Hazardous Waste Treatment Notification/Unit fields in a HazWaste/TP submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"HWUnitRegulatorKey","ID":11911,"Identifier":"20.0059","Length":36,"RegistryFieldNumber":20.0059,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"HWUnitRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify CESQT Unit fields in a HazWaste/TP submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"HWUnitCESQTRegulatorKey","ID":11915,"Identifier":"20.0063","Length":36,"RegistryFieldNumber":20.0063,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"HWUnitCESQTRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify Hazardous Waste Certification of Financial Assurance fields in a HazWaste/TP submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"HWCertOfFinancialAssuranceRegulatorKey","ID":11917,"Identifier":"20.0065","Length":36,"RegistryFieldNumber":20.0065,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"HWCertOfFinancialAssuranceRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify Recycling Activites fields in a Recyclable Materials Report submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"RMRActivitiesReportRegulatorKey","ID":11918,"Identifier":"20.0066","Length":36,"RegistryFieldNumber":20.0066,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"RMRActivitiesReportRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify Recyclable Material Information fields in a Recyclable Materials Report submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"RMRRecyclableMaterialRegulatorKey","ID":11919,"Identifier":"20.0067","Length":36,"RegistryFieldNumber":20.0067,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"RMRRecyclableMaterialRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify fields in a Remote Waste Consolidation Site Annual Notification submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"RWConsolidationSiteRegulatorKey","ID":11920,"Identifier":"20.0068","Length":36,"RegistryFieldNumber":20.0068,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"RWConsolidationSiteRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"The date the chemical was last updated in the CERS Chemical Library.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"LastUpdated","ID":11930,"Identifier":"20.0073","Length":null,"RegistryFieldNumber":20.0073,"Section":"ChemicalLibraryExport","Type":"Date","XMLTag":"LastUpdated"},{"CodeArray":null,"CodesCriteria":"","Description":"The CERS unique identifier UUID/GUID for a given entity.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"CERSUniqueKey","ID":11931,"Identifier":"20.0074","Length":36,"RegistryFieldNumber":20.0074,"Section":"CMESubmittalResponse","Type":"Alphanumeric","XMLTag":"CERSUniqueKey"},{"CodeArray":null,"CodesCriteria":"","Description":"The CERS unique identifier UUID/GUID for a given entity.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"CERSUniqueKey","ID":11932,"Identifier":"20.0074","Length":36,"RegistryFieldNumber":20.0074,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"CERSUniqueKey"},{"CodeArray":null,"CodesCriteria":"No length limit for this field.","Description":"In EDT response messages for processed submittals, this element provides a human readable block of text describing any guidance messages of an \"Error\" nature. Error guidance messages normally result in the rejection of the entire EDT transaction. ","FieldFormat":"No length limit for this field.","Obsolete":false,"MinRequired":false,"FieldName":"ErrorSummary","ID":11933,"Identifier":"20.0075","Length":null,"RegistryFieldNumber":20.0075,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"ErrorSummary"},{"CodeArray":null,"CodesCriteria":"No length limit for this field.","Description":"In EDT response messages for processed submittals, this element provides a human readable block of text describing any guidance messages of a \"Warning\" nature. Warning guidance is generated for records where the provided data is highly likely to have issues which the regulators should check/resolve.","FieldFormat":"No length limit for this field.","Obsolete":false,"MinRequired":false,"FieldName":"WarningSummary","ID":11944,"Identifier":"20.0076","Length":null,"RegistryFieldNumber":20.0076,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"WarningSummary"},{"CodeArray":null,"CodesCriteria":"No length limit for this field. ","Description":"In EDT response messages for processed submittals, this element provides a human readable block of text describing any guidance messages of an \"Advisory\" nature. Advisory guidance is generated for records where the provided data might result in potential issues a regulators may wish to check on. ","FieldFormat":"No length limit for this field. ","Obsolete":false,"MinRequired":false,"FieldName":"AdvisorySummary","ID":11945,"Identifier":"20.0077","Length":null,"RegistryFieldNumber":20.0077,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"AdvisorySummary"},{"CodeArray":null,"CodesCriteria":"","Description":"A CERS-defined numeric identifier for a particular type of guidance message.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Guidance Code","ID":11946,"Identifier":"20.0078","Length":null,"RegistryFieldNumber":20.0078,"Section":"FacilitySubmittalResponse","Type":"Numeric","XMLTag":"GuidanceCode"},{"CodeArray":null,"CodesCriteria":"","Description":"A permanent 4 digit, CERS-assigned code used to identify and track the actions of a specific regulator (UPA/PA). For a CUPA without any PAs, this code will always be the CUPA\u0027s code. For CUPAs with PAs, this code should reflect the UPA responsible for a submittal record.","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"RegulatorCode","ID":5600,"Identifier":"20.0001","Length":null,"RegistryFieldNumber":20.0001,"Section":"FacilitySubmittal","Type":"Numeric","XMLTag":"RegulatorCode"},{"CodeArray":null,"CodesCriteria":"XML DateTime Data Type: YYYY-MM-DDThh:mm:ss","Description":"The date/time a regulator set or changed the status of an inspection, violation, enforcement, or enforcement-violation (CME) record. Updates of CME records will only be accepted when this timestamp field is more current than the RegulatorActionDateTime value currently in CERS. ","FieldFormat":"XML DateTime Data Type: YYYY-MM-DDThh:mm:ss","Obsolete":false,"MinRequired":false,"FieldName":"RegulatorActionDateTime","ID":5601,"Identifier":"20.0040","Length":null,"RegistryFieldNumber":20.0040,"Section":"CMESubmittal","Type":"Date","XMLTag":"SubmittalSource"},{"CodeArray":null,"CodesCriteria":"","Description":"A UUID that uniquely identifies a chemical in the CERS Chemical Library.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"CERSChemicalLibraryKey","ID":11928,"Identifier":"20.0072","Length":36,"RegistryFieldNumber":20.0072,"Section":"ChemicalLibraryExport","Type":"Alphanumeric","XMLTag":"CERSChemicalLibraryKey"},{"CodeArray":null,"CodesCriteria":"","Description":"In EDT response messages for processed submittals, this field (if present) provides a CERS URL where a complete, detailed XML/ZIP package can be accessed for a given EDT transaction.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"DetailUri","ID":11951,"Identifier":"20.0083","Length":250,"RegistryFieldNumber":20.0083,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"DetailUri"},{"CodeArray":null,"CodesCriteria":"","Description":"Give a general indication of how many submittals need to be processed before an EDT transaction will be processed.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"QueuePosition","ID":11952,"Identifier":"20.0090","Length":null,"RegistryFieldNumber":20.0090,"Section":"FacilitySubmittalResponse","Type":"Numeric","XMLTag":"queuePosition"},{"CodeArray":null,"CodesCriteria":"","Description":"The Regulator\u0027s unique identifier for the Facility. Recommend using UUID but any alphanumeric value is accepted.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"FacilityRegulatorKey","ID":12703,"Identifier":"20.0084","Length":36,"RegistryFieldNumber":20.0084,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"FacilityRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify a specific supplemental documentation instance. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"DocumentRegulatorKey","ID":12712,"Identifier":"20.0085","Length":36,"RegistryFieldNumber":20.0085,"Section":"Document","Type":"Alphanumeric","XMLTag":"DocumentRegulatorKey"},{"CodeArray":null,"CodesCriteria":"","Description":"In EDT response messages for processed submittals, this element provides XML-formatted listing of guidance messages associated with an EDT transaction. Schema validation errors are NOT included in this element (only the human-readable ErrorsText field). ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"GuidanceMessage","ID":12724,"Identifier":"20.0092","Length":null,"RegistryFieldNumber":20.0092,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"GuidanceMessage"},{"CodeArray":null,"CodesCriteria":"","Description":"Businesses can provide any additional notes/comments they wish to send to the regulator concerning the submittal element. Regulators sending \"Modified Submissions\" via EDT should either detail the changes or provide the following sentence: \"There is regulator-entered information in this submission.\" ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"SubmitterComments","ID":12726,"Identifier":"20.0093","Length":1500,"RegistryFieldNumber":20.0093,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmittedByComments"},{"CodeArray":null,"CodesCriteria":"","Description":null,"FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Username","ID":12727,"Identifier":"20.0100","Length":16,"RegistryFieldNumber":20.0100,"Section":"CERS Business+Regulator Portal UI Fields","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":null,"FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Security Question","ID":12728,"Identifier":"20.0101","Length":null,"RegistryFieldNumber":20.0101,"Section":"CERS Business+Regulator Portal UI Fields","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":null,"FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Security Question Answer","ID":12729,"Identifier":"20.0102","Length":null,"RegistryFieldNumber":20.0102,"Section":"CERS Business+Regulator Portal UI Fields","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":null,"FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Password Protection Phrase","ID":12730,"Identifier":"20.0103","Length":null,"RegistryFieldNumber":20.0103,"Section":"CERS Business+Regulator Portal UI Fields","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":"The name of the business or organization that owns/operates a facility. The name is typically the legal or corporate name for the business, but may be based on some other convention depending upon the business\u0027 electronic reporting needs. For businesses reporting on only one facility, the business name and facility name are typically the same.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Organization Name","ID":12731,"Identifier":"20.0016","Length":100,"RegistryFieldNumber":20.0016,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"OrganizationName"},{"CodeArray":null,"CodesCriteria":"","Description":"The timestamp for when processing of an EDT transaction was completed.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"DataProcessedOn","ID":11948,"Identifier":"20.0080","Length":null,"RegistryFieldNumber":20.0080,"Section":"FacilitySubmittalResponse","Type":"Date","XMLTag":"DataProcessedOn"},{"CodeArray":null,"CodesCriteria":"","Description":"The timestamp when an EDT transaction was received by a CERS endpoint.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"TransactionReceived","ID":11949,"Identifier":"20.0081","Length":null,"RegistryFieldNumber":20.0081,"Section":"FacilitySubmittalResponse","Type":"Date","XMLTag":"TransactionReceived"},{"CodeArray":null,"CodesCriteria":"","Description":"Comments related to either 1) when a submitter indicates they are exempt from the supplemental documentation requirement, or 2) when a submitter indicates the supplemental documentation has already been submitted in some other submittal element.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Comment","ID":12714,"Identifier":"20.0086","Length":500,"RegistryFieldNumber":20.0086,"Section":"Document","Type":"Alphanumeric","XMLTag":"Comments"},{"CodeArray":null,"CodesCriteria":"","Description":"A regulator-assigned date when the facility owner/operator should next submit a specific submittal element. This is an optional field/feature regulator can choose to use for reporting and to trigger overdue alerts to CERS-based business users.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Next Due Date","ID":12716,"Identifier":"20.0087","Length":null,"RegistryFieldNumber":20.0087,"Section":"FacilitySubmittal","Type":"Date","XMLTag":"NextDueDate"},{"CodeArray":null,"CodesCriteria":"","Description":"A unique, CERS-assigned identifier for each hazardous material synonym listed in the CERS Chemical Library. The identifier is not used in CERS EDT as the synonym\u0027s CCLID should be reported instead (the identifier for the actual APPROVED material the synonym points to). This identifier is only to help uniquely identify specific synonym records for suggested edits/deletions.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"CERS Chemical Library Synonym ID","ID":12733,"Identifier":"20.0095","Length":50,"RegistryFieldNumber":20.0095,"Section":"ChemicalLibraryExport","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":"The synonym for an approved hazardous material in the CERS Chemical Library. Most synonyms originated from the US EPA\u0027s Substance Registry System.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Synonym Name","ID":12734,"Identifier":"20.0096","Length":100,"RegistryFieldNumber":20.0096,"Section":"ChemicalLibraryExport","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":null,"FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Lead Regulator","ID":12735,"Identifier":"20.0097","Length":null,"RegistryFieldNumber":20.0097,"Section":"CERS Business+Regulator Portal UI Fields","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":null,"FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Set Violation Actual RTC Values","ID":12736,"Identifier":"20.0098","Length":null,"RegistryFieldNumber":20.0098,"Section":"CERS Regulator Portal UI Fields","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify Recyclable Material Information fields in a Recyclable Materials Report submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"RMOffsiteGeneratorIdentificationRegulatorKey","ID":12750,"Identifier":"20.0104","Length":36,"RegistryFieldNumber":20.0104,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"RMOffsiteGeneratorIdentificationRegulatorKey"},{"CodeArray":null,"CodesCriteria":"4-digit number for General Violations, 7-digit number of Specific Violations.","Description":"4 or 7-digit Unique Identifier for each entry in the Violation Library.","FieldFormat":"4-digit number for General Violations, 7-digit number of Specific Violations.","Obsolete":false,"MinRequired":false,"FieldName":"Violation Type Number","ID":12768,"Identifier":"20.0409","Length":7,"RegistryFieldNumber":20.0409,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"TypeNumber"},{"CodeArray":null,"CodesCriteria":"","Description":"Name of the Violation.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Violation Name","ID":12769,"Identifier":"20.0410","Length":1000,"RegistryFieldNumber":20.0410,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Name"},{"CodeArray":null,"CodesCriteria":"","Description":"Description of the Violation.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Violation Description","ID":12770,"Identifier":"20.0411","Length":null,"RegistryFieldNumber":20.0411,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Description"},{"CodeArray":null,"CodesCriteria":"","Description":"Violation Category.  The Violation Category is already reflected in digits 3 and 4 of the Violation Type Number.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Violation Category","ID":12771,"Identifier":"20.0412","Length":100,"RegistryFieldNumber":20.0412,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Category"},{"CodeArray":null,"CodesCriteria":"","Description":"Violation Program Element.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Violation Program Element","ID":12772,"Identifier":"20.0110","Length":100,"RegistryFieldNumber":20.0110,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"ProgramElement"},{"CodeArray":null,"CodesCriteria":"","Description":"Chapter of the Source where the Citation is located.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Citation Chapter","ID":12773,"Identifier":"20.0405","Length":10,"RegistryFieldNumber":20.0405,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Chapter"},{"CodeArray":null,"CodesCriteria":"","Description":"Cited section from the source for the citation.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Citation Section","ID":12774,"Identifier":"20.0406","Length":100,"RegistryFieldNumber":20.0406,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Section"},{"CodeArray":null,"CodesCriteria":"","Description":"Name of the Violation Citation. [deprecated]","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Citation Name","ID":12775,"Identifier":"20.0407","Length":100,"RegistryFieldNumber":20.0407,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Name"},{"CodeArray":null,"CodesCriteria":"","Description":"Additional notes, description, and/or history related to the citation.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Citation Description","ID":12776,"Identifier":"20.0408","Length":255,"RegistryFieldNumber":20.0408,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Description"},{"CodeArray":null,"CodesCriteria":"","Description":"Name of the Source where the Violation Citation\u0027s Section was cited.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Citation Source","ID":12777,"Identifier":"20.0115","Length":100,"RegistryFieldNumber":20.0115,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":"Source"},{"CodeArray":null,"CodesCriteria":"","Description":"Comments about the Violation Library entry.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Violation Comments","ID":12778,"Identifier":"20.0116","Length":1000,"RegistryFieldNumber":20.0116,"Section":"ViolationLibraryExport","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":"Date the Violation Library entry is effective (first available for use).","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Violation Begin Date","ID":12779,"Identifier":"20.0117","Length":10,"RegistryFieldNumber":20.0117,"Section":"ViolationLibraryExport","Type":"Date","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":"Last date the Violation Library entry was available for use.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Violation End Date","ID":12780,"Identifier":"20.0118","Length":10,"RegistryFieldNumber":20.0118,"Section":"ViolationLibraryExport","Type":"Date","XMLTag":null},{"CodeArray":null,"CodesCriteria":"No length limit for this field.","Description":"In EDT response messages for processed submittals, this element provides a human readable block of text describing any guidance messages of an \"Required\" nature. Required guidance is generated for records where the provided data might result in potential issues a regulators may wish to check on.","FieldFormat":"No length limit for this field.","Obsolete":false,"MinRequired":false,"FieldName":"RequiredSummary","ID":12783,"Identifier":"20.0119","Length":null,"RegistryFieldNumber":20.0119,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"RequiredSummary"},{"CodeArray":null,"CodesCriteria":"","Description":"Include any comments that explains why the Regulator is creating an additional/duplicate facility at the same address.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Comments","ID":12784,"Identifier":"20.0104","Length":500,"RegistryFieldNumber":20.0104,"Section":"Regulator Facility Create","Type":"Alphanumeric","XMLTag":"Comments"},{"CodeArray":null,"CodesCriteria":"true/false","Description":null,"FieldFormat":"true/false","Obsolete":false,"MinRequired":false,"FieldName":"IgnoreExactDuplicateAddressWarnings","ID":12785,"Identifier":"20.0122","Length":null,"RegistryFieldNumber":20.0122,"Section":"Regulator Facility Create","Type":"Alphanumeric","XMLTag":"IgnoreExactDuplicateAddressWarnings"},{"CodeArray":null,"CodesCriteria":"","Description":"Additional information (such as corporate office location, etc) to assist in making a Organization or Business name unique. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Organization Headquarters","ID":12786,"Identifier":"20.0106","Length":75,"RegistryFieldNumber":20.0106,"Section":"Regulator Facility Create","Type":"Alphanumeric","XMLTag":"OrganizationHeadquarters"},{"CodeArray":null,"CodesCriteria":"Commit = Commit the data\r\nTrial = No not commit the data, but report back what might occur.","Description":"Instructs services to actually commit the data, or to essentially do a trial run to see what might result from the action.","FieldFormat":"Commit = Commit the data\r\nTrial = No not commit the data, but report back what might occur.","Obsolete":false,"MinRequired":false,"FieldName":"Transaction Mode","ID":12787,"Identifier":"20.0107","Length":null,"RegistryFieldNumber":20.0107,"Section":"Regulator Facility Create","Type":"Alphanumeric","XMLTag":"mode"},{"CodeArray":null,"CodesCriteria":"","Description":"The numeric identifier part of a postal address. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Street Range","ID":12788,"Identifier":"20.0108","Length":null,"RegistryFieldNumber":20.0108,"Section":"Regulator Facility Create Response","Type":"Alphanumeric","XMLTag":"StreetRange"},{"CodeArray":null,"CodesCriteria":"","Description":"The direction (north, west, east, south, etc) as it occurs before the street name. For example, 1001 E. I St.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Street PreDirection","ID":12789,"Identifier":"20.0109","Length":null,"RegistryFieldNumber":20.0109,"Section":"Regulator Facility Create Response","Type":"Alphanumeric","XMLTag":"StreetPreDirection"},{"CodeArray":null,"CodesCriteria":"","Description":"The name of the street.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Street Name","ID":12790,"Identifier":"20.0110","Length":null,"RegistryFieldNumber":20.0110,"Section":"Regulator Facility Create Response","Type":"Alphanumeric","XMLTag":"StreetName"},{"CodeArray":null,"CodesCriteria":"","Description":"The direction (north, east, west, south, etc) that appears after the name of the street. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Street PostDirection","ID":12791,"Identifier":"20.0111","Length":null,"RegistryFieldNumber":20.0111,"Section":"Regulator Facility Create Response","Type":"Alphanumeric","XMLTag":"StreetPostDirection"},{"CodeArray":null,"CodesCriteria":"","Description":"The suffix of a street (Wy, St, Blvd, etc.)","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"StreetSuffx","ID":12792,"Identifier":"20.0112","Length":null,"RegistryFieldNumber":20.0112,"Section":"Regulator Facility Create Response","Type":"Alphanumeric","XMLTag":"StreetSuffix"},{"CodeArray":null,"CodesCriteria":"","Description":"The date the facility was created in CERS. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Established On","ID":12793,"Identifier":"20.0113","Length":null,"RegistryFieldNumber":20.0113,"Section":"Regulator Facility Create Response","Type":"Date","XMLTag":"EstablishedOn"},{"CodeArray":null,"CodesCriteria":"","Description":"Indicates the likelihood of duplicity of the address against the address specified. Scale is 0 to 100. With 0 being least likely, and 100 being very confident. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Duplicity Score","ID":12794,"Identifier":"20.0114","Length":null,"RegistryFieldNumber":20.0114,"Section":"Regulator Facility Create Response","Type":"Numeric","XMLTag":"score"},{"CodeArray":null,"CodesCriteria":"","Description":null,"FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"ExcludeNotApplicableFacilities","ID":12795,"Identifier":"20.0120","Length":null,"RegistryFieldNumber":20.0120,"Section":"CERS Regulator Portal UI Fields","Type":"Alphanumeric","XMLTag":null},{"CodeArray":null,"CodesCriteria":"","Description":"A locally-generated unique identifier used to identify APSA Facility Information fields in an APSA submittal element. Although not required, regulators using EDT are encouraged to supply and track this field so CERS can provide more specific diagnostic/error reporting. Although any unique alphanumeric string is allowable, a Universally Unique Identifier (UUID) is encouraged.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"APSAFacilityInformationRegulatorKey","ID":12834,"Identifier":"20.413","Length":36,"RegistryFieldNumber":20.0413,"Section":"FacilitySubmittalLocalRegulatorKeys","Type":"Alphanumeric","XMLTag":"APSAFacilityInformationRegulatorKey"},{"CodeArray":" = Queued| = Accepted| = Rejected","CodesCriteria":" = Queued  = Accepted  = Rejected ","Description":"Status of an EDT transaction.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Transaction Status","ID":11950,"Identifier":"20.0082","Length":25,"RegistryFieldNumber":20.0082,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"TransactionStatus"},{"CodeArray":"1 = Cancer|2 = Developmental (M/F)|3 = Developmental (M)|4 = Developmental (F)","CodesCriteria":"1 = Cancer 2 = Developmental (M/F) 3 = Developmental (M) 4 = Developmental (F) ","Description":"A comma-separated list of Proposition 65 toxicity types associated with the chemical/mixture. More information is available at http://www.oehha.ca.gov/prop65.html","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Proposition 65 Toxicity Type","ID":12732,"Identifier":"20.0094","Length":null,"RegistryFieldNumber":20.0094,"Section":"ChemicalLibraryExport","Type":"Alphanumeric","XMLTag":null},{"CodeArray":"1 = Draft|2 = Approved|3 = Deleted","CodesCriteria":"1 = Draft 2 = Approved 3 = Deleted ","Description":"This field indicates the status of a new or updated inspection, violation, enforcement, or enforcement-violation (CME) record. The normal value for new or updated submissions would be \"Approved.\" The \"Deleted\" status would be used when a regulator wants to remove a CME record from CERS (e.g., record was sent in error).","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"Data Entry Status","ID":5602,"Identifier":"20.0041","Length":25,"RegistryFieldNumber":20.0041,"Section":"CMESubmittal","Type":"Alphanumeric","XMLTag":"CMEDataStatus"},{"CodeArray":"1 = Draft|2 = Submitted|3 = Under Review|4 = Accepted|5 = Not Accepted|6 = Not Applicable|8 = Certified","CodesCriteria":"1 = Draft 2 = Submitted 3 = Under Review 4 = Accepted 5 = Not Accepted 6 = Not Applicable 8 = Certified ","Description":"The current status of a submittal element. \"Draft\" is for internal CERS use only--CERS EDT will never accept or emit submittal elements of status \"draft.\" ","FieldFormat":null,"Obsolete":false,"MinRequired":true,"FieldName":"Submittal Action (Submittal Status)","ID":11887,"Identifier":"20.0005","Length":25,"RegistryFieldNumber":20.0005,"Section":"FacilitySubmittal","Type":"Alphanumeric","XMLTag":"SubmittalAction"},{"CodeArray":"1 = Facility Information|2 = Hazardous Materials Inventory|3 = Emergency Response and Training Plans|4 = Underground Storage Tanks|5 = Onsite Hazardous Waste Treatment Notification|6 = Recyclable Materials Report|7 = Remote Waste Consoidations Annual Notification|8 = Hazardous Waste Tank Closure Certification|9 = Aboveground Petroleum Storage Tanks|10 = California Accidental Release Program","CodesCriteria":"1 = Facility Information 2 = Hazardous Materials Inventory 3 = Emergency Response and Training Plans 4 = Underground Storage Tanks 5 = Onsite Hazardous Waste Treatment Notification 6 = Recyclable Materials Report 7 = Remote Waste Consoidations Annual Notification 8 = Hazardous Waste Tank Closure Certification 9 = Aboveground Petroleum Storage Tanks 10 = California Accidental Release Program ","Description":"A code identifying a Submittal Element type. This is an attribute on the SubmittalElement XML element used in the Submittal Action Update Notification XML Schema. It is also used as an element to indicate if a document has been provided in some other submittal element. ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Submittal Element Code","ID":12713,"Identifier":"20.0071","Length":null,"RegistryFieldNumber":20.0071,"Section":"Document","Type":"Numeric","XMLTag":"SubmittalElementCode"},{"CodeArray":"1 = Facility Information|2 = Hazardous Materials Inventory|3 = Emergency Response and Training Plans|4 = Underground Storage Tanks|5 = Onsite Hazardous Waste Treatment Notification|6 = Recyclable Materials Report|7 = Remote Waste Consoidations Annual Notification|8 = Hazardous Waste Tank Closure Certification|9 = Aboveground Petroleum Storage Tanks|10 = California Accidental Release Program","CodesCriteria":"1 = Facility Information 2 = Hazardous Materials Inventory 3 = Emergency Response and Training Plans 4 = Underground Storage Tanks 5 = Onsite Hazardous Waste Treatment Notification 6 = Recyclable Materials Report 7 = Remote Waste Consoidations Annual Notification 8 = Hazardous Waste Tank Closure Certification 9 = Aboveground Petroleum Storage Tanks 10 = California Accidental Release Program ","Description":"A code identifying a Submittal Element type. This is an attribute on the SubmittalElement XML element used in the Submittal Action Update Notification XML Schema. It is also used as an element to indicate if a document has been provided in some other submittal element.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Submittal Element Code","ID":11927,"Identifier":"20.0071","Length":null,"RegistryFieldNumber":20.0071,"Section":"FacilitySubmittalActionNotification","Type":"Numeric","XMLTag":"code (Attribute)"},{"CodeArray":"1 = Locally-Discovered Facility|2 = Substantial Operational Change at Facility|3 = Facility Subdivided|4 = Local Regulator Need","CodesCriteria":"1 = Locally-Discovered Facility 2 = Substantial Operational Change at Facility 3 = Facility Subdivided 4 = Local Regulator Need ","Description":"Regulators use this field to justify a new CERS ID request for a \"new\" CERS facility. Cal/EPA encourages regulators to not create new CERS IDs for existing facilities unless onsite operations are fundamentally different than the previous owner/operator, or there is a need to subdivide an existing facility.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"NewIDJustification","ID":11899,"Identifier":"20.0018","Length":null,"RegistryFieldNumber":20.0018,"Section":"FacilitySubmittal","Type":"Numeric","XMLTag":"NewIDJustification"},{"CodeArray":"1 = Not Applicable|2 = Applicable|3 = Always Applicable","CodesCriteria":"1 = Not Applicable 2 = Applicable 3 = Always Applicable ","Description":"Indicates if a facility has or is required to complete a submittal element. By default, all submittal elements (except Facility Information) are set to \"Not Applicable.\" The first time a reporter indicates an element is relevant on the Business Activities form (or when CERS receive the first EDT transaction for that facility/element), a submittal element for that facility is set to \"Applicable.\" Regulators or reporters can opt to set a submittal element to \"Not Applicable,\" to signify the facility no longer needs to report on an element they may have previously reported on, and regulators can set this status to \"Always Applicable\" to force a reporter to complete a submittal element (via the CERS UI).  ","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Submittal Element Reporting Requirement","ID":12723,"Identifier":"20.0088","Length":null,"RegistryFieldNumber":20.0088,"Section":"FacilitySubmittal","Type":"Numeric","XMLTag":"ReportingRequirement"},{"CodeArray":"1 = Yes|2 = No|0 = Unknown","CodesCriteria":"1 = Yes 2 = No 0 = Unknown ","Description":"Indicates if the current Inventory in question has been changed in some way from the last inventory submitted by the business. The field will be shown in regulator submittal review screens to help them quickly see if a submittal is different from the previous one. Should be set to Yes (1) if a business starts a new inventory, or a business adds/edits/deletes any record(s) in an inventory based upon the previous inventory. Implementers can assume a value of Yes when when a business uploads an entire inventory. If a local reporting portal does not implement this kind of tracking it is submittal user interface, the value must be set to Unknown (0).","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"ChangedFromLastSubmittal","ID":12758,"Identifier":"20.0105","Length":1,"RegistryFieldNumber":20.0105,"Section":"FacilitySubmittal","Type":"Numeric","XMLTag":"ChangedFromLastSubmittal"},{"CodeArray":"Advisory = Advisory Guidance|Warning = Warning Guidance (Important)|Required = Required Guidance (error condition)","CodesCriteria":"Advisory = Advisory Guidance Warning = Warning Guidance (Important) Required = Required Guidance (error condition) ","Description":"Indicates the level of the guidance message. Advisory Required Warning","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Level","ID":11947,"Identifier":"20.0079","Length":10,"RegistryFieldNumber":20.0079,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"Level"},{"CodeArray":"BA = Business Activities|BOOI = Business Owner/Operator Identification|HMI = Hazardous Material Inventory|FSPM = Facility Site Plan Map|SM = Storage Map|ERCP = Emergency Response/Contingency Plan|ETP = Employee Training Plan|OHWTF = Onsite Hazardous Waste Treatment Notification: Facility|OHWTU = Onsite Hazardous Waste Treatment Notification: Unit|TPUPBR = Tiered Permitting Unit: Permit By Rule (PBR)|TPUCA = Tiered Permitting Unit: Conditionally Authorized (CA)|TPUCESW = Tiered Permitting Unit: Conditionally Exempt - Specified Wastestreams (CESW)|TPUCESQT = Tiered Permitting Unit: Conditionally Exempt - Small Quantity Treatment (CESQT)|TPCEL = Tiered Permitting Unit: Conditionally Exempt - Limited (CEL)|HWCFA = Certification of Financial Assurance|RMA = Recyclable Materials Activities (Page 1)|RMM = Recyclable Materials: Material (Page 2)|RWCSAN = Remote Waste Consolidation Site Annual Notification|HWTPPM = Onsite Hazardous Waste Treatment Plot Plan/Map|TPUPEH = Tiered Permitting Unit: Prior Enforcement History|OHWTWECC = Onsite Hazardous Waste Treatment: Written Estimate of Closure Costs|HWFACM = Financial Assurance Closure Mechanism|TPUTCC = Tiered Permitting Unit: Tank and Container Certification|TPUNLAA = Tiered Permitting Unit: Notification of Local Agency or Agencies|TPUNPO = Tiered Permitting Unit: Notification of Property Owner|RMDKM = Recyclable Materials: Documentation of Known Market|HWTCC = Hazardous Waste Tank Closure Certificate|FILRD = Facility Information Locally-Required Document|USTOPF = UST Operating Permit Application: Facility Information|USTOPT = UST Operating Permit Application: Tank Information|USTCIM = UST Certification of Installation/Modification|USTMP = UST Monitoring Plan|USTMSP = UST Monitoring Site Plan|USTCFR = UST Certification of Financial Responsibility|USTRP = UST Response Plan|USTOOWA = UST Owner and UST Operator: Written agreement|USTLCFO = UST Letter from the Chief Financial Officer|USTOSDOC = Owner Statement of Designated UST Operator Compliance|APSADOC = AST/APSA Document|HWTCC = Hazardous Waste Tank Closure Certification|FILF = Facility Information Local Fields|HMILRD = Hazardous Material Inventory Locally-Required Document|ERTPLRD = Emergency Response and Training Plans Locally-Required Document|USTLRD = UST Locally-Required Document|OHWTNLRD = Onsite Hazardous Waste Treatment Notification Locally-Required Document|RMRLRD = Recyclable Materials Report Locally-Required Document|RWCANLRD = Remote Waste Colidation Annual Notification Locally-Required Document|HWTCCLRD = Hazardous Waste Tank Closure Certification Locally-Required Document|APSTLRD = Aboveground Petrolium Storage Tanks Locally-Required Document|CALARPLRD = California Accidental Release Program Locally-Required Document","CodesCriteria":"BA = Business Activities BOOI = Business Owner/Operator Identification HMI = Hazardous Material Inventory FSPM = Facility Site Plan Map SM = Storage Map ERCP = Emergency Response/Contingency Plan ETP = Employee Training Plan OHWTF = Onsite Hazardous Waste Treatment Notification: Facility OHWTU = Onsite Hazardous Waste Treatment Notification: Unit TPUPBR = Tiered Permitting Unit: Permit By Rule (PBR) TPUCA = Tiered Permitting Unit: Conditionally Authorized (CA) TPUCESW = Tiered Permitting Unit: Conditionally Exempt - Specified Wastestreams (CESW) TPUCESQT = Tiered Permitting Unit: Conditionally Exempt - Small Quantity Treatment (CESQT) TPCEL = Tiered Permitting Unit: Conditionally Exempt - Limited (CEL) HWCFA = Certification of Financial Assurance RMA = Recyclable Materials Activities (Page 1) RMM = Recyclable Materials: Material (Page 2) RWCSAN = Remote Waste Consolidation Site Annual Notification HWTPPM = Onsite Hazardous Waste Treatment Plot Plan/Map TPUPEH = Tiered Permitting Unit: Prior Enforcement History OHWTWECC = Onsite Hazardous Waste Treatment: Written Estimate of Closure Costs HWFACM = Financial Assurance Closure Mechanism TPUTCC = Tiered Permitting Unit: Tank and Container Certification TPUNLAA = Tiered Permitting Unit: Notification of Local Agency or Agencies TPUNPO = Tiered Permitting Unit: Notification of Property Owner RMDKM = Recyclable Materials: Documentation of Known Market HWTCC = Hazardous Waste Tank Closure Certificate FILRD = Facility Information Locally-Required Document USTOPF = UST Operating Permit Application: Facility Information USTOPT = UST Operating Permit Application: Tank Information USTCIM = UST Certification of Installation/Modification USTMP = UST Monitoring Plan USTMSP = UST Monitoring Site Plan USTCFR = UST Certification of Financial Responsibility USTRP = UST Response Plan USTOOWA = UST Owner and UST Operator: Written agreement USTLCFO = UST Letter from the Chief Financial Officer USTOSDOC = Owner Statement of Designated UST Operator Compliance APSADOC = AST/APSA Document HWTCC = Hazardous Waste Tank Closure Certification FILF = Facility Information Local Fields HMILRD = Hazardous Material Inventory Locally-Required Document ERTPLRD = Emergency Response and Training Plans Locally-Required Document USTLRD = UST Locally-Required Document OHWTNLRD = Onsite Hazardous Waste Treatment Notification Locally-Required Document RMRLRD = Recyclable Materials Report Locally-Required Document RWCANLRD = Remote Waste Colidation Annual Notification Locally-Required Document HWTCCLRD = Hazardous Waste Tank Closure Certification Locally-Required Document APSTLRD = Aboveground Petrolium Storage Tanks Locally-Required Document CALARPLRD = California Accidental Release Program Locally-Required Document ","Description":"Identifies the particular resource that a Guidance Message and/or EntityKey is about.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Entity Resource","ID":11929,"Identifier":"20.0070","Length":10,"RegistryFieldNumber":20.0070,"Section":"CMESubmittalResponse","Type":"Alphanumeric","XMLTag":"Entity Resource"},{"CodeArray":"BA = Business Activities|BOOI = Business Owner/Operator Identification|HMI = Hazardous Material Inventory|FSPM = Facility Site Plan Map|SM = Storage Map|ERCP = Emergency Response/Contingency Plan|ETP = Employee Training Plan|OHWTF = Onsite Hazardous Waste Treatment Notification: Facility|OHWTU = Onsite Hazardous Waste Treatment Notification: Unit|TPUPBR = Tiered Permitting Unit: Permit By Rule (PBR)|TPUCA = Tiered Permitting Unit: Conditionally Authorized (CA)|TPUCESW = Tiered Permitting Unit: Conditionally Exempt - Specified Wastestreams (CESW)|TPUCESQT = Tiered Permitting Unit: Conditionally Exempt - Small Quantity Treatment (CESQT)|TPCEL = Tiered Permitting Unit: Conditionally Exempt - Limited (CEL)|HWCFA = Certification of Financial Assurance|RMA = Recyclable Materials Activities (Page 1)|RMM = Recyclable Materials: Material (Page 2)|RWCSAN = Remote Waste Consolidation Site Annual Notification|HWTPPM = Onsite Hazardous Waste Treatment Plot Plan/Map|TPUPEH = Tiered Permitting Unit: Prior Enforcement History|OHWTWECC = Onsite Hazardous Waste Treatment: Written Estimate of Closure Costs|HWFACM = Financial Assurance Closure Mechanism|TPUTCC = Tiered Permitting Unit: Tank and Container Certification|TPUNLAA = Tiered Permitting Unit: Notification of Local Agency or Agencies|TPUNPO = Tiered Permitting Unit: Notification of Property Owner|RMDKM = Recyclable Materials: Documentation of Known Market|HWTCC = Hazardous Waste Tank Closure Certificate|FILRD = Facility Information Locally-Required Document|USTOPF = UST Operating Permit Application: Facility Information|USTOPT = UST Operating Permit Application: Tank Information|USTCIM = UST Certification of Installation/Modification|USTMP = UST Monitoring Plan|USTMSP = UST Monitoring Site Plan|USTCFR = UST Certification of Financial Responsibility|USTRP = UST Response Plan|USTOOWA = UST Owner and UST Operator: Written agreement|USTLCFO = UST Letter from the Chief Financial Officer|USTOSDOC = Owner Statement of Designated UST Operator Compliance|APSADOC = AST/APSA Document|HWTCC = Hazardous Waste Tank Closure Certification|FILF = Facility Information Local Fields|HMILRD = Hazardous Material Inventory Locally-Required Document|ERTPLRD = Emergency Response and Training Plans Locally-Required Document|USTLRD = UST Locally-Required Document|OHWTNLRD = Onsite Hazardous Waste Treatment Notification Locally-Required Document|RMRLRD = Recyclable Materials Report Locally-Required Document|RWCANLRD = Remote Waste Colidation Annual Notification Locally-Required Document|HWTCCLRD = Hazardous Waste Tank Closure Certification Locally-Required Document|APSTLRD = Aboveground Petrolium Storage Tanks Locally-Required Document|CALARPLRD = California Accidental Release Program Locally-Required Document","CodesCriteria":"BA = Business Activities BOOI = Business Owner/Operator Identification HMI = Hazardous Material Inventory FSPM = Facility Site Plan Map SM = Storage Map ERCP = Emergency Response/Contingency Plan ETP = Employee Training Plan OHWTF = Onsite Hazardous Waste Treatment Notification: Facility OHWTU = Onsite Hazardous Waste Treatment Notification: Unit TPUPBR = Tiered Permitting Unit: Permit By Rule (PBR) TPUCA = Tiered Permitting Unit: Conditionally Authorized (CA) TPUCESW = Tiered Permitting Unit: Conditionally Exempt - Specified Wastestreams (CESW) TPUCESQT = Tiered Permitting Unit: Conditionally Exempt - Small Quantity Treatment (CESQT) TPCEL = Tiered Permitting Unit: Conditionally Exempt - Limited (CEL) HWCFA = Certification of Financial Assurance RMA = Recyclable Materials Activities (Page 1) RMM = Recyclable Materials: Material (Page 2) RWCSAN = Remote Waste Consolidation Site Annual Notification HWTPPM = Onsite Hazardous Waste Treatment Plot Plan/Map TPUPEH = Tiered Permitting Unit: Prior Enforcement History OHWTWECC = Onsite Hazardous Waste Treatment: Written Estimate of Closure Costs HWFACM = Financial Assurance Closure Mechanism TPUTCC = Tiered Permitting Unit: Tank and Container Certification TPUNLAA = Tiered Permitting Unit: Notification of Local Agency or Agencies TPUNPO = Tiered Permitting Unit: Notification of Property Owner RMDKM = Recyclable Materials: Documentation of Known Market HWTCC = Hazardous Waste Tank Closure Certificate FILRD = Facility Information Locally-Required Document USTOPF = UST Operating Permit Application: Facility Information USTOPT = UST Operating Permit Application: Tank Information USTCIM = UST Certification of Installation/Modification USTMP = UST Monitoring Plan USTMSP = UST Monitoring Site Plan USTCFR = UST Certification of Financial Responsibility USTRP = UST Response Plan USTOOWA = UST Owner and UST Operator: Written agreement USTLCFO = UST Letter from the Chief Financial Officer USTOSDOC = Owner Statement of Designated UST Operator Compliance APSADOC = AST/APSA Document HWTCC = Hazardous Waste Tank Closure Certification FILF = Facility Information Local Fields HMILRD = Hazardous Material Inventory Locally-Required Document ERTPLRD = Emergency Response and Training Plans Locally-Required Document USTLRD = UST Locally-Required Document OHWTNLRD = Onsite Hazardous Waste Treatment Notification Locally-Required Document RMRLRD = Recyclable Materials Report Locally-Required Document RWCANLRD = Remote Waste Colidation Annual Notification Locally-Required Document HWTCCLRD = Hazardous Waste Tank Closure Certification Locally-Required Document APSTLRD = Aboveground Petrolium Storage Tanks Locally-Required Document CALARPLRD = California Accidental Release Program Locally-Required Document ","Description":"Identifies the particular resource that a Guidance Message and/or EntityKey is about.","FieldFormat":null,"Obsolete":false,"MinRequired":false,"FieldName":"Entity Resource","ID":11926,"Identifier":"20.0070","Length":10,"RegistryFieldNumber":20.0070,"Section":"FacilitySubmittalResponse","Type":"Alphanumeric","XMLTag":"entityResource (Attribute)"}],"Total":109,"AggregateResults":null,"Errors":null}