M67854-23-R-4907 Amend 0004_30 June 0223.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to: 1)Revise Attachment 8 Existing Telecomm and Netw ork Infrastructure 2) Revise the Travel/ODC tab in

Attachment 10 PDO 0001 Pricing Workbook 3) Revise Attachment 13 RDSD Current PON Netw ork and Expected Grow th 4) Revise FAR

52.212-1 Addendum 11.1 Volume III, Section 5.1 - Pricing Workbook and 5) Provide responses to additonal industry solicitation questions.

The Solicitation close date of 11 July 2023 has not been extended as a result of this amendment.

1. CONTRACT ID CODE PAGE OF PAGES

1 13

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

16C. DATE SIGNED

BY 30-Jun-2023

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

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

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

X 9B. DATED (SEE ITEM 11)

10-May-2023

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

30-Jun-2023

CODE

COMMANDER MARINE CORPS SYSTEMS COMMAND

2200 LESTER STREET

QUANTICO VA 22134

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M6785423R4907

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

EXHIBIT/ATTACHMENT LIST

Exhibit/Attachment List

Attachments

DOCUMENT TYPE PAGES DATE

Attachment 1- ISTC Systems Engineering Plan 67 18 JAN 2023

Attachment 2 - ISTC Test and Evaluation Management Plan 33 03 MAR 2022

Attachment 3 - PEO Digital Configuration Management Plan 60 01 SEP 2022

Attachment 4 - ISTC Risk Management Plan 30 26 APR 2023

Attachment 5 - PM N&I Programmatic Environmental, Safety, and Occupational

Health Evaluation (PESHE)

80 10 MAR 2014

Attachment 6 - ISTC BAN Solution Architecture and CONOPS 40 11 MAY 2021

Attachment 7 - ISTC UC Solution Architecture and CONOPS 30 17 MAY 2021

Attachment 8 - ISTC Existing Telecommunications and Network Infrastructure 3 28 JUNE 2023

Attachment 9 - NetMod Plan v 2.2 347 09 SEP 2021

Attachment 10 - PDO Pricing Workbook M67854-23-R-4907 4 28 JUNE 2023

Attachment 11 - Past Performance Questionnaire 8 14 MAR 2023

Attachment 12 – PDO Performance Work Statement 15 09 JUNE 2023

Attachment 13 – RDSD Current PON Network and Expected Growth 8 28 JUNE 2023

Exhibits

DESCRIPTION PAGES DATE

Exhibit A, Contract Data Requirements List (CDRLS) 28 23 JUNE 2023

Exhibit B, CDRLS 10 26 MAY 2023

Exhibit D, CDRLS 24 26 APR 2023

FAR 52.212-1 ADDENDUM

Instructions to Offerors

1. OVERVIEW

The Government Infrastructure Services, Transport and Communications (ISTC) portfolio is seeking potential

Offerors with the capability to meet the requirements described in this solicitation. This solicitation describes the instructions to Offerors for the BAN IDIQ contract and the initial Proposed Delivery Order (PDO). The proposal process will be a single-phase effort consisting of a written proposal leading to the award of multiple IDIQ contracts.

The Government will consider several non-price factors and price during the evaluation process. The non-price factors include Technical Approach (which includes as an element, the Technical Approach for the initial PDO), Management Approach, and Past Performance. The Government intends to award the first delivery order concurrently with the IDIQ awards. The Government will also evaluate prices proposed for the initial PDO, in order to determine the best value proposals. The Offeror who submits the best value proposal will receive one of the multiple IDIQ awards as well as the initial Delivery Order. The Offerors with the remaining best value proposals will also receive an IDIQ contract that includes the guaranteed minimum of $1,500. The Government intends to conduct the source selection in accordance with the competitive source selection procedures contained in FAR Part

12, in conjunction with FAR Part 15. Subsequent Delivery Orders will be competed amongst the multiple IDIQ award holders on a best value basis, consistent with the fair opportunity procedures in FAR 16.505.

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

THE GOVERNMENT RESERVES THE RIGHT TO REJECT ANY PROPOSAL THAT DOES NOT

SUBSTANTIALLY COMPLY WITH THESE PROPOSAL PREPARATION INSTRUCTIONS.

2. GENERAL

A single concise and comprehensive proposal is required. The Government will not consider multiple or alternative proposal submissions from an Offeror. The proposal shall be complete and clear in all respects without the need for additional explanation or information. The proposal shall be in sufficient detail and scope to permit the Government to evaluate it with respect to the evaluation factors specified in Evaluation Factors for Award.

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

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

As prescribed by FAR 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 later determined by the

Contracting Officer to be necessary. Therefore, each initial proposal shall contain the Offeror’s best terms from a price, management and technical standpoint.

Proposals submitted for consideration for award must address the factors of the solicitation. Proposals, which address only part of the solicitation, will be considered unacceptable. Limits on the number of pages in the proposal have been imposed, as indicated in Section 7 below. Proposals that exceed the maximum page limit will have the excess pages disposed of.

Data, even though previously submitted or presumed known by the Government, cannot be considered as part of the

Offeror’s proposal unless submitted with, and incorporated into, the proposal.

Offerors requesting the restricted documents on SAM.gov, must provide an active CAGE code in their request prior to receiving access to the RFP restricted documents. Should offerors have issues or questions about accessing the requesting documents please contact the Contract Specialists Mr. Todd Ingold at todd.ingold@usmc.mil and Ms.

Monet Payne at monet.l.harrison@usmc.mil with a copy to the Contracting Officer Ms. Morgan Brady at morgan.brady@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.

3. QUESTIONS AND CLARIFICATIONS

Questions regarding the solicitation documents are due by 3:00 pm ET on May 22, 2023 and must be submitted via e-mail to the Contract Specialists Mr. Todd Ingold at todd.ingold@usmc.mil and Ms. Monet Payne at monet.l.harrison@usmc.mil with a copy to the Contracting Officer Ms. Morgan Brady at morgan.brady@usmc.mil in the format specified in Table 1 with the subject line M67854-23-R-4907 ISTC MAC IDIQ Questions. Please do not bundle multiple questions into one. The Government reserves the right to merge similar questions and to eliminate duplicative questions. Questions received after the above time and date may not be answered.

Government responses will be posted on the sam.gov website. No information concerning this solicitation or mailto:todd.ingold@usmc.mil mailto:monet.l.harrison@usmc.mil mailto:morgan.brady@usmc.mil https://sam.gov/ mailto:todd.ingold@usmc.mil mailto:monet.l.harrison@usmc.mil mailto:morgan.brady@usmc.mil requests for clarifications will be provided via telephone. Government responses will be provided as an amendment to this solicitation, requiring vendor acknowledgement.

Table 1: Question Format

Question

Number

Document/Section Paragraph

Number

Question/Issue/Concern

General Issue

Solicitation

SOW

Other

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

Submission Instructions

Offerors shall submit an electronic copy of all volumes of their proposals via the PIEE Solicitation Module (found at https://piee.eb.mil) no later than 3:00 pm Eastern Time (ET) on July 11, 2023. Each individual file has a size limitation of 1.9GB. There is no total size submission limitation. 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.212-1(f).

Proposals shall be valid for a period of not less than 180 days from the closing date listed above.

Offerors shall prominently mark all proposals with the following:

“SOLICITATION M67854-23-R-4907 ISTC MAC IDIQ PROPOSAL”

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

Pricing and Contracting website at: https://www.acq.osd.mil/dpap/pdi/eb/docs/PIEE/PIEE

Solicitation_Module_Vendor_AccessInstructions.pdf.

For access to the subject Solicitation within the PIEE Solicitation Module, Offerors submitting proposals shall provide their active CAGE code to the Contract Specialists Mr. Todd Ingold at todd.ingold@usmc.mil and Ms.

Monet Payne at monet.l.harrison@usmc.mil with a copy to the Contracting Officer Ms. Morgan Brady at morgan.brady@usmc.mil no later than 12:00 pm Eastern Time (ET) on 11 July 2023. Proposals shall be fully uploaded within the PIEE Solicitation Module no later than 3:00 pm Eastern Time (ET) on July 11, 2023.

4. NOTIFICATION OF POTENTIAL ORGANIZATIONAL CONFLICT(S) OF INTEREST

The Offeror is reminded that certain existing contractual arrangements may preclude or restrict participation as either a Prime Contractor or Subcontractor under this competitive procurement. Existing contractual arrangements in which a Contractor provides support to Program Executive Office Digital and Enterprise Services, Portfolio

Infrastructure Services, Transport and Communications (ISTC) operations, or related activities are of primary concern. General guidance may be found in FAR 9.505; however, this guidance is not all-inclusive. The Offeror’s attention is directed to the “Organizational Conflict of Interest” or similar requirement which may be contained in current or completed contract(s) which prohibits the Prime or Subcontractor from providing certain supplies or services to the Government as described above during the period of the current “support” contract(s) or for a period after completion of the “support” contract(s).

https://piee.eb.mil/ https://www.acq.osd.mil/dpap/pdi/eb/docs/PIEE/PIEE%20Solicitation_Module_Vendor_AccessInstructions.pdf https://www.acq.osd.mil/dpap/pdi/eb/docs/PIEE/PIEE%20Solicitation_Module_Vendor_AccessInstructions.pdf

Notwithstanding the existence or non-existence of an Organizational Conflict of Interest (OCI) clause or similar requirement in current or completed contract(s), the Offeror shall comply with FAR 9.5 and shall identify whether an OCI exists and not rely solely on the presence of an OCI requirement.

Offerors shall review their existing contractual arrangements to determine whether they believe a potential conflict of interest exists, at any tier. If an Offeror believes a potential conflict of interest exists, the Offeror is required to notify the Contracting Officer within seven (7) calendar days of the date of this solicitation. The Offeror shall provide the following information in its notification: (1) the contract number and name and phone number of the

Contracting Officer for the contract which gives rise to a potential OCI; (2) a copy of the requirement; (3) the statement of work (or technical instruction) from the existing contract; (4) a brief description of the type of work to be performed by each Subcontractor under the competitive procurement; (5) a proposed mitigation plan; and (6) any additional information the Contracting Officer should consider in making a determination of whether a conflict of interest exists. The Government may independently verify the information received from the Offeror.

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

The Government will make the determination in any case of a conflict of interest has been identified as mitigated.

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

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

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

5. INTENT TO INCORPORATE CONTRACTOR’S TECHNICAL PROPOSAL

Portions of each successful Offeror’s technical proposal may be incorporated in any contract resulting from this solicitation. Nothing contained in the successful Offeror’s technical proposal shall constitute a waiver to any requirement of the contract.

6. INSTRUCTIONS FOR PREPARATION OF PROPOSALS

Offerors are required to address all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, and must thoroughly address all evaluation factors. Failure to adequately address an evaluation factor shall result in an Offeror being ineligible for award.

Margins and Fonts: Proposals shall be prepared using uncompressed “Arial” or “Times New Roman” font no smaller than 12-point. Font size no smaller than 10-point may be used in flow charts, diagrams, and tables. Margins shall be 1 inch on all four sides. All materials submitted may be no more condensed than single-spaced and shall not use proportional spacing or any other method in an attempt to get more text on the page than is here specified.

Offerors shall ensure that each page provides identification of the submitting Offeror in the header or footer. The header and footer may use the margins at the top and bottom of the page, but the substance of the proposal may not.

Each page of the Offeror’s proposal shall contain the following legend at the bottom: Source Selection Information

– See FAR 2.101 and 3.104.

Pages: The definition of a page is a single side of paper with text, drawings, data, or similar content. Pages shall be

8.5 x 11 inches in size. Foldouts are allowed for technical diagrams, shall be no larger than 11 inches x 17 inches, and shall be counted as two pages.

Page Limitations: Page limitations are identified for each Volume/Section of the proposal, as described in Table 2 below, and will be treated as maximums. The maximum page limits identified in Table 2 are sequential; excess pages, those that exceed stated page limitations, will not be read or considered in evaluation of the proposal. Unless stated otherwise herein, pages providing graphics, charts, illustrations, and pictures are included in the page count.

Any proposal that is prepared inconsistently with the intent of these instructions, that appears to be designed to avoid or circumvent the page limits, or that in any way inhibits the Government’s ability to evaluate offers on an equal basis may result in portions of the proposal being disregarded, or the entire proposal being rejected as non-conforming.

Format: The Offeror shall organize and submit their proposals in accordance with the instructions below in Sections

7 and 8. All proposal volumes shall be in searchable Adobe Acrobat .pdf files. The Offeror shall submit the Project

Schedule in Microsoft Project 2016 for PC applicable and the price breakdown shall include Microsoft Excel 2016 spreadsheets with formulas intact.

Electronic file naming convention: Please name all files submitted electronically as follows: company, volume #, document title.xxx; where xxx is the file type (i.e., docx .xls, .mpp or .pdf).

Each Offeror must submit its proposal materials in separate volumes and files as identified in Table 2 below. Each volume shall contain a title page, table of contents, and a list of tables and figures for that volume. The title page, table of contents, and list of tables and figures do not count against page count. Number all pages sequentially.

Only material allocated to a specific section shall be in that section.

In each volume, Offerors shall provide a Table of Contents and Acronym List. Volume I shall include a Cross-

Reference Matrix showing the proposal paragraph number where an evaluator will find the detailed discussion of the requirements listed in the Performance Work Statement. The Cross-Reference Matrix will not be included as part of the page count.

7. Proposal Volume Breakout

The Offeror shall present pertinent information in the appropriate sections as indicated below. Volume page maximums shall be limited in accordance with the following table:

Table 2 - Proposal Outline

Section Title Maximum Pages File Naming

Structure

Volume I

Section 1.1 Executive Summary 2 * (excludes SF1449 and amendments) ABC_Vol I_ES.xxx

Section 1.3 SOW Cross Reference Matrix

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

Technical Approach and will not be considered in assessing the Technical

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

ABC_Vol

I_PCM.xxx

Section 1.4 Acronym List and Glossary No page limit* ABC_Vol I_AL.xxx

Factor 1 - Technical Approach

Section 2.1 SOW Overarching Technical

Approach

ABC_Vol

I_Tech_App.xxx

Section 2.2 Technical Project Approach

Proposed Delivery Order (PDO)

ABC_Vol

I_PDO_TPA.xxx

Section Title Maximum Pages File Naming

Structure

Section 2.3 Project Schedule PDO 5 ABC_Vol

I_PDO_PS.xxx

Factor 2 - Management Approach

Section 3.1 Overarching Program Management

Approach

ABC_Vol

I_Mgmt_PMA.xxx

Section 3.2 Overarching Staffing Plan 5 ABC_Vol

I_Mgmt_SP.xxx

Section 3.3 Management Tools, Governance, and Partnering Approach

ABC_Vol

I_Mgmt_TGP.xxx

Section 3.4 Staffing Plan PDO 5 ABC_Vol I_Mgmt_

PDOSP.docx

Volume I Maximum Total Page Count 59

Volume II

Factor 3 - Past Performance

Section 4.1 Recent and Relevant Past

Performance

ABC_Vol II_PP.xxx

Volume II Maximum Total Page Count 5

Volume III

Factor 4 – Proposed Delivery Order Pricing

Section 5.1 Pricing Workbook No Limit ABC_Vol

III_PDO_Pricing.xls

Volume IV Maximum Total Page Count No Limit *Note: page limits with an asterisk shall not count against the total page count for the section in which they are included.

8. INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT

8.1 Volume I, Section 1.1 - Executive Summary:

An authorized official of the Offeror shall sign the Executive Summary. On the first page of this volume, the

Offeror shall certify that the proposal has been prepared completely consistent with the terms and conditions of the solicitation or that any exceptions, deviations, and waivers to the solicitation are addressed in the Executive

Summary. If any exceptions, deviations and/or waivers are taken, the proposal may be determined non-compliant and thus, ineligible for award. An Offeror’s proposal shall include an Executive Summary that includes the following:

• Solicitation number and closing date and time;

• Government issuing office identification;

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

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

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

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

This section shall include an overall executive summary that describes the significant attributes of the Offeror’s proposal and describes the Offeror’s understanding and capability to accomplish the requirements of the contract.

This part shall identify the Offeror’s cognizant Defense Contract Management Agency (DCMA), Defense Contract

Audit Agency (DCAA), and Defense Finance and Accounting Services (DFAS) payment office. A signed copy of the SF1449 and all Amendments shall be signed by an agent who has the authority to sign on behalf of the Offeror, acknowledging any/all amendments shall be included in this section. The signed SF1449 and any amendments are excluded from the page count listed in table 2.

Valid Period: State clearly the period for which the proposal is valid. The proposal shall be valid for a minimum of

180 calendar days.

8.2 Volume I, Section 1.2 - RESERVED

8.3 Volume I, Section 1.3 - SOW Cross Reference Matrix

Offerors shall create a SOW Cross Reference Matrix, which maps each SOW requirement identified in:

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

• 9 Volume I, Section 3, Factor 2 Management Approach

• 10 Volume II, Section 4, Factor 3 – Past Performance addressed to the proposal location (Volume, Section, Page, and Paragraph) where the requirement is discussed.

Offerors shall not use the SOW Cross Reference Matrix to provide substance regarding the proposed solution or in any manner attempt to increase the volume of information permitted by the page limitations.

8.4 Volume I, Section 1.4 - Acronym List and Glossary

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

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

8.5.1 Volume I, Section 2.1 –SOW Overarching Technical Approach

The Technical Approach proposal consists of the Offeror’s overarching Technical Approach to the SOW and overall engineering approach. For evaluation purposes only, the Offeror’s Overarching Technical Approach will not address all of the requirements delineated in the Base IDIQ SOW. Instead, the Offeror’s Technical Approach should clearly demonstrate the Offeror’s thorough understanding of the solicitation’s technical requirements identified below.

The Offeror shall address its understanding of the Equipment Procurement task; Configuration Item Refresh task;

and the Development Testing, and Fielding of Current TRL-9 Capabilities task, as well as its approach to satisfy each as identified in SOW section 5.0. The proposal shall include a description of proposed tools, processes, analysis, and methodologies to be used in performing each of the specific tasks identified. The Offeror should also address any value added skill sets and capabilities within their proposal that meet or exceed requirements;

• The Offeror shall provide its methodology to go from a functional baseline to a product baseline/reference architecture using the three-phased approach of Phase 1: VSS; Phase 2: Engineering Design; and Phase 3:

Implementation. Key emphasis shall be placed on the integration of the production design into the installation including consideration of other systems, installation particularities, logistics management, and key stakeholders;

• The Offeror shall describe its approach to Configuration Management during the three-phased approach of

Phase 1: VSS; Phase 2: Engineering Design; and Phase 3: Implementation;

• The Offeror shall describe their approach for the Configuration Item Refresh task, and the Development

Testing, and Fielding of Current TRL-9 Capabilities task, regarding both multi-installation and single installation fielding.

Offerors shall submit CDRL B004 Quality Control Plan with this section. The CDRL submission shall be not more than 10 pages but will be outside of the page count identified in Table 2 above.

8.5.2 Volume I, Section 2.2 – Technical Project Solution PDO

For evaluation purposes only, the Offeror’s Technical Project Solution will not address all of the requirements delineated in the PDO SOW (Attachment 12). Instead, the Offeror’s Technical Project Solution should clearly demonstrate the Offeror’s thorough understanding of the PDO technical requirements identified below.

• The Offeror shall describe its understanding, analysis, approach, risks, and roadblocks to delivering a

MCRD San Diego voice solution that provides business voice capability to USMC and tenant users on the installation. The Offeror’s approach shall discuss the use of the three phrased approach Phase 1: VSS,;

Phase 2: Engineering Design; and Phase 3: Implementation. Key emphasis shall be placed on the integration of the production voice design with session border controller and telecommunications infrastructure into MCRD San Diego including consideration of other systems, installation particularities, logistics management, and key stake holders.

• The Offeror shall describe its understanding, analysis, approach, risks, and roadblocks to expanding the existing MCRD San Diego Passive Optical Network (PON) to extend the network to all voice user locations and install the latest software version on all PON system components. The Offeror’s approach shall discuss the use of the three phrased approach Phase 1: VSS; Phase 2: Engineering Design; and Phase

3: Implementation. Key emphasis shall be placed on the integration of the production design into the installation including consideration of enterprise network and cybersecurity systems, installation particularities, logistics management, and key stake holders.

• The Offeror shall demonstrate its understanding and approach to meeting or exceeding Key System

Attributes identified in Section 2.2 of Attachment 6 ISTC BAN Solution Architecture Concept of

Operations and Section 2.2 of Attachment 7 Regional Unified Capabilities Voice Services Solution

Architecture and Concept of Operations.

Offerors shall Submit CDRL D002 Material and Equipment List/BOM with their Technical solution, this will not count against the page limitation for this section.

8.5.3 Volume I, Section 2.3 – Project Schedule PDO

The Offeror shall summarize its proposed approach to scheduling and allocating program resources in the Project

Schedule. All Project Schedule information must be consistent with the events and tasks described in the proposal.

The Project Schedule shall reflect all appropriate events and tasks in the proposal, to include the proposed delivery schedule, in a Gantt (or similar presentation format) chart for all events and tasks to Work Breakdown Structure

(WBS) Level 3 for the PDO, using contract award as the start date. The Project Schedule shall provide, at a minimum, task names, duration, predecessor tasks (i.e. task interdependencies), a start date, and a finish date for all activities.

9. Volume I, Section 3, Factor 2 – Management Approach

9.1 Volume I, Section 3.1 - Overarching Program Management Approach

The Offeror shall provide a detailed and thorough Program Management approach that demonstrates the Offeror’s capability to effectively manage and execute the Base IDIQ SOW requirements for multiple systems at multiple installations. This Management Approach should define proposed interfaces with the Government that will be employed over the ordering period. The Offeror shall provide detailed information concerning the various methods or techniques to be used in planning, scheduling, processing, controlling, and completing the requirements stated in the SOW.

The Offeror shall provide organization charts showing the proposed management structure, teaming relationships, Subcontractors, and organizational elements. The Offeror shall describe the organizational boundaries and interfaces between the Offeror and external entities and how communication and coordination of efforts will be managed. “External” is defined as entities or organizations not on the Offeror’s team (e.g. program office, system users, hosting facilities). The Offeror shall also describe its internal structure. “Internal” is defined as entities or organizations within the Offeror’s team, including roles and responsibilities of the Offeror’s team, to include

Subcontractors and teaming partners.

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

At a minimum, the Offeror shall define and describe:

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

SOW.

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

• Stakeholder Management: Shall define the Offeror’s plan to manage and communicate with the multiple

Marine Corps Stakeholders throughout the contract.

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

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

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

• Management Plan and Staffing Approach in the event of Simultaneous Orders: Since each order under this multiple award IDIQ effort will be awarded based on the fair opportunity procedures outlined at FAR

16.505, the possibility exists that a single vendor may be awarded, and be required to perform, multiple task orders simultaneously. The Offeror shall explain its plan for how it will manage and staff multiple, simultaneous orders of different scopes, in multiple, geographically dispersed locations.

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

Offerors shall submit CDRL B005 Project Management Plan with this section. The CDRL submission shall be not more than 10 pages but will be outside of the page count identified in Table 2 above.

9.2 Volume I, Section 3.2 - Overarching Staffing Plan

The Offeror shall provide an overarching staffing plan for onboarding, retention, and off boarding of personnel throughout the ordering period. At a minimum, the Offeror’s plan shall include the following:

• The staffing plan shall indicate notionally, if the Prime or Subcontractor will perform the SOW requirements.

• The Offeror shall show all labor categories, and labor categories descriptions anticipated to be performed under each of the SOW requirements. Labor categories, and labor categories descriptions shall be excluded from the page count listed in Table 2 above.

• The staffing plan shall address the plan to recruit and retain employees to fill all positions required.

The Offeror shall include the approach used to manage all Subcontractors, regardless of company size, in the staffing plan. Include a description of the core capabilities provided by each of its teaming partners and

Subcontractors.

9.3 Volume I, Section 3.3 - Management Tools, Governance, and Partnering Approach

The Offeror shall describe, using Base IDIQ SOW requirements, the application of proactive and predictive management tools and techniques to plan and manage the required effort. The Offeror shall include a description of their approach to implementing transparent governance and reporting, a sound partnering approach grounded on shared goals and objectives, and proactive problem identification and resolution. This information shall describe the

Offeror’s ability to ensure the logistics management oversight necessary to deliver effective operational capabilities in Continental United States (CONUS) and Outside Continental United States (OCONUS) in support of ISTC’s projects across multiple DOs.

9.4 Volume I, Section 3.4 – PDO Staffing Plan

The Offeror shall provide a realistic labor mix profile for the initial PDO, noting proposed labor categories, labor category descriptions, and labor hours to be performed with regard to requirements identified in the PDO SOW. At a minimum, the Offeror’s plan shall include the following:

• A table containing a description of the labor categories, mix of skills proposed, and the associated labor hours to perform the requirements identified in the PDO SOW at each place of performance needed during the time frame required by the PDO. This table shall also identify which labor categories are designated as key personnel. This table shall be excluded from the page count listed in Table 2 above.

• The Offeror shall indicate notionally, if the Prime or Subcontractor will perform the specific tasks identified in the PDO SOW; if the work will be performed by Subcontractors, include a description of the core capabilities provided by the subcontractor(s).

• The Offeror shall include the approach used to manage all Subcontractors, regardless of company size, in the staffing plan.

• For unfilled positions, the staffing plan should address the current status of effort to recruit employees to fill all positions required to accomplish the PDO tasks.

The Offeror shall include a list of all proposed Subcontractors with a proposed subcontract value estimated at $10 million or more, to include the following information: Company name, address, individual’s name/point of contact, and telephone number.

10. Volume II, Section 4, Factor 3 – Past Performance

10.1 Volume II, Section 4.1 - Recent and Relevant Past Performance

The Offeror shall submit a maximum of three (3) recent and relevant summaries of past performance similar in size, scope, and complexity to this requirement. "Recent" is defined as an effort, whether ongoing or completed, occurring during 5 years preceding the solicitation closing date. "Relevant" past performance would be a recent effort accomplished by the Offeror with a similar scope and complexity as the PDO described in this solicitation.

“Relevant” past performance is defined as a recent effort accomplished by the Offeror with a similar scope and complexity with a minimum total value of $5 million. The Offeror must submit dollar amounts of the effort actually performed by the company for which the past performance effort is being submitted.

Task or delivery orders awarded under single-award IDIQ or Multiple-Award Contracts (MACs) will be considered standalone “contracts” for purposes of past performance evaluation. Thus, Offerors shall not propose an entire IDIQ or MAC as a past performance contract reference.

The Offeror shall include all requested data that illustrates the adequacy of the Offeror’s (or principle

Subcontractor’s) various contracts selected to convey recent and relevant past performance. For each contract identified, the Offeror shall provide the following information:

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

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

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

Representative (COR).

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

Subcontractors’ past performance.

o The Offeror’s past performance:

▪ In the delivery of quality supplies/services, which includes meeting technical requirements.

▪ In meeting schedule requirements, to include on time or late deliveries, and modifications of original schedules.

▪ In managing the contracted effort, to include program management, subcontract management, and cooperation with the customer.

▪ In meeting any identified Acceptable Quality Levels or minimum thresholds of performance.

▪ If applicable, describe any improvements made during performance or efforts taken to resolve problems or issues related to performance requirements. For each problem or improvement identified, describe how it was resolved or implemented and, where applicable, demonstrate the impact that the improvement effort had on resolving or preventing the recurrence of systemic problem.

The identified contracts shall be with Department of Defense or other Federal agencies. Past performance as a

Prime, teaming partner, or as a Subcontractor will be considered, as will past performance by a company proposed as a Subcontractor to this effort. However, past performance by the Offeror as a Subcontractor may be less relevant to the overall past performance rating than past performance by the Offeror as a Prime Contractor.

For each past performance example submitted, the Offeror shall provide a Past Performance Questionnaire (PPQ)

(Attachment 11). PPQs will not count against the page limitations identified in the Proposal Outline Table in

Section 7. The Offeror shall send out, and track the completion of, the PPQ to each of the Offeror’s Government

Points of Contact. Any completed PPQ must be submitted directly to the Contract Specialists Mr. Todd Ingold at todd.ingold@usmc.mil and Ms. Monet Payne at monet.l.harrison@usmc.mil with a copy to the Contracting Officer

Ms. Morgan Brady at morgan.brady@usmc.mil no later than 3:00 pm Eastern Time (ET) on July 11, 2023. It is incumbent upon the Offeror to explain the relevance of data provided in its proposal. The Government has no duty to search for additional data to fill gaps the Government finds in the information provided by the Offeror.

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

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

The Government reserves the right to use contract performance data provided in the Offeror’s proposal and contract performance data obtained from other sources, including but not limited to, CPARS, the Government’s Excluded

Parties List System (EPLS), and the Specially Designated Nationals (SDN) List.

11. Volume III, Section 5, Factor 4 – Proposed Delivery Order Pricing

11.1 Volume III, Section 5.1 –Pricing Workbook (Attachment 10)

Offeror’s proposal is presumed to represent its best efforts to respond to this solicitation. The burden of proof as to price credibility rests with the Offeror. Unreasonably low prices may indicate an inability to understand requirements and a high-risk approach to contract performance. The Government reserves the right to conduct a price reasonableness determination to determine whether an Offeror’s proposed prices are realistic for the work to be performed. The Government may consider the findings of such an analysis in evaluating an Offeror’s ability to perform and the risk of its approach.

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

Government.

The submission of pricing (Attachment 10) in accordance with the instructions shall, if accepted by the Government, contractually bind the Government and the Offeror to the terms and conditions of the model contract. The Offeror shall prepare and submit the cost/price proposal narrative substantiation and rationale in Adobe Acrobat format and any numerical data in Microsoft Excel format. Offerors shall not alter the format of the spreadsheets (Attachment

10) except that column(s) and row(s) may be widened or added as needed. However, for Travel/ODC costs, offerors may adjust the formula if necessary but shall include all formulas, functions, computations, or equations used to compute the proposed amounts.

The price proposal shall be submitted via Attachment 10: Pricing Workbook. The pricing proposal submitted via

Attachment 10 for the proposed delivery order shall be the basis for the Government’s price evaluation for this solicitation. The Offeror shall submit pricing for every line item in Attachment 10; failure to do so may result in the proposal being ineligible.

mailto:todd.ingold@usmc.mil mailto:monet.l.harrison@usmc.mil mailto:morgan.brady@usmc.mil

The Offeror is advised that these workbooks may be redacted to remove pricing for review by the technical evaluators. The Offeror is additionally advised that the proposals should not include a breakout of proposed costs as an ODC, which are a typical cost of doing business, such as cell phones, teleconference costs, office supplies, and local travel.

(End of Summary of Changes)