Remove Tag?

Do you want to untag yourself from this post?

USS Sentinel

Engineering - Still Docked

Posted by EvilJen (DDoSFEO) in Engineering - Still Docked

Posted by Ensign Hugh MacClure (Engineering) in Engineering - Still Docked

Posted by Master Chief Petty Officer Karl Johansson (Chief Engineer) in Engineering - Still Docked
Posted by… suppressed (34) by the Post Ghost! 👻
There were two men in red uniforms running an inspection. The Engineering crew just assumed that they were from the starbase doing a routine inspection but, a closer look would show that their uniforms didn’t have any rank insignia and the delta wasn’t quite right.

They opened up the main computer and was testing when suddenly alarms started going off. They jerked back and started pushing buttons on a panel.

“UNAUTHORIZED SHUTDOWN OF THE MAIN COMPUTER ATTEMPTED, EMERGENCY CORE SHUTDOWN PROTOCOL IN PROGRESS”

The two men stepped back and looked at each other. One of them pulled out a communicator and flipped it open. They both transported out before anyone could stop them.

GM

Randy quickly jolted himself from the injector realignment he was doing and dashed off to the source of the alarms. “What the hell…” He muttered as he attempted every trick he knew to get these state of the art computers to follow commands but whatever tampering had been performed he wasn’t able to interrupt the sequence. Pulling out his communicator he let the trademark chirping end before he said somewhat frantically, “Randy tae anyone important. We’ve got a problem wi’ the computer, she’s shuttin’ doon an’ Ah cannae stop it. Ah dinnae know how long it’ll take tae come back online once the damn thing will respond tae ma controls.”

~Randal Farquharson, Engineering~

The captain’s voice came back from over the comms. [O] Do the best you can Lt. Then get it back on line as soon as possible.[C]

Hugh was on his way to Engineering when he heard the alarms start to go off. As he moved into Engineering he saw a Lieutenant working on the issue. “Sir,” Hugh asked without making the Lieutenant waver, “Wa’ seems ta be the issue.” and began looking at the controls to try and see what was causing the issues.

MacClure, Engineering

The computer log showed that someone had tried to destabilize the warp field and the dilithium intermix values. However, the upgraded security functions had prevented the intruder from actually making the changes needed. However, the algorithm used was a starfleet standard, showing that whomever had attempted the access, was Starfleet.

-GM

Hugh looked at Randal and stated, “We need the Chief Engineer down here. This issue is bigger then us.” Hugh went back to working the panel to see what else was happening.

MacClure, Engineering

Cpt. Asam, CO

The team seemed to have everything under control, but the fact that this happened and it was done using a Starfleet code was unsettling. He needed to let the higher ups know what happened, tapped his badge and said, =^=MacClure to bridge, we need the Security Chief and possibly the XO down here in Engineering.=^= Hugh didn’t want to broadcast the issue over the communication system. If someone did this they maybe tapped in somewhere.

MacClure, Engineer

[O]Someone will be there momentarily. Asam out.[C]

Cpt. Asam, CO

That someone turned out to be the first officer, Commander Alden, as he briskly headed into the engineering department. “What’s the problem, Ensign?” He asked politely in his crisp, “proper” English accent.

~ Cmdr Alden, XO/CSO

Hugh spun to the Commander’s words and replied, “Sir, the engines are under control, but it appears the issues stemmed from an unknown algorithm that used Starfleet standard code.” After a moment, Hugh continued, “Only someone within Starfleet could have done this.”

Hugh waited for further instructions from the XO.

MacClure, Engineer

“Show me the access code used. Starfleet personnel data is associated with each code, especially with any sort of clearance.” Roman said.

When given the code, he inputted it on a nearby console to see whose code it was.

~ Cmdr Alden, XO/CSO

With the computer down, Alden would have to go to the Starbase for answers to his inquiry.

The sound of heavy, rapid footfalls preceded the arrival of Karl Joahnsson, the Chief Engineer, he’d been on the other side of the ship, overseeing some maintenance work, when the call came; he’d run the length of the ship and commandeered a turbolift, tossing out a very confused young ensign. He briefly glanced at the First officer but ignored him and ran to the Warp Core information panel “Status report” He said to no one in particular. He was a little winded from the running, but he was quickly focusing his breath

Master Chief Karl - CE

Hugh looked at the Chief Engineer and said, “Chief, good to see you.”

MacClure, Engineer

Karl didn’t look up “Yes MacClure I am quite the sight” There was a slight edge to his otherwise cheerful tone “Now kindly report on the status of whatever’s going on”

Master Chief Karl - CE

Hugh turned back to the console and said, “If you look here, you will see that the algorithm used to cause the issues to our systems was Starfleet. Hugh then tapped a few more buttons to ensure everything was functional within normal operating parameters.

MacClure, Engineer

Karl looked at the data MacClure showed him “Well I’ll be” He muttered as he quickly read through the code “Alright MacClure, I’m sending you a new Security Protocol, quickly review the code before applying it, I’m tying in my personal clearance as a stopgap measure for the moment” He stepped back and joined the first officer to see how he was doing reviewing the algorithm used. “Sir”

Master Chief Karl - CE

“Aye Chief.” Hugh replied and quickly scanned through the new protocol and started implementing it into the system.

MacClure, Engineer

The problem was, the computer was down. Everything was. Basic backup systems were on to run life support, so MacClure was able to put in the new security algorigthm and lock the systems from further tampering. Identifying the identify of the code user would require the ship’s computer be restarted. Or someone prying open the doors to the star base and going over there to use their computer.

EvilJen, DDoSFEO

Hugh looked at the panel and said, “Getting the computer core back up.” and started his diagnosis of the problem.

MacClure, Engineer

Karl frowned at the console and looked back at his small cubby office with fantasies of going in to get his lucky wrench so he could get some therapeutic violence towards the computer core itself “Alright I want to double and triple check the code they implanted before we restart the computer core, I don’t want something nasty messing up my engine when we restart it” He smiled again “Let’s go, prep for a full reboot” HE flipped a wall switch [O]Master Chief to Bridge, ship’s broken, gonna turn it off and on again, comms likely not secure[O] He didn’t elaborate further regarding the security breach.

Master Chief Karl - CE

The captain’s voice came back over the comm, [O]Acknowledged chief. Do what you have to. Asam out.[C]

Cpt. Asam, CO

Karl nodded “Ok kids, let’s shut this thing down” He called out and began the standard procedure for reebooting the main computer.

Master Chief Karl - CE

EvilJen, DDoSFEO

Karl and the engineering team went through the shut down procedures and began the reboot process.

Master Chief Karl - CE

Able started tapping his console as the reboot started and hoped everything would be ok.

MacClure, Engineer

Rebooting an entire ship was not a simple nor a fast procedure. Shutting down went smoothly, and then once the power was restored, every system had to have diagnostics run to make sure everything was in working order.

EvilJen, DDoSFEO

Bump

“Alright, let’s get the reeboot process going. I want teams of two going over every function, rotate before sending your work through, I want everything double-checked before anything gets a green light. Then when you get a green light I want you to check another diagnostic. I don’t want any mishaps.”

Master Chief Karl - CE

Johansson’s teams worked hard and soon the ship’s systems were running smoothly and correctly. Though it took time. Fortunately Johansson’s crew noticed the breach and sabotage early enough to prevent permanent damage.

EvilJen, DDoSFEO

Karl leaned against his console when things started coming back online “Ok team good work, let’s run a couple more diagnostics and make sure we didn’t miss anything”

Master Chief Karl - CE

The final diagnostic came back with some damaged relays and the seal around the dilithium chamber was weak.

EvilJen, DDoSFEO

Karl waved his hand “Teams 1 with me to repair the DC seal, teams 2 through 4 get on those relays, rest of you make sure we’re ready for warp factor by the time the Captain needs it” He grabbed his toolkit and got to work, first preparing a temporary seal for the chamber so they could repair or replace the first “NE Bradley, open a com to the bridge for me”

NE Bradley nodded and grabbed a communicator and held it up in front of Karl as he worked [O]Master Chief to bridge, reboot was succesful, we’re doing some final repairs but you should have Warp capabilities within the hour[O] HE wasn’t actually sure on the time but an eyeball of the current damage gave him a rough estimate.

Master Chief Karl - CE

[O]Thank you Master Chief. Good work and pass on my thanks to you and your team. Bridge out.[C]

The relays seemed to have blown from the cascade, but the seal…that had obviously been tampered with. It looked like someone took a plasma torch to it and a chisel to crack several places in the seal. It would need a complete replacement or a complete rebuild.

EvilJen, DDoSFEO

Karl frowned, it’d take time they likely did not have to get a replacement and he didn’t have time for a rebuild, he looked around then pulled two enlisted engineers, a pair of Petty Officers 3rd class “Gentlemen, I need you two to sashay over to the base. The mission: Strategic Transfer of Equipment to Alternate Locations. Equipment is a replacement seal, Alternate Location is my Engine room, go”

Master Chief Karl - CE

The two Petty Officers looked at each other and then back at Karl. “Aye, Sir.” They hurried off with huge grins on their faces. Time for some capering!

Hugh watched as the Chief gave orders to the engineering teams and started tapping at his console again to see what the next order of business would be.

MacClure, Engineer

There were relays down in junctions 34b, 29a, then deck 2 junction 8 and deck 6 junction y.

It was rouhgly thirty minutes later the two Petty Officers scurried back to Karl, their faces flush with the rush and trying not to show they were panting. “Strategic transfer complete, Master Chief.” They handed him the seal.

EvilJen, DDoSFEO

Karl laughed “Excellent, now you two head to D6JY and get this set up, Team two you take D2J8, McClure you take Junction 34b and I’ll take 29a” He quickly handed out the work product his team of E4’s had very legally procured in a way that was not stealing at all in any shape or form.

Master Chief Karl - CE

Use the full posts index to browse this ship's thread list.

Open Full Posts Index