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

Friday, 4 July 2003

SCOPE OF WORK

SCOPE OF WORK

Cyril / Hugh/ Yogesh

 The scope of work is schematically described in the enclosed diagram. The basis inputs are TEXTS of various types. The printed texts will be scanned and subjected to an OCR software to convert into ASCII files. Then, there will be texts received

ELECTRONICALLY such as

   - Floppies

   - Fax

   - E : Mails

   - Computer files (Dial - Up / Internet / Intranet)

In both the cases, the software will search, identify and pick - out KEYWORDS and place them in appropriate BINS/ FIELDS, based on the "meaning" of each keyword. In this way, the software will Create a database (or several databases). This basic process will remain the same irrespective of the type / size / structure / format of the document being scanned (whether printed or electronically received document).

 Of course, all the keywords picked - out from a given document will be linked to that document (identified as belonging to that particular document).

Having created a DATABASE, it should be capable of being QUERRIED, by using any of the KEYWORDS (one or more, in the AND/ OR fashion). For each keywords "SYNONYM RINGS" WILL have to be created.

The search will produce a short list of all the records (documents) where such a designated / specified KEYWORDS appears. We should be able to VIEW all such records on the Screen (one by one) or be able to take print - outs.

By using a computer - memorized STANDARD - LETTER, we should be able to send - out the short - list to a given client.

Besides responding to a QUERRY shot from one of our own LAN Nodes, the software must permit a client to shot such a query from his own office computer by remotely logging - on to our Server thru a dial - up Modern or thru internet connection. This feature (of remote query) is absolutely essential. Of course, we must provide for a password within a password within a password (!) to ensure data - security.

of course, what part of the database each user will be allowed to access (locally or remotely) will be strictly defined in advance and rigidly administered. The users are :-

   - Self

          - Associated (e.g. Mankodi/ Gangolli etc)

          - Candidates

          - Clients

          - Foster Partner Member and may be

          - Anyone from Public.

What is expected of the software is REMOTE ACCESS CAPABILITY. And that should be built into the Software RIGHT NOW.

However,

Which user will be allowed to remote access

What databases and shoot

What type of quarries and

When (point of time)

Will be spread - out over next 2 /3 years.

However, in the first phase itself.

We want

1. Candidate to enter and modify their own biodatas remotely (This is the ONLY WAY, we can hope to build up a

    - Large candidate database

           - Quickly

           - Without hiring an army of data - entry operators or persons to scan typed bio - datas.

2. Candidates to be able to shoot queries to JOB BULETIN BOARD. This is the MOST POWERFUL VALUE - ADDED SERVICE (VAS) as far as employment / change - seeking executives is concerned. This VAS will be available only to those executives who register / enroll with us by

     - Remotely entering their biodatas

            - Sending biodatas on floppies.

    Once again, the idea is to transfer the data - entry burden onto the candidate himself.

3. Clients to be able to shoot "Executive Search Queries" remotely (from their own computers) exactly the way we would have done locally. The software will search and tell the client (or potential client) "How many suitable candidates we have in our database? - a number" Nothing more ! But this is a great way of HOOKING him ! If his need is really SERVIOUS, he would, next day, send a cheque (advance) along with search Request !considering that it would

- Cost him over a lakh of rupees to adventure that vacancy

- to take him 8 weeks to get response,

The bait of REMOTE ACCESS/ IMMEDIATE ACCESS/ CHEAP ACCESS is simply irrestible !

This is an IMPORATANT aspect of the cost-Benefit analysis of the software to be developed .

The rest of the REMOTE ACCESS applications can wait for 2/3 years – as each database gets built-up by scanning  thousand of pages of other documents, some of which are enclosed herewith.

h.c.parekh

Bio-data (Resume)

Samples of typed bio-datas are already given to you. These are quite typical. Some 5%–10% of the bio-datas arrive on fax. The software should be able to take care of these as well.

Before long we shall start receiving bio-datas:

  • on E-mail
  • on floppies
  • by remote “log-in” by candidates
  • candidates telephonically dictating to 3P staff
  • by voice-mail

The software should be able to take care of these as well.


While running OCR software (on scanned bio-datas), there is a possibility that 80% ASCII characters come out OK leaving 20% “errors” (spelling mistakes). Normally, these errors are corrected by Data Entry Operators on the screen.

This operation slows down the entire process. We would like to eliminate/avoid this operation if possible.

You should examine the possibility of your software to take care of this.

 KEY-WORDS

To identify & decipher all grammatically defined words such as:

  • Verb
  • Adverb
  • Preposition
  • Adjective
  • Nouns (Common Nouns / Proper Nouns)

 

FIELDS

To identify & decipher Adjectives and Nouns (whether Common Noun or Proper Noun) which are BIODATA RELATED. These include:

  • Name of Candidate
  • Name of Boss / Colleague / Subordinate
  • Companies
  • Addresses (several types) / PIN codes
  • Locations / Cities / Countries
  • Birth-date / Age
  • Industry / Employer
  • Phone Nos. (incl. STD / ISD codes)
  • Dates (of joining / leaving etc.)
  • Durations of employments (Periods)
  • Educational Qualifications (years of passing) / Colleges / Universities
  • Salary
  • Designations / Positions held
  • Departments
  • Functions
  • Skills
  • Knowledge
  • Attitudes
  • Attributes
  • Codes
  • Equipment
  • Products

 

  • Raw Materials
  • Manufacturing-related
  • Management-related
  • Engineering-related
    • Techniques
    • Processes
    • Languages
    • etc. etc.

The above is not a comprehensive list. It is only indicative. A comprehensive list can be prepared over a period of time by scanning thousands of bio-datas. This could be done by scanning over 40,000 bio-datas lying with us.

Even if most of these are OBSOLETE, the keywords contained in these are not obsolete, so these could be a good starting point for building a comprehensive list.

 CONVERTED BIO-DATA

A sample form is enclosed. This is only for guidance. We would be happy if you could come up with a superior presentation, which is both attractive/catchy and easy to print.

In the sample “converted bio-data” enclosed, there is no provision for writing descriptive “Achievements” and “past/current Job Responsibilities”. But these two paragraphs are a MUST, as you would notice from any of our currently formatted converted bio-datas.

Please take care of this.

CONTRACT FOR DEVELOPMENT OF ARDIS/ARGIS SOFTWARE

  • Scope of Work
  • Inputs / Outputs
  • Platform (Hardware / Software)
  • Upgradability / Flexibility
  • Integration
  • Documentation
  • Secrecy / Exclusivity / Ownership Rights
  • Future Support
  • Performance Guarantee
  • Time Frame / Benchmarks
  • Payment Schedule

DEFINITIONS

  • Bio-data (Typed or E-Mail or Faxed)
  • Key-Words & Fields
  • Converted Bio-data

 The scope of this project shall comprise development of a computer software.

TASK #1

The software shall be capable of reading typed bio-datas/resumes and picking out all the KEYWORDS.

Having picked out the keywords, the software shall assign each keyword to a specific FIELD (BIN) to which the keyword belongs, while also linking the keyword (and its field) with or linked to the particular (Permanent Executive Number — PEN).

In this way, the software shall create:

  • A DATABASE of keywords:
    • linked to specific executives (PEN)
    • linked to specific FIELDS

This means developing a SEARCH ENGINE for:

  • searching out each keyword
  • deciphering each keyword and deciding what it “means” (to enable placing it in an appropriate field)

The search engine shall also be able to:

  • Given one or more KEYWORDS (under which to search), the search engine should be able to identify/list all executives (PEN) against whose names these keywords appear (i.e. existing in their bio-datas).

 

The second task of the software would be to recreate (represent) the bio-data (of any executive) in a specific format called CONVERTED BIO-DATA.

The converted bio-data would have the option of printing or not printing:

  • Executive Name
  • Current Employer Name

and to be replaced by appropriate alternate codes/descriptions.


In the development of this software, the following may be assumed:

a. Use of existing scanner (H.P. Model 3P) & scanning software.

b. Use of existing OCR software.

 Of course the software shall be capable of using:

  • High capacity scanners
  • Improved versions of OCR softwares
  • DMP/Inkjet/Laser printers & even line-printers

INPUTS

  • The basic input will be any typed bio-data.

In Phase #2, we would like you to consider any printed advertisement (for advert) also as an input. This would be for the purpose of creating a DATABASE OF JOB BULLETIN BOARD.

This is because the basic capability of the search engine shall remain the same irrespective of whether it is working on:

  • a bio-data
  • or advertisement

This basic ability is:

  • to pick out KEYWORDS
  • place them in appropriate FIELDS
  • rearrange these in some formatted/tabular OUTPUT statement
  • subject them to be “searched” given certain SEARCH PARAMETERS (which will be Keywords)
  • create a “listing” of “Records Found”

OUTPUTS

As mentioned earlier, the desired outputs are:

  • a database of keywords, deciphered & stored in appropriate FIELDS
  • a converted bio-data
  • a converted (tabulated) job-advertisement

 

A.      Hardware

B.      The software should be designed for a Pentium-based Server & 156-based LAN. Of course, these will be upgraded in course of time.

C.      Software

D.      You may use ______ language and create a database (RDBMS).

Please configure around ______ Operating System, with a provision to changeover to ______ in course of time.


INTEGRATION

The software should be capable of seamless integration with our existing softwares, which are as follows:

We are also planning to incorporate OS-2 / WARP 4 (IBM) Speech Recognition Software on our LAN. The software should be capable of thorough integration with this or any other improved voice-recognition software.

PERFORMANCE ACCURACY

After installation and debugging the software should be capable of correctly picking up (identifying) and deciphering (i.e. to which field does the keyword belong) at least 80% of the keywords appearing in each bio-data/job-advertisement.

Within 6 months of the installation, this figure should go up to 90% and within 12 months up to 98%.


TIME-FRAME

For Installing

The software shall be installed on our system within 6 months from the date of this agreement. The detailed time-frame is shown at Annex: _______

For Debugging

The debugging shall be carried out within 2 months of the date of installation.

FUTURE SUPPORT

We are looking at a long-term relationship with FELYNX.

We therefore expect that we will continue to receive full support from you in future as far as:

  • Development of new modules of software
  • Maintenance of the software being developed

SECRECY / EXCLUSIVITY

After installation and debugging, you will handover the SOURCE CODE to us which will become our “Intellectual Property”.

You will not sell this software or part with it in any manner whatsoever to any other person or organization at any time.

You will not share or pass on to any other person or organization any information given to you and collected by you relating to our business (including any of our future plans that you may come to know of).

PAYMENT SCHEDULE

The total charges payable to you for the development of this software would be Rs. 5,50,000/- (Rupees five lakh and fifty thousand).

This total amount will be paid to you in installments as per payment schedule (Annex: ___) enclosed.

Each (payment) installment shall be made subject to satisfactory completion of software development activities which are planned to be completed by that point of time, as per TIME FRAME (Annex: ___).


Note (4/3/97):
According to Yogesh, if we wish this software to run on a client-server (LAN environment), then we will need to separately buy and install ORACLE RDBMS Software costing about Rs. 1 lakh!

The software that they will develop cannot run on NOVEL 3.11!! This means our total cost will be Rs. 5.5 + 1.0 = 6.5

Cyril had told us that in Rs. 5.5 itself, there are about Rs. 2.0 worth of “tools/compilers.”