1 / 30

RIMIS

RIMIS. Regional Integrated Management Information System M. A. Cameron a , B. Croke bc , K. L. Taylor a , G. Walker a , B. Watson c a CSIRO Mathematical & Information Sciences Internet Marketplaces Group b ANU CRES c ANU iCAM. This Presentation. Requirements

laird
Download Presentation

RIMIS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RIMIS Regional Integrated Management Information System M. A. Cameron a, B. Croke bc, K. L. Taylor a, G. Walker a, B. Watson c a CSIRO Mathematical & Information SciencesInternet Marketplaces Groupb ANU CRESc ANU iCAM

  2. This Presentation • Requirements • Salinity Problem Environment • A Vision of RIMIS • RIMIS Components • EPSS Interface

  3. Requirements • Facilitate interactive analysis of integrated resource management tradeoffs • Targeting salinity reduction with respect to land use change within catchments • Facilitate community consultation processes

  4. Salinity Problem Environment • 1 Data from all States, Qld only for 2050. • 2 Data from WA, SA, Vic and NSW, Qld only for 2050. • 3 Data from WA, SA, Vic and NSW. • 4 Including Ramsar wetlands. • 5 Much of the remnant and perennial vegetation reported for each State occurs on agricultural lands.

  5. Salinity Problem Environment • Multi-stakeholder • Catchment Management Board (CMB), individuals, communities, commercial/non-commercial organisations, Local, State and Federal Government • Multi-role • domain specialist, problem solver, interested public • The problem is… • Multiple perspectives on problem(s) and acceptable management option(s) • Patchy data environment • Distributed, fragmented heterogeneous sources • Domain specific modelling expertise • but an integrated view needed

  6. Achieves integration across disciplines, scales, issues & organisations for catchment management issues Shopfront between problem stakeholders and professional domain experts Extensible Architecture in terms of data and process models permitting the CMB to re-configure aspects of RIMIS in response to evolving needs, typical of catchment management problems Delivers data access & integration from a range of data custodians A Vision of RIMIS

  7. A Vision of RIMIS • Discovery and exploration of complex data • through hyper-media linking and visualization of information across organizations • Access to baseline data • for biophysical, social and economic process models relevant to the problem at hand • Problem focused exploration of issues and goals through an explicit statement of problem definition: • the context in which the problem occurs; • the process models active for the problem; • the proposed action plan interventions explored as part of the problem solving process; and • a record of the simulated outcomes of those action plans.

  8. RIMIS Components • Website • Public site for community information & selected trade-offs • Secure for CMB, domain specialists • EPSS • Problem management interface • Models are Web Services • IMP infrastructure

  9. EPSS Interface • ‘when faced with <problem>, what <outcome> might we observe if we do <action plan> assuming <scenario>?’ • Interface between CMB and domain specialists • CMB gets to define problem • Domain specialists model problem • Data sources • Process models • Model flow to coordinate and link information flow among process models • Problem solver explores scenario-action plan-outcome

  10. Infrastructure Components • Each model node in model flow encapsulates a composition of: • general filter & transform operations • model invocation on transformed data • data store invocation (for memory of model outcome) • Problem solvers are not generally interested in this techno-babble view, although useful at design time • Model flow is a simplified domain specific representation of information flow among: • Data source(s) • Domain dependant models • Domain independent data store(s)

  11. Infrastructure Components

  12. Infrastructure Components

  13. Infrastructure Components

  14. Future Work • Installation at NSW Department of Land and Water Conservation, October 2002 • Feedback from Domain Specialists, CMB members, Problem Solvers and DLWC IT Support • Domain Specialist Tools for Adding New Models • Commercialisation • Have we missed anything?

  15. RIMIS Regional Integrated Management Information System M. A. Cameron a, B. Croke bc, K. L. Taylor a, G. Walker a, B. Watson c a CSIRO Mathematical & Information SciencesInternet Marketplaces Groupb ANU CRESc ANU iCAM

More Related