P18571: Sunspot Radio Telescope III

Planning & Execution

Table of Contents

Team Setup


Contact List

Team Values

Each team member will be prompt and arrive at the team meetings on time. If an unexpected conflict comes up, the absent team member will notify all affected teammates with reasonable notice. An absent team-member should confirm that a team-mate has received their message (in person, voice mail, email, etc).
Team members should review their prior commitments with the rest of the team in order to resolve priority conflicts.
Proactive and Prepared
Before working with the rest of the team, be aware of all relevant information regarding the tasks to be completed. Complete any prerequisite work before the meeting. Challenge and motivate teammates to do likewise.
Each team member will complete their tasks thoroughly and completely, so that the work does not have to be re-done by a peer on the team. If a member does not know how to complete a task, feels overwhelmed, or needs assistance then the member notifies peers, and seeks assistance either from a peer, the faculty guide, a faculty consultant, or another person.
Each team member completes their work accurately and in a way that can be easily checked for accuracy by peers and the faculty guide. All work is fully documented and easy to follow. Document everything, including SVN and EDGE versioning in both comment text and version table.
Always have a positive attitude toward other team members. Consider others’ viewpoints, answer questions team members may have, and constructively criticize if needed. No talking behind other backs, transparency and calm conflict resolution is the standard
Professional and Ethical
Each team member gives credit where credit is due. All work completed includes citations to appropriate literature, or sources of assistance. If a team member has gotten assistance from a publication or individual, then that assistance or guidance is fully documented in the reports prepared. Each team member is honest and trustworthy in their dealings with their peers.

Team Norms

Value Unsatisfactory Needs Improvement Meets Expectations Exceeds Expectations
Punctual The team member has had one or more unexcused absences or tardy arrivals to a scheduled team activity. The team member is not notifying others of conflicts with meeting times, or has allowed other committments to impede the member's duties to this team. The team member is detracting from the performance of the entire team. The team member has had one or more unexcused absences or tardy arrivals. The individual could and should have done a better job at notifying (in advance) a peer of the absence or tradiness. At the current time, the problem has not caused significant harm to the team, but this behavior needs to improve. It is not unusual for a team member to receive this rating a couple of times during the project. The team member was prompt and present at every team event this week, or any absences were excused in advance. If there was an unexcused absence or tardiness, then the team-mates agreed that the reason disclosed after the fact was indeed unavoidable. For example, a member is in a fender bender on the way to campus, and was unable to contact a team-mate about being late. The absent member caught up with a peer as soon as practical, and informed them of the problem. Not only is the team member always prompt and present, but the member clearly plans ahead for excused absences (such as job trips) and insures that the absence will not adversely affect the team's performance. The member notifies the team of heavy loads and external conflicts (such as exams in other classes) that COULD have an adverse impact on the team, and works with the peers on this team to make sure that the information flow from the member to and from the peers is smooth even in such cases.
Committed The team member is a burden to the rest of the team The team member is carrying less than their fair share of the work load. The team member is carrying their fair share of the workload. The team member is carrying more than their fair share of the workload.
Proactive and Prepared Team member is unprepared for meetings or activities and fails to complete expected work independently. Team member may be familiar with material for team meetings or activities, but is only minimally prepared or has not fully completed their independent work. Team member is prepared for meetings and activities and completes independent work before the team needs it. Team member is prepared for meetings and activities, and in addition to having completed all independent work, has already considered steps for future work and facilitating other team members.
Thorough The team member has not completed the task assigned, or has submitted a response that is clearly insufficient. The work will need to be re-done by another team member in order for the team to move forward. Some of the work may have been done, but it was incomplete. The team member is detracting from the performance of the entire team. The team member made some progress towards the task assigned, but not as much progress as should have been accomplished. The work may be done, but the other team member's have no way of checking the results, because the supporting documentation is incomplete. The team member is getting behind on the tasks that need to be completed. The team member needs to make up the missed work during the next evaluation period. The team member has made solid progress towards the task assigned. The task is complete, and is well done, though it may need some additional work and refinement to be fully complete. The assignment may be incomplete, but the team member has clearly made a good effort towards getting the task done. In retrospect, this task may have been too much for the member to do in the time allocated, so the fact that the task is not done yet is not due to lack of effort by the member. The task has been completed fully, and is in essentially finished form. The other team members can readily check the work submitted since the documentation is so clear. Not only is the work done, but everyone on the team recognizes that the task is complete with little or no need for additional effort.
Accurate The work completed by the team member is unacceptable and does not meet the basic standards of engineering work. Engineering principles were not applied, or were grossly mis-applied. Basic elements of the engineering task were overlooked. The work completed must be re-done completely. The work completed by the member contains many errors that must be corrected. While the basic approach to problem solving may be ok, the actual work completed needs to be largely re-done in order to be useful to the team. Some things were not done by the team member, that should have been obvious to complete. The work was corrected through consultation with the team members or faculty guide. The team member completed the task with virtually no errors or omissions. The work was accurate, and can be easily scaled to other applications or tasks that the team may encounter.
Respectful Team member does not respect other team members, the customer, or the MSD staff. Team member generally respects other team members, the customer, and the MSD staff, but occasionally expresses a negative, disrespectful or counterproductive attitude. Team member respects other team members, the customer, and the MSD staff. Team member respects other team members, the customer, and the MSD staff, and makes an effort to please all aforementioned parties.
Professional and Ethical The team member has committed plagiarism, falsified data, ignored their responsibility as an engineer. The team member may have behaved inappropriately at a team event, or in a manner that reflects adversely on the team. The members' actions may cause the entire team to fail. The team member has overlooked some references or consistently fails to cite sources and conduct individual tasks. The team member may have made some off-color remarks or been offensive to a team-mate or other individual. The team member needs to clean up his/her act. The team member behaves responsibly and fully documents sources and collaborators on all work. The team member is a role model for others, and behaves in a professional and ethical fashion even under very trying and difficult circumstances.

Project Plans & Schedules

A preliminary project plan is presented in this simplified Gantt chart. Individual tasks are not yet broken down.
Preliminary Project Plan

Preliminary Project Plan

Risk Assessment and Growth Curves

ID Category Risk Item Effect Cause Likelihood Severity Importance Action to Minimize Risk Owner
R1 Technical Improper feedhorn installation Feedhorn may have loose mounting or be unable to be assembled. Manufacturing Faults 1 3 3 "Use proper machining procedures" ME
R2 Technical Unreliable internet connection to Zurich May not be able to transmit all data overnight. Environmental conditions including thunderstorms. 3 1 3 "Provide data backup until Zurich server confirms reception" CE
R3 Technical Dish may be too heavy for motors/actuators Tracking functionality is lost, manual repairs required Ice buildup, power depletion, errors in measurements 2 2 4 "Provide flags and warnings to warn users of imminent disruption" CE
R4 Technical File transfer system error Zurich server receives incomplete data Power lost or connectivity issues. 1 2 2 "Provide data backup until Zurich server confirms reception" CE
R5 Technical Auto-calibration error Incorrect data analysis, manual repairs required Drift of control systems over time 2 3 6 "Provide recurring updates to autonomous calibration results" CE
R6 Technical TeamViewer software error Remote operation made difficult or impossible Incorrect data structures and / or program speed 3 1 3 Use cross-platform coding techniques CE
R7 Technical UPS battery dies System loses power and is no longer operational. Mains power is lost and UPS battery is exhausted. 1 2 2 Put system into safe shutdown state before battery is exhausted EE
R8 Technical RadioEyes/LabView incompatibility Additional time required for integration solution Incorrect data structures and / or program speed 1 2 2 Use cross-platform coding techniques CE
R9 Technical Feedhorn selection may carry unexpected collaterals (integration) RX levels may become inefficient for extraction from raw signal Mismatching impedance and frequency response 2 2 4 Perform extensive testing on feed/dish assembly EE
R10 Technical eCALLISTO software error Data may be corrupted or incorrect; Zurich may not recieve data at all Improper program setup / unforeseen program error 1 2 2 "Perform extensive software testing and provide data backup" CE
R11 Technical Interference between subsystems May cause errors or discrepencies in subsystem operation Improper magnetic shielding on power lines near vulnerable systems 1 2 2 "Isolate magnetic interference, or place wiring more carefully" EE
R12 Technical Improper power management One or more subsystems failing due to internal power loss Power delivery components insufficient to meet power needs 1 3 3 Perform extensive power system simulations EE
R13 Technical Internal subsystem overheating Damage to one or more subsystems Inadequate cooling systems or lack of temperature sensor 2 3 6 Run worst-case scenario models, consider cooling solution ME
R14 Technical UPS overheat Damage to battery system Temperature sensitive battery in harsh enviornment 2 3 6 Attempt to install UPS inside observatory building ME
R15 Resource Scarcity of integration and/or testing facilities Project receives unexpected delays waiting for facilities Primary facilities are 1 hour away. 2 1 2 "Establish carpools and overlap schedules to ensure effective use of lab" All
R16 Resource Insufficient budget to meet all project requirements May need to take performance hits to accomodate cheaper budget Limited funds (~$500) 3 1 3 "Design and build where possible" All
R17 Resource Destruction of "Suntracker" project hardware Loss of unique designed hardware, project delays Incorrect assumptions about input levels and tolerances 1 3 3 "Implement strict guidelines for interacting with unique hardware" All
R18 Resource Inadequate space to assemble and test Team may not be able to prove that the project works "Necessary space or devices not easily available" 1 3 3 Ensure that proper space or devices are reserved well in advance All
R19 Resource Theft of system components Irreplaceable components may be lost Improper storage of materials 1 3 3 Lock physical project materials in a locker All
R20 Resource Insufficient backup data storage Zurich or ASRAS server may fail to recieve data Insufficient or nonexistant backup data storage 2 2 4 "Ensure that a minimum amount of backup data storage is available" CE
R21 Resource Insufficient manufacturing tools available One or more subsystem additions may not be able to be completed Limited budget and/or resources of RIT or sponsors 1 2 2 "Prioritize subsystems based on accessibility" All
R22 Safety Team member injury during construction Slowed rate of project work while team member recovers "Improper safety measures taken during construction and use" 1 2 2 "Observe proper safety rules during device construction and operation" All
R23 "Environmental/Social" Other unwanted data could be intercepted Zurich server recieves noisy data Improper selection of device reciever frequency 1 2 2 "Observe proper FCC rules and regulations" CE
R24 "Environmental/Social" Transmission of RF data could cause interference Remote operation difficulty, conflict with TV/radio stations Improper selection of device transmittal frequency 1 2 2 "Observe proper FCC rules and regulations" CE
R25 "Environmental/Social" Remote log-in to unit may pose security threat Sensitive data may restrict remote login Malicious actor obtaining password/login information 1 3 3 "Ensure strict security in regard to username/ password information" All

Risk Management

Other Team Resources

Meeting Minutes, Notes, & Actions

A listing of current meeting minutes can be found here.

Project Reviews

Preparation, notes and actions, etc. Refer to Gate Reviews page, as well.

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation