Michigan DMR Data Exchange With EPA or

1
Michigan DMR Data Exchange With EPAor What I
Node To Be True

• Bill Geake
• Michigan Department of
• Information Technology

2
Overview of DMR Data Flow Process
Regulated Wastewater Facilities
Michigan DEQ
US EPA
PCS
IDEF GenTran
MI Node Client
Legacy CDX
CDXNode
3
Facility-to-State DMR Data Flow
Regulated Wastewater Facilities
Michigan DEQ
DB
DEQ DMZ
DEQ Intranet
NMS DB
E-DMR DB
4
(No Transcript)
5
(No Transcript)
6
(No Transcript)
7
State-to-EPA DMR Data Flow
EPA
State of Michigan
DEQ Intranet
PCS
NMS DB
IDEF GenTran
MI Node Client
Legacy CDX
CDX Node
8
Michigan Node Client Processing
Michigan Node Client
NMS DB
9
EPA-to-State Feedback Flow
EPA
PCS
IDEF GenTran Processor
Legacy CDX
CDX Node
From State
10
EPA-to-State Feedback Flow
PCS Update Audit Report
State of Michigan
EPA
PCS Reject Resolution Utility
CDX Web Site
NMS DB
DEQ Data Coding Operator
11
The BIG Picture
80-Column text file
PCS
State NPDES Permit Database
Edit/Update Reports
12
The BIG Picture
PCS
State NPDES Permit Database
IDEF GenTran
IDEF XML
CDX Web Site
Edit/Update Reports (PDF Format)
13
The BIG Picture
PCS
State NPDES Permit Database
IDEF GenTran
CDX Web Site
Edit/Update Reports (PDF Format)
CDX Node
IDEF XML
14
FLOWS are about PROCESSING!

• Two Aspects of Data Exchange
• Format
• Data Container
• XML Schema
• Process
• Rules surrounding the flow of data
• More complex than creating a format
• Can we have XML-based processing instructions?

15
The Ideal Data Flow Scenario

• One Owner/Authority for a given dataset
• Each owner publishes to their node
• Nodes each provide a common interface for given
  data flow

16
The Ideal Data Flow Scenario

• Data Consumer should initiate Requests from the
  Data Provider
• Come and get it approach
• Only the consumer knows what it needs and when it
  needs it

Want My Data?
Data ProviderNode
Data ConsumerNode
NoNoNo
17
The Ideal Data Flow Scenario

• Data Provider should need NO knowledge of Data
  Requestors state
• Complexity of storing data consumers state on
  the provider side
• Not as scalable

Gimme the Data I Dont Have
Data ProviderNode
Data ConsumerNode
Nope. Tell me what you want!!!
18
The Synchronization Data Flow Scenario

• Push or Pull will work
• Should all happen in the background
• Only require user intervention when and exception
  occurs
• Difficult to achieve when synchronizing
  heterogeneous systems
• Crosswalking datawhat a mess!

19
Final Thoughts
20
The Ubiquitous Questions Slidewith Tacky
WordArt
Questions???