Silver → Platinum-Plated Transition | Out-of-the-Box vs. Extension scoring against the o9 Digital Brain (HERO programme)
This blueprint maps the 12 Aurora A27 requirements (Requirements Spec. Register v1.2, owner: Aurora GOPT / Jan Karreby) against Pandora's existing planning system landscape, with depth on the o9 Digital Brain. Each requirement is scored on how much is delivered natively (out-of-the-box) versus how much requires configuration, modelling, or build extensions — and where the work lands across the wider landscape (Logility, Aptean, IPPL/IPPL-120, AX12 MANU, D&A, Merch/O2C).
Seven systems surround the o9 Digital Brain. Each has a specific role in how Aurora moves from Silver to Platinum-Plated.
Core IBP / demand + supply planning engine for o9 markets. Enterprise Knowledge Graph (EKG) digital twin. Primary mapping target.
Twelve spokes, twelve requirements. Spoke length is the share o9 delivers natively; outer arc colour signals the GOPT impact. Click any spoke to dive in below.
Native data model; the only true build is Aurora-specific DQ gating + the Silver↔PP link governance.
Lowest OOTB fit — o9 consumes natively, but the requirement is fundamentally an external dependency + integration on AX12 MANU.
o9 covers the planning spine natively; extensions concentrate on Aurora transition mechanics, retail-grain disaggregation, compliance workflow, and the AX12 integration.
Filter by band or GOPT impact. Click a card to open the full capability mapping on the right.
o9 EKG natively models product master, planning attributes, hierarchies and assortments as a digital twin. Variant relationships and attribute-based product structures are first-class. Predecessor–successor (Silver→PP) linkage is a standard lifecycle construct.
Configure A27 PP DV attribute set, hierarchy/assortment nodes, and the Silver↔PP link relationship; default-inheritance-from-Silver rule via attribute defaulting; route/BOM planning attributes for hybrid flow.
Custom validation measures to enforce 'unique ID + valid planning attributes' and 'mandatory Silver↔PP link on Base Transition DVs' as gating data-quality rules with reject reporting (AC3).
Authoritative product/BOM master originates upstream (PIM / AX12); o9 consumes via integration. Load-success confirmation handshakes to downstream systems (Logility, Aptean, IPPL).
Native data model; the only true build is Aurora-specific DQ gating + the Silver↔PP link governance.
The substitution engine exists; the Aurora cutover rule-set is bespoke and ownership is deliberately distributed off GOPT.
Lowest OOTB fit — o9 consumes natively, but the requirement is fundamentally an external dependency + integration on AX12 MANU.
Attributes fit o9 but compliance sign-off & COO route logic are workflow-heavy and largely external — low OOTB.
Concentrated on Aurora transition mechanics, retail-grain disaggregation, compliance workflow, and the AX12 integration.
Beyond o9 OOTB: every item that must be built, configured, or integrated. Grouped by priority, tagged by owning system and type.
Ingest allocation proportions + step lead times; PP setup confirmation; one-cycle change propagation; consistency check
Cutover-type config, soft-cutover transfer profiles, override matrix + audit, post-cutover Silver thresholds
Disposal/markdown rule for outgoing Silver stock
Retail-grain disaggregation with reconciliation; new build below core planning grain
Versioned SKU×Store handoff consumable by Aptean; cadence contract
Scalable automated NPI method to replace Year-1 manual workaround before 2027 (330+ DVs)
Weekly finite plating capacity, wave-allocation & capacity-sharing rules, utilisation alerts
Per-market sign-off gating prior to ship/readiness; COO route logic for hybrid route
Run-down/build-up deviation alert engine; Silver-vs-PP split views linkable
WIP at platers + in-transit + store-level visibility feeds
Cross-market KPI calc rules, RAG/exception, weekly cadence reconciling demand↔supply/inventory
Validation measures enforcing unique ID, valid attributes, mandatory link on Base Transition DVs; reject reporting
Pack-aware phase-in/out (volume, timing, pack composition) for initial Aurora launches
Elasticity effect at differing Silver/PP price points + sell-in pack forecast logic
Source-mix evolution toward fully insourced model over horizon
Consistent node IDs across o9 / Logility / IPPL for plater nodes & route legs
Revenue / margin-impact views alongside volume KPIs
Integrate Logility outputs + surface through D&A semantic layer
Eighteen extension items, three phases, four parallel squads, ten 2-week sprints. Critical path runs through AX12 MANU (REQ-10) and PLM compliance sign-off (REQ-08).
Data spine + critical integration
AX12→o9 feed live; master data & node IDs stable; DQ gating passing.
Go-live transition mechanics
Cutover rules, SKU×Store + Aptean feed, capacity model, compliance gating validated for H2-26 launch.
Scorecard, value, Wave-2 scale
Transition scorecard + value KPIs live; Wave-2 NPI automation ready before 330+ DV wave.
AX12 MANU→o9 integration (REQ-10, 5 sprints) and PLM compliance sign-off (REQ-08, 4 sprints) are the longest, externally-dependent items. Start both at sprint 1 / earliest; slippage here moves go-live.
Parallel squads (Data & Integration, Demand, Supply, Reporting); external partners (AX12/Pl2Pr, PLM, Aptean, Logility) resourced to agreed cadence; o9 reference-model alignment maintained to limit custom build.
Go/No-Go for transition build: AX12 feed flowing, master data + node IDs stable, DQ gating green. Blocks P1 if not met.
Go-live readiness for H2-2026 launch: cutover rules, SKU×Store + Aptean feed, plating capacity, compliance gating all UAT-signed.
Wave-2 scale readiness: scorecard + value KPIs live, NPI auto-disaggregation proven before the 330+ DV 2027 wave.
Each requirement traced to the systems that must deliver against it. Hover to isolate a thread.
Hover a requirement or system to isolate its dependencies. Derived from primary + extension owner mappings.