Talk:Force XXI Battle Command Brigade and Below

Article title

Seems to be the article should be titled "FBCB2" as opposed to "Force XXI Battle Command Brigade and Below" since FBCB2 is how it is most commonly referred (per WP:COMMONNAMES). — X96lee15 (talk) 16:41, 16 September 2009 (UTC)

We very rarely use abbreviations rather than the full name. DJ Clayworth (talk) 16:55, 16 September 2009 (UTC)

@X96lee15, in response to your suggestion, it looks like @DJ Clayworth correctly created a REDIRECT link that points to this article. So, anyone searching for FBCB2 will automatically find the page with the longer title. — TadgStirkland⁴⁰¹ (Tadg^Talk) 19:15, 11 August 2024 (UTC)

Merger proposal

The following discussion is an archived discussion of a

Merge Proposal and / or Redirect. Please do not modify it.
The result of the request for the Proposed Merger of Project Manager Force XXI Battle Command Brigade and Below into this talk page's article was:

Not Done—No Consensus to Merge.
— — — — —

Went to do this 4-year (Dec 2009) pending merger request: Merge from Project Manager Force XXI Battle Command Brigade and Below into Force XXI Battle Command Brigade and Below and there is now some question about over-lap. Also, the tag is missing from the merge-source document. I am re-listing at the Wikipedia:Proposed mergers site and dating to current as we are trying to wrap up 2009. Discussion can take place here. Thank you. GenQuest ^{"Talk to Me"} 04:06, 29 April 2013 (UTC)

Oppose. Why Merge? The PM for FBCB2 and the system are two separate things entirely. The PM just manages the program while the System itself are the different components and the functions those components can do. I have personal experience working army acquisition and can testify that the systems and PM are related but separate and distinct. The only reason I could think of for merging the topics is if the view were taken that the PM and the system are inextricably linked, which is generally not the case. The FBCB2 PM manages all the sub-systems of FBCB2 as well as the overall program. Each sub-system can and often is eventually handled by a different PM making a sub-structure of project managers who oversee development not every sub-system will eventually get fielded. The system itself is what eventually gets fielded and used by the force.Scout1067 (talk) 07:46, 14 May 2013 (UTC)

— — — — —
The above discussion is preserved as an archive of a WP:PM.

Please do not modify it.
Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

GenQuest ^{"Talk to Me"} 13:28, 11 June 2013 (UTC)

A copy of this template can be found here.

Linux

I removed "Linux-based" from the header because 1. it's unreferenced and 2. for everybody except a computer nerd it's an important aspect of the system. If somebody finds a reference please put the information back but not in the intro. DJ Clayworth (talk) 13:39, 30 August 2024 (UTC)

AN/GYK-55 FBC2B2 Create Device

I have 2 questions for anyone who may know... The ARMY TM 11-7010-346-13&P manual cited at the end of the first sentence of the article says on page 0002-1 (page 39 of the PDF file), The Ruggedized Laptop Computer is also referred to as the "FBCB2 Create Device" or simply as the "Create Device." Why is the AN/GYK-55 computer called "FBC2B2 Create Device" or "Create Device"? Where does the term "Create Device" originate? It doesn't seem to denote computer in any way. Anyone know? Also, is the GYK-55 actually the entire FBCB2 by itself? — TadgStirkland⁴⁰¹ (Tadg^Talk) 23:21, 6 September 2024 (UTC)