M6785422R2001-0007.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provi ded herei n, all t erms and condit ions of t he document refere nced in Item 9A or 10A, as heretofore change d, remai ns unchanged and in ful l force and effect .

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

ST ANDARD FORM 30 (Rev. 10-83) Prescr ibed by GSA

FAR (48 CFR) 53.243

Amendment 0007 is issued to extend the proposal due date f rom 13 September 2022 to 20 September 2022.

1. CO NTRACT ID CODE P AGE OF P AGES

S 1 20

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

16C. DAT E SIGNED

BY 26-Aug-2022

16B. UNITED ST AT ES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contract ing Officer )(Signature of person authorized t o sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, Count y, Stat e and Zip Code) X M6785422R2001

X 9B. DAT ED (SEE IT EM 11)

10-Jun-2022

10B. DAT ED (SEE IT EM 13)

9A. AMENDMENT OF SOLICITAT ION NO.

11. THIS IT EM ONLY APPLIES T O AMENDMENT S OF SOLICITATIONS

X The above numbered soli cit ati on i s amended as set forth in It em 14. The hour and date specified for rece ipt of Offer X is ext ended, is not extended.

Offer must acknowl edge rece ipt of t his amendment pri or to the hour and date specified in the sol ici tat ion or as amended by one of t he fol lowing methods:

(a) By compl eti ng Items 8 and 15, and returning copi es of the amendment ; (b) By acknowledgi ng recei pt of thi s a mendment on each copy of t he offer submit ted;

or (c) By s epara te let ter or t elegram whi ch i ncludes a refe rence t o t he s olic ita tion and amendment numbers . FA ILURE OF YOU R A CKNOWLEDGMENT TO BE RECEIVED AT TH E P LACE D ESIGNATED FOR TH E RECEIPT OF OFFERS P RIO R TO THE HOUR AN D DATE SP ECIFIED MA Y RESULT IN

REJECTIO N OF YOUR OFFER. If by vir tue of thi s amendment you desire t o change an offer already submit ted, s uch c hange ma y be made by t ele gram or let ter, provided each t elegram or l ett er makes reference to the sol ici tat ion and this amendment , and is re ceived prior to the openi ng hour and dat e speci fi ed.

12. ACCOUNTING AND APPROPRIATION DAT A (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 FORT H IN ITEM 14 ARE MADE IN THE

CONT RACT ORDER NO. IN ITEM 10A.

B. T HE ABOVE NUMBERED CONT RACT /ORDER IS MODIFIED T O REFLECT THE ADMINIST RATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORT H IN ITEM 14, PURSUANT TO T HE AUTHORITY OF FAR 43.103(B).

C. T HIS SUPPLEMENT AL AGREEMENT IS ENT ERED INTO PURSUANT TO AUTHORITY OF:

D. OT HER (Specify type of modification and authorit y)

E. IMPORTANT: Contract or is not, is required to sign this document and return copies t o the issuing office.

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

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/ MODIFICATION NO. 5. P ROJECT NO .(If appli cable)

6. ISSUED BY

3. EFFECTIVE DATE

26-Aug-2022

CODE

COMMANDER MARCORSYSCOM

2200 LESTER STREET

QUANTICO VA 22134

M67854 7. AD MINISTERED BY (If other t han item 6)

4. REQUISITION/PU RCHASE REQ. NO.

CODE

See I tem 6

FACILITY CODECODE

EMAIL:TEL:

M6785422R2001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

L-1.0 INSTRUCTIONS FOR THE SUBMISSION OF PROPOSALS

L-1.1 INTRODUCTION

The Government intends to meet this requirement by selecting a single contractor for a single-award, Indefinite Delivery/Indefinite Quantity contract for both systems, consisting of five, 1-year ordering periods, using a firm-fixed-price Contract Line Item Number (CLIN) structure and cost-reimbursable (no fee) Travel CLINs.

L-1.2 GENERAL

A. This section contains general instructions for submitting proposals for this effort.

1) The Government will post the Solicitation via SAM.gov and the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module.

2) A single, concise, and comprehensive proposal is required. Organization, 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 Section M of this solicitation.

3) It is the offeror’s responsibility to submit a well-written proposal with adequately detailed information, which demonstrates its clear understanding of, and compliance with, the solicitation requirements. Offerors are cautioned against making general, vague, or unsubstantiated statements; statements such as “will comply,” or “noted and understood,” without further elaboration, may cause an offeror to be evaluated as unacceptable. The Government is not obligated to assume that an offeror possesses any capability, or has demonstrated its understanding of a requirement, or committed to a particular approach unless the same is specifically described in its proposal. Proposals that merely restate the requirement or state that the requirement will be met without providing supporting rationale or substantiating data may be found to be unacceptable.

4) 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 the sections below. In the event an offer 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.

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

6) As prescribed by Federal Acquisition Regulation (FAR) Clause 52.215-1, the Government may award on the basis of initial offers received, without discussions.

Therefore, each initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions and award on the basis of proposal revisions. Each offeror may submit only one proposal in response to this solicitation. Proposals shall not contain classified information.

7) The offeror shall disclose any actual or potential OCI situations with itself, subcontractors, partners or any other offeror as it applies to this solicitation for the MCWS L/H contract award. This obligation applies even if identified prior to proposal submission. If an offeror identifies an actual or potential OCI, the offeror shall disclose the OCI. The disclosure shall include the facts and an analysis of the actual or potential conflict and recommend an approach to neutralize, mitigate, or avoid the conflict. If the contracting officer determines that any actual or potential OCIs cannot be mitigated, then the offeror shall not be eligible for award.

L-1.3 OFFEROR’S PROPOSAL REQUIREMENTS

L-1.3.1 QUESTION AND ANSWER PERIOD

A. Questions

1) All questions regarding the solicitation documents are due no later than 2:00 PM (local time, Quantico, VA) on 24 JUN 2022. Please use a Microsoft (MS) Office Word table format similar to Table L-1, when submitting your questions. Please do not bundle multiple questions into one.

Table L-1: Question Format Question Number

Document/Section Paragraph

Number Question/Concern

General Issue Solicitation Performance Spec Other

2) Questions shall be sent via email (MS Office Word format) to Wanda Harner and Katy Hurd at wanda.harner@usmc.mil and kathryn.hurd@usmc.mil respectively with a subject line of “MCWS-L/H, M67854-22-R-2001 Offeror Questions.”

3) Email is the only acceptable method of submitting questions.

B. Answers

1) The Government intends to publish written responses to questions via SAM.gov and the Solicitation Module within PIEE. The Government reserves the right to disregard or answer untimely questions, to combine or duplicate similar questions for efficiency, to edit questions for clarity, and to pose and answer questions of its own.

L-1.3.2 PROPOSAL SUBMISSION

L-1.3.2.1 The Government does not anticipate that offerors will need to submit cost or pricing data, as defined in FAR Section 2.101. However, the Government reserves the right to require the submission of Certified Cost or Pricing Data or Other Than Certified Cost or Pricing Data if it is deemed necessary for the purposes of evaluation and negotiation. By submission of an offer to this solicitation, the offeror acknowledges that Certified Cost or Pricing Data or Other Than Certified Cost or Pricing Data may be required. The PCO is the sole individual with the discretion to make the decision of whether Certified Cost or Pricing Data or Other Than Certified Cost or Pricing Data will be required. In the event that Cost or Pricing Data or Other Than Cost or Price Data are required, that data shall be submitted in accordance with FAR Clause 52.215- 20.

L-1.3.2.2 Proposals in response to this solicitation must be valid for 180 calendar days from the closing date listed above. THE GOVERNMENT RESERVES THE RIGHT TO REJECT ANY

PROPOSAL, OR PART THEREOF, THAT DOES NOT COMPLY WITH THESE PROPOSAL

PREPARATION INSTRUCTIONS. THIS INCLUDES, BUT IS NOT LIMITED TO,

PROVIDING COMPLETE AND COMPREHENSIVE SECTIONS IN ALL VOLUMES. ANY

APPARENT ATTEMPT TO CIRCUMVENT THE PAGE LIMITS OR OTHER

INSTRUCTIONS, OR ANY STEPS TAKEN THAT RENDER IT MORE DIFFICULT FOR

THE GOVERNMENT TO EVALUATE THE PROPOSAL ON A CONSISTENT AND FAIR

BASIS, MAY RESULT IN THE PROPOSAL’S REJECTION.

L-1.3.2.3 Content and Organization of Proposals

L-1.3.2.3.1 Offerors should frequently check the SAM.gov website and the Solicitation Module within PIEE for information concerning the requirement, responses to questions, and any amendments.

L-1.3.2.3.2 A legible, neat, orderly, well-organized and comprehensive proposal is required. Elaborate brochures or artwork, or expensive visual or presentation aids are neither necessary nor desirable. Offerors shall confine the proposal submission to essential matters, sufficient to define the offer, and provide an adequate basis for evaluation.

L-1.3.2.3.3 Offerors shall follow the general rule that the quality of information is significantly more important than quantity or visual esthetics of presentation. The proposal shall be in sufficient detail and scope to permit the Government to evaluate it with respect to the evaluation factors specified in Section M, Evaluation of Proposals.

Organization, clarity, accuracy of information, relevance, and completeness are of prime importance.

L-1.3.2.4 Format of Proposal: To assure a timely and fair evaluation of proposals, offerors must follow the instructions contained herein. Offerors are required to thoroughly address all evaluation factors and address all solicitation requirements, including: terms and conditions, representations and certifications, and technical requirements. Failure to adequately address an evaluation factor may result in an offeror being ineligible for award. The offeror is cautioned that some of the solicitation provisions and/or contract clauses require an offeror response/representation. Such solicitation provisions and contract clauses shall be included in the offeror's proposal response.

L-1.3.2.4.1 Margins and Fonts: Proposals shall be prepared using uncompressed “Arial” or “Times New Roman” font no smaller than 12-point. This font format and font size applies to Headers/Footers. 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. Proposals shall have no more than 46 lines of text per page, excluding headers and footers. 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 Sections 2.101 and 3.104.

L-1.3.2.4.2 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. Larger pages are allowed for technical diagrams, shall be no larger than 11 inches x 17 inches, and shall be counted as two pages. All proposal Volume pages shall be numbered sequentially (or in the preferred numbering format)

L-1.3.2.4.3 Page Limitations: Page limitations are identified for each Volume/Section of the proposal, as described in Table L-2, and will be treated as maximums. The maximum page limits identified in Table L-2 are sequential. Portions of proposals that exceed stated page limitations will not be read or considered in the 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 inconsistent with the intent of these instructions, that appears to be designed to avoid or circumvent the page limits, or that in any way makes it more difficult for the Government to evaluate offers on an equal basis may result in portions of the proposal being ignored or the entire proposal being rejected as non-conforming.

L-1.3.2.4.4 Format: The offeror must submit the proposal in MS Office 2010 or later format. The price breakdown shall include MS Excel spreadsheets with formulas intact.

L-1.3.2.4.5 Electronic file naming convention: Please name all electronic files submitted via the Solicitation module in PIEE in this manner: company-document title.xxxx; where xxxx is the file type (i.e. .xlsx or .docx).

L-1.3.2.4.6 Offerors are responsible for following all submission instructions and adequately addressing all evaluation factors. Ensure each section contains all the information necessary for evaluation under that section.

L-1.3.2.5 INTENT TO INCORPORATE CONTRACTOR’S PROPOSAL

Portions of the successful offeror’s proposal may be incorporated in any contract resulting from this solicitation, based solely on the Government’s discretion. In the event of any conflict between the successful offeror’s proposal and other requirements of the contract, the conflict shall be resolved in favor of the contract requirements.

L-1.3.2.6 Pricing Information. NO PRICING INFORMATION OF ANY KIND SHALL BE

INCLUDED IN ANY VOLUMES EXCEPT THE FOLLOWING: VOLUME III –

COST/PRICE, VOLUME V – SUBCONTRACTING & SMALL BUSINESS PARTICIPATION

AND EXHIBIT K – SPARE PARTS PRICING MATRIX

L-1.3.2.7 Proposal Submission Location, Time, and Date:

L-1.3.2.7.1 Offerors shall submit an electronic copy of all volumes of their proposals via the PIEE Solicitation Module (found at https://piee.eb.mil) by 10:00 a.m. (local time, Quantico, VA) on 20 SEP 2022. Any proposal received after such date and time will be considered a late submission. Late submissions will be treated in accordance with FAR Clause 52.215-1(c)(3). Proposals shall be valid for a period of not less than 180 days from the closing date listed above. Offerors shall prominently mark all proposal volumes with the following statement:

“REQUEST FOR PROPOSAL – SOLICITATION M67854-22-R-2001”

Source Selection Information – See FAR Sections 2.101 and 3.104.

L-1.3.2.7.2 The offeror shall submit their proposal by electronic means, via the PIEE Solicitation Module. Proposals will NOT be accepted via email; instead, all documents shall only be submitted via the PIEE Solicitation Module. Offerors must adhere to specified page limits. Proposal volumes shall be separate files and shall be titled accordingly. A vendor registration guide for contractors on how to set up accounts in the system has been posted to the Defense Pricing and Contracting website at:

https://www.acq.osd.mil/dpap/pdi/eb/docs/PIEE/PIEE Solicitation_

Module_Vendor_AccessInstructions.pdf. Proposals must be fully uploaded no later than the date and time listed above.

Table L-2: Proposal Organization

Volume Title Maximum Pages

I EXECUTIVE SUMMARY 2

Section 1.1 Acronym List and Glossary No page limit

II TECHNICAL APPROACH As defined below

Section 2.1 System Performance As defined below

Section 2.1.1 PSPEC Compliance Matrix - Light

Attachment 1, no page limit; this document must not include substance of the proposed

Technical Approach; instead, it should be used to document the proposed MCWS-L System’s compliance with the MCWS-L PSPEC, provide capability values, indicate the location of substantiating data, and note if a waiver is requested.

Section 2.1.2 PSPEC Compliance Matrix - Heavy

Attachment 2, no page limit; this document must not include substance of the proposed

Technical Approach; instead, it should be used to document the proposed MCWS-H System’s compliance with the MCWS-H PSPEC, provide capability values, indicate the location of substantiating data, and note if a waiver is requested.

Section 2.1.3 Supporting Documents (test reports, analysis, data, certifications) As applicable; no page limit

Section 2.1.4 Discussion of Design and Identified

PSPEC Requirements

Section 2.2 Sustainment Approach As defined below

Section 2.3 Delivery Schedule Attachment 4, 5 pages

Section 2.3.1 SOW Cross Reference Matrix

(CRM)

Attachment 3; no page limit.

These documents must not include substance of the proposed technical solution;

instead, it should be used to assist evaluators in locating portions of the proposed approach.

Section 2.3.2 Supportability 5

Section 2.3.3 Training Materials No page limit

Section 2.3.4 Technical Manuals No page limit

Section 2.3.5 Spares and Warranty Exhibit K no limit; 5 for remaining spares and warranty information

Section 2.3.6 Supply Chain Risk Management

(SCRM)

Section 2.3.7

Identification and Assertion of Restrictions on the Government's

Use, Release, or Disclosure of Technical Data or Computer

Software as required by DFARS 252.227-7017

Attachment 11, no page limit

Section 2.4 Exceptions, Deviations, Conditions, Assumptions, and Waivers

Section 2.5 Get Well Plan 15

III COST/PRICE As defined below

Section 3.1 Pricing Workbook Attachment 5; no page limit

Section 3.2 Model Contract- Signed SF 33 No page limit

Section 3.3

Equal Employment Opportunity (EEO) and Veterans’ Employment and Training Service (VETS) 4212 Pre-Award Clearance Information

No page limit

IV PAST PERFORMANCE As defined below

Section 4.1 Past Performance Summaries 2-page limit per effort referenced with a 6 page overall limitation.

V SUBCONTRACTING & SMALL

BUSINESS PARTICIPATION

As Defined Below

Section 5.1 Small Business Achievements and Subcontracting Record

Attachment 9; no page limit

Section 5.2 Small Business Participation and Commitment Strategy

Attachment 10; 13 page limit

Section 5.4 Small Business Subcontracting Plan No page limit

*In the event an offeror provides a proposal that is printed or copied double-sided on paper pursuant to FAR clause 52.204-4, each side of the paper shall be numbered and will represent one page.

L-1.4 INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT

L-1.4.1 VOLUME I: EXECUTIVE SUMMARY

L-1.4.1.1 Executive Summary:

L-1.4.1.1.1 Confirmation: Confirm that your company’s representations, certifications, acknowledgments, and statements have been completed electronically. (Note: Offerors must also comply with the System for Award Management requirements of FAR Clause 52.204-7).

L-1.4.1.1.2 Validity Period: Statement of the period for which the proposal is valid (must be not less than 180 calendar days from the closing date listed above).

L-1.4.1.1.3 Authorized Offeror Personnel: Provide the name, title, email address, and direct telephone number of the company/division point of contact for your proposal who is authorized to contractually bind, and negotiate on behalf of, your company.

Additionally, please provide an alternate point of contact (with the above listed contact information) who may be reached for general matters, or in the absence of the individual listed above.

L-1.4.1.1.4 Company and Codes: Include your company’s Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, county and facility code; Unique Entity Identifier (UEI); Commercial Activity and Government Entity code; Data Universal Numbering System code; Tax Identification Code (TIN); and size of business (large or small) under NAICS code 517410. Also provide contact information for your principal, to include the principal’s name, position title, and contact details. Provide the same information for the major subcontractors intended to work at any time during the contract period.

L-1.4.1.1.5 Agency POCs: Identify your company’s cognizant points of contact at the Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and the Defense Finance and Accounting Services (DFAS) payment office.

L-1.4.1.1.6 ISO 9001 certification date: Include your company’s latest ISO 9001 certification date.

L-1.4.2 VOLUME II: TECHNICAL APPROACH

The technical approach volume shall not include any pricing data.

L-1.4.2.1 System Performance:

The offeror shall provide a detailed description of the system design including a consolidated description of the hardware and software components proposed. The description shall include the specific make, model, and physical size of the proposed hardware, the hardware/software options proposed to be implemented, the software applications, and the operating systems. Information relating to the software shall include the manufacturer, version/release number, and other information that identifies all the exact software proposed.

The offeror’s proposal shall include a completed copy of the MCWS-L PSPEC Compliance Matrix for the Light variant (Attachment 1) and the MCWS-H PSPEC Compliance Matrix for the Heavy variant (Attachment 2). In populating the PSPEC Compliance Matrices, the offeror shall:

Under “Met,” indicate if the proposed system meets (Yes (Y) or No (N)) each requirement.

For any requirement that is not met at the time of proposal submission, the offeror shall provide, in Section 2.5, a description of the offeror’s “Get Well” plan, including the methods and technical approach to satisfying the requirement and whether the unmet requirement will degrade system performance.

Under “Proposed Capability,” include a capability associated with the requirement only if proposing a different system capability than is specified in the PSPEC requirement.

Offerors should understand that the Government intends to incorporate as a contract requirement any proposed capability that is more beneficial to the Government than the PSPEC requires; therefore, if an Offeror does not wish to be bound to provide the better capability, the Offeror should simply leave the Proposed Capability block blank and the PSPEC value will apply. Note that an offeror that does not propose a more beneficial capability in the PSPEC Compliance Matrix will not receive added consideration for that better capability as part of the source selection process.

Under “Substantiating Verification Data Reference,” include the location (Section 2.1.3 page and paragraph number) of the substantiating information demonstrating the verification of each requirement. In Section 2.1.3 of the proposal, the Offeror shall include supporting documents (such as independent test reports, analysis, data, or certifications) verifying the capability proposed. The Government reserves the right to limit its consideration of supporting documents that do not succinctly demonstrate verification of the claimed capability.

Under “Requirement Discussion Reference,” indicate the location (Section 2.1.4, page and paragraph) where the requirement is discussed. For each requirement with an asterisk in the PSPEC Paragraph column, the offeror shall explain, in Section 2.1.4 of Volume II, specifically how its system meets or exceeds the requirement or why, as appropriate, it does not. The offeror may elaborate requirements not marked with an asterisk, but is not required to do so and should not do so at the expense of providing a concise but complete explanation for the requirements identified for elaboration. Additionally, the offeror shall provide a clear Medium Earth Orbit (MEO) Capability Roadmap for meeting the MEO objective requirements listed in paragraphs 3.1.3, 3.1.12.6, and 3.1.12.7 of the MCWS-L PSPEC and in paragraphs 3.1.3, 3.1.14.6, and 3.1.14.7 of the MCWS-H PSPEC. These requirements are currently documented as objective requirements, but the implementation plan is required now as these capabilities are expected to become threshold requirements in the near future. The offeror’s implementation plan shall include a timeline in which this capability will be offered to the Government for operational use.

Under “Waiver Request Reference” indicate where the request and associated information is located (Section 2.4, page and paragraph) for any waiver being requested.

L-1.4.2.2 Delivery Schedule (Attachment 4): The offeror shall provide a Delivery Schedule in accordance with FAR Clause 52.211-9, Desired and Required Time of Delivery, using Attachment 4. The Delivery Schedule shall show deliveries in Days After Delivery Order Issuance (DADOI) for the Developmental Test Assets, production MCWS L/H Systems, and spare parts. The offeror shall describe its manufacturing approach and capabilities to support its proposed delivery schedule. The offeror shall identify any surge or ramp-up capabilities in the Delivery Schedule that could affect production lead time.

L-1.4.2.3 Sustainment Approach:

L-1.4.2.3.1 Attachment 3, SOW CRM: Offerors shall complete the SOW CRM, at Section 2.3.1, mapping the listed SOW requirements to the proposal location (Volume, Section, Page, and Paragraph) where the requirement is referenced. Offerors shall not use the SOW CRM to provide substance regarding the proposed solution or attempt in any manner to increase the volume of information permitted by the page limitations.

L-1A.4.2.3.2 Supportability: The offeror shall provide, at Section 2.3.2, a proposed system sustainment approach that supports the Marine Corps sustainment and maintenance concept of enabling Marines to maintain, test, diagnose, and repair the system using Government personnel and equipment in the field.

L-1.4.2.3.3 Training Materials: The offeror shall provide, at Section 2.3.3 of the proposal, its existing system training materials–such as instructor guides, student materials, and supporting media–that would be used to provide Marines with a thorough knowledge and understanding of MCWS-L/H system set up and tear down, storage, operation, preventive maintenance, corrective maintenance (if possible), troubleshooting procedures, and safety information, as outlined in SOW paragraph 4.14.

L-1.4.2.3.4 Technical Manual: The offeror shall provide, at Section 2.3.4 of the proposal, the manuals to be delivered under a resulting contract, including the operation and maintenance manuals. The manuals shall provide Marines with a thorough knowledge and understanding of the MCWS-L/H system and include instructions for set up and tear down of the system, operation and maintenance, troubleshooting guides, and safety information as outlined in SOW paragraph 4.13.17. In accordance with DFARS Clause 252.227-7017, the offeror shall provide any assertion of restrictions for commercial or non-commercial data provided. The Government reserves the right to limit its consideration of technical manuals that do not succinctly address the required topics.

L-1.4.2.3.5 Spares and Warranty: The offeror shall provide, at Section 2.3.5 of the proposal, supportability data to include reliability, availability, and maintainability (RAM) analysis of each proposed MCWS-L/H system variant, and their Lowest Replaceable Units (LRUs), as outlined in SOW paragraph 4.13.13.

The offeror shall submit, as Exhibit K, a full list of spare parts and prices for each MCWS variant (Light and Heavy), noting the recommended number of spares sufficient to support one system of each variant for 2 years of operations, in accordance with SOW Section 4.13.9. Section 2.3.5 of the proposal shall provide the supporting analysis for the spare parts recommendations.

The offeror shall provide the details of the warranties that will apply to the items delivered under a resulting contract, including the parts covered, coverage terms and conditions, coverage periods, and exclusions for any parts and for the system as a whole.

The submissions shall include warranty terms that are consistent with the previous warranties it has provided in the defense marketplace for all systems and components procured on prior defense contracts. These warranty terms will be incorporated by reference into the contract upon final award.

The contractor shall propose a Return Material Authorization (RMA) and Warranted Item replacement approach that includes RMA processing time, help desk support, and Turn Around Time (TAT) for all items under warranty.

L-1.4.2.3.6 SCRM : The offeror shall describe, at Section 2.3.6, the SCRM methods and procedures it will use to secure mission critical microelectronics and software supply chains of hardware and software components and parts, as described in SOW Section

4.8.9. The contractor shall describe:

A. The contractor’s approach to SCRM, how critical components are tracked to the original equipment manufacturers, and how other parts suppliers and vendors are vetted throughout the product/system life cycle.

B. The factors the offeror will use in assessing critical component supply chain risk, the methodology the offeror will use to determine risk, and the risk mitigation practices the offeror will apply.

C. The locations of the manufacturing facilities where the hardware and software are designed, manufactured, packaged, and stored prior to distribution.

D. Any Foreign Ownership, Control, or Influence (FOCI) that impacts this contract or its subcontracts and identify how the contractor will protect and segregate US Government information and technology from any FOCI relationships or concerns.

L-1.4.2.3.7 Attachment 11, Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or Computer Software as required by DFARS 252.227-7017. Offerors must complete and submit Attachment 11, Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or Computer Software as required by DFARS 252.227- 7017.

L-1.4.2.4 Exceptions, Deviations, Conditions, Assumptions, and Waivers: Section 2.4 shall contain all exceptions, deviations, conditions, assumptions, and waiver requests that the offeror submits with respect to the provisions of the RFP and its applicable documents. An exception is an offeror statement that it will not comply with a requirement, usually involving contract terms and conditions. A deviation is an offeror statement 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. A waiver is where an offeror requests authorization for the Government to accept performance, or an item, that will depart from specified requirements, but would nevertheless be considered suitable. Objective requirements listed in the PSPECs (Attachments 6 and 7) do not need a waiver if they are not met.

If the offeror submits a proposal including any of the preceding features, the offeror shall provide a description of each exception, deviation, condition, assumption, or request for waiver. The offeror must indicate the relevant provision or requirement, describe offeror's difficulty with the applicable requirement, and describe the offeror's proposed solution, where applicable. Each Request for Waiver should be clear in identifying the extent of waiver required, any substitute performance proposed, and the offeror’s ability to perform and meet requirements if the requested waiver is not granted.

In submitting an exception, deviation, condition, assumption, or waiver, the offeror should make no assumption about the willingness of the Government to accede to the request to grant the exception, deviation, or waiver, or to accept the offeror’s condition or assumption. The inclusion of any exception, deviation, condition, assumption, or waiver may render a proposal unawardable if the Government, in its sole discretion, determines that said exception, deviation, condition, assumption, or waiver, or the proposed solution thereof, presents an unacceptable risk to contract performance.

L-1.4.2.5 Get Well Plan The offeror shall submit a get well plan for those requirements which are currently not met, but the offeror has a plan to meet in the future. The get well plan should include the requirement not met, the offeror’s plan to meet it, and the timeline which it will take to meet the requirement. The test data for any “Get-Well Plan” will be considered during the evaluation process. The Government reserves the right to halt its review of data if it is deemed excessive, unreliable, incomplete, inconclusive, or otherwise of too little value to be efficiently and effectively considered during proposal evaluation.

L-1.4.3 VOLUME III: COST/PRICE

The pricing volume shall include all pricing information for the entire proposal. No pricing information shall be included in other volumes except Volume V – Subcontracting & Small Business Participation. As this is a competitive acquisition with adequate price competition anticipated, the Government does not request certified cost or pricing data as described in FAR

15.403. However, in the event that adequate price competition does not exist under this effort after the receipt of proposals, the Government may request additional cost or pricing data as necessary from the offeror, any of its subcontractors, and its team members, pursuant to FAR 15.403-4.

L.1.4.3.1 Attachment 5 - Pricing Workbook.

Pricing shall be submitted on the provided spreadsheet, Attachment 5 – Pricing Workbook, with formulas intact.

Offerors may propose alternate quantity discounts for all CLINs as shown in Attachment 5 – Pricing Workbook. If quantity discounts are proposed, the offeror shall reference the CLIN number, quantity range(s), and price(s) proposed.

CLINs X010, MEO ECP, represent the price for the development required to incorporate the MCWS-L PSPEC requirements described in 3.1.3, 3.1.12.6, and 3.1.12.7 and the MCWS-H PSPEC requirements described in 3.1.3, 3.1.14.6, and 3.1.14.7 into the offeror’s proposed solution. CLINs X011, MEO Upgrade – MCWS-L, represent the per unit price of upgrading the MCWS-L systems to meet the MCWS-L PSPEC requirements described in 3.1.3, 3.1.12.6, and

3.1.12.7. CLINs X012, MEO Upgrade – MCWS-H, represent the per unit price of upgrading the MCWS-H systems to meet the MCWS-H PSPEC requirements described in 3.1.3, 3.1.14.6, and 3.1.14.7.

Offerors proposing a solution that meets the MCWS-L PSPEC requirements described in 3.1.3, 3.1.12.6, and 3.1.12.7 and the MCWS-H PSPEC requirements described in 3.1.3, 3.1.14.6, and

3.1.14.7 at the time of proposal submission shall include the price of meeting those MEO requirements in the unit price of the systems at CLINs X001, CLINs X002, CLINs X018, and

CLINs X019 for all ordering periods. Offerors proposing such a solution shall propose a price of N/A for CLINs X010, MEO ECP; CLINs X011, MEO Upgrade – MCWS-L; and CLINs X012, MEO Upgrade MCWS-H.

Offerors who do not propose a solution that meets the MCWS-L and MCWS-H PSPEC MEO requirements outlined above at the time of proposal submission shall propose a price for CLIN X010, MEO ECP, for the development required to incorporate the outlined MEO capabilities as an ECP; for CLIN X011, MEO Upgrade – MCWS-L, to upgrade MCWS-L systems; and X012, MEO Upgrade – MCWS-H to upgrade MCWS-H systems. CLINs X010, X011, and X012 shall be proposed in the ordering period in which the offeror is capable of incorporating the PSPEC MEO requirements outlined above into their solution. Offerors shall only propose a CLIN X010 price in one ordering period, for the development required to incorporate the outlined MEO capabilities into the solution, and shall use “N/A” in pricing CLIN X010 for all prior and successive ordering periods. Offerors shall propose a price for CLIN X011, MEO Upgrade – MCWS-L, and X012, MEO Upgrade – MCWS-H, first in the same ordering period in which the offeror proposes a price for CLIN X010, MEO ECP, and then in all ordering periods to follow.

For example, if an offeror is proposing to incorporate the specified MEO capabilities through an ECP in Ordering Period 2, the offeror would not propose a price for CLIN X010, MEO ECP;

CLIN X011, MEO Upgrade – MCWS-L; or CLIN X012, MEO Upgrade – MCWS-H in Ordering Period 1, but would propose a price for all three of those CLINs in Ordering Period 2.

Additionally, the offeror would propose a price for CLIN X011, MEO Upgrade – MCWS-L, and CLIN X012, MEO Upgrade – MCWS-H, for all subsequent Ordering Periods, and shall use “N/A” in pricing CLIN X011 and CLIN X012 for all prior periods. See sample below:

Table L-3: Sample Proposed Pricing

OP1 OP2 OP3 OP4 OP5

CLIN X010 – MEO ECP N/A Price N/A N/A N/A

CLIN X011 – MEO

Upgrade – MCWS-L

N/A Price Price Price Price

CLIN X012 – MEO

Upgrade – MCWS-H

N/A Price Price Price Price

L-1.4.3.2 Model Contract:

The offeror's proposal shall include the model contract, including a completed copy of SF 33 and acknowledgment of any solicitation amendments (SF 30), each signed by a person authorized to enter into the proposed contract on behalf of the offeror. In addition, offerors shall complete and include all RFP Provisions and Clauses that require completion by the offeror.

L-1.4.3.3 EEO and VETS 4212 Pre-Award Clearance Information:

L-1.4.3.3.1 Clearance Information: To expedite the Government’s EEO pre-award clearance request process, the prime contractor 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, with direct telephone number, and UEI. The Government plans to request EEO clearances early in the evaluation process to avoid possible delays in making contract award (page limit not applicable).

L-1.4.3.3.2 Confirmation of Receipt: In addition, offerors shall submit a copy of the confirmation of receipt notification (e-mail) for verification of successful submission of VETS 4212 report for the prime contractor and any subcontractor with a proposed subcontract value estimated at $100,000 or more. If a contractor, for any reason, cannot produce a confirmation notification, then they may contact the VETS 4212 Service Center to request a verification search to be performed.

Phone: (866) 237-0275 Email: VETS4212-customersupport@dolnnc.dol.gov

Please note that to perform a verification search, the VETS 4212 Service Center will need one, or a combination of, the following information. Having all of the requested data elements will provide for a more detailed search.

- Company Name

- Company Address

- Employer Identification Number (EIN)

- UEI

L-1.4.4 VOLUME IV: PAST PERFORMANCE

At Section 4.1 of the proposal, the offeror (e.g. as the Prime contractor only or the Prime and proposed subcontractors/major subcontractors) shall submit up to three recent contracts or orders, performed by the offeror as a prime contractor, that are relevant to this solicitation’s requirements. To qualify as recent, a contract must have 12 months of performance occurring during the 36-month period preceding the proposal submission deadline. Government contracts shall be used as past performance summaries before non-Government contracts. Provide information for any and all of the offeror’s contracts with federal agencies, whether or not similar to the proposed effort, which were terminated, in whole or in part, for any reason during the past 3 years. Include all efforts where the prime or proposed subcontractors have received notice of the Government’s intent to terminate, whether or not the contract ended in a termination action. (These termination submissions will be excluded from the page count.)

L-1.4.4.1 Each past performance summary shall be limited to two pages and shall include:

A. Section 1 – Contract Description:

1) Contract number, order number if applicable, CAGE code, UEI, and North

American Industry Classification System (NAICS) code;

2) Government contracting activity, Contracting Officer’s name, telephone number, and email address;

3) Government Contracting Officer’s Representative’s (COR) and/or technical representative’s name, telephone number, and email address;

4) Government contract administration activity, Administrative Contracting Officer’s (ACO) name, telephone number, and email address (if applicable);

5) In addition to the contact information required in 1 through 4 above, provide:

(a) Contract type

(b) Awarded price/cost

(c) Final (actual) or projected final (if ongoing) price/cost

(d) Final (actual) or projected final (if ongoing) start and end dates of the contract’s period of performance

(e) Percentage of effort, based on the total cost of the work required in the referenced contract or order, performed by the offeror as prime contractor as of the time of this effort’s proposal submission

(f) Description of the specific tasks or activities performed by the offeror itself under the contract

B. Section 2 - Narrative:

1) Offeror’s description of the effort, highlighting similarities and differences between the reported and solicited efforts, particularly with respect to scope, magnitude and complexity. Offerors should pay particular attention to the type of equipment being procured and this solicitation’s SOW, providing sufficient detail in the description to readily allow for a comparison of the effort’s supplies and scope to that of the solicited effort.

C. Section 3 - Contract Performance:

1) For any contracts that failed to meet technical performance requirements, provide a brief explanation of the reasons for the shortcomings, any corrective actions taken to avoid recurrence, and the effectiveness of those actions in addressing the problem(s).

2) The offeror shall also provide a copy of any Cure Notices or Show Cause Letters they received for any contract listed and a description of any corresponding corrective action implemented by the offeror. (Note: Cure Notices, Show Cause Letters, and associated explanations are excluded from the page count).

3) Offerors should not attempt to describe the quality of their work as they are deemed inherently biased and will be of little use to evaluators.

4) The offeror shall provide the CPAR(s) for the portion(s) of the cited contract or order that meet the recency definition. Beyond the CPAR and the information identified in c)1) or c)2), offerors should not provide descriptions of the quality of their work as they are deemed inherently biased and will be of little use to evaluators. CPARS are excluded from the page count limitations

Offerors are reminded that while the Government may elect to consider data obtained from other sources, it is not obligated to do so as the burden of providing thorough and complete past performance information rests solely with the offeror.

L-1.4.5 VOLUME V – SUBCONTRACTING AND SMALL BUSINESS PARTICIPATION

Both Large and Small Businesses shall provide this Volume in order for the Government to assess both the offeror’s historical achievements in using small business concerns as subcontractors and its proposed small business participation and commitment strategies.

L-1.4.5.1 Small Business Achievements and Small Business Subcontracting Record

At Section 5.1 of the proposal offerors shall provide a narrative to describe their achievements in supporting the Government’s policy to provide maximum practicable opportunities for small businesses (SB), veteran-owned small businesses (VOSB), service-disabled veteran-owned small businesses (SDVOSB), historically underutilized business zone (HUBZone) small businesses, small disadvantaged businesses (SDB), and women-owned small businesses (WOSB) to participate as subcontractors, consistent with efficient contract performance.

A. All offerors shall submit small business subcontracting information associated with each project included as an example of past performance, if those efforts required a subcontracting plan. Information shall be submitted in the format provided in Attachment 9, Small Business Subcontracting Record.

1) Offerors representing as other than small businesses shall also provide copies of the most current Individual Subcontracting Reports (ISRs) associated with each project cited under the Past Performance Factor if a small business subcontracting plan was required by the contract. If such projects were completed under specific task orders, provide ISRs for the overall contract. For cited projects with state and local Government agencies, provide similar subcontracting performance reports, if they were required by the contracts. When not specifically addressed in the ISR or similar report, offerors shall provide explanations for all instances of failures to meet dollar or percentage goals as expressed in the individual subcontracting plans. Corporate Subcontracting Reports will be accepted in lieu of ISRs if the efforts are recent and relevant.

B. Notes:

1) The Government reserves the right to consider achievements information on other recent, relevant projects from all available sources.

2) Offerors utilizing achievements information of team members or key subcontractors shall clearly demonstrate how these companies will have meaningful involvement in the “management” of the subcontracting program for this acquisition. Without adequate demonstration of meaningful management involvement, such achievement information will not be considered. If the offeror is a new joint venture, partnership, or other entity consisting of more than one company, provide achievements information for each individual business entity that will be responsible for managing the subcontracting program and clearly describe those management responsibilities.

3) Failure to provide ISRs or any other requested information must be fully explained and its absence may negatively impact the offeror’s evaluation.

L-1.4.5.2 Small Business Participation and Commitment Strategy (Attachment 10)

A. All offerors shall submit, at Section 5.2, a Small Business Participation and Commitment

Strategy including all data elements shown in Attachment 10, Small Business Participation and Commitment Strategy.

1) Identify, in terms of dollar value and percentage of the total acquisition, the extent of work the offeror will self-perform as the prime contractor. If submitting an offer as a joint venture, identify the percentage of work each member will be responsible for and indicate the size status of each member (e.g. small business, woman-owned small business, other than small business).

2) Include supplemental narratives (limited to 5 pages) addressing other elements of the offeror’s strategy, such as binding agreements covering post award roles for execution of the contract and specific initiatives and tools that will be employed under the contract to enhance small businesses opportunities including utilization of SBIR products to both participate in this acquisition and build capabilities to support future Marine Corps Systems Command (MCSC) acquisitions.

3) The anticipated prime and first tier overall small business participation rate for this acquisition (i.e., work to be performed by small businesses as the prime and/or subcontractors) is 1% - 5% of the contract value, at a minimum. Offerors are encouraged to exceed this percentage and seek meaningful levels of participation in each of the small business socioeconomic programs listed in Attachment 10, consistent with efficient contract performance. Offerors shall explain in their participation and commitment strategies how proposed participation rates were established. The small business participation and commitment strategy must be in agreement with any required small business subcontracting plan at time of award and will be made a part of the contract upon award.

L-1.4.5.3 Small Business Subcontracting Plan (OTHER THAN SMALL BUSINESSES

ONLY) The Small Business Subcontracting Plan is only required from Other than Small Businesses and will be incorporated into any resultant contract. FAR 52.219-9 sets forth the Small Business Subcontracting Plan’s required elements.

(End of Summary of Changes)