|
| |
|
Commanding Officer: Senior Captain Kristinia
|
| I. PREAMBLE |
The Department of Engineering (hereinafter referred to as
'Engineering') is formed by Article VI of the Constitution of
FEDERATION COMMAND with the purpose of maintaining the web site,
forums, signatures, and any other graphics of FEDERATION COMMAND. This
Charter is designed to outline the role and structure of Engineering
policies and procedures as lawfully promulgated.
|
| II. COMMAND |
Engineering will be commanded by a Chief Engineer (CE) and a Deputy
Chief Engineer (DCE) whom will assume the positions of Commanding
Officer and Executive Officer respectively.
|
| III. ROLE |
Engineering under the direction higher of authority will be responsible
for repairs, upgrades, installs, fabrication and general up keep of the
Federation Command web-site, forums, Team Speak and graphical needs of
Federation Command. Additionally Engineering will be responsible for
researching new technologies for the above mentioned Federation Command
Assets to include new designs and method to maintain our superiority in
the field of Graphics. Engineering will ensure Federation Command meets
a cutting edge in web, forums, Team Speak, and graphical presence in
the Star Trek community.
|
| IV. STRUCTURE |
The structure of Engineering, including any sub-departments, is at the
discretion of Engineering Command..
|
| V. MEMBERSHIP |
Any Officer of FEDERATION COMMAND at or above the rank of Ensign may be
accepted into Engineering. Engineering Command has the responsibility
to conduct admissions and training as deemed appropriate.
|
| VI. SITE ACCESS
|
Engineering Command via FEDCOMMAND.ORG/Engineering will furnish,
monitor and maintain FTP access and other administrative access to the
above mentioned assets. At the discretion of the Engineering Command CO
access will be granted and removed as needed for all engineers .
Additionally engineers granted FTP access shall not abuse or misuse
said access. Engineering Officers are not to store personal data such
as graphics, or documents on the FTP. No executable files, patches,
scripts or games will be uploaded to the FTP. Only PSDs, PNGs, HTML
files, or other approved files may be uploaded as directed by
Engineering Command.
|
| VII. SIGNATURES
|
Signatures are recommended to consist of but not limited to the
following:
1. NAME
2. FLEET/SQUADRON
3. DUTY 1
4. DUTY 2
5. DUTY 3 OR RANK
6. FEDERATION COMMAND logo
7. STAR TREK RELATED IMAGERY ONLY
Officers of FEDERATION COMMAND may develop their own signatures without
the use of FEDERATION COMMAND copyrighted material, however, any use of
such material must be approved by Engineering Command. Only one
signature and one awards case will be allowed per person. An awards
case may accompany a signature. Signature requests must be made in the
proper forum and follow the workflow process as written by policy..
|
| VIII. ROLES AND POWERS
|
CHIEF ENGINEER
1. Power to hire and fire Engineering Officers;
2. Power to access to all designs and templates;
3. Power to pre-approve new designs and templates; however, final
approval must be voted by the Council of Admirals.
4. Power to assign work to Engineering Officers;
5. Ensuring the quality of graphics. (This will of course stop any sub
par graphics outside of a council vote. (ie, non major graphics, like
logos etc)
6. Power to access administrative resources As directed by higher
authority.
DEPUTY CHIEF ENGINEER
1. Power to hire and fire Engineering Officers;
2. Power to access to all designs and templates;
3. Power to assign work to Engineering Officers;
4. Ensuring the quality of graphics.
5 Power to access resources as directed in writing by the CO of
Engineering.
ENGINEERING OFFICER
1. Power to access resources as directed in writing by the CO of
Engineering based on position within engineering department.
|
| X. POLICY
|
Ratified by the Council of Admirals on 29th July 2011.
|
| ROSTER |
|
