Escolar Documentos
Profissional Documentos
Cultura Documentos
Table of Contents
FOREWORD..................................................................................................................... 3
INTRODUCTION............................................................................................................. 5
DEFINING AN ENTRY................................................................................................... 5
PROPOSED PROCESS ................................................................................................... 5
DOUBLE ENTRY PROCEDURE .................................................................................. 6
TIME ESTIMATION....................................................................................................... 6
COST ESTIMATION....................................................................................................... 7
COMPLEXITY OF DATA .............................................................................................. 9
IN-HOUSE VS. OUTSOURCED .................................................................................. 12
TENDER EVALUATION.............................................................................................. 12
BID EVALUATION CRITERION ............................................................................... 12
QUALIFICATION CRITERIA .................................................................................... 13
EVALUATION CRITERIA .......................................................................................... 14
SAMPLE TIME CALCULATION FORMS TEMPLATE ........................................ 17
COST CALCULATION SHEET .................................................................................. 18
DATA ENTRY COSTING EXAMPLE........................................................................ 19
COMPLEXITY CALCULATION SHEET.................................................................. 20
2
Data Entry Cost Estimation & Outsourcing Guidelines
Foreword
E-government initiatives are becoming pervasive in the public sector as the need
and demand for efficiency in the government operations grows. Information Technology
Policy and Action Plan of the government envisage the use of ICTs to build internal
efficiencies for an improved public service delivery. A number of IT projects are now
being implemented in the province. Most of them require huge and complex data to be
entered.
Once the software is developed the biggest challenge is that of data entry
particularly when it happens to be fairly large one. The government offices with their
present work force do not have sufficient capacity to do the job themselves. Whatever
little resource is available, it is usually engaged elsewhere doing daily chores and cannot
be spared for a dedicated effort for data entry. Particularly historic data entry is the most
crucial and delicate of all operations requiring speed, very high level of
accuracy/reliability and very stringent quality assurance process. No mistake in
government records that determine important rights and crucial obligations of the citizens
is acceptable. One hundred percent accuracy is essential. It has been observed that the
estimation of time and cost calculations are usually unrealistic and perfunctorily done.
Resultant time and cost overruns cause failure of the projects and optimal return on huge
investment that maay have gone into building an ICT infrastructure is not obtained. For
instance, in the case of Land Revenue Record Computerization Project for Kasur District,
it took more than 5 years with cost overruns and yet the data entry was not complete.
Despite the creation of a dedicated cell in 1998 in the Board of Revenue and huge
investment into hiring of workforce from the market, the entries of records of rights
maintained by the patwaries for all the villages have not yet been made. It is important to
recognize that government offices neither have the requisite manpower to do this kind of
job nor do they have the professionally competent supervisory management to technically
approach the issue. Large public organizations like NADRA have come to realize that
more professional approach and tools are required to complete particularly the large data
entry operations through outsourcing to the private sector. The current data and day to
day entries might, however, be another matter requiring a different approach; such as
building in-house capacity or hiring manpower through fresh recruitment. Success of any
big project with data building requirement lies in smooth and credible data entry
operation. These guidelines are generic in nature and designed to help the government
offices estimate as accurately and close to the requirement as possible. Outsourcing
parameters are meant to help acquire quality service in a transparent manner.
The document has been prepared by the IT Department to provide necessary
guidelines to make the job for the planners easier to calculate reasonably good estimates.
I would like to appreciate the contribution made by Prof. Dr. Noor M. Sheikh, UET, Dr.
Arif Iqbal Rana, Associate Professor, LUMS, Prof. Dr. Muhammad Naeem Ayyaz, UET,
and Mr. Osman Asad, Research Associate, LUMS. Thanks are also due to officers of the
departments of Services and General Administration, Finance and Planning and
Development, who supported the concept, examined the methodology and analysis tools
used in this document and gave useful input.
3
Data Entry Cost Estimation & Outsourcing Guidelines
The following broader objectives have been identified for the proposed
framework:
• Defining an entry
• Determination of time required and cost involved in each data entry proposal.
• Development of transparent and workable outsourcing mechanism.
• Formation of an objective criterion for measuring and comparing vendors' data
entry capabilities and their bids for the contract award.
4
Data Entry Cost Estimation & Outsourcing Guidelines
Introduction
Software projects can be classified into the following categories:
• System Software Projects
• Application Software Projects
o Scientific Applications
o “Data Oriented” Applications (Business Automation)
It is observed that more than 80% of total number of the Government projects for
computerization would fall in the category of “Data Oriented Applications”. Thus data
entry is a very important factor in the success of Data Oriented Applications. Without a
proper and accurate data entry, any software would only be a vaporware lying installed
without any tangible use.
Defining an Entry
Standardization of data entry may not be quite possible. This task is very much
dependent upon the format and type of data required to be entered. Urdu and English data
entries are completely different from each other and former requires less time & effort
than the latter. Quality of data would usually determine the number of man hours/ days
required for the task. In many cases there would be a requirement of scanning the
documents and linking them to the relevant data already entered; OCR may also have to
be applied, etc., and such a case cannot be easily compared with any other data entry task
even with a great deal of similarities within. There would be simple entries with lesser
fields (one or more) and complex entries (more than one). For example, an entry in I.D
Card would be simpler than the one in land revenue record where the entries are far more
complex and domain knowledge of the operator would also be an added requirement to
make the entry job efficient. Each entry in general would be determined on actual basis
by the time it takes.
Proposed Process
As the need for data entry is felt, it would always be advisable rather essential to
prepare a complete cost benefit analysis. Some departments may have sufficient capacity
to perform the task of data entry using their existing resources but this might be truer for
the current/ongoing records and not for the old records/historic data. In the latter case
outsourcing would usually be a preferred option. However in the case of outsourcing care
is required to be taken to ensure security of official data though it is equally important not
to jeopardize the operations by opting for self-entry without requisite capacity. It has also
been observed that estimated data entry costs in the government projects have been
incorrectly calculated resulting in lower estimates than the actual costs based on
prevailing market rates. Such mistakes have bearings on the time and cost resulting in
5
Data Entry Cost Estimation & Outsourcing Guidelines
Time Estimation
Calculating exact time required for the data entry in any project is dependent on a
number of variables. One possible way is counting the key strokes hypothetically
illustrated as below (Annexure B)
6
Data Entry Cost Estimation & Outsourcing Guidelines
Forms, however, should be designed before this calculation is done. Using above
table estimation can be worked out for simple entries but not for the complex ones like in
the case of Urdu handwritten characters. There would be need to perform an analysis on
the data and finding out the estimated number of forms to be entered for each designed
form. Multiplying each with the estimated time required to be entered should give
reasonable time estimation for complete data entry.
In this method however it would be important to actually get a sample data
entered and then calculate the speed, number of characters, field type, etc. Care should be
taken in keeping margins for the human endurance, capacity and attention levels.
For labor tasks one can assume a learning curve rate of at least 85%; which means
that every time we double the number of records entered, the time to enter a record
decreases by 85%. As shown in Table 2, if the 10,000th record is taking 10 minutes on
average, then the 100th record should have taken 29.5 minutes and the 1,000th record
17.16 minutes on average. The change in the overall average time for all records as the
total number of records changes is also given in Table 2. Given that the number of
records may be in millions, it is assumed that any vendor who is subcontracted data entry
would be handling at least 10,000 records of every type.
Cost Estimation
Cost of a project, if not calculated correctly, can bear the greatest risk of failure to
a project. Government projects need to be well equipped with cost benefit analysis to
avoid such a disaster. Following tables are recommended to be followed when
calculating cost of data entry in a project for determining the cost on the basis of man-
hours put in for the x number of entries in 1000 hours (Annexure C)
A data entry operator’s salary is assumed to be Rs 5,250 (and that of the quality
assurance operator and supervisor to be Rs 6,600 and 15,000 respectively). However,
salaries will vary depending upon the project and the nature of data entry job.
Also for calculating the average cost per hour, the general guidelines for each
Data Entry Operator, one Quality Assurance Operator and one Supervisor a ratio of
16:4:1. However, this will also vary as the nature of project varies (Annexure D)
7
Data Entry Cost Estimation & Outsourcing Guidelines
Quality Assurance
8
Data Entry Cost Estimation & Outsourcing Guidelines
Basic Data
Daily working hours 8
Working days a Week 6
Weeks a month 4.23
Working days a month 25.38
Quality Check @ 10% 0.8 Hours per day
Total 284,700.00 i
Management and Supervisory Expenditure (@ 150 % of (i) 427,050.00 ii
Other Fringe Benefits @ 50% of (i) + (ii) 355,875.00 iii
Grand Total (Without printing & Photocopy 1,067,625 A
Expenses)
Man-Hour Cost 136.88
Complexity of Data
Another important factor in calculating the cost of data entry is the complexity of
the data. Following table can be used for calculating the said complexity. This will lead to
calculating the estimated cost of data entry in relation to the factors that influence the data
entry greatly (Annexure E).
9
Data Entry Cost Estimation & Outsourcing Guidelines
COMPLEXITY MATRIX
Description of Process Level of Complexity
Quality of Data
Complexity Level
Level of Accuracy
Total (F)
Quality
Percentage
Allowance for Difficulty Level
Difficulty Level
0% (Qlevel1) Data is typed and clearly readable
20% (Qlevel2) Data is typed but not clearly readable
40% (Qlevel3) Data is hand written and clearly readable
50% (Qlevel4) Data is hand written and not clearly readable/
on an old fragile page
60% (Qlevel5) Sequence/ on a torn page/ old and very fragile
page
Complexity
Percentage
Allowance for Difficulty Level
Difficulty Level
0% (Clevel1) All field are on the same page
30% (Clevel2) Fields are separated on more than two
pages/more than one book
40% (Clevel3) Fields are separated on more than three
pages/more than two books
50% (Clevel4) Fields are separated on more than four
pages/more than three books
60% (Clevel5) Fields are separated on more than five
pages/more than four books
Table 6 – Complexity
10
Data Entry Cost Estimation & Outsourcing Guidelines
Accuracy
Percentage
Allowance for Difficulty Level
Difficulty Level
0% (Alevel1) Data is without any typing mistakes
20% (Alevel2) Data is with typing mistakes ≥1% & ≤ 9%
30% (Alevel3) Data is with typing mistakes ≥10% & ≤ 19%
40% (Alevel4) Data is with typing mistakes ≥20% & ≤ 29%
50% (Alevel5) Data is with typing mistakes ≥30% & ≤ 39%
60% (Alevel6) Data is with typing mistakes ≥40%
Table 7 - Accuracy
Once the complexity of the data is calculated and multiplied with the estimated
man-hour cost, the resulting cost should be added to the estimated man-hour cost.
COMPLEXITY MATRIX
Above example shows that a data with Quality level 20%, Complexity level 40%
and Accuracy level 20% will increase the cost @ 80 %. This also depicts that if the data is
prefect there will be no change in the anticipated cost. Overall increase in the cost is
anticipated to be between 10 to 160%.
11
Data Entry Cost Estimation & Outsourcing Guidelines
Tender Evaluation
When the data entry projects are outsourced, capability of the vendor plays a
significant role in the final outcome of the project. It is therefore imperative that
acquisition of domain knowledge, management capability and rational estimation are
analyzed carefully to evaluate the information regarding vendors and their bids.
Preferably the data entry should be outsourced to the customized software vendor to allay
the copyright concerns and to elicit a commitment to make the project a success as data
entry is 100% integral to the use of software application and success of its operations. The
software vendor may, however, subcontract the data entry services at his own will.
12
Data Entry Cost Estimation & Outsourcing Guidelines
Qualification Criteria
Only the companies that meet following criteria will be allowed to participate in
the tendering process.
a. Firm must possess a recent and active International Quality certification from any
UKAS recognized International Quality Auditing Company.
b. Firm must be financially sound and for evidence thereof last 3 years annual tax
returns should be submitted and audited financial reports as well as references
from banks may also be provided for the purpose of assessment.
c. Firm must be willing to deliver the required services within the time span
proposed by the tendering department with a negotiable margin from 10 to 20%.
d. Firm must not have misrepresented any information in the submitted proposal
e. Firm must not have failed to deliver a project in public sector
13
Data Entry Cost Estimation & Outsourcing Guidelines
Evaluation Criteria
TECHNICAL PROPOSAL EVALUATION CRITERIA
*(80% marks in each individual section & 80% marks overall will be the passing criteria)*
**(Failure in a single section will amount to disqualification from the bid)**
2. Company Quality 175 Firm must possess Specific and/or General Quality management
Management certification. Only current year and active certifications will score
any point.
a. Overall ISO9001:2000 or CMM Level 3 Quality
Certification. In case of Local Auditors 60 points and
Foreign Auditors 100 points
b. Very specific to project/job ISO9001:2000 or CMM Level 3
Quality Certification. In case of Local Auditor 140 points
and Foreign Auditors 175 points
Multiple certifications (overall or specific) do not count for
separate points. Maximum points to be awarded in this section
will not exceed 175 points.
3. Project Experience with 225 Past project experience of the firms will be evaluated on the basis
special relevance to the of following criteria:
experience related to the 1. Recent/Current projects – last 3 years (65 pts per project)
Assignment being tendered for 2. Past Projects done in the last 7 years (40 pts per project)
3. 25 additional points to be awarded for each project
relevant to the tendered project in terms of
content/knowledge base and/or task/activity.
Total points in this section will not be allowed to exceed 225
points. The evaluation of each project will not only be done on
the basis of number of projects but also on the size of the project,
technical challenges faced, content/quality of the delivered
projects, documentation, processes followed as well as delivery
and client satisfaction. Client satisfaction of the project must be
presented in the form of a letter issued by no less than the CEO or
Head of the Department/Organization/Project Director/Manager.
4. Proposed Project 320 Detailed proposals must be submitted as well as presented before
Methodology and Work Plan the evaluation committee.
1. Rationale, Professional Quality and Content of the
Written Proposed Methodology (100 points)
2. Interview and Presentation on the Proposed Methodology
(90 points)
3. Demonstration of the Software Prototype/Data Entry
Demonstration of proposed Skill set (Data Entry Times
will be used as a marker for rationalizing the submitted
Financial Proposal in the latter part of the Bid
14
Data Entry Cost Estimation & Outsourcing Guidelines
15
Data Entry Cost Estimation & Outsourcing Guidelines
Annexure – A
1. The GUI design of the Land Record Management Information System should be
such that the curser should jump automatically to next data entry box whenever
the operator hits the ENTER key or any specific key on the keyboard.
2. The automatic movement of curser from one field to another must be designed in
such a manner that the effort in grabbing data from the source documents
(i.e. Register Haqdaraan-e-Zamin, Shajra-e-Nasab, Register Gardawari and
Taghayyaraat, and Register Intiqaal) is minimal. This can be done by ensuring that
the data entry operator moves to next source document/page, if possible, only after
all the data from the previous source document/page has been entered into the
system. Furthermore, the flow of cursor movement in GUI should be designed in
such a way that there is natural flow of information retrieval from the source
document.
These changes in the GUI design will save the time for data entry operator (and
hence the cost saving for both the Client and the Consultant) which is being wasted in
moving the mouse to the next field and then clicking to activate it. Also, the time wasted
in searching/navigating between different source documents, for required data, could be
saved. Following are some examples.
• There should be a way to go to the previous page when entries on next opened
page have been completed.
• To select a drop down, it should be clicked only once by mouse. This feature is
not currently implemented in RHZ.
• Typical sentences of Note, Pemana-e-Haqeeat, Lagaan should be already shown
in GUI. Also in the ID card no. entry, dashes should be shown by default to save
a couple of key strokes.
• Land Share should be calculated by the system (use calculator) or, if possible
Data Entry operator should only need to enter values in a formula to calculate
the land share.
• In RHZ, if ‘Malik ka naam’ is not found in the Drop down then Data Entry
operator should enter it in the drop down text field, not in another text field.
• In Date field, dd-mm-yy format should be followed in case Data Entry Operator
doesn’t want to look at Calendar for selecting Date.
By studying the data entry flow in detail, an optimized navigation flow in software
GUIs and source documents could be designed. If this is ensured, a further 3-5 percent
reduction in the effort and consequent proportional increase in the productivity could be
achieved. It is predicted that with this little effort, at least 3 percent further reduction
would easily be achieved.
16
Data Entry Cost Estimation & Outsourcing Guidelines
Annexure – B
17
Data Entry Cost Estimation & Outsourcing Guidelines
Annexure – C
Costing Sheet
Basic Data
Daily working hours 8
Working days a Week 6
Weeks a month 4.23
Working days a month 25.38
Quality Check @ 10% 0.8 Hours per day
Data Correction Wait Time @ 20% 1.6 Hours per day
Management and Supervisor Expenditures @ 10 % of Total cost
Estimated time required Z Hrs (a)
Quality Check time (@ 10%) 0 Hrs (b)
Data Correction wait time (@ 20%) Z*20/100 Hrs ( c )
Time required with Quality Check & Data Correction a+b+c Hrs (d)
Time required with 5 DEOs d/5 Hrs (e)
Pay of one Data Entry Operator 175 /Hour
Pay of one Quality Assurance Operator 220 /Hrs
Total pay of DEOs e*175*5 Rs (f)
QAO's pay(For every 5 DEOs there will be one QAO) e*220 Rs(g)
18
Data Entry Cost Estimation & Outsourcing Guidelines
Annexure – D
19
Data Entry Cost Estimation & Outsourcing Guidelines
Annexure E
COMPLEXITY MATRIX
Description of Process Level of Complexity
Quality of Data P
Complexity of Data R
Level of Accuracy S
Total T = P + R +S
Total Cost = (T % * A) + A
20