110 likes | 432 Views
Lecture 3.9: RFP, SOW and CDRL (SEF Ch 19). Dr. John MacCarthy UMBC CMSC 615 Fall, 2006. Organizing and Integrating System Development (Ch. 18). Integrated Development Project Organization & Integrated Teams Team Organization and Development Team Membership, Roles and Maintenance
E N D
Lecture 3.9: RFP, SOW and CDRL (SEF Ch 19) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
Organizing and Integrating System Development (Ch. 18) • Integrated Development • Project Organization & Integrated Teams • Team Organization and Development • Team Membership, Roles and Maintenance • Team Processes • Barriers to Integration • Integrated Product and Process Development (IPPD) and Integrated Product Teams (IPTs) • Government Role in IPTs
Contracting Process (19.2) • Key Documentation: • Request for Proposal (RFP) • Statement of Work (SOW) • Source Select Plan • Contract Data Requirements List (CDRL) • Work Breakdown Structure • Contract
Solicitation • Request for Proposal (RFP) • Solicitation for proposals • Describes customer needs and what contractor must do to be considered for the contract • An RFP generally includes: • a SOW • a definition/specification of the system to be developed, • a CDRL
Contracting Options • A number of contracting options are available to the Government
The SOW (S19-B) • SOW specifies the work to be done by the contractor • It is derived from the PWBS (System Architecture) • It normally consists of three sections: 1 Scope: Defines overall purpose of the program and to what the SOW applies 2 Applicable Documents: Lists specifications and standards referenced in Section 3 3 Requirements: States the tasks the contractor has to perform to provide the deliverables. Tasks should track to with the WBS.
Definition/Specification of System to be Developed • Provides the customer requirements for the system to be developed • Generally they will be high-levelfunctional and interface requirements • Usually they will include performance requirements • Often requirements will be incomplete • Occasionally requirements will appear to be contradictory • Sometimes it will include a description of the environment and constraints (design and/or legacy components) • Sometimes it will neglect to mention these
CDRL (SEF S19-C) • Contract Data Requirements List (CDRL): • “A list of authorized data requirements for a specific procurement that forms a part of a contract” • A collection of DD Forms 1423 containing data requirements and delivery instructions • Definitions of the blocks may be found in SEF S19-C • A Data Item Description (DID) (DD Form 1664) generally accompanies each CDRL Data Item. The DID defines the data content, preparation instructions, format, intended use, and recommended distribution of the data required of the contractor for delivery
Summary (19.3) • Solicitation Planning includes development of an RFP, PWBS, SOW, System Specification/Description, CDRL, and Source Selection Plan, • There are various options available as to how to contract system development • The RFP describes what the contractor must do to be considered for a contract. It generally includes the SOW, Specification and CDRL • The SOW indicates the work the contractor is to perform • The System Specification indicates what the contractor is to build • The CDRL lists the data the contractor is required to provide to the Government • CDRL Data Items generally have an associated DID that describes required content and format • Source Selection is base on evaluation criteria outlined in the SSP and in Sections L and M of the RFP