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

Part IV, Section C (References) #67

Closed
paulakeen opened this issue Mar 9, 2017 · 6 comments
Closed

Part IV, Section C (References) #67

paulakeen opened this issue Mar 9, 2017 · 6 comments

Comments

@paulakeen
Copy link
Collaborator

Please find below a proposal for the mock-up regarding the references to be provided by the EO:

mu_recipients_eo

(in the example above, for work contracts, but the same information and structure would apply to services and supplies)

@paulakeen
Copy link
Collaborator Author

Please find below a new proposal for the mock-ups regarding the references on similar works, deliveries or services, both from the view of the CA and the view of the EO:

  • View of the CA: The CA is able to enter the minimum number of references required and to enter as many requirements as needed.

mu_references_ca

  • View of the EO: The specific requirements entered by the CA are displayed to the EO. The EO can add the references the comply with the requirements.

mu_references_eo

(The examples above apply to work contracts, but the same information and structure would apply to services and supplies)

@paulakeen
Copy link
Collaborator Author

Please find below what was commented about this issue in the discussion group:

Anne Katrine Mortensen: But isn´t that info found in the contract notice?

Anne Katrine Mortensen: When info is repeated in different procurement documents there is always a danger of not the same wording being repeated

Timo Rantanen / Hansel / Finland: Adding jusgt one text box for CA woudl do the job

Timo Rantanen / Hansel / Finland: yes

Anne Katrine Mortensen: Couldn´t we call it "Recipient(s) and contact mail(s)"

Jose Luis Cueva - Spain: what about an url where the picture is available

Anne Katrine Mortensen: I thought the meaning with the ESPD also was to reduce transactions costs, therefore make an application shorter than before 2016.

Michaël De Winne / e-Proc Belgium: I agree with Anne Katrine, aren't we complicating the life of EOs instead of facilitating their participation to tenders?

Michaël De Winne / e-Proc Belgium: by asking all this extra information

Jose Luis Cueva - Spain: I gree with A-K: not to add too much to the ESPD. Pictures can be overkill

Anne Katrine Mortensen: Architects and others feel that they need pictures but what is the meaning overall with the ESPD

Jose Luis Cueva - Spain: the ESPD is in the "selection phase". I do not think necessary much more at this stage.

Michaël De Winne / e-Proc Belgium: Jose Luis: I agree

Marit, Mercell: would it be OK for procurement systems to allow pictures in the description? It is a big request - from those who are good looking ;-)

Jose Luis Cueva - Spain: Pictures can be important for evaluating the tender itself, but for the selection of tenderers not so much needed

Jose Luis Cueva - Spain: could ypou spaak louder please?

Jose Luis Cueva - Spain: I could not hear you

Anne Katrine Mortensen: Is "Issuer" necessary? And what is meant by issuer?

Marit, Mercell: Source?

Anne Katrine Mortensen: But isn´t that the recepient?

Michaël De Winne / e-Proc Belgium: Would the "issuer" not most often be the CA who awarded thereferenced contract?

Anne Katrine Mortensen: I don not find "Issuer" necessary.

Anne Katrine Mortensen: Make the ESPD more simple and only with need-to-know-info at this stage.

Anne Katrine Mortensen: What do you need issuer for when you can contact the recipient?

Anne Katrine Mortensen: I understand "URL" that could be the firms own website. And code I can understand if you need a password.

Anne Katrine Mortensen: I agree people will be confused by Issuer

Jose Luis Cueva - Spain: I agree

Laura Martin / Scottish Government: We would use the term 'example' rather than reference. In the UK, we consider references to be provided by the previous customers. i.e the Recipent in this screenshot.

Marit Lysemose Thomsen, Mercell: yes

Rudolf Maier: The link must lead to the translation of the reference in the language of the CA.

Anne Katrine Mortensen 2: I never see an operator states an URL

Laura Martin / Scottish Government: yeah, that seems fine

Marit Lysemose Thomsen, Mercell: I thought URL could be used to link to e.g. a website that shows descrption photos film of the project of the reference

Rudolf Maier: Proof of a former contract fullfilled to the satisfaction of the former CA.

Jose Luis Cueva - Spain: url is not sufficient in manu cases

Laura Martin / Scottish Government: I was referring to reference in the other screenshot.

Jose Luis Cueva - Spain: the url can point to a database with many references - > the key for the particular reference is needed

Laura Martin / Scottish Government: It would be more clear in Scotland but we could change it in our system.

Rudolf Maier: the challange is the proof of the reference by the EO (signature of the CA who had a contracted with the EO.

Steve Patterson (Scottish Government): A reference is prvided by a third party, whereas asexample is provided by the EO

Laura Martin / Scottish Government: I am not sure about that :)

Steve Patterson (Scottish Government): not sure about that!

Alba Colomer (GROW): maybe a tooltip with an explanation would be enough?

Anne Katrine Mortensen 2: or name it former work

Jose Luis Cueva - Spain: The Directive says "supporting documents"

Jose Luis Cueva - Spain: I do not suggest using the label "supporting document"

Rudolf Maier: As aselection criteria refences are necessary not examples.

@paulakeen
Copy link
Collaborator Author

paulakeen commented Mar 20, 2017

Please find below a new proposal for the mock-up regarding the references on similar works, deliveries or services from the view of the EO, according to the final decision made in last Wednesday's meeting:

mu_references_new_proposal_eo

The information provided in the tooltip could be as follows: "The verification code will allow the CA to verify that the information and documents provided by the EO exactly matches the reference available in the URL."

@paulakeen
Copy link
Collaborator Author

Please find below what was commented about this issue in the discussion group (22/03/2017):

Anne Katrine Mortensen, DK: Appliers contract sum

Enric Staromiejski (GROW): @josé luis: +1

Anne Katrine Mortensen, DK: EO´s fee or EO´s amount

virgiliu: total amount and specific amount?

Michaël De Winne / e-Proc Belgium: the whole amount should only be asked to the main contractor, no?

Anne Katrine Mortensen, DK: Total amount or Specific amount

virgiliu: yes, mc, something like that

Michaël De Winne / e-Proc Belgium: but will a subcontractor know what the total value of a project was, if he only did only part of it as a subcontractor?

Anne Katrine Mortensen, DK: Yes

Anne Katrine Mortensen, DK: Consultants might be sub sub consultants

Anne Katrine Mortensen, DK: Necessary for services, total and specific

Anne Katrine Mortensen, DK: Optional is a good idea, M-C

John Degiorgio: I believe that the tender would set a threshold. The contractor has to confirm if he meets that requirement

John Degiorgio: Yes my comment is holistic. Why all this info?

Anne Katrine Mortensen, DK: I find it clear.

@paulakeen
Copy link
Collaborator Author

paulakeen commented Mar 27, 2017

Please find below a new proposal for the mock-up regarding the references on similar works, deliveries or services from the view of the EO, according to the final decision made in last Wednesday's meeting:

mu_references_eo_67

@paulakeen
Copy link
Collaborator Author

Please find the details of the final decision in https://github.com/ESPD/ESPD-EDM/wiki/8.-References-on-similar-works,-deliveries-or-services

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

1 participant