Andrew Boulton wrote:
"No, it's simpler than that - there are two ships."
Mr. Boulton,
Precisely. Because an X-boat's primary 'cargo' can be transferred electronically, the idea that a newly arrived 'boat must be hurried refueled and refurbished so that it can rapidly depart is ludicrous. Passengers and parcels are incidental cargo for the 'boats. They can be collected and transferred in relative leisure. The real 'cargo' gets radioed or masered to where it needs to go.
Also, the idea that an X-boat need be separated between two different modules is laughable. An engineering section comprised of 'only' fuel and drives would still displace over 75% of an X-boat's volume. Why add the complexity of 'fast fuelers' shuttling around three quarters of an X-boat and hurriedly readying a newly arrived 'boat for departure when simply having 100% of another X-boat on hand and waiting for a message download would get the job done?
The 'frenetic' operational vision of the X-boat network presented here lately is unnecessarily complex, hideously inefficient, and almost completely wrong on every level. At the very least, it betrays a complete lack of understanding with regards to the very nature of jump drive and the operational tempo of the network.
The X-boat network does not operate frenetically. Given the nature of jump drives, it cannot operate that way. Multiple departures within a short time span; the 'reasoning' behind 'fast fuelers', plug n' chug engineering modules, and all that other nonsense, simply do not occur. Why? Because of the jump drive's temporal accuracy, that's why.
Jump lasts 168 hours - plus and minus 10%. A vessel's arrival window is then 33.6 hours wide. Multiple departures to the same destination within a single day means you run the risk of having the 1500 Hour 'boat arrive before the 0900 Hour 'boat. Single departures each standard day obviates that risk. As the average system hosting an X-boat station is only linked to two other systems, that system will only see two arrivals and two departures every 24 hours. That isn't frenetic, that isn't even busy. It rates as downright sleepy.
While the temporal accuracy of jump drive limits the amount of work required every 24 hours of each tender, the physical accuracy of jump drive makes that work even easier. Jumps are accurate to within 3000km of every parsec jumped. Given that the maximum possible jump by an X-boat is 4 parsecs, the arrival area will be a sphere of only a 12K-km radius. You can even increase that by an order of magnitude; 120K km - call it sloppy navigation, and still have trivial area in which the tender need operate.
The X-Boat Station Operating Region of an average system will be ~250K diameter sphere. The Region will be placed well above or below the system ecliptic in order to avoid any jump masking or shadowing concerns. Within the Region, a single tender awaits the arrival of two X-boats each standard day. For systems with more than two links, additional Operating Regions patrolled by additional tenders are set up.
As each boat arrives, the tender moves to intercept as the 'boat downloads its message load. The tender strips out any messages for the local system, adds any outgoing messages to the traffic queue, and rebroadcasts the entire package to a previously refueled and refurbished X-boat waiting to depart.
After the intercept, the newly arrived 'boat is refueled, personnel swaps occur, any scheduled maintenance done, and the occasional passenger or package collected. Sometimes, more extensive maintenance is required, the offending X-boat is brought aboard the tender, and another X-boat simply moves up in the queue of those waiting to depart.
X-boats ready for departure; those 'on-deck', are given a final check and placed on whatever normal space vector their destination system may require. The 'boat and her pilot simply wait for the next arrival, download their message 'cargo', hit the switch, and jump away.
Each standard day, 2 'boats arrive, 2 'boats are refueled and refurbished, and 2 'boats depart. It is steady. It is workman-like. It is nearly serene. Two arrive, two are caught, and two depart each and every standard day. High points of each week will include the visit by the in-system tanker topping off the tender's fuel stores and dropping off supplies or the occasional scout-courier summoned to collect the odd package or passenger or tasked with a message load due at a non-Network system. It is boring and, despite the logo, it is definitely not the Pony Express.
So the X-boat Network isn't some hurly-burly, turn-em-around-quick, dozens of 'boats coming and going kind of affair. The nature of jump drive won't allow that and the nature of the X-boat Network doesn't require it. You see, the X-Boat Network isn't a communications system, it is a control system. Any message that must be transmitted as rapidly as possible doesn’t go on the X-Boats. The Emperor, the nobility, the Navy, the megacorps, everyone who can afford it, they all have jump6 couriers. The X-boat system is for everyone and everything else.
Sincerely,
Larsen
"No, it's simpler than that - there are two ships."
Mr. Boulton,
Precisely. Because an X-boat's primary 'cargo' can be transferred electronically, the idea that a newly arrived 'boat must be hurried refueled and refurbished so that it can rapidly depart is ludicrous. Passengers and parcels are incidental cargo for the 'boats. They can be collected and transferred in relative leisure. The real 'cargo' gets radioed or masered to where it needs to go.
Also, the idea that an X-boat need be separated between two different modules is laughable. An engineering section comprised of 'only' fuel and drives would still displace over 75% of an X-boat's volume. Why add the complexity of 'fast fuelers' shuttling around three quarters of an X-boat and hurriedly readying a newly arrived 'boat for departure when simply having 100% of another X-boat on hand and waiting for a message download would get the job done?
The 'frenetic' operational vision of the X-boat network presented here lately is unnecessarily complex, hideously inefficient, and almost completely wrong on every level. At the very least, it betrays a complete lack of understanding with regards to the very nature of jump drive and the operational tempo of the network.
The X-boat network does not operate frenetically. Given the nature of jump drives, it cannot operate that way. Multiple departures within a short time span; the 'reasoning' behind 'fast fuelers', plug n' chug engineering modules, and all that other nonsense, simply do not occur. Why? Because of the jump drive's temporal accuracy, that's why.
Jump lasts 168 hours - plus and minus 10%. A vessel's arrival window is then 33.6 hours wide. Multiple departures to the same destination within a single day means you run the risk of having the 1500 Hour 'boat arrive before the 0900 Hour 'boat. Single departures each standard day obviates that risk. As the average system hosting an X-boat station is only linked to two other systems, that system will only see two arrivals and two departures every 24 hours. That isn't frenetic, that isn't even busy. It rates as downright sleepy.
While the temporal accuracy of jump drive limits the amount of work required every 24 hours of each tender, the physical accuracy of jump drive makes that work even easier. Jumps are accurate to within 3000km of every parsec jumped. Given that the maximum possible jump by an X-boat is 4 parsecs, the arrival area will be a sphere of only a 12K-km radius. You can even increase that by an order of magnitude; 120K km - call it sloppy navigation, and still have trivial area in which the tender need operate.
The X-Boat Station Operating Region of an average system will be ~250K diameter sphere. The Region will be placed well above or below the system ecliptic in order to avoid any jump masking or shadowing concerns. Within the Region, a single tender awaits the arrival of two X-boats each standard day. For systems with more than two links, additional Operating Regions patrolled by additional tenders are set up.
As each boat arrives, the tender moves to intercept as the 'boat downloads its message load. The tender strips out any messages for the local system, adds any outgoing messages to the traffic queue, and rebroadcasts the entire package to a previously refueled and refurbished X-boat waiting to depart.
After the intercept, the newly arrived 'boat is refueled, personnel swaps occur, any scheduled maintenance done, and the occasional passenger or package collected. Sometimes, more extensive maintenance is required, the offending X-boat is brought aboard the tender, and another X-boat simply moves up in the queue of those waiting to depart.
X-boats ready for departure; those 'on-deck', are given a final check and placed on whatever normal space vector their destination system may require. The 'boat and her pilot simply wait for the next arrival, download their message 'cargo', hit the switch, and jump away.
Each standard day, 2 'boats arrive, 2 'boats are refueled and refurbished, and 2 'boats depart. It is steady. It is workman-like. It is nearly serene. Two arrive, two are caught, and two depart each and every standard day. High points of each week will include the visit by the in-system tanker topping off the tender's fuel stores and dropping off supplies or the occasional scout-courier summoned to collect the odd package or passenger or tasked with a message load due at a non-Network system. It is boring and, despite the logo, it is definitely not the Pony Express.
So the X-boat Network isn't some hurly-burly, turn-em-around-quick, dozens of 'boats coming and going kind of affair. The nature of jump drive won't allow that and the nature of the X-boat Network doesn't require it. You see, the X-Boat Network isn't a communications system, it is a control system. Any message that must be transmitted as rapidly as possible doesn’t go on the X-Boats. The Emperor, the nobility, the Navy, the megacorps, everyone who can afford it, they all have jump6 couriers. The X-boat system is for everyone and everything else.
Sincerely,
Larsen