ERP Data Models for OUR Enterprise

We have never had a comprehensive set of data models for our ERP system (J.D. Edwards, aka JDE). The models we do have are piecemeal, some being generic vendor models while others were done for individual projects. This is a common problem with ERPs and other 3rd party applications – either no data models exist or the models are generic and do not accurately reflect the local implementation. We decided to challenge the status quo -- to see if we could develop models to document our configuration of JDE.

Leveraging Confucious' wisdom, that "A journey of a thousand miles begins with a single step", we have been moving this initiative forward one step at a time, getting validation and support at every step before moving forward.

First steps:

• simple reverse-engineering of our General Ledger
• sophisticated reverse-engineering of our General Ledger, designing our approach to optimize modeling effort and communication value
• pilot model to validate our approach (which was successful!)

Our reverse-engineering design identified 3 levels of modeling to be most effective:

• skeleton logical/physical model of a subject area
• conceptual (high-level) overview model (will be built over time)
• filled-in logical/physical model of a subject area (produced as time permits)

It also identified the benefits of using logical entities and relationships to highlight and/or clarify facets of the physical design.

A number of examples were shown in the presentation, to illustrate the 3 levels of models and the annotations.

The results have been positive. We are finally developing models that are designed to communicate the physical configuration of our ERP: our tables, our primary keys, our relationships, our terminology, our definitions. Our skeletal models give us a quick start, that can be fleshed out over time. The conceptual model will gradually give us an overview of all the information captured in our ERP. Best of all, we've realized that this approach is not limited to casting light on our ERP implementation, but can (and will) be applied to other databases.

To paraphrase Eleanor Roosevalt, we've stopped cursing the darkness. We've lit a single candle, and it's getting brighter all the time!