00:00Every sortie of the Air Force flies depends on one thing before the crews ever step to the aircraft.
00:04Readiness.
00:04Today, the process of stepping air crews and maintaining readiness is challenged by disparate systems,
00:09manual transcription of records, and harbors vast areas of risk for human error.
00:13Across the Air Force, pilot training, stand eval, currencies, testing, FCIFs, and scheduling
00:18are tracked using multiple disconnected tools, partially functioning websites, spreadsheets,
00:23SharePoint trackers, emails and PDFs, whiteboards and tribal knowledge.
00:27None of these systems talk to each other, creating hours of work linking data points from sources that may be out of date.
00:33The result? Redundant data entry, conflicting records, missed currencies, scheduling rework,
00:38late discoveries before step, and an unacceptable risk of human error.
00:43We are asking airmen to maintain combat readiness using tools that were never designed for the complexity of modern air crew operations.
00:50Strike was not built on assumptions.
00:52We measured the problem.
00:53We conducted voice-of-the-customer interviews with pilots, schedulers, stand eval, training, and leadership,
00:59five-wise analysis, activity analysis to measure where time is actually spent,
01:03end-to-end process and data flow mapping to expose bottlenecks.
01:06What we found was consistent across units.
01:08The same data entered three to seven times.
01:10Critical decisions based on manually reconciled information.
01:14Single individuals acting as single points of failure.
01:16High-risk moments occurring right before step when time pressure is highest.
01:20This is not a people problem.
01:21It's a system design problem.
01:22So what is the solution?
01:24Strike, the scheduling, training, readiness, and integration of key data and evaluations,
01:29solves this by doing one simple but powerful thing.
01:32It unifies air crew readiness into a single authoritative system.
01:35Strike integrates training, stand eval, currencies, testing, FSAFs, and scheduling,
01:41creates a single source of truth for readiness, eliminates redundant data entry,
01:45flags risk before it becomes a problem, reduces reliance on tribal knowledge,
01:49provides air crew with upcoming due tasks to maintain currency,
01:52and gives commanders real-time visibility into readiness and risk.
01:56Today, we have already built a working proof-of-concept version of Strike within Microsoft Access
02:00that our squadron has been using locally to support our flying operations for the last seven months.
02:05Our local version of Strike saves arms, training, and MCCs a combined total of over 800 hours per year,
02:10as well as significantly increasing data integrity by massively reducing the amount of manual data entry required.
02:15Instead of chasing spreadsheets, airmen focus on flying, training, and leading.
02:20Strike doesn't replace people.
02:21It gives them back their time and confidence in the data.
02:24With a projected timeline of just 12 months, our small but dedicated team is focused on rapid development
02:29while maintaining a high-quality product that air crew and support staff can count on.
02:33To succeed, we are asking for requisite POCs, full-time orders for our core three team members,
02:38an additional two to three multi-capable airmen, and advocacy from career field leadership.
02:42The Air Force is flying more complex missions with fewer people in less time.
02:45We cannot afford fragmented systems that increase risk and waste airmen's energy.
02:48Strike and its integration with Palantir Foundry eliminates the need for large IT and program overhead other solutions require.
02:55This is not just an IT solution.
02:56It is the readiness solution.
