CURRENT STATE/ FUTURE STATE (SPIN) - Bonnie...

CURRENT STATE/ FUTURE STATE (SPIN)

SEARS PRODUCT INFORMATION NETWORK (SPIN)

CURRENT STATE/ FUTURE STATE

__________________________________

SPIN (Online Business Unit)

Created by

BONNIE ALICEA PhD, abd

CHANGE MANAGEMENT ANALYST

For internal use only. Nothing contained herein shall be disclosed outside Sears Holding Corporations without proper authorization.

1


AREA OF STATE CHANGE OVERVIEW

Area Current State Future StateProcess Flows 7 Different process flows with built timeframes

ranging up to 6 weeks2 different flows to create items (external and internal providers)

System of Record No system of record results in redundant updates and increased errors

SPIN will be the one system of record.

Build and Enrichment Single Third party vendor owns build and enrichment

Reduce dependency of 3rd Party service

Metadata Internally built content metadata requires enrichment by external vendor

Reduce dependency of 3rd Party service

Data Governance Lacks true data governance Establish and controls data governanceQuality Management Lacks quality management

• Limited quality management processes• Content quality varies across categories • Multiple integration points lead to high

reject rates

• Formal quality management processes• Content quality improves with system of

record and 3P software• Reduced integration points

Time • Systems and process complexity• 2-6 week average build cycle

• Systems and process simplified• 1 day – 2 week average build cycle

2


TAKE WITH FLOW

Item Lifecycle Phase

Task Current State Performed by Future State Performed By Effort req/task

Process Change?

1 Initiation 1A Select, buy

merchandise from supplier

FLS buyer (FLS org)

Unchanged FLS buyer (FLS org) N

1B Create item data in legacy systems (IMA, CORE, RIM, etc.)

The Merchandise Support Team builds TW items directly into IMA that we are responsible for (i.e., Tool catalog items that are stocked).

FLS buyer (FLS org)

Unchanged? FLS buyer (FLS org) N

1C Obtain and attach digital assets

Task happens in Complete Item Build phase (task 2E)

ARS Gather and load digital assets into IMA from manufacturer vendor

FLS buyer (FLS org) Y

2 Content Creation

2A Import items from IMA into content system

Items are imported into WEBCON from IMA

IMA, TCN Items are imported into SPIN from IMA. IMA WebTab data is primary source content.Where there is no IMA Web Tab data, IMA base data is taken.

IMA, SPIN Y

2B Confirm items to sell online

FLS buyer (FLS org) works through list of newly imported items from IMA and selects those that will be sold online. Kmart buyers do this fully in webcon, Sears buyers download some info from webcon and complete the process using spreadsheets sent to ARS.

FLS buyer (FLS org)

Confirm item to be sold online; if yes start build process with Task 2C; if no flag item for 'excluded'


2C Specify Item Details: Enter product title

in Webcon FLS buyer (FLS org)

Information provided by the vendor on the IMA Web Tab will be utilized, so this task may be reduced.

FLS buyer (FLS org), Vendor

Y

3

CURRENT STATE/ FUTURE STATE (SPIN) Item

Lifecycle Phase


Process Change?

Specify Item Details: Enter product description


Information provided by the vendor on the IMA Web Tab will be utilized, so this task may be reduced. Items sent to Schawk for image will have copy provided by Schawk

FLS buyer (FLS org), Vendor, Schawk

Y

Specify Item Details: Select web hierarchy

in Webcon Online Merchant (OBU org)

user will select Item Class - web hierarchy(cross-categorization) will be derived from the selected item class


Specify Item Details: Attach attributes individually


No longer applies. All the user has to do in SPIN is specify the item class, and the system will automatically attach the appropriate set of attributes.

FLS buyer (FLS org), SPIN

Y

Specify Item Details: Fill in attributes Values for each item


Unchanged FLS buyer (FLS org) Y

2D Image - Option 1 (Vendor image): Obtain digital assets from vendor, mfg etc.

ARS This should done at the beginning of the process by the FLS buyer (FLS org) but can be done here on an exception basis.

N/A Y

Image - Option 1 (Vendor image): Submit image

Image is copied to ARS ftp site FLS buyer (FLS org)

Image is loaded directly in SPIN FLS buyer (FLS org)

Image - Option 2 (3P Photo shoot): Attain sample/handover to photo vendor

FLS buyer (FLS org)

Unchanged FLS buyer (FLS org)

Image - Option 2 (3P Photo shoot): Specify photo instructions

Kmart in WebCon UI; Sears uploaded via spreadsheet into WebCon

FLS buyer (FLS org)

No longer applies. Photo instructions will be defaulted according to item class. However, the user will have the option to overwrite the default.

FLS buyer (FLS org), SPIN

Item Task Current State Performed by Future State Performed By Effort Process

4

CURRENT STATE/ FUTURE STATE (SPIN)Lifecycle Phase

req/task Change?

2E Additional Build Options: Define bases/variations

in Webcon Online Merchant (OBU org)

SPIN will recommend groupings but confirmation will need to be done by a user.


Additional Build Options: Define collections - identify/select collection items, provide collection title

in webcon, TCN or through ARS Online Merchant (OBU org)

FLS buyer (FLS org)

Additional Build Options: Define collections - input collection image instructions (if needed)

in webcon or added to the upload/download image request

Online Merchant (OBU org)

(is there a default for collections too?)

FLS buyer (FLS org)

Additional Build Options: Define collections - flag collection for bundle pricing

via ARS?? Online Merchant (OBU org)

FLS buyer (FLS org)

Additional Build Options: Specify coordinating items

in WebCon or TCN Online Merchant (OBU org)


Additional Build Options: Specify Accessories

in WebCon or TCN Online Merchant (OBU org)


2F Approve/Submit for build

Kmart users flag for send in WebCon UI; Sears submits spreadsheet to ARS

FLS buyer (FLS org), Online Merchant (OBU org)

Users will be able to publish and/or assign items to 3P. If assigned to 3P, a task appears on 3P content specialist's dashboard. Item never leaves the system; 3P content specialists performs work in the system

FLS buyer (FLS org), Online Merchant (OBU org) via SPIN

Y

Item Lifecycle


Process Change?

5

CURRENT STATE/ FUTURE STATE (SPIN)Phase

2G Optional 3P tasks: Create/colorize swatches

ARS

Optional 3P tasks: Create color chips

ARS

Optional 3P tasks: Alter images (crop, change background color, etc.)

ARS Image provider/photo agency will be responsible for creating finished images.

Image provider Y

Optional 3P tasks: Proof content with manufacturer

ARS No longer applies. N/A Y

2H Shoot images (when requested) - 3P

Schawk, RRD Unchanged Schawk, RRD

Send images (when requested) from 3P photo shoot to ARS

Schawk, RRD Photo agency will be responsible for creating finished images and systemically sent/loaded to the SHC system.

N/A Y

Upload images to S7

ARS SPIN will send images to S7 as they are loaded into the system. No human intervention is required.

SPIN Y

Receive manifest file

ARS Manifest will be replaced with response from API call. No human intervention is required.

SPIN Y

Update item with image URL

ARS SPIN will rename loaded images according to naming conventions, and will update the item with the appropriate image URL. No human intervention is necessary.

SPIN Y

Upload PDFs to AKAMAI.

pdf is sent via email to ARS or Content Specialist; pdf is loaded directly into Akamai and url of pdf is added to the item along with type of PDF (owner's manual, warranties etc.)

ARS SPIN will rename loaded PDFs according to naming conventions, and will update the item with the appropriate PDF URL. No human intervention is necessary.

SPIN Y



Process Change?

3 Publish

6

CURRENT STATE/ FUTURE STATE (SPIN)3A Load items to

content system (items, bases and collections)

ARS sends exports to TCN daily. ARS, TCN No longer applies. Items are created in the system as soon as they are imported from IMA

IMA, SPIN Y

3B Send items to WCS

TCN, WCS Processing time will be reduced dramatically by utilizing Seller Portal-WCS Web service approach.

SPIN, WCS Y

4 Maintain Add/remove skus

as part of a base ARS Instead of relying on ARS, internal

content specialists or the vendors themselves will be able to perform this task

Internal Content Specialist, Vendor, FLS buyer (FLS org), Online Merchant (OBU org)

update image ARS, Content Team

Instead of relying on ARS, internal content specialists or the vendors themselves will be able to perform this task




Process Change?

7

CURRENT STATE/ FUTURE STATE (SPIN) re-categorize ARS, Content

TeamInstead of relying on ARS, internal content specialists will be able to change the Item Class that the item is associated to. Web hierarchy associations to Item Classes will be managed by the Taxonomists.

Internal Content Specialist, Vendor, FLS buyer (FLS org), Online Merchant (OBU org). Web hierarchy changes for an item class will be done by the taxonomists.

update copy (title, descriptions etc.)

ARS, Content Team



Item inactivation ARS, Content Team



Add/remove catalog associations

ARS, Content Team

Instead of relying on ARS, internal content specialists will be able to perform this task


Marketing, Ads/promos

ARS, Content Team

Not handled by the current content management system; not in scope for SPIN

FLS buyer (FLS org), Online Merchant (OBU org)



Process Change?

Dimension updates

IMA Unchanged IMA

8

CURRENT STATE/ FUTURE STATE (SPIN) Add brand ARS Update Brand

display name ARS

Create dummy brand logo

ARS

update brand logo

ARS

modify pid/websku

associate services to items

Can Carry Change - Kmart Only

Currently TW items that are chosen to be carried by the online buyer are transmitted via a Webcon report to team to add store 7840 to the can carry. This allows the KIN to get pricing

Merchandise Support

Can Carry codes will still need to be changed. A report needs to be send to Merchandise Support from SPIN

Spin, Merchandise Support

VENDOR DIRECT FLOW

Item Lifecycle Task Current State

Performed by Future State Performed By

9


Phase1 Initiation

On-board vendorSet up vendor in legacy vendor master systems

Vendor Onboarding Team Unchanged

Vendor Onboarding Team

Send spreadsheet of new vendor data to Content Team


Insert link to SPIN in Good News Letter that goes out to new vendors.


Load spreadsheet into TCNContent Team No longer applies. N/A

Vendor logs in to SPIN initially with Pay and Order DUNS numbers. SPIN authenticates credentials using data from IMA, then allows the vendor to set up profile with appropriate user ID and password. Vendor

Train vendor on content management system

Content Team

No longer applies. System will provide hints to guide the user through every task. N/A

2 Content Creation

2A Option 1: Vendor bulk-loads items into SHC Content application

Send product class information to vendor

Content Team

No longer applies.

Item Lifecycle Phase Task Current State


10


Send item bulk load template to vendor

Content Team

Vendor downloads item bulk load templates from SPIN. Templates are item class specific, so the vendor simply fills in each attribute with the appropriate value. Vendor

Fill in standard item fields on spreadsheet Vendor Unchanged Vendor

Add class-specific attributes on spreadsheet Vendor No longer applies. N/A

Fill in class-specific attributes on spreadsheet Vendor Unchanged Vendor

Additional Build Options: Define bases/variations

Vendor

Unchanged

Vendor

Additional Build Options: Define collections - identify/select collection items, provide collection title

Not available via TCN n/a Available in SPIN y


Not available via TCN n/a Available in SPIN Y



Additional Build Options: Define collections - flag collection for bundle

Not available via TCN n/a Available in SPIN

11


pricing Additional Build

Options: Specify coordinating items




Upload spreadsheet into TCN Vendor Unchanged Vendor

Send items to IMA (via batch process) TCN Unchanged SPIN

Load items into IMA; result status returned to TCN

Automated batch process? Unchanged N/A

Update status of successful IMA loaded items; send report of rejected?

Automated batch process? N/A

2B Option 2: Vendor works with ARS

Send product class information to vendor

OBU merchant? No longer applies. N/A

Send item AI load template to vendor ARS

Vendor downloads item bulk load templates from SPIN. Templates are item class specific, so the vendor simply fills in each attribute with the appropriate value. Vendor



Fill in auto-intake sheet Vendor No longer applies. N/A

Additional Build Options: Define collections - identify/select

OBU merchant?

Available in SPIN y

12


collection items, provide collection title

Send auto-intake sheet to ARS Vendor No longer applies. N/A

Load auto-intake sheet in system ARS No longer applies. N/A

Additional Build Options: Create collections

ARS

Available in SPIN

Vendor

y

Additional Build Options: Create collections - flag collection for bundle pricing

ARS (at instruction of OBU merchant?)

Available in SPIN

Vendor


?

Available in SPIN

Vendor


?

Available in SPIN

Vendor

Prepare IMA DSD sheet ARS No longer applies. N/A

Send DSD sheet to SHC (IMA) ARS No longer applies. N/A

Load DSD sheet in IMA

Merchant Support Analyst No longer applies. N/A



Option 3: Vendor creates items 1x1 (via UI) into SHC Content application

Fill in standard and class-specific attributes via UI

Fill in standard and class-specific attributes via UI Vendor Unchanged SPIN

Additional Build Options: Define collections - identify/select collection items,


13


provide collection title



Additional Build Options: Define collections - flag collection for bundle pricing






Send items to IMA Send items to IMA TCN Unchanged SPIN



Automated batch process? Unchanged N/A





Automated batch process? N/A

Add'l tasks Applicable to all build options

RIM Record Creation - Sears VD - new

RIM Record create new Sears VD items that are uploaded via the TCNIMA id

Merchandise Support

RIM Record create new Sears VD items that are uploaded via the SPIN user id

Merchandise Support

Change RIM Record Creation to new vendor - Vendor

Make sure that RIM is pointing to the new vendor for the newly created IMA vendor Pack

Merchandise Support

Make sure that RIM is pointing to the new vendor for the newly created IMA vendor Pack. In

SPIN, Merchandise Support

14


Pack addedorder to do this, we will need a SPIN report of data added.

Information updates to Vendor Pack data, that was not accepted

Sell, attribute, RSOS code, etc. data update where vendor pack data was added. (IMA does not accept this data, keeps data it already has on the item).

Merchandise Support

Sell, attribute, RSOS code, etc. data update where vendor pack data was added. (IMA does not accept this data, keeps data it already has on the item). In order to do this, we will need a SPIN report of data added.

SPIN, Merchandise Support

Work items that have IMA errors

Items that are missing data or have incorrect data that get stuck in the IMA workflow process

Merchandise Support Unchanged

Merchandise Support

3 Publish

Load items to content system (Option 2 only) ARS sends exports to TCN daily. ARS, TCN

No longer applies. Items are created in the system as soon as they are imported from IMA IMA, SPIN

Send items to WCS TCN, WCS

Processing time will be reduced dramatically by utilizing Seller Portal-WCS Web service approach. SPIN, WCS



4 Maintain

Add/remove skus ARS


Internal Content Specialist, Vendor

update image ARS, Content Team



re-categorize ARS, Content Team


Internal Content Specialist

update copy (title, descriptions etc.)

ARS, Content Team



15


Item inactivation ARS, Content Team



Add/remove catalog associations

ARS, Content Team



Marketing, Ads/promos

ARS, Content Team

Not handled by the current content management system; not in scope for SPIN


Dimension updates IMA Unchanged IMA

16

CURRENT STATE/ FUTURE STATE (SPIN) - Bonnie...

Documents

Transcript of CURRENT STATE/ FUTURE STATE (SPIN) - Bonnie...