State of California Arnold Schwarzenegger, Governor State and Consumer Services Agency DEPARTMENT OF GENERAL SERVICES ADDENDUM #02 TO RFP DPR

Size: px

Start display at page:

Download "State of California Arnold Schwarzenegger, Governor State and Consumer Services Agency DEPARTMENT OF GENERAL SERVICES ADDENDUM #02 TO RFP DPR"

Marianna Gallagher
6 years ago
Views:

State of California Arnold Schwarzenegger, Governor State and Consumer Services Agency DEPARTENT OF GENERAL SERVICES Procurement Division 707 Third Street West Sacramento, CA 95605 (916) 375-4400 Fax

1 State of California Arnold Schwarzenegger, Governor State and Consumer Services Agency DEPARTENT OF GENERAL SERVICES Procurement Division 707 Third Street West Sacramento, CA (916) Fax (916) ADDENDU #02 TO RFP DPR REQUEST FOR PROPOSAL DEPARTENT OF PARKS AND RECREATION PUBLIC SAFETY TECHNOLOGY ODERNIZATION (PST) NOTICE TO PROSPECTIVE BIDDERS December 24, 2008 TO ALL INTERESTED BIDDERS: Re: REVISED RFP DPR Addendum # 2 Based on questions submitted by bidders and to provide additional information and clarification the State has amended the original RFP DPR The attached RFP DPR Addendum # 2 replaces the original RFP DPR in its entirety. Bidders are instructed to base their bid on the information contained in the attached RFP DPR Addendum # 2. Attachment # CL1 (Contains a list of all changes to the original RFP DPR ) Attachment RFP DPR Addendum # 2 (Complete Revised RFP) If you have any questions, please call me at or me at dennis.link@dgs.ca.gov. Regards, ORIGINAL SIGNATURE ON FILE Dennis W. Link, S-CIS, PP Department of General Services Procurement Division 707 Third Street, S West Sacramento, CA dennis.link@dgs.ca.gov (916) (916) FAX BUILDING GREEN BUYING GREEN WORKING GREEN

2 1 I.E Updated Dennis Link s phone number 2 I.G Clarify Last Day to Request s to Contract Language 3 I.G Updated date for Draft Proposal Submission Correction Clarify the last day to submit changes to contract language. A Last Day to Request a in Requirements Updated dates. 5-Feb-08 February Last Day to Request a in Requirements and Last Day to Request a to Contract Language 4 II.C.2.d Replace reference to Conceptual and Detailed Technical Proposals with draft proposal. Clarify the conceptual and detailed technical proposals are not applicable to this procurement. In accordance with the discussion agenda, the evaluation team will meet with each bidder for the purpose of discussing the Conceptual Proposal or Detailed Technical Proposal (as the case may be) in detail. In accordance with the discussion agenda, the evaluation team will meet with each bidder for the purpose of discussing the Draft Proposal in detail. 5 II.C.2.f Replace reference to Conceptual and Detailed Technical Proposals with draft proposal. Clarify the conceptual and detailed technical proposals are not applicable to this procurement. If, after full discussion with a bidder, the State is of the opinion that the bidder's proposal (Conceptual Proposal or Detailed Technical Proposal, as the case may be) cannot be restructured or changed in a reasonable time to satisfy the needs of the State, If, after full discussion with a bidder, the State is of the opinion that the bidder's proposal (Draft Proposal ) cannot be restructured or changed in a reasonable time to satisfy the needs of the State, Page 2 of 19 Type of (A Add, odify, D Delete)

3 6 II.C.2.g Replace reference to Conceptual and Detailed Technical Proposals with draft proposal. Clarify the conceptual and detailed technical proposals are not applicable to this procurement. If, at the conclusion of the Confidential Discussion, the State determines that required and agreedto changes can only be fully confirmed through the submission of an amended proposal (Conceptual Proposal or Detailed Technical Proposal, as the case may be), the State may require the submission of an addendum consisting only of those pages which were in doubt or a complete resubmittal. If, at the conclusion of the Confidential Discussion, the State determines that required and agreed-to changes can only be fully confirmed through the submission of an amended proposal (Draft Proposal ), the State may require the submission of an addendum consisting only of those pages which were in doubt or a complete resubmittal. 7 II.E.1 Remove the blank so that it is clear when the protest must be received. The selection protest must be received the day after the Intent to Award. A written Notice of Intent to Protest the proposed award of this solicitation must be received (facsimile acceptable) by the Coordinator before the close of business 5 p.m. PST/PDT on the day after issuing the notice of intent, as specified in the solicitation. A written Notice of Intent to Protest the proposed award of this solicitation must be received (facsimile acceptable) by the Coordinator before the close of business 5 p.m. PST/PDT on the first day after issuing the notice of intent, as specified in the solicitation. 8 IV.C.2.e Removed reference to a CAD reporting tool component. This reference is no longer necessary. New reports defined either through the CAD component or a third-party reporting tool will be stored as a standard report available through the CAD component. New reports defined through a third-party reporting tool will be stored as a standard report available through the CAD component. Page 3 of 19 Type of (A Add, odify, D Delete)

4 9 IV.C.5 Remove reference to AFIS, Livescan, DV Photo DB, DAs, courts, jail, and Resource Scheduling System V.C.1.f From bidder change request CR2-11 AFIS and fingerprinting is not allowed by the State of California; DV does not permit a direct link to their system; there is no current resource scheduling system to interface to (this may be part of a bidder's system). There will not be an interface to the district attorneys, courts or jails. Allow bidders to provide proof of insurance. D < See original version > See Addendum 2.. A valid General Liability Insurance Policy in the amount of at least $1,000,000 for the Bidder and all Subcontractors must be included in the Draft and Final Proposals. Bidders must provide proof of General Liability Insurance Policy in the amount of at least $1,000,000 for the Bidder and all Subcontractors must be included in the Draft and Final Proposals. Proof must indicate the insured s name, issuing agent/company, policy limit, an indication that the policy is for liability insurance, and the effective dates of the policy. Page 4 of 19 Type of (A Add, odify, D Delete)

5 V.C.1.g From bidder change request CR2-12 Allow bidders to provide proof of insurance. A valid Workers Compensation Insurance Policy in the amount of at least $1,000,000 for all Bidder and Subcontractor employees proposed in the performance of these Contracts must be included in the Draft and Final Proposals. Bidders must provide proof of Workers Compensation Insurance Policy in the amount of at least $1,000,000 for all Bidder and Subcontractor employees proposed in the performance of these Contracts must be included in the Draft and Final Proposals. Proof must indicate the insured s name, issuing agent/company, policy limit, an indication that the policy is for Workers Compensation Insurance, and the effective dates of the policy. 10 V.C.1.h AR 15: 500 mobile units to 50; and remove requirement for multiple dispatch centers. 11 V.C.1.i.2 AR 18: reference from draft schedule to Proposed schedule This will eliminate too many vendors. Clarify that the schedule is the proposed version. 2) the Customer has at least 500 mobile units; 3) the Customer operates and must coordinate operations between at least two (2) dispatch/communications centers The Bidder must commit to the continuing availability of the Key Personnel, to the extent of the Bidder s control, for the duration of the project or for their proposed period of involvement (as defined in the Draft Project Schedule). 2) the Customer has at least 50_ mobile units; 3) DELETED The Bidder must commit to the continuing availability of the Key Personnel, to the extent of the Bidder s control, for the duration of the project or for their proposed period of involvement (as defined in the Proposed Project Schedule). Page 5 of 19 Type of (A Add, odify, D Delete)

6 12 V.C.2.b AR 20: reference from draft schedule to Proposed schedule Clarify that the schedule is the proposed version. After Contract Award, the Prime Contractor will work with the DPR to update and finalize the Draft Project Schedule that was submitted as part of the Proposal. After Contract Award, the Prime Contractor will work with the DPR to update and finalize the Proposed Project Schedule that was submitted as part of the Proposal. 13 V.C.2.d AR 22: Indicate Site Plan is a single document. 14 V.C.2.g Added new section to discuss Rolodex and GeoDex conversions. Labeled as Admin Reqmt #24a. 15 V.C.2.h AR 25: Indicate Fit/Gap Analysis is a single document. Clarify that it is a single document that describes all the sites and not a separate document per location. Add requirement for the vendor to perform this conversion and loading to the new system. Clarify that it is a single document that describes all the sites and not a separate document per location. A N/A The Site Plan shall be a single document that describes all of the locations. A N/A See Addendum 2. The Bidder will deliver a Fit/Gap Analysis Report that describes the results of the analysis, the gaps and how the gaps will be addressed, and the specific timeframes for resolving the gaps, including areas which require DPR participation. The Bidder will deliver a Fit/Gap Analysis Report that describes the results of the analysis for all locations, the gaps and how the gaps will be addressed, and the specific timeframes for resolving the gaps, including areas which require DPR participation. Page 6 of 19 Type of (A Add, odify, D Delete)

7 16 V.C.2.i.5 AR 30: Add that failover test is part of the performance test. 17 V.C.2.l Added new section to discuss peak operational months and the staff availability constraints. Labeled as Admin Rqmt #36a Need to ensure that failover works prior to acceptance. Added requirement that defines when DPR staff are available and when the Bidder can rollout the system. A N/A See Addendum 2. Page 7 of 19 Type of (A Add, odify, D Delete)

8 18 V.C.3.a AR 37: Clarify that the sample documents from the Bidder (user manual, system administration manual and operational procedures) are required as part of the proposal submission, and indicate the forms for the planning documents (Forms A16 through A19). terms to be preliminary (for the draft proposal) and proposed plans (for the final proposal). 19 V.C.3.c AR39: Clarify number of days for deliverable review is minimum of 5 State business days, unless otherwise addressed in DED Ensure that there is a requirement calling for these documents to be provided, and use forms to enforce format of planning documents. Provide the Bidders a basic number of days to use in planning. A N/A Unless otherwise indicated by the State in the approval of the DED, the State s review period shall be a minimum of five (5) State business days. Page 8 of 19 Type of (A Add, odify, D Delete)

9 20 V.C.3.f.2 AR43: Added paragraphs regarding use of RAID. 21 V.C.3.f.3 AR44: Indicate environments must be per component 22 V.C.4.b.2 AR49: Deleted Liquidated Damages 23 V.C.4.c.2 AR51: Deleted Liquidated Damages 24 V.C.4.c.4 AR 53: Clarify that the enterprise licensing must include DPR's five allied agencies. 25 V.C.4.d AR 57: Updated reference to the proposed project schedule Clarified constraints if the Bidder is proposing RAID. Clarify that the test environment must accommodate all 3 components (CAD, RS, AS). N/A See Addendum 2. The Bidder must provide a test environment for each of the three (3) Communication Centers and the RS at DPR HQ. Delete the LDs D < See original version > N/A Delete the LDs D < See original version > N/A Ensure that there is coverage for Dept of Fish and Game, et al. "draft" to "proposed" The Bidder must provide a CAD, RS, and AS test environment for each of the three (3) Communication Centers and at DPR HQ. A N/A The enterprise license(s) must allow DPR and its five (5) allied agencies to use all components of the Proposed System. The Bidder must identify on Form A15: Hardware and COTS Software Proposed, when the specific hardware and software items are required, according to the Draft Project schedule The Bidder must identify on Form A15: Hardware and COTS Software Proposed, when the specific hardware and software items are required, according to the Proposed Project schedule Page 9 of 19 Type of (A Add, odify, D Delete)

10 26 V.C.4.d.4 AR61: Clarify that the Bidder must provide the spare equipment and parts to meet the required performance metrics. Clarified in response to reaction to Bidder question (C5). The Bidder also will provide spare equipment. The Bidder also will provide spare equipment and parts as necessary to manage and maintain their proposed equipment, based on the stated uptime and reliability requirements (refer to SECTION V.C.2.i.5: Performance Testing). 27 V.C.6.b.2 AR67: Update to provide more payments and indicate the season (peak or off peak) when the activity/payment may occur. 28 V.C.6.c AR68: Update to indicate testing must include the spare equipment and that software payment will not be made until all components are accepted. Due to the constraints of the peak/off peak periods, vendors need to have more frequent payment points. Hardware testing must include the appropriate spare equipment before payment will be made. Software payment must wait until the final UAT that verifies connectivity and integration of all 3 components. Payment for the hardware shall be made after the equipment has been delivered, installed and tested at each site. The hardware must successfully complete Installation Testing before payment will be made and the State must witness the Installation Testing at each location. Payment for the COTS software will not be made until the system has completed the Total System Validation/UAT Test. Payment for the hardware shall be made after the equipment has been delivered, installed and tested at each of the three (3) Communication Centers, at DTS and at DPR HQ, including testing of the spare equipment, as applicable. Separate payments will be made for the CAD, RS and AS hardware. The hardware must successfully complete Installation Testing before payment will be made and the State must witness the Installation Testing at each location. Payment for the COTS software will not be made until the entire system (i.e., CAD, RS and AS) has completed the Total System Validation/UAT Test. Page 10 of 19 Type of (A Add, odify, D Delete)

11 29 V.C.7 Add language to conform to Darfur Contracting Act of 2008 New Legislation A NA See Addendum VIII.C Clarify that preliminary versions must be submitted in the draft proposal. 31 VIII.C.1 title of Section 5 to be "planning documents" instead of "draft plans". 32 VIII.C.1.f Update the points to account for making the planning documents pass/fail. Clarify that preliminary versions must be submitted in the draft proposal. Remove "draft plans" term. Double the points available for the Section VI Requirements. A N/A Preliminary versions of the Planning Documents must be included in the Draft Proposal (refer to SECTION V.C.3.a: Planning Documents in the Proposal Submission). These versions will not be scored, but must be sufficiently detailed in order for the State to understand the Bidder s approach. Section 5: Draft Plans Section 5: Planning Documents Page 11 of 19 Type of (A Add, odify, D Delete)

12 33 VIII.C.1.g Indicate form numbers for the planning documents ( new Forms A16 through Form 19) and change to reference preliminary and proposed plans. 34 IX.D.1.c Update to refer to proposed (instead of Draft) project mgmt plan and reference new RFP Form A IX.D.1.d Update to refer to proposed (instead of Draft) project schedule and clarify that this is an S Project file. Use forms to enforce format of planning documents and clarify that preliminary versions must be submitted in the draft proposal and proposed versions must be submitted in the final proposals. Use form to enforce format of planning document and update for change in terms. Update for change in terms. Page 12 of 19 Type of (A Add, odify, D Delete)

13 36 IX.D.2 Update to refer to proposed planning documents (instead of Draft) and update Table 13 to indicate Total Solution Description section is pass/fail. Adjust remaining points accordingly. 37 IX.D.2.a.1 Update to indicate how points will be handled if the reference cannot verify the information or disagrees with the Bidder's information. Replace table with updated scoring information to remove "exceeded expectations" et al, and include the new criteria definitions. Clarify Evaluation Criteria. Clarify Evaluation Criteria. Page 13 of 19 Type of (A Add, odify, D Delete)

14 38 IX.D.2.a.2 Update to indicate how points will be handled if the reference cannot verify the information or disagrees with the Bidder's information. Remove customer reference rating form table and adjust point values. 39 IX.D.2.b d to Pass/Fail Updated to indicate preliminary plans (for draft proposal) and proposed plans (for final proposal). Clarify Evaluation Criteria. Updated to indicate preliminary plans (for draft proposal) and proposed plans (for final proposal). odified to Pass/Fail to conform to change in evaluation criteria. 40 IX.D.2.b Table 17 - caption for table to indicate "Rating Scale for Bidder's Draft Plans" Removed table entirely. Page 14 of 19 Type of (A Add, odify, D Delete)

15 41 IX.D.2.b Table 17 - Remove Rating for Exceeded Expectations; adjust remaining items to indicate ratings for "meets requirements", "meets most", "meets some" and "does not meet". 42 IX.D.2.b.1 Indicate form for Proposed System Description and correct typo (product not procedures), and change to pass/fail rating. 43 IX.D.2.b.2 Indicate form for Proposed aintenance Plan, and change to pass/fail rating. 44 IX.D.2.b.3 Indicate form for Proposed Training Plan, and change to pass/fail rating. 45 IX.D.2.b.3 to pass/fail rating. Removed table entirely. Use forms to enforce format of planning documents. Use forms to enforce format of planning documents. Use forms to enforce format of planning documents. Clarify Evaluation Criteria. Page 15 of 19 Type of (A Add, odify, D Delete)

16 46 IX.D.2.b.4 odify Document Quality evaluation to pass/fail odified to Pass/Fail to conform to change in evaluation criteria. 47 IX.D.2.c Update points. Adjust the scoring example in Table 17 & 19. Double the points available for the Section VI Requirements. 48 Appendix A Form A10 (Customer Reference Form) was updated to remove the Exceeded Expectations Ratings and added the explicit criteria and point values Clarify Evaluation Criteria. Page 16 of 19 Type of (A Add, odify, D Delete)

17 49 Appendix A Forms A14-A, A14-B and A14- C (Key Personnel Qualifications Certifications) were updated to add space for the bidder to describe specific information that will be scored and added the point values for each criteria. 50 Appendix A Form A15 (Hardware and COTS Software Proposed) was updated to reference the Preliminary/Prop osed Plans (not the draft). Clarify Evaluation Criteria. Clarify Evaluation Criteria. Replace Draft with Preliminary Proposed. Indicate the date (mm/yyyy) or work plan activity that requires the hardware item, in accordance with the Draft Project Schedule. Indicate the date (mm/yyyy) or work plan activity that requires the hardware item, in accordance with the Preliminary/Proposed Project Schedule. Page 17 of 19 Type of (A Add, odify, D Delete)

18 51 Appendix A Added Forms A16: Preliminary/Prop osed Project anagement Plan, Form A17: Preliminary/Prop osed System Description, A18: Preliminary/Prop osed aintenance Plan, and A19: Preliminary/Prop osed Training Plan 52 Appendix A Added FOR A20: DARFUR CONTRACT ACT CERTIFICATION 53 Form VII-1 Updated Payment ilestones table in Appendix B 54 Form VII-5 Updated to remove AFIS Interface reference in Appendix B Excel workbook 55 Glossary Updated Appendix D to remove AFIS from the Glossary Use forms to enforce format of draft plans. A N/A See Addendum 2. New Legislation A N/A See Addendum 2. Updated Appendix B to include the revised payment milestones Removed due to fingerprint reference Removed due to fingerprint reference D < See original version > See Addendum 2. D < See original version > See Addendum 2. Page 18 of 19 Type of (A Add, odify, D Delete)

19 56 Glossary Updated Appendix D to add definitions of Peak and Off Peak Periods Define the periods when activities may occur. A N/A See Addendum 2. Page 19 of 19 Type of (A Add, odify, D Delete)

St. Lucie Public Schools

St. Lucie Public Schools April 26, 2016 TO: FROM: RE: All Prospective Proposers Kim Albritton Coordinator of Business Services RFP 16-18 Speech-Language Therapy & Audiology Services ADDENDUM 1 TO RFP 16-18 SPEECH-LANGUAGE THERAPY