This HTML5 document contains 30 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n35:

n18:wikiPageDisambiguates

n2:

Subject Item

n2:

rdfs:label

Juggernaut Mk. I

rdfs:comment

After analyzing field reports that showed grievous losses, the GDI Board of Directors met to address the issue of the lack of long-range mobile artillery support. The Juggernaut Mk. I combined GDI naval and walker technology by fitting three large-caliber naval guns to a modified Titan Mk. I chassis. After the Firestorm Crisis, the Steel Talons division designed the second iteration of the Juggernaut, called the Behemoth. By the Third Tiberium War, this iteration was adapted to the Juggernaut Mk. III, used by regular GDI regiments.

dcterms:subject

n4: n25:

n10:

5

n17:

Mobile and deployed Juggernauts

n26:

Light

n21:

75

n11:

6

n32:

n33:

n14:

120

n13:

150

n8:wikiPageUsesTemplate

n9: n28: n30: n34: n36:

n20:

18

n6:

n7:

n22:

n23:

n29:

Self-propelled artillery walker

n15:

Juggernaut Mk. I

n19:

250

n12:

950

n24:

Must deploy to fire

n31:

9

n16:

*350 *400

n27:

Sensors

n18:abstract

After analyzing field reports that showed grievous losses, the GDI Board of Directors met to address the issue of the lack of long-range mobile artillery support. The Juggernaut Mk. I combined GDI naval and walker technology by fitting three large-caliber naval guns to a modified Titan Mk. I chassis. Like contemporary Nod self-propelled artillery, the Juggernaut had to deploy stabilizers out of its rear and become stationary prior to firing. Each of the walker's guns was smaller than the single gun carried by its Nod counterpart, but the larger number of guns allowed the Juggernaut to better saturate a target area. When deployed, the turret can traverse 360 degrees, ensuring all around security. The Juggernaut is notably faster in mobile mode, compared to Nod's artillery. Like all walkers of the period, the Juggernaut emerged from the conflict with mixed reviews. GDI found the all-terrain mobility conferred by walkers to be offset by the expense of construction and deployment. However, while other walkers were withdrawn from service, the Juggernaut and its descendants remained essential parts of the arsenal. As indirect combat vehicles GDI decided the all-terrain mobility outweighed the costs. After the Firestorm Crisis, the Steel Talons division designed the second iteration of the Juggernaut, called the Behemoth. By the Third Tiberium War, this iteration was adapted to the Juggernaut Mk. III, used by regular GDI regiments.