Methodology
For each contracting process, the submission period is calculated as:Example: The National Rail Service publishes a tender notice on March 15 with a submission deadline of March 20. The submission period is 5 days, which is less than the default threshold of 15 days, so this contracting process would be flagged.
Output
The indicator’s value is always1.0 when a contracting process is flagged.
Configuration
All configuration is optional.The minimum number of whole days required for the submission period. Contracting processes with shorter periods are flagged.Add to your settings file:
Set different thresholds based on procurement method details (
/tender/procurementMethodDetails). Useful for aligning with jurisdiction-specific legislation.Add a [R003.procurement_method_details] section where property names are /tender/procurementMethodDetails values:Calculate this indicator only for specific procurement methods (
/tender/procurementMethod). Provide as a pipe-separated list.Example Output
Input (OCDS JSONL):Implementation Details
Fromsrc/indicators/r003.rs:27-49:
The indicator:
- Checks if the tender has a
tenderPeriodwith bothstartDateandendDate - Calculates the duration in whole days using
num_days() - Determines the applicable threshold (custom per procurement method details, or default)
- Flags the process if
duration < threshold - Only processes tenders matching configured procurement methods (if specified)
