Search NASA⌕ Search

SEARCH · Search NASA

Results for “success”

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 145 records · Page 8

A Successful Infusion Process for Enabling Lunar Exploration Technologies

The NASA Vision for Space Exploration begins with a more reliable flight capability to the International Space Station and ends with sending humans to Mars. An important stepping stone on the path to Mars encompasses human missions to the Moon. There is little doubt throughout the stakeholder community that new technologies will be required to enable this Vision. However, there are many factors that influence the ability to successfully infuse any technology including the technical risk, requirement and development schedule maturity, and, funds available. This paper focuses on effective infusion processes that have been used recently for the technologies in development for the lunar exploration flight program, Constellation. Recent successes with Constellation customers are highlighted for the Exploration Technology Development Program (ETDP) Projects managed by NASA Glenn Research Center (GRC). Following an overview of the technical context of both the flight program and the technology capability mapping, the process is described for how to effectively build an integrated technology infusion plan. The process starts with a sound risk development plan and is completed with an integrated project plan, including content, schedule and cost. In reality, the available resources for this development are going to change over time, necessitating some level of iteration in the planning. However, the driving process is based on the initial risk assessment, which changes only when the overall architecture changes, enabling some level of stability in the process.

Over, Ann P.↗

Systems Engineering Technical Authority: A Path to Mission Success

The systems engineering of space missions to study planet Earth has been an important focus of the National Aeronautics and Space Administration (NASA) since its inception. But all space missions are becoming increasingly complex and this fact, reinforced by some major mishaps, has caused NASA to reevaluate their approach to achieving safety and mission success. A new approach ensures that there are adequate checks and balances in place to maximize the probability of safety and mission success. To this end the agency created the concept of Technical Authority which identifies a key individual accountable and responsible for the technical integrity of a flight mission as well as a project-independent reporting path. At the Goddard Space Flight Center (GSFC) this responsibility ultimately begins with the Mission Systems Engineer (MSE) for each satellite mission. This paper discusses the Technical Authority process and then describes some unique steps that are being taken at the GSFC to support these MSEs in meeting their responsibilities.

Andary, James F.↗

Proven and Robust Ground Support Systems - GSFC Success and Lessons Learned

Over the past fifteen years, Goddard Space Flight Center has developed several successful science missions in-house: the Wilkinson Microwave Anisotropy Probe (WMAP), the Imager for Magnetopause-to-Aurora Global Exploration (IMAGE), the Earth Observing 1 (EO-1) [1], and the Space Technology 5 (ST-5)[2] missions, several Small Explorers, and several balloon missions. Currently in development are the Solar Dynamics Observatory (SDO) [3] and the Lunar Reconnaissance Orbiter (LRO)[4]. What is not well known is that these missions have been supported during spacecraft and/or instrument integration and test, flight software development, and mission operations by two in house satellite Telemetry and Command (T & C) Systems, the Integrated Test and Operations System (ITOS) and the Advanced Spacecraft Integration and System Test (ASIST). The advantages of an in-house satellite Telemetry and Command system are primarily in the flexibility of management and maintenance - the developers are considered a part of the mission team, get involved early in the development process of the spacecraft and mission operations-control center, and provide on-site, on-call support that goes beyond Help Desk and simple software fixes. On the other hand, care must be taken to ensure that the system remains generic enough for cost effective re-use from one mission to the next. The software is designed such that many features are user-configurable. Where user-configurable options were impractical, features were designed so as to be easy for the development team to modify. Adding support for a new ground message header, for example, is a one-day effort because of the software framework on which that code rests. This paper will discuss the many features of the Goddard satellite Telemetry and Command systems that have contributed to the success of the missions listed above. These features include flexible user interfaces, distributed parallel commanding and telemetry decommutation, a procedure language, the interfaces and tools needed for a high degree of automation, and instantly accessible archives of spacecraft telemetry. It will discuss some of the problems overcome during development, including secure commanding over networks or the Internet, constellation support for the three satellites that comprise the ST-5 mission, and geographically distributed telemetry end users.

Pfarr, Barbara↗

Improving Our Odds: Success through Continuous Risk Management

Launching a rocket, running a business, driving to work and even day-to-day living all involve some degree of risk. Risk is ever present yet not always recognized, adequately assessed and appropriately mitigated. Identification, assessment and mitigation of risk are elements of the risk management component of the "continuous improvement" way of life that has become a hallmark of successful and progressive enterprises. While the application of risk management techniques to provide continuous improvement may be detailed and extensive, the philosophy, ideals and tools can be beneficially applied to all situations. Experiences with the use of risk identification, assessment and mitigation techniques for complex systems and processes are described. System safety efforts and tools used to examine potential risks of the Ares I First Stage of NASA s new Constellation Crew Launch Vehicle (CLV) presently being designed are noted as examples. Recommendations from lessons learned are provided for the application of risk management during the development of new systems as well as for the improvement of existing systems. Lessons learned and suggestions given are also examined for applicability to simple systems, uncomplicated processes and routine personal daily tasks. This paper informs the reader of varied uses of risk management efforts and techniques to identify, assess and mitigate risk for improvement of products, success of business, protection of people and enhancement of personal life.

Greenhalgh, Phillip O.↗

The Successful Implementation of NASA Orbital Debris Requirements for the Retirement of TDRS-1

TDRS-1 was decommissioned on October 28th 2009 following more than 26 years of operation. The Grand Old Dame of the TDRSS constellation wa s launched aboard the maiden voyage of the Space Shuttle Challenger ( STS-6) in April 1983. TDRS-1 survived a malfunction of the Inertial Upper Stage eventually utilizing its own propulsion system to success fully reach its assigned station in geosynchronous orbit. The anomalo us beginning of the TDRS-1 mission was not without lasting consequenc es as the primary reaction control system (A-side) was completely di sabled with an apparent propellant leak and the secondary system (B-s ide) suffered damage to its negative roll thruster rendering the thru ster inoperable. Following decommissioning the challenge to completin g a successful TDRS-1 end-of-mission (EOM) was the implementation of the stringent orbital debris requirements of NPR 8715.6 with a parti ally functioning spacecraft not originally designed to meet those req uirements. The TDRS-1 EOM had three key goals: 1) removal of the spac ecraft from geosynchronous orbit; 2) depletion of the remaining prope llant; and 3) passivation of all other sources of energy storage or generation. The TDRS-1 EOM approach was one of minimizing risks while accomplishing the goals above. The orbit raising portion of EOM was accomplished using deltavelocity operations already proven during pre vious stationchanging maneuvers. The propellant depletion approach wa s necessarily more aggressive as over 20 hours of burn time was requ ired to deplete the remaining fuel. A novel approach utilizing a spin ning, thrusting, passively controlled spacecraft configuration was ut ilized to achieve reasonable burn durations that met schedule constra ints. This nonstandard configuration required careful analysis of ele ctrical, thermal, and communication subsystems. The configuration wa s thoroughly simulated prior to the start of operations and carefully characterized during the initial spin period and first burn. Passiva tion was by definition a unique operation not previously performed wi thin the TDRS 1-7 constellation. Use was made of a TDRS spacecraft si mulator to verify the operational procedure to mitigate risks and pro vide crew training. TDRS-1 orbit raising maneuvers commenced on June 5th 2010 and completed on June 14th with an apogee 370 km and a peri gee 352 km above geosynchronous altitude. 127 kg of propellant were e stimated to be remaining in the tanks at the completion of orbit rais ing. TDRS-1 was placed in its spinning orientation on June 16th and the first fuel depletion burn was performed the following day. A seri es of 10 depletion burns were performed ending on June 26th when both propellant tank pressures experienced dramatic drops. Final passivat ion was performed on June 27 th deactivating electronics, removing t he batteries from the bus and solar arrays, and disabling the space-t o-ground communications equipment. The Second TDRS Ground Terminal (S TGT) continued to open loop track TDRS-1 for several days attempting command reacquisition several times a day. All attempts were unsucce ssful confirming passivation was achieved. The TDRS-1 orbit at passiv ation was an orbital debris compliant 36,319 x 36,128 km in height. W hile differing spacecraft designs may preclude mimicking the exact TD RS-1 EOM approach, the TDRS-1 campaign serves to demonstrate that pr e-NPR 8715.6 designs can be made to meet the requirements resulting i n a reduced orbit debris environment for future missions

Mirczak, Walter↗

The NASA MLAS Flight Demonstration - A Review of a Highly Successful Test

NASA has tested the Max Launch Abort System (MLAS) as a risk-mitigation design should problems arise with the baseline Orion spacecraft launch abort design. The Max in MLAS is not Maximum, but rather dedicated to Max Faget, The renowned NASA Spacecraft designer. In the fall of 2009, the mission was flown, with great success, from the NASA Wallops Flight Facility. The MLAS flight test vehicle prototype consists of a boost ring, coast ring, and the MLAS fairing itself, which houses an Orion Command Module (CM) boilerplate. The objective of the MLAS flight test is to reorient the fairing with the CM, weighing approximately 29,000 lbs and traveling 290 fps, 180 degrees to an orientation suitable for the release of the CM during a pad abort and low altitude abort. Although multiple parachute deployments are used in the MLAS flight test vehicle to complete its objective, there are only two parachute types employed in the flight test. Five of the nine parachutes used for MLAS are 27.6 ft DO ribbon parachutes, and the remaining four are standard G-12 cargo parachutes. This paper presents an overview of the 27.6 ft DO ribbon parachute system employed on the MLAS flight test vehicle for coast ring separation, fairing reorientation, and as drogue parachutes for the CM after separation from the fairing. Discussion will include: the process used to select this design, previously proven as a spin/stall recovery parachute; descriptions of all components of the parachute system; the minor modifications necessary to adapt the parachute to the MLAS program; the techniques used to analyze the parachute for the multiple roles it performs; a discussion of the rigging techniques used to interface the parachute system to the vehicle; a brief description of how the evolution of the program affected parachute usage and analysis; and a summary of the results of the flight test, including video of the flight test and subsequent summary analysis. . A discussion of the flight test which was highly successful as well as the flight test observations will be a significant portion of the review.

Taylor, Anthony P.↗

CANADARM: 20 Years of Mission Success Through Adaptation

As part of the National Aeronautics and Space Administration's Space Shuttle Transportation System, the Shuttle Remote Manipulator System has played a vital role in the success of 60 space missions. This paper concludes that the robustness and success of the Canadarm over its 20 year life can be attributed to the adaptations that have been made to it to meet the increased demands that have been placed on the system. Enhancements that have been made to the arm to improve its operational capabilities, reduce risk and extend its life are examined in this paper. Potential future enhancements based on operational trends are also discussed.

Hiltz, Michael↗

Techniques for Assuring NASA Mission Success Using Redundancy and Multi-Functionality Designs

Topics include NASA centers around the country; 2009 highlights of significant successes in space transportation, exploration, and science; significant accomplishments; places to explore include Lagrange points, near-Earth objects, Mars and the Moon, and International Space Station research; Marshall's missions include propulsion and transportation systems, life support systems, and earth and space science spacecraft, systems, and operations; project lifecycle management model; motivation of avionics fault-tolerance, redundancy needs and concerns, redundancy versus reliability; parallel-series configurations; effect of adding redundancy on mission success; example of rules-based approach where reliability and safety interaction impacts design; impact of common cause failure; approach ot bottom-up reliability analysis; three factors that lead to redundant system failure; Apollo 13 multi-functional reliability and example; and mitigating the risk of single string spacecraft architecture;.

Shivers, Herb↗

Ares I-X Flight Test Development Challenges and Success Factors

The NASA Constellation Program's Ares I-X rocket launched successfully on October 28, 2009 collecting valuable data and providing risk reduction for the Ares I project. The Ares I-X mission was formulated and implemented in less than four years commencing with the Exploration Systems Architecture Study in 2005. The test configuration was founded upon assets and processes from other rocket programs including Space Shuttle, Atlas, and Peacekeeper. For example, the test vehicle's propulsion element was a Shuttle Solid Rocket Motor. The Ares I-X rocket comprised a motor assembly, mass and outer mold line simulators of the Ares I Upper Stage, Orion Spacecraft and Launch Abort System, a roll control system, avionics, and other miscellaneous components. The vehicle was 327 feet tall and weighed approximately 1,800,000 pounds. During flight the rocket reached a maximum speed of Mach 4.8 and an altitude of 150,000 feet. The vehicle demonstrated staging at 130,000 feet, tested parachutes for recovery of the motor, and utilized approximately 900 sensors for data collection. Developing a new launch system and preparing for a safe flight presented many challenges. Specific challenges included designing a system to withstand the environments, manufacturing large structures, and re-qualifying heritage hardware. These and other challenges, if not mitigated, may have resulted in test cancellation. Ares I-X succeeded because the mission was founded on carefully derived objectives, led by decisive and flexible management, implemented by an exceptionally talented and dedicated workforce, and supported by a thorough independent review team. Other major success factors include the use of proven heritage hardware, a robust System Integration Laboratory, multi-NASA center and contractor team, concurrent operations, efficient vehicle assembly, effective risk management, and decentralized element development with a centralized control board. Ares I-X was a technically complex test that required creative thinking, risk taking, and a passion to succeed.

Askins, Bruce↗

ISS Regenerative Life Support: Challenges and Success in the Quest for Long-Term Habitability in Space

This presentation will discuss the International Space Station s (ISS) Regenerative Environmental Control and Life Support System (ECLSS) operations with discussion of the on-orbit lessons learned, specifically regarding the challenges that have been faced as the system has expanded with a growing ISS crew. Over the 10 year history of the ISS, there have been numerous challenges, failures, and triumphs in the quest to keep the crew alive and comfortable. Successful operation of the ECLSS not only requires maintenance of the hardware, but also management of the station resources in case of hardware failure or missed re-supply. This involves effective communication between the primary International Partners (NASA and Roskosmos) and the secondary partners (JAXA and ESA) in order to keep a reserve of the contingency consumables and allow for re-supply of failed hardware. The ISS ECLSS utilizes consumables storage for contingency usage as well as longer-term regenerative systems, which allow for conservation of the expensive resources brought up by re-supply vehicles. This long-term hardware, and the interactions with software, was a challenge for Systems Engineers when they were designed and require multiple operational workarounds in order to function continuously. On a day-to-day basis, the ECLSS provides big challenges to the on console controllers. Main challenges involve the utilization of the resources that have been brought up by the visiting vehicles prior to undocking, balance of contributions between the International Partners for both systems and resources, and maintaining balance between the many interdependent systems, which includes providing the resources they need when they need it. The current biggest challenge for ECLSS is the Regenerative ECLSS system, which continuously recycles urine and condensate water into drinking water and oxygen. These systems were brought to full functionality on STS-126 (ULF-2) mission. Through system failures and recovery, the ECLSS console has learned how to balance the water within the systems, store and use water for contingencies, and continue to work with the International Partners for short-term failures. Through these challenges and the system failures, the most important lesson learned has been the importance of redundancy and operational workarounds. It is only because of the flexibility of the hardware and the software that flight controllers have the opportunity to continue operating the system as a whole for mission success.

Bazley, Jesse A.↗

Full-Scaled Advanced Systems Testbed: Ensuring Success of Adaptive Control Research Through Project Lifecycle Risk Mitigation

The National Aeronautics and Space Administration's Dryden Flight Research Center completed flight testing of adaptive controls research on the Full-Scale Advance Systems Testbed (FAST) in January of 2011. The research addressed technical challenges involved with reducing risk in an increasingly complex and dynamic national airspace. Specific challenges lie with the development of validated, multidisciplinary, integrated aircraft control design tools and techniques to enable safe flight in the presence of adverse conditions such as structural damage, control surface failures, or aerodynamic upsets. The testbed is an F-18 aircraft serving as a full-scale vehicle to test and validate adaptive flight control research and lends a significant confidence to the development, maturation, and acceptance process of incorporating adaptive control laws into follow-on research and the operational environment. The experimental systems integrated into FAST were designed to allow for flexible yet safe flight test evaluation and validation of modern adaptive control technologies and revolve around two major hardware upgrades: the modification of Production Support Flight Control Computers (PSFCC) and integration of two, fourth-generation Airborne Research Test Systems (ARTS). Post-hardware integration verification and validation provided the foundation for safe flight test of Nonlinear Dynamic Inversion and Model Reference Aircraft Control adaptive control law experiments. To ensure success of flight in terms of cost, schedule, and test results, emphasis on risk management was incorporated into early stages of design and flight test planning and continued through the execution of each flight test mission. Specific consideration was made to incorporate safety features within the hardware and software to alleviate user demands as well as into test processes and training to reduce human factor impacts to safe and successful flight test. This paper describes the research configuration, experiment functionality, overall risk mitigation, flight test approach and results, and lessons learned of adaptive controls research of the Full-Scale Advanced Systems Testbed.

Pavlock, Kate M.↗

Capacitor-Chain Successive-Approximation ADC

A proposed successive-approximation analog-to-digital converter (ADC) would contain a capacitively terminated chain of identical capacitor cells. Like a conventional successive-approximation ADC containing a bank of binary-scaled capacitors, the proposed ADC would store an input voltage on a sample-and-hold capacitor and would digitize the stored input voltage by finding the closest match between this voltage and a capacitively generated sum of binary fractions of a reference voltage (Vref). However, the proposed capacitor-chain ADC would offer two major advantages over a conventional binary-scaled-capacitor ADC: (1) In a conventional ADC that digitizes to n bits, the largest capacitor (representing the most significant bit) must have 2(exp n-1) times as much capacitance, and hence, approximately 2(exp n-1) times as much area as does the smallest capacitor (representing the least significant bit), so that the total capacitor area must be 2(exp n) times that of the smallest capacitor. In the proposed capacitor-chain ADC, there would be three capacitors per cell, each approximately equal to the smallest capacitor in the conventional ADC, and there would be one cell per bit. Therefore, the total capacitor area would be only about 3(exp n) times that of the smallest capacitor. The net result would be that the proposed ADC could be considerably smaller than the conventional ADC. (2) Because of edge effects, parasitic capacitances, and manufacturing tolerances, it is difficult to make capacitor banks in which the values of capacitance are scaled by powers of 2 to the required precision. In contrast, because all the capacitors in the proposed ADC would be identical, the problem of precise binary scaling would not arise.

Cunningham, Thomas↗

The Application of Lean Thinking Principles and Kaizen Practices for the Successful Development and Implementation of the Ares I-X Flight Test Rocket and Mission

On October 28, 2009 the Ares I-X flight test rocket launched from Kennedy Space Center and flew its suborbital trajectory as designed. The mission was successfully completed as data from the test, and associated development activities were analyzed, transferred to stakeholders, and well documented. A positive lesson learned from Ares I-X was that the application of lean thinking principles and kaizen practices was very effective in streamlining development activities. Ares I-X, like other historical rocket development projects, was hampered by technical, cost, and schedule challenges and if not addressed boldly could have resulted in cancellation of the test. The mission management team conducted nine major meetings, referred to as lean events, across its elements to assess plans, procedures, processes, requirements, controls, culture, organization, use of resources, and anything that could be changed to optimize schedule or reduce risk. The preeminent aspect of the lean events was the focus on value added activities and the removal or at least reduction in non-value added activities. Trained Lean Six Sigma facilitators assisted the Ares I-X developers in conducting the lean events. They indirectly helped formulate the mission s own unique methodology for assessing schedule. A core team was selected to lead the events and report to the mission manager. Each activity leveraged specialized participants to analyze the subject matter and its related processes and then recommended alternatives and solutions. Stakeholders were the event champions. They empowered and encouraged the team to succeed. The keys to success were thorough preparation, honest dialog, small groups, adherence to the Ares I-X ground rules, and accountability through disciplined reporting and tracking of actions. This lean event formula was game-changing as demonstrated by Ares I-X. It is highly recommended as a management tool to help develop other complex systems efficiently. The key benefits for Ares I-X were obtaining unambiguous schedule margin, defining enabling options for risk reduction, and most importantly a stronger more unified team.

Askins, B. R.↗

Guidelines for Successful Use and Communication of Instrument Heritage in Early Mission Development with a Focus on Spectrometers

Heritage is important for both cost and risk related issues and as such, it is heavily discussed in NASA proposal evaluations. If used and communicated efficiently, heritage can lower both the perception of risk and the associated costs. Definitions of heritage vary between engineering, cost, and scientific communities, but when applied appropriately, heritage provides a benefit to the proposed mission. By making an instrument at least once before, the cost of producing it again can be reduced. The time and effort needed to develop the instrument concept and test the product represent an expense that can be lowered through the use of a previously built and developed instrument. This same thought can be applied when using a flight spare or build-to-print model of the heritage instrument. The lowered perception of risk is a result of the confidence gained in the instrument through successful use in the target environment. This is extremely important in early mission development to the evaluation board. This analysis will use JPL-managed proposals from 2003 to 2011, including Discovery, New Frontiers, and Mars Scout missions. Through the examination of these proposals and their associated debriefs, a set of guidelines have been created for successful use and communication of instrument heritage in early mission development

specrtometers↗

V&V of Fault Management: Challenges and Successes

This paper describes the results of a special breakout session of the NASA Independent Verification and Validation (IV&V) Workshop held in the fall of 2012 entitled "V&V of Fault Management: Challenges and Successes." The NASA IV&V Program is in a unique position to interact with projects across all of the NASA development domains. Using this unique opportunity, the IV&V program convened a breakout session to enable IV&V teams to share their challenges and successes with respect to the V&V of Fault Management (FM) architectures and software. The presentations and discussions provided practical examples of pitfalls encountered while performing V&V of FM including the lack of consistent designs for implementing faults monitors and the fact that FM information is not centralized but scattered among many diverse project artifacts. The discussions also solidified the need for an early commitment to developing FM in parallel with the spacecraft systems as well as clearly defining FM terminology within a project.

Verification↗

Cassini's Maneuver Automation Software (MAS) Process: How to Successfully Command 200 Navigation Maneuvers

To keep Cassini on its complex trajectory, more than 200 orbit trim maneuvers (OTMs) have been planned from July 2004 to July 2010. With only a few days between many of these OTMs, the operations process of planning and executing the necessary commands had to be automated. The resulting Maneuver Automation Software (MAS) process minimizes the workforce required for, and maximizes the efficiency of, the maneuver design and uplink activities. The MAS process is a well-organized and logically constructed interface between Cassini's Navigation (NAV), Spacecraft Operations (SCO), and Ground Software teams. Upon delivery of an orbit determination (OD) from NAV, the MAS process can generate a maneuver design and all related uplink and verification products within 30 minutes. To date, all 112 OTMs executed by the Cassini spacecraft have been successful. MAS was even used to successfully design and execute a maneuver while the spacecraft was in safe mode.

Yang, Genevie Velarde↗

Successful Validation of RNA Purification and Quantitative Real-Time PCR Analysis of Gene Expression on the International Space Station

The NASA Ames WetLab-2 system was developed to offer new on-orbit gene expression analysis capabilities to ISS researchers and can be used to conduct on-orbit RNA isolation and quantitative real time PCR (RT-qPCR) analysis of gene expression from a wide range of biological samples ranging from microbes to mammalian tissues. On orbit validation included three quantitative PCR (qPCR) runs using an E. coli genomic DNA template pre-loaded at three different concentrations. The flight Ct values for the DNA standards showed no statistically significant differences relative to ground controls although there was increased noise in Ct curves, likely due to microgravity-related bubble retention in the optical windows. RNA was successfully purified from both E. coli and mouse liver samples and successfully generated singleplex, duplex and triplex data although with higher standard deviations than ground controls, also likely due to bubbles. Using volunteer science activities, a potential bubble reduction strategy was tested and resulted in smooth amplification curves and tighter Cts between replicates. The WetLab-2 validation experiment demonstrates a novel molecular biology workbench on ISS which allows scientists to purify and stabilize RNA, and to conduct RT-qPCR analyses on-orbit with rapid results. This novel ability is an important step towards utilizing ISS as a National Laboratory facility with the capability to conduct and adjust science experiments in real time without sample return, and opens new possibilities for rapid medical diagnostics and biological environmental monitoring on ISS.

microgravity↗

Success of Montreal Protocol Demonstrated by Comparing High-Quality UV Measurements with “World Avoided” Calculations from Two Chemistry-Climate Models

The Montreal protocol on Substances that Deplete the ozone Layer has been hailed as the most successful environmental treaty ever (https://www.unenvironment.org/news-and-stories/story/montreal-protocol-triumph-treaty). Yet, although our main concern about ozone depletion is the subsequent increase in harmful solar UV radiation at the earth’s surface, no studies to date have demonstrated its effectiveness in that regard. Here we use long-term UV Index (UVI) data derived from high-quality UV spectroradiometer measurements to demonstrate its success in curbing increases in UV radiation. Without this landmark agreement, UVi values would have increased at mid-latitude locations by approximately 20% between the early 1990s and today and would approximately quadruple at mid-latitudes by 2100. In contrast, an analysis of UVI data from multiple clean-air sites shows that maximum daily UVI values have remained essentially constant over the last ~20 years in all seasons, and may even have decreased slightly in the southern hemisphere, especially in Antarctica, where effects of ozone depletion were larger. Reconstructions of the UVi from total ozone data show evidence of increasing UVI levels in the 1980s, but unfortunately, there are no high-quality UV measurements available prior to the early 1990s to confirm these increases with direct observations.

UV Index (UVI) data derived from high-quality UV s↗