JOB DESCRIPTION
26/5/14 05:16The communications officer is in charge of sending and receiving all messages, whether inter or intra-ship. They observe and maintain the ship's network, monitors activity, and relays comms to specific officers; they also report whether signals have been lost or muddled, and essentially make sure that all relevant lines of communication are open and functioning properly. -- Tranquility job description
What is Comms responsible for?
Someone in Comms is usually always monitoring the network. That's their job. Presently - with no communication with the outside world - that only means maintaining the internal comms based network. However, external communications are now in progress. They monitor activity (i.e. listen on everything everyone is doing); facilitate the delivery of messages to the right departments (i.e. making sure doctors get to medical emergencies); and keep an eye out for strange activities, broken messages, hidden codes--basically anything dodgy going on with the network itself.
As an extension of this, they are now moving into providing a base of operations for tracking everyone on board using comms signals, sourcing that information out to the relevant departments, archiving all information past and present on the network, and setting up programs that are designed to recognise specific words, whether they be spoken or written, and flag them accordingly.
Comms, as a result of handling all the information on board, usually employs people who are naturally cautious or good with computers, and their security measures are quite high; they are, after all, poking their nose into other people's privacy more often than not--but it's for the good of the ship, they swear! More important is making sure that information stays soundly behind their doors, as being very private, paranoid people themselves, they're understandably prudent about what they do with other people's secrets.
So you just signed up for Comms...
First of all thanks for coming, you'll fit in well here, probably even if you're doing something shady, so long as that shadiness doesn't get in the way of your work. The Comms department are a close knit group of incredibly private individuals, and although initially suspicious of newcomers, tend to open up to people who are like themselves quickly enough.
Your first week or two of working in Comms will be spent on the top level on the limited access terminal. Remember, it's a department of ex-hackers, meaning if you come in trying to cause trouble or rake the system for data, you'll be in all kinds of trouble. You'll start off working - unless given special provisions to do otherwise - listening to the public network and reporting anything that seems odd, suspicious or dangerous, and archiving those recordings accordingly.
After that, welcome to the team. You'll be expected to at least work with people 'on-line', which is within the comms network, expected to keep private information private, and be able to dedicate extra time to the department in times of emergency. Oh, and you'll need to make a certain amount of coffee yourself, too. There's no need to prove your work, nobody's going to punish you for pursuing your own projects--you'll be taken at your word.
Most of the time.
-- Nathan Petrelli
What is Comms responsible for?
Someone in Comms is usually always monitoring the network. That's their job. Presently - with no communication with the outside world - that only means maintaining the internal comms based network. However, external communications are now in progress. They monitor activity (i.e. listen on everything everyone is doing); facilitate the delivery of messages to the right departments (i.e. making sure doctors get to medical emergencies); and keep an eye out for strange activities, broken messages, hidden codes--basically anything dodgy going on with the network itself.
As an extension of this, they are now moving into providing a base of operations for tracking everyone on board using comms signals, sourcing that information out to the relevant departments, archiving all information past and present on the network, and setting up programs that are designed to recognise specific words, whether they be spoken or written, and flag them accordingly.
Comms, as a result of handling all the information on board, usually employs people who are naturally cautious or good with computers, and their security measures are quite high; they are, after all, poking their nose into other people's privacy more often than not--but it's for the good of the ship, they swear! More important is making sure that information stays soundly behind their doors, as being very private, paranoid people themselves, they're understandably prudent about what they do with other people's secrets.
So you just signed up for Comms...
First of all thanks for coming, you'll fit in well here, probably even if you're doing something shady, so long as that shadiness doesn't get in the way of your work. The Comms department are a close knit group of incredibly private individuals, and although initially suspicious of newcomers, tend to open up to people who are like themselves quickly enough.
Your first week or two of working in Comms will be spent on the top level on the limited access terminal. Remember, it's a department of ex-hackers, meaning if you come in trying to cause trouble or rake the system for data, you'll be in all kinds of trouble. You'll start off working - unless given special provisions to do otherwise - listening to the public network and reporting anything that seems odd, suspicious or dangerous, and archiving those recordings accordingly.
After that, welcome to the team. You'll be expected to at least work with people 'on-line', which is within the comms network, expected to keep private information private, and be able to dedicate extra time to the department in times of emergency. Oh, and you'll need to make a certain amount of coffee yourself, too. There's no need to prove your work, nobody's going to punish you for pursuing your own projects--you'll be taken at your word.
Most of the time.
-- Nathan Petrelli
Tags: