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

Criterion #23 wording – inconsistency with Regulation #246

Closed
sakispantazis opened this issue May 19, 2019 · 3 comments
Closed

Criterion #23 wording – inconsistency with Regulation #246

sakispantazis opened this issue May 19, 2019 · 3 comments

Comments

@sakispantazis
Copy link

Criterion 23 (i.e. the question regarding Guilty of misinterpretation, withheld information, inability to provide required documents and obtained confidential information of this procedure)

The Regulation’s stipulations for this criterion are:
image

In the current implementation of the ESPD taxonomy/structure for the criterion 23 the question differs compared to the Regulation. It seeks for a negative answer instead of a positive one and the wording is:

“Can the economic operator confirm that:
a) It has been guilty of serious misrepresentation in supplying the information required for the verification of the absence of grounds for exclusion or the fulfillment of the selection criteria,
b) It has withheld such information,
c) It has not been able, without delay, to submit the supporting documents required by a contracting authority or contracting entity, and
d) It has undertaken to unduly influence the decision making process of the contracting authority or contracting entity, to obtain confidential information that may confer upon it undue advantages in the procurement procedure or to negligently provide misleading information that may have a material influence on decisions concerning exclusion, selection or award?”
We implemented this criterion accordingly to the current ESPD taxonomy/structure. Hopefully all implementers have changed the question’s wording to match the ESPD taxonomy/structure. However, the following issue arises: should we change the Regulation accordingly to match the ESPD taxonomy/structure or vice versa? If it was up to me, sending a notification eMail to all implementers to double check the wording, would be enough. However, since it might have legal implications and because lawyers are rather attached to the wording, we might have to change one or the other. Notice: Changing the ESPD taxonomy/structure, would have the consequence that all ESPD artifacts completed so far will show a wrong answer.

@mireiaBM
Copy link

mireiaBM commented Aug 8, 2019

The wording will not be modified, as the wording is an issue related to the application/UI and not to the ESPD data model per se.

@mireiaBM mireiaBM closed this as completed Aug 8, 2019
@jerouris
Copy link
Collaborator

jerouris commented Aug 29, 2019

Dear Mireia,
I would like to reopen this issue because your statement might be incorrect and we need some more clarifications.

You state that wording is an issue related to the application/UI, however, the application/UI takes its wording from the ESPD Taxonomy, which is an official artifact of the ESPD EDM. (see here )

Can you please reevaluate the issue, taking these facts into account?

@JosePRevenga
Copy link
Collaborator

Exclusion grounds are to be answerd always negatively to confirm that there is no law offendance.

For more information please refer to issue #242.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants