The work during the project is divided into several \acp{WP}. For each package there are one or more team members responsible \change{with the main responsible person given below.} Responsibilities for the different work packages can be shifted if needed. Therefore, some team members will also work on work packages which are not their main responsibility.
This work package includes the team coordination, the organization of meetings, the orders to make, keeping track of budget/resources and the communication with the \ac{RX/BX} organizers.
This work package includes the paper work for the \ac{SED}. All team members are responsible to write documentation related to their work. The individual documentation tasks are distributed and then inserted into the \ac{SED} by the \ac{SED} supervisor\deleted{s \hannes\:and \clara}.
The design and fabrication of the mechanical housing \deleted{as well as the integration of the housing} and mounting of the experiment on the gondola are included in this work package. The thermal design is part of this work package as well.
The design \replaced{and fabrication of the circuit boards}{of the preamplifier board} as well as the design \change{and fabrication} of the electronical setup of the sensor head are included in this work package. The sensor head consists of the \acfp{SSD}, the Cherenkov detector and the \acf{BGO} crystal.
This work package consists of the development of the software needed to perform the experiment. A lot of software does already exist and needs to be adapted for \ac{CHAOS}. \change{This work package ties into the ground station development.}
This work package includes all tasks related to the testing \deleted{and calibration} of the instrument. \change{Tests are done for the overall system as well as subsystems.} A detailed description of the tests planned can be found in chapter \ref{sec:experiment_verification_and_testing}.
This work package includes the calibration \change[4]{measurements} of the different detector stages needed for a successful experiment and data treatment.}\change[4]{The work package does not include the detailed analysis of the performed measurements. Instead this will be part of the data analysis after the flight.}
This work package includes the analysis of the acquired flight data \change{during and} after the launch of \ac{CHAOS}. \change{This work package ties into the ground station development.}
This work package includes all tasks related to the outreach program. The outreach program is made up of different components. All team members are responsible to write blog entries about their work for our website \url{https://www.bexus.org/}. The Instagram and Linkdin pages are updated on a regular basis by the outreach supervisor. During the whole project, local media will be contacted. Conference visits (e.g. \ac{DPG} meeting in Greifswald) are planed as well.
The Gantt chart of the \ac{CHAOS} project is presented in figure \ref{fig:gantt}. A more detailed Gantt chart can be found in chapter \ref{sec:appendix}. There are the following milestones planned:
The following table \ref{tab:up_to_date_status} will be subsequently updated and will show the up-to-date status with respect to the original planning.
\\\change{The detailed Gantt chart in chapter \ref{sec:appendix} shows the current progress of the project. Furthermore, multiple critical paths can be identified and are marked. For example, the fabrication of the mechanical housing and electronics can only begin if the design process is finished. And the integration of the instrument can only start if the the mechanical and electronical subsystems are ready. Nevertheless, some overlap is expected. To start with the integration of the instrument not all subsystems are needed. Furthermore, the machine shop started to manufacture parts before the design process was finished due to time constraints.\\ The tests of the different subsystems span over the whole life cycle of the project and are not described in every last detail. Nevertheless, the begin of the different tests depends on whether the needed subsystems are ready. Especially for the system level tests the instrument has to be assembled.\\\deleted[3]{The calibrations of the subsystems have to be finished before the integration of the instrument.}\\The preparations for the data analysis should be finished until the Launch Campaign.}\\
Each team member has been given a field of work for the project. If a team member cannot finish a task, more team resources will be allocated towards it. All supporters can be contacted for help at any time. The main responsibilities of each team member are listed in section \ref{sec:team_members}. Nevertheless, some team members will have to do work outside their main responsibility.
While distributing the work, it has to be kept in mind that \replaced{\sophie\:and \clara\:will leave Kiel in autumn 2024.}{\sophie\:will leave Kiel in September/October 2024.} This will not affect the project in a negative way because \replaced{it was known in advanced and could be included in the project planning.}{most work in her responsibility will be done by then.} Furthermore, \tom\:\replaced{transferred}{will transfer} from \acs{CAU} Kiel to \acs{FH} Kiel in March 2024. \change{His bachelor's thesis gave insight in the scintillation behavior of the \ac{BGO} and let to some design decisions for \ac{CHAOS}. These insights were very useful but are not related to a specific work package. Lars Rahn joined the team in April 2024 and has no field of expertise yet. Therefore, he will not be assigned to a specific \acl{WP}. Instead, he will help wherever additional manpower is needed to gain experience and subsequently does not appear in table \ref{tab:work_distribution}.}
The availability of manpower is calculated under the assumption that team members with a high workload contribute \replaced{ten}{six} hours per week to the project on average. Members with medium workload are assumed to contribute \replaced{five}{four} hours and members with low workload two hours per week. These assumptions were made based on experiences from previous \ac{BEXUS} projects from \acs{CAU} Kiel. The actual amount of work done per week can vary depending on the phase of the project. Some team members are unavailable in the exam weeks 2024-02-12 to 2024-02-24, 2024-04-02 to 2024-04-13, 2024-07-15 to 2024-07-27 and 2024-10-07 to 2024-10-19. \change{Lars Rahn serves as replacement for Tom Ruge's manpower.} On average, there are \replaced{63}{50} hours available per week. Excluding the exam weeks, the projects spans over 50 weeks. This leads to approximately \replaced{3150}{2500} work hours available. Table \ref{tab:work_distribution} shows that the amount of planned work sums up to \replaced{3000}{2370} hours. Therefore, there are more work hours available than needed. The distribution of work hours in table \ref{tab:work_distribution} is based on experiences from previous \ac{BEXUS} projects from \acs{CAU} Kiel as well.
Currently, we plan to have the \ac{ZARM} cover some of the cost of the materials needed. All other expenses for the experiment are covered by the \ac{IEAP}, because we mainly use parts which are already in stock at the \acs{IEAP}.
The \ac{RX/BX} programme only covers the travel expenses for a limited number of students. Additional team members are therefore sponsored by the \ac{IEAP} and listed in an extra line in table \ref{tab:cost_estimation_travel}. Travel expanses which are not part of the official \ac{RX/BX} programme (conference visists, etc.) are covered by the \ac{IEAP}. Sometimes, only approximations of the costs can be given because informations are missing. For example, \ac{ZARM} covered some travel expanses, but provided no invoices.
At the \acs{IEAP} we have guaranteed access to an electronics lab with soldering stations, a clean room, a thermal vacuum chamber, computers for simulations, a 3D printer for manufacturing and different radioactive probes for calibration. Furthermore, the Physics Department of Kiel University has its own machine shop with staff to produce parts.
Our team consists of students from the Department of Extraterrestrial Physics, which is part of the Institute of Experimental and Applied Physics (\acs{IEAP}) at the \acf{CAU} zu Kiel and already contributed to numerous missions to space. We can count on the support of many different experts from our department listed in table \ref{tab:external_support}. The \ac{IEAP} also covers some of our expenses. Further technical and financial support comes from \ac{ZARM}.
Our public outreach program is made up of our website, social media pages and conference visits. A highlight was the flight of our instrument \ac{CHAOS}junior prior to our acceptance to the \ac{BEXUS} programme. \change{More information on our outreach programme can be found in chapter \ref{sec:outreach_appendix}.}
Our website, accessible at \url{https://www.bexus.org/}, stands as the primary information portal for the \ac{CHAOS} project. This website is not only a repository of comprehensive details about the current project's goals, activities, and achievements but also features a dedicated blog section. This blog is a vital aspect of the website, offering in-depth articles, updates, and insights into the project's progress and developments. It serves as a dynamic platform for storytelling and sharing knowledge, making the project more accessible and engaging to a wide audience.\\
Furthermore, the website is designed with future scalability in mind. It is envisioned to serve as a platform for showcasing various \ac{BEXUS} projects undertaken by \ac{CAU} Kiel. An example of this is the inclusion of the \ac{TANOS} project, which is already featured on the site. This approach not only highlights the diverse range of projects under the \ac{BEXUS} umbrella but also ensures that the website remains a relevant and up-to-date resource for anyone interested in the scientific and technological advancements at \ac{CAU} Kiel.
\subsection{Instagram}
Instagram is a key platform in our outreach strategy. It is particularly effective for engaging with younger demographics, such as students, and sparking their interest in the \ac{BEXUS} project or scientific disciplines in general. Through visually appealing content and interactive features, Instagram allows us to create a more relatable and engaging narrative around our project. This platform is crucial for building a community of followers who are keenly interested in our activities and updates. Our Instagram page can be found at \url{https://www.instagram.com/chaos.bexus/}.
Visits to scientific conferences offer the possibility to present \ac{CHAOS} to other scientists in a more professional context. Here, we can get useful feedback from other experts in our field. Furthermore, it is a chance for us as aspiring scientists to gain first experiences in scientific communication and networking. \replaced{The first conference which we attended was the \ac{DPG} Spring Meeting in Greifswald in February 2024 (see section \ref{sec:dpg_spring_meeting}).}{The first conference we plan to attend is the \ac{DPG} Spring Meeting in February 2024.}
As part of our application to the \ac{BEXUS} program we started a simplified version of our experiment called \ac{CHAOS}junior during the science festival "Highlights der Physik" (\url{https://www.highlights-physik.de/}) which took place in Kiel in September 2023. The festival was aimed at school children and tried to interest them in physics and sciences in general. \ac{CHAOS}junior was our contribution to this endeavour. More information on the flight of \ac{CHAOS}junior can be found at \url{https://www.bexus.org/index.php/2023/09/30/successful-launch-of-chaosjunior/} and \url{https://www.bexus.org/index.php/2023/10/01/mission-success-recovery-of-chaosjunior/}.
\subsection{Others}
While our primary focus remains on the \ac{BEXUS} website and Instagram, we also recognize the value of other social media platforms such as Facebook and LinkedIn. Facebook offers additional reach, allowing us to connect with a broader audience and share updates and news about the project. LinkedIn, on the other hand, provides a more professional presence. It is an excellent platform for networking with industry professionals and academics, which can lead to potential collaborations and opportunities. However, it's important to note that our main emphasis will continue to be on maintaining a strong and informative presence on our website and engaging with our audience on Instagram.
\change[5]{Just prior to the launch campaign, our team was visited by NDR television to produce a TV report which aired on the 25th September 2024 \citep{ndr2024}. The report was also published on the website of German news broadcast \textit{tagesschau} (see chapter \ref{sec:ndr_television}). With the TV appearance an audience was reached which is normally not invested in scientific research.}
PE01 & Team member unable to continue with the project. & B & 3 &\cellcolor{low}low & Enough team members to compensate any drop out, overlapping expertise of team members enables quick exchange \\
\color{black} SF01 &\color{black} Use of \acf{HV}. &\color{black} B &\color{black}\replaced[4]{3}{\replaced[3]{4}{5}}&\cellcolor{low}low &\color{black} Building a pressure housing around the experiment to avoid corona discharges and prevent direct contact with the \acf{HV}. \replaced[4]{During descent the \ac{HV} will be automatically ramped down once the pressure outside the pressure housing rises above 800\,mbar. Furthermore, the \ac{HV} will be ramped down if the pressure inside the pressure housing falls under 500\,mbar.}{The \ac{HV} will be ramped down for pressures above 800\,mbar during descent and leakage of the pressure housing.} Integration of LED indicating \acs{HV} operation. The energy stored in the \ac{HV} electronics will not exceed 4\,mJ.\\
\color{black} SF02 &\color{black} Sharp edges of the mechanical housing. & A & 2 &\cellcolor{verylow}very low &\color{black} Sharp edges are mitigated in the design process. Furthermore, the experiment is placed inside a pressure housing and inside an insulation box.\\
TC01 & Data damage on the SD-Card during landing. & B & 3 &\cellcolor{low}low & The downlink will be used as additional backup. No data will be stored on the SD\:card for pressures above 800\,mbar during descent.\\
\color{black}TC02-1 &\color{black}Experiment gets too hot. &\replaced[4]{B}{C}& 4 &\cellcolor{low}low &\color{black}An appropriate insulation system is planned. Usage of heritage and well tested components. Tests will ensure functionality. \\
\color{black}TC02-2 &\color{black}Experiment gets too cold. &\replaced[4]{B}{C}& 4 &\cellcolor{low}low &\color{black}An appropriate insulation system is planned. Usage of heritage and well tested components. Tests will ensure functionality. \\
TC05 & Failure of one or several electronic components due to production errors or overheating & A & 3 &\cellcolor{verylow}very low & Usage of heritage and well tested components.\\
TC07 & Failure of a part of the sensor head during flight due to defect bond wires. & A & 3 &\cellcolor{verylow}very low & Careful installation of the sensor head in the mounting solution. Test functionality before flight.\\
MS02 & Ground software program fails during flight. & A & 2 &\cellcolor{verylow}very low & Secure stability of software through long time tests and bring a second ground station. \\
MS04 & Experiment delivery to launch campaign not in time. & A & 4 &\cellcolor{verylow}very low & Send experiment via \ac{ZARM} after thermal vacuum test week. \\
VE01 & Mounting solution breaks during landing, experiment becomes loose. & C & 2 &\cellcolor{low} low & Conduct pre-flight test to make sure mounting solution is stable enough to withstand sufficient impacts.\\
