Mark 1 Active Repair System: Difference between revisions

From Solas Tempus DB
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
The Mark 1S repair system is designed to manage and deploy the [[Mark 1S Active Repair Drone]]Controlling via the ships computer or [[MSAI]]. The repair system involves upgrades to internal sensors and additional components for the management of and deploying of individual drones to different areas.  Also included are docking and staging areas placed at strategic points within a vessel or facility from which drones will be deployed.  Finally upgrades to the internal communication network and relay systems will also be provided to support drone communication channels.
{{DEFAULTSORT:Active Repair System, Mark 1}}The Mark 1 Active Repair System is designed to manage and deploy automated repair systems aboard a starship or facility.  While the prototype of this system (the Mark X) only used the Mark 1S drones, this version is capable of coordinating repair using all of a vessel's potential automated repair systems with a more varied approach to repair managementIn general the Mark 1 is designed to be controlled primarily by a ships onboard computer or [[MSAI]].   The repair system involves upgrades to internal sensors and additional components for the management of and deploying of individual drones to different areas.  Also included are docking and staging areas placed at strategic points within a vessel or facility from which drones will be deployed.  Finally upgrades to the internal communication network and relay systems will also be provided to support drone communication channels.
 
== Automated Repair Systems ==
These automated repair systems are capable of being managed and deployed by the Mark 1 system.
* [[Astromech Droid]]
* [[Mark 1S Active Repair Drone]]
* [[Mark 1D Active Repair Drone]]
* [[Mark 2D Active Repair Drone]]
* [[Mark 1R Active Repair Drone]]
* [[Automated Service Robot]]


== Command and Control ==
== Command and Control ==
Line 5: Line 14:


During normal operations the ships Chief Engineer and Operations Officer will set system priorities both in general and for specific situations.
During normal operations the ships Chief Engineer and Operations Officer will set system priorities both in general and for specific situations.
=== Regional Control & Management ===
On large installations the primary command and control system can assign regional repair control centers, usually using either secondary AI's and / or the Astromech Droid.  Even with smaller installations an Astromech is capable of taking over primary control of the repair system and control / deploy its various parts.  On some installations, such as the X-Wing Fighter, which use an Astromech for an onboard computer the Astromech manages the on board repair system by design.
For complex repairs, constructions, or other projects regional control zones and jobs are dynamically set up by the central control computer.  These regional management centers control particular jobs or manage the repair of specific regions of a vessel or facility.
=== Cross Facility / Vessel Operations ===
While more rare in any specific, control computers can network and coordinate repair operations between installations.  For fleet deployments and during combat, the active repair systems of multiple vessels can make command crews aware of repair status of various ships.  Protocol dictates that either an MSAI or [[XIA]]s actively collate information on vessels, facilities, and other installations to make available for command staff upon request.  This coordination allows for easier deployment of resources and more effective repair operations.  The Operations Officer of a vessel / facility would then manage the deployment of resources within the regular command structure.
== Small Installations ==
On especially small installations the drones will be placed at key areas and there will not be a staging area but rather special transceiver assemblies at those key locations.  This is the case for things like fighters, shuttles, and smaller runabouts where space is at a premium and the internal systems are not accessible during operation.  In these cases the pilot has the ability to direct repair operations from the cockpit or a support vessel for a fighter or shuttle group may also do so.
Many smaller vessels lack advanced computer systems, so drone operations are often reliant upon their automated directives.  The Operations Officer or Wing Commander may set broad policies for drones within fighters as well as auxiliary craft to permit the drones to continue automated repair functions without pilot intervention.
== Remote Deployment ==
Each staging area is equipped with micro [[transporter]] nodes connected to ships power, though this is missing from smaller installations, larger vessels even have dedicated power supplies for staging areas.  This allows drones to be deployed into areas of the facility which are otherwise inaccessible.  During routine repair and maintenance the use of these systems can significantly increase the effectiveness of both automated repairs as well as routine maintenance without bothering the crew.  These nodes are understandably low-power and thus short range.  The pattern buffers in use are only large enough for 1 or 2 drones at a time.  These nodes can only beam to locations inside the ship or on the outer hull, not to planets or distant locations.


== Drone Compliments ==
== Drone Compliments ==

Latest revision as of 00:23, 30 August 2023

The Mark 1 Active Repair System is designed to manage and deploy automated repair systems aboard a starship or facility. While the prototype of this system (the Mark X) only used the Mark 1S drones, this version is capable of coordinating repair using all of a vessel's potential automated repair systems with a more varied approach to repair management. In general the Mark 1 is designed to be controlled primarily by a ships onboard computer or MSAI. The repair system involves upgrades to internal sensors and additional components for the management of and deploying of individual drones to different areas. Also included are docking and staging areas placed at strategic points within a vessel or facility from which drones will be deployed. Finally upgrades to the internal communication network and relay systems will also be provided to support drone communication channels.

Automated Repair Systems

These automated repair systems are capable of being managed and deployed by the Mark 1 system.

Command and Control

The drones are dependant on a central computer for control and will have a dedicated ODN line from each drone staging area to the central computer, which serves as a backup if on board communications have failed. In addition each drone staging area can be fed commands directly from its own control console to direct the drones connected to that staging area. If internal communications are down, each staging area has its own short-range transceiver to maintain a connection to the mesh network of the drones themselves. Using the mesh network established by the drones it is possible to coordinate a large number of drones from one staging area console. Drones can also be directed to focus repairs on a specific system from such a console if there is a failure of the main computer in order to coordinate the drones in making repairs.

During normal operations the ships Chief Engineer and Operations Officer will set system priorities both in general and for specific situations.

Regional Control & Management

On large installations the primary command and control system can assign regional repair control centers, usually using either secondary AI's and / or the Astromech Droid. Even with smaller installations an Astromech is capable of taking over primary control of the repair system and control / deploy its various parts. On some installations, such as the X-Wing Fighter, which use an Astromech for an onboard computer the Astromech manages the on board repair system by design.

For complex repairs, constructions, or other projects regional control zones and jobs are dynamically set up by the central control computer. These regional management centers control particular jobs or manage the repair of specific regions of a vessel or facility.

Cross Facility / Vessel Operations

While more rare in any specific, control computers can network and coordinate repair operations between installations. For fleet deployments and during combat, the active repair systems of multiple vessels can make command crews aware of repair status of various ships. Protocol dictates that either an MSAI or XIAs actively collate information on vessels, facilities, and other installations to make available for command staff upon request. This coordination allows for easier deployment of resources and more effective repair operations. The Operations Officer of a vessel / facility would then manage the deployment of resources within the regular command structure.

Small Installations

On especially small installations the drones will be placed at key areas and there will not be a staging area but rather special transceiver assemblies at those key locations. This is the case for things like fighters, shuttles, and smaller runabouts where space is at a premium and the internal systems are not accessible during operation. In these cases the pilot has the ability to direct repair operations from the cockpit or a support vessel for a fighter or shuttle group may also do so.

Many smaller vessels lack advanced computer systems, so drone operations are often reliant upon their automated directives. The Operations Officer or Wing Commander may set broad policies for drones within fighters as well as auxiliary craft to permit the drones to continue automated repair functions without pilot intervention.

Remote Deployment

Each staging area is equipped with micro transporter nodes connected to ships power, though this is missing from smaller installations, larger vessels even have dedicated power supplies for staging areas. This allows drones to be deployed into areas of the facility which are otherwise inaccessible. During routine repair and maintenance the use of these systems can significantly increase the effectiveness of both automated repairs as well as routine maintenance without bothering the crew. These nodes are understandably low-power and thus short range. The pattern buffers in use are only large enough for 1 or 2 drones at a time. These nodes can only beam to locations inside the ship or on the outer hull, not to planets or distant locations.

Drone Compliments

The size of a vessel directly impacts how many drones it needs and will support. Different vessels and facilities require different numbers to balance out internal space utilized by the drones and their equipment with how likely systems are to require repair without intervention. In particular fighters and auxiliary craft which can be especially prone to damage require potentially more support but also have limited internal spaces within which to work.

Category Drones Compliment Guidelines Classes
Large Facilities 1000+ 1 Drone per 10 Meters in Length Space Docks and Ground Facilities
Mobile Bases 1000+ 1 Drone per 8 Meters in Length Atlantis Class, Icarus Class, etc..
Small Facilities ~60 1 Drone per 4 Meters in Length Class K, Class 2, or Similar Space Stations
Capital Ships 140 to 210 1 Drone per 3 Meters in Length Galaxy Class, Nebula Class, etc..
Frigates 90 to 120 2 Drones per 5 Meters in Length Miranda Class, Steamrunner Class, etc..
Large Scout ~50 1 Drone per 5 Meters in Length Saladin Class Starship and Similar
Small Scout 12 to 35 1 Drone per 2 Meters in Length Archer Class, Kestrel Class, etc..
Auxiliary Ships 2 to 8 1 Drone per 3 Meters in Length Danube Class, Venture Class, and Shuttles
Fighters 3 to 5 1 Drone per 4 Meters in Length Valkyrie, Thunder, Gunstar, etc..