World Library  
Flag as Inappropriate
Email this Article
 

United States Africa Command

United States Africa Command
The Emblem of the United States Africa Command
Active Authorized: 15 December 2006
Announced: 6 February 2007
Established: 1 October 2007
Activated: 1 October 2008
Country  United States of America
Type Unified Combatant Command
Size 2,000 (1,500 stationed at HQ in Germany)[1]
Headquarters Kelley Barracks, Stuttgart, Germany
Nickname(s) U.S. AFRICOM
Engagements 2011 military intervention in Libya
Website http://www.africom.mil
Commanders
Commander General David M. Rodriguez,
U.S. Army
Deputy for Military Operations Vice Admiral Michael T. Franken, U.S. Navy
Deputy for
Civil-Military Engagement
Ambassador Donald W. Koran,
U.S. Department of State

The United States Africa Command (U.S. AFRICOM (official abbreviation), USAFRICOM, or AFRICOM) is one of nine Unified Combatant Commands of the United States Armed Forces, headquartered at Kelley Barracks, Stuttgart, Germany. It is responsible for U.S. military operations and military relations with 53 African nations. Its area of responsibility covers all of Africa except Egypt, which is within the area of responsibility of the United States Central Command. U.S. AFRICOM headquarters operating budget was $276 million in fiscal year 2012.[1]

The Commander of U.S. AFRICOM reports to the Secretary of Defense.[2] In individual countries, U.S. Ambassadors continue to be the primary diplomatic representative for relations with host nations.

Contents

  • Function 1
  • History (2000–2006) 2
  • Creation of AFRICOM (2006–2008) 3
  • Geographic scope 4
  • Headquarters and facilities 5
    • Selection of the headquarters 5.1
  • Personnel 6
  • Components 7
    • U.S. Army Africa (USARAF) 7.1
    • U.S. Naval Forces, Africa (NAVAF) 7.2
    • 3d Air Force (Air Forces Africa) [3AF (AFAFRICA)] 7.3
    • U.S. Marine Corps Forces, Africa (MARFORAF) 7.4
  • Subordinate Commands 8
    • U.S. Special Operations Command, Africa 8.1
    • Combined Joint Task Force – Horn of Africa 8.2
  • Programs and operations 9
    • Programs 9.1
    • Operations 9.2
  • List of commanders 10
  • See also 11
  • References 12
  • Further reading 13
  • External links 14

Function

In 2007, the White House announced, "[AFRICOM] will strengthen our security cooperation with Africa and create new opportunities to bolster the capabilities of our partners in Africa. Africa Command will enhance our efforts to bring peace and security to the people of Africa and promote our common goals of development, health, education, democracy, and economic growth in Africa."[3]

General Carter F. Ham said in a 2012 address at Brown University that U.S. strategy for Sub-Saharan Africa is to strengthen democratic institutions and boost broad-based economic growth.[1]

History (2000–2006)

Prior to the creation of AFRICOM, responsibility for U.S. military operations in Africa was divided across three Unified Commands: United States European Command (EUCOM) for West Africa, United States Central Command (CENTCOM) for East Africa, and United States Pacific Command (PACOM) for Indian Ocean waters and islands off the east coast of Africa.

A U.S. military officer wrote the first public article calling for the formation of a separate African command in November 2000.[4] Following a 2004 global posture review, the Pentagon began establishing a number of Cooperative Security Locations (CSLs) and Forward Operating Sites (FOSs) across the African continent, through the auspices of EUCOM which had nominal command of West Africa at that time. These locations, along with Camp Lemonnier in Djibouti, would form the basis of AFRICOM facilities on the continent. Areas of military interest to the United States in Africa include the Sahara/Sahel region,[5] over which Joint Task Force Aztec Silence is conducting anti-terrorist operations (Operation Enduring Freedom - Trans Sahara), Djibouti in the Horn of Africa, where Combined Joint Task Force – Horn of Africa is located (overseeing Operation Enduring Freedom - Horn of Africa), and the Gulf of Guinea.

The website Magharebia.com was launched by USEUCOM in 2004 to provide news about North Africa in English, French and Arabic.[6] When AFRICOM was created, it took over operation of the website.[7] Information operations of the Pentagon was criticized by the Senate Armed Forces Committee and defunded by Congress in 2011. The site was closed down in February 2015.[8][9]

In 2007, the United States Congress approved $500 million for the Trans-Saharan Counterterrorism Initiative (TSCTI) over six years to support countries involved in counterterrorism against threats of Al Qaeda operating in African countries, primarily Algeria, Chad, Mali, Mauritania, Niger, Senegal, Nigeria, and Morocco.[10] This program builds upon the former Pan Sahel Initiative (PSI), which concluded in December 2004[11] and focused on weapon and drug trafficking, as well as counterterrorism.[12] Previous U.S. military activities in sub-Saharan Africa have included Special Forces associated Joint Combined Exchange Training. Letitia Lawson, writing in 2007 for a Center for Contemporary Conflict journal at the Naval Postgraduate School, noted that U.S. policy towards Africa, at least in the medium-term, looks to be largely defined by international terrorism, the increasing importance of African oil to American energy needs, and the dramatic expansion and improvement of Sino-African relations since 2000.[13]

Creation of AFRICOM (2006–2008)

In mid-2006, Defense Secretary


  • Official website and March 2010 posture statement
  • United States Army Africa official website
  • Africa Interactive Map from the United States Army Africa
  • APCN (Africa Partner Country Network)
  • Advanced Questions for General William E. "Kip" Ward, U.S. Army Nominee for Commander, U.S. Africa Command PDF (165 KB), U.S. Senate Committee on Armed Services testimony.
  • U.S. Africa Command: A New Strategic Paradigm? PDF (1.03 MB) by Sean McFate in Military Review, January–February 2008
  • Africa’s Security Challenges and Rising Strategic Significance, Strategic Insights, January 2007
  • AFRICOM public brief PDF (652 KiB), United States Department of Defense, 2 February 2007
  • "Blood Oil" by Sebastian Junger in Vanity Fair, February 2007. Retrieved 28 January 2007
  • "Africa Command: 'Follow the oil'" in World War 4 Report, 16 February 2007
  • The Americans Have Landed, Esquire, 27 June 2007. Retrieved 2007-08-10.
  • Does Africa need Africom?
  • ResistAFRICOM website
  • Criticism of AFRICOM

External links

Further reading

  1. ^ a b c d
  2. ^
  3. ^
  4. ^
  5. ^
  6. ^
  7. ^
  8. ^
  9. ^
  10. ^
  11. ^
  12. ^
  13. ^
  14. ^
  15. ^
  16. ^
  17. ^ a b
  18. ^
  19. ^
  20. ^
  21. ^ The Economist, "Policing the undergoverned spaces", 16–22 June 2007, p. 46
  22. ^
  23. ^
  24. ^
  25. ^
  26. ^
  27. ^ Erik Holmes, Official: AFRICOM Will Need Air Force Aircraft, Air Force Times, 5 December 2007
  28. ^ "TRANSCRIPT: General Ward Outlines Vision for U.S. Africa Command", 18 February 2008
  29. ^ "TRANSCRIPT: AFRICOM's General Ward Interviewed by the BBC's Nick Childs", 18 February 2008
  30. ^ "Bush Says No New U.S. Bases in Africa"
  31. ^ Stars and Stripes, AFRICOM to depart from J-code structure, 12 August 2007
  32. ^
  33. ^ [1]
  34. ^ [2]
  35. ^ Novak, Lisa M., "Italy To Host AFRICOM Headquarters", Stars and Stripes, 5 December 2008.
  36. ^ Special Operations Technology, Q & A with Brigadier General Patrick M. Higgins, Vol. 6, Issue 6, 2008
  37. ^ Lt. Gen. William Grisoli, "The Army has now aligned a brigade with U.S. Africa Command." accessdate=2012-12-10
  38. ^
  39. ^
  40. ^
  41. ^
  42. ^
  43. ^
  44. ^
  45. ^
  46. ^
  47. ^
  48. ^ http://www.africom.mil/Newsroom/Article/8250/nswu-10-commissioning-provides-socafrica-operation
  49. ^ SOCOM 2015 Factbook
  50. ^
  51. ^ Ham, Carter. "STATEMENT: AFRICOM Commander on Commencement of Military Strikes in Libya." AFRICOM, 19 March 2011.
return p

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


return p-------------------------------------------------------------------------------- -- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


-- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --


References

See also

No. Image Name Service Start End Time in office
1. General William E. Ward U.S. Army 1 October 2007 8 March 2011 days
2. General Carter F. Ham U.S. Army 8 March 2011 5 April 2013 days
3. General David M. Rodriguez U.S. Army 5 April 2013 Incumbent 986 days

List of commanders

Operations

Programs

Programs and operations

Combined Joint Task Force – Horn of Africa (CJTF-HOA) conducts operations in the East Africa region to build partner nation capacity in order to promote regional security and stability, prevent conflict, and protect U.S. and coalition interests. CJTF-HOA's efforts, as part of a comprehensive whole-of-government approach, are aimed at increasing African partner nations' capacity to maintain a stable environment, with an effective government that provides a degree of economic and social advancement for its citizens.[50]

Combined Joint Task Force – Horn of Africa

Combined Joint Task Force – Horn of Africa

  • Special Operations Command Forward-East (Special Operations Command and Control Element - Horn of Africa)
  • Special Operations Command Forward-Central (AFRICOM Counter-Lord's Resistance Army Control Element)
  • Special Operations Command Forward-West (Joint Special Operations Task Force-Trans Sahara)
  • Naval Special Warfare Unit 10, Joint Special Operations Air Component Africa, and SOCAFRICA Signal Detachment
  • Commander SOCAFRICA serves as the Special Operations Adviser to Commander, USAFRICOM."

Organizations included in SOCAFRICA include:[49]

On April 8, 2011, Naval Special Warfare Unit 10, operationally assigned and specifically dedicated for SOCAFRICA missions, was commissioned at Panzer Kaserne, near Stuttgart, Germany.[48] It is administratively assigned to Naval Special Warfare Group 2 on the U.S. East Coast.

SOCAFRICA’s objectives are to build operational capacity, strengthen regional security and capacity initiatives, implement effective communication strategies in support of strategic objectives, and eradicate violent extremist organizations and their supporting networks. SOCAFRICA forces work closely with both U.S. Embassy country teams and African partners, maintaining a small but sustained presence throughout Africa, predominantly in the OEF-TS and CJTF-HOA regions. SOCAFRICA’s persistent SOF presence provides an invaluable resource that furthers USG efforts to combat violent extremist groups and builds partner nation CT capacity.[47]

Special Operations Command Africa was activated on October 1, 2008 and became fully operationally capable on October 1, 2009. SOCAFRICA is a Subordinate-Unified Command of United States Special Operations Command, operationally controlled by U.S. Africa Command, collocated with USAFRICOM at Kelley Barracks, Stuttgart-Möhringen, Germany. Also on 1 October 2008, SOCAFRICA assumed responsibility for the Special Operations Command and Control Element – Horn of Africa, and on 15 May 2009, SOCAFRICA assumed responsibility for Joint Special Operations Task Force Trans – Sahara (JSOTF-TS) – the SOF component of Operation Enduring Freedom – Trans Sahara.

Special Operations Command Africa: United States Army Element Shoulder Sleeve Insignia and Combat Service Identification Badge

U.S. Special Operations Command, Africa

Subordinate Commands

In 2013, the Special Purpose Marine Air-Ground Task Force for Crisis Response was formed to provide quick response to American interests in North Africa by flying marines in Bell Boeing V-22 Osprey aircraft from bases in Europe.[46]

MARFORAF conducted military to military events in 2009 designed to familiarize African partners with nearly every facet of military operations and procedures, including use of unmanned aerial vehicles, tactics, and medical skills. MARFORAF, as the lead component, continues to conduct Exercise AFRICAN LION in Morocco—the largest annual Combined Joint Chiefs of Staff (CJCS) exercise on the African continent—as well as Exercise SHARED ACCORD 10, which was the first CJCS exercise conducted in Mozambique.[45]

U.S. Marine Corps Forces, Africa conducts operations, exercises, training, and security cooperation activities throughout the AOR. In 2009, MARFORAF participated in 15 ACOTA missions aimed at improving partners’ capabilities to provide logistical support, employ military police, and exercise command and control over deployed forces.

U.S. Marine Corps Forces Africa

U.S. Marine Corps Forces, Africa (MARFORAF)

3AF succeeds the Seventeenth Air Force by assuming the AFAFRICA mission upon the 17AF's deactivation on 20 April 2012.[44]

3AF (AFAFRICA) works with other U.S. Government agencies, to include the State Department and the U.S. Agency for International Development (USAID), to assist African partners in developing national and regional security institution capabilities that promote security and stability and facilitate development.[43]

[42] Headquarters,

U.S. Air Forces Africa

3d Air Force (Air Forces Africa) [3AF (AFAFRICA)]

-- based on setting/preference specify order local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "poj", "zhu", "l"} if (t1) then orderlist[2] = "t" orderlist[3] = "s" end if (j1) then orderlist[4] = "j" orderlist[5] = "cy" orderlist[6] = "p" orderlist[7] = "tp" orderlist[8] = "w" end -- rename rules. Rules to change parameters and labels based on other parameters if args["hp"] then -- hp an alias for p ([hanyu] pinyin) args["p"] = args["hp"] end if args["tp"] then -- if also Tongyu pinyin use full name for Hanyu pinyin labels["p"] = "Hanyu Pinyin" end if (args["s"] and args["s"] == args["t"]) then -- Treat simplified + traditional as Chinese if they're the same args["c"] = args["s"] args["s"] = nil args["t"] = nil elseif (not (args["s"] and args["t"])) then -- use short label if only one of simplified and traditional labels["s"] = labels["c"] labels["t"] = labels["c"] end local body = "" -- the output string local params -- for creating HTML spans local label -- the label, i.e. the bit preceeding the supplied text local val -- the supplied text -- go through all possible fields in loop, adding them to the output for i, part in ipairs(orderlist) do if (args[part]) then -- build label label = "" if (uselabels) then label = labels[part] if (capfirst) then label = mw.language.getContentLanguage():ucfirst( Any naval unit within the USEUCOM or USAFRICOM AOR may be assigned to Task Force 60 as required upon signal from the Commander of the Sixth Fleet.

        local t1 = false -- whether traditional Chinese characters go first
        local j1 = false -- whether Cantonese Romanisations go first
        local testChar
        if (args["first"]) then
                 for testChar in mw.ustring.gmatch(args["first"], "%a+") do
          if (testChar == "t") then
           t1 = true
           end
          if (testChar == "j") then
           j1 = true
           end
         end
        end
        if (t1 == false) then
         local title = mw.title.getCurrentTitle()
         t1 = t1st[title.text] == true
        end

function p.Zh(frame) -- load arguments module to simplify handling of args local getArgs = require('Module:Arguments').getArgs local args = getArgs(frame) return p._Zh(args) end function p._Zh(args) local uselinks = not (args["links"] == "no") -- whether to add links local uselabels = not (args["labels"] == "no") -- whether to have labels local capfirst = args["scase"] ~= nil

local italic = { ["p"] = true, ["tp"] = true, ["w"] = true, ["j"] = true, ["cy"] = true, ["poj"] = true, } -- Categories for different kinds of Chinese text local cats = { ["c"] = "", ["s"] = "", ["t"] = "", }

-- for those parts which are to be treated as languages their ISO code local ISOlang = { ["c"] = "zh", ["t"] = "zh-Hant", ["s"] = "zh-Hans", ["p"] = "zh-Latn-pinyin", ["tp"] = "zh-Latn", ["w"] = "zh-Latn-wadegile", ["j"] = "yue-jyutping", ["cy"] = "yue", ["poj"] = "hak", ["zhu"] = "zh-Bopo", }

-- article titles for wikilinks for each part local wlinks = { ["c"] = "Chinese language", ["s"] = "simplified Chinese characters", ["t"] = "traditional Chinese characters", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Yale romanization of Cantonese", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Bopomofo", }

-- the labels for each part local labels = { ["c"] = "Chinese", ["s"] = "simplified Chinese", ["t"] = "traditional Chinese", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Cantonese Yale", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Zhuyin Fuhao", ["l"] = "literally", }

-- articles in which traditional Chinese preceeds simplified Chinese local t1st = { ["228 Incident"] = true, ["Chinese calendar"] = true, ["Lippo Centre, Hong Kong"] = true, ["Republic of China"] = true, ["Republic of China at the 1924 Summer Olympics"] = true, ["Taiwan"] = true, ["Taiwan (island)"] = true, ["Taiwan Province"] = true, ["Wei Boyang"] = true, }

local p = {}

Task Force 60 will normally be the commander of Naval Task Force Europe and Africa.require('Module:No globals')

The area of responsibility covers more than 20 million square nautical miles of ocean, touches three continents and encompasses more than 67 percent of the Earth's coastline, 30 percent of its landmass, and nearly 40 percent of the world's population.[41]

The Commander, U.S. Naval Forces Europe-Commander, U.S. Naval Forces Africa (NAVEUR-NAVAF) area of responsibility (AOR) covers approximately half of the Atlantic Ocean, from the North Pole to Antarctica; as well as the Adriatic, Baltic, Barents, Black, Caspian, Mediterranean and North Seas.[40] NAVEUR-NAVAF covers all of Russia, Europe and nearly the entire continent of Africa. It encompasses 105 countries with a combined population of more than one billion people and includes a landmass extending more than 14 million square miles.

U.S. Naval Forces Africa

U.S. Naval Forces, Africa (NAVAF)

The 2nd Brigade Combat Team, 1st Infantry Division, the "Dagger Brigade", is being aligned with AFRICOM.[39]

Headquartered on Caserma Ederle in Vicenza, Italy, U.S. Army Africa, in concert with national and international partners, conducts sustained security engagement with African land forces to promote peace, stability, and security in Africa. As directed, it can deploy as a contingency headquarters in support of crisis response.[38]

U.S. Army Africa

U.S. Army Africa (USARAF)

The U.S. Army has allocated a brigade to the Africa Command.[37]

On 3 December 2008 the U.S. announced that Army and Navy headquarters units of AFRICOM would be hosted in Italy. The AFRICOM section of the Army’s Southern European Task Force would be located in Vicenza and Naval Forces Europe in Naples would expand to include the Navy's AFRICOM component.[35] Special Operations Command, Africa (SOCAFRICA) is also established, gaining control over Joint Special Operations Task Force-Trans Sahara (JSOTF-TS) and Special Operations Command and Control Element – Horn of Africa (SOCCE-HOA).[36]

On 1 October 2008, the Seventeenth Air Force was established at Ramstein Air Base, Germany as the United States Air Force component of the Africa Command.[32] Brig. Gen. Tracey Garrett was named as commander of the new USMC component, U.S. Marine Corps Forces Africa (MARFORAF), in November 2008.[33][34] MARFORAF is a dual-mission arrangement for United States Marine Corps Forces, Europe.

Components

U.S. Africa Command has limited assigned forces and relies on the Department of Defense for resources necessary to support its missions.

As of December 2010, the command has five Senior Foreign Service officers in key positions as well as more than 30 personnel from 13 U.S. Government Departments and Agencies serving in leadership, management, and staff positions. Some of the agencies represented are the United States Department's of State, Treasury, and Commerce, United States Agency for International Development, and the United States Coast Guard.

U.S. Africa Command completed fiscal year 2010 with approximately 2,000 assigned personnel, which includes military, civilian, contractor, and host nation employees. About 1,500 work at the command’s main headquarters in Stuttgart. Others are assigned to the command’s units in England and Florida, along with security cooperation officers posted at U.S. embassies and diplomatic missions in Africa to coordinate Defense Department programs within the host nation.

Personnel

-- based on setting/preference specify order local orderlist = {"c", "s", "t", "p", "tp", "w", "j", "cy", "poj", "zhu", "l"} if (t1) then orderlist[2] = "t" orderlist[3] = "s" end if (j1) then orderlist[4] = "j" orderlist[5] = "cy" orderlist[6] = "p" orderlist[7] = "tp" orderlist[8] = "w" end -- rename rules. Rules to change parameters and labels based on other parameters if args["hp"] then -- hp an alias for p ([hanyu] pinyin) args["p"] = args["hp"] end if args["tp"] then -- if also Tongyu pinyin use full name for Hanyu pinyin labels["p"] = "Hanyu Pinyin" end if (args["s"] and args["s"] == args["t"]) then -- Treat simplified + traditional as Chinese if they're the same args["c"] = args["s"] args["s"] = nil args["t"] = nil elseif (not (args["s"] and args["t"])) then -- use short label if only one of simplified and traditional labels["s"] = labels["c"] labels["t"] = labels["c"] end local body = "" -- the output string local params -- for creating HTML spans local label -- the label, i.e. the bit preceeding the supplied text local val -- the supplied text -- go through all possible fields in loop, adding them to the output for i, part in ipairs(orderlist) do if (args[part]) then -- build label label = "" if (uselabels) then label = labels[part] if (capfirst) then label = mw.language.getContentLanguage():ucfirst(

        local t1 = false -- whether traditional Chinese characters go first
        local j1 = false -- whether Cantonese Romanisations go first
        local testChar
        if (args["first"]) then
                 for testChar in mw.ustring.gmatch(args["first"], "%a+") do
          if (testChar == "t") then
           t1 = true
           end
          if (testChar == "j") then
           j1 = true
           end
         end
        end
        if (t1 == false) then
         local title = mw.title.getCurrentTitle()
         t1 = t1st[title.text] == true
        end

function p.Zh(frame) -- load arguments module to simplify handling of args local getArgs = require('Module:Arguments').getArgs local args = getArgs(frame) return p._Zh(args) end function p._Zh(args) local uselinks = not (args["links"] == "no") -- whether to add links local uselabels = not (args["labels"] == "no") -- whether to have labels local capfirst = args["scase"] ~= nil

local italic = { ["p"] = true, ["tp"] = true, ["w"] = true, ["j"] = true, ["cy"] = true, ["poj"] = true, } -- Categories for different kinds of Chinese text local cats = { ["c"] = "", ["s"] = "", ["t"] = "", }

-- for those parts which are to be treated as languages their ISO code local ISOlang = { ["c"] = "zh", ["t"] = "zh-Hant", ["s"] = "zh-Hans", ["p"] = "zh-Latn-pinyin", ["tp"] = "zh-Latn", ["w"] = "zh-Latn-wadegile", ["j"] = "yue-jyutping", ["cy"] = "yue", ["poj"] = "hak", ["zhu"] = "zh-Bopo", }

-- article titles for wikilinks for each part local wlinks = { ["c"] = "Chinese language", ["s"] = "simplified Chinese characters", ["t"] = "traditional Chinese characters", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Yale romanization of Cantonese", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Bopomofo", }

-- the labels for each part local labels = { ["c"] = "Chinese", ["s"] = "simplified Chinese", ["t"] = "traditional Chinese", ["p"] = "pinyin", ["tp"] = "Tongyong Pinyin", ["w"] = "Wade–Giles", ["j"] = "Jyutping", ["cy"] = "Cantonese Yale", ["poj"] = "Pe̍h-ōe-jī", ["zhu"] = "Zhuyin Fuhao", ["l"] = "literally", }

-- articles in which traditional Chinese preceeds simplified Chinese local t1st = { ["228 Incident"] = true, ["Chinese calendar"] = true, ["Lippo Centre, Hong Kong"] = true, ["Republic of China"] = true, ["Republic of China at the 1924 Summer Olympics"] = true, ["Taiwan"] = true, ["Taiwan (island)"] = true, ["Taiwan Province"] = true, ["Wei Boyang"] = true, }

local p = {}

In general, U.S. Unified Combatant Commands have an HQ of their own in one location, subordinate service component HQs, sometimes one or two co-located with the main HQ or sometimes spread widely, and a wide range of operating locations, main bases, forward detachments, etc. USAFRICOM initially appears to be considering something slightly different; spreading the actually COCOM HQ over several locations, rather than having the COCOM HQ in one place and the putative "U.S. Army Forces, Africa", its air component, and "U.S. Naval Forces, Africa" in one to four separate locations. AFRICOM will not have the traditional J-type staff divisions, instead having outreach, plans and programs, knowledge development, operations and logistics, and resources branches.[31] AFRICOM went back to a traditional J-Staff in early 2011 after General Carter Ham took command.require('Module:No globals')

President Bush denied that the United States was contemplating the construction of new bases on the African continent.[30] U.S. plans include no large installations such as Camp Bondsteel in Kosovo, but rather a network of "cooperative security locations" at which temporary activities will be conducted. There is one U.S. base on the continent, Camp Lemonnier in Djibouti, with approximately 2,300 troops stationed there having been inherited from USCENTCOM upon standup of the command.

On 18 February 2008 General Ward told an audience at the Royal United Services Institute in London that some portion of that staff headquarters being on the continent at some point in time would be "a positive factor in helping us better deliver programs."[28] General Ward also told the BBC the same day in an interview that there are no definite plans to take the headquarters or a portion of it to any particular location on the continent.[29]

The Sudan Tribune considered it likely that Ethiopia, a strong U.S. ally in the region, will house USAFRICOM's headquarters due to the collocation of AFRICOM with the African Union's developing peace and security apparatus.[25] Prime Minister Meles Zenawi stated in early November that Ethiopia would be willing to work together closely with USAFRICOM.[26] This was further reinforced when a U.S. Air Force official said on 5 December 2007, that Addis Ababa was likely to be the headquarters.[27]

It was reported in June 2007 that African countries were competing to host the headquarters because it would bring money for the recipient country.[21] However, of all the African nations, only Liberia has publicly expressed a willingness to host AFRICOM's headquarters. The U.S. declared in February 2008 that AFRICOM would be headquartered in Stuttgart for the "foreseeable future". In August 2007, Dr. Wafula Okumu, a research fellow at the Institute for Security Studies in South Africa, testified before the United States Congress about the growing resistance and hostility on the African continent.[22] Nigeria announced it will not allow its country to host a base and opposed the creation of a base on the continent. South Africa and Libya also expressed reservations of the establishment of a headquarters in Africa.[23][24]

Selection of the headquarters

The AFRICOM headquarters is located at Kelley Barracks, a small urban facility near Stuttgart, Germany, and is staffed by 1,500 personnel. In addition, the command has military and civilian personnel assigned at Camp Lemonnier, Djibouti; RAF Molesworth, United Kingdom; MacDill Air Force Base, Florida; and in Offices of Security Cooperation and Defense Attaché Offices in about 38 African countries.[1]

Headquarters and facilities

The U.S. military areas of responsibility involved were transferred from three separate U.S. unified combatant commands. Most of Africa was transferred from the United States European Command with the Horn of Africa and Sudan transferred from the United States Central Command. Responsibility for U.S. military operations in the islands of Madagascar, the Comoros, the Seychelles and Mauritius was transferred from the United States Pacific Command.

The territory of the command consists of all of the African continent except for Egypt, which remains under the direct responsibility of USCENTCOM, as it closely relates to the Middle East. USAFRICOM also covers island countries commonly associated with Africa:

February 2007 Draft Map of U.S. AFRICOM showing its creation from parts of USEUCOM, USCENTCOM and USPACOM.
U.S. AFRICOM Area of Responsibility

Geographic scope

On 1 October 2008, the command separated from USEUCOM and began operating on its own as a full-fledged combatant command. [19] as AFRICOM's first commander and AFRICOM officially became operational as a sub-unified command of EUCOM with a separate headquarters.William E. "Kip" Ward On 28 September the U.S. Senate confirmed General [18][17], the director of the AFRICOM transition team, arrived in Stuttgart, Germany to begin creating the logistical framework for the command.Robert Moeller Rear Admiral U.S. Navy [16] On [6 February 2007], Defense Secretary

[15][14]

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 



Copyright © World Library Foundation. All rights reserved. eBooks from World eBook Library are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.