The following scenarios illustrate how the features of the MLU might be used in PPM.
Consider a standardized demand management process that is used in multiple regions, but each "run" of the process involves only a single region. For example, in Korea, requests are submitted and processed entirely in Korean. In the United Kingdom, the same request process is used, but requests are submitted and processed entirely in English.
This scenario applies best to project and program issues, risks, and scope changes. A project defined in Japanese would have all of its associated issues, risks, and scope change requests in Japanese. A project defined in German would have the associated requests in German. This scenario is common in large corporations in which IT processes are defined centrally and regional subsidiaries simply use the processes.
Laws that regulate importation of pharmaceuticals in different countries require that a corporation define several unique, region-specific processes for transactions of this type. In this case, the company does not require multiple translations of the PPM entities involved. They just need the ability to define the necessary entities in different languages on their single PPM instance.
Anything that is subject to local laws in different regions benefit from the ability to handle processes and transactions in multiple languages.
A subsidiary of a large enterprise must follow strict guidelines in outsourcing projects to off-shore workers.
A Swedish bank plans to purchase commercial buildings in three different countries, each of which has its own regulations on foreign purchase of real estate. They need separate processes for property purchases in all three cities.