Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Contents

Key


This page shows the set of Standard Tasks within the system. These tasks have been designed so that they can be assembled together in any order to create a variety of end-to-end Workflows (subject to some validation)


Receive & Put-Away

Pick, Pack & Release

Transport

Receive From Agent

Handover To Agent

End Customer Schedule

White Glove Partner Instruction

The above shows the main state transition model for this Task. However there can be a set of one or more sub-tasks that can be configured by the SEKO operator, based on the requirements of the situation. The task is only complete as a whole once all sub-tasks have been completed by the White Glove Partner, and evidenced via completed documentation, attached photos and videos.

The available sub-tasks can be one or more from any of the following sub-task Types:

  • Site Survey

  • Transport (of Goods to stated End Customer Site)

  • Assemble / Install (the Goods to form the final end-customer product)

  • Dismantle (the Goods, in preparation for later goods transfers)

  • Maintenance (go to stated End Customer Site and perform maintenance on their product)

Each kind of sub-task has a set of associated documents / questionnaires applicable to that sub-task and the Client, that must all be filled in by the White Glove Partner as part of proof of completion of the overall Task.

The SEKO operator will be able to select manually the required document / form and accompanying documents or instruction manuals, limited by the Client and the sub-task-type applicable.

For example the Assemble / Install, Dismantle or Maintenance sub-tasks will each have their own POQ (proof of quality) which must be be filled in; the SEKO operator will attach the applicable POQ to the Task, see the details and any additional photos / videos that the White Glove Partner filled in, and can then ‘approve’ the overall Task.

  • No labels