This bill amends Section 355(c)(2)(A) of the National Defense Authorization Act for Fiscal Year 2022 to add a requirement that the annual report on the Navy Shipyard Infrastructure Optimization Program (SIOP) describe “the incorporation of digital infrastructure (including hardware, software, and cloud storage) and platforms.” The change is limited to the content of the report; it does not itself appropriate funds or create new procurement authority.
The practical effect is to force program managers and Navy leadership to document plans and progress on digital elements of shipyard modernization—everything from sensors and maintenance software to cloud data stores and enterprise platforms. For practitioners, that means oversight will increasingly examine digital readiness, cybersecurity posture, data architectures, and how digital investments are planned and justified alongside physical recapitalization work.
At a Glance
What It Does
The bill inserts a new phrase into the statutory description of the SIOP annual report, requiring discussion of how digital infrastructure and platforms—explicitly including hardware, software, and cloud storage—are being incorporated into shipyard modernization efforts. It modifies the statutory reporting content only.
Who It Affects
Navy SIOP program offices, naval shipyard managers, NAVSEA and other Navy acquisition organizations, defense contractors that supply digital systems or integrate them into yard projects, and congressional oversight committees that review the annual report.
Why It Matters
Shipyard modernization increasingly relies on digital systems for maintenance, scheduling, and logistics; the change pushes digital factors into formal oversight and planning. That will affect acquisition strategies, budgeting discussions, cybersecurity expectations, and contractor deliverables tied to SIOP projects.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill makes a single, targeted change to the SIOP annual reporting requirement by inserting language that expressly requires the report to address digital infrastructure and platforms. The statutory phrase lists hardware, software, and cloud storage as examples, which broadens the report’s scope beyond physical facilities to include digital assets that support shipyard operations.
Because the amendment applies only to report content, it does not by itself allocate funding or create new acquisition authorities. Instead, it creates an expectation that Navy leaders will inventory and describe digital elements—how they will be used, how they integrate with physical upgrades, and how they will be secured and maintained.
In practice, authoring the expanded report will require coordination among program managers, IT leads, cybersecurity personnel, and contracting officers.The change is likely to surface planning questions that were previously implicit: whether shipyard upgrades include integrated sensors and condition-based maintenance systems, how maintenance data is stored and shared (including cloud solutions), whether enterprise platforms will be adopted for scheduling and supply-chain management, and what workforce training is planned. The provision therefore converts digital modernization from a technical implementation detail into a topic for congressional oversight and program-level justification.
The Five Things You Need to Know
The bill amends Section 355(c)(2)(A) of the NDAA for Fiscal Year 2022 (10 U.S.C. 8013 note) to require the SIOP annual report to discuss “the incorporation of digital infrastructure (including hardware, software, and cloud storage) and platforms.”, The statutory change is limited to reporting content — it does not appropriate money, change procurement authorities, or mandate specific technical solutions.
By naming hardware, software, and cloud storage, the insertion signals congressional interest in both edge devices/sensors and centralized data services as part of shipyard modernization.
Producing the expanded report will require cross-functional inputs (program management, IT, cybersecurity, contracting), increasing administrative workload on SIOP program offices.
The amendment raises oversight levers: congressional reviewers will now have a formal basis to evaluate digital readiness, data plans, and cybersecurity posture in SIOP submissions.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Textual amendment to SIOP annual reporting requirement
This single-line amendment inserts the phrase about digital infrastructure and platforms into the existing statutory description of the SIOP annual report. The practical legal effect is narrow: the statute governing report content now explicitly includes digital matters. That placement means the obligation flows to whoever is already responsible for assembling the SIOP report under Section 355.
Where the requirement sits in the law
The amendment modifies a note to 10 U.S.C. 8013 that was created by the FY2022 NDAA. Because it is an amendment to report language in an NDAA note rather than to an appropriations section, the change clarifies congressional intent for oversight without altering budgetary mechanics. Agencies will treat this as a compliance item when preparing the annual SIOP submission to Congress.
What program offices must provide and coordinate
Program offices will need to describe plans for incorporating digital hardware (sensors, diagnostic equipment), software (maintenance management systems, analytics), cloud storage, and platforms (enterprise or industrial platforms used to run yard operations). That means consolidating inputs from IT leads, cybersecurity staff, facility engineers, and contractors into a single narrative and likely attaching technical annexes or roadmaps to satisfy reviewers.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Congressional oversight committees — Gain a clearer, statutory basis to evaluate digital aspects of shipyard modernization, improving the ability to ask for details on data, cybersecurity, and integration.
- Navy program managers and planners — Receive an opportunity to align digital modernization with SIOP funding and to justify digital investments within an established oversight document.
- Defense contractors and systems integrators — Firms that supply digital systems (software vendors, cloud service providers, integrators) gain a clearer path to be included in SIOP projects as their capabilities become part of documented program plans.
Who Bears the Cost
- Navy SIOP program offices — Must absorb additional reporting responsibilities and coordinate cross-functional inputs, increasing administrative time and potentially requiring new staff or contractor support.
- Naval shipyards and internal IT organizations — Face pressure to produce maturity assessments, data inventories, and modernization plans that could reveal capability gaps and trigger additional work.
- Small and specialized contractors — May incur upfront investment to meet new expectations for cloud, platform, or cybersecurity capabilities if those become de facto requirements for participation in SIOP-related procurements.
Key Issues
The Core Tension
The bill reflects a legitimate demand for transparency about digital modernization, but requiring descriptive reporting without corresponding funding, standards, or clear security boundaries forces program offices to choose between useful candor and operational prudence — and creates pressure to turn oversight-driven reporting into a proxy for policy and procurement decisions that the statute does not itself make.
The statute changes only the content of an annual report, not funding or acquisition rules, which creates a core implementation puzzle: reporting will highlight digital needs without delivering immediate resources to meet them. That can produce a ‘want list’ effect where oversight exposes capability gaps but requires separate budget or procurement actions to close them.
Program offices may respond by documenting aspirational plans rather than concrete, funded roadmaps.
Another tension arises around sensitive information. The bill’s public reporting requirement risks forcing programs to choose between transparency and operational security.
Detailed disclosures about sensors, network architectures, cloud providers, or platform interconnections could reveal vulnerabilities; agencies will need to determine what belongs in an unclassified report and what must remain classified or redacted. Finally, the statutory language is broad and undefining—terms like “platforms” and “incorporation” are open to interpretation, which will produce variation across reports and complicate congressional comparisons unless the Navy adopts internal reporting standards.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.