M67854-20-R-2025-0003.docx

M6785420R2025

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The DPAS code DO-A7 has been added.

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0002

The CLIN description has changed from Initial Issue Provisioning (IIP) Kit to RESERVED.

The CLIN extended description has changed from:

IAW SOW Section 3.2 and P-Spec. Ordering Period 1.

To:

The pricing detail quantity has decreased by 432.00 from 432.00 to 0.00.

The PSC code D304 has been deleted.

The PROG code A70 has been deleted.

The NAICS code 517919 has been deleted.

CLIN 1002

The CLIN description has changed from Initial Issue Provisioning Kit to RESERVED.

IAW SOW Section 3.2 and P-Spec. Ordering Period 2.

The PSC code D304 has been deleted.

CLIN 2002

IAW SOW Section 3.2 and P-Spec. Ordering Period 3.

The PSC code D304 has been deleted.

CLIN 3002

IAW SOW Section 3.2 and P-Spec. Ordering Period 4.

The PSC code D304 has been deleted.

CLIN 4002

IAW SOW Section 3.2 and P-Spec. Ordering Period 5.

The PSC code D304 has been deleted.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

STATEMENT OF WORK

1. SCOPE OF WORK

This Statement of Work (SOW) defines the efforts required for the delivery of the Marine Corps Wideband Satellite – Expeditionary (MCWS-X) satellite terminals, spare parts, provisioning data, commercial technical manual(s), and training materials.

1.1. Background

MCWS-X is a man-packable, multiband (X, Ku, Ka) Super High Frequency (SHF), multi-waveform satellite communications (SATCOM) terminal capable of being transported by one Marine, and being set-up by that Marine in under 15 minutes. The MCWS-X provides throughput rates up to at least 2 Megabits per second (Mbps) and, objectively, up to 10 Mbps, and utilizes waveforms that are backward compatible with legacy Marine Corps Satellite Communications (SATCOM) systems and Department of Defense (DoD) Enterprise SATCOM Gateways, and forward compatible with future upgrades planned to implement the Protected Tactical Waveform (PTW).

2. APPLICABLE DOCUMENTS

The following documents specified form a part of this SOW to the extent specified herein. The most recent revision of the referenced document at the time of contract award shall be used unless otherwise specified. In the event of conflict between the applicable documents and this SOW, the SOW shall take precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

2.1 Government Documents

The following specifications, standards, and handbooks form a part of this document to the extent specified herein and are contained in the table below. Copies of the documents should be obtained from the ASSIST database at http://quicksearch.dla.mil/. ASSIST is the official source for all Defense Standardization Program documents and contains the most current information. An ASSIST Update (a bi-monthly summary of changes to the ASSIST document database) may be viewed or downloaded at Uniform Resource Locator (URL): https://quicksearch.dla.mil/qsSearch.aspx.

Requests for copies of Occupational Safety and Health Agency (OSHA) references should be addressed to the Department of Labor, OSHA, Washington, DC 20210. Requests for copies of National Security Agency (NSA) references should be addressed to National Security Telecommunications and Information Systems Security Committee (NSTISSC) Secretariat (V503), NSA, 9800 Savage Road STE 6716, Fort Meade, MD 20755-6716. Request for copies of MCWS-X documentation should be addressed to Marine Corps Systems Command, 2200 Lester St., Quantico, VA 22134, ATTN: PM Communications Systems.

*NOTE: If a newer version exists at the time of contract award, that version will apply instead.

2.2 Non-Government Documents – Information

3. REQUIREMENTS

The contractor shall perform all tasks required by, and delineated in, this SOW to manufacture and deliver the MCWS-X systems as well as to prepare associated documentation. The contractor shall deliver all materials, equipment, hard tooling, personnel, and facilities necessary to perform the tasks listed in this SOW, and to deliver the types and quantities of deliverables specified by the contract.

The contractor shall deliver all Contract Data Requirements Lists (CDRLs) in accordance with each DD Form 1423 and the CDRL Submission Instructions. Deliverables are referenced by name and reference number after the paragraph containing the requirement for that deliverable.

3.1 MCWS-X System

The contractor shall deliver complete integrated MCWS-X systems in accordance with the performance specifications at Attachment 1.

3.2 MCWS-X Spares

3.2.1 MCWS-X Initial Issue Provisioning

The contractor shall deliver spare Lowest Replaceable Units (LRUs), expendables, and consumables to form Initial Issue Provisioning (IIP) Kits sufficient to support each system for 2 years.

3.2.1 MCWS-X Spares List

The contractor shall deliver spare LRUs, expendables, and consumables in accordance with Exhibit K.

3.3 Program and Data Management

3.3.1 Travel

The contractor shall be responsible for all travel costs for its own personnel for all travel associated with the execution of this SOW. Travel costs will not be reimbursed by the Government.

3.3.2 Security Requirements

The information provided to the contractor will be unclassified and/or Controlled Unclassified Information (CUI). The contractor is not required or expected to have a Facility Clearance and contractor personnel supporting this effort are not required to possess Personnel Clearance Levels. However, any contractor personnel requiring access to U.S. Government CUI shall possess a completed background investigation (minimum of a T-1/NACI) for this Public Trust Position.

3.3.3 System Security Plan and Plans of Action and Milestones (SSP/POAM) Reviews Within 30 days of contract award, the contractor shall deliver its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) for review by the Government in electronic format. The SSP(s) shall implement the security requirements in Department of Defense (DoD) Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The contractor shall fully cooperate in the Government’s review of the SSPs.

If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012, the Government shall notify the contractor of each identified deficiency. The contractor shall correct any identified deficiencies within 30 days of notification by the Government. The contracting officer may provide for a correction period longer than 30 days and, in such a case, may require the contractor to submit a plan of action and milestones (POAM) for the correction of the identified deficiencies. The contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a POAM.

Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s), remotely or at the contractor’s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the contractor has corrected all identified deficiencies in the SSP(s).

The Government may, at its sole discretion, conduct subsequent reviews at the contractor’s site to verify the information in the SSP(s). The Government will conduct such reviews at least every 3 years (measured from the date of contract award) and may conduct such reviews at any time upon 30 days’ notice to the contractor.

(CDRL A001 – System Security Plan (SSP) and Associated Plans of Action for a Contractor’s Internal Unclassified Information System)

3.3.4 Compliance to National Institute of Standards and Technology (NIST) SP 800-171 The contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), and establish a SSP(s) indicating compliance with associated POAMs that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

Notwithstanding the allowance for such variation, the contractor shall identify, in the SSP and POAM, their plans to implement the following, at a minimum:

· Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted;

· Control 3.1.5 (least privilege) and associated Controls, and identify practices that the contractor implements to restrict the unnecessary sharing, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles;

· Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

· Privilege Auditing. Audit user privileges on at least an annual basis;

· Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls, as documented in a SSP and POAM); and,

· NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program);

· Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POAM for implementation, which shall be evaluated by the Navy for risk acceptance.

· Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

3.3.5 Cyber Incident Response:

The contractor shall, within 15 days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the contractor determines is impacted by the incident and begin assessment of potential warfighter/program impact.

Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media, available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Media.docx. In delivery of the incident data, the contractor shall, to the extent practical, remove contractor-owned information from Government covered defense information.

If the contractor subsequently identifies any such data not previously delivered to DC3, then the contractor shall immediately notify the contracting officer in writing and shall deliver the incident data within 10 days of identification. In such a case, the contractor may request a delivery date later than 10 days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

(CDRL A002 – Cyber Incident Reporting for a Contractor’s Internal Unclassified Information System)

3.3.6 Naval Criminal Investigative Service (NCIS) Outreach

The contractor shall engage with NCIS industry outreach efforts and consider recommendations for hardening of covered contractor information systems affecting Department of the Navy (DON) programs and technologies.

3.3.7 NCIS/Industry Monitoring

In the event of a cyber incident or at any time the Government has indication of a vulnerability or potential vulnerability, the contractor shall cooperate with the Naval Criminal Investigative Service (NCIS), which may include cooperation related to: threat indicators; pre-determined incident information derived from the contractor's infrastructure systems; and the continuous provision of all contractor, subcontractor or vendor logs that show network activity, including any additional logs the contractor, subcontractor or vendor agrees to initiate as a result of the cyber incident or notice of actual or potential vulnerability.

If the Government determines that the collection of all logs does not adequately protect its interests, the contractor and NCIS will work together to implement additional measures, which may include allowing the installation of an appropriate network device that is owned and maintained by NCIS, on the contractor's information systems or information technology assets. The specific details (e.g., type of device, type of data gathered, monitoring period) regarding the installation of an NCIS network device shall be the subject of a separate agreement negotiated between NCIS and the contractor. In the alternative, the contractor may install network sensor capabilities or a network monitoring service, either of which must be reviewed for acceptability by NCIS. Use of this alternative approach shall also be the subject of a separate agreement negotiated between NCIS and the contractor.

In all cases, the collection or provision of data and any activities associated with this statement of work shall be in accordance with federal, state, and non-US law.

3.3.8 Contractor’s Record of Tier 1 Level Suppliers who Receive or Develop Covered Defense Information The contractor shall supply record of Tier 1 Level Suppliers who receive or develop Covered Defense Information. The contractor shall deliver its plan to track flow down of covered defense information and to assess DFARS Clause 252.204-7012 compliance of known Tier 1 Level suppliers.

(CDRL A003 – Contractor's Record of Tier 1 Level Suppliers Receiving/Developing Covered Defense Information)

3.3.9 Radio Frequency Spectrum Compatibility

Per the Equipment Location – Certification Information Database (EL-CID) process, the contractor shall complete and deliver the EL-CID Cut Sheet Template provided for obtaining an approved frequency for the MCWS-X system.

(CDRL A004, Technical Report – Study/Services (Applications for Equipment Frequency Allocation)

3.3.10 Logistics Product Data

The contractor shall develop and deliver a Provisioning Parts List (PPL). The contractor shall ensure that the PPL contains the end item; components or assemblies; and all support items that can be disassembled, reassembled, or replaced. The PPL shall include all support items which, when combined, constitute the end item, component, or assembly. The PPL shall include items such as parts, materials, consumables, connecting cabling, mounting, and fittings required for the operation and maintenance of the end item, component, or assembly. The PPL shall be used to indicate the range and depth of support items required to maintain the end item. The PPL shall include all repairable and non-repairable Commercial Off-the-Shelf (COTS) items. The PPL shall be structured in a Top-Down Breakdown sequence. Indenture Codes shall be in Alpha Character format. Provisioning List Item Sequence Number (PLISN) sequencing of the PPL shall begin with Alphanumeric Codes of A001 as the first “B” indenture PLISN, continue through A999, then B00l, and continue through B999. All repairable items will be identified by the contractor. The PPL shall contain repair kits and repair part sets required to maintain the end item, component, or assembly.

(CDRL C001, Logistics Product Data)

3.3.11 Commercial Technical Manuals

The contractor shall deliver commercial manuals sufficient to provide Marines with a thorough knowledge and understanding of MCWS-X system set up and tear down, storage, operation, preventive maintenance, corrective maintenance (if possible), troubleshooting, and safety information. Note the requirements of DFARS 252.227-7013(d), regarding requirements for third party copyrighted works provided as part of the deliverables.

(CDRL E001, Commercial Technical Manual)

3.3.12 Training Instruction

The contractor shall deliver commercial training materials sufficient to provide Marines with a thorough knowledge and understanding of MCWS-X system set up and tear down, storage, operation, preventive maintenance, corrective maintenance (if possible), troubleshooting procedures, and safety information.

(CDRL F001, Training Data Products)

3.3.14 Commercial Warranty

Warranty coverage will clearly identify limitations, exclusions, and restrictions upon the intended military application, use and environmental stress that may be imposed by the tactical employment of the equipment, systems or items being acquired. The contractor shall ensure that subcontractor and/or contractor warranties provide the same coverage for all end items.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

ATTACHMENTS AND EXHIBITS

26 pages

30 April 2020

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

INSTRUCTIONS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

INSTRUCTIONS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

L-1.0 INSTRUCTIONS FOR THE SUBMISSION OF PROPOSALS

L-1.1 INTRODUCTION

The Government intends to meet this requirement by selecting a contractor for a single award Indefinite Delivery Indefinite Quantity (IDIQ) contract, consisting of five 1-year ordering periods, using a firm-fixed-price Contract Line Item Number (CLIN) structure.

L-1.2 GENERAL

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 the solicitation.

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 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.

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 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.

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

Proposals shall be delivered to the location listed below by 1000 am Local Time on June 12, 2020. Any proposal received after such time and date will be considered a late submission. Late submissions will be treated in accordance with FAR Clause 52.215-1(c)(3). Facsimile or e-mail 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 containers used for delivery of proposals with the following:

“SOLICITATION M67854-20-R-2025”

Proposals shall be either hand delivered or mailed to the appropriate address listed below. Regardless of method of delivery, proposals must be received by the due date listed above. Hand carried proposals should not be delivered to the security desk.

NOTE: The building at 105 Tech Parkway in Stafford is secure, so Offerors are instructed to contact Ms. Stasia Baker at 703-432-8726 when arriving at the building. The individual delivering the proposal will be met in the lobby.

The Offeror shall also submit an electronic copy, via Department of Defense (DoD) Secure Access File Exchange (SAFE), accessible at https://safe.apps.mil. The Offeror shall email lisa.bennett@usmc.mil requesting a drop off be created and provide a name and email for the POC that should receive the drop off request. An automated email will be sent notifying the POC the drop off is open along with the required verification code. The drop off is valid for 14 days upon creation. Directions on how to execute the drop off once the POC has received the request can be found in the DoD SAFE User Guide published at https://safe.apps.mil.

INTENT TO INCORPORATE CONTRACTOR’S PROPOSAL

All or part of the successful Offeror’s proposal may be incorporated in any contract resulting from this solicitation. Nothing contained in the successful Offeror’s proposal shall constitute a waiver to any requirement of the contract. 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 QUESTIONS

Questions regarding the solicitation documents are due by 1200 local time on May 18, 2020 and must be submitted via e-mail to stasia.baker@usmc.mil and lisa.bennett@usmc.mil in the format specified in Table 1. Please do not bundle multiple questions into one. Questions received after the above time and date may not be answered. Government responses will be posted on Contract Opportunities website.

Table 1: Question Format

General Issue

Solicitation

Performance Spec

Other

L-2.0 PREPARATION OF PROPOSALS

L-2.1 FORMAT OF PROPOSAL

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 may 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 proposal in MS Office 2010 or later format. The price breakdown shall include MS Excel spreadsheets with formulas intact. In the event that there is a conflict between the printed copy of the proposal and the electronic copy of the proposal, the electronic copy will take precedence.

Electronic file naming convention: Please name all files submitted electronically as follows: company-document title.xxx; where xxx is the file type (i.e. .xls or .doc).

Binders: Each printed proposal volume shall be included in three-ring binders. Individual sections should be removable from and replaceable to the volumes. Each volume shall contain a title page, table of contents, and list of tables and figures for that volume. Include a SOW Cross Reference Matrix (Attachment 7) showing the location where the evaluator should look in that volume for a discussion of a particular solicitation requirement (excluding price information). Use tab separators to separate required sections within a volume and to separate volumes within a binder; tab separators will not count against volume page limits. Number all pages (other than dividers) sequentially. Only material addressing a specific proposal section shall be included in that section. That is, Offerors must not use one section of a proposal to address another section of the proposal. Submissions deemed to have attempted to circumvent the page limits in this, or any other, manner may result in the proposal being rejected.

Copies: The Offeror shall submit one set of binders containing a paper copy of Volumes I - IV, as listed below in Table 2. Additionally, the Offeror shall submit one binder with a paper copy of Volume V, as listed below in Table 2. The Offeror shall also submit an electronic copy, via Department of Defense (DoD) Secure Access File Exchange (SAFE), accessible at https://safe.apps.mil.

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

L-2.2 ORGANIZATION OF THE PROPOSAL

A legible, neat, orderly, well-organized, well-written, and comprehensive proposal is required. Elaborate brochures or artwork, expensive paper or bindings, or expensive visual or presentation aids are neither necessary nor desirable; the Government requests Offerors simply present a complete and comprehensive proposal. 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, below. Organization, clarity, accuracy, relevance, and completeness are of prime importance.

Table 2: Proposal Organization

As defined below

L-2.3 INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT

L-2.3.1 Volume I: Executive Summary

Executive Summary: This section shall include a brief summary of the Offeror’s 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).

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 obligate your company contractually.

Company and Codes: Include Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, county and facility code; Commercial Activity and Government Entity (CAGE) code; Data Universal Numbering System (DUNS) code; Tax Identification Code (TIN); and size of business (large or small). Also provide Company Point of Contact (POC) to include Principal(s) name, position title, and contact details.

· Attachment 7 - SOW Cross Reference Matrix: This section shall indicate the page and paragraph number(s) within the Technical Volume where an evaluator will find the detailed discussion of a particular requirement outlined in the Statement of Work (SOW). Offerors shall create a SOW Cross Reference Matrix which maps each SOW requirement addressed to the proposal location (Volume, Section, Page and Paragraph) where the requirement is discussed. Offerors shall not use the SOW 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.

L-2.3.2 Volume II: Exceptions, Deviations, Conditions, Assumptions, and Waivers

Volume II shall contain all exceptions, deviations, conditions, assumptions and waiver requests that the Offeror takes with respect to the provisions of the Request for Proposal (RFP) 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. 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. Any requirements annotated in Attachment 1, the Performance Specification, as objective requirements 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. Indicate the Offeror's difficulty with the applicable requirement and the Offeror's proposed solution, where applicable. Specifically identify the portions of the RFP and the Offeror's proposal that are affected. 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.

Note: Waiver requests should not be submitted for those requirements designated as key as the failure will be deemed a deficiency, rendering the proposal unawardable.

L-2.3.3 Volume III: Technical Approach

System Performance

The Offeror shall propose a system that satisfies the requirements specified in Attachment 1, Performance Specification. The offeror shall provide a brief narrative that supplements the completed Attachment 2 – P-Spec Compliance Matrix, detailing the proposed system’s capabilities and ability to meet the P-Spec requirements, and addresses SOW requirements, as required.

The Offeror shall include in its proposal a completed copy of Attachment 2, P-Spec Compliance Matrix. The matrix identifies each P-Spec requirement and includes a space for the Offeror to identify whether its proposed MCWS-X system meets or exceeds the requirement and notes the proposed capability. Offerors should understand that the Government intends to include any proposed capability that exceeds the specification as a contract requirement; therefore, if an Offeror does not wish to be bound to provide the greater capability, the Offeror should simply propose the specified value instead. The Offeror shall include supporting documents (such as independent test reports, analysis, data, or certifications) verifying the capability proposed. Additionally, the Offeror shall identify the page and paragraph numbers where the verification can be located in the supporting documents. The Government reserves the right to limit its consideration of supporting documents that do not succinctly demonstrate verification of the claimed capability. Within the P-Spec Compliance Matrix the Offeror shall identify all P-Spec requirements that are not met and for threshold requirements, reference (page and paragraph number) the appropriate Request for Waiver in Volume II.

The technical volume shall not include any cost/pricing data.

Delivery Schedule

The Offeror shall provide a Delivery Schedule in accordance with FAR Clause 52.211-9, Time of Delivery, as outlined in Attachment 3. The Delivery Schedule shall show deliveries per month as well as a quantified production lead time, from delivery order placement, for the MCWS-X Systems, MCWS-X IIP and Exhibit K (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.

Sustainment Approach

Training Materials The Offeror shall provide commercial training materials–such as instructor guides, student materials, and supporting media–deemed sufficient to provide Marines with a thorough knowledge and understanding of MCWS-X system set up and tear down of the system, storage, operation, preventive maintenance, corrective maintenance (if possible), troubleshooting procedures, and safety information, as outlined in SOW paragraph 3.3.12. The Government reserves the right to limit its consideration of training materials that do not succinctly demonstrate the required training.

Spares and Warranty The Offeror shall provide supportability data to include reliability, availability, and maintainability (RAM) analysis of the proposed MCWS-X system and of Lowest Replaceable Units (LRUs).

The Offeror shall provide a full list of MCWS-X spare parts in accordance with SOW Section 3.2 and Exhibit K.

The Offeror shall provide a sparing strategy to consist of a list of recommended spare LRUs, expendables, and consumables as well as recommended quantities to form a IIP Kit sufficient to support each system for 2 years, as well as and analysis to support the recommended IIP Kit chosen parts and quantities.

The Offeror shall provide a list of MCWS-X spare parts in accordance with SOW Section 3.2.2 and Exhibit K.

The Offeror shall provide the details of the warranties that will apply to the items delivered under a resulting contract, including which items are covered and which are not (if any), the terms and conditions, coverage periods, and exclusions, as outlined in SOW paragraph 3.3.13. The submissions should also address the terms of FAR clause 52.246-17.

Technical Manual The Offeror shall provide the commercial 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-X 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 3.3.11. 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-2.3.4 Volume IV: Past Performance

The Offeror shall document its recent and relevant past performance by identifying a maximum of three of its most relevant contracts with at least 12 months of performance occurring during the 36 months prior to the proposal submission deadline. (Offerors shall not submit past performance information for its intended subcontractors or for work the Offeror performed as a subcontractor.) If the contract was performed for a federal agency, please submit a copy of the complete CPAR for each rating period within the 36 month recency period. Offerors shall provide a detailed explanation of the relevance (with respect to the scope, magnitude, and complexity) of the listed contracts to the requirements of the solicitation.

Offerors submissions shall address, at a minimum, delivery schedule compliance, quality control, product performance with respect to customer specifications, product sustainability, and overall customer satisfaction.

The past performance information shall contain accurate and concise information for each contract including:

Offerors are advised that the Government may use and evaluate independently obtained past performance data from the Contractor Performance Assessment Reporting System (CPARS), telephonic interviews, or any other source or method, as deemed appropriate.

L-2.3.5 Volume V: Price/Cost

The pricing volume shall include all pricing information for the entire proposal. No pricing information shall be included in other volumes.

This volume shall include the model contract with all proposed pricing, including a completed copy of the Standard Form 33, acknowledging any solicitation amendments, signed by a person authorized to enter into the proposed contract on behalf of the Offeror. Pricing shall be submitted on the provided spreadsheet, Attachment 4 – Pricing Workbook and Exhibit K – Spare Parts Pricing Matrix.

For bundled costs, the phrase “Not Separately Priced” (NSP) shall be indicated for the corresponding CLIN/SLIN. Offerors shall provide a price for all line items in the solicitation.

Offerors may propose stepladder pricing for CLIN 0001 and 0002 and all applicable CLINs for the MCWS-X System and Spares in the remaining ordering periods based on the attached Pricing Workbook (Attachment 4). The price breakdown shall include MS Excel spreadsheets with formulas intact. If stepladder pricing is proposed, the Offeror shall reference the CLIN number, quantity range and price proposed. As described in FAR Clause 52.207-4, each Offeror who believes that acquisitions in different quantities would be more advantageous is invited to recommend an economic purchase quantity. If there are significant price breaks at different quantity points than what is found in the Pricing Workbook, the Offeror may propose this information as well.

Offerors shall not propose pricing for CLIN 0003 and all applicable CLINs for Exhibit K in the remaining ordering periods. Instead, the Offeror shall provide a list of individual spares and pricing in Exhibit K.

The Government assumes a proposal represents the Offeror’s best efforts to respond to the solicitation. As this is a competitive acquisition with adequate price competition anticipated, any cost/price documentation requested need not be certified cost or pricing data, as described in FAR Subsection 15.406-2. In the event that adequate price competition does not exist under this effort, after receipt of proposals, the Government may request additional cost or pricing data as necessary from the Offeror, subcontractors, and team members, pursuant to FAR Subsection 15.403-4.

Model Contract: The Offeror's proposal shall include a signed copy of the SF 33, with blocks 12 through 18 completed and with all Amendments acknowledged. In addition, Offerors shall include all RFP Clauses that require completion by the Offeror. 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.

The Offeror shall include a firm-fixed unit price and total CLIN price for each separately priced CLIN in Section B in the format provided. All dollar amounts provided in completed Section B shall be rounded to the nearest dollar.

SECTION M - EVALUATION FACTORS FOR AWARD

EVALUATION FACTORS

SECTION M - EVALUATION FACTORS FOR AWARD

BASIS OF AWARD

The Government will utilize the evaluation factors in this Section to identify the best value proposal. The evaluation factors represent key areas of importance to be considered in the source selection decision. The factors have been chosen to support meaningful discrimination between and among competing proposals.

The Government will evaluate each Offeror’s proposal received before the RFP closing date and time established for this solicitation, and will use the results in making the source selection decision. The source selection process will determine the merits of each proposal in terms of its potential to best satisfy the needs of the Government as well as the overall merits in making the source selection decision.

Any Offeror that is rated “Marginal” or below in any evaluation criteria will not be considered for contract award. Any Offeror whose proposal contains a deficiency will not be considered for award. Award will be to the responsible Offeror whose proposal (conforming to the solicitation) represents the best value to the Government considering the areas of Technical Approach, Past Performance, and Cost/Price. Within the best value continuum, the Government will employ a tradeoff process that permits tradeoff among cost/price and non-cost factors (see Federal Acquisition Regulation (FAR) Subsection 15.101-1).

EVALUATION FACTORS AND RELATIVE ORDER OF IMPORTANCE

The evaluation factors are listed below in descending order of importance:

· Factor 1 – Technical Approach

· Factor 2 – Past Performance

· Factor 3 – Price/Cost

Within Technical Approach, System Performance is generally more important than Sustainment Approach which is generally more important than Delivery Schedule. Note, however, that proposal flaws in either of the less important areas could be of sufficient significance as to overshadow benefits posed in either of the more important areas.

The evaluation of proposals will be conducted on a best value basis using a “trade-off” process. The non-price factors, when combined, are significantly more important than cost or price. Because this is a best value procurement, the Government may award to other than the lowest price Offeror or to other than the Offeror with the highest technical rating if the Source Selection Authority determines that doing so would result in the best value to the Government.

FACTOR 1: TECHNICAL APPROACH

The proposed Technical Approach will be evaluated and assigned a combined technical and risk rating that reflects the proposal’s approach to, and understanding of, the Government’s requirements, the strengths and weaknesses posed by the proposal, and the risk associated with the proposed performance. Risk is the potential for unsuccessful contract performance, whether in the form of schedule disruption, degraded performance, increased cost, or the need for increased Government oversight.

The technical rating evaluates the quality of the Offeror’s technical solution for meeting the Government's requirement with respect to the strengths, weaknesses, significant weaknesses, and deficiencies to determine the technical rating.

Note: Regarding Table 3, ratings are merely guides for intelligent decision making. Thus, even if one or more Offeror received the same factor rating, the fact that the rating is the same does not indicate the proposals are equally rated or viewed the same; qualitative distinctions may exist even between proposals that receive the same factor rating. Ratings will be assigned at the factor level.

Table 3: Technical Ratings

Any Offeror that is rated “Marginal” or below in any evaluation criteria will not be considered for contract award.