IPI regulation #1049
-
Dear TED team, According to eForms Guideline on the IPI: Finalise IPI guide (#16) · Issues · eProcurement Group / eForms Group / Change Requests · GitLab, if it is indicated that an IPI measure is applicable to this EU public procurement procedure, more information needs to be provided under the business group Information on IPI Measures (BG-681). It is necessary to provide the Number of tender applications that fall under this IPI Measure (BT-686) for each Specific IPI Measure (BT-685). As it is possible to have different types of Specific IPI Measure (BT-685), it is possible to provide multiple measures and to mention for each of them the Number of tender applications that fall under this IPI Measure (BT-686). The problem is that in the table of the 2nd amendments of e-forms (in the attachment), IPI activities should be indicated against the tenders (BG-320), not against the results (BG-137). The table suggests that IPI activities should be indicated for each tender, but this does not align with the previously mentioned business process description (which states that the applicable IPI activities should be indicated alongside the corresponding number of tenders). Currently, SDK version 12 is available. However, the fields for IPI regulation are planned only for SDK version 13, which is not yet available. Therefore, it’s unclear how the IPI measures will be recorded in the scheme. Thank you in advance! Kind regards, Evija Mozga |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi,
|
Beta Was this translation helpful? Give feedback.
Hi,
Issues are exclusively used for SDK specific issues, so this has been changed to a Discussion/Q&A.
Regarding the issue raised for the association with LotTender vs LotResult, you should get in touch directly with DG GROW. As you reminded, aggregated information is expected which for a given Tender wouldn't be suitable while for a given LotResult makes sense.
There isn't currently any Implementing Act and no IPI information may currently be reported.
When the documentation of SDK 1.13 will get published, you'll be able to find an illustrative example I've copied below. Note that the example is only there for illustration purpose and not for consistency. Focus was to show the implementa…