RFI Answers 1-122.pdf

A) Document Access

1) PGDS Availability.

PGDS v8.0 is available on SAM.gov. Respondents should use the most current posted version for any standards references.

2) CRPG Technical Appendices (CAD, electrical, standard layouts).

An updated CRPG and appendices was released on August 1, 2025. It can be found here:

https://www.tsa.gov/sites/default/files/checkpoint-requirements-and-planning-guide.pdf

Vendors may request supplemental information via CheckpointRequirements@tsa.dhs.gov

B) Technical Requirements

3) Performance Metrics for SPP effectiveness.

TSA evaluates via multiple operational and compliance metrics, including: APR observations, NTP completion pace, TIP performance, standard and PreCheck wait-time targets (e.g., <20 min standard, <10 min PreCheck), selectee find rate, AIT utilization, ATLAS activities, workforce performance observations by Federal TMs, and broader operational execution (data accuracy, equipment maintenance, incident management, reporting, SSI handling, staffing). Respondents should map proposed outcomes/KPIs to these areas.

4) AI/ML integration standards with existing checkpoint equipment.

Not specified in this RFI; vendors should describe standards used (e.g., model governance, auditability, false-alarm management), interfaces, safety cases, and how they will interoperate with current TSE where applicable.

5) Remote screening & centralized image review—cyber/privacy frameworks.

Not specified here; respondents should state the security architecture, applicable frameworks (e.g., NIST SP 800-53/800-171 controls), data-in-transit/at-rest protections, and data sovereignty posture.

6) Integrated system certification (multiple approved technologies).

TSA will continue to certify systems using the current process. If your detection chain depends on multiple systems, the specific chain configuration will be certified. Design and submit as an integrated detection chain.

https://www.tsa.gov/sites/default/files/checkpoint-requirements-and-planning-guide.pdf

C) Submission & Contracting

7) Response format & 20page limit (what’s- excluded).

Stay within page limits. TSA may disregard pages in excess. Excluded from the limit: cover pages, table of contents, glossary of acronyms, appendices, and indexes. Put technical details, drawings, and detailed pricing in an appendix.

8) Teaming arrangements preference.

TSA will review teaming arrangements without preference; justify why your teaming improves performance, speed, cost, or risk.

D) Implementation Considerations

9) Scalability parameters.

Design modular, scalable offerings deployable across a range of airport sizes/layouts. State any constraints or tailoring by category.

10) Infrastructure integration (power, HVAC, IT).

No fixed level is specified; describe assumed integration touchpoints and optionality by site— your solution should still be modular/scalable.

11) Pilot program timeline and selection criteria.

Not established yet; this RFI is to inform potential pilots. Propose your ideal pilot size, success metrics, and schedule assumptions.

E) Program Scope

12) Existing vs. new SPP sites.

No implementation plan established at this time. You may address both, explaining where your approach best fits.

F) Technology Innovation

13) Passwordless, privacy--preserving biometrics.

Welcome—submissions will inform future strategies. Explain privacy model, liveness, and opt--out pathways.

14) Decentralized identity / secure multi-party computation.

Welcome—submit approaches and tradeoffs.

G) Integration Expectations

15) Integration with CAT-2, Secure Flight.

No specific expectations are identified. TSA is exploring integrated, tech-forward solutions that reduce manual labor, incorporate AI/remote screening, improve passenger satisfaction, and handle surges. Describe your integration approach and APIs. -

H) Compliance & Certification

16) FedRAMP / NIST framework requirements now?

Not specified for this RFI. Propose your current authorizations (e.g., FedRAMP, SOC 2) and how you’ll meet U.S. Government controls if selected for pilots/production.

I) Privacy & Data Security

17) Biometric privacy (central storage avoidance).

Not specified here. Vendors may propose privacy-preserving patterns (-edgematch/no retention;

tokenization) and show compliance with applicable law/SSI handling. -

J) Evaluation & Pilots

18) Vendor--led pilots / limited demos.

TSA may partner on vendor-led- pilots that align to strategic priorities. Propose scope, evaluation plan, and governance.

19) Metrics for authentication technologies.

This is market research; define and justify your proposed performance metrics (accuracy, latency, throughput lift, false positive/negative, demographic performance) and how they map to TSA objectives.

K) Next Steps & Engagement

20) Industry engagement sessions / briefings.

TSA is considering additional engagements; monitor SAM and the RFI Q&A channel for updates.

21) Deadline extension request to Aug 8.

TSA has extended the submission deadline to Aug 15, 2025 05:00 pm EDT.

22) Budget disclosure.

This is market research; no budget provided.

23) Preferred first deployment (large vs. small hub).

Not specified; propose a deployment profile and rationale (risk, complexity, change management).

24) Workforce baseline data.

No additional information will be provided. Respondents should state assumptions and a data collection- plan.

L) Requested Information — Deployment & Logistics

25) Which solution elements to address in the deployment model?

Address all relevant elements for a turnkey outcome (technology, staffing concept, training, governance, integration, cybersecurity, logistics).26) Phased pilots prior to full deployment.

This RFI may inform future pilots; propose a phased approach and decision gates.

27) Ownership/lease of deployed equipment.

Not yet determined; submit both GFE and contractor owned-/leased options with cost/benefit and risk tradeoffs.

28) Implementation barriers.

Vendors should identify regulatory, legal, policy, SSI, labor, and integration barriers relevant to their approach and propose mitigations.

29) Submission time on due date.

Time not specified here; use SAM posting for the definitive deadline timestamp.

M) “Turnkey” Scope Clarification

30) Does “turnkey” mean full checkpoint or elements thereof?

TSA seeks modular, scalable solutions applicable across airport sizes. You may propose full checkpoint- or modular elements; clearly note scope limits, dependencies, and barriers.

31) Integration with legacy TSA systems; APIs; proposing enhancements.

Not prespecified; describe APIs, data exchange patterns, and any incremental enhancements you recommend.

32) Remote monitoring/centralized image review—data sovereignty & cybersecurity.

Not prespecified; propose your approach, including where data resides, cross- border controls, SOC operations, and audit.

33) Submitting solutions not yet commercially available.

Yes. Emerging concepts are welcome to inform strategy—explain TRL, path to validation, and risks.

34) Timeline from RFI to pilot awards / demos.

Not set; propose your recommended timeline and demo readiness.

35) CRPG appendices A/B/C access.

Update released ; request supplemental information via CheckpointRequirements@tsa.dhs.gov.

36) Is this RFI only for SPP usage?

Use this RFI to inform SPP related acquisition strategies; related innovations may also inform future TSA planning. -

37) Solutions that reduce/replace human labor.

Applicable. Clearly show safety, reliability, throughput impacts, detection impacts, and compliance.

38) Industry Day for “Checkpoint of the Future.”

None planned currently; TSA is considering additional engagements.

39) Checkpoint vs. checked baggage scope.

Your list captures the question; treat checked baggage interfaces as in scope only if they are integral to an end-to--end- checkpoint solution. Clarify boundaries in your proposal.

40) “Overall Rollout Plan” breadth.

Propose an end-to---end rollout covering TSE, ancillary IT/network, facilities considerations, training, staffing, change management, and regulatory milestones. -

41) TSA role—shift to regulator on standards/certification while airports set customer service metrics?

Undecided; respondents may propose governance models that preserve TSA regulatory oversight while enabling airport level service adaptation.

N) SPP Structure & Contracting Model

42) Transition to full turnkey from current TSE ownership/operations.

Not yet determined; propose transition paths (e.g., phased dual-ops, shadow period, asset transfer).

43) Will TSA contract centrally or will individual airports contract?

Not yet determined; this is market research and decisions follow analysis of responses.

44) Must SPP provider purchase existing TSE, or will TSA provide GFE?

Not yet determined; vendors should address both scenarios and pricing.

45) Will RFPs be airport specific- to reflect site uniqueness?

Contracting approach is not yet determined; this RFI informs strategies (including potential pilot programs at select airports).

46) Will TSA provide site -level TSE counts, workforce, passenger counts?

No—no additional information will be provided at this time. Vendors should state assumptions and a data -collection/validation plan.

47) One SPP provider vs. airport-by---airport awards.

Not yet determined; all options remain open pending responses.

48) Must provider cover both checked baggage and checkpoint?

Include your recommendation in the proposed solution—justify benefits, risk, and cost.

49) Opt--in vs. mandated by legislation.

This is market research to inform strategies/pilots; no decision stated.

50) Mixed opt--in scenarios (hub/spoke misalignment).

Same as above; describe how your model handles mixed participation with minimal disruption.

51) Are all technologies in Section 3 required?

No—treat them as examples; propose a modular set that achieves the objectives, with scope limits and barriers clearly noted.

52) Must remote screening be TSA-operated or third--party-?

Open to options; justify how your approach meets security, performance, and oversight needs.

53) Are offerors required to cover all areas vs. a subset?

Subsets are acceptable; again, modular, scalable solutions are sought—state limits and dependencies.

54) Multiple SPP providers collaborating (unique services/TSE) but contracting individually?

Open—TSA will consider all proposed solutions; explain governance, SLAs, and accountability across providers.

55) Is off-prem remote screening required; hub--and---spoke assumed?

Not required; propose architectures (including hub-and--spoke-) and note tradeoffs.

56) Are listed technologies examples vs. requirements?

Treat as examples—propose cost/efficiency/flexibility enhancements beyond the list.

57) TSA-to---remote interface & cybersecurity requirements.

Not specified here; vendors should propose interface specs and cybersecurity controls aligned to federal standards; TSA will refine in subsequent phases.

58) Business intelligence / data expected; decisions enabled.

Not specified; describe telemetry, operational analytics, and decision support you provide (e.g., staffing optimization, queue predictions, asset health).

59) Current checkpoint data collected by TSA and continuity by TSE type.

No detailed inventory provided here; propose a data publishing schema and mapping to TSA/airport decision needs.

60) SPP ability to capture/own/analyze/on-sell non--security, non---PII data.

Not specified; if proposing, ensure no PII/SSI, clear consent where applicable, and value back to TSA/airports (e.g., performance dashboards).

61) Traditional hub-and---spoke equipment/training deployment?

Provide a modular, scalable concept; hub-and--spoke- is one acceptable pattern—explain why.

62) Staffing/headcount performance standards.

Not provided at this time.

63) Airport/Airline application integrations—examples.

Not specified; describe candidate integrations (e.g., airport ops, resource mgmt, airline DCS) and security boundaries.

64) Who installs the equipment—provider vs. checkpoint integrator?

Not specified; propose your approach. Note: TSA may use pilots to inform this decision.

65) Should the provider propose screening personnel; can TSA share labor rates/standards?

Not specified in this RFI. If proposing, provide labor categories, quals, training plans, and wage compliance strategy.

66) Would congressional authorization be required to expand SPP to full turnkey (tech, personnel, ops)?

Not answered in this document; respondents may note dependencies on statutory authorities and propose interim models.

67) Sharing TSA performance standards, security requirements, SSI/cyber controls, passenger experience metrics, certifications.

No additional information will be provided at this time. Propose compliance assumptions and list required government furnished- references for a next phase.

68) Additional internal detailed guidelines beyond CRPG/PGDS/ACL.

No additional information will be provided at this time. Design to public standards and identify deltas you would need clarified later.

69) Recurring checkpoint operational metrics to publish; technical data expected.

Not specified; propose your operational metrics set and reporting cadence.

70) Lifecycle ownership/maintenance—assume provider or GFE?

Not specified; provide pricing/risks for both provider--owned and GFE models.

71) Regulatory/legal/procurement limitations being explored (vetting time, SSI access, unions).

Not specified; vendors should identify relevant constraints and mitigation in their proposals.

72) Industry working group / innovation forum.

TSA is considering additional engagements.

73) Government indemnification against losses due to screening failures.

Not addressed here; respondents should assume no indemnification unless expressly provided in a future solicitation/contract.

74) Applicability across airport categories (CAT X–IV).

Assume solutions should scale across categories; specify any category dependent- limits.

75) TSA PerSec responsibility for background checks / hiring authority.

Not specified; propose how your model integrates with existing PerSec processes and timelines.

76) Disposition of TSA-owned- equipment and removal responsibilities.

Not specified; propose approaches for non-integrable legacy TSE (de-install, disposal coordination, cost responsibility).

77) Workforce optimization flexibility vs. adherence to TSA staffing models.

Not specified here; propose optimization capabilities aligned to TSA SOP/directives and describe what changes would be needed to realize savings.

78) Ongoing oversight by FSDs.

Not specified; assume FSDs retain oversight responsibility and design your governance model accordingly.

79) IDIQ/task order- award process.

Not yet established. You may suggest contracting constructs that best fit your solution (e.g., IDIQ with airport task orders).

80) Section 3A “Technology Integration”—integrate with existing vs. provide capability?

Assume both: show how you integrate with existing systems and/or provide the capability when integration is impractical; specify decision criteria and migration paths.

81) Page limit- exclusions (title page/TOC/list of figures) confirmed.

Confirmed—cover pages, TOC, glossary, appendices, indexes do not count toward the 20 -page limit.

82) Unbundling technology from operational services.

TSA is particularly interested in modular, scalable offerings that can be deployed across a range of airport sizes and layouts. This could include both bundled and unbundled capabilities. See the RFI for objectives of the SPP solutions.

83) Orchestration model for SPP-operated airports.

The respondent is expected to provide this information as part of their solution.

84) Amendment/expansion of existing airport assets.

The respondent is expected to provide this information as part of their solution.

85) Main driver: cost vs. efficiency/performance.

TSA is exploring opportunities to modernize the program by incorporating integrated, technology-forward solutions that:

• Reduce reliance on manual labor

• Incorporate AI-driven threat detection and remote screening

• Improve passenger satisfaction

• Increase adaptability during surge events or staffing constraints

86) Cost-beneficial business case requirement.

See the Cost Considerations in the Requested Information section of the RFI.

87) Next steps after the RFI.

This RFI is for market research purposes and does not constitute a Request for Proposal (RFP).

TSA may use the results of this RFI to inform future acquisition strategies and potential pilot programs at select airports.

88) Publication of received submissions.

No.

89) Expected planning moving forward (RFP, implementation, milestones).

This RFI is for market research purposes and does not constitute a Request for Proposal (RFP).

TSA may use the results of this RFI to inform future acquisition strategies and potential pilot programs at select airports.

90) Suggesting technologies outside TSA's current scope.

Respondents may suggest technologies not currently certified or qualified by TSA, along with detailed information about the hardware and software.

91) Integration and cybersecurity requirements for cloud-based command and control centers.

Please include your integration plans and cybersecurity capabilities in your submissions.

92) Application of automation and robotics beyond specified areas.

TSA is exploring opportunities to modernize the program by incorporating integrated, technology-forward solutions that:

• Reduce reliance on manual labor

• Incorporate AI-driven threat detection and remote screening

• Improve passenger satisfaction

• Increase adaptability during surge events or staffing constraints

It is recommended respondents review the Requested Information section of the RFI to ensure their solutions are described appropriately.

93) Applicability to other screening environments beyond checkpoints.

Yes, TSA will also consider solutions for checked baggage.

94) TSA performance standards, security requirements, SSI/cybersecurity controls, passenger experience metrics, and equipment certifications.

No additional information will be provided at this time.

95) Sample rollout plan, scalability strategy, and past deployment case studies.

TSA is interested in modular, scalable offerings that can be deployed across a range of airport sizes and layouts. The deployment model refers to how the respondent proposes their solution be deployed.

96) TSA requirements for system reliability, availability, and repair time.

TSA does not intend on providing additional information on the current screening model as it is seeking solutions that leverage innovative technology, modern operational models, and process designs.

97) Dynamic links to videos about technologies and solutions offered.

No.

98) Fully integrated end-to-end solutions vs. modular solutions.

TSA is seeking turnkey, modular, and scalable solutions. Respondents should detail how the elements of the solution are provided in their overall solution.

99) Multiple award contracts under SPP for teaming arrangements.

This RFI is for market research purposes and does not constitute a Request for Proposal (RFP).

TSA may use the results of this RFI to inform future acquisition strategies and potential pilot programs at select airports.

100) Conditional participation for proprietary or pilot technologies not on the TSA Qualified Products List (QPL).

Respondents may suggest technologies not currently certified or qualified by TSA, along with detailed information about the hardware and software.

101) Preferred architecture or baseline for integrated screening lanes.

TSA is seeking innovative solutions that may include integration with existing technologies or a modernization of current technologies.

102) Value of information on technologies piloted with other agencies or international airports.

Respondents may suggest technologies not currently certified or qualified by TSA, along with detailed information about the hardware and software.

103) Proof-of-concept demonstrations or coordination of future pilots with TSIF.

This RFI is for market research purposes and does not constitute a Request for Proposal (RFP).

TSA may use the results of this RFI to inform future acquisition strategies and potential pilot programs at select airports.

104) Expected level of human staffing per checkpoint/lane.

This is up to the respondent and driven by their solution.

105) Hybrid operating model with existing TSA staff or entirely self-contained workforce.

TSA is seeking innovative solutions that may include integration with existing screening services and technologies or a modernization of them.

106) Required cybersecurity frameworks for integrated screening technologies.

Respondents should state the security architecture, applicable frameworks (e.g., NIST SP 80053/800171 controls), data-in-transit/at-rest protections, and data sovereignty posture.

107) Restrictions or review processes for AI/ML-based detection or passenger behavior analysis.

The Requested Information section of the RFI asks respondents to identify implementation barriers TSA should address in their solutions.

108) Preferred deployment timeframes or sequencing across airport sizes.

Respondents should provide the deployment timeframes driven by their solution.

109) Baseline ILS elements for alignment with proposed logistics models.

Respondents should provide an ILS logistics support model to include elements as part of their overall solution.

110) Standardized cost structure vs. detailed breakout of CAPEX/OPEX by airport category.

The RFI states cost comparisons across small, medium, and large-sized airports.

111) Ownership/maintenance of technology and equipment lifecycle.

Respondents should provide ownership/maintenance solutions as part of their overall solution.

112) Regulatory, legal, or procurement-related limitations within the SPP framework.

The Requested Information section of the RFI asks respondents to identify implementation barriers TSA should address in their solutions.

113) Establishing an industry working group or innovation forum.

Yes.

114) Indemnification against losses due to screening failures.

SPP vendors are eligible to receive SAFETY Act protection. TSA will not indemnify contractors.

115) Applicability of turnkey solutions across all airport categories.

TSA is interested in modular, scalable offerings that can be deployed across a range of airport sizes and layouts.

116) TSA PerSec responsibility for background checks and hiring authority.

Not specified; propose how your model integrates with existing PerSec processes and timelines.

117) Disposition of TSA-owned equipment at airports.

Respondents should provide disposition solutions as part of their overall solution.

118) Workforce optimization flexibility vs. adherence to TSA staffing models.

This RFI is for market research purposes and does not constitute a Request for Proposal (RFP).

TSA may use the results of this RFI to inform future acquisition strategies and potential pilot programs at select airports. Workforce optimization solutions are an objective of this RFI.

119) FSD oversight of screening operations under SPP.

TSA is open to exploring fully integrated solutions, including staffing and leadership models.

Please include details of your staffing plan in your submission.

120) Process for awarding IDIQ and/or task orders.

This RFI is for market research purposes and does not constitute a Request for Proposal (RFP).

TSA may use the results of this RFI to inform future acquisition strategies and potential pilot programs at select airports.

121) Technology integration with existing systems vs. providing new capabilities.

Either. TSA is particularly interested in modular, scalable offerings that can be deployed across a range of airport sizes and layouts.

122) Exclusion of title page, table of contents, and list of figures from the 20-page limit.

Confirmed—cover pages, TOC, glossary, appendices, and indexes do not count toward the 20-page limit.