M67854-21-R-2090 Amendment 0003.docx

M6785421R2090

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

ATTACHMENTS

Exhibits

Attachments

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

INSTRUCTIONS TO OFFERORS

SECTION L INSTRUCTIONS

L. Proposal Instructions

L.1.1 General Instructions This section contains general instructions for submitting proposals for this effort as defined below:

1. 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 technical and cost/price factors specified under Section M of this solicitation.

1. 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 general, vague or unsubstantiated statements that prevent, or render difficult, the Government’s evaluation of the proposal. Statements such as “will comply,” or “noted and understood,” without a supporting narrative to demonstrate compliance, are rarely acceptable. Further, a proposal that merely “parrots back” the requirements of the solicitation, but fails to provide the required approach to meeting the solicitation’s requirements, is generally unacceptable. Offerors cannot presume the Government is aware or has knowledge of information not included in its proposal.

1. As prescribed by FAR 52.215-1(f)(4), the Government intends to award on the basis of initial offers received, without discussion. Therefore, each initial offer should contain the offeror’s best terms from a cost or price and technical standpoint. However, the Government reserves the right to conduct discussions and award on the basis of proposal revisions. Additionally, the Government reserves the right to limit the number of proposals in any competitive range if the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, so as to permit an efficient competition among the most highly rated proposals.

1. Proposals submitted for consideration for award must address the full scope of the solicitation. Proposals which address only part of the solicitation will likely 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. Furthermore, any apparent attempt to circumvent the page limits or other instructions, or any steps taken that may render it more difficult for the Government to evaluate the proposal on a consistent and fair basis, may result in the proposal’s rejection.

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

1. All classified material must be handled in accordance with DD254 (Attachment 5). The Government will verify all Facility Clearance information through Defense Counterintelligence Security Agency for all offerors. Offerors without a security Facility Clearance will not be able to discuss or access aspects of the program that are classified nor will they be able to pass such information on to their subcontractors. MIL-STD-2169C, as referenced in Attachment 1 (PSPEC), is classified SECRET. Offerors requesting this document must provide their classified mailing address and classified account e-mail (if applicable) address to the MCHH Contract Specialist at zachary.seay@usmc.mil. The request shall include the offeror’s business name, mailing address, CAGE code, and point of contact. The Government will verify the offeror’s eligibility (current facility security clearance and appropriate storage capability) and provide the MIL-STD via U.S. Postal Service. Further dissemination by offerors is NOT authorized.

1. All classified material must be handled in accordance with the DD254 (Attachment 5), DoD National Industrial Security Program Operating Manual (32 CFR 117), Industrial Security Regulation (DoD 5220.22-R), and DoD Information Security Program (DoDM 5200.01, Volume 1-3). The Government will verify all Facility Clearance (FCL) information through the Defense Security Service for all offerors and their subcontractors. Offerors without a security FCL will not be able to discuss or access key aspects of the program that are classified nor will they be able to pass such information on to their subcontracor(s).

1. Chairman of the Joints Chief of Staff Notice 6510, provided as (Attachment 7) and Chairman of the Joints Chief of Staff Instruction 6510.02E, provided as (Attachment 8) to this solicitation, are classified SECRET. Offerors requesting this document are required to fill out and submit a Classified Material Mailout Courier Request (Attachment 9) to the MCHH Contract Specialist at zachary.seay@usmc.mil with a CC to Katy Hurd at kathryn.hurd@usmc.mil. The Government will verify the offeror’s eligibility (currently facility security clearance and appropriate storage capacity) and provide the document via U.S. Postal Service or other appropriate method. Further dissemination by offerors is NOT authorized.

L.1.2 Organizational Conflicts of Interest (OCI) 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 MCHH contract award, or submit a statement declaring that there are no known actual or potential OCIs. This obligation applies even if identified prior to proposal submission. If the offeror concludes that it has no actual or potential OCI it shall submit a statement in its proposal affirming that it is not aware of any actual or potential OCI. 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 an offeror fails to submit either a disclosure of potential OCI situations or an affirmative statement that the offeror is not aware of any OCI, or fails to appropriately and promptly update its submission, the offeror may not be considered for award. If the contracting officer determines that any actual or potential OCIs cannot be mitigated, then the offeror shall not be eligible for award.

Offerors are advised that Government support contractors from the following company(ies) participated in the preparation of this RFP:

Prime Contractor: Alexandria Insights

L.1.3 Responsibility The offeror is solely responsible for any and all costs associated with the preparation and submission of any proposal in response to this solicitation (bid and proposal costs), including any and all incurred costs associated with offeror’s participation in verification or demonstration activities. Offerors are advised that the Government will not reimburse any offeror for bid, proposal, or demonstration related costs, as a contract line item associated with responding to this solicitation or participating in verification or demonstration-related activities.

L.1.4 Validity Each offeror’s entire proposal shall remain valid for a minimum of 210 days from the date for receipt of offers by the Government, and the offeror shall insert "210" in Block 12 of the Standard Form 33 (SF 33). If an offeror states in their proposal that the proposal is valid for any period less than 210 days, the proposal may not be considered for award.

L.1.5 Proposal Format

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

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. Content shall not be placed in charts, diagrams or tables for the apparent purpose of avoiding page limits. 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.

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

Page Limitations: Page limitations are identified for each Volume/Section of the proposal, as described in Table L-2 below, and will be treated as maximums. Pages in excess of the stated limits 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 a fair and consistent 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 newer 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 (all of which will be excluded from page limits). 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 a set of binders containing paper copies of each Volume, at the quantities listed below in L.2.1. The offeror shall also submit an electronic copy of all seven volumes of the proposal on compact discs (CD(s)).

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.1.6 Delivery of Proposal

Proposals must be delivered in both a hard-copy format and an electronic format via the means described below.

Hard copy proposals shall be either hand delivered or mailed to the location listed below by 10:00 a.m. Local Time, Quantico, Virginia, on 22 October 2021. 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 210 days from the date specified for the receipt of offers.

Offerors shall prominently mark all containers used for delivery of proposals with the following:

“SOLICITATION M67854-21-R-2090”

Source Selection Information – See FAR 2.101 and 3.104

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 and time listed above. Hand carried proposals must be delivered to the address listed below.

The proposal shall be marked prominently on the outer face “Request for Proposal – Solicitation M67854-21-R-2090” and delivered to one of the following addresses, submitted in the quantities indicated at L.2.1.

NOTE: The building at 105 Tech Parkway in Stafford is secure, so offerors are instructed to contact Ms. Katy Hurd at 703-863-4499 or Mr. Zachary Seay at 703-432-8725 when arriving at the building. The individual delivering the proposal will be met in the lobby. Please wear a mask if hand delivering items inside the building.

The offeror shall also submit an electronic copy of all volumes, on CDs. Each CD shall be marked with the title, RFP number, and offeror’s name. CD Requirements: Offerors shall use Microsoft Office 2007 software or higher to create the required .xls, .ppt and .doc files as well as Adobe Acrobat Version7.0 or higher to create .pdf files.

INTENT TO INCORPORATE CONTRACTOR’S PROPOSAL

The Government may decide to incorporate all or part of the successful offeror’s proposal 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.7 Questions

Questions regarding the solicitation documents are due by 1:00 p.m. Local Time, Quantico, Virginia, on 24 September 2021, and must be submitted via e-mail to kathryn.hurd@usmc.mil and zachary.d.seay@usmc.mil in the format specified in Table L-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. The Government reserves the right to combine or edit questions for clarity and efficiency and to create questions of its own, to communicate additional information to offerors.

Table L-1: Question Format

General Issue

Solicitation

Performance Spec

Other (identify)

L.2 Proposal Contents

All information the offeror intends to have considered shall be submitted with the initial proposal. The initial proposal shall contain the best offer. Offerors are responsible for including sufficient information to permit a complete, thorough, and accurate evaluation of the submitted 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 aesthetics 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 great importance.

L.2.1 Proposal Layout

The proposal submitted in response to this Request for Proposal (RFP) shall be submitted in the following volumes and numbers:

Volume I: Executive Summary (10 copies) Volume II: Exceptions, Deviations, Conditions and Waivers (3 copies) Volume III: Technical (10 copies) Volume IV: Technical Appendices (10 copies) Volume V: Past Performance (10 copies) Volume VI: Subcontracting and Small Business Participation (3 copies) Volume VII: Cost and Price (6 copies)

Volumes I through VII shall include no classified material. The offeror shall omit all cost/price and past performance information from Volumes I-IV. Any price/cost or past performance information in these volumes will render the proposal non-compliant. All past performance information shall be in Volume V and VI and all cost/price information shall be in Volume VI and VII. Volumes I-IV may bound together as a single set. Volumes V, VI, and VII shall each be bound separately from all other volumes.

Table L-2: Proposal Organization

As defined below

Restrictions Table

(DFARS 252.227-7017)

No page limit

L.2.2 Volume I: Executive Summary

L.2.2.1 Offerors shall submit an Executive Summary on company letterhead.

The Executive Summary shall not exceed three pages, including the signed SF 33. The following information shall be included in the cover letter:

1. Brief summary of the offeror’s capability to accomplish the requirements of the contract;

1. 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);

1. The point of contact for the proposal, including the individual’s name, company position/title, phone number, and e-mail address;

1. A statement that the offeror is proposing as either a small business or a large business;

1. An affirmative statement that the identified point of contact has the authority to enter into an agreement on behalf of the offeror’s company;

1. An affirmative statement of agreement to all terms, conditions, and provisions of this solicitation and that the proposal does not include any assumptions, terms, conditions, caveats, or exceptions that are not detailed in Volume II;

1. An affirmative statement that the offeror is not aware of any OCI or potential OCI with itself, subcontractors, partners or any other offeror as it applies to this solicitation for the MCHH contract award, or an affirmative statement that any OCI or potential OCI that the offeror is aware of, as it applies to this solicitation, has been disclosed to the Contracting Officer and the date it was disclosed, including if it was disclosed with the proposal submission;

1. An affirmative statement that the entire proposal will remain valid for a minimum of 210 days from the date specified in Block 9 of the SF 33 and completion of Block 12 of the SF 33 (offeror shall insert "210");

1. The offeror’s cognizant Defense Contract Audit Agency (DCAA), Defense Contract Management Agency (DCMA) and Defense Finance and Accounting Services (DFAS) payment office offices;

1. 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); and

1. Signed copy of the SF 33; digital signature or handwritten signature on scanned copy will be acceptable.

Offerors shall attach to the Executive Summary any submissions required in accordance with Section K of this solicitation. Submission requirements for Section K are not included in the page limit for the Executive Summary.

L.2.2.2 MCHH System Matrixes

The offeror shall populate and submit the Performance Specification Matrix (PSPEC Compliance Matrix) and the Statement of Work Cross Reference Matrix (SOW CRM) provided as Attachments 2 and 6 at Section J of this solicitation.

L.2.2.2.1 Volume I, Section 1.1: SOW Cross Reference Matrix

In populating the SOW CRM, Attachment 6, the offeror shall indicate where in Volume III, Section 3, and/or Volume IV an evaluator will find the detailed discussion of those particular requirements identified in the SOW CRM and more fully outlined in the SOW. Offerors shall not use the SOW CRM itself to provide substance regarding the proposed solution or method of performing the work; instead, the SOW CRM is merely a map indicating where certain of the SOW requirements are discussed in Volume III and/or Volume IV, and must not be used in any manner to increase the volume of information permitted by the Table L-2 page limits.

L.2.2.2.2 Volume I Section 1.2: PSPEC Compliance Matrix

In populating the PSPEC Compliance Matrix, Attachment 2, the offeror shall indicate whether the proposed system meets (Yes or No) each requirement; may list a “Proposed Capability” associated with the requirement (only if a capability that exceeds the required one is proposed); shall indicate, under “Substantiating Data Reference,” where the specific Test Reports and Exhibits are located (in Section 4.1 of Volume IV) to substantiate that the requirement is met, or exceeded; shall indicate, under “Key Requirement Reference,” where in Section 3.2 of Volume III their proposal discusses those PSPEC requirements designated as “Key;” and shall indicate, under “Waivers Requested Reference,” where in Volume II the waiver and plan for achieving the waived requirement is discussed for the particular PSPEC requirement. Offerors shall not use the PSPEC Compliance Matrix to address PSPEC requirements or any aspect of the proposal to be addressed elsewhere. The PSPEC Matrix is intended to provide PSPEC compliance information, to provide capability information (where a requirement is exceeded), and to map where evaluators may find other information or discussion. The PSPEC Compliance Matrix must not be used in any manner to increase the volume of information permitted by the Table L-2 page limits.

L.2.2.2.3 Volume I Section 1.3 NSA and CNSA Compliance

The offeror shall submit a copy of the documentation demonstrating that their proposed MCHH has National Security Agency (NSA) certification for operation up to the Secret level, is capable of operating with CNSA Suite encryption, and meets NSA’s Communications Security Modernization requirements. If the proposed system is not yet approved by NSA as meeting one or more of these security standards, the offeror must describe how it does not meet the standard, where it is within the process of securing certification as meeting the standard, and when it anticipates receiving NSA certification. In the event an offeror’s proposed MCHH becomes certified with respect to one of these security standards during the source selection process, the offeror is requested to immediately provide evidence demonstrating that certification to the Contracting Officer (kathryn.hurd@usmc.mil) and Contract Specialist (zachary.d.seay@usmc.mil) listed for proposal submission. That information will be considered up until the point that an award determination is made.

The Offeror shall submit the Volume I Section 1.3 NSA and CNSA Compliance as an Adobe .pdf file and label the file as Volume I Section 1.3 NSA and CNSA Compliance (DDMMMYYYY).pdf for submittal to the Government. The Offeror shall submit the below Supporting Documents as an Adobe .pdf:

(a) National Security Agency (NSA) Certification. The Offeror shall provide NSA Certification for operations up to Secret as defined in 3.4.1 of the PSPEC.

(b) CNSA Suite. The Offeror shall provide proof the proposed MCHH is capable of operating with CNSA Suite encryption as defined in 3.4.2 of the PSPEC.

(c) NSA Certification Plan. A NSA Certification Plan, which shall not exceed 15 pages, signed physically or digitally by the Offeror and providing all of the following information:

(1) Company Part Number or the Nomenclature or the National Stock Number (NSN) and name of Offeror's company;

1. Software configuration baseline;

1. Hardware configuration baseline;

1. The date the certification process was started, and the steps and documents that were completed at the time of the initial technical proposal submission for NSA Certification;

(5) The steps and documents remaining to be completed to obtain NSA Certification;

(6) Any anticipated Governmental actions enabling the completion of NSA Certification;

1. The anticipated date that the proposed MCHH will obtain the NSA Information Assurance Directorate Certificate; and

1. The Government NSA Point of Contact for the Certification.

The Government may contact NSA to verify the feasibility of the proposed MCHH achieving certification in accordance with the offeror’s proposed Certification Plan. Any discrepancies identified between the Certification Plan and information obtained from NSA may result in an unacceptable rating. The Offeror may receive an unacceptable rating if the content of the plan or information obtained from NSA is contrary to, or inconsistent with, achieving certification or that information indicates that the vendor’s solution is not likely to achieve certification. The Company Part Number or the Nomenclature or the National Stock Number (NSN) and the Offeror’s name identified on the Certification shall be readily identifiable as the same MCHH proposed and identified throughout the documents references in the PSPEC Compliance Matrix

L.2.3 Volume II: Exceptions, Deviations, Conditions, Assumptions, Understanding and Waivers

Volume II shall contain all exceptions, deviations, conditions, assumptions, understandings, and waiver requests that the offeror takes with respect to the provisions of the 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 that if not met by the Government prior to contractor performance, would reduce or remove the contractor’s obligation to perform the contract according to the solicitation’s terms. An assumption is a statement meant to convey an offeror’s understanding of a condition or underlying fact that is not expressly stated in the solicitation, such as circumstances that might impact the offeror’s benefits and burdens under a resulting contract. An understanding is a specific statement of the meaning an offeror attaches to a solicitation requirement. A waiver is an offeror’s request for the Government to accept performance or an item that will depart from specified requirements because the contractor believes this differing performance or item would be considered suitable by the Government. It is unnecessary to seek a waiver for any PSPEC requirement listed as an objective requirement.

If the offeror submits a proposal including any of the preceding features, the offeror shall provide a description of each exception, deviation, condition, assumption, understanding or request for waiver. The offeror’s submission shall describe 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. All waivers (including PSPEC Waivers) shall be submitted in Volume II. In submitting an exception, deviation, condition, assumption, understanding 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, assumption or understanding. Finally, the inclusion of any of these in an offeror’s proposal may render the proposal unawardable.

L.2.4 Volume III: Technical

This volume shall be sufficiently specific, detailed, and complete to demonstrate clearly and fully that the offeror has a thorough understanding of the solicitation’s technical requirements, is proposing a solution that meets those requirement, and has an approach to satisfying those requirements is likely to succeed. Offerors shall submit only one solution.

L.2.4.1 Volume III, Section 3.1: System Design

The offeror shall provide a detailed description of the system design including a consolidated description of 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.

L.2.4.2 Volume III, Section 3.2: System Performance

Offerors shall describe how their chosen technical solution allows the proposed system to meet or exceed the PSPEC requirements designated as “key requirements” in the PSPEC Compliance Matrix. They may discuss how their substantiating data authoritatively demonstrates and validates that the system meets those capabilities. If the offeror has indicated in the PSPEC Compliance Matrix that the proposed system fails to meet a threshold PSPEC requirement, key or otherwise, the offeror shall request a waiver and discuss its “Get-well Plan” in Volume II and should identify where in Section 4.1, Volume IV evaluators can find the test results showing the threshold failure.

L.2.4.3 Volume III, Section 3.3: System Sustainment Approach and Technology Insertion Program Plan

In Section 3.3 of Volume III, the offeror’s proposal shall include a system sustainment approach that best supports the Marine Corps’ maintenance strategy, as expressed here and in the SOW, in the context of Marines using the MCHH in a deployed environment. The proposed approach shall address how it supports and enables the Marine Corps’ ability to successfully sustain the MCHH for the life of the contract and beyond. The proposal shall include the offeror’s approach to reducing reliance on a manufacturer warranty in favor of an organic Marine Corps maintenance capability, and reducing the overall Marine Corps logistics footprint. The offeror shall address strategies that increase the reliability, availability and maintainability of the proposed system while reducing the Government’s total ownership costs. The offeror’s proposal shall describe a Return Material Authorization (RMA) and Warranted Item replacement approach that includes RMA processing time, help desk support, and indicates Turn-Around Time (TAT) for all items under warranty.

In Section 3.3 of Volume III, the offeror shall describe how it plans to initiate and maintain a Technology Insertion Program as described in Section 3.1.2 of the SOW. This plan should describe existing capabilities the offeror maintains within its organization to develop its MCHH solution and incorporate state-of-the art developments in relevant technologies. The offeror should describe how it plans to address this performance requirement or otherwise develop its existing capabilities to ensure a cutting edge MCHH solution. The offeror should describe how it would approach updating the existing MCHH inventory by inserting technology, to include supporting software and/or hardware, and porting waveforms such as Single Channel Ground and Airborne Radio System Frequency Hopping III. It is the Government’s intent to insert such technology, when it is sufficiently mature, to be fielded in a relatively short period of time with acceptable risk. The Offeror shall describe how it plans to add a specific technology, capability, or waveform–upon the Government determining such technology, capability, or waveform to be instrumental to the evolutionary approach of MCHH–while meeting any updates to the performance specifications and the schedule agreed upon by both parties.

L.2.4.3.1 System Sustainment

The Marine Corps plans to sustain the MCHH using Government personnel and facilities, beginning as soon as practicable and continuing throughout the program’s lifecycle. The Marine Corps’ maintenance concept for the MCHH requires that the contractor enable Government personnel and equipment to fully maintain, diagnose, and repair the system in a deployed environment without sending equipment back to the contractor. The Government estimates that the transition period to providing Government performed maintenance on the MCHH will be no greater than 2 years after contract award. Offerors’ proposed sustainment approach shall address how best the Marine Corps can achieve this objective and shall propose reasonable warranty support for the transition period. Note, the Government does not intend to contract for Field Support Representatives as part of its sustainment efforts. Furthermore, the Marine Corps views a sustainment process that requires MCHH systems to be shipped to an offeror’s facility for repairs as adversely affecting operational availability. Therefore, the offeror’s proposed approach for system sustainment should be one that minimizes the shipping time associated with system repair. The offeror shall provide a narrative of the overall approach to sustainment that the Marine Corps should employ to successfully manage system configuration control and technical aspects of the MCHH. This approach should include notifying the Government of changes to the following: sources of supply, configuration baseline, interface and software control, parts and accessories, provisioning, training, technical manuals, and data requirements management, as each applies to sustainment.

L.2.4.4 Volume III, Section 3.4: Technical Data

The Government requires delivery of the technical data necessary to support its maintenance strategy, to allow the Government to test, diagnose, and repair or replace components down to the circuit card assembly level through the use of general support maintenance personnel and equipment that is organic to the Marine Corps. The necessary data deliverables are listed throughout the SOW. Offerors are welcomed to provide deliverables with greater rights than those required by the operative DFARS clause, and may propose and describe those greater rights in specifically identified deliverables, or other technical data, in Section 3.4 of Volume III.

L.2.4.5 Volume III, Section 3.5: Assertion of Restrictions Table (DFARS 252.227-7017)

Offerors shall complete, sign, and submit, within Section 3.5 of Volume III, the Assertion of Restrictions Table mentioned in DFARS 252.227-7017 to identify deliverables that will include restrictions on the Government’s rights to use, release, or disclose the technical data or software to be delivered.

L.2.5 Volume IV: Technical Appendices

The Technical Appendices are identified in the subparagraphs that follow, and have no associated page limit.

L.2.5.1 Volume IV, Section 4.1: Test Data and Exhibits

In Section 4.1 of Volume IV, the offeror shall provide supporting test data and exhibits that map directly to requirements defined in the MCHH PSPEC. Where the verification method listed in the PSPEC is identified as “Test,” the vendor shall provide the Test Report in Section 4.1 of Volume IV, properly referenced in the PSPEC Compliance Matrix.

The test data submitted to support the proposal will not count against the volume page count. However, 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 efficiently and effectively consider. The test equipment used (to include calibration information), test setup, test procedures, and testing approach, shall be included in the test data. The offeror shall provide test results and reports that were verified through independent or third-party test agencies, with Government testing preferred. Offeror testing, which is testing conducted internally by the offeror, or without independent or third part test observers, shall be clearly denoted as such in this appendix. The test data and exhibits shall be organized as follows:

1. Test data resulting from a Government hosted test event at Government facilities, either by a Department of Defense Service Component, or certified test agency.

1. Test Data resulting from an independent and/or third party test, including a commercial source. Certification from the independent and/or third party organization must accompany the test data.

1. Test Data resulting from testing conducted internally by the offeror. If any internal test data is provided in the proposal, it shall be certified as accurate by the offeror.

1. Offerors shall note the absence of test data for each threshold requirement, properly referenced in the PSPEC Compliance Matrix, and shall include an analysis and risk statement in Section 4.1 of Volume IV, for consideration.

L.2.5.2 Volume IV, Section 4.2: Integrated Master Schedule (IMS) At Section 4.2 of Volume IV, the Offeror shall summarize its proposed approach to scheduling and allocating program resources in the Integrated Master Schedule (IMS). All IMS schedule information must be consistent with the events and tasks described in the proposal. The IMS shall reflect all appropriate events and tasks in the proposal, to include the proposed production and delivery schedule, in a Gantt (or similar presentation format) chart for all events and tasks to Work Breakdown Structure (WBS) Level 3 for the basic contract, using contract award as the start date. The IMS shall provide, at a minimum, task numbers, task names, duration, predecessor tasks (i.e. task interdependencies), a start date, and a finish date for all activities. In building the IMS, offerors shall assume the maximum order quantity will be ordered each year.

L.2.5.3 Volume IV, Section 4.3: Quality Management

At Section 4.3 of Volume IV, the Offeror shall discuss specific processes and methodologies it proposes to use to ensure MCHH quality control is maintained throughout this contract.

L.2.5.4 Volume IV, Section 4.4 Waveform Compliance Roadmap

At Section 4.4 of Volume IV, the offeror shall provide a Waveform Compliance Roadmap that illustrates the offeror’s plan to meet the cryptographic requirements of Chairman of the Joints Chief of Staff Notice 6510 and Chairman of the Joints Chief of Staff Instruction 6510.02E. The Waveform Compliance Roadmap shall incorporate the software communications architecture and technical performance waveform requirements of the MCHH PSPEC. This roadmap shall define the offeror’s plan for the development of Waveform Engineering Change Proposals (ECPs), Waveform Modification Instructions (MIs), and Waveform Notices of Revision (NOR). The offeror’s Waveform Compliance Roadmap shall depict the development steps required to meet the NSA’s evolving waveform requirements, including software and hardware configuration in accordance with the contractor’s configuration management. The waveform compliance roadmap shall also identify any risks to cost, schedule, and performance. The present and planned waveforms described in Table 3.1 of the MCHH PSPEC shall be addressed in the Waveform Compliance Roadmap. The offeror shall depict a clear path to meet the implementation and certification of the Warrior Robust Enhanced Network (WREN) waveforms, currently documented as objective requirements, but expected to become threshold in the near future, as specified in paragraph 3.23 of the PSPEC. The offeror’s Waveform Compliance Roadmap shall depict a timeline in which WREN will be offered to the Government for operational use.

L.2.5.5 Volume IV, Section 4.5 Production and Delivery Schedule

In Section 4.5 of Volume IV, the Offeror shall provide a production and delivery schedule that illustrates their plan to produce and deliver an initial quantity of 100 MCHHs and 100 VIKs within 30 days of contract award. The Offeror’s production schedule shall also illustrate their plan to produce and deliver an estimated quantity of 1300 MCHHs and 1100 VIKs per month beginning no later than January 1, 2023, and a production rate of 4000 per month for MCHH and 2500 per month for VIKs beginning no later than April 1, 2023.

L.2.6 Volume V: Past Performance.

In Volume V, offerors shall submit up to three recent contracts performed by the prime, as a prime contractor, that are relevant to this solicitation’s requirements, particularly in terms of scope, magnitude, and complexity. 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 for any reason during the past 3 years, whether terminated in whole or in part. Also, include all efforts where the prime or proposed integrator have received notice of the Government’s intent to terminate, whether or not the contract ended in a termination action. The information regarding efforts terminated or proposed for termination will not count towards the page limit in Table L-2.

L.2.6.1 Each past performance summary shall be limited to three pages and shall include:

1. Section 1 – Contract Description:

0. Contract number, order number if applicable, CAGE code, DUNS number, and North American Industry Classification System (NAICS) code;

0. Government contracting activity, Contracting Officer name, telephone number, and email address;

0. Government Contracting Officer Representative (COR) and/or technical representative, telephone number, and email address;

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

0. Address in lieu of or in addition to the contact information required above:

4. Contract type

4. Awarded price/cost

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

4. Final (actual) or projected final (if ongoing) start and end dates of the reported period of performance

4. Percentage of effort, based on the total cost of the work required in the referenced contract or order, performed or to be performed by the offeror as prime contractor

4. Description of the specific tasks or activities performed by the offeror itself under the contract

1. Section 2 - Narrative:

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

1. Section 3 - Contract Performance:

2. For any contracts that failed to meet technical performance requirements, provide a brief explanation of the reasons for the shortcomings and any corrective actions taken to avoid recurrence of the failure.

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

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

L.2.7 Volume VI 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.2.7.1 Volume VI, Section 6.1: Small Business Achievements

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

L.2.7.2 Volume VI, Section 6.2: Small Business Subcontracting Record (Attachment 3)

All offerors shall submit, at Section 6.2 of Volume VI, 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 3, Section 6.2: 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.

Notes:

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

1. Offerors utilizing achievements information of team…