An IXM Engine represents a core planning algorithm implemented in code based on classes from the One Network SDK.
While IXM Engines can be configured to run on a regular schedule common to traditional batch-oriented processing, they can also be invoked using execution-level events. In these cases, the planning engine can sense and respond to real-time transactional data and provide real-time plan updates. This allows for a more agile business model. Data yielded from traditional batch processing is only as current as of the timing of the last batch, usually at least a day old. Responses to this data take additional time to process propagating down the process timelines resulting in increases in delays, artificially inflated lead-times, etc. IXM Engines are flexible enough to provide batch processing and real-time processing depending on business needs.
IXM Subnet and Planning Parameters
The concept of an IXM Subnet refers to breaking down planning into manageable chunks. Envision a very large enterprise with many partners, locations, large SKU counts, etc. With so many data points it is easy to imagine running into memory and hardware limitations when attempting to run an enterprise-wide plan. Subnets allow you to process portions of an enterprise in a discrete slice. For example, you could break planning tasks down by organizations within geographical states within limited date ranges or specific product lines.
Subnets are purely conceptual. We'll talk about them at length in the IXM tutorials, however there is no direct class or code artifact that directly relates to subnets.
- Task Creation
- Engine Processing
- Engine Execution
- Alternate Automations
- Types of Engines
- Types of Broken
- Grid Tuning