PBAS Industry Day Announcement Questionnaire.pdf

20-21 January 2026 PBAS Industry Days Questionnaire

1. Company Background Company Name Company Address Company Point of Contact (POC)- (no nicknames), phone number, and e-mail address.

Company Cage Code- (if applicable), business unit, and address. (This will be used to validate CUI access and participation eligibility) Full names of all attendees- Include memo from the FSO stating they are US citizens.

Does your company have authorization to serve as a DoD contractor (Y/N) Short description of services Business Type (Large, Small, other classifications of status) Does your business qualify as a Non-Traditional Defense Contractor?

Do you intend to be a Prime Contractor or subcontractor? Please see definition in the announcement.

If you meet the definition of “Prime Contractor” and plan to respond to future solicitations as a Prime Contractor, are you requesting a 1:1 meeting with USG representatives on 21 January 2026?

Do you have any International Traffic in Arms Regulations (ITAR) or other similar restrictions?

There is an OPSEC requirement to assure all company attendees meet access requirements IAW 32 CFR 117, NISPOM and DoDM 5200.48, Controlled Unclassified Information (CUI). CUI information is not releasable to the public, therefore please coordinate with your Security Managers and:

i. Company responses should include a statement as shown: “attendees do meet the access requirements IAW 32 CFR 117, NISPOM and DoDM 5200.48, Controlled Unclassified Information (CUI).”

2. System Specific Information Name of the System System Description including picture showing major components.

What is the weight (grams) of your <5” and <10” air vehicle (AV) platforms?

Which specific components are NDAA-compliant?

Which specific components are not NDAA-compliant and when do you anticipate full

NDAA-compliance?

Is the system MOSA-compliant? If so, what components?

Is the system listed on the DIU Blue list? If not, when do you anticipate this?

3. System Performance

What is the munition/fuze type and manufacturer used in the system?

Is the munition/fuze delivery system CLIK compatible? IE: Does the munition/fuze type mount to a Picatinny rail? Are there power and/or data connections to the munition/fuze payload?

What other delivery systems are compatible with the AV, that have not been mentioned, if any?

Is the munition/fuze certified by the Army Fuze Safety Release Board (AFSRB), or any other Army Safety Board?

What size payload, in pounds, does your <5” and <10” AV platforms support? How long does it take to fully attach/mount the payload?

What is the make and model of electrical motors?

What type of batteries are used?

What energy density rating do the batteries have (W*hr/Kg) Are there arming and safety mechanisms on the AV?

Does the AV have a data and charging port?

What is the system's endurance (in minutes) under favorable conditions?

What is the system's range under favorable conditions (<10mph head wind)?

What is the system's max loitering time?

What is the cruise and dash speed of the AV?

What is the system's setup time?

What radio frequencies does the system use?

Is the radio unit modular and swappable?

What is its max range?

Does the Command and Control (C2) data link, and/or video data link, use encryption?

Can the AV perform handoff, abort, arm/disarm (to include status), retarget, and waypoints functionality?

Can the system sustain lock to the target in the terminal phase of engagement?

Is the flight control on the Flight Control System (FCS) semi-autonomous with continuous flight when loss of communication is experienced?

What type of navigation does the AV utilize? (Global Positioning System (GPS), Inertial Navigation Systems (INS), Visual navigation, or other) Is the GPS SAASM or M-Code capable?

Has any environmental performance testing been conducted on the system? If so, please list all the government monitored/conducted environmental testing.

What are the specific maintenance requirements for your product?

What is the Technology Readiness Level of the system?

What is current reliability of the system? What is the reliability of the air vehicle?

What is the reliability of the FCS?

What is the Gimbal and payload performance characteristics (angle of look, pan, tilt, zoom, image quality (in pixels for EO/IR), ability to pixel lock from what range in

EO/IR?

What type of EO/IR Sensor is mounted/integrated into the AV?

What onboard capabilities are in the AV to ensure survivability of flight, given an EW cluttered and contested operating environment (SAASM, M-CODE, VBN, etc.)?

Has the system tested under realistic EW threat conditions? If yes, what was the event or location?

Can the AV interface with Android Team Awareness Kit (ATAK)? If so, what capabilities are currently offered through ATAK?

What autonomous capabilities does your system have?

4. Pricing and Production What is the estimated AV (<5” & <10” rotor platforms) Unit Price? (prime vendors only) What is the estimated price for one (1) PBAS system? (prime vendors only) What is your current production lead time of the system? What is the current production lead time of 100 systems?

What is your current monthly production rate? What is your maximum production rate with your current production facilities and resources?

5. System Architecture and Common Controller Integration

The system architecture effort will iteratively enable command and control of small Uncrewed Aircraft Systems (sUAS) in support of Brigade Combat Teams (BCT) across the Army Command and Control infrastructure. Beginning with integration in PEO Soldier managed products or programs and progressing to integration in the Integrated Tactical Network and other manned or unattended systems.

The system architecture will use MOSA-compliant command and control networks, radios, software, architecture and products to create a software back-bone that can manage and integrate AVs. The initial effort will focus on integration with existing systems or hardware to greatly reduce sensor to shooter timeline and putting lethality into the hands of the IBCT to engage targets out to 10km from the Forward Line of Own Troops (FLOT), with numerous mission scenarios. The integration will enable an iterative approach to conduct P3Is to increase capability over time. These would include, but are not limited to: aided target recognition algorithms, autonomy, vision-based navigation, improved munitions, electronic warfare threat mitigation, Assured Position, Navigation, and Timing (A-PNT) enhancements, target tracking, etc.

For the common controller, the initial effort is envisioned as a TAK-based plug-in. The application would reside on NettWarrior-based devices to view, track, task, pass targets and call multiple AVs. This approach leverages hardware that soldiers already carry to reduce the weight burden. It is possible a variety of AVs will be procured from multiple vendors. Future integration efforts will span different ground and aerial-based products managed across many Army Acquisition groups. The common control effort will rapidly advance to controlling multiple variants of AVs and to understand, develop, produce and deliver an interface-controlled design of a common controller application. Upon effective integration with other products/programs (e.g. NettWarrior, IVAS, APP controlling proprietary AVs via a TAK-based plug-in, tactical radios, etc.) and with Government approval, the vendor will formally deliver the software application.

PBAS will leverage MOSA-compliant interfaces between key system components and will be interoperable with ITN, NettWarrior, and common controller framework and will incorporate features that enable autonomy, multiple effects on targets, and rapid technology insertion. Given this background:

Describe your prior implementations of Modular Open System Approach (MOSA) and Future Airborne Capability Environment (FACE) conformant architectures.

Some potential MOSA modules for PBAS can be warhead, gimbal, batteries, radios, common control, flight control etc. Describe potential modularity to PBAS architecture and your expertise in one or more of these modules. Describe your experience developing the interface control documents between similar modules.

Describe your experience integrating and executing complex software efforts for military programs along with any applications of FACE.

Describe your experience leveraging MOSA/FACE to provide capability refresh within short timelines.