David looked flabbergasted by this explanation. “How do you know all this?”
“You know, books and stuff,” Christine said, with a sarcastic smile.
“This is pretty much what I concluded when I was with my parents,” Mike added. “We never explored how far the system could go on its own.” He paused and looking meaningful at David. “So, what do we do?”
“I think you and I have to go right to Gary Mitchell, and tell him the truth. Even if that means I lose my job as the result of this. We have to get Gary to approve an immediate outage with hard power down. Then we can pull ELOPe off the system, even if that means we rebuild those servers from the ground up. Forget home. Mike, please go straight to the site.”
“On my way,” Mike replied, as he sped down Alberta Avenue, bypassing the turnoff for David’s block, and heading for the highway to downtown.
“Gary Mitchell is still gone. His admin says he was supposed to take a vacation over the holiday break, but he should have been back by now. Tahiti, in case you were wondering.” David had just returned from the building across the street where Gary’s office was located, while Mike and Christine waited in David’s office.
“I’m picturing him laying on a beach, a cigar in one hand, and a whiskey in the other.” Mike shook his head.
“I know,” David said, laughing, “I don’t think his admin meant to tell me where he was, but I was a bit demanding.”
“No word from him?”
“Nothing. He should have been back in town a couple of days ago. His admin has paperwork waiting for him to sign. She’s sent him emails and left voicemails, but nothing.”
Mike grunted.
“While you were over there, I spoke to Richard, who was the only member of our development team that worked through the holiday break,” Mike explained. “Remember that email you told me about just after we received the additional servers? You mentioned that we were assigned a team of top notch performance optimization experts to help us work on performance improvements to drive down resource utilization?”
David nodded. “Yeah?”
“According to Richard, that team showed up on the Monday after Christmas,” Mike said. “They were a bunch of subcontractors he had never met before. They had two guys onsite for the entire Christmas break, and another dozen offsite. He says he had an email from you telling him to grant them access, so he did.”
“Let me see what changes they made.” David turned to his computer, attempting to pull down the latest source code. He stared in frustration as an error dialog popped up, with an ‘access denied’ message. He tried again, and then pounded the keyboard in frustration.
“I’m in the same boat you’re in,” he finally said to Mike. “My access to the source code has been removed. I can’t pull down a copy of the latest code to see what they changed. Do you have any ideas?”
“Well, Richard kept an eye on them the first few days, and then he left for a skiing trip over New Year. If you look in your email inbox, the contractors emailed us both a written report of what they did. It was sent Friday morning, so they finished up just before either of us got back to town. According to the email, they made some major improvements in performance, mostly related to the Bayesian network. Melanie was here at work yesterday, pulled down the latest code and ran the performance tests against it. The new code seems to have taken the import of new emails from x squared to x log x, and quartered the evaluation time.”
“Woah, are you guys saying you originally had an exponential resource utilization curve?” Christine thought about her own work on massively multiplayer games. She knew that, in the ideal case, when you add users to an internet application of any kind, you want the application to scale linearly. She shook her head and turned to look at David and Mike. “How the hell did you ever expect this to scale?”
“Scaling the resources has been the major bottleneck all along. It’s why we ran into so many resource constraints, and why the project was in danger. It didn’t appear that there was any way to scale without requiring a massive number of servers.” David shrugged. “I just kept hoping that as long as we kept the project alive, we’d find some way to overcome that limitation. Now it seems that someone has.”
David turned back to his computer. He was still trying to coerce his computer into giving him access to the code. “Damn, how did our project access get revoked? I don’t understand how email could interface with the access rights.” He turned back to Mike. “Do we have any idea what else these contractors did?”
“I might.”
Everyone turned around to look at the door. There stood an older unshaven man, dressed in rumpled clothes, carrying bundles of paper under his arms.
“Gene Keyes, Controls and Compliance.” He spoke in a deep rumble. “I’m here to save your ass.”
Over the course of the next hour, Gene briefed the others on what he had found during his investigation. Like them, he had tried to reach Gary Mitchell, with no success. He had uncovered that while there were unusual charges across the company, the only consistent patterns of unusual behavior were found in three departments. As Gene spoke, he laid printed reports across David’s desk.
The first, of course, was the R&D department in which David’s ELOPe project was housed. According to Gene’s print outs, it had paid for several small allotments of servers and subcontractors to make modifications to ELOPe. The nature of the modifications was not specified, but the budget amounts were sufficient for dozens of engineer-months of work from an outside vendor.
In fact, it was the expenditures in David’s department that had led Gene to them. David’s legitimate order several months earlier of a pool of high performance servers had clued Gene in that all of the later purchases might be somehow tied to the project that first needed additional servers.
“So does this mean we’re under suspicion?” Mike asked meekly.
“No, I can see the problem is bigger than you boys. In fact, I can see the problem is bigger than just people,” Gene said, the cryptic answer more puzzling.
“But where did the money come from?” David asked. “I exhausted our budget weeks ago.”
“Transferred in from other departments,” Gene answered. “Namely, Gary Mitchell’s Ops group.”
Gene went on to explain that the second department that contained the unusual pattern of purchases was Gary Mitchell’s department, which was responsible for operations for the company’s communication products, including AvoMail, Avogadro Voice, and Avogadro Chat. By virtue of the size of its business, Mitchell’s department had a vast operational budget compared to the relatively small R&D budget for the ELOPe project. Gene’s printed records showed that Gary’s department purchased tremendous quantities of servers, had servers reallocated from other projects, paid for a variety of subcontractors to do programming work, and finally transferred substantial funds to both the ELOPe project and the Offshore Data Center department.
“Offshore Data Center department? What do they do?” asked Christine.
“They took the data center in a box concept, which is a standard shipping container filled with racks of computers, and put it on a seaworthy barge,” David answered. “Then they connect the data-center-boxes to wave-action electrical generators. The whole thing is connected back to the data grid with fiber optic cables. Avogadro calls them ODCs for short.”