Spacecraft Systems Intern

Task Objective: In this task you are required to plan your work as a Spacecraft Systems Intern by studying mission analysis in depth. Your focus should be on understanding what the role actually involves, what standards and practices apply, and how a professional would approach the problem before any hands-on work begins. Expected Deliverables: Submit a planning document (PDF or Word file) covering your research on mission analysis, the scope of the problem you intend to work on, the standards or references you will follow, and a week-by-week plan for the rest of this internship. Include a diagram or table summarising your approach. Key Steps: 1. Research how professionals handle mission analysis and note the accepted methods and standards. 2. Define the scope of the problem you will work on, with clear assumptions and constraints. 3. List the references, tools or software you will use and explain why each was chosen. 4. Prepare a diagram or table that summarises your plan for the coming weeks. Evaluation Criteria: Your submission will be assessed on depth of research, clarity of scope, sensible choice of methods and references, and the quality of your written plan. Your file should be professionally formatted, written in your own words, and detailed enough that another engineer could follow and repeat your work.

Task Objective: In this task you are required to carry out the subsystem breakdown work for your chosen problem. The focus this week is on doing rather than planning: apply the methods you identified in Week 1 and produce real working output, showing every calculation, model or step you took. Expected Deliverables: Submit a working document (PDF or Word file) containing your complete subsystem breakdown work — calculations, drawings, models, screenshots or data as appropriate. Every result must be traceable: show the inputs you used, the method you applied and the output you obtained. Key Steps: 1. Set up your tools, data or model for the subsystem breakdown work. 2. Perform the work step by step, recording inputs, methods and intermediate results. 3. Include drawings, screenshots, plots or tables that evidence what you produced. 4. Note any assumption you had to make and explain why it is reasonable. Evaluation Criteria: Your submission will be assessed on correctness of your method, completeness of the working, quality of the evidence you provide, and how clearly another engineer could follow your steps. Your file should be professionally formatted, written in your own words, and detailed enough that another engineer could follow and repeat your work.

Task Objective: In this task you are required to analyse and validate what you produced last week, using budget allocation. The focus is on checking your own work: verifying that results are sensible, comparing them against references or expected values, and identifying where your approach could fail. Expected Deliverables: Submit an analysis document (PDF or Word file) presenting your budget allocation, a comparison of your results against published data or expected values, a discussion of the errors and uncertainties involved, and the changes you made after checking your work. Key Steps: 1. Carry out the budget allocation on the output from Week 2. 2. Compare your results with published data, standards or an independent calculation. 3. Identify sources of error and explain how much they affect your conclusions. 4. Revise your work where the analysis shows it is needed, and record what changed. Evaluation Criteria: Your submission will be assessed on rigour of your analysis, honesty about limitations, quality of the comparison you make, and the improvements you identify. Your file should be professionally formatted, written in your own words, and detailed enough that another engineer could follow and repeat your work.

Task Objective: In this task you are required to bring the whole internship together into a professional architecture pack. The focus is on communication: presenting your work the way it would be presented to a design review board or a client, with conclusions an engineer could act on. Expected Deliverables: Submit a complete architecture pack (PDF or Word file) covering the problem, your method, your results, your analysis and your conclusions, with a short executive summary at the front. Include a presentation (slides or a recorded walkthrough) summarising the work in under ten minutes. Key Steps: 1. Write an executive summary that states the problem, your approach and your main findings. 2. Bring together the work from Weeks 1 to 3 into one structured, professionally formatted document. 3. State clear conclusions and recommendations that follow from your results. 4. Prepare a short presentation summarising the project for a technical audience. Evaluation Criteria: Your submission will be assessed on completeness of the report, strength of your conclusions, professional presentation and formatting, and how well the work would stand up in a real design review. Your file should be professionally formatted, written in your own words, and detailed enough that another engineer could follow and repeat your work.