REQUEST FOR PROPOSAL

Development of Android
Applications
forKaAsenso

1.INTRODUCTION
1.1.Background
KaAsenso empowers and enables micro-businesses (or mini-negosyos) with
the right tools and programs to help them progress into sustainable and
profitable enterprises. One of the offerings of KaAsensoare the PLDT Telpad
Plans. A Telpad plan comes with a landline service, which is incorporated on
a tablet dock, a tablet unit telpad which runs on Android OS and DSL
Internet connectivity. The Telpadunit can be used by the negosyante as a
tool for their small business. PLDT plans to provide productivity applications
or apps to exclusive KaAsenso subscribers by offering it through knAPPsack
application installer (pre-installed on all Telpad units).
1.2.Objectives
1.2.1 To develop productivity applications that will be used on PLDT Telpad
units running android operating system.
1.2.1. These applications will be distributed exclusively for KaAsenso
customers only.
1.3.Scope
1.3.1. Scope of this document will cover PLDT requirements only.

2.TECHNICAL REQUIREMENTS
2.1.All applications will be distributed by PLDT.
2.2.The applications should work on a stand-alone mode, all components
(database, etc.) should be locally contained on the device.
2.3.The applications should be designed and optimized to run on devices
(tablets, phablets, mobile) running Android operating system environment
starting with Gingerbread version onwards.
2.4.The applications should be compatible with future android OS and/or OS
related feature upgrades.
2.5.The applications should be optimized/adapt to different screen resolutions
and tablet screen orientation.
2.6.The applications should be able to handle updates for new features, bug
fixes, version upgrades.
2.7.A server application with CMS should also be developed to handle the
following:
2.7.1. Controlling the content in the splash page
2.7.2. To poll the usage of the applications and provide statistics for reports
2.8.Each application should include an error or bug report log that will be
forwarded to the server application and can be accessed via the CMS and/or
set to be emailed to a defined email address.

3.FEATURE REQUIREMENTS
- Initial state of each application is
-

basic version. To activate to full

version you need to supply the activation key.
Management and validation of activation keys are stored on the server.
Applications will connect to the server to validate the supplied key.
When authenticated, all functionalities will be activated.

3.1.
SALES AND EXPENSE TRACKER
3.1.1.BASIC VERSION (limited to 50 items only)
3.1.1.1. Capable to generate quotes and invoices.
3.1.1.2. Capable of adding multiple products and/or services as line
items.
3.1.1.3. Capable of setting the credit status, add discounts and taxes.
3.1.1.4. Generate reports on a daily reports only
3.1.1.5. All generated reports, invoices, expense, quotations should be
capable of saving the output to a PDF file format
3.1.1.6. Monitor status of open or pending quotes and invoices.
3.1.1.7. Manage an internal customer list for quotation and invoice
generation
3.1.1.8. User definable expense categories
3.1.1.9. Capable of detecting application updates for bug fixes, new
features , etc.
3.1.1.10.
Capable of displaying advisories, application tips and
tricks or information updates to users on its splash page.
3.1.2.FULL VERSION
3.1.2.1. Capable to generate quotes and invoices.
3.1.2.2. Capable of adding multiple products and/or services as line
items.
3.1.2.3. Capable of setting the credit status, add discounts and taxes.
3.1.2.4. Basic customization of invoices and quotes by inserting
Company Logo and signatures as picture files into Quotes and
Invoices.
3.1.2.5. Generate reports on a specific duration (daily, weekly, monthly,
summary, etc.)
3.1.2.6. All generated reports, invoices, expense, quotations should be
capable of saving the output to:
3.1.2.6.1.1.
PDF file format.
3.1.2.6.1.2.
Export to CSV data format.
3.1.2.7. Monitor status of open or pending quotes and invoices.
3.1.2.8. Manage an internal customer list for quotation and invoice
generation
3.1.2.9. Option to select customers from system Contact list.
3.1.2.10.
Capable of doing duplicate quotes to reuse with multiple
customers

3.1.2.11.
Search functionality for both sales and expense records
3.1.2.12.
Tabulate daily expenses as purchases, mileage and rents
3.1.2.13.
Categorize and sort expenses
3.1.2.14.
Automate recurring expenses
3.1.2.15.
User definable expense categories
3.1.2.16.
Access restrictions by setting password protection.
3.1.2.17.
Backup/Restore functionality, storage can be either SD
Card, send to email or online storage (Dropbox, etc.)
3.1.2.18.
Capable of detecting application updates for bug fixes,
new features , etc.
3.1.2.19.
Capable of displaying advisories, application tips and
tricks or information updates to users on its splash page.
3.2.
INVENTORY MANAGEMENT
3.2.1.BASIC VERSION (limited to 50 items only)
3.2.1.1. Product Management (basic information price, cost, quantity,
photo, description, category, reorder limit, etc.)
3.2.1.2. Cost and Pricing Management
3.2.1.3. Transaction records
3.2.1.4. Stock on hand balance
3.2.1.5. Re-order level alert advisory/report
3.2.1.6. All generated reports, should be able capable of saving the
output to PDF file format
3.2.1.7. Capable of detecting application updates for bug fixes, new
features , etc.
3.2.1.8. Capable of displaying advisories, application tips and tricks or
information updates to users on its splash page.
3.2.2.FULL VERSION
3.2.2.1. Product Management (basic information price, cost, quantity,
photo, description, category, reorder limit, etc.)
3.2.2.2. Cost and Pricing Management
3.2.2.3. Transaction records
3.2.2.4. Stock on hand balance
3.2.2.5. Re-order level alert advisory/report
3.2.2.6. Quickly make transactions by scanning product barcodes
3.2.2.7. All generated reports, should be able capable of saving the
output to :
3.2.2.7.1.
PDF file format
3.2.2.7.2.
Export to CSV data format.
3.2.2.8. Output can be stored in SD, send via email, or online storage
(Dropbox, etc.)
3.2.2.9. Access restrictions by setting password protection.
3.2.2.10. Backup/Restore functionality, storage can be either SD Card,
send to email or online storage (Dropbox, etc.)
3.2.2.11. Capable of detecting application updates for bug fixes, new
features , etc.
3.2.2.12. Capable of displaying advisories, application tips and tricks or
information updates to users on its splash page.

3.3.
PAYROLL
3.3.1. BASIC VERSION (limited to 5 employees only)
3.3.1.1. Basic employee profile management
3.3.1.2. Tracking of daily time records
3.3.1.3. Automatic computation of basic salary, overtime, and basic
deductions
3.3.1.4. Monthly and yearly summary reports
3.3.1.5. Generate payslips
3.3.1.6. All generated reports, payslips should be able capable of saving
the output to a PDF file format
3.3.1.7. Capable of detecting application updates for bug fixes, new
features , etc.
3.3.1.8. Capable of displaying advisories, application tips and tricks or
information updates to users on its splash page.
3.3.2. FULL VERSION
3.3.2.1. Employee profile management (photo and employee details)
3.3.2.2. Tracking of daily time records
3.3.2.3. Automatic computation of basic salary, overtime, and basic
deductions
3.3.2.4. Monthly and yearly summary reports
3.3.2.5. Generate payslips
3.3.2.6. All generated reports, payslips should be able capable of saving
the output to:
3.3.2.6.1.
PDF file format
3.3.2.6.2.
Export to CSV data format.
3.3.2.7. Output can be stored in SD, send via email, or online storage
(Dropbox, etc.)
3.3.2.8. Access restrictions by setting password protection.
3.3.2.9. Backup/Restore functionality, storage can be either SD Card,
send to email or online storage (Dropbox, etc.)
3.3.2.10. Capable of detecting application updates for bug fixes, new
features , etc.
3.3.2.11. Capable of displaying advisories, application tips and tricks or
information updates to users on its splash page.
3.4.
BASIC POINT OF SALE (POS) SYSTEM
3.4.1. BASIC VERSION (maximum of 20 product/service entries)
3.4.1.1. Basic inventory system (Add a name, price and a photo for each
product)
3.4.1.2. Input sales with option to note tax and discounts
3.4.1.3. Barcode reader integration
3.4.1.4. Daily, summary reports capable of saving the output to PDF file
format

3.4.1.5. Capable of detecting application updates for bug fixes, new

features , etc.
3.4.1.6. Capable of displaying advisories, application tips and tricks or
information updates to users on its splash page.
3.4.2. FULL VERSION
3.4.2.1. Capable of linking Inventory System or have its own basic
inventory system
3.4.2.1.1.
Classify products by categories and with a specific color
3.4.2.1.2.
Add a name, price and a photo for each product
3.4.2.2. Input sales with option to note tax and discounts
3.4.2.3. Barcode reader integration
3.4.2.4. Daily, weekly, monthly and yearly summary reports capable of
saving the output to :
3.4.2.4.1.
PDF format
3.4.2.4.2.
Export to CSV data format.
3.4.2.5. Output can be stored in SD, send via email, or online storage
(Dropbox, etc.)
3.4.2.6. Access restrictions by setting password protection.
3.4.2.7. Backup/Restore functionality, storage can be either SD Card,
send to email or online storage (Dropbox, etc.)
3.4.2.8. Capable of detecting application updates for bug fixes, new
features , etc.
3.4.2.9. Capable of displaying advisories, application tips and tricks or
information updates to users on its splash page.

4.PROJECT REQUIREMENTS
4.1Request for Proposal Process
4.1.1 Confidentiality
4.1.1.1 PLDT requests that the contents of this DOCUMENT and any
other information obtained through discussions with the companys
personnel (in relation to this DOCUMENT), pursuant to the receipt of
this DOCUMENT and/or during and following the response period,
remain strictly confidential and are not disclosed to any third party
without the prior written consent of the PLDT Contact.
4.1.1.2 All information provided by you will be treated as Commercial in
Confidence by PLDTand will not be disclosed to a third party
without your written permission
4.1.2 Vendor Confidentiality
4.1.2.1 Respondents shall not disclose to any third party, except to
those directly involved in making their bid, nor publicize in anyway
the existence, details, invitation to participate and participation in
this proposal. This restriction remains in force, for both successful
and unsuccessful respondents, for a period of 3 years from date of
submission of the Request for Proposal. Proposals from
respondents who breach this clause shall at the companys sole
discretion be excluded from consideration.
4.1.3 IT Security Principles
4.1.3.1 The respondent (and any of its subsidiaries, sub-contractors or
partners) engaged on this project shall agree to abide by PLDT IS
Security Principles and operate within its guidelines at all times.

4.1.4 Warranties & Representations

4.1.4.1 Nothing in this document or any other communication made
between PLDT and the respondent shall be taken as constituting a
contract or representation binding on PLDT and nor shall it be
taken as constituting an agreement or representation that a
contract shall be offered, awarded or entered into. PLDT also
reserves the right to discontinue the RFP process at any time.
4.1.4.2 PLDT does not bind itself to accept any proposal submitted as a
result of the RFP, nor to accept any alternative proposals made by
the respondent nor to enter into any contract as a result of this RFP,

irrespective of whether the evaluation criteria are met in full or

otherwise.
4.1.5 Contact for the RFP process
4.1.5.1 The project organizer shall be the primary contact for all queries
and clarifications. The other listed personnel shall be available
should the primary contact be unavailable during regular business
hours.

Procurement Team (Primary Contacts)

Tina Chan
Email:

CPChan@pldt.co.pmh

Carlito Angelo
Email:

CACAngelo@pldt.com.ph

Gunther S. Guia
Email:

GSGuia@pldt.com.ph

Dan Pis-an
Email :DLPis-an@pldt.com.ph

4.1.6
Disclaimers
4.1.6.1 PLDT reserves the right for the following:

4.1.6.1.1 Change or modify the details within the RFP prior to

submission
4.1.6.1.2 Cancel future phases of the project for any reason
4.1.7 Submission of Request for Proposal
4.1.7.1 Commercial Pricing and Price Breakdown
4.1.7.1.1 The bid submission shall provide project cost quotations for
outright purchase. Include as an option, the cost of the
source-code.
4.1.7.2

Company Profile

4.1.7.2.1 The company profile shall not only present the company
information and history but also summarize the relevant
capabilities, experience & qualifications of the respondent
and its sub-contractors. The summary shall include:

4.1.7.2.2 Company history

4.1.7.2.3 Details of size and organization for carrying out the design,
implementation and continued support
4.1.7.2.4 Details on key partnerships and alliances that are relevant to
this RFP
4.1.7.2.5 Personnel directly or indirectly attached to the project with
particular reference to relevant skills and expertise
4.1.7.2.6 A reference of implemented projects describing approximate
scope (size, complexity, duration and value) using the
proposed system
4.1.8 Proposal Documentation
The RFP format should contain the following sections:
4.1.8.1.1 Executive Summary
4.1.8.1.2 Company profile
4.1.8.1.3 Statement of Work
4.1.8.1.4 Project Plan, Project resources, Test Plan, Implementation
Plan
4.1.8.1.5 System architecture and diagrams
4.1.8.1.6 Warranty and support information
4.1.8.1.7 Training information
4.1.8.1.8 References
4.1.8.1.9 Commercial proposal
4.1.8.1.10
4.2

Compliance Checklist (see appended excel file for format)

Scope of Work

4.2.1 Commercial Requirements

4.2.1.1 Proposed project cost shall be on an outright purchase model.
4.2.1.2 Proposed project cost shall be inclusive of all applicable licensing
fees
4.2.1.3

Respondent shall have local presence and support

4.2.2 Technical Requirements

4.2.2.1 The request for proposal document shall contain all functional
and non-functional requirements stated in sections 2 & 3 of this
document.
4.2.3 Warranty & Support
4.2.3.1 The Respondent shall provide the following warranty and
support:
4.2.3.2 A 1 (one) year warranty period from the date of commissioning
and shall rectify any faults that might occur within the period
without any charges to the PLDT
4.2.3.3 A local 24/7phone/e-mail support shall be available for issue
resolution.
4.2.3.3.1 Capability to provide timely support on possible identified
issues and/or severity level
4.2.3.3.2 Listing of possible issues & severity level to be presented
according to the following matrix: Severity Level, Availability,
Response Time, Restore Time, and Permanent Solution.
4.2.3.3.3 Listing of Response, Resolution & Escalation time according
to the following matrix: Escalation Points, Failure or Issue
Type, 1st Escalation time & contact, 2nd escalation time &
contact
4.2.3.4 Software support for 2 years shall include patches, updates and
new versions
4.2.3.5 The respondent shall also include a section on post warranty
support and costs for budgetary requirements. Although not a
critical part of the bid submission, PLDT requires a cost related to
continued annual product support for up to 3 years.
4.2.4 Documentation
4.2.4.1 As part of the deliverables, the respondent shall provide
documentation of each application. This will include the features
and description, transaction flows, how-to use guide.