Monitor the money flow

[eprocurementontology]

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

Description from the Landscaping report:
In order to obtain an exhaustive and unified view of the flow of public money, from tax collection and budget over to procurement until spending, e-Procurement data should be integrated with other datasets such as budget, spending and location data. A common ontology such as the ePO is necessary in order to interlink such datasets, and help with the creation of a unified view over the flow of public money.
Example:
A procurement watchdog is analysing the flow of public money during an interval of two years. Using the ePO as the common model for representing data, allows the watchdog to find their way through the different sources that have to be consulted, e.g. budget dataset, calls for tender and procurement notices, and to interlink the data in order to identify the trails. Examples of the data to be interlinked by the watchdog, in order to discover the flow of money could be:

• the value of the contract;
• the name of the awarded tender;
• the location of the awarded tender; and
• the department of the public administration that awarded the tender.

Information requirements: In this case it would be required:

• Of the ePO to model all procurement process data e.g. calls for tenders, notices etc.;
• Of the ePO to model economic operator data e.g. name, location etc.;
• Of the ePO to model contract data e.g. contract value;
• Of the ePO to model exclusion criteria etc.;
• Of the ePO to link to other datasets e.g. budget datasets, spending datasets, tax information datasets.

Element	Description
Title	Monitor the money flow
Category	Transparency and monitoring
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: First step Second step Third step Fourth step (if required)
Comments	Any other observation related to the use case

Do you have any reactions regarding this proposition?

[eprocurementontology]

to be added as a use case