Planning Cycle
One governed FY27–FY31 cycle: inputs are collected and validated, scenarios are modelled on published versions, and one plan is signed off.
Sustained capacity gaps
0
Family / region combinations short for two or more consecutive months
Earliest constraint
None
First month the network cannot fully serve requirement
Network coverage
99.7%
Allocated volume against total requirement
Peak line utilization
55.5%
Highest monthly loading across all lines
Cycle stages
Where the planning cycle stands today
Demand intake
7 of 7 regions submitted
Capacity intake
1 site group pending validation
Planning rules
Planning Rules v4 locked
Scenario modelling
2 scenarios in the cycle
Leadership sign-off
Scheduled 12 Sep 2026
Validation issues
Must be cleared before sign-off
Greater China
Refill attach rate missing for Smart Series FY30.
India / MEA
FY31 half-year split deviates more than 15% from the approved profile.
Latin America
High-side submission not yet received.
Regional demand submissions
Balanced (50/50) and high-side (20/80) views
| Region | Balanced | High side | Status |
|---|---|---|---|
North America M. Delgado · 02 Aug 2026 | Submitted | Submitted | Complete |
Europe A. Osei · 04 Aug 2026 | Submitted | Submitted | Complete |
Greater China L. Chen · 03 Aug 2026 | Submitted | Submitted | Validation Required |
Asia Pacific S. Tanaka · 01 Aug 2026 | Submitted | Submitted | Complete |
Latin America R. Almeida · 29 Jul 2026 | Submitted | Not Started | Submitted |
India / Middle East / Africa N. Prasad · 31 Jul 2026 | Submitted | Submitted | Validation Required |
Japan / Korea H. Mori · 02 Aug 2026 | Submitted | Submitted | Complete |
Capacity submissions
Line-level inputs by site group
| Site group | Lines | Status |
|---|---|---|
EU Site Group A L. Brenner · 22 Jul 2026 | 3 | Complete |
NA Site Group B K. Idowu · 18 Jul 2026 | 2 | Validation Required |
APAC Site Group C S. Tanaka · 21 Jul 2026 | 1 | Complete |
APAC Site Group D S. Tanaka · 12 Jul 2026 | 1 | Submitted |
How the cycle stays trustworthy
- Scenarios can only be built on published demand, capacity and rule versions.
- Every assumption change is recorded with a reason, an owner and a timestamp.
- Any result can be traced back through allocation, lead time and demand translation.
- Only one scenario is approved and locked for the cycle.