BID BULLETIN NO. 1

This is to notify bidders of the amendments/clarifications in the Terms of Reference (TOR) and Instructions to Bidders (ITB) as discussed during the pre-bid conference conducted on January 19, 2010 at the Resource Center Conference Room, 6^th Floor, SSS Building, Ayala Avenue corner V. A. Rufino St., Makati City:

1. Terms of Reference:

   1. Section V.A.9, page 5

      1.1 The demonstration mentioned maybe in the form of an operational site (existing user reference site) or a demo/prototype system installed at the work area of the bidder.

      1.2 The 6-second requirement is reiterated.

      1.3 The demonstration shall only be required from the lowest responsive bidder. If they fail, then the next lowest responsive bidder will be required to do the same.

   2. Section V.B.5, page 7

      It is preferred that the reporting tool to be packaged with the software proposal should be of the same brand as the software proposal. However, if the proposed reporting tool will be a third party solution, then two licenses should be included on top of the required licenses as specified in Annex A of the TOR.

   3. Annex A of TOR – Software Licenses

      The 10 licenses for Viewer/Auditors are read-only licenses for the use of auditors and management, while the 18 Makers/Reviewers/Approvers are for the use of PDIC users who will directly transact with the system.

   4. Section V.C.1, page 7

      4.1 PDIC uses Microsoft 2003 Active Directory of Microsoft. Currently, we are still employing Multiple Sign-on authentication where a user is prompted for another username and password during logging-on into a system. However, the said username and password should be synchronized with the Active Directory account.

      4.2 PDIC should have the option to implement a Single Sign-on authentication where upon logging on to Windows, users should be able to access the systems already without prompting for another username and password. Username and passwords, including user access rights and credentials, shall be integrated with Active Directory. Any software and licenses needed for the implementation shall be included and should be for the account of the bidder.

   5. Section E.1 – System Service/Warranty, page 12

      The warranty for the implemented software shall cover program bugs, configuration errors or implementation concerns that are part of the deliverables under the TOR of this project.

   6. Section E.2 – System Service/Warranty, page 12

      6.1 Software

      The 24/7-support infrastructure refers to a helpdesk available to clients seeking solutions to system related concerns. However, support from the winning vendor will still be the default channel in relaying and resolving said concerns as detailed in item 5.

      6.2 Hardware

      The warranty shall be a three-year standard warranty. However, during emergencies or highly meritorious cases, PDIC may request the winning bidder for support even outside of business hours.

   7. Section E.3 – System Service/Warranty, page 12

      The provision of technical support of two days per month for one year is intended for new requirements six months after acceptance/go-live. The equivalent of 24 man-days may be spent consecutively to address new requirements as long as it is within the one-year period.

   8. Section D.1 – page 8

      The current implementation of the PDIC relative to its storage device is SAN (HP MSA 2000).

   9. Report formats as discussed during the Pre-Bid Conference will be available starting January 22, 2010. Please contact our BAC Secretariat for details.

   10. Section VII

       The table below provides the detailed payment schedule for the project subject to the provisions of RA 9184. Further, to better operationalize the payment schedule, Bid Form No. 6 (Annex A) is being introduced which shall form part of the bid documents.

       Task	Deliverables	Contract Value	Progress Billing
       1. Acquisition and customization of an Integrated Financial System called the IFS	DELIVERY OF HW & SW
       	Delivery, installation and commissioning of all hardware components, as specified in the TOR.	Cost of hardware component (Item A Financial Proposal)	100% of contract value upon delivery and installation
       	Delivery and installation of all software components, as specified in the TOR.	Cost of software component (Item B Financial Proposal)	70% of contract value upon delivery and installation
       	IMPLEMENTATION
       	IFS configured, customized and ready for testing.(Certification of system ready for testing)	Cost of implementation component (Item C Financial Proposal)	30% of contract value of implementation
       	IFS accepted, tested and installed in the production sever as per specifications of the TOR.(Certification of systems acceptance signed by project team)		40% of contract value of implementation30 % of contract value of software component
       	Migration of applicable data from existing systems as agreed with the PDIC as per section IV-B of this document		10% of contract value of implementation
       	Documentation		10% of contract value of implementation
       	Training of users and technical staff		10% of contract value of implementation

       
       

   11. Section IV-B

       11.1 Investments

       Only “open” or live investment transactions/records shall be migrated in the new system.

       11.2 Financials

       The beginning balances to be setup in the system are as of December 31, 2009. Transactions starting January 2010 shall be migrated in the new system.

   12. Section V.B.2 – TIMS

       The Bloomberg/other data provider connectivity refers to the capability of the proposed system to connect/interface to a data provider. The subscription fees to said data provider shall be for the account of PDIC.

   13. Section V.A.10

       Licenses for the proposed database management system (DBMS) shall be for the account of the bidder. The type of licenses for the DBMS shall ensure that configuration/changes in the database will be allowed for purposes of addressing future requirements of end-users.

   14. Section V.D.1 and V.D.2

       The CPU for the production and development servers as clarified mean, at least two Quad Core Intel CPUs. Additional specifications are reflected in the section provided.

   15. Section V.D

       All hardware specifications defined are the minimum requirements. Bidders proposing for hardware with higher specifications are welcome in the interest of providing the best solution for this project and/or to be at par with the latest available technology in the market.

   16. Sizing requirements of bidders

       The bidders requested to undertake a “sizing activity” to better estimate the “right” hardware that will be included in their respective proposals. The said activity shall be undertaken by the bidder’s provision of a Sizing Form/Questionaire to be filled-up/answered by PDIC.

       The form shall be emailed to rdantonio@pdic.gov.ph. Bidders were also requested to send the forms as soon as possible.

   17. Annex B1 nos. 11-12, page 15

       The budget facility mentioned is not the full-blown implementation of the budget module. Items 11 and 12 are reiterated and shall still form part of the deliverables. It refers to the monitoring of budget utilization.

       Further, the items also intend to make the bidders appreciate PDIC’s requirement of “responsibility accounting”.

   18. Annex B2 no. 5, page 18

       The various sources mentioned may mean an existing production system such as PDIC’s Claims System and MS Excel files for PDIC loan receivables. Uploading shall be on a per transaction basis i.e. per bank, per branch for claims paid by the corporation and per account for loan receivables. The vendor shall provide the file format acceptable to the proposed solution, preferably in MS Excel or text format.

       The volume of the data to be uploaded shall be addressed by the sizing activity as per item 16 of this document

2. Instructions to Bidders

   As provided under Sec. 22 b) of the IRR of RA 9184, the Joint Venture Agreement (JVA) shall be submitted in case the joint venture is already in existence. In the absence of a JVA, duly notarized statements from all the potential joint venture partners stating that they will enter into and abide by the provisions of the JVA in the instance that the bid is successful shall be included in the submission of documents. Failure to enter into a joint venture in the event of a contract award shall be ground for the forfeiture of the bid security.

   A Filipino corporation may form a joint venture with a foreign corporation. Provided, that the Filipino ownership/interest in the joint venture shall be at least sixty percent (60%). For this purpose, Filipino ownership/interest shall be based on the capital ownership or contributions of each of the members of the joint venture as specified in the JVA.

   Each partner of the joint venture shall submit the legal eligibility documents, i.e. Securities and Exchange Commission (SEC) or Department of Trade and Industry (DTI) or Cooperative Development Authority (CDA) Registration, and Municipal License/Mayor’s Permit. If a partner of the joint venture agreement is a foreign corporation, said foreign corporation may substitute the DTI/SEC/CDA Registration and Municipal License/Mayor’s Permit with the appropriate equivalent document if any, issued by the country of the said foreign corporation. In case the equivalent document is in another foreign language, a translation of said documents in English certified by the appropriate embassy or consulate in the Philippines must be attached to the documents.

   The submission of the other eligibility, technical and financial documents by any of the joint venture partners constitutes compliance.

January 21, 2010