1 lecture 2.2b: proposal process, rfp, sow, clins, dids, and forming team projects dr. john...

10
1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

Upload: alexandrina-kennedy

Post on 19-Jan-2016

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

1

Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects

Dr. John MacCarthyUMBC CMSC 615Fall, 2006

Page 2: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

2

Agenda Proposal Process RFPs SOWs CLINs List Typical Products and Services DIDs Class Project RFP/SOW Class Project CLINs List & DIDs Form Project Teams

Page 3: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

3

Proposal/Contract Process Phase I: Government

Preparation of an RFP Source Selection Plan

Membership/Responsibilities of Source Selection Team

Evaluation Criteria Detailed Evaluation Procedures

Statement of Objectives (SOO) [Statement of Need (SON)]

Statement of Work (SOW) Section 1: Scope Section 2: Applicable

Documents Section 3: Requirements

Contract Data Requirements List (CDRL)

Request for Proposals (RFPs)

Phase II: Contractor Preparation of Proposals

PMP/SEMP WBS Schedule Cost Estimate Key Personnel Past Performance Requirements Analysis Artifacts Conceptual Design

Phase III: Government Source Selection (Proposal Evaluation)

Technical Management Past Performance

Phase IV: Contract/Contract Award

Phase V: Start Project

Page 4: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

4

The Statement of Work (SOW)

Definition: The document that specifies the scope of the contract. It generally includes:

A description of the work to be performed A description of the system to be developed A concept of operations for the system A set of high level requirements for the system A description of the work that the customer expects the contractor

to perform A CLINs List: a list of products (and services) to be provided by

the contractor. A DID for each document/artifact CLIN: a description of the

content and format of key deliverables

Purpose: Defines the contract

Page 5: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

5

Contract Line Item Numbers (CLINs) List

Definition: A numbered list of items (products and/or services) that the contractor is contractually obligated to deliver to the customer (i.e. contractual deliverables)

Purpose: The principal means for the customer to evaluate contractor performance

Generally a SOW will come with a CLINs List Often the customer will ask the contractor to make

SOW/CLINs recommendations Generally the contractor will propose additions/deletions

Generally allocated to WBS Elements and then to Work Packages

Failure to deliver any item on the CLINs List can result in Legal Action (everything else is optional)

Page 6: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

6

Data Item Description (DID)

Definition: A description of the content and structure of a key document/artifact CLIN

Purpose: The principal means for the customer to covey their expectations of document/artifact content and structure

Generally there will be DID for each artifact CLIN Often the customer will ask the contractor to propose

and/or review the DIDs Generally the contractor will propose modifications

Failure to follow a DID generally results in the Customer not accepting a product.

Page 7: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

7

Typical SE Services and Products

Some Typical Services: Systems Engineering

Management System Architecting Requirements Generation Configuration

Management Systems Analysis Modeling and Simulation Validation and

Verification Support Reviews and Audits

Some Typical Products: Work Packages Plans

Systems Engineering Plan Risk Management Plan Configuration Management

Plan Selected Quality

Management Procedures Architecture Artifacts Specifications Analyses/Trade Studies System Models/SimulationsThis is a partial list.

Services and Products provided by SE vary from project to project.

Page 8: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

8

Class Project Customer System Specification/Description

See Word File

Page 9: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

9

Class CLINs List and DIDs CLINs List:

Homework 1-10

SEP

Requirements Document Architecture Artifacts Research Papers Project Briefing Project Notebook

Midterm Exam Final Exam

DIDs: Homework 1-10: see Lecture 1 &

each assignment SEP: See Reference SEP Annotated

Outline Requirements Document: IEEE-830 Architecture Artifacts: Lecture

Notes Research Paper: see Lecture 1 Project Briefing: TBD Project Notebook: see Lecture 1

Midterm Exam: TBD Final Exam: TBD

Page 10: 1 Lecture 2.2b: Proposal Process, RFP, SOW, CLINS, DIDs, and Forming Team Projects Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

10

Form Project Teams 3-4 people per team