DAF SBIR DAF26BZ06-NV036: Flightline Radio Network
Quick Answer
DAF26BZ06-NV036 is a Department of the Air Force SBIR Phase I topic under the DAF 2026 SBIR Broad Agency Announcement, Release 6. The Air Force wants a secure, adaptable, interoperable private cellular network for the flight line at Edwards Air Force Base, built on 5G and Open Radio Access Network architecture, to support aircraft maintenance, logistics, and test and evaluation operations. Awards are up to $250,000 for a period of performance up to 6 months, with a 20 page or slide technical volume limit. The topic opens September 23, 2026 and closes October 21, 2026 through the Defense SBIR/STTR Innovation Portal.
Two features make this the most accessible topic in the release for a commercial company. First, it is a named-site problem: Edwards AFB, its existing infrastructure, its flight line, and the 412th Maintenance Group as an eventual transition partner. That specificity means the winning proposal will be the one that understands the site, not just the technology. Second, the technology itself is commercial. 5G Open RAN, private cellular, and augmented reality maintenance support all exist in industry today, and the topic starts the technology at Technology Readiness Level 4. This is an adaptation and integration problem, not a research problem, and the Phase I deliverable is a feasibility study with initial design and a preliminary prototype proof-of-concept.
Topic At a Glance
Topic number: DAF26BZ06-NV036
Title: Flightline Radio Network
Solicitation: Department of the Air Force 2026 SBIR Broad Agency Announcement (BAA), Release 6, Phase I Proposal Submission Instructions
Program type: Phase I
Award maximum value: $250,000
Award maximum duration: 6 months
Technical volume page limit: 20 pages or slides
OUSD (R&E) Critical Technology Area: Quantum and Battlefield Information Dominance (Q-BID)
Component Technology Priority Areas: Integrated Network System-of-Systems; Sustainment and Logistics; FutureG
Projected CMMC level requirement: Level 2 (Self)
Export control status: no topic-level ITAR or EAR restriction paragraph appears on this topic, unlike NV034 in the same release. General disclosure obligations still apply
Site: Edwards Air Force Base flight line
Technology readiness at project start: TRL 4
Phase I success criterion: the topic states achieving TRL 3 to 4
Target at end of Phase II: TRL 6, with the topic also stating a targeted advancement to TRL 6 to 7 by end of Phase II
Phase III target: TRL 7
Named transition partners: the 412th Maintenance Group, Air Force Materiel Command, and commercial partners, supported by Air Force Sustainment Center and AFLCMC funding
Program alignment: Advanced Battle Management System (ABMS)
Minimum work performed in house: two-thirds of the research or analytical effort
Subcontract and consultant cap: one-third of total contract price, profit excluded
Technical and Business Assistance: up to $6,500 per Phase I award
Type size: no smaller than 10-point
Topic open date: September 23, 2026
Proposal deadline: October 21, 2026, at the time stated in the DoW FY26 SBIR BAA
Selection timeline: within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027
Submission portal: DSIP at dodsbirsttr.mil
Keywords: 5G, private cellular, flight line, aircraft maintenance, secure communications, predictive maintenance, augmented reality, Edwards AFB, logistics
Note on the deadline time. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the proposal submission deadline date and time. DoW SBIR deadlines are ordinarily 12:00 p.m. Eastern on the close date. Confirm the exact time on the live DSIP posting rather than assuming end of day.
What the Air Force Is Actually Looking For
The operational problem at Edwards
Flight line operations at Edwards Air Force Base face increasing demands for more efficient, secure, and real-time communication systems to enhance aircraft maintenance, logistics, and operational performance. The Air Force is direct about why current arrangements fall short: current communication solutions are limited by outdated infrastructure, lack of interoperability, and insufficient data transmission capabilities.
There is a distinct opportunity to leverage advanced cellular network technologies, particularly 5G and Open Radio Access Network architectures, to address these limitations and modernize the flight line environment.
Note that Edwards is a test and evaluation base, which shapes the requirement. The objective states that the effort aims to support advanced test and evaluation activities, promoting a high-performance communication environment that meets the stringent demands of a modern Air Force Base. A flight line at a test wing generates instrumentation data, telemetry, and rapidly changing configurations in a way that an operational fighter wing does not, and the Range Commanders Council IRIG 106 telemetry standards reference in the topic reinforces that this environment has its own data conventions.
The objective
The objective is to explore and develop innovative technologies leveraging cellular network infrastructure, particularly Open RAN architectures, to enhance communication capabilities on the flight line at Edwards AFB. The goal is to establish a secure, adaptable, and interoperable cellular network that facilitates superior aircraft maintenance, logistics, and operational efficiency.
This research and development initiative will focus on feasibility studies, system design, and foundational prototyping, ensuring flexibility for future adaptation and integration into subsequent phases based on Phase I outcomes and insights.
That last sentence tells you the shape of the Phase I effort. Feasibility studies, system design, and foundational prototyping, with deliberate flexibility rather than a locked architecture.
The use cases the Air Force names
The topic is specific about what the network is for, and each named use case is a place your proposal should say something concrete.
Ground crew coordination. The project will focus on enhancing ground crew coordination, which is the baseline voice and data communication problem.
Real-time aircraft health monitoring. Enabling real-time aircraft health monitoring, which implies on-aircraft or on-equipment data collection moving over the network while the aircraft is on the ground.
Predictive maintenance. Supporting predictive maintenance to reduce aircraft downtime and enhance mission readiness. This is the value argument, since downtime is the cost the Air Force is trying to reduce.
Augmented reality maintenance support. Augmented reality applications will be integrated to provide maintenance personnel with real-time guidance, schematics, and remote support, further optimizing maintenance tasks. Note the specificity: guidance, schematics, and remote support. AR is named as an integrated application, not an aspiration, which means bandwidth and latency budgets for AR belong in your design.
Improved data sharing and operational efficiency. The aim is a secure, adaptable, and interoperable network that improves real-time communication, data sharing, and operational efficiency at Edwards AFB.
The technical direction
From a technical standpoint, the initiative will employ a 5G Open RAN architecture, offering increased flexibility, interoperability, and security while minimizing vendor lock-in and lowering costs.
Vendor lock-in avoidance and cost reduction are named as reasons for Open RAN, which is worth registering. The Air Force is not asking for Open RAN because it is fashionable; it is asking because a disaggregated, multi-vendor architecture is the procurement outcome it wants. A proposal built on a single-vendor proprietary stack answers a different question.
The modular design of this network will allow it to accommodate evolving test requirements and future upgrades, ensuring a scalable and cost-effective solution.
The network will integrate seamlessly with Edwards AFB's existing infrastructure and employ efficient frequency allocation through spectrum sharing mechanisms.
Those last two clauses are the hard parts, and they are the ones a commercial cellular vendor is most likely to underestimate. Integration with existing base infrastructure means engaging with what is already there rather than overlaying a greenfield network. Spectrum sharing at a Department of Defense test range is a genuinely constrained problem, involving federal spectrum allocations, range operations, and coordination that has no commercial analogue.
Interference with aircraft systems is a named requirement
The detailed Phase I description states that the effort will outline network architecture, components, deployment strategy, and address potential interference with aircraft systems.
This deserves emphasis because it is where a commercial telecom proposal most often fails to persuade a flight test audience. Radiating RF energy near aircraft, in a flight test environment, next to instrumentation and telemetry systems, raises electromagnetic interference and electromagnetic environmental effects questions that must be addressed on their own terms. Phase II reinforces this, stating that testing will evaluate performance and ensure compatibility with aircraft systems. If your proposal treats interference as a footnote, a reviewer from the test community will notice.
Phase I
The topic describes Phase I twice, and the two descriptions are complementary rather than contradictory.
The summary version: conduct feasibility studies and initial system design. This includes analyzing current flight line communication requirements, exploring Open RAN components, and developing foundational prototypes. Deliverables will include a comprehensive feasibility report, initial design schematics, and a preliminary prototype proof-of-concept.
The detailed version: Phase I will assess the feasibility of an Open RAN network for flight line use at Edwards AFB. It will outline network architecture, components, deployment strategy, and address potential interference with aircraft systems. Deliverables include security analysis, use cases, and integration plans. Success includes achieving TRL 3 to 4, demonstrating proof-of-concept through a preliminary prototype and feasibility report.
Combined, your Phase I deliverable list is: a comprehensive feasibility report, initial design schematics, a preliminary prototype proof-of-concept, a security analysis, documented use cases, and integration plans. That is six named items in six months, and every one of them is a document or a bench-level demonstration rather than a fielded system. Scope accordingly.
Note a small inconsistency in the source. The topic states the anticipated TRL at the start of the project is TRL 4, but then says Phase I success includes achieving TRL 3 to 4. Starting at 4 and succeeding by reaching 3 to 4 does not quite parse. The most sensible reading is that commercial Open RAN technology generally sits at TRL 4 or higher, while the specific flight line application at Edwards is what needs to be brought to TRL 3 to 4. Frame your maturity claims in terms of the application rather than the underlying technology, and describe what you will actually demonstrate.
Phase II
Phase II will develop and test a prototype Open RAN network at Edwards AFB. The system will include base stations, network components, user equipment, and specialized sensors. Testing will evaluate performance and ensure compatibility with aircraft systems, assessing coverage, bandwidth, latency, security, and operational impact. The system must integrate with Edwards AFB's infrastructure and achieve TRL 6, demonstrating a functional prototype in an operational setting.
The summary version adds that Phase II involves developing and refining the prototype based on Phase I insights, implementation of pilot deployments and rigorous testing to validate system performance and security, with deliverables including a full-scale prototype, detailed test results, and an integration plan for transitioning the technology to operational use at Edwards AFB.
Five assessment dimensions are named for Phase II: coverage, bandwidth, latency, security, and operational impact. Your Phase I design work should establish predicted values or targets against those five, because that is the framework your own Phase II will be measured on. Note also that specialized sensors appear in the Phase II system description, which connects back to the real-time aircraft health monitoring use case.
The topic also notes a targeted advancement to TRL 6 to 7 by the end of Phase II in one place and TRL 6 in another. Planning toward TRL 6, a functional prototype in an operational setting, satisfies both.
Phase III and the transition path
Phase III involves scaling the Open RAN cellular network at Edwards AFB to enhance flight line operations, targeting TRL 7. Military applications include real-time maintenance data and improved logistics coordination. Commercial use spans complex logistics in aerospace sectors. Transition efforts will engage the 412th Maintenance Group, Air Force Materiel Command, and commercial partners, supported by Air Force Sustainment Center and AFLCMC funding.
This is among the most concrete transition descriptions in the DAF Release 6 portfolio. You are given the using organization, the 412th MXG at Edwards, the major command, AFMC, and two named funding sources, the Air Force Sustainment Center and AFLCMC. Reference all of them in your future research and development discussion.
The topic also states that successful completion is expected to significantly advance the Department of Defense's technological state by providing a robust, future-proof communication solution tailored to the unique demands of flight line operations, and that this development aligns with modernization priorities such as Integrated Network System-of-Systems and Sustainment and Logistics, ultimately contributing to the operationally focused Advanced Battle Management System.
The ABMS connection is worth using carefully. It elevates a base infrastructure project into a recognized Air Force modernization line, and the topic makes the link itself so you are not stretching.
The cited references
Four references, all standards and industry documents rather than research papers, which reinforces that this is an integration topic.
3rd Generation Partnership Project, 3GPP, the mobile broadband standard.
Range Commanders Council IRIG 106, the 106 Telemetry Standards, via the Public RCC TRMC website.
O-RAN Alliance, O-RAN Use Cases and Deployment Scenarios.
Next Generation Mobile Networks Alliance, Open RAN White Paper.
The IRIG 106 citation is the one that distinguishes this topic from a generic private cellular opportunity. It is the telemetry standard family used at test ranges, and its presence signals that the flight line environment at Edwards carries range instrumentation conventions your network has to coexist with. A proposal that cites 3GPP and O-RAN but ignores IRIG 106 has read half the reference list.
Funding Allowance and Cost Structure
Award ceiling and realistic scoping
Up to $250,000 across up to 6 months. The topic index states that proposals in excess of this amount will not be considered for evaluation or award, and proposals in excess of this duration will not be considered for evaluation or award.
The instructions add that any per-award or per-topic funding caps are budgetary estimates only and more or less funding may become available. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals. Funding decisions are made with complete disregard to the other awards under the same topic.
Six months and $250,000 supports a serious requirements analysis, an architecture and deployment design, a security analysis, an integration plan, and a laboratory or small-scale proof-of-concept. It does not support standing up a network at Edwards, and the topic does not ask you to. Deployment at the base is Phase II.
Contract type
The DAF primarily makes SBIR Phase I and Phase II awards as firm-fixed-price contracts. Awardees are strongly urged to work toward a Defense Contract Audit Agency approved accounting system, since if the company intends to continue work with the Department of War an approved accounting system allows competition in a broader array of acquisition opportunities, including award of cost-reimbursement type contracts. For a commercial telecom company new to defense work, that is worth acting on early, because DCAA accounting system approval takes time.
If no exceptions are taken to an offeror's proposal, the Government may award a contract without negotiations. Therefore the offeror's initial proposal should contain the offeror's best terms from a cost or price and technical standpoint. If there are questions regarding the award document, contact the Phase I Contracting Officer identified on the cover page. The Government reserves the right to reopen negotiations later if the Contracting Officer determines doing so to be necessary.
Technical and Business Assistance
The DAF will provide up to $6,500 per Phase I award, in addition to the per-topic total identified in the DSIP Volume 3 Cost Proposal.
This BAA Phase I document carries the full detailed TABA request requirements. Awardees can only use TABA funding for the activities outlined in 15 U.S.C. 638(q)(1) and the purposes outlined in 15 U.S.C. 638(q)(1)(A) through (E). Eligible activities include access to a network of scientists and engineers engaged in a wide range of technologies, assistance with product sales, intellectual property protections, cybersecurity assistance, market research, market validation, development of regulations and manufacturing plans, and access to technical and business literature available through online databases. Those activities can be undertaken in furtherance of making better technical decisions concerning such projects, solving technical problems which arise during the conduct of such projects, minimizing technical risks associated with such projects, developing and commercializing new commercial products and processes resulting from such projects including intellectual property protections, and screening for potential foreign involvement in technology development or commercialization activities.
Cybersecurity assistance and development of regulations are the two most relevant here. Cybersecurity because a security analysis is a named Phase I deliverable and CMMC Level 2 self-assessment is the projected requirement. Development of regulations because spectrum coordination at a federal test range is a regulatory problem as much as a technical one.
Requests for TABA funding creditable to a TABA provider must include the following or will be subject to denial: the TABA providers; the providers' point of contact, email address, and phone number; an explanation of the provider's unique qualifications to provide the TABA service; the tasks that will be performed by the provider including the purpose and objective of the assistance, with the task milestone list tracking to the milestone payment schedule otherwise provided by the applicant; and total provider cost, number of hours, and labor rates, with average or blended rates acceptable.
If proposing TABA funding to hire new staff, augment staff, or direct staff to conduct or participate in training activities consistent with the purpose of TABA, the following must be included or may be subject to denial: names and positions, business need to be filled or training to be provided; number of employees to be hired, augmented, or directed to participate in training activities; qualifications of employees hired or augmented, or detailed need for training; tasks that will be performed including both a description of the activity and the purpose that it will serve; and total staff or training cost, number of hours, and labor rates.
A detailed request for TABA funding must be included in the Volume 5 Supporting Documents in DSIP. TABA requests that only specify a TABA request value in the Volume 3 Cost Proposal will not be considered.
Cost volume requirements
Cost information should be provided by completing the Cost Volume in DSIP and including the Cost Volume Itemized Listing. The cost volume detail must be adequate to enable Air Force personnel to determine the purpose, necessity, and reasonableness of each cost element. The DSIP Cost Volume and Itemized Cost Volume Information will not count against the specified page limit, and the itemized listing may also be submitted in Volume 5 under the "Other" dropdown option.
Direct cost materials. Justify costs for materials, parts, and supplies with an itemized list containing types, quantities, prices, and where appropriate purpose. Material costs may include raw materials, parts, subassemblies, components, and manufacturing supplies. On this topic, radio units, servers or edge compute for the RAN Intelligent Controller and core, test user equipment, and AR headsets belong here.
Other direct costs. This includes but is not limited to specialized services such as machining, milling, special testing or analysis, and costs incurred in temporarily using specialized equipment. Proposals including leased hardware must include an adequate lease versus purchase justification. Anechoic or shielded chamber time for interference characterization, spectrum analysis equipment rental, and commercial software or licensing may sit here, and the lease versus purchase rationale is likely to be relevant given how much cellular test equipment is normally rented.
Direct labor. Identify key personnel by name, if possible, or by labor category, if not. Direct labor hours, labor overhead or fringe benefits, and actual hourly rates for each individual are necessary for the Contracting Officer to determine whether these hours, fringe rates, and hourly rates are fair and reasonable. On a study and design Phase I, this is most of the budget. RF and network engineers, security engineers, and someone credible on flight line or maintenance operations should all be visible.
Travel. Travel costs must relate to project needs. Break out travel costs by trip, number of travelers, airfare, per diem, lodging, and similar. The number of trips required, as well as the destination and purpose of each, should be reflected. The instructions recommend budgeting at least one trip to the Air Force location managing the contract.
On this topic that recommendation is more than a formality. The entire proposition is a network at a specific base, and a requirements analysis of the Edwards flight line performed entirely from a distance is weaker than one informed by a site visit. Budget the travel and say what you will do there.
Subcontracts. Involvement of university or other consultants in the project's planning or research stages may be appropriate. If so, describe in detail and include information in the Cost Volume. The proposed total of consultant fees, facility lease or usage fees, and other subcontract or purchase agreements may not exceed one-third of the total contract price or cost, with profit excluded from the calculation, unless otherwise approved in writing by the Contracting Officer. The SBIR funded work percentage calculation considers both direct and indirect costs after removal of the small business concern's proposed profit. Support subcontract costs with copies of executed agreements that adequately describe the work to be performed, and at a minimum include a Statement of Work with a corresponding detailed Cost Volume for each planned subcontract.
Open RAN is by design a multi-vendor architecture, which creates a specific tension with this cap. One-third of $250,000 is roughly $83,000 for all consultant fees, facility lease and usage fees, and subcontract or purchase agreements combined. If your architecture requires radio units, a core, and a controller from three different vendors, the purchase agreements alone can approach that. Model it early, and consider whether Phase I needs procured hardware at all or whether a design plus a software-based or emulated proof-of-concept satisfies the deliverable.
Special tooling, special test equipment, and material. The inclusion of equipment and materials will be carefully reviewed relative to need and appropriateness to the work proposed. Special tooling and special test equipment purchases must, in the Contracting Officer's opinion, be advantageous to the Government and relate directly to the effort. These toolings or equipment should not be of a type that an offeror would otherwise possess in the normal course of business, and may include items such as innovative instrumentation or automatic test equipment.
Consultants. Provide a separate agreement letter for each consultant, briefly stating what service or assistance will be provided, the number of hours required, and the hourly rate. A consultant with flight line maintenance or range spectrum experience is a strong addition to this proposal, and this is how you document them.
Performance of work requirements
For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee. The DAF measures percentage of work by both direct and indirect costs, not including profit.
Occasionally the DAF will consider deviations from this performance of work requirement. Requests for Performance of Work deviations must be made twice: prior to submission during the topic open period, and as part of the initial proposal submission. For requests prior to the initial proposal submission, the DAF will consider the request and approve or disapprove requesting applicants to proceed with DSIP submission. Upon proposal receipt, the DAF will again consider such requests for approval for the resultant award.
All R/R&D work must be performed in the United States. Based on a rare and unique circumstance, the DAF may approve a particular portion of the R/R&D work to be performed or obtained in a country outside the United States. The awarding Funding Agreement officer must approve each specific condition in writing. Applicants seeking this approval must make the request with their initial proposal submission, and the DAF will not consider these requests prior to proposal submission.
This last point deserves attention on a telecom topic. Cellular network software development is frequently distributed internationally, and offshore engineering teams are common in the industry. All research and development work under this award must be performed in the United States absent specific written approval sought with the initial proposal.
Supply Chain, Which Is a Live Issue for Cellular Equipment
Nothing in this topic is more likely to disqualify an otherwise strong bidder than equipment sourcing. The foreign risk denial criteria name eight lists, and cellular network equipment intersects several of them directly. The Section 889 Prohibition List, the FCC List of Equipment and Services, the Entity List, and the Military End User List all include telecommunications equipment suppliers.
Radio units, baseband hardware, transport equipment, and even components inside otherwise domestic products are the exposure. Open RAN's multi-vendor premise increases the number of suppliers you have to clear rather than decreasing it. Audit your intended bill of materials against those lists before you propose, and be prepared to name your suppliers.
Note also that the projected CMMC level requirement for this topic is Level 2 with self-assessment, and that a security analysis is a named Phase I deliverable. A company proposing to build a secure network for a flight line should expect its own security posture to be relevant, and cybersecurity practices is the first item on the foreign risk assessment list.
Personnel Disclosure and Export Control
This topic does not carry a topic-level ITAR and EAR restriction paragraph, unlike NV034 in the same Phase I release. Your general obligations still apply.
The Volume 2 Key Personnel requirements apply to every topic in this release. Identify in the Technical Volume all key personnel who will be involved in this project, including information on directly related education, experience, and citizenship. A technical resume of the principal investigator, including a list of publications if any, must be included, and only one principal investigator or project manager can be designated to a proposal at any given time. Concise technical resumes for subcontractors and consultants are also useful.
Identify all U.S. permanent residents to be involved in the project as direct employees, subcontractors, or consultants. Identify all non-U.S. citizens expected to be involved in the project as direct employees, subcontractors, or consultants. For all non-U.S. citizens, in addition to technical resumes, provide countries of origin, the type of visa or work permit under which they are performing, and an explanation of their anticipated level of involvement on this project, as appropriate. Additional information may be requested during negotiations in order to verify the foreign citizen's eligibility to participate on a contract issued as a result of this announcement.
Do not upload information such as Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information requested, not the underlying identity documents.
If you are asserting export-controlled status for your own technology, a copy of the certified DD Form 2345, Militarily Critical Technical Data Agreement, or evidence of application submission is a Volume 5 document, and approval will be required if selected for award.
Proposal Structure: The Seven Volumes
Formatting, and what does not count against the page limit
The Technical Volume should include all graphics and attachments but should not include the Cover Sheet, which is completed separately as Volume 1. Ensure that all graphics are distinguishable in black and white, which matters here because network architecture diagrams and coverage maps often rely on color.
The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. This differs from the DAF Direct to Phase II instructions, which require 11-point.
The Phase I Technical Volume page and slide limits identified for the topics do not include the Cover Sheet, the Cost Volume, or the Cost Volume Itemized Listing. Only the Technical Volume and any enclosures or attachments count toward the page limit. The documents required for upload into Volume 5 under "Other" do not count toward the specified limits. In the interest of equity, pages or slides in excess of the stated limits will not be reviewed.
The limit for this topic is 20 pages or slides. A slide-format volume is acceptable and suits architecture diagrams, coverage analysis, and deployment layouts well.
Fraud, Waste and Abuse training must be completed prior to proposal submission, and DSIP will indicate completion of the Volume 6 requirement once the training is complete and certified. Note the criminal warning the instructions carry: knowingly and willfully making false, fictitious, or fraudulent statements or representations may be a felony under 18 U.S.C. Section 1001, punishable by a fine up to $250,000, up to five years in prison, or both.
Volume 1, Cover Sheet
Complete the proposal Cover Sheet in accordance with the instructions provided via DSIP. The technical abstract should include a brief description of the program objectives, a description of the effort, anticipated benefits and commercial applications of the proposed research, and a list of keywords and terms.
The technical abstract of each successful proposal will be submitted to the Office of the Secretary of War for publication and therefore must not contain proprietary or classified information. If selected for funding, the proposal's technical abstract and discussion of anticipated benefits will be publicly released. Be careful here about anything describing base infrastructure or vulnerabilities.
Volume 2, Technical Volume
The Phase I technical volume shall contain the required elements below. These instructions supplement the FY26 SBIR BAA, and in addition to the requirements found in the BAA, applicants are required to provide the following information in Volume 2.
Key personnel, as described above.
Phase I Statement of Work outline. The DAF uses the work plan outline as the initial draft of the Phase I Statement of Work. Therefore, do not include proprietary information in the work plan outline. To do so will necessitate a request for revision, if selected, and may delay award.
Include a work plan outline in the following format. Scope, listing the effort's major requirements and specifications. Task Outline, providing a brief outline of the work to be accomplished during the Phase I effort. Milestone Schedule. Deliverables. Progress reports. Final report with SF 298.
Your Deliverables entry should reflect the six items the topic names across its two Phase I descriptions: a comprehensive feasibility report, initial design schematics, a preliminary prototype proof-of-concept, a security analysis, use cases, and integration plans.
The SF 298 is the Report Documentation Page that accompanies a technical report. It is named in the required outline, so plan for it.
Volume 3, Cost Volume
Covered above.
Volume 4, Company Commercialization Report
Completion of the CCR as Volume 4 of the proposal submission in DSIP is required. Refer to the FY26 SBIR BAA for full details. Information contained in the CCR will not be considered by the Air Force during proposal evaluations.
Volume 5, Supporting Documents
The following documents may be required if applicable to your proposal. DD Form 2345, for proposals submitted under export-controlled topics. Verification of Eligibility of Small Business Joint Ventures, Attachment 3 to the FY26 SBIR BAA. Technical Data Rights Assertions, if asserting data rights restrictions.
For a commercial telecom company, Technical Data Rights Assertions matter because your existing software, orchestration, and network management intellectual property predates this award. This is the mechanism for keeping that boundary clear.
The detailed TABA request, if you are requesting TABA, also goes in Volume 5. Documents uploaded into Volume 5 under "Other" do not count toward the page limit, and the Cost Volume Itemized Listing may also be submitted there.
Volume 6, Fraud, Waste, and Abuse Training
Material can be found in the Volume 6 section of the proposal submission module in DSIP and must be thoroughly reviewed once per year to proceed with proposal submission.
Volume 7, Disclosures of Foreign Affiliations or Relationships to Foreign Countries
Small business concerns must complete the webform in Volume 7 of the DSIP proposal submission. The disclosures will not be accepted as a PDF Supporting Document in Volume 5, and previous versions of this form must not be uploaded to Volume 5. For additional details, refer to the DoW SBIR Program BAA.
How Your Proposal Will Be Evaluated
The criteria live in the BAA
Proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. The DAF is seeking varying technical and scientific approaches and varying and new technologies that would be responsive to the problem statements and areas of interest in the topic. Multiple procurements are planned and anticipated to be awarded as a result of the topic, each proposal is considered a separate procurement and will be evaluated on its own merit, and the Government may award all, some, or none of the proposals.
This BAA document does not reproduce the evaluation criteria, unlike the DAF Release 6 CSO Phase I instructions which restate Criteria A, B, and C. Read the criteria in the DoW FY26 SBIR BAA before writing, and do not assume the CSO criteria carry over.
Foreign risk evaluation
15 U.S.C. 638 and the Small Business Innovation and Economic Security Act of 2026 require the Department of War, in coordination with the Small Business Administration, to implement a due diligence program to assess security risks presented by small business concerns seeking a federally funded award.
The DAF will evaluate all small business concerns that submit proposals under this release on whether the concern presents a security risk for any reason. The measures include the due diligence process required under 15 U.S.C. 638(vv), disclosures required under 15 U.S.C. 638(g) and (o), and coordination with the intelligence community as defined in section 3 of the National Security Act of 1947 (50 U.S.C. 3003), federal law enforcement, and other counterintelligence capabilities of the United States Government.
The DAF will assess using a risk-based approach as appropriate: the cybersecurity practices; patent analysis; employee analysis; foreign ownership of a small business concern seeking an award, including the financial ties and obligations, which shall include surety, equity, and debt obligations, of the concern and employees of the concern to a foreign country, foreign person, or foreign entity; foreign affiliations of a covered individual, owner, or other key personnel of a concern with an entity in a foreign country of concern; investment relationships of a concern with an individual or entity in a foreign country of concern; technology licensing agreements or joint ventures, including joint venture like agreements, with an individual or entity in a foreign country of concern; and business relationships between a covered individual, owner, or other key personnel and an individual or entity in a foreign country of concern.
The DAF will also assess proposals utilizing open-source analysis and analytical tools for the nondisclosures of the information set forth in 15 U.S.C. 638(g)(13) or 638(o)(17), and examine any relationship of a concern seeking an award to any entity or individual included on the lists described in 15 U.S.C. 638(g)(16)(D) and 638(o)(20)(D).
If the DAF assesses that a concern has security risks, the DAF will review the proposal, the evaluation, and the security risks and may choose either to create a plan to mitigate the risks or to not select the proposal for award based upon a totality of the review.
Applicants will be required to disclose, under penalty of perjury, the representations, attestations, and certifications required under 15 U.S.C. 638(g)(13) and 638(o)(17), fulfilled by completing Volume 7. In addition, a written statement with any substantial changes to a foreign disclosure form must be provided to the awarding agency within 30 days of any changes while on a project for the DAF.
The DAF will not make an award if it determines the concern has an owner or covered individual that is party to a malign foreign talent recruitment program; has a business entity, parent company, or subsidiary located in the People's Republic of China or another foreign country of concern; has an owner or covered individual that has a foreign affiliation with a research institution located in the PRC or another foreign country of concern; or has a security risk connecting the concern to an entity, including any affiliates of the entity, or individual on any of the following: the UFLPA Entity List maintained by the Department of Homeland Security; the Non-SDN Chinese Military-Industrial Complex Companies List of the Office of Foreign Assets Control maintained by the Department of the Treasury; the Section 889 Prohibition List established under section 889 of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 and maintained by the Department of War; the list of Chinese Military Companies required under section 1260H of the William M. Thornberry National Defense Authorization Act for Fiscal Year 2021 and maintained by the Department of War; the Military End User List maintained by the Bureau of Industry and Security of the Department of Commerce; the Entity List maintained by the Bureau of Industry and Security; the List of Equipment and Services maintained by the Federal Communications Commission; or the Withhold Release Orders and Findings List maintained by U.S. Customs and Border Protection.
The DAF will also not make an award if it determines the concern has a security risk with a primary source that is classified or has a security risk the DAF determines warrants a denial.
If an award is denied on these grounds, the DAF will, as appropriate pursuant to its discretion and in a manner that does not compromise security, provide a notification advising the small business of the determination, the basis for the determination, and a statement that denial of award does not prohibit the concern from being eligible for an award in a subsequent award cycle. The same applies to denials under 15 U.S.C. 638(vv).
Of all the topics in this release, this is the one where the eight lists bite hardest, because telecommunications equipment is the explicit subject of several of them.
Venture capital, hedge fund, and private equity ownership
Small business concerns that are owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible to submit applications or receive awards for DAF topics.
Worth stating plainly because the DAF Release 6 BAA Direct to Phase II instructions say the opposite for that document's topic. Within the same BAA cycle, the Phase I instructions permit venture-backed firms and the Direct to Phase II instructions do not. The Phase I instructions govern this topic, so venture-backed private cellular companies are eligible here. Verify eligibility per document rather than assuming a cycle-wide rule.
Support contractors, status, feedback, and protests
Restrictive notices notwithstanding, proposals may be handled for administrative purposes only by support contractors, which may include but are not limited to TEC Solutions, Inc., APEX, Oasis Systems, Riverside Research, Peerless Technologies, HPC-COM, Mile Two, Montech, Wright Brothers Institute, and MacB (an Alion Company). In addition, only Government employees and technical personnel from the FFRDCs MITRE and Aerospace Corporations working under contract to provide technical support to AF Life Cycle Management Center and Space and Missiles Centers may evaluate proposals. All support contractors are bound by appropriate non-disclosure agreements. Contact the AF SBIR/STTR Contracting Officer with concerns regarding the use of support contractors.
The Principal Investigator and Corporate Official indicated on the Proposal Cover Sheet will be notified by email regarding proposal selection or non-selection. Small businesses will receive a notification for each proposal submitted, so read each notification carefully and note the Proposal Number and Topic Number referenced.
Automated feedback will be provided for Phase I proposals designated Not Selected. Additional feedback may be provided at the sole discretion of the DAF.
Proposals submitted to the DAF are received and evaluated by different organizations, handled by topic. Each organization operates within its own schedule for proposal evaluation and selection, so updates and notification timeframes will vary. If contacted regarding a proposal submission, it is not necessary to request information regarding additional submissions.
The Air Force anticipates that all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close. Refrain from contacting the BAA Contracting Officer for proposal status before that time.
Refer to the DoW SBIR Program BAA for procedures to protest the Announcement. As further prescribed in FAR 33.106(a) and FAR 52.233-2, protests should be submitted to Air Force SBIR/STTR Contracting Officer Daniel J. Brewer. The DAF uses its best efforts to resolve concerns raised by interested parties at the contracting officer level through open and frank discussions, and for agency protests the DAF provides for inexpensive, informal, procedurally simple, and expeditious resolution of protests.
All final reports will be submitted to the awarding DAF organization in accordance with contract instructions. Companies will not submit final reports directly to the Defense Technical Information Center.
How Phase II works
DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the conclusion of the period of performance. This decision will be based on the awardee's technical progress, as determined by a DAF Technical Point of Contact review using the Phase II review criteria.
Phase II is the demonstration of the technology found feasible in Phase I. Only Phase I awardees are eligible to submit a Phase II proposal. All Phase I awardees will be sent a notification with the Phase II proposal submittal date and detailed preparation instructions. If the physical or email addresses or firm points of contact have changed since submission of the Phase I proposal, correct information shall be sent to the DAF SBIR/STTR One Help Desk. Phase II dollar values, performance periods, and proposal content will be specified in the Phase II request for proposal. Only one Phase II proposal may be submitted for each Phase I award.
The DAF reserves the right to modify the Phase II submission requirements, and should the requirements change, all Phase I awardees will be notified. The DAF also reserves the right to change any administrative procedures that will improve management of the DAF SBIR/STTR Program at any time.
Because Phase II involves deploying at Edwards and the request can come during Phase I performance, building the relationship with the base during Phase I is directly instrumental rather than merely helpful.
Timeline and What to Do When
The dates
Topic opens: September 23, 2026
Proposal deadline: October 21, 2026, at the time specified in the DoW FY26 SBIR BAA, ordinarily 12:00 p.m. Eastern. Confirm on DSIP.
Selections finalized: within approximately 90 calendar days of close, on or about January 19, 2027
Period of performance: up to 6 months from award
A working backward plan
Before September 23. Read the evaluation criteria in the DoW FY26 SBIR BAA, since they are not in the component instructions. Read the four cited references, including IRIG 106, which is the one most likely to be unfamiliar to a commercial cellular team. Learn what you can about the Edwards flight line environment and the 412th Maintenance Group. Audit your intended equipment bill of materials against the eight denial lists, which on a telecom topic is the highest-risk diligence item. Identify a consultant with flight line maintenance or range spectrum experience if you do not have that inside. Work out your spectrum approach and the electromagnetic interference story. Model the one-third outside cost cap against any hardware procurement, and decide whether Phase I needs purchased equipment at all. Inventory background intellectual property for Technical Data Rights Assertions. Complete Volume 6 training and verify SAM and DSIP alignment. Send clarifying questions to the DAF SBIR/STTR One Help Desk, which encourages early inquiries.
September 23 through October 3. Draft the technical volume against the 20 page limit, organized around the six named Phase I deliverables. Give the network architecture, components, and deployment strategy real specificity, address interference with aircraft systems on its own terms, and write the security analysis as an actual analysis rather than a compliance statement. Set targets for the five Phase II assessment dimensions: coverage, bandwidth, latency, security, and operational impact. Write the work plan outline separately with no proprietary content, since it becomes the Statement of Work. Build the milestone schedule early since the TABA task list must track to it.
October 4 through October 12. Build the cost volume and itemized listing, neither of which counts against the page limit. Itemize radios, compute, test user equipment, and AR hardware if you are procuring any. Include the recommended trip to the Air Force location managing the contract with a stated purpose. Get separate agreement letters from each consultant and executed agreements with statements of work and detailed cost volumes for each planned subcontract, and check the one-third cap including purchase agreements. Write the detailed TABA request into Volume 5 if requesting TABA.
October 13 through October 16. Assemble Volume 5 with Technical Data Rights Assertions and any applicable DD Form 2345, complete the Volume 7 webform, finish the Volume 4 CCR, and run compliance: 20 page limit, 10-point minimum type, one-inch margins, graphics distinguishable in black and white, no PII uploaded to DSIP, no proprietary content in the technical abstract or the work plan outline.
October 17 through October 19. Submit and certify in DSIP.
October 20 through October 21. Buffer only.
Frequently Asked Questions
What is DAF SBIR topic DAF26BZ06-NV036?
DAF26BZ06-NV036 is a Department of the Air Force SBIR Phase I topic titled "Flightline Radio Network," released under the DAF 2026 SBIR Broad Agency Announcement, Release 6. It seeks innovative technologies leveraging cellular network infrastructure, particularly 5G Open Radio Access Network architectures, to establish a secure, adaptable, and interoperable network on the flight line at Edwards Air Force Base supporting aircraft maintenance, logistics, and operational efficiency.
How much funding is available under DAF26BZ06-NV036?
Up to $250,000 for a period of performance up to 6 months. Proposals in excess of that amount or duration will not be considered for evaluation or award. Up to $6,500 in Technical and Business Assistance is available per Phase I award, in addition to the per-topic total.
When is the proposal deadline?
The topic closes October 21, 2026. The DAF instructions direct offerors to the DoW FY26 SBIR BAA for the exact submission time, ordinarily 12:00 p.m. Eastern on the close date. Confirm on the live DSIP posting.
When does this topic open?
September 23, 2026, giving a 29 day submission window.
Is this topic tied to a specific base?
Yes. The flight line at Edwards Air Force Base is named throughout, the network must integrate with Edwards AFB's existing infrastructure, Phase II deploys and tests there, and Phase III scales there. The 412th Maintenance Group at Edwards is named as a transition partner. Site understanding is a differentiator, not a detail.
What are the use cases?
Ground crew coordination, real-time aircraft health monitoring, predictive maintenance to reduce aircraft downtime and enhance mission readiness, and augmented reality applications providing maintenance personnel with real-time guidance, schematics, and remote support. The broader aim is improved real-time communication, data sharing, and operational efficiency.
Why Open RAN specifically?
The topic states that a 5G Open RAN architecture offers increased flexibility, interoperability, and security while minimizing vendor lock-in and lowering costs, and that its modular design will accommodate evolving test requirements and future upgrades. Vendor lock-in avoidance and cost reduction are stated procurement goals, so a single-vendor proprietary stack is answering a different question.
What does Phase I deliver?
Across the topic's two Phase I descriptions, six items are named: a comprehensive feasibility report, initial design schematics, a preliminary prototype proof-of-concept, a security analysis, use cases, and integration plans. Phase I will also outline network architecture, components, and deployment strategy, and address potential interference with aircraft systems.
What technology readiness level applies?
The topic states the anticipated TRL at project start is TRL 4, and that Phase I success includes achieving TRL 3 to 4. Those do not quite reconcile, and the sensible reading is that commercial Open RAN technology sits at TRL 4 or above while the specific flight line application at Edwards is what must be matured to TRL 3 to 4. Frame maturity claims around the application rather than the underlying technology.
Do I need to address interference with aircraft systems?
Yes, explicitly. Phase I is required to address potential interference with aircraft systems, and Phase II testing must ensure compatibility with aircraft systems. Radiating RF near aircraft in a flight test environment raises electromagnetic interference and environmental effects questions, and a proposal that treats this as a footnote will not persuade a test community reviewer.
What about spectrum?
The topic states the network will employ efficient frequency allocation through spectrum sharing mechanisms. Spectrum at a Department of Defense test range involves federal allocations, range operations, and coordination that has no direct commercial analogue, so treat it as a substantive design problem rather than an assumption.
What happens in Phase II?
Develop and test a prototype Open RAN network at Edwards AFB, including base stations, network components, user equipment, and specialized sensors. Testing evaluates performance and ensures compatibility with aircraft systems, assessing coverage, bandwidth, latency, security, and operational impact. The system must integrate with Edwards AFB's infrastructure and achieve TRL 6, demonstrating a functional prototype in an operational setting. Deliverables include a full-scale prototype, detailed test results, and an integration plan for transitioning to operational use.
What happens in Phase III?
Scaling the Open RAN cellular network at Edwards AFB, targeting TRL 7. Military applications include real-time maintenance data and improved logistics coordination, and commercial use spans complex logistics in aerospace sectors. Transition efforts will engage the 412th Maintenance Group, Air Force Materiel Command, and commercial partners, supported by Air Force Sustainment Center and AFLCMC funding.
How does this connect to larger Air Force programs?
The topic states the development aligns with modernization priorities such as Integrated Network System-of-Systems and Sustainment and Logistics, ultimately contributing to the operationally focused Advanced Battle Management System. Because the topic makes that link itself, you can reference ABMS without overreaching.
What references should I read?
Four are cited: 3GPP, the mobile broadband standard; Range Commanders Council IRIG 106 telemetry standards; the O-RAN Alliance's O-RAN Use Cases and Deployment Scenarios; and the NGMN Alliance Open RAN White Paper. IRIG 106 is the one that distinguishes this from a generic private cellular opportunity, since it governs range telemetry conventions your network must coexist with.
How long can my technical volume be?
20 pages or slides. The Technical Volume must be no smaller than 10-point on standard 8.5 by 11 inch paper with one-inch margins. The Cover Sheet, Cost Volume, and Cost Volume Itemized Listing do not count toward the limit; only the Technical Volume and any enclosures or attachments do. Documents uploaded into Volume 5 under "Other" do not count either. Pages or slides in excess of the stated limit will not be reviewed.
What is my biggest disqualification risk?
Equipment supply chain. The foreign risk denial criteria name eight lists, including the Section 889 Prohibition List, the FCC List of Equipment and Services, the Entity List, and the Military End User List, all of which reach telecommunications equipment. Open RAN's multi-vendor premise increases the number of suppliers you must clear. Audit your bill of materials before you propose.
How much of the work must my company perform?
For Phase I, a minimum of two-thirds of the research or analytical effort must be performed by the awardee, measured by direct and indirect costs excluding profit. Separately, all consultant fees, facility lease or usage fees, and other subcontract or purchase agreements together may not exceed one-third of the total contract price or cost with profit excluded, unless the Contracting Officer approves otherwise in writing. On a $250,000 award that is roughly $83,000 for all outside costs combined.
Does the one-third cap include equipment purchases?
The cap as written covers consultant fees, facility lease or usage fees, and other subcontract or purchase agreements. Because Open RAN is multi-vendor by design, purchased radios, core software, and controllers can approach that figure quickly. Consider whether Phase I requires procured hardware at all, or whether a design plus a software-based or emulated proof-of-concept satisfies the deliverable.
Can my offshore engineering team work on this?
Not without specific approval. All research and development work must be performed in the United States. The DAF may approve a particular portion performed or obtained outside the United States only based on a rare and unique circumstance, with written approval from the awarding Funding Agreement officer, and the request must accompany the initial proposal submission. This is a real constraint in an industry where distributed development is common.
Is this topic export controlled?
This topic does not carry a topic-level ITAR and EAR restriction paragraph, unlike NV034 in the same release. General disclosure obligations still apply, including identifying all U.S. permanent residents and all non-U.S. citizens involved with countries of origin, visa or work permit type, and anticipated level of involvement.
What identity information should I not upload?
Do not upload Permanent Resident Cards, birth certificates, Social Security Numbers, or other personally identifiable information to the DSIP system. Provide the categories of information requested, not the underlying documents.
How will my proposal be evaluated?
The BAA component instructions do not restate the evaluation criteria. They say only that proposals will be evaluated for overall merit in accordance with the criteria discussed in the FY26 SBIR BAA. Read those criteria before writing, and do not assume the Criteria A, B, and C structure from the DAF CSO instructions carries over.
Are venture capital backed companies eligible?
Yes, for this topic. The BAA Phase I instructions state that firms owned in majority part by multiple venture capital operating companies, hedge funds, or private equity funds are eligible for DAF topics. The DAF Release 6 BAA Direct to Phase II instructions state the opposite for that document's topic, so verify per document.
Does the Company Commercialization Report affect my score?
No. Completing the CCR as Volume 4 in DSIP is required, but the instructions state information contained in the CCR will not be considered by the Air Force during proposal evaluations.
Why does the work plan outline matter so much?
Because the DAF uses it as the initial draft of the Phase I Statement of Work. The instructions direct you not to include proprietary information in it, warning that doing so will necessitate a request for revision if selected and may delay award.
What is TABA and how do I request it?
Up to $6,500 per Phase I award, in addition to the per-topic total, identified in the Volume 3 Cost Proposal. This BAA document carries the full detailed request requirements: provider name, point of contact with email and phone, an explanation of unique qualifications, the tasks with purpose and objective, and total cost with hours and labor rates, with the task milestone list tracking to your milestone payment schedule. The detailed request must be in Volume 5, and requests specifying only a value in Volume 3 will not be considered. Cybersecurity assistance and development of regulations are the most relevant eligible activities here.
Should I budget travel to Edwards?
The instructions recommend budgeting at least one trip to the Air Force location managing the contract, and on this topic that is substantive rather than administrative. A requirements analysis of a specific flight line performed entirely remotely is weaker than one informed by a site visit. Budget it and say what you will do there.
How do I get to Phase II?
DAF organizations may request Phase II proposals while Phase I technical performance is ongoing or at any time after the period of performance concludes, based on the awardee's technical progress as determined by a DAF Technical Point of Contact review. Only Phase I awardees are eligible, and only one Phase II proposal may be submitted for each Phase I award.
When will I hear about selection?
The Air Force anticipates all proposals will be evaluated and selections finalized within approximately 90 calendar days of solicitation close, meaning on or about January 19, 2027. The Principal Investigator and Corporate Official on the cover sheet are notified by email.
Who do I contact with questions?
The AF SBIR/STTR One Help Desk at usaf.team@afsbirsttr.us for general program and proposal preparation questions, and the DAF encourages requesting clarifying information as early as possible because delays constrain its ability to respond. For DSIP submission system issues, dodsbirsupport@reisystems.com. For technical questions about the topics during the pre-announcement and open period, reference the DoW FY26 SBIR BAA. The Air Force SBIR/STTR Contracting Officer is Mr. Daniel J. Brewer at Daniel.Brewer.13@us.af.mil. Address or point of contact changes after submission go to the One Help Desk with the subject line "FY26 SBIR BAA Address Change."
Positioning Advice for Companies Considering This Topic
Win on site knowledge, not on cellular expertise. Many companies can build a private 5G network. Far fewer understand a flight line at a test wing, where instrumentation, telemetry, rapidly changing aircraft configurations, and range spectrum coordination all intersect. Demonstrating that you understand Edwards specifically is the strongest differentiator available on this topic.
Get someone with flight line credibility on the team. A consultant with maintenance operations or range spectrum experience changes how the proposal reads to a reviewer from the test community, and the cost volume has a documented path for consultants. This is a high-return, low-cost addition.
Treat interference with aircraft systems as a first-class technical section. It is a named Phase I requirement and a named Phase II test criterion. Address emissions, coexistence with aircraft avionics and instrumentation, and your test approach. This is where a commercial telecom proposal most often loses a defense flight test audience.
Read and cite IRIG 106. It is the reference in the list least likely to be familiar and the one that signals whether you understand the environment. Range telemetry conventions are part of your interoperability problem.
Write the security analysis as analysis. It is a named deliverable, CMMC Level 2 self-assessment is the projected requirement, and cybersecurity practices leads the foreign risk assessment list. A threat model for a base flight line network, covering the RAN, the core, the user equipment, and the AR endpoints, is worth real pages.
Audit your bill of materials before anything else. On a cellular topic, the eight denial lists are the most likely cause of a mandatory denial. Section 889, the FCC covered list, the Entity List, and the Military End User List all touch telecom equipment. Know your suppliers and their component sources.
Solve the one-third cap problem structurally. Open RAN means multiple vendors, and purchase agreements count against the same cap as subcontracts. Decide early whether your Phase I proof-of-concept can be software-based or emulated, since that keeps procurement out of a tight cost envelope and leaves room for the analysis the topic actually asks for.
Set targets against the five Phase II dimensions now. Coverage, bandwidth, latency, security, and operational impact are the Phase II assessment criteria. Establishing predicted values in Phase I gives the government a measurement framework and gives you a defensible basis for the Phase II request.
Make the downtime argument quantitative. Predictive maintenance reducing aircraft downtime is the value proposition. Even a rough model of sortie availability or maintenance cycle time improvement is more persuasive than a description of the technology.
Use the named transition path in full. The 412th Maintenance Group, Air Force Materiel Command, the Air Force Sustainment Center, AFLCMC, and ABMS are all named in the topic. Very few SBIR topics hand you the using organization, the command, the funding sources, and the program alignment. Put all of them in your future research and development section.
Build the commercial case on aerospace logistics. The topic names complex logistics in aerospace sectors as the commercial application. Commercial MRO facilities, airport ramp operations, and manufacturing plants have the same problem structure, which makes the dual-use argument straightforward rather than strained.
