N00019-14-R-0025-0003.docx

N00019-14-R-0025

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L-1 CONTENT OF PROPOSALS

L-1 INSTRUCTIONS, CONDITIONS, CONTENT OF PROPOSALS

PART A - GENERAL INSTRUCTIONS

1. GENERAL INFORMATION

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of all requirements and associated risks; is able, willing, and competent to devote the resources necessary to meet all requirements; and has valid and practical solutions for all requirements and potential risk areas. The burden of proof for all substantiation within the proposal rests with the Offeror. Unsubstantiated statements that the Offeror understands, and can or will comply with the specifications, and paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable. Alternate proposals are not acceptable. A maximum of two (2) multiple stand-alone proposals from the same Offeror are acceptable provided the proposals are compliant with the solicitation requirements.

Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government into the final contract. With the exception of the Price Volume, no price should appear in any other volume.

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 shall not alter or rearrange the solicitation.

The Offeror shall include any data necessary to illustrate the adequacy of the various ground rules, assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information should be included in the most logical place and summarized and referenced in other areas if an overlap exists. Unnecessarily elaborate brochures or other presentation beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

Throughout these instructions, Offeror is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form 33 (SF 33), Solicitation, Offer, and Award. A “Principal Subcontractor” is defined as a subcontractor who provides at least 10% of the proposed total price for the contract. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. A “JV Team Member” is an entity that makes up a Joint Venture. A “Critical Subcontractors” is defined as a subcontractor who performs a critical function in the performance of the resulting contract, whether it is technical or financial, and/or have important roles in any high or medium risk areas identified in the Offeror’s proposal. The term “entity” is used to mean any or all of the following: Prime, principal subcontractor, critical subcontractor, JV, JV team member, or other subcontractor. Offerors are reminded to supply the information required in accordance with Clause 5252.215-9505 should it apply.

2. PROPOSAL FORMAT

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/ printed on, standard 8.5 x 11 inch paper. All pages should be numbered with section, volume, paragraph, and page numbers. When fold-out pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. If the Offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described. 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 one page. Graphs and tables shall be presented in no smaller than a 10 pt font. Graphs should contain a grid that allows values to be read directly from the graph to the same detail that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented. Text utilized in charts, figures, and graphics shall also be no smaller than a 10 pt font and may use a font type selected by the Offeror. Each volume, book, or annex shall be provided separately in a 3-ring binder, unless otherwise indicated. The binders shall be of an appropriate thickness for the number of pages it contains (e.g., a 30-page book shall not be placed in a 2-inch binder).

2.1 Electronic Submission of Proposal

This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting proposals. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and install proposals onto the electronic evaluation system, and will ensure that the proposals received are suitable for reading electronically.

2.1.1 Electronic Proposal Media

The Offeror should submit all volumes of its proposal electronically on CD-ROM disk(s) compatible with the operating system and applications defined in Section 2.1.2 below. The Offeror should put as much proposal material as possible on each CD-ROM disk, keeping the portions of the proposal that contain pricing information on separate CD-ROM disk(s) from the portions of the proposal that do not contain pricing information. For this solicitation, Table T-1 (Small Business Goals) and Volume 4 Price contain price information and should be delivered on separate CD-ROM disk(s) from the remainder of the proposal. The Offeror should submit two sets of CD-ROM disks that contain its proposal. One set of CD-ROM disks should be marked "Master" and the other should be marked "Back-Up." Both sets of CD-ROM disks should be clearly marked with the Offeror's name and address, the point of contact's name and phone number, and proposal volumes contained therein. The Offeror is responsible for ensuring electronic proposals are virus free in accordance with Section 2.1.4. If a discrepancy exists between the original paper copy of the proposal and the CD-ROM disk copy, the original paper copy shall take precedence.

2.1.2 Operating System and Applications

The proposals will be accessed utilizing the Microsoft Office 2010. The Offeror shall submit two identical proposals in separate, electronic versions with one version in Portable Document Format (.pdf) and one version in Microsoft Office 2010 Applications (Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Project). The .pdf document must be fully searchable. The Offeror is responsible for ensuring that the .pdf and the appropriate Microsoft Office 2010 applications versions contain identical information. The Government shall have the discretion to use the information in either version, and shall not be responsible for any differences in content between the two proposal formats submitted by the Offeror. Use of other application software for submission of proposals is prohibited except where specific instructions for non- PDF or Office 2010 applications are provided.

2.1.3 Hyperlinks

Offerors may use hyperlinks within and among proposal volumes that do not include price information. However, there shall be no links from any other volume into Volume 4 Price or any portion of the proposal that contains price information.

2.1.4 Virus Free Electronic Submission

The Offeror is responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify in its proposal cover letter that all electronic proposal information has been checked for viruses, and specify the software, version, and virus definition used to check the data. With each subsequent submission of proposal information (e.g., responses to Evaluation Notices, Final Proposal Revisions, etc.), the Offeror shall ensure and certify that its files are virus free.

2.1.5 Multimedia

The Offeror should not embed sound or video (e.g., MPEG) files within the proposal submission.

2.1.6 Graphics

Large files require greater computer system resources and are discouraged. The Offeror is encouraged to:

· Simplify the color palette used in creating figures;

· Minimize size of graphics files; and

· Avoid scanned images.

3. PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one for one comparison between the information presented and these proposal instructions. Proposal information must be structured such that paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier subparagraphs.

In addition to the electronic copies requested in paragraph 2.1, “Electronic Submission of Proposal,” each volume, book, and annex of the proposal shall be submitted as one paper original and additional paper copies as specified in Table G-2 Proposal Structure. The Offeror shall submit all paper and electronic copies of the proposal to the address provided in section 4.0. Suggested page counts for each volume, if any, are also specified in Table G-2 Proposal Structure. Title and table of contents pages are not included in the suggested page count. Annexes do not have suggested page counts.

Information submitted as an Annex to a particular proposal volume may include manuals, specifications, plans, procedures, and company policies, as well as other information requested in Section L Part B - Specific Instructions and do not count towards the suggested page count. Additionally, the individual subcontracting reports for the past performance volume are not included in the suggested page count.

Table G-1 Proposal Structure

Technical

(35 page for Volume)

Each volume must contain the following information. Use tabs and dividers.

a. Cover and title page;

b. Title of proposal and proposal number as applicable;

c. Offeror’s name, address, and point of contact;

d. Solicitation/Request for Proposal (RFP) number;

e. Proposal volume/book number/annex number; and copy number;

f. Table of Contents providing sufficient detail to enable easy location of important elements; and

g. Glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the suggested page count.

Catalog Card - Each volume must contain an 8 1/2" x 11" Catalog Card containing the information required for the cover and title page. The back of the card must be formatted with three columns entitled "Name", "Date Out", and "Date In". This card must be removable from the back of each binder.

The following Table G-3 lists the attachments provided to the Offeror with Section L, to assist with proposal development.

Table G-2 Section L List of Attachments

Table G-3. Cross Reference Matrix

A Government Cross Reference Matrix (CRM) is provided below to help the Offeror ensure that all requirements are addressed, are easily accessible to the evaluators, and to aid in ensuring accurate format and mapping of the CRM to its proposal. The Offeror is required to provide a CRM for the Technical Volume only. The Offeror’s CRM’s shall cross-reference its proposal volume, page and paragraph to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The CRM provided in the Technical proposal volume is not included in the suggested page count. The Offeror’s Technical CRM may be identical to the one provided below or revised to add columns to indicate the page number on which information may be found or to provide other comments.

Clarification Language for P. Spec Attachment #7

SOW

Volume / Page Location within Offeror’s Proposal

2.0 Vol. 2 Technical

3.1-3.17

3.1 - 3.6, 4.1 – 4.3, 5.1 – 5.3

PMA201-12-001

3.2.4.4, 3.3.1.1, 3.3.2.3.1, and 3.5.3

3.2 - 3.3

3.3.1.3 and Appendix B

2.6 Program and Schedule

Key:

N/A = Not applicable

Note: Table G-3. (Cross Reference Matrix) is provided as a guide and should only be used for information only.

4.0 PROPOSAL PACKAGING AND SUBMISSION

4.1 Proposal Marking and Submission

Clearly mark all packages with the solicitation number. The submission date for all volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the Solicitation/RFP. However, it is requested that one hard copy and one electronic copy on a CR-ROM disk of the following be submitted at least two weeks prior to submission date/time specified on SF 33 (Block 9).

· Volume 3 Past Performance Table PP-1 “Past Performance Contract Data”

· Volume 1 Executive Summary Table ES-1 “Offeror Summary,” and Volume 1 Executive Summary Table ES-2 “Relevant Contract Summary”

· Volume 5 Small Business Subcontracting Plan.

Method of delivery, such as by hand, United States Postal Service, or commercial carrier, shall be coordinated with Brianna Shaw, Contracts Specialist, telephone number: (301) 757-5922 and/or e-mail address: brianna.shaw@navy.mil. Proposals shall be submitted using the address provided below. Unless otherwise provided for by the PCO, Chris Lyons, Initial and Final Proposals shall not be submitted by facsimile or electronically via email.

Naval Air Systems Command Attention: Brianna Shaw Air-2.4.1.3.2, Suite 256, Bldg 2272 47123 Buse Rd Patuxent River, MD 20670-1547 N00019-14-R-0025

All proposals must be UNCLASSIFIED.

4.2 Proposal Packaging

The Offeror shall package the proposal volumes in cartons or equivalent packaging containers (hereinafter “carton”) in the most efficient manner possible and grouping like volumes to the maximum extent possible. Each carton should identify its contents by including a packing slip detailing each volume/book number, title, and copy number. Each carton should be double wrapped. The outside of the carton should be plain and the inside carton shall be stamped or marked ― For Official Use Only and Source Selection Information – See FAR 2.101 and 3.104, marked for the intended recipient as identified below. The master set of proposals and set No. 1 copy shall be marked for NAVAIR PCO, AIR-2.4.3.5. The Master Set shall include the following: all original proposal volumes; all proposal volumes on CD-ROM disk; a completed and original signed Standard Form 33; all signed solicitation amendments Standard Form 30, if applicable; and Representations, Certifications and Other Statements of Offerors or Respondents (Section K of the Solicitation) and other applicable fill-ins. Note: Any documents that contain price data shall be on a separate disk(s) from the other disks.

5.0 CHANGES TO SOLICITATION

All amendments to this solicitation shall be posted at https://www.fbo.gov/. Amendments may be found by searching the database for solicitation number N00019-14-R-0025 and N00019-14-P1-AZ002.

6.0 REQUESTING TECHNICAL DATA NOT AVAILABLE FOR PUBLIC RELEASE

This program includes information that is subject to the Arms Export Control Act. As such, this information will not be posted with the solicitation. To obtain a copy of these documents, please contact Ms. Darla Kelly at darla.kelly@navy.mil with the name of your company, mailing address, phone number, email address, and current CAGE number. Please include a copy of DD Form 2345, Militarily Critical Technical Data Agreement, with your request.

Prior to release of any controlled documents under this solicitation, any U.S. contractor must acknowledge its responsibilities under U.S. export control laws and regulations (including the obligation, under certain circumstances, to obtain an export license prior to the release of technical data within or outside the United States) and agree that it will not disseminate any export-controlled technical data subject to this requirement in a manner that would violate applicable export control laws and regulations. Upon review of your written request, verification of your status and acknowledgement of the contractor’s responsibility under the U.S. Export laws and regulations, the requested attachments will be provided.

Documents listed in Section J that are not posted on the FedBizOps webpage may be requested by contacting Ms. Darla Kelly. For requests to be accommodated, additional information from your company may be required.

7.0 FACE-TO-FACE DISCUSSIONS

The Government intends to conduct the Face-to-Face Discussions, as defined in FAR 15.306(d), with all Offerors who submit a timely proposal. The fact that an Offeror may be initially included in the competitive range does not preclude the Government from excluding the Offeror’s proposal from further consideration if the proposal is found to no longer have a reasonable chance of receiving award.

7.1 Schedule and Content

Face-to-Face Discussions will be held at a Government-provided facility located at or near the Naval Air Systems Command, Naval Air Station, Patuxent River, Maryland. Prior to the face-to-face discussions, the Government will provide the scheduled date and time and provide a list of any prepared questions and/or evaluation notices regarding the proposal.

7.2 Participants

All participants shall be employees of the Offeror or its proposed subcontractors. Due to space constraints, Offerors, including subcontractor participants, are limited to no more than 10 attendees in the room at one time. At least 2 business days prior to the scheduled start time of the Offeror’s Face-to-Face Discussions, the Offeror shall provide the Government a listing of names, firms, and position titles of those individuals who will be attending the Face-to-Face Discussions to the Contract Specialist, Ms. Darla Kelly with a copy to the PCO, Chris Lyons.

7.3 Facilities

The Government will provide a computer connected to an overhead projector/digital projector. Additionally, a phone will be available in the discussion room to interface with on-site or off-site subject matter experts. Any digital information to be presented shall be provided as a CD-ROM.

7.4 Face-to-Face Discussion Procedures

At the beginning of the Face-to-Face Discussions, the Offeror shall present their responses to any questions and/or evaluation notices previously provided by the Government and provide any written updates to their proposals.

The Government may engage in further discussions, as defined in FAR 15.306(d), on all aspects of the proposal including any information presented at the Face-to-Face Discussion event. The Government may ask questions (in addition to the provided questions or as follow-up to responses) and the Offeror should be prepared to respond to the Government's questions during these discussions. For any information presented orally that modifies the Offerors proposal, the Offeror must submit written updates to their proposal for the Government to consider the information as part of its evaluation. Discussions may continue after the completion of the Face-to-Face Discussion Phase.

7.5 Proposal for Evaluation Purposes

The Offeror’s proposal, for purposes of evaluation, will consist of the proposal as submitted plus written answers to questions presented during the Face-to-Face Discussion phase, written responses to Evaluation Notices, and any written changes to the proposal. Oral answers to questions or Evaluation Notices are not considered part of the Offeror’s proposal.

8.0 POINTS OF CONTACT

If an Offeror believes that the requirements in these instructions contain an error, omission, or are unclear, the Offeror shall immediately notify the PCO AIR-2.4.3.5, Chris Lyons at Chris Lyons@navy.mil or by phone (301) 342-3516 or Contract Specialist, Darla Kelly at darla.kelly@navy.mil or by phone (732) 323-7437.

PART B - SPECIFIC INSTRUCTIONS

1. VOLUME I – EXECUTIVE SUMMARY

NOTE: THIS VOLUME SHALL NOT CONTAIN ANY REFERENCE TO PRICE ASPECTS OF THE OFFER.

The following is a list of Section L Attachments that the Offeror shall utilize to provide information for this volume:

Attachment L-1 Executive Summary Tables

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal, excluding price. Each section within the Executive Summary shall contain the salient points contained in each of the proposal volumes, with the exception of the Price Volume and the Small Business Subcontracting Goals table. In addition, this volume should be used by the Offeror to identify and highlight significant features of its proposal. The Executive Summary volume should be divided into the areas outlined below:

a. Offeror Summary Table

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment L-1 (Executive Summary Tables), according to the instructions within the attachment and submit it within this section and as a separate electronic file.

(2) The Offeror shall provide a written explanation if multiple CAGE codes for the same physical location are provided in Table ES-1 (Offeror Summary). The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason.

Note: Place of Performance for this solicitation pertains to the physical location of the prime, all subcontractors, and JV team members who will perform the work.

ES-1 Offeror Summary Table

Offeror:

Price

b. Relevant Contract Summary Table The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance for the Prime, principal subcontractors, critical subcontractors, and JV team members. Complete the table according to the instructions within the attachment and submit it within this section and as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 Table PP-1 (Past Performance Contract Data).

ES-2 Relevant Contract Summary Table

Offeror:

Referenced in:

Reference

P2

P3

T2

T3

T4

S2

S3

S5

c. Technical The Offeror shall provide a summary of the technical effort and describe how its approach addresses the requirements of the solicitation.

d. Past Performance The Offeror shall provide a summary of the Prime’s, principal subcontractors’, critical subcontractors’, and JV team members’ past performance and systemic improvements that pertains to the tasks required by this solicitation.

e. Viewgraphs/Photographs The Offeror may provide up to five electronic photographs for the proposed concept to assist the Government in understanding the Offeror’s design. The electronic photographs must be in a standard readable format, e.g., Joint Photographic Expert Group (JPEG).

5. VOLUME 2 – TECHNICAL PROPOSAL

NOTE: THIS VOLUME SHALL NOT CONTAIN ANY REFERENCE TO PRICE ASPECTS OF THE OFFER.

The following is a list of Sections J and L Attachments that the Offeror shall utilize to provide information for this volume:

In this volume, provide the information described below:

Throughout the Technical Volume, the Offeror should identify any proposed capability, approach, or feature that exceeds a requirement or provides merit associated with a performance or operational benefit to the Government. The Offeror should also identify any proposed capability, approach, or feature that reduces risk inherent in the program. The Offeror should explain the benefits to the Government in technical terms and the impact to performance, operations, and/or risk. Offerors are advised that any offer to exceed a requirement or to provide a feature with performance and/or operational benefits may be included in the resulting applicable Contract within the proposed cost.

2.1 DESIGN OVERVIEW

The Offeror shall provide an overview of the technical approach to meet the solicitation requirements. The overview shall provide sufficient detail to allow the Government to understand the Offeror’s overall design concept. A description of how each requirement will be met is not required. The Offeror shall identify the most significant risk areas and shall discuss the risk mitigation activities proposed for these risk areas.

2.2 SERIAL DATA INTERFACE

The Offeror shall describe its implementation of the Serial Data Interface (SDI) requirements outlined in the FMU-139D/B Performance Specification and FMU-139D/B Serial Data Interface Control Document into its fuze design. This description shall describe, in detail, the efforts to integrate the SDI capability into the fuze design, the method to verify and test that all requirements have been met, and any areas of risk. The Offeror shall indicate what testing will be done by the Offeror or by independent test agencies and any testing the Offeror proposes be done by the Government or with the use of Government test facilities. The Offeror shall indicate any Government Furnished Equipment that will be required to complete these efforts.

2.3 FUZE FUNCTION CONTROL SET

The Offeror shall describe its implementation of the Fuze Function Control Set (FFCS) requirements outlined in the FMU-139D/B Performance Specification into its fuze design. This description shall include the efforts to integrate the FFCS capability into the fuze design, the verification and testing that will be performed to demonstrate that all requirements have been met, and any areas of risk that exist for the integration of this capability. The Offeror shall indicate what testing will be done by the Offeror or by independent test agencies and any testing the Offeror proposes be done by the Government or with the use of Government test facilities. The Offeror shall indicate any Government Furnished Equipment that will be required to complete these efforts.

2.4 WIND TURBINE ALTERNATOR

The Offeror shall describe, in detail, all efforts required to produce the wind turbine alternator and the verification and testing that will be performed to demonstrate that all related requirements have been met in accordance with the FMU-139D/B Performance Specification. The Offeror shall describe its approach for meeting the low airspeed requirement as described in the FMU-139D/B Performance Specification. The Offeror shall identify any areas of risk identified with integrating the wind turbine alternator with the fuze or any planned weapon system identified in the FMU-139D/B Performance Specification. The Offeror shall indicate what testing will be done by the Offeror or by independent test agencies and any testing the Offeror proposes be done by the Government or with the use of Government test facilities. The Offeror shall indicate any Government Furnished Equipment that will be required to complete these efforts.

2.5 TECHNICAL DATA PACKAGE OPTION CLIN 0410

The Government may procure the Technical Data Package (TDP) under the FMU-139D/B Program pursuant to CDRL A00J. The Offeror shall separately identify those items submitted as part of the DFARS 252.227-7017 (Assertions List) that are related to the TDP that are being provided to the Government with license rights greater than those the Government would otherwise possess in accordance with DFARS data rights clauses 252.227-7013 (Rights in Technical Data – Noncommercial Items), 252.227-7014 (Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation), and 252.227-7015 (Rights in Technical Data for Commercial Items).

a. For all commercial and noncommercial technical data and computer software used, developed, and delivered under the FMU-139D/B contract, the Government desires, at a minimum, a Government Purpose Rights license in such technical data and computer software, as defined in DFARS 252.227-7013 and DFARS 252.227-7014. Such licenses will permit the Government to procure and/or fully support, maintain, and modify the FMU-139D/B hardware and software in a competitive environment throughout the life cycle of the FMU-139D/B.

b. This solicitation contains DFARS 252.227-7017, which requires Offerors to identify the technical data and computer software that the Offeror, its subcontractors or suppliers, or potential subcontractors or suppliers, asserts should be furnished to the Government with restrictions. Such restrictions may impede the Government’s ability to meet its above-identified intentions for technical data and computer software. However, the Offerors may agree to provide the Government with a Government Purpose Rights license (as defined in DFARS 252.227-7013 and 252.227-7014) to use, modify, reproduce, release, perform, display and/or disclose such commercial and/or noncommercial technical data and computer software in order to satisfy those needs identified in subparagraph (a.) above.

c. With respect to the data rights and licensing provided in the Offeror’s proposal, the Offeror shall segregate and identify CLIN 0410 costs associated with any proposed licenses that provide the Government with rights above and beyond the rights the Government would be entitled to by virtue of the DFARS data rights clauses 252.227-7013 (Rights in Technical Data – Noncommercial Items), 252.227-7014 (Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation), and 252.227-7015 (Rights in Technical Data for Commercial Items). In accordance with DFARS 227.7103-1, failure to provide rights in technical data and software that enable the Government to procure and fully support, maintain and modify the FMU-139D/B hardware and software shall NOT be considered a failure to meet a Government requirement that renders the proposal ineligible for award.

d. Where the Offeror asserts that technical data and computer software will be furnished to the Government with Commercial, Restricted, or Limited rights, the Offeror (a) shall provide the identifications and assertions set forth in 252.227-7017 and (b) may provide a license agreement granting the Government additional rights in accordance with DFARS 252.227-7013(b)(3)(iii) and 252.227-7014(b)(3)(ii) and the price for such license under CLIN 0410.

e. The Offeror shall explain how its data rights assertions in 252.227-7017 will impact the FMU-139D/B life cycle supportability and sustainment strategy and provide a mitigation plan for any Commercial, Restricted, or Limited rights that will negatively impact the FMU-139D/B sustainment strategy.

2.6 SCHEDULE

2.6.1 COMPLETION OF CLIN 0001 (QUALIFICATION AND FIRST ARTICLE TESTING)

The Offeror shall provide a schedule, as Annex 1, that demonstrates its ability to complete all the work associated with CLIN 0001 within 32 months after contract award. The Offeror shall describe its plan, including contractor-defined program phases, planned program reviews, and manpower strategy to execute the program from contract award to completion of first article testing, qualification testing, approval of Safety Boards, and closure of SETR events.

2.6.2 SCHEDULE OF PRODUCTION UNITS

The Offeror shall demonstrate its ability to meet the following sample schedule of production units, which is for evaluation purposes only. The Offeror shall identify anticipated monthly production capability rates to meet the required deliveries. The Offeror shall identify existing capabilities and its plan to reach the required production schedule in the sample schedule, staffing levels, facilities, equipment, testing capability, and its proposed plan for improvements in these areas to meet the anticipated required monthly production schedule.

SAMPLE SCHEDULE OF PRODUCTION UNITS (SAMPLE TASK):

First year production The Government awards a delivery order on January 1, 2017 for 25,000 FMU-139D/B Fuze System. Deliveries shall commence within 12 months after delivery order award and complete within 12 months of first delivery.

Second year production The Government awards a delivery order on January 1, 2018 for 30,000 FMU-139D/B Fuze System. Deliveries shall commence within 12 months after delivery order award and complete within 12 months first delivery under the delivery order.

2.7 SMALL BUSINESS MANAGEMENT

All Offerors (Large and Small Businesses) shall address their strategies for utilizing SB Concerns in the performance of this contract, whether as a joint venture, teaming arrangement or subcontractor. SB Offerors may meet this requirement using work they perform themselves. For purposes of this solicitation, the term SB Concern shall also include the subcategories of Veteran-Owned Small Business (VOSB), Service-Disabled Veteran-Owned Small Business (SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and Women-Owned Small Business (WOSB). Each subcategory of SB shall be addressed. This strategy is separate from, but shall be consistent with, the SB Subcontracting Plan, if such a Plan is required. In describing its SB Utilization Strategy for this solicitation, the Offeror shall, as applicable:

a. Describe its approach to identifying SB Concerns;

b. Describe the extent of participation of SB Concerns on this contract, including a detailed description of the supplies and services for each SB Concern subcategory, and the complexity and variety of the work SB Concerns are to perform. For each SB Concern specifically identified in the proposal, provide the SB Concern's CAGE Code, or, if the SB Concern is not registered in the System for Award Management (SAM), at a minimum provide evidence of self-certification in accordance FAR 19.703(b) as an SB Concern. Where possible, provide documentation regarding enforceable commitments to utilize each SB Concern.

c. Identify processes to correct inabilities to meet proposed goals with corresponding improvements that will be used on this contract;

d. Provide goals, expressed as dollars and percentages of total contract value and percentages of total subcontract value for SB Concerns and each subcategory of SB, using the format depicted below and provided electronically in Attachment L-2 (Table T-1 Small Business Goals). The Offeror shall provide Table T-1 as part of Volume 5 because it contains price information. This table does not replace the Subcontracting Plan requirements in FAR 19.7. Use tab 1 for the prime and tab 2 etc. for each Tier One subcontractor as goals for each subcontractor must be listed separately;

Table T-1 Small Business Goals

Offeror Name

Large Business

Small Business

Total

100%

VOSB

SDVOSB

HUBZone

SDB

WOSB

e. Describe its specific efforts and new, contract-specific initiatives to ensure the resulting contract meets or exceeds proposed goals. These efforts shall include, but are not limited to: sponsoring program specific outreach events and industry conferences, establishing Mentor-Protégé relationships and market research using websites such as the NAVAIR Office of Small Business Programs website (http://www.navair.navy.mil/osbp ) to locate small business concerns; and

f. Demonstrate (Large Businesses only) that its SB Utilization Strategy is consistent with its SB Subcontracting Plan. If the Offeror is a participant in the DoD Comprehensive Subcontracting Test Program specified in DFARS 219.7, or if the Offeror submits a Commercial Subcontracting Plan for this proposal, then the Offeror shall describe how SB participation on this contract will contribute to its overall Comprehensive or Commercial Subcontracting Plan goals.

3.0 VOLUME 3 - PAST PERFORMANCE

NOTE: THIS VOLUME SHALL NOT CONTAIN ANY REFERENCE TO PRICE ASPECTS OF THE OFFER.

The following is a list of Section L Attachments that the Offeror shall utilize to provide information for this volume:

For this volume, the Offeror shall identify relevant contracts, or those portions of a relevant contract, whose performance is within five years of the proposal due date and contains efforts similar to those efforts (e.g., end product or service, type effort, contract tasks, contract type, contract dollar value, etc.), required by this solicitation for the Prime, principal subcontractors, critical subcontractors, and JV team members, identified in Table ES-1 (Offeror Summary). Offerors shall also identify relevant contracts within five years of proposal due date that had any show-cause notices, cure notices, or terminations for default.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. The Past Performance Information Reporting System (PPIRS) will be the primary paperless method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Attachment L-3 Past Performance Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM), or commercial contractor equivalents. Please forward all questionnaires within two weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference the solicitation number when distributing the past performance questionnaires to customers. The Offeror shall include instructions for the customers to send completed questionnaires within two weeks of receipt via e-mail to Darla Kelly darla.kelly@navy.mil. The Offeror shall ensure that all points of contact are current and include an email address and phone number for each point of contact. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

Offerors are reminded that the Government reserves the right to use information obtained from sources other than those identified by the Offeror to evaluate past performance. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team.

0. Authorization Letter(s) Within this section, the Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each participating principal subcontractor, critical subcontractor, or JV team member authorizing the release of adverse past performance information to the Prime. This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any subcontractors or JV team members that do not provide an authorization letter with such written consent, the Offeror shall state that adverse past performance issues shall be coordinated directly with the subcontractor or JV team member. The Offeror shall provide a point of contact with a name, address, phone number, and email address for each subcontractor or JV team member with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if Offerors do not submit the Release of Adverse Past Performance Authorization Letters with written consent, then the Government will address any past performance issues directly with the subcontractor or JV team member and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

For each contract identified for past performance in Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), the Offeror shall complete Attachment L-4 Table PP-1 (Past Performance Contract Data), following the instructions provided within the attachment and submit it within this section and as a separate electronic file. Please note that this form is a summary of the Prime’s, principal subcontractors’, critical subcontractors’, and JV team members’ relevant contract data. All detailed information and comparative analysis of the past performance references to this solicitation’s requirements shall be provided in Volume 3, Section 3.3 (Evaluation), of the Offeror’s proposal. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing this Volume and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (e.g., the contracts identified as P1, S1, T1, etc.).

In general, recent performance will be considered more relevant than older performance. Commercial contracts may be included. If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole and for each team member of the JV.

Table PP-1 Past Performance Contract Data

Phone:

Email:

Phone:

Email:

Phone:

Email:

Title:

Phone:

Email:

3.2.1 Evaluation

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

For each contract or delivery order identified in Attachment L-4 Table PP-1 (Past Performance Contract Data), the Offeror shall provide contract data regarding relevancy, past performance information, and demonstrated systemic improvement, as described below, organized by contract. Demonstrate the relevancy of the Prime’s, principal subcontractors’, critical subcontractors’ and JV team members’ past performance with respect to this solicitation’s requirements. For any contracts referenced where the Prime, principal subcontractors, critical subcontractors, and/or JV team members are aware of problems, describe the issues in section 3.3.b (Past Performance Information). For each past performance problem identified, describe the status of the systemic improvement efforts in section 3.3.c (Demonstrated Systemic Improvement).

3.2.1.1 Relevancy: Offerors are required to explain what aspects of the contracts are deemed relevant to this solicitation’s requirements. To demonstrate relevancy, Offerors should provide a comparative analysis to this solicitation’s requirements. In Annex 2, Offerors should provide two electronic copies of the Statement of Work/Performance Work Statements (SOW/PWS) from each of the referenced contracts identified in Table ES-2. Within the comparative analysis, Offerors should identify the relevant portions (sections, paragraphs and page numbers) of the referenced contract’s SOW/PWS to clearly identify how past tasks performed are similar to this solicitation’s requirements. Annex 2 should only be provided in electronic format and should not be provided in hard copy. In addition, the referenced sections only need to be referenced/identified, and do not need to be broken out separately from the complete SOW/PWS.

The following definitions are provided as guidance for relevancy:

Relevant (R) – Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

Not Relevant (NR) - Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

Consider the following ground rules when performing the comparative analysis:

(1) The Offeror is advised that the Government will assess each contract and assign a relevancy rating.

Relevant contracts are those whose present/past performance effort involved similar scope, magnitude of effort, and complexities this solicitation requires.

(2) Offerors are advised that contracts assessed as Not Relevant by the Government will not be considered in the Past Performance assessment. Contracts or the portion of those contracts submitted by the Offeror that meet any of the conditions below will be assessed as Not Relevant:

i. Contracts from an entity that does not have a defined role and responsibility identified in Table ES-1 (Offeror Summary);

ii. Contracts from a different physical location (e.g., with different CAGE code) than the entity proposed in Table ES-1 (Offeror Summary);

iii. Contracts that involve little to none of the scope, magnitude of effort, and/or complexities required by this solicitation; or

iv. Contracts, or those portions of the contract, whose performance is more than 5 years from the proposal due date. (If only a portion of a contract performance is more than 5 years, then only that portion is not relevant for reasons of recency.)

(3) Past performance of any entity with multiple CAGE codes will be considered for the same physical location if each entity have distinct roles and responsibilities identified in Table ES-1 (Offeror Summary), or the current and previous CAGE codes were created as a result of a corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. However, all current CAGE Codes must appear in Table ES-1, which indicates a commitment of work for those entities. To facilitate the relevancy determination, the Offeror shall provide an explanation of why multiple CAGE codes are proposed; identify all applicable CAGE codes along with their defined roles and responsibilities; and provide a description of all such changes in the organization of the company within Volume 1.0, Executive Summary [if past performance for a previous CAGE code is submitted]. In addition, the Offeror shall provide a narrative within this section explaining how the changes impact the relevance of any past performance contracts provided.

(4) The comparative analysis utilized to determine relevancy should show how similar the past performance contract reference is to this solicitation with regard to scope of effort (consider SOO/SOW/PWS tasks), magnitude of effort (consider dollar amount), and complexity (consider attributes of the work being performed such as type of effort, end product, frequency such as turn-around-time or delivery rate, number of sites, skills, processes, contract type, etc.).

3.2.1.2 Past Performance Information: Provide a brief description of performance in delivering quality products in each of the areas identified below. Include in these descriptions any information that demonstrates the level of performance obtained. Where available, provide quantifiable measures/trends to demonstrate past and current performance.