JCP BEAT PLAN CONSOLIDATION

Process Overview

Field	Details
Process Name	JCP Beat Plan Consolidation
Segment	Consumer
Process Family	Lenovo India
Process User(s)	Wyzmindz solutions pvt ltd
Process Purpose	This report is instrumental in providing actionable insights, tracking performance, and supporting Lenovo’s sales strategies

Version History

Version Tag	Prepared By	Date of Update/Revision	Validated by	Reviewed by	Approved by	Revision Details
V 1.0	Kiran Biradar	17-12-2025	Dayanand U	Sushruth Vasista	Vishwanath Mosale	SOP Document Creation

Distribution and Access List

Designation	Read	Write	Approval
Analyst	Yes	No	No
Team Lead	Yes	Yes	No
Manager	Yes	Yes	Yes

1.1 Purpose

Each DSM must submit the regional beat plan on a monthly basis. The beat plan outlines the store visit schedule determined by the DSM, based on the dates provided by the ASOs.

1.2 Scope

• Geographic Scope: India.
• Business Segment: Consumer Segment.
• Process Frequency: Weekly basis.
• Core Activity: This SOP applies to downloading, preparing, validating, and publishing Monthly JCP – Update the scope of data not steps of reports

1.3 Business/Segment Overview

This process supports Lenovo India's sales strategies by delivering actionable insights and monitoring performance. The primary objective is to ensure the accuracy of channel sales data (3S) for Consumer products, focusing on Sell-through, Sell-out, and segmentation across Consumer, SMB, and Tablet categories.

1.4 Responsibility and authority

• Analyst : Kiran Biradar
• Process Owner : Jospha Jeevitha J
• Process Manager : Dayanand
• Escalation Manager : Sushruth Vasista
• Approval Authority : Vishwanath Mosale

1.5 Escalation matrix: (Wyzmindz and Lenovo)

Escalation Matrix – WyzMindz Solutions Pvt Ltd India

Sl No.	Name	Designation	Email ID
1	Sushruth Vasista	Manager	sushruth.vasista@wyzmindz.com
2	Vishwanath Mosale	Director	Vishwanath.mosale@wyzmindz.com

Escalation Matrix – Lenovo India Pvt Ltd

Sl No.	Name	Designation	Email ID
1	Bhanuprakash HS	-	bhanuprakash.hs@v5global.co.in
2	Shilpi Gautam	Program Manager	sgautam2@lenovo.com

1.6 RACI Matrix

RACI Matrix – WyzMindz Solutions Pvt Ltd India

Report / Process	Responsible	Accountable	Consultation	Informed
Data download	Kiran	Bhanuprakash	Shilpi	Lenovo Ind Pvt Ltd, Wyzmindz – Lenovo Process Team
Data processing & mapping	Kiran	Bhanuprakash	Shilpi	Lenovo Ind Pvt Ltd, Wyzmindz – Lenovo Process Team
Validation	Kiran	Shilpi	Bhanuprakash	Lenovo Ind Pvt Ltd, Wyzmindz – Lenovo Process Team
Publishing	Kiran	Shilpi	Bhanuprakash	Lenovo Ind Pvt Ltd, Wyzmindz – Lenovo Process Team

1.7 Access Required

Below credential for accessing historical data(Fetching Store id)

• Platform: Bsharp
• URL: https://apps.bsharpcorp.com/users_dashboard
• Access: Email ID and mobile number based password provided by Lenovo / Bsharp

Mail: for receiving beat plan data from DSM’s

1.8 Overview of Tools

• Microsoft Excel is required for data cleaning, dynamic formulas.

1.9 Legends

Field	Meaning
ASO	Area Sales Officer
RCM	Regional Channel Manager
RSM	Regional Sales Manager
DSM	Divisional Sales Manager
User Zone	Zone classification based on region

1.10 Data Dependencies

• DSM’s Beat Plan data received from mail

1.11 Schedule of Reporting

Frequency: Daily

1.12 Process Flow Chart

1.13 Steps of Procedure

Monthly Beat Plan Consolidation & Submission Process

Step 1: Receive Beat Plan from DSMs

• All DSMs must share the monthly Beat Plan Consolidation for their respective regions via email.
• Once received, begin validation and data cleaning activities

Step 2: Data Validation, Cleaning & Completion

• Perform the following checks and corrections for every record:
• Store ID Check
  • If Store ID is blank, map it using historical JCP Beat Plan data or download historical data from the SHARP platform.
• Store Name Check
  • If Store Name is blank, populate it based on the Store ID using historical JCP Beat Plan data or SHARP platform data.
• ASO Details Check
  • If ASO Name is blank, retrieve it using ASO ID from historical JCP Beat Plan or SHARP data.
  • If ASO ID is blank, retrieve it using ASO Name from historical JCP Beat Plan or SHARP data.
• DSM/Region Standardization
  • Rationalize and clean the respective DSM Names and Region Names to ensure consistency with master data.
• City / State / Region Check
  • If City, State, or Region is blank, derive and map them using a combination of ASO ID and Store ID from historical data.

• Mandatory Details Check

  • Ensure that the following fields are available:
    • GSTIN
    • Segmentation (A/B/C/D)
    • TAM/Month If missing, request the details from the respective DSM.

• Plan Value Standardization

  • All plan values should be “1”.
  • If values appear as “Visite”, “visit”, or similar variants, convert them to “1”.
  • If the beat plan value is blank or not applicable, assign “NA”.

Step 3: Regional Consolidation & Submission:

• Consolidate all cleaned beat plans region by region.
• Share the final consolidated file with the BSharp Team for further processing.

Step 4: Request JCP Template

• After consolidation is completed and shared, request the Beat Plan Template required for the JCP report.

1.14 Output Overview

Processed dataset containing:

• Store wise plan
• Below image is raw data before publishing / sharing

1.15 Validation checklist

Beat Plan – Data Validation Checklist

Use the following validation rules when reviewing monthly beat plan submissions from DSMs:

Store Information Validation:

• Store ID:
  • Must not be blank.
  • If blank → map using historical JCP Beat Plan or SHARP platform data.
• Store Name:
  • Must match the Store ID.
  • If blank → fetch from historical JCP or SHARP data.

ASO Information Validation:

• ASO Name:
  • Must be present.
  • If blank → derive using ASO ID from historical JCP or SHARP.
• ASO ID:
  • Must be present.
  • If blank → derive using ASO Name from historical JCP or SHARP.

DSM / Region Standardization:

• Ensure DSM name is consistent with the master list.
• Check Region name for proper format and alignment with the correct hierarchy.
• Correct mismatches or spelling variations.

City / State / Region Details:

• These fields must be filled.
• If City, State, or Region is blank:
  • Use ASO ID + Store ID to derive the correct mapping from historical data.

Mandatory Business Fields:

• Ensure the following fields are completed for every record:
  • GSTIN
  • Segmentation (A/B/C/D)
  • TAM/Month
  • If any are missing → request details from the respective DSM.

Beat Plan Value Standardization:

• All plan entries should be recorded as “1”.
• Convert any variations such as:
  • “Visite”
  • “visit”
  • “Visited”
  • “Yes” → to “1”
• If value is blank or the store is not part of the beat plan → mark as “NA”.

File-Level Quality Check:

• Ensure no duplicate Store ID + Visit Date combinations.
• Confirm region wise segregation before consolidation.
• Validate that the final file is consistent in formatting (date format, column naming, case formatting).

1.16 Communication

Final processed files are shared with Lenovo reporting stakeholders.

1.17 Repository Details:

Field	Details
Name	JCP File
Type	.xlsx
Path / URL	📊JCP Beat Plan Consolidation
Access	Kiran/Admin
Owner / Team	Kiran
Last Updated	14-12-2025