Working Group Meeting
Date: 25/02/2025
Participants: Victorio Bentivogli, Natalie Muric, Dragos Stoica,
Model editor: Andreea Pasăre
Note editor: Achilles Dougalis
Discussions
-
During the meeting, the eRequest ORSD was developed.
-
The introduction was expanded: “In the procurement domain, eRequest represents a document created by the Buyer to request an offer for goods and services from a Contractor within a Framework Agreement and direct awards for procurements below threshold (small scale procurement).”
-
The Roles Involved were expanded:
-
Buyer
-
Contractor
-
Offer Issuer
-
-
The Activity description was expanded:
-
The Buyer sends a Request for Offer to the Contractor.
-
The Contractor receives the Request for Offer and analyses it.
-
The Offer Issuer issues and sends the Offer to the Buyer.
-
The Buyer receives the Offer and analyses it.
-
If the Offer is accepted, the Buyer writes the Contract/Order based on the Offer.
-
If the Offer is not accepted, the Buyer may ask for modifications of the Request for Offer and re-start the process.
-
-
-
-
During the meeting, the eAwarding ORSD was further developed.
-
The DPS was further explained by sharing this document.
-
The Description was divided into two segments: Awarding Notification and Dynamic Purchase System.
-
For the Dynamic Purchase System the following description was added: “Dynamic Purchase System
-
The Buyer creates a Call For Competition.
-
The Unique Responsible of the Procurement *ensures *the evidence for the Participation Conditions and the Qualification Criteria are fulfilled by Candidates proposed for Qualification.
-
If the evidence is good, the Qualification Response is *sent *by the Unique Responsible of the Procurement to the Candidate mentioning he is accepted on the Candidate List.
-
If the evidence is not good, the Qualification Response is *sent *by the Unique Responsible of the Procurement to the Candidate mentioning he is not accepted on the Candidate List. “
-
A Call for Tender is created.
-
-
-
The Award Decision Notification diagram for the eAwarding module was presented and expanded. By the end of the WGM the diagram looked like this:
-
In the above diagram epo-awa:AwardDecisionNotification was defined.
-
AwardDecision Attribute hasAdditionalNonAwardJustification became hasAwardJustification.
-
Definition was updated as follows: "Description of the reason behind an award or non-award of a given Tender.Additional information: This is generally used when the non award justification code is set to "Other" and when the Lot is awarded. It may highlight the justification of the non-award of a Tender with regard to awarded Tenders."
-
Action Points
-
Fill in the rest of the eRequest ORSD Fill in the rest of the eAwarding ORSD
-
Create a github issue: To look and check for the semantic wording for all the classes in the Ontology that have a composite naming.
-
Model the Qualification Resolution found here: https://docs.oasis-open.org/ubl/os-UBL-2.4/mod/summary/reports/UBL-TendererQualificationResponse-2.4.html#Table-QualificationResolution.Details
-
Model the TenderReceipt: Model the https://docs.oasis-open.org/ubl/os-UBL-2.4/mod/summary/reports/UBL-TenderReceipt-2.4.html
