14-R-0008-0001_Solicitation.pdf

1XXXXXXXX

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

The purpose of this amendment is to update the Government point of contact for questions on the solicitation and give a POC for the 3 draw ings that w ere inadvertantly left out of the TDP package as show n herein:

1. CONTRACT ID CODE PAGE OF PAGES

J 1 13

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

16C. DATE SIGNED

BY 15-May-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 N68936-14-R-0008

X 9B. DATED (SEE ITEM 11)

30-Apr-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 is extended, X 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

15-May-2014

CODE

CDR NAWCWD CODE 254300D

ATTN: R. FISHER

(760) 939-8366

429 E BOWEN RD - STOP 4015

CHINA LAKE CA 93555

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N68936-14-R-0008

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

POC FOR DRAWING PACKAGE

To receive the 3 drawings that were inadvertantly left out of the TDP, please contact Jo-Ellen Poston at joellen.poston@navy.mil.

The following have been modified:

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L – [1] CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(JUN 2011) (Nov 2013)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

The Offeror is required to submit sufficient information concerning the following areas to enable Government personnel to fully ascertain capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the Offeror’s capability to meet the defined elements as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the requirements, associated risks and is able, willing and competent to devote the resources necessary to meet the requirements, and that the Offeror has valid and practical solutions for all requirements and potential risk areas. Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror has the burden of proof to demonstrate compliance with all the evaluation factors identified in this solicitation. With the exception of the Price/Cost volume, no cost or pricing information should appear in any volume. Alternate proposals are not acceptable.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. The Offeror is responsible to present enough information to allow the Government to evaluate the proposed work effort, support, and approach, as well as the price/cost proposal without opening discussions. Statements that the prospective Offeror understands, or can and/or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may render a rating of unacceptable. For the purpose of this solicitation, relevance is defined as something that has a logical connection with the matter under consideration. Such aspects of relevance include the type of effort (e.g., development, production, repair), the type of requirements (e.g., weapon systems, information systems, engineering services, scheduled depot maintenance), service similarity, service complexity, contract type, contract dollar value, the division of the company that will perform the work, and degree of participation by principal subcontractors, team members, or critical team members. Recency is defined as performance within 3 years of the date of this proposal submission.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor clearly may be considered technically unacceptable.

There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond what is sufficient to present a complete and effective proposal is neither necessary nor desired.

The Offeror is expected to comply with all requirements of the RFP. The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the proposal un-awardable, unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition. The Government may consider any exception or deviation to any term or condition of the RFP that is not expressly authorized by the RFP to be technically unacceptable.

Throughout these instructions, a “principal subcontractor” is defined as a subcontractor who provides at least 10% of the proposed total price/cost (excluding the Offeror’s profit/fee), for the contract. “Team member” is defined as those entities that make up a joint venture or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. “Critical team member” is defined as those entities of the Offeror that perform a critical function in the performance of the resulting contract, whether it is technical or financial.

2.0 PROPOSAL FORMAT

Written proposals must be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. All pages should be numbered with section and page numbers. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 point font and should contain a grid, which allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented.

The Offeror will provide one complete copy of the writtten proposal to the Procuring Contracting Officer (PCO) as electronic files on a CD-ROM fully compatible with Microsoft Office 2003 and for information not supported by MS Office products, use Adobe Acrobat reader. The Offeror will ensure that the Price/Cost Volume is provided on a separate CD-ROM with all data and cell formulas, in Microsoft Excel. Each CD-ROM is to be labeled with volume number, volume title, solicitation number, and the Offeror’s name.

The Offeror must present proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that its paragraph number/letter is identical to the Proposal Instructions paragraph number/letter to which it is responding, although the Offeror may add lower tier subparagraphs. The Offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the volume, book, section, and element, etc., in the Offeror’s proposal.

3.0 PROPOSAL CONTENT AND VOLUMES

Each volume of the proposal shall be submitted as two originals and one CD-ROM. The table below supersedes the copies requested in Block 9 of the Standard Form (SF) 33. All volumes of the original proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation, Block 9 of Standard Form

33. Page limitations for each volume are also specified in the table below; title and table of contents pages do not count towards page limit. Proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation.

Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Part B Specific Instructions. Annexes do not have page limitations. The authorized volumes are summarized in the table below.

Volume Number Volume Title Page Limit Copies Required

1 EXECUTIVE

SUMMARY

5 2 originals and one CD-ROM

2 TECHNICAL 75 2 originals and one CD-ROM

3 PAST PERFORMANCE 15 2 originals and one CD-ROM

4 PRICE/COST 15 2 originals and one CD-ROM

Each volume shall contain the following information:

Cover and title page Title of proposal and proposal number as applicable Offeror’s name, address and POC RFP number Proposal volume/book number Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements) Use tabs and dividers

The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the Offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The Offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

Section L – Proposal Instructions Government SOW

Section M – Evaluation Factor Offeror’s Proposal Reference

CLIN

Reference

Section L – Proposal Instructions Government SOW

Section M – Evaluation Factor Offeror’s Proposal Reference

CLIN

Reference

Volume 2 Technical

Example: Para 3.1 Note: This column shall address all paragraphs in Sections xx and xy of the

SOW

2.A Provide reference to Offeror’s Proposal Volume I – Technical.

Example: Refer to appropriate page number in Offeror’s written proposal

4.0 PROPOSAL SUBMISSION:

Clearly mark all packages with the solicitation number. The submission date for the original proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP. Offeror shall submit proposals via United States Postal Service or through a commercial carrier using the address provided below. Offeror shall not submit proposals via facsimile or electronically via email.

Commander

NAWCWD (254340D)

Attn: Robert Fisher 429 E. Bowen Road, Mail Stop 4015 China Lake, CA 93555-6108

Hand carried proposals may be delivered to the address above, attention Robert Fisher.

5.0 PROPOSAL PACKAGING:

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Each container shall be single person portable. One container shall include all Original Proposal volumes including the original/signed documents submitted as part of Volume 1 Executive Summary.

Each container should include a packing slip detailing the contents to include the volume number, and title. Also, each container should be stamped or marked “For Official Use Only” and “Source Selection Information – See FAR-2.101 and 3.104”.

6.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED

7.0. SOLICITATION QUESTIONS

The Contract Specialist is the sole point of contact for this acquisition. Address any questions, concerns, or requests for clarification you may have, in writing, to Robert Fisher at robert.v.fisher@navy.mil and Amanda Bartel at amanda.bartel@navy.mil. It is requested that each question reference the applicable document, paragraph, and page.

Questions containing proprietary information shall not be submitted. Questions answered by the Government will be provided to all potential Offerors via an amendment to the solicitation. It is requested that all questions be received within five (5) days of the date this solicitation was posted. All questions received more than ten (10) days after the original posting of this solicitation will not be answered.

8.0 SOLICITATION CHANGES

For any changes and additional information for the solicitation please go to website: https://www.fbo.gov

PART B SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to cost or price aspects of the offer.

The purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s proposal and strategy. The Offeror shall include the following in this volume:

i. A concise abstract of the Offeror’s strategy for each of the non-cost/price evaluation criteria contained in the solicitation.

ii. Offeror Summary Table: The Offeror shall complete the table below. The Offeror should include all subcontractors and team members who will be involved with the performance or management of the program work and should list all sites where the work will be performed. If a teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below.

Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Contractor Name (Indicate Prime, Team Member or Sub)

Place of Performance/DUNS # if applicable

Brief Work Description and/or Program Responsibility

% of Total Proposed Price

iii. Signed SF33 for basic solicitation and each amendment

iv. Signed Representations, Certifications and Acknowledgements or System for Award Management (SAM) reference

v. Affirmation of no Exceptions, Deviations or Waivers

vi. Guarantee the length of proposal validity for at least 180 days after proposal submission.

vii. Written consent from principal subcontractors and critical team members that will allow the Government to coordinate potential past performance and/or cost/price issues with the Offeror.

2.0 VOLUME 2: TECHNICAL

2.1 The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall address the following in the proposal:

2.1.1 Technical Approach. Describe the planned technical approach for fulfilling the Government’s technical requirements.

2.1.2 Reliability. Describe the planned approach to satisfy the reliability requirements within the applicable drawings identified in the Statement of Work.

2.1.3 Quality Assurance. Describe the planned approach to satisfy the Quality Assurance (QA) Requirements within the Specifications and Statement of Work including a detailed discussion on internal QA processes. If the Offeror proposes an equivalent Quality System Model in accordance with FAR Clause 52.246-11, the Offeror shall provide detailed information on the system, including how it is comparable to the ISO 9000 and ANSI/Q9001/Q9003 systems. (Note that MIL-I-45208 or MIL-Q-9858, if proposed by the Offeror, is an acceptable substitution). Offeror shall describe how the proposed quality system will control the quality of the program in the design, qualification and production phases. The QA program shall address material and parts selection, process control, workmanship, inspection and configuration management for both development and production.

2.1.4 Experience. Provide information that describes the Offeror’s experience with fabricating and producing systems like those required for this contract. Specifically describe previous units produced and when they were delivered to the Government. Provide examples of experience demonstrating the similarity of the effort in terms of fabrication and production technologies that will be utilized to fulfill the requirements of this contract as well as the Offeror’s ability to sustain production and modification efforts simultaneously.

2.1.5 Obsolescence. The contractor shall show sufficient market research and address any potential obsolescence issues.

3.0 VOLUME 3: PAST PERFORMANCE

3.1 General

The Offeror shall identify any contracts performed within three years of this proposal submission date which contains efforts similar to those performed by Offeror, Offeror’s principal subcontractors, and critical team members in solicitation. e.g., tasks, complexity, contract type, contract dollar value, etc. Commercial contracts may be included. List the contracts from the most relevant to the least relevant. In general, recent performance will be considered more relevant than older performance. When possible, these contracts should include at least five of the most relevant contracts for the prime contractor, five of the most relevant contracts for each critical team member, and two of the most relevant contracts for each principal subcontractor (as defined in Paragraph I, General Instructions). If proposing as joint venture/single legal entity (JV/SLE), the Offeror should provide the five past performance references for the JV/SLE. If less than the five past performance references are available for the JV/SLE, each member of the JV/SLE should individually submit the five references in addition to their JV/SLE references.

For each contract identified, provide contract data, relevancy, past performance, and systemic improvement information as described below. Demonstrate the relevancy of the Offeror’s, and if applicable, the Offeror’s principal subcontractors’ or critical team members’ past performance and systemic improvements with respect to the solicitation requirements. For each past performance problem identified, describe the status of the systemic improvement efforts and, where applicable, demonstrate the impact that the systemic improvement effort had on resolving the problem such that it would not reoccur.

For contracts that have CPARS Reports that are more than six months old (e.g., the completion date is more than six months before the due date for this Past Performance Volume) the Offeror will forward a copy of the CPARS Update Questionnaire (Attachment P1) to that contract customer’s Program Manager. For all contracts identified which do not have CPARS reports, the Offeror will forward a copy of the Past Performance Questionnaire (Attachment P2) to that contract customer’s PCO, Administrative Contracting Officer, and Program Manager. All questionnaires shall be forwarded to respondants two weeks prior to the submission date/time specified in Block 9 of Standard Form 33 of the RFP. The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to Robert Fisher, Contract Specialist, at Email robert.v.fisher@navy.mil, thereby allowing the customer approximately two weeks to complete their response. This submittal information is provided at the top of the questionnaires to facilitate the Offeror’s effort in meeting these instructions. The Offeror shall not conduct follow-up actions with regard to this questionnaire.

The Offeror shall provide written consent from their principal subcontractors and critical team members that will allow the Government to coordinate their Past Performance issue(s) with the Offeror. If the Offeror does not submit such written consent, then the Government will address any past performance issues directly with the principal subcontractor or critical team member and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractors and critical team members that do not provide such written consent, provide a point of contact (name, address, phone number, and email address) with which the Government may coordinate these issues and obtain any responses as needed.

The Government may use information other than that provided by the Offeror in their proposals to evaluate past performance. The Government may use Past Performance information obtained from sources other than those identified by the Offeror. The Past Performance Information Reporting System (PPIRS) will be the primary method used to evaluate Past Performance. It is incumbent upon the Offeror to explain the relevance of the data provided.

The Government has no duty to search for data to cure the problems it finds in the information provided by the Offeror. The Offeror has the burden of providing thorough and complete past performance information.

(a) Contract Data Provide all the information identified below separately for each contract. Additionally, provide this information electronically as a separate document file containing Offeror’s Past Performance proposal in a Word Table in the format depicted below:

Relevant Contract Data Prime (P), or Sub (S)

1. Contractor Name P1 P2 P3 P4 PX S1 SX

2. Title of contract

3. Contract number/type

4. Procuring agency

5. Description of product

6. Period of performance

7. CAGE Code/ DUNs #

8. Dollar value of contract

9. Acquisition Phase(s) of Contract, e.g., SDD, Production

10. CPARs? - CPARS completion date - on DOD PPIRS? 1

11. Recency 2

12. Relevancy 3

1CPARS (yes/no) - CPARS completion date - on DOD PPAIS (yes/no) (Indicate whether or not any CPARS have been completed and identify the last CPARS completion date and if it is currently on DoD PPAIS).

2 Recency-Efforts performed within the last three years.

3Relevancy – Provide a concise assessment of the degree of relevancy that each contract identified has to the solicitation; identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program.

Also provide the Offeror’s assessment of the relevancy of the contract in terms of one of the following ratings: Very Relevant (V), Relevant (R), Somewhat Relevant (S), or Not Relevant (N).

(b) Relevancy - The Offeror shall explain what aspects of the contract are deemed relevant to the proposed contract. At a minimum, identify key or critical tasks of the solicitation and indicate the relevancy of the “past performance” contract to these tasks. Also identify where contract performance took place and provide rationale why it is relevant to the solicitation if the location is different from where the related effort is proposed to take place.

(c) Past Performance Information - The Offeror shall provide a brief description of performance in delivering quality products in each of the following areas: 1) meeting technical requirements, i.e., the quality of technical performance, e.g., performing analysis, design, testing, etc., 2) meeting schedule requirements, i.e., schedule performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., 3) controlling contract cost, i.e., cost performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., and 4) managing the contracted effort, i.e., program management, e.g., cooperation with customer, subcontract management.

(d) Systemic improvement Information - Identify those systemic improvement actions taken to resolve past problems. Describe the techniques, elements, and tools used to correct problems and, if applicable, how these techniques, elements, and tools will be used during this contract.

Earned Value (If applicable): Provide earned value data generated for that contract, with variances, Cost Performance Index, and Schedule Performance Index. Identify if there were any Over Target Baselines or restructures, and how performance data was impacted. For CPARS data, explain significant differences between earned value measure and CPARS rating, e.g., Exceptional CPARS rating under Schedule and SPI of 0.85.

Award Fee (If applicable): Provide a summary of the award fee available and earned for each evaluation period over the past three years of an on-going contract, or last three years of a completed contract (both in dollars earned and percentage of available award fee received).

Small Business Concerns Participation Goals (if applicable): Note whether the contract met or exceeded small business, small disadvantaged business, small business HUB Zone, veteran-owned small business, service disabled veteran owned small business, women-owned small business participation and subcontracting goals.

3.2. Past Performance Data Requirements

Provide all the information identified below separately for each contract. Provide a summary of the Customer’s Points of Contact in a MS Word Table using the format below which is illustrated with an example.

Include an electronic copy of this table in MS Word on a CD.

1. Offeror’s Name (Prime, Principal Sub, or Critical Team Member, JV/SLE, JV/SLE Member)

1. Contract #,

4. Offeror’s Role (e.g., prime or sub)

Customer’s Name

1. CPARS? Recent?

2. Questionnaire # __ Sent?

3. For Subs - Agreement to allow Coordination with Prime?

Point of Contact’s Name;

Phone Number, Fax Number and E-mail address

AB (prime) 1. N009,

4. Prime

RYP 1. CPARS: No

2. Questionnaire #1:

- Sent 5/4/05

3. N/A

Al (PM) 444-444-4444, fax 555-555-5555, Al@RYP

1. CPARS: No

2. Questionnaire #2:

- Sent 5/4/05

3. N/A

Sue (PCO) 333-333-3333 fax 222-222-2222 Sue@RTP

1. CPARS: No

2. Questionnaire #3:

- Sent 5/4/05

3. N/A

Joe (ACO) 111-111-1111 fax 888-888-8888 Joe@ RYP

AB (prime) 1. N008,

4. Sub

L&M 1. CPARS: Yes/No

2. Questionnaire # 1: - Sent 5/4/05

3. N/A

Sue (PCO) 333-333-3333 fax 222-222-2222 Sue@AB

NNB (sub) 1. N007,

4. Prime

RST 1. CPARS: Yes/Yes

2. Questionnaire: - Not Sent

3. Agreement: Yes

Sue (PCO) 333-333-3333 fax 222-222-2222 Sue@NNB

4.0 VOLUME 4: PRICE/COST PROPOSAL

4.1 Volume Content:

(a) This Volume shall contain the information requested below and shall include a copy of Section B with the Contract Line Item (CLIN) Unit Prices, and for evaluation purposes, the Total Prices filled in using the estimated quantities value in the solicitation and the instructions below. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using output type “value only” cells. If links are utilized, supply those referenced files. Spreadsheets shall not be protected.

(b) All price/cost and price/cost supporting information shall be contained in section B and the price/cost proposal. No price or pricing information shall be included in any other proposal volume including cover letters.

Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price/cost proposal.

4.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition with adequate price competition anticipated, any price/cost documentation requested shall not be certified cost or pricing data in accordance with FAR 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors and may conduct negotiations with the Offeror, pursuant to FAR Part 15.403-4, in order to ensure a reasonable and realistic price/cost.

Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2. Offeror shall acknowledge the requirement to provide additional cost or pricing information and certify the data prior to award if/when requested by the Government.

(b) The Offeror shall provide sufficient information to support its price/cost as well as an explanation of all ground rules and assumptions that affect the price/cost estimates. Any apparent imbalances in the pricing, high or low proposed prices/costs as compared to historical data, or any other anomalies should be fully explained. Topics to be addressed include, but are not limited to, investments, programmatic variables (e.g., inflation/escalation, location, make/buy decisions, prime/subcontractor relationships, and business base concerns), etc.

4.3 Price/Cost Information:

(a) Reasonableness and Consistency between the Technical and Price/Cost Volumes. Demonstrate that the unit prices and the total proposed price/cost are reasonable, realistic, and commensurate with the work required by the solicitation and the technical and management approaches identified in the Technical Volume of the proposal.

Show traceability with the CLINS and SOW, proposed effort, proposed manning levels, and the prices/costs. Refer to specific sections in the Technical Volume as needed to illustrate the consistency between the Price/Cost Volume and the Technical Volume. The Offeror shall explain any inconsistency between promised performance and price/cost, as well as any appearance of unbalanced pricing, in the proposal.

(b) The Offeror shall identify the proposed prices/costs for each CLIN as specified in Section B of this solicitation. The Offeror shall sum up the proposed Total Prices by contract year, and provide a total overall price/cost of the proposal using estimated quantities, and submit a complete Section B. For Fixed Priced CLINs, the Schedule B Total Price is equal to the proposed unit price multiplied by the Section B Estimated Quantity for that CLIN as denoted in the extended description of each CLIN. The Offeror shall propose on each CLIN as follows:

(i) For Firm Fixed Price CLINs 0001-0011 and 0014-0024 insert the unit price for each quantity amount;

(ii) For Firm Fixed Price CLIN 0012 insert the total price for hardware variants including materials over all ordering periods. The Offeror shall use the sample task provided as Attachment P4 when estimating the total price of this CLIN. Quantity not to exceed 20 orders for production variants.

4.4 Use of Government Furnished Property:

(a) If the Offeror proposes/requires the use of Government Furnished Equipment (GFE) or Government Furnished Information (GFI), then the Offeror shall provide:

A complete description of the required GFE/GFI including part number and serial number, if applicable.

Where the GFE/GFI is to be located.

The name, organization, complete address and telephone number of a cognizant Government point of contact.

In the case of GFE/GFI accountable to other Government contracts, a copy of the correspondence authorizing use of such GFE/GFI on this contract.

The monetary impact to the Offeror’s proposal if the proposed GFE/GFI is not provided as GFE/GFI.

If none, so state.

4.5 Other Costs

The Offeror shall identify additional costs, that would be incurred, that have not been identified in the solicitation and describe in detail the performance that would cause these costs. Also, describe any assumptions with regard to Government’s actions (e.g., providing resources whether it be equipment or people) that enabled the proposed price/cost to be lower and identify the amount by which it is lower.

In addition to completing Section B, the Offeror shall complete Attachment P3 Proposal Price Evaluation Summary Worksheet.

FOR YOUR INFORMATION:

The following addresses and points of contact are provided:

Contract Specialist: Robert Fisher Phone: (760) 939-8366

DSN: 437-8366

FAX: (760) 939-5694

Email address: robert.v.fisher@navy.mil

U.S. Postal Service Mailing

Address: COMMANDER CODE 254300D (R. Fisher – 760-939-8366)

NAVAIRWARCENWPNDIV

429 E. BOWEN RD. MAIL STOP 4015

CHINA LAKE, CA 93555-6108

Direct Delivery Address (UPS, FedEx, etc):

COMMANDER

CODE 254300D (R. Fisher)

NAVAIRWARCENWPNDIV

BLDG 982, MAIL STOP 4015

Procuring Contracting Officer: Jennifer S. Corcoran Phone: (760) 939-9536

DSN: 437-9536

FAX: (760) 939-8107

Email address: jennifer.corcoran@navy.mil

U.S. Postal Service Mailing Address: COMMANDER CODE 254300D (J. Corcoran – 760-939-9536)

NAVAIRWARCENWPNDIV

429 E. BOWEN RD. MAIL STOP 4015

Direct Delivery Address (UPS, FedEx, etc):

COMMANDER

CODE 254300D (J. Corcoran)

NAVAIRWARCENWPNDIV

BLDG 982, MAIL STOP 4015

All questions shall be submitted in writing and e-mailed to:

Name: Robert Fisher and Amanda Bartel

Email address: robert.v.fisher@navy.mil and amanda.bartel@navy.mil

It is requested that all questions be received within five (5) days of the date this solicitation was posted.

All questions received more than ten (10) days after the posting of this solicitation will not be answered.

CONTRACTOR’S ARE REQUIRED TO HOLD PRICES FIRM

FOR A MINIMUM OF 180 DAYS.

(End of Summary of Changes)