Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

OSGi and Next Generation Trains - Jens Haeger, Deutsche Bahn

415 views

Published on

OSGi Community Event 2008

Published in: Technology
  • Be the first to comment

  • Be the first to like this

OSGi and Next Generation Trains - Jens Haeger, Deutsche Bahn

  1. 1. Page 1 Mobile Integration Platform (MIP) A Project of Deutsche Bahn AG Berlin den 10.06.2008 Deutsche Bahn AG DB Systemtechnik Jens Haeger, Roman Roelofsen
  2. 2. Page 2 Infrastructure and Services Modernization of track infrastructure and stations Expansion of high-speed network Expansion of IT and telematics networks Passenger Transport New regional and long-distance vehicles in service New mobility offers such as Call-a-Bike, DB Carsharing, RailNet; exact-address information in Internet, Cityticket available More international connections Transport and Logistics Expansion of air, ocean, road, and logistics businesses Strong growth noted in Germany and abroad Establishment of logistics chains with rail as a strong backbone We have become a leading operator of transportation networks
  3. 3. Page 3 DB is pursuing three essential strategic goals DB Group Further improve core business Expand transportation networks Create economies of scope Organic Growth, Cooperation and M&A Control strategic elements in the transportation systems, conjoint development of infrastructure and transportation systems Cross Selling and innovative solutions in the transportation systems Cut costs by using economies of scale across all business units Further restructuring and optimization of the core business Centralizing control of key matters DB’s strategic goals
  4. 4. Page 4 Requirements to data communication from vehicles to stationary platforms • Increasing mobile customer needs leads to intense growth ⇒ new services for travelers has to be developed and supplied • Rapid technical innovation ⇒ enable new applications for customers Answers today, by: • stand-alone solutions, reasons are: ­ preventing increasing complexity ­ decreasing project coordination ­ impulse to „small and keen“ solutions • individual solutions because: ­ different vendors are involved ­ mostly no one risk a view over the horizon conclusion! Mobile Integration Platform (MIP) Initial situation (1)
  5. 5. Page 5 • only small integration of applications • singular, different solutions • multiple radio path (antennas, modems, accounts) • only few multiple utilization each application has own methods / and singular infrastructure costs für investments, maintenance and operations are high LCC Mobile Integration Platform (MIP) Initial situation (2) life cycle costs
  6. 6. Page 6 IT Vehicles The challenge: how can we reasonable connect both life cycles? 2 to 5 Years 15 Years (Redesign) 30 Years (minimum) Mobile Integration Platform (MIP) Different life cycle: Vehicle – IT-Technology
  7. 7. Page 7 Mobile Integration Platform (MIP) Different life cycle: Vehicle – IT-Technology How can we connect reasonable both life cycles (IT – Vehicles) ? Assumptions: • Vehicles have to stay operational over the whole life cycle (guideline) • Technological changes in IT has to be free of negative impact to vehicel sector (guideline) Challenge: • To make useful new technology innovations, which enables new applications • Constant increase of need of informations by travelers and vehicle owners
  8. 8. Page 8 Mobile Integration Platform (MIP) Objective Creating a unique base of modern data communication supporting processes from and to vehicles as an onboard integration solution for – Information - mining – Information - allocation – Information - distribution – Information - processing
  9. 9. Page 9 Mobile Integration Platform (MIP) Basic requirements • High modularity (“modular design”: flexible configuration, based on consistent components for different profiles of usage), thereby scalability from “top to down”; • Adoption of a basic concept, which should avoid any impact of applications each other, thus decrease efforts for admittance and sample testing; • Integration capability in existing system landscape of vehicles, though the product-responsibility remains at vendors of connecting components; • Platform-independency (standard software-architecture, closed portable software-module, consistent concept for developing, operating, maintenance, software-allocation, configurations-management,...); thereby easy maintenance and administration; • High reliability (Usage of „state of the art“ technology; under compliance of standards); • Common extensibility by capsulating the implementation and interfaces; • Flexibility regarding the usage different existing and possible future transmission channels for the train <-> ashore communication;
  10. 10. Page 10 Mobile Integration Platform (MIP) Open system architecture for a modular approach • Open infrastructure • Open software architecture • Capsulated, predetermined hard- and software-interfaces • Complete and open definition of mobile - - - stationary communication Therefore we need
  11. 11. Page 11 Mobile Integration Platform (MIP) Basic design of future system architecture
  12. 12. Page 12 Mobile Integration Platform (MIP) Stages of expansion MIP Hardware MIP Software APIDatastorage Operationsystem OSGI-Framework Basic Services APIKonAdminSysMagm APIOperationstatus APISelf-Diagnosis APIcommMgr MIP basement Possible MIP increments Applications Optional ServicesUnit Services APIclock API… APIDiagnostic API… APIDiagnosticFA API… APISingleSeatIndicator APIEPAFA Java-VM
  13. 13. Page 13 Mobile Integrationsplattform (MIP) Goals of Deutsche Bahn AG 1st Step To make MIP available for concrete vehicle-projects 2nd Step Development of MIP to an industrial standard 3rd Step European-Norming of MIP

×