Applitech Solution limited SRS
3P Consultants
Document flow table
|
Source |
Document |
Recipient |
|
Client |
Inquiry |
Consultant |
|
Consultant |
Proposal |
Client |
|
Client |
Signed proposal |
Consultant |
|
Consultant |
Sales order |
Client |
|
Consultant |
Project plan |
Management |
|
Consultant |
Advertising draft |
Consultant |
|
Consultant |
Advertising details |
Client |
|
Client |
Approved Ad. details |
Consultant |
|
Candidate |
Candidate interest |
Consultant |
|
Consultant |
Preliminary screening |
Client |
|
Client |
Interview schedule |
Consultant |
|
Consultant |
Interview details |
Candidate |
|
Candidate |
Confirm interview |
Consultant |
|
Client |
Interview feed back |
Consultant |
|
Candidate |
Interview feedback |
Consultant |
|
Client |
Compensation details |
Consultant |
|
Consultant |
Invoice |
Client |
|
Client |
Follow up |
Consultant |
|
Candidate |
Follow up |
Consultant |
|
Prospective candidate |
Prospective candidate |
Consultant |
1. Inquiry
Following details as captured
during an inquiry from a prospect or client
- Inquiry no. (auto)
- Type of inquiry (email, fax, website, tele,
personal meetings, other)
- Date of inquiry (not necessary the current (system)
date it can be back date also)
- Consultant handling inquiry
- Client details
5.1. Name of person
5.2. Company
5.3. Tele no
5.4. Address
- Mode of search (multiple modes) (advt., data
search, head hunting)
- Vacancy details (multiple vacancy)
7.1. Name of vacancy
7.2. No of vacancy
- Expected date of sending proposal
- Remarks
2. Proposal
- Proposal no (auto)
- Inquiry no
Confidential Oct-2000 Page 1 of 9
Applitech Solution limited SRS
3P Consultants
- Client name
- Type of proposal (flat rate, % rate, Turnkey)
- Covering letter details
5.1. Text as per format
- Terms and conditions
6.1. Professional fee details
6.1.1. Figure (numeric value for
% or value in currency)
6.1.2. Unit (could be % or value)
6.1.3. Currency
6.2 Minimum fee
6.3 Valuation of perks
6.4. Paying cycle (there can be
upto five phases)
6.4.1. Phase
6.4.2. Figure (numeric value for
% or value in currency)
6.4.3. Unit (could be % or value)
6.4.4. Currency
6.5. Out of pocket expense
6.5.1. Cost head
6.5.2. Cost
6.6. Copy format form samples
3. Sales order
- Order execution no (auto)
- Proposal no
- Inquiry no (D)
- Mode of search (D)
- Client details (D)
- Consultant name
- Schedule dates for
7.1. Identification of
prospective candidate
7.2. Completion of preliminary
interview
7.3. Sending of resumes of
candidate to client
7.4. Note (note has to be printed
at the bottom of sales order)
4. Project plan
- OEN
- Proposal no (D)
- Inquiry no (D)
- Mode of search (D)
- Client details
5.1. Name contact no
5.2. E-mail
5.3. contact person
5.4. address
- Consultant name
- Due date and actual date for activities (actual
date will be captured automatically)
7.1. Inquiry
7.2. Proposal
Confidential Oct-2000 Page 2 of 9
📄 Scan_0003.jpg (Page 3
of 9)
Applitech Solution limited SRS
3P Consultants
7.3. Sales order
7.4. Adv. Details
7.5. Candidate listing and head
hunting
7.6. Preliminary screening
7.7. Resume to client
7.8. Interview
7.9. Result sent to candidate
7.10. End date
5. Advertising details
- Advertising details no.
- Date
- OEN (can be multiple)
- Advertisement details (can be multiple)
4.1. Media
4.2. Location
4.3. Size
4.4. Cost
4.5. Approved by client (Y/N)
- Date of approval
- Note
- Response to add
6. Candidate listing
- Date (Auto)
- OEN
- Candidate details
3.1. PEN
3.2. Name of candidate
3.3. Organization
3.4. Designation
3.5. Educational Qualification
3.6. Past company details
3.7. Age
3.8. City
3.9. Phone (R)
3.10. Phone (O)
3.11. Mobile no.
3.12. Contact agency
3.13. Status
3.14. Comment
3.15. Mode of communication
3.16. Candidate response (Y/N)
7. Preliminary screening
Confidential Oct-2000 Page 3 of 9
📄 Scan_0004.jpg (Page 4
of 9)
Applitech Solution limited SRS
3P Consultants
- Date
- OEN
- Client name
- Candidate assessment
4.1. PEN
4.2. Candidate name(D)
4.3. Panel (multiple names)
4.4. Assessment sheet
4.4.1. Attribute name
4.4.2. Score
4.5. Overall assessment (out
standing, good, acceptable, not suitable)
4.6. Family background
4.7. Current company details
4.7.1. Brief info
4.7.2. Size
4.7.3. Turnover
4.7.4. No of employees
4.8. Strengths
4.9. Weakness
4.10. Product exposure
4.11. Industry exposure
4.12. Contribution to
organization
4.13. Salary breakup
4.14. Current compensation
4.15. Expected compensation
4.16. Availability
4.17. Housing (own, rent,
company)
4.18. Reason for change
4.19. Other info
4.20. Comments
4.21. Short listed by 3P (Y/N)
4.22. Short listed by client
(Y/N)
8. Interview schedule
- OEN
- Client name
- Date
- Multiple schedules
4.1. PEN
4.2. Name
4.3. Venue
4.4. Tel
4.5. Time
4.6. Date/day
4.7. Mode of communication
4.8. Note
Confidential Oct-2000 Page 4 of 9
📄 Scan_0005.jpg (Page 5
of 9)
Applitech Solution limited SRS
3P Consultants
4.9. Other info
4.10. Candidate confirmation (if
timings are not confirmed re scheduling of interview)
4.11. Feedback from client
(Interview Selected rejected hold and shortlist, if short listed than arranging
for subsequent interview till get selected or rejected)
9. Compensation details of
selected details Candidates
- OEN
- PEN
- Client name
- Monthly (Rs. Per month prorate)
4.1. Basic salary
4.2. DA/ equivalent
4.3. Housing
4.4. HRA
4.5. Soft/Hard furnitining
4.6. Car/conveyance allowance
4.7. City compensation
4.8. Education
4.9. Servant
4.10. Electricity
4.11. Gas
4.12. Medical
4.13. News paper/periodicals
4.14. Driver salary
4.15. Entertainment
4.16. Telephone
4.17. Other allowance
reimbursement/payment 1
4.18. Other allowance
reimbursement/payment 2
4.19. Other allowance
reimbursement/payment 3
- Sub total (total of all above elements in monthly
category)
- Annual (Rs. Per month prorate)
6.1. Bonus
6.2. Exgratia (in lieu of bonus0
6.3. LTA
6.4. Commission/incentive/profit
sharing (estimated or projected)
- Sub total (total of all item under annual)
- Retirement benefits
8.1. Provident funds (12%)
8.2. Super annuation (15%)
8.3. Gratuity (4%)
9. Sub total (total of the item
under retirement benefits)
- Indirect benefits
10.1. Benefit due to interest
savings (over 18% rate of interest) arising out of loans advanced by the
employer
10.2. Club fees (entrance fees /
60)
10.3. Lump sum
furniture/furnishing outlay (amount / 60)
10.4. Sign off bonus (/ 60)
10.5. ESOPs (market value /60 )
- Sub Total (total of all items under indirect
benefits)
Confidential Oct-2000 Page 5 of 9
📄 Scan_0006.jpg (Page 6
of 9)
Applitech Solution limited SRS
3P Consultants
- Total (Total of all sub total)
9. Follow up with client
- OEN
1.1. Activity
1.2. Date of follow up
1.3. Outcome
1.4. Next follow up date if any
1.5. Mode of communication
10. Follow up with candidate
- OEN
- PEN
2.1. Activity
2.2. Date of follow up
2.3. Outcome
2.4. Next follow up date if any
2.5. Mode of communication
Confidential Oct-2000 Page 6 of 9
📄 Scan_0007.jpg (Page 7
of 9)
Applitech Solution limited SRS
3P Consultants
11. Prospective client
Client
Position
Candidate Name
Current company
Designation
Source
Comments
Office address
Residence address
Tel
Date of contact
Consultant
Confidential Oct-2000 Page 7 of 9
📄 Scan_0008.jpg (Page 8
of 9)
Applitech Solution limited SRS
3P Consultants
Masters
- Industry
1.1. Code
1.2. Name
- Product or Service
2.1. Code
2.2. Name
- Parent Group Details
3.1. Client code
3.2. Client name
3.3. Contact person
3.4. Contact telephone number 1
3.5. Contact telephone number 2
3.6. Contact telephone number 3
3.7. Correspondence address
3.8. Fax number
3.9. Email address 1
3.10. Email address 2
3.11. Industry name
- Company Details
4.1. Client code
4.2. Client name
4.3. Contact person
4.4. Contact telephone number 1
4.5. Contact telephone number 2
4.6. Contact telephone number 3
4.7. Correspondence address
4.8. Fax number
4.9. Email address 1
4.10. Email address 2
4.11. Parent group code
- Division details
- Currency
6.1. Code
6.2. Name
- Designation
7.1. Code
7.2. Name
Confidential Oct-2000 Page 8 of 9
📄 Scan_0009.jpg (Page 9
of 9)
Applitech Solution limited SRS
3P Consultants
- Designation level names
8.1. Code
8.2. Name
- Function
9.1. Code
9.2. Name
- Project Activity
10.1. Code
10.2. Name
- Follow up
11.1. Follow up activity code
11.2. Follow up activity
- Consultant
12.1. Consultant code
12.2. Name
- Candidate master (already available in oracle 8)
- Terms and conditions
- Media
15.1. Code
15.2. Name
- Communication type
16.1. Code
16.2. Name
- Language
- Billing
Confidential Oct-2000 Page 9 of 9
📄 Scan_0010.jpg
(Handwritten Note)
INFO. REQD (OUTPUT STATEMENT.)
$\triangleright$ What Shopping
Baskets (online) were received - on any given date?
- for any given period?
- for any given Consultant?
- from any given Client - Co?
- from any given
"Industry"?
- for any given
"Function"?
- for any given
"Designation-level"?
- from any given City / Region /
country?
DECISIONS IT WILL HELP TAKE
$\triangleright$ How are online
"Inquiries (i.e. shopping baskets) behaving? Going up / down?
$\triangleright$ Do we need
additional resources to handle increasing inquiries? Do we need to hire more
"Industry - specific" consultants.
$\triangleright$ Do we need to
open office (appoint franchisee associate) in any particular City / Region /
Country from where a large no. / % of shopping - baskets are originating?
Scan_0011.jpg (Handwritten
Note - MS/2)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ How many / which
shopping-basket got converted into an order? How long did it take – from
- receipt of shopping basket
- sending of proposal / terms
$\triangleright$ Which / how many
shopping-basket did not get converted into an order? What were the reasons in
each case? (few, most frequent "reasons" can be incorporated and can
be "clicked". Rest can be entered by typing.) All consultant wise
& overall summary.
DECISIONS IT WILL HELP TAKE
$\triangleright$ Which is the
most "frequent" reason for losing an order? Price? Delivery? Our late
response? Poor quality / quantity of resume database i.e. stock of candidates?
$\triangleright$ What can we do,
in each of these cases?
$\triangleright$ Are any
policy-changes warranted?
$\triangleright$ Should we
"revive" the case?
$\triangleright$ Should we make
an "exception"?
📄 Scan_0012.jpg
(Handwritten Note - MS/3)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ How many
Shopping-Baskets have been "answered" (i.e. proposal / terms sent)?
$\triangleright$ How many
remaining to be answered?
$\triangleright$ How long
remaining to be answered (in descending order)? We have promised to answer in
24 hours (on our website).
All of the above, to be
consultant-wise.
DECISIONS IT WILL HELP TAKE
$\triangleright$ What are reasons
for building up of a "backlog" – if any?
$\triangleright$ Which consultant
is in "arrears" & why? – Reasons?
$\triangleright$ Do we need to
"re-allocate" industries allocated to each consultant?
$\triangleright$ What / how to
re-allocate if a given consultant is going on leave / resigns?
📄 Scan_0013.jpg
(Handwritten Note - HS/1)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ "EXECUTIVES
APPOINTED SO FAR" Summary
- Industry-wise
- Func-wise
- Desig. level-wise
- Client-wise
- Date-wise
- Billing Amount-wise (Descending order)
- Overall.
DECISIONS IT WILL HELP TAKE
- To send-out promotional letters to chiefs of any
given Industry (names of executives appointed must be hidden; also letter
must not be sent to that very company from whom we had hired / pinched
that executive! Then promotion will boomerang!!)
- To help in "Advertising-Matter" (to
bolster our "claims"!)
- To approach / write to these very executive (whom
we appointed anywhere / anytime) for
$\triangleright$ recommending
someone
$\triangleright$ giving us
"business" from his new company / employer.
📄 Scan_0014.jpg
(Handwritten Note - HS/2)
INFO. REQD (OUTPUT STATEMENT)
- Analysis of all orders executed during
just-completed year / quarter / month.
DECISIONS IT WILL HELP TAKE
- Who was our biggest / smallest client (in terms of
order-value)? Descending order of value wise.
- A-B-C analysis of clients Vs. Order Values
(Cumulative)
- Where are most orders coming from? (Ind / Func /
Desig / Region wise). Where should we focus our efforts?
- Are we putting all (or too many) of our eggs in one
basket? Is our business too heavily dependent on one / few clients
(industries / regions)?
- Is there a need for "diversifying" /
Spreading-out evenly?
- Which are the "SUNRISE" /
"SUNSET" industries?
- Do we need to open additional offices? Where?
- Should we "donate" a Video-conf. facility
to a Client who, for example, gave us Rs. 50 lakh business, last year?
📄 Scan_0015.jpg
(Handwritten Note - HS/3)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ CANDIDATE
HISTORY (Janam Kundli)
DECISIONS IT WILL HELP TAKE
- Which (Company's) interviews did he attend? Which
he did not? What are the type of jobs / companies that he
"prefers"?
- What functions / desig. levels / posting cities he
is interested in? (from interviews attended so far).
- For what kind of jobs / companies he should NOT
be approached? – Regrets.
- What are his MOBILITY limitations – in terms
of Wife's job / Children's edu. / family's health / parental obligations?
- Is he a job-jumper? How often?
- Does he accept job-offers, then fail to join?
Unreliable!
- What do "antecedent checks" reveal about
him?
- All the companies to Whom we ever sent his resume?
When? Against which position / vacancy / purchase order? What was the
outcome in each case?
- Did he / she ever get appointed thru us? If so,
where? When? as what? at what salary? Did we collect our fees?
📄 Scan_0016.jpg
(Handwritten Note - HS/4)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ CLIENT HISTORY
(Janam-kundli)
DECISIONS IT WILL HELP TAKE
- Is this client giving us regular / profitable
business thru repeat orders?
- Should we develop specific POLICY / PROCEDURE
in dealing with this client? What should that be?
📄 Scan_0017.jpg
(Handwritten Note - PY/1)
INFO. REQD. (OUTPUT STATEMENT)
$\triangleright$
"OUT-OF-POCKET" EXPENSE INVOICE SUMMARY
Client wise / Value wise / Date
wise
DECISIONS IT WILL HELP TAKE
- How much payment is to be collected? from whom?
When was it due?
- Whom to follow-up? How?
- Who should follow-up?
- When was invoice sent? For what amount?
- How much actual payment received against our
invoice? How much still remaining? Should we write-off balance?
- Is there a dispute?
📄 Scan_0018.jpg
(Handwritten Note - PY/2)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ PAYMENT CHEQUES
RECD. HISTORY (Overall / Client-wise / Date-wise)
DECISIONS IT WILL HELP TAKE
- Client-wise / Invoice-wise, cheques received. To
help send out statements to clients (confirmations)
- Assist in clarifying over phone, what payments have
been received against which invoice
&
What payments are still TO BE
RECD against each invoice
- What cheques (payments) are overdue
- "Promises Made" Column to enter the date,
client has promised to give cheque, so that Computer automatically reminds
accountant on that date.
📄 Scan_0019.jpg
(Handwritten Note - PY/3)
INFO. REQD. (OUTPUT STATEMENT)
$\triangleright$ INVOICE SUMMARY
TABULATION
- Client-wise
- Consultant-wise
- Overall
- Value-wise
- Date-wise
(Anytime / Month-end / Quarter
end / Year-end)
DECISIONS IT WILL HELP TAKE
- Who did, how much billing (absolute & as % of
total billing).
- Calculation of individual consultant's or
group-of-consultant's INCENTIVE-EARNING for the period.
- Compare "Outstanding" with
"Invoicing"
- Find out "bad debts" (Consultant-wise)
- Find "chronic" defaulters (blacklisting
action to be taken)
- Find which client delays payments & by how
much.
📄 Scan_0020.jpg
(Handwritten Note - PY/4)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ "FINAL
PAYMENT" Tabulation. (Value wise / Date wise)
DECISIONS IT WILL HELP TAKE
$\triangleright$ How much final
payment (after adjusting "advance" & "progress
payment") is due / overdue from whom & when.
$\triangleright$ How to
follow-up? Who shall follow-up?
Scan_0021.jpg (Handwritten
Note - PY/5)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ "PROGRESS
PAYMENT" Tabulation (Value wise / Date wise)
DECISIONS IT WILL HELP TAKE
- For each order, is any "progress-payment"
due? If yes:
- how much?
- when?
- has it become due or not?
- if yes, when?
- if not yet, then when?
- Which client / order to follow-up, when?
📄 Scan_0022.jpg
(Handwritten Note - PY/6)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ ADVANCE /
MINIMUM SEARCH FEE / RETAINER-FEE TABULATION (Value wise / Date wise)
DECISION IT WILL HELP TAKE
- For which orders / assignments we have still to
receive advance / how much / from whom / when (Follow-Up Action)
- For which, we have already received
- Whether we should wait till advance is received? or
start work?
- Whether we have, in a particular case, agreed to
work without advance?
📄 Scan_0023.jpg
(Handwritten Note - PY/7)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ CUSTOMER
OUTSTANDING PAYMENTS
(Ind / Func / Desig. level /
Client / Consultant wise in chronological order) – Value wise (Descending)
DECISIONS IT WILL HELP TAKE
$\triangleright$ Which client to
follow-up? In what way – oral / written? – How often?
$\triangleright$ Who should make
a personal visit, if required?
$\triangleright$ Should we
write-off the amount & close the chapter? Accept lesser amount?
$\triangleright$ Should we send a
legal notice? When?
$\triangleright$ Should we
"Black-list" the client & regret his future inquiries /
shopping-baskets? (Black-listing should "disable" sending of
proposals / terms to a client).
📄 Scan_0024.jpg
(Handwritten Note - OB/1)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ Overall, Order-backlog
analysis (month-end or at any point of time)
- Ind-wise
- Func-wise
- Desig. level wise
- chronological (Descend)
- Client wise
- Consultant wise
- Order Value wise (Descend)
- Salary-wise
DECISIONS IT WILL HELP TAKE
$\triangleright$ Trend-Analysis
(which sector / function etc) is booming. Website based online
"guidance" of jobseekers & recruiters.
$\triangleright$ Internal
"re-deployment" of resources. Addition of resources to ensure that
backlog does not become UNMANAGEABLE, nor should order-backlog drop to such
low-levels (overall & consultant wise & regional office-wise) that there
is an immediate likely hood of "wasted / underutilised" resources. We
must maintain a "healthy" backlog at all times by adjusting our
INPUTS / RESOURCES.
📄 Scan_0025.jpg
(Handwritten Note - OB/2)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ How many orders
are pending (at any given moment) from a particular client? – Arranged:
- Chronologically
- Order Value wise
- Designation-level wise
- Likely Completion-date wise
- Consultant-wise
$\triangleright$ DECISIONS IT
WILL HELP TAKE
$\triangleright$ Shall we
approach client for more orders?
$\triangleright$ Is one client
monopolizing / tying-up our resources?
$\triangleright$ Shall we
"re-allocate" these pending orders? Amongst whom? (Will require
informing client).
📄 Scan_0026.jpg
(Handwritten Note - OB/3)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ What is the load
/ backlog on a given consultant? How "booked" is he / she? How
long will it take him to clear the backlog? How many orders is he handling
simultaneously at this point of time? As per normal schedule, when are each of
these orders likely to be completed? Is he / she overloaded / underloaded?
DECISIONS IT WILL HELP TAKE
$\triangleright$ Rearrange
Order-priorities
$\triangleright$ Give additional
help to Consultant (in case of overload)
$\triangleright$ Give additional
help / load to Consultant (in case of underload)
$\triangleright$ Advise Client /
Clients of likely delay
📄 Scan_0027.jpg
(Handwritten Note - OP/1)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ Interest-Letters
- Sent out
- To be sent
} Inquiry-wise
DECISIONS IT WILL HELP TAKE
- Aggressive follow-up
- Automatic Reminder
📄 Scan_0028.jpg
(Handwritten Note - OP/2)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ Resumes
(Search-Results)
- already sent out
- Remaining to be sent
} order wise
$\triangleright$ One-line
Statements
DECISIONS IT WILL HELP TAKE
- Aggressive follow-up
- Automatic Reminder
📄 Scan_0029.jpg
(Handwritten Note - OP/3)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ Interview-call
letters
- Sent out
- remaining to be sent
- confirmations recd
- confirmations remaining
} order-wise
DECISIONS IT WILL HELP TAKE
- Aggressive follow-up
- Automatic Reminder
Scan_0031.jpg (Handwritten
Note - OP/5)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ At what stage is
a particular order?
$\triangleright$ Is it
progressing / proceeding as per pre-decided schedule? Are we ahead / behind
schedule?
- Committed by consultant (internally)
- Committed to Client (externally)
DECISION IT WILL HELP TAKE
$\triangleright$ Advise client of
delay / revised schedule
$\triangleright$ Change
priorities of Consultant
$\triangleright$ Transfer to
another consultant
$\triangleright$ Provide
additional "help" to consultant
📄 Scan_0032.jpg
(Handwritten Note - OP/6)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ "RESPONSE
RECEIVED" Tabulation.
This will cover
- Vacancies / positions at 3P
- Hot Jobs
|
Only put up on our website
by ourselves |
First advertised in print
& response invited thru our website |
|
for a client |
DECISIONS IT WILL HELP TAKE
$\triangleright$ Who / How many
applied
$\triangleright$ online
"rating" / short listing / segregating rating-wise / position wise /
city wise
$\triangleright$ Sending-out
interview-call letters
$\triangleright$ Printing one
line statements for sending to client
📄 Scan_0033.jpg
(Handwritten Note - OP/7)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ Purchase Order
History (Janam Kundli)
DECISIONS IT WILL HELP TAKE
- Did order get executed within the TIME-FRAME
promised to client? If not, what were the reasons for delay? Were these
reasons beyond OUR CONTROL?
- Where, if any, did we goof-up? What could we do to
prevent this in future?
- What did we over-estimate / under-estimate,
both time-wise / expense-wise? How can we use this "feedback" to
improve our estimates in future / make them more realistic?
- What should be our future strategy / policy / terms
in dealing with this client? What lessons did we learn from this order
which are
$\triangleright$ generally
applicable to all future orders from all / any clients
$\triangleright$ specifically
applicable for future inquiries from this client.
- Was "yield" commensurate with our
efforts?
📄 Scan_0034.jpg
(Handwritten Note - OP/8)
INFO. REQD (OUTPUT STATEMENT)
$\triangleright$ COMMUNICATION
HISTORY
|
ALLIES |
COMPANY |
PERSON |
|
Client |
Any other |
DECISIONS IT WILL HELP TAKE
- What is the best "mode" to communicate
with each of the above? (email / SMS / WAP / POTS / fax / letter /
voice-mail etc)
- What was our first / last "message /
communication" to each of these? What was their "last"
message to us? Where shall we pick-up the
"thread-of-communication"? Follow the coloured string.
- Ball is in whose "court"? What action /
response is expected of us / expected from them?
- History-folder should open simply by typing the
name of person and / or Company / Ally.
📄 Scan_0035.jpg (Table)
OUTPUT STATEMENTS
ORDER EXECUTION SYSTEM
|
category → statement ↓ |
Marketing – Sales |
Order Processing |
Order Backlog |
Payments |
History |
|
As Proposed by Applitech |
(1.5) Consultant-wise client
List (2) Proposal (4) Sales Order (6) Project Plan |
(2.3) Advt. Response (media)
(2.2) Advt. Response (client) (2.6) Project Plan (2.5) Expected Date of
Joining (18) Order Execution Details (17) Resume Sent History
(Candidate-wise) (16) Resume Sent History (client wise) (19) Interview
Details (20) Interview Schedule (11) Prospective Candidate (12) Follow-up
with 3P (13) Follow-up with client (14) Interview schedule (15) One-line
Statement |
(1.2) Pending OEN (client /
consultant / date wise) |
(1.9) Compensation Details
(1.7) Invoice |
(21) Client Information (24)
Janam Kundli of client (25) Janam Kundli of candidate (1.8) Order History
(client) (9) Project Variance |
|
Additional (Including
duplicate) proposed by 3P |
MS/1 – What shopping baskets
were received? MS/2 – How many / which SB got converted into an order? MS/3 –
How many / which SB has been answered? |
OP/2 – Interest Letters OP/3 –
Resumes Sent OP/4 – Interview Call Letters OP/5 – Order stages 4 OP/2 – Order
Monitoring OP/6 – Response Recd. OP/7 – Purchase Order History OP/8 –
Communication History |
OB/1 – Order Backlog Analysis
OB/2 – Orders Pending Analysis OB/3 – Load on a Consultant |
PY/1 – OOP Invoices PY/2 –
Cheques Received PY/3 – Invoices summary PY/4 – Final Payment Tabulation PY/5
– Progress Payment Tabulation PY/6 – Advance Tabulation PY/7 – Customer
Outstanding |
HS/1 – Executives Appointed so
far HS/2 – Order Execution Analysis HS/3 – Candidate History HS/4 – Client
History |
📄 Scan_0036.jpg
(Handwritten Letter - 1/6)
To: Tapan (Applitech-A'bad)
$\qquad$ Oct. 9, 2000
cc: Ravi (Applitech-A'bad),
Sudhakar (-Mumbai), Mr. Nagle, Mr. Cyril Ovely (Mumbai)
Order Execution System (OES)
I refer to our several meetings
last week, including last one on Friday (Oct. 6) when Mr. Nagle was also
present.
In this meeting you had submitted
a list of 25 output statements (albeit, not a comprehensive list). Then Mr.
Nagle suggested that, independent of your list, I should also try to prepare a
list of OUTPUT STATEMENTS which we need from OES.
Enclosed, please find details of
such statements (once again, may not be comprehensive).
📄 Scan_0037.jpg
(Handwritten Note - 2/6)
On a separate chart, I have also
tried to tabulate your statements & my statements, under some broad
categories. This chart will bring-out the duplications and those which,
$\triangleright$ occured to you
but not to me
$\triangleright$ occured to me
but not to you.
Taken together, hopefully, these
will add-up to our requirement.
Since many of these are in the
manner of "SUMMARIES", it will mean there will be quite a few
"INDIVIDUALS" (statements), from which, you will construct these
"summaries".
I have not attempted to prepare a
list of the "INDIVIDUAL STATEMENTS".
Further, I have not attempted to
actually "design" (the layout / columns / rows etc) these output
statements. You will, no doubt, do a better job!
📄 Scan_0038.jpg
(Handwritten Note - 3/6)
Even, what should be the precise
"content" (fields) of these statements, is something, you should
decide.
As far as we are concerned, we
need to take some
$\triangleright$ tactical /
operating decisions
$\triangleright$ strategic /
policy decisions.
So, what I have done is to list
the types / kinds of "decisions", that we have to take day-in &
day-out. It is dynamic "course correction" all the time.
Now,
If "relevant / up-to-date /
historical" info. is readily available / accessible at finger-tip, then
the decisions taken tend to be "SMARTER"
but
If relevant info. is absent /
incomplete, the decisions tend to be POORER.
📄 Scan_0039.jpg
(Handwritten Note - 4/6)
So,
your job is to figure-out,
"what info (fields) will be
needed by 3P to be able to take SMART DECISIONS?"
Then, provide that info. in each
statement.
Simple !
When you show us the exact design
of the OUTPUT STATEMENTS, our consultants, would be able to say whether
each statement contains all the info they need (at the finger-tip / one glance)
to take the decisions.
As far as using CRYSTAL REPORT
/ ORACLE DISCOVERER is concerned, both, Mr. Nagle & Mr. Cyril Ovely
have serious reservations about the technical skills of our consultants to be
able to use these. They feel,
📄 Scan_0040.jpg
(Handwritten Note - 5/6)
These "tools" are
really meant for "techies".
They feel,
$\triangleright$ Wherever
possible (to the extent possible), we should "freeze" the design of
each output statement in advance
$\triangleright$ Only in case,
where absolutely necessary to construct a "customised" statement, we
should export the data to EXCEL (as was suggested by Ravi in our first
meeting).
So, let us forget about Crystal
Report / Oracle discoverer.
As far as this note
(incorporating a set of desired OUTPUT STATEMENTS) is concerned, it should not
be looked-upon in isolation but it should be read in conjunction with my
following earlier notes:
This final set of notes
consolidates the requirement for the Order Execution System (OES), emphasizing
that the focus should be on creating a set of pre-designed, user-friendly
"frozen" output statements to enable consultants to make smarter tactical
and strategic decisions, rather than relying on complex reporting tools like
Crystal Reports or Oracle Discoverer.
Scan_0041.jpg
6/6
$\triangleright$ Note dt. Aug.
24, 2000 (our original order)
$\triangleright$ Note dt. Sept.
14, 2000 (our revised order)
$\triangleright$ your revised
offer dt. 12/9/2000 (and the discussions on features listed on p. 13)
$\triangleright$ My email of
Sept. 20 to Ravi
$\triangleright$ My note given to
you on Oct. 5
I now await your detailed report.
With regards
[Signature]
P.S. Also find enclosed, my
remarks on various pages of
"REQUIREMENT
CATALOGUE"
which was handed over to Namit on
Oct. 5.
cc: Namit
cc: CMT
cc: AMB
cc: Mitchelle
} Only, your own intense interest
/ involvement / interaction with APPLITECH team, will lead to a satisfying
solution.
📄 Scan_0042.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
2. System Diagrams and Tables
2.1. Document Flow Table
|
Source |
Communication Mode |
Dataflow/Document |
Recipient |
|
Client |
Any |
Inquiry |
Consultant |
|
Consultant |
Hard Copy |
Proposal |
Client |
|
Client |
Hard Copy |
Signed Proposal |
Consultant |
|
Consultant |
Hard Copy |
Sales Order |
Client |
|
Consultant |
Hard Copy |
Project Plan |
Management |
|
Advertising Agency |
Hard Copy |
Advertising Draft |
Consultant |
|
Consultant |
Hard Copy |
Advertising Details |
Client |
|
Client |
Hard Copy |
Approved Ad. Details |
Consultant |
|
Candidate |
Any |
Candidate Interest |
Consultant |
|
Consultant |
Any |
Preliminary Screening |
Client |
|
Client |
Any |
Interview Schedule |
Consultant |
|
Consultant |
Any |
Interview (Details) Letter |
Candidate |
|
Candidate |
Any |
Confirm Interview |
Consultant |
|
Client |
Any |
Interview Feedback |
Consultant |
|
Candidate |
Any |
Interview Feedback |
Consultant |
|
Client |
Any |
Compensation Details |
Consultant |
|
Consultant |
Any |
Invoice |
Client |
Any includes E-mail, Smail-mail,
Fax and Phone.
Hard copy is Fax, Smail-mail
[Handwritten Note/Diagram below
table]
Prelim. Interview Schedule
$\rightarrow$ This is prepared by a consultant independently - since client is
not participating in these interviews. Mostly these interviews are conducted at
3P's premises, by 3P's own consultants/confidential experts, who fill-in
"Interview Evaluation" sheets.
Final Interview Schedule
$\rightarrow$ This is normally given by client (over the phone) to our
consultant. Quite often this is based on one-line statement and/or interview
evaluation sheets (of prelim. Interviews held by 3P) prepared/sent by 3P
consultant to the client.
Confidential October 2000 Page 3
of 42
📄 Scan_0043.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
2.2. Document Flow Diagram
[Diagram showing the flow between
Client, Candidate, and Consultant via the central "Order Execution"
process box]
Flow Details:
- Client to Order Execution: Inquiry, Signed
proposal, Approved screening Details, Compensation (details) format
- Consultant to Order Execution: Inquiry,
Signed proposal, Approved screening Details, Interview schedule, Confirm
interview, Interview feedback, compensation details, follow-up.
- Order Execution to Client: Proposal, Sales
order, Approved screening Details, Preliminary screening results, Invoice
- Order Execution to Consultant: Proposal,
Sales order, Project plan, Advertising Details, Preliminary screening,
Interview details, Invoice, prospective candidate
- Order Execution to Candidate: Interview
details
Handwritten Notes:
- [Added to flow lines] $\rightarrow$ Interview
Evaluation Sheets
- [Box near Candidate] $\rightarrow$ Candidate
Interest, Confirm interview, Interview feedback, follow up, Confirmation
that he/she has $\triangleright$ resigned from current job
$\triangleright$ joined new employer.
- [Handwritten Box] $\rightarrow$ We also like to
collect from the candidate, a copy of his/her Appointment letter (to
compare with "Compensation format" made available to us by our
client)
Confidential October 2000 Page 4
of 42
📄 Scan_0044.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
2.3. Context Level Diagram –
Proposed System
[Context Level Diagram showing
Input and Output for the central "Order Execution System"]
- Input: Inquiry, Signed Proposal, Advertising
Draft, Approved Advertising Details, Candidate Interest, Interview
schedule, Confirm interview, Interview feedback, compensation details,
follow-up, Prospective candidate
- Output: Proposal, Sales order, Project Plan,
Advertising Details
Confidential October 2000 Page 5
of 42
📄 Scan_0045.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
3. Modules
3.1. Order Execution
Following is the list of
Requirements:
3.1.1. List of Masters
|
Requirement ID 1 |
|
|
Requirement Name: Industry
Master |
Available as dropdown on
website. - Separate for IT-Professionals |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the name of various kind of industries. |
|
|
Benefits: Details of the
Industry are maintained which can be used for easy data entry. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of Industry names, following information will be captured. |
|
|
1. Industry Code |
|
|
2. Industry name |
Confidential October 2000 Page 6
of 42
📄 Scan_0046.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 2 |
|
|
Requirement Name: Product or
Service Master |
{ Such a MASTER, since,
literally there are millions of products & services. As a result
on our website, we have kept this as a "free-text" search.
It is impossible to create/maintain |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the name of various kind of products and services. |
|
|
Benefits: A list of the
products and services is maintained which can be used for easy data entry. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of Product or services, following information will be
captured. |
|
|
1. Product Code - forget
coding! |
|
|
2. Product or service name
$\rightarrow$ Same "product-name" will be spelled slightly
differently by different people! |
Confidential October 2000 Page 7
of 42
📄 Scan_0047.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 3 |
|
|
Requirement Name: Parent
Group Details |
|
|
Source: As and when
required. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the details of the parent group company. |
|
|
Benefits: Details of the
parent company are maintained which can be used for information retrieval at
a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of existing client or prospect, following information will
be captured. |
|
|
1. Client code No code, only
MASTER for Ind. Names. |
|
|
2. Client name |
|
|
3. Contact person |
|
|
4. Designation of contact
person |
|
|
5. Other contact person |
|
|
6. Designation of contact
person |
|
|
7. Contact telephone number 1 |
|
|
8. Contact telephone number 2 |
|
|
9. Contact telephone number 3 |
|
|
10. Correspondence address |
|
|
11. Registered address |
|
|
12. Fax number |
|
|
13. Website |
|
|
14. Email address 1 |
|
|
15. Email address 2 |
|
|
16. Industry code (D) |
|
|
17. Industry name (D) |
[Handwritten Note] $\rightarrow$
Pl. see my notes (cp-1/2/3) dt. Oct. 5, on Corporate Profile Screens (Janam
kundli).
Confidential October 2000 Page 8
of 42
📄 Scan_0048.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 4 |
|
|
Requirement Name: Company
Details Master |
|
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the name of various kind of industries. |
|
|
Benefits: Details of the
company are required for storing and retrieval of the vital business
information regarding any client of 3P. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the companies the following information will be captured. |
|
|
1. Client code |
|
|
2. Client name |
|
|
3. Contact person |
|
|
4. Designation of contact
person |
|
|
5. Other contact person |
|
|
6. Designation of contact
person |
|
|
7. Contact telephone number 1 |
|
|
8. Contact telephone number 2 |
|
|
9. Contact telephone number 3 |
|
|
10. Correspondence address |
|
|
11. Registered address |
|
|
12. Fax number |
|
|
13. Website |
|
|
14. Email address 1 |
|
|
15. Email address 2 |
|
|
16. Industry code |
|
|
17. Industry name (D) |
|
|
18. Parent group code |
[Handwritten Note] $\rightarrow$
See Corpo. Profile Notes CP-1/2/3. (Oct. 5).
Confidential October 2000 Page 9
of 42
📄 Scan_0049.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 5 |
|
|
Requirement Name: Currency
Master |
|
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of currencies that may be used
for business transactions with the clients. |
|
|
Benefits: |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of referring Doctors, following information will be
captured. |
|
|
1. Currency Code |
} only two - Rs. & $ |
|
2. Currency |
Confidential October 2000 Page 10
of 42
📄 Scan_0050.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 6 |
|
|
Requirement Name:
Designation Master |
$\rightarrow$ We have a "Desig.
Level Master" as a dropdown on our website. |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the name of various designations. |
|
|
Benefits: This list can
be enlarged/expanded from time to time. |
|
|
Comments & Suggestions:
NA |
As far as "ACTUAL
DESIGNATIONS" is concerned, we have a "static" page giving
some "Examples" only in case of IT-Professionals. Of course. As
far as as "Non-IT (other) Professionals" are concerned, we
have neither a "drop-down" nor a static page, as far as as
"actual designations" is concerned - although, if required, I have
prepared one, which runs into, maybe 200/300. |
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the companies the following information will be captured. |
|
|
1. Designation code [X] |
Once again the problems that we
run into are: |
|
2. Designation name |
$\triangleright$ A dropdown of
200/300, takes too long to "download" & too long to "scroll",
once downloaded. |
|
$\triangleright$ When people
make "free text" entries, they spell, same designation differently
! |
Confidential October 2000 Page 11
of 42
Scan_0051.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 7 |
|
|
Requirement Name: Function
Master |
|
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the name of various functions. |
|
|
Benefits: This list can
be enlarged/expanded from time to time. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the functions, the following information will be
captured. |
|
|
1. Function Code |
|
|
2. Function name |
📄 Scan_0052.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 8 |
|
|
Requirement Name: Project
Activity Master |
$\rightarrow$ I have already
given a list of activities (7.1-7.10) in the "Project Plan"
sheet (P-2) |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of project activities. |
|
|
Benefits: A list of the
project activities is maintained which can be used for easy data entry. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the project activities, the following information will be
captured. |
|
|
1. Project activity code |
|
|
2. Project activity name |
📄 Scan_0053.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 9 |
|
|
Requirement Name: Follow up
Master |
|
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of follow up activities. |
|
|
Benefits: A list of the
follow up activities is maintained which can be used for easy data entry. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the follow up activities, the following information will
be captured. |
|
|
1. Follow up activity code |
|
|
2. Follow up activity |
📄 Scan_0054.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 10 |
|
|
Requirement Name: Consultant
Master |
$\rightarrow$ Pl. incorporate "Industry-wise"
allocation & "Region-wise" allocation |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the details of the consultant working with 3P. |
|
|
Benefits: This
information can be used for proper tracking and monitoring of the consultant. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the consultant, the following information will be
captured. |
|
|
1. Consultant code |
|
|
2. Consultant name |
|
|
3. Industry code (can be
multiple) $\rightarrow$ $\triangleright$ code $\triangleright$ name |
|
|
4. Region code (can be
multiple) $\rightarrow$ $\triangleright$ code $\triangleright$ name |
📄 Scan_0055.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 11 |
|
|
Requirement Name: Candidate
Master |
$\rightarrow$ This is not
needed. This master is already available in the ORACLE 8 database of "candidates".
You will "pick-up" the required info. from there. |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the details of all the candidates who are
registered with 3P. |
|
|
Benefits: Complete
details of the candidate can be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the candidates, the following information will be
captured. |
|
|
1. Candidate code |
|
|
2. Candidate name |
|
|
3. Candidate address |
|
|
4. Candidate telephone number |
📄 Scan_0056.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 12 |
|
|
Requirement Name: Terms and
Conditions |
$\rightarrow$ This is not a MASTER.
This is part of the "Proposal" (p-2) |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of terms and conditions that may
be applicable to a particular client. |
|
|
Benefits: Terms and
conditions will be used for easy data entry while preparing the proposal. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the Terms and conditions, the following information will
be captured. |
|
|
1. Terms and conditions code |
|
|
2. Terms and conditions |
📄 Scan_0057.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 13 |
|
|
Requirement Name: Media
Master |
|
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of media that may be used for
advertising. |
|
|
Benefits: |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the media, the following information will be captured. |
|
|
1. Media code |
|
|
2. Media name |
📄 Scan_0058.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 14 |
|
|
Requirement Name:
Communication Type Master |
|
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of communication modes. |
|
|
Benefits: |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the communication type, the following information will be
captured. |
|
|
1. Communication type code |
|
|
2. Communication type name |
📄 Scan_0059.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 15 |
|
|
Requirement Name: Language
Master |
|
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of languages. |
|
|
Benefits: |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the languages, the following information will be
captured. |
|
|
1. Language code |
|
|
2. Language name |
📄 Scan_0060.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 16 |
|
|
Requirement Name: Billing
Master |
$\rightarrow$ This is not
needed. This is part of the "Proposal" (p-2) |
|
Source: As and when
required. |
|
|
User Responsible:
Operator |
|
|
Functional Requirements:
The system should maintain the various kind of billing modes that may be used
for business transactions with the clients. |
|
|
Benefits: |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the billing modes, the following information will be
captured. |
|
|
1. Billing code |
|
|
2. Billing name |
Scan_0061.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 17 |
|
|
Requirement Name: Resume
Sent History (Client wise) |
|
|
Source: Resume sent to
client at the time of preliminary screening. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the history of the resume sent to the client. |
|
|
Benefits: History will
be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements:
Resume Sent History (Candidate wise) |
|
|
Solution: In order to
maintain details of the resume sent to the client, the following information
will be captured. |
|
|
1. Client name |
|
|
2. OEN |
|
|
3. Candidate name (can be
multiple) |
|
|
4. Date of resume sent |
|
|
5. Mode of communication |
Confidential October 2000 Page 12
of 42
📄 Scan_0062.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 18 |
|
|
Requirement Name: Order
Execution Details |
|
|
Source: Data captured
during the execution of the order. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the details captured during the execution of the
order. |
|
|
Benefits: Order
Execution Details will be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the order execution, the following information will be
captured. |
|
|
1. OEN |
|
|
2. Client name (D) |
|
|
3. Date of inquiry |
|
|
4. Date of proposal |
|
|
5. Date of order receipt |
|
|
6. Date of adv. placed |
|
|
7. Date of candidate
listing/head hunting completed |
|
|
8. Date of preliminary
screening |
|
|
9. Date of resume sent to
client |
|
|
10. Date of interview (Final) |
|
|
11. Date of selection |
|
|
12. Date of joining |
|
|
13. Date of resignation |
Confidential October 2000 Page 13
of 42
📄 Scan_0063.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 19 |
|
|
Requirement Name: Interview
Details |
|
|
Source: Feedback from
client and candidate. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the feedback regarding the interview from the
client and the candidate. |
|
|
Benefits: Interview
Details will be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the interview, the following information will be
captured. |
|
|
1. OEN |
|
|
2. Candidate name |
|
|
3. Interview type (Preliminary,
Final) |
|
|
4. Interview date |
|
|
5. Interview venue |
|
|
6. Interview time |
|
|
7. Feedback (client, candidate) |
|
|
8. Remarks |
Confidential October 2000 Page 14
of 42
📄 Scan_0064.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 20 |
|
|
Requirement Name: Interview
Schedule |
|
|
Source: Interview
schedule given by client and candidate. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the details of the interview schedule. |
|
|
Benefits: Interview
schedule will be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the interview schedule, the following information will be
captured. |
|
|
1. OEN |
|
|
2. Candidate name |
|
|
3. Interview date |
|
|
4. Interview venue |
|
|
5. Interview time |
Confidential October 2000 Page 15
of 42
📄 Scan_0065.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 21 |
|
|
Requirement Name: Client
Information |
|
|
Source: Inquiry,
proposal, sales order. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the details of the client. |
|
|
Benefits: Client
Information will be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the client, the following information will be captured. |
|
|
1. Client name |
|
|
2. Contact person |
|
|
3. Designation of contact
person |
|
|
4. Contact telephone number 1 |
|
|
5. Contact telephone number 2 |
|
|
6. Contact telephone number 3 |
|
|
7. Correspondence address |
|
|
8. Registered address |
|
|
9. Fax number |
|
|
10. Website |
|
|
11. Email address 1 |
|
|
12. Email address 2 |
|
|
13. Industry name |
|
|
14. Parent group name |
Confidential October 2000 Page 16
of 42
📄 Scan_0066.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 22 |
|
|
Requirement Name: Resume
Sent History (Candidate wise) |
|
|
Source: Resume sent to
client at the time of preliminary screening. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the history of the resume sent to the client. |
|
|
Benefits: History will
be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements:
Resume Sent History (Client wise) |
|
|
Solution: In order to
maintain details of the resume sent to the client, the following information
will be captured. |
|
|
1. Candidate name |
|
|
2. OEN |
|
|
3. Client name (can be
multiple) |
|
|
4. Date of resume sent |
|
|
5. Mode of communication |
Confidential October 2000 Page 17
of 42
📄 Scan_0067.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 23 |
|
|
Requirement Name: Order
History (Client wise) |
|
|
Source: Data captured
during the execution of the order. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the history of the order for a particular client. |
|
|
Benefits: Order History
will be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the order history, the following information will be
captured. |
|
|
1. Client name |
|
|
2. OEN (can be multiple) |
|
|
3. Order date |
|
|
4. Order value |
|
|
5. Order status |
Confidential October 2000 Page 18
of 42
📄 Scan_0068.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 24 |
|
|
Requirement Name: Janam
Kundli of Client |
|
|
Source: All information
pertaining to a client. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the complete information of the client. |
|
|
Benefits: Janam Kundli
will be used for complete reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain complete details of the client, the following information will be
captured. |
|
|
1. Client name |
|
|
2. Client code |
|
|
3. Date of first contact |
|
|
4. Total orders |
|
|
5. Orders pending |
|
|
6. Orders completed |
|
|
7. Max order value |
|
|
8. Min order value |
|
|
9. Avg order value |
|
|
10. Avg order completion time |
|
|
11. Avg payment cycle |
|
|
12. Amount outstanding |
Confidential October 2000 Page 19
of 42
📄 Scan_0069.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 25 |
|
|
Requirement Name: Janam
Kundli of Candidate |
|
|
Source: All information
pertaining to a candidate. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the complete information of the candidate. |
|
|
Benefits: Janam Kundli
will be used for complete reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain complete details of the candidate, the following information will be
captured. |
|
|
1. Candidate name |
|
|
2. Candidate code |
|
|
3. Date of registration |
|
|
4. Total interviews attended |
|
|
5. Total offers received |
|
|
6. Total offers accepted |
|
|
7. Total offers rejected |
|
|
8. Total appointments |
|
|
9. Last appointment date |
|
|
10. Current status |
|
|
11. Current company |
|
|
12. Current compensation |
Confidential October 2000 Page 20
of 42
📄 Scan_0070.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 26 |
|
|
Requirement Name: Project
Variance |
|
|
Source: Project Plan. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should maintain the difference between the planned and the actual
dates for the project activities. |
|
|
Benefits: Project
Variance will be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the project variance, the following information will be
captured. |
|
|
1. OEN |
|
|
2. Activity name (can be
multiple) |
|
|
3. Planned date |
|
|
4. Actual date |
|
|
5. Variance (Planned - Actual) |
Confidential October 2000 Page 21
of 42
Scan_0071.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 27 |
|
|
Requirement Name: Sales
Order |
|
|
Source: Signed proposal. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should generate a sales order based on the signed proposal. |
|
|
Benefits: Sales order
will be used for execution of the order. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents:
Proposal |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the sales order, the following information will be
captured. |
|
|
1. Order execution no. (auto) |
|
|
2. Proposal no. |
|
|
3. Inquiry no. (D) |
|
|
4. Mode of search (D) |
|
|
5. Client details (D) |
|
|
6. Consultant name |
|
|
7. Schedule dates for: |
|
|
7.1. Identification of
prospective candidate |
|
|
7.2. Completion of preliminary
interview |
|
|
7.3. Sending of resumes of
candidate to client |
|
|
8. Note |
Confidential October 2000 Page 22
of 42
📄 Scan_0072.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 28 |
|
|
Requirement Name: Inquiry |
|
|
Source: Prospect or
client. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the inquiry received from a prospect
or client. |
|
|
Benefits: Inquiry will
be used as the base for the proposal. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements:
Proposal |
|
|
Solution: Following
details as captured from an inquiry from a prospect or client. |
|
|
1. Inquiry no. (auto) |
|
|
2. Type of inquiry (e-mail,
fax, website, tele, personal meetings, other) |
|
|
3. Date of inquiry (not
necessary the current (system) date it can be back date also) |
|
|
4. Consultant handling inquiry |
|
|
5. Client details |
|
|
5.1. Name of person |
|
|
5.2. Company |
|
|
5.3. Tele no. |
|
|
6. Mode of search (multiple
modes) (advt., data search, head hunting) |
|
|
7. Vacancy details (multiple
vacancy) |
|
|
7.1. Name of vacancy |
|
|
7.2. No. of vacancy |
|
|
8. Expected date of sending
proposal |
|
|
9. Remarks |
Confidential October 2000 Page 23
of 42
📄 Scan_0073.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 29 |
|
|
Requirement Name: Proposal |
|
|
Source: Inquiry. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should generate the proposal based on the inquiry. |
|
|
Benefits: Proposal will
be used for execution of the order. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents:
Inquiry |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the proposal, the following information will be captured. |
|
|
1. Proposal no. (auto) |
|
|
2. Inquiry no. |
|
|
3. Client name |
|
|
4. Type of proposal (flat rate,
% rate, Turnkey) |
|
|
5. Covering letter details |
|
|
5.1. Text as per format |
|
|
6. Terms and conditions |
|
|
6.1. Professional fee details |
|
|
6.1.1. Figure (numeric value
for % or value in currency) |
|
|
6.1.2. Unit (could be % or
value) |
|
|
6.1.3. Currency |
|
|
6.2. Minimum fee |
|
|
6.3. Valuation of perks |
|
|
6.4. Paying cycle (there can be
upto five phases) |
|
|
6.4.1. Phase |
|
|
6.4.2. Figure (numeric value
for % or value in currency) |
|
|
6.4.3. Unit (could be % or
value) |
|
|
6.4.4. Currency |
|
|
6.5. Out of pocket expense |
|
|
6.5.1. Cost head |
|
|
6.5.2. Cost |
|
|
6.6. Copy format form samples |
Confidential October 2000 Page 24
of 42
📄 Scan_0074.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 30 |
|
|
Requirement Name: Project
Plan |
|
|
Source: Sales Order. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the project plan. |
|
|
Benefits: Project Plan
will be used for monitoring and control of the order execution. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Sales
Order |
|
|
Related Requirements:
Project Variance |
|
|
Solution: In order to
maintain details of the project plan, the following information will be
captured. |
|
|
1. OEN |
|
|
2. Proposal no. (D) |
|
|
3. Inquiry no. (D) |
|
|
4. Mode of search (D) |
|
|
5. Client details |
|
|
5.1. Name contact no. |
|
|
5.2. e-mail |
|
|
5.3. contact person |
|
|
5.4. address |
|
|
6. Consultant name |
|
|
7. Due date and actual date for
activities (actual date will be captured automatically) |
|
|
7.1. Inquiry |
|
|
7.2. Proposal |
|
|
7.3. Sales order |
|
|
7.4. Adv. Details |
|
|
7.5. Candidate listing and head
hunting |
|
|
7.6. Preliminary screening |
|
|
7.7. Resume to client |
|
|
7.8. Interview |
|
|
7.9. Result sent to candidate |
|
|
7.10. End date |
Confidential October 2000 Page 25
of 42
📄 Scan_0075.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 31 |
|
|
Requirement Name:
Advertising Details |
|
|
Source: Draft given by
advertising agency. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the advertising. |
|
|
Benefits: Advertising
Details will be used for placing the advertisement and tracking the cost. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the advertising, the following information will be
captured. |
|
|
1. Advertising details no. |
|
|
2. Date |
|
|
3. OEN (can be multiple) |
|
|
4. Advertisement details (can
be multiple) |
|
|
4.1. Media |
|
|
4.2. Location |
|
|
4.3. Dates |
|
|
4.4. Cost |
|
|
4.5. Approved by client (Y/N) |
|
|
5. Date of approval |
|
|
6. Note |
|
|
7. Response to add |
Confidential October 2000 Page 26
of 42
📄 Scan_0076.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 32 |
|
|
Requirement Name: Candidate
Listing |
|
|
Source: Response to
advertisement, data search, head hunting. |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the candidate listing. |
|
|
Benefits: Candidate
listing will be used for shortlisting and preliminary screening. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements:
Preliminary screening |
|
|
Solution: In order to
maintain details of the candidate listing, the following information will be
captured. |
|
|
1. Date (Auto) |
|
|
2. OEN |
|
|
3. Candidate details |
|
|
3.1. PEN |
|
|
3.2. Name of candidate |
|
|
3.3. Organization |
|
|
3.4. Designation |
|
|
3.5. Educational Qualification |
|
|
3.6. Past company details |
|
|
3.7. Age |
|
|
3.8. City |
|
|
3.9. Phone (R) |
|
|
3.10. Phone (O) |
|
|
3.11. Mobile no. |
|
|
3.12. Contact agency |
|
|
3.13. Status |
|
|
3.14. Comment |
|
|
3.15. Mode of communication |
|
|
3.16. Candidate response (Y/N) |
Confidential October 2000 Page 27
of 42
📄 Scan_0077.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 33 |
|
|
Requirement Name:
Preliminary Screening |
|
|
Source: Preliminary
interview (with 3P consultant) |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the preliminary screening. |
|
|
Benefits: Preliminary
screening will be used for final shortlisting. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents:
Candidate listing |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the preliminary screening, the following information will
be captured. |
|
|
1. Date |
|
|
2. OEN |
|
|
3. Client name |
|
|
4. Candidate assessment |
|
|
4.1. PEN |
|
|
4.2. Candidate name (D) |
|
|
4.3. Panel (multiple names) |
|
|
4.4. Assessment sheet |
|
|
4.4.1. Attribute name |
|
|
4.4.2. Score |
|
|
4.5. Overall assessment (out
standing, good, acceptable, not suitable) |
|
|
4.6. Family background |
|
|
4.7. Current company details |
|
|
4.7.1. Brief info |
|
|
4.7.2. Size |
|
|
4.7.3. Turnover |
|
|
4.7.4. No. of employees |
Confidential October 2000 Page 28
of 42
📄 Scan_0078.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 33
(Continued) |
|
|
Solution: In order to
maintain details of the preliminary screening, the following information will
be captured. |
|
|
4.8. Strength |
|
|
4.9. Weakness |
|
|
4.10. Product exposure |
|
|
4.11. Industry exposure |
|
|
4.12. Contribution to
organization |
|
|
4.13. Salary breakup |
|
|
4.14. Current compensation |
|
|
4.15. Expected compensation |
|
|
4.16. Availability |
|
|
4.17. Housing (own, rent,
company) |
|
|
4.18. Reason for change |
|
|
4.19. Other info |
|
|
4.20. Comments |
|
|
4.21. Short listed by 3P (Y/N) |
|
|
4.22. Short listed by client
(Y/N) |
Confidential October 2000 Page 29
of 42
📄 Scan_0079.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 34 |
|
|
Requirement Name: Follow up
with Client |
|
|
Source: Consultant |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the follow up with the client. |
|
|
Benefits: Follow up will
be used for proper tracking and execution of the order. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the follow up with the client, the following information
will be captured. |
|
|
1. OEN |
|
|
2. Activity |
|
|
3. Date of follow up |
|
|
4. Outcome |
|
|
5. Next follow up date if any |
|
|
6. Mode of communication |
Confidential October 2000 Page 30
of 42
📄 Scan_0080.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 35 |
|
|
Requirement Name: Follow up
with Candidate |
|
|
Source: Consultant |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the follow up with the candidate. |
|
|
Benefits: Follow up will
be used for proper tracking and execution of the order. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the follow up with the candidate, the following
information will be captured. |
|
|
1. OEN |
|
|
2. PEN |
|
|
3. Activity |
|
|
4. Date of follow up |
|
|
5. Outcome |
|
|
6. Next follow up date if any |
|
|
7. Mode of communication |
Scan_0081.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 36 |
|
|
Requirement Name:
Out-of-Pocket Expense |
|
|
Source: Consultant |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the out-of-pocket expenses incurred
during the execution of the order. |
|
|
Benefits: Out-of-Pocket
Expense will be used for reimbursement and billing to the client. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the out-of-pocket expense, the following information will
be captured. |
|
|
1. OEN |
|
|
2. Date |
|
|
3. Consultant code |
|
|
4. Expense type |
|
|
5. Amount |
|
|
6. Mode of payment (cash,
cheque, credit card) |
|
|
7. Status (submitted to client,
approved, paid by client, paid by 3P) |
|
|
8. Remarks |
Confidential October 2000 Page 32
of 42
📄 Scan_0082.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 37 |
|
|
Requirement Name: Invoice |
$\rightarrow$ Advance /
Progress / Final |
|
Source: Proposal,
Out-of-Pocket Expense |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should generate the invoice based on the proposal and
out-of-pocket expense. |
|
|
Benefits: Invoice will
be used for billing to the client and revenue recognition. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents:
Proposal, Out-of-Pocket Expense |
|
|
Related Requirements:
Payments |
|
|
Solution: In order to
maintain details of the invoice, the following information will be captured. |
|
|
1. Invoice no. (auto) |
|
|
2. OEN |
|
|
3. Invoice type |
|
|
4. Client name |
|
|
5. Date of invoice |
|
|
6. Service tax |
|
|
7. Surcharge |
|
|
8. Cess |
|
|
9. Cost |
|
|
10. Total amount |
|
|
11. Amount in words |
|
|
12. Mode of payment |
|
|
13. Terms and conditions (D) |
Confidential October 2000 Page 33
of 42
📄 Scan_0083.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 38 |
|
|
Requirement Name: Payment |
$\rightarrow$ Date and Amount
of the payment received against the Invoice, Cheque No., Date, etc. |
|
Source: Cheques/Payments
received from client. |
|
|
User Responsible:
Accounts |
|
|
Functional Requirements:
The system should capture the details of the payments received against the
invoice. |
|
|
Benefits: Payments will
be used for tracking of outstanding payments. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents:
Invoice |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the payment, the following information will be captured. |
|
|
1. Payment no. (auto) |
|
|
2. Invoice no. |
|
|
3. OEN (D) |
|
|
4. Date of payment |
|
|
5. Amount |
|
|
6. Cheque no. |
|
|
7. Cheque date |
|
|
8. Bank name |
|
|
9. Payment status (Deposited,
Cleared, Bounced) |
|
|
10. Remarks |
Confidential October 2000 Page 34
of 42
📄 Scan_0084.jpg
Applitech Solution Limited
Requirement Catalogue Ver 1.0 3P Consultants
|
Requirement ID 39 |
|
|
Requirement Name:
Communication |
$\rightarrow$ This is not
required. Already covered in the "Communication-History"
(OP/8) |
|
Source: Consultant |
|
|
User Responsible:
Consultant |
|
|
Functional Requirements:
The system should capture the details of the communication between client,
candidate, and 3P. |
|
|
Benefits: Communication
will be used for reference at a later stage. |
|
|
Comments & Suggestions:
NA |
|
|
Related Documents: Nil |
|
|
Related Requirements: |
|
|
Solution: In order to
maintain details of the communication, the following information will be
captured. |
|
|
1. OEN (can be multiple) |
|
|
2. Communication date |
|
|
3. From (client/candidate/3P) |
|
|
4. To (client/candidate/3P) |
|
|
5. Communication type (email,
letter, fax, phone, SMS, personal meeting) |
|
|
6. Communication details |
|
|
7. Remarks |
No comments:
Post a Comment