70RSAT25R00000005 0001 Attachment 1 Questions and Answers.pdf

Question # Reference Area Question Government Response

1 Appendix A Topic Number DHS251-001 Is this topic specifically and only looking for methods to extract “signature information from pills and powders at drug interdiction events,” etc. Or is the topic open to other means of supply chain analysis outside of pill and powder analysis? Any form of analysis that meets the topic requirement can be proposed.

2 Appendix A Topic Number DHS251-001 I meant to ask about two references provided in DHS251-001. Both papers have specific methods. What I understood that these two papers are optional information it is not a requirement. Would you be able to confirm? The references were provided for informational purposes.

3 Appendix A Topic Number DHS251-001

Additionally, the requirement of obtaining appropriate licensing and/or approval from the Drug Enforcement Agency (DEA) is unclear. Could you please elaborate on this requirement in Phase - 1? My plan is to utilize alternative and public data in Phase 1.

Licensing and/or approval from the DEA would be applicable if work with controlled substances was part of the proposed research.

4 Appendix A Topic Number DHS251-001 Will DHS provide access to database(s) that have source information (e.g. which samples come from the same batch) or is that up to the proposer to source? DHS would be unable to provide source information from a database. GFP/GFI are not permitted on a SBIR Phase 1.

5 Appendix A Topic Number DHS251-001

Section 3.4. Key Personnel

Are there any education/experience requirements for the Principal Investigator?

There are no specifc education/experience requirements for a Principal Investigator. The education and experience will be evaluated based on the proposed approach.

6 Appendix A Topic Number DHS251-001

Section 3.4. Key Personnel

Will the USG accept consultant labor identified as subject-matter experts? DHS SBIR Key Personnel can include Consultants, as properly included in the proposal.

7 Appendix A Topic Number DHS251-001

Section 3.4 Commercialization Strategy

Will the USG accept a commercialization strategy that is geared toward USG requirements (Federal, State and local municipalities) and needs vs. private commercial industry if the company has an established history of providing goods and services specifically engineered towards the Federal, State and Local authorities)of the USG?

DHS SBIR Commercialization Strategies should demonstrate a viable approach for the technology to be transitioned to the intended end user identified in the topic.

8 Appendix A Topic Number DHS251-001

Section 3.4 Commercialization Strategy

Will the USG acceptance criteria allow for a suite of testing modalities ( qty 2) specifically targeted to identify the chemical makeup, production and ownership of the targeted material (ownership defined as: "origin or source of a sample, production and potential manipulation) to compare to existing and to be created federal databases currently within law enforcement? There is no inherent issue with multiple testing modalities. The offeror would need to determine the best approach.

9 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Description: Paragraph 2

There is a description in this paragraph that the capability could be "...portable analysis instruments..." What are the size, weight, and power (SWaP) restrictions for the prototype and subsequent production models? Portable should be able to be carried by a single human and should have self-contained power able to last 12 hours.

10 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Description: Paragraph 2

There is a description in this paragraph that the capability could be "...portable analysis instruments..." What tools are currently being used by the USG in an attempt to meet the current Federal needs? A variety of COTS tools are currently being used, and are able to be found via publicly available research.

11 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Description: Paragraph 2

This paragraph mentions innovative ideas to rapidly extract unique signatures from samples — Are there specific restrictions on the type of human DNA (hDNA) signatures detected from the samples? E.g: Forensic investigative genetic genealogy (FIGG) The identification of hDNA has not been identified as a requirement.

12 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Description: Paragraph 2

This paragraph mentions innovative ideas to rapidly extract unique signatures from samples — What is the definition of rapid?

(Seconds (chemical analysis), Minutes (hDNA), Hours, Days) Rapid should be commesurate or better than the current standard achievable for the subject method.

13 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Description: Paragraph 2

This paragraph mentions innovative ideas to rapidly extract unique signatures from samples — Please define the secondary/confirmation analysis and how the USG would want this to fit into the proposed pipeline? E.g: National Laboratory (FBI), Combined DNA Index System (CODIS), the current unclassified national hDNA database that allows law enforcement agencies to compare DNA profiles. Any developed tool would be part of a variety of both internal and external processes.

14 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Description: Paragraph 2

This paragraph mentions innovative ideas to rapidly extract unique signatures from samples — Please define the confidence level requirements for the proposed prototype. Target confidence would be 90 percent.

15 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Phase 1 Description

Phase 1 includes the use of publicly available spectral libraries provided by the USG. Please define the current publicly available databases the USG will provide. Publicly available databases would not be provided by USG. No GFI will be provided in Phase I. Discussions regarding suitable public data or GFI can be considered for Phase II.

16 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Phase 1 Description

Phase 1 includes the use of publicly available spectral libraries provided by the USG. what level the spectral libraries within the database are subject to Quality Control prior to upload of the spectra? This has not been defined.

17 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Phase 1 Description

Phase 1 includes the use of publicly available spectral libraries provided by the USG. When are the use of publicly available libraries as data sources no longer acceptable during the development of the prototype?

Publicly available databases would not be provided by USG. This would be determined based on the maturity of the solution provided.

18 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Phase 1 Description

DHS S&T desires to "supply sufficiently unique signatures to link the emergence of drugs from the same producer." Does DHS have prior knowledge of the producer (site, suspects) and are trying to link signatures to that known producer? Or, is DHS seeking to link signatures across seizures (CONUS/OCONUS) that may not yet be identified? Either scenario could be possible.

19 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Phase 1 Description

DHS S&T desires to "supply sufficiently unique signatures to link the emergence of drugs from the same producer." Will DHS S&T Have access to CODIS and similar law enforcement databases? We do not have access to law enforcement databases.

20 Appendix A Topic Number DHS251-001

Appendix A, DHS251-001; Phase 1 Description

DHS S&T desires to "supply sufficiently unique signatures to link the emergence of drugs from the same producer." Will DHS S&T Have access to partner nation law enforcement databases? We do not have access to law enforcement databases.

21 Appendix A Topic Number DHS251-001

The solicitation mentions that the proposed technology should have the capability to identify the batch or source of fentanyl.

However, I am unclear about the number of different batches being seized by law enforcement and the specific differences among them. Are these batches distinguished by variations in color, chemical composition, or impurities?

The solutions proposed should be effective regardless of number of batches seized and the characteristics to be used would be defined based on the proposed approach.

22 Appendix A Topic Number DHS251-001 For detection, does the packaging need to stay undisturbed or can the package barrier be compromised and/or the package opened, and contents removed for testing?

Our approach is always to protect the operator from exposure to any harmful substances. Offerors should propose the best way to access the material for their solution. It is important to note, the topic is not seeking solutions for detection.

23 Appendix A Topic Number DHS251-002

AI-Generated Disruptions:

While our expertise includes addressing AI-driven disruptions, such as attacks on emergency response systems (e.g., AI-generated 911 calls), would DHS consider this capability relevant to the objectives outlined in this topic?

Yes – with the understanding that PSAPs today may not be interconnected across ESInets, so the challenge would remain how to get the data from the learning models to those PSAPs not connected.

24 Appendix A Topic Number DHS251-002

Technical Alignment

Could you clarify the priority DHS places on real-time data processing and AI/ML-driven solutions for NG911 systems?

The topic requires the capability of extracting data from PSAPs and using AI/ML to detect anomalies and threats such as Denial of Service Attacks. Also, we want to enable the capability to take the “learned data form multiple AI systems.

Presumably, PSAPs may use their own AI/ML or LLMs to collect data and “learn” about threats and data trends- but there is no means to share this “learning” with other PSAPs.

25 Appendix A Topic Number DHS251-002

Technical Alignment

Are there specific interoperability standards or technical requirements for integrating proposed solutions with existing systems like Emergency Services IP Networks (ESInets)?

Currently, we do not believe that there are standards for integrating solutions— perhaps the solution would come up with an approach.

26 Appendix A Topic Number DHS251-002

Technical Alignment

Would solutions that focus on anomaly detection and automated updates, as seen in electronic warfare technologies, align with the situational awareness objectives for NG911?

Yes, solutions that focus on anomaly detection and automated updates align with the situational awareness objectives for

NG911.

27 Appendix A Topic Number DHS251-002

Cybersecurity and Privacy

For NG911 systems, are there particular cybersecurity threats that DHS is prioritizing, such as ransomware or data breaches? Prioritizing trending on call flow and DOS attacks first – other threats are secondary.

28 Appendix A Topic Number DHS251-002

Cybersecurity and Privacy

For the video communication security topic, how critical is integration with existing video platforms (e.g., Zoom, Microsoft Teams) versus developing standalone solutions? Integration with existing video platforms is fine, but data analytics should be prioritized.

29 Appendix A Topic Number DHS251-002

Proposal Expectations

Could you provide additional details on how DHS defines “innovation” in the context of this solicitation?

In the context of this solicitation, "innovation" is defined as addressing the solution in a novel way that may not have been done before.

30 Appendix A Topic Number DHS251-002

Proposal Expectations

Are dual-use solutions that can be adapted for other federal agencies (e.g., defense, law enforcement) considered advantageous in the evaluation process? Dual use could be seen as advantageous, depending on the ability to most effectively address the topic requirements

31 Appendix A Topic Number DHS251-002

Proposal Expectations

Are there specific formatting requirements or additional documentation (e.g., compliance matrices, certifications) required for proposal submission? Yes, formatting requirements can be found in the solicitation, subsection 3.4.

32 Appendix A Topic Number DHS251-002

Strategic Considerations

Are there opportunities to engage DHS stakeholders during Phase I development to refine alignment with operational needs?

Yes, DHS can assist in providing opportunities to engage DHS stakeholders during Phase I development to refine alignment with operational needs.

33 Appendix A Topic Number DHS251-002

Strategic Considerations

Beyond this solicitation, are there broader DHS initiatives or long-term goals that align with capabilities like Radiant Expanse’s AI-driven signal processing and real-time updates? This solicitation is only seeking responses to the topics in Appendix A.

34 Appendix A Topic Number DHS251-002

Procurement and Submission Logistics

Can components of the Radiant Expanse project, developed under prior R&D efforts, be integrated into a Phase I proposal, provided they align with the solicitation’s objectives?

The approach to take must be determined by the offeror and should address the primary requirements that are in scope. If is not recommended to force other capabilities that do not meet the requirements, as the proposals will be evaluated based on how the solutions meet the topic requirements in the solicitation.

35 Appendix A Topic Number DHS251-002

Procurement and Submission Logistics

Are there specific restrictions or guidance regarding subcontractor involvement or partnerships with academic institutions during Phase I?

Yes. Among them are limits to the amount that can be subcontracted out and information on foreign relationships. The full requirments are found within the solicitation.

36 Appendix A Topic Number DHS251-002

Procurement and Submission Logistics

Could you clarify export control considerations specific to technologies involving secure communication pathways and AI-enhanced data models?

The Department of State has the responsbility for determinations related to International Traffic in Arms Regulations (ITAR) and the Department of Commerce has the responsibility related to the Export Administration Regulations (EAR), with respect to export controls.

37 Appendix A Topic Number DHS251-002

Procurement and Submission Logistics

What specific data rights protections are applicable under this solicitation, particularly for AI-driven innovations like those utilized in Radiant Expanse? See "SBIR Technical Data Rights" in APPENDIX B – DEFINITIONS of the solicitation.

38 Appendix A Topic Number DHS251-002

Please can you provide the types of metadata that the DHS is looking to capture? This was taken from the last paragraph on page A3:

"This topic seeks innovative methods to develop the capability to collect and share emergency call metadata amongst PSAPs and ESInets while maintaining and assuring all necessary and required data privacy rules are maintained related to the original 911 calls such as HIPAA information, restricted law enforcement data, and security protocols built into the original call center program (bomb calls, stakeouts, undercover operations)."

Examples such as call hold-time, here are some examples: EMS, FIRE, Law enforcement, administrative), origination location, carrier, call type (land line, VOIP, SMS). Recommend some research to come up with others—we want innovation on types of data incoming and what can be done with it.

39 Appendix A Topic Number DHS251-002 Assuming we are successful delivering the R&D and platform for phases 1 and 2, can we offer our solution as a flexible and customizable platform to future government entities (PSAP as a Service concept). You can market to anyone--the objective is to make this a viable business system.

40 Appendix A Topic Number DHS251-002 Does the DHS-SBIR prefer a Cloud-based, Hybrid, or On-site solution?

Propose the solution that you think is best fit for the requirements provided in the topic in the solicitation. Consider sustainment (i.e., costs), flexibility and resiliency and security

41 Appendix A Topic Number DHS251-002 Does DHS already have pilot PSAPs signed up that are ready to meet with the selected vendor to help understand the data flows and data collected? No, but DHS may be able to facilitate subsequent to contract award.

42 Appendix A Topic Number DHS251-002 Is there a DHS team that will meet with the vendor to help illuminate the regulations and reporting requirements in place at the federal level? Yes. DHS will engage with NENA, NG911 Interoperability Task force and DoT

43 Appendix A Topic Number DHS251-002 Are any specific problems that DHS is interested in solving within the general NG911 domain, and would you be open to a discussion to help us understand these challenges to ensure the proposal fully meets the needs of DHS?

We addressed the high level requirements within the topic area – there are a number of other issues that exist- but these may expand the scope of the effort.

44 Appendix A Topic Number DHS251-002

Data Collection and Requirements:

What specific call data metrics are considered essential for collection (e.g., call volume, source, duration, geolocation)?

Yes – location, call holding, type of call, if possible carrier (type of call- cellular, VoIP, POTS), Type of call EMS, FIRE, Law Enforcement

45 Appendix A Topic Number DHS251-002

Data Collection and Requirements:

Are there any standardized data formats or protocols already established for call data reporting across PSAPs? The Government will provide response to this question in a subsequent amendment to this solicitation.

46 Appendix A Topic Number DHS251-002

Data Collection and Requirements:

Is there a preference for centralized vs. decentralized data storage for collected call data? No inherent preference- solution should best addresss topic requirements in the solicitation.

47 Appendix A Topic Number DHS251-002

Privacy, Security, and Compliance:

What are the specific HIPAA and FCC compliance requirements for call data storage and transmission?

We are looking for you to come up with recommendations—We know for a fact that PII data is not transferable outside the

PSAP.

48 Appendix A Topic Number DHS251-002

Privacy, Security, and Compliance:

Should the solution be designed for both Personally Identifiable Information (PII) and non-PII data? No – PII data will too challenging- We need to ensure that the data we collect can be verified (to protect PII data).

49 Appendix A Topic Number DHS251-002

Privacy, Security, and Compliance:

Are there existing standards or frameworks for data anonymization and encryption that should be followed? What are your recommendations- data standards and frameworks? This is the innovation part.

50 Appendix A Topic Number DHS251-002

Privacy, Security, and Compliance:

What cybersecurity frameworks should be adhered to (e.g., NIST Cybersecurity Framework, Zero Trust Architecture)? Yes. We need to ensure that the solution does not make PSAPs more vulnerable.

51 Appendix A Topic Number DHS251-002

System Integration and Interoperability:

What standards exist for PSAP and ESInet integration (e.g., NG911 IP standards, NENA i3)? NG911 and NENA I3 and perhaps 3GPP standards are in play.

52 Appendix A Topic Number DHS251-002

System Integration and Interoperability:

Will there be a requirement for the solution to integrate with legacy 911 systems or focus exclusively on NG911? Ideally focus on NG911 but legacy solutions will be a bonus.

53 Appendix A Topic Number DHS251-002

System Integration and Interoperability:

What communication protocols and APIs should the system support for interoperability between PSAPs? NG911 and NENA I3 and perhaps 3GPP standards are in play.

54 Appendix A Topic Number DHS251-002

Real-Time Monitoring and Anomaly Detection:

What is the acceptable latency for real-time data reporting and alerting? Unclear what the art of the possible is?

55 Appendix A Topic Number DHS251-002

Real-Time Monitoring and Anomaly Detection:

What types of anomalies should the system detect (e.g., call spikes, service degradation, cyber threats)? Call spoofing, location obfuscation (if detectable) maybe others- recommend you propose what are good indicators

56 Appendix A Topic Number DHS251-002

Real-Time Monitoring and Anomaly Detection:

Are there any specific thresholds or event types that must trigger alerts? This should be selectable based on requirements from research and proposed effort.

57 Appendix A Topic Number DHS251-002

Real-Time Monitoring and Anomaly Detection:

Should the solution support customizable reporting per PSAP? If so, how? This should be selectable based on requirements from research and proposed effort.

58 Appendix A Topic Number DHS251-002

AI/ML and Data Sharing:

Are there preferred approaches for sharing AI/ML datasets across PSAPs while preserving data privacy? We are looking for your innovative ideas.

59 Appendix A Topic Number DHS251-002

AI/ML and Data Sharing:

Should the system support federated learning or collaborative AI models between PSAPs? Yes ideally.

60 Appendix A Topic Number DHS251-002

AI/ML and Data Sharing:

What mechanisms should be in place for PSAPs to control their data sharing permissions? We are looking for your innovative ideas.

61 Appendix A Topic Number DHS251-002

Testing and Evaluation:

Will DHS provide any simulated datasets or test environments for Phase I, or will synthetic data need to be created? Synthetic data will probably be required as NG911 systems are just beginning to roll out. (Probably a phase II need)

62 Appendix A Topic Number DHS251-002

Testing and Evaluation:

What level of testing is required to demonstrate system performance and compliance in Phase I? Phase I testing is not required. But feel free to propose what is possible for a 5 month solution.

63 Appendix A Topic Number DHS251-002

Testing and Evaluation:

Should the prototype be tested in both controlled testbeds and live PSAP environments? Maybe in Phase II

64 Appendix A Topic Number DHS251-002

Technical and Infrastructure Considerations:

Are there specific infrastructure preferences, such as on-premise, cloud-based, or hybrid solutions? Feel free to innovate – recommend the optimum solution

65 Appendix A Topic Number DHS251-002

Technical and Infrastructure Considerations:

Will the system need to support a specific number of concurrent PSAPs during Phase I testing? Phase I testing is not required. But feel free to propose what is possible for a 5 month solution.

66 Appendix A Topic Number DHS251-002

Technical and Infrastructure Considerations:

What are the requirements for system scalability across multiple PSAPs and ESInets? The Government will provide response to this question in a subsequent amendment to this solicitation.

67 Appendix A Topic Number DHS251-002

Phase I Deliverables and Metrics:

What key performance indicators (KPIs) will be used to measure the success of Phase I? Phase I is a proof of concept- it should identify approach and should describe your solution to a level that is satisfactory.

68 Appendix A Topic Number DHS251-002

Phase I Deliverables and Metrics:

Are there specific documentation or reporting requirements for Phase I deliverables?

Phase I is a proof of concept- we have seen proposals that are a conceptual approach and design all the way to working prototypes (prototypes are not required for Phase I). It is up to you.

69 Appendix A Topic Number DHS251-002

Phase I Deliverables and Metrics:

Should Phase I results include recommendations for Phase II system enhancements? Yes

70 Appendix A Topic Number DHS251-002

Operational Use and Stakeholder Engagement:

Will there be a need for PSAP operator training as part of the Phase I effort?

No. Phase I is a proof of concept. Should flush out the questions you answer or propose those risk or questions that will be done during phase II

71 Appendix A Topic Number DHS251-002

Operational Use and Stakeholder Engagement:

Who are the primary stakeholders and end-users for testing and feedback during Phase I?

DHS and possibly some PSAPs who wish to work with us. DHS will provide the contacts, during the contract performance, through our relationships.

72 Appendix A Topic Number DHS251-002

Operational Use and Stakeholder Engagement:

Should the system design consider varying operational procedures between states and jurisdictions? System should be flexible/adaptable enough to be applicable for various states and jurisdictions.

73 Appendix A Topic Number DHS251-002

Budget and Resource Clarifications:

Will any government-furnished equipment (GFE) or software be provided for Phase I? No

74 Appendix A Topic Number DHS251-002

Budget and Resource Clarifications:

Should travel costs for testing at DHS-designated sites (e.g., Texas, California) be included in the Phase I budget? If you need to propose it based on your proposed approach – up to you. If there are assumptions please provide.

75 Appendix A Would the use of AI for cybersecurity enhancement be discussed as a part of the solution?

We are looking for your innovative ideas. Offeror's can include innovations they believe could meet or exceed the topic requirements.

76 Appendix A Topic Number DHS251-003

For a walk-through threat detection system, we were wondering if there are requirements or solution preferences for either:

Object detection from video data to identify, categorize, and localize objects in individual frames of video data without temporal continuity (for instance, during a single scan at an airport check point); or Video object tracking to follow the movement of an object across multiple frames of video data (i.e., tracking an object’s trajectory over time, after the object is initially detected)? For instance, tracking an item as an individual walks from point A to point B in an airport. The Government will provide response to this question in a subsequent amendment to this solicitation.

77 Appendix A Topic Number DHS251-003

Object Counting: For either object detection or video object tracking, we were wondering if there are object counting requirements, in terms of counting the number and type of detected objects and anthropometric characteristics per individual, and/or among a group of individuals over time? The Government will provide response to this question in a subsequent amendment to this solicitation.

78 Appendix A Topic Number DHS251-003

Cloud-computing vs. On-Device vs. Edge computing: We were wondering if there are requirements for data processing to operate in either in a cloud-based environment or on-device (iOS or Android smartphone), or in an edge computing environment? The Government will provide response to this question in a subsequent amendment to this solicitation.

79 Appendix A Topic Number DHS251-003 Continual Model Training vs. Single Deployment of a Static Model: Are there requirements for continual model training after initial deployment, to improve model performance over time? The Government will provide response to this question in a subsequent amendment to this solicitation.

80 Appendix A Topic Number DHS251-003

UI for Displaying & Querying Real-time Detection Results: We were wondering if there are requirements for how real-time results should be displayed to product users, queried for real-time analysis, or stored and exported for future analysis (i.e., specific alerts to display when an item is detected, data storage formats for ML model results in JSON, XML, etc.)? Or if the UI for displaying model results to a smartphone or other device would be beyond the scope of the current solicitation? The Government will provide response to this question in a subsequent amendment to this solicitation.

81 Appendix A Topic Number DHS251-003

The SBIR indicates that the intended end use of the model by TSA is as a part of the "Screening at Speed" program. Does this imply that the model will be used in conjunction with environmental features that reduce noise such as the backscatter machines or the proposed screening tunnels?

In Phase I, 1) determine the technical feasibility of the proposed on-person screening stream of commerce analysis tool and 2) demonstrate analysis on preliminary proof of concept algorithm to develop the software/hardware requirements. The environment (e.g., laboratory, operational) will be at the discretion of the awardee. At a minimum, the On-Person Screening Stream of Commerce Analysis Tool should be designed to analyze data (e.g., CCTV footage) at the area before an airport security checkpoint, often referred to as the queueing area or pre-checkpoint zone, is a transitional space where passengers prepare to go through the screening process.

82 Appendix A Topic Number DHS251-003 Are there current examples of the mentioned "threat detection systems currently being developed/sponsored by the Screening at Speed program" that are publicly available for observation? No

83 Appendix A Topic Number DHS251-003 Is there any need to identify the brand/model of articles of clothing/accessories, or should the model simply identify items as shown on the individual e.g.: "white sneakers", "red jacket", "gold watch?"

No. The tool is to Identify and catalogue clothing articles such as jacket type (e.g., button-up, zipper, blazer, denim, leather) clothing types (e.g., shorts, dress, blouse, long sleeves, short sleeves, jeans, etc.), headwear types (e.g., turbans, ski cap, baseball cap, derby, scarves), shoe types (e.g., dress shoe, high-heels, sneakers, sandals, boots, etc.).

84 Appendix A Topic Number DHS251-004

Digital Injection Attacks Focus:

Does DHS prioritize solutions that preemptively block digital injection attacks by ensuring the integrity of live video streams during real-time interactions, rather than relying on post-incident detection methods? Yes the focus of the topic is prevention

85 Appendix A Topic Number DHS251-004

Secure Video Communication Systems:

Would a solution focusing on real-time integrity verification of live video streams across commodity devices—immune to known and emerging digital injection attacks—fully meet DHS’s goals for secure video communications? Yes

86 Appendix A Topic Number DHS251-004

System Integration Requirements:

Are there specific interoperability requirements, such as mandatory integration with DHS-approved video conferencing platforms (e.g., Microsoft Teams, Zoom) or adherence to standards like CEN/TC 224?

The ability to integrate with existing widely used videoconferencing software is important. Demonstrating the ability to integrate with one widely used solution and an approach to integrate with others is key. The ability to prevent attacks described in FprCEN/TS 18099:2024.

87 Appendix A Topic Number DHS251-004

Notification and User Feedback:

How critical is the requirement for user-facing notifications about security changes during video interactions? Would a real-time, non-intrusive alert system fulfill DHS’s needs? Yes

88 Appendix A Topic Number DHS251-004

Distinctiveness of Proposed Solution:

To what extent must the proposed solution differentiate itself from existing commercial Presentation Attack Detection (PAD) and liveness detection technologies? Should it address challenges like live deepfake attacks more broadly or exclusively focus on ensuring real-time video integrity?

The solution must demonstrate meaningful research and development that provides novel value in ensuring real-time video integrity distinct from existing commercial offerings.

89 Appendix A Topic Number DHS251-004 Can the use of AI-enhanced video and customer service capabilities be a part of the platform?

The focus of this topic is establishing and maintaining confidentiality and integrity of the video and audio stream. The offeror is free to include innovations they believe could meet or exceed the topic requirements.

90 Appendix A Topic Number DHS251-004 Is the ideal software solution focused on detecting hardware such as a maliciously injected camera or is it focused on signs of a live deepfake in the end video?

The topic is outcome focused on establishing and maintaining confidentiality and integrity of the video and audio stream.

Recognizing the diversity of threats the offeror is encouraged to describe the key threats they perceive and how their proposed R&D addresses those threats.

91 Appendix A Topic Number DHS251-004 Does the customer have any particular type of live deepfaking techniques it is most concerned about?

The topic is outcome focused on establishing and maintaining confidentiality and integrity of the video and audio stream.

Recognizing the diversity of threats the offeror is encouraged to describe the key threats they perceive and how their proposed R&D addresses those threats.

92 Appendix A Topic Number DHS251-004 In addition to the live deepfake injection that includes video + audio, are you interested in detection of only voice injection or voice cloning attacks? No the scope is limited to video calls.

93 Appendix A Topic Number DHS251-004 To what extent is the proposed solution expected to integrate with existing video platforms like Microsoft Teams, Zoom, or Webex?

The ability to integrate with existing widely used videoconferencing software is important. Demonstrating the ability to integrate with one widely used solution and an approach to integrate with others is key.

94 Appendix A Topic Number DHS251-004 Should the proposed solution avoid storing any sensitive video data locally or in the cloud to minimize privacy risks?

The focus of this topict is establishing and maintaining confidentiality and integrity of the video and audio stream. Storing data is not a DHS requirement.

95 Appendix A Topic Number DHS251-004 Are there specific privacy regulations that the solution must comply with? All solutions should comply with relevant privacy regulations, which can vary depending on the solution proposed.

96 Appendix A Topic Number DHS251-004 Will the solution be expected to function primarily in enterprise environments, or should it also accommodate lower-resource environments such as personal consumer devices on unstable networks?

It should be able to accommodate both use cases. This is expected to work where Wi-Fi, strong cellular connectivity is available. This is not expected to work in bandwidth constrained or challenged environments.

97 Appendix A Topic Number DHS251-004 For the video communication security topic, how critical is integration with existing video platforms (e.g., Zoom, Microsoft Teams) versus developing standalone solutions? It is a key consideration.

98 Appendix A Topic Number DHS251-005

Can you please provide model numbers of the most popular biometric devices currently used by DHS stakeholders for contact fingerprint, contactless fingerprint, iris, and face capture? This will help ensure our solution aligns with the most widely used devices in DHS operations.

Current market devices for fingerprint or iris capture that are both iOS compatible and Android compatible are of initial interest.

99 Appendix A Topic Number DHS251-005 Will DHS provide access to datasets, test devices, or biometric capture hardware during Phase I to assist with modeling and simulation? No

100 Appendix A Topic Number DHS251-005 Given DHS stakeholders’ focus on iOS, should we prioritize iOS compatibility in Phase I and address Android functionality in later phases? iOS and Android are equally of interest. However, Android already supports wired connections, iOS does not.

101 Appendix A Topic Number DHS251-005 Does the adapter need to support power delivery for other devices or external peripherals beyond the biometric capture device? No

102 Appendix A Topic Number DHS251-005 Do the biometric capture devices have additional port requirements beyond Lightning and USB-C, such as micro-USB or proprietary connectors? Should we consider adapters or compatibility for other standards? No

103 Section 1.4 Section 1.4 When will we know if funding is available? If it is not available, will this effort be stopped or can it be restarted once funding is secured. If that is the case, do we have to resubmit the bid?

Please see the table in Section 1.4 of the solicitation, Key Dates and Events. At this time, we do not anticipate any issues with the availability of funding. Proposals submitted under the 25.1 Solicitation will be considered valid for 180 days, it is unlikely that you would need to resubmit in the case of a lapse of funding.

104 Section 3.7 Section 3.7 Regarding the DHS Phase II Transition Rate Benchmark, our company is new to the SBIR program and bidding process. Are we still qualified to bid if we have not received any previous Phase 1 awards?

Yes, there is no requirement to have been awarded a prior SBIR award. In section 3.7, the Phase I to Phase II Transition Rate requirement applies only to SBIR and STTR Phase I applicants that have received more than 20 Phase I awards over the past 5 fiscal years, excluding the most recent year.

The DHS SBIR Program Office encourages all small business concerns, including small disadvantaged, women-owned, veteran-owned, service-disabled veteran-owned, and socially and economically disadvantaged small business concerns, with the capability to conduct research and development for homeland security-related topic areas described in Appendix A, and to commercialize the results of that Research /Research & Development (R/R&D), to submit proposals in response to topics described in this Solicitation.

105 Section 1.3 Section 1.3 Are we expecting to submit a bid or plan for phase 3 at this time? Or is phase 3 submission only needed for phases 1 and 2 awardees?

While the Phase II proposal process is covered in this Solicitation, at this time this solicitation requests and accepts Phase I proposals only. See Section 1.3.

106 Section 2.1 Section 2.1 Please refer to us for all the forms (such as form 11055) the offeror has to submit.

The solicitation includes information on all required forms. The portal also provides guidance for the completion of fields that will populate a form or indicate if a document is required to be uploaded. All forms generated from populated data should be reviewed in the system by the offeror prior to submission to ensure accuracy. For Technical Support for proposal submission to the portal the helpdesk contact information and availability is on the bottom of the SBIR portal homepage:

https://sbir.dhs.gov/sbir/public.

107 Appendix A Appendix A Please confirm there are only 5 research topics in Appendix A? Will there be additional topics in the future? Currently DHS SBIR issues one solicitation per year and this year's solicitation, the 25.1, has 5 topics.

108 Appendix A Appendix A Do the offerors have to submit individual write up for each of the 5 topics in Appendix A? Can we provide a comprehensive R&D that discusses all 5 topics?

You are allowed to submit to more than one topic, but individual proposals must be submitted to each topic for which the offeror would like to be considered for award.

109 Section 3.1 Section 3.1 The Phase 1 15-page limit and Phase 2 40-page limit are applicable to all 5 topics or is it 15-page limit and 40-page limit for each topic?

For this solicitation phase, we are only accepting proposals for Phase 1 and there is a 15 page limit for each technical proposal submitted. Multiple proposals can be submitted to a topic or to multiple topics but they must all be submitted separately. For Phase II similarly, the page limit will be 40 pages per technical proposal.

110 Section 3.2 Section 3.2 Is the Technical Abstract and Project Aims sections word-limitation applicable to all 5 topics at once or is it unique for each topic?

The Technical Abstract and Project Aims sections discussed in section 3.2 of the solicitation should be unique per proposal submitted.

111 Section 3.5 Section 3.5 Is the phase 1 Post Award travel cost a part of the overall cost (not to exceed $175,000) or will be cost be excluded from the phase 1 proposal cost?

The overall cost is all inclusive with the exception of TABA, in Phase I. In Phase II the TABA is inclusive of the threshold. Please see section 5.11 of the solicitation for information regarding TABA.

112 Section 3.6 Section 3.6 Please clarify whether the Commercialization Report is a part of phase 2 or phase 3?

The Commercialization Report is required for Phase II proposal submission. Phase III proposal submission requirements may vary based on the contracting office executing the award.

113 Appendix A Appendix A Is the DHS-SBIR looking for a fully functional prototype for phase 2? Will we receive additional functional requirements in the future to complete the prototype and demo?

Please refer to the Phase II section of each topic in Appendix A for more information regarding the deliverable expectations. A demonstratable prototype is required as part of Phase II. Only Phase I awardees will be eligible to compete for a Phase II award.

114 Section 2.4 Section 2.4 We do not intend to use offshore or non-citizen resources at this time. If the need arrives in the future (phase 3), can we still ask for permission?

It may be possible to add individuals. For Phase I and Phase II, the addition of a foreign individual would need to be requested and approved prior to thier participation. This solicitation does not define the terms of a Phase III effort. The process for adding individuals to a Phase III would need to be addressed at that time.

115 Section 1.3 Section 1.3 What is the anticipated time for phase 3 deployment?

A Phase III, which is not SBIR Funding, does not always get awarded. The award would occur upon available funding from a potential stakeholder for the SBIR developed solution, who is interested in pursuing addition work or procurement.

116 Section 1.3 Section 1.3 If we are selected for phase 3, will we be the exclusive solution provider? Or will there be multiple solution providers.

A Phase III can be pursued for any work that derives from, extends, or completes efforts made under prior funding agreements under the SBIR program, using non-SBIR/STTR funding.