<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DefenceTalk &#124; Defense &#38; Military News - Forums - Pictures - Weapons &#187; Army Systems</title>
	<atom:link href="http://www.defencetalk.com/weapons/land-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.defencetalk.com</link>
	<description>Defense Industry News, forums and world military pictures</description>
	<lastBuildDate>Fri, 20 Nov 2009 07:29:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>FCS &#8211; Unattended Ground Sensors (UGS)</title>
		<link>http://www.defencetalk.com/fcs-unattended-ground-sensors-ugs-17083/</link>
		<comments>http://www.defencetalk.com/fcs-unattended-ground-sensors-ugs-17083/#comments</comments>
		<pubDate>Tue, 31 Oct 2006 21:39:44 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Army Special Weapons]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[The FCS Unattended Ground Sensors (UGS) program is divided into two
major subgroups of sensing systems: Tactical-UGS (T-UGS), which
includes Intelligence, Surveillance and Reconnaissance (ISR)-UGS and
Chemical, Biological, Radiological and Nuclear (CBRN)-UGS; and
Urban-UGS (U-UGS), also known as Urban Military Operations in Urban
Terrain (MOUT) Advanced Sensor System.


The intelligence, reconnaissance
and surveillance (ISR)-UGS will be modular and composed of tailorable
sensor groups [...]<p><a href="http://www.defencetalk.com/fcs-unattended-ground-sensors-ugs-17083/">FCS &#8211; Unattended Ground Sensors (UGS)</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></description>
			<content:encoded><![CDATA[<p>The FCS Unattended Ground Sensors (UGS) program is divided into two<br />
major subgroups of sensing systems: Tactical-UGS (T-UGS), which<br />
includes Intelligence, Surveillance and Reconnaissance (ISR)-UGS and<br />
Chemical, Biological, Radiological and Nuclear (CBRN)-UGS; and<br />
Urban-UGS (U-UGS), also known as Urban Military Operations in Urban<br />
Terrain (MOUT) Advanced Sensor System.<br />
<br /><span id="more-17083"></span></p>
<p>
The intelligence, reconnaissance<br />
and surveillance (ISR)-UGS will be modular and composed of tailorable<br />
sensor groups using multiple ground-sensing technologies. An Unattended<br />
Ground Sensors (UGS) field will include low-cost, expendable and<br />
multimode sensors for target detection, location and classification;<br />
and an imaging capability for target identification. A sensor field<br />
will also include a gateway node to provide sensor fusion and long-haul<br />
communications capability for transmitting target or other information<br />
to a remote operator, or the common operating picture through the FCS<br />
Modular Force Network. </p>
<p>The Unattended Ground Sensors (UGS) can be used<br />
to perform mission tasks such as perimeter defense, surveillance,<br />
target acquisition and situational awareness (SA), including Chemical,<br />
Biological, Radiological and Nuclear (CBRN) early warning.</p>
<p>
Urban-Unattended Ground Sensors (U-UGS) will provide a<br />
leave-behind, network-enabled reporting system for situational<br />
awareness (SA) and force protection in an urban setting, as well as<br />
residual protection for cleared areas of Urban Military Operations in<br />
Urban Terrain (MOUT) environments. They can be hand-employed by<br />
Soldiers or robotic vehicles either inside or outside buildings and<br />
structures.</p>
<p><a href="http://www.defencetalk.com/fcs-unattended-ground-sensors-ugs-17083/">FCS &#8211; Unattended Ground Sensors (UGS)</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.defencetalk.com/fcs-unattended-ground-sensors-ugs-17083/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FCS &#8211; The Soldier</title>
		<link>http://www.defencetalk.com/fcs-the-soldier-17082/</link>
		<comments>http://www.defencetalk.com/fcs-the-soldier-17082/#comments</comments>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Army Special Weapons]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[All Soldiers in the Modular Force are part of the Soldier as a
System (SaaS) overarching requirement encompassing everything the
Soldier wears, carries, and consumes to include unit radios, crew
served weapons, and unit specific equipment in the execution of tasks
and duties.


&#160;


All Soldiers systems will be treated as an integrated System of Systems (SoS).


The FCS Soldier, as defined [...]<p><a href="http://www.defencetalk.com/fcs-the-soldier-17082/">FCS &#8211; The Soldier</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></description>
			<content:encoded><![CDATA[<p>All Soldiers in the Modular Force are part of the Soldier as a<br />
System (SaaS) overarching requirement encompassing everything the<br />
Soldier wears, carries, and consumes to include unit radios, crew<br />
served weapons, and unit specific equipment in the execution of tasks<br />
and duties.<br />
<br /><span id="more-17082"></span>
<p>
&nbsp;
</p>
<p>
All Soldiers systems will be treated as an integrated System of Systems (SoS).
</p>
<p>
The FCS Soldier, as defined by Soldier as a System (SaaS), meets the<br />
need to improve the current capability of all Soldiers, regardless of<br />
Military Occupational Specialty (MOS), to perform Army Common Tasks and<br />
functions more efficiently and effectively.
</p>
<p>
Soldier as a System (SaaS) establishes a baseline for core Soldier<br />
requirements, and establishes the foundation for specific or mission<br />
unique Warrior Programs (Land, Mounted, and Air).
</p>
<p>
It will present a fully integrated Soldier that provides a balance of<br />
tasks, and mission equipment in support of the Soldier Team, FCS, and<br />
the Future Force.<img src="images/stories/military/unitedstates/soldier.jpg" border="0" alt="Future Combat Systems (FCS) - The Soldier" title="Future Combat Systems (FCS) - The Soldier" hspace="5" vspace="5" width="300" height="206" align="left" /></p>
<p><a href="http://www.defencetalk.com/fcs-the-soldier-17082/">FCS &#8211; The Soldier</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.defencetalk.com/fcs-the-soldier-17082/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Future Combat Systems (FCS) Overview</title>
		<link>http://www.defencetalk.com/future-combat-systems-fcs-overview-17081/</link>
		<comments>http://www.defencetalk.com/future-combat-systems-fcs-overview-17081/#comments</comments>
		<pubDate>Thu, 01 Jan 1970 01:00:00 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Army Special Weapons]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[The Army&#39;s Future Combat Systems (FCS) network allows the FCS
Family-of-Systems (FoS) to operate as a cohesive system-of-systems
where the whole of its capabilities is greater than the sum of its
parts.



As the key to the Army&#39;s transformation, the network, and its
logistics and Embedded Training (ET) systems, enable the Future Force
to employ revolutionary operational and organizational concepts. The
network [...]<p><a href="http://www.defencetalk.com/future-combat-systems-fcs-overview-17081/">Future Combat Systems (FCS) Overview</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></description>
			<content:encoded><![CDATA[<p>The Army&#39;s Future Combat Systems (FCS) network allows the FCS<br />
Family-of-Systems (FoS) to operate as a cohesive system-of-systems<br />
where the whole of its capabilities is greater than the sum of its<br />
parts.<br />
<br /><span id="more-17081"></span>
<p>
<br />
As the key to the Army&#39;s transformation, the network, and its<br />
logistics and Embedded Training (ET) systems, enable the Future Force<br />
to employ revolutionary operational and organizational concepts. The<br />
network enables Soldiers to perceive, comprehend, shape, and dominate<br />
the future battlefield at unprecedented levels as defined by the FCS<br />
Operational Requirements Document (ORD).
</p>
<p>
The FCS network consists of four overarching building blocks:<br />
System-of-Systems Common Operating Environment (SOSCOE); Battle Command<br />
(BC) software; communications and computers (CC); and intelligence,<br />
reconnaissance and surveillance (ISR) systems. The four building blocks<br />
synergistically interact enabling the Future Force to see first,<br />
understand first, act first and finish decisively.
</p>
<p>
System-of-Systems Common Operating Environment (SOSCOE) Central to<br />
FCS network implementation is the System-of-Systems Common Operating<br />
Environment (SOSCOE), which supports multiple mission-critical<br />
applications independently and simultaneously. It is configurable so<br />
that any specific instantiation can incorporate only the components<br />
that are needed for that instantiation. SOSCOE enables straightforward<br />
integration of separate software packages, independent of their<br />
location, connectivity mechanism and the technology used to develop<br />
them.
</p>
<p>
System-of-Systems Common Operating Environment (SOSCOE) architecture<br />
uses commercial off-the-shelf hardware and a Joint Tactical<br />
Architecture-Army compliant operating environment to produce a<br />
nonproprietary, standards-based component architecture for real-time,<br />
near-real-time, and non-real-time applications. System-of-Systems<br />
Common Operating Environment (SOSCOE) also contains administrative<br />
applications that provide capabilities including login service,<br />
startup, logoff, erase, memory zeroize, alert/emergency restart and<br />
monitoring/control. The System-of-Systems Common Operating Environment<br />
(SOSCOE) framework allows for integration of critical interoperability<br />
services that translate Army, Joint, and coalition formats to native,<br />
internal FCS message formats using a common format translation service.<br />
Because all interoperability services use these common translation<br />
services, new external formats will have minimal impact on the FCS<br />
software baseline. The FCS software is supported by<br />
application-specific interoperability services that act as proxy agents<br />
for each Joint and Army system. Battle Command (BC) can access these<br />
interoperability services through application program interfaces that<br />
provide isolation between the domain applications, thereby facilitating<br />
ease of software modifications and upgrades.
</p>
<p><strong>Battle Command (BC) Software</strong></p>
<p>
Battle Command (BC) mission applications include: mission planning<br />
and preparation, situation understanding, BC and mission execution and<br />
warfighter-machine interface (WMI). These four software packages&#39;<br />
combined capabilities enable full interaction among the FCS-equipped<br />
Units of Action (UAs). Battle Command (BC) capabilities will be common<br />
to, and tightly integrated into, all FCS, and will share a common<br />
framework to achieve the long-desired goal of an integrated and<br />
interoperable system with no hardware, software or information<br />
stovepipes.
</p>
<p>
The Mission Planning and Preparation package consists of 16 services<br />
embedded within System-of-Systems Common Operating Environment<br />
(SOSCOE). They support the development of deliberate, anticipatory and<br />
rapid-response plans; the ability to perform plan assessments and<br />
evaluations; terrain analysis; mission rehearsals; and after-action<br />
reviews for the Modular Force. As an example of the capabilities<br />
provided by this package, consider the FCS-networked fires key<br />
performance parameter (KPP). This package&#39;s predictive planning<br />
capabilities pre-approve airspace for weapons/munitions to target<br />
pairings so that when the decision to engage a target is made, the<br />
available weapons/munitions are already understood.
</p>
<p>
The 10 Situation Understanding package&#39;s services allow warfighters<br />
to better comprehend the battlespace and gain information superiority.<br />
The package includes map information and situational awareness (SA)<br />
database maintenance, which performs fusion as follows:
</p>
<ul>
<li> Situation refinement that fuses spatial and temporal relationships<br />
	among objects, grouping objects and abstract interpretation of the<br />
	patterns in the order of battle.
	</li>
<li>Threat refinement that combines activity with capability of enemy<br />
	forces, infers enemy intentions and performs threat assessment.
	</li>
<li>Process refinement that monitors the fusion process itself,<br />
	assesses the accuracy of the fusion process and regulates the<br />
	acquisition of data to achieve optimal results.
	</li>
</ul>
<p>
The Battle Command (BC) and Mission Execution package contains<br />
planning and decision aids that assist the commander in making quick,<br />
informed and accurate decisions to best prosecute the battle. These<br />
services are fully independent of mode -- training, rehearsal or<br />
operational -- and are intended to support manual to autonomous<br />
operations.
</p>
<p>
The warfighter-machine interface (WMI) package provides the<br />
capabilities to present Soldier information and receive Soldier<br />
information. WMI provides a common user interface across multiple<br />
platforms supporting the common crew station and &quot;personal digital<br />
assistant&quot; display system. It considers parameters such as echelon,<br />
type of system being used, and the warfighter&#39;s role to tailor<br />
information presentation.
</p>
<p><strong>Communications and Computers (CC) Systems</strong></p>
<p>
The FCS Family-of-Systems (FoS) are connected to the command,<br />
control, communications, computers, intelligence, surveillance and<br />
reconnaissance (C4ISR) network by a multilayered Communications and<br />
Computers (CC) network with unprecedented range, capacity and<br />
dependability. The Communications and Computers (CC) network provides<br />
secure, reliable access to information sources over extended distances<br />
and complex terrain. The network will support advanced functionalities<br />
such as integrated network management, information assurance and<br />
information dissemination management to ensure dissemination of<br />
critical information among sensors, processors and warfighters both<br />
within, and external to the FCS-equipped organization.
</p>
<p>
The Communications and Computers (CC) network does not rely on a<br />
large and separate infrastructure because it is primarily embedded in<br />
the mobile platforms and moves with the combat formations. This enables<br />
the command, control, communications, computers, intelligence,<br />
surveillance, and reconnaissance (C4ISR) network to provide superior<br />
Battle Command (BC) on the move to achieve offensive-oriented,<br />
high-tempo operations.
</p>
<p>
The FCS communication network is comprised of several homogenous<br />
communication systems such as Joint Tactical Radio System (JTRS)<br />
Clusters 1 and 5 with Wideband Network Waveform (WNW) and Soldier Radio<br />
Waveform (SRW), Network Data Link and Warfighter Information<br />
Network-Tactical (WIN-T). FCS leverages all available resources to<br />
provide a robust, survivable, scalable and reliable heterogeneous<br />
communications network that seamlessly integrates ground, nearground,<br />
airborne and space-borne assets for constant connectivity and layered<br />
redundancy.
</p>
<p>
Every FCS vehicle in the Modular Force will be equipped with a 4- or<br />
8-channel Joint Tactical Radio System (JTRS) Cluster 1. Soldiers and<br />
other weight and power-constrained platforms will be equipped with a 1-<br />
or 2-channel Joint Tactical Radio System (JTRS) Cluster 5. In addition<br />
to the Wideband Network Waveform (WNW) and Soldier Radio Waveform (SRW)<br />
communications backbone, the software programmable Joint Tactical Radio<br />
System (JTRS) will support other waveforms to ensure current force<br />
Joint, Interagency and Multinational (JIM) interoperability. The WIN-T<br />
will provide additional communications capability within the Modular<br />
Force, as well as reach to echelons above -- intra- and inter-Modular<br />
Force, and UA to Unit of Employment (UE) --and range extension.
</p>
<p>
The FCS Network Management System manages the entire Modular Force<br />
network including radios with different waveforms, platform routers,<br />
and local area networks (LANs), information assurance elements, and<br />
hosts. It provides a full spectrum of management capabilities required<br />
during all mission phases, including pre-mission planning, rapid<br />
network configuration upon deployment in the area of operations,<br />
monitoring the network during mission execution and dynamic adaptation<br />
of network policies in response to network performance and failure<br />
conditions.
</p>
<p>
FCS will employ an integrated computer system to host the<br />
System-of-Systems Common Operating Environment (SOSCOE), ensure common<br />
processing, support networking and employ consistent data<br />
storage/retrieval across all FCS platforms and applications. The<br />
integrated computer system consists of processors, storage media,<br />
dynamic memory, input/output devices, local area networks (LANs) and<br />
operating systems. A suite of seven computing system types have been<br />
identified to meet the various FCS platform-specific requirements for<br />
security, processing capability, computational capacity, throughput,<br />
memory, size, weight and power.
</p>
<p><strong>Intelligence, Reconnaissance and Surveillance (ISR)</strong></p>
<p>
A distributed and networked array of multispectral intelligence,<br />
reconnaissance and surveillance (ISR) sensors provides FCS with the<br />
ability to &quot;see first.&quot; Intelligence, Reconnaissance and Surveillance<br />
(ISR) assets within the Modular Force -- as well as those external to<br />
the Modular Force and at higher echelons -- will provide timely and<br />
accurate situational awareness (SA), enhance survivability by avoiding<br />
enemy fires, enable precision networked fires, and maintain contact<br />
throughout engagement. FCS will process real-time ISR data, outputs<br />
from survivability systems, situational awareness (SA) data and target<br />
identification information to update the common operating picture (COP)<br />
containing information on friendly forces, battlespace objects (BSOs),<br />
BSO groupings and their associated intent, threat potential and<br />
vulnerabilities. The real-time distribution and dissemination of<br />
information and data are reliant on robust, reliable, and high-capacity<br />
network data links.
</p>
<p>
To provide warfighters with actionable information, the data from<br />
the various distributed intelligence, reconnaissance and surveillance<br />
(ISR) and other sensor assets are subject to complex data processing,<br />
filtering, correlation, aided target recognition and fusion. The Sensor<br />
Data Management (SDM) software organizes all the sensor data --<br />
including detection reports -- and tracks information as received from<br />
the sensor packages. Data are then processed and fused to synthesize<br />
information about the object, situation, threat and ongoing<br />
intelligence, reconnaissance and surveillance (ISR) processes. In<br />
addition to receiving data from FCS organic sensors, Sensor Data<br />
Management (SDM) has the capability to receive sensor data from<br />
nonorganic sources including, current forces and Joint, Interagency,<br />
and Multinational (JIM). Sensor Data Management (SDM) will perform<br />
sensor data format conversions to output the data in FCS standard data<br />
formats.
</p>
<p><strong>Networked Logistics Systems</strong></p>
<p>
The key to the success of the FCS is the Networked Logistics Systems<br />
integrated through the Family-of-Systems (FOS) to achieve the logistics<br />
goals of reducing the logistics footprint, enhancing deployability,<br />
increasing operational availability, and reducing total ownership<br />
costs. These critical program goals are included in the two logistics<br />
Key Performance Parameters (KPP), KPP 4<br />
(Transportability/Deployability) and KPP 5<br />
(Sustainability/Reliability). Inherent to meeting these KPPs is the<br />
integration of logistics in the command, control, communications,<br />
computers, intelligence, surveillance and reconnaissance (C4ISR)<br />
network primarily through the Platform-Soldier Mission Readiness System<br />
(PSMRS) and the Logistics Decision Support System (LDSS). These systems<br />
provide unprecedented logistics information and decision tools to the<br />
commanders and logisticians by enabling the distribution system to<br />
deliver the right stuff to the right place at the right time. The<br />
networked logistics is further enabled by the demand reduction<br />
technologies designed into the System of Systems. Increased Reliability<br />
Availability Maintainability - Test (RAM-T) goals and implementing a<br />
Performance Based Logistics (PBL) support concept through extensive up<br />
front systems engineering efforts will result in increased Operational<br />
Availability and significant decreases in both parts and maintenance<br />
personnel while generating increased combat power for the Soldiers.
</p>
<p><strong>Embedded Training</strong></p>
<p>
The FCS network facilitates the Soldier&#39;s ability to train anywhere,<br />
any time. Technology has matured to a level that supports these<br />
requirements. Embedded Training (ET) will be developed as an integral<br />
part of the FCS manned platform and command, control, communications,<br />
computers, intelligence, surveillance, and reconnaissance (C4ISR)<br />
architectures.
</p>
<p>
The Embedded Live-Virtual-Constructive (L-V-C) Training is the<br />
cornerstone of the networked Embedded Training (ET) and will satisfy<br />
the Key Performance Parameter (KPP#6) which states &quot;The FCS Family of<br />
Systems (FoS) must have an embedded individual and collective training<br />
capability that supports live, virtual, and constructive training<br />
environments.&quot; Embedded Training (ET) must be designed-in at the start<br />
of the program to ensure it is developed in conjunction with the other<br />
FCS System of Systems (SoS) components. To do otherwise would lead to<br />
needless duplication of software development, potential negative<br />
training as a result of inevitable baseline divergence (as training<br />
tries to keep pace with operational software functionality) and<br />
additional space/weight/power claims for training. To fulfill the<br />
Operational and Organizational (O&amp;O) concepts, the System of<br />
Systems (SoS) must be capable of supporting operations, mission<br />
rehearsal and training of separate audiences (soldiers, units,<br />
leader/staff teams) simultaneously.</p>
<p><a href="http://www.defencetalk.com/future-combat-systems-fcs-overview-17081/">Future Combat Systems (FCS) Overview</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.defencetalk.com/future-combat-systems-fcs-overview-17081/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Javelin Anti-tank Guided Missile</title>
		<link>http://www.defencetalk.com/javelin-anti-tank-guided-missile-17080/</link>
		<comments>http://www.defencetalk.com/javelin-anti-tank-guided-missile-17080/#comments</comments>
		<pubDate>Sun, 31 Jul 2005 03:27:32 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Anti-Tank Weapons]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Javelin is an American man-portable anti-tank guided missile.


{mosgoogle}


It is a &#34;fire and forget&#34; system which utilises a top-attack flight profile against armoured vehicles and also has a direct-attack mode for use against buildings or fortifications. The system has a soft launch arrangement which ejects the missile from the tube to a safe distance before igniting [...]<p><a href="http://www.defencetalk.com/javelin-anti-tank-guided-missile-17080/">Javelin Anti-tank Guided Missile</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></description>
			<content:encoded><![CDATA[<p><strong>Javelin</strong> is an American man-portable anti-tank guided missile.<br />
<br /><span id="more-17080"></span>
<div>
{mosgoogle}
</div>
<div>
It is a &quot;fire and forget&quot; system which utilises a top-attack flight profile against armoured vehicles and also has a direct-attack mode for use against buildings or fortifications. The system has a soft launch arrangement which ejects the missile from the tube to a safe distance before igniting the main rocket motor. This reduces the firing signature and allows use from within buildings.
</div>
<div>
<br />
Javelin should not be confused with the British Javelin surface-to-air missile.
</div>
<h3>Service&nbsp;History</h3>
<div>
Javelin was used in the 2003 invasion of Iraq.</p>
</div>
<h3>Technical Information</h3>
<ul>
<li>Primary Function: Man-portable anti-tank guided missile. </li>
<li>Contractor: Lockheed Martin, Raytheon. </li>
<li>Power Plant: solid fuel rocket. </li>
</ul>
<ul>
<li><strong>Length:</strong>
<ul>
<li>108.1 cm (42.6 in) missile. </li>
<li>119.8 cm (47.2 in) launch tube. </li>
</ul>
</li>
<li><strong>Diameter:</strong>
<ul>
<li>12.7 cm (5.0 in) missile. </li>
<li>14.2 cm (5.6 in) launch tube. </li>
</ul>
</li>
<li><strong>Weight:</strong>
<ul>
<li>11.8 kg (21.6 lb) missile. </li>
<li>6.4 kg (14.1 lb) CLU. </li>
</ul>
</li>
<li><strong>Warhead:</strong>
<ul>
<li>8.4 kg tandem shaped charge HEAT. </li>
<li>Armour penetration &gt;600 mm RHA. </li>
</ul>
</li>
<li>Range: &lt;75 to &gt;2500 m </li>
<li>Guidance system: Imaging infra-red guidance, fire and forget. </li>
<li><strong>Command Launch Unit:</strong>
<ul>
<li>Passive target acquisition/fire control with integrated day/thermal sight. </li>
<li>Magnification 4x day and 4x or 9x thermal. </li>
</ul>
</li>
</ul>
<p></p>
<h3>Cost &amp; Procurement</h3>
<div>
In January 2003, the UK Ministry of Defence announced that it had decided to procure Javelin for the Light Forces Anti-Tank Guided Weapon System (LFATGWS) requirement. Javelin will replace the MILAN system.</p>
<p><a href="news/publish/article_002753.php"><strong>New Shoulder-Launched Missile Enters Service Four Months Early </strong></a>
</div>
<p></p>
<div>
In a 2002 contract, Lithuania bought 360 Javelin missiles and 40 launcher units for $39 million. The contract also included training devices, logistics support, associated equipment and training. press release<span class="urlexpansion">&nbsp;(<em>http://www.missilesandfirecontrol.com/our_news/pressreleases/02pressrelease/072402_JAVELIN.htm</em>)</span>
</div>
<p></p>
<div>
This works out at about $100,000 per missile.
</div>
<div>
<a name="wp-Users" title="wp-Users"></a>
</div>
<p></p>
<h3>Javelin is used by these countries:</h3>
<ul>
<li>Australia </li>
<li>Canada (In the process of testing prior to deciding to purchace the system) </li>
<li>Czech Republic </li>
<li>Jordan </li>
<li>Lithuania </li>
<li>New Zealand </li>
<li>Norway </li>
<li>Republic of Ireland </li>
<li>Taiwan </li>
<li>United Kingdom </li>
<li>United States </li>
</ul>
<h3>Related Topics</h3>
<ul>
<li>Anti-tank guided missile </li>
<li>List of missiles 
	</li>
</ul>
<h3>Related&nbsp;links</h3>
<ul>
<li><a href="http://www.missilesandfirecontrol.com/our_products/antiarmor/JAVELIN/product-JAVELIN.html" target="wpext" title="http://www.missilesandfirecontrol.com/our products/antiarmor/JAVELIN/product-JAVELIN.html">Lockheed Martin</a></li>
</ul>
<p><a href="http://www.defencetalk.com/javelin-anti-tank-guided-missile-17080/">Javelin Anti-tank Guided Missile</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.defencetalk.com/javelin-anti-tank-guided-missile-17080/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>M1 Abrams Main Battle Tank</title>
		<link>http://www.defencetalk.com/m1-abrams-main-battle-tank-17079/</link>
		<comments>http://www.defencetalk.com/m1-abrams-main-battle-tank-17079/#comments</comments>
		<pubDate>Thu, 23 Jun 2005 21:05:01 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[Tanks]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[purpose
Provide heavy armor superiority on the battlefield.



General Information
The Abrams tank closes with and destroys enemy forces on the integrated battlefield using mobility, firepower, and shock effect. There are three variants in service: M1, M1A1 and M1A2. The 120mm main gun on the M1A1 and M1A2, combined with the powerful 1,500 hp turbine engine and special [...]<p><a href="http://www.defencetalk.com/m1-abrams-main-battle-tank-17079/">M1 Abrams Main Battle Tank</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></description>
			<content:encoded><![CDATA[<p><strong><em>purpose<br />
</em></strong>Provide heavy armor superiority on the battlefield.</p>
<p><span id="more-17079"></span></p>
<p><!-- InstanceEndEditable --></p>
<div>
<strong>General Information</strong><br />
The Abrams tank closes with and destroys enemy forces on the integrated battlefield using mobility, firepower, and shock effect. There are three variants in service: M1, M1A1 and M1A2. The 120mm main gun on the M1A1 and M1A2, combined with the powerful 1,500 hp turbine engine and special armor, make the Abrams tank particularly suitable for attacking or defending against large concentrations of heavy armor forces on a highly lethal battlefield.
</div>
<p></p>
<div>
Features of the M1A1 modernization program include increased armor protection; suspension improvements; and a nuclear, biological and chemical (NBC) protection system that increases survivability in a contaminated environment. The M1A1D modification consists of an M1A1 with integrated appliqu&eacute; computer and a far-target-designation capability.
</div>
<p></p>
<div>
The M1A2 modernization program includes a commander&#39;s independent thermal viewer, an improved commander&#39;s weapon station, position navigation equipment, a distributed data and power architecture, an embedded diagnostic system and improved fire control systems.
</div>
<p></p>
<div>
The M1A2 System Enhancement Program (SEP) adds second-generation thermal sensors and a thermal management system. The SEP includes upgrades to processors/memory that enable the M1A2 to use The Army&#39;s common command and control software, enabling the rapid transfer of digital situational data and overlays.</p>
<table border="0" cellspacing="0" cellpadding="0" width="422" height="170">
<tbody>
<tr>
<td>&nbsp;</td>
<td><strong>M1/IPM1</strong></td>
<td><strong>M1A1</strong></td>
<td><strong>M1A2</strong></td>
<td><strong>M1A2 SEP</strong></td>
</tr>
<tr>
<td><em><strong>Length:</strong></em></td>
<td>32.04 ft</td>
<td>32.04 ft</td>
<td>32.04 ft</td>
<td>32.04 ft</td>
</tr>
<tr>
<td><em><strong>Width:</strong></em></td>
<td>12 ft</td>
<td>12 ft</td>
<td>12 ft</td>
<td>12 ft</td>
</tr>
<tr>
<td><em><strong>Height:</strong></em></td>
<td>7.79 ft</td>
<td>8.0 ft</td>
<td>8.0 ft</td>
<td>8.0 ft</td>
</tr>
<tr>
<td><em><strong>Top speed:</strong></em></td>
<td>45 mph</td>
<td>41.5 mph</td>
<td>41.5 mph</td>
<td>42 mph</td>
</tr>
<tr>
<td><em><strong>Weight:</strong></em></td>
<td>61.4/62.8 tons</td>
<td>67.6 tons</td>
<td>68.4 tons</td>
<td>69.5 tons</td>
</tr>
<tr>
<td><em><strong>Main armament:</strong></em></td>
<td>105mm</td>
<td>120mm</td>
<td>120mm</td>
<td>120mm</td>
</tr>
<tr>
<td><em><strong>Crew:</strong></em></td>
<td>4</td>
<td>4</td>
<td>4</td>
<td>4</td>
</tr>
</tbody>
</table>
<p><!-- InstanceEndEditable --><!-- InstanceBeginEditable name="Manufacturer" -->
</div>
<div>
<strong><em><br />
Entered Army Service</em></strong><br />
<!-- InstanceBeginEditable name="entered date" -->1980<strong><em></p>
<p>Manufacturer</em></strong><br />
General Dynamics (Sterling Heights, MI; Warren, MI; Muskegon, MI; Scranton, PA; Lima, OH; Tallahassee, FL)<!-- InstanceEndEditable -->
</div>
<p></p>
<div>
<em><strong>Point of Contact<br />
</strong><a href="http://www.dtic.mil/armylink">Office of the Chief of Public Affairs</a><br />
Media Relations Division<br />
1500 Army Pentagon<br />
Washington, DC 20310-1500<br />
703.697.7592 / 7591</em>
</div>
<p></p>
<p><a href="http://www.defencetalk.com/m1-abrams-main-battle-tank-17079/">M1 Abrams Main Battle Tank</a> is a post from: <a href="http://www.defencetalk.com">DefenceTalk | Defense &amp; Military News - Forums - Pictures - Weapons</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.defencetalk.com/m1-abrams-main-battle-tank-17079/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
