Concept

The sequence of actions in the Concept phase may vary slightly depending on the selected procedure option: scalar, MOS, or SOS. Specifically, for MOS and SOS, certain steps from the Design phase must be performed concurrently with the Concept phase. This section starts with a general introduction to the DPSIR framework within mDSS, followed by an overview of the Catalogue of DPSIR Indicators and the Catalogue of Options. It then provides a detailed explanation of the steps users need to follow for each procedure option.

The DPSIR Framework

The Concept phase is based on the Driving Force-Pressure-State-Impact-Response (DPSIR) framework. This tool facilitates the conceptualization of the problem, outlining the options and defining the indicators used to evaluate them during the analysis. The experiences gained by using the earlier versions of the software confirmed the potential of the DPSIR approach.

Figure 4. Initial View of the DPSIR Page

When a new or existing project is opened, the DPSIR window automatically appears in both the scalar and MOS cases. In the SOS case, however, an additional intermediate step is required to generate a graphical visualization of the completed framework, as explained in the following paragraphs. Despite these variations, the core task in this phase remains consistent across all three cases: the user must conceptualize the problem by linking the necessary indicators for quantitative analysis to the corresponding DPSIR nodes and creating a schematic representation of the causal relationships between the different variables.

The nodes of the DPSIR framework are implemented as buttons. By clicking on the “Driving Force”, “Pressure”, “State”, “Impact”, or “Response” buttons the user can move them across the frame, to improve the quality of the graphical representation, in particular when it becomes crowded with long lists of indicators and links. Further options can be accessed by right-clicking on any of the “Driving Force,” “Pressure,” “State,” or “Impact” buttons. This action opens the program window displaying the Catalogue of DPSIR Indicators. Clicking on “Catalogue of DPSIR Indicators”, users can compile or edit indicators within the Indicator Window (refer to the following sections for more details). Within this window, the indicators are categorized into four groups: Driving Force (D), Pressure (P), State (S), and Impact (I).

Similarly, the alternative options are linked to the Response button. Right-clicking on the “Response” button itself allows the user to open both the Catalogue of Response Measures and the Catalogue of DPSIR Indicators. Right-clicking on an option’s name opens a window displaying the specific details of that option.

Figure 5. Final Visualization of the DPSIR Framework Applied to the Case Study

Figure 5 depicts the final window of the DPSIR framework applied to the Auronzo di Cadore case study. In this simple(scalar) scenario, the project’s considered options(Responses), defined at the beginning of the Design phase, are BAU (Business As Usual), Ski-intensive, Alternative skiing, and Beyond-skiing. These options are assessed based on the criteria outlined in the DPSI nodes, with the quantitative analysis focusing only on the blue indicators—those sent to the AM.

Figure 5 also demonstrates the Link feature, showing a connection between the Pressure Indicator “Artificial snow” and the State Indicator “Snow cover.” This feature in mDSS helps enhance users’ understanding and conceptualization of the problem being analyzed, even though it does not have a direct impact on subsequent quantitative analysis.

By right-clicking instead on a selected indicator, the user can:

  • see the indicator’s details (“Show indicator details”);
  • add (“Add link”) and remove (“Remove link”) links between indicators;
  • isolate the DPSI chains to which the selected indicator belongs (“Show related ’indicator’ links”), or show only the indicators related to the one selected in the other lists (“Show only related ’indicator’ links”).
  • delete “X” item

By right-clicking on one of the DPSIR arrows, a menu of options is activated, including:

  • Show all indicators and links;
  • Show all indicators;
  • Show only chains from which no indicator has been sent to AM;
  • Load indicators’ values (from an existing catalogue);
  • Save all indicators’ values (to a new catalogue);
  • Save image as jpg;

The Catalogue of Indicators

As stated before, right-clicking on the Driving Force, Pressure, State, or Impact buttons allows the user to open the Indicators Window. The Indicators Window (Figure 6) enables users to upload, create, and view the Catalogue of DPSIR Indicators. This catalogue offers a comprehensive list of relevant indicators to assess the problem and support decision-making during the working session. Each indicator is accompanied by detailed information, such as its unit of measure, to enhance understanding and facilitate informed choices. This catalogue is specifically designed to support a comprehensive evaluation of the problem at hand within the DPSIR framework (Driving Force, Pressure, State, Impact, and Response).

Figure 6. Example of Indicators Window where “External Catalogue” is checked

In mDSS, indicators are organized into two types of catalogues: External and Internal. External catalogues are not tied to any specific project; instead, they contain a broad range of indicators that can be selected to create a customized list for a particular project. The indicators chosen by the user for the analysis are placed in the Internal Catalogue, which is specific to the project at hand. For example, a policymaker specializing in ecosystem restoration may possess a comprehensive and diverse collection of indicators, developed over years of workshops with a wide range of stakeholders. For each case study, they can select the most relevant indicators for the specific ecosystem, creating a customized internal catalogue that aligns with the unique needs of the project.

In the Indicator Window, when the External Catalogue option is checked, the user can open an existing Catalogue (“Open catalogue” button) or, after expanding the window by clicking on the “More” button on the right, create a new catalogue. The new Catalogue can be created ex-novo by selecting “External” and pressing the “More” button, thus being prompted to a blank indicator catalogue that the user can later save (Save button) in .xlsx format.

To add indicators from the External Catalogue to the Internal Catalogue, first select the desired indicator from the left-side list in the Indicator Window, then click the “Select for X list” button. The value of “X” can be D, P, S, or I, depending on the node where the user opens the Indicator Window by right-clicking. For example, if the user double-clicks on the “Pressure” node and selects the “Artificial Snow” indicator, clicking the “Select for P list” button will add that indicator to the Pressure list in the Internal Catalogue (Figure 7).

When the Internal Catalogue option is checked, the user can also directly open an existing catalogue, update it, save the current catalogue and, after expanding the window by clicking on the “More” button on the right, update the indicators details in the Internal catalogue. Ideally, once the final .xlsx catalogue file is prepared, the user can quickly complete the DPSIR indicators setup by selecting the “Internal Catalogue” option and uploading the file.

Notably, the Catalogue of Indicators does not include the numerical values of each indicator for the various options to be evaluated. Its purpose is solely to provide a list and a description of the indicators used in the analysis. The assignment of quantitative values to these indicators, depending on the chosen analytical method, represents an additional distinct step in the process.

Figure 7. Example of Item Description in the Indicator Window

On the right-side of the Indicators Window the item description is shown, as presented in Figure 8. For each indicator, the user should define the Sector (the macro area linked to the indicator i.e. Natural Resources, Local Economy, and so on), a brief description, the measurement unit, the most frequent role in the DPSI chain,  the link with one of the three different dimensions of sustainable development (Social, Environmental, Economic), the catalogue of provenience, some user’s comments, and the possible source. The consistency range refers to the interval of values that can be correct for a certain indicator.

At least the first four fields (i.e. the sector, full name, description, and unit) and the most frequent role played by the indicator must be specified in order to be able to save a new indicator. To add a new item to the Catalogue of DPSIR Indicators, the user should first click the “More” button, then fill in the required details for the Indicator, and finally click the “New Item” button to save the entry.

 By clicking on the “More” button the user can also analyze the list of indicators with simple queries using logical functionalities (“and”/“or”), including or not the selected indicator.

The Catalogue of Response Measures

Right-clicking on the “Response” button opens the Catalogue of Response Measures window, where alternative measures are displayed (Figure 7). Defining the various alternatives to be evaluated is considered the first step in the Design phase, although this step may be closely linked to the Conceptual phase due to practical software requirements. In any case, the specific steps for each analysis method (Spatial, MOS and SOS) will be outlined in the following sections.

Figure 7. Catalogue of Response Measures for the Auronzo di Cadore Case Study

The measures (Options) are organized into a catalogue, and the window is structured similarly to the Indicator Window. For each response, the following details are provided: the code, full name, target, category, involved actors, a brief description, and the source.

Similar to the Catalogue of DPSIR Indicators, the Catalogue of Response Measures serves to list and provide information about the various alternative options. An additional, distinct step in the process involves assigning different values to each indicator, based on the selected analytical method.

Starting from Scratch

This section outlines the key steps a user must follow to successfully complete the Concept phase and advance to the Design phase. The three available methods — Scalar, MOS, and SOS — each have a distinct approach to these steps, shaped by the characteristics of the chosen method and the specific requirements of the software structure.

1. The Scalar Case

To begin a new scalar analysis from the mDSS homepage, as outlined in the Introduction, the user must click on File -> New .mD5 Project -> Scalar. The software then directs the user to the “Conceptual” phase of the mDSS session, opening an empty DPSIR window as shown in Figure 4.

Next, the user should right-click on one of the DPSIR nodes and select Catalogue of DPSIR Indicators to display the Indicator Window, as shown in Figure 6-7. Following the outlined steps, the user can create a catalogue of indicators or upload and modify an existing one.

Once the Internal Catalogue is ready, with each indicator linked to the appropriate node, the user can close the Indicator Window. It is important to note that the final Internal Catalogue can be saved in a .xlsx file and easily uploaded in future sessions. This applies whether the catalogue was created within mDSS or developed externally in a .xlsx file, as long as it adheres to the software’s required structure.

After uploading the indicators, the user should right-click on the Response node and follow the analogous procedure to complete the Catalogue of Response Measures. As with the Internal Catalogue, it is advisable to save the Catalogue of Response Measures so that it can be easily re-uploaded in future sessions.

After completing these two steps, the DPSIR window will resemble the one shown in Figure 8.

Figure 8. DPSIR Window in the Scalar case, after uploading both Catalogues.

The next steps involve the Design Phase, where the user identifies the criteria to be considered in the analysis and assigns values to each criterion for all available options. For a comprehensive explanation of the subsequent steps, please refer to Chapter 4.

2. The Spatial Planning Case (MOS)

To begin a new MOS analysis from the mDSS homepage, the user must click on File -> New .mD5 Project -> Spatial Planning (MOS). To proceed with the Concept Phase and access the DPSIR window, mDSS requires the user to upload three files:

  • A .dbf file containing attribute data.
  • A .shp (shape file)
  • A .shx (index file)

An example of a .dbf file is shown in Figure 9, which corresponds to the case study of Auronzo di Cadore. This file format is used to store attribute data in a tabular form and is commonly paired with shapefiles (.shp) and index files (.shx) in geographic information systems (GIS). Together, these files contain information about geographic features, such as locations, types, and other attributes, all linked to specific spatial coordinates.

In the context of mDSS, a .dbf file should include the following elements:

  • Geographical Identifier. A column that uniquely identifies the geographical units, such as REC_NUM (a numerical ID) or NAME (the name of the unit), ensuring clear and distinct reference for each spatial object.
  • Spatial Characteristics. Columns provide key characteristics of the geographical unit, which can aid in the weighting process during analysis. For instance, Population and Area (denoted as AREA) are useful for considering the size and demographic features of the unit.
  • Indicator Values for Different Scenarios. Grouped columns that contain the values of different indicators for each option or scenario being analysed. For example, columns such as INVST_1 and INVST_2 represent the values of the “Investment costs” indicator under two distinct scenario options. This enables comparison and further evaluation of alternative outcomes.

By organizing the .dbf file in this way, the data can support a thorough analysis and facilitate the subsequent stages of the mDSS process, such as weighting and decision-making.

Figure 9. Example of a .dbf file uploaded in mDSS. The file refers to the case study of Auronzo di Cadore.

Once the three files are selected, mDSS directs the user to the initial, empty DPSIR window, similar to the one shown in Figure 4. At this stage, the user needs to upload the Catalogue of DPSIR Indicators and the Catalogue of Response Measures, as described in the previous section. This can be done by right-clicking on one of the DPSIR nodes.

The key difference between the steps in the Scalar case and the MOS approach (as well as the SOS approach) lies in the preparation required before initiating the mDSS session. For MOS, users must first define and prepare the indicators and options. This includes selecting the relevant indicators, specifying the options to be analysed, and assigning values to the indicators. This preparatory work is essential to ensure that all necessary data is available and properly structured for the system input. In contrast, in the Scalar context, users can define the indicators during the Concept Phase and assign values to them only during the Design Phase.

For MOS (and SOS), the selection of indicators, options, and values must be completed before the mDSS session begins. Importantly, mDSS does not require that all uploaded indicator columns be used in the quantitative analysis. It only requires that the relevant indicators intended for analysis be uploaded according to the specified procedure. For example, a user may upload in the .dbf file indicator columns for Biodiversity such as BIODIV_1 and BIODIV_2, but choose not to include them in the subsequent quantitative analysis.

Figure 10. User’s View after uploading the two Catalogues in the MOS case.

Once the Catalogue of DPSIR Indicators and the Catalogue of Response Measures are uploaded, the user will be presented with a Concept window similar to the one shown in Figure 10. At this stage, the two uploaded Catalogues are not yet linked to the .dbf file. At the beginning of the Design Phase, the user will need to specify to mDSS which column of the .dbf file corresponds to the “Investment costs” indicator for “OPT1” and which column corresponds to “Investment costs” for “OPT2,” as well as mapping the relevant columns for all other selected indicators. The steps to proceed with the Design Phase in the MOS case are outlined in Chapter 4.

3. The Location/Suitability Analysis Case (SOS)

To begin a new SOS analysis from the mDSS homepage, the user must click on File -> New .mD5 Project -> Location/Suitability Analysis (SOS). To proceed with the Concept Phase and access the DPSIR window, mDSS requires the user to upload three files:

  • A .dbf file containing attribute data.
  • A .shp (shape file)
  • A .shx (index file)

The user can also choose to upload only the .dbf file, but this choice will result in the loss of the spatial dimension of the analysis. For example, in this case, the user would lose the ability to visualize the spatial distribution of the analysis scores. Notably, mDSS supports a maximum dimension for the .dbf file of 10,000 cells. This translates to a maximum of 1,000 spatial objects and 100 columns (which can include indicators, unique codes, information, etc.), or other similar combinations.

Figure 11. Indicator Window displayed after uploading the required files in the SOS case.

After uploading the required file(s), mDSS presents the usual Indicator Window to the user, as illustrated in Figure 11. At this point, the user can upload a Catalogue of DPSIR Indicators from a .xlsx file. From this file, only those indicators with corresponding field names in the previously selected .dbf file will be selected. Importantly, in this window, only the “Internal” catalogue function can be chosen. This first step is optional, as the same operation can be performed later from the standard DPSIR window during the Concept Phase. If the user prefers to postpone this step, they can close the window by clicking the top-right button.

After completing the first step, mDSS will display a window similar to the one shown in Figure 12. The top section of the window features a tabular view of the uploaded .dbf file, with the names of the columns (representing the indicators) displayed in bold. The lower part of the window is divided into three sections, designed to assist the user in uploading the input parameters for the single-option spatial planning (SOS) in mDSS.

Figure 12. Window displayed after completing the Indicator phase in the SOS case.

Firstly, the user must select the column containing the unique code that identifies the spatial object. This can be done from the menu under the label “Select the Options field”. For the Auronzo di Cadore case study, the column “REC_NUM” is selected, as shown in Figure 13, although “NAME” could also be a valid option.

To assign an indicator to the correct DSIR node, the user should first select it from the central list labelled “List of Possible Indicators.” Then, the user can click the right-directed arrow to move the indicator to the appropriate node. To choose the specific node for assignment, the user can navigate through the DPSIR menu under the label “Selected Indicators.” If the user wants to remove an indicator from a node, they can select its name in the right list and click the left-directed arrow.

Figure 13

The user can repeat this process and upload the choices made in this phase by navigating to the Main Menu and selecting File > Update Location/Suitability Analysis (SOS).

Once the process is complete, the user can click the “OK” button to return to the standard DPSIR window. At this stage, the user can upload a Catalogue of DPSIR Indicators and/or a Catalogue of Response Measures. To proceed to the Design Phase and access the Analysis Matrix, the user must click the “Design” button in the Tab Bar. Detailed instructions for advancing to the Design Phase in the SOS case are provided in Chapter 4.