| |
|
|
Software Procurement FAQs |
|
|
|
|
|
| 1. Has the software for Land Records Management and Information Systems been developed? | | The project of developing software for maintenance of land records has been executed through a competitive outsourcing scheme. Four firms have developed a software product each. |
| | Back to Top | 2. Which firms have worked on development of software for LRMIS? | | | The firms which worked on the software development project for LRMIS were: - Accountancy Outsourcing Services (Pvt.) Ltd
- Techlogix Pakistan (Private) Limited
- Netsol Technologies Limited
- Descon Information Systems (Pvt.) Limited
|
| | Back to Top | 3. How were the four firms selected to enter the competition? | | An international invitation for expression of interest in the software development project was issued by Punjab Information Technology Board on 31-05-2006. This invitation was published in United Nations Development Business on 02-06-2006, the Dawn on 31-05-2006 and the News on 31-05-2006. 22 firms expressed interest in the project. Punjab Information Technology Board shortlisted 10 firms out of these 22 on the basis of the following criteria | Criteria for Pre-qualification of firms | Mandatory Requirements | | Following are the mandatory requirements that each Consultant had to meet in order to be pre-qualified | - Last three (3) years average annual Software sales of the Consultant should be greater than Rs. 14.0 Million (Approx. $ 233,000 USD). Copies of last three years income tax return or financial statement must be provided with the EOI.
- The Consultant must have developed a software application with multilingual support using UNICODE.
- Following conditions shall be considered in the technical evaluation for the reference(s) provided by the bidding Consultants in their EOI
- The referenced (already deployed) mulit-tier / multiuser / Online Transaction Processing (OLTP) client server based application on RDBMS in a distributed environment must be handling ten thousand (10,000) transactions (Insert / Update) per year.
- Only the reference(s) of the bidding Consultants shall be considered in the technical evaluation and not its subsidiary(ies) or sister company(ies).
- Only the resource(s) of the bidding Consultants shall be considered in the technical evaluation and not its subsidiary(ies) or sister company(ies).
- Consultant must have developed and successfully deployed a minimum of one (1) mulit-tier / multiuser / Online Transaction Processing (OLTP) client server based application on RDBMS in a distributed environment.
- Consultant must have been in business for a minimum period of one (1) year.
| Technical Evaluation Criteria for Pre-Qualification | | Evaluation Parameter | Total Marks | Details | | Expression of Interest | 50 | 1) Mulit-tier / multiuser / Online Transaction Processing (OLTP) client server based application on RDBMS in a distributed environment developed and deployed successfully in the last five years. Each project should have a minimum worth of PKR I.0 Million ($ 16,667/- USD) - Four (04) software development projects (Excluding Hardware and Networking) of combined worth over PKR 8.0 Million ($ 133,333/- USD) 50 Marks
- Three (03) software development projects (Excluding Hardware and Networking) of combined worth over PKR 6.0 Million ($ 100,000/- USD) 35 Marks
- Two (02) software development projects (Excluding Hardware and Networking) of combined worth over PKR 4.0 Million ($ 66,666/- USD) 20 Marks
- One (01) software development project (Excluding Hardware and Networking) of worth over PKR 2.0 Million ($ 33,333/- USD) 10 Marks
- No project 0 Marks
| | | 25 | 2) Provide Company Profile, mention years of experience - 4 years 50 Marks
- From 3 to 4 years 20 Marks
- From 2 to 3 years 15 Marks
- From 1 to 2 years 10 Marks
- One year 05 Marks
- Less than 1 year 0 Marks
| | | 25 | 3) Provide the detail profile of the following Personnel to be appointed for this project on a full time basis - Project Manager10 Marks
- Education 03 Marks
- MS 03 Marks
- MBA/BS/MIT/M.Sc/BCS/MCS 02 Marks
- PMP Certified 03 Marks
- Project Management Experience 04 Marks
- 5 Yrs of Exp 04 Marks
- 3 to 5 Yrs of Exp 03 Marks
- 2 to 3 Yrs of Exp 01 Marks
- Less than 2 Yrs of Exp 0 Marks
- System / Business Analyst 05 Marks
- Education 02 Marks
- MS 02 Marks
- MBA/BS/MIT/M.Sc/BCS/MCS 01 Marks
- System/Business Analysis Experience 03 Marks
- 5 Yrs of Exp 03 Marks
- 3 to 5 Yrs of Exp 02 Marks
- 2 to 3 Yrs of Exp 01 Marks
- Less than 2 Yrs of Exp 0 Marks
- Database Administrator05 Marks
- Education 02 Marks
- MS 02 Marks
- MBA/BS/MIT/M.Sc/BCS/MCS 01 Marks
- DBA Experience 03 Marks
- 5 Yrs of Exp 03 Marks
- 3 to 5 Yrs of Exp 02 Marks
- 2 to 3 Yrs of Exp 01 Marks
- Less than 2 Yrs of Exp 0 Marks
- Quality Assurance Manager 05 Marks
- Education 02 Marks
- MS 02 Marks
- MBA/BS/MIT/M.Sc/BCS/MCS 01 Marks
- Quality Assurance Experience 03 Marks
- 5 Yrs of Exp 03 Marks
- 3 to 5 Yrs of Exp 02 Marks
- 2 to 3 Yrs of Exp 01 Marks
- Less than 2 Yrs of Exp 0 Marks
| | Total | 100 | |
| Note: - The Consultant must meet all the “Mandatory Requirements” in order to be pre-qualified.
- The Consultant must obtain a minimum of 50% of the total 100 marks in the technical evaluation in order to be pre-qualified.
- Consultant must provide the listing of their clients where the reference software application has been successfully deployed by the Consultant. Reference letter(s) from the client(s) should also be submitted with EOI.
- Years of qualification of the personnel in the above mentioned evaluation criteria shall be considered as given below:
| Sr.No | Degree | Years | | 1 | MS (Computer Sciences or any Engineering field) | Minimum of 17 Years of Education | | 2 | MBA / BS (Computer Sciences or any Engineering field) / MIT / M.Sc (Computer Sciences or any Engineering field) | Minimum of 16 Years of Education | | 3 | BCS / MCS | Minimum of 15 Years of Education |
Requests for proposals were issued to these ten firms on 18-09-2006. Six firms submitted their technical and financial proposals. Technical proposals were opened on 04-11-2006. Four firms out of these six were selected on the basis of the following criteria. Technical Evaluation Criteria for selection of four (4) Consulting firmsMandatory RequirementsThe Consultant must provide a detailed process / explanations on how the mandatory requirements will be satisfied. If any of the mandatory requirements is not met / satisfied by the Consultant, it shall result in the disqualification of the Consultant and the LRMIS Software application developed by the Consultant. The Consultant must obtain a minimum of 650 Marks (65%) out of 1000 Marks in the Technical Evaluation. Failure to obtain a minimum of 650 Marks in total or Less than 65% marks in any category/section in the Technical Evaluation shall result in disqualification of the Consultant. Other mandatory requirements are categorized as under: Requirements for Consultants- Foreign Consultant must manifest their ability to travel freely to Pakistan and should obtain work permit.
- Foreign Consultant must show his / her ability to conduct business in Pakistan and must have a Local Bank Account.
- Foreign consultant(s) must elaborate his / her detailed business plan in Pakistan for this project.
Technical Evaluation Criteria for Pilot
| i | | Adequacy of the proposed methodology and work plan in responding to this RFP Document. | | | 600 | | | a | Technical approach and methodology | | 110 | | | | | - CMM / ISO
- CMM Level 5
- CMM Level 4
- CMM Level 3 / ISO Certification
| | 20 | | | | | | - Methodologies (Each year of experience will get 04 points with the maximum of 20 points for 5 years of experience.)
- Project Implementation Methodologies
- Project Management Lifecycle
- Experience in proposed methodology
- Software Engineering Methodologies
- Software development Lifecycle
- Experience in proposed methodology
- Support and Maintenance Methodologies
- Support and Maintenance plan
- Standard Operating Procedure (SOP) for Bug Tracking & Fixing (Please provide reference(s) where these SOPs were implemented.)
| - Max 90 Marks
- 30 Marks
- 30 Marks
- 30 Marks
| 90 | | | | | b | Work plan | | 440 | | | | | Detailed Project Plan (Detail project plan including activities, resources, cost estimation, tasks, along with deliverables and timelines) | 30 | | | | | | - Proposed Business Process Model
- High Level Data Model
- Data Flow Diagrams
- Business Process Flow Model/Diagrams
- Object Oriented Approach
| - Max 20 Marks
- 05 Marks
- 05 Marks
- 05 Marks
- 05 Marks
| 20 | | | | | | FIFO (First in First Out: The system to be able to handle applications queue base on the priorities assigned to the transactions.) | Max 30 Marks | 30 | | | | | | Proposed Security | | 150 | | | | | | Proposed Security | | 150 | | | | | | - Application user authentication
- Password
- Biometric
- Equipment Registration
- Role Based
- Role Based
| - Max 25 Marks
- 05 Marks
- 05 Marks
- 05 Marks
- 05 Marks
- 05 Marks
| | | | | | | - Data Integrity
- Message Digest
- Creation of user Logs
- Detection and prevention of Tampering
| | | | | | | | - Data Security
- Encryption
- Secure Exchange of data over the network / internet
- Restriction of data to Authorized Equipment, Kanungoi and Tehsil
| | | | | | | | - Proposed Application Security
- o User level (Only the authorized user(s) should be able to access the LRMIS software application)
- o Module Level (Only the authorized user(s) should be able to access a LRMIS Software module(s))
- o Form / Report Level (Only the authorized user(s) should be able to access a form(s) / report(s))
- o Function level (Only the authorized user(s) should be able to Create, View and Update record(s).)
- o Field Level (Only the authorized user(s) should be able to update certain field(s))
| - Max 50 Marks
- 10 Marks
- 10 Marks
- 10 Marks
- 10 Marks
- 10 Marks
| | | | | | | Proposed Software Application Performance and Scalability | | 90 | | | | | | Level of Support Provided by the consultant to enhance the software application | Max 20 Marks | | | | | | | Database and Hardware Configuration Management - Resource(s) requirement
- Time Requirement
| Max 10 Marks | | | | | | | Database Import and Export Utility Module | Max 20 Marks | | | | | | | Software Application Performance - Time Required for data entry in the register(s)3(Please Specify the Proposed time to enter data in each registers mentioned in footnote three (3) Page 44
- Time required to search a records 3 (Please Specify the Proposed time to search the record for each register(s) / report(s) mentioned in footnote three (3) Page 44
- Time required for data transfer from Kiosk(s) to Tehsil(s) / District HQ Tehsil(s), Tehsil(s) to District HQ Tehsil(s), District HQ Tehsil(s) to Provincial Data Center and vice versa.
| Max 40 Marks | | | | | | | Proposed Tier Approach - Business Process Layer
- GUI and Presentation Layer
- Data Access Layer
| Max 15 Marks | 15 | | | | | | Data Entry - Approach
- Heads up
- Heads down
- Double data entry
| Max 30 Marks | | | | | | | Data Verification - Data entry verification software
- Maintaining Data Entry Operator logs
| Max 60 Marks | | | | | | | Data Entry standard operating procedures (SOP) and Data Entry Plan ( The Transactional Software developed by the Consultant shall be used for Data Entry ) - Data Entry Resources ( Number of resources, Data Entry Terminals, placement)
- Data Entry Quality Management Plan
- Data Entry SOP
| Max 15 Marks | | | | | | | Organization and staffing - Detail Organization Structure (Detail Organization Structure(with organogram) should include technical, non-technical and networking strength of the organization)
- Data Entry Quality Management Plan
- Data Entry SOP
| | 50 | | | | ii | Key professional staff qualifications and competence for the assignment | | | | | 300 | | | | Project Manager | | | 40 | | | | | Education | Max 10 Marks | 10 | | | | | | PMP Certified | Max 05 Marks | 10 | | | | | | Project Management Experience - 5 Yrs of Exp
- 3 to 5 Yrs of Exp
- 2 to 3 Yrs of Exp
- Less than 2 Yrs of Exp
| Max 25 Marks - 25 Marks
- 15 Marks
- 05 Marks
- 0 Marks
| 25 | | | | | | Training Manager | | | 30 | | | | | Education | Max 10 Marks | 10 | | | | | | Experience - 5 Yrs of Exp
- 3 to 5 Yrs of Exp
- 2 to 3 Yrs of Exp
- Less than 2 Yrs of Exp
| Max 20 Marks - 20 Marks
- 10 Marks
- 05 Marks
- 0 Marks
| 20 | | | | | | System / Business Analyst / System Architect | | | 30 | | | | | Education | Max 10 Marks | 10 | | | | | | Experience - 5 Yrs of Exp
- 3 to 5 Yrs of Exp
- 2 to 3 Yrs of Exp
- Less than 2 Yrs of Exp
| Max 20 Marks - 20 Marks
- 10 Marks
- 05 Marks
- 0 Marks
| 20 | | | | | | Database Administrator | | | 30 | | | | | Education | Max 10 Marks | 10 | | | | | | Experience - 5 Yrs of Exp
- 3 to 5 Yrs of Exp
- 2 to 3 Yrs of Exp
- Less than 2 Yrs of Exp
| Max 20 Marks - 20 Marks
- 10 Marks
- 05 Marks
- 0 Marks
| 20 | | | | | | Quality Assurance Manager | | | 30 | | | | | Education | Max 10 Marks | 10 | | | | | | Experience - 5 Yrs of Exp
- 3 to 5 Yrs of Exp
- 2 to 3 Yrs of Exp
- Less than 2 Yrs of Exp
| Max 20 Marks - 20 Marks
- 10 Marks
- 05 Marks
- 0 Marks
| 20 | | | | | | Technical Writer | | | 30 | | | | | Education | Max 10 Marks | 10 | | | | | | Experience - 5 Yrs of Exp
- 3 to 5 Yrs of Exp
- 2 to 3 Yrs of Exp
- Less than 2 Yrs of Exp
| Max 20 Marks - 20 Marks
- 10 Marks
- 05 Marks
- 0 Marks
| 20 | | | | | | Domain Expert5 (domain expert must have experience with the revenue records.) | | | 20 | | | | | Experience - 20 or more Yrs of Exp
- 10 to 19 Yrs of Exp
- 05 to 09 Yrs of Exp
- Less than 5 Yrs of Exp
| Max 20 Marks - 20 Marks
- 15 Marks
- 10 Marks
- 0 Marks
| | | | | | | At least 09 development resources in the proposed programming languages with more than 2 years of experience. | | | 60 | | | | | - Team Lead Development (Sr. Software Engineer/Application Software Engineer)
| | 10 | | | | | | - 8 Software Engineers / Software Developer / Programmer
| | 50 | | | | | | Four QA Resources with more than 2 years of experience. | | | 30 | | | | | - Team Lead QA (Sr. Quality Assurance Analyst)
| | 10 | | | | | | | | 20 | | | | iii | | Suitability of the transfer of knowledge (training) program | | | | 50 | | | a | Relevance of training program | | | 10 | | | | b | Training approach and methodology | | | 30 | | | | | Training plan | | 10 | | | | | | Technical / User Manuals (Samples from the previous projects must be submitted with the proposal) | | 20 | | | | | c | Qualifications of experts and trainers | | 10 | | | | iv | | Participation by nationals among proposed key staff | | | | 50 |
The minimum technical score required to pass is: 650 Marks Only four (4) Consulting firms were to be selected for the pilot phase. In case more than four (4) firms met the minimum point’s requirement, the four (4) with the highest point’s scores were to be selected. |
| | Back to Top | 4. Was selection of these four firms based on their financial proposals? | | No. Punjab Information Technology Board chose the means of a fixed price contract for the competition phase of software development. Therefore, for the competition phase financial proposals were not invited. The request for proposal simply stated that for this phase each of the four selected firms will be paid Rs. 7,837,500 PKR. Financial proposals were submitted by these firms alongside their technical proposals but these were only for the subsequent phase when one of the firms would be selected. These financial proposals were kept sealed and were opened only for the two firms whose software products qualified on the basis of the criteria included in the Request for Proposal. |
| | Back to Top | 5. Was any contract signed with these four firms for the software development process? | | Yes. A separate contract was signed with each of these firms. The Request for Proposal contained two draft contracts. One to be signed with each of the four firms and one to be signed with the top ranking firm after technical evaluation of the software and evaluation of the financial proposals. |
| | Back to Top | 6. What were the deliverables expected from these four firms during the software development process? | The deliverables expected from these four firms during various phases of the software development process were as under: | Sr. No | Phase | Deliverables | | 1 | Initial | Detailed Project Plan | | 2 | Analysis | Software Requirement Specification | | 3 | Hardware Procurement | Hardware for the Kanungois (Servers, Workstations, Network Printers, UPS, Wireless Access Points, DVDs, CDs, USBs) | | 4 | Design | Functional Specifications Document Domain Knowledge Document | | 5 | Development | Technical Functional Specifications Document | | 6 | System Integration and QA | Detailed Test Plan Detailed Test Cases Installation Manual Application setup Manual | | 7 | User Acceptance Testing | Test Status Report UAT Report Updated Patches of the Software Application | | 8 | Data Entry | Data Entry Plan and SOP LRMIS Database backup Instruction Manual | | 9 | Deployment Phase | Installation & Deployment Manual User Manual Source Code Training Manual | | 10 | Training Phase | LRMIS Training material |
|
| | Back to Top | 7. Which deliverables were submitted by the four firms? | The details about submission of deliverables by the four firms is given in the following table. The deliverables were handed over to the PMU-Board of Revenue by PITB after transfer of executing agency and the deliverables marked with a “YES” are available with PMU-Board of Revenue.
| Sr. No | Deliverables | AOS | DESCON | NETSOL | TECHLOGIX | | 1 | Detailed Project Plan | YES | YES | YES | YES | | 2 | Software Requirement Specification | YES | | YES | YES | | 3 | Hardware for the Kanungois (Servers, Workstations, Network Printers, UPS, Wireless Access Points, DVDs, CDs, USBs) | YES | YES | YES | YES | | 4 | Functional Specifications Document | YES | YES | YES | YES | | | Domain Knowledge Document | YES | YES | YES | YES | | 5 | Technical Functional Specifications Document | YES | YES | YES: Hard copy is available | YES | | 6 | Detailed Test Plan | YES | YES | YES | YES | | | Detailed Test Cases | YES | YES | YES | YES | | | Installation Manual | YES | YES | YES | YES | | | Application setup Manual | YES | YES | YES | YES | | 7 | UAT Report | YES | YES | YES | YES | | | Updated Patches of the Software Application | YES | YES | YES | YES | | 8 | Data Entry Plan and SOP | YES | NO | YES | YES | | | LRMIS Database backup | YES | NO | YES | YES | | | Instruction Manual | YES: Hard copy is available | NO | NO | NO | | 9 | Installation & Deployment Manual | YES | NO | YES | YES | | | Source Code | YES | NO | YES | YES | | | Training / User Manual | YES | NO | YES: Hard copy is available | YES | | 10 | LRMIS Training material | YES | | YES | NO |
|
| | Back to Top | 8. Was payment to be made for each of these deliverables separately or was it to be a Lumpsum payment? | | A schedule of payments was a part of the contracts with all the four firms. According to this schedule (Appendix E of the contract), payments were to be made to the firms on successful completion of each of the nine phases and acceptance of the deliverables associated with that phase. |
| | Back to Top | 9. Was any payment made to these firms for their development effort? If yes, how much? | Yes payments were made to these firms for their development effort. The payments made to these firms were as under:
| Sr. No | Milestone | Milestone | NETSOL | AOS | TECHLOGIX | DESCON | | 1 | Initial Payment | 13-Mar-07 | 800,000 | 800,000 | 800,000 | 800,000 | | 2 | Analysis Complete | 26-Jul-07 | 800,000 | 800,000 | 800,000 | 800,000 | | 3 | Hardware Procurement | 9 Sep 2007 for AOS/Techlogix, 25 Oct 07 for DESCON and 31 Jan 08 for NETSOL | 837,500 | 837,500 | 837,500 | 837,500 | | 4 | Detailed Design Complete | 25-Oct-07 | 800,000 | 800,000 | 800,000 | 800,000 | | 5 | Development Complete | 14 Mar 08 for NETSOL/AOS/Techlogix and 31 Jan 08 for DESCON | 800,000 | 800,000 | 800,000 | 800,000 | | 6 | System Integration and QA Testing Complete | 30-May-08 | 800,000 | 800,000 | 800,000 | 800,000 | | 7 | User Acceptance Test Complete | 2-Aug-08 | 800,000 | 800,000 | 800,000 | | | 8 | Data Entry Complete | 20 Oct 08 for AOS, 11 Jun 09 for NETSOL | 300,000 | 600,000 | | | | 9 | Deployment Complete | | | | | | | 10 | Training Complete | | | | | | | | Total Payment | | 5,937,500 | 6,237,500 | 5,637,500 | 4,837,500 |
|
| | Back to Top | 10. Are the software products developed by these firms owned by these firms or the government? | | These software products are owned by the Government of the Punjab in accordance with the contracts signed between the client and these firms (Clause 3.7 (a) of General Conditions of Contract) |
| | Back to Top | 11. Has the source code of the software products delivered by these firms to the government? | | Yes. Source code of the software products has been delivered to the Government as a deliverable for the QA and testing phase of the software development. |
| | Back to Top | 12. Who owns the source code of these software products? | | Source code of the software products for LRMIS software developed by these firms is owned by the Government of the Punjab in accordance with the contracts signed between the client and these firms (Clause 3.7 (a) of General Conditions of Contract). |
| | Back to Top | 13. Was each of these firms successful in developing a software? | | Each of these firms developed a software product. However, the product developed by Descon Information Systems (Pvt.) Limited could not pass the User Acceptance Tests. As a consequence the contract with the firm was terminated by Punjab Information Technology Board. |
| | Back to Top | 14. What was the criterion for selection of a software product from among the four products developed by these four firms? | The selection of one firm out of the four, in the first (competitive) phase of the process was to be made through technical evaluation of the software product and performance of the firm as well as on the basis of the financial proposals of the firms. The weight assigned to the technical and financial evaluation was 60% and 40% respectively. Punjab Information Technology Board (PITB) developed detailed criteria for technical evaluation of the software. These criteria were a part of the Request for Proposals sent to the ten shortlisted firms as mentioned above. The criteria as given in the Request for Proposals were as under Mandatory Requirements- All the deliverables mentioned in section 5 Terms of Reference are mandatory
- Input and output for customized software should be according to existing business processes of BOR
- Multilingual (Urdu and English) Support. All screens/forms must be in Urdu Nastaleeq font.
- Efficient register inter linkages - The user should only have to enter the data once in the software application. Meaning, if the data is entered on one form it should be linked to and reflected in all the relevant forms / registers without requiring the user to enter it again
- Data Replication Module / Routines between Kiosks / Service Center, Tehsil / District HQ Tehsil(s) and Provincial Data Center must be provided
- The Consultant must obtain a minimum of 390 Marks (65%) out of 600 Marks in the Final Evaluation for the opening of Financial Proposals and for further consideration. Failure to obtain a minimum of 390 Marks in total in the Final Evaluation shall result in disqualification of the Consultant
- The Consultant shall install the complete software application at the Data Entry Consultant(s) / Vendor(s) site(s) selected by the Client. There shall be no additional licensing and installation charges (other than the price quoted in the financial proposal of the Consultant) for the Client and the data entry Consultant(s) / Vendor(s). Also, the Consultant shall train the relevant technical staff of the Client in installing the Software Application and provide all the source code and third party tools (if used in the software application). There shall be no additional charge to the Client and Data Entry Consultant(s) / Vendor(s) for this service given by the Consultant.
- The LRMIS Software Application must be developed on the latest version of tools, technology(ies) and database(s) (for example .Net, Java, SQL Server, ORACLE etc).
- Any third party application development tool(s) and database(s) used in the LRMIS Software application must be supported by the original third party Vendor(s). The LRMIS Software developed on an older / de-supported version of the application development tool(s) or database(s) shall not be accepted
- Forms / Reports mentioned in endnote three (3) are mandatory. However, the number of Forms / Reports can increase or decrease after the detail analysis by the selected consultants with the approval from the Client.
- The Consultant shall also provide the time taken to enter data, record search and printing of records.
- If any of the mandatory requirements is not met / satisfied by the Consultant, it shall result in the disqualification of the Consultant and the LRMIS Software application developed by the Consultant.
| | | | | Total Marks | | 1. Application Architecture | | | | 25 | | Distributed Operation | | 05 | | | | Layering and Modularization | | 05 | | | | Graphical User Interface / Usability | | 15 | | | | 2. Software Scalability | | | | 40 | | • Response time | | | 10 | | | • Data retrieval and Printing | | 05 | | | | • Replicating entries from multiple sources | | 05 | | | | • Interoperable data-entry formats and storage. | | | 10 | | | • Time taken to rebuild a Kiosk server from scratch following a full server crash10. | | | 10 | | | • Database Import and Export Utility Module (Import Utility shall be tested by importing all the 25 thousands records from some other Kiosk(s) database and export the data in the same way to the other Kiosk(s) database. The import export module should be able to import and export data to XML format). | | | 10 | | | 3. Backup and Recovery Plan | | | | 50 | | • Integrated backup management function | | | 10 | | | • Recovery mechanism for system outage | | | 20 | | | • During transaction (This will be tested by pulling the power plug / network cable while performing a transaction). | | 10 | | | | • During system recovery process. (Crash of software application / RDBMS) | | 10 | | | | • Integrated roll back function | | | 20 | | | • Roll Back during Data Transfer (This will be tested by pulling the power plug / network cable while transferring the data from kiosk to District HQ Tehsil(s) and District HQ Tehsil(s) to provincial data center) | | 10 | | | | • Must have the capability to restore the complete database and database table(s). | | 10 | | | | 4. Security | | | | 150 | | • Access Control and Authentication | | | 25 | | | • Password | | 05 | | | | • Biometric | | 05 | | | | • Equipment Registration | | 05 | | | | • Role Based | | 05 | | | | • Centralized Security Management across the network (For example, Software application administrator should be able to lock / unlock a user(s), Kiosk(s), Tehsil(s) from a Centralized location / Provincial Data Center.) | | 05 | | | | • Software Application Security | | | 50 | | | • User level (Only the authorized user(s) should be able to access the software application) | | 10 | | | | • Module Level (Only the authorized user(s) should be able to access a module(s)) | | 10 | | | | • Form / Report Level (Only the authorized user(s) should be able to access a form(s) / report(s)) | | 10 | | | | • Function level (Only the authorized user(s) should be able to Create, View and Update record(s).) | | 10 | | | | • Field Level (Only the authorized user(s) should be able to update certain field(s)) | | 10 | | | | • Secure Storage and Retrieval of datay | | | 50 | | | • Persistence of records and logging of updates to track changes in the system. (The system must ensure that no record is ever deleted, while changes to the database must always be traced back to an authorized user.) | | 25 | | | | • Logging and updates: All changes/updates to the software application must be logged and tracked. | | 25 | | | | • Database Security (Field level encryption and security) | | | 25 | | | • Secure Data Replication including Encryption | | 15 | | | | • Database Authentication and Authorization. | | 15 | | | | 5. Database Architecture | | | | 50 | | • Database Design | | | 25 | | | • Effectiveness of Database Design | | 25 | | | | • Database interoperability with other Database System | | | 15 | | | • Extensibility in Data-entry fields | | | 10 | | | 6. Application Maintenance | | | | 20 | | • Application Installation Mechanisms | | | 10 | | | • Ease of Installation | | 10 | | | | • Ease of Application Configurations | | | 10 | | | • Configuration Time | | 03 | | | | • Updates / Patches | | 03 | | | | • Resource Utilization | | 02 | | | | • Remote Configurations | | 02 | | | | 7. Forms & Reports | | | | 75 | | • Forms | | | 50 | | | • Data Entry Time | | 30 | | | | • Data Retrieval | | 10 | | | | • GUI | | 10 | | | | • Reports | | | 25 | | | • Samples and instructions of reports design and integration into the system | | 10 | | | | • Sort Categories of Search Criteria | | 05 | | | | • Print / View Time | | 05 | | | | • Quality of Report Formatting | | 05 | | | | 8. Data Entry | | | | 25 | | • Approach | | | 07 | | | • Heads up | | 03 | | | | • Heads down | | 01 | | | | • Double data entry | | 04 | | | | • Data Verification | | | 08 | | | • Data entry verification software | | 05 | | | | • Maintaining Data Entry Operator logs | | 03 | | | | • Data Entry standard operating procedures (SOP) and Data Entry Plan ( The Transactional Software developed by the Consultant shall be used for Data Entry ) | | | 10 | | | • Data Entry Resources ( Number of resources, Data Entry Terminals, placement) | | 04 | | | | • Data Entry Quality Management Plan | | 03 | | | | • Data Entry SOP | | 03 | | | | 9. Documentation | | | | 50 | | • Analysis and Design Documents | | | 42 | | | • Software Requirement Specification | | 06 | | | • Quality of Document - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Contents and Completeness - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Formatting and Indexing - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | | • Analysis Document (Business Process Flow) | | 06 | | | • Quality of Document - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Contents and Completeness - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Formatting and Indexing - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | | • Design Document including ER Diagram | | 06 | | | • Quality of Document - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Contents and Completeness - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Formatting and Indexing - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | | • Functional Specification | | 06 | | | • Quality of Document - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Contents and Completeness - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Formatting and Indexing - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | | • QA Documentation | | 06 | | | • Quality of Document - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Contents and Completeness - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Formatting and Indexing - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | | • Software User Manual | | 06 | | | • Quality of Document - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Contents and Completeness - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Formatting and Indexing - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | | • Training Manuals etc | | 06 | | | • Quality of Document - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Contents and Completeness - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | • Formatting and Indexing - Above Average 02 Marks
- Average 01 Marks
- Below Average 0 Marks
| 02 | | | | | 10. Troubleshooting | | | | 15 | | • Error Handling | | | 05 | | | • Proper error display messages | | | 05 | | | • Help to avoid the error | | | 05 | | 11. Meeting of LRMIS Project Deadlines The Consultant(s) shall be judged against the following deadlines / milestones. On time completion shall be given 100 % Marks. No marks shall be given for delayed submission / missed deadlines | | | | 50 | | • Deliverables Time Plan | | | 50 | | | • Requirements Analysis | | 05 | | | | • Detailed Design | | 05 | | | | • Development | | 05 | | | | • System Integration | | 05 | | | | • QA Testing | | 05 | | | | • User Acceptance Test | | 05 | | | | • Deployment including Software and Hardware | | 05 | | | | • Training | | 05 | | | | • Data Entry | | 05 | | | | • Services and Maintenance | | 05 | | | | 12. Training | | | | 25 | | • Training Material | | | 10 | | | • Training Facilities | | | 10 | | | • Training as per user satisfaction | | | 5 | | | 13. Customer Service and Help | | | | 25 | | • Customer service / support during and after implementation | | | 15 | | | • Query response at all levels (i.e. Kiosk / Tehsil / District HQ Tehsil(s) / Provincial Data Center etc). | | | 10 | |
| Total: 600 Marks End notes (Criteria for Technical Evaluation included in RFP): - - Forms of electronic authentication could be public key infrastructure (PKI), biometric, security token or passwords. Message digest should be used for data verification and authenticity. Discretionary access control, Mandatory access control or Role-Based Access Control mechanism could be used as Access Control mechanism. The encryption technique used should be such that it is independent of the software/database used.
SrNo. | Forms | 1 | Mutation Registers | رجسٹرداخل خارج | 2 | Shajra Nasab Part (A) | شجرھ نسب حصھ (ا) | 3 | Shajra Nasab Part (B) | شجرھ نسب حصھ (ب) | 4 | Register Haqdaran Zamin Missal Haqiat | رجسٹرحقداران زمین مسل حقیت | 5 | Register Haqdaran Zamin Missal Miyadi | رجسٹرحقداران زمین مسل میعادی | 6 | Register Haqdaran Zamin Abadi | رجسٹرحقداران زمین آبادی | 7 | Fard Badar | فرد بد ر | 8 | Gardawari Register | رجسٹرگرداوری | 9 | Register Tagyarati Kasht Qabza Lagan Mahal | رجسٹرتغیرات قبضھ،کاشت ولگان محال | 10 | Field Book Mahal | فیلڈبک محا ل | 11 | Tatima Field Book | تتمہ فیلڈبک | 1 2 | Wajib-ul-Arz (Statement of customs) | واجب العرض | 1 3 | Kitab Karguzari Patwari | کتاب کارگزاری پٹواری | 1 4 | Interrogatories (Band Sawal) | بندسوال | 1 5 | Tatma Shajra | تتمہ شجرہ | 16 | Shajra Parcha | شجرہ پارچہ | 17 | Register Scheme | رجسٹرسکیم | 18 | Register Haqdaran Nakhlistan | رجسٹرحقداران نخلستان | 19 | Fard Taqseem-e-Aab | فردتقسیم اب | 2 0 | Naqsha Haqooq Chahaat-o-Nul Chahaat | نقشہ حقوق پن چکیات | 2 1 | Naqsha Haqooq Pan Chakyat (Water Mills) | نقشہ حقوق چاہات و نل چاہات | 2 2 | Index Survey / Khasra number | انڈکس سروے/خسرہ نمبران |
SrNo. | Reports | 1 | Mutation Registers | رجسٹرداخل خارج | 2 | Copy of Mutation order | جاری شدہ حکم براۓانتقال | 3 | Memoranda Invoice | چالان ہمراہ پرچہ یاداشت | 4 | Summary of attested mutations | منظورشدہ داخل خارج | 5 | Index Manzoor Shudah Dakhil Khiraj Mashmula Misal Haqiqat or Misal Miyadi | انڈکس منظورشدہ داخل خارج مشمولہ مسل حقیت و مسل میعادی | 6 | Register Haqdaran Zamin Missal Haqiat | رجسٹرحقداران زمین مسل حقیت | 7 | Register Haqdaran Zamin Missal Miyadi | رجسٹرحقداران زمین مسل میعادی | 8 | Register Haqdaran Zamin Abadi | رجسٹرحقداران زمین آبادی | 9 | Shajra Nasab Part (A) | شجرھ نسب حصھ (ا) | 10 | Shajra Nasab Part (B) | شجرھ نسب حصھ (ب) | 11 | Gardawari Register | رجسٹرگرداوری | 12 | Fard Badar | فرد بد ر | 13 | Register Jinswar | رجسٹرجنسوار | 14 | Receipts of Mutation fess | رسیدبراےوصولی فیس انتقال | 15 | Tatima Field Book | تتمہ فیلڈبک | 16 | Tatima Field Book Muraba Bandi | تتمہ فیلڈبک مربع بندی | 17 | Tatma Field Book Mustatiel Bandi | تتمہ فیلڈبک مستطیل بندی | 18 | Naqsha Kharaba | نقشھ خرابھ | 19 | Akhier Tasdiq Register Haqdaran Zamin | آحیر تصدیق رجسٹرحقداران زمین | 20 | Index Radiefwar Malikan and Marthehan | انڈکس ردیف وار ما لکان ومرتہان | 21 | Fard Badar | فرد بد ر | 22 | Index Survey/Khasra Numberan | انڈکس سروے/خسرہ نمبران | 23 | Mizan Safa-war Field Book | میزان صفحہ وار فیلڈبک | 24 | Note Kanungo and Revenue Officer Babat Partal-o-Tasdiq Misal Miyadi | نوٹ قانونگووریونیوافسربابت پڑتا ل وتصدیق مسل میعادی | 25 | Field Book Mahal | فیلڈبک محا ل | 26 | Note Tabdile Qisam Zamin | نوٹ تبدیلی قسم زمین | 27 | Roznamcha Waqiati | روزنامچہ واقعاتی | 28 | Register Scheme | رجسٹرسکیم | 29 | Register Haqdaran Nakhlistan | رجسٹرحقداران نخلستان | 30 | Fard Taqseem-e-Aab | فردتقسیم اب | 31 | Roubkar Ibtadiey | روپکارابتدائ | 32 | Naqsha Haqooq Chahaat-o-Nul Chahaat | نقشہ حقوق چاہات و نل چاہات | 33 | Parcha Khatauni | پرچہ کھتونی | 34 | Naqal Register Gardawari | نقل رجسٹرگرداوری | 35 | Aam Roznamcha Parat Patwar | عام روزنامچہ پرت پٹوار | 36 | Wajib-ul-Arz | واجب العرض |
- Data Entry Plan should include the number of machines, number of data entry operators used for data entry and estimated time required for data entry (Average transaction of each Kanungoi is ranges from 18,000 to 25,000).
- At application level, it is necessary to interconnect processes for the purpose of resource sharing with some sort of mechanism for communication.
- The application should use best practices and guidelines for multi tier development. The application should be accordingly divided into presentation, business, data access and services and data tier. Moreover, the application should be properly sub divided into modules such that they can operate within that system independently from the operations of the other components.
- 8. Time taken to retrieve and print 20 randomly selected Fards on a system with 20,000 owner records, 100,000 owner records, 1,000,000 owner records and 10,000,000 owner records. (We will have 20,000 entered records while the remaining loads will be generated using scripts). This will be conducted using a stress test technique involving up to 100 concurrent users
- 9. Time taken to replicate 1,000 entries at a Kiosk to the Tehsil, and 5,000 from Tehsil to District Data Center and 40,000 from District Data Center to Provincial Data Center. This will simulate the average daily expected load. Time taken to replicate 40,000 entries from multiple sources (minimum of 10 sources) to Provincial Data Center. This test will be performed with a data population of 100,000 at each source, and 1,000,000 at the Provincial Data Center. The test will use network connectivity with 99.9%, 95% and 90% availability to test the ability of the application to deal with varying line quality.
- 10. In this test a new server will be built with restore performed via replication from the Tehsil/ District HQ Tehsil(s).
- 11. Integrated backup management function will enforce a backup administration to be performed by the Kiosk operator. Backup will be managed to limit loss of data to a maximum of one shift.
- 12. Time taken to rebuild systems at the Kiosk, Tehsil and Provincial Data Center level with full synchronization across the hierarchy.
- 13. On a Kiosk with 20,000 records, 1,000 new transactions will be made and the same will then be rolled back. The resulting rolled back state will be compared with the original state of 20,000 records. The rolled back version of the 20,000 records must have a 100% match with the original state of the 20,000 records.
- 14. The system should be architected such that the design includes all of the hooks and mechanisms for expanding/enhancing the system with new capabilities without having to make major changes to the system infrastructure if required.
- 15. Traceability refers to the ability to link the requirements set forth at the beginning of the LRMIS project, to the corresponding design document, to the resulting software and associated test cases.
- 16. All the Deliverables should be according to Appendix E – Breakdown of Contract Price in Local Currency of Annex-I.
Financial Evaluation The evaluation of the financial proposal was to be done in accordance with the following formula: Financial Score = 400 x Fm / F, Fm is the lowest price and F the price of the proposal under consideration. |
| | Back to Top | 15. Why were only three firms technically evaluated out of the four which were originally selected for the competition? | | One of the firms i.e. Descon IT24 submitted their deliverables upto “System Integration and QA Testing” phase. While the three remaining firms were able to pass User Acceptance Testing after three (for AOS and Netsol) and four (for Techlogix) iterations, Descon IT24 did not participate in the testing process after the first iteration. In view of this they were issued notices by PITB for fulfillment of their obligations and consequent to their failure to do so, contract with them was terminated after no-objection from the World Bank. Since this firm did not complete the entire cycle and since contract with them had been terminated, they were not a part of the final technical evaluation. |
| | Back to Top | 16. Who conducted the technical evaluation of the three software products? | | Technical evaluation was conducted on the basis of the criteria mentioned above by an independent third party. M/S Sidat Hyder Morshed were selected as the independent third party. |
| | Back to Top | 17. What were the results of the technical evaluation? | The three competing firms scored following marks as reported by the third party
| | Name of the firm | Technical Score out of 600 | | 1 | Accountancy Outsourcing Services (Pvt.) Ltd. | 440.86 | | 2 | NetSol Technologies (Pvt.) Ltd. | 424.42 | | 3 | Techlogix Pakistan (Pvt.) Ltd. | 336.67 |
|
| | Back to Top | 18. Who conducted the financial evaluation? | | Financial evaluation consisted of public opening of financial proposals and then applying the preannounced formula to the financial proposals. This was done by a committee consisting of representatives of Finance Department, P&D Department and the PMU-Board of Revenue. |
| | Back to Top | 19. What were the combined results of the technical and financial evaluation? | | | Name of the firm | Technical Score out of 600 | Financial Score out of 400 | Total Score out of 1000 | | 1 | Accountancy Outsourcing Services (Pvt.) Ltd. | 440.86 | 400 | 840.86 | | 2 | NetSol Technologies (Pvt.) Ltd. | 424.42 | 63.63 | 488.05 |
|
| | Back to Top | |
|
|
|
|
|
|
|
|
|
News & Updates |
|
|
|
|
|
-
Service Centre for seven villages of Kasur operational (3rd May, 2010)
-
First three live mutations recorded at Kasur Service Centre (15th June, 2010)
-
-
-
-
-
-
-
-
-
-
-
-
A Small Pilot for Mustafabad Kanungoi to be Established in Kasur (31th December, 2009)
-
Test Data Entry Lab setup in PMU
|
|
|
Quick Links |
|
|
|
|
|
|
|
|