04_Attachment_1_BAA_Forms.pdf

W900KK-16-R-0031

PAST PERFORMANCE INFORMATION

Offerors shall provide the information requested in this form for each contract/project being described. Offerors should provide frank, concise comments regarding their performance on the contracts, if contractor, or funded work efforts, if government agency, they identify. Offerors shall provide a separate completed form for each contract/project submitted. Offerors shall limit the number of past efforts submitted and the length of each submission to the limitations set forth at Part III, paragraph 8 of this BAA.

A. Offeror Name (Company /Division): ____________________

CAGE Code: ____________________

DUNS Number: ____________________

(NOTE: If the company or division performing this effort is different from the Offeror or the relevance of this effort to the instant acquisition is impacted by any company/corporate organizational change, note those changes.

B. Project Title: ________________________________________

C. Contract Specifics:

1. Contracting Agency or Customer _____________________________________________

2. Contract Number __________________________

3. Contract Type __________________________

4. Period of Performance __________________________

5. Original Contract $ Value _________________ (Do not include unexercised options)

6. Current Contract $ Value _________________ (Do not include unexercised options)

7. If Amounts for 5 and 6 above are different, provide a brief description of the reason

D. Brief Description of Effort as __Prime or __Subcontractor

(Please indicate whether it was development and/or production, or other acquisition phase and highlight portions considered most relevant to current acquisition

(add lines as necessary)

E. Completion Date:

1. Original date: _________________

2. Current Schedule: ____________________

3. Estimate at Completion: ____________________

4. How Many Times Changed: ____________________

5. Primary Causes of Change: ________________________________________

F. Primary Customer Points of Contact: (For Government contracts, provide current information on all three individuals. For commercial contracts, provide points of contact fulfilling these same roles.)

1. Project Manager: Name ____________________

Office ____________________

Address ____________________

Telephone ____________________

Email ____________________

2. Contracting Officer: Name ____________________

Office ____________________

Address ____________________

3. Administrative Name ____________________

Contracting Officer Office ____________________

Address ____________________

G. Address any technical (or other) area about this contract/project considered unique.

H. Specify, by name, any key individual(s) who participated in this project and are proposed to support the instant acquisition. Also, indicate their contractual roles for both acquisitions.

Project Execution Plan (PEP)

Each T&E/S&T Project will have a Project Execution Plan (PEP). The PEP establishes the execution baseline for each project and serves as an execution agreement between the S&T developer, Executing Agent and the Test

Resource Management (TRMC).

Each PEP will contain the following elements:

Title page with project contact information

Description of work scope by phase

Description of T&E Needs, S&T Challenges, starting/ending Technology Readiness Levels (TRL)

Budget by phase and Government Fiscal Year

Project Schedule

Phase Exit Criteria

Project Specifications

Transition Plan

List of deliverables per phase

The PEP format is provided in the following template section. Offerors should note that majority of draft PEP documentation is already provided in the technical proposal and statement of work and can be leveraged from those documents to create the draft PEP for proposal submission.

Upon contract award, the S&T developer has within 60 days of receipt of contract award/funds to finalize the PEP using feedback from the Government.

Once the baseline has been approved, the PEP will be modified as necessary as changes to the projects are necessary and evident.

Test Resource Management Center

Test and Evaluation/Science and Technology Program

[TEST TECHNOLOGY AREA NAME]

[PROJECT NAME (ACRONYM)]

Project Execution Plan

[Principal Investigator Name]

[PI Contact Info – Affiliation]

[Phone Number ]

[Email]

[Government Lead Name]

[GL Contact Info – Affiliation]

[Phone Number]

[Email]

Distribution Statement C

Distribution: Authorized to U.S. Government Agencies and their contractors only; Reason: administrative/ operational use. Other requests for this document shall be referred to the Program Manager for Test and

Evaluation/Science and Technology (T&E/S&T), Test Resource Management Center, 1225 South Clark Street, Suite 1200, Arlington, VA 22202.

[Title of Project and PI should be included in all pages of the PEP]

Work Scope

Phase 1 - In bulletized form, give the major areas of work to be done under this phase

Phase 2 – If there are majors reviews such as CDR, state so

Phase 3 – If there are systems being demonstrated or delivered, it should be noted by phase

T&E Needs

T&E Need 1 – In bulletized form, state the T&E need and how it was determined if possible

- sub need 1 – give details of the need that will flow down into specifications

- sub need 2

T&E Need 2 – If there is more than one overall T&E need, state it here

- sub need 1

- sub need 2

S&T Challenges

S&T Challenge 1 – In bulletized form provide the major S&T challenges that must be overcome in order for this project to be successful

S&T Challenge 2 – There may be multiple S&T challenges and they may or may not address the T&E Needs

Technology Readiness Levels

Give the TRL for the start of the project and the expected TRL at the end of each phase (and end of the project).

Give the date of the initial TRL assessment and who participated in the TRL assessment.

Budget

[In this section the funding by phase and fiscal year should be identified. If there is external funding (non-T&E

S&T), there should be a line item for each. All years with funding should be shown].

FY10 FY11 FY12 FY13

Phase 1

Phase 2

Phase 3

External Source

Totals

Project Schedule

[In this section include copies of the schedule with all major milestones. Multiple pages can be used if necessary]

Activity

2010 2011

Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sept Oct

PHASE 1

(6 months)

Post Award

Conference

OSC upgrade to handle e(T)

Create e(t) database

Upgraded OSC ready

Create synthetic scenes

Define Objective

Function

Establish covariances

Monthly reports

Draft/Final Report

Phase-II Decision

Mtg.

[rolled up tasks should be in gray, on schedule tasks in green, and schedule slips shown in red]

Project Specifications:

Parameter

Current T&E

Capability

Current

Target Ultimate Goal Achieved

Temperature

-Accuracy

-Range

Unknown

Unknown

± 30 K

400-4000 K

± 30 K

400-4000 K

TBD

Wavelength Coverage NIR to LWIR NIR to LWIR NIR to LWIR NIR to LWIR

(model only)

Image Processing Drivers

-Pixels/Image

-Frame Rate

256 x 256

>60 Hz

≥ 25 x 25

30 Hz

≥ 25 x 25

30 Hz

25 x 25 (model only)

Phase Exit Criteria

- In bulletized form give the list of conditions that must be met in order to proceed to the next phase

- These criteria should be distinct, concisely defined, measureable, and not subject to varied interpretation

Phase 2

- criteria 1

- criteria 2

- A criterion for entry into the final phase is the transition partner’s agreement to accept the successful deliverable(s).

Phase 3

- criteria 1

- criteria 2

Project Transition

The preliminary transition partner should be identified in this section, along with the keys to solidifying the transition plan.

List of Deliverables

- In bulletized form, give the deliverables by phase. For prototype hardware or software, the disposition of each deliverable should be discussed.

- Deliverable 2

Phase 2

- Deliverable 3

- Deliverable 4

Phase 3

- Deliverable 5

- Deliverable 6

DATA RIGHTS ASSERTIONS

IAW DFARS 252.227-7017 IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE

RESTRICTIONS

Offers submitted in response to this BAA shall identify to the Government, the technical data or computer software that the Offeror, its subcontractors or suppliers, or potential subcontractors or suppliers, assert should be furnished to the Government with restrictions on use, release, or disclosure. The Offeror's assertions, including the assertions of its subcontractors or suppliers or potential subcontractors or suppliers, shall be submitted as an attachment to its offer in the following format, dated and signed by an official authorized to contractually obligate the Offeror:

Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or

Computer Software. The Offeror asserts for itself, or the persons identified below, that the Government's rights to use, release, or disclose the following technical data or computer software should be restricted.

Technical Data and

Computer Software to be

Furnished with Restrictions*

Basis for Assertion** Asserted Rights Category***

Name of Person

Asserting

Restrictions****

(List)***** List List List

*For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such item, component, or process. For computer software or computer software documentation, identify the software or documentation.

**Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Government's rights in computer software documentation generally may not be restricted. For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.

***Enter asserted rights category (e.g., government purpose license rights from a prior contract, rights in SBIR data generated under another contract, limited, restricted, or government purpose rights under this or a prior contract, or specially negotiated licenses).

****Corporation, individual, or other person, as appropriate.

*****Enter “none” when all data or software will be submitted without restrictions.

Date___________________________________

Printed Name and Title__________________________________________________________________________

Signature_____________________________________________________________________________________

Note: An offeror's failure to submit, complete, or sign the notification and identification required with its offer may render the offer ineligible for award. If the Offeror is awarded a contract, the assertions identified will be listed in an attachment to that contract. Upon request by the Contracting Officer, the Offeror shall provide sufficient information to enable the Contracting Officer to evaluate any listed assertion.