TRANSPORTATION, DEPARTMENT OF › FEDERAL AVIATION ADMINISTRATION › 6973GH FRANCHISE ACQUISITION SVCS
RFI for ENTERPRISE SERVICES CENTER (ESC) — NATIONAL WIRELESS PROGRAM (NWP)
Key facts
- Response deadline
- Nov 20, 2026
- 4:00 PM UTC-05:00
- Set-aside
- Not stated
- Notice type
- Sources sought
- Posted on SAM.gov
- Nov 18, 2026
- Archives Dec 5, 2026
Description
Show the full descriptionShow less
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: Replicating federal financial accounting strings, employee Personally Identifiable Information (PII), and mobile device IMEIs to a secondary database (whether external cloud or on-premise virtual machine) multiplies the physical locations where information at rest must be protected, creating potential duplication and waste in security controls pursuant to 40 U.S.C. Section 11319(d)(1)(C). Storing 100% of core data within the host ServiceNow database ensures that all information at rest remains governed by the agency's existing encryption and access boundaries, thereby increasing the efficiency and effectiveness of pre-existing agency IT investments pursuant to 40 U.S.C. Section 11319(d)(1)(A).
- Control Family IA (Identification and Authentication - IA-2) & AC (Access Control - AC-3): "Control IA-2 (Identification and Authentication - Organizational Users): Uniquely identify and authenticate organizational users... using multi-factor authentication (MFA) that is phishing-resistant..." "Control AC-3 (Access Enforcement): Enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies." Application to this Procurement: A native application natively inherits the host ServiceNow platform's Single Sign-On (SSO) and Personal Identity Verification (PIV) / Common Access Card (CAC) multi-factor authentication configurations. Interfaced architectures require external user accounts, secondary operating system logons, or API service accounts, creating fragmented access enforcement across disconnected systems.
- Control CA-3 (Information Exchange / System Interconnections): "Control: Approve information system interconnections to other systems... verify that the interconnecting systems possess valid authorizations to operate... and prohibit unauthorized information exchange across system boundaries." Application to this Procurement: Operating natively inside ServiceNow eliminates the necessity of establishing external system interconnections for core data processing, thereby avoiding the security risks, Interconnection Security Agreements (ISAs), and vulnerability exposure associated with continuous external API bridges.
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:
- Direct Common Control Inheritance: Deploying a native scoped application within the FAA's ServiceNow Government Community Cloud (GCC) allows the TEM application to directly inherit pre-authorized FedRAMP High and DoD Impact Level 4 (IL-4) controls pursuant to NIST SP 800-37 Rev. 2, Section 3.3.
- Elimination of Standalone Authorization Burden: Deploying a non-native system (whether Model 2 Cloud or Model 3 On-Premises) introduces separate application servers and databases outside the host ServiceNow PaaS boundary. Under Rule FRR201 and NIST SP 800-37, this forces the FAA to author, fund, audit, and maintain a secondary standalone Authority to Operate (ATO) and Security Assessment & Authorization (SA&A) package, creating duplicative and wasteful overhead in direct conflict with 40 U.S.C. Section 11319(d)(1)(C).
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:
- Fulfilling Shared-Service and Consolidation Mandates (Subsections A & B): Deploying a ServiceNow Store-certified native application maximizes the efficiency and effectiveness of the agency's pre-existing enterprise ServiceNow IT investment (Subsection A). Furthermore, as an OMB-designated Financial Management Shared Service Provider (QSMO), ESC directly executes the mandate of Subsection B by centralizing mobile telecom asset management across customer agencies within a unified, pre-existing enterprise platform rather than procuring redundant external software environments.
- Eliminating Lifecycle Duplication, Waste, and Recurring Maintenance Overhead (Subsections C & D): Non-native TEM architectures (Model 2 and Model 3) require continuous agency investments in custom REST/Simple Object Access Protocol (SOAP) API connectors, commercial middleware licensing (e.g., MuleSoft, Boomi), secondary database administration (Oracle/SQL Server), Operating System (OS) patching (RHEL/Windows Server), virtual host allocation (VMware vCPUs/RAM/Storage), secondary Security Operations Center (SOC) monitoring, and continuous regression testing across semiannual ServiceNow family release cycles. Pursuant to Subsection C (identifying potential duplication and waste) and Subsection D (identifying potential cost savings), the FAA requires commercial market data quantifying these recurring lifecycle overhead costs. Requiring an application certified on the official ServiceNow Store eliminates third-party integration broker fees, prevents API deprecation breaks during platform upgrades, and ensures zero custom middleware maintenance costs across the lifecycle of the system, directly achieving the cost savings mandated by Subsection D.
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:
- Unencumbered Historical Retention & Vendor Lock-in Risk Mitigation: In an interfaced architecture (whether Model 2 Cloud or Model 3 On-Premises), historical billing records, line-item rate schedules, and workflow audit logs reside in a separate database schema outside the host ServiceNow enterprise system. In accordance with OMB Circular A-130 Section 5(h), NARA Universal ERM Requirement 3.2 (Record Export and Portability), Cybersecurity and Infrastructure Security Agency (CISA) / Department of Homeland Security (DHS) Cloud Security Technical Reference Architecture (v2.0, Section 3.4), and General Records Schedule (GRS) 1.1 / Federal Acquisition Regulation (FAR) Part 4.7, storing core federal records in non-native secondary databases creates documented risks of vendor lock-in, data egress/extraction penalties, schema translation corruption, and loss of historical transaction records necessary to "protect the legal and financial rights of the Government" under 44 U.S.C. Section 3101.
- Guaranteed Data Sovereignty: With a native scoped application, 100% of historical carrier billing records, rate plan audit trails, and device transaction logs reside permanently inside the FAA's ServiceNow database schema. In accordance with OMB Circular A-130 Section 5(a)(1) (Agency Records Ownership), NARA Universal ERM Requirement 3.1 (In-System Record Retention), and ServiceNow CSDM 4.0 Architecture Governance, in-schema database residency guarantees unencumbered retention, zero extraction fees, and full compliance with statutory records management obligations under 44 U.S.C. Section 3101.
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:
- Avoidance of Proprietary Dependencies: Traditional commercial TEM offerings frequently bundle software with mandatory Business Process Outsourcing (BPO) managed services (as documented in General Services Administration (GSA) Enterprise Telecom Management (ETM) Benchmarks and consistent with vendor lock-in risks identified under OMB Circular A-130 Section 5(h)), wherein routine workflow modifications, approval matrix updates, and custom reporting require proprietary vendor engineering intervention. Pursuant to OMB Memorandum M-19-16 Section II and Question 12 of this RFI, the agency seeks empirical market data to identify solutions that eliminate mandatory BPO operational dependencies.
- Government-Operated Administration ("Tech Stack Only"): A native scoped application utilizes standard ServiceNow low-code workflow tools (Flow Designer, IntegrationHub, Workflow Studio). In accordance with OMB Memorandum M-19-16 Section II (Direct Shared-Service Administration) and ServiceNow CSDM 4.0 Architecture Governance Guidelines, operating natively enables ESC to transition routine business rules and rate administration to certified agency civil service personnel, directly executing OMB M-19-16's directive to build sustainable, government-administered shared-service capabilities while controlling long-term labor costs.
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
- ServiceNow Store Listing Verification: Is your commercial TEM software currently certified and listed on the official ServiceNow Store as a native scoped application? Provide the exact Store Application Title, Store App ID, and current certified platform release family (e.g., Washington DC, Xanadu, Yokohama).
- Scoped Application Installation: Confirm that your software installs 100% directly into the host agency's ServiceNow instance as a registered scoped application within the native schema table. Does any portion of the core execution engine require external server hosting (whether cloud or on-premise VM)?
- Execution Engine & User Interface: Does 100% of your business logic, inventory tracking, and workflow automation execute within the native ServiceNow Glide record engine? Confirm that the administrative user interface resides entirely within native ServiceNow Workspaces and Service Portals.
Category 2: Data Sovereignty, Database Residency & CMDB Authority
- Exclusive Data Residency at Rest (NIST SP 800-53 SC-28): Confirm that 100% of line-item carrier billing data, employee PII, financial accounting strings, and device IMEIs reside permanently at rest within the agency's ServiceNow database tables. Does your architecture mirror, replicate, or store operational data in a secondary database (e.g., external AWS RDS, Azure SQL, or an on-premise database server engine)?
- Authoritative CMDB System of Record (CSDM 4.0): Confirm that the internal ServiceNow Configuration Management Database (CMDB) serves as the singular, authoritative database of record for all wireless asset state changes without relying on batch synchronizations from an external operational master. Detail how your data model natively writes to and extends standard CSDM 4.0 tables (e.g., cmdb_ci_comm_hardware, alm_hardware).
- Historical Data Retention & Sovereignty (44 U.S.C. Section 3101 & OMB Circular A-130): Confirm that in the event of contract termination or service transition, 100% of historical carrier invoices, rate tables, workflow audit trails, and device lifecycle logs remain permanently accessible, queryable, and functional inside the agency's ServiceNow schema at zero additional extraction cost.
Category 3: Cybersecurity Boundary Inheritance & Authentication
- FedRAMP High Boundary Inheritance (NIST SP 800-37 Section 3.3 / FedRAMP RFC-0004 Rule FRR201): Confirm that core TEM workflows and database operations execute entirely within the agency's ServiceNow Government Community Cloud (GCC) tenant, fully inheriting its active FedRAMP High and DoD IL-4 baseline authorizations without requiring an independent agency-level ATO package.
- On-Premise / External Security Assessment Burden (NIST SP 800-37 / Rule FRR204): If your solution deploys via external cloud (Model 2) or on-premise virtual machines within the FAA boundary (Model 3), identify the specific operating system, database engine, STIG compliance requirements, and estimated labor hours required for the agency to author, audit, and maintain a separate ATO package.
- Identity, Authentication & Access Control (NIST SP 800-53 Controls IA-2 & AC-3): Confirm that your application natively and exclusively inherits the host ServiceNow instance's Single Sign-On (SSO), federal PIV/CAC multi-factor authentication, and native Access Control Lists (ACLs), without requiring secondary administrative credentials or API service accounts.
Category 4: Lifecycle Maintenance Overhead, Upgrade Resilience & Government Autonomy
- Elimination of Duplicative Infrastructure & Middleware (40 U.S.C. Section 11319(d)(1)(C)): Does your solution operate without requiring external integration middleware (e.g., MuleSoft, Boomi), custom Scripted REST endpoints, secondary server hardware, OS licensing, or separate database engine licenses? Itemize all secondary infrastructure required to operate your software (including VMware vCPUs, RAM, storage, RHEL/Windows Server licenses, Oracle/SQL Server licenses, and DBA patching labor).
- Biannual Platform Upgrade Validation: Detail your certification and regression testing process prior to ServiceNow's semiannual family release upgrades (e.g., Xanadu to Yokohama). Confirm full test suite coverage under the ServiceNow Automated Test Framework (ATF) and document historical maintenance labor required to maintain API mapping and schema compatibility post-upgrade.
- Transition to Government-Operated "Tech Stack Only" Model (OMB M-19-16): Confirm that your application architecture supports an operational transition to an internally administered model where certified FAA administrators configure business rules, rate schedules, and approval matrices natively using ServiceNow Flow Designer and IntegrationHub without mandatory ongoing vendor managed-service dependency.
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:
- Attn: Samantha Pearce, Contracting Officer
- Email: [email protected]
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.
Contacts
Samantha Pearce · primary
405-954-7739
Attachments
No attachment links are available here.
Record dates
- Posted on SAM.gov: Nov 18, 2026
- The agency’s publication date, as SAM.gov states it.
- First recorded by BidLookup: Nov 18, 2026
- The UTC day of the first read of SAM.gov’s listings that stored this notice.
- Last confirmed: Nov 18, 2026
- The UTC day of the latest read that still listed this notice. It does not mean the notice is unchanged or still open on SAM.gov now, and it is not the index’s last-read time.
Published by the agency on SAM.gov as notice 4b7ba15023f3485b9d1f4d87f5f5f151. What these dates mean
Record
- Solicitation number
- 11182026
- Search the index for this number
- NAICS
- 518210 · Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services
- Place of performance
- Oklahoma City, Oklahoma
- Contracting office
- OKLAHOMA CITY, OK 73125
- SAM.gov notice ID
- 4b7ba15023f3485b9d1f4d87f5f5f151