ADDENDUM NO. 1. Date: November 5, 2012 For RFP No. 301D

Transcription

1 ADDENDUM NO. 1 Date: For RFP No. 301D Enterprise Finance, Human Resources and Payroll Software and Related Services General-All project documents shall remain unchanged with the exception of those elements added, revised, deleted, or clarified by written addendum. Page 1 of 6

2 CONTENTS ADDENDUM ITEMS INDEX PAGE 1 Table of Contents 1-1 General Conditions Questions and Answers... 3 Page 2 of 6

3 1-1 Questions and Answers Q1: Please explain the expectations around the level of integration that SOCCCD expects through the Portal solution specified in the RFP (Critical Criteria for Proposed Software question 3). More specifically, what is SOCCCD s present/future plans for the current SharePoint platform with regards to its portal capabilities? Is SOCCCD assuming the implementation of an Identity Provider (IdP) solution as part of this project to enable SSO? What type of Single Sign-On technology/capabilities does SOCCCD plan to leverage in order to provide SSO access to ancillary third-party solutions? A1: SOCCCD requires that the solution be delivered through a portal. For example, upon logging into the portal, a user would have access to all capabilities appropriate to their role. The vendor s portal must support Active Directory (AD) authentication, which is the SOCCCD standard. SOCCCD currently has the MySite Student Information System portal and SharePoint intranet portal, both of which use AD authentication. SOCCCD has not yet implemented a single signon (SSO) solution. We will most likely implement SSO in the future, using AD as the source of authentication. SOCCCD is looking for a solution that will be flexible enough to participate in a variety of possible future SSO open standard solutions. Please describe the SSO support provided in your product. Q2: Please explain the relevance of server side hardware/software technology questions (General Technical Information questions 1-4) with regards to the evaluation of the RFP responses if you are considering a SaaS solution. The assumption is made here that the server-side platform technical requirements will be owned by the cloud solution provider to track, manage and maintain and will become transparent to SOCCCD in a multi-tenant SaaS environment if positioned as a SaaS solution A2: The District is exploring all options with regards to solutions some of which do not offer a SaaS solution. Therefore we have requested this technical information. If your solution is offered only in a SaaS model then the following response would be an acceptable answer to the question: Server-side platform technical requirements will be owned by the cloud solution provider to track, manage and maintain and will become transparent to SOCCCD in a multi-tenant SaaS environment if positioned as a SaaS solution. Page 3 of 6

4 Q3: Is it the intention of the district to continue the use of its internally developed MIS/320 State reporting system? A3: Yes however we would expect that information from the any new Finance and HR/Payroll solutions would be able to feed data to our existing reporting systems where relevant to this reporting. Q4: Please clarify if we are mailing our proposal response that it should be directed to the point of contact and information in the mailing address or the place of bid receipt? A4: Proposals should be sent to the place of bid receipt as outlined in the RFP Instructions and Requirements Section: Submittal Deadline: 2:00 PM, Tuesday, November 27, 2012 Place of Bid Receipt: Mailing Address: SOCCCD Facilities Planning and Purchasing Department Saddleback College Third Floor, Heath Sciences Building Marguerite Parkway Mission Viejo, CA Attn: Brandye D Lena Executive Director of Facilities Planning and Purchasing Marguerite Parkway Mission Viejo, CA Proposals will be received up to the above-indicated time and date. Late proposals will not be accepted and will be returned unopened. Proposals may be delivered in person, by U.S. mail, or courier services. Fax proposals are not acceptable. Proposals must be submitted in an envelope plainly marked with the following information: Enterprise Finance, Human Resources and Payroll Software (SOCCCD #301D) Q5: Does the district currently use procurement cards? A5: No, however, we expect to be starting a pilot project by the end of this fiscal year. We expect to have a full roll-out of our procurement card implementation after a one year pilot program period. Page 4 of 6

5 Q6: If the district does currently use procurement cards, will this functionality need to be included? A6: We want to integrate procurement card program with any new system. Q7: Can you provide an idea of how many levels of approval maximum will be required for requisition processing? A7: We do not know how many approval levels will be required for requisition processing yet. Along with the selection of a new system, we are undergoing business process analysis to streamline existing processes. We are making our current procedures more efficient and user-friendly, so expect to decrease the number of approval levels. Our expectation would be that the ideal solution would provide for as many levels of approval as would be required. Q8: Does the district encumber funds at the time of requisition? A8: Yes the current system encumbers fund at the time the requisition is submitted. Q9: Is there currently a training department or resource within the district that will assist in the coordination and deployment of any training initiatives? A9: There is currently no training department or resource available within the district to provide training coordination and deployment of training initiatives. Decisions on the provision of these services will be considered later in the process. Q10: In the SOCCCD RFP, is Section 17, Contact Information Page a continuation of Section 17, Client References? A10: No this section should be relabeled Section 18, Contact Information Page Q11: If yes, does SOCCCD require the requested contact information for each of the Client References? A11: See response to Question 10 above. Page 5 of 6

6 Q12: If no, should Section 17, Contact Information Page be labeled Section 18 in the Vendor s RFP Response? A12: Section 17, Contact Information Page should be relabeled Section 18 in the Vendor s RFP Response? Q13: Is the electronic version of our signatory s longhand signature acceptable to SOCCCD for the Affidavit of Non-Collusion form? A13: Yes an electronic version is acceptable to SOCCCD. Page 6 of 6