SEDSAT-2 Team Handbook

From SEDSWiki

If you have any questions, please add them to the discussion page. Questions are certainly encouraged -- we want you to understand how to participate on the team.

Contents 1 New Members 1.1 Important Registrations 2 Roles 2.1 Subsystems 2.2 Positions 2.2.1 Core Committee 2.2.2 Subsystem Lead 2.2.3 Team Members 2.2.4 Mentors 2.2.5 Advisers 3 Tools 3.1 ProtoForge 3.2 SEDSWiki 3.3 SEDS Blogs 3.4 Google Calendar 4 Policies 4.1 On the Use of Protoforge and Wiki 5 File storage 6 Page-naming conventions 6.1 Creating a new page 6.2 Subsystem design notes. 6.3 SEDSAT-2 team meeting notes. 6.4 Subsystem meeting notes. 7 Advisers 7.1 Adding New Members

New Members

Important Registrations

1. Join the team e-mail list. All team communications occur here.
   • Join the SEDSAT-2 news list.
   • Optional: Join the SEDS-Earth email list. SEDSAT-2 is a project of SEDS-Earth, the international chapter of SEDS.
2. Register an account at SEDSWiki. This is the location of our documentation: SEDSAT-2 wiki site.
3. Register an account at ProtoForge. This is where we manage the system requirements and make decisions. Once you have registered for an account on protoforge, you need to join the SEDSAT-2 project. To do this, log in to protoforge and click on "Projects" (in the menu on the left", then click on "SEDSAT-2" in the main part of the page, then click on "Membership" in the blue bar at the top of the page, and finally click "Request membership" at the top right of the membership page, immediately below the blue protoforge-navigation bar. Fill in the membership request and submit it.
4. Register an account on the SEDSAT-2 SVN.
5. Register an account at SEDS Blogs. After creating an account, email Kirk (kittell@seds.org) so that he can give you permission to be an author on the SEDSAT-2 blog. This is where we communicate with the public.

Roles

Subsystems

Ground

• Develop scheme for communicating with satellite (work with communications subsystem)
• Develop scheme for coordinating ground stations via public outreach
• Ground processing of received data
• Develop SEDSAT-2 Google Earth Project for displaying satellite images and other information, such as team distribution and location of participating ground stations

Power

• Manage power budget
• Develop method for generation, storing, and distributing electrical power
• Determine hardware needs

Command and Data Handling

• Manage on-board data budget
• Determine hardware and software needs
• Determine what tasks processor is required to handle

Communications

• Manage link budget (between satellite and ground)
• Determine hardware needs
• Determine method of communicating with ground

Structure

• Manage mass budget
• Perform structural analysis of satellite components

Payload

• Select payload concept
• Determine hardware needs

Systems

• Manage requirements

Attitude Determination and Control (provisional)

• Determine pointing requirements
• Determine method of controlling spacecraft
• Determine hardware and software needs

Program

• Manage cost budget
• Acquire launch vehicle

Positions

Core Committee

• The core Committee shall consist of three people.
• The members of the core committee shall remain so until defined milestones have been accomplished in the development of SEDSAT II, in which case other members of development team may be offered the chance play this role.
• Responsible for identifying key milestones in the development of SEDSAT II, and insuring that decisions on these milestones are made efficiently and effectively.
• Responsible for identifying major sticking points in the development process and stimulating their solution.
• Other responsibilities?

Subsystem Lead

• Responsible for all tasks required to complete design and construction of subsystem
• Must work with other subsystem leads to ensure successful integration of subsystems in completed spacecraft. This includes attending the weekly general meetings, or sending a qualified representative (any other subsystem team member well versed with the progress of the subsystem).
• Must manage team members assigned to subsystem
• Responsible for acquiring help from mentors (or delegating this task to team members)
• Responsible for sending weekly updates to the rest of the project team. Instructions on how to do so can be found here: SEDSAT-II Weekly Updates Instructions

Team Members

• Assigned to work on individual tasks to support subsystem completion.

Mentors

• Available to ask for help with design and construction of satellite components

Advisers

• Essentially the same as Mentors, but also aid in the administration of the email list, wiki, and blog.

Tools

ProtoForge

ProtoForge
How to use ProtoForge

SEDSWiki

All of the notes and research done by the teams will be saved on SEDSWiki. Esssentially, SEDSWiki is a notebook in which all of the team members can write.

Why do we use a wiki for managing our information? There are several reasons. First, it is available for free to everyone. Second, it allows us to keep our information in the open so that we can invite experts to view our work (don't worry -- there are administrators that monitor changes to the wiki so that no one vandalizes your work). Third, it allows SEDS to keep the research and design information for future SEDSAT teams (SEDSAT-3, SEDSAT-4, etc.).

SEDSWiki Help

SEDS Blogs

Why do we use a blog? The SEDSAT-2 Blog is the dynamic public face of the team. A frequently updated blog shows to the outside world that the team is active and moving toward a completed satellite. Also, experts will periodically be invited to give "seminars" on the blog to teach us important knowledge for our design.

How to Use SEDS Blogs

Google Calendar

The schedule for SEDSAT-2 is maintained at Google Calendar. All team members should have access to edit this calendar. If you need edit access, email Kirk (kittell@seds.org). Why do we use Google Calendar? It is available for free to everyone everywhere.

Official SEDSAT-2 Calendar

Policies

On the Use of Protoforge and Wiki

As an outline, Protoforge = decision making, discussion and requirements generation (planning, sorta) Wiki = documentation, tracking

So, what does the above mean? You use the Wiki to document the project - the Mission Feasibility Study and all such similar studies go in there. You can also load it up with links of the documents that you think will be necessary during the course of the design period. Like the two documents relating to our registration with the CubeSat community like the CubeSat Design Specifications. Kirk has introduced the concept of using the "Things to Do" in the user pages of the Wiki which is a great way to track what people are doing and make sure that there aren't two people working to get the same information.

You use Protoforge as a way to make decisions, discuss ideas and then have a way to check out your reasoning when you're designing. What Protoforge basically does is help to keep the project expand properly from basic needs of the satellite to the more specific aspects of the satellite and does it in a way that helps you to "cover all your bases".

File storage

.gif, .jpg, .txt, .pdf, and .png files will be stored on ProtoForge. .png files will be used for charts. .jpg files will be used for photographs.

Spreadsheets and word processor documents will be stored on Google Docs & Spreadsheets. Documents will be written on SEDSWiki. After the final revision on SEDSWiki, documents will be moved to Google Docs & Spreadsheets for formatting. Kirk has software to convert files to PDF.

Page-naming conventions

Creating a new page

There are two ways to create a new page.

1. Create a link on an existing page. On the edit page of an existing page, type the wiki link to the page you wish to create. Even though the page does not exist, SEDSWiki will create the link. If you If want to create a page called Last Man on the Moon type this in the edit page:

[[Last Man on the Moon]]

2. Type the URL of the new page. In the address bar of your browser, type the URL of the page you wish to create. If want to create a page called Last Man on the Moon type this in the address bar (don't forget the underscore between words):

http://wiki.seds.org/index.php/Last_Man_on_the_Moon

Subsystem design notes.

Think of design notes like pages in a subsystem lab notebook. When you make notes about design ideas -- links, references, drawings, random thoughts -- enter them on a new page in your notebook using this page-naming convention:

SEDSAT-2_(Subsystem)_Design_Notes_(Date)  --->  SEDSAT-2_Power_Design_Notes_20061217

Include the tag [[Category:SEDSAT-2_(subsystem)]] on the notes page to organize the page in your subsystem category. For example, including [[Category:SEDSAT-2_Power]] on a page will organize the page here: Category:SEDSAT-2 Power.

SEDSAT-2 team meeting notes.

Team meetings involve all members of the SEDSAT-2 team. Information from meetings will be saved in two forms: Notes and Transcipts. Transcripts contain the full text of each chat and Notes contain only the important points of the chat.

SEDSAT-2_Meeting_Notes_(Date)  --->  SEDSAT-2_Meeting_Notes_20061217
SEDSAT-2_Meeting_Transcript_(Date)  --->  SEDSAT-2_Meeting_Transcript_20061217

Include the tag [[Category:SEDSAT-2_Meetings]] to organize the pages in the meeting notes category.

Subsystem meeting notes.

Subsystem meetings involve only a single subsystem team. Information from meetings will be saved in two forms: Notes and Transcipts. Transcripts contain the full text of each chat and Notes contain only the important points of the chat.

SEDSAT-2_(Subsystem)_Meeting_Notes_(Date)  --->  SEDSAT-2_Structure_Transcript_20061217
SEDSAT-2_(Subsystem)_Meeting_Transcript_(Date)  --->  SEDSAT-2_Structure_Meeting_Transcript_20061217

Include the tag [[Category:SEDSAT-2_Meetings]] and [[Category:SEDSAT-2_(subsystem)]] to organize the pages in the meeting notes and particular subsystem categories.

Advisers

Adding New Members

1. Respond to application email
   • Give link to Handbook page for important registrations
2. Add member to sedsat2 and sedsat2-announce email lists
3. Add member to calendar list
4. Add member to blog list (after he/she creates username)