Request for Information - Enterprise Learning Management System (LMS) of Record with a Learning Experience Platform (LXP)
HOMELAND SECURITY, DEPARTMENT OF › TRANSPORTATION SECURITY ADMINISTRATION › WORKFORCE & ENTERPRISE OPERATIONS
- Solicitation
- 70T01027I8403N002
- Responses due
- November 6, 2026 at 12:00 PM EST
- Questions due
- October 27, 2026
- NAICS
- 541512, Computer Systems Design Services
- Set-aside
- No Set aside used
- Place of performance
- Springfield, VA
- Notice type
- Sources Sought
- First posted
- October 23, 2026
- Latest version posted
- November 3, 2026
InstantSam read 109,358 characters from 4 of this notice’s 4 attachments, and pulled out what it requires.
At a glance
- What they want
- This is a Request for Information (RFI), not a solicitation. TSA is doing market research on an enterprise digital learning ecosystem: an official Learning Management System (LMS) of record combined with a Learning Experience Platform (LXP).
- Who should respond
- Businesses that can meet the requirement and follow the response instructions in the notice. This is market research, not a request for offers, so no set-aside applies yet and any future one is not stated. NAICS 541512, Computer Systems Design Services, which sets the size standard.
- When
- October 27, 2026, 12:00PM: Questions due
- November 2, 2026: Responses due
- November 6, 2026 at 12:00 PM EST: Responses were due
The response deadline is the one in bold: a late offer is normally not considered. An amendment can move any of these dates, and the changes recorded for this notice are listed further down. Whether a site visit is required is in the submission instructions below.
- Check first
- Partial-scope responses will not be considered (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "TSA will not consider services-only or partial-scope responses for discrete portions of the requirement."
- TSA wants one provider to deliver a unified LMS and LXP (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "TSA seeks a single-provider to provide a unified enterprise LMS-LXP solution."
- The LMS and LXP must share one platform, user experience, data environment, reporting capability, security posture and support model (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "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."
- Watch out
- Date conflicts: RFI-Learning-System A00002.pdf and RFI-Learning-System.pdf give a response due date of 11/2/2026. Consolidated-Questions_Answers-RFI-LMS LXP.pdf (A19) and the notice extend it to November 6, 2026. Use November 6.
- Period-of-performance conflict: Section 6.6 of RFI-Learning-System A00002.pdf and RFI-Learning-System.pdf describes a one-year base plus a "five-year option period." Section 8 and the SOO describe a base plus four options. TSA resolved this as five years total (Consolidated-Questions_Answers-RFI-LMS LXP.pdf, A1).
- Document versions: RFI-Learning-System.pdf is a near-duplicate of RFI-Learning-System A00002.pdf and still contains the duplicate item 6.1.5. TSA says that item was removed (A102). RFI-Learning-System A00002.pdf appears to be the corrected version.
- What was read
- It read 4 of the 4 attachments on this notice, 109,358 characters, all 4 in full. Document by document.
Nothing here is new: each line is taken from what the review says below, written from the documents, and a requirement that could stop a quote is listed first, in bold. A figure the review read from a scanned page says so. The compliance checklist in the app quotes the sentence behind each requirement, after checking it against the documents word for word (how a review is checked). Read a requirement in the solicitation before you rely on it.
From the solicitation
Consolidated-Questions_Answers-RFI-LMS LXP.pdf
TSA seeks a single-provider to provide a unified enterprise LMS-LXP solution.
What the review made of it: TSA wants one provider to deliver a unified LMS and LXP (Consolidated-Questions_Answers-RFI-LMS LXP.pdf).
We checked this passage against the text of the document: it is there word for word, with only spacing and quotation marks evened out.
Scope of Work
- This is a Request for Information (RFI), not a solicitation. TSA is doing market research on an enterprise digital learning ecosystem: an official Learning Management System (LMS) of record combined with a Learning Experience Platform (LXP). The documents say it is "not a solicitation, Request for Proposal, Invitation for Bid, or Government commitment to issue a future solicitation or make an award" (RFI-Learning-System A00002.pdf, Section 1).
- The Statement of Objectives (SOO-Learning-Systems Draft.pdf) lists eight performance objectives:
- Official LMS of record and compliance reporting.
- Learner-centric LXP integration.
- Adaptive, modular and test-out assessments.
- Rapid content creation, curation and deployment.
- Standardized enterprise training delivery.
- Analytics and dashboards.
- Secure interoperability, open standards and portability.
- Operational continuity, plus historical record import and export.
- Delivery modes in scope are instructor-led, virtual instructor-led, web-based, blended, mobile, field-based, modular and microlearning (SOO-Learning-Systems Draft.pdf, Section 3).
- Geographic scope covers TSA Headquarters (Springfield, VA), field locations and airports, training centers, and CONUS and OCONUS personnel (SOO-Learning-Systems Draft.pdf).
- Per Consolidated-Questions_Answers-RFI-LMS LXP.pdf (Q34), academy and training-center operations management is within scope at a broad level. This includes class and instructor scheduling, practical evaluations, testing and certification tracking.
- The anticipated period of performance is five years: one base year plus four one-year options (Consolidated-Questions_Answers-RFI-LMS LXP.pdf, A1; SOO-Learning-Systems Draft.pdf, Section 4.1).
- Place of performance may be contractor facilities, Government-approved cloud environments, TSA sites and authorized remote locations (SOO-Learning-Systems Draft.pdf).
- Per Consolidated-Questions_Answers-RFI-LMS LXP.pdf, TSA anticipates pursuing the effort within 12 months (A8). No solicitation date, budget, contract type or vehicle is given.
Key Requirements
- TSA wants one provider to deliver a unified LMS and LXP (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "TSA seeks a single-provider to provide a unified enterprise LMS-LXP solution."
- Partial-scope responses will not be considered (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "TSA will not consider services-only or partial-scope responses for discrete portions of the requirement."
- The LMS and LXP must share one platform, user experience, data environment, reporting capability, security posture and support model (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "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."
- Offerors must show how they meet the eight core objectives (SOO-Learning-Systems Draft.pdf): "Offerors shall demonstrate how their proposed solutions will achieve the following core objectives:"
- Respondents must state their FedRAMP status (RFI-Learning-System A00002.pdf): "Respondents should identify the current federal cloud authorization status of the proposed solution, including whether the solution currently holds FedRAMP Moderate authorization or higher." SOO-Learning-Systems Draft.pdf lists FedRAMP Moderate (or higher) as a constraint, but TSA did not say when it must be held (Consolidated-Questions_Answers-RFI-LMS LXP.pdf, A72 and A73).
- Government data and content stay under Government ownership (RFI-Learning-System A00002.pdf): "Government data and Government-developed content must remain under Government ownership and control."
- Data export must be guaranteed at contract end (SOO-Learning-Systems Draft.pdf): "Offerors must guarantee data export capabilities in non-proprietary formats upon contract conclusion."
- ROM sizing should assume about 65,000 active users (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Respondents should assume approximately 65,000 active users for ROM pricing purposes."
- Migration and storage sizing assumptions are given (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "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."
- Retention must run up to 40 years (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "The proposed solution must support retention periods for up to 40 years following the applicable records-schedule cutoff."
- Historical audit trails must be migrated as live records (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Respondents should assume historical audit trails must be migrated as active and accessible records."
- The migration approach must include cleansing and reconciliation (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Respondents should include data cleansing, deduplication, validation, reconciliation, and exception remediation in their proposed migration approach."
- Sensitive Security Information (SSI) will be in the system (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "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."
- Super Intelligence (SI, TSA's term for AI) functions must be switchable by TSA (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "At a minimum, SI-enabled functions must be configurable and capable of being disabled by TSA."
- Government data cannot train public or unauthorized models (RFI-Learning-System A00002.pdf): "Using Government data to train public or otherwise unauthorized commercial models is strictly prohibited."
- Learning-content standards are listed (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "The proposed solution should support xAPI, SCORM 1.2 and 2004, AICC, CMI, HTML5/web output, and JSON."
- An accessibility report is required (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Respondents should provide a current Accessibility Conformance Report using the applicable Voluntary Product Accessibility Template for the proposed solution."
- Remediating legacy courseware for Section 508 is excluded (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Remediation of legacy courseware to current Section 508 standards is not within scope."
- The solution must be U.S.-based with vetted operators (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "The solution must be based in the United States and operated by vetted personnel that meet government security requirements (eg. FedRamped environments)."
- TSA will supply identity and sign-on services (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Respondents should assume TSA will provide identity, single sign-on, and authentication services."
- Support is expected at a hybrid tier level (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "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."
- Academy and training-center operations are in scope (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Academy and training-center operations management is within scope at a broad level."
- The SOO's other constraints are not quoted here, because the sentences are hard to copy exactly. They include 49 CFR Part 1520 (SSI), Section 889 of the NDAA (supply-chain risk management), single sign-on and role-based access, Principle of Least Privilege, Section 508 and WCAG, low-bandwidth performance, and transparent lifecycle pricing with exit support (SOO-Learning-Systems Draft.pdf, Section 6).
Submission Instructions
- Responses go by email in PDF or Word to two named contacts. The deadline was extended to November 6, 2026, which matches the notice (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "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."
- The email subject line is prescribed (RFI-Learning-System A00002.pdf): "State the following in the subject line: Response to TSA Enterprise LMS/LXP RFI 70T01027I8403N002."
- Questions were due by October 27, 2026 (RFI-Learning-System A00002.pdf): "Submit questions regarding this RFI to Siobhan Lawson at Siobhan.Lawson@tsa.dhs.gov and Stacey Davis at Stacey.Davis@tsa.dhs.gov no later than 12:00PM, EST on October 27, 2026." Consolidated-Questions_Answers-RFI-LMS LXP.pdf already contains consolidated answers.
- The response must follow a ten-part outline (RFI-Learning-System A00002.pdf): "TSA requests responses organized as follows:" The parts are cover page, executive summary, company information, technical approach, answers to all Section 6 items, implementation and operational-assessment approach, acquisition approach, ROM lifecycle pricing, assumptions and risks, and past performance.
- The page limit covers the substantive response (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "The 20-page limit applies to the substantive RFI response, including narrative, tables, pricing information, and case studies." The cover letter, table of contents and a separate accessibility attachment do not count.
- Overlapping answers may be cross-referenced (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "Respondents may address substantively overlapping requirements once and use clear cross-references elsewhere in the response."
- The writing must meet the Plain Writing Act (RFI-Learning-System A00002.pdf): "All submissions must comply with the Plain Writing Act of 2010 (Public Law 111-274) to facilitate rapid review."
- ROM pricing should separate one-time and recurring costs (Consolidated-Questions_Answers-RFI-LMS LXP.pdf): "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."
- Each capability should be labeled by how it is delivered: standard commercial, configuration, third-party dependent, customization, or planned future release (RFI-Learning-System A00002.pdf, Section 6 note). The RFI-Learning-System A00002.pdf text is a heading fragment, so it is not quoted.
- Proprietary information must be marked (RFI-Learning-System A00002.pdf): "Minimize and clearly mark any proprietary information or confidential commercial information included."
- Sensitive technical data must not be submitted (RFI-Learning-System A00002.pdf): "Respondents must not submit classified information, system credentials, passwords, detailed security configurations, vulnerability information, or other cybersecurity-sensitive information."
- Section 6.1.1 also asks for legal name, address, point of contact, business size, socioeconomic status and contract vehicles.
Risks and Red Flags
- Date conflicts: RFI-Learning-System A00002.pdf and RFI-Learning-System.pdf give a response due date of 11/2/2026. Consolidated-Questions_Answers-RFI-LMS LXP.pdf (A19) and the notice extend it to November 6, 2026. Use November 6.
- Period-of-performance conflict: Section 6.6 of RFI-Learning-System A00002.pdf and RFI-Learning-System.pdf describes a one-year base plus a "five-year option period." Section 8 and the SOO describe a base plus four options. TSA resolved this as five years total (Consolidated-Questions_Answers-RFI-LMS LXP.pdf, A1).
- Document versions: RFI-Learning-System.pdf is a near-duplicate of RFI-Learning-System A00002.pdf and still contains the duplicate item 6.1.5. TSA says that item was removed (A102). RFI-Learning-System A00002.pdf appears to be the corrected version.
- Inconsistent signals on splitting the work: Section 6.6.2 asks which components could be competed separately. TSA later says it will not consider component or partial-scope responses (A13, A20).
- FedRAMP timing undefined: TSA did not say whether FedRAMP Moderate must be held at RFI, proposal, award or deployment (A72 and A73). It does expect the full solution inside one clearly defined security boundary.
- Heavy SI emphasis with strong controls: Objective 2 calls for a "super-intelligence-enabled" experience. TSA also requires SI to be disableable, human-overseen and authorized before use, and it expects SI to process SSI. Training SI on TSA data needs written approval from a Senior Executive Service employee. The documents state that "Super Intelligence" replaces "AI" under Executive Order 14434. I cannot verify that from these documents, so confirm the terminology.
- Large migration with little source data: Scale is about 127 million records, 4 to 5 TB and 40-year retention. TSA says the current environment is updated manually and gives no schemas, interface specifications or system lists (A53, A56, A58, A64).
- Current systems withheld: Questions mention an SAP SuccessFactors-based Online Learning Center, but TSA declined to confirm incumbent systems, coexistence or the OPM Core HCM path (A29 to A31, A35, A36).
- No budget, schedule or go-live data is provided (A7, A16). Pricing must rest on your own assumptions.
- Tight response limit: 20 pages for 20-plus numbered Section 6 questions plus ROM pricing, and a VPAT is required.
- Lock-in sensitivity: TSA stresses open standards, export in non-proprietary formats and transition-out. Proprietary dependencies must be disclosed (Section 5.1).
- No reimbursement for response costs (RFI-Learning-System A00002.pdf).
The solicitation’s own words on the questions deadline
“Submit questions regarding this RFI to Siobhan Lawson at Siobhan.Lawson@tsa.dhs.gov and Stacey Davis at Stacey.Davis@tsa.dhs.gov no later than 12:00PM, EST on October 27, 2026.”
What the review read
It read 4 of the 4 attachments on this notice, 109,358 characters, all 4 in full.
| Document 1, RFI-Learning-System A00002.pdf | Read in full, 23,778 characters |
| Document 2, SOO-Learning-Systems Draft.pdf | Read in full, 9,630 characters |
| Document 3, RFI-Learning-System.pdf | Read in full, 23,875 characters |
| Document 4, Consolidated-Questions_Answers-RFI-LMS LXP.pdf | Read in full, 52,075 characters |
Read in full means the whole text was taken out of the file. Whether that text was legible is for the review to say: a damaged scan or a broken conversion reads in full and says little.
We do not host these files. Download the originals from SAM.gov
Amendment history
Deadline moved to November 6, 2026 at 12:00 PM EST.
November 3, 2026 at 2:04 PM EST
2 new documents attached.
November 3, 2026 at 2:04 PM EST
Deadline moved to November 4, 2026 at 12:00 PM EST.
October 30, 2026 at 12:04 PM EDT
There is more in the full review
How this solicitation is evaluated, who is eligible and whether it is set aside, and a bid or no-bid assessment. Plus the compliance checklist. On a paid plan, a check against your own NAICS codes and set-aside status, and an assistant that answers questions from the notice itself.
Evaluation Criteria · Eligibility and Set-Aside · Bid / No-Bid Considerations
Sign up free and read 3 solicitationsBrowsing and searching federal opportunities is free forever.
New Computer Systems Design Services (NAICS 541512) notices, by email, weekly
One email a week with what was posted under this page, only in weeks when there is something new. No account. A confirmation link comes first, and every email carries a link to stop.
This is our reading of a public notice, produced automatically, and it is a research aid rather than advice. Always confirm requirements and deadlines against the official notice on SAM.gov before you bid. How this compares to SAM.gov.
Questions? Email Moses Ganiyu directly at talktomoses@instantsam.com. Built by a public-sector statistician with over a decade in government data.