DERP.
I have made an error of assumption on the availability of the Jump Tender and its capacity for transits, which then has knock on effects for the capacity of Boughene Station itself.
Let's start with the map.
The primary "route of concern" for the Boughene Station Jump Tender is between Boughene and Efate to be running station modules to/from Efate for annual overhaul maintenance and to deliver exports of raw materials extracted from the Boughene system to fund operations of Boughene Station. Boughene may be politically included in the County of Menorb but economically speaking Boughene is functionally a "colony producer" for industry on Efate.
My original assumption was to simply have the Jump Tender do this:
- Jump-2 from Boughene to Efate with Starport Module plus 2 Cargo Modules (1 week)
- Remain at Efate waiting for annual overhaul maintenance of Starport Module (optional, plus 2 Cargo Modules) to be completed (1 week)
- Remain at Efate waiting for annual overhaul maintenance of Starport Module (optional, plus 2 Cargo Modules) to be completed (1 week)
- Jump-2 from Efate to Boughene with (maintained) Starport Module plus 2 Cargo Modules (1 week)
Wash, rinse, repeat.
Such an operational cycle would necessarily mean that the Jump Tender would be capable of transporting 12-13 Starport Modules per year to Efate for annual overhaul maintenance ... hence why I set up the assumptions for Boughene Station to have 10 type B Starport Modules (maintenance only) and 3 type A Starport Modules (maintenance and construction) with the type B Starport Modules almost completely occupied with performing rotating maintenance of the 500 Secondary Modules (habitat, commerce, industry, research, cargo, fuel, etc.) which then makes up the rest of Boughene Station. With 13 Starport Modules in total and 1 Starport Module "unavailable" on a rotating basis for transit to Efate for annual maintenance, that then left 12 Starport Modules "available at all times, of which 10 would be involved at all times in rotating annual maintenance of the 500 Secondary Modules, consuming their supply of services permanently. This in turn would then leave 2 Starport Modules "available" for interstellar support services, giving the "starport" at Boughene a 2x 20,000 ton capacity for shipyard services.
So ... on a 1 month round trip cadence with the Jump Tender, 12-13 Starport Modules could be supported indefinitely ... so long as the Jump Tender "stays with" the Starport Module sent to Efate for annual maintenance.
With me so far on the logistics constraint?
But then I started thinking that such an arrangement might be decidedly suboptimal.
Why?
Because it has the Jump Tender "sitting around" for 2 weeks out of every 4 weeks "doing nothing" at Efate simply waiting for the annual overhaul maintenance cycle on the current Starport Module to complete before hauling the (freshly cleaned) Starport Module back to Boughene.
It also doesn't help that loading and unloading the starport modules probably doesn't happen in zero time (docking a 100,000 ton starship to a 50,000 ton non-starship for transport can take some maneuvering time) and transits from 100 diameters away to the mainworld is also not going to happen in zero time (especially at Boughene, a moon of a gas giant) and refueling operations are not going to happen in zero time ... I think you can see where I'm going with this. An assumption of 4 weeks per round trip from Boughene to Efate back to Boughene will very likely take longer than 4 weeks (28 days). For one thing, jump duration varies from 150-175 hours ... and if you include 16 hours of routine drive checks after jump that's then 166-191 hours (168 hours = 7 days, 192 hours = 8 days).
So a much more reasonable assumption is 1 day to dock/load and maneuver to the jump point, 8 days of jump plus drive maintenance, 1 day to maneuver to the mainworld in order to undock/unload. In other words, a 10 days per jump operational cycle.
10 days per jump operational cycles amounts to a total capacity of 36 jumps per year (365 days per year).
Considering that the Jump Tender itself will need to be taken offline for 2 weeks of annual maintenance itself, that necessarily reduces the availability of the Jump Tender down to 350 days per year (discounting 1 day for the annual holiday every year), and to build in some "padding" into the schedule for unanticipated delays in the scheduling, let's call it 320-330 days per year are available for Jump Tender operations.
320 / 10 days = 32 jumps per year
330 / 11 days = 30 jumps per year
336 / 12 days = 28 jumps per year
So, just to be kind to the logistics people who are going to have to keep these plates spinning all the time, let's call it an 11 day jump cycle with 30 jumps per year by the Jump Tender. That then means 15 jumps to Efate and 15 jumps to Boughene every year for "regular service" with an "extended stay" at Efate by the Jump Tender for the Jump Tender's own annual maintenance cycle ... and there are 35 days remaining past the 330 days allocated which is sufficient for a standard 2x 11 days plus 14 days in drydock (total 35 days, oh hey lookee here...). That then makes for a total of 16 complete round trips per year between Boughene and Efate as a maximum cadence.
However, in order to make that 16 round trips per year (including the annual maintenance of the Jump Tender) "work" the Jump Tender is going to need to "leave" Starport Modules at Efate and essentially "round robin" them for deployment to Efate for annual maintenance.
Remember the assumption I was making above?
Having the Jump Tender do this:
- Jump-2 from Boughene to Efate with Starport Module plus 2 Cargo Modules (1 week)
- Remain at Efate waiting for annual overhaul maintenance of Starport Module (optional, plus 2 Cargo Modules) to be completed (1 week)
- Remain at Efate waiting for annual overhaul maintenance of Starport Module (optional, plus 2 Cargo Modules) to be completed (1 week)
- Jump-2 from Efate to Boughene with (maintained) Starport Module plus 2 Cargo Modules (1 week)
Take that assumption and change it to be something more like this:
- Load Starport Module 1 plus Cargo Modules 1+2 onto Jump Tender, maneuver to Jump Point, Jump-2 to Boughene, maneuver to Boughene, undock Starport Module 1 plus Cargo Modules 1+2 at Boughene Station (11 days)
- Load Starport Module 3 plus Cargo Modules 5+6 onto Jump Tender, maneuver to Jump Point, Jump-2 to Efate, maneuver to Efate, undock Starport Module 3 plus Cargo Modules 5+6 at Efate Shipyard (11 days)
- Load Starport Module 2 plus Cargo Modules 3+4 onto Jump Tender, maneuver to Jump Point, Jump-2 to Boughene, maneuver to Boughene, undock Starport Module 2 plus Cargo Modules 3+4 at Boughene Station (11 days)
- Load Starport Module 4 plus Cargo Modules 7+8 onto Jump Tender, maneuver to Jump Point, Jump-2 to Efate, maneuver to Efate, undock Starport Module 4 plus Cargo Modules 7+8 at Efate Shipyard (11 days)
Wash, rinse, repeat.
Now, with 16 round trip cycles like that per year, staggering the "swap" of Starport Modules at Efate every 22 days (so as to give the Efate shipyard a little "squoosh factor" on when they get started after drop off before they start the 14 day/2 week overhaul procedure) Boughene Station would be capable of supporting 16 Starport Modules (instead of merely 13) per Jump Tender ... which is where things get interesting.
With an extra 3x type A Starport Modules added ... so 6x type A and 10x type B ... Boughene Station would have construction capacity (type A) for a combined 120,000 tons of starship(s) ... which, incidentally, is enough for Boughene Station to
not need to export their annual maintenance needs to Efate anymore ... since they would be capable of maintaining Boughene Station "organically" with in-situ resources and still have sufficient capacity to service external trading demand for services.
Boughene Station (and the system as a whole) would still be classified as Non-industrial and in need of imports of PARTS (electronic, mechanical, cybernetic, computer, machine per the speculative cargo table in LBB2.81) ... but would have sufficient Starport Modules to be able to "build and maintain" their Starport Modules (and all other Secondary Modules) entirely in-system using the available Starport Module capacity to maintain EVERYTHING.
In other words, with just a few more Starport Modules, which Boughene Station would be capable of supporting on an annual overhaul maintenance rotation to Efate ... Boughene Station would be on the verge of a "breakout" situation in terms of long term sustainability.
Meaning, that if the Fifth Frontier War hadn't happened (to set Boughene Station back) it's entirely possible that with just a little more investment by the oligarchs in control of Boughene Station that the station would have been well positioned to grow and expand into the future. Such an expansion would have increased the demand for labor, raised the standards of living and put Boughene on track to growing into a population code: 6 in less than 10 years after 1105.