Document 11.1 • Ref. Ares(2020)1527358-12/03/2020 Contract no.: JRC/Frontex/1571/2018 Annex II- Deliverables Due Date D1 27.09.2019 Description Title The document upload system will allow the insertion NewsDesk Document Upload into the FMM system of ad hoc documents, that are then processed by the automated systems following which can then be exploited in Newsdesk and visualised in NewsBrief. - In order to allow Frontex to better understand the associated business process, the JRC should provide generic examples of possible use cases of document upload for example in Newsletters and in NewsBrief. - Following previous point Frontex should elaborate their specific use case/s. - Frontex will be required to provide further hardware in order to support the processing of documents that are uploaded. Therefore the JRC should provide the specifications of the platform for the press-review processing chain. - JRC will customise and install document upload system and processing chain components (perhaps on test system) D2 29.03.2019 NewsDesk The NewsDesk system will be updated to: expunged justifcation 4 - Template maintenance and updates, further customisation of templates, Flash News and disable post to web for it.

D3 |28.06.2019 | Reporting Bi-annual Frontex-JRC videoconferences formally
20.12.2019 reporting on the progress of software improvements
and deployment, upon the agreement between the
two parties. Further VC’s will be organised on and ad
hoc basis including an additional informal reporting
every 3 months between the formal reporting every 6
months.

 

 

    
     
    
  
   
  
     
     
   
      
 
    
 

20.12.2019

31.10.2019

31.06.2019

EMM Support and
Updates

JRC will provide a week day working hours support for
technical problems regarding FMM. In agreement with
Frontex the JRC will perform installation, integration,
slight customisation and support of new or improved
EMM functionalities which are developed during the
course of regular JRC research activities. Provide
training on all new features developed during the course
ofthe contract.

  
 

FMM Applications
for mobile devices

  
 

JRC to further develop and improve the FMM mobile
based on input from Frontex.

 

  
  
  

 
  

Preview of an
automated
transition to EN

Frontex will need subscribe to the google translate
service and then will provide the credentials to JRC. JRC
will then develop an automated API system to pick up
the translation on a per click basis. JRC could also
potentially enhance this mechanism to provide the
translation of all articles in a given newsletter.

    

D7 |31.06.2019 | Automatic post | Currently there no automated way to post a

of newsletters | published newsletter to another system unless

inpdfto FOSS |there is a common shared drive. JRC will
discuss with all interested parties in Frontex the
technical mechanism (Post/Pull..etc.) in order
to support this need.

D8 | 31.12.2019 Dedicated
training
sessions at

Frontex

 

Although the JRC provides free training
sessions to EMM users, the nature of the
Frontex system setup together with the custom
features that will be delivered (cited previously)
dedicated training sessions will be held onsite
at Frontex.

Deliverable Acceptance Form

Contract No Frontex/1571/2018 (FMM/Newsdesk)

| Original document - duly signed - to be attached to the invoice |

DELIVERABLE DESCRIPTION

Please give reference to the Terms of Reference and short description of the task or deliverable.

 

Please describe observations and reservations if any.

In case of Task/Deliverable rejection please detail reasons.

In the time covered by the contract, JRC has provided regular support, and bug resolution for
FMM/Newsdesk according to the contract terms.

The Contract included a list of eight deliverables (detailed description in Annex II):

Deliverable 1
Deliverable 2
Deliverable 3
Deliverable 4
Deliverable 5
Deliverable 6
Deliverable 7

Deliverable 8

DELIVERABLE is ACCEPTED / REJECTED
To be filled in by Frontex:

Official responsible for acceptance

  
 
   
  
  

in block capitals):
Date and signature

 

Official responsible for final validation
(in block capitals):

 

 

Date and signature