HHT Ver 5 0 FS - V1.2

Project Name-HPOS Web Applications
FS for HHT Ver 5

(2014-05-099)
TCS Disclaimer:
INFORMATION CONTAINED HEREIN IS PROPRIETARY AND CONFIDENTIAL AND MAY BE
DISCLOSED AND USED SOLELY FOR THE OPERATION AND MANAGEMENT OF THE TMF-TCS
BUSINESS
HHT Ver 5.0 FS
Document History
Version
Date of Change
Owner of Changes
Description of Change
1.0
23/09/14
Neha Zavar
Final Version
TCS-TMF Confidential
Page 2 of 56
HHT Ver 5.0 FS
Teams required to Review

(List the impacted groups that need to review the document)
Review Team
IT Execution Committee Jigar Parekh, Alok Choudhary, Swapnil Sarkar,Siddharth Seth
Collections Bharat Bhat ,
Operations Mandar Shrotri, Rakesh Kumar, Samir Sawant
Business Owner Alok Chadha , Anil Rathi
Steering Committee Mr. Jitendra Jadhwani , Mr. Sandeep Dongre
SAB - Rajesh Meher , P.S. Padmakumar, Rahul Mhatre
Vendor - Forbes
Audit - Alok Chawla
Page 3 of 56
HHT Ver 5.0 FS
Contents
1.OVERVIEW.....................................................................................................................................................5
1.1 REFERENCE...........................................................................................................................................5
1.2 POINTS EXCLUDED FROM THIS FS.........................................................................................................5
1.3 SHORT DESCRIPTION OF FUNCTIONALITY..............................................................................................5
2.BUSINESS REQUIREMENT & SOLUTION ........................................................................................................10
2.1 CUSTOMER CONTACT NUMBER UPDATION.........................................................................................10
2.2 LEAD CAPTURE FUNCTIONALITY..........................................................................................................12
2.3 CAPTURING THIRD PARTY DETAILS......................................................................................................14
2.4 MINI STATEMENT...............................................................................................................................16
2.5 LINKING OPERATIONAL/SALES ISSUE TO SAGE QRC SYSTEM...............................................................19
2.6 FUNCTIONALITY TO SEND SMS ON EXECUTIVES UPDATED MOBILE NUMBER......................................21
2.7 LOG OFF TIMING REPORT....................................................................................................................22
2.8 NEW FEEDBACK CODE ADDITION........................................................................................................23
2.9 PAPER ROLL MANAGEMENT AND TRACKING STOCK DISTRIBUTION....................................................26
2.10 SURRENDER (LOCKING) OF HHT........................................................................................................29
2.11 OTP FOR ENTERING ADMIN PRIVILEGE ON HHT MACHINE................................................................ 31
2.12 ENHANCEMENTS IN REPORTS...........................................................................................................32
2.13 TRACKING OF REPAIR MACHINE AND ITS SPARE PARTS....................................................................33
2.14 DEFAULT LOCKING SHOULD BE "SELECT" AND NOT "LOST".............................................................. 34
2.15 DRC / BRC MACHINE LOCK FUNCTIONALITY ON DUE DAYS LOGIC.................................................... 34
2.16 AUTO MACHINE LOCKING & REPORT................................................................................................35
2.17 CONFLICTED ID DESCRIPTION ENHANCEMENT..................................................................................34
2.18 ASSET CONFIRMATION MACHINE LOCKING.......................................................................................35
2.19 MACHINE RECOVERY.........................................................................................................................36
2.20 LOST MACHINE..................................................................................................................................36
2.21 GUI FOR ROLE MANAGEMENT...........................................................................................................37
2.22 PROPER ERROR MESSAGES INSTEAD OF SYSTEM GENERATED EXCEPTIONS.......................................41
2.23 SYNC BETWEEN MIDDLEWARE AND TMF UNIVERSE.........................................................................42
2.24 BAM RELATED CHANGES..................................................................................................................47
2.25 DNS CHANGES..................................................................................................................................48
2.26 SECURITY ENHANCEMENT ON HHT MACHINE TO SERVER COMMUNICATION...................................49
2.27 SECURITY ENHANCEMENT ON MIDDLEWARE APPLICATION..............................................................50
2.28 DEPLOYMENT REPORT ISSUES..........................................................................................................51
Page 4 of 56
HHT Ver 5.0 FS
1 Overview
1.1. Reference
This FS is based on the BRD raised by TMF Business User (#2014-05-099) from
Collections & Operations which covers following points:-
A. Collections:1) Customer Contact Number Updation functionality required in DRC and BRC
machines
2) Lead capture functionality required in DRC & BRC machines
3) Capturing Third Party Details from all HHT machines
4) Mini Statement to be generated from all HHT machines
5) Linking operational/sales issue to Sage QRC system
6) Functionality to send SMS on executives updated mobile number
7) Log off timing in middleware report
8) New Feedback Code addition as per business requirement
B. Operations :1) management and tracking stock distribution

2) Locking and Surrender of HHT
3) OTP for entering Admin privilege on HHT machine
4) Enhancements in Reports
5) Tracking of repair machine and its spare parts
6) Default Locking should be "select and not "Lost
7) DRC / BRC machine lock functionality on due days logic
8) Conflicted ID description enhancement
Page 5 of 56
HHT Ver 5.0 FS
9) Locking machines not used for >30 days
10) Machine Locking for Asset Confirmation
C. IT requirements :1) GUI for Role Management

2) Proper Error messages instead of system generated exceptions
3) Sync between Middleware and TMF Universe
4) BAM related changes
5) DNS Changes
6) Security enhancement on HHT machine to server communication
7) Security enhancement on middleware server web services
8) Deployment Report Issues
1.2. Points Excluded from this FS
The following points are excluded from this FS:-
1) Bucket transfer functionalities to be discussed and build This is an independent

requirement at Indus end. FS will be submitted directly by Indus.
2) New GUI for uploading Common customer list This will be taken as a separate
enhancement and will be delivered in month of Oct-14.
3) Approval required for authorization- This will be taken as a separate
enhancement and will be delivered in month of Oct-14.
4) Lost/Found machine page required - A separate FS will be submitted for sign off
before Sep-14 end.
5) Lost/Found machine should not be allowed to do transactions :- A separate FS
will be submitted for sign off before Sep-14 end.
Page 6 of 56
HHT Ver 5.0 FS
1.3. Short Description of the Functionality

This document will include the solution for following functionalities:-
A. Collections :1.
Customer Contact Number Updation functionality required in DRC and BRC

machines
i. Customer Contact Number Updation functionality to be built in DRC and BRC
machines
ii.
Updated customer contact numbers to be sent to INDUS system at EOD.
2. Lead capture functionality

i.
ii.
Lead Capture functionality to be enabled in DRC and BRC Machines

Lead captured information needs to be forwarded to SAGE system
3. Capturing Third Party Details

i.
ii.
Third Party Details will be captured by collection agents (Field Executives / BRC / DRC)
through HHT machines.
The data will flow from Middleware to TMF Universe and then from TMF Universe to
INDUS collection system.
4. Mini Statement
i. Last 6 transactions of all the cases allocated to respective HHT machines will be
ii.
available in offline/online mode on machines.

The executive will be able to print a statement of these last 6 transactions in
offline/online mode.
5. Linking operational/sales issue to Sage QRC system

i.
ii.
iii.
iv.
v.
Customer could have not made the payment due to any service or operational issue
faced.
Any such Service Issue or Service Issue (Sales) feedback captured in HHT machines
should be routed to Sage QRC system for raising an incident in SAGE QRC.
The SAGE QRC helpdesk team will work on the incident and record the response after
resolution.
Response captured in Sage QRC will be sent back to Indus and TMF Universe systems.
TMF Universe will send these updates on executives mobile number.
6. Functionality to send SMS on executives updated mobile number

i.
ii.
iii.
Provision to update executive mobile number will be made available in HHT

Middleware system.
Whenever executive mobile number is updated in middleware , it will flow to Indus
system.
Indus will not allow to update any executive details from its system and if there is a
provision to do so , it will be disabled.
Page 7 of 56
HHT Ver 5.0 FS
7. Log off timing report

i. Timing of the logout done by an executive on HHT machines will be displayed through
reports available in middleware.
8. New Feedback Code addition as per business requirement

i. Provision to add new feedback code as per the business requirement on HHT
machines will be made available.
B. Operations :1. Paper roll management and tracking stock distribution

i.
ii.
This module facilitate to keep track user Paper roll request initiate by BOM/ DEALER
Also for user Admin, This module allows close look on paper roll stock distribution and
distributed stock consumption. User 'REQUESTOR' (BOM/ DEALER) facilitates to see
current stock of paper roll, with an options or parameter for distribution of stock.
2. Locking and Surrender of HHT

i.
ii.
There should be a process to handle surrendering of the machines

Once the machine is surrendered the executive should not be able to do any
transactions.
3. OTP for entering Admin privilege on HHT machine

i.
ii.
One time password is required for accessing admin module of the machine
This will help in enhancing the overall security of the process.
4. Enhancements in Reports
i.
Enhancement is required in Deployment and Asset confirmation report.
5. Tracking of repair machine and its spare parts

i.
ii.
To track the machine right from where it is submitted to repair till it is back in stock
The machine will be tracked after it gets repaired and gets allocated
6. Default Locking should be "select and not "Lost

i.
Middleware application on lock-unlock screen , when locking the executive the
default option for reason should be Select instead of the default of Lost
7. DRC / BRC machine lock functionality on due days logic
i.
ii.
iii.
Due days locking logic would implemented for Branch and Dealer Cashier user to
restrict transaction based on due days logic.
This logic works on number of days defined by middleware user.
Due days locking logic will works only in online mode
8. Conflicted ID description enhancement

i. KYC initiator User BCM will facilitate to see details of executive, which occur as
ID conflicts with past created IDs.
ii.
Here Surrender Reason and status will added (resigned/ suspended/ terminated/
absconding)
Page 8 of 56
HHT Ver 5.0 FS
9. Locking machines not used for >30 days

i. The machines which has not done any transaction for more than 30 days
should get locked automatically
10 Machine Locking for Asset Confirmation
i. There should be a functionality to automatically lock the machines which are
not confirmed by a certain date.
C. IT requirements :1. GUI for Role Management

i. Role addition, modification for both EPOS and middleware application will be
developed
2. Proper Error messages instead of system generated exceptions
i. Currently in middleware application system generated error messages are
getting displayed
ii. Proper error messages to be displayed on middleware application
3. Sync between Middleware and TMF Universe
4. BAM related changes
5. DNS Changes
6. Security enhancement on HHT machine to server communication
7. Security enhancement on middleware server web services
8. Deployment Report Issues
Page 9 of 56
HHT Ver 5.0 FS
2 Business Requirements & Solution
A. Collections :2.1. Customer Contact Number Updation -:
2.1.1. Detailed Description -:

1. Currently customer contact updation functionality is available on the field
executive machines.
2. Business needs same functionality to be enabled on DRC and BRC machines
3. Using which updated customer contact details can be captured for customers
4. Updated customer contact numbers will flow to INDUS system on EOD basis.
2.1.2.
Interface/Integration-:
1. HHT Machine HHT Middleware TMF Universe For New Contact Numbers
captured in HHT machines
2. TMF Universe Indus For New Contact Numbers captured in HHT machines
2.1.3. Proposed Logic -:

a) HHT Machine to TMF Universe -:
1. Mobile number to be entered in a mandatory field of 10 digits while capturing the

phone number on receipt issuance (comment added by forbes on 30/9/14)
1.
2. Additional option on Main screen required for updation of mobile number for DRC and
BRC like in COLLECTION EXECUTIVES machines.
3. After selecting Contract number, give option to select CUSTOMER OR THIRD PARTY and
then allow entering MOBILE NUMBER of 10 DIGITS
4.3. There will be validation on the mobile number. It will accept only numeric values
5.4. Process flow at HHT machine level is as follows,
Page 10 of 56
Formatted: Font: (Default) Calibri
Formatted: List Paragraph, Numbered +

Level: 1 + Numbering Style: 1, 2, 3, + Sta
at: 1 + Alignment: Left + Aligned at: 0.25" +
Indent at: 0.5"
Formatted: Indent: Left: 0.5", No bullets o

numbering
Formatted: Numbered + Level: 1 +

Numbering Style: 1, 2, 3, + Start at: 1 +
Alignment: Left + Aligned at: 0.25" + Inden
at: 0.5"
HHT Ver 5.0 FS
b) TMF Universe to Indus -:

1.
2.
List of updated numbers sent by middleware database will be stored into TMF
universe.
From TMF Universe database captured updated mobile numbers will be sent to
INDUS system through an EOD batch job.
Page 11 of 56
HHT Ver 5.0 FS
2.2. Lead capture functionality for DRC & BRC machines -:

1.
2.
3.
4.
5.
Currently lead capture functionality is enabled on field executive machines

Business needs same functionality to be enabled on DRC and BRC machines
Lead capture information needs to flow to SAGE system.
Further SAGE system will create a lead of the same in their system
Status of the lead created can be tracked in SAGE system
2.2.2. Interface/Integration-:
1. HHT Machine HHT Middlewware TMF Universe SAGE For Leads
Captured

a) Middleware
1. Dropdown will be created for product list.
2. List for dropdown is as follows,
HHT Product
207/Xenon
Ace

Level: 1 + Numbering Style: a, b, c, + Sta
Indent at: 0.8"

at: 1.3"
Formatted Table
Bus
Magic
Truck
Venture
Winger
Nano
MUV
Car
a)

numbering
Formatted: List Paragraph
b) TMF Universe 1.
2.
3.
4.
A new screen will be created on DRC and BRC HHT machines to capture leads.
Dropdown will be created for product list.
Executive/DRC/BRC will select the product from the dropdown list
Lead capture details will be sent to TMF universe database.
Page 12 of 56

Level: 1 + Numbering Style: a, b, c, + Sta
Indent at: 0.8"
Formatted: Font: (Default) Calibri, Bold
HHT Ver 5.0 FS
5.
6.
7.
From TMF Universe database details will be sent to SAGE system through an EOD
batch job
Once the data is available in SAGE system, a lead will be created and its status could
be tracked.
Following details will be captured for lead creation,
Sr
no
Field
1 FinanceType
2 Business Division
3
4
5
6
7
8
9
10
11
12
13
14
15
Product
Channel
TMFL Region
TMFL State
TMFL Area
TMFL Branch
Lead Type
First name
Last name
Mobile Number
State
Lead city
Referred by
Values
hardcode to New
CV/PC (derived from product)
Product codes from 1 to 9 preferably drop
down
hardcoded to value CollectionLead
derived based from collector code
Harcoded to value Individual
Available
Blank space
Available
Executive code
8.
Once the lead is created in Sage system, lead id will be sent in a response to TMF
Universe.
9.
Product codes required in HHT screen are as follow,

Prod product family
HHT Product
207/Xenon
Ace
Bus
TMF_CV
Magic
Truck
Venture
Winger
Nano
TMF_PC
MUV
Car
10. Please refer the below sheet for HHT Sage product mapping.
Page 13 of 56
HHT Ver 5.0 FS
HHT - SAGE product

mapping.xlsx
2.3. Capturing Third Party Details -:

1. Presently, HHT machines used by field executives have capability to capture third
party contact number. HHT machines with dealer and branch cashier version dont
have this facility.
2. Contact details are getting stored on middleware and same are flowing to TMF
Universe.
3. Presently, HHT machine dont have capability to capture Third Party Name, address
and Email Id.
4. Following fields needs to be captured through HHT screen,
Third party Name
Third party Mobile No
Third Party Address
Third Party Email ID
5. Captured third party details needs to be provided to INDUS collection System.
2.3.2. Interface/Integration-:
1. HHT machine HHT MiddlewareTMF Universe Indus System
Page 14 of 56
HHT Ver 5.0 FS
a) HHT machine to TMF Universe-:

1. New screen will be created to capture third party details for all machines.
2. Name and Mobile no. should be mandatory field to capture third party detail.
3. Email id (30 char) and address (70 char) will be optional field to capture third party
detail.
4. Name, Address Email and Mobile no. field will be added in Middleware database.
5. Web service used to communicate between TMF Universe Server and HHT
Middleware will be changed as per above field details.
6. Data compression and security encryption will help in increasing the payload.
6.7. Third party details will be captured under update sub menu. (comment added by
forbes on 30/9/14)
7.8. Process diagram at HHT machine level is as follows, flow diagram to be changes
(comment added by forbes on 30/9/14)
b) TMF Universe to Indus-:

1. These details will be sent from TMF Universe to INDUS Collection system by procedure
(.CSV) on EOD basis
2. Integration diagram is as follows,
Third party
details
Third party
details
HHT Machine
Real time
basis
TMF Universe
Page 15 of 56
EOD basis
INDUS System
HHT Ver 5.0 FS
2.4. Mini Statement -:

2.4.1.
Detailed Description -:
1. Mini statement of last 6 transactions of a contract to be displayed on HHT machines

and the same can be printed by an executive.
2.4.2.
Interface/Integration -:
1. ODS TMF Universe to fetch transaction history data

2. TMF Universe HHT Middleware HHT Machines To display transaction history
of last 6 transactions.
2.4.3.
Proposed Logic -:
a) ODS to TMF Universe -:

1. Collection done through different modules like HHT, SAP or webpos gets
stored in SAP. ODS will maintain repository of contract data on incremental
basis.
2. Universe DB will pull contract data from ODS through an EOD job
3. The fields required are as follows :Field Description
Contract number
Document number
Transaction Date
Amount
Rejection indicator
Inception Date(entry Date)
Page 16 of 56
SAP Field
OBJECTID
BELNR
BUDAT
AMOUNT I
R Status
CPUDT
HHT Ver 5.0 FS
4. The data flow diagram is as follows :Incremental Data
Universe DB
ODS
PULL
M/C
Middleware
DB
5. The sample receipt of last 6 transactions will be as follows :Rcpt Date

Amount
1/1/2014
1000000
1/2/2014
145000
1/3/2014
15000
1/4/2014
6000
1/5/2014
24000
1/6/2014
32000
* This statement is as on 'uploaded
date'
Page 17 of 56
HHT Ver 5.0 FS
b) TMF Universe to HHT flow-:

1. Mini Statement synchronize Button will be provided to fetch the last 6 payment
Transaction history data of all the cases allocated to respective HHT
2. Mini Statement option will be provide to executive to generate last 6 transaction
history report.
3. The synchronize button will be allowed to be used only once in a day. This restriction
will be in place.
4. Whenever synchronize button is pressed, the old mini statement related data on the
HHT machine will be removed and the new mini statement related data will be
downloaded and it will replace the old data.
5. Grid will not be present in the statement receipt.
6. Data compression and encryption will help in reducing the overall size of the
payload.
7. Process flow diagram on HHT machine is as follows,
Page 18 of 56
HHT Ver 5.0 FS
c) TMF Universe to HHT -:

1. A database view will be exposed from TMF Universe database to
middleware

Numbering Style: a, b, c, + Start at: 1 +
at: 0.8"
Formatted: Font: Not Bold

Alignment: Left + Aligned at: 1" + Tab after
1.25" + Indent at: 1.25"
2.5. Linking operational/sales issue to Sage QRC system -:
2.5.1.
1. There are separate Collection Teams across different verticals & they are entrusted
with collection & recovery of overdue for these various buckets for both the Direct
as well as the Dealer Portfolio of TMFL.
2. Feedback Trails captured through the HHT machines help the Collections Teams
across various buckets in understanding the repayment behavior of a customer
throughout the Tenure of the contract.
3. Customer can miss out the payment in case of any service/operational issue
he/she has faced.
4. Such Service Issue or Service Issue (Sales) captured in HHT machine should be
routed to Sage QRC system for faster resolution and reconciliation
5. Once the information flows to Sage QRC system a case will be created in Sage QRC
system and which can be traced till the case gets closed.
6. Customer response captured in Sage QRC should be sent back to Indus and TMF
Universe system
7. Updates on such issues to be sent on executives mobile number
8. Based on the response the executive can take necessary action on the case
2.5.2.
1. HHT Machine HHT Middleware TMF universe ( to flow feedback data)

2. TMF Universe SAGE QRC (to flow operational/sales issue data and status to and
fro)
3. TMF Universe Indus system (to flow feedback data for operational/sales issue)
4. SAGE QRC Indus system (to flow operational/sales issue status related data to and
fro
5. SAGE QRC TMF Universe ( To flow the response of the case back to TMF Universe)
Page 19 of 56
HHT Ver 5.0 FS
2.5.3.
Proposed Logic -:
a) HHT flow-:
1. Mobile number will be additional new field which will be captured and sent to server.
2. Mobile number will be mandatory field if CRE select option Service Issue or Service
Issue Sale otherwise, mobile number will be optional field for rest option.
3. Following fields will be captured through an HHT screen,
Customer Name
Customer Mobile No (mandatory)
Executive Id /Name
Executive Mobile No
Remark
Contract No
b) HHT TMF Universe -:
Formatted: Font: 11 pt, No underline
4. Mobile number will be additional new field which will be captured and sent to server.
5. Mobile number will be mandatory field if CRE select option Service Issue or Service
Issue Sale otherwise, mobile number will be optional field for rest option.
6. Following fields will be captured through an HHT screen,
Customer Name
Customer Mobile No (mandatory)
Executive Id /Name
Executive Mobile No
Remark
Contract No
7.1. All above captured fields will be sent to TMF Universe.
b) TMF Universe SAGE QRC-:
1.
Above captured details will be sent to Sage QRC system on real time basis through a
web service call
2.
A case will be registered in Sage QRC system once all required details are received
3.
The helpdesk will work on the case and resolve the same and record the feedback.
4.
All the feedback captured in Sage QRC system will flow to TMF Universe
5.
Following fields will be sent as a response from Sage QRC system,

Case id
Case status
Last updated date
Note (remarks)
Page 20 of 56

at: 0.5"
HHT Ver 5.0 FS
6.
Case updates will be sent to executives mobile number to let executive know the
case status. Contract number and case status will be sent to executives.
7.
SMS contents will be provided by business.
C) TMF Universe - INDUS -:

1.
Above feedback data will be sent to Indus system through SAP PI
d) SAGE - INDUS -:
1. Case updates will be sent from Sage QRC to Indus system on real time basis through a
web service. Field level mapping will be done between Sage and Indus.
2.6. Functionality to send SMS on executives updated mobile number -:
2.6.1.
1. There should be a provision in the system to send alerts etc from the Indus system to
the Mobile No updated in the Indus system.
2. There should be a UI on the TMF Universe system wherein a BM/BCM or any
collection team manager can update the Mobile No of an executive
2.6.2.
1. HHT HHT Middleware TMF Universe to send updated mobile number details
2. TMF Universe Indus to send updated mobile number details
2.6.3.
Proposed logic-:
Page 21 of 56
HHT Ver 5.0 FS
a) HHT TMF Universe -:

1. There will be a provision in middleware application to update executive mobile
number
2. Updated executive mobile number will be sent to Universe database on real
time basis.
b) TMF Universe - Indus -:
2.
3.1. As updated mobile number needs to be sent to the Indus system for the purpose
of updation, so that an individual can send SMSs / Alerts to an executive as
required
4.2. This update from TMF Universe to Indus will be done through a web service call,
which will update executive mobile number.
5.3. There is a provision in Indus system to updated executive details. Business team
needs to communicate it to indus system users not to make use of this page to
update executive details as it may lead to data inconsistency in future. This
functionality will be disabled.
6.4. The data flow from Middleware to Universe for updated mobile number needs to
be incorporated by Forbes
2.7. Log off timing report -:
2.7.1.
1. Log off timing of the executive on HHT machine needs to be captured.
2. Log off timing of the executive on HHT machines to be displayed through a
middleware report.
2.7.2.
1.
2.
3.
4.
Proposed logic-:
Offline Logout will be provided on HHT machine
Logout can be done offline on HHT by its user.
Logout timing will be save locally on database.
Logout timing will flow to server whenever HHT is in online.
Page 22 of 56

at: 0.44"
Formatted: Font: (Default) Calibri, Bold,

Underline
Formatted: Font: (Default) Calibri, Bold,
Underline

at: 0.44"
Formatted: Indent: Left: 0.78", No bullets

numbering

at: 0.44"
HHT Ver 5.0 FS
5. Logout Report will be provided in Report Menu in middleware.

6. This new report will be available under admin role.
A sample report of the logout timings will be as follows :Exec

Name
M/C ID
12345
178985
345621
# of days
Logout
not logged Logout
Exec ID Date
out
Time
A 123456 12/5/2014
21
13:51:51
B 454678 15/7/2014
356
7:05:34
C
45
29865 21/09/2014
34:23:45
2.8. New Feedback Code addition as per business requirement-:
2.8.1.
1. Currently all feedback codes are stored in HHT machine software

2. If any new feedback code has to be added then a new HHT machine software
version has to be released.
3. To avoid this, there should be a provision to add feedback code as per the
business requirement on HHT machines
2.8.2.
1. HHT (m/w) TMF Universe Indus --to flow newly added feedback code data
2. HHT (m/w) HHT Machines.
Page 23 of 56
HHT Ver 5.0 FS
2.8.3.
Proposed logic-:
a) TMF Universe -:
1. Once the new feedback code is added in master data the same information will be
sent to Indus system.
2. The master for feedback codes will be updated in Indus system as well.
b) HHT /Middleware -:
1. Currently, in M/W, frontend screen is not developed for new Feedback code
addition. Below details will be captured on addition page:
2.
3.
4.
5.
6.
7.
Feedback Code
Feedback Description
On addition of above details, data is inserted in M/W DB.
Feedback master data will be flown to Universe database, which will keep
Feedback codes master details in sync on both sides.
Feedback Code sub menu will be provided to display list of all action code.
All codes must be revised and reset on the machine in the below order or priority
and as per the below codes and description.
At HHT Login all Code will be sync to local database. Auto update of action code
will be done on HHT.
Feedback codes with defined priority are as below,
Description
CODE
Priority
Promise to Pay
PTP
Collected (Full)
CF
Collected (Partial)
CP
Deposited by Customer
DC
No Commitment
NC
Out of Home or Office
OHO
Service Issue (Sales)
SIS
Not Traceable
NT
Page 24 of 56
HHT Ver 5.0 FS
8.
Service Issue
(Operations)
SIO
Theft or Accidental
TA
10
Repossessed or
Surrendered
RS
11
Vehicle Abandoned
VA
12
Legal / Police Issue
LPI
13
Customer Deceased
CD
14
Process flow diagram at HHT level is as below,
Page 25 of 56
HHT Ver 5.0 FS
B. OPERATIONS -:
2.9. PAPER ROLL MANAGEMENT AND TRACKING STOCK DISTRIBUTION
2.9.1.
Detailed Description:-
1. This module facilitates to keep track user Paper roll request initiate by BOM/
DEALER
2. Also for user Admin, This module allows close look on paper roll stock
distribution and distributed stock consumption. User 'REQUESTOR' (BOM/
DEALER) facilitates to see current stock of paper roll, with an options or
parameter for distribution of stock.
Page 26 of 56
HHT Ver 5.0 FS
2.9.2.
Proposed Logic:-
Paper rolls Tracking Process flow:

1. BOM/Dealer request for paper roll.
2. Admin will approve/reject request from GUI and send Paper roll through
courier.
2.3. New role for service provider will be created to access TMF universe for
entering POD details while dispatching the courier. There will be one vendor
located centrally at HO. (comment added on 30-sep-14)
3.
4. BOM/Dealer will receive and confirm delivery on Website
5. New role for service provider will be created to access TMF universe for
entering POD details while dispatching the courier.
6. Input parameters for request will be number of paper rolls required
7. Opening and closing balance will be displayed
8.7. Auto mailer to be sent to vendor for all requests raised on HO approval (
request id, branch name, no of rolls requested, request date)
9.8. Date and time willto be captured for all the updates of paper roll request
transactions(comment added on 30-sep-14)
9. Stock out to be maintained and report for the same will be present. User will
be allowed to enter stock consumed on a particular day and agency list will be
provided including self in a list of dropdown for self consumable number of
rolls. (comment added on 30-sep-14)
10. Validations to be present for stock in and stock out details. (comment added
on 30-sep-14)
10.
11. Two reports for paper roll will be provided. The fields in both the reports will
be as below,
a. Paper Roll Status Tracker
Search parameter to extract report will be date, branch/dealer
The format is as below :Sr. No.
Request ID
Branch Name/Dealer Name
Region
State
current stock with dealer / branch
requestor's name
requestor's login id
Status
Request date
Page 27 of 56
HHT Ver 5.0 FS
No of rolls requested
b. Paper Roll Distribution Tracker
Sr. No.
dealer / branch name
Region
State
current stock with
dealer/branch
Remarks
Agency/self (30/9/14)
Formatted Table
Restriction of user BOM/ DEALER for Initiate request are:
1. 1] Dealer / branch should confirm and acknowledge the delivery

2. 2] Till the time of confirmation of earlier request raised, BOM/Dealer would
not be able to generate new request for paper roll.
3. There should be a provision to cancel the request in case if the dispatch is
lost in transit so that a new request can be raised. Ho admin will have this
privilege. (comment added on 30/9/14)
4. 3] there will be a restriction to raise a new request on no of paper rolls to
be requested should not be greater than 500. (comment added on
30/9/14)
5. if available stock at particular branch/dealer is greater than 500 then new
request can not be raised. These limit values can be extended with the help
of IT team. (comment added on 30/9/14) No in stock restriction will be
available for requesting new request for paper roll.
Flow diagram to be updated as POD details will be updated by Vendor and not byy
BOM/Dealer (comment added on 30/9/14)
IMPACTS: MIDDLEWARE
DEPENDENCIES: NONE
Page 28 of 56
Formatted: Font: (Default) +Body (Calibri)

Indent at: 1"

HHT Ver 5.0 FS
PROCESS:
Page 29 of 56
HHT Ver 5.0 FS
2.10.
SURRENDER (LOCKING) OF HHT
2.10.1.
Proposed Logic:-
Surrender process flow change:

1. As per the current functionality surrender will be initiated by middleware user
(BOM/Dealer). Here middleware HHT machine status will change to Surrender in
progress.
2. After middleware surrender process initiated, Respective HHT get prompted to do
surrender machine (mandatorily). If machine user tries to login into HHT machine
isin online mode, then user will not be able to login or performdo any transaction
(comment added on 30/9/14)
3. Surrender option will be available in main menu of HHT machineat the time of
login.(no need for thumb impression authentication and id password) (comment
added on 30/9/14)
4. At HHT, Surrender process will push all offline data in machine to middleware and
will erase all data from machine (including contract allocation data ).
5. Once aboveHHT surrender process is completed, middleware user has to confirm
that respective HHTs transaction till date gets authorized by checking on TMF
Universe application for any pending transactions. Post this confirmation
respective machine status will change to Surrendered. Auto surrender to be
provided. It should check no pending transactions for authorization. (comment
added on 30/9/14)
5.6.
Point to clarify on receiving an alert for surrender if CRE removes the
battery/switch off and again logs in offline mode then transactions will be allowed
or not? Transactions can not be done in offline mode probably machine should be
logged in online mode after surrender is initiated. (comment added on 30/9/14)
6.7.
Separate report would be available for surrendered machines. The fields
will be as follows :Sr. No.
Branch Name
State
Region
Surrendered By
Executive Name
Executive ID
Page 30 of 56
Formatted: Font: 12 pt, Highlight

Formatted: Font: 12 pt, Font color: Text 2,
Highlight
Formatted: Highlight
Formatted: Font: 12 pt, Not Highlight

Formatted: Font: 12 pt, Not Highlight
HHT Ver 5.0 FS
Surrendered Date
Machine Number
7.8.
Successfully Surrendered machine would not go to part of 'Asset
confirmation' & 'Deployment report' as in stock.
IMPACTS: HHT, MIDDLEWARE
DEPENDENCIES: NONE
PROCESS:
Page 31 of 56
HHT Ver 5.0 FS
2.11.
OTP for entering Admin privilege on HHT machine
2.11.1.
Proposed Logic -:
1. OTP password will be generated through a GUI(middleware) after providing input

as machine number or executive id
2. HHT Admin Login password will be One Time password
3. OTP for HHT machines will be synced via middleware and it will be only numeric.
4. At a time ten random OTP will be available per HHT machine at middleware. HHT
user has to punch OTP according to index of OTP. Once executive logs in into
machine all OTPs will be synced with that HHT
5. No one will be able to view all 10 OTPs.
6. In case of offline mode, 10 random generated OTPs can be used. For the next
password executive needs to be logged in online mode.
7. Once an OTP is used it will get expired.
8. Index of OTP will maintain equal on both HHT side as well as Middleware.
9. Middleware will have ten OTP available which will change randomly as per usage.
10. This password will be used to gain admin privilege on the machine by an executive.
11. Factory User login will be provided in HHT
12. This will be used by NOC team for their operations. It will not be shared with TMF
All existing menu in admin login, will be segregate between admin and factory user.
13. Only BOM to have access of this page.
14. Menus available under admin and factory user are as follows,
a. Executive/Cashier Enrollment (admin)
b. Set Date and Time (TBD)
c. Comm Setting ( FTP and HTTP URL ) (factory user)
d. Printer Test (factory user/admin)
e. Bash Prompt (factory user)
f. Select Service Provider (admin)

Indent at: 0.5"

Formatted: List Paragraph
IMPACTS: HHT
DEPENDENCIES: NONE
Page 32 of 56
HHT Ver 5.0 FS
PROCESS: NOT REQUIRED
2.12.
ENHANCEMENTS IN REPORTS
SOLUTION:
Deployment report & HHT Confirmation Summary Report:
Customize in current report will be done as per TMFL requirement.
1. Deployment report :
a. Proper Headings of columns in report
2. Asset Confirmation report ( Attachment 2 )
Report needs to be extracted for all branches
AssetConfirmation03
0914.xls
Report format should be shared post comparison of current and required format
(comment added on 30/9/14)post comparison is as follows,
Page 33 of 56
HHT Ver 5.0 FS

Field Code Changed
rpt_AssetConfirmatio
n(1).xls
2.13.
TRACKING OF REPAIR MACHINE AND ITS SPARE PARTS
SOLUTION:
This module facilitate user to track machine which are in Repair and also allow
tracking asset of machines after Repair stage
1) The machine will be reallocated from executive to NOCC present in surrendered
status for repairing. This surrender functionality will be different from normal
surrender of HHT machines.(comment added by forbes on 30/9/14)
2) Naming to be changed. Instead of surrender it should be under repair menu.(to be
removed)
3) New menu will be provided for repair in m/w application under machine
repair(comment added by forbes on 30/9/14)
1)
4) Machines in stock will not be allowed to repair with the extra efforts and
architectural changes at application.
Page 34 of 56
Formatted: Font: 12 pt, Highlight

numbering

numbering, Widow/Orphan control, Adjust
space between Latin and Asian text, Adjust
space between Asian text and numbers
HHT Ver 5.0 FS
2)5)
During the process of enrollment at the time of thumb impression if it is
found that machine is damaged then will it be possible to surrender the
machine.this category will fall in post allocating the HHT to executive which has
already been taken care as mentioned above.
6) Two separate options byhand and by courier will be provided. (comment added by
forbes on 30/9/14)
7) If byhand then system wont ask for courier details. (comment added by forbes on
30/9/14)
8) If by courier then POD details will be mandatory when machine is marked to
repair. (comment added by forbes on 30/9/14)
9) FTL will acknowledge receiption of machine for repair. (comment added by forbes
on 30/9/14)
3)10)
Here ,from the time HHT machine declared as under repair, then it goes to
FTL (NOOC) stock
4)11)
For reason dropdown will be addeda. Antenna
b. Battery
c. Printer
d. Adapter
e. Motherboard
f. Display
g. Others (remarks)
g.12)
Remarks option will be displayed and it will be mandatory for others
option
13) Simultaneously multiple options can be selected and will be displayed in single
field as remarks. (comment added by forbes on 30/9/14)
14) After repair, FTL will Fill POD details and send machine back to respective branch
by courier. (comment added by forbes on 30/9/14)
15) Branch will acknowledge the receiption of machine. (comment added by forbes on
30/9/14)
16) After repair done respective HHT gets back in branch stock. (comment added by
forbes on 30/9/14)
17) No of machines with FTL for repair and with TMFL should be displayed in
deployment report(not reuired). As when machine is surrendered for repair in
deployment report it shows as repair. Once the machine is with FTL, status should
be displayed as repair with FTL.(not required in new design. To be discussed with
business) (comment added by forbes on 30/9/14)
Formatted: Font: Bold

Formatted
Formatted: Font: Bold
5)18)
Vendor to provide the access of repair page to enter POD details and repair
details.
6)19)
These all status will be available through a report. The report format will
be as follows :-
Page 35 of 56

numbering
HHT Ver 5.0 FS
Machine repair
tracking report.xlsx
Input parameters to be decided. from business

Report needs to be finalized. from business
NOTE: Spare parts of machines will not be considered for tracking.
IMPACTS: MIDDLEWARE
DEPENDENCIES: NONE
2.14.
Default Locking should be "select and not "Lost
SOLUTION:
1. Middleware application on lock-unlock screen , when locking the executive the
default option for reason should be Select instead of the default of Lost
IMPACTS: MIDDLEWARE
DEPENDENCIES: NONE
2.15.
DRC / BRC MACHINE LOCK FUNCTIONALITY ON DUE DAYS
LOGIC
SOLUTION:
1. Due days locking logic would implemented for Branch and Dealer Cashier user
to restrict transaction based on due days logic.
2. This logic works on number of days defined by middleware user.
3. Due days locking logic will works only in online mode
Page 36 of 56
HHT Ver 5.0 FS
DEPENDENCIES: NONE
2.16.
CONFLICTED ID DESCRIPTION ENHANCEMENT
SOLUTION:
1. KYC initiator User BCM will facilitate to see details of executive, which occur as
ID conflicts with past created IDs.
2. Here Surrender Reason and remarks will added (resigned/ suspended/
terminated/ absconding)
IMPACTS: MIDDLEWARE
DEPENDENCIES: NONE
2.17.
AUTO MACHINE LOCKING & REPORT
SOLUTION:
1. A daily base scheduler will run to check 30 days no receipt logic if any HHT meets
this condition it will be locked.
2. The unblocking requests of these machines will be done by Ops Team through
their middleware apps.
3. This functionality will be applicable for BRC as well as DRC machines.
4. Lock executives should appear in existing Lock User report with a remark Auto
locked by system as HHT machine not in use for more than 30 days
DEPENDENCIES: NONE
2.18.
ASSET CONFIRMATION MACHINE LOCKING
SOLUTION:
Page 37 of 56
HHT Ver 5.0 FS
1. Asset confirmation will work as user specified: Till date asset confirmation work on
10th of each month, New GUI will facilitate user flexibility to set any twelve dates
of the year (one per month). This date field would not mandatory so user get full
flexibility to set any date to run respective scheduler.
2. Locking mechanism as earlier if HHT not confirmed respective HHT get LOCKED
(Only if HHT in online mode)
IMPACTS: MIDDLEWARE, HHT
DEPENDENCIES: NONE
2.19.
MACHINE RECOVERY
BUSINESS DESCRIPTION:
This module facilitate to get stock-in HHT which is earlier stated as LOST
Need to discuss with business team (comment added by forbes on 30/9/14)
Formatted: Normal, Indent: Left: 0.25", N

bullets or numbering
Formatted: Normal, No bullets or numberin
IMPACTS: MIDDLEWARE
DEPENDENCIES: NONE
PROCESS:
2.20.
LOST MACHINE
BUSINESS DESCRIPTION:
No transaction to be allowed from the machine marked as LOST
[NOTE: Post HHT declared as LOST from middleware, Transaction which made at
offline mode will consider under risk]
Write off machines to be removed from stock.
Page 38 of 56
HHT Ver 5.0 FS
Need to discuss with business team (comment added by forbes on 30/9/14)

DEPENDENCIES: NONE
C. IT REQUIREMENTS -:
2.21.
GUI FOR ROLE MANAGEMENT
2.21.1.
1. Presently, whenever we add a new role as well as modify existing rights of a

particular role, we do it through database as a back-end process.
2. As an Internal It Requirement, we require a GUI for addition of new roles to the
system and modification of existing rights of roles.
3. In case, if a particular role needs to be terminated, application should also allow
deactivating the existing role.
2.21.2.
Proposed Logic -:
a) TMF Universe -:
A new GUI will be developed to

1. add a new role
2. update existing rights of a role
Page 39 of 56
HHT Ver 5.0 FS
3. deactivate existing role

Audit trail for the same will be maintained.
Fields on UI will be available as mentioned below
1.
Search Role :Business User can search a role by selecting a role name from provided list.
Sr. No.
Field
Na
me
Role
Field Type
Mandatory
(Y: Yes/
N:No)
Drop
Down
List
Description
List will contain existing role

names.
UI will show role name and existing rights of that role.

2.
Update rights of Role :Business User can update the existing rights of role by selecting a role from provided list.
Sr. No.
Field
Na
me
Field Type
Mandatory
(Y: Yes/ N:No)
Description
Role
Drop
Down
List
List will contain existing

role names. User will
select role name.
Search
Button
On clicking, role name

and existing rights of
selected role will be
displayed.
Progra
m
Multiple
selection
box
Name of the menu whose

right needs to be
given to that role
Updat
e
Button
On
S. No.
1
Status Message
Rights Updated successfully
Sorry. Unable to update. Please try

again.
Page 40 of 56
Remarks
If success
If failure
clicking, selected
rights will be updated
against that role.
HHT Ver 5.0 FS
3.
Add New Role :Business User can add a new role by entering role name and selecting the rights to be given
to that role.
Sr. No.
Field Type
Mandatory
(Y: Yes/
N:No)
Description
Role
Na
me
Text Field
Role to be added.
Progra
m
Multiple
selection
box
Name of the menu whose

right needs to be given to
new role
Add
Button
To save changes.
Sr. No.
1
2
4.
Field
Na
me
Status Message
Role Added Successfully.
Remarks
If success
Sorry. Unable to add. Please try again.
If failure
Deactivate existing Role :Business User can deactivate / terminate a new role by selecting a role from provided list.
Sr. No.
Field
Nam
e
Field Type
Mandatory
(Y: Yes/
N:No)
Description
Role
Drop
Down
List
List will contain existing role

names. User will select
role
name
to
be
deactivated.
Deactivat
e
Button
On clicking, popup will be

displayed
for
confirmation.
Pop up will ask Do you really want to terminate this role ?

a. Click OK to confirm. Role will be deactivated.
b. Click CANCEL to select another role.
Page 41 of 56
HHT Ver 5.0 FS
Sr. No.
1
Status Message
Role Terminated Successfully.
Sorry. Unable to terminate. Please try

again.
Remarks
If success
If failure
b) Middleware -:
1. This module allows admin to register new users on the middle-ware. A registered user
can have only one active login session at a time:
2. At the time of role creation Admin can define master menu for any role.
3. Define role can be assign at the time of user creation.
Page 42 of 56
HHT Ver 5.0 FS
Page 43 of 56
HHT Ver 5.0 FS
2.22.
Proper Error messages instead of system generated exceptions
2.22.1.
1. Currently in middleware application system generated error messages are

getting displayed
2. Proper error messages to be displayed on middleware application
2.22.2.
Proposed Logic -:
1. Middle application will handle all type of exception in website. If any exception
occurs application will redirect to error page.
Page 44 of 56
HHT Ver 5.0 FS
2.23.
Sync between Middleware and TMF Universe
2.23.1 Detailed Description -:

As per the requirement, automation is required to sync master details between TMF Universe
and Middleware. Once data is added in TMF Universe, it should automatically flow to
Middleware in following Master Details:
Agency
Branch
Branch Cashier
Dealer
Collection executive details
Addition and modification is functionality is required.
2.23.2
Proposed Logic -:
a) TMF Universe -:
Formatted: Font: Arial, Underline
As per the requirement, for available master addition pages, some modification is
required in fields and application to send data to middleware. New pages required
to be developed which are not yet developed. For various master additions,
functionality and approach will be as of below:
1) Branch:
Addition:
Currently, in TMF Universe, frontend screen is developed for new branch addition with below
fields:
Region
Location
City
State
Branch Address1
Branch Address2
Branch Address3
Pin code
Unique Branch Code
Contact Number
On addition of above details, data is inserted in Universe DB; in addition to that, data will be
flowed to middleware side also, which will keep branch master details in sync on both sides.
Here, for purpose of addition, flag will be sent to middleware, indicating new addition of
branch details.
Modification:
Page 45 of 56
HHT Ver 5.0 FS
Modification screen needs to be developed for branch details, where from above specified
fields; only few fields will be available for update.
On modification screen, below fields can be modified:
Region
Location
City
State
Branch Address1
Branch Address2
Branch Address3
Pin code
Contact Number
Status
Search Field for modification:

Branch Id
On search with above field, if records found in Universe DB, details of same will be displayed
with editable fields which will be available for modification, as specified above.
After the input fields are updated, records will be updated in Universe DB and same will be
sent to middleware side with flag indicating modification of records. Successful status
message will be displayed after successful processing of records.
2) Branch Cashier:
Addition:
Currently, in TMF Universe, frontend screen is developed for new branch cashier addition with
below fields:
Vendor Code
SAP ID Number
Employee Name
flowed to middleware side also, which will keep branch cashier master details in sync on both
sides. Here, for purpose of addition, flag will be sent to middleware, indicating new addition of
branch details.
Modification:
Modification screen needs to be developed for branch cashier details, where from above
specified fields; only few fields will be available for update.
Employee Name
Status
Page 46 of 56
HHT Ver 5.0 FS
SAP Id
3) Agency:
Addition:
Currently, in TMF Universe, frontend screen is developed for new Agency addition with below
fields:
Vendor Code
SAP Code
Name
As below additional fields are available in middleware, hence these will be captured on input
screen of currently available to user.
Address1
Address2
Address 3
Location
Pin code
flowed to middleware side also, which will keep agency master details in sync on both sides.
Here, for purpose of addition, flag will be sent to middleware, indicating new addition of
branch details.
Modification:
Modification screen needs to be developed for agency details, where from above specified
fields; only few fields will be available for update.
Name
Address1
Address2
Address3
Pin code
Location
Status
SAP Code
Page 47 of 56
HHT Ver 5.0 FS
4) Dealer:
Addition:
Currently, in TMF Universe, frontend screen is developed for new Dealer addition with below
fields:
Dealer Name
Dealer Sac Code
TMF Universe Id
Address
State
Region
Pin Code
On middleware side, below additional fields are captured:
Branch
Area
Which we need to add in developed pages. On addition of above details, data is inserted in
Universe DB; in addition to that, data will be flowed to middleware side also, which will keep
dealer master details in sync on both sides. Here, for purpose of addition, flag will be sent to
middleware, indicating new addition of branch details.
Modification:
Modification screen is developed for dealer details, where from above specified fields; only
few fields will be available for update.
Dealer Name
Address
State
Region
Pin Code
Status
Universe Id
Page 48 of 56
HHT Ver 5.0 FS
5) Collection Executive Locking Status:
Addition:
Currently, frontend screen is developed in middleware, where status/details of collection
executives are maintained. Same details are captured on TMF universe side once executive is
created. Also, now active/inactive status of executive is maintained on both sides. Now as per
requirement, new additional flag of locking status will be maintained on Universe side which
will be triggered from middleware.
Assumption: Locking/unlocking both status flags will be saved along with date for the same.
b) Middleware -:
Formatted: Font: 11 pt, Underline
All data will flow from TMF Universe to MW. This will be handled through web service.
There will be different methods in a single web service.
List of master to be sync if any addition-modification has been done:
1. Agency
2. Branch
3. Branch Cashier
4. Dealer
5. Middleware user
Page 49 of 56
Formatted: Font: (Default) Calibri, 11 pt
HHT Ver 5.0 FS
2.24.
BAM related changes
2.24.1
1. Currently sequence of actions is as shown in below screen shot when

requesting executive enrollment.
2. On Collection Executive Enrollment Form, after providing ID proof for

executive, System is asking for below details,
i.
Collection Team -:
Options are ( X / RSC / 1-4 / 5-10 / 11-23 / 0-N ).
ii.
Collection Executive Designation
Page 50 of 56
HHT Ver 5.0 FS
Options are ( CRE / TEAM LEADER / LRE / RSC Executive / FOS(FIELD EXECUTIVE OF
SUB AGENCY) / FOS(FIELD EXECUTIVE OF AGENCY) / AMR / CRE (CENTRALISED
VENDOR) / BAM / FOS (DECETRALISED VENDOR) )
iii.
Collection Executive Working For ( Company Name )

Options are ( Intellect / E-nxt / Agency Agency No. / Addeco / TMF-Staff )
3. Currently, Using this sequence executives have been created wrongly under
BAM designation.
2.24.2
Proposed Logic -:
1. Following sequence needs to be followed to avoid such issues in future,

i.
Collection Executive Working For ( Company Name )

a. Options are ( Intellect / E-nxt / Agency Agency No. / Addeco / TMF-Staff )
b. Here System will check for Company Name and based on it options for
Collection team will be provided.
ii.
Collection Team
a. Options are ( X / RSC / 1-4 / 5-10 / 11-23 / 0-N ).
b. Based on Collection Team, options for designation will be provided.
iii.
Collection Executive Designation

a. Options are ( CRE / TEAM LEADER / LRE / RSC Executive / FOS(FIELD
EXECUTIVE OF SUB AGENCY) / FOS(FIELD EXECUTIVE OF AGENCY) / AMR / CRE
(CENTRALISED VENDOR) / BAM / FOS (DECETRALISED VENDOR) )
2. Here if User selects Company Name as TMF-Staff then collection team should be 0-N and
designation should be BAM. ( existing mapping of collection team and company name
will remain same )
3. After Submitting the form, request will be sent to Branch Operation Manager for
Verification and Machine Allocation.
4. Collection team mapping details are as follows,
CollectionTeamMappi
ng.xlsx
2.25. DNS changes

1. As per existing functionality, Server IP is hardcoded in HHT machine Image.
2. Through this change, Instead of IP, Machine Image will have domain name of server.
Page 51 of 56
HHT Ver 5.0 FS
3. This will help to establish disaster recovery where in case of complete outage of live
server, data will flow to backup server ( DR Server ).
2.26. Security enhancement on HHT machine to server communication

2.26.1.
Protocol
2.26.2.
REST based web services using HTTP protocol

Machine fetches data using a HTTP GET request. The Middle-ware
responds with the required data serialized.
The following APIs use a GET request:
i. PID Block API for login
ii. Fetch data API
Machine sends data using a HTTP POST request.
i. Transaction API
Securing API
2.26.3.
Every request by the HHT is accompanied by an AUTH CODE. The AUTH

CODE is used to identify & validate a machine on the middle-ware.
Auth code generation
2.26.4.
Every machine has a unique 8 digit Sr. no. (ex. 11028766)

The serial number is encrypted using an RSA 2048 bit Public key on the
machine. New public keys are shared by the middle-ware during the login
process.
Identifying HHT
The AUTH CODE is attached to a GET request as a parameter.

The middle-ware fetches the parameter, decrypts it using a private key &
identifies the machine to validate the request.
Page 52 of 56
HHT Ver 5.0 FS
2.26.5.
Validating data which comes from the middle-ware
2.26.6.
Once the HHT request is validated, the server generates a ZIP folder with
an XML packet & a checksum file for the HHT.
The checksum could be a SHA-256 encoded hash of the machine serial
number, or size of the XML packet.
This checksum is used by the HHT to validate the XML packet.
Proposed solution diagram
2.27. Security enhancement on middleware application

2.27.1 Proposed Logic
1
2
3
4
5
User Information in Memory Dump

Improper Exception Handling
Improper Error Handling
Passwords are sent encrypted mode on Network
Security logs
Login/Logout success/failure
Page 53 of 56
HHT Ver 5.0 FS
Critical user activities viz: creation, deletion, modification on sensitive

business data
creation of a user profile;
deletion of a user profile;
renaming of a user profile;
modification of user profile access rights;
change to user profile , password characteristics
2.28. Deployment Report Issues

Following issues will be taken care of in Deployment report issue resolution,
1. Last transaction date is displaying as N/A.
2. Machine version number is displaying as NULL.
3. Last transaction date (LastTrnDate) to be renamed as CRE last transaction date
4. Count mismatch of in stock machines in deployment report and consolidated
deployment report
5. Few of the SIM card numbers are missing from deployment report.
Page 54 of 56
HHT Ver 5.0 FS
Document Release Notice

Subject:
<Functional Specification Document>
Version
Author
Description
1.0
TCS
Base version
Approved by:
Signature:
________________________
Name:
________________________
Dept :
Collections
Organization:
Tata Motors Finance Limited.
Approved by:
Signature:
Name:
Approved by:
_______________________
________________________
Signature:
________________________
Name:
________________________
Dept : Operations
Dept :- TMF IT
Organization:
Organization:
Approved by:
Approved by:
Page 55 of 56
HHT Ver 5.0 FS
Signature:
________________________
Signature:
________________________
Name:
________________________
Name:
________________________
Organization:
TATA Consultancy Services Ltd.
Dept :- Audit
Organization:
Page 56 of 56

HHT Ver 5 0 FS - V1.2

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HHT Ver 5 0 FS - V1.2

Uploaded by

Copyright:

Available Formats

Project Name-HPOS Web Applications

FS for HHT Ver 5

HHT Ver 5.0 FS

HHT Ver 5.0 FS

Teams required to Review

HHT Ver 5.0 FS

HHT Ver 5.0 FS

B. Operations :1) management and tracking stock distribution

HHT Ver 5.0 FS

9) Locking machines not used for >30 days

10) Machine Locking for Asset Confirmation

C. IT requirements :1) GUI for Role Management

1) Bucket transfer functionalities to be discussed and build This is an independent

HHT Ver 5.0 FS

1.3. Short Description of the Functionality

Customer Contact Number Updation functionality required in DRC and BRC

Updated customer contact numbers to be sent to INDUS system at EOD.

2. Lead capture functionality

Lead Capture functionality to be enabled in DRC and BRC Machines

3. Capturing Third Party Details

available in offline/online mode on machines.

5. Linking operational/sales issue to Sage QRC system

6. Functionality to send SMS on executives updated mobile number

Provision to update executive mobile number will be made available in HHT

HHT Ver 5.0 FS

7. Log off timing report

8. New Feedback Code addition as per business requirement

B. Operations :1. Paper roll management and tracking stock distribution

2. Locking and Surrender of HHT

There should be a process to handle surrendering of the machines

3. OTP for entering Admin privilege on HHT machine

Enhancement is required in Deployment and Asset confirmation report.

5. Tracking of repair machine and its spare parts

6. Default Locking should be "select and not "Lost

8. Conflicted ID description enhancement

HHT Ver 5.0 FS

9. Locking machines not used for >30 days

C. IT requirements :1. GUI for Role Management

HHT Ver 5.0 FS

2 Business Requirements & Solution

A. Collections :2.1. Customer Contact Number Updation -:

2.1.1. Detailed Description -:

2.1.3. Proposed Logic -:

1. Mobile number to be entered in a mandatory field of 10 digits while capturing the

Formatted: Font: (Default) Calibri

Formatted: List Paragraph, Numbered +

Formatted: Indent: Left: 0.5", No bullets o

Formatted: Numbered + Level: 1 +

HHT Ver 5.0 FS

b) TMF Universe to Indus -:

HHT Ver 5.0 FS

2.2. Lead capture functionality for DRC & BRC machines -:

2.2.1. Detailed Description -:

Currently lead capture functionality is enabled on field executive machines

2.2.3. Proposed Logic -:

Formatted: List Paragraph, Numbered +

Formatted: Numbered + Level: 1 +

Formatted: Indent: Left: 1.3", No bullets o

Formatted: List Paragraph, Numbered +

HHT Ver 5.0 FS

Product codes required in HHT screen are as follow,

HHT Ver 5.0 FS