Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alerting services #10

Closed
eprocurementontology opened this issue Apr 14, 2017 · 1 comment
Closed

Alerting services #10

eprocurementontology opened this issue Apr 14, 2017 · 1 comment
Assignees
Labels
module: ePO core ePO core type: use case Use Case (User story)
Milestone

Comments

@eprocurementontology
Copy link
Collaborator

Patrizia Cannuli would like to propose a use case on behalf of Consip. It would be based on the use case 2.3 "Alerting services" from the Landscaping report. They would like to analyse deeper this use case in the short-term.

Description from the Landscaping report:
Contracting authorities announce and publish the calls for tender to economic operators, citizens and third parties. Through the use of alerting services, economic operators are informed about published call for tenders that match their profile. In order to automate alerting services, e-Procurement data such as tenders and information about economic operators should be machine processable, so they can be integrated, matched, and the right data should be delivered to the right person (depending on their subscription to the alerting services).
Example:
A Spanish public administration procures stationery and textbooks for the forthcoming year. The public administration publishes the call for tenders on an online platform. Since the call for tenders is published in a machine-readable format, following the structure of the ePO, third-party applications can process the call for tender and send alerts to interested parties who are subscribed in their client bases. Usually, such third party applications offer their clients the ability to define criteria for which they want to be automatically alerted.
Information requirements:
In this case it would be required:

  • Of the ePO to model the calls for tenders and the details within it.
Element Description
Title Alerting services
Category Innovation & value added services
Description Concise text that provides basic information about the actors, the goal and the intended results of the use case
Actors Further details on the agents (persons, organisations or software programs) involved in the use case
Final recipients The actors that receive the results or benefits from the use case
Preconditions Anything that can be said about the situation before the use case begins
Flow A step-by-step description of the actions taken and responses received by the user:
  1. First step
  2. Second step
  3. Third step
  4. Fourth step (if required)
Comments Any other observation related to the use case

Do you have any reactions regarding this proposition?

@eprocurementontology
Copy link
Collaborator Author

Add to use cases

@costezki costezki added type: use case Use Case (User story) module: ePO core ePO core labels Aug 31, 2022
@costezki costezki added this to the 2022 Q4 milestone Aug 31, 2022
@andreea-pasare andreea-pasare removed this from the 2022 Q4 milestone Nov 13, 2022
@andreea-pasare andreea-pasare added this to the 2023 Q4 milestone Feb 28, 2023
@OP-TED OP-TED locked and limited conversation to collaborators Jan 17, 2024
@AchillesDougalis AchillesDougalis converted this issue into discussion #503 Jan 17, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
module: ePO core ePO core type: use case Use Case (User story)
Projects
None yet
Development

No branches or pull requests

3 participants