Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Comm-Link:Galactic Guide - WillsOps Systems

From the Star Citizen Wiki, the fidelity™ encyclopedia
Comm-Link-WillsOp Logo 13a.jpg
Galactic Guide: WillsOps Systems
SeriesGalactic Guide
TypeSpectrum Dispatch
ID14065
Published2014-08-05
SourceGalactic Guide: WillsOps Systems
In the series
Title Published
Galactic Guide: Anvil Aerospace 2013-04-23
Galactic Guide - Earth & New Jump Point 2013-05-31
Galactic Guide - Stanton System 2013-07-12
Galactic Guide - Hurston Dynamics 2013-07-23
Galactic Guide - Terra 2013-07-26
Galactic Guide: Oberon System 2016-07-23
Galactic Guide: Banshee System 2016-06-22
Galactic Guide: Nemo System 2016-06-15
Galactic Guide: Chronos System 2016-05-05
Galactic Guide: Kayfa 2016-04-06
Galactic Guide: Croshaw System 2015-10-20
Galactic Guide: Kastak Arms 2015-10-06
Galactic Guide: Ferron System 2015-10-06
Galactic Guide: Osiris System 2015-08-07
Galactic Guide: Castra System 2015-08-05
Galactic Guide: Kruger Intergalactic 2015-07-29
Galactic Guide: ArcCorp 2015-04-29
Galactic Guide: Vega System 2015-04-22
Galactic Guide: Tyrol System 2015-04-15
Galactic Guide: 78th Squadron 2015-04-08
Galactic Guide: Helios System 2015-03-15
Galactic Guide: Accelerated Mass Design 2015-03-08
Galactic Guide: Virgil System 2015-02-19
Galactic Guide: Squad 214, Bravo Flight 2015-02-05
Galactic Guide: Hades System 2015-01-07
Galactic Guide: Nyx 2015-01-01
Galactic Guide: Sakura Sun 2014-12-30
Galactic Guide: Gold Horizon 2014-12-23
Galactic Guide: 36th Fighter Squadron 2014-11-20
Galactic Guide: Nul System 2014-11-19
Galactic Guide: GNP 2014-11-12
Galactic Guide: Taranis 2014-10-29
Galactic Guide: Baker System 2014-10-15
Galactic Guide: The Murray Cup 2014-10-01
Galactic Guide: Consolidated Outland 2014-09-23
Galactic Guide: Bremen 2014-09-16
Galactic Guide: WillsOps Systems 2014-08-05
Galactic Guide: Rihlah System 2014-07-29
Galactic Guide: Stor-All 2014-06-17
Galactic Guide: Corel System 2014-06-10
Galactic Guide: Behring Applied Technology 2014-05-27
Galactic Guide: Original Systems 2014-05-20
Galactic Guide: Pyro 2014-05-06
Galactic Guide: Odin 2014-04-15
Galactic Guide: Tiber 2014-03-04
Galactic Guide: Davien 2014-02-11
Galactic Guide: Aegis Dynamics 2014-01-30
Galactic Guide: Drake Interplanetary 2014-01-08
Galactic Guide: Magnus 2014-01-02
Galactic Guide: MISC 2013-12-19
Galactic Guide: Centauri 2013-12-10
Galactic Guide: Goss 2013-12-02
Galactic Guide: Klaus & Werner 2013-10-28
Galactic Guide: Ellis System 2013-10-07
Galactic Guide: Hangar Manufacturers 2013-09-30
Galactic Guide: Kilian System 2014-12-23
Galactic Guide: ORIGIN 2013-08-02
Galactic Guide: Horus System 2016-02-09
Galactic Guide: Nexus System 2015-12-22
Galactic Guide: Orion System 2013-06-17
Galactic Guide: Oso System 2015-07-08
Galactic Guide: Tayac 2016-02-03
Galactic Guide: Cubby Blast 2015-07-17
Galactic Guide: Covalex Shipping 2015-06-26
Galactic Guide: Cathcart System 2013-04-16
Galactic Guide: Kellog System 2018-01-10
Galactic Guide: Caliban System 2018-04-11
Galactic Guide: Tal System 2018-03-14
Galactic Guide: Leir System 2018-10-17
Galactic Guide: Kiel System 2018-12-12
Galactic Guide - Kabal System 2019-01-09
Galactic Guide: Kallis System 2019-04-03
Galactic Guide: Gliese System 2019-07-03
Galactic Guide: Garron System 2019-06-12
Galactic Guide: Min System 2019-12-11
Galactic Guide: Rhetor System 2015-11-10

Company History

WillsOp is a Croshaw-based limited liability corporation established in 2902 for the express purpose of developing starship targeting system software. WillsOp’s critical feature was a unique, if unappreciated, one: they adhered to a strict ‘made here’ philosophy. Unlike every other sensor company on the market at the time, WillsOp used absolutely no shared source code. The result was a more stable platform, but also a closed one which could not easily integrate outside enhancements.

The corporation’s first project was a multi-million UEC bid to develop sensor rigging for the UEE Navy’s Carrier-Based Strike contract, the spacecraft design proposal which ultimately resulted in the Gladiator bomber. Lacking name recognition and any sort of technological pedigree, WillsOp’s bid failed in favor of the DiSys D-33 MultiSuite (long since replaced on active duty Gladiators). The company’s founders briefly considered disbanding, but ultimately decided that they believed in the product too much to let their first loss define them.

With that defeat, WillsOp settled in for the long haul, competing on the civilian market as a ‘higher end’ third-party upgrade option. For two decades, the company went largely unnoticed. It signed no first-party contracts and was viewed (by that small portion of the public which considers starship sensor manufacturers at all) as a reliable but generally unspectacular option. That all suddenly changed in 2922.

On August 9, 2922, a digital plague began to spread from spacecraft to spacecraft. Broadcast from an unmarked sensor buoy parked in geostationary orbit within sublight broadcasting distance of Terra’s second-largest trade lane, a signal began to move across the system. Within hours, hundreds of ships were carrying an unnoticed software slot-in; within a week, this package had unknowingly spread to a dozen star systems.

And then, DeathGrrrr struck, with a virus designed to infiltrate the shared code found in most sensor systems and timed to strike simultaneously around the galaxy. DeathGrrrr’s trick didn’t disable spacecraft (something which would have been extremely difficult given inherent safety backups unrelated to sensor suites), but it did lock every infected sensor suite to grayscale mode. Traffic ground to a halt until a fix could be reached; billions of UEC in shipping were lost.

DeathGrrrr was never captured or even identified, and it remains unknown whether the attack was intended as a prank or something more sinister; an analysis of the software and the drone turned up nothing. But the method of infection was clear: a small worm script delivered directly to common-core code. And unquestionably, the winner in the situation was WillsOp.

With their unique code, WillsOp’s sensors were unaffected by the attack. Overnight, the company became a household name and sales skyrocketed. Some newscasters went so far as to suggest that the company might even be behind the attack. Whatever the truth, by the end of the fiscal year, WillsOp had captured a 35% market share in the private spacecraft sensor market (up from under 1%.) With the additional revenue, the company diversified, building robust physical radars and scanners in addition to continued development of their proprietary software.

Now a market leader in all aspects of sensor technology, WillsOp is routinely pursued by top level spacecraft designs, and certain top-of-the-line designs ship with their technology as a default install. The military, too, has come courting; WillsOp packages are standard in several advanced UEE starcraft.

Targeting

Today, WillsOp’s prime seller is the P3 Autocompensator, an aftermarket software installation capable of being configured for almost any current-year civilian spacecraft. In essence, anything from a Drake Herald to a MISC Hull D can be equipped with P3 software. The P3 is one of the best target tracking systems on the market, capable of direct tracking of up to three spacecraft and (with an attached WillsOp device, required) passive tracking of up to 512 ships in a standard interaction sphere. Videogame designer Original Systems has licensed the P3 interface design for their Arena Commander game. It currently comes standard with all trainer ships.

Origin Jumpworks GmbH has also signed an agreement with WillsOp, making them the exclusive supplier of custom-designed targeting systems for the Origin 325a spacecraft variant. The WillsOp-designed system will premiere with the 2944 model of the 325a, and is hotly anticipated by spacecraft enthusiasts.

Star Citizen Art Design sheet: F7C Hornet's Long Look Radar

Tracking

In addition to direct targeting systems, WillsOp is responsible for passive tracking systems that have become an industry-defining standard. Where a targeting suite typically focuses on extracting as much information as possible about one target, tracking systems are necessary for keeping tabs on everything else in a given area. WillsOp’s trackers are capable of making dozens of identifiers (limited only by range) available for instant targeting.

While any WillsOp targeting suite requires proprietary WillsOp tracking software to function, the tracker is actually manufacturer-neutral. WillsOp trackers are produced in OEM models and are made available at cost to spacecraft manufacturers. The company’s objective is simple: introduce users to their ecosystem, then trap them when they opt to choose an aftermarket targeting system.

Deep-Space Radar

It was a moment of redemptive glory for WillsOp when, after nearly four decades, they finally secured a valuable long-term UEE military contract. WillsOp has partnered with Anvil Aerospace and the UEE Navy to manufacture both the structure and the software for the LongLook Radar system installed in every F7A-R Hornet Tracker. The dome-like enclosure installs in the Hornet’s upper turret slot, replacing the moveable guns with an incredibly powerful radar.

The LongLook offers the fullest battlefield view possible in a single-seat fighter, with the processing power to track fleet movements and coordinate squadron-level engagements. A civilian model of the LongLook is also available and can be installed in any Hornet model in place of the standard cargo container (with some impact on stats).

The company’s future continues to look bright, although safety mechanisms put in place since the DeathGrrrr attack have allowed other software systems to once again flourish. Observers frequently cite WillsOp’s lack of specialty or boutique sensor options (such as metal-penetrative mining scanners) as a source of lost revenue. For their part, WillsOp seems content to be responsible for standard sensor equipment and to leave anything more specific to the also-rans.

Heya! We only use cookie to make the site function and save your preferences, nothing else :)