Page 1 A Guide to the Procurement of Trusted Systems: An ... - csirt

Software Unit Specifications are also called "C" Specifications. A detailed
development specification applies to each component of the system. The "C"
Specifications are the documents that the "builders" of the system use to
construct the various parts of the system. Different types of "C"
Specifications can exist, including critical item product specifications and
software design documents.
2.5.3.9 CONTRACTING DOCUMENTS
Contracting documents are written in support of solicitations. The Federal
Acquisition Regulation (FAR) provides guidance, indicates content, and
sometimes provides standard formats for these documents.
2.5.3.10 INFORMATION FOR BID
This type of document is normally used for acquisitions of standard commercial
off-the-shelf (COTS) items, where several vendors could provide the same
item or capability. If the requirements are satisfied, the low bidder has
the highest likelihood of winning the contract.
2.5.3.11 REQUEST FOR QUOTE (RFQ)
This document is a request by the Government for vendor pricing information.
2.5.3.12 REQUEST FOR INFORMATION (RFI)
This type of document typically precedes an RFP. The RFP is actually a draft
RFP issued to obtain feedback from industry on the approach, content, and
language of the proposed solicitation. The objective is to ensure the final
RFP is clear, comprehensive, and fair to all Competitors. An RFP also helps to
ensure requirements can be met using available technology, that the schedule
is realistic, and the approach is workable. It is important for the Program
Manager to listen to industry's feedback, although he/she does not always have
to agree.
2.5.3.13 REQUEST FOR PROPOSAL
The RFP is often referred to as the solicitation package. The RFP is the
most widely used document for AlS oriented acquisitions and is the focus of
this procurement guideline series. The General Services Administration (GSA)
has available standard solicitation documents for Systems, Software, Equipment
and Maintenance. A guide on how to use these documents is also available.
While the specifications for security must still be developed, the basic
acquisition documents have proven to be valuable, especially to those new to
acquisition. A standard RFP has thirteen sections, which are each referred
to by a letter (see Table 2-1). Upon contract award, the final RFP, with
sections L and M omitted, becomes the final contract guideline, including
security-relevant aspects, are discussed below.
Table 2-1 RFP Organization
Letter
Section Title
A Solicitation/Contract Form - Standard Form 33
Page 30