users' meeting san francisco, ca april 18 th, 2006 rcrainfo network exchange
TRANSCRIPT
Users' Meeting San Francisco, CA
April 18th, 2006
RCRAInfo Network Exchange
Discussion Topics
RCRAInfo 101 Exchange Overview Getting Ready to Flow Path Forward Open Session
– Input into Outbound Services – Questions
RCRAInfo 101: Scope of System And Flow Status
HandlerAddressContacts
Regulated Activities
PermittingPermitting Events
Waste Treatment UnitsUnit Operating Status
Corrective ActionLocation Addressed (area)
Corrective Activities (events)
Legal Authority for Actions
Compliance (CME)Inspections (evaluations)
Violations
Enforcement Actions
Waste ActivityWaste Treated
Waste Shipped
RCRAInfo 101: Historic Approaches to Interfacing with RCRAInfo
State
Internet
RCRAInfo
Direct Data Entry
State
Internet
RCRAInfo
State System
Dual Data Entry
State
Internet
RCRAInfo State System
Permitting
CME
Handler
Flat Files
Flat File Translation
Exchange Overview: Submission Processing
State SystemXML
Submission
InternetState Node
CDX Node
XML to Text Converter
Permitting
CME
Handler
Validate AgainstSchema
Validate RCRAInfoRules
Load Into RCRAInfo
Return Validation Errors`
Submit or Solicit
Exchange Overview: Document Structure
Document Header
Exchange Network Document
Payload (1)Operation:FullReplace| HD
Payload (2)Operation:Transactional| PM
Payload (3)Operation:Transactional| CA
Exchange Overview: Payload Operations
Transactional Pros:
– Provides precise control for manipulating data at the record level.
– Can be more efficient in processing. Cons:
– Requires a thorough understanding of State’s data relative to RCRAInfo processing.
– Requires that the State system have the ability to recognize and track record deletions to ensure accurate data synchronization.
Currently Supported
Exchange Overview: Payload Operations
Full Replace Pros:
– Significantly less complicated approach when compared to transactional processing.
Cons:– Has negative impacts on exchange efficiency due to file
size and processing demands.– Requires that ALL of a handler’s data for a module be
sent to RCRAInfo. This will result in newer data validation rules being applied to older data.
Currently Supported (Put in place this last year)
Exchange Overview: Payload Operations
Full Replace by Handler Pros:
– More efficient than Full Replace operation; as only specified handler’s data within a module is being replaced.
– Offers more control to implementers, as they can send data only for those handlers who have had a change in data within a module.
Exchange Overview: Payload Operations
Cons:– Requires more system sophistication to determine which
handlers have had modifications to their data. – Requires that ALL of a handler’s data for a module be
sent to EPA. This will result in newer data validation rules being applied to older data.
Anticipated for RCRAInfo V3
RCRA Network Exchange: Getting Ready to Flow
Evaluate readiness and compatibility.– Mapping of look-up values from State to RCRAInfo.– Use of RCRAInfo compatible system keys.– Ability to meet RCRAInfo data validation checks.– Impacts of Data Ownership/Co-Implementation issues.
Evaluate and select submission processing mode. Obtain user ID and authorization to RCRAInfo Pre-
Production and Production databases .– Need to obtain rights to the specific modules you will be
submitting.
RCRA Network Exchange: Getting Ready to Flow
Enter into agreement with EPA / Region on approach to testing, submission and data. stewardship (Trading Partner Agreement).
Notify EPA RCRAInfo system support of intention to submit data for testing.
Perform testing of selected processing method and XML document creation.
Resolve data issues. Notify EPA RCRAInfo system support of intention
to submit data to production system.
RCRA Network Exchange: Getting Ready to Flow
Biggest hurdles to date:– Gaining system ID’s and rights.– Relationship with Regions.– Underestimating effort necessary to successfully load
data. The larger difference between the source system and RCRAInfo the greater the effort required to successfully submit data.
RCRA Network Exchange: Path Forward
Data Synchronization Services– Get (Handler/Permitting/Corrective Action/CME)
Data – Used to synchronize States system with Federal system.
E.g. Retrieving all EPA Inspection and Enforcement Data for a State.
RCRA Network Exchange: Path Forward
Data Sharing Services – Get Handler ID
Used to create a new Handler and associated Handler ID in RCRAInfo.
Envisioned as a real-time service; used during Handler data entry in State system.
– Get Handler Basic Retrieves all basic handler data for a State or entire
nation. Envisioned to address data validation issues e.g.
Validating out of state handlers listed on Hazardous Waste Manifest / Biennial Report.
RCRA Network Exchange: Path Forward
Update FCD. Develop and test CME Conversion Style Sheets.
(pending RCRAInfo V3 production release). Finalize CME schema and re-release FCD. Develop outbound services.
RCRA Network Exchange: Available Resources
Exchange Network Site – http://www.exchangenetwork.net/– Schema– Data Exchange Template– Flow Configuration Document
RCRAInfo Data Submission Overview and Challenges RCRA XML Schema Users Guide Flow Implementation and Testing Checklists
RCRA Network Exchange: Available Resources
RCRAInfo Site – http://www.epa.gov/cdx/rcraft
– RCRAInfo Data Validation Checks Contacts
– RCRAInfo: Eric Schwartz [email protected]
– RCRA Network Exchange Support [email protected]
RCRA Network Exchange: Open Session
Input into Outbound Services – Get (Handler/Permitting/Corrective Action/CME)
Data. – Get Handler ID– Get Handler Basic
Questions?