The set of possible configuration values for reporting:
The set of possible configuration values for negotiation:
The set of possible configuration values for negotiation.quick:
You can look for more details in :ref:`config` section.
- You can create three procedures:
reporting
- reporting with no stand-still periodnegotiation
- negotiation procedure with 10 day stand-still before contract registrationnegotiation.quick
- quick negotiation procedure with 5 day stand-still before contract registration
To create tender for reporting procedure you should set reporting
value for procurementMethodType
.
Let’s create a tender:
.. http:example:: http/tutorial/create-tender-procuringEntity.http :code:
We have 201 Created response code, Location header and body with extra id, tenderID, and dateModified properties.
Let's check what tender registry contains:
.. http:example:: http/tutorial/tender-listing-after-procuringEntity.http :code:
We don't see internal id of tender, because tender appears in the listing from active status.
To create tender for negotiation procedure you should set negotiation
value for procurementMethodType
.
.. http:example:: http/tutorial/create-tender-negotiation-procuringEntity.http :code:
To create tender for negotiation.quick procedure you should set negotiation.quick
value for procurementMethodType
.
.. http:example:: http/tutorial/create-tender-negotiation-quick-procuringEntity.http :code:
For activating reporting, negotiation, negotiation.quick procedures you should update status to active
:
.. http:example:: http/tutorial/tender-activating.http :code:
Let's see what listing of tenders reveals us:
.. http:example:: http/tutorial/active-tender-listing-after-procuringEntity.http :code:
We do see the internal id of a tender (that can be used to construct full URL by prepending http://api-sandbox.openprocurement.org/api/0/tenders/) and its dateModified datestamp.
Let's update tender by supplementing it with all other essential properties:
.. http:example:: http/tutorial/patch-items-value-periods.http :code:
We see the added properies have merged with existing tender data. Additionally, the dateModified property was updated to reflect the last modification datestamp.
Checking the listing again reflects the new modification date:
.. http:example:: http/tutorial/tender-listing-after-patch.http :code:
.. index:: Document
Procuring entity can upload documents and files into the created tender. Uploading should follow the :ref:`upload` rules.
.. http:example:: http/tutorial/upload-tender-notice.http :code:
201 Created response code and Location header confirm document creation.
In case we made an error, we can reupload the document over the older version:
.. http:example:: http/tutorial/update-tender-notice.http :code:
Addition of supplier information is the same for all procedures.
Procuring entity registers supplier information for reporting procedure:
.. http:example:: http/tutorial/tender-award.http :code:
Procuring entity registers supplier information for negotiation procedure:
.. http:example:: http/tutorial/tender-negotiation-award.http :code:
You can notice that there is complaintPeriod
record with startDate
value generated.
Procuring entity registers supplier information for negotiation.quick procedure:
.. http:example:: http/tutorial/tender-negotiation-quick-award.http :code:
Award for negotiation.quick procedure also has complaintPeriod
record with startDate
value.
You can upload award documents only before awarding decision is confirmed. Let's add award document:
.. http:example:: http/tutorial/tender-award-upload-document.http :code:
201 Created response code and Location header confirm that document has been added.
Let's see the list of award documents:
.. http:example:: http/tutorial/tender-award-get-documents.http :code:
We can add another award document:
.. http:example:: http/tutorial/tender-award-upload-second-document.http :code:
201 Created response code and Location header confirm second document has been added.
Let's see the list of all uploaded award documents:
.. http:example:: http/tutorial/tender-award-get-documents-again.http :code:
Procuring entity can confirm awarding decision:
.. http:example:: http/tutorial/tender-award-approve.http :code:
Award confirmation for negotiation procedure:
.. http:example:: http/tutorial/tender-negotiation-award-approve.http :code:
The difference between startDate
and endDate
in complaintPeriod
record for negotiation is 10 days.
Award confirmation for negotiation.quick procedure:
.. http:example:: http/tutorial/tender-negotiation-quick-award-approve.http :code:
The difference between startDate
and endDate
in complaintPeriod
record for negotiation.quick is 5 days.
.. index:: Setting Contract
All operations with contract moved to :ref:`econtracting`
Reporting tender contract can be registered immediately after award confirmation:
.. http:example:: http/tutorial/tender-contract-sign.http :code:
Negotiation tender contract can be registered only after the stand-still (10 day period after the award confirmation):
.. http:example:: http/tutorial/tender-negotiation-contract-sign.http :code:
Negotiation.quick tender contract can be registered after the stand-still (5 day period after the award confirmation):
.. http:example:: http/tutorial/tender-negotiation-quick-contract-sign.http :code:
Tender creator can cancel tender anytime (except when tender in status active.auction or in terminal status e.g. unsuccessful, canceled, complete).
The following steps should be applied:
- Prepare cancellation request
- Fill it with the protocol describing the cancellation reasons
- Passing complaint period(10 days),only for negotiation and negotiation.quick
- Cancel the tender with the reasons prepared.
Only the request that has been activated (4th step above) has power to cancel tender. I.e. you have to not only prepare cancellation request but to activate it as well.
For cancelled cancellation you need to update cancellation status to unsuccessful from draft or pending.
See :ref:`cancellation` data structure for details.
You should pass reason and reasonType, status defaults to draft.
There are four possible types of cancellation reason - tender was noDemand, unFixable, forceMajeure and expensesCut.
id is autogenerated and passed in the Location header of response.
.. http:example:: http/tutorial/prepare-cancellation.http :code:
You can change reasonType
value to any of the above.
.. http:example:: http/tutorial/update-cancellation-reasonType.http :code:
There are five possible types of cancellation reason - tender was noObjectiveness, unFixable, noDemand, expensesCut, dateViolation.
.. http:example:: http/tutorial/negotiation-prepare-cancellation.http :code:
You can change reasonType
value to any of the above.
.. http:example:: http/tutorial/negotiation-update-cancellation-reasonType.http :code:
This step is required. Without documents you can't update tender status.
Upload the file contents
.. http:example:: http/tutorial/upload-cancellation-doc.http :code:
Change the document description and other properties
.. http:example:: http/tutorial/patch-cancellation.http :code:
Upload new version of the document
.. http:example:: http/tutorial/update-cancellation-doc.http :code:
For activate complaint period, you need to update cancellation from draft to pending.
.. http:example:: http/tutorial/pending-cancellation.http :code:
When cancellation in pending status the tender owner is prohibited from all actions on the tender.
if the complaint period(duration 10 days) is over and there were no complaints or all complaints are canceled, then cancellation will automatically update status to active.