Integration, and more specifically the changes that require a block upgrade, are what UAI covers.
The only thing that has to happen after a weapon has a UAI interface is to perform the separation tests. Any changes that are needed will be performed to the launching AC or the weapon itself, not the UAI interface. There is nothing that can be changed, as part of UAI, that would affect how the weapon separates anyways.
Here is an example of how it will work.
1. A weapon gets developed with a UAI interface.
2. Simulation work confirms that the weapon should separate with no problems.
3. The appropriate service sends it to it’s OT&E squadron.
4. The AC gets the weapon’s UAI specs uploaded and the weapon attached.
5. The OT&E AC performs separation tests to confirm the simulation data.
6. If no problems are found, the weapon (and it’s UAI data) are cleared for worldwide usage across the entire fleet and can be used within hours anywhere it is needed, no block upgrade needed.
If you cannot see how this is a “game-changer” in the area of weapon integration then I do not know what you are not understanding.
As far as aerodynamic data and how it affects the AC, that is part of the UAI spec. Think of it this way, the AC will know all the pertinent weapon data (size, weight, CG, drag, etc) and will do it’s own calculation as to how it will affect range, lift, drag, etc.
btw, yes UAI is cleared for export and NATO is thinking of developing it’s own NUAI interface.
Once again, your missing the point.
What they are doing is similar to what happens when computers went from DOS to Windows.
In DOS, each word processor had to support each printer internally. I other words, each printer had to be integrated into each program that wanted to use it. As new printers came out, they had to wait till the programs could be updated in order to work.
When Windows came out, they introduced a middleman called Print Manager. Now, each program that wanted to use a printer would interface with the Print Manager using a common set of protocols. Each printer mfg was responsible to provide drivers for their printers that would facilitate these protocols.
These mfgs did not need to know the inner working of Windows, just the needed protocols. This is the same thing with UAI. Each weapon mfg will create a set of protocols for their weapon that will communicate, in a uniform format, with the F-35’s (or any aircraft that has UAI) UAI interface and allow that plane to use that weapon without a block upgrade. This is why, if you had actually read it, the article says that a plane can use a new weapon with a “one day integration” instead of the several year process that is traditional.
Try doing some research after you take your keyboard of your mouth.
If you were speaking of the traditional way of integrating weapons, then yes you need not only hard data (on the F-35), but you also need to be able to upgrade the block software of the F-35.
UAI changes all this. In short:
Stores-Aircraft Interface: This project conducts stores-aircraft interface upgrades and standards development to include the Universal Armament Interface (UAI). UAI is an Air Force initiative to develop standardized software interfaces in aircraft, weapons and mission planning to support integration of future weapons independent of aircraft Operation Flight Program (OFP) cycles.
http://www.dtic.mil/descriptivesum/Y2011/AirForce/0604602F_PB_2011.pdf
Here is a great article that covers, in detail, what the UAI is.
http://www.mputtre.com/id11.html
Here is a small nuget on it’s future plans:
the UAI standard currently only addresses 1760-class precision-guided munitions, in the future, his program office will look at expanding it to include air-to-air missiles, training pods, sensors, and other pods and stores.
The answer is yes, because it does not work that way for all to see. 😉
Your showing your ignorance here again. Weapon integration DOES NOT require the “codes” or a Block upgrade thanks to UAI.
Even without UAI, they could be integrated during a block upgrade or be programed to emulate an existing weapon.
who says that the SA will receive the DEWS?
Near the bottom of the list:
169 Digital Electronic Warfare Systems (DEWS)
You missed it
158 AN/AAQ-33 Sniper Targeting Systems
(F-35B) will carry much less payload -half in stealth mode-
If you are speaking of just the size of the JDAM, then yes the F-35B is limited to a 1000lb JDAM while the A/C can carry a 2000lb JDAM.
If you are carrying SDBs or additional AAMs, the internal carriage is the same (4 SDBs or 2/3 internal AAMs).
I wonder if they will need source code to integrate all of this?
Short answer, NO
The F-35 has an interface called UAI (Universal Armament Interface) which allows new weapons to be installed “on the fly”, pardon the pun.
In computer vernacular all they would need is the dev software to write the “drivers” for the weapon.
Well, that is 8 airframes (AF-1,2,3 & BF-1,2,3,4 & CF-1 not counting any new ones) which works out to one flight per plane every 5.8 days. Very doable.
A New CAPE Cost Estimate for the F-35: Thanks to a new cost-estimating model, the Pentagon’s Cost Assessment and Program Evaluation office’s numbers on the F-35 strike fighter are “a lot closer” to Lockheed Martin’s own internal estimates than ever before, says Dan Crowley, chief operating officer of the company’s aeronautics unit. Crowley told the Daily Report that the CAPE developed a new cost model to use in the recently concluded negotiations for the F-35 Lot 4 production contract that took into account items that the company has been asking them to consider for years. Among them were the multinational complexity the program, “should cost” agreements with vendors, and the economies of scale, said Crowley. And surprise: the CAPE’s numbers are now more in line with Lockheed’s. While there’s still some daylight between the two estimates on both the Marine Corps F-35B and Navy F-35C versions, the CAPE numbers for the Air Force’s F-35A variant “met” Lockheed’s own, said Crowley. “Too bad this had to come after the Nunn-McCurdy” breach earlier this year, Crowley said. The CAPE previously based its estimates on the assumption that the F-35 program would play out just like all previous fighter projects. Crowley thinks the government and Lockheed both seem satisfied with the Lot 4 numbers, which should be made public soon.—John A. Tirpak
I am so tempted to say ‘I told you so’ to so many people re: the NM breech being a false one based on overinflated CAPE numbers.
Those numbers are also supported by the JPO. Btw, my point was that the F-35B is not any more expensive than the F-35C.
If they did not do that the critics would complain every year as the average price goes up (because of it being a Then Year dollar price that includes inflation).
Nobody who knows what they are talking about expects the F-35C to be significantly cheaper than the F-35B.
From the latest F-35 Fast Facts
Average Unit Recurring Flyaway Cost (in FY 2002 dollars – the most recent comprehensive estimate)
— F-35A upper-$40 million
— F-35B mid-$60 million
— F-35C mid-$60 million
One small benefit of waiting till 2018 is that they will likely be Blk5 instead of Blk4 as in 2016.