Consolidated-Questions_Answers-RFI-LMS LXP.pdf
PDF 233 KB Posted
- Solicitation number
- 70T01027I8403N002
About this file
This document is a consolidated questions-and-answers (Q&A) file regarding a TSA Enterprise Learning Management System–Learning Experience Platform (LMS-LXP) Request for Information (RFI 70T01027I8403N002). The RFI is for market-research purposes to support acquisition planning for a comprehensive, fully integrated enterprise LMS-LXP solution designed to replace or modernize TSA's current learning infrastructure. TSA is seeking complete end-to-end solutions from single providers and explicitly will not consider services-only, component-only, LMS-only, LXP-only, or partial-scope responses. The planned period of performance is five years (one-year base period plus four one-year option periods). RFI responses were due by 12:00 PM EST on November 6, 2026, submitted to Siobhan Lawson (Siobhan.Lawson@tsa.dhs.gov) and Stacey Davis (Stacey.Davis@tsa.dhs.gov) in PDF/Word format.
The solution must support approximately 65,000 active users, approximately 127 million learning-history records, a database of 4–5 TB, and approximately 7 million annual updates. Key requirements include FedRAMP Moderate or higher authorization within a government cloud environment (FedRAMP-authorized, Azure Government, or AWS GovCloud); support for interoperability standards including xAPI, SCORM 1.2 and 2004, AICC, CMI, HTML5/web, and JSON; retention periods of up to 40 years for certain records; integration with TSA-provided identity, single sign-on, and authentication services; data migration including cleansing, deduplication, validation, and reconciliation; academy and training-center operations management at a broad level; and support for Super Intelligence (SI)-enabled capabilities (content creation, recommendations, analytics, learner insights) that must be configurable and capable of being disabled by TSA. The solution must handle Sensitive Security Information; support role-based access control, least-privilege access, and organizational hierarchy management; and operate within U.S. data-hosting requirements with TSA personnel using Personal Identity Verification cards and Government Furnished Equipment. ROM pricing should separately identify one-time and recurring costs for software/licenses, implementation, migration, integration, hosting, cybersecurity, training, help desk, administration, operations and maintenance, enhancements, and transition-out. TSA anticipates pursuing this effort within 12 months and has not finalized determinations regarding contract vehicles, small-business set-asides, evaluation factors, or deployment sequencing.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI-Learning-System A00002.pdf | ||
| SOO-Learning-Systems Draft.pdf | ||
| RFI-Learning-System.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Consolidated Questions and Responses Regarding TSA Enterprise LMS-LXP RFI 70T01027I8403N002
The questions below have been grouped into the requested sections and consolidated to remove exact and substantially duplicative questions. Vendor-specific introductory statements, company identifiers, and duplicate copies of the same questions were removed.
Terminology Note
For purposes of this RFI, references to “Artificial Intelligence,” “AI,” “Super Intelligence,” and “SI” refer to Super Intelligence-enabled capabilities.
Artificial intelligence was renamed Super Intelligence (SI) for government systems by executive order. Executive Order 14434, “Inaugurating the Era of Super Intelligence,” signed September 29, 2026, directs the executive branch to replace “Artificial Intelligence” and “AI” with “Super Intelligence” and “SI” in official communications. Federal Register, Vol. 91, No. 190, Friday, October 2, 2026, Presidential Documents.
1. Period of Performance and Lifecycle Pricing
Q1. RFI Section 6.6 describes a one-year base period followed by a five-year option period, while RFI Section 8 and Draft SOO Section 4.1 describe a one-year base period plus four one-year options. Which period-of-performance structure should respondents use for lifecycle planning and the ROM lifecycle cost estimate?
A1. The planned period of performance is for a period of five years (one-year base period and four one-year option periods) for lifecycle planning and ROM cost estimates.
Q2. For the RFI market-research response, what pricing format and level of precision does TSA prefer: a single-point estimate, planning range, unit rates, tiered user bands, or multiple pricing scenarios?
A2. This RFI is for market-research purposes only. Respondents should submit the ROM pricing information, format, and supporting assumptions they consider relevant. Specific pricing instructions will be provided in any future solicitation. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q3. Should respondents separately identify costs for software subscriptions or licenses, implementation, migration, integration, cloud hosting, cybersecurity, training, help desk, administration, operations and maintenance, enhancements, and transition-out?
A3. Respondents should separately identify one-time and recurring costs, including software or licenses, implementation, migration, integration, hosting, cybersecurity, training, help desk, administration, operations and maintenance, enhancements, and transition-out, as applicable.
Q4. What user population, user-tier thresholds, annual growth assumptions, storage volumes, data-egress assumptions, and retention assumptions should respondents use for ROM pricing?
A4. Respondents should assume approximately 65,000 active users for ROM pricing purposes.
Respondents should identify user-tier assumptions, growth assumptions, storage assumptions, data-egress assumptions, retention assumptions, and other material pricing assumptions.
Q5. May respondents identify proprietary commercial assumptions, dependencies, exclusions, and cost drivers in lieu of providing a fully specified lifecycle estimate where TSA has not provided planning data?
A5. Yes. Respondents may identify proprietary commercial assumptions, dependencies, exclusions, risks, and cost drivers relevant to their estimates.
Q6. For component-only or services-only responses, is a complete lifecycle ROM required, or may respondents provide a scoped ROM, pricing basis, and identified third-party licensing, hosting, and platform dependencies?
A6. TSA will not consider services-only or partial-scope responses for discrete portions of the requirement. TSA seeks responses from providers that can deliver a complete, fully integrated, end-to-end enterprise LMS-LXP solution.
Q7. Does TSA have an estimated budget range or anticipated funding allocation for implementation, licensing, migration, and ongoing support?
A7. This RFI is for market-research purposes only. TSA is not providing budget information currently. Any future solicitation will provide applicable pricing instructions.
2. Acquisition Strategy, Schedule, and Competition
Q8. What acquisition strategy, procurement timeline, solicitation-release date, anticipated award date, and implementation-start date is TSA considering?
A8. This RFI is for market-research purposes only and assists TSA with acquisition planning.
TSA anticipates pursuing this effort within 12 months. Any potential future acquisition will be announced through appropriate official acquisition channels.
Q9. Is TSA considering a full-and-open competition, a small-business set-aside, separately competed small-business workstreams, or another acquisition approach?
A9. TSA has not made a final determination regarding small-business participation or set-aside strategy. This RFI is for market research purposes only. Any future acquisition determination will be announced through appropriate official acquisition channels.
Q10. Which contract vehicles or procurement methods is TSA considering, such as GSA MAS, DHS strategic-sourcing vehicles, OASIS+, NASA SEWP, or a standalone procurement?
A10. This RFI is for market-research purposes only. TSA has not made final determinations regarding contract vehicles or procurement methods. Any potential future acquisition will be announced through appropriate official acquisition channels.
Q11. Is this RFI intended to inform a FY2027 follow-on for current Online Learning Center support, a separate enterprise LMS-LXP modernization procurement, or both?
A11. This RFI is for market-research purposes only. TSA is not providing additional information currently regarding current contracts, incumbent arrangements, or internal modernization decisions.
Q12. Does TSA plan to leverage the existing OLC support contract or vehicle for any portion of this effort, or will this be a separate competitive procurement?
A12. This RFI is for market-research purposes only. TSA is not providing additional information currently regarding current contracts or acquisition vehicles.
Q13. Does TSA anticipate acquiring software, implementation, migration, integration, managed services, and operations under one procurement, or separately competing some components?
A13. TSA seeks a complete, fully integrated, end-to-end enterprise LMS-LXP solution. TSA does not intend to consider component-only, services-only, or partial-scope responses. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q14. What contract type, ordering structure, and evaluation factors does TSA anticipate emphasizing, such as technical capability, user experience, cybersecurity, interoperability, transition risk, measurable outcomes, past performance, and price?
A14. This RFI is for market-research purposes only. TSA has not made final determinations regarding contract type, ordering structure, or evaluation factors. Any future solicitation will provide applicable instructions and evaluation information.
Q15. Would TSA consider phased modernization, pilots, incremental capability releases, or coexistence with the incumbent environment rather than a single enterprise-wide cutover?
A15. This RFI is for market-research purposes only. Respondents should describe their standard implementation, transition, and phased deployment approaches. TSA will determine the appropriate approach based on operational needs, technical feasibility, pricing, and overall value to the Government. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q16. What is the target go-live date, and are there fixed milestones, blackout periods, legacy-system sunset dates, contract expirations, or other operational constraints that will drive the schedule?
A16. This RFI is for market-research purposes only. TSA is not providing additional implementation-schedule, blackout-period, or transition details currently.
Q17. Will the operational assessment or proof of concept occur pre-award or post-award? If applicable, what duration, participant population, test environment, evaluation criteria, and funding approach should respondents assume?
A17. TSA does not plan to conduct a proof of concept as part of this RFI. This RFI is for market-research purposes only. Any future solicitation will provide applicable requirements.
Q18. Does TSA anticipate industry days, vendor demonstrations, one-on-one sessions, or follow-up discussions after reviewing RFI responses? If so, what format, timing, and scenarios are anticipated?
A18. TSA does not plan to conduct an industry day as part of this RFI. Based on the information provided in RFI responses, TSA may conduct vendor demonstrations, one-on-one sessions, or follow-up discussions.
Q19. Will TSA consider extending the RFI response due date, including to allow time after responses to vendor questions are issued?
A19. The response date has been extended as follows: Submit responses electronically in PDF/Word format to: Siobhan Lawson at Siobhan.Lawson@tsa.dhs.gov and Stacey Davis at Stacey.Davis@tsa.dhs.gov no later than 12:00PM, Eastern Standard Time (EST) on November 6, 2026.
3. Acceptable Response Models and Teaming
Q20. Will TSA consider responses from:
• Systems integrators proposing third-party commercial LMS-LXP products;
• Services-only providers addressing implementation, migration, integration, accessibility, governance, change management, or operations;
• LMS-only or LXP-only providers;
• Component providers, such as AI-assisted learning, microlearning, offline-learning, or accessibility-validation solutions; and
• Teams combining specialized providers with an enterprise LMS-LXP platform provider?
A20. No. TSA will not consider services-only, component-only, LMS-only, LXP-only, or partial-scope responses. TSA seeks responses from providers that can deliver a complete, fully integrated, end-to-end enterprise LMS-LXP solution.
Q21. May a lead integrator provide implementation, migration, governance, program management, and operations while a named partner provides and operates the FedRAMP-authorized LMS-LXP?
mailto:Siobhan.Lawson@tsa.dhs.gov mailto:Stacey.Davis@tsa.dhs.gov
A21. TSA seeks a seamlessly integrated enterprise LMS-LXP solution with out-of-the-box capabilities to the greatest extent practicable. TSA will not consider services-only, component-only, LMS-only, LXP-only, or partial-scope responses. TSA seeks responses from providers that can deliver a complete, fully integrated, end-to-end enterprise LMS-LXP solution.
Q22. For a disclosed team, which qualifications, past performance, authorizations, and operating experience must be held by the responding legal entity or prime contractor, and which may be demonstrated by named platform providers, implementation partners, or material subcontractors?
A22. TSA seeks a seamlessly integrated enterprise LMS-LXP solution with out-of-the-box capabilities to the greatest extent practicable. TSA will not consider services-only, component-only, LMS-only, LXP-only, or partial-scope responses. TSA seeks responses from providers that can deliver a complete, fully integrated, end-to-end enterprise LMS-LXP solution.
Q23. May respondents propose a COTS LMS-LXP selected with TSA after the RFI stage, rather than identifying a specific platform provider in the RFI response? If so, may product-specific questions be answered at the market-category level?
A23. No. Respondents should identify the proposed solution and describe its current capabilities, security authorization status, and ability to meet the RFI requirements. TSA will not consider services-only, component-only, LMS-only, LXP-only, or partial-scope responses. TSA seeks responses from providers that can deliver a complete, fully integrated, end-to-end enterprise LMS-LXP solution.
Q24. Will TSA consider a multi-vendor, best-of-breed, vendor-neutral architecture integrating LMS, LXP, content, analytics, AI, and specialized learning capabilities, rather than requiring all capabilities from one platform provider?
A24. TSA seeks a single-provider to provide a unified enterprise LMS-LXP solution. TSA will not consider services-only, component-only, LMS-only, LXP-only, or partial-scope responses.
TSA seeks responses from providers that can deliver a complete, fully integrated, end-to-end enterprise LMS-LXP solution.
Q25. Must LMS and LXP functionality be supplied as a single commercial product, or may separately sourced products be integrated through documented interfaces, unified access, and consolidated reporting?
A25. TSA seeks a single-provider, unified enterprise LMS-LXP solution that provides an integrated platform, user experience, data environment, reporting capability, security posture, and support model for all required LMS-LXP functions.
Q26. Would TSA consider a small-business prime contractor partnering with an established enterprise LMS-LXP technology provider?
A26. This RFI is for market-research purposes only. Any teaming/ partnering arrangement should clearly demonstrate the prime contractor’s ability to manage contract performance and meet all applicable requirements.
Q27. May a professional-services contractor submit an independent RFI response recommending an acquisition structure or services approach without identifying a specific LMS manufacturer?
A27. No. TSA will not consider services-only or partial-scope responses.
Q28. Would TSA welcome a response describing training, change-management, learner-engagement, performance-reinforcement, or specialized conversational-AI capabilities as part of a broader integrated solution?
A28. Respondents may describe relevant capabilities, including change management, learner engagement, performance reinforcement, and Super Intelligence-enabled functionality, as part of a complete integrated enterprise LMS-LXP solution.
4. Current Environment and Future-State Scope
Q29. Which LMS, LXP, Online Learning Center, SAP SuccessFactors capabilities, and other learning technologies are currently in use across TSA?
A29. This RFI is for market-research purposes only. TSA is not providing additional information currently regarding current systems, subscriptions, or internal modernization decisions. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q30. Is the contemplated LMS-LXP intended to:
• Replace the existing SAP SuccessFactors-based OLC environment;
• Retain the current LMS of record and add an LXP;
• Modernize selected components over time;
• Consolidate multiple learning systems; or
• Support another target-state architecture?
A30. This RFI is for market-research purposes only. TSA is not providing additional information currently regarding current systems, subscriptions, or internal modernization decisions. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q31. Does TSA intend to retain the current OLC subscription or incumbent platform during transition, and what coexistence period should respondents assume?
A31. This RFI is for market-research purposes only. TSA is not providing additional information currently regarding current systems, subscriptions, or internal modernization decisions. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q32. What current-state limitations, pain points, mission needs, and desired outcomes should industry address in RFI responses?
A32. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO. Respondents should describe how their solutions address the objectives and operational needs as described in the RFI.
Q33. Does TSA anticipate evaluating solutions based on outcomes such as reduced time-to-readiness, recognition of prior learning, personalized learning pathways, proficiency, learning effectiveness, scenario-based performance, knowledge retention, or administrative efficiency?
A33. This RFI is for market-research purposes only. TSA will determine the appropriate approach based on operational needs, technical feasibility, pricing, and overall value to the Government.
Q34. Is academy and training-center operations management in scope, including course and class scheduling, instructor and resource or facility scheduling, practical and performance evaluations, testing, and certification or qualification tracking?
A34. This RFI is for market-research purposes only. Academy and training-center operations management is within scope at a broad level. Respondents should describe applicable capabilities that support course and class scheduling, instructor and resource or facility scheduling, practical and performance evaluations, testing, certification, qualification tracking, and related training-management functions. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q35. What is TSA’s anticipated approach and timeline for the government-wide OPM Core HCM platform and its learning-management capabilities? Should respondents assume that the future LMS-LXP will replace, supplement, integrate with, or transition to OPM Core HCM within the lifecycle planning period?
A35. This RFI is for market-research purposes only. TSA is not providing additional information currently regarding OPM Core HCM or internal modernization decisions. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q36. Does TSA expect the future contractor to support a transition to OPM Core HCM, a commercial LMS, or both, depending on the final modernization approach?
A36. This RFI is for market-research purposes only. TSA is not providing additional information regarding future internal modernization decisions currently.
Q37. What workforce populations, certifications, qualifications, test-out processes, equivalencies, training waivers, adaptive-learning workflows, and assessment-validation requirements are in scope?
A37. Respondents should describe their standard capabilities for qualifications, certifications, test-out processes, equivalencies, training waivers, adaptive learning, and assessment support, for the TSA enterprise population. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q38. Does TSA expect the contractor to develop and maintain custom courseware, provide authoring tools for TSA staff, provide COTS content libraries, integrate existing authoring tools, or some combination of these approaches?
A38. This RFI is for market-research purposes only. Respondents should describe their capabilities for content authoring, curation, deployment, integration with authoring tools, and COTS content libraries, as applicable. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q39. Which authoring tools, external-content providers, virtual-instructor-led training platforms, and enterprise content repositories are currently used or anticipated for the future environment?
A39. The proposed solution should support xAPI, SCORM 1.2 and 2004, AICC, CMI, HTML5/web output, and JSON. Respondents should also describe support for CSV, PDF, API-based data feeds, raw data logs, PDF certificates, electronic badges, user-generated content, curated learning paths, and modern web frameworks, including React, Vue.js, or Angular. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q40. Is eCommerce or payment processing for training within the scope of the future LMS-
LXP?
A40. This RFI is for market-research purposes only. TSA is not establishing an eCommerce requirement through this RFI.
5. User Population, Licensing, and Operational Scale
Q41. What total user population should respondents assume, including registered users, active users, monthly active users, peak concurrent users, learners, administrators, instructors, supervisors, content authors and reviewers, contractors, airport partners, other agencies, and foreign or international users?
A41. Respondents should assume approximately 127 million learning-history records, a database size of approximately 4 to 5 TB, and average annual activity of approximately 7 million updates per year. Respondents should identify any assumptions used for registered users, monthly active users, peak concurrent users, administrators, instructors, supervisors, content authors and reviewers, external users, storage, and user growth.
Q42. What population growth, seasonal fluctuation, annual completion volume, transaction volume, storage volume, and retention volume should respondents assume over the contract lifecycle?
A42. This RFI is for market-research purposes only. Respondents should identify their assumptions for growth, completions, transactions, storage, and retention.
Q43. What user populations will require access, including TSA employees, contractors, external users, airport partners, other agencies, and OCONUS users? What are the anticipated CONUS and OCONUS distributions?
A43. The anticipated population should focus on providing access to TSA personnel with Personal Identity Verification (PIV) cards and Government Furnished Equipment (GFE).
Q44. Will TSA license the entire enterprise at deployment, or does it prefer a phased rollout by organization, location, population, or capability?
A44. This RFI is for market-research purposes only. TSA is not establishing a required deployment sequence. Respondents may describe their standard deployment approach. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q45. What licensing model should respondents assume, such as named user, registered user, active user, concurrent user, enterprise license, or tiered user bands?
A45. Respondents should describe their standard licensing approach, including the basis for pricing, available user tiers or bands, scalability, and assumptions used to develop the estimate.
TSA will consider proposed licensing approaches based on operational needs, flexibility, scalability, pricing, and overall value to the Government.
Q46. How many TSA organizations, occupational groups, locations, sub-portals, administrative boundaries, catalogs, branding configurations, and audience-specific landing pages must be supported?
A46. This RFI is for market-research purposes only. Respondents should describe their ability to support multiple organizations, audiences, administrative boundaries, catalogs, and configurations. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q47. How will users interact with the environment, including mandatory, optional, recurring, certification-based, instructor-led, virtual, self-paced, or one-time learning?
A47. Respondents should describe how their solution supports mandatory, optional, recurring, certification-based, instructor-led, virtual, self-paced, and one-time learning. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q48. How many certifications, qualifications, competencies, skills, continuing-education credits, curricula, and blended-learning programs must be configured at go-live?
A48. This RFI is for market-research purposes only. Vendors may propose different roll-out solutions or processes. Be sure to identify all assumptions. Respondents should describe relevant configuration and management capabilities. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q49. Must the LMS-LXP support languages other than English? If so, which languages?
A49. This RFI is for market-research purposes only. TSA is not establishing a specific multilingual requirement currently. Respondents may describe available language capabilities.
TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q50. Which international locations require access, and are there any data-hosting or data-residency requirements outside the United States?
A50. This RFI is for market research purposes only. The solution must be based in the United States and operated by vetted personnel that meet government security requirements (eg.
FedRamped environments).
6. Identity, Access, and Enterprise Integrations
Q51. Which identity providers, identity-federation protocols, and single-sign-on methods must the solution support, including PIV/CAC, ICAM, SAML, OIDC, MFA, and other authentication requirements?
A51. Respondents should assume TSA will provide identity, single sign-on, and authentication services. These services are managed by TSA IT and may change during the period of performance. Respondents should describe their ability to integrate with TSA-provided identity, SSO, and authentication services, including support for applicable standards and future changes to TSA’s identity environment.
Q52. What role-based access-control, least-privilege, organizational-hierarchy, airport-hierarchy, supervisor-relationship, and administrative-access requirements should respondents anticipate?
A52. Respondents should describe capabilities for role-based access control, least-privilege access, organizational hierarchy management, and administrative access management. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q53. What is the authoritative source for personnel, organizational, location, supervisor, and user-account data, including HRIS, DHS HR, NFC, OPM Core HCM, or other systems?
A53. The current learning environment is updated manually. This RFI is for market-research purposes only. The proposed solution should support integration with DHS and TSA provided systems for personnel, organizational, location, supervisor, and related data, as those integrations become available. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q54. How should user accounts be created and maintained for employees, contractors, external users, inactive users retained for historical reference, and other nonemployee populations? Are self-registration, automated feeds, manual account creation, and bulk-load scenarios required?
A54. Respondents should describe capabilities for automated provisioning, administrator-managed accounts, bulk loading, account maintenance, and support for authorized external-user scenarios. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q55. What frequency and mechanisms should be used for inbound and outbound data exchanges, such as real-time APIs, web services, nightly batch files, flat files, or manual processes?
A55. Respondents should describe standard support for APIs, secure data feeds, batch files, file-based exchange, and other secure integration methods. Respondents should provide their inbound and outbound data capabilities. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q56. Which TSA, DHS, OPM, HR, workforce-management, qualification, credentialing, scheduling, assessment, reporting, analytics, data-warehouse, and business-intelligence systems must integrate with the future LMS-LXP?
A56. This RFI is for market-research purposes only. TSA will not define current or future technology integrations at this time. Respondents should describe standard integration capabilities, including support for APIs, data feeds, and secure data exchange. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q57. What third-party content providers and virtual-classroom platforms, such as Microsoft Teams, WebEx, Zoom, Skillsoft, LinkedIn Learning, or other providers, must be integrated?
Should external course completions be recorded in the LMS?
A57. Respondents should describe how they would host the outputs from the above platforms (i.e. how would a save Zoom call or a WebEx meeting be hosted on the proposed solution?). The proposed solution should support xAPI, SCORM 1.2 and 2004, AICC, CMI, HTML5/web output, and JSON. Respondents should also describe support for CSV, PDF, API-based data feeds, raw data logs, PDF certificates, electronic badges, user-generated content, curated learning paths, and modern web frameworks, including React, Vue.js, or Angular. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q58. What data must be exchanged through each interface, including data elements, source and destination systems, update frequency, directionality, interface method, and business scenario?
A58. This RFI is for market-research purposes only. TSA is not providing detailed interface specifications currently. Respondents should describe their approach to data mapping, interface configuration, security, testing, monitoring, reconciliation, and ongoing support. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the
SOO.
Q59. Will TSA provide interface specifications, REST/SOAP API documentation, data dictionaries, and other technical documentation during solicitation or implementation?
A59. This RFI is for market-research purposes only. Any future solicitation or implementation effort will provide applicable requirements and documentation, as appropriate. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q60. Objective 7 refers to interoperability with “all TSA-approved software and hardware.” Can TSA provide the relevant list, categories, or integration standards at an appropriate level of detail?
A60. Assume current Windows / Apple hardware and software for access through standard browsers. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
7. Migration, Content, and Records Management
Q61. How many current learning systems, repositories, and source systems are in scope for migration, and which systems currently serve as the LMS or systems of record?
A61. This RFI is for market-research purposes only. TSA is not providing additional information currently regarding current or future LMS systems. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q62. What migration volumes should respondents assume for:
• Active and inactive learner records;
• Historical completions;
• Certifications and qualifications;
• Audit history and metadata;
• Courses and learning objects;
• SCORM, AICC, xAPI, and cmi5 content;
• Instructor-led and virtual-instructor-led training;
• Future sessions;
• Documents, videos, assessments, question banks, curricula, and blended-learning objects;
and
• Content attachments and other associated data?
A62. Respondents should assume approximately 127 million learning-history records, a database size of approximately 4 to 5 TB, and average annual activity of approximately 7 million updates per year.
Q63. What years or age range of historical data must be migrated, retained, or made retrievable?
A63. The proposed solution must support retention periods for up to 40 years following the applicable records-schedule cutoff. Respondents should assume records start at TSA’s inception.
Q64. What are the source-data formats, schemas, export methods, and data-quality conditions?
Will TSA provide data extracts, or should the contractor plan to extract data from legacy systems?
A64. TSA is not providing detailed source-data schemas, formats, or extraction requirements currently. Respondents should describe standard migration and extraction capabilities. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q65. Should the migration scope include data cleansing, deduplication, exception remediation, reconciliation, conversion, modernization, or validation of legacy records and content?
A65. Yes. Respondents should include data cleansing, deduplication, validation, reconciliation, and exception remediation in their proposed migration approach.
Q66. Must historical audit trails, timestamps, course versions, equivalencies, qualification records, and other legacy information be migrated as live records, or is a read-only archive acceptable for some historical data?
A66. Yes. Respondents should assume historical audit trails must be migrated as active and accessible records.
Q67. What data-validation, reconciliation, acceptance, data-portability, and transition-out requirements should respondents anticipate?
A67. Respondents should describe standard data validation, reconciliation, acceptance, portability, export, and transition-out capabilities. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q68. Which learning-content interoperability standards and versions are mandatory or preferred for migration and future deployment, including SCORM 1.2, SCORM 2004, AICC, xAPI, cmi5, LTI 1.3, Common Cartridge, and Learning Record Store capabilities?
A68. The proposed solution should support xAPI, SCORM 1.2 and 2004, AICC, CMI, HTML5/web output, and JSON. Respondents should also describe support for CSV, PDF, API-based data feeds, raw data logs, PDF certificates, electronic badges, user-generated content, curated learning paths, and modern web frameworks, including React, Vue.js, or Angular. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q69. Does TSA anticipate retaining content in legacy formats? If so, is content conversion or modernization in scope?
A69. Respondents should describe their ability to support legacy content conversion, modernization, and migration. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q70. Which NARA General Records Schedules, DHS/TSA records schedules, OCHCO requirements, retention periods, and disposition requirements apply to training, certification, qualification, and separated-employee records?
A70. The proposed solution must support retention periods that vary by record type, user population, training program, certification, and other applicable business requirements. Certain records for specific populations may require retention for up to 40 years following the applicable records-schedule cutoff. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q71. Is the LMS-LXP expected to execute retention and disposition actions, or retain records and export them to a TSA records-management system?
A71. Respondents should describe support for records classification, configurable retention rules, audit trails, search and retrieval, legal or administrative holds, archival export, authorized disposition, and secure deletion. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
8. Security, Hosting, and FedRAMP
Q72. Must the proposed LMS-LXP hold active FedRAMP Moderate or higher authorization at the RFI stage, proposal submission, award, or before production deployment?
A72. This RFI is for market-research purposes only. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q73. Will TSA consider a solution with FedRAMP authorization in process, a documented authorization pathway, or a component deployed within and inheriting from a FedRAMP-authorized partner environment?
A73. This RFI is for market-research purposes only. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q74. Must each SaaS component, optional module, integration, AI capability, and LXP component independently hold FedRAMP Moderate authorization, or may an integrated solution satisfy the requirement through a defined authorized boundary?
A74. This RFI is for market-research purposes only. TSA seeks a complete, fully integrated, end-to-end enterprise LMS-LXP solution. Vendors should propose all potential solutions that they believe meet this requirement.
Q75. How should respondents document FedRAMP authorization coverage and inherited controls for third-party integrations, optional modules, implementation services, support services, and other components outside the core platform boundary?
A75. Respondents must identify any component hosted outside the primary proposed environment or security boundary and explain how it meets applicable security requirements.
Q76. Are any components or services excluded from FedRAMP consideration at the RFI stage?
A76. This RFI is for market-research purposes only. TSA is not identifying exclusions currently.
Respondents should identify the authorization status and security boundary for all proposed components. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q77. Will a FedRAMP Moderate-authorized commercial SaaS environment, government community cloud, Azure Government, or AWS GovCloud satisfy TSA’s hosting requirements?
Are additional DHS/TSA authorization, hosting, deployment, or DHS 4300A requirements anticipated?
A77. TSA will consider solutions hosted in a FedRAMP-authorized government cloud environment, provided the proposed solution meets applicable TSA security, privacy, records-management, and operational requirements. TSA prefers that the complete proposed solution operate within the same cloud environment and clearly defined security boundary to the greatest extent practicable. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q78. Will Sensitive Security Information be stored, delivered, processed, or generated in the LMS-LXP, including courseware, assessments, documents, learner records, or AI-enabled functions?
A78. Respondents should assume that the proposed solution may store, process, or deliver SSI, including SSI contained in training content, assessments, supporting documents, learner records, or SI-enabled functions.
Q79. If SSI is in scope, what additional handling, segmentation, authorization-impact-level, personnel-suitability, background-investigation, data-residency, U.S.-person, or administrator-access requirements apply?
A79. The proposed solution must support applicable SSI safeguarding requirements, including appropriate access controls, role-based permissions, least-privilege access, audit logging, encryption, records management, and secure handling of sensitive information.
Q80. What security requirements apply to specialized AI-enabled learning components integrated with a FedRAMP-authorized LMS-LXP?
A80. All SI-enabled learning components must meet applicable TSA security, privacy, governance, testing, and authorization requirements before activation or operational use.
Q81. What service-level expectations apply to system availability, disaster recovery, incident response, continuity, and technical support?
A81. This RFI is for market-research purposes only. Respondents should describe standard capabilities for system availability, disaster recovery, incident response, continuity, and technical support. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
9. Artificial Intelligence and Super Intelligence
Q82. How does TSA define “Super Intelligence” or “SI” in the RFI and SOO? Does it refer to commercially available AI and machine-learning capabilities, or to a distinct category of capability?
A82. Artificial intelligence was renamed Super Intelligence (SI) for government systems by Executive Order 14434, “Inaugurating the Era of Super Intelligence,” signed September 29, 2026. The Executive Order directs the executive branch to replace “Artificial Intelligence” and “AI” with “Super Intelligence” and “SI” in official communications. Federal Register, Vol. 91, No. 190, Friday, October 2, 2026, Presidential Documents.
For purposes of this RFI, SI refers to advanced technology capabilities that may support content creation and curation, personalized learning recommendations, analytics, reporting, learner insights, search, and learner support.
Q83. Which AI-enabled capabilities are priorities for initial deployment, such as recommendations, personalized learning pathways, skills inference, adaptive learning, generative-AI content assistance, conversational learner support, scenario-based exercises, or performance reinforcement?
A83. This RFI is for market research purposes only. Respondents may describe available SI-enabled capabilities that support content creation and curation, recommendations, analytics, reporting, learner insights, SI-enabled generative-content assistance, and related learning functions. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q84. Must SI or AI capabilities be available at contract award or go-live, or may respondents propose phased, optional, configurable, or roadmap capabilities?
A84. This RFI is for market research purposes only. Any SI-enabled capabilities must meet applicable TSA security, privacy, governance, testing, and authorization requirements before activation or operational use. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q85. What TSA or DHS policies, security restrictions, governance requirements, approvals, content controls, human-oversight requirements, and authorization requirements govern AI functionality?
A85. TSA is following all Office of Management & Budget guidance (M-25-21) and DHS SI Strategy. Respondents should describe governance, security, and human-oversight controls for all proposed SI-enabled capabilities. At a minimum, SI-enabled functions must be configurable and capable of being disabled by TSA. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q86. May governed conversational-AI assistants support training clarification, scenario-based exercises, post-training reinforcement, or other learner-support functions? If so, what human oversight and content controls are required?
A86. This RFI is for market research purposes only. Respondents may describe available conversational-SI learner-support capabilities. Such capabilities must meet applicable TSA security, governance, human-oversight, testing, and authorization requirements before use. SI-enabled functions must be configurable and capable of being disabled by TSA. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q87. Will AI-assisted authoring or other AI features process SSI or other sensitive Government content in the initial phase, or will initial AI use be limited to non-SSI content?
A87. Respondents should assume that the proposed solution will process SSI. Any SI-assisted authoring or other SI-enabled capability that processes TSA information must meet all applicable security, privacy, governance, testing, and authorization requirements before activation or operational use. SI-enabled functions must be configurable and capable of being disabled by TSA. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q88. Must AI-enabled capabilities fall within the existing FedRAMP-authorized boundary of the LMS-LXP, or may they be evaluated as integrated components within an approved architecture?
A88. SI-enabled capabilities must meet applicable FedRAMP and TSA security requirements as part of the complete proposed solution. Respondents should identify the authorization status and security boundary of all proposed SI-enabled capabilities. SI-enabled functions must be configurable and capable of being disabled by TSA.
Q89. Is TSA interested in measuring applied knowledge retention, scenario-based decision-making, performance improvement, and other outcomes beyond course completion, assessments, and certification tracking?
A89. Respondents may describe their ability to support outcome measures beyond completions and certifications, including knowledge retention, scenario-based decision-making, performance improvement, and other learning-effectiveness measures. Respondents may also describe how SI-enabled capabilities support these functions, subject to applicable TSA security, privacy, governance, testing, and authorization requirements. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
10. Accessibility, Performance, and Support
Q90. Should respondents provide an Accessibility Conformance Report, such as VPAT 2.5 Rev 508, for the core platform only or also for TSA-specific configurations, custom components, integrations, and third-party courseware?
A90. Respondents should provide a current Accessibility Conformance Report using the applicable Voluntary Product Accessibility Template for the proposed solution.
Q91. Which WCAG version and conformance level should respondents address, such as WCAG
2.0 AA under the Revised Section 508 Standards or WCAG 2.1 AA?
A91. This RFI is for market-research purposes only. Respondents should identify the accessibility standards and conformance levels addressed by their proposed solution. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q92. Is remediation of existing legacy, Government-furnished, or third-party courseware for Section 508 compliance within scope? Does TSA have an inventory of the current accessibility status of its course library?
A92. No. Remediation of legacy courseware to current Section 508 standards is not within scope.
Q93. For airport, field, training-room, shared-workstation, low-bandwidth, high-latency, and OCONUS environments, is fully offline learning with later synchronization required, or is low-bandwidth online access sufficient?
A93. This RFI is for market-research purposes only. TSA is not establishing a specific offline-learning requirement.
Q94. Will learners primarily use TSA-furnished devices, shared workstations, authorized personal devices, mobile devices, or a combination of device types?
A94. Yes. Respondents should describe supported access methods and device compatibility for authorized TSA users. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q95. What support model does TSA expect, including Tier 1 learner help desk, Tier 2/3 application support, system administration, integration support, reporting, release management, configuration, testing, onboarding, and ongoing operational support?
A95. Respondents should describe a helpdesk and operational-support model sufficient to support an enterprise LMS-LXP environment. TSA anticipates a Level 1.5 to Level 2.0 support model in which initial user support is provided through TSA services and escalated to a specialized LMS-LXP support environment, as appropriate. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q96. Which support tiers will remain Government-operated, and which are expected from the contractor?
A96. Respondents should describe a helpdesk and operational-support model sufficient to support an enterprise LMS-LXP environment. TSA anticipates a Level 1.5 to Level 2.0 support model in which initial user support is provided through TSA services and escalated to a specialized LMS-LXP support environment, as appropriate. TSA is relying on the contractor's expertise to propose a solution to meet the requirements as outlined in the SOO.
Q97. What service-desk coverage hours, user populations, response expectations, and staffing qualifications are required, including 24x7 support, OCONUS support, airport-shift coverage, and vendor-certified resources?
A97. Respondents should describe service hours, escalation procedures, staffing qualifications, and standard support coverage. TSA operates in all different time zones.
Q98. What level of option-year support should respondents assume for configuration, testing, onboarding new audiences, enhancements, and operations?
A98. Respondents should describe standard approaches for ongoing configuration, testing, onboarding, enhancements, and operations support.
11. RFI Response Format
Q99. Does the 20-page limit include:
• Section 5 and 6 summary tables;
• ROM pricing tables;
• Past-performance case studies;
• Cover letters;
• Tables of contents;
• Product data sheets;
• Accessibility Conformance Reports or VPATs; and
• Other appendices or supplementary attachments?
A99. This RFI is for market research purposes only, and the response-format instructions apply only to this RFI. The 20-page limit applies to the substantive RFI response, including narrative, tables, pricing information, and case studies. A cover letter and table of contents do not count toward the page limit. Respondents may include accessibility documentation as a separate attachment, consistent with the RFI response instructions. Other supplemental attachments, including product data sheets, should be limited to material necessary to support the response within the 20-page limit.
Q100. Because Section 9 overlaps with several Section 6 response requirements, may respondents answer each topic once under Section 6 and use concise summaries and…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .