Search NASA⌕ Search

SEARCH · Search NASA

Results for “ISS Program”

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 73 records · Page 4

Lessons Learned in Developing Multiple Distributed Planning Systems for the International Space Station

The planning processes for the International Space Station (ISS) Program are quite complex. Detailed mission planning for ISS on-orbit operations is a distributed function. Pieces of the on-orbit plan are developed by multiple planning organizations, located around the world, based on their respective expertise and responsibilities. The pieces are then integrated to yield the final detailed plan that will be executed onboard the ISS. Previous space programs have not distributed the planning and scheduling functions to this extent. Major ISS planning organizations are currently located in the United States (at both the NASA Johnson Space Center (JSC) and NASA Marshall Space Flight Center (MSFC)), in Russia, in Europe, and in Japan. Software systems have been developed by each of these planning organizations to support their assigned planning and scheduling functions. Although there is some cooperative development and sharing of key software components, each planning system has been tailored to meet the unique requirements and operational environment of the facility in which it operates. However, all the systems must operate in a coordinated fashion in order to effectively and efficiently produce a single integrated plan of ISS operations, in accordance with the established planning processes. This paper addresses lessons learned during the development of these multiple distributed planning systems, from the perspective of the developer of one of the software systems. The lessons focus on the coordination required to allow the multiple systems to operate together, rather than on the problems associated with the development of any particular system. Included in the paper is a discussion of typical problems faced during the development and coordination process, such as incompatible development schedules, difficulties in defining system interfaces, technical coordination and funding for shared tools, continually evolving planning concepts/requirements, programmatic and budget issues, and external influences. Techniques that mitigated some of these problems will also be addressed, along with recommendations for any future programs involving the development of multiple planning and scheduling systems. Many of these lessons learned are not unique to the area of planning and scheduling systems, so may be applied to other distributed ground systems that must operate in concert to successfully support space mission operations.

Maxwell, Theresa G.↗

Benefits of International Collaboration on the International Space Station

The International Space Station is a valuable platform for research in space, but the benefits are limited if research is only conducted by individual countries. Through the e orts of the ISS Program Science Forum, international science working groups, and interagency cooperation, international collaboration on the ISS has expanded as ISS utilization has matured. Members of science teams benefit from working with counterparts in other countries. Scientists and institutions bring years of experience and specialized expertise to collaborative investigations, leading to new perspectives and approaches to scientific challenges. Combining new ideas and historical results brings synergy and improved peer-reviewed scientific methods and results. World-class research facilities can be expensive and logistically complicated, jeopardizing their full utilization. Experiments that would be prohibitively expensive for a single country can be achieved through contributions of resources from two or more countries, such as crew time, up- and downmass, and experiment hardware. Cooperation also avoids duplication of experiments and hardware among agencies. Biomedical experiments can be completed earlier if astronauts or cosmonauts from multiple agencies participate. Countries responding to natural disasters benefit from ISS imagery assets, even if the country has no space agency of its own. Students around the world participate in ISS educational opportunities, and work with students in other countries, through open curriculum packages and through international competitions. Even experiments conducted by a single country can benefit scientists around the world, through specimen sharing programs and publicly accessible \open data" repositories. For ISS data, these repositories include GeneLab, the Physical Science Informatics System, and different Earth science data systems. Scientists can conduct new research using ISS data without having to launch and execute their own experiments. Multilateral collections of research results publications, maintained by the ISS international partnership and accessible via nasa.gov, make ISS results available worldwide, and encourage new users, ideas and research. The paper explores effectiveness of international collaboration in the course of the ISS Program execution. The collaboration history, its evolution and maturation, change of focus during its different phases, and growth of its effectiveness (in accordance with the especially established criteria) are also considered in the paper in the light of benefits for the entire ISS community. With the International Space Station extended through at least 2024, more crew time becoming available and new facilities arriving on board the ISS, these benefits of international scientific collaboration on the ISS can only increase.

Robinson, Julie A.↗

Safety Review Process: International Space Station Program (Revision F)

The International Space Station (ISS) Program has developed a safety review process to execute its responsibilities for the overall integrated safety of the ISS. This process will assess the design and operations of the ISS hardware/elements(including visiting vehicles during integrated ISS operations)and its ground support equipment in accordance with the applicable safety requirements as specified in Section2.0.

ISS↗

Space Shuttle Program (SSP) Dual Docked Operations (DDO)

This document describes the concept definition, studies, and analysis results generated by the Space Shuttle Program (SSP), International Space Station (ISS) Program (ISSP), and Mission Operations Directorate for implementing Dual Docked Operations (DDO) during mated Orbiter/ISS missions. This work was performed over a number of years. Due to the ever increasing visiting vehicle traffic to and from the ISS, it became apparent to both the ISSP and the SSP that there would arise occasions where conflicts between a visiting vehicle docking and/or undocking could overlap with a planned Space Shuttle launch and/or during docked operations. This potential conflict provided the genesis for evaluating risk mitigations to gain maximum flexibility for managing potential visiting vehicle traffic to and from the ISS and to maximize launch and landing opportunities for all visiting vehicles.

Sills, Joel W., Jr.↗

Using Distributed Operations to Enable Science Research on the International Space Station

In the early days of the International Space Station (ISS) program, and as the organization structure was being internationally agreed upon and documented, one of the principal tenets of the science program was to allow customer-friendly operations. One important aspect of this was to allow payload developers and principle investigators the flexibility to operate their experiments from either their home sites or distributed telescience centers. This telescience concept was developed such that investigators had several options for ISS utilization support. They could operate from their home site, the closest telescience center, or use the payload operations facilities at the Marshall Space Flight Center in Huntsville, Alabama. The Payload Operations Integration Center (POIC) processes and structures were put into place to allow these different options to its customers, while at the same time maintain its centralized authority over NASA payload operations and integration. For a long duration space program with many scientists, researchers, and universities expected to participate, it was imperative that the program structure be in place to successfully facilitate this concept of telescience support. From a payload control center perspective, payload science operations require two major elements in order to make telescience successful within the scope of the ISS program. The first element is decentralized control which allows the remote participants the freedom and flexibility to operate their payloads within their scope of authority. The second element is a strong ground infrastructure, which includes voice communications, video, telemetry, and commanding between the POIC and the payload remote site. Both of these elements are important to telescience success, and both must be balanced by the ISS program s documented requirements for POIC to maintain its authority as an integration and control center. This paper describes both elements of distributed payload operations and discusses the benefits and drawbacks.

Bathew, Ann S.↗

The Role of Independent Assessment in the International Space Station Program

This paper presents the role of Independent Assessment in the International Space Station (ISS) Program. Independent Assessment is responsible for identifying and specifying technical and programmatic risks that may impact development, launch, and on-orbit assembly and operations of the ISS. The various phases of the assessment process are identified and explained. This paper also outlines current and future participation by Independent Assessment in Human Exploration and Development of Space projects including the X-38 Space Plane, Mars mission scenarios, and applications of Nanotechnology. This paper describes how Independent Assessment helps the shuttle, ISS, and other programs to safely achieve mission goals now and into the next century.

Strachan, Russell L.↗

Utilizing the ISS Mission as a Testbed to Develop Cognitive Communications Systems

The ISS provides an excellent opportunity for pioneering artificial intelligence software to meet the challenges of real-time communications (comm) link management. This opportunity empowers the ISS Program to forge a testbed for developing cognitive communications systems for the benefit of the ISS mission, manned Low Earth Orbit (LEO) science programs and future planetary exploration programs. In November, 1998, the Flight Operations Directorate (FOD) started the ISS Antenna Manager (IAM) project to develop a single processor supporting multiple comm satellite tracking for two different antenna systems. Further, the processor was developed to be highly adaptable as it supported the ISS mission through all assembly stages. The ISS mission mandated communications specialists with complete knowledge of when the ISS was about to lose or gain comm link service. The current specialty mandated cognizance of large sun-tracking solar arrays and thermal management panels in addition to the highly-dynamic satellite service schedules and rise/set tables. This mission requirement makes the ISS the ideal communications management analogue for future LEO space station and long-duration planetary exploration missions. Future missions, with their precision-pointed, dynamic, laser-based comm links, require complete autonomy for managing high-data rate communications systems. Development of cognitive communications management systems that permit any crew member or payload science specialist, regardless of experience level, to control communications is one of the greater benefits the ISS can offer new space exploration programs. The IAM project met a new mission requirement never previously levied against US space-born communications systems management: process and display the orientation of large solar arrays and thermal control panels based on real-time joint angle telemetry. However, IAM leaves the actual communications availability assessment to human judgment, which introduces unwanted variability because each specialist has a different core of experience with comm link performance. Because the ISS utilizes two different frequency bands, dynamic structure can be occasionally translucent at one frequency while it can completely interdict service at the other frequency. The impact of articulating structure on the comm link can depend on its orientation at the time it impinges on the link. It can become easy for a human specialist to cross-associate experience at one frequency with experience at the other frequency. Additionally, the specialist's experience is incremental, occurring one nine-hour shift at a time. Only the IAM processor experiences the complete 24x7x365 communications link performance for both communications links but, it has no "learning capability." If the IAM processor could be endowed with a cognitive ability to remember past structure-induced comm link outages, based on its knowledge of the ISS position, attitude, communications gear, array joint angles and tracking accuracy, it could convey such experience to the human operator. It could also use its learned communications link behaviors to accurately convey the availability of future communications sessions. Further, the tool could remember how accurately or inaccurately it predicted availability and correct future predictions based on past performance. The IAM tool could learn frequency-specific impacts due to spacecraft structures and pass that information along as "experience." Such development would provide a single artificial intelligence processor that could provide two different experience bases. If it also "knew" the satellite service schedule, it could distinguish structure blockage from schedule or planet blockage and then quickly switch to another satellite. Alternatively, just as a human operator could judge, a cognizant comm system based on the IAM model could "know" that the blockage is not going to last very long and continue tracking a comm satellite, waiting for it to track away from structure. Ultimately, once this capability was fully developed and tested in the Mission Control Center, it could be transferred on-orbit to support development of operations concepts that include more advanced cognitive communications systems. Future applications of this capability are easily foreseen because even more dynamic satellite constellations with more nodes and greater capability are coming. Currently, the ISS fully employs a 300 million bit-per-second (Mbps) return link for harvesting payload science. In the coming eighteen months, it will step up to 600 Mbps. Already there is talk of a 1.2 billion bit-per-second (Gbps) upgrade for the ISS and laser comm links have already been tested from the ISS. Every data rate upgrade mandates more complicated and sensitive communications equipment which implies greater expertise invested in the human operator. Future on-orbit cognizant comm systems will be needed to meet greater performance demands aboard larger, far more complicated spacecraft. In the LEO environment, the old-style one-satellite-per-spacecraft operations concept will give way to a new concept of a single customer spacecraft simultaneously using multiple comm satellites. Much more highly-dynamic manned LEO missions with decades of crew members potentially increase the demand for communications link performance. A cognizant on-board communications system will meet advanced communications demands from future LEO missions and future planetary missions. The ISS has fledgling components of future exploration programs, both LEO and planetary. Further, the Flight Operations Directorate, through the IAM project, has already begun to develop a communications management system that attempts to solve advanced problems ideally represented by dynamic structure impacting scheduled satellite service. With an earnest project to integrate artificial intelligence into the IAM processor, the ISS Program could develop a cognizant communications system that could be adapted and transferred to future on-orbit avionics designs.

Jackson, Dan↗

Utilizing the ISS Mission as a Testbed to Develop Cognitive Communications Systems

The ISS provides an excellent opportunity for pioneering artificial intelligence software to meet the challenges of real-time communications (comm) link management. This opportunity empowers the ISS Program to forge a testbed for developing cognitive communications systems for the benefit of the ISS mission, manned Low Earth Orbit (LEO) science programs and future planetary exploration programs. In November, 1998, the Flight Operations Directorate (FOD) started the ISS Antenna Manager (IAM) project to develop a single processor supporting multiple comm satellite tracking for two different antenna systems. Further, the processor was developed to be highly adaptable as it supported the ISS mission through all assembly stages. The ISS mission mandated communications specialists with complete knowledge of when the ISS was about to lose or gain comm link service. The current specialty mandated cognizance of large sun-tracking solar arrays and thermal management panels in addition to the highly-dynamic satellite service schedules and rise/set tables. This mission requirement makes the ISS the ideal communications management analogue for future LEO space station and long-duration planetary exploration missions. Future missions, with their precision-pointed, dynamic, laser-based comm links, require complete autonomy for managing high-data rate communications systems. Development of cognitive communications management systems that permit any crew member or payload science specialist, regardless of experience level, to control communications is one of the greater benefits the ISS can offer new space exploration programs. The IAM project met a new mission requirement never previously levied against US space-born communications systems management: process and display the orientation of large solar arrays and thermal control panels based on real-time joint angle telemetry. However, IAM leaves the actual communications availability assessment to human judgement, which introduces unwanted variability because each specialist has a different core of experience with comm link performance. Because the ISS utilizes two different frequency bands, dynamic structure can be occasionally translucent at one frequency while it can completely interdict service at the other frequency. The impact of articulating structure on the comm link can depend on its orientation at the time it impinges on the link. It can become easy for a human specialist to cross-associate experience at one frequency with experience at the other frequency. Additionally, the specialist's experience is incremental, occurring one nine-hour shift at a time. Only the IAM processor experiences the complete 24x7x365 communications link performance for both communications links but, it has no "learning capability." If the IAM processor could be endowed with a cognitive ability to remember past structure-induced comm link outages, based on its knowledge of the ISS position, attitude, communications gear, array joint angles and tracking accuracy, it could convey such experience to the human operator. It could also use its learned communications link behaviors to accurately convey the availability of future communications sessions. Further, the tool could remember how accurately or inaccurately it predicted availability and correct future predictions based on past performance. The IAM tool could learn frequency-specific impacts due to spacecraft structures and pass that information along as "experience." Such development would provide a single artificial intelligence processor that could provide two different experience bases. If it also "knew" the satellite service schedule, it could distinguish structure blockage from schedule or planet blockage and then quickly switch to another satellite. Alternatively, just as a human operator could judge, a cognizant comm system based on the IAM model could "know" that the blockage is not going to last very long and continue tracking a comm satellite, waiting for it to track away from structure. Ultimately, once this capability was fully developed and tested in the Mission Control Center, it could be transferred on-orbit to support development of operations concepts that include more advanced cognitive communications systems. Future applications of this capability are easily foreseen because even more dynamic satellite constellations with more nodes and greater capability are coming. Currently, the ISS fully employs its high-data-rate return link for harvesting payload science. In the coming months, it will double that data rate and is forecast to fully utilize that capability. Already there is talk of an upgrade that quadruples the current data rate allocated to ISS payload science before the end of its mission and laser comm links have already been tested from the ISS. Every data rate upgrade mandates more complicated and sensitive communications equipment which implies greater expertise invested in the human operator. Future on-orbit cognizant comm systems will be needed to meet greater performance demands aboard larger, far more complicated spacecraft. In the LEO environment, the old-style one-satellite-per-spacecraft operations concept will give way to a new concept of a single customer spacecraft simultaneously using multiple comm satellites. Much more highly-dynamic manned LEO missions with decades of crew members potentially increase the demand for communications link performance. A cognizant on-board communications system will meet advanced communications demands from future LEO missions and future planetary missions. The ISS has fledgling components of future exploration programs, both LEO and planetary. Further, the Flight Operations Directorate, through the IAM project, has already begun to develop a communications management system that attempts to solve advanced problems ideally represented by dynamic structure impacting scheduled satellite service. With an earnest project to integrate artificial intelligence into the IAM processor, the ISS Program could develop a cognizant communications system that could be adapted and transferred to future on-orbit avionics designs.

Jackson, Dan↗

International Space Station ECLSS Technical Task Agreement Summary Report

This Technical Memorandum provides a summary of current work accomplished under Technical Task Agreement (TTA) by the Marshall Space Flight Center (MSFC) regarding the International Space Station (ISS) Environmental Control and Life Support System (ECLSS). Current activities include ECLSS component design and development, computer model development, subsystem/integrated system testing, life testing, and general test support provided to the ISS program. Under ECLSS design, MSFC was responsible for the six major ECLSS functions, specifications and standard, component design and development, and was the architectural control agent for the ISS ECLSS. MSFC was responsible for ECLSS analytical model development. In-house subsystem and system level analysis and testing were conducted in support of the design process, including testing air revitalization, water reclamation and management hardware, and certain nonregenerative systems. The activities described herein were approved in task agreements between MSFC and NASA Headquarters Space Station Program Management Office and their prime contractor for the ISS, Boeing. These MSFC activities are in line to the designing, development, testing, and flight of ECLSS equipment planned by Boeing. MSFC's unique capabilities for performing integrated systems testing and analyses, and its ability to perform some tasks cheaper and faster to support ISS program needs, are the basis for the TTA activities.

Ray, C. D.↗

Producing a Live HDTV Program from Space

By the year 2000, NASA had flown HDTV camcorders on three Space Shuttle missions: STS-95, STS-93 and STS-99. All three flights of these camcorders were accomplished with cooperation from the Japanese space agency (then known as NASDA and now known as JAXA). The cameras were large broadcast-standard cameras provided by NASDA and flight certified by both NASA and NASDA. The high-definition video shot during these missions was spectacular. Waiting for the return of the tapes to Earth emphasized the next logical step: finding a way to downlink the HDTV live from space. Both the Space Shuttle and the International Space Station (ISS) programs were interested in live HDTV from space, but neither had the resources to fully fund the technology. Technically, downlinking from the ISS was the most effective approach. Only when the Japanese broadcaster NHK and the Japanese space agency expressed interest in covering a Japanese astronaut's journey to the ISS did the project become possible. Together, JAXA and NHK offered equipment, technology, and funding toward the project. In return, NHK asked for a live HDTV downlink during one of its broadcast programs. NASA and the ISS Program sought a US partner to broadcast a live HDTV program and approached the Discovery Channel. The Discovery Channel had proposed a live HDTV project in response to NASA's previous call for offers. The Discovery Channel agreed to provide addItional resources. With the final partner in place, the project was under way. Engineers in the Avionics Systems Division at NASA's Johnson Space Center (JSC) had already studied the various options for downlinking HDTV from the ISS. They concluded that the easiest way was to compress the HDTV so that the resulting data stream would "look" like a payload data stream. The flight system would consist of a professional HDTV camcorder with live HD-SDI output, an HDTV MPEG-2 encoder, and a packetizer/protocol converter.

Grubbs, Rodney↗

Quo Vadis Payload Safety?

As we complete the preparations for the fourth Hubble Space Telescope (HST) servicing mission, we note an anniversary approaching: it was 30 years ago in July that the first HST payload safety review panel meeting was held. This, in turn, was just over a year after the very first payload safety review, a Phase 0 review for the Tracking and Data Relay Satellite and its Inertial Upper Stage, held in June of 1977. In adapting a process that had been used in the review and certification of earlier Skylab payloads, National Aeronautics and Space Administration (NASA) engineers sought to preserve the lessons learned in the development of technical payload safety requirements, while creating a new process that would serve the very different needs of the new space shuttle program. Their success in this undertaking is substantiated by the fact that this process and these requirements have proven to be remarkably robust, flexible, and adaptable. Furthermore, the payload safety process has, to date, served us well in the critical mission of safeguarding our astronauts, cosmonauts, and spaceflight participants. Both the technical requirements and their interpretation, as well as the associated process requirements have grown, evolved, been streamlined, and have been adapted to fit multiple programs, including the International Space Station (ISS) program, the Shuttle/Mir program, and most recently the United States Constellation program. From its earliest days, it was anticipated that the payload safety process would be international in scope, and so it has been. European Space Agency (ESA), Japan Aerospace Exploration Agency (JAXA), German Space Agency (DLR), Canadian Space Agency (CSA), Russian Space Agency (RSA), and many additional countries have flown payloads on both the space shuttle and on the ISS. Our close cooperation and long-term working relationships have culminated in the franchising of the payload safety review process itself to our partners in ESA, which in turn will serve as a roadmap for extending the franchise to other Partners.

Fodroci, Michael P.↗

International space station wire program

Hardware provider wire systems and current wire insulation issues for the International Space Station (ISS) program are discussed in this viewgraph presentation. Wire insulation issues include silicone wire contamination, Tefzel cold temperature flexibility, and Russian polyimide wire insulation. ISS is a complex program with hardware developed and managed by many countries and hundreds of contractors. Most of the obvious wire insulation issues are known by contractors and have been precluded by proper selection.

May, Todd↗

NASA Human Spaceflight Overview

Current Human Space Flight Programs: a) Space Shuttle Program (SSP); b) International Space Station (ISS) Program; c) Constellation Program (CxP).

Blackburn, Gregory C.↗

International Space Station Instmments Collect Imagery of Natural Disasters

A new focus for utilization of the International Space Station (ISS) is conducting basic and applied research that directly benefits Earth's citizenry. In the Earth Sciences, one such activity is collecting remotely sensed imagery of disaster areas and making those data immediately available through the USGS Hazards Data Distribution System, especially in response to activations of the International Charter for Space and Major Disasters (known informally as the "International Disaster Charter", or IDC). The ISS, together with other NASA orbital sensor assets, responds to IDC activations following notification by the USGS. Most of the activations are due to natural hazard events, including large floods, impacts of tropical systems, major fires, and volcanic eruptions and earthquakes. Through the ISS Program Science Office, we coordinate with ISS instrument teams for image acquisition using several imaging systems. As of 1 August 2013, we have successfully contributed imagery data in support of 14 Disaster Charter Activations, including regions in both Haiti and the east coast of the US impacted by Hurricane Sandy; flooding events in Russia, Mozambique, India, Germany and western Africa; and forest fires in Algeria and Ecuador. ISS‐based sensors contributing data include the Hyperspectral Imager for the Coastal Ocean (HICO), the ISERV (ISS SERVIR Environmental Research and Visualization System) Pathfinder camera mounted in the US Window Observational Research Facility (WORF), the ISS Agricultural Camera (ISSAC), formerly operating from the WORF, and high resolution handheld camera photography collected by crew members (Crew Earth Observations). When orbital parameters and operations support data collection, ISS‐based imagery adds to the resources available to disaster response teams and contributes to the publicdomain record of these events for later analyses.

Evans, C. A.↗

Logistics Reduction: RFID Enabled Autonomous Logistics Management (REALM) (LR-REALM)

The Advanced Exploration Systems (AES) Logistics Reduction (LR) project Radio-frequency identification (RFID) Enabled Autonomous Logistics Management (REALM) task focuses on the subset of autonomous logistics management functions pertaining to automated localization and inventory of all physical assets pertaining to, or within, a vehicle utilizing RFID technologies. REALM technology can provide detailed data to enable autonomous operations such as automated crew procedure generation and robotic interaction with logistics and deep space habitats; this is especially of value where communication delays with Earth drive the need for self-reliance. The REALM project will conduct a series of ISS technology demonstrations. The first ISS demonstration, REALM-1, started in February 2017 and was completed at the end of FY19 when it was transitioned to the ISS program for sustaining operations. The second ISS demonstration, REALM-2, started late2019 and will continue for at least one year.

NASA TechPort↗

A Ground Systems Architecture Transition for A Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the ISS payloads program, and the resulting functional breakdown of the products that support that architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗

A Ground Systems Architecture Transition for a Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the International Space Station (ISS) payloads program, and the resulting functional breakdown of the products that support this architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗

Java Mission Evaluation Workstation System

The Java Mission Evaluation Workstation System (JMEWS) is a collection of applications designed to retrieve, display, and analyze both real-time and recorded telemetry data. This software is currently being used by both the Space Shuttle Program (SSP) and the International Space Station (ISS) program. JMEWS was written in the Java programming language to satisfy the requirement of platform independence. An object-oriented design was used to satisfy additional requirements and to make the software easily extendable. By virtue of its platform independence, JMEWS can be used on the UNIX workstations in the Mission Control Center (MCC) and on office computers. JMEWS includes an interactive editor that allows users to easily develop displays that meet their specific needs. The displays can be developed and modified while viewing data. By simply selecting a data source, the user can view real-time, recorded, or test data.

Pettinger, Ross↗