TCTS II L_M Draft RFP.pdf

CUI – SOURCE SELECTION INFORMATION – SEE FAR 2.101 and 3.104

Section L – Instructions, Conditions and Notices to Bidders

LTXT.209-9512 CONFLICT OF INTEREST REQUIREMENTS (NAVAIR) (FEB 2025)

(a) Any time the Offeror represents that there is an actual or potential conflict of interest per KTXT.209-9511 either for itself (or any of its subcontractors, partners, or affiliates) or other Offerors or potential Offerors, the Offeror shall submit information detailing the actual or potential conflict. There is no page limitation on this information.

(b) Any time the Offeror represents that there is an actual or potential conflict of interest for itself (or any of its subcontractors, partners, or affiliates) per KTXT.209-9511, Conflict of Interest Representation, the Offeror shall also submit a mitigation plan. The mitigation plan shall, at a minimum, identify the conflicted party/parties, provide salient facts, provide an analysis of the actual or potential conflict of interest, and recommend an approach to neutralize, mitigate, or avoid the actual or potential conflict. There is no page limitation on the conflict of interest mitigation plan.

(c) The actual or potential conflict of interest and the Offeror’s proposed mitigation plan, if applicable, will be reviewed as part of the Contracting Officer’s responsibility determination and will not be considered as part of the evaluation conducted per Section M. If the Contracting Officer determines that the conflict of interest cannot be neutralized, mitigated, or avoided such that the integrity of the procurement is maintained, then the conflicted Offeror may be deemed ineligible for award.

(d) The Offeror’s mitigation plan may be submitted at any time prior to the due date for receipt of proposals and, if not provided in advance, shall be submitted no later than the due date for receipt of proposals. If the Offeror provides an updated KTXT.209-9511 representation after the due date for receipt of proposals, the Offeror’s mitigation plan shall be submitted concurrently with the submission of the updated representation.

FAR 52.215-1 Alt 1 is included as a Section L Clause.

PART A GENERAL INSTRUCTIONS

1. GENERAL

The Offeror’s proposal must be sufficient in detail and scope to provide the Government with a clear understanding of the Offeror’s approach, expertise, and capabilities as required by the solicitation. The Offeror’s proposal must demonstrate the Offeror’s understanding of the solicitation requirements and its associated risks with its proposed approach. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Alternate proposals are not acceptable.

The Offeror shall include the data necessary to illustrate the adequacy of its various assumptions, approaches, and solutions to problems. The Offeror shall include detailed information in the most logical place and summarize or reference the information in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Throughout these instructions, the “Offeror” is the Prime Contractor with its Commercial and Government Entity (CAGE) code identified in Block 15A on Standard Form (SF)-33, Solicitation, Offer, and Award. For purposes of this evaluation, the Prime Contractor is the Principal Entity.

2. PROPOSAL FORMATING

2.1 Electronic Formatting and Applications

This section provides information to the Offeror on the electronic format and the appropriate software for drafting and submitting proposals. To ensure that the Offeror’s proposal is suitable for reading electronically, Offeror’s shall use the software and procedures described in this section. The Offeror shall format proposals using a Times New Roman 12-point normal font (no reduction permitted). The Offeror may use 10-point font for Tables and Graphics. The Offeror shall ensure that proposal pages include a volume number and page number. In addition to any marking that the Offeror chooses to include in the proposal in accordance with FAR 52.215-1(e), the Offeror shall also mark all proposal information as

Controlled Unclassified Information/Source Selection using “CUI//SSEL” and “Source Selection Information-See FAR 2.101 and 3.104” to comply with FAR 3.104-4. The Offeror shall include any additional CUI markings, as applicable.

Table G-1 identifies the proposal structure, file naming conventions, and suggested page counts for each volume.

2.2 Operating System and Applications

The Government uses Microsoft Windows 11 Enterprise Operating System and the Microsoft Office 365 suite to access proposals. Offerors shall submit proposal information either using Office 365 or otherwise compatible applications.

Offerors shall provide letters and other signed documents as fully searchable Portable Document Format (.pdf) files. Unless expressly authorized, the use of other application software for submission of proposals is unacceptable. Failure to comply with the instructions in this paragraph may render the Offeror’s proposal unawardable.

2.3 Hyperlinks

Offerors shall not include hyperlinks unless expressly authorized within its proposal.

2.4 Virus Free Electronic Submission

Offerors shall ensure that its electronic proposal is virus free. The Government will disqualify any Offeror who submits documents that contain a virus or malicious code from the competition.

2.5 Multimedia

The Offeror shall not embed sound or video (e.g., MPEG) files within its proposal submission.

2.6 Graphics

To avoid the need for extensive computer system resources to view graphics, Offerors shall:

a. Simplify the color palette when creating figures and minimize the use of color print or graphics to the maximum extent possible;

b. Minimize size of graphics files; and

c. Avoid scanned images.

3. PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one for one comparison between the information presented in the proposal volume and the Section L proposal instructions. The Offeror shall structure proposal information such that its paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier sub paragraphs.

Price information, (e.g., dollar values and/or hourly rates) shall appear only in Volume 1 (Contract Administration), Volume 4 (Price), Volume 5 (Small Business), and Annex D (Small Business Subcontracting Plan).

The Offeror shall follow the basic structure of the file naming convention in Table G-1 for electronic file submissions (e.g., proposal volumes, attachments, appendices), where “#” represents the sequential numbering of files and shall preface files with an abbreviated company name. Offerors shall keep the file name as short as possible (i.e., under 40 characters) to ensure file accessibility on Government SharePoint systems or shared drives. Files with longer names often become corrupt or inaccessible.

The Offeror shall organize its submission using one folder for each proposal volume or annex, and include the electronic files requested for that specific volume or annex. Offerors should submit each volume or annex as one file, if possible.

Offerors shall not submit each proposal section/paragraph using separate files. Information submitted as an Annex to a particular proposal volume may include manuals, specifications, plans, procedures, and company policies, as well as other information requested in “Part B Specific Instructions” and do not count towards the suggested page count.

Table G-1 Offeror File Naming and Proposal Structure

Volume Number

Proposal Volume Title File naming convention Suggested Pages

PREREQ Prerequisite [Company Preface]Vol PreReq.pdf

1 Contract Administration [Company Preface]Vol 1 KA#.pdf

Model Contract [Company Preface] Vol 1 Model_Contract.docx or

.pdf

As Needed

Attachment L-1 Volume 1 KA Tables Table KA-1 Offeror Summary Table KA-2 Offeror Information Table KA-3 Business System Status Table KA-4 Terms and Conditions

[Company Preface]Vol 1 KA Tables.xlsx

As Needed

2 Technical [Company Preface]Vol 2 Tech#.pdf

See Below

2.1 System Overview and Interoperability As Needed

2.2 Cross Domain Solution Certification As Needed

2.3 Encryption Certification As Needed

2.4 Manufacturing Readiness As Needed

2.5 Data Rights / Technical Data Package

2.6 Delivery Order One / Technical Maturity As Needed

Attachment L-2 Vol 2 VCRM Results Attachment L-5 Delivery Order 0001 PWS

[Company Preface]Vol 2 VCRM.xlsx [Company Preface]Vol 2 DO 0001 PWS.docx

As Needed

3 Cost/Price [Company Preface]Vol 3 Cost- Price#.xlsx

As Needed

Cost/Price Tables Attachment L-3 Vol 3 Pricing Workbook

[Company Preface]Vol 3 Pricing Workbook.xlsx [Company Preface]Vol 3 Pricing Workbook.xlsx

As Needed

4 Small Business [Company Preface]Vol 4 SB.pdf As Needed

Attachment L-4 Small Business Participation Commitment Document

[Company Preface]Vol 4 SBPCD.pdf

Annexes

Annex A Joint Venture Agreements [Company Preface] Ann-A JVA.docx or .pdf

N/A

Annex B DCAA/DCMA Reports, Audits, and Determinations [Company Preface] Ann-B DCMA-DCAA Reports.pdf

N/A

Annex C OCI Mitigation Plan [Company Preface] Ann-C OCI.docx or OCI.pdf

N/A

Annex D Small Business Subcontracting Plan [Company Preface] Ann-D SBSP.docx or pdf

N/A

Annex E VCRM Verification Data Artifacts [Company Preface] Ann-E .docx or .pdf

N/A

Annex F CLASSIFIED (IF APPLICABLE) VCRM Verification Data Artifacts

[Company Preface] Ann-F .docx or .pdf

N/A

Annex G Delivery Order 0001 PWS Supporting Documentation

[Company Preface] Ann-G .docx or .pdf

N/A

Table G-2 lists the attachments provided to the Offeror within Section L.

Table G-2 Section L List of Attachments

Section L Attachment Number

Electronic File Title Attachment Contents

L-1 Att L-1 Vol 1 KA Tables Table KA-1: Offeror Summary Table KA-2: Offeror Information Table KA-3: Business System Status Table KA-4: Terms and Conditions

L-2 Att L-2 Vol 2 VCRM Results VCRM Results L-3 Att L-3 Vol 3 Pricing Workbook Pricing Tables L-4 Att L-4 Vol 4 SPBCD Small Business Participation Commitment Document

(SBPCD)

L-5 Att L-5 Vol 2 DO 0001 PWS Performance Work Statement for Delivery Order 0001

4. PROPOSAL SUBMISSION AND PACKAGING

4.1 Electronic Proposal Submission

The Offeror shall submit its unclassified proposal volumes electronically through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. For instructions on how to post an offer, please refer to the Posting Offer demo: https://pieetraining.eb.mil/wbt/sol/PostingOffer.pdf. The Offeror shall not use any other method to submit its initial proposal including any postal delivery service, hand-carried, or other electronic systems (e.g., DOD SAFE).

It is the Offeror’s responsibility to follow the registration instructions found on the PIEE website. It is advised that all potential prime Offerors and their subcontractors ensure the proper company points of contact are registered in the site based on their CAGE codes and have the proper roles assigned well in advance of the solicitation closing date.

Subcontractors are only required to register in PIEE if they want to submit their proprietary proposal information separate from the prime offer. Documents submitted by the subcontractor directly to the Government must have the prime contractor’s name, prime contractor’s CAGE code, and RFP number on the first page of the document.

Offerors are responsible for submitting proposals, and any modifications or revisions, to reach the Government office designated in this solicitation by the date and time specified. While Offerors are encouraged to submit documents early, any submission, modification, or revision received at the Government office after the exact date and time specified is “late” and will not be evaluated or considered for award. In the event there is acceptable evidence to establish that the submission, and any modifications or revisions were received at the Government installation designated for receipt of offers and was under the Government’s control prior to the date and time set for receipt of offers, the Procuring Contracting Officer (PCO) may accept the submission. It is also the Offeror’s responsibility to confirm receipt of proposals and all electronic communications. The Government advises Offerors to take screen shots of its submission to validate submission acceptance in the PIEE system against this solicitation. The Government will not search for proposals in PIEE submitted incorrectly.

The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the RFP.

If there is an unanticipated PIEE System outage within 24 hours of the proposal due date and the outage has interrupted normal Government processes so that proposals cannot be received by the exact time specified in the solicitation, the Contractor shall immediately notify the Contracting Officer. This notification shall occur prior to the proposal submission deadline and shall be made in writing. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain written approval from the Contracting Officer to submit the proposal via an alternate method or the Contracting Officer may advise the Offeror that the Government will follow the procedures set forth in FAR 15.208(d) for amending the solicitation closing date.

4.2 Classified Data

Offerors shall not submit classified material using the PIEE or DOD SAFE system. Offerors shall submit classified materials in accordance with the guidance in this section.

Offerors shall submit unclassified proposals to the greatest extent possible. Offerors shall minimize to the greatest extent possible the impact to readability resulting from dividing the information between the classified and unclassified portions of the proposal. If Offerors submit classified information, the unclassified portion shall reference the applicable portion of the classified portion. It is not necessary to attempt to provide an unclassified version of the information included in the classified portion of the proposal. Offerors shall comply with SECNAV M-5510.36B and associated DoD directives and procedures relating to the packaging and handling of classified materials. Offerors shall utilize the guidance below when submitting classified materials using the United States Postal Service (USPS) or through an overnight express carrier.

Preferred method of communication is electronic to Hannah McGraner at hannah.b.mcgraner@navy.smil.mil.

Offerors choosing to hand deliver classified materials shall send a written request to the Procuring Contracting Officer (PCO), at least three working days in advance of the proposal due date to coordinate delivery. Couriers must display a valid courier card and possess the appropriate level current security clearance and background investigation required to carry the information in their possession. Offerors shall not submit data classified above the Secret Level unless previously coordinated with PCO.

OUTER Label:

COMMANDING OFFICER PMA-205

ATTN: SECURITY

47123 BUSE ROAD, BUILDING 2272, SUITE 345

PATUXENT RIVER, MD 20650-1547

INNER Label:

COMMANDING OFFICER PMA-205

ATTN: Hannah McGraner

47123 BUSE ROAD, BUILDING 2272, SUITE 345

PATUXENT RIVER, MD 20650-1547

4.3 Proposal Validity Date

All proposals shall be valid for 365 days.

5. CHANGES TO SOLICITATION

The Government will post all amendments to this solicitation at https://www.sam.gov or https://piee.eb.mil.

Search the database for solicitation number N6134026R1008

6. TECHNICAL LIBRARY

A Technical Library of information directly related to the requirements of this contract is available to all Offerors with approved access.

Following a prospective Offeror's request for Technical Library access, the Offeror shall include a certified copy of DD Form 2345, Military Critical Technical Data Agreement. The Defense Logistics Information Service (DLIS) link for instructions on filling out the DD Form 2345 and obtaining certification is https://www.dla.mil/LogisticsOperations/Services/JCP/DD2345Instructions/.

The Offeror shall submit names and email addresses for up to three (3) designated personnel who will serve as points of contact for receiving the Technical Library through PIEE Solicitation Module. Ensure at least one POC is capable of receiving classified information via SIPRNet at the collateral secret level.

The Offeror, if granted access, shall be responsible for distributing technical library data to subcontractors and team members on a "need to know" basis only. All handling, distribution, and destruction guidance specified herein shall be passed down to subcontractors and team members. Recipients of library data shall comply with all applicable laws, export controls, and distribution statements governing the data.

PART B SPECIFIC INSTRUCTIONS

PR. PREREQUISITE VOLUME

The Offeror shall address the following Prerequisites PR.1 and PR.2 in the Prerequisite Volume.

PR.1 CROSS DOMAIN SOLUTION

The Offeror shall provide in the Prerequisite Volume the nomenclature of its Cross Domain Solution that is on the National Cross Domain Solution Management Office (NCDSMO) List for Raise the Bar (RtB) 1.2 or higher in accordance with (IAW) PWS Table 2.1.1-1, references 27-30 and para 3.6.42.

PR.2 ENCRYPTION CERTIFICATION

The Offeror shall provide in the Prerequisite Volume a letter signed by the National Security Agency (NSA) identifying the End-item Cryptographic Unit (ECU) that it plans to integrate is certified to protect collateral Secret, or above data IAW PWS para 3.4.1.

1. VOLUME 1 – CONTRACT ADMINISTRATION

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-1 Table KA-1: Offeror Summary

Table KA-2: Offeror Information Table KA-3: Business System Status Table KA-4: Terms and Conditions

The purpose of the Contract Administration Volume is to provide the Government the ability to assess the Offeror’s compliance with the information specified within the solicitation. This information is to facilitate the PCO’s responsibility determination and the need to resolve information related to an Offeror’s responsibility does not constitute discussions. The Offeror shall complete all Tables (KA-1, KA-2, KA-3, and KA-4) as separate tabs in Attachment L-1, according to the instructions within the attachment, and submit a completed Attachment L-1 as a separate electronic file within Volume 1 folder. If no narrative is necessary, please simply refer to the submission of Attachment L1 under the respective Sections a through d.

The Offeror shall divide the Contract Administration volume into the Sections outlined below:

a. Offeror Summary Table KA-1

(1) The Offeror shall complete Table KA-1 (Offeror Summary) to summarize the Offeror and its entities’ pertinent information by CAGE code/SAM UEID including the proposed type and level of work to indicate a commitment of work for entity identified. Offerors shall demonstrate the proposed work commitment for each entity in Table KA-1 (Offeror Summary) in Volume 3 (Price) by associating a dollar value commensurate with the Percent of Total Proposed Cost/Price reflected in Table KA-1 (Offeror Summary). The Offeror shall ensure that each CAGE code/SAM UEID is correctly associated to the entity proposed.

(2) For Joint Venture arrangements, the Offeror shall submit the legal document that established the Joint Venture and provide the associated agreements detailing the roles/responsibilities of each member of the JV. Note: All proposed Joint Ventures shall provide the Joint Venture legal document with agreement(s) in Annex A (Joint Venture Agreement(s)). If no JV is proposed, state “None” here.

b. Offeror Information Table KA-2 The Offeror shall complete table KA-2 (Offeror Information). Offerors shall provide the name, title, phone number and email address of the Offeror’s principal point of contact for the solicitation. In addition, the Offeror shall identify those individuals authorized to negotiate with the Government and contractually bind the Offeror.

Offerors shall provide the mailing address, telephone, fax numbers, email address, and facility codes for the Offeror’s local Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office. In addition, provide the name, telephone number, fax number, and email address for the Administrative Contracting Officer (ACO) at DCMA.

c. Business System Status Table KA-3

The Offeror shall complete Table KA-3 (Business Systems Status) showing the current status and or determinations regarding its business systems. If any item is not applicable to the Offeror or for contract performance, so state and justify. The Offeror shall outline the potential impact on contract execution, mitigation plan, and correction plan for any system considered inadequate or not approved by DCMA. The Offeror shall submit relevant DCAA/DCMA reports, audits, and determinations in Annex B (DCAA/DCMA Reports, Audits, and Determinations).

d. Terms and Conditions Table KA-4

Submission of a signed offer to the Government constitutes agreement and acceptance of the terms and conditions of the solicitation.

The Offeror shall complete Table KA-4 (Terms and Conditions). See section M for the definitions of “Exception” and “Deviation”. The Offeror shall provide one of the following two statements in Table KA-4 (Terms and Conditions). If the Offeror takes any exceptions or deviations to the provisions of the solicitation and its applicable documents, the Offeror shall provide the following statement: “All exceptions and deviations taken from the solicitation terms, conditions or requirements, including any applicable documents, are included in this section”. If the Offeror does not take any such exceptions or deviations, then the Offeror shall provide the following statement: “No exceptions or deviations are taken to the terms and conditions or any requirement of the solicitation.”

If proposing an exception or deviation, the Offeror shall provide a detailed description for each in this section.

Indicate the difficulty with the applicable requirement and the proposed solution. Specifically identify the portion of the solicitation and the proposal, which are affected. Also, identify any proposed H-clauses containing unique contract terms and conditions not covered by clauses in this solicitation and associated with an exception or deviation identified in this section.

e. Organizational Conflict of Interest (OCI) Declaration and Mitigation Plan

In accordance with KTXT.209-5911 “Conflict Of Interest Representation” the Offeror shall identify and address in its proposal all actual or potential OCI situations with itself, subcontractors, partners, or any other Offeror as it applies to this solicitation or state that there are no known potential OCIs. If there are no known potential OCIs, the Offeror shall include a statement affirming that there are no known actual or potential OCIs within this section. If any actual or potential OCIs are identified, then the Offeror shall submit an OCI Mitigation Plan in accordance with LTXT.209-9512 “Conflict of Interest Requirements” as Annex C (OCI Mitigation Plan). The contracting officer will determine if any unmitigated risk exists and whether the Offeror shall be eligible for award.

f. Model Contract Documents:

The model contract (inclusive of Sections A through J) shall be provided as a separate file (Model Contract) within the Volume 1 folder. The Offeror Shall not embed the Model Contract as pictures into the Volume 1 narrative.

The Offeror shall ensure the Model Contract includes:

(1) Original signed SF-33 (Solicitation, Offer, and Award) cover page of the solicitation and a signed SF-30 cover page of each amendment (as applicable) with all applicable Blocks completed and acknowledgement of receipt of each amendment (as applicable) to this solicitation. The SF-33 Block 12 “fill-in” (proposal validity date) shall be completed in accordance with (IAW) Section A (Solicitation/Contract Form);

(2) Signed Representations, Certifications, and Acknowledgements or System for Award Management (SAM) reference;

(3) A completed copy of all Federal Acquisition Regulation (FAR), Defense Federal Acquisition Regulation Supplement (DFARS), Naval Air Systems Command (NAVAIR), and special clauses and provisions requiring contractor fill-ins.

(4) Section H (including any other proposed clauses). All Offeror proposed H Clauses, or other contract additions, in full text, if applicable. If not applicable state “None”. If an Offeror proposes to perform work above or not included in this solicitation (e.g., including, but not limited to, an aspect of a proposal that the Offeror believes the Government should evaluate as a strength), the Offeror must include contractually binding language for inclusion in the awarded contract. These additions may be H clauses, additions to the SOW, additions to the CDRLs (if data is to be delivered), or other additions. For the H clause, it must state as a minimum: a) the Offeror’s performance responsibilities; b) the performance periods, including delivery dates, if applicable;

and, c) the financial responsibilities and liabilities of the Offeror. The Offeror’s proposal should include information regarding any Government performance and financial responsibilities incurred as a result of any proposed H clause or other proposed language for inclusion in the awarded contract.

g. Small Business (SB) Subcontracting Plan

Large Business Offerors shall provide their Small Business Subcontracting Plan conforming to the requirements of FAR 19.7 and DFARS 219.7 as Annex D (Small Business Subcontracting Plan). The SB Subcontracting Plan of the successful Offeror(s) will be reviewed as well as approved by the PCO prior to contract award as part of the responsibility determination. See FAR 19.702(a) (1) Statutory requirements, regarding failure of the apparent successful Offeror to negotiate and submit a SB Subcontracting Plan or submit a Comprehensive or Commercial SB Subcontracting Plan acceptable to the Contracting Officer. The successful Offeror’s approved Subcontracting Plan will be incorporated into the resultant contract and contractor performance against the plan will be monitored by the Government during contract execution.

2. VOLUME 2 – TECHNICAL

Note: This volume shall not contain any reference to price aspects of the offer.

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-2 Vol VCRM Results Attachment L-5 DO 0001 TCTS II PWS

The Offeror shall complete Table T-1 (Technical Cross Reference Matrix) and submit it as the first page of Volume 2 (Technical). The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s Technical CRM may be identical to the one provided or revised to add information. For example, the Offeror’s Technical CRM may cross-reference its proposal volumes, paragraph numbers, and pages to specific solicitation requirements identified within the table, as well as other parts of the proposal that contain relevant information.

The burden of proof rests with the Offeror to demonstrate the extent to which its proposed capabilities will meet the requirements. The extent and the type of substantiation may vary, but each paragraph in the Technical Volume must be substantiated. The method of demonstration is at the discretion of the Offeror.

One method of demonstration is documented performance in an operational environment (an environment that addresses all of the operational requirements and specifications required of the system to include platform/packaging) or a simulated operational environment (a real environment that can simulate all of the operational requirements and specifications required of the system). Another method of demonstration is independent testing/evaluation in a non-operational (laboratory) environment (a simulated environment that allows for testing to determine if a system will meet the operational requirements and specifications of the system) at the system-level. The instructions below provide specific guidance for the type of demonstration. However, the Offeror is advised that application of this guidance is not a guarantee that the Offeror's demonstration will be deemed adequate or without risk

Table T-1 Cross Reference Matrix

Section L – Proposal Instructions Volume or Paragraph Numbers / Title

RFP

Section M

PWS Other Relevant

Info

Proposal Reference (Volume/

Paragraph)

2.0 Technical

2.1 System Overview / Interoperability

IIA

3.6.25 ICDs and

DRD

Drawing

DRD

4062AS3550

(Offeror fill-in)

2.2 Cross Domain Solutions (CDS)

Certification Plan

IIA

3.6.42 (Offeror fill-in)

2.3 Encryption Certification IIA 3.4 (Offeror fill-in)

2.4 Manufacturing Readiness IIA 3.6.31 - 3.6.38; 3.8.16 (Offeror fill-in)

2.5 Data Rights

IIA

3.1, 3.2, 3.3, 3.4, 3.5,

3.13 (Offeror fill-in)

2.6 DO 0001 Evaluation / Technical

Maturity IIA

3.6.32, 3.8.11, 3.8.6.3(IDIQ PWS.

DO1 PWS is separate)

Attachment L-2

(Offeror fill-in)

Technical proposals shall address each of the following elements:

2.1 System Overview / Interoperability

The Offeror shall provide a description of the proposed TCTS-II system. The description shall be written at the system level and describe the purpose of each subsystem. The Offeror shall provide a functional block diagram and an exploded view diagram depicting each hardware configuration item. The Offeror shall describe how the proposed design will be integrated with the legacy TCTS II system to meet the interoperability requirements.

2.2 Cross Domain Solution Certification Plan

The Offeror shall provide the Security Assessment Report (SAR), Technology Risk Report (TRR), and Policy Bypass Threat Report (PBTR) for the proposed cross domain solution. The Offeror shall provide a mitigation strategy for any Lab Based Security Assessment (LBSA) risk findings.

2.3 Encryption Certification

The Offeror shall provide either a or b below:

a. The proposed ECU is certified to protect Top Secret data. Note: If the NSA letter submitted for the pre-requisite evaluation indicates a TS certification, no further information is required for section 2.3. The Offeror shall reference the NSA letter within its proposal response.

b. The proposed plan to achieve Top Secret Certification. The proposed plan shall include a schedule, Key and Certificate Management Approach, and the Security Verification Plan and Procedures (SVPP). The SVPP shall include TEMPEST (Red and Black separation approach) and Encryption Kernal verification at the TS level.

2.4 Manufacturing Readiness

2.4.1. Manufacturing Readiness Level Demonstration.

The Offeror’s proposal shall identify those elements (systems, subsystems, suppliers, and/or processes) being assessed for manufacturing risk and its current Manufacturing Readiness Levels using the criteria and process identified in the 2025

Manufacturing Readiness Level Deskbook (Link http://www.dodmrl.com). The Offeror shall describe its Manufacturing Readiness Assessment (MRA) method used to evaluate the MRL Criteria. For any element that is assessed below MRL 10, the Offeror shall deliver its Manufacturing Maturation Plans (MMPs) to achieve MRL 10 within 24 months of contract award.

2.4.2. Manufacturing Plan (CDRL A056).

The Offeror shall provide a draft manufacturing plan per CDRL A056. Within the proposal, the Offeror shall include the following:

a. How its manufacturing management system meets the requirements of AS6500A.

b. The major assembly sequence chart and anticipated manufacturing process flow.

c. The manufacturing build schedule, including drawing release; tooling design, build, and proofing; key supplier deliveries; and fabrication, assembly, and delivery schedules.

d. Facility requirements and layouts.

e. The Offeror’s plans to provide the needed manpower, facilities, and equipment for expected delivery rates per maximum quantities as defined in Section L Attachment L-3 (Pricing Workbook).

2.5 Data Rights

Terms used throughout this element are defined in FAR 2.101 or DFARS 252.227-7989.

The Government seeks rights to technical data and computer software that will allow both the Government and third parties to operate, sustain, and modify the system throughout its lifecycle without the involvement of any particular vendor.

The Data Rights Approach section of the Offeror’s Technical proposal shall consist of: (1) a Technical Data and Computer Software Table, (2) Software Dependencies Diagrams, (3) Hardware Dependencies Diagrams, and (4) a Narrative.

2.5.1 Technical Data and Computer Software Table. Table 2.5-1 is provided for reference. The Offeror shall provide a table that:

2.5.1.1 identifies each computer software (excluding Commercially available off the shelf (COTS) software) and other than commercial (OTC) technical data the Offeror will deliver or generate in performance of the resultant contract;

2.5.1.2 identifies whether the entry is technical data or computer software;

2.5.1.3 identifies the rights offered to the Government of each listed technical data and computer software as

Unlimited, Government Purpose, Limited, or Restricted , SBIR/STTR (as described in DFARS 252.227- 7989), or specifically negotiated or commercial license (if offering a specifically negotiated license(s), include the proposed license(s));

2.5.1.4 identifies the total number of fielded instances of each listed computer software (for technical data, write “N/A”).

2.5.1.5 identifies each Contract Data Requirements List (CDRL) DD-1423 under which each listed technical data or computer software will be delivered (if the technical data or computer software is not associated with a CDRL DD-1423, write “N/A”); and

2.5.1.6 identifies whether the source code for each listed computer software will be delivered (for technical data, write “N/A”).

Table 2.5-1 Notional Table

Find #

Data or Software Item Name

Technical Data or Computer

Software?

Proposed Rights # of instances CDRL Includes Source code

1 DSTCWAN

Suite

CS Unlimited rights 22 Software Product Package (SPP)

Yes

2 S-RAFD

Models

CS Restricted Rights 13 SPP No

3 RIAVAN 2024 TD Commercial N/A N/A N/A

2.5.2 Software Dependencies Diagrams

Via diagram(s), the Offeror shall identify all interfaces and dependencies related to Other Than Commercial (OTC) computer software and commercial computer software (excluding COTS) that are necessary for the system's operation. The Offeror shall:

2.5.2.1 provide software tree diagram(s) detailing the hierarchical structure and components for each proposed computer software,

2.5.2.2 provide software architectural data flow diagram(s) illustrating how each computer software component interacts with other computer software components, and

2.5.2.3 label each computer software component in each diagram with the corresponding entry (row number) in the Technical Data and Computer Software Table provided in Section 2.5.1.

2.5.3 Hardware Dependencies Diagrams

Via diagram(s), the Offeror shall identify all interfaces and dependencies related to hardware items that are necessary for the system's operation. The Offeror shall:

2.5.3.1 provide hardware tree diagram(s) detailing the hierarchical structure and components for each proposed item with sufficient level of detail to determine traceability to the assertion table,

2.5.3.2 provide hardware interconnect diagram(s) illustrating how each hardware component interfaces with other hardware components, and

2.5.3.3 label each hardware component in each diagram with the corresponding entry (row number) in the Technical Data and Computer Software Table provided in Section 2.5.1.

2.5.4 Narrative.

The Offeror shall describe the extent to which the proposed rights for technical data and computer software will enable the Government and third parties to operate, sustain, and modify the system without the involvement of any particular vendor.

The Offeror may include strategies for negotiating rights with subcontractors to secure more favorable terms for the Government data rights (excluding COTS) to include a contingency plan (e.g. substituting computer software components) if unable to obtain favorable terms to enable the Government and third parties to operate, sustain, and modify the proposed system without the involvement of any particular vendor.

2.6 Delivery Order 0001 / Technical Maturity

Note: System Readiness Levels (SRL) will be used to assess the maturity of a proposed solution and help identify technological risks. The contract requires SRL 7 (threshold), SRL 9 (objective). The DoD Technology Readiness Guidebook defines SRL 7 as system threshold capability demonstrated at operational performance level using operational interfaces. SRL 9 is defined as the system has achieved initial operating capability and can satisfy mission objectives.

For this element (Delivery Order 0001 / Technical Maturity), the Offeror may provide either (a) or (b) below. If the Offeror provides (a) below then paragraph 2.6.1 is not required. All Offerors shall complete paragraphs 2.6.2 and 2.6.3.

a. A Permanent Flight Clearance (NATOPS/NATIP) for USN F/A-18 series and USN F-16 for the proposed AS solution with documentation adequate to establish the certification and fielding status of the proposed GS solution.

If a permanent flight clearance is proposed the Offeror shall provide a Verification Cross Reference Matrix (VCRM) in accordance with 2.6.2.

b. If a Permanent Flight Clearance and fielded configuration baseline does not exist for the proposed solution, or if the configuration of the proposed solution is different than the configuration authorized in the Permanent Flight Clearance or delivered to the Government and demonstrated or fielded, the Offeror shall provide a schedule to First Article delivery and a Verification Cross Reference Matrix (VCRM).

2.6.1 Schedule

The Offeror shall provide a Level 2 schedule, in MS Project, that includes any remaining verification requirements, required certifications and the SETR events necessary to meet Production Readiness Review (PRR) entrance criteria in accordance with NAVAIRINST 4355.19E. Include in this schedule estimated dates for First Article delivery as well as any critical milestones and long-lead items that could reasonably impact First Article delivery.

The schedule shall include the Systems Engineering Technical Review (SETR) milestones, in accordance with NAVAIRINST 4355.19E, as required to mature proposed solution, obtain a permanent flight clearance, and obtain a Full Rate Production decision. The minimum required SETR events include a PRR and Physical Configuration Audit (PCA). In addition to the entry criteria specified in NAVAIRINST 4355.19A, First Articles will be required, and will require a Permanent Flight Clearance prior to conducting PRR. Any proposed solution baseline that has not been verified to meet all requirements or for which final certifications have not been obtained from all certifying agencies will also require, at a minimum, a PCA, Flight Readiness Review (FRR), and Functional Configuration Audit (FCA) and may require additional SETR events depending on the technical maturity of the proposed solution and extent of unsatisfied requirements and incomplete certifications.

The Offeror’s proposal shall provide justification if it is tailoring a proposed SETR event to include, but not limited to, SRR, PDR, and CDR and schedule as supported by System Readiness Level assessment and provide its supporting documentation.

2.6.2 Verification Cross Reference Matrix (VCRM)

The Offeror shall provide the status of all requirements identified in Attachment L-2 Verification Cross Reference Matrix (VCRM) Results. In Annex E (VCRM Data Artifacts), include the data artifact, at minimum an executive summary, that satisfies each requirement. For those data artifacts that are Classified, please submit an unclassified reference in Annex E stating that a document exists. Provide a classified Annex F (CLASSIFIED VCRM Data Artifacts) that includes the data artifacts that satisfy those requirements.

2.6.3 Previously Completed Tasks

With respect to Attachment L-5 (Delivery Order 0001 PWS), the Offeror shall identify the specific PWS task(s) by paragraph and shall provide supporting documentation demonstrating the task was completed to the standards outlined in the PWS Delivery Order 0001 in its Annex G (DO 0001 PWS Supporting Documentation). The Government reserves the right to determine the acceptability of the previously completed work and its relevance to the current requirement.

VOLUME 3 – PRICE

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Att L-3 Vol 3 Pricing Workbook

No price or pricing information shall be included in any other proposal volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate the Price proposal.

As this is a competitive acquisition with adequate price competition anticipated, any price documentation requested shall not be certified in accordance with FAR 15.406-2. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional certified cost and pricing data as necessary from both the Offeror and subcontractors and may conduct negotiations with the Offeror, pursuant to FAR Part 15.403-4. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2.

Any numerical data shall be in an MS Excel spreadsheet; and any narrative shall be in MS Word format. Files received in a format other than requested are unacceptable. Portable Document Format (PDF) is not acceptable, except when provided in addition to MS Excel and MS Word formats. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using “value only” cells. Spreadsheets shall not be protected. The Price proposal shall be unprotected and unlocked, with formulas intact to show mathematical operations.

Price information shall be submitted in Then Year dollars (TY$) based on the Government’s fiscal year (1 October through 30 September). All /price information shall be submitted in United States Dollars (USD) and rounded to the nearest dollar.

Table 3-1 contains the notional procurement plan. The following is the notional procurement plan for this IDIQ contract.

This procurement plan is provided for planning purposes only and Offerors are advised that the estimated procurement quantity is subject to change throughout performance of this contract. The ICS and CLS are not location specific. Table 3-2 shall be used to complete Attachment L-3 (Pricing Workbook) CLINs 0006-0012.

Table 3-1 Annual Projected Estimated Quantities for CLINS 0001 & 0002

FISCAL YEAR AS MOST LIKELY

QTY

GS MOST LIKELY

QTY

RRU MOST LIKELY

QTY

PSES MOST

LIKELY QTY

FY26 8 4 2 1

FY27 154 6 14 7

FY28 194 8 17 10

FY29 241 6 15 8

FY30 242 6 12 8

Table 3-2: Contract Ceiling Price CLIN Government IDIQ Contract Ceiling Price Number

0006 TBD

0007 TBD

0008 TBD

0009 TBD

0010 TBD

0011 TBD

0012 TBD

Total TBD

3.1 Price Narrative

The Offeror shall provide sufficient information to support its price as well as an explanation of all ground rules and assumptions that affect the price. The Offeror shall address any appearances of unbalanced pricing. Any apparent imbalances in the pricing (high or low) or any other anomalies should be fully explained. The Government is not soliciting any Offeror investments. However, the Offeror shall fully identify and explain any investments (e.g., company investment or management challenge or a contribution of resources and/or equipment). Other topics to be addressed include programmatic variables (e.g., inflation/escalation, location, make/buy decisions, prime/subcontractor relationships, and business base concerns, etc.)

3.2. Pricing Workbook

The Offeror shall change only the red text in Attachment L-3. The blue cell content is fixed; the Offeror shall not change the content of those cells.

The Offer shall complete Tabs (CLIN 0001, CLIN 0002, and CLIN 0003) of Attachment L-3 (Pricing Workbook). The offer shall assume the unit price for all hardware items includes the labor and facility costs associated with producing the hardware. No labor hours related to CLINS 0006 – 0015 shall be included within the production units.

For each CLIN the Government has determined minimum and maximum quantities/pricing points for the creation of pricing step ladders. The Offeror is to determine the pricing step ladders for each Tab for each fiscal year of the ordering period. Pricing shall be provided for each of the stair steps in each pricing table. To assist with offer planning, Annual Projected Estimated Quantities for CLINS 0001 & 0002 have been provided in Table 3-1 above (Annual Projected Estimated Quantities for CLINS 0001 & 0002).

For CLIN 0003, Ballast Kits (both Uninstalled & Installed):

Pricing step ladders are not to be provided; a per unit cost for each FY shall be provided. For Ballast Kits Installed, the pricing should include the amount of effort necessary for the Offeror to bring an Airborne Subsystem into the Heavy Configuration outlined in SPS para 3.2.1.2.

For CLIN 0003, Peculiar Support Equipment:

For each item proposed IAW PWS para 3.3.1.8, pricing is to be provided in the pricing table. Additional columns/rows can be added to the table to accommodate the totality of items proposed IAW PWS para 3.3.1.8.

CLIN 0004 is Not Separately Priced. Data related to production hardware as specified in PWS paragraphs 3.4 through

3.6.54.1 shall be included within the unit price for CLINS 0001-0003.

CLIN 0005 (Spares) The Offeror shall propose an itemized list of spares along with a spares kit with sufficient sparing to support the system utilizing Tab CLIN 0005 Spares of Attachment L-3 (Pricing Workbook . The Offeror shall propose a spares kit with sufficient items/quantities for the Government to sustain the amount of items outlined in Table 3-1 above (Annual Projected Estimated Quantities for CLINS 0001 & 0002) with an annual spares kit purchase.

CLINS 0006 – 0012 (Program Management, Systems Engineering, Non-Recurring Engineering, Cyber Engineering, Logistics, Interim Support, Depot Support)

The Offeror shall complete Tab (CLINs 0006-0012 Labor Matrix) of Attachment L-3 (Pricing Workbook) using the instructions within the Attachment.

CLIN 0013 (Technical Data Package) The Offeror shall propose its Technical Data Package in accordance with PWS paragraph 3.13.2.

The Offeror shall fill in Tab (CLIN 0013 TDP) of Attachment L-3 (Pricing Workbook) with its proposed TDP price.

CLIN 0014 (Travel)

The Offeror shall complete Tab 0014 in the L-3 Pricing Workbook. The Offeror shall not include Contractor fee on CLIN 0014 for Prime Contractor travel. Offerors shall add its indirect costs and applicable burdens to the Government estimated amounts to determine the proposed amounts to be provided on the Estimated Cost line. Offerors shall account for any effort associated with B001 (i.e. Trip Report) as specified in PWS paragraph 3.14.1 CLIN in the creation of any burdens.

CLIN 0015 (Data) The Offeror shall complete Tab CLIN 0015 of L-3 Pricing Workbook using the instructions within the Attachment. The Offeror shall provide Separately Priced Data related to the execution of CLIN 0006 - 0010 as specified in PWS paragraphs

3.7 through 3.10.27. Pricing for all CDRLS not specified on Tab 0015 of Attachment L-3 Pricing Workbook which are outlined in PWS paragraphs 3.7 – 3.10.27 will be negotiated at the Task/Delivery Order level when a requirement for the CDRL delivery materializes.

Delivery Order 0001

The Offeror shall provide a complete Section B for Delivery Order 0001 in Tab D0001 Pricing L-3 Pricing Workbook.

Proposed Delivery Order 0001 pricing shall align with any pricing proposed elsewhere in Attachment L-3 (Pricing Workbook). Delivery date for all CLINs shall be 24 months after award.

At award, the Government may modify Delivery Order 0001 PWS scope of work requirements (i.e., SETR Events, qualification testing) that the offeror has previously demonstrated IAW Volume 2 (Technical), element 2.6.3 (Previously Completed Work). Therefore, the offeror should not include the price of previously completed work scope within this Price section.

VOLUME 4 – SMALL BUSINESS

The following is a list of Section L Attachments that the Offeror shall use to provide information for this volume:

Attachment L-4 Vol 4 Small Business Participation Commitment Document (SBPCD)

4.1 INSTRUCTIONS FOR SMALL BUSINESS OFFERORS

Small Business Offerors are not required to submit any of the information requested in paragraphs 4.2 and 4.3 below.

Instead, Small Business Offerors shall provide their current System for Award Management (SAM) profile. This shall include FAR 52.219-1 (Small Business Program Representations) expanded to display the full text of the provision, showing the NAICS code for this solicitation.

4.2 SMALL BUSINESS PARTICIPATION COMMITMENT DOCUMENT

4.2.1. Other Than Small Business (OTSB) Offerors shall complete the Small Business Participation Commitment Document (SBPCD) provided as Attachment L-4 which shall be completely stand-alone, and not require any reference to another source, volume, or proposal section. The Offerors should submit it as a part of VOLUME 4 SMALL BUSINESS (ref FAR 52.219-8 and DFARS 215.304). The SBPCD is separate from a Subcontracting Plan that is required from Other Than Small Businesses (OTSB). Small Business Offerors are not required to submit a SBPCD.

4.2.2. OTSB Offerors shall complete the SBPCD sections as follows:

a. SBPCD Section 1: Enter the contract and subcontracting total values.