Skip to content

2. Specific Turnover

Jump to bottom Edit New page
arocamop edited this page Jan 10, 2017 · 2 revisions

  • User story: As a CA I would like to be able to assess the economic and financial standing of the Economic Operators (EO) for which I would need to be able to require the EOs provide their Turnovers of the past N years.

  • Status: Draft

  • Requirements:

  • The CA SHOULD be able to specify the number of the past recent years for which it will require Turnovers.

  • The EO MUST express the Turnover as an Amount, and must specify the currency for that Amount (the default should be €, Euros).

  • For Turnovers "in the business covered by the contract" the EO MAY specify one or more Common Procurement Vocabulary codes to indicate the activities that were developed for that turnover.

  • The CA SHOULD have the possibility of specifying the minimum Amount it expects from the EO.

  • Mockups:

  • Specific avarage turnover

CA viewpoint:

mu_specificaverageturnover_ca

EO viewpoint:

mu_specificaverageturnover_eo

  • Specific yearly turnover

CA viewpoint:

mu_specificyearlyturnover_ca

EO viewpoint:

mu_specificyearlyturnover_eo

  • Data model:

The data model is not affected. But the XML instance (data structure) is. See below.

  • Data Structure for the XML instantiation:

ds_turnoverspecific

  • XML Instance:

The screen-capture below shows a fragment of the XML example for a Specific Turnover. A complete distribution with the entire XML file will distributed once the discussions finished (ZOOM IN to enhance readability):

xml_specificturnover

Add a custom footer

ESPD-EDM UML Data Model

Introduction

Specifications

Additional Tools

see more

Archive:

see more
Clone this wiki locally