HierarchicalDEA-ValueAdditive_preferenceRelations

Version:1.0
Provider:PUT
SOAP service’s name:
 HierarchicalDEA-ValueAdditive_preferenceRelations-PUT (see SOAP requests for details)

Description

Computes necessary and possible preference relations for the pairs of DMUs (alternatives) using Additive Data Envelopment Analysis Model with hierarchical structure of inputs and outputs.

Contact:
Anna Labijak <anna.labijak@cs.put.poznan.pl>

Inputs

(For outputs, see below)

units

A list of alternatives (DMUs).

The input value should be a valid XMCDA document whose main tag is <alternatives>. It must have the following form:

<alternatives>
        <alternative>
            [...]
        </alternative>
        [...]
    </alternatives>

inputsOutputsScales

Information about inputs and outpus (leaf criteria) scales (preference directions) and optionally about boundaries

The input value should be a valid XMCDA document whose main tag is <criteriaScales>. It must have the following form:

<criteriaScales>
<criterionScale>

<criterionID>[…]</criterionID> <scales>

<scale>
[…]

</scale>

</scales>

</criterionScale> […]

</criteriaScales>

performanceTable

A list of alternatives (DMUs) performances (on leaf hierarchy criteria).

The input value should be a valid XMCDA document whose main tag is <performanceTable>. It must have the following form:

<performanceTable>
                                <alternativePerformances>
                                        <alternativeID> [...] </alternativeID>
                                        <performance>
                                                <criterionID>
                                                        [...]
                                                </criterionID>
                                                <values><value>[...]</value></values>
                                        </performance>
                                        [...]
                                </alternativePerformances>
                                [...]
                        </performanceTable>

hierarchy

The hierarchical structure of criteria.

The input value should be a valid XMCDA document whose main tag is <criteriaHierarchy>. It must have the following form:

<criteriaHierarchy>
                                <nodes>
            <node>
                <criterionID>[...]</criterionID>
                <nodes>
                    <node>
                        <criterionID>[...]</criterionID>
                        [...]
                    </node>
                    [...]
                </nodes>
            </node>
        <nodes>
                        </criteriaHierarchy>

weightsLinearConstraints (optional)

A list of hierarchy criteria linear constraints.

The input value should be a valid XMCDA document whose main tag is <criteriaLinearConstraints>. It must have the following form:

<criteriaLinearConstraints>
    <constraints>
        <constraint>
            <elements>
                <element>
                    <criterionID> [...] </criterionID>
                    <coefficient>
                        [...]
                    </coefficient>
                </element>
                [...]
            </elements>
            <operator>[...]</operator>
            <rhs>
                [...]
            </rhs>
        </constraint>
        [...]
    </constraints>
</criteriaLinearConstraints>

methodParameters

Represents parameters.
“hierarchy node” is the ID of the hierarchy criterion for which the analysis should be performed; “transformToUtilities” means if data should be tranformed into values from range [0-1]; “boundariesProvided” means if inputsOutputs file contains information about min and max data for each factor.

The input value should be a valid XMCDA document whose main tag is <programParameters>. It must have the following form:

<programParameters>
    <parameter id="hierarchyNode">
        <values>
            <value><label>%1</label></value>
        </values>
    </parameter>
    <parameter id="transformToUtilities">
  <values>
    <value><boolean>%2</boolean></value>
  </values>
            </parameter>
            <parameter id="boundariesProvided">
  <values>
    <value><boolean>%3</boolean></value>
  </values>
            </parameter>
</programParameters>

where:

  • %1 is a parameter named “hierarchy node”. This is a string. The default value is root.
  • %2 is a parameter named “transform to utilities”. This is a boolean. The default value is true.
  • %3 is a parameter named “boundaries provided”. This is a boolean. The default value is false.

Outputs

necessaryDominance

A matrix containing necessary preference relation between pairs of DMUs.

The returned value is a XMCDA document whose main tag is <alternativesMatrix>. It has the following form:

<alternativesMatrix>
                            <row>
        <alternativeID>[...]</alternativeID>
        <column>
            <alternativeID>[...]</alternativeID>
            <values>
                <value><integer>1</integer></value>
            </values>
        </column>
        [...]
    </row>
    [...]
                    </alternativesMatrix>

possibleDominance

A matrix containing possible preference relation between pairs of DMUs.

The returned value is a XMCDA document whose main tag is <alternativesMatrix>. It has the following form:

<alternativesMatrix>
                            <row>
        <alternativeID>[...]</alternativeID>
        <column>
            <alternativeID>[...]</alternativeID>
            <values>
                <value><integer>1</integer></value>
            </values>
        </column>
        [...]
    </row>
    [...]
                    </alternativesMatrix>

messages

A list of messages generated by the algorithm.

The returned value is a XMCDA document whose main tag is <programExecutionResult>.

Original xml description