Segregation of Demantra users/requirements
I have a general question about Demantra.
We are currently successfully running Demantra to forecast a large subset of our Finished Goods products. This work is the responsibility of a dedicated team of forecast analysts getting input from end users globally.
Completely disconnected from this effort we have a business requirement to import low level component forecasts (not finished goods) created in a stand alone legacy system into Demantra so that our ASCP manufacturing plan can use this forecast as a demand input.
My question is can I create a completely stand alone Demantra instance or version to act as the go between from the stand alone legacy system to the ASCP manufacturing plans. I do not want to impact (in any way) the efforts of the forecast analysts working on the Finished Goods products. I want to use Demantra as a pass through but I want it to be effectively invisible to the Finished Goods forecast team.