1 / 39

WP6: Status & Achievements Project Management Report

WP6: Status & Achievements Project Management Report. Ricardo Sanz Universidad Politécnica de Madrid. Contents. HRTC Project overview Project Context and Objectives Work Organisation Previous Review Recommendations Actions Present status Achievements Numbers Future. The HRTC Project.

constance-mosley
Download Presentation

WP6: Status & Achievements Project Management Report

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. WP6: Status & AchievementsProject Management Report Ricardo Sanz Universidad Politécnica de Madrid WP6 / R.Sanz / Lund 16 September 2003

  2. Contents • HRTC Project overview • Project Context and Objectives • Work Organisation • Previous Review • Recommendations • Actions • Present status • Achievements • Numbers • Future WP6 / R.Sanz / Lund 16 September 2003

  3. The HRTC Project An Step towardHard Real-time CORBA WP6 / R.Sanz / Lund 16 September 2003

  4. Complex Control Systems • Control systems are software-intensive applications that are becoming extremely complex as new functionality is required from them. • Software complexity is a major engineering challenge • Distributed object technology and middleware have proved useful in dealing with the integration problem in complex systems WP6 / R.Sanz / Lund 16 September 2003

  5. HRTC Project Objectives • Start R+D activities in CORBA for hard real-time distributed control: • Elaborate requirements for CORBA-based controllers • Foster activity inside the OMG • Domain Analysis and Domain Architecting • Build two testbeds • Robot Control Testbed: tight timing, performance • Process Control Testbed: heterogeneity, scalability • Build a pluggable transport over predictable networking hardware WP6 / R.Sanz / Lund 16 September 2003

  6. Milestones • Milestone MS1 • Domain analysis of CORBA control systems (CCS) • Analysis and design of real-time protocols • Specification and design of testbeds • Milestone MS2 • Implementation of HRT Protocols for RT CORBA • Non-HRT testbeds • Core set of CCS architectures • Milestone MS3 • HRT testbeds • Testbed testing and documentation • CCS engineering handbook WP6 / R.Sanz / Lund 16 September 2003

  7. Work Organisation Team and Workpackage Structure WP6 / R.Sanz / Lund 16 September 2003

  8. Work Packages • CORBA Control Systems • Hard Real-time Protocols • Robot Control Testbed (RCT) • Process Control Testbed (PCT) • Dissemination • Management WP6 / R.Sanz / Lund 16 September 2003

  9. Project Testbeds • Robot Control Testbed • Robots, sensors, native controllers • Focus on temporal aspects • Process Control Testbed • Continuous process, commercial DCS, simulation, embedded devices • Focus on integration WP6 / R.Sanz / Lund 16 September 2003

  10. Previous Review Brussels, Jan 22, 2003 WP6 / R.Sanz / Lund 16 September 2003

  11. Recommendations • 8+4 recommendations • 8 from the review report • 4 from the addendum • The consortium took the necessary steps to implement recommendations of the HRTC 1st Review Report and addendum. WP6 / R.Sanz / Lund 16 September 2003

  12. Recommendation 1 • “The deliverables provided were of varying standards and quality. It should be noted that the deliverables for WP4 set the appropriate standard and project partners should aim to emulate this in all future deliverables.” • Quality control measures have been enhanced to ensure quality and homogeneity. WP6 / R.Sanz / Lund 16 September 2003

  13. Recommendation 2 • “For WP2 discussing ‘protocols’ the presentation given clarified many things that were not clear from the deliverable. The partners should ensure that future deliverables provide a clear, concise and complete description of the work done.” • Enhanced releases of the protocol design deliverable have been produced. WP6 / R.Sanz / Lund 16 September 2003

  14. Recommendation 3 • “In the presentation for WP3 emphasis was placed on the TrueTime and JITTERBUG tools that had been developed at the University of Lund. The use of these tools is not clearly stated in Annex 1 and little was said about them in the deliverables provided. The work on co-simulation and timing analysis using these tools was thought to be very useful and it would be helpful to explain how these tools will be used in the definition of requirements and the analysis of systems.” • The document HRTC 057 was prepared and submitted. It was accepted with qualification. WP6 / R.Sanz / Lund 16 September 2003

  15. Recommendation 4 • “The criteria and method for evaluation proposed in Evaluation Plan D6.2 was thought to be insufficient. The partners should produce a revised version at the end of month 8 that expresses evaluation criteria on tangible outputs. The partners should concentrate on identifying outputs that demonstrate the success of the project.” • A new version was released (2.0) that was accepted with qualification. WP6 / R.Sanz / Lund 16 September 2003

  16. Recommendation 5 • “The late / delayed deliverables D1.1, D2.2 and D3.3 should be provided latest at the end of month 8; no further delay would be considered acceptable.” • Done. WP6 / R.Sanz / Lund 16 September 2003

  17. Recommendation 6 • “The Dissemination and Exploitation plans presented were acceptable for this stage of the project and it is clear that activities within the OMG have started very well. However, the strategy for commercial exploitation of the results was not clear. Decisions should be made for the final plan to be provided at the end of the project. The final plan should consider the target market and the potential for strategic partnerships. Also the consortium is encouraged to circulate the questionnaire to as wide an audience as possible.” • Done. WP6 / R.Sanz / Lund 16 September 2003

  18. Recommendation 7 • “For planning the routes for exploitation the consortium is strongly advised to put a consortium agreement in place that discusses and clarifies among the partners the Intellectual Property Rights (IPRs).” • Done. A Consortium Agreement has been prepared and is in lawyer hands for approval and signature. WP6 / R.Sanz / Lund 16 September 2003

  19. Recommendation 8 • “The consortium should reassess the project progress/status at the end of month 9 when the impact of the current delay on the project is clearer. At that moment of time a decision should be taken whether an extended project duration is needed or not. The request made for an extension of two months should be reconsidered at that moment of time, i.e at the end of March 2003.” • The decision to ask for extension was taken and the extension was granted. WP6 / R.Sanz / Lund 16 September 2003

  20. After-review Deliverables • Sent after the review: • D1.1 Domain Analysis • D3.3 RCT Procurement • HRTC 057 TrueTime and Jitterbug • D2.2 Protocol Specification • D6.2 Evaluation Plan (second version) WP6 / R.Sanz / Lund 16 September 2003

  21. Additional Actions: D1.1 • “it remains unclear how the timing analysis or control techniques to compensate for delays presented fed into the HRT CORBA” • “clarification on the above open issues should be provided at the next review.” • Clarifications will be provided in WP1 presentation WP6 / R.Sanz / Lund 16 September 2003

  22. Additional Actions: D2.2 • “deliverable suffers from the said weaknesses and seems to be not yet complete; it would benefit from a revision” • A new release has been provided • HRTC D2.2 HRT Protocol Specification v 1.2 WP6 / R.Sanz / Lund 16 September 2003

  23. Additional Actions: D6.2 • Some concerns regarding testing procedures and depth of tests in both testbeds • To be addressed during testbed testing WP6 / R.Sanz / Lund 16 September 2003

  24. Additional Actions: 057 • “Any ‘additional enhancements’ should be reported in an ‘addendum to HRTC 057’ and presented during the final review of the project” • They will be reported in WP1 presentation and new release of HRTC-057 WP6 / R.Sanz / Lund 16 September 2003

  25. Present Status As of M14 WP6 / R.Sanz / Lund 16 September 2003

  26. Expected/Actual Status • Planned for Milestone 2 • Implementation of non-HRT RCT • Completed* • Implementation of non-HRT PCT • Completed • Implementation of HRT Protocols • Completed (Prototype) • Core set of CCS architectures specified • Completed WP6 / R.Sanz / Lund 16 September 2003

  27. Expected/Actual Status • Planned for Milestone 3 • Implementation of HRT RCT • Ongoing • Implementation of HRT PCT • Ongoing • Testbed Documentation • Ongoing • Engineering Handbook • Ongoing WP6 / R.Sanz / Lund 16 September 2003

  28. WP6 / R.Sanz / Lund 16 September 2003

  29. WP6 / R.Sanz / Lund 16 September 2003

  30. D1.2 CCS Domain Architectures UPM D2.2 HRT Protocol Specification (revised Version) SCI D2.3 HRT Protocol TUV HRTC 066 RTE Transport Definition ULUND HRTC 067 TTP Transport Definition TUV D4.4 Non HRTP PCT Implementation UPM D5.2.7 CSWG White Paper UPM D5.2.8 HRTC Poster at OMG RT-DOC Workshop UPM D5.2.9 CORBA on TTA at OMG RT-DOC Workshop TUV D5.4 HRTC Project Web Page SCI D5.6 Exploitation and Use Plan SCI HRTC 082 HRT CORBA Market Study SCI D6.5 Quarterly Report (Q3/M9) UPM D6.6 Periodic Report M12 UPM Deliverables for the Review Id Title Lead WP6 / R.Sanz / Lund 16 September 2003

  31. Efforts Used during the project WP6 / R.Sanz / Lund 16 September 2003

  32. Efforts by WorkPackage WP6 / R.Sanz / Lund 16 September 2003

  33. Efforts by partner WP6 / R.Sanz / Lund 16 September 2003

  34. Future Activities and plans for the rest of the project WP6 / R.Sanz / Lund 16 September 2003

  35. Next Milestone • MS3: • Scheduled for M15 • Operational testbeds with new protocols • Tests performed • Final Documentation WP6 / R.Sanz / Lund 16 September 2003

  36. Work per Package (MS3) • Complete Engineering Handbook • Testing • Implement HRT robot testbedPerform tests + document • Implement HRT process testbedPerform tests + document • OMG RFI in CSWGPrepare journal papers • Perform project evaluation and reporting WP6 / R.Sanz / Lund 16 September 2003

  37. Pending Documents (M15) D1.3 CCS Engineering Handbook D3.6 RCT Testing D3.7 RCT Documentation D4.6 PCT Testing D4.7 PCT Documentation D5.2.10 Control Systems RFI D6.9 Periodic Report M15 D6.7 Project Evaluation Report D6.8 Final Report HRTC075 TrueTime and Jitterbug 2.0 WP6 / R.Sanz / Lund 16 September 2003

  38. Questions ? WP6 / R.Sanz / Lund 16 September 2003

  39. UPM LTH TUW SCI HRTC IST 37652

More Related