BidTerrierSign in

RFI for ENTERPRISE SERVICES CENTER (ESC) - NATIONAL WIRELESS PROGRAM (NWP)

Transportation, Department of, Federal Aviation Administration

This bid is closed.

It closed on Nov 20, 2026, 4:00 PM ET. The page stays up for reference. See open IT services and software bids.

View the official notice at sam.gov

The official notice is always free. Read the full documents there before you bid.

Key facts

Closed
Nov 20, 2026, 4:00 PM ET
Place of work
Oklahoma City, Oklahoma
Notice type
Sources soughtThe agency is checking which businesses could do the work. It is not a request for a bid.
Solicitation number
11182026
Office
6973GH FRANCHISE ACQUISITION SVCS
Posted
Nov 18, 2026
Codes
NAICS 518210
Contact in the notice
Samantha Pearce, samantha.a.pearce@faa.gov
Source
SAM.gov Contract Opportunities

What this is

This is a Request for Information (RFI) from the Federal Aviation Administration (FAA). The agency is seeking information on Technology Expense Management (TEM) solutions. The purpose is to conduct market research and plan for a future acquisition.

AI summary of the public notice. Check the official notice before you bid.

Report a problem with this summary How we use AI

Full summary

The full summary of this notice is for signed-in users

  • Who can bid
  • Key dates
  • What the work includes
  • How to respond
  • Requirements to watch for

A free account lets you read 3 full summaries a day and save one search with a daily email. The official notice stays free for everyone.

Similar open bids

More IT services and software bids

Recent awards from Transportation, Department of

Award notices this agency published, as listed by the source.

Original description from the notice

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: ServiceNow Store: Technology & Telecom Expense Management Directory: https://store.servicenow.com/store/search?q=telecom+expense+management 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: Automation as an Operational Forcing Function: Consolidating disparate administrative functions into the enterprise ServiceNow platform serves as an operational forcing function, allowing ESC to absorb workforce shifts by automating manual touchpoints, standardizing cross-agency approval hierarchies, and maximizing personnel productivity. Elimination of Disconnected Operational Silos: Moving away from disparate point solutions enables technical and functional teams to administer unified workflows within a single operating fabric, eliminating the maintenance burden of disconnected third-party databases, manual reconciliations, and custom batch Extract, Transform, Load (ETL) routines pursuant to 40 U.S.C. Section 11319(d)(1)(C). Shared-Service Velocity: This operational consolidation ensures that ESC fulfills its performance commitments as a designated Federal Shared Service Provider without sacrificing operational velocity, data hygiene, or customer responsiveness. 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: Enterprise Help Desk & Incident Management: Centralized multi-tenant ticketing, omnichannel service intake, and automated routing. Hardware Asset Management (HAM): Lifecycle tracking of IT physical assets from procurement through sanitization and disposal in compliance with NIST SP 800-88 Rev. 1 (Guidelines for Media Sanitization). Software Asset Management (SAM): Software license position reconciliation, compliance tracking, and audit readiness aligned with federal FITARA standards. IT Asset Discovery: Automated discovery and inventory scanning across federal network infrastructure. Vulnerability & Compliance Tracking: Unified security vulnerability logging, remediation workflow tracking, and Federal Information Security Modernization Act (FISMA) reporting. Automated Workflow Orchestration: Standardized approval matrices, proactive notification triggers, and non-repudiation audit logging. Executive Dashboards & Operational Analytics: Real-time visibility into operational velocity, shared-service metrics, and financial resource allocation. Automated Customer Interfacing & Reporting: Role-based self-service portals and automated reporting delivered to customer agencies. Realized Efficiencies Realized by ESC: Reduction in Platform Maintenance Overhead: Consolidating standalone legacy software packages eliminated duplicative software license fees, server infrastructure footprints, and separate administrative support contracts pursuant to 40 U.S.C. Section 11319(d)(1)(C) & (D). Workforce Efficiency in Data Center Operations: Decreased manual patching, compliance reporting, and systems administration overhead across the ESC Enterprise Data Center (EDC) pursuant to 40 U.S.C. Section 11319(d)(1)(D). Support Desk Ticket Deflection: Deflected substantial volumes of manual service tickets to customer self-service catalogs governed by automated routing, significantly reducing tier-one support labor pursuant to 40 U.S.C. Section 11319(d)(1)(D). Definitive Single Source of Truth: Established authoritative, real-time data integrity across configuration, ownership, and financial chargeback records without synchronization latency or data drift pursuant to 40 U.S.C. Section 11319(d)(1)(A). 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: Centralized Asset & Inventory Repository: Centralize wireless hardware, active phone lines, IMEI/Subscriber Identity Module (SIM) identifiers, carrier contract terms, rate plan structures, and user assignments within the enterprise CMDB (Common Service Data Model (CSDM) 4.0 compliant). Automated Physical & Logical Lifecycle Tracking: Maintain automated tracking of device allocation linked directly to federal personnel profiles, cost centers, departments, and physical duty stations. Carrier Invoice Ingestion & Parsing: Ingest, parse, and normalize complex electronic billing files across major carriers (AT&T/FirstNet, Verizon Wireless, T-Mobile). Automated Audit & Reconciliation Engine: Perform automated line-item auditing against carrier contract schedules to systematically detect billing discrepancies, orphaned/zero-use lines, plan misallocations, and unauthorized surcharges prior to invoice approval. Standardized MACD Workflows & Self-Service Catalog: Provide standardized workflows for Moves, Adds, Changes, and Disconnects (MACD) and role-based provisioning portals with built-in supervisory approval hierarchies. Granular Financial Allocation & Chargebacks: Calculate and assign detailed billing allocations down to specific accounting strings for automated general ledger posting to DOT's financial system of record (Delphi / Oracle E-Business Suite). The system shall provide native, documented APIs or pre-built connectors supporting integration with Unified Endpoint Management (UEM) and Mobile Device Management (MDM) platforms to enable future ingestion of device posture telemetry in accordance with Executive Order 14028 Zero Trust Architecture requirements. The system shall generate customizable financial reports and dashboards that allocate costs by organizational hierarchy (e.g., agency, department, branch) and provide actionable rate optimization recommendations (e.g., discounted pricing tiers, commitment plans, or licensing adjustments) to reduce ongoing operational spend. Accessibility Compliance: Full accessibility compliance in accordance with Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. Section 794d) and Title 36 of the Code of Federal Regulations (36 C.F.R.) Part 1194. 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: Model 1: Embedded Native Scoped Application (Mandatory Target) Model 2: Non-Compliant Interfaced External SaaS / Vendor Cloud Model 3: Non-Compliant Interfaced On-Premises (External Server within FAA Boundary) 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: Real-Time Dynamic Verification vs. Batch API Latency: Interfaced TEM architectures (both Model 2 External Cloud and Model 3 On-Premises) rely on scheduled batch API synchronizations (e.g., nightly or weekly polling). This latency creates temporal gaps where device status changes, employee reassignments, or compromised mobile endpoints are masked from agency CDM monitoring tools, violating EO 14028's requirement for "continuous verification of the operational picture via real-time information." In-Place Event-Driven Processing: A native scoped application updates device records and ownership mappings in real time directly at the database layer, ensuring instantaneous, event-driven security visibility required by OMB M-22-09. 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): Control SC-28 (Protection of Information at Rest): "Control: Protect the confidentiality and integrity of [Assignment: organization-defined information at rest]." "Discussion: Information at rest refers to the state of information when it is located within storage devices as specific components of information systems... Unauthorized access to, or exfiltration of, sensitive information at rest can compromise system integrity and individual privacy." Application to this Procurement: Replicat

Source: SAM.gov, General Services Administration (public domain). BidTerrier shows public notices as published and cannot confirm that a notice is complete or current. Details can change, so always check the official notice. Nothing here says whether your business is eligible.