"When the European Union adopted a new market regulation for the sugar industry in 2006, Südzucker was forced to re-evaluate their entire supply chain network. On the one hand the company’s ability to export sugar to world markets became very limited, on the other hand major sugar deficit areas within the European Union were created. This led to a much greater focus on sales and distribution. Südzucker also knew this ruling would give them the ability to enter new sugar markets like Greece, Italy, Spain and the United Kingdom. Their challenge was to merge their national supply chain networks to create one integrated and powerful European supply chain network. The company had to determine how to modify their supply chain network by adding new facilities to ensure excellent service but also minimize transportation costs."
IBM Decision Optimization
A new case study is available showing how Südzucker, Europe's leading supplier of sugar products with an annual revenue of approximately €7 billion, uses IBM ILOG LogicNet Plus to help meet their goals of a cost-effective and flexible supply chain:
Here is a quick summary of the case:
We recently had a chance to revisit a large model built prior to 2009 using LogicNet Plus XE (LNP XE) 6.0. Since machines change over time, we re-ran this model in LNP XE 6.0 an existing machine.
We then ran the same model on the same machines using LNP XE 7.0 (which was released in June 2009), and it ran 15% faster.
Using LNP XE 7.1 (released in June 2010), it ran 14% faster. Overall, run time decreased by 27% since LNP XE 6.0.
Of course, with these types of models, run times will vary from model to model. However, IBM's continued investment in the underlying performance allows LNP XE customers to solve larger problems and tackle different business issues.
Ganesh_Ramakrishna 270002Q6PE Etiquetas:  lnp supply chain geocoding modeling tip network design logicnet plus 1.954 vistas
Anyone who has worked on network design projects focusing on networks outside North America will tell you that geocoding international locations is a slow and painful multi-step process. The main pain point being multiple spellings for the same city/state name. Is it ‘Bangalore’ or ‘Bengaluru’? Does your data read ‘Kaapstad’ instead of ‘Capetown’ (Kaapstad is the Afrikaans name for Capetown)?
Our consulting team works on dozens of international assignments every year. We use a combination of the resources below to make the geocoding process less painful.
If there are any locations that did not get geocoded at the end of this process, we clean the names manually and have a go at it again!
If you know of other sources, please feel free to add them in the comments section.