| Version: | 1.0 |
|---|---|
| Provider: | PUT |
| SOAP service’s name: | |
HierarchicalDEA-CCR-SMAA_efficiencies-PUT (see SOAP requests for details) |
|
Computes efficiency scores for the given DMUs (alternatives) using SMAA-D method and CCR Data Envelopment Analysis Model with hierarchical structure of outputs. For given number of buckets and samples, returns a matrix with alternatives in each row and buckets representing efficiency intervals in each column. Single cell indicates how many samples gave efficiency scores of respective alternative in respective bucket.
(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 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>
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>
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>
“number of samples” represents the number of samples to generate; “number of buckets” represents the number of buckets which efficiency scores will be assigned to; “hierarchy node” is the ID of the hierarchy criterion for which the analysis should be performed.
The input value should be a valid XMCDA document whose main tag is <programParameters>.
It must have the following form:
<programParameters>
<parameter id="samplesNb">
<values>
<value><integer>%1</integer></value>
</values>
</parameter>
<parameter id="intervalsNb">
<values>
<value><integer>%2</integer></value>
</values>
</parameter>
<parameter id="hierarchyNode">
<values>
<value><label>%3</label></value>
</values>
</parameter>
<parameter id="randomSeed">
<values>
<value><integer>%4</integer></value>
</values>
</parameter>
</programParameters>
where:
%1 is a parameter named “number of samples”. This is a int, and the value should conform to the following constraint: The value should be a positive integer.. More formally, the constraint is:
%1 > 0
The default value is 100.
%2 is a parameter named “number of buckets”. This is a int, and the value should conform to the following constraint: The value should be a positive integer.. More formally, the constraint is:
%2 > 0
The default value is 10.
%3 is a parameter named “hierarchy node”. This is a string. The default value is root.
%4 is a parameter named “random seed (-1 for default time-based seed)”. This is a int, and the value should conform to the following constraint: The value should be a non-negative integer or -1 if no constant seed required.. More formally, the constraint is:
%4 >= -1
The default value is -1.
A performance table for given alternatives. Single performance consists of attribute criterionID representing certain bucket, and a value representing the ratio of efficiency scores in this bucket.
The returned value is a XMCDA document whose main tag is <performanceTable>.
It has the following form:
<performanceTable>
<alternativePerformances>
<alternativeID> [...] </alternativeID>
<performance>
<criterionID>[...]</criterionID>
<values>
<value>[...]</value>
</values>
</performance>
[...]
</alternativePerformances>
[...]
</performanceTable>
A list of alternatives with maximum efficiency scores (obtained with sampling).
The returned value is a XMCDA document whose main tag is <alternativesValues>.
It has the following form:
<alternativesValues>
<alternativeValue>
<alternativeID> [...] </alternativeID>
<values>
<value>
[...]
</value>
</values>
</alternativeValue>
[...]
</alternativesValues>
A list of alternatives with computed minimum efficiency scores (obtained with sampling).
The returned value is a XMCDA document whose main tag is <alternativesValues>.
It has the following form:
<alternativesValues>
<alternativeValue>
<alternativeID> [...] </alternativeID>
<values>
<value>
[...]
</value>
</values>
</alternativeValue>
[...]
</alternativesValues>
A list of alternatives with average efficiency scores (obtained with sampling).
The returned value is a XMCDA document whose main tag is <alternativesValues>.
It has the following form:
<alternativesValues>
<alternativeValue>
<alternativeID> [...] </alternativeID>
<values>
<value>
[...]
</value>
</values>
</alternativeValue>
[...]
</alternativesValues>
A list of messages generated by the algorithm.
The returned value is a XMCDA document whose main tag is <programExecutionResult>.