N66604-14-R-1120_Amendment_7.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 2

1. CONTRACT ID CODE PAGE OF PAGES

U 1 41

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

16C. DATE SIGNED

BY 14-Nov-2014

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 N66604-14-R-1120

X 9B. DATED (SEE ITEM 11)

14-Aug-2014

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 X 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 1 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

14-Nov-2014

CODE

NAVAL UNDERSEA WARFARE CENTER

ALISON C. WICKS, CODE 0223

CONTRACTS DEPARTMENT

1176 HOWELL STREET, BLDG. 1258

NEWPORT RI 02841

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N66604-14-R-1120

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 7

The purpose of Amendment 0007 is to clarify information concerning the cost incentive as follows:

Section B:

1. Revise CLIN 1001, 1002, and 1003 descriptions.

2. Revise Note D to the following: NOTE D (COST INCENTIVE)– The Contractor shall propose a Cost Plus Incentive Fee (CPIF) structure for these item(s). The Contractor shall propose within the following Government/Contractor shareline boundaries:

ITEM UNDERRUN OVERRUN

1001 & 1002 50/50 50/50 Minimum Fee - No Greater than 0% of Target Cost. Maximum Fee – Up to 8% of Target Cost.

Section I: Include FAR Clause 52.216-10-Incentive Fee, by full text. Please note offerors are required to fill in this clause.

Section L: Revise Section L 3.2.2 Cost Summary for (CPIF) - CLINs 1001, and 1002, to include the following language:The Offeror shall propose the Target Cost, Target Fee, and Target Cost plus Fee for the Cost Plus Incentive Fee CLINs within the Government/Contractor share line boundaries of 50/50. For the Cost Plus Incentive Fee contract lines, the Offeror shall propose a minimum fee of no greater than 0% and a maximum fee of no more than 8%.

Additional Information: All previous amendments and answers to questions indicating there is no cost incentive are incorrect and should be disregarded. There are both cost and performance incentives. The cost incentive should be considered/applied within CPIF CLINs 1001 and 1002 in accordance with Note D and FAR Clause 52.216-10.

The performance incentive should be considered/applied within CLIN 1003 in accordance with Attachment J-4.

The proposal due date is hereby extended to 2:00 PM EST on Tuesday, 25 November 2014.

All other terms and conditions remain unchanged.

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 10-Nov-2014 02:00 PM to 25-Nov-2014 02:00 PM.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 1001

The CLIN extended description has changed from Product Integration & Non-Recurring EngineeringSee NOTES A & D to Product Integration & Non-Recurring Engineering. See NOTE A and See NOTE D, concernig

COST INCENTIVE.

CLIN 1002

The CLIN extended description has changed from See NOTES A & D to See NOTE A and See NOTE D, concernig COST INCENTIVE.

CLIN 1003

The CLIN extended description has changed from See NOTE A to See NOTE A and See Attachment J-4, concerning PERFORMANCE INCENTIVE.

The following have been modified:

CLIN NOTES

NOTE A – Option item which is to be supplied only if, and to the extent, said option is exercised.

NOTE B – Stepladder pricing for CLINs 5001, 5002, 6001, 6002, and 7001, 7002 is established in Tables 1-6 below. The offerors shall adjust the break-point quantities for the step levels within its proposal in order to match the optimal economic quantity manufacturing processes and supplier pricing.

NOTE C – Labor hours, if any, shall be ordered by issuance of Technical Instructions (TIs) by the Contracting Officer’s Representative in accordance with NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS (APR 1999) included in Section H –Special Contract Requirements.

Fixed Fee Table CLIN Hours Est Cost/Hr

(rate) Fixed Fee/Hr

(FF)

Fixed Fee (Hrs*FF)

Est Cost (Hrs*rate)

CPFF

NOTE D (COST INCENTIVE)– The Contractor shall propose a Cost Plus Incentive Fee (CPIF) structure for these item(s). The Contractor shall propose within the following Government/Contractor shareline boundaries:

ITEM UNDERRUN OVERRUN

1001 & 1002 50/50 50/50 Minimum Fee – No greater than 0% of Target Cost. Maximum Fee – Up to 8% of Target Cost.

TABLE 1: Stepladder Pricing for RTI Production Units, CLIN 5001

UNIT NAME

Part /

Drawing Number

PRICE PER QUANTITY PROCURED

CLIN Range 1 (start at 1) Range 2 Range 3

(maximum 6)

Breakpoints to be Proposed by Contractors

Escort Mission Module Production Units 5001 Pricing here for each unit Pricing here for each unit

Pricing here for each unit

TABLE 2: Stepladder Pricing for RTI Production Units, CLIN 6001

Number

PRICE PER QUANTITY PROCURED

CLIN Range 1 (start at 1) Range 2 Range 3

(maximum 8)

Breakpoints to be Proposed by Contractors

Escort Mission Module Production Units 6001 Pricing here for each unit Pricing here for each unit

TABLE 3: Stepladder Pricing for RTI Production Units, CLIN 7001

Number

PRICE PER QUANTITY PROCURED

CLIN Range 1 (start at 1) Range 2 Range 3

(maximum 8)

Breakpoints to be Proposed by Contractors

Escort Mission Module Production Units 7001 Pricing here for each unit Pricing here for each unit

TABLE 4: Stepladder Pricing for RTI Spare Parts for CLIN 5002

Number

PRICE PER QUANTITY PROCURED

CLIN Range 1 Range 2 Range 3

Breakpoints to be Proposed by Contractors

List Spare Parts Individually 5002 Pricing here for each unit

Pricing here for each unit

Pricing here for each unit

Continue Lines as needed. 5002

TABLE 5: Stepladder Pricing for RTI Spare Parts for CLIN 6002

Number

PRICE PER QUANTITY PROCURED

CLIN Range 1 Range 2 Range 3

Breakpoints to be Proposed by Contractors

List Spare Parts Individually 6002 Pricing here for each unit

Pricing here for each unit

Pricing here for each unit

Continue Lines as needed. 6002

TABLE 6: Stepladder Pricing for RTI Spare Parts for CLIN 7002

Number

PRICE PER QUANTITY PROCURED

CLIN Range 1 Range 2 Range 3

Breakpoints to be Proposed by Contractors

List Spare Parts Individually 7002 Pricing here for each unit

Pricing here for each unit

Pricing here for each unit

Continue Lines as needed. 7002

SECTION I - CONTRACT CLAUSES

52.216-10 INCENTIVE FEE (JUN 2011)

(a) General. The Government shall pay the Contractor for performing this contract a fee determined as provided in this contract.

(b) Target cost and target fee. The target cost and target fee specified in the Schedule are subject to adjustment if the contract is modified in accordance with paragraph (d) below.

(1) "Target cost," as used in this contract, means the estimated cost of this contract as initially negotiated, adjusted in accordance with paragraph (d) below.

(2) "Target fee," as used in this contract, means the fee initially negotiated on the assumption that this contract would be performed for a cost equal to the estimated cost initially negotiated, adjusted in accordance with paragraph

(d) below.

(c) Withholding of payment.

(1) Normally, the Government shall pay the fee to the Contractor as specified in the Schedule. However, when the Contracting Officer considers that performance or cost indicates that the Contractor will not achieve target, the Government shall pay on the basis of an appropriate lesser fee. When the Contractor demonstrates that performance or cost clearly indicates that the Contractor will earn a fee significantly above the target fee, the Government may, at the sole discretion of the Contracting Officer, pay on the basis of an appropriate higher fee.

(2) Payment of the incentive fee shall be made as specified in the Schedule; provided that the Contracting Officer withholds a reserve not to exceed 15 percent of the total incentive fee or $100,000, whichever is less, to protect the Government's interest. The Contracting Officer shall release 75 percent of all fee withholds under this contract after receipt of an adequate certified final indirect cost rate proposal covering the year of physical completion of this contract, provided the Contractor has satisfied all other contract terms and conditions, including the submission of the final patent and royalty reports, and is not delinquent in submitting final vouchers on prior years' settlements.

The Contracting Officer may release up to 90 percent of the fee withholds under this contract based on the Contractor's past performance related to the submission and settlement of final indirect cost rate proposals.

(d) Equitable adjustments. When the work under this contract is increased or decreased by a modification to this contract or when any equitable adjustment in the target cost is authorized under any other clause, equitable adjustments in the target cost, target fee, minimum fee, and maximum fee, as appropriate, shall be stated in a supplemental agreement to this contract.

(e) Fee payable. (1) The fee payable under this contract shall be the target fee increased by . . [OFFEROR TO FILL-IN] cents for every dollar that the total allowable cost is less than the target cost or decreased by [OFFEROR TO FILL-IN] cents for every dollar that the total allowable cost exceeds the target cost. In no event shall the fee be greater than [OFFEROR TO FILL-IN] percent or less than [OFFEROR TO FILL- IN] percent of the target cost.

(2) The fee shall be subject to adjustment, to the extent provided in paragraph (d) above, and within the minimum and maximum fee limitations in subparagraph (1) above, when the total allowable cost is increased or decreased as a consequence of (i) payments made under assignments or (ii) claims excepted from the release as required by paragraph (h)(2) of the Allowable Cost and Payment clause.

(3) If this contract is terminated in its entirety, the portion of the target fee payable shall not be subject to an increase or decrease as provided in this paragraph. The termination shall be accomplished in accordance with other applicable clauses of this contract.

(4) For the purpose of fee adjustment, "total allowable cost" shall not include allowable costs arising out of--

(i) Any of the causes covered by the Excusable Delays clause to the extent that they are beyond the control and without the fault or negligence of the Contractor or any subcontractor;

(ii) The taking effect, after negotiating the target cost, of a statute, court decision, written ruling, or regulation that results in the Contractor's being required to pay or bear the burden of any tax or duty or rate increase in a tax or duty;

(iii) Any direct cost attributed to the Contractor's involvement in litigation as required by the Contracting Officer pursuant to a clause of this contract, including furnishing evidence and information requested pursuant to the Notice and Assistance Regarding Patent and Copyright Infringement clause;

(iv) The purchase and maintenance of additional insurance not in the target cost and required by the Contracting Officer, or claims for reimbursement for liabilities to third persons pursuant to the Insurance Liability to Third Persons clause;

(v) Any claim, loss, or damage resulting from a risk for which the Contractor has been relieved of liability by the Government Property clause; or

(vi) Any claim, loss, or damage resulting from a risk defined in the contract as unusually hazardous or as a nuclear risk and against which the Government has expressly agreed to indemnify the Contractor.

(5) All other allowable costs are included in "total allowable cost" for fee adjustment in accordance with this paragraph (e), unless otherwise specifically provided in this contract.

(f) Contract modification. The total allowable cost and the adjusted fee determined as provided in this clause shall be evidenced by a modification to this contract signed by the Contractor and Contracting Officer.

(g) Inconsistencies. In the event of any language inconsistencies between this clause and provisioning documents or Government options under this contract, compensation for spare parts or other supplies and services ordered under such documents shall be determined in accordance with this clause.

(End of clause)

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

SECTION L

INSTRUCTIONS TO OFFERORS

L 1.0 General Information The Offeror shall submit all information required by this RFP. Failure to comply with the terms and conditions of the RFP may result in the Offeror being removed from consideration for award. The Offeror’s proposal shall be based on the requirements contained in this RFP (including those documents, exhibits, and other attachments to the RFP identified in Section J). The performance of this contract requires that the Offeror have a Secret facility clearance granted by a Military Department by the time of contract award.

The RFP will be made available only through the internet at:

http://www.fbo.gov

Offerors are hereby notified that from time to time, the Government may post additional information to the web site relating to this RFP (e.g. responses to questions, amendments, etc.). It is the Offeror’s responsibility to check the web site for any such information.

The Government will make a Technical Data Package (TDP) available to Offerors to review for information only.

The Offerors are free to decide the manner and extent to which they may choose to use the information provided in this Technical Data Package, but any reliance on the information provided in the Technical Data Package shall be at the Offerors’ own risk. The Government makes no warranty as to the information and data contained in the Technical Data Package, including as to the accuracy or usefulness of the information and data for purposes of the Offerors’ proposals under the current competitive procurement.

L 1.1 General Content Requirements The offer consists of and must include the following to be eligible for award:

• Cover Letter, providing the information outlined in FAR 52.215-1(c)(2). A statement that the offeror agrees to all terms, conditions, and requirements included in the solicitation. There shall not be any pricing information in the cover letter.

• Standard Form 33, “Solicitation, Offer and Award,” with blocks 13 through 18 completed by the Offeror.

• RFP Sections A through J, “Solicitation, Offer and Award.”

• RFP Section K, “Representation, Certifications and Other Statements of Offerors,” completed by the Offeror. Items which are not applicable should be marked N/A.

• RFP: Offerors must complete all areas of the RFP listed as Offeror fill-ins.

• Small Business Subcontracting Plan. The Offeror’s attention is directed to Section I clauses FAR 52.219-9 entitled Small Business Subcontracting Plan, DFARS 252.219-7003 entitled “Small Business Subcontracting Plan (DoD Contracts)” and FAR 52.219-16 entitled “Liquidated Damages – Small Business Subcontracting Plan”. As prescribed in FAR 19.708, Offerors other than small business concerns shall submit a subcontracting plan and that plan, once approved, shall be made part of any contract resulting from this solicitation. The Offeror’s Small Business Subcontracting Plan will be incorporated into the contract as an Attachment.

• Volume I, Executive Summary.

• Volume II, Technical Proposal.

• Volume III, Price Proposal.

L 1.2 Government Data Access

L 1.2.1 – Unclassified Data The Navy will provide Compact Disks (CDs) to Offerors for unclassified technical information related to the RTI procurement, see Section J Attachment “SOW Addendum 2” for a list of GFI. Requests for CDs shall be sent to the Contract Specialist, Melissa Ardis, via email, melissa.ardis@navy.mil.

The subject line in the email should read “RTI procurement data CD”. See Section A, “Distribution of GFI” for further instructions.

Information provided, under this RFP, is for the sole purpose of bidding on the RFP and no information therein shall be disclosed for any other purpose.

L 1.2.2 – Classified Data If there are portions of the GFI data which are classified, they will not be provided with the procurement data CD.

Requests for this data shall be sent to the Contract Specialist, Melissa Ardis, via email, melissa.ardis@navy.mil in accordance with the instructions in Section A, “Distribution of GFI”. No classified Bidders questions shall be submitted for this RFP; however, questions regarding classified material may be asked in an unclassified manner.

L 1.3 Specificity Required for the Proposals

Proposals will be evaluated in accordance with the Evaluation Factors for Award (SECTION M) of this RFP.

Offerors shall submit proposals that are sufficiently detailed and complete in order to fully demonstrate understanding of, and compliance with, all of the requirements of the RFP and shall contain only material directly related to this acquisition.

A legible, neat, orderly and comprehensive proposal is required. Elaborate brochures or artwork, expensive paper or bindings, or expensive visual or presentation aids beyond those sufficient to present a complete and comprehensive proposal are neither necessary nor desirable. Offerors shall follow the general rule that quality of information is significantly more important than quantity or visual esthetics of presentation. Each Offeror is responsible for the condition of its delivered proposal. Binders and their contents that are broken apart or received in a disorderly fashion will be reassembled by the Government in a manner with expeditiousness as the rule. The Government is not responsible for proper reassembly of these binders. Thus binders may not be reassembled as originally sent.

General statements such as “the Offeror understands”, “the Offeror can or will comply with the requirements”, “standard procedures will be used”, “well-known techniques will be used”, or statements which merely paraphrase the RFP in whole or in part will not constitute compliance with the requirements for proposal content and will be interpreted as a lack of understanding. Data previously submitted, or presumed to be known (e.g., data or services previously submitted or performed for the Government), cannot be considered as part of the proposal unless physically incorporated into the proposal. Failure to conform to all requirements of this RFP may form the basis for rejection of the proposal.

mailto:melissa.ardis@navy.mil mailto:melissa.ardis@navy.mil

In the event that any portion of the proposal is written by anyone who is not a bona fide employee of the firm submitting the proposal, a certificate to this effect shall be furnished which must be signed by an authorized official of the Offeror and shall indicate the person’s name, employment capacity, firm name, relationship of that firm to the Offeror, and which portion of the proposal was written by that person.

L 1.4 RFP Response Requirements

Each Offeror shall submit a proposal in response to this RFP subject to the following requirements.

The RFP response will be contained in three separate Volumes, delivered by 2:00PM LOCAL time on the date identified in Block 9 on page 1.

VOLUME TITLE PAGE LIMIT ORIGINALS COPIES CD ROMS

I Executive

Summary 3 1 1 12

II Technical Proposal

75 1 1 12

III Price Proposal None 1 1 2 IV Classified

Annex (As needed)

None* 1 1 1

* Note: Vol. IV, Classified Annex pages are included in the page count for Volume II (Technical Proposal).

The electronic proposal material shall not contain any information not contained in the hard copy format. In the event of disparities between hardcopies and electronic information, the hardcopy governs. Disks shall be CD-Read Only Memory (ROM) formatted and all documents, spreadsheets, databases, or other data submitted must be compatible with Microsoft Office 2007, Microsoft Project 2007, and Adobe Acrobat 9. The information contained within the CDs shall not be locked such that formulas are able to be viewed. Original documents created in Word, Access, Excel, or equivalent shall be the actual workable documents, and not scanned Portable Document Format (PDFs). All Microsoft Excel files shall be completely readable and editable, as to ascertain the validity of the pricing or other data contained therein. All Adobe Acrobat files shall be word-searchable.

The narrative material in the hardcopy proposal shall be typed or printed in a font with the type no smaller than size 12 point Times New Roman font on standard 8-1/2 x 11 inch paper. Text line spacing shall be 1.5 lines. One-inch minimum margins on each side, including top and bottom are required. Text within tables, diagrams, pictorial charts, or graphic material may use no smaller than size 8 point Times New Roman font. Every paragraph, figure, and table shall be numbered; paragraphs within sections do not need to be numbered. Proposal material shall be presented on double-sided pages only and in a single column on each page (refer to Section I, FAR 52.204-4). Each double-sided page counts as 2 pages. Pages are to be numbered sequentially and tabs are to be used for chapter breaks. Proposals that restart page numbering every chapter within an individual volume will not be acceptable. Each page shall be labeled with the Offeror’s name, the RFP number, and the proposal disclosure position in accordance with FAR 52.215-1. A page is defined as a typed page of the proposal document, i.e. one sheet of 8-1/2 x 11 paper with typing on one side. All volumes shall be submitted in three-ring binders with index tabs or tabbed index divider pages indicating sections which correspond to those set forth below.

Proposals containing data that is not to be disclosed to the public for any purpose or used by the Government except for evaluation purposes shall include the following statement on the cover page: “This document includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed – in whole or in part – for any purposes other than evaluation. If, however, a contract is awarded to this Offeror as a result of – or in connection with – the submission of this data, the Government shall have the right to duplicate, use, and disclose this data to the extent provided in the resulting award document. This restriction does not limit the Government's right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets marked "Proprietary" or that contains the legend prescribed by FAR 52.215-1.”

Each volume shall be bound separately and shall not exceed the page limitation cited above. A date shall be placed on each page of the proposal corresponding to the date of the initial proposal. Any pages that may be revised as a result of discussions (if required) shall contain revision numbers and dates.

Elaborate artwork, expensive visual or other presentation aids are neither necessary nor desired. The Proposal shall contain all the pertinent information in sufficient detail to permit evaluation. The proposal shall be so detailed and complete as to clearly demonstrate that the Offeror has a thorough comprehension of all technical and other requirements. If an Offeror fails to comply with content requirements its proposal may be downgraded for failure to follow instructions.

Pages excluded from the page count for each volume are the cover letter, title pages, tables of contents, tabbed index divider pages, resumes, and glossaries. Any other content that is excluded from the page count will be addressed in the section for that particular volume. Any pages intended to be blank shall be marked, "Intentionally Left Blank."

Index pages and Tabs are required and shall be cross-referenced to the TOC. If the proposal volume exceeds the page limit, the Government will remove all pages exceeding the specified page count from the back of the proposal volume prior to the evaluation and will not review these pages. These pages will not be removed from the index or appendices provided at the back of the proposal volume.

Offerors are cautioned that, in accordance with the “Instruction to Offerors-Competitive Acquisition” clause (FAR 52.215-1), the Government intends to award a contract on the basis of initial proposals received, without discussions. Therefore, each proposal shall contain the Offeror’s best terms from a cost and technical standpoint.

Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements, which prevent concise proposal evaluation. Each factor will be evaluated on how well the response meets the requirements of the RFP. The response that completely addresses all of the RFP requirements may be judged superior to the response that minimally addresses RFP requirements under evaluation factors.

If an award is not made on the basis of initial proposals, the Contracting Officer will make the determination as to which proposals are in the “Competitive Range.” The competitive range shall be determined based on the results of the evaluation of initial Technical and Cost Proposals, considering all evaluation criteria, and shall include the most competitive proposals.

It is the Government’s intent to award on initial proposals, however it reserves the right to conduct discussions. If discussions are held, Offerors selected to participate in discussions shall be advised of weaknesses and risks in their proposals, and shall be offered a reasonable opportunity to correct or resolve such weaknesses and risks and to submit such technical and cost information, or other revisions to their proposals, that may result from such discussions.

Proposals in response to this solicitation shall be valid for a period of 240 calendar days from the date the original proposal was submitted.

L 1.5 Format of Electronic Submissions (CD ROMs)

The CDs for Volumes I and II contents shall not be in a "read only" format or in scanned PDF format. For Volume III, any spreadsheets shall be "unlinked" to allow for review during cost/price analysis on all of the CDs. The pricing spreadsheets generated must replicate the format of Tables L-1 and L-2. All cells containing derived data shall be presented together with the formulas used to derive the data. This is only for evaluation purposes. In the event that situations arise which necessitate the submission of revised information, to include pricing, technical, or other items, the revisions shall adhere to same instructions of SECTION L. Additionally, any spreadsheets, word processing documents, or other information shall be submitted in a working document form to permit the validation of submitted information. The electronic version shall not contain spreadsheet or word processing documents that have been changed, printed, and then scanned to a PDF or other file that cannot be readily used to verify the accuracy of pricing or other information.

CD ROMs, as required above, shall be attached to the proposal such that they do not fall out or become dislodged during transport and handling.

L 1.6 Cross Referencing

Cross referencing between sections within Volumes I-II and IV is permitted where its use would conserve space without impairing clarity. However, each factor response within a given volume of the proposal shall be written to the greatest extent possible on a stand-alone basis so that its content may be evaluated with minimal cross referencing to other factors within other volumes of the proposal. Where cross referencing is necessary, Offerors must cite the specific factor, page number, section or paragraph for reference. Information required for each factor, which is not found in its designated factor or properly cross referenced, will be assumed to have been omitted from the proposal. Cross referencing between Volumes I-III is not permitted.

L 1.7 Glossary of Abbreviations and Acronyms

Each volume of the Proposal shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against page limitations for their respective volumes.

L 1.8 Questions from Offerors

Offerors may electronically submit written questions by sending an email to the Contract Specialist, Melissa Ardis, at melissa.ardis@navy.mil. All questions should be posted in an unclassified manner. Answers to bidders’ questions will be posted on the Federal Business Opportunities (FBO) website. Offerors are required to periodically check the FBO Web page for information concerning the requirement, responses to questions, and any issued amendments. All such questions should be received in writing within twenty calendar days after release of the RFP to allow the Navy adequate time to prepare and issue responses to all Offerors prior to the date and time set for receipt of proposals. Only questions transmitted electronically will receive a response. The Navy will continue to accept questions up to the closing date and time of the RFP; however, time may not permit responses to be issued prior to proposal receipt. Questions received after the time set forth above will not result in an extension to the proposal due date. It is the Government’s intention that questions and responses will be distributed electronically to all Offerors.

Information provided with each question should include the document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification.

L 1.9 System for Awards Management (SAM) All Offerors submitting proposals must:

a) Be registered in the SAM (formerly the Central Contractor Registry (CCR)) prior to submission;

b) Maintain an active SAM registration with current information at all times during which it has an active

Federal award or an application under consideration by any agency; and

c) Provide its DUNS number in each application or proposal it submits to the agency.

The SAM is a free web site that consolidates the capabilities you used to find in CCR/FedReg, ORCA, and EPLS.

Future phases of SAM will add the capabilities of other systems used in Federal procurement and awards processes.

Offerors may access SAM at https://www.sam.gov/portal/public/SAM/ NOTE TO FORMER CCR REGISTRANTS: If you had an active record in CCR, you have an active record in SAM. You do not need to do anything in SAM at this time, unless a change in your business circumstances requires a change in SAM in order to receive a payment or award. SAM will send notifications to the registered user via e-mail 60, 30, and 15 days prior to expiration of the record. You can search for registered entities in SAM by typing the DUNS number or business name into the search box.

L 1.10 Volume I – EXECUTIVE SUMMARY https://www.sam.gov/portal/public/SAM/

The Executive Summary Volume shall be unclassified. The Executive Summary shall summarize the proposed technology improvement, as well as any innovative claims, and the Offeror’s experience, capabilities and past performance in this area. The Offeror shall include a Quad Chart, using Microsoft Office Power-Point compatible formats, showing a graphic of the technology, problem solved or benefits provided, technical approach, and schedule. Title Pages, cover pages, glossaries, tabbed dividers, and table of contents shall not be subject to the page limitations, will not be evaluated, and shall not be numbered. Price information shall be completely omitted from the Executive Summary Volume. The Executive Summary shall not be evaluated.

L 2. Volume II - TECHNICAL PROPOSAL Offerors are permitted to submit classified data as part of their technical proposal in accordance with the DD 254.

Pages of the proposal that contain this data shall also be marked in accordance with the DD 254. Classified pages are included in the page count.

The Technical Proposal Volume shall be limited to the page count specified in paragraph 1.4 above. Pages in excess of the page limit will not be read or evaluated. Title Pages, cover pages, glossaries, tabbed dividers, and table of contents shall not be subject to the page limitations, will not be evaluated, and shall not be numbered.

Volume II shall contain, as necessary, any alternative specifications or standards in accordance with “Alternatives to Specifications or Standards (NAVSEA) (AUG 1994) and the initial Software Development Plan (SDP) for software projects (as an attachment, not included in the page count). Price information shall be completely omitted from the Technical Proposal Volume.

Foldouts shall be used only where needed, i.e., engineering drawings, diagrams, and schematics, in the Technical Proposal volume not to exceed 6 foldouts. Extensive written text or tabular data, beyond that reasonably required for clarity shall not be included in the material presented on the foldout sheet. Each foldout shall contain printed material on only one side of the foldout. Foldout pages shall fold entirely within the particular volume. Foldouts shall fold from left to right (sideways), shall not exceed 11” in height, shall count as one page, and shall not exceed three (3) folds.

The Technical Proposal Volume shall enable technical/engineering personnel to make a thorough evaluation and arrive at a sound determination of whether or not the proposal meets the requirements of the RFP. To this end, the Technical Proposal Volume shall be specific, detailed, and complete. Proposals shall include the block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror's proposed concept. The technical section must be sufficient to show how the Offeror proposes to comply with the Government's requirements and include a full explanation of the methodology and procedures to be followed. The following is an outline of the information required to be addressed in the Technical Volume and shall be addressed in the following order:

Technical Proposal, Volume II

Title page Table of contents (including Figures, Tables, and Appendices) Glossary of acronyms and abbreviations

2.1 Technology Maturity

2.2 Technical Approach

2.2.1 Primary Engineering Measurement Parameter

2.2.2 Secondary Engineering Measurement Parameter

2.2.3 Technical Rationale / Substantiation

2.2.4 LCS Compatibility

2.2.5 Software Development Plan Rationale

2.3 Life Cycle and Sustainment

2.3.1 Reliability and Availability

2.3.2 Support (Maintainability) Approach

2.3.3 Manning / Training Approach

2.3.4 Manufacturing Plan, Processes, and Technologies

2.4 Rights in Technical Data and Computer Software

2.5 Management Organization and Schedule

2.5.1 Management Organization

2.5.2 IMS

2.5.3 Staffing and Key Personnel

2.5.4 Small Business Participation

2.6 Past Performance

2.6.1 Relevant Past Performance

2.6.2 Self Assessment

The Offeror shall provide detailed discussion for each of the following sections and content requirements, and discuss how and when the contract phases affect their proposed engineering approach.

L 2.1 Technology Maturity.

Proposals shall provide all of the following:

• Show evidence such as measurements, test results, or evidence of working component prototype(s) or mature system(s) in a relevant environment;

• Show evidence that the technology maturity of the proposed RTI project is sufficient to support the requirements of Phases I and II within 27 months of initial award

• Identify the essential technologies and evidence of their maturity, previous use, and any planned testing to mitigate risks, if needed;

• Identify evidence of previous testing, shipboard installation, production/fielding, or naval system integration for similar technology or essential technology elements.

L 2.2 Technical Approach L 2.2.1 Primary Engineering Measurement Parameter (PEMP).

Discuss how the offer provides benefit to the LCS in resolving technical challenges as defined by the Primary Engineering Measurement Parameter (PEMP) value. Discuss how much improvement is being obtained for the PEMP as defined by the Technical Topic Appendix, and how this will be measured and monitored through the design and test process. Discuss current technical performance of the technology or baseline, how the performance levels will change as a result of the project, and how much margin will be provided compared to the PEMP performance level needed. Provide actual data to backup performance claims, and explain how data will be collected during and after the project to prove performance levels. Provide details on the technology improvement(s) being proposed. Show how planned testing in the RTI schedule will resolve any key issues and demonstrate performance. Full compliance with the RFP provided SOW shall be referenced by the Technical Approach. Provide previous test results, modeling data, or simulation results that show the projected performance levels and compare that to the desired metrics as well as current product capability or performance.

Provide a Technical Performance Statement (TPS) that details the magnitude and the proposed PEMP performance resulting from the project. Full compliance with the RFP provided SOW shall be referenced by the TPS. The TPS may be provided as a draft, revised, or updated specification document or requirements verification traceability matrix. The Government anticipates that the proposed TPS will be incorporated as an attachment to the resultant award instrument, and the Offeror shall acknowledge that restrictions or markings as prescribed by FAR 52.215-1 can be removed after contract award. The TPS shall reside below the Specifications in the Order of Precedence.

Offerors should use the format of Table 3, Engineering Measurement Parameters, from the SOW Technical Topic Addendum, in creating the TPS.

L 2.2.2 Secondary Engineering Measurement Parameter (SEMP). Discuss how the offer provides benefit to the LCS in resolving technical challenges as defined by the Secondary Engineering Measurement Parameter (SEMP) value. Discuss the impacts to, or expected performance in, the Secondary Engineering Measurement Parameter (SEMP), how they are expected to change or be affected, and how and when they will be measured.

Discuss current technical performance of the secondary parameters of the technology or baseline, how the performance levels will change as a result of the project, and what performance level will be achieved. Provide actual data to backup performance claims, including relevant contextual information (e.g. test environment), and explain how data will be collected during and after the project to demonstrate performance levels. Full compliance with the RFP provided SOW shall be referenced by the Technical Approach. Provide previous test results, modeling data, or simulation results that show the projected performance levels and compare that to the desired metrics as well as current product capability or performance.

For the SEMP the Offeror shall provide Technical Performance Statement (TPS) or Specification Sheet that details the magnitude and the proposed performance resulting from the project. Full compliance with the RFP provided SOW shall be referenced by the TPS. The TPS may be provided as a table, draft, revised, or updated specification document, or requirements verification traceability matrix. The Government anticipates that the proposed TPS will be incorporated as an attachment to the resultant award instrument, and the Offeror shall acknowledge that proprietary restrictions or markings can be removed after contract award. The TPS shall reside below the Specifications in the Order of Precedence. Offerors should use the format of Table 3, Engineering Measurement Parameters, from the SOW Technical Topic Addendum, in creating the TPS.

L 2.2.3 Technical Rationale / Substantiation: The Offeror shall submit a clear explanation of how they will achieve and show the performance levels described in the RFP, including, the tasks to be completed, the technical approach, and the deliverables. Describe the approach to be used for each of the design stages and functional areas, including the any prototypes and the planned testing and verification methods. Discuss the design steps using the NAVSEA Technical Reference Manual (TRM) as a reference for describing the proposed systems engineering and integration activity. Describe the risk relevant to support the requirements of RTI Phases I and II within 27 months of initial award and how it will be mitigated or how margin and schedule slack is built into the project in advance through pre-planning and early investment. Identify any dependencies and assumptions that are critical to the project success..

L 2.2.4 LCS Compatibility The Offeror shall describe in detail how the proposed design accommodates or improves on the existing constraints for Weight Management, Physical Interfaces, and Data Interfaces, for integration of the new technology with the LCS Ship and its Mission Modules, including the TSCE and MPCE. Discuss the compatibility of the new technology with the LCS, what changes would be needed (if any) to integrate the new technology into the ship or MM, and if and how the ship or MM would be impacted by the technology or capability from a physical, size, weight, power, and ship-alteration aspect.

Discuss compatibility with Interface Control Drawings (ICDs) and Interface Design Specifications (IDS) and changes needed (if any) to accommodate the technology, and compatibility with general Naval Ship standards of design and construction. Discuss the human interface, and whether the typical sailor will be able to easily interact with the technology or software, and what training may be needed for them to be successful.

The Offeror shall provide an SRVM which provides traceability of the proposed PEMP and SEMP performance levels to the LCS Ship and Mission Module environmental requirements, including the analysis/test method and test event that proves compliance for each of the RTI engineering parameters.

L 2.2.5 Software Development Plan (SDP), Applicable to projects with more than 5,000 equivalent software source lines of code:

HQ L-2-0016 SOFTWARE DEVELOPMENT PLAN (NAVSEA) (DEC 2006)

(a) As part of the proposal, offerors shall submit an initial SDP that at a minimum addresses the requirements of Section C. The initial SDP shall not be subject to the technical proposal page limitation of the solicitation. Offerors are advised however, that initial SDPs, which are concise and well-written, may receive more favorable consideration than those that contain extraneous material and/or brochuremanship.

(b) Offerors shall also submit an SDP rationale which describes why their specific approach is appropriate for the system to be procured, developed or maintained and how their proposed processes are equivalent to those articulated by CMMI® capability level 3.

The SDP rationale is subject to the technical proposal page limitation of the solicitation and shall not exceed 10 pages.

HQ L-2-0017 SOFTWARE DEVELOPMENT AND CMMI OR EQUIVALENT

EXPERIENCE (NAVSEA) (DEC 2006)

(a) Offerors shall submit a description of previous relevant experience, within the past 36 months in developing software of the similar size and complexity as that required under the statement of work. As a part of this description, the offerors shall describe the extent to which personnel who contributed to these previous efforts will be supporting any resultant contract.

(b) Offerors shall also describe any previous relevant CMMI® or equivalent model-based process maturity appraisals performed within the past 24 months. As a part of this description, offerors shall identify the organizational entity and location where the appraisal was performed, the type of evaluation, the organization performing the evaluation, and the level earned. This description shall not exceed 2 pages.

(c) The descriptions called for under paragraphs (a) and (b) above are subject to the technical proposal page limitation of the solicitation.

L 2.3 Life Cycle & Sustainment L 2.3.1 Reliability & Availability. Provide real or estimated reliability and availability performance levels, and show how the new technology meets mission success criteria. Provide data to justify performance claims.

L 2.3.2 Support (Maintainability) Approach: Discuss the methods of sustaining and supporting the technology when in operational use, including the proposed maintenance concept and skill levels and equipment needed.

Provide rationale for the provisioning approach used including depth of spare parts needed at the operational, intermediate, and depot level.

L 2.3.3 Manning / Training Approach. Discuss the impacts to ship’s manning, and the training requirements to operate and maintain the technology.

L 2.3.4 Manufacturing Plan, Processes, and Technologies: Discuss any special manufacturing processes, facilities, or equipment needed to produce the technology. Address the manufacturing plans, including Quality Assurance, Configuration Management, Environmental Stress Screening, production testing program, how quality will be maintained in for all units manufactured, parts standardization program, and manufacturing training/certification. Discuss the production test strategy, including component testing and acceptance criteria for components received from subcontractors, execution of the Factory Acceptance Test and what other testing procedures are to be used. Clearly explain any differences that would exist between the initial unit and production unit design or testing approach.

The Offeror shall describe the approach to manufacture, test, and deliver the RTI products or systems in accordance with the requirements of this RFP, providing detail on innovative design and manufacturing approaches and the associated risks from contract award through Government acceptance.

The Offeror shall describe the manufacturing technologies intended for use in the manufacturing effort and elaborate on any changes to the current manufacturing approach used for the product, including a risk mitigation plan for each change required. The Offeror shall identify any proprietary manufacturing processes and technologies that may be employed in the manufacturing effort, and explain how these can be accommodated or reverse engineered by other suppliers if necessary.

L 2.4 Rights in Technical Data and Computer Software Identify any intellectual property (IP) claims associated with the project. Specifically justify the use of any proprietary, vendor-unique, or closed components including, but not limited to, hardware, software, and interfaces in current or future designs;

• The Government desires Government Purpose rights so that it can meet its life cycle requirements, including independent construction, upgrade, repair, and maintenance of the RTI technology . The Offeror shall provide an explanation on the data rights they shall deliver and how it intends to deliver these rights to the Government.

• Proposals that propose technology derived from Small Business Innovation Research (SBIR) or Small Business Technology Transfer (STTR) projects are welcome. The SBIR or STTR technology may originate in any Federal agency. SBIR proposals should clearly show whether, after contract award, the Offeror plans to retain any data rights or explain the desired terms for relinquishing, transferring, selling, leasing, or changing data rights subsequent to contract award.

Provide a clear graphical depiction of how open the configuration items and interfaces are within the technology or system, with both hardware and software views of the architecture.