120 likes | 137 Views
Mni Sose Intertribal Water Rights Coalition, Inc. Exchange network Project. Presented by Rhonda Azure Mni Sose Treasurer. Mni Sose Intertribal Water Rights Coalition, Inc. Mni Sose (pronounced “mini so-shay”) is a consortia of delegates representing tribes in the Missouri River Basin.
E N D
Mni Sose Intertribal Water Rights Coalition, Inc. Exchange network Project Presented byRhonda AzureMni Sose Treasurer
Mni Sose Intertribal Water Rights Coalition, Inc. • Mni Sose (pronounced “mini so-shay”) is a consortia of delegates representing tribes in the Missouri River Basin. • The Basin falls within two separate U.S. EPA Regions—Region 7 and Region 8. • Region 7 has nine sovereign tribal nations, seven of which are active members of our organization. • Member tribes include: Kickapoo Tribe in KS, Omaha Tribe of NE & IA, Ponca Tribe of NE, Prairie Band of Potawatomi Nation, Sac & Fox Nation of Missouri in KS and NE, Santee Sioux Nation and the Winnebago Tribe of NE. • Mni Sose received the Exchange Network grant from the EPA to provide services to the Region 7 nations via tribal Environmental Protection offices.
Exchange Network Project Goals • Improve individual and collective information capacity of member Tribes • Establish base infrastructure (technical and management) which can be expanded to new flows, services and Tribes • Improve Tribes’ access to external information sources and services • Refine and expand the business case for Tribal use/participation in the EN
Project Components • Multi-partner node • Available to all Region 7 Tribes • Shared application and services • Identify and adapt applications that provide improved capability to member Tribes and Mni Sose • member Tribes have secured access to individual and shared space/applications. • Integrate and provide value-added access to member data • Management Support • Mni Sose Information Plan • Member Tribe training, support and tech transfer
Project Approach – Three Phases • Phase 1 – Assess and Plan • User Data, Software, Needs and Opportunities Inventory • Scan of existing applicable applications • in use by other Partners (Tribes and States) • Perform buy/build/adapt analysis • Install proof of concept Node and Client • Test conversion of historical facility and water data • Conduct test flows • Develop Proposed Architecture and Plan • Flows to be implemented • Core shared applications/services
Project Approach – Three Phases (cont’d) • Phase 2- Implementation • Shared Applications • Revised Node/Client software • Flow Implementation • Application Development and Deployment • Phase 3 –Support and Future Planning • Training • Share findings with EN community • Plan next steps
Establishing a Multi-Partner Node (AKA “Super-Node”) • Many partners want to use EN but not administer a Node • PNWWQX and STORET Tribal Warehouse in Region 8 demonstrated proof of concept of a “super node” • Provide EN client and web interface to data providers/users • Works with users who have local/mixed data stores • What Mni Sose will do: • Tribal member users maintain control of their data • Host a multi partner Node on behalf of member tribes • Do authorized transactions and publishing of Mni Sose member data • Provide value-added client and web applications to members (e.g. Analysis, Visualization and Reporting) • Mni Sose handles Allow tribal members with local data stores and easy way to publish • Will host a secured web-based application to provide both data hosting, and useful functionality for members who want it • Users will be able to add, remove and download their specific data.
Tribal Data Management Issues • Very different levels of information management capacity at member Tribes • Data format/consistency diversity • Individual Tribal Environmental Protection office data are currently in a variety of raw forms. • will be a challenge to catalog the data and format it for storage in the shared management system. • In collaboration with member tribes, we will adapt/create a standard template to be utilized among the Region 7 tribes. • Support will be needed to ensure project supports both direct individual needs of members and collective needs
Candidate Flow List • Short List: • Facility • Tribe to EPA (FRS flow) • EPA to Tribe (What facilities EPA thinks) • Water Quality • Historical data…get that entered first…then establish process • Use WQX flow • Air • Scope the AQS flow, both directions • Others being considered: • Meth Lab Location and Cleanup Status/Issues • Open Dumps • Underground Tanks
Exploring Full Range of Data Flow Options -- Then picking a few to implement
90 90 80 80 70 70 60 60 East 50 East 50 West West 40 40 North North 30 30 20 20 1st Qtr 10 10 0 0 2nd Qtr 1st Qtr 2nd Qtr 2nd Qtr 4th Qtr 4th Qtr 1st Qtr 3rd Qtr 3rd Qtr 3rd Qtr 4th Qtr Tribal Member Mni Sose Multi-User Node Tribe A State Agencies Spreadsheet Only Shared Applications and Services Tribal Web Application ________________________________________________________________________________________________________________________ ______________________________________________ Asthma Report » DOH Data » State Specific Node Client Tribe A __________________________________________________________________________________________________________________________________ __________________________________________ _______________________________________________________________ Tribal Member Member Data Tribe B Local Data Server Data and Services Node Client Spreadsheet WQX Tribe B FRS AQS EPA Data Analysis Tools ________________________________________________________________________________________________________________________ ______________________________________________ » NCM » MD » KM » Tools » Links Data NCM
QUESTIONS? • First, our questions for you: • Do you have good (web-based) Air, Water or Waste applications we should look at? • How have you successfully supported less-resourced partners in USING data? • Who else is doing what we are?! • Your questions