Search NASASearch

SEARCH · Search NASA

Results for “CARA”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records

CARA Devolution ESMO Pilot Program

Information regarding the current effort ongoing with CARA to determine the steps needed to have a mission move away from being supported by CARA, otherwise referred to as Devolving/Devolution. Information regarding the working group established to undertake this effort, documents agreed that needed to be written and plans for a parallel operations period. The communication between ESMO and CARA during the Parallel Operations period will be as the following: – A daily email will be sent from ESMO to CARA describing each HIE that is being actively planned and worked, and the action that ESMO is planning on taking – A weekly email will be sent from ESMO to CARA listing the progress toward achieving the parallel operations success criteria – The CARA team will remain on distribution for ESMO HIE communications and CAM invitations associated with DAMs/RMMs during the parallel operations period – At a minimum, 2 members of the CARA team will be in attendance at all ESMO planning and review discussions – A monthly email will be sent from ESMO to CARA with the HIE metrics • During parallel operations, ESMO will contact NASA Headquarters to report any redDevolution Working Group laid out and completed all steps needed to begin parallel operations • Parallel Ops for ESMO began on 11/26 (CARA in shadow mode only) • Any lessons learned from parallel ops will be folded back into documents/templates • Hope to achieve all success criteria < 6 months • Decision for permanent devolution will be based on completion of parallel ops and other future documentation creation (CARA Standard and Handbook, etc) and reviews (ORR) event which is less than 2 days from TCA, including the proposed remediation, on an as-needed daily basis flow using SpaceTrack to send and receive data

ESMO pilot devolution program

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment

NASA Conjunction Assessment Risk Analysis (CARA) Updated Requirements Architecture

The NASA Conjunction Assessment Risk Analysis (CARA) program has been performing routine on-orbit satellite conjunction risk analysis for unmanned NASA spacecraft since 2005, and has developed a robust operations procedure and set of recommended best practices for operational conjunction assessment. However, a number of recent developments in Space Situational Awareness and commercial space operations conduct, such as the immanent deployment of much more sensitive space sensing systems and the launching of much larger satellite constellations, have begun to challenge these standard collision risk parameters and calculations. In response CARA has pursued a multi-year evaluation initiative to re-examine risk assessment algorithms and techniques, to develop needed improvements, and to assemble analysis-based operational requirements. This paper gives an overview of the principal parts of the Conjunction Assessment (CA) risk assessment process used at CARA, outlines the technical challenges that each part presents, surveys the possible solutions, and then indicates which particular solution is being recommended for NASA.

Newman, L. K.

NASA CARA Tools

The NASA Conjunction Assessment Risk Analysis (CARA) team has created and posted to GitHub a set of MATLAB software tools for collision assessment (CA) analysis. The software is provided to the public under a NASA Open-Source Software Agreement and is maintained/updated by the CARA Analysis team. Capabilities provided within the toolset include algorithms in assessing probability of collision (Pc), collision consequence, covariance realism, Orbit Determination (OD) quality assessment, and single covariance max Pc. Additionally, a set of utilities are provided for astrodynamics topics closely related to CA, such as: Conjunction Data Message (CDM) parsing, covariance transformations, coordinate system transformations, etc. The repository is regularly updated on a monthly basis and new functionality will be added as algorithms are approved for public release. This presentation will provide a brief introduction to the toolset, highlight some of the key components which can be used in operations, and will present information on algorithms that are in the release pipeline and can be expected soon. This software will enable operators to independently perform CA calculations using the same core algorithms that CARA uses in operations.

L. Baars

NASA CARA Tools

The NASA Conjunction Assessment Risk Analysis (CARA) team has created and posted to GitHub a set of MATLAB software tools for collision assessment (CA) analysis. The software is provided to the public under a NASA Open-Source Software Agreement and is maintained/updated by the CARA Analysis team. Capabilities provided within the toolset include algorithms in assessing probability of collision (Pc), collision consequence, covariance realism, Orbit Determination (OD) quality assessment, and single covariance max Pc. Additionally, a set of utilities are provided for astrodynamics topics closely related to CA, such as: Conjunction Data Message (CDM) parsing, covariance transformations, coordinate system transformations, etc. The repository is regularly updated on a monthly basis and new functionality will be added as algorithms are approved for public release. This presentation will provide a brief introduction to the toolset, highlight some of the key components which can be used in operations, and will present information on algorithms that are in the release pipeline and can be expected soon. This software will enable operators to independently perform CA calculations using the same core algorithms that CARA uses in operations.

Luis Baars

NASA Conjunction Assessment Risk Analysis (CARA) Ground Systems, Software and Operations Infrastructure Cloud Implementation

The growing number of large-scale constellations and the improvements made in the tracking and detection of resident space objects have contributed to the increase of satellite conjunction events. As a result of the increase of objects in Earth orbit, the timeline for risk analysis computations for satellite collision avoidance is more urgent when conjunctions occur. It is imperative NASA maintains a space environment safety functionality for the agency that allows CARA remote access to the ground system while maintaining redundancy. CARA’s On-premises (On-prem) ground system would no longer be able to meet these access and redundancy requirements, hence the investigation and eventual implementation of a Cloud-based ground station infrastructure as a viable solution. This paper will provide an overview of the principal parts of the Conjunction Assessment (CA) risk analysis process used at CARA, summarize the key drivers towards the Cloud solution, and share key lessons learned that are significant for any operational entity considering a cloud solution for real-time satellite operations to ensure a sustainable space traffic environment for all.

Sustainability

Middle Man Concept for In-Orbit Collision Risks Mitigation, CAESAR and CARA Examples

This paper describes the conjunction analysis which has to be performed using data provided by JSpOC. This description not only demonstrates that Collision Avoidance is a 2- step process (close approach detection followed by risk evaluation for collision avoidance decision) but also leads to the conclusion that there is a need for a Middle Man role. After describing the Middle Man concept, this paper introduces two examples with their similarities and particularities: the American civil space effort delivered by the NASA CARA team (Conjunction Assessment Risk Analysis) and the French response CAESAR (Conjunction Assessment and Evaluation Service: Alerts and Recommendations). For both, statistics are presented and feedbacks discussed. All together, around 80 satellites are served by CARA and/or CAESAR. Both processes regularly evolve in order either to follow JSpOC upgrades or to improve analysis according to experience acquired during the past years.

conjunction

ESMO's Approach to CARA Devolution

This presentation attempts to provide a walk-through of how ESMO prepared/is preparing to handle the situation should CARA no longer support day to day operations.

Devolution

CARA Devolution: ESMO Pilot Program/Parallel Operations

This presentation attempts to provide a walk-through of how ESMO prepared/is preparing to handle the situation should CARA no longer support day to day operations, with specific updates regarding the parallel operations period (6 month test).

Mantziaras, Dimitrios

Collision Avoidance Short Course: Conjunction Assessment Risk Analysis - NASA Robotic CARA: Theory - Part I:

Satellite conjunction assessment is perhaps the fastest growing area in space situational awareness and protection with military, civil and commercial satellite owner-operators embracing more and more sophisticated processes to avoid the avoidable - namely collisions between high value space assets and orbital debris. NASA and Centre National d'Etudes Spatiales (CNES) have collaborated to offer an introductory short course on all the major aspects of the conjunctions assessment problem. This half-day course will cover satellite conjunction dynamics and theory. Joint Space Operations Center (JsPOC) conjunction data products, major risk assessment parameters and plots, conjunction remediation decision support, and present and future challenges. This briefing represents the NASA portion of the course.

Conjunction

Cara Status and Upcoming Enhancements

RIC Miss Values in Summary TableTabular presentation of miss vector in Summary Section RIC Uncertainty Values in Details SectionNumerical presentation of miss component uncertainty values in Details SectionGreen Events with Potentially Maneuverable Secondary ObjectsAll potentially maneuverable secondary objects will be reported out to 7-days prior to TCA for LEO events and 10-days for NONLEO events, regardless of risk (relates to MOWG Action Item 1309-11) All green events with potentially active secondary objects included in Summary ReportsAllows more time for contacting other OOBlack Box FixSometimes a black square appeared in the summary report where the ASW RIC time history plot should beAppendix Orbit RegimeMission Name MismatchPc 0 Plotting BugAll Pc points less than 1e-10 (zero) are now plotted as 1e-10 (instead of not at all)Maneuver Indication FixManeuver indicator now present even if maneuver was in the past.

Operations

CARA Risk Assessment Thresholds

Warning remediation threshold (Red threshold): Pc level at which warnings are issued, and active remediation considered and usually executed. Analysis threshold (Green to Yellow threshold): Pc level at which analysis of event is indicated, including seeking additional information if warranted. Post-remediation threshold: Pc level to which remediation maneuvers are sized in order to achieve event remediation and obviate any need for immediate follow-up maneuvers. Maneuver screening threshold: Pc compliance level for routine maneuver screenings (more demanding than regular Red threshold due to additional maneuver uncertainty).

conjunction