The U.S. Air Force Looks To Advanced Manufacturing To Keep Existing Aircraft Flying And Develop Next-Gen Capabilities

What if there were Olympic events that weren’t physical, but were focused instead on completely geeking out on super-cool breakthrough technologies for real-world aerospace and defense challenges? Even better, what if they offered prize money totaling nearly a million dollars?

Now there are just such events, thanks to the U.S. Air Force’s Rapid Sustainment Office (RSO). In fact, participants in five such Olympic “sports” (or Technical Challenges, as the RSO calls them) have already been competing over the past few months. Those competitions will culminate when the winners are announced during next week’s four-day Advanced Manufacturing Olympics. This virtual conference runs from October 20-23, and features technology demonstrations, expert speakers from both industry and the military, virtual networking opportunities, and the awarding of prized for those Technical Challenges mentioned above.

“RSO is working to revolutionize sustainment, while building an agile supply chain for the future,” said Nathan Parker, Deputy Program Executive Officer at the RSO. “Originally, we were planning to hold this inaugural event outside Salt Lake City, Utah. But then Covid hit, so we’ve taken the whole thing virtual.”

Event speakers will include military officials such as Barbara M. Barrett, Secretary of the Air Force; General Charles Q. Brown, Jr., Chief of Staff of the Air Force; and General John W. Raymond, Chief of Space Operations of the U.S. Space Force. Other speakers featured are Sebastian Thrun, founder of Google X; Dr. Mae Jemison, NASA astronaut; and Brad Kesolowski, NASCAR Cup Series driver and founder of Kesolowski Advanced Manufacturing.

The five Technical Challenges began with an

SOLVED: if I can force the sensor in the computer to act as if its not full – Samsung Refrigerator

Pablo Lopez. When you reset the ice maker your bypassing the thermostat that tells the ice maker to dump the ice and refill. If the problem is in the optic sensor the ice maker wouldn’t fill.

In my 35 year career, I’ve never had an issue whit an optic sensor. That doesn’t mean they don’t fail, it’s just not very common.

////////////////// FACEBOOK PROVIDED TRACKING CODE //////////////////////

!function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(window,document,'script', 'https://connect.facebook.net/en_US/fbevents.js');

const pixelid = '216235165439303';

// This disables the SubscribedButtonClick and Microdata events from // automatically firing. When this feature was enabled we were recieving // too many duplicate reports because our page framework was not // optimized for auto-subscribing to click events. // // https://developers.facebook.com/docs/facebook-pixel/advanced#automatic-configuration fbq('set', 'autoConfig', 'false', pixelid);

// Instruct Facebook to opt California users out of data processing that // doesn't comply with the California Consumer Privacy Act (CCPA). The 0 // arguments for user country and state tell Facebook to determine the // country and state themselves using geolocation. // // https://developers.facebook.com/docs/marketing-apis/data-processing-options fbq('dataProcessingOptions', ['LDU'], 0, 0);

fbq('init', pixelid);

fbq('track', 'PageView');

////////// Custom functions for tracking click-based events //////////////

// These functions use Mootool's $$(), so we can't run them // till the document has loaded document.addEventListener('DOMContentLoaded', function() { var trackButtons = document.getElementsByClassName('js-check-out-fb-track-button'); var fbInitiateCheckout = fbq.bind(null, 'track', 'InitiateCheckout'); for (var i=0; i < trackButtons.length; i++) { trackButtons[i].addEventListener('click', function() {fbInitiateCheckout();}); } });

Source Article

US Air Force sends software updates to one of its oldest aircraft midair

WASHINGTON — For the first time, the U.S. Air Force updated the software code on one of its aircraft while it was in flight, the service announced Oct. 7.

And there’s a surprise twist: The aircraft involved wasn’t the “flying computer” F-35, the mysterious B-21 bomber still under development, or any of the Air Force’s newest and most high-tech jets. Instead, the service tested the technology aboard the U-2 spy plane, one of the oldest and most iconic aircraft in the Air Force’s inventory.

On Sept. 22, the U-2 Federal Laboratory successfully updated the software of a U-2 from the 9th Reconnaissance Wing, which was engaged in a training flight near Beale Air Force Base, California, the Air Force said in a news release.

To push the software code from the developer on the ground to the U-2 in flight, the Air Force used Kubernetes, a containerized system that allows users to automate the deployment and management of software applications. The technology was originally created by Google and is currently maintained by the Cloud Native Computing Foundation.

For the demonstration, the U-2 lab employed Kubernetes to “run advanced machine-learning algorithms” to the four flight-certified computers onboard the U-2, modifying the software without negatively affecting the aircraft’s flight or mission systems, the service said.

“The successful combination of the U-2′s legacy computer system with the modern Kubernetes software was a critical milestone for the development of software containerization on existing Air Force weapon systems,” said Nicolas Chaillan, the Air Force’s chief software officer.

During a Sept. 15 interview with C4ISRNET, Chaillan hinted that the service would soon be able to update the software of flying aircraft, calling the capability a “gamechanger” and describing the challenges involved with ensuring the aircraft could be updated without posing a safety risk.

“We need to

Bank rules force staff to turn off NHS COVID-19 tracing app at work

By Iain Withers and Sinead Cruise

LONDON (Reuters) – Branch staff at some of Britain’s biggest banks say rules that require them to store phones in lockers while at work are putting them at undue risk of COVID-19 from colleagues and customers, as they cannot use the country’s tracing app.

Lloyds Banking Group <LLOY.L>, along with rival TSB, are among those advising employees to deactivate the NHS Track & Trace app during office hours, when they are not allowed to keep phones on their person.

Some banks ask staff and cashiers to store phones away to prevent leaks of sensitive customer data, although this is not formally required by regulator the Financial Conduct Authority.

Under current government guidelines, users of the NHS app are advised to disable bluetooth or pause the app when away from their phones to avoid false notifications.

Other companies have told staff to pause the app at work, including pharmaceuticals firm GSK <GSK.L>, which said its other safety measures were sufficient, the Guardian newspaper reported.

The BTU union, which represents staff working for Lloyds but is not recognised by the bank, said it had been contacted by dozens of staff unable to use the app, which has been downloaded by more than 14 million people.

One unnamed Lloyds employee who contacted the BTU said: “I live and work in a high-risk area so I am very concerned at being told that while I’m at work I have to suspend the NHS test and trace app… This defeats the object of track and trace.” 

Another said they were at risk as they had to conduct face-to-face meetings and due to the “blatant transgression of the social distancing rules by many customers”.

“Customers and staff have a right to know if they have come into contact with someone

Case closed: California judge ends SpaceX’s lawsuit against the U.S. Air Force

The judge said the Air Force’s actions were not arbitrary, capricious, or in violation of the law, and that SpaceX was not entitled to any relief in this action.”

WASHINGTON — A California judge Oct. 2 officially ended SpaceX’s 18-month-long lawsuit against the U.S. Air Force. Following a Sept. 24 ruling denying SpaceX’s claim, the judge on Friday ordered the case to be closed. 

U.S. District Court Judge Judge Otis Wright II of the Central District of California on Sept. 24 ruled against SpaceX in its legal complaint over contracts the U.S. Air Force awarded in October 2018 to United Launch Alliance, Northrop Grumman and Blue Origin. 

The judge’s Sept. 24 order, first reported by Reuters, was sealed by the court because it contained sensitive information.

In the Oct. 2 motion to close the case, the judge noted that his Sept. 24 order denied SpaceX’s claim, “concluding that the Air Force’s actions were not arbitrary, capricious, or in violation of the law, and that SpaceX was not entitled to any relief in this action.”

SpaceX first filed the complaint May 17, 2019, with the Court of Federal Claims. The company argued that the Air Force gave an unfair advantage to the other companies by awarding them Launch Service Agreements and excluding SpaceX. 

After the Court of Federal Claims ruled that it lacked jurisdiction, the case was transferred in August 2019 to the U.S. District Court of the Central District of California.

The Air Force awarded Launch Service Agreements contracts to Blue Origin ($500 million), United Launch Alliance ($967 million) and Northrop Grumman ($762 million) to help the companies defray the costs of developing new rockets and infrastructure as they competed for a launch service procurement contract. 

SpaceX’s proposal for a Launch Service Agreement contract was to leverage its Starship