Building the Network of Now: A Practical Guide to Defense Network Modernization

The answer isn’t rip­ping and replac­ing everything—it’s cre­at­ing what I call the “Net­work of Now” through intel­li­gent, incre­men­tal modernization.

The Current Reality Check

Let’s be hon­est about where we are. Crit­i­cal defense sys­tems still in use are writ­ten in COBOL or FORTRAN, and oper­at­ing decades-old hard­ware remains a crit­i­cal aspect of over­all defense oper­a­tions. Mean­while, we’re try­ing to deploy AI/ML capa­bil­i­ties for mis­sile defense and inte­grate space-based sen­sors that gen­er­ate ter­abytes of data per sec­ond. It’s like try­ing to stream 4K video through a dial-up modem.

The tra­di­tion­al approach—complete sys­tem replacement—isn’t just expen­sive; it’s dan­ger­ous. These lega­cy sys­tems work. They’re bat­tle-test­ed. What we need is a bridge between what we have and what we need.

Step 1: Embrace Hybrid Architecture (Not Replacement)

The Strat­e­gy: Cre­ate abstrac­tion lay­ers that enable old and new sys­tems to com­mu­ni­cate with­out requir­ing whole­sale replacement.

Why This Works: Finan­cial ser­vices faced this exact chal­lenge. Banks still run COBOL sys­tems that process tril­lions of trans­ac­tions, yet they offer mobile apps with real-time AI fraud detec­tion. They achieved this through API gate­ways and microser­vices that wrap lega­cy func­tion­al­i­ty in mod­ern interfaces.

For defense, this means cre­at­ing a “Lega­cy Inte­gra­tion Office” with­in each Pro­gram Exec­u­tive Office. These teams would devel­op stan­dard APIs that expose lega­cy sys­tem data with­out touch­ing the core code. Think of it as putting a uni­ver­sal trans­la­tor between sys­tems speak­ing dif­fer­ent languages.

The Rea­son­ing: Risk mit­i­ga­tion. By keep­ing sta­ble lega­cy sys­tems run­ning while adding mod­ern capa­bil­i­ties around them, we main­tain oper­a­tional con­ti­nu­ity while gain­ing new func­tion­al­i­ty. It’s evo­lu­tion, not revolution.

Step 2: Liberate the Data First

The Strat­e­gy: Before mod­ern­iz­ing sys­tems, mod­ern­ize data access. Extract infor­ma­tion from lega­cy silos into mod­ern data lakes where AI/ML can use it.

Why This Works: Data is the ammu­ni­tion for mod­ern war­fare. A mis­sile defense sys­tem needs to cor­re­late infor­ma­tion from hun­dreds of sen­sors in mil­lisec­onds. If that data is locked in COBOL sys­tems acces­si­ble only through batch process­es, we’ve already lost.

The approach is straight­for­ward: build extrac­tion pipelines that con­tin­u­ous­ly copy data from lega­cy sys­tems into mod­ern repos­i­to­ries. The lega­cy sys­tems con­tin­ue to run unchanged, but their data is now avail­able for advanced analytics.

The Rea­son­ing: Data lib­er­a­tion is a low-risk, high-reward approach. It does­n’t require chang­ing oper­a­tional sys­tems, yet it enables trans­for­ma­tion­al capa­bil­i­ties. It’s like installing a win­dow in a bunker—you don’t com­pro­mise the struc­ture, but sud­den­ly you can see outside.

Step 3: Overlay Modern Networks (Don’t Replace Infrastructure)

The Strat­e­gy: Use soft­ware-defined net­work­ing to cre­ate vir­tu­al mod­ern net­works on top of exist­ing infrastructure.

Why This Works: Telecom­mu­ni­ca­tions providers faced sim­i­lar chal­lenges tran­si­tion­ing from cir­cuit-switched to pack­et-switched net­works. They could­n’t replace every­thing overnight, so they built over­lay net­works that grad­u­al­ly took over traffic.

For the DoD, this means imple­ment­ing dual-stack oper­a­tions that sup­port both IPv4 and IPv6, deploy­ing trans­la­tion gate­ways at net­work edges, and uti­liz­ing Soft­ware-Defined Net­work­ing (SDN) to cre­ate flex­i­ble, pro­gram­ma­ble net­works regard­less of the under­ly­ing hardware.

The Rea­son­ing: Net­work infra­struc­ture is expen­sive and mis­sion-crit­i­cal. By over­lay­ing mod­ern capa­bil­i­ties, we can achieve next-gen­er­a­tion func­tion­al­i­ty with­out the risk and cost of phys­i­cal replace­ment. It’s like adding express lanes to an exist­ing high­way rather than build­ing an entire­ly new road.

Step 4: Deploy AI/ML as a Force Multiplier (Not a Replacement)

The Strat­e­gy: Imple­ment AI/ML capa­bil­i­ties as “side­car” ser­vices that aug­ment human deci­sion-mak­ing rather than replac­ing exist­ing systems.

Why This Works: The most suc­cess­ful AI imple­men­ta­tions enhance rather than replace. Con­sid­er how Tes­la’s autopi­lot assists dri­vers rather than replac­ing them. For defense appli­ca­tions, AI should pro­vide deci­sion sup­port, pat­tern recog­ni­tion, and pre­dic­tive ana­lyt­ics while humans retain ulti­mate control.

Start with non-crit­i­cal appli­ca­tions, such as pre­dic­tive main­te­nance, and progress to logis­tics opti­miza­tion. Then, care­ful­ly move into oper­a­tional sup­port. Each step builds con­fi­dence and capability.

The Rea­son­ing: Trust is earned incre­men­tal­ly. By demon­strat­ing AI’s val­ue in low-risk areas first, we estab­lish the orga­ni­za­tion­al con­fi­dence nec­es­sary for mis­sion-crit­i­cal appli­ca­tions. It also allows us to devel­op the human-machine team­ing skills essen­tial for future warfare.

Step 5: Reform Acquisition to Incentivize Modernization

The Strat­e­gy: Devel­op new con­tract vehi­cles that reward incre­men­tal improve­ments and facil­i­tate con­tin­u­ous modernization.

Why This Works: Tra­di­tion­al defense con­tracts assume a fixed end-state. But mod­ern­iza­tion is a jour­ney, not a des­ti­na­tion. We need “Mod­ern­iza­tion as a Ser­vice” con­tracts that pay for outcomes—reduced laten­cy, increased avail­abil­i­ty, improved security—rather than spe­cif­ic technologies.

Include pro­vi­sions for sole-source bridges dur­ing tran­si­tions, rapid acqui­si­tion for inte­gra­tion tools, and shared sav­ings mod­els where con­trac­tors ben­e­fit from the effi­cien­cy improve­ments they create.

The Rea­son­ing: Cur­rent acqui­si­tion reg­u­la­tions were designed for hard­ware pro­cure­ment, not soft­ware evo­lu­tion. By align­ing incen­tives with mod­ern­iza­tion goals, we moti­vate the indus­try to invest in cre­ative solu­tions rather than pro­tect­ing incum­bent positions.

Step 6: Organize for Success

The Strat­e­gy: Cre­ate ded­i­cat­ed mod­ern­iza­tion lead­er­ship with real author­i­ty and bud­get control.

Why This Works: Mod­ern­iza­tion efforts typ­i­cal­ly fail due to orga­ni­za­tion­al antibodies—the peo­ple and process­es that resist change. By estab­lish­ing a Chief Mod­ern­iza­tion Offi­cer with bud­get author­i­ty and cre­at­ing cross-func­tion­al teams, we ensure a sus­tained focus and allo­ca­tion of resources.

Equal­ly impor­tant is work­force devel­op­ment. The weapon sys­tems based on either COBOL or FORTRAN aren’t just obsolete—they are also poor­ly doc­u­ment­ed. Part­ner with mod­ern devel­op­ers to cap­ture that knowl­edge while build­ing new systems.

The Rea­son­ing: Tech­nol­o­gy prob­lems are peo­ple’s prob­lems. Suc­cess requires chang­ing cul­ture, incen­tives, and orga­ni­za­tion­al struc­tures. With­out this human ele­ment, even the best tech­ni­cal solu­tions will fail.

The Path Forward: Start Now, Start Small, Scale Fast

The Net­work of Now isn’t about hav­ing the newest tech­nol­o­gy everywhere—it’s about mak­ing our cur­rent capa­bil­i­ties work togeth­er while build­ing tomor­row’s foun­da­tion. Every day, we delay makes the chal­lenge hard­er and our adver­saries stronger.

Start with pilot pro­grams that demon­strate val­ue. Pick a sin­gle crit­i­cal sys­tem and show how mod­ern inte­gra­tion can enhance its capa­bil­i­ties with­out replace­ment. Use that suc­cess to build momen­tum for broad­er initiatives.

The Gold­en Dome mis­sile defense sys­tem exem­pli­fies why this mat­ters. We can’t wait for per­fect infra­struc­ture to defend against hyper­son­ic threats. We need to lever­age what we have while build­ing what we need. That’s the essence of the Net­work of Now—pragmatic mod­ern­iza­tion that deliv­ers capa­bil­i­ty today while prepar­ing for tomorrow.

The ques­tion isn’t whether to modernize—it’s how to mod­ern­ize intel­li­gent­ly. By fol­low­ing this roadmap, we can trans­form defense net­works from lia­bil­i­ty to advan­tage, ensur­ing our warfight­ers have the tools they need when they need them.

June 15, 2025

Posted in DOD.