AFAS_Salilent Characteristics.docx
DOCX document 22 KB Posted
- Attached to
- Aviation Fuel Accounting Software
- Solicitation number
- FA4452-26-AFAS-SS
About this file
This is a Salient Characteristics document supporting a Sources Sought Notice for web-based Aviation Fuel Accounting Software. The Air Force Air Mobility Command (AMC) seeks a commercial-off-the-shelf enterprise-level software solution to manage aviation fuel transactions conducted by Air Force crews globally under the AMC AD AIR CARD Program. The requirement encompasses fuel receipt and bill reconciliation, fuel transaction and alert validation, and in-flight refuel management for a 12-month period beginning September 30, 2026.
The software must provide scalable, enterprise-wide capabilities including automatic fuel transaction management, command-wide visibility, auto-matching functionality, sales receipt transaction importing, and data and metrics collection. The solution will serve multiple Air Force installations and must integrate with DoD fuel purchase reconciliation processes. Any awarded vendor must obtain Department of the Air Force Authority to Operate (ATO) certification. The Air Force is conducting market research to identify qualified sources among large and small businesses, including Small Disadvantaged Businesses, HUBZone Firms, Certified 8(a) Businesses, Service-Disabled Veteran-Owned Small Businesses, and Women-Owned Small Businesses. This pre-solicitation notice is issued for information and planning purposes only and does not constitute a binding commitment by the Government.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Aviation Fuel Accounting Software Salient Characteristics
I. Core System & SaaS Scalability
· Scalable Enterprise SaaS Architecture: Must be an enterprise-wide, web-based Software as a Service (SaaS) solution capable of accounting for all aviation fuel transactions conducted globally by Air Force crews.
· Capacity Beyond Current Footprint: The platform's SaaS architecture must possess the inherent capacity to scale and support operations beyond the currently identified 11 CONUS Document Control Officers (DCOs), allowing for seamless expansion to additional users, units, and commands without system degradation or custom code rewrites.
· End-to-End Reconciliation: Must organize, automate, and manage the entire aviation fuel accounting reconciliation process in strict compliance with Air Force Instruction (AFI) 11-253.
· Legacy System Interoperability: Must natively interface with and pull data from legacy and external Air Force systems (including EEBP, CRIS, and REMIS) to compare, validate, and audit transaction data.
· Command-Wide Visibility: Must provide real-time, command-wide visibility of fuel transactions and execution metrics across the entire enterprise.
II. Fuel Transaction Program Manager (FTPM) Capabilities
· Automated Business Rules: Must utilize automated validation rules to instantly identify and flag:
· Duplicate fuel billings.
· Errors in unit cost charges.
· Invalid fuel charges (e.g., fuel billed to an aircraft no longer assigned to that specific wing).
· Automated Matching & Data Import: Must automatically ingest sales receipt data and match transactions to streamline the reconciliation workload.
· Analytics & Reporting: Must aggregate historical transaction data and operational metrics to generate reports and support end-of-year closeouts (such as tracking unbilled charges across fiscal years).
III. Fuel In-flight Program Management (FIPM) Capabilities
· Electronic Flight Bag (EFB) Integration: Must be fully approved to operate on government-issued EFBs, enabling aircrews to electronically record in-flight secondary sales.
· Electronic DD Form 791 Workflows: Must provide an electronic process for generating, routing, and sign-off on the DD Form 791 (Inflight Refueling Transmitter Sheet).
· In-Flight Tail Validation: Must perform real-time aircraft tail number validation during flight to ensure billing accuracy for tanker offloads.
· Immediate Ground-to-Air Synchronization: Must interface seamlessly with the ground-based FTPM module to provide Home Station personnel with immediate, worldwide visibility of in-flight offloads.
· Multi-Role Coordination & Digital Signatures: Must support role-based workflows (Boom Operator, FMS, POL, WRDCO) and secure digital signatures, specifically for the verification of Foreign Military Sales (FMS) transactions.
File details come from the government source that posted it. Updated .