The OSMOSE project is user- and pilot-driven: two partially overlapping design-development-integration-validation iteration cycles are foreseen: the former will take place between M1 and M24 (Milestones I, II, III and IV), the latter between M18 and M36 (Milestones IV, V and VI).
Since the very beginning of the project, WP2 (user requirements) will be launched to analyse the as-is business scenarios in the automotive and aerospace industry in order to discover common models, patterns and business interactions for driving architecture (WP3) and ICT infrastructure design and development (WP4-5), to identify user requirements for the Sensing-Liquid Enterprise Applications (WP6) and to provide the two pilots with the conceptual and technical framework for assessing business benefits during experimentations (WP7).
Since M1, the design of the system architecture could start in WP3 to drive all the subsequent software developments and to allow a coherent and efficient system integration and technical functional and non-functional evaluation
Since M1, the design of the system architecture could start in WP3 to drive all the subsequent software developments and to allow a coherent and efficient system integration and technical functional and non-functional evaluation.
The ICT infrastructure for Sensing-Liquid Enterprises will be designed and developed in WP4 and WP5 which will be conducted in parallel starting from M6. WP4 is in charge of the backend infrastructure made of a blending SOA+EDA bus and of the basic osmosis processes of interchange between worlds; while WP5 is in charge of the front-end infrastructure made of actors-agents-avatars interacting and exchanging-sharing knowledge and experiences gained in one world and then transferring them orderly by osmosis membranes. First prototypes of the ICT infrastructure back- and front-ends will be available at M12.
WP6 (Sensing-Liquid Enterprise Business Applications) starts from existing applications (quality inspection in production and operations monitoring in maintenance) and extends them, according to WP3 architectural guidelines, to the Sensing-Liquid enterprise paradigm, thanks to the ICT infrastructure developed in WP4 and WP5.
WP7 is in charge of piloting, experimenting and assessing the OSMOSE applications in realistic industrial environments provided by our two industrial end users in automotive and aeronautics. The first experimentation will be conducted in 6 months and concluded at M24. Such a solution engineering process will be repeated a second time between M18 and M36, so partially overlapping with the first iteration cycle but receiving important feedback, lessons learned and business/technical indicators measures, so that to improve the impact of the solutions in the test cases.
WP8 is in fact in charge of the dissemination and exploitation activities, with the final aim to generate a wofold positive impact i) of the Sensing-Liquid enterprise concept in the scientific environment but mostly ii) of the innovative Sensing-Liquid enterprise applications in the IT and manufacturing industries.
Work Package description
|Work Package No||Work Package Title||Type of Activity||Lead (Short Name)||Person-Months||Start Month||End Month|
|WP1||Project Management & Coordination||MGT||PIKS||31||1||36|
|WP2||User Scenarios, Requirements, Proof of Concepts and Business Validation||RTD||UNIN||52||1||36|
|WP3||Reference Architecture, Integration, System Testing Technical Evaluation||RTD||CAS||59||3||33|
|WP4||Osmiotic Middleware for Liquid-Sensing Enterprise||RTD||DFKI||75||6||30|
|WP5||Front-End Human Stargate||RTD||PIKS||65||6||30|
|WP6||Sensing-Liquid Enterprise Business Applications||RTD||TXT||109||9||33|
|WP7||Proof of Concept, Pilots and Experimentations||DEM||INNOV||73||12||36|
|WP8||Dissemination and Exploitation||RTD||RPLY||36||1||36|