OOC: This thread is for internal messages and announcements for the crew of the USS Shackleton.
1 Like
![]() |
Stardate 95627.7
Security Level 1 - Open ![]() TO CAPT Derenzis, Alyx; LT Voyrays CC CMDR Akaela, Tala; LT Mercer, Olivia FROM LTJG Khet, Mossic SUBJ Prototype "Icarus" Probe Development Summary |
Captain, the development team working on the probe project you requested has completed its design and prototyping phase. The modified probe, nicknamed "Icarus"* by Lt. Vandenberg, is complete and undergoing some limited testing in the remaining hours before our arrival. The team will construct two more identical units as backups in the event of equipment failure during the experiment.
(* Lt. Vandenberg assured me that the allusion being made with this name choice, referencing a mythological human youth prone to disregarding safety instructions, would be well understood by you.)
The prototype probe has been significantly modified from its factory configuration, sacrificing most of its drive and sensor internals for the transporter system, shielding and a greatly expanded power plant. The onboard M/ARA, assembled from runabout fittings, should supply enough power to simultaneously maintain a directed heat barrier and conduct a short-range transport for the sample. The sample pattern will be held in the transporter buffer for the duration of the probe's transit, then transferred to the Shackleton when the latter intercepts the former at the other side of its parabolic flight path.
Due to the technical and temporal requirements of this project, some design concessions were made which you should bear in mind:
- First, the prototype's modifications have caused it to outgrow the profile restrictions of a standard class IV probe, meaning it will not be possible to launch the probe from any of the Shackleton's torpedo tubes. The team has instead assembled a mass driver array in the aux. shuttlebay to launch the probe instead.
- Due to the high power draw anticipated during the probe's close proximity to the sun, steps were taken to make sure the shield emitter array was configured as efficiently as possible. The emitters are arranged to focus all available power into a limited area of coverage between the probe and the coronal surface. However, because so much of the probe's sensor suite had to be removed to achieve other design priorities, it was determined that the probe cannot be trusted to adjust this shield facing in realtime; it must instead use its maneuvering thrusters to keep the stationary shield facing aligned with the star throughout its near transit window.
- In addition to the sacrifices made in the probe's sensor package, most of the drive system had to be removed as well. The microfusion generators and impulse systems had to go; only the maneuvering thrusters remain, to facilitate the orientation adjustments detailed above. This means that the probe will not be able to move under its own power to any significant degree. The flight path must be carefully computed and executed upon launch, after which only minor course adjustments will be possible.
- Finally, it must be understood that without adequate sensory instruments or propulsion, the probe will be dependent almost entirely upon guidance from a remote operator aboard the Shackleton to make course and orientation adjustments during transit.
In summary, the prototype must be fired aftward with great precision from the specialized mass driver installed in the aux. shuttlebay; it must travel along its parabolic flight path with minimal course adjustment; it must be remotely guided to keep its concentrated shield facing the star; and it must be intercepted at the other end of its path before its limited fuel supply is exhausted and the pattern stored in its buffer degrades irreparably.
But the good news is we'll have three shots at it.
//SIGNED//
Lt. J.G. Mossic Khet
Engineering, U.S.S. Shackleton
4 Likes
![]() |
Stardate 95628.1
Security Level 1 - Open TO LTJG M. Khet; LT O. Mercer CC CMDR T. Akaela; LCDR L. Kealohanui; LT Voyrays FROM CAPT A. Derenzis SUBJ Re: Prototype "Icarus" Probe Development Summary |
Lieutenant Khet,
Well done. We were hoping for one probe, and your team has delivered three. Although this would explain the yelling I got from the main shuttlebay about "sudden appropriation of runabout reserve parts...". Lorena, if you can calm CPO Flagg on that matter it'd be appreciated.
This gives us some much-needed leeway to see this experiment through to success, though I'd like to see if we can get it right on the first try. The mythical Icarus didn't listen to his father and paid the price. We'll do our best to keep within the design limitations of your probes, and hopefully fare better. Lorena, Lt. Mercer, that would be your department. Please review Lt. Khet's conditions and adapt accordingly.
We'll be arriving at LHS 1670 at Stardate 95629.8. Both I and Dr. Morrissey aboard the SS Sarah Tuttle would like to start no later than 95630.0. I trust all involved will be ready when the moment comes.
In the meantime, Lt. Khet, you and your team have my permission to sleep in - you've definitely earned the rest!
//SIGNED//
CAPT Alyx J. Derenzis
Commanding Officer / U.S.S. Shackleton
3 Likes
![]() |
Stardate 95657.3
Security Level 1 - Open TO LT Olivia Mercer CC CMDR Tala Akaela; CAPT Alyx Derenzis FROM LCDR Lorena Kaelohanui SUBJ New Regular Duty Assignment |
Lieutenant! I hope you're adjusting to life aboard the Shackleton. I know duties since the LHS 1670 mission have been a little slapdash, but we now have a new regular post for you!
Starting tomorrow at 1600, you'll be serving as our new Beta Shift Mission Ops Officer on the bridge. So you'll be responsible for all our communications and mission resource allocation during that shift. The Beta Shift Ops Officer will still handle most major shipboard operations.
Now your performance on the away team sent to the Tuttle hasn't gone unnoticed, so I've also placed you on the away team roster. In those cases, Lt. Erdi Ireso will take over while you're on the surface. But if you prefer to stay off away teams, let me know, and I'll change the roster.
Duty shifts will be Monday-Friday, with weekends off. We all need some time to unwind, after all!
Got questions? Ping me, night or day!
//SIGNED//
Lieutenant Commander Lorena Kealohanui
Chief Operations Officer / U.S.S. Shackleton
![]() |
Stardate 95628.1
Security Level 1 - Open TO LTJG M. Khet CC CMDR T. Akaela; CAPT A. Derenzis FROM LT Voyrays SUBJ Engineering Standard Duty Assignment |
Greetings, Khet-Lieutenant,
After much consideration, I have decided to employ you in two capacities if you feel up to the challenge. I have taken your technician background and your performance during the Icarus Probe design and construction work, and have assigned you to join Maintenance Team 9, under Lieutenant Wright. Team 9 handles maintenance for Sickbay facilties on both Decks 12 and 16. Your first shift with Team 9 will be Stardate 95669.4.
The Captain was sufficiently impressed by your performance during the LHS 1670 mission that she has also requested your presence on the Bridge. I am assigning you the Beta Shift Bridge Engineering Position for Fridays; your first shift with them will be Stardate 95659.4. Should you find bridge duty to be to your liking, we can discuss altering your assignment to have you as a more regular presence on the Bridge; and contrariwise, should you not prefer bridge duty, we can discuss an assignment that you may find more preferable. You will also have what humans call the 'weekend' as days off, though as a member of maintenance, you may be called to duty for emergency repair work.
If you have questions or concerns about your assignment, do not hesitate to contact me.
May your children see the Springtime.
//SIGNED//
Voyrays-Lieutenant
Chief Engineer / U.S.S. Shackleton
((OOC: Beta Shift is for IC reference only; our regular events remain at Gamma+2!))
3 Likes
![]() |
Stardate 95657.6
Security Level 1 - Open ![]() TO LT Voyrays FROM LTJG Khet, Mossic SUBJ Re: Engineering Standard Duty Assignment |
Thank you Voyrays-Lieutenant. I'm proud to be selected for bridge duty so soon. I will do my best to represent the engineering department well.
//SIGNED//
Lt. J.G. Mossic Khet
Engineering, U.S.S. Shackleton
1 Like
![]() |
Stardate 95676.8
Security Level 1 - Open TO CMDR T. Akaela; Shackleton/Dept. Heads CC FROM CAPT A. Derenzis SUBJ Upcoming Missions: Kelterre Sector |
We have two missions in Kelterre Sector we need to prepare for.
Our first assignment is to render assistance at the research outpost on Kelterre II. The outpost staff has reported the arrival of several unknown objects in the ocean of that world. Because of Kelterre II's unique atmospheric contaminants, transporters will not be available for regular or emergency operations planetside; we will be relying exclusively on shuttlecraft. Department heads are required to alter their plans accordingly. I expect Xenobiology and Planetary Sciences to be ready to act as soon as we reach orbit.
Our second assignment will be the Renovaman Cluster mapping mission, which Command has approved. Feel free to pass congratulations to Lieutenant Commander Sylvester Whittaker of Stellar Cartography next time you see him. This will be a month-long mission, and we can expect limited communications with DS-13 for over half of that time. A special warning has been issued about asteroids in the cluster bearing a highly dangerous substance. For this reason, we will not be conducting away missions to or sample collections from asteroids in or near the cluster. At the same time, we should consider contingencies should we face threat of infection; Tactical, Security, and Medical are required to review the reports of the last encounter with this substance, and devise countermeasures and contingency plans.
Beyond that, we will consider additional operations near the cluster so long as they do not interfere with our assignment or expose the ship to 'enpurplement'. Proposals, interdepartmental resource allocations as well as departmental personnel assignments should go to Commander Akaela for review.
Both of these assignments are why the Shackleton was built. I have complete confidence in each of you and your staff to bring these assignments to satisfactory ends. Let's show the rest of the 38th how it's done.
//SIGNED//
CAPT Alyx J. Derenzis,
Commanding Officer / U.S.S. Shackleton
//ATTACHMENT//Kelterre-II.file
//ATTACHMENT//renovamen-cluster.file
//ATTACHMENT//uss-ceres-recovery.aar
3 Likes
![]() |
Stardate 95725.1
Security Level 2 - Confidential TO LTJG Mossic Khet; ENS Fonnu jav Zhosh; ENS Rose Shaw CC CAPT Alyx Derenzis; CMDR Tala Akaela FROM LT Stavic SUBJ Xedi Probe Analysis Assignment |
Officers: peace and long life,
Effective this stardate we have been assigned to study the probes secured on Stardate 95722.4. Individual assignments to follow:
Lieutenant Khet, you will be assigned to study the control, communications, and data storage of each probe. Should there have been any erasure, you will also be tasked with data recovery.
Ensign jav Zhosh, you will be assigned to study the hull materials and alloys used in the probe's construction. It will also be your task to find ways either to get past the sensor-scattering effects of the hull so that scans may be conducted, or to open the probe so your fellow officers may have access to the probe's interior.
Ensign Shaw, you will be assigned to study the power and propulsion systems of each probe. Initial sensor reports indicate a possible fusion power source; please follow up on this.
Report to Cargo Bay 8 at 0900 hours tomorrow morning to begin work. Please note that security on this analysis is listed as classified and make sure your reports are labelled accordingly.
Live long and prosper.
//SIGNED//
Lieutenant Stavic,
Systems Engineer/U.S.S. Shackleton
2 Likes
![]() |
Stardate 95791.3
Security Level 1 - Open TO Shackleton/All CC FROM LCDR L. Kealohanui SUBJ Computer Core Downtime and LCARS Update Schedule |
The Captain's given the green light for a full scan, copy, and update of the LCARS operating system on all three computer cores on the Shackleton. While we'll be taking each core out in sequence and testing carefully before putting it back in the network, we have to watch out for, in the Captain's words, "the hidden volcano". So, here's our planned update schedule and how it will affect YOU.
Stage One will be a sync operation of all data files on all three computer cores. This will take place on Stardate 95792.0 and will take upwards of two hours to complete. This will be in the middle of Gamma Shift, so nothing important will be happening (I kid! I kid!) but please keep computer usage to a minimum during that time.
Stage Two will involve the Primary Computer Core going offline for a full OS Update and Level 1 Diagnostic, starting at 0600 hours that morning. We expect the update and diagnostic to take eight hours total, with the Level 1 Diagnostic taking up the lion's share of that time. All Computer functions will be shunted to the Secondary and Engineering Cores, and so normal operations should be unaffected.
Once the Primary Core clears the diagnostic, we'll be taking the Secondary Core offline, first to perform a data file sync back to the Primary Core, and then to repeat the OS update and Level 1 Diagnostic on the Secondary Core. The Secondary Core is scheduled to go offline on 95794.1. During this time all computer functions will be exclusively through the Engineering Core. Although the Engineering Core is more than capable of handling all ship functions by itself, we'll be putting a freeze on nonessential computer use. Holodecks will be offline for this time, and people using replicators can expect some delays while getting their food. I know the last one is going to suck, but we don't want a repeat of the Coffee Tubegrub Incident, trust me!
Once both Primary and Secondary Cores are updated and working properly, we'll switch computer functions from the Engineering Core back to the Primary and Secondary Cores, and take the Engineering Core offline for its update and diagnostic. Barring delays, this handoff will occur on Stardate 95797.2. This will bring us back up to two cores operating in sync, and so holodeck and replicator restrictions will be lifted.
Finally, once the Engineering Core update is complete, we'll perform a final data file sync between all three cores. All three computer cores will be back online and computer functions restored to normal by Stardate 95799.3.
I realize this is a lot of time, but this is a big operation. We'll be running full virus and malware scans during data syncs and updates, but please remember to practice safe downloading practices when linking to networks off the ship. All it takes is for one 'Ferengi Prince' message to get in to ruin everyone's day! That will make the Captain cranky, and we don't want her cranky, do we?
We'll keep you posted if there are any changes to this schedule. Check with your department head if you or your section has questions or concerns about the update.
Thanks in advance for your patience!
//SIGNED//
LCDR Lorena Kealohanui,
Chief Operations Officer / U.S.S. Shackleton
3 Likes
![]() |
Stardate 96016.1
Security Level 1 - Open TO Shackleton/ALL CC FROM LCDR Gov Hlolsh SUBJ Annual Physical |
We're now in a new year as the humans count them, and as per Starfleet Protocol that means its time for your annual physical and psychological examinations. Both Main Sickbay and the Sickbay on Deck 16 are currently cleared of patients and staff are waiting for you to show up. Contact myself or Dr. T'Luka to set up an appointment for your physical, and contact Counsellor Naismith for your psych examinations. If things get too busy, you're welcome to contact the starbase medical staff and have your examinations on DS13.
I know some of you hate to come to sickbay as much as I hate seeing people enter, but regulations must be followed - there are to be NO EXCEPTIONS. I want ALL assessments to be done and filed no later than Stardate 96084.9 (Jan 31). As an incentive for you stubborn types; the next day marks the Shackleton's completion of its first year in space and I know the Captain is planning a celebration. Get your assessment done before then, I'll clear you fit to celebrate as much as you like.
If you're late, not only will you not be cleared to attend the celebration, but I will be certain to make your assessment as long and uncomfortable as medical ethics and Starfleet Protocol would allow. We Tellarites know how to be stubborn, so don't push me.
//SIGNED//
Dr. Gov Hlolsh,
Chief Medical Officer / U.S.S. Shackleton
(OOC: This is more a narrative hook for any medical RP Shackleton players might want to do; if you prefer to handle that stuff off-screen, feel free! I'll be available to bring NPC Hlolsh along for some assessments, and I've talked to Calyx about bringing T'Luka to conduct some if asked. Feel free to put in your request ICly here, but please coordinate with us on our Discord channel so we can get scheduling right - some of us have a tight window of opportunity.
You can also consider this advance warning for a social event I'm planning for sometime on Feb 1. Official event notice will be forthcoming!)
3 Likes
The following was broadcast on allcon through the Shackleton:
Attention all hands, this is the Captain,
In a few hours, an inspection team from the Advanced Starship Design Bureau will board this ship. You've all heard about this inspection from your respective department heads, but since rumours are flying faster than facts, especially since the inspection team lead made such a lousy first impression, I feel that some things must be stressed for the coming days.
First, contrary to rumour, we are not being decommissioned. This inspection is one of several being conducted on Nebula Class starships throughout Starfleet, in a bid to assess the viability of this class in future. I am aware that, at 66 years, the Nebula has hardly reached the vintage of older designs still in service, such as the Miranda, or the Excelsior. However, it is Starfleet's responsibility to make sure that the ships of the fleet are able to continue to uphold this organization's mission statement. Such reviews as we're about to experience are a necessary part of that process.
To that end, I expect every member of this crew to be on their best behaviour while the inspection team is aboard. I know some of you have expressed not just concerns but anger, especially towards the team lead. I must ask you to shelve those feelings for the time being. Consider yourselves not just crew aboard this ship, but representatives for what the Nebula class can do. It would not serve to antagonize the inspection team.
Some of you in the engineering and operations departments will be asked to assist members of the inspection team with their tasks. Your respective department heads will hand out specific assignments shortly. If you feel that you cannot carry out such assistance for any reason, please speak to your immediate superior; if those reasons are valid, another will be assigned in your place. If it helps, you will not likely have to interact with the team lead himself, but rather with his subordinates. I expect they will be on their best behavior as well. Should there be any friction between our crew and the inspection team, please speak to your superior officer at once to submit a full report.
We will certainly require the skills and support of our Operations officers above and beyond this inspection. Command has recommended that we step up our resupply efforts while the inspection is ongoing, so that we may resume our exploratory and science mission with dispatch once the inspection is complete. I take this as a sign of confidence from Command that we will emerge from this trial faultless.
I will be keeping my ready room open to all who have further questions or concerns about this inspection, its team members, or the future of this ship. I will also be granting limited shore leave to Deep Space 13 for our crewmembers who may wish to spend time away from the ship while this is going on.
Finally, I remind you all of the trials we have faced together. We have rescued pilgrims and colonists. We have faced pirates, terrorists, multidimensional beings and neurogenic weapons, and triumphed. We have escaped a dying sun, and captured a piece of a dead sun. Most recently, we averted tragedy, saving a ship of wayward travellers and an entire civilization. We have done all these things at risk to ourselves, but though some of us were injured in these trials, not one of us has been lost. Compared to these, an inspection holds little fear.
Our dedication plaque reads "Optimism is true moral courage." Let us prove it right by our actions and our attitude.
Thank you.
//SIGNED//
CAPT Alyx J. Derenzis,
Commanding Officer / U.S.S. Shackleton
![]() |
Stardate 96097.8
Security Level 1 - Open TO Shackleton/ALL CC FROM CAPT A. Derenzis SUBJ Starship Inspection |
Attention all hands, this is the Captain,
In a few hours, an inspection team from the Advanced Starship Design Bureau will board this ship. You've all heard about this inspection from your respective department heads, but since rumours are flying faster than facts, especially since the inspection team lead made such a lousy first impression, I feel that some things must be stressed for the coming days.
First, contrary to rumour, we are not being decommissioned. This inspection is one of several being conducted on Nebula Class starships throughout Starfleet, in a bid to assess the viability of this class in future. I am aware that, at 66 years, the Nebula has hardly reached the vintage of older designs still in service, such as the Miranda, or the Excelsior. However, it is Starfleet's responsibility to make sure that the ships of the fleet are able to continue to uphold this organization's mission statement. Such reviews as we're about to experience are a necessary part of that process.
To that end, I expect every member of this crew to be on their best behaviour while the inspection team is aboard. I know some of you have expressed not just concerns but anger, especially towards the team lead. I must ask you to shelve those feelings for the time being. Consider yourselves not just crew aboard this ship, but representatives for what the Nebula class can do. It would not serve to antagonize the inspection team.
Some of you in the engineering and operations departments will be asked to assist members of the inspection team with their tasks. Your respective department heads will hand out specific assignments shortly. If you feel that you cannot carry out such assistance for any reason, please speak to your immediate superior; if those reasons are valid, another will be assigned in your place. If it helps, you will not likely have to interact with the team lead himself, but rather with his subordinates. I expect they will be on their best behavior as well. Should there be any friction between our crew and the inspection team, please speak to your superior officer at once to submit a full report.
We will certainly require the skills and support of our Operations officers above and beyond this inspection. Command has recommended that we step up our resupply efforts while the inspection is ongoing, so that we may resume our exploratory and science mission with dispatch once the inspection is complete. I take this as a sign of confidence from Command that we will emerge from this trial faultless.
I will be keeping my ready room open to all who have further questions or concerns about this inspection, its team members, or the future of this ship. I will also be granting limited shore leave to Deep Space 13 for our crewmembers who may wish to spend time away from the ship while this is going on.
Finally, I remind you all of the trials we have faced together. We have rescued pilgrims and colonists. We have faced pirates, terrorists, multidimensional beings and neurogenic weapons, and triumphed. We have escaped a dying sun, and captured a piece of a dead sun. Most recently, we averted tragedy, saving a ship of wayward travellers and an entire civilization. We have done all these things at risk to ourselves, but though some of us were injured in these trials, not one of us has been lost. Compared to these, an inspection holds little fear.
Our dedication plaque reads "Optimism is true moral courage." Let us prove it right by our actions and our attitude.
Thank you.
//SIGNED//
CAPT Alyx J. Derenzis,
Commanding Officer / U.S.S. Shackleton
3 Likes
TO LTJG Khet FROM LT Mercer SUBJ Your Pal |
Khet,
I sure hope you've gotten better about reading your emails. I was on computer core diagnostics when your friend from the party showed up, wanting to install a program. I had the computer scan it and it couldn't come up with any reason not to, so I installed it read-only and he left. I don't see anything wrong with the code so I don't want to ring the captain's bell yet, but I thought to myself, what engineer do I know who could give it a really thorough interrogation?
Happy hunting.
//SIGNED//
Lt. Mercer
Operations/Shackleton
//ATTACHMENT//pierce-06.bin
2 Likes
![]() |
Stardate 96108.9
Security Level 1 - Open ![]() TO LT Mercer, Olivia FROM LTJG Khet, Mossic SUBJ Re: Your Pal |
![]() |
IDK what this is supposed to be for. They already have access to all the logs they could want. There's no reason for this and it could represent a security risk if it's used to bypass normal access control measures. They need to justify any elevated access they need, instead of installing an insecure back door. I'm going to ask about it and if I don't get good answers I'll bring it to the captain.
//SIGNED//
Lt. J.G. Mossic Khet
Engineering, U.S.S. Shackleton
2 Likes
![]() |
Stardate 96152.2
Security Level 3 - Restricted TO <Shackleton/Senior Staff> CC <38th/Command> FROM CAPT A. Derenzis SUBJ Urgent Situation - Shackleton Repair and Battle Readiness |
Officers,
Please read the attached communique from the Admiral. I must stress this information is classified RESTRICTED.
I am calling an emergency senior staff meeting at 1800 hours Station Time to discuss the situation and our options. To prepare, I have tasks for each of you:
Lieutenant Voyrays, I will need estimates on how quickly the Shackleton can be repaired, with special attention to our operational status by the end of the timeframe outlined in the communique. While it would be nice to assume the drydock staff will assist, give me estimates assuming that we will not have the drydock's resources to help.
LCDRs zh'Cholal and Kaelohanui; I need your latest tactical readiness updates; Lorena, I also need you to draw up a list of nonessential crew to remain on the Starbase if and when we are needed to assist in the larger operation. Dr. Hlolsh, estimates on restoring our sickbay and needed supplies not only for dealing with injured crew, but with people we may have to rescue from the battlesite.
CMDR T'Vrin, I need you to get up to speed on the listed projects in the communique; specifically Teleraptor and Udox. Coordinate with LCDR zh'Cholal and LT Voyrays on the feasibility of adapting these defenses to our systems.
CMDR Akaela, clearly any preparations we make will depend on our ship's status and the attached investigations being wrapped up in a satisfactory manner for all concerned. If you are able to give me an update on if and when we can expect to resume repair operations, it would be most helpful. I will also need you to give us an overview of the Confederacy of Azed and the strategic concerns surrounding our relations with them.
Our current ship status will clearly preclude our ability to take part in the aforementioned operation in the Dartius system, but we may still have a role to play in backup and rescue operations after the battle or, if worse comes to worst, in defending this starbase from Azedi attack. We have been bloodied, driven from our home, and strained by the past week, but we must pull through. The Federation needs us to aid it; and I do not believe any one of us can dare turn our backs. I have confidence in each of you to rise to the challenge before us.
//SIGNED//
CAPT Alyx J. Derenzis,
Commanding Officer / U.S.S. Shackleton
//ATTACHMENT// Operational Update - SD96152.1
3 Likes
![]() |
Stardate 96191.6
Security Level 1 - Open TO CMDR T. Akaela CC CAPT A. Derenzis FROM LT Voyrays SUBJ Repair Update and Ship Status |
Greetings, Akaela-Commander,
We have completed our repairs to the damaged systems on Decks 22 and 26, and will begin final tests on ship systems tomorrow. We have also purged and reset the diagnostics programs that Pierce-Commander sabotaged. Barring unforeseen difficulties, we should be fully spaceworthy by Stardate 96194.4.
Holodeck 3 on Deck 10 will still be offline for some days more; two walls and a large portion of the floor were destroyed by the EPS explosion and plasma fires. Now that more critical systems are back online, I have detailed two teams to commence repairs. I estimate Holodeck 3 will be back online by Stardate 96206.9. The other holodecks are, of course, operational and free for the crew to use.
May your children see the Springtime.
//SIGNED//
Voyrays-Lieutenant
Chief Engineer / U.S.S. Shackleton
4 Likes
TO LTCDR Kealohanui CC FROM LT Ledar SUBJ Vivariam and quarters modification |
I am about to transfer aboard the Shackleton as assistant chief of security, and have a requirement for a habitat for a pet.
My pet is a mature male Birgus latro, a terran arthropod commonly known as the Coconut Crab. Due to the nature of the species, it requires a vivarium, rather than being allowed to roam my quarters. Ideally, this would be 5x3m, extending to the ceiling, and contain a selection of terran 'desert island' flora, such as palm trees, with a small water feature to provide drinking water. Tek is extremely friendly and non-aggressive, but is capable of causing broken bones and damaging hands, so requires this level of containment.
It would also be medically advisable to have the majority of my quarters at 1.35G, the gravity in which my species evolved. Normally, I would adjust the environmental controls, but there is a need for Tek's enclosure not to be affected, as he did not evolve in 1.35G.
If it would be possible to arrange these adaptions, it would be greatly appreciated by both myself and Tek.
//SIGNED//
Lieutenant Kelzi Ledar
Assistant Chief of Security (transferring), USS Shackleton
//Vivarium Specifications// filename.log
2 Likes
![]() |
Stardate 96350.1
Security Level 1 - Open TO LT K. Ledar CC FROM LCDR L. Kaelohanui SUBJ Re: Vivarium and quarters modification |
Hi Kelzi, and welcome to the Shackleton family!
So, I talked over your request with Voyrays, our chief engineer, and he says its doable. We'll need to split the grav generator circuit into two, one for the vivarium and the other for the rest of your quarters. I also talked with our botany people, and they can get some plants suitable for little Tek. There is one specimen of Kekuna tree they can transplant from the arboretum, but we'll have to grow a coconut tree from seed - even with accelerated growth, it might not be available to produce coconuts for Tek for at least a year. Smaller plants should be no problem. If Tek gets bored of candlenuts, I'm sure the replicator can produce other foods he might like.
You'll be assigned quarters on Deck 3, Section 38 - that's an internal section, so no windows, sorry. Voyrays has a team assigned there now, so we should have it all ready by the time you beam aboard. You're still coming on the U.S.S. Yoshiyuki, right? We're scheduled to rendezvous with them tomorrow morning.
//SIGNED//
LCDR Lorena Kaelohanui,
Chief Operations Officer / U.S.S. Shackleton
3 Likes
![]() |
Security Level 1 - Open
TO LCDR L. Kaelohanui/font] CC FROM LT K. Ledar SUBJ Re: Vivarium and quarters modification |
I'm taking a very brief layover at DS13 before I board the shuttle to rendezvous with the Yoshiyuki, as my previous assignment is still on patrol in the Ba'aja sector. I still expect to arrive tomorrow morning.
I'm sure Tek will be able to cope with candlenuts and similar foodstuffs. I'll definitely need to find a way to thank your botany department and the arboretum for being so generous to him, as well as yourself and the engineering department for making the modifications to my assigned quarters at such short notice. Regarding the lack of a window, this is not a problem. If anything, I prefer not having windows on my quarters, as it reduces my sensory load.
//SIGNED//
Lieutenant Kelzi Ledar
Assistant Chief of Security (transferring)/ USS Shackleton
//ATTACHMENT// filename.log
1 Like
![]() |
Stardate 96401.1
Security Level 1 - Open TO LT Kelzi Ledar CC FROM LT Boafo SUBJ Bridge Weapon Policy |
![]() |
When you have a free moment, could you stop by my office next to the Armory? Please bring the weapons you had on the bridge last weekend.
//SIGNED//
LT Boafo,
Chief of Security, U.S.S. Shackleton
![]() |
Security Level 1 - Open
TO LT Boafo/font] CC FROM LT K. Ledar SUBJ Re: Vivarium and quarters modification |
I will present myself shortly.
//SIGNED//
Lieutenant Kelzi Ledar
Assistant Chief of Security, USS Shackleton
![]() |
Stardate 96479.3
Security Level 1 - Open TO <Shackleton/Department Heads> CC FROM CAPT A. Derenzis SUBJ Upcoming Summer Leave and Refit |
![]() |
Everyone:
I know we've all been looking forward to the summer leave rotation, especially after the harrowing events of two weeks ago. First of all, I'm happy to report that the leave schedule has been approved, with a few small changes. Details are attached below.
The reason for the change is that Starfleet Command has decided to push forward the Shackleton's scheduled refit. Part of this is due to our battle performance at Doza-L605, but it is also partly due to the ASDB looking to make amends for the inspection debacle earlier this year. There are a number of upgrades that will be installed and tested to improve the ship's overall performance. For the leave schedule, this boils down to some departments will be getting a longer shore-leave than expected, while others - engineering and operations specifically - will have a more staggered leave schedule, to insure experienced staff are on hand to assist the spacedock staff with the refits.
I have also been informed that Starfleet has granted us permission to submit a "wish list" of upgrades in addition to the standard refit. They've sent us some guidelines, which I've attached to this message, to help ground any suggestions we may put forward. So I would like each of you to take some time to poll your respective departments on upgrades or new equipment you would like to see. Please have your submissions sent to CMDR Akaela no later than Stardate 96526.0 (July 11). The engineers heading the refit will have final refusal on suggestions if they get too outlandish. No, Zarsa, we will not be installing a phaser lance.
I look forward to seeing your suggestions. Together we can make this ship the finest in the Fleet.
//SIGNED//
CAPT Alyx J. Derenzis,
Commanding Officer, U.S.S. Shackleton
//ATTACHMENT//
leaveschedule2419-summer.doc
refit-suggestions-guidelines.doc
refit-suggestions-guidelines.doc
((OOC: Suggestion Time! This is to give all player crew members a chance to change up bits of the Shackleton. If your character has a suggestion for their department head, submit it in this thread as a message. Acceptance will depend on how good a case you can make for your suggestion! There won't be any structural changes as that goes far beyond a standard refit (so no fighter bays or lateral torpedo launchers, for example), but beyond that almost anything goes. If you haven't already, take some time to familiarize yourself with the Ship Specifications and Deck Layout to see what we have now. You have until July 11 to get those suggestions in! ))
3 Likes