development manual 01

User Types

User Access Flow Architecture

ID Nomenclature Logic

User Type Creation

Personal Resource Planner's Branch

Creation

DEVELOPER’s GUIDELINE MANUAL

TERMINOLOGY

CLUB MEMBERS – CLIENTS, MEMBERS

PERSONAL RESOURCE PLANNER ( PR-PLNR) – BUSINESS PARTNER, FRANCHISE OWNER

HO – HEAD OFFICE

RO- REGIONAL OFFICE

BRANCH – PERSONAL RESOURCE PLANNER’S OFFICE

DD- DROPDOWN

User Types



User Type Creation


Creation


User Types

TYPE OF USERS

MASTER- HO*- RO**

EMPLOYEE- CK- PLANNER’S

PERSONAL RESOURCE PLANNER

* HO > Head Office **RO > Regional Office

User Types



User Type Creation


Creation



MASTER -HO All PR Plnrs and All Members

MASTER -RO

EAST

WEST

NORTH

SOUTH

All PR Plnrs in his/her ZoneAll Members in his/her zone


EMPLOYEE -HO All PR Plnrs and All Members as per the privilege access given by Admin / Master HO

EMPLOYEE -RO

EAST

WEST

NORTH

SOUTH

All PR Plnrs in his/her ZoneAll Members in his/her zone

as per the privilege access given by Admin /Master RO



All Members MAPPED TO HIM/HER

EMPLOYEEOF PR-PLNR

MEMBERS MAPPED WITH HIS PR-PLNRAccess privilege will be given by the PR-PLNR

User Types



User Type Creation


Creation



Personal Resource Planner Each and every Club Kautilya Personal Resource Planner would be allocated a System Generated Unique ID. The below mentioned sample and proposed UID constitutes of four (4) parts, where each is a different identifier:

CK RP 33 A001

CK here denotes “Club Kautilya”, which is used an identifier for differentiating Club Kautilya

Personal Resource Planner from all Other Partners of Microsec

A001 here is the alpha numerical number given to Personal

Resource Planner. The same number may be present but it will

for a different state

33 here denotes “West Bengal” which is represented by the CK

code of the State, which signifies the state of the Personal Resource

Planner

RP here signifies “Personal Resource Planner”, which is again

used here to differentiate them from Club Kautilya

Members/Employees/Other Resources

Total Number of Unique Personal Resource Planner IDs that can be created is around 8.58 Lacs (Pan India)


Personal Resource Planner – Branch Code Each and every Personal Resource Planner’s Branch will be allocated a System Generated Unique ID. The below mentioned sample and proposed UID constitutes of four (4) parts, where each is a different identifier:

Total Number of Unique Personal Resource Planner Branch Codes that can be created is around 85.8 Lacs (Pan India)

CK RP 33 A001 B01 CK here denotes “Club Kautilya”,

which is used an identifier for differentiating Club Kautilya


A001 here is the alpha numerical number given to Personal Resource Planner. The same number may be

present but it will for a different state

33 here denotes “West Bengal” which is represented by the CK

code of the State, which signifies the state of the Personal Resource

Planner

RP here signifies “Personal Resource Planner”, which is again

used here to differentiate them from Club Kautilya

Members/Employees/Other Resources

B01 is the Branch Code generated under the PR-

PLNR. Where B signifies the Branch and 01 is the branch

number

ID Nomenclature LogicPersonal Resource Planner – Employee Each and every Personal Resource Planner’s Branch will be allocated a System Generated Unique ID. The below mentioned sample and proposed UID constitutes of four (4) parts, where each is a different identifier:

Total Number of Unique Personal Resource Planner Employee IDs that can be created is more than 8.58 Crores (including Employees at their Branches, Pan India)

CK E 33A001 01



01 here is the numerical given to the Employee of the Personal Resource Planner’s Employee

E here signifies “Personal Resource Planner’s Employee”,

which is again used here to differentiate them from HO

Employees

33A001 here is taken from the Personal Resource Planner’s ID

ID Nomenclature LogicHead Office – Employee Each and every HO Employees will be allocated a System Generated Unique ID. The below mentioned sample and proposed UID constitutes of three (3) parts, where each is a different identifier:

Total Number of Unique HO Employees IDs that can be created is more than 0.67 Lacs (Pan India)

CK HOE AA01



AA01 here is the alpha numerical given to the Employee of the Head

Office’s Employees

HOE here signifies “Head Office’s Employee”, which is again used here to differentiate them from

Personal Resource Planner’s Employees

ID Nomenclature LogicRegional Office – Employee Each and every RO Employees will be allocated a System Generated Unique ID. The below mentioned sample and proposed UID constitutes of three (3) parts, where each is a different identifier:

Total Number of Unique HO Employees IDs that can be created is more than 0.67 Lacs (Pan India)

CK RWE AA01



AA01 here is the alpha numerical given to the Employee of the Head

Office’s Employees

RWE here signifies “Regional Office’s Employee of West”,

similarly for East(E), South(S), North(N)

ID Nomenclature LogicMembers Each and every Member will be allocated a System Generated Unique ID. The below mentioned sample and proposed UID constitutes four (4) parts, where each is a different identifier:

Total Number of Unique Member IDs that can be created is more than 8.58 Crores (Pan India)

CK M 33 A00001



A00001 here is the alpha numerical number given to

Member. The same number may be present but it will for a

different state

33 here denotes “West Bengal” which is represented by the STD

code of the Capital, which signifies the state of the Member

M here signifies “Member”, which is again used here to differentiate them from Club Kautilya Members from all other Microsec Members

ID Nomenclature LogicSummary The system can generated a maximum of 10 Unique Branch Codes and 100 Employees IDs for each Personal Resource Planner. The system will also generate approximately 9 Crores Unique Member IDs on Pan India basis. A HO Employee (including super HO and ROs) will be allocated an approximate 13 Personal Resource Planners to serve (irrespective of their positions and profile in the company/organization).

User Types



User Type Creation


Creation


User Type Creation

MASTER USER (HO/RO)

CK-EMPLOYEE (HO/RO)


EMPLOYEE OF PR PLNR

CLUB MEMBER

User Creation InterfacesUser Types

ADMIN PANEL

ADMIN PANEL

WEB INTERFACE

WEB INTERFACE & ADMIN BOTH

WEB INTERFACE

User Type Creation

Admin Interfaces for User CreationThis is for Head Office and Regional Office’s Master Users and Employees

and PR Plnr’s Employee

User Type Creation

CREATE MASTER USER (HO/RO)

CREATE EMPLOYEE (HO/RO)

CREATE USER EDIT USER

Admin Interface – User Creation Landing

CREATE EMPLOYEE (PR Plnr)

User Type Creation

Admin Interface for User Creation – MASTER UserThis is for Head Office and Regional Offices

User Type Creation

CREATE MASTER USER (HO/RO)

All

Access Privilege

EAST WEST NORTH SOUTHSave

F Name M Name L NameEmail ID:

HR Code:DOB:

Password:

City: State:

User Type Creation

FunctionalityIf Access Privilege is set to All then the Master User will be treated as Master User (HO), which means Master User (HO) can access all the Planners’ details as well as their Members. If Access Privilege is set for any specific zone then the Master User will be treated as Master User (RO), which means Master User (RO) can access Planners’ details of the specified zone along with their Members.

User Type Creation

Admin Interface for User Creation – EMPLOYEE(HO/RO)This is for Head Office and Regional Offices

User Type Creation CREATE EMPLOYEE (HO/RO)


Mobile:HR Code:

All

Access Privilege

EAST WEST NORTH SOUTH

DOB:

Personal Resource Planner List Access list

123456345123567553567993

123456567

List A List B

Department: AllBDFPTrainerCRM

Password:

City: State:

Save

User Type Creation

Functionality

If Access Privilege is set to All then the Employee will be treated as Employee (HO), which means Employee (HO) can access the selected Planners’ details as well as their Members of all zones.

If Access Privilege is set for any specific zone then the Employee will be treated as Employee (RO), which means Employee (RO) can access selected Planners’ details of the specified zone along with their Members.

Once the privilege has been set for the new Employee , list of Personal Resource Planner under that zone will be populated on the left hand side list ( List A) and then Admin can set the access by transferring the PR Plnrs to List B. Now this employee can only access the details of the PR Plnrs who are on list B.

PR Plnrs details means, PR Plnrs profile, Business Updates, Members details who are mapped with the PR Plnrs etc. Type of details, one employee can access depends on the Employee’s department.

Create an Employee Code and Map with the respective Branch Code ( As we are creating separate branch codes for our HO and four ROs)

Send the details to Employees email ID and also to the Master User’s ( Respective Zone) email id.

User Type Creation

Admin Interface for User Creation – EMPLOYEE(PR Plnr)

User Type Creation CREATE EMPLOYEE (PR Plnr’s Employee)

Member List Access list

123456345123567553567993

123456567

List A List B


HR Code:DOB:

Password:

City: State:

Save

All

Access Privilege

EAST WEST NORTH SOUTH

Select PR Plnr

User Type Creation

Functionality

Admin can create employee for specified PR-PLNR using the above interface.PRPL’s employee can access the selected members’ details.

User Type Creation

WEB Interface for User Creation – EMPLOYEESThis is for Personal Resource Planners

We have to open the following screen from the Website

User Type Creation CREATE EMPLOYEE (PR Plnr’s Employee)

Member List Access list

123456345123567553567993

123456567

List A List B


HR Code:DOB:

Password:

City: State:

Save

FunctionalityPRPL’s employee can access the selected members’ details. PR-Plnr will get this interface in post login phase where he can add his employee directly from website.

User Type Creation

REGISTRATION PROCESS FLOW Personal Resource Planners

User Type Creation

FORM FIELDS

Personal Resource Planners - Registration

User Type Creation

Fields for Page 1: First Name*Middle Name Last Name*Email ID*Mobile No* City*Area (dropdown)*

Fields for Page 2: Enter the Code

User Type CreationFields for Page 3: Demographic Profile

First Name* (pre-populated)Middle Name (pre-populated)Last Name* (Pre-populated)Date of Birth*Gender*Pan No./UID*Occupation*EducationAddress Line 1*Address Line 2City* (pre-populated)Pincode* Email ID* (pre-populated)Alternative Email IDResidence Contact No.Business Contact No.Mobile No.* (pre-populated)Fax No.User ID* ( Email ID) – un editable fieldPassword*Confirm Password* (Password Recovery)Secret question & Answer* * TEMP ID should generate after proceeding from this page

User Type CreationFields for Page 4: Add Other Details ( Completely Non Mandatory- Collapsible Section)

Communication PreferenceLocation

ResidenceOffice

MediumEmailCallIn-Person

TimeFromTo

Marital Status (dropdown)

No. of Dependants

Details of DependantsNameDoBRelationship


Professional DetailsCurrent EmployerDesignation/TitleNature of Work/BusinessTotal Work Experience

Asset DetailsHome (Self Owned/Rented/Leased)Office (Self Owned/Rented/Leased)Vehicle (three options)

4-wheeler/2-wheeler (dropdown)MakeModelYear

Primary Bank You Use

Bank Name

Branch

Account no

Have you read Chanakya’s Arthshasthra?Yes/No

User Type CreationFields for Page 5: Upload Section Upload scanned copy of PAN*Address Proof of Office(any one)-Electricity bill/registered Rent agreement/Tel bill/Passport*

User Type Creation

FLOW


Input name, email, mobile no, city, area, pin

Verification code sent through email/sms

Enquiry details with reference code

Input Verification code IF Ok

YesNo

Proceed to input demographic details, upload documents in steps

Pr-Plnr details

Confirmation msg along with login info & detailing abt the process through email to PR-Plnr, admin & Concerned Depts.

Verification Of uploaded Docs

Approval and PR-PlnrID generation along with Branch Code

Sent email for pending docs (due to improper uploaded docs)

IF Ok

Yes

No

Login using PR-Plnr ID/email id & password

Generate & send temp id/password to complete pending details

State Code

Verification Of signed hard copies with uploaded soft copies

IF Ok

Yes

Sent email for approval pending (due to Soft copy & hard copy mismatch)

NoAdmin Activities

User Type Creation


Personal Resource Planners – Registration Explanation of the Process Flow

User Type Creation

Personal Resource Planners – Registration – Explanation of Process Flow

There can various cases witnessed when a Personal Resource Planner registers with Club KautilyaCase 1: When Registration is Complete (with no pending/mismatch/discrepancies/delay)PRPL Activity: A Personal Resource Planner (otherwise referred to as “PRPL” later in the document) registration page will constitute of around 6 pages (including all), which when filled up completely by the PRPL will be considered as completePage 1: Herein the PRPL will fill details, such as Name, Email ID, Mobile No., City, Area and Pincode to generate a Verification Code (this will be used as a check to verify the authenticity of the Email ID and Mobile No. provided). Data Points, such as City, Area and Pin code will also be used later when a Member registers and/or while mapping the Member. Once the data as filled and submitted, the system will then:

Generate a Verification Code and send the same at the provided PRPL’s Email ID and Mobile No.Store the data and pre-populate the same in the Page 3

Page 2: Once the code is generate and the PRPL will then be prompted to enter the exact code in this page. Once entered and checked by the system, the PRPL will be taken to Page 3Page 3: Once on this page, the PRPL will then be prompted to enter their Demographic ProfilePage 4: This page will focus primarily on seeking details about the PRPL current professional/business/employment related details (this will be helpful when profiling a PRPL and also when designing Marketing related activities)Page 5: On this page, the PRPL will upload documents supporting the data and information provided in Page 3 and also facilitating the Operation and/or the Administration Team in selecting/approving/rejecting a PRPLPage 6: This page will basically be used to review and change (wherever necessary) all the details furnished by PRPL in the earlier pages, before they submit

User Type Creation


Once all the details are completely filled and submitted (as per the knowledge of PRPL), the system will then:Thank the PRPL for their registration through a HTML Pop-up page and detailing about the processSend an email to the registered Email ID of the PRPL with the similar details as mentioned above Notify the updates on admin panel

Admin Activity: Once the admin is finished checking the registration details, documents uploaded and matching the documents details with the details of registration. He/she will then click the “Verified” tab. Here the system will then:

Generate a PDF document containing the Agreement and the snapshots of the documents uploaded by the PRPL. This document will then be sent to the respective PRPL’s Email ID, for him/her to download, sign in original and send the same at the provided address through courier

Admin Activity: Once the document is received in physical by the admin, he/she will then re-check the document and if found in order will go ahead and click the “Approved” tab in the system. Then, the system will:

Generate a Planner ID in the systemSend an email to the PRPL with an authentication link along with generated Planner ID/Email ID & passwordSend sets of requisite documents along with the PRPL CK Planner ID to various other internal departments through email, corresponding email ids to be already feed in the system

User Type Creation


Case 2: PRPL Activity: When Registration is In-Complete due to Non-Availability of the Documents/TimeOnce PRPL has reached Page 5 of the registration process, they will have two options at their disposal:

Upload the relevant and related documents orDo it later, whether that be due non-availability of time and/or documents

In the latter case, the PRPL will need to generate a Temp ID, by clicking on the “Do it later”. This when clicked, the system will then:

Generate the Temp ID Flash the Temp ID on the ScreenSend the Temp ID & password to the PRPL via Email

This system generated Temp ID, can be used by the PRPL to log-in at a later date to upload and complete the registration process. This Temp ID will only be valid for a period of 15 days After this, the process followed is as mentioned under Case 1 point 1 :Page 6 onwards

User Type Creation


Case 3: Admin Activity: When Registration is In-Complete due to Pending/Mismatch/Wrong Data and/or UploadsFollowed after Point 3 as mentioned under Case 1 Once the admin starts checking the registration details, documents uploaded and matching the documents details with the details of registration and found them to be Pending/Mismatched/Suspicious/Not In-Order, he/she will then click the “Document Pending” tab. Here the system will then:

Generate the Temp ID. This Temp ID will only be valid for a period of 15 daysFlash the Temp ID on the ScreenSend an email informing the PRPL about the Pending Situation along with the Temp ID & password

After this, the process followed is as mentioned under Point 4 under Case 1

User Type CreationPersonal Resource Planners – Registration – Explanation of Process FlowCase 4: Admin Activity: When Registration is In-Complete due to Wrong/In-Correct/Not-Clear Physical Documents is ReceivedFollowed after Point 4 as mentioned under Case 1 Once the document is received in physical by the Operations Executive, he/she will then re-check the document and if found not in order will go ahead and click the “Approval Pending” tab in the system. Then, the system will:

Generate the Temp ID. This Temp ID will only be valid for a period of 10-15 daysFlash the Temp ID on the ScreenSend an email informing the PRPL about the Pending Situation along with the Temp ID & password

After this, the process followed is as mentioned under Point 5 under Case 1

Conclusion: So there will be total 4 actions in admin panel as follows:Verified –Yes/No (Option button)

If All uploaded documents are ok then Yes else NoApproved – yes/No (Option button)

If Soft copy & hard copy mismatch then No Else YesActive/ Inactive

Activate the PRPL Account (default is active after approval)Deactivate the approved account (On hold in later stage)

Verification code checking activity in registration process can be set on or off from admin.

During approval process ,a flag needs to be set with the PR –PLNR whether they are Individual or operating from HO/RO.

Master user HO by default can access all PR-PLNRs.

Master user RO by default can access all PR-PLNRs of the specified zone.

No Employee can access PR-PLNR HO and PR-PLNR RO.

User Type Creation

REGISTRATION PROCESS FLOW Members

CK-MEMBER REGISTRATION – Key Information

1. Member can be registered in two waysa. Direct from website (Web User)b. Via a Personal Resource Plannerc. Members can be logged in with Membership ID/Email ID and Password ( For reference check bharatmatrimony.com)

2. ‘Members’ are actually ‘Clients’

3. Personal Resource Planner ( PR-Plnr) are actually ‘Business Partners’

4. HO – Head Office ( Also treated as a Personal Resource Planner)

5. RP – Resource Plan – this will be of two types, d. Initial Resource Plan ( This will be done during Registration Process) - IRPe. Comprehensive Resource Plan ( This will be done in later stage and no relation with the registration process – CRP

6. DD - dropdown

User Type Creation

CK – MEMBER REGISTRATION Direct from WEB (WEB-USER)

User Type Creation

User Type Creation

FORM FIELDS

Member - Registration

User Type Creation

Fields for Page 1: First Name*Middle Name Last Name*Email ID*Mobile No* City*Area (dropdown)*

Fields for Page 2: Enter the Code


First Name* (pre-populated)Middle Name (pre-populated)Last Name* (Pre-populated)Date of Birth*Gender*Pan No./UID*Occupation*EducationAddress Line 1*Address Line 2City* (pre-populated)Pincode* Email ID* (pre-populated)Alternative Email IDResidence Contact No.Business Contact No.Mobile No.* (pre-populated)Fax No.User ID* ( Email ID) – un editable fieldPassword*Confirm Password* (Password Recovery)Secret question & Answer*



ResidenceOffice


TimeFromTo


No. of Dependants







Bank Name

Branch

Account no


User Type Creation

Fields for Page 5 : Details for Resource Planning (IRP)

Refer the attached EXCEL sheet for detail fields, calculation and output format

User Type Creation

FLOW

CK – MEMBER REGISTRATION – Direct from WEB (WEB-USER)

Input name, email, mobile no, city and area (DD)

PR-Plnr Details

IF PR-Plnr Exists for specified

city Service not available email sent to user

Enquiry details with Reference ID

Proceed to input Demographic details, Login details, IRP inputs & others in steps

Membership details

IF all IRP input s given

Generate IRP

Yes

Make available to PR-Planner

/Admin /Member

NoPeriodical reminder through email for incomplete IRP/ other inputs

Email sent to member about what to do next Along with his PR-Plnr details

If all inputs (Irrespective of IRP

details )given

Send confirmation email for system generated membership ID along with a A/c activation link to user

Yes

Member login Member Landing Page

PR-Planner to schedule appointment, update appointment

No

Email sent to Concerned Depts

notifying the membership

creation

Approval

Default-Mapping with HO

B

Member Mapping with PR-PLnr

A

Yes

No

Admin Functionality

ATill this stage the web user is by default mapped with HO. Now Admin will have option to map the respective user to a specific Personal Resource Planner or leave him mapped with the HO itself and send him the email about what to do next Along with his PR-Plnr details.

BAdmin should have facilities to send the IRP to the Mapped PR-Plnr or Member or Both. Flexibility to send any other person, such as Business Manager etc.

User Type CreationCK – MEMBER REGISTRATION – Direct from WEB (WEB-USER)

User Type Creation

CK – MEMBER REGISTRATION Via Personal Resource Planner

User Type Creation

FORM FIELDS

Member – Registration via Planner


First Name* (pre-populated)Middle Name (pre-populated)Last Name* (Pre-populated)Date of Birth*Gender*Pan No./UID*Occupation*EducationAddress Line 1*Address Line 2City* (pre-populated)Pincode* Email ID* (pre-populated)Alternative Email IDResidence Contact No.Business Contact No.Mobile No.* (pre-populated)Fax No.User ID* ( Email ID) – un editable fieldPassword*Confirm Password* (Password Recovery)Secret question & Answer*Captcha



ResidenceOffice


TimeFromTo


No. of Dependants







Bank Name

Branch

Account no


User Type Creation

Fields for Page 3 : Details for Resource Planning (IRP)

Refer the attached EXCEL sheet for detail fields, calculation and output format

FLOW

User Type CreationCK – MEMBER REGISTRATION – Via Personal Resource Planner

Input Demographic details, Login details, IRP inputs & others in steps

Membership details

IF all IRP input s given

Generate IRP

Yes

Make available to PR-Planner

/Admin /Member

NoPeriodical reminder through email for incomplete IRP/ other inputs

Email sent to member about what to do next Along with his PR-Plnr details

If all inputs given

Send confirmation email for system generated membership ID along with a A/c activation link to user and P R Plnr

Yes

Member login Member Landing Page

PR-Planner to schedule appointment, update appointment

No

Approval

Default-Mapping with P R Plnr

A

P R Plnr logged in and click “Register New Member from the P R Plnr landing page

Email sent to Concerned Depts

notifying the membership

creation

A

Admin Functionality

Admin should have facilities to send the IRP to the Mapped PR-Plnr or Member or Both. Flexibility to send any other person, such as Business Manager etc.

User Type CreationCK – MEMBER REGISTRATION – Via Personal Resource Planner

User Type CreationCK – MEMBER REGISTRATION - Explanation of the Process Flow for both who register directly from web or via a Personal resource Planner

Members from the area of Personal Resource Planner will only be able to register with Club KautilyaThe above criteria will be checked with the help of three parameters – City and AreaMember Registration Page will be based on initial verification by sending a code on the Members email id and mobile numberIn case, the Member represents an area where there are no Personal Resource Planner present, the system will then:

Intimate the Member that, the registration cannot be taken forward stating the reason via HTML Pop-up Page and EmailStore the details for future referenceNot send the Membership No., only Reference Code to be sent

In case, the Member is from an area where Club Kautilya has a Personal Resource Planner present, the system will then:

Send a verification Code via Email and SMS to the MemberStore the details already feed

After the Member has received and feed-in the code, he/she will only then be allowed to proceed further to enter his/her other demographic details to registerThe stage-1 form will only seek “Basic Demographic Profile” and will be mandatory, such as – Name, DoB, Gender, PAN No, Occupation, Address, Area, City, State, Pincode, Email ID, Education, Residence No., Business No., Mobile No.,Fax No., User ID and Password.


The stage-2 form will be optional and will seek additional demographic, lifestyle and asset details, such as – Professional Details, Asset Details like Home/Vehicle Details.(This form can be skipped by the Member and he/she may wish to enter these data later at his/her convenience)The stage-3 & 4 form will seek details pertaining to Initial Resource Plan(This form can be skipped by the Member and he/she may wish to enter these data later at his/her convenience)In case, the Member has filled-in all the relevant details required for the resource plan, the system will then:

Generate the Resource Plan and send it to the mapped (in case, the Member is direct web user, by default they would be mapped to HO (which is also to be considered as a PRPL), which the Admin Team can change at a later date and map any other Personal Resource Planner matching City and Area) Personal Resource Planner, who will then be responsible to schedule a meeting with the Member and understand him/her the planSend an email to the Member detailing about the process and the details of the mapped Personal Resource PlannerWe need to presently track the status of the enquiry i.e.,

Appointment fixedMet withStatus update ( Closed / Lost etc )


In future the appointment data to be parked in the CRM lead management module for process flow.In case, the Member has not filled-in all the relevant details required for the resource plan and has skipped the form. In such a situation also the Member is able to register with Club Kautilya, but here the system marks the Member and sends soft reminder emails at regular intervals stating him/her to fill and generate his Resource Plan (after which point no. 10 is executed)After the Member, has submitted (in all the cases), he/she is been sent an authentication email, which when clicked will prompt the Member to enter his/her user id and password. Simultaneously, the system will then also generate a Membership No. for the Member.After login members will be taken to an intermediary web page (between Club Kautilya Website and PRP Solutions Website), which will also act as a Dashboard; detailing about PRP Solutions, Member Profile Meter, Areas of Quick Action, Any Marketing Communication, etc.

User Type Creation




Creation


Personal Resource Planner's Branch Creation

FORM FIELDS


Fields for Page 1:

PRPL Full Name : Pre populated PRPL ID : Pre populated Contact Person Details F_Name, M_Name, L_Name*Date of Birth*Gender*Address Line 1*Address Line 2State*City*Pincode*Email ID*Mobile*

Fields for Page 2:Upload SectionUpload scanned copy of PANAddress Proof of Office (any one) - Electricity Bill/Registered Rent Agreement/Telephone Bill/Passport


FLOW

Login using PR-Plnr ID/email id & password

Proceed to input demographic details, upload documents in steps

Branch details

Confirmation email to PR-Plnr & admin

Verification Of uploaded Docs

Branch approval & Branch Code generation for the PR-PLNR

IF Ok

Yes

No

Sent email for pending docs

State Code

Verification Of signed hard copies with uploaded soft copies

IF incomplete

upload

Yes

No

IF Ok

Yes

No

Admin Activities


Explanation of the Process Flow


An existing Personal Resource Planner (PRPL), will only be able to register/create a new branch under him/her when in log-in conditionThere can various cases witnessed when a Personal Resource Planner registers a Branch under him/her with Club KautilyaCase 1: When Registration is Complete (with no pending/mismatch/discrepancies/delay)Once logged-in, the PRPL needs to click on the “Create a Branch” Tab on the Right Hand side of the pageThis opens a new window, where the PRPL gets to see his Full Name as “Personal Resource Planner” and ID as “Planner ID”, which is pre-populated through the systemThen the PRPL needs to feed-in data regarding the New Branch (step-wise)The stage-1 form will only seek “Basic Demographic Details” and will be mandatory (marked) as provided in the next page under “Fields for Page 1”The stage-2 form will be the area where the PRPL needs to upload supporting documents relating to the new branch(This form can be skipped by the PRPL and he/she may wish to enter these data later at his/her convenience)Once all the details are completely filled and submitted (as per the knowledge of PRPL), the system will then:

Thank the PRPL for branch creation through a HTML Pop-up page and detailing about the processAn email is sent to the registered Email ID of the PRPL with the similar details as mentioned aboveAnother email is sent to the Admin notifying them about such activity/registration

Once the Admin is finished checking the registration details, documents uploaded and matching the documents details with the details of registration. He/she will then click the “Verified” tab. Here the system will then:

Generate a PDF document containing the Agreement and the snapshots of the documents uploaded by the PRPL. This document will then be sent to the respective PRPL’s Email ID, for him/her to download, sign in original and send the same at the provided address through courier


Once the document is received in physical by the Admin, he/she will then re-check the document and if found in order will go ahead and click the “Approved” tab in the system. Then, the system will:Generate a Branch Code in the systemSend sets of requisite documents along with the CK Branch Code to various other internal departments for them to create and map Branch Codes in their respective system with the CK Branch Code

PRPL then needs to assign the privileges for the said branch, for them to access the CK Website. If not done, the branch personnel will not be able to access the data/information Case 2: When Registration is In-Complete due to Non-Availability of the Documents/TimeOnce PRPL has reached “Upload Section” of the registration process, they will have two options at their disposal:

Upload the relevant and related documents orDo it later, whether that be due non-availability of time and/or documents

In the latter case, the PRPL will need to generate a Temp ID, by clicking on the “Upload Later/Brower Cross Tab”. This when clicked, the system will then:

Generate the Temp ID Flash the Temp ID on the Screen and Send the Temp ID to the PRPL via Email

This system generated Temp ID, can be used by the PRPL to log-in at a later date to upload and complete the registration process. This Temp ID will only be valid for a period of 10-15 daysAfter this, the normal process followsCase 3: When Registration is In-Complete due to Wrong/In-Correct/Not-Clear Physical Documents is ReceivedFollowed after “Upload Section”Once the document is received in physical by the Admin, he/she will then re-check the document and if found not in order will go ahead and click the “Pending” tab in the system. Then, the system will:

Generate the Temp ID. This Temp ID will only be valid for a period of 10-15 daysFlash the Temp ID on the ScreenSend an email informing the PRPL about the Pending Situation along with the Temp ID

After this, the normal process follows