PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf

More documents

Recommendations

Info

Final Report PRE-DRIVE C2X 29.9.2010 bench environment addresses the validation of the prototyped components and the integration in a laboratory environment, and the field operational test environment supports the tests of the integrated complete system in a real world-environment. Based on the edited test objectives, which address all test environments, WP4000 deduced the requirements of the test system and allocated them to relevant test system’s environments. While WP2000 addresses the specification and implementation of the simulation environment and WP3000 provides the test bench, WP4000 has specified and realized the field operational test environment. Based on the given field operational test system requirements, WP4000 allocated the requirements into functional groups and identified a corresponding tool set, which is required to prepare, conduct and evaluate tests. There was also a tool developed to define and specify tests: the scenario editor. The resulting architecture, which is described in D4.2 “Requirements and specification of testing architecture and procedures and requirements and specification of test management centre” and D4.3 “Requirements and selection of test and trial sites (A), specification and integration of test management centre (B) and implementation of test management tools (C)”, is also shortly illustrated in chapter 2.3.4 Two tools are required for monitoring tests in real time: one is deployed at the ITS station (ITS testing unit) in order to collect relevant data from the system and initialize the transfer to the second tool. That is the one accessible for a central test operator for test monitoring (test monitoring component). In addition to that, this test operator should be able to influence the test based on what he or she monitors. Therefore, WP4000 specified a control component. In order to evaluate tests and validate developed prototypes, the test run must be recorded. That means that relevant data should be logged and transmitted (not necessarily in real time) to a central database such that log data could be employed for evaluation and validation analysis. In addition to these functional components, which address user’s requirements directly, WP4000 identified some “back-office” components, which support the tools. These provide components to manage a reliable data transmission for monitoring and log data as well as a control data. A database was designed to store all test related data. That ranges from defined test cases to logged test run data. The scope and design of all components were harmonized with WP5000 requirements and expectations, since that work package was responsible to conduct the test and therefore had to employ the provided tools. Based on the specification of the test tools, WP4000 started the implementation of all sub-systems. The specification included in deliverable D4.2 “Requirements and specification of testing architecture and procedures and requirements and specification of test management centre” was revised based on the experience gained during the development process. That reasoned some delay in the overall integration of all sub-components in this work package. The integration was done through an iterative process. WP4000 organized an integration workshop in Berlin, in which the integration of all test tools was verified with all relevant partners. Besides, overall integration meetings in Brunswick (April 2010) and Ulm (June 2010) were used to test the field operational test environment, also in cooperation with the PRE-DRIVE C2X systems developed in WP3000. WP4000 was also responsible to review potential tests sites, which could be considered for large-scale field operational tests. This work package identified several potential test sites operated by specialized companies for common vehicle tests and also test sites prepared for field operational tests. WP4000 edited initial Deliverable D0.3 Version 1.0 13 Final Report
Final Report PRE-DRIVE C2X 29.9.2010 requirements for test and trial sites. Relevant operators of such test sites were contacted. A questionnaire was sent to test site operators. Based on preliminary results, the best suited candidates were identified. WP4000 representatives visited selected sites and reviewed them. Based on that, a recommendation for test sites was provided, which are suitable for large-scale field operational test. 2.2.5 WP5000 Demonstration and impact assessment This work package had two major objectives: First, the PRE-DRIVE C2X Prototype System which was integrated in test cars and Road Side Units should be verified. Well matured use cased had to be tested in real life scenarios on private and public roads. The test management centre had to show its performance. Simulations should show traffic and safety impact. Second, the PRE-DRIVE C2X system had tro be evaluated from the socio economic and business economics point of view using tools that had to be developed for this purpose in the project as well. The work was divided into three tasks that are discussed in more detail in the following chapters. 2.2.5.1 Demonstration and test of prototype system WP5100 planned and executed two integration tests and a “Friendly User Test”. The 1st Integration Test was conducted in Braunschweig where a first set of use cases was tested on the ground of a former Bundeswehr barrack. This site was selected and organized by the DLR. This first test that took place from April 19 to 20, 2010 was not executed on public roads. During the tests the software bundles were checked and the parameters of the use cases were evaluated. Eight PRE-DRIVE C2X demonstration vehicles and three Road Side Units underwent this testing. Figure 6 shows the demonstration vehicles as well as one Road Side Unit. Figure 6: Test fleet in Braunschweig On April 20, also the “Friendly User Test” was carried out. 30 test subjects were selected from DLR staff. In a first step they filled out the first part of a questionnaire prepared for these tests, which queried the general attitude to vehicle communications and the expectations regarding usability and impact. Because meeting the users’ expectations is so important for the rollout of vehicle communication, 14 more subjects selected by PRE-DRIVE C2X partner facit completed this part. Deliverable D0.3 Version 1.0 14 Final Report
Page 1 and 2: Deliverable D0.3 Final Report Versi
Page 3 and 4: Legal disclaimer PRE-DRIVE C2X 9/29
Page 5 and 6: PRE-DRIVE C2X 9/29/2010 Table of co
Page 7 and 8: PRE-DRIVE C2X 9/29/2010 1 Managemen
Page 9 and 10: PRE-DRIVE C2X 9/29/2010 With the po
Page 11 and 12: PRE-DRIVE C2X 9/29/2010 2.1.5 WP500
Page 13 and 14: Final Report PRE-DRIVE C2X 29.9.201
Page 23: Final Report PRE-DRIVE C2X 29.9.201
Page 75 and 76:
Final Report PRE-DRIVE C2X 29.9.201
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
PRE-DRIVE C2X 29.09.2010 6 Report o
Page 127 and 128:
PRE-DRIVE C2X 29.09.2010 6.1.5 E: S
Page 129 and 130:
PRE-DRIVE C2X 29.09.2010 6.1.8 H: U
Page 131:
PRE-DRIVE C2X 29.09.2010 3. MEDICAL
show all

PRE-DRIVE C2X Deliverable D0.3 Final report_20100929.pdf

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?