24.5 Preparing an RFP

24.5.0 Preparing an RFP

When preparing an RFP, resolve the issues and questions in Appendix B, Checklist of Issues to Resolve Before and During RFP Preparation, and follow these best practice recommendations:

  • The RFP planning and the RFP document should be comprehensive. The RFP should be written in plain, straight-forward language avoiding ambiguous, conflicting and undefined terms. All acronyms and other critical terms should be defined.
  • VITA SCM Only: Use the technology sourcing process (TSP) model for preparing and evaluating an RFP.
  • Use a standard and/or authorized RFP template. This helps ensure all project needs are identified and clearly communicated to suppliers. The RFP template includes a “laundry list” of typical issues that need to be addressed to trigger productive thought processes and ensure that no requirements are overlooked. VITA has developed an RFP template for use by VITA sourcing specialists. Training for customer agencies on the use of this template will become available from VITA SCM at a future date and should be undertaken prior to first-time use.
  • Provide all information needed for any outside party to understand the current situation or business need, the desired solution and the terms and conditions of the future relationship.
  • Use extra dilig "meat" of the RFP.
  • Address quality assurance, performance standards and measures, service level expectations, etc.
  • Address upgrades, enhancements, expansions, modifications, disaster recovery, business assurance, training as well as environmental, confidentiality and federal, state and local security and data privacy standards.
  • Include appropriate requirements, the proposed IT contract template (see Chapter 25 - IT Contract Formation, IT Contract Formation.) (Other agencies: see box text below.) This places the burden of understanding on the suppliers to have a handle on the project’s requirements and prepare fully responsive proposals.

VITA has developed and approved IT contract templates that are customized for the specific type of IT acquisition: Services, Software, Solution, Hardware, Hardware Maintenance, Cloud, and EULA license addendum. Other agencies should be trained in using these prior to use. Until that occurs, agencies should use their own templates and ensure the Minimum VITA Requirements for Agency Delegated RFPs/Contracts provisions are included in the RFP. This can be found on SCM’s website at this location under the Forms section: SCM Policies & Forms. Refer to Chapter 28 - Agency IT Procurement Security and Cloud Requirements for Solicitations and Contracts for more information on required security and cloud related terms and conditions.

Once the requirements are completed, in addition to the agency’s general contract terms, appropriate IT terms should be included, as well as any special terms to cover any extraordinary risk(s) associated with the project. VITA sourcing specialists will use the approved template or master definitions and terms that match the procurement type, while agencies should include all necessary provisions that relate to the IT procurement such as necessary terms related to services, hardware, or software that may include: Ownership of Intellectual Property, Third Party Acquisition of Software, Software Upgrades, Software Disposition, Source Code, Term of Software License, special warranties, etc. It is not the standard for VITA to provide its IT templates or terms to agencies at this time. Agencies who have received delegated authority to conduct their own IT procurements may request assistance for complex solution, application service provider and/or software as a service type IT procurements by contacting: scminfo@vita.virginia.gov.

A project that is part of a larger federal initiative or one funded with federal money may require including specific terms that must be flowed down from the funding sponsor or from federal statute. Examples are: the HITECH and HIPAA Acts for health records related projects. Obviously, this type of project or a project related to data within any Commonwealth agency that processes private health, confidential or sensitive citizen information; i.e., Department of Health, Department of Motor Vehicles, or Department of Social Services, may have special security or data protection needs as well. Procurement officials should seek, ask, research available internal sources, OAG and VITA to determine the requirements for such special terms and conditions.

It is important to perform a quality review of the solicitation to remove redundant, ambiguous and conflicting terms.