Compare six apparel use cases by maturity, return opportunity and data need. Test the tier, then check the phase and data gates. Every numeric score is illustrative.
Vision leads the illustrative launch case. Forecasting stays a first-tier priority but waits for its data and scale phase. Change any input: the plane re-seats every disc and re-rings the gates.
Computer-vision defect detection
priority points out of 100
· Eligible for investigation
eligible
+
gated
=
cases
1 eligible + 5 gated = 6 cases
Computer-vision defect detection leads the eligible set in Tier 1. 5 of 6 cases stay gated: confirm a baseline and run a bounded pilot first.
Phase and data gates pass. This is not deployment approval.
Exact values and their sources
Read every input beside its result.
All scores are illustrative points and tiers are ordered categories. Point at a row and the lens finds its disc; choose a source layer and the table shows what that layer feeds.
sourced · illustrative
Six default inputsStatus Point at a segment, or choose a layer, to light what it feeds.
Names and tiersSection 3 Six cases, two per tier, from the digital strategy, section 3.
ScoresIllustrative Engineering judgement. No measured data supports maturity, opportunity or data need.
Phase and capacityIllustrative Phase 1 and capacity 40: an illustrative launch scenario, not a count of records.
Dependency floorsSection 7 Vision 1; forecasting and inventory 2; generative applications 3, from section 7. Printing’s floor is illustrative.
ThresholdsIllustrative Tier cut-offs and the priority equation were made for this instrument. Not an industry standard.
Sorted by case order.
Current scenario, all use cases. S3 and S7: sourced, digital strategy sections 3 and 7.
Prog. tier
Floor
Readiness
Status
01Computer-vision defect detection
90
85
20
1
P1
1
76.5
Eligible
S3S7Scores
02ML demand forecasting
85
80
60
1
P2
1
68
Needs P2 · gap 20
S3S7Scores
03Inventory and supply-chain optimisation
70
75
60
2
P2
2
52.5
Needs P2 · gap 20
S3S7Scores
04Digital printing and sample reduction
65
60
45
2
P2 *
2
39
Needs P2 · gap 5
S3Floor *Scores
05Multi-model design-to-spec pipelines
45
65
80
3
P3
3
29.3
Needs P3 · gap 40
S3S7Scores
06Physics-constrained generation and GenAI content
30
50
90
3
P3
3
15
Needs P3 · gap 50
S3S7Scores
GFT’s Cameroon textile programme, digital strategy, sections 3 and 7 (prepared 31 January 2024, sources refreshed 2026). Use-case structure only; all numeric scores and screening thresholds are illustrative GFT assumptions. Not offered for download here. The asterisk marks the illustrative Phase 2 floor for digital printing.
The method, ordinal not financial
A first-tier idea can still need to wait.
01 / 05
Two cases per programme tier, from the digital strategy, section 3. These are the programme’s priorities, rather than measured results.
A return score is not a percentage saving, a rate of return, a price or a forecast of cash flow. Area is data need.
Cases now: 2 / 2 / 2 in T1 / T2 / T3. The cut-offs are illustrative design choices, not an industry standard.
At a capacity of 40: 1 of 6 cases pass under the wall. Gaps: 20, 20, 5, 40, 50.
01
01 / 05
The programme sets the order.
The programme puts computer-vision defect detection and machine-learning demand forecasting in its first tier. Inventory optimisation and digital printing follow in the second. Multi-model design pipelines and physics-constrained generation sit in the emerging third tier.
Sourced: digital strategy, section 3
02
02 / 05
Score every case on one boundary.
This instrument adds an explicit, illustrative scoring scheme so that a team can challenge that structure. Maturity is confidence in the approach for the intended process. Return opportunity is the materiality of the problem. Data need is the burden of usable history, labels and access. Neither score is a probability.
Illustrative scoring scheme
03
03 / 05
Priority is a product.
Maturity and opportunity each run from 0 to 100, so priority is the share of the plane that a case’s rectangle covers. Maturity 80 and opportunity 70 give 56 points.
P = M × R / 100
Selected case: 90 × 85 / 100 = 76.5
Illustrative equation
04
04 / 05
Tiers are cut-offs.
Tier 1 needs maturity of at least 80 and opportunity of at least 70. Otherwise Tier 2 needs at least 55 and 50; the rest fall into Tier 3, and equality passes. The cut-offs are illustrative choices that reproduce the programme’s starting order.
T1: M ≥ 80, R ≥ 70Illustrative thresholds
05
05 / 05
Readiness is a separate gate.
The priority index orders cases within a tier. It cannot remove a dependency. The data gap is max(0, data need minus capacity): the ochre part of each bar above the wall.
phase ≥ max(tier, floor) · capacity ≥ data need · opportunity > 0Screening gate, not deployment approval
Before anyone scores
A beautiful plot cannot compensate for inconsistent scoring.
01Computer-vision defect detection, maturity 90
02ML demand forecasting, maturity 85
03Inventory and supply-chain optimisation, maturity 70
04Digital printing and sample reduction, maturity 65
06Physics-constrained generation and GenAI content, maturity 30
0 means: never run at this station100 means: proven at this station
0 means: untried on this product family100 means: proven across the family
0 means: no evidence for this decision100 means: proven for this decision
Score each case against the same operating boundary. Compare applications only when the team agrees what the low and high ends mean. Record a short rationale outside this tool.
One inspection station. Write down what a maturity of 0 and of 100 means here, and what a return of 0 and of 100 means here, before the first score.
One product family. Write down what a maturity of 0 and of 100 means here, and what a return of 0 and of 100 means here, before the first score.
One planning decision. Write down what a maturity of 0 and of 100 means here, and what a return of 0 and of 100 means here, before the first score.
Read WP02 Measure Before You Model A title from the GFT paper programme; no released PDF is claimed. The bracket width is illustrative.
Source boundary
The programme supplies the sequence, not a forecast.
The programme sequence begins with capture and bought vision, adds forecasting once sales history exists and reserves emerging generative applications for later pilots.
P0 / SET UP
Set up opens no use case.
In the default scenario no case has an earliest phase of 0, so this phase builds the data spine only. Every use case waits on its thread.
WP14 The Industrial Data Spine
P1 / LAUNCH
Launch opens the first-tier vision case.
Computer-vision defect detection is the only case whose earliest phase is 1. Its floor comes from the digital strategy, section 7, and its illustrative data need sits under the default capacity of 40, so it drops through the weft.
Sourced floor, illustrative scores
P2 / SCALE
Scale adds forecasting, inventory and printing.
Forecasting and inventory carry sourced Phase 2 floors; digital printing uses an illustrative one. All three need more data capacity than the default of 40, so they stop at the weft. Raise capacity in the instrument to open them.
Sourced floors, illustrative printing *
P3 / OPTIMISE
Optimise is the earliest phase for the emerging cases.
Multi-model design pipelines and physics-constrained generation sit in the programme’s third tier with Phase 3 floors. Their data needs are the highest in the set, so they hang highest above the weft and wait longest.
Sourced floors, illustrative scores
Reading P1 Launch · 1 of 6 cases pass phase and data gates at a capacity of 40.
What the gates leave out
Use the shortlist to design a test.
Passing the gates does not demonstrate accuracy, security, rights to use data, safe process integration or economic value. A scalar capacity score cannot tell sales history from defect labels. Design the test before the pilot.
Inspect real fabric varieties and difficult defects: 3 of 18 swatches carry a hard defect in this illustrative layout.
Sector literature, context only, not used to calibrate any score.
Back-test against a simple baseline: the last 40 percent of the series is held out, with no future information in training.
Sector literature, context only, not used to calibrate any score.
Read WP04 Forecasting From a Cold Start
Establish a production-loss baseline before scoring a remedy.
Check that generated output becomes a manufacturable specification: 3 hand-overs, each with human review and a rollback route.
No external source is cited for this test.
Read WP14 The Industrial Data Spine
Paper titles from the GFT programme; no released PDF is claimed.
Not modelled: capital cost, operating cost, implementation capacity, vendor dependency, downtime, energy, financing. Build a separate costed business case. Not investment, legal or tax advice.
capital costoperating costimplementation capacityvendor dependencydowntimeenergyfinancing
Use the result in its boundary
Score it once, sequence it, then pilot it.
Use the shortlist to assign a problem owner, a baseline and an acceptance test. A high score is a reason to investigate, not evidence that an application will work in your factory.
Nothing settles in P0 Set up. The data spine comes first and every case waits.
Computer-vision defect detection settles in P1 Launch, the earliest phase its sourced floor allows.
P2 Scale adds forecasting, inventory and printing beside vision. Each still needs the data capacity.
P3 Optimise is where the emerging cases settle, once the earlier phases and data are in place.
0 of 4 checks. Complete the checklist to scope a pilot. This is not deployment approval.