Version: | 1.0 |
---|---|
Provider: | PUT |
SOAP service’s name: | |
ImpreciseDEA-ValueAdditive_preferenceRelations-PUT (see SOAP requests for details) |
Computes efficiency scores for the given DMUs (alternatives) using Additive Data Envelopment Analysis Model with imprecise information.
Contact: Anna Labijak <support@decision-deck.org>
Reference: G. Jahanshahloo, F. H. Lotfi, M. R. Malkhalifeh, and M. A. Namin. A generalized model for data envelopment analysis with interval data. 2009.
Reference: MC. Gouveia et al. Super-efficiency and stability intervals in additive DEA. 2013
(For outputs, see below)
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>
A list of criteria with specified preference direction. List has to contains at least one criterion that will be minimized (input) and at least one criterion that will be maximized (output).
The input value should be a valid XMCDA document whose main tag is <criteria>
.
It must have the following form:
<criteria>
<criterion>[...]</criterion>
[...]
</criteria>
Informations about inputs and outputs scales 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>
Shapes of functions assigned to inputs and outputs (if other than linear)
The input value should be a valid XMCDA document whose main tag is <criteriaFunctions>
.
It must have the following form:
<criteriaFunctions>
- <criterionFunction>
<criterionID>[…]</criterionID> <functions>
- <function>
- <piecewiseLinear>
- <segment>
- <head>
- […]
</head> <tail>
[…]</tail>
</segment>
</piecewiseLinear>
</function> […]
</functions>
</criterionFunction> […]
</criteriaFunctions>
A list of alternatives (DMUs) minimal performances (or exact performances if intervals should be created by tolerance).
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>
A list of alternatives (DMUs) maximal performances.
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>
A list of 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>
The input value should be a valid XMCDA document whose main tag is <programParameters>
.
It must have the following form:
<programParameters>
<parameter id="tolerance">
<values>
<value><real>%1</real></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>
<parameter id="functionShapeProvided">
<values>
<value><boolean>%4</boolean></value>
</values>
</parameter>
</programParameters>
where:
%1 is a parameter named “tolerance”. This is a float, and the value should conform to the following constraint: The value should be non-negative.. More formally, the constraint is:
%1 >= 0
The default value is 0.00.
%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.
%4 is a parameter named “function shapes provided”. This is a boolean. The default value is false.
A list of pairs of pairs of DMU related with necessary preference relation.
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>
A list of pairs of pairs of DMU related with possible preference relation.
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>
A list of messages generated by the algorithm.
The returned value is a XMCDA document whose main tag is <programExecutionResult>
.