To improve the flexibility and robustness of the engineering of automated production systems (aPS) in the case of extending, reducing, or modifying parts, several approaches propose an encapsulation and clustering of related functions, e.g., from electrical, mechanical, or software engineering, based on a modular architecture. Considering the development of these modules, there are different stages, e.g., module planning or functional engineering, that have to be completed. A reference model that addresses the different stages for the engineering of aPS is proposed by the automation markup language (AML). Due to these different stages and the integration of several engineering disciplines, e.g., mechanical, electrical/electronic, or software engineering, information not limited to one discipline are stored redundantly, increasing the effort to transfer information and the risk of inconsistency. Although data formats for the storage and exchange of plant engineering information exist, e.g., AML, fixed domain specific structures and relations of the information, e.g., for automated material flow systems (aMFSs), are missing. This paper presents the integration of a metamodel into the development of modules for aMFS to improve the transferability and consistency of information between the different engineering stages and the increasing level of detail from coarse-grained plant planning to fine-grained functional engineering. Note to Practitioners-The engineering of automated production systems (aPSs) is a highly interdisciplinary procedure that requires the interaction of all participating people. However, communication during the engineering process is based on the exchange of information, orally or by documents. In addition, many influences during the different design stages, i.e., time periods, cause the change of parts or parameters. Hence, the neighboring engineering disciplines that employ these data need to be updated regarding the changes. Consequently, one challenge during the engineering of aPS is the data exchange as well as the guarantee for a consistent and complete description of the system. This contribution presents a methodology for a data exchange between the different tools applied during the engineering cycle in the design process of aPS. Therefore, the reference process proposed by the automation markup language and the associated data model for data exchange are applied. In contrast to the current state of the art, our approach additionally proposes the integration of a metamodel of the aPS in order to identify all engineering data required for a complete description of