Review of Profile P013

OpenPEPPOL · Sep 17, 2023 · c8732e4 · c8732e4
1 parent 3ec31a1
commit c8732e4
Show file tree

Hide file tree

Showing 14 changed files with 51 additions and 58 deletions.
diff --git a/guides/profiles/p002/principles/encryption-certificate.adoc b/guides/profiles/p002/principles/encryption-certificate.adoc
@@ -1,4 +1,4 @@
 
 = Transport of encryption certificate via the Call For Tenders
 
-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 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 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/T004/index.html[T004 - section  6.5. Transport of encryption certificate via the Call For Tenders].
diff --git a/guides/profiles/p009/principles/parties-roles.adoc b/guides/profiles/p009/principles/parties-roles.adoc
@@ -1,4 +1,4 @@
-
+__
 = Parties and roles
 
 

diff --git a/guides/profiles/p013/codes/peppol.adoc b/guides/profiles/p013/codes/peppol.adoc
@@ -20,22 +20,16 @@ In the table below you will find the values to be used as the specification iden
 
 | TransactionID | Transaction name | Short Description | *Element* `cbc:CustomizationID`
 
+| T024
+| Invitation to Tender
+| CA sends an Invitation to Tender to the EO
+| _urn:fdc:peppol.eu:prac:trns:t024:1.0_
+
 | T003
-| TenderStatusRequest
-| EO requests CA for the procurement project documents
+| Tender Status Inquiry
+| EO requests CA for the latest procurement project documents
 | _urn:fdc:peppol.eu:prac:trns:t003:1.2_
 
-
-| T004
-| CallForTenders here knows as InvitationToTender
-| CA sends all procurement project documents to the formerly chosen EOs
-| _urn:fdc:peppol.eu:prac:trns:t004:1.2_
-
-| T013
-| TenderWithdrawal
-| EO resigns from participating in tendering process
-| _urn:fdc:peppol.eu:prac:trns:t013:1.2_
-
 |===
 
 [NOTE]

diff --git a/guides/profiles/p013/links.adoc b/guides/profiles/p013/links.adoc
@@ -2,9 +2,9 @@ include::../../shared/links.adoc[]
 
 include::settings.adoc[]
 
-:link-profile: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:62055&cs=1FA2AB7C9A0F601605C549112B7B93DA3[{name-profile-org}]
-//:link-profile2: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:62029&cs=16BDCBBEBAE1A6A235013E1B31A0B78D6[{name-profile-org}]
-:sig-cft: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:62060&cs=1D0ACDA2A9232666E1F4196153554FD0A[UBL Syntax Implementation Guideline for Trdm083 Call for Tenders (CWA 17027-216)]
+:link-profile: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:62034&cs=14EBEB82D050E426BA2F37CC537677DFB[{name-profile-org}]
+:link-profile2: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:62055&cs=1FA2AB7C9A0F601605C549112B7B93DA3[{name-profile-org2}]
+:sig-cft: UBL Syntax Implementation Guideline for Trdm088 Invitation to Tender (CWA 17027-216)
 :tender-status: http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.html#S-TENDER-STATUS-SCHEMA[UBL Tender Status Schema]
 :call-for-tenders: http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.html#S-CALL-FOR-TENDERS-SCHEMA[UBL Call for Tenders Schema]
 
diff --git a/guides/profiles/p013/principles/encryption-certificate.adoc b/guides/profiles/p013/principles/encryption-certificate.adoc
@@ -1,4 +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/T004/index.html[T004 - section  5.5. 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].
+
+
diff --git a/guides/profiles/p013/principles/non-functional-requirements.adoc b/guides/profiles/p013/principles/non-functional-requirements.adoc
@@ -6,11 +6,10 @@ For the {link-peppol} BIS all {link-peppol} non-functional requirements are appl
 [cols="2,10", options="header"]
 |===
 | Req. ID | Requirement statement
-| br52-001 | The contracting body decides to invite a reduced number of candidates based on a previous selection (either based on a pre-qualification business process or on a pre-selection list based on other criteria). In open procedures economic operators may access to all contract documents .
-| br52-002 | The contracting body prepares the Invitation to tender as a structured document and optionally an unstructured Invitation to Tender and sends it to the pre-selected economic operators.
+| br52-001 | The contracting body decides to invite a reduced number of candidates based on a previous selection (either based on a pre-qualification business process or on a pre-selection list based on other criteria).
+| br52-002 | The contracting body prepares the Invitation to tender and sends it to the pre-selected economic operators.
 | br52-003 | The economic operator receives and evaluates the Invitation to tender and decides whether to participate or not in the tendering process.
 | br52-004 | It is the responsibility of the contracting body that data contained in the transactions is valid from a technical as well as a business point of view.
-| br52-006 | The Invitation to tender may include an (unstructured) ESPD template.
-| br52-007 | The Invitation to tender metadata must be consistent with the Contract Notice metadata.
-| br52-008 | An economic operator who subscribed to the procedure must be informed when an addendum to the Invitation to tender is published and always be able to get the latest version of the Invitation to tender.
+| br52-007 | The Invitation to tender must be consistent with the Contract Notice and Call for Tender metadata.
+| br52-008 | An economic operator who subscribed to the procedure must be informed when an addendum to the Invitation to tender is published and always be able to get the latest version of the Invitation to tender using the Tender Status Inquiry.
 |===
diff --git a/guides/profiles/p013/process/implementation-guidelines.adoc b/guides/profiles/p013/process/implementation-guidelines.adoc
@@ -5,7 +5,7 @@
 urn:oasis:names:specification:ubl:schema:xsd:InvitationToTender-2
 urn:oasis:names:specification:ubl:schema:xsd:TenderStatusRequest-2
 
-The syntax mapping for {name-profile} has been tested and revised during the {link-esens} pilot and is based on transaction description for Tender Status Inquiry (Trdm097) and  Call for Tenders (Trdm083) done by {link-bii3}. Requirements, business rules and code lists used are inherited from the following documents:
+The syntax mapping for {name-profile} has been tested and revised during the {link-esens} pilot and is based on transaction description for Tender Status Inquiry (Trdm097) and  Invitation to Tender (Trdm088) done by {link-bii3}. Requirements, business rules and code lists used are inherited from the following documents:
 
 * {link-profile}
 * {link-profile2}

diff --git a/guides/profiles/p013/process/index.adoc b/guides/profiles/p013/process/index.adoc
@@ -12,20 +12,20 @@ image::../images/InvitationToTender.svg[align="center", width=800]
 | Category
 | 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 economic operator evaluates the information given with the invitation to tender and decides whether to accept the invitation or to reject it.
-If the economic operator accepts the invitation, the business process follows through an external process.
+| 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 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.
 
 | Pre-conditions
-| The contracting body had pre-selected a list of candidate economic operators (shortlist).
+| The contracting body has pre-selected a list of candidate economic operators (shortlist).
 
 | Post-conditions
-| The economic operator has received the invitation to tender and can proceed to prepare and submit the qualification or tender.
+| The economic operator has received the Invitation to Tender and can proceed to prepare and submit the tender.
 
 | Remarks
-| The invitation to tender is used in a negotiated procedure to submit the tender documents to a list of preselected economic operators.
+| 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.
 |===
 
 
@@ -34,16 +34,21 @@ If the economic operator rejects the invitation, no notification needs to be sen
 | Activity
 | Role involved
 | Description
-| Send invitation to tender
+| Send Invitation to Tender
 | Contracting body
-| The contracting body sends an invitation to tender to an economic operator.
-| Receive invitation to tender
+| The contracting body sends an Invitation to Tender to an economic operator.
+| Receive Invitation to Tender
 | Economic operator
-| The economic operator receives the invitation to tender, enabling him to prepare a bid.
+| 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.
-| 
+| 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.
 |===
 
 

diff --git a/guides/profiles/p013/revision/index.adoc b/guides/profiles/p013/revision/index.adoc
@@ -4,15 +4,7 @@
 [cols="1,2,3,2,4", options="header"]
 |===
 | Version | Date | Author | Organization | Description
-| 0.1 | 2015-10-24 | Chander Khoenkhoen | PIANOo | Initial version.
-| 0.2 | 2015-10-28 | Chander Khoenkhoen, Christoph Karich | PIANOo, msg systems ag/BeschA | Revision after mutual review.
-| 0.3	| 2015-12-19 | Chander Khoenkhoen | PIANOo | Changes in section "Business Rules" (updated tables for business and syntax rules for Trdm081 and Trdm081, schematron files) Updated section "Syntax Mapping".
-| 0.4	| 2017-01-05 | Chander Khoenkhoen | PIANOo	| Updated schematron file names in section “Technical interoperability”.
-| 0.5	| 2017-01-11 | Chander Khoenkhoen | PIANOo	| Updated schematron file, business and syntax rules and syntax mapping for transaction Trdm097 (based on 2017-01-09 schematron files).
-| 0.6	| 2017-01-13 | Chander Khoenkhoen | PIANOo	| Updated schematron file for transaction Trdm097 (based on 2017-01-13 schematron files).
-| 0.7	| 2017-01-18 | Chander Khoenkhoen | PIANOo	| Updated schematron file for transaction Trdm097 (based on 2017-01-17 schematron files).
-| 0.8	| 07-02-2017 | Chander Khoenkhoen | PIANOo	| Updated section for technical interoperability, schematron file, business and syntax rules, and example for transaction Trdm097 (based on 2017-02-06 schematron files).
-| 0.9	| 16-02-2017 | Chander Khoenkhoen | PIANOo	| Transaction business and information requirements for Trdm097.
-| 1.0	| 23-04-2021 | Ansgar Mondorf | UKL	| Editorial changes related to links and references.
-| 1.1	|01-03-2023| Ansgar Mondorf | Mondorf IT | Final editorial review for March Release 2023: Update Version information, links & examples, editorial improvements, change of transaction structure
+| 0.1 | 02-07-2023 | Gabrielle Dall | adesso SE | Completion of T024 syntax mapping, examples and schematrons
+| 0.2 | 27-07-2023 | Gabrielle Dall | adesso SE | Creation of BIS 012, Inclusion of Requirements and Process Models
+| 0.3 | 29-06-2023 | Ansgar Mondorf | Mondorf IT | Final review of  P013 - Inviation to Tender and T024 - Invitation to Tender
 |===
diff --git a/guides/profiles/p013/settings.adoc b/guides/profiles/p013/settings.adoc
@@ -3,8 +3,9 @@
 include::../shared/settings.adoc[]
 
 :version: 1.0.0
-:name-profile-org: "Profile BII52 Invitation to tender" (CWA 3456-117)
-:name-profile: Profile P013 - "Invitation to tender" 1.0
+:name-profile-org: "Profile BII52 Invitation to tender" (CWA 17027-117:2016)
+:name-profile-org2: "Profile BII60 Tender Status Inquiry" (CWA 17027-123:2016)
+:name-profile: Profile P013 - "Invitation to Tender" 1.0
 
 
 
diff --git a/guides/shared/interoperability.adoc b/guides/shared/interoperability.adoc
@@ -22,7 +22,7 @@ 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 main flow of open 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.
+** 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 .