GEMINI & COSTING

01 Welcome / Agenda

02 Proposed Timeline

Questions & Answers

03
- Current response
- Still in analysis
- New questions today?

04 Request for Analysis by Dec 2

2
PROPOSED
TIMELINE

3
 DRAFT TIMELINE PROPOSAL
Data Structure Change and Import/Export Milestones with Factory Partners (FPs)

Oct 2021 Nov Dec Jan Feb Mar Apr May 2022

Requirements & Solution

Design Nike Import/Export Update Build & QA

Nike Internal
FP Internal Analysis Downstream Data End to End
Testing Testing 1
Issue
Nike Resolution
Review/Up End to End
-date Plan Code Stabilization
Testing 2

PROPOSED FP Data Change Build & QA

Pilot
User Communications User Training
Import/Export

Data Cutover and

App Launch
Early June

Dec 1: FP Share Initial Analysis
FPs to provide Nike an initial assessment of:
• Level of effort
• Response to proposed timeline
• Risks and unknowns
Late Jan: FP Build & QA Complete
Timeframe to be confirmed pending FP
analysis!
• Build and internal testing completed
• Ready for pilot testing
Late Feb: Pilot Import/Export Early Apr: Complete E2E Testing
Two rounds of end-to-end testing will allow
Nike provides FPs hands-on experience of the
time for issue resolution and retesting.
updated DLA
• FP and Nike roles and responsibilities for
• In Dev environment
E2E testing to be determined
• With new data contract and season-source-
colorway structure
• FP may export, make test modifications to
data, and import

4
Q&A

5
 Q&A Topics

Gemini Construct

1.In Gemini do we still have something similar like DEV style in PCX?
2.Nike Dev will release the BOM direct in Gemini? So, the PCC Dev can update BOM in Gemini as
well?
3.BOM is created in PCX. I heard it will be overridden by Gemini in meeting, but just double
checking if I get it right as below:
• When it initially creates new colorway in PCX, only create the section headers, others are empty, no
ONE BOM part name there,
• Then WHQ works in Gemini for BOM part name/material etc. detail,
• Then data flow back to PCX to have exactly same BOM detail from Gemini. Previous PCX one BOM
would not impact new season Gemini BOM for existing model.

6
 Q&A Topics

Process
1. In PCX one BOM, we can edit BOM at the same time for many colorways if they share the same material. However, we
can edit many color at the same time in Gemini?
2. Need further discussion about how to manage transfer model or multiple sourcing model on Gemini. Really hope future
Gemini can ease the work about multiple sourcing BOM management.
3. About BOM ID, as meeting mentioned, there will be new BOM ID for true carry over colorways for costing new season
CBD working. Would like to D-check more detail:
• Will there be many BOMs with different BOM ID in Gemini if it carry over for many seasons?
• Do we need to export the Json file based on every new BOM ID for NCF working again and again when carry over? Or cost sheet
ID will be generated once new BOM ID is created automatically by system, and costing team just upload with new cost sheet ID, no
need developer extra duplicate work for export/release again?
• What about the previous season colorway carry over after Gemini go live? I think Gemini will have a BOM from PCX if it carry over,
no need dev to write again in Gemini, and no issue for costing team to use, right?

4. In PCX, material 100 = new material , is that still the same in Gemini? In last meeting, I remembered we won’t have
material 999 in Gemini, right?
5. How about costing related data, such as tooling, will we maintain it in PCX or through Gemini?

7
 Q&A Topics

Export/Import Contract

1.New BOM header attribute “bomPartUUID” is a unique BOM ID for every CWS and season
variation, so the “bomPartUUID” is also present for every version of CWS bom?
2.Do we still need to keep the value of “developmentColorwayIdentifier” when uploading BOM
JSON to MASS BOM Import app? (because we have UUID to identify which BOM need to be
updated)
3.If we download multiple BOM JSON, by what attributes we can determine some boms belongs
to the same dev style (by “styleName” ?)

8
 Q&A Topics

BOM Data Conversion

1.What is the scope & methodology of Data conversion from PCX to Gemini? (we will be given a
list of BOMs? And update new attributes for these BOMs ? ) we will make data conversion plan
for our internal system accordingly.

9
NEXT STEPS

10
 Focus Areas for PCC Tech

Questions for this Session

Go-around to each Factory Partner:

1. Do you have what you need to do your analysis?
2. If not, what do you need?

11
 Focus Areas for PCC Tech

By December 1 (WHQ time):

• WHQ gives responses to additional questions

• FPs to provide WHQ an initial assessment of:
• Level of effort
• Response to proposed timeline
• Risks and unknowns

Send email response and technical questions to:

Ken Lo and Manju Pandit: ken.lo@nike.com; manunath.pandit@nike.com

Next meeting: Tentatively planned for Dec 2 (WHQ time)

12
APPENDIX

14
CURRENT/FUTURE
STATE

15
DEVELOPER
BOM & BOL Import: Current State
WHQ

Create BOM
DEVELOPER

Export BOM from Export each Mass import all

Complete &
PCC

PCX individual BOM colorways

audit BOM in
& import BOM colorway from (JSON files) into
PCC System
into PCC System PCC System PCX
COSTING

Export BOM &

Export BOL from Add Costing Mass import
BOL for each
PCC

PCX Populate BOL in information to BOM & BOL

individual
& import BOL PCC System BOM in PCC colorways into
colorway from
into PCC System System PCX
PCC System

PCC
PCX System
16
DEVELOPER
BOM & BOL Import: Future State
WHQ

Create BOM

NEW
DEVELOPER

Export BOM from Export each Mass import all

Complete &
PCC

PCX individual BOM colorways Publish Data to

audit BOM in
& import BOM colorway from (JSON files) into PCX
PCC System
into PCC System PCC System Gemini
COSTING

Export BOM &

Export BOL from Add Costing Mass import
BOL for each
PCC

PCX Populate BOL in information to BOM & BOL

individual
& import BOL PCC System BOM in PCC colorways into
colorway from
into PCC System System PCX
PCC System

PCC
PCX System
17
 PCX: Current State
PCX always has one BOM that contains all Colorways, Colorway-Source Level data

Example: PCX UI – for Vamp material

BOM ID: 101 Style: JORDAN MELO FINALE

Seasons: All Seasons

Part Variation Material Color Fty-Factory Fty-Net

Name Unit Price Usage
VAMP Style 5678 Red
CW1
CW1-S 2 3
CW2
CW2-S 3 4

18
 PCX: Future State
PCX will have one BOM per Season > Source> Colorway

Example: PCX UI – for Vamp material

BOM ID: 101 Style: JORDAN MELO FINALE

Season: SU20 Colorway : CW1
BOM GUID: a0441d11-fdeb-464d-ad41-ce92d1419ba4 Source: Pouchen

Part Name Material Color Fty-Factory Unit Price Fty-Net Usage

VAMP 5678 Red 2 3

BOM ID: 102 Style: JORDAN MELO FINALE

Season: SU20 Colorway : CW2
BOM GUID: 1c95185e-0800-4a90-9e71-8c671bc0b91f Source: Pouchen

Part Name Material Color Fty-Factory Unit Price Fty-Net Usage

VAMP 5678 Red 4 5

19
 Mass Import: Update Scenarios
Update Use Case 1

Inheritance is not broken and rollup Indicator is 1 and Material has changed to 6000

PCX UI – Before Export

Vamp material Set at Style Level

Part Variation Material Color Fty-Factory Fty-Net

Name Unit Price Usage
VAMP Style 6000 Red
CW1
CW1-S 2 3
CW2
CW2-S 3 4

20
 PCX: Future State
PCX will have one BOM per season - colorway-source, so there is no need for Rollup

Example: PCX UI – for Vamp material

BOM ID: 101 Style: JORDAN MELO FINALE

Season: SU20 Colorway : CW1
BOM GUID: a0441d11-fdeb-464d-ad41-ce92d1419ba4 Source: Pouchen

Part Name Material Color Fty-Factory Unit Price Fty-Net Usage

VAMP 6000 Red 2 3

BOM ID: 102 Style: JORDAN MELO FINALE

Season: SU20 Colorway : CW2
BOM GUID: 1c95185e-0800-4a90-9e71-8c671bc0b91f Source: Pouchen

Part Name Material Color Fty-Factory Unit Price Fty-Net Usage

VAMP 6000 Red 4 5

21
HOW ARE GEMINI &
COSTING RELATED

22
Factory Partner Impacts Due to Gemini

BOM Flattened Data Factory Internal

Import/Export Structure System

One
Data Change Volume Historical
BOM to
Contract Loader in BOM Influx of BOM/CBD
Season
App IDs BOM IDs Info
al BOM

• Addition of seasonal • Unique BOM ID in • Factory Internal

attribute(s) in export/ each colorway – system changes for
import contract (BOM source – season for converted BOM –
only, not BOL) BOM Import Structure, Reference,
Volume
• Consequent changes • Accommodate
on Data Loader. UI volume of BOM ID’s • Prep for SRTs
experience to remain change (post
the same cutover) • Retain historical BOM
or CBD information
23
 Data Conversion
One BOM Seasonal BOM

Dev Style 1 Dev Style 1

BOM BOM
ID 001 ID 001

FA21 SU22 HO22 FA21 SU22 HO22

CW1 CW2 CW3 CW1 CW4 CW5 CW1 CW2 CW3 CW1 CW4 CW5
BOM BOM BOM BOM BOM BOM
ID 001 ID 001 ID 001 ID 001 ID 001 ID 001

Primary
Source
BOM BOM BOM BOM BOM BOM BOM BOM BOM BOM BOM BOM
ID 001 ID 001 ID 001 ID 001 ID 001 ID 001 ID 001 ID 003 ID 005 ID 007 ID 009 ID 011

BOM BOM BOM BOM BOM BOM BOM BOM BOM BOM BOM BOM
ID 001 ID 001 ID 001 ID 001 ID 001 ID 001 ID 002 ID 004 ID 006 ID 008 ID 010 ID 012

Secondary
Source
• Same BOM ID • Different BOM ID for each Colorway Source AND Season
variation
• Variations available for CW-Source related differences • BOM ID will be as unique as a Cost Sheet ID

IMPACT: One BOM ID will become 50X BOM ID’s

24
 BOM Import Data Contract 4.0
• BOM Import v4.0 – introduce seasonal and Gemini related attributes

Update BOM Header BOM Line items

Attributes Added BOM Part UUID Line item UUID

Season Identifier
Attributes Removed Rollup variation level (Roll Up Indicator)

• In Seasonal BOM –
• a unique BOM ID will be present for every season-CW-source combination
• Season Identifier (e.g. “SP22”) will help Factory map the season of the BOM
• Apart from the BOM ID, a Universal Unique Identifier (UUID) is being introduced for header and every line item. This
unique ID needs to be retained and passed back without any change.
• Due to a flattened BOM structure in Season BOM (unlike One BOM – Dev Style/CW /CW-S layers) there is no roll up
logic. Hence Rollup variation level (Roll up Indicator) is being removed.

Import BOM v4.0 contract Import BOM v4.0 sample payload

25
 From To
Seasonless BOM Seasonal BOM
Conversion / migration CW –
Style BOM 1 Source - BOM 1 BOM 2 BOM 3 BOM 4 BOM 5 BOM 6 BOM 7
Season

CW BOM 1 BOM 1

CW -
Sourc BOM 1 BOM 1 BOM 1 BOM 1
e

Seasonless BOM Import Seasonal BOM Import

Import
by PCC Single Import Contract Mass Import Contract
Single Import contract Mass Import contract
SP20 Unique ID
Unique ID BOM ID
Import Unique ID
Unique ID BOM ID Unique ID
Unique ID BOMSeason
ID ID
PCX
PCX
BOM ID Colorway ID
by PCC Unique ID BOMSeason
ID ID
Season ID
-
Conversion /
Season ID Colorway ID
BOM ID Colorway
Season ID ID BOM ID Colorway ID - -
Season ID Colorway ID - Import - Unique ID
Season ID -

migration
Colorway ID - - - BOM ID
BOM ID: 123 Unique
- ID by PCC Unique ID
-
- Unique ID BOM ID Colorway ID Unique ID
BOM ID
BOMSeason
ID
Colorway
Season ID
ID
ID
CW – Colorway ID: Unique ID
BOM ID
BOMSeason
ID
Colorway
Season ID
ID
ID
Version No Season ID Colorway ID -
-
Colorway ID
Source Version No.: Season ID Colorway ID - - -
-
Unique
- ID
-
Level - Colorway ID
-
-
Unique
- ID
-
Unique ID
Unique ID BOM ID
BOMSeason
ID ID
- -
Unique ID
Unique ID BOM ID
BOMSeason
ID ID
SU20 BOM ID
Season ID
Colorway
Season ID
Colorway ID-
ID-
-
- BOM ID Colorway
Season ID ID- Colorway ID- -
Unique ID
BOM App
Season ID Colorway ID- - -
Colorway ID- -

BOM App BOM ID

-

Season ID Import
Colorway ID Import by PCC
Version No. by PCC
- Future
State

Seasonal Cost Sheet Seasonal Cost Sheet

SP20 SU20 SP20 SU20

Spec: 001: Colorway – CW1 Spec: 001: Colorway – CW1 Spec: 006: Colorway – CW1
Spec: 006: Colorway – CW1
CW – Cost Sheet ID - 234 Cost Sheet ID - 789
Cost Sheet ID - 234 Cost Sheet ID - 789
Source Calculate Calculate Version No.: A.5 Calculate Version No.: A.9 Calculate
Version No.: A.5 Version No.: A.9
Level
BOM ID: 123 BOM ID: 123 BOM ID: 456
BOM ID: 123
Version – A.20 Last Used BOM: A.16 Version – A.20 Last Used BOM: A.16 Version – A.40 Last Used BOM: A.36
Version – A.40 Last Used BOM: A.36

26
 Seasonal BOM Impacts
PCX Costing Factory Partner

BOM Contract • Addition of season attribute on FP contract BOM Contract • Contract change implementation
Change • Check impact on PCX Contract Change • Refactor Internal systems

Mass Import • DLA logic BOM • One BOM to Seasonal – Process/Tech change
DLA Conversion
• PCX validations • Migration of BOM ID – Volume Performance

BOM Import • Removal of rollup, primary/secondary, • Development runway for timing (~6
Engagement
Validation duplicate logic months)
• Q4: System Readiness Testing (SRT)

Cost Sheet • BOM drop down, migration

Changes
• Last Used and Early/Late buy

Downstream • PARC Contract changes/Perf, CBD Display

Impacts • Snowflake impacts

27
Gemini Design Excerpts
Unified Nike Design System

28