Monitoring Plan Compatibility

Last updated
Save as PDF

Information about the compatibility of the sensor requirements of a monitoring plan with a trailer is implemented as the MonPlanCompatibility object. The attributes of a MonPlanCompatibility object are:

Attribute	Description
cargoSensor	A string indicating whether or not the trailer is compatible with the monitoring plan's cargo sensor requirement. Possible values are: 0 Trailer compatible with sensor requirement 2 Trailer incompatible with sensor requirement, and missing required sensor
doorSensor	A string indicating whether or not the trailer is compatible with the monitoring plan's door sensor requirement. Possible values are: 0 Trailer compatible with sensor requirement 2 Trailer incompatible with sensor requirement, and missing required sensor
auxSensor	A string indicating whether or not the trailer is compatible with the monitoring plan's auxiliary sensor requirement. Possible values are: 0 Trailer compatible with sensor requirement 2 Trailer incompatible with sensor requirement, and missing required sensor
overall	A string indicating whether or not the trailer is compatible with the monitoring plan's overall requirements. Possible values are: 0 Trailer compatible with requirements 2 Trailer incompatible with requirements; a sensor or reefer requirement is not met

Example XML

Below is sample XML that shows how the Monitoring Plan Compatibility object will look in XML.

<checkMonitoringPlanCompatibilityReturn>

<cargoSensor>0</cargoSensor>

<doorSensor>0</doorSensor>

<auxSensor>0</auxSensor>

<overall>0</overall>

</checkMonitoringPlanCompatibilityReturn>

WSDL Definition

Below is how the Monitoring Plan Compatibility object is defined in the WSDL

<complexType name="MonPlanCompatibility">

<sequence>

<element name="cargoSensor" nillable="true" type="xsd:string"/>

<element name="doorSensor" nillable="true" type="xsd:string"/>

<element name="auxSensor" nillable="true" type="xsd:string"/>

<element name="overall" nillable="true" type="xsd:string"/>

</sequence>

</complexType>