Editing Monitor (naval concept)
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision
Your text
Line 1:
Line 1: − {{otheruses|the spacecraft design concept|other uses|Monitor}} + {{otheruses|the spacecraft design concept|other uses|Monitor (disambiguation)}} ==Overview== ==Overview== In the context of [[BattleTech]] spacecraft, the term '''Monitor''', although not clearly defined, is usually used to describe the concept of a [[WarShip]] without a [[jump drive]] core. In the context of [[BattleTech]] spacecraft, the term '''Monitor''', although not clearly defined, is usually used to describe the concept of a [[WarShip]] without a [[jump drive]] core. Line 28:
Line 28: :With the advent of the [[compact KF drive]], space became a much more dangerous place. No longer were warships limited to assault DropShips, but they could easily surpass a million tons. Yet, almost half of that mass was still tied up in the KF drive. During the latter part of the twenty-seventh century, a group of [[SLDF]] [[admiral]]s pushed to create a new breed of WarShip, dispensing with the KF drive with the goal of doubling the potential firepower such a vessel could bring to bear. After over a decade of campaigning, funding was finally allocated for project AMHITRITE and Blue Nose Clipperships won the bidding to provide construction for the prototype. :With the advent of the [[compact KF drive]], space became a much more dangerous place. No longer were warships limited to assault DropShips, but they could easily surpass a million tons. Yet, almost half of that mass was still tied up in the KF drive. During the latter part of the twenty-seventh century, a group of [[SLDF]] [[admiral]]s pushed to create a new breed of WarShip, dispensing with the KF drive with the goal of doubling the potential firepower such a vessel could bring to bear. After over a decade of campaigning, funding was finally allocated for project AMHITRITE and Blue Nose Clipperships won the bidding to provide construction for the prototype. − :Though the concept “monitor” was based on the proven hull of the venerable ''[[Avatar (WarShip class)|Avatar]]'' class cruiser, almost immediately problems emerged when the KF drive was removed from the equation. Without the frame around the KF drive acting as the ship’s primary keel, stress analysis revealed that a great deal of additional structural reinforcement would be needed to avoid integrity failure under combat thrust. The design plans were hastily re-drawn and construction resumed, but the structure reinforcements ate away far more mass than originally expected. + :Though the concept “monitor” was based on the proven hull of the venerable ''[[Avatar (WarShip)|Avatar]]'' class cruiser, almost immediately problems emerged when the KF drive was removed from the equation. Without the frame around the KF drive acting as the ship’s primary keel, stress analysis revealed that a great deal of additional structural reinforcement would be needed to avoid integrity failure under combat thrust. The design plans were hastily re-drawn and construction resumed, but the structure reinforcements ate away far more mass than originally expected. :As construction continued on three prototype hulls, the numerous setbacks and additional costs mounted, drawing greater scrutiny from a number of oversight committees. While these monitors had a potential military impact, the potential political impact of their possible failure was orders of magnitudes greater. Internal divisions, even among the Star League admiralty, quickly formed, with pro-monitor and anti-monitor camps ignoring any data that failed to agree with their positions. :As construction continued on three prototype hulls, the numerous setbacks and additional costs mounted, drawing greater scrutiny from a number of oversight committees. While these monitors had a potential military impact, the potential political impact of their possible failure was orders of magnitudes greater. Internal divisions, even among the Star League admiralty, quickly formed, with pro-monitor and anti-monitor camps ignoring any data that failed to agree with their positions. Line 46:
Line 46: ==Existing Monitors== ==Existing Monitors== Although the Monitor concept at large was refuted, a few isolated cases exist in canon that could be regarded as Monitors: Although the Monitor concept at large was refuted, a few isolated cases exist in canon that could be regarded as Monitors: − *The ''[[Bonaventure (WarShip class)|Bonaventure]]''-class corvette ''[[Sheridan (Individual Bonaventure-class WarShip)|Sheridan]]'', as of [[3067]], operates as a training ship in the [[Sol]] system. It has had its jump drive removed to make room for a full second crew and some training gear; however, it is unknown just how much of the jump drive was removed and how much room/mass the extra facilities take up.<ref>BattleCorps short story "The Last Full Measure"</ref> + *The ''[[Bonaventure]]''-class corvette ''[[Sheridan (Individual Bonaventure-class WarShip)|Sheridan]]'', as of [[3067]], operates as a training ship in the [[Sol]] system. It has had its jump drive removed to make room for a full second crew and some training gear; however, it is unknown just how much of the jump drive was removed and how much room/mass the extra facilities take up.<ref>BattleCorps short story "The Last Full Measure"</ref> − *The [[Word of Blake]]'s converted ''[[Naga (WarShip class)|Naga]]''-class [[SDS]] control ships in the [[Sol]] system were effectively monitors.<ref>''Jihad Hot Spots: Terra'', pp. 178–180</ref> + *The [[Word of Blake]]'s converted ''[[Naga (WarShip class)|Naga]]''-class [[SDS]] control ships in the [[Sol]] system were effectively monitors.<ref>''Jihad Hot Spots: Terra'', pp. 178-180</ref> *[[Battlesat]] type space stations with (limited) thrust power could also arguably be described as monitors. It should be noted that they are legal under current construction rules, but have been rendered largely moot due to their limited movement. As a consequence, it is questionable if battlesats were deployed outside of the known canonical example in the [[Luthien]] system.<ref>As explained in [http://bg.battletech.com/forums/index.php/topic,28084.0.html this thread] on the official [[BattleTech forum]]</ref> *[[Battlesat]] type space stations with (limited) thrust power could also arguably be described as monitors. It should be noted that they are legal under current construction rules, but have been rendered largely moot due to their limited movement. As a consequence, it is questionable if battlesats were deployed outside of the known canonical example in the [[Luthien]] system.<ref>As explained in [http://bg.battletech.com/forums/index.php/topic,28084.0.html this thread] on the official [[BattleTech forum]]</ref> *Despite its name, the ''[[Cockatrice]] Monitor Platform'' is technically a DropShip (its design in turn based on a [[Small Craft]], the [[K-1]] DropShuttle); while it could be described as a monitor in a functionality sense, it is not a Monitor in the design sense of being a WarShip without a jump drive core. *Despite its name, the ''[[Cockatrice]] Monitor Platform'' is technically a DropShip (its design in turn based on a [[Small Craft]], the [[K-1]] DropShuttle); while it could be described as a monitor in a functionality sense, it is not a Monitor in the design sense of being a WarShip without a jump drive core.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | {{otheruses|the spacecraft design concept|other uses|Monitor}} | + | {{otheruses|the spacecraft design concept|other uses|Monitor (disambiguation)}} |
==Overview== | ==Overview== | ||
In the context of [[BattleTech]] spacecraft, the term '''Monitor''', although not clearly defined, is usually used to describe the concept of a [[WarShip]] without a [[jump drive]] core. | In the context of [[BattleTech]] spacecraft, the term '''Monitor''', although not clearly defined, is usually used to describe the concept of a [[WarShip]] without a [[jump drive]] core. | ||
| Line 28: | Line 28: | ||
:With the advent of the [[compact KF drive]], space became a much more dangerous place. No longer were warships limited to assault DropShips, but they could easily surpass a million tons. Yet, almost half of that mass was still tied up in the KF drive. During the latter part of the twenty-seventh century, a group of [[SLDF]] [[admiral]]s pushed to create a new breed of WarShip, dispensing with the KF drive with the goal of doubling the potential firepower such a vessel could bring to bear. After over a decade of campaigning, funding was finally allocated for project AMHITRITE and Blue Nose Clipperships won the bidding to provide construction for the prototype. | :With the advent of the [[compact KF drive]], space became a much more dangerous place. No longer were warships limited to assault DropShips, but they could easily surpass a million tons. Yet, almost half of that mass was still tied up in the KF drive. During the latter part of the twenty-seventh century, a group of [[SLDF]] [[admiral]]s pushed to create a new breed of WarShip, dispensing with the KF drive with the goal of doubling the potential firepower such a vessel could bring to bear. After over a decade of campaigning, funding was finally allocated for project AMHITRITE and Blue Nose Clipperships won the bidding to provide construction for the prototype. | ||
| − | :Though the concept “monitor” was based on the proven hull of the venerable ''[[Avatar (WarShip | + | :Though the concept “monitor” was based on the proven hull of the venerable ''[[Avatar (WarShip)|Avatar]]'' class cruiser, almost immediately problems emerged when the KF drive was removed from the equation. Without the frame around the KF drive acting as the ship’s primary keel, stress analysis revealed that a great deal of additional structural reinforcement would be needed to avoid integrity failure under combat thrust. The design plans were hastily re-drawn and construction resumed, but the structure reinforcements ate away far more mass than originally expected. |
:As construction continued on three prototype hulls, the numerous setbacks and additional costs mounted, drawing greater scrutiny from a number of oversight committees. While these monitors had a potential military impact, the potential political impact of their possible failure was orders of magnitudes greater. Internal divisions, even among the Star League admiralty, quickly formed, with pro-monitor and anti-monitor camps ignoring any data that failed to agree with their positions. | :As construction continued on three prototype hulls, the numerous setbacks and additional costs mounted, drawing greater scrutiny from a number of oversight committees. While these monitors had a potential military impact, the potential political impact of their possible failure was orders of magnitudes greater. Internal divisions, even among the Star League admiralty, quickly formed, with pro-monitor and anti-monitor camps ignoring any data that failed to agree with their positions. | ||
| Line 46: | Line 46: | ||
==Existing Monitors== | ==Existing Monitors== | ||
Although the Monitor concept at large was refuted, a few isolated cases exist in canon that could be regarded as Monitors: | Although the Monitor concept at large was refuted, a few isolated cases exist in canon that could be regarded as Monitors: | ||
| − | *The ''[[ | + | *The ''[[Bonaventure]]''-class corvette ''[[Sheridan (Individual Bonaventure-class WarShip)|Sheridan]]'', as of [[3067]], operates as a training ship in the [[Sol]] system. It has had its jump drive removed to make room for a full second crew and some training gear; however, it is unknown just how much of the jump drive was removed and how much room/mass the extra facilities take up.<ref>BattleCorps short story "The Last Full Measure"</ref> |
| − | *The [[Word of Blake]]'s converted ''[[Naga (WarShip class)|Naga]]''-class [[SDS]] control ships in the [[Sol]] system were effectively monitors.<ref>''Jihad Hot Spots: Terra'', pp. | + | *The [[Word of Blake]]'s converted ''[[Naga (WarShip class)|Naga]]''-class [[SDS]] control ships in the [[Sol]] system were effectively monitors.<ref>''Jihad Hot Spots: Terra'', pp. 178-180</ref> |
*[[Battlesat]] type space stations with (limited) thrust power could also arguably be described as monitors. It should be noted that they are legal under current construction rules, but have been rendered largely moot due to their limited movement. As a consequence, it is questionable if battlesats were deployed outside of the known canonical example in the [[Luthien]] system.<ref>As explained in [http://bg.battletech.com/forums/index.php/topic,28084.0.html this thread] on the official [[BattleTech forum]]</ref> | *[[Battlesat]] type space stations with (limited) thrust power could also arguably be described as monitors. It should be noted that they are legal under current construction rules, but have been rendered largely moot due to their limited movement. As a consequence, it is questionable if battlesats were deployed outside of the known canonical example in the [[Luthien]] system.<ref>As explained in [http://bg.battletech.com/forums/index.php/topic,28084.0.html this thread] on the official [[BattleTech forum]]</ref> | ||
*Despite its name, the ''[[Cockatrice]] Monitor Platform'' is technically a DropShip (its design in turn based on a [[Small Craft]], the [[K-1]] DropShuttle); while it could be described as a monitor in a functionality sense, it is not a Monitor in the design sense of being a WarShip without a jump drive core. | *Despite its name, the ''[[Cockatrice]] Monitor Platform'' is technically a DropShip (its design in turn based on a [[Small Craft]], the [[K-1]] DropShuttle); while it could be described as a monitor in a functionality sense, it is not a Monitor in the design sense of being a WarShip without a jump drive core. | ||