Registering and documenting development of a MSR system is project-oriented, whereby there may be several versions of the product data of a project. The projects can be combined with the help of main projects. This can be defined within <overall-project> by a <label> an a short description in <desc>. Each project is assigned to a maximum of one main project.
The documentation and continuation of project phases occurs in versions. We differentiate between active versions, the data of which can still be modified, and fixed versions, the data of which can no longer be modified. New versions can be designed on the basis of a fixed version. New versions can reuse complete fixed versions of a document or even parts of such a document. This is illustrated by the following figure:
Figure 119: Structure of <project-data>
Project data can be described by a PDM system in an integrated SGML-Editor and PDM environment. This is information on the current project and possibly the main project. Company-specific details about the project can be specified in <general-project-data> on the following items:

System overview <system-overview>
This chapter can be used to define information about a global system, e.g. a certain car model.
Order justification <reason-order>
This may be used to specify information about the reasons for the order of the described component resp. for making the specification of such a component.
Objectives <objectives>
This chapter can be used to specify information about the project objectives. E.g. "Development and system release of the engine-managment-system for the model NEW-BEETLE"
Models <sample-spec>
This structure is used to define development samples like A-,B-,C-,D-sample. These samples represent the results of the different development phases.
Variant specification <variant-spec>
This section is used to specify all variant definitions and their corresponding variant characteristics. See also 15.5. Variant Concept.
Limits to other projects <demarcation-other-projects>
This chapter is used to describe the demarcation to other projects.
Parallel developments <parallel-design>
This can be used to give an overview of the work in parallel projects.
Integration capability <integration-capability>
In this chapter requirements on the capabilities of integration in other systems can be described.
Acceptance conditions<acceptance-cond>
This chapter is used to define the general conditions for the acceptance of the described components.
Schedule and plans <project-schedule>
This chapter is used to define the project-schedule, e.g. project milestones, dates, time limits etc.
Purchasing conditions <purchasing-cond>
This is used to define purchasing conditions like amount of devices per year, delivery times, storage quantities, etc. .
Protocols, minutes of meeting <protocols>
This is the place where project minutes and other arrangements can be mentioned.
Handed over documents and data<dir-hand-over-doc-data>
This is the directory of the handed over documents and data.
Additional project specifications<add-spec>
Any kind of additional project description which can't be described with the chapters mentioned above.