Unified Data Model

Single Solution, Single Data Model, In-Memory

All of Adexa planning solutions from network planning to supply chain planning, plant planning and sequencing are based on a unified data model. This is a unique feature of Adexa applications that is the foundation of Adexa IBP solution. But why is a unified data model important? There are a number of reasons as explained below.

The most obvious reason is that if different data models are used at (say) supply chain level and plant level, then the plans sent to the users at the factory level from the supply chain do not make sense! Because different models and algorithms are used, the generated plans are either too much or too little, for the available capacity and material, at the lower more detailed levels. This can cause, unreliable promised dates and negatively impact customer service levels and/or unnecessarily cause increase in inventory.

Also, having a unified data model drastically reduces the cost of integrating your planning and execution environments as well as integrating such systems with the rest of your IT systems, e.g. ERP and MES. Only one gateway is needed to integrate to the entire IBP solution of Adexa. We refer to this as One-Touch™ integration. Needless to say that, this approach in addition to reducing the cost of integration it also improves the accuracy of plans.

Unified Data Model (UDM) is Better!

In Sales and Operation planning, the demand planning, inventory planning and supply planning all need to speak the same language. Constraints and requirements at the demand level need to be accurately translated to supply constraints and inventory requirements as defined by the attributes of the demand and supply (see Attribute-Based Planning white paper). Having a unified data model implies no translation is needed and enables smooth transition of demands into supply constraints and availability. The bottom line is that a unified data model saves cost, time, effort and leads to a much lower cost of ownership and reliable plans for execution.

In summary, A unified data model implies a single solution that can expand and contract vertically and extend horizontally only because it has a single data model. In the absence of the latter single solution code does not exist! Other solution providers may have a single code but they have yet to prove that they can extend it vertically to show detail and execution planning!

Latest Blog

section divider
Life after S&OP
Life after S&OP

Many supply chain leaders think of S&OE as yet another system to be acquired or patched on to S&OP. Although this maybe a viable strategy but not a particularly efficient one.


Request Demo