SEDS-Canada



PREFACEDear Students,Welcome to the Canadian Stratospheric Balloon Experiment (CAN-SBX) Design Challenge, Canada’s only national competition for post-secondary students to design and build a small payload to be flown onboard a stratospheric balloon provided by the Canadian Space Agency. The CAN-SBX challenge was conceived to be a real-world opportunity for students to conduct meaningful stratospheric research. As such, it will push your limits as you learn skills not taught in traditional classrooms. Resourcefulness and perseverance are among the many things you will develop throughout this experience, which are always in high demand in the space sector. We hope you will be inspired to apply what you’ve learned to even greater challenges being faced today to responsibly advance humankind’s presence in space. In this handbook, you will find information about the rules and regulations of the competition, deadlines for submissions, and guidelines on how to complete major project milestones. Although this document is intended to be comprehensive, we encourage you to contact the organizers, listed under ‘Important Contacts’, for further details. We look forward to seeing you at the CAN-SBX campaign!— The entire SEDS-Canada teamSEDS-Canada (Students for the Exploration and Development of Space) is a student-run non-profit, federally incorporated since October 2014. We are a member-based organization with hundreds of members all across Canada who partners with many established university student groups.We are dedicated to promoting the development of the Canadian space sector and supporting our fellow students who wish to pursue careers in this industry. To achieve this mandate, we offer students opportunities for professional development. Our strategy includes national competitions such as CAN-RGX and CAN-SBX, an annual conference, and eventually, competitive grants.TABLE OF CONTENTS TOC \h \u \z PETITION OVERVIEW PAGEREF _Toc50978505 \h 11.1.Project Scope PAGEREF _Toc50978506 \h 11.2.Eligibility PAGEREF _Toc50978507 \h 21.petition Timeline PAGEREF _Toc50978508 \h 21.3.1.Selection Process PAGEREF _Toc50978509 \h 21.3.2.Project Milestones PAGEREF _Toc50978510 \h 21.4.Formatting Guidelines for Submission of Documents PAGEREF _Toc50978511 \h 31.5.Team Guidelines and Definitions PAGEREF _Toc50978512 \h 41.6.Funding Expectations PAGEREF _Toc50978513 \h 41.7.Flight Overview & Basic Requirements PAGEREF _Toc50978514 \h 41.7.1.Experiment Enclosure PAGEREF _Toc50978515 \h 61.7.2.Flight Campaign PAGEREF _Toc50978516 \h 61.7.3.Disclaimer PAGEREF _Toc50978517 \h 62.PROJECT PROPOSAL PAGEREF _Toc50978518 \h 72.1.Overview PAGEREF _Toc50978519 \h 72.2.Proposal Guidelines PAGEREF _Toc50978520 \h 72.3.Proposal Review Criteria PAGEREF _Toc50978521 \h 83.KICK-OFF MEETING PAGEREF _Toc50978522 \h 143.1.Procedures for Scheduling Meetings PAGEREF _Toc50978523 \h 143.2.Kick-off Meeting Overview PAGEREF _Toc50978524 \h 144.PROGRESS PRESENTATIONS PAGEREF _Toc50978525 \h 154.1.Overview PAGEREF _Toc50978526 \h 154.2.Presentation Content PAGEREF _Toc50978527 \h 155.PRELIMINARY DESIGN REVIEW (PDR) PAGEREF _Toc50978528 \h 165.1.Overview PAGEREF _Toc50978529 \h 165.2.Presentation PAGEREF _Toc50978530 \h 175.3.Documentation PAGEREF _Toc50978531 \h 185.4.Feedback PAGEREF _Toc50978532 \h 226.CRITICAL DESIGN REVIEW PAGEREF _Toc50978533 \h 246.1.Overview PAGEREF _Toc50978534 \h 246.2.Presentation PAGEREF _Toc50978535 \h 246.3.Documentation PAGEREF _Toc50978536 \h 257.FINAL EDP SUBMISSION PAGEREF _Toc50978537 \h 268.OUTREACH ACTIVITIES REPORT PAGEREF _Toc50978538 \h 278.1.Overview PAGEREF _Toc50978539 \h 278.2.Structure PAGEREF _Toc50978540 \h 278.3.Outreach Activities Record PAGEREF _Toc50978541 \h 279.POST-FLIGHT SURVEY PAGEREF _Toc50978542 \h 2910.DELIVERABLE CHECKLIST PAGEREF _Toc50978543 \h 2911.TEMPLATES PAGEREF _Toc50978544 \h 3011.1.Risk Assessment Tables PAGEREF _Toc50978545 \h 3011.2.Work Breakdown Structure (WBS) PAGEREF _Toc50978546 \h 3011.3.Requirement Verification Compliance Matrix (RVCM) PAGEREF _Toc50978547 \h 3111.4.Mass and Power Budgets PAGEREF _Toc50978548 \h 3411.5.Budget and Funding PAGEREF _Toc50978549 \h 3511.6.Hazard Sheet PAGEREF _Toc50978550 \h 3612.APPENDICES PAGEREF _Toc50978551 \h 3812.1.Physical Health Hazards PAGEREF _Toc50978552 \h 3812.2.Team/Project Checklist PAGEREF _Toc50978553 \h 4012.3.Faculty Endorsement Letter PAGEREF _Toc50978554 \h 41IMPORTANT CONTACTSNOTE: To submit of project milestones (Proposal, PDR, CDR, TEDP), e-mail cansbx@seds.ca1905039515Ilija Hristovski | CAN-SBX Project Manager |ilija.hristovski@seds.ca | (778) 821-1724Ilija holds a Bachelor of Applied Science Degree majoring in Electrical Engineering from the University of British Columbia’s Okanagan campus (UBC). He is currently enrolled in a master’s degree in electrical engineering and is on his way to fast-tracking to his PhD. His current and future research focuses on developing optical structures for efficient and secure free-space optical ground-to-satellite, satellite-to-satellite, and satellite-to-deep-space communication links. As project manager, Ilija oversees all activities pertaining to the CAN-SBX campaign.5715046210James Xie | CAN-SBX Asst. Project Manager |james.xie@seds.ca | (613) 217-8064 James has a Bachelor of Applied Science in Engineering Chemistry from Queen's University. He is now working as an operations consultant for Stroud International in Calgary, specializing in process optimization and project risk analysis. James is interested in astrobiology and has worked on nanosatellites and rovers for the Canadian Satellite Design Challenge and University Rover Challenges. As assistant CAN-SBX project manager, James will be involved with logistics associated with the campaign.5715058275Robert Nagle | CAN-SBX Project Advisor |robert.nagle@seds.ca | (613) 315-7594 Robert holds a bachelor’s degree in Aerospace Engineering from Carleton University with a concentration in Space System Design. Robert is currently a Satellite Communication System Engineer at Honeywell Aerospace, as well as an Executive for the Canadian Space Society, Ottawa Chapter. Robert is also currently pursuing a specialization in RF Engineering through the University of California. As CAN-SBX project advisor Robert aids planning of CAN-SBX.57151295275Kristen Cote | SEDS-Canada Projects Chair |kristen.cote@seds.ca | (780) 233-9335 Kristen holds a B.Sc. (Hons) in Astrophysics from the University of Alberta, an M.Sc in Earth and Space Science from York University, and is currently studying towards her PhD in Physics at the University of Toronto. Having been involved with many life-changing student projects—like the Ex Alta-1 cube satellite—she is excited to further opportunities for student involvement in Canada's space exploration community as the Projects Chair on the SEDS-Canada Board of Directors. As Projects Chair, Kristen oversees all SEDS-Canada projects. Project Advisors/Subject Matter ExpertsSteeve Montminy, Manager, Suborbital Demonstration, Canadian Space AgencyPhilippe Vincent, Payload Integration Officer, Canadian Space AgencyAnnie Rosenzveig, STRATOS Payload Manager, Canadian Space AgencyEmail: annie.rosenzveig@canada.ca (please CC SEDS-Canada on all emails to the CSA)Martin LaFlamme, Engineer, Power Electronics, Canadian Space AgencyABBREVIATIONSCBE — Current Best EstimateCDR — Critical Design Review COTS — Commercial-off-the-ShelfCSA — Canadian Space AgencyEDT — Eastern Daylight TimeEST — Eastern Standard TimeOAR — Outreach Activities ReportPDR — Preliminary Design Review SEDS — Students for the Exploration and Development of Space SME — Subject Matter Expert STEM — Science, Technology, Engineering and MathTBA — To Be AnnouncedTBC — To Be ConfirmedVAC — Volts of Alternating CurrentWBS — Work Breakdown StructureCOMPETITION OVERVIEWProject ScopeThe Canadian Stratospheric Balloon Experiment Design Challenge (CAN-SBX) is a competition for Canadian post-secondary students to design, build, and test a small scientific experiment onboard a high-altitude balloon at up to 30 km in altitude. Post-secondary students from Canadian universities are challenged to submit a proposal of their payload design in accordance with constraints set by the Canadian Space Agency (CSA) and SEDS-Canada. Experiments will be evaluated by the CSA on several criteria including the feasibility of the design, relevance to Canadian stratospheric science, the team’s management and funding structure, and the team’s outreach plan. Any student team from a post-secondary academic institution can submit a proposal for their experiment, and the top teams will have the opportunity to build and launch their experiment. Students will be responsible for overseeing the execution of their experiment. The flight campaign will occur near the CSA headquarters in Saint-Hubert, Quebec. The 2018-2019 flight campaign was held in August in Timmins, Ontario as part of the CSA/CNES STRATOS project.SEDS-Canada and its collaborators developed this initiative to benefit students who are passionate about space exploration by providing access to a platform to perform ground-breaking research in the stratosphere. CAN-SBX provides an opportunity for students to complete a full engineering design cycle from conception to execution and gain transferable professional skills for careers in the Canadian space industry. Student teams will gain project management and risk mitigation skills which are critical for many projects in the space industry. In addition, they will have the opportunity to work with Subject Matter Experts who will coach and mentor them throughout the competition and gain unique experience through operating a mission with the CSA.In previous competitions, teams designed and tested experiments for a CNES gondola as part of the STRATOS partnership between the CSA and CNES. This year, student teams will help the CSA demonstrate its own high-altitude balloon launch capabilities. These launches will be smaller, so students will need to design payloads that are both compact and lightweight. The launch campaign will also involve students in launch operations and payload recovery to provide enough experience to lead balloon launches from their home institutions! Note about the new call for teams: The COVID-19 pandemic has resulted in disruptions to competition and program schedules throughout 2020. The Flight Campaign for the 2019-2020 CAN-SBX competition (CAN-SBX III) has been delayed to July 2021. As a result, SEDS-Canada has opened another application window for interested teams to join the CAN-SBX III competition; up to two additional teams may be selected to join the already selected two teams to launch their payloads to the stratosphere in July 2021. Considering the uncertainties due to the pandemic, we’re including a short checklist to ensure teams applying to CAN-SBX are set up for success and are able to complete their project; you will be required to submit this checklist as part of your proposal. Any questions or concerns regarding COVID-19 related safety precautions can be forwarded to cansbx@seds.ca.The CAN-SBX Student Handbook is a resource detailing the full requirements and expectations of participating students, teams, faculty, and partners. Included is the competition timeline, key information about deliverables, statements on project restraints, and examples of tables and charts that must be submitted throughout development. The Handbook will guide teams through every step of the development cycle, but if any questions arise that are not answered here they should be addressed as soon as possible to cansbx@seds.ca.EligibilityAny undergraduate student enrolled at recognized post-secondary institutions in Canada is eligible to enter this competition. Students are required to provide proof of enrolment at the time of submission of the proposal. Graduate students (i.e. enrolled in Masters, PhD, and Postdoc programs) cannot form a team but may join undergraduate teams. The percentage of graduate students per team must not exceed 34%. At least one member of your team must be/become a member of SEDS-Canada (see seds.ca/join). Teams must obtain a Faculty Advisor and must submit a Faculty Letter of Endorsement at the Proposal stage (see Section REF _Ref30759418 \r \h 1.5 and Appendix REF _Ref50967899 \r \h 12.3).Competition TimelineSelection ProcessStudents must adhere to the following timeline and requirements to qualify for the selection process. All submissions should be emailed to cansbx@seds.ca (unless otherwise noted).Tues., Nov. 17th, 2020, 11:59 p.m. (ET): Submit your ProposalWed., Nov. 25th, 2020: Teams will be notified of their selection and feedback will be provided by SMEsProject MilestonesSome of the following milestones include documents that must be submitted by the selected teams for evaluation by subject matter experts (SMEs) from the CSA. Specific instructions for submitting these documents can be found in their respective sections of this handbook. A checklist of all expected deliverables (once selected for the CAN-SBX competition) can be found in Section REF _Ref30948779 \r \h 9. All submissions should be emailed to cansbx@seds.ca.Mon., Nov. 30th, 2020: Kick-Off meeting with SMEs and selected teamsMon., Jan. 11th, 2021: Meeting with Faculty AdvisorFri., Jan. 15th, 2021, 12 noon (ET): Submit Progress Presentation 1 (PP1)Mon., Jan. 18th, 2021: Progress Meeting via teleconference with SMEsSun., Feb. 28th, 2021, 11:59 p.m. (ET): Submit Preliminary Design Review (PDR)Mon., Mar. 8th, 2021: Present PDR via teleconference to SMEsSun., Mar. 14th, 2021: Submit EDPFri., Mar. 19th, 2021: SMEs give back Feedback SheetThurs., Apr. 1st, 2021: Submit Progress Presentation 2 (PP2)Tues., Apr. 6th, 2021: Progress Meeting via teleconference with SMEsSun., Apr. 11th, 2021: Teams submit Feedback Sheet Sun. Apr. 25th, 2021: Risk assessment and Go/No-Go decision for July 2021 Flight Campaign (due to the unknown nature of COVID-19)Sun., May 9th, 2021, 11:59 p.m. (ET): Submit Critical Design Review (CDR)Mon., May 17th, 2021: Present CDR via teleconference to SMEsSun., May 23rd, 2021: Submit EDP + Feedback SheetMon., Jul. 5th, 2021: Submit final EDP + Feedback SheetJul. 19th-30th, 2021: Flight Campaign period (TENTATIVE, barring weather, Transport Canada approval, COVID-19 safety)Aug. 31st, 2021: Submit your Post-Flight SurveyOct. 2021: Backup Flight Campaign period, if required by Go/No-Go milestone (TENTATIVE, barring student’s availability during the school semester, weather, Transport Canada approval, COVID-19 safety)Formatting Guidelines for Submission of DocumentsThe following guidelines should be followed for all report submissions, including the proposal. PDF file typeSubmitted electronically to cansbx@seds.caSubmit all files using the following file name format: teamname_filename_year.format (ie: UVic_PDR_2020.pdf) Standard 8 ?” x 11” pages1” margins on the top, bottom, and sides12-point Times New Roman fontNumbered pages on the bottom right cornerInclude a cover page (see Section 2.3) Team Guidelines and DefinitionsThere are no constraints for team size however it is recommended that a team be composed of at least 6 students. Teams must enlist at least one faculty member from their primary institution to act as their team’s advisor. The faculty advisor(s) must complete a Faculty Letter of Endorsement (Appendix REF _Ref50967899 \r \h 12.3) to be submitted with the Proposal. Teams may have additional faculty advisors (from the primary or any collaborating institutions) as needed.Primary InstitutionA recognized college or university in Canada where the team leader is enrolled as a student. Collaborating InstitutionsColleges, universities, and high schools that have contributed time and/or resources to the project.Team LeaderThe team leader is responsible for organizing and coordinating the efforts of the entire team for the duration of the project. The team leader must be enrolled at the team’s primary institution. In most cases, the Team Leader also becomes a member of SEDS-Canada.Faculty Advisor(s)The faculty advisor(s) is/are required to attend progress meetings via teleconference. Faculty advisors cannot become SMEs or project reviewers/judges for the competition.Funding ExpectationsFunding for the CAN-SBX project is not guaranteed. Student teams should not expect funding from SEDS-Canada or the CSA and should exhaust all existing routes to fund their experiments (e.g. Student Union grants, University-based travel grants, partnerships with industry specific to their project, crowd-funding campaigns, etc.). All expenses incurred during the development of the experiment, such as building materials and access to tools and facilities, are expected to be covered by the team. Please contact cansbx@seds.ca with any funding concerns (especially if it is prohibitive to your team submitting an application).Flight Overview & Basic Requirements For reviewers to assess the project proposal, hardware must meet the following constraints below:Maximum 3 kg weight limitThe payload must be contained in the volume shown in REF _Ref39853865 \h \* MERGEFORMAT Figure 2: Figure SEQ Figure \* ARABIC 2: Payload volume constraint in yellow. Note that the payload must be clear of the 6 rods on the perimeter.The experimental design must also meet the following flight constraints: Non-pointing: balloon orientation is not controlledNon-insulated: balloon temperature is not controlledFlight may occur during daylight or nighttime (can be specified as a requirement in the proposal)~3-hour flight Up to 30 km altitudeFlight profile: balloon will reach ceiling height and burstCommunication/telemetry is not facilitated by the CSA. Teams are responsible for their own communication system or retrieving data from the payload after landing.Flight launch, tracking, and recovery will be provided by the CSA. There will be opportunities for students to directly participate in all three stages of the flight (details TBD). It is recommended that you overview the CSA’s STRATOS Expandable Balloon Manual which you can find here: EnclosureEnclosures for small-scale high-altitude balloon missions are typically made of high-density Styrofoam, which is easy to manipulate, lightweight, inexpensive, and buoyant. Figure 1 (below) shows example enclosures.Figure 1: Examples of Styrofoam enclosures for high altitude balloon flights.Flight CampaignAlthough the launch of these high-altitude balloons will be facilitated by the CSA, the goal of this year’s CAN-SBX project is to train students such that their teams will be able to launch their own high-altitude balloons in the future. As such, students will have the opportunity to participate in the launch and recovery efforts during this year’s flight campaign. More information on the tasks required for these roles will be specified at a later date.The Flight Campaign will be held near the CSA headquarters in Saint-Hubert, QC.DisclaimerSEDS-Canada is committed to continue organizing and supporting this amazing learning opportunity for future participants. All participants who are selected to take part in the project will be asked: for consent in being featured in photo/video content for the purposes of SEDS-Canada publicity material (can opt-out), for consent to use submitted materials in advertisement campaigns (can opt-out), andto acknowledge the work of SEDS-Canada in the organization of this campaign or include SEDS-Canada as a contributor in any external publicity, social media materials, outreach activities, or the like. These steps will help us advertise our organization and the CAN-RGX program to future participants and potential sponsors, allowing us to continue hosting these amazing experiences. PROJECT PROPOSALOverviewThe project proposal will be judged by a panel of SMEs with experience in the field of stratospheric research using balloons and should be written with this audience in mind. Your document must be limited to 20 pages, including appendices. Proposals are due Monday, December 2nd, 2019 at 11:59 pm (EST). Please read all the requirements to ensure your proposal is reviewed. Remember to follow the formatting guidelines laid out in Section REF _Ref30759827 \r \h 1.4.NOTE: Proposals which do not meet the experimental constraints outlined in Section REF _Ref30759440 \r \h 1.7 will not be reviewed.Along with the proposal, a Faculty Letter of Endorsement (see Appendix REF _Ref50967899 \r \h 12.3), the Team/Project Checklist (see Appendix REF _Ref50967957 \r \h 12.2), and proof of student enrollment for the team must be submitted.Proposal GuidelinesYour project proposal should include the following sections:Cover pageThe cover page should include all the necessary information about your team and project:Project titleTeam nameTeam member names, emails, and academic affiliationDate of submissionTeam logo (optional)Table of contentsList of tables and figuresThis will serve as a directory for figures and tables included in the document. Provide page numbers or refer to the appendix for each item.Executive summaryThe executive summary should provide an overview of all the sections in the proposal in one page or less. It should only include information that can otherwise be found in the body of the proposal:Brief introduction of the projectClearly indicate the need for your experiment to fly to the stratosphere!Experimental design requirements metScientific valueAbbreviated budget and timelineOutline of outreach activities plannedConclusion and expected outcomes Proposal PlanFollowing the marking scheme provided in Section REF _Ref30948845 \r \h 2.3, address all proposal criteria in full sentences, using primary research literature and diagrams when necessary. References should be cited in IEEE style. Diagrams may be included in the body of the text if they are small or in the appendix if they are full-page. All diagrams must include a descriptive legend or caption. Follow the templates provided in Section REF _Ref30759723 \r \h 10 to complete the Risk Assessment Tables for technical and managerial risks, the Work Breakdown Structure, and the Budget and Funding Table.ReferencesFollowing IEEE style, provide a list of references cited in your proposal.Appendix The appendix should be used for full-page diagrams, engineering drawings, and any other documents which are referenced in your proposal. List appendices using capital letters (i.e., Appendix A, B, C, etc.)You must also include the following appendices:Team/Project Checklist (see Section REF _Ref50967957 \r \h 12.2)Faculty Letter of Endorsement (see Section REF _Ref50967899 \r \h 12.3)Proof of EnrollmentInclude proof of enrollment documentation confirming that your team members are enrolled at a recognized Canadian post-secondary institution. Proof of enrollment can be unofficial, as long as it clearly shows name/student ID (examples include: a picture of a student ID card showing the student ID, name, and expiry date; a screenshot of a timetable showing the student ID and name; a financial statement showing the student ID and name).Proposal Review CriteriaEach submitted proposal will be evaluated and scored according to a standardized rubric for the following criteria (weight in brackets):Description of CriteriaMarking SchemeScientific merit (35%)Scientific ObjectivesDescribe the scientific objectives and the expected outcomes of the proposed experiment (e.g., what are your hypotheses and how will you test them?).0 = no objectives provided, or, objectives are inadequately defined, or not aligned with purpose of competition1 = objectives are aligned with purpose of competition2 = the objectives are well aligned with the purpose of the competition and have a high likelihood of delivering on the stated outcomesNoveltyHave similar experiments been conducted in the past? If so, describe how the proposed experiment is different/original. 0 = an experiment with major similarities has been conducted in the past1 = some literature research was conducted2 = in-depth literature research is provided leading to the conclusion that the experiment is novel Relevance of the high altitudeDescribe why the project requires stratospheric altitudes to achieve its scientific objectives. Show that the scientific objectives can be achieved within the flight profile of the balloon.0 = the experiment was not designed for a high-altitude environment1 = reasoning for conducting the experiment in a reduced gravity environment is described but details not elaborated on how the experiment will survive a high-altitude environment2 = the experiment is appropriate for up to a high-altitude environmentBonus: Importance to Canada’s space sectorReferring to the Canadian Space Agency’s 2020-21 Departmental Plan (), describe how the proposed project fits within Canada’s current planned results (referred to as 'Departmental Results' in the document)2 bonus marks will be given for an appropriate and well-described evaluation of the proposal’s relevance to at least one key strategy area (referred to as ‘sub-sub programs’ in the document)Technical description and feasibility (35%)Experimental DesignDescribe how the experiment satisfies each of the CAN-SBX experimental constraints (refer to Section REF _Ref30759854 \r \h 1.7). Use diagrams and/or sketches to illustrate how the experiment satisfies these constraints.Pass/Fail**Only projects satisfying all experimental constraints will be reviewed.Describe what you intend to measure (variables) and the data collection methods involved.0 = proposed variables or data collection methods are inappropriate/inadequate1 = proposed variables and data collection methods are reasonable but lacking in detail2 = proposed variables and data collection methods are achievable and well-describedUsing the templates in Section REF _Ref30943376 \r \h 11.4, complete a table listing component (a) names (b) descriptions, (c) quantities, (d) estimated power budget (in Watts) and estimated mass budget (in Kgs) of all components of the design (e.g., mechanical and electrical parts). Specify if a component has moving parts. Include estimated total power consumption and mass (with and without a 15% margin).0 = a table not provided or inappropriate/ incompatible for high altitude flight1 = table is lacking detail in its description of components or power and mass budgets2 = thorough descriptions of all components are provided and components are appropriateExplain how the stratospheric environment (pressure, vibration, temperature, radiation, etc.) will affect the proposed experiment.0 = no detailed description for any of the variables provided, or the effects of at least one variable is inappropriate/hazardous1 = a description for each variable is provided but lacking details or appropriate assessment2 = a detailed description for each variable is provided and no risks are expectedList all components of your experiment classified as hazards under Canada’s Hazardous Products Act and specify each hazard. Refer to Section REF _Ref30759882 \r \h 11.1.0 = no hazards were specified1 = some hazards are missing or were not specified according to Canada’s Hazardous Products Act and Section REF _Ref30759882 \r \h 11.12 = all hazards were identified and specified according to Canada’s Hazardous Products Act and Section REF _Ref30759882 \r \h 11.1Experimental ProceduresIn a numbered list, describe in-flight procedures required for the proper execution of the experiment. Specify how any moving parts will function throughout these procedures. Include diagrams and/or sketches as needed.0 = descriptions not provided or inappropriate1 = descriptions are incomplete or lacking detail2 = descriptions are well-described for each stage and are appropriate for the balloon’s flight profileResourcesDescribe the specialized facilities or tools/equipment needed and how the team intends to gain access to these to design, build and test the experiment (e.g., CAD software, laboratory facilities, custom-machined parts).0 = the resources needed are inappropriate/inadequate1 = the resources are listed but details not provided2 = the resources are well-defined and achievableTechnical Risk Assessmenta. HumanDescribe risks involved to team members during the building/assembly of the experiment and how these risks will be handled (will team need to be trained to use tools/equipment, etc.). Special attention should be given to risks involving hazardous products. Refer to Template in Section REF _Ref30759983 \r \h 10.1.0 = the risks are not described or inappropriate/avoidable1 = the risks are defined but mitigation strategies are not2 = the risks and mitigation strategies are well-defined and unavoidableDescribe the risks to team members when executing any tasks during pre-launch and post-flight procedures such as experiment setup and retrieval. Provide mitigation strategies to eliminate (or minimize) risks. Refer to Template in Section REF _Ref30759983 \r \h 10.1.0 = the risks are not described or inappropriate/avoidable1 = the risks are defined but mitigation strategies are not2 = the risks are minimal; mitigation strategies are well-defined and unavoidableb. Technical & EnvironmentalDescribe any points of failure for the experiment, such as mechanical malfunctions, leaks, etc.0 = points of failure were not described or are inappropriate for the experimental design1 = points of failure inadequately described2 = all possible points of failure have been described in sufficient detail Describe the safety mechanisms (ex: kill switches) that will be integrated into the experiment (providing technical drawings/diagrams is encouraged) and how they will be initiated.0 = no safety mechanisms included1 = inadequate safety mechanisms or description is lacking detail2 = well-defined, adequate safety mechanisms which are easily initiatedProject Plan (15%)Team Structure and ManagementFollowing the template provided (see Section REF _Ref30759935 \r \h 11.2), create a Work Breakdown Structure with assigned roles and tasks for each team member, including high school students and faculty advisors. You may rearrange or add components to the template to suit your project and team size. 0 = the roles of each member are unclear/poorly defined1 = the roles of each member are defined but lacking detail2 = the roles of each member are defined in detail for each stage of the projectDemonstrate that team members have a variety of backgrounds. Teams should strive to have discipline diversification throughout their teams (i.e. both scientists and engineers)0 = no discipline diversity presented1 = team has some discipline diversity2 = team has a diverse range of disciplinesA team member has been identified as an Outreach Lead in the Work Breakdown Structure. 0 = no Outreach Lead is identified1 = an Outreach Lead is identifiedIf a team member chooses not to continue with the project, describe the protocol for re-organizing the division of labour.0 = no strategies provided1 = a strategy is provided but lacking details2 = a well-defined strategy is describedProject TimelineIn a table, diagram or Gantt chart, present an expected timeline of the project’s development. Include details such as length of time required for building and testing of each sub-system of the experiment, and completion dates of deliverables such as the PDR and CDR.0 = a timeline is not provided 1 = the timeline is inappropriate or lacking details 2 = the timeline is complete and well-defined Describe how the team intends to stay on schedule and provide strategies that would be implemented when the project is behind schedule including the role of each key team member.0 = no plan provided or the plan is insufficient1 = some mitigation strategies but no detailed plan provided2 = details about which team members will lead the scheduling efforts and how each key team member will contribute to staying on schedule were providedBudget and FundingFollowing the template provided (see Section REF _Ref30759965 \r \h 11.5) include all foreseeable expenses for the entire duration of the project including travel and food, purchase and fabrication of equipment/parts, etc. Describe current and future sources of funding including the duration and amount of this funding.0 = budget and funding plan not provided or inappropriate1 = budget and funding plan not elaborated in detail2 = budget and funding plan is achievable and well-describedDescribe the measures the team will take to ensure the project stays within budget and how the team intends to acquire the necessary funds. Explain the role of each key team member.0 = the team has not planned to stay within budget or the plan is insufficient1 = the team has listed some measures for staying within budget but no detailed plan provided2 = the team has provided details about which team members will lead the budgeting efforts and how each key member will contribute to staying within budgetManagerial Risk AssessmentCreate preliminary risk tables based on the template provided (see Section REF _Ref30759983 \r \h 10.1). Evaluate each risk based on its probability and its consequences. Provide brief justifications for your assessments.0 = tables not provided or inappropriate1 = tables are incomplete or lacking detail2 = tables are well-elaborated and the level of detail is sufficient. Risks have been justified based on sound reasoningOutreach (15%)PublicDescribe how the team intends to engage with the public and K-12 students for each stage of the project, including after the campaign.0 = the team has not made an engagement plan or the plan is inappropriate for this project1 = the team has listed some methods for engagement but has not elaborated on details or some aspects of the plan are missing2 = a detailed plan for engagement throughout the duration of the project is providedDescribe a plan for the involvement of high school students in the project.0 = the team has either chosen not to pursue the inclusion of high school students or a plan for recruiting from high schools was not provided1 = the team intends to recruit high school students but a plan to achieve this has not been elaborated in enough detail2 = the team intends to involve high school students in the project, and they have a descriptive plan for the contributions these students will provideAcademicDescribe how this project will benefit the scientific community (publications, seminars, etc.).0 = the team has not provided any information on the project’s impact on the scientific community1 = Benefits are listed but details are not provided2 = the team has elaborated on the project’s impact on the scientific community and given specific examples of how the scientific community will benefit Describe how this project will increase interest and retention of talent in space exploration and development in Canada and how it will inspire and encourage youth to pursue studies in STEM fields.0 = the project will not increase interest and retention of talent or no adequate description was provided1 = the description is lacking detail2 = the project’s rationale for increasing interest and retention of talent is appropriate and well-described.KICK-OFF MEETINGProcedures for Scheduling MeetingsThere will be many meetings throughout the course of the CAN-SBX competition. The procedure for scheduling meetings is as follows: A SEDS-Canada CAN-SBX representative will reach out to the CSA SMEs to inquire about their availability at least two weeks prior to each relevant milestone. Students will then be contacted and expected to pick a time slot within the available dates/times provided by the CSA SMEs. Once a date/time is selected, a meeting invite will be sent to you with instructions on how to join the meeting.The meetings are often conducted using the Cisco WebEx platform—although, occasionally Google Meets is used. Please download the WebEx platform on your computer. To connect to voice within WebEx, click on: “More Options” below the “Connect to Audio” icon. You can select to have the WebEx call you at a number you specify, or you can call either of two phone numbers provided (one is toll-free) and enter the attendee access code listed in the meeting invite instructions to join the meeting.Please connect via phone for audio and DO NOT use your laptop or PC audio, as WebEx has a compatibility issue when some participants are on the phone and others are using pc/laptop microphones.Kick-off Meeting OverviewThe Kick-Off meeting takes place with the selected teams, SEDS-Canada CAN-SBX personnel, and CSA SMEs. The CSA SMEs will present the Payload User Manual & Requirements document during this meeting. This is an excellent opportunity to introduce your team to the campaign and allow you to begin making progress right away!PROGRESS PRESENTATIONS OverviewProgress presentations are a chance to check-in with teams before major milestones and provide an opportunity for feedback, asking questions, raising concerns, and practicing presentation skills. Teams are expected to be professional in their presentations. This is a great chance to receive help and engage with SMEs; we are all here to help you towards a successful design!Slides should be submitted to cansbx@seds.ca as a PDF. Presentations will be kept to a strict 15 minutes, with 25 minutes at the end for questions. The presentations will be held via teleconference with CSA advisors and the SEDS-Canada team using the Cisco Webex platform. Presentation ContentThe presentation and report should summarize the following content, however if a topic is not relevant to the progress meeting for your team, it should be explicitly stated with a rationale.Title slide — Include all team information, and responsibilities of each member Updates — These slides outline any work that has been completed since the last milestone that include (but are not limited to) the following:Design ChangesAssemblyTestingAnalysisFeedback from previous milestones (if applicable)Next Steps — Immediate next steps to reach the next milestone and an updated project timeline.Please include detail on the methodologies used in planned testing or analysis and the goal of that test/analysis as it relates to the CSA design requirementsAny other topics the team wishes to address including questions, concerns, and roadblocksBudget — Update on whether your team is currently on budget, overbudget, or underbudgetOutreach — Update on outreach activities completed by the teamPRELIMINARY DESIGN REVIEW (PDR)OverviewAfter your proposal has been reviewed by the judging panel, you will be notified if you have been approved to continue with the design process. Your team will be required to give a PDR presentation and submit an Experiment Data Package (EDP) required by the CSA containing a technical review of your payload. Deadlines are listed in Section REF _Ref30759440 \r \h 1.7.Alongside Section 1.7, additional requirements and flight data are listed in the CSA’s STRATOS Expandable Balloon Requirements and User Manual. This document contains information about hardware requirements, the flight, and payload documentation requirements. Major hardware constraints are summarized below. It is the responsibility of the teams to read the STRATOS documentation to understand the complete set of requirements. The payload must withstand a vertical downward acceleration of 15G and a lateral acceleration of 7.5G in any direction in the XY plane applied to the payload’s center of mass (REQ-MEC-001) The payload must be able to interface with the gondola provided by the CSA. Mechanical constraints on the interface are shown in Figure 3. The interface must have 6 clearance holes to allow for ease of assembly when integrating the payload with the gondola.The payload must be able to maintain operation throughout the pressure and temperature fluctuations expected over the duration of the flight (see REF _Ref30949118 \h \* MERGEFORMAT Figure 4). Figure 3: Mechanical interface requirements for integration on CSA gondola. Six clearance holes are required.Figure 4: Temperature and pressure profile with increasing altitude. CAN-SBX 2020 payloads expect to reach an altitude of 30 km.The PDR must provide evidence that your experiment will satisfy all design requirements based on preliminary quantitative analyses and hardware specifications. During the presentation, SMEs will provide comments, feedback, and any concerns they may have about your experiment. You will have 10 days to make any necessary revisions to your EDP before submission. Your report must address any issues raised from the feedback received and present updated design specifications. We encourage you to complete both the EDP and the presentation by the presentation deadline, and then make minor changes to the report after the presentation. An unsuccessful or incomplete PDR can lead to project cancellation at the discretion of SMEs. PresentationTeams will be required to provide a 45-minute presentation followed by a 45-minute discussion period to our panel of SMEs and judges via teleconference. The presentation file format is up to you (PDF, PPT, KEY, etc.). Please submit the slides at least three business days before your presentation date to allow time for the SMEs to familiarize themselves with your design. You must convince the SMEs that your experiment is compliant with payload requirements. Be prepared to answer technical questions. Please structure your presentation as follows:Title slide — Include all team information, and responsibilities of each member Introduction — 1-2 slides on the topic of research and the proposed experimentExperiment design and proceduresFull system specifications and diagrams (be sure to point out where you do and do not currently meet CSA’s payload constraints).Requirement compliance and safety (see Section REF _Ref30759754 \r \h 10.3)Present a compliance chart Describe any prototyping and testing done to date, and lessons learnedIdentify all hazards and list appropriate mitigation strategies for eachProvide a plan to achieve compliance for any requirements not yet fully compliant, including test/analysis methodology, referring to the CSA relevant requirementDescribe your plan to execute a full cycle of ground tests prior to submission of the CDR, including test/analysis methodology, and referring to the relevant CSA requirement, hazard mitigation, or a specific payload function.Project managementUpdated timeline showing immediate next steps to reach the CDR milestoneOutreach & fundingUpdate on outreach effortsFunding status – under, on-track, or over-budget based on an updated budget review.Using this presentation structure, teams should be able to cover all parts of the EDP in detail. DocumentationThe EDP will be used for final design approval by the CSA prior to launch, however a preliminary EDP will be required at PDR. The template for the EDP is given in the STRATOS Expandable Balloon Requirements and User Manual and is reproduced below with additions required by SEDS-Canada. At this milestone, some sections of the EDP may contain preliminary information, however the overall design should be representative of the payload’s flight configuration. The EDP should be formatted following the guidelines listed in Section REF _Ref30942008 \r \h 1.4.Your EDP should include the following sections in the order listed below. If a section is not applicable, it should instead contain a justification for why it is not applicable. Teams can add subsections as necessary if they would like to include additional information. Cover PageThe cover page should include the following information about your team and project: project title, team name, team members, date of submission, current document version, and logo (optional).Table of ContentsThe table of contents will include a list of tables and figures, as well as a list of appendices.List of Reference DocumentsReference documents are files where the contents are not included in the EDP. This may include analyses, test procedures, and reports, CAD files, etc. The reference documents list should indicate the document title, release date, and revision.Technical DescriptionMission ObjectivesGive a brief introduction to the background required for your research topic. Your introduction should answer why your proposed experiment is important to the advancement of space exploration, science, and technology. Describe the mission objectives (what questions do you want to answer?) and how your experiment will address them in a ponent Description and FunctionDescribe your experiment components and their functions. Overview the payload at a system and sub-system level. Block diagrams, models and pictures are encouraged.Mass BudgetProvide a mass budget following the template in Section REF _Ref30943376 \r \h \* MERGEFORMAT 10.4. The budget should include electrical cables/harnesses, the mounting interface with attachment hardware (screws, straps, clamps), the payload enclosure, and payload thermal protection (as required). A 20% margin should be included on the total mass, measured mass prior to launch.Centre of MassThe centre of mass should be clearly indicated with a diagram. Mounting InterfaceProvide a CAD model or figure of the mounting interface, along with a description of the attachment hardware. The mechanical constraints on the mounting interface are given in REF _Ref30943596 \h \* MERGEFORMAT Figure 3 and further detailed in the STRATOS Expandable Balloon Requirements and User Manual. Load CasesAnalysis that the payload meets the required accelerations.Thermal Protection Describe the thermal environment which the payload is designed to operate in. Describe the passive or active thermal protection and thermal control system (as required). Electrical DescriptionPower SystemDescribe the power system. Include battery cell type and part number, as well as voltage regulators with their efficiencies.Power BudgetProvide a power budget using the template in Section REF _Ref30943789 \r \h 10.4. The power budget should be broken into sufficient detail to represent the power consumption of separate components. A 20% margin should be included on the total power consumption. Electrical ProtectionDescribe the electrical protection, including over current, over charge, over discharge, external short-circuits, under temperature and over temperature, and any circuit-breaks or emergency shut-off systems.Electrical cable and HarnessingDescribe the interconnection of different systems through cables and harnessing. Include the wire size (AWG) used. Include an interconnection diagram.GroundingDescribe the grounding schema.Internal RF TransmittersList all the frequencies of the transmitters and receivers used by the payload. Verify that the payload does not emit in the wavelengths listed in the STRATOS Expandable Balloon Requirements and User Manual. SafetyIdentification of Hazardous Materials and EquipmentIdentify all hazardous materials and equipment using the following table. A hazard list is given in Section REF _Ref30945600 \r \h 11.1 of this document. For each hazard identified, a Hazard Sheet must be submitted in Appendix B of your EDP. A template of the Hazard Sheet is given in Section REF _Ref30945622 \r \h 10.6 of this document.No.Risk identifiedSerious or CatastrophicDescription of Potential Event(s)Reference1Hazard Sheet #2Safety BarriersDescribe the safety barriers and risk mitigations in the payload design (e.g. a fuse), referring to the relevant hazard identified above.Safety Critical TestsDescribe the safety critical tests, which demonstrate that any hazardous materials or components within the payload can be sustained during the nominal operations and used in the environment, for the duration of the entire flight (e.g. a particular battery tested under vacuum).Safe Handling ProceduresDescribe the procedures to safely handle and manipulate the payload. Include any specialized tools or equipment as necessary. Safe Testing, Calibration and Integration Procedures Describe the procedures to safely test, calibrate and integrate the payload. Safe Recovery ProceduresDescribe the procedures to safely recover the payload after landing. Include any specialized tools or equipment as necessary. Experiment & Project Management (Additional for SEDS-Canada)Experiment Testing Describe any prototypes built to test the experiment, lessons learned, and how those tests have impacted the preliminary design.Each team should complete one full cycle of ground test experiments, as you would in the flight, prior to the CDR. Provide a plan for these tests, including operations procedures and responsibilities, a list of variables to be measured, and outcomes expected. Include technical risk assessment tables with updated estimates of likelihood, impact, and mitigation and contingency plans. Use the templates provided in Section REF _Ref30946484 \r \h 10.1 to list the risks (each with their own risk table) and then asses their impact in the assessment matrix. Describe how the environment differs from that onboard the Gondola and how that will impact the ground test.Briefly describe the data output and the steps to be taken to analyze data and interpret results. Project Management Provide an updated timeline including a detailed plan of activities to reach the CDR, referring to the relevant CSA requirement or payload functional requirement that the activity is performed to meet.Provide an updated budget, including the status of any outstanding funding. State if the team is over-, under-, or at-budget. Identify any obstacles which may affect the budget going forward.Update the Work Breakdown Structure, including new teammates recruited since the proposal. Use the template provided in REF _Ref30946573 \r \h 10.2.ReferencesReference all externally sourced material including manufacturer specification sheets.AppendicesAppendix A: Requirements Verification and Compliance MatrixThe Requirements Verification and Compliance Matrix (found in Section REF _Ref30947866 \r \h 10.3 of this document) should be included here. For each requirement in the matrix, the following information must be filled out by the payload team in the table: Compliance column: compliant, partially compliant, not compliant or not applicable (following the lettering shown in Section REF _Ref30947866 \r \h 10.3)Statement column: explanation for how the payload complies to that requirement, or why the requirement is not applicable Reference column: analysis, test report, etc. that proves compliance to the requirement. There should be a reference to the Analyses and Calculations Appendix or any other section of the document (if needed).Appendix B: Hazard SheetsThe Summary of Hazards table (provided above) and Hazard Sheets (see Section REF _Ref30945622 \r \h 10.6) should be included for each identified hazard. Appendix C: Analyses and CalculationsAnalyses and calculations can be given here which support compliance to requirements. FeedbackYou will be given feedback on many occasions throughout the CAN-SBX competition (e.g., at progress presentations, PDR, CDR, etc.). Please remember that this feedback provides an opportunity for you and others to constructively assess some aspect of your project and then improve it! While verbal feedback is to be expected after every presentation (e.g., progress presentations, PDR, CDR), there is also a Feedback Sheet that will be used to track outstanding items. The Feedback Sheet is typically in the form of an Excel file and is provided by SMEs after your PDR presentation. An example of one row in the Feedback Sheet is provided below. In this scenario, an SME noticed that a secondary OBC was missing from the C&DH (“command and data handling”) section of the mass budget and recommended that the team add the secondary OBC to the mass budget. The team then responded to this question/comment and upon agreement with the CSA SME, this item’s status would be changed from Open to Closed on the Feedback Sheet. No.ReviewerEDP SectionPageDescription of Comment or QuestionRecommended ActionTeam AnswerSTATUSComments1SME Name1.2.5 Mass Budget16Secondary OBC missing from C&DH section of mass budgetAdd secondary OBC to the mass budgetSOBC mass was added to the mass budget and the table updated accordinglyOpen/ClosedAdditional comments provided here CRITICAL DESIGN REVIEWOverviewThe Critical Design Review (CDR) must demonstrate that your experiment design has achieved a sufficient level of maturity to proceed with full-scale manufacturing, integration, and testing on an expandable balloon. The CDR will be presented to SMEs for feedback via a presentation, and then an updated EDP document will be submitted 10 days later. Comments from judges during the CDR presentation must be addressed in this document. It is recommended to complete both the report and the presentation by the deadline, and then only make minor changes to the report after the presentation. The CDR deadlines are given in Section REF _Ref50977781 \r \h 1.3.2.An unsuccessful or incomplete CDR can lead to project cancellation at the discretion of SMEs. PresentationTeams will be required to provide a 45-minute presentation followed by a 45-minute discussion period to our panel of SMEs and judges via teleconference. Teams must submit their CDR slides to cansbx@seds.ca in advance of their scheduled CDR presentation (see Section REF _Ref50977746 \r \h 1.3.2 for the Timeline). You must demonstrate that your design satisfies all requirements with detailed, compelling evidence. You must be prepared to answer technical questions. Please structure the presentation as follows:Title slide — Include all team information and responsibilities of each memberIntroduction — 1 slide on research topic and experimentTechnical Experiment and ProceduresFinal system specifications and diagramsProcedures for both pre-flight (to get the payload ready for flight), flight (if applicable), and recovery operations, along with team responsibilities.Experiment TestingBriefly describe the setup of the final ground test(s) conducted. Describe the results of the test and how they have impacted the final design specified in the CDR report.Safety InformationIdentify all hazards, making sure to highlight any new hazards since PDRWith each hazard list appropriate mitigation strategiesPresent a requirement compliance tableAll requirements are expected to be compliant or partially compliant (with a clear path to compliance) at the CDR stage.Project managementUpdated timeline Outreach & fundingUpdate on outreach efforts Update on funding and any issues with travel to the flight campaign (if applicable)Highlight the most important milestones completed to date and the remaining tasks to accomplish prior to the integration of your experiment with the Gondola.DocumentationThe EDP document submitted post-CDR should be an updated version of the EDP submitted post-PDR, following the same outline as Section REF _Ref30948521 \r \h \* MERGEFORMAT 4.3. At this point, requirements should be compliant or with a path to compliance. All calculations should be included in the Appendix. All tables should be updated. The mass and power budgets should now only have 10% margins. Any new tests done with the payload should be updated in the Experiment & Project Management section. Procedures for pre-flight, flight (if applicable), and recovery operations, along with team responsibilities should now be included in the Experiment & Project Management section as well. Remember to follow the formatting guidelines laid out in Section REF _Ref30759827 \r \h 1.4.If there are any questions with the expectations for an ‘updated EDP’ please email cansbx@seds.ca.FINAL EDP SUBMISSIONThe CSA requires a finalized version of the EDP prior to launch for final approval of the payload. All requirements must be shown as compliant and no further modifications of the payload shall be made upon submission of the final EDP.An unsuccessful or incomplete EDP will lead to project cancellation. There is no page limit, however clear and concise presentation will ensure no content is missed by reviewers. The submission date for the final EDP is listed in Section REF _Ref50977705 \r \h 1.3.2.OUTREACH ACTIVITIES REPORTOverviewPart of this competition involves inspiring the next generation of STEM leaders, educating youth and the public on microgravity research and space exploration and development at large, and communicating your work to peers in your field. Even as students, we are custodians of the scientific world and have a responsibility to nurture the curiosity and fascination with the universe. It is important for the general public to understand why science is important to inform their decisions and support educational programs. The Outreach Activities Report (OAR) must demonstrate that your team has made an impact on students, the public, and your peers through various activities and presentations. We encourage you to pursue a variety of outreach pathways such as interactive demos, school visits, festival exhibits, and academic presentations/posters. At least one activity must relate to your project’s research and experiment.StructureThe OAR should include a title page that clearly lists all team members involved in the planning and delivering of outreach activities, and their specific roles, followed by a list of activity records describing the outreach performed. At the end of the document, please provide an overview detailing your team’s overall impact on each level of audience listed in the record template.If you included high school students during your project, briefly describe the specific roles these students held during the project, work they have completed, and feedback for the project, their involvement, and the CAN-SBX competition. These details will strengthen SEDS-Canada’s funding portfolio to continue supporting STEM education and expand the reach of the CAN-SBX project to high school students. The format of the document should follow the requirements listed in Section REF _Ref30759827 \r \h 1.4.Outreach Activities RecordFor every outreach activity you perform, please fill out an activity record using the formatted table below.ActivitiesLocation(s) of activityDates(s) of activityNames and roles of team members involved in this activity.Were these activities part of a larger event? If so, please provide a name and brief description.Was this activity related to your project? (Y/N)Was this activity included in your Outreach Plan in the Proposal? (Y/N)Audience Educational Level (Circle or Shade all applicable)K-45-89-12Post-SecondaryEducatorOtherSummaryBriefly describe the activities conducted at the event.Briefly describe any feedback received from the audience or organizers.This will help inform our best practices guide for future teamsBriefly describe any challenges faced while planning or executing the activities.This will help inform our best practices guide for future teamsWould you repeat these activities? Please provide additional detail as to why or why not.This will help inform future outreach activities conducted by SEDSPOST-FLIGHT SURVEYThe Post-flight survey will help SEDS-Canada improve the CAN-SBX competition. It includes questions such as:Were your experiment objectives met? Explain why or why not?What results were obtained from the data collected? Was the data expected or unexpected? Explain.What changes would you make to the CAN-SBX competition?The Post-flight survey will become available as a Google Form after the flight campaign and must be submitted by the deadline listed in Section REF _Ref50977596 \r \h 1.3.2. DELIVERABLE CHECKLISTTo ensure on-time submission of all deliverables expected throughout the CAN-SBX competition, the following can be used as a checklist: Progress Presentation 1Preliminary Design Review (PDR) PresentationDraft EDP (after PDR presentation)Feedback Sheet (recurring submission)Progress Presentation 2Critical Design Review (CDR) PresentationUpdated EDP (after CDR presentation)Feedback Sheet (recurring submission)Final EDP ReportOutreach Activities ReportPictures/video for social mediaPost-flight Survey (submitted via a Google Form)TEMPLATESThis section contains templates that each team should use for various parts of the project:Risk Assessment TablesCreate a risk table for each technical risk (TR#), describing what the risk is, its probability and consequence with associated rankings (Low, Medium or High), and a mitigation and contingency plan.List all risks (TR1, MR1, etc.) in the Risk Assessment Matrix (Table 11-2).Table 111: Risk table template.Risk Event – TR1What is the risk?ProbabilityL / M / HDescribe probabilityConsequenceL / M / HDescribe consequenceMitigation PlanDescribe plan to mitigate riskThis may include active methods (ex. detection, feedback, controls), passive methods (ex. deterrence, avoidance, initial planning), or no mitigation.Contingency PlanDescribe plan in case risk occurs Table 112: Risk assessment matrix template.ProbabilityLowMediumHighConsequenceLowMediumUse this matrix to guide the type and rigor of mitigation and contingency plansHighWork Breakdown Structure (WBS)A work breakdown structure (WBS) separates your project into distinct scopes and assigns a person responsible for managing that scope to ensure accountability and identify gaps in personnel. Scopes should be broken into sub-scopes which may have their own managers. Specific activities should be defined in the project timeline within each scope and may have linkages across different groups. In small spacecraft design, scopes are typically defined by timeline (ex. design, manufacturing, testing), discipline (ex. engineering, finances, management), or system (ex. comms, power, payload), with sub-scopes encompassing the other aspects. A WBS may contain multiple layers as needed to organize your project.Modify the template tree outlined below (currently organized by discipline, with engineering split by timeline) to structure your project from start to finish. You can access the template at seds.ca/wbs. Add or remove tasks as needed based on your project and management plan. Assign a number to each member of your team and list their names in the legend. Each task in the WBS should be given a number(s) corresponding to the team members responsible for that task. When accessing the template at seds.ca/wbs, you can edit the WBS using the edit buttons shown in the screenshot below. It will open a new page in draw.io, where you can edit the WBS without modifying the template. Requirement Verification Compliance Matrix (RVCM)The following template lists the CSA design requirements which must be fully verified prior to the final EDP report. A sufficiently comprehensive RVCM should allow any other group to conduct a replicate experiment if all requirements are met. Use the following 3 columns to fill in the RVCM:Compliance Column: C = Compliant, P = Partially Compliant, N = Non-Compliant, N/A = Not applicable. Put an ‘X’ in the column which matches your compliance status.Statement column: explanation for how the payload complies to that requirement, or why the requirement is not applicable Reference column: analysis, test report, etc. that proves compliance to the requirement (reference the Analyses and Calculation section of your EDP or other sections, as required)REQ IDRequirementComplianceJustificationReferenceCPNN/AMEC-001The payload shall be able to withstand a vertical downward G-force of 15G and a lateral G-force of 7.5G in any direction in the XY plane applied to the payload’s center of mass.MEC-010The mass of the payload shall be a maximum of 3 kg, including the mass of the mounting plate, the payload enclosure and any payload thermal protection.MEC-020The payload shall fit within the cylindrical envelope volume with a diameter of 285 mm and height of 524 mm.MEC-030The centre of mass of the payload shall be located within a 25 mm diameter from the coordinate system origin of the gondola.MEC-040The payload mounting interface shall be provided by the payload team and shall be reviewed and approved by CSA prior to the flight campaign.MEC-050All parts shall remain attached to the payload during launch, flight and landing.ELE-001Each payload instrument shall be equipped with a protective system (such as a fuse) to prevent overloading of the circuits.ELE-010The payload’s frequency plan, listing all the frequencies of the transmitters and receivers used by the payload, shall be submitted to CSA before the campaign to check for compatibility with the campaign’s frequency plan.ELE-015The payload must not emit in the following wavebands: 1090 MHz (CSA transponder), TBD MHz (CSA GPS).ELE-020All cables and harnesses shall be rated for a current equal to or greater than that of the protective system (fuse).ELE-025Wire size smaller than AWG 26 shall not be used without CSA approval.ELE-030All cables shall be insulated, protected and secured. ELE-040The connectors of electrical circuits at risk shall be designed in such a way that there is no ambiguity in their connection (mechanical guides, fool proofing devices, etc.). They shall also be protected against any deterioration and include a system for locking the connections in position.SAF-001Payload teams shall identify all hazardous materials and equipment, taking both nominal and non-nominal operation into account.SAF-010Systems at risk shall comply with the most stringent applicable regulations and their compliance must be proven by the submission of a dossier approved by a recognized inspection body.SAF-020The use of any system involving a risk shall be clearly indicated on the equipment concerned, as well as on the outside of the gondola, by labelling stipulated under the most stringent regulations. SAF-030Systems at risk shall include at least two barriers, excluding the control system, on electric circuits that could cause the loss of human lives if opened; at least one barrier on circuits that could cause serious injury or considerable damage if opened.SAF-040Hazardous chemical systems shall have safety features to prevent inadvertent release of any caustic, toxic or reactive chemicals. SAF-050For each hazardous material or component present in the payload, safety testing shall be performed to prove that there is no risk during nominal operations in the flight environment, for the duration of the flight and during landing.Mass and Power BudgetsYour experiment is expected to have more components than the sample budgets below. Please use the following nomenclature: E = Estimated Mass/PowerM0 = Calculated using a 3D solid model or modelling software (SolidEdge, Eagle, etc.)M1 = Taken from a manufacturer spec sheetM2 = Measured (using a scale, voltmeter, ammeter, etc.)Table 113: Mass budget ponentStatusQtyCBE Unit [kg]CBE Total [kg]Mass FractionRemarksStructure and MechanismsSubtotal9.0052%Aluminum StructureM216.006.00Support BracketsM250.201.00Experiment ComponentsSubtotal5.0029%High-Speed CameraM110.501.00Power SystemSubtotal0.855%BatteriesM240.100.409V Power AdaptersM230.050.15Data HandlingSubtotal1.106%Data LoggerM210.500.50ElectronicsSubtotal0.503%Arduino UNOM010.100.10MiscellaneousSubtotal0.805%CablingE10.500.50FastenersM010.300.30TOTAL17.25100%Target Mass20.00-Margin2.7514%Table 114: Power budget ponentStatusPower Consumption [W]QtyExperiment Operational ModeIdleScienceAverage [W]Duty CycleAverage[W]Duty CycleRF ModuleE0.1740.000%0.68100%TabletM110.00110.00100%10.00100%Robotic ManipulatorM220.0010.000%20.00100%MicrocontrollerM15.0025.0050%10.00100%Power Used [W]15.00-40.68-Power Available [W]50-50-Margin [%]70%-19%-Budget and FundingUsing your Work Breakdown Structure as a guide, complete a table listing the costs of each major task of the project. This budget and funding table is not exhaustive and should be modified to suit your needs. Include all current and future sources of funding in order to estimate total available funds and determine the overall project budget. Include as many details as possible.Table 115: Budget and funding table template. Update the Project Tasks column as needed.Estimated Expenses ($CAD)Project ManagementProject TasksLabourMaterialTravelOtherMeetingsSubtotalDesignCAD ModelPrototype Sub-system 1SubtotalDevelopmentCustom-machined partsMaterials and Tools Machine shop trainingSub-system 1SubtotalTestingStructural testsSoftware testsSub-system 1Procedures testsSubtotalFlight CampaignTravel to/from flight campaignMealsExperiment shippingSpare partsData collection and managementData analysisSubtotalOutreachConferencesPublic engagementSubtotalOther CostsOther costsSubtotalSubtotalsSubtotal With +15% MarginTotal (Estimated)Estimated Funding ($CAD)Funding SourcesUniversity/College GrantsGovernment GrantsSubtotalSubtotal with -15% MarginTotal (Estimated)Deficit/Overture (Funding – Costs)Hazard SheetThe following template is taken from the STRATOS Expandable Balloon Requirements and User Manual.HAZARD SHEETa. No (#): XXXb. PAYLOAD:c. PHASE:d. SUBSYSTEM:e. IDENTIFIED HAZARD:f. DATE:g. HAZARD IDENTIFIER:c. CATEGORY: (SHADE CHOICE)CATASTROPHICSERIOUSh. APPLICABLE SAFETY SPECIFICATIONS:j. DESCRIPTION OF HAZARD:k. CAUSES OF HAZARDS:l. CONTROL OF ASSOCIATED RISK:m. SAFETY AUDIT RISK:n. AUDIT STATUS:Name and Signature of the sheet’s authorApprovalAPPENDICESPhysical Health HazardsPlease see Section 6.1 in the STRATOS Expandable Balloon Requirements and User Manual for a list of hazards to be aware of.Physical HazardsHazard ClassGeneral DescriptionFlammable gases?Flammable aerosols?Flammable liquids?Flammable solidsThese four classes cover products that have the ability to ignite (catch fire) easily and the main hazards are fire or explosion.Oxidizing gases?Oxidizing liquids?Oxidizing solidsThese three classes cover oxidizers, which may cause or intensify a fire or cause a fire or explosion.Gases under pressureThis class includes compressed gases, liquefied gases, dissolved gases and refrigerated liquefied pressed gases, liquefied gases and dissolved gases are hazardous because of the high pressure inside the cylinder or container. The cylinder or container may explode if heated. Refrigerated liquefied gases are very cold and can cause severe cold (cryogenic) burns or injury.Self-reactive substances and mixturesThese products may react on their own to cause a fire or explosion or may cause a fire or explosion if heated.Pyrophoric liquids?Pyrophoric solids?Pyrophoric gasesThese products can catch fire very quickly (spontaneously) if exposed to air.Self-heating substances and mixturesThese products may catch fire if exposed to air. These products differ from pyrophoric liquids or solids in that they will ignite only after a longer period of time or when in large amounts.Substances and mixtures which, in contact with water, emit flammable gasesAs the class name suggests, these products react with water to release flammable gases. In some cases, flammable gases may ignite very quickly (spontaneously).Organic peroxidesThese products may cause a fire or explosion if heated.Corrosive to metalsThese products may be corrosive (chemically damage or destroy) to bustible dustThis class is used to warn of products that are finely divided solid particles. If dispersed in air, the particles may catch fire or explode if ignited.Simple asphyxiantsThese products are gases that may displace oxygen in the air and cause rapid suffocation.Physical hazards not otherwise classifiedThis class is meant to cover any physical hazards that are not covered in any other physical hazard class. These hazards must have the characteristic of occurring by chemical reaction and result in serious injury or death of a person at the time the reaction occurs. If a product is classified in this class, the hazard statement on the label and SDS will describe the nature of the hazard.Health HazardsHazard ClassGeneral DescriptionAcute toxicityThese products are fatal, toxic or harmful if inhaled, following skin contact, or if swallowed.?Acute toxicity refers to effects occurring following skin contact or ingestion exposure to a single dose, or multiple doses given within 24 hours, or an inhalation exposure of 4 hours.?Acute toxicity could result from exposure to the product itself, or to a product that, upon contact with water, releases a gaseous substance that is able to cause acute toxicity.Skin corrosion/irritationThis class covers products that cause severe skin burns (i.e., corrosion) and products that cause skin irritation.Serious eye damage/eye irritationThis class covers products that cause serious eye damage (i.e., corrosion) and products that eye irritation.Respiratory or skin sensitizationA respiratory sensitizer is a product that may cause allergy or asthma symptoms or breathing difficulties if inhaled. Skin sensitizer is a product that may cause an allergic skin reaction.Germ cell mutagenicityThis hazard class includes products that may cause or are suspected of causing genetic defects (permanent changes (mutations) to body cells that can be passed onto future generations).CarcinogenicityThis hazard class includes products that may cause or are suspected of causing cancer.Reproductive toxicityThis hazard class includes products that may damage or are suspected of damaging fertility or the unborn child (baby).?Note: There is an additional category which includes products that may cause harm to breast-fed children.Specific target organ toxicity – single exposureThis hazard class covers products that cause or may cause damage to organs (e.g., liver, kidneys, or blood) following a single exposure.?This class also includes a category for products that cause respiratory irritation or drowsiness or dizziness.Specific target organ toxicity – repeated exposureThis hazard class covers products that cause or may cause damage to organs (e.g., liver, kidneys, or blood) following prolonged or repeated exposure.Aspiration hazardThis hazard class is for products that may be fatal if they are swallowed and enter the airways.Biohazardous infectious materialsThese materials are microorganisms, nucleic acids or proteins that cause or is a probable cause of infection, with or without toxicity, in humans or animals.Health hazards not otherwise classifiedThis class covers products that are not included in any other health hazard class. These hazards have the characteristic of occurring following acute or repeated exposure and have an adverse effect on the health of a person exposed to it - including an injury or resulting in the death of that person.? If a product is classified in this class, the hazard statement will describe the nature of the hazard.Team/Project Checklist You can also download a copy of this letter on the CAN-SBX website (seds.ca/can-sbx)Faculty Endorsement LetterYou can also download a copy of this letter on the CAN-SBX website (seds.ca/can-sbx) ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download