1 / 30

F-MAN Project – Final Review Genoa, December 2 nd – 3 rd , 2004

F-MAN Project – Final Review Genoa, December 2 nd – 3 rd , 2004. F-MAN Project Activities & Outcomes. Contents. This presentation provides an overview on: The major technical activities performed The multiple outcomes achieved Some future perspectives Conclusions. F-MAN

conner
Télécharger la présentation

F-MAN Project – Final Review Genoa, December 2 nd – 3 rd , 2004

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. F-MAN Project – Final ReviewGenoa, December 2nd – 3rd, 2004 F-MAN Project Activities & Outcomes

  2. Contents This presentation provides an overview on: • The major technicalactivities performed • The multiple outcomes achieved • Some future perspectives • Conclusions

  3. F-MAN MAJOR ACTIVITIES

  4. WP1 – Users’ needs Interviews & questionnaires to Railway partners CP, PI-SZ, SIGMA-SNCF (their future accessible strategies) • Consultations on organisational conditions and their evolutions (via interviews and questionnaires) with a broader set of rail cargo operators (private and ex-public) • Presentation of Users needs analysis to the RailwayOperators Group (ROG) during a dedicated Workshop for validation and fine tuning

  5. WP2 – Functional Requirements & Architecture • Derived from the Users needs: the overall requirements, and the functional specification • Tool: AFNOR standards to ensure a complete definition of the system; • Based on the “main function identification” of the overall system, the F-MAN systemarchitecture was defined, as well as the one of each single module. • Based on AFNOR application also checking of the consistency of the designed architecture (via a bottom up pocedure).

  6. WP3 – Development Basedon the architecture: development of the 3 modules of F-MAN prototype: • Tracking System Module (TSM) • OBT (GNSS + GSM) • SMS Hub (including the SMS/XML translation & e-mail(!) dispatching) • Digital maps to locate wagons and to show status info • Data Processing Module (DPM) • Data collection from the TSM, storage, processing, and dispatching to the remaining of the ground system(Hub) • ETA functionalities • Asset Management Module (AMM) • Decision Support tool for the User and his key players - FM, OM, OPM and MM • Proposition of proper wagon allocation for the different tasks (orders fulfilment, costs reduction, resource conflict resolution, Customer satisfaction, …) • Deeper interconnection with the DPM to take advantage from the data retrieved from the TSM

  7. WP4 – Integration • Objective: to integrate TSM, DPM and AMM into the F -MAN prototype • development of internal interfaces among SW modules • development of communication interfaces between on-board and ground equipment • Fine tuning of each F-MAN Module for successful integration • Management of different access rights to raise the degree of fulfilment and system’s security • Installation of OBTs on board of wagons and OBT initialisation THE F-MAN PROTOTYPE

  8. WP5 – Testing and Verification (1/5) Three major steps were carried out in WP5: • Plan of the Verification Activities • detailed definition of how to perform the testing and verification of the F-MAN prototype • Functional tests • to verify each single prototype functionality • Field tests • to verify the real operation of the OBT-equipped wagons

  9. WP5 – Testing and Verification (2/5) 1 - Plan of the Verification Activities • Starting from the Functional Requirements: • Identification of each single item to be measured • How to perform the measurement activities • Criteria to be used to evaluate the prototype performance • Define Level of performance to be reached (fulfillment rate of the prototype operation) • Identification of specific corridors connecting Portugal and Spain, France, Italy, Austria, Slovenia and others.

  10. WP5 – Testing and Verification (3/5) 2 - Functional tests • Performed by both developers and Users, in close cooperation • Test of each single F-MAN function and constraint, as well as each sub-function (“item”) • Reporting tables from Users (test results, fulfillment rate and comments per each function)

  11. WP5 – Testing and Verification (4/5) 3 - Field tests • Performed by Users with constant support from developers • Operating of F-MAN wagons along the test corridors and also outside • Testing with different parameters initialised in the OBTs • Collection of data to perform off-line verification and analysis • Interpretation of on-the-field results

  12. WP5 – Testing and Verification (5/5) Thanks to the interest / trust of the partner railways, as well as the ROG Members, F-MAN Partners agreed on continuing running the Prototype in the next months – despite the finalisation of verification (Sep 30th) . Thus, although the end was scheduled months ago, additional FIELD TESTS are still GOING ON. F-MAN Consortium is covering the extra-costs, to increase users confidence and satisfaction, and to step forward into the industrialisation phase of the prototype and into the future potential business.

  13. WP6 – Assessment and Evaluation (1/2) Objective: to achieve a fair assessment of the project results • Preparation of the Evaluation Plan (infos & methods for fair assessment of results) • Final assessment of the project based on: • the Evaluation Plan • The results of Prototype functional & field tests • The results of the added value analysis through an ad-hocSimulation Tool to estimate: F-MAN approach versuscurrent classic management criteria • Preliminary Users acceptance (questionnaire filled in by Users within the Partnership, ROG members and other RCOs) • Peer review processes for all project deliverables before their submission to the EC.

  14. WP6 – Assessment and Evaluation (2/2) Simulations • Design and implementation of a specific SW simulator, developed by the Coordinators SCIRO and UGDIE • Identification of simulation scenarios • Set up of simulation parameters • Running of simulations under different initialconditions • Evaluation of results (WP6)

  15. WP7 – Dissemination & Implementation • Dissemination of generated knowledge and results: • Scientific knowledge • Technological knowledge • Practical relevant results • Dissemination Tools • Set up and constant updating of ROG members (linking of research activities and exploitation) • Participation to International Conferences and publications on scientific journals • Organisation of specific events • Set up and update of www.fman.org (Further details are provided within the special presentation)

  16. WP8 – Project Management Two Coordinators (SCIRO and UGDIE) were focussing commonly(witha defined work division) on the following objectives: • To drive and to monitor the project development and progresses • To verify the milestones and the time schedule • To control the overall performance • To audit the costs • To act as “trouble shooter” whenever troubles arose Suplementary activities to: • issue an effective and efficient Quality Plan at project start • define a detailed Configuration Management (using proper SW tools) • check and release the project deliverables • coordinating the WP leaders on project • prepare the Progress Reports for the EC • prepare the Annual Review documentation for the EC • issue the Final Report

  17. F-MAN MAJOR OUTCOMES

  18. Grouping the outcomes… • The major F-MANoutcome and its valuable assessment results • A number of Project Exploitable Results • The High Level outcomes • The Technological & Scientific outcomes • The Dissemination of scientific knowledge • The future potentialities, based on the positive feedback from important bodies like the UIC and potential customers looking forward to the F-MAN market product The result playing the key role for the future of the F-MAN Consortium is…

  19. F-MAN major outcome …that set of innovative tools capable of improving the sustainability of rail freight transport and the competitiveness of Railway Cargo Operators, going under the name of… THE F-MAN PROTOTYPE

  20. F-MAN Pool management approach Traditional (RIV) management approach Vs. Not within the scope of the F-MAN project DEMONSTRATION or SIMULATION F-MAN Prototype assessment results (1/5) • PERFORMANCE EVALUATION THROUGH COMPARISON WITH REFERENCE CASE • Large number of equipped wagons • Large number of orders to be processed • Systematic utilisation of the approaches • Multilateral agreement on wagons utilisation Simulation did not aim at reproducing the actual management procedures, nor to test the effectiveness of the prototype; but to provide data for a comparison between the theoreticalperformances (of two simplified models of the actual fleet management approaches). Evaluation needs:

  21. PERFORMANCE EVALUATION THROUGH COMPARISON WITH REFERENCE CASE F-MAN Pool management approach Vs. Traditional (RIV) management approach F-MAN Prototype assessment results (2/5) • Orders List Composition Various simulation scenarios : obtaining information on performances evolution with variation of input data and simulation parameter (sensitivity analysis): Orders per day, wagons per order, domestic/international trips • Fleet size and initial distribution Small – Large fleet size • Internal parameters Send back time – Unavailability time

  22. Performance Indicators F-MAN Prototype assessment results (3/5) • Undersized fleet (too many orders for our fleet) • the loaded mileage is increased of about 37% in the worst case; • the increase of loaded mileage is achieved with a striking reduction of empty mileage with respect to the Traditional management; • F-MAN approach reduces by more than 25% the mean time between missions of wagons • Sufficient fleet (just the wagons we need for our orders) • the number of satisfied orders is almost the same; • the movements of empty wagons are significantly reduced with the F-MAN approach; • the results above are achieved with an F-MAN fleet which is 25% reduced with respect to the Traditional one. • Oversized fleet (more wagons than what our orders would need) • F-MAN Pool management approach allows to downsize the fleet of wagons which guaranties fulfilment of all the orders request; • despite the reduced number of wagons, the F-MAN approach achieves 100% fulfilment of orders request with a dramatic reduction as far as movements of empties are concerned; • the reduction of fleet size (25%) is directly reflected in the reduction of the fleet cycle time.

  23. F-MAN Prototype assessment results (4/5) Costs/Benefits Evaluation • regardless the considered scenario (order list, composition,andfleet size), the F-MAN Pool management approach will significantly improve the fleet productivity; • increase of the daily wagon productivity may range from approximately 40 % up to 80% and more; • the impact of the costs of the F-MAN “Product” on fleet productivity is low. The industrial implementation of the F-MAN approach would be a good deal for users (and developers)

  24. F-MAN Prototype assessment results (5/5) Preliminary Users Acceptance

  25. Project Exploitable Results • F-MAN prototype: • Asset Management Module • Data Processing Module • Tracking System Module • Graphical User Interface • Expected Time of Arrival – ETA algorithms • Service, support & training for installation and use • SMS Hub Many of those results bears the potential for future successful exploitation in different business areas & scientific applications

  26. High level outcomes The positive feedback and evaluation received by the three Railway Partners CP, Sigma-SNCF, and PI-SZ, together with: • their explicit request to enlarge the tests and verifications since last September and for other months to come, accepting to bear consequent extra-costs on their shoulders • Further initiatives towards the final industrialisation of the product (e.g. CP and others) • see next presentation

  27. High level outcomes The concrete appreciation expressed by the UIC for the results achieved by the F-MAN Consortium, e.g.: • the number of presentations and meetings to which the Consortium has been invited, and mainly… • by the presence of our UIC Colleague Mr Friso Barstra

  28. High level outcomes The Scientific Publications and Papers presented at International and National Conferences all over Europe, sometimes also following explicit invitation received from the Scientific Management Board of such Conferences… Dissemination topics are scheduled in the following presentation concerning

  29. High level outcomes The business opportunities that are opening in front of the Consortium, which are paving the way to the future industrialisation of the F-MAN prototype Dissemination topics are scheduled in the following presentation

  30. Conclusions • Project activities were planned and carried out to reach the main goals, notwithstanding the multiple obstacles that the Consortium had to overcome • Project outcomes and exploitable results obtained a considerable success among the Railway Partners and ROG members • The end of F-MAN Project is far from being the end of F-MAN activities, as the market is hosting our innovative tools to raise competitiveness of rail cargo transport in Europe

More Related