Stats

  • 9 Mission Posts

Last Post

Sun Dec 8th, 2019 @ 1:34pm

Chief Petty Officer "Chief" Alpha I

Name "Chief" Alpha I CSH

Position Chief of the Boat

Rank Chief Petty Officer


Character Information

Gender Male
Species Hologram (AI)
Age 31 (appearance)

Physical Appearance

Height 1.83m
Weight 74kg
Hair Color Light Red
Eye Color Blue
Physical Description Still to do

Family

Spouse N/A
Children N/A
Father Lewis Zimmerman, Reginald Barclay
Mother N/A
Brother(s) N/A
Sister(s) N/A
Other Family Various scientists at Jupiter Station and Daystrom institute who contributed to the project development. Holomatrix based off of the USS Voyager’s EMH Mk I, a.k.a “The Doctor”, using the experience and development he gained during Voyager’s mission in the Delta Quadrant. Additionally, emotion matrix based off of Noonien Soong’s (and Juliana O'Donnell) work on the Soong Type Android and subsequent Emotion chip.

Personality & Traits

General Overview To do
Strengths & Weaknesses Strengths


  • Instant access to all computer functions in any Starfleet or Federation based facility. Additionally, Chief is able to transfer itself into any other Federation based computer system for remote access and control


  • Ability to fulfil any role required by accessing Federation Database for knowledge. Chief is also based off of the EMH, ECH and ESH programs, so he has a robust built-in Medical, Command and Security/Tactical database.


  • Doesn't require food, rest or recreational time. Therefore he can be called on at any time for anything.


  • Can duplicate itself in multiple locations at once (up to 5 independent avatars)




Weaknesses



  • Unlike other holograms, Chief is unable to modify his looks, height or voice print and he has the same physical strength as a normal human. This is to prevent it from being able to impersonate other beings as a security precaution. However, Chief can alter whether or not his body is "solid" or not, therefore he is able to bypass most weapons and obstacles (Direct attack to the computer core, holo-emitters or energy dampening weapons are still effective)


  • Chief is still an active development project so it may have unknown instabilities. As a result, several "backdoor" commands are in place should anything negatively affect him. These commands are designed to terminate any or all functions of Chief if needed. Additionally, a specialised computer virus has been designed to aggressively erase any trace of Chief, effectively killing him. Chief knows about the existence of the commands and virus but does not know their exact content and composition, therefore making it impossible to adapt to them.


  • As with any hologram, Chief is unable to physically exist without holo-emitters (though he can still transfer to some computers) therefore he is unable to leave the ship/station. Additionally, due to the complex nature of his program, he requires a large amount of computer resources, so he is unable to transfer into a portable medium such as PADDs and Tricorders.


  • While Chief is able to interface and use any system within the ship, Chief can not take control of a station that is currently being used by a Crew member without a direct Command order. Most of his day to day roles are passive and diagnostic in fashion.


  • As with all machines and computers, Chief finds it difficult to evolve and make 'Leaps of faith' etc. A machine only knows what it knows and is inputted into it, Chief is limited with 'Creative solutions'.




(While Chief is still a very powerful character, I have attempted to include more weaknesses and controls so that he is not insane or can be abused. Additionally, I have no desire to play him as a God-like character and will have further limitations as he develops. I want to play an interesting character, not an OP one)
Ambitions As a hologram in its early stages, Chief currently has very limited ambitions beyond what is already programmed into him. Chief does desire to better integrate into a Starfleet crew and become a true asset to that crew, hopefully paving the way for other programs such as himself being adopted by Starfleet. Chief is also curious about interacting and co-existing with other beings outside of Jupiter Station, seeing the diversity of life first hand and close up.

Chief has also been programmed with learning and development subroutines, meaning that he will be able to grow and develop in time, as a normal being does. It is the hope of his creators that Chief can become more than a machine, much like The Doctor did.
Hobbies & Interests To do

Character Bio

Personal History Early life / Research phase (2371 - 2375)

The Command & Support Hologram (Or CSH for short) was first conceived shortly after Dr Lewis Zimmerman completed his work on the Mk 1 EMH program, it was his ambition to create a wide range of Holoprogames that would work alongside real Crew to help increase efficiency and reliability of Starfleet vessels. The early drafts of the CSH defined a program that was easily adaptable to any situation and was able to provide any data needed, much like a walking/talking encyclopaedia.

However, the project was put on hold indefinitely following the stunted launch and unpopularity of the EMH Mk1, large numbers of Starfleet personnel saw very little need for Holographic crews and when it was needed, crews reported that the EMH Mk1 was difficult to work with, most commonly citing personality issues.

While the CSH program was suspended, Dr Zimmerman continued to develop several other EMH programs, each with varying degrees of success. With each successful iteration of the EMH programs, Starfleet was becoming more open to the use of Holoprogames, but there were still a number of hardliners that didn't want a fully integrated hologram, citing various security concerns about letting a computer control itself.
Despite this slight forward progress, the project was once again put on hold due to a much larger need. The Dominion had launched a full-scale war against the Alpha Quadrant and all available resources were diverted towards defence.

Zimmerman continued to pursue his ideas of a more long term Hologram, looking to improve on the general failure of the Mk 1 program. To help improve the chances of success, Zimmerman decided to base the new program off of someone other than himself and someone who is already a respected Doctor. With this in mind, Zimmerman travelled to Deep Space 9 to speak to and study Dr Julian Bashir, the Chief Medical Officer of DS9.

Initially, the program started off well, Bashir was well-liked and respected among his peers and he also was an accomplished Doctor. Zimmerman started drafting a base template hologram with Bashir's likeness, personality and attributes. However, the project had to be cancelled shortly after it started due to the revelation of Bashir's genetic engineering status, Zimmerman felt that a program based off of an illegal procedure would not be successful. While the LTMH program was scrapped before it could truly begin, it did provide some interesting insights for the future.
Before the end of the war, Zimmerman once again returned to DS9 but not to study Bashir, this time it was to study someone else entirely. Word had reached Zimmerman about a hologram that had been running near constantly and had a good degree of popularity among the crew and visitors, Vic Fontaine. Zimmerman worked closely with the hologram to study it's program, to learn how to make his programs more stable, how to develop more relatable programs that people can connect with easier. Zimmerman also studied all the engineering reports based on Fontaine and as much of his base code as possible. While Fontaine's program was unique and impossible to replicate, it was able to help Zimmerman improve his own designs to have more useful programs.

Throughout the bloody war, Starfleet officers depended more and more on the EMH programs, especially in the case of large scale traumas. Slowly, the opinion on Holographic crew began to change as they demonstrated their usefulness and capabilities.
Eventually, the crew of the USS Voyager was able to establish a stable line of communication with Starfleet, which allowed the crew to send messages back home. Additionally, the crew was able to send The Doctor back to the Alpha Quadrant to help care for a then terminally ill Dr Zimmerman.

At first, Zimmerman refused to be treated by a "failed program", but The Doctor attempts to assure him that he was more than his original programming and that he wasn't another failure. Eventually, Zimmerman relented and allowed The Doctor to treat him and cure his terminal illness. Zimmerman was also able to learn several things from The Doctor, how his program was able to function for so long, how it was able to adapt and grow from his original design and most importantly, how The Doctor had not only become a valued member of Voyagers crew but also a friend. These discoveries and a copy of The Doctor's program helped Zimmerman further his work into long term holograms.
With the combined research from the various visits to DS9 and also studying The Doctor, Zimmerman decided to restart work on the CSH once more but without informing Starfleet, he would continue his work on EMH programs as Starfleet required, he simply decided that he did not want for Starfleet to eventually be ready in order to begin development. Zimmerman would build the CSH and present it to Starfleet when needed.


The Project begins (2376 - Mid 2377)

In order to keep the CSH program secret, Zimmerman informed Starfleet that he was beginning work on the EMH MK 4 (Which was true as well), he only worked on the CSH during his off-hours and the privacy of his own quarters. This approach would take more time to develop, but it ensures that Starfleet couldn't prematurely shut down the CSH as it once did.

Zimmerman began by building a basic holomatrix that was designed for longevity and growth at its core, after all the CSH would be designed to run 24/7 with only minor downtime. Initially, progress was slow and tedious, the developing holomatrix was able to run much longer than normal Holograms but it did start to suffer integrity issues after a few days of simulation. Another issue of the early framework was that of system use and power requirements, even though it was just a basic frame, the program required a staggering amount of resources to run which wasn't an ideal outcome.

To help solve both issues, Zimmerman looked at his notes collected from both The Doctor and Fontaine's program. To solve the issue of resource drain, Zimmerman decided to compartmentalize some of the CSH's functions and subroutines, that way they were not active and drawing resources when not needed, while only sacrificing minimal efficiency. Additional optimisation and compression would come later on in the development cycle, but this was a good start.

The CSH would still need it's own dedicated computer processors and power supply, though this added additional protection, redundancy and security to the program and facility it was installed in. Having the CSH not directly built into the facilities mainframe means that it could be disconnected or removed if needed, without compromising the main network.

While the resource issues was a relatively easy fix, the lifespan issue was not as easy. Zimmerman experimented with several fixes, all providing small amounts of stability and strength. Eventually, a breakthrough came from The Doctors own program and troubles within the Delta Quadrant, during which the crew of Voyager had to "graft" his program with the Hologram Diagnostic Tool that was installed as part of the EMH suite.
Zimmerman programmed the CSH to automatically access and patch any stray parts of its code, but he also included the ability for the CSH to be grafted onto another blank holomatrix (of the same type) if the program became unstable. Furthermore, every crew would be provided a complete diagnostic toolset that included special programs that could completely remove and reinstall the CSH in case of catastrophic failure. Finally, the CSH would be programmed to complete a complete high-level self-diagnostic every week, automatically recording and reporting the results of the diagnostic without failure, regardless if there were any issues or not.

Now that the core holomatrix was developed and it was as stable as possible, Zimmerman went on to begin developing the functions of the CSH. The initial intent was for it to be able to access any unclassified data stored on any Federation network and be able to provide instantaneous calculations or reports on facility status, but Zimmerman felt this was not enough as any computer could do that. He wanted to program to be an integral part of any crew, to be more than just a walking fact machine, however, there was still some lingering hostility toward Holograms despite their success during the Dominion war.

It was at this time another major event occurred, Voyager's surprise return back to the Alpha Quadrant. While this was a monumental occasion for most due to the safe return of a stranded crew, Zimmerman saw another great opportunity. Rumours began to circulate that Voyager had brought back several different advanced technologies, both from the Delta Quadrant but also a few futuristic technologies and even some Borg adapted techs. While the vast majority of those techs were of no interest to Zimmerman, as well as being severely classified, the improvements to Voyager's Holotechnology was.

Since the last time they had met, The Doctor had made further expansions to his programming, predominantly the development of his Emergency Command Hologram sub-routines. This gave Zimmerman the idea and breakthrough he wanted, a way the CSH could be more than what it was. After reading through the reports and designs of the ECH, which were simple at best, Zimmerman decided to adapt and improve it for his purposes.

The CSH would now be able to command any Starfleet vessel or facility in an emergency situation, where the command staff were incapacitated or had to evacuate suddenly. While this would provide a large benefit to Starfleet, Zimmerman also recognised that some members would be against this development due to security concerns and the potential of a rogue AI taking control. With that in mind, Zimmerman made those sub-routines inaccessible to the CSH and they'd also require two command-level officers to enable, the CSH would still be aware of the sub-routines, but it would be unable to activate them by itself.

Furthermore, Zimmerman made a note to not give the CSH the ability to alter its voice or physical parameters, while he hadn't begun to develop those parts of the program, he suspected that more people would accept the CSH if it was unable to copy them.

At this point in development, while Zimmerman was also working on the Mk 4 version of the EMH program, that he thought of another use of the CSH. It could act as another backup EMH program as needed, running alongside or instead of the usual EMH programs. Moving forward in the development process, Zimmerman would include all of his EMH sub-routines and breakthroughs into the CSH ensuring that it will be as versatile as possible.

The downside to all these additions to the CSH program was starting to show effect, each new subroutine was causing the program to grow exponentially in size and complexity, which started to lead to unexpected failures and performance issues such as program instability and increased lag time when performing tasks. If it could not be stabilised, the CSH program would never launch and all the effort would have been for nothing. Over the next several months, Zimmerman focused all of his spare time reviewing and rewriting several sections of the CSH, attempting to compress and optimise its code without hindering performance. Zimmerman secluded himself in his own lab for hours on end, even more so than usual, revising code and reviewing all of his research from the last 6 years.

Although Zimmerman was never an overly social person, this was a new level for him. This new level of seclusion began to concern one member of Zimmerman staff and possibly his only friend as well, Reginald Barclay. Barclay kept trying to raise his concerns with his friend but kept getting shut down, Zimmerman stating that he was working on an important program and didn't wish to be disturbed. While this was partially true and eased Barclay's concerns a little, he was still uneasy with the situation so he decided to keep an eye on Zimmerman.

After a while, and much persistence, Zimmerman finally revealed to Barclay what he was working on and his ideas. Initially, Barclay had extremely large concerns about the CSH as well as the fact Zimmerman was developing the project in secret, without approval from Starfleet. Barclay raised several arguments as to why a program such as the CSH would never be accepted by Starfleet and how it was dangerous to even develop one in the first place. Zimmerman argued back with the potential uses and benefits of the CSH, how it could revolutionise Starfleet ships and potentially save hundreds of lives, if not more. He also listed all of the security enhancements the CSH has in order to prevent it going rogue. When Barclay bought up Zimmerman's recent seclusion, Zimmerman informed him of all the issues he had been having with the CSH, it's complexity and growing instability. Though he wasn't convinced on the idea, Barclay could see Zimmerman's passion for the project, it was something he wouldn't give up, so he decided to try and help his friend with the CSH.

One becomes two (Late 2377 - 2378)

Now with Barclay and Zimmerman both working on the CSH, things began to progress a lot faster and easier. Many of the issues still existed but the duo were able to combine their efforts and ideas to fix the early problems with the CSH.

The program was nearing the point where Zimmerman would need to start developing a physical avatar and personality subroutines. Taking on board lessons learnt from the Mk 1 program, Zimmerman chose not to model the CSH after himself but create a new template instead. Working together, Zimmerman and Barclay designed an avatar that was male in appearance, of average height and build with a youthful but still experienced look. Since Zimmerman wanted the CSH to have a prominent role where it was installed, he gave the CSH a strong jawline and assertive nature, one that Barclay insisted was too aggressive but Zimmerman dismissed his concerns.

While Zimmerman was focused on developing the physical shell and basic personality, Barclay was coming up with additional ideas that can be integrated into the CSH to improve functionality and usefulness. An idea that interested him greatly was the ECH that had already been incorporated into the program, Barclay wondered just how far that kind of idea could be taken, would it be possible to create other variations such as Tactical or Engineering? What about a Science sub-routine? Using the ECH as a base, Barclay started developing his ideas further, the CSH would be able to switch roles as needed and have access to a limitless wealth of knowledge from the Federation databases, even completing tasks that may be too dangerous for a biological crew to complete.

While these ideas would revolutionise the CSH, Barclay quickly realised he would be unable to complete this task on his own, he may have been a good engineer but he was no scientists or tactician. Additional support would have to wait however, Zimmerman wasn't ready to go to Starfleet with the project yet, so all Barclay could do was lay down the basic foundations and hope they could be built upon one day.
With that portion of the project on hold, Barclay turned his mind to that of multiplication and expansion. He began to wonder if I could be possible to get a program as complex as the CSH to be able to sustain multiple avatars at once throughout a single ship or base. Other Holograms could easily duplicate themselves, but most other Holograms are just simple interactive story characters, nowhere near as complex as even the Mk1 EMH, let alone the CSH. Though it may seem like an impossibility, Barclay knows that Zimmerman had considered the same idea a few years before, even going as far as testing it out but all those tests failed. Despite those failures, Barclay continued with his ideas and research, technology had vastly improved since Zimmerman's early tests.

Barclay set to work, adapting Zimmerman's original ideas and blending them with his own, as well as factoring new technological breakthroughs. The first trials were moderately successful, Barclay was able to get the CSH to have multiple avatars but they weren't able to keep form for long, this effect was more pronounced the more avatars that were spawned. Realising this, Barclay decided to start small and get two avatars stable before increasing the number. After several weeks worth of work, numerous tests and tweaks, the CSH was able to successfully generate three avatars of itself before becoming unstable, Barclay accepted this achievement for now but still would prefer to increase that number.

Before the end of 2378, Zimmerman finally agreed that is was time to present the CSH program to Starfleet in order to get access to additional resources and personnel for further development. Both Zimmerman and Barclay made a joint presentation to a board of members from Starfleet Command, including Captain Montgomery Scott as the head of S.C.E and Commander Bruce Maddox, a member of the Daystrom Institute.

The initial reaction from the board was not positive, many felt that Zimmerman's secrecy with the project did not bode well, going behind Starfleet's back to create a potentially dangerous program. The board was ready to dismiss the project and order a cessation of all work on the CSH but Zimmerman launched into a heated discussion, reminding the board of all the good Holograms have done over the past 7 years, the aid they provided on the battlefields of the Dominion war and also that of The Doctor aboard the USS Voyager. Barclay reinforced Zimmerman's outburst, though a lot more tamely, with the list of security precautions that they have implemented into the CSH at its core, precautions that it can't alter or remove.

The combined arguments of Zimmerman and Barclay seemed to sway some of the board members, not all of them but enough of a majority. The pair were allowed to demonstrate the CSH and show the board their creation, which they spent the next several hours doing, covering everything from the basic code to the CSH's advanced learning and evolution subroutines. Impressed, but not fully convinced, the board of reviewers raised additional concerns about the security implications of the CSH and its still substantial resource drain.
Furthermore, the board felt that the CSH's personality left a lot to be desired, they felt it was very blunt and flat, while also being very arrogant in some ways, much like the original Mk 1 EMH. Zimmerman assured them that the personality was still in development and subject to enhancement providing the program be allowed to continue.

The meeting continued for a few more hours, with both sides providing argument and subsequent counter-argument, but eventually, a decision was made. Zimmerman and Barclay were given the approval to continue their work


The CSH lives, and gets a heart? (Late 2378 - 2379)

With approval from Starfleet Command, Zimmerman was able to bring the project out of the shadows and get the rest of his staff working on the CSH program, as well as bringing in other experts to the project.

The first task that needed to be worked on was the CSH's personality, or lack of according to the review board. With that in mind, Zimmerman requested that he be granted access to all of Noonien Soong's work on the Soong Type Android as well as he's designs for the emotion chip prototype. Additionally, he also requested access for himself and his team to the Daystrom Institutes vast research on artificial life. While Starfleet was sceptical at first, sighting the fact that his team was working on a Hologram and not an android so the data wouldn't be useful to the project.

However, Zimmerman persisted, stating that the Soong emotion chip was currently one of the best artificial emotion simulators and it could help him develop a more realistic personality. In addition to this, Zimmerman planned on contacting several Starfleet counsellors to help refine the developing the CSH's personality. He assured Starfleet that these steps were needed if they wanted a more lifelike result, Starfleet eventually granted access to the data that the team required.

While a portion of the development team worked on the CSH's new personality and emotions, Zimmerman, Barclay and another section of the staff focused on completing some of Barclay's earlier efforts with avatar multiplication and developing other specialists roles for the CSH, as well as general optimisation for the program overall.

Zimmerman started by critiquing, sometimes harshly, Barclay's earlier efforts but was generally impressed by the groundwork, though he seldom admitted it but Zimmerman considered Barclay a good engineer and programmer. The team began by looking into the multiplication issues and instabilities, it was discovered that the CSH was actually duplicating its program on partitions of itself when another avatar was generated, which lead to the program consuming more resources exponentially, thus causing the instability. After correcting this issue, the CSH now generated new avatars of itself using the one program, cutting down on the resources required and helping with the instability. As a result, the CSH was able to generate up to 5 avatars of itself without any issues, anymore than 5 caused too many fluctuations for Barclay to be happy, so he capped it at that.

Now that the CSH's core was working better than ever, Zimmerman turned his team's effort towards Barclay's ideas of expansion and making the CSH more flexible. Barclay gave a quick presentation on what he had envisioned, the ideas of having sub-routines for every department (Science, Tactical/security, Engineering etc) so the CSH can fill any role as needed. Since the basic framework of the idea was in place, thanks to Barclay's earlier work and also Zimmerman's work on the ECH idea, the team already had a good start. All that was needed was to populate the CSH with the knowledge it required to complete the various tasks, which could easily be provided from Starfleet's database, and also to train the CSH on how to use that knowledge.

As the CSH was designed to learn and evolve, the training period was perhaps one of the most important parts of this stage, after all, it is one thing to have raw knowledge but knowing how to apply that knowledge is critical. Since the team developing the CSH's new personality wasn't quite ready to integrate it into the main program, Zimmerman decided to spend that spare time testing the CSH's new expansions and getting the support team to help train it.

At first, the CSH performed as expected, like a machine reading from a database. Every task was completed by the book, which wasn't a bad thing but the CSH was unable to adapt easily or come up with new solutions to problems and it's environment. Zimmerman spent a few days tweaking the CSH's learning and adaptation subroutines, which helped it evolve beyond its core programming. After a few more days of testing and tweaking, the CSH was finally starting to adapt and grow to each new situation, it wasn't a large change but it was a start.
During the training cycle, one of the engineers suggested that they were going about the tests wrong, they should be schooling the CSH instead of forcing it to assimilate large amounts of raw data. At first, Zimmerman rejected the idea, stating that an advanced Holoprogame such as the CSH didn't need school but just time to parse the data it had been given. Barclay disagreed, and with a little help from the team developing the CSH's new personality, managed to convince Zimmerman to give the idea a try.

Over the next few days, the engineering team installed additional higher capacity holoprojectors throughout Jupiter Station's education centre, ready in time for the CSH's first day of school. A lot of the students, and even some teachers, were uncomfortable with having an "adult" as part of the class, but after a little time and encouragement, everyone soon blended in well. As expected, the CSH's base knowledge was far greater than anyone present in class and completed tasks easily, however, the classes weren't a total waste of time. The CSH was able to develop its personal skills far easier than any previous Hologram, it learnt a great deal about social interaction and etiquette, furthermore, it's self-learning subroutines were able to develop and take hold. Lastly, it was a good time to test the newly improved personality for the CSH, while it was a definite improvement over its original personality, the team still made some constant tweaks and adjustments.

Zimmerman decided that the school experiment was going well, though the work was a little easy, he decided to keep the CSH in school for the remainder of the year.

While the CSH was at school, Zimmerman and Barclay continued to improve its programming and refine the work they had been doing over the past year. They also took the time to review the work they had done and think of ways that it could be adapted in the future for other projects, more specialised Holograms or Holograms that can duplicate themselves more, or even a ship mostly crewed by Holograms? The possibilities were numerous.

Field testing (2380 - 2382)

After almost a year and a half worth of refinements, enhancements and training, the CSH was finally ready for review again. Zimmerman and Barclay once more presented the CSH to the same Starfleet review board, who were a lot happier with the CSH's personality and general overview. The board still had a number of reservations about the security issues it may pose, giving a Hologram that much control of any Starfleet installation was dangerous. Again, Zimmerman reminded the board of all the safety precautions that he had already built into the CSH but they remained unconvinced.

There was some back and forth discussions between the board and Zimmerman, before Barclay stepped in with a solution. After a brief, and slightly uncomfortable silence, Barclay suggested that more countermeasures could be built into the CSH's program, a series of back door codes that could disable part or all of its program, those codes could be secured on a non-networked and shielded device that the CSH couldn't access, so it could never adapt its program to compensate for those codes. This helped ease the board's concerns a little, but then Captain Maddox asked what would happen if the CSH did gain control of a ship, how could it be stopped? Stepping in, Zimmerman said that he could develop a virus program that would be able to remove all traces of the CSH from a computer, deleting it and any backups that it had. With those security measures approved, the board agreed to allow the CSH to go into field testing.

The next major task was selecting a ship to test the CSH on, Zimmerman wanted to test it on a frontier vessel, though Starfleet preferred to test it closer to home, and this was one argument Zimmerman wasn’t going to win.

(There is a lot more to come on this front, I am not done yet)

Service Record

Service History These are mostly just my notes and key dates to refer back to

2371 - The Doctor is created
2373 - 2375 - Dominion war
2373 - Long Term Medical Hologram project started but later scrapped due to Bashir's genetic engineering history
2374 - Voyager discovers coms relay network, Doctor goes to Prometheus Mk 2 EMH
2375 - Zimmerman researches Vic Fontaine's program - Mk 3 active during the war but retired after
2376 - Zimmerman terminally ill, Doctor sent back to help cure him
2376 - CSH program restarted
2377 - Voyager returns home
2377 - EMH mk 4 active
2378 - CSH presented to Starfleet. Starfleet wasn't impressed with Zimmerman's subterfuge and keeping the project secret. While they did admit the CSH could be useful, it would need improvement, especially in the personality subroutines.
2380 - Zimmerman represents the CSH for review with new updates, after some debate, it was officially approved for further development and testing
2380 - ESH developed and USS Galen project started - EMH mk 9 active
2381 - Galen launched with ESH, EEH and various others

Awards

Awards