How to handle different thresholds for different types of Services from the same Jurisdiction?
afomi opened this issue · 6 comments
Solano County, CA has logical conditions in its Procurement logic related to amount and type of service. Does OpenProcure handle/track this? If so, how?
Source: http://www.solanocounty.com/civicax/filebank/blobdload.aspx?blobid=12011
This #24 is a great start!
Solano has 4 branches in its logic. I'm wondering if and how consistent these thresholds and conditions are across jurisdictions.
Thanks for the input Ryan!
This is a great example where to apply the vague threshold definitions I
had in mind: below $10,000 for one written quote, above $25,000 for formal
sealed bids.
On Oct 13, 2015 6:15 PM, "Ryan Wold" notifications@github.com wrote:
This #24 #24 is a great
start!Solano has 4 branches in its logic. I'm wondering if and how consistent
these thresholds and conditions are across jurisdictions.—
Reply to this email directly or view it on GitHub
#25 (comment)
.
Ryan brings up a good point and something that is important to clearly explain. The data shows there is no universal consistency, but in most cases there are three thresholds:
- up to $5,000 => no quotes required, can purchase direct.
- $5,000 - $25,000 => informal bid, 3 quotes usually required - sometimes can be oral quotes
- above $25,000 => formal bids
OK. You picked a different first threshold than me ($5k verbal quote vs $10k written quote) but we're all saying the same thing: there most often are 3 ranges, separated by 2 thresholds.
After I merge #24 we can work on clarifying what we think the thresholds should represent.
👍
—
Sent from Mailbox
On Tue, Oct 13, 2015 at 7:10 PM, Julien Vanier notifications@github.com
wrote:
OK. You picked a different first threshold than me ($5k verbal quote vs $10k written quote) but we're all saying the same thing: there most often are 3 ranges, separated by 2 thresholds.
After I merge #24 we can work on clarifying what we think the thresholds should represent.
Reply to this email directly or view it on GitHub:
#25 (comment)