Network and Node 101
Exchange Network Conference
San Francisco, CA
April 18, 2006
101 Topics
•
•
•
•
•
•
•
•
Introduction
The Mechanism: Nodes
The Medium: XML
The Mimic: Node Clients
The Menu: Exchanges
The Main Act: A LIVE demonstration
The Mob: Governance
The End: Getting Started
What
is
the
Exchange
Network?
State
x
y
z
x
y
z
Business
x
y
x
y
Internet
x
Internal System
x
y
z
x
y
z
EPA
XML Schema
x
Tribe
Network Node
Node Client
An Internet and standards-based method for
exchanging environmental information between partners.
Purpose of Network
•
•
•
•
Support automated exchange of data
Enable timely and accurate exchange
Reduce reporting burden
Improve data quality
What is a Network Node ?
“A simple environmental
information Web service that
initiates requests for information,
processes authorized queries, and
sends/receives the requested
information in a standard format.”
Underlying Technologies
Connectivity
(FTP, E-mail)
Connect
the Web
Presentation
(Web Pages)
Browse
the Web
Connecting
Applications
(Web Services)
Program
the Web
Nodes (Web Service)
• A Node:
State
x
y
z
x
y
z
Business
x
y
x
y
www
x
x
Tribe
x
y
z
x
y
z
EPA
– Is a Server accessible by
the www
– Complies with the protocols
to ensure secure exchange
– Returns requested
information as XML
– Each partner has only one
Node
The old medium for
exchange: flat files
• A simple way to share data
• Cannot be validated without custom
software
• Very hard to read
• Cannot accommodate complex data in
one file
• Simple but messy
XML
• XML Schema
State
x
y
z
x
y
z
Business
x
y
x
y
www
x
x
Tribe
x
y
z
x
y
z
EPA
– Describe format of data
being exchanged
– Draw upon data
standards
– Potential to reuse XML
schema modules
XML in a nutshell
• XML: eXtensible Markup Language
• XML Schema: defines the Structure
and the Rules of data to be shared
• XML Document: a file that contains the
data (and references the Schema)
Create an XML document, open it with
Internet Explorer and it validates itself
against the schema
XML is not a silver bullet
• Agreement on the definition of data is
still the same old challenge
• XML is a new skill
• XML is verbose
Node Client
Node
Client
Internet
NODE
Network Exchange
‘Exchange’: the sharing of a specific type
of data between two or more Partners;
for example, sharing of water quality
data. This is often also referred to as a
‘flow’.
The Main Act
Cradle to Grave Shipments
of Hazardous Waste
NODE
A
HazWaste
Internet
NODE
B
HazWaste
Data Request
Node A: “Hey, what Treatment
Facilities can receive waste
over there?”
Data Service:
GetLegalTreatmentFacilities
DATA STORE: TSDF
Data:
Just the facts
NODE
B
HazWaste
ACME CORP
3121, RUMINGTON AVE, DUKE,DE
DEW123412312
F001 D002 P032
4343, DEXTER AVE, DUKE, DE
BOCACIOUS ENTERPRISES
DEW234317657
F001 D002 P032
1222, BRUSER AVE, DUKE, DE
CORNY CANDY
DEW145323423
F001 D002 P032
9898, LEXOR AVE, DUKE, DE
FRACTIOUS CORP
DEW123324234
F001 D002 P032
2222, TENBY AVE, DUKE, DE
FRIVIOUS INC
DEW234234234
F001 D002 P032
LEGAL TREATMENT FACILITIES FORM
XML
Schema:
A data entry
form and
instructions
RCRA ID:
FACILITY NAME:
FACILITY ADDRESS:
PERMITTED WASTE CODES:
CANNOT EXCEED 12
CHARACTERS
RCRA ID:
FACILITY NAME:
FACILITY ADDRESS:
PERMITTED WASTE CODES:
RCRA ID:
FACILITY NAME:
CODES MUST START
WITH D, F, P, K OR X
FACILITY ADDRESS:
PERMITTED WASTE CODES:
RCRA ID:
FACILITY NAME:
FACILITY ADDRESS:
PERMITTED WASTE CODES:
RCRA ID:
FACILITY NAME:
FACILITY ADDRESS:
PERMITTED WASTE CODES:
AT LEAST ONE CODE
REQUIRED, NO LIMIT
OF HOW MANY
LEGAL TREATMENT FACILITIES
XML
Document:
A filled out
form
RCRA ID:
DEW123412312
FACILITY NAME:
ACME CORP
FACILITY ADDRESS:
3121, RUMINGTON AVE, DUKE,DE
PERMITTED WASTE CODES:
F001 D002 P032
RCRA ID:
DEW1234317657
FACILITY NAME:
BOCACIOUS ENTERPRISES
FACILITY ADDRESS:
4343, DEXTER AVE, DUKE, DE
PERMITTED WASTE CODES:
F001 D002 P032
RCRA ID:
DEW145323423
FACILITY NAME:
CORNY CANDY
FACILITY ADDRESS:
1222, BRUSER AVE, DUKE, DE
PERMITTED WASTE CODES:
F001 D002 P032
RCRA ID:
DEW123324234
FACILITY NAME:
FRACTIOUS CORP
FACILITY ADDRESS:
9898, LEXOR AVE, DUKE, DE
PERMITTED WASTE CODES:
F001 D002 P032
RCRA ID:
DEW234234234
FACILITY NAME:
FRIVIOUS INC
FACILITY ADDRESS:
2222, TENBY AVE, DUKE, DE
PERMITTED WASTE CODES:
F001 D002 P032
SSL
Certificate
Yes Soliciting
Question: “Hey, what Generators can send waste my way?”
Answer: “42…No, hang on, let me think on it a while…”
•
•
•
•
If requesting a large set of data
Immediate response may not be practical
Query is immediate, Solicit is delayed
Take a ticket (AKA transaction id)
Network Exchanges
3 Types:
1. Data Reporting
2. Data Synchronization
3. Data Publishing
Data Reporting
Hazardous
Waste
Reporter
Internet
NODE
HazWaste
DB
Data Synchronization
Hazardous
Waste
Reporter
Internet
NODE
NODE
Internet
HazWaste
DB
CDX
EPA’s
RCRAInfo
Data Publishing
Oregon DEQ
Inter-state
waste
shipments
Hazardous
Waste
Reporter
Internet
NODE
Internet
NODE
NODE
Internet
HazWaste
DB
CDX
EPA’s
RCRAInfo
The Exchanges on Today’s
Menu are:
Exchanges in Production
Today’s Specials
cross-program
• Facility Identification
(FRS)
• Substance Registry
System
water
• Safe Drinking Water
• Discharge Monitoring
Reports
• Pacific NW Water
Quality
• Beach Notification
• Washington Fish
Tissue Data
F/S
Identific’n
XML
Haz. Waste Gen and Mgmt
XML
Toxics Release Inventory
XML
Chemical Inventories
XML
NPDES Permitting (IDEF)
XML
Grants Administration
XML
Permitting, Compliance
XML
Haz. Waste Activities
AQ SIS
?
`
blue sky
AGBAR
C&G
XML
Payable
Agency
x
y
z
x
y
z
Business
HWTRIn
fo
EPCRA
XML
TIER II
x
y
x
y
Node
TurboWaste
Facility Identfication
XML
Air Ambient Monitoring
XML
Air Quality Permitting
WPLCS
XML
Air Emission Inventory
XML
Discharge Monitoring
EIM
XML
Water Quality
XML
Beaches Monitoring
XML
Beaches Notification
XML
Drinking Water Reporting
DOH DB
DOH DB
x
y
z
x
y
z
EPA
Exchange Network Governance
Getting Started
• Research the Network
– Exchange Network Web Site
• 30 minutes Guide to Implementing a
Node
• Consult Other Partners States
• Don’t Reinvent the Wheel
Node Capabilities +
• Administration interface.
• Separation of the Node and the
individual data exchange.
• Support of authentication and
authorization through NAAS.
• Support for both incoming and outgoing
data flows.
Factors affecting exchange
selection
• Priorities for data sharing with Partners
• Your data management authority
• The exchanges that are proven / available
• The status of agency information systems
Descargar

Network & Node 101