Booking Management - Br/brfs: Gis Pd/vd Training

BOOKING MANAGEMENT - BR/BRFS GIS PD/VD TRAINING JULY/AUGUST, 2017

AGENDA • •

Overview of Booking Management Understand the Booking Management Process

o o o o o o o o

• • •

CFT Finalizes Assortment PD Brand Likes Cost Option

GIM Publishes Planned Receipts PD-GIS Reviews and Shares with Vendor Vendor Reviews and Assigns Factory PD GIS Confirms or Flags

MST Create PO GIM Completes Size & Pack Activities

Business and System SLAs Understand the Chase & Change Process Appendix

o Tool Navigation o FAQ

2

Overview of Booking Management

PETE CAPABILITIES

PETE = Product End-to-End

Enables end-to-end activities for Planning and Merchandising

Global Assort

Global Buy Plan

Price & Event Mgmt. (PEM)

Receipt Manager (Booking Management) Ad Hoc Reporting

Data feeds across all PETE Modules

Size & Pack

Global Reforecasting*

Allocation*

In Season Pricing (PEM)*

Enables inventory optimization across channels /markets in one platform PETE is continually evolving. Updates and new functionality are released approximately every 2-4 weeks

4

SMEE CAPABILITIES

SMEE = Sourcing & Manufacturing End-to-End

Enables end-to-end sourcing activities to support Product 3.0

Fabric Management

Sample Management

Quality Assurance

PI Test & Certification

Costing Tool

Production Change Management

Responsive Management

Booking Management

WIP

Capacity Management

Optimizes collaboration among brand, GIS and vendors in one platform SMEE is continually evolving. Updates and new functionality are released approximately every 2-4 weeks

5

PETE & SMEE INTEGRATION Brand

Product End-to-End (PETE) GA

Receipt Manager

Allocation

Buy Plan

PEM

IPM

Booking

Responsive

VD

CS/PD

MST

MM

QA

Vendors/ Mills

Sourcing & Manufacturing End-to-End (SMEE) CS/ PD /VD Workspace

MST Workspace

MM/QA Workspace

Vendor/ Mill Workspace

Role-based Workspace Capacity, Booking & Responsive

Fabric Management

Sample Management

Production/WIP Management

Quality Management

Supplier Performance

Core Functional Modules

Enterprise Legacy Applications • VPS

• PLM

• TradeStone

• PROMPT/SCMS

• WMS and Logistics

Product 3.0 • Right Products

• Made Well

• Delivered

• Transformation

6

WHAT IS BOOKING MANAGEMENT SMEE Booking Management module is integrated with PETE and other systems to provide on-line platform for GIS / vendors to review and manage bookings.

PETE Receipt Manager & Global Assort

Web portal

GIS (PD)

Tradestone

RPT2.0

SMEE

CPT

Booking Management

Prompt/SCMS

Brands

GIS (VD) GIS (MST)

Web portal

Vendors 7

WHAT ARE WE SOLVING FOR?

Challenge: As we Booking Management become increasingly will help address these responsive, it our is harder challenges for crossfunctional to manage teams, against all of MST-GIS: whom play a critical role tight booking timelines owns in thetobooking process track receipts creating the and PO that change over time

PD-Brand: owns finalizing costing

PD-GIS: ensures planning intent can be executed by vendors

8

BENEFITS Financial Control Places financial control with the Global Planning team. Receipts are made visible to all business partners when Global Planning chooses to do so

Single Source of Truth Reduces errors through a single source of truth that will increase the speed and efficiency of the booking process

Integration Connected to other PETE modules and GIS systems with plans to extend into order systems (e.g., PROMPT, SCMS), as well

Visibility

Benefits

Includes a reporting solution that aggregates data from a number of different sources (e.g., Buy Plan, Size and Pack, Order, GLV, etc.), providing greater visibility to inventory ownership at any given point in time 9

KEY DIFFERENCES TO TODAY New way of communicating planning intent

Planners have control over which receipts are published and when for partners to review

New way of evaluating draft bookings and confirming demand and supply align

PD-GIS will review the draft booking, flag if needed for brand action or confirm for order creation

New way of accessing the confirmed booking to manually create the PO

MST- GIS will only have visibility to the booking once it is confirmed

More direct communication between PD-GIS & Global Planning

PD-Brand also continues to play key role in managing costs and assessing sourcing options.

Ability to track changes to units over time

Provide full end-to-end receipt visibility, including planned units, published units, confirmed units, and booked units 10

DEFINING KEY TERMS

Receipt to Booking Life Cycle

Planned Receipt Published Receipts Draft Booking Flagged Booking Confirmed Booking

Receipt Plan in Receipt Manager, resulting from your final CP in Global Buy Plan. Includes total units and the fiscal in-DC week for the buy

Finalized receipts that are shared to business partners and downstream systems/reporting & require action (e.g., Capacity validation for RR or PO Creation at the time of a final book date)

The intersection of the planned receipt and sourcing details. Rapid Response bookings will remain in draft status (i.e., unconfirmed) until the final trigger date

Status to indicate an issue exists for the draft booking related to the receipt, sourcing details, or color

Status to indicate the draft booking can move forward with PO creation

11

ROLES & RESPONSIBILITIES All roles have critical responsibilities that impact other key business partners and our ability to achieve the ultimate goal of booking/PO creation Global Merchandising • •

Global Planning (GOP) • • •

Creates assortment Finalizes color in advance of final quantity milestones Resolves flags related to color challenges

•

•

PD-Brand

MST-GIS • •

Finalizes buy and receipt plan Publishes receipts Resolves flags related to unit challenges Owns Size & Pack

•

Reviews confirmed booking Creates PO

• •

PD-GIS • • • •

Attributes publish dates and other details in GA Finalizes sourcing details Resolves flags related to sourcing challenges

Reviews draft booking Validates capacity Shares draft booking with vendor Confirms/flags bookings Confidential

12

ROLLOUT PLAN - BR/BRFS Banana Republic

Banana Republic Factory Store

Go-live date

22 Aug 2017

3 Aug 2017

INDC cut-off

1st week of Jan 2018 and onwards - manage in SMEE

5th week of Dec 2017 and onwards – manage in SMEE

Go-live market/chann el

Retail: US/CA/JP Online: US/CA/JP/EU

Retail: US/CA/JP Online: US

Out of scope

Franchise - continue to manage via Delivery Tracker (excel)

N/A

13

END TO END PROCESS Final book1

Merchant

PD Brand

IM

PD GIS

Vendor

Brands ▪ Realize BOM CC

PETE Global Assort

Confirm booking + 1 week

PD GIS

MST

GIS/ Vendors

▪ Like cost option

Tradestone Costing

Final Book + 1 week

▪ Finalize and CP plan ▪ Publish receipts

PETE GBP /Receipt Manager

1 Refer to brand calendar for exact final book date 2 Flagged bookings for brand reference only 3 IM size & pack - 1 week from PO creation

▪ Review booking ▪ Share with vendor

SMEE Booking Mgmt

▪ Review booking ▪ Assign factory ▪ Review loading report

SMEE Booking Mgmt

▪ Flag booking ▪ Confirm booking

SMEE Booking Mgmt

▪ Review confirmed booking • Create PO3

SMEE Booking Mgmt / Prompt

Daily Box files2 14

END TO END PROCESS Final book1

Merchant

PD Brand

IM

PD GIS

Vendor

Brands ▪ Realize BOM CC

PETE Global Assort

Confirm booking + 1 week

PD GIS

MST

GIS/ Vendors

▪ Like cost option

Tradestone Costing

Final Book + 1 week

▪ Finalize and CP plan ▪ Publish receipts

PETE GBP /Receipt Manager

1 Refer to brand calendar for exact final book date 2 Flagged bookings for brand reference only 3 IM size & pack - 1 week from PO creation

▪ Review booking ▪ Share with vendor

SMEE Booking Mgmt

▪ Review booking ▪ Assign factory ▪ Review loading report

SMEE Booking Mgmt

▪ Flag booking ▪ Confirm booking

SMEE Booking Mgmt

▪ Review confirmed booking • Create PO3

SMEE Booking Mgmt / Prompt

Daily Box files2 15

PUBLISH DATES AND BOOK DATES There are multiple reasons to publish…  GIS requires visibility to quantities to plan capacity before the PO needs to be created.  Units required for Rapid Response confirmation  Passing off final quantities for PO Creation and exercising triggers

To simplify coordination publish dates are defined separately from book dates: Publish Date

When units are shared

Book Date

When units are booked

First date GOP needs to publish receipts.

PD-GIS confirms receipts for PO creation

Attributed in GA by PDBrand.

Attributed in Prod Comments in GA.

Note: VMI and Test Receipts will not be published in Receipt Manager (Out of Scope) Confidential

16

END TO END PROCESS Final book1

Merchant

PD Brand

IM

PD GIS

Vendor

Brands ▪ Realize BOM CC

PETE Global Assort

Confirm booking + 1 week

PD GIS

MST

GIS/ Vendors

▪ Like cost option

Tradestone Costing

Final Book + 1 week

▪ Finalize and CP plan ▪ Publish receipts

PETE GBP /Receipt Manager

1 Refer to brand calendar for exact final book date 2 Flagged bookings for brand reference only 3 IM size & pack - 1 week from PO creation

▪ Review booking ▪ Share with vendor

SMEE Booking Mgmt

▪ Review booking ▪ Assign factory ▪ Review loading report

SMEE Booking Mgmt

▪ Flag booking ▪ Confirm booking

SMEE Booking Mgmt

▪ Review confirmed booking • Create PO3

SMEE Booking Mgmt / Prompt

Daily Box files2 17

PD GIS REVIEW DRAFT BOOKING Action required  Use Google Chrome to access SMEE Booking Management  Leverage selections on the search panel to scope bookings and click ‘Submit’  Once data loads, then leverage filters at the header to fine tune data set to manage  Production Comments from GA will be available in SMEE. Prior to that, the production comments are included in the PDS report -

18

PD GIS REVIEW DRAFT BOOKING Best practice / notes  The source of Category/Sub Category/Item Type is Tradestone  These selections are mandatory in the search panel: (1) Planning Period or INDC Date [max. 180 days] (2) Brand

* Planning Period (Season) is based on season mapping between Global Assort and Tradestone for costing purpose. To ensure you do not miss any bookings, you may search by INDC date range and leave Planning Period blank. * If you wish to search for “incomplete” bookings as well, please leave Category blank

 If the booking status is “incomplete”, it means (1) BOM CC is not realized in PETE GA; or (2) there’s no Liked cost option in Tradestone; or (3) both.  Incomplete bookings (along with Flagged bookings) will be auto shared at box.com for Brand follow-up, until an automated approach is available in PETE. The box file is read only.  Incomplete bookings can NOT be shared with vendor (as sourcing information such as Category & vendor is missing)

19

PD GIS REVIEW DRAFT BOOKING Best practice / notes  Multiple cost options - If there’s “Y” under “Multi Cost” column, it means there’re more than one liked cost options which could occur due to:  Late booking/ chase by market/ channel with cost variance: Same style same color, April needs (by sea), May ( by air)

 PD GIS need to select the right liked cost option from a dropdown list

20

PD GIS REVIEW DRAFT BOOKING Best practice / notes  Multiple cost options - PD GIS need to select the right liked cost option from a dropdown list

“Y” under the Multi Cost column indicates there’re more than one cost option. Click on “Y” to review details

All “liked” cost options are displayed on the pop up screen. Check the box of the correct cost option and click Save.

21

PD GIS SHARE DRAFT BOOKING WITH VENDOR Action required  Filter booking status to “Published to PD”  Input additional information into GIS-Vendor Comments column for vendor reference (e.g. book greige only)

 Select draft bookings to be shared and click the “Share with Vendor” button

Best practice / notes  The “Share with Vendor” action applies only to selected bookings on the current page. Leverage the number of styles to be displayed per page to minimize number of pages, as illustrated below  OK to share with multiple vendors at once (each vendor can only review its own bookings), or filter by vendor before sharing  Once a booking is shared with vendor, all subsequent changes will be visible on vendor workspace automatically  When booking status is “Shared with Vendor”, PD GIS is not able to Flag or Confirm, until it’s submitted by vendor and booking status is changed to “Updated by Vendor”.

22

END TO END PROCESS Final book1

Merchant

PD Brand

IM

PD GIS

Vendor

Brands ▪ Realize BOM CC

PETE Global Assort

Confirm booking + 1 week

PD GIS

MST

GIS/ Vendors

▪ Like cost option

Tradestone Costing

Final Book + 1 week

▪ Finalize and CP plan ▪ Publish receipts

PETE GBP /Receipt Manager

1 Refer to brand calendar for exact final book date 2 Flagged bookings for brand reference only 3 IM size & pack - 1 week from PO creation

▪ Review booking ▪ Share with vendor

SMEE Booking Mgmt

▪ Review booking ▪ Assign factory ▪ Review loading report

SMEE Booking Mgmt

▪ Flag booking ▪ Confirm booking

SMEE Booking Mgmt

▪ Review confirmed booking • Create PO3

SMEE Booking Mgmt / Prompt

Daily Box files2 23

VENDOR REVIEW DRAFT BOOKING Action required  Use Google Chrome to access SMEE Booking Management  Leverage selections on the search panel to scope bookings and click ‘Submit’  Once data loads, then leverage filters at the header to fine tune data set to manage  Refer to GIS-Vendor Comments column for additional information from GIS (e.g. book greige only)  Input additional information into GIS-Vendor Comments column for GIS reference (e.g. incorrect first cost)  Click the “Save” button for internal review

Best practice / notes  Do NOT delete or overwrite information input by GIS when entering comments in the GIS-Vendor Comments column  If COO is incorrect, it can NOT be updated in Booking Management. Please work with PD GIS to update in Tradestone Costing, which will then reflect in Booking Management.

 “Save” will NOT change the booking status

24

VENDOR ASSIGN FACTORY Action required  Filter booking status to “Shared with Vendor”  Select draft bookings from the same COO  Use the mass update function at the header to select a factory from the dropdown list  Click the “Save” button for internal review

Best practice / notes  The source of factory is Vendor Profile System (VPS). If a new factory needs to be added, please work with PD GIS to add

into VPS first, which will then be available in Booking Management for selection  The list of factories available for selection is based on COO. i.e. if COO is X, user is only able to select a factory from the country of X  Factory will be auto populated if there’s only one factory from a specific COO

 Vendor is able to assign factory at Style, or CC, or booking level  Factory assigned by vendor can be over-written by PD GIS. Vendor is able to review the revised factory real time.  Vendor is able to review the capacity loading report at factory level once the factory allocation is saved 25

VENDOR UPDATE SPECIAL CONSTRAINTS Action required  Filter booking status to “Shared with Vendor”  Select draft bookings at style or cc level  Use the mass update function at the header to update special constraints  Click the “Save” button for internal review

Best practice / notes  Special constraints include: Embroidery, Garment Dye, Garment Wash, Print and Yarn Dye

 The purpose of updating special constraints is to enable visibility of capacity loading and mitigate delivery risk  Special constraints need to be updated if and only if there’s a capacity constraint (bottleneck), which has been indicated by vendor in the Capacity Planning Tool  Vendor is able to review the special constraints loading report once the input is saved

26

VENDOR SUBMIT TO GIS Action required  Filter booking status to “Shared with Vendor”  Select draft bookings to be submitted  Click the “Submit to GIS” button

Best practice / notes  Before submitting to GIS, review capacity loading report and special constraints report and ensure capacity issue has been addressed (e.g. increase offer capacity, re-assign factory, etc)

 The booking is read only for vendor once it’s submitted  If factory needs to be updated, vendor need to contact PD GIS to share the booking again, i.e. booking status becomes Shared with Vendor  Factory allocation is mandatory. Without factory allocation, vendor is not able to submit to GIS

 Generally vendor need to assign factory and submit to GIS within 1 - 2 days. (3 - 5 days if there’re capacity issues)

27

END TO END PROCESS Final book1

Merchant

PD Brand

IM

PD GIS

Vendor

Brands ▪ Realize BOM CC

PETE Global Assort

Confirm booking + 1 week

PD GIS

MST

GIS/ Vendors

▪ Like cost option

Tradestone Costing

Final Book + 1 week

▪ Finalize and CP plan ▪ Publish receipts

PETE GBP /Receipt Manager

1 Refer to brand calendar for exact final book date 2 Flagged bookings for brand reference only 3 IM size & pack - 1 week from PO creation

▪ Review booking ▪ Share with vendor

SMEE Booking Mgmt

▪ Review booking ▪ Assign factory ▪ Review loading report

SMEE Booking Mgmt

▪ Flag booking ▪ Confirm booking

SMEE Booking Mgmt Daily Box files2

▪ Review confirmed booking • Create PO3

SMEE Booking Mgmt / Prompt

28

PD GIS FLAG DRAFT BOOKING Action required  Select draft bookings to be flagged  Use the mass update function at the header to select one or multiple Flag Reason Code  Input additional information into GIS-Brand Comments column for PD Brand/Merchant/IM review  Click the “Flag” button

Best practice / notes  Flagged booking (along with incomplete booking) with GIS-Brand comments will be shared at box.com for Brand follow-up, until an automated approach is available in PETE. The box file is read only.

 Flagged booking will be un-flagged automatically and changed back to “Published to PD” once the corresponding issue has been resolved.  Flagged booking can be confirmed by PD GIS if (1) it’s flagged accidentally; (2) PO needs to be created while the issue is being resolved with Brand. Flag reason codes will remain if a flagged booking is confirmed.

 User can leverage the functionality of Check Production MOQ to filter bookings below MOQ. This functionality will be further enhanced; it has certain limitations as listed below:  It checks style level production MOQ only (no MCQ checking)  Not all markets/channels are on board (e.g. Franchise will continue to use Delivery Tracker)

29

FLAGS WILL BE RESOLVED BY CFT WITHIN ONE DAY #

Flag Reason Code

1 2

Incomplete Color

3 4 5 6 7

Incomplete Sourcing

8

Cost not Final

9

Inaccurate Sourcing

10

Use Case

Flag by

Booking Status

BOM CC TBD or missing Color TBD Fabric description TBD (RD# and details mentioned in merch comments column instead) Mill details TBD Vendor TBD COO; Transfer Point TBD Cost TBD Cost is not final according to offline discussion (Cost discrepancies) Cost is inaccurate

System PD-GIS

Incomplete Flagged

PD-GIS

Flagged

PD-GIS System System System

Flagged Incomplete Incomplete Incomplete

PD-GIS

Flagged

PD-GIS

Flagged

Incorrect COO

PD-GIS

Flagged

11

Units Change (incl Units change required (e.g. MOQ/MCQ) due to MOQ/MCQ)

PD-GIS

Flagged

12

INDC Change (incl - INDC change required Split Shipment) - Split shipment required

PD-GIS

Flagged

Accountable by Merchant

Resolution GM realizes color in Global Assort PD-Brand updates in PLM and reconfirms cost option in Tradestone

PD Brand PD-Brand confirms/reconfirms cost in Tradestone

PD Brand (will involve IM as needed)

PD-Brand reviews and communicates action required to GIM. PD-Brand confirms new cost in Tradestone, if needed 30

PD GIS FLAG DRAFT BOOKING - SUPPLEMENT WITH COMMENTS Flag Reason Code Cost not final Cost not final

Inaccurate sourcing INDC Change (incl Split Shipment) Units Change (incl MOQ/MCQ) Incomplete color Incomplete sourcing

Comments Examples Final FC cost should be $$ as per promoted cost option with fabric RD#12345. Please refer to email from XXX dated YYY with subject line “ZZZ” Revised RFQ promoted for MCQ upcharge. Incorrect cost option liked. Vendor should be xxx and FC should be $$ with cost option desc XXX. Please refer to email dated xx/xx Need split delivery due to vendor capacity: 10/15 INDC 2000 units 10/31 INDC 2000 units for details, please refer to email dated XXX. Need to meet MCQ 1000 units. This booking is auto-flagged because of the lack of realized CC for the booking * This booking is auto-flagged because of missing a liked-cost for the style cc *

* This is a generic comments and it’s auto populated

31

FLAGGED - AND INCOMPLETE - BOOKING WILL BE SHARED AT BOX •

Department MENS DENIM MENS DENIM MENS DENIM MENS DENIM MENS KNITS MENS KNITS MENS KNITS MENS KNITS MENS KNITS MENS KNITS MENS KNITS MENS KNITS

Market Canada Europe Japan USA Canada Canada Europe Europe Japan Japan USA USA

Channel Flagged Incomplete Grand Total RETAIL 101 10 111 RETAIL 130 130 RETAIL 103 9 112 RETAIL 128 5 133 ONLINE 51 51 RETAIL 21 21 ONLINE 54 54 RETAIL 11 11 ONLINE 61 61 RETAIL 24 24 ONLINE 61 61 RETAIL 7 7

Each zipped file contains two CSV files: one is the list of incomplete and flagged bookings with comments; one is the summary table by Dept/Market/Channel

PD-Brand and GM are expected to access the Box file every morning in the two weeks following a Book Date o If Global IM input or action is needed (e.g., Capacity issue with an implication on Units), PD-Brand is expected to engage GIM o Global IM will have visibility to flags within the Booking UI and is not expected to access the file on a daily basis

•

The Box file will be saved by Division within the below folder: o ? • The same file will be updated daily at 7:45pm HK time (i.e., there will not be a daily history of flags - once a flag is resolved, it will drop from the file the next day) • The file is read only • Communicate offline if a flag needs to be clarified 32

PD GIS CONFIRM DRAFT BOOKING Action required  Select draft bookings to be confirmed  Ensure factory has been allocated  Use the mass update function at the header to input Agent Dept Code and Corp Dept Code  Click the “Confirm” button

Best practice / notes  Confirm booking only when PO needs to be created

 Factory* / Corp Dept Code / Agent Dept Code are mandatory fields before a booking can be confirmed  Confirmed booking will show up on MST & Vendor workspace real time  No un-confirm or recall function; communicate offline to MST and other stakeholders if a booking is confirmed accidentally.  Confirm all CCs under the same style with the same receipt week at the same time to make sure we don’t inadvertently

create more POs than necessary.

* Factory is auto-populated if there’s only one factory for the vendor-COO. Both PD GIS and vendor can assign factory; PD GIS can over-write vendor’s factory allocation.

33

PD GIS CONFIRM DRAFT BOOKING Best practice / notes (cont.)  Monthly Book / RR: the MB and RR attributes and trigger dates will flow from RPT2.0 to Booking Management. MB and RR bookings can only be confirmed on or after final trigger date. Share projection with vendors prior to final trigger date.

Upon PD Brand nomination in RPT2.0, Responsive Capability Type and Trigger will be displayed in Booking Mgmt

Once PD GIS provides trigger dates in RPT2.0, the trigger dates will be displayed in Booking Mgmt

34

TOOL DEMO Final book1

Merchant

PD Brand

IM

PD GIS

Vendor

Brands ▪ Realize BOM CC

PETE Global Assort

▪ Like cost option

Tradestone Costing

1 Refer to brand calendar for exact final book date 2 Flagged bookings for brand reference only 3 IM size & pack - 1 week from PO creation

Final Book + 1 week

Confirm booking + 1 week

PD GIS

MST

GIS/ Vendors ▪ Publish receipts

PETE Receipt Manager

▪ Review booking ▪ Share with vendor

SMEE Booking Mgmt

▪ Review booking ▪ Assign factory ▪ Review loading report

SMEE Booking Mgmt

▪ Flag booking ▪ Confirm booking

SMEE Booking Mgmt

▪ Review confirmed booking • Create PO3

SMEE Booking Mgmt / Prompt

Daily Box files2 35

BOOKING CONFIRMATION - FROM PD TO MST •

PD to leverage Booking Management Tool to confirm bookings to MST o NO email request is required to be sent to MST Mailbox for PO Creation Confirm Booking

36

BOOKING CONFIRMATION - FROM PD TO MST Contd. •

Prior to confirming bookings to MST, PD needs to ensure below checklist is followed: •

Vendor has reviewed and completed their respective detail(s) - like Factory

• Mandatory information required to create POs are complete and accurate in the tool o Enclosed is the list of mandatory fields o If any of the fields are not accurate, update Trade Stone as applicable or work with NY PD / IM / Merchants to get the same fixed

37

KEY CALLOUTS •

PO# would be auto populated (in Near Real Time) on the Booking Management Tool (BMT) itself. MST would NOT send any email confirmation stating closure / PO#s

•

TnR PO Creation would NOT follow BMT process; this needs to follow AS IS process (requesting via Mailbox)

•

Franchise PO Creation would NOT follow BMT process; this needs to follow AS IS process

38

UN-CONFIRM BOOKING In cases of exception, where booking has been confirmed to MST but now needs to unconfirmed (either Cancel or Hold), needs to be managed as an offline process outside the BMT •

PD to extract excel from BMT with ONLY those Styles CCs / Receipts that need to be held up for PO creation o The original format needs to be maintained and NO filters need to be applied

•

Cadence should be within 1 working day

•

PD would need to communicate this over the email (as BMT does not support any unconfirm use case). Email needs to be sent to [email protected]

•

Subject line of email – BOOKING MANAGEMENT – HOLD PO CREATION

•

Other than HOLD / Cancel requests, NO offline emails need to be sent to MST

39

Looking Ahead

WHAT’S COMING? Systemic Visibility to Attributes & Milestone Dates

Change Log Integration ▪ Enabling the brand to request a change in their native tools (e.g., Buy Plan for Planning) and to route that to functional leadership and GIS for approval. Upon approval, system executes the change ▪ Locking mechanism ▪ Chase attribution

Order Automation ▪ Once a booking is confirmed, the order is auto created. Includes the ability to automatically update a PO if changes are made

Booking Management will be continually enhanced with additional functionality over the next few seasons

▪ Early Book and Critical style attribution ▪ Providing visibility to ALL book dates and other sourcing milestone dates (e.g., fabric dyed, tickets printed) systemically to help manage workflow

Cross-functional, cross-tool Collaboration ▪ The ability to support in-app communication (e.g. flagging) across different functions (e.g., Global Planning and GIS) 41

SMEE BOOKING MANAGEMENT ROADMAP Process & System Enhancements • MST task manager & issue resolution capabilities and streamlined processes • Flagging code and process improvement - make reason codes more specific to drive efficient resolution (e.g. link to cost option status to differentiate accountable party) • Incomplete booking - Brand leverage reporting prior to final book to resolve outstanding issues and minimize incomplete bookings • Notification at different workflow stages and key events (e.g., multiple costs, PO creation, etc.) • Workflow enhancement - e.g. recall sharing with vendor

SPR18 (end Aug)

SUM18

FY18

Process & System Enhancements

Process & System Enhancements

• Attribution - provide visibility for Fast Track/Placeholder on UI and exclude from list of incomplete bookings at box • Flagging code and process improvement - split Unit change and INDC change • Visibility of re-publish status post confirmation • Adoption of PCL by brand and auto-confirm capability (TBC) • Link PO# to both confirmed & non-confirmed booking • Add ship cancel date • Remove confirmation validation for 0 unit receipts • Reporting - compare re-confirmed vs confirmed booking to facilitate PO update by MST

• Publish Gate: receipt can only be published when BOM CC is realized AND cost option is liked. i.e. block publishing of “incomplete” booking. • Publish Locking: receipt can only be re-published post the blackout period AND post approval via PCL • Auto-republish and auto-confirm: post approval via PCL, receipt is auto-republished in Receipt Manager and auto-confirmed in SMEE Booking Management 42

SLA’s

BUSINESS SLA Brand and GIS have pre-established SLAs for all Booking activities Scenario

IM publishes

Days

0

GIS-PD checks for complete/a ccurate info

GIS-PD flags for color/cost 1

GP/GM resolves flag

GIS-PD validates capacity

1

GIS-PD flags for units 1-3*

Task

Timeline - BRFS

Timeline - BR

Owner

Final book received via SMEE

8/04 Asia time

8/23 Asia time

IM

CFT resolves flag

GIS-PD confirms

1

1

Remarks

Review bookings - confirm or raise flags where applicable

8/04 to 8/11

8/23 to 8/30

GIS PD

Applicable for "complete" bookings only . GIS PD will not be reviewing "incomplete” bookings

Resolve Flags

8/04 to 8/11

8/23 to 8/30

Brand CFT

Flag resolution SLA is 1 day

All bookings to be confirmed in SMEE

No later than 8/11

No later than 8/30

GIS PD

Create POs

8/14 to 8/18

8/31 to 9/07

MST

Size/Pack PO

8/21 to 8/25

9/07 to 9/14

IM

This is dependent on Brand CFT resolving flags within 1 day SLA . This activity will be delayed if flags are not resolved within SLA *Applicable for only those bookings which are confirmed by GIS PD in SMEE

* No change to RR SLA’s, i.e. 1 working day for Booking confirmation by PD GIS, 1 working day for PO creation by MST and 1 working day for Size & Pack by IM

44

SYSTEM SLA SLA’s for step execution include… Activity

SLA

Time for a liked cost to be recognized by PD Screen

Near real time

Publishing Receipts from Receipt Manager to be viewed in PD Screen

Near real time

Shared Receipts from PD Screen to Vendor Screen

Immediate

Confirmed Receipts from PD Screen to Vendor/MST Screen

Immediate

MB/RR attribute and trigger date from RPT2.0 to Booking Management

Near real time

GIS flags or confirmed receipts in PD Screen to be visible in Receipt Manager

Near real time

If Order is created, time for Order to be visible in Receipt Manager UI and Booking Management

Near real time

45

Chase & Change Management

CHASE & CHANGE MANAGEMENT As is… Type of changes

BR

BRFS

Receipt changes

SMEE-PCL

Offline/email

Product changes

Merch change log

Offline/email

Vendor changes

SMEE-PCL

Submit in WIP Approve offline/email

To be…

 Add “post-confirm” to booking status when the booking is republished post confirmation  Integrate SMEE-PCL with Booking Management and enable autoconfirmation  More details to be communicated separately 47

Change Indicator and Notifications

CHANGE INDICATOR IN BOOKING MANAGEMENT

Post 6/2 change can be initiated via the change process

49

CHANGE INDICATOR - SCOPE Changes captured in the change indicator

Changes NOT captured in the change indicator (will be reflected in a new booking)

Order units

INDC

First cost

Market

Color code

Channel

Color description

Vendor

Color comment

COO Change Cancel / Cut Chase

CC drop/CC re-activate Ship Mode Responsive Capability Type

Booking status ELC * Transfer point * Terms of sale *

Pack factor * Duty rate *

* Change history will display “Other Sourcing attribute”

50

CHANGE NOTIFICATIONS  User can subscribe for notification which will reflect on SMEE homepage. User can also choose to receive notifications by email (optional)

 Notification by email:  One email per day sent at 09:30am Hong Kong time  Detailed bookings based on subscription criteria will be listed in email body, and can be copied and

pasted to excel

 Notification on SMEE homepage:  Daily refreshed at 09:30am Hong Kong time

 Changes of the last 24 hours are captured  Notifications can be set up at Brand/Division/Department/Vendor/Category level 51

CHANGE NOTIFICATIONS - SUBSCRIBE Click on user name and then on “My Subscription”

Based on user profile from HR. Not-editable

Subscribe daily email

Subscribe daily email

Define subscription criteria: 1. Select “Daily Email” to receive daily summary email. 2. Click “+Add” to add additional row Click on “Save” to make notification set-up effective 52

CHANGE NOTIFICATIONS - ON SMEE HOMEPAGE

53

CHANGE NOTIFICATIONS - BY EMAIL

54

Tool Navigation - Booking Management (as attached)

Confidential

FAQ - Booking Management (as attached)

Available on SMEE homepage

Confidential

End of Document