All tasks go through certain status transitions, before being closed (delivered or cancelled). Within this article the various statuses and common flows will be explained.

InTask Status

An InTask is always the start of the order flow. An InTask is created by the active operator and contains work orders for the contractor. The InTask is the only visible task an Active operator can open from the task overview, whereas the Passive operator can both open InTasks and OutTasks. The contractor can only open the OutTask Tasks from the task overview.

However, all parties can see the corresponding InTask and OutTask statuses when opening a task from the overview.

New

This is the beginning status of a Task, that can only be seen by the Active Operator when creating a task via the API.

Network Check

After the Active Operator sends an order, Gridsz gathers all data needed from Availability Checker and Active Operator to check whether the Task meets the standard requirements. If there is no issue found, an OutTask is created that is sent to the Contractor.

Received

The Task is accepted by the platform after successfully passing the prior clean Task check and gets an unique ID. The task is now visible for both the active operator (as an InTask) and the contractor (as an OutTask). The status Received will only be set on the OutTask, whereas the InTask will received the status Confirmed.

Confirmed

The equivalent counterpart of received, visible to the Active Operator. So after successvully passing the clean Task check, the InTask will be set to the status Confirmed whereas the OutTask will be set to Received.

Network check was successful and the plan date is filled successful. Gridsz checks to make sure the task can be executed before creating a corresponding OutTask and then sends a sync to indicate the new task was received successfully. Active Operator can now be sure the task will be executed.

Prepared

The status Prepared is only visible to the Active Operator. This will be set on an InTask when all OutTasks have been confirmed (sync received).

WIP (Work In Progress)

The Task has been planned and is being executed by the contractor. The status change from Received to WIP is a manual update. SLA’s are in effect.

Delivered

The Contractor puts the InTask on Delivered whenever he completes a WIP Task. In the case of Network and Connection Incidents, the Contractor also needs to select a reason.

Provided

The Contractor finished the work of the task and changes the Task status to Delivered. The status of the InTask will appear PROVIDED for the AO, until manually accepted. The OutTask will appear as Delivered.

Administration

For some task types the network administration needs to be updated. After sending (DELIVERED) to the Active Operator, and before sending the update to Availability Checker the status of the InTask will appear as Administration for the Active Operator. For the Contractor, the OutTask status will remain on Delivered.

To be Cancelled

Request to stop the task is send by the Active Operator. The Active Operator needs to provide reasoning as to why the task should be cancelled. This status allows the Contractor to determine whether any work has already been completed.

Cancelled

The request to stop the task is confirmed by the Contractor. The OutTask is no longer available for the Contractor to execute, and both the InTask and OutTask have the status of Cancelled. The SLA is also stopped.

Terminated

A Task is denied by the contractor. The Contractor always has to give a reason for the terminated task, see reason codes in OutTask list below. Both the InTask and OutTask will receive the status Terminated.

Denied

The Clean Network check, as executed by GRIDSZ for every new order, failed and the new InTask is set to Denied for the active Operator to check the data plus reasoning. As a result, GRIDSZ will not create an OutTask, thus the Contractor will not receive anything.

OutTask status

The following statuses are use for the OutTasks:

Received

The Active Operator has created an new InTask. The InTask is available for the contractor and the work that needs to be done for this InTask is visible as one or multiple OutTask for the contractor, initially with the status Received.

WIP (Work In Progress)

Before an OutTask can be set to WIP, the Plan date has to be set. After setting an OutTask to WIP, both the TaskSet and InTask will be updated to WIP. In cases of severeal OutTasks, the remaining OutTask will stay on Received until manually set to WIP. The WIP is an indication to the Active Operator that the Contractor is working on the TASK.

On Hold

In certain scenarios, a task cannot be completed within the specified Plan Date, due to several potential reasons among which: customer not at home, PoP / DP inaccessible or technical path not found. In these cases, the Contractor can set an OutTask status to On Hold, after which the status of all related Tasks gets set to On Hold (Unless a Task has already been Delivered).

Once a TaskSet is set to On Hold, the SLA is paused and will remain so until the task is set back to its previous Status, either Received or WIP. If necessary, the Contractor needs to update the Plan Date when resuming the Task.

Delivered

The Task is successfully executed by the Contractor and set to Delivered. This is only in effect for the OutTask that the Contractor sets this Status to. In case of a singular OutTask, the TaskSet and InTask is also set to Delivered. The SLA calculation stops when setting an OutTask to Delivered.

Terminate

At all times, a Contractor has the option to Terminate a Task. However, it is compulsory to give a reason whilst doing so. When an OutTask Task is set to Terminate, all related Tasks are also set to Terminate, with the exception of Tasks that already achieve status Delivered.

To Be Cancelled

The status To Be Cancelled can only be selected by the Active Operator, when an task is already put On Hold by the Contractor.

This status is an indication for the Contractor to completely cancel the Task (Cancelled), but also allows the Contractor to determine whether any work has already been completed that needs to be billed or registered.

Cancelled

The status Cancelled always follows the status To Be Cancelled, and is a definitive end status. Meaning once a Contractor puts a task on status Cancelled, all related tasks who are yet to be completed will follow suit.

Filtering OutTask

In the portal it is possible to filter OutTasks and create a customized filter by adding a query. Filtering is possible based on:

• PRIORITIES
• STATUSES
• TYPES

Flow

There are different possible OutTask status. The most common are:

• RECEIVED → WIP → DELIVERED (Happy flow)
• RECEIVED → WIP → ON_HOLD → WIP → DELIVERED
• RECEIVED → WIP → TERMINATED
• RECEIVED → TERMINATED
• RECEIVED → TO_BE_CANCELLED → CANCELLED
• RECEIVED → WIP → ON_HOLD → TO_BE_CANCELLED→ CANCELLED

Status Model

The status model used for Order Fulfilment is shown below.