#  Introduction

##  The FITGEN Project

FITGEN aims at developing a functionally integrated e-axle ready for
implementation in third generation electric vehicles. It is delivered at TRL
and MRL 7 in all its components and demonstrated on an electric vehicle
platform designed for the European market (A-segment reference platform). The
e-axle is composed of a latest generation Buried-Permanent-Magnet Synchronous
Machine, driven by a SiC-inverter and coupled with a high-speed transmission.
It is complemented by a DC/DC-converter for high voltage operation of the
motor in traction and for enabling super-fast charging of the 40-kWh battery
(120 kW-peak) plus an integrated AC/DC on-board charger. The e-axle also
includes a breakthrough cooling system which combines the water motor/inverter
circuit with transmission oil. The FITGEN e-axle delivers significant advances
over the 2018 State of the Art:

  * 40 % increase of the power density of the e-motor, with operation up to 18,000 rpm; 

  

  * 50 % increase of the power density of the inverter, thanks to the adoption of SiC-components; 

  

  * affordable super-fast charge capability (120 kW-peak) enabled by the DC/DC-converter, integrated with single- or 3-phase AC/DC-charger; 

  

  * increase of the electric driving range from 740 to 1,050 km (including 75 minutes of charging time) in real-world freeway driving with the use of auxiliaries. 

  

The FITGEN e-axle will enter the market in the year 2023, reaching a
production volume target of 200,000 units/year by 2025 and of 700,000
units/year by 2030. It is designed to be brand-independent and to fit
different segments and configurations of electric vehicles, including hybrids.
The FITGEN consortium includes one car-maker and three automotive suppliers
for motor, power electronics, and transmission, reproducing the complete
supply chain of the e-axle. Their expertise is leveraged by the partnership
with research institutions and academia, constituting an ideal setup for
strengthening the competitiveness of the European automotive industry.

The aim of deliverable D8.1 is to describe the project management structures
and procedures aimed at ensuring that the above-mentioned objectives are met
and that the results and deliverables of the project are of high quality,
fulfilling the specifications set in the description of work and the grant
agreement. Hence D8.1 is the document defining the quality assurance
procedures for the FITGEN project. To enter in force, the quality plan is
accepted by the full FITGEN consortium. Furthermore, it is intended as a
dynamic document that is kept up to date as the needs of the project evolve
and emerge at the general assembly meetings.

##  Scope of the quality plan

The quality plan encompasses the description of the quality assurance
procedures and is addressed to the project partners for the successful
development of the FITGEN project. Hence the quality plan will guide all
consortium partners responsible for preparing and amending deliverables (e.g.
WP leader, Task leader), the steering committee and the quality coordinator
(who is responsible for reviewing completed or updated parts of the quality
plan) and any responsible consortium partner for approving works to be done by
third parties, to complete deliverables.

##  Description of the process

As an integral part of management planning, the quality plan is prepared in
the early project phase to provide the consortium with the guidelines and
conditions for the execution of the technical activities. To ensure the
applicability of the quality plan at any time, the coordinator should perform
quality reviews throughout the duration of the FITGEN project and shall ensure
that the quality plan is available to all involved partners and that the
requirements regarding the quality assurance are met.

#  Governance structure

##  Overall structure

Figure 1 depicts the governance structure of the FITGEN project. As defined in
the Consortium Agreement (CA), the organizational main structure of the
consortium comprises the general assembly (GA), the coordinator and the
steering committee (SC).

**Figure 1. Governance structure**

##  General assembly

The General Assembly (GA) is the decision-making body of the consortium.
Decisions can refer to all administrative and technical questions of the
project. The GA consists of at least one member per each consortium partner.  
  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

</th>  
<th>

**General Assembly**

</th>  
<th>

</th>  
<th>

</th>  
<th>

</th> </tr>  
<tr>  
<td>

AIT

</td>  
<td>

CRF

</td>  
<td>

TEC

</td>  
<td>

BRU

</td>  
<td>

POLITO

</td>  
<td>

ST-I

</td>  
<td>

GKN

</td>  
<td>

VUB

</td> </tr> </table>

**Table 1. Members of the General Assembly**

##  Project coordinator

AIT is the acting Project Coordinator (PC) for FITGEN. The PC is the legal
entity acting as intermediary between the consortium and the Funding
Authority. The Coordinator shall, in addition to its responsibilities as a
Party, perform the tasks assigned to it as described in the Grant Agreement
and the Consortium Agreement.

##  Steering committee

The Steering Committee (SC) assists the GA and the Coordinator in all
administrative, technical and quality issues. The SC consists of the
Coordinator (AIT) plus one representative of the WP leaders of the consortium,
i.e. CRF, ST-I, BRU, TEC, POLITO. The project-quality assurance will be
reviewed subsequently during the SC meetings considering:

  * the results from project audits and from internal audits; 

  

  * the official project deliverables (reports and prototypes); 

  

  * the corrective action requests and the preventive actions; 

  

  * any project prototype deficiencies and subsystems/parts problems, project participants staff training and adequacy for the tasks undertaken; 

  

  * level of used resources per category and adequacy of spent resources per task. 

  

  
<table>  
<tr>  
<th>

</th>  
<th>

</th>  
<th>

**Steering Committee**

</th>  
<th>

</th>  
<th>

</th> </tr>  
<tr>  
<td>

AIT

</td>  
<td>

CRF

</td>  
<td>

ST-I

</td>  
<td>

BRU

</td>  
<td>

TEC

</td>  
<td>

POLITO

</td> </tr> </table>

**Table 2. Members of the Steering Committee**

##  Governing bodies and responsibilities

###  Quality Coordinator

AIT will also cover the role of quality coordinator shall assist and
facilitate the work of the SC. The Quality Coordinator will monitor the
progress of the FITGEN project and report to the SC any significant deviations
in terms of results, quality, timing and resources spent. Further the Quality
Coordinator will ensure that all project outcomes (like material used in
presentations, conferences and workshops) will have the same high level of
quality.

###  Work Package Leader

The Work Package (WP) Leaders are responsible for the achievement of the
related WP objectives. Their role is to coordinate all efforts of the
participants in the WP and to monitor the progress by checking status and task
quality. The leading beneficiaries for each WP are defined in the GA and
listed here as follows.  
  
<table>  
<tr>  
<th>

**WP No.**

</th>  
<th>

**Work Package Title**

</th>  
<th>

**Lead Participant Short Name**

</th> </tr>  
<tr>  
<td>

1

</td>  
<td>

Electrical architecture of the e-axle

</td>  
<td>

CRF

</td> </tr>  
<tr>  
<td>

2

</td>  
<td>

Power electronics: SiC-inverter, DC/DC-converter and on-board charger

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

3

</td>  
<td>

High speed permanent magnet electric motor and transmission

</td>  
<td>

BRU

</td> </tr>  
<tr>  
<td>

4

</td>  
<td>

Cooling circuit design and control of the e-axle

</td>  
<td>

TEC

</td> </tr>  
<tr>  
<td>

5

</td>  
<td>

Prototyping, testing and qualification of e-axle components

</td>  
<td>

AIT

</td> </tr>  
<tr>  
<td>

6

</td>  
<td>

Integration of the e-axle into the A-segment platform, demonstration and final
assessment

</td>  
<td>

CRF

</td> </tr>  
<tr>  
<td>

7

</td>  
<td>

Exploitation, Dissemination and Communication

</td>  
<td>

POLITO

</td> </tr>  
<tr>  
<td>

8

</td>  
<td>

Project Management

</td>  
<td>

AIT

</td> </tr> </table>

**Table 3. WP Leaders**

###  Task leaders

The role and responsibility of task leaders is similar to that of the WP
leaders but at the Task level (e.g. monitoring and coordinating the technical
progress of the task). The task leaders report to the WP leader. In case of
arising issues, the WP leader discusses the issue with the task leader and
comes up with the proposed solution.

#  Quality Assurance - Reporting

##  6-months progress reporting

To ensure the quality and compliance to project schedule of each WP, each WP
leader is requested to report the technical and financial status of their own
WP in written form to the PC every six months, in concomitance with the date
set for the GA. The reporting begins in Month 7\. To achieve a consistent flow
of information, the status reporting shall be sent to the PC latest 2 weeks
after end of the progress reporting period. The following information shall be
included in the technical section:

  * Performed work and achieved results; 

  

  * Status of each task; 

  

  * Status of each deliverable; 

  

  * Status of each milestone; 

  

  * Gap analysis to original project plan; 

  

  * Assessment of compliance to original project timeline; 

  

  * If applicable, countermeasures to regain compliance to original timeline; 

  

  * Outlook on work items and targets of next reporting period. 

  

The financial content shall be reported by using an Excel template. This sheet
needs to be submitted along with the technical progress information. The
templates to report the technical and financial status will be made available
by the coordinator in due time.

##  Progress report to the EC

At the end of each Reporting Period, progress reports must be submitted to the
EC. According to the Grant Agreement, delivery dates are Month 18 + 60 days
and Month 36 + 60 days. The reports need to include the technical and
financial progress. Reports will be created by the Coordinator with the
support of all WP leaders. The internal 6-month progress reports shall be used
as basis for these documents. To achieve a timely delivery of the reports to
the EC, the following timeline shall be followed:

  * 8 weeks / 60 days before submission deadline i.e. at the end of the reporting period: coordinator requests contents from WP leaders by email; 

  

  * 6 weeks before submission deadline: WP leaders receive feedback from respective Task leaders; 

  

  * 4 weeks before submission deadline: WP leaders provide draft reports to Coordinator; 

  

  * 2 weeks before submission deadline: Coordinator sends out feedback on report draft; 

  

  * at submission deadline, i.e. 60 days after the end of the reporting period: the Coordinator submits the progress report to the EC. 

  

#  Quality Assurance – Creation of Deliverables

##  Dissemination level

In FITGEN, the deliverables can fall under two different confidentiality
levels:

  * Confidential (CO): Only accessible for consortium members (including the Commission Services); 

  

  * Public (PU). 

  

Each Deliverable is assigned a dissemination level (DL), as per Table below.  
  
<table>  
<tr>  
<th>

**Deliverable number**

</th>  
<th>

**Deliverable name**

</th>  
<th>

**WP**

</th>  
<th>

**Short name of lead participant**

</th>  
<th>

**Type**

</th>  
<th>

**DL**

</th>  
<th>

**Delivery date (Month)**

</th> </tr>  
<tr>  
<td>

D1.1

</td>  
<td>

Driving cycles specification and enduser requirements

</td>  
<td>

WP1

</td>  
<td>

CRF

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

4

</td> </tr>  
<tr>  
<td>

D1.2

</td>  
<td>

Architecture and interface of the eaxle/charger

</td>  
<td>

WP1

</td>  
<td>

BRU

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

6

</td> </tr>  
<tr>  
<td>

D1.3

</td>  
<td>

Reliable and scalable design ready for mass manufacturing and dismantling

</td>  
<td>

WP1

</td>  
<td>

VUB

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

9

</td> </tr>  
<tr>  
<td>

D2.1

</td>  
<td>

Design of SiC-inverter, DC/DCconverter and on-board charger

</td>  
<td>

WP2

</td>  
<td>

ST-I

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

18

</td> </tr>  
<tr>  
<td>

D2.2

</td>  
<td>

Electrical architecture and interfaces

</td>  
<td>

WP2

</td>  
<td>

AIT

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

21

</td> </tr>  
<tr>  
<td>

D3.1

</td>  
<td>

E-axle specification input

</td>  
<td>

WP3

</td>  
<td>

CRF

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

9

</td> </tr>  
<tr>  
<td>

D3.2

</td>  
<td>

BPM-SM and transmission

development

</td>  
<td>

WP3

</td>  
<td>

GKN

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

18

</td> </tr>  
<tr>  
<td>

D3.3

</td>  
<td>

BPM-SM, SiC-inverter and

transmission integration

</td>  
<td>

WP3

</td>  
<td>

ST-I

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

24

</td> </tr>  
<tr>  
<td>

D4.1

</td>  
<td>

Control system design

</td>  
<td>

WP4

</td>  
<td>

TEC

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

24

</td> </tr>  
<tr>  
<td>

D4.2

</td>  
<td>

Cooling system design and integration

</td>  
<td>

WP4

</td>  
<td>

AIT

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

24

</td> </tr>  
<tr>  
<td>

D5.1

</td>  
<td>

Report on the prototyping of the components

</td>  
<td>

WP5

</td>  
<td>

BRU

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

24

</td> </tr>  
<tr>  
<td>

D5.2

</td>  
<td>

Integration of the components and bench qualification

</td>  
<td>

WP5

</td>  
<td>

TEC

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

30

</td> </tr>  
<tr>  
<td>

D6.1

</td>  
<td>

E-axle integration report

</td>  
<td>

WP6

</td>  
<td>

CRF

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

33

</td> </tr>  
<tr>  
<td>

D6.2

</td>  
<td>

Verification of the vehicle

functionalities

</td>  
<td>

WP6

</td>  
<td>

CRF

</td>  
<td>

R

</td>  
<td>

CO

</td>  
<td>

33

</td> </tr>  
<tr>  
<td>

D6.3

</td>  
<td>

Vehicle testing report

</td>  
<td>

WP6

</td>  
<td>

AIT

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

36

</td> </tr>  
<tr>  
<td>

D6.4

</td>  
<td>

E-axle assessment report (TRL, MRL and LCA)

</td>  
<td>

WP6

</td>  
<td>

VUB

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

36

</td> </tr>  
<tr>  
<td>

D7.1

</td>  
<td>

Dissemination strategy

</td>  
<td>

WP7

</td>  
<td>

POLITO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

6

</td> </tr>  
<tr>  
<td>

D7.2

</td>  
<td>

Project website and communication strategy

</td>  
<td>

WP7

</td>  
<td>

AIT

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

6

</td> </tr>  
<tr>  
<td>

D7.3

</td>  
<td>

Exploitation strategy

</td>  
<td>

WP7

</td>  
<td>

BRU

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

21

</td> </tr>  
<tr>  
<td>

D7.4

</td>  
<td>

Final report and summary of published documents

</td>  
<td>

WP7

</td>  
<td>

POLITO

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

36

</td> </tr>  
<tr>  
<td>

D8.1

</td>  
<td>

Quality plan, contracts and reports

</td>  
<td>

WP8

</td>  
<td>

AIT

</td>  
<td>

R

</td>  
<td>

PU

</td>  
<td>

3

</td> </tr> </table>

**Table 4. Deliverables.**

##  Templates

The official template for deliverables can be found on the FITGEN SharePoint
at the link:

_https://portal.ait.ac.at/sites/FITGEN/SitePages/FITGEN%20Home.aspx?RootFolder=%2Fsites%2FFITGEN%2_

_FShared%20Documents%2FDocument%20templates
&FolderCTID=0x012000BA32B24263A1BC4E82338CD7 _ _8794D48E
&View=%7B0CAA86DF%2DDA3A%2D469F%2DA229%2D9CCD602B7033%7D _

These templates must be used by all project partners.

##  Reviewing and approval

To assure good quality deliverables, they need to be reviewed and checked
before submission. This review shall be done by the PC and previously
appointed reviewers. The following timeline shall be followed for the
submission of deliverables:

  * 8-to-6 weeks before the deadline: the coordinator reminds the deliverable owner of the upcoming submission deadline; 

  

  * 4 weeks before the deadline: the deliverable owner submits the draft to the appointed reviewer; 

  

  * 3 weeks before the deadline: the appointed reviewer proposes an amended version to the deliverable owner; 

  

  * 2 weeks before the deadline: the deliverable owner submits the draft to the PC; 

  

  * From 2 weeks before the deadline and until the deadline: the PC and the deliverable owner work together to finalise the deliverable. The final version of the deliverable is always uploaded in SYGMA by the PC. 

  

Reviewers have been nominated for each deliverable at the KoM. The guidelines
for selection are the following: the reviewer must be a representative of the
entity that is mostly involved in the task(s) to which the deliverable belongs
and must be different from the deliverable owner and the PC. Reviewers for
each Deliverable are proposed by the PC. The GA needs to be consulted for
final approval of the Reviewers. A list with nominated reviewers is reported
below.  
  
<table>  
<tr>  
<th>

**Deliverable number**

</th>  
<th>

**Deliverable name**

</th>  
<th>

**WP**

</th>  
<th>

**Leader**

</th>  
<th>

**Reviewer**

</th>  
<th>

**Approver**

</th> </tr>  
<tr>  
<td>

D1.1

</td>  
<td>

Driving cycles specification and enduser requirements

</td>  
<td>

WP1

</td>  
<td>

CRF

</td>  
<td>

POLITO

</td>  
<td>

AIT

</td> </tr>  
<tr>  
<td>

D1.2

</td>  
<td>

Architecture and interface of the eaxle/charger

</td>  
<td>

WP1

</td>  
<td>

BRU

</td>  
<td>

POLITO

</td> </tr>  
<tr>  
<td>

D1.3

</td>  
<td>

Reliable and scalable design ready for mass manufacturing and dismantling

</td>  
<td>

WP1

</td>  
<td>

VUB

</td>  
<td>

POLITO

</td> </tr>  
<tr>  
<td>

D2.1

</td>  
<td>

Design of SiC-inverter, DC/DCconverter and on-board charger

</td>  
<td>

WP2

</td>  
<td>

ST-I

</td>  
<td>

BRU

</td> </tr>  
<tr>  
<td>

D2.2

</td>  
<td>

Electrical architecture and interfaces

</td>  
<td>

WP2

</td>  
<td>

AIT

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

D3.1

</td>  
<td>

E-axle specification input

</td>  
<td>

WP3

</td>  
<td>

CRF

</td>  
<td>

BRU

</td> </tr>  
<tr>  
<td>

D3.2

</td>  
<td>

BPM-SM and transmission

development

</td>  
<td>

WP3

</td>  
<td>

GKN

</td>  
<td>

BRU

</td> </tr>  
<tr>  
<td>

D3.3

</td>  
<td>

BPM-SM, SiC-inverter and

transmission integration

</td>  
<td>

WP3

</td>  
<td>

ST-I

</td>  
<td>

BRU

</td> </tr>  
<tr>  
<td>

D4.1

</td>  
<td>

Control system design

</td>  
<td>

WP4

</td>  
<td>

TEC

</td>  
<td>

VUB

</td> </tr>  
<tr>  
<td>

D4.2

</td>  
<td>

Cooling system design and integration

</td>  
<td>

WP4

</td>  
<td>

AIT

</td>  
<td>

TEC

</td> </tr>  
<tr>  
<td>

D5.1

</td>  
<td>

Report on the prototyping of the components

</td>  
<td>

WP5

</td>  
<td>

BRU

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

D5.2

</td>  
<td>

Integration of the components and bench qualification

</td>  
<td>

WP5

</td>  
<td>

TEC

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

D6.1

</td>  
<td>

E-axle integration report

</td>  
<td>

WP6

</td>  
<td>

CRF

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

D6.2

</td>  
<td>

Verification of the vehicle

functionalities

</td>  
<td>

WP6

</td>  
<td>

CRF

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

D6.3

</td>  
<td>

Vehicle testing report

</td>  
<td>

WP6

</td>  
<td>

AIT

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

D6.4

</td>  
<td>

E-axle assessment report (TRL, MRL and LCA)

</td>  
<td>

WP6

</td>  
<td>

VUB

</td>  
<td>

ST-I

</td> </tr>  
<tr>  
<td>

D7.1

</td>  
<td>

Dissemination strategy

</td>  
<td>

WP7

</td>  
<td>

POLITO

</td>  
<td>

VUB

</td> </tr>  
<tr>  
<td>

D7.2

</td>  
<td>

Project website and communication strategy

</td>  
<td>

WP7

</td>  
<td>

AIT

</td>  
<td>

POLITO

</td> </tr>  
<tr>  
<td>

D7.3

</td>  
<td>

Exploitation strategy

</td>  
<td>

WP7

</td>  
<td>

BRU

</td>  
<td>

POLITO

</td> </tr>  
<tr>  
<td>

D7.4

</td>  
<td>

Final report and summary of published documents

</td>  
<td>

WP7

</td>  
<td>

POLITO

</td>  
<td>

VUB

</td> </tr>  
<tr>  
<td>

D8.1

</td>  
<td>

Quality plan, contracts and reports

</td>  
<td>

WP8

</td>  
<td>

AIT

</td> </tr> </table>

**Table 5. Deliverables’ reviewers.**

#  Quality Assurance – Management of Risks

A proper management of risks is key in the execution of FITGEN. The critical
risks for implementation of the project have been identified and reported in
Table 6. Description of the risks (including level of likelihood, i.e.
low/medium/high), involvement of WPs and risk-mitigation measures are
preliminary identified, at the best of the knowledge of the consortium. The
risk management table will be revised at each GA; updates will be made in case
new risks arise during the execution of the technical activities. In this
case, also appropriate mitigation measures will be indicate, addressing an
appropriate response to the changing environment.  
  
<table>  
<tr>  
<th>

**Description of risk (indicate level of likelihood: Low/Medium/High)**

</th>  
<th>

WP(s) involved

</th>  
<th>

Proposed risk-mitigation measures

</th> </tr>  
<tr>  
<td>

**Low**

Vehicle validation platform

(demonstrator) not available.

</td>  
<td>

All WPs

</td>  
<td>

The commitment of CRF to provide the donor vehicle will be recorded in the CA.

</td> </tr>  
<tr>  
<td>

**High**

Project partner cannot provide e-axle and/or component prototype (or/and mock-
up parts for first-level testing) in time or in budget.

</td>  
<td>

WP3

WP4

</td>  
<td>

Continuous monitoring of the FITGEN project progress by task- and work
package-leaders (i.e. timely report to the SC any significant deviations in
terms of results) to take corrective and/or preventive actions against any
prototype deficiencies or problems in terms of subsystems/parts/mock-up parts.

</td> </tr>  
<tr>  
<td>

**Low**

Developed and realized components of the e-axle does not reach the expected or
simulated behavior (power, efficiency, etc.)

</td>  
<td>

WP3

WP4

</td>  
<td>

Testing of all relevant prototypes on the testbench will be performed prior to
vehicle integration test.

</td> </tr>  
<tr>  
<td>

**Medium**

SotA data of the vehicle and its components cannot be assessed in the required
depth of detail.

</td>  
<td>

WP1

</td>  
<td>

A non-disclosure agreement will be set up, which must be signed and committed
by all project partners. This allows the partners to share data with the
consortium and to make relevant data accessible.

</td> </tr>  
<tr>  
<td>

**Medium**

Temperatures exceed limits in integrated e-drivetrain, especially in
electronics/power electronics compartment.

</td>  
<td>

WP4

WP5

</td>  
<td>

Accurate loss calculation with possible crosscheck between different design
tools in the consortium (analytical and finite elements) and first level
measurements will be applied. Temperature sensors will be inserted in
prototypes. Derating and safety functions will be included in the control
system.

</td> </tr>  
<tr>  
<td>

**Medium**

Prototype components get damaged during first or second level testing.

</td>  
<td>

WP5

WP6

</td>  
<td>

Spare parts for all critical components will be purchased/produced before
starting the tests. Test sequences will start with the lowest power rating and
end with short-term overload tests (the involved partners are very experienced
in testing).

</td> </tr>  
<tr>  
<td>

**High**

Packaging of the developed components and systems leads to box volume problems
in the vehicle validation platform.

</td>  
<td>

WP2

WP3

WP4

</td>  
<td>

Exchange of coarse CAD data and simulation models (vehicle, modules and
components) must start just at the beginning of the project.

</td> </tr>  
<tr>  
<td>

**High**

The investigations show that the benefits of the proposed technological
improvements have a lower impact on the vehicle (energy consumption, vehicle
weight, comfort or maximum driving range) than expected.

</td>  
<td>

WP1

WP6

WP7

</td>  
<td>

Suitable types and the right combination of the novel technologies must be
found, and synergistic effects must be used in order to maximize the impact on
the vehicle.

Before integrating the new technologies into the vehicle, their operating
behavior will be analyzed, and the expected benefit will be adapted.
Recognizing early deviations from the planned improvements enables to find
possible solutions to balance the lower benefit with other components or
technologies.

</td> </tr> </table>

**Table 6. Critical risks for implementation**

#  External communications and publications

##  Logo

Figure 2 shows the official FITGEN project logo. This logo has been presented
by the GA during the Kick-off meeting of FITGEN and consequently approved by
the consortium. On external and internal publications, the use of the official
project logo is required.

The project logo is located on the FITGEN SharePoint at the link:

_https://portal.ait.ac.at/sites/FITGEN/_layouts/15/start.aspx#/SitePages/WP7%20-_

_%20Exploitation%2C%20Dissemination%20and%20Communication.aspx?RootFolder=%2Fsites%2FFITGEN%_
_2FWP7%20documents%2FT7%2E2%20%2D%20Website%2C%20social%20media%20and%20communicatio_
_n%20towards%20stakeholders%20and%20citizens%2FLogos%20%2D%20FITGEN
&FolderCTID=0x01200034 _ _E985CF7C09D7459B979B5536FE7CE3
&View=%7B7757C34F%2DF1C2%2D48AE%2D9052%2D59B52F00DC4 _ _A%7D_

##  Templates

To ensure that presented contents are clearly connected to FITGEN and to
create a recognition factor of the project itself, the usage of the official
project presentation template can be found on the FITGEN SharePoint at the
link:

_https://portal.ait.ac.at/sites/FITGEN/SitePages/FITGEN%20Home.aspx?RootFolder=%2Fsites%2FFITGEN%2_

_FShared%20Documents%2FDocument%20templates
&FolderCTID=0x012000BA32B24263A1BC4E82338CD7 _ _8794D48E
&View=%7B0CAA86DF%2DDA3A%2D469F%2DA229%2D9CCD602B7033%7D _

##  Rules

On all project publications, the funding by the European Union needs to be
acknowledged. This includes the usage of the FITGEN project logo and the EU
flag in sufficiently high resolution. For the acknowledgement itself, the
following sentence is mandatory:

_This project has received funding from the European Union’s Horizon 2020
research and innovation programme under grant agreement No. 824335._

Additionally, dissemination documents can include the following disclaimer(s):

_The content of this publication is the sole responsibility of the Consortium
partners listed herein and does not necessarily represent the view of the
European Commission or its services._

_This publication reflects only the author’s view and the Innovation and
Networks Executive Agency (INEA) is not responsible for any use that may be
made of the information it contains._

##  Procedures

Before executing any formal publication or external communication, the PC
needs to be informed in advance. The PC will finally confirm the content and
visual appearance. To ensure an orderly procedure, the following deadlines
shall be met:

  * 6 weeks before submission: giving notification to Coordinator, and distribution to the Project Consortium; 

  

  * 2 weeks before submission: summarising feedback and approval from Project Consortium; 

  

The PC regards the publication or communication as authorised if no objection
from the partners is received within the feedback period. However, the
publishing party needs to receive a written confirmation of that approval
before any material can be submitted or communicated.

#  Communication and meeting management

##  Communication

Standard working communication shall be done via phone or email. Important
communication and exchange of information (e.g. to provide information on the
release of new deliverables or to notify the project partners about the
availability of new information and events or to circulate meeting agendas,
etc.) should be done via email to enable tracking and follow-up. To enable the
coordinator to maintain an overview of the entire project, the coordinator
contacts shall be included in all technical and administrative e-mails in CC.
For project documents, especially large ones, the project SharePoint should be
used as the definitive repository:

_https://portal.ait.ac.at/sites/FITGEN/_layouts/15/start.aspx#/_

Instead of sending attachments via email, good practise is to upload them to
the appropriate folder on the SharePoint and reference them (hyperlink) in an
email.

##  Bi-weekly plenary calls

Web meetings are a powerful tool for keeping frequently in touch with partners
via display aided telephone conferences (e.g. GoToMeeting). Partners need only
basic equipment (i.e. a telephone set and a standard working station) to use
this type of meeting environment. Bi-weekly web meetings are organized by the
PC. Regardless of these regular meetings, spontaneous web meetings with short
notice are possible at any time to save resources (e.g. travel budget and
time) and for having WP-dedicated discussions. For web meetings generally, the
same principles are valid as for physical meetings. This means, all required
documents must be shared with the attendees before the meeting. This includes
an agenda and a participant list.

##  Face-to-Face meetings

The main pillar for communication in the project will be the Face-to-Face
meetings. To foster the personal exchange of project participant across all
WPs, these meetings will be held on a regular basis. Two types of meetings
shall be held during the project:

  * General Assembly meetings; 

  

  * Steering Committee meetings; 

  

The following target dates/locations have been set for the GA meetings:  
  
<table>  
<tr>  
<th>

**Meeting ID**

</th>  
<th>

**Project Month**

</th>  
<th>

**Location**

</th> </tr>  
<tr>  
<td>

GA - 1 (Kick-Off Meeting)

</td>  
<td>

M1 (Jan. 2019)

</td>  
<td>

AIT (Vienna, AT)

</td> </tr>  
<tr>  
<td>

GA - 2

</td>  
<td>

M7 (July 2019) 2  nd  /3  rd  July (tentative)

</td>  
<td>

ST-I (Catania, IT)

</td> </tr>  
<tr>  
<td>

GA - 3

</td>  
<td>

M13 (Jan. 2020)

</td>  
<td>

BRU (Sennwald, CH)

</td> </tr>  
<tr>  
<td>

GA - 4 (MidTerm Meeting)

</td>  
<td>

M19 (July 2020)

</td>  
<td>

AIT (Vienna, AT)

</td> </tr>  
<tr>  
<td>

GA - 5

</td>  
<td>

M25 (Jan. 2021)

</td>  
<td>

TEC (Bilbao, ES)

</td> </tr>  
<tr>  
<td>

GA - 6

</td>  
<td>

M31 (July 2021)

</td>  
<td>

VUB (Brussels, BE)

</td> </tr>  
<tr>  
<td>

GA - 7 (Final Meeting)

</td>  
<td>

M36 (Dec. 2021)

</td>  
<td>

CRF (Torino, IT)

</td> </tr> </table>

**Table 7. GA meetings.**

Ordinary meetings of the Steering Committee shall be held at least quarterly.
Extraordinary meetings can be called at any time upon written request of any
member of the SC. At each meeting, the location for the following meeting
shall be discussed and decided by the GA.

##  Meeting minutes

Meeting minutes shall be prepared by the PC. After the meeting, the minutes
will be distributed among all participants and the coordinator within 10
calendar days. The partners should send comments on the minutes within 10
working days. Within further 2 working days the final revised meeting minutes
should be circulated again.

#  Electronic Data Management

##  Document creation

To ensure compatibility and open access to all electronic project documents,
common standards on data formats need to be defined. Electronic project
documents shall be created using the Microsoft Office (2013 and later)
software suite. The following data formats need to be used:

  * Text documents: Microsoft Office Word Document (.docx); 

  

  * Presentations Microsoft Office PowerPoint Presentation (.pptx); 

  

  * Spreadsheets Microsoft Office Excel Workbook (.xlsx); 

  

All documents shall use the English (United Kingdom) language. Common rules
for file names need to be followed. File names need to comply with the
following rule:

  * FITGEN_Index_DocName_Date_Version_Partner.ext; with the following meanings: 

  

  * Index Number of WP or deliverable, e.g. WP1 or D1.4; 

  

  * DocName Short name suitable for content identification, e.g. KickOff; 

  

  * Date Date of document creation, e.g. 2017-11-06; 

  

  * Version Version number, e.g. V1; 

  

  * Partner Acronym of document responsible partner, e.g. AIT; 

  

  * ext File extension, e.g. .docx; 

  

##  Data transfer and storage

Presentations and general documents shall be shared via SharePoint. This
system is administered and maintained by the PC. After invitation by the PC,
the storage location can be accessed via the following URL:

_https://portal.ait.ac.at/sites/FITGEN/_layouts/15/start.aspx#/_

**Figure 3. FITGEN SharePoint.**

#  Conclusions

Procedures and standards to be used in the FITGEN project to guarantee the
quality of the outcomes are formulated in D8.1, in full compliance with all
contractual requirements framed into the GA and CA.

#  Risk Register  
  
<table>  
<tr>  
<th>

**Risk No.**

</th>  
<th>

**What is the risk**

</th>  
<th>

**Probability of risk occurrence** 1

</th>  
<th>

**Effect of risk** 2

</th>  
<th>

**Solutions to overcome the risk**

</th> </tr>  
<tr>  
<td>

n.a.

</td>  
<td>

n.a.

</td>  
<td>

n.a.

</td>  
<td>

n.a.

</td>  
<td>

n.a.

</td> </tr> </table>

#  Project partners  
  
<table>  
<tr>  
<th>

**Participant No.**

</th>  
<th>

**Participant short name**

</th>  
<th>

**Participant organization name**

</th>  
<th>

**Country**

</th> </tr>  
<tr>  
<td>

1 (Coordinator)

</td>  
<td>

**AIT**

</td>  
<td>

AIT Austrian Institute of Technology GmbH

</td>  
<td>

Austria

</td> </tr>  
<tr>  
<td>

2

</td>  
<td>

**CRF**

</td>  
<td>

Centro Ricerche FIAT SCPA

</td>  
<td>

Italy

</td> </tr>  
<tr>  
<td>

3

</td>  
<td>

**TEC**

</td>  
<td>

Fundacion Tecnalia Research & Innovation

</td>  
<td>

Spain

</td> </tr>  
<tr>  
<td>

4

</td>  
<td>

**BRU**

</td>  
<td>

BRUSA Elektronik AG

</td>  
<td>

Switzerland

</td> </tr>  
<tr>  
<td>

5

</td>  
<td>

**POLITO**

</td>  
<td>

Politecnico di Torino

</td>  
<td>

Italy

</td> </tr>  
<tr>  
<td>

6

</td>  
<td>

**ST-I**

</td>  
<td>

STMicroelectronics SRL

</td>  
<td>

Italy

</td> </tr>  
<tr>  
<td>

7

</td>  
<td>

**GKN**

</td>  
<td>

Guest, Keen and Nettlefolds

</td>  
<td>

Germany

</td> </tr>  
<tr>  
<td>

8

</td>  
<td>

**VUB**

</td>  
<td>

Vrije Universiteit Brussel

</td>  
<td>

Belgium

</td> </tr> </table>

_This project has received funding from the European Union’s H2020 research
and innovation programme under Grant Agreement no. 824335._

_This publication reflects only the author’s view and the Innovation and
Networks Executive Agency (INEA) is not responsible for any use_

_that may be made of the information it contains._

##  Appendix A – Quality Assurance

The following questions should be answered by the WP Leader, the reviewers and
the coordinator as part of the Quality Assurance Procedure. Questions answered
with NO should be explained. The author will then make an updated version of
the Deliverable. When all reviewers have answered all questions with YES, only
then the Deliverable can be submitted to the EC.

NOTE: For public documents this Quality Assurance part will be removed before
publication.  
  
<table>  
<tr>  
<th>

**Question**

</th>  
<th>

**Deliverable Leader**

</th>  
<th>

**Peer reviewer**

</th>  
<th>

**Coordinator**

</th> </tr>  
<tr>  
<td>

</td>  
<td>

Michele DE GENNARO

(AIT)

</td>  
<td>

Boschidar GANEV

(AIT)

</td>  
<td>

Michele DE GENNARO

(AIT)

</td> </tr>  
<tr>  
<td>

**1\. Do you accept this deliverable as it is?**

</td>  
<td>

YES

</td>  
<td>

YES

</td>  
<td>

YES

</td> </tr>  
<tr>  
<td>

**2\. Is the deliverable completely ready (or are any changes required)?**

</td>  
<td>

YES

</td>  
<td>

YES

</td>  
<td>

YES

</td> </tr>  
<tr>  
<td>

**3\. Does this deliverable correspond to the DoW?**

</td>  
<td>

YES

</td>  
<td>

YES

</td>  
<td>

YES

</td> </tr>  
<tr>  
<td>

**4\. Is the Deliverable in line with the FITGEN objectives?**

</td>  
<td>

YES

</td>  
<td>

YES

</td>  
<td>

YES

</td> </tr>  
<tr>  
<td>

**a. WP Objectives?**

</td>  
<td>

YES

</td>  
<td>

YES

</td>  
<td>

YES

</td> </tr>  
<tr>  
<td>

**b. Task Objectives?**

</td>  
<td>

YES

</td>  
<td>

YES

</td>  
<td>

YES

</td> </tr>  
<tr>  
<td>

**5\. Is the technical quality sufficient?**

</td>  
<td>

YES

</td>  
<td>

YES

</td>  
<td>

YES

</td> </tr> </table>