I saw that example over on the BT forums, and it's an interesting one. Edit: Your most recent post over in that 3250 thread does a great job of explaining more info on the breakdown of SFB and the various different games. Thanks for that. I'm not familiar with ADB and that pairing of games. How does the number of products (and type) per year compare to CGL? And company/staffing size compare? Are those game lines producing similar types of resource intensive sourcebooks, requiring the level of fact-checking and oversight? I'm sure that there are ways that a dual development scheme could work. I'm just not convinced that such a practice can work with the situation CGL currently finds itself in (specifically, the production backlog, extremely limited staff/freelancer support, resources already stretched between SR and BT, and the unit creation software issue).
I'm glad someone noticed it! (It is a little disheartening to write up so much and not get noticed, but the thread seemed to be going in a new direction. Perhaps I'd be as well to delete that post and re-enter it as its own thread? But anyway.)
At this point, there are three companies involved with the Star Fleet Universe, in one way or another. (In a game design terms, at least; minis are another matter.)
Amarillo Design Bureau look after
Star Fleet Battles,
Federation Commander, and a series of other "in-house" game systems (such as the strategic wargame
Federation and Empire, and the recently-released
Star Fleet Marines ground combat game engine). They have a print-on-demand system which allows them to print their own black-and-white rulebooks directly, but they have to order colour works (book covers, countersheets, hex maps, laminated Ship Cards for
Federation Commander modules, etc) from an outside source. Also, the older Starline 2400 series of minis are ordered from a casting company. I want to say Reaper do it, but I'm not too sure off of the top of my head.
In terms of product printing, ADB tend to batch main line items based on the countersheets needed to support them. For example, the counters for the recently-published
FC: Reinforcements Attack were done at the same time as the upcoming
Star Fleet Marines: Last Stand, as well as (I think) those for the also-upcoming
SFB Module C6. Also, there are a number of uploads to e23, as well as a new issue of the
Captain's Log magazine every six months or thereabouts.
(I don't work for ADB, so I can't give a definite answer on that front; but there should be more accurate information over on their own site.)
Majestic 12 Games run
Starmada (in is various incarnations), and signed an agreement with ADB a few years back which allows them to port the setting into their game engine/s. I don't know what kind of printing setup they themsevles have, but I know that ADB use their own POD system for the books from the Star Fleet adaptation.
Mongoose Publishing are over in the UK, and have been around for a while now in their own right. (They used to hold the
Babylon 5 licence, and inherited some of the old minis from
Babylon 5 Wars when establishing the
B5 edition of the
A Call to Arms game engine.) As part of the joint venture with ADB, Mongoose run
A Call to Arms: Star Fleet (one of two games which currently use the same game engine; the other being an adaptation of
Holistic Design's
Noble Armada, which is set in the
Fading Suns RPG universe being handled by
FASA 2.0) and the Starline 2500 miniature line, and will be printing an edition of the
Traveller engine for the
Prime Directive RPG line. They printed a hardback rulebook for
ACtA:SF, which is partially in colour; though ADB will be doing the printing for
Traveller: Prime Directive.
(The main difference between
Starline 2400 and
Starline 2500 is that the former were hand-sculpted, while the latter are all done using 3D models. Well, the 2500s are also a slightly bigger size.)
By and large, MJ12 does much of the running for Star Fleet
Starmada, while Mongoose handle the development of
ACtA:SF; but at each stage of development, both companies have to defer to ADB's oversight in order to ensure the setting remains consistent. (The to-and-fro-ing is much more active in the latter case, since the joint venture with Mongoose is significantly more involved than the agreement with MJ12.)