Toyota UTrust

Get Started. It's Free
or sign up with your email address
Toyota UTrust by Mind Map: Toyota UTrust

1. Procurement

1.1. 4.1 Enables PO/PTL to maintain purchase checklist and confirm purchase

1.1.1. In Valuation History, Flag should show for procurement valuation. This will be done based on date comparison of valuation and confirm purchase

1.1.2. Can access it from Procurement Tab in Seller Enquiry

1.1.2.1. First access Popup for Valuation

1.1.2.1.1. Header : Valuation Popup

1.1.2.1.2. Pop up Message - Please check valuation and save

1.1.2.1.3. Valuation detail button

1.1.2.1.4. Checklist items for valuation will be prefilled. Target Date & Actual Date will be the date when checklist is saved.

1.1.2.1.5. Complete Valuation button will update the valuation in CTDMS and PO will be redirected to Procurement Checklist screen.

1.1.2.1.6. Notes

1.1.2.2. Screen Feature (Confirm Purchase)

1.1.2.2.1. Aadhar number(Tapping on for purchase entry)

1.1.2.2.2. Checklist Status

1.1.2.2.3. Target Date

1.1.2.2.4. Purchase Checklist

1.1.2.2.5. Confirm Vehicle Collection

1.1.2.3. PTL Approval screen (Alternate number)

1.1.2.3.1. PTL Can Access from Menu

1.1.2.3.2. Will display a list of approvals for alternate number

1.1.2.3.3. Two buttons will be displayed beside Alternate Number for PTL in Procurement Tab to approve or reject alternate number

1.1.2.3.4. Each item in the list will open Seller Enquiry with Procurement tab

1.1.2.4. Document Checklist Status

1.1.2.4.1. Target Date(Is mandate for the all pending documents )

1.1.2.4.2. Single Tap(document “Collected”)

1.1.2.4.3. Double Tap(document “Pending from Customer”)

1.1.2.5. Purchase

1.1.2.5.1. Confirm Vehicle Collection( OTP will be sent to customer’s mobile no. to confirm the vehicle collection)

1.1.2.6. System Integrations

1.1.2.6.1. UCTDMS

1.2. 4.2 Procured Vehicles List

1.2.1. Can access from Menu

1.2.1.1. Collected Vehicle (Refer to 4.2.1)

1.2.1.2. Purchased Vehicle (Refer to 4.2.2)

1.3. 4.2.1 Collected Vehicles

1.3.1. Show all Collected Vehicles

1.3.2. Items will be displayed in a list in descending order of collected date

1.3.3. Current Year’s (calendar) items will be displayed

1.3.4. Item fields

1.3.4.1. Vehicle Details: Reg. No. Make, Model, Suffix, Year, Color, Transmission, Fuel, Odometer

1.3.4.2. Collected Date & Time

1.3.4.3. PO Name

1.3.4.4. Sign Off Documents

1.3.4.4.1. On click

1.3.4.5. Pending Documents Count

1.3.5. Action

1.3.5.1. On Click

1.3.5.1.1. Open seller enquiry with procurement tab open.

1.3.5.2. Filters

1.3.5.2.1. Current Month

1.3.5.2.2. Last Month

1.3.5.2.3. Last 2 Months

1.3.5.2.4. Date Range (Range cannot be more than a year)

1.4. 4.2.2 Purchased Vehicles

1.4.1. Showing all Purchased Vehicles

1.4.2. Items will be displayed in a list in descending order of purchase date

1.4.3. Current Year’s (calendar) items will be displayed

1.4.4. Item fields

1.4.4.1. Vehicle Details: Reg. No. Make, Model, Suffix, Year, Color, Transmission, Fuel, Odometer

1.4.4.2. Current vehicle stage

1.4.4.3. Purchase Date & Time

1.4.4.4. PO Name

1.4.4.5. Sign Off Documents

1.4.4.5.1. On click

1.4.4.6. Pending documents count

1.4.5. Action

1.4.5.1. On Click

1.4.5.1.1. Open seller enquiry with procurement tab open.

1.4.5.2. Filters

1.4.5.2.1. Current Month

1.4.5.2.2. Last Month

1.4.5.2.3. Last 2 Months

1.4.5.2.4. Date Range (Range cannot be more than a year)

1.5. 4.3 Pending Document List

1.5.1. Display List of enquiries whose target date for collection is today, this month and selected date range (Based on selected filter)

1.5.2. Items

1.5.2.1. Enquiry No

1.5.2.2. Customer details : Name & No

1.5.2.3. Vehicle Details: Reg. No. Make, Model, Suffix, Year, Color, Transmission, Fuel, Odometer

1.5.2.4. PO Name

1.5.2.5. Call Action

1.5.2.6. Pending Documents Count

1.5.3. Action

1.5.3.1. On Click

1.5.3.1.1. Will open seller enquiry with procurement tab open

1.5.3.2. Filters

1.5.3.2.1. Today (Default Selected)

1.5.3.2.2. Current Month

1.5.3.2.3. Date Range (From Date: Cannot be less than current date and range cannot be more than a year)

2. SELLER ENQUIRY

2.1. Create Enquiry : Search - 1

2.1.1. Mobile No.

2.1.1.1. Search Result ( Last 3 month)

2.1.1.1.1. Search button

2.1.2. Vehicle Registration No.

2.1.2.1. Search Result ( Last 3 month)

2.1.2.1.1. Search button

2.1.3. First Name + Last Name

2.1.3.1. Search Result List (like address book)

2.1.3.1.1. Search Result ( Last 3 month only , more than that will be dropped )

2.1.3.2. Search result should be shown as drop down and result show the list like address book

2.1.4. Mobile Number & Registration Number

2.1.4.1. Search Result ( Last 3 month)

2.1.4.1.1. Search button

2.2. Types of Enquiry - 2

2.2.1. Walk - in /Field

2.2.2. N car Trade in

2.3. Existing Enquiry Pop up - 3

2.3.1. Same Dealer(Same Location)

2.3.1.1. Open in enquiry in View and Edit mode

2.3.1.2. Same PO

2.3.1.2.1. Edit Enquiry

2.3.1.3. Other P O

2.3.1.3.1. View in Read only mode

2.3.1.4. Cancel

2.3.1.4.1. Open create enquiry

2.3.2. Same Dealer (Different Location)

2.3.2.1. Enquiry information and Summary visible

2.3.2.2. Negotiation details not visible

2.3.2.3. UCM has read only mode

2.3.2.4. PO of that location will not be able to edit the enquiry

2.3.3. Different Dealer : Pop up will be shown

2.3.3.1. Name of Dealer

2.3.3.2. Enquiry date / Valuation date

2.3.3.2.1. If enquiry at Multiple dealers

2.3.4. PO not allocated

2.3.4.1. Allocation button will be visible to PO

2.3.4.1.1. Self Allocation can be done

2.4. Bussiness card scan - 4

2.4.1. PO->click->scan button

2.4.1.1. Scanner utility

2.4.1.1.1. Map field (Editable )

2.4.1.1.2. Map field pre filled

2.4.1.1.3. After mapping ->Save

2.5. RC card scan - 5

2.5.1. PO -> Click -> Scan Button

2.5.1.1. Scanner utility ->Device camera

2.5.1.1.1. Map field (Editable)

2.6. Customer Type- 6

2.6.1. Corporate Customer Type

2.6.1.1. Corporate Selection

2.6.1.1.1. Corporate Type

2.6.1.1.2. Corporate Number

2.6.1.1.3. Corporate Title

2.6.1.1.4. Corporate Name

2.6.1.1.5. Email(Mandatory with basic email validation)

2.6.1.2. More(Optional for PO)

2.6.1.2.1. Enquiry Generated by

2.6.1.2.2. Channel Contact Name

2.6.1.2.3. Activity Date

2.6.1.2.4. Actual Valuation Date

2.6.1.2.5. Preferred Contact mode(Drop down menu)

2.6.1.2.6. Office address inputs

2.6.1.2.7. Other Information

2.6.2. Individual Customer Type (Default Selected), (Toggle button)

2.6.2.1. Individual Selection(Mandatory field)

2.6.2.1.1. Mobile Number

2.6.2.1.2. Title

2.6.2.1.3. First Name

2.6.2.1.4. Middle Name

2.6.2.1.5. Last Name

2.6.2.1.6. Email (Mandatory Field)

2.6.2.2. More(Optional)

2.6.2.2.1. Enquiry Generated by

2.6.2.2.2. Channel Contact Name

2.6.2.2.3. Activity Date

2.6.2.2.4. Actual Valuation Date

2.6.2.2.5. Preferred Contact Mode (Contact number Mandatory)

2.6.2.2.6. Address

2.6.2.2.7. Office

2.6.2.2.8. Contact

2.6.2.2.9. Other Information

2.7. Enquiry Status selection - 7

2.7.1. Prospect (Default)

2.7.2. Hot

2.8. Mobile NumberInput, Search & OTP flow - 8

2.8.1. Mobile Number(mandatory field) / OTP Flow (not Mandatory)

2.8.1.1. Mobile number not verified / Mobile number changed

2.8.1.1.1. Show OTP related icon ->Tap on the button

2.8.1.2. Mobile number verified

2.8.1.2.1. Green color

2.9. Enquiry Basic Fields - 9

2.9.1. PO enters basic details

2.9.1.1. Customer

2.9.1.1.1. Mobile Number(Mandatory filed)

2.9.1.1.2. Title(Mandatory filed)

2.9.1.1.3. First name(Mandatory filed)

2.9.1.1.4. Last name(Mandatory)

2.9.1.1.5. Middle name

2.9.1.1.6. Email Address (Mandatory)

2.9.1.2. Enquiry

2.9.1.2.1. Source Type ( Mandatory filed)

2.9.1.2.2. Source name(Mandatory filed)

2.9.1.2.3. Status reasoning default value(Mandatory field)

2.9.1.3. Email entry (Mandatory input)

2.9.1.4. Location (city pre filled based on location)

2.9.1.5. PO(Default selected for logged in user)

2.9.1.6. Demand Structure((Mandatory filed)

2.9.1.6.1. Default Value of Demand Structure : "Replacement"

2.9.1.7. Direct purchase input [checkbox]

2.10. Stock Matching Data - 10

2.10.1. PO: Enter Vehicle information like, Make, Model, Year, Grade & Suffix

2.10.1.1. Counters for In Stock, Buyer Enquiry and Wanted list will be populated

2.10.2. PO :Input customer details +used vehicle details

2.10.2.1. Vehicle details get verified

2.10.2.1.1. Result:Stock matching data

2.11. Save Button(All mandatory fields should have inputs) - 11

2.11.1. Input follow up details: Next follow up plan ,date and time

2.11.1.1. Click save button

2.11.1.1.1. Enquiry will be saved and Enquiry number will be assigned

2.11.2. Select remark from standard remark set or text value in remarks

2.11.3. Mandatory fields

2.11.3.1. Basic / Personal Information

2.11.3.1.1. Mobile number

2.11.3.1.2. First name , last name , email

2.11.3.1.3. Source type , source name , source reasoning

2.11.3.1.4. Enquiry type and demand structure

2.11.3.2. Vehicle Information

2.11.3.2.1. Registration no (if not goushi )

2.11.3.2.2. Make, model , year

2.11.3.3. Negotiation and follow up

2.11.3.3.1. Customer expected price , Initial offer

2.11.3.3.2. Next follow up plan , date and remarks

2.12. Vehicle Details Entry - 12

2.12.1. Create Enquiry for current / used vehicle

2.12.1.1. Registered Vehicle Selection

2.12.1.1.1. Unregistered (Gaushi) vehicle

2.12.1.1.2. Registered vehicle (default). Vehicle registration number mandatory if registered selected.

2.12.1.2. Registration Number Input(Mandatory)

2.12.1.2.1. Enquiry exist: Another Dealer

2.12.1.2.2. Existing Enquiry Popup

2.12.1.3. Last three valuation Details which include Make, Model, Year, Grade, Suffix, Valuation &Valuation Date.

2.12.1.4. Input Vehicle information

2.12.1.4.1. Make

2.12.1.4.2. Model

2.12.1.4.3. Year

2.12.1.4.4. Month (optional)

2.12.1.4.5. Vehicle Grade and Suffix

2.12.1.5. VehiclePrice Related Information

2.12.1.5.1. Grade selection, Suffixselection, Exterior Colorselection, Fuel type selection, Transmission selection.

2.12.1.5.2. Mileage value, Accidental related input, Previous owner related input.

2.12.1.5.3. Insurance selection and Input Year and month.

2.12.1.5.4. Inspection done or not

2.12.1.5.5. Detailed inspection selected then Valuation process will be initiated.

2.12.1.5.6. Approximate Price based on basic mandatory vehicle details

2.12.1.6. Check Price

2.12.1.6.1. Only when price related input is already present->tap on check price

2.13. Stock Matching(PO enters make , model , year , grade& suffix) - 13

2.13.1. In Stock

2.13.1.1. Vehicle Stages (Filters)

2.13.1.1.1. Procurement

2.13.1.1.2. Refurbishment

2.13.1.1.3. Certification

2.13.1.1.4. Display

2.13.1.2. List

2.13.1.2.1. Make

2.13.1.2.2. Model

2.13.1.2.3. Year

2.13.1.2.4. Grade-Suffix

2.13.1.2.5. Color

2.13.1.2.6. Registration no

2.13.1.2.7. Buying Price

2.13.1.2.8. Selling price

2.13.1.2.9. Inventory Days

2.13.1.2.10. Vehicle stage

2.13.1.3. Certified / Non-Certified

2.13.1.3.1. Certified (show icon)

2.13.1.3.2. Non-Certified

2.13.2. Buyer Enquiry (For last 3 months)

2.13.2.1. List

2.13.2.1.1. Buyer Enquiry No

2.13.2.1.2. Buyer Enquiry Source

2.13.2.1.3. Date of Enquiry

2.13.2.1.4. Assigned SO

2.13.2.1.5. Buyer Name

2.13.2.1.6. Buyer Enquiry status

2.13.2.1.7. Customer budget range

2.13.2.1.8. Follow up Remarks

2.13.2.2. Status->Shown to all buyers enquiry ->Matching the filter criteria

2.13.2.2.1. Hot

2.13.2.2.2. Prospects

2.13.2.2.3. Success

2.13.2.2.4. Dropped

2.13.3. Wanted List

2.13.3.1. Filters

2.13.3.1.1. Make

2.13.3.1.2. Model

2.13.3.1.3. Year

2.13.3.2. List of record for each matching details

2.13.3.2.1. Make

2.13.3.2.2. Model

2.13.3.2.3. Year

2.13.3.2.4. Grade-Suffix

2.13.3.2.5. Who Added

2.13.3.2.6. Add Date

2.13.3.2.7. Color

2.13.3.3. ‘+’ icon visible if no records found

2.13.3.4. Add to Wanted List

2.13.3.4.1. Make

2.13.3.4.2. Model

2.13.3.4.3. Year

2.13.3.4.4. Grade / Suffix

2.13.3.4.5. Color

2.13.3.4.6. Matching values will be pre-populated

2.13.3.4.7. Cancel (Exist the add to wanted list screen)

2.13.3.4.8. Save (save the record)

2.13.3.4.9. Automatically removed after 45 days

2.13.4. Same dealer Group for PO will be able to view stock also with location

2.14. List & View Enquiry - 14

2.14.1. Users

2.14.1.1. PO

2.14.1.1.1. Assigned and open enquiries will be visible

2.14.1.2. PTL

2.14.1.2.1. All Team member wise enquiry will be shown

2.14.2. Type

2.14.2.1. All

2.14.2.1.1. Filtered by the Enquiry source

2.14.2.1.2. Enquiry Sources are Walk-in, Trade-in, Web, Service, Additional, Insurance & Finance

2.14.2.1.3. All selected by default

2.14.2.1.4. Make, Model, Year, Color, Customer name, Mobile no, Assigned PO name, Enquiry No, Enquiry Date, Enquiry Status,Last follow-up remarks& Status reasoning

2.14.2.2. New

2.14.2.2.1. Make, Model, Year, Color, Customer name, Mobile no, Enquiry Source, AssignedPO name, EnquiryNo, Enquiry Date and Enquiry Status

2.14.2.2.2. New Assigned Enquiries will be shown.

2.14.2.3. Follow-up

2.14.2.3.1. After first follow-up then show in follow-up & remove from New

2.14.3. Filters (for All List)

2.14.3.1. Filters

2.14.3.1.1. Filters by enquiry Sources Walk-in, Trade-in, Web, Service, Additional, Finance and others.

2.14.3.2. Default

2.14.3.2.1. By default All to be selected

2.14.3.3. Content

2.14.3.3.1. Enquiry source will be visible as content item of each enquiry

2.14.4. Enquiry Selection

2.14.4.1. Open with pre-filled enquiry data

2.14.4.2. View/ edit the enquiry details

2.14.5. Filter & Sort

2.14.5.1. Date Filters

2.14.5.1.1. Date Filters category

2.14.5.1.2. User

2.14.6. Enquiry Type/ Source Filter

2.14.6.1. All (will Show all details with below category)

2.14.6.2. New Car Trade-in

2.14.6.2.1. Old Car:Make, Model, Year, Color

2.14.6.2.2. Customer: Customer Name (Title, First Name, LastName & Middle Name), Mobile Number

2.14.6.2.3. New Car: Make, Model, Grade, Suffix

2.14.6.2.4. Enquiry: Enquiry Type, Enquiry No, Date, EnquiryStatus, PO

2.14.6.2.5. New car likely delivery date & Last follow up remarks

2.14.6.2.6. Last follow-up remarks: Used car follow up remark

2.14.6.2.7. Status reasoning

2.14.6.3. Walk-in / Field

2.14.6.3.1. Old Car:Make, Model, Year, Color

2.14.6.3.2. Customer: Customer Name (Title, First Name, LastName & Middle Name), Mobile Number

2.14.6.3.3. Enquiry: Enquiry Type, Enquiry No, Date, EnquiryStatus, PO

2.14.6.3.4. Last follow-up remarks

2.14.6.3.5. Status reasoning

2.14.6.4. Website

2.14.6.4.1. Old Car:Make, Model, Year, Color

2.14.6.4.2. Customer: Customer Name (Title, First Name, LastName & Middle Name), Mobile Number

2.14.6.4.3. Enquiry: Enquiry Type, Enquiry No, Date, EnquiryStatus, PO

2.14.6.4.4. Last follow-up remarks

2.14.6.4.5. Status reasoning

2.14.6.5. Service

2.14.6.5.1. Old Car:Make, Model, Year, Color

2.14.6.5.2. Customer: Customer Name (Title, First Name, LastName & Middle Name), Mobile Number

2.14.6.5.3. New Car: Make, Model, Grade, Suffix

2.14.6.5.4. Enquiry: Enquiry Type, Enquiry No, Date, EnquiryStatus, PO

2.14.6.5.5. Last follow-up remarks

2.14.6.5.6. If created from TOPSERV then Service adviser name (High Maintenance cost)

2.14.6.6. Finance

2.14.6.6.1. Old Car:Make, Model, Year

2.14.6.6.2. Customer: Customer Name (Title, First Name, LastName & Middle Name), Mobile Number

2.14.6.6.3. Enquiry: Enquiry Type, Enquiry No, Date, EnquiryStatus, PO

2.14.6.6.4. Last follow-up remarks

2.14.6.6.5. Status reasoning

2.14.6.6.6. Loan Details (Loan amount, Current EMI &Expected loan Close date).Or Pre-approved loan details (Approved Loan amount, New EMI)

2.14.6.7. Others

2.14.6.7.1. High BPC:High Body Paint Cost

2.14.6.7.2. Additional (New car Additional)

2.14.6.7.3. U-Car Dropped

2.14.6.7.4. Exchange (Old car to Old car)

2.14.6.7.5. IFC enquiry (Innova Fortuner )

2.14.7. New Car Enquiry List

2.14.7.1. Classified as first-time buyers (Demand Structure = F)

2.14.7.1.1. Customer: Customer Name (Title,First Name, Last Name & Middle Name), Mobile Number

2.14.7.1.2. New Car: Enquiry No, Date, Status, SO

2.14.7.1.3. New car Last follow-up remarks

2.14.7.1.4. Generate enquiry action

2.15. Edit Enquiry - 15

2.15.1. PO ->View or edit Seller Enquiry

2.15.1.1. Seller enquiry number and enquiry date is visible

2.15.1.1.1. Mandatory fields

2.15.1.1.2. Optional

2.16. Drop Enquiry - 16

2.16.1. Helps PO to drop enquiry

2.16.1.1. PO tap on Drop enquiry button->Drop enquiry pop up is displayed

2.16.1.1.1. Status reasoning Selection and standard remark selection

2.16.2. PTL get notified for drop enquiry pop up

2.16.2.1. Notification will have enquiry details , show drop reason and remarks

2.16.2.1.1. Click on Notification opens the enquiry

2.17. Enquiry Time line View - 17

2.17.1. Each events / actions

2.17.2. Enquiry Create, Edit, each follow-up details

2.17.3. Each follow-up remark with date and time of follow up

2.17.4. Plan follow-up and actual follow-up

2.17.5. Highlight planned follow-up not done by PO by different color / icon

2.17.6. PTL get notification for drop enquiry. Show Grey Color if notification not seen by PO (like Whatsapp delivery report) and if seen show as acknowledgement

2.18. Prompt will be sent as Alert notification.

2.19. View Valuation Summary - 18

2.19.1. Initial or Detailed

2.19.2. High level section wise score for Exterior, Interior, Engine and frame and final score

2.19.3. Valuation level showing as star

2.19.4. Accidents, Flooding values

2.19.5. Insurance details, Original RC Details

2.19.6. Estimated RF Cost

2.19.7. Documentation available or not

2.19.8. View Details will show the valuation details

2.20. Parallel Enquiry case - 19

2.20.1. Matching Enquiry (Mapping)

2.20.1.1. In case of the Trade-in Seller enquiry not created or transferred from New car system(TSA / NCTDMS) to UCTDMS system. The same customer attended by PO and a new seller enquiry (Trade-in)is created in UCTDMS system for further processing.

2.20.1.2. Once a new Trade-in Seller enquiry created in system(App Enquiry)/ UCTDMS system and later to that event the same enquiry gets transferred from New Car system, the Enquiry mapping engine will be implemented.

2.20.1.3. The new Trade-in enquiry created from system, will be checked with following matching parameters.

2.20.1.3.1. Used Vehicle Registration Number

2.20.1.3.2. Customer Mobile Number

2.20.1.3.3. Customer Name (Title, First Name, Last Name)

2.20.1.4. The matching parameters will be checked considering maximum 2days of differences.

2.20.1.5. The mapping engine will try to match all parameters. If all parameters are matching, then it will be mapped automatically.

2.20.1.6. If all conditions are not matching in that case the best matching related results will matched and PO will be prompted, PO need to manually specify the exact matching link.

2.20.1.7. Mapping the Seller enquiry (First created in UCTDMS)will be updated with new car enquiry details (created later),if any additional information is available.

2.20.1.8. With mapping the earlier created seller Enquiry(App Enquiry)will have all the details, and will have new car enquiry linkage created, and the second enquiry created from system will be automatically dropped, with duplicate enquiry reason (System define reason and remarks).

2.20.2. Exception Rule

2.20.2.1. if Vehicle registration Number and mobile number is not matching in that case PO need to map / link both the enquiries manually.

2.20.2.2. In enquiry listing un-mapped trade-in enquiries to be shown to PO & PTL

2.20.2.3. Under trade-in listing the un-mapped to be shown and filter for the un-mapped to be defined.

2.21. Enquiry Follow-up - 20

2.21.1. Follow-up List

2.21.1.1. PO

2.21.1.1.1. Dashboard or Menu

2.21.1.1.2. Need to be followed up

2.21.1.1.3. Each Item Details

2.21.1.2. PTL

2.21.1.2.1. Specific enquiry and its follow-up details

2.21.1.2.2. Adding PTL remarks

2.21.1.2.3. Add remarks by PTL and notification will be sent to PO

2.21.1.2.4. Show Grey color if PO has not yet seen notification (like Whatsapp delivery report)

2.21.1.2.5. Call button in follow-up screen

2.22. Enquiry List –Allocation - 21

2.22.1. Allocation of PO can be done by PTL

2.22.2. Enquiry source Type

2.22.2.1. All

2.22.2.2. New Car Trade-in

2.22.2.2.1. Available real time to PTL

2.22.2.2.2. Get notification when created

2.22.2.2.3. Notification will be high priority

2.22.2.2.4. PTL click on the notification

2.22.2.3. Walk-in / Field

2.22.2.4. Website

2.22.2.4.1. Once created in the UCTDMS system

2.22.2.4.2. PTL get notification as information

2.22.2.4.3. PTL does allocation

2.22.2.5. Service

2.22.2.5.1. Service list details available to PTL

2.22.2.5.2. Generate the enquiry and Allocate PO

2.22.2.5.3. Generated service Enquiries

2.22.2.5.4. Created directly in to the system from TOPSERV

2.22.2.5.5. PO can self-allocated

2.22.2.6. Finance

2.22.2.6.1. Old Car:Make, Model, Year, Color, Registration No

2.22.2.6.2. Customer: Customer Name (Title, First Name, LastName & Middle Name), Mobile Number

2.22.2.6.3. Finance Details:Loan Outstanding, Loan Closure date, current EMI.

2.22.2.6.4. Same dealer code to be matched

2.22.2.6.5. TFS related values

2.22.2.6.6. Customer list,Generate the enquiry & allocate PO

2.22.2.6.7. TFS Customer list and view Finance Enquiries for PTL

2.22.2.7. Others

2.22.2.7.1. High BPC:High Body Paint Cost (Created from service/ TOPSERV)

2.22.2.7.2. Additional (New car Additional)

2.22.2.7.3. U-Car Dropped

2.22.2.7.4. Exchange (Old car to Old car)

2.23. Self-Allocation by PO- 22

2.23.1. PO gets any walk-in customer or any customer details are forwarded to PO

2.23.1.1. PO search by mobile number / Registration number /First name+Last Name

2.23.1.2. Self allocate screen will be available if no PO is allocated (Refer screen for buyer enquiry)

2.23.1.3. After self-allocated and further processing can be done

2.23.1.4. Cancel and create a new enquiry as well

2.24. Duplicate Enquiry creation

2.24.1. Duplicate buyer enquiry create in system, the notification will be sent to reporting PTL and UCM

2.25. Multiple PTL case

2.25.1. For dealer having multiple PTL then enquiry needs to allocated one by one to available PTL

2.26. Enquiry – Price Approvals / Negotiation -23

2.26.1. Price Approvals are done between PO and PTL

2.26.1.1. PO

2.26.1.1.1. Input Values like expected customer price & latest offer price for approval

2.26.1.1.2. View Negotiation / Approval history

2.26.1.1.3. Save Enquiry & Negotiation / Approval

2.26.1.1.4. Notification will be sent to respective PTL

2.26.1.2. PTL

2.26.1.2.1. Get the notification for price approval

2.26.1.2.2. Click on the notification, Seller enquiry negotiation section to be displayed

2.26.2. Negotiation History

2.26.2.1. PO/ PTL can see Negotiation history

2.26.2.2. Descending order of dates

2.26.2.3. Green Color icon for approved price

2.26.2.4. Red Color icon for rejected price

2.26.2.5. Yellow Color icon yet to be commented on

2.26.2.6. PTL new price will automatically reject PO old price

2.26.2.7. Each details

2.26.2.7.1. Latest offer price

2.26.2.7.2. Date & PO name who send for approval

2.26.2.7.3. Date & PTL name who approve / Rejects

2.26.2.7.4. PTL remarks.

2.26.2.8. PTL is not approved the price show in Yellow color

2.26.2.9. For notification acknowledgement show in Grey Color (like Whatsapp delivery report)

2.26.2.10. 50,000 or less difference between customer expected price & final/ last offered price. Send Notification to UCM & Group Head. Discuss with PO / PTL

2.26.2.10.1. UCM will also receive notifications like PTL, and all actions(Delivered,Seen etc) will be like whatsApp

3. Buyer Enquiry

3.1. 7.1. Buyer Enquiry module is for Sales Team to create & manage

3.1.1. Buyer enquiries

3.1.2. Follow-up

3.1.3. Vehicle search

3.1.4. Shortlisting of vehicles

3.1.5. Select vehicle and its price negotiations

3.1.6. Finance related options

3.1.7. Enquiries linked orders

3.1.8. Invoice details view & Delivery note

3.2. 7.1.1. - Search (with Mobile or Customer name)

3.2.1. Search Result ( Last 3 month)

3.2.1.1. Search button

3.2.1.1.1. Non Existing Enquiry

3.2.1.1.2. Name search will be there like address book view, specific name to be selected. (Refer to 7.1.2.2.)

3.2.1.1.3. Existing enquiry (Edit Existing enquiry pop up)

3.2.1.1.4. Existing enquiry(Different Dealer)

3.2.1.2. User action

3.2.1.2.1. Open click

3.2.1.2.2. Cancel

3.2.1.2.3. Self-allocation (For same Dealer Location) if SO is not allocated & STL is not around

3.2.2. UCM will be able to view but not EDIT

3.3. 7.1.2. - Basic & Mandatory Details

3.3.1. User need to input the basic & mandatory details to save the buyer enquiry. (Refer to 7.1.2.2. & 7.1.2.3.)

3.4. 7.1.2.1. - Mobile number input, Search & OTP flow (Delaler's Choice to keep Mandatory)

3.4.1. SO enters the Mobile number, if the mobile number is available in system, search will be performed

3.4.2. SO enters the Mobile number, if the mobile number is not in the system in that case the OTP related icon/ button will be visible

3.4.3. Show OTP related icon ->Tap on the button

3.4.3.1. Send OTP to defined mobile number

3.4.3.1.1. Customer receive OTP (verify within 300 seconds)

3.4.3.1.2. OTP verification pop up will be visible

3.4.3.2. Resend OTP

3.4.3.2.1. Link will be hidden for 300 sec

3.4.4. OTP verification not Mandatory process

3.4.5. OTP Procedure to keep mandatory or not upto dealer

3.5. 7.1.2.2. - Individual Customer Type (Default Selected)

3.5.1. Individual Selection(Mandatory field)

3.5.1.1. Mobile Number

3.5.1.2. Title("Mr." as default)

3.5.1.3. First Name

3.5.1.4. Middle Name (not Mandatory)

3.5.1.5. Last Name

3.5.2. More(Optional)

3.5.2.1. Enquiry Generated by

3.5.2.1.1. Channel / Contact Name

3.5.2.1.2. Activity Date

3.5.2.2. Preferred Contact Address & Preferred Contact Mode (Contact number Mandatory)

3.5.2.3. Address

3.5.2.3.1. Address 1

3.5.2.3.2. Address 2

3.5.2.3.3. Address 3

3.5.2.3.4. State

3.5.2.3.5. District

3.5.2.3.6. City

3.5.2.3.7. Location

3.5.2.3.8. Pin Code

3.5.2.3.9. Telephone Number( Mandatory based on selection. i.e., if the residence type is selected then residence No. is mandatory)

3.5.2.4. Office

3.5.2.4.1. Address 1

3.5.2.4.2. Address 2

3.5.2.4.3. Address 3

3.5.2.4.4. State

3.5.2.4.5. District

3.5.2.4.6. City

3.5.2.4.7. Location

3.5.2.4.8. Pin Code

3.5.2.4.9. Telephone Number

3.5.2.5. Contact

3.5.2.5.1. Title

3.5.2.5.2. First Name

3.5.2.5.3. Middle Name

3.5.2.5.4. Last Name

3.5.2.5.5. Contact No.

3.5.2.5.6. Email

3.5.2.6. Other Information

3.5.2.6.1. Reason for buy

3.5.2.6.2. Remarks

3.6. 7.1.2.3. - Corporate Customer Type (Not individual)

3.6.1. Corporate Selection

3.6.1.1. Corporate Type

3.6.1.2. Contact Number

3.6.1.3. Corporate Title

3.6.1.4. Corporate Name

3.6.2. More(Optional for SO)

3.6.2.1. Enquiry Generated by

3.6.2.1.1. Channel / Contact Name, Activity Date

3.6.2.2. Preferred Contact mode

3.6.2.3. Office address

3.6.2.3.1. Address 1

3.6.2.3.2. Address 2

3.6.2.3.3. Address 3

3.6.2.3.4. State

3.6.2.3.5. District

3.6.2.3.6. City

3.6.2.3.7. Location

3.6.2.3.8. Pin Code

3.6.2.3.9. Telephone Number

3.6.2.4. Other Information

3.6.2.4.1. Reason for Buy

3.6.2.4.2. Remarks

3.7. 7.1.2.4. - Business card scan

3.7.1. SO->click->scan button

3.7.1.1. If user don't have input values

3.7.1.1.1. Scanner utility

3.7.1.2. If user have already input values

3.7.1.2.1. will prompt to user for overwriting the values

3.8. 7.1.2.5. - Enquiry Source & Other filed entry

3.8.1. Create new enquiry will have Walk-in / Field (Default)

3.8.1.1. SO enter the basic details of the customer and enquiry (Refer to 7.1.6.2)

3.8.1.1.1. Mob. No

3.8.1.1.2. Title

3.8.1.1.3. First name

3.8.1.1.4. Middle name

3.8.1.1.5. Last name

3.8.1.1.6. Source type, Source name, Status reasoning (Mandatory)

3.8.1.1.7. Email (Mandatory)

3.8.1.1.8. SO will be default selected for logged in user

3.8.1.1.9. Location(City will be prefilled based on the location)

3.8.1.1.10. Enquiry source (Mandatory) ( by default Walk-in)

3.9. 7.1.2.6. - Enquiry Status change

3.9.1. Prospect(Default) (Refer to 7.1.2.2.)

3.9.2. Hot (Refer to 7.1.2.2.)

3.9.3. Success

3.9.4. Dropped

3.10. 7.1.3.1. - Vehicle entry & Stock matching

3.10.1. Vehicle entry & search dealer stock (search vehicles which are available in stock) ( Refer to 7.1.3.2)

3.10.1.1. Vehicle Search

3.10.1.1.1. Make: Selection from available makes.

3.10.1.1.2. Model( this depends on make selection.)

3.10.1.1.3. Grade & Suffix(depends on selected Make & Model)

3.10.1.1.4. Year: Numericinput value (Selected year and above will be applicable)

3.10.1.1.5. Exterior Color: selection from available Color in application.

3.10.1.1.6. Budget From & Budget To

3.10.1.1.7. Mileage range

3.10.1.1.8. Transmission type (Auto or Manual or AMT)

3.10.1.1.9. Fuel type

3.10.1.2. Vehicle search & Screen features

3.10.1.2.1. No default selected

3.10.1.2.2. Min 3 parameters need to select (if more(all the selected parameters-based filter will be done in vehicle stock search))

3.10.1.2.3. Carousal view

3.10.1.2.4. dealer group the searched vehicles

3.10.1.2.5. Vehicle section is not in expand mode

3.10.1.3. Carousal view actions

3.10.1.3.1. Slide left/right

3.10.1.3.2. Slide up

3.10.1.3.3. Click / select

3.10.1.4. Vehicle wise action options

3.10.1.4.1. Share

3.10.1.4.2. Add to Wishlist / Shortlist (Vehicle added to shortlisting in inquiry)

3.10.1.4.3. Add to Test drive

3.10.1.4.4. Select vehicle (for price negotiation and order booking)

3.10.1.5. Vehicle details view (Vehicle presentation view)

3.10.1.5.1. Vehicle details view / presentation

3.10.1.6. User actions

3.10.1.6.1. SO need to select minimum three filter parameters

3.10.1.6.2. If SO selects Make, Model and year in that case the vehicles in stock will be searched based on the matching criteria and the carousal view will be visible

3.10.1.6.3. In addition to the selected or input parameters, if SO selects any additional parameter or gives input in that case the vehicles will be applied with the new added filter

3.10.1.6.4. The vehicle search will be done based on all the input parameters

3.10.1.6.5. If SO did not enter the budget range in that case, based on the shortlisted vehicles the minimum and maximum sale price will be defined as budget range. In case of single vehicle shortlisting, the sale price will be defined to budget range.

3.10.1.6.6. If the shortlisted vehicle or selected vehicle is not having sale price defined in that case budget range entry is required to enter

3.10.1.6.7. The searched based vehicles will be available in carousal view, SO can navigate the vehicles and based on the customer’s shortlisting the vehicles will be shortlisted.

3.10.1.6.8. For the shortlisted vehicles test drive can be selected as well.

3.10.1.6.9. If SO want to share the vehicle details in that case with share option, the vehicle display card will be shared to customer

3.10.1.6.10. Based on the vehicle details Make, model & year input the stock counters will be updated.

3.10.2. Stock matching (Vehicle information-based stock matching counters will be updated)

3.11. 7.1.3.2. - Stock Matching Data

3.11.1. User Action

3.11.1.1. SO will Enter Vehicle information like, Make, Model, Year.

3.11.1.2. In Stock, Seller Enquiry, Buyer Enquiry and Wanted list will be populated.

3.11.1.3. No data found then in wanted list show add option.

3.11.1.4. Clicking on the In-Stock Icon / button the Stock matching screen will be visible.

3.11.1.5. The Stock will be shown based on Make, Model&Year

3.11.1.5.1. Enabled (Default)

3.11.1.5.2. Disabled

3.11.1.6. Matching vehicle stock from the inventory will be visible, further filtered based on the vehicle stage. Default selection will be all matching vehicles.

3.11.1.7. For dealer group, stock should be visible for current dealer location.

3.11.1.8. Filter to view stock of another dealer location of the same group

3.11.1.8.1. Details should show dealer location as additional field.

3.11.1.9. Vehicle Stages

3.11.1.9.1. Procurement

3.11.1.9.2. Refurbishment

3.11.1.9.3. Certification

3.11.1.9.4. Display

3.11.2. Stock Matching Screen

3.11.2.1. Stock Matching Details (Show Hot as default))

3.11.2.1.1. Each matching record will show Make, Model, Year, Grade-Suffix, Color of the vehicle, Registration no, Buying Price, Selling price, Inventory Days and Vehicle stage

3.11.2.1.2. Vehicle stages are Procurement, Refurbishment, Certification and Display. All stages will give information of all the stock vehicles, matching with the Enquiry vehicle information.

3.11.2.1.3. User can select the specific vehicle stage and the stage specific vehicles will be filtered.

3.11.2.1.4. Display stage vehicles will be shown all the vehicle in display, which includes non-certified and certified vehicles.

3.11.2.1.5. Certified vehicles will be shown with additional certificate icon with Display stage.

3.11.2.2. Buyer Enquiry Screen

3.11.2.2.1. Each matching record will show Buyer name, Mobile number, selected vehicle details like make, model, year and registration no,Buyer Enquiry No, Buyer Enquiry Source, Date of Enquiry, Assigned SO,Buyer Enquiry status& last follow up Remarks.

3.11.2.2.2. Hot buyer enquiry status will be shown as default selection.All status will show all the Buyer enquires which are matching the filter criteria.

3.11.2.2.3. User can select specific Buyer Enquiry status; the status specific Buyer enquiries will be visible.

3.11.2.2.4. There will be last 3 months buyer enquiries will be visible in stock matching.

3.11.2.3. Seller Enquiry Screen

3.11.2.3.1. Each matching record will show Vehicle make, model, year, Color, Seller Enquiry No,Enquiry Source, Date of Enquiry, Assigned PO, SellerName, SellerEnquiry status & last follow up Remarks.

3.11.2.3.2. Hot seller enquiry status will be shown as default selection. Seller Enquiry status are Hot, Prospects, Success and Dropped. All status will show all the Buyer enquires which are matching the filter criteria.

3.11.2.3.3. User can select specific SellerEnquiry status; the status specific Seller enquiries will be visible.

3.11.2.3.4. There will be last 3 months Seller enquiries will be visible in stock matching.

3.11.2.4. Wanted List Screen

3.11.2.4.1. User Actions

3.11.2.4.2. Record will show Make, Model, Year, Grade-Suffix, Color, who added and Add Date

3.11.2.4.3. Add option will be available in wanted list screen so User can add a new item to wanted list

3.11.2.4.4. Data is not found in that case wanted list will have ‘+’ icon visible.

3.11.2.4.5. Show the wanted list addition screen if icon is clicked

3.11.2.4.6. Add to Wanted List

3.12. 7.1.4 - Finance

3.12.1. SO can input the values in Finance section(if customer is interested in Finance)

3.12.1.1. Finance screen & features

3.12.1.1.1. Input value (Check box)

3.12.1.1.2. When finance required is selected then finance dropdown will be enabled, with Select value and TFS will be the first value to select.

3.12.1.1.3. If finance required is selected, then financer selection is mandatory

3.12.1.1.4. If TFS Lead number available, it needs to be displayed

3.12.1.1.5. Input for EMI which will be calculated value based on EMI calculator.

3.12.1.1.6. EMI Calculator button will open EMI calculator button.

3.12.1.1.7. Documents list button click will open Finance related document list.

3.12.1.2. User actions

3.12.1.2.1. When SO open the Finance section

3.12.1.2.2. TFS loan number input and enter will query TFS application API and get the current customer’s Loan details based on the input loan number

3.12.1.2.3. If customer is interested in Finance, then user wills check on finance required

3.12.1.2.4. When user click on finance required, it will enable financer selection which will have TFS as pre-selected, but user can change to other financers based on need

3.12.1.2.5. TFS is selected as financer in that case the buttons for EMI calculator and documents will be enabled

3.12.1.2.6. When user click on EMI calculator button a new pop-up screen will be visible

3.12.1.3. TFS Document List

3.12.1.3.1. Based on the user type either Individual or corporate the document list will be show.

3.12.1.3.2. User can update the customer for finance related documents, these documents will be TFS specific requirements only. For other financers these documents can vary.

3.12.1.4. Finance data sharing to TFS application.

3.12.1.4.1. ExistingTFS customer entry and / or finance required, and financer

3.12.1.4.2. From TFS application against these information TFS lead number will be shared which will be used for further communication with TFS application

3.12.1.4.3. During retail if TFS Loan status details will be available based on TFS Lead number so if the TFS Lead number is not linked with Enquiry in that case TFS loan status will not be available in retail order listings

3.13. 7.1.5. - Exchange - Seller Enquiry

3.13.1. User actions

3.13.1.1. SO will click on exchange icon

3.13.1.1.1. Pop-up(Exchange information)

3.14. 7.1.6.Enquiry save with Initial Negotiation & Follow up

3.14.1. To save the buyer enquiry SO need to input the initial negotiation information (not mandatory) and follow-up plan

3.15. 7.1.6.1. - Negotiation & Follow up

3.15.1. Negotiation

3.15.1.1. The selected vehicle’s sale price will be visible with information icon

3.15.1.1.1. User actions

3.15.2. Follow Up

3.15.2.1. User actions

3.15.2.1.1. SO will input next follow-up

3.16. 7.1.6.2. - Enquiry Save

3.16.1. User actions

3.16.1.1. Visible in Edit mode

3.16.1.1.1. Buyer enquiry number

3.16.1.1.2. Buyer enquiry date

3.16.1.2. Validation(Mandatory fields)

3.16.1.2.1. Basic / Personal information

3.16.1.2.2. Vehicle Information

3.16.1.2.3. Follow up

3.16.1.3. If these fields input are not done in that case the field(s) required related validation message will be visible

3.17. 7.2. - View-Edit Buyer Enquiry

3.17.1. Edit Enquiry screen enables SO to view / edit Buyer enquiry

3.17.1.1. Same SO will be able to EDIT

3.17.1.2. Different SO will be able to VIEW

3.18. 7.2.1. - Edit Enquiry

3.18.1. User actions

3.18.1.1. Visible in Edit mode

3.18.1.1.1. Buyer enquiry number

3.18.1.1.2. Buyer enquiry date

3.18.1.2. Validation(Mandatory fields)

3.18.1.2.1. Basic / Personal information

3.18.1.2.2. Vehicle Information

3.18.1.2.3. Follow up

3.18.1.3. If these fields input are not done in that case the field(s) required related validation message will be visible (Refer to 7.1.6.2)

3.19. 7.2.2.- View/Edit Selected Vehicle

3.19.1. Vehicle screen features

3.19.1.1. Selected vehicle will show

3.19.1.1.1. Different back Color

3.19.1.2. selected icon will be show

3.19.1.2.1. Green Color

3.19.1.3. Shortlisted vehicles

3.19.1.3.1. Red color

3.19.1.4. Vehicle test drive given to customer and updated in that case the test drive icon

3.19.1.4.1. Green color

3.19.1.5. During view /edit time the shortlisted/ selected vehicle’s real-time status will be visible

3.19.1.5.1. If the vehicle is already booked / delivered

3.19.1.5.2. If booked/Sold status to be shown

3.19.1.5.3. If other buyer enquiry it is booked

3.19.1.5.4. If Selected / blocked vehicle is booked in other buyer enquiry

3.19.1.5.5. If the vehicle is blocked

3.19.2. User actions

3.19.2.1. SO can update the selection of shortlisted vehicles / selected vehicle.

3.19.2.2. If test drive is given in that case SO can tap on test drive icon

3.19.2.2.1. Green color

3.19.2.3. SO can remove vehicle from

3.19.2.3.1. Shortlisting / selection

3.19.2.3.2. Search more vehicles with different parameter

3.19.2.3.3. New vehicles to shortlisting / selection for further updates / negotiations

3.20. 7.2.3. - Edit Finance information

3.20.1. User actions (Refer to 7.1.4)

3.20.1.1. SO can view the already input finance related information.

3.20.1.2. Input can be made(If the input for finance section is not there )

3.20.1.3. User can change all the input parameters(If finance not required, input will be disable)

3.20.1.4. If Financer change from TFS to other value

3.20.1.4.1. The data which are already shared with TFS application will not get affected

3.20.1.5. If any changes in vehicle, loan amount

3.20.1.5.1. The updated values will be send to TFS application against the old TFS Lead number

3.20.1.6. After inquiry stage if the TFS loan related status is required

3.20.1.6.1. The details need to be linked with Buyer enquiry only.

3.20.1.7. Lead number and its status to be shown(for booked vehicle)

3.21. 7.2.4.- Order & Invoice details

3.21.1. Order & Invoice screen & features

3.21.1.1. Will have all the view/ read only information

3.21.1.1.1. Visible

3.21.1.2. There will be batch interface defined for getting Order, Invoice and delivery note related data

3.21.1.3. UCTDMS system update, after interface sync the data will be visible

3.21.1.3.1. Sales order details

3.21.1.3.2. Invoice details

3.21.1.3.3. Delivery notes details

3.21.1.4. If the PDI details & document status updated in retail section, the updated status will be visible

3.21.2. User Actions

3.21.2.1. SO can click on

3.21.2.1.1. Invoice button to view invoice report.

3.21.2.1.2. Delivery note button to view delivery note report

3.22. 7.2.5. - Drop buyer Enquiry

3.22.1. User actions

3.22.1.1. SO

3.22.1.1.1. Click on drop enquiry

3.22.1.2. STL

3.22.1.2.1. STL will get the notification for drop enquiry request.

3.22.1.2.2. Notification will have enquiry details

3.22.1.2.3. Once STL approves the drop request, the enquiry status will be set to dropped.

3.22.1.2.4. If STL rejects the drop request in that case the enquiry will remain in the same status.

3.23. 7.2.6. - Enquiry Timeline

3.23.1. User actions

3.23.1.1. SO Click on Enquiry time line button

3.23.1.1.1. Timeline screen

3.24. 7.2.7 - Follow-up

3.24.1. Follow-up List

3.24.1.1. Dashboard/Menu(Buyer enquiry list open by default follow up list will open)

3.24.1.2. BuyerEnquiry –Follow-up list have the enquiry listings which need to be followed up.

3.24.1.3. The follow up list will have enquiry source / type wise selection. (All is default selected.)

3.24.1.4. Grouping will be day wise and Today and Next day’s follow-up items will be visible.

3.24.1.5. Pending follow-ups

3.24.1.5.1. Shown first

3.24.1.6. Planned follow-up which is missed

3.24.1.6.1. Red color

3.24.1.7. Each item will show the details including

3.24.1.7.1. Customer name and mobile number

3.24.1.7.2. Enquiry number, date and enquiry status

3.24.1.7.3. Vehicle information:

3.24.1.7.4. Last follow-up date and Last follow-up remarks

3.24.2. User actions

3.24.2.1. SO can filter the enquiries based on enquiry source/ filter like Web, Walk-in etc.

3.24.2.2. SO can select the specific Buyer enquiry which need to be followed-up.

3.24.2.3. Selecting specific item will open a Follow up screen for the selected enquiry.

3.24.2.3.1. Selected Enquiries Follow-up details will be available in follow-up screen

3.24.2.3.2. Follow-up section of the BuyerEnquiry have

3.24.2.3.3. Call button

3.24.2.3.4. For STL Follow up Remarks related notification will be sent to SO

3.24.3. STL Follow-up

3.24.3.1. User action

3.24.3.1.1. STL can view specific enquiry and its follow-up details.

3.24.3.1.2. When STL view the follow up details, and there will be option for adding STL remarks.

3.24.3.1.3. STL can click on Add Remarks button and remarks

3.24.3.1.4. When STL add any specific remarks, the notification will be sent to SO for the remarks and SO can view the STL remarks in follow up section.

3.24.4. System Integrations:

3.24.4.1. UCTDMS: Enquiry related information Save, Get Enquiry information including Follow-up, Negotiations, Valuation

3.25. 7.2.8. - Price Approvals / Negotiation - Buyer enquiry

3.25.1. BuyerEnquiry Negotiation Section:(SO will enter input for Latest expected price from customer and Latest offered price for the vehicle in Negotiation section.)

3.25.1.1. User actions

3.25.1.1.1. SO

3.25.1.1.2. STL

3.26. 7.2.9. - Blocking of vehicle

3.26.1. Vehicle Block feature in Negotiation Section (Only STL can Block the vehicle)

3.26.1.1. On customer / buyer request the vehicle is blocked with the block/ token amount.

3.26.1.2. Negotiation section of buyer enquiry will have vehicle block option available for STL

3.26.1.3. STL can block the vehicle with block amount. (Block amount is mandatory but zero can be accepted as block amount)

3.26.1.4. Once the selected vehicle is blocked, in vehicle listing screen the block icon will be visible

3.26.1.5. Blocked vehicles will be visible and available for other buyer enquiries

3.26.1.5.1. Name of STL (Who blocked the vehicle)

3.26.1.5.2. Blocked date

3.26.1.5.3. Dealer location (in case of dealer group).

3.26.1.6. If the blocked vehicle is not further confirmed for order in that case STL can un-block the vehicle

3.26.1.6.1. When Vehicle is Un-blocked then the token/ block amount will be removed & in vehicle search the block icon will be removed

3.26.1.7. The blocked vehicle will be visible in another buyer enquiry search and can be shortlisted.

3.26.1.8. Once STL block the vehicle, information notification will be sent to UCM, STL & SO (Against the buyer enquiry the vehicle is blocked).

3.26.1.9. The blocked vehicles will be visible in stock statements as separate status of blocked.

3.26.1.10. The blocked vehicle cannotbe selected in another enquiry for further processing.

3.26.1.11. The blocked vehicles will be visible in stock statements as separate status of blocked.

3.26.1.12. The blocked vehicle can not be selected in another enquiry for further processing.

3.26.2. User actions

3.26.2.1. STL will have the Block vehicle button visible.

3.26.2.2. STL can click on Block vehicle button, Block amount input will be visible

3.26.2.3. For blocked vehicles action-based notification will be send to UCM, STL & SO.

3.26.2.3.1. Notification will be sent after 7 days, 14 days and 21 days for extending the block or releasing the block (un-block).

3.26.2.3.2. In Notification if the STL extends then the block will remain otherwise after 2 days the block will be removed

3.26.2.4. Input the block amount and save Buyer enquiry will block the selected vehicle

3.26.2.5. If the vehicle is already blocked then click on Un-Block vehicle, block amountwill be removed, and vehicle will be un-blocked

3.26.3. UnBlocking can be done by same STL who block the car. Also UCM for same dealer group has provision for Unblocking.

3.27. 7.3 - List Buyer Enquiry

3.27.1. Enquiry list availability

3.27.1.1. STL

3.27.1.2. SO

3.28. 7.3.1 -Enquiry List –All & New (Beside SO & STL others are also involved please refer to user Matrix)

3.28.1. Type

3.28.1.1. All

3.28.1.1.1. Users

3.28.1.1.2. Filtered by the Enquiry source

3.28.1.1.3. Enquiry Sources are Walk-In,Web,Tele-In,Print Adv., Exchange Mela, New Car showroom,New Car Dropped,U-Car Dropped.

3.28.1.1.4. By default, all will be selected, where all source wise inquiries will be visible.

3.28.1.1.5. Items

3.28.1.2. New

3.28.1.2.1. Users

3.28.1.2.2. New Assigned Enquiries will be shown

3.28.1.2.3. For SO the Assigned SO name will not be visible.

3.28.1.2.4. Items

3.28.1.3. Follow-up

3.29. 7.3.2 Enquiry source Filter

3.29.1. Enquiries can be filtered by Enquiry source (Refer to 7.3.4)

3.29.1.1. Enquiry source

3.29.1.1.1. Walk-in

3.29.1.1.2. Web

3.29.1.1.3. Tele-in

3.29.1.1.4. Print Adv

3.29.1.1.5. Exchange Mela

3.29.1.1.6. New car showroom

3.29.1.1.7. New car dropped

3.29.1.1.8. U-Car dropped

3.29.2. "All" selected by default

3.29.3. In case of all Enquiry selection the enquiry source will be visible as content item of each enquiry.

3.30. 7.3.3 Enquiry Selection

3.30.1. Open with pre-filled enquiry data

3.30.2. View/ edit the enquiry details

3.31. 7.3.4 Filter & Sort

3.31.1. Date Filters

3.31.1.1. Date Filters category

3.31.1.1.1. This Month (Default Selection)

3.31.1.1.2. Last Month

3.31.1.1.3. Previous 2 Months

3.31.1.1.4. Date Range selection [Maximum date range 6 Months]

3.31.1.1.5. Enquiry Status filter

3.31.1.1.6. Filter will be for Make, Model, Year

3.31.1.2. User

3.31.1.2.1. STL

3.31.1.2.2. SO

3.32. 7.3.5 Enquiry Type/ Source Filter (Refer to 7.3.6)

3.32.1. All

3.32.2. Walk-In/ Field Enquiry

3.32.3. Web

3.32.4. Tele-In

3.32.5. Print Adv. (Print Advertise)

3.32.6. New car showroom

3.32.7. New car dropped

3.32.8. Others

3.32.8.1. on click (Dropdown will show other types)

3.32.8.1.1. Exchange Mela

3.32.8.1.2. U-Car Dropped

3.33. 7.3.6 Enquiry Type/ Source Filter

3.33.1. All

3.33.2. Walk-In/ Field Enquiry

3.33.2.1. Customer Details

3.33.2.1.1. Customer Name(Title, First Name, Last name & Middle name)

3.33.2.1.2. Mobile Number

3.33.2.2. Enquiry details

3.33.2.2.1. Enquiry Type, Enquiry number, Date Enquiry status, SO

3.33.2.3. Vehicle information

3.33.2.3.1. Shortlisted or Selected vehicles

3.33.2.4. Last follow-up remarks & Date

3.33.2.5. For SO the Assigned SO name will not be visible.

3.33.3. Web

3.33.3.1. Customer Details

3.33.3.1.1. Customer Name(Title, First Name, Last name & Middle name)

3.33.3.1.2. Mobile Number

3.33.3.2. Enquiry details

3.33.3.2.1. Enquiry Type, Enquiry number, Date Enquiry status, SO

3.33.3.3. Vehicle information

3.33.3.3.1. Shortlisted or Selected vehicles

3.33.3.3.2. New node

3.33.3.4. Last follow-up remarks & Date

3.33.3.5. For SO the Assigned SO name will not be visible.

3.33.4. Tele-In

3.33.4.1. Enquiry details

3.33.4.1.1. Enquiry Type, Enquiry number, Date Enquiry status, SO

3.33.4.2. Customer Details

3.33.4.2.1. Customer Name(Title, First Name, Last name & Middle name)

3.33.4.2.2. Mobile Number

3.33.4.3. Vehicle information

3.33.4.3.1. New node

3.33.4.3.2. Shortlisted or Selected vehicles

3.33.4.4. Last follow-up remarks & Date

3.33.4.5. For SO the Assigned SO name will not be visible.

3.33.5. Print Adv. (Print Advertise)

3.33.5.1. Enquiry details

3.33.5.1.1. Enquiry Type, Enquiry number, Date Enquiry status, SO

3.33.5.2. Customer Details

3.33.5.2.1. Customer Name(Title, First Name, Last name & Middle name)

3.33.5.2.2. Mobile Number

3.33.5.3. Vehicle information

3.33.5.3.1. New node

3.33.5.3.2. Shortlisted or Selected vehicles

3.33.5.4. Last follow-up remarks & Date

3.33.5.5. For SO the Assigned SO name will not be visible.

3.33.6. New car showroom

3.33.6.1. Enquiry details

3.33.6.1.1. Enquiry Type, Enquiry number, Date Enquiry status, SO

3.33.6.2. Customer Details

3.33.6.2.1. Customer Name(Title, First Name, Last name & Middle name)

3.33.6.2.2. Mobile Number

3.33.6.3. Vehicle information

3.33.6.3.1. New node

3.33.6.3.2. Shortlisted or Selected vehicles

3.33.6.4. Last follow-up remarks & Date

3.33.6.5. For SO the Assigned SO name will not be visible.

3.33.7. New car dropped

3.33.7.1. Customer Details

3.33.7.1.1. Customer Name(Title, First Name, Last name & Middle name)

3.33.7.1.2. Mobile Number

3.33.7.2. New car Enquiry details

3.33.7.2.1. Enquiry No., Date, Status, SO

3.33.7.3. Enquiry details

3.33.7.3.1. Enquiry Type, Enquiry number, Date Enquiry status, SO

3.33.7.4. Last follow-up remarks & Date

3.33.7.5. Vehicle information

3.33.7.5.1. Shortlisted or Selected vehicles

3.33.7.6. New car dropped enquiries to be checked for last 1 to 2 days, will be filtered by the last follow-up remarks (To be defined by STL)

3.33.7.6.1. Pre-defined dropped enquiry reasons

3.33.7.7. There will be standard remarks selection will be given for STL.

3.33.7.8. STL can view new car drop enquiry list for month only (last 30 days).

3.33.7.9. Pre-defined dropped enquiry reasons

3.33.7.9.1. OUT OF BUDGET

3.33.7.9.2. LONG WAITING PERIOD/NEED IMMEDIATE DELIVERY

3.33.7.9.3. HIGH DISCOUNT EXPECTED

3.33.8. Others

3.33.8.1. on click (Dropdown will show other types)

3.33.8.1.1. Exchange Mela

3.33.8.1.2. U-Car Dropped

3.34. 7.4 Buyer Enquiry allocations

3.34.1. List available for STL

3.34.2. Allocation of SO can be done by STL

3.34.3. Enquiry source type

3.34.3.1. All

3.34.3.2. Walk-In/ Field Enquiry

3.34.3.3. Web

3.34.3.4. Tele-In

3.34.3.5. Print Adv. (Print Advertise)

3.34.3.6. New car showroom

3.34.3.7. New car Dropped

3.34.3.8. Others

3.34.3.9. Exchange Mela

3.34.3.10. U-Car Dropped

3.34.4. BuyerEnquiry List

3.34.4.1. The new Walk-in / Field, Tele-In,Print Adv., Exchange Mela, New Car showroom

3.34.4.2. Enquiries created by SO will be visible to STL for information

3.34.4.3. Web Enquiries

3.34.4.3.1. These inquiries will be available once created in the UCTDMS system.

3.34.4.3.2. When a new web enquiry gets created, STL will get notification as information.

3.34.4.3.3. When STL view the new Web Enquiries, the list will be visible, and allocation for the same can be done.

3.34.4.3.4. Action

3.34.5. New car Dropped & U-Car Dropped (for STL)

3.34.5.1. Customer Details

3.34.5.1.1. Customer Name(Title, First Name, Last name & Middle name)

3.34.5.1.2. Mobile Number

3.34.5.2. New car Enquiry details

3.34.5.2.1. Enquiry No., Date, Status, SO (New car details if new car dropped)

3.34.5.3. Enquiry details

3.34.5.3.1. Enquiry Type, Enquiry number, Date Enquiry status, SO

3.34.5.4. Vehicle Information

3.34.5.4.1. Make, Model, Year & Registration number (Shortlisted or Selected Vehicles)

3.34.5.4.2. Shortlisted or Selected vehicles

3.34.5.5. Last follow-up remarks & Date

3.34.5.5.1. STL will review the enquiry list

3.34.5.6. Action

3.34.5.6.1. STL review Customer data details

3.35. 7.4.1 Self-Allocation by SO

3.35.1. If SO gets any walk-in customer or any customer details are forwarded to SO

3.35.1.1. SO search by mobile number or tried to create a new buyer enquiry

3.35.1.1.1. If new buyer enquiry already created in system and not allocated to any SO

3.35.2. Action

3.35.2.1. SO Search with Mobile number or tries to create a new buyer enquiry with customer mobile number

3.35.2.1.1. If If buyer enquiry not allocated to SO

3.36. 7.4.2 Duplicate Enquiry creation

3.36.1. If existing enquiry found & allocated or not allocated to any SO

3.36.1.1. SO has option to cancel & create new buyer enquiry

3.36.1.1.1. If duplicate buyer enquiry

3.37. 7.4.3 Multiple STL case

3.37.1. If multiple STL in same dealer location

3.37.1.1. Enquiry allocation engine

3.37.1.1.1. Help to allocate Enquiry one by one to available STL

3.38. 7.5 Transfer of Buyer Enquiry

3.38.1. Available for STL on menu

3.38.1.1. STL can select SO to transfer enquiries

3.38.1.1.1. Once STL selects SO, all his/her open enquiries will be listed

3.38.1.1.2. Check box will be there to select all the listed enquiry

3.38.1.1.3. Each buyer enquiry also will have check box to select individual

3.38.1.1.4. Mandatory input

3.38.1.1.5. STL can transfer enquiries between team members only

3.38.1.1.6. Actions

4. Refurbishment

4.1. 5.1.Refurbishment

4.1.1. Refurbishment module enables RFC (Refurbishment Co-ordinator) to perform Retail eligibility decision of procured vehicles

4.1.2. Allows to do

4.1.2.1. Re-Classification

4.1.2.2. create Refurbishment request

4.1.2.3. view its approval status

4.1.3. Prior retail eligibility decision RFC need to review Valuation and update the valuation.

4.1.4. UCM (Used car Manager) can review submitted refurbishment request and follow approval process: UCM will approve the request

4.2. 5.1.1. RFC (Refurbishment Coordinator) Menu

4.2.1. Dashboard:Refer to Dashboard

4.2.2. Procured List:Will show the vehicles which are procured and having retail classification

4.2.3. Valuation list : Will show the procured vehicle’s valuation list.

4.2.4. Retail Eligible list: will show the list of vehicles, whose retail eligible decision already made

4.2.5. RF request Status : will show the list of Refurbishment request which are created and its status of approval / rejection.

4.2.6. RF Tracker:will show the vehicle list which all the tracking details of RF process.

4.2.7. Notification: will show list of all notifications

4.2.8. Logout : User can logout form the application.

4.3. 5.1.2.UCM (Used Car Manager) Menu

4.3.1. RF Request Status: will show the list of Refurbishment request which are created by RFC, UCM need to review and follow approval process. P.S : UCM menu and RFC menu have common items

4.4. 5.2. Procured List

4.4.1. Procured vehicles classified under retail will be available in procured vehicle list. This list will be available to RFC and UCM.

4.4.1.1. RFC

4.4.1.1.1. RFC will have actions associated

4.4.1.2. UCM

4.4.1.2.1. UCM will have this list available as view only

4.4.2. Procured list will be accessible from

4.4.2.1. Menu

4.4.2.2. Dashboard

4.4.3. Procured list have day wise filter/ buttons

4.4.3.1. 2 Days: this will be default selection applied and will show procured list of last two days.

4.4.3.2. 5 Days: this will show procured list of last 5 days

4.4.3.3. 10 Days: this will show procured list of last 10 days.

4.4.3.4. Select Date: this will open a pop up where user can select the date range which will be up to last 3 months (Current date –90 days).

4.4.3.4.1. Date range can be extended to 1 Year.

4.4.4. Procured list will show the list in order of the procured date descending order

4.4.4.1. Search could be done for the specific vehicle by input of registration number.

4.4.4.1.1. The searched vehicle record if found then will be shown as list item

4.4.4.2. Each list item will show the details like

4.4.4.2.1. Make, Model, Year, Color& Registration number

4.4.4.2.2. Purchase Number, Purchase date & Purchase price

4.4.4.2.3. Valuation Number, Valuation level and PO name

4.4.4.3. Filters will be

4.4.4.3.1. PO

4.4.4.3.2. Pending RFC Valuations

4.4.4.3.3. Make –Model

4.4.5. User actions

4.4.5.1. Retail eligibility decision button allows RFC to make retail eligibility decision

4.4.5.1.1. Prior retail eligibility decision, RFC need to save valuation of the vehicle.

4.4.5.1.2. If there is valuation entry saved by RFC in that case the valuation button will be shown as Green Color.

4.4.5.1.3. If there is no valuation entry saved by RFC

4.4.5.2. Valuation button allows

4.4.5.2.1. View Valuation summary

4.4.5.2.2. Start valuation process

4.5. 5.3.Valuation List(RFC Valuation)

4.5.1. Valuation list will be there for the procured vehicles (List is accessible from Menu )

4.5.1.1. Procured vehicles valuations

4.5.1.2. Valuation created / updated by RFC

4.5.2. Valuation list have day wise filter/ buttons will be arranged

4.5.2.1. 2 Days: this will be default selection applied and will show procured list of last two days.

4.5.2.2. 5 Days: this will show procured list of last 5 days

4.5.2.3. 10 Days: this will show procured list of last 10 days.

4.5.2.4. Select Date: this will open a pop up where user can select the date range which will be up to last 3 months (Current date –90 days).

4.5.2.4.1. Date range can be extended to 1 Year.

4.5.3. Valuation list will show the list in order of the procured date descending order

4.5.3.1. Search could be done for the specific vehicle by input of registration number.

4.5.3.1.1. The searched vehicle record if found then will be shown as list item

4.5.3.2. Each list item will show the details like

4.5.3.2.1. Make, Model, Year, Color& Registration number

4.5.3.2.2. Valuation Number, Valuation level and PO name

4.5.3.2.3. Purchase Number, Purchase date & Purchase price

4.5.3.2.4. RFC Valuation status (Pending / updated)

4.5.3.3. Filters will be

4.5.3.3.1. PO name

4.5.3.3.2. RFC Valuations status

4.5.3.3.3. Make –Model

4.5.3.4. Valuation list will be available to

4.5.3.4.1. RFC

4.5.3.4.2. UCM

4.5.3.5. User Actions:

4.5.3.5.1. RFC can view

4.6. 5.4.Retail Eligibility Decision

4.6.1. Made by RFC, Retail Eligibility Decision screen consists of :

4.6.1.1. Vehicle specific details like

4.6.1.1.1. Registration Number

4.6.1.1.2. Purchase number

4.6.1.1.3. Purchase date

4.6.1.1.4. Vehicle make

4.6.1.1.5. Model

4.6.1.1.6. Year and valuation level.

4.6.1.2. Retail Eligibility check list parameters will be derived from the valuation data

4.6.1.2.1. Data / Documents captured for Valuation will help in deciding the Retail eligibility check list parameters

4.6.1.3. Each check list will have three states

4.6.1.3.1. Not applicable

4.6.1.3.2. Yes

4.6.1.3.3. No

4.6.1.4. Retail Eligible will be selected true by default.

4.6.1.5. No RF Required will be selected false as by default.

4.6.1.6. Wrong buy will be selected false as by Default.

4.6.1.6.1. This will be used to specify vehicle as wrong buy.

4.6.2. User actions

4.6.2.1. Retail eligibility check list parameter can be clicked / tapped then it will be enabled and true.

4.6.2.2. If the parameter is clicked/ tapped two time, then it will be having value false.

4.6.2.2.1. When the value is false then popup will be visible for remarks entry.

4.6.2.3. Retail eligible input is clicked to false value will show two input values. Both inputs will be mandatory

4.6.2.3.1. Wholesale Eligible Reason: dropdown input for wholesale reason.

4.6.2.3.2. Remarks: text input value.

4.6.2.4. No RF Required input is clicked to true value will show two input values. Both inputswill be mandatory

4.6.2.4.1. No RF Required Reason: dropdown input for reason

4.6.2.4.2. Remarks: text input value.

4.6.2.5. Wrong buy input is clicked true value will show one input value

4.6.2.5.1. Remarks: Text input value for Wrong buy remarks.

4.6.2.6. Save button click will save the retail eligibility decision for the specific vehicle

4.6.2.6.1. Retail eligible input is false in that case the vehicle retail eligibility decision is false and that will not be further processed as retail vehicle

4.6.2.6.2. If No RF Required is false in that case the vehicle will require refurbishment

4.6.2.6.3. In case of No RF Required is true in that case the vehicle will not require refurbishment and ready for display

4.6.2.6.4. When Retail eligible input is true, and No RF required is false, save button will prompt user to create a new refurbishment request for vehicle.

4.6.2.6.5. Once retail eligibility decision is made and saved the vehicle will be removed from procured list

4.6.2.7. Vehicle Reclassification button click will show vehicle reclassification screen.

4.7. 5.4.1.Vehicle Reclassification:

4.7.1. Vehicle reclassification screen allows user to reclassify the vehicle to Retail to wholesale.

4.7.2. This screen will be open from retail eligibility decision screen.

4.7.3. Vehicle re classification screen will have following information and inputs

4.7.3.1. Vehicle specific details like

4.7.3.1.1. Registration Number

4.7.3.1.2. Purchase number

4.7.3.1.3. Purchase date

4.7.3.1.4. Vehicle make & Model

4.7.3.1.5. Year and valuation level

4.7.3.2. Classification Type is dropdown selection which have values

4.7.3.2.1. Retail (Default)

4.7.3.2.2. Wholesale

4.7.3.3. Classification Reason is dropdown selection.

4.7.3.4. When Classification type is selected to value Wholesale then two input fields will be enabled.

4.7.3.4.1. Wholesale reason is dropdown selection

4.7.3.4.2. Remarks is text input value.

4.7.3.5. User Actions

4.7.3.5.1. User can select the classification type and input values.

4.7.3.5.2. Save button click will save the reclassification of the value.

4.7.3.5.3. If the vehicle is reclassified as wholesale in that case it will be removed from procured & retail eligible list

4.8. 5.5.Retail Eligible List

4.8.1. The vehicles retail eligibility decision is saved then the vehicle will be available in retail eligible list

4.8.1.1. This will be available to

4.8.1.1.1. RFC

4.8.1.1.2. UCM

4.8.2. Retail Eligible List will be open

4.8.2.1. Menu

4.8.2.2. Dashboard

4.8.3. Retail eligible list have day wise filter/ buttons will be arranged

4.8.3.1. 2 Days: this will be default selection applied and will show retail eligible list of last two days.

4.8.3.2. 5 Days: this will show retail eligible list of last 5 days

4.8.3.3. 10 Days: this will show retail eligible list of last 10 days.

4.8.3.4. Select Date: this will open a pop up where user can select the date range which will be up to last 3 months (Current date –90 days).

4.8.3.4.1. Date range can be extended to 1 Year.

4.8.4. Retail Eligible List will show the list in order of the Retail eligibility decision date in descending order.

4.8.4.1. Search could be done for the specific vehicle by input of registration number.

4.8.4.2. The searched vehicle record if found then will be shown as list item

4.8.4.3. Each list item will show the details like

4.8.4.3.1. Make, Model, Year, Color& Registration number

4.8.4.3.2. Purchase Number, Purchase date & Purchase price

4.8.4.3.3. Valuation Number, Valuation level and PO name

4.8.4.3.4. Retail eligibility decision date & RFC Name.

4.8.4.4. Filters will be

4.8.4.4.1. PO

4.8.4.4.2. Pending RF Request

4.8.4.5. User Actions:

4.8.4.5.1. Retail eligibility decision button allows users to view/edit retail eligibility decision [RFC and UCM].

4.8.4.5.2. Create RF button click will open refurbishment request form which allows user to create a new refurbishment request

4.9. 5.6.Refurbishment Request

4.9.1. Refurbishment Request screen allows user to create / view the refurbishment request.

4.9.1.1. This screen will be open from retail eligible list or when retail eligibility decision is saved.

4.9.1.1.1. Refurbishment request will be created for those vehicles whose retail eligibility decision is already made with retail eligible and RF is required (No RF required is false)

4.9.2. Create refurbishment request screen

4.9.2.1. Vehicle specific details

4.9.2.1.1. Registration Number

4.9.2.1.2. Vehicle make,

4.9.2.1.3. Model

4.9.2.1.4. Year

4.9.2.2. PO Name and RFC Name

4.9.2.3. Refurbishment request details

4.9.2.3.1. Category: dropdown will have values GS & BP

4.9.2.3.2. Job Category

4.9.2.3.3. RF Cost & Job description will be input value.

4.9.2.3.4. Service at & Send to workshop will be dropdown inputs

4.9.2.4. Filter for this list will be PO & RF Request status.

4.9.2.5. Refurbishment request details will be derived from the valuation. During RFC valuation the information for Category, service a & Send to workshop will defined.

4.9.2.6. While creating refurbishment request RFC can change the values if needed otherwise it will be populated from inputs of the RFC saved valuation.

4.9.2.7. When new refurbishment request is created in that case all refurbishment details will be available and selected.

4.9.2.8. Once Refurbishment request is approved by UCM, RFC will have option to edit the sub request and add actual RF related details.

4.9.2.9. Actual RF data input

4.9.2.9.1. Job Card number

4.9.2.9.2. Job Card Start Date

4.9.2.9.3. Actual RF Cost

4.9.2.9.4. Job card close / Complete date

4.9.2.10. RF request wise close date and total actual RF cost related input to-be defined in the application that will update the respective fields in RF request UCTDMS.

4.9.2.11. Delete RF request option to be provided, there will be delete button which will allow to delete the RF Request. If the RFC created Refurbishment request, the request isnot approved fully or partially by RFC in that case the delete will be allowed.

4.9.2.12. RFC can edit the RF request and remove sub Request as well.

4.9.3. User Actions

4.9.3.1. RFC can un-select refurbishment request detail during creating new RF request.

4.9.3.2. Add button will show popup screen where user can input RF request details. Click on save will add a new record of refurbishment request details

4.9.3.3. The RF sub request data will be fetched from valuation, any addition that will be additional sub request from RFC. New added additional sub request will be shown as different back Color–Grey Color.

4.9.3.4. RFC can un-select RF request detail during creating new RF request or while updating existing RF request (if it is not approved by UCM).

4.9.3.5. Save button will save the refurbishment request

4.9.3.5.1. Once the RF Request is saved, RF Request number and RF request date will be visible.

4.9.3.5.2. On save of the RF request, a notification will be sent to UCM for approvals

4.9.3.5.3. Once RF request is approved then actual refurbishment process will start on vehicle.

4.10. 5.7.Refurbishment Request Approval

4.10.1. Refurbishment request which are created by RFC will be available to UCM for approvals.

4.10.2. Refurbishment request list can be open from

4.10.2.1. Menu

4.10.2.2. Dashboard

4.10.3. From RF Request notification tap will open the specific RF request for approvals

4.10.4. RFC create refurbishment request will be available to UCM for approval

4.10.5. Refurbishment request list have day wise filter/ buttons wil be arranged like followings,

4.10.5.1. 2 Days: this will be default selection applied and will show Refurbishment request list of last two days.

4.10.5.2. 5 Days: this will show Refurbishment request list of last 5 days

4.10.5.3. 10 Days: this will show Refurbishment request list of last 10 days.

4.10.5.4. Select Date: this will open a pop up where user can select the date range which will be up to last 3 months (Current date –90 days).

4.10.5.4.1. Date range can be extended to 1 Year.

4.10.6. Retail Eligible List will show the list in order of the Refurbishment request date in descending order.

4.10.7. Refurbishment request list screen will have following information of each item

4.10.7.1. Vehicle specific details

4.10.7.1.1. Registration number

4.10.7.1.2. Vehicle Make, Model, Year

4.10.7.2. RF Request Number & RF Request Date.

4.10.7.3. RFC name and PO name

4.10.7.4. Filter for this list will be PO,RF Request status & Search by Registration no

4.10.8. User Actions

4.10.8.1. UCM can click / tap on the specific request,

4.10.8.1.1. View RF request screen will be visible.

4.10.8.2. On RF Request UCM have option of all approval or all rejection.

4.10.8.3. When UCM click on Green tick button it will approve all the sub request in the RF request

4.10.8.4. If UCM click on Red cross button it will reject all the sub request, while rejecting the popup will be open to take input of rejection remark.

4.10.8.5. UCM can approve or reject single / multiple sub requests of single RF request.

4.10.8.6. Swap right will reject specific sub request, prior rejection a new popup screen will open for accepting input value for rejection remarks.

4.10.8.7. There will be three state check boxes for sub request approval instead of swipeLeft and right

4.10.8.7.1. Red cross button

4.10.8.7.2. Green tick button

4.10.8.7.3. Empty box

4.10.8.8. Save button, after approval / rejections RF request need to be save by UCM

4.10.8.9. Approval / Rejection will send notification to RFC.

4.11. 5.8.Refurbishment Request Status

4.11.1. It will be available in Refurbishment request list which will show all the created RF requests with its approval status

4.11.2. Refurbishment request list can be opened from

4.11.2.1. Menu

4.11.2.2. Dashboard

4.11.3. RF Request notification tap will open the specific RF request to view its status if any action for UCM

4.11.4. List of RF request will be visible in this screen, the list have day wise filter / button.

4.11.4.1. The list will show created RF requests, the filed parameters and filters will be same as section 6.7(Valuation Round 2 :Left side full inspection

4.11.5. Request status will be depicted as background Color of the list item.

4.11.5.1. Approval status to be shown as text status as well

4.11.5.1.1. White Color

4.11.5.1.2. Green Color.

4.11.5.1.3. Orange Color

4.11.5.1.4. Red Color

4.11.6. Filter for this list will be PO,RF Request status & Search by Registration no

4.11.7. User Actions

4.11.7.1. RFC can click / tap on the specific request; view RF request screen will be visible.

4.11.7.2. RF Request screen will show approved / rejected sub request.

4.11.7.3. In case of rejected sub request, rejection remarks related icon will be available.

4.11.7.3.1. On click of the icon will show rejection remarks

4.11.7.4. If any request is approved in that case RFC cannot edit it’s any sub requests.

4.11.7.4.1. If the sub request is rejected in that case RFC can rectify and submit again for approval

4.11.7.5. Save / update of RF request will send notification to UCM for approvals.

4.12. 5.9.Refurbishment Tracker

4.12.1. Refurbishment tracker will be available to view / track all the status of the procured vehicles whose retail eligibility decision is made

4.12.2. Refurbishment tracker can be open from

4.12.2.1. Menu

4.12.2.2. Dashboard

4.12.3. Refurbishment Tracker will be visible in this screen with day wise filter / button.

4.12.3.1. The list of vehicles will show with all stage wise status, the filed parameters and filters will be same as section 6.7

4.12.3.2. Filter for this list will be

4.12.3.2.1. PO

4.12.3.2.2. Make, Model

4.12.3.2.3. Search by Registration no

4.12.3.3. Tracker will show each vehicle with following details

4.12.3.3.1. Procurement number & date

4.12.3.3.2. Refurbishment request number, Date & Sub request count

4.12.3.3.3. Request approval date & sub request count which are approved.

4.12.3.3.4. Job Card number & created date.

4.12.3.3.5. Job Card number & close date

4.12.3.3.6. Refurbishment request close date

4.12.3.4. *For one Refurbishment request there is possibility to have multiple Job card numbers.(Particularly non toyota vehicles suppose two places we are giving for repair for different work)

4.12.3.4.1. Latest Job card number ->click

4.12.3.4.2. Latest Date

4.12.3.5. Showing Job card number and date depends on data availability in UCTDMS system.

4.12.3.5.1. If the Job card data linking is available

4.12.3.6. When there is non-Toyota vehicle or other workshop

4.12.3.6.1. When there is non -Toyota vehicle or other workshop

4.12.4. User Actions:

4.12.4.1. RFC / UCM can click / tap on

4.12.4.1.1. The specific record and view details like RF request and its approval status

4.12.4.1.2. Specific record’s job card number to view all job cards numbers for the request.

4.12.5. System Integrations:

4.12.5.1. UCTDMS

4.12.5.1.1. Procured vehicle list

4.12.5.1.2. Valuation

4.12.5.1.3. Retail eligibility decision

4.12.5.1.4. Vehicle Re-classification

4.12.5.1.5. Refurbishment requests & approvals

4.12.5.1.6. RF Actual / Job card data

5. Valuation

5.1. 6.1 Valuation enables PO to perform valuation for vehicle.

5.1.1. Trigger points for accessing Valuation

5.1.1.1. Menu

5.1.1.1.1. Valuation landing screen

5.1.1.1.2. Service History

5.1.1.1.3. Authenticity Check

5.1.1.2. Enquiry

5.1.1.2.1. Action

5.2. 6.2 Valuation Round 1 & Round 2: Functional check

5.2.1. Valuation Process starts with initial inspection and functional check inside the cabin

5.2.2. Screen Features

5.2.2.1. Functional Check will have five categories. Each will be a collapsible control

5.2.2.1.1. Steering

5.2.2.1.2. Electrical

5.2.2.1.3. Transmission

5.2.2.1.4. Engine

5.2.2.1.5. Others

5.2.2.2. Initial Check: Here, along with fields, hint and button “OBD Port” will be displayed to check the OBD port of the vehicle

5.2.2.2.1. Tapping on it will open the popup showing the location of OBD in car. This will be unique based on the “Make” of the vehicle

5.2.2.2.2. Initial Check includes following check

5.2.2.3. Power Windows

5.2.2.3.1. Power Windows check will have two toggle buttons to select the front / rear manual and power windows

5.2.2.3.2. By default, it will be manual

5.2.2.4. Vehicle Features

5.2.2.4.1. Applicable based on make & model

5.2.2.4.2. It will be visible by tapping (single tap / double tap) on the respective checkpoint.

5.2.2.4.3. PO can check/uncheck the same to determine whether feature is there in the vehicle or not.

5.2.2.4.4. If Functional Checkpoint has dependency on feature, then the checkpoint will be visible only if the respective feature is applicable to model.

5.2.2.4.5. Features which do not have associated functional checkpoints will be displayed in the end under “Features” accordion (below others) as checkboxes.

5.2.2.5. Following checkpoints have “Non-OE” button along with features. It will be visible when the checkpoint is tapped (single tap / double tap). If Non-OE is selected, then it will appear in accessories section in Complete Valuation screen.

5.2.2.5.1. Power Windows

5.2.2.5.2. Music System

5.2.2.5.3. Navigation System

5.2.2.5.4. Reverse Camera

5.2.2.5.5. Reverse Sensor

5.2.2.5.6. Alloy Wheels

5.2.2.6. Action

5.2.2.6.1. Single tap: Single tap on item will display correct icon and will be considered as available and OK.

5.2.2.6.2. Double tap: Double tap on item will display default (cross) icon and will be considered as not ok. Also, it will display

5.2.2.6.3. Description: Box or standard comments to be selected. Dropdown will also have blank section, whatever is written there will be considered as description for defect.

5.2.2.6.4. Large icon (only if small and large are different) to select large value for defect

5.2.2.6.5. Image: If Good or Bad Image will be available for the function then tapping on it will open a popup showing Good and Bad Pictures.

5.2.2.6.6. Video: If video is available for the functional check then tapping on it will open video in a popup.

5.2.2.6.7. By default, for “Not OK”, small value will be considered

5.2.2.6.8. “All OK” will be visible in all categories except Initial Check. If its checked then all functions for the category will be considered as OK.

5.2.2.6.9. “Next” button: Tapping on “Next” button will open a popup in the screen showing hint: “Please open Bonnet Hood, Trunk Hood & Fuel Lid”.

5.2.2.7. Round 1

5.2.2.7.1. Walk around the car to lock for Panel gaps, Color difference & Major damages

5.2.2.8. Round 2

5.3. 6.3 Valuation Round 2: Dashboard: Interior Inspection

5.3.1. Following components will be checked for Round 2 Dashboard

5.3.1.1. Dashboard

5.3.1.2. Steering

5.3.1.3. Glove Box

5.3.1.4. Gear Knob

5.3.1.5. Center Console

5.3.2. There will be specific button for each components by which user can click and mention the notes of damages

5.3.3. Action

5.3.3.1. Damage Info

5.3.3.1.1. Toggle button to see the damage information. Tapping on it will open a popup, showing damage information

5.3.3.1.2. Tapping on it will open a popup for the particular part damage capture

5.3.3.2. PO can specify the damage by selecting respective option and tapping on close button in popup.

5.3.3.2.1. Damage values will be toggle button. Tapping it will select the damage value and tapping again will remove the same

5.3.3.2.2. X2, X3 damages are mandatory to have at least one photograph.

5.3.3.3. Photograph can be captured by tapping on “Upload image” icon.

5.3.3.3.1. Once image is uploaded, it will be shown as thumbnail

5.3.3.4. “Prev” and “Next” button to go back to previous (valuation Round 1 & Round 2: Functional Check) and next (Valuation Round 2: Right Side Full Inspection) screens respectively.

5.3.3.5. Inspection Video (icon): Tapping on it will open inspection video in popup for functional check of Black & White Smoke

5.3.3.6. Functional Check: Black Smoke & White Smoke. It will be same as other functional check

5.4. 6.4 Valuation Round 2: Right Side Full Inspection

5.4.1. Following items (components) will be checked for Round 2: Right Side Full Inspection

5.4.1.1. Front Door

5.4.1.2. Rocker Panel

5.4.1.3. Rear Door

5.4.1.4. Center Floor

5.4.1.5. Rear Fender

5.4.1.6. Rear Wheel House

5.4.2. Actions

5.4.2.1. Single Tap: Single tapping on any item will be considered as OK and will be displayed in green colour.

5.4.2.2. Double Tap: Double tapping on any item will redirect user to that respective sub screen which are described below in sequence

5.4.2.3. “Prev” and “Next” button will be present to go back (Valuation Round 2: Dashboard: Interior Inspection) and forth (Valuation Round 2: Rear Side Full Inspection) respectively

5.4.2.4. Note: Sequence must be followed. PO cannot go to 3 without checking (single tap / double tap) 1 & 2. Also, PO cannot go to next screen without completing all the inspection points.

5.4.3. Components

5.4.3.1. Front Door

5.4.3.1.1. Front Door & Side Frame Inspection

5.4.3.1.2. Inspection Tips: Video (BSI): Tapping on the icon will open the respective video in the popup

5.4.3.1.3. Door Replacement: Same as described above, tapping on icon will open a popup with “RP” as damage value in circle

5.4.3.1.4. Damage Photograph capturing in this case will be optional

5.4.3.2. Front Pillar: Same as described above, tapping on icon will open a popup enabling PO to capture damage value

5.4.3.2.1. Here, the options are Dent, Repaired and Replaced.

5.4.3.2.2. Only Large Damages or Replaced value would be considered for mandatory photograph

5.4.3.2.3. Example for damage value capture in icon: For small dent damage, it will be “D-S”. Center Pillar: Same as Front Pillar.

5.4.3.3. Front Door Inspection: Interior

5.4.3.3.1. Inspection Tips: Video (DRSC): Tapping on the icon will open the respective video in the popup.

5.4.3.3.2. Following Components can be checked for Front Door & Frame Inspection

5.4.3.3.3. “Back” button will only be visible once user taps on second step (Front Door Inspection: Interior)

5.4.3.4. Rocker Panel

5.4.3.4.1. Rocker Panel damage capturing Repaired (R) or Replaced (RP) same as described above. Photo capture is optional

5.4.3.5. Rear Door:

5.4.3.5.1. Rear Door Replacement, Center Pillar & DRSC Check

5.4.3.6. Center Floor

5.4.3.6.1. Center Floor Replacement same as described above for Front Pillar. Photo capturing is non-mandatory.

5.4.3.7. Rear Fender

5.4.3.7.1. Rear Fender Replacement / Repaired Check same as described above for “Rocker Panel”

5.4.3.8. Rear Wheel House

5.4.3.8.1. Rear Wheel House – Dent, Repaired or Damage check. Same as described above for Front Pillar.

5.5. 6.5 Valuation Round 2: Rear Side Full Inspection

5.5.1. Following items (components) will be checked for Round 2: Rear Side Full Inspection

5.5.1.1. Trunk Hood

5.5.1.2. Rear Fender Panels, End Panel & Rear Side Members

5.5.1.3. Rear Floor Panel

5.5.1.4. Rear Cross Member

5.5.2. Actions

5.5.2.1. Single Tap: Single tapping on any item will be considered as OK and will be displayed in green colour

5.5.2.2. Double Tap: Double tapping on any item will redirect user to that respective sub screen which are described below in sequence.

5.5.2.3. “Prev” and “Next” button will be present to go back (Valuation Round 2: Right Side Full Inspection) and forth (Valuation Round 2: Rear Functional Check) respectively.

5.5.2.4. Note: Sequence is non-mandatory here. PO can directly go to 3 from 1 or directly go to next screen

5.5.3. Components

5.5.3.1. Trunk Hood

5.5.3.1.1. Trunk Hood Replacement Inspection: No Images required. Hence, tapping on it will capture the damage as replacement

5.5.3.1.2. Trunk hood video required

5.5.3.1.3. Trunk Hood Inspection

5.5.3.1.4. Rear Inside Panel Inspection

5.5.3.2. Fenders, End Panel & Rear Side Members

5.5.3.2.1. LH Rear Fender

5.5.3.2.2. RH Rear Fender

5.5.3.2.3. End Panel

5.5.3.2.4. LH Rear Side Member

5.5.3.2.5. RH Rear Side Member

5.5.3.3. Rear Floor Panel

5.5.3.3.1. Rear Floor Panel Check for Dent, Repaired and Replaced. Large Damages and Replaced will have mandatory photograph capture

5.5.3.4. Rear Cross Member

5.5.3.4.1. Rear Cross Member Check for Dent, Repaired and Replaced

5.5.3.4.2. Photograph capture is non-mandatory.

5.5.3.4.3. Additional Check (Checkbox) for Chassis / VIN Replaced. This will be shown in valuation summary, detail and history if selected.

5.6. 6.6 Valuation Round 2: Rear Functional Check

5.6.1. Next step in valuation process is Functional Check from Rear Side

5.6.1.1. This will be same as other functional check.

5.6.1.2. Only exception is for “Spare Wheel”.

5.6.1.3. Single Tap means Spare Wheel has good condition which is >50%.

5.6.1.4. Double tap means “<50%”. Description will be available for both the cases.

5.6.1.5. “Prev” and “Next” button will be present to go back (Valuation Round 2: Rear Side Full Inspection) and forth (Valuation Round 2: Left Side Full Inspection) respectively

5.7. 6.7 Valuation Round 2: Left Side Full Inspection

5.7.1. Next step in valuation process is Left Side Full Inspection

5.7.1.1. This will be same as Right Side Full Inspection

5.7.1.2. Sequence is mandatory here same as Right Side.

5.7.1.3. Left Side will be performed in following sequence

5.7.1.3.1. Rear Wheel House

5.7.1.3.2. Rear Fender

5.7.1.3.3. Rear Door

5.7.1.3.4. Front Door

5.7.1.3.5. Rocker Panel

5.7.1.3.6. Roof Panel

5.7.1.4. “Prev” and “Next” button will be present to go back (Valuation Round 2: Rear Functional Check) and forth (Valuation Round 2: Front Full Inspection) respectively.

5.8. 6.8 Valuation Round 2: Front Full Inspection

5.8.1. Front Full Inspection

5.8.1.1. Next step in the valuation process is “Front Full Inspection.”

5.8.1.2. Following items (components) will be checked for Round 2: Front Full Inspection

5.8.1.2.1. Bonnet Hood

5.8.1.2.2. Left Fender

5.8.1.2.3. Right Fender

5.8.1.2.4. Front Frame Parts

5.8.1.2.5. Dash Panel

5.8.1.2.6. Left Wheel House

5.8.1.2.7. Right Wheel House

5.8.1.2.8. Bottom Check

5.8.1.3. Actions

5.8.1.3.1. Single Tap: Single tapping on any item will be considered as OK and will be displayed in green colour.

5.8.1.3.2. Double Tap: Double tapping on any item will redirect user to that respective sub screen which are described below in sequence.

5.8.1.3.3. “Prev” and “Next” button will be present to go back (Valuation Round 2: Left Side Full Inspection) and forth (Valuation Round 2: Inspection Summary & Cost Input) respectively.

5.8.1.3.4. Note: Sequence following is non-mandatory. PO can directly go to 3 from 1 or directly go to next screen.

5.8.1.4. Components

5.8.1.4.1. Bonnet Hood

5.8.1.4.2. Right Front Fender

5.8.1.4.3. Left Front Fender

5.8.1.4.4. Front Frame Parts

5.8.1.4.5. Dash Panel

5.8.1.4.6. Right Front Wheel House

5.8.1.4.7. Left Front Wheel House

5.8.1.4.8. Bottom Check

5.9. 6.9 Valuation Round 2: Inspection Summary & Cost Input

5.9.1. Inspection Summary & Cost Input

5.9.1.1. All functional, Interior and Frame damages will be displayed here in summary screen.

5.9.1.2. PO can see the damages and input the respective RF cost.

5.9.1.3. Action

5.9.1.3.1. Damages: Tapping on the button will open a popup showing captured photographs.

5.9.1.3.2. Functional Section

5.9.1.3.3. Interior Section

5.9.1.3.4. Frame section

5.9.1.3.5. “Next” button: Tapping on “Next” button will redirect PO to next screen – “Round 3: Exterior Check”.

5.9.1.3.6. “Prev” button: Tapping on “Prev” button will redirect PO to Previous screen – “Round 2: Front Full Inspection”.

5.9.1.3.7. IF RFC is editing valuation then there will be two additional input from RFC here

5.10. 6.9 Valuation Round 2: Inspection Summary & Cost Input

5.10.1. Inspection Summary & Cost Input

5.10.1.1. All functional, Interior and Frame damages will be displayed here in summary screen.

5.10.1.2. PO can see the damages and input the respective RF cost.

5.10.1.3. Action

5.10.1.3.1. Damages: Tapping on the button will open a popup showing captured photographs.

5.10.1.3.2. Functional Section

5.10.1.3.3. Interior Section

5.10.1.3.4. Frame section

5.10.1.3.5. “Next” button: Tapping on “Next” button will redirect PO to next screen – “Round 3: Exterior Check”.

5.10.1.3.6. “Prev” button: Tapping on “Prev” button will redirect PO to Previous screen – “Round 2: Front Full Inspection”.

5.10.1.3.7. IF RFC is editing valuation then there will be two additional input from RFC here

5.11. 6.10 Valuation Round 3: Exterior Check

5.11.1. Next step in valuation process will be “Exterior Check”.

5.11.1.1. It will be done in following sequence: Right, Rear, Left and Front.

5.11.1.2. By tapping on next button respective screens will be accessed

5.11.2. If Door Replacement is captured in Round 2, it will come here as editable input

5.11.2.1. Repaired, Replaced and Damaged will be represented in different colours

5.11.3. Actions

5.11.3.1. Windshield Check Popup will be visible while arriving at exterior check.

5.11.3.1.1. A popup will display following information:

5.11.3.2. Damage Info

5.11.3.2.1. Tapping on the “Damage Info.” Button will display a popup showing damage information.

5.11.3.2.2. For Doors, Replaced (RP) and Repainted (R/P) input will be captured along with P, B, X and photographs. For replaced, photograph is mandatory.

5.11.3.2.3. Paint Gauge input (manual)

5.12. 6.11 Valuation Round 3: Inspection Summary and Cost Input (Exterior)

5.12.1. Next step is to provide input for exterior damages

5.12.2. “Prev” and “Next” buttons will be present to go back (Round 3: Exterior Check – Front) and forth (Round 3: Test Drive Functional Check).

5.12.3. Action

5.12.3.1. For each damage, there will be damage button

5.12.3.1.1. Damage button

5.12.3.2. Damage value

5.12.3.2.1. Damage input captured which can be changed by tapping on the button

5.12.3.3. RF Cost

5.12.3.3.1. RF cost input for each damage

5.12.3.4. Common Remarks

5.12.3.4.1. Common Remarks section for capturing remarks

5.13. 6.12 Valuation Round 3: Test Drive Functional Check

5.13.1. Next step is to provide input captured during test drive.

5.13.2. Action

5.13.2.1. All Ok – Same as other functional check.

5.13.2.2. Single Tap and Double Tap– Same as other functional check

5.13.2.3. If Not OK, then RF Cost input will be captured along with capturing description

5.14. 6.13 Valuation Completion

5.14.1. Valuation Completion screen, PO will view valuation summary, input required details and complete valuation

5.14.2. Screen Features

5.14.2.1. Valuation Summary

5.14.2.1.1. Valuation Summary will contain following fields

5.15. 6.14.Valuation List

5.15.1. Valuation List will have two tabs

5.15.1.1. Pending Valuations

5.15.1.2. Completed Valuations

5.16. 6.14.1.Pending Valuations

5.16.1. It displays

5.16.1.1. Vehicle Reg. No.

5.16.1.2. Valuation Date & Time

5.16.1.3. Vehicle Make

5.16.1.4. Model

5.16.1.5. Suffix & Year

5.16.1.6. Customer Name,

5.16.1.7. Mobile No.

5.16.1.8. Email Address

5.16.1.9. Valuation Level

5.16.1.10. Total RF Cost

5.16.1.11. Tapping on item will redirect PO to the screen where he left off

5.16.1.12. If he will be redirected to “Complete Valuation” then following changes will appear on the screen

5.16.1.12.1. “Complete Valuation” button will have text as “Update Valuation”

5.16.1.12.2. “Edit” button will be there in the menu bar at right hand side to edit the valuation.

5.16.2. Two types of valuations will come in pending category

5.16.2.1. Offline (in application storage -not saved to cloud)

5.16.2.2. Saved but not synced to UCTDMS.

5.16.3. Date filters will be there to filter the valuations

5.16.3.1. Current Month (Default Selected)

5.16.3.2. Last 2 months

5.16.3.3. Last month

5.16.3.4. Date Range (Max. 1 year)

5.16.3.5. The list will be displayed in descending order of valuation date & time

5.17. 6.14.2.Completed Valuations

5.17.1. Will display following information

5.17.1.1. Valuation No

5.17.1.2. Valuation Date & Time

5.17.1.3. Duration

5.17.1.4. Vehicle Reg. No

5.17.1.5. Vehicle Make,

5.17.1.6. Model

5.17.1.7. Suffix & Year

5.17.1.8. Customer Name

5.17.1.9. Mobile No.

5.17.1.10. Email Address

5.17.1.11. Valuation Level

5.17.1.12. Total RF Cost

5.17.1.13. Latest Offered Price

5.17.1.14. Tapping on item will redirect PO/PTL to the valuation detail screen

5.17.2. PO will see only his latest valuations

5.17.3. RFC will see only his valuation

5.17.4. In History, show all valuations

5.17.5. Active Enquiry valuations need to be considered. When enquiry is dropped, all valuations will be scrapped if enquiry is dropped

5.17.6. The list will be displayed in descending order of valuation date & time

5.17.7. Date filters will be there to filter the valuations

5.17.7.1. Current Month (Default Selected)

5.17.7.2. Last 2 months

5.17.7.3. Last month

5.17.7.4. Date Range (Max. 1 year)

5.18. 6.14.2.1 Valuation Detail

5.18.1. Valuation Detail screen will have following components

5.18.1.1. Edit button

5.18.1.1.1. Tapping on edit button will redirect PO to the valuation process screen Round 1

5.18.1.2. Share button

5.18.1.2.1. Tapping on share button will enable PO to share report with seller via WhatsApp / email.

5.18.1.3. Valuation Info

5.18.1.3.1. Valuation No., PO Name, PO Mobile No., PTL Name, PTL Mobile No., Location, Date & Time, Duration

5.18.1.4. Customer Info

5.18.1.4.1. Name, Mobile No., Email

5.18.1.5. Vehicle Info

5.18.1.5.1. Reg. No., Make, Model, Suffix, Year, Colour, Fuel Type, Transmission, Mileage, Engine No., VIN, No. of Owners, Taxi to Private (if yes), Migrated (if yes), Ex showroom price, Hypothecated (if yes)

5.18.1.6. Traffic Violation Info

5.18.1.6.1. Fine Amount & Description

5.18.1.7. RC & Insurance Info.

5.18.1.7.1. RC & RC Type, Duplicate RC, Insurance Type, Insurance Expiry (Month & Year), Insurance Company

5.18.1.8. Valuation Summary

5.18.1.8.1. Exterior, Interior, Function, Frame and Final Score

5.18.1.8.2. Damage Comments for each section

5.18.1.8.3. Damage Photographs for each section (Tapping on it will open a screen showing captured photographs with the facility to upload new ones – will be considered as general pics)

5.18.1.8.4. Valuation Level, Total RF Cost, Standard RF Cost, History (button- to view valuation history)

5.18.1.8.5. Exterior Pics button (Tapping on it will open screen showing exterior photographs)

5.18.1.9. Vehicle Check

5.18.1.9.1. Captured Remarks: Accidental, Flooded, Total Loss, Stolen Vehicle, Chassis / VIN Replaced, Odometer Tempering, Odometer Changed At

5.18.1.10. Vehicle Features

5.18.1.10.1. Accordion Control to expand / collapse

5.18.1.11. Vehicle USP

5.18.1.12. Negotiation

5.18.1.12.1. Same as seller enquiry

5.19. 6.14.2.2 Valuation History

5.19.1. Valuation History will show history of defect & RF Cost with information like

5.19.1.1. Valuation Date & Time

5.19.1.2. Duration

5.19.1.3. Person who did the valuation

5.19.1.4. PTL Remarks (Last negotiation remarks given by PTL for each valuation)

5.19.1.5. Valuation Score

5.19.2. Chassis / VIN Replaced if it is yes

5.20. 6.15 Valuation Appointments

5.20.1. Valuation appointments with filters – All (Default), Today and Week

5.20.1.1. Seller Enquiry No.

5.20.1.2. Valuation Date & Time

5.20.1.3. Vehicle Reg. No

5.20.1.4. Vehicle Make, Model, Suffix and Year

5.20.1.5. Customer Name, Mobile No. and Email Address

5.20.1.6. Edit icon

5.20.1.6.1. Tapping on edit in the list will open Add Appointment screen in edit mode where user can update appointment date & time for the respective appointment

5.20.1.7. Open Valuation

5.20.1.7.1. Tapping on it will open respective valuation in add/edit mode

5.21. 6.15.1 Add Valuation Appointment

5.21.1. Valuation Appointment can be added by searching enquiry based on

5.21.1.1. Customer Name

5.21.1.2. Mobile No

5.21.1.3. Reg. No.

5.21.2. Only 3 months old enquiries will be searched.

5.21.3. Valuation Appointment will be added by defining date & time.

5.21.3.1. Valuation appointment will also be added from follow-up in enquiry with tick mark for valuation

5.22. 6.16 Common Features / General Points

5.22.1. VIN Plate Reading

5.22.1.1. VIN Plate Reading can be done anytime during valuation

5.22.1.1.1. In all screens except the information screen, a popup will be displayed showing VIN number

5.22.1.2. Value Addition (To-be-checked for GMSI & TKM for additional cost of service)

5.22.1.2.1. Based on VIN Number, Vehicle Make, Model, Grade, Suffix and Year can be identified

5.22.2. Features will be based on the excel sheet uploaded in master

5.22.2.1. This will change based on Make & Model (first phase)

5.22.2.1.1. In subsequent phases, it will be based on Make, Model, Suffix & Year.

5.22.3. PO can edit valuation till procurement of the vehicle is done

5.22.4. RFC can edit valuation till retail eligibility decision is made

5.22.5. Valuation Date & Time will be saved / updated in application (offline / cloud) while saving the valuation (Date & Time of save will be considered as valuation date & time)

5.22.5.1. However, it will be updated when it is synced to UCTDMS when valuation number is generated.

5.22.6. For Toyota vehicles, ex showroom price will be fetched from TSA

5.22.7. OBD-II integration will be done via BLE 4.0 Open Stack

5.22.8. If Valuation is done, then Detail Inspection Check will be yes, and Quality Rating will be updated based on valuation score.

5.22.8.1. It cannot be updated by PO.

6. Retail

6.1. 9.1.Retail Vehicle List

6.1.1. Retail Vehicle List enables user to perform following things

6.1.1.1. PDI (Pre Delivery Inspection)

6.1.1.1.1. Updates Document Check the vehicle

6.1.1.1.2. Updates PDI check for the vehicle

6.1.1.2. Delivery

6.1.1.2.1. Update Delivery Date of vehicle

6.1.1.3. Name Transfer

6.1.1.3.1. Coordinate with customer for Name Transfer

6.1.1.3.2. Updates Name Transfer Status

6.2. 9.1.1. PDI

6.2.1. Display the list of vehicles which PDI is pending and completed

6.2.1.1. PDI screen consists of two tabs

6.2.1.1.1. Pending

6.2.1.1.2. Closed

6.2.2. Displayed in ascending order of likely delivery date / delivery date (for closed list)

6.2.2.1. Each item consists of following details

6.2.2.1.1. Reg.No(Vehicle Reg.No)

6.2.2.1.2. Vehicle Details

6.2.2.1.3. Customer Details

6.2.2.1.4. Call Button

6.2.2.1.5. Likely Delivery Date / Delivery Date

6.2.2.1.6. DocumentCheck button

6.2.2.1.7. PDI Check button

6.2.2.1.8. Dealer

6.2.2.1.9. SO Name

6.2.3. System Integrations

6.2.3.1. UCTDMS

6.2.3.1.1. Getting Vehicle Details

6.2.3.1.2. Getting Customer Details

6.2.3.1.3. Getting Likely Delivery Date

6.3. 9.1.2. Delivery

6.3.1. Displays list of vehicles which likely delivery date is in next 10 days

6.3.2. List will be displayed in ascending order of likely delivery date.

6.3.3. Each item in list consists of following details

6.3.3.1. Reg.No(Vehicle Reg.No)

6.3.3.2. Vehicle Details

6.3.3.2.1. Vehicle Make

6.3.3.2.2. Model

6.3.3.2.3. Suffix

6.3.3.2.4. Year

6.3.3.3. Customer Details

6.3.3.3.1. Customer Name

6.3.3.3.2. Mobile No

6.3.3.3.3. Email Address

6.3.3.4. Call button

6.3.3.4.1. Tapping on it will place the call to customer on his mobile number (Mobile Call function will be invoked)

6.3.3.5. Likely Delivery Date

6.3.3.5.1. Likely Delivery Date of the vehicle

6.3.3.6. Delivery Date & Time

6.3.3.6.1. Delivery Date & Time input

6.3.3.6.2. Save button

6.3.3.6.3. Reset button

6.3.4. System Integrations

6.3.4.1. UCTDMS (From Order)

6.3.4.1.1. Getting Vehicle Details

6.3.4.1.2. Getting Customer Details

6.3.4.1.3. Getting Likely Delivery Date

6.4. 9.1.3. Name Transfer

6.4.1. Name Transfer screen will enable user to update the Name Transfer details

6.4.2. Screen is divided into two tabs

6.4.2.1. Pending

6.4.2.1.1. will display a list of vehicles for which delivery note is generated and name transfer is not yet confirmed

6.4.2.2. Closed

6.4.2.2.1. will display a list of vehicles which name transfer is confirmed

6.4.2.2.2. Closed Items will have same fields as open items except call functions and status button.

6.4.3. List will be displayed in ascending order of delivery note date (delivery date)

6.4.4. Following filters are available to filter the screen

6.4.4.1. Current Month (Default Selected)

6.4.4.2. Last Month

6.4.4.3. Last 2 Months

6.4.4.4. Date Range

6.4.4.5. SO (SO Name)

6.4.4.6. PO (PO Name)

6.4.4.7. Dealer Filter (Only for UCM / Group Head)

6.4.4.7.1. Default 'All' will be selected.

6.4.5. Screen will have following components

6.4.5.1. Vehicle List (List of Vehicles)

6.4.5.1.1. Each item in the list will contain following information

6.5. 9.2. Order List

6.5.1. This screen will show orders in ascending order of order date

6.5.1.1. Screen consists of following components

6.5.1.1.1. Filter

6.5.1.1.2. Filters

6.5.1.1.3. Order List

6.5.2. System Integrations

6.5.2.1. UCTDMS (From Order)

6.5.2.1.1. Getting Vehicle Details

6.5.2.1.2. Getting Customer (old & new) Details

6.6. 9.3. General Points

6.6.1. Based on role matrix

6.6.1.1. SO can only view/update

6.6.1.1.1. PDI (for his own enquiries / orders)

6.6.1.1.2. Delivery (for his own enquiries / orders)

6.6.1.1.3. Name Transfer (for his own enquiries / orders)

6.6.1.2. STL can view

6.6.1.2.1. PDI (for his SO's enquiries / orders)

6.6.1.2.2. Delivery (for his SO’s enquiries / orders)

6.6.1.2.3. Name Transfer for his SO’s enquiries / orders

6.6.1.3. UCM / Group Head / EDP(Administration person) / Admin can view PDI, Delivery and Name Transfer for all dealers which are part of his dealer group

6.6.1.4. TKM Sub Zone can view orders for all dealers which are part of his allocated zone. (For e.g. East Zone)

6.6.1.5. Zonal can view orders for all dealers which are part of his dealer group

6.6.1.6. Refer Role Matrix for roles & rights

6.7. System Integrations

6.7.1. UCTDMS

6.7.1.1. For getting following details from UCTDMS

6.7.1.1.1. Order Details

6.7.1.1.2. Follow-Up details

6.7.2. TFS

6.7.2.1. Passing Orders to TFS (where TFS is selected as Financer)

6.7.2.2. Getting following details from TFS

6.7.2.2.1. Status

6.7.2.2.2. EMI amount

6.7.2.2.3. Loan amount

7. Certification

7.1. 11.1. Dealer Certification Request

7.1.1. Using this screen Dealer User can generate certification request to TKM

7.1.2. By default, the following vehicles will be displayed under Dealer Certification Request

7.1.2.1. All vehicles which are purchased and retail eligibility done

7.1.3. UCM status will be 'No Action"

7.1.4. Screen Features

7.1.4.1. Recertification Due

7.1.4.1.1. Tapping on icon will display list of vehicles which recertification due(expiry date)in next 15 days

7.1.4.1.2. Each item in the list will display

7.1.4.1.3. “Close” icon will also be available in the screen to close the screen and go back to listing

7.1.4.2. Search

7.1.4.2.1. User can search for the particular vehicle by entering reg. no

7.1.4.2.2. Vehicles list will be filtered based on the entered reg. no

7.1.4.3. UCM Status

7.1.4.3.1. Following options will be available to filter the vehicles list based on the selection

7.1.4.4. Date Filters

7.1.4.4.1. The following date filters are available on the screen to filter vehicles list based on purchased day

7.1.4.4.2. Vehicle List will show vehicles which purchase date is within the selected duration.

7.1.4.5. Vehicles List

7.1.4.5.1. List showing vehicles which purchase date is in last 3 months (default) or matching the selection (Date & Status filter)

7.1.4.5.2. The list will be displayed in descending order of purchase date

7.1.4.5.3. Each item in the list contains following fields

7.2. 11.1.1. Service History

7.2.1. This screen will display service history of the vehicle

7.2.2. Each service history item contains following information

7.2.2.1. Job Order No

7.2.2.2. Job Order Date

7.2.2.3. Dealer CD

7.2.2.4. Branch CD

7.2.2.5. VIN No

7.2.2.6. Mileage In

7.2.2.7. Customer Name

7.2.2.8. Dealer Group

7.2.2.9. Dealer Name

7.2.2.10. Job Nature

7.2.2.11. Cust Req

7.2.2.12. OP Desc

7.2.2.13. QC Comments

7.2.2.14. Labour Cost

7.2.2.15. Part Cost

7.2.2.16. Outside Labour Cost

7.2.2.17. Outside Part Cost

7.2.2.18. Outside Body Cost

7.2.2.19. Outside Oil Cost

7.2.2.20. Grand Total

7.2.2.21. Parts

7.2.2.21.1. Part Name

7.2.2.21.2. Quantity

7.2.3. Close icon will also be available in the screen to close the screen and go back to listing screen.

7.3. 11.1.2. Certification Checklist

7.3.1. This screen enables user to create certification checklist

7.3.2. Screen features

7.3.2.1. Certification Checklist (To-Be Entered by Dealer)

7.3.2.1.1. This will list checklist items to-be entered by dealer

7.3.2.1.2. Header will have count along with label showing filled counts from all. For example, 3/5

7.3.2.2. Certification Checklist (From Procurement)

7.3.2.2.1. This will list checklist items captured in procurement

7.3.2.2.2. user can update anything if he wants

7.3.2.2.3. Header will have count along with label showing filled counts from all. For example, 3/5

7.3.2.3. Certification Checklist (From Valuation)

7.3.2.3.1. This will list checklist items captured in valuation

7.3.2.3.2. User can update anything if he wants

7.3.2.3.3. Header will have count along with label showing filled counts from all. For example, 3/5

7.3.3. Each list is an accordion control, tapping on it will collapse / expand the list.

7.3.4. User Actions

7.3.4.1. All matching option

7.3.4.1.1. Yes or No will be there

7.3.4.1.2. If selected, all will be considered as yes / no and ‘’green check icon /red cross ‘’ icon will be displayed

7.3.4.2. Single tapping

7.3.4.2.1. Single tapping any item will show ‘’green check" icon in the list

7.3.4.2.2. 'Availability Matching' and 'Matching Certification Criteria' will be considered yes for the same

7.3.4.3. Double tapping (tapping twice)

7.3.4.3.1. Double tapping (tapping twice) any item will show "red cross" icon in the list

7.3.4.3.2. ‘Availability Matching’ and ‘Matching Certification Criteria’ will be considered No for the same

7.3.4.4. Close

7.3.4.4.1. will close the certification checklist screen

7.3.4.5. Save

7.3.4.5.1. Save the certification checklist and close the certification checklist screen

7.3.5. Note

7.3.5.1. Each item must have either ‘yes’ or ‘no’ for certification checklist to be saved

7.3.5.2. On tapping of ‘Save’ button, if anything is not filled then the respective item should be highlighted with error message ‘Mandatory fields need to be filled’

7.3.5.3. Certification Checklist items and respective mapping is defined in certification checklist file(Certification Checklist Items & Mapping)

7.4. 11.1.3. Images

7.4.1. This screen will enable user to view /upload certification images.

7.4.2. Screen Features

7.4.2.1. Consists of following fields

7.4.2.1.1. 4 image thumbnails

7.4.2.1.2. Save

7.4.2.1.3. Close

7.5. 11.2. Dealer Certification Details

7.5.1. This screen will display dealer certifications list which has been sent to TKM for approval

7.5.2. Screen Features

7.5.2.1. Search

7.5.2.1.1. User can enter vehicle reg. no. to search for the specific vehicle

7.5.2.1.2. Vehicles list will be filtered based on the entered reg. no

7.5.2.2. Date Filters

7.5.2.2.1. 15 Days

7.5.2.2.2. 30 Days

7.5.2.2.3. Date Range (Only 3 months)

7.5.2.3. Status Filters

7.5.2.3.1. Five status filters will be displayed in the screen to filter the vehicle list

7.5.2.3.2. Each filter will have the following respective count

7.5.2.3.3. List will be filtered based on the selected filter

7.5.2.4. Vehicle List

7.5.2.4.1. Displays Vehicles which certification request date is within last 3 months of current day.

7.5.2.4.2. List will be displayed in descending order of certification request date

7.5.2.4.3. Each item in the list will display following items

7.5.2.4.4. Based on the following status the fields will be displayed for each item in the list

7.5.3. User Actions

7.5.3.1. View Certification Checklist

7.5.3.1.1. Opens Certification Checklist in read-only mode

7.5.3.2. View Images

7.5.3.2.1. Opens Images screen

7.5.3.2.2. User can only view images

7.5.3.3. Re-apply (only available for expired items)

7.5.3.3.1. Tapping on it will re-apply the certification

7.5.3.3.2. Certification request will be raised to TKM and in Dealer certification request

7.5.3.3.3. it will be shown as “No action” in dealer certification request”

7.5.3.3.4. Record (Expired) will be removed from screen

7.6. 11.3. TKM Certification Request & Details

7.6.1. By using this screen,TKM Users can see dealer certification requests, certify and reject certifications

7.6.2. Screen Features

7.6.2.1. Zones & Subzones filters

7.6.2.1.1. TKM HO will have zones & sub zones filters

7.6.2.1.2. HO can select either zone or sub zone

7.6.2.1.3. Dealer group(s) which fall under the selected zone or sub-zone will be displayed under Dealer Group dropdown

7.6.2.2. Dealer Group

7.6.2.2.1. Displays Dealer Group(s) allocated to TKM user based on his role.

7.6.2.3. Dealer(branch)

7.6.2.3.1. Populated based on selected dealer group

7.6.2.4. Search

7.6.2.4.1. Tapping on it will search for certification requests and certification details of the selected dealer as shown below

7.6.3. Certification Request & Details

7.6.3.1. Consists of two tabs

7.6.3.1.1. Judgement Approval (Certification Request)

7.6.3.1.2. Certification Approval (Certification Details)

7.6.4. Note

7.6.4.1. The following will be based on certification criteria mapped with make & model

7.6.4.1.1. Certification Type

7.6.4.1.2. certification fees

7.6.4.1.3. warranty fees

7.6.4.2. Respective mapping is defined in certification checklist file under ‘model wise (eg for innova , etios)certification criteria tab’

7.7. 11.3.1. TKM Certification Checklist

7.7.1. TKM user will fill certification checklist for certification

7.7.2. Screen Features

7.7.2.1. Checklist items

7.7.2.1.1. Section wise ,checklist items will be displayed as accordion

7.7.2.1.2. Each accordion will have the following

7.7.2.1.3. Each item in the list will display following things

7.7.2.2. Certification Fields

7.7.2.2.1. Following fields can be filled for certification checklist:

7.7.3. Certification cannot be created until explicitly ‘Certify’ button is tapped

8. Stock

8.1. 8.0 Stock - 3 Main Category

8.1.1. Fast/Slow: This will display Fast and Slow-moving stocks

8.1.2. Statement: This will display stock statement. This tab will be default selected.

8.1.3. Inventory: This will display ageing inventory.

8.2. 8.1. Stock Statement

8.2.1. Stock statement screen displays available stock.

8.2.1.1. Search by Reg. No

8.2.1.1.1. User will search in the stock statement by entering vehicle registration number

8.2.1.1.2. The stock list will be filtered based on the entered reg. no.

8.2.1.1.3. This filter will be applicable to all four lists

8.2.1.2. Retail Stock Filter

8.2.1.2.1. Free(Default selected.)

8.2.1.2.2. Booked

8.2.1.2.3. All

8.2.1.3. Retail / WholesaleFilter

8.2.1.3.1. User can change to Wholesale or Retail and selecting respective option.

8.2.1.4. Filter

8.2.1.4.1. Tapping on it will open Filter screen.

8.2.1.5. Make, Model, Suffix& Year Filter

8.2.1.5.1. It will filter the vehicles based on the selection.

8.2.1.6. Retail Stock list (All)

8.2.1.6.1. Displays in list(Descending order)

8.2.1.6.2. Each item in the list will contain

8.2.1.7. Location Filter(By Default, dealer’s location will be displayed).

8.2.1.7.1. For UCM & Group Head or any role, “All” will be selected by default.

8.2.1.7.2. However, user can change the location and select other location of the same dealer group or applicable dealer groups (in case of TKM user)to view the stock available in other locations.

8.2.1.7.3. Select location

8.2.1.8. Transferred Stock Filter

8.2.1.8.1. Toggle button to filter the stocks showing only transferred stock.

8.2.1.9. Non-Toyota Filter

8.2.1.9.1. Toggle button same as Transferred Stock Filter. Tapping on it will show only non-Toyota stock in list. Tapping again will display all stocks.

8.3. 8.1.1. Filters

8.3.1. Color(select from the selection box).

8.3.1.1. Filter the stock list based on color.

8.3.2. Fuel(User will select fuel from the selection box.Tapping again will remove the filter. Multiple filters can be selected)

8.3.2.1. Petrol

8.3.2.2. Diesel

8.3.2.3. CNG

8.3.2.4. Electric

8.3.3. Transmission

8.3.3.1. Toggle button(Only single can be selected from both. Either none is selected, or single is selected)

8.3.3.1.1. Manual

8.3.3.1.2. Automatic

8.3.3.1.3. AMT

8.3.4. Emission

8.3.4.1. User will select emission from the selection box.

8.3.5. Sale Price

8.3.5.1. Filter the stock list based on selected price range.

8.3.6. Odometer

8.3.6.1. Filter the stock list based on selected odometer range.

8.3.7. Discounted Only

8.3.7.1. Filter the stock list showing only discounted stocks.

8.3.8. Promotional Only

8.3.8.1. Filter the stock list showing only stocks which has promotional remarks defined.

8.3.9. Pending Selling Price

8.3.9.1. Filter the stock list showing items where selling price is not defined.

8.3.10. Images / 360 Pending

8.3.10.1. Filter the stock list showing items where images / 360 view not uploaded.

8.3.11. Not Pushed to Website

8.3.11.1. Filter the stock list showing items where images are not pushed to website

8.3.12. Rejected for Website

8.3.12.1. Filter the stock list showing items where images/ 360-degree are rejected for website.

8.3.13. Blocked Vehicles Only

8.3.13.1. Filter the stock list showing vehicles which are blocked.

8.3.14. Under RF

8.3.14.1. Filter the stock list showing vehicles which are under RF.

8.3.15. Certified

8.3.15.1. Filter the stock list showing vehicles which are certified.

8.3.16. RF Required

8.3.16.1. RF required is selected in Retail Eligibility Test.

8.3.17. Date Filters

8.3.17.1. Current month

8.3.17.2. Last month

8.3.17.3. Last 2 months

8.3.17.4. Date range

8.3.18. Wholesale Parameters(These filter parameters will be applicable only to wholesale vehicle list.)

8.3.18.1. Party type

8.3.18.1.1. Toggle buttons(Only single can be selected )

8.3.18.2. Party(Select party from the selection box.)

8.3.18.2.1. This has dependency on Party Type. The selection box will contain values for the selected party type.

8.3.18.2.2. If party type is not selected, then this filter cannot be applied.

8.3.18.3. Sales Officer(Filter the list based on sales officer.)

8.3.18.3.1. User will select sales officer from the selection box.

8.3.19. Booked Parameters(applicable only to booked vehicle list.)

8.3.19.1. Booked + 3 Days: (If selected)

8.3.19.1.1. Booked Vehicles List will show vehicles only which are booked, and 3 days has been already passed

8.3.19.2. LDD Passed: (If selected)

8.3.19.2.1. Booked Vehicles List will show vehicles only which likely delivery date has already passed.

8.3.20. Close

8.3.20.1. It will close the screen and changes will not be saved.

8.3.21. Apply

8.3.21.1. It will save the filters, close the screen and refresh the stock list (retail & wholesale) based on the selection.

8.4. 8.1.2. Vehicle card(vehicle specific information.)

8.4.1. Timeline: This will display the timeline of vehicle from procurement to delivery

8.4.1.1. By default, Un checked icon will be displayed.

8.4.1.2. If respective stage is complete for the vehicle then Checked icon will be displayed marking stage completion.

8.4.2. Vehicle details

8.4.2.1. Reg No.

8.4.2.2. Make, Model, Suffix, Year

8.4.2.3. Reg. date

8.4.2.4. Color

8.4.2.5. Transmission

8.4.2.6. Fuel

8.4.2.7. VIN

8.4.2.7.1. It's with tick icon if VIN plate is scanned. Tapping on it will open scanned VIN plate image in popup if it is done during valuation.

8.4.2.8. Engine No.

8.4.2.9. Name transferred

8.4.2.9.1. If name transfer is done i.e. confirm to seller status is selected under Name Transfer screen in Retail

8.4.3. 360 Exterior & Interior View / Images

8.4.3.1. 360 Exterior View: Shows Thumbnail Image of 360-degree

8.4.3.1.1. Exterior view.

8.4.3.1.2. Interior view.

8.4.3.2. Images

8.4.3.2.1. 12 Images will be displayed if 360-degree view not captured.

8.4.3.2.2. Thumbnail will be displayed for each image. Tapping on it will display full image in popup.

8.4.4. Insurance and Warranty Details

8.4.4.1. No. of owners

8.4.4.2. Odometer

8.4.4.3. Purchase date

8.4.4.4. Inventory days

8.4.4.5. Vehicle classification(Retail/Wholesale)

8.4.4.6. Insurance Type

8.4.4.7. Insurance Expiry Date

8.4.4.8. Certification with Warranty (Certification Type)

8.4.4.9. Insurance Company Name

8.4.5. Valuation Summary

8.4.5.1. Exterior Score

8.4.5.2. Interior score

8.4.5.3. Function Score

8.4.5.4. Frame Score

8.4.5.5. Total Score

8.4.5.6. Level

8.4.5.7. Accidental Flag(if yes)

8.4.5.8. Flooded Vehicle Flag (if yes)

8.4.5.9. Duplicate RC Flag if RC is duplicate

8.4.5.10. Stolen Vehicle Flag (if yes)

8.4.5.11. Total Loss Flag (if yes)

8.4.5.12. Odometer Tempering (if yes)

8.4.5.13. Chassis / Vin Replaced Flag (if yes)

8.4.5.14. Insurance Expired Flag: Insurance Expired flag with expiry date –‘Insurance expired on expiry date

8.4.5.15. Odometer Changed At: Label and Value

8.4.5.16. Hypothecation: Hypothecation status

8.4.5.17. RF Cost: RF Cost and amount

8.4.5.18. Std. RF Cost: Std. RF Cost and Amount

8.4.5.19. Total RF Cost: Total RF Cost and amount

8.4.5.20. View Detail: Tapping on it will open Valuation Detail screen.

8.4.6. Customer Details

8.4.6.1. Customer Name

8.4.6.2. Order No.

8.4.6.3. Order Date

8.4.6.4. Sale Date

8.4.6.5. Sale Price

8.4.6.6. Margin

8.4.7. RF Details

8.4.7.1. RF Request & Actual Cost

8.4.7.1.1. Sub Request

8.4.7.1.2. RF Actual Cost

8.4.8. Vehicle Features(As per valuation)

8.4.9. Previous Owners Details:

8.4.9.1. Customer Name

8.4.9.2. Purchase Date

8.4.9.3. Buying Price

8.5. 8.1.3. Selling price(enables UCM / Group Head to define selling price for the vehicle)

8.5.1. Vehicle Details

8.5.1.1. Reg. No

8.5.1.2. Make

8.5.1.3. Model

8.5.1.4. Suffix

8.5.1.5. Year

8.5.1.6. Color

8.5.1.7. Transmission

8.5.1.8. Fuel Type

8.5.1.9. VIN and Engine No.

8.5.2. Valuation Summary(Same as described above in Vehicle Card screen.)

8.5.3. Price Assignment & Review

8.5.3.1. UCM / Group Head can define selling price.

8.5.3.1.1. Selling Price = Buying Price + RF Cost + Inv. Cost + Administration Cost + Marketing Expense + Certification Cost + Handling Cost + Margin.

8.5.3.1.2. Ownership Transfer Fees: Ownership Transfer Fees defined by dealer in Master (Number). This value is editable. UCM / Group Head can change this value.

8.5.3.1.3. TCS (%): TCS defined by dealer in Master (% of selling price). This value is editable. UCM / Group Head can change this value

8.5.3.1.4. Insurance Expired Cost: Insurance Expired Cost defined by dealer in Master (Number). This value is editable. UCM / Group Head can change this value.

8.5.3.1.5. Stock Days Target: Editable field. Value will be derived based on avg. stock days of same Make, Model, Suffix, Fuel & Color.

8.5.3.1.6. Selling Price: Editable field. Automatically derived based on the above formula. If this is changed then margin should be changed automatically change.

8.5.3.1.7. Price Review Date: Editable Field. Automatically derived based on end day of month.

8.5.3.1.8. History icon: Tapping on it will open history showing selling price, person name and date.

8.5.3.1.9. Suggested Price: Suggested Price based on make, model, suffix and year of last 5 sold vehicles.

8.5.3.1.10. In Stock: Functionality will be same as described under Stock Matching under buyer enquiry.

8.5.3.1.11. Buyer Hot Enquiry: Functionality will be same as described under Stock Matching under buyer enquiry except only hot buyer enquiries will be displayed here.

8.5.3.1.12. Seller Hot Enquiry: Functionality will be same as described under Stock Matching under buyer enquiry except only hot seller enquiries will be displayed here.

8.5.3.1.13. Close: Tapping on close button will close the screen.

8.5.3.1.14. Save: Tapping on Save button will save the price and following information will be saved in UCTDMS:

8.6. 8.1.4.Images / 360-degree view

8.6.1. All users can view Images / 360-degree view whereas RFC / EDP (or New User Role) can upload the images / 360-degree view.

8.6.1.1. Toggle button

8.6.1.1.1. To access 360-degree interface(Default selected) or Images.

8.6.1.2. Push to website

8.6.1.2.1. If this is selected then Images & 360-degree view will be available for website review for reviewer. (It will be available on website once approved.)

8.6.1.3. 360-degree

8.6.1.3.1. User can capture or view the interior and exterior 360-degree(video recording).

8.6.1.4. Images

8.6.1.4.1. Photo angles should be displayed where user can tap and take the photographs

8.6.1.4.2. Tapping on the item will open a popup/screen where user can take the photograph.

8.6.1.4.3. Captured photograph can be previewed in the popup/screen

8.6.1.4.4. If 360-degree is not captured, then following 12 images should be captured

8.6.1.4.5. Primary image for website

8.6.1.4.6. If Images are already captured, then tapping on particular item (number) will open captured photograph in popup/screen with the facility to update the same.

8.6.1.5. Rejected Images / 360-degree view

8.6.1.5.1. Rejected images will be displayed as ‘X’ mark for the particular item in screen.

8.6.1.5.2. If interior and exterior 360-degree view is rejected / approved, then similar kind of indication will be shown. Once updated, again it will be sent for review.

8.7. 8.1.5. Display Report

8.7.1. Vehicle Details

8.7.1.1. Reg. No

8.7.1.2. Make

8.7.1.3. Model

8.7.1.4. Suffix

8.7.1.5. Year

8.7.1.6. Color

8.7.1.7. Transmission

8.7.1.8. Fuel Type

8.7.1.9. New car price(Ex: Showroom)

8.7.1.9.1. New Car Price will come from TSA or excel upload in Master.

8.7.2. QR Code

8.7.2.1. QR code of the vehicle (website link)

8.7.3. 360 Exterior & Interior View / Images.

8.7.3.1. Same as described above in Vehicle Card

8.7.4. Insurance & Warranty Details:

8.7.4.1. No. of Owners

8.7.4.2. Odometer

8.7.4.3. Selling Price

8.7.4.4. Certification with Warranty

8.7.4.5. Insurance Type

8.7.4.6. Insurance Expiry Date

8.7.4.7. Insurance Company Name

8.7.5. Insurance Images

8.7.5.1. Tapping on it will open a popup showing insurance images captured during valuation.

8.7.6. RC Images

8.7.6.1. Tapping on it will open a popup showing RC images captured during valuation.

8.7.7. Valuation Summary

8.7.7.1. Same as described above in Vehicle Card screen

8.7.8. Vehicle Features

8.7.8.1. Vehicle Features captured during valuation

8.7.9. USP

8.7.9.1. USP captured during valuation

8.7.10. Print

8.7.10.1. Facility should be available to print the display report.

8.7.10.2. Print Report will have all the fields except RF Cost in valuation summary including thumbnail image of interior and exterior 360-degree view.

8.8. 8.1.6. Discount

8.8.1. Discount screen enables UCM / Group Head to define discount and all users to view Discount History.

8.8.1.1. Discount

8.8.1.1.1. Define discount for the vehicle. This field will be blank for defining new discount.

8.8.1.1.2. This field will be read-only for all users except UCM & Group Head.

8.8.1.2. Discount History

8.8.1.2.1. Discount History will display the discounts applied for the vehicle.

8.8.1.3. Close

8.8.1.3.1. Tapping on this will close the screen.

8.8.1.4. Save

8.8.1.4.1. Tapping on this will save the discount amount.

8.8.1.4.2. For every save, new discount should be saved with person name and date.

8.8.1.4.3. Selling Price will be updated based on the discount and same need to be saved in CTDMS with no change in Stock Days Target and Next Price Review Date as end day of the current month.

8.9. 8.1.7.Promotional Remarks

8.9.1. Popup will be display as shown below when user taps on Promotional Remarks link.

8.9.1.1. Header

8.9.1.1.1. Promotional Remarks

8.9.1.2. Promotional Remarks(This field will become read-only for them.)

8.9.1.2.1. Promotional Remarks view / create / update. UCM / Group Head can create / update the promotional remarks whereas other users can only view remarks.

8.9.1.3. Cancel

8.9.1.3.1. Tapping on it will close the popup.

8.9.1.4. Save

8.9.1.4.1. Tapping on it will save promotional remarks and close the popup.

8.9.1.4.2. Promotional Remarks notification will be sent to PO, PTL, SO & STL

8.10. 8.1.8.Booked Vehicles List

8.10.1. It will be displayed when user selects ‘Booked’ in the stage

8.10.1.1. Selected Filters will be applied on the Booked Vehicles List.

8.10.1.2. List will be displayed in ascending order of order date.

8.10.1.3. list will display vehicles which are booked & not delivered

8.10.1.4. Likely Delivery Date passed items should be highlighted in different color.

8.10.2. List item fields

8.10.2.1. Vehicle Reg. No.

8.10.2.1.1. Tapping on it will open Vehicle Card.

8.10.2.2. Vehicle Details

8.10.2.2.1. Make

8.10.2.2.2. Model

8.10.2.2.3. Suffix

8.10.2.2.4. Year

8.10.2.2.5. Color

8.10.2.2.6. Transmission

8.10.2.2.7. Fuel Type

8.10.2.2.8. Odometer

8.10.2.2.9. Inventory Days

8.10.2.2.10. SO Name

8.10.2.2.11. Booking Date (Order Date)

8.10.2.2.12. Selling Price (Vehicle Sales Price)

8.10.2.2.13. Likely Delivery Date

8.10.2.2.14. Customer Name

8.10.2.2.15. Action: Comment / Notify to SO & STL(Available to UCM):

8.11. 8.1.9.Free Vehicles List

8.11.1. Free Vehicles List screen will be displayed when user selects ‘Free in the stage.

8.11.1.1. Free vehicles list will display a list of vehicles which are in Procurement, Refurbishment & Display Stage.

8.11.1.2. List will be displayed in ascending order of purchase date.

8.11.1.3. Selected Filters will be applied on the FreeVehicles List.

8.11.2. List Item fields

8.11.2.1. Reg. No. & Stage Panel

8.11.2.1.1. This will display vehicle reg. no., stage and certification icon (if vehicle is certified). Tapping on panel will open vehicle card of that vehicle.

8.11.2.2. Make

8.11.2.3. Model

8.11.2.4. Suffix

8.11.2.5. Year

8.11.2.6. Color

8.11.2.7. Transmission

8.11.2.8. Fuel Type

8.11.2.9. Odometer

8.11.2.10. Inventory Days

8.11.2.11. Inventory Cost [Formula: Max (Inventory Cost Amount, (Inv. Rate (%) / 365) X Buying Price X Inventory Days))]

8.11.2.11.1. Inventory cost amount from master or calculated inventory cost whichever is maximum is considered for Inventory Cost.

8.11.2.12. Certification Type (if Certified)

8.11.2.13. Actions

8.11.2.13.1. Comment/Notify to PO & PTL(Available to UCM)

8.11.2.13.2. Hot Enquiries

8.12. 8.1.10.Wholesale Vehicle List

8.12.1. This screen is accessible by selecting “Wholesale” in Retail / Wholesale selection box.

8.12.1.1. Selected Filters will be applied on the WholesaleVehicles List.

8.12.1.2. List will be displayed in descending order of confirmation date.

8.12.1.3. All confirmed vehicles will be displayed.

8.12.1.4. Stage tab will disappear for this screen.

8.12.1.5. List Item fields

8.12.1.5.1. Reg. No.

8.12.1.5.2. Make

8.12.1.5.3. Model

8.12.1.5.4. Suffix

8.12.1.5.5. Year

8.12.1.5.6. Color

8.12.1.5.7. Transmission

8.12.1.5.8. Fuel Type

8.12.1.5.9. SO Name

8.12.1.5.10. Party Type: Dealer or Broker

8.12.1.5.11. Party Name

8.12.1.5.12. Buying Price

8.12.1.5.13. Selling Price

8.12.1.5.14. Confirmed Date

8.12.1.5.15. Likely Delivery Date

8.13. 8.2.Fast / Slow

8.13.1. The screen will be divided in to two tabs

8.13.1.1. Fast Moving Stock( The list will display vehicles in ascending order of inventory days.)

8.13.1.1.1. Display top 10 stock items which are fast moving i.e. vehicles which stock days are less than 30 days.

8.13.1.2. Slow Moving Stock( The list will display vehicles in descending order of inventory days.)

8.13.1.2.1. Display top 10 stock items which are slow moving i.e. vehicles which stock days are greater than 45 days.

8.13.2. List Item fields

8.13.2.1. Make

8.13.2.2. Model

8.13.2.3. Suffix

8.13.2.4. Year

8.13.2.5. Color

8.13.2.6. Transmission

8.13.2.7. Fuel Type

8.13.2.8. Inventory days

8.14. 8.3.Inventory(Ageing inventory items (retail vehicles))

8.14.1. Search by Reg. No.

8.14.1.1. User can search by vehicle reg. no. stock list will show the vehicle of the searched reg. no

8.14.2. ICB

8.14.2.1. Tapping on this will open Inventory Control Board screen which is described below in detail.

8.14.3. Break Even

8.14.3.1. Tapping on this will open Break Even screen which is described below in detail.

8.14.4. Ageing Filters: Following ageing filters and sub filters will be available to filter the stock list:

8.14.4.1. <30 Days (Default selected)

8.14.4.1.1. Toyota

8.14.4.1.2. Non-Toyota

8.14.4.1.3. Certified

8.14.4.2. 31-45 Days

8.14.4.2.1. Toyota

8.14.4.2.2. Non-Toyota

8.14.4.2.3. Certified

8.14.4.3. 46 –60 Days

8.14.4.3.1. Toyota

8.14.4.3.2. Non-Toyota

8.14.4.3.3. Certified

8.14.4.4. >90

8.14.4.4.1. Toyota

8.14.4.4.2. Non-Toyota

8.14.4.4.3. Certified

8.14.5. Ageing Days will be considered from purchased date to current date. Each sub filter will display associated count of the vehicle

8.14.5.1. Discounted Only

8.14.5.1.1. Filter to see only discounted stocks. Selecting it will display only discounted stocks in stock list.

8.14.5.2. Promotional Only

8.14.5.2.1. Filter to see only promotional stocks. Selecting it will display only promotional stocks in stock list.

8.14.5.3. Stock List

8.14.5.3.1. Display vehicles for selected filter in the list.

8.15. 8.3.1.Inventory Control Board

8.15.1. Inventory Control Board will display vehicles for the selected location in inventory screen.

8.15.2. Only single location’s stock can be displayed here.

8.15.3. A location dropdown will be available on the screen to change the location for current screen only.

8.15.4. If “All” is selected in the inventory screen, then first location from CTDMS will be considered as default location

8.15.5. Car icon and badge counter

8.15.5.1. Car icon and badge counter will be displayed for each cell in the table if there is any vehicle.

8.15.5.1.1. Tapping on the same will display vehicle list

8.15.6. Inventory Control Board to be available on TV.

8.15.6.1. In TV / Display Monitor, user logs in only this board will be visible. This user login need to be managed from application

8.15.7. Separate user login will be created. The specific user will have only inventory control board access as a web page.

8.16. 8.3.2.Break Even

8.16.1. Break Even screen will display vehicles for the selected location in inventory screen.

8.16.2. A location dropdown will be available on the screen to change the location for current screen only.

8.16.3. Break Even screen will display list of vehicles which is about to break even (real margin will become 0) in 1 week, 2 weeks or 1 month.

8.16.4. Screen Features

8.16.4.1. Filters (Filters based on break even duration)

8.16.4.1.1. In 1 Week (0 to 7 Days)

8.16.4.1.2. In 2 Weeks (8 to 14 Days)

8.16.4.1.3. In 3 Weeks (15 to 21 Days)

8.16.4.2. Vehicle List (Each item in a list will display following information)

8.16.4.2.1. Vehicle Reg. No.

8.16.4.2.2. Make, Model, Suffix & Year

8.16.4.2.3. Color

8.16.4.2.4. Fuel Type

8.16.4.2.5. Buying Price

8.16.4.2.6. Fixed Cost (RF Cost + Administration Cost + Marketing Expense + Certification Cost + Handling Cost

8.16.4.2.7. Selling Price

8.16.4.2.8. Variable Cost (Inventory Cost + Depreciation).

8.16.4.2.9. Total Cost (Fixed Cost + Variable Cost)

8.16.4.2.10. Discount

8.16.4.2.11. RF Cost

8.16.4.2.12. Original Margin

8.16.4.2.13. Revised Margin = Original Margin + Inventory Cost Amount –Variable Cost.

8.16.4.2.14. Break Even Days = (Original Margin + Inventory Cost Amount) / Variable Cost per day

8.17. 8.4.Website Image Approval Screen (Web)(Ascending order of the date)

8.17.1. User can access this screen to approve /reject images for website.

8.17.1.1. Vehicle Details: Reg. No., Make, Model, Suffix and Year

8.17.1.2. Request Date: Date when images uploaded

8.17.1.3. Dealer & Dealer Group

8.17.1.4. Images (icon)

8.17.1.4.1. Tapping on it will open uploaded images in a popup/screen.(Grid View of photographs with positions name on the top)

8.17.1.5. 360-degree view (icons)

8.17.1.5.1. Interior view: Tapping on it will open screen showing interior view(video)

8.17.1.5.2. Exterior view: Tapping on it will open screen showing exterior view(Video)

8.17.1.6. Actions

8.17.1.6.1. Item will disappear from the screen as approve or rejection action is performed.

8.17.1.7. System Integrations(Stock):

8.17.1.7.1. UCTDMS

8.17.1.7.2. Website

8.18. 8.5.General Points

8.18.1. Based on role matrix,

8.18.1.1. PO, PTL, RFC, SO, STL, EDP / Admin can view stocks of dealer locations which come under their dealer group. Hence, dealer location dropdown will have only locations which are part of their dealer group.

8.18.1.1.1. UCM & Group head can view stocks of dealer locations which come under their dealer group. Hence, dealer location dropdown will have only locations which are part of their dealer group

8.18.1.2. TKM Sub Zone(South 1) / Zone can view stocks for all dealers which are part of his allocated zone

8.18.1.2.1. Dealer Group & Dealer location filter to be enabled. TKM Sub Zone user can view stock for specific dealer group at a time.It is mandatory to select dealer group or location to get stock data.

8.18.1.3. TKM HO can view stocks for all dealers in India. Hence, dealer location dropdown will show dealer locations grouped by dealer group grouped by zone.

8.18.1.3.1. Zone, Sub Zone, Dealer Group & Dealer location filter to be enabled. TKM Sub Zone user can view stock for specific dealer group at a time. It is mandatory to select dealer group or location to get stock data.

8.18.2. Vehicle will go in display stage if “Selling Price” is defined and “Images” uploaded.

8.18.3. If Push to website is selected and selling price yet not defined, then images / 360-degree will be available for approval when selling price is defined.

9. Dashboard

9.1. Enables user to review overall progress(Tasks & pending status)

9.2. 10.1. PO dashboard

9.2.1. It will available to PO users, Which will cover the features & actions based on the specific role

9.3. 10.1.1. Dashboard(PO)

9.3.1. Status of Seller Enquiry, Valuation and Procurements.

9.3.2. Today’s Activities.

9.3.3. Pending Follow-ups.

9.3.4. Action Items.

9.3.5. New Allocations.

9.3.6. Seller enquiry source wise conversion

9.3.7. Stock data.

9.3.8. Shortcut

9.4. 10.1.1.1. Status of Seller Enquiry, Valuation and Procurements.

9.4.1. It will give overall status of the Seller enquiry, Valuation and Procurement progress in terms of assigned target and actual progress.

9.4.1.1. Base on the archived target the required rate is also visible in centre, hence user can focus to finish the assigned target.

9.4.2. Seller enquiry, Valuation and Procurements actual counts will be shown against the target, the consolidated chart will depict the progress.

9.4.3. The parameters will be process, Assigned Target, Actual value and required rate will be calculated based on pending target and available days of the month.

9.4.4. Each stage wise separate bar chart is shown which will be based on each day of the month.

9.4.5. At the bottom of the section there will be Direct purchase count. Which will be calculated based on direct purchase input in the Seller enquiry.

9.4.5.1. It will show the Direct purchase list which have the specific input. (Direct purchase list – Refer PO performance section)

9.4.6. The data will be specific to the user and month to date data.

9.5. 10.1.1.2. Today’s Activities.

9.5.1. This section will depict the activities which are scheduled or performed by the user for the day.

9.5.1.1. Created Enquiry.

9.5.1.1.1. Count of the new created enquiry by the user in the day.

9.5.1.1.2. Click on the count of created enquiry will show the enquiry list for new created enquiries for the day.

9.5.1.2. Follow-up done.

9.5.1.2.1. Count of the actual done & target/ planned follow-up will be shown.

9.5.1.2.2. Click on the count will show the follow-up list for the day.

9.5.1.3. Valuation done with Appointments.

9.5.1.3.1. Count of the scheduled appointment & valuation done for the day.

9.5.1.3.2. Click will show the list of the valuation done.

9.5.1.3.3. Click on planned appointments will show the list of the valuation appointments of the day.

9.5.1.4. Valuation done without Appointments.

9.5.1.4.1. Count of the valuation done without any pre-scheduled appointments.

9.5.1.4.2. Click on the count will show the valuation list which are done for the day which are not scheduled.

9.5.1.5. Procurement done.

9.5.1.5.1. Count of the procurement will be shown for the day. The count will be calculated based on the collected vehicles and purchase confirmation done.

9.5.1.5.2. Click will be show the vehicle procurement list for the day

9.6. 10.1.1.3. Pending Follow-ups.

9.6.1. In seller enquiry when the follow-up entry is done the planned date is required to be defined. Based on that information the pending follow-up for the day is calculated.

9.6.1.1. Total Pending Follow-ups (All Sources).

9.6.1.1.1. Total pending follow-ups will be shown which calculated including planned follow-ups for the day and old pending follow-ups.

9.6.1.1.2. Click on the count will show all the pending seller enquiry follow-up list of the user.

9.6.1.2. Pending follow-ups by enquiry source / Type.

9.6.1.2.1. Based on the enquiry source type all the pending follow-ups will be grouped.

9.6.1.2.2. Enquiry source wise the count of the pending follow-up will be shown.

9.6.1.2.3. Click on the enquiry source & count will show the follow-up listing screen for the specific enquiry source

9.7. 10.1.1.4 Action Items.

9.7.1. Action items will show month to date actions which are available for the user with the updates.

9.7.1.1. New Car Booked

9.7.1.1.1. Month to date new cars booked count will be shown.

9.7.1.1.2. The count will be calculated based on the interface defined with the NCTDMS.

9.7.1.1.3. Click on the count will show the list of the seller enquiry which are linked with the new car enquiry data and have status updates available as the new car is booked.

9.7.1.1.4. In seller enquiry listing the new filter for the new car booked will be defined.

9.7.1.2. Wanted list

9.7.1.2.1. Count of the wanted list will show vehicles added in the wanted list.

9.7.1.2.2. Click on the count will show the wanted list screen.

9.7.1.2.3. The wanted list will have option to add new vehicle, refer buyer enquiry where adding vehicle to wanted list is explained in detail with screen.

9.7.1.2.4. Vehicle added to wanted list will be available for 45 days from date of entry. After 45 days the vehicle will be automatically removed from the wanted list.

9.7.1.2.5. The wanted list data will be specific to dealer location only. PTL, STL and UCM will have option to reset the wanted list or remove vehicles from the wanted list.

9.7.1.3. Documents Pending Cases

9.7.1.3.1. Documents pending cases count will be calculated based on the pending document in procurement. The count will be based on the enquiry only, if the specific enquiry in procurement phase has documents pending will be included.

9.7.1.3.2. Click on the count will show the procurement list of the enquiries.

9.7.1.4. Hot Enquiries.

9.7.1.4.1. The count of the assigned enquiries which are having enquiry status hot will be shown.

9.7.1.4.2. Click on the count will show the enquiry listing which are having enquiry status hot.

9.8. 10.1.1.5 New Allocations.

9.8.1. New allocations will show enquiries which are recently assigned to the user and any follow-up action is not done by the user.

9.8.1.1. Total Count of new assigned enquiries.

9.8.1.1.1. All new assigned enquiries count including all the enquiry sources.

9.8.1.1.2. Click on the count will show new assigned enquiry list for all enquiry sources.

9.8.1.2. Enquiry source wise new allocations.

9.8.1.2.1. Based on the enquiry source type all allocated / assigned enquiries will be grouped.

9.8.1.2.2. Enquiry source wise the count of the new allocation of enquiry will be shown.

9.8.1.2.3. Click will show the new assigned / allocated enquiry list for the selected enquiry source.

9.9. 10.1.1.6. Seller enquiry source wise conversion

9.9.1. This section will show the bar chart covering the conversion of the enquiry based on the enquiry source.

9.9.2. The enquiries which are converted to the procurement will be shown by each source type.

9.9.2.1. Each source type wise conversion percentages will be shown as well. IFC (Innova / Fortuner / Corolla) conversion flag related data to-be shown as separate source.

9.10. 10.1.1.7. Stock data

9.10.1. Stock data will show the overview of the stock data to user.

9.10.1.1. Count of Fast-moving stock

9.10.1.1.1. Fast moving stock count will be calculated from stock.

9.10.1.1.2. Click on the count will show the stock statement listing for the fast-moving stock.

9.10.1.2. Count of Slow-moving stock

9.10.1.2.1. Slow moving stock count will be calculated from stock.

9.10.1.2.2. Click on the count will show the stock statement listing for the slow-moving stock.

9.10.1.3. Discount

9.10.1.3.1. Count will be calculated for the vehicles which have discount defined.

9.10.1.3.2. Click on the count will show the stock statement filtered for the discounted vehicles.

9.10.1.4. Promotions

9.10.1.4.1. Count will be calculated for the vehicles which have promotions defined.

9.10.1.4.2. Click on the count will show the stock statement filtered for the defined promotions.

9.11. 10.1.1.8. Shortcut

9.11.1. For PO the short cut will be defined on the dashboard which will allow user to direct go to create seller enquiry screen.

9.11.1.1. Click on the add shortcut will show the create seller enquiry screen.

9.12. 10.1.2. PO Performance

9.12.1. PO Performance screen will give performance related counters and details for the user.

9.12.1.1. PO performance will have following features.

9.12.1.2. RF Cost

9.12.1.3. Wrong Buy Count

9.12.1.4. Valuation Time

9.12.1.5. GRN discrepancy

9.12.1.6. Enquiry & Follow-up count

9.12.1.7. Valuation & Procurement counts

9.12.1.8. Funnel: Trade-in

9.12.1.9. Direct Purchase

9.12.1.10. Deal Fail Analysis

9.12.1.11. Lead times

9.13. 10.1.2.1 RF cost

9.13.1. The bar chart will show the comparison between PO valuation and RFC valuation cost differences.

9.13.2. The Average cost of Valuation done by PO and Average cost of valuation done by RFC will be shown in the graph.

9.13.3. The before (PO Last valuation) & after (RFC last Valuation) base differences are shown.

9.13.3.1. The RF cost defined by the PO & RFC in valuation will to be considered.

9.13.3.2. PO Valuation will be the last valuation done prior procurement will be considered.

9.14. 10.1.2.2. Wrong buy count

9.14.1. The bar chart will be shown for the Wrong buy count.

9.14.1.1. The entry for the Wrong buy will be defined by RFC in retail eligibility decision.

9.14.1.2. Based on the input defined the wrong buy count will be calculated for the vehicles procured by the PO.

9.14.1.3. The average of wrong buy count for the dealer location and dealer group will be shown for comparison.

9.15. 10.1.2.3. Valuation time

9.15.1. The bar chart will show the valuation times specific to the PO.

9.15.1.1. Valuation time will be calculated from Valuation start to finish.

9.15.1.2. Highest time taken for a valuation.

9.15.1.3. Lowest time taken for a valuation.

9.15.1.4. Total average time taken for all the valuation done till date for the month.

9.15.1.5. Average time will be shown for the dealer location and dealer group for comparison.

9.16. 10.1.2.4. GRN discrepancy

9.16.1. The bar chart will show the procurement to GRN discrepancy counts.

9.16.1.1. GRN discrepancy will be calculated based on purchase confirmation done in procurement.

9.16.1.2. Purchase entry to Purchase confirmation if the duration is more or equal to 36 hours in that case it will be marked as GRN discrepancy.

9.16.1.3. The count of the GRN discrepancy will be shown for the PO for Month to date data.

9.16.1.4. Average count of the GRN discrepancy will be shown for the dealer location and dealer group for comparison.

9.17. 10.1.2.5. Enquiry & Follow-up count

9.17.1. The bar chart will show the target v/s actual data for Seller enquiry and its follow-ups.

9.17.1.1. Seller enquiry and Follow-up related target data will be shown.

9.17.1.2. For Follow-up the target data will be planned follow-ups (based on plan date).

9.17.1.3. New seller enquiries created or assigned to the PO will be calculated.

9.17.1.4. Total seller enquiries related follow-ups done will be calculated.

9.17.1.5. The percentage of the achievement will be calculated based on actuals and target data.

9.17.1.6. Target data will be available from UCTDMS system.

9.18. 10.1.2.6. Valuation & Procurement counts

9.18.1. The bar chart will show the target v/s actual data for Valuation and procurements.

9.18.1.1. Valuation and Procurement related target data will be shown.

9.18.1.2. New valuations created by the PO will be calculated.

9.18.1.3. Total procurements done will be calculated.

9.18.1.4. The percentage of the achievement will be calculated based on actuals and target data.

9.18.1.5. Target data will be available from UCTDMS system.

9.19. 10.1.2.7. Funnel: Trade-in

9.19.1. The funnel chart report will be plotted for trade-in data. The parameters and details will be as followings

9.19.1.1. Total replacement enquiries.

9.19.1.2. Valuation done for the replacement enquiries.

9.19.1.3. Procurement done for the replacement enquiries and will have new car booked.

9.19.1.4. The percentages will be calculated based on enquiries to valuation & valuation to procurement.

9.19.1.5. The average lead time will be calculated based on stages.

9.19.1.6. Dealer location & Dealer group wise average ratios to be shown in the funnel.

9.20. 10.1.2.8. Direct Purchase

9.20.1. The bar chart will show the count of the direct purchase’s enquiries converted to procurement.

9.20.1.1. Direct purchase input is defined in seller enquiry.

9.20.1.2. Direct purchase list to be defined which will have following parameters.

9.20.1.2.1. Enquiry no, enquiry Date

9.20.1.2.2. Source Type, Source Name

9.20.1.2.3. Vehicle information: Make, Model, Suffix & Year

9.20.1.2.4. The list data will be group by Source Type & Source Name

9.20.1.3. Count will be calculated based on the defined direct purchase enquiries get converted to procurement.

9.20.1.4. The average of dealer location will be shown which will be of all the PO of the dealer location.

9.21. 10.1.2.9. Deal Fail Analysis

9.21.1. The deal fail analysis section will show two parameters.

9.21.1.1. Dropped enquiries

9.21.1.1.1. Month to date the dropped enquiries could will be shown.

9.21.1.1.2. Click on the dropped enquiry count will show the dropped enquiry listing screen.

9.21.1.2. Top 5 reasons for dropped enquiries.

9.21.1.2.1. Based on the input defined for status reasons in dropped enquiry.

9.21.1.2.2. The top 5 reasons with count will be calculated and shown in tabular view.

9.21.1.2.3. Each reason wise dropped enquiry count will be shown, arranged by the highest count to lowest.

9.22. 10.1.2.10. Lead times

9.22.1. Average lead time data is calculated for followings.

9.22.1.1. Enquiry to Valuation

9.22.1.1.1. Average time taken for enquiry to valuation will be calculated for MTD (Month Till Date) data.

9.22.1.1.2. Time will be calculated from enquiry creation time to valuation creation time.

9.22.1.1.3. In case of the system created enquiries.

9.22.1.1.4. The dealer location average will be shown for comparison.

9.22.1.2. Valuation to Procurement

9.22.1.2.1. Average time taken for Valuation to procurement will be calculated for MTD data.

9.22.1.2.2. Time will be calculated from valuation creation time to procurement confirmation time.

9.22.1.2.3. The dealer location average will be shown for comparison.

9.22.1.3. Enquiry to Procurement

9.22.1.3.1. Average time taken for enquiry to procurement will be calculated for MTD data.

9.22.1.3.2. Time will be calculated from enquiry creation time to procurement confirmation time.

9.22.1.3.3. The dealer location average will be shown for comparison.

9.23. 10.2. SO Dashboard

9.23.1. SO Dashboard will be available to the SO (Sales officer) users. Which will cover the features and actions based on the specific role.

9.24. 10.2.1. Dashboard(SO)

9.24.1. SO Dashboard will have following features

9.24.2. Status of Buyer Enquiry, Sales Orders and Delivery.

9.24.3. Today’s Activities.

9.24.4. Pending Follow-ups.

9.24.5. Action Items.

9.24.6. New Allocations.

9.24.7. Buyer enquiry source wise conversion

9.24.8. Stock data.

9.24.9. Shortcut

9.25. 10.2.1.1. Status of Buyer Enquiry, Sales Orders and Delivery.

9.25.1. This section will give overall status of the Buyer enquiry, Sales Orders and Delivery Process / Stage in terms of assigned target and actual progress.

9.25.1.1. Base on the archived target the required rate is also visible in centre, hence user can focus to finish the assigned target.

9.25.2. Buyer Enquiry, Sales Orders and Delivery actual counts will be shown against the target, the consolidated chart will depict the progress.

9.25.3. The parameters will be process, Assigned Target, Actual value and required rate will be calculated based on pending target and available days of the month.

9.25.4. Each stage wise separate bar chart is shown which will be based on each day of the month.

9.25.5. The data will be specific to the user and month to date data.

9.26. 10.2.1.2. Today’s Activities.

9.26.1. This section will depict the activities which are scheduled or performed by the user for the day.

9.26.1.1. Created Enquiry.

9.26.1.1.1. Count of the new created Buyer enquiry by the user in the day.

9.26.1.1.2. Click on the count of created enquiry will show the enquiry list for new created enquiries for the day.

9.26.1.2. Follow-up done.

9.26.1.2.1. Count of the actual done & target/ planned follow-up will be shown.

9.26.1.2.2. Click on the count will show the follow-up list for the day.

9.26.1.3. Planned Delivery

9.26.1.3.1. In retail module the delivery dates are defined.

9.26.1.3.2. Two counts to be shown

9.26.1.3.3. Click on the count will show the delivery listing screen in the retail section.

9.26.1.4. Planned PDI

9.26.1.4.1. Based on the defined delivery date and likely delivery date the planned PDI will be shown.

9.26.1.4.2. Two counts to be shown

9.26.1.4.3. Click on the count will show the PDI listing screen in the retail section.

9.27. 10.2.1.3. Pending Follow-ups.

9.27.1. In buyer enquiry when the follow-up entry is done the planned date is required to be defined. Based on that information the pending follow-up for the day is calculated.

9.27.1.1. Total Pending Follow-ups.

9.27.1.1.1. Total pending follow-ups will be shown which calculated including planned follow-ups for the day and old pending follow-ups.

9.27.1.1.2. Click on the count will show all the pending buyer enquiry follow-up list of the user for all source types.

9.27.1.2. Pending follow-ups by enquiry source / Type.

9.27.1.2.1. Based on the enquiry source type all the pending follow-ups will be grouped.

9.27.1.2.2. Enquiry Sources: Walk-in, Web, New Car dropped, U-Car dropped & Exchange Mela.

9.27.1.2.3. Enquiry source wise the count of the pending follow-up will be shown.

9.27.1.2.4. Click on the enquiry source & count will show the follow-up listing screen for the specific enquiry source.

9.28. 10.2.1.4. Action items

9.28.1. Action items will show month to date actions which are available for the user with the updates.

9.28.1.1. Booked + 3 Days

9.28.1.1.1. The stock and retail related interfaces the information for the booked vehicle will be available.

9.28.1.1.2. Based on the Sales order booking date + 3 days the count will be calculated and shown.

9.28.1.1.3. Booked + 3 Days notification will be sent.

9.28.1.1.4. Click on the count will show the order listing screen with 3 days filter (All records greater than Today – 3 Days).

9.28.1.1.5. In case of order cancelled or delivery made the count will be updated.

9.28.1.2. Hot Enquiries.

9.28.1.2.1. The count of the assigned buyer enquiries which are having hot enquiry status.

9.28.1.2.2. Click on the count will show the buyer enquiry listing which are having hot enquiry status.

9.28.1.3. Vehicle in demand

9.28.1.3.1. Vehicle in demand will be calculated based on the buyer enquiry vehicle data.

9.28.1.3.2. The shortlisted and selected vehicles base count will be calculated for MTD data.

9.28.1.3.3. Click on the count will show a new pop up screen which will show following details

9.28.1.3.4. Once vehicle order is booked in that case the vehicle will get removed from the list.

9.28.1.4. Name Transfer

9.28.1.4.1. The count of pending name transfer will be calculated based on the vehicles which has delivery note generated and name transfer is not confirmed.

9.28.1.4.2. Click on the count will show the name transfer list.

9.28.1.5. Wanted list

9.28.1.5.1. Count of the wanted list will show vehicles added in the wanted list.

9.28.1.5.2. Click on the count will show the wanted list screen.

9.28.1.5.3. The wanted list will have option to add new vehicle, refer buyer enquiry where adding vehicle to wanted list is explained in detail with screen.

9.28.1.5.4. Vehicle added to wanted list will be available for 45 days from date of entry. After 45 days the vehicle will be automatically removed from the wanted list.

9.28.1.5.5. The wanted list data will be specific to dealer location only. PTL, STL and UCM will have option to reset the wanted list or remove vehicles from the wanted list.

9.29. 10.2.1.5. New allocations

9.29.1. New allocations will show enquiries which are recently assigned to the user and any follow-up action is not done by the user.

9.29.1.1. Total Count of new assigned enquiries.

9.29.1.1.1. All new assigned enquiries count including all the enquiry sources.

9.29.1.1.2. Click on the count will show new assigned enquiry list for all enquiry sources.

9.29.1.2. Enquiry source wise new allocations.

9.29.1.2.1. Based on the enquiry source type all allocated / assigned enquiries will be grouped.

9.29.1.2.2. Enquiry Sources: Web, New Car dropped, U-Car dropped.

9.29.1.2.3. Enquiry source wise the count of the new allocation of enquiry will be shown.

9.29.1.2.4. Click will show the new assigned / allocated enquiry list for the selected enquiry source.

9.30. 10.2.1.6 Buyer enquiry source wise conversion

9.30.1. This section will show the bar chart covering the conversion of the enquiry based on the enquiry source. The buyer enquiries which are converted to the delivery will be shown by each source type. Each source type wise conversion percentages will be shown as well.

9.30.2. The buyer enquiries which are converted to the delivery will be shown by each source type.

9.30.3. Each source type wise conversion percentages will be shown as well.

9.31. 10.2.1.7. Stock data

9.31.1. Stock data will show the overview of the stock data to user.

9.31.1.1. Count of Fast-moving stock

9.31.1.1.1. Fast moving stock count will be calculated from stock.

9.31.1.1.2. Click on the count will show the stock statement listing for the fast-moving stock.

9.31.1.2. Count of Slow-moving stock

9.31.1.2.1. Slow moving stock count will be calculated from stock.

9.31.1.2.2. Click on the count will show the stock statement listing for the slow-moving stock.

9.31.1.3. Discount

9.31.1.3.1. Count will be calculated for the vehicles which have discount defined.

9.31.1.3.2. Click on the count will show the stock statement filtered for the discounted vehicles.

9.31.1.4. Promotions

9.31.1.4.1. Count will be calculated for the vehicles which have promotions defined.

9.31.1.4.2. Click on the count will show the stock statement filtered for the defined promotions.

9.31.1.5. Certification Lapsed

9.31.1.5.1. Count will show the already lapsed certifications.

9.31.1.5.2. Show all the lapsed Certifications.

9.31.1.5.3. Click on the count will show the certification list with lapsed data filter.

9.31.1.6. Procurement

9.31.1.6.1. Count will show the new procurements of the vehicles last 5 days.

9.31.1.6.2. The count will be defined from the purchase confirmation data.

9.31.1.6.3. Click on the count will show the procurement list of the vehicles.

9.32. 10.2.1.8 Shortcut

9.32.1. For SO the short cut will be defined on the dashboard which will allow user to direct go to create buyer enquiry screen.

9.32.2. Click on the add shortcut will show the create buyer enquiry screen.

9.33. 10.2.2.SO Performance

9.33.1. SO Performance screen will give performance related counters and details for the user.

9.33.1.1. Enquiry & Follow-up count

9.33.1.2. Sales Orders & Delivery counts

9.33.1.3. Discount Amount

9.33.1.4. Test Drive

9.33.1.5. Funnel: Retail data

9.33.1.6. Deal Fail Analysis

9.33.1.7. Orders Cancelled Analysis

9.33.1.8. Lead times

9.34. 10.2.2.1.Enquiry & Follow-up count

9.34.1. The bar chart will show the target v/s actual data for Buyer enquiry and its follow-ups.

9.34.1.1. Buyer enquiry and Follow-up related target data will be shown.

9.34.1.2. New Buyer enquiries created or assigned to the PO will be calculated.

9.34.1.3. Total Buyer enquiries related follow-ups done will be calculated.

9.34.1.4. The percentage of the achievement will be calculated based on actuals and target data.

9.34.1.5. Target data will be available from UCTDMS system.

9.35. 10.2.2.2.Sales Orders & Delivery counts

9.35.1. The bar chart will show the target v/s actual data for Sales Orders and Delivery.

9.35.1.1. Sales Orders and Delivery related target data will be shown.

9.35.1.2. New Sales orders created in UCTMS will be available from the sync interface and count will be calculated.

9.35.1.3. Total Delivery notes created in UCTMS system will be available from the sync interface and count will be calculated.

9.35.1.4. The percentage of the achievement will be calculated based on actuals and target data.

9.35.1.5. Target data will be available from UCTDMS system.

9.36. 10.2.2.3.DiscountAmount

9.36.1. The bar chart will show the discount amount given/ specified by the SO.

9.36.1.1. Discount amount will be calculated from sales order bookings data.

9.36.1.2. Highest discount amount specified by SO.

9.36.1.3. Lowest discount amount specified by SO.

9.36.1.4. Total average discount specified for all the sales orders for MTD.

9.36.1.5. Average discount amount of all SO for the dealer location and dealer group for comparison.

9.37. 10.2.2.4.Test Drive

9.37.1. The bar chart will show the count of the test drive given by the SO in buyer enquiry.

9.37.2. Test drive count will be calculated for SO for MTD.

9.37.3. The average test drive count of all SO for the dealer location will be shown for comparison.

9.38. 10.2.2.5.Funnel: Retail data

9.38.1. The funnel chart report will be plotted for retail data. The parameters and details will be as followings

9.38.1.1. Total buyer enquiries.

9.38.1.2. Sales orders booking done for the buyer enquiries.

9.38.1.3. Delivery notes created for the enquiries.

9.38.1.4. The percentages will be calculated based on the buyer enquiry to sales order & sales orders to delivery.

9.38.1.5. The average lead time will be calculated based on stages.

9.38.1.6. Dealer location and dealer group average ration to shown.

9.39. 10.2.2.6.Deal Fail Analysis

9.39.1. The deal fail analysis section will show two parameters.

9.39.1.1. Dropped buyer enquiries

9.39.1.1.1. Month to date the dropped buyer enquiries could will be shown.

9.39.1.1.2. Click on the dropped buyer enquiry count will show the dropped buyer enquiry listing screen.

9.39.1.2. Top 5 reasons for dropped enquiries.

9.39.1.2.1. Based on the input defined for status reasons in dropped enquiry.

9.39.1.2.2. The top 5 reasons with count will be calculated and shown in tabular view.

9.39.1.2.3. Each reason wise dropped enquiry count will be shown, arranged by the highest count to lowest.

9.40. 10.2.2.7.Orders CancelledAnalysis

9.40.1. The order cancelled analysis section will show two parameters.

9.40.1.1. Orders Cancelled

9.40.1.1.1. Month to date the orders cancelled count will be calculated.

9.40.1.1.2. Click on the count will show orders listing screen with filter of cancelled orders.

9.40.1.2. Top 5 reasons for Orders Cancelled.

9.40.1.2.1. Based on the input defined for status reasons in order cancel in UCTDMS the data will be available.

9.40.1.2.2. The top 5 reasons with count will be calculated and shown in tabular view.

9.40.1.2.3. Each reason wise cancelled orders count will be shown, arranged by the highest count to lowest.

9.41. 10.2.2.8.Lead times

9.41.1. Average lead time data is calculated for followings.

9.41.1.1. Enquiry to Sales order

9.41.1.1.1. Average time taken for enquiry to Order booking will be calculated for MTD data.

9.41.1.1.2. Time will be calculated from enquiry creation time to Order date.

9.41.1.1.3. In case of the system created enquiries.

9.41.1.1.4. The dealer location average will be shown for comparison.

9.41.1.2. Sales order to Delivery

9.41.1.2.1. Average time taken for Sales order to Delivery will be calculated for MTD data.

9.41.1.2.2. Time will be calculated from Sales order date to delivery note date.

9.41.1.2.3. The dealer location average will be shown for comparison.

9.41.1.3. Enquiry to Delivery

9.41.1.3.1. Average time taken for enquiry to Delivery will be calculated for MTD data.

9.41.1.3.2. Time will be calculated from enquiry creation time to Delivery note date.

9.41.1.3.3. The dealer location average will be shown for comparison.

9.42. 10.3.RFC Dashboard

9.42.1. RFC Dashboard will be available to the RFC (Refurbishment Co-ordinator) users. Which will cover the features and actions based on the specific role

9.42.1.1. RFC Dashboard will have following features

9.42.1.2. Pending Retail Eligibility

9.42.1.3. Pending RF Request

9.42.1.4. Pending RF approvals

9.42.1.5. RF Not Started

9.42.1.6. RF Completed

9.42.1.7. Pending RF Cost

9.42.1.8. Certification Lapsed

9.42.1.9. Pending Certification (UCM)

9.42.1.10. Pending Certification (TKM)

9.42.1.11. Certification Lapsed in 7 Days

9.42.1.12. RF Lead Time

9.42.1.13. RF Cost

9.42.1.14. RF Cost comparison

9.42.1.15. RF Cost to Buying price Ratio

9.43. 10.3.3.1. Pending Retail Eligibility

9.43.1. The Pending Retail Eligibility count will be shown.

9.43.1.1. Pending Retail eligibility count will be calculated for the procured vehicles.

9.43.1.2. Procured vehicles whose retail eligibility decision is not made will calculated.

9.43.1.3. Click on the count will show the pending retails eligibility list in refurbishment section.

9.44. 10.3.3.2. .Pending RF Request

9.44.1. The Pending RF Request count will be shown.

9.44.1.1. Pending RF Request will be calculated based of following conditions.

9.44.1.1.1. Retail eligibility decision is made and classified as retail vehicle.

9.44.1.1.2. Specific vehicle required refurbishment

9.44.1.1.3. RF request is not created for the vehicle.

9.44.1.2. Click on the count will show the pending Retail eligibility list in refurbishment section with filter of pending RF requests.

9.45. 10.3.1.3.Pending RF approvals

9.45.1. The Pending RF Approvals count will be shown.

9.45.1.1. Pending RF approvals will be calculated based of following conditions.

9.45.1.1.1. RF Request created by RFC.

9.45.1.1.2. RF request not approved by UCM. RF requested sent back or rejected by UCM.

9.45.1.2. Click on the count will show RF request list with filter of approval status.

9.46. 10.3.1.4.RF Not Started

9.46.1. The RF Not started count will be shown.

9.46.1.1. RF Not started count will be calculated based on following conditions.

9.46.1.1.1. RF request is approved by UCM

9.46.1.1.2. Job card data is not available / Job card start date is not defined.

9.46.1.2. Click on the count will show the RF request list which do not have any job card data.

9.47. 10.3.1.5.RF Completed

9.47.1. The RF Completed count will be shown.

9.47.1.1. RF Completed count will be calculated based on

9.47.1.1.1. RF Request created and approved by UCM.

9.47.1.1.2. RF Completion date and RF costing with Actual RF data input is defined in UCTDMS.

9.47.1.1.3. RF request will have Job Card close date defined.

9.47.1.2. Click on the count will show the RF request list which will have the completed status defined.

9.48. 10.3.1.6.Pending RF Cost

9.48.1. The Pending RF Cost count will be shown.

9.48.1.1. Pending RF Cost count will be calculated based on following conditions.

9.48.1.1.1. RF Request created and approved by UCM.

9.48.1.1.2. RF Completion date defined and RF costing with Actual RF input is not defined in UCTDMS.

9.48.1.1.3. RF request will not have Job card close date and Actual RF amount not defined.

9.48.1.2. Click on the count will show the RF request list which do not have costing defined.

9.49. 10.3.1.7.Certification Lapsed

9.49.1. The count will show the certifications which are lapsed.

9.49.1.1. Count will be calculated based on the Certification expiry date and vehicles available in stock.

9.49.1.2. Click on count will show the certification list with lapsed data filter.

9.50. 10.3.1.8.Pending Certification (UCM)

9.50.1. The count will show the certification request are not approved by UCM.

9.50.1.1. Count will be calculated based on the request made and not approved by UCM.

9.50.1.2. Click on count will show the certification list filter of approval status.

9.51. 10.3.1.9.Pending Certification (TKM)

9.51.1. The count will show the certification request are not approved by TKM Zonal.

9.51.1.1. Count will be calculated based on the request made and not approved by TKM Zonal.

9.51.1.2. Click on count will show the certification list filter of approval status.

9.52. 10.3.1.10.Certification Expiring in 7 Days

9.52.1. The count will show the certifications which are going to be lapsed in next 7 days.

9.52.1.1. Count will be calculated based on the certification expiry date and vehicles available in stock.

9.52.1.2. Click on count will show the certification list with expiry date filter (Expiry date <= Today +7 Days)

9.53. 10.3.1.11.RF Lead Time

9.53.1. RF Lead time bar chart will be shown

9.53.1.1. RF Lead time will show the average time taken to complete the RF request.

9.53.1.2. RF Lead time will be shown for Toyota vehicles, Non-Toyota vehicles and all vehicles.

9.53.1.3. Click on Toyota section will show Toyota model wise average lead time.

9.53.1.4. Click on Non-Toyota section will show Non-Toyota make, model wise average lead time. Top seven selling models.

9.54. 10.3.1.12.RF Cost

9.54.1. RF Cost bar chart will be shown

9.54.1.1. RF Cost will show the average actual cost of the Vehicle.

9.54.1.2. RF Cost will show average cost for Toyota vehicles, Non-Toyota vehicles and all vehicles.

9.54.1.3. Click on Toyota section will show Toyota model wise average cost.

9.54.1.4. Click on Non-Toyota section will show Non-Toyota make, model wise average cost. Top seven selling models.

9.55. 10.3.1.13.RF Cost comparison

9.55.1. RF Cost Comparison bar chart will be shown

9.55.1.1. RF Cost Comparison will show the RF estimations by PO, RF estimations by RFC and actual RF Cost.

9.55.1.2. Average RF costing by PO, RFC and actual will be shown.

9.55.1.3. Click on Graph will show the tabular view of the data which will contain following details.

9.55.1.3.1. PO, PTL details

9.55.1.3.2. Vehicle information: Make, Model, Suffix & Year

9.55.1.3.3. PO Estimation

9.55.1.3.4. RFC Estimation

9.55.1.3.5. Actual RF Cost.

9.55.1.3.6. Top 10 differences will be shown.

9.56. 10.3.1.14.RF Cost to Buying price Ratio

9.56.1. Refurbishment cost to buying price ration will be calculated and shown for Toyota and Non-Toyota vehicles.

9.56.1.1. Ratio will be calculated based on the buying price and average refurbishment cost of the model.

9.56.1.2. Click on Toyota ratio will show following details in tabular view

9.56.1.2.1. Toyota model

9.56.1.2.2. Average buying price

9.56.1.2.3. Average refurbishment cost

9.56.1.2.4. Ratio RF(Actual) to BP.

9.56.1.2.5. Dealer average.

9.56.1.2.6. All Toyota models to be shown.

9.56.1.3. Click on Non-Toyota ratio will show following details.

9.56.1.3.1. Make, model

9.56.1.3.2. Average buying price

9.56.1.3.3. Average refurbishment cost

9.56.1.3.4. Ratio RF to BP.

9.56.1.3.5. Dealer group average.

9.56.1.4. For Non-Toyota top 7 models with high RF to BP ratio to be shown.

9.57. 10.4.PTL Dashboard

9.57.1. PTL Dashboard will be available to the PTL (Procurement Team Leader) users. Which will cover the features and actions based on the specific role.

9.58. 10.4.1.Dashboard main

9.58.1. PTL Dashboard will have following features

9.58.2. Status of Seller Enquiry, Valuation and Procurements.

9.58.3. Today’s Activities.

9.58.4. Pending Follow-ups.

9.58.5. Action Items.

9.58.6. Pending Allocations & Self-Allocations

9.58.7. Seller enquiry source wise conversion

9.58.8. Stock data.

9.59. 10.4.1.1.Status of Seller Enquiry, Valuation and Procurements.

9.59.1. PTL will have consolidated data for all the PO in the team.

9.59.2. For details refer PO section for status of seller enquiry, Valuation and procurement.

9.60. 10.4.1.2.Today’s Activities

9.60.1. PTL will have consolidated data for all the PO in the team.

9.60.2. For details refer PO section for Today’s Activities.

9.61. 10.4.1.3.Pending Follow-ups.

9.61.1. PTL will have consolidated data for all the PO in the team.

9.61.2. For details refer PO section for Pending Follow-ups.

9.62. 10.4.1.4.Action Items.

9.62.1. PTL will have consolidated data for all the PO in the team.

9.62.2. For details refer PO section for Action items.

9.62.3. TFS Customer List

9.62.3.1. New count for TFS customer list count to be shown which are not converted to Enquiry. Same will be available to UCM as well.

9.62.3.2. Click will show the TFS customer list, passed from TFS application (not converted to enquiry).

9.63. 10.4.1.5.Pending Allocations & Self-Allocations.

9.63.1. Pending Allocations & Self Allocations will have two sections.

9.63.1.1. Pending Allocations

9.63.1.1.1. Seller enquiries create in system which PTL need to assign / allocate to team PO, but not yet not allocated will be shown.

9.63.1.1.2. The pending allocations will show all pending allocations count.

9.63.1.1.3. Enquiry source wise pending allocations.

9.63.1.2. Self-Allocations

9.63.1.2.1. The non-allocated enquiries are self-assigned by team PO will be shown.

9.63.1.2.2. Count of total self-allocated enquiries of Team PO

9.63.1.2.3. PO wise self-allocated enquires counts

9.64. 10.4.1.6.Seller enquiry source wise conversion

9.64.1. PTL will have consolidated data for all the PO in the team.

9.64.2. For details refer PO section for seller enquiry source wise conversion bar chart.

9.65. 10.4.1.7.Stock data

9.65.1. Stock data will show the overview of the stock data to user.

9.65.1.1. Count of Fast-moving stock

9.65.1.1.1. Fast moving stock count will be calculated from stock.

9.65.1.1.2. Click on the count will show the stock statement listing for the fast-moving stock.

9.65.1.2. Count of Slow-moving stock

9.65.1.2.1. Slow moving stock count will be calculated from stock.

9.65.1.2.2. Click on the count will show the stock statement listing for the slow-moving stock.

9.65.1.3. Discount

9.65.1.3.1. Count will be calculated for the vehicles which have discount defined.

9.65.1.3.2. Click on the count will show the stock statement filtered for the discounted vehicles.

9.65.1.4. Promotions

9.65.1.4.1. Count will be calculated for the vehicles which have promotions defined.

9.65.1.4.2. Click on the count will show the stock statement filtered for the defined promotions

9.66. 10.4.2.Team Performance

9.66.1. Team/ PO Performance screen will give performance related counters and details for team PO.

9.66.2. PTL will have consolidated data available for the team (All PO). PTL can filter for specific PO and view the performance data of the selected PO.

9.67. 10.4.2.1.Team/ PO Performance

9.67.1. Team/ PO Performance will have following features which will be consolidated for team for details refer PO performance in PO Dashboard section.

9.67.1.1. RF Cost

9.67.1.2. Wrong Buy Count

9.67.1.3. Valuation Time

9.67.1.4. GRN discrepancy

9.67.1.5. Enquiry & Follow-up count

9.67.1.6. Valuation & Procurement counts

9.67.1.7. Funnel: Trade-in

9.67.1.8. Direct Purchase

9.67.1.9. Deal Fail Analysis

9.67.1.10. Lead times

9.67.2. PTL can switch over by clicking table icon to Team performance table view.

9.68. 10.4.2.2.Team Performance Table View

9.68.1. Team performance table view will show consolidated performance view of the all PO.

9.68.1.1. PO Name.

9.68.1.2. RF Cost difference.

9.68.1.3. Wrong Buy count.

9.68.1.4. GRN Discrepancy count.

9.68.1.5. Average Valuation time.

9.68.1.6. Total Enquiry

9.68.1.7. Total Valuation

9.68.1.8. Total Procurement

9.68.1.9. Direct Purchase count

9.68.1.10. Enquiry % of Target v/s Actual.

9.68.1.11. Follow-up % of Target v/s Actual.

9.68.1.12. Average lead time of Enquiry to Valuation.

9.68.1.13. Average lead time of Valuation to Procurement.

9.68.2. PTL can switch over by clicking chart icon to Team/ PO Performance view.

9.69. 10.4.3.Dashboard secondary

9.69.1. PTL Dashboard will be secondary dashboard available.

9.70. 10.4.3.1.RF Cost comparison

9.70.1. PTL will have consolidated data for all the PO in the team.

9.70.2. The data will be calculated for the vehicles procured by all the team PO.

9.70.3. For details refer RFC dashboard RF Cost comparison section.

9.71. 10.4.3.2.RF Cost to Buying Price Ratio

9.71.1. PTL will have consolidated data for all the PO in the team.

9.71.2. The data will be calculated for the vehicles procured by all the team PO.

9.71.3. For details refer RFC dashboard RF to BP Ratio section.

9.72. 10.4.3.3.SO Contribution

9.72.1. In Contribution and conversion section will have SO contribution counts.

9.72.1.1. Count of the New car SO will be shown who had sent the replacement enquiries.

9.72.1.2. Click on the count will open the tabular view of SO contribution (New car SO).

9.72.1.2.1. New car SO Name

9.72.1.2.2. New car enquiry Count

9.72.1.2.3. New car Sold Count

9.72.1.2.4. Replacement enquiry count created by SO

9.72.1.2.5. Replacement enquires converted to Trade-in.

9.72.1.2.6. Trade-in Percentage.

9.72.1.3. There will be interface defined which will get the new car so related information from UCTDMS/ NCTDMS system.

9.73. 10.4.3.4.SA Contribution

9.73.1. In Contribution and conversion section will have SA contribution counts.

9.73.1.1. Count of the SA (Service adviser) will be shown who had created service enquiry from TOPSERV.

9.73.1.2. Click on the count will open the tabular view of SA contribution.

9.73.1.2.1. Service Adviser Name

9.73.1.2.2. Created Service enquiries to U-Trust application / UCTDMS system.

9.73.1.2.3. Procurement done for the defined service enquiries.

9.73.1.2.4. Enquiry to procurement conversion ratio.

9.73.1.3. The interface will be defined with UCTDMS system, so the service enquiries created from TOPSERV will be available.

9.74. 10.4.3.5.WebEnquiry & Conversion

9.74.1. In Contribution and conversion section will have Web Conversion counts.

9.74.1.1. Web conversion count will be calculated based on following conditions

9.74.1.1.1. Enquiry

9.74.1.1.2. Conversion

9.74.1.2. Click on the count will show the tabular view of Web conversion.

9.74.1.3. Web conversion tabular view will have following details

9.74.1.3.1. Seller enquiry number

9.74.1.3.2. Vehicle information: Make, Model, Suffix

9.74.1.3.3. Assigned PO name

9.74.1.3.4. If Procured, then show Procurement status (Y/N)

9.74.1.3.5. New car information: New car Enquiry No, Model & Suffix

9.74.1.3.6. If converted to Trade-in in that case, show ‘Y’.

9.74.1.4. The web conversion will be specific to the seller enquiries having source type defined as Web.

9.75. 10.4.3.6.Finance Enquiry & Conversion

9.75.1. In Contribution and conversion section will have Finance Conversion counts

9.75.1.1. Finance conversion count will be calculated based on following conditions

9.75.1.1.1. Enquiry

9.75.1.1.2. Conversion

9.75.1.1.3. Based on the all conditions the count will be calculated.

9.75.1.2. Click on the count will show the tabular view of Finance conversion.

9.75.1.3. Finance conversion tabular view will have following details

9.75.1.3.1. Seller enquiry Number

9.75.1.3.2. TFS Vehicle details: Make, Model, Suffix, Current EMI

9.75.1.3.3. Updated RV

9.75.1.3.4. Upgrade Option 1: Model, Suffix, Scheme, Loan Amount, New EMI

9.75.1.3.5. Upgrade Option 2: Model, Suffix, Scheme, Loan Amount, New EMI

9.75.1.3.6. Seller Enquiry status

9.75.1.3.7. Converted to Trade-In

9.75.1.3.8. New car Enquiry Details: Enquiry Number, Date, Enquiry Status

9.75.1.3.9. New car Information: Model, Suffix

9.75.1.3.10. New car booked in that case booking details (New car model, Suffix)

9.75.1.3.11. New car SO Name

9.75.1.3.12. Zone, Dealer Group, Dealer location (In case of TKM Dashboard)

9.75.1.4. Interface already defined to create new car enquiry. New interface to be defined to get the new car enquiry and booking details

9.76. 10.5.STL Dashboard

9.76.1. STL Dashboard will be available to the STL (Sales Team Leader) users. Which will cover the features and actions based on the specific role

9.77. 10.5.1.Dashboard main

9.77.1. STL Dashboard will have following features

9.77.1.1. Status of Buyer Enquiry, Sales Orders and Delivery.

9.77.1.2. Today’s Activities.

9.77.1.3. Pending Follow-ups.

9.77.1.4. Action Items.

9.77.1.5. Pending Allocations & Self-Allocations.

9.77.1.6. Buyer enquiry source wise conversion

9.77.1.7. Stock data.

9.78. 10.5.1.1.Status of Buyer Enquiry, Sales Orders and Delivery

9.78.1. STL will have consolidated data for all the SO in the team.

9.78.2. For details refer SO section for status of Buyer Enquiry, Sales Orders and Delivery.

9.79. 10.5.1.2.Today’s Activities.

9.79.1. STL will have consolidated data for all the SO in the team.

9.79.2. For details refer SO section for status of Today’s Activities.

9.80. 10.5.1.3.Pending Follow-ups.

9.80.1. STL will have consolidated data for all the SO in the team.

9.80.2. For details refer SO section for status of Pending Follow-ups.

9.81. 10.5.1.4.Action Items.

9.81.1. STL will have consolidated data for all the SO in the team.

9.81.2. For details refer SO section for Action items.

9.82. 10.5.1.5.Pending Allocations & Self-Allocations

9.82.1. Pending Allocations & Self Allocations will have two sections.

9.82.1.1. Pending Allocations

9.82.1.1.1. Buyer enquiries create in system which STL need to assign / allocate to team SO, but not yet not allocated will be shown.

9.82.1.1.2. The pending allocations will show all pending allocations count.

9.82.1.1.3. Enquiry source wise pending allocations.

9.82.1.2. Self-Allocations

9.82.1.2.1. The non-allocated enquiries are self-assigned by team SO will be show.

9.82.1.2.2. Count of total self-allocated enquiries of Team SO

9.82.1.2.3. SO wise self-allocated enquires counts

9.82.1.2.4. Click will show the list of enquiries which are self-allocated by the specific SO.

9.83. 10.5.1.6.Buyer enquiry source wise conversion

9.83.1. STL will have consolidated data for all the SO in the team.

9.83.2. For details refer SO section for buyer enquiry source wise conversion bar chart.

9.84. 10.5.1.7.Stock data

9.84.1. Stock data will show the overview of the stock data to user.

9.84.1.1. Count of Fast-moving stock

9.84.1.1.1. Fast moving stock count will be calculated from stock.

9.84.1.1.2. Click on the count will show the stock statement listing for the fast-moving stock.

9.84.1.2. Count of Slow-moving stock

9.84.1.2.1. Slow moving stock count will be calculated from stock.

9.84.1.2.2. Click on the count will show the stock statement listing for the slow-moving stock.

9.84.1.3. Discount

9.84.1.3.1. Count will be calculated for the vehicles which have discount defined.

9.84.1.3.2. Click on the count will show the stock statement filtered for the discounted vehicles.

9.84.1.4. Promotions

9.84.1.4.1. Count will be calculated for the vehicles which have promotions defined.

9.84.1.4.2. Click on the count will show the stock statement filtered for the defined promotions.

9.84.1.5. Certification Lapsed (Refer SO Dashboard)

9.84.1.5.1. Count will show the already lapsed certifications for MTD.

9.84.1.5.2. Click on the count will show the certification list with lapsed data filter.

9.84.1.6. Procurement (Refer SO Dashboard)

9.84.1.6.1. Count will show the new procurements of the vehicles for MTD.

9.84.1.6.2. The count will be defined from the purchase confirmation data.

9.84.1.6.3. Click on the count will show the procurement list of the vehicles.

9.85. 10.5.2.Team Performance

9.85.1. Team/ SO Performance screen will give performance related counters and details for team SO.

9.85.2. STL will have consolidated data available for the team. STL can filter for specific SO and view the performance data of the selected SO.

9.86. 10.5.2.1.Team/ SO Performance

9.86.1. Team/ SO Performance will have following features which will be consolidated for team for details refer SO performance in SO Dashboard section.

9.86.1.1. Enquiry & Follow-up count

9.86.1.2. Sales Orders & Delivery counts

9.86.1.3. Discount Amount

9.86.1.4. Test Drive

9.86.1.5. Funnel: Retail data

9.86.1.6. Deal Fail Analysis

9.86.1.7. Orders Cancelled Analysis

9.86.1.8. Lead times

9.86.2. STL can switch over by clicking table icon ‘’ to Team performance table view.

9.87. 10.5.2.2.Team Performance Table View

9.87.1. Team performance table view will show consolidated performance view of the all SO.

9.87.1.1. SO Name

9.87.1.2. Total Enquiry

9.87.1.3. Total Sales Order

9.87.1.4. Total Delivery

9.87.1.5. Enquiry % of Target v/s Actual.

9.87.1.6. Sales Order % of Target v/s Actual.

9.87.1.7. Delivery % of Target v/s Actual.

9.87.1.8. Average discount specified by SO

9.87.1.9. Average lead time of Enquiry to Sales order.

9.87.1.10. Average lead time of Sales order to Delivery.

9.87.2. STL can switch over by clicking chart icon ‘’ to Team/ SO Performance view.

9.88. 10.5.3.1.Refurbishment

9.88.1. The refurbishment section will have two parameters

9.88.1.1. RF Not started: The RF Not started count will be shown.

9.88.1.1.1. RF Not started count will be calculated based on following conditions.

9.88.1.1.2. Click on the count will show the RF request list which do not have any job card data.

9.88.1.2. RF Completed: The RF Completed count will be shown.

9.88.1.2.1. RF Completed count will be calculated based on following conditions.

9.88.1.2.2. Click on the count will show the RF request list which will have the completed status defined.

9.89. 10.5.3.2.Certification

9.89.1. The Certification section will show four parameters.

9.89.1.1. Certification Lapsed: The count will show the certifications which are lapsed.

9.89.1.1.1. Count will be calculated based on the Certification expiry date and vehicles available in stock.

9.89.1.1.2. Click on count will show the certification list with lapsed data filter.

9.89.1.2. Pending Certification (UCM): The count will show the certification request are not approved by UCM.

9.89.1.2.1. Count will be calculated based on the request made and not approved by UCM.

9.89.1.2.2. Click on count will show the certification list filter of approval status.

9.89.1.3. Pending Certification (TKM): The count will show the certification request are not approved by TKM Zonal.

9.89.1.3.1. Count will be calculated based on the request made and not approved by TKM Zonal.

9.89.1.3.2. Click on count will show the certification list filter of approval status.

9.89.1.4. Certification Expiring in 7 Days: The count will show the certifications which are going to be lapsed in next 7 days.

9.89.1.4.1. Count will be calculated based on the certification expiry date and vehicles available in stock.

9.89.1.4.2. Click on count will show the certification list with expiry date filter (Expiry date <= Today +7 Days)

9.90. 10.5.3.3.Stock Actions

9.90.1. The Stock Actions section will show three parameters.

9.90.1.1. Pending Selling Price: The count will show the stock vehicles which are not updated with selling price.

9.90.1.1.1. Count will be calculated based on following conditions

9.90.1.1.2. Click on count will show stock statement list with filter of pending selling price.

9.90.1.2. Pending Photo: The count will show the stock vehicles which are not updated with vehicle photo.

9.90.1.2.1. Count will be calculated based on following conditions

9.90.1.2.2. Click on count will show stock statement list with filter of Image or 360 pending.

9.90.1.3. Pending Website Display: The count will show stock vehicles which are not pushed to website.

9.90.1.3.1. Count will be calculated based on following conditions

9.90.1.3.2. Click on count will show stock statement list with filter of Not Pushed to Website or Rejected for Website.

9.91. 10.5.3.4. Stock summary

9.91.1. The Stock summary data will show stock list arranged by aging days.

9.91.1.1. Aging days will be defined as (Ageing Days will be considered from purchased date to current date)

9.91.1.1.1. <30 Days

9.91.1.1.2. 31- 45 Days

9.91.1.1.3. 46 – 60 Days

9.91.1.1.4. 61 – 90 Days

9.91.1.1.5. >90

9.91.1.2. Stock list will be defined as

9.91.1.2.1. Toyota

9.91.1.2.2. Non-Toyota

9.91.1.2.3. Certified.

9.91.1.3. Booked Vehicles shown as well.

9.91.1.4. Click will show stock inventory screen with the selected filters applied.

9.92. 10.5.3.5.Breakeven

9.92.1. The Breakeven section will show two parameters.

9.92.1.1. In 1 Week: The count will show the stock vehicles which are going to have breakeven in next 1 week.

9.92.1.1.1. Count will be calculated based on following conditions

9.92.1.1.2. Click on count will show stock breakeven listing screen.

9.92.1.2. In 2 Week: The count will show the stock vehicles which are going to have breakeven in next 2 week.

9.92.1.2.1. Count will be calculated based on following conditions

9.92.1.2.2. Click on count will show stock breakeven listing screen.

9.93. 10.5.3.6.Web Enquiry & Conversion

9.93.1. In Conversion section will have Web Conversion counts.

9.93.1.1. Web conversion count will be calculated based on following conditions

9.93.1.1.1. Enquiry

9.93.1.1.2. Conversion

9.93.1.2. Click on the count will show the tabular view of Web conversion.

9.93.1.3. Web conversion tabular view will have following details

9.93.1.3.1. Buyer enquiry number

9.93.1.3.2. Vehicle information: Make, Model, Suffix

9.93.1.3.3. Assigned SO name

9.93.1.3.4. Order No & Date

9.93.1.3.5. Delivery No & Date

9.93.1.4. The web conversion will be specific to the buyer enquiries having source type defined as Web.

9.94. 10.5.3.7.Finance Enquiry & Conversion

9.94.1. In Contribution and conversion section will have Finance Conversion counts.

9.94.1.1. Finance Conversion count will be calculated based on following conditions

9.94.1.1.1. Enquiry

9.94.1.1.2. Conversion

9.94.1.2. Click on the count will show the tabular view of Finance conversion.

9.94.1.3. Finance conversion tabular view will have following details

9.94.1.3.1. Buyer Enquiry Number

9.94.1.3.2. Sold/Selected Vehicle details: Make, Model, Suffix

9.94.1.3.3. Buyer Enquiry status

9.94.1.3.4. Sales Order number & Date

9.94.1.3.5. TFS Loan No / Lead Number

9.94.1.3.6. TFS Loan status

9.94.1.3.7. SO Name

9.95. 10.6. UCM dashboard

9.95.1. UCM Dashboard UCM Dashboard will be available to the UCM (Use Car Manager) users. Which will cover the features and actions based on the specific role.

9.96. 10.6.1.Dashboard main

9.96.1. UCM Dashboard will have following features

9.96.2. Pending RF Approvals

9.96.3. Pending Certification Approvals

9.96.4. Pending Selling price

9.96.5. Hot Seller Enquiry & Hot Buyer Enquiry

9.96.6. Pending Allocations Seller Enquiry

9.96.7. Pending Allocations Buyer Enquiry

9.96.8. Pending Website Display

9.96.9. Photo Pending

9.96.10. Certification Lapsed

9.96.11. Certification Expiring in 7 Days

9.96.12. RF Not Started

9.96.13. Name Transfer

9.96.14. Wanted List

9.96.15. Orders Cancelled

9.96.16. Deal Fail Seller Enquiry

9.96.17. Deal Fail Buyer Enquiry

9.96.18. Dropped Seller Enquiry

9.96.19. Dropped Buyer Enquiry

9.96.20. Discount & Promotions

9.97. 10.6.1.1.Pending RF Approvals

9.97.1. The Pending RF Approval count will be shown.

9.97.1.1. RF Approval count will be calculated based on following conditions.

9.97.1.1.1. RF Request made by RFC

9.97.1.1.2. RF request not approved by UCM

9.97.1.2. Click on the count will show the RF request list which are not yet approved by UCM.

9.98. 10.6.1.2.Pending Certification Approvals

9.98.1. The count will show the certification request are not approved by UCM.

9.98.1.1. Count will be calculated based on the request made and not approved by UCM.

9.98.1.2. Click on count will show the certification list filter of approval status.

9.99. 10.6.1.3.Pending Selling price

9.99.1. The count will show the stock vehicles which are not updated with selling price.

9.99.1.1. Count will be calculated based on following conditions

9.99.1.1.1. Vehicles retail eligibility decision is made, classified as retail vehicle.

9.99.1.1.2. Selling price is pending.

9.99.1.2. Click on count will show stock statement list with filter of pending selling price.

9.100. 10.6.1.4.Hot Seller Enquiry

9.100.1. The count will show the consolidated data of all PTL & PO.

9.100.1.1. The count of the all seller enquiries which are having enquiry status hot will be shown.

9.100.1.2. Click on the count will show the enquiry listing which are having enquiry status hot

9.101. 10.6.1.5.Hot Buyer Enquiry

9.101.1. The count will show the consolidated data of all STL & SO.

9.101.1.1. The count of the all buyer enquiries which are having enquiry status hot will be shown.

9.101.1.2. Click on the count will show the enquiry listing which are having enquiry status hot

9.102. 10.6.1.6.Pending Allocations Seller Enquiry

9.102.1. The count will show the consolidated data of PTL & PO

9.102.1.1. The count of the all seller enquiries which are not yet allocated.

9.102.1.2. Click will show all pending allocation seller enquiry list.

9.103. 10.6.1.7.Pending Allocations Buyer Enquiry

9.103.1. The count will show the consolidated data of STL & SO

9.103.1.1. The count of the all buyer enquiries which are not yet allocated.

9.103.1.2. Click will show all pending allocation buyer enquiry list.

9.104. 10.6.1.8.Pending Website Display

9.104.1. The count will show stock vehicles which are not pushed to website.

9.104.1.1. Count will be calculated based on following conditions

9.104.1.1.1. Vehicles retail eligibility decision is made, classified as retail vehicle.

9.104.1.1.2. Not Pushed to Website or Rejected for Website

9.104.1.2. Click on count will show stock statement list with filter of Not Pushed to Website or Rejected for Website.

9.105. 10.6.1.9.Photo Pending

9.105.1. The count will show the stock vehicles which are not updated with vehicle photo.

9.105.1.1. Count will be calculated based on following conditions

9.105.1.1.1. Vehicles retail eligibility decision is made, classified as retail vehicle.

9.105.1.1.2. Image or 360 is pending

9.105.1.2. Click on count will show stock statement list with filter of Image or 360 pending.

9.106. 10.6.1.10.Certification Lapsed

9.106.1. The count will show the certifications which are lapsed.

9.106.1.1. Count will be calculated based on the Certification expiry date and vehicles available in stock.

9.106.1.2. Click on count will show the certification list with lapsed data filter.

9.107. 10.6.1.11.Certification Expiring in 7 Days

9.107.1. The count will show the certifications which are going to be lapsed in next 7 days.

9.107.1.1. Count will be calculated based on the certification expiry date and vehicles available in stock.

9.107.1.2. Click on count will show the certification list with expiry date filter (Expiry date <= Today +7 Days)

9.108. 10.6.1.12.RF Not Started

9.108.1. The RF Not started count will be shown.

9.108.1.1. RF Not started count will be calculated based on following conditions.

9.108.1.1.1. RF request is approved by UCM

9.108.1.1.2. Job card data is not available / Job card start date is not defined.

9.108.1.2. Click on the count will show the RF request list which do not have any job card data.

9.109. 10.6.1.13.Name Transfer

9.109.1. The count will show the consolidated data of STL & SO

9.109.1.1. The count of pending name transfer will be calculated based on the vehicles which has delivery note generated and name transfer is not confirmed.

9.109.1.2. Click on the count will show the name transfer list.

9.110. 10.6.1.14.Wanted List

9.110.1. The wanted list will have option to add new vehicle, refer buyer enquiry where adding vehicle to wanted list is explained in detail with screen.

9.110.2. Count of the wanted list will show vehicles added in the wanted list.

9.110.3. Click on the count will show the wanted list screen.

9.110.4. Vehicle added to wanted list will be available for 45 days from date of entry. After 45 days the vehicle will be automatically removed from the wanted list.

9.110.5. The wanted list data will be specific to dealer location only. PTL, STL and UCM will have option to reset the wanted list or remove vehicles from the wanted list.

9.111. 10.6.1.15.Orders Cancelled

9.111.1. The count will show the consolidated data of STL & SO

9.111.2. Refer SO performance section for order cancelled details.

9.112. 10.6.1.16.Deal Fail Seller Enquiry

9.112.1. The count will show the consolidated data of PTL & PO

9.112.2. Refer PO performance section for deal fail Seller Enquiry.

9.113. 10.6.1.17.Deal Fail Buyer Enquiry

9.113.1. The count will show the consolidated data of STL & SO

9.113.2. Refer SO performance section for deal fail Buyer Enquiry.

9.114. 10.6.1.18.Dropped Seller Enquiry

9.114.1. The count will show the consolidated data of PTL & PO

9.114.2. Refer PO performance section for dropped Seller Enquiry details.

9.115. 10.6.1.19.Dropped Buyer Enquiry

9.115.1. The count will show the consolidated data of STL & SO

9.115.2. Refer SO performance section for dropped Buyer Enquiry details.

9.116. 10.6.1.20.Discount

9.116.1. Count will be calculated for the vehicles which have discount defined.

9.116.2. Click on the count will show the stock statement filtered for the discounted vehicles.

9.117. 10.6.1.21.Promotions

9.117.1. Count will be calculated for the vehicles which have promotions defined.

9.117.2. Click on the count will show the stock statement filtered for the defined promotions.

9.118. 10.6.2.Procurement Dashboard

9.118.1. UCM will have Procurement Dashboard and Team performance dashboard available which will be consolidated data of all PO & PTL.

9.119. 10.6.3.Retail Dashboard

9.119.1. UCM will have Retail Dashboard and Team performance dashboard available which will be consolidated data of all SO & STL.

9.120. 10.6.4.Dashboard 2

9.120.1. UCM Dashboard will have secondary dashboard available.

9.120.1.1. Stock (Inventory Analysis)

9.120.1.2. Breakeven

9.120.1.3. Lead times

9.120.1.4. Trade-in

9.120.1.5. Trade-in analysis

9.120.1.6. Conversion

9.121. 10.6.4.1.Stock Inventory Analysis

9.121.1. Stock inventory analysis will show stock list arranged by aging days including vehicle counts and inventory costs.

9.121.2. The Stock inventory analysis data will show stock list arranged by aging days.

9.121.2.1. Aging days will be defined as (Ageing Days will be considered from purchased date to current date)

9.121.2.1.1. <30 Days, 31- 45 Days, 46 – 60 Days, 61 – 90 Days, >90

9.121.2.2. Stock counts will be defined and grouped followings

9.121.2.2.1. Toyota, Non-Toyota & Certified.

9.121.2.3. Stock count wise Total Inventory cost.

9.121.3. The summation of the inventory cost will be shown and that is divided in three parts.

9.121.3.1. Total Inventory Cost

9.121.3.2. Retail Inventory Cost

9.121.3.3. Wholesale Inventory Cost

9.121.3.4. Click on the total costs will show the tabular information in pop-up form. Following information will be shown.

9.121.3.4.1. Make, Model, Average days & Average cost.

9.121.3.5. Group by Toyota & Non-Toyota

9.121.3.5.1. For Toyota, Inventory cost for all models to be shown.

9.121.3.5.2. For Non-Toyota, Inventory cost for top 10 models to be shown.

9.122. 10.6.4.2.Stock Breakeven

9.122.1. Stock breakeven details will be shown. Refer STL dashboard breakeven section for the details.

9.122.2. Below the count the details to be shown as followings.

9.122.2.1. Toyota (Counts)

9.122.2.2. Non-Toyota (Counts)

9.123. 10.6.4.3.Lead Times

9.123.1. The lead times section will show lead times for three parameters

9.123.1.1. Procurement Lead Time.

9.123.1.1.1. Counts of Seller enquiries, Valuations and Procurements defined each stage wise.

9.123.1.1.2. Each stage wise average lead time will be calculated.

9.123.1.1.3. Each stage wise Conversion percentages.

9.123.1.2. Retail Lead Time.

9.123.1.2.1. Counts of Buyer enquiries, Sales Orders and Delivery defined each stage wise.

9.123.1.2.2. Each stage wise average lead time will be calculated.

9.123.1.2.3. Each stage wise Conversion percentages.

9.123.1.3. Certified Lead Time.

9.123.1.3.1. The certified vehicles related data will be calculated.

9.123.1.3.2. Counts of Buyer enquiries, Sales Orders and Delivery defined each stage wise.

9.123.1.3.3. Each stage wise average lead time will be calculated. Each stage wise Conversion percentages.

9.124. 10.6.4.4.Trade-In

9.124.1. The bar char will be shown for Trade-in details and ratio of new car models.

9.124.1.1. Model wise Trade-In Numbers & Percentages

9.124.1.2. Trade-In Percentages will be calculated based on used cars purchased / procured against the total number of new car model sold.

9.124.1.3. Direct purchase related seller enquiry will not be considered in Trade-In.

9.124.1.4. Filters to be defined which will allow user to Further drill down to Suffix level.

9.124.1.5. The interface to be defined for UCTDMS/NCTDMS for getting new car monthly sale data, new car sale data need to have model and suffix details, so filters can be applied.

9.125. 10.6.4.5.Trade-In Analysis

9.125.1. The bar char will be shown for Trade-In Analysis.

9.125.1.1. Trade-In Analysis to be shown for all Toyota models.

9.125.1.2. Analysis to be done as followings.

9.125.1.2.1. All Toyota Model sold (New car sale)

9.125.1.2.2. Used cars purchased / procured to be grouped and top 7 Models to be derived.

9.125.1.2.3. New Car model against top 7 procured models.

9.125.1.3. Sold Toyota Model Through Trade-In

9.125.1.3.1. Buy Old cars

9.126. 10.6.4.6.Web Conversion

9.126.1. Consolidated data will be shown for PTL & STL.

9.126.2. Refer web conversion section of PTL and STL dashboard.

9.126.3. For UCM there will be Seller web conversion and Buyer web conversion buttons available.

9.127. 10.6.4.7.Finance Conversion

9.127.1. Consolidated data will be shown for PTL & STL. Refer web conversion section of PTL and STL dashboard.

9.127.2. For UCM there will be Seller web conversion and Buyer web conversion buttons available.

9.128. 10.6.5.Dashboard Funnels

9.128.1. UCM Dashboard will have Funnel dashboard.

9.128.1.1. Purchase section will have two funnels & two table.

9.128.1.1.1. Table F/A/R: F, A & R Percentages to be shown for MTD data.

9.128.1.1.2. Funnel 1: Replacement to Trade-In conversions.

9.128.1.1.3. Funnel 2: Total Purchase to Certification conversions.

9.128.1.1.4. Table 1

9.128.1.1.5. Table 2

9.128.1.2. Sales section will have one funnel and one table.

9.128.1.2.1. Funnel 1: Sale – Retail conversion.

9.128.1.2.2. Table 1

9.129. 10.6.6.Dashboard 3

9.129.1. UCM Dashboard will have secondary dashboard available.

9.130. 10.6.6.1.RF Lead Time

9.130.1. RF Lead time bar chart will be shown. Refer RFC dashboard RF Lead time section for more details.

9.131. 10.6.6.2.RF Cost

9.131.1. RF Cost bar chart will be shown. Refer RFC dashboard RF Cost section for more details.

9.132. 10.6.6.3.RF Cost Comparison

9.132.1. RF Cost Comparison bar chart will be shown. Refer RFC dashboard RF Cost Comparison section for more details.

9.133. 10.6.6.4.Profit Data

9.133.1. All Toyota Models data to be shown

9.133.1.1. Toyota Certified

9.133.1.2. Toyota Non-Certified

9.133.2. For Non-Toyota Top seven selling models.

9.133.3. Profit data Tabular view will be shown which will show following details

9.133.3.1. Make

9.133.3.2. Model

9.133.3.3. Sold count/ Numbers (Delivery Note count)

9.133.3.4. Average Profit

9.133.3.4.1. Actual Margin to be considered.

9.133.3.4.2. Margin = Sell price (Invoice Unit price from UCTDMS) – [ Buying price + Actual RF Cost + Average Inventory cost]

9.133.4. RF Cost (Actual)

9.134. 10.6.6.5.Survey Results

9.134.1. Survey Result summary data will be shown. Which will have following details.

9.134.1.1. Module Name: Valuation, Procurement & Buyer enquiry

9.134.1.2. Total Feedback count

9.134.1.3. Feedback: Happy, Neutral, Not-Happy.

9.134.1.4. Feedback count and percentages against total.

9.134.2. Feedback summary will be shown in tabular format. Click on specific module / table cell the detail report will be shown.

9.134.3. Detail report will have following information.

9.134.3.1. Procurement & Valuation Module

9.134.3.1.1. PO Name, PTL Name

9.134.3.1.2. Customer Name, Registration Number

9.134.3.1.3. Vehicle Information: Make, Model, Year

9.134.3.1.4. Feedback & Remarks

9.134.3.2. Buyer enquiry Module

9.134.3.2.1. SO Name, STL Name

9.134.3.2.2. Customer Name

9.134.3.2.3. Vehicle Information: Make, Model, Year

9.134.3.2.4. Feedback & Remarks

9.135. 10.7.Group Head Dashboard

9.135.1. Group Head Dashboard will be available to the Group head users. Which will cover the features and actions based on the specific role.

9.135.2. Group head dashboard will have consolidated data of the UCM dashboard.Group head will have filter for UCM / Dealer Location.

9.136. 10.8.TKM Dashboard (Sub-Zone, Zone & HO)

9.136.1. TKM Dashboards will be available to Sub-Zone, Zone and HO users.

9.136.2. The UCM & Group head dashboard will be consolidated and available TKM Dashboards.

9.136.2.1. Filters

9.136.2.1.1. Sub-Zone will have filter for Dealer location / Dealer group which are part of sub-zone team.

9.136.2.1.2. Zone will have filter for Sub zone.

9.136.2.1.3. HO will have filters for Zone & All India data.

9.137. 10.8.1. Dashboard main

9.137.1. TKM Dashboard will have following features

9.137.1.1. Certification Lapsed. (Refer RFC Dashboard)

9.137.1.1.1. Click will show the intermediate screen which will have following items,

9.137.1.2. Pending Certification Approvals (Zone): Count

9.137.1.2.1. Click will show the intermediate screen which will have following items,

9.137.1.3. Hot Seller Enquiry

9.137.1.3.1. Click will show the intermediate screen which will have following items,

9.137.1.4. Hot Buyer Enquiry

9.137.1.4.1. Click will show the intermediate screen which will have following items,

9.137.1.5. Pending Allocations Seller Enquiry

9.137.1.5.1. Click will show the intermediate screen which will have following items,

9.137.1.6. Pending Allocations Buyer Enquiry

9.137.1.6.1. Click will show the intermediate screen which will have following items,

9.137.1.7. Pending Website Display

9.137.1.7.1. Click will show the intermediate screen which will have following items,

9.137.1.8. Photo Pending

9.137.1.8.1. Click will show the intermediate screen which will have following items,

9.137.1.9. Name Transfer

9.137.1.9.1. Click will show the intermediate screen which will have following items,

9.137.1.10. Orders Cancelled

9.137.1.10.1. Click will show the intermediate screen which will have following items,

9.137.1.11. Deal Fail Seller Enquiry

9.137.1.11.1. Click will show the intermediate screen which will have following items,

9.137.1.12. Deal Fail Buyer Enquiry

9.137.1.12.1. Click will show the intermediate screen which will have following items,

9.137.1.13. Dropped Seller Enquiry

9.137.1.13.1. Click will show the intermediate screen which will have following items,

9.137.1.14. Dropped Buyer Enquiry

9.137.1.14.1. Click will show the intermediate screen which will have following items,

9.137.2. TKM Dashboard will have all the summarized data consolidated.

9.138. 10.8.2 Procurement Dashboard

9.138.1. TKM Dashboard will have procurement dashboard summarized and consolidated at UCM / Group head level.

9.138.1.1. Click will show the intermediate screen which will have following items,

9.138.1.1.1. Dealer Name

9.138.1.1.2. Dealer Location

9.138.1.1.3. Count

9.138.2. TKM Dashboard the all graphs will be show summarized data for view.

9.138.3. The tabular data will be summarized and from TKM Dashboard the download options will be there instead of view. i.e. PO Performance tabular view.

9.139. 10.8.3. Retail Dashboard

9.139.1. TKM Dashboard will have retail dashboard summarized and consolidated at UCM / Group head level.

9.139.1.1. Click will show the intermediate screen which will have following items,

9.139.1.1.1. Dealer Name

9.139.1.1.2. Dealer Location

9.139.1.1.3. Count

9.139.1.2. TKM Dashboard the all graphs will be show summarized data for view.

9.139.1.3. The tabular data will be summarized and from TKM Dashboard the download options will be there instead of view. i.e. SO Performance tabular view.

9.140. 10.8.4. Other Dashboard Data

9.140.1. TKM Dashboard will have following data summarized and consolidated at UCM / Group head level.

9.140.1.1. Stock

9.140.1.2. Lead Time

9.140.1.3. Trade-in

9.140.1.4. Trade-in Analysis

9.140.1.5. Funnels

9.140.1.6. RF

9.140.1.7. Profit (Refer UCM Dashboard – Profit)

9.140.1.8. Survey (dealer Level)

9.141. 10.8.5.RV (Residual Value) Report

9.141.1. TKM Dashboard will have section defined for RV Report.

9.141.1.1. RV Report will be calculated for YTD Data.

9.141.1.2. RV Report will have filters as followings.

9.141.1.2.1. Zone

9.141.1.2.2. Sub-Zone

9.141.1.2.3. Competition

9.141.1.3. 5 Year data to be shown based on ex-showroom price of current year.

9.141.1.4. Data to be calculated based on procured vehicles. (Old year data to be considered from UCTMDS).

9.141.1.5. Only retails classified vehicles to be considered.

9.141.1.6. RV Report will be prepared against procured price of vehicles.

9.141.1.7. In masters Toyota model wise competition vehicles to be defined.

9.141.1.8. For RV Report the inputs which are required will be uploaded from the admin website.

9.141.1.8.1. Competition wise ex showroom prices per Sub-Zone

9.141.1.9. This data will be processed as batch process and will be available to TKM Dashboard.

9.142. 10.8.6.TKM Certification Revenue

9.142.1. TKM Dashboard will have section defined for review TKM Certification Revenue.

9.142.1.1. In masters each Toyota Model wise Certification charges will be defined. If data available from UCTDMS then to be get from UCTDMS otherwise Master to be created for the inputs.

9.142.1.2. Each Toyota Model wise data to be shown.

9.142.1.3. Filters will be All India, Zone & Sub-Zone.

9.142.1.4. The tabular report will show following information

9.142.1.4.1. Toyota Model

9.142.1.4.2. Total Revenue

9.142.1.4.3. Total Numbers (Certifications applied)

9.142.1.4.4. Total Numbers Certified.

9.142.1.4.5. Percentage of Certified

9.143. 10.8.7.Top 10 & Bottom 10 Dealers

9.143.1. TKM Dashboard will have section defined for review top 10 and bottom 10 dealers.

9.143.1.1. All Dealers to be considered (Location wise)

9.143.1.2. Filters will be All India, Zone & Sub-Zone.

9.143.1.3. Tabular report will be shown based on following parameters

9.143.1.3.1. Trade-In numbers (Primary parameter for order)

9.143.1.3.2. Trade-In Ratio

9.143.1.3.3. Trade-In v/s Replacement Enquiry Ratio

9.143.1.3.4. Certification Ratio

9.143.1.3.5. Toyota Purchases (Including Retail & Wholesale)

9.143.1.3.6. Used Car Sale (Retail Sale)

9.144. 10.9.Dashboard Common Features

9.144.1. Mobile application will have MTD (Month to date) and YTD (Year to date) options available.

9.144.2. For each dashboard default selection will be MTD (Month to date).

9.144.3. For web application MTD, YTD and Year (old Year data will be applicable).

9.144.4. PO & SO will have data available only specific user only.

9.144.5. PTL Dashboard will have filter for PO. PTL will have team PO related data only.

9.144.6. STL Dashboard will have filter for SO. STL will have team SO related data only.

9.144.7. UCM Dashboard will filter for PTL for procurement data & STL filter for retail data. Including all team PTL and STL.

9.144.8. Group head dashboard will have Dealer location / UCM wise filter. (Generally, dealer location is mapped to the specific UCM). GH will have consolidated data of all group dealer / UCM.

9.144.9. TKM Sub-Zone, Zone and HO will have summarized data.

9.144.10. Intermediate screen for Dealer Group, Dealer location and Counts will be there.

9.144.11. Sub-Zone will have filter for Dealer location / Dealer group which are part of sub-zone team.

9.144.12. Zone will have filter for Sub zone.

9.144.13. HO will have filters for Zone, Sub zone & All India data.

9.145. 10.10.Business KPI

9.145.1. Business KPI reports will be available to TKM HO, Zone & Sub-Zone. It could be triggered from Menu item.

9.145.1.1. 8 in 1 Report is consolidated Business KPI report.

9.145.1.1.1. Trade-In Volume

9.145.1.1.2. Trade-In Ratio & Replacement Enquiry capturing

9.145.1.1.3. Seller Enquiry to Purchase

9.145.1.1.4. Valuations

9.145.1.1.5. Toyota Purchase & Certification

9.145.1.1.6. Used Car Sales

9.145.1.1.7. Stock Rotation Days (Avg.)

9.145.1.1.8. TFS penetration Ratio

9.145.1.2. Data dependency for Business KPI reports are followings.

9.145.1.2.1. Used Car DSR

9.145.1.2.2. Trade-in DSR

9.145.1.2.3. Volume Summary report

9.145.1.3. Manual entry to be defined in website.

9.145.1.3.1. Trade-In Ratio & Replacement Enquiry capturing

9.145.1.3.2. Used Car Sales

9.145.1.3.3. Stock Rotation Days (Avg.)

9.145.1.3.4. TFS penetration Ratio

9.145.1.4. All Manual entry of data there excel upload to be defined to upload the data and will be visible in website so modification for the data to be allowed.

9.145.1.5. Excel will have following format of data input.

9.145.1.5.1. U-Trust Dealer code

9.145.1.5.2. Dealer name

9.145.1.5.3. Dealer location

9.145.1.5.4. New car Dealer code

9.145.1.5.5. New car – MTD (Count of new car sale / Retail data): [5: N-Car Retail]

9.145.1.5.6. Trade-in Volume – Number input: [6: Trade-In Vol]

9.145.1.5.7. Total Retail: [29: Total Retail (From TFS shared data)]

9.145.1.5.8. TFS cases: [30: TFS cases (From TFS shared data)]

9.145.1.5.9. INF Dealers: [31: INF Dealers (From TFS shared data)]

9.145.1.6. 28: All U-Cars (From System calculated) – Calculation Logic

9.145.1.6.1. Report generation requires the pre-requisite data input to the system, once the data input is done with excel for the month, the report can be generated.

9.145.1.6.2. The data input can be done by TKM HO user. This is monthly report, TKM HO User will input the data and generate the monthly KPI reports, the data need to be stored month wise and other users will fetch the data and generate the pdf files.

9.145.1.7. Report Generate, View, Export & Printing

9.145.1.7.1. Website application / Desktop

9.145.1.7.2. Mobile Application

9.145.1.8. Business KPI reports will be available to TKM HO, Zone & Sub Zone.

9.145.1.8.1. Filters for TKM HO will be followings.

9.145.1.8.2. Filters for Zone / will be followings.

10. Common features

10.1. 12.1. Application roles & responsibility matrix

10.1.1. The application will have following roles defined in the system.

10.1.1.1. PO

10.1.1.2. PTL

10.1.1.3. RFC

10.1.1.4. SO

10.1.1.5. STL

10.1.1.6. EDP / Dealer Admin

10.1.1.7. UCM

10.1.1.8. Group Head

10.1.1.9. CEO/ DP

10.1.1.10. RM

10.1.1.11. TKM Sub Zone

10.1.1.12. TKM Zone

10.1.1.13. TKM ZO

10.1.1.14. Inventory Display Role (Only for inventory dashboard display permission).

10.1.2. Each role wise responsibility or permissions are defined

10.1.2.1. Refer page no 325- 329

10.2. 12.2.Application Menus

10.2.1. The application will have each role wise menu items defined

10.2.1.1. User role

10.2.1.1.1. PO

10.2.1.1.2. PTL

10.2.1.1.3. SO

10.2.1.1.4. STL

10.2.1.1.5. RFC

10.2.1.1.6. UCM/GH

10.2.1.1.7. TKM users

10.2.2. Each role wise user will have the specific set of menus available, if the user have multiple role in that case the consolidated menu will be visible with highest role permissions.

10.2.3. The Common Menu items which will be available to all the users.

10.2.3.1. U-Trust Library will have following items

10.2.3.1.1. Valuation tutorials: List of tutorial videos and images will be offline available to users.

10.2.3.1.2. Customer Education videos: List of videos will be available offline in the application.

10.2.3.1.3. Customer Testimonial: List of videos will be available offline in the application.

10.2.3.1.4. Journalist Blog: List of videos will be available offline in the application.

10.2.3.1.5. Training Manual: PDF file will be available to view, will open in default pdf viewer of the mobile application.

10.2.3.1.6. In case of web application all the content will be played from the server.

10.2.3.1.7. In TKM Admin the tutorial section management to be defined.

10.2.3.2. Notifications will have list of the notification which are sent in mobile application.

10.2.3.3. Support will have following items. (In details it will be defined for support & maintenance: Subject to change / Revise)

10.2.3.3.1. Request list

10.2.3.4. Create Support request / ticket

10.2.3.4.1. A new form will be opened.

10.2.3.4.2. Field would be title, description and image upload option (up to 5 images)

10.2.3.4.3. Submit button click will submit the request to support team.

10.2.3.5. Support request / ticket system to be defined during maintenance phase / proposal.

10.3. 12.3.Application Reports(As per discussions and finalization with Users)

10.3.1. Application reports will be available in the system which can be printed or exported to excel.

10.3.2. The report menu will be there in the application which have the reports accessible based on the user rights defined.

10.3.2.1. Report Name

10.3.2.1.1. Invoice Report.

10.3.2.1.2. Delivery note report.

10.3.2.1.3. Valuation Report.

10.3.2.1.4. Seller Enquiry Listing report.

10.3.2.1.5. Buyer Enquiry listing report.

10.3.2.1.6. PO performance report (Tabular view)

10.3.2.1.7. SO Performance report (Tabular View).

10.3.2.1.8. New Car SO Contribution report (tabular view)

10.3.2.1.9. SA (Service Adviser) Contribution report (tabular view)

10.3.2.1.10. RF Cost comparison (tabular view)

10.3.2.1.11. RF Cost (from Dashboard)

10.3.2.1.12. Profit Report

10.3.2.1.13. Trade-in Report Model wise(dashboard).

10.3.2.1.14. Trade in Analysis (dashboard) - Top 7 Model.

10.3.2.1.15. Funnels (UCM - Procurement and retail funnels)

10.3.2.1.16. KPI Report (8 in 1 report)

10.3.2.1.17. Survey output report in excel.

10.3.2.1.18. Display report

10.3.2.1.19. Stock Listing

10.3.2.1.20. Order Listing

10.3.2.1.21. RF Cost per Vehicle Report

10.3.2.1.22. Web conversion (Seller Enquiry)

10.3.2.1.23. Web conversion (Buyer Enquiry)

10.3.2.1.24. Finance Conversion (Seller)

10.3.2.1.25. Finance Conversion (Buyer)

10.3.2.1.26. TKM Dashboard Summary Report

10.3.2.1.27. RV Report

10.3.2.1.28. Certification List

10.3.3. TKM Users (Sub-Zone, Zone and HO) for all reports will have Filters of Zone, Sub Zone, Dealer Group, Dealer Name (Location

10.3.3.1. From Web site all reports can be viewed Export to Excel & PDF options.

10.4. 12.4.Calendar

10.4.1. PO & PTL Calendar

10.4.1.1. Enquiry Follow-up (planned)

10.4.1.1.1. Count will be shown

10.4.1.1.2. Tapping will open follow up list for the respective date.

10.4.1.2. Valuation Appointments (Planned)

10.4.1.2.1. Count will be shown

10.4.1.2.2. Tapping will open the appointment list for the respective date.

10.4.1.3. Procurement document check list items (to be collected)

10.4.1.3.1. Count will be shown (Total Count of checklist items which target date is on the defined day i.e. 5 documents for 2 procurements to be collected today then 5 will be shown today)

10.4.1.3.2. Tapping will open Pending Documents list which are scheduled / planned (enquiries i.e. procurement which has pending documents and target date is on defined day)

10.4.2. SO & STL Calendar

10.4.2.1. Enquiry Follow-up (planned)

10.4.2.1.1. Count will be shown

10.4.2.1.2. Click will open follow up list for the respective date.

10.4.2.2. Planned deliveries

10.4.2.2.1. Count will be shown

10.4.2.2.2. Click will open Deliveries list for the respective date.

10.4.2.3. Planned PDI

10.4.2.3.1. Count will be shown

10.4.2.3.2. Click will open PDI list for the respective date.

10.5. 12.5.Common Search

10.5.1. Common Search function will be accessible from “Application Menu”or“Dashboard”.

10.5.1.1. User can perform search operation by entering any or any combination of fields and pressing search button.

10.5.1.1.1. Vehicle Search (Reg. No.&Engine No.)

10.5.2. After entering three characters it will show the auto suggestions of Name(auto complete feature matching First Name & Last Name)

10.5.2.1. Example(If search as kunal)

10.5.2.1.1. Kunal Khan

10.5.2.1.2. Kunal Abraham

10.5.2.1.3. Kunal Vyas

10.5.3. Display Components (Displayed when Search is done)

10.5.3.1. Customer Card Snapshot

10.5.3.1.1. Title + First Name + Last Name

10.5.3.1.2. Contact No.

10.5.3.1.3. Email Address

10.5.3.1.4. Seller / Buyer

10.5.3.1.5. Tapping on customer card snapshot, will open respective customer card – seller / buyer screen.

10.5.3.2. Vehicle Card Snapshot

10.5.3.2.1. Reg. No.

10.5.3.2.2. Engine No.

10.5.3.2.3. Make, Model, Suffix and Year

10.5.3.2.4. Tapping on vehicle card snapshot, will open vehicle card screen. It will be same as described above in stock.

10.5.3.3. Procurement Timeline: (displays each stage of procurement and respective no. and date.)

10.5.3.3.1. Seller Enquiry: Seller Enquiry No. & Date

10.5.3.3.2. Valuation: Valuation No. & Date

10.5.3.3.3. Procurement: Purchase No. & Date

10.5.3.4. Retail Timeline(Displays each stage of retail and respective no. and date.)

10.5.3.4.1. Refurbishment: Refurbishment No. & Date

10.5.3.4.2. Order: Order No. & Date

10.5.3.4.3. Invoice: Invoice No. & Date

10.5.3.4.4. Delivery: Delivery Note No. & Delivery Note Date

10.6. 12.5.1.Customer Card –Seller

10.6.1. Customer Card Title:

10.6.1.1. Customer Card

10.6.1.2. Unique Customer Code.

10.6.1.2.1. Unique Customer Code will be generated based on combination

10.6.2. Close button

10.6.2.1. Tapping on it will close the screen.

10.6.3. Procurement Timeline

10.6.3.1. Timeline showing each stage of procurement with related information

10.6.3.1.1. Seller Enquiry: Date & Time

10.6.3.1.2. Valuation: Date & Time. Note: All PO valuations should be considered.

10.6.3.1.3. Procurement: Date & Time

10.6.4. Name Transferred (Label)

10.6.4.1. Indication if Name is Transferred for the sold vehicle i.e. Confirm to Seller status is selected in Name Transfer.

10.6.5. Customer Details:

10.6.5.1. Title, First Name & Last Name

10.6.5.2. Contact No.

10.6.5.3. Email Address

10.6.5.4. Seller Enquiry Source

10.6.6. Follow-up Timeline (link-button):

10.6.6.1. It is same as enquiry timeline except only follow-up details i.e. follow-up plan (plan / done, date-time, remarks)& actual details will be displayed here.

10.6.7. Negotiation History (link-button)

10.6.7.1. It is same as described above in Seller Enquiry module.

10.6.8. Valuation Summary

10.6.8.1. Same as described above in valuation module.

10.6.9. Procurement Details:

10.6.9.1. Header (Label): Sold Car Details

10.6.9.2. Vehicle Reg. No.

10.6.9.3. Purchase No.

10.6.9.4. Make, Model, Suffix and Year

10.6.9.5. Color

10.6.9.6. Odometer

10.6.9.7. Fuel Type

10.6.9.8. Purchase Date

10.6.9.9. PO Name

10.6.9.10. PTL Name

10.6.9.11. Buying (Purchase) Price

10.6.9.12. Owners:

10.6.9.12.1. Sr. No. (based on owner type i.e. sell order. For example, 1st owner will have number 1)

10.6.9.12.2. Name (First Name + Last Name)

10.6.9.12.3. Mobile No.

10.6.9.12.4. Email Address

10.6.10. N-Car (Trade-in Details) / U-Car (Exchange):

10.6.10.1. Header (Label): “New Car Details” if Trade-in enquiry. “Used Car (Exchanged) Details” if U-Car exchange enquiry.

10.6.10.2. Make, Model, Suffix & Year

10.6.10.3. Color

10.6.10.4. Fuel Type

10.6.10.5. SO Name

10.6.10.6. Likely Delivery Date

10.6.10.7. Order No.

10.6.10.8. Sale Date

10.6.10.9. U-Car Follow-up Remarks / N-Car Follow-up Remarks

10.6.11. Name – Transfer Details:

10.6.11.1. Header (Label): Name Transfer Details

10.6.11.2. Old Customer Details: Title + First Name + Last Name, Contact No., Email Address

10.6.11.3. New Customer Details: Title + First Name + Last Name, Contact No., Email Address

10.6.11.4. Name Transfer Status

10.6.12. Old Transactions:

10.6.12.1. Header (Label): Old Transactions

10.6.12.2. Reg. No.

10.6.12.3. Flag: Sold / Bought By Customer

10.6.12.4. Make, Model, Suffix and Year

10.6.12.5. Color

10.6.12.6. Fuel Type

10.6.12.7. Buying Price (Purchase Price) / Selling Price (Vehicle Sale Price: Invoice Amount)

10.6.12.8. Delivery Note and Delivery Date for vehicles bought by customer

10.7. 12.5.2.Customer Card –Buyer

10.7.1. Customer Card Title

10.7.1.1. Customer Card Title will be combination of two things.

10.7.1.1.1. Customer Card

10.7.1.1.2. Unique Customer Code.

10.7.2. Close button: Tapping on it will close the screen.

10.7.3. Retail Timeline: Timeline showing each stage of retail with related information

10.7.3.1. Buyer Enquiry: Date & Buyer Enquiry No.

10.7.3.2. Order: Date & Order No.

10.7.3.3. Invoice: Date & Invoice No.

10.7.3.4. Delivery: Delivery Note Date & Delivery Note No.

10.7.4. Customer Details

10.7.4.1. Title, First Name & Last Name

10.7.4.2. Contact No.

10.7.4.3. Email Address

10.7.4.4. Buyer Enquiry Source

10.7.5. Follow-up Timeline (link-button)

10.7.5.1. It is same as enquiry timeline except only follow-up details

10.7.5.1.1. Follow-up plan (plan / done, date-time, remarks) & actual details will be displayed here.

10.7.6. Negotiation History (link-button)

10.7.6.1. It is same as described above in Buyer Enquiry module.

10.7.7. View Vehicles

10.7.7.1. Following four buttons will be displayed. Tapping on each will open a popup / screen showing respective vehicle list.

10.7.7.1.1. Each item in the list will display Reg. No., Make, Model, Suffix, Year, Fuel Type, Color and Date

10.7.8. Order Details:

10.7.8.1. Header (Label): Bought Car Details

10.7.8.2. Vehicle Reg. No.

10.7.8.3. Make, Model, Suffix and Year

10.7.8.4. Color

10.7.8.5. Fuel Type

10.7.8.6. Order No.

10.7.8.7. Order Date

10.7.8.8. Likely Delivery Date

10.7.8.9. Sale Price (Invoice Amount)

10.7.8.10. SO Name

10.7.8.11. STL Name

10.7.9. U-Car (Exchange):

10.7.9.1. Header (Label): Trade-in (Used Car Exchange) Details

10.7.9.2. Reg. No.

10.7.9.3. Purchase No.

10.7.9.4. Make, Model, Suffix & Year

10.7.9.5. Color

10.7.9.6. Fuel Type

10.7.9.7. Purchase Date

10.7.9.8. PO Name

10.7.9.9. PTL Name

10.7.9.10. Sale Date

10.7.9.11. U-Car Last Follow-up Remarks

10.7.10. Name – Transfer Details:

10.7.10.1. Header (Label): Name Transfer Details

10.7.10.2. Old Customer Details( Title + First Name + Last Name, Contact No., Email Address)

10.7.10.3. New Customer Details( Title + First Name + Last Name, Contact No., Email Address)

10.7.10.4. Name Transfer Status

10.7.11. Old Transactions:

10.7.11.1. Header (Label): Old Transactions

10.7.11.2. Reg. No.

10.7.11.3. Flag: Sold / Bought By Customer

10.7.11.4. Make, Model, Suffix and Year

10.7.11.5. Color

10.7.11.6. Fuel Type

10.7.11.7. Buying Price (Purchase Price) / Selling Price (Vehicle Sale Price: Invoice Amount)

10.7.11.8. Delivery Note and Delivery Date for vehicles bought by customer

10.8. 12.6.Caller Snapshot

10.8.1. When any customer calls to PO / SO’s mobile no., if enquiry (seller / buyer) exists in the system for the customer (identification will be done based on mobile no.)

10.8.2. Customer Title, First Name, Last Name

10.8.3. Email Address

10.8.4. Flag: Seller / Buyer

10.8.5. Last Enquiry Details

10.8.5.1. Vehicle Details: Reg. No., Make, Model, Suffix and Year

10.8.5.2. Flag: valuation flag (only if seller enquiry)

10.8.5.3. Enquiry Date

10.8.5.4. Last Follow-up Remarks

10.8.5.5. Last Offered Price

10.8.5.6. New Car Follow up remarks (if trade-in enquiry)

10.9. 12.7.Survey& Feedback

10.9.1. In Web admin section there will be a survey management section defined which will have following questions to be available to view/ update.

10.9.1.1. Valuation

10.9.1.1.1. Professional & well mannered

10.9.1.1.2. Knowledgeable & could answer all your queries

10.9.1.1.3. Explanation of valuation & pricing

10.9.1.1.4. Price offered as per your expectation

10.9.1.2. Procurement

10.9.1.2.1. Professional & well mannered

10.9.1.2.2. Follow-up & Updating on status

10.9.1.2.3. Explanation of documents

10.9.1.2.4. Transparency in Deal

10.9.1.3. Buyer Enquiry

10.9.1.3.1. Vehicle availability

10.9.1.3.2. Display of vehicle

10.9.1.3.3. Understanding need & providing solution

10.9.2. When the specific events for the module get finished the SMS will be sent to the customer.

10.9.2.1. The SMS will have short URL link.

10.9.2.1.1. Web page visible to customer to give feedback.

10.9.3. Based on the module the questions will be available, and each question will have the specific input values define for Happy, Neutral and Un-happy.

10.9.4. In Comment box user can input remarks / comments if any.

10.9.5. Click on submit button the feedback will be registered for the users and thank you page will be visible.

10.9.6. The Link generated for user feedback will have specific enquiry number related details, so the feedback will be logged against the enquiry number (Seller enquiry / Buyer enquiry).

10.9.7. The feedback link will be available for 30 Days.

10.9.8. If customer already submitted feedback and click on the link in that case the thank you page will be visible to customer.

10.10. 12.8.Central Repository

10.10.1. Central Repository will be maintained for stock, certification, valuation images & videos.

10.10.2. Images will be approved / rejected by application maintenance team.

10.11. 12.9.Password Policy, Offline Data& Login Mechanism

10.12. 12.9.1.Offline Data

10.12.1. Lists:

10.12.1.1. Seller Enquiry: 50 + Today & Tomorrow's Follow-up

10.12.1.2. Buyer Enquiry: 50 Open enquiries

10.12.1.3. Valuation: 50 Hot Enquiries valuations (with captured images)

10.12.1.4. Procurement: 50 Hot Enquiries Procurement

10.12.2. New/Save:

10.12.2.1. Seller Enquiry: 10

10.12.2.2. Buyer Enquiry: 10

10.12.2.3. Valuations: 5 (with captured images)

10.12.2.4. Procurement: 5

10.12.3. Other Points:

10.12.3.1. Every night offline data need to be synched.

10.12.3.2. Manual and Auto both sync mechanism should be there.

10.12.3.3. Syncing preference: Go to CTDMS, In from CTDMS

10.12.3.4. On application download, all video & images should be downloaded. For every update, new version should be available.

10.12.3.4.1. On downloading the same, video & images would be updated.

10.12.3.5. Offline image capturing & captured images storage will be based on the device storage capacity.

10.12.3.5.1. Resolution for image capturing will be defined based on device finalization.

10.13. 12.9.2.Password Policy

10.13.1. Password Policy: Min 8 Char Alpha numeric + 1 special character (standard characters support) + 1 Capital.

10.13.2. Password Expiry: Every 60 Days

10.13.3. When a new user created a temporary password will be sent (24 hours limit) to user and with first login user need to change password.

10.14. 12.9.3.Login Mechanism

10.14.1. Login will be done based on User Id & Password.

10.14.2. Invalid login attempts - 5 allowed and for 24 hours user account will be locked (inactive).

10.14.3. Single instance login should be considered

10.14.4. Remains login - indefinite

10.14.5. Password Change & Logout facility should be there.

10.14.6. Forgot Password facility should be based on email.

10.15. 12.10.Email Share

10.15.1. For each report (from application) shared with customer/dealer in email via share option will have system email share functionality

10.15.1.1. Email will be sent from server and from dealer configured email address in dealer management. So, for following email share functionality, email will be sent from server and via dealer configured email address

10.15.1.1.1. Valuation report share with customer

10.15.1.1.2. Warranty booklet sharing with dealer and customer

10.15.1.1.3. Vehicle Display Card in Buyer Enquiry

11. Website Admin Features

11.1. Same URL will be created for dealer admin, TKM admin.

11.2. The modules will be accessible based on their login credentials.

11.2.1. User ID

11.2.2. Password

11.3. 13.1.Dealer Admin

11.3.1. Dealer Admin will have following accessibility / features

11.3.1.1. Users Management

11.3.1.2. Masters for Excel Upload

11.3.1.3. Cost Management for Selling Price

11.3.1.4. Configurations

11.3.1.5. Target Settings Screen

11.3.2. Dealer Admin can select specific dealer or all dealers where this setting will be applicable.

11.3.3. If Dealer is accessing these features as Dealer Admin, then he can only define / update settings for his own.

11.4. 13.1.1 Users Management

11.4.1. SC2 Not Available

11.4.1.1. Dealer Admin can manage (add/edit/view/activate/deactivate/delete) dealer users

11.4.1.2. User creation form will contain following form fields

11.4.1.2.1. Photo

11.4.1.2.2. First Name*

11.4.1.2.3. Middle Name

11.4.1.2.4. Last Name*

11.4.1.2.5. Mobile No.*

11.4.1.2.6. Email Address*

11.4.1.2.7. Role Assignment* (e.g. PO, PTL etc. Multiple Selection possible including Dealer Admin role)

11.4.1.2.8. User Id* (UCTDMS Id)

11.4.1.3. On successfully saving user (creating user) will send confirmation email to the created user with temporary password and it is valid for 24 hours

11.4.1.4. Following user actions will be done along with user creation:

11.4.1.4.1. Edit User (Link)

11.4.1.4.2. Activate / Deactivate User (Link)

11.4.1.4.3. Reset Password (link)

11.4.1.4.4. Delete User (link)

11.4.2. SC2 Available

11.4.2.1. User Management will have following features if SC2 is available

11.4.2.1.1. Role Assignment

11.4.2.1.2. Reset Password

11.4.2.1.3. Activate / Deactivate

11.5. 13.1.2 RF Cost Master

11.5.1. RF Cost List

11.5.1.1. Each item in the list will display following information

11.5.1.1.1. Body Type

11.5.1.1.2. RF Cost Upload Status (Y/N)

11.5.1.1.3. Update button (Open the same screen of Upload RF Cost with the body type already selected and read-only)

11.5.2. Upload RF Cost

11.5.2.1. Dealer Admin will select body type (Hatchback/ MPV/ Sedan/ SUV) and upload the excel file for RF cost for each body type

11.5.2.2. Sample file to upload will be downloaded

11.5.2.3. Once the file is uploaded, field mapping interface will be available where admin will map the db fields with the excel fields

11.5.2.4. Following fields will be mapped

11.5.2.4.1. Description

11.5.2.4.2. P2/B2

11.5.2.4.3. P3/B3

11.5.2.5. Based on matching description, respective (P2/B2, P3/B3) value will be uploaded

11.5.3. Sample file will contain following field

11.5.3.1. Description (All rows will be pre-filled). (Non-editable)

11.5.3.2. P2/B2 Header with Sample value for one description

11.5.3.3. P3/B3 Header with sample value for one description

11.5.4. Notes

11.5.4.1. Refer Annexure 4 Exterior RF Format for reference. CTDMS Checkpoint Name and CTDMS ID will be saved in db for CTDMS integrations. No-relevance for upload

11.5.4.2. P2 & B2 will be separate columns in db. However, only one value will be captured from the excel and will be replicated in both.

11.5.4.3. P2 & B3 will be separate columns in db. However, only one value will be captured from the excel and will be replicated in both

11.6. 13.1.3 Ex-ShowRoom Price : Toyota

11.6.1. list will show the Ex Showroom price for Toyota vehicles

11.6.2. Each item will contain following information

11.6.2.1. Model

11.6.2.2. Grade

11.6.2.3. Suffix

11.6.2.4. Fuel type

11.6.2.5. Exterior Color

11.6.2.6. Ex-Showroom Price

11.7. 13.1.4 Ex-ShowRoom Price : Non-Toyota

11.7.1. Ex Showroom Price List

11.7.1.1. Each item in the list will display following information:

11.7.1.1.1. Make

11.7.1.1.2. Model

11.7.1.1.3. Suffix

11.7.1.1.4. Fuel Type

11.7.1.1.5. Color

11.7.1.1.6. Year

11.7.1.1.7. Ex showroom price

11.7.2. Upload

11.7.2.1. Excel file upload will be done for definition of ex-show room price for Non-Toyota vehicle.

11.7.2.2. Option to download sample file will be provided

11.7.2.3. Once the file is uploaded, mapping interface will be provided for mapping the excel columns with db columns

11.7.2.4. Following fields will be mapped with excel columns

11.7.2.4.1. Make

11.7.2.4.2. Model

11.7.2.4.3. Suffix

11.7.2.4.4. Fuel Type

11.7.2.4.5. Color

11.7.2.4.6. Year

11.7.2.4.7. Ex showroom price

11.7.2.5. Based on matching make, model, suffix, fuel type, color and year; ex show room price will be stored.

11.7.2.6. Sample file will contain following columns:

11.7.2.6.1. Make (Pre-filled and non-editable)

11.7.2.6.2. Model (Pre-filled and non-editable)

11.7.2.6.3. Suffix (Pre-filled and non-editable)

11.7.2.6.4. Fuel Type (Pre-filled and non-editable)

11.7.2.6.5. Color (Pre-filled and non-editable)

11.7.2.6.6. Year (Latest, Pre-filled and non-editable)

11.7.2.6.7. Ex showroom price (Sample price for one row)

11.7.3. Notes:

11.7.3.1. Refer annexure 5 Ex showroom price format for details

11.8. 13.1.5 Cost Management for Selling Price

11.8.1. Inventory Cost Variable (%)

11.8.1.1. Percentage of buying price

11.8.1.2. This will be used for variable cost definition in break even. User can add/view/update this cost

11.8.1.3. This cost will be standard for all makes, models and suffixes.

11.8.2. Vehicle selling price configurations (List)

11.8.2.1. Each item in the list will display following information:

11.8.2.1.1. Make

11.8.2.1.2. Model

11.8.2.1.3. Suffix

11.8.2.1.4. Configurations

11.8.3. Add / Edit

11.8.3.1. User will select Make, Model (Optional) & Suffix (Optional) of the vehicle

11.8.3.2. Following cost configurations will be done for selling price definition of selected vehicle:

11.8.3.2.1. Inventory Cost

11.8.3.2.2. Admin Cost

11.8.3.2.3. Marketing Expense

11.8.3.2.4. Handling Cost

11.8.3.2.5. Margin

11.8.3.2.6. Ownership Transfer Fees

11.8.3.2.7. TCS (Tax collected source)

11.8.3.2.8. Insurance Expired Cost

11.8.4. Notes

11.8.4.1. User should be able to have the facility to define cost for one make and apply to other makes by selecting multiple make(s) or all makes (selecting this will select all makes). However, individual change can be done from the list

11.8.4.2. If model specific amount is not selected then cost defined for make will be applicable to all models. Same as make, there should be facility to define cost for one model and apply to other models by selecting multiple model(s) or all models. However, individual change can be done from the list.

11.8.4.3. If suffix specific amount is not selected then cost defined for make or make & model will be applicable to all suffixes. Same as make, there should be facility to define cost for one suffix and apply to other suffixes by selecting multiple suffixes or all suffixes. However, individual change can be done from the list

11.8.4.4. If inventory cost is already defined for selected make, model, suffix or any combination (i.e. make, make & model) while adding the configuration then value (cost) should be editable and the update will be done for the respective configuration.

11.9. 13.1.6 Configurations

11.9.1. Following configuration parameters will be defined by dealer admin

11.9.1.1. OTP / Mandatory for Seller Enquiry and Buyer Enquiry

11.9.1.2. Show ex showroom price in

11.9.1.2.1. Valuation Detail (Checkbox)

11.9.1.2.2. Display Report (checkbox)

11.9.1.3. N-Car dropped follow-up days

11.9.1.3.1. default is 2 days.

11.9.1.3.2. Admin can change it up to 5 days

11.9.1.4. Links for Local RTO (VIN) & Traffic Violations can be defined and managed by dealer admin

11.10. 13.1.7 Dealer Management

11.10.1. Admin can manage following information using dealer management:

11.10.1.1. Dealer Name (Read-only: It will come from CTDMS)

11.10.1.2. Location (Read-only: It will come from CTDMS)

11.10.1.3. Address (Read-only: It will come from CTDMS)

11.10.1.4. Dealer Email Address

11.11. 13.1.8 Target Settings

11.11.1. Target Settings defined for dealer level will be visible. Same as UCTDMS.

11.11.2. In Web application the target settings which are defined in UCTDMS system will be visible as read-only data.

11.12. 13.1.9 View Roles & Responsibility Matrix

11.12.1. Admin can view Roles & Responsibility Matrix specific to Dealer Group & Dealer Users.

11.13. 13.2 TKM Admin

11.13.1. TKM Admin will have following accessibility / features.

11.13.1.1. Users Management

11.13.1.2. Content Management

11.13.1.3. Template Management for TFS

11.13.1.4. Survey / Feedback Management

11.13.1.5. Valuation Features Upload

11.13.1.6. Body Type Mapping

11.13.1.7. Target Settings Screen with Filters Dealer Group & Dealer

11.13.1.8. Business KPI related input parameters

11.14. 13.2.1 Users Management

11.14.1. Users Management will be same as Dealer Users Management except here TKM Signature Upload and specific role assignment will be done along with TKM Admin.

11.14.2. TKM Signature Upload

11.14.2.1. Image Upload with following constraints

11.14.2.1.1. Formats

11.14.2.1.2. White background

11.14.2.1.3. image dimensions

11.14.2.1.4. image size

11.14.2.2. This will also show help text as :

11.14.2.2.1. Image should be matched with following standards

11.15. 13.2.2 Content Management(U Trust Library)

11.15.1. Content Management for following things

11.15.1.1. Valuation Tutorials: Videos & Images:

11.15.1.1.1. A central repository would be managed (folder structure).

11.15.1.1.2. Checkpoints / Fields list will be displayed with mapped video (url/path) and image (url/path)

11.15.1.1.3. Filter option will be provided to view only videos / images

11.15.1.1.4. Activate / Deactivate option would also be provided

11.15.1.1.5. Only activated video / image will be displayed in valuation module

11.15.1.1.6. Admin will select “Functional Checkpoint Name” and select the image and / or video from central repository

11.15.1.1.7. For other fields than functional check points (e.g. BSI / DRSC check), Admin can edit the video or image (select new video or image)

11.15.1.2. Customer Education Videos:

11.15.1.2.1. A central repository would be managed (folder structure).

11.15.1.2.2. Already uploaded videos (url/path) will be displayed in a list with title and description

11.15.1.2.3. Activate / Deactivate option would be provided

11.15.1.2.4. Only activated video will be displayed in application

11.15.1.2.5. Admin will define Name*, Description and select video*(from central repository)

11.15.1.3. Customer Testimonials Videos:

11.15.1.3.1. This will work same as Customer Education Videos

11.15.1.4. Journalist Blogs:

11.15.1.4.1. This will work same as Customer Education Videos.

11.15.1.5. Training Manual:

11.15.1.5.1. A central repository would be managed (folder structure)

11.15.1.5.2. Admin will select the pdf file to be used as Training Manual.

11.15.1.6. Animated Training Videos:

11.15.1.6.1. This will work same as Customer Education Videos.

11.15.1.7. TVCF (TV Adverts):

11.15.1.7.1. This will work same as Customer Education Videos

11.15.1.8. Miscellaneous:

11.15.1.8.1. This will work same as Customer Education Videos.

11.16. 13.2.3 Template Management for TFS

11.16.1. The template to be created which could be editable

11.16.2. The template yet to be shared.

11.16.3. We need to utilise the template and create HTML page / pdf file which will include following:

11.16.3.1. Customer name and mobile number

11.16.3.2. Some text (defined in template)

11.16.3.3. Upgrade option 1

11.16.3.4. Upgrade option 2

11.16.3.5. Existing Vehicle Reg. No.

11.16.3.6. Existing Vehicle Make, Model & Suffix

11.17. 13.2.4 Survey/Feedback Management

11.17.1. In Web admin section there will be a survey management section defined which will have following questions to be available to view/ update

11.17.2. The questions are defined for specific module as followings

11.17.2.1. Valuation

11.17.2.1.1. Professional & well mannered

11.17.2.1.2. Knowledgeable & could answer all your queries

11.17.2.1.3. Explanation of valuation & pricing

11.17.2.1.4. Price offered as per your expectation

11.17.2.2. Procurement

11.17.2.2.1. Professional & well mannered

11.17.2.2.2. Follow-up & Updating on status

11.17.2.2.3. Explanation of documents

11.17.2.2.4. Transparency in Deal

11.17.2.3. Buyer Enquiry

11.17.2.3.1. Vehicle availability

11.17.2.3.2. Display of vehicle

11.17.2.3.3. Understanding need & providing solution

11.17.3. Based on the defined questions, when the specific events for the module get finished the SMS will be sent to the customer. The SMS will have short URL link.

11.17.3.1. Example: “Thank you for your time, Valuation for KA01AB1234 is done by Venkatesh P (#9876543210). Help us to serve you better. click ABC Home Page - ABC.com, to give feedback.”

11.17.4. When customer click on the defined link, there will be a web page visible to customer to give feedback.

11.17.4.1. The web page / form will have following items

11.17.4.1.1. List of questions

11.17.4.1.2. Comment box

11.17.4.1.3. Submit button

11.17.4.2. Based on the module the questions will be available, and each question will have the specific input values define for Happy, Neutral and Un-happy

11.17.4.3. In Comment box user can input remarks / comments if any

11.17.4.4. Click on submit button the feedback will be registered for the users and thank you page will be visible

11.17.5. The Link generated for user feedback will have specific enquiry number related details, so the feedback will be logged against the enquiry number (Seller enquiry / Buyer enquiry).

11.17.6. The feedback link will be available for 30 Days

11.17.7. If customer already submitted feedback and click on the link in that case the thank you page will be visible to customer.

11.18. 13.2.5 Valuation Features Upload

11.18.1. This screen will display a single dropdown “Make” with search button

11.18.2. Searching the particular make will display following things:

11.18.2.1. Models & Features List (if highest variant for models already uploaded):

11.18.2.1.1. Each item in the list will display following information:

11.18.2.2. Upload button (To upload highest variant features for models):

11.18.2.2.1. Clicking on this will open a page where admin can upload highest variant features

11.18.2.2.2. Sample file can be downloaded in this case. That will contain following columns

11.18.2.2.3. Refer Annexure “Features File Format” for details on format.

11.18.2.2.4. Mapping Interface will be defined to map following fields with db fields:

11.19. 13.2.6 Body Type Mapping

11.19.1. Dealer Admin will select body type (Hatchback/ MPV/ Sedan/ SUV) and upload the excel file for Make & Model for each body type

11.19.2. Sample file to upload will be downloaded

11.19.3. Once the file is uploaded, field mapping interface will be available where admin will map the db fields with the excel fields

11.19.4. Following fields will be mapped:

11.19.4.1. Make

11.19.4.2. Model

11.19.5. Based on matching Body Type, respective Make & Model will be uploaded.

11.19.6. Sample file will contain following field:

11.19.6.1. Make

11.19.6.2. Model

11.19.7. Notes:

11.19.7.1. Refer Annexure 3 Body Type Format for reference. Body Type column is not required. No-relevance for upload

11.20. 13.2.7 Target Settings

11.20.1. Target Settings same as UCTDMS with filters of Dealer Group and Dealer

11.20.2. In Web application the target settings which are defined in UCTDMS system will be visible as read-only data

11.21. 13.2.8 Business KPI related input parameters

11.21.1. Business KPI reports will be available to TKM HO, Zone & Sub-Zone

11.21.2. It could be triggered from Menu item.

11.21.3. 8 in 1 Report is consolidated Business KPI report

11.21.3.1. Report will have following parts

11.21.3.1.1. Trade-In Volume

11.21.3.1.2. Trade-In Ratio & Replacement Enquiry capturing

11.21.3.1.3. Seller Enquiry to Purchase

11.21.3.1.4. Valuations

11.21.3.1.5. Toyota Purchase & Certification

11.21.3.1.6. Used Car Sales

11.21.3.1.7. Stock Rotation Days (Avg.)

11.21.3.1.8. TFS penetration Ratio

11.21.4. Data dependency for Business KPI reports are followings

11.21.4.1. Used Car DSR

11.21.4.2. Trade-in DSR

11.21.4.3. Volume Summary report

11.21.5. Manual entry to be defined in website

11.21.5.1. Trade-In Ratio & Replacement Enquiry capturing

11.21.5.1.1. 5: N-Car Retail (From New car Data)

11.21.5.1.2. 6: Trade-In Vol (From New car Data)

11.21.5.2. Used Car Sales

11.21.5.2.1. 23: Toyota Retail (From Volume Summary report)

11.21.5.3. Stock Rotation Days (Avg.)

11.21.5.3.1. 28: All U-Cars (From calculated)

11.21.5.4. TFS penetration Ratio

11.21.5.4.1. 29: Total Retail (From TFS shared data)

11.21.5.4.2. 30: TFS cases (From TFS shared data)

11.21.5.4.3. 31: INF Dealers (From TFS shared data)

11.21.5.5. All Manual entry of data there excel upload to be defined to upload the data and will be visible in website so modification for the data to be allowed.

11.21.6. Excel will have following format of data input

11.21.6.1. U-Trust Dealer code

11.21.6.2. Dealer name

11.21.6.3. Dealer location

11.21.6.4. New car Dealer code

11.21.6.5. New car – MTD (Count of new car sale / Retail data): [5: N-Car Retail]

11.21.6.6. Trade-in Volume – Number input: [6: Trade-In Vol]

11.21.6.7. Total Retail: [29: Total Retail (From TFS shared data)]

11.21.6.8. TFS cases: [30: TFS cases (From TFS shared data)]

11.21.6.9. INF Dealers: [31: INF Dealers (From TFS shared data)]

11.21.7. 28: All U-Cars (From System calculated) – Calculation Logic

11.21.7.1. Report generation requires the pre-requisite data input to the system, once the data input is done with excel for the month, the report can be generated.

11.21.7.2. The data input can be done by TKM HO user

11.21.7.3. his is monthly report, TKM HO User will input the data and generate the monthly KPI reports, the data need to be stored month wise and other users will fetch the data and generate the pdf files.

11.21.8. Report Generate, View, Export & Printing

11.21.8.1. Website application / Desktop

11.21.8.1.1. In Website application the 8 in 1 graph will be consolidated created and print can be done

11.21.8.1.2. Print need to be done on A3 Size paper

11.21.8.1.3. Export to PDF

11.21.8.1.4. Export to Excel for tabular data, graph will be exported as image.

11.21.8.2. Mobile Application

11.21.8.2.1. When Business KPI report is triggered from Menu, dropdown will have option to select the specific report

11.21.8.2.2. Selection of the report and generate report button click will generate and show the select KPI report.

11.21.8.2.3. In mobile application one report at time can be generated and viewed

11.21.8.2.4. Option to be provided to generate 8 in 1 report PDF

11.21.8.2.5. The request will be sent from mobile application and report will be generated on server and the PDF will be available on mobile application, so user can download or open from mobile application

11.21.8.2.6. The generated PDF will be accessible from Central repository server and will be available for 15 days, after 15 days the report will be deleted from central repository

11.21.9. Business KPI reports will be available to TKM HO, Zone & Sub Zone

11.21.9.1. Filters for TKM HO will be followings

11.21.9.1.1. All India

11.21.9.1.2. Zone

11.21.9.2. Filters for Zone / will be followings.

11.21.9.2.1. Dealer Group

11.21.9.2.2. Dealer

11.22. 13.2.9 View Roles & responsibility Matrix

11.22.1. Admin can view Roles & Responsibility Matrix specific to TKM Users

11.23. 13.2.10 U-Trust Application Usage

11.23.1. U-Trust Application Usage (Month-to-Date):

11.23.1.1. Total Logins done

11.23.1.2. Dealer & Dealer location

11.23.1.3. All Users login done: Count (Active users)

11.23.1.4. New Seller enquiries created: Counts

11.23.1.5. New Valuations created: Counts

11.23.1.6. Procurement checklist created / Confirmation done: Counts

11.23.1.7. Refurbishment

11.23.1.7.1. Retail eligibility done: Counts

11.23.1.7.2. RF request created / approved: Counts

11.23.1.8. Stock

11.23.1.8.1. Price assignments done: Counts

11.23.1.8.2. Vehicles – Image/ 360 done: Counts

11.23.1.9. New Buyer enquiries created: Counts

11.23.1.10. Retail

11.23.1.10.1. PDI: Counts

11.23.1.10.2. Name transfers done: Counts

11.23.1.11. Certification - Dealer request made: Counts

11.23.2. There will be filter defined for Zone, Sub-Zone and Dealer Location.

11.23.3. The List will have option to export to excel and pdf

11.24. 13.3 Maintenance Admin

11.24.1. Maintenance Admin role will be given to maintenance team of the project

11.24.2. They will do following things:

11.24.2.1. Website Approval / Images:

11.24.2.1.1. User can access this screen to approve /reject images for website.

11.24.2.1.2. All ‘Push-to-website’ requests will be displayed in a list.

11.24.2.1.3. The list will be displayed in ascending order of the date

11.24.2.1.4. Each item in the list will display following information:

11.24.2.1.5. System Integrations(Stock):

11.24.2.2. Roles & Responsibility Definition:

11.24.2.2.1. Roles & Responsibility Matrix can be added/ updated using this feature. (if SC2 connection and mapping is available then this will be revised at application level)

11.24.3. Maintenance Admin will have all rights to access the application and all web admin (Dealer and TKM Admin) features along with above two things

12. '