RFP Amendment M67854-23-R-1000-0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to incorporate the follow ing changes:

1) Extend proposal submission due date from 20 June 2023 to 27 June 2023 ; and

2) Revise the Period of Performance contained in clause 52.216-18 Ordering from 120 months to 60 months.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 19

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

16C. DATE SIGNED

BY 14-Jun-2023

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

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X M6785423R1000

X 9B. DATED (SEE ITEM 11)

21-Apr-2023

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

14-Jun-2023

CODE

COMMANDER MARINE CORPS SYSTEMS COMMAND

2200 LESTER STREET

QUANTICO VA 22134

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M6785423R1000

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 20-Jun-2023 03:00 PM to 27-Jun-2023 03:00 PM.

The following have been modified:

52.212-1 INSTRUCT TO OFFERORS

Instructions to Offerors

1. Overview

The Government Ground Combat Element Systems (GCES) portfolio is seeking potential

Offerors with the capability to provide the products described in this solicitation. The proposal process will be a single-phase effort consisting of a written proposal leading to the award of a single source Indefinite Delivery Indefinite Quantity (IDIQ) contract. The Government intends to conduct a source selection in accordance with the competitive source selection procedures contained in the Federal Acquisition Regulation (FAR) Part 15, in conjunction with FAR Part 12.

The Not-to-Exceed (NTE) maximum contract value for this IDIQ shall be $500M.

NOTE: Any reference to “solicitation” or “this solicitation” shall be deemed to include all exhibits and attachments thereto.

THE GOVERNMENT RESERVES THE RIGHT TO REJECT ANY PROPOSAL THAT

DOES NOT SUBSTANTIALLY COMPLY WITH THESE PROPOSAL PREPARATION

INSTRUCTIONS.

2. General

A single, concise, and comprehensive proposal is required. Corporate, clarity, accuracy of information, relevance, and completeness are of prime importance. The proposal shall be complete and clear in all respects without the need for additional explanation or information.

The proposal shall be in sufficient detail and scope to permit the Government to evaluate it with respect to the evaluation factors specified in Evaluation Factors for Award.

Unnecessarily elaborate proposals beyond what is sufficient to present a complete and effective proposal are not desired. Offerors shall confine the proposal submission to essential matters, sufficient to define the offer, and provide an adequate basis for evaluation. Likewise, Offerors are cautioned against general, vague, or unsubstantiated statements, which prevent or render difficult the Government’s evaluation of the proposal. Statements such as “will comply,” or

“noted and understood,” without supporting narrative to demonstrate compliance, may cause an offeror to be evaluated as unacceptable. Moreover, the Government will not assume that an offeror possesses any capability, understanding, or commitment that is not specifically delineated and supported in its respective proposal.

As prescribed by FAR 52.215-1, the Government may award on the basis of initial proposals received, without discussions. Therefore, each initial proposal should contain the offeror’s best terms from a price and technical standpoint.

Proposals submitted for consideration for award must address the full scope of the solicitation.

Proposals which address only part of the solicitation will be considered unacceptable. Limits on the number of pages in the proposal have been imposed, as indicated in Table 2, Proposal

Outline Table, below. In the event an offeror exceeds the maximum page limit, the Government will only evaluate the number of pages prescribed (starting with page one and continuing until the maximum number is reached) for the respective volume. All pages, or any other material, in excess of the maximum number of pages stated will not be evaluated.

Data, even though previously submitted or presumed known by the Government, cannot be considered as part of the offeror’s proposal unless submitted with, and incorporated into, the proposal.

All or part of the successful Offeror’s technical proposal may be incorporated in any contract resulting from this solicitation. Nothing contained in the successful Offeror’s technical proposal shall constitute a waiver to any requirement of the contract. In the event of any conflict between the successful Offeror’s technical proposal and any portion of the contract, the conflict shall be resolved in favor of the contract.

Offerors should frequently check the Contract Opportunities website at https://sam.gov/ for information concerning the requirement, responses to questions, and any issued amendments.

Submission Instructions

Offerors shall submit their proposals; Volumes I-III at the location listed below no later than

3:00 pm Eastern Standard Time (EST) on June 27, 2023 to the point of contacts listed in Section

3. Any proposal received after such time and date will be considered a late submission. Late submissions will be treated in accordance with FAR 52.215-1(c)(3). Facsimile submissions are not acceptable and will not be considered for award. Proposals shall be valid for a period of not less than 180 days from the closing date listed above.

Offerors shall prominently mark all proposals with the following:

“SOLICITATION M67854-23-R-1000”

The offeror shall submit two (2) hard copy proposals to the following address:

Marine Corps Systems Command

2201A Willis Street

Quantico, VA 22134-6050

Attn: Nathaniel Sudbeck, Solicitation: M67854-23-R-1000 https://sam.gov/

The Government will accept proposals from any delivery service allowing independent tracking and receipt verification from both parties.

3. QUESTIONS AND CLARIFICATIONS

Questions regarding the solicitation documents are due by 5:00 pm EST on May 10, 2023 and must be submitted via e-mail to cori.kirkbride@usmc.mil and nathaniel.sudbeck@usmc.mil in the format specified in Table 1 with the subject line M67854-23-R-1000. Please do not bundle multiple questions into one. The Government reserves the right to merge similar questions and to eliminate duplicative questions. Questions received after the above time and date may not be answered. Government responses will be posted on the sam.gov website. No information concerning this solicitation or requests for clarifications will be provided via telephone.

Table 1: Question Format

Question

Number

Document/Section Paragraph

Number

Question/Issue/Concern

General Issue

Solicitation

SOW

Other

NOTE: The Government is not responsible for the omission of responses to Offerors whose requests for clarification did not use the required subject title.

4. Solicitation Classified Material

In order for Offeror’s to receive Solicitation Attachment 2 – Performance Specification

(PSPEC) and Exhibit B – ICDs, Offerors shall request via email to the POCs identified in

Section 3 above and provide the Offeror’s Cage Code and email addresses the documents are to be sent to. This request to be made by the Offeror is required due to these documents classified as Controlled Unclassified Information (CUI). Once the Offeror’s Cage Code has been verified, the Government will deliver these documents via DoD SAFE.

PSPEC section 3.5.5. Laser Protection contains a classified material reference, MIL-PRF-49257.

Classified material references contained within the PSPEC are classified SECRET. The

Government is providing the PSPEC as Attachment 2 to the Solicitation, however, Offerors requesting the classified and restricted material listed within the PSPEC must submit the DD

Form 254, provided as Attachment 3. The Government will verify the Offeror’s eligibility

(current facility security clearance and appropriate storage capability) and provide the Annex via postal mail. Offerors requesting this classified material shall provide their classified mailing address along with their completed DD Form 254. The Offeror’s request for this classified material shall be submitted by 5 May 2023. Further dissemination of classified material by

Offerors is UNAUTHORIZED.

The Contractor shall handle all classified material in accordance with the DD254, Classified

Annex, the National Industrial Security Program Operating Manual (NISPOM) (DoD 5220-22-

M), and Industrial Security Regulation (DoD 5220.22-R). The Government will verify all mailto:cori.kirkbride@usmc.mil mailto:nathaniel.sudbeck@usmc.mil

Facility Clearance (FCL) information through the Defense Security Service for all Offerors and their subcontractors. Offerors without a security FCL will not be able to discuss or access key aspects of the program that are classified nor will they be able to pass such information on to their subcontractors. An Offeror without an FCL will still be able to submit a proposal, however, Offerors shall have a minimum SECRET FCL at the time of proposal submission in order to receive classified material containing objective requirements. The Government will only release this objective requirement to Offerors possessing the appropriate facility clearance (provided under separate cover upon request). Offerors are not required to propose to this objective requirement in order to be eligible for consideration/award. Lack of an FCL will not make an

Offeror’s proposal unawardable. The offeror without an FCL accepts the risk of not meeting the classified performance objective. The Marine Corps will not sponsor FCL for offerors at any time, including during the period of performance.

5. NOTIFICATION OF POTENTIAL ORGANIZATIONAL CONFLICT(S) OF

INTEREST

The Offeror is reminded that certain existing contractual arrangements may preclude or restrict participation as either a Prime Contractor or Subcontractor under this competitive procurement.

Existing contractual arrangements in which a Contractor provides support to GCES operations, or related activities are of primary concern. General guidance may be found in FAR 9.505;

however, this guidance is not all-inclusive. The Offeror’s attention is directed to the

“Organizational Conflict of Interest” or similar requirement which may be contained in current or completed contract(s) which prohibits the Prime or Subcontractor from providing certain supplies or services to the Government as described above during the period of the current

“support” contract(s) or for a period after completion of the “support” contract(s).

Notwithstanding the existence or non-existence of an Organizational Conflict of Interest (OCI) clause or similar requirement in current or completed contract(s), the Offeror shall comply with

FAR 9.5 and identify whether an OCI exists and not rely solely on the presence of an OCI requirement.

Offerors shall review their existing contractual arrangements to determine whether they believe a potential conflict of interest exists, at any tier. If an Offeror believes a potential conflict of interest exists, the Offeror is required to notify the Contracting Officer (KO) within seven (7) calendar days of the date of this solicitation. The Offeror shall provide at this time the following information: (1) the contract number and name and phone number of the Contracting Officer for the contract which gives rise to a potential OCI; (2) a copy of the requirement; (3) the statement of work (or technical instruction) from the existing contract; (4) a brief description of the type of work to be performed by each Subcontractor under the competitive procurement; (5) a proposed mitigation plan; and (6) any additional information the Contracting Officer should consider in making a determination of whether a conflict of interest exists. The Government may independently verify the information received from the Offeror.

Notwithstanding the above, the Government reserves the right to determine whether a conflict of interest exists based on any information received from any source. Any Offeror who is determined to have an OCI that cannot be mitigated will be deemed ineligible to participate in the current competition and will have their proposal rejected. The Government will make the determination that the conflict of interest has been mitigated.

The Government will notify the Offeror of any conflict of interest within fourteen (14) calendar days of receipt of all required information. Those Offerors deemed to have a conflict of interest may be ineligible for award. Failure to provide the information in a timely manner does not waive the Government's rights to make a conflict of interest determination. All proposal preparation and expenditures are at the Offeror’s own risk and will not be reimbursed by the

Government if it is determined that an organizational conflict of interest exists.

Any Offeror that proposes a Subcontractor later determined to have a conflict of interest and deemed ineligible to participate in the current competition, may not be granted the opportunity to revise its proposal to remove the ineligible Subcontractor. The Government reserves the right to determine which Offerors continue as part of the evaluation through the normal source selection process.

6. INSTRUCTIONS FOR PREPARATION OF PROPOSALS

To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to address all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, and must thoroughly address all evaluation factors. Failure to adequately address an evaluation factor shall result in an Offeror being ineligible for award.

Margins and Fonts: Proposals shall be prepared using uncompressed “Arial” or “Times New

Roman” font no smaller than 12-point. Font size no smaller than 10-point may be used in flow charts, diagrams, and tables. Margins shall be 1 inch on all four sides. All materials submitted may be no more condensed than single-spaced and shall not use proportional spacing or any other method in an attempt to get more text on the page than is here specified. Offerors shall ensure that each page provides identification of the submitting Offeror in the header or footer.

The header and footer may use the margins at the top and bottom of the page, but the substance of the proposal may not. Each page of the Offeror’s proposal shall contain the following legend at the bottom: Source Selection Information – See FAR 2.101 and 3.104.

Pages: The definition of a page is a single side of paper with text, drawings, data, or similar content. Pages shall be 8.5 x 11 inches in size. Foldouts are allowed for technical diagrams, shall be no larger than 11 inches x 17 inches, and shall be counted as two pages.

Page Limitations: Page limitations are identified for each Volume/Section of the proposal, as described in Table 2 below, and will be treated as maximums. The maximum page limits identified in Table 2 are sequential; excess pages (those that exceed stated page limitations) will not be read or considered in evaluation of the proposal. Unless stated otherwise herein, pages providing graphics, charts, illustrations, and pictures are included in the page count. Any proposal that is prepared inconsistently with the intent of these instructions, that appears to be designed to avoid or circumvent the page limits, or that in any way inhibits the

Government’s ability to evaluate offers on an equal basis may result in portions of the proposal being disregarded, or the entire proposal being rejected as non-conforming.

Format: The Offeror shall submit the Business and Technical Volumes proposal in Adobe

Acrobat .pdf files. The price breakdown shall include Microsoft Excel spreadsheets with formulas intact.

Offerors shall submit two (2) CDs with their proposal submission. Electronic file naming convention: Please name all files submitted electronically as follows: company, volume

#document title.xxx; where xxx is the file type (i.e. .xls or .doc).

Each Offeror must submit its proposal materials in separate volumes and files as identified in

Table 2 below. Each volume shall contain a title page, table of contents, and a list of tables and figures for that volume. The title page, table of contents, and list of tables and figures do not count against page count. Number all pages sequentially. Only material allocated to a specific section shall be in that section.

Business and Technical Volumes shall be submitted in three separate volumes. Each volume shall be compatible with Microsoft Office 2003-2007, Microsoft Project 2007 for PC, or Adobe

Acrobat PDF files, as applicable.

In each volume, Offerors shall provide a Table of Contents and Acronym List and Glossary. The

Technical Volume shall include a Cross-Reference Matrix showing the proposal paragraph number where an evaluator will find the detailed discussion of the requirements listed in the

Statement of Work and Performance Specification. The Cross-Reference Matrix will not be included as part of the page count.

7. Proposal Volume Breakout

The Offeror shall present pertinent information in the appropriate sections as indicated below.

Volume page maximums shall be limited in accordance with the following table:

Table 2: Proposal Outline Table

Section Part Title Maximum Pages File Naming

Structure

Volume I

Section 1.1

Executive Summary 2 ABC_ES

Section 1.2 Exceptions, Deviations, Conditions And Assumptions

5 ABC_EDCA

File Naming

Structure

Section 1.3

Statement of Work

(SOW)/Performance

Specification (PSPEC) Cross

Reference Matrix

No page limit; this document must not include substance of the Technical

Approach and will not be considered in assessing the

Technical

Approach, other than to assist evaluators in locating portions of the proposed approach.

ABC_PCM

Section 1.4 Acronym List and Glossary No page limit ABC_AL

Factor 1 - Technical Approach

Section 2.1

Statement of Work (SOW)/

Performance Specification

(PSPEC) Approach

ABC_VolI_Tech

_App

Section 2.1.1 Product Description 35 ABC_VolI_PD

Section 2.1.2 PSPEC Modeling Data No Page Limit ABC_VolI_Mod

Section 2.2

Integrated Product Support 5 ABC_VolI_Tech

_LCAT

Section 2.3 Overarching Program

Management Approach

ABC_VolI_Mg mt_PMA

Section 2.4

Management Tools, Governance, and Partnering

Approach

ABC_VolI_Mg mt_TGP

Section 2.5 Manufacturing Approach 2 ABC_VolI_Mg mt_MA

Factor 2 – Small Business Participation

Section 3 Small Business Participation 5 ABC_VolI_Tech

_SB.

Volume I Maximum Total Page Count 74

Volume II

Factor 3 - Past Performance

File Naming

Structure

Section 1.1 Recent and Relevant Past

Performance

ABC_VolII_PP

Volume III

Factor 4 – Price

Section 1.1 Pricing Workbook No Limit ABC_VolIII_PT

O_Pricing

8. INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT

8.1 Volume I, Section 1.1 - Executive Summary:

An Offeror’s proposal shall include a transmittal letter that includes the following:

• Solicitation number

• Government issuing office identification

• Full official name and address of firm, company size, along with CAGE code

• Name, phone number, and email address of the individual designated as the contact for the firm

• Reference to the enclosures or volume numbers and quantities being provided for each, and

• The date of the enclosures or volumes if different from the date of an Offeror’s proposal

An authorized official of the Offeror shall sign the transmittal letter. On the first page of this volume, the Offeror shall certify that the proposal has been prepared completely consistent with the terms and conditions of the solicitation or that any exceptions, deviations, and waivers to the solicitation are addressed in the Executive Summary. If any exceptions, deviations, and/or waivers are taken the proposal may be determined non-compliant and thus, ineligible for award.

This section shall include an overall Executive Summary that describes the significant attributes of the Offeror’s proposal and describe the Offeror’s understanding and capability to accomplish the requirements of the contract. This part shall identify the Offeror’s cognizant Defense

Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Defense

Finance and Accounting Services (DFAS) payment office.

Confirmation: Confirm that representations, certifications, acknowledgments, and statements have been completed electronically. (Note: Offerors must also comply with the System for

Award Management (SAM) requirements of FAR Clause 52.204-7).

Valid Period: State clearly the period for which the proposal is valid (not less than 180 calendar days).

8.2 Volume I, Section 1.2 - Exceptions, Deviations, Conditions, Assumptions, and Waivers:

This section shall contain all exceptions, deviations, conditions, and assumptions that the Offeror takes with respect to the provisions of the solicitation and its applicable documents. An exception is where an Offeror states it will not comply with a requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a requirement but proposes an alternative to meet the intent of the requirement, usually involving a specification. Conditions are any contractor requirements, which, if not met, would reduce or remove the contractor’s obligation to perform the contract according to the solicitation’s terms.

An assumption is the Offeror’s understanding of something not expressly stated in the solicitation, such as circumstances that might impact the Offeror’s benefits and burdens under a resulting contract.

If the Offeror submits a proposal including any of the preceding features, the Offeror shall provide a description of each exception, deviation, condition, or assumption. Indicate the

Offeror's difficulty with the applicable requirement and the Offeror's proposed solution, where applicable. Specifically identify the portions of the solicitation and the Offeror's proposal that are affected.

The Government may incorporate all or part of the successful Offeror’s technical proposal in any contract resulting from this solicitation. Additionally, the Performance Specification in the awarded contract will reflect all above-minimum performance levels or capabilities for which the

Government gave evaluation credit during source selection. Nothing contained in the successful

Offeror’s technical proposal shall constitute a waiver to any other requirement within the contract. The Order of Precedence clause governs in instances of conflicts between the successful Offeror’s technical proposal and any other requirement of the contract. When the

Offeror’s proposal exceeds the Government’s requirement, the Offeror’s proposed solution will become the new contract requirement.

8.3 Volume I, Section 1.3 – SOW/PSPEC Cross Reference Matrix

Offerors shall create a SOW/PSPEC Cross Reference Matrix, which maps each SOW/PSPEC requirement addressed to the proposal location (Volume, Section, Page and Paragraph) where the requirement is discussed. Offerors shall not use the SOW/PSPEC Cross Reference Matrix to provide substance regarding the proposed solution or in any manner attempt to increase the volume of information permitted by the page limitations.

8.4 Volume I, Section 1.4 - Acronym List and Glossary

The Offeror shall provide a comprehensive list of all acronyms used throughout the proposal.

8.5 Volume I, Section 2, Factor 1 - Technical Approach

8.5.1 Volume I, Section 2.1 –SOW/PSPEC Approach

The Technical Approach proposal shall consist of the Offeror’s overarching technical approach to the SOW/PSPEC. The Offeror’s understanding of the technical requirements shall address the proposed system’s design parameters as well as threshold and objective performance traits.

Additionally, the offeror shall describe with supporting information and data, how their product meets the PSPEC Attributes 3.1.1, 3.1.2, 3.1.3, 3.2.10 and the attributes contained in Table 3 below:

Table 3: PSPEC Attributes Table

PSPEC Para Attribute Title

3.1.4 Weight

3.1.9 NIR Illuminator

3.1.10 Interoperability with Helmets

3.1.14 Interoperability with Power Cables

3.1.15 Interoperability with External Battery Packs

3.1.16 Interoperability with Helmet Positioning

Assemblies

3.1.17 Interoperability with Thermal Imager Mount

Adapters

3.1.18 Interoperability with LIFs

3.2.1 I2 On-Axis Limiting Resolution

3.2.7 I2 Field of View

3.2.9 I2 Target Detection

3.2.11 I2 Signal-to-Noise Ratio

3.2.12 I2 Tube Center Resolution

3.2.13 I2 Tube Halo

3.2.15 I2 Tube Photocathode Luminous Sensitivity

3.3.1 Thermal Field of View

3.3.2 Thermal Target Detection

3.4.1 Eye Relief

3.4.2 Interpupillary Distance Adjustment

3.4.4 Eyepiece Diopter Range

3.6.7.1 Internal Batteries, I2 Assembly

3.6.7.2 Internal Battery, Thermal Assembly

3.6.7.3 External Batteries, I2 Assembly

3.6.7.4 External Batteries, Combined Cold Weather

Operation

3.6.9 Auto-Off Stowage Feature

3.7.1 Storage Temperature

3.7.2 Operating Temperature

3.7.3 Temperature Shock

3.7.4 Immersion

3.7.5 Operating Altitude

3.7.6 Salt Fog

3.7.7 Electromagnetic Susceptibility

3.7.8 Sand and Dust

3.7.9 Vibration

3.7.10 Operational Drop

3.7.12 Operation in Rain

3.8.9 Single Eye Operation

3.8.12 Mount Interface Mechanical Backlash

3.9.2 Availability/Reliability

To demonstrate compliance with the weight parameters, the offeror shall provide a table listing the weight of each component listed in PSPEC 3.1.4.

For all other PSPEC requirements not mentioned above, the offeror’s proposal shall confirm either meeting the requirement’s thresholds or objectives or shall document any variance from the requirement.

Furthermore, offerors shall describe how they will meet the required Contract Data

Requirements List (CDRLs). The Offeror shall also provide details as to how they will meet each SOW requirement. All proposal responses, as outlined below, shall ensure consideration of and compliance with the pertinent performance standards within the SOW.

8.5.1 Volume I, Section 2.1.1– Product Description

The offeror shall provide a detailed Product Description (PD) which describes the attributes of their system comparative to the PSPEC.

8.5.1 Volume I, Section 2.1.2– PSPEC Modeling Data

The offeror shall provide modeling data which supports the PD performance claims of their system comparative to the PSPEC. Offerors shall provide sensor performance modeling input decks to validate claims from Table 3 – PSPEC Attributes Table via hard copy as raw output text files as well as in electronic format appropriate to the modeling software (e.g., .xml for NV-

IPM). Offerors shall specify which modeling software, version, and date for the model it uses for each sensor.

8.5.2 Volume I, Section 2.2 – Integrated Product Support

The Offeror shall detail their approach to supporting the Marine Corps maintenance requirements from organizational to intermediate levels of maintenance in accordance with SOW.

Additionally, the Offeror shall provide a detailed explanation of their commercial warranty, including its duration, any limitations, and any actions that could void the warranty.

8.5.3 Volume I, Section 2.3 - Overarching Program Management Approach

The Offeror shall provide a detailed and thorough PM approach that demonstrates the Offeror’s capability to effectively manage and execute the SOW requirements. The Offeror shall provide detailed information concerning the various methods or techniques to be used in planning, scheduling, processing, controlling, and completing the requirements in the SOW.

The Offeror shall provide corporate charts and show the proposed management structure, teaming relationships, Subcontractors, and organizational elements. The Offeror shall describe the organizational boundaries and interfaces between the Offeror and external entities and how communication and coordination of efforts will be managed. “External” is defined as any entity or organization not on the Offeror’s team (e.g., program office, system users, hosting facilities).

The Offeror shall also describe the internal structure; “Internal” is defined as and entity or organization within the Offeror’s team including roles and responsibilities, of the Offeror’s team to include Subcontractors.

The Offeror shall describe the processes and procedures the Offeror will employ to execute management and oversight tasks in support of the requirements in the SOW. The Offeror shall describe their approach for maintaining project schedule, operating within approved budgets, meeting project milestones, providing early notification of potential problems, utilizing management metrics to track progress and trends, providing deliverables on-time, and maintaining ongoing operations in an effective manner.

At a minimum, the Offeror shall define and describe:

• Processes: Must define how the Offeror’s proposed processes will support the requirements defined in the SOW.

• Planning: Must define the Offeror’s contract planning, coordination, and schedule as well as methods, tools, and techniques used to estimate schedule and resource requirements.

• Staffing: Explain the process to recruit and retain qualified staff. Explain how the

Offeror will identify and acquire qualified or incumbent staff. The Offeror shall include the approach used to manage all Subcontractors, regardless of company size, in the staffing plan. Offeror shall include a list of all proposed subcontractors with a proposed subcontract value estimated at $10 million or more, to include the following information:

Name, address, individual’s name/point of contact, and telephone number.

• Resource Acquisition: Must specify the plan for acquiring the resources (other than staffing) needed to successfully execute the contract, operate, and support the systems projected to be consolidated into this contract.

• Staff Training: Must specify the training that will be provided to employees working on the contract. Discuss any unique or specific training that will be provided.

• Process Improvement: Must provide a plan for periodically assessing the contract, determining areas for improvement, gaining Government approval, and implementing improvement plans.

• Risk Management: Must describe a risk management process that identifies the methods and procedures to be employed to identify, assess, monitor, and control risk during performance of this contract.

• The Contractor furnished property in support of the SOW requirements.

8.5.4 Volume I, Section 2.4 - Management Tools, Governance, and Partnering Approach

The Offeror shall describe, using SOW requirements, the application of proactive and predictive management tools and techniques to plan and manage the required effort. The Offeror shall include a description of their approach to implementing transparent governance and reporting, a sound partnering approach grounded on shared goals and objectives, proactive problem identification and resolution. This information shall describe the Offeror’s ability to ensure the logistics management oversight necessary to deliver effective operational capabilities in support of PM IW’s vision and goals across multiple TOs. The Offeror shall also describe its approach to configuration management and implementation.

8.5.5 Volume I, Section 2.5 -Manufacturing Approach

The Offeror shall provide a description of how they plan to implement configuration management and ensure consistent quality throughout contract performance. The Offeror shall describe how their manufacturing processes are designed to minimize defects (including latent defects) in materials and workmanship that degrade system performance. The Offeror shall detail their ability to manufacture quality, Berry Amendment compliant products. The Offeror shall include maximum monthly production of potential SBNVG quantities for the Offeror’s manufacturing facility. The Offeror shall also include detail into the capability to support increased production quantities based on planned future delivery order quantities.

Offerors are advised the Berry Amendment specifically restricts any funding appropriated or otherwise available to DoD from being used to buy the following end items, components, or materials unless they are wholly of US origin: An article or item of food; clothing; tents, tarpaulins, or covers; cotton and other natural fiber products; woven silk or woven silk blends;

spun silk yarn for cartridge cloth; synthetic fabric or coated synthetic fabric (including all textile fibers and yarns that are for use in such fabrics); canvas products, or wool (whether in the form of fiber or yarn or contained in fabrics, materials, or manufactured articles); or any item of individual equipment (Federal Supply Class 8465) manufactured from or containing such fibers, yarns, fabrics, or materials; and hand or measuring tools.

If the Berry Amendment does NOT apply to a proposed solution, the Offeror shall make an affirmative statement in its proposal that its proposed complete system does not contain any natural fibers or other items subject to 10 U.S.C. §4862.

If the Berry Amendment does apply, Offerors shall submit the following self-certification:

BERRY AMENDMENT SELF CERTIFICATION

I, (insert name here), in submitting this offer under solicitation number M67854-23-R-1000, affirm that only products compliant with the Berry Amendment (10 USC 4862) will be delivered to the Government. As such, all items delivered, either as end products or components, will be grown, reprocessed, reused, or produced in the United States (as defined in DFARS 252.225-

7012(b) included by reference herein). This certification covers all materials (including those of all components) and components supplied by subcontractors at any tier, and all labor (including that of all intervening processes), whether performed by the offeror or any of its subcontractors at any tier.

8.6 Volume I, Section 3, Factor 2 – Small Business Participation

The Offeror’s cover page for Small Business (SB) participation shall state percentage goals for work to be performed by small businesses with applicable breakdown of goals for proposed categories of small business concerns for the Government’s total requirement.

Table 4: Template for the SB Summary Table

SB Participation Plan

Total

Small Business (SB)

Small Disadvantaged Business (SDB)

Woman-Owned Small Business (WOSB)

HUBZone Small Business (HUBZone SB)

Small Disadvantaged Veteran-Owned Small Business

(SDVOSB)

All Offerors regardless of size shall submit a Small Business Participation Plan presenting percentages in terms of total dollars of work for each SB category.

The Offeror shall identify the extent and nature of participation of SB, WOSBs, HUBZone SBs, and SDVOSBs in the performance of the proposed contract. Participation includes subcontractors or material suppliers to the prime contractor or subcontractors. Offerors shall include in the percentages their own participation as an SB, WOSB, HUBZone SB or SDVOSB.

The plan shall include:

a. The name and SAM Unique Entity Identifier (UEI) number (or CAGE code) of each firm included in the plan;

b. A copy of the System for Award Management (SAM) profile for each firm included in the plan;

c. Discussion of the specific components or services each firm will deliver or perform;

d. Identification of the North American Industry Classification System (NAICS) code

(appropriate to the principal nature of the planned subcontract) supporting each firm’s size status;

e. The estimated total dollar value provided to each small business including the prime if they are a small business;

f. The percentage of total contract value provided to each small business including the prime if they are a small business;

g. Evidence of any enforceable commitments in place between the Offeror and the participating small businesses (i.e., detailed supporting documentation regarding the individual commitments).

If applicable, for each category in which the Offeror’s SB Participation Plan contains goals below the Government’s SB Utilization Objectives, the offeror shall provide a detailed explanation as to how the Offeror will increase the percentages for performance under contract.

Justifications adequately describing valid actions toward increasing percentage goals will receive an acceptable rating.

The Government’s SB Participation objectives for this acquisition are:

• Small Business: 5%

• Small Disadvantaged Business: 1.25%

• Women-Owned Small Business: 1.25%

• HUBZone Small Business: 1.25%

• Service-Disabled Veteran-Owned Small Business: 1.25%

8.6.1 Small Business Subcontracting Plan - LARGE BUSINESSES ONLY

The SB Subcontracting Plan is only required from large business Offerors (i.e., not a SB, SDB, WOSB, HUBZone SB or SDVOSB) and will be incorporated into any resultant contract. The

SB Subcontracting Plan describes the Offeror’s approach to maximizing small businesses opportunities in this effort relative to the subcontracted portion’s value. The Offerors shall present their SB Subcontracting Plan percentages in terms of total dollars of work for each SB category divided by the total value of subcontracts. This Small Business Subcontracting Plan submission shall not be counted against the maximum page count specified for Factor 2 – Small

Business Participation.

FAR 52.219-9 sets forth the SB Subcontracting Plan’s required elements. Offerors should address their SB Subcontracting Plans’ elements in an order similar to the FAR order to demonstrate they meet each element of the SB Subcontracting Plan. The Offeror shall provide the CAGE code or DUNS number for each proposed subcontractor and include the NAICS code

(appropriate to the principal nature of the planned subcontract) supporting each proposed subcontractor’s size status. The information in the Offeror’s SB Subcontracting Plan must correlate with its SB Participation Plan.

The Government’s SB Subcontracting Plan objectives for this acquisition are:

• Small Business: 33%

• Small Disadvantaged Business: 5%

• Women-Owned Small Business: 5%

• HUBZone Small Business: 3%

• Service-Disabled Veteran-Owned Small Business: 3%

Offerors proposing a SB Subcontracting Plan with percentages below the Government’s subcontracting objectives shall, for each category below the objective, explain in detail why they are unable to meet the objectives and what measures, if any, they will take to meet the objectives.

9. Volume II, Section 1, Factor 3 – Past Performance

9.1 Volume II, Section 1.1 - Recent and Relevant Past Performance

The Offeror shall submit three (3) recent and relevant summaries of past performance similar in size, scope, and complexity to this requirement. "Recent" is defined as an effort, whether ongoing or completed, that has at least 12 months of performance, occurring during five (5) years preceding the solicitation closing date. "Relevant" past performance would be a recent effort accomplished by the Offeror with a similar scope and complexity as the effort described in this solicitation. The Offeror must submit dollar amounts of the effort actually performed by the company for which the past performance effort is being submitted.

The Offeror shall include all requested data that illustrates the adequacy of the Offeror’s (or principle Subcontractor’s) various contracts selected to convey recent and relevant past performance. For each contract identified, the Offeror shall provide the following information:

o Name, title, email address, phone number and any additional information for the point of contact.

o A description of the contract effort, relative to this solicitation, that the

Offeror performed.

o For each contract effort, identify the Program Manager (PM) and the

Contracting Officer Representative (COR).

o The relevancy of the Offeror’s, and if applicable, the Offeror’s Principal

Subcontractors’ past performance.

o The Offeror’s past performance in the delivery of quality supplies/services, which includes meeting technical requirements.

o The Offeror’s past performance in meeting schedule requirements, to include on time or late deliveries, and modifications of original schedules.

o The Offeror’s past performance in managing the contracted effort, to include program management, subcontract management, and cooperation with the customer.

o The Offeror’s past performance in meeting any identified Acceptable Quality

Levels or minimum thresholds of performance.

o If applicable, any improvements made during performance to resolve problems with respect to the problems or issues related to performance requirements. For each past performance problem identified, describe the status of the improvement efforts and, where applicable, demonstrate the impact that the improvement effort had on resolving the systemic problem such that it would not recur.

The identified contracts shall be with Department of Defense or other Federal agencies. Past performance as a Prime, teaming partner, or as a Subcontractor will be considered, as will past performance by a company proposed as a Subcontractor to this effort. However, past performance by the Offeror as a Subcontractor may be less relevant to the overall past performance rating than past performance by the Offeror as a Prime Contractor.

For each contract of relevant work, the Offeror shall provide a Past Performance Questionnaire

(Exhibit B). The Offeror shall send out, and track the completion of, the PPQ to each of the

Offeror’s Government Points of Contact. Any completed PPQ must be submitted with their proposal. It is incumbent upon the Offeror to explain the relevance of data provided in its proposal. The Government has no duty to search for additional data to cure problems the

Government finds in the information provided by the Offeror.

Task or delivery orders awarded under single-award IDIQ or Multiple-Award Contracts (MACs) will be considered standalone “contracts” for purposes of past performance evaluation unless the

Government has definitively elected to assess performance on a contract level. Thus, Offerors shall not propose an entire IDIQ or MAC as a past performance contract reference unless there has been Contractor Performance Assessment Reporting System (CPARS) assessment(s) completed by the Government on a contract vs. order level.

In addition, regardless of relevancy, the Offeror shall provide a list of Show Cause Notices, Cure

Notices, and Terminations for Default received on any and all contracts, task orders, or delivery orders within the past five (5) years. If the Offeror has not received any Show Cause Notices, Cure Notices, or Terminations for Default in the past five (5) years, the Offeror shall insert a statement to that effect. The list or statement shall not count against the maximum page count.

The Government reserves the right to use contract performance data provided in the Offeror’s proposal and contract performance data obtained from other sources, including but not limited to, CPARS, the Government’s Excluded Parties List System (EPLS) the Specially Designated

Nationals (SDN) List.

10. Volume III, Section 1, Factor 4 – Price

10.1 Volume III, Section 1.1 – Pricing Workbook

Offeror’s proposal is presumed to represent its best efforts to respond to this solicitation. The burden of proof as to cost credibility rests with the Offeror.

It is expected that a determination of fair and reasonable pricing will be made on the basis of adequate price competition in accordance with FAR 15.404-1. Therefore, the Offeror is not required to submit or certify cost or pricing data with its proposal. If, after receipt of the proposals the Government determines that adequate price competition does not exist, the Offeror shall submit other than certified cost or pricing data as requested by the Government.

The submission of pricing in accordance with the instructions shall, if accepted by the

Government, contractually bind the Government and the Offeror to the terms and conditions of the model contract. The Offeror may prepare and submit the cost/price proposal narrative substantiation and rationale, if the Offeror determines is necessary, in Adobe Acrobat format and shall provide any numerical data in Microsoft Excel format. Offerors shall not alter the format of the spreadsheets except that column(s) and row(s) may be widened or added as needed.

The price proposal shall be submitted on both the SF 1449 and via Attachment 5: Pricing

Workbook. The Offeror shall submit pricing for every line item in the SF 1449 and Attachment

5; failure to do so may result in the proposal being ineligible for award without discussions. In the event of inconsistencies between the SF 1449 and Exhibit A, the SF 1449 shall take precedence. Any additional pricing line items required by the Offeror should be included at the end of the pricing workbook or on a new tab.

The Offeror shall provide a Recommended Buy List identifying individually priced spares and repair parts necessary for the Government to sustain an operational SBNVG.

The submission of these items in accordance with the instructions shall, if accepted by the

Government, contractually bind the Government and the Contractor to the terms and conditions of the model contract.

52.216-18 ORDERING. (AUG 2020)

(a) Any supplies and services to be furnished under this contract shall be ordered by issuance of delivery orders or task orders by the individuals or activities designated in the Schedule. Such orders may be issued from for a period of 60 months from the date of contract award.

(b) All delivery orders or task orders are subject to the terms and conditions of this contract. In the event of conflict between a delivery order or task order and this contract, the contract shall control.

(c) A delivery order or task order is considered "issued" when--

(1) If sent by mail (includes transmittal by U.S. mail or private delivery service), the Government deposits the order in the mail;

(2) If sent by fax, the Government transmits the order to the Contractor's fax number; or

(3) If sent electronically, the Government either--

(i) Posts a copy of the delivery order or task order to a Government document access system, and notice is sent to the

Contractor; or

(ii) Distributes the delivery order or task order via email to the Contractor's email address.

(d) Orders may be issued by methods other than those enumerated in this clause only if authorized in the contract.

(End of clause)

(End of Summary of Changes)