Final Review of T024 and Updating parts of T004 and T024

OpenPEPPOL · Sep 19, 2023 · a9ff4c5 · a9ff4c5
1 parent 2fa8647
commit a9ff4c5
Show file tree

Hide file tree

Showing 16 changed files with 126 additions and 57 deletions.
diff --git 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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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
@@ -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]