IE11 Not Supported

For optimal browsing, we recommend Chrome, Firefox or Safari browsers.

Report: 21 Recommendations of State IT Procurement Task Force

According to today’s report “Recommendations to Improve Large Information Technology Procurements: A Road Map for Success in California,” Governor Brown and State Controller John Chiang appointed task force members to help the state identify how it can hire the right vendors, at the best value and hold them accountable for their performance.

Included in the 34-page report are 21 recommendations:

1. Department of General Services (DGS), California Technology Agency (CTA), and Department of Finance (a.k.a. Finance or DOF) should abandon the FSR and restructure the project-approval process to create two stages: (1) initial approval and (2) detailed planning approval.

2. Understand, document, and validate business requirements and objectives before solicitation.

3. Use business process reengineering to modernize and standardize state processes.

4. The Procurement Authority should strengthen the market research requirement in the project-approval process and provide detailed guidance on how to conduct market research, including the use of one-on-one meetings.

5. Require the acquisition strategy and procurement plans to describe the governance body for each project that includes a transparent, clear, timely, and robust decision-making process.

6. Under the authority and direction of the CTA, extend the Office of Systems Integration (OSI) model to the rest of the state for large-scale IT projects.

7. The Procurement Authority should require a formal staffing plan as part of the project-approval process.

8. The Procurement Authority should develop a cadre of procurement and legal staff well versed in the use of PCC 6611 and expand its use for IT projects.

9. At the recommendation of the project executive, allow for a contingency contract dollar amount consistent with the size and complexity of the project.

10. The Procurement Authority should study and annually report on the viability and utility of using alternative contracting vehicles.

11. The Procurement Authority should develop and publish a model procurement task plan that establishes the goal of a 10-month maximum timeline from RFP issuance to contract execution.

12. The Procurement Authority should conduct formal post-project evaluation of major procurements, with annual reporting on lessons learned and needed improvements.

13. Use a combination of quantitative and qualitative criteria to evaluate proposals.

14. The CTA as the state’s technology leader must set an expectation that IT procurements are iterative and that staff should expect and plan for change.

15. The Procurement Authority should develop and publish a standard, streamlined framework for the addendum process.

16. The Procurement Authority should require a contract-management office for large-scale IT projects and should assess the need for a central contract management office.

17: Develop and use contract incentive provisions to reward excellent performance and address underperforming projects.

18. The CTA should identify methods to collect vendor performance data and incorporate it into prescreening of vendors for future procurements.

19: Reduce and track vendor changes of key personnel and subcontractors.

20. The Procurement Authority should develop an ongoing forum for vendors and state staff to meet outside of the pressure of solicitations.

21. The CTA should review the procurement life cycle to identify opportunities to increase effective and fair communication between the state and vendors.