From 0546e602722c702c18767d919601b002f4c401b0 Mon Sep 17 00:00:00 2001 From: "gabriele.dall@adesso.de" Date: Fri, 15 Nov 2024 17:24:50 +0100 Subject: [PATCH] Quality improvement at p-level and for t019 and T023 regarding naming of economic operator and contracting body, decapitalizing of certain an UBL/BIS-Terms and correction imange names and Links --- guides/profiles/p011/introduction.adoc | 4 +-- .../non-functional-requirements.adoc | 4 +-- .../principles/qualification-encryption.adoc | 2 +- guides/profiles/p011/process/index.adoc | 2 +- guides/shared/interoperability.adoc | 1 + guides/shared/links.adoc | 2 +- guides/shared/tendering.adoc | 21 +++++------ .../T019/descriptions/date-time.adoc | 2 +- .../T019/descriptions/parties.adoc | 3 +- .../T019/principles/parties-roles.adoc | 2 +- .../transactions/T019/requirements/index.adoc | 2 +- .../T022/principles/parties-roles.adoc | 10 +++--- .../transactions/T023/descriptions/index.adoc | 34 +++++++++--------- ...ejection.png => QualificationResponse.png} | Bin .../transactions/T023/identifiers/index.adoc | 2 +- .../transactions/T023/identifiers/peppol.adoc | 4 +-- .../T023/principles/parties-roles.adoc | 6 ++-- 17 files changed, 52 insertions(+), 49 deletions(-) rename guides/transactions/T023/files/{QualificationRejection.png => QualificationResponse.png} (100%) diff --git a/guides/profiles/p011/introduction.adoc b/guides/profiles/p011/introduction.adoc index 4d8c2bd0..c5031fba 100644 --- a/guides/profiles/p011/introduction.adoc +++ b/guides/profiles/p011/introduction.adoc @@ -10,8 +10,8 @@ The {name-profile} describes electronic messaging support for the business proce * An economic operator can use this BIS {P011} to submit qualification documents to a contracting authority as specified in the Call for Tender documents. * The BIS can be used for qualification as part of a restricted, negotiated or competitive dialogue tendering procedure. The qualification transaction is specific to a particular call for tenders. - * The contracting authority confirms the reception of the qualification documents using BIS {P011}. - * Out of scope: The contracting authority evaluates the qualification information and reports his decision, positive or negative, to the economic operator. The decision reporting is out of the scope of this BIS. In the case of a positive qualification response the contracting authority can continue with the tendering process. The positive qualification is expressed by the invitation to submit a tender (not in scope of this BIS) covered by PEPPOL BIS {P013}. PEPPOL BIS {P012} provides capabilities to inform an economic operator that his qualification has been rejected and that the economic operator is excluded from the procedure by the contracting authority. + * The contracting body confirms the reception of the qualification documents using BIS {P011}. + * Out of scope: The contracting body evaluates the qualification information and reports his decision, positive or negative, to the economic operator. The decision reporting is out of the scope of this BIS. In any case, every economic operator having applied by sending in their qualification documents will receive a {P012}. While a positive response will soon be followed by the invitation to submit a tender (not in scope of this BIS), covered by PEPPOL BIS {P013}. Those who have been informed that their qualification has been rejected are excluded from the ongoing procurement process by the contracting authority. In an open procedure this profile is not used but the qualification may be sent together with the tender, an economic operator submits. Submitting a tender with qualification is defined in {P003}. diff --git a/guides/profiles/p011/principles/non-functional-requirements.adoc b/guides/profiles/p011/principles/non-functional-requirements.adoc index 704c8c71..54c32cfa 100644 --- a/guides/profiles/p011/principles/non-functional-requirements.adoc +++ b/guides/profiles/p011/principles/non-functional-requirements.adoc @@ -8,8 +8,8 @@ For the {link-peppol} BIS all non-functional requirements are applicable as docu | Req. ID | Requirement statement | br49-001 | All qualifications shall be linked to a procurement project in order for the contracting body to be able to evaluate them. | br49-002 | A qualification must enable identifying the candidate as one economic operator or a set of economic operators and their roles. -| br49-003 | A qualification must provide the minimal information, possibly unstructured to provide sufficient evidences as required by the Contracting body. +| br49-003 | A qualification must provide the minimal information, possibly unstructured to provide sufficient evidences as required by the contracting body. | br49-004 | All qualifications may be encrypted upon submission. Encryption keys are provided by the contracting body. | br49-005 | The economic operator shall receive an acknowledgement that his qualification has been received by the contracting body for the purpose of recipient non repudiation. -| br49-006 | The receipt notification of a qualification shall contain a cryptographic time stamp of the moment the Contracting body received the complete qualification. +| br49-006 | The receipt notification of a qualification shall contain a cryptographic time stamp of the moment the contracting body received the complete qualification. |=== diff --git a/guides/profiles/p011/principles/qualification-encryption.adoc b/guides/profiles/p011/principles/qualification-encryption.adoc index becc98c3..9a886f07 100644 --- a/guides/profiles/p011/principles/qualification-encryption.adoc +++ b/guides/profiles/p011/principles/qualification-encryption.adoc @@ -1,7 +1,7 @@ = Encryption of Qualification documents -The Call For Tenders (CfT) business document is used by the contracting authority to provide an economic operator with the latest updated procurement documents. Besides transporting procurement documents it MUST be used to transport the encryption certificate needed by the economic operator to encrypt his qualification for submission. The method how to include the Encryption Certificates is desribed in link:/pracc/transactions/T004/index.html[T004 - section 5.5. Transport of encryption certificate via the Call For Tenders] +The Call For Tenders (CfT) business document is used by the contracting body to provide an economic operator with the latest updated procurement documents. Besides transporting procurement documents it MUST be used to transport the encryption certificate needed by the economic operator to encrypt his qualification for submission. The method how to include the Encryption Certificates is desribed in link:/pracc/transactions/T004/index.html[T004 - section 5.5. Transport of encryption certificate via the Call For Tenders] If the CfT business document provided an encryption certificate, the qualification documents MUST be encrypted by the economic operator using that certificate. diff --git a/guides/profiles/p011/process/index.adoc b/guides/profiles/p011/process/index.adoc index 4c9117e1..cb986d73 100644 --- a/guides/profiles/p011/process/index.adoc +++ b/guides/profiles/p011/process/index.adoc @@ -9,7 +9,7 @@ image::bpmnQualification.svg[align="center", width=800] .Business process |=== | Category | Description -| Description | The Economic operator sends an electronic qualification document containing the information requested for qualification by the contracting body in the call for tenders. +| Description | The economic operator sends an electronic qualification document containing the information requested for qualification by the contracting body in the call for tenders. The reception of the qualification is confirmed by the contracting body. diff --git a/guides/shared/interoperability.adoc b/guides/shared/interoperability.adoc index 2bacdbc0..b325cd55 100644 --- a/guides/shared/interoperability.adoc +++ b/guides/shared/interoperability.adoc @@ -10,6 +10,7 @@ It applies the Framework as follows: ** {2014-23-EU} ** {2014-24-EU} ** {2014-25-EU} +** {2009-81-EC} ** {eforms-reg} ** {espd-reg} diff --git a/guides/shared/links.adoc b/guides/shared/links.adoc index 01f35402..f8935e44 100644 --- a/guides/shared/links.adoc +++ b/guides/shared/links.adoc @@ -95,7 +95,7 @@ :2014-23-EU: https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX:32014L0023[Directive 2014/23/EU] :2014-24-EU: https://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX%3A32014L0024[Directive 2014/24/EU] :2014-25-EU: https://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX%3A32014L0025[Directive 2014/25/EU] -:2009-81-EC: https://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX%3A32009L0081 +:2009-81-EC: https://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX%3A32009L0081[Directive 2009/81/EC] :espd-reg: https://eur-lex.europa.eu/eli/reg_impl/2016/7/oj[Commission Implementing Regulation (EU) 2016/7] // ESPD diff --git a/guides/shared/tendering.adoc b/guides/shared/tendering.adoc index 6bdddeed..eb00d381 100644 --- a/guides/shared/tendering.adoc +++ b/guides/shared/tendering.adoc @@ -9,7 +9,7 @@ The profiles provided by CEN BII3 and Peppol are designed to facilitate effectiv Official notification through publishing bodies is part of many procurement procedures. Many pre-award opportunities first become visible to the economic operators in the form of notices describing upcoming or current procurement procedures (prior information notices or contract notices). At the end of a procedure, a contract award notice about the result of the procedure is published. -eNotification covers the transfer of electronic procurement notices for publication and dissemination with the ultimate aim of opening business opportunities. eNotification profiles are addressed to all those who exchange procurement notices for publication and further information processing. eNotification is therefore generally addressed to eTendering Plattform Providers, Contracting Bodies, publishers, print shops, information brokers or monitoring or statistical services. eNotification can be carried out at various levels and between different levels (regional, state, European etc). The legal obligation of publishing notices at the correct level is the responsibility of the contracting bodies. +eNotification covers the transfer of electronic procurement notices for publication and dissemination with the ultimate aim of opening business opportunities. eNotification profiles are addressed to all those who exchange procurement notices for publication and further information processing. eNotification is therefore generally addressed to eTendering platform providers, contracting bodies, publishers, print shops, information brokers or monitoring or statistical services. eNotification can be carried out at various levels and between different levels (regional, state, European etc). The legal obligation of publishing notices at the correct level is the responsibility of the contracting bodies. The content model of procurement notices in Europe is based on {eform-reg} and upon {2014-23-EU}, {2014-24-EU}, {2014-25-EU} and {2009-81-EC} and their annexes, particularly the annex describing the standard forms to be used for the publication of procurement notices. eForms are at the core of the digital transformation of public procurement in the EU. Through the use of a common standard and terminology, they can significantly improve the quality and analysis of data. Well-implemented eForms increase the ability of businesses and other organisations to find opportunities. They will also reduce the administrative burden for buyers, increase the ability of governments to make data-driven decisions about public spending, and make public procurement more transparent. @@ -17,13 +17,13 @@ eNotification covers the electronic transfer of electronic notices for publicati In the EU, eForms are used to publish notices above threshold on Tenders Electronic Daily (TED)—an online portal for public procurement notices from across the EU. On the national level public procurement decision makers can benefit from eForms through tailoring and defining a national approach to the various aspects of eForms, e.g. using them for contracts below thresholds, considering different policies and requirements. -The Peppol BIS {P006} supports a process by which a notification platform can be queried along a set of parameters to find relevant notices and related metadata required by other PEPPOL BISs. The profile is based on CEN WS/BII 3 Profile {BII45} (CWA 17026-104:2016). The transactions, specified in BIS {P006} are intended to be exchanged between eTendering systems and Publication Bodies but they can be adopted by many other actors. Since the {P006} provides access to Open Data, it also provides possibilities for the establishment of new business models that allow monitoring, the provision of statistical information or easy access for economic operators to business opportunities in different countries across different eTendering and eNotification platforms. +The Peppol BIS {P006} supports a process by which a notification platform can be queried along a set of parameters to find relevant notices and related metadata required by other PEPPOL BISs. The profile is based on CEN WS/BII 3 Profile {BII45} (CWA 17026-104:2016). The transactions, specified in BIS {P006} are intended to be exchanged between eTendering systems and publication bodies but they can be adopted by many other actors. Since the {P006} provides access to Open Data, it also provides possibilities for the establishment of new business models that allow monitoring, the provision of statistical information or easy access for economic operators to business opportunities in different countries across different eTendering and eNotification platforms. In order to execute the Peppol BIS {P008} and Peppol BIS {P006}, it is necessary that the parties have Peppol eDelivery in place to enable them to send and receive the transactions in a secure way. Implementers must also support {eforms-specs} content model because the transactions are based on the EU-wide eForms standard. == Tendering procedures -For the purpose of initiating electronic tendering via Peppol, the Peppol BIS {P006} plays a significant role. When the contracting body has published a notice, the interested economic operators who finds it may want to subscribe to this procedure by using PEPPOL {P001} based on {BII46}. Thereby, the Profile {P006} delivers necessary organisational and technical information to identify the procedure and contracting authority. This information is required because the request for procurement procedure subscription must be directed to the entity responsible for the procurement procedure. +For the purpose of initiating electronic tendering via Peppol, the Peppol BIS {P006} plays a significant role. When the contracting body has published a notice, the interested economic operators who find it may want to subscribe to this procedure by using PEPPOL {P001} based on {BII46}. Thereby, the profile {P006} delivers necessary organisational and technical information to identify the procedure and contracting authority. This information is required because the request for procurement procedure subscription must be directed to the entity responsible for the procurement procedure. eTendering can be put in place using different procedures, depending on the value and the type of the contract to be awarded, on the legal nature of the contracting body and on specific member state national legislation ({2014-24-EU} art. 26). Article 26 to 32 from {2014-24-EU} and article 43 to 50 from {2014-25-EU} describe the different tendering procedures that can be used by contracting bodies. For the purpose of electronic tendering, some of these procedures have been described in CEN WS/BII 3 {BII37} (CWA 17027-106) and CEN WS/BII 3 {BII39} (CWA 17027-108). @@ -31,18 +31,19 @@ In open procedures, any economic operator can access the call for tenders docume When the contracting body has published a notice, the interested economic operators may subscribe (unscubsribe) to obtain (not obtain) tendering information using profile CEN WS/BII 3 {BII46} (CWA 17027-111) covered by Peppol BIS {P001}. -Once the interested economic operator has subscribed to an open procedure, the contracting authority provides the procurement documents by using Peppol BIS {P002}. The BIS P002 is based on CEN WS/BII 3 {BII60} (CWA 17027-123) and CEN WS/BII 3 {BII47} (CWA 17027-112) and provides the call for tender documents. It can be repeated at any time until the tender submission deadline to receive the latest version of the procurement documents. Additionally, contracting authorities must push updates to the economic operators that subscribed to a procedure. +Once the interested economic operator has subscribed to an open procedure, the contracting authority provides the procurement documents by using Peppol BIS {P002}. The BIS P002 is based on CEN WS/BII 3 {BII60} (CWA 17027-123) and CEN WS/BII 3 {BII47} (CWA 17027-112) and provides the call for tender documents. It can be repeated at any time until the tender submission deadline to receive the latest version of the procurement documents. Additionally, contracting bodies +must push updates to the economic operators that subscribed to a procedure. -Within the call for tenders, contracting authorities must inform economic operators how to qualify for the procedure. This may be done by an European Single Procurement Document (ESPD) defined by the {espd-reg} for which Peppol develops the BIS ESPD 3.0 based on the {espd-edm}. Additionally, call for tenders may include pre-award catalogue information to describe products and services in a common format allowing economic operators to send offers in a structured way and contracting authorities to evaluate products and services automatically through their tendering tools. The Peppol BIS {preaward-cat} can be used for this purpose and was defined according to the CEN WS/BII 3 Profile {BII35}. +Within the call for tenders, contracting bodies must inform economic operators how to qualify for the procedure. This may be done by an European Single Procurement Document (ESPD) defined by the {espd-reg} for which Peppol develops the BIS ESPD 3.0 based on the {espd-edm}. Additionally, call for tenders may include pre-award catalogue information to describe products and services in a common format allowing economic operators to send offers in a structured way and contracting authorities to evaluate products and services automatically through their tendering tools. The Peppol BIS {preaward-cat} can be used for this purpose and was defined according to the CEN WS/BII 3 Profile {BII35}. -In restricted or negotiated procedures the selection and exclusion criteria for the qualification phase are communicated in a first step to the economic operator by using BIS P002 based on CEN WS/BII 3 {BII60} (CWA 17027-123) and CEN WS/BII 3 {BII47} (CWA 17027-112). The submission of qualification is executed using profile CEN WS/BII 3 {BII49} (CWA 17027-114) covered by PEPPOL BIS {P011}. In restricted and negotiated procedures the contracting authority will send an invitation to tender (second step) only to the identified candidates which have been selected after the qualification phase using profile CEN WS/BII 3 {BII52} (CWA 17027-117). The invitation to tender provides the possibility to submit a tender and contains the actual call for tender documents. It is captured by the PEPPOL BIS {P013}. In contrast, those economic operators whose qualifications are being rejected by the contracting authority are informed using profile CEN WS/BII 3 {BII51} (CWA 17027-116) reflected by PEPPOL BIS {P012}. +In restricted or negotiated procedures the selection and exclusion criteria for the qualification phase are communicated in a first step to the economic operator by using BIS P002 based on CEN WS/BII 3 {BII60} (CWA 17027-123) and CEN WS/BII 3 {BII47} (CWA 17027-112). The submission of qualification is executed using profile CEN WS/BII 3 {BII49} (CWA 17027-114) covered by PEPPOL BIS {P011}. In restricted and negotiated procedures the contracting body will send an invitation to tender (second step) only to the identified candidates which have been selected after the qualification phase using profile CEN WS/BII 3 {BII52} (CWA 17027-117). The invitation to tender provides the possibility to submit a tender and contains the actual call for tender documents. It is captured by the PEPPOL BIS {P013}. In contrast, those economic operators whose qualifications are being rejected by the contracting body are informed using profile CEN WS/BII 3 {BII51} (CWA 17027-116) reflected by PEPPOL BIS {P012}. -Once the economic operator has received the call for tenders or invitation to tender, it can use the Peppol BIS {P004} for the business process of answering questions about a call for tenders. The BIS P004 is based upon CEN WS/BII3 profile {BII48} (CWA 17027-113) and supports economic operators to clarify open questions until the submission deadline. Answers of the contracting authority then have to be sent to all economic operators that subscribed to the procedure and additionally the call for tenders (or invitation to tender) should be updated and pushed to the (qualified) subscribers of the procedure. +Once the economic operators have received the call for tenders or invitation to tender, they can use the Peppol BIS {P004} for the business process of answering questions about a call for tenders. The BIS P004 is based upon CEN WS/BII3 profile {BII48} (CWA 17027-113) and supports economic operators to clarify open questions until the submission deadline. Answers of the contracting body then have to be sent to all economic operators that subscribed to the procedure and additionally the call for tenders (or invitation to tender) should be updated and pushed to the (qualified) subscribers of the procedure. -In case the economic operator decides to submit a tender, he can use the Peppol BIS {P003}. After the submission of a tender, the contracting body notifies the economic operator of having received the tender. The BIS P003 is based upon CEN WS/BII3 profile {BII54} (CWA 17027-119). On the contrary, economic operators can decide to withdraw a tender (or qualification) that was previously submitted by using the Peppol BIS {P007}. The BIS P007 was derived from CEN WS/BII3 profile {BII53} (CWA 17027-118) and provides electronic messaging support for the economic operator to withdraw a tender. The contracting body notifies the economic operator of having received the tender withdrawal. After the tender withdrawal, an economic operator may submit a new offer at any time before the tender submission deadline. +In case an economic operator decides to submit a tender, he can use the Peppol BIS {P003}. After the submission of a tender, the contracting body notifies the economic operator of having received the tender. The BIS P003 is based upon CEN WS/BII3 profile {BII54} (CWA 17027-119). On the contrary, economic operators can decide to withdraw a tender (or qualification) that was previously submitted by using the Peppol BIS {P007}. The BIS P007 was derived from CEN WS/BII3 profile {BII53} (CWA 17027-118) and provides electronic messaging support for the economic operator to withdraw a tender. The contracting body notifies the economic operator of having received the tender withdrawal. After the tender withdrawal, an economic operator may submit a new offer at any time before the tender submission deadline. -On the opening date, the contracting authority gathers and opens all received tenders. The opening board members can now evaluate the received tenders (or qualifications). If questions about specific offers (or qualifications) arise during the course of the evaluation, they can be answered through the Peppol BIS {P005}. The BIS P005 supports the contracting authority to clarify questions on a tender (or qualification) which has been submitted. The BIS P005 was defined according to the requirements gathered by the CEN WS/BII3 profile {BII50} (CWA 17027-115). +On the opening date, the contracting body gathers and opens all received tenders. The opening board members can now evaluate the received tenders (or qualifications). If questions about specific offers (or qualifications) arise during the course of the evaluation, they can be answered through the Peppol BIS {P005}. The BIS P005 supports the contracting body to clarify questions on a tender (or qualification) which has been submitted. The BIS P005 was defined according to the requirements gathered by the CEN WS/BII3 profile {BII50} (CWA 17027-115). -At the end of the evaluation process, the contracting authority needs to inform the participating economic operators upon the results of the tender evaluation. For this purpose, contracting authorities can use the Peppol BIS {P009} which provides electronic messaging support to inform the bidders that a contract has been awarded. The BIS P009 is based upon the CEN WS/BII3 profile {BII58} (CWA 17027-121). The contracting authority can use BIS {P009} to inform the winner(s) at the same time as they inform the unsuccessful tenderers and they must individually declare the reasons why they failed. The notification of the awarding decision initated by BIS {P009} shall also start the standstill period clock. After the stand still period, the contracting authority can finalize the contract with the winning supplier and also send a contract award notice using BIS Peppol BIS {P008}. +At the end of the evaluation process, the contracting body needs to inform the participating economic operators upon the results of the tender evaluation. For this purpose, the contracting body can use the Peppol BIS {P009} which provides electronic messaging support to inform the bidders that a contract has been awarded. The BIS P009 is based upon the CEN WS/BII3 profile {BII58} (CWA 17027-121). The contracting body can use BIS {P009} to inform the winner(s) at the same time as they inform the unsuccessful tenderers and they must individually declare the reasons why they failed. The notification of the awarding decision initated by BIS {P009} shall also start the standstill period clock. After the stand still period, the contracting body can finalize the contract with the winning supplier and also send a contract award notice using BIS Peppol BIS {P008}. diff --git a/guides/transactions/T019/descriptions/date-time.adoc b/guides/transactions/T019/descriptions/date-time.adoc index ae742c23..81aa10d3 100644 --- a/guides/transactions/T019/descriptions/date-time.adoc +++ b/guides/transactions/T019/descriptions/date-time.adoc @@ -1,7 +1,7 @@ = Date and time -In the tender both the issue date and time must be sent. The issue date and time is indicative. The contracting authority shall reply to the qualification document with a qualification receipt notification where the actual registration date and time for the tender will be indicated. +In the tender both the issue date and time must be sent. The issue date and time is indicative. The contracting body shall reply to the qualification document with a qualification receipt notification where the actual registration date and time for the tender will be indicated. Issue date is xs:date data type, and the date is specified as "YYYY-MM-DD" where: diff --git a/guides/transactions/T019/descriptions/parties.adoc b/guides/transactions/T019/descriptions/parties.adoc index 50aae2dd..8e0ae024 100644 --- a/guides/transactions/T019/descriptions/parties.adoc +++ b/guides/transactions/T019/descriptions/parties.adoc @@ -19,7 +19,8 @@ include::../files/Qualification-doc.xml[tags=MainQualifyingParty] <.> Details to the country of the economic operator, with accompanying code list <.> Further contact details to the economic operator <.> Additional economic operators that belong to a group of economic operators can be added using cac:AdditionalQualifyingParty/cac:Party. -<.> The response to a T19 - Qualification, a T020 - Qualification Reception Confirmation must be returned to the Main Qualifying Party. + +The response to a T19 - Qualification, a T020 - Qualification Reception Confirmation must be returned to the Main Qualifying Party. == Contracting Body diff --git a/guides/transactions/T019/principles/parties-roles.adoc b/guides/transactions/T019/principles/parties-roles.adoc index 9dae5a53..3929ceee 100644 --- a/guides/transactions/T019/principles/parties-roles.adoc +++ b/guides/transactions/T019/principles/parties-roles.adoc @@ -25,7 +25,7 @@ The following parties participate as business partners in this transaction, acti | Role | Description | *Contracting body* -| The Contracting Authority or Contracting Entity who is buying supplies, services or tendering public works. +| The contracting authority or contracting entity who is buying supplies, services or tendering public works. | *Economic operator* | Party participating with a bid in a procurement process to sell goods, services or works. |=== diff --git a/guides/transactions/T019/requirements/index.adoc b/guides/transactions/T019/requirements/index.adoc index 61dce806..69e5b56d 100644 --- a/guides/transactions/T019/requirements/index.adoc +++ b/guides/transactions/T019/requirements/index.adoc @@ -22,7 +22,7 @@ The following table describe the transaction business and information requiremen * Call for tenders ID and version * Procurement Reference number -| tbr86-007 | The message shall contain either credentials issued by the Contracting Body, or the following information about the business: +| tbr86-007 | The message shall contain either credentials issued by the contracting body, or the following information about the business: * Economic operator ID * Economic operator ID type diff --git a/guides/transactions/T022/principles/parties-roles.adoc b/guides/transactions/T022/principles/parties-roles.adoc index 2dac4b21..7ce5bdd0 100644 --- a/guides/transactions/T022/principles/parties-roles.adoc +++ b/guides/transactions/T022/principles/parties-roles.adoc @@ -10,11 +10,11 @@ The following business partners participate in this transaction, acting in the r | Description | Example of roles | *Customer* -| The Customer is the legal person or organization who is in demand of a product or service. -| Examples of customer roles are Buyer, Consignee, Debtor and contracting body. +| The customer is the legal person or organization who is in demand of a product or service. +| Examples of customer roles are buyer, consignee, debtor and contracting body. | *Supplier* -| The Supplier is the legal person or organization who provides a product or service. -| Examples of Supplier roles are Seller, Consignor, Creditor and economic operator. +| The supplier is the legal person or organization who provides a product or service. +| Examples of supplier roles are seller, consignor, creditor and economic operator. |=== @@ -24,7 +24,7 @@ The following business partners participate in this transaction, acting in the r | Role | Description | *Contracting body* -| The Contracting Authority or Contracting Entity who is buying supplies, services or tendering public works. +| The contracting authority or contracting entity who is buying supplies, services or tendering public works. | *Economic operator* | Party participating with a bid in a procurement process to sell goods, services or works. |=== diff --git a/guides/transactions/T023/descriptions/index.adoc b/guides/transactions/T023/descriptions/index.adoc index caa7ad4f..267a2713 100644 --- a/guides/transactions/T023/descriptions/index.adoc +++ b/guides/transactions/T023/descriptions/index.adoc @@ -55,30 +55,30 @@ include::../files/QualificationResponse.xml[tags=IssueDateTime] === Sender Party The party sending a Qualification Response to the party that initiated the request to qualify for a Procurement. -The sender party in this case corresponds to the contracting body. +The sender party corresponds to the contracting body. [source,xml,indent=0] -.Example of sender party +.Example of contracting body as sender party .... include::../files/QualificationResponse.xml[tags=SenderParty] .... -<.> Identifies the sender party's electronic address and the scheme identifier for the electronic address -<.> Identifies the sender party itself and the scheme identifier to resolve sender party's identifier -<.> Contains the sender party's official name. +<.> Identifies the contracting body's electronic address and the scheme identifier for the electronic address +<.> Identifies the contracting body itself and the scheme identifier to resolve sender party's identifier +<.> Contains the contracting body's official name. === Receiver Party The party who is supposed to receive the Qualification Response. This is the same party that initiated the request to qualify for a Procurement. -The receiver party in this case corresponds to the Economic Operator who handed in the Qualification to which this Qualification Response refers to. +The receiver party corresponds to the economic operator who handed in the Qualification to which this Qualification Response refers to. [source,xml,indent=0] -.Example of receiver party +.Example of economic operator as receiver party .... include::../files/QualificationResponse.xml[tags=ReceiverParty] .... -<.> Identifies the receiver party's electronic address and the scheme identifier for the electronic address -<.> Identifies the receiver party and the scheme identifier to resolve the receiver party's identifier -<.> Contains the receiver party's official name including the organization's legal form. +<.> Identifies the economic operator's electronic address and the scheme identifier for the electronic address +<.> Identifies the economic operator and the scheme identifier to resolve the receiver party's identifier +<.> Contains the reconomic operator's official name including the organization's legal form. == Response Document Reference @@ -90,23 +90,23 @@ The Response Document Reference contains a reference to the original Qualificati .... include::../files/QualificationResponse.xml[tags=ResolutionDocumentReference] .... -<.> The Response Document Reference must contain an identifier, being expressed in uuid syntax. +<.> The response document reference must contain an identifier, being expressed in uuid syntax. == Qualification Response Resolution -The Qualification Response Resolution is the central part of any Qualification Response. It contains all information required to inform about the Qualification Rejection. +The qualification response resolution is the central part of any qualification response. It contains all information required to inform about the qualification result (rejected or accepted). -*The Qualification Response Resolution returned with this transaction may be positive or negative*. It is expected to respond every rejection but it is also possible to respond any acceptance. If more than one lot have been aimed to qualify for and need to be responded, one Qualification Response Resolution for each lot is expected. +*The qualification response resolution returned with this transaction may be positive or negative*. It is expected to respond every rejection but it is also possible to respond any acceptance. If more than one lot have been aimed to qualify for and need to be responded, one qualification response resolution for each lot is expected. [source,xml,indent=0] .Example of Qualification Response Resolution .... include::../files/QualificationResponse.xml[tags=QualificationResolution] .... -<.> Gives the qualification result. If the result ist *false*, it states that the Tenderer is not allowed to attend the further Procurement Process and the (generally neutral) qualification response can alo be seen as qualification rejection. Any qualification rejection is required to be answered. A positive answer resulting in *true* may also be given, but is not necessarily requested. -<.> If the decision leading to a Qualification Rejection, the Reason for Rejection can be explained in one or more resolution elements. The Qualification Rejection Resolution is expected be te described in plain text. At least one Reason for Rejection element should be provided. A positive answer may be sent without a specific resolution element. -<.> The Date at which the decision expressed in this Qualification Rejection Resolution was made. -<.> The ProcurementProjectLot referenced in this Qualification Response +<.> Names the qualification result. If the result ist *false*, it states that the economic operator is not allowed to attend the further procurement process and the qualification response can alo be named as qualification rejection. Any qualification rejection is required to be answered. A positive answer resulting in *true* may also be given, but is not necessarily requested. +<.> If the qualification response contains a qualification rejection, the reason for rejection must be explained in one or more resolution elements. The qualification rejection resolution is expected be te described in plain text. At least one reason for rejection element must be provided. A positive answer may be sent without a specific resolution element. +<.> The date at which the decision expressed in this qualification rejection resolution was made. +<.> The ProcurementProjectLot referenced in this qualification response <.> The ProcurementProjectLot's ID diff --git a/guides/transactions/T023/files/QualificationRejection.png b/guides/transactions/T023/files/QualificationResponse.png similarity index 100% rename from guides/transactions/T023/files/QualificationRejection.png rename to guides/transactions/T023/files/QualificationResponse.png diff --git a/guides/transactions/T023/identifiers/index.adoc b/guides/transactions/T023/identifiers/index.adoc index 7c645b71..16fb113c 100644 --- a/guides/transactions/T023/identifiers/index.adoc +++ b/guides/transactions/T023/identifiers/index.adoc @@ -11,6 +11,6 @@ include::../../shared/peppol.adoc[] | `cbc:CustomizationID` | T023 | Qualification Response -| The contracting body sends the Qualification Response to the economic operator that has tendered. +| The contracting body sends the qualification response to the economic operator who applied for qualification. | urn:fdc:peppol.eu:prac:trns:t023:1.0 |=== diff --git a/guides/transactions/T023/identifiers/peppol.adoc b/guides/transactions/T023/identifiers/peppol.adoc index 72b290ee..b244d9f3 100644 --- a/guides/transactions/T023/identifiers/peppol.adoc +++ b/guides/transactions/T023/identifiers/peppol.adoc @@ -9,7 +9,7 @@ The `@type` attribute must be populated in all instances of the ID element when Example of usage in Sender Electronic Address Identifier and Receiver Electronic Address Identifier: [source,xml,indent=0] -.Example of usage of Sender Electronic Address Identifier in `cac:SenderParty` +.Example of using the contracting body's electronic address identifier in `cac:SenderParty` ---- 500820007 @@ -17,7 +17,7 @@ Example of usage in Sender Electronic Address Identifier and Receiver Electronic ---- [source,xml,indent=0] -.Example of usage of Receiver Electronic Address Identifier in `cac:ReceiverParty` +.Example of using the economic operator's electronic address identifier in `cac:ReceiverParty` ---- DE122268496 diff --git a/guides/transactions/T023/principles/parties-roles.adoc b/guides/transactions/T023/principles/parties-roles.adoc index 3728a8ce..4e6f5e48 100644 --- a/guides/transactions/T023/principles/parties-roles.adoc +++ b/guides/transactions/T023/principles/parties-roles.adoc @@ -13,10 +13,10 @@ The following parties participate as business partners in this transaction, acti | Example of roles | *Customer* | The Customer is the legal person or organization who is in demand of a product or service. -| Examples of customer roles are Buyer, Consignee, Debtor and contracting body. +| Examples of customer roles are buyer, consignee, debtor and contracting body. | *Supplier* | The Supplier is the legal person or organization who provides a product or service. -| Examples of Supplier roles are Seller, Consignor, Creditor and economic operator. +| Examples of Supplier roles are seller, consignor, creditor and economic operator. |=== @@ -26,7 +26,7 @@ The following parties participate as business partners in this transaction, acti | Role | Description | *Contracting body* -| The Contracting Authority or Contracting Entity who is buying supplies, services or tendering public works. +| The contracting authority or contracting entity who is buying supplies, services or tendering public works. | *Economic operator* | Party participating with a bid in a procurement process to sell goods, services or works. |===