Search NASA⌕ Search

SEARCH · Search NASA

Results for “co-ops”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1978

A New Look For Greenbelt

Greenbelt, Maryland, 12 miles from the nation's capital, is an efficiently planned model town and most of its 1600 homes are almost identical in appearance. Four of them, however, stand out from their neighbors; they have distinctive blue glass rooftop superstructures made up of a series of solar collectors. They are part of a NASA community aid program, a joint energy research project involving the Greenbelt housing cooperative and NASA's Goddard Space Flight Center, located near the community. Built in 1935, Greenbelt is one of three government-planned communities of President Franklin D. Roosevelt's first administration; the others are Greendale, Wisconsin and Greenhills, Ohio. The government built the towns to make available low-cost housing, provide employment for workers on relief in the Great Depression era, and to establish models designed to encourage construction of similar developments by private industry. In 1952, the residents of Greenbelt formed a nonprofit cooperative called Greenbelt Homes, Inc., which bought the dwellings, facilities and a large part of the land from the government. The homes are individually owned but collectively maintained by the co-op, with each owner paying a prorated share of utility and maintenance costs. Greenbelt residents are mostly in the low and medium income brackets, and one of every three families lives on a fixed retirement income. For that reason, the sharp escalation of fuel oil prices that began in 1973 imposed particular hardship on the co-op community. So Greenbelt Homes' management asked its NASA neighbor, Goddard Space Flight Center, for assistance in setting up a solar energy research project. The idea was to conduct a small scale demonstration to show what savings could be realized by solar heating Greenbelt homes, with an eye toward possible future expansion of solar energy systems as a means of combating rising fuel costs. Goddard undertook the project as part of the federal government's effort to research and demonstrate ways of conserving energy. The Center was well qualified for the assignment, having acquired extensive expertise in designing thermal control systems for satellites, which must maintain stable temperatures for successful operation.

Source record↗
NASA NTRS2009

Preliminary Evaluation of the AFWA-NASA (ANSA) Blended Snow-Cover Product over the Lower Great Lakes Region

The Air Force Weather Agency (AFWA) - NASA (ANSA) blended-snow product utilizes EOS standard snow products from the Moderate-Resolution Imaging Spectroradiometer (MODIS) and the Advanced Microwave Scanning Radiometer for EOS (AMSR-E) to map daily snow cover and snow-water equivalent (SWE) globally. We have compared ANSA-derived SWE. with SWE values calculated from snow depths reported at approx.1500 National Climatic Data Center (NCDC) coop stations in the Lower Great Lakes basin. Our preliminary results show that conversion of snow depth to SWE is very sensitive to the choice of snow density (we used either 0.2 or 03 as conversion factors). We found overall better agreement between the ANSA-derived SWE and the co-op station data when we use a snow density of 0.3 to convert the snow depths to SWE. In addition, we show that the ANSA underestimates SWE in densely-forested areas, using January and February 2008 ANSA and co-op data. Furthermore, apparent large SWE changes from one day to the next may be caused by thaw-re-freeze events, and do not always represent a real change in SWE. In the near future we will continue the analysis in the 2006-07 and 2007-08 snow seasons.

Hall, Dorothy K.↗
NASA NTRS2015

[Fall 2015 Abstract by Stephanie Scharf]

This Fall I worked on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the Branch. The purpose of this document is to create a standard process and ensure that the data is collected in the same way, no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own, all while taking notes on the procedure. These notes were used to write the final work instruction, which will become the Branch standard. My second project continued the work of the Summer co-op before me. I tested aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks had been designed by the previous Summer co-op, but there was not much time for testing before he left. We thus ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (Energy Systems Test Area) and are providing very promising results, indicating that safe, high performing (>180 Wh/kg) designs are possible. My main project was a redesign of the LLB (Lightweight Lithium Battery). Another summer intern had done some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the existing design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density, and the rest of the design was up to me. First, I created new heat sink banks in CREO, using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place, and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve > 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options for cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan was to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Cutting open a cell for DPA After photo from oven heat-to-vent test

Scharf, Stephanie↗
DOE OSTI2024

Electric Grid and Markets 101 [Slides]

This presentation covers aspects of operating the bulk power system with a focus on the regulatory levels of the US grid at a pretty introductory level. It was meant ot help inform a request from USDA for a "101" presentation that spoke to how electricity markets, contracting and regulation interact with the engineering and physics of operating the bulk power system. They are presently moving to being able to more directly fund PPAs or other non-co-op owned assets for member co-ops, is my understanding.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS1989

Lincoln Advanced Science and Engineering Reinforcement (LASER) program

Lincoln University, under the Lincoln Advanced Science and Engineering Reinforcement (LASER) Program, has identified and successfully recruited over 100 students for majors in technical fields. To date, over 70 percent of these students have completed or will complete technical degrees in engineering, physics, chemistry, and computer science. Of those completing the undergraduate degree, over 40 percent have gone on to graduate and professional schools. This success is attributable to well planned approaches to student recruitment, training, personal motivation, retention, and program staff. Very closely coupled to the above factors is a focus designed to achieve excellence in program services and student performance. Future contributions by the LASER Program to the pool of technical minority graduates will have a significant impact. This is already evident from the success of the students that began the first year of the program. With program plans to refine many of the already successful techniques, follow-on activities are expected to make even greater contributions to the availability of technically trained minorities. For example, undergraduate research exposure, broadened summer, and co-op work experiences will be enhanced.

Williams, Willie E.↗
NASA NTRS1994

On the Use of Computers for Teaching Fluid Mechanics

Several approaches for improving the teaching of basic fluid mechanics using computers are presented. There are two objectives to these approaches: to increase the involvement of the student in the learning process and to present information to the student in a variety of forms. Items discussed include: the preparation of educational videos using the results of computational fluid dynamics (CFD) calculations, the analysis of CFD flow solutions using workstation based post-processing graphics packages, and the development of workstation or personal computer based simulators which behave like desk top wind tunnels. Examples of these approaches are presented along with observations from working with undergraduate co-ops. Possible problems in the implementation of these approaches as well as solutions to these problems are also discussed.

Benson, Thomas J.↗
NASA NTRS2004

My Work in the NASA Glenn History Office and Records Management Office

This is my fourth summer working with my mentor, Kevin P. Coleman, who is the Center History Coordinator, Center Records Manager, and Center Forms Manager. I am working in the GRC History Office with some overlap in the Records Management Office. I have three major projects this summer. First, I am assisting in the documentation of historic facilities. Second, I am involved in a project to organize files and create an archives at Plum Brook Station. Third, I have helped the records management office with its inventory of stored records at Plum Brook. Also, I received an award this summer for research work I had done for NASA in the past. First, my primary project is to help assemble documentation for historic facilities at Glenn. This is somewhat of an extension of my project from last summer. Last summer, I worked to compile a complete list of all of NASA s historic sites and landmarks (as designated by the National Park Service, as well as several private organizations) throughout the country. Then, I briefly researched the significance of historic designation under federal law. Finally, I put my findings into a report which was submitted to NASA Headquarters. Upon review by the NASA History Office and several center-level history officials, it was decided that NASA should work to update its documentation of its historic sites and landmarks since some of the documentation was outdated or unavailable. Until recently, many project managers and facility managers working at historic facilities were not even aware that their surroundings had been designated as historic under federal law (most specifically, the National Historic Preservation Act of 1966 and its amendments). Therefore, they were unaware of the legal obligations for historic preservation. This summer, my project is to research some of Glenn s historic sites and landmarks in more detail. The goal is to put together a template for documenting historic NASA facilities. The hope is that this template of requirements for historic documentation of facilities (which may include records, drawings, photos, film, interviews, and a Web site) can be used agency-wide to assist center history offices in documenting historic sites and landmarks. To this end, I am working with Bob Arrighi, an archivist from InDyne, Inc., and Anne Burke, a NASA co-op, to gather and assess the historic value of records from several facilities at Glenn and Plum Brook Station. We will also work to determine the costs of each part of the template.

Mate, Robert C.↗
NASA NTRS2010

The Process of the Development of an Operator

On the job training is where new employees called operators can start gaining knowledge on what they will be working on during their time in JSC. In these lessons I learned different things that are important ranging from thermal systems to electrical systems. While doing OJT classes the student will learn how to use a portable computer system which has displays that I also helped edit and clean up. The way you can also learn is by reading system briefs which describes the different systems. Due to the fact of a possible change in the ISS I updated a systems brief so that it can be relevant to what is actually on the space station. I was given a task that will help develop my skills and make myself better prepared for my future in the work field. The project that I worked on had me pulling real time data from the International Space Station. The Data I obtained from the space station will be correlated to battery performance. The group I will be working which is called REBA and we will take the telemetry and evaluate the data. I will be working with my mentor Ben Chislom and co-op Tyler along with the Pro team. They then will put this data into a graph so that they can get the discrepancies and find a way to improve the battery performance. The first weeks I read familiarization books that informed me how the ISS works, how it was built, and the systems that are used to keep the station working. This project is going to benefit NASA by finding out how electricity is being used on the ISS and enabling us to see how it can be used more efficiently. This way we can operate the ISS without wasting power. While conducting research that goes on inside the space station knowing all electricity is being used efficiently.

Banks, Terrence↗
NASA NTRS2010

Operation Duties on the F-15B Research Testbed

This presentation entails what I have done this past summer for my Co-op tour in the Operations Engineering Branch. Activities included supporting the F-15B Research Testbed, supporting the incoming F-15D models, design work, and other operations engineering duties.

Truong, Samson S.↗
NASA NTRS2012

True Story of the Moon Rock Heist

In 2002, three NASA Co-op students along with a colleague from the University of Utah stole lunar samples from the Johnson Space Center. Three members of the "gang" removed a 600 pound safe containing lunar, meteorite and Martian samples from Dr. Gibson s laboratory. The thieves offered the samples for sale using the internet. They were arrested by undercover FBI and OIG agents. Three guilty pleas along with a conviction yielded sentences as long as 90 months in federal prison. Two of the thieves went to federal prison and have now been released. One of the thieves told his story to the popular author Ben Mezrich who released the book "Sex on the Moon" in July. Hollywood has "picked-up" the rights to their caper. The stolen lunar samples were not "trash". The loss of 30 years of Dr. Gibson s research records occurred along with contaminating and breaking the chain-of-custody for the lunar samples. The ring-leader has displayed no remorse for his crimes and is currently on the motivational speaker s lecture circuit. Investigators commented "they were the gang, who may have had the highest IQ but the least common sense in history." Previous unreleased information about the crime will be discussed by Dr. Gibson along with information about the forthcoming National Geographic Society s television special on the crime.

Gibson, Everett↗
NASA NTRS2012

Improving the Accuracy of the AFWA-NASA (ANSA) Blended Snow-Cover Product over the Lower Great Lakes Region

The Air Force Weather Agency (AFWA) -- NASA blended snow-cover product, called ANSA, utilizes Earth Observing System standard snow products from the Moderate- Resolution Imaging Spectroradiometer (MODIS) and the Advanced Microwave Scanning Radiometer for EOS (AMSR-E) to map daily snow cover and snow-water equivalent (SWE) globally. We have compared ANSA-derived SWE with SWE values calculated from snow depths reported at ~1500 National Climatic Data Center (NCDC) co-op stations in the Lower Great Lakes Basin. Compared to station data, the ANSA significantly underestimates SWE in densely-forested areas. We use two methods to remove some of the bias observed in forested areas to reduce the root-mean-square error (RMSE) between the ANSA- and station-derived SWE. First, we calculated a 5- year mean ANSA-derived SWE for the winters of 2005-06 through 2009-10, and developed a five-year mean bias-corrected SWE map for each month. For most of the months studied during the five-year period, the 5-year bias correction improved the agreement between the ANSA-derived and station-derived SWE. However, anomalous months such as when there was very little snow on the ground compared to the 5-year mean, or months in which the snow was much greater than the 5-year mean, showed poorer results (as expected). We also used a 7-day running mean (7DRM) bias correction method using days just prior to the day in question to correct the ANSA data. This method was more effective in reducing the RMSE between the ANSA- and co-op-derived SWE values, and in capturing the effects of anomalous snow conditions.

Hall, Dorothy K.↗
NASA NTRS2012

STEM Careers Are Out of This World--No Need to Fear Science, Technology, Engineering, or Math

At NASA, we fully support the President's Educate to Innovate Program in the hopes that American students move from the middle of the pack to the top in the next decade; and that we are expanding STEM education and career opportunities for underrepresented groups, including minorities and females. The first goal we have implemented to help accomplish this is to Strengthen NASA and the Nation's future workforce - Many of you in the audience could be our potential workforce, and the co-op and intern program at NASA is helping students like you. The second goal is to Attract and retain students in STEM disciplines-To compete effectively for the minds, imaginations and career ambitions of young people like you, throughout NASA, we regularly send educators and NASA speakers into classrooms to work directly with you, encouraging you to follow in the footsteps of NASA engineers and scientists. The Third goal is to Engage Americans in NASA's mission- To get young people involved in NASA's mission, we have many exciting programs for college students like the Lunabotics Mining Competition and the Cubes Satellites sent to space

Griffin, Amanda↗
NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗
NASA NTRS2013

Center Planning and Development Student Engineer

This fall I was the Student Trainee (Engineering) Pathways Intern (co-op) at the Kennedy Space Center (KSC) in the Center Planning Development (CPD) Directorate. CPD works with commercial companies who are interested using KSCs unique capabilities in spaceflight, spacecraft processing, ground systems and Research Development (RD) projects that fall in line with NASAs mission and goals. CPD is divided into four (4) groups: (1) AD-A, which works on the Master Planning for center, (2) AD-B (where I am), which works on project management and integration, (3) AD-C, which works on partnership development, and (4) AD-T, which works on the RD aspects of partnerships. CPDs main goal is to one day make KSC the worlds largest spaceport and maintain the center as a leader in space exploration. CPD is a very diverse group with employees having a wide knowledge of not only the Space Shuttle, but also that of the Apollo era. Our director of CPD, Scott Colloredo, is on the advisory board for Commercial Space Operations (CSO) and has a degree at ERAU. I worked on a number of different tasks for AD-B, as well as CPD, that includes, but not limited to: reviewing and reissuing engineering drawings from the Apollo and Shuttle eras, to supporting NASA rocket launches (MAVEN), and working on actual agreementsproposals that will be used in the partnership process with multiple partners. Most of the work I have done is sensitive information and cannot be disclosed.

engineering↗
NASA NTRS2015

Center Planning and Development Student Engineer at KSC

This summer I was the Student Trainee (Engineering) Pathways Intern (co-op) at the Kennedy Space Center (KSC) in the Center Planning & Development (CPD) Directorate. CPD works with commercial companies who are interested in using KSC's unique capabilities for spaceflight, spacecraft processing, ground systems and Research & Development (R&D) projects that fall in line with NASA's Mission and Vision. CPD is divided into three (3) groups: (1) AD-A, which works on the Master Planning for the center, (2) AD-B (where I am), which works on project control, management and integration, and (3) AD-C, which works on partnership development. CPD's main goal is to make KSC the world's preeminent multi-user spaceport and maintain the center as a leader in space exploration. CPD is a very diverse group of employees having a wide knowledge of not only the Space Shuttle, but also Expendable Launch Vehicles (ELV). The director of CPD, Scott Colloredo, is on the advisory board for Commercial Space Operations (CSO) and has a degree from ERAU. I worked on a number of different tasks for AD-B, as well as CPD, that includes, but not limited to: reviewing and reissuing engineering documents, weekly notes for CPD and senior management, engineering familiarizations with facilities at KSC, leading a tour for the Embry-Riddle Aeronautical University Career Services office, and working on actual agreements/proposals that will be used in the partnership process with multiple partners, along with other projects. Most of the work I have done is sensitive information and cannot be disclosed.

Engineer↗
NASA NTRS2015

[Redesign of the Spacesuit Long Life Battery and the Personal Life Support System Battery]

This fall I was working on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the department. The purpose of this document is to create a standard process and ensure that the data in the same way no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own all while taking notes on the procedure. These notes were used to write the final work instruction that will become is the department standard. My second project continued the work of the summer co-op before me. I was testing aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks were designed by the summer intern but there was not much time for testing before he left. We ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (energy systems test area) and are providing very promising results that safe, high performing (greater than 180 Wh/kg) designs are possible. My main project was a redesign of the LLB battery. Another summer intern did some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the current design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density and the rest of the design was up to me. First, I created new heat sink banks in Creo using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve greater than 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options of cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan is to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Some of my side projects included working on the CAD data for the PLSS with EC and attending the NASA Aerospace Battery Workshop in Huntsville. I was also a member of the Tours and Lectures Committee for the USRA and Pathways interns. I coordinated Apollo Evening and was on the committee for touring KSC and seeing an Atlas 5 launch. I really enjoyed my time at JSC and I would like to continue working for NASA or another aerospace company in the future. I have worked other internships prior to this, but I think the heavy research and development focus is the best fit for me. I originally thought I would need to go to grad school to work in an environment like this, but I now see it is possible with a bachelor’s degree and hard work. I would like to go into the workforce and maybe continue my education with night classes.

Scharf, Stephanie↗
NASA NTRS2016

Flight Planning and Procedures

The National Aeronautics and Space Administration (NASA) was founded in 1958 by President Eisenhower as a civilian lead United States federal agency designed to advance the science of space. Over the years, NASA has grown with a vision to "reach for new heights and reveal the unknown for the benefit of humankind" (About NASA). Mercury, Gemini, Apollo, Skylab, and Space Shuttle are just a few of the programs that NASA has led to advance our understanding of the universe. Each of the eleven main NASA space centers located across the United States plays a unique role in accomplishing that vision. Since 1961, Johnson Space Center (JSC) has led the effort for manned spaceflight missions. JSC has a mission to "provide and apply the preeminent capabilities to develop, operate, and integrate human exploration missions spanning commercial, academic, international, and US government partners" (Co-op Orientation). To do that, JSC is currently focused on two main programs, Orion and the International Space Station (ISS). Orion is the exploration vehicle that will take astronauts to Mars; a vessel comparable to the Apollo capsule. The International Space Station (ISS) is a space research facility designed to expand our knowledge of science in microgravity. The first piece of the ISS was launched in November of 1998 and has been in a continuous low earth orbit ever since. Recently, two sub-programs have been developed to resupply the ISS. The Commercial Cargo program is currently flying cargo and payloads to the ISS; the Commercial Crew program will begin flying astronauts to the ISS in a few years.

Rich, Allison C.↗