CAPE EVAMOSC Platform Support

Dive into the EVAMOSC opportunity and discover how this major DoD initiative is transforming operating and support cost visibility through advanced data analytics, cloud platforms, and enterprise-wide sustainment solutions. Learn about the contract scope, key requirements, and what makes this opportunity strategically important for government contractors.

Tune in now to stay ahead of federal contracting trends and gain actionable insights into the EVAMOSC platform support opportunity.

Contact ProposalHelper at sales@proposalhelper.com to find similar opportunities and help you build a realistic and winning pipeline. 

Transcript

Sticker Price Versus Upkeep

SPEAKER_00 0:00

Have you ever like bought something really expensive, uh, maybe like a car, and you just feel that immediate wave of buyer's remorse.

SPEAKER_01 0:09

Absolutely. The second you drive it off the lot.

SPEAKER_00 0:11

Right. You save up all the money, you negotiate the price, you sign that uh that endless stack of papers, and you drive it off feeling fantastic. But then, you know, a year goes by.

SPEAKER_01 0:22

And then the reality of owning it sets in.

SPEAKER_00 0:24

Exactly. You suddenly have to pay for comprehensive insurance, routine oil changes, maybe a whole new set of tires, or I mean, there's that weird rattling noise in the engine that costs a thousand bucks just for a mechanic to diagnose.

SPEAKER_01 0:37

Aaron Powell Yeah, because the initial acquisition, that's visible. It's a one-time transaction. But the operating and support costs, the fuel, the maintenance, the human labor, that firms a massive ongoing financial commitment.

SPEAKER_00 0:49

Trevor Burrus, Jr.: Yeah, and it often just completely dwarfs the original purchase price. Suddenly you realize the sticker price was just, well, the opening bid, the upkeep is what actually drains your bank account. So I want you to imagine that exact scenario. But instead of just a single commuter car, you're managing a massive global fleet of military helicopters, heavily armored tanks, precision missile systems. Trevor Burrus, Jr.

SPEAKER_01 1:12

Which is a logistical nightmare, honestly.

SPEAKER_00 1:13

Yeah, right. And instead of draining your personal bank account, the upkeep is pulling from a multi-billion dollar military budget. You would assume, right, that the entity paying those bills knows exactly where every single dollar is going.

SPEAKER_01 1:25

Aaron Powell Well, you would assume that. But the reality of enterprise-scale government accounting is um it's far more convoluted. Trevor Burrus, Jr.

SPEAKER_00 1:32

It always is.

SPEAKER_01 1:33

Yeah. The sheer volume of transactions and you know the legacy systems tracking them, it creates this environment where the true granular cost of operating a specific weapon system becomes incredibly difficult to pin

The EVAM OSC Mission And Sources

SPEAKER_01 1:46

down.

SPEAKER_00 1:46

Aaron Powell, which brings us to today. Welcome to today's deep dive. We are looking at how the U.S. Department of Defense is attempting to solve this colossal multi-billion dollar blind spot regarding exactly how much its major weapons systems actually cost to operate and maintain.

SPEAKER_01 2:00

And our grounding material for this exploration is uh it's a stack of highly detailed U.S. government contracting documents.

SPEAKER_00 2:07

Aaron Powell The fun stuff.

SPEAKER_01 2:09

Oh, very dense reading. Specifically, we're looking at a request for proposal number, HQ00342000079, along with two performance work statements or PWS documents.

SPEAKER_00 2:23

Aaron Powell And these outline a massive data integration project known as EVAM OC, right?

SPEAKER_01 2:27

Exactly. EVAM OC.

SPEAKER_00 2:29

So the mission of this deep dive is to basically decode this dense contracting material. Because if you look past the bureaucratic formatting and the, you know, the endless acronyms.

SPEAKER_01 2:39

There's so many acronyms. So many.

SPEAKER_00 2:40

But what you find is this genuinely fascinating story about advanced fita science, government bureaucracy, and what it actually takes to build a 100-terabyte system capable of tracking every drop of aviation fuel and like every spare tank tread across

Siloed Systems Create Cost Fog

SPEAKER_00 2:54

the entire military.

SPEAKER_01 2:54

Aaron Powell To really understand the solution here, we first have to fully grasp the problem, which is highlighted right at the top of these sources. Right. Despite having the largest military budget in the world, the documents flatly state that the DOD lacks complete, accurate, and granular data on the operating and support costs.

SPEAKER_00 3:13

Aaron Powell They call those OS costs, right?

SPEAKER_01 3:14

Yeah, ONS costs. And they lack this data for many of their major acquisition programs.

SPEAKER_00 3:20

Okay, let's unpack this. Because to the average listener, it sounds completely absurd that the military wouldn't already track this stuff. But if you break down the mechanics of a massive organization, it sort of starts to make sense.

SPEAKER_01 3:32

Aaron Powell It does. It's an enterprise problem.

SPEAKER_00 3:34

Right. So think of it like trying to run a massive Fortune 500 delivery company. The HR department is meticulously tracking all the truck driver salaries in one specialized software system. Sure. Then the mechanics down the garage, they have a completely different database where they log replacement brake pads and tires. And a third, entirely separate logistics department tracks fuel consumption at the pumps.

SPEAKER_01 3:58

And they don't talk to each other.

SPEAKER_00 4:00

Exactly. Everyone is doing their job perfectly, but the databases are completely siloed. So the CEO sitting at the top has absolutely no idea if delivery truck number 42 is actually profitable to keep on the road because all that cost data is just fractured across three different departments.

SPEAKER_01 4:17

If we connect this to the bigger picture, the stakes here are significantly higher than a delivery company.

SPEAKER_00 4:23

I mean, obviously, yeah.

SPEAKER_01 4:25

The sources point out that this fractured data environment isn't just an administrative annoyance, it's actually a legal liability.

SPEAKER_00 4:32

Wait, really? A

Title 10 Mandate For CAPE

SPEAKER_00 4:33

legal liability?

SPEAKER_01 4:34

Yes. There is a specific statutory mandate driving this entire project. The documents reference Title 10 of the U.S. Code, Section 2337A.

SPEAKER_00 4:43

Okay.

SPEAKER_01 4:43

It's a federal law concerning guidance on life cycle management.

SPEAKER_00 4:46

So Congress actually had to put it in writing and like pass a law demanding accountability for these operating costs.

SPEAKER_01 4:52

Pretty much. Congress recognized the blind spot. This law legally requires the Director of Cost Assessment and Program Evaluation, an office known as OSD KPE, to develop and maintain a centralized database on these actual realized operating and support costs.

SPEAKER_00 5:07

OSD CAPES. So they're the ones on the hook for this.

SPEAKER_01 5:10

Right. KPE acts as the internal auditors and prognosticators of the DoD. They have this strict statutory requirement from Congress, but the enterprise database they need to fulfill it. It literally does not exist yet across this sprawling DoD infrastructure.

SPEAKER_00 5:26

Wow. And just as a reminder to you listening, we're simply unpacking the goals stated in these government documents. The text itself, driven by Congress, explicitly argues that without this centralized data, the government just can't achieve savings for the taxpayer or control these massive sustainment budgets.

SPEAKER_01 5:45

Exactly. We're looking at the mechanism they are building to attempt that goal, regardless of the broader politics surrounding military spending.

SPEAKER_00 5:51

Aaron Powell Right, because without data-driven insight, you just can't improve life cycle cost estimates for future programs. You're basically flying blind in the sustainment phase, which is where the vast majority of a weapon system's lifetime cost actually occurs.

SPEAKER_01 6:03

Aaron Powell, which is exactly why solving a structural problem of this magnitude requires a massive framework and frankly serious technological investment.

SPEAKER_00 6:11

Yet

The 100 Million Dollar IDIQ Plan

SPEAKER_00 6:12

this isn't cheap.

SPEAKER_01 6:13

No, not at all. And that leads us directly to the financial architecture of the request for proposal. The government isn't just cutting a single check, they're utilizing an indefinite delivery, indefinite quantity contract.

SPEAKER_00 6:27

An IDIQ.

SPEAKER_01 6:28

Yes, an IDIQ.

SPEAKER_00 6:29

And the maximum value on this IDIQ is a staggering $100 million.

SPEAKER_01 6:33

It's massive, but the IDIQ format is crucial here. It basically tells the contractor look, we have a massive complex integration problem up to this $100 million ceiling, but we can't predict every single data hurdle on day one.

SPEAKER_00 6:46

Aaron Powell Because it's too big to map out entirely in advance.

SPEAKER_01 6:49

Exactly. So they say we will issue specific task orders as we define the exact requirements over time. And the overarching umbrella for all this work is that EVAMAAC system. Right.

SPEAKER_00 7:00

Enterprise visibility and management of operating and support cost, EVAAC.

SPEAKER_01 7:04

Aaron Powell And the technical scale detailed in the performance work statement is huge. It requires the contractor to design a secure, scalable repository that can handle up to 100 terabytes of data.

SPEAKER_00 7:15

Aaron Powell Wait, let me push back on that for a second.

SPEAKER_01 7:17

Sure.

SPEAKER_00 7:17

Because 100 terabytes, I mean, in the era of massive cloud computing, 100 terabytes is practically nothing. Uh-huh. No, seriously, Netflix streams that in a fraction of a second globally, right? You can buy a desktop hard drive with a huge chunk of that capacity for just a few hundred bucks. So why is this a $100 million problem if the storage footprint is that relatively small?

SPEAKER_01 7:41

Because it is a structural relational data problem, not a storage volume problem. We aren't talking about storing massive 4K video files or high-resolution images, which, you know, chew up terabytes quickly.

SPEAKER_00 7:54

Right. Video is huge.

75 Legacy Systems And Data Wrangling

SPEAKER_01 7:55

You're talking about text. Millions upon millions of individual transaction rows. The sources explicitly state that the data acquisition and preparation task is the most challenging aspect of the work.

SPEAKER_00 8:06

Oh, okay.

SPEAKER_01 8:06

And it represents the greatest value to the government. The contractor has to pull data from over 75 disparate legacy source systems.

SPEAKER_00 8:12

75? Wow, that is the core of the friction right there. Because these 75 systems cover everything from financial management to logistics, maintenance, human resources, property, and the documents note that absolutely none of those upstream data systems were designed or implemented to support cost mapping to individual weapons.

SPEAKER_01 8:33

Yeah, they were just built to pay people or order parts.

SPEAKER_00 8:36

Right. So the mechanism of this challenge is what justifies the $100 million ceiling. The contractor's real job is complex data cleansing and wrangling.

SPEAKER_01 8:45

Think of it this way: imagine you're trying to calculate the true cost of a decade of family dinners.

SPEAKER_00 8:50

Okay, I'm tracking.

SPEAKER_01 8:52

But your receipts are from 75 different grocery stores. Some receipts measure ingredients in weight, some in volume, some are in different currencies, even. And half the receipts are from like 1998.

SPEAKER_00 9:04

And none of them say dinner on Tuesday. They just list a raw ingredient, like flour or tomatoes.

SPEAKER_01 9:09

Aaron Powell Precisely. So the contractor has to build algorithms that grab those raw ingredients and turn them into a cohesive meal.

SPEAKER_00 9:15

Man, that sounds impossible.

SPEAKER_01 9:17

It's incredibly complex. They have to build automated business rules that map general ledger transactions, so raw accounting data over to the highly structured Cape Cost estimating structure.

SPEAKER_00 9:28

Aaron Powell And to highlight the sheer mechanical difficulty of that, the sources mention that all incoming data expressed in dollars are in then year dollars.

SPEAKER_01 9:35

Aaron Powell Which is a huge headache.

SPEAKER_00 9:37

Aaron Powell Meaning the cost is recorded exactly as it was on the day of the transaction, completely unadjusted for inflation.

SPEAKER_01 9:43

Yes. So the algorithms have to grab a supply invoice from, say, 2004, explicitly identify the economic index for that specific base year, apply the exact inflation conversion rate to normalize it into current year dollars. Wow. And then trace that specific expenditure to the engine of one specific vehicle. It is automated forensic accounting on just a staggering scale.

SPEAKER_00 10:07

And obviously, you can't test a highly experimental 100-terabyte data model on the entire military at once without causing absolute chaos. You need a sandbox, right? A massive self-contained data ecosystem to prove the concept actually works.

Proof Of Concept Using Army Fleets

SPEAKER_01 10:20

Exactly. And that logic dictates the strategy behind Task Order One.

SPEAKER_00 10:24

Right. Task Order One, this is the proof of concept. It focuses primarily on U.S. Army weapons systems, starting specifically with the ground vehicle commodity group.

SPEAKER_01 10:34

Though the documents do note that future task orders will expand to address the Navy, Air Force, and Marines, but the Army provides the perfect testing ground.

SPEAKER_00 10:43

And the hardware they're tracking in this first phase, it really grounds this abstract data project in heavy reality. They are mapping costs for M1 Abrams tanks, Apache and Blackhawk helicopters, striker vehicles, javelin missiles, and the MQ-1C Grey Eagle drones.

SPEAKER_01 10:59

It's a massive fleet.

SPEAKER_00 11:00

Yeah.

SPEAKER_01 11:00

And they aren't just tracking the broad category of Abrams tanks.

SPEAKER_00 11:03

Right, because the variations matter. The system has to handle type model series or mission description series derivatives.

SPEAKER_01 11:09

Yes, the data has to differentiate between a base M182 and M1A2 SEP or an upgraded M182 SCP-3.

SPEAKER_00 11:16

And the MQ1C Grey Eagle, I mean, that isn't just a drone flying in the air. Tracking its cost means tracking the ground control stations, the satellite links, the specific maintenance crew hours.

SPEAKER_01 11:25

The data granularity has to be flawless.

SPEAKER_00 11:27

So to achieve that granularity, we have to look at the alphabet soup of legacy feeder systems this new platform is forced to ingest.

Converting Fuel Ammo Transport Into Dollars

SPEAKER_00 11:36

The sources list systems like FedLog.

SPEAKER_01 11:38

Right, FedLog. This is the Federal Logistics Data System. It's essentially a massive parts catalog where they pull prices for consumable repair parts.

SPEAKER_00 11:46

But then FedLog has to talk to FMD, Fuel Manager Defense, which is run by the Defense Logistics Agency.

SPEAKER_01 11:52

Aaron Powell And this is where the systems clash spectacularly. FMD measures fuel transactions in volume, so gallons on hand and gallons pumped.

SPEAKER_00 12:01

But the SVPE database doesn't care about gallons, right? They need to report to Congress in dollars.

SPEAKER_01 12:06

Aaron Ross Powell Exactly. So the automated business rules have to grab a transaction from FMD in gallons, ping another database to find the exact price per gallon on that specific day.

SPEAKER_00 12:15

Oh my gosh.

SPEAKER_01 12:15

Convert it into dollars, and then somehow link that fuel burn back to an Apache helicopter's tail number, not just the military base's general operating fund.

SPEAKER_00 12:24

It requires just relentless calculation. And then you also have TAMIS, the training ammunition management information system, which tracks missiles in single units, and Syncata, a third-party payment system used to track transportation costs in flat monetary fees. Trevor Burrus, Jr.

SPEAKER_01 12:40

Gallons, units, and fees. All of it has to be converted, standardized, and mapped.

SPEAKER_00 12:45

The complexity of normalizing that data just cannot be overstated. But here's where it gets really interesting to me. Okay. We are

Securing The Data With Two Platforms

SPEAKER_00 12:52

talking about pulling an incredible amount of sensitive readiness and cost data into one centralized location. If an adversary gains access to this database, they don't just see a budget, right? They see exactly how much fuel we have, how many replacement parts are moving, and the exact operational readiness of our tank fleets.

SPEAKER_01 13:10

The gold mine of strategic intelligence.

SPEAKER_00 13:12

Exactly. So how does the government architect this to keep the data safe while actually letting analysts use it?

SPEAKER_01 13:18

That's a great question. The sources outline a very distinct two-platform architecture to solve that exact security puzzle. The actual EVAMP OSC backend, the engine room where all this messy data ingestion, wrangling, and storage happens, is hosted securely on Amazon GovCloud.

SPEAKER_00 13:36

Okay, Amazon GovCloud.

SPEAKER_01 13:37

Yes. And it is designated at Impact Level 4.

SPEAKER_00 13:40

Let's define that for the listener real quick. Impact Level 4 is a specific DoD security standard for controlled unclassified information. It means the data won't like reveal nuclear launch codes, but aggregated together, it reveals critical troop readiness, supply chain vulnerabilities, and strategic posture.

SPEAKER_01 13:57

Right. So the impact level four environment is the vault. Yeah. It is strictly controlled, meant primarily for the highly cleared CPE analysts who are managing the platform and writing the algorithms.

SPEAKER_00 14:06

But the broader DOD community still needs to see the results, right?

SPEAKER_01 14:09

You do. So to share this data safely, EDMPOPAS packages up the finished, sanitized cost profiles and pushes them over to a completely separate public-facing platform called Advana.

SPEAKER_00 14:19

Advana is like the storefront. The back-end factory makes the product and Advana puts it in the display window.

SPEAKER_01 14:25

Exactly. Advana hosts what the documents call the common Vemise tool. This separation of duties is really a brilliant administrative move.

SPEAKER_00 14:34

Because of the authority to operate, right?

SPEAKER_01 14:36

Yes. The authority to operate, which is the military's strict, formalized cybersecurity permission slip to plug a system into the network is a massive hurdle. By separating the platforms, the Bacape team doesn't have to manage the authority to operate or grant user access for every single military commander who just wants to view a readiness analytics dashboard.

SPEAKER_00 14:57

Oh, that's smart.

SPEAKER_01 14:58

Right. Advantage handles all the public-facing security protocols while the AvAMSE backend remains hidden, just quietly feeding it the clean processed data.

SPEAKER_00 15:07

But building a secure bridge between 75 siloed legacy systems and a modern cloud-based analytics platform, I mean, that requires an incredibly specialized workforce.

The Specialized Team Behind The Pipelines

SPEAKER_00 15:17

You cannot just hire a standard Silicon Valley software development team to execute this. The intense human requirements outlined in this contract are a testament to how difficult this is.

SPEAKER_01 15:27

The government is incredibly rigid about the key personnel required to run this project. For instance, the product manager must have a minimum of 10 years of experience relating to major program management.

SPEAKER_00 15:38

And the senior cost analyst requirement is even more intense. They need a master's degree in a math-heavy field like operations research, applied mathematics, industrial engineering, or economics. Plus, they need five years of experience specifically in DOD business cost analysis.

SPEAKER_01 15:54

What's fascinating here is the specific fusion of skills the government is demanding. Yeah. They need top-tier software engineers who understand how to build automated data pipelines in an Amazon GovCloud environment. But those engineers are useless unless they're paired with analysts who hold degrees in operations research.

SPEAKER_00 16:12

Which is the mathematical study of logistics and efficiency.

SPEAKER_01 16:16

Right. They need people who fundamentally understand army logistics, inflation indices, and cost estimating methodologies. Because if the engineers don't understand the mechanics of army supply chains, the automated business rules they code will output completely flawed data.

SPEAKER_00 16:31

Wow, yeah. And the physical working conditions for this team, they really reflect the extreme sensitivity of the project.

Physical Security Rules Down To Keys

SPEAKER_00 16:39

The physical security requirements in this contract keep this from feeling like a normal tech job.

SPEAKER_01 16:44

Oh, absolutely. Contractor employees are strictly forbidden from wearing clothing with their company logos, for example.

SPEAKER_00 16:50

No casual startup hoodies.

SPEAKER_01 16:51

Nope. They have to maintain a neat business casual appearance that blends in, ensuring they don't create the impression that they are government officials while walking the halls of the Pentagon or associated DOD facilities.

SPEAKER_00 17:04

And they all have to maintain secret facility clearances, which is a rigorous background check process. But the detail in the contract that really highlights the reality of government security work is the section on key control.

SPEAKER_01 17:18

Oh, the keys.

SPEAKER_00 17:19

It's wild. The contract explicitly states that contractors cannot duplicate keys. But if a contractor loses a master key, the government will step in, replace the entire lock system for that area, and deduct the total cost of replacing all those locks directly from the contractor's monthly payment.

SPEAKER_01 17:36

Which is incredibly expensive.

SPEAKER_00 17:37

Right.

SPEAKER_01 17:38

It proves that in the era of a hundred terabyte cloud architecture, the biggest vulnerability to the U.S. military is still a contractor misplacing a physical brass key.

SPEAKER_00 17:48

It's an absolute zero-tolerance policy for security breaches, whether they are digital intrusions or physical lapses. A compromised physical lock is treated with the exact same severity as a compromised cloud server.

SPEAKER_01 18:01

So what does this all mean?

What Transparency Could Change In War

SPEAKER_01 18:03

Why spend an entire deep dive dissecting a government request for proposal? Because whether you are a data scientist dealing with integration challenges, a project manager battling scope creep, or just someone fascinated by massive logistical puzzles, this Eve Ame document is a masterclass.

SPEAKER_00 18:19

It really is.

SPEAKER_01 18:20

It provides a real-time mechanical look at how a massive enterprise attempts to wrangle decades of fractured digital chaos into centralized, actionable intelligence.

SPEAKER_00 18:29

We've basically traced the complete operational journey today. It begins with a legal mandate from Congress demanding accountability for billions of dollars. Yep. That mandate spawns a hundred million dollar contractual framework designed to build a highly secure 100-terabyte relational database. And it culminates with elite data scientists writing complex algorithms to pull unadjusted ammunition and fuel receipts out of 75 different aging databases, normalizing the inflation rates and mapping them to specific M1 Abrams tanks. It is an unbelievable logistical and technical mountain to climb. But it leaves me with one final thought. We talked at the beginning about the true ongoing cost of owning a car, the oil, the tires, the unpredictable upkeep. Right. If the Evan Mosi project actually succeeds, and the DOD can instantly accurately track the exact true cost of every single bullet, every gallon of aviation fuel, and every mechanical repair hour tied to a specific vehicle, how might that unprecedented level of financial transparency fundamentally change the way future conflicts are budgeted, planned, and fought?

SPEAKER_01 19:39

When you remove the blind spot and eliminate the true cost of sustaining a military force, the strategic decisions regarding what equipment to buy and how to deploy it will inevitably shift.

SPEAKER_00 19:49

The lingering question to chew on as data continues to rewrite the rules of modern administration. Thank you for joining us on this deep dive. Keep exploring the hidden systems and massive databases that run our world, and we'll catch you next time.