Once the cleaning has been completed, the driver of the equipment may sign off the cleaning, completing the scenario.

Sign off eECD by driver

PUT {eecdapi}/equipment/{equipmentId}/cleaningactions/{cleaningId}/signoff

Usage

  • Driver signs off the cleaning 

Information

Remark

  • This signature is not to be mistaken by the cleaning completion which also requires a signature in the physical flow which becomes redundant with the digital eECD process, as shown in the below snippet of a digital eECD.

Body

Sign off Cleaning

{
    "DriverName": "string",
    "DriverComments" : "string",
    "Signature": "data:image/png;base64,.."
}
JSON

Example

Sign off example

{
    "DriverName": "John Doe",
    "DriverComments" : "Tastes well",
    "Signature": "data:image/png;base64,OIHLJLKJKLJIUOIUIUH65468724s6dqsdf7r89a7erf8[...]"
}
JSON

Validation

To be completed

Result

Get EFTCO codes

{
    "DriverName": "string",
    "DriverComments" : "string",
    "Signature": "data:image/png;base64,..."
}
JSON

Add comments

POST {eecdapi}/equipment/{equipmentId}/cleaningactions/{cleaningId}/postsignoffcomment

Usage

  • Add comments after driver sign-off 

Information

  • This call can only be done if no new load has already been planned for the equipment.

Body

A simple string containing the comment:

Validation

To be completed

Result

The entire cleaning action, with the new added comment

Get signature

GET {eecdapi}/equipment/{equipmentId}/cleaningactions/{cleaningId}/signature

Usage

  • Get a signature for a cleaning

Result