%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% ULTIMATE GUIDE TO WRITING A WORLD-CLASS SPACE MISSION PROPOSAL
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
% Author: [Your Name]
% Date:   [Date]
%
% This LaTeX template is structured to meet the high standards of
% a space mission proposal. It includes commentary on best
% practices for how to write each section
%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\documentclass[12pt]{article}

%===================== PACKAGES =====================%
\usepackage[margin=1in]{geometry}   % 1-inch margins all around
\usepackage{graphicx}               % For figures
\usepackage{amsmath,amssymb}        % Math symbols/environments
\usepackage{hyperref}               % Hyperlinks in PDF
\usepackage{setspace}               % For line spacing
\usepackage{booktabs}               % Professional-looking tables
\usepackage{siunitx}                % SI units formatting
\usepackage{enumitem}               % Customized lists
\usepackage[numbers,sort&compress]{natbib} % Numeric references
\usepackage{xcolor}                 % Colored text
\usepackage{fancyhdr}               % Custom headers/footers
\usepackage{tcolorbox}              % For "speech bubble" or highlight boxes
\usepackage[table]{xcolor}  % For color in tables
\usepackage{pgfgantt}   % For Gantt charts
\usepackage{tikz}       % Required by pgfgantt
\usepackage{booktabs}   % For enhanced table aesthetics
\usepackage{array}      % For better table formatting
\usepackage{siunitx}    % For consistent SI units
\usepackage{caption}    % For customizing captions
\usepackage{enumitem}   % For customized lists
\usepackage{geometry}   % For setting page dimensions


%\usepackage{helvet}                % (Optional) For a sans-serif font style
%\renewcommand{\familydefault}{\sfdefault}

%================= DOCUMENT PROPERTIES ==============%

\title{\bfseries Guide to Writing a Space Mission Proposal}
\author{[Your Name]\\
\textit{[Your Institution or Organization]}}
\date{\today}

% Header/Footer setup (Optional)
\pagestyle{fancy}
\fancyhf{}
\rhead{\thepage}
\lhead{\textit{Space Mission Proposal}}

%==================== START DOCUMENT =================%
\begin{document}
\maketitle

%------------------- EXECUTIVE SUMMARY (OPTIONAL) -------------------%
\noindent
\textbf{(Optional) Executive Summary}

\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Executive Summary)]
\begin{itemize}
\item \textbf{Purpose and Role:} The Executive Summary is typically placed before the Table of Contents. It gives the \textit{highest level} overview of the mission’s essential points. Decision-makers often read only this section to decide if they should go further.

\item \textbf{Conciseness is Key:}
  \begin{itemize}
    \item Keep it short (1-2 pages max) and direct. 
    \item Emphasize significance, unique selling points, and mission feasibility.
  \end{itemize}

\item \textbf{What to Include:}
  \begin{itemize}
    \item \textit{Mission Concept}: In one or two sentences, give the essence of what you’re trying to accomplish.
    \item \textit{Rationale}: Summarize \textbf{why} the mission matters—scientific, economic, societal impact.
    \item \textit{Key Objectives \& Outcomes}: Bullet out the most important targets (scientific measurements, technology demos, partnerships).
    \item \textit{Benefits and Implications}: Explain how these results or technologies will advance the field or solve a critical gap.
    \item \textit{High-Level Feasibility}: Mention overall cost or schedule feasibility if you have strong metrics (e.g., “within a \$150M budget”).
  \end{itemize}

\item \textbf{Tone \& Style:} Use persuasive language, but remain factual. Reference the novelty compared to previous missions.

\item \textbf{Review Tip:} Have multiple stakeholders (technical and non-technical) review this summary to ensure it speaks to a broad audience.
\end{itemize}
\end{tcolorbox}

\begin{abstract}
\noindent
\textbf{Executive Summary:}
This proposal introduces the \textit{[Mission Name]} mission concept, developed to address critical objectives in \textit{[Target Science Area]} while advancing next-generation spacecraft capabilities beyond those demonstrated by prior missions. This mission fills an essential gap in our current understanding of \textit{[Phenomena]}, leveraging novel data acquisition methods and autonomous operations to ensure high-impact, cost-effective results.

Major goals include:
\begin{enumerate}
\item Measuring \textit{[Parameter]} at unprecedented resolution, far surpassing existing benchmarks,
\item Validating an advanced autonomous navigation system for enhanced real-time hazard detection and avoidance,
\item Establishing robust international or commercial partnerships to amplify scientific reach and economic viability.
\end{enumerate}

Operating for \textit{[Duration]}, \textit{[Mission Name]} is expected to return \textit{[Data Volume]} of valuable data, driving breakthroughs in \textit{[Target Science Area]} and offering immediate applications for broader scientific, economic, or societal benefit. Preliminary analyses confirm that the mission can be executed within a feasible schedule and budget framework (e.g., \textit{[Proposed Cost]}, \textit{[Proposed Timeline]}), making it a strong candidate for agencies seeking innovative yet achievable solutions.
\end{abstract}


\clearpage
\tableofcontents
\clearpage

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 1. INTRODUCTION
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Introduction}
\label{sec:introduction}

\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Introduction)]
\begin{itemize}
    \item \textbf{Set the Stage:} Provide context on the state of the art, existing missions, or unsolved problems that drive the need for your proposed mission.
    \item \textbf{Highlight Significance:} Illustrate the potential impact (scientific, commercial, exploratory, or societal). This helps evaluators see the value proposition.
    \item \textbf{Bridge Gaps:} Clearly identify the gap in knowledge or capability that your mission will address. Show how the mission is \textit{uniquely} poised to fill this gap.
    \item \textbf{Use Clear, Crisp Language:} An introduction should be free of technical jargon unless necessary. Provide definitions or references if you must use specialized terms.
    \item \textbf{Transition to Proposal Structure:} Conclude the introduction with a short summary of how the document is organized and how each section builds upon the last.
    \item \textbf{Establish Credibility:} If relevant, mention your team’s experience or prior mission heritage in a subtle, direct manner.
\end{itemize}
\end{tcolorbox}

\subsection{Purpose and Scope}
\noindent
\textbf{Purpose:}  
This document presents a comprehensive proposal for the design, development, and operation of the \textit{[Mission Name]} mission. Conceived to address pivotal scientific or technological challenges in \textit{[Field: planetary science, Earth observation, astrophysics, etc.]}, the mission aspires to deliver breakthrough results at a standard consistent with the world’s foremost space programs.

\noindent
\textbf{Scope:}
\begin{itemize}
    \item Spans the entire mission life cycle, from conceptual planning to decommissioning and disposal.
    \item Defines high-level goals, objectives, subsystem requirements, and overarching strategies for risk mitigation, schedule, and budget.
\end{itemize}

\subsection{Document Structure}
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Document Structure)]
\begin{itemize}
    \item \textbf{Roadmap for Reviewers:} Summarize each major section so that anyone can quickly jump to relevant parts.
    \item \textbf{Logical Flow:} Each section logically follows from the previous (e.g., “Mission Goals” before “Requirements”).
    \item \textbf{Short Summaries:} Keep the overview concise; more detailed content appears in the respective sections.
    \item \textbf{Clarity \& Conciseness:} Busy reviewers appreciate immediate orientation and clear navigation cues.
\end{itemize}
\end{tcolorbox}

\noindent
\textbf{Proposed Organization:}
\begin{itemize}
    \item \hyperref[sec:goals_objectives]{\textbf{Mission Goals and Objectives}} – Establishes the mission’s purpose and defines specific, measurable objectives aligned with the overarching goals.
    \item \hyperref[sec:req]{\textbf{Mission Requirements}} – Specifies the mandatory, measurable criteria necessary to achieve mission success, organized by system and subsystem levels.
    \item \hyperref[sec:conops]{\textbf{Concept of Operations (ConOps)}} – Outlines the mission’s phased operational timeline, including nominal and contingency operations from launch to disposal.
    \item \hyperref[sec:arch]{\textbf{Mission Architecture and Design}} – Describes the spacecraft's architecture, subsystem designs, key trade studies, and performance margins.
    \item \hyperref[sec:vv]{\textbf{Verification and Validation (V\&V)}} – Details the methodologies to confirm compliance with requirements and validate mission objectives through testing, analysis, and demonstration.
    \item \hyperref[sec:risk]{\textbf{Risk Management}} – Identifies mission risks, evaluates their likelihood and impact, and describes mitigation strategies and contingency plans.
    \item \hyperref[sec:schedule_budget]{\textbf{Schedule and Budget}} – Provides an overview of the project timeline, major milestones, cost breakdowns, and funding profiles, including reserves and contingencies.
    \item \hyperref[sec:optional_sections]{\textbf{Optional Sections}} – Enhances the proposal with additional sections like Technology Readiness Assessment, Launch Vehicle Details, and Educational Outreach Plans.
    \item \hyperref[sec:appendices]{\textbf{Appendices}} – Includes supplementary materials such as detailed technical data, interface control documents, and a glossary of acronyms.
    \item \textbf{References} – Lists all cited sources, formatted in IEEE style, including links to standards, handbooks, and peer-reviewed publications.
\end{itemize}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 2. MISSION GOALS AND OBJECTIVES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Mission Goals and Objectives}
\label{sec:goals_objectives}

%-------------------------------------------
% FIRST BOX (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Goals \& Objectives, Part 1)]
\begin{itemize}
    \item \textbf{Hierarchy of Intent:} 
    \begin{itemize}
        \item \textit{Goals} describe the broad, aspirational “why” of the mission. They capture the overarching vision, the scientific or technological “grand challenge,” and the strategic motivation behind your endeavor.
        \item \textit{Objectives} translate each goal into concrete, time-bound, and measurable targets—the actionable “what” and “how much.”
    \end{itemize}

    \item \textbf{S.M.A.R.T. Objectives:} For every stated objective, check that it is:
    \begin{itemize}
        \item \textbf{Specific:} Pinpoint exactly which parameter or phenomenon you aim to measure, test, or demonstrate.
        \item \textbf{Measurable:} Incorporate quantitative or qualitatively verifiable metrics (e.g., “achieve \SI{2}{km} spatial resolution,” “acquire \SI{3}{Tb} of data,” “maintain \SI{1}{degree} pointing accuracy”).
        \item \textbf{Achievable:} Align with current or near-future technology readiness, available budget, and schedule constraints.
        \item \textbf{Relevant:} Tie clearly to the mission’s science or technology theme, while supporting broader agency or stakeholder priorities.
        \item \textbf{Time-bound:} Indicate the timeframe for completion (e.g., “within 12 months of launch,” “by the end of Phase C”).
    \end{itemize}

    \item \textbf{Consistency with Agency Priorities:}
    \begin{itemize}
        \item Reference higher-level strategies such as NASA’s \textit{Decadal Survey} or ESA’s \textit{Cosmic Vision}, showing how your objectives align with established roadmaps.
        \item Explicit cross-reference each goal to major science themes or technology roadmap items wherever possible to bolster the proposal’s relevancy.
    \end{itemize}

        \item \textbf{Clear Goal–Objective Linking:}
    \begin{itemize}
        \item At the end of each objective, identify which goal(s) it advances (e.g., “This addresses Goal~2.”).
        \item If multiple objectives support the same goal, ensure they do so from different angles (e.g., measurement, demonstration, operations).
    \end{itemize}
    
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SECOND BOX (PART 2)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Goals \& Objectives, Part 2)]
\begin{itemize}

    \item \textbf{Prioritization and Grouping:}
    \begin{itemize}
        \item Mark critical, “must-have” objectives (primary) vs.\ aspirational or “enhancing” objectives (secondary).
        \item If helpful, cluster objectives by major themes (e.g., \textit{Scientific Objectives}, \textit{Technology Demonstration Objectives}) to guide reviewers’ focus.
    \end{itemize}

    \item \textbf{Forward-Looking Impact:}
    \begin{itemize}
        \item Indicate how meeting these goals opens doors for follow-on missions, spin-off technologies, or extended scientific inquiries.
        \item Provide a brief outlook on how data archiving or technology transitions might be leveraged by future NASA, ESA, or commercial projects.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% MISSION GOALS
%-------------------------------------------
\subsection{Mission Goals}
\begin{itemize}
    \item \textbf{Goal 1:} \textit{Scientific Breakthroughs.} Substantially advance our understanding of \textit{[Target Phenomenon]} by acquiring high-fidelity, multi-parameter data. This addresses specific knowledge gaps identified in \textbf{[Relevant Decadal Survey / Agency Directive]} and contributes novel insights to the global scientific community.

    \item \textbf{Goal 2:} \textit{Next-Generation Technology Validation.} Demonstrate and validate cutting-edge spacecraft systems—such as autonomous navigation, advanced materials, or novel propulsion concepts—enabling future long-duration or cost-effective missions beyond current state-of-the-art capabilities.

    \item \textbf{Goal 3:} \textit{Global Collaboration \& Outreach.} Establish a robust international or public-private partnership framework, aiming to maximize scientific return and inspire cross-disciplinary innovations. This includes data sharing agreements, co-development of payloads, or joint mission operations.
\end{itemize}

%-------------------------------------------
% MISSION OBJECTIVES
%-------------------------------------------
\subsection{Mission Objectives}
\noindent
Each objective below is directly linked to one or more of the above goals, maintaining a tight, traceable structure.

\begin{enumerate}[label=Objective \arabic*.]
    \item \textbf{High-Resolution Parameter Mapping:}
    \begin{itemize}
        \item \textit{Statement:} Obtain measurements of \textit{[Physical Parameter]} with \(\pm \SI{0.1}{\percent}\) accuracy over a \SI{12}{month} operational period.
        \item \textit{Relevance:} Fills the data gap highlighted by \textbf{Goal~1}, offering unprecedented detail for modeling or fundamental research.
        \item \textit{Measurable Target:} Achieve at least \SI{95}{\%} coverage of the targeted region, with less than \SI{10}{\%} data loss due to downlink or sensor anomalies.
        \item \textit{Timeframe:} Complete coverage by the end of nominal mission phase (12 months after commissioning).
    \end{itemize}

    \item \textbf{Autonomous Navigation Validation:}
    \begin{itemize}
        \item \textit{Statement:} Implement and validate an on-board navigation system capable of maintaining a positional accuracy of \(\pm \SI{5}{\meter}\) for \SI{6}{months} continuously.
        \item \textit{Relevance:} Demonstrates next-generation autonomy under \textbf{Goal~2}, reducing reliance on ground-based tracking and enabling deep-space orbits with minimal communication delays.
        \item \textit{Success Criteria:} Successful station-keeping maneuvers and hazard avoidance documented via post-mission analysis.
        \item \textit{Timeframe:} Validation testing begins after 3 months in-orbit, concluded by 9 months in-orbit.
    \end{itemize}

    \item \textbf{Data Return \& Coverage:}
    \begin{itemize}
        \item \textit{Statement:} Downlink a minimum of \SI{2}{Tb} of high-quality, error-corrected data covering \(\geq 90\%\) of \textit{[Target Region]}.
        \item \textit{Relevance:} Supports \textbf{Goal~1} (robust scientific dataset) and \textbf{Goal~3} (collaboration on data analysis and distribution).
        \item \textit{Performance Metric:} At least 90\% of recorded data are within acceptable signal-to-noise thresholds; data made publicly available within 2 months of acquisition for collaborative research.
    \end{itemize}

    \item \textbf{International/Commercial Partnership:}
    \begin{itemize}
        \item \textit{Statement:} Establish at least one major partnership (e.g., shared ground stations, joint development of a secondary payload) to amplify mission outcomes.
        \item \textit{Relevance:} Ties directly to \textbf{Goal~3}, fostering global engagement and potential cost-sharing or technology transfer.
        \item \textit{Success Criteria:} Formal Memoranda of Understanding (MOUs) signed prior to launch; joint operations or data-sharing activities documented by end of mission.
        \item \textit{Optional or Secondary Objective:} If schedule or budget constraints require de-scoping, maintain minimal data-exchange channels with future partnership expansion in subsequent missions.
    \end{itemize}
\end{enumerate}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 3. MISSION REQUIREMENTS
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Mission Requirements}
\label{sec:req}

%-------------------------------------------
% FIRST BOX (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Requirements)]
\begin{itemize}
    \item \textbf{Definition:} Requirements represent the mission’s \textit{essential} capabilities and constraints. They derive directly from stated objectives and serve as the cornerstone for design, development, verification, and operations.

    \item \textbf{Precision \& Testability:} 
    \begin{itemize}
        \item Use “\textit{shall}” for strict requirements to remove all ambiguity.
        \item Each requirement \textit{must} be objectively verifiable via testing, analysis, inspection, or demonstration.
        \item Specify measurable criteria (e.g., power levels in Watts, temperature in \si{\celsius}, velocity in \si{m/s}, etc.) to ensure clarity.
    \end{itemize}

    \item \textbf{Requirement Categories:}
    \begin{itemize}
        \item \textit{System-Level Requirements}: Broad constraints, performance baselines, and overarching architecture drivers (e.g., total mission duration, data throughput).
        \item \textit{Subsystem-Level Requirements}: Constraints tailored to specific mission domains (propulsion, thermal, communications, structures, etc.).
        \item \textit{Derived Requirements}: Further requirements uncovered through system analyses, simulations, or compliance with external regulations (e.g., debris mitigation, radiation tolerance).
    \end{itemize}

    \item \textbf{Avoid Over-Specification:}
    \begin{itemize}
        \item Only impose constraints that directly advance mission objectives or mitigate critical risks.
        \item Overly rigid specs can inflate cost and schedule; strive for balanced, “just enough” definitions.
    \end{itemize}

    \item \textbf{Traceability:} 
    \begin{itemize}
        \item Each requirement \textit{shall} map to at least one mission objective.
        \item A Requirements Traceability Matrix (RTM) is strongly encouraged for systematically tracking coverage, verification, and accountability.
    \end{itemize}
    
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SECOND BOX (PART 2)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Requirements)]
\begin{itemize}

    \item \textbf{Common Pitfalls:}
    \begin{itemize}
        \item Vague or subjective wording (e.g., “should be robust”)—instead, include quantifiable measures (e.g., “survive \(\Delta T\) of \SI{60}{\celsius}”).
        \item Contradictory requirements (e.g., conflicting mass vs.\ volume allocations) or ignoring cross-subsystem impacts.
        \item Failing to account for official standards/regulations (NASA-STD-8719.14 on debris, ESA ECSS for systems engineering, etc.).
    \end{itemize}

    \item \textbf{Documentation Best Practices:}
    \begin{itemize}
        \item \textbf{Unique IDs:} Use a consistent naming scheme (e.g., “REQ-SYS-XXX” for system-level, “REQ-THERM-XXX” for thermal, etc.).
        \item \textbf{Grouping:} Organize requirements by subsystem or functional domain for clarity and streamlined design reviews.
        \item \textbf{Threshold vs.\ Goal:} 
        \begin{itemize}
            \item \textit{Threshold} = the \textbf{minimum} acceptable performance to meet mission objectives.
            \item \textit{Goal} = the \textbf{desired} or optimal target offering higher performance or additional capability.
        \end{itemize}
    \end{itemize}

    \item \textbf{Change Control \& Configuration Management:}
    \begin{itemize}
        \item Document the rationale for any requirement change, along with cost, schedule, and risk impact.
        \item Obtain approval from a designated board (e.g., Systems Engineering Review Board) before altering baselined requirements.
    \end{itemize}

    \item \textbf{Verification and Validation:}
    \begin{itemize}
        \item Identify methods early: test (thermal vacuum, vibration, functional), analysis (link budget, FEA), inspection (dimensions, workmanship), demonstration (integrated system).
        \item Tie each requirement to a verification event or milestone (e.g., integration testing, environmental qualification, operational readiness tests).
    \end{itemize}

\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SYSTEM-LEVEL REQUIREMENTS
%-------------------------------------------
\subsection{System-Level Requirements}

\subsubsection{Performance Requirements}
\begin{itemize}
    \item \textbf{REQ-SYS-001:} The spacecraft \textit{shall} collect data at a minimum continuous rate of \SI{1}{Mbps} during nominal operations. 
    \begin{itemize}
        \item \textit{Rationale:} Ensures sufficient science data return per day to fulfill mission objectives.
        \item \textit{Verification:} End-to-end communication test and link-budget analysis.
    \end{itemize}

    \item \textbf{REQ-SYS-002:} The mission \textit{shall} maintain an operational lifetime of at least \SI{2}{years}, enabling multi-seasonal science campaigns. 
    \begin{itemize}
        \item \textit{Rationale:} Supports extended data collection and environmental variability studies.
        \item \textit{Verification:} Reliability analysis and life testing of critical components (e.g., battery cycles, propulsion cycles).
    \end{itemize}
\end{itemize}

\subsubsection{Operational Requirements}
\begin{itemize}
    \item \textbf{REQ-SYS-003:} The spacecraft \textit{shall} operate autonomously for up to \SI{48}{hours} in the event of lost ground-link. 
    \begin{itemize}
        \item \textit{Rationale:} Protects spacecraft during communication outages or safe-mode transitions.
        \item \textit{Verification:} Functional demonstration of on-board autonomy algorithms in relevant environment.
    \end{itemize}

    \item \textbf{REQ-SYS-004:} The spacecraft’s safe-mode power consumption \textit{shall} not exceed \SI{100}{W}. 
    \begin{itemize}
        \item \textit{Rationale:} Ensures limited battery and solar power resources are not overly taxed during anomalies.
        \item \textit{Verification:} Power budget analysis and integrated system power draw test.
    \end{itemize}
\end{itemize}

%-------------------------------------------
% SUBSYSTEM REQUIREMENTS
%-------------------------------------------
\subsection{Subsystem Requirements}
\begin{itemize}
    \item \textbf{REQ-PROP-001:} The propulsion subsystem \textit{shall} deliver a total \(\Delta v\) capability of at least \SI{300}{m/s} for station-keeping and maneuvering. 
    \begin{itemize}
        \item \textit{Rationale:} Required for orbital adjustments and potential de-orbit or end-of-mission disposal.
        \item \textit{Verification:} Analysis of propulsion models (propellant mass, thruster performance), validated via acceptance testing.
    \end{itemize}

    \item \textbf{REQ-THERM-001:} The thermal control subsystem \textit{shall} maintain all critical components within a temperature range of \SI{-10}{\celsius} to \SI{50}{\celsius} under worst-case conditions.
    \begin{itemize}
        \item \textit{Rationale:} Protects sensitive electronics from extreme temperature excursions.
        \item \textit{Verification:} Thermal vacuum testing, thermal balance test, and environmental modeling (including margin).
    \end{itemize}
\end{itemize}

%-------------------------------------------
% DERIVED REQUIREMENTS
%-------------------------------------------
\subsection{Derived Requirements}
\begin{itemize}
    \item \textbf{REQ-DER-001:} The spacecraft bus \textit{shall} withstand a total ionizing dose (TID) of up to \SI{50}{krad} based on radiation environment analyses. 
    \begin{itemize}
        \item \textit{Rationale:} Protects mission-critical electronics from space radiation over the operational lifetime.
        \item \textit{Verification:} Radiation testing and component-level qualification (e.g., per NASA-STD-4003 or equivalent).
    \end{itemize}

    \item \textbf{REQ-DER-002:} The mission \textit{shall} comply with international orbital debris mitigation standards (e.g., NASA-STD-8719.14), ensuring safe disposal or passivation post-mission.
    \begin{itemize}
        \item \textit{Rationale:} Reduces risk to other spacecraft and ensures responsible end-of-life practices.
        \item \textit{Verification:} Formal review of de-orbit plans or passivation procedures, documented in the final mission disposal plan.
    \end{itemize}
\end{itemize}

%-------------------------------------------
% REQUIREMENTS TRACEABILITY MATRIX (RECOMMENDED)
%-------------------------------------------
\subsection{Requirements Traceability Matrix (Recommended)}
\begin{table}[h!]
\centering
\caption{Illustrative Requirements Traceability Matrix}
\begin{tabular}{@{}llll@{}}
\toprule
\textbf{Requirement ID} & \textbf{Linked Objectives} & \textbf{Verification Method} & \textbf{Verification Level} \\
\midrule
REQ-SYS-001   & Obj.\ 1, 3  & Test (End-to-End Comms)             & System \\
REQ-PROP-001  & Obj.\ 2     & Analysis (Propulsion Modeling)      & Subsystem \\
REQ-DER-001   & All         & Radiation Testing                   & System \\
REQ-DER-002   & Obj.\ 3, 4  & Review of Disposal Plan             & System \\
\bottomrule
\end{tabular}
\end{table}

\noindent
\textit{Note:} Including columns for \textit{Rationale}, \textit{Mission Phase}, and \textit{Priority} can further enhance the matrix, along with references to external standards such as \textbf{NASA NPR 7123.1} for Systems Engineering and \textbf{ECSS-E-ST-10-06C} for European missions.

\vspace{1em}
\noindent
A well-maintained traceability matrix ensures every requirement remains anchored to a mission objective, with a clearly defined path to verification. Each change to a requirement \textit{must} follow a formal change-control process, ensuring updates are properly evaluated, approved, and documented.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 4. CONCEPT OF OPERATIONS (ConOps)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Concept of Operations (ConOps)}
\label{sec:conops}

%-------------------------------------------
% FIRST BOX (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (ConOps, Part 1)]
\begin{itemize}
    \item \textbf{Comprehensive Timeline:} 
    \begin{itemize}
        \item Present a top-level view of mission events from launch to decommissioning (LEOP, commissioning, primary operations, disposal).
        \item Highlight key transitions (e.g., final orbit insertion, payload deployments, major calibrations).
    \end{itemize}

    \item \textbf{Nominal vs.\ Contingency:} 
    \begin{itemize}
        \item Clearly differentiate normal “day-to-day” operations from unexpected fault conditions.
        \item Define safe-mode triggers (e.g., power or thermal anomalies) and outline fallback procedures for rapid recovery.
    \end{itemize}

    \item \textbf{Phase-by-Phase Details:}
    \begin{itemize}
        \item Summarize each mission phase (LEOP, commissioning, primary ops, extended ops, disposal).
        \item Call out critical milestones such as orbit raising, major subsystem tests, or software updates.
    \end{itemize}

    \item \textbf{Visual Aids:}
    \begin{itemize}
        \item Use diagrams, flowcharts, or Gantt timelines for clarity. Show data flow paths, commanding flows, and decision points.
        \item Illustrate nominal operations vs.\ contingency routes on the same chart for easy comparison.
    \end{itemize}

        \item \textbf{Use Cases:}
    \begin{itemize}
        \item Describe routine scenarios (science data collection, downlink sessions, station-keeping) to validate mission readiness.
        \item Include contingency case narratives: safe-mode entry, ground intervention steps, and timeline to resume nominal operations.
    \end{itemize}

    \item \textbf{Granularity:}
    \begin{itemize}
        \item Provide sufficient operational detail to show thorough planning (e.g., how frequently comm passes occur).
        \item Avoid overloading the section with excessive timelines or hourly schedules unless specifically required.
    \end{itemize}

    
    
\end{itemize}
\end{tcolorbox}


%-------------------------------------------
% MISSION PHASES
%-------------------------------------------
\subsection{Mission Phases}
A common approach divides operations into distinct phases:

\begin{enumerate}[label=\textbf{Phase \arabic*:}]
    \item \textbf{Launch \& Early Orbit (LEOP):}
    \begin{itemize}
        \item Deploy the spacecraft from the launch vehicle. 
        \item Power on and verify essential subsystems (e.g., communication, power, thermal).
        \item Establish initial ground communication and assess spacecraft health.
    \end{itemize}

    \item \textbf{Commissioning:}
    \begin{itemize}
        \item Calibrate and validate all subsystems (e.g., ADCS, communication, thermal) and payload instruments.
        \item Refine orbital parameters (station-keeping maneuvers if needed).
        \item Transition from initialization settings to full operational readiness.
    \end{itemize}

    \item \textbf{Primary Operations:}
    \begin{itemize}
        \item Execute the nominal science plan or primary mission objectives.
        \item Collect and downlink data during scheduled contact windows.
        \item Perform routine health checks, station-keeping maneuvers, and orbit maintenance (if applicable).
    \end{itemize}

    \item \textbf{Extended Operations:}
    \begin{itemize}
        \item Pursue additional science or technology goals, capitalizing on remaining resources (propellant, instrument lifespan).
        \item Adapt operational parameters based on in-flight discoveries or emerging collaboration opportunities.
    \end{itemize}

    \item \textbf{Disposal/End-of-Life:}
    \begin{itemize}
        \item Deorbit or execute passivation maneuvers in line with debris mitigation guidelines (e.g., NASA-STD-8719.14).
        \item Archive final datasets, secure handover of remaining deliverables, and formally close mission operations.
    \end{itemize}
\end{enumerate}

%-------------------------------------------
% OPERATIONAL SCENARIOS
%-------------------------------------------
\subsection{Operational Scenarios}
\begin{itemize}
    \item \textbf{Nominal Operations:}
    \begin{itemize}
        \item Routine data acquisition and instrument mode transitions (standby \(\rightarrow\) active).
        \item Scheduled communication passes for data downlink and command uplink.
        \item Periodic subsystem health checks (e.g., telemetry analysis for power, thermal, ADCS).
    \end{itemize}
    
    \item \textbf{Contingency Operations:}
    \begin{itemize}
        \item Automatic entry into safe-mode upon detecting anomalies (e.g., undervoltage, excessive temperature).
        \item Predefined decision tree for ground operators to diagnose and resolve issues.
        \item System recovery and re-entry to nominal operations once fault isolation and rectification are confirmed.
    \end{itemize}
\end{itemize}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 5. MISSION ARCHITECTURE AND DESIGN
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Mission Architecture and Design}
\label{sec:arch}

%-------------------------------------------
% FIRST BOX (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Architecture \& Design: Part 1)]
\begin{itemize}
    \item \textbf{Systems Engineering Approach:}  
    Present a holistic framework illustrating how mission requirements (Section~\ref{sec:req}) flow down into subsystem specifications, ensuring all design choices align with top-level objectives and constraints:
    \begin{itemize}
        \item \textit{Requirements Flowdown}: Show how each subsystem inherits (and meets) one or more system-level requirements. 
        \item \textit{Interfaces}: Define all mechanical, electrical, and data interfaces clearly. Identify critical points of interaction among subsystems (e.g., power lines, data buses, thermal coupling). 
        \item \textit{Integration \& Testing Strategy}: Summarize the high-level plan for subsystem integration and test campaigns (refer to Section~\ref{sec:vv} for Verification \& Validation details).
    \end{itemize}

    \item \textbf{Subsystem Details:}  
    For each major subsystem, emphasize the design rationale—\textit{why} particular components, materials, or architectures were chosen. If leveraging flight-proven heritage, highlight its relevance; if introducing innovation, discuss associated risks and mitigation strategies.
    \begin{itemize}
        \item \textit{Technology Readiness Level (TRL)}: Identify TRLs for any novel technologies and outline the plan to mature them to flight readiness.
        \item \textit{Heritage vs.\ Innovation}: Clearly state when you opt for proven solutions versus new technologies, balancing risk and performance needs.
    \end{itemize}

    \item \textbf{Diagrams \& Tables:}  
    Use clean, well-labeled diagrams to illustrate data flow, power distribution, mechanical layout, and subsystem interconnects. Provide summary tables for:
    \begin{itemize}
        \item \textit{Mass Budgets}: Show breakdowns per subsystem and corresponding margins.
        \item \textit{Power Budgets}: Distinguish between average and peak power demands; note any safe-mode provisions.
        \item \textit{Data Rates}: Summarize instrument output rates and downlink bandwidth allocations.
    \end{itemize}
    Effective visuals let reviewers quickly assess whether your design is balanced, robust, and coherent.
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SECOND BOX (PART 2)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Architecture \& Design: Part 2)]
\begin{itemize}
    \item \textbf{Trade Studies:}  
    For any major design decision (e.g., propulsion method, comm frequency band, thermal control strategy), include a concise comparison of alternatives:
    \begin{itemize}
        \item \textit{Evaluation Criteria}: Typical metrics include mass, cost, reliability, complexity, heritage, schedule, and performance margin.
        \item \textit{Decision Matrix or Trade Tree}: Present your decision-making process, showing how each option was weighed or scored.
        \item \textit{Key Drivers}: Identify the leading factor (e.g., cost, volume constraints, launch availability) that most influenced your final selection.
    \end{itemize}

    \item \textbf{Performance Margins:}  
    Clearly indicate where margins exist (e.g., 20\% mass margin, 15\% power margin) to demonstrate you can accommodate uncertainties. These margins often come under close scrutiny by senior reviewers.

    \item \textbf{Scalability \& Growth:}  
    Note how this architecture might be adapted for future missions or follow-ons. If relevant, emphasize modularity (ease of adding instruments, upgrading subsystems) and compatibility with multiple launch vehicles or mission profiles.
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SPACECRAFT BUS OVERVIEW
%-------------------------------------------
\subsection{Spacecraft Bus Overview}
\noindent
Outline how core elements of the spacecraft bus operate together to meet mission requirements and environmental challenges.

\begin{itemize}
    \item \textbf{Structure \& Mechanisms}:  
    \begin{itemize}
        \item \textit{Materials}: (e.g., aluminum honeycomb, composite panels), mechanical stiffness, and fundamental frequency.
        \item \textit{Deployables}: Solar arrays, booms, antenna reflectors—specify deployment mechanisms and expected reliability.
        \item \textit{Mass Budget}: Highlight margin policies, especially for uncertain aspects like harness growth.
    \end{itemize}

    \item \textbf{ADCS (Attitude Determination \& Control System)}:  
    \begin{itemize}
        \item \textit{Sensors}: Star trackers, inertial measurement units, sun sensors, magnetometers.
        \item \textit{Actuators}: Reaction wheels, thrusters, or control moment gyroscopes. 
        \item \textit{Pointing Requirements}: State pointing accuracy/stability (e.g., \(\pm 0.1^\circ\)) and reorientation frequency for comm or science ops.
    \end{itemize}

    \item \textbf{Power System}:  
    \begin{itemize}
        \item \textit{Generation}: Solar array design (rigid vs.\ flexible, cell efficiency), expected degradation in the mission environment.
        \item \textit{Energy Storage}: Battery type (e.g., Li-ion), capacity, charge/discharge cycles and depth-of-discharge limits.
        \item \textit{Distribution}: Power buses, redundancy approach, peak-load handling, and fault management architecture.
    \end{itemize}

    \item \textbf{Thermal Control}:  
    \begin{itemize}
        \item \textit{Passive Elements}: Multi-layer insulation (MLI), radiators, heat straps, coatings.
        \item \textit{Active Elements}: Heaters, louvers, or fluid loops (if required by instrument sensitivity).
        \item \textit{Thermal Margins}: Summarize hot/cold case analyses, survival heaters, and any special constraints (e.g., cryogenic).
    \end{itemize}

    \item \textbf{Command \& Data Handling (C\&DH)}:  
    \begin{itemize}
        \item \textit{Onboard Computer}: Processing capability, fault tolerance (e.g., dual-string redundancy), watchdog systems.
        \item \textit{Data Bus}: Architecture (e.g., SpaceWire, CAN, Ethernet) for subsystem communications.
        \item \textit{Onboard Storage}: Memory size, expected data volume, compression algorithms, and buffer management.
    \end{itemize}

    \item \textbf{Communications}:  
    \begin{itemize}
        \item \textit{Frequency Bands}: S-, X-, or Ka-band, plus rationale (throughput vs.\ antenna size, ground station network).
        \item \textit{Hardware}: Antenna type (high-gain, low-gain, patch array), transceiver redundancy, traveling wave tube amplifiers (TWTAs) if needed.
        \item \textit{Link Budgets}: Nominal vs.\ worst-case scenarios, link margin, achievable contact time per orbit.
    \end{itemize}
\end{itemize}

%-------------------------------------------
% PAYLOAD / INSTRUMENTS
%-------------------------------------------
\subsection{Payload/Instruments}
\noindent
Summarize the instruments (or payload suite) central to achieving the mission’s science or technology demonstration goals.

\begin{itemize}
    \item \textbf{Instrument A}:  
    \begin{itemize}
        \item \textit{Measurement Principle}: (e.g., spectrometer, camera, sensor array), unique capabilities, expected data rates.
        \item \textit{Interface Requirements}: Input power, data throughput, mechanical constraints (size/weight).
        \item \textit{Data Volume}: Estimated daily or per-orbit output to inform downlink planning.
    \end{itemize}

    \item \textbf{Instrument B}:  
    \begin{itemize}
        \item \textit{Sensitivity \& Dynamic Range}: (e.g., wavelength coverage, signal-to-noise ratio).
        \item \textit{Operating Modes}: Include nominal science mode, calibration mode, standby, etc.
        \item \textit{Thermal/Mechanical Constraints}: Required alignment or thermal stability (e.g., stable to \(\pm\SI{1}{\celsius}\)).
    \end{itemize}
\end{itemize}

%-------------------------------------------
% TRADE STUDIES
%-------------------------------------------
\subsection{Trade Studies}
\noindent
Reinforce your design decisions with a structured set of trade studies:

\begin{itemize}
    \item \textbf{Propulsion}:  
    Compare chemical and electric propulsion (e.g., ion, Hall thrusters) in terms of mass efficiency, mission duration impacts, integration complexity, and heritage flight data.
    
    \item \textbf{Communication Band}:  
    Contrast S-, X-, and Ka-band for data throughput, antenna size, ground station compatibility, and link margins.

    \item \textbf{Thermal Approach}:  
    Weigh purely passive solutions (MLI, radiators) vs.\ active methods (fluid loops, cryocoolers) considering reliability, power draw, and instrument temperature stability needs.
\end{itemize}

\noindent
By substantiating these decisions with quantitative comparisons, you exhibit rigorous systems engineering—a key factor in earning reviewer confidence and ensuring mission success.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 6. VERIFICATION AND VALIDATION (V&V)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Verification and Validation (V\&V)}
\label{sec:vv}

%-------------------------------------------
% BOX 1: V&V EXPLANATION (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (V\&V: Part 1)]
\begin{itemize}
    \item \textbf{Verification vs.\ Validation:}
    \begin{itemize}
        \item \textit{Verification} – “Did we build it right?” Ensures the design and its implementation comply with all specified requirements (Section~\ref{sec:req}).
        \item \textit{Validation} – “Did we build the right thing?” Confirms that the final product meets mission objectives and stakeholder needs.
    \end{itemize}

    \item \textbf{Overview of Methods:}
    \begin{itemize}
        \item \textit{Test}: Physical qualification (e.g., thermal vacuum, vibration, EMI/EMC).
        \item \textit{Analysis}: Numerical simulations (FEA, orbital modeling) and analytical calculations (power budgets, link budgets).
        \item \textit{Inspection}: Physical checks for dimensional conformance, workmanship, and interface compatibility.
        \item \textit{Demonstration}: Controlled environment operation of deployables or critical software routines.
    \end{itemize}

    \item \textbf{Planning \& Coordination:}
    \begin{itemize}
        \item Develop a master test schedule aligned with design review milestones (e.g., SRR, PDR, CDR).
        \item Connect major V\&V milestones (qualification, acceptance) with requirement closure or risk retirement.
    \end{itemize}

    \item \textbf{Instruments \& Calibration:}
    \begin{itemize}
        \item Define calibration protocols referencing recognized standards (e.g., NIST-traceable).
        \item Outline in-flight calibration or alignment checks to ensure ongoing data quality.
    \end{itemize}

        \item \textbf{Documentation:}
    \begin{itemize}
        \item Maintain a dedicated V\&V Plan or “Compliance Matrix” tracking each requirement to at least one verification method.
        \item Document all test results in formal test reports—essential for design reviews and audits.
    \end{itemize}

        \item \textbf{Lifecycle Integration:}
    \begin{itemize}
        \item Include V\&V steps early in the design phase to catch issues prior to final integration.
        \item Consider \textit{protoflight} or \textit{engineering model} approaches if resources limit multiple test units.
    \end{itemize}
    
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% VERIFICATION APPROACH
%-------------------------------------------
\subsection{Verification Approach}
\noindent
Verification activities confirm that each subsystem and component \textit{meets the design requirements}:

\begin{itemize}
    \item \textbf{Inspection}:  
    \begin{itemize}
        \item Dimensional checks of mechanical parts, harness routing, and mechanical interfaces.
        \item Verification of workmanship (e.g., solder joints, bonding, fastener torque).
        \item Compliance checks against Interface Control Documents (ICDs).
    \end{itemize}

    \item \textbf{Analysis}:  
    \begin{itemize}
        \item Structural Finite Element Analysis (FEA) for predicted stresses, strains, and modes.
        \item Orbital simulations to confirm \(\Delta v\) and mission duration feasibility.
        \item Link budget calculations to ensure communication margins under worst-case scenarios.
    \end{itemize}

    \item \textbf{Demonstration}:  
    \begin{itemize}
        \item Functional deployment tests for solar arrays, booms, or antenna reflectors in a representative environment.
        \item Operational demonstration of autonomous features or on-board software routines in a testbed.
    \end{itemize}

    \item \textbf{Test}:  
    \begin{itemize}
        \item \textit{Vibration \& Shock}: Validate launch survivability with sine, random, and shock spectra matching the launch vehicle envelope.
        \item \textit{Thermal Vacuum (TVAC)}: Confirm thermal performance and material outgassing in space-like conditions.
        \item \textit{EMI/EMC}: Test subsystem electromagnetic compatibility and compliance with relevant frequency regulations.
    \end{itemize}
\end{itemize}

%-------------------------------------------
% VALIDATION APPROACH
%-------------------------------------------
\subsection{Validation Approach}
\noindent
Validation ensures the \textit{fully integrated system} meets higher-level mission objectives and end-user needs:

\begin{itemize}
    \item \textbf{Mission Simulations}:  
    \begin{itemize}
        \item Hardware-in-the-loop (HIL) or software-in-the-loop (SIL) exercises to replicate operational scenarios.
        \item Identify command sequence issues or fault scenarios before launch.
    \end{itemize}

    \item \textbf{Instrument Calibration}:  
    \begin{itemize}
        \item \textit{Pre-Launch}: Validate instrument accuracy and performance against reference standards in the lab.
        \item \textit{Post-Launch}: Execute in-orbit calibration using known celestial or terrestrial references; cross-compare readings if multiple sensors overlap in coverage.
    \end{itemize}

    \item \textbf{Data Quality Checks}:  
    \begin{itemize}
        \item Regularly compare returned data against expected performance envelopes (e.g., SNR targets, resolution bounds).
        \item Investigate anomalies (sensor drift, unexpected offsets) swiftly to preserve data integrity.
    \end{itemize}
\end{itemize}



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 7. DATA MANAGEMENT PLAN (DMP)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Data Management Plan (DMP)}
\label{sec:dmp}

\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Data Management Plan)]
\begin{itemize}
    \item \textbf{Purpose:} NASA mandates that all mission data be archived in publicly accessible repositories, fostering open science and maximizing the scientific return on investment.
    \item \textbf{Best Practices:}
    \begin{itemize}
        \item Clearly outline how data will be collected, processed, archived, and made accessible.
        \item Specify which standards (e.g., FITS, SPICE) will be used to ensure compatibility and longevity.
        \item Provide timelines for data release to the public and indicate any embargo periods, if applicable.
        \item Detail the budget allocated to data curation and dissemination.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

\subsection{Data Collection and Formats}
\noindent Mission data will be collected using \textit{[instruments]} and processed according to NASA’s data standards. All raw and calibrated data will be formatted in compliance with the Flexible Image Transport System (FITS) and/or SPICE standards.

\begin{itemize}
    \item \textbf{Science Data Products:} Raw data, calibrated datasets, and higher-level derived products will be stored in standardized formats with accompanying metadata.
    \item \textbf{Instrument Telemetry:} Archived in binary and decoded formats for operational analysis and public accessibility.
\end{itemize}

\subsection{Archiving and Dissemination}
\noindent The \textit{[Mission Name]} team commits to archiving all mission data in NASA’s Planetary Data System (PDS) or a similar NASA-endorsed repository.

\begin{itemize}
    \item \textbf{Archiving Plan:}
    \begin{itemize}
        \item All data products will be deposited in \textit{[repository name]} within \SI{6}{months} of acquisition.
        \item Metadata will adhere to \textit{[standard, e.g., PDS4]} to ensure discoverability.
    \end{itemize}
    \item \textbf{Access:} Data will be available via NASA’s public repositories with no restrictions after \textit{[embargo duration, if any]}.
\end{itemize}

\subsection{Long-Term Stewardship}
\noindent A dedicated data management team will oversee the archiving, quality control, and long-term accessibility of mission data:
\begin{itemize}
    \item Annual reviews will ensure all archived data meet NASA standards for completeness and accuracy.
    \item Budget for data stewardship is allocated at \textit{[amount]} over the mission’s lifespan.
\end{itemize}



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 8. SUSTAINABILITY AND ENVIRONMENTAL COMPLIANCE
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Sustainability and Environmental Compliance}
\label{sec:env_compliance}

\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Sustainability and Environmental Compliance)]
\begin{itemize}
    \item \textbf{Purpose:} Ensure mission compliance with international sustainability standards (ISO 24113, COSPAR) while addressing environmental concerns associated with space operations.
    \item \textbf{Best Practices:}
    \begin{itemize}
        \item Prioritize ISO-compliant debris mitigation plans to minimize long-term space hazards.
        \item Adhere to COSPAR planetary protection policies to preserve the integrity of celestial bodies.
        \item Integrate sustainability in all mission phases, from launch to decommissioning.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

\subsection{Space Debris Mitigation}
\noindent The \textit{[Mission Name]} design fully adheres to ISO 24113 standards for orbital debris mitigation:
\begin{itemize}
    \item \textbf{Collision Avoidance:} Utilize real-time conjunction alerts from \textit{[e.g., Space Surveillance Network (SSN)]} and implement autonomous collision avoidance maneuvers.
    \item \textbf{Post-Mission Disposal:} Employ a controlled deorbit strategy, ensuring the spacecraft re-enters the atmosphere within 25 years of mission end.
    \item \textbf{Passive Mitigation Features:} Design deployables and structural elements to reduce fragmentation risk during collisions.
\end{itemize}

\subsection{Planetary Protection}
\noindent The mission complies with COSPAR guidelines based on the nature of its objectives:
\begin{itemize}
    \item \textbf{Mission Categorization:} Designated as \textit{[COSPAR Category]} for its destination and potential contamination risks.
    \item \textbf{Sterilization Procedures:} Critical hardware exposed to extraterrestrial environments will undergo heat sterilization and bioassay testing to meet contamination thresholds.
    \item \textbf{Verification:} Pre-launch inspections will ensure adherence to sterilization and cleanliness requirements.
\end{itemize}

\subsection{Sustainability in Operations}
\begin{itemize}
    \item \textbf{Energy Efficiency:} Use high-efficiency solar cells and low-power components to minimize energy demands during the mission.
    \item \textbf{Launch Impact Reduction:} Partner with a launch provider employing sustainable fuels or emissions reduction technologies.
    \item \textbf{Ground Segment Sustainability:} Operate from green-certified facilities that meet energy efficiency and waste management standards.
\end{itemize}

\subsection{Compliance Monitoring}
\noindent The mission team will appoint an Environmental Compliance Officer to oversee adherence to sustainability and protection standards:
\begin{itemize}
    \item Regular audits will ensure continued compliance with ISO 24113 and COSPAR policies.
    \item A final compliance report will be submitted to \textit{[e.g., NASA, ESA]} at the mission’s conclusion.
\end{itemize}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 9. RISK MANAGEMENT
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Risk Management}
\label{sec:risk}

%-------------------------------------------
% FIRST BOX: RISK MANAGEMENT EXPLANATION (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Risk Management: Part 1)]
\begin{itemize}
    \item \textbf{Risk Register:} 
    \begin{itemize}
        \item \textit{Living Document:} Maintain an up-to-date risk register that captures each risk’s description, likelihood, impact, mitigation strategy, and current status. This ensures continuous monitoring and proactive management.
        \item \textit{Ownership:} Assign a dedicated owner to each risk to ensure accountability and timely mitigation. Owners are responsible for monitoring risk indicators and implementing mitigation actions.
    \end{itemize}
    
    \item \textbf{Risk Classification:}  
    Categorize risks to streamline identification and mitigation efforts. Common categories include:
    \begin{itemize}
        \item \textit{Technical Risks}: Potential failures in hardware, software, or performance shortfalls that could impede mission success.
        \item \textit{Programmatic Risks}: Issues related to budget constraints, resource allocation, and shifting sponsor priorities.
        \item \textit{Schedule Risks}: Delays in testing, integration, or supplier deliveries that could affect the overall timeline.
        \item \textit{Safety Risks}: Hazards associated with launch operations, propellant handling, and on-orbit activities that could threaten mission or personnel safety.
    \end{itemize}

    \item \textbf{Mitigation Strategies:}  
    Develop robust strategies to minimize the probability and impact of identified risks:
    \begin{itemize}
        \item \textit{Redundancy}: Incorporate backup systems for critical subsystems to ensure continued functionality in case of primary system failure.
        \item \textit{Early Prototyping}: Build and test prototypes early to identify and rectify design flaws before full-scale development.
        \item \textit{Alternate Suppliers}: Secure multiple suppliers for critical components to mitigate the risk of supply chain disruptions.
        \item \textit{Contingency Reserves}: Allocate additional budget and schedule buffers to address unforeseen issues without jeopardizing mission timelines.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SECOND BOX: RISK MANAGEMENT EXPLANATION (PART 2)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Risk Management: Part 2)]
\begin{itemize}
    \item \textbf{Proactive vs.\ Reactive Management:}  
    \begin{itemize}
        \item \textit{Proactive Monitoring}: Continuously track leading indicators such as test anomalies, supplier performance, and schedule adherence to identify potential risks early.
        \item \textit{Reactive Response}: Develop predefined action plans to address risks once they materialize, minimizing their impact on the mission.
    \end{itemize}
    
    \item \textbf{Regular Updates:}  
    \begin{itemize}
        \item \textit{Milestone Reviews}: Update the risk register at each major program milestone (e.g., System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR)).
        \item \textit{Periodic Assessments}: Conduct regular risk assessment meetings (e.g., monthly or quarterly) to evaluate the status of existing risks and identify new ones.
        \item \textit{Risk Boards}: Establish risk management boards or committees to oversee risk mitigation efforts and make strategic decisions.
    \end{itemize}
    
    \item \textbf{Reference Standards:}  
    \begin{itemize}
        \item \textit{NASA NPR 8000.4}: Adhere to NASA's guidelines for risk management, ensuring systematic identification, assessment, and mitigation of risks.
        \item \textit{ISO 31000}: Implement internationally recognized risk management frameworks to enhance consistency and reliability.
        \item \textit{ECSS-Q-ST-10-02C}: For European missions, follow the ECSS standards for risk management practices.
    \end{itemize}
    
    \item \textbf{Risk Assessment Techniques:}  
    Utilize both qualitative and quantitative methods to evaluate risks effectively:
    \begin{itemize}
        \item \textit{Qualitative Analysis}: Use expert judgment and historical data to assess the likelihood and impact of risks.
        \item \textit{Quantitative Analysis}: Apply statistical methods and modeling to quantify risk probabilities and potential impacts on mission objectives.
    \end{itemize}
    
    \item \textbf{Communication and Documentation:}  
    \begin{itemize}
        \item \textit{Transparent Reporting}: Ensure that all stakeholders are informed about current risks, their status, and mitigation actions.
        \item \textit{Comprehensive Documentation}: Maintain detailed records of risk identification, assessment, mitigation strategies, and outcomes to support decision-making and future mission planning.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% RISK IDENTIFICATION
%-------------------------------------------
\subsection{Risk Identification}
\noindent
Effective risk identification leverages historical mission data, lessons learned, and expert judgment to uncover potential challenges. Utilize a 5x5 Risk Matrix (Table~\ref{tab:risk_matrix}) to grade each risk by \textbf{likelihood} (1=Rare, 5=Almost Certain) and \textbf{consequence} (1=Negligible, 5=Catastrophic):

\begin{table}[h!]
\small
\centering
\caption{Generic 5x5 Risk Matrix (Color-Coded for Emphasis)}
\label{tab:risk_matrix}
\begin{tabular}{c|ccccc}
\toprule
 & \multicolumn{5}{c}{\textbf{Consequence}} \\
\textbf{Likelihood} & 1 & 2 & 3 & 4 & 5 \\
\midrule
1 (Rare) & \cellcolor{green!20}Low & \cellcolor{green!20}Low & \cellcolor{green!20}Low & \cellcolor{yellow!20}Moderate & \cellcolor{orange!20}High \\
2 (Unlikely) & \cellcolor{green!20}Low & \cellcolor{green!20}Low & \cellcolor{yellow!20}Moderate & \cellcolor{orange!20}High & \cellcolor{red!20}Critical \\
3 (Possible) & \cellcolor{green!20}Low & \cellcolor{yellow!20}Moderate & \cellcolor{orange!20}High & \cellcolor{red!20}Critical & \cellcolor{red!20}Critical \\
4 (Likely) & \cellcolor{yellow!20}Moderate & \cellcolor{orange!20}High & \cellcolor{orange!20}High & \cellcolor{red!20}Critical & \cellcolor{red!50}Critical \\
5 (Almost Certain) & \cellcolor{orange!20}High & \cellcolor{orange!20}High & \cellcolor{red!20}Critical & \cellcolor{red!50}Critical & \cellcolor{red!50}Critical \\
\bottomrule
\end{tabular}
\end{table}

\noindent
Green boxes indicate low or acceptable risk (monitor only), yellow/orange reflect moderate risk (active tracking/mitigation), and red highlights high-priority risk (requires immediate action).

%-------------------------------------------
% EXAMPLE RISK REGISTER
%-------------------------------------------
\subsection{Example Risk Register for a Deep-Space Mission}
\noindent
The sample in Table~\ref{tab:risk_register} illustrates typical entries for a deep-space mission:

\begin{table}[h!]
\scriptsize
\renewcommand{\arraystretch}{1.2}
\centering
\caption{Sample Risk Register (Hypothetical Deep-Space Mission)}
\label{tab:risk_register}
\begin{tabular}{@{}p{0.8cm}p{3.0cm}p{1.2cm}p{1.5cm}p{6.5cm}@{}}
\toprule
\textbf{Risk ID} & \textbf{Risk Description} & \textbf{LxC} & \textbf{Risk Level} & \textbf{Mitigation} \\
\midrule
\textbf{R-01} & Reaction wheel bearing failure & 2 x 4 & Medium-High &
\begin{tabular}[c]{@{}l@{}}
- Incorporate redundant reaction wheels \\
- Conduct rigorous vibration and endurance testing \\
- Implement on-orbit diagnostics and fault-tolerance algorithms
\end{tabular} \\
\midrule
\textbf{R-02} & Late propulsion subsystem delivery & 3 x 3 & Medium &
\begin{tabular}[c]{@{}l@{}}
- Secure contracts with multiple suppliers \\
- Initiate early prototyping and component testing \\
- Allocate schedule buffers to accommodate delays
\end{tabular} \\
\midrule
\textbf{R-03} & Propellant leak or valve failure & 1 x 5 & Medium &
\begin{tabular}[c]{@{}l@{}}
- Implement stringent quality assurance for seals and lines \\
- Perform comprehensive pressure testing pre-integration \\
- Design mission fallback options (e.g., limited maneuvering)
\end{tabular} \\
\midrule
\textbf{R-04} & Insufficient data rate from deep space & 2 x 5 & High &
\begin{tabular}[c]{@{}l@{}}
- Utilize high-gain antennas with adaptive pointing \\
- Secure dedicated Deep Space Network (DSN) support during critical operations \\
- Implement onboard data compression and error-correction algorithms
\end{tabular} \\
\midrule
\textbf{R-05} & Software bugs in autonomous navigation system & 3 x 4 & High &
\begin{tabular}[c]{@{}l@{}}
- Conduct extensive software testing and validation \\
- Implement redundancy in critical software modules \\
- Establish robust fault-detection and recovery protocols
\end{tabular} \\
\midrule
\textbf{R-06} & Thermal control subsystem failure & 2 x 5 & High &
\begin{tabular}[c]{@{}l@{}}
- Design with multiple thermal control redundancies \\
- Perform thermal vacuum testing under extreme conditions \\
- Monitor thermal performance continuously with onboard sensors
\end{tabular} \\
\bottomrule
\end{tabular}
\end{table}

%-------------------------------------------
% RISK MITIGATION
%-------------------------------------------
\subsection{Risk Mitigation}
\noindent
Implementing effective mitigation practices ensures the mission can adapt to unforeseen challenges:

\begin{itemize}
    \item \textbf{Technical Redundancies}:  
    \begin{itemize}
        \item Duplicate essential hardware such as reaction wheels, transceivers, and power sources to provide backup in case of primary system failures.
        \item Design systems with fail-safes and fallback modes to maintain functionality during partial system outages.
    \end{itemize}
    
    \item \textbf{Rigorous Testing}:  
    \begin{itemize}
        \item Conduct comprehensive subsystem-level qualifications, including thermal, vibration, EMI/EMC, and functional tests to validate design margins.
        \item Implement environmental testing (e.g., thermal vacuum, acoustic) to simulate space conditions and ensure subsystem resilience.
    \end{itemize}
    
    \item \textbf{Schedule \& Budget Reserves}:  
    \begin{itemize}
        \item Allocate contingency funds and schedule buffers to address potential test failures, redesign cycles, or unforeseen technical challenges.
        \item Prioritize critical path activities and monitor closely to prevent cascading delays.
    \end{itemize}
    
    \item \textbf{Operational Contingencies}:  
    \begin{itemize}
        \item Develop and document Fault Detection, Isolation, and Recovery (FDIR) protocols to manage and mitigate operational anomalies.
        \item Define fallback modes or partial success scenarios to maintain mission objectives even under suboptimal conditions.
        \item Train mission control teams on contingency procedures and ensure clear communication channels for rapid decision-making.
    \end{itemize}
    
    \item \textbf{Continuous Monitoring and Review}:  
    \begin{itemize}
        \item Implement real-time monitoring systems to track risk indicators and trigger mitigation actions when thresholds are breached.
        \item Conduct regular risk reviews and update the risk register to reflect the current mission status and emerging risks.
    \end{itemize}
    
    \item \textbf{Stakeholder Engagement}:  
    \begin{itemize}
        \item Involve key stakeholders in risk identification and mitigation planning to leverage diverse expertise and ensure comprehensive coverage.
        \item Maintain transparent communication with sponsors, partners, and regulatory bodies regarding risk status and management strategies.
    \end{itemize}
\end{itemize}

\noindent
By systematically identifying, assessing, and mitigating risks, the mission team can proactively address potential challenges, ensuring mission objectives are achieved within budget and schedule constraints. Adhering to established risk management frameworks and continuously refining strategies based on evolving project dynamics fortifies the mission's resilience and success.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 10. SCHEDULE AND BUDGET
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Schedule and Budget}
\label{sec:schedule_budget}

%-------------------------------------------
% FIRST BOX: SCHEDULE & BUDGET EXPLANATION (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Schedule \& Budget: Part 1)]
\begin{itemize}
    \item \textbf{Realistic Timeline:} 
    \begin{itemize}
        \item Develop a comprehensive timeline that outlines all major mission phases from design to decommissioning.
        \item Incorporate schedule margins to account for potential delays, ensuring flexibility without compromising mission integrity.
    \end{itemize}
    
    \item \textbf{Milestones \& Reviews:}  
    \begin{itemize}
        \item Identify and highlight critical milestones such as System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), and Launch Readiness Review (LRR).
        \item Define key deliverables and decision points that align with these milestones to facilitate structured progress tracking and accountability.
    \end{itemize}
    
    \item \textbf{Use of Visual Aids:} 
    \begin{itemize}
        \item Utilize Gantt charts, milestone charts, or timeline diagrams to visually communicate the project schedule.
        \item Supplement visual aids with concise tables that provide quick reference points for major activities and their timelines.
    \end{itemize}
    
    \item \textbf{Work Breakdown Structure (WBS):} 
    \begin{itemize}
        \item Develop a detailed WBS that decomposes the mission into manageable sections, allocating resources (cost and labor) across each mission element (e.g., spacecraft bus, payload, ground segment).
        \item Ensure the WBS aligns with project objectives and facilitates effective cost tracking and management.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SECOND BOX: SCHEDULE & BUDGET EXPLANATION (PART 2)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Schedule \& Budget: Part 2)]
\begin{itemize}
    \item \textbf{Identify Reserves:}  
    \begin{itemize}
        \item Allocate cost and schedule reserves (typically 10–30\%) to mitigate unforeseen challenges or risks identified in Section~\ref{sec:risk}.
        \item Clearly justify the size and management of reserves, ensuring they are sufficient to cover potential overruns without excessive padding.
    \end{itemize}
    
    \item \textbf{Alignment to Funding Profiles:}  
    \begin{itemize}
        \item Map budget allocations to the sponsor’s funding windows, ensuring that financial needs align with available funding phases or milestones.
        \item Illustrate how phased or multi-source funding will support different mission phases, demonstrating financial feasibility and strategic resource management.
    \end{itemize}
    
    \item \textbf{Contingency Planning:}  
    \begin{itemize}
        \item Develop contingency plans for both budget and schedule, detailing how deviations will be managed to minimize impact on mission objectives.
        \item Incorporate flexibility in project management practices to adapt to changing circumstances without compromising key deliverables.
    \end{itemize}
    
    \item \textbf{Continuous Monitoring and Adjustment:}  
    \begin{itemize}
        \item Implement robust monitoring systems to track budget expenditures and schedule adherence in real-time.
        \item Regularly review and adjust the schedule and budget based on project progress, emerging risks, and stakeholder feedback.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% PROJECT SCHEDULE
%-------------------------------------------
\subsection{Project Schedule}
\noindent
Provide a detailed overview of the project’s schedule, outlining each phase and its corresponding milestones. Visual aids such as Gantt charts are highly recommended to enhance clarity and engagement.

\begin{figure}[h!]
    \centering
    \resizebox{\textwidth}{!}{%
    \begin{tikzpicture}
        \begin{ganttchart}[
            hgrid,
            vgrid,
            time slot format=isodate-year,
            compress calendar,
            milestone/.append style={fill=red},
            bar/.append style={fill=blue!50},
            bar height=.6,
            group label font=\bfseries\small\color{black},
            milestone label font=\bfseries\small\color{black},
            bar label font=\scriptsize\color{black},
            milestone label font=\scriptsize\color{black},
            time slot unit=year,
            x unit=2cm, % Adjusted for yearly slots
            y unit title=0.4cm,
            y unit chart=0.5cm,
            title height=1,
            title/.style={fill=none},
            ]{2025}{2028}
            \gantttitlecalendar{year} \\
            \ganttgroup{Phase A:\\ Conceptual Design}{2025}{2025} \\
            \ganttbar[bar label font=\scriptsize]{SRR}{2025}{2025} \\
            \ganttgroup{Phase B:\\ Preliminary Design}{2026}{2026} \\
            \ganttbar[bar label font=\scriptsize]{PDR}{2026}{2026} \\
            \ganttgroup{Phase C:\\ Detailed Design \& Fabrication}{2026}{2027} \\
            \ganttbar[bar label font=\scriptsize]{CDR}{2027}{2027} \\
            \ganttgroup{Phase D:\\ Assembly, Integration \& Test}{2027}{2027} \\
            \ganttbar[bar label font=\scriptsize]{LRR}{2027}{2027} \\
            \ganttgroup{Phase E:\\ Operations}{2028}{2028} \\
            \ganttmilestone[milestone label font=\scriptsize]{Launch}{2028} \\
        \end{ganttchart}
    \end{tikzpicture}
    }
    \caption{High-Level Project Schedule}
    \label{fig:gantt_chart}
\end{figure}

\noindent
\textbf{Sample High-Level Timeline}:
\begin{enumerate}
    \item \textbf{Phase A} (Conceptual Design): 6--9 months
    \item \textbf{Phase B} (Preliminary Design): 9--12 months
    \item \textbf{Phase C} (Detailed Design \& Fabrication): 12--18 months
    \item \textbf{Phase D} (Assembly, Integration, \& Test): 12--18 months
    \item \textbf{Phase E} (Operations): 2--5 years (depending on mission scope)
\end{enumerate}

%-------------------------------------------
% COST ESTIMATE
%-------------------------------------------
\subsection{Cost Estimate}
\noindent
A structured \textbf{Work Breakdown Structure (WBS)} is essential for budgeting, enabling precise allocation of costs across mission subsystems, project management, and ground operations. Below is an example breakdown (values in \$M). Adjust categories and amounts to fit your specific proposal.

\begin{table}[h!]
\scriptsize
\centering
\caption{Example Budget by Phase (in \$M)}
\renewcommand{\arraystretch}{1.2}
\label{tab:budget_example}
\begin{tabular}{@{}lccccc@{}}
\toprule
\textbf{WBS Element} & \textbf{Phase A} & \textbf{Phase B} & \textbf{Phase C} & 
\textbf{Phase D} & \textbf{Phase E} & \textbf{Total} \\
\midrule
Project Management & 1.0 & 2.0 & 2.5 & 3.0 & 1.5 & 10.0 \\
Spacecraft Bus & 2.0 & 5.0 & 20.0 & 25.0 & 5.0 & 57.0 \\
Payload & 2.5 & 7.0 & 10.0 & 12.0 & 4.0 & 35.5 \\
Launch Vehicle & - & - & - & 40.0 & - & 40.0 \\
Ground Segment & 0.5 & 1.0 & 1.5 & 2.0 & 2.0 & 7.0 \\
\midrule
\textbf{Total} & 6.0 & 15.0 & 34.0 & 82.0 & 12.5 & 149.5 \\
\bottomrule
\end{tabular}
\end{table}

\noindent
\textbf{Key Points:}
\begin{itemize}
    \item \textbf{Management Costs:} Includes program offices, contract management, safety assurance, and systems engineering.
    \item \textbf{Spacecraft Bus:} Often the largest cost driver, encompassing propulsion, power, ADCS, thermal, and C\&DH subsystems.
    \item \textbf{Payload:} Science instruments or technology demonstration units; costs vary based on TRL and complexity.
    \item \textbf{Launch Vehicle:} Significant portion of total mission cost; consider smallsat rideshare options if feasible.
    \item \textbf{Ground Segment:} Covers mission operations, ground stations, data processing centers, and communication network fees.
\end{itemize}

%-------------------------------------------
% RESERVES AND CONTINGENCY
%-------------------------------------------
\subsection{Reserves and Contingency}
\noindent
Funding agencies such as NASA and ESA typically expect \textbf{risk-adjusted reserves} to account for unforeseen technical challenges or schedule slips, ranging from 10\% to 30\% of the total budget. Provide a clear justification for the sizing and management of these reserves:

\begin{itemize}
    \item \textbf{Cost Reserves:} Allocate a specific percentage of the total budget to handle unexpected expenses, such as component failures, scope changes, or additional testing requirements.
    \item \textbf{Schedule Reserves:} Incorporate buffer time within each mission phase to accommodate potential delays without impacting critical milestones.
    \item \textbf{Management Reserves:} Set aside contingency funds and time for high-impact risks identified in the risk register (Section~\ref{sec:risk}).
\end{itemize}

\noindent
\textbf{Example Allocation:}
\begin{itemize}
    \item \textbf{Total Budget}: \$149.5M
    \item \textbf{Cost Reserve (15\%)}: \$22.4M
    \item \textbf{Schedule Reserve}: 10\% buffer on total timeline (additional 1-2 months)
\end{itemize}

%-------------------------------------------
% FUNDING PROFILE ALIGNMENT
%-------------------------------------------
\subsection{Funding Profile Alignment}
\noindent
If external funding is provided in discrete increments (e.g., annual budgets, milestone-based releases), explicitly map budget allocations to the sponsor’s funding windows to demonstrate financial feasibility:

\begin{itemize}
    \item \textbf{Phase Funding Windows}: 
    \begin{itemize}
        \item Align each mission phase’s expenditures with the sponsor’s fiscal calendar or funding milestones.
        \item Ensure that key deliverables coincide with funding release points to secure continuous financial support.
    \end{itemize}
    
    \item \textbf{Payment Milestones}: 
    \begin{itemize}
        \item Connect significant deliverables (e.g., completion of PDR, arrival of critical hardware) to partial payment releases.
        \item Use contractual milestones to ensure timely funding aligned with project progress.
    \end{itemize}
    
    \item \textbf{Contractual Flexibility}: 
    \begin{itemize}
        \item Describe any agreements in place, such as cost-plus versus fixed-price contract structures, that provide flexibility to adapt to evolving funding realities.
        \item Highlight provisions for budget adjustments or scope modifications based on funding availability and mission requirements.
    \end{itemize}
\end{itemize}

\noindent
\textbf{Sample Funding Profile Alignment}:
\begin{itemize}
    \item \textbf{Phase A (Conceptual Design)}: Funded by initial grant release, covering preliminary studies and requirement definitions.
    \item \textbf{Phase B (Preliminary Design)}: Secured through milestone-based payments tied to the successful completion of PDR.
    \item \textbf{Phase C \& D (Detailed Design \& Fabrication \& Assembly, Integration, \& Test)}: Funded through subsequent budget releases, aligned with CDR and LRR milestones.
    \item \textbf{Phase E (Operations)}: Supported by operational funds or follow-on grants, ensuring sustained mission activities.
\end{itemize}

\noindent
By clearly presenting a realistic schedule, milestone plan, and cost breakdown aligned with the mission’s technical scope and funding profiles, you provide decision-makers with a transparent and confidence-inspiring roadmap for resource allocation and mission execution.

%-------------------------------------------
% WORK BREAKDOWN STRUCTURE (OPTIONAL)
%-------------------------------------------
\subsection{Work Breakdown Structure (WBS)}
\noindent
A detailed \textbf{Work Breakdown Structure (WBS)} facilitates precise cost allocation and resource management. Below is an enhanced example that decomposes the mission into hierarchical elements:

\begin{table}[h!]
\scriptsize
\centering
\caption{Enhanced Work Breakdown Structure (WBS)}
\renewcommand{\arraystretch}{1.2}
\label{tab:wbs}
\begin{tabular}{@{}llcp{3cm}@{}}
\toprule
\textbf{WBS Code} & \textbf{Element} & \textbf{Description} & \textbf{Cost (\$M)} \\ 
\midrule
1.0 & Project Management & Overall program oversight, scheduling, reporting & 10.0 \\
\midrule
2.0 & Spacecraft Bus & Core spacecraft systems and integration & 57.0 \\
\hspace{2mm} 2.1 & Propulsion System & Thrusters, fuel management, delta-v allocation & 15.0 \\
\hspace{2mm} 2.2 & Power System & Solar arrays, batteries, power distribution & 12.0 \\
\hspace{2mm} 2.3 & ADCS & Attitude sensors, actuators, control algorithms & 10.0 \\
\hspace{2mm} 2.4 & Thermal Control & Passive/active thermal systems, insulation & 10.0 \\
\hspace{2mm} 2.5 & C\&DH & Onboard computers, data buses, storage systems & 10.0 \\
\midrule
3.0 & Payload & Science instruments or technology demonstrators & 35.5 \\
\hspace{2mm} 3.1 & Instrument A & Spectrometer, data acquisition & 15.0 \\
\hspace{2mm} 3.2 & Instrument B & Imaging system, calibration tools & 10.0 \\
\hspace{2mm} 3.3 & Integration & Payload integration and testing & 10.5 \\
\midrule
4.0 & Launch Vehicle & Vehicle acquisition and integration & 40.0 \\
\midrule
5.0 & Ground Segment & Mission operations, data processing & 7.0 \\
\hspace{2mm} 5.1 & Operations Center & Command and control infrastructure & 3.0 \\
\hspace{2mm} 5.2 & Ground Stations & Communication links, data downlink facilities & 2.0 \\
\hspace{2mm} 5.3 & Data Processing & Data analysis and storage systems & 2.0 \\
\bottomrule
\end{tabular}
\end{table}

\noindent
\textbf{Advantages of a Detailed WBS:}
\begin{itemize}
    \item \textbf{Enhanced Cost Tracking}: Facilitates precise monitoring of expenditures across all mission elements.
    \item \textbf{Resource Allocation}: Ensures optimal distribution of labor and materials, preventing over-allocation or under-utilization.
    \item \textbf{Transparency}: Provides clear visibility into project structure and financial commitments, aiding stakeholder confidence.
\end{itemize}

\noindent
Ensure that your WBS aligns with both technical requirements and financial constraints, enabling seamless integration with project management and financial tracking systems.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 11. OPTIONAL SECTIONS
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Optional Sections}
\label{sec:optional_sections}

%-------------------------------------------
% FIRST BOX: OPTIONAL SECTIONS EXPLANATION (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Optional Sections: Part 1)]
\begin{itemize}
    \item \textbf{Value-Add Sections:}  
    \begin{itemize}
        \item \textit{Strategic Importance:} Incorporate sections that highlight additional strengths or unique aspects of your mission, addressing emerging priorities or concerns of funding agencies.
        \item \textit{Enhanced Credibility:} Demonstrate comprehensive planning and foresight by covering areas beyond the core mission requirements.
    \end{itemize}
    
    \item \textbf{Use Discretion:}  
    \begin{itemize}
        \item \textit{Page-Limit Compliance:} Prioritize optional sections that offer significant value and align closely with the mission’s unique selling points or mitigate high-impact risks.
        \item \textit{Relevance and Impact:} Focus on sections that reinforce your mission’s strengths, address potential weaknesses, or showcase additional benefits such as societal impact or technological innovation.
    \end{itemize}
    
    \item \textbf{Examples of Optional Sections:}  
    \begin{itemize}
        \item \textit{Technology Readiness Assessment}
        \item \textit{Launch Vehicle \& Ground Segment Details}
        \item \textit{Educational Outreach (EPO) Plan}
        \item \textit{Management Approach and Key Personnel}
        \item \textit{Environmental Compliance}
        \item \textit{Data Management and Sharing Policies}
    \end{itemize}
    \item \textbf{Integration with Core Sections:}  
    \begin{itemize}
        \item Ensure optional sections seamlessly integrate with core sections, providing deeper insights without redundancy.
        \item Reference relevant core sections (e.g., Risk Management, Systems Engineering) to maintain coherence and traceability.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SECOND BOX: OPTIONAL SECTIONS EXPLANATION (PART 2)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Optional Sections: Part 2)]
\begin{itemize}
    \item \textbf{Customization for Audience:}  
    \begin{itemize}
        \item Tailor optional sections to address specific interests or concerns of your target reviewers or stakeholders.
        \item Highlight aspects that differentiate your mission from others, showcasing innovation and leadership.
    \end{itemize}
    
    \item \textbf{Comprehensive Coverage:}  
    \begin{itemize}
        \item Provide sufficient detail to demonstrate thorough planning and expertise without overwhelming the reader.
        \item Use appendices for supplementary information if necessary, keeping the main document concise.
    \end{itemize}
    
    \item \textbf{Professional Presentation:}  
    \begin{itemize}
        \item Maintain consistent formatting, clear headings, and organized layouts for optional sections.
        \item Utilize tables, figures, and diagrams where appropriate to enhance clarity and visual appeal.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% OPTIONAL SUB-SECTIONS
%-------------------------------------------

\subsection{(Optional) Technology Readiness Assessment}
\label{sec:tech_readiness}
\noindent
When the mission relies on technologies at lower Technology Readiness Levels (TRL 3–5), it is crucial to present a clear roadmap for their maturation to ensure flight readiness. This assessment demonstrates your proactive approach to mitigating technological risks and aligning with agency expectations.

\begin{itemize}
    \item \textbf{Ground Demonstrations or Suborbital Tests:}  
    \begin{itemize}
        \item \textit{Planned Test Campaigns:} Detail any planned thermal-vacuum tests, vibration tests, or functional tests that will advance the TRL of critical technologies.
        \item \textit{Test Objectives:} Define specific objectives for each test, such as validating thermal performance, ensuring structural integrity under launch conditions, or verifying autonomous software routines.
        \item \textit{Timeline and Milestones:} Align test campaigns with project phases, indicating when each technology will reach its targeted TRL.
    \end{itemize}
    
    \item \textbf{Target TRL for Flight Readiness:}  
    \begin{itemize}
        \item \textit{Final TRL Requirement:} Specify the required TRL (typically TRL 6 or higher) for each technology at the time of mission integration and launch.
        \item \textit{Milestone-Based Progression:} Outline major milestones for verification and validation that will confirm TRL advancement, such as successful prototype demonstrations or subsystem integration tests.
    \end{itemize}
    
    \item \textbf{Risk Reduction Plans:}  
    \begin{itemize}
        \item \textit{Redundancy and Backup Solutions:} Identify any redundant systems or fallback options in case the primary technology does not achieve the desired TRL.
        \item \textit{Iterative Development:} Describe an iterative approach to technology development, allowing for incremental improvements and timely issue resolution.
        \item \textit{Partnerships and Collaborations:} Highlight collaborations with research institutions, industry partners, or technology providers that enhance technology maturation and reduce risks.
    \end{itemize}
    
    \item \textbf{Technology Heritage:}  
    \begin{itemize}
        \item \textit{Flight-Proven Components:} Where possible, incorporate flight-proven technologies to balance innovation with reliability.
        \item \textit{Lessons Learned:} Reference lessons learned from previous missions or similar technology deployments to inform current development and testing strategies.
    \end{itemize}
\end{itemize}

\subsection{(Optional) Launch Vehicle \& Ground Segment Details}
\noindent
Providing detailed information about the launch vehicle and ground segment underscores your mission’s feasibility and readiness. This section demonstrates your understanding of integration requirements and operational dependencies.

\begin{itemize}
    \item \textbf{Launch Vehicle Constraints:}  
    \begin{itemize}
        \item \textit{Payload Fairing Volume and Mass Limits:} Specify the dimensions and mass constraints imposed by the chosen launch vehicle, ensuring your spacecraft design complies.
        \item \textit{Rideshare Opportunities:} Explore potential rideshare options to optimize launch costs and schedule flexibility. Highlight any pre-negotiated agreements or partnerships.
        \item \textit{Integration Timelines:} Detail the schedule for spacecraft integration with the launch vehicle, including any critical path items that could impact launch dates.
    \end{itemize}
    
    \item \textbf{Integration \& Handling Requirements:}  
    \begin{itemize}
        \item \textit{Cleanroom Specifications:} Describe the cleanroom environments required for spacecraft assembly and integration, adhering to contamination control standards.
        \item \textit{Environmental Test Requirements:} Outline the environmental tests (thermal, vibration, EMI/EMC) needed during integration to validate spacecraft resilience.
        \item \textit{Fueling Procedures:} If applicable, detail the procedures and safety protocols for propellant loading, ensuring compliance with launch vehicle and regulatory requirements.
    \end{itemize}
    
    \item \textbf{Ground Segment Coverage:}  
    \begin{itemize}
        \item \textit{Communication Architecture:} Explain the communication infrastructure, including Deep Space Network (DSN) support, commercial ground stations, and any international collaborations.
        \item \textit{Coverage Intervals and Data Downlink Assumptions:} Provide estimates of communication windows, data rates, and expected downlink volumes based on ground segment capabilities.
        \item \textit{Ground Operations Facilities:} Describe the facilities and software systems used for mission control, data processing, and real-time monitoring.
    \end{itemize}
    
    \item \textbf{Launch and Early Operations:}  
    \begin{itemize}
        \item \textit{Launch Services Provider (LSP) Coordination:} Detail the coordination process with the LSP, including pre-launch checks, launch window selection, and post-launch support.
        \item \textit{Early Orbit Operations}: Describe the ground operations required immediately after launch, such as initial communication establishment, health checks, and orbital insertion verification.
    \end{itemize}
\end{itemize}

\subsection{(Optional) Educational Outreach / EPO Plan}
\noindent
An effective Educational Outreach (EPO) plan demonstrates your mission’s commitment to inspiring and educating the next generation, enhancing public engagement, and fostering scientific literacy.

\begin{itemize}
    \item \textbf{Student Involvement:}  
    \begin{itemize}
        \item \textit{Internship and Fellowship Programs:} Offer structured programs for students and early-career professionals to participate in mission activities, gaining hands-on experience.
        \item \textit{University-Led Experiments:} Collaborate with academic institutions to integrate student-designed experiments or CubeSat projects within the mission framework.
        \item \textit{Collaborative Research Opportunities:} Provide opportunities for joint research projects, allowing students and faculty to publish findings and contribute to mission science.
    \end{itemize}
    
    \item \textbf{Public Engagement:}  
    \begin{itemize}
        \item \textit{Real-Time Mission Dashboards:} Develop interactive platforms where the public can track mission progress, view live data streams, and engage with mission updates.
        \item \textit{Citizen Science Portals:} Create platforms that allow the public to contribute to data analysis, fostering a sense of ownership and participation in the mission’s scientific endeavors.
        \item \textit{Public Events and Outreach Activities:} Organize events such as webinars, workshops, and public lectures to disseminate mission findings and inspire interest in space science.
        \item \textit{Open Data Repositories:} Ensure that mission data is accessible to researchers, educators, and the public, promoting transparency and broad utilization of mission outputs.
    \end{itemize}
    
    \item \textbf{Impact Metrics:}  
    \begin{itemize}
        \item \textit{Anticipated Reach:} Estimate the number of students, schools, organizations, and individuals engaged through EPO activities.
        \item \textit{Media Coverage:} Plan for media engagement strategies to maximize visibility, including press releases, social media campaigns, and partnerships with media outlets.
        \item \textit{Partnerships with Museums and STEM Programs:} Collaborate with science museums, educational programs, and STEM initiatives to integrate mission content into their offerings, enhancing educational impact.
        \item \textit{Evaluation and Feedback:} Implement mechanisms to assess the effectiveness of EPO activities, collecting feedback to refine and improve outreach efforts continuously.
    \end{itemize}
\end{itemize}

\subsection{(Optional) Management Approach and Key Personnel}
\noindent
A robust management approach and a team of experienced personnel are critical to the successful execution of the mission. This section outlines your organizational structure, leadership, and the expertise driving the mission forward.

\begin{itemize}
    \item \textbf{Organizational Chart \& Roles:}  
    \begin{itemize}
        \item \textit{Org Chart:} Provide a clear organizational chart illustrating lines of authority, major work packages, and key collaboration points among team members and partners.
        \item \textit{Roles and Responsibilities:} Define the roles of prime contractors, subsystem leads, and collaborative partners, ensuring accountability and streamlined decision-making.
        \item \textit{Subsystem Coordination:} Explain how different subsystems are coordinated, highlighting interfaces and integration points to ensure cohesive mission operations.
    \end{itemize}
    
    \item \textbf{Team Expertise:}  
    \begin{itemize}
        \item \textit{Principal Investigators (PIs) and Project Managers:} Highlight the experience, flight heritage, and technical expertise of key leadership personnel, emphasizing past mission successes and relevant qualifications.
        \item \textit{Specialized Domain Knowledge:} Showcase team members’ expertise in critical areas such as propulsion, avionics, data analysis, or autonomous systems, demonstrating the team’s capability to handle mission complexities.
        \item \textit{Advisory Boards and Consultants:} Mention any advisory boards, external consultants, or subject matter experts involved in guiding the mission, ensuring diverse perspectives and expert oversight.
    \end{itemize}
    
    \item \textbf{Management Style:}  
    \begin{itemize}
        \item \textit{Communication Cadence:} Describe the frequency and format of team meetings, such as weekly teleconferences, monthly reviews, and quarterly board meetings, ensuring effective communication and coordination.
        \item \textit{Decision-Making Processes:} Outline the processes for making critical decisions, including the use of risk boards, change control boards, and escalation protocols to handle issues efficiently.
        \item \textit{Project Management Tools:} Mention any project management software or tools used for scheduling, task tracking, and collaboration, enhancing transparency and productivity.
        \item \textit{Performance Monitoring and Reporting:} Explain how project performance is monitored, including key performance indicators (KPIs), regular status reports, and progress tracking against milestones.
    \end{itemize}
    
    \item \textbf{Leadership and Governance:}  
    \begin{itemize}
        \item \textit{Governance Structure:} Detail the governance framework, including committees, oversight bodies, and reporting hierarchies that ensure mission alignment and accountability.
        \item \textit{Conflict Resolution Mechanisms:} Describe mechanisms in place to address conflicts or disagreements within the team, promoting a collaborative and effective working environment.
        \item \textit{Continuous Improvement:} Highlight practices for continuous improvement, such as after-action reviews, lessons learned sessions, and feedback loops to enhance mission processes and outcomes.
    \end{itemize}
\end{itemize}

\noindent
\textbf{Example Organizational Chart:}
\begin{figure}[h!]
    \centering
    \begin{tikzpicture}[node distance=2cm, auto, every node/.style={rectangle, draw, align=center, rounded corners, minimum height=1cm}]
        \node (PM) {Project Manager\\(Dr. Jane Doe)};
        \node (TechLead) [below left of=PM, xshift=-1cm] {Technical Lead\\(Dr. John Smith)};
        \node (OpsLead) [below right of=PM, xshift=1cm] {Operations Lead\\(Ms. Emily Zhang)};
        \node (PayloadLead) [below of=TechLead] {Payload Lead\\(Dr. Alan Brown)};
        \node (EPO) [below of=PayloadLead] {EPO Coordinator\\(Ms. Lisa Nguyen)};
        \node (MgmtBoard) [right of=PayloadLead, xshift=3cm] {Management Board\\(Stakeholders)};
        
        \draw[->] (PM) -- (TechLead);
        \draw[->] (PM) -- (OpsLead);
        \draw[->] (TechLead) -- (PayloadLead);
        \draw[->] (PayloadLead) -- (EPO);
        \draw[->] (PayloadLead) -- (MgmtBoard);
        \draw[->] (OpsLead) -- (MgmtBoard);
    \end{tikzpicture}
    \caption{Sample Organizational Chart}
    \label{fig:org_chart}
\end{figure}

\noindent
\textbf{Key Elements:}
\begin{itemize}
    \item \textbf{Clear Hierarchical Structure:} Ensures accountability and streamlined communication across all mission elements.
    \item \textbf{Dedicated Leadership Roles:} Assigns specific roles to manage technical, operational, and outreach aspects, promoting specialized focus and expertise.
    \item \textbf{Collaborative Oversight:} Incorporates a management board comprising stakeholders to provide strategic direction and oversight.
\end{itemize}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% 12. APPENDICES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Appendices}
\label{sec:appendices}

%-------------------------------------------
% FIRST BOX: OPTIONAL SECTIONS EXPLANATION (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (Appendices)]
\begin{itemize}
    \item \textbf{Technical Depth:}  
    Appendices allow you to include detailed analyses, calculations, design data, and extended discussions without interrupting the flow of your main narrative. This ensures that the main sections remain concise while providing reviewers access to comprehensive technical information.
    
    \item \textbf{ICDs, Drawings, Data:}  
    Provide expanded mechanical drawings, interface specifications, detailed schematics, or extensive tabulated data that would clutter primary sections if inserted inline. Use high-resolution images and clearly labeled diagrams to enhance understanding.
    
    \item \textbf{Keep It Organized:}  
    Label each appendix with a clear and descriptive title (e.g., Appendix A: Technical Data Sheets) and reference them appropriately from the main body (e.g., see Appendix A). This organization ensures reviewers can quickly locate and navigate supporting information.
    
    \item \textbf{Supplementary Information:}  
    Include any additional documentation that supports your proposal, such as detailed test procedures, raw data from experiments, or comprehensive simulation results. Ensure that all supplementary materials are relevant and enhance the credibility of your mission plan.
\end{itemize}
\end{tcolorbox}

\subsection{Technical Data Sheets}
\noindent
Include subsystem mass properties, center-of-gravity data, power consumption breakdowns, thermal profiles, and other in-depth tables and schematics. For example:
\begin{itemize}
    \item \textbf{Mass Properties:} Detailed mass distributions for each subsystem.
    \item \textbf{Center of Gravity:} Calculations and diagrams showing the spacecraft's center of gravity.
    \item \textbf{Power Consumption:} Breakdown of power usage for each component and subsystem.
    \item \textbf{Thermal Profiles:} Temperature ranges and thermal control system specifications.
\end{itemize}

\subsection{Interface Control Documents (ICDs)}
\noindent
Formal documents explaining how instruments or subsystems connect and interact:
\begin{itemize}
    \item \textbf{Mechanical Attachments:} Specifications for bolt patterns, tolerances, and mounting fixtures.
    \item \textbf{Electrical Interfaces:} Details on voltage lines, signal grounding, data bus specifications, and connector types.
    \item \textbf{Software/Command Protocols:} Protocols for controlling payloads, exchanging data, and interfacing with ground systems.
\end{itemize}

\subsection{Acronyms and Abbreviations}
\noindent
List domain-specific or mission-specific abbreviations used throughout the document:
\begin{itemize}
    \item \textbf{ADCS} – Attitude Determination and Control System
    \item \textbf{C\&DH} – Command and Data Handling
    \item \textbf{ICD} – Interface Control Document
    \item \textbf{TRL} – Technology Readiness Level
    \item \textbf{WBS} – Work Breakdown Structure
    \item \textbf{EPO} – Educational and Public Outreach
    % Add any additional relevant acronyms here
\end{itemize}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% REFERENCES
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\clearpage
\section*{References}

%-------------------------------------------
% FIRST BOX: REFERENCES EXPLANATION (PART 1)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (References: Part 1)]
\begin{itemize}
    \item \textbf{Citation Style:}  
    Follow the IEEE citation style with bracketed numeric references in order of appearance (e.g., [1], [2]). This structure is widely recognized and maintains a clean reference list.

    \item \textbf{Formatting Rules:}
    \begin{itemize}
        \item Use standard IEEE abbreviations for journals (e.g., \textit{Proc. IEEE}, \textit{J. Lightw. Technol.}).
        \item Capitalize the first word of the title, proper nouns, and acronyms in article/book titles; other words should be lowercase.
        \item Include the \textbf{DOI} (Digital Object Identifier) whenever available for journal articles.
        \item For books, include the edition (if not the first), publisher, year, and place of publication.
        \item For conference papers, include the full conference name, location, and date.
        \item For online resources, provide a stable \textbf{URL} that leads directly to the referenced document.
    \end{itemize}

        \item \textbf{BibTeX Integration:}  
    Define BibTeX entries inline using the \texttt{filecontents*} environment to avoid the need for a separate \texttt{.bib} file. Below is an example of an IEEE BibTeX citation:
    
    \vspace{0.5em}
    \textbf{Example BibTeX Entry:}
    \begin{verbatim}
@book{wertz1999,
  author    = {J. R. Wertz and W. J. Larson},
  title     = {Space Mission Analysis and Design},
  edition   = {3rd},
  publisher = {Microcosm Press},
  address   = {Hawthorne, CA, USA},
  year      = {1999},
  url       = {https://www.example.com}
}
    \end{verbatim}
    
    \vspace{0.5em}
    \textbf{Example In-Text Citation:}
    \begin{verbatim}
As discussed in \cite{wertz1999}, the design process...
    \end{verbatim}
\end{itemize}
\end{tcolorbox}

%-------------------------------------------
% SECOND BOX: REFERENCES EXPLANATION (PART 2)
%-------------------------------------------
\begin{tcolorbox}[colback=gray!10,colframe=gray!70,title=Explanation \& Best Practices (References: Part 2)]
\begin{itemize}
    
    \item \textbf{Practical Guidance:}
    \begin{itemize}
        \item Cite authoritative sources (e.g., official NASA, ESA, or ISO standards; peer-reviewed journal articles; recognized textbooks).
        \item Whenever possible, link to direct, stable URLs (e.g., NASA, ESA, standard organizations) instead of ambiguous landing pages.
        \item If certain documents (e.g., NASA directives) are not easily found on standard web pages, provide the best known direct link or the official accession number.
    \end{itemize}
\end{itemize}
\end{tcolorbox}

% Force *all* refs in .bib to appear (even if not cited)
\nocite{*}

% Choose an IEEE style bibliography
\bibliographystyle{IEEEtran}
\bibliography{inline_references}

% BibTeX Entries
\begin{filecontents*}{inline_references.bib}
@book{wertz1999,
  author    = {J. R. Wertz and W. J. Larson},
  title     = {Space Mission Analysis and Design},
  edition   = {3rd},
  publisher = {Microcosm Press},
  address   = {Hawthorne, CA, USA},
  year      = {1999},
  url       = {https://www.example.com}
}

@standard{iso-14300-1,
  title = {{ISO 14300-1:2023: Space Systems — Programme Management — Part 1: Structuring of a Project}},
  organization = {International Organization for Standardization},
  year = {2023},
  url = {https://www.iso.org/standard/86543.html}
}

@standard{iso-14300-2,
  title = {{ISO 14300-2:2023: Space Systems — Programme Management — Part 2: Product Assurance}},
  organization = {International Organization for Standardization},
  year = {2023},
  url = {https://www.iso.org/standard/86544.html}
}

@standard{iso-24113,
  title = {{ISO 24113:2023: Space Systems — Space Debris Mitigation Requirements}},
  organization = {International Organization for Standardization},
  year = {2023},
  url = {https://www.iso.org/standard/83494.html}
}

@standard{iso-18676,
  title = {{ISO 18676:2024: Space Systems — Requirements and Guidelines for the Management of Systems Engineering}},
  organization = {International Organization for Standardization},
  year = {2024},
  url = {https://www.iso.org/standard/87631.html}
}

@misc{nasa_se_handbook,
  author = {{NASA}},
  title = {NASA Systems Engineering Handbook: {NASA SP-2016-6105 Rev 2}},
  howpublished = {\url{https://www.nasa.gov/wp-content/uploads/2018/09/nasa_systems_engineering_handbook_0.pdf}},
  year = {2016}
}

@misc{nasa_std_6016,
  author = {{NASA}},
  title = {Standard Materials and Processes Requirements for Spacecraft: {NASA-STD-6016C}},
  howpublished = {\url{https://standards.nasa.gov/sites/default/files/standards/NASA/C/2021-09-30-NASA-STD-6016C-Approved.pdf}},
  year = {2021}
}

@misc{ecss_standards,
  author = {{European Cooperation for Space Standardization (ECSS)}},
  title = {ECSS Standards},
  howpublished = {\url{https://www.ecss.nl/standards/}},
  year = {2023}
}

@misc{esa_requirements,
  author = {{European Space Agency (ESA)}},
  title = {Requirements and Standards},
  howpublished = {\url{https://www.esa.int/Enabling_Support/Space_Engineering_Technology/Requirements_and_standards}},
  year = {2023}
}

@misc{nasa_endorsed_standards,
  author = {{NASA}},
  title = {NASA OCE Endorsed Technical Standards},
  howpublished = {\url{https://standards.nasa.gov/nasa-endorsed-standards}},
  year = {2023}
}

@misc{sae_aerospace_standards,
  author = {{SAE International}},
  title = {SAE Aerospace Standards},
  howpublished = {\url{https://www.sae.org/standards/aerospace}},
  year = {2023}
}

@misc{aiaa_standards,
  author = {{American Institute of Aeronautics and Astronautics (AIAA)}},
  title = {AIAA Standards},
  howpublished = {\url{https://www.aiaa.org/publications/standards}},
  year = {2023}
}

\end{filecontents*}




\end{document}
