GovCon Bid and Proposal Insights

Information Technology Program Management Support (ITPMS)

BidExecs

Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.

0:00 | 19:35

In this episode, we break down the upcoming Single BPA for Information Technology Program Management Support (ITPMS) with the Department of Homeland Security - U.S. Immigration and Customs Enforcement (ICE). With an anticipated value of $50M–$100M and a Full & Open competition, this opportunity covers enterprise IT portfolio management, governance, financial oversight, acquisition management, scheduling, and PMO support for HSI systems.

Listen now to understand the scope, competition landscape, and how to prepare before the solicitation drops.

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

Stakes Of HSI’s Digital Nerve

SPEAKER_01

I want you to imagine uh just a really specific kind of pressure. You are responsible for the digital nervous system of a massive federal law enforcement agency. Right. And we aren't talking about, you know, uh a startup selling coffee subscriptions here. We are talking about Homeland Security investigations, HSI. Yeah. These are the people tracking cross-border criminal organizations, terrorists, money launderers. The stakes are quite literally life and death.

SPEAKER_00

Trevor Burrus, Jr.: It is a high-stakes environment. Absolutely. I mean, if the system goes down, investigations stall. Evidence doesn't get tracked.

SPEAKER_01

Exactly.

SPEAKER_00

And uh bad actors might slip through the cracks. It's not just an inconvenience.

SPEAKER_01

Trevor Burrus, Jr.: Right. So you have this massive responsibility, but then you look at your to-do list for the day. Item one, develop a strategy for artificial intelligence and machine learning to catch cartels. Sure. Item two, go down to the supply closet and make sure there are enough toner cartridges for the printer. Trevor Burrus, Jr.

SPEAKER_00

And item three, uh write a script for a congressional testimony and then immediately after that update the office seating chart because someone moved to a different cubicle.

SPEAKER_01

It's that is the wild, completely contradictory world we are diving into today.

SPEAKER_00

It really is.

SPEAKER_01

Welcome to the deep dive. We are looking at a solicitation document today titled ITPMS Higher Level Requirements. It is basically this massive help-wanted sign posted by HSI.

SPEAKER_00

Aaron Powell Yeah, and they need a contractor to come in and run, well, almost everything involved in their IT infrastructure. Trevor Burrus, Jr.

SPEAKER_01

And when we say run, we mean it in the absolute broadest possible sense. The mission for this deep dive is to unpack this document because it outlines a roadmap for HSI to move from a very traditional IT setup to this flexible, mobile future.

SPEAKER_00

Aaron Powell Using an agile-driven approach, quote unquote. Trevor Burrus, Jr.

SPEAKER_01

Right. But it exposes the tension at the heart of modern government work.

The Massive Help‑Wanted Blueprint

SPEAKER_00

Aaron Powell Oh, perfectly. On one side, you have this desperate need to be agile and futuristic, and on the other side, you have the crushing weight of bureaucracy, paperwork, and these physical legacy processes that just won't die.

SPEAKER_01

Aaron Powell We are going to explore the specific systems involved, uh the bureaucratic hurdles, and this really surprising mix of high-tech strategy and low-tech administrative duties.

SPEAKER_00

It's a survival guide for the federal contractor, essentially.

SPEAKER_01

So let's start with the landscape. What is the actual stuff this contractor is going to be responsible for? The document mentions the HSI portfolio. Can you give us the lay of the land?

SPEAKER_00

Yeah, so it's a huge footprint. The document explicitly highlights three major acquisition oversight list investments.

SPEAKER_01

M-A-O-L.

SPEAKER_00

Right. In government speak, these are level two investments. That means they are big money, high risk, and they get a ton of scrutiny from the top.

SPEAKER_01

Okay. Walk us through these big three.

SPEAKER_00

First, you have Tech-S modernization.

SPEAKER_01

Chex S.

TekS, SEVIS, And Raven Defined

SPEAKER_00

Yeah. TechS. This is the bread and butter. It's defined in the text as investigative case management. Basically, every agent working a case is likely interacting with this system.

SPEAKER_01

So it's the filing cabinet.

SPEAKER_00

It's the digital filing cabinet, but much, much smarter. Then you have SEVIS. That's the student and exchange visitor system.

SPEAKER_01

Okay, I've heard of that one.

SPEAKER_00

Most people have. This tracks millions of non-immigrants entering the country for school or exchange programs. It's massive.

SPEAKER_01

Those sound like very established, steady ships. Yeah. Big, heavy, but they're moving. But then there's the third one on this level two list, Raven.

SPEAKER_00

Ah, yes, Raven. I mean, the name alone sounds cooler than the others.

SPEAKER_01

It does. It stands for the repository for analytics in a virtualized environment.

SPEAKER_00

It sounds like a secret weapon.

SPEAKER_01

And in a way, it is a secret weapon. This is the analytics arm. This is where they take all that data and try to find patterns, connections, threats. But here is the catch.

SPEAKER_00

Okay.

SPEAKER_01

And the document is very specific about this. Raven is essentially the problem child.

SPEAKER_00

Aaron Ross Powell How so? What makes it the problem child?

SPEAKER_01

The text notes that Raven is the only program among these major three that has not achieved AD3.

SPEAKER_00

Okay, stop right there. We need to unpack ADE3 because I see that acronym a lot in these government docs. What does it actually mean for the people doing the work on the ground?

SPEAKER_01

Think of ADE3 Acquisition Decision Event 3 as the bar exam for a piece of software.

SPEAKER_00

The bar exam.

SPEAKER_01

Yeah. Until you pass ADE3, you aren't really a lawyer. You're still a student. You're an experiment.

Raven Vs. ADE3 And The Valley

SPEAKER_00

Got it. In government terms, ADE3 is the green light for full production and deployment. It means the system is stable, the costs are known, and it is ready for prime time.

SPEAKER_01

And Raven hasn't passed the bar exam yet.

SPEAKER_00

No. And that is incredibly dangerous territory for a government program. There is something in the defense and tech industry called the Valley of Death.

SPEAKER_01

The Valley of Death sounds ominous.

SPEAKER_00

It is. It's where software projects go to die because they burn through all their development money, but they never quite get the approval to actually launch and become permanent. The fact that Raven hasn't hit ADE3 means it is stuck right in that high pressure zone.

SPEAKER_01

And the document mentions it requires a dedicated support team. That reads to me like they are calling in the paramedics.

SPEAKER_00

Or the special forces. They need a team specifically to push this thing over the finish line because analytics is so much harder than just case management.

SPEAKER_01

Right, because it's not just storing files.

SPEAKER_00

Exactly. It's abstract, it's virtualized. Proving that an analytics tool works reliably is much harder than proving a standard database works. So the contractor walking into this isn't just maintaining servers, they are walking into a rescue mission for a critical national security asset.

SPEAKER_01

And just to add scale to this, the document also mentions there are about 10 smaller level three IT system investments as well. So it's a massive portfolio.

SPEAKER_00

Oh, yeah, it's not just the big three.

SPEAKER_01

That sets the stakes pretty high. You have this rescue mission on one hand, but then you have the overall philosophy of the contract. The document talks heavily about agile and this new mobility initiative.

SPEAKER_00

This is where the cognitive dissonance really kicks in for me. The document explicitly demands an agile-driven approach for all these services.

Agile Dreams Meet Waterfall Rules

SPEAKER_01

Now, agile is one of those words that has almost lost all meaning because corporate folks use it for everything. But in software development, it actually means moving fast, iterating, breaking things to fix them quickly.

SPEAKER_00

Exactly. Agile is entirely about speed and flexibility. But the federal acquisition process, the actual rules for buying things and building things, is designed for the exact opposite. Right. It's designed for what we call waterfall. It wants you to plan every single detail five years in advance and never deviate from the plan.

SPEAKER_01

So this document is essentially asking the contractor to be agile, to sprint, while wearing the concrete shoes of federal regulation.

SPEAKER_00

That's a great way to put it.

SPEAKER_01

And it's not just software, they want mobility in the physical workplace too. I was reading the section on the mobility initiative. It says the contractor isn't just maintaining servers, they are expected to lead the change towards a long-term mobility workplace.

Mobility As Cultural Revolution

SPEAKER_00

It's incredibly ambitious. They don't just want IT support. They want a cultural revolution within HSI. They want the contractor to help place the agency as the leader among federal agencies at transforming workspaces.

SPEAKER_01

They want agents to be able to work from anywhere, collaborate seamlessly, use advanced information technology on the fly, maximize flexibility. But let's pause for a second. Can an outside IT contractor actually change the culture of a federal agency? That feels a bit like asking the plumber to redesign the architecture of your entire house while he's under the sink fixing a pipe.

SPEAKER_00

It is a massive ask. And frankly, it puts the contractor in a really tough spot. They have to push for this forward-leaning, flexible future, but they don't have the actual authority of the agency director.

SPEAKER_01

They're just the hired help.

SPEAKER_00

Exactly. They have to influence without authority. And they have to do it while managing the governance and financials of the agency, which, as we'll see, are arguably the least flexible things on earth.

SPEAKER_01

Aaron Powell Okay, let's get into the actual meat of the contract then. We've got the dream here: mobility, agile, saving Raven. Now, what are the day-to-day obstacles? The document breaks the work down into eight distinct task areas.

SPEAKER_00

Aaron Powell Yes, eight tasks.

SPEAKER_01

Let's focus on the most interesting contrasts here. Task one and two are portfolio and strategic planning.

Eight Tasks, One Contradiction

SPEAKER_00

Aaron Powell Right. And this is where they ask for the innovation. They want data analytics, automation, machine learning. They want the contractor to drive open source adoption. It reads like a very Silicon Valley wish list.

SPEAKER_01

Aaron Powell But then right in the middle of this high-tech Silicon Valley wish list, there is a requirement that literally stopped me cold. I had to read it twice to make sure I wasn't hallucinating.

SPEAKER_00

Oh, I know exactly what you say. The catalog.

SPEAKER_01

The catalog. The requirement states they need to develop and print an annual IT catalog. Specifically, it says at least 25 professionally bound and printed books.

SPEAKER_00

With an option for quantities up to 75.

SPEAKER_01

Wait, just run that by me again. 25 physical printed books. In 2026, we just talked about leading the federal government in mobility and digital transformation. Why on earth are we professionally binding a physical book?

The Printed IT Catalog Surprise

SPEAKER_00

It is the perfect symbol of the government straddle. You have the mobility goal, this digital future, but you have to ask who is actually reading this physical catalog. It's likely senior leadership. Or maybe congressional overseers, or perhaps people who simply like to hold a physical object during a budget meeting.

SPEAKER_01

It has to be professionally bound. You can't just staple it in the break room. That suggests to me it's a prop. It's political theater.

SPEAKER_00

It's legitimacy. In the government, if it's just a PDF on a screen, it feels temporary. If it's bound in leather or heavy cardstock, it's real. It's official. So the contractor has to be cutting edge enough to design an AI strategy, but old school enough to know a really good print shop.

SPEAKER_01

It's hilarious, but it's also kind of sad. It shows that the culture change they desperately want hasn't actually happened yet at the very top. They still want the paper.

SPEAKER_00

Precisely. And if you think the printed book is rigid, look at task three integrated governance. This involves managing something called the storefront.

SPEAKER_01

Yeah, they call it the HSI Governance Board Storefront on SharePoint. What is the actual function of this storefront?

Governance Storefront As Gatekeeper

SPEAKER_00

It's the ultimate gatekeeper. Imagine you're an investigator and you find a cool new open source app that helps you map out financial transactions. You can't just download it to your government laptop. You have to submit an intake request. The contractor manages this entire storefront process. They have to validate your request, conduct assessments of the as is business process versus your proposed-to-be solution, and decide if it fits the enterprise architecture.

SPEAKER_01

So they're essentially the bouncers of the IT club.

SPEAKER_00

They are the bouncers. You're not getting in with those shoes. And they are also the accountants. Which brings us to task four, financial management. And this is where that agile dream we talked about really goes to die.

SPEAKER_01

I saw the acronyms in this section. EVM, CPIC? It looks like a tax audit on steroids.

EVM, Budgets, And Exhibit 300

SPEAKER_00

It is so much worse than a tax audit. Let's talk about EVM, earned value management. To the uninitiated, this just sounds like tracking a budget, but is an incredibly aggressive mathematical framework.

SPEAKER_01

How so? Give me an example.

SPEAKER_00

Okay, imagine you hire a contractor to build a deck in your backyard. Two weeks in they come to you and say, hey, we've spent 50% of the budget. You might naturally assume the deck is 50% done.

SPEAKER_01

That would be the logical assumption, yeah.

SPEAKER_00

But in reality, maybe they just bought all the premium wood and haven't cut a single board yet. They've spent the money, but they haven't actually earned the value of that money in completed work. EVM is designed to catch exactly that discrepancy. Oh wow. It forces the contractor to prove, with hard data, that the physical work completed precisely matches the dollars burned.

SPEAKER_01

So it's basically a lie detector test for the project manager.

SPEAKER_00

Exactly. And the document requires this level of tracking for the entire MAOL portfolio. The contractor has to run these EVM calculations constantly. If you deviate too much from your baseline, you trigger a breach. Then you have to write a formal corrective action plan. It is a massive administrative burden.

SPEAKER_01

And all this financial tracking feeds into something called the OMB Exhibit 300, right?

Cost Models And Funding Risk

SPEAKER_00

Yes. The Exhibit 300, that is the life or death document for these systems. Every year, major investments like Raven or Tekkenos would have to submit a massive business case to the Office of Management and Budget, the OMB. That's the White House, basically. Right. If that exhibit 300 is weak or the EVM numbers don't add up, Congress can just cut the funding.

SPEAKER_01

So the contractor isn't just counting the beans, they are writing the legal argument for why the program should even continue to exist.

SPEAKER_00

Yes. They are the defense attorneys for the program's budget. The document says they have to use ACT modeling to create life cycle cost estimates, LCCEs.

SPEAKER_01

AC modeling.

SPEAKER_00

It's a specialized cost estimating tool. They have to predict, with mathematical certainty, what a complex system like Raven will cost to run in the year 2030. Every dollar obligated or expensed has to be tracked. If they get the estimate wrong, the program could be completely defunded.

SPEAKER_01

If you think about it, that feels like a huge conflict of interest. The contractor is getting paid to support the program, but they are also the ones generating the data that proves the program is working to the government.

SPEAKER_00

Welcome to Federal Contracting. It is a self-reinforcing ecosystem. But the rigor required here, the sheer amount of paperwork to justify every single dollar, is exactly what makes Agile so hard.

SPEAKER_01

Because you're locked in.

SPEAKER_00

You're completely locked in. You can't just pivot to a brilliant new idea next week if you've already locked your life cycle cost estimate into an exhibit 300 for the next fiscal year.

D‑102, Documents, And Oversight

SPEAKER_01

So we have the visionaries in task one, the bouncers in task three, and the defense attorneys in task four. Now let's talk about the pure bureaucracy. Tasks five and six cover acquisition and program management. This seemed to be where the alphabet soup got the thickest.

SPEAKER_00

Oh, it is incredibly dense. We talked about achieving ADE3 for Raven earlier. To get there, you need to generate a literal mountain of documents. The document lists ITARs, which are IT acquisition requests, BWS balanced workforce services, acquisition program baselines.

SPEAKER_01

And D-102 documents. What is D-102?

SPEAKER_00

D102 is the Department of Homeland Security's specific acquisition instruction. It is the rulebook. It dictates every single step of buying something or building a system. If the contractor misses one step in the D-102 process, the purchase is invalid.

SPEAKER_01

It's like playing a board game where if you roll the dice wrong, you go straight to jail.

SPEAKER_00

Or at least you get a very angry, very public letter from the Government Accountability Office.

SPEAKER_01

Which is terrifying. And speaking of oversight, Task 6 mentions that the contractor assists with responding to congressional inquiries and GAO requests.

SPEAKER_00

And preparing congressional testimony.

SPEAKER_01

Yes, that one really stood out to me.

SPEAKER_00

It should. Think about the chain of command here. You are a contractor employee, you might be a consultant three years out of college, and you are drafting the highly technical briefing points that the director of HSI is going to read aloud to a Senate subcommittee to explain why they spent$50 million on a database.

SPEAKER_01

You are effectively the voice of the agency.

SPEAKER_00

You are the ghostwriter for the agency. You have to translate the techno reality like, hey, the server is crashing because the legacy code is terrible into political speak. Like we are currently optimizing the infrastructure for greater mission resilience.

SPEAKER_01

That is a very distinct skill set. It's not IT, it's high-level political communications.

SPEAKER_00

It really is. And that's what makes this help-wanted ad so unicorn-like. They want a tech wizard, a forensic accountant, a lawyer, and a speechwriter all rolled into one contract.

SPEAKER_01

And an office manager.

SPEAKER_00

Yes. We have to talk about Task 8, administrative support.

Task Eight: Toner And Seating Charts

SPEAKER_01

This is hands down my favorite part of the entire document because after all the high-flying talk about AI strategies and mobility initiatives and saving Raven from the valley of death, Task 8 brings us crashing right back down to Earth.

SPEAKER_00

It absolutely does. The human element, procuring office consumables. Specifically, it lists copier paper and printer cartridges.

SPEAKER_01

It is such a jarring shift in tone. I can just picture the morning meeting. Okay, team, fantastic job on the congressional testimony regarding our neural network architecture. Now, who ordered the cyan toner? Because the printer is blinking again.

SPEAKER_00

It highlights the gritty reality of program management support. You aren't just the brain of the operation, you are the hands. The document explicitly mentions managing seating charts. It mentions maintaining physical inventory records.

SPEAKER_01

Seating charts.

SPEAKER_00

Yes, seating charts. If a new federal employee gets hired, the contractor has to figure out what cubicle they sit in. They effectively run the office. From the high-level strategy down to taking the meeting minutes.

SPEAKER_01

Does this worry you at all? I mean, just from a pure focus perspective.

SPEAKER_00

It absolutely does. If I'm HSI and I am paying a massive premium for a specialized contractor to modernize my Craigle investigative systems, do I really want that same expensive expertise worrying about seating charts and printer paper? It feels like a massive dilution of focus.

Synthesis And The Central Tension

SPEAKER_01

It also feels like a trap for the contractor on the ground. You can deliver the best AI strategy in the federal government, but if the boss runs out of paper right before a big meeting, that is what they are going to remember.

SPEAKER_00

That is the ultimate customer service aspect of IT. The printer is always the most visible failure. But it really brings us back to that central tension we started with. The document asks the contractor to transform the workspace into this mobile digital utopia. But it also explicitly requires them to maintain the physical, paper-based reality of the current office.

SPEAKER_01

They have to build the future while keeping the past on life support and supplying the copier paper for the past to live on. So as we wrap this up, let's synthesize this for a second. If you are listening to this, and maybe you work in a big organization, you probably recognize some of this chaos. What is the main takeaway here?

SPEAKER_00

The main takeaway is that modernization in a massive government agency is incredibly messy. It is never a clean switch from old to new. It is a very messy, overlapping process. You have Raven, the future, struggling to be born and pass ADE3. You have Tex, the legacy system, doing the heavy lifting every day.

SPEAKER_01

Right.

SPEAKER_00

And you have the contractor stuck right in the middle, trying to use agile methods in a strict waterfall world, writing checks with EVM math and binding physical books to prove they are doing a good job.

Mobility’s Paradox And Closing

SPEAKER_01

It sounds like a job that requires a very specific kind of masochism to succeed at.

SPEAKER_00

Or just a really, really high tolerance for irony.

SPEAKER_01

I want to leave you, our listener, with a final thought about that mobility initiative. We started by pointing out that HSI wants to be the leader among federal agencies in workspace transformation.

SPEAKER_00

Right, the forward-leaning mobile workplace.

SPEAKER_01

But looking at task eight, the paper, the seating charts, the physical inventory, it raises a bigger question for me. In any large transformation, does the sheer weight of legacy process inevitably slow down the vision of the future? Like, can you ever truly be mobile and agile when your contract literally requires you to be the anchor for the physical office?

SPEAKER_00

That's the real challenge. If the contractor does their job perfectly and makes everyone completely mobile, nobody needs a seating chart. Nobody needs printer paper. But the contract requires them to manage those things. So in a strange way, the contract incentivizes keeping the physical office alive even while it tells them to kill it.

SPEAKER_01

The contract fights itself.

SPEAKER_00

It fights itself, and the winner of that fight will determine if HSI actually gets its futuristic renovation or if they just get a fresh coat of paint and a really well stocked supply closet.

SPEAKER_01

And 25 professionally bound books to read in the lobby while they wait. Thanks for taking this deep dive with us.

SPEAKER_00

Always a pleasure.