Attachment J-7 - Solicitation Questions and Comments Amendment 0002.pdf

RFP No. 70RDA226R00000001 Amendment 00021

Question

Reference Question Category

(Choose One) Question Answer

# Solicitation Section Attachment Section Solicitation Page No.

Contractual, Technical, Price Question Answer

1 N/A

Attachment J-5 Self Certification Technical

Experience Form N/A Contractual Must offerors submit J-5 Part III only for Track 2?

Part III applies to proposals for Tracks 1 and 2.

Offerors must submit Part III for whichever Tracks the Offerors submits proposals. Offerors must submit an associated completed Project Form (Part III of Attachment J-5) for each solution marked in the Part II matrix. Part III can be reused for each solution. The RFP, Attachment J-5, Part II is amended to make this clarification.

2 Section L N/A 102 of 127 Contractual

Can a product vendor/OEM submit a partial (i.e.

software only) solution to address Track 1, or does a submission have to address every aspect of Track 1?

The government is interested in offerors that can provide a wide range of solutions, but offerors are not precluded from submitting software-only solutions.

3 N/A N/A N/A General

Due to the recent resolution of the government shutdown and the delays it inadvertently caused in obtaining required government endorsements of past performance, [Offeror name] respectfully requests the Government provide a 30-day extension (Jan 7, 2026 ) to the deadline for submission of the DHS Counter-Unmanned Aircraft Systems (C-UAS) proposal as required under Section L of RFP 70RDA226R00000001, in order to ensure the Government receives the most viable and complete proposed C-UAS solutions in support of DHS’s vital role to secure these events and respond to evolving threats. The proposal due date remains unchanged at this time.

4 N/A N/A N/A General

[Offeror name] also request moving the Questions/Comments deadline by one week to December 2, 2025

The government may answer questions received after the deadline at its discretion.

5 Section L, Cover Letter N/A Page 106 of 127 Contractual

Section L.3.3 states "All cover letters are limited to two (2) pages. Each Volume shall include a signed and dated cover letter that states the following…" Please confirm that the Offerors are required to submit a Cover Letter for each volume of the proposal.

Yes, all volumes shall include a signed and dated cover pageletter. RFP Section L.3.3.2 is amended to "the Offeror shall include one (1) cover letter page for its Volume II proposal submission, which does not count towards the page limitations."

6 Section L.4.4 Subcontracting Plan N/A Page 109 of 127 Contractual

Section L.4.4. states that "Offerors should submit acceptable subcontracting plans with their proposals before the proposal due date…" Will the Government clarify this statement about when the subcontracting plan is due.

Subcontracting plans should be submitted at time of proposal submission.

7 Attachment J-6 N/A N/A Contractual Please confirm that the J-6 Attachment is only required to be submitted under Track 1. Confirmed.

8 Section M.2.2 N/A Page 119 of 127 Contractual Please provide how the Government is defining the adjectival ratings scale being used in this evaluation.

The definitions for each confidence rating is provided in Solicitation Section M.4 through M.5.2.

Section L.4.5 Contractor Team Arrangements (CTA) N/A Page 111 of 127 Contractual

Section L.4.5 states that "'Contractor Team Arrangement' (CTA) means... a potential Prime Contractor agrees with one or more other companies to have them act as its subcontractor(s) under this CUAS contract (see FAR Paragraph 9.601(2))."In respect to the requirements in L.4.5, are Offerors required to submit Teaming Agreements to demonstrate the Prime-first-tier Subcontractor relationship?

If the offeror seeks the Government to consider the subcontractor's experience (as a CTA member) for evaluation of Track 1 Factor 2 or Track 2 Factor 2, then the offeror must submit the Section L.4.5 CTA agreement.

Attachment_J-2_-_Track_2_C- UAS_Pricing_Schedule N/A Track 2 Tab Price

Section F.4 States the Place of Performance will be Contractor's Facilities or the Customer site. The pricing sheet only provides 1 line for pricing per LCAT. We respectfully recommend that Offerors be permitted to add lines to the template and provide two sets of rates (Contractor Site and Customer Site).

Section L.6.1 is revised to state "Offerors are instructed to input entries in the cells highlighted in yellow and may add additional rows and columns to the Pricing Schedule in order to propose additional labor categories and associated labor rates not included in the Track 2 – Pricing Schedule (Attachment J-2) and to provide its commercial or Federal Contract Labor Rates to support proposed option period pricing." This includes adding columns to allow for the proposal of contractor site and customer site rates.

Attachment_J-2_-_Track_2_C- UAS_Pricing_Schedule N/A Track 2 Tab Price

Column B and Column C only allow for Offerors to enter the current 2026 Ceiling rate for a Commercial or GSA Schedule Rate. We respectfully request that the Government update the template to add tabs for each Option Period, allowing Offerors to add their corresponding ceiling rate and applicable discount for that period of performance.

Section L.6.1 is revised to state "Offerors are instructed to input entries in the cells highlighted in yellow and may add additional rows and columns to the Pricing Schedule in order to propose additional labor categories and associated labor rates not included in the Track 2 – Pricing Schedule (Attachment J-2) and to provide its commercial or Federal Contract Labor Rates to support proposed option period pricing." This includes adding columns to allow for the proposal of contractor site and customer site rates.

Attachment_J-2_-_Track_2_C- UAS_Pricing_Schedule N/A Track 2 Tab Price

Cells E3 through H3 only mention Commercial Labor Rates and does not include Federal Contract Rates. Please confirm that Offerors are permitted to change the title to include Federal Contract Rate.

Attachment J-2 Track 2 Price Schedule is amended to remove reference to "discounted commercial" in cells E3 through H3. The Government is seeking to obtain the Offeror's proposed labor rates for each ordering period in these columns.

Attachment_J-2_-_Track_2_C- UAS_Pricing_Schedule N/A Track 2 Tab Price

Please provide the Period of Performance dates for the IDIQ for Offerors to provide accurate rate data.

The Government anticipates the start date of each IDIQ to begin in December 2025.

RFP 70RDA226R00000001

FINAL—Section L

L.3.3.2 VOLUME II

(CAPABILITIES)

PROPOSAL FORMAT 107 General

Section L specifies illustrations and their content be eye-readable. As this is a subjective assessment, please confirm illustrations using a 8-point font size would be considered eye-readable.

The government will not confirm if 8-point is an acceptable eye-readable size font for graphics as there are too many other variables that may impact the readability of the graphic. RFP Section L.3.3.2 is amended to add “Non eye-readable means the majority of Technical Evaluation Team (TET) Members vote that the material is non eye-readable.”

RFP 70RDA226R00000001

FINAL—Section L

L.3.3 PROPOSAL

FORMAT 105 General

Section L indicates the offeror is to submit one proposal when proposing both tracks. Please confirm the offeror may cross reference sections within a single volume (e.g., in Volume II material presented in the Business Approach (Track 1) is referenced vs.

repeated in the Staffing Plan (Track 2).

The government will not consider cross-referenced material.

RFP 70RDA226R00000001

FINAL—Section C & Section L

1.3 Technical Tracks

&L.3.3.2 VOLUME II

(CAPABILITIES)

PROPOSAL FORMAT 13 & 107 General

Section C defines Track 2 as "Comprehensive Services" consisting of:-C-UAS as a Service-System Integration-Research and Development (R&D) and Test and Evaluation (T&E) SupportSection L.3.3.2 states that "Offerors proposing for Track 2 shall provide a staffing plan that demonstrates their ability to deliver C-UAS as a Service."Please confirm that the Track 2 staffing plan should address Comprehensive Services and not just C-UAS as a Service.

While Section L.3.3.2 emphasizes the need to demonstrate the ability to deliver C-UAS as a Service, this does not exclude the other components of Comprehensive Services. Since Track 2 encompasses all three elements, the staffing plan should reflect the offeror's ability to support the full scope of Comprehensive Services, not just C-UAS as a Service.

RFP 70RDA226R00000001

FINAL—Section L

L.3.3 PROPOSAL

FORMAT 106 General

Section L indicates each volume shall include a signed and dated cover letter. Please confirm the Offeror can add a tab to Attachment J-1 and J-2 Pricing Schedules to embed a PDF with the signed cover letter. Confirmed.

RFP 70RDA226R00000001

FINAL—Section L

L.6.1 PRICE PROPOSAL

(FACTOR III) 116 General

Will the Government allow Offeror's to submit pricing information in a separate MS Word document to supplement the information provided in the Attachment J-1 and J-2 Pricing Schedules, Narrative tabs?

The solicitation is amended to add "Offerors may submit a pricing narrative in a separate Adobe PDF or Microsoft Office (MS) Word document (if desired)."

Section L.3.3.3 of the solicitation is amended to add “The addendum pricing narrative may only supplement column K – Price Narrative citations (e.g. page numbers, paragraph numbers, sections) for both Attachment J-1 and J-2 Pricing Schedules.”

Additionally, see the answers to questions 20, 22, 64, 84, 100, 101, 112, 121, 122, 132, 137, 267, 301, 375, 377 for more information.

FINAL—Section B

B.14.1 Schedule of Supplies/Services 9 Contractual

Please confirm our understanding that, at the Task Order level, Offeror's may propose additional Hardware/Software and Ancillary Services beyond those items proposed at the IDIQ level to satisfy the specific requirements of the Use Case Scenarios.

No hardware, software, or support services will be explicitly priced at the Track 1 IDIQ level. At the task order level, Offeror's may propose Hardware, Software, and/or Ancillary Services that are within scope of the IDIQ that were not previously submitted on the Attachment J-1 Pricing Schedule. It will be the responsibility of the OCO to determine the fair and reasonableness of each item proposed under Track 1 at the order level.

RFP 70RDA226R00000001

FINAL—Section L

L.6.1 PRICE PROPOSAL

(FACTOR III) 116 General

Please confirm the Offeror may add addition tabs to Attachment J-1 and J-2 Pricing Schedules to supplement/organize their Pricing Narratives.

Confirmed. Additionally, the solicitation is amended to add "Offerors may submit a pricing narrative in a separate Adobe PDF or Microsoft Office (MS) Word document (if desired). Section L.3.3.3 of the solicitation is amended to add “The addendum pricing narrative may only supplement column K – Price Narrative citations (e.g. page numbers, paragraph numbers, sections) for both Attachment J-1 and J-2 Pricing Schedules.”

Additionally, see the answers to questions 18, 22, 64, 84, 100, 101, 112, 121, 122, 132, 137, 267, 301, 375, 377 for more information.

21 RFP- Section L.3.1., Para 1 N/A Pg. 103 Contractual

For internal reviews and approvals, would the Government please consider an extension of the Proposal Due Date and time to Friday, December 12, 2025, 5:00 p.m.? The proposal due date remains unchanged at this time.

RFP- L.6.1 PRICE PROPOSAL

(FACTOR III) N/A 116 Price

Would the Government please allow Offerors to submit their pricing "Narrative" in a Word file instead of in the Narrative tab of Attachments J1 and J2? Allowing a Word document will allow for much easier formatting of the contents of the Narrative, and, it will allow Offeror's to site specific page numbers/paragraphs/sections as required in the last column of the Pricing tabs for Attachments J1 and J2.

The solicitation is amended to add "Offerors may submit a pricing narrative in a separate Adobe PDF or Microsoft Office (MS) Word document (if desired)."

Section L.3.3.3 of the solicitation is amended to add “The addendum pricing narrative may only supplement column K – Price Narrative citations (e.g. page numbers, paragraph numbers, sections) for both Attachment J-1 and J-2 Pricing Schedules.”

Additionally, see the answers to questions 18, 20, 64, RFP- L.6.1 PRICE PROPOSAL

(FACTOR III) N/A 116 Price

Will the government confirm that Offeror's may propose innovative Hardware/Software in Track 1 to meet DHS requirements that they have not previously sold Federally/Commercially, but for which Offeror's have commercial price justification to illustrate Fair and Reasonableness?

Confirmed. See the answer to question 271 for more information.

24 F.2 IDIQ Ordering Periods N/A 47 Contractual

For planning and estimating purposes and to submit compliant Pricing, can the Government please advise of a notional start date for the Period of Performance?

The Government anticipates the start date of each IDIQ to begin in December 2025.

RFP- L.6.1 PRICE PROPOSAL

(FACTOR III) Attachment J-2 N/A Price

Attachment J-2 has columns for option period pricing, but only related to "Commercial Labor Rates". In order to accommodate Federal Contract Labor Rates, would the Government please modify the attachment so the column headers read "Proposed Base Period IDIQ Rate" and "Proposed Option Period X IDIQ Rate"?

Attachment J-2 has been revised to remove reference to "discounted commercial" rate in cells D3 through H3.

RFP- B.7 Labor Subject to the Service Contract Labor Standards 7 Price

Section B.7 references the wage determination from San Francisco, CA, however this document was not part of the final RFP package. Would the government please provide this wage determination or provide the applicable revision number for WD 2015-5637?

Service Contract Act WD #: 2015-5637 can be found at www.sam.gov

27 RFP- L.6.2 Offeror’s Pricing Data N/A 117 Price

Section L.6.2 states "...the Offeror is not required to provide its Federal contract pricing and is not required to complete the column “Federal Contract Unit Price” in Attachment J-1 or the column “Federal Contract Labor Rate” in Attachment J-2."

This seems to imply that the Commercial rate column in Attachment J-2 must be populated.

Would the government consider allowing Offeror's to populate either the Commercial or the Federal column as a basis for fair and reasonable comparison on labor rates?

Yes, Offerors may populate either the Commercial or the Federal column which may be used as a basis for fair and reasonable comparison on labor rates.

28 J-5 Template Instructions 1 Contractual

For Track 2 – Comprehensive Services, may an offeror propose only a subset of the three service types (C-UAS as a Service, System Integration, R&D/T&E Support), or does DHS expect each Track 2 awardee to be capable of performing all three service types across all use cases?

The government is interested in offerors that can provide a wide range of solutions, but offerors are not precluded from submitting partial responses to Track 2.

RFP- M.4.2 TECHNICAL

EXPERIENCE (FACTOR II) N/A 124 Contractual

Does DHS anticipate issuing task orders that bundle multiple Track 2 services (for example, C-UAS as a Service plus System Integration and R&D/T&E Support) under a single task order, or will these typically be competed as separate, more narrowly scoped orders?

The inclusion of different services under one task order or separated amongst multiple task orders will vary and depend on several factors determined by the OCO at the task order level.

RFP- M.4.2 TECHNICAL

EXPERIENCE (FACTOR II) N/A 124 Technical

For C-UAS as a Service task orders under Track 2, does the Government anticipate that any underlying C-UAS hardware and software will be procured via Track 1 IDIQ awardees, or may a Track 2 contractor provide and operate its own hardware and software within the Track 2 scope as part of the managed service?

The Government’s intent for Track 2 task orders under "C-UAS as a Service" is that contractors may provide and operate their own hardware and software within the Track 2 scope as part of the managed service. Track 2 encompasses "vendor-operated turnkey solutions," including the provision of Detection, Tracking, and Identification (DTI) Systems, Mitigation Systems, and Integrated Systems as part of a fully managed service.

There is no explicit requirement that hardware or software must be procured via Track 1 IDIQ awardees.

However, contractors under Track 2 are responsible for ensuring that their solutions meet the applicable requirements and capabilities necessary for the specific task orders, including full system integration and interoperability with existing DHS systems.

31 J-4 Template Instructions 1 Contractual

Are the three scenarios in Attachment J-4 (Huntsville corridor, Arrowhead Stadium NSSE/SEAR, and Patrol Cutter) intended only to support Track 1 pricing and evaluation, or should Track 2 offerors explicitly frame their staffing and technical experience in the context of those same scenarios as representative task-order environments?

The three scenarios in Attachment J-4 are intended only to support Track 1 pricing and evaluation and should not be used for Track 2 proposals.

32 J-4 Template Instructions 1 Technical

For the NSSE/SEAR and maritime use cases, can DHS provide typical or expected durations of deployment (for example, single-day events, multi-week deployments, or multi-month maritime patrols) to inform realistic staffing and surge planning?

NSSE/SEAR would most likely be limited to 1-4 days while mission-based deployments may range from multi-week to multi-month, or a fixed site location could operate throughout the duration of the contract.

33 RFP- F.4 Place of Performance N/A 47 Contractual

For Track 2 services, does DHS anticipate deployments primarily within CONUS, or should offerors plan for OCONUS deployments as well, such as U.S. territories or overseas locations in coordination with other agencies?

The Government anticipates deployments primarily within CONUS. However, the government reserves the right to have work performed OCONUS, which may include areas like Hawaii or Alaska. Section B.4 states "Rates for services performed OCONUS will be established as needed at the task order level."

34 RFP 2.5 Testing Requirements N/A 17 Technical

Will DHS accept existing contractor test reports, including third-party or foreign-government tests, to demonstrate compliance with MIL-STD-810H, MIL- STD-461G, MIL-STD-464C and functional performance, or does DHS anticipate requiring additional Government-witnessed testing under this IDIQ before accepting solutions?

DHS will accept test reports from other U.S. federal agencies or U.S. accredited labs (FFRDC/UARC) to evaluate compliance with MIL-STD-810H, MIL-STD- 461G, MIL-STD-464C and functional performance. The government retains the right to request to additional government witness testing, as warranted.

35 RFP 2.5 Testing Requirements N/A 17 Contractual

The SOW references acceptance criteria such as successful detection and mitigation of 95 percent of simulated UAS threats during testing. Can DHS clarify whether stated acceptance criteria applies to all solution types (including services leveraging third-party systems) and all task orders, or whether it will be tailored by task order based on mission context?

The acceptance criteria referenced in the SOW, such as successful detection and mitigation of 95 percent of simulated UAS threats during testing, serves as a baseline standard for evaluating solution effectiveness.

However, DHS clarifies that acceptance criteria will be tailored by task order (TO) based on mission-specific requirements and operational context. This flexibility ensures that the criteria align with the unique needs of each deployment, including services leveraging third-party systems.

RFP 2.8 Interoperability Declaration N/A 18 Technical

For TAK interoperability requirements, can DHS specify the target TAK baseline and any DHS-specific profiles or plugins (for example, TAK variants, data schemas, or plugin frameworks) that offerors should assume for planning integration and testing?

Offerers should assume, for interoperability, their systems meet the Modular Open Systems Architecture (MOSA), and/or DHS Enterprise and Security Architecture with open data standards for the surveillance of signals and metadata. Open API with updatable software Integrated Sensor Architecture (ISA) compatible with artificial intelligence (AI) and machine learning algorithms should also be considered.

RFP 2.8 Interoperability Declaration N/A 18 Technical

Beyond TAK and DHS Common Operating Picture systems, are there any other DHS-mandated situational awareness or command-and-control platforms that Track 2 offerors should assume for interoperability in their system integration and C- UAS as a Service offerings?

Offerers should assume, for interoperability, their systems meet the Modular Open Systems Architecture (MOSA), and/or DHS Enterprise and Security Architecture with open data standards for the surveillance of signals and metadata. Open API with updatable software Integrated Sensor Architecture (ISA) compatible with artificial intelligence (AI) and machine learning algorithms should also be considered.

38 RFP 1.3- Technical Tracks N/A 13 Technical

For C-UAS as a Service and R&D/T&E Support, can DHS clarify expectations for data ownership and rights, including operational data, test data, derived analytics, and software models generated under this IDIQ, particularly when the contractor uses proprietary algorithms or third-party tools?

DHS retains ownership of all operational and test data generated during the performance of the contract.

Contractors may be granted access to operational data during the contract period but must safeguard its confidentiality and adhere to DHS data security policies.Test data produced during R&D and T&E phases is the property of DHS, as it is generated using Government-funded resources. If contractors use proprietary algorithms or third-party tools to generate test data, DHS may require access to the underlying algorithms or methods to validate the results. This ensures compliance with DHS intellectual property requirements and data security standards.

39 RFP 1.3- Technical Tracks N/A 13 Technical

For task orders involving RF-based detection or mitigation, will DHS obtain FCC and NTIA authorizations and waivers as applicable, or will the contractor be responsible for obtaining experimental licenses, special temporary authority, or other RF authorizations required for operations and testing?

DHS will obtain FCC and NTIA authorizations, waivers, or other RF authorizations, as applicable.

40 RFP 1.3- Technical Tracks N/A 13 Technical

Can DHS clarify the expected division of responsibilities between DHS personnel and contractors for actions taken under DHS’s C-UAS legal authorities, and confirm whether contractor personnel will be limited to technical system operations and recommendations rather than exercising statutory mitigation authorities?

Contractors are not authorized to operate mitigation technologies under 6 USC 124n, only authorized Federal law enforcement officers.

RFP 2.11- Compliance Documentation N/A 19 Contractual

The SOW references 'Buy America' provisions for hardware components. For Track 2 C-UAS as a Service where hardware may be embedded in the service, can DHS clarify whether and how 'Buy America' requirements will be applied, for example at the system, component, or subcomponent level?

Ordering offices will be responsible for determining if the Buy American Act or Trade Agreements Act (TAA) applies to their procurement.

RFP 8.1 Sensitive but Unclassified Systems Requirements N/A 23 Contractual

For Track 2 staffing, can DHS clarify baseline clearance expectations, such as the percentage of positions requiring Secret or TS clearances and any facility clearance requirements, at the IDIQ level versus the task-order level?

As stated in Section C.10.1 Security Requirements, "This acquisition is entirely unclassified and does not involve the procurement of classified products or require contractor personnel to access classified information. As such, no classified security measures, DD Form 254, personnel security clearances, or facility security clearances are required for this contract."

43 J-5 Template Instructions 1 Contractual

Does DHS anticipate any Track 2 C-UAS as a Service task orders requiring 24/7 operations with multiple shifts, and if so, will DHS require vendors to demonstrate capabilities in the technical volume for successful 24/7 operations?

Yes, DHS anticipates that some Track 2 C-UAS as a Service task orders may require 24/7 operations with multiple shifts to ensure continuous coverage and operational readiness in critical scenarios. For such task orders, DHS may require Offerors to demonstrate their ability to support successful 24/7 operations in the technical volume of their proposals, including staffing plans, system reliability, and operational scalability.

44 RFP- F.4 Place of Performance N/A 47 Contractual

The SOW notes that travel may be required to customer sites. Can DHS clarify whether it anticipates any remote-operations models, such as contractor C-UAS operations centers, under Track 2, or whether contractor personnel should generally assume on-site presence at DHS locations for operations and training?

Under Track 2 – C-UAS as a Service, DHS anticipates a mix of remote operations models and on-site presence depending on the specific requirements outlined in the task order (TO). While certain task orders may require contractor personnel to be physically present at DHS locations for operations and training, others may allow for remote operations through contractor-operated C-UAS operations centers or similar setups.

45 J-5 Template Instructions 1 Contractual

The J-5 instructions allow reuse of completed Project Forms for multiple proposed services. Can DHS confirm that a single project may be used to support multiple Track 2 services, such as C-UAS as a Service and System Integration, in different matrices, as long as the narrative clearly addresses each functional capability and use case claimed?

Confirmed that a single project may be used to support multiple Track 2 services, however, it should be submitted as 2 (or more) seperate submissions to ensure the Government understands the Offerors intent to reuse the single project.

RFP- H.4 On-Ramping and Off- Ramping of C-UAS IDIQ Awardees N/A 53 Contractual

For the off-ramping criteria related to non-participating contractors that do not respond to three or more task order solicitations in an option period, how will DHS account for offerors that are only capable or authorized to perform certain subsets of services or mission environments? Will such offerors be expected to bid on all task orders regardless of scope to avoid being considered non-participating? DHS will assess off-ramping on a case-by-case basis.

47 N/A N/A N/A Contractual

Will DHS incorporate all Q&A responses that materially clarify the solicitation into the final RFP via amendment, and may offerors rely on those clarifications as controlling in the event of any conflict with the original RFP language?

Questions and Answers will be published in an Amendment to the RFP. Rules of solicitation interpretation apply, including ramifications for failure to identify and seek clarification from the contracting officer of perceived ambiguities in the solicitation.

RFP- L.3 INSTRUCTIONS TO

OFFERORS N/A 103 Technical

For Track 2 C-UAS as a Service, does DHS view a prime that predominantly integrates and operates third-party systems from multiple OEMs as fully aligned with the intended acquisition model, or is there an expectation that primes also field their own organic C-UAS hardware and software?

No, is there an expectation that primes also field their own organic C-UAS hardware and software. As a matter of technical acceptability, there is not a mandatory requirement that primes field their own organic C-UAS hardware and software. Instead, the Government anticipates that industry will propose a variety of solutions that might include both types of solutions— organic CUAS hardware and software—to be provided as part of the overall offering.

RFP- M.5.2 TECHNICAL

EXPERIENCE (FACTOR II) N/A 125 Technical

Given DHS’s desire for a broad range of solutions and capabilities, does the Government prefer that a Track 2 prime present a small number of curated, pre-integrated solution families, or a broader catalog of interchangeable sensors and effectors that can be mixed and matched per Component and task order?

A broader catalog of interchangeable sensors and effectors would be better suited for flexibility and adaptability for a more diverse mission need.

Ultimately, offerer should provide solutions that can meet any number of operational need, single solution is always preferred. Vendor should specify if there's a specific operation they intend to provide a solution for.

Offerors should provide solutions that can meet a range of operational needs, whether through a single integrated solution or a modular approach that supports adaptability. While a single solution may be preferred for simplicity, the Government also recognizes the value of modular systems that can address specific operational requirements. Offerors should specify whether their proposed solution is designed for general operational needs or tailored to specific missions. RFP Sections L.5.1.2 and M.4.2 have been amended accordingly.

50 RFP 1.3- Technical Tracks N/A 13 Technical

Without committing to specific quantities, can DHS provide any notional expectations about which Components are likely to be the heaviest users of Track 2, such as CBP border operations, FPS fixed facilities, USSS NSSEs, USCG maritime operations, or FEMA deployments, to better inform staffing and surge planning?

The Government does not have this information at this time.

51 RFP 1.3- Technical Tracks N/A 13 Technical

For kinetic mitigation options, can DHS provide any high-level expectations around acceptable risk and collateral effects, for example limitations on damage or secondary effects in urban and stadium environments, to inform how interceptor-based and other kinetic solutions should be presented in proposals and future task-order responses?

Solutions will be evaluated for execution under applicable laws.

52 RFP 1.3- Technical Tracks N/A 13 Technical

Where contractor simulation and RF analysis tools are already in use within DHS or S&T, will DHS allow and encourage those tools to be leveraged under Track 2 task orders, and will any additional validation or accreditation be required beyond what S&T has already performed?

Yes, DHS will allow those tools to be leveraged under Track 2 task orders. DHS will accept test reports from other U.S. federal agencies or U.S. accredited labs (FFRDC/UARC) to evaluate compliance with MIL- STD-810H, MIL-STD-461G, MIL-STD-464C and functional performance. The government retains the right to request to additional government witness testing, as warranted.

RFP- M.5.1 Staffing Plan (FACTOR I) N/A 23 Contractual

Since a facility clearance is not required at the IDIQ level but may be needed for some orders, will existing Secret or Top Secret personnel and facility clearances be considered a positive discriminator in the Track 2 Staffing Plan evaluation, or will they be treated as neutral until required by specific task orders?

The Government does not anticipate the procurement of classified products or the requirement for contractor personnel to access classified information under this IDIQ. As a result, classifed personnel security clearances or facility security clearances will not be considered a positive discriminator and will be treated as neutral during the proposal evaluations.

54 RFP 1.3- Technical Tracks N/A 13 Contractual

For events and missions involving state, local, tribal, and territorial partners, such as NSSEs and SEAR events, are there any additional expectations for contractors regarding memoranda of understanding, background checks, or other partner-specific onboarding requirements that should be factored into staffing and deployment timelines?

Currently there are no additional expectations regarding memoranda of understanding, background checks, or other partner-specific onboarding requirements.

55 RFP 1.3- Technical Tracks N/A 13 Contractual

For complex Track 2 task orders, such as multi-site persistent coverage or high-end NSSEs, does DHS anticipate using additional industry days, one-on-one meetings, or draft RFIs at the task-order level to communicate architecture and integration expectations prior to proposal submission?

The OCO will be responsible for determining the need for industry days, one-on-one meetings, or draft RFIs at the order level.

56 RFP- Section L.4.4 RFP 109 Contractual

RFP's Subcontracting Plan section states "Offerors should submit acceptable subcontracting plans with their proposals before the proposal due date, because the contracting officer does not intend to negotiate or conduct exchanges with the apparent awardees about their subcontracting plans." Is the plan due with the proposal response (as part of Vol 1) or before? If before, when is it due?

Subcontracting plans should be submitted at time of proposal submission.

57 RFP- Section L.3.3.2 RFP 107 General

RFP states Vol II "shall be no less than single-spaced, 11-point font size, and 1-inch margins, and all illustrations (e.g., graphs, charts, diagrams, tables, etc.) and their content shall be eye-readable without the intervention of specialized equipment or a computer when printed." Please confirm 9-point is an acceptable eye-readable size font for graphics.

The government will not confirm if 9-point is an acceptable eye-readable size font for graphics as there are too many other variables that may impact the readability of the graphic. RFP Section L.3.3.2 is amended to add “Non eye-readable means the majority of Technical Evaluation Team (TET) Members vote that the material is non eye-readable.”

RFP- L.6.1 PRICE PROPOSAL

(FACTOR III) Attachment J-2 N/A Price

For Labor Categories that do not cleanly map to an offerors' commercial rate card nor on one of their federal contracts, may offerors provide other data points for comparison to prove fair and reasonableness (e.g. GSA Calc Tool, Salary Survey Data, subcontractor vendor quotes, etc.)? Yes

59 RFP- Section B.7 RFP 7 Price

Section B.7 states that task orders may require work subject to 41 USC 67, Service Contract Labor Standards (SCLS). Will the government please indicate which of the 39 labor categories in Attachment J-2 are SCLS applicable?

The solicitation is amended as follows: "IDIQ ceiling rates for labor categories identified as covered by the Service Contract Act by the OCO may be exceeded where the prevailing wage rate for those categories at the time of order exceeds the prevailing rates used to establish the ceiling rate."

RFP- L.6.2 PRICE PROPOSAL

(FACTOR III) Attachment J-1 N/A Price

Please confirm that the reference to "Products" in section L.6.2 corresponds to "Proposed Item" in columns B and C of Attachment J-1, and not to "Labor Rate" in columns B through H of Attachment J-2.

This section has been amended to add services.

Depending on the track the offeror proposes for, this section applies to Attachment J-1 for products and Attachment J-2 for labor rates.

RFP- L.4.4 SUBCONTRACTING

PLAN (IF APPLICABLE) N/A 109 Contractual

Please confirm that the subcontracting plan should utilize the vehicle ceiling amount for Track 2 as the baseline contract value of which the subcontracting dollars will be based on. Confirmed.

RFP - M.4.2 TECHNICAL

EXPERIENCE (FACTOR II) RFP 124 Contractual

Please confirm that providing a Technical Experience Form (Attachment J-5) for a solution addressing the Detection, Tracking, Identification, and Mitigation Functional Capabilities cell in the matrix (bottom row) within a specified use case (fixed location, fixed location/aviation, fixed location/maritime, mobile, mobile/aviation, and mobile/maritime) represents comprehensive coverage of capabilities within that use case.

Yes, providing a Technical Experience Form (Attachment J-5) for a solution addressing the Detection, Tracking, Identification, and Mitigation (DTIM) Functional Capabilities cell in the matrix (bottom row) within a specified use case (e.g., fixed location, fixed location/aviation, fixed location/maritime, mobile, mobile/aviation, and mobile/maritime) represents comprehensive coverage of capabilities within that use case. This demonstrates that the solution is capable of addressing all relevant functional capabilities required for the specified use case.

63 RFP

RFP, B.3 Contract Type RFP, B.10 Materials

RFP, B.11 ODCs RFP B.12 Travel Pages 6, 8, 8, 9 Price

RFP Section B.3, Contract Type, states: "This is an IDIQ Contract which will permit Firm-Fixed-Price (FFP), Labor-Hour (LH), and Time-and-Materials (T&M) orders, or any combination thereof." RFP Sections B.10-B.12 state "price", "costs", or "actual costs." At the same time, we note that there are no provisions for Cost Reimbursable CLINS currently in the RFP. Please clarify which contract type(s) will be used for Material, ODC, and Travel.

The OCO will be responsible for determining the appropriate contract type at the order level. Any reference to "costs" is referring to B. 11 Other Direct Costs (ODCs) in accordance with FAR 52.212-4 – ALT I (i)(1)(ii)(D)(1).

Attachment J-1 Attachment J-2

RFP - Section L.6.1, Price Proposal (Factor III)

Attachment J-1 - Track 1 Pricing Schedule &

Attachment J-2 - Track 2 Pricing Schedule Pg. 116 Price

Section L states, "Offerors shall submit a Pricing Narrative in the Attachment J-1 - Track 1 Pricing Schedule to clearly detail how price data supports the prices proposed." Since Excel is not an ideal format for a narrative response, please confirm that offerors are permitted to submit the Pricing Narrative as a PDF and reference it in the “Price Narrative Citations” column of the Excel file, or alternatively embed the PDF within the “Narrative” tab?

The solicitation is amended to add "Offerors may submit a pricing narrative in a separate Adobe PDF or Microsoft Office (MS) Word document (if desired)."

Section L.3.3.3 of the solicitation is amended to add “The addendum pricing narrative may only supplement column K – Price Narrative citations (e.g. page numbers, paragraph numbers, sections) for both Attachment J-1 and J-2 Pricing Schedules.”

Additionally, see the answers to questions 18, 20, 22, 65 RFP, Notice N/A Pg 1 General

We understand the urgency, however with some notable changes and ambiguity in requirements, release of the use cases and the MITRE NDA requirement, will the Government allow for a one-week extension in the submission? The proposal due date remains unchanged at this time.

66 RFP N/A N/A Contractual What is the Government's expectation for data rights?

The Rights in Data-General clause (FAR 52.227-14) (May 2014) is incorporated into the solicitation and will be incorporated into contract awards. Data delivery requirements and any need for the use of alternates to the Rights in Data-General clause will be established at the delivery/task order level.

67 RFP, Section C, 1.3 N/A Pg 13 Technical

Please clarify the approach for C-UAS as a Service.

Does it include the vendor hardware and software required or just labor? Please provide examples of deploying a C-UAS as a Service on DHS hardware?

What is the expected balance between contractor-owned vs Government-owned solutions? Will the network be DHS operated or contractor owned?

What are the operator expectations - manned at each site and 24/7 operations?

If you are submitting under Track 1, you are providing a C-UAS solution that encompasses the procurement of hardware. Under a Track 2 solution, there is no hardware involved. Under a Track 2 solution, the predominant proportion of the requirement, expressed in terms of estimated order value, is for C-UAS as a Service, System Integration, Research and Development (R&D), and/or Test and Evaluation (T&E) Support.

Ancillary hardware, software, and services may be included as part of the overall solution, provided they support the primary service-oriented purpose of the requirement.

68 RFP, Section C, 1.3 N/A Pg 13 Contractual

Does the Government perceive any OCI issues in Track 2 R&D/T&E Support with respect to the other Comprehensive Services or Track 1? If so, will the Government accept a mitigation statement from the contractor?

The Government acknowledges the potential for Organizational Conflict of Interest (OCI) issues in Track 2 R&D/T&E Support, particularly with respect to other Comprehensive Services under Track 2 or hardware/software solutions under Track 1 at the task order level once specific requirements are identified for task order performance. OCI concerns may arise if a contractor involved in R&D/T&E activities has the ability to influence requirements, testing outcomes, or evaluations in a way that provides an unfair competitive advantage or impairs objectivity. To address this, the Government will evaluate potential OCI issues on a case-by-case basis and may require Offerors to submit an OCI mitigation statement as part of their proposal at the task order level.

69 RFP, Section C, 2.1 N/A Pg 14 Technical

Please clarify which requirements apply to Track 1 vs Track 2 C-UAS as a Service? Or are they the same requirements? They are the same requirements.

70 RFP, Section C, 2.1 N/A Pg 14 Technical

Does the Government prefer a multi-modal/multi-layers solution for sensing and neutralization? Will technical preference be given for multi-modal solutions vs single solutions?

Technical preference will be given to superior performance, reliability, and scalability. The preference depends on the specific requirements of the application, cost-effectiveness, and operational constraints.

Technical preferences for superior performance, reliability, and scalability will be evaluated at the order level, depending on the specific requirements of the application, cost-effectiveness, and operational constraints.

71 RFP, Section C, 2.1.2 N/A Pg 14 Technical For each use case, please define the class of drones.

Please include classes in 2.1.2.

Per federal small UAS drone classifications, classes 1-3.

RFP section C.2.1 has been amended accordingly.

72 RFP, Section C, 2.1.2 N/A Pg 14 Technical

For each use case, please define the minimum and maximum altitude for each drone. Please include altitudes in 2.1.2.

Per federal small UAS drone classifications, classes 1-3.

RFP section C.2.1 has been amended accordingly.

73 RFP, Section C, 2.1.5 N/A Pg 15 Technical

Should we assume that all three simultaneous threats (2.1.3) are coming from the same direction or disperate directions? No assumptions should be made on direction of threat.

74 RFP, Section C, 2.1.5 N/A Pg 15 Technical

For each use case, can the Government define what is the allowable mitigations (kinetic, non-kinetic, capture, etc.) with respect to the requirements in 2.1.5?

Attachment J-4 Track 1 Use Case Scenarios has been amended. DHS requirements for allowable mitigations will be stated at the task order level. DHS prefers non-kinetic solutions, however, kinetic/net capture solutions will be considered based on operational conditions.

75 RFP, Section C, 10.4.2 N/A Pg 34 Technical Can the government be specific on which roles are considered Key Personnel? There are no Key Personnel at the IDIQ level.

76 RFP, Section L, L.3.1 N/A Pg 103 Contractual Does a reseller agreement to other primes preclude a vendor from priming its own solution?

Offerors are prohibited from submitting a proposal as a prime (or being a partner or joint-venture member of a prime), and partnering with another offeror in any type of contractor team arrangement under the same Track.

77 RFP, Section L, L.3.1 N/A Pg 103 Contractual

For the L.3.1 Proposal Due Date, the Government states Offerors are prohibited from submitting a proposal as a prime (or being a partner or joint-venture member of a prime), and partnering with another offeror in any type of contractor team arrangement under a Track. Does the Government consider all teaming agreements to fall under contractor teaming arrangement (CTAs) as defined in FAR part 9.601? No.

78 RFP, Section L, L.6.1 N/A Pg 115 & J-4 Pg

2 Technical

Please define the service level agreement in each Use Case to aide in pricing SLIN X003AC. Include hours to be on-call and response times.

No, service level agreements will be determined by the component at time of award.

79 RFP, Section L, L.6.1 N/A Pg 115 & J-4 Pg

1 Technical

For training, please define expectations for classroom vs IMI vs over-the shoulder. Please define the class size. Please clarify whether this is operator only or to include maintainer training?

Vendors should define the training scope at time of award, government will provide a list of those needed to be trained.

80 RFP, Section L, L.6.2 N/A Pg 117 Contractual

Please clarify the statement in reference to "If the offeror does not have an active Federal contract for a proposed product" that the Government will accept a viable solution that is not in a catalog nor on an active contract.

Confirmed. Offerors will be required to provide supporting information in their narrative for the government's consideration.

Attachment J-4 Use Cases, Use Case #1, Operational Capabilities

Attachment J-4 Use Cases, Use Case #1, Operational

Capabilities J-4 Pg 1 Technical For Use Case #1, please include mitigation expectations for this scenario.

DHS prefers non-kinetic solutions, however, kinetic/net capture solutions will be considered based on operational conditions. Attachment J-4 Track 1 Use Case Scenarios has been amended.

Attachment J-4 Use Cases, Use Case #2, Operational Capabilities

Attachment J-4 Use Cases, Use Case #2, Operational

Capabilities J-4 Pg 4 Technical

Will Government please confirm that "Man Protable" refers to a single human to carry, install and employ the solution.

Per MIL-STD-1472H, the system's individual components, including transport cases, shall weigh less than 51 pounds for one-person carry; 102 pounds for 2-person carry. Attachment J-4 – Track 1 Use Case Scenarios has been amended accordingly.

83 SF1449 SF1449 SF1449 Pg 1 Contractual Please confirm Boxes 21-24 shall remain blank in the offeror's submission documents? Confirmed

84 L.5, L.5.1.1.

FACTOR I BUSINESS

APPROACH AND

SOLUTIONS TO USE-

CASE

SCENARIOS (Track 1 Only) Pg 112 Price

Attachment J1 contains a Narrative Tab for which Section L without instructions. In the last paragraph of the Section L.6.1 instructions it says that "Offerors shall submit a Pricing Narrative in Attachment J-1 and further that For each Product or Service proposed, the offeror must provide the Pricing schedule, Price Narrative citations (e.g. page numbers, paragraph numbers and sections). Can the government confirm that all narrative should be included in the J1 attachment and there is not another section where pricing narrative should be provided?

The solicitation is amended to add "Offerors may submit a pricing narrative in a separate Adobe PDF or Microsoft Office (MS) Word document (if desired)."

Section L.3.3.3 of the solicitation is amended to add “The addendum pricing narrative may only supplement column K – Price Narrative citations (e.g. page numbers, paragraph numbers, sections) for both Attachment J-1 and J-2 Pricing Schedules.”

Additionally, see the answers to questions 18, 20, 22, 64, 100, 101, 112, 121, 122, 132, 137, 267, 301, 375, 377 for more information.

85 Attachment J-5, Part III Self-Certification Technical

Experience Form Pg 3 Price

Please clarify the detailed requirements for the Narrative block in Attachment J-5, including length restrictions and specific content. Additionally, please indicate whether it is permissible to include an appendix that addresses supplementary information from the Narrative block.

The narrative shall explain the project and how it demonstrates that the vendor has experience with providing a solution for the use case/functional capability combination. There are no page limitations for Attachment J-5.

Attachment J-5, Part II and

SOW 2.10

Self-Certification Technical Experience Form

Attach. J-5 Pg 2 SOW Pg 18 / Technical

Please confirm the guidelines for demonstrating our ability to meet functional requirements and define system configurations (for but not limited to use cases) within the page count limitations. Please confirm it is acceptable to provide an excel spreadsheet with configuration details as an exhibit.

Functional requirements and system configurations are driven by the component need and will be defined at time of award. RFP Section M.4.1 is revised to state “Additionally, the Government will consider the offeror’s non-price information in Attachment J-1 columns A, B, C, and I contained in the Use Case Scenario Tabs that is the offeror’s proposed solutions to the Attachment J - 4 Track 1 use-case scenarios. The Government will consider whether the offeror’s non-price information about its solutions to the use-case scenarios demonstrate ability to perform the full range of the SOW requirements and the products’ ability to meet the functional requirements that are applicable to the three use-case scenarios. For the solutions proposed for the Attachment J-4 Track 1 Use Case Scenarios, the Government has a preference for solutions that demonstrate superior performance, reliability, scalability, and cost-effectiveness. The Detection, Tracking, Identification, and Mitigation capabilities will be evaluated collectively as part of the overall technical capability.”

87 L.3.3 PROPOSAL FORMAT Pg 104 - 106 General Please confirm it is permissable to cross-reference to other volumes within the proposal.

The government will not consider cross-referenced material.

88 L.6.1 116 Contractual

When addressing price reasonableness in the required price narrative relative to hardware products and labor rates, are contractors to embed printed copies of published…