SKU System SOP v15.docx

1、SKU System SOP v15SOPSKU SystemAuthorTerence LuiSystem EngineeringApproverAlex ChoiCEOReviewerChapman ChingSourcingReviewerGarret FungProject ManagementReviewerNamson KwokProduct ManagementReviewerSally NgCustomer ServicesReviewerTeresa WongFirmware EngineeringReviewerJeffrey LinTechnical SupportRev

2、iewerWK TangQuality Assurance1. OBJECTIVESAn SKUsystem is introduced that supports business management to:- Provide convenience for customer to order specific products- Instruct OEM suppliers to manufacture specific products- Connect with ERP to build database for product pricing and costing2. DEFIN

3、ITION OF SKUSKU consists of three parts:- SKU1, 5-character unique identifier to describe New Product at default state (i.e. without customization). It is responsible by Product Marketing- SKU2, 6-character unique identifier to describe tangible visual customization (i.e. silkscreen, packaging desig

4、n, accessories, etc.), in which first 4 characters are treated as customer code and last 2 characters are treated as the revision of customization under same customer code. It is responsible by Customer Services- SKU3, 9-character unique identifier to describe firmware and configuration customizatio

5、n. It is responsible by Technical Support.- The readiness of a full SKU including SKU1, SKU2 and SKU3 is maintained by Project Management.Accompanying with SKU1, SKU2 and SKU3, there are various items in their packages respectively.- SKU1 Packageo It is created and developedunder Product Realization

6、 Process (PRP)o The readiness of the package is verified by Product Marketing before releaseo Inside SKU1 package, the following items are included: Electrical BOM Product Specification Control Plan Quality Specification Production Working Instruction Testing Procedure for PCBA, Semi-Finish Good and

7、 Finished Product Reliability Test Plan PCB Gerber File and PCB Requirement 3D, 2D and Assembly Drawings Firmware Download and RSA tools SMT test tool with bootloader integrated Key Injection Instruction- SKU2 Packageo It is created upon customer requesto It is referred to the default version (i.e.

8、BBPOS) created under PRP o It includes the modifications based on the default version andthe customer requirement on tangible visual changes (e.g. silkscreen, packaging design, accessories etc.)o It is released only with customer approvalo The readiness of the package is verified by Customer Service

9、s before releaseo Inside SKU2 package, the following items are included: Mechanical BOM Color, Material and Finishing (CMF) related Production Files Accessory List Packaging Instruction- SKU3 Packageo It is created upon customer requesto It is referred to the default version (i.e. BBPOS) created und

10、er PRPo It includes the modifications based on the default version and the customer requirement on EMV settings and device settingso It is released only with customer approvalo The readiness of the package is verified by Technical Support before releaseo Inside SKU3 package, the following item is in

11、cluded: Customized Firmware Package with Configuration File3. SKU SYSTEM OVERVIEWThe operation flow of the system is responsible by Product Marketing, and performed as below:i. After PRP, a SKU1 shall be created and its package shall be maintained and controlled under Document Control Centre (DCC)ii

12、. Once SKU1 ready in DCC, it shall be created also in Developer Site System (DSS) and ERP system respectivelyiii. Meanwhile SKU1 package shall be released thru DCC for OEM supplier to download if needediv. In the Developer Site, SKU2 and SKU3 shall be created respectively upon customer request, with

13、 reference to the available SKU1 in the sitev. Once customized SKU2 and SKU3 ready, they will be transferred from Developer Site to DCC& ERP respectivelyvi. Similarly, SKU2 or SKU3 packages shall be released thru DCC to OEM supplier to download respectively if neededvii. In the case of changes requi

14、red for the contents in the released SKU packages, an Engineering Change Notice (ECN) Process may be proceeded, and the packages in the DCC may be updated accordingly with approvalProduct Realization Process (PRP)PRP is the module to generate a new product and so provide SKU1 and its package, as wel

15、l as reference SKU2 & SKU3 for default BBPOS version and their packages, as an input to the system for customized full SKU generation. For the details of the PRP, please refer to its process document separately.Document Control Centre (DCC)DCC is the module to maintain and control the packages of SK

16、U1, SKU2 and SKU3. It separates in two parts for two purposes: i) internal document management system for PRP; ii) external document storage and interface for release of the packages to various systems especially to OEM suppliers. Microsoft Sharepoint (with link here) is facilitated to support the f

17、unctions and operations of this module, with specific permission management for dedicated persons of OEM suppliersto download appropriate SKU packages. For the details of DCC, please refer to its SOP.Developer Site System (DSS)DSS is the module to:- Connect with customers for review on tangible visu

18、al design and firmware design customizations- Allow customers sign-off customized design and provide evidenceAs mentioned above, DSS is served for customizations on SKU2 or SKU3 only. The input of the system are either:- Customer request on tangible visual design information, or- Customer request on

19、 EMV and device settings informationTogether with the inputs, there is an entry criteria that an SKU1 is ready with default SKU2 & SKU3 as a baseline.For SKU2, there are 3 activities to be performed in the DSS:a. Open an Customer Code by CSb. Store customized visual design files by CS c. Allow custo

20、mer sign-off the customized design filesFor SKU3, similarly, there are 4 activities to be performed in the DSS:a. Provide online configuration form to customer for filling in requirementsb. Share configuration form in PDF format to Firmware Engineering, Technical Support, Product Marketing etc. as a

21、 referencec. Store customized firmware binary and its config file, and allow customer to download for evaluationd. Allow customer sign-off the customized firmware package with configuration fileFinally, specific on SKU2 and SKU3, few output shall be released.For SKU2:a. Customized tangible visual de

22、sign package for downloadb. Sign-off evidence for customized visual designFor SKU3:a. Customized firmware package with configuration file for downloadb. Sign-off evidence for customized firmware packageFirmware Engineering is responsible to maintain and control the DSSProduct Marketing is responsibl

23、e to execute the activities to provide input to DSS, and to pass output from DSS to other systems. It is to ensure SKU2, SKU3 and their packages are in sync between DSS, DCC and ERP once createdThere is a remark that, DSS is the interface between customers and BBPOS internal system only, so it shall

24、 not be disclosed to any OEM suppliers for any purposesEnterprise Resource Planning (ERP)ERP is the module to apply SKU1, SKU2 and SKU3 and their information, to support product pricing, costing and ordering for daily operation. The product costing and pricing of the SKU shall be responsible bySourc

25、ing and Customer Services respectively. ERPis interfaced with DCC to ensure the information of SKU are in sync in between, which is responsible by Product Marketing. Microsoft NAV is facilitated to support the functions and operations of this module. For the details of ERP, please refer to its proce

26、ss document.Engineering Change Notice Process (ECN)ECN is the module that can manage the changes related to product after SKU release. It is interfaced with DCC, to update the contents in the SKU packages in there once changes approved. For the details of ECN, please refer to its process document.4.

27、 SKU CREATIONBy considering different natures, SKU1, SKU2 and SKU3 shall be created in different ways.SKU1SKU1 is to describe a product range in the organization, which is created under PRP. Project Management manages the related product development activities and also the deliverables of SKU1 packa

28、ge including:- Product Information by Product Marketing:o Product Specification- Electronic design outputs by Electrical Engineering:o EE BOMo Testing Procedure for PCBA, Semi-Finish Good or Finished Producto PCB Gerber file and PCB requirement- Mechanical design outputs by Mechanical Engineering:o

29、Testing Procedure for Semi or Finished Producto 3D, 2D and Assembly Drawings- Software design outputs by Firmware Engineering:o Key Injection Method and Instructiono Firmware Download tool and RSA toolo SMT test tool with bootloader- Quality design document by Quality Assurance:o Quality Specificati

30、ono Reliability Test Plano Control Plan- Production engineering document by Product Engineering:o Production Working InstructionProject Management is responsible to ensure the readiness and quality of the above deliverables under internal DCC before informing Product Marketing for final review.Produ

31、ct Marketing is responsible to verify the readiness of deliverables in quality; and once accepted, create a new SKU1 in ERP and DSS respectively, and its package underexternal DCC for business operations.Together with the acceptance, achecklistfor SKU1 package shall be signed off by Product Marketin

32、g.Finally, Product Marketing is also responsible to inform Customer Services, Technical Support, Sourcing and Project Management etc. that the SKU1 and its package is ready for business operationsThere is a remark that, specific on the EE BOM and ME BOM, they are in a form of design BOM once ready after PRP.They shall be input into ERP so as to c