P_BUC_04_Mainproc_Specification_v4.1.0 | Lexipedia

EESSI Business Use Case

P_BUC_04

Request for Child Raising Periods

P_BUC_04

Request for Child Raising Periods

Table of Contents

1.3. Definitions, Acronyms and Abbreviations 6

References 7

6.1. Issues 23

Document Control Information

Settings

Value

Document Title:

Business Use Case

P_BUC_04 - Request for Information about Child Raising Periods

Project Title:

EESSI (Electronic Exchange of Social Security Information) Project

Document Author:

European Commission, DG EMPL F5

System Owner:

European Commission, DG EMPL D2

Doc. Version:

v4.1.0

Sensitivity:

Public

Date:

03/08/2018

Document history:

The Document Author is authorized to make the following types of changes to the document without requiring that the document be re- approved:

Editorial, formatting, and spelling

Clarification

To request a change to this document, contact the Document Author or Owner.

Revision

Date

Created by

Short Description of Changes

v0.1.0

04/03/2016

Phil Cummings

Initial Draft

v0.2.0

22/04/2016

Cristina Ezaru

Incorporated review received from AHG:

5. branch 2 was removed H_BUC_07_Subprocess Notification of Death

v0.3.0

22/06/2016

Carine Molle

Alignment to the standard description and layout of the BUC.

v0.4.0

14/07/2016

Cristina Ezaru

Incorporated review received during the AHG meeting (13/07/2016)

1. Branch2 updated: removing participants should be able to any

participant (within their own MS)

2. Branch3 updated: adding participants should be able to any

participant (within their own MS)

4. Other small text corrections

v0.5.0

12/09/2016

Cristina Ezaru

Incorporated AC comments:

2. Other small text corrections

v0.99.0

30/09/2016

Cristina Ezaru

Candidate for AC Approval

Incorporated review received during the AHG meeting (29/09/2016)

4. Business Scenario rewording text: " The Insured Person … begin to

pursue an employed…"

6. Branch9 updated: replaced "any Participant" with "Case Owner"

v1.0.0

19/10/2016

Cristina Ezaru

AC APPROVED VERSION

v1.0.1

26/06/2017

Madalina Alecsandrescu

Last version BPMN section 5

v1.0.2

11/08/2017

Eric Briffoz

- Included the version of the BPMN Diagram in section 5.

- Correction in the horizontal subprocess table in section 4.5.

- Removed Use Case diagram

Madalina Alecsandrescu

Align wording for Invalidate SED and Forward participant

v.4.1.0

03/08/2018

Madalina Alecsandrescu

- Section 4.4 merged 2 tables (for SED & for Subprocesses) into 1 BUC Artefact table."

- Version adaptations to release 4.1.0.

- Correction in wording in SR to [Branch 4]

Introduction

Purpose

The purpose of this document is to construct an external view of, part of, the 'EESSI business system' as described in EC Regulations 883/2004 and 987/2009. The ‘EESSI Business System’ describes the business and expected business processes without consideration as to which part(s) may be realized by an IT System (i.e. the proposed EESSI IT System).

The external view comprises of models and descriptions of business use cases, the services of a business system offered to business actors: customers, business partners, or other business systems.

A business use case is described from an actor's perspective; it describes the interaction between an actor and the business system, meaning it describes the behaviours of the business system that the actor utilizes. The Business Use Case includes Use Case Diagrams and Business Process Models.

Use case diagrams show actors, business use cases, and their relationships. Use case diagrams do not describe procedures. Alternative scenarios also remain hidden. These diagrams give a good overview of the behaviours of the EESSI business system which will direct and govern part of the expected behaviours and functionality delivered by the EESSI IT System.

Scope

This document is limited to the external view on the pension sector process of the Request for Child Raising Periods. The different elements like use case description, actors, and business process as well as

supporting UML diagrams and BPMN models pertaining to the Request for Child Raising Periods.

Definitions, Acronyms and Abbreviations

Please see the EESSI Project Glossary here.

References

Description

EC Regulation 883/2004

Regulation EC No 883- 2004.pdf

EC Regulation 987/2009

Regulation EC No 987-2009.pdf

UML 2.x

http://www.omg.org/spec/UML/

BPMN 2.0

http://www.omg.org/spec/BPMN/index.htm

UML 2.0 In Action

Henriette Baumann, Patrick Grassle & Philippe Baumann, 2005, ISBN 1904811558

RUP@EC standard 5.0

http://www.cc.cec/RUPatEC_Standard/

RUP op maat

http://www.rupopmaat.nl/

Overview

Chapter 1 introduces the external view on the business system under review and lists the elements of this specification.

Chapter 2 introduces us to the Request for Child Raising Periods business process. The chapter gives a short and detailed description as well as a reference to business process´ legal base.

Chapter 3 lists the actors involved in the Request for Child Raising Periods business process.

Chapter 4 describes in detail Request for Child Raising Periods business process based on the RUP use case template, as well as the relationship to other use cases.

Chapter 5 describes the Request for Child Raising Periods business process using business process modelling notation (BPMN).

Description

Business Scenario

The definition of a ‘child-raising period’ means any period that is credited under the pension legislation of a Member State or which provides a supplement to a pension explicitly for the reason that a person (hereinafter Insured Person) has raised a child, irrespective of the method used to calculate those periods and whether they accrue during the time of child-raising or are acknowledged retroactively

The responsibility for taking into account child-raising periods is primarily vested in the Member State that is competent under the provisions on applicable legislation according to Title II of the basic Regulation.

However, Article 44 of Regulation 987/2009 lays down legal provisions whereby under the following circumstances another Member State shall assume responsibility for providing child raising periods that would not ordinarily be competent under Title II.

An Insured Person meet the conditions to receive child-raising periods in a Member State

While in receipt of those child-raising periods they become subject to the legislation of a Member State who does not provide Child Raising Periods.

The Insured Person does not immediately begin to pursue an employed or self-employed activity.

Under these conditions the MS that was previously providing the Child- Raising Periods remains competent to continue to provide the periods up to and until one of the following situations occurs

The conditions under their national legislation to provide Child Raising Periods no longer exist (e.g. the child reaches a certain age)

The Insured Person begins to pursue an employed or self-employed activity in another MS

Legal Base

This Business Use Case document's legal base is described in the following Regulation

implementing Regulation (EC) No 987/2009

The following matrix specifies the SEDs that are used in this Business Use Case and documents the articles that provide the legal basis for each SED.

SED

Implementing Reg (987/09)

Art 44

P1000

P1100

Table 1: SED – Legal base relationship matrix

Actors & Roles

This chapter captures details of the actors which are important to understand the different types of system users. An actor is anyone or anything that exchanges data with the business system. An actor can be a user, external hardware, or another system.

The overarching description of each actor described in this Business Use Case can be found in the Glossary. Below you will find a short description which provides further clarity of this actor within the context of this Business Use Case.

Actor name

Description

Case Owner

In this BUC the Case Owner is a Competent Institution that is requesting information about Child Raising Periods in another MS

Counterparty

In this BUC the Counterparty(ies) are Competent Institutions that are requested to provide information about Child Raising Periods in their MS

Insured Person

In this BUC the Insured Person is the person to whom the Child Raising

Periods are provided

Child

In this BUC the child is the person [reason] for which the Child Raising Periods are provided to the Insured Person

Use Case

RUP Table Representation

Use Case ID:

P_BUC_04

Use Case Name:

Request for Information about Child Raising Periods

Created By:

Phil Cummings

Last Updated By:

Cristina Ezaru

Date Created:

04/03/2016

Last Revision Date:

30/09/2016

Actors:

Case Owner

Counterparty

Description:

However, Article 44 of Regulation 987/2009 lays down legal provisions whereby under the following circumstances another Member State shall assume responsibility for providing child-raising periods that would not ordinarily be competent under Title II.

An Insured Person meet the conditions to receive child-raising periods in a Member State

While in receipt of those child-raising periods they become subject to the legislation of a Member State who does not

provide Child Raising Periods.

The Insured Person does not immediately begin to pursue an employed or self-employed activity.

Under these conditions the MS that was previously providing the Child Raising Periods remains competent to continue to provide the periods

up to and until one of the following situations occurs

The conditions under their national legislation to provide Child Raising Periods no longer exist (e.g. the child reaches a certain age)

The Insured Person begins to pursue an employed or self-employed activity in another MS

Trigger:

An institution requires specific information about Child Raising Periods during the course of its investigations.

Preconditions:

none

Post conditions:

The Case Owner has received the information they require about Child Raising Periods to determine if they need to provide Child Raising Periods to the Insured Person.

Main Scenario:

Identify Participants

The Case Owner identifies the Member State(s) that they require the information from;

The Case Owner then identifies the correct institution or institutions (the Counterparty(ies)) in each Member State that are responsible for providing the information of child raising periods they need. There will be one Counterparty or more. The Case Owner and the Counterparty(ies) are herein collectively referred to as the Participants.

Request Child Raising Periods

The Case Owner fills in a Request for child raising periods (P1000) to request information about the child raising

periods;

The Case Owner sends the Request for child raising periods (P1000) to all participants concerned .

Provide Child Raising Periods

Each Counterparty who received a Request for child raising periods (P1000) gathers the information about Child Raising Periods and fills in Reply to Request for Child Raising Periods (P1100);

Each Counterparty who filled in the Request for child raising periods (P1100) sends it to the Case Owner and other Counterparties.

The use case ends here.

Alternative Scenarios

at any step after [step 4] the Case Owner may choose to send another Request for child raising periods (P1000) to the Counterparties to request information about another child.

The Case Owner fills in a Request for child raising periods (P1000) to request information about the child raising periods;

The Case Owner sends the Request for child raising periods (P1000) to all participants concerned;

The Counterparty who received a Request for child raising periods (P1000) gathers the information about Child Raising Periods and fills in Reply to Request for Child Raising Periods (P1100);

Each Counterparty who filled in the Reply to Request for Child Raising Periods (P1100) sends it to the Case Owner and other Counterparties;

[This Branch] Ends.

The Following Branches Determine the use of Horizontally

Defined Sub Processes within this Business Process

The Following Branches Determine the use of Administrative Sub Processes within this Business Process

at any step after [step 4] any participant may choose to Remove participants to this Business Process. Case owner should be able to remove participants in any MS, Counterparties should be able to remove participants in their own MS.

The Participant executes business use case AD_BUC_04_Subprocess – Remove Participant;

[This Branch] Ends.

at any step after [step 4] any participant may choose to Add new participants to this Business Process. Case owner should be able to add participants in any MS, Counterparties should be able to add participants in their own MS.

The Participant executes business use case AD_BUC_03_Subprocess – Add Participant;

[This Branch] Ends.

at any step after [step 4] any participant may choose to Forward this Business Process to another Institution within their MS who assumes responsibility for handling it.

The participant executes business use case AD_BUC_05_Subprocess – Forward Case;

[This Branch] Ends.

at any step after [step 4] the Case Owner may choose to advise all recipients of their P1000 is Invalid under Art 5 of 987/09.

The Case Owner executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Case Owner fills out the P1000, by entering all the required data;

Optionally, the Case Owner sends P1000, including any attachments, to all Counterparties;

[This Branch] Ends.

at any step after [step 6] a Counterparty may choose to advise all recipients of their P1100 is Invalid under Art 5 of 987/09.

The Counterparty executes business use case AD_BUC_06_Subprocess - Invalidate_SED;

Optionally, the Counterparty fills in P1100, by entering all the required data;

Optionally, the Counterparty sends P1100, including any attachments, to all Counterparties;

[This Branch] Ends.

at any step after [step 4] the Case Owner may choose to send an updated version of P1000.

The Case Owner executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

at any step after [step 6] the Counterparty may choose to send an updated version of their P1100

The Counterparty executes business use case AD_BUC_10_Subprocess - Update_SED;

[This Branch] Ends.

at any step after [step 4] the Case Owner may optionally choose to send a Reminder to another Participant for the return of information they were expecting from that participant but did not receive.

The Case Owner who invokes this branch executes business use case AD_BUC_07_Subprocess -_Reminder;

[This Branch] Ends.

Exceptions:

Exception 1: removed

Includes:

See diagram at part 4.4

Special Requirements:

SR1: Rules about the invoking of Branches:

Administrative

[Branch 2] to [Branch 9] – May be invoked more than once, per Participant, exception [Branch 4] – May be invoked only once, per Participant

SR2: Rules about the destination for each SED Type when the SED is sent:

P1000 – Defines and is sent to all Active Participants

P1100 – Must be sent to all Active Participants

SR3: The term "Send/Sent to All Active Participants" does not include sending to themselves (i.e. to the senders institution)

SR4: Active Participants are defined as those participants identified at [Step 2] and those participants added through the execution of [Branch 3] and/or [Branch 4] and not removed through the execution of [Branch 2] and/or [Branch 4]

SR5: Alternative Branches 1 – 9 are non-interrupting Branches;

Assumptions:

Notes and Issues:

Request – Reply SEDs

The following table specifies and SED that have a logical pairing to one another, usually this is known as a request-reply pair.

REQUEST SED

REPLY SED(s)

P1000

P1100

Attachments Allowed

The following table specifies whether attachments are permitted to be included when sending a SED type.

SED

Attachments

P1000

Allowed

P1100

Allowed

Artefacts used

The following table specifies the artefacts that are used in this Business Use Case.

Artefact name

Artefact type

P1000

SED

P1100

SED

AD_BUC_03_Subprocess – Add Participant

BUC

AD_BUC_04_Subprocess – Remove Participant

BUC

AD_BUC_05_Subprocess – Forward Case

BUC

AD_BUC_06_Subprocess – Invalidate SED

BUC

AD_BUC_07_Subprocess – Reminder

BUC

AD_BUC_10_Subprocess – Update SED

BUC

AD_BUC_11_Subprocess – Business Exception

BUC

AD_BUC_12_Subprocess – Change of Participant

BUC

Business Processes

This chapter describes the Business Use Case Request for Information about Child Raising Periods .

Case Owner and Counterparty

Sub Processes

n/a

Appendices

Issues

Issue date

Description

Replies

Action/Resolution

Close date