Joe Carioti email me

Carolyn Cunningham (C.C.) email me

Q. What are the differences between the various releases of RCRAInfo?

A. RCRAInfo is a regulatory system that changes when new rules and statutes are introduced to the RCRA Program. Each subsequent version of RCRAInfo implements recommendations that were formulated by an EPA/State partnership. RCRAInfo was implemented in 2000 replacing the legacy systems RCRIS and BRS. Version 2 was released in 2002, and addressed updates to the Site ID form in the Handler module, implemented the Waste Activity Reporting module, and began efforts on integrating with the Central Data Exchange. Version 3 was released in 2006 and implemented improvements to the Handler and CME modules as well as introduced a new feature called USITS (User Support Issue Tracking System) to track bugs and user questions. Version 4 was released in 2008 and implemented improvements to the Permitting and Corrective Action modules, and introduced the Financial Assurance and GIS modules. Version 5 was implemented in 2010 and modified the Handler and Biennial Reporting modules due to the new definition of solid waste and the new Subpart K rule.

Q. What is IOR?

A. IOR is defined as ‘Implementer of Record’. It is the term used to describe the agency (EPA or State) responsible for the data entry and management of the RCRA data housed in RCRAInfo. You must have IOR for the module that you are planning to translate. For example, if EPA Region is IOR for the handler module than the State cannot translate Handler data into RCRAInfo. For more information, contact the State System Administrator for your State.

Q. What are the benefits of using XML?

A. NEED TO PROVIDE

Q. What are the types of Translation methods and what are the differences between them?

A. There are currently 3 Translation Methods. They are described below.

• Full Replacement: The full replacement method deletes all data (including child records in RCRAInfo) for the specified module for that state and replaces it with the data in the current submission. (This method is being phased out.)
• Partial Replacement: The partial replacement method is similar to the full replacement method in that data is deleted from both parent and child tables, however, with the partial replacement method only the data associated with that Handler Id is deleted.
• Transactional Method: Unlike the partial and full replace methods, the transactional replace method enables the user to change (Add or Delete) data in a transactional manner one record at a time.

Q. How do I specify whether my xml submission is a Full, Partial, or Transactional translation?

A. Within the submittal file, there is an ‘Operation’ attribute that is part of the ‘Payload’ element. Depending on which type of translation you’re doing, provide the following:

For Full Replace: <hdr:Payload Operation="RCRA-FullReplace|XX">

For Partial Replace: <hdr:Payload Operation="RCRA-FullReplaceByHandler|XX">

For Transactional: <hdr:Payload Operation="RCRA-Transactional|XX">

Note: The ‘XX’ would be replaced with one of the Module parameters as indicated in the chart above (e.g. if you are submitting handler data, XX would be replaced with HD).

Q. Does my data have to be 100% correct before the submittal will be successful?

A. Yes. RCRAInfo functions as an All or None data flow. Any errors in the submittal will result in the entire submittal to fail and none of the data will be loaded.

Q. How do I receive notification that my submission is complete?

A. RCRAInfo allows a user to specify who will receive notifications upon completion of the data loading process. There are two methods you can use for this, and which one you use depends on whether you are a Node 1.1 State or a Node 2.0 State. For Node 1.1 users, add the following property to your Header:

<hdr:Property>
<hdr:name>notificationURI</hdr:name>
<hdr:value>MyEmail@epa.gov</hdr:value>
</hdr:Property>

Note: Change the MyEmail@epa.gov to be the address that you want to have the notification sent to.

For Node 2.0 users, the Header is not used for Notification, rather you use the notificationURI parameter from the Node 2.0 specification. The notification type is intended to only send notifications for specific types of events such as errors or warnings. Please note that CDX will ignore any value specified in this attribute. Notifications will be sent to the email address specified, regardless of success or failure.

Q. How Do I Get Error Reports for RCRAInfo Data Submissions?

A. There are three methods to retrieve error reports:

• Provide an email address in the notificationURI in the actual submission
• Download from the EN using the transaction ID
• Logging into RCRAInfo and clicking on the status report link under Utilities.

Q. Why don’t I see my data after what I believe is a successful submittal?

A. You must wait for the universe calculators to run before the data is updated. These universe calculators run every one and a half hours.

Q. How does RCRAInfo handle communication and outreach so I can get more involved?

A. The RCRAInfo Team has set up some of the following communication channels to enable it’s stakeholders to get involved with the activities supported by RCRAInfo:

• Change Management: Responsible for addressing changes to the RCRAInfo system. The point of contact is Debbie Goodwin, please email her with questions or comments.
• RCRAInfo Conference: RCRAInfo conferences are usually held every two to three years. This is a great opportunity to have face-to-face communication with the entire user community.
• List Serve: Primary means of email communication for the RCRAInfo community to participate in RCRAInfo discussions. To register for the List Serve send a blank message to RCRAInfoList-subscribe@lists.epa.gov.
• National Monthly Data Calls: Available to all stakeholders every third Thursday of the month. The point of contact for the data calls is Debbie Goodwin.

Q. As a State who will be translating data, how can I prepare myself for translation when a new version is released?

A. Translators should familiarize themselves with the latest document provided entitled, Schema Changes. This document will show where all of the new schema changes are identified and will be found on the link http://exchangenetwork.net/exchanges/waste/rcra.htm. This document will provide, in detail, the comparison of what data elements will be changed from version to version. In addition, Translators should begin mapping to the new Schemas by referencing the Schemas for each of the modules found on the exchangenetwork.net Website; and during the test period, begin testing their submittals and understanding the error reports they receive.

Q. What standard is RCRAInfo using for the GIS module?

A. RCRAInfo uses the GeoRSS GML (Geographic Markup Language) which is embedded in the XML schema for the use of exchanging geographic information.

GeoRSS has emerged as a defacto standard to provide a basic approach for encoding basic geographic information in RSS (feeds, blogs, etc.) and other web applications. EPA selected GeoRSS because it provides a balance of simplicity and features that match typical Exchange Network schema content and also supports the current RCRAInfo Data structure. The RCRAInfo GIS schema will support basic geometries such as handlers with points, lines and polygons.

One of the main advantages of using GeoRSS is that in our future implementation of Web Services, users will be able to leverage standard mapping technologies to display their Handler on a map.