VDA Structure Component Requirement Specification Module I
VDA Structure Component Requirement Specification Module I
VDA Structure Component Requirement Specification Module I
Module I
CRS Universal Requirements
<Title>
<Number>
Version 1.0
Release
Technical depart-
ment/function
Name Date Signature
CRS author
Technical department
Project management
Development
Table of Contents
3. Headlines that are not used may not be deleted on levels 1 and 2 of
the Modules I and II, in order to guarantee the transparency and clarity of
the component requirement specification contents. Instead, these
chapters are to be marked with the reference “not relevant for this
component”.
2.1 Objective
2.2 Organisation
In this chapter criteria and workflows are to be established for how to, for
example, coordinate, approve and document cost, weight and deadline-
relevant changes during the development time.
Additionally, metrics for project tracking with which the customer checks
the project progress can be listed. Typical metrics are for example
milestone trend analysis, expense or error tracking. The data for the
metrics to be transferred by the contractor and the intervals of the data
transfer are established here.
4 Reporting and Documentation
In this chapter the customer defines the data and its form of recording
that are to be made available by the contractor in the framework of a
change documentation in the course of the development and, if
applicable, production processes (e.g. entries in a project manual).
In this chapter all parts for which there are special documentation
requirements due to safety or certification relevance are to be listed (see
also VDA volume 1 – determination of documents with special archiving).
The contractor’s duty to co-operate and the data processing system to
be used are also to be established.
4.6 Traceability
If the given content structure does not suffice to assign all requirements
on level 2 to the superordinated subject on level 1, the requirements can
be assigned to this chapter.
Here the fundamental measures for the concept, product and process
safeguarding (e.g. quality functional deployment, FMEA, system, design
or process FMEAs, reviews) that are valid for all awardings within a
project are to be requested by the customer.
If the given content structure does not suffice to assign all requirements
on level 2 to the superordinated subject on level 1, the requirements can
be assigned to this chapter.
In this chapter the general rights and obligations of the contractor and
customer to non-disclosure, reuse, evaluation, etc. of the information
contained in the component requirement specification can be defined by
the customer.
7 Product Data Management
Define the requirements on the contents and the form of the parts list to
be kept by the contractor (if the contractor is responsible for keeping the
parts list).
If the given content structure does not suffice to assign all requirements
on level 2 to the superordinated subject on level 1, the requirements can
be assigned to this chapter.
If the given content structure does not suffice to assign all requirements
on level 2 to the superordinated subject on level 1, the requirements can
be assigned to this chapter.
In this chapter the general requirements and regulations for surface pro-
tection and the properties and condition of the surfaces and edges is to
be determined.
If the given content structure does not suffice to assign all requirements
on level 1, the requirements can be assigned to this chapter.
The further applicable documents that were valid at the CRS issue date
are applicable.