Let’s go!

Budgets, Funding and Plans

Endpoint

GET /get/budgets

01. Expenditure Items (EIs)

‘Expenditure Item’ is a model describing a group of goods, services or works that CA plans to procure over a certain period, as well as the amount allocated by the CA to finance the purchases of the subject of this group during the specified period.

01.1. Retrieving a list of existing EIs

Retrieving process follows according to general data retrieving mechanism

Retrieving conducted EIs and related information

All operations of reading and displaying of content of conducted ‘Expenditure Items’ are based on EI transport-model. Use of this structure allows to read hi-level data for each conducted EI as well as lists of related data (such us FSs, PNs, PINs, CNs, ACs).

Example

Let’s try exploring the /budgets endpoint:

GET /get/budgets?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{
"offset": ""
"data": [
{
"ocid":"ocds-t1s2t3-UA-1513094593", // ocid of founded EI-Entity
"date":"2018-06-23T00:00:00Z" // date of newest release in founded record
}
]
}

Let’s access the URL of one of retrieved EI-entities:

GET /get/budgets/ocds-001-00000-ei?offset=2018-06-23T00:00:00Z HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on EI transport model

EI with hi-level details and list of related FSs The ‘EI’ transport-model allows to display an item of expenditure with detailed information about the object of procurement, future consumer, planned budget and other information, as well as a list of related processes
List of related FSs Use of ‘EI’ data-model allows to display a list of related to particular EI sources of funding. Links to such related FSs described in a ‘relatedProcesses’ array as items with relationship-code 'x_FinanceSource'.
List of related Tenders Use of ‘EI’ data-model allows to display a list of ‘PNs’, ‘PINs’, ‘CNs’ related to this ‘EI’. Links to such related Tenders described in a ‘relatedProcesses’ array as items with relationship-code 'x_execution'.
List of related Contracts Use of ‘EI’ data-model allows to display a list of ‘ACs’ related to this EI. Links to such related FSs described in a ‘relatedProcesses’ array as items with relationship-code 'x_contract'.

The same could be used to retrieve a list of e.g. ‘Tenders’ or details of such entities

01.2. Create EI

To create new entity of EI standard Command Model should be used for preparation of POST-request.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=ei&country=...&identifierSchema=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operations.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request

POST /do/ei?country=MD HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
Content-Type: application/json
Host: bpe.eprocurement.systems

{} //data set according to EI command model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Request for full Result

Public Point will respond with Record Package of just created EI according to the Transport Model

GET /get/budgets/ocds-000-00001-ei?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on EI transport-model

01.3. Update EI

To update existing entity of EI existing rules for update of EI must be considered for preparation of request.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-ei&oсid=ocds-000-00001-ei&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operations.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request with updates

POST /do/ei/ocds-000-00001-ei HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: 2ef61fa89e8a451ba4149d2f8e31173b
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set according to EI command model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Request for result

Public Point will respond with Record Package of just created EI according to the Transport Model:

GET /get/budgets/ocds-000-00001-ei/?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on EI transport-model

01.4. Retrieving a list of available budget lines (IBANs) for EI

In case if CA or his separate specific need is funded via Treasury, for each identified need (Expenditure Item) a list of available budget lines (IBANs) can be received. To receive a list, parametrized GET-request must be sent to the BPE.

GET /budget/iban?idno=...&cpv=...-5&year=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: mconnect.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{
"getIbanList_response": {
"iban": [
"MD10TRPCBW518430A00362AA",
"MD05AGPEAT518430A00362AA",
"MD05AGPGAB518430A00362AA",
"MD62TRPCBW518430B00362AA"
]
}
}

02. Funding Source (FS)

‘Funding Source’ is a model describing a specific source of funding for procurement of goods, services or works from the parent Expenditure Item. Description contains information on both the amount and the organization that provides the funds, as well as other organizations involved in the disposal of this particular budget: payer, donor.

02.1. Retrieving a list of existing FS

Retrieving process follows according to general data retrieving mechanism beginning from step 2: “Getting individual entity information” because there is no need to keep or work with FS without parent EI

Retrieving conducted FSs and detailed information

All operations of reading and displaying of content of used ‘Funding Sources’ are based on FS data-model.

Example

Let’s access the URL of specific FS-entity:

GET /get/budgets/ocds-000-00001-ei/ocds-000-00001-fs?offset=... HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on FS query model

Details of selected related FS

Use of ‘FS’ query-model allows to display details of particular chosen ‘FS’ conducted for ‘Expenditure Item’ (Tender, Contract) with all information about params describing such ‘FS’.

To do that, defined link to needed FS should be used to retrieve all details as Release Package.

The same mechanisms could be used to retrieve a list of ‘FSs’ of ‘Tender’ or ‘Contract’ or details of any of such ‘FSs’

02.2. Create FS

To create new entity of FS standard Command Model should be used for preparation of POST-request.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=fs&ocid=ocds-000-00001-ei&funder=...&payer=...&lang=...&isEuropeanUnionFunded=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operations.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request

POST /do/fs/ocds-000-00001-ei HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
Content-Type: application/json
Host: bpe.eprocurement.systems

{} //data set according to FS command model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

{
"initiator": "platform",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001-fs",
"url": "http://public.eprocurement.systems/budgets/ocds-000-00001-ei/ocds-000-00001-fs",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"fs": [
{
"id": "ocds-t1s2t3-TEST-FS",
"X-TOKEN": "2ef61fa89e8a451ba4149d2f8e31173b"
}
]
}
}
}

Request for Result

Public Point will respond with Release Package of just created FS according to the Query Model:

GET /get/budgets/ocds-000-00001-ei/ocds-000-00001-fs?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on FS query model

02.3. Update FS

To update existing entity of FS existing rules for update of FS must be considered for preparation of request.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-fs&ocid=ocds-000-00001-fs&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request

POST /do/fs/ocds-000-00001-ei/ocds-000-00001-fs HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: 2ef61fa89e8a451ba4149d2f8e31173b
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on FS command model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Request full result

Public Point will respond with Release Package of newly updated FS according to the Query Model:

GET /get/budgets/ocds-000-00001-ei/ocds-000-00001-fs?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on FS query model

02.4. Retrieving an amount of available value for specific IBAN

To be provided

GET /budget/get?iban=...&year=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: mconnect.mtender.gov.md

200 OK
Content-Type: application/json; charset=UTF-8

{

"sum":"90000.00" // the amount of available funds

}

02.5. Validation of amount for specific IBAN

To be provided

GET /budget/check?iban=...&year=...&sum=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: http://mconnect.mtender.gov.md

200 OK
Content-Type: application/json; charset=UTF-8

{

"result":"1" // 0 - if false

}

Scheduled or announced Tenders: PN, PIN, CN

‘CN’ is a model describing a specific contract process - the procurement procedure announced by the CA. Depending on the type of procedure, method of procurement, geography and the legal basis, the attribute composition of the model can be adjusted, but its general logic remains unchanged for all types of procedures.

Endpoint

GET /get/tenders

03.1. Retrieving scheduled or announced CNs and related information

All operations of reading and displaying of content of conducted ‘Expenditure Items’ are based on CN transport-model. Use of these structures allows to read hi-level data for each conducted EI as well as lists of related data (such us FSs, PNs, PINs, CNs, ACs).

Example

Let’s try exploring the /tenders endpoint:

GET /get/tenders?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{
"offset": ""
"data": [
{
"ocid":"ocds-000-00001", // ocid of founded entity
"date":"2018-06-23T00:00:00Z" // date of newest release in founded record
}
]
}

Let’s access the URL of one of retrieved EI-entity:

GET /get/tenders/ocds-000-00001?offset=2018-06-23T00:00:00Z HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on CN transport model

Preparing a notice

To launch a tender CA prepares a notice: determines key fields of the yet-to-be announced procurement, uploads tender documentation with the requirements to the subject indicated as that which determines winner evaluation criteria. Depending on CA’s procurement strategy such a Notice (CN) may include data in three different consistencies:

Planning Notice (planningNotice) - using this kind of notice means that CA has an intention to conduct a tender in some date during procurement year
Prior Information Notice (priorNotice) - using this kind of notice means that CA has an intention to conduct a tender in particular date (date, month or quarter) of procurement year
Contract Notice (contractNotice) - using this kind of notice means that CA has an intention to conduct a tender and start to collect bids right after publication date

Planning Notice

Planning notice is an announcement of intention to conduct a tender. On this stage just hi-level params of future procedure should be indicated including estimated period of start (month or quarter). Specification of subject of procurement, detailed eligibility, award and non-price criteria etc could be announced within Prior Information Notice or Contract Notice.

03.2. Create PN

To create new entity of PN standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=pn&ocid=...&procuringEntity=...&responsibleContactPerson=...&pmd=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Procuring entity can register files for the future CN before such CN is created. Document registration is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

{
"success": true,
"data": {
"id": "4c4f5a50-89cd-11e8-b758-dd76462396b0",
"url": "http://storage.eprocurement.systems/get/4c4f5a50-89cd-11e8",
"dateModified": "2018-07-17T14:25:47Z",
"datePublished": null
}
}

Send Request

POST /do/pn?country=...&pmd=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on СN command-model

202 Accepted
Content-Type: application/json; charset=UTF-8

Evaluation panel provisional declaration

Within PN command model a set of Procuring Entity evaluation panel could be announced on the PN level. For this array of Persone to be included into Organization block of a role:procuringEntity of the request as follows:

{

...

"procuringEntity":{

"id":"",

"persones":[

{

"title":"",

"name":"",

"identifier":{},

"businessFunctions":[

{

"id":"",

"type":"authority",

"jobTitle":"",

"period":{},

"documents":[]

}

]

}

...

}

Note that in case of ‘persones’ array is applied, at least one element with a businessFunction.type: authority shall be included

In the future steps this information will be used for the establishment of the automated evaluation flow.

Feed Point Response

{
"initiator": "platform",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-pn",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"pn": [
{
"id": "ocds-t1s2t3-TEST-PN",
"X-TOKEN": "c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4"
}
]
}
}
}

Uploading Documentation

Procuring entity can upload files for the future CN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /upload/389684cc28c242b79c97c56be5142e25 HTTP/1.0
Authorization:
Content-Length: 58
Content-Type: multipart/form-data; boundary=----------a_BoUnDaRy572732436472$
Host: storage.eprocurement.systems

------------a_BoUnDaRy572732436472$
content
------------a_BoUnDaRy572732436472$--

201 Created
Content-Type: application/json; charset=UTF-8

{
"data": {
"url": ".../get/389684cc28c242b79c97c56be5142e25"
}
}

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-pn?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on PN query-model

03.3. Update PN

To update an existing entity of PN standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-pn&ocid=ocds-000-00001-pn&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Procuring entity can register files for the future updated CN before such CN is updated. Document registration is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/pn/ocds-000-00001/ocds-000-00001-pn HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: 2ef61fa89e8a451ba4149d2f8e31173b
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on CN command-model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Procuring entity can upload files for the updated CN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

{
"data": {
"url": ".../get/389684cc28c242b79c97c56be5142e25"
}
}

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-pn?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on PN query-model

Prior Information Notice (PIN)

Prior Information Notice - using this kind of notice means that CA has an intention to conduct a tender in particular date of procurement year. As mentioned above, PIN may be created in one of two ways (depending on CAs procurement strategy):

Prior Information Notice as such - PIN from scratch
Prior Information Notice based on Planning Notice - PIN on PN

These approaches executed in a different way from BPE perspective

03.4. Create PIN

To create new entity of PN standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=pin&ei-ocid=...&procuringEntity=...&responsibleContactPerson=...&pmd=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/pin?country=...&pmd=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: 1a6350b26a094a39adf455ee9a495f6c
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on CN command-model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

{
"initiator": "platform",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-pin",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"pin": [
{
"id": "ocds-t1s2t3-TEST-PN",
"X-TOKEN": "c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4"
}
]
}
}
}

Uploading Documentation

Procuring entity can upload files for the future CN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

{
"data": {
"url": ".../get/389684cc28c242b79c97c56be5142e25"
}
}

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-pin?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on CN query-model

03.5. PIN on PN

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

Send Request

Feed Point Response

Request full result

03.6. Update PIN

To update an existing entity of PIN standard Command Model should be used.

Get X-OPERATION-ID

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-pin&ocid=ocds-000-00001-pin&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/pin/ocds-000-00001/ocds-000-00001-pin HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: 2ef61fa89e8a451ba4149d2f8e31173b
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on CN command-model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Procuring entity can upload files for the updated CN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

{
"data": {
"url": ".../get/389684cc28c242b79c97c56be5142e25"
}
}

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-pin?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on CN query-model

Contract Notice (CN)

Contract Notice - using this kind of notice means that CA has an intention to conduct a tender and start to collect bids right after publication date. As mentioned above, CN may be created in one of three ways (depending on CAs procurement strategy):

Contract Notice as such - from scratch
Contract Notice based on Prior Information Notice - CN on PIN
Contract Notice based on Planning Notice - CN on PN

These approaches executed in a different way from BPEs’ perspective.

03.7. Create CN

To create new entity of CN standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=cn&ocid=...&procuringEntity=...&responsibleContactPerson=...&pmd=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/cn?country=...&pmd=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on CN command-model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Procuring entity can upload files for the future CN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

{
"data": {
"url": ".../get/389684cc28c242b79c97c56be5142e25"
}
}

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-cn?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on CN query-model

03.8. CN on PIN

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

Send Request

Feed Point Response

Request full result

03.9. CN on PN

To update an existing entity of PN to CN, standard Command Model should be used for preparation request

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-cn&ocid=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/cn/ocds-000-00001/ocds-000-00001-pn HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb

X-TOKEN: 2ef61fa89e8a451ba4149d2f8e31173b
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on СN command-model

202 Accepted
Content-Type: application/json; charset=UTF-8

Within CNonPN command a number of information needed for future automated evaluation can be expressed:

Evaluation panel declaration

A set of Procuring Entity evaluation panel could be announced or updated (if some changes or replacements took place since PN for this contracting process was published). For this array of Persone to be included into the Organization block of a role:procuringEntity of the request in the same way as it is in a ‘Create PN’ request In the future steps this information will be used for the establishment of the automated evaluation flow.

Criteria

Set of criteria may include different types of requirements, used in different ways and for different reasons.

Read more about criteria in a Contract Notice

Conversions

Where scoring function to be applied, a set of verifiable conversions needed for future ranking and evaluation.

Read more about conversions for scoring function

Scoring function

Where criteria for future evaluation of the bids received and the relevant conversions are applied, PE shall also indicate its intention to apply a scoring function. To do that an ‘awardCriteriaDetails’ attribute to be set as ‘automated’ in a request for BPE.

Read more about how scoring function works

Feed Point Response

{
"id": "ocds-000-00001-cn"
}
]
}
}
}

Uploading Documentation

Procuring entity can upload files for the future CN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

{
"data": {
"url": ".../get/389684cc28c242b79c97c56be5142e25"
}
}

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-cn?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on CN query-model

03.10. Update CN

Once Contract Notice is published, there only non-significant changes and amendments are available. To update an existing entity of CN standard Command Model should be used for preparation request.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-cn&ocid=ocds-000-00001-cn&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/cn/ocds-000-00001/ocds-000-00001-cn HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: 2ef61fa89e8a451ba4149d2f8e31173b
Content-Type: application/json
Host: bpe.eprocurement.systems

{} // data set based on CN command-model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Procuring entity can upload files for the updated CN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

{
"data": {
"url": ".../get/389684cc28c242b79c97c56be5142e25"
}
}

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-cn?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on CN transport model

Clarification

Clarification period (enquiryPeriod) is separately distinguished in the procurement procedure during which any user can ask questions regarding the procurement requirements, demand issue resolution, and submit a complaint, while CA can provide answers to questions and introduce changes into the procurement conditions.

04.1. Submit a Questions

To create new Enquiry standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=enquiry&lot-id...&&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 Ok
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request

POST /do/enquiry/ocds-000-00001/ocds-000-00001-cn HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
Content-Type: application/json
Host: bpe.eprocurement.systems

{} //data set according to Enquiry command model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Since ‘enquiry’ object requests a response from Procuring Entity who might be registered and use another NEPP, feed-point will generate 2 messages: one for NEPP whose user submitted the enquiry (EO topic) and another one - for NEPP whose user is owner of this Contracting Process (CA topic)

Message for CA topic

{
"initiator": "bpe",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001-cn",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"enquiries": [
{
"id": "ocds-000-00001-cn-enquiry-1",
"X-TOKEN": "c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4",
}
]
}
}
}

Message for CA topic

Request full result

GET /get/tenders/ocds-000-00001/ocds-000-00001-cn?offset= HTTP/1.1
Host: public.eprocurement.systems

200 OK
Content-Type: application/json; charset=UTF-8

{} // data set based on CN query-model including ENQUIRY-extension

04.2. Post an answer

To put an answer to Enquiry standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=answer&enquiry-id=...&lang=... HTTP/1.1
Authorization: Basic QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 Ok
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request

POST /do/enquiry/ocds-000-00001-cn/ocds-000-00001-cn/ocds-000-00001-enquiry-1 HTTP/1.1
Authorization: Basic QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: 2645b26a094a39adf455ee9a495f6c
Content-Type: application/json
Host: bpe.eprocurement.systems

{} //data set according to Answer command model

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

{
"initiator": "platform",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",

"data": {
"ocid": "ocds-000-00001-cn",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "2018-08-14T13:51:06Z",
}
}

Request full result

04.3. Suspension of procedure

Any accepted enquiries which have no relevant clarification provided by CA before ‘enquiryPeriod.endDate’ suspend the start of next phase of contracting process - submission period. Such suspending implemented by setting tender.statusDetails:suspended for current active stage (EV)

{
"tender": {

"statusDetails": "suspended"

}

04.4. Unsuspending of the procedure

After the publication of the CAs’ clarifications for each registered enquiry, procedure is unsuspended automatically with prolongation of ‘enquiryPeriod’ according to the rules, prescribed by Law.

Submission

During tenderPeriod interested parties can submit and update submitted bids.

05.1. Submit bid

To submit a new bid to CN standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=bid&ocid=...&lot-id=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Tenderer can register files for the future BID before such BID is created. Document registration is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/bid/ocds-000-00001/ocds-000-00001-cn HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Requirement Responses

For each requirement expressed by Procuring Entity within ‘criteria’ for the bidders (all the criteria where criterion.source is not specified) each bid shall include a relevant requirement response, expressing a value proposed within this bid against specific requirement.

Feed Point Response

{
"initiator": "platform",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001-cn",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"bids": [
{
"id": "ocds-000-00001-cn-bid-1",
"X-TOKEN": "c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4",
}
]
}
}
}

Uploading Documentation

Tenderer can upload files for the newly created BID. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Note that: there will be no updated information in a public point after submission of a bid since all the bids remain confidential until deadline for submission (tender.tenderPeriod.endDate)

05.2. Update bid

To update an existing BID standard Command Model should be used.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-bid&ocid=...&lot-id=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Tenderer can register files for the future updated BID before such BID is updated. Document registration is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Send Request

POST /do/bid/ocds-000-00001/ocds-000-00001-cn/ocds-000-00001-bid-1 HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: 98798f26a094a39adf455ee9a495f6c
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Tenderer can upload files for the newly updated BID. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

05.2. Withdraw bid

To be provided

Electronic Auction

Date of the auction is determined by the BPE automatically, once the CN is published. NEPPs have to inform their users about the upcoming auction start date. If no participant is registered before tenderPeriod.endDate, the system automatically changes the process status for separate lot to unsuccessful.

Scheduling of the auction

Public link to the auction will be published for each lot.status.active once tenderPeriod.endDate achieved and contracting process switched to statusDetails:auction

{
"tender": {
"electronicAuctions": {
"details": [
{
"electronicAuctionModalities": [
{
"url": ""
}
]
}
]
}
}
}

Access-links for tenderers

If more than one bid is registered for a separate lot, the system activates the e-Auction module. Those participants who registered their offers can participate in the auction. All the other users, including the CA, can observe how the auction develops. The set of unique private links for each registered bid.status:pending will be transferred via feed-point to NEPPs who operating bid-owner (tenderer)

{
"X-OPERATION-ID": "95945400-d5d0-11e8-b646-791d6894bd79",
"X-RESPONSE-ID": "50c50350-d5d1-11e8-b646-791d6894bd79",
"initiator": "bpe",
"data": {
"ocid": "ocds-000-00001-cn",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "2018-10-22T08:06:00Z",
"outcomes": {
"awards": [
{ "id": "509f04c0-d5d1-11e8-85b1-337a681d86a2" }
],
"links": [
{
"relatedBid": "a80b61e0-c348-11e8-b9a8-dd319bd9bbdf",
"url": "http://eauction.eprocurement.systems/ocds-000-00001/lot-id?bid_id=...&sign=..."
}
]
}
}
}

Note that:

Auctions are held for each lot separately
Information disclosure on participants occurs once the last auction is completed

Evaluation of the offers received

Once the submission period (tenderPeriod) is over and participants can no longer submit or update their bids or or electronic auction is over, the system will initiate an evaluation phase of this contracting process.

Disclosure of the offers

System will disclose all submitted bids and execute following actions:

06.1. Generation of negative Contract Award Notices

System will automatically generate and add to initial query-model of the stage set of Contract Award Notices (CANs) for all lots where:

no offers were received during tender period
CAs decision on lot cancellation was received during valid period

CANs will be published in a terminal state (status:unsuccessful)

{
"initiator": "BPE",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001-cn",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"cans": [
{
"id": "ocds-000-00001-can-1", // CAN for lot with no offers received
"status": "unsuccessful",
"statusDetails": "noOffersReceived",

"relatedLot": "1"
},

{
"id": "ocds-000-00001-can-2", // CAN for previously cancelled lot
"status": "unsuccessful",
"statusDetails": "lotCancelled",

"relatedLot": "2"
}
]
}
}
}

In case if after submission period end there is nothing to disclose (no bids were submitted) or all submitted bids failed, the system will automatically change this specific lot of this contracting process to status “unsuccessful”.

06.2. Preparation for the evaluation by Procuring Entity

For all the disclosed bids system will automatically generate a set of qualification envelopes (awards) and launch the awarding period (tender.awardPeriod) for this contracting process.

Automated eligibility check

Where it is applicable, the system will automatically verify eligibility based on actual official data available via external bus (Mconnect) for each tenderer whose bid was disclosed according to rules of dispatch under the current procurement method. Those bids that passed eligibility check, will go to the technical qualification by Procuring Entity. All the others that failed - go to automatic exclusion.

Automated ranking based on award criteria

Depending on the award criteria and the method of the initial evaluation applied by PE (awardCriteriaDetails) system will rank eligible bids and suggest them in order of admissibility: from most to least acceptable by applicable criteria.

Read more about initial automated ranking for evaluation by the system

As it's shown in the table below, automated ranking can be undertaken using a set of criteria and the relevant conversions applied by PE for each available value of each applied requirement and published in a Contract Notice on one hand and the requirement responses submitted by each EO against published criteria on another hand. These two data-sets allow to calculate normalized value for each bid based on the same approach.

awardCriteria

awardCriteriaDetails

priceOnly

costOnly

qualityOnly

ratedCriteria

automated

ranking based

on absolute value of the amount of price offer

ranking based

on absolute value of the amount of price offer considering set of values for quantifiable criteria by Procuring Entity (non-price criteria)

ranking based on

values for quantifiable and qualifiable criteria by Procuring Entity (technical requirements, non-price criteria, criteria on a subject specification)

ranking based on absolute value of the amount of price considering set of values for quantifiable and qualifiable criteria by Procuring Entity (technical requirements, non-price criteria, criteria on a subject specification)

manual

no ranking

Award of most acceptable offer will be marked with statusDetails:awaiting.

06.3. Publication of qualification envelopes (awards)

‘Awards‘ section will be added to the initial query-model of the stage and will include all awards that were generated for all disclosed ‘bids’. Initial status of awards will be ‘pending’.

{
"awards": [

{

"id": "ocds-000-00001-award-1", // automatically excluded bid
"status": "unsuccessful",

"statusDetails": "excluded"
},

{

"id": "ocds-000-00001-award-2", // most acceptable eligible bid
"status": "pending",

"statusDetails": "awaiting"
},

{

"id": "ocds-000-00001-award-3", // acceptable bid in the line for review
"status": "pending"
}

]
}

06.4. Award for manual evaluation in offline procedure

‘Awards‘ section will be added to initial query-model of the stage and will include all awards that were introduced by the CA. Initial status of awards will be ‘pending’.

{
"awards": [

{

"id": "ocds-000-00001-award-2",
"status": "pending",

"statusDetails": "empty"
}

]
}

Evaluation by Procuring Entity

Once set of awards for manual qualification and evaluation established, feed point will inform operating NEPP with a list of such awards and its tokens. NEPP shall notify its user (CA) and share received master-data (tokens) with him to be able to operate and provide manual qualification and evaluation.

Feed Point notification about ‘awards’ generated

{
"initiator": "BPE",
"X-OPERATION-ID": "gbrt56yu-5ff8-463f-fdgr-rghnh56yh45",
"data": {
"ocid": "ocds-t1s2t3-TEST-1528370112857",
"url": "public.eprocurement.systems/get/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "",
"outcomes": [
{
"id": "ocds-000-00001-award-1",
"X-TOKEN": "c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4"
},
{
"id": "ocds-000-00001-award-2",
"X-TOKEN": "vbgtr5497-ac2d-4e25-bd7f-cd55dg456dhf"
},
{
"id": "ocds-000-00001-award-3",
"X-TOKEN": "1234d497-ac2d-4e25-bd7f-cd55111aa7b4"
}
]
}
}

CA shall sequentially review the bids that are eligible considering its compliance to eligibility criteria automatically checked by the system (if applicable), starting with first ranked by the system (award.statusDetails:awaiting).

07.1. Declaration of non conflict of interests by evaluation panel

Due to requirements of declaration of non conflict of interest by evaluation panel members against each tenderer for each bid to be evaluated, the system will generate relevant requests for each member declared by PE within CN. These requests are elements of the ‘criteria’ array related to procuringEntity (criterion.source:procuringEntity)

{
"tender": {
"criteria": [
{
"id": "nonConflictOfInterest",
"source":"procuringEntity",
"requirementGroups": [
{
"id": "nonConflictOfInterest-1",
"requirements": [
{
"id": "nonConflictOfInterest-1-1",
"description": "Text of the declaration",
"dataType": "boolean"
},
{
"id": "nonConflictOfInterest-1-2",
"description": "Text of the confirmation of confidentiality",
"dataType": "boolean"
}
]
}
]
}
]
}
}

Each initial or new (in case of replacement) member of the evaluation panel shall submit relevant responses in order to confirm an absence of conflict of interest for each tenderer (legal entity) in bid received for evaluation by panel and currently associated with an ‘award.statusDetails: awaiting’.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=declaration&lot-id=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request

A standard command model of declaration of non conflict of interest to be used for the preparation of a request for BPE (for each evaluation panel member against each tenderer from the award.tenderers[])

POST /do/declaration/ocds-000-00001/ocds-000-00001-cn/ocds-000-00001-award-2?tendererId=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Once all the evaluation panel members declared a non conflict of interest against each tenderer from the ranked bid, such bid can be switched to the following step of evaluation. For this a related ‘award’ to be switched into the following state - consideration.

07.2. Switch to consideration

The ‘award’ associated with an offer (bid) covered by a declarations of non conflict of interest by evaluation panel shall be switched into following specific state which allows PE to evaluate it - ‘award.statusDetails: consideration’:

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Send Request

POST /do/consideration/ocds-000-00001/ocds-000-00001-cn/ocds-000-00001-award-2 HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

As a result of the request targeted ‘award’ will be switched into ‘statusDetails:consideration’ and all the related documents (captured with a document type prescribed by the ESPD model) will be disclosed for the PE review.

{
"initiator": "platform",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001-cn",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"awards": [
{
"id": "ocds-000-00001-award-2",
"status": "pending",
"statusDetails": "consideration",

"documents": []
}
]
}
}
}

Such ‘award’ now can be reviewed by an evaluation panel.

07.3. Eligibility check and qualification

Depending on the award criteria applied and availability of the scoring function, the system will disclose either eligibility documents only for all bids where related award is not in statusDetails:consideration and full package of documents submitted by EOs within bid for award.statusDetails: consideration or full package of submitted documents for all the offers submitted for manual review by Procuring Entity.

Where automated eligibility check is not applicable, Procuring Entity shall provide an eligibility check manually during evaluation. The financial part of bids of those candidates who passed eligibility check will go to the technical evaluation. All the others who failed eligibility check are excluded from evaluation.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-award&lot-id=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Procuring Entity can register files for the future updated award before such award is updated. Document registration is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

{
"success": true,
"data": {
"id": "4c4f5a50-89cd-11e8-b758-dd76462396b0",
"url": "http://storage.eprocurement.systems/get/4c4f5a50-89cd-11e8",
"dateModified": "2018-07-17T14:25:47Z"

}
}

Send Request

If the most acceptable bid is in compliance with the eligibility criteria and CAs’ requirements (both technical and financial), CA determines this offer as a qualified by sending ‘award.statusDetails:active’. If it is not, CA confirms his decision to disqualify the participant by sending award:statusDetails:unsuccessful, and declines such an offer.

POST /do/award/ocds-000-00001/ocds-000-00001-cn/ocds-000-00001-award-2 HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{
"award":{
"description": "",

"statusDetails": "active",

"documents": []
}
}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Tenderer can upload files for the newly updated award. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Before selection step is confirmed as ended CA is able to change his decisions regarding most acceptable offer as many time as needed

If the most acceptable offer was rejected by CA the system suggests to qualify the next offer from the acceptance perspective. If all the offers for specific lot were declined by CA, this specific lot of this contracting process automatically changes its statusDetails to ‘unsuccessful’ and, upon the completion of the complaining process - to status ‘unsuccessful’.

06.2. Submission of evaluation protocol (completion of evaluation in lot)

Once a winner is selected or all existing offers rejected for a specific lot, CA submits the evaluation protocol which, in its turn, indicates the publication of decision. Such evaluation protocol has to be submitted for each evaluated lot separately.

Get X-OPERATION-ID

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
}

Send Request

POST /do/protocol/ocds-000-00001/ocds-000-00001-cn/lotID HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

As a result of the decision under each separate lot (submission of evaluation protocol) Contract Award Notice associated with particular lot will be automatically generated and published as an object inside "contracts" section. Depending on the decision of CA, different values of statusDetails attribute will be set for generated CANs:

for CAN under lot where supplier was determined - statusDetails:active
for CAN under lot where supplier was not selected (al bids were rejected) - statusDetails:unsuccessful

{
"initiator": "platform",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001-cn",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-cn",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"contracts": [
{
"id": "ocds-000-00001-can-3", // CAN for lot with selected supplier
"status": "pending",
"statusDetails": "active"
},
{
"id": "ocds-000-00001-can-4", // CAN for lot with all offers rejected
"status": "pending",
"statusDetails": "unsuccessful"
}
]
}
}
}

Future steps

06.3. Review period

Review period is a time-slot during which the decision of the procuring entity to award a contract can be challenged. All tenderers whose offers were reviewed by PE are able to claim on such made decisions. This review period is the same for all tenderers.

{
"contracts": [

{

"reviewPeriod":{
"startDate":"",
"endDate":""
}
}

]
}

If any complaints were received and accepted for review during the review period, the system automatically establishes standstill period for each received complaint separately.

Complaint submission

Complaints on made decisions received during the review period and accepted for review transfer to the official Review body. After the Complaint submission, a representative of the Review Body checks whether all requirements are fulfilled and carried out. If so, a complaint is accepted for review. Otherwise, it is rejected.

Suspending of procedure

Such accepted complaints block the opportunity to run a contracting step (publish a contract with the winner) and suspend all evaluation stage via establishing a special time-slot: system automatically establishes standstill period for each complaint received and accepted for review.

Standstill period

The duration of the applicable standstill period following a challenge or complaint of decisions or actions taken by the Procuring Entity that are allegedly not in compliance with the provisions of the Law.

Reviewing

To indicate the results of review of accepted complaint, representative of Review Body shall specify the results via changing of status of reviewed complaint together with contribution of additional needed information.

If the complaint was dismissed by Review body, standstill period of such complaint ends
If the complaint was satisfied by the Review body, the Procuring entity carries out the decision under its own responsibility, there are no additional automatic control means. Carried out decision marked with ‘satisfied’ state by CA himself indicates that prescribed judgments of Review Body are satisfied and complaint is complete.

Resumption of procedure

After the publication of the Review body’s decision with the status “dismissed” procedure is unsuspended automatically. Satisfied complaints should be changed by CA to ‘complete”.

06.4. Update of the bid selected as winning offer

Once the Procuring Entity has selected a particular bid as a winning (relevant award:statusDetails:active is set for the related award) and before the Awarded Contract is issued, Economic Operator is able to update his previously submitted bid with any required documents, requested by Procuring Entity or prescribed by the Law.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST POST ?form=update-bid&ocid=...&lot-id=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Procuring entity can register files for the future updated award before such award is updated. Document registration is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

{
"success": true,
"data": {
"id": "4c4f5a50-89cd-11e8-b758-dd76462396b0",
"url": "http://storage.eprocurement.systems/get/4c4f5a50-89cd-11e8",
"dateModified": "2018-07-17T14:25:47Z"

}
}

Send Request

POST /do/document/bid/ocds-000-00001/ocds-000-00001-cn/ocds-000-0001-bid-1 HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Tenderer can upload files for the newly updated BID. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added.

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

06.5. Update prepared CAN with document

Once CAN is published and before CAN is confirmed Procuring Entity able to update such CAN with any additionally required or prescribed documents (e.g. report on procedure or signed decision of evaluation panel):

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST POST ?form=update-can&ocid=...&lot-id=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

{
"success": true,
"data": {
"id": "4c4f5a50-89cd-11e8-b758-dd76462396b0",
"url": "http://storage.eprocurement.systems/get/4c4f5a50-89cd-11e8",
"dateModified": "2018-07-17T14:25:47Z"

}
}

Send Request

POST /do/document/can/ocds-000-00001/ocds-000-00001-cn/ocds-000-0001-can-1 HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

CA can upload files for the newly updated CAN. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Future steps

06.6. Signing of the decision made by TC

To be provided

06.7. CAN confirmation

CANs with statusDetails:active (positive) or statusDetails:unsuccessful (negative) has to be confirmed by the Procuring Entity once review period for these decisions expired. Such confirmation executes in a different way for different cases:

Confirmation of positive CAN

Once the review period expires for specific CAN and there are no complaints received or satisfied, positive CAN can be confirmed by Procuring Entity with initiation of generation of draft for awarded contract.

Confirmation of negative CAN

Confirmation of negative CAN requires additional action. Such action can be executed within submitting of separate request to BPE:

Get X-OPERATION-ID

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",

"schema": {},
"data": {}
}

Send Request

POST /do/confirmation/can/ocds-000-00001/ocds-000-00001-cn/ocds-000-00001-can-4/ HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

202 Accepted
Content-Type: application/json; charset=UTF-8

As a result of confirmation of negative CAN, this CAN will be switched by the system automatically to the terminal state with an indication of details of negative outcome through statusDetails attribute:

{
"contracts": [
{
"id": "ocds-000-00001-can-4",
"status": "unsuccessful",
"statusDetails": "allOffersRejected"
}
]
}

06.8. CAN cancellation

In case of a limited list of reasons published Contract Award Notice can be cancelled by Procuring Entity. Such cancellation can be executed within submitting of separate object - amendment, contains all the information needed to execute and publish such cancellation.

Get X-OPERATION-ID

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=cancel-can&ocid=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",

"schema": {},
"data": {}
}

Send Request

POST /cancel/can/ocds-000-00001/ocds-000-00001-cn/ocds-000-00001-can-3/ HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

As a result of cancellation of CAN, this CAN will be switched by system automatically to the terminal state ‘cancelled’, lot will be moved back to evaluation phase and all previous decisions of CA under cancelled CAN will be cancelled. So CA will be able to proceed with evaluation of awards of this lot from very beginning

{
"contracts": [
{
"id": "ocds-000-00001-can-3",
"status": "cancelled"
}
]
}

Future steps

Signing of the decision on cancellation made by TC

To be provided

Contracting

Since awarded contract shall be generated as a single AC for several lots, either single or several CANs’ IDs can be put under one AC-initiation request depending on decision of Procuring Entity to have separate contract concluded per each awarded lot or one single ‘merged’ contract concluded for the set of awarded lots where selected winner is the same legal entity.

8.1. Awarded contract initiation

Once the established review period expires, a set of awarded contracts for manual update and issuing of the contract to be signed and validated by Treasury can be generated by initiation from Procuring Entity.

Get X-OPERATION-ID

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=ac&ocid=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",

"schema": {},
"data": {}
}

Send Request

POST /do/contract/ocds-000-00001/ocds-000-00001-cn HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point notification about ‘awarded contracts’ generated

Feed point will inform operating NEPP with such awarded contracts and its tokens. NEPP must notify its user (CA) and share received master-data (tokens) with him to be able to operate and provide manual qualification and evaluation.

{
"initiator": "bpe",
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"X-RESPONSE-ID": "f5c6a3c1-5ff8-463f-9c0c-d4c1f324b7fb",
"data": {
"ocid": "ocds-000-00001",
"url": "http://public.eprocurement.systems/tenders/ocds-000-00001",
"operationDate": "2018-08-14T13:51:06Z",
"outcomes": {
"ac": [
{
"id": "ocds-000-00001-ac-1",
"X-TOKEN": "c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4"
}
]
}
}
}

Each generated ‘awarded contract’ is now related to each ‘award:active’. Such relation described within ‘RelatedProcesses’ object as attribute of specific item of ‘contracts’ array in evaluation part included by the system once ‘awarded contracts’ are generated.

Updates of parent Contract Award Notices

{
"id": "ocds-000-00001-can-1",

"relatedProcesses": [

{

"id": "1",

"identifier": "ocds-000-00001-ac-1",

"relationship": "x_contracting",

"scheme": "ocds",

"uri": "http://public.eprocurement.systems/tenders/ocds-000-00001/ocds-000-00001-ac-1"
}

]
}
]
}
}
}

Thereafter, CA prepares each draft for signing with updates with actual needed data.

8.2. Contract preparation

CA shall complete data required for issuing of the contract (its PDF version) based on prescribed template: separate for different procurement categories (goods, works or service). Set of such required date is described by auto-generated draft of the contract.

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=update-ac&ocid=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Tenderer can register files for the future updated contract before such contract is updated. Document registration is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

{
"success": true,
"data": {
"id": "4c4f5a50-89cd-11e8-b758-dd76462396b0",
"url": "http://storage.eprocurement.systems/get/4c4f5a50-89cd-11e8",
"dateModified": "2018-07-17T14:25:47Z"
}
}

Send Request

POST /do/contract/ocds-000-00001/ocds-000-00001-ac-1/ocds-000-00001-ac-1 HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Tenderer can upload files for the newly updated awarded contract. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

Before prepared contract is issued CA is able to update AC as many time as needed.

08.3. Issuing of prepared contract

Once all updates are done, CA indicates this contract is fully prepared for signing.

Get X-OPERATION-ID

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb"
}

Send Request

POST /issue/contract/ocds-000-00001/ocds-000-00001-ac-1 HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

System automatically generates PDF document of needed contract based on received data and standardized template. Such document will be put as a docType:contractSigned to the ‘documents’ section of specific contract and all this contract will be switched to ‘statusDetails:approvement’. Thereafter, signing and validation process starts.
Also system will include description of required confirmations via adding a ‘confirmationRequests’ array of object to the ‘contract’

08.4. Signing

Once contract is issued and PDF version is generated and added to the contract.documents by the system, contract will go to ‘statusDetails:approvement’ and will be ready to signed by Contracting Authority. To confirm that contract signed by CA:

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operation.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

{
"success": true,
"data": {
"id": "4c4f5a50-89cd-11e8-b758-dd76462396b0",
"url": "http://storage.eprocurement.systems/get/4c4f5a50-89cd-11e8",
"dateModified": "2018-07-17T14:25:47Z"
}
}

Send Request

POST /do/confirmation/buyer/ocds-000-00001/ocds-000-00001-ac-1/confirmationRequestID HTTP/1.1

POST /do/confirmation/supplier/ocds-000-00001/ocds-000-00001-ac-1/confirmationRequestID HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Tenderer can upload files for the newly updated awarded contract. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

The signing of generated contract and any other documents that must be signed according to confirmation requests is completely on the NEPPs side through M-Sign

08.5. Validation

08.6. Activation

Future steps

08.7. Execution

To be provided during next phase

08.8. Amendments and extensions

To be provided during next phase

08.9. Termination

To be provided during next phase

Tender/lot cancellation

The cancellation mechanism technically implemented in a different way for all tender and separate lot:

09.1. Cancellation of procedure

Any time before first AC is concluded, issued, signed and activated, CA is able to cancel procedure by his own decision based on one or several of pre-defined reasons. After at least one AC passed preparation phase and activated - there is no more way to cancel all procedure. It is only lots can be canceled in case if such lots still in ‘active’ status and there is no activated AC related with this lot (see details bellow).

Get X-OPERATION-ID and needed data set from Form Service

Learn more about mechanism and what is ‘X-OPERATION-ID’ is

POST ?form=cancellation-tender&ocid=...&lang=... HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Host: operations.eprocurement.systems

201 OK
Content-Type: application/json; charset=UTF-8

{
"X-OPERATION-ID": "f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb",
"schema": {},
"data": {}
}

Registration Documentation

Procuring entity can register files for the future amendment for contracting process before such amendment is updated. Document registration is an iterative process.

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

{
"success": true,
"data": {
"id": "4c4f5a50-89cd-11e8-b758-dd76462396b0",
"url": "http://storage.eprocurement.systems/get/4c4f5a50-89cd-11e8",
"dateModified": "2018-07-17T14:25:47Z"
}
}

Send Request

POST /cancel/cn/ocds-000-00001/ocds-000-00001-cn HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
X-OPERATION-ID: f5c6a3c0-5ff8-463f-9c0c-d4c1f324b7fb
X-TOKEN: c3bdd497-ac2d-4e25-bd7f-cd55111aa7b4
Content-Type: application/json
Host: bpe.eprocurement.systems

{}

202 Accepted
Content-Type: application/json; charset=UTF-8

Feed Point Response

Uploading Documentation

Tenderer can upload files for the newly created amendment. Document uploading is an iterative process. Accordingly, a registration request must be made for each document added

POST /registration HTTP/1.1
Authorization: Bearer QWxhZGRpbjpPcGVuU2VzYW1l
Content-Type: application/json
Host: storage.eprocurement.systems

{
"hash": "9a0364b9e99bb480dd25e1f0284c8555",
"weight": "1024",
"filename": "file.txt"
}

201 Created
Content-Type: application/json; charset=UTF-8

09.2. Cancellation of single lot

Cancellation of lot is executed within standart update of Contract Notice: identifier of lot or lots to be excluded needs to be absent in update-payload based on cn command-model

CA can cancel either procedure or separate lot anytime before its completion

Let’s go!

Budgets, Funding and Plans

01. Expenditure Items (EIs)

01.1. Retrieving a list of existing EIs

Retrieving conducted EIs and related information

01.2. Create EI

Get X-OPERATION-ID and needed data set from Form Service

Send Request

Feed Point Response

Request for full Result

01.3. Update EI

Get X-OPERATION-ID and needed data set from Form Service

Send Request with updates

Feed Point Response

Request for result

01.4. Retrieving a list of available budget lines (IBANs) for EI

02. Funding Source (FS)

02.1. Retrieving a list of existing FS

Retrieving conducted FSs and detailed information

02.2. Create FS

Get X-OPERATION-ID and needed data set from Form Service

Send Request

Feed Point Response

Request for Result

02.3. Update FS

Get X-OPERATION-ID and needed data set from Form Service

Send Request

Feed Point Response

Request full result

02.4. Retrieving an amount of available value for specific IBAN

02.5. Validation of amount for specific IBAN

Scheduled or announced Tenders: PN, PIN, CN

03.1. Retrieving scheduled or announced CNs and related information

Preparing a notice

Planning Notice

03.2. Create PN

Get X-OPERATION-ID and needed data set from Form Service

Registration Documentation

Send Request

Feed Point Response

Uploading Documentation

Request full result

03.3. Update PN

Get X-OPERATION-ID and needed data set from Form Service

Registration Documentation

Send Request

Feed Point Response

Uploading Documentation

Request full result

Prior Information Notice (PIN)

03.4. Create PIN

Get X-OPERATION-ID and needed data set from Form Service

Registration Documentation

Send Request

Feed Point Response

Uploading Documentation

Request full result

03.5. PIN on PN

Get X-OPERATION-ID and needed data set from Form Service

Send Request

Feed Point Response

Request full result

03.6. Update PIN

Get X-OPERATION-ID

Registration Documentation

Send Request

Feed Point Response

Uploading Documentation

Request full result

Contract Notice (CN)

03.7. Create CN

Get X-OPERATION-ID and needed data set from Form Service

Registration Documentation

Send Request

Feed Point Response

Uploading Documentation

Request full result

03.8. CN on PIN

Get X-OPERATION-ID and needed data set from Form Service

Send Request