Rules to prevent the input of negative values in certain amounts fields
We have conducted research on the use of negative amounts in eForms notices. Please see below the break-down, specifying for which amount field negative values were used how many times (per notice and in total).
| Field | Instance count | Notice count | Field Type | Field Name |
|---|---|---|---|---|
| BT-720-Tender | 166 | 102 | amount | Tender Value |
| BT-710-LotResult | 64 | 45 | amount | Tender Value Lowest |
| BT-161-NoticeResult | 43 | 43 | amount | Notice Value |
| BT-711-LotResult | 34 | 27 | amount | Tender Value Highest |
| BT-271-Lot | 9 | 7 | amount | Framework Maximum Value |
| BT-271-Procedure | 5 | 5 | amount | Framework Maximum Value |
| BT-27-Lot | 5 | 4 | amount | Estimated Value |
| BT-1118-NoticeResult | 2 | 2 | amount | Notice Framework Approximate Value |
| BT-660-LotResult | 2 | 2 | amount | Framework Re-estimated Value |
| BT-709-LotResult | 3 | 2 | amount | Framework Maximum Value |
| BT-27-Procedure | 1 | 1 | amount | Estimated Value |
| BT-118-NoticeResult | 0 | 0 | amount | Notice Framework Maximum Value |
| BT-156-NoticeResult | 0 | 0 | amount | Group Framework Maximum Value |
| BT-1561-NoticeResult | 0 | 0 | amount | Group Framework Re-estimated Value |
| BT-157-LotsGroup | 0 | 0 | amount | Group Framework Maximum Value |
| BT-160-Tender | 0 | 0 | amount | Concession Revenue Buyer |
| BT-162-Tender | 0 | 0 | amount | Concession Revenue User |
| BT-27-LotsGroup | 0 | 0 | amount | Estimated Value |
| BT-27-Part | 0 | 0 | amount | Estimated Value |
| BT-271-LotsGroup | 0 | 0 | amount | Framework Maximum Value |
| BT-553-Tender | 0 | 0 | amount | Subcontracting Value |
| BT-644-Lot | 0 | 0 | amount | Prize Value |
| BT-779-Tender | 0 | 0 | amount | Tender Payment Value |
| BT-782-Tender | 0 | 0 | amount | Tender Penalties |
| BT-793-Review | 0 | 0 | amount | Review Remedy Value |
| BT-795-Review | 0 | 0 | amount | Review Request Fee |
We suggest that if negative amounts have been used less than 10 times for a specific field (across ca. 1.9 million notices) we will introduce rules prohibiting the input of negative amounts into this field to increase data quality.
Concretely, we would suggest putting this rule in place for the following fields in SDK 1.15:
- BT-271-Lot (Framework Maximum Value)
- BT-271-Procedure (Framework Maximum Value)
- BT-27-Lot (Estimated Value)
- BT-1118-NoticeResult (Notice Framework Approximate Value)
- BT-660-LotResult (Framework Re-estimated Value)
- BT-709-LotResult (Framework Maximum Value)
- BT-27-Procedure (Estimated Value)
- BT-118-NoticeResult (Notice Framework Maximum Value)
- BT-156-NoticeResult (Group Framework Maximum Value)
- BT-1561-NoticeResult (Group Framework Re-estimated Value)
- BT-157-LotsGroup (Group Framework Maximum Value)
- BT-160-Tender (Concession Revenue Buyer)
- BT-162-Tender (Concession Revenue User)
- BT-27-LotsGroup (Estimated Value)
- BT-27-Part (Estimated Value)
- BT-271-LotsGroup (Framework Maximum Value)
- BT-553-Tender (Subcontracting Value)
- BT-644-Lot (Prize Value)
- BT-779-Tender (Tender Payment Value)
- BT-782-Tender (Tender Penalties)
- BT-793-Review (Review Remedy Value)
- BT-795-Review (Review Request Fee)
For the following fields, where negative amounts are used more often, we would like to discuss more during the workshop:
- BT-720-Tender (Tender Value)
- BT-710-LotResult (Tender Value Lowest)
- BT-161-NoticeResult (Notice Value)
- BT-711-LotResult (Tender Value Highest)
For these 4 fields we would like to discuss about the possible circumstances where negative amounts would be used. Based on the discussions we would then either put in place more nuanced rules for these fields (accounting for different circumstances), or it could be decided to not put such controls on these fields for the moment.