is divided in three modules in order to be adapted to different levels of motorsport or teams:

Transcription

1 page 1 of 8

2 It includes: is divided in three modules in order to be adapted to different levels of motorsport or teams: : Compilation of information in a single location from everyone involved in track operations Seamless distribution of information to all team members Customisable database Simple importation of data Generation of automatic reports Tyre package and heating management It includes: : Management of ECU parameters Assignments of team members responsibilities Edition of values and creation of datasets Comparison and merger of datasets or/and files Link to to keep records : Management of issues includes: Customisable workflow Customisable fields and forms notifications Link to to create issues directly from the track is a multi-users database which compiles in a single location the information from everyone involved in track operations. page 2 of 8

3 Synchronise your track and factory-based database in real-time, allowing your personnel behind the scenes at base to monitor what is happening at the circuit. Create all the fields you need for your team, arrange them in views and arrange views in layouts. Attach rights to fields in order to control who can read or write the information. The database can be filled in manually. Moreover, link to the telemetry in order to automatically create runs and laps, and import some of the car s information. In addition, you have the possibility to import the data from Excel (car setup). allows you to automatically generate reports using data already stored in the database, for the debriefing or for your records. Create your own templates in order to generate highly customised reports. page 3 of 8

4 Manage your tyre package and tyre heating for the event with the Tyre set manager. Or perform all kind of actions outside with Pyton scripts. Manage your Bosch, Magneti Marelli or McLaren ECU parameters directly inside. Create as many targets (ECU) as you need and manage parameters for each software version. Because every team is organised differently, parameters can be arranged in your own groups in order to split responsibilities accordingly. Create new values of parameters with the editor or import some values from your files. You can then choose a value for each parameter in order to create a dataset which can be exported for the ECU. page 4 of 8

5 Compare your datasets or/and your files and merge them to create new ones. Datasets of parameters can be linked to the in order to keep the records of each run setup. Store all the incidents experienced by the team in the multi-projects database. You can then manage each incident until it is solved, or manage all sorts of tasks until they are finished. Every team has a unique working process. Use an out-of-the-box workflow, or create one to match the way your team works page 5 of 8

6 Should your team need more detailed information, create some custom fields in order to fit to your needs and import the additional information from your forms. According to their rights, your team members can read, edit, comment or assign issues. They can create and save filters in order to easily have access to the information they need. As each one needs a different level of notification, allows each member of your team to decide which he wants to receive. On track you can quickly create an issue for the factory from your. Factory based team members will find all the information they need to start working (description of the issue, car setup, track condition ). page 6 of 8

7 is a client/server software. s multi-window interface is easily configurable. Users views can be arranged in different layouts. is the perfect multi-users application. It allows all team members to work together in different areas. is a client/server software. uses a Microsoft SQL database to store information. Each user uses which is connected to the, in order to write or import his own information, or read others. The standard configuration includes two : one on track and one at the factory. They are synchronised live during an event. When the synchronisation is not needed, standalone configurations are possible by using only the track database (In this case, regular backups are required in order to secure data). Configurations with more than two databases are also possible. Notes: There are two levels of There are two versions of available: standalone or multi-servers. available: Windows application or Windows service. Minimum system requirements For standalone: Operating system: Windows 7, 8, 8.1, 10 or Windows server 2008, 2008R2, 2012, 2012R2, 2016 CPU: Core i5 or higher Memory: 4GB RAM SQL Server Express 2008 R2, 2012, 2014, 2016 (limited to 10GB and no replication due to Express version limitations) or SQL Server Standard 2008 R2, 2012, 2014, 2016 (allows report generation with no capacity limitation) For multi-servers: Operating system: Windows 7, 8, 8.1, 10 or Windows server 2008, 2008R2, 2012, 2012R2, 2016 CPU: Core i5 or higher Memory: 4GB RAM SQL Server Standard 2008 R2, 2012, 2014, 2016 (allows replication and report generation, with no capacity limitation) For : Operating system: Windows 7, Windows 8, Windows 8.1 or Windows 10 CPU: Core i5 or higher Memory: 4GB RAM page 7 of 8

8 You can choose either the purchase of licenses or an annual rental. In addition to the purchase of licenses, you can buy an annual support. It includes some assistance by to software users and free updates of the software covering improvements and maintenance. The support is included in the annual rental. Notes: Each module of (notes, parameters, issues) can be purchased independently, with a different amount of users for each of them. Degressive prices according to the number of users. Microsoft SQL server database is not included with. page 8 of 8