1. Technical Capabilities & Limitations
- Does Optimizer work with the Polaris engine?
Not directly at this time. A direct integration is on the roadmap and expected by the end of the year. For now, you will need two separate workspaces: one using the Classic engine for Optimizer and another for Polaris. - Can Optimizer use native Anaplan time dimensions?
No, Optimizer cannot use native time dimensions. The recommended best practice is to use a custom list to represent time periods in your optimization models. - Can inputs and outputs be spread across different modules?
Yes, the data for Optimizer actions (inputs, constraints, and outputs) can be located in multiple modules within your Anaplan model. - How does Optimizer evaluate variables?
It does not process variables and constraints sequentially. Instead, it evaluates all decision variables, objectives, and constraints simultaneously to find the best possible feasible solution.
2. Performance and Concurrency
- Does Optimizer lock the model while running?
Yes, Optimizer is a "blocking action," which means it can prevent other users from making changes to the input/output models while a run is in progress. - What are the best practices for managing performance and reducing the MIP Gap?
For detailed guidance on improving Optimizer performance, a great resource is the Performance Tuning in Anaplan's Optimizer post on the Anaplan Community.
https://community.anaplan.com/discussion/157946/performance-tuning-in-anaplan-s-optimizer
3. Modeling Best Practices
- How do you differentiate between a constraint and a variable?
A constraint represents a limited resource, such as time, capacity, or materials. In contrast, a variable represents a decision you need to make, such as assigning an employee to a project or determining how much of a product to manufacture.
