Realistic estimated value

Rule Definition

Every procurement procedure with estimated value above a given threshold has an estimated value wich follows follows a realistic number pattern.

---

Additional Information

Rule elaboration

Examples of unrealistic number patterns: 111,111,1111; 222,222,222; 333,333,333; 444,444,444; 555,555,555; 666,666,666; 777,777,777; 888,888,888; 999,999,999 or 123,456,789.

Accuracy Business Rule with ID ACC002 as defined in deliverable D06.06 – Data Quality Action Plan.

Ontology property involved: http://data.europa.eu/a4g/ontology#hasEstimatedValue

Rule source

https://code.europa.eu/eproc/ppds/documentation/-/blob/main/documents/d0606_data_quality_action_plan.md#24-accuracy-business-rules

Rule implementation

ppsh:Lot-hasEstimatedValue

Implementation note

Implementation in PPDS SHACL shapes graph:

ppsh:Lot-hasEstimatedValue a sh:PropertyShape ;
	sh:description "For procurement procedures with total value (Contract Award Value) above a given threshold, the Contract Award Value should not follow an unrealistic number pattern (e.g. 111,111,1111; 222,222,222; 333,333,333; 444,444,444; 555,555,555; 666,666,666; 777,777,777; 888,888,888; 999,999,999 or 123,456,789)" ;
	sh:class epo:MonetaryAmount ;
	sh:severity sh:Warning ;
	sh:message "ACC002" ;
	sh:name "The MonetaryValue needs to be coherent." ;
    sh:path epo:hasEstimatedValue ;
	sh:not [
		sh:pattern "([0-9]+)\\1$" ;
	] .

https://sdlc.webcloud.ec.europa.eu/ppds/docker/ppds-shacl-shapes/-/blob/featured/revision_0.3.3/ppds-shapes.ttl?ref_type=heads

Related rules

#25

#82

History note

(If applicable, add here a note about a previous state of the rule, before the Rulebook)