Field BT-05 24 hour rule about eforms-sdk HOT 7 CLOSED

Hi,
The concern expressed here is not about the dysfunction of the SDK, it is about a business decision which defines a timeframe for valid notice submission. For business questions, please share your concern directly with the helpdesk.

from eforms-sdk.

Hello
This question relates to a business decision - there is nothing technically wrong with the rule in the SDK.
For a short business answer, the Publications Office has 5 calendar days to publish a notice from the moment the buyer sends it for publication. We assume the eSender doesn't take took long to forward it, as otherwise this reduces the period the Publications Office has to publish the notice (which might already include non-working days). We consider that 1 day is enough for eSenders to do what they need to do, as well as allowing for any possible technical disruptions. Currently, eSentool imposes a 12 hour limit for how "old" a notice can be so the rule for eForms is more generous.
For any further questions, please email the TED helpdesk.

from eforms-sdk.

Hello
BT-803 was added in last year's amendment to the eForms regulation and only allows to see how long it takes an eSender to forward the notice from their user/client/buyer to the Publications Office, which should be kept to a minimum.
The important field is BT-05 as this is the dispatch date from the point of view of the buyer, who should be able to count on a publication in the OJS within no more than 5 days, as defined in the directives. The buyer should have to worry about how long an eSender takes to process their notice. From the Publications Office BT-05 is the legally binding date so the rule is set on this field, not on BT-803.
If, as an eSender, you need some days to check what a buyer sends to you before you send it to TED, then perhaps you need to be clearer with your buyers what constitutes the date of dispatch to TED, as this has many implications in the timing of their procurement procedures. If you are already using eSentool, you can probably keep the same definition of the date you already put in the current TED-XML.

from eforms-sdk.

Hi,
Please for non-issues, use the discussions channel instead. Also for non-technical questions, please address your inquiries directly to the Helpdesk at [email protected].
I close this non-issue.
KR.

from eforms-sdk.

Hi,

Why do you think, this problem is not a technical issue?
We have the same problem.

Celex: BT-05: "The date and time when the notice has been sent for publication by the buyer."

One real case:
If the user submit a notice from the procurement system to eSender on Saturday (it is a real situation) the eSender cannot forward it on Monday because the Schematron rule is blocked it.

Other real case:
All notices are manually checked for lawfullness by the eSender (Official Org). This may take 1-2 days.
That's why the dynamic Schematron validation block this notice.

Now the eSender needs to update this date, so that this date will not be equal to the date "when the notice has been sent for publication by the buyer."

According to local law, the time of sending by the buyer must be indicated, according to the documents, we thought this is BT-05.

Are we wrong?
What could you suggest?

from eforms-sdk.

Hi,

We understand that, but from our point of view the BT-05: "The date and time when the notice has been sent for publication by the buyer." and BT-803 "The date and time the notice was transmitted electronically by the eSender to the Publications Office of the European Union". Field BT-05 contains the 24 hour rule instead of field BT-803.

from eforms-sdk.

Thanks for your response
Anna

from eforms-sdk.