content_image/479181.jpg content_image/479183.jpg
<img src='content_image/479181.jpg'>

• Data architecture / Big data / Real-time data processing 

• Data integration / exchange 

• Data security 

• Architectural guidance 

## 4.5.3.2. Deliverables 

The deliverables expected are the ones related to the activities above, e.g. as-is or gap analysis reports, strategy roadmaps, rationalisation reports, audits, architecture blueprints, studies etc. 

## 4.5.3.3. Pricing 

Due to the special nature of the tasks under this work package, the three kind of contracts can apply: Fixed-Price, Quoted time and means or Time and means. Nevertheless, the preferred contracting modes will be Fixed-Price or Quoted Time and Means. 

## 4.6. Run (WP 6) 

The Run work package focuses on ensuring continuity of services and high quality of the operations. It maintains essential functions and delivers efficiency at the appropriate service level for all relevant stakeholders of the Industry channel and data platform. Run includes corrective maintenance, service desk, application management and security in operations. 

The following table describes the work packages covered under this work package. The contractor shall have an adequate organisation, expected staffing, methodology, inputs and outputs to successfully engage in the tasks and services to be provided. 

## This Work Package refers to activities in scope of Lot 2 

<img src='content_image/479183.jpg'>

## 4.6.0. Objectives 

The main objective of this work package is to provide a single horizontal service across the scope of the FWC666. The Contractor fulfils all Run  requests within the contractual SLAs. The main effect of fulfilling the Run  objectives horizontally can be exemplified when an incident is detected in the behaviour of one of the capabilities in the Industry channel (let’s say RE ACH submission) but incident response ramifies into several parts of the scope, in such case the Contractor handles a single incident, regardless the affected parts of the channel. It can also happen that the very same incident requires interaction with a third party (e.g. the provider of infrastructure services), triggering the interaction model as specified in Interaction between contractors and third parties. 

The Contractor organises the Run work as DevOps, whereby the staff working on development activities and operations act as one team, ensuring sharing of knowledge and flexibility in the handling of fluctuations in the volume of activity (e.g. temporarily increase the ops  capacity to address a work intense period). 

