|
|
Home Author Templates Call for Papers Technical Program Registration Sponsor/Exhibit Committee Contact Search |
|
Reinventing Space: Design of Low-Cost Space Missions Course |
|
||||||||
Large.jpg){kind=logo}
Past Conference Papers:
Responsive Operations
| Paper Number RS1-2003-3004: Interoperable Scheduling Concept, Low-Cost Responsive Ground Systems and Operations | |
| Fred Wynkoop (L-3 Communications) | |
| View/Download:Presentation | Paper | |
| Abstract: Low-cost and responsive satellite ground systems previously unattainable, are now possible. | |
| | |
| Paper Number RS1-2003-5000: Technology for Responsive Space Capability | |
| Robert Pugh (AFRL) | |
| View/Download:Presentation | |
| | |
| Paper Number RS1-2003-5001: Responsive Launch With the Scorpius Family of Low-Cost Expendable Launch Vechicles | |
| James R. Wertz (Microcosm), Robert Conger (Microcosm), Jack Kulpa (Scorpius Space Launch Company) | |
| View/Download:Presentation | Paper | |
| Abstract: Scorpius® is a family of low cost, expendable launch vehicles under development by Microcosm. The first orbital vehicle in the family is the Sprite Small Launch Vehicle (700 lbs to a 100 NMi circular orbit due East from the launch site), currently scheduled for its initial test flight in 2006. One of the top-level requirements on the entire vehicle family is to be able launch within 8 hours of arrival of the payload at the launch site or a formal request for launch for those payloads stored at the site. This paper addresses the economic, technical, regulatory, philosophical, and cultural hurdles to be overcome to achieve this objective and how we are going about getting over (or burrowing under or going around) these to get there. The most fundamental hurdle is economic, i.e., the launch vehicle itself must be sufficiently low cost to allow it to be built to inventory. The cost of the Sprite vehicle is about $2 million which represents an interest cost for vehicles in inventory of about $15,000 per month per vehicle which we believe would be acceptable in most business models. The technical hurdle is overcome largely by designing the vehicle from the outset to be moved and launched expeditiously ? i.e., stored as an assembled launcher to which the payload is attached and the completed vehicle is then transported to the pad, fueled, and launched. The most serious difficulties are largely the regulatory, philosophical, and cultural hurdles that dictate that launches in the West simply aren’t done in a few hours, even though this has been done in Russia for many years. In the U.S., there needs to be time for approvals, notices to air and ship traffic, and the cultural impediment that says that the payload “must” be checked out on the launch pad. These challenges are perhaps the biggest and must ultimately be addressed jointly by the launch provider, the customer, and the government. | |
| | |
| Paper Number RS1-2003-6002: Fast Responsiveness Experiment Flight Opportunities Using SSPC | |
| Gerald Murphy (Design_Net Engineering), Kirk Stewart (Design_Net Engineering) | |
| View/Download:Presentation | Paper | |
| Abstract: The need to rapidly and affordably fly small space missions for science investigations, technology demonstrations, and risk reduction efforts is a frequently cited critical deficiency in our national space efforts. For small payloads whose missions can be accomplished from a low altitude, mid-inclination orbit, this problem can now be solved. Using a NASA mission flown in CY2000 as a proof-of-concept demonstration, Design_Net Engineering, LLC has performed IR&D and developed concepts and designs for a flexible system of Small Satellite Payload Carriers (SSPC™). These systems are small enough to be accommodated late in the manifesting cycles for launch on Space Transportation System (STS) missions to the International Space Station (ISS). Launch in Orbiter locker or soft stowage areas enables payload missions with less than 6 month lead time and very low launch costs. An SSPC™ is deployed by shuttle astronauts during a short EVA, using standard EVA proven hardware. SSPC™s are externally attached to the space station at one of many attachment locations used by the astronauts during station assembly. An SSPC™ does not require any station resources, which is a key in obtaining accommodation. They operate independently of the space station by providing their own electrical power, telemetry, command, thermal control, avionics, and experiment interfaces. They communicate and operate directly to Earth through the payload user’s selected ground support system. This may be the DoD’s AFSCN, a NASA or commercial network, or a university ground station, and an SSPC™ operates as would an independent small satellite, although it is attached to ISS. These SSPC™ systems require no costly attitude control or propulsion systems, yet numerous attitudes, orientations, and mission durations are possible because of the large number of attach locations. Built affordably, as two separable modules, the SSPC™s use a main base module to house the typical satellite payload support or satellite bus systems and a second module to accommodate added payloads. The main base module stays on orbit after an initial deployment mission to provide a resident support capability for subsequent missions which use interchangeable payload modules. Payloads and missions may be of varied durations and benefit from the cost effectiveness of the reuse of the base module. Ultimate responsiveness is achieved by this system and space flight can be available as quickly as a payload can be built, integrated into a payload support module, and delivered for the next STS mission to the ISS. No other current concept offers this responsiveness or potential for the lowest cost flights on a regular basis. Typical payload support capabilities are in the neighborhood of 30 lbs, 30 to 50 watts, and 10 to 20kbps average data rate. Final capabilities will be determined by the sponsors’ requirement trades and applications. This concept is currently being evaluated for development by the government. Commercial opportunities are also under consideration. This paper will describe the concept, system, alternatives, and payload support capabilities. | |
| | |
| Paper Number RS1-2003-9004: Demonstrating Low Cost Access to Space for Small Satellites: Space Test Program-1 Mission | |
| Tim Sumrall (Kirtland Air Force Base) | |
| View/Download:Presentation | Paper | |
| Abstract: The DoD Space Test Program (STP) is charged with providing spaceflight to Research and Development (R&D) payloads from the Space Experiments Review Board (SERB) priority list. STP is dedicated to timely, cost-effective spaceflight opportunities. Often these opportunities result in innovative missions that maximize the amount of SERB payloads manifested per launch vehicle. In this spirit, STP has designed a multi-manifest mission that will deliver up to seven separate spacecraft to different earth orbits. This mission is called the Space Test Program–1 (STP-1). STP-1 is the most aggressive United States Department of Defense (DoD) multi-satellite R&D mission ever attempted. This complex mission is a collaboration between the Air Force Space Command (AFSPC), the Air Force Research Laboratory (AFRL), and the Defense Advanced Research Projects Agency (DARPA). Other participants include the Naval Research Laboratory (NRL), the Naval Postgraduate School (NPS), United States Naval Academy (USNA) and the United States Air Force Academy (USAFA). This paper will briefly review the STP-1 mission payloads. The focus of this paper is to discuss the Evolved Expendable Launch Vehicle (EELV) Secondary Payload Adapter (ESPA) and challenges facing the first ESPA mission. STP is managing this mission utilizing a diverse Integrated Product Team (IPT). This IPT is working to overcome several unique challenges in balancing limited manpower resources with the requirement to manage all the separate STP-1 mission components. | |
| | |
| Paper Number RS1-2003-9005: The Scorpius Expendable Launch Vehicle Family and Status of the Sprite Small Launch Vehicle | |
| Shyama Chakroborty (Microcosm), James R. Wertz (Microcosm), Robert Conger (Microcosm), Jack Kulpa (Scorpius Space Launch Company) | |
| View/Download:Presentation | Paper | |
| Abstract: Microcosm and the Scorpius® Space Launch Company are developing a family of expendable launch vehicles that will provide low-cost, responsive access to space. The Scorpius® family includes single and two-stage suborbital and orbital vehicles with payloads ranging from 700 lbs to LEO for the Sprite Mini-lift Launch Vehicle to over 50,000 lbs to LEO (18,000 lbs to GTO) for the Heavy-lift vehicle. Two suborbital vehicles have been flown successfully from White Sands Missile Range, including the SR-XM-1 in March 2001, which was, effectively, a full-scale test of a Sprite pod, although not all of the Sprite components were flown. The first Sprite orbital launch is scheduled for 2006. This paper describes the technology and development plan of the Sprite Small Launch Vehicle (SLV). Starting with a contract from the Air Force Research Laboratory in 1993, technology development has progressed with increasing maturity in design, manufacturing techniques, and component development and qualification. Low-cost and scalable ablative engines based on flight-proven technology, allcomposite propellant tanks, and a Tridyne-based High Performance Pressurization System are all in the final stages of qualification. A low-cost baseline design has been developed for the Sprite upper stage. The Scorpius® modular design approach, built around scalable critical components such as the engines and all-composite propellant tanks, will allow us to transition from the Sprite SLV to the medium-lift Exodus and then to heavier-lift vehicles if the need justifies the economic investment. In addition to carrying primary payloads, the entire Scorpius® family will have provisions to use the excess lift for any launch to carry multiple, small auxiliary payloads at little or no cost for universities, industry, and government organizations to obtain component testing with quick turn-around. These auxiliary payloads remain attached to the stage, but are given access to power and telemetry. This allows the system to realize maximum benefit from each launch. The Scorpius® vehicles are designed to facilitate encapsulated payloads, vertical transport of the assembled vehicle to the pad, and little or no on-pad preparation. The low recurring cost allows us to build to inventory and enables true launch-on-demand. The design incorporates operational features and procedures that will allow us to launch Scorpius® vehicles within 8 hours of arrival of the payload at the launch site or a request for launch for payloads stored on site in a launchable configuration. Thus, Scorpius® is fully capable of meeting the challenge of responsive access to space. | |
| | |
| Paper Number RS2-2004-5000: Development and Operations of Flight Systems for Responsive Missions | |
| Michael J. Mahoney (Universal Space Lines), Layne Cook (Universal Space Lines) | |
| View/Download:Paper | |
| Abstract: Vehicle flight operations (and more particularly, the operation of a vehicle’s flight through its onboard software) must be built from the “ground up” to support responsive, safe flight at a significantly lower cost than that experienced with today’s space flight vehicles. To accomplish this, we must deviate from the current flight system paradigm. We must design and develop systems from the beginning considering the entire life cycle (how to fly it, flight software maintenance and upgrades, etc.) This includes developing flight test prototypes and test articles early in the system life cycle to gain “real” experience and determine the “real” requirements such that the ultimate design leads to the “correct” development product. Flight operations (and more specifically, the flight systems and guidance navigation and control (GN&C) operations) can be developed early in the program to support rapid test articles, rapid mission planning and rapid flight software development, without an army of people doing each function. This development “system” can then also support the operations of the flight systems with flight software maintenance and turn-around and pre, during and post flight analysis. One tool that supports this design philosophy has already been partially developed under NASA’s NRA 8-30 Space Launch Initiative (SLI) program. It is called the Integrated Development and Operations System (IDOS). IDOS is an integrating environment designed to support the flight software life cycle needs of reusable launch vehicles (per SLI goals) and by extension other aerospace vehicles. This integrated environment provides for design, development, implementation, test, validation, operation (mission planning and execution) and maintenance of advanced GN&C algorithms in a flight operations environment. Using IDOS, we have demonstrated an order of magnitude reduction in the required effort to transform an advanced GN&C “idea” (algorithm) into working flight software operating on a flight like processor in real time. | |
| | |
| Paper Number RS2-2004-3000: Operational Concept Modeling for Responsive Space | |
| Herschel Melton (AllySoft), Yvonne Sheets (SPARTA) | |
| View/Download:Presentation | Paper | |
| Abstract: This paper addresses the utility of the application of highly visually-oriented modeling techniques to system operational concept development and defines a methodology for migrating concepts into larger overarching architectures. This is crucial exercise which enables discussions about utility to the warfighter and supplies additional information about how future concepts my fit in the context of his mission. This paper describes an example of the application of these techniques to a Responsive Launch System and highlights the contribution of the modeling techniques to the development of the Operational Concepts themselves. The paper also explores characteristics of the tools available to support this approach, the application of the methodology and the potential utility of the tools. The tool utilized in the sample case was Extend™. This methodology also illustrates the role of such modeling within a “Team Environment” and how it can be applied to gain stakeholder buy-in early in the concept development process. We have also explored the possibility of a more formal role for such approaches in the initial phases of system development as part of a robust Systems Engineering process. These suggestions have derived from applications of this methodology to a broad set of concept development problems and have resulted in a set of lessons learned that will be discussed. | |
| | |
| Paper Number RS2-2004-A019: Responsive Space Requires Responsive Manufacturing | |
| Todd Mosher (USU), Brent Stucker (USU) | |
| View/Download:Presentation | |
| | |
| Paper Number RS2-2004-A020: A Conformally-Mounted SatCom Antenna System To Support Stars Phase-2 Testing | |
| Cooke (EMS Technologies) | |
| View/Download:Presentation | |
| | |
| Paper Number RS2-2004-A022: Wallops Flight Facility | |
| Reed (WFF) | |
| View/Download:Presentation | |
| | |
| Paper Number RS3-2005-2002: Interim Results from NSSO Responsive Space Operations Architecture Development | |
| Patrick Frakes (NSSO) | |
| View/Download:Presentation | Paper | |
| Abstract: Some measure of responsiveness is likely to emerge as a significant new requirement for our nation’s future space capabilities. The DoD Executive Agent for Space directed the National Security Space Office (NSSO) to develop a Responsive Space Operations (RSO) Architecture to give the senior Intelligence Community and Department of Defense leadership an integrated picture of missions, needs, required capabilities, and current shortfalls associated with responsive space capabilities. In FY04, the Architecture and Engineering Group of the NSSO began development of the RSO Architecture. The Terms of Reference (TOR) was approved and the architecture development team began the process to identify approaches to achieve the long-term (adaptability), mid-term (flexibility), and short-term responsiveness (agility) attributes that space capabilities will need in order to respond to dynamic world environments, national priorities, and operational requirements. NSSO expects the architecture development to be completed in late 2005, but presents an interim “work-in-progress” report, including a discussion of capability needs, applicable technologies, potential architecture concepts, and analytical approaches as the study proceeds into the concept development and analysis phases. | |
| | |
| Paper Number RS3-2005-4002: Responsive Ground Systems | |
| Findiesen (Space Launch Initiative) | |
| View/Download:Presentation | |
| | |
| Paper Number RS3-2005-4004: The Multi-Mission Satellite Operations Center | |
| Jason Parker (Schriever Air Force Base) | |
| View/Download:Presentation | Paper | |
| Abstract: The concept for the Multi-Mission Satellite Operations Center (MMSOC) was borne of the need for a single agency responsible for the oversight and/or operations (cradle to grave) of unique space based/focused missions. Experienced Air Force and contractor operators supported by an in-house team of acquisitions and development experts who can expedite the fielding of new programs constitutes the backbone of the MMSOC. The Air Force Space Command (AFSPC) vision for MMSOC is for a single facility to perform satellite operations for AFSPC Space Vehicles (SVs) not currently supported by a Space and Missile Systems Center (SMC) System Program Office (SPO). The MMSOC will also perform other assigned missions, such as operations conducted in support of non-AFSPC SVs. AFSPC operations for non-AFSPC SVs include support to other United States Government agencies [e.g., National Reconnaissance Office (NRO), National Aeronautics and Space Administration (NASA), and National Oceanic and Atmospheric Administration (NOAA)], Allied Nations, and various Launch Vehicle (LV) boosters. The MMSOC will also be a satellite command and control spiral evolution resource for test and evaluation of new systems. With the increased availability of commercially based satellite command and control systems, the MMSOC will be an in-house AFSPC resource for analysis of these systems and architectures. These evaluations will provide feedback between the operational and development communities and lead to a continuous loop of overall system improvement. The MMSOC staffing is envisioned to be a Combined Task Force (CTF) with a mix of Active Duty AFSPC personnel, Air Reserve Component (ARC) personnel, civilians, and contractors. Additionally, the MMSOC is envisioned to have operational relationships with Air Force Research Laboratory (AFRL), to provide personnel, as liaisons, to support MMSOC development evaluations. This force mixture will facilitate flexibility, continuity, and stability to support legacy missions and future AFSPC satellite programs, as well as newly assigned AFSPC missions. The MMSOC is the end-state, and as currently planned will be officially "turned on" in the FY'08 timeframe. The out-going transition of four legacy missions and the complete rebuild of two Space Operations Centers (SOCs) at Schriever Air Force Base will be the major milestones for final stand up of the MMSOC. 3rd Responsive Space Conference 2005 2 The details behind the "Re-build" will be covered later in the paper. | |
| | |
| Paper Number RS5-2007-6005: Net-Centric Operations and Responsive Spacecraft - A Guide to Implementation | |
| Jeffrey L. Janicik (Innoflight) | |
| View/Download:Presentation | Paper | |
| Abstract: Net-Centric Operations is clearly a significant enabler for Responsive Space. One of the key enablers that to Net-Centric Operations is the Global Information Grid (GIG). The GIG represents a globally interconnected, end-to-end set of information capabilities and processes for collecting, processing, and managing information on demand to warfighters, policymakers, and support personnel. The GIG fulfills a fundamental principle of Net-Centric Operations by securely connecting people and systems regardless of time or place, providing vastly superior situational awareness and better access to information for accelerated decision-making. At the core of the GIG is a high throughput TCP/IP network. The “I/O” to the core is data-generators and data-users. The users include secure IP network users, command centers, and field units such as infantry and armored divisions. The generators are an increasing number of sources that both front line and rear command posts desire to utilize. These sources can be spacecraft assets (imaging), UAV (imaging & offensive weapons), remote controlled platforms (Remotely Operated Vehicles, deployable surveillance) and Beyond Line of Site (BLOS) near space platforms such as balloons and high-altitude airships. Most of these sources, especially those in space, are not networked and those that are typically rely on point-to-point stovepipe communications systems. In extending the GIG to the scores of DoD users, it is important to do the same on the source side all the way to individual payloads and sensors. Once both the users (shooters) and the sources (sensors) have full and transparent connectivity, the true benefits of the GIG concept will be fully utilized and expanded beyond the terrestrial domain. This paper will describe how the aerospace industry should implement IP in the spacecraft bus design to realize this sensor-to-shooter benefit of net-centric operations while keeping cost and schedule to a minimum. The key facets to this implementation include the following: a network-enabled bus that establishes IP addresses at each desired sensor, secure IP-compatible communications security (COMSEC), unaltered use of RFC’d Internet standards, and smart adaptation of the physical layer to maximize bandwidth efficiency. | |
| | |
| Paper Number RS5-2007-7004: Aerodynamic and Propulsion Assisted Maneuvering for Orbital Transfer Vehicles | |
| Patrick R. Jolley (Utah State University), Stephen A. Whitmore (Utah State University) | |
| View/Download:Presentation | Paper | |
| Abstract: The ability to perform rapid and unpredicted orbital transfers will provide the ability for unpredictable reconnaissance or timely rescue missions. This paper examines the means and ways of enabling responsive space through propulsive or aero-assisted maneuvers. A conical hypersonic waverider was designed to execute these maneuvers. The aerodynamic database was generated using hypersonic incidence angle analysis tools with a viscous skin-drag correction. A comparative performance analysis is performed by examining some of the vehicle’s qualities. Some of these are stagnation point heating, handling qualities and controllability, etc. The orbital transfer trajectories were analyzed using an interactive simulation tool. Results have confirmed previous research that aero-assisted maneuvers are more efficient than purely propulsive maneuvers alone for executing synergetic plane changes. These results are contingent on the basis that the vehicle has an integrated propulsion system and has a thermal protection system as analyzed here. | |
| | |
| Paper Number RS3-2005-5002: PNP Transceiver-FNT | |
| K.D. Brown (NNSA KCP) | |
| View/Download:Presentation | Paper | |
| Abstract: The National Nuclear Security Administration’s (NNSA) Kansas City Plant (KCP) has supported design, development, and production of weapon flight test telemetry technology in conjunction with the national weapons laboratories for decades. The notion of a responsive satellite is predicated on bus components that are flexible, pre-qualified, and interoperable with other bus subsystems across a quickconnect interface bus. This paper describes a novel, standardsbased, modular, scalable, dynamically configurable, wireless network transceiver architecture that can support integration into a satellite interface bus to provide flexible network data links for a range of network centric requirements A plug and play interface is under development and will be integrated into the Flexible Network Transceiver (FNT). The paper will describe the transceiver’s development, architecture, and capabilities which support responsiveness. | |
| | |
| Paper Number RS3-2005-A006: Mid-Range Vision for Launch and Test Range System | |
| Michael B Coolidge (Satellite and Launch Control) | |
| View/Download:Presentation | |
| | |
| Paper Number RS4-2006-4002: Pulling the Pieces Together at AFRL | |
| Peter M. Wegner (USAF AFRL/VS), Col. Rex R. Kiziah (USAF AFRL/VS) | |
| View/Download:Presentation | Paper | |
| Abstract: In partnership with Air Force Space Command, the Office of Force Transformation, and the other military services’ S&T and R&D organizations, the Space Vehicles Directorate of the Air Force Research Laboratory is aggressively pursuing the development of responsive space technologies and spacecraft. The Directorate has made responsive space one of its six core thrusts. The objective of the responsive space thrust is to develop and demonstrate the technologies that will enable spacecraft with the following attributes: • Operational within six days of call-up • Total mass (<400 kg) and low-cost (<$30M mission costs, including spacecraft, launch and operations) • Tasking and data dissemination utilizing existing warfighting equipment and architectures • Satellite payloads are taskable by theater commanders/forces with direct downlink/data dissemination into theater assets • Missions-tailored for a specific theater of operations In order to realize this objective, the responsive space thrust consists of a robust portfolio of technology investments, ground and space experiments, and strategic collaborations. Even beyond this thrust, the philosophy of utilizing small, low-cost satellites with valuable military capability is a key component of the Space Vehicles’ vision for the future. This philosophy and experimental approach is reflected in the recent, highly successful XSS-11 Spacecraft and the upcoming TacSat-2 and TacSat-3 experiments. This paper will discuss the work being performed by the Air Force Research Laboratory and its strategic partners to enable the future vision of low-cost, highly responsive, militarily useful spacecraft. This will include a discussion of the XSS-11 spacecraft and its highly successful experiments, current investments in plug-n-play technologies, the development of a modular spacecraft bus based upon these technologies, a ground-based test-bed to enable rapid experimentation with these technologies, and the TacSat-2 and TacSat-3 space flight experiments to explore the military utility of this new class of space systems. | |
| | |
| Paper Number RS4-2006-5001: SciBox Based Uplink Operations Planning Concepts for Responsive Space | |
| Andy McGovern (Johns Hopkins University Applied Physics Laboratory) | |
| View/Download:Presentation | Paper | |
| Abstract: Time sensitive targeting is of keen interest in the C2 arena. Implementations of this concept also appear in civilian space missions in the form “responsive targeting,” meaning an unexpected event warrants a rapid response. The goal in both C2 and civilian arenas is to quickly produce the desired effect at minimal cost and low risk. Techniques that greatly simplify and streamline the processes of mission planning, command sequence generation and command upload have been developed in the civilian space arena by the Applied Physics Laboratory of Johns Hopkins University. We have developed innovative mission operations techniques and software tools for the CRISM instrument on board the Mars Reconnaissance Orbiter (MRO). CRISM is a gimbaled visible/infrared spectrometer for analyzing the Martian surface and atmosphere. CRISM’s gimbaled platform and MRO’s roll capabilities make responsive targeting and pointing a challenge that we have addressed. We streamline the process of planning, command sequence generation and upload by linking flight software with planning software via a macro library and a visualization tool. Our approach enables the scientist (or the field commander) to directly task the instrument without the need of an operations support center. Part of CRISM’s mission is to target dust storms which form and dissipate rapidly during one season. Our approach, which enables the scientist to command the instrument at a high level and visualize predicted results, is critical for these time sensitive observations. This presentation provides an overview of our approach to responsive targeting in the context of the CRISM mission and how it may be implemented for responsive space systems. | |
| | |
| Paper Number RS4-2006-5005: On-orbit Calibration and Focus of Responsive Space Remote Sensing Payloads | |
| Thomas Chrien (Raytheon Space and Airborne Systems), Stephen Schiller (Raytheon Space and Airborne Systems) | |
| View/Download:Presentation | Paper | |
| Abstract: Radiometric, spectral, and spatial response performance and calibration knowledge requirements have been traditional cost drivers for remote sensing payloads. Performance has a direct relationship to the usefulness of the information product, including (1) bore-sight calibration in order to achieve geolocation accuracy, (2) optimization of focus to maximize spatial resolution, and (3) absolute spectral and radiometric calibration for effective atmospheric compensation. Meeting strict requirements prior to launch is problematic. Careful (and costly) compensation must be made for gravity effects, and thermal vacuum test conditions can only approximate on-orbit thermal environments. Furthermore, the trauma of launch and subsequent space contamination can invalidate a “perfect” pre-launch calibration. An alternative approach is to fine tune focus and calibration after the payload is on orbit using vicarious calibration techniques. This reduces cost and schedule by relieving the accuracy requirements and complexity of pre-launch calibration measurements. Cost / benefit rationale as well as conceptual approaches to pre-launch testing and on-orbit focus and vicarious calibration will be presented. | |
| | |
| Paper Number RS4-2006-7001: Autonomous Operations for Responsive Spacecraft | |
| Jackie Reilly (a.i. Solutions), Terrance Yee (Microsat Systems) | |
| View/Download:Presentation | Paper | |
| Abstract: MicroSat Systems, Inc. (MSI) is currently supporting the Air Force Research Laboratory (AFRL) on several responsive space programs demonstrating tactically useful small satellites with autonomous operations. Contrary to previous autonomy efforts, these missions have autonomous on-board software which is specifically designed to allow end-users (or Warfighter), with no satellite expertise, to task the vehicle directly. This capability puts the Warfighter in direct control of a spacecraft changing several aspects of the original paradigm throughout the mission. The use of autonomy tools and modular software elements change the paradigms for traditional spacecraft operations. The change in the operational concept creates implications for overall project development timelines and for the end user in the field. Autonomous operations must be accounted for at the beginning of the requirements definition phase. While it is possible to upgrade existing systems after they are already designed, it is much more straightforward to initially design with the non-expert end-user in mind. This allows the appropriate selection of command and telemetry architecture to accommodate both the traditional expert end-user and a specialized interface for the Warfighter. Designing the Warfighter interface to be simple and minimalist from the beginning has profound impacts on the structure of the entire autonomous software. There is a major impact on spacecraft integration and testing throughout the development cycle and during on-orbit commissioning. There is significant synergy gained from coordinating the automation software (that performs ground testing), on-board testing (to verify state of health), and commissioning the spacecraft on orbit. By careful design of these capabilities, it is possible to not only save time but also increase the degree to which the ground team follows the “test like you fly” principle. The net impact of these changes is the following: shorten the time needed to deliver a working product to the end user, bring the end user concerns closer to the design team, change the focus of spacecraft utility design from a strategic asset to one which has short term tactical significance, and to place extremely powerful space assets in the hands of ground forces within minutes of request. This places a unique set of requirements on the software to be as easy to use as possible while also ensuring the safe operation of the spacecraft. Pairing the expertise of ground support and current autonomous ground system software with the expertise of spacecraft developers and current on-board software will help to design the on-board autonomous software that accomplishes this task. | |
| | |
| Paper Number RS4-2006-7003: Concept of Operations for Operationally Responsive Space | |
| Don Knight (General Dynamics C4 Systems) | |
| View/Download:Presentation | Paper | |
| Abstract: This paper provides a Concept of Operations (CONOPS) on how United States Strategic Command (USSTRATCOM) and theater Combatant Commands (COCOM) might deploy and employ, and how the services might organize, train, and equip an Operational Responsive Space (ORS) weapon system. Since this CONOPS only covers satellite systems, it uses the term ORS over Joint Warfighter Space (JWS) as JWS has evolved to include both space and near-space forces. While the paper does not necessarily reflect the views and/or positions of any service, combatant command, or Department of Defense, it is based upon over 30 different technical interchange meetings conducted over the last two years with a multiple of agencies involved with ORS. ORS satellites can augment Space Force Enhancement (SFE), Space Control (SC), and Space Force Application missions. For classification purposes, this paper only covers SFE operations, but also has some applicability to SC missions. Space Force Application requires its own separate CONOPS. The paper begins by identifying the various SFE missions an ORS could perform and recognizing that they fall into two natural orbit regimes: LEO and MAJIC. It then looks at four different trigger events that would cause the deployment of an ORS constellation. Next, the paper identifies launch parameters, constellation sizing, launch windows (to include a Time Phased Force Deployment List of ORS missions), and early orbit check-out timelines required to support the theater commander. Under employment, the paper first examines how the roles and responsibilities for an ORS would be divided between USSTRATCOM and the theater commander. It then presents how mission planning; collection; mission data downlinking; mission data processing; and telemetry, tracking and commanding would be accomplished. Switching to the services’ responsibilities, the paper provides an organizational structure to include the types and numbers of both the operational and acquisition units required. “Training the way we will fight” is a vital aspect of the warfighter acceptance of ORS and the paper identifies how peacetime training would be accomplished. The paper concludes with a table of allowance for equipping an ORS weapon system to include both an Initial and Final Operational Capability. | |
| | |
| Paper Number RS4-2006-7004: Navy Team Responds to Bandwidth Challenges in Support of War Efforts with Innovative Employment of UHF Follow-On (UFO) and LEASAT Satellites | |
| Mike Mattis (Maxim Systems, Inc.), Neil Butler (Maxim Systems, Inc.), Jack Turner (Maxim Systems, Inc.) | |
| View/Download:Presentation | Paper | |
| Abstract: The U.S. Navy’s UFO satellite constellation is the replacement for the Fleet Satellite (FLTSAT) and LEASAT spacecraft and maintains the Navy’s global narrowband communications network. In mid 2002, the operational community expressed the need for increased narrow-band bandwidth in support of Operation Enduring Freedom (OEF). The Naval Networks and Space Operations Command (NNSOC) and the Navy Communications Satellites Program (PMW146) were tasked to investigate methods to increase narrow-band capacity. The 11th UFO spacecraft would not be available until the second quarter of FY04 so the UFO/LEASAT team examined a wide variety of options, including employment of the UFO on-orbit spare satellite (UFO-2). Analysis and testing proved a frequency reuse scheme could allow 12 UFO-2 channels to be turned on to result in a 30% capacity increase in the CENTCOM Area Of Responsibility (AOR). This improved capacity realized by the warfighter in support of OEF saved approximately $1M/month for equivalent commercial services. In Oct 2002, the UFO/LEASAT team, acting as the Acquisition agent for the Joint Staff, inquired about the cost and availability of LEASAT satellites to support emerging bandwidth requirements in the CENTOCM AOR utilizing some of the new frequency reuse techniques developed for UFO-2. Although the LEASAT contract had been terminated once the UFO constellation was deployed; the Program Office coordinated an acquisition scheme with the Royal Australian Navy and negotiated a Memorandum of Agreement with the Australian Ministry of Defense to procure services and share LEASAT-5. To better support users, Strategic Command (STRATCOM) requested LEASAT-5 be moved to the Indian Ocean (IO) to support emerging requirements for Operation Iraqi Freedom (OIF). The UFO/LEASAT team obtained approval for LEASAT-5 reactivation and coordinated use of the Guam TT&C equipment to support the relocation effort. Even after the TT&C facility in Guam was unexpectedly destroyed by a typhoon in December 2002, a new TT&C site in Australia was brought on line, avoiding a three-month delay of the satellite repositioning effort and enabling immediate initiation of the move. Upon receipt of funding and final approval from the Joint Staff, the UFO/LEASAT team had the LEASAT contract modification fully funded and the LEASAT-5 spacecraft moving within 24 hours. In response to this urgent requirement to provide an additional SATCOM asset in the IO, STRATCOM also requested development of a situational awareness tool that could be used by warfighters and communications planners to show LEASAT-5 availability as it was being moved into theater. The team used Satellite Tool Kit (STK) modeling software to produce a simple self extracting flash video tool that could be quickly sent to communications planner and warfighters in country to determine when link closure would occur as the satellite drifted west to its final station. Often time Responsive Space is thought of as responsive launch. In this case the Navy utilized innovative reuse of existing assets and applied new Concepts of Operations (CONOPS) to identify additional assets and support mechanisms to rapidly mobilize additional SATCOM bandwidth to support the Warfighter. | |
| | |
| Paper Number RS4-2006-7005: Time Critical Targeting Using Responsive Tactical Satellites | |
| John Carrico (Applied Defense Solutions), Travis Langster (Analytical Graphics, Inc.) | |
| View/Download:Presentation | Paper | |
| Abstract: A key enabler for responsive space is the capability to respond to unanticipated military needs in any geographical theater in a timely fashion. The CONOPS and utility for Unmanned Aerial Vehicles (UAVs) have become critical assets in current military operations. UAVs are deployed to specific theaters of ongoing operations. However, when an unexpected national security event of interest occurs, UAVs can not provide the same capability to any location on the globe within hours. However, the migration of UAV CONOPS to space could re-locate an asset to any geographical theater within hours. This paper will discuss the utility of pre-deployed tactical satellites to achieve national security responsive space through modeling & simulation techniques. Scenario — A high value target on the ground is identified via HUMINT sources. A military plan is required to nullify the target. The military plan requires time critical targeting information for pre-mission operations which include imagery and other intelligence data. There are no airborne sensors in-theater to support the mission within the desired timeline. The theater commander requests a capability of a tactical satellite with appropriate sensors be tasked to provide mission support to a forward unit. Concept — A concept of operations for this solution utilizes knowledge and information about the orbit of a rapid response satellite. An in-theater soldier utilizes an existing chat tool (Instant Messenger in the business world or Jabber in military intelligence operations) for computing the window of opportunity for the in-theater soldier to know precisely when an overhead responsive satellite would able to image or intercept signals from the target location. The same device used for the chat session receives imagery or other data via e-mail from the satellite as it passes overhead. Data is downloaded from responsive space satellite to handheld device with Time Critical Targeting information (e.g. imagery, target coordinates, etc…). Alternatively, the device could be outfitted to upload tasking commands of known targets for imagery or signals collection. The commercial software tool computes the precise time of collection opportunity and this start/stop time is uploaded in the tasking plan. Summary — The technology to compute precise collection opportunities and provide them in-realtime to in-theater soldiers is available today. Responsive space concepts can be achieved prior to launching new systems. By implementing unique modeling, simulation & analysis techniques with existing space platforms and within existing military, intelligence, and DoD infrastructures – tactical data from space platforms can be delivered. Responsive space concepts can have immediate military utility and can be enhanced with dedicated responsive space platforms. | |
| | |
| Paper Number RS5-2007-4002: How TacSat-2 is Proving the Military Utility of Web Enabled Space Operations | |
| Terrance Yee (MicroSat Systems) | |
| View/Download:Presentation | Paper | |
| Abstract: MicroSat Systems, Inc. (MSI) recently participated in the launch and early orbit operations of TacSat-2. MSI provided the bus for this spacecraft and worked with a number of other organizations under the auspices of the Air Force Research Laboratory at Kirtland AFB to support integration, test, launch and operations activities. One of the most innovative aspects of this mission is the use of the Internet and World Wide Web to support operations. The utility of these methods was extensively demonstrated during the recovery of the mission following the early loss of communications due to ground system configuration mistakes. In this paper we will describe the capabilities of the TacSat-2 ground system to allow collaboration of a geographically diverse team. We will discuss the implications of these new capabilities on operational TacSat type vehicles and the systems they support with an emphasis on the utility provided to the military end customer. The calculation of such utility is peculiar to the Responsive Space paradigm because great emphasis is placed on the timeliness of delivery of critical information to lower echelon commanders rather than the sheer quantity and quality of total information produced which is more germane to strategic assets. The internet accessible tools created for the TacSat-2 ground system dramatically alter the utility calculations for these types of missions. We will also examine in detail several use cases from the first month of operations that exemplify the new capabilities and highlight their utility. These include cases of time critical responses to demand for new tasks as a result of the nature of the mission recovery where members of the technical team not in the mission operations center generated commands across the internet for operators to authenticate and execute, cases where collaborative planning of daily activities was supported by online tools, cases where international cooperation supported technical analysis of state of health and cases where real time pass support was coordinated across four states and two simultaneous communications links. We will also discuss how the use of the internet has standardized several telemetry products and allowed the creation of third party tools to support telemetry trending and real time notification of spacecraft events. | |
| | |
| Paper Number RS5-2007-6001: Virtual Mission Operations Center (VMOC) Development and Experimentation | |
| Eric Miller (General Dynamics), Mike Hurley (Naval Research Laboratory), Omar Medina (Naval Research Laboratory), Lt. Col. Jay Hopkins (Joint Space Operations Center), Lt. Col. Richard Lane (AF Space Battlelab), Capt. Ramon Veglio (AF Space Battlelab), Allen Kirkham (Army Space and Missile Defense Battle Lab), Will Ivancic (NASA Glenn Research Center), Brenda Jones (US Geological Survey EROS/SAIC), Ron Risty (US Geological Survey EROS/SAIC) | |
| View/Download:Presentation | Paper | |
| Abstract: An Operationally Responsive Space (ORS) system requires all system segments to work together effectively to support operational users. Efforts to advance the ground segment are discussed in this paper. Specifically, this paper discusses US Air Force, US Army, US Navy, and NASA demonstrations and experimentation based around the Virtual Mission Operations Center (VMOC). The intent is to begin standardizing the spacecraft to ground interfaces needed to reduce costs, maximize space effects to the user, and allow the generation of Tactics, Techniques and Procedures (TTPs) that lead to Responsive Space employment. Combining the US Air Force/Army focus of theater command and control of payloads with the US Navy’s user collaboration and FORCEnet consistent approach lays the groundwork for the fundamental change needed to maximize responsive space effects. This paper is the jointly written to properly include and describe the VMOC activities underway. | |
| | |
| Paper Number RS5-2007-6003: Tactical Spacecraft Commanding Service Architecture | |
| Puck-Fai Yan (Johns Hopkins University Applied Physics Laboratory), James A. McGovern (Johns Hopkins University Applied Physics Laboratory), Matthew Potter (Johns Hopkins University Applied Physics Laboratory) | |
| View/Download:Presentation | Paper | |
| Abstract: Actionable intelligence requires timely information gathering and dissemination to warfighters. This need can be accomplished through the use of rapidly deployable assets from Space, Air, and Ground. The Office of Force Transformation (OFT) highlighted its need for rapid deployment and employment of new capabilities to improve the operational response to potential threats. As part of its five goals, OFT has stated network centric warfare as a transformational element in the success of DoD defense strategy. Of particular interest and concern is the ability to efficiently and effectively use space systems and provide access to them at the lowest tactical level possible. The primary space system aspects that enable such capabilities include: tactical spacecrafts, the implementation of distributed planning and tasking (e.g. tasking requests to the satellite constellation as opposed to a spacecraft; effecting distributed command and control), intra-satellite constellation communications, and distributed reporting. In parallel, DoD efforts in development of network-centric technologies within the Global Information Grid (GIG) are moving to radically new approaches for command and control of both tactical and strategic assets, based on the notion of service-based architectures that allow users to discover and use new functionality during system operation. The Tactical Spacecraft Commanding Service Architecture (TSCSA) effort proposes to develop a system architecture that is warfighter centric and will explore a fundamentally new way to access, task, and receive information from tactical spacecraft assets based on the notion of a distributed, semi-automated planning and scheduling framework built on current web service standards. The TSCSA will present tactical spacecraft sensing assets as an abstract service to potential warfighter clients. As such, the assets will be “discoverable” through standard web services mechanisms (e.g. Jini, UDDI registry, WSDL). Past research efforts have focused on the development of autonomous control and coordination for spacecraft constellations, with an emphasis on diagnostics, fault protection, and common modular architectures for both flight and ground software. These efforts have not specifically addressed the integration of tactical space sensor assets into the emerging service-based architecture being developed by OSD NII for the next generation warfighting GIG. They have also not addressed the problem of distributed spacecraft tasking (e.g. multiple clients independently requesting remote sensing services from a limited set of assets). A team of APL engineers began an IR&D effort to develop a capability that focused on warfighter needs with the use of service¬based architecture. The architecture is designed as a four-tier system to allow the system to flexibly meet the demands of warfighters coming in an operational theater. This paper will present our work resulted in a demonstration prototype system where warfighters are equipped with the capability to request and monitor assets availability and received timely tactical information through this architecture. | |
| | |
| Paper Number RS5-2007-6004: Training and Tactical ORS Operations (TATOO) | |
| Robert Strunce (Star Technologies Corporation), Barbara Sorense (Star Technologies Corporation), Thomas Mann (Star Technologies Corporation) | |
| View/Download:Presentation | Paper | |
| Abstract: Star Technologies Corporation is developing a “Training and Tactical (Operationally Responsive Space) Operations (TATOO) Classroom/Laboratory under the direction of the Air Force Research Laboratory / Human Effectiveness (AFRL/HE) Division. This paper will discuss the laboratory hardware/software implementation in support of the in-theater warfighter. The goal of the TATOO laboratory is to provide an environment for the development of procedures/protocol for tasking tactical satellites as well as provide an environment for training. ORS systems aim to provide operational space capabilities, flexibility and responsiveness to tactical battlefield commander that do not exist today. ORS communication, navigation and ISR satellites are designed to replace or supplement existing systems in order to enhance the current space force. They intend to rapidly meet near term space needs of the tactical forces. The ORS concept includes new tactical satellites specifically designed to support contingency operations such as increased communication bandwidth, and ISR imagery over the theater for a limited period to support air, ground, and naval force missions. The full potential of ORS is to support in-theater tactical forces to develop satellite tasking, data retrieval and interface capabilities for mission operations from a warfighter centered perspective, and to develop realistic training and simulation that allows development, demonstration, and assessment of ORS tactical CONOPS. The TATOO Objectives are to support in-theater commanders & warfighters by developing, training, and assessing Operationally Responsive Space mission CONOPS for in-theater tasking, scheduling, interface and data retrieval for tactical satellites. TATOO provides a laboratory/classroom environment for the development, test and evaluation of ORS Tactical Mission CONOPS for in-theater ORS operations to: • Emulate major in-theater satellite mission control components including-Tactical Ground Stations, Tactical Mission Tasking Operations, & Warfighter support systems. • Emulate SIPRNET with local area network to provide connectivity. • Simulate tactical satellite operations, dynamics, and data collection with Spacecraft Design Tool. • Emulate the Virtual Mission Operation Center (VMOC) for operational satellite control using Remote Intelligent Monitoring System. • Provide remote access via the internet. The potential TATOO benefits are • Support the ability to rapidly design, fabricate, test and launch a responsive tactical satellite within a six day window. • Provide realistic training and simulation capabilities that will allow development, demonstration, and assessment of ORS tactical CONOPS. • Allow distributed mission teams to interact in day-to-day satellite operational control through VMOC • Support the operational side of ORS and merge with the revolutionary ORS spacecraft development and deployment processes to make the ORS paradigm a reality. • Enable in-theater interactive training exercises that promotes training of in-theater personnel. | |
| | |
| Paper Number RS6-2008-1006: Air Force Satellite Control Network (AFSCN) Support for Operational Responsive Space (ORS) | |
| Len Hodges (Schriever Air Force Base) | |
| View/Download:Presentation | Paper | |
| Abstract: The AFSCN is a common user, satellite control network that supports the Department of Defense (DoD), the Intelligence Community (IC), National Aeronautics and Space Administration (NASA) and National Oceanic and Atmospheric Administration (NOAA) programs. The AFSCN can provide a worldwide network communications infrastructure to ORS programs that should be considered as a primary ground communications architecture for ORS planning and requirements. There is no charge for DoD or IC use of the AFSCN. Currently the AFSCN has eight remote ground facilities (RGFs) located around the world with a total of 15 antennas or remote tracking stations (RTS). Future plans are to expand to 10 RGFs with 19 RTSs. The tracking stations operate in the L-band for uplink and S-band downlink (e.g. Space Ground Link Subsystem [SGLS]). Future plans are to also include S-band for both up and down link communication (e.g. Unified S-Band [USB]). The AFSCN is composed of three segments: the Range Segment (also known as the RTS) which provides the ground to spacecraft interface; the Communication Segment which connects the RTS to the two Operational Control Nodes (OCN); and the Network Management Segment which provides network scheduling and network status. The user must have a command and control (C2), scheduling and communications control interface to the AFSCN. The user must build a RTS configuration database (includes the uplink frequency, command rate, downlink frequency and signal format, etc.). The AFSCN is a common user network where each user’s requirements are satisfied according to their mission priority. The user submits a schedule request to the AFSCN Network Operations Center (NOC) for arbitration. The AFSCN can be used by ORS to provide ground system to space craft communications. This provides satellite Telemetry, Tracking and Commanding for the satellite bus and possibly the payload. NOTE: Although the ground system is many times the last piece of the puzzle in a satellite program, it is a necessity that cannot be placed at the end of the planning and funding cycle. Whether the AFSCN is used or not, the ORS ground system must be planned at the same time as the space craft and tested with the space craft before launch. (i.e. a critical lesson learned) | |
| | |
| Paper Number RS6-2008-3007: A PCI-Based, Multiple-Payload Processing System for the DSX Flight Experiment” | |
| James King (QinetQ North America/PSI), Robert Gillis (QinetQ North America/PSI), Scott Greeley (QinetQ North America/PSI), Lawrence Davis (QinetQ North America/PSI), Lt. Col. Jon Schoenberg (Air Force Research Laboratory), Capt. Mark Scherbarth (Air Force Research Laboratory) | |
| View/Download:Presentation | Paper | |
| Abstract: The need rapidly to accommodate a variety of diverse payloads, each with its own data processing and command/telemetry protocols, is increasingly common in the emerging responsive space environment. On the AFRL Demonstration and Science Experiments (DSX) spacecraft, the Experiment Computer System (ECS) provides communication interfaces, mass data storage, and complex processing for ten different payloads, each from a different organization, some of legacy design and some developmental, while providing a single, simple interface to the host spacecraft. In this paper we discuss the hardware and software design of the ECS with a view to clarifying how a single architecture has supported and isolated the complexity of a variety of different payloads. Of equal importance, we show how an aggressive program of early integration testing, using hardware and software prototypes representing the payloads at various stages of development, has reduced the risk of payload integration, and isolated the host spacecraft from the vicissitudes of payload development. | |
| | |
| Paper Number RS6-2008-5002: Virtual Mission Operations Center Integration: The Next Step in Development and Experimentation | |
| Eric Miller (General Dynamics), Omar Medina (US Naval Research Lab), Lt. Col. Jay Hopkins (614 Air Operations Center), Kim Holloman (Science Applications International Corporation) | |
| View/Download:Presentation | Paper | |
| Abstract: Collaborative Virtual Mission Operations Center (VMOC) demonstrations over the last three years have supported the standardization of spacecraft to ground interfaces needed to reduce costs, maximize space effects to the user, and allow the generation of new tactics, techniques and procedures that lead to responsive space employment. The three main thrusts were the US Air Force platform apportionment and command and control, US Army theater access to payloads, and the US Navy’s user collaboration and FORCEnet principles. While each thrust was focused on a specific aspect of ORS, in some cases, the user community was confused and thought of the systems as competitors rather than complementary which was the intent. To eliminate the confusion and accelerate the effort, the next step has begun with the integration of the VMOC architectures sponsored by the Office of Naval Research and the Office of the Secretary of Defense to explore the way ahead related to Operationally Responsive Space, with the Naval Research Laboratory designated as the program manager. This paper is jointly written and details the integration of the Tactical, Mission, and Apportionment VMOCs with an emphasis on the end to end, multi mission, 14AF Joint Space Operations Center demonstration set for April 2008. | |
| | |
| Paper Number RS7-2009-4002: A Roadmap for Responsive Software Systems | |
| Ed Birrane (Johns Hopkins University Applied Physics Laboratory), Brian Bauer (Johns Hopkins University Applied Physics Laboratory) | |
| View/Download:Presentation | Paper | |
| Abstract: Responsive systems provide dynamic operational benefits within short timeframes and tight cost constraints. Fundamental to this concept is engineered adaptability which is atypical of many heritage systems. This is achieved by reducing the coupling between components in a system – a modularizing approach to system decomposition that creates discrete functional units that can be recombined during construction, deployment, or on orbit. Practically, this capability requires an infrastructure investment to ensure that multiple domain vendors build interoperable and re-usable systems. In the hardware domain this infrastructure work is underway, but similar infrastructure construction must be commenced for software. Flight software is a critical component of any re-usable system design as hardware components are difficult to alter once integrated and nearly impossible to alter post-launch. Software is the mechanism through which spaceborne capabilities are extended. While there are certain guidelines for success – open-architectures, open standards, modularity, and cross-vendor interoperability – there has been little work in understanding the specific enablers necessary to actually construct reusable software. This level of modularity requires a reasoned, vendor-neutral approach to interoperable, re-usable software systems. Lacking this, subsequent integration issues risk failure in meeting response times despite the presence of modular hardware. Our research has identified five critical enablers for flight software systems: software certification procedures, low-level architectures and frameworks, systems-level architectures and patterns, integration environments, and an evolving software library. It is notable that there are dependencies between these enablers: building a software re-use library without common test/certification procedures will result in code that is far less re-usable across missions. This paper further defines these enablers, the milestones necessary to mature each one, a brief review of the state of the industry relevant to these milestones, and recommended priorities in the maturation of these technologies. The goal of this work is to publish a framework for consideration by performers in the responsive space community to more rapidly converge on software-adaptable capabilities. | |
| | |
| Paper Number RS7-2009-6001: Virtual Mission Operations Center and ORS Ground System Enterprise | |
| Eric Miller (General Dynamics Advanced Information Systems), Omar Medina (US Naval Research Lab), Mike Hurley (US Naval Research Lab), James Barlow (Operationally Responsive Space Office), Ed Quinonez (Booz Allen Hamilton), Deborah James (ISIS Engineering LLC ) | |
| View/Download:Presentation | Paper | |
| Abstract: Virtual Mission Operations Center (VMOC) development over the last four years has allowed the community to explore new concepts of operations supporting the standardization of spacecraft to ground interfaces needed to reduce costs, maximize space effects to the user, and allow the generation of new tactics, techniques and procedures that lead to responsive space employment. The three main thrusts were the US Air Force platform apportionment and command and control, US Army theater access to payloads, and the US Navy’s user collaboration and FORCEnet principles with each thrust focused on a specific aspect of ORS. The successful efforts and demonstrations of 2008 led the ORS Office to select the VMOC as the primary ORS Payload Tasking and Asset Visibility capability for the ORS 2015 Ground System Enterprise. This paper is jointly written and details the next steps being taken by the VMOC team to support TacSat-4, TacSat-1a, and ORS Sat-1. | |
| | |
| Paper Number RS7-2009-6002: In a Tactical Minute: Lessons Learned From the First-Ever In-Theater Command and Data Dissemination | |
| Capt. Lisa Baghal (Air Force Institute of Technology) | |
| View/Download:Presentation | Paper | |
| Abstract: Responsive Space in the military world means responsive spacecraft development, launch, and operations. A tactical user, or warfighter, must be able to utilize the asset in near real-time in support of his urgent mission. This paper will focus on a means for the warfighter to utilize a space ISR asset directly from theater. Consider the following scenario: Unit X in-theater is not receiving the ISR data they need in a timely manner. Their U-2s and Global Hawks do not have access to the airspace, but they need to know what is over the hill. The wait for up-to-date ISR products could be days long, and they don’t have that kind of time. Luckily, their Common Data Link (CDL), like the Mobile Interoperable Surface Terminal (MIST) used to communicate with the U-2 and Global Hawk, is also configured for communications with a Tactical Satellite (TacSat) that will be overhead in a matter of minutes. With the flip of a switch, Unit X now has a satellite command and control station at their fingertips. As the satellite comes over the horizon, the MIST will lock on to the satellite and provide direct commanding access to the warfighter. Now he can task the satellite for ISR collection overhead, but only has a few minutes to do it. But with an interface as easy to use as Orbitz.com, tasking the satellite can be done very quickly. Now that the satellite has a tasking, all he has to do is sit back and wait – but not for long! In a matter of minutes, a high speed downlink begins and the image can be displayed on the computer right in front of him. As you can see from the description of an in-theater contact, a tactical minute goes by in a flash. Because of the quick-paced nature of a tactical contact, processes and interfaces must be streamlined and easy to use. By examining lessons learned from the first-ever in-theater tasking/data collection using TacSat-2 and MIST, it can be shown that the scenario described above is feasible and responsive to the tactical user. | |
| | |
| Paper Number RS7-2009-6004: ORS In The Cloud | |
| Barbara Sorensen (HPW/RHAC), Craig Eddy (Star Technologies Corporation ), Thomas Mann (Star Technologies Corporation ) | |
| View/Download:Presentation | Paper | |
| Abstract: Star Technologies Corporation is developing Satellite Tasking Manager (STM) tools for Operationally Responsive Space, ORS, under the direction of the Air Force Research Laboratory / Human Effectiveness (HPW/RHAC) Division. ORS systems aim to provide operational space capabilities, flexibility and responsiveness to tactical battlefield commanders as well as the warfighter. The ORS concept should include the ability for the Warfighter to task satellites with product requests, receive those requests, and provide tools for analyzing the requested data. However, depending on the nature of the product a diverse set of analysis may be required to create meaningful information from the product. This requires a collaboration framework so different disciplines can interface on a single problem. Star Technologies has been studying approaches to creating an ORS Service that will provide a central hub for receiving requests, identifying the appropriate asset to service those requests, routing the received product to the appropriate analysts, and finally returning the analyzed information product to the requester. This paper will discuss an approach to the ORS Service that utilizes cloud computing and cloud data storage. Cloud data storage allows for data to be available across platforms, machines, and networks while preserving all necessary security. Cloud computing allows for the requests and analysis to be serviced by first-available resources as opposed to sitting unattended. | |
| |