Search NASA⌕ Search

SEARCH · Search NASA

Results for “spaceport”

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 NTRS2017

Kennedy Space Center: Apollo to Multi-User Spaceport

NASA Kennedy Space Center (KSC) was established as the gateway to exploring beyond earth. Since the establishment of KSC in December 1963, the Center has been critical in the execution of the United States of Americas bold mission to send astronauts beyond the grasp of the terra firma. On May 25, 1961, a few weeks after a Soviet cosmonaut became the first person to fly in space, President John F. Kennedy laid out the ambitious goal of landing a man on the moon and returning him safely to the Earth by the end of the decade. The resultant Apollo program was massive endeavor, driven by the Cold War Space Race, and supported with a robust budget. The Apollo program consisted of 18 launches from newly developed infrastructure, including 12 manned missions and six lunar landings, ending with Apollo 17 that launched on December 7, 1972. Continuing to use this infrastructure, the Skylab program launched four missions. During the Skylab program, KSC infrastructure was redesigned to meet the needs of the Space Shuttle program, which launched its first vehicle (STS-1) on April 12, 1981. The Space Shuttle required significant modifications to the Apollo launch pads and assembly facilities, as well as new infrastructure, such as Orbiter and Payload Processing Facilities, as well as the Shuttle Landing Facility. The Space Shuttle was a workhorse that supported many satellite deployments, but was key for the construction and maintenance of the International Space Station, which required additional facilities at KSC to support processing of the flight hardware. After reaching the new Millennium, United States policymakers searched for new ways to reduce the cost of space exploration. The Constellation Program was initiated in 2005 with a goal of providing a crewed lunar landing with a much smaller budget. The very successful Space Shuttle made its last launch on July 8, 2011, after 135 missions. In the subsequent years, KSC continues to evolve, and this paper will address past and future efforts of the transformation of the KSC Apollo and Space Shuttle heritage infrastructure into a more versatile, multi-user spaceport. The paper will also discuss the US Congressional and NASA initiatives for developing and supporting multiple commercial partners, while simultaneously supporting NASAs human exploration initiative, consisting of Space Launch System (SLS), Orion spacecraft and associated ground launch systems. In addition, the paper explains the approach with examples for NASA KSC to leverage new technologies and innovative capabilities developed to reduce the cost to individual users.

launchpad↗
NASA NTRS1991

Spaceport Florida Authority

The topics are covered in viewgraph form and include the following: objectives; current initiatives; the Space Research Initiative Program; the Cape San Blas Launch Program; and Spaceport Florida Laboratories.

Source record↗
NASA NTRS1996

Spaceport Florida Authority: Business Plan

The Spaceport Florida Authority (SFA) was established under Florida Statute by the Governor and Legislature to assist the development of our nation's space transportation industry and to generate new space-related jobs, investment and opportunities statewide. Included in the Authorities' business plan is the statement of work and list of team members involved in creating the report, SFA's current operating concept, market analysis, assessment of accomplishments, a sample operating concept and a "roadmap to success".

Source record↗
NASA NTRS1999

Spaceport Support

Command and Control Technologies (CCT) Corporation of Titusville, Florida, a Florida/NASA Business Incubator tenant, is commercializing technology based on Kennedy Space Center's (KSC's) spacecraft ground processing program known as the Control Monitor Unit (CMU). The CMU was developed by engineers with NASA and McDonnell Douglas Space & Defense Systems at KSC to prepare the International Space Station elements for launch. CCT is significantly expanding the commercial capability of the product, called the Command and Control Toolkit(TM) (CCTK), according to Kevin Brown, CCT vice president for business development. In fact, CCT is the only U.S. firm specializing in launch vehicle control systems design and development for spaceports and new launch vehicle programs.

Source record↗
NASA NTRS2007

Methods and systems for advanced spaceport information management

Advanced spaceport information management methods and systems are disclosed. In one embodiment, a method includes coupling a test system to the payload and transmitting one or more test signals that emulate an anticipated condition from the test system to the payload. One or more responsive signals are received from the payload into the test system and are analyzed to determine whether one or more of the responsive signals comprises an anomalous signal. At least one of the steps of transmitting, receiving, analyzing and determining includes transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a remotely located facility. In one particular embodiment, the communications link is an Internet link from a payload processing facility to a remotely located facility (e.g. a launch facility, university, etc.).

Fussell, Ronald M.↗
NASA NTRS2007

Methods and Systems for Advanced Spaceport Information Management

Advanced spaceport information management methods and systems are disclosed. In one embodiment, a method includes coupling a test system to the payload and transmitting one or more test signals that emulate an anticipated condition from the test system to the payload. One or more responsive signals are received from the payload into the test system and are analyzed to determine whether one or more of the responsive signals comprises an anomalous signal. At least one of the steps of transmitting, receiving, analyzing and determining includes transmitting at least one of the test signals and the responsive signals via a communications link from a payload processing facility to a remotely located facility. In one particular embodiment, the communications link is an Internet link from a payload processing facility to a remotely located facility (e.g. a launch facility, university, etc.).

Fussell, Ronald M.↗
NASA NTRS2005

Transformational Spaceport and Range Concept of Operations: A Vision to Transform Ground and Launch Operations

The Transformational Concept of Operations (CONOPS) provides a long-term, sustainable vision for future U.S. space transportation infrastructure and operations. This vision presents an interagency concept, developed cooperatively by the Department of Defense (DoD), the Federal Aviation Administration (FAA), and the National Aeronautics and Space Administration (NASA) for the upgrade, integration, and improved operation of major infrastructure elements of the nation s space access systems. The interagency vision described in the Transformational CONOPS would transform today s space launch infrastructure into a shared system that supports worldwide operations for a variety of users. The system concept is sufficiently flexible and adaptable to support new types of missions for exploration, commercial enterprise, and national security, as well as to endure further into the future when space transportation technology may be sufficiently advanced to enable routine public space travel as part of the global transportation system. The vision for future space transportation operations is based on a system-of-systems architecture that integrates the major elements of the future space transportation system - transportation nodes (spaceports), flight vehicles and payloads, tracking and communications assets, and flight traffic coordination centers - into a transportation network that concurrently accommodates multiple types of mission operators, payloads, and vehicle fleets. This system concept also establishes a common framework for defining a detailed CONOPS for the major elements of the future space transportation system. The resulting set of four CONOPS (see Figure 1 below) describes the common vision for a shared future space transportation system (FSTS) infrastructure from a variety of perspectives.

Source record↗
NASA NTRS2013

Spaceport Processing System Development Lab

The Spaceport Processing System Development Lab (SPSDL), developed and maintained by the Systems Hardware and Engineering Branch (NE-C4), is a development lab with its own private/restricted networks. A private/restricted network is a network with restricted or no communication with other networks. This allows users from different groups to work on their own projects in their own configured environment without interfering with others utilizing their resources in the lab. The different networks being used in the lab have no way to talk with each other due to the way they are configured, so how a user configures his software, operating system, or the equipment doesn't interfere or carry over on any of the other networks in the lab. The SPSDL is available for any project in KSC that is in need of a lab environment. My job in the SPSDL was to assist in maintaining the lab to make sure it's accessible for users. This includes, but is not limited to, making sure the computers in the lab are properly running and patched with updated hardware/software. In addition to this, I also was to assist users who had issues in utilizing the resources in the lab, which may include helping to configure a restricted network for their own environment. All of this was to ensure workers were able to use the SPSDL to work on their projects without difficulty which would in turn, benefit the work done throughout KSC. When I wasn't working in the SPSDL, I would instead help other coworkers with smaller tasks which included, but wasn't limited to, the proper disposal, moving of, or search for essential equipment. I also, during the free time I had, used NASA's resources to increase my knowledge and skills in a variety of subjects related to my major as a computer engineer, particularly in UNIX, Networking, and Embedded Systems.

Systems Engineering↗
NASA NTRS2014

IT Security Support for the Spaceport Command Control System Development

My job title is IT Security support for the Spaceport Command & Control System Development. As a cyber‐security analyst it is my job to ensure NASA's information stays safe from cyber threats, such as, viruses, malware and denial-of-service attacks by establishing and enforcing system access controls. Security is very important in the world of technology and it is used everywhere from personal computers to giant networks ran by Government agencies worldwide. Without constant monitoring analysis, businesses, public organizations and government agencies are vulnerable to potential harmful infiltration of their computer information system. It is my responsibility to ensure authorized access by examining improper access, reporting violations, revoke access, monitor information request by new programming and recommend improvements. My department oversees the Launch Control System and networks. An audit will be conducted for the LCS based on compliance with the Federal Information Security Management Act (FISMA) and The National Institute of Standards and Technology (NIST). I recently finished analyzing the SANS top 20 critical controls to give cost effective recommendations on various software and hardware products for compliance. Upon my completion of this internship, I will have successfully completed my duties as well as gain knowledge that will be helpful to my career in the future as a Cyber Security Analyst.

IT Security↗
NASA NTRS2013

IT Security Support for Spaceport Command and Control System

During the fall 2013 semester, I worked at the Kennedy Space Center as an IT Security Intern in support of the Spaceport Command and Control System under the guidance of the IT Security Lead Engineer. Some of my responsibilities included assisting with security plan documentation collection, system hardware and software inventory, and malicious code and malware scanning. Throughout the semester, I had the opportunity to work on a wide range of security related projects. However, there are three projects in particular that stand out. The first project I completed was updating a large interactive spreadsheet that details the SANS Institutes Top 20 Critical Security Controls. My task was to add in all of the new commercial of the shelf (COTS) software listed on the SANS website that can be used to meet their Top 20 controls. In total, there are 153 unique security tools listed by SANS that meet one or more of their 20 controls. My second project was the creation of a database that will allow my mentor to keep track of the work done by the contractors that report to him in a more efficient manner by recording events as they occur throughout the quarter. Lastly, I expanded upon a security assessment of the Linux machines being used on center that I began last semester. To do this, I used a vulnerability and configuration tool that scans hosts remotely through the network and presents the user with an abundance of information detailing each machines configuration. The experience I gained from working on each of these projects has been invaluable, and I look forward to returning in the spring semester to continue working with the IT Security team.

computer security↗
NASA NTRS2015

Center Planning and Development: Multi-User Spaceport Initiatives

The Vehicle Assembly building at NASAs Kennedy Space Center has been used since 1966 to vertically assemble every launch vehicle, since the Apollo Program, launched from Launch Complex 39 (LC-39). After the cancellation of the Constellation Program in 2010 and the retirement of the Space Shuttle Program in 2011, the VAB faced an uncertain future. As the Space Launch System (SLS) gained a foothold as the future of American spaceflight to deep space, NASA was only using a portion of the VABs initial potential. With three high bays connected to the Crawler Way transportation system, the potential exists for up to three rockets to be simultaneously processed for launch. The Kennedy Space Center (KSC) Master plan, supported by the Center Planning and Development (CPD) Directorate, is guiding Kennedy toward a 21st century multi-user spaceport. This concept will maintain Kennedy as the United States premier gateway to space and provide multi-user operations through partnerships with the commercial aerospace industry. Commercial aerospace companies, now tasked with transporting cargo and, in the future, astronauts to the International Space Station (ISS) via the Commercial Resupply Service (CRS) and Commercial Crew Program (CCP), are a rapidly growing industry with increasing capabilities to make launch operations more economical for both private companies and the government. Commercial operations to Low Earth Orbit allow the government to focus on travel to farther destinations through the SLS Program. With LC-39B designated as a multi-use launch pad, companies seeking to use it will require an integration facility to assemble, integrate, and test their launch vehicle. An Announcement for Proposals (AFP) was released in June, beginning the process of finding a non-NASA user for High Bay 2 (HB2) and the Mobile Launcher Platforms (MLPs). An Industry Day, a business meeting and tour for interested companies and organizations, was also arranged to identify and answer any additional questions posed by potential proposers. After amending the AFP and posting additional material for potential users to consider, proposals are being accepted until July 31, at which point they will be evaluated to determine the proposer which best meets the objectives of the government. By identifying VAB HB2 as available and seeking proposals from the commercial sector for VAB HB2 and MLP use, Center Planning and Development is ensuring Kennedy Space Centers relevance in the evolving launch industry of the 21st century.

AFP↗
NASA NTRS2016

Cyber Security for the Spaceport Command and Control System: Vulnerability Management and Compliance Analysis

With the rapid development of the Internet, the number of malicious threats to organizations is continually increasing. In June of 2015, the United States Office of Personnel Management (OPM) had a data breach resulting in the compromise of millions of government employee records. The National Aeronautics and Space Administration (NASA) is not exempt from these attacks. Cyber security is becoming a critical facet to the discussion of moving forward with projects. The Spaceport Command and Control System (SCCS) project at the Kennedy Space Center (KSC) aims to develop the launch control system for the next generation launch vehicle in the coming decades. There are many ways to increase the security of the network it uses, from vulnerability management to ensuring operating system images are compliant with securely configured baselines recommended by the United States Government.

Cyber Security↗
NASA NTRS2016

Spaceport Command and Control System User Interface Testing

The Spaceport Command and Control System will be the National Aeronautics and Space Administration's newest system for launching commercial and government owned spacecraft. It's a large system with many parts all in need of testing. To improve upon testing already done by NASA engineers, the Engineering Directorate, Electrical Division (NE-E) of Kennedy Space Center has hired a group of interns each of the last few semesters to develop novel ways of improving the testing process.

SCCS↗
NASA NTRS2016

Spaceport Command and Control System - Support Software Development

The Information Architecture Support (IAS) Team, the component of the Spaceport Command and Control System (SCCS) that is in charge of all the pre-runtime data, was in need of some report features to be added to their internal web application, Information Architecture (IA). Development of these reports is crucial for the speed and productivity of the development team, as they are needed to quickly and efficiently make specific and complicated data requests against the massive IA database. These reports were being put on the back burner, as other development of IA was prioritized over them, but the need for them resulted in internships being created to fill this need. The creation of these reports required learning Ruby on Rails development, along with related web technologies, and they will continue to serve IAS and other support software teams and their IA data needs.

Information Architecture↗
NASA NTRS2016

Spaceport Command and Control System Support Software Development

The Spaceport Command and Control System (SCCS) is a project developed and used by NASA at Kennedy Space Center in order to control and monitor the Space Launch System (SLS) at the time of its launch. One integral subteam under SCCS is the one assigned to the development of a data set building application to be used both on the launch pad and in the Launch Control Center (LCC) at the time of launch. This web application was developed in Ruby on Rails, a web framework using the Ruby object-oriented programming language, by a 15 - employee team (approx.). Because this application is such a huge undertaking with many facets and iterations, there were a few areas in which work could be more easily organized and expedited. As an intern working with this team, I was charged with the task of writing web applications that fulfilled this need, creating a virtual and highly customizable whiteboard in order to allow engineers to keep track of build iterations and their status. Additionally, I developed a knowledge capture web application wherein any engineer or contractor within SCCS could ask a question, answer an existing question, or leave a comment on any question or answer, similar to Stack Overflow.

Knowledge Transfer↗
NASA NTRS2017

Spaceport Command and Control System Automation Testing

The goal of automated testing is to create and maintain a cohesive infrastructure of robust tests that could be run independently on a software package in its entirety. To that end, the Spaceport Command and Control System (SCCS) project at the National Aeronautics and Space Administration's (NASA) Kennedy Space Center (KSC) has brought in a large group of interns to work side-by-side with full time employees to do just this work. Thus, our job is to implement the tests that will put SCCS through its paces.

Plano, Tom↗