Portfolio & Lifecycle
RoadmapNPI launch planning. Phase-in and phase-out curves. Cannibalization. EOL sequencing. Decisions that live on a quarters-to-years horizon but cascade all the way down to next week's replenishment order.
What makes this a distinct decision domain
The state variables are shared with supply and demand, inventory, capacity, lifecycle states, but portfolio introduces decision variables those domains don't carry: launch date, phase-out curve, assortment, strategic fit. The exogenous information is also different: competitor launches, category-level elasticity, trade events, strategic roadmap signals. The objective function shifts from cost–service balance to NPV, market share, and portfolio coherence.
The policy class is DLA with stochastic lookahead, scenario-based planning over multi-year horizons with monthly re-planning cycles.
Why it belongs on the same platform
An NPI launch without capacity checks, long-lead component availability, and distribution feasibility is fantasy. Every planning vendor that tried to bolt on demand-side planning as a separate product ended up with integration debt and customers using spreadsheets between the two. On Autonomy, portfolio decisions propagate into the same world model that supply and production plan against, so an unfeasible launch is flagged before it's committed.
Roadmap
Portfolio & Lifecycle is on the roadmap. Production rollout sequences after transport and production scheduling. Design partners wanted.
This plane intersects with
Where the collaboration contract lives, not an integration project.
Interested in Portfolio planning as a design partner?
Shape the policy modules, governance surface, and KPIs for the domain as it goes from roadmap to live.