Week four in Fast Track started with the worst spring storm in twenty years. The tail end of hurricane Sheva, an anomalous El Nino child tempest, tore across the Atlantic in five days and smashed itself first against Ireland and then, barely diminished, romped across South West England into London. For once the faintly hysterical British approach to any weather outside of bucolic norms was justified. Heathrow was closed completely when an aging, fully fuelled, Boeing triple seven was pancaked by wind shear against a primary noise baffle outside Terminal 6. Flash floods, now an established (and manageable) part of the start of British summertime, even threatened to overwhelm the drainage capacity of the new subterranean London orbital. Even in the rigid, over engineered confines of the Gaunt, the sounds of 200 km/h+ winds penetrated the carbon walls of my tiny apartment, and groggily woke me from my chemically mandated 5.5 hours.
There’s only five left of us in the final week of management training. Attrition has been brutal and swift; from the first culling at lobby level, to stress related death and even a tissue rejection of one of the on-board Jobs (that was gross). It’s an insidious process though; conditions that would repel the most rampant go-getter are ignorable in light of torturously incremental progress up the pyramid. As the weeks go by the spectre of poverty becomes more and more ephemeral and the dependency equation becomes increasingly distant. Privation becomes someone else’s problem: survival becomes an abstract performance related process, not a nutritional and energetic priority. This is just as marginal, but dressed up in the polysyllables of management jargon, the Darwinistic imperative of corporate survival starts to feel like wholly natural process in a completely artificial world.
Week four focuses on one of main managerial tools in the WorkSpace arsenal for Operator control. As the primary worker antforce, the Operators are the most vulnerable and yet potentially most volatile section of the sprawling polycorp that is WorkSpace. Subject to draconian control methodologies that skim the surface of abuse, the Operators are a beleaguered corpus of stringently mandated drones, lock stepping borg-like towards an ever extending horizon of profit. Corralled and hobbled by chemcontrol, Confluence management, haemoglobin starvation and good old paranoia, the Operators are a tough proving ground for fresh, new Fast Track graduates. So, in our final week of training we are introduced to Formalising Externality (FE), more commonly (and off channel) called Skinned in the Game.
FE can be applied in any number of contexts but is most commonly utilised to offset primary corporation costs, these can (and do) include: energy needs, raw feed supply, governmental kickbacks (an industry of its own) and probably most critically, data grid access. WorkSpace’s lifeblood is based on connectivity; without the bandwidth hungry data systems that infiltrate and entwine every aspect of corporation life there would be, in a very real sense, no corporation. Despite a nationwide initiative throughout the 2010’s to re-wire the UK data infrastructure with high capacity hard lines, the past fifteen years has seen an ever increasing reliance on distributed, wireless, nodal data infrastructures that co-opt essential workplace hardware to generate a fluidic, malleable data grid that can be put to use for a myriad of processing requirements. Theoretically open ended in capacity, and Euro-wide, the grid does have finite resources; its performance is still predicated on a sometimes erratic energy supply and non-sanctioned piggyback hacks; and the occasional non-cooperative EU member country can disrupt overall capacity of the grid system. Early in the twenties a pan-Euro regularity body was set up to manage access to (and process revenue from) what has more recently become known as just The Grid. This body is called MeshGate, a universally reviled Swiss-based bunch of bureaucrats loathed the continent over.
WorkSpace therefore is, in part, forced to use, and pay for, a wide area data network system that it has no direct control over (a condition that periodically causes almost schizophrenic spasms of corporate anxiety within management prime; WorkSpace is not used to outside mandate on anything it does). Grid usage is based on a standardised packet transfer volume algorithm and is strictly monitored; excess Grid usage during a given job does not result in access termination but it does result in hefty financial penalties for the accessing organisation.
This is where FE comes into play; when a particularly data-heavy job is required by WorkSpace (climate modelling for example, or tactical nuke impact assumptions), management prime will deliberately under-fund the Grid data allowance for the job. Instead of ensuring adequate network capacity for the job they will impose a best-practise guideline on the Operators. This directive will demand hopelessly over-ambitious efficiency targets for the job in hand, and place the onus on maintaining prescribed bandwidth usage quotients squarely on the Operators. Together with these best-practise imperatives, there will be a per-Operator penalty clause for excessive Grid usage (it is fictitiously assumed that WorkSpace will have provided its valuable employees with sufficient processing finesse to achieve these absurd targets). The result is that the job will almost always exceed the management set maximum data allowance, and the Operator penalties come into play. These forfeitures are invariably financial in nature, or at best a reduction in employee benefits that have a positive effect on WorkSpace bottomline. In this predictably nefarious manner, WorkSpace get the job done, just under budget for the client, and they get to over-subscribe the allotted Grid data allowance, and offset the penalties that this implies. And who pays? Operators pay.
The FE session ends and the water-cooler dissection rapidly embarrasses me—I’m the only one there expressing any (carefully phrased) outrage. It seems, that in these cynical times, FE is not even considered particularly evil, merely another working condition that is to be wearily hefted onto the shoulder by an ever-refreshed morass of Operators workers. If anything, my objections are an indication of a naivety that is woefully out of place here, but I’ve been there—countless hours ensconced in a claustrophobic exo-suit, catheterized and catamited, chipping endlessly away at abstract data chunks for thousands of seconds at a time. Next time you droolingly unbox your latest consumer ephemera, spare a thought for the unnamed soldier who helped design your fleeting hollow pleasure.
Roll on Friday…