With the release of the Node Specification v2.0, Exchange Network partners are beginning to implement upgraded node software. While new data exchanges will be written to take advantage of the new features in Node v2.0, there are many existing flows that need to continue to operate into the future. Until all of the existing exchanges are rewritten to target the Node 2.0 platform, Network partners will need to adapt each exchange to operate in a Node v2.0 environment. The Exchange Network governance has documented the necessary changes to many national regulatory data flows in a series of addenda to the Flow Configuration Documents (FCDs). These changes are relatively minor and do not require any changes to the XML schema or to your data mapping. U.S. EPA's Central Data Exchange (CDX) is now ready to accept test submissions to its Node 2.0 endpoint for the flows listed below.
Note that no new functionality has been introduced to any exchange; the goal of the addenda is to provide a set of rules for implementing each exchange to a Specification v2.0-compliant node without changes to functionality. It is expected that future versions of each exchange will take advantage of the capabilities offered by the v2.0 Specification. You can find more background information on the approach taken in developing the FCD addenda in this document on Node 2.0 FCD Compatibility Guideline Development [PDF].
flow configuration document addenda
The Exchange Network governance is producing addenda to Flow Configuration Documents (FCDs) for each of the national regulatory flows. U.S. EPA's Central Data Exchange (CDX) is now ready to accept test submissions to its Node 2.0 endpoint for the flows listed below. Please note that CDX will continue to support Node 1.1 data flows for the foreseeable future to allow adequate time for all partners to make the transition for all flows.
At this time, the other national flows listed below are only available for use with Node 1.1 endpoints at CDX. See below for more information about the timing for the transition to Node 2.0 for each of these flows.
- ICIS-NPDES (eDMR) - More information coming soon.
- National Emissions Inventory (NEI) - No addendum will be produced for the NEI data flow because 2009 is the last reporting year in which this flow will be available. NEI is transitioning to a new data system called the Emissions Inventory System (EIS) starting in 2010. Information on implementing the EIS flow on a 2.0 Node will be incorporated into the new FCD which is still in production. For more information on timing, please see the EIS web page.
- RCRAInfo - The RCRAInfo data flow is currently undergoing an upgrade for use with version 4.0 of the RCRAInfo database. Information on implementing the RCRAInfo flow on a 2.0 Node will be included in the forthcoming FCD which will be available in Spring 2009. See the RCRAInfo web page for more details on timing.
- Safe Drinking Water Information System (SDWIS) - An FCD does not exist for the current version of the SDWIS data flow. As such, the Exchange Network governance is currently working with EPA's Office of Water to identify a mechanism and timeline for documenting the necessary steps to migrate the SDWIS data flow to a 2.0 Node.
- Substance Registry System (SRS) - More information coming soon.
- Toxic Release Inventory (TRI) - More information coming soon.
considerations when implementing node 2.0
Keep in mind that version 1.1 Nodes cannot communicate with version 2.0 Nodes. When you upgrade to a 2.0 Node, you will need to consider how that change will affect all of the different partners with whom you share information. Until all of your partners have fully made the transition to Node 2.0 for all data flows, you will need to maintain two endpoints (one for Node 1.1 and one for Node 2.0). Consider the following scenarios when planning to implement a Node and migrate your existing data flows:
- Your Node currently only shares information with U.S. EPA's CDX Node
The vast majority of states, tribes, and other Network partners exchange information with U.S. EPA's Central Data Exchange Node. You may begin testing exchanges with EPA's CDX using a 2.0 Node as indicated above in the section on FCD addenda. CDX will continue to support Node 1.1 data flows for the foreseeable future to allow adequate time for all partners to make the transition for all flows.
- Your Node shares information with CDX and at least one other partner Node
If you use your Node to share information with partners other than CDX, you will need to consider their readiness to accept Node 2.0 flows when deciding to migrate your own flows to Node 2.0. Communicate with your other exchange partners so you are aware of their plans regarding Node 2.0. If you opt to implement Node 2.0 before your other partners, you may maintain two endpoints for your exchanges--one for flows with 1.1 Nodes and one for flows with 2.0 Nodes. Several of the Node products that are being developed will support endpoints for either version of the Node.
|
