N00019-10-R-0097-0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

See Page Tw o

1. CONTRACT ID CODE PAGE OF PAGES

S 1 6

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 25-Jun-2012

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00019-10-R-0097

X 9B. DATED (SEE ITEM 11)

30-Apr-2012

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

25-Jun-2012

CODE

NAVAL AIR SYSTEMS COMMAND

AIR-2.2.4.3 - B2272 - R453

47123 BUSE ROAD

PATUXENT RIVER MD 20670

N00019 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00019-10-R-0097

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following revisions are hereby incorporated into N00019-10-R-0097, Section L:

1. Section 3.1 General

FROM:

3.1 General

The following is a list of the Section L Past Performance Attachments that the Offeror shall utilize to provide past performance information as required for this Volume:

PP Attachment PP-01 Past Performance Questionnaire

PP Attachment PP-02 Summary of Relevant Past Performance Contract Data

The Offeror shall identify recent relevant contracts on similar programs that provide evidence of its organization’s (including the Offeror’s principal subcontractors, critical subcontractors and JV/SLE team members) ability to perform the effort required for this program on similar programs. Past Performance information provided should be related to similar programs/contracts performed in the same division, or price center (e.g. the same CAGE code) in which the Offeror proposes to perform this effort. Additionally, Past Performance information shall be related to efforts performed within five years from the proposal due date. Offerors shall provide information concerning any show-cause notices, cure notices, termination for default on any contract. As much as possible, correspond to the descriptions of the Offeror’s corporate experience provided in Volume 4, Corporate Experience with the descriptions provided in this Volume.

TO:

3.1 General

The following is a list of the Section L Past Performance Attachments that the Offeror shall utilize to provide past performance information as required for this Volume:

PP Attachment PP-01 Past Performance Questionnaire

PP Attachment PP-02 Summary of Relevant Past Performance Contract Data

The Offeror shall identify recent relevant contracts on similar programs that provide evidence of its organization’s (including the Offeror’s principal subcontractors, critical subcontractors and JV/SLE team members) ability to perform the effort required for this program on similar programs. Past Performance information provided should be related to similar programs/contracts performed in the same division, or price center (e.g. the same CAGE code) in which the Offeror proposes to perform this effort. Additionally, Past Performance information shall be related to contracts, or those portions of a contract, whose performance is within five years from the proposal due date. Offerors shall provide information concerning any show-cause notices, cure notices, termination for default on any contract. As much as possible, correspond to the descriptions of the Offeror’s corporate experience provided in Volume 4, Corporate

Experience with the descriptions provided in this Volume.

2. Section 3.2 Relevant Contract Data

3.2 Relevant Contract Data

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

In this Volume, identify contracts whose performance is within five years of this proposal due date and contain efforts similar to those efforts, e.g., end product or service, contract tasks, contract type, contract dollar value, etc., required by this solicitation for the Offeror, the principal subcontractors, critical subcontractors and JV/SLE team members. In general, recent performance will be considered more relevant than older performance. Commercial contracts may be included. List the contracts from the most relevant to the least relevant. These contracts should include the relevant contracts for the Prime and principal subcontractors, critical subcontractors and JV/SLE team members. If the Offeror is proposing as a JV/SLE, the Offeror should also provide the relevant contracts for the JV/SLE and for each member of the JV/SLE. Contracts detailed in this Volume should be the same contracts/efforts identified in the

Corporate Experience Volume provided that they are within five years of this proposal due date.

3.2 Relevant Contract Data

The burden of providing thorough and complete past performance and systemic improvement information remains with the Offeror.

In this Volume, identify contracts, or those portions of a contract, whose performance is within five years of this proposal due date and contain efforts similar to those efforts, (e.g., end product or service, contract tasks, contract type, contract dollar value, etc.), required by this solicitation for the Offeror, the principal subcontractors, critical subcontractors and JV/SLE team members. In general, recent performance will be considered more relevant than older performance. Commercial contracts may be included. List the contracts from the most relevant to the least relevant. These contracts should include the relevant contracts for the Prime and principal subcontractors, critical subcontractors and JV/SLE team members. If the

Offeror is proposing as a JV/SLE, the Offeror should also provide the relevant contracts for the JV/SLE and for each member of the JV/SLE. Contracts detailed in this Volume should be the same contracts/efforts identified in the Corporate Experience Volume.

Note 1: Relevancy

Provide a concise assessment of the degree of relevancy that each past performance referenced contract has to the solicitation, identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program. Include your assessment of the relevancy of the contract in terms of one of the following ratings: Very Relevant (VR) and Somewhat Relevant (SR) where:

Very Relevant (VR) – Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant (SR) - Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

The contract relevancy assessment should be relative to the prime’s, principal subcontractors’, critical subcontractors’ and JV/SLE team members’ proposed role/responsibility versus relative to the whole solicitation. For example, a subcontractor who is being proposed to perform only software has a past contract whose total work is software. Even though the software effort is only

10% of the solicitation effort, it relates to 100% of the subcontractor proposed effort for this proposal and therefore is considered Very Relevant vice Somewhat Relevant.

Contracts submitted by the Offeror that meet any of the conditions below will be assessed as

Not Relevant:

contracts from an entity that does not have a defined proposed role and responsibility;

contracts from a different physical location (e.g., with different CAGE code/DUNS) than the entity proposed in the roles and responsibility table contracts that involve little to none of the scope, magnitude of effort and/or complexities required by this solicitation; or contracts or those portions of the contract whose performance is older than 5 year from the proposal due date.

Not Relevant contracts will not be considered in the Past Performance assessment.

Note 1: Relevancy

Provide a concise assessment of the degree of relevancy that each past performance referenced contract has to the solicitation, identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program. Include your assessment of the relevancy of the contract in terms of one of the following ratings: Very Relevant (VR) and Somewhat Relevant (SR) where:

Very Relevant (VR) – Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant (SR) - Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

The contract relevancy assessment should be relative to the prime’s, principal subcontractors’, critical subcontractors’ and JV/SLE team members’ proposed role/responsibility versus relative to the whole solicitation. For example, a subcontractor who is being proposed to perform only software has a past contract whose total work is software. Even though the software effort is only

10% of the solicitation effort, it relates to 100% of the subcontractor proposed effort for this proposal and therefore is considered Very Relevant vice Somewhat Relevant.

The following conditions result in a Not Relevant assessment:

Contracts from an entity that does not have a defined proposed role and responsibility will be assessed as not relevant;

Contracts from a different physical location (e.g., with different CAGE code/DUNS) than the entity proposed in the roles and responsibility table will be assessed as Not Relevant;

Contracts that involve little or none of the scope and magnitude of effort and/or complexities required by this solicitation will be assessed as Not Relevant; ;

Contracts or those portions of a contract whose performance is older than five years from the proposal due date will be assessed as Not Relevant.

Not Relevant contracts will not be considered in the Past Performance assessment.

3. Section 5 - Volume 5 – Price Proposal

5.0 VOLUME 5 - PRICE PROPOSAL

5.3 Price/Cost Proposal Instructions:

Section 2 –FFP CLINs

a. Ground Rules and Assumptions for Firm Fixed Price CLINs

The Offeror shall provide an explanation of all ground rules and assumptions that affect the cost estimates.

b. Contract Prices for Firm Fixed Price CLINs/ SLINs

Provide the proposed cost for each CLIN/SLIN using Price Attachments PA-02 and PA-03. The Offeror shall identify the proposed costs by CLIN/SLIN and by work center using Price Attachments PA-02 and

PA-03. The Offeror shall provide a duplicate of the Manning specified in Section 2.1.7 (a) and (c) with associated pricing data. If the manning, price buildup, unit price and extended price is the same for multiple identical Option SLINs within a CLIN, the proposal may show a single build-up and then state “SLINs

XXXX-XXXX build-up is the same as SLIN XXXX. Any inconsistency between proposed performance and price should be explained in the proposal as well as any appearance of unbalanced pricing.

5.0 VOLUME 5 - PRICE PROPOSAL

5.3 Price/Cost Proposal Instructions:

Section 2 –FFP CLINs

a. Ground Rules and Assumptions for Firm Fixed Price CLINs

The Offeror shall provide an explanation of all ground rules and assumptions that affect the cost estimates.

b. Contract Prices for Firm Fixed Price CLINs/ SLINs

Provide the proposed cost for each CLIN/SLIN using Price Attachments PA-02 and PA-03. The Offeror shall identify the proposed costs by CLIN/SLIN and by work center using Price Attachments PA-02 and

PA-03. The Offeror shall provide a duplicate of the Manning specified in Section 2.1.6 (a) and (c) with associated pricing data. If the manning, price buildup, unit price and extended price is the same for multiple identical Option SLINs within a CLIN, the proposal may show a single build-up and then state “SLINs

XXXX-XXXX build-up is the same as SLIN XXXX. Any inconsistency between proposed performance and price should be explained in the proposal as well as any appearance of unbalanced pricing.

(End of Summary of Changes)

[This page left intentionally blank]