6973GH Franchise Acquisition Svcs of Federal Aviation Administration posted this Sources Sought on Nov 18, 2026. Responses are due Nov 20, 2026. NAICS 518210 (Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services). Place of performance: Oklahoma. Solicitation number 11182026.
FOR OFFICIAL USE ONLY // PRE-SOLICITATION MARKET RESEARCH
DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION (FAA)
ENTERPRISE SERVICES CENTER (ESC) — NATIONAL WIRELESS PROGRAM (NWP)
MARKET RESEARCH REQUEST FOR INFORMATION (RFI)
Notice ID: 6973GH-27-R-00TEM (Referencing Prior Inquiries under Notice ID: 6973GH-26-R-00TBD)
Title: Enterprise Mobile Technology Expense Management (TEM) Solution: ServiceNow Store Certification, Native Platform Residency, Cybersecurity Control Inheritance, and Lifecycle Cost Optimization
Issuance Date: November 18, 2026.
Response Due Date: November 20, 2026 @ 4:00 PM Eastern
1. Executive Summary, Authority & Strategic Intent
The Federal Aviation Administration (FAA), Enterprise Services Center (ESC), National Wireless Program (NWP), issues this Request for Information (RFI) for market research and acquisition planning purposes in accordance with FAA Acquisition Management System (AMS) Policy Section 3.2.1 (Procurement Planning) and Section 3.2.1.2.1 (Market Analysis).
This inquiry is an investigative market research instrument only. It does not constitute a Screening Information Request (SIR), Request for Offers (RFO), or Request for Proposals (RFP), nor does it commit the FAA to award a contract, enter into a binding agreement, or pay for any information submitted in response to this notice.
1.1 Purpose, Scope, and Mandatory Architectural Baseline
This targeted RFI builds upon baseline functional market research previously conducted under Notice ID 6973GH-26-R-00TBD. While prior market inquiries evaluated high-level functional capabilities across the commercial marketplace (such as invoice auditing, wireless inventory tracking, device lifecycle workflows, and Oracle Enterprise Resource Planning (ERP) integration), technical evaluations and security risk assessments conducted under FAA AMS Section 3.2.1.2.1 Market Analysis have established a mandatory agency technical baseline:
To satisfy binding federal Zero Trust cybersecurity directives under Executive Order (EO) 14028 and Office of Management and Budget (OMB) Memorandum M-22-09, safeguard federal financial accounting records under National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 Rev. 5, enforce Configuration Management Database (CMDB) integrity, and eliminate duplicative infrastructure and unnecessary lifecycle costs pursuant to Title 40 of the United States Code (40 U.S.C.) Section 11319(d)(1)(C), the FAA requires a commercial Technology Expense Management (TEM) solution that is certified on the official ServiceNow Store and executes natively within the agency's pre-existing, accredited ServiceNow Government Community Cloud (GCC) environment.
Commercial TEM solutions listed and certified on the platform must be verified directly on the public ServiceNow Store directory:
Under this mandatory baseline, 100% of core operational data at rest—including telecommunications inventory, device International Mobile Equipment Identity (IMEI) numbers, employee Personally Identifiable Information (PII), carrier billing records, and agency general ledger accounting strings—must reside exclusively within the agency's ServiceNow database schema. Interfaced, standalone, or external Software as a Service (SaaS) architectures that mirror, replicate, stage, or maintain primary operational records in external third-party cloud environments (e.g., external Amazon Web Services (AWS) Relational Database Service (RDS), Microsoft Azure Structured Query Language (SQL), or proprietary vendor-hosted servers) do not satisfy the agency's minimum cybersecurity, data sovereignty, and lifecycle operational requirements.
The purpose of this RFI is to formally survey the commercial market to evaluate all deployment models (including Native Scoped Applications, Interfaced External SaaS, and Interfaced On-Premises deployments) to gather empirical technical, security, and lifecycle cost data across the entire commercial marketplace.
2. Institutional Background & Shared Service Provider Authority
Establishment & Statutory Authority: Conceptually founded in 2003 and formally established in 2005 under the Mike Monroney Aeronautical Center (MMAC), the Federal Aviation Administration (FAA), and the U.S. Department of Transportation (DOT), ESC operates under the statutory authority of the Administrative Services Franchise Fund which was established by the Department of Transportation and Related Agencies Appropriations Act of 1997 (Public Law 104-205), to deliver shared technical, financial, and Information Technology (IT) solutions across federal civil departments and agencies.
Location & Operational Scale: Headquartered in Oklahoma City, OK, ESC maintains an enterprise workforce of over 700 federal civil servants and specialized technical support contractors delivering mission-critical enterprise shared services across the executive branch.
QSMO Shared Service Designation & Value Proposition: In accordance with OMB Memorandum M-19-16 ("Centralized Mission Support Capabilities for the Federal Government"), ESC serves as an OMB-designated federal Financial Management Quality Services Management Office (FM-QSMO) Shared Service Provider (SSP). ESC centralizes financial, business, and IT operations for more than 40 federal agencies. By offering a standardized catalog of modern, secure, and pre-vetted enterprise solutions, ESC executes the statutory mandate of the Federal Information Technology Acquisition Reform Act (FITARA) (40 U.S.C. Section 11319(d)(1)(B)) by consolidating IT acquisitions, increasing shared-service delivery models, standardizing federal financial reporting, and eliminating duplicate administrative systems across the federal government.
3. Operational Drivers: Workforce Realignment & Platform Consolidation
In furtherance of its Shared Service Provider mandate and executive branch directives on workforce optimization, ESC continuously refines internal operations to sustain service delivery standards while controlling lifecycle labor costs.
Following workforce realignments under the federal Deferred Resignation Program (DRP), ESC faced the operational imperative to maintain uninterrupted delivery of mission-critical financial management and asset tracking services with a leaner personnel footprint. To mitigate institutional knowledge loss and eliminate manual handoffs, ESC accelerated an enterprise digital modernization strategy centered on a unified enterprise platform:
4. Current Enterprise ServiceNow Footprint & Realized Value
To date, pursuant to 40 U.S.C. Section 11319(d)(1)(B), (D), & (E), ESC has consolidated core enterprise capabilities into its centralized ServiceNow platform, establishing an authoritative single source of truth across customer agencies:
Realized Efficiencies Realized by ESC:
5. Functional Scope: Telecom Expense Management (TEM) Expansion
The National Wireless Program (NWP), pursuant to 40 U.S.C. Section 11319(d)(1)(A) & (B), requires commercial software to expand this unified operational architecture into telecommunications and mobile expense lifecycle management across an active inventory exceeding 37,000 wireless devices and service plans.
The commercial solution must deliver the following functional capabilities natively within ServiceNow:
6. Architectural Classification & Evaluation Framework
To ensure an exhaustive market evaluation that addresses all commercial deployment options, the FAA classifies potential TEM deployment architectures into three distinct operational models:
Figure 1: Architectural Classification Framework comparing Model 1 (Embedded Native Scoped App inheriting GCC FedRAMP High boundary) against Model 2 (Interfaced External SaaS) and Model 3 (Interfaced On-Premises Virtual Machine (VM) within the FAA Boundary).
6.1 Architectural Topology Comparison Matrix
The following matrix further details the difference between the three architectures, the mandatory native model against both external cloud and on-premise interfaced architectures:
Technical Evaluation Dimension
Model 1: Mandatory Native Scoped Application
Model 2: Non-Compliant Interfaced External SaaS
Model 3: Non-Compliant Interfaced On-Premises (FAA Boundary)
Store Certification
Actively certified on official ServiceNow Store
Uncertified external connector
Uncertified external connector
Database Residency at Rest (NIST SC-28)
100% inside agency ServiceNow GCC database tables
Stored externally in AWS RDS, Azure SQL, or vendor cloud
Stored in separate on-premise database server engine (Oracle/SQL)
Authoritative System of Record
Internal ServiceNow CMDB is sole master (CSDM 4.0)
External vendor cloud acts as operational master
External on-premise database acts as operational master
Security Boundary & ATO (NIST SP 800-37)
Directly inherits agency Federal Risk and Authorization Management Program (FedRAMP) High / Impact Level 4 (IL-4) Platform as a Service (PaaS) Authority to Operate (ATO)
Requires separate Third-Party Assessment Organization (3PAO) assessment and external cloud ATO
Requires separate Operating System (OS)/Database (DB) Security Technical Implementation Guide (STIG) auditing, scanning, and Security Assessment and Authorization (SA&A) ATO package
Middleware & API Overhead (FITARA)
Zero middleware or Application Programming Interface (API) connector maintenance
High recurring API maintenance and middleware licensing (MuleSoft/Boomi)
Requires custom Representational State Transfer (REST) API scripts and maintenance across ServiceNow releases
Platform Upgrades
Pre-tested via ServiceNow Store certification
High risk of API breakage and custom code remediation
High risk of API script breaks and database schema synchronization drift
Duplication & Waste (40 U.S.C. Section 11319)
Zero duplicate servers, OS licenses, DB engines, or VMware VMs
Duplicative external cloud hosting and security monitoring
Duplicative server hardware/VMware instances, OS licensing, DB licenses, Database Administrator (DBA) labor, and Security Operations Center (SOC) monitoring
Records Sovereignty (44 U.S.C. Section 3101)
100% of audit logs remain in agency schema
Locked in vendor cloud; subject to extraction fees
Stored in separate database schema requiring custom export scripts
7. Federal Statutory & Executive Authorities Justifying This Requirement
The agency's requirement for a ServiceNow Store-certified, natively hosted TEM solution is grounded directly in binding federal statutes, executive orders, cybersecurity standards, and fiscal mandates:
7.1 Executive Order 14028 & OMB Memorandum M-22-09 (Zero Trust Architecture)
Executive Order 14028: Improving the Nation's Cybersecurity: https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-14028-improving-the-nations-cybersecurity/
OMB Memorandum M-22-09: Moving the U.S. Government Toward Zero Trust Cybersecurity Principles: https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf
Under Executive Order (EO) 14028 Section 10(k), Congress and the President define Zero Trust Architecture as follows:
"(k) The term 'Zero Trust Architecture' means a security model, a set of system design principles, and a coordinated cybersecurity and system management strategy based on an acknowledgement that threats exist both inside and outside traditional network boundaries. The Zero Trust security model eliminates implicit trust in any one element, node, or service and instead requires continuous verification of the operational picture via real-time information from multiple sources to determine access and other system responses."
Furthermore, Section 3(a) of Executive Order 14028 directs executive agencies:
"The Federal Government must adopt security best practices; advance toward Zero Trust Architecture; accelerate movement to secure cloud services, including Software as a Service (SaaS), Infrastructure as a Service (IaaS), and Platform as a Service (PaaS); centralize and streamline access to cybersecurity data to drive analytics for identifying and managing cybersecurity risks; and invest in both technology and personnel to match these modernization goals."
Implementing this directive, OMB Memorandum M-22-09 (Section C, "Meeting Specific Cybersecurity Standards - Asset Management") sets binding federal requirements:
"Agencies must maintain complete, inventory-level visibility of all enterprise devices... Federal civilian agencies must integrate dynamic asset management with Continuous Diagnostics and Mitigation (CDM) capabilities to maintain real-time operational picture and dynamic risk posture."
In executing these mandates, the FAA establishes that:
7.2 NIST SP 800-53 Rev. 5 (Security and Privacy Controls for Information Systems)
NIST SP 800-53 Rev. 5: Security and Privacy Controls for Information Systems and Organizations: https://csrc.nist.gov/pubs/sp/800-53/r5/upd1/final
The agency's native residency mandate directly enforces the verbatim control baselines established by the National Institute of Standards and Technology (NIST):
7.3 NIST SP 800-37 Rev. 2 & FedRAMP Boundary Policy RFC-0004 (Control Inheritance)
NIST SP 800-37 Rev. 2: Risk Management Framework for Information Systems: https://csrc.nist.gov/pubs/sp/800-37/r2/upd1/final
FedRAMP Request for Comments (RFC)-0004: Cloud Authorization Boundary Guidance: https://www.fedramp.gov/rfcs/0004/
Defense Information Systems Agency (DISA) Department of Defense (DoD) Cloud Computing Security Requirements Guide (DoD CC SRG): https://dl.dod.cyber.mil/wp-content/uploads/aero/pdf/dod_cc_srg_v1r3.pdf
Under NIST SP 800-37 Rev. 2, Section 3.3 ("Common Control Providers and Control Inheritance"):
"Common controls are controls whose implementation results in a security or privacy capability that can be inherited by one or more organizational systems... Inheriting common controls from a pre-authorized host system significantly reduces the cost and complexity of security assessments and eliminates redundant authorization processes."
Furthermore, FedRAMP RFC-0004 establishes binding authorization boundary rules:
"Rule FRR201: The Cloud Service Provider (CSP) authorization boundary must include all internal and external components, services, and connections that process, store, or transmit federal data."
"Rule FRR204: Any external service or data store that resides outside the authorized boundary must hold an independent, comparable FedRAMP authorization or be formally evaluated through a separate risk assessment and interconnect authorization."
In applying these standards:
7.4 Federal Information Technology Acquisition Reform Act (FITARA) — 40 U.S.C. Section 11319(d)
Federal Information Technology Acquisition Reform Act (FITARA) — 40 U.S.C. Section 11319: https://www.govinfo.gov/app/details/USCODE-2014-title40/html/USCODE-2014-title40-subtitleIII-chap113-subchapII-sec11319.htm
Under 40 U.S.C. Section 11319(d), Congress mandates that executive agencies systematically review their information technology portfolios to achieve measurable operational and fiscal efficiencies:
"(d) Information Technology Portfolio, Program, and Resource Reviews.— (1) Process.—The Director of the Office of Management and Budget, in consultation with the Chief Information Officers of appropriate agencies, shall implement a process to assist covered agencies in reviewing their portfolio of information technology investments— (A) to identify or develop ways to increase the efficiency and effectiveness of the information technology investments of the covered agency; (B) to identify or develop opportunities to consolidate the acquisition and management of information technology services, and increase the use of shared-service delivery models; (C) to identify potential duplication and waste; (D) to identify potential cost savings; (E) to develop plans for actions to optimize the information technology portfolio, programs, and resources of the covered agency; (F) to develop ways to better align the information technology portfolio, programs, and financial resources of the covered agency to any multi-year funding requirements or strategic plans required by law; (G) to develop a multi-year strategy to identify and reduce duplication and waste within the information technology portfolio of the covered agency, including component-level investments and to identify projected cost savings resulting from such strategy; and (H) to carry out any other goals that the Director may establish."
In executing its statutory responsibilities under Section 11319(d)(1), the FAA establishes the following market research evaluation parameters:
7.5 Federal Records Act (44 U.S.C. Chapter 31) & OMB Circular A-130 (Data Sovereignty)
Federal Records Act — 44 U.S.C. Section 3101: https://www.govinfo.gov/app/details/USCODE-2020-title44/html/USCODE-2020-title44-chap31.htm
OMB Circular A-130: Managing Information as a Strategic Resource: https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/circulars/A130/a130revised.pdf
National Archives and Records Administration (NARA) Universal Electronic Records Management (ERM) Requirements: https://www.archives.gov/records-mgmt/policy/universal-erm-requirements
Under 44 U.S.C. Section 3101 (Records Management by Agency Heads; General Duties):
"The head of each Federal agency shall make and preserve records containing adequate and proper documentation of the organization, functions, policies, decisions, procedures, and essential transactions of the agency and designed to furnish the information necessary to protect the legal and financial rights of the Government and of persons directly affected by the agency’s activities."
Furthermore, 44 U.S.C. Section 3102 mandates:
"The head of each Federal agency shall establish and maintain an active, continuing program for the economical and efficient management of the records of the agency. The program, among other things, shall provide for— (1) effective controls over the creation and over the maintenance and use of records in the conduct of current business..."
In accordance with OMB Circular A-130, Section 5(a)(1) and Section 5(h):
"Agencies must maintain ownership and control over all Federal records created or maintained on their behalf by commercial contractors or cloud service providers... Contractual terms must prevent vendor lock-in, ensure the agency retains unencumbered rights to its data, and guarantee that records can be exported or preserved without penalty or proprietary impediment."
Application to this Procurement:
7.6 OMB Memorandum M-19-16 (Operational Autonomy & Shared Service Sustainability)
OMB Memorandum M-19-16: Centralized Services Regarding Quality Services Management Offices: https://www.whitehouse.gov/wp-content/uploads/2019/04/M-19-16.pdf
Under OMB Memorandum M-19-16, Section II ("Policy"):
"To drive efficiency, reduce duplication, and improve customer experience across the Federal Government, agencies designated as Quality Services Management Offices (QSMOs) shall establish and manage centralized shared-service marketplaces... Agencies must optimize their operating models by utilizing standardized, pre-existing enterprise platforms rather than establishing standalone, custom-managed IT environments... Agencies must prioritize modern solutions that empower internal agency staff and shared-service providers to administer enterprise services directly, avoiding vendor-proprietary operating dependencies."
Application to this Procurement:
8. Targeted Technical & Architectural Questionnaire
Respondents are requested to provide direct, verified technical answers and supporting architectural documentation for the following twelve (12) clarification questions across all proposed deployment models:
Category 1: ServiceNow Store Certification & Application Architecture
Category 2: Data Sovereignty, Database Residency & CMDB Authority
Category 3: Cybersecurity Boundary Inheritance & Authentication
Category 4: Lifecycle Maintenance Overhead, Upgrade Resilience & Government Autonomy
9. Submission Instructions & Administrative Information
Submission Format: Submissions must be delivered in searchable Portable Document Format (PDF) or Microsoft Word format, not exceeding twelve (12) pages total (excluding existing GSA schedule pricelists and technical architectural diagrams).
Delivery Point: Submit all responses via email directly to the Contracting Officer:
Response Due Date: November 20, 2026 @ 4:00 PM Eastern.
Email Subject Line: RFI Response - FAA ESC Native TEM ServiceNow Architecture (Notice ID: 6973GH-26-R-00TEM)
Data Rights & Proprietary Information: The Government will not pay for any information submitted in response to this RFI. Offerors must clearly mark proprietary, confidential, or business-sensitive data on every applicable page. Proprietary materials will be protected in accordance with the Trade Secrets Act (18 U.S.C. Section 1905), the Freedom of Information Act (5 U.S.C. Section 552), and applicable federal procurement statutes.
The operating system for your proposal team - for federal and state contractors. Submit a polished proposal with minimal effort.
Plans from $129 a month, or $99 a month billed yearly.