SEARCH · Search NASA
Results for “service”
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.
Extending Cost Model of Earth satellite broadband services to future commercial lunar relay service?
No abstract provided
Spaceflight Operations Services Grid (SOSG)
In an effort to adapt existing space flight operations services to new emerging Grid technologies we are developing a Grid-based prototype space flight operations Grid. This prototype is based on the operational services being provided to the International Space Station's Payload operations located at the Marshall Space Flight Center, Alabama. The prototype services will be Grid or Web enabled and provided to four user communities through portal technology. Users will have the opportunity to assess the value and feasibility of Grid technologies to their specific areas or disciplines. In this presentation descriptions of the prototype development, User-based services, Grid-based services and status of the project will be presented. Expected benefits, findings and observations (if any) to date will also be discussed. The focus of the presentation will be on the project in general, status to date and future plans. The End-use services to be included in the prototype are voice, video, telemetry, commanding, collaboration tools and visualization among others. Security is addressed throughout the project and is being designed into the Grid technologies and standards development. The project is divided into three phases. Phase One establishes the baseline User-based services required for space flight operations listed above. Phase Two involves applying Gridlweb technologies to the User-based services and development of portals for access by users. Phase Three will allow NASA and end users to evaluate the services and determine the future of the technology as applied to space flight operational services. Although, Phase One, which includes the development of the quasi-operational User-based services of the prototype, development will be completed by March 2004, the application of Grid technologies to these services will have just begun. We will provide status of the Grid technologies to the individual User-based services. This effort will result in an extensible environment that incorporates existing and new spaceflight services into a standards-based framework providing current and future NASA programs with cost savings and new and evolvable methods to conduct science. This project will demonstrate how the use of new programming paradigms such as web and grid services can provide three significant benefits to the cost-effective delivery of spaceflight services. They will enable applications to operate more efficiently by being able to utilize pooled resources. They will also permit the reuse of common services to rapidly construct new and more powerful applications. Finally they will permit easy and secure access to services via a combination of grid and portal technology by a distributed user community consisting of NASA operations centers, scientists, the educational community and even the general population as outreach. The approach will be to deploy existing mission support applications such as the Telescience Resource Kit (TReK) and new applications under development, such as the Grid Video Distribution System (GViDS), together with existing grid applications and services such as high-performance computing and visualization services provided by NASA s Information Power Grid (IPG) in the MSFC s Payload Operations Integration Center (POIC) HOSC Annex. Once the initial applications have been moved to the grid, a process will begin to apply the new programming paradigms to integrate them where possible. For example, with GViDS, instead of viewing the Distribution service as an application that must run on a single node, the new approach is to build it such that it can be dispatched across a pool of resources in response to dynamic loads. To make this a reality, reusable services will be critical, such as a brokering service to locate appropriate resource within the pool. This brokering service can then be used by other applications such as the TReK. To expand further, if the GViDS application is constructed using a services-based mel, then other applications such as the Video Auditorium can then use GViDS as a service to easily incorporate these video streams into a collaborative conference. Finally, as these applications are re-factored into this new services-based paradigm, the construction of portals to integrate them will be a simple process. As a result, portals can be tailored to meet the requirements of specific user communities.
DIP for Service Providers
The second DIP workshop’s topic is DIP for Service Providers. The workshop presentation covers topics such as DIP onboarding process, service authentication, catalog service capabilities, API requirements, NASA services and their access points, and data requirements for service providers. The Onboarding Process describes the required documentation that enables to collaborate with NASA as well as other industry partners through DIP. Also, step by step approach for the partner to take to register services or consme services through the DIP platform. The Catalog Service describes the different ways for the users to search for services that are of interest as well as registering services to the platform, so other users can search and discover. The API Requirements and Service Specifications describes the benefits of DIP's API management approach via API Gateway where services are managed centrally but ownership is decentralized and partners completely own the administration of their own services. NASA Services and Data Access Points topic describes the services, both data access service and machine learning prediction service, that NASA provides via the DIP platform in near time and post operations via REST API endpoints defined on the API Gateway. Also, NASA's approach for data storage process is explained. The Data Requirements for service providers describes the requirements for storing and exposing to support the performance of services that are provided by the service providers. Lastly, NASA's technology development plan with preliminary scheduler will be presented. There will be a Q&A session at the end of each segment of the presentation to solicit feedback from the participants.
Combined Global Navigation Satellite Systems in the Space Service Volume
Besides providing position, velocity, and timing (PVT) for terrestrial users, the Global Positioning System (GPS) is also being used to provide PVT information for earth orbiting satellites. In 2006, F. H. Bauer, et. al., defined the Space Service Volume in the paper GPS in the Space Service Volume , presented at ION s 19th international Technical Meeting of the Satellite Division, and looked at GPS coverage for orbiting satellites. With GLONASS already operational, and the first satellites of the Galileo and Beidou/COMPASS constellations already in orbit, it is time to look at the use of the new Global Navigation Satellite Systems (GNSS) coming into service to provide PVT information for earth orbiting satellites. This presentation extends GPS in the Space Service Volume by examining the coverage capability of combinations of the new constellations with GPS GPS was first explored as a system for refining the position, velocity, and timing of other spacecraft equipped with GPS receivers in the early eighties. Because of this, a new GPS utility developed beyond the original purpose of providing position, velocity, and timing services for land, maritime, and aerial applications. GPS signals are now received and processed by spacecraft both above and below the GPS constellation, including signals that spill over the limb of the earth. Support of GPS space applications is now part of the system plan for GPS, and support of the Space Service Volume by other GNSS providers has been proposed to the UN International Committee on GNSS (ICG). GPS has been demonstrated to provide decimeter level position accuracy in real-time for satellites in low Earth orbit (centimeter level in non-real-time applications). GPS has been proven useful for satellites in geosynchronous orbit, and also for satellites in highly elliptical orbits. Depending on how many satellites are in view, one can keep time locked to the GNSS standard, and through that to Universal Time as long as at least one satellite is in view (the longest duration with no satellites in view is important in determining the maximum clock drift from GNSS time). Instantaneous position requires four satellites in view, but because orbital motion is predictable, it is possible to build up knowledge of the orbital position gradually through time without a need for constant four satellite coverage. However, it is desirable to have four satellite coverage when performing satellite maneuvers, since there can be significant changes in velocity, leading to large changes in orbit parameter, causing substantial divergence in position over time. The Space Service Volume has been defined as the volume between three thousand km altitude and geosynchronous altitude, and can be divided into medium orbit services between three thousand km altitude and eight thousand km altitude, and high orbit services above eight thousand km. The Terrestrial Service Volume includes the Earth s surface, the atmosphere, and space below the altitude of three thousand km. The Terrestrial Service Volume is the volume within which the GNSS systems will have very similar performance to the Earth surface, and satellites need only use the signals specified to provide terrestrial performance. Above three thousand km the use of signals passing by the Earth s limb becomes important, so it is desirable to have additional information on signal strength, phase delay, and group delay covering wider beam angles than are needed for terrestrial service (and which can be obtained by monitoring GNSS signals from the Earth s surface). This presentation will look at each of the new GNSS constellations in combination with GPS (GLONASS with GPS, Galileo with GPS, Beidou/COMPASS with GPS), and also at the combination of all four GNSS systems. The presentation will largely follow the format of GPS in the Space Service Volume , presenting data on the availability of one, two, three, or four of the various combinations of GNSS constellation satelles at approximately two thousand grid points evenly spaced and fixed in longitude and latitude, the duration of the longest single-fold outages (intervals when no satellites are available), and the duration of the longest four-fold outages (intervals when fewer than four satellites are available) at several altitudes. Following the original paper, we will use the altitudes of three hundred km (typical LEO satellite, and within the Terrestrial Service Volume), at three thousand km (border between Terrestrial Service Volume and Space Service Volume), at eight thousand km (the border between medium and high orbit service within the Space Service Volume), at fifteen thousand km (just below the GNSS constellations), at twenty five thousand km (just above the GNSS constellations), at thirty six thousand, five hundred km (limit of Space Service Volume definition, geosynchronous altitude), and at seventy thousand km (to show the potential usefulness of GNSS beyond geosynchronous altitude).
Servicing capability for the evolutionary Space Station
Since the beginning of the Space Station Freedom (SSF) program the concept of on-orbit servicing of user hardware has been an integral part of the program implementation. The user servicing system architecture has been divided into a baseline and a growth phase. The baseline system consists of the following hardware elements that will support user servicing - flight telerobotic servicer, crew and equipment translation aid, crew intravehicular and extravehicular servicing support, logistics supply system, mobile servicing center, and the special purpose dextrous manipulator. The growth phase incorporates a customer servicing facility (CSF), a station-based orbital maneuvering vehicle and an orbital spacecraft consumables resupply system. The requirements for user servicing were derived from the necessity to service attached payloads, free flyers and coorbiting platforms. These requirements include: orbital replacement units (ORU) and instrument changeout, National Space Transportation System cargo bay loading and unloading, contamination control and monitoring, thermal protection, payload berthing, storage, access to SSF distributed systems, functional checkout, and fluid replenishment. The baseline user servicing capabilities accommodate ORU and instrument changeout. However, this service is limited to attached payloads, either in situ or at a locally adjacent site. The growth phase satisfies all identified user servicing requirements by expanding servicing capabilities to include complex servicing tasks for attached payloads, free-flyers and coorbiting platforms at a dedicated, protected Servicing site. To provide a smooth evolution of user servicing the SSF interfaces that are necessary to accommodate the growth phase have been identified. The interface requirements on SSF have been greatly simplified by accommodating the growth servicing support elements within the CSF. This results in a single SSF interface: SSF to the CSF.
Energy Services Interface: Architecture, Requirements, and Agreements
This report continues and extends the development of the Energy Services Interface (ESI) that recently has been led by the U.S. Department of Energy’s Grid Modernization Laboratory Consortium. The ESI is intended to facilitate the coordination of multiple, flexible energy resources that work in tandem to satisfy grid objectives by using performance attributes encoded within an ESI Service Template. The ESI relies on a pair of interfaces, representing the service requestor (the consumer of a service) and a service provider (who manages its resources per the agreed performance attributes) to achieve what is commonly known as a “grid service”. Due to its performance-driven approach, the ESI is hypothesized to be able to satisfy all common grid needs via only six common ESI service types. This report first reviews the status of ESI development, including its fundamental tenets. The report makes three important contributions to ESI development: First, it recognizes the similarity between service level agreements and the contract-like agreements that would be needed between energy service requestors and providers and recommends that ESI service agreements be modeled after the web services agreement specification. Second, whereas prior development efforts had focused on a flat, five-stage lifecycle, this report asserts that the ESI should have three behavioral layers in its architecture—the discovery, agreement, and service layers. Finally, this report offers concrete requirements that should be useful toward the development of the service requestors’ and service providers’ respective communications interfaces.
Virtualized Multi-Mission Operations Center (vMMOC) and its Cloud Services
His presentation will cover, the current and future, technical and organizational opportunities and challenges with virtualizing a multi-mission operations center. The full deployment of Goddard Space Flight Centers (GSFC) Virtualized Multi-Mission Operations Center (vMMOC) is nearly complete. The Space Science Mission Operations (SSMO) organizations spacecraft ACE, Fermi, LRO, MMS(4), OSIRIS-REx, SDO, SOHO, Swift, and Wind are in the process of being fully migrated to the vMMOC. The benefits of the vMMOC will be the normalization and the standardization of IT services, mission operations, maintenance, and development as well as ancillary services and policies such as collaboration tools, change management systems, and IT Security. The vMMOC will also provide operational efficiencies regarding hardware, IT domain expertise, training, maintenance and support.The presentation will also cover SSMO's secure Situational Awareness Dashboard in an integrated, fleet centric, cloud based web services fashion. Additionally the SSMO Telemetry as a Service (TaaS) will be covered, which allows authorized users and processes to access telemetry for the entire SSMO fleet, and for the entirety of each spacecrafts history. Both services leverage cloud services in a secure FISMA High and FedRamp environment, and also leverage distributed object stores in order to house and provide the telemetry. The services are also in the process of leveraging the cloud computing services elasticity and horizontal scalability. In the design phase is the Navigation as a Service (NaaS) which will provide a standardized, efficient, and normalized service for the fleet's space flight dynamics operations. Additional future services that may be considered are Ground Segment as a Service (GSaaS), Telemetry and Command as a Service (TCaaS), Flight Software Simulation as a Service, etc.
Scheduling Position, Navigation and Time Service Requests from Non-dedicated Lunar Constellations
This paper presents a centralized scheduler that satisfies user requests for Position, Navigation, and Time (PNT) services from an ad-hoc, non-dedicated orbital constellation around the Moon. Traditional, dedicated GNSS networks provide service 24/7, which allows users to acquire localization services at-will. For ad-hoc networks, a coordinated schedule is needed to ensure Quality of Service (QoS) guarantees for user localization, while satisfying non-dedicated assets’ usage constraints. This scheduler bridges this coordination gap by leveraging Mixed Integer-Linear Programming (MILP) to schedule this “as-needed” localization service while respecting the constraints on each asset. In upcoming decades there is expected to be a substantial increase in Lunar missions. Many of these missions will feature low-cost surface assets near the moon’s polar regions and small-sat science missions in orbit. Most missions need PNT capabilities to ensure safe operations and meet their science objectives, but low-cost missions may not be able to support the large power, mass, and weight that a weak GNSS or DSN based navigation solution would entail. Asset localization has been demonstrated using a decentralized extended Kalman Filter (DEKF) in the previously presented Lunar Autonomous PNT System (LAPS). Within the LAPS simulation environment, a module has been developed to generate the coordinated user-asset schedules described above; this Service Scheduler Module (SSM) allows for complete end-to-end testing of the entire system. Within SSM, a user service request consists of a location on the Lunar surface, a cumulative service duration, and a window in which service must occur. SSM takes as input these requests and the LAPS-predicted positional degree of precision as the QoS for each available set of orbital assets. A simple, baseline MILP model is formulated to provide the highest-precision service balanced across all requests. To reflect the non-dedicated nature of the constellation, this baseline model is augmented with additional asset-specific load capacity constraints or availability constraints. The load capacity constraints limit total time spent providing service, and the availability constraints reflect blockout times or availability windows when the assets are not otherwise occupied. SSM outputs two schedules: the user schedule to indicate their service times and expected QoS, and a satellite schedule to be transmitted to the orbiting constellation, describing when each non-dedicated asset provides PNT service. SSM is predominantly implemented in MATLAB and allows the use of any MILP solver to generate the resulting schedules. This paper describes the SSM - LAPS interface, how the output of LAPS is used to construct the MILP, and how SSM provides user localization service while satisfying constraints. It will also demonstrate the tool’s flexibility for formulating schedules for the end user and the constellation, focusing on scenarios that match real-world proposed missions. It will detail how SSM can be used to compare the addition of load capacity constraints, satellite availability constraints, and QoS guarantees for the users. Finally, we describe how SSM can be used to support the design of the ad-hoc constellation itself. The resulting integrated capability will support the design of future ad-hoc Lunar PNT networks, enabling high-quality, low-cost Lunar exploration
NASA’s Efforts to Pursue Commercial Communications Services for Missions in Near Space
The National Aeronautics and Space Administration (NASA) Space Communications and Navigation (SCaN) Program enables high speed, robust, secure, and cost-effective space communications and navigation services to current and future science and exploration missions. Consistent with National Space Policy, NASA is seeking commercial services for all its future near-Earth requirements by incorporating additional direct to Earth (DTE) providers and introducing commercial satellite relay communications (SATCOM) vendors as NASA’s Tracking and Data Relay Satellites (TDRS) begin to decline. Through the progression of these efforts, SCaN is also integrating commercial services in the cislunar domain. The overarching objective is to satisfy the demands from the mission community – both in terms of capacity and capability – in a robust, reliable, and cost-effective way, leveraging the strong and growing commercial space sector. For near earth space relay, six SATCOM vendors were awarded Funded Space Act Agreements in June of 2022 to demonstrate the ability to serve near-Earth missions with space-based communication relay services. All six vendors are working through their committed milestones with end-to-end service demonstrations tacking place throughout the mid-2020’s. The failure of TDRS Flight-9 (F9) in late 2022 prompted an increased tempo of mission engagement to identify driving user needs that commercial SATCOM can meet in the near-term. NASA has set a course to accelerate a decision to terminate offering TDRS services to new missions and is developing a plan to execute validation and risk reduction efforts with early adopter “pathfinder” missions, paving the way to operational services. As the Artemis Program matures and builds on the successful Artemis I flight in November-December of 2022, the definition of the supporting communications and navigation architecture has further been refined. Although NASA government assets will continue to play a key role in provision of services, such as through the Deep Space Network, SCaN is pursuing commercial services offerings to expand ground network capability and implement lunar relay services. In February of 2023, SCaN released solicitation for services that include DTE services to missions near-Earth and in cislunar space, as well as lunar relay services. Further, SCaN is seeking opportunities to integrate commercial capability into lunar surface communications infrastructure. NASA is also advocating for standards that promote interoperability and strategic technology investments in the commercial sector. This paper addresses the recent progress and future plans in the near-Earth space and lunar regimes, discusses the unified approach for industry engagement, and highlights both the common and unique challenges of commercialization efforts in the two regimes.
Grid Technology as a Cyberinfrastructure for Delivering High-End Services to the Earth and Space Science Community
Grid technology consists of middleware that permits distributed computations, data and sensors to be seamlessly integrated into a secure, single-sign-on processing environment. In &is environment, a user has to identify and authenticate himself once to the grid middleware, and then can utilize any of the distributed resources to which he has been,panted access. Grid technology allows resources that exist in enterprises that are under different administrative control to be securely integrated into a single processing environment The grid community has adopted commercial web services technology as a means for implementing persistent, re-usable grid services that sit on top of the basic distributed processing environment that grids provide. These grid services can then form building blocks for even more complex grid services. Each grid service is characterized using the Web Service Description Language, which provides a description of the interface and how other applications can access it. The emerging Semantic grid work seeks to associates sufficient semantic information with each grid service such that applications wii1 he able to automatically select, compose and if necessary substitute available equivalent services in order to assemble collections of services that are most appropriate for a particular application. Grid technology has been used to provide limited support to various Earth and space science applications. Looking to the future, this emerging grid service technology can provide a cyberinfrastructures for both the Earth and space science communities. Groups within these communities could transform those applications that have community-wide applicability into persistent grid services that are made widely available to their respective communities. In concert with grid-enabled data archives, users could easily create complex workflows that extract desired data from one or more archives and process it though an appropriate set of widely distributed grid services discovered using semantic grid technology. As required, high-end computational resources could be drawn from available grid resource pools. Using grid technology, this confluence of data, services and computational resources could easily be harnessed to transform data from many different sources into a desired product that is delivered to a user's workstation or to a web portal though which it could be accessed by its intended audience.
CCSDS Time-Critical Onboard Networking Service
The Consultative Committee for Space Data Systems (CCSDS) is developing recommendations for communication services onboard spacecraft. Today many different communication buses are used on spacecraft requiring software with the same basic functionality to be rewritten for each type of bus. This impacts on the application software resulting in custom software for almost every new mission. The Spacecraft Onboard Interface Services (SOIS) working group aims to provide a consistent interface to various onboard buses and sub-networks, enabling a common interface to the application software. The eventual goal is reusable software that can be easily ported to new missions and run on a range of onboard buses without substantial modification. The system engineer will then be able to select a bus based on its performance, power, etc and be confident that a particular choice of bus will not place excessive demands on software development. This paper describes the SOIS Intra-Networking Service which is designed to enable data transfer and multiplexing of a variety of internetworking protocols with a range of quality of service support, over underlying heterogeneous data links. The Intra-network service interface provides users with a common Quality of Service interface when transporting data across a variety of underlying data links. Supported Quality of Service (QoS) elements include: Priority, Resource Reservation and Retry/Redundancy. These three QoS elements combine and map into four TCONS services for onboard data communications: Best Effort, Assured, Reserved, and Guaranteed. Data to be transported is passed to the Intra-network service with a requested QoS. The requested QoS includes the type of service, priority and where appropriate, a channel identifier. The data is de-multiplexed, prioritized, and the required resources for transport are allocated. The data is then passed to the appropriate data link for transfer across the bus. The SOIS supported data links may inherently provide the quality of service support requested by the intra-network layer. In the case where the data link does not have the required level of support, the missing functionality is added by SOIS. As a result of this architecture, re-usable software applications can be designed and used across missions thereby promoting common mission operations. In addition, the protocol multiplexing function enables the blending of multiple onboard networks. This paper starts by giving an overview of the SOIS architecture in section 11, illustrating where the TCONS services fit into the overall architecture. It then describes the quality of service approach adopted, in section III. The prototyping efforts that have been going on are introduced in section JY. Finally, in section V the current status of the CCSDS recommendations is summarized.
Space Mission Operations Ground Systems Integration Customer Service
The facility, which is now the Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center in Huntsville, AL, has provided continuous space mission and related services for the space industry since 1961, from Mercury Redstone through the International Space Station (ISS). Throughout the long history of the facility and mission support teams, the HOSC has developed a stellar customer support and service process. In this era, of cost cutting, and providing more capability and results with fewer resources, space missions are looking for the most efficient way to accomplish their objectives. One of the first services provided by the facility was fax transmission of documents to, then, Cape Canaveral in Florida. The headline in the Marshall Star, the newspaper for the newly formed Marshall Space Flight Center, read "Exact copies of Documents sent to Cape in 4 minutes." The customer was Dr. Wernher von Braun. Currently at the HOSC we are supporting, or have recently supported, missions ranging from simple ISS payloads requiring little more than "bentpipe" telemetry access, to a low cost free-flyer Fast, Affordable, Science and Technology Satellite (FASTSAT), to a full service ISS payload Alpha Magnetic Spectrometer 2 (AMS2) supporting 24/7 operations at three operations centers around the world with an investment of over 2 billion dollars. The HOSC has more need and desire than ever to provide fast and efficient customer service to support these missions. Here we will outline how our customer-centric service approach reduces the cost of providing services, makes it faster and easier than ever for new customers to get started with HOSC services, and show what the future holds for our space mission operations customers. We will discuss our philosophy concerning our responsibility and accessibility to a mission customer as well as how we deal with the following issues: initial contact with a customer, reducing customer cost, changing regulations and security, and cultural differences, to ensure an efficient response to customer issues using a small Customer Service Team (CST) and adaptability, constant communication with customers, technical expertise and knowledge of services, and dedication to customer service. The HOSC Customer Support Team has implemented a variety of processes, and procedures that help to mitigate the potential problems that arise when integrating ground system services for a variety of complex missions and the lessons learned from this experience will lead the future of customer service in the space operations industry.
NASA Electric Vertical Takeoff and Landing (eVTOL) Aircraft Technology for Public Services – A White Paper
History has shown that our personal life is highly dependent on the technology that people have developed. A strategic scan of the aerospace environment at the beginning of the 21st century strongly suggests that the world might be approaching a new age of airpower—the era of electrified/hybrid aircraft propulsion. Undeniably, starting from the Montgolfier Brothers balloon flight in 1783, to the Wright Brothers piston engine flight in 1903, and the jet engine of the 1960s, or the space age of today, one can say that leaps in propulsion technology have marked the different ages of human flight. The technological advancements, brought at the beginning of 21st century by the revolution in data exchange, computational power, sensors, wireless communication, internet, and autonomy, contributed to the vision of this new age of propulsion we are approaching. Historically, conventional vertical takeoff and landing (VTOL) aircraft have been equipped with propulsion units relying on complex internal combustion machines (turbines, piston engines, for example), and complex mechanical arrangements (gearboxes, shafts, variable pitch propeller). By contrast, electric VTOL aircraft (eVTOL)1 rely on simpler propulsion units (electric motors and in some cases fixed-pitch propellers). This promotes redundancy and improves tolerance to failures, in turn improving safety. The use of simpler electric propulsion units should also allow significant acquisition and operating cost reductions. Whether full-electric (relying solely on batteries) or hybrid-electric (relying on a combination of batteries, fuel-powered engines, and generators.), eVTOLs are also expected to generate less noise and air pollution than conventional aircraft with similar payloads. According to the 2019 Annual Review of IATA (International Air Transport Association) [ref.1], due to an expected increase in air transport traffic by 5% every year and a doubling of air transport passenger numbers to 8.2 billion by 2037 significant challenges are posed to the aviation industry. Furthermore, this report does not factor in the expected demand for short-range (intra-city) air transportation, which is in development and yet to be operational. The increased demand to fly creates a responsibility to expand in a sustainable manner and an endeavor to develop more environmentally-friendly aircraft. eVTOL aircraft, either piloted or autonomous, is gathering considerable interest worldwide. Modern and novel full-electric or hybrid-electric eVTOL configurations enable a new paradigm shift in air transportation as the aviation industry remains committed to its goals of carbon-neutral growth from 2020 onwards and cutting CO2 emissions to half 2005 levels by 2050. While electric power has been used for decades, recent developments in mobile electric/hybrid propulsion coupled with advanced materials and autonomous systems may create the possibility to transition into the next age of air mobility propelled by electric/hybrid VTOL aircraft technology. Although eVTOL aircraft might seem like an incremental improvement or even a counterintuitive regression with regard to past VTOL development, it has in fact the potential to transform air mobility across a wide range of government applications. Previous transformations in aviation generated dramatic leaps in performance, but the cost was commensurate with performance, limiting quantity produced. This next age appears to take a different approach. Performance may not increase, but at this moment technology is poised for future urban mobility that will spawn commercial passenger drone services, that is, autonomous (pilotless) air taxis and thereby add a new dimension to the urban transportation mix of the future [ref. 2]. Advances in electric propulsion, autonomous flight technology, and 5G communication networks will enable this fast new-growing market to become a reality. It is now time to envision the introduction of electric/hybrid eVTOL aircraft for Public Services2. We believe that in the next decades eVTOL aircraft will have the potential to become an essential tool to Public Service agencies around the world in applications such as firefighting, public safety, search and rescue, disaster relief and law enforcement. This is due to several major factors. • First, with the increasing popularity of small, unmanned aircraft vehicles (UAVs) or drones, many companies today are focusing on the development of passenger UAVs designed to accommodate up to five passengers or equivalent cargo payload. Many such configurations are electric or hybrid-electric designs with VTOL capabilities. Several of these projects have started a flight test program and many more are expected to be in the experimental and development phase in 2020. Such revolutionary vehicles could be in commercial operations by 2030. These eVTOL systems could be ready for selected Public Services missions even sooner. • Second, although these advanced eVTOL vehicles under development still need access to fuel (hybrid) and/or electric charging capability, they can take off and land from almost anywhere. Therefore, such vehicles, both manned and unmanned can be successfully integrated for the critical missions of the Public Services with extra deployment flexibilities. • Third, advancement in electric propulsion systems in the automotive industry together with NASA’s leading efforts in electrification of aircraft propulsion systems, FAA’s ongoing active eVTOL certification programs, and EASA’s proposed framework for the certification of electric/hybrid small category VTOL aircraft in Europe [ref. 3] will help accelerate industry electric propulsion system development and integration. • Finally, eVTOL vehicles could be deployed for Public Services sooner than air taxi or other commercial applications, since Public Services missions may be more easily approved based on specific mission criteria, localized airworthiness authority for public-use aircraft3, and are normally operating under centralized airspace management and control by the theater command. Moreover, public perception and acceptance are generally less of a concern when operations save lives and benefit the wider community. The prioritized introduction of eVTOL aircraft in Public Services is ambitious, but we believe it is achievable in the coming decades if fundamental enablers (people and technologies) are engaged in defining the objectives and needs of these missions. The revolution that is currently taking place in eVTOL aircraft represents an unprecedented opportunity to develop a safer, more affordable, more available and more environmentally friendly future of vertical flight. To ensure that these novel aircraft meet the future expectations of Public Services, it is essential to take a collaborative and multi-disciplinary approach to their development, across engineering disciplines, policy-making, program management, business case development, manufacturing, and flight demonstrations. It should be noted that the term eVTOL (in the near term) used throughout this publication implies aircraft capable of transporting up to 5 persons which may or may not include a pilot if operated fully autonomously, assuming an average of 200 pounds (91 kg) per person or equivalent payload and a range up to 60 miles plus a suitable reserve. Hybrid or hydrogen powered eVTOLs would have greater range. For example, a “3-seat” eVTOL aircraft may only be able to carry two fully equipped firemen, and payload capacity is more relevant when used for the supply mission. Moreover, this paper concentrates on the “last-mile” solutions with a deployment time of no more than 6 hours. Although not specifically discussed in this document, it is understood that the future of Transformative Vertical Flight in general and Public Services, in particular, will also involve smaller UAVs that will undoubtedly play a crucial role in future aerial operations. For example, smaller unmanned aircraft may be used to dispatch medical supplies, portable filtration systems or perform the Search task of future Search and Rescue (SAR) operations. Close collaboration between the aircraft industry, the Civil Aviation Authorities (CAA), e.g., Federal Aviation Administration (FAA), European Aviation Safety Agency (EASA), Transport Canada Civil Aviation (TCCA) and the Department of Defense (DoD) certifiers, will help identify Public Services requirements, define expectations and limit development cost and timescales. Take the US Air Force Agility Prime as an example, the majority of the eVTOL application opportunities and mission elements identified are in line with the NASA TVF WG-4 objectives and use cases. Together, it forms a strong partnership to accelerate the development, certification, and practical deployment for public service missions. The US Air Force Agility Prime has been a collaboration partner on this white paper, and provided valuable input and recommendations. Most of the eVTOL public service mission elements discussed in this paper and additional use cases envisioned by the NASA TVF WG-4 team are shared by the Agility Prime program. The focus and efforts of the Agility Prime in product and system development, industry and government partnership, accelerated certifications as well as early test and deployment are totally in sync with the path forward recommended by this white paper. This kind of collaboration and partnership will help enable the practical use of the eVTOL for public service missions, benefit the eVTOL public acceptance, and accelerate the eVTOL industry revolution.
Combined Global Navigation Satellite Systems in the Space Service Volume
Besides providing position, navigation, and timing (PNT) services to traditional terrestrial and airborne users, GPS is also being increasingly used as a tool to enable precision orbit determination, precise time synchronization, real-time spacecraft navigation, and three-axis attitude control of Earth orbiting satellites. With additional Global Navigation Satellite System (GNSS) constellations being replenished and coming into service (GLONASS, Beidou, and Galileo), it will become possible to benefit from greater signal availability and robustness by using evolving multi-constellation receivers. The paper, "GPS in the Space Service Volume," presented at the ION GNSS 19th International Technical Meeting in 2006 (Ref. 1), defined the Space Service Volume, and analyzed the performance of GPS out to seventy thousand kilometers. This paper will report a similar analysis of the signal coverage of GPS in the space domain; however, the analyses will also consider signal coverage from each of the additional GNSS constellations noted earlier to specifically demonstrate the expected benefits to be derived from using GPS in conjunction with other foreign systems. The Space Service Volume is formally defined as the volume of space between three thousand kilometers altitude and geosynchronous altitude circa 36,000 km, as compared with the Terrestrial Service Volume between 3,000 km and the surface of the Earth. In the Terrestrial Service Volume, GNSS performance is the same as on or near the Earth's surface due to satellite vehicle availability and geometry similarities. The core GPS system has thereby established signal requirements for the Space Service Volume as part of technical Capability Development Documentation (CDD) that specifies system performance. Besides the technical discussion, we also present diplomatic efforts to extend the GPS Space Service Volume concept to other PNT service providers in an effort to assure that all space users will benefit from the enhanced interoperability of GNSS services in the space domain. A separate paper presented at the conference covers the individual GNSS performance parameters for respective Space Service Volumes.
Spaceflight Operations Services Grid Prototype
NASA over the years has developed many types of technologies and conducted various types of science resulting in numerous variations of operations, data and applications. For example, operations range from deep space projects managed by JPL, Saturn and Shuttle operations managed from JSC and KSC, ISS science operations managed from MSFC and numerous low earth orbit satellites managed from GSFC that are varied and intrinsically different but require many of the same types of services to fulfill their missions. Also, large data sets (databases) of Shuttle flight data, solar system projects and earth observing data exist which because of their varied and sometimes outdated technologies are not and have not been fully examined for additional information and knowledge. Many of the applications/systems supporting operational services e.g. voice, video, telemetry and commanding, are outdated and obsolete. The vast amounts of data are located in various formats, at various locations and range over many years. The ability to conduct unified space operations, access disparate data sets and to develop systems and services that can provide operational services does not currently exist in any useful form. In addition, adding new services to existing operations is generally expensive and with the current budget constraints not feasible on any broad level of implementation. To understand these services a discussion of each one follows. The Spaceflight User-based Services are those services required to conduct space flight operations. Grid Services are those Grid services that will be used to overcome, through middleware software, some or all the problems that currently exists. In addition, Network Services will be discussed briefly. Network Services are crucial to any type of remedy and are evolving adequately to support any technology currently in development.