Logical models representing the as is and to be system data are products of the vast majority of data reengineering projects. Once derived this system metadata is typically maintained using entity relationship diagrams. Meta information about entity relationship diagrams can be maintained with a many to many association between two metadata entities: logical data entity and logical data attribute. The universality of this approach and the relative commonality of the representation format prompted the research question: would it other be easier to integrate and utilize other data reengineering information if it were maintained in the same format? The answer appears to be yes. The two metadata entities form the basis of a metadata model that can be used as a structured repository for information obtained by reverse engineering and as a integrated collection of information forming and facilitating the subsequent forward engineering the system data. This poster describes the use of the metadata model to guide data reengineering. Maintaining relevant information about a system data in - by definition - its most flexible and adaptable format permits it to be subsequently reused in a number of different ways in reengineering and non-reengineering contexts including year 2000 analysis.