BRS_Samsung_RLI v1.02.docx

**Business Requirements Specification** **System Migration Document** (BRS-SMD) **SAMSUNG RLI** BRS -- SMD ---------------------------------------- -- Project Sponsor: Operations Manager: Zubin Patel Commercial Manager: K...

**Business Requirements Specification** **System Migration Document** (BRS-SMD) **SAMSUNG RLI** BRS -- SMD ---------------------------------------- -- Project Sponsor: Operations Manager: Zubin Patel Commercial Manager: Kay Kim Solution Design Manager: Roel Prondoso Implementation Manager: Document Version/Date: **Change Control** **Version\#** **Content** **Change** **Issued Date** --------------- -------------------------- ------------ ----------------- V1.0 Functional As-Is Process 03-05-2024 **Related Documents** **Name** **Date** ---------- ---------- **Table of Contents** Purpose of the Document 4 System Migration Document 4 1 Introduction 4 1.1 Project Summary 4 1.1.1 Background 4 1.1.2 Scope of Service 4 2 Commercial 4 2.1.1 Budget / Investment Application 4 2.1.2 Commercial Management 5 3 System Migration Strategy 5 4 Facility 5 4.1 Technical Requirements 5 4.1.1 Fittings and Supplies 5 4.1.2 Layout 5 4.1.3 Material Flow 5 5 Operation Processes 5 5.1 Process Flows 5 5.2 TO-BE SOP/WI 6 5.3 Volume Information 6 6 Information Technology (IT) 6 6.1 Warehouse Management System (WMS) 6 6.2 IT Infrastructure 6 6.3 IT Security 6 6.4 Additional Application Requirements 6 6.5 System Training 6 7 Implementation 7 7.1 Implementation Org Chart 7 7.2 Milestones & Timeline 7 Approval 8 Purpose of the Document {#purpose-of-the-document.ListParagraph} ======================= The purpose of the document is to formally capture detailed business requirements specification -- system migration document (BRS-SMD) for WMS migration in accordance with System Migration Framework. The Implementation Manager collaborates with the key stakeholders through requirements gathering workshops to create the BRS-SMD. Once the document has been completed, it is then approved by the parties as noted in the approval section. This document is required to formally progress from Detailed Planning to Execution. All requirements as documented within the BRS-SMD remain as the basis for the system migration. Where a subject is not relevant to the project, the header must remain, and the narrative explicitly state the subject is considered out of scope. This document is applicable to system migration to Schenker WMS system. System Migration Document {#system-migration-document.ListParagraph} ========================= Introduction ============ Project Summary --------------- \*A brief summary of the customer, the proposed solution, expected timeline for project including anticipated Go Live date. ### Background \*Provide a brief history on the bid & selection process, and the clients motivation in tendering. ### Scope of Service \*Describe what requirements are in scope for the project, **and specifically what is out of scope**, beyond the current budget, resources and timeline as approved by the project stakeholders. This is designed to prevent "scope creep" of additional features and functions not originally anticipated and provide a basis for Change Management during Implementation. Commercial ========== ### Budget / Investment Application \*Details of the Investment Application or budget as submitted for infrastructure and implementation cost ### Commercial Management \*Document how the system migration will be costed if there is any alignment process for re-costing activity due to system migration? - Any changes to pricing for customer that are migrating? System Migration Strategy ========================= \*Document all assumptions to include the following: - Communication with customer on the migration period and potential impact to customer during migration period including aligning major milestones with customer (e.g: SIT, UAT) - Data migration plan: The approach for migration existing data to the new system, ensuring data integrity and minimal downtime including data preparation, cleansing, mapping and verification process. - Cut over plan including data validation for accuracy and integrity post migration and performance monitoring - Any dependencies? Integration dependencies to external applications (e.g: customer's system, ERP upgrade, avoid peak season, performance threshold) Facility ======== Technical Requirements ---------------------- ### Fittings and Supplies *\*Detail any additional fit-out requirements required due to the system migration, (e.g automation required, etc. )* ### Layout *\*Insert layout drawing only if there are any changes in the layout due to the system migration.* ### Material Flow *\*Insert material flow drawing only if there are any changes in the material flow due to the system migration.* Operation Processes =================== Process Flows ------------- *[EDI process Workflow:]* MSG TYPE MSG\_TYP\_ID PARTNER SYSTEM OPERATIONS DESCR Status Last Trigger Date ---------- -------------- ---------------- ------------- --------------------------------------------- ---------------- ------------------- Inbound ACKANS SEAU - NERP RLI Common EDI Active 22/05/2024 15:53 Inbound GENRES SEAU - NERP RLI Common EDI Active 17/05/2024 21:01 Inbound MODINF SEAU - NERP RLI SKU Master Active 21/05/2024 19:47 Inbound OUTDLY SEAU - NERP RLI Outbound Orders & Returns (Inbound ASN) Active 22/05/2024 16:06 Inbound SHPNOT SEAU - NERP RLI Advance Shipping Notification (ASN) Active 22/05/2024 13:48 Inbound STKORD SEAU - NERP RLI Stock Change Order Active 22/05/2024 14:54 Inbound SHPMNT SEAU - NERP RLI DR consolidation from SEAU No Longer Used 27/11/2023 14:59 Outbound GENRES SEAU - NERP RLI Common EDI Active 22/05/2024 14:42 Outbound GIINFO SEAU - NERP RLI Goods Issue Active 20/05/2024 9:36 Outbound GRINFO SEAU - NERP RLI Goods Receipt Active 22/05/2024 15:50 Outbound PODDLY SEAU - NERP RLI Information On Delivery (COD) Active 21/05/2024 15:24 Outbound SHPINF SEAU - NERP RLI Tracking Info and also used for RRDD update Active 21/05/2024 15:25 Outbound STKRST SEAU - NERP RLI STRORD Result Active 22/05/2024 15:05 Outbound FREINV SEAU - NERP RLI Freight Invoice used in FG No Longer Used 10/08/2023 16:49 Outbound SHPRST SEAU - NERP RLI Result for DR Consolidation No Longer Used 12/10/2023 11:12 Inbound ACKANS SDS - CELLO Spare Parts Common EDI Active 22/05/2024 16:04 Inbound GENRES SDS - CELLO Spare Parts Common EDI Active 22/05/2024 15:54 Inbound GIINFO SDS - CELLO Spare Parts Goods Issue from Cello Active 22/05/2024 16:10 Inbound MODINF SDS - CELLO Spare Parts SKU Master Active 22/05/2024 15:11 Inbound OUTDLY SDS - CELLO Spare Parts Outbound Orders & Returns (Inbound ASN) Active 22/05/2024 16:02 Outbound GENRES SDS - CELLO Spare Parts Common EDI Active 17/05/2024 12:06 Outbound ACKANS SDS - CELLO Spare Parts Common EDI Active Outbound MNFDLY SDS - CELLO Spare Parts Manifest Information Active 22/05/2024 15:45 Outbound PODDLY SDS - CELLO Spare Parts Information On Delivery (COD) Active 22/05/2024 15:52 Outbound TRKINF SDS - CELLO Spare Parts Outbound Tracking No Longer Used 22/05/2024 15:55 *[Inbound Process Flow:]* *[Outbound Process Flow:]* **[Inbound:]** 1. Volume (Monthly/Weekly Average) ** ** **RA** **STO** ------------- --------- ----------- --------- ----------- ** ** **Qty** **Count** **Qty** **Count** **Daily** 150 138 40 3 **Weekly** 750 688 200 15 **Monthly** 3,000 2,750 800 60 2. ASN Types: a. Stock Transfer -- SHPNOT (ASN) b. Returns -- OUTDLY ORD\_CD = R10 (Converted to ASN) c. RLO -- Manual ASN 3. EDI Validation for multi-line RA. d. System checks against a list of ShipTo codes to reject having multiple lines of items in the same RA. e. This list is found in the lookup table as shown in example below. f.  4. []{#Inbound_Receiving.anchor}Inbound Receiving -- This is the physical receipt of freight being scan off board to capture its arrival. g. Barcodes may or may not be available to scan. h. Use Scan Off Board RF function to scan RA number or serial number to be checked against the RA ASN data. i. Scan Off Board RF function ii. i. Creates RLI Inspection task List. This is used as actual task list of pending inspection. iii.  j. Arrival List Report by Date. Report that is accessible in WMS to generate a list of arrivals (based on scan off) by Date. iv. 5. []{#GR_By_Inspection.anchor}Inspection Process -- GR process using RF to capture Inspection results and functions code. Note: There is a separate inspection process by scanning the serial number first instead of RA number. It can be combined in one RF functionality if possible. k. Scan RA number v.  vi. If scanning serial number and serial has a matching RA number, complete inspection the same manner as scanning RA number first. vii. If scanning serial does not result to a matching RA number, proceed as RLO receiving. l. []{#C_Grade_Exclusion.anchor}Quarantine stock validation -- C Grade Exclusion List viii. SKU - based on a database updated from time-to-time by Samsung via email to a technical email address which unpacks the updated list and update the database. Matching quarantine reason to be shown on label. 1. HHP 2. QUARANTINE 3. HN NON SELLABLE 4. NON-SELLABLE 5. Re-call WM 6. PANDA 7. Sample Label: 8. Sample Email  ix. []{#Over_3Years.anchor}Serial Number -- based on a logic provided by Samsung to calculate if product is Over 3 years. If over 3 years, it also must be visible on the label. 9. 10. Sample label  m. []{#Inspection_Grade.anchor}Inspection Grade Calculation -- Based on the inspection result, the system will calculate the appropriate grade C for CSales or D for Scrapping. x. Default grade is A from the EDI data. xi. Sample Grading Matrix n. Sample Inspection Codes  o. If all information captured is valid and correct. System will perform: xii. Print Label 11. Sample Label xiii. Close ASN xiv. Generate GRINFO and trigger to Samsung if GRHOLD is disabled. Inventory is placed on a staging location prior to putaway. If GRHOLD is enabled, inventory is stored in a dummy Storer (RLIGRHOLD) pending release to the actual destination Storer. p. []{#WrongStock.anchor}Other Validation checks for RA only (STO excluded) xv. WRONGSTOCK Category (Reasons) -- Inventory goes to WRONGSTOCK Dummy Storer. Wrongstock reason can only be applied to the first Wrongstock case. Skip other validation and go straight to capture Pallet ID then close the inspection process. No EDI (GRINFO is generated) and ASN status remains open. 12. RA Closed -- when checking RA number against system status 13. RA Cancelled - when checking RA number against system status 14. SKU Mismatch -- When SKU is different from system record for the RA 15. Serial Mismatch -- when serial number is different from system record for the RA. a. Allow ability to generate dummy serial if requested by Samsung or for non-serialised products. 16. No Unit Or Non Samsung -- if "NO UNIT" or "NON SAMSUNG" is entered in the 2^nd^ SKU field. 17. Sample Label:  xvi. NDF (No defect Found) category - If function code entered is TNDF. Inventory goes to dummy Storer RLINDF. 18. Sample Label q. Inspection Result 6. []{#WMS_Receipt.anchor}WMS Receipt -- Goods receipt is completed using the WMS front end. No serial number and inspection results captured. r. s. []{#GRHOLD.anchor}Generate GRINFO and trigger to Samsung if GRHOLD is disabled. Inventory is placed on a staging location prior to putaway. If GRHOLD is enabled, inventory is stored in a dummy Storer (RLIGRHOLD) pending release to the actual destination Storer. GRHOLD only applies for Returns not Stock transfers. t. []{#Inspection_Upload.anchor}Allow system capability to update serial number and inspection results after GR using upload file. xvii. Bulk upload  xviii. Single Update 7. []{#GR_Release.anchor}GR Release for pending GRHOLD items. This is currently done using WMS screen to upload release file. u. GR Release page v. Update ASN status to close. w. Trigger GRINFO to Samsung x. Transfer inventory from the dummy RLIGRHOLD Storer to the destination (original) Storer from ASN. y. Allow system functionality to enable or disable GRHOLD. xix. GRHOLD Setting 8. []{#RLO_Receiving.anchor}RLO Receiving (No RA created) - Bulk Return items without Samsung RA reference number. z. []{#RLO_Manual_ASN.anchor}Manual ASN is sent by Samsung via email to a technical address and create manual ASN for each item. The inventory from this receipt type goes to dummy Storer RLIGRRLO. No GRINFO is generated until Samsung will provide a list of RA matching the SLP to release and GR. a. Sample email  b. Sample BL Summary Report for the RLO Manual ASN c. External Reference Number called SLP is used instead of RA number. d. []{#RLO_Inspection.anchor}Inspection is performed in a similar manner to the normal RF inspection process in Inbound item 4. xx. Sample RF Screen  xxi. WRONGSTOCK Category -- Inventory goes to WRONGSTOCK Dummy Storer. Wrongstock reason can only be applied to the first Wrongstock case. Skip other validation and go straight to capture Pallet ID then close the inspection process. No EDI (GRINFO is generated) and ASN status remains open. 19. SKU Mismatch -- When SKU is different from system record for the RA 20. Serial Mismatch -- when serial number is different from system record for the RA. b. Allow ability to generate dummy serial if requested by Samsung or for non-serialised products. 21. No Unit Or Non Samsung -- if "NO UNIT" or "NON SAMSUNG" is entered in the 2^nd^ SKU field. e. []{#RLO_Release.anchor}RLO Release page xxii. xxiii. Release GR for RA that matched the SLP. xxiv. Update RA ASN status to close. xxv. Trigger GRINFO to Samsung xxvi. Transfer inventory from the dummy RLIGRRLO Storer to the destination (original) Storer from ASN. 9. []{#ASN_Cancellation_WMS.anchor}ASN Cancellation can be done in two different ways: f. Cancellation using WMS  g. []{#ASN_Cancellation_SEAU.anchor}Cancellation message from Samsung (most common method) xxvii. WMS checks if status has changed before ASN (SHPNOT or OUTDLY) cancellation can be done automatically. **[Putaway:]** 1. No system putaway logic 2. []{#Putaway_Single.anchor}Putaway can be perform in both RF scanner and WMS screen. a. RF putaway i. Single Item putaway ii. Bulk putaway by PalletID iii. Sample RF b. []{#Putaway_Bulk.anchor}WMS Screen for putaway/move function. iv.  **[Inventory & Facility: ]** 1. []{#SKU_Master.anchor}Master SKU data is sent from Samsung using MODINF EDI message. a. All new SKU is blocked for GR until operations updates some required information. b. 2. []{#Block_QI.anchor}Ability to put a Block or QI (Quality Inspection) for selected inventory items. c. Samsung can also send a file to use as a reference to mimic Block/QI Status on the daily snapshot report. d. Sample file email and file 3. []{#Daily_INV_Snapshot.anchor}Daily inventory snapshot (INVSTK) -- To be triggered daily for stock status comparison to Samsung. e. Inventory located in Dummy Storers to be excluded in the inventory snapshot. f. []{#Daily_INV_Snapshot_VGI.anchor}Inventory allocated for orders that have been virtually Goods issue to be excluded in the inventory snapshot. 4. []{#SCO.anchor}Stock Change Order (SCO) -- This is an inventory system request from Samsung to change existing attribute/s of an inventory item using STKORD EDI message from Samsung. g. Three attributes that can be modified -- Storer, SKU and Grade. h. On completion of the task, we send back STKRST message to confirm. i. SCO can be processed in two different ways. i. Manual -- Samsung will advise of the SCO number then ops team will process. ii. []{#SCO_Automated.anchor}Automated -- WMS will process automatically for those SCOs created by Samsung RPA process. j. Sample SCO page 5. []{#Inventory_Movement.anchor}Inventory movement k. Single Item or bulk movement l. Using RF or WMS page 6. []{#Inventory_Adjustments.anchor}Inventory Adjustments m. Single item or bulk adjustments n. WMS page only 7. []{#Cycle_Count.anchor}Cycle Count and Stocktake o. Stocktake frequency -- Bi-Annual (Mid-Year & EOY) p. Cycle Count frequency -- on demand q. Currently conducted manually with system support using RF scanner and WMS online reporting. Counting is done by scanning the item including serial number. iii. iv.  8. []{#Location_Setup.anchor}Location Setup r. Barcoded locations using 10 chars only in the naming convention. s. Not all Locations are pick locations. t. Locations can be blocked to flag all items in the location as QI or Block u. No replenishment strategy 9. []{#Storer_Setup.anchor}Storer Setup -- These Storers must be setup up under one facility (SYD09) v. Type of Storers v. Samsung NERP Storers (8) -- these storers must matched Samsung inventory and included in the daily inventory comparison. 1. vi. Dummy Storers (4) -- used to maintain inventory integrity for all handled items that do not comply Samsung requirements or GRINFO not expected. 2.  **[Outbound:]** 1. []{#Outbound_orders.anchor}Outbound Orders are created by Samsung and sent to WMS on OUTDLY EDI message ORD\_CD = O10/O11/O12 2. Carrier is assigned once Order is received in WMS. 3. Order Type -- Is based on DO Type matrix which comes from OUTDLY. a. 4. Order Cancellation b. []{#Order_Cancellation_WMS.anchor}WMS cancellation -- requires reason for cancellation. c. []{#Order_Cancellation_SEAU.anchor}Cancellation message from Samsung (most common method) i. WMS checks if status has changed before OUTDLY cancellation can be done automatically. 5. FIFO -- not required. 6. []{#Allocation.anchor}Allocation logic -- Allocate any available stock that matches the order request based on: d. Storer e. SKU f. Grade 7. Picking Document -- Picking list is used to perform picking using RF scanner. g. Picking Slip h. RF Picking Option - 8. []{#Picking_Logic.anchor}Picking Logic -- Pick the exact item based on the attributes of the allocated item for serialised products located in the same location and of the same SKU. i. Pick by Label j. Serial number of the picked item must match the serial attribute of the allocated item. k. If serial of the picked item does not match, perform internal data switch to maintain correct system record and the physical item. l. Does not apply for non-serialised products. m. Bulk Picking not required. 9. []{#VGI.anchor}Virtual Goods Issue (VGI) -- Allow ability to trigger GIINFO (Goods Issue) any time after allocation process. n.  o. This functionality allows GIINFO sent to Samsung, but the actual picking and shipping can happen later. p. Inventory that belongs to the virtually GI'ed orders must be excluded in the daily inventory snapshot. 10. []{#RDD.anchor}Requested Delivery Date or Revised RDD -- This is a system ability to update the requested delivery date if different from original date stated from the order information. This will be triggered using the SHPINF EDI message to Samsung. q. 11. Electronic COD (IOD) -- Once delivery is confirmed, PODDLY EDI message is sent to Samsung. This is currently achieved by: r. []{#IOD_TMS.anchor}Receiving data from TMS and automatically trigger PODDLY to Samsung. s. []{#IOD_WMS.anchor}Uploading IOD information in WMS to trigger PODDLY. ii.  **[Reporting: ]** 1. Mail Robots (Automated Reports) a. SEAU RLI Inspection b. SEAU RLI Wrongstock Inspection c. SCO Not Processed d. RLO Inspection Report e. Daily Phantom GR Report f. Released GR Hold Report g. RA Arrival List h. Samsung - DO Without POD Report i. Samsung - Closed RA Report j. SEAU OPEN Orders Report k. Samsung Daily Inventory Snapshot 2. Other Reports (Macros) -- to be provided. **[Others:]** 1. Ability to cancel or re-trigger EDI messages if it fails or as requested by Samsung. **[Functional Gap Analysis:]** +-----------------------------------+-----------------------------------+ | FUNCTIONAL GAP ANALYSIS | | +===================================+===================================+ | Legacy Exceed WMS | NGW | +-----------------------------------+-----------------------------------+ | 1. [Inbound | Testing of the recommended | | Receiving](#Inbound_Receiving | solution from NGW SPOC is in | | ) - | progress. | | This is the physical receipt | | | of freight being scan off | Explore Inbound QC functionality. | | board to capture its arrival. | | | (Refer to item 4 of the | | | Inbound workflow) | | +-----------------------------------+-----------------------------------+ | 2. [Goods Receipt by Inspection | Testing of | | Process](#GR_By_Inspection) | the recommended solution from NGW | | [-] GR process | SPOC is in progress. | | using RF to capture | | | Inspection results, function | Explore Inbound QC functionality. | | code and calculate the | | | inspection grade. (Refer to | | | item 5 of the Inbound | | | workflow). Validations | | | required: | | +-----------------------------------+-----------------------------------+ | a. [C Grade Exclusion | Testing of the recommended | | Check](#C_Grade_Exclusion). | solution from NGW SPOC is in | | (Refer to item 5b of the | progress. | | Inbound workflow). | | | | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | b. [Product Aging | Testing of | | identification](#Over_3Years) | the recommended solution from NGW | | - | SPOC is in progress. | | Over 3 Years. (Refer to item | | | 5b\_ii of the Inbound | Explore Inbound QC functionality. | | workflow). | | +-----------------------------------+-----------------------------------+ | c. [Inspection Grade | Testing of the recommended | | Calculation](#Inspection_Grad | solution from NGW SPOC is in | | e). | progress. | | (Refer to item 5c of the | | | Inbound workflow). | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | d. [Wrongstock | Testing of | | Validation](#WrongStock). | the recommended solution from NGW | | (Refer to item 5f of the | SPOC is in progress. | | Inbound workflow). | | | | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | 3. [Goods Receipt using WMS | Possible in NGW | | front end](#WMS_Receipt) | | | [-] Goods receipt | | | is completed using the WMS | | | front end. No serial number | | | and inspection results | | | captured. (Refer to item 6 of | | | the Inbound workflow). | | +-----------------------------------+-----------------------------------+ | a. [Single and Bulk Update | Testing of | | (Upload)](#Inspection_Upload) | the recommended solution from NGW | | - | SPOC is in progress. | | Allow system capability to | | | update serial number and | Explore Inbound QC functionality. | | inspection results after GR | | | using upload file. (Refer to | | | item 6c of the Inbound | | | workflow). | | +-----------------------------------+-----------------------------------+ | b. [GRHOLD](#GRHOLD) | Testing of the recommended | | Functionality - Applies to | solution from NGW SPOC is in | | both Goods Receipt processes. | progress. | | (Refer to item 6b of the | | | Inbound workflow). | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | c. [GRHOLD Release](#GR_Release) | Testing of | | -- Releasing of ASN that has | the recommended solution from NGW | | been put on GRHOLD status. | SPOC is in progress. | | (Refer to item 7 of the | | | Inbound workflow). | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | 4. [RLO | Testing of the recommended | | Receiving](#RLO_Receiving) | solution from NGW SPOC is in | | [-] Bulk Return | progress. | | items without Samsung RA | | | reference number. (Refer to | Explore Inbound QC functionality. | | item 8 of the Inbound | | | workflow). | | +-----------------------------------+-----------------------------------+ | a. [Manual ASN | Bulk ASN | | Creation](#RLO_Manual_ASN) | creation or upload possible in | | (Non-EDI). (Refer to item 8a | NGW but not via email | | of the Inbound workflow). | | +-----------------------------------+-----------------------------------+ | b. [RLO | Testing of the recommended | | Inspection](#RLO_Inspection) | solution from NGW SPOC is in | | -- This is similar process to | progress. | | the RA inspection process | | | | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | c. [RLO Release](#RLO_Release) | Testing of | | -- Automatically process | the recommended solution from NGW | | goods receipt for open RAs | SPOC is in progress. | | matching RLO item | | | | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | 5. [ASN | Possible in NGW | | Cancellation](#ASN_Cancellati | | | on_WMS) | | | | | | d. Cancellation using WMS | | +-----------------------------------+-----------------------------------+ | e. [Cancellation message from | Testing of | | Samsung (most common | the recommended solution from NGW | | method)](#ASN_Cancellation_SE | SPOC is in progress. | | AU) | | | | Explore Inbound QC functionality. | +-----------------------------------+-----------------------------------+ | 6. [Putaway](#Putaway_Single) | Possible in NGW | | | | | f. RF single item & bulk | | | (location) putaway. | | | (Refer to item 2a in | | | Putaway workflow). | | +-----------------------------------+-----------------------------------+ | g. [Bulk putaway/move/transfer | Assessment | | using front | from NGW SPOC required | | end](#Putaway_Bulk) | | +-----------------------------------+-----------------------------------+ | 12. [Outbound] -- | Possible in NGW | | [Outbound | | | Orders](#Outbound_orders) are | | | created by Samsung and | | | received into WMS via OUTDLY | | | EDI message. | | +-----------------------------------+-----------------------------------+ | t. [Waving & | Possible in | | Allocation](#Allocation) | NGW | +-----------------------------------+-----------------------------------+ | u. [Picking | Assessment from NGW SPOC required | | Logic](#Picking_Logic) -- | | | Pick the exact item based on | | | the attributes of the | | | allocated item for serialised | | | products located in the same | | | location and of the same SKU. | | | (Refer to item 8 in outbound | | | workflow). | | +-----------------------------------+-----------------------------------+ | v. [Virtual Goods Issue](#VGI) | Assessment | | (VGI) -- Allow ability to | from NGW SPOC required | | trigger GIINFO (Goods Issue) | | | any time after allocation | | | process. (Refer to item 9 in | | | outbound workflow). | | +-----------------------------------+-----------------------------------+ | w. [Revised RDD Update](#RDD) -- | Assessment from NGW SPOC required | | This is a system ability to | | | update the requested delivery | | | date if different from | | | original date stated from the | | | order information. This will | | | be triggered using the SHPINF | | | EDI message to Samsung. | | | (Refer to item 10 in outbound | | | workflow). | | +-----------------------------------+-----------------------------------+ | x. [Electronic COD | Possible in | | (IOD)](#IOD_TMS) -- Delivery | NGW | | confirmation EDI triggering | | | | | | iii. Receiving data from TMS | | | and automatically trigger | | | PODDLY to Samsung. (Refer | | | to item 11a in outbound | | | workflow). | | +-----------------------------------+-----------------------------------+ | iv. [Bulk IOD upload](#IOD_WMS) | Assessment from NGW SPOC required | | in WMS. (Refer to item 11b in | | | outbound workflow). | | +-----------------------------------+-----------------------------------+ | y. Order Cancellation -- | Possible in | | | NGW -- check if reason can be | | v. [Cancel in | captured | | WMS](#Order_Cancellation_ | | | WMS) | | +-----------------------------------+-----------------------------------+ | vi. [Cancel from Samsung via | Assessment from NGW SPOC required | | EDI](#Order_Cancellation_SEAU | | | ) | | +-----------------------------------+-----------------------------------+ | 13. [Inventory & Facility | Possible in | | --] [Master SKU | NGW | | data](#SKU_Master) is sent | | | from Samsung using MODINF EDI | | | message. (Refer to item 1a in | | | inventory and facility | | | workflow). | | +-----------------------------------+-----------------------------------+ | z. [Ability to flag block or QI | Assessment from NGW SPOC required | | status](#Block_QI). (Refer to | | | item 2 in inventory and | | | facility workflow). | | +-----------------------------------+-----------------------------------+ | a. [Daily Inventory | Possible in | | Snapshot](#Daily_INV_Snapshot | NGW | | ) | | | | | | vii. Exclude items in dummy | | | Storers. (Refer to item | | | 3a in inventory and | | | facility workflow). | | +-----------------------------------+-----------------------------------+ | viii. [Exclude VGI | Assessment from NGW SPOC | | items.](#Daily_INV_Snapshot_V | required. Might require IT | | GI) | changes | | (Refer to item 3b in | | | inventory and facility | | | workflow). | | +-----------------------------------+-----------------------------------+ | b. [Stock Change Order](#SCO) -- | Possible in | | This is an inventory system | NGW for single operator assisted | | request from Samsung to | process | | change existing attribute/s | | | of an inventory item using | | | STKORD EDI message from | | | Samsung. (Refer to item 4 in | | | inventory and facility | | | workflow). | | +-----------------------------------+-----------------------------------+ | ix. [Automated | Assessment from NGW SPOC required | | SCO](#SCO_Automated) | | | Processing -- WMS will | | | process automatically for | | | SCOs created by Samsung RPA | | | process. | | +-----------------------------------+-----------------------------------+ | c. [Inventory | Possible in | | Movement](#Inventory_Movement | NGW | | ) | | | -- Single item move. (Refer | | | to item 5 in inventory and | | | facility workflow) | | +-----------------------------------+-----------------------------------+ | x. [Bulk movement, transfer, and | Assessment from NGW SPOC required | | putaway using WMS front | | | end](#Putaway_Bulk) | | +-----------------------------------+-----------------------------------+ | d. [Inventory | Possible in | | Adjustments](#Inventory_Adjus | NGW | | tments) | | | -- Single item or bulk | | | adjustments. (Refer to item 6 | | | in inventory and facility | | | workflow). | | +-----------------------------------+-----------------------------------+ | e. [Cycle Count and | Assessment from NGW SPOC required | | Stocktake](#Cycle_Count) - | | | Counting is done by scanning | | | the item including serial | | | number. (Refer to item 7 in | | | inventory and facility | | | workflow). | | +-----------------------------------+-----------------------------------+ | f. [Location | Possible in | | Setup](#Location_Setup). | NGW | | (Refer to item 8 in inventory | | | and facility workflow). | | +-----------------------------------+-----------------------------------+ | g. [Storer | Assessment from NGW SPOC required | | Setup](#Storer_Setup). (Refer | | | to item 9 in inventory and | | | facility workflow). | | +-----------------------------------+-----------------------------------+ TO-BE SOP/WI ------------ Volume Information ------------------ \*Document any known / expected seasonality - *Average and max number of inbound lines* - *Average and max number of outbound lines* Information Technology (IT) =========================== Warehouse Management System (WMS) --------------------------------- *\*Refer to IT SRS document provided by local IT which needs to document details of the following:* - *Functions in WMS* - *WMS configuration and strategy setup and logic* - *User access controls* - *Reports and labels* - *Integration with other applications (e.g: TMS, Inviewpro etc...)* - *Carrier Integration (if any)* IT Infrastructure ----------------- *Any additional or change in the current IT infrastructure to support the system migration (jointly decided by local IT and operations) ?* - *Lease line* - *WIFI access point* - *Printers including label printers* - *RF scanners* IT Security ----------- *\*Detail any specific customer or DBS security requirements for IT* Additional Application Requirements ----------------------------------- *\*Any additional IT applications required?* - *Customs module* - *Inviewpro/ Web portal* - *Dashboard requirements* - *CSM (Customer Service Management)* - *TMS/ Labour Mgmt tool* - *Smart Suite* System Training --------------- \*Any required training, including process training, WMS training, and any additional application training Implementation ============== Implementation Org Chart ------------------------ *\*Insert here the org chart for the implementation, and the escalation pathway for risks/issues* - *Sample Org Chart. Mandatory roles: Steering committee, implementation manager, IT Business architect and operations*  Milestones & Timeline --------------------- *\*State high level milestones and overall expected timeline* Approval {#approval.ListParagraph} ======== Approval can be accomplished via physical signature, e-mail response or documented meeting minutes. **Operations Manager** ------------------- ------- ----------- Name: Zubin Patel Date: Signature ------------------- ------- ----------- **Business Architect** --------------------- ------- ----------- Name: Roel Prondoso Date: Signature --------------------- ------- ----------- **IT Manager** ------- ------- ----------- Name: Date: Signature ------- ------- ----------- **Implementation Manager** ------- ------- ----------- Name: Date: Signature ------- ------- -----------