1 / 25

The Core Project

The Core Project. Jose Jimenez (project manager). What is the Core platform?. An empty placeholder ?. Or rather…. The core of the PPP?. Our objective. Suppliers. Governments. Manufacturer. Consumers. Retailers. Wholesalers. App/Services ecosystem and delivery framework.

axelle
Download Presentation

The Core Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Core Project Jose Jimenez (project manager)

  2. What is the Core platform? Anemptyplaceholder?

  3. Or rather… The core of the PPP?

  4. Our objective

  5. Suppliers Governments Manufacturer Consumers Retailers Wholesalers App/Services ecosystem and delivery framework Cloud Hosting Internet of Things Interface to Networks What services? Future Internet Core Platform Provisioning – Hosting – Brokering – Consumption

  6. Our (real) objective

  7. Some figures and data Main data 26 partners 5 Universities 4248 Person Months (excl. open calls) Total Funding 41 M€ Open calls 12,3 M€ Total budget 66,4 M€ Three years duration

  8. Driven by developers needs Consumers People Businesses Apps/Services Provider Open Interfaces Platform Provider Provide “Generic Enablers” to the usage areas…and beyond

  9. In collaboration to Usage Areas

  10. How this collaboration is going to proceed? Define, Merge, Extrapolate, Prioritize, … Agile SW development Component Backlog Component Backlog Using a common backlog for WPL and Usage area projects

  11. FI Core Platform Architecture: main chapters Functionality Trust and Security Operations Developer tools Service delivery Cloud Hosting Internet of Things Support Services Interface to the Network and devices

  12. Service delivery Objective: Provision, Composition and delivery of services • Application and service ecosystem and delivery framework Multi channel multi service access Composition and mash-up Business Framework Registry and repository

  13. Cloud Hosting Objective: Handle the provison of computation, networks and software resources Cloud hosting PaaS Enablement Network Edge/cloud proxy mgt. PaaS Advanced management SaaS Basic management IaaS Virtualization

  14. Internet of Things Objective: Interaction with “things”, searchable and accessible IoT process automation IoT resource management IoT Data handling IoT Communications

  15. Data and context management Objective: Transform the data into information Data and context management Context management High level intelligent Services Event management Analysis infrastructure Data Storage and core services

  16. Interface to the network and devices Objective: Open and standardized interfaces to network and devices I2ND Context management Interface to connected devices Interface to Network services Interface to open networking entities Data Storage and core services Interface to Cloud proxies

  17. Security privacy and Trust Objective: Develop a security ecosystem, comprising core and generic enablers Security privacy and trust Generic Security Enablers Context based and compliance Optional security services Data Storage and core services Security monitoring

  18. Development tools, testing and exploitation Objective: Support the community of developers DevComE Testing and deployment API IDE support Forge implantation

  19. Testing and exploitation Objective: Integrated testing and validation Objective: Exploitation and standardization Testing Exploitation Support to Usage cases Standards Integration Exploitation Strategy Internaltestbed Market analysis

  20. Core Platform Instances and Use Case Trials

  21. Market and Scientific councils SMEs University

  22. Our time schedule First year June/September 2011: High level architecture description January 2012: First open call issued May 2012: Reference implementation Second year June 2012: Open call closes September 2012: First FI-WARE testbed January 2013: Second open call issued May 2013: FirstReference implementation Third year June 2013: Open call closes September 2013: second FI-WARE testbed January 2014: Reference implementation May 2014: Fi-Ware final release

  23. In a nutshell Create a solid basis for the Internet of the Future

  24. EVIDENCE OF CHANGE Changing the way European research goes!! “Not only we had so much fun working but we also delivered something useful ”

  25. Thank you!

More Related