Life-cycle management

From Wikicap - European Commission

Go up to the main update page

In order to illustrate the life-cycle of a data instance, let’s take the example of a reference parcel that resides in the LPIS of the current campaign year, which is therefore valid. Suppose that during some routine operation, a discrepancy, for example the unexpected presence of a water body has been found. The operator opens an anomaly. From this moment the update process starts that will affect the status of two instances: the anomaly and the reference parcel.

The statuses of anomaly and reference parcel will be described in terms of the pre-defined code list according to the following scenarios:

Scenario 1: in course of processing the anomaly is confirmed that triggers a need to update the geometry and the reference area of the related reference parcel.

Event

Status of anomaly

Status of the reference parcel

Farmer’s application

n.a.

Valid

Staff Member discovers, what he believes, a non-conformity (water body)

Open

Under evaluation

LPIS operator confirms anomaly

In progress

In progress

LPIS operator corrects the geometry in the LPIS

Under cross check

In progress

LPIS data manager collects evidences (imagery) from previous years to determine the time of the change on the land

Under cross check

In progress

LPIS data manager provides information to the paying agency

Under cross check

In progress

The Paying agency takes measures for retroactive recovery and send feedback to LPIS custodian

Under approval

In progress

LPIS data manager approves the change

Approved

In progress

LPIS data manger finishes the update workflow

Valid

Old geometry archived

New geometry valid


Scenario 2: in course of processing the anomaly is not confirmed

''''Event

Status of anomaly

Status of the reference parcel

Farmer’s application

n.a.

Valid

Staff member discovers what he believes to be a non-conformity (water body)

Open

Under evaluation

LPIS operator on all available imagery founds that there ist no permanent water body and suspects that the parcel was flooded

In progress

Under evaluation

LPIS data manager collects further evidences (hydro-meteorological data, RFV). The hypothesis of flooding confirmed.

Under cross check

Under evaluation

LPIS data manager rejects the update request

Rejected

Valid

LPIS data manager finishes the workflow

Archived

Valid

The different life-cycle statuses and the transitions between them are presented in Figure 3.

Pic2.jpg

Figure 2: Life-cycle management: statuses and transitions between them

It should be noted that upgrading a schema element of the information model can be performed in a similar way. The only difference is that the feature type used for monitoring the status of the upgrade is called an issue.

Go up to the main update page