Concept of Operations (external version)

CHECK THE MASTER LIST — VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE

CCP-CQC-CONOPS-03.05e

REVISION - National Aeronautics and Space Administration EFFECTIVE DATE: March 28, 2021

NASA Centennial Challenges in Collaboration with Ames Research Center Marshall Space Flight Center, Alabama 35812

Cube Quest Challenge

Concept of Operations

(external version)

March 28, 2020

NASA Centennial Challenges Title: Cube Quest Challenge Document No.: CCP-CQC-CONOPS-03.05e Revision: - Concept of Operations Effective Date: March 28, 2021 Page 2 of 20

CHECK THE MASTER LIST VERIFY THAT THIS IS THE CORRECT VERSION BEFORE USE

DOCUMENT HISTORY LOG

Status (Baseline/ Revision/ Canceled)

Document Revision

Effective Date

Description First Draft

i 2/11/19 Initial Outline

Revision

ii 5/8/19 Added in updated checklists. Added spots for Orbit Verif. Flowcharts. Added in 3rd Party Launch. Added in draft of High level ConOps (whiteboard sketch)

Revision

iii 5/20/2020 Redefined instructions for use by administrators rather than participants

Revision iv 10/26/2020 Updated for Artemis I, DSN agreement, and SW key Revision v 12/30/2020 Converted to a guide for competitors from a NASA-internal document

NASA Centennial Challenges Title: Cube Quest Challenge Document No.: CCP-CQC-CONOPS-03.05e Revision: - In-Space Challenge Workbook Effective Date: March 28, 2021 Page 3 of 31

CHECK https://www.nasa.gov/cubequest/reference/ TO VERIFY THIS IS THE LATEST VERSION BEFORE USE

Table of Contents Page 1.0 Introduction ......................................................................................................................... 5

Document Objectives ....................................................................................................................... 5

Definitions ........................................................................................................................................ 6

2.0 Applicable and Reference Documents ............................................................................... 8

Government Publications ................................................................................................................. 8

3.0 Participation ........................................................................................................................ 9

Participation Requirements Checklist .............................................................................................. 9

4.0 In-Space Challenge Concept of Operations .................................................................... 11

Concept of Operations for Deep Space and Lunar Derbies ........................................................... 11

4.1.1 Distance Verification ............................................................................................................... 13

4.1.2 Best Burst Data Rate Verification ........................................................................................... 14

4.1.3 Largest Data Volume Verification .......................................................................................... 16

4.1.4 Farthest Communications Distance from Earth Verification .................................................. 18

4.1.5 Spacecraft Longevity Verification .......................................................................................... 20

4.1.6 Complete Concept of Operations for Deep Space and Lunar Derbies .................................... 22

In-Space-Derby Orbit Determination ............................................................................................. 24

4.2.1 Deep Space Derby distance determination – DSN .................................................................. 24

4.2.2 Lunar Orbit Determination – self-reported .............................................................................. 25

5.0 In-Space Challenge Verification Checklist ..................................................................... 26

Deep Space Derby Verification Checklists .................................................................................... 26

5.1.1 Best Burst Data Rate ............................................................................................................... 27

5.1.2 Largest Aggregate Data Volume ............................................................................................. 27

5.1.3 Longest Communications Distance ......................................................................................... 28

5.1.4 Spacecraft Longevity ............................................................................................................... 28

Lunar Derby Verification Checklists ............................................................................................. 29

5.2.1 Best Burst Data Rate ............................................................................................................... 30

5.2.2 Largest Aggregate Data Volume ............................................................................................. 30

5.2.3 Spacecraft Longevity ............................................................................................................... 31



List of Illustrations Figure Page Figure 1-1: The Cube Quest Challenge has two derbie ................................................................................ 5 Figure 3-0: Contest end ................................................................................................................................. 9 Figure 3-2: Timeframes to submit documentation to Cube Quest ............................................................ 10 Figure 4-1: Deep Space and Lunar Derby summary timelines ................................................................... 11 Figure 4-2: Deep Space Derby in Brief: ..................................................................................................... 12 Figure 4-3: Lunar Derby in Brief: ............................................................................................................... 12 Figure 4-4: Rescheduling DSN Run ........................................................................................................... 13 Figure 4-5: First Navigation Milestone - reaching deep space or achieving one lunar orbit, ..................... 13 Figure 4-6: Collecting evidence of reaching deep space or achieving lunar orbit. ..................................... 14 Figure 4-7: Best Burst Data Rate - One of three Communication Milestones ........................................... 15 Figure 4-8: Collect Data Rate. .................................................................................................................... 16 Figure 4-9: Evaluate Burst. ......................................................................................................................... 16 Figure 4-10: Largest Data Volume - One of three Communication Milestones ......................................... 17 Figure 4-11: Collect Data Volume: ............................................................................................................. 18 Figure 4-12: Evaluate Volume: ................................................................................................................... 18 Figure 4-13: Farthest Communications Distance from Earth ..................................................................... 19 Figure 4-14: Collect Data Distance. ............................................................................................................ 20 Figure 4-15: Evaluate Distance. .................................................................................................................. 20 Figure 4-16: Spacecraft Longevity - Final communications milestone ...................................................... 21 Figure 4-17: Collect Last Data Block. ........................................................................................................ 22 Figure 4-18: Evaluate Age. ......................................................................................................................... 22 Figure 4-19: In-Space Derby Challenge activities detailed flow chart ....................................................... 23 Figure 4-20: Comms Architecture. ............................................................................................................. 24 Figure 4-21: DSN services verify ≥3M km for Deep Space ....................................................................... 24 Figure. 4-22: Verification of Lunar Derby first orbit. ................................................................................. 25 Figure 5-1: Timeline of Deep Space Derby activities ................................................................................. 26 Figure 5-2: Timeline of Lunar Derby activities .......................................................................................... 29

List of Tables Table Page Table 2-1 – Government Applicable Documents ......................................................................................... 8 Table 3-1: COOL Registration Checklist ................................................................................................... 10 Table 5-1: Arrival in Deep Space checkpoint ............................................................................................ 26 Table 5-2: Data Rate Checklist .................................................................................................................. 27 Table 5-3: Data Volume Checklist ............................................................................................................. 27 Table 5-4: Distance Checklist ..................................................................................................................... 28 Table 5-5: Longevity Checklist ................................................................................................................... 28 Table 5-6: Lunar Propulsion (Lunar Orbit Verification) ......................................................................... 29 Table 5-7: Data Rate Checklist .................................................................................................................. 30 Table 5-8: Data Volume Checklist ............................................................................................................. 30 Table 5-9: Longevity Checklist ................................................................................................................... 31



1.0 INTRODUCTION The Centennial Challenges Program (CCP) is NASA’s flagship program for technology prize

competitions (www.nasa.gov/Challenges). The program directly engages the public, academia, and industry in open prize competitions to stimulate innovation in technologies that have benefit to NASA and the nation. The CCP is an integral part of NASA's Space Technology Mission Directorate (STMD), which is innovating, developing, testing, and flying hardware for use in NASA's future missions. For more information about NASA's STMD, visit: http://www.nasa.gov/spacetech.

Beginning in 2015, NASA CCP has conducted the Cube Quest Challenge, for CubeSats to compete in one of two Derbies beyond low earth orbit (see Fig 1-1). The Deep Space Derby will be conducted once Competitor Team CubeSats have achieved, and maintain, a range of at least 3,000,000 kilometers (3M km) from Earth. The Lunar Derby will be conducted once a

Competitor Team’s CubeSat successfully achieves, and maintains, a verifiable lunar orbit. The challenge is defined in CCP-CQ-OPRULs-001 CubeQuest Challenge Operations and Rules. Prizes will be awarded for various communications, navigation and longevity achievements that are performed under the conditions of these Rules.

A series of Ground Tournaments (GTs) were held starting in 2017, in which three Competitor Teams were offered a secondary payload opportunity on NASA’s Artemis I, planned for 2021. All Artemis I Secondary Payload integration costs will be provided by Exploration Systems Development (ESD) for the selected payloads. These payloads will be inserted into a trans-lunar trajectory for in-space Challenge purposes. New Competitor Teams may join by selecting a third-party launch provider

in order to participate in this Challenge.

Document Objectives

The objective of this document is to consolidate all of the applicable procedures of the In-Space portion of the Cube Quest Challenge into one, easy to understand document. Contained in this document are various checklists, tables, and flowcharts aimed at aiding Cube Quest administration in carrying out the contest. These External Conops procedures are for competitor teams to use as a “grading rubric,” to see how the Challenge will be run and how their data will be judged.

Figure 1-1: The Cube Quest Challenge has two derbies; one in which CubeSats complete a lunar orbit, and another in which CubeSats reach deep space.



Definitions

The following terms are used in conjunction with and for the purposes of the Cube Quest Challenge.

An “administrator” is a NASA employee who organizes Cube Quest Challenge activities. A “competition day” is defined as a 24 hour period that starts at the respective time the

Competitor Team receives confirmation of launch (regardless of whether deployed from Artemis I SLS or from a Competitor Team-arranged launch vehicle). Each Competitor Team will have their own start time at which their competition days begin counting.

A Competitor Team is defined as any combination of one or more Team Members. Competitors Obtaining Their Own Launch (COOL) teams are defined as those funding

their CubeSat launch campaign, as differentiated from those teams awarded Artemis I launch slots based on ground tournament competitions.

A “data block” is 1024 bits of random data generated by a NASA-provided algorithm as prescribed by NASA. The “End of Competition” is the final day of the Cube Quest Challenge In-Space Competition, as defined in Rule 19.C

An Entity is a private or publicly owned company, private or publicly owned corporation, college, or university.

“Error free data” and “volume of error free data” are determined by the number of unique (nonduplicative), whole data blocks delivered to the judges that are free of transmission errors. Competitors may employ any error correction protocols (FEC, ARQ, hybrids) of their choice to achieve error-free data delivery.

In-Space Prizes is the all-inclusive term to refer to the Prizes available in the Deep Space Derby and the Lunar Derby.

Judges are the panel that assesses and scores entries during Ground Tournaments, and hold the final determination of prize award winners.

An “operating period” is a continuous 30-minute time segment during which the Competitor Teams will officially attempt to receive data.

Prizes is the all –inclusive term to refer to the monetary amounts awarded during the Ground Tournaments, Deep Space Derby, and Lunar Derby.

A Team Member is an individual or Entity who is currently contributing to a CubeSat, or who is providing ground station communication services, launch services or other services at rates not available to other customers, for a CubeSat competing in the Cube Quest Challenge. Team Members may be associated with more than one Competitor Team. If a Team Member is an individual, the individual has to be a citizen or permanent resident of the United States. If the Team Member is an Entity, the Entity must be a U.S. Entity.

A Team Leader is a Team Member acknowledged or designated by the Competitor Team as the leader or Cube Quest Challenge point of contact. The Team Leader must be a U.S. citizen, permanent resident, or U.S. Entity to be eligible to win Challenge Prizes.



A United States (U.S.) Entity is an Entity incorporated, chartered, or organized in the U.S. and maintains a primary place of business in the U.S.



2.0 APPLICABLE AND REFERENCE DOCUMENTS The documents listed in this section are referenced by this document. While every effort has

been made to ensure the completeness of these lists, document users are cautioned that they must meet all specified requirements of documents cited in the body of this document, whether or not they are listed here.

Document revisions are current to the date of this publication. Unless specifically noted within the document, the most recent document revision shall be applicable. Document users are responsible to verify correct versions.

The Cube Quest Challenge website (https://www.nasa.gov/cubequest/details) will be the primary location for document(s) access and updates. Hardcopy versions will not be available, except for inhibiting circumstances.

Government Publications

Government specifications, standards, and handbooks in Table 2-1 form a part of this document to the extent specified herein.

Table 2-1 – Government Applicable Documents Document # Document name Date Revision

CCP-CQ-OPRULs-001

CubeQuest Challenge Operations and Rules

June 15, 2020

Revision D

CQC-004-NNL-01 Instructions and Required Data Package for Cube Quest Challenge Competitors Obtaining Their Own Launch (COOL teams)

September 30, 2020

Revision B

NavArt-03.06 Required Navigation Artifacts 2020 Revision - CCP-CQ-COMPRO-001

Communications Procedure for Both In-Space Challenges (CommsProc)

March 1, 2020

Revision 4



3.0 PARTICIPATION There are two routes to participating in the Space Derbies. One was through the 2017 Ground Tournament activities, when participating teams registered for tournaments and were awarded launch opportunities through Artemis I. The other is through independently obtaining a launch opportunity, and is still open as of effective date of this document. Guidelines for this second route are given in the document “Instructions for Competitors Obtaining Their Own Launch (COOL),” available on the Cube Quest website (Sec. 2). These COOL teams, joining the contest after 2017, will have differing timeframes in which to complete Challenge activities relative to teams launching with Artemis I (see Fig 3-0).

Figure 3-0: Contest end: Activities eligible for prizes are within 365 days after Artemis I launches, or 365 days after the team deploys its CubeSat, whichever comes first (Rule 19). Late launch COOL teams contest activities also end at this time. Operations may continue after the contest end at the teams’ own expense; these may be eligible for publicity but are not counted towards prizes.

For clarity and transparency, the steps toward In-Space Competitions are outlined in a checklist below (Section 3.1) which the Cube Quest Administrators will use to register and verify COOL teams.

Participation Requirements Checklist

This checklist (Table 3-1) covers the tasks a COOL team must submit to Cube Quest Challenge administrators in the timeframe between registration of its notice of intent to join the Cube Quest



Challenge and the CubeSat’s integration with the launch vehicle. Figure 3-2 gives a top-level timeline of these activities. For the pre-launch process, most deadlines are related to the individual launch date (L). Table 3-1: COOL Registration Checklist

# COOL doc Section

Rules Section

Eligibility Steps Towards In-Space Competitions (Documentation to be submitted to Challenge administrators)

√

1 4.1 2.B Contacted Cube Quest Challenge with Notice of Intent? 2 4.2 2.B, 5.0 Submitted Registration Data Package? 4.F Received declaration of eligibility to enter? 3 4.3 4.F Submitted Pre-Launch Package? 4.3.1 4.F Integrated Pre-Launch Schedule? 4.3.2 -- Evidence of Launch Service Provider agreement, Launch Provider

Requirements, and V&V plan?

4.3.3 -- Concept of Operations? 4.3.4 Launch Service Provider’s Data? 4.3.5 5.C Radio license application? -- Approved radio licenses? 4.3.6 17.B ODAR and Planetary Protection Plans? (these cover decommissioning) -- ODAR and Planetary Protection approvals from NASA? 4.3.7 4 CubeSat design data? 4.3.8 -- List of any relevant additional considerations? 4.3.9 -- Home institution’s certificate of flight readiness? 4.3.10 -- Launch service provider’s statement of flight readiness? -- Received declaration of eligibility to compete? 4 4.4 4.F Has the CubeSat been inspected by Cube Quest judges prior to

integration with the LV provider’s deployment mechanism?

5 4.5 -- Have progress reports been submitted monthly until inspection? 6 18C Have agreed on communications log format & data wrapping protocol? 7 15A Launch Notification (within12 hours) 8 15A&B Deployment Notification (within 12 hours)

Figure 3-2: Timeframes to submit documentation to Cube Quest between notice of intent to compete and start of contest. Caution: FCC approvals may take up to 1 year and are to be obtained before submitting evidence of their completion to Cube Quest.



4.0 IN-SPACE CHALLENGE CONCEPT OF OPERATIONS An overview of the in-space through final awards timeline is given in Fig. 4-0, where line #1 shows the Deep Space Derby and line #2 shows the Lunar Derby. Timing is listed above each timeline, while deliverables or assessments are listed below. After launch, there is an interval of time while the rocket is reaching the drop-off point, at which time each CubeSat is released from the rocket. This deployment time (D) is used to measure the start of the contest for each participant. The end of the contest is measured as 365 days from the Artemis I launch (per Rule 19, End of Challenge). Further details and schedules are given in the subsections that follow. As in Fig. 4-1, all Deep Space Derby illustrations will contain the emblem with three stars, and all Lunar Derby illustrations will have a moon emblem. As many operations for the two derbies are similar, any differences for the Lunar Derby will be highlighted in a lunar blue glow.

Figure 4-1: Deep Space and Lunar Derby summary timelines

Concept of Operations for Deep Space and Lunar Derbies

Deep Space and Lunar Derby operations eligible for prizes are described here, alongside processes for validating each team’s communications and navigation. The overview shows stages of the contest at which data is collected (See Figures 4-2 and 4-3).

Communications milestones are self-reported but involve a verification key that NASA uses to verify they were received from space. Navigation milestones will be judged based on navigation artifacts sent by the teams, and may be verified with the help of Deep Space Network (DSN). See the document “Required Navigation Artifacts” for more detail.



Figure 4-2: Deep Space Derby in Brief: Proof of arrival is collected first; after which proof of burst, aggregate, and farthest comms are collected. Proof of longevity is the final data collection step.

Figure 4-3: Lunar Derby in Brief: Proof of achieving one lunar orbit is collected first; after which proof of burst and aggregate are collected. Proof of longevity is the final data collection step.



4.1.1 Distance Verification To verify that a CubeSat has reached deep space, or has achieved one lunar orbit, Cube Quest relies on data from the team (date and location) as well as information from the Deep Space Network (DSN) as shown in Fig. 4-5. DSN works with the team to plan the DSN run during the date and location they predict their CubeSat reaches deep space or has achieved one lunar orbit. The team will then coordinate with DSN to perform a simultaneous one-way doppler run at the projected time (see Fig 4-6). If the team’s schedule changes; i.e. if their launch date slips, deployment happens at a different time than predicted, or if startup activities take longer than planned, they need to reschedule their DSN run (see Fig 4-4). Challenge administrators may add another simultaneous one-way doppler run at their discretion. The data submitted by the team will be counted towards any prize after the navigation artifacts from the DSN run or from the team’s own ground station show that the CubeSat passes 3M km from earth’s surface or has reached lunar orbit.

Figure 4-5: First Navigation Milestone - reaching deep space or achieving one lunar orbit, respectively. Other milestones for the CubeSat will be eligible following this milestone.

Figure 4-4: Rescheduling DSN Run (same for both derbies).



4.1.1.1 Simultaneous One Way Doppler Run Cube Quest administration coordinates between the team, the Deep Space Network (DSN), and Mission Design & Navigation (MDNAV) to collect data on the location of the CubeSat. Teams will use the projected mission schedule to coordinate the timing of the simultaneous one-way doppler run with DSN. DSN will send the data collected to Challenge administrators, who will route it to MDNAV. MDNAV will produce a report for Cube Quest to archive for judging (see Fig. 4-6). The timestamp at which deep space or lunar orbit is achieved marks the earliest boundary for which a team may be considered eligible for prizes.

4.1.2 Best Burst Data Rate Verification To verify that the team’s best burst data rate, Cube Quest relies on data from the team and a verification key. The team shall notify Cube Quest of their best burst of error-free data volume transmitted over any 30-minute period and provide the contents thereof (see Fig. 4-7). Rules and information governing data packet requirements can be found in the CommsProc document.

Figure 4-6: Collecting evidence of reaching deep space or achieving lunar orbit.



Challenge administrators will archive this raw data, which, along with validation of the time the cubesat reached deep space or achieved one lunar orbit (per Section 4.1.1), will be used by the judges to evaluate burst data rate winners. The administrators will also archive the processed, verified data for the judges’ reference. 4.1.2.1 Data Rate Calculation Judges will use beginning and end time stamps to validate that the data set was sent after the start of the competition, and before the end of the competition (See Fig. 4-8). They will then compare the amount of data sent per unit time from each CubeSat. 4.1.2.2 Data Rate Flagging Teams will flag the highest data rate packet so that judges are spared the task of looking at all packets sent by the CubeSats (See Fig. 4-9). This may be done at the time of data submittal.

Figure 4-7: Best Burst Data Rate - One of three Communication Milestones



Figure 4-8: Collect Data Rate. Judges coordinate records of timestamps, competition start and end times, and # bytes sent in a given packet to determine data rate from the archived data.

Figure 4-9: Evaluate Burst. Teams may follow this logic flow to flag the highest data rate packet sent by each CubeSat for judges.

4.1.3 Largest Data Volume Verification To verify that the team’s largest data volume, Cube Quest relies on data from the team and a verification key. The team shall notify Cube Quest of their largest cumulative volume of error free data transmitted over any contiguous 28 days and provide its contents (see Fig. 4-10). Rules and information governing data packet requirements can be found in the CommsProc document. Challenge administrators will archive their processed data, which, along with validation of the time the CubeSat reached deep space or achieved one lunar orbit (per Section 4.1.1), will be used by the judges to evaluate aggregate data volume winners. The administrators will also archive the certification that the processed data has been run through software to verify use of the key, for the judges’ reference.



Figure 4-10: Largest Data Volume - One of three Communication Milestones

4.1.3.1 Data Volume Calculation Judges will use beginning and end time stamps to validate that the data set was sent after the start of the competition, and before the end of the competition (See Fig. 4-11). They will then compare the amount of error-free data sent per communications packet from each CubeSat. 4.1.3.2 Data Volume Flagging Teams will flag the highest data volume packet so that judges are spared the task of looking at all packets sent by the CubeSats (See Fig. 4-12).



Figure 4-11: Collect Data Volume: Judges coordinate records of timestamps, competition start and end times, and # bytes sent in a given packet to determine data rate from the archived data.

Figure 4-12: Evaluate Volume: Teams may follow this logic flow to flag the largest data volume packet sent by each CubeSat.

4.1.4 Farthest Communications Distance from Earth Verification To verify that the deep space CubeSat’s location for its farthest communication, Cube Quest relies on data from the team (date and location) and a verification key as well as information from DSN. The team shall notify Cube Quest of the date and location that their CubeSat sends its farthest data block above the minimum distance of 3M km from Earth and provide the contents thereof (see Fig. 4-13). Challenge administrators will archive their processed data, which, along with validation of the CubeSat’s trajectory (per Section 4.1.1), will be used by the judges to evaluate distance winners. The administrators will also archive the certification that the processed data has been run through software to verify use of the key, for the judges’ reference. 4.1.4.1 Farthest Communications Calculation Judges will use beginning and end time stamps to validate that the data set was sent after the start of the competition, and before the end of the competition (see Fig. 4-14). They will then confirm which error-free, 1024-bit data block was sent from the farthest distance from Earth based on a DSN run’s corroboration of the CubeSat’s trajectory. 4.1.4.2 Farthest Data Flagging Teams will flag the farthest distance data packet so that judges are spared the task of looking at all packets sent by the CubeSats (see Fig. 4-15).



Figure 4-13: Farthest Communications Distance from Earth

- Final Navigation Milestone (Deep Space Derby only).



Figure 4-14: Collect Data Distance. Judges coordinate records of timestamps, competition start and end times, and trajectory timing to determine farthest communication from the archived data.

Figure 4-15: Evaluate Distance. Teams may follow this logic flow to flag the farthest communication packet sent by each CubeSat.

4.1.5 Spacecraft Longevity Verification To verify CubeSat longevity, Cube Quest relies on data from the team, projected trajectory, and a verification key. The team shall send Cube Quest their first error-free, 1024-bit data block timestamped just after reaching deep space, and their last error-free, 1024-bit data block, timestamped more than 28 days from deployment, with the intervening locations projected to be in deep space or lunar orbit (see Fig 4-16). For the Deep Space Derby, position data may be interpolated based on the initial DSN run on reaching deep space (see Sec. 4.1.1 Deep Space Distance Verification) and the farthest distance DSN run (see Sec. 4.1.4 Farthest Communications Distance from Earth Verification).



Figure 4-16: Spacecraft Longevity - Final communications milestone

4.1.5.1 Last Communications Calculation Judges will use beginning and end time stamps to validate that the data set was sent after the start of the competition, and before the end of the competition (see Fig. 4-17). They will then confirm which error-free, 1024-bit data block was sent closest to the end of the competition timeframe and in deep space or lunar orbit, based on a DSN run’s corroboration of the CubeSat’s trajectory. 4.1.5.2 Last Data Flagging Teams will flag the last data packet sent so that judges are spared the task of looking at all packets sent by the CubeSats (see Fig. 4-18).



Figure 4-17: Collect Last Data Block. Judges coordinate records of timestamps, competition start and end times, and trajectory timing to determine last communication.

Figure 4-18: Evaluate Age. Teams may follow this logic flow to flag the last eligible communication packet sent by each CubeSat.

4.1.6 Complete Concept of Operations for Deep Space and Lunar Derbies The overall flow of activities between the teams and Challenge administrators is shown for the the In-Space Derbies (Fig 4-19). Deep Space Derby operations are annotated with a field of stars:

while Lunar Derby operations are annotated with a blue moon:



Figure 4 -19: In -Space D

erby Challenge activities detailed flow

chart



In-Space-Derby Orbit Determination

DSN authenticates claimed distance for Challenge Administrators to enable verification that a team’s CubeSat has acheived the Derby start conditions. The teams can also provide their Consultative Committee for Space Data Systems (CCSDS)-compliant navigation data from their ground stations, as shown in Fig 4-20.

4.2.1 Deep Space Derby distance determination – DSN Administrators expect that Deep Space Derby teams will schedule their DSN runs to occur when their CubeSat nears the 3 M km boundary. Additional (non-DSN) location data may be used to verify that all Derby activities occur on the far side of the 3 M km boundary from Earth’s surface (see Fig. 4-21).

Figure 4-20: Comms Architecture. Challenge administrators recieve location and communication checks for verification and evaluation of data from both NASA and the teams.

Figure 4-21: DSN services verify ≥3M km for Deep Space



4.2.2 Lunar Orbit Determination – self-reported Potentially, achievement of Lunar Orbit for entry into the Lunar Derby could be verified the same way as for the Deep Space Derby, using DSN and verifying through MDNAV at JPL to authenticate achievement/ maintenance of lunar orbit (Section 4.2.1). Currently, no lunar team plans on using DSN for location or guidance.

A COOL team wishing to use an alternate method may apply for a waiver. Another method may not use DSN, but provide MDNAV CCSDS-compliant data from a series of ground stations (such as WFF). Administrators will verify a team’s CubeSat is in Lunar Orbit during their communications operations using time stamps and data with an embedded key (see Fig. 4-22).

Figure. 4-22: Verification of Lunar Derby first orbit. Administrators rely on the team’s navigation data, each submitted within minutes of receipt, and comms with an embedded key.



5.0 In-Space Challenge Verification Checklist Each stage in the competition will require evidence, reports, and permissions. To keep track

of this mountain of paperwork that is likely to outweigh the CubeSats themselves, the administrators and contestants will benefit from checklists. The administrators can check off each document as it is received, and can help teams remember any that are missing. The verification deliverables for each of the in-space challenges will be slightly different; we provide a checklist for both Deep Space (section 5.1) and Lunar (section 5.2) Derbies below.

Deep Space Derby Verification Checklists

A checklist has been provided in the following sections for each Deep Space Derby prize from achievement of ≥ 3M km onwards. The Deep Space Derby (Fig. 5-1) includes two requirements checkpoints and 4 potential prizes.

Requirements:

1. Participation Requirements Checklist (see checklist in Section 3.1), 2. Arrival in Deep Space (see checklist in Section 5.1),

Prizes: 1. Best Burst Data Rate (see checklist in Section 5.1.1),

2. Largest Aggregate Data Volume (see checklist in Section 5.1.2), 3. Longest Communications Distance (see checklist in Section 5.1.3), and

4. Spacecraft Longevity (see checklist in Section 5.1.4).

Figure 5-1: Timeline of Deep Space Derby activities

Table 5-1: Arrival in Deep Space checkpoint # Rules

Section CommsProc

Section From Launch to Competition Start (Arrival in Deep Space, ≥3M km

from Earth’s surface) √

1 Coordinated operating schedule with DSN & CQC administrators? 2 Scheduled DSN run verifying arrival at ≥3M km? 3 18.A 4.4 Informed administrators ≥ 24 hours before the start of each operating

period?

4 Received first communication after deployment? 5 Received communication from near 3M km? 6 22B 4.4 Performed DSN run? 7 Received first communication after reaching 3M km? 8 18.F 4.4 Filed raw data with administrators within 10 minutes? 9 18.E 4.4 File processed data with administrators within 1 hour? 10 18.C 4.4 Supplied judges with pre-Deep Space communications log, to verify

timing of reaching 3M km?



5.1.1 Best Burst Data Rate

Table 5-2: Data Rate Checklist # Rules

Section CommsProc

Section Eligibility for Best Burst Data Rate in Space √

1 18A 4.4 Informed administrators ≥ 24 hours before the start of each operating period?

2 23A, 18B 4.4 Received at least one, 1024-bit data block? 3 23A Recorded max number of data blocks received in

continuous 30 minute operating period?

4 18F 4.4 Delivered raw and processed data after each operating period?

5 18C 4.4 Provided Communications Log at the end of each Operating Period?

6 22A, 22B 4.4 Supplied Navigation Artifacts showing data block was received while on portion of trajectory >3M km?

7 19A Timestamped prior to End of Competition? Highlighted rows give selection criteria specific to this prize.

5.1.2 Largest Aggregate Data Volume

Table 5-3: Data Volume Checklist # Rules

Section CommsProc

Section Eligibility for Largest Aggregate Data Volume in Space √


2 23B 4.4 Received at least 1000, 1024-bit data blocks? 3 23B 4.4 Recorded max number of data blocks received in

continuous 28-day period?







5.1.3 Longest Communications Distance

Table 5-4: Distance Checklist # Rules

Section CommsProc

Section Eligibility for Longest Communications Distance √

1 18A Informed administrators ≥ 24 hours before the start of each operating period?

2 23B 4.4 Received ≥one, error-free, 1024-bit data block? 3 Recorded time last, error-free, 1024-bit data block

received?


5 18C 4.4 Provided Communications Log at the end of last Operating Period?



5.1.4 Spacecraft Longevity

Table 5-5: Longevity Checklist # Rules

Section CommsProc

Section Eligibility for Spacecraft Longevity √


2 23B 4.4 Recorded time first, error-free, 1024-bit data block received?

3 Recorded time last, error-free, 1024-bit data block received?







Lunar Derby Verification Checklists

A checklist has been provided in the following sections for each Lunar Derby prize from achievement of lunar orbit onwards. The Lunar Derby (Fig. 5-2) includes one requirements checkpoint and 4 potential prizes.

Requirement: 1. Participation Requirements Checklist (see checklist in Section 3.1)

Prizes: 1. Lunar Propulsion/Completion of Lunar Orbit (see checklist in Section 5.2),

2. Best Burst Data Rate (see checklist in Section 5.2.1), 3. Largest Aggregate Data Volume (see checklist in Section 5.2.2), and

4. Spacecraft Longevity (see checklist in Section 5.2.3).

Figure 5-2: Timeline of Lunar Derby activities

Table 5-6: Lunar Propulsion (Lunar Orbit Verification) # Rules

Section CommsPro

c Section From Launch to Competition Start (Completion of lunar

orbit, between 300 and 10,000 km) √

1 Coordinated operating schedule with DSN & CQC administrators?

2 Scheduled DSN run verifying one lunar orbit? 3 18.A 4.4 Informed administrators ≥ 24 hours before the start of

each operating period?

4 Received first communication after deployment? 5 Received communication from entry into lunar orbit? 6 22B 4.4 Performed DSN run? 7 Received first communication after achieving orbit? 8 18.F 4.4 Filed raw data with administrators within 10 minutes? 9 18.E 4.4 File processed data with administrators within 1 hour? 10 18.C 4.4 Supplied judges with pre-orbit communications log, to

verify timing of entering and completing orbit?



5.2.1 Best Burst Data Rate

Table 5-7: Data Rate Checklist # Rules

Section CommsProc

Section Eligibility for Best Burst Data Rate in Orbit √


2 25B, 18B 4.4 Received at least one, 1024-bit data block? 3 25B 4.4 Recorded max number of data blocks received in

continuous 30 minute operating period?



6 24B 4.4 Supplied Navigation Artifacts showing data block was received while in lunar orbit (300 - 10,000 km)?


5.2.2 Largest Aggregate Data Volume

Table 5-8: Data Volume Checklist # Rules

Section CommsProc

Section Eligibility for Largest Aggregate Data Volume in Orbit √


2 25C 4.4 Received at least 1000, 1024-bit data blocks? 3 25C 4.4 Recorded max number of data blocks received in

continuous 28-day period?







5.2.3 Spacecraft Longevity

Table 5-9: Longevity Checklist # Rules

Section CommsProc

Section Eligibility for Spacecraft Longevity √

1 18A Informed administrators ≥ 24 hours before the start of each operating period?

2 25D Recorded time first, error-free, 1024-bit data block received?

3 25D Recorded time last, error-free, 1024-bit data block received?



