...
Table 1 - Web service operations provided by the XVergabe Bidder Interface.
The operations sendMessage and getMessages define a relatively open interface for exchanging messages between bidder client and tendering platform. Table 2 lists the type of messages that can be exchanged. Some messages are to be sent from client to platform, others from platform to client. The structure of the messages is specified in the file xvergabe-messages.xsd
.
Message | Sender | Receiver | Description |
---|---|---|---|
ClientInquiry | client | platform | Contains a document sent from client to the platform. This document can for example contain questions concerning a tendering procedure. These questions can then be answered via a ServerInquiry. |
InvitationToParticipation | platform | client | Contains the documents needed to take part in a participation contest of a tendering procedure. |
InvitationToTender | platform | client | Contains the tendering documents needed to take part in the bidding phase of a tendering procedure. |
Notice | platform | client | Contains the notice information of a tendering procedure. |
Offer | client | platform | Contains the offer documents. With this message a bidder takes part in the bidding phase of a tendering procedure. |
OfferDeliveryReceipt | platform | client | Contains an affirmation for the duly received offer documents. |
OfferWithdrawal | client | platform | With this message, a bidder can withdraw a previously submitted offer. |
OfferWithdrawalReceipt | platform | client | Contains an affirmation for the duly received offer withdrawal. |
Participation | client | platform | Contains the participation documents. With this message a bidder takes part in the participation phase of a tendering procedure. |
ParticipationDeliveryReceipt | platform | client | Contains an affirmation for the duly received participation documents. |
ParticipationWithdrawal | client | platform | With this message, a bidder can withdraw a previously submitted participation. |
ParticipationWithdrawal-DeliveryReceipt | platform | client | Contains an affirmation for the duly received participation withdrawal. |
Response | platform | client | Technical response of the platform to a request by a bidder client. May contain an error code. |
ResultNotice | platform | client | Contains information about the result of a tendering procedure. If a bidder won a procedure, he may be notified via ResultNotice. |
ServerInquiry | platform | client | Contains a document sent from the platform to the client. This document can for example contain answers to bidder questions previously sent via ClientInquiry. |
TenderMetaInformation | platform | client | Contains meta information about a tendering procedure. This message is sent each time some attribute of a tendering procedure changes so that all bidders are up to date. |
Table 2 -Messages that are exchanged between bidder client and tendering platform via sendMessage and getMessages.
...
To illustrate the possibilities of the XVergabe Bidder Interface, the following sections describe the exchange between bidder client and platform in some exemplary scenarios.
...
The scenario in Figure 2 shows how a bidder client can subscribe a tendering procedure and download the tendering documents using the XVergabe Bidder Interface.
Figure 2- Subscribing to a tendering procedure and downloading the tendering documents via XVergabe Bidder Interface.
...
The scenario in Figure 3 shows how a bidder can send questions concerning a tendering procedure and receive the answers to the questions via the XVergabe Bidder Interface.
Figure 3 - Sending Questions to a tendering procedure and receiving the answers.