Working Group meeting 07/02/2023
Date: 07/02/2023
Participants: Jana Ahmad, Natalie Muric, Csongor Nyulas
Model editor: Andreea Pasăre
Note editor: Eugeniu Costetchi
Agenda
-
Standard form mappings - ePO GitHub issues:
-
GH 422 Missing fields F21, IV.2.5, IV.2.9
-
-
Procedure/Sub-procedure
Discussion
GH 442
In the context of concession contracts, the award of procedure actually means procedure. So the “scheduled date for start of award of procedure” is the start of the procedure. We should look into the Directive 2014/24/EU for a better understanding.
Procedure versus sub-procedure
The term procedure has been conflated.
Question: What is a procedure?
Answer: A description of steps taken by someone, a plan.
This plan acts as a general plan for multiple Lots. There are specific plans per each Lot, but the general plan should be fine-tuned in order to cover all the Lots.
Within a procurement project we can have a procedure type. Each lot should be executed once or multiple times according to the procedure type.
There are procedural things that are open to all Lots. We can think about it as a procurement procedure.
Some actions/events are reusable within a procedure:
-
Buyer calls for competition [object] (publish Competition Notice)
-
Buyer awards [object] (and publish a Contract Award Notice)
-
Buyer (re-)opens a (mini-)competition [object]
The negotiation action can be part of the competition.
Also, WG discussed re-usable process fragments:
-
Qualification (exclusion grounds and selection criteria)
-
Competition
eAuction and mini competitions are subsets of closed competition.
Some important examples of procedure types are discussed:
-
Restricted procedure:
-
Buyer calls for competition [specific-object] (Competition Notice)
-
Qualification
-
Closed-Competition [specific-object]
-
Buyer awards [specific-object] (Contract Award Notice)
-
-
Restricted procedure with eAuction
-
Restricted procedure with Dynamic Purchasing System
The competition is related to award criteria and the qualification is related to exclusion grounds and selection criteria. All the process fragments should take into consideration the criteria and the appropriate objects.
Plan versus execution
A differentiation between a plan and an execution is discussed.
-
A Plan (~Procedure + Lots) is a detailed proposal for doing or achieving something.
-
Goal: award of a contract
-
-
An *Execution (~ProcedureExecution) *represents the carrying out of a plan, order or course of actions.
-
Achievement: award of a specific contract.
-
We can have procedure executions per Lot (for a Lot there may be one or multiple executions)
-
We can have procedure-executions per Lot. For a lot, there may be one or multiple executions.
There is one execution for the whole procedure.
-
Each lot has one or multiple procedure executions within the “frame” of the “Procedure” execution.
Procurement purpose is split into Lots, and NOT the procedure that is split into lots.