Working Group meeting
Date: 29/08/2023
Participants: Paloma Arillo, Giovanni Paolo Selitto
Model editor: Andreea Pasăre
Note editor: Alexandros Vassiliades/Andreea Pasăre
Discussion:
All the properties that go to epo:MonetaryValue were extracted and checked if they respect the requirements for standard forms and eForms.
The following predicates were presented:
-
epo:hasApproximateFrameworkAgreementValue replaces epo:hasFrameworkAgreementEstimatedValue.
Definition:
The estimated value to be spent within the Framework Agreement(s).
Additional information:
In the case of an Award Decision for a Lot, this relation represents the estimated value for the awarded Framework Agreement.
In the case of a Notice, this relation represents the estimated value for all Framework Agreements covered by the Notice.
Domain, Range and Cardinality:
epo:LotAwardOutcome → epo:MonetaryValue [0..1]
epo:NoticeAwardInformation → epo:MonetaryValue [0..1]
Usage:
eForms – BT 660
-
epo:hasAwardedEstimatedValue was DELETED since it is the same concept as epo:hasApproximateFrameworkAgreementValue.
-
epo:hasLaunchFrameworkAgreementMaximumValue moved from epo:FrameworkAgreementTerm level to epo:ProcurementObject level.
Definition:
The highest value that can be awarded to a Framework Agreement.
Additional information:
This relation can be used for a Procurement Object or a Group of Lots.
In the case of the Group of Lots, this information can be provided when the maximum value of the Group of Lots is lower than the sum of maximum values of individual Lots in this group (e.g. when the same budget is shared for several Lots).
Domain, Range and Cardinality:
epo:ProcurementObject → epo:MonetaryValue [0..1]
Usage:
eForms – BT-271
-
epo:hasLaunchGroupFrameworkAgreementMaximumValue was changed to epo:hasLaunchFrameworkAgreementMaximumValue (this way we align with epo:hasApproximateFrameworkAgreementValue which can be used both at the Lot level and Notice level) and was moved at the Lot Group level.
Definition:
The highest value that can be awarded to a Framework Agreement.
Domain, Range and Cardinality:
epo:ProcurementObject → epo:MonetaryValue [0..1]
Usage:
eForms – BT-157
-
epo:hasTotalValue - changed cardinality between Tender Group and Monetary Value from 1 to [0..1].
-
epo:hasEstimatedValue was added at the Lot Group level.
Definition:
A forecast of the value of the procurement before competition.
Additional Information:
Different cases of estimated values may refer to a lot, the global value of the procedure, or of a combinatorial value of a group of lots.
The forecast is calculated by the buyer and covers all revenues whether coming from the buyer or third parties.
See for example recital (19), Article 5 of Directive 2014/24/EU and other articles from the rest of Directives about procurement.
In the case of framework agreements and dynamic purchasing systems this refers to the maximum estimated value.
This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used for BT-157 (for LotGroup).
WG Approval 05/12/2019
Domain, Range and Cardinality:
epo:LotGroup → epo:MonetaryValue [0..1]
Usage:
eForms – BT-27
The UML diagrams related to Monetary Values below were presented:
