Outer-Rim R&D #10
Model (Abridged): Mk. I Graviton Detector, Design Scheme No. 4Designation: Supplemental Starship Sensor; Auxiliary Targeting Engine
Research Board: Undisclosed – Bureau of Sovereignty Intelligence
Production Rights: Outer-Rim Drive Yards [All] – Secondary Distribution Restrictions Undefined (Military, Commercial, and Otherwise)
Components:
1.) System Core, Primary Interface; Unit [3’ 3’ 5’], 5th Vacant Expansion Block (Standard)
2.) Secondary Interfaces, 3; Unit [1’ 2’ 3’ Min.], 1st Bridge, 2nd-3rd Optional, Varies
3.) Reception Mounds, 3000 Nodes per, 2000+ (Varies with Vessel); Unit [1’ 1’ ½’ Overall], Varies (Equal Distribution)
4.) Integration Circuitry, –Battle Charts –Star Charts –Weapon Systems –Maneuvering Systems; Unit [Length Varies], Primary Line Conduits
5.) Static Relay Link, Linear Transmitter, 6+ (Varies with Vessel); Unit [2’ 2’ 3’ Overall], Varies (Equal Distribution)
Scanning Radius: Standard
Conventional methods of detection beginning to pale in comparison to the stealth technology rapidly reaching the assembly lines of its enemies, the Outer-Rim Sovereignty now must respond to the call for greater efficiency in the sensor capabilities available and “standard” to the vast majority of its fleets. While several previous attempts to remedy the crisis have failed, shown to come up short to the contingency safeguards of the opposition, these unintentional investigations of trial-and-error have gone to forge a new method of detection unhampered by existing masks.
While the system utilizes the newest innovations in engineering to gather and communicate its data, the technique of the collection is untraditional in its own right: the mapping of gravitational fields. Omnipresent in average conditions and, for all intensive purposes, uninfluenced by the behavior of the electromagnetic spectrum, if pinpointed to even an inexact area a graviton, when viewed with clusters of others, can shed “light” on what light cannot.
Recent advances in precision probing and surgery, though making it relatively easy to identify specifics in the attitudes of gravitational energy, can only provide sloppy, convoluted sketches of the fields that form. This information, what is received from the negative pressure calculated to pull on super-sensitive “nodes” contained in environments otherwise cleansed of natural exertions, and then applied to various algorithms detailing the known behavior of gravity, can be simplified, however, by applying the gravitic knowledge of pre-identified bodies of mass. The gravity signatures of nearby celestial bodies and vessels, for instance, can be discounted using the resources of star and battle charts, resulting in a clearer picture of the objects masked from conventional sensors. And, all the while, additional data is obtained from hidden targets employing unstable forms of gravitational masking. Due to the primary need of limiting recognition by means of the electromagnetic spectrum, a “bent space” method usually results in these vessels to bypass the latter while only hoping to bypass the former, leaving a significant loophole: when blotting-out the effects of electromagnetic sensory pulses, slight but detectable distortions surface in the seemingly nonexistent field of gravity (suspected a result of unaccounted for activity). Therefore simple devices equipped to the “mounds” of each node collective rapidly fire and scatter photons to locations inadequately touched by the light of nearby stars.
A final map is then produced by the system incorporating imprecise (albeit with a margin of uncertainty hardly greater than that of standard sensors) but accurate locations of objects hidden from primary scanners, which is then transmitted to weapon systems – automated or manned – and viewable separately or with the combined data of all probes.
Data of any step of the process can be transmitted to other starships capable of receiving standard transmissions, but in the form of more localized – and therefore defendable – signals. Information is sent in the form of “linear transmissions,” broadcast signals a great deal more concentrated, with the advantage of being easily lined with anti-jamming frequencies, however with each “beam” needing a specified target rather than a range. Every array is capable of maintaining such links with as many as 2,000 other vessels, multiple arrays connected to the same receiving target when possible, with blind spots resulting only when a direct line of contact cannot be established from any array of any transmitting starship.
Status:
Research – 20 Days, 12/2
Post-Production Installations – 5 Days, 12/7
Comments
#42 12:06am 30/11/03
Yes. I was just curious as to whether you were expanding the term "Post-Production Installation" or not.
#41 11:15pm 29/11/03
You go about applying the tech like this.
VSD under construction
900 meters = 9 day build time.
R&D #10 applied to ship: +5 days
14 day build time total
If you want to apply it to ships you already have, just run the 5 day build through for each ship it'll be applied to.
That answer the question?
#40 9:55pm 29/11/03
Ah, my mistake.
Will this apply to vessels built after the research completes, those not requiring "post-production installations"?
#39 8:11pm 29/11/03
VSD's take 9 days, shipyards now build at 100 MPD, rather than 200.
#38 5:34pm 29/11/03
Per craft, eh? Although powerful in its task, the system is really quite simple; little more complex, I would guess, than any other scanner.
I understand the motive, however. I just think that 5 days is rather steep, and that some degree of realism should be considered (an entire VSD in less time?).
Would you settle for two or three?
Also, I meant "post-production installations" as vessels receiving the system after they've been fully built, the device not having been another item on the construction checklist. Is the meaning the same when you use it "per craft"?
#37 8:45am 29/11/03
Before I forget...
"Post-Production Installations – 5 Days, 12/7"
This should read:
"Post-Production Installations – 5 Days per craft"
All other powerful upgrades like this have been getting general build time increases for the craft they are applied to, not blanket applications.
#36 10:56pm 28/11/03
Ok.
APPROVED, then.
#35 8:17pm 28/11/03
I have little doubt of the device's vulnerability to further R&D, especially in consideration of the, uh, imaginative minds that TRF has to offer. It's stated almost outright that it cannot detect what's behind a full, independent gravitational cloak (whatever that would be) without another factor coming into play.
As for evading the system without an R&D...well, I just don't know. I would guess it to be with just as much ease as evading that of the Shroud.
Just as new cloaks are meant to topple older detectors, new detectors are meant to topple older cloaks. This R&D isn't capable of halting the cycle I'm sure.
But that's a bit off topic...
Keep in mind that the R&D up for approval [i]is not[/i] a Mk. II model. If a second version does come around that closely parallels what you suggest, it would be an option to "get us" on the uberness [i]then[/i]. What is being proposed now cannot detect a turbolaser battery on a Star Destroyer, much less the ink strokes of a document aboard one.
If what you refer to by a "limited" is only a guarantee that the system will never reach that point, I'll gladly give that assurance. Our purpose isn't so much to target as it is to detect.
#34 1:45am 28/11/03
How 'bout we say we won't. Unless TNO improves their shroud. In which case it will be like the war between hackers and security companies. Action, Reaction, Action, Reaction...
#33 4:20am 27/11/03
Bhindi hasn't been promoted in years.
#32 10:26pm 26/11/03
The tech itself is fine, it's fairly plausible and well written.
My biggest concern is for its uberness. With a few adjustments, a 'mark 2' version of this could be constructed that would be able to detect anything, and still be equally plausible and well written.
I would greatly appreciate it if we could figure out some way to make it less powerful, or have some sort of limited that will keep it from becoming the uber scanner that detects when Theren picks his nose, or who Bhindi is bedding for her next promotion.
#31 9:00pm 26/11/03
I'll need one more before 12/2. Unless, of course, there are any more questions/ concerns.
#30 6:11am 19/11/03
Don't hold this to the design of the "CGT," however, unless there are verifiable similarities between the two systems in regard to the issue requiring it.
From how little I know of it, I wouldn't want a certain capability, or a lack thereof, to be wrongly transferred over.
#29 5:53am 19/11/03
<span style="font-family:helvetica; color:white;font-size:xx-large;">APPROVED</span>
#28 5:50am 19/11/03
Since the 10th or 11th in a semi-active role.
123>>>