diff --git a/guides/profiles/p013/codes/peppol.adoc b/guides/profiles/p013/codes/peppol.adoc index 1ab07f58..2291db00 100644 --- a/guides/profiles/p013/codes/peppol.adoc +++ b/guides/profiles/p013/codes/peppol.adoc @@ -8,7 +8,7 @@ PEPPOL has defined a Policy for Using Identifiers that specifies how to use iden All transactions within this profile uses the following profile identifier The value of the *Element* `cbc:ProfileID` for all transactions of this profile must be -_urn:fdc:peppol.eu:prac:bis:p013:1.2_ +_urn:fdc:peppol.eu:prac:bis:p013:1.0_ == Specification identification diff --git a/guides/profiles/p013/introduction.adoc b/guides/profiles/p013/introduction.adoc index 6011e216..51e5c89d 100644 --- a/guides/profiles/p013/introduction.adoc +++ b/guides/profiles/p013/introduction.adoc @@ -2,7 +2,7 @@ [preface] = Introduction to openPEPPOL and BIS -This {link-peppol} BIS provides a set of specifications for implementing a {link-peppol} business process. The document is concerned with clarifying requirements for ensuring interoperability of pan-European Public eProcurement and provides guidelines for the support and implementation of these requirements. This document is based on work done by the {link-esens} pilot project as well as work done by {link-bii3}. +This {link-peppol} BIS provides a set of specifications for implementing a {link-peppol} business process. The document is concerned with clarifying requirements for ensuring interoperability of pan-European Public eProcurement and provides guidelines for the support and implementation of these requirements. This document is based on work done by {link-bii3}. .Relationship between BII profiles and PEPPOL BIS image::../../../shared/images/BII_relationship.png[align="center", width=600] @@ -11,10 +11,10 @@ The {name-profile} describes electronic messaging support for the business proce The key aspects covered by this profile are: -* The contracting body has decided to invite an economic operator to participate in a tendering procedure, sending the invitation to tender. -* The contracting body makes the Invitation to tender document available to the economic operator +* The contracting body has decided to invite an economic operator to participate in a tendering procedure, sending the Invitation to Tender (ItT). +* The contracting body makes the Invitation to Tender document available to the economic operator. * The economic operator decides whether he participates in the tendering process, but no communication needs to be sent back to the contracting body if he decides not to. -* After having received the invitation to tender, an economic operator can request the status of the procurement project from the contracting body, who provides the economic operator with the latest procurement project call for tender. +* After having received the Invitation to Tender, an economic operator can request the status of the procurement project from the contracting body at any time. The contracting body provides the economic operator with the latest procurement project call for tender documents using the Invitation to Tender message. In this {name-profile}, most information about the call for tenders is defined in (unstructured) attachments. The purpose of this document is to facilitate an efficient implementation and increased use of electronic collaboration regarding the tendering process based on these formats. diff --git a/guides/profiles/p013/principles/encryption-certificate.adoc b/guides/profiles/p013/principles/encryption-certificate.adoc index 8b92c277..0f41caa5 100644 --- a/guides/profiles/p013/principles/encryption-certificate.adoc +++ b/guides/profiles/p013/principles/encryption-certificate.adoc @@ -1,6 +1,6 @@ // TODO adapt to Invitation for Tender = Transport of encryption certificate via the Call For Tenders -The Invitation To Tender (ItT) 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 tender for submission. The method how to include the Encryption Certificates is described in link:/pracc/transactions/T024/index.html[T024 - section 6.5. Transport of encryption certificate via the Invitation to Tender]. +The Invitation to Tender business document is used by the contracting authority to provide an economic operator with the procurement documents. Besides transporting procurement documents it MUST be used to transport the encryption certificate needed by the economic operator to encrypt his tender for submission. The method how to include the encryption certificate is described in link:/pracc/transactions/T024/index.html[T024 - section 6.5. Transport of encryption certificate via the Invitation to Tender]. diff --git a/guides/profiles/p013/principles/non-functional-requirements.adoc b/guides/profiles/p013/principles/non-functional-requirements.adoc index ce09dd2c..6c7996fa 100644 --- a/guides/profiles/p013/principles/non-functional-requirements.adoc +++ b/guides/profiles/p013/principles/non-functional-requirements.adoc @@ -1,7 +1,7 @@ // TODO adapt to Invitation for Tender = Non-functional requirements -For the {link-peppol} BIS all {link-peppol} non-functional requirements are applicable as mentioned on {link-profile}. When adopting the {link-peppol} BIS implementers must comply to these requirements. +For the {link-peppol} BIS the following non-functional requirements are applicable as mentioned on {link-profile}. When adopting the {link-peppol} BIS implementers must comply to these requirements. [cols="2,10", options="header"] |=== diff --git a/guides/profiles/p013/process/implementation-guidelines.adoc b/guides/profiles/p013/process/implementation-guidelines.adoc index a12a42b4..81a813ab 100644 --- a/guides/profiles/p013/process/implementation-guidelines.adoc +++ b/guides/profiles/p013/process/implementation-guidelines.adoc @@ -10,11 +10,12 @@ The syntax mapping for {name-profile} has been tested and revised during the {li * {link-profile} * {link-profile2} * {sig-cft} -* {tender-status} * {call-for-tenders} +* {tender-status} + {link-peppol} {name-profile} business process includes 2 transactions: * link:../../transactions/T024/index.html[T024 Invitation To Tender] -* link:../../transactions/T003/index.html[T003 Invitation To Tender Status Inquiry] +* link:../../transactions/T003/index.html[T003 Tender Status Inquiry] diff --git a/guides/profiles/p013/process/index.adoc b/guides/profiles/p013/process/index.adoc index c545cc5a..ff709abd 100644 --- a/guides/profiles/p013/process/index.adoc +++ b/guides/profiles/p013/process/index.adoc @@ -13,7 +13,7 @@ image::../images/InvitationToTender.svg[align="center", width=800] | Description | Description | The contracting body sends an electronic Invitation to Tender document containing the information required for the economic operator to participate in a tendering process. -The contracting body may send a formal Invitation to Tender as an attachment to the Invitation to Tender document. +The contracting body may send a formal Invitation to Tender letter as an attachment to the Invitation to Tender message. The economic operator evaluates the information given with the Invitation to Tender and decides whether to submit an tender or not. If the economic operator accepts the invitation and submits a tender the business process continuous through the external process Tender Submission. If the economic operator rejects the invitation, no notification needs to be sent back to the contracting body. @@ -25,7 +25,7 @@ If the economic operator rejects the invitation, no notification needs to be sen | The economic operator has received the Invitation to Tender and can proceed to prepare and submit the tender. | Remarks -| The Invitation to Tender is typically used in negotiated procedure and restricted procedures where the economic operator could not view the call for tenders information and a list of selected economic operators is created at a first step. +| The Invitation to Tender is typically used in negotiated procedure and restricted procedures where the economic operator could not view the call for tenders information and a list of selected/qualified economic operators is created at a first step. |=== @@ -42,13 +42,13 @@ If the economic operator rejects the invitation, no notification needs to be sen | The economic operator receives the Invitation to Tender, enabling him to prepare a bid. | Send Invitation to Tender Status Inquiry | Economic Operator -| The economic operator (regularly) asks for Tender Document Status changes. +| The economic operator (regularly) asks for status changes of the procurement documents. | Receive Invitation to Tender Status Inquiry | Contracting body | The contracting body receives an Invitation to Tender status update request from the Economic operator. | Sent current version of the Invitation to Tender | Contracting body -| The contracting body sents the current version of the to the Economic operator. +| The contracting body sents the current version of the Invitation to Tender to the Economic operator. |=== diff --git a/guides/shared/interoperability.adoc b/guides/shared/interoperability.adoc index 0d7921e6..9f2cac7b 100644 --- a/guides/shared/interoperability.adoc +++ b/guides/shared/interoperability.adoc @@ -22,8 +22,8 @@ It applies the Framework as follows: * Organization (Process): ** {link-bis} support a set of “common business processes” that are assumed to be supported by most enterprises whether public or private. These are processes that are used widely or understood as being relevant for most companies. -** The current scope of the {link-bis} and guidelines include processes that support the flow of open procedures and restricted procedures such publication of notices, search of notices, calls for tenders, tenders and awarding notifications. During these processes additional support processes may be executed between contracting bodies and economic operators, such as procurement procedure subscription, call for tenders’ questions and answers, tender withdrawal or tender clarifications. Specific processes like qualification, qualification rejection and invitation to tender are required for the implementation of restricted procedures. -** The {link-OpenProcedure} describes the choreography to execute open procedures using Peppol. Thus, the Notification & Open Procedure Guideline is a procedural specification. The guideline does not define individual transactions but it refers to Peppol several BISs and underlying standards, in which the transactions and the transaction information requirements are listed and defined. Even though the guideline is based on a set of PEPPOL BISs, its contents are derived from the agreement {BII37} of the CEN Workshop on Business Interoperability Interfaces for Public Procurement in Europe . +** The current scope of the {link-bis} and guidelines include processes that support the flow of open procedures and restricted procedures such publication of notices, search of notices, calls for tenders, tenders and awarding notifications. During these processes additional support processes may be executed between contracting bodies and economic operators, such as procurement procedure subscription, call for tenders’ questions and answers, tender withdrawal or tender clarifications. Specific processes like qualification, qualification rejection and invitation to tender are required for the implementation of restricted or negotiated procedures. +** The {link-OpenProcedure} describes the choreography to execute open procedures using Peppol. Thus, the Notification & Open Procedure Guideline is a procedural specification. The guideline does not define individual transactions but it refers to several Peppol BISs and its underlying standards, in which the transactions and the transaction information requirements are listed and defined. Even though the guideline is based on a set of PEPPOL BISs, its contents are derived from the agreement {BII37} of the CEN Workshop on Business Interoperability Interfaces for Public Procurement in Europe . diff --git a/guides/shared/links.adoc b/guides/shared/links.adoc index e029e5b9..09111870 100644 --- a/guides/shared/links.adoc +++ b/guides/shared/links.adoc @@ -4,7 +4,7 @@ :link-peppol: https://peppol.org/[Peppol] :link-bis: https://docs.peppol.eu/pracc/[PEPPOL eTendering BIS] :link-common: https://peppol.org/[Peppol] -:preaward-cat: https://docs.peppol.eu/pracc/catalogue/1.0/bis/[BIS pre-award catalogue] +:preaward-cat: https://docs.peppol.eu/pracc/catalogue/1.0/bis/[P035 Pre-Award Catalogue] //PEPPOL BIS Preaward :P001: https://docs.peppol.eu/pracc/profiles/p001/index.html[P001 Procurement procedure subscription] diff --git a/guides/shared/tendering.adoc b/guides/shared/tendering.adoc index 6156b2fc..2d3915fb 100644 --- a/guides/shared/tendering.adoc +++ b/guides/shared/tendering.adoc @@ -27,20 +27,22 @@ For the purpose of initiating electronic tendering via Peppol, the Peppol BIS {P 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). -In open procedures, any economic operator can access the tender documents (including the call for tenders) and submit a tender before the time expires, without any previous assessment of their capabilities. In restricted and negotiated procedures and in a competitive dialogue the interested economic operators must submit a request to participate in order to be invited in the tendering process by the contracting body. 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}. +In open procedures, any economic operator can access the call for tenders documents and submit a tender before the time expires, without any previous assessment of their capabilities. In restricted and negotiated procedures and in a competitive dialogue the interested economic operators must submit a request to participate in order to be invited in the tendering process by the contracting body. + +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. -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 {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 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}. -Restricted and negotiated procedures require a qualification phase using profile CEN WS/BII 3 {BII49} (CWA 17027-114) covered by PEPPOL BIS {P011} before submitting a tender. The selection and exclusion criteria for the qualification phase are beforehand communicated 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). In restricted and negotiated procedures the contracting authority will send an invitation to tender using profile CEN WS/BII 3 {BII52} (CWA 17027-117) to the identified candidates which have been selected after the qualification phase to submit a tender. The invitation to tender is captured by the PEPPOL BIS {P013}. In contrast, those economic operators whose qualifications are being rejected 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 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}. -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 asking questions about call for tenders. 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 should be updated and pushed to the subscribers of the procedure. +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. -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 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 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. -On the opening date, the contracting authority gathers and opens all received tenders. The opening board members can now evaluate the received tenders. If questions about specific offers 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 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 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). -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 to a particular economic operator. 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 imitated 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 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}. diff --git a/guides/transactions/T004/descriptions/attachment.adoc b/guides/transactions/T004/descriptions/attachment.adoc index 5abbb1dc..ea635dc3 100644 --- a/guides/transactions/T004/descriptions/attachment.adoc +++ b/guides/transactions/T004/descriptions/attachment.adoc @@ -1,16 +1,12 @@ = Description of the attachment of documents -Using this transaction, the information of the tendering process and the details of the procurement project are described in unstructured files. The call for tenders reference the unstructured files so it is possible to access them through their URI. +Using this transaction, the information of the tendering process and the details of the procurement project are described in unstructured files. The call for tenders reference the unstructured files. Thus, it is possible to access them in the ASiC-E Container (see {link-eDocument}). -The `cac:AdditionalDocumentReference` class contains references to all the files for the tenderers to prepare their bids. The mandatory `cbc:ID` element contains an identifier of the file, and the `cac:DocumentStatusCode` is used to inform the tenderers about the action that has to be done with the current document. +The `cac:AdditionalDocumentReference` class contains references to all the files for the tenderers to prepare their bids. The mandatory `cbc:ID` element contains an identifier of the file, and the `cac:DocumentStatusCode` is used to inform the tenderers about the action that has to be done with the current document. If a `cac:Attachment` is provided, the `cac:ExternalReference` shall contain the `cbc:FileName` and `cbc:MimeCode` using defined media types of e.g.link:ftp://ftp.cen.eu/public/CWAs/BII2/CWA16558/CWA16558-Annex-G-BII-CodeLists-V2_0_4.pdf[IANA] -Find below an example on how to define a document reference that provides a document for reading purposes only. - -In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the coded values of `documentTypeCode`: +Find below an example on how to define a document reference that provides a document that is provided by the contracting authority and must not be returned. In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the coded values of `documentTypeCode`: * The code `Provided` or `Pro` is used to indicate that a document is provided as part of an Invitation to Tender or tender. It must include a physical attachment. The value `No Return (NR)` of the codelist `documentStatusCode` indicates that the document must not be returned during the bid or tender (e.g. the encryption certificate to encrypt a tender) -* The code `Required` or `Req` is used to indicate that a document must be created by the economic operator as part of the bid or tender (e.g. a template that need to be filled). As documents that are classified as `Required` must be returned, they cannot use the value `No Return (NR)` of the codelist `documentStatusCode`. The remaining values of that codelist however, could indicate that document MUST be returned but no signature is required (e.g. `Return without signature (RWOS)`) or that an advanced signature is required. - [source,xml,indent=0] .Additional document reference @@ -19,3 +15,19 @@ In this example, the contents of the coded elements DocumentTypeCode and Documen include::../{xml-doc-file}[tags=AdditionalDocumentReference2] ---- + +In contrast to this a document reference could be also established as follows: + +* The code `Required` or `Req` is used to indicate that a document must be created by the economic operator and submitted as part of the bid or tender. It therefore does not use the component `cac:Attachment`. As documents that are classified as `Required` must be returned, they cannot use the value `No Return (NR)` of the codelist `documentStatusCode`. The remaining values of that codelist however, could indicate that document MUST be returned but no signature is required (e.g. `Return without signature (RWOS)`) or that an advanced signature is required. + +---- +include::../{xml-doc-file}[tags=AdditionalDocumentReference5] + +---- + +Another example shows how the contracting authority may provide a document template for product classification and pricing that needs to be filled out and returned by the economic operator. + +---- +include::../{xml-doc-file}[tags=AdditionalDocumentReference6] + +---- diff --git a/guides/transactions/T004/descriptions/transport-encryption.adoc b/guides/transactions/T004/descriptions/transport-encryption.adoc index bb38d02b..156e6d4f 100644 --- a/guides/transactions/T004/descriptions/transport-encryption.adoc +++ b/guides/transactions/T004/descriptions/transport-encryption.adoc @@ -3,15 +3,15 @@ == Introduction -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 tender for submission. +The Call For Tenders 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 tender for submission. == Encryption certificate -The encryption certificate MUST be transported as an attachment within the Call For Tenders ASIC. The Call For Tenders business document contains metadata regarding all attachments thus also for the tender encryption certificate. +The encryption certificate MUST be transported as an attachment within the Call For Tenders ASiC-E Container. The Call For Tenders business document contains metadata regarding all attachments thus also for the tender encryption certificate. -This metadata is resembled by the UBL container cac:AdditionalDocumentReference. In the case of the encryption certificate this container MUST contain the elements and values mentioned in the table below. +The encryption certificate metadata is assembled by the UBL container `cac:AdditionalDocumentReference`. In the case of the encryption certificate this container MUST contain the elements and values mentioned in the table below. -To identify the encryption certificate, the UBL MUST contain exactly one AdditionalDocumentReference-container as described below. Any other container MUST NOT make use of this value combination. +To identify the encryption certificate, the UBL MUST contain exactly one `cac:AdditionalDocumentReference`-container as described below. Any other container MUST NOT make use of this value combination. [cols="3,2,3,4", options="header"] |=== @@ -20,13 +20,13 @@ To identify the encryption certificate, the UBL MUST contain exactly one Additio | Required document reference identifier | 1..1 | cbc:ID | Reference identifier of a document that is provided as part of a tender or call for tenders. Value supplied by tendering system of the CA. Is not necessarily populated with the filename but rather an internal identifier. | Document issue date | 0..1 | cbc:IssueDate |The date on which the tender encryption key has been issued. -| Document type code | 1..1 | cbc:DocumentTypeCode | Fixed value of “PROVIDED” +| Document type code | 1..1 | cbc:DocumentTypeCode | Fixed value of “PRO” for "Provided" | | | cbc:DocumentTypeCode/@listID | Fixed value of "urn:eu:esens:cenbii:documentType" | Provided document version | 0..1 | cbc:VersionID | Version of a document that is provided as part of a tender or call for tenders. -| Provided document to be returned indicator | 1..1 | cbc:DocumentStatusCode | Fixed value of “NO RETURN” -| | | cbc:DocumentStatusCode/@listID | Fiexd value of "urn:eu:esens:cenbii:documentStatusType" +| Provided document to be returned indicator | 1..1 | cbc:DocumentStatusCode | Fixed value of "NR" for “NO RETURN” +| | | cbc:DocumentStatusCode/@listID | Fixed value of "urn:eu:esens:cenbii:documentStatusType" | Document mime type code | 1..1 | cac:Attachment/cac:ExternalReference/cbc:MimeCode | Fixed value of "application/pkix-cert". -| Provided document name | 1..1 | cac:Attachment/cac:ExternalReference/cbc:FileName | Name of a document that is provided as part of a tender or call for tenders. The extension of the file MUST be “cer”. +| Provided document name | 1..1 | cac:Attachment/cac:ExternalReference/cbc:FileName | Name of a document that is provided as part of a tender or call for tenders. The extension of the file MUST be “.cer”. |=== Instead of `Provided document name`, alternatively a `Provided document URI` could be used to reference the encryption certificate. diff --git a/guides/transactions/T004/files/call-for-tenders-instance-doc.xml b/guides/transactions/T004/files/call-for-tenders-instance-doc.xml index 7e5a9c80..c1359fa8 100644 --- a/guides/transactions/T004/files/call-for-tenders-instance-doc.xml +++ b/guides/transactions/T004/files/call-for-tenders-instance-doc.xml @@ -40,17 +40,38 @@ - Bekanntmachung + ContractNotice 2016-10-20+02:00 PRO NR - bekanntmachung.html + application/xml + ContractNotice.xml + + + ISO 27001 Certificate + REQ + RWOS + + + + + Product classification and pricing + 2016-10-20+02:00 + PRO + RWOS + + + ProductDescriptionTemplate.xlsx + + + + DE122268496 diff --git a/guides/transactions/T024/descriptions/attachment.adoc b/guides/transactions/T024/descriptions/attachment.adoc index 530d8a31..68361ae1 100644 --- a/guides/transactions/T024/descriptions/attachment.adoc +++ b/guides/transactions/T024/descriptions/attachment.adoc @@ -1,16 +1,12 @@ = Description of the attachment of documents -Using this transaction, the information of the tendering process and the details of the procurement project are described in unstructured files. The Invitation to Tender reference the unstructured files so it is possible to access them through their URI. +Using this transaction, the information of the tendering process and the details of the procurement project are described in unstructured files. The Invitation to Tender reference the unstructured files. Thus, it is possible to access them in the ASiC-E Container (see {link-eDocument}). -The `cac:AdditionalDocumentReference` class contains references to all the files for the tenderers to prepare their bids. The mandatory `cbc:ID` element contains an identifier of the file, and the `cac:DocumentStatusCode` is used to inform the tenderers about the action that has to be done with the current document. +The `cac:AdditionalDocumentReference` class contains references to all the files for the tenderers to prepare their bids. The mandatory `cbc:ID` element contains an identifier of the file, and the `cac:DocumentStatusCode` is used to inform the tenderers about the action that has to be done with the current document. If a `cac:Attachment` is provided, the `cac:ExternalReference` shall contain the `cbc:FileName` and `cbc:MimeCode` using defined media types of e.g.link:ftp://ftp.cen.eu/public/CWAs/BII2/CWA16558/CWA16558-Annex-G-BII-CodeLists-V2_0_4.pdf[IANA] -Find below an example on how to define a document reference that provides a document for reading purposes only. - -In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the coded values of `documentTypeCode`: +Find below an example on how to define a document reference that provides a document that is provided by the contracting authority and must not be returned. In this example, the contents of the coded elements DocumentTypeCode and DocumentStatusCode have been defined following the coded values of `documentTypeCode`: * The code `Provided` or `Pro` is used to indicate that a document is provided as part of an Invitation to Tender or tender. It must include a physical attachment. The value `No Return (NR)` of the codelist `documentStatusCode` indicates that the document must not be returned during the bid or tender (e.g. the encryption certificate to encrypt a tender) -* The code `Required` or `Req` is used to indicate that a document must be created by the economic operator as part of the bid or tender (e.g. a template that need to be filled). As documents that are classified as `Required` must be returned, they cannot use the value `No Return (NR)` of the codelist `documentStatusCode`. The remaining values of that codelist however, could indicate that document MUST be returned but no signature is required (e.g. `Return without signature (RWOS)`) or that an advanced signature is required. - [source,xml,indent=0] .Additional document reference @@ -19,3 +15,19 @@ In this example, the contents of the coded elements DocumentTypeCode and Documen include::../{xml-doc-file}[tags=AdditionalDocumentReference2] ---- + +In contrast to this a document reference could be also established as follows: + +* The code `Required` or `Req` is used to indicate that a document must be created by the economic operator and submitted as part of the bid or tender. It therefore does not use the component `cac:Attachment`. As documents that are classified as `Required` must be returned, they cannot use the value `No Return (NR)` of the codelist `documentStatusCode`. The remaining values of that codelist however, could indicate that document MUST be returned but no signature is required (e.g. `Return without signature (RWOS)`) or that an advanced signature is required. + +---- +include::../{xml-doc-file}[tags=AdditionalDocumentReference5] + +---- + +Another example shows how the contracting authority may provide a document template for product classification and pricing that needs to be filled out and returned by the economic operator. + +---- +include::../{xml-doc-file}[tags=AdditionalDocumentReference6] + +---- \ No newline at end of file diff --git a/guides/transactions/T024/descriptions/tendering-process.adoc b/guides/transactions/T024/descriptions/tendering-process.adoc index d13fd2ea..055b1609 100644 --- a/guides/transactions/T024/descriptions/tendering-process.adoc +++ b/guides/transactions/T024/descriptions/tendering-process.adoc @@ -4,8 +4,8 @@ The Invitation to Tender describes some information of the tendering process. The `cac:TenderingProcess` class contains the deadlines of the process and the codes describing the type of procedure, the contract type and the type of submission. -The example below describes an open procedure and the deadlines of the process. The `cbc:ProcedureCode` and the tender submission end date are required data elements. -The `cac:TenderingProcess` class contains information about the type of contract that will be established by setting one of the given codes at `cbc:ContractingSystemCode`. +The example below describes a restricted procedure, `cbc:ProcedureCode` = 2 (Restricted procedure), and the deadlines of the process. The `cbc:ProcedureCode` and the tender submission end date are required data elements. +The `cac:TenderingProcess` class also contains information about the type of contract that will be established by setting one of the given codes at `cbc:ContractingSystemCode`. In this case, `cbc:ContractingSystemCode` = 5, a public contract based on a Dynamic Purchasing System shall be established. [source,xml,indent=0] diff --git a/guides/transactions/T024/descriptions/transport-encryption.adoc b/guides/transactions/T024/descriptions/transport-encryption.adoc index a60b3dc3..444a9c31 100644 --- a/guides/transactions/T024/descriptions/transport-encryption.adoc +++ b/guides/transactions/T024/descriptions/transport-encryption.adoc @@ -3,17 +3,17 @@ == Introduction -The Invitation to Tender (ItT) business document is used by the contracting authority to provide a qualified economic operator with the latest updated procurement documents. Sending the Invitation to Tender to any of the remaining economic operators determines the second step of the restricted procurement procedure. Besides transporting procurement documents it MUST be used to transport the encryption certificate needed by the economic operator to encrypt his tender for submission. +The Invitation to Tender provides the latest updated procurement documents to a qualified economic operator. Sending the Invitation to Tender to an economic operators starts the second step of the restricted procurement procedure. Besides transporting procurement documents it MUST be used to transport the encryption certificate needed by the economic operator to encrypt his tender for submission. Since the Invitation to Tender is also used to sent out business document changes after a {T003} (by sending a status-update-inquiry), any Invitation to Tender MUST contain the encryption certificate needed by the economic operator to encrypt his tender for submission. == Encryption certificate -The encryption certificate MUST be transported as an attachment within the Invitation to Tender's'ASIC. The Invitation to Tender business document contains metadata regarding all attachments thus also for the tender encryption certificate. +The encryption certificate MUST be transported as an attachment within the Invitation to Tender's ASiC-E Container. The Invitation to Tender business document contains metadata regarding all attachments thus also for the tender encryption certificate. -This metadata is resembled by the UBL container cac:AdditionalDocumentReference. In the case of the encryption certificate this container MUST contain the elements and values mentioned in the table below. +This encryption certificate metadata is assembled by the UBL container `cac:AdditionalDocumentReference`. In the case of the encryption certificate this container MUST contain the elements and values mentioned in the table below. -To identify the encryption certificate, the UBL MUST contain exactly one AdditionalDocumentReference-container as described below. Any other container MUST NOT make use of this value combination. +To identify the encryption certificate, the UBL MUST contain exactly one `cac:AdditionalDocumentReference`-container as described below. Any other container MUST NOT make use of this value combination. [cols="3,2,3,4", options="header"] |=== @@ -22,13 +22,13 @@ To identify the encryption certificate, the UBL MUST contain exactly one Additio | Required document reference identifier | 1..1 | cbc:ID | Reference identifier of a document that is provided as part of a tender or call for tenders. Value supplied by tendering system of the CA. Is not necessarily populated with the filename but rather an internal identifier. | Document issue date | 0..1 | cbc:IssueDate |The date on which the tender encryption key has been issued. -| Document type code | 1..1 | cbc:DocumentTypeCode | Fixed value of “PROVIDED” +| Document type code | 1..1 | cbc:DocumentTypeCode | Fixed value of “PRO” for "Provided" | | | cbc:DocumentTypeCode/@listID | Fixed value of "urn:eu:esens:cenbii:documentType" | Provided document version | 0..1 | cbc:VersionID | Version of a document that is provided as part of a tender or call for tenders. -| Provided document to be returned indicator | 1..1 | cbc:DocumentStatusCode | Fixed value of “NO RETURN” -| | | cbc:DocumentStatusCode/@listID | Fiexd value of "urn:eu:esens:cenbii:documentStatusType" +| Provided document to be returned indicator | 1..1 | cbc:DocumentStatusCode | Fixed value of "NR" for “NO RETURN” +| | | cbc:DocumentStatusCode/@listID | Fixed value of "urn:eu:esens:cenbii:documentStatusType" | Document mime type code | 1..1 | cac:Attachment/cac:ExternalReference/cbc:MimeCode | Fixed value of "application/pkix-cert". -| Provided document name | 1..1 | cac:Attachment/cac:ExternalReference/cbc:FileName | Name of a document that is provided as part of a tender or call for tenders. The extension of the file MUST be “cer”. +| Provided document name | 1..1 | cac:Attachment/cac:ExternalReference/cbc:FileName | Name of a document that is provided as part of a tender or call for tenders. The extension of the file MUST be “.cer”. |=== Instead of `Provided document name`, alternatively a `Provided document URI` could be used to reference the encryption certificate. diff --git a/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml b/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml index 2c3f8ea8..92f0db72 100644 --- a/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml +++ b/guides/transactions/T024/files/invitation-to-tender-instance-doc.xml @@ -51,6 +51,27 @@ + + + ISO 27001 Certificate + REQ + RWOS + + + + + Product classification and pricing + 2016-10-20+02:00 + PRO + RWOS + + + application/vnd.ms-excel + ProductDescriptionTemplate.xlsx + + + + DE122268496