N00421-18-R-0008_Amendment_2.docx

N0042118R0008

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

Amendment 2 to Solicitation N00421-18-R-0008 modifies the following:

1. L-1, PART B, Section 9.1 has been updated to include additional clarifying language in the first paragraph with respect to Attachment L-3.

Additionally, Amendment 2 revises the following Section L Attachments:

· Attachments L-1 and L-2 updates Column C to require Contract Number and Order Number (if applicable) for each project.

· Attachment L-3 adds clarifying language to the note at the top of the form

L - 1 CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(JUN 2011) (05 September 2017)

PART A

1.0 GENERAL INSTRUCTIONS

This solicitation is being issued on a competitive, 100% Small Business set aside basis and utilizes the North American Industry Classification Code System (NAICS) code 541330 which has a small business size standard of $38.5M.

The Government expects to award Indefinite Delivery, Indefinite Quantity (IDIQ) Multiple Award Contracts (MACs) as a result of this solicitation to support the Program Executive Officer for Unmanned Aviation and Strike Weapons (PEO(U&W)). The Government will award an Unmanned Systems IDIQ/MAC and a separate and distinct Weapon Systems IDIQ/MAC, hereafter referred to as (U) and (W). Offeror’s may propose under the (U) MAC, the (W) MAC, or under both the (U) and (W) MACs. Separate proposals and supporting documents for each MAC are required.

Task Orders (T.O.s) will be competed under the (U) IDIQ/MAC and the (W) IDIQ/MAC. Each T.O. may use different evaluation criteria from what is used for the evaluation and award of the (U) and (W) MACs. Offeror’s must be a (U) MAC holder in order to compete for a T.O. under the (U) MAC. Offeror’s must be a (W) MAC holder in order to compete for a T.O. under the (W) MAC.

The following instructions are for the preparation and submission of proposals for the (U) IDIQ/MAC and the (W) IDIQ/MAC. The purpose of this section is to establish requirements for the format and content of proposals so that proposals contain all essential information and can be evaluated equitably.

Offerors are instructed to read the entire solicitation document, including all attachments in Section L prior to submitting questions and/or preparing your offer. Omission of any information from the proposal submission requirements may result in rejection of the offer. This solicitation instructs Offerors to provide support documentation for all scored evaluation criteria.

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award, with a corresponding CAGE Code and DUNS Number in SAM.GOV that matches the Offeror name on the SF 33, Block 15A. A “principal subcontractor” is defined as a subcontractor who provides at least 20% of the proposed total price/cost (excluding the Offeror’s profit/fee), for the contract or provides one or more Key Personnel. 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. “JV Team member” is defined as one of the entities that make up a JV formed for the purpose of responding to this solicitation.

The Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation except as identified in FAR Clause 52.204 Alternate Line Item Proposal (JAN 2017).

The Offeror is advised that the Government may incorporate any portions of the Offeror’s proposal deemed beneficial to the Government, into the resulting contract, with or without discussions.

Price information, (e.g., dollar values and/or hourly rates) shall appear only in the Cost Volume. Alternate proposals are not acceptable except in accordance with FAR Clause 52.204.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization shall be emphasized during proposal preparation. Statements that the prospective Offeror understands, can comply with, or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may result in assessing weaknesses and/or deficiencies.

The Offeror must include any documentation that illustrates the adequacy of the evaluation criteria to enable Government personnel to conduct the evaluation described within Section M. The burden of proof for all substantiation with the proposal rests with the Offeror. Failure to address a specific factor clearly may be considered a deficiency. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

All proposal information is subject to verification by the Government. Falsification of any proposal submission, documents, or statements may subject the Offeror to civil or criminal prosecution under Section 1001 of Title 18 of the United States Code.

In accordance with FAR Part 9, Offerors that are not deemed responsible will not be considered for award. A satisfactory record of integrity and business ethics is required. In making the determination of responsibility, information in the Federal Awardee Performance and Integrity Information System (FAPIIS) and the System for Award Management (SAM) will be utilized.

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the Contract Specialist at teresa.mellies@navy.mil. The Offeror must include the company name and solicitation number in the subject line of the email. The question(s) must include the page number, section number, and paragraph number that pertain to the Offeror’s question(s). The Government will not accept questions in person or by phone. Questions can be e-mailed any time after the solicitation is posted at http://www.fbo.gov; however, it is required that all questions be received within 10 calendar days of the date this solicitation is issued. The Government will post all Questions and Answers to FedBizOpps at http://www.fbo.gov.

The Government intends to compete Task Orders for PMA 262/266 and PMA 263 among the (U) MAC awardees as part of this source selection. To be considered for an award of the PMA 262/266 T.O. and/or the PMA 263 T.O., Offeror’s must provide complete and separate proposals for each T.O. as part of the response to this solicitation. Proposal instructions and evaluation criteria for the PMA 262/266 T.O. are provided in Section L as Attachments L-8, L-9, L-10, L-11, L-12, and L-13. Proposal instructions and evaluation criteria for the PMA 263 T.O. are provided in Section L as Attachments L-14, L-15, L-16, L-17, L-18, and L-19.

2.0 PROPOSAL FORMAT

Written proposals (with the exception of Attachments L-2 and L-3) 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. All pages should be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. 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, including such data as tables or charts, should be consistent with the purpose of the data presented.

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 ensure that the proposals received are suitable for reading electronically. If a discrepancy exists between the original paper copy of the proposal and the original electronic copy on the CD-ROM disk, the original paper copy shall take precedence.

2.1.1 Electronic Proposal Media

The Offeror will provide one complete copy of the written proposal to the PCO in an electronic format that is compatible with Microsoft (MS) Office 2010 and for information not supported by MS Office products, with the latest Adobe Acrobat reader on a CD-ROM. The Offeror will ensure that the Price/Cost Volume is provided on a separate CD-ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. Offerors must include their company name or company name abbreviation and volume number in the electronic filename. For example ABC Incorporated filename for Volume 1, SF33 is ABC.VOL1.SF33.pdf. Offerors may make minor adjustments to the file name methodology as long as the resulting file names and organization are clearly understood.

3.0 PROPOSAL CONTENT AND VOLUMES

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 Volume/section/paragraph number matches the Proposal Instructions Volume/section/paragraph number to which it is responding. The Offeror must provide reasons it will not provide information for a particular Volume/section/paragraph. The Proposal Format Table provided in Section 3.1 is provided to assist Offerors in organizing their proposal submission documents to ensure the Government can easily identify which documents apply to which criteria for evaluation purposes. Offerors must adhere to the Volume Numbers, Section Numbers, Format and/or Templates, and Page Limitations (if any) provided in the Proposal Format Table.

Each volume of the proposal shall be submitted as one (1) original paper proposal and (2) additional paper copies. All volumes of the proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation. Page limitations for each volume, if any, are also specified in the table below; title and table of contents pages do not count towards the page limit. Any pages submitted exceeding the page limit shall be disregarded and NOT evaluated.

3.1 Proposal Format Table

(Company, Volume, Project Identifier) Repeat as necessary:

Organizational Conflict of Interest (OCI) disclosure and OCI Mitigation Plan Submit Section K

Pages should be 8.5x11 inches; 12 point normal font type and size Limited to Section K.

No page limitations ABC.VOL1.RC.pdf

ABC.VOL1.OCI.pdf

Attachment L-1 and/or L-2 Limited to the template.

ABC.VOL1.AttL2.xls ABC.VOL1.AttL3.xls

Attachment L-3

Each project with all supporting documents should be submitted in a single .pdf

Limited to the template.

No page limitations for supporting documents.

ABC.VOL2.Project1.pdf ABC.VOL2.Project2.pdf ABC.VOL2.Project3.pdf ABC.VOL2.Project4.pdf ABC.VOL2.Project5.pdf

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: N00421-18-R-0008

· Proposal volume/book number

· Copy number

· Use tabs and dividers

4.0 PROPOSAL 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 the SF33 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 by facsimile or electronically via email.

Naval Air Systems Command Code: AIR-2.4.2.2.4 (Teresa R. Mellies) Address: 47123 Buse Road, Building 2272 Patuxent River, MD 20670 Solicitation Number: N00421-18-R-0008

Hand carried proposals may be delivered to the address above, attention Teresa R. Mellies or John Cappello.

The outside shipping container shall be marked with: Solicitation Number N00421-18-R-0008.

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 the Cost/Price Volume.

Each box should include a packing slip detailing the contents to include the volume number, title, and copy number. Also, each box 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 CHANGES

For notice of any changes and additional information provided by the Government for the solicitation, please go to www.FedBizOpps.gov.

PART B SPECIFIC INSTRUCTIONS

The following is a list of Section L Attachments that the Offeror shall use to provide information for Volume 1: General Requirements, Volume 2: Technical and Volume 3: Cost/Price.

Section L List of Attachments

Section L Attachment Number

PMA262/266 and PMA263 Fair Opportunity Proposal Request (FOPR)

(U) MAC Task Orders ONLY

8.0 VOLUME 1: GENERAL REQUIREMENTS

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

This Volume shall contain the Contract Compliance information specified below as follows:

8.1 Standard Form (SF) 33

8.1.1 Using the SF 33 form, Solicitation, Offer and Award, posted as page 1 of the solicitation in http://www.fbo.gov, the Offeror shall fill out blocks 12 through 18 accordingly in addition to completion of any solicitation clause or provision that requires a fill-in or response.

8.1.2. The Government requires a minimum acceptance period of not less than 240 calendar days. The Offeror shall complete Block 12 of each SF 33 submitted with full cognizance of the minimum acceptance period of 240 calendar days. "Acceptance Period” means the number of calendar days available to the Government for awarding a Contract from the date specified in this solicitation for receipt of offers. Your offer may only specify a longer acceptance period than the Government's minimum requirement.

8.1.3. If any amendments to the solicitation are issued, the Offeror must acknowledge each amendment number and date in Block 14 of the SF 33 or complete Blocks 8 and 15 of the SF 30 for each amendment.

8.1.4. The Offeror’s Legal Name and Address in Block 15A on the SF33 must match the information for the Offeror in SAM.GOV at http://www.sam.gov, including the corresponding Commercial and Government Agency (CAGE) Code Number and Data Universal Numbering Systems (DUNS) Number.

(Note: the address listed in Block 15A will be the official mailing address used by the Government for letter correspondence, if necessary).

8.2 Representations and Certifications

The Offeror is to complete and submit Section K of the solicitation. The Offeror shall include an Organizational Conflict of Interest (OCI) disclosure and OCI Mitigation Plan, if applicable, based on Offeror’s completion of NAVAIR Provision 5252.209-9511.

9.0 VOLUME 2: TECHNICAL

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

9.1 Document Verification and Self-Scoring Worksheet

The Offeror shall utilize Attachment L-3 (Relevant Experience Project Template) and Attachment L-1 and/or L-2 (Document Verification and Self-Scoring Worksheets) for Section L, paragraphs and subparagraphs 9.1 through 9.2 of this volume. The Offeror shall utilize and submit Attachment L-3 for each separate project identified in Attachment L-1 and/or L-2. The Offeror shall utilize and submit Part 1 & Part II of Attachment L-3 for each separate project identified in Attachment L-1 and/or L-2. The Offeror shall only utilize Part III of Attachment L-3 if any individual claimed scoring elements are being verified by a PCO, COR or PDPM. In addition, if using the optional verification method, the Offerors shall annotate column G of the Attachment L-1 and/or Attachment L-2 with “See Validated Attachment L-3”. For any individual claimed scoring elements not verified by a PCO, COR or PDPM, the supporting documentation shall be annotated in column G of the applicable Attachment L-1 and/or Attachment L-2.

The Offeror shall submit the “Document Verification and Self Scoring Worksheet” utilizing Attachment L-1 if the Offeror is proposing under the Unmanned Systems IDIQ/MAC. The Offeror shall submit the “Document Verification and Self Scoring Worksheet” utilizing Attachment L-2 if the Offeror is proposing under the Weapon Systems IDIQ/MAC. No other format will be considered.

The Offeror shall submit Attachment L-1 and L-2 as part of complete and separate proposals if proposing under both the Unmanned and Weapon Systems IDIQ/MAC.

The Offeror shall provide Relevant Experience Projects for similar programs/contracts in accordance with Section 9.1.1. The experience provided shall only relate to experience gained through contracted work at the organization level. The individual experience of the Offeror personnel will not be considered in the evaluation of the Document Verification and Self-Scoring Worksheet.

The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. Offerors may provide whatever official, verifiable documentation is necessary to validate any scored evaluation element being claimed in sections of Section L that do not require the Offeror to provide a particular form of documentation for validation purposes.

1. Do not alter rows or columns of the Document Verification and Self Scoring Worksheet.

2. The Offeror shall enter their name in Row 4.

3. The Offeror must fill in Column D by entering a “Yes” or “No” for each element. Just type the word, not the quotation marks. Do not leave any Rows under Column D blank. The point value for each element will automatically be calculated in Column F based on the “Yes” or “No” response. The point value for each element is calculated as a zero (0) or as the full point value assigned to a specific individual scoring element. If Column D is left blank, the Government will assume a response of “No” for the element and a point value of zero (0) will be given.

4. If “Yes” is entered in Column D, the Offeror shall enter the file name(s) in Column G for each associated supporting document submitted. Reference the file naming structure provided in Section 3.1.

5. The Project Identifier (Project 1 through Project 5) in the Document Verification and Self-Scoring Worksheet must mirror the same Project Identifier selected in the Attachment L-3 Relevant Experience Project Template (see Section L, paragraph 9.1.1 for instructions).

6. The Offeror must fill in Column C with the Project Identifier(s) that satisfies the claimed credit under Section 9.1 and in the Document Verification and Self-Scoring Worksheet in addition to completing Column D and Column G.

9.1.1 Relevant Experience Projects

A Relevant Experience “project” is defined as (1) a contract; (2) a task order awarded under an Indefinite Delivery Indefinite Quantity (IDIQ) Multiple Award contract; (3) a task order awarded under a Single-Award Indefinite Delivery task order contract (Definite Quantity, Requirements, or Indefinite Quantity) contract (FAR 16.5); (4) a task order placed under a Federal Supply Schedule contract (FAR 8.405-2); or (5) a task order placed under a Blanket Purchase Agreement (BPA)(FAR 8.405-3). Relevant Experience Projects do not apply to Section 9.1.19.

The submitted Relevant Experience Projects must meet the following minimum conditions:

a. Each project must have included the performance of program management support services. Program management support services include business management, acquisition management, management of Government furnished items, configuration/data management, risk management, security or operations activities as well as engineering management, logistics management, test and evaluation management functions that relate directly to PM support.

b. Each project must be ongoing or have been completed within 7 years from the date proposals for this solicitation are due. Each project must have a minimum of two years of performance.

c. No Individual Project Value shall be less than $2 Million. The Project Value for completed projects is determined by the total obligated dollars. Project value for ongoing projects is determined based on the total estimated value (inclusive of all option periods).

d. The Offeror’s Relevant Experience Projects may have been performed as a Prime Contractor or as a Principal Subcontractor as defined in Section L. EXCEPT, scoring element 9.1.6 must have been performed as a Prime Contractor. If providing Relevant Experience Projects as a Principal Subcontractor, the completed Attachment L-3 shall be submitted with a PCO, COR, or Principal Deputy Program Manager (PDPM) verification and signature.

Each offer will be limited to a MAXIMUM of five (5) Experience Projects for each MAC Self-Scoring Worksheet. All of the individual elements in the Attachment L-1 and Attachment L-2 Document Verification and Self-Scoring Worksheets will apply only to the same five (5) projects. Relevant Experience is tied solely to the Relevant Experience Projects submitted under Section 9.1.1.

For each Relevant Experience Project, Offeror’s must provide the following:

1. A completed Attachment L-3, Relevant Experience Project Template. All fields in the template must be completed. No other format will be considered.

2. Copy of Contract SOW - The SOW, or Performance Work Statement (PWS), from the contract that describes the general scope, nature, complexity, and purpose of the supplies or services the customer acquired under the contract. Additionally, the Offeror must also identify and call attention to the specific section or sections of the SOW that support the claim of having performed the claimed scoring elements on Attachment L-1 and/or Attachment L-2.

3. Federal Procurement Data System – Next Generation (FPDS-NG) - FPDS-NG Report that provides verification of all claimed scoring elements included on the Attachment L-3, Relevant Experience Project Template. See Attachment L-4, FPDS-NG Sample, for examples of which fields will provide appropriate verification of scoring elements. (If multiple FPDS-NG reports are available, the most recent report shall be submitted as well as any previous reports necessary for verification of claimed scoring elements.)

4. Copy of original contract award document, this may include the following:

Standard Form (SF) 1449 – Solicitation/Contract/Order for Commercial Items – (Block 17a identifies the Prime Contractor; Block 9 identifies the U.S. Federal Government Agency, Block 3 identifies the Award/Effective Date, and Block 31c. identifies the date the Contracting Officer signed)

SF 26 – Award/Contract – (Block 7 identifies the Prime Contractor, Block 5 identifies the U.S. Federal Government Agency, Block 3 identifies the Effective date, and Block 20C identifies the date the Contracting Officer signed)

SF 33 – Solicitation, Offer, and Award – (Block 15A identifies the Prime Contractor, Block 7 identifies the U.S. Federal Government Agency, and Block 28 identifies the date the Contracting Officer awarded/signed)

Department of Defense (DD) 1155 – Order for Supplies or Services (Block 9 identifies the Prime Contractor, Block 6 identifies the U.S. Federal Government Agency, Block 3 identifies the date of Order, and Block 24 identifies the Contracting Officer signature)

The Offeror must substantiate all information by providing enough evidence within a contract or task order document or other verifiable contractual documents to support each answer. The Offeror may provide any official, verifiable documentation necessary to validate any scored evaluation elements being claimed.

Alternatively, a Procuring Contracting Officer (PCO) with cognizance over the submitted project or Contracting Officer’s Representative (COR) or Principal Deputy Program Manager (PDPM) directly associated with the project may provide written verification of any individual claimed scored evaluation element. Any individual claimed scored evaluation element that is verified and signed off on by a PCO, COR or PDPM on the Section L, Attachment L-3 does not require additional supporting documentation for those elements. Any individual claimed scored evaluation element not verified by a PCO, COR or PDPM shall require official and verifiable supporting documentation.

9.1.2 Relevant Experience Project under Product Service Code (PSC) R408

For each Relevant Experience Project submitted under Section 9.1.2, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the PSC that represents the service purchased by the Federal Government and reported in the Federal Procurement Data System (FPDS) was issued under R408.

9.1.3 Relevant Experience Individual Project Value

For each Relevant Experience Project submitted under Section 9.1.3, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the value of a Relevant Experience project is equal to or greater than $7 Million on an annual basis.

9.1.4 Relevant Experience Project with ACAT Programs

9.1.4.1 For each Relevant Experience Project submitted under Section 9.1.4, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project was identified as a Rapid Development Capabilities (RDC) program as defined by SECNAVINST 5000.42. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.4.2 For each Relevant Experience Project submitted under Section 9.1.4, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project was identified as a DoDI 5000.02 ACAT I program. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.4.3 For each Relevant Experience Project submitted under Section 9.1.4, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project was identified as a SECNAV 5000.2E Abbreviated Acquisition Program. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.5 Relevant Experience Project with Phase of Programs

9.1.5.1 For each Relevant Experience Project submitted under Section 9.1.5, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project performance covered the Materiel Solution Analysis (MSA) phase of the Acquisition Life Cycle as defined in the DoDI 5000.02. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.5.2 For each Relevant Experience Project submitted under Section 9.1.5, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project performance covered the Technology Maturation and Risk Reduction (TMRR) phase of the Acquisition Life Cycle as defined in the DoDI 5000.02. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.5.3 For each Relevant Experience Project submitted under Section 9.1.5, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project performance covered the Engineering and Manufacturing Development (EMD) phase of the Acquisition Life Cycle as defined in the DoDI 5000.02. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.5.4 For each Relevant Experience Project submitted under Section 9.1.5, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project performance covered the Production and Deployment (P&D) phase of the Acquisition Life Cycle as defined in the DoDI 5000.02. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.5.5 For each Relevant Experience Project submitted under Section 9.1.5, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project performance covered the Operations and Support (O&S) phase of the Acquisition Life Cycle as defined in the DoDI 5000.02. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.6 Relevant Experience Project with Unmanned Systems and Weapon Systems

L-1 Document Verification and Self-Scoring Worksheet for Unmanned Systems (U)

For each Relevant Experience Project submitted under Section 9.1.6, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project supported one of the following Unmanned Aerial Systems (UAS). An acceptable verification requirement may include the SOW from the Relevant Experience Project. Scoring element 9.1.6 must have been performed as a Prime Contractor.

· Group I UAS

· Group II UAS

· Group III UAS

· Group IV UAS

· Group V UAS

L-2 Document Verification and Self-Scoring Worksheet for Weapon Systems (W)

For each Relevant Experience Project submitted under Section 9.1.6, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project supported one of the following Weapon Systems. An acceptable verification requirement may include the SOW from the Relevant Experience Project. Scoring element 9.1.6 must have been performed as a Prime Contractor.

· Air-to-Ground Missile Systems

· Air-to-Surface Missile Systems

· Air Launched Rocket Systems

· Strike Planning and Execution Systems

· Precision Guided Bomb Systems

· Aerial Target Systems

9.1.7 Relevant Experience Project with Operations Support

9.1.7.1 For each Relevant Experience Project submitted under Section 9.1.7, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified operations support for processing and management of travel orders and travel vouchers. Support may include preparation, review, tracking, and coordination of tasks associated with travel. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.7.2 For each Relevant Experience Project submitted under Section 9.1.7, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified operations support for tracking action items. Support may include maintaining, review, tracking, coordination, and closure of action items and/or an action item log/database. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.7.3 For each Relevant Experience Project submitted under Section 9.1.7, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified operations support for the development of executive level briefs. Support may include preparation, review, and coordination with stakeholders of executive level briefs. Executive level is defined as PEO or equivalent Echelon III Commander, Assistant Secretary of the NAVY (ASN), Office of the Chief of Naval Operations (OPNAV), United States Marine Corp (USMC), and Office of the Secretary of Defense (OSD). An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.7.4 For each Relevant Experience Project submitted under Section 9.1.7, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified operations support for development of Executive Review Board (ERB) briefs and Annual Program Office Reviews (APORs). Support may include preparation, review, and coordination of ERB and PEO(U&W) APOR briefs. An acceptable verification requirement may include a SOW.

9.1.7.5 For each Relevant Experience Project submitted under Section 9.1.7, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified operations support for Naval correspondence. Support may include preparation, review, and coordination/dissemination of messages, forms, and correspondence. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.7.6 For each Relevant Experience Project submitted under Section 9.1.7, the Offeror will receive additional points for a MAXIMUM of 5 Relevant Experience projects if the project identified operations support for submitting visitor requests. Support may include preparation, processing, statusing and coordination of visit requests. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.8 Relevant Experience Project with Acquisition Support

9.1.8.1 For each Relevant Experience Project submitted under Section 9.1.8, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified acquisition support for development of acquisition documentation. Support may include research, development, review, analysis, revision, and tailoring of acquisition documentation. Acquisition documentation may include, but is not limited to; Acquisition Plan (AP), Acquisition Program Baseline (APB), Program Protection Plan (PPP), and other acquisition documents in accordance with DoDI 5000.02. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.8.2 For each Relevant Experience Project submitted under Section 9.1.8, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified acquisition support for development of Procurement Initiation Documents (PIDs). Support may include preparation, review, processing, tracking, reporting and coordination of PIDs. PIDs may include but are not limited to; Statement of Work (SOW)/Statement of Objectives (SOO)/Performance Work Statement (PWS), Contract Data Requirements Lists (CDRLs), Specifications, and other attachments. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.8.3 For each Relevant Experience Project submitted under Section 9.1.8, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified acquisition support for acquisition reporting as defined in the DoDI 5000.02. Support may include preparation, review, processing, and coordination of ASN(RDA) Information System (RDAIS), Defense Acquisition Executive Summary (DAES), and Selected Acquisition Report (SAR) reports. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.8.4 For each Relevant Experience Project submitted under Section 9.1.8, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified acquisition support for monitoring the status of acquisition documentation. Support may include tracking, routing, review, and coordination of the status of the acquisition documentation through applicable stakeholders to include PEO, NAVAIR competencies, and external NAVAIR customers. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.9 Relevant Experience Project with Project Management Support

9.1.9.1 For each Relevant Experience Project submitted under Section 9.19, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified management support for program road maps. Support may include research and coordination with other acquisition programs in support of development of program road maps. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.9.2 For each Relevant Experience Project submitted under Section 9.19, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified management support for tracking of program hardware/software Government Furnished Equipment/Information/Property (GFE/I/P). Support may include monitoring, tracking, reporting, and coordination of GFE/I/P and verification of contractual requirement dates. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.10 Relevant Experience Project with Schedule Support

9.1.10.1 For each Relevant Experience Project submitted under Section 9.1.10, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified schedule support for development of project schedules. Support may include development, coordination, monitoring, analysis, facilitation of review, and statusing of Government project schedules. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.10.2 For each Relevant Experience Project submitted under Section 9.1.10, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified schedule support for monitoring adherence to a prime contractor delivery schedule. Support may include tracking, review, and coordination with the prime contractor to determine status of delivery timelines. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.10.3 For each Relevant Experience Project submitted under Section 9.1.10, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified schedule support for monitoring schedule and milestone changes to ensure compatibility with program office schedules. Support may include providing schedule update recommendations, submitting and tracking schedule baseline change requests, and schedule baseline maintenance. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.11 Relevant Experience Project with Risk Management Support

9.1.11.1 For each Relevant Experience Project submitted under Section 9.1.11, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified risk support for development of risk mitigation strategies. Support may include identification of risk and development of mitigation plans, risk cubes, and strategies. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.11.2 For each Relevant Experience Project submitted under Section 9.1.11, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified risk support for facilitating risk management meetings and risk boards. Support may include coordination/facilitation of risk management meetings, recording of actions, and dissemination of minutes. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.11.3 For each Relevant Experience Project submitted under Section 9.1.11, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified risk support for a risk management database. Support may include establishment and maintenance of a risk management database. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.12 Relevant Experience Project with Configuration and Data Management Support

9.1.12.1 For each Relevant Experience Project submitted under Section 9.1.12, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified configuration and data management support for monitoring ECP packages and other configuration changes. Support may include identification, coordination, tracking, reviewing, and implementation of the ECPs. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.12.2 For each Relevant Experience Project submitted under Section 9.1.12, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified configuration and data management support for development of configuration management plans. Support may include development, coordination, and implementation of configuration management plans. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.12.3 For each Relevant Experience Project submitted under Section 9.1.12, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified configuration and data management support for coordination of Contract Data Requirement List (CDRL) submittals. Support may include coordination of comments with CDRL owner, preparation of CDRL submittals, signature coordination, and dissemination to contractor. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.12.4 For each Relevant Experience Project submitted under Section 9.1.12, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified configuration and data management support for monitoring CDRL deliveries in a CDRL Tracking Tool. Support may include establishment, population, maintenance, and notification to Government recipients of CDRL delivery. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.13 Relevant Experience Project with Cybersecurity/Information Assurance (IA) Support

9.1.13.1 For each Relevant Experience Project submitted under Section 9.1.13, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified cyber security/information assurance (IA) support for review of cybersecurity/IA strategies and recommendations. Support may include reviewing, documenting, coordinating, and analyzing cybersecurity/information assurance strategies for improvement recommendations. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.13.2 For each Relevant Experience Project submitted under Section 9.1.13, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified cyber security/information assurance (IA) support for assisting with the preparation of artifacts supporting Risk Management Framework and CYBERSAFE requirements. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.14 Relevant Experience Project with Foreign Military Sales (FMS) and International Support

9.1.14.1 For each Relevant Experience Project submitted under Section 9.1.14, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified Foreign Military Sales (FMS) and International support for development of Letters of Offer and Acceptance (LOA). Support may include coordination, preparation, and analysis of LOAs. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.14.2 For each Relevant Experience Project submitted under Section 9.1.14, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified Foreign Military Sales (FMS) and International support for development of Technology Transfer Security Assistance Review Board (TTSARB) documentation. Support may include coordination with stakeholders, preparation, review, and revision of TTSARB documentation. Stakeholders are defined as Navy International Program Office (NIPO), NAVAIR Security, and NAVAIR competencies. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.14.3 For each Relevant Experience Project submitted under Section 9.1.14, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified Foreign Military Sales (FMS) and International support for case administration and closure operations. Support may include assisting in case development and management, examination, analysis, and coordination of case execution and closure operations. An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.14.4 For each Relevant Experience Project submitted under Section 9.1.14, the Offeror will receive additional points for a MAXIMUM of 5 Relevant Experience projects if the project identified Foreign Military Sales (FMS) and International support for Price and Availability documentation. Support may include coordination, monitoring, and reconciliation of documentation in Defense Security Assistance Management System (DSAMS). An acceptable verification requirement may include the SOW from the Relevant Experience Project.

9.1.14.5 For each Relevant Experience Project submitted under Section 9.1.14, the Offeror will receive points for a MAXIMUM of 5 Relevant Experience projects if the project identified Foreign Military Sales (FMS) and International support for documentation releasability.