Who Does What on the Pitwall
15 April 08
Pictured left to right (seated):
Tony Ross, Nico Rosberg Race Engineer
Jonathan Eddolls, Nico Rosberg Data Engineer
Tim Newton, Team Manager
Rod Nelson, Chief Operations Engineer
Mark Barnett, Strategy Engineer
Nick Perrin, Kazuki Nakajima Data Engineer
Xevi Pujolar, Kazuki Nakajima Race Enginner
Tony Ross, NR Race Engineer
Tony leads the track engineering for car 7 and is the primary communicator with Nico when out on track. He also forms the link between the pit wall and Nico’s car crew in the garage, specifying tyre sets, tyre pressure adjustments and set-up changes such as roll bars and springs, as well as determining fuels loads which the mechanics will carry out to his instruction. Prior to each session, he will work in tandem with all the track engineers and the driver to create a programme, planning how many runs the car will make, at what times and in what specification (ie everything from mechanical set-up to brake pad material, fuel loads and tyre choice). He is responsible for logging all of the driver feedback and modifying the run plan according to the prevailing circumstances (eg flags during sessions). For qualifying and race, he will manage the flow of information to the driver about modifications to electronic settings (eg engine maps) to providing information about the position of other cars on the track, their likely strategies and of course informing the driver of flags and safety cars. To a greater or lesser degree, depending on the driver, he is also partly responsible for encouraging the driver, reminding him to maintain his hydration levels and other non-technical communication.
Jonathan Eddolls, NR Data Engineer
The data engineer works in tandem with the race engineer. His primary role is to collate all data from the race car and supply this to the driver and race engineer in a variety of different ways. The most routine method to deliver information to the driver is by the creation of ‘overlays’ or graphical illustrations of driver inputs over the course of one lap compared to another. By showing throttle angles, braking inputs and gear selection, the driver is able to compare his best laps or indeed one of his laps with his team-mate. These overlays will be created by the data engineer in real time during the sessions and displayed on the driver pod when he is in the garage between runs. In consultation with the driver and race engineer, the data engineer also makes adjustments to electronic car settings such as the differentials which will have as important an effect on lap times as mechanical set-up parameters such as springs and dampers. The data engineer will also provide more detailed analysis of track performance to the engineers in post-session debriefs in order to inform wider decisions about car preparation for qualifying and the race.
Tim Newton, Team Manager
The Team Manager has a responsibility to both cars on the circuit, rather than focusing on just one driver. He provides a link between race control (Charlie Whiting) and the race engineers, race strategist and the drivers. He will report FIA decisions accordingly, whether advising the car crews to clear the grid prior to the race start, declaring a wet race, informing the drivers of penalties (such as a drive through) and also making requests of the Race Director (requesting blue flags if a Williams driver is likely to be impeded by a back marker). During qualifying, the Team Manager will instruct the pitwall when a car has been called onto the weighbridge and ensures that any such requests are complied with. One of the most important roles the Team Manager plays is to call the pitstops and communicate with the driver to advise him to box. He then advises the car crews of the driver’s position on the circuit and instructs the pit crew at the appropriate time to bring tyres into the pitlane and prepare for the stop.
Rod Nelson, Chief Operations Engineer
As the senior engineer on the pitwall, Rod’s role is to draw together the various different elements of race operation, from the instructions and information provided by the FIA to the updates from the individual race engineers on the status of their cars and, importantly, from the race strategist. By collating all of these different inputs, Rod will oversee the management of the race strategy and lead decisions to alter the run plan if the race circumstances change (eg modifying Kazuki’s stop plan from two to one stop in Australia). Generally, Rod will not communicate directly with the cars on the track but will advise the Team Manager and the race engineers of his instructions for onward relay to the cars on the track. After the sessions, Rod will lead the debrief process and head the planning for the next session. Together with Tim Newton, Rod has a detailed knowledge of both the sporting and technical regulations and will contribute to official communication with the FIA.
Mark Barnett, Race Strategist
Mark Barnet’s role is to maintain a real time analysis of all of the team’s various strategies, from their tyre selections to their fuel loads. His analysis during the practice sessions enables the engineers to assess the baseline competitiveness of all of the other cars. Based on this and other information, he will model a preferred strategy for Nico and Kazuki for the race, but importantly will run real-time computer analysis so that he can quickly advise Rod Nelson and the race engineers of suggested amendments to the plan if the race circumstances alter, whether due to weather, safety car periods or other eventualities.
Nick Perrin, KN Data Engineer – As per Jonathan Eddolls for Kazuki’s car
Xevi Pujolar, KN Race Engineer – As per Tony Ross for Kazuki’s car






