4. T3PI Section L Instructions Amend 0001.pdf

FA240125R0001 Attachment 04

(U) Proliferated Warfighter Space Architecture (PWSA)

Tranche 3 Program Integration (T3PI)

Attachment 4 – Section L - Proposal Instructions, Conditions and Notice to Offerors

December 13, 2024

Amendment 0001 dated January 10, 2025

DISTRIBUTION STATEMENT A: Approved for public release: distribution unlimited.

Table of Contents

1 Introduction

2 Submission Instructions

2.1 Proposal Format Instructions

2.2 Table of Contents, Cross Reference Matrix, and Glossary

3 General Information

3.1 Use of Non-Government Advisors

4 Definitions

5 Volume I: Program Management / Personnel Qualifications

5.1 Tab 1 Executive Summary

5.2 Tab 2 Program Management/Staffing

5.2.1 Management

5.2.2 Staffing

5.3 Tab 3 Key Personnel Résumés

6 Volume II: Technical Approach

6.1 Tab 1 Tranche 3 Program Systems Engineering and Integration (SE&I)

6.1.1 Enterprise Architecture Analysis

6.1.2 Program Requirements Assessment and Management

6.1.3 Program Integration and Verification Management

6.1.4 Program Configuration Management

6.1.5 Integration Focus Areas

6.1.6 Program Schedule Management

6.1.7 Program Risk, Issue, and Opportunity Management

6.1.8 Program Trades and Technical Assessments

6.1.9 Technical Reviews

6.2 Tab 1 (Appendix): Technical Approach Scenarios

6.2.1 Complex System Delivery under Schedule, Cost, and Performance Constraints ... 89

6.2.2 Critical Assessment of Existing Interface Control Document (ICD)

6.3 Tab 2 Technical Data and Computer Software Rights Assertions

6.4 Tab 3 Unpriced Basis of Estimate (BOEs)

7 Volume III: Past Performance

7.1 Past Performance Citations

7.2 Past Performance Questionnaires (PPQs)

8 Volume IV: Organizational Conflict of Interest (OCI) Assessment and Plan

9 Volume V: Security

9.1 Facilities Clearance

9.2 Key Personnel Clearances

9.3 Foreign Ownership and Controlling Interest

10 Volume VI: Small Business Participation

11 Volume VII: Model Contract/Offer

12 Volume VIII: Cost/Price

12.1 Contract Line Item Number (CLIN) Structure

12.2 Cost/Price

12.2.1 Tab 1: Narrative/Executive Summary

12.2.2 Tab 2: Cost Price Summary (Narrative Portion)

12.3 Proposal Pricing Detail

12.4 Tab 3: Cost Build Up

12.5 Tab 4 Travel (CLIN 0002):

12.6 Tab 5: Priced BOM, Other Direct Costs (ODCs) Subscriptions and Licenses (CLIN 0003) 1718

12.7 Tab 6: Major Teammate Proposals

12.8 Tab 7 Government Furnished Information/ Government Furnished Property

13 Attachments

1 Introduction

This acquisition will be conducted in accordance with FAR 52.215-1, ‘Instructions to Offerors- Competitive Acquisition” wherein the Government intends to award without discussions. In addition, the Government will not accept alternate proposals. The Offeror shall submit a proposal for the PWSA Tranche 3 Program Integration (T3PI) in eight (8) volumes. Specific volumes with associated page limits are detailed below.

Volume/Tab Title Page Limit Due Date/Time

All Volumes due at 1200 EST on date specified below Volume I Program Management / Personnel

Qualifications 31 January 2025

Table of Contents/Matrix Unlimited

Tab 1 Executive Summary 3 pages

Tab 2 Program Management/Staffing 10 pages (including personnel matrix)

Tab 3 Key Personnel Résumés 2 pages each (one (1) résumé for each proposed key personnel)

Volume II Technical Approach 31 January 2025

Table of Contents/Matrix Unlimited

Tab 1 Technical Approach Narrative & Appendix

20 Pages (15 Technical Approach & 5 Scenarios Appendix)

Tab 2 Technical and Computer Data Rights Unlimited

Tab 3 Basis of Estimate (BOEs) Unpriced Unlimited

Volume III Past Performance

12 pages (NTE 3 pages per contract)

31 January 2025

Volume IV OCI Assessment & Plan Unlimited Volume V Security 10 pages

Unlimited for SF328 &

DD254

31 January 2025

Volume VI Small Business Participation Commitment Document (SBPCD)

5 pages

Volume VII Model Contract Unlimited 31 January 2025 (If Applicable)

Pre-Award Survey of Prospective Contractor (SF 1408) Pre-award Acc Syst Adequacy Checklist

Unlimited (If Applicable)

06 January 2025

Volume VIII Cost/Price Unlimited 31 January 2025 Note: Page numbering should re-start at the beginning of each section or volume.

Note: Classified Addendums are included in the page count identified above.

Note: Cover pages, tables of contents, appendices and acronym tables are not part of the page count in any volume and are optional for Volumes III-VIII.

Proposals must be clear, concise, and include sufficient detail to support a thorough and efficient evaluation. Offerors are urged to not simply rephrase or restate the Government’s requirements.

Proposals must provide convincing rationale supported by factual, verifiable information that fully demonstrates that the Offeror understands the requirements outlined in the Statement of Work (SOW) for this acquisition. Proposals must clearly describe how the Offeror intends to fully satisfy these requirements. The Offeror should assume the Government has no prior knowledge of its capabilities and experience and will base its evaluation solely upon the information presented in the Offeror’s proposal except for Past Performance and SBPCD. The Offeror shall provide tailored T3PI processes and procedures including stakeholders, teammates, subcontractors, and associate contractors for all inputs.

2 Submission Instructions

The Space Development Agency (SDA) requests that Offerors submit only electronic proposals.

All Volumes along with any appendices and/or attachments shall be submitted only in .pdf format, except in cases where another format is explicitly required, and must be submitted independently by file as SDA will not accept .zip files. Offerors shall submit their responses via Department of Defense (DoD) Secure Access File Exchange (SAFE): https://safe.apps.mil. Offerors shall submit one (1) original copy of each Volume and appendices and/or attachments to be used for any and all printing (i.e. official copy retention requirements) no later than 1200 EST, 31 January 2025 for all Volumes. Each Volume shall be submitted as a separate .pdf file. Offerors shall submit their proposal via a separate DoD SAFE submission and all files should be included in a single DoD SAFE submission. Each file submitted must be clearly labeled with the SDA Request for Proposal (RFP) number, prime contractor organization name, prime contractor proposal title (short title recommended), and Volume number and appendix or attachment number (as appropriate). The size limit for each SAFE file transmission is 8192 MB. Proposals submitted shall be appropriately marked in accordance with DoD Instruction 5200.48 – Controlled Unclassified Information, dated March 6, 2020, if CUI is present, or appropriate security classification guide if classified information is present. Submission via DoD SAFE Instructions

SAFE Drop-Off Request: Offeror shall request a SAFE Drop-off Request, via an email to no ussf.pentagon.sda.mbx.sda-25r0001-t3pi@mail.mil later than 1200 EST 27 Jan 2025. The Offeror shall request a SAFE Drop-off Request regardless of whether they have access to DoD SAFE already. The subject line shall be: T3PI RFP Submission SAFE Request (m of n) and the Offeror’s organization name, where m is the request number and n the total number of requests that will be made by the Offeror. If the Offeror’s submission will exceed the DoD size limit, then they shall make the required number of requests to complete their submission. Within the body email, the Offeror shall clearly state the email address to which the Drop-off Request will be sent.

The Offeror is free to request read receipts for each Drop-off Request email sent.

29 Jan 2025 SAFE Drop-Off Email Response: The Offeror will receive an email with their SAFE Drop-Off Request. Note that this email will not come from the email address listed above.

31 Jan 2025 SAFE Proposal Submission: The Offeror shall upload the proposal to DoD SAFE

NLT 1200 EST.

Within the DoD SAFE submission form, the Offeror shall check both the “Encrypt every file” check box and the “Send me an email when each recipient picks up the files” check box. The password shall be sent under separate email to the email address above with the subject line: T3PI RFP Submission SAFE Request (m of n) Password and the Offeror’s organization name. The “Short note to the Recipients” field shall clearly identify the Offeror’s organization name, the proposal name, and the number of the submission.

SDA expects Volumes I - VIII to be unclassified or CUI. Should a classified Volume III, Past Performance, be required, the Offeror must contact SDA via email ussf.pentagon.sda.mbx.sda- 25r0001-t3pi@mail.mil to for submission instructions. Request for instructions should be received NLT 1200 EST 27 Jan 2025 to allow for timely submission. Offerors desiring to submit classified Past Performance attachments must ensure the information is appropriately classified and marked in accordance with the appropriate security classification guidance.

Proposals received after the proposal submission date and time will be considered late and not evaluated. If any part of the submission is late, all parts of the proposal will be removed from consideration. Offerors whose proposals which are considered late will be informed by the Contracting Officer (CO) and their proposals will be deleted without any files being opened or read.

2.1 Proposal Format Instructions

The font in normal text for all volumes shall be no smaller than Times New Roman 12 pt., while text in tables and figures shall be no smaller than Times New Roman 10 pt. A table shall consist of at least two (2) columns in every row. Tables that are deemed as attempts to circumvent these text formatting restrictions will be removed from the proposal and not evaluated. All margins (top, bottom, left, and right) shall be no smaller than one (1) inch. No less than single line spacing shall be used for all text in paragraphs, bulleted lists, and tables. All .pdf pages, in all volumes, formatted larger than 8.5 inches X 11 inches shall be counted as two (2) pages. Line numbers shall be applied to all text sections in all volumes and shall be set within the left margin of the page so as not to reduce the usable size of the page. Title pages and tables of contents, tables of figures and/or tables will not count against the page counts of the respective volumes and will not be evaluated for content. Page numbering should re-start at the beginning of each section or volume.

Note: Nonconforming proposals may be rejected without review.

2.2 Table of Contents, Cross Reference Matrix, and Glossary

A Table of Contents shall be incorporated into Volume I & II, and will include a listing of the section titles and , subsection titles, paragraph and subparagraph titles. Page numbers for each title must be indicated. The Table of Contents shall also include a listing of illustrations and tables with page numbers.

A cross-reference matrix for Volume I & II is also required. This matrix shall indicate the proposal volume section, subsection, and paragraph, cross-referenced with the appropriate SOW paragraphs, applicable RFP instructions; evaluation criteria, and CDRLs, as applicable.

A glossary of acronyms and terms for Volume I & II is required. The use of acronyms without definitions within the proposal volume is acceptable; however, the Offeror shall ensure that all acronyms are defined in the glossary for that volume. These pages will not be included in the page count for any volume.

3 General Information

3.1 Use of Non-Government Advisors

The Offeror is advised that schedule, technical and price data submitted to the Government in response to this solicitation may be released to non-Government advisors that have signed non-disclosure agreements (NDAs) for review and analysis. These non-Government advisors are employed by the following entities:

AirIn Technologies, Inc.

Alpha 2, Inc.

Altus LLC Amentum Services, Inc. (formerly CENTRA) Bryce Space & Technology, LLC Custom Analysis LLC Emolbi, LLC Full Rev LLC GoLion Company MMAX, Inc.

MTSI

PL Consulting, Inc.

QinetiQ Qualis Corporation Sigmatech, Inc.

Space Systems Integration, LLC Strategic Analysis, Inc.

Strategic Engineering Solutions, LLC TEC Solutions, LLC The Stacia Group, LLC The Aerospace Corporation The MITRE Corporation

All non-Government advisors performing this role are expressly prohibited from performing SDA-sponsored technical research and are bound by appropriate nondisclosure agreements. No Past Performance information will be reviewed by other than Government employees. Any objection to release shall be provided in writing to the Procuring Contracting Officer (PCO) within ten (10) days of RFP issuance and shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal which the Offeror objects to disclosure to non-Government advisors.

3.2 Alternative or Multiple Proposals

Alternative proposals will not be considered. Each Offeror may submit only one (1) proposal.

4 Definitions

Within this Attachment, the following definitions are used:

Prime: The T3PI Offeror.

Major Teammate/Subcontractor: A member of the Prime's development team (at any tier), with a different Commercial and Government Entity (CAGE) code from the prime Offeror, that provides at least ten (10) percent of the proposed cost.

5 Volume I: Program Management / Personnel Qualifications

Volume I (Tabs 1 & 2) shall not exceed 13 pages total (when combined) as identified above. Any pages in excess of this limit, other than those noted below as specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated.

5.1 Tab 1 Executive Summary

Tab 1 shall not exceed three (3) pages.

The proposal shall include an Executive Summary that presents an overview of the Offeror's proposal. An effective Executive Summary will function as a proposal roadmap, helping the Government evaluator understand the Offeror's overall approach to satisfying the requirements of the RFP. The Executive Summary should highlight the proposal's most significant strengths and capabilities that make the Offeror qualified to perform the effort and should contain an overview of the program management and personnel qualifications including team composition and construct as well as contributions of each major teammate.

5.2 Tab 2 Program Management/Staffing

Tab 2 shall not exceed 10 pages. Any pages in excess of this limit, other than those noted as specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated.

5.2.1 Management

The Offeror shall provide a Program Management Plan, detailing the Offeror’s proposed program management processes, procedures, methods, organizational structure, subcontract management and tools for executing the program.

5.2.2 Staffing

The Offeror shall provide a staffing plan detailing the Offeror’s proposed staffing including subcontractors; providing qualified personnel for various work areas; and maintaining expertise.

The Offeror should also address its surge capability/corporate commitment to staffing. The Offeror shall include Attachment 4g, Personnel Matrix in this Section.

5.3 Tab 3 Key Personnel Résumés

Key Personnel résumés shall not exceed two (2) pages each. The résumés shall be included as attachments to this volume and will not be included in the Volume I page limit.

The Offeror shall identify the appropriately cleared, available key personnel to be assigned to this program from the Offeror and major teammates and subcontractors as appropriate. Résumés should use the provided template (Attachment 4c).

For proposed Key Personnel not currently employed by the Offeror, the Offeror shall include signed contingent offer letters (letter of intent). These letters should be signed by both the Offeror and the proposed staff member and should state the willingness of the proposed staff member to join the Offeror in support of the SDA T3PI program if awarded. Personnel not employed by the Offeror or team without a signed contingent offer letter (letter of intent) will be assumed unavailable for the program and the proposal negatively evaluated accordingly. The Offeror shall confirm Key Personnel are available to start at ATP.

Résumés shall be included for key personnel fulfilling the following functions:

Program Manager Chief Systems Engineer Tactical Communications Mission Engineering Lead Space-based Sensing Mission Engineering Lead

6 Volume II: Technical Approach

6.1 Tab 1 Tranche 3 Program Systems Engineering and Integration (SE&I)

6.1.1 Enterprise Architecture Analysis

The Offeror shall describe their technical approach to performance of the Enterprise Architecture Analysis scope. The Offeror shall define the priorities for content to be included in the PWSA Enterprise Architecture products to provide the necessary architectural guidance to all stakeholders.

6.1.2 Program Requirements Assessment and Management

The Offeror shall describe their technical approach to performance of the Program Requirements Assessment and Management scope. The Offeror shall describe the processes and tools that they propose to use to develop, evaluate, and manage requirements products.

The Offeror shall describe their proposed approach to develop and manage required interface control documents (ICDs). The Offeror shall describe their proposed approach to supporting the development of requirements products primarily developed by other organizations, to include ICDs specifying critical system interfaces with and within the Ground Segment expected to be developed by the Ground Segment integrator. The Offeror shall describe their approach to efficiently coordinating requirements products with T3 Component Programs (Transport, Tracking, Custody, Ground Segment) to ensure that system and interface requirements are adequately understood and that derived requirements products and system development activities proceed accordingly.

The Offeror shall provide an assessment of the completeness of the requirements products set included in the T3 Program Functional Baselines (FBLs) as specified in Attachment 7 – Proliferated Warfighter Space Architecture Capabilities, Architecture, and Systems Engineering

References Relevant to Tranche 3 Program Execution. The Offeror shall describe any critical gaps in this set of requirements products and provide recommendations for closing those gaps.

6.1.3 Program Integration and Verification Management

The Offeror shall describe their technical approach to performance of the Program Integration and Verification Management scope. The Offeror shall describe the processes and tools that they propose to use to develop and manage verification products, including but not limited to the T3 System Integration Plan, T3 System Verification Plan, compatibility and interoperability test plans across key intra-PWSA interfaces, compatibility test plans across space-to-user interfaces, and system-level test plans that ensure that system elements delivered by the T3 Program operate in accordance with all applicable requirements once integrated with the PWSA.

The Offeror shall describe their approach to the planning and execution of integration and verification activities. The Offeror shall describe their approach to coordinating integration and verification plans with all relevant participants and stakeholders to ensure that all participants are adequately prepared for each event, the events are efficiently executed, and the outcomes are consistent with the event objectives. The Offeror shall briefly describe the expectations for contributions expected from integrations and verification event participants and stakeholders during event planning and execution.

The Offeror shall provide an assessment of the completeness of the verification products set included in the T3 Program Functional Baselines (FBLs) as specified in RFP Attachment 7 – Proliferated Warfighter Space Architecture Capabilities, Architecture, and Systems Engineering References Relevant to Tranche 3 Program Execution. The Offeror shall describe any critical gaps in this set of verification products and provide recommendations for closing those gaps.

6.1.4 Program Configuration Management

The Offeror shall describe their technical approach to performance of the Program Configuration Management scope. The Offeror shall describe the processes and tools that they propose to use to perform the required configuration management activities.

The Offeror shall state any assumptions involving tools and resources expected to be provided by the Government in support of the Offeror’s configuration management activities. Note that the Offeror may propose solutions that do not involve the use of Government tools and resources should those solutions provide the necessary access and content safeguarding features.

6.1.5 Integration Focus Areas

The Offeror shall describe their technical approach to performance of the Integration Focus Areas scope. The Offeror shall describe their approach to employing expertise in the required space, ground, launch, mission, and systems engineering disciplines to ensure that T3 Program delivery occurs on schedule and in accordance with all applicable requirements and user expectations.

6.1.6 Program Schedule Management

The Offeror shall describe their technical approach to performance of the Program Schedule Management scope. The Offeror shall describe the processes and tools that they propose to use to perform the required schedule management activities across the T3 entire program, including integrating SV and ground contractor efforts. The Offeror shall provide a detailed description of the proposed schedule risk management approach, citing specific examples of schedule performance issues that may be identified and resolved using this approach.

6.1.7 Program Risk, Issue, and Opportunity Management

The Offeror shall describe their technical approach to performance of the Program Risk, Issue, and Opportunity Management scope. The Offeror shall describe the processes and tools that they propose to use to perform the required risk, issue, and opportunity management activities. The Offeror shall provide a detailed description of how the proposed risk, issue, and opportunity management approach will be used to efficiently identify and mitigate risks and ensure successful, on-time T3 Program delivery across the entire T3 program.

The Offeror shall provide a preliminary assessment of the top risks expected to be encountered during T3 Program execution based on the information provided in this solicitation, along with recommended mitigation strategies.

6.1.8 Program Trades and Technical Assessments

The Offeror shall describe their technical approach to performance of the Program Trades and Technical Assessments scope. The Offeror shall identify an example of a trade study that they believe will be required as a matter of practice to ensure successful execution of the T3 Program Integration work scope. The Offeror shall provide a brief description of the necessary tasks to perform as part of that trade study, and a summary of its expected outcomes.

6.1.9 Technical Reviews

The Offeror shall describe their technical approach to performance of the Technical Reviews scope.

The Offeror shall evaluate the notional set of T3 Program technical reviews specified in Attachment 1

– Proliferated Warfighter Space Architecture Tranche 3 Program Integration Statement of Work and provide a recommendation to the Government regarding whether the set is complete or reviews should be added or removed from the list. The Offeror shall provide additional recommendations regarding the use of T3 Program and Component Program technical reviews to reduce risk to successful, on-time execution of the T3 Program.

6.2 Tab 1 (Appendix): Technical Approach Scenarios

6.2.1 Complex System Delivery under Schedule, Cost, and Performance Constraints

The Offeror shall provide a detailed description of a critical development, systems engineering, integration, and/or test role that they have performed in the delivery of a complex system under stressing cost, schedule, and performance constraints. In describing their role, the Offeror shall focus specifically on the responsibilities most relevant to the T3 Program Integration effort. The Offeror shall describe their approach to balancing technical rigor against stressing cost and schedule constraints, including specific strategies that proved effective in ensuring successful delivery without cost or budget overruns. Of additional and particular interest are concrete examples of how the Offeror successfully navigated associate and adjacent contractor constraints to execute a system-of-systems delivery.

6.2.2 Critical Assessment of Existing Interface Control Document (ICD)

The Offeror shall critically evaluate the PWSA Tranche 2 Space-to-Ground (S2G) ICD. The Offeror shall describe which specific content and features of the ICD are effective in specifying the S2G system interface and which specific content and features of the ICD could be rendered more effective with modifications. The Offeror shall describe the modifications that would render the ICD more effective in specifying the system interface. The Offeror shall identify what information is missing from the ICD and what risks are introduced by the absence of that content.

6.3 Tab 2 Technical Data and Computer Software Rights Assertions

The Offeror (and teammate) shall provide a brief narrative and shall clearly delineate all limitations on data, hardware, and computer software rights using the format shown in Table 1. It is the Government’s assumption that no hardware, technical data or computer software will be provided with less than Government Purpose Rights (GPR) (see DFARS 252.227-7013,7014,7015) and that the vast majority of information generated will be provided with Unlimited Rights to the Government. The Government’s intent of this effort includes interface control document development and software development that can be expanded or competed in the future. Data rights must enable this intent, therefore requiring GPR at a minimum. The Offeror shall clearly identify those elements to be provided with less than Unlimited Rights and identify the rationale for their assertion(s) using the format shown in Table 1.

Table 1: Technical and Data Rights Assertion Template

Company Asserting Data Rights

Hardware/Technical Data/Computer Software to be Furnished with Restrictions

Summary of Intended Use in the Conduct of the Effort

Basis for Assertion

Asserted Rights Category

Name of Person Asserting Restrictions

(NAME) (LIST) (NARRATIVE) (LIST) (LIST) (LIST)

Table 1 shall be included as an attachment to Volume I and will not be counted in the page count.

Any associated narrative will be counted in the page limit.

6.4 Tab 3 Unpriced Basis of Estimate (BOEs)

The Offeror shall provide Basis of Estimate (BOE) data by CLIN without cost information to support technical review using Attachment 4d.

7 Volume III: Past Performance

7.1 Past Performance Citations

The Offeror may provide up to four (4) past performance citations (total to include teammates).

Note, only one (1) citation may be submitted for a given program/contract regardless of the number of team members performing on that program/contract. This volume shall not exceed twelve (12) pages inclusive of all unclassified or classified pages. Any pages in excess of this limit, other than those noted below as specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated. Partial pages will count as a single page.

The Offeror shall introduce the current and relevant past performance citations, clearly stating why they have chosen the efforts and how they best demonstrate the Offeror’s ability to perform the proposed work scope. The Government expects direct correlations between the past performance citations and the proposed T3PI technical approach.

The Offeror shall include information on recent/current programs that are similar in magnitude, scope, and complexity to this program. These submissions shall clearly demonstrate the ability of the Offeror and its teammates to satisfy the totality of the T3PI requirements. Past performance from recently acquired companies or subsidiaries is acceptable. All submissions shall have a period of performance within three (3) years from the T3PI proposal due date.

For each submitted citation, the Offeror shall identify:

Customer (Name, phone, email, affiliation Agency/Office) Scope and relevance to the T3PI requirements Place of performance, period of performance, contract/agreement type Bid cost/price, currently invoiced cost/price, Final price/Estimate at Completion If Award or Incentive Fee, scores and fee percentages earned for each completed fee period If CPARS have been completed by the Customer, ratings earned for each completed rating period

In each citation, the Offeror shall address the relevance of the effort and how well it fulfilled the contractual requirements to include schedule management, technical requirements, subcontract management (if applicable) and suppliers.

Current and Past Performance citations shall only include work that has been completed or is ongoing. If a citation indicates expected capability, such as a program that has yet to be awarded, only the work completed to date will be evaluated. For those instances where the Offeror or any teammates, subcontractors and/or vendors have an existing relationship in support of other SDA programs or projects, only a single citation may be submitted and will be evaluated. If the Offeror is providing support to SDA this must be cited by the Prime Offeror only. If one (1) or more teammates, subcontractors and/or vendors are providing support to the Offeror for SDA or other customers, such efforts may not be cited unless a customer other than the Offeror can be identified and would serve as a reference for the teammate, subcontractor and/or vendor. Any citations submitted in violation of these directions will be removed and not evaluated which may result in decreased confidence regarding the Offeror’s ability to perform this effort.

Offerors are hereby notified that SDA intends to survey Contractor Performance Assessment Reports (CPARs) and to conduct interviews with customers identified in Volume III. SDA reserves the right to survey other past performance information beyond the submitted citations.

Information obtained via either of these methods will be included in Offeror evaluations per the criteria in Attachment 5 – T3PI Section M Evaluation Criteria.

7.2 Past Performance Questionnaires (PPQs)

For each past performance citation, the Offeror shall provide the Attached Past Performance Questionnaire (Attachment 4a) to the Government or industry contracting officer or program manager to complete and submit directly to the SDA in accordance with the questionnaire instructions. The Offeror shall provide a list of names and point of contact for the PPQs in the proposal. (Note PPQs completed by the Government and the PPQ POC list are not included in the page count.)

8 Volume IV: Organizational Conflict of Interest (OCI) Assessment and Plan

(a) The Government has determined there is potential organizational conflict of interest (see FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest) due to the nature of the anticipated separate solicitations and contracts for the entire Tranche 3 Program. The entire, fully integrated T3 program will likely include multiple T3 SV contractor(s) (primes and subs) and T3 Ground contractor(s) (primes and subs) who will interface with the T3PI Contractor. Therefore, if a T3PI Contractor intends to bid or perform on any other T3 contract, there will be an OCI. In addition, the Space Development Agency’s OCI policy clearly states that SDA SETA must remain OCI free within SDA; therefore, a contractor cannot concurrently be an SDA SETA contractor and a T3PI Contractor.

(b) As a part of the proposal, the Offeror shall provide the Contracting Officer with complete information of previous, potentially impending, or ongoing work that is in any way associated with the contemplated acquisition. The Offeror shall provide a written assessment addressing why there is no OCI and whether a future OCI is likely or will be avoided. In the event there is a known OCI or if the bidder intends to bid on future T3 Program acquisitions, the Offeror shall include an OCI Plan in addition to the Assessment. An Offeror who assesses it will avoid OCI with the T3 Program MUST include a statement (guarantee) attesting it will avoid OCI for the life of this T3PI contract. If no OCI exists or will exist, the Offeror need only provide the Assessment. If a conflict exists or may exist, both the Assessment and the OCI are required to be a complete proposal.

(c) The resulting contract will include an organizational conflict of interest limitation applicable to the related Government scope of work, at either a prime contract level, at any subcontract tier, or both. During evaluation of proposals, the Government may also, after engagement with the Offeror and consideration of ways to avoid the conflict of interest, insert a special provision addressing eligibility for future contract awards within the existing Tranche 3 Program.

9 Volume V: Security

The Offeror shall describe the Offeror's security approach and ability to comply with the security requirements of this solicitation. It should contain the Offeror's security approach, the approach to meeting the clearance requirements for proposed personnel, facility locations, and classified information safeguarding.

9.1 Facilities Clearance

The Offeror shall identify its proposed location(s) for performing classified efforts for this program. The Offeror is required to hold a current Top Secret facility clearance issued by DCSA in accordance with 32 CFR Part 117 and must provide the complete address and CAGE Code of the facility using Attachment 4f – Personnel & Facilities Template.

9.2 Key Personnel Clearances

The Key Personnel listed below MUST have current, Top Secret (TS) clearances with SCI eligibility and be available to work at contract start. The Offeror shall provide the required information for the Key Personnel below using Attachment 4f – Personnel & Facilities Template:

Program Manager

Chief Systems Engineer Tactical Communications Mission Engineering Lead Space-based Sensing Mission Engineering Lead

9.3 Foreign Ownership and Controlling Interest

The Offeror shall describe its approach for satisfying all requirements of this solicitation related to Foreign Ownership, Control, or Influence (FOCI). The Offeror's security approach should identify, at a minimum, the following:

Compliance with Disclosure of Ownership or Control by a Foreign Government (DFAR 252.209-7002) and shall include submission of a current SF 328, "Certificate Pertaining to Foreign Interests (FOCI)" SF 328 if applicable. Offerors must provide the same information for each proposed subcontractor or subsidiary if applicable. If Offeror’s are foreign owned, they must have an approved FOCI mitigation plan and/or a Cognizant Security Agency (CSA) Security Control Agreement (SCA), or Special Security Agreement (SSA). For Companies that will require access to Collateral, SCI, or COMSEC information, a National Interest Determination (NID) is required.

9.4 Contract Security Classification Specification (DD254)

The Offeror shall complete DD254 and submit it with the Security Volume. The DD254 should include the CAGE code and address of all locations where classified work is anticipated.

10 Volume VI: Small Business Participation

The page limit for Volume V is 5 pages. Content in Volume V will only be evaluated in support of the Small Business Utilization Factor and will not be evaluated for other technical content.

For Large Businesses Only: The Offeror shall submit a Small Business Utilization Plan (SBUP) and/or Small Business Participation Commitment Document (SBPCD) (see Attachment 4b) detailing their anticipated small business inclusion for this procurement to include selection, integration and evaluation processes. While SDA will not mandate specific percentage goals by individual small business type, the Offeror must meet the Minimum Quantitative Requirement (MQR) of small business participation which is five (5) percent of the total proposed contract value (to include options). This requirement may be filled by subcontractors or small business suppliers.

The Offeror shall detail planned small business contribution by type (Woman- Owned, Disadvantaged, Veteran-Owned, Service Disabled, etc.) and by type of work expected to be performed (administrative, engineering, assembly, test and evaluation, modeling and simulation, etc.). The Government expects that some engineering and technical elements of this procurement will be contributed by other than traditional large aerospace and defense contractors, including but not limited to new and emerging small businesses. The SBPCD shall address the following:

a. The quantitative degree (based on the percentage of total price) to which the Offeror will utilize small business (including small, disadvantaged business, women-owned small business, historically underutilized business zone [HUB Zone] small business, veteran-owned small business, and service-disabled and veteran-owned small business). Small business participation constitutes small business utilization contributions to contract performance at the first-tier subcontract level only.

b. Identification of participating small businesses by type of business, product/service, dollar value, timeframe, as available.

c. The complexity and variety of the work small firms are to perform.

d. Enforceable commitments to use such firms. Enforceable commitments (e.g., fully executed teaming agreement, planned purchase order, signed letters of commitment) are more convincing than non-enforceable ones. The SBPCD for each successful Offeror will be incorporated into their respective contract as Attachment TBD.

For Small Businesses: If an Offeror is a small business (NAICS 541715; 1,000 employees) the Offeror shall affirm they are a small business in this Volume. No other information is required in this section for small businesses.

11 Volume VII: Model Contract/Offer

There is no page limit for Volume VII: This Volume shall include the following:

Cover Letter

a. The cover letter shall include the following information and be signed by an official authorized to legally bind the Offeror:

b. Information required by FAR 52.215-1, "Instructions to Offerors-Competitive Acquisitions." For the purpose of providing this information, the cover letter is not considered the first page of the proposal as stated in FAR 52.215-1.

c. The names, titles, and telephone numbers and e-mail addresses of persons to be contacted for clarification or questions regarding this proposal. List no more than two people.

d. The names, titles, and telephone numbers and e-mail addresses of the company point of contact and an alternate to be contacted regarding source selection decisions.

e. A statement that the proposal is firm for a period of not less than 180 days from the proposal due date.

f. A statement that the Offeror’s accounting system meets the requirements of DFARS 252.242-7006, “Accounting System Administration”.

g. If the Offeror does not have an approved accounting system, the Offeror shall complete the following documents and submit to the Contracting Officer in advance of proposal submission:

Pre-Award Survey of Prospective Contractor (Accounting System) (SF 1408) Pre-award award Accounting System Adequacy checklist located at:

https://www.dcaa.mil/Checklists-Tools/Pre-award-Accounting-System- Adequacy-Checklist/.

Both documents shall be submitted to the Contracting Officer as soon as possible but NLT 6 January 2025 via email to beatriz.a.estrada.civ@mail.mil. Failure to submit this information may result in the Offeror being deemed nonresponsive and removed from consideration for award.

h. Any exceptions taken to the terms and conditions, or RFP shall be identified and justified. The Offeror should add, at the end of each exception, as appropriate, a statement substantially as follows: "This offer (is/is not) contingent upon acceptance of the exception or deviation to the cited above." An exception is defined as any instance where the Offeror proposes to provide something less than 100% of the capability or service required by the Model Contract or the documents referenced therein. Each exception must be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information must be provided in the format shown. These exceptions must mirror the assumptions, terms, conditions, and exceptions requested in the Cost Volume, but without any cost information. If there are no exceptions, so state. Failure to comply with the terms and conditions of the solicitation may result in the Offeror being removed from consideration for award.

i. The Offeror must provide a list, with supporting rationale, of all proposal assumptions, terms, and conditions, including any related GFX.

j. The Offeror must identify any subcontractor ground rules, assumptions, or conditions that may cause risk to overall program cost, schedule, and performance, and discuss how the Offeror has addressed them, or plans to address them in its proposed offer, including incorporation into prime contract assumptions, terms, and conditions as appropriate.

k. A statement that administrative changes by the Government to the awarded Contract are acceptable and will not invalidate the offer.

l. The corporate name to be used on any resultant contract and the remittance address.

m. A list of all subcontractors (include company name and address).

Offer/SF 33

a. The Offeror shall complete all clause variables for Model Contract Sections B through K.

b. At a minimum, this section shall include the following:

c. Standard Form 33, "Solicitation, Offeror, and Award," with blocks 12 through 16 completed by the Offeror;

d. Section B, "The summary from Attachment 4e” will be used for Section B for award; and,

e. Section K, "Representations, Certifications, and Other Statements of Offerors," completed by the Offeror, to include appropriate signatures.

The completion and submission to the Government of the above items will constitute an offer.

Upon notification of award and request by the Contracting Officer, the successful Offeror shall provide a signed contract with Sections A through K, fully completed, as applicable, to the Contracting Officer.

12 Volume VIII: Cost/Price

There is no page limit for Volume VIII. This volume consists of relevant information describing the Offeror's proposed cost/price for meeting solicitation requirements.

The Offeror's proposal shall contain sufficient factual information to establish the realism, reasonableness, and completeness of the proposed cost, see the RFP Attachment 5 – T3PI Section M Evaluation Criteria. The Offeror shall detail their assumptions, basis of estimates, and rationale supporting their proposed cost and pricing. This information will be used to evaluate the risks associated with the proposed technical solution, schedule, and price.

The Offeror should assume an Authority to Proceed (ATP) date of 30 April 2025 for pricing and planning purposes.

The Cost/Price Volume should be organized as outlined below and Offerors should use the Cost & Price Template Attachment 4e:

Volume VIII Cost/Price

Tab 1 Cost/Price Executive Summary and Required Contractual Data/Information

MS Word

Tab 2 Cost/Price Summary (Attachment 4e) Narrative and MS Excel/active cells

Tab 3 Cost/Price Build Up (Attachment 4e) plus itemized

Narrative and MS Excel/active cells

Tab 4 Travel Narrative and MS Excel/active cells

Tab 5 Priced BOM, ODCs, Subscriptions and Licenses

Narrative and MS Excel/active cells

Tab 6 Major Teammate Proposals MS Word

Tab 7 Government Furnished Information/ Government Furnished Property

Narrative and MS Excel/active cells

Note: The Section L Attachment 4e for Volume VIII will be submitted in the provided Excel format but are not included within the separate tabs. The Tabs are intended to provide the textual narrative to explain the proposed approach, including any rationale or justification for the price/cost position. The Tab submission may include snapshots or data from the template but should NOT include wholescale copying of the template data (excluding summary tables). The Excel spreadsheets shall include active formulas and any textual narrative required to explain the submission.

For each volume listed above, Offerors shall submit one (1) electronic (soft) copy with appropriate classification markings. The electronic copy will be considered the official copy.

The format of proposal volumes must align directly and sequentially with the instructions contained herein. Offeror responses should be complete and concise. The Government's intent is to obtain brief, specific information in which to evaluate the proposal.

12.1 Contract Line Item Number (CLIN) Structure

The Government anticipates awarding the Contract Line Item Numbers (CLINs) as shown in Section B of the Model Contract. To be considered a compliant proposal, all CLINs must be priced using Attachment 4e. CLIN 0004, Directed Trade Studies will not be priced or evaluated pre-award.

12.2 Cost/Price

12.2.1 Tab 1: Narrative/Executive Summary

The cost/price narrative tab shall include an Executive Summary that presents an overview of the Offeror’s proposal. An effective Executive Summary will function as a proposal roadmap and will help the Government evaluator understand the Offeror’s overall approach to pricing the requirements of the RFP. The Executive Summary should highlight the proposal’s pricing development and any significant cost elements impacting the proposed price. Describe all key ground rules and assumptions used in the development of the proposed costs. For example, resources required of the Government (e.g., Government-furnished equipment and property, including estimated costs if required for Offeror’s technical approach).

12.2.2 Tab 2: Cost Price Summary (Narrative Portion)

In this section, the Offeror shall describe the underlying methodology used for each CLIN with adherence to its respective Cost Accounting Standards (CAS). Items that shall be addressed include, but are not limited to, the following:

1. Provide a listing of company labor categories, position codes, or designators, and definitions of those proposed categories for the Prime and each subcontractor.

2. The Offeror shall identify the basis of direct labor rates (e.g., forward pricing rate agreement or forward pricing rate proposal or forward pricing rate recommendation). The use of composite rates by Contractor Fiscal Year is required.

3. Identify, in full detail, all internal bid codes and burden centers corresponding to each labor category if applicable.

4. Price and percentage of price by the prime and major teammates, where the minimum set of major teammates is defined in the introduction to this attachment. Major Teammates are defined in the Definitions section of this document.

12.3 Proposal Pricing Detail

The Offeror shall provide the total price and elements of price broken down by the Work Breakdown Structure (WBS) and by Government Fiscal Year.

The cost shall be broken down by WBS task and Government Fiscal Year (GFY) using the template in Attachment 4e. The price shall be provided for items down to Level 3 of the WBS for each GFY. The Offeror shall provide the product in Microsoft Office Excel. Excel spreadsheets shall include active formulas and any textual narrative required to explain the submission.

12.4 Tab 3: Cost Build Up

This section shall contain a summary of labor hours, direct and indirect rates, and other information supporting the proposed costs. Items addressed shall include, but are not limited to the following:

Offerors shall provide un-sanitized cost breakdown(s) in accordance with FAR 15.408 Table 15-2.

1. Offeror shall provide an itemized Bill of Materials (BOM) to include item description, quantity, unit pricing, and the basis of estimates. Basis of estimates may include but are not limited to, catalog pricing, purchase estimates, quotes and detailed engineering estimates. The Offerors BOM shall be proposed by SOW task. The BOM shall describe the material in terms defined by FAR 45.101, such as equipment, material, special test equipment, special tooling and other listing as needed. Travel costs shall be supported by detailed itineraries to include origin, destination, number of travelers, trip duration, airfare, car rental and lodging (IAW Joint Travel Regulations).

2. The Government will use Microsoft Office Excel for evaluation and analysis of the cost section of the Cost Volume. The Excel spreadsheets submitted with the proposal shall contain active formulas that enable the Government to trace priced development from hours, rates, dollars, burdens, and escalations to the bottom-line price. The Offeror shall not remove the functionality of the Excel spreadsheet.

3. The Offeror shall submit cost summaries by both Contractor Fiscal Year (CFY) and GFY.

4. Within the Cost Reimbursement data, proposed hours, rates, and resulting costs, shall be broken out by quarter CFY over the entire Contract PoP.

5. The Offeror shall provide major teammate/subcontractor pricing data to the fidelity requested in items 1-4 above in this Section. For concerns related to financial proprietary information of a teammate/subcontractor, see Section 11.612.7.

6. CLIN 0005, Incentive Fee: The Offeror shall propose incentive fee equating to 2% of the proposed CLIN 0001 value (total cost and fee).

7. Fee limits are stated in the CLIN table below:

CLIN

CLIN

Type DESCRIPTION

Fee

0001 CPAF Development and Integration 12%…