ALIS and other automated logistics systems

US Air Force’s acquisition chief talks {ALIS,} new B-52 engines and the future of battle management

Can you provide an update on Mad Hatter, the Air Force’s project to use agile software development to try to fix some of the problems with the F-35’s logistics system? You said in February that several improvements were to be fielded to the Autonomic Logistics Information System within weeks.

Mad Hatter is doing great. I have to give the team an A+ on being able to get started and start pulling apart the problems that our maintainers had.

They already deployed several apps that are helping maintainers. They fixed problems with the electronic equipment logs that were showing false positives, so those have been fixed, and the maintainers get to focus on things that are actually broken — not things that are reported as broken.

They fixed the scheduler, which had mismatches between the flight line system and ALIS, and they are currently working on things that are going to help maintainers do their own workflow on the flight line. There is a lot more to go for them. They’re putting Wi-Fi out on the line so that you can touch ALIS at the flight line, which currently you can’t. Maintainers have to go do their maintenance and then come back and enter data in the subsequent systems, and it doesn’t make sense to create data once and then replicate it again.

We want maintainers to be able to have ALIS in a protected, secure Wi-Fi network at the flight lines; that data is instantly uploaded. We’ve got work to go to get the accreditation done so that we could reach all the way back into the standard operating unit that touches Lockheed Martin. But we got a great partnership with Lockheed. They’ve been with us every step of the way.

What happens next?

I don’t have the answer yet, but one of the things that I think we should consider is the next variant of ALIS to be delivered. That’s 3.6. It’s currently going through negotiation and we’re approaching it as traditional ALIS, but if we believe in agile development, eventually we need to pull a development module of ALIS out of the traditional and put it into the Mad Hatter process. [Version] 3.6 is a candidate for that. If it’s not 3.6, is it 3.7 or 3.8?

The discussions we’re having now is about where’s the chalk line that we switch to the new methodology. We have to have enough development teams to do it and support the level and scope of the software, but I think we’re ready. We’ve got the team in the Air Force. We have 800 people in Kessel Run, [the Air Force’s software development team], that are currently doing amazing work for us.

With agile software development, you want to have exposure with the user. Once those apps were deployed, what was the feedback like? Did users want to see additional fixes, or were the apps coming out well already?

When final deployment was done, it was software as the users wanted. The users are involved from the beginning. Step one is the coders leaving their coding shop and going out to the flight line in Nellis [Air Force Base, Nevada], and sitting down, walking through how ALIS works and how the rest of the maintenance planning tools work. Understanding the pain points: What do you not like? What takes up your time? What do you want to change? Storyboarding that out to understand how it might be fixed, turning that into a development back log; so what am I going to attack and when? And then having the user touch products before they become final.

What the Mad Hatter team does is continues to iterate during design so that by the time you deploy, it’s in the image of what the operators have requested, not in the image of what the developers expected they wanted, and that’s the secret to “agile.”

https://www.defensenews.com/digital-sho ... anagement/

ALIS-Next
From JPO's Facebook https://www.facebook.com/F35JPO/photos/ ... 714517446/

(Do not know why but) From this month JPO had opened Twitter. (There are only a few tweets.)
https://twitter.com/theF35JPO

ALIS is a dirty word on the F-35 program. It has given LM a black eye, of sorts.

And while not excusing LM, because they have a degree of responsibility in the product delivered, I doubt ALIS, being as large and as complicated as it is, was a freebie that LM threw together and told the miltary / JPO, "Hey, we've got this great software tool for you to use to maintain the F-35... you'll love it!"

Rather, being as large and as complex as it is, I am guessing the requirements for ALIS are rather detailed, complex, and lengthy in and of themselves. While aerospace companies are not known as stalwarts of software elegance, the military services are not terribly bright either, at writing good requirements, less software requirements that can be terribly complex and tedious. Generally speaking, the US government gets exactly what they specify in a contract.

"Eight clicks to load a weapon"? How much paperwork was involved before ALIS / F-35 came along?

ALIS + Mad Hatter is going well...?
https://breakingdefense.com/2019/09/net ... -progress/

Net Assessment Comes To DNI; Roper Says F-35’s ALIS Makes Progress
By COLIN CLARK on September 05, 2019
NATIONAL HARBOR: A key capability the Defense Department has relied on since the late Andy Marshall invented it — Net Assessment — is coming to the Intelligence Community.

In other news, the head of Air Force acquisition, Will Roper, told me that the attempt to rebuild F-35’s maintenance and mission planning system known as ALIS as a cluster of apps is “going well, actually.”

However, the nascent effort is still an experiment at Nellis AFB run by software team known as Mad Hatter. The next step is, Roper said, for the Navy to decide if Mad Hatter should continue to work on what may become a substantial rebuild of ALIS, which has become perhaps the most troubled part of the F-35 program. That decision will be up to the Navy’s James Geurts, assistant secretary for research, development and acquisition, who now has acquisition authority for the F-35.

How good is ALIS 3.1.1...?
https://aviationweek.com/defense/lockhe ... chitecture

Lockheed To Migrate F-35 Backbone To Cloud Architecture
Sep 11, 2019Lee Hudson and Steve Trimble | Aerospace Daily & Defense Report
Lockheed Martin intends to migrate its F-35 digital support backbone, the Autonomic Logistics Information System (ALIS), to a native-cloud architecture by year’s end and field it in 2020.

A joint government and industry team tested an early version of the new framework in both lab and flight test environments in May, company spokesman Mike Friedman said in a Sept. 11 statement to Aerospace DAILY.

“By moving all ALIS applications to a cloud-native, open architecture, we can rapidly develop and test pieces of ALIS without having to load the entire system for each upgrade,” he said. “And instead of aggregating many fixes over a 12- to 18-month period into a single upgrade, the new approach allows developers to create, test, receive feedback and implement fixes every few weeks while reducing development and fielding costs.”

The new construct still must be tested in an operational environment so that developers can garner user feedback to refine their approach.

Separately, the newest ALIS software release, 3.1.1, is saving pilots an average of 35 min. in report generation and review. The new software release also is saving maintainers 40 min. each day in report generation and several hours weekly in managing fleet directive reports, he added.

“This latest release leverages the development work Lockheed Martin completed in 2018 with its internal investment funding,” Friedman said. “In 2018, Lockheed Martin invested approximately $50 million in ALIS and will continue investing approximately $180 million through 2021 to modernize ALIS and enhance enterprise sustainment systems.”

Extrapolated across the enterprise of more than 425 aircraft flying today, it will save more than 20,000 manhours annually. Lockheed Martin has invested in additional time saving and efficiency ALIS automations and is working with the government on implementation and fielding plans, Friedman said.

The Pentagon plan to save the F-35’s logistics system hinges on whether Lockheed will relinquish data control
14 Nov 2019 David B. Larter & Joe Gould [BEST READ IT ALL AT THE SOURCE]

"WASHINGTON – The Pentagon and Lockheed Martin are at odds over how much data the military can have access to for its own jet, the F-35, and that’s creating renewed friction in the fight to fix longstanding issues with the automated logistics system vital to keeping it flying. The Pentagon and Lockheed say a relaunched version of the Autonomic Logistics Information System, or ALIS, should be ready to start sending to squadrons by September 2020. Both the military’s top acquisition official and the F-35 program manager expressed frustration to lawmakers at a House Armed Services subcommittee hearing Tuesday with how much control Lockheed asserts over crucial data for the system....

...“One of the key elements of coming up with a new ALIS architecture, data standards, and all the other parts that would make a very good system is understanding the data set as it exists today — what all the algorithms are — and we are still in the process of going through that with Lockheed Martin,” said Ellen Lord, the under secretary of defense for acquisition and sustainment. “But understanding where all the intellectual property is and making sure the government has access to what it has paid for is a key part of rearchitecting ALIS.”

The fight over intellectual property stems from the original concept for the program, which gave Lockheed Martin sweeping control over virtually every major aspect of the F-35, from design and fabrication to maintenance, parts and logistics. But in recent years, dissatisfied by rising costs and delays, the Pentagon has sought to wrest more control back from Lockheed. Intellectual property rights and disputes over proprietary data, however, have often tripped up such efforts.

Frustrations
Some of Lockheed’s intellectual property assertions have bordered on ridiculous, according to F-35 Program Executive Officer Lt. Gen. Eric Fick, but getting a handle on what data the military needs to do its job is crucial, he said....

...Lord told lawmakers that the key to getting a successful system was breaking Lockheed’s grip on the logistics data infrastructure and housing more of it in a government cloud. “One of the challenges we have is that fact that a lot of the ALIS data and functionality works back through Lockheed Martin computers,” Lord said. ‘So, what we need to have in a newly rearchitected ALIS to is have that in a government cloud and accessible. So, this deconflicting of Lockheed data and government data will become much more clear.”... [then some good stuff to read at URL]

...Fick, who runs the Joint Program Office, told lawmakers that the latest software release for ALIS is expected this month. He predicted “significant progress” by September 2020 toward four different efforts to improve ALIS, including software upgrades, rearchitecting the system itself and Lockheed’s internal research and development work.

Though the ALIS software release in the fall of 2018 met the required-capabilities threshold for its design and development phase, Fick acknowledged the system needs “significant additional improvements” and noted that combat coded squadrons require 12 system administrators to maintain deployed operations and that training squadrons require eight.... [then stuff about risk & flight hours & availability best read at URL - get the picture? Read it all at URL]

...The U.S. F-35 fleet missed the monthly availability target of 65 percent, missed an 80 percent mission-capable target and missed reliability and maintainability metrics. Behler linked recent improvements in availability and mission capable rates to a greater availability of spare parts ― through the programs efforts to improve maintenance process and depot support.

Fick noted that the mission capable rate of the operational fleet jumped from 54.7 percent in October, 2018, to 72.5 percent in September of 2019.

Parts shortages was the chief contributor to low mission capable rates, Government Accountability Office’s Director of Defense Capabilities and Management Diana Maurer, told lawmakers. Parts were breaking more often than expected, it’s taken twice as long to fix them, and the depots for the repairs won’t be ready until 2024."

Source: https://www.defensenews.com/naval/2019/ ... ta-rights/

So, last month during the 478 aircraft block buy announcement it was, “...the aircraft are performing exceptionally well...” from DoD acquisition leadership. Hmmm...

Further F-35 ALIS Fixes in Progress as Pentagon Tackles Jet Costs [BEST READ AT SOURCE]
13 Nov 2019 Rachel S. Cohen

"The F-35 is making progress but still faces major hurdles with its logistics system, intellectual property, supply chain, and more, officials overseeing the F-35 Joint Strike Fighter program told lawmakers on Capitol Hill Nov. 13. Program leadership laid out a path to turn one of the key challenges, the underperforming Autonomic Logistics Information System, into a functional tool for operations and maintenance data as it’s meant to be....

...“Over the past year, the department has delivered three ALIS software updates and we are on track to release quarterly releases to rapidly improve current performance—a vast improvement from the 18 months between software updates in the past,” Lord [Pentagon acquisition chief Ellen Lord] added in written testimony. “Our efforts to stabilize and improve the usability of ALIS has driven trouble reports down 38 percent from their peak. These efforts mitigate risk while the department charts a path to the future of ALIS that will help deliver a more ready fleet at a lower cost."...

...“Upcoming software releases include the capability for centralized administration, bulk administration of Portable Maintenance Aids, and squadron resource sharing,” Fick wrote. “These initiatives will reduce the requirements for on-site administration of the current ALIS system with an estimated decrease in life [cycle] costs of $1.9 billion, nearly a 6.5 percent cost reduction.”

Robert Behler, the Pentagon’s director of operational test and evaluation, noted the data the F-35 sends to the Air Operations Center, which manages sorties overseas, is subpar. He suggested the AOC could use an ALIS terminal or software-defined radios to gather data on the plane in real time. [???]

Officials are working through other areas as well. Intellectual property disputes, an issue that piqued the interest of multiple lawmakers, has slowed the program’s ability to connect to the Pentagon’s Joint Simulation Environment—a major wargaming system the F-35 must work with to complete its initial test phase. Behler said the JSE won’t be ready to start the final phase of operational testing with the F-35 until July 2020.

The initial integration of the JSE and F-35 was held up by an IP dispute between Lockheed and the government, Fick said [ F-35 Program Executive Officer Lt. Gen. Eric Fick]. He told lawmakers that DOD agreed to accept less IP data than it might want, but still reserved the right to challenge Lockheed if it didn’t release certain information the Pentagon wanted. Lockheed protested that arrangement, and its complaint currently sits with the Armed Services Board of Contract Appeals. DOD doesn’t necessarily need every piece of IP data, but Fick said the program is still figuring out which information is crucial to making the F-35 a better product.

“One of the key elements of coming up with a new ALIS architecture, and … data standards, and all the other parts that would make a very good system, is understanding the entire data set as it exists today, what all the algorithms are, and we are still in the process of going through that with Lockheed Martin,” Lord added. “Understanding where all of the intellectual property is and making sure the government has access to what it has paid for is a key portion of rearchitecting ALIS.”...

...The F-35 Joint Program Office saw a 9 percent drop in cost per flying hour in 2019 compared to the previous year, according to Fick’s written testimony."

Source: http://www.airforcemag.com/Features/Pag ... Costs.aspx

Further F-35 ALIS Fixes in Progress as Pentagon Tackles Jet Costs [BEST READ AT SOURCE]
13 Nov 2019 Rachel S. Cohen

...but Fick said the program is still figuring out which information is crucial to making the F-35 a better product.

“One of the key elements of coming up with a new ALIS architecture, and … data standards, and all the other parts that would make a very good system, is understanding the entire data set as it exists today, what all the algorithms are, and we are still in the process of going through that with Lockheed Martin,” Lord added. “Understanding where all of the intellectual property is and making sure the government has access to what it has paid for is a key portion of rearchitecting ALIS.”...


Source: http://www.airforcemag.com/Features/Pag ... Costs.aspx

Sorry... not sorry.

"the program is still figuring out which information is crucial" ... ???

The government doesn't know? Sounds like a major failing of the gummint in not know what they bought.

It's the government's game. They set the rules. Contractors tend to stick to the rules, religiously... usually because the gummint audits the snot out of them (also driving up costs) and the fines for not conforming to contracts can be expen$ive.

While I suspect LM could probably have done a better job with ALIS, it also sounds like the gummint is getting exactly what it specified and paid for. So the government... the same institution that spend $billions on some basic medical insurance website boondoggle, thinks it can save ALIS by creating a better one? Except it doesn't know what the data and algorithms are? And they're going to wave a magic wand and fix it in 2-3 years?

From DOD official site.
https://www.defense.gov/explore/story/A ... 35-system/

DOD Expects Significant Progress on Critical F-35 System
NOV. 13, 2019 | BY C. TODD LOPEZ
Nearly 460 F-35 Lightning II joint strike fighter aircraft have been delivered to military organizations around the world — including the U.S. Air Force, Navy and Marine Corps, as well as to a handful of partner nations. But a critical component of the F-35 program, the Autonomic Logistics Information System, or ALIS, has proven less stellar than the aircraft itself. Defense Department officials say that's going to change soon.

The F-35 manufacturer bills ALIS as the "IT backbone" of the F-35 system. ALIS is meant to be involved in aircraft sustainment, maintenance, planning and support. For example, both operators and maintainers would use it for work orders and automatically ordering spare parts. The F-35 has a wide array of sensors that can upload data into ALIS after it lands. The system can analyze how the jet performed and identify parts that might be wearing out — and then order them.

"Sadly, as presently constituted, ALIS is not delivering the capabilities the warfighter needs," Ellen M. Lord, undersecretary of defense for acquisition and sustainment, said today during a joint hearing of two House Armed Services Committee subcommittees. "The problems with ALIS are ones we can and must solve."

Lord told lawmakers the Defense Department has a plan to make ALIS work the way it was intended.

DOD has assigned ALIS issues to specific individuals with dates that they need to meet, she said. "What we are doing is re-architecting ALIS to make sure it meets the needs of the warfighter while making good use of taxpayer dollars, and we are working on a detailed plan right now as to when that capability will be delivered," Lord said.

Air Force Lt. Gen. Eric T. Fick, the F-35 program executive officer, said the version of ALIS in the field now is 3.1.1.1, but that version 3.5 is being fielded now. "That will bring about 300 stability fixes to that baseline functionality to allow it to be a better system for the users," he said.

Fick said he expects "significant progress" on ALIS by fall of 2020, when existing "squadron operational units" — the individual ALIS systems used by units that operate the F-35 — might be shut down in favor of a new version.

Ongoing efforts by the Air Force, aircraft manufacturer Lockheed Martin, and DOD will coalesce into a "single new version of ALIS marching forward that leverages an underlying data architecture that's expandable with the expanding fleet in ways that the current ALIS is not," Fick said.

https://docs.house.gov/meetings/AS/AS03 ... 191113.pdf

STATEMENT OF GREGORY ULMER VICE PRESIDENT AND GENERAL MANAGER F-35 PROGRAM LOCKHEED MARTIN CORPORATION
BEFORE THE READINESS AND TACTICAL AIR & LAND FORCES SUBCOMMITTEES HOUSE ARMED SERVICES COMMITTEE ON F-35 PROGRAM UPDATE: SUSTAINMENT, PRODUCTION AND AFFORDABILITY CHALLENGES
NOVEMBER 13, 2019
ALIS Modernization At Lockheed Martin, we want F-35 maintainers to feel the same pride and excitement as F-35 pilots, and we recognize that improving ALIS is foundational to changing their experience. In partnership with the JPO, our goal is to drastically improve speed, minimize hardware infrastructure, reduce required labor and enhance user experience and overall capability.

We continue to make incremental improvements with each ALIS software update. We recently fielded ALIS version 3.1.1. , which improves workflows and saves thousands of man-hours annually across the fleet. In flight test, users saved an average of about 35 minutes per flight in generation and pilot review; about 40 minutes per day in maintenance report generation and several hours per week in managing fleet directive reports. Extrapolated across the enterprise of more than 455 airplanes flying today, this saves more than 20,000 man-hours annually.

We are now fielding ALIS version 3.5 before year-end which will bring further improvements to the system, including improved Air Vehicle transfers, usage and aircraft component stabilization, Low Observable Health Assessment System (LOHAS) enhancements, Electronic Equipment Logbook (EEL) visibility with dashboard, and improved inventory accuracy.

The incremental enhancements to ALIS are directly improving performance on the production flight line. In August 2019, a newly delivered F-35A aircraft landed Code One and flew its first operational mission within five hours of landing at Hill AFB from Lockheed Martin’s Fort Worth factory.

This latest release leverages Lockheed Martin’s internal investment in 2018 of $50 million, which will rise to approximately $180 million through 2021 to modernize ALIS and enhance enterprise sustainment systems.

We are also partnering with the JPO and 309th Software Squadron from Hill AFB to make longer-term investments that take advantage of agile concepts and commercially available tools, and also account for unique warfighter operational needs like deploying to austere sites, supporting operations with no network connections, and upholding stringent security and cyber requirements. Lockheed Martin’s goal is to deliver a modernized ALIS by 2020 that is driven by 4 key enhancements:

• Agnostic cloud-native architecture: As the ALIS integrator, Lockheed Martin is moving ALIS applications to a cloud-native, open architecture, we can rapidly develop and test pieces of ALIS for each upgrade. And instead of aggregating many fixes over a 12 to 18-month period into a single “big bang” upgrade, the new approach allows developers to create, test, receive feedback and implement incremental fixes every few weeks while reducing development and fielding costs. The important part of this modernized architecture is the cloud-enabled technology – which enables secure development operations (DevSecOps) and lower administration cost while allowing incorporation of 3rd party commercial off-the-shelf software modules, additional applications developed by others into ALIS.

• Automated test and deployment: The DevSecOps approach increases the ability to conduct automated test and deployment of software updates utilizing commercial best practices to improve velocity of updates and improvements to the field. A testament to the DevSecOps approach was our recent ability to issue eight software upgrades in just one week.
Improved user interface and user experience: Lockheed Martin partnered with Silicon Valley company UE Group to redesign the ALIS weapons loading user interface, driving complexity, time and cost out of maintenance workflows in ALIS. The JPO team validated a 60 percent improvement in the workflow for weapons loading using the newly designed user interface. We have not stopped there however, as we continue to modernize and re-engineer older code and data structures into improved performing applications fielded in a rapid manner – in fact striving for the “pace of war.” Lockheed Martin has done this although each of our U.S. Services, international partners and foreign military sales countries have different operating concepts, missions, and sovereign needs.

• Strengthened cyber security and data resiliency: With the transition to a cloud-native architecture we continue to improve the cyber security of ALIS and we’ve implemented several actions including automation and enhanced supplier accountability processes that are delivering improved data resiliency. In addition, offline key data is vetted and validated automatically versus manually, improving speed and ensuring accurate integrated data. With these new actions and related efforts, we’ve seen a 50 percent reduction in Electronic Equipment Logbooks and other action requests since 2017, which indicates software and data quality are steadily improving.

What is the right path for ALIS?
Proposal: I propose the ALIS contest. Ah... Like the X-35vsX-32 JSF contest, How about ALIS competing contest DoD vs LM ? (madness)@@@@@@

Kessel Run brings new software to Vermont ANG aircraft maintainers
11 Mar 2020 Julie M. Shea, 158th Fighter Wing Public Affairs

"SOUTH BURLINGTON, Vt. (AFNS) -- Vermont Air National Guard’s 158th Fighter Wing recently partnered with software company, Kessel Run to complete its first test and evaluation of their new software, a suite known as Mad Hatter, at the Vermont ANG Base in South Burlington.

In the course of two weeks, Kessel Run personnel started with zero Mad Hatter users from the Vermont ANG and grew to 78 user accounts at the 158th Maintenance Group. Airmen were able to recover, service and launch aircraft entirely using Mad Hatter applications, resulting in 10 successful sorties flown.

Mad Hatter, part of Air Force Life Cycle Management Center’s Detachment 12, or Kessel Run, is organized under Air Force Materiel Command in partnership with the F-35 Joint Program Office and other entities. They are a government entity and software development organization based in Boston, and are primarily focused on employing new technologies to modernize the Air Force, including innovating F-35A Lightning II maintenance.

“Kessel Run is the Air Force’s first real foray into trying to do software better, smarter, faster with modern technology,” explained Alexander Morris, Kessel Run portfolio owner and Air Force civilian employee. “Inside Kessel Run, we have two branches. One is air ops … We’re under wing ops, which handles aircraft maintenance. Mad Hatter is the product name, it’s our customer-facing name for everything we make. Right now, it’s eight different applications all rolled up together.”

The Kessel Run team arrived in South Burlington in late January to provide user briefings on the functionality of the Mad Hatter suite and to complete onboarding for the first group of users. Throughout their first week in Vermont, they observed F-35 flying operations, gathered and responded to user feedback and resolved issues where needed, further completing onboarding during January’s drill weekend.

On average, members of the 158th MXG were able to create a new account in a single day. Mad Hatter accounts are able to be created by the user, in-house, in a much shorter amount of time, and these Airmen were able to start using the application immediately. Lockheed Martin’s Autonomic Logistics Information System has proven to be a timely process that requires filling out request forms and waiting on approval from a third party in another office, who then creates the account on the requester’s behalf. This often takes weeks or months, reducing the efficiency of onboarding new maintainers.

“Mad Hatter is a program working with Kessel Run and the DoD to create a more user-friendly program for the F-35,” said Tech. Sgt. Leah Curtin, 158th MXG crew chief. “Basically, to make the job easier for not only for the maintainers on the flightline but also for production and being able to schedule maintenance easier, schedule flying and have the program all in one, live and up-to-date so anyone can actually keep tabs on what aircraft is flying, what aircraft is maintenance and a better way to fix the jet in a reasonable amount of time.”

To address those tasks and improve the efficiency between roles, the Mad Hatter suite is currently composed of eight different applications to include fleet management, personnel management, audiovisual (AV) schedule, technical orders, AV configuration, debrief, work orders and aircraft status, all of which work in conjunction with Lockheed Martin’s ALIS.

“We’ve got eight different applications that are designed to take the functionality that is in F-35’s ALIS and modernize it to the point where we save thousands of maintenance man hours per year in duplication of entry, scheduling our folks more effectively to work on the flightline,” Morris said. “Our eight different applications – which we’ve started with and we’ll probably grow into a couple more in the future – are significantly more user-friendly, when they’re hosted in the cloud. They’re going to be adopted by the F-35 Joint Program Office into a massive overarching modernization effort.”

The primary advantage of the Mad Hatter platform is the ability to pull and transfer data between all eight applications and integrate that information into an intelligent display and readout that is consolidated onto a single screen, capable of updating in real-time due to the use of modern software technology.

“Mad Hatter provides several applications … all within one program (that is) very simple to navigate. It’s also very user-friendly in the way everything views, whereas ALIS, you have to go back and forth between windows just to accomplish one objective. Mad Hatter … it’s all right there on one page,” said Senior Airman Liam McKelvey, 158th MXG crew chief.

Used on government computers, the Mad Hatter interface can be accessed sitting at a desk inside an office or transferred outside, such as on the flightline, by using mobile computers with touchscreens. The Wi-Fi connectivity and application integration provide ease of use, while the use of cloud storage provides modern security.

Curtin explained that Mad Hatter has made their jobs easier, as it can be used on the go. She continued that there is excitement that the portability will allow crew chiefs to fill out forms and complete jobs immediately on the flightline, rather than hours later back in the office.

With an emphasis on user experience, the Kessel Run group was focused on developing maintainer-to-software developer relationships during their visit to the 158th FW. During this training, 21 Kessel Run employees visited Vermont at varying times to be able to interact with Airmen. They shadowed maintainers who were using their products for the first time, provided training and tips for use, and gathered feedback on how to improve the software and user experience.

Establishing such relationships allow for coders and designers to have direct contacts for feedback, providing Mad Hatter product teams with a wealth of knowledge from the maintainers in Vermont who provide product and user experience feedback. In return, the Boston-based team is available to provide regular help-desk support on all applications and is quick to understand, respond and meet the needs of the F-35 maintenance community by talking directly to the maintainers using their products.

“Two weeks ago, I was introduced to Mad Hatter and I’m hoping it becomes a thing here and Air Force-wide,” McKelvey said. “So far, the product has been pretty handy, pretty user-friendly and pretty easy to navigate, especially compared to (other products).”

Photo: "Maj. Jennifer Kannegaard, Mad Hatter F-35 Lightning II Joint Strike Fighter software project product manager, leads members of the software design team to a working area for 57th Wing Bolt Aircraft maintenance unit maintainers April 10, 2019, at Nellis Air Force Base, Nev. The Vermont Air National Guard recently added 78 user accounts at the 158th Maintenance Group, during which the Airmen were able to recover, service and launch aircraft entirely using Mad Hatter applications. (U.S. Air Force photo by Airman 1st Class Bailee Darbaise)" https://media.defense.gov/2019/May/14/2 ... 71-011.JPG (5.3Mb)

Source: https://www.af.mil/News/Article-Display ... intainers/

....during which the Airmen were able to recover, service and launch aircraft entirely using Mad Hatter applications.

Who puts the virtual chocks in?

What could possibly go wrong.

HOT CHOCK LATE? https://www.youtube.com/watch?v=epOtBesq18s