PDSS RFP AMEND 01 24R7603 20240515.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as p rovid ed herein, all terms and cond itions o f th e document referenced in Item 9A o r 10 A, as hereto fore chang ed , remains un ch an ged and in full force and effect.

15A. NAME AND T IT LE OF SIGNER (T ype or print )

30-105-04EXCEP TION T O SF 30

AP PROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) P rescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to:

1. Change off er due date from 03 July 2024 to 15 July 2024.

2. Add DFARS clause 252.204-7012, Saf eguarding Covered Def ense Inf ormation and Cyber Incident Reporting (DEVIATION 2024-O0013) and remove DFARS Clause 252.204-7012.

3. Update Section L to revise due dates in Tables L.1 and L.2.

All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 25

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

16C. DATE SIGNED

BY 15-May-2024

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

(Signa ture of Cont ract ing Officer)(Signat ure of person aut horized t o sign)

8. NAME AND ADDRESS OF CONT RACT OR (No., St reet , County, Sta te and Zip Code) X M6785424R7603

X 9B. DATED (SEE IT EM 11)

02-May-2024

10B. DATED (SEE IT EM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS IT EM ONLY AP PLIES TO AMENDMENT S OF SOLICITAT IONS

X Th e ab ove n umbered solicitation is amend ed as set forth in Item 1 4. Th e hou r and date sp ecified for receipt o f Offer X is extend ed , is not extended.

Offer mu st ackn owled ge receipt of this amen dment p rior to the h our an d d ate specified in the solicitation or as amen ded b y o ne of the following method s:

(a) By completing Items 8 and 15 , and returnin g 1 co pies of the amen dment; (b ) By ackn owled ging receipt of this amen dment o n each copy of the o ffer sub mitted ;

o r (c) By separate letter o r teleg ram wh ich includ es a reference to th e so licitation and amend men t nu mbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtu e of this amen dment y ou desire to change an offer already su bmitted, su ch change may be made by teleg ram or letter, p rovid ed each telegram o r letter mak es reference to th e so licitation and this amen dment, an d is receiv ed prio r to the op en ing hou r and date sp ecified.

12. ACCOUNTING AND AP PROP RIATION DATA (If required)

13. THIS ITEM AP PLIES ONLY T O MODIFICATIONS OF CONT RACT S/ORDERS.

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

A. THIS CHANGE ORDER IS ISSUED P URSUANT T O: (Specify aut horit y) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN T HE

CONT RACT ORDER NO. IN ITEM 10A.

B. T HE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office , appropria tion dat e, et c.) SET FORT H IN ITEM 14, P URSUANT TO T HE AUT HORITY OF FAR 43.103(B).

C. T HIS SUPP LEMENTAL AGREEMENT IS ENT ERED INTO PURSUANT TO AUT HORITY OF:

D. OT HER (Specify type of modificat ion and aut horit y)

E. IMP ORTANT: Contrac tor is not, is required t o sign this document and re turn copies to t he issuing office.

14. DESCRIP TION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, inc luding solic ita tion/contrac t subject mat t er where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If app licable)

6. ISSUED BY

3. EFFECTIVE DATE

15-May-2024

CODE

M ARINE CORPS SYSTEMS COM MAND - CT 2.76

2200 LEST ER STREET

QUANT ICO VA 22134

M67854 7 . ADMINISTERED BY (If o ther than item 6)

4 . REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M6785424R7603

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 03-Jul-2024 11:00 PM to 15-Jul-2024 10:59 AM.

The following have been added by full text:

252.204-7012 (DEV)

252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting. (DEVIATION 2024- O0013)

(a) Definitions. As used in this clause—

Adequate security means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information.

Compromise means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred.

Contractor attributional/proprietary information means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company.

Controlled technical information means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination.

Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions.

Covered contractor information system means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information.

Covered defense information means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/categorylist.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is—

(1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or

(2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract.

Cyber incident means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein.

Forensic analysis means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data.

Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information.

Malicious software means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware.

Media means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system.

Operationally critical support means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation.

Rapidly report means within 72 hours of discovery of any cyber incident.

Technical information means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data—Other Than Commercial Products and Commercial Services, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code.

(b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems.

To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections:

(1) For covered contractor information systems that are part of an Information Technology (IT) service or system operated on behalf of the Government, the following security requirements apply:

(i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract.

(ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract.

(2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply:

(i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations”, Revision 2 (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171).

(ii)(A) The Contractor shall implement NIST SP 800-171, as soon as practical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award.

(B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place.

(C) If the DoD CIO has previously adjudicated the contractor’s requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract.

(D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment.

(3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan.

(c) Cyber incident reporting requirement.

(1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor’s ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall—

(i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor’s network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor’s ability to provide operationally critical support; and

(ii) Rapidly report cyber incidents to DoD at https://dibnet.dod.mil.

(2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at https://dibnet.dod.mil.

(3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see https://public.cyber.mil/eca/.

(d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer.

(e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest.

(f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information equipment that is necessary to conduct a forensic analysis.

(g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause.

(h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released.

(i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD—

(1) To entities with missions that may be affected by such information;

(2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents;

(3) To Government entities that conduct counterintelligence or law enforcement investigations;

(4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or

(5) To a support services contractor (“recipient”) that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information.

(j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government’s use and release of such information.

(k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data.

(l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor’s responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements.

(m) Subcontracts. The Contractor shall—

(1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial products or commercial services, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and

(2) Require subcontractors to—

(i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and

(ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause.

(End of clause)

The following have been modified:

52.212-1 ADDENDUM

SECTION L

This section lists the instructions for all interested offerors submitting a proposal in response to Solicitation #M67854-24-R-7603 for the Post Deployment System Support services contract. The Government intends to conduct the source selection in accordance with the competitive source selection procedures contained in Federal Acquisition Regulation (FAR) Part 12, in conjunction with FAR Part 15, resulting in a single award, indefinite delivery, indefinite quantity contract. This contract will be issued to the offeror who provides the best value to the Government in terms of non-price factors and price.

The Government has listed certain documents in this RFP that an interested offeror may need in order to submit a responsive proposal. Offerors can find the documents in Section J of the RFP starting with Attachment J13. If offerors have issues or questions about the documents, please contact the Contract Specialist, Mr. Phillip Makely, at phillip.makely@usmc.mil, with a copy to the Contracting Officer, Ms. Renée Stahl, at renee.stah@usmc.mil .

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

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

L.1 General

L.1.1 Estimated Award and Start Dates

The estimated date of contract award is approximately 30 April 2025 with the actual paid period of performance for the base CLIN beginning approximately 30 days after award. All fully qualified personnel required for initial transition purposes must be onsite and operational at all locations at the start of the period of performance for TO 01.

The Government reserves the right to award sooner or later, if necessary.

L.1.2 Facility Clearance Requirement

This effort requires that the contractor obtain an active SECRET facility clearance, and to maintain that clearance for the duration of contract performance once the clearance is received. The Government will sponsor any new SECRET facility clearance requests for this requirement in the event that the awardee does not hold the required clearance at the time of award.

L.1.3 Proposal Characteristics

A single, concise, and comprehensive proposal is required. The Government will not consider multiple or alternative proposals, or proposals that deviate from the solicited requirements. The proposal shall be complete and clear in all respects without the need for additional explanation or information. The offeror shall propose in sufficient detail and scope to permit the Government to evaluate the proposal with respect to the evaluation factors specified in the 52.212-2 Addendum, Evaluation Factors for Award.

Unnecessarily elaborate proposals beyond what is sufficient to present a complete and effective proposal are not desired. The proposal should be clear, complete, and succinct while addressing the request in sufficient detail to allow the Government to be able to evaluate the offeror’s capability to perform. Likewise, offerors are cautioned against general, vague, or unsubstantiated statements, which prevent or render difficult the Government’s evaluation of the proposal.

Proposals that merely restate the requirement or state that the requirement will be met, without providing supporting rationale or adequate description of how the requirement will be met (e.g., brief statements such as “will comply,” or “noted and understood,” without supporting narrative to demonstrate how compliance will be achieved), may be evaluated as unacceptable by the Government. Moreover, the Government is not obligated to assume that an offeror possesses any capability, understanding, or commitment that is not specifically delineated and supported in its proposal. 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 and form an adequate basis for the Government to assess the merits of the offeror’s proposal.

As prescribed by FAR Provision 52.212-1, the Government intends to award on the basis of initial proposals received, without discussions. The Government reserves the right to conduct discussions if the Contracting Officer determines them to be necessary. Therefore, each initial proposal shall contain the offeror’s best terms from a price and non-price standpoint.

Additionally, the Government may reject any or all offers, accept other than the lowest price offer, and waive informalities and minor irregularities in offers received, if such actions are in the public interest.

Proposals submitted for consideration for award must address the requirements of the solicitation. Proposals, which address only part of the solicitation will most likely be considered unacceptable. Limits on the number of pages in the proposal have been imposed, as indicated in Table L.1, below.

Offerors shall not rely on the Government’s awareness of information previously submitted or assumed known;

instead, the offeror is obligated to submit whatever information the Government should consider in support of its proposal.

L.1.4 Award Determined Using a Multi-Step Approach

The Government will make the award determination using a two-step process as described below. The first step will assess the experience of interested offerors. Offerors will be required to provide past performance and work experience information for Government evaluation. Offerors who demonstrate sufficient experience to be considered viable will then progress to the second step where written proposal documentation, price information, and oral presentation will be evaluated. Contract award will be made to the offeror who represents the best value to the Government.

L.1.5 Notification of Potential Organizational Conflict(s) of Interest

Per FAR Part 9.5, the offeror is reminded that certain existing contractual arrangements may preclude or restrict participation, as either a prime contractor or subcontractor, under this competitive procurement. Existing contractual arrangements in which a contractor provides program support to Program Manager (PM), Logistics Integrated Information Solutions Services- Marine Corps (LI2S-MC), or related activities are of primary concern. General guidance may be found in FAR 9.505; however, this guidance is not all-inclusive. The offeror’s attention is directed to the “Organizational Conflict of Interest (OCI),” and to similar requirements which may be contained in a current or completed contract which may prohibit the prime or subcontractor from providing certain supplies or services to the Government, as described above, during the period of the current “program support” contract(s) or for a period after completion of the “program support” contract(s).

Offerors shall review their existing contractual arrangements to determine whether they believe a potential conflict of interest exists, at any tier, between any of these arrangements (under a current or recent contract) and performance of the solicited effort. If an offeror believes a potential conflict of interest exists, the offeror is required to notify the Contracting Officer within 7 calendar days of the publication date of this solicitation. The offeror shall provide the following information in its notification:

a) The contract number and name and phone number of the Contracting Officer for the contract which gives rise to a potential OCI;

b) A copy of the contract and the contract’s RFP;

c) The statement of work (or technical instruction) from the existing contract;

d) A brief description of the type of work to be performed by each subcontractor under this solicited effort;

e) A proposed mitigation plan; and

f) Any additional information the Contracting Officer should consider in making a determination of whether a conflict of interest exists.

The Government may independently verify the information received from the offeror.

Notwithstanding the above, the Government reserves the right to determine whether a conflict of interest exists based on any information received from any source and, if an OCI exists, whether it can be mitigated. If the Government determines the OCI cannot be mitigated, the contractor will be deemed ineligible to participate in the current competition and will have their proposal, if submitted, rejected.

The Government will notify the offeror regarding any conflict of interest, or potential conflict of interest, that it has identified as an OCI concern within 14 calendar days of receipt of all required information from the offeror. Those offerors deemed to have a conflict of interest may be ineligible for award. Failure to provide the information in a timely manner does not waive the Government's right to make a conflict of interest determination and take appropriate remedial action to protect the integrity of this procurement. All proposal preparation expenditures are at the offeror’s own risk and will not be reimbursed by the Government, whether or not it is determined that an OCI exists.

An offeror that proposes a subcontractor who is later determined to have a conflict of interest and is thereby deemed ineligible to participate in the current competition, may or may not be granted the opportunity to revise its proposal to remove the ineligible subcontractor, at the Government’s sole discretion.

L.1.6 Intent to Incorporate Offeror’s Proposal

The successful offeror’s proposal may be incorporated, in whole or part, in any resulting contract from this solicitation. Nothing contained in the successful offeror’s proposal shall constitute a waiver to any requirement of the contract.

L.2 Submission Instructions

L.2.1 Format Instructions

The contractor’s proposal, including submissions for Step One and Step Two, shall be prepared in accordance with these instructions:

a) Printable on letter-sized (8-1/2” X 11”) pages, single-spaced, with one-inch (1”) margins on all edges. All documents shall be submitted in Microsoft Office 2013 or newer (Word/Excel/Power Point) or Adobe Pro as a

PDF;

b) Use a 12-point font size in either Times New Roman or Arial;

c) Tables, graphics, and illustrations are not required but, if included, shall be kept to a minimum (within the page limitation) and shall not be used to circumvent the page limits, but should be prepared with no less than 9-point font size with single spacing;

d) Header and footer may fall within the margins described above;

e) Any section header/footer material shall not be larger than 14-point font;

f) Separate pages for tables of contents, definitions sections, and acronyms listings are allowed. The number of pages for these sections do not count toward the page limitations imposed herein;

g) If acronyms are used, they should be spelled out the first time they are used in the document in which they appear; and

h) Offerors alone bear the risk of evaluators not understanding what is intended.

The offeror’s proposal shall be submitted in accordance with the associated formatting parameters in Table L.2. Any pages in excess of the page limitations will not be considered.

Offerors shall mark the first page of all proposal volumes with the following legend:

“REQUEST FOR PROPOSAL – SOLICITATION [M67854-24-R-7603]”

Source Selection Information – See FAR Sections 2.101 and 3.104.

L.2.2 Step One

Table L.1 below reflects the date and time for actions to be completed during Step One.

Table L.1 – Step One Submission

REQUIREMENT/ACTION VIA RESPONSIBILITY DUE DATE

Solicitation Released PIEE &

SAM*

Government 5/2/2024

Solicitation Amendment 1 Released PIEE &

SAM*

Government 5/15/2024

Submit Questions regarding solicitation (L.2.3) Email to Contract Specialist (see address below).

Offeror 5/28/2024

Post Responses to Offerors’ Solicitation Questions PIEE and

SAM

Government 6/20/2024

Send Past Performance Questionnaires to Customers (L.2.4.3)

Email Offeror TBD

Past Performance Questionnaires due to Government

Email Offeror’s Customers 7/15/2024

Submit Past Performance References/Work Experience Submission (L.2.4.2 and L.2.4.1)

PIEE Offeror 7/15/2024

Notification of Eligibility for Continuation in the Competition Process (L.2.4.4)

Email Government 8/12/2024

* NOTES:

(1) Find the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module at: https://piee.eb.mil.

(2) Find the System for Award Management (SAM) website at: https://sam.gov.

L.2.3 Questions.

Questions regarding the solicitation documents are due by the date and time listed in Table L.1, and must be submitted via email to both of the following addresses:

Contracting Officer: Ms. Renée Stahl, Renee.Stahl@usmc.mil Contract Specialist: Mr. Phillip Makely, Phillip.Makely@usmc.mil

The Government reserves the right to modify questions for clarity, merge similar questions, eliminate duplicate questions, and to disregard questions deemed to be spurious or argumentative in nature. Questions received after the above time and date may, in the Government’s sole discretion, not be answered. Government responses will be provided as an amendment to this solicitation, requiring offeror acknowledgment, via the original solicitation method. Government responses will be posted on the original point of solicitation publication along with any amendments to the solicitation. Any requests for information or clarifications sought by an offeror or potential offeror shall be submitted only via the methods, and in accordance with the dates, set forth above. Offerors or potential offerors shall not contact any Government personnel directly outside of the methods or outside of the timelines described above. Additionally, the Government reserves the right to include solicitation questions and responses of its own creation as deemed likely to improve the offerors’ understanding of the solicitation.

NOTE: The Government need not respond to questions that are not submitted in conformance with these instructions, including substance, delivery method, and timeliness of submission.

L.2.4 Work Experience Submission, Past Performance References, and Past Performance Questionnaires (PPQ)

Interested offerors must use their judgment on how best to demonstrate, through the efforts selected as their work experience and their past performance submissions, that they are a viable offeror.

L.2.4.1 Work Experience Submission:

Interested offerors shall submit, on no more than 18 (single-sided) pages, a work experience submission which includes a description of their experience and involvement on prior contracts of similar scope, magnitude, and complexity of effort that they consider most relevant to the Performance Work Statement (PWS). Any work experience, as described in the list below, that does not have an associated past performance reference shall not be submitted and will not be evaluated by the Government. Examples of relevant experience are defined as, but not limited to, the following:

Providing technical support services for the operation, maintenance, and sustainment of a large enterprise logistics system's hardware and software.

Providing technical support services for the operation, maintenance, and sustainment of the solution development environment for a large highly integrated logistics system.

Providing accreditation processes, administration, and management support services for large integrated military enterprise systems.

Providing disaster and recovery planning, operations, and maintenance support services for large integrated enterprise systems.

Providing operation, maintenance, sustainment, and upgrade support services for a high volume, multi-system enterprise service desk.

Providing technical and functional subject matter experts to oversee the daily operations of a large integrated enterprise system, which includes the continual surveillance of systems operations, systems maintenance, systems sustainment, and system upgrade support services.

Providing a fleet of support services, including fulfilling logistics, training, manpower, financial, and auditing tasks, for a large integrated enterprise logistics system.

Providing change request services using the Agile methodology to address software operation, maintenance, sustainment, and upgrade support for a large integrated enterprise.

Providing integrated enterprise cloud operation, maintenance, sustainment, storage, migration, and upgrade support services.

Providing support services for cybersecurity monitoring, intrusion prevention, vulnerability analysis and management, security planning, vulnerability management, Information Technology position category requirements, compliance monitoring, and testing services.

Providing system engineering, configuration management, and system level management for a large enterprise system.

Interested offerors should use their judgment on how to best demonstrate that they are a viable offeror through their 18-page submission. These pages shall demonstrate the similarity of the work experience to the solicited effort, as well as establishing the offeror’s experience performing those efforts.

Offerors shall submit their documents electronically to the Contracting Officer, Ms. Renée Stahl, Renee.Stahl@usmc.mil , and the Contract Specialist, Mr. Phillip Makely, Phillip.Makely@usmc.mil no later than 11:00 PM EST on 3 July 2024.

L.2.4.2 Past Performance References:

For each work experience example submitted--and only those efforts—offerors shall ensure they have also submitted the effort as an example of past performance. The past performance effort shall be recent, as defined in Section M, and be as similar to the solicited effort with respect to scope, magnitude, and complexity as possible. An offeror who has not performed similar work will not have the experience necessary to be considered viable and, therefore, should not submit a proposal. The offeror shall consider recency and relevancy (as described by the 52.212-2 Evaluation Addendum) when selecting its work experience and past performance references. The submission shall include Government references for recent Federal Government contracts. References for work performed for Department of Defense Military Commands are preferred over references involving other Government agencies. Each past performance reference shall be no more than five pages total, and shall include the following:

a) Project Identification:

i. Project Name

ii. Awarding Agency/Organization

iii. Award Date

iv. Total Periods of Performance (Dates)

v. Total Award Value and Performed Value

vi. Contract/Task Order (TO) Number

vii. Identify if the Offeror was a prime or a subcontractor

b) Points of Contact:

i. Name of the Procuring Contracting Officer (PCO) and the Contracting Officer Representative

(COR) from the agency to which the service(s) were provided

ii. Current phone numbers for PCO and COR

iii. Email Addresses for PCO and COR

c) Performance:

i. Describe the nature of the work performed

ii. Describe the primary responsibilities of the contractor

iii. Explain how the work performed on the referenced contract is same or similar with regard to scope, magnitude, and complexity of the work described in the Contract PWS and TO 01 PWS for this RFP.

L.2.4.3 Past Performance Questionnaires (PPQ):

The offeror shall send PPQs (found in RFP Attachment J07) to the identified customers and instruct them to submit the completed PPQs directly to the Government. The offeror shall complete only those portions of the PPQ noted for offeror completion and the balance of the PPQ may be completed only by the customer’s representative. The customer shall return the completed questionnaire directly to the PM-LI2S Contracting Officer and Contract Specialist and not share it with the offeror.

Offerors shall submit their documents electronically to the Contracting Officer and the Contract Specialist listed in L.2.3 above, and in accordance with the dates specified in Table L.2 below.

L.2.4.4 Viable/Non-Viable Process and Notifications

At the end of the Step One evaluation, the Contracting Officer will notify offerors regarding their inclusion in, or exclusion from, Step Two. Offerors will receive notification in writing from the Contracting Officer of their viable/non-viable status in advance of the Step Two process.

L.2.5 Step Two

The below table reflects the actions to be completed during Step Two, along with reference to the Step One documents for overall awareness. The offeror shall respond by the date and time listed in Table L.2, unless otherwise directed in writing by the Contracting Officer.

Offerors shall mark the first page of all proposal volumes with the following legend:

“REQUEST FOR PROPOSAL – SOLICITATION [M67854-24-R-7603]”

Source Selection Information – See FAR Sections 2.101 and 3.104.

Table L.2 – Proposal Submission Documents

THE GOVERNMENT RESERVES THE RIGHT TO REJECT ANY PROPOSAL, OR PART THEREOF, THAT

DOES NOT COMPLY WITH THESE PROPOSAL PREPARATION INSTRUCTIONS (including, for example, margins, font size, spacing, including narrative in tables, graphics, or illustrations, etc.). ANY APPARENT ATTEMPT TO CIRCUMVENT THE PAGE LIMITS OR OTHER INSTRUCTIONS, OR ANY OFFEROR STEPS

TAKEN THAT RENDER IT MORE DIFFICULT FOR THE GOVERNMENT TO EVALUATE THE PROPOSAL

ON A CONSISTENT AND FAIR BASIS, MAY RESULT IN THE PROPOSAL’S REJECTION.

L.2.5.1 Proposal Submission

Section Title Maximum Pages

Due Date File Naming Structure

Cover Letter Cover Letter 5 9/9/2024 Company Name_CL_24R7603

Volume I Past Performance Stated in Step One above.

7/15/2024 Company Name_VOLI_24R7603

Volume II Technical Approach & Capability Oral Presentation-Slides

75 9/9/2024 Company Name_VOLII_24R7603

Volume III Price No Limit 9/9/2024 Company Name_VOLIII_24R7603

Volume IV Small Business Participation Plan

No Limit 9/9/2024 Company Name_VOLIV_24R7603

The Contracting Officer will request proposals only from the offerors deemed viable during Step One. Proposals shall address the following factors:

Factor 1 - Past Performance (Step One submission will be used for the past performance evaluation) Factor 2 – Technical Approach and Capability/Oral Presentation Factor 3 – Price Factor 4 – Small Business (SB) Participation Plan

L.2.5.2 Proposal Documents Submissions

Offerors shall submit an electronic copy of all volumes of their proposals via the PIEE Solicitation Module (found at https://piee.eb.mil/xhtml/unauth/home/login.xhtml ) in accordance with the dates specified in Table L.2.

Each individual file in the offeror’s proposal has a size limitation of 1.9 GB. There is no total size submission limitation.

Any proposal received after the specified date/time will be considered a late submission. Late submissions will be treated in accordance with FAR Clause 52.212-1(f).

Proposals shall be valid for a period of not less than 365 days from the solicitation closing date.

NOTE: A vendor registration guide for contractors on how to set up accounts in the system has been posted to the PIEE website at:

https://piee.eb.mil/xhtml/unauth/home/login.xhtml

Scroll to the bottom of the page and click “VENDORS.”

L.3 Content

L.3.1 Cover Letter

A cover letter shall be used to transmit the proposal and is considered a part of the proposal. The cover letter will be used to transmit any information the offeror wishes to bring to the attention of the Contracting Officer, including any assumptions, understandings, waivers, conditions, exceptions, or deviations taken concerning the RFP requirements.

An authorized official of the offeror shall sign the transmittal letter. On the first page of this volume, the offeror shall certify that the proposal has been prepared completely consistent with the terms and conditions of the solicitation, as published, or that any assumptions, understandings, waivers, conditions, exceptions, and deviations from the solicitation are addressed in the cover letter. If any assumption, understanding, waiver, condition, exception, or deviation is taken, the proposal may be determined non-compliant and thus, ineligible for award.

An assumption—or an understanding—is the offeror’s dependence upon a set of facts not included in the Government’s solicitation, as the offeror has developed its offer. The assumption/ understanding may impact the offeror’s benefits and burdens under a resulting contract. The Government may deem the offeror’s expression of an “assumption” or an “understanding” as indicating the parties do not have a meeting of the minds and may treat the offeror’s expression as a condition of acceptance, or an exception to the Government’s requirements. 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 offeror’s obligation to perform the contract according to the solicitation’s terms.

If the offeror submits a proposal including any of the preceding features, the offeror shall provide a description of each, indicating the offeror's difficulty with the applicable requirement and the offeror's proposed solution, where applicable. Further, the offeror shall specifically identify the portions of the solicitation and the offeror's proposal that are affected by this proposal feature.

The cover letter shall include the following information, at a minimum:

a) Date submitted;

b) Contractor’s name (including CAGE Code, Unique Entity Identifier [UEI], and Taxpayer ID);

c) Contractor Point of Contact & contact information;

d) Contractor’s contact information for those who can legally bind the contractor;

e) All offered subcontractor(s) (as applicable) (including CAGE Code, UEI, and Taxpayer ID);

f) Reference to any unique terms or conditions; and

g) Offer length of validity period. The contractor shall specify an offer validity period of not less than 365 calendar days from date of closing.

L.3.2 Factor 1 – Past Performance

The past performance references that were provided as part of Step One, will also be used to evaluate past performance.

L.3.3 Factor 2 – Technical Approach and Capability/Oral Presentation

Volume II: Technical Approach and Capability shall be delivered in PowerPoint format with no more than one slide per page. This will be the basis of the Oral Presentation. Regardless of when its oral presentation is scheduled, the offeror shall use only the slides submitted as Volume II in conducting that presentation. It is anticipated that Oral Presentations will take place in person, in the month of August 2024, in Stafford, VA. Offerors will be notified of the specifics by the Contracting Officer no less than 14 days in advance of their presentation date, time, and location.

The Government will not reimburse the offeror for any travel related to their submissions including travel for Oral Presentations.

Offerors will provide an oral presentation demonstrating their technical and management acumen regarding the work and tasks required in the base contract’s PWS and the first TO’s PWS.

L.3.3.1 Presentation Instructions

Offerors shall conduct the presentation using the slides submitted in Volume II and are cautioned against submitting slides that are PowerPoint versions of written, narrative proposals. Government evaluators have no responsibility to read or consider the slides submitted, either during or apart from the oral presentation, and offerors are cautioned not to have presenters merely read the slides to the evaluators. The duration of the presentation shall not exceed 135 minutes. There will be one, 15-minute break at the 60-minute mark of the presentation. At the conclusion of the presentation, an optional "Question and Answer" period may be exercised at the discretion of the Government.

Additionally, Government evaluators may raise questions at any time during the presentation. Questions raised during the presentation will not result in additional presentation time.

The presentation should be based on, and consistent with, the material in the advanced Volume II submission.

Offerors shall demonstrate an understanding of the PWS requirements and establish a technical capability to perform the work, largely by reference to performance of prior efforts of a similar nature. The presentation will include the offeror’s approach and plans to meet all requirements. Offerors shall address the risk in implementing those requirements, based on their technical capabilities and their chosen approach. The proposal shall address the requirements for both the base contract and TO 01. It is imperative that the presenters clearly and thoroughly describe how they will meet the requirements, using past work accomplishments as appropriate. Do not simply copy and paste, rephrase, or restate PWS language; doing so will not demonstrate either a technical capability or a specific approach, and is more likely to result in the Government finding your proposal unacceptable and excluded from further competition.

The Government will record each presentation given by all offerors in any format deemed sufficient to maintain an adequate agency record and reference for the evaluation process. Presenters are advised that their presentation will be recorded and will be protected in accordance with the rules and regulations applicable to source selection materials.

L.3.3.2 Presentation Content

The offeror should come prepared to discuss, at a minimum, the following points:

L.3.3.2.1 Technical Approach

a) The offeror shall address their proposed approach to oversight and management;

b) The offeror shall present an organization chart showing lines of authority, responsibility, and communication for management, supervisory, and technical personnel;

c) The offeror shall explain how they plan to manage the transition period; and

d) The offeror shall discuss how schedules will be maintained for the technical solutions, requirements, and goals identified in the PWS.

L.3.3.2.2 Technical Capability

a) The offeror shall address their understanding of the requirements and goals set forth in the scope of the work identified in the PWS;

b) The offeror shall explain how they plan to fulfill the requirements…