STF

Side Sim - Conference Room - CRIT... And So It Begins (Tag CO, XO, CIO)

Posted July 6, 2020, 1:45 p.m. by Lieutenant Commander Gravel Mardusk (Chief of Security) (James Sinclair)

Posted by Lieutenant Commander Gravel Mardusk (Chief of Security) in Side Sim - Conference Room - CRIT… And So It Begins (Tag CO, XO, CIO)

Posted by Commander D’Vash Odinson (Chief Intelligence Officer) in Side Sim - Conference Room - CRIT… And So It Begins (Tag CO, XO, CIO)

Posted by Lieutenant Commander Gravel Mardusk (Chief of Security) in Side Sim - Conference Room - CRIT… And So It Begins (Tag CO, XO, CIO)
Posted by… suppressed (8) by the Post Ghost! 👻
Mardusk looked around and made sure everything was squared away and the Skipper had three pots of coffee. The meeting requests had gone out yesterday, and the giant Orion had spent the next day sweating bullets. He knew the Captain was supportive of his and Cochrane’s CRIT team initiative. And the Brass had applauded him and Alex on the idea and gave them their blessings. But now… now is where the rubber met the road.

And Gravel was nervous.

He had gone over the potential candidates time and time again. And he knew the new CIO had the background and experience he was looking for. The question was: would he want to take the job? It was going to be hard enough coming onto a new ship, not just to him but to everyone, and settle in. Now along comes Mardusk to drop a new team with massive responsibilities and leeway to operate in his lap. A team that he would be responsible for, but who he also had to trust enough to hand the reins over to if someone was better geared to handle the specific situation. And it was the leeway that worried him. Cochrane was a ship’s Captain. It was his idea to have the team only answer to the CO. He said it would ‘cut down on the bull@$#t’ if they didnt have DH’s and off-ship authorities tugging at the team all the time. And he was right… but that meant a CO had to be willing to take it on the chin if the team screwed up. And so did the team leader. It was a lot to ask of Kelly and the new CIO.

“Double edge sword much?” he said out loud to no one in particular.

Mardusk, CoS

The door swooshed open and the ships new Intel chief stepped in. “Double-edged sword, Cmdr.? It depends on what type of battle you’re going into. The single-bladed Oriental weapons are useful for quick, precise strikes, but personally, I like the big, two-handed swords and battle axes my ancestors used to invade Europe. Those were just big and scary.”

He stepped forward and introduced himself. Cmdr. D’vash Odinson, CIO.” He was nowhere near as big as the Orion security chief, but he was built solidly. D’vash’s appearance more closely resembled his human mother, but if Mardusk paid any attention, he would notice a slight green tint to Odinson’s skin color, showing that there was some Orion blood in the new crew member.

Odinson (CIO)

Mardusk chuckled and said “Talking to myself actually, sir.” and he held out a truly massive hand to D’vash and said “Lieutenant Commader Gravel Mardusk, Security Chief and Co-Architect of either a really good or really really bad idea. Either way, thanks for coming. I hope the presentation doesn’t disappoint.”

Mardusk, CoS

Jen followed behind shortly after, entering as punctual as one was able without being a Vulcan. The meeting agenda that the Security Chief had called was cryptic and brief. CRIT. He had only recently met the security chief as the co conspirator of the anomalous bar that still had his antennae quivering. All they needed was a Horta in this meeting to make it a truly eclectic and alien meeting. He glanced at the rank insignia and half smiled. “If we have too many more of us in this room there will need to be a name for it. A ‘flight of commanders’ perhaps?” He looked at the newcomer whom he recognized as one named Odinson. “Commander, welcome aboard,” he said to the newest member. It wasn’t hard to remember his name after the rank. It wasn’t every day that a new full commander was aboard.

One corner of D’vash’s mouth pulled up into a grin. He stood up and nodded to the XO. “Thank you, Commander. I’m happy to be here, and exited to get back into the field.”

He looked to Mardusk. “Any spoilers before the Captain arrives?” he inquired.
- Jen, XO

Mardusk smiled slightly and said “Now where the fun be in spoliers?” and he chuckled as he gestured for the XO to be seated. “This is a proposal myself and the CO of the USS Manhattan put together a few months back. We were discussing the need for specialized responses across all departments, and how to make that efficient and easily mobilized. What I’ll be presenting today is the plan that we developed and that the Skipper and the Fleet Brass have approved for trial runs here and on the Manhattan.” The big Orion was obviously a bit nervous… but just that fact would show those that knew him how serious he took the project.

Mardusk, CoS

Odinson had dealt with his share of Orions in his early Intel days, usually at the other end of a phaser. He could tell by Mardusk’s demeanor and the way he carried himself that he was a loyal Starfleet officer. No need to worry about him. He still carried suspicions about most Orions he dealt with, but most of them weren’t in the fleet.

Odinson (CIO)

Jen contemplated the idea. He was open to new things, though had reservations. There was, technically, little that was new under the sun, and the effectiveness of many a plan could be researched. However, every tactic was circumstantial. He moved around to pull out a seat and gestured to Odinson. “Have a seat,” he offered. “No sense standing on ceremony. You were last on the Olympic. Same class ship. What do you see as the principle strength and weakness of that design?” Jen glanced at Mardusk. His expression presented the option to him as well, though with the Orion making the presentation his take was that he preferred to stand. He might be an IO now but his prior position was as his now.
- Jen

D’vash thought for a moment before replying. “The interchangeable mission modules were a definite bonus. That gives the class the ability to take on just about any kind of mission. A lot of flexibility for whatever the need may be. In my honest opinion, the only weakness she has is that there are civilians on board. In times of crisis, you can’t worry about if your family, spouse, and children are safe.”

The door opened and Kelly breezed in rapidly. Running the floating palace she had been given was like being the mayor of a small town. There were always a few civilians here and there on a ship however they typically always belonged to someone. Now the Atlantis was a ship of Starfleet crew and private contractors. The crew were fine.
The private contractors were the handful. They were bound by some of the rules of Starfleet but not all. Privately she called come of these contractors the Starfleet Ship Association because they complained about every minor inconvenience they saw both real or imagined. Inhaling deeply, Kelly smelled the scent of coffee in the air. “God Mardusk tell me that is the stash your mom left when she visited,” Kelly moved to the pot pouring a large mug.

Savoring a sip she moved to the table and sat down. “So what have I missed,” she looked at the XO, COS, and newest CIO.

Captain Kelly Bordeaux

Mardusk nodded and said “Side chatter,Skipper. Waiting for you for the nuts and bolts.” Mardusk then slid PaDDs to everyone and said “Skipper is aware, so they’ll be review for her. Fleet has approved implementation of a new response group. You can read the order and overview here.”

On the device was a document marked confidential and entitled ‘CRIT Directive- Activation and Implementation’. It read:

“Based on discussion between two senior Security personnel, a need for a ship-specific rapid response entity was identified and addressed with the creation and subsequent approval for the formation of CRIT (Containment - Response - Intervention - Tactics) teams on the USS Atlantis and the USS Manhattan.
These teams are to be made up of individuals from all departments who possess uncommon skill sets and are capable of operating under extreme stress and pressure. The qualifications for the CRIT designation are as follows:
• Complete psychological and medical assessment and approval of CMO and CMS for duty on the team.
• Recommendation of Department Head and two subordinates. (In the case of a Department Head application, recommendation will come from CO and XO).
• Skills test conducted by CRIT team members.
• Monthly Physical and Psychological assessments.
• Passing of Final CRIT Simulation test.
Upon completion, CRIT certification will be assigned.”

“It must be noted that all CRIT teams are ship / station specific. CRIT designation is non-transferrable from posting to posting. Any previous CRIT member who transfers to another duty station will have to reapply for the designation.”

“CRIT teams will deal with any situation deemed necessary for their deployment by the Commanding Officer. The Commanding Officer can deploy CRIT at the request of others, but the final decision rest with that entity. In the event the Commanding Officer is incapacitated, CRIT will automatically activate to asses and respond as needed. Specific examples of CRIT activation are:
• Boarding Operations
• Away Team operational support in unknown or hostile areas
• Hostage situations
• Repelling of Boarders (Operational support to ship’s Security)
These are examples of CRIT team use. By the nature of the team, their use will be varied and unique from activation to activation.”

“The hierarchy of the team is unique. There is a designated team leader, but their position is one of ensuring the team is current and prepared. All CRIT members have an equal voice in team decisions, but ALL members are expected, even mandated, to defer to the subject expert on their team for any given situation. To explain: A freighter has been boarded by pirates and the warp core has begun to go critical. The team leader designates risk priorities. Here, the warp core is the priority. The team’s Engineer takes the lead, directs the team to contain the breach. When that is done, the Security expert would take the lead to deal with the pirates. This is why the team must be a truly cohesive unit. Trust and mutual respect for each member is key.”

“CRIT teams will have access to all supplies and equipment they deem necessary to carry out operations in the manner they see best. This level of logistical support is uncommon, and Commanding Officers and Team Leaders should be diligent in ensuring such support is not abused.”

“Oversight and responsibility for the actions taken by the team fall to the designated Team Leader and the Commanding Officer of the ship or station. Disciplinary actions against CRIT team members are encouraged to be done out of public eye on order to maintain the desired reputation of professionalism, integrity, and elite capabilities. Only if deemed necessary by the team as a whole and / or the Commanding Officer will charges against a member for actions taken during CRIT operations be made public. It should be noted that this is not done to protect members of CRIT, but to protect the public view of the operational entity.”

“CRIT will be activated for period of one year Standard Time from this date. After such time, a review by the approving Admiralty will be conducted to make a final decision on the efficacy and desirability to maintain the program.”

Mardusk watched as the assembled group read, and waited for questions.

Mardusk, CoS

“Interesting concept, Mr. Mardusk,” D’vash began. “A team of specialists to be first responders to any given situation. Definitely a viable option with a crew this size. Approximately, what size of a team are we looking at?”

Odinson (CIO)

Mardusk smiled and then shrugged. “That’s what I believe is the core strength of this concept. No formal team sizes, no mandated equipment lists. Each team is it’s own entity, designed to meet the specific needs of the post by those who are actually doing the job. They decide how many they need, what equipment, what training. They are responsible for being able to deploy in a myriad of different scenarios and be effective. How they do that is up to them. Oversight and responsibility coupled with flexibility and ease of responsiveness. That’s the goal.”

Mardusk, CoS

OOC: Fixing typos.


Posts on USS Atlantis

In topic

Posted since


© 1991-2024 STF. Terms of Service

Version 1.15.9