When SWO Leads to a 'Conflict'

In the most colloquial verbatim - A conflict is like a cat-fight. Two or more people claiming their right on a common object.

In R2, this happens when two or more orders reserve the same asset. Thus, to resolve this there need to be rules in place which help draw a line in stone, and address who can assert their claim on the named asset.

We are using the term 'Inflicts' to refer that — A SWO became a cause/source/reason for a conflict to get generated.

As briefed in the Conflicts description above, even in the case of SWO, a conflict may arise at Site Level or at Pool Level.

A Site Level Conflict happening means, an item which is being requested by an Order, is already 'In-repair' with an SWO, and the SWO is not done yet or is Overdue (the Due Date is in past). Explained below are the situations in which a SWO may cause a Conflict, and what would be affects of it.

Prerequisite Data:

Create Stock at Site London with San Francisco with 10 quantity.

Workflow Executed:

1. SWO [CO1505794913]  was created on 1st and was expected to be done on 5th.

2. Rental Order [ORD-4683] was scheduled to start on 10th.

3. On 6th the SWO [CO1505794913] goes overdue, and does not get resolved until 11th, by when the Rental Order, has short-fall. Which leads to a conflict. 

Table 1.0: Negative Conflicts impacted by Site scenario