Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Bid section to Tender #197

Closed
practicalparticipation opened this issue Mar 12, 2015 · 5 comments
Closed

Add Bid section to Tender #197

practicalparticipation opened this issue Mar 12, 2015 · 5 comments
Assignees
Labels
Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions
Milestone

Comments

@practicalparticipation
Copy link
Contributor

practicalparticipation commented Mar 12, 2015

Bidding information was not included in the 1.0 RC due to a range of different proposals. There is however demand to be able to express bidding information

Based on discussions in #78 we should provide an updated bidding schema proposal and work this up as an extension.

@practicalparticipation practicalparticipation added this to the After 1.0 milestone Mar 12, 2015
@practicalparticipation practicalparticipation added the Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions label Mar 12, 2015
@timgdavies
Copy link
Contributor

There is a clear proposal at http://api-docs.openprocurement.org/en/latest/standard/bid.html which we should consider, work up and test with data from Mexico City and other contexts.

(cc @myroslav - any learning from use of your bid section we should take into account?)

@myroslav
Copy link

Our procurement process has no pre-qualification and so called self-declaration principle is employed. i.e. it is assumed that all bidders are able to provide qualification documents "when needed" and thus provides only significant documentation in advance i.e. specs of a product to deliver, and the value. After auction (so called reduction) where bid value is reduced there is clear sequence of bids to do qualification process (from lowest to highest value).

The winner (and only the one) is able to provide her extra qualification documents, that were omitted in earlier bidding stage. These documents appear to be the same in data structures as the ones provided in advance, but in fact they have to clearly separated, since they were provided for different bid amount (i.e. the one significantly reduced by reduction). We do that differentiation by date, since we know when auction took place, but that solution is not the most elegant one. The winner can be disqualified, and next Bid in the sequence is allowed to provide extra documentation for qualification purposes.

The other not-so-smooth part was bid value, since it has currency and VAT flag that should match the one of the tender. It is information duplication requiring extra validation.

There is only single element in tenderers array, since collective bids always have some single Organization here.

Bid status is not used at all, yet. We are employing Awards for the qualification process.

These are the most important elements of Bid in our procurement process.

@timgdavies
Copy link
Contributor

Bidding information is also desired in Taiwan, where draft data includes a block along the lines below, capturing failed bids:

withoutTenderer: [
   {
     bidAmount: 1536406,
     number: 1,
     failReason: "資格、規格合於招標文件但非最低(高)標"
  },
  { 
     bidAmount: 1536406,
     number: 2,
     failReason: "資格、規格合於招標文件但非最低(高)標"
   }
]

@timgdavies
Copy link
Contributor

I've not had time to work up a full schema here yet, but as a quick example of what a bids block could look like which would fit with the current approach in Ukraine, and potentially help model the Taiwan data, here's an example:

{"bids":[
  {
    "id":"123",
    "date":"2015-12-05T13:11:59+00:00",
    "tenderers":[{ }],
    "status":"failed",
    "statusDetails":"",
    "value": {
       "amount":12356.00,
       "currency":"USD"
    },
    "documents":[]

  } 
  ]
}

In this case, the data above from Taiwan could be modelled as:

{"bids":[
  {
    "id":"1",
    "status":"failed",
    "statusDetails":"資格、規格合於招標文件但非最低(高)標",
  },
{
    "id":"2",
    "status":"failed",
    "statusDetails":"資格、規格合於招標文件但非最低(高)標",
  },

  ]
}

@timgdavies timgdavies modified the milestones: Version 1.1, After 1.0 Jul 25, 2016
@timgdavies timgdavies changed the title Develop Bid Extension Add Bid section to Tender Jul 25, 2016
@timgdavies
Copy link
Contributor

timgdavies commented Sep 18, 2016

Developed in #379

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions
Projects
None yet
Development

No branches or pull requests

4 participants