Difference between revisions of "EMDS"
(→Capability to support decision making phases) |
(→Models) |
||
| Line 78: | Line 78: | ||
All logic and decision models used by the system are user defined. | All logic and decision models used by the system are user defined. | ||
| − | Logic models are designed in NetWeaver Developer | + | Logic models are designed in [http://rules-of-thumb.com NetWeaver Developer]. |
| + | |||
| + | Decision models are designed in [http://www.infoharvest.com Criterium DecisionPlus]. | ||
== Decision Support == | == Decision Support == | ||
Revision as of 00:39, 2 December 2009
General System description
System name: Ecosystem Management Decision Support
Acronym: EMDS
Brief overview
The Ecosystem Management Decision Support (EMDS) system is a general solution framework for knowledge-based decision support of ecological assessments at any geographical scale.[[Category:]] [[Category:]]
Contents
Scope of the system
The system provides decision support for landscape-level analyses through logic and decision engines integrated with the ArcGIS geographic information system. The NetWeaver logic engine evaluates landscape data against a formal logic specification designed in the NetWeaver Developer system, to derive logic-based interpretations of ecosystem conditions. The decision engine evaluates NetWeaver outcomes, and data related to the feasibility and efficacy of land management actions, against a decision model for prioritizing landscape features built with its development system, Criterium DecisionPlus. CDP models implement the analytical hierarchy process, the simple multi-attribute rating technique, or a combination of the two methods. The system has been used in a high variety of applications[1].
System origin
- EMDS was initially developed by the US Department of Agriculture, Forest Service under the direction of Dr. Keith M Reynolds (Pacific Northwest Research Station).
- Through version 3, the system was developed by the Environmental Systems Research Institute (ESRI) under federal government contract.
- EMDS development is now maintained by a private, non-profit development consortium hosted by the Redlands Institute. The core of EMDS remains in the public domain, but commercial products are used in conjunction with EMDS to support model development (see Related Software).
- There are numerous real-life applications of the system. Visit the EMDS page on Wikipedia for a list of EMDS applications and associated publications.
Support for specific issues
EMDS is a general solution framework, designed to support a wide variety of applications at any, or multiple spatial scales.
Support for specific thematic areas of a problem type
Typical areas of application include, but are not limited to, the following:
- Silviculture
- Certification
- Conservation
- Restoration
- Transportation
- Development choices / land use zoning
- Policy/intervention alternatives
- Sustainability impact assessment (SIA)
Capability to support decision making phases
- Design. User-designed logic models are used to assess the state of a system (e.g., watershed condition or wildfire potential).
- Choice. User-desigend decision models are used to set priorities for management activities among landscape elements.
- Monitor. The speifications of the logic and decision models collectively define the monitoring requirements needed to support a decision process.
- Repeated application of a logic model over time can be used to support change detection and plan performance.
Related systems
EMDS is an extension to ArcMap, and is also available in a stand-alone edition built on ArcEngine.
The system uses the logic engine of NetWeaver Developer, which is a knowledge-based decision-support system for logic-based inference. NetWeaver Developer is used to design the logic models used by EMDS.
The system also uses the decision engine of Criterium DecisionPlus, which implements the Analytic Hierarchy Process (AHP) and Simple Multi-Attribute Rating Technique (SMART) to support resource allocation decisions. CDP is used to design the decision models used by EMDS.
Projects are stored as either SQL Server of Microsoft Access databases, and spatial data are stored in ArcGIS file geodatabases.
Data and data models
Typical spatial extent of application
Spatial scale of an EMDS application is user defined, and with multiple scale interaction (projects can accommodate multiple scales of potentially linked assessments).
Forest data input
Data inputs are user defined. Data may represent biophysical, social, economic, or political attributes of a landscape unit.
Units of observation may be forests, stands, points (e.g., individual tree), lines (e.g., roads and streams), or any other GIS (vector) feature class (e.g., region, province, ecotype, etc.).
Raster data sets are not currently supported.
Type of information input from user (via GUI)
The user specifies what GIS layers are to be included in a specific assessment, and which logic and decision models are to be run against the specified set of layers.
Data provided to logic models can be edited "on the fly" by users in scenarios.
Both the logic and decision components of the system attempt to automatically match attribute field names from the input layers to model data-input fields. Dialog windows in each component present the resulting field mapping to the user for verification and, if necessary, editing.
Models
All logic and decision models used by the system are user defined.
Logic models are designed in NetWeaver Developer.
Decision models are designed in Criterium DecisionPlus.
Decision Support
Definition of management interventions
Define what is available for the manager to intervene in the forest: time of harvest, plantations, thinnings, reconversions... Existence of prescription writer, simple enumeration of all possibilities, scenario simulation , etc.
Typical temporal scale of application
Define the temporal scale of the application: E.g., operational and immediate level, Tactical planning (short term) and strategic level.
Types of decisions supported
- Management level
- strategic decisions
- administrative decisions
- operating control decisions
- Management function
- planning decisions
- organizing decisions
- command decisions
- control decisions
- coordination decisions
- decision making situation
- unilateral
- collegial
- Bargaining / participative decision making
Decision-making processes and models
- Logic modeling
- Operations research modeling
- Direct approaches
- Heuristic manipulation of simulation models
- Business modeling
- Simulation (with and without stochasticity)
- Multiple criteria/ranking
- Other
Output
Types of outputs
Types of outputs produced (tables, maps, 3-D visualizations, pre-programmed summaries, etc)
Spatial analysis capabilities
- integrated capabilities
- facilitates links to GIS (wizards, etc.)
- provides standard data import/export formats
- allows spatial analysis (e.g. topology overlays (e.g. multi layering of different maps, selection of objects based on selection criteria, aggregation by attributes (e.g. areas of similar characteristics), Linking by logical means, Statistics by area, analysis with digital terrain model)
Abilities to address interdisciplinary, multi-scaled, and political issues
Evaluate interactions between different basic information types (biophysical, economic, social). Produce coordinated results for decision makers operating at different spatial scales facilitate social negotiation and learning
System
System requirements
- Operating Systems: (Windows, Macintosh, Linux/UNIX, Web-based, Others)
- Other software needed (GIS, MIP packages, etc...)
- Development status
Architecture and major DSS components
Describe the basic architecture of the system in software and hardware. Desktop client-server, web based, as well as the integration with available systems. Basic data flow, focusing on retrieval of required input and propagation and implementations of decisions. Mention its modular and scalability capabilities.
Usage
Describe the level of use: Research level use, Industry use, Government use
Computational limitations
Describe the system limitations: e.g. number of management units, number of vehicles, time horizon
User interface
Describe the quality of user interface and the Prerequisite knowledge for using the system
Documentation and support
Describe the connection to Help-system and possibilities for assistance, as well as the required training and user support levels
Installation
- Prerequisite knowledge: Level of effort to become functional
- Cost: (purchase price, development costs, demonstrated return on investment, cost of use, training costs, licence and maintenance costs)
- Demo: allows the download/utilization of a trial version. If yes, where is it available and what are the trial conditions.
References
Please visit the EMDS page on Wikipedia for a list of EMDS applications and associated publications.
Cited references
- ↑ REYNOLDS, K.M., M. TWERY, M.J. LEXER, H. VACIK, D. RAY, G. SHAO et J.G. BORGES (2008): Decision Support Systems in Forest Management. In BURSTEIN, F. et C. W. HOLSAPPLE (Eds.): Handbook on Decision Support Systems 2: Variations. Springer Berlin Heidelberg. pp 499-533.
