The Distribution Center Reference Model has a hierarchical structure with four levels:

At each level, the information offered is on a different aggregation level and meets the requirements of different user groups (top management, project manager, section manager, planning experts).

The Top Level gives an aggregated overview of the distribution center. Important information about the entire distribution center is given, including existing structures, used resources and the performance level achieved by the distribution center as a whole.
Examining the processes

The workflows on the Process Level resemble by the flow of materials and include: receiving, storage and picking, consolidation and packing, shipping and added value. In addition, the process overhead displays the administrative work, which is not directly connected to the flow of materials. Findings at the Top Level are further detailed on the Process Level so the performance of every process can be evaluated. This evaluation becomes the basis for conducting a more detailed analysis on the Task Level.
Examining the tasks

Within the third level – the core of the Distribution Center Reference Model – all processes are separated into tasks. Due to their structure, the evaluation of the tasks is independent from the individual technical realization. Comparability is guaranteed on the Task Level. Therefore, tasks of different distribution centers can be compared.
Examining the tasks with analytical models

The Technical Realization Level allows for each task to be compared with a "virtual benchmarking partner”, which is represented through an analytical model. For each task, several analytical models exist. Each one represents one technical realization. The models determine the typical key data, e.g. costs, space and time requirement. They represent idealized states and therefore a "theoretical Best Practice“. These models can also hint at performance differences. Finally, the models can be used to answer further questions, such as: Was the right system chosen? Can the system handle future requirements? Is a separation or consolidation of areas expedient?