Section L_Attachment 00A.pdf

H92254-25-RE-001

Section L_ Attachment 00A

Section L – Instructions to Offerors

L.0 Overview

L.0.1 General Requirements

Each offeror intending to submit a proposal in response to this solicitation shall notify the Contracting Officer via e-mail Brian.C.Hubbs.civ@socom.mil and Michael.T.Geegan.civ@socom.mil within 10 days of Request for Proposal

(RFP) issuance. This is an all-electronic solicitation release. No hard copies of the solicitation will be mailed.

Amendments to the solicitation will be posted to www.SAM.gov. The offeror is responsible for reviewing the webpage for notice of amendments, updates, or changes to current information. A proposal may include data, such as technical designs or concepts, financial data, or management plans that the Offeror does not want disclosed to the public for any reason or used by the Government for any purpose other than proposal evaluation and contract award.

If the Offeror wishes to restrict the proposal, the Offeror shall mark it in accordance with FAR 52.215-1 (e). In accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain all electronic proposals and supplemental documents provided to the Government. Proposals shall be unclassified and will be treated as

Source Selection Information (see FAR 2.101 and 3.104). Classified information will not be accepted and will be returned to the offeror.

L.0.1.1 Clarity & Completeness

It is the Offeror’s responsibility to draft a logical, practical, clear, and concise proposal that contains all pertinent information in sufficient detail so that the Government evaluators are able to meaningfully evaluate the Offeror’s proposed approach. Proposals must be complete, self-sufficient, and respond directly to the requirements of the solicitation. Any significant inconsistency, if unexplained, raises a fundamental issue with the offeror’s understanding and ability to perform the contract. This may be a basis for rejection of the proposal. In no case shall words like, “we will comply with the requirements of the contract” or equivalent statements be acceptable to meet all the requirements of this RFP. However, the proposal shall include a declaration statement that acknowledges and accepts, without exceptions, all performance work statement (PWS) requirements. Failure to comply with these instructions may result in an offeror’s proposal being excluded from further consideration for award.

L.0.1.2 Cover Letter

The offeror shall submit a cover letter with the proposal that includes a list of names and telephone numbers of persons authorized to conduct negotiations as well as names and telephone numbers for the cognizant Defense

Contract Management Agency (DCMA) Contract Management Office and Defense Contract Audit Agency (DCAA) office for the business unit proposed.

L.0.1.3 Restriction to Prime Offerors Only

Offerors are advised that proposals will only be accepted from those Offerors proposing as potential prime contractors. Such Offerors shall be responsible for submitting complete proposal packages containing all components of the proposal inclusive of any team member or subcontract proposal information. Pricing data, or other information which may be considered proprietary to team members or subcontractors, shall be submitted with the prime contractor’s proposal. If a subcontractor’s proposal must be submitted apart from the prime offeror’s, it can be provided separately on the offeror’s appointed date. It is the prime offeror’s responsibility to ensure that the subcontractor’s proposal is IAW the instructions contained in Section L.

L.0.1.4 Proposal Preparation

Offerors shall submit their proposal in five (5) separate volumes, organized as described below.

a. Volume 1 - Technical (Factor 1) shall be prepared in accordance with these instructions and will be evaluated in accordance with the evaluation criteria in Section M, Evaluation Factors for Award. Proposals shall include necessary information to enable the evaluators to form a definitive conclusion concerning the offeror’s mailto:michael.hawkins4@socom.mil ability to perform the required support. The Technical volume shall be organized in tab format in the order listed in this Section L and submitted IAW L.0.2 and L.0.2.1.

b. Volume 2 - Past Performance (Factor 2) shall be prepared in accordance with these instructions and will be evaluated in accordance with the evaluation criteria in Section M, Evaluation Factors for Award. The Past

Performance volume shall be submitted IAW L.0.2 and L.0.2.1.

c. Volume 3 - Task Order Management (Factor 3) shall be prepared in accordance with these instructions and will be evaluated in accordance with the evaluation criteria in Section M, Evaluation Factors for Award.

The Task Order Management volume shall be submitted IAW L.0.2 and L.0.2.1.

d. Volume 4 - Task Order Cost (Factor 4) shall be prepared in accordance with these instructions and will be evaluated in accordance with the evaluation criteria in Section M, Evaluation Factors for Award. The Task

Order volume shall be submitted IAW L.0.2 and L.0.2.1.

e. Volume 5 - Administrative Criteria shall be prepared in accordance with these instructions and will be provided to the Contracting Officer and utilized as part of the separate determination of Contractor responsiveness and responsibility IAW FAR 9.104-1. The Administrative Criteria volume shall be submitted

IAW L.0.2 and L.0.2.1.

Specific details about page limitations and the required numbers of copies for each volume is contained in Section

L.0.3.2 below.

L.0.2 Proposal Delivery Requirements

Offerors should note that Physical proposal submission is the only acceptable form. Offerors who intend to submit a proposal shall first request a delivery appointment by emailing the Contracting Officer, Brian.C.Hubbs.civ@socom.mil NLT 1400 Eastern Daylight Time (EDT), on 29 October 2025. Proposals of

Offerors that fail to schedule a delivery appointment by NLT 1400 EDT, on 29 October 2025, will not be accepted.

Submit proposals to:

PEO SOFSA

ATTN: H92254-25-R-0001; Brian Hubbs

5751 Briar Hill Road

Lexington, KY 40516

L.0.2.1 Delivery Appointments

The Government will schedule delivery appointments to accept physical proposals the week of 17-21 November

NLT, with the last available delivery appointment time occurring at 1330 EDT on 21 November 2025 to ensure all proposals are received by 1400 EDT that day. If, due to unforeseen circumstances, an Offeror is unable to attend its assigned proposal delivery appointment, the Government will accept proposals up to, but not later than, 1400 EDT on 21 November 2025. In such an instance, the Offeror shall email the Government POCs at L.0.2 to establish a new drop-off time to occur before 1400 EDT on 21 November 2025.

The proposal delivery appointment request shall include:

• Company Name and Cage Code

• One Company Point of Contact (POC) responsible for delivering the proposal to the USG, and their respective contact information, to include email address and phone number

• Requested delivery appointment date and time: between 17 and 21 November NLT 1330 Eastern Daylight

Time

• One Company Point of Contact (POC) to receive the “confirmation of delivery appointment” email and their respective contact information, to include email address and phone number mailto:Brian.C.Hubbs.civ@socom.mil

• The Government will reply with delivery appointment confirmation emails on 31 October 2025 NLT 1500

EDT.

On the date of the delivery appointment, each offeror shall submit its proposal on a DVD-R disc in person at

Bluegrass Station Lexington, KY as noted on the SF33. Re-writable media will NOT be accepted and will be returned to the offeror.

Upon receipt, the Government will upload to a disconnected network (airgap) for virus scan and then move the documents to government systems for evaluation.

** PROPOSALS SUBMITTED THROUGH OTHER MEANS WILL NOT BE ACCEPTED. **

L.0.2.2 Proposal Delivery Package Markings

Offerors are directed to clearly mark the description for each document by Offeror Name, Solicitation Number and

Volume number. If there is more than one file/section per Volume due to file size, clearly mark the description for each file/section by X of X Volume number files. If proposals are submitted as encrypted, the encryption passphrase shall be written on the disc submitted or provided on a separate piece of paper at the time of submission. Proposals submitted will be considered late unless all proposal documents are successfully transmitted in DVD-R disc format, to include any passphrase, prior to the closing date and time for receipt of proposals (See Block 9 of the SF33). The

Government is not responsible for technical difficulties associated with the transmission of any electronic files.

The Offeror is responsible for ensuring the successful delivery of its proposal. Proposals are valid for at least 180 days beyond the due date set for receipt of proposals. Offerors shall include an affirmative statement clearly articulating that offers, to include pricing and/or cost, are valid for at least 180 days beyond the final due date of 21 November 2025. Late proposals shall be rejected from consideration. If any proposal is received late, the KO will promptly notify the Offeror that its proposal was received late.

L.0.2.3 Virus Scan Requirements

The Government will airgap and perform a virus scan on all DVD-Rs provided by the offeror. Any submittal failing the virus scan shall not be considered and will not be reviewed further.

L.0.3 Proposal Organization & Formatting Requirements

L.0.3.1 Required Format

Format of the proposal volumes shall be as follows:

• At a minimum, each Volume shall be submitted as a separate file. Within each Volume any subfactors shall be separated into individual chapters. Text size shall be no smaller than what is equivalent to Microsoft Word, Times New Roman, 11-point, uncompressed font.

• Pages (to include Cover Pages) shall be one and one half spaced, with a minimum of one-inch margins on all sides. The offeror’s name, volume, subfactor, and page number shall be on each page in the footer.

• Text size and spacing requirements do not apply to header and footer text.

• Pages shall be dated and numbered sequentially by volume. All documents identified in L.0.3.4 as excluded from the identified Volume page count shall be provided at the end of the applicable Volume and distinguished by adding “unlimited” after the page number.

• Proposal table of contents, cover page, acronym lists, compliance matrices, and tab dividers are not included in the page count.

• Elaborate format and color representations are not desirable. Any pages that are changed (as the result of discussions) should have changed information clearly marked by a vertical line in the right margin of the page and/or circling if changing data in a chart. The offeror shall indicate the new date on revised pages.

https://safe.apps.mil/

• Legible tables, charts, graphs and figures shall be used when necessary to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, may be single spaced, and shall not exceed 11 by 17 inches in printable size. These displays count as two pages. These displays may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text.

For tables, charts, graphs and figures, the text shall be no smaller than 8-point Arial font.

• The Offeror shall submit all volumes in electronic format (uncompressed), readable and usable by Adobe

Acrobat or the Microsoft Office 2016 suite (MS Word, MS Excel, Project, and PowerPoint), unless otherwise specified in the RFP. Hidden fields, comments, macros, etc., shall be omitted. If a spreadsheet is submitted, submit a locked version and an unlocked version. Original documents created in Microsoft

Word, Excel, or equivalent shall be the actual workable documents. Scanned Portable Document Formats

(PDFs) and scanned images are acceptable in those instances where no other format is available to the offeror. All Microsoft Excel files shall be completely readable and editable with formulas visible and traceable, as to ascertain the validity of the pricing or other data contained therein. All data and tables shall be in a printable format. All Adobe Acrobat files shall be word searchable. The files shall be consistent and uniformly named to allow for easy distinction by Solicitation Number and Volume, inclusion of company name or abbreviation is acceptable.

L.0.3.2 Markings

The Offeror shall mark each page of its proposal with “Source Selection Information – See FAR 2.101 and 3.104”.

Note that the Offeror has an independent requirement to mark anything deemed to be bid or proposal information, protected proprietary information, or other information that is to be protected from disclosure to ensure that the information is protected. The proposal and corresponding program will be unclassified and treated as Source

Selection Sensitive Information. Additionally, the Offeror shall mark each applicable page of its proposal with

“Controlled Unclassified Information (CUI)” that contains CUI information.

L.0.3.3 Cover Page and Table of Contents

Each volume shall contain a cover page and table of contents.

Cover Page: The cover shall indicate the following:

• Proposal Title

• Solicitation Number

• Proposal Volume

• Offeror Name and Address

• Principal Point of Contact Name and Phone Number

• CAGE Code/ SAM UEI

• DCMA/DCAA Point of Contact Name and Phone Number

Table of Contents:

• The table of contents shall provide sufficient detail as to allow the important elements to be easily located.

L.0.3.3 Completeness/Standalone Response

Offeror shall provide an independent response for each Subfactor. Information provided in one factor and subfactor response WILL NOT be considered in a differing factor OR subfactor response (even if that subfactor is in/under the same factor). Each subfactor response is a standalone response and will be evaluated based upon the information provided in that subfactor ONLY. Example: Information in factor 1 that is relevant to both subfactor 1 and 2 must be contained in Both subfactor 1 and 2 chapters (duplication of information). If subfactor 2 references information that is contained in subfactor 1, that information will NOT be evaluated under subfactor 2 because it is not contained in the subfactor 2 chapter. However, conflicting information across factors may be assessed as increased risk of unsuccessful contract performance.

L.0.3.4 Volume Contents & Page Limitations

Proposal Submission and Preparation:

Proposal Submissions Factor

Electronic

Copies Per

Volume Number of Pages

Volume 1, Technical Factor 1 1 40 max + Key management personnel resumes +

Letters of Commitment

Management Organizational Structure and Business Processes Subfactor 1

Teaming Arrangements and Small

Business Participation Subfactor 2

Phase-In Transition Subfactor 3

Volume 2, Past Performance Factor 2 1

50 max + ISRs + Consent Letters + Explanation if required + Organizational Structure Change

History

Volume 3, Task Order Management Factor 3 1 10 max TO Management Approach + 30 max PWS

+ resume per subfactor

Task Order 1 Subfactor 1

Task Order 2 Subfactor 2

Task Order 3 Subfactor 3

Volume 4, Task Order Cost Factor 4 1

20 max (Executive Summary all subfactors) + RFP

Attachment 10 + RFP Attachments 11a-c +

FPRA/FPRR/FPRP + Disclosure Statement excerpts

Task Order 1 Subfactor 1

Task Order 2 Subfactor 2

Task Order 3 Subfactor 3

Volume 5, Administrative Criteria N/A 1 No Limit (20 Max SCRM, 20 Max Data

Management)

L.0.3.5 Incurred Expenses

The Government shall not be responsible for any costs incurred or associated with preparation and submission of a proposal in response to this solicitation. No offeror will be compensated for submitting a proposal.

L.0.4 Questions

The Offeror may submit written questions requesting clarification of RFP requirements. The Offeror shall submit questions related to this RFP electronically to the persons listed below. Telephone inquiries will not be accepted.

TO: Brian Hubbs (Contracting Officer) at Brian.C.Hubbs.civ@socom.mil and Michael Geegan (Contract

Specialist) at Michael.T.Geegan.civ@socom.mil

SUBJECT LINE: Question (insert name of Offeror) RFP H92254-25-R-0001 (GLSS2)

All questions must be submitted in writing using the format and contents of RFP Attachment 12, Q&A Template to ensure accurate responses. Prime offerors should consolidate questions from their team members and submit as one submission to the maximum extent practicable. Any questions received after the below requested due date may not be answered prior to the RFP closing date. Responses to questions will be provided to all the interested Offerors.

It is requested that all contract/administrative and technical related questions be received NLT 1700 EDT on 9

October 2025.

L.0.5 Use of Artificial Intelligence (AI) tools in Proposal Evaluation

The Government reserves the right to employ AI as a tool to assist in the analysis and review of proposals to support tasks such as summarizing proposal content, assist in identifying compliance with request for task order proposal / solicitation requirements, and assist in identifying areas of potential strength, weakness, or risk. All evaluation ratings decisions, best value determinations, and source selection decisions will be made exclusively by Government personnel. The Government retains sole responsibility for all inherently governmental functions and will not delegate decision-making authority to any AI tool. The AI tools utilized by the Government will be employed in a manner consistent with applicable statutes and regulations that govern the protection of proprietary and source selection sensitive information. No proposal data will be transmitted to or processed by external, non-Government systems.

L.1 VOLUME 1 – Factor 1 – Technical

L.1.1 Subfactor 1: Management Organizational Structure and Business Processes.

L.1.1.1 Approach

The offeror shall provide a concise summary of the approach, proposed organizational structure, and team for meeting the requirements of the SOF GLSS2 effort. The offeror shall demonstrate an understanding of the organization, logistics, sourcing, management expertise, and business processes required by this solicitation. At a minimum, the offeror shall address the following and, when viewed collectively, demonstrate its ability to successfully execute the requirements in the solicitation:

• Identify each organizational element with explanatory rationale and defined responsibilities in support of the requirements in the PWS, including locations of key management personnel and how these personnel will have the ability to manage all task order pre-award functions through contractually binding the offeror, while simultaneously managing the performance of existing orders, Enterprise functions, and General

Management Requirements (PWS 4.2 and 4.3). Describe how your organization intends to interface with

Government personnel at various levels, specifically addressing the PEO SOFSA organization with clear lines of responsibility and authority for controlling (including officials authorized to contractually bind the offeror as it applies to Task Orders), reporting, and reviewing work to ensure successful contract performance.

• Describe how your organization intends to ensure an enterprise mindset vice stove-pipe task order solution is presented to the Government across all team members and levels within the organization.

• Describe your understanding of the type of equipment and services to be provided, existing programs and customers supported, and your ability to effectively manage multiple customer requirements at times utilizing the same workforce.

• Describe your processes to train new and existing employees to ensure initial capability and continued technical expertise as technology advances and policies change throughout the contract period of performance.

• Describe how you would maintain the required technical expertise and workforce as program support requirements (PWS 4.1) ebb and flow without impacting the level of performance for existing efforts or unreasonably driving up costs.

• Describe how you plan to interface with and utilize the Government-owned business and automation systems IAW PWS 4.2.5 and PWS Appendix A, B, and C.

• Describe how you plan to efficiently manage material sourcing, how remaining or excess contractor acquired material/property from Task Orders will be utilized more efficiently to benefit the government and minimize excess property onsite.

L.1.1.2 Enhancements

The Government encourages enhancements in the offeror’s proposal. The Government desires the focus of enhancements to be in the areas of warehouse modernization and automation (utilizing Enterprise Logistics

Management System (ELMS) (previously known as Defense Property Accountability System (DPAS)) as the mandated Accountable Property System of Record (APSR) for USSOCOM), supply chain risk management, data management and business intelligence, and the use of artificial intelligence tools and applications. The enhancements should be focused on transparency, increased automation of processes, enhancement of (or new) automation systems, gaining efficiencies through increased enterprise-focused business processes that would be of benefit to performance, and providing more accurate and actionable data. Identify any enhancements involving

Government-owned business and automation systems that you plan to provide after the contract transition period that would be of benefit to the Government, improve contract performance IAW PWS Sections 4.2.5 and 7.1, and assist the Government with process automation and technological advancement of these systems.

Offerors are also encouraged to propose enhancements for areas not specifically identified in this section. For all enhancements proposed, the offeror shall include the resource implications (i.e. manpower, time, logistics, etc.)

except for cost and clearly articulate the benefit to the Government. The offeror shall propose updated contractual language (e.g. for the PWS, Section H) as appropriate to implement the enhancement. Associated cost implications shall be reflected in Volume 4 with linkage back to the Volume 1 section where the proposed enhancements are described. By submission of its proposal, offerors expressly consent to the incorporation of any proposed enhancement that is evaluated as a Strength as a requirement in the resultant contract.

L.1.1.3 Key Management Personnel

The offeror shall provide information regarding their proposed key management positions, including identification of the key management positions and the corporate and personal commitment of providing proposed candidates to identified positions. For each proposed key management position candidate, the offeror shall include a resume (2-page limit) and a letter of commitment that includes the following information:

• Management experience on other relevant contracts

• Length of time employed with current employer

• Technical competency to include familiarity with DoD policies and procedures (PWS 4.3.2)

• Specific examples of knowledge and skills in interfacing with people at all levels including problem solving capability

• Education and training

The resumes submitted will become the baseline for the addition or substitution of Key Personnel (SOFARS

5652.237-9001) upon contract award. The PWS will be updated to reflect key personnel awardee information.

L.1.2 Subfactor 2: Teaming Arrangements and Small Business Participation.

The offeror shall describe its management approach to interact with, allocate work to, and simultaneously exercise oversight/control over subcontractor cost, schedule, and performance of multiple teaming partners. The offeror shall list by team member (both large and small businesses; for small businesses include the socio-economic category(ies) for each entity) the types of tasks projected to be subcontracted, clearly outlining program support coverage in the three Core Competencies described in PWS 4.1: Streamlined Design and Rapid Prototyping; Production, Modification, and Integration; and Lifecycle Sustainment Activities across all major platforms and programs.

Additionally, address those Enterprise functions and General Management Requirements described in PWS 4.2 and

PWS 4.3) that you find key to the makeup of your individual team. The offeror is not required to address every functional area of expertise required under the PWS but should address all key areas to show the overall team’s capabilities and demonstrate an understanding of the requirements.

The offeror shall include the following within this subfactor (*NOTE* the NAICS code of 561990 pertains to the prime offeror. The offeror will then be able to determine their subcontractors and the NAICS code for the work that the subcontractor will be performing):

• Describe your corporate commitment in providing subcontracting opportunities for small business, small, disadvantaged business, women-owned small business, HUBZone small business, veteran-owned small business, and service-disabled veteran-owned small business concerns.

• Describe the strength and specificity of each corporate commitment (i.e. what type of commitment, how binding the commitment is, how specific the commitment is to this proposed effort, and what type of work will be included in these subcontracting opportunities from the overall corporate level).

• Address the process for vetting new supply sources, existing partnerships, and reach-back capability used to acquire additional team members and/or supply sources as required over the period of performance.

The offeror shall include a discussion on how it will assess the technical and contractual requirements of solicited tasks, determine the most effective allocation of effort among prime and subcontractors/team members, and submit quality task order proposals in the standard and quick reaction timeframes as outlined in Section H.5.

This subfactor is separate from the Individual Subcontracting Plan required by FAR 19.702(a)(1) and Volume 5, Administrative Criteria and the acceptable purchasing system required by DFARS 244.305-70.

L.1.3 Subfactor 3: Phase-In Transition

The offeror shall provide a phase-in transition plan that describes its overall management approach for transition.

The plan shall address the offeror’s capability to execute a smooth and turn-key phase-in transition leading to assumption of full responsibility for all areas of the operation as defined in PWS 7.0 and its subsections. The plan shall include identification of management expertise, ability to meet all security requirements (facility and personnel), procedures and processes, risk mitigation techniques, flexibility, and ability to identify and satisfy site specific requirements prior to personnel deployment to OCONUS locations that, when viewed collectively, demonstrates the offeror’s ability to successfully execute a contract phase-in transition while minimizing impacts to

SOF users. The plan shall also include the offeror’s strategy to phase-in the Enterprise functions (PWS 4.2) and ensure a no-fail transition of these key efforts as it assumes full responsibility within the required timelines (PWS 7).

The plan shall explain how each activity would be assured of timely completion, identify the offeror’s phase-in transition management team, describe the offeror’s approach for interfacing with the incumbent contractor, and describe the offeror’s capability to effectively partner with the Government team. The plan shall also include a timeline that graphically supports the narrative and highlights key milestones that demonstrate an understanding of the requirements necessary to assume full contract responsibilities following contract award.

L.2 VOLUME 2 – Factor 2 – Past Performance

L.2.1 Contents & Organization

The offeror shall submit a Past Performance Proposal (Volume 2) containing the following:

• Table of Contents

• Summary Page describing the role of the offeror and each subcontractor, teaming partner, and/or joint venture partner for which the offeror is required to provide Past Performance Information Sheets in accordance with paragraph L.2.2 below.

• Past Performance Information Sheets for Prime Contractors (paragraph L.2.2.1 below).

• Past Performance Information regarding Subcontracting (paragraph L.2.2.2 below) and Small Business

(L.2.2.3).

• Consent Letters executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of past performance information so the offeror can respond to such information. If applicable, offerors must include Client Authorization Letters for each identified effort performed for a commercial customer, authorizing release to the Government of requested information on the offeror’s performance.

**Excluded from page limit for Volume 2**

• Organizational Structure Change History (paragraph L.2.4 below). **Excluded from page limit for

Volume 2**

L.2.2 Past Performance Information Sheets

The offeror shall submit information on contracts it considers most recent and relevant in demonstrating its ability to perform the proposed effort. The offeror shall submit a maximum of five and a minimum of three Past Performance

Information Sheets identifying active or completed contracts, either Government or commercial, for the prime and a maximum of two and a minimum of one Past Performance Information Sheet for each major subcontractor. The

Government does not anticipate a single prime offeror will have the capability to perform, nor has performed in the past the entire scope of the effort on its own. Therefore, “major” is defined as those subcontractors who the offeror feels are key to demonstrating its ability to perform the entire scope of the proposed effort. No more than four separate major subcontractors may be submitted.

In accordance with FAR 15.305(a)(2)(vi), for those offering as joint ventures, the evaluation shall take into account past performance of the joint venture. If the joint venture cannot demonstrate past performance for award, the contracting officer will consider the past performance of each member of the joint venture. In that event, each member of the joint venture is required to submit at least one Past Performance Information Sheet as the prime. If the joint venture has more than five members, then the offeror shall be allowed to submit one Past Performance

Information Sheet for each member exceeding the five-submission limit.

Past Performance Information Sheets for each prime contractor are limited to five pages and for each major subcontractor to three pages (does not include Individual Subcontracting Reports (ISRs) or consent letters). Offerors are advised that the Government will use the information provided by each offeror in this volume as well as information obtained from other sources for the overall evaluation of past performance. The Government requests the offeror provide references including current Points of Contact (POCs) for each contract identified. Contact information for each POC and reference shall include both a telephone number and email address.

The Government has provided a Past Performance Questionnaire (PPQ) template as RFP Attachment 14. The offeror is encouraged to kindly request the POC to complete the PPQ and have them submit it directly to the

Government via email to Brian.C.Hubbs.civ@socom.mil and Michael.T.Geegan.civ@socom.mil no later than one week prior to the proposal submission due date and time. The email subject line for the PPQ submission shall be:

'PPQ Submission for [Offeror Name] - Ref: [Contract Number]'. PPQ data is an important part of the Government’s

Past Performance Evaluation, however, Offerors are not required to provide as part of their proposal submission.

L.2.2.1 Prime Contractors

Past Performance Information Sheets shall include specific information for each effort regarding experience in accordance with the following areas outlined below. NOTE: If the experience in the following areas was not required under the referenced contract the offeror shall indicate that it was not applicable on the Past Performance

Information Sheet.

For each submitted prime offeror effort offerors should:

• State whether the prime offeror was the prime contractor or subcontractor for that effort. If not the prime contractor for the effort, all information should be reflective of what was actually performed as a subcontractor rather than what was required of the overall team.

• Identify contract number, contract type, ceiling value (if applicable), current value (awarded tasks/exercised options), Government or commercial organizations supported, the period of performance (POP), the number of task orders awarded by year for each year of the POP (if applicable), and the number of

Government task order requests for proposals for which proposals were submitted but not awarded by year for each year of the POP (if applicable).

• Describe the overall scope of the effort and how it relates to the Core Competencies of the SOF GLSS2

PWS: Streamlined Design and Rapid Prototyping; Production, Modification, and Integration; and Lifecycle

Sustainment Activities.

• Describe performance in recruiting, hiring, training, and retaining large numbers of personnel (include number of employees) requirements.

• Show management of multiple subcontractors/teaming partners (include number managed) to include price negotiations, resolving performance issues, and demonstrating use of cost controls.

• Show management of a geographically diverse workforce located primarily in Government facilities, specifically annotating if OCONUS support was required.

• Show management of a GOCO-type or commercial operation with similar Enterprise management and logistics operations requirements.

• Describe experience in accessing internal and external team resources that were necessary to provide support for a wide scope of requirements to include multi-level security requirements, specifically citing what the security level required was for both facility and personnel.

• If enhancements had been proposed under that effort, explain if they were or were not successfully implemented, and if implemented, describe the benefits received by the Government or commercial organization.

• Describe how the ebb and flow of requirements were effectively overcome, specifically citing how the effort was still maintained.

L.2.2.2 Subcontractors

For each submitted major subcontractor effort, offerors should:

• Describe what effort(s) that major subcontractor will be performing in support of the prime offeror under this contract.

• Describe if they were the prime contractor or subcontractor for that effort. If not the prime contractor for the effort, all information should be reflective of what was actually performed as a subcontractor rather than what was required of the overall team. identify current contract value (awarded tasks/exercised options), Government or commercial organizations supported, and the period of performance (POP).

• Describe the overall scope of the effort and how it relates to the specific area(s) in the PWS the major subcontractor is proposed to actually perform under this contract.

• Any additional information the offeror finds necessary to demonstrate the overall team capability

L.2.2.3 Small Businesses

The offeror shall demonstrate its corporate commitment to meeting its subcontracting goals/targets for individual contracts by providing the most current Individual Subcontracting Report (ISR) or equivalent for individual contracts/projects submitted under Past Performance. The ISRs are excluded from the Volume 2 page count. Small

Business offerors are exempt from this requirement.

If goals were not met on the ISRs, the offeror shall provide an explanation as to why the goals were not met.

If an ISR was not required due to size status as a small business under the contract(s) submitted, then the offeror shall include a valid explanation with detailed information.

L.2.3 Recency & Relevancy

L.2.3.1 Definitions

General definitions of recent and relevant are as follows:

• Recent Contracts. The Government defines “recent” as contracts that have been performed during the past seven years from the date of issuance of this solicitation.

• Relevant Contracts. Relevancy will be determined based on contract references reflecting recent (within the past seven years) past performance.

For the prime offerors, relevancy is defined as contracts that are most similar to this overall effort described in this solicitation in terms of scope, magnitude, complexity and require similar organizational structures, management expertise, and business processes required by this solicitation. Table 2 below outlines the criteria the Government will consider in determining relevancy (for prime offeror efforts only). The more an effort is similar in these areas, the more relevant that effort becomes.

L.2.3.2 Evaluation Criteria for Relevancy

No formal weights exist for the individual relevancy criterion and overall criteria, but rather all criterion are considered holistically to subjectively assess one overall relevancy rating (per the definitions in Table 3) for each prime offeror effort. While individual criterion may involve objective measurements (e.g., contract value thresholds, number of personnel), the overall relevancy determination for each contract reference remains a holistic, subjective assessment. A prime offeror effort does not have to be “Very Relevant” in all criteria to be determined “Very

Relevant” overall. Additionally, a prime offeror effort could hypothetically be “Not Relevant” in one or more criterion and still be determined “Somewhat Relevant” or higher for that effort overall.

SECTION L – Table 2. Past Performance Relevancy Criteria Baseline

Section L.2.3.2 Very Relevant Relevant Somewhat Relevant Not Relevant

Scale and

Complexity of

Subcontractor

Management

Requires extensive program management experience;

Required to manage subcontracting requirements where the total value was greater than or equal to

30% of the contract value and included over 20 subcontractors, suppliers, and/or partners

Requires extensive program management experience;

Required to manage multiple

Subcontracting requirements.

Required to manage some Subcontracting requirements

Not Required to manage

Subcontracting requirements

Formal Small

Business (SB)

Subcontracting Plan

SB plan required;

Included small business subcontracting goals or mandates of 25% or higher of total

SB plan required;

Included specific small business subcontracting goals or mandates of any amount

SB plan required but no goals or mandates included and/or

Commercial SB plan acceptable

No subcontracting opportunities and/or

SB plan not required subcontracted dollars

Awarded Contract

Value

(not just ceiling value)

$400M+ in a 365-day period

$301M-$399M in a

365-day period

$250M-$300M in a

365-day period

Less than $250M in a 365-day period

Contract Type Single Award

IDIQ where the most used pricing arrangement for

DO/TOs is more than 50% cost-reimbursable (FAR

16.3)

Single Award IDIQ where the most used pricing arrangement for

DO/TOs is more than 50% fixed price (FAR 16.2)

Multiple Award

IDIQ with fixed-price (FAR 16.2) and some cost-reimbursement

TO/DO pricing arrangements (FAR

16.3)

Not IDIQ and/or all fixed-price (FAR

16.2)

Contract Type

(Services, Supply, R&D)

Primarily services Supply and/or

R&D with greater than incidental but less than 50% services

Supply and/or R&D incidental services only

Supply and/or R&D with no services/

Number of Task

Orders Required to

Propose and Manage

(Combined Total)

175+ Annually 76-174 Annually 50-75 Annually less than 50

Annually

Number of

Employees Required to Manage

2,500+ 1,501-2,499 1,000-1,500 less than 1,000

Required Business

Systems

All contractor’s business systems defined in DFARS clause 252.242-

7005 were applicable and

Cost Accounting

Standards (CAS) were required

At a minimum the contractor was required to have an adequate accounting system, an acceptable purchasing system, and an acceptable property management system and Cost

Accounting

Standards (CAS) were required

At a minimum the contractor was required to have an adequate accounting system, an acceptable purchasing system, and one of the remaining four systems in DFARS

252.242-7005

Effort required no acceptable business systems outlined in

DFARS 252.242-

Security

Classification

Requirements –

Facility and

Safeguarding

Top Secret (TS)

Facility Clearance and Secret

Safeguarding required

Secret Facility

Clearance and

Secret

Safeguarding required

Secret Facility

Clearance and no

Safeguarding required

No Facility

Clearance or

Safeguarding required

Security

Classification

Requirements –

Personnel

TS/SCI or equivalent security clearances required for select workforce

TS or equivalent security clearances required for select workforce

Secret or equivalent security clearances required for select workforce

No security clearances required for workforce

Scope Required in the PWS – Core

Competencies

Required services in all three Core

Competencies

Required services in at least two Core

Competencies

Required services in one Core

Competency

No Core

Competencies required

Scope Required in the PWS – Types of

Platforms/Programs

Required support for all three types of platforms/ programs;

Aviation, Ground, and Maritime

Required support for Aviation and

EITHER Ground

OR Maritime platforms/programs

Required support to one type of platform/program;

Aviation, Ground, or

Maritime

No support for any type of platform/program required

Performance

Locations and

Geographical requirements

Performance required in 10 or more CONUS and

OCONUS

locations

(hazardous and non-hazardous)

Performance required in more than 1, but less than 10 CONUS and OCONUS locations (non-hazardous)

Performance required in more than one

CONUS or

OCONUS location

Performance required at one contractor location

Diversity of requirements

Includes management of a

GOCO, GOCO-

like, or commercial operation with similar Enterprise management and logistics operations requirements

Includes management of a

GOCO, GOCO-

like, or commercial operation with similar Enterprise management requirements

Includes management of similar logistics operations requirements

Includes neither similar Enterprise management nor logistics operations requirements

SOF, DoD, and

OGA Support

SOF Support DoD or OGA

Support

Non-government entity

This section is not used

For proposed major subcontractors, relevancy is defined by that which reflects experience in the area of expertise the major subcontractor is proposed to actually perform under this contract (i.e. specific areas in the PWS).

L.2.3.3 Rating Criteria for Relevancy

When making the relevancy determination the following definitions will be used for both prime offeror and major subcontractor efforts:

SECTION L – Table 3. Past Performance Relevancy Rating Method

Adjectival Ratings Description

Very Relevant Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires.

Relevant Present/past performance effort involved similar scope and magnitude of effort and complexities this solicitation requires.

Somewhat Relevant Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires.

Not Relevant Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires.

L.2.4 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the performance of relevant present or past efforts or between conclusion of recent past efforts and this source selection.

As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate the relevancy determination, the offeror shall include in this proposal Volume a roadmap describing all such changes in the organization of its company (prime offerors only). As part of this explanation, the offeror shall show how these changes impact the relevance of any contracts/projects submitted under Past Performance. Since the

Government intends to consider present and past performance information provided by other sources as well as that provided by the offeror, the “roadmap” should be both specifically applicable to the contracts/projects submitted under Past Performance and general enough to apply to efforts on which the Government receives information from other sources.

L.3 VOLUME 3 – Factor 3 – Task Order Management

L.3.1 Task Order Management

The offeror shall submit the following information for each task order (Subfactors 1-3). In addition, the offeror must ensure task order proposals are submitted IAW each task order Instructions To Offerors (ITO). Task order Statement of Objectives (SOOs) and ITOs are located in Section J, Attachments 4-9 of the solicitation. Following the SOF

GLSS2 IDIQ contract award, the Government will award all three task orders based on the results of this source selection, with the performance starting on the various dates provided in each task order ITO.

L.3.2 Task Order Management Approach

The offeror shall provide a concise summary of the planned approach for meeting the requirements and objectives of the individual task order that demonstrates a clear understanding of the type of equipment and services to be provided.

a. Team Composition. The proposed approach shall include the identification of the proposed team composition, team’s qualifications and experience as it relates to each specific task order, and key management processes that will be utilized to ensure successful task order performance.

b. OCONUS Support. The offeror shall describe infrastructure and procedures to support deployed personnel for those tasks requiring OCONUS support. Special attention should be given to the unique nature of

OCONUS locations that require visas, travel coordination (to include US Military coordination and transportation), Synchronized Pre-Deployment and Operational Tracker (SPOT) requirements, and the ability to plan for site specific requirements prior to personnel deployment.

c. Training. The offeror shall describe how it will train employees to ensure initial capability to include knowledge transfer (while minimizing overlap of resources) during task order transition.

d. Staffing. The offeror shall summarize its team’s capability to obtain suitably qualified personnel and maintain program continuity, which demonstrates the offeror’s ability to provide uninterrupted, high-quality work throughout the anticipated period of performance while complying with all applicable labor laws. The offeror shall describe its contingency plan for the insertion of non-incumbent employees in the event incumbent employees decline employment with their company and/or its subcontractors are otherwise unavailable for work under this requirement.

e. Government Furnished. Additionally, the offeror shall identify any unique Government furnished property, materials, and data required for performance if not already identified in the task order documents.

This information should directly align to the proposed task order costs.

f. Resume. The offeror shall also submit a resume (2-page limit) for the proposed Program Manager or Task

Lead for each task order.

g. Enhancements. The offeror shall discuss how enhancements proposed in Factor 1 could be specifically applied to each task order where applicable with linkage back to the Volume 1 section where the proposed enhancements are described. For task order specific enhancements that aren’t described in Volume 1, the offeror shall include the associated resource implications (manpower, time, logistics, etc.) with the exception of cost and articulate the benefit to the Government. Associated cost implications shall be reflected in Volume 4 with linkage back to the Volume 3 section where the task order specific proposed enhancements are described.

L.3.3 Performance Work Statement

In addition to the proposed approach, and in response to the Government’s SOO, the offeror is responsible for proposing a Task Order PWS. The Task Order PWS will be performance-based IAW FAR 37.602 to the maximum extent practical for the requirement and reflect a detailed technical understanding of the requirements. The offeror will include the task order SDS table from the SOO in the PWS submission.

L.4 VOLUME 4 – Factor 4 –Task Order Cost

L.4.0 Task Order Cost Executive Summary

The offeror shall submit one executive summary applicable to all task orders and Enterprise functions. The executive summary shall provide an introduction and overview of proposed costs to include any general cost assumptions, an explanation of the methodology used to develop the direct labor rates, identification and explanation of any applicable escalation or de-escalation of rates, a description of indirect cost pools and basis for application, and a list of any subcontractors proposed for the Enterprise management functions and the three representative task orders with anticipated subcontract type. In addition, the cost(s) associated with any enhancements proposed in

Volume 1 or Volume 3 (with the exception of those costs realized in the first year) should also be included with linkage back to the Volume 1 or Volume 3 section where the proposed enhancements are described. Cost implications realized in the first year shall be reflected within RFP Attachments 10 and 11a-c as applicable and are not required in this executive summary. Detailed historical data, to include assumptions for the individual task orders are not required for this executive summary and shall only be included in applicable attachments or within the required backup documentation as outlined in L.4.2.

L.4.1 Enterprise Management Functions and Business Unit

The offeror shall utilize the Enterprise Budget Template, RFP Attachment 10, to show…