Rapid Alerts

previously

Rapid Alert System for Food and Feed Safety

28th CEFACT FORUM

Bangkok

September 26-30, 2016

Introduction

• Current RASFF System

• CEFACT Implementation

• Network exchanges and collaboration proposal

• Other domains and synergies

• Planning

2

The RASFF System

• System:

• Network (organisations)

• IS (IT Tool)

• Participants

• Food & Feed authorities

• Central Authorities

• Exchange on

• Incidents and cases

• Controls

• Measures taken 3

The RASFF system in practice

4

The RASFF workflow – a standard case

5

Escalate

RASFF Level and organizations

• The notification flows involve different organizations and levels.

• In typical scenarios, 3 levels are involved for the exchanges: • Level n-1, level n and level n+1, but more levels could be used.

• Key roles for each level:

Local/Creator: Authorities typically creating and submitting the notifications to their Central Authorities

Central/Validator: Authorities validating these notifications and escalating them to the Central Authorities at the next level

Auth

orities

Centr

al

Local

Level n - 1 Level n

Submit (same level)

Escalate Validate

Level n+1

Validate Escalate Validate

Submit (same level)

Submit (same level)

RASFF Operation Across Levels Symmetrical model for all levels

Business Process Symmetrical workflow of a notification

Le

ve

l n

- 1

Ce

ntr

al

/

Va

lid

ato

r

Lo

ca

l /

Cre

ato

r

Le

ve

l n

Lo

ca

l /

Cre

ato

r

Ce

ntr

al

/

Va

lid

ato

r

Le

ve

l n

+ 1

Lo

ca

l /

Cre

ato

r

Ce

ntr

al

/

Va

lid

ato

r

Alert occurred

Create Draft Submit

Validate Escalate

Alert received

Validate Escalate

Message received

Validate

End

Current CEFACT model

• Specification of the workflows for the different levels

• Four levels are assumed, but there is no limit in the levels number

• Intended for use by authorities

• Collaboration model

8

Collaboration model

• The collaboration currently flows hierarchically, unless the notification / alert has been validated at the top level, lower levels cannot see it

• Proposal of a new model is proposed allowing

• Collaboration within a level

• Collaboration across levels

The alert contents remain the same, but new messages are created between the collaborating entities

9

Collaboration model Collaboration within a level

sd Assign horizontally

Organisation1

at level n

(lead)

Organisation2

at level n

level n+1Organisation3

at level n

Organisation4

at level n

Validate notification()

Escalate()

Create followup()

Assign()

Create followup()

Assign()

Create followup()

Assign()

Collaboration model Collaboration across levels

sd Assign downward

Organisation1

at level n

(lead)

Organisation2

at level n

level n+1Organisation3

at level n

Organisation4

at level n

Create followup()

Create followup()

Assign()

Assign()

Assign()

Escalate()

Create followup()

Create followup()

Assign()

Proposal for extension of RASFF

Short term

• Launch project to improve - Data content / component model

- Message exchanges

- Alignment with Agriculture domain projects

- Use case model

- Terminology (more general terms are needed)

• At the end of the activity we plan to propose implementation guidelines

Long term

• Launch project for other domains

12

Component model

• The current component model assumes that all information is sent at once

• Introduce independent notions of

• Product

• Consignment

• Other info - Risks / Hazards

- Constraints in breach (legislation, common practices, other)

• Decompose message to smaller messages depending on

- Use cases / basic message exchanges

- Contents changes / requests

13

Targeted parties & exchanges

• Currently the model only addresses Government-to-Government communication and collaboration

• Exchanges to be addressed in the future:

• Business-to-Government

• Government-to-Business

• Business-to-Business

14

Synergies with agriculture projects

• Track and Trace

• Transformations / processing and transportation

• Key messages

• e-Labs

• Laboratory analysis & results

• Key messages

• e-Crops

• Primary products, pesticides treatment

• Key messages

15

Synergies with agriculture projects

• Develop common controlled lists

• Product processing & transformation / transportation

• Analysis parameters / sampling etc..

• Services: discovery, updates, sync…

• A model for reusing control lists and simplifying evolution is needed

• FLUX characteristics as an inspiration / model to follow

16

New General model

• Networks with members can be created for different domains

• The model does not address how a network operates, only message types and content are addressed by the new model

• Network members /parties can send/receive all message types

• Associated Parties can participate on a more limited number of exchanges

• All parties can provide information on request 17

New General model (cont.)

• Alerts and collaboration on following domains:

• Food safety and food chain

• e-Commerce,

• textiles (?),

• e-Cert,

• import inspections,

• …

18

Planning proposal

• 29th CEFACT (Spring 2017)

• Collaboration elements - New collaborative model approved

- New component model approved

- Draft implementation guidelines

• Rapid Alert and Collaboration Network - Explore interest and support by delegations

- Launch collaboration with other domains

- Initial BRS proposal

• 30th CEFACT (Autumn 2017)

• Approved BRS / RSM for the Rapid Alert and Collaboration Network

19

Thank you

20

Annex

21

Business transaction (activity diagram) Submit Notification

22

act Submit Notification

Local/Central Authority at lev el n Central Authority at lev el n+1

Initial

SubmitNotification

Process Submitted

Notification

Notification

(Submitted)

Acknowledgement

(Sent)

Send

NotificationReceiv e

Notification

Send

Acknowledgement

Receiv e

Acknowledgement

Business transaction (activity diagram) Validate Submitted Notification

23

act Validate Notification

Central Authority at lev el n+1Local/Central Authority at lev el n

Initial

Notification

(Validated)Validate

Notification

Send

v alidated

notification to

registered

systems

Receiv e

v alidated

notification

act Query Notification

Local/Central Authority at lev el n Central Authority at lev el n+1

Initial

QueryNotification

Retreiv e NotificationNotification

QueryQuery for

Notification

Receiv e

Notification

Query

Notification Send

Notification

Receiv e

Notification

Business transaction (activity diagram) Query notification [Read]

24