European Technology Platforms

1

• European Technology Platforms
• and European Software Industry
• José M. Cavanillas
• International Activities Director

2
Agenda

• Atos Origin
• Global strategy on ETPs
• ETP simple approach and deeper view
• ETP on software and services
• S3 short history
• Baltic presence in ETPs

3
An International Player
A leading IT services company providing business
consulting, systems integration and managed
operations that improve the effectiveness of its
clients businesses

• 5th largest worldwide IT Consulting company, 1st
  European
• Annual revenues over 5 bn
• 48,000 employees
• In 50 countries
• RD mainly in Spain

4
Worldwide Presence
5
Global strategy on ETPs

• ETP is an important asset challenge ()
• ETP requires investment (-)
• Atos is cautious where to intervene
• Nanotech (ENIAC)
• Embedded (ARTEMIS)
• Mobile (eMobility)
• NEM under consolidation process
• Software ETP (S3 SCOUT) under consolidation
  process
• Other options, always under the light of
  coherence, clear definition of role for Atos, and
  impact in Europe and business -gt Not any good
  idea is an ETP

6
ETP simple approach
ETP
ETP
FP7
FP6
FP5
7
ETP simple approach

• Lentius, Altius, Fortius
• Vacuius

ETP
ETP
FP7
FP6
FP5
8
ETP deeper view (1)

• ETP is
• is NOT an instrument of the European
  Commission,
• NOR an Member State project,
• NOR a private banks project
• An ETP exists because companies get together and
  decide to join forces
• Several contributors may support the existence of
  platforms (EC, MS, private banks, companies)
• Ways of contribution by EC
• For the moment, room coffee
• Joint undertaking (art. 171)
• Assisted presence in IP, NoEs, STREPs
• Ways of contribution by MS
• National research programmes
• Art 169 (uncertainty)

9
ETP deeper view (2)

• When is an ETP created?
• An ETP (industry-driven) is created when industry
  observes
• () an industry need/challenge
• (-) an industry concern
• ETP is an autonomous entity, industry-led, and
  industry-driven. Contribution from public
  partners and academia are welcome
• ETP is made for agreeing on research agenda that
  will drive to business (companys target) and EU
  target (growth, jobs, competitiveness)

10
Candidates to ETP
S3 Atos Origin Nokia Engineering Siemens Softwar
e AG Symbian Thales Telecom Italia Telefónica Ob
jectWeb
Joint initiative
2004
2005
Dec
Nov
Oct
Sep
Apr
Mar
Feb
Jan
SCOUT Atos Origin BT HP IBM SAP Telefónica
11
ETP on Software (17)

• S3 and SCOUT merged
• Two merging teams were created
• Governance team (Atos, SAP, BT, Engineering)
• Vision Document team (Atos, SAP, Engineering, HP,
  Thales)
• S3 SCOUT is a 14 company-wide platform

12
S3 short history (1)

• Technological Initiative ID Card
• Preliminary works since July 2004
• First Plenary Meeting 12-October-2004
• Outcome vision document and initiative launch
  (FP7)
• Organisation and roadmap
• Weekly conference calls (Core Group)
• 14-Dec-2004, Second Plenary Meeting
• 15-Dec-2004, Discussion with Member States
  (Mtries of ST)
• 22-Dec-2004, Rome
• 12-Jan-2005, Brussels
• ...

13
S3 short history (2)

• Who is there?
• Participants (open)
• Software System Development 14
• Software Product 5
• Industrial Users 3
• Telecom 3
• Mobile 2
• Research 8
• Core Group
• Atos Origin
• Engineering Ingegneria Informatica SpA
• Nokia
• ObjectWeb
• Siemens
• Software AG
• Symbian
• Telecom Italia
• Telefónica
• Thales

14
S3 short history (3)

• Nokia
• ObjectWeb
• Politecnico di Milano
• SAP
• Semantic Systems
• Siemens
• SINTEF
• Società Generale dInformatica
• Software AG
• Symbian
• T-Systems
• Telecom Italia
• Telefónica
• Telelogic
• Telvent
• Thales
• TSSG

• Who is there?
• Participants (open)
• ABB
• Alcatel
• Archimedia
• ATC
• Atos Origin
• BAE Systems
• CEA
• City University
• Engineering I.I. SpA
• European Dynamics
• European Software Institute
• EuroTEX
• FIAT
• Ibermática
• ILog
• INRIA
• Interactive Object Software

15
S3 short history (4)

• Integration and cohesion in research activities
  in the European Software Industry is progressing
  from being a good idea to a real need
• Why?
• New technological waves require a common
  perspective
• Service engineering
• Ambient intelligence
• Semantic interoperability
• Large investments in research call for joining
  forces
• Specific concerns (e.g. global threats) for
  European Software Industry should be tackled
  together

16
S3 short history (5)

• Global Threats
• U.S. domination in packed consumer software and
  operating systems
• Few room/development for European companies
• Offshore software factories in Third Countries
• Globalisation effect
• Economic factors we cannot modify
• Unlikely other markets, software does not imply
  transport costs
• The effect of software BPO will only grow (prices
  will remain low, quality will remain high or get
  higher)
• Long-term industry-scape
• European IT companies as sales agents for
  European customers of the Asian companies devoted
  to software production

17
S3 short history (6)

• Consequences
• European software companies have to rethink the
  way they do business
• Investigate the points where we can act
• Act !!

18
S3 short history (7)

• Keep the European software industry competitive
  advantage (BUILD ON KNOWLEDGE)
• Find the path ahead of European industry for the
  coming years (Key Evolution Elements that will
  allow European software to evolve above 3rd
  countries software factories)
• Tackle European software industry needs
• Avoid shortage of professionals in the KEE
• Resiliency to external attacks
• Keep/Care European users through user-centred
  engineering
• Attack other markets

19
S3 short history (8)

• Our sector
• gt 1 million workers in Europe
• Roughly 0,5 of labour force
• 205,000,000,000 Euros sector turnover in 2004
• Expected growth of 4,4 for 2005
• Roughly 2 of European GDP
• Is it worth it to help it prevent threats?
• Hence... lets do it!

20
S3 short history (9)

• Main Goal and Actions
• The main goal of this initiative is to
  consolidate the creation of a joint undertaking
  of companies, research centres and institutions
  that, counting on resources of their own and from
  external donors, and in line with regulatory
  authorities in Europe, carry out the following
  actions
• Establish a vision
• Identify the KEE
• Apply the KEE
• Evaluate and measure actions and effects,
  modifying 1, 2, and 3

21
S3 short history (10)

• 1. Establish a vision
• Establish a clear vision of the situation of the
  market of Software, Services, and Systems in
  Europe, its evolution in the last years, and its
  forecasts for the coming years, concerning
• Existing technical trends
• Thorough analysis of the most important
  technologies for the evolution of S3
• Economic vision last years and coming years, in
  relation with those technologies

22
S3 short history (11)

• 2. Identify the KEE
• Identify the Key Evolution Elements (KEE) that
  may drive up the forecasts for the coming years,
  in a way that both national economies, Europe
  continental economy and, if applicable, worldwide
  economy, result in clear profit. This information
  will also be provided to the European Commission
  and National Authorities as input for deciding
  future research trends

23
S3 short history (12)

• 2. Identify the KEE (contd)
• Key Evolution Elements preliminarily identified
• The aware computer comprising the basics of
  semantics and the awareness of concepts
  (ontologies), self-awareness and awareness of its
  own resources (tackling semantic grid), and
  awareness of physical locations (advanced GIS,
  based on different sources, like GPS, Galileo,
  using connectivity standards, architectures and
  infrastructures like INSPIRE).
• The trusting computer advanced PKI mechanisms
  for secure identification of source and
  destination of information, as well as all
  possible ways of assuring the communication path
  for avoiding tapping or fraudulent emission.
• Total ubiquitous computing, including computing
  based on wireless usage, RFID, support for
  ambient intelligence, mobile applications,
  satellite connections, wireless internet,
  autonomous sensors and actuators (pervasiveness).

24
S3 short history (13)

• 2. Identify the KEE (contd)
• Key Evolution Elements preliminarily identified
• Advanced technologies paving the way for the
  alive software shared Free/Open Source
  Software, adaptative algorithms, reconfiguration,
  web services as a tool for run-time service
  aggregation and the complex application of
  aggregation to solving complex problems, process
  composition, component engineering and component
  interaction up to full-fledged fourth level
  component interaction, MDA, and dynamic grid
  applications.
• Advanced technologies paving the way to let the
  user harness the power of IT to its maximum
  extent requirement engineering, and service
  engineering as a superset of that, usability
  techniques, complex legacy evolution algorithms
  in order to incorporate new systems to users
  depending on old systems, vertical downstreaming
  on user markets with specific needs, like eGov,
  or eHealth.

25
S3 short history (14)

• 3. Apply the KEE
• Apply the identified Key Evolution Elements in
  the contents of the coming Framework Programme(s)
  by supporting research and development activities
  in Europe using the methods of implementation
  described in chapter 5 of Guidelines for future
  European Union policy to support research from
  16-06-2004, Doing better to do more
• Actions enabling Implementation methods
• Establish a management structure in order to
  develop Article 171 of Treaty Establishing the
  European Community (OJEC 12-12-2004), that is
  capable to carry out small-scale, medium-scale
  and large-scale RTD actions that do apply the
  identified Key Evolution Elements.

26
S3 short history (15)

• 3. Apply the KEE (contd)
• Actions enabling Implementation methods (contd)
• Pave the way, in line with Article 169 of Treaty,
  and as explicitly mentioned in chapter 5 of
  Guidelines, for incorporating national research
  programmes and inter-national research
  co-ordination to the fulfilment of the KEEs, and
  define clearly the communication matrix with the
  different national authorities in a way that all
  companies, research institutions, European
  Commission and national authorities work towards
  the same goal and in a co-ordinated way.
• Foster, with the support of the management
  structure, the creation of specific TENs
  (Trans-European Networks) with concrete
  sub-objectives, which comply with the KEEs.
• Convert the mgt structure into a transparent,
  private-run, solid, economic and management
  platform that can be used used by the European
  Commission for implementing Externalised
  Management as mentioned in Articles 47 and 48 of
  Guidelines, concerning specific research fields
  or sub-fields.

27
S3 short history (16)

• 4. Evaluate and measure actions and effects
• Evaluate in a continuous way the procedures of
  application of KEE in the contents, measuring the
  effects and impact of every single RTD action in
  the European market, at micro-scale, medium-scale
  and large scale results. Results of this
  continuous evaluation will be used to modify
  periodically the vision established in 1, update
  the KEEs identified in 2, and correct the actions
  developed in 3.
• ? Highlight on IMPACT

28
Ubiquitous
In the past, RTD to high-added value IT
Technologies was a good factor to GROW
Aware
Trusting
alive
user
Currently, RTD to high added value
IT Technologies is a NEED
USA, Others
Europe
Packed software
Application- Specific Software
National Research Programmes and FP7 should be
built taking these elements into account
Third countries
Operating Systems
Low-price Software Factories
29
Joint S3SCOUT initiative
Approaches on governance being discussed
30
Baltic presence in ETPs under construction (to my
knowledge)

• Estonia
• Latvia
• Lithuania

31

• Paldies! - Uzredzešanos
• José M. Cavanillas
• International Activities Director
• jose-maria.cavanillas_at_atosorigin.com