Skip to main content
by learnformula
Explore courses
search
For Business
Team license & compliance management
For Higher Education
Academic partnerships
For Government Agencies
Government training solutions
For Instructors & Course Creators
Teach on our marketplace
Become a Sponsor
Reach professionals where they learn
Log inStart 7-Day Free TrialStart Free TrialStart Free Trial
search
Explore courses
arrow_backBack to Latest Intelligence

Verification Moves Upstream: What Siemens' Raleigh Skid Plant, a Brooklyn Collapse, and Five Other Signals Mean for U.S. Engineering Accountability

David Miller•Nov 19, 2026•
9 min read
Share
SIGN UP AND GET
10% OFF
Sign up for our newsletter and get 10% off your next purchase!
By subscribing, I agree to LearnFormula's email marketing. I can unsubscribe anytime. See Privacy Policy.

The most expensive engineering failures rarely start with a bad calculation. They start in the gap between what was approved on paper and what gets built, assembled, or tested in the field. This week's news puts that gap under a sharp light, from a new Siemens factory in Raleigh that pulls power equipment testing indoors to a Brooklyn collapse that forensic engineers are now picking apart.

Taken together, this set of developments points to a single shift. Verification is moving upstream, away from the job site and toward controlled environments, documented plans, and code-level decisions. For U.S. engineers, that shift changes where liability, quality, and schedule risk actually sit.

Factory Testing Comes to Power Infrastructure

Siemens has opened a power infrastructure facility in Raleigh, North Carolina, where the integration and testing of medium-voltage power skids now take place in a controlled engineering and manufacturing environment. A skid is a pre-assembled package of switchgear, transformers, controls, and related equipment that is designed to be delivered as a unit and connected on site.

The logic behind this model is straightforward. Every hour of troubleshooting that happens in a factory is an hour not spent on a energized site with a constrained crew and a tight outage window. For data centers, substations, and industrial plants, where power commissioning often sits on the critical path, the factory test is becoming the first real proof that the design works as a system.

For engineers, this has three practical consequences:

  • Interface definition matters more. Skids only work when electrical, mechanical, and controls boundaries are specified precisely before fabrication begins.
  • Commissioning plans start earlier. Factory acceptance testing protocols need to be written alongside the design, not after it.
  • Site engineers inherit a different job. Their work shifts toward verifying connections, foundations, and installation tolerances rather than debugging integrated equipment.

When Approved Plans Meet Real Sites

If the Raleigh story shows verification moving indoors, the Brooklyn collapse investigation shows what happens when it does not. Forensic engineers and local regulators are examining excavation designs and site conditions, and early findings point to critical gaps between approved engineering plans and on-site execution.

Excavation is one of the most unforgiving phases of any project. Shoring, underpinning, dewatering, and soil assumptions all depend on conditions that can differ from what was modeled. An approved drawing shows intent. It does not guarantee that the crew in the trench is working from the same assumptions, or that field changes were reviewed by the engineer of record.

The core question in the investigation is not whether the design existed, but whether it was carried out as designed, and whether anyone was checking.

Engineers should treat this as a prompt to review their own field-verification systems. Key questions include:

  1. Are the assumptions behind excavation and shoring designs documented in a form the field team can actually read and check?
  2. Who has authority to stop work when observed soil or groundwater conditions diverge from the geotechnical report?
  3. Is every field change logged, reviewed, and sealed when it affects structural or geotechnical performance?
  4. Are inspection hold points tied to specific design assumptions, rather than to calendar milestones?
Key Takeaway: A stamped plan is only the starting point of accountability. Engineers who can show that design assumptions were verified against site conditions, and that changes were controlled, are the ones best positioned to defend their work when something goes wrong.

Megaprojects Are Still Being Bought, Built, and Rebuilt

While verification practices tighten, the capital pipeline keeps moving. Several recent awards and completions show how large projects are being structured and delivered.

At Washington's airports, the Metropolitan Washington Airports Authority selected Jacobs and TYLin to oversee major infrastructure and facility upgrades at Washington Dulles International Airport and Ronald Reagan Washington National Airport. Reported as a roughly $150 million contract, the work reflects a common model: owners are hiring engineering firms to manage complex, phased upgrades at facilities that cannot shut down.

In New Jersey, a Skanska and Traylor Bros. joint venture completed the $1.6 billion Portal North Bridge project, delivering a new 2.4-mile fixed rail span to replace an aging swing bridge over the Hackensack River. Replacing a movable bridge with a fixed span removes a mechanical failure mode that has long caused service disruptions, and it shows how rail resilience is increasingly being purchased through structural replacement rather than repair.

In Texas, Ferrovial subsidiary Webber won an approximately $538 million contract to build the Mary's Creek Water Reclamation Facility in Fort Worth. The source describes it as the company's largest water infrastructure project in the United States, a signal that wastewater and reclamation capacity is attracting major contractors as municipalities plan for growth.

Project Sector Reported Scope or Value Practical Engineering Lesson
Siemens Raleigh skid facility Power infrastructure Medium-voltage skid integration and testing Front-load commissioning risk into factory testing
Dulles and Reagan National upgrades Aviation Approx. $150M oversight contract (Jacobs, TYLin) Phased upgrades at live facilities demand strong owner-side coordination
Portal North Bridge Rail and bridges $1.6B, 2.4-mile fixed rail span Eliminating mechanical failure modes can be a durability strategy
Mary's Creek Water Reclamation Water Approx. $538M, Fort Worth Reclamation capacity is a growth-driven priority for utilities

Embodied Carbon Moves Into the Code Conversation

The last development in this set is perhaps the most consequential over the long run. The Structural Engineering Institute and Charles Pankow Foundation published Phase 1 findings from the CURE project, which evaluates how building code updates can help structural engineers reduce embodied carbon. Embodied carbon refers to the emissions associated with producing, transporting, and installing materials, such as concrete and steel, over a building's life cycle.

For structural engineers, this moves sustainability from a voluntary design preference toward a question of code language and design defaults. When codes specify how material efficiency is evaluated, they shape what gets specified on every project, not just on projects where owners demand it.

Practitioners should watch for three developments as CURE work progresses:

  • Material optimization pathways that show how reduced-carbon mixes and sections can meet existing performance requirements.
  • Documentation expectations for embodied carbon calculations, which may soon become part of permit submittals.
  • Training and tool needs, since engineers will need consistent methods to quantify and compare alternatives.
Key Takeaway: Code-level changes on embodied carbon will reach engineers through their everyday specifications. Firms that build carbon comparison into early design now will avoid scrambling when those requirements become standard.

What U.S. Engineers Should Do Next

These stories share a common thread: the engineer's value increasingly lies in demonstrating that a design holds up at every handoff. Whether that handoff is a factory test bench, a trench on a city street, a live airport terminal, or a permit application, the question is the same. Can you show how the design was verified, who verified it, and what changed along the way?

Over the coming year, engineering leaders should prioritize three actions. First, formalize factory and field verification protocols so that each interface has a documented owner and test criteria. Second, audit how geotechnical assumptions and field changes flow to the crews who actually execute the work. Third, begin modeling embodied carbon on active projects so that future code requirements do not arrive as a surprise.

The next phase of U.S. engineering delivery will not be defined only by how much capital flows into power, water, transit, and aviation. It will be defined by whether the engineering record, from the first sketch to the last inspection, is strong enough to carry the weight placed on it.