Hi Friends,

Even as I launch this today ( my 80th Birthday ), I realize that there is yet so much to say and do. There is just no time to look back, no time to wonder,"Will anyone read these pages?"

With regards,
Hemen Parekh
27 June 2013

Now as I approach my 90th birthday ( 27 June 2023 ) , I invite you to visit my Digital Avatar ( www.hemenparekh.ai ) – and continue chatting with me , even when I am no more here physically

Thursday, 17 February 2022

DARFT -- MR.-VIVEK MEHTA L&T POWAI

DRAFT -- MR. VIVEK MEHTA L&T POWAI

Draft
Mr. Vivek Mehta
L&T / Powai
07-05-03

Dear Vivek,

ResuMine / ResuSearch Webservice

As suggested by Pronoti, our team (Kartavya / Abhi / Inder) visited your office yesterday and met/discussed our proposed webservice with your team (Pronoti / Anuj / Gautam / Jawalkar).

I believe your team asked for "customization" of ResuMine / ResuSearch in respect of the following:

#1 The webservice should enable you to add "new" functions and related "keywords" for each new function — directly on your own, ON-LINE, when you subscribe to the webservice.

#2 It should also enable you to create a list of educational institutions (Colleges / Universities etc.) — ONLINE, directly on your own, so that:

  • ResuMine extracts this field
  • ResuSearch searches on this field

#3 For emailing, you would like to use LOTUS instead of Outlook Express. (Outlook is crossed out and replaced with Lotus)

I wish to confirm that we will incorporate these "customization" features in our webservice, which is slated for commercial launch on June 27th (— my 70th birthday).

However, what is not possible to incorporate at this stage is:

Developing the webservice on JAVA platform (as suggested by Mr. Jawalkar).

With hardly ... weeks left for the commercial launch, we are set.

For over 6 months now, we have designed our webservice-architecture along the .NET platform, since a great majority of the webservices in the world are designed around this platform. We are also basing it on HR-XML, which is the emerging "world-standard" for all HR software.

The reason for choosing these platforms is simple.

A webservice must be capable of being able to "talk" and exchange data with any other webservice.
E.g.: There are webservices offering "online" testing of candidates, and you may well want your job-applicants to undergo some such test before considering him.
You may want that the "result/score" obtained by such a candidate gets firmly incorporated in his resume — as a permanent record.

.NET vastly simplifies such exchanges of data.

Whereas, JAVA may have its own merits — and we would certainly examine this option in the future — with barely 6 weeks left for the commercial launch of our webservice, it just does not appear feasible at this stage for us to also develop the JAVA version in parallel with the .NET version.

Developing Resume/ResSearch as "Enterprise" versions (as opposed to webservice).

I want to draw your attention to the fact that our "GLOBAL RECRUITER"...

… is being offered as a prepaid/pay-per-use webservice, comprising in all 5 modules as follows:

  1. Advt. Composing/Publishing
  2. Manpower Request Module (Ad-Compose)
  3. Resume Management Module (Resume/ResSearch)
  4. Interview Management Module
  5. Employee Management Module
  6. Organization Management Module

These are described in detail in the folder given to you.

You will notice that Resume/ResSearch is just one of these modules — all of which form part of an "Integrated" database/application.

Since we plan to offer this integrated application as a monolithic webservice, it is not possible to simply "take out" any particular module and license it as an enterprise version.

Only as a webservice, Resume/ResSearch becomes truly self-learning, knowledge-capturing, artificial intelligence software, as thousands of corporates start processing millions of resumes, as our webservice subscribers!

As an isolated/stand-alone enterprise application, Resume/ResSearch would deprive itself of the accumulated knowledge/wisdom of thousands of domain-experts from around the world.

I hope I have answered your misgivings, if any. If required, I would be happy to come over for a personal discussion.

In the meantime, we are proceeding to incorporate in our webservice the three "customization" requirements mentioned earlier.

With regards
H.C.P.







 

No comments:

Post a Comment