Buyer creates a plan. He should specify himself in buyers list and point at one of the central procurement organizations in procuringEntity field:
As central procurement organization sees itself as procuringEntity of a plan, it can post milestones to this plan:
Only if the access token from the response is provided, the milestone can be changed later:
Note
The fields you can update depend on current milestone status: - dueDate can only be updated at scheduled milestone status - description - either at scheduled or met
Posting documents is also require the milestone access token (as well as changing documents using PATCH/PUT methods):
The central procurement organization creates an aggregated tender in draft status and specifies all the buyer organizations using buyers list of PlanOrganization:
The central procurement organization connects the plan to the tender. If there are many plans, they should be connected one by one.
As a result the plan is moved to "complete" status
The tender plans field contains all the plan ids
For each buyer object in tender system is creating separate contract respectively when award become active.
Create tender with several buyers, each item should be assigned to related buyer using relatedBuyer field :
Move forward as usual, activate award:
After activating award system is creating such amount of contracts that corresponds to the amount of buyers
Update Amount.Value of each contract considering the sum of product of Unit.Value by Quantity for each item in contract.
You can activate or terminate each contract as usual. If there are not contracts in pending status and at least one contract became active tender is becoming complete
If award was cancelled, all contracts related to this awardID become in cancelled status.
Contracts can be cancelled:
Except when contract is the last not cancelled contract:
In that case related award should be cancelled:
Let's check all contracts are cancelled: