|
|
Home RS2011 Conference (Details) Call for Papers Conference Program Registration Sponsor/Exhibit Prior Conferences ORS Reference Search Contact Info |
|
Past Conference Papers:
Tacsats
| 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-4004: Responsive Spacecraft Bus Implementation for Unique HEO Missions Based on Standard Interfaces | |
| P.A. Stadter (Johns Hopkins University Applied Physics Laboratory), C.S. Schein (Johns Hopkins University Applied Physics Laboratory), M.T. Marley (Johns Hopkins University Applied Physics Laboratory), C.T. Apland (Johns Hopkins University Applied Physics Laboratory), R.E. Lee (Johns Hopkins University Applied Physics Laboratory), B.L. Kantsiper (Johns Hopkins University Applied Physics Laboratory), B.D. Williams (Johns Hopkins University of Applied Physics Laboratory), E.D. Schaefer (Johns Hopkins University of Applied Physics Laboratory), S.R. Vernon (Johns Hopkins University of Applied Physics Laboratory), P.D. Swartz (Johns Hopkins University of Applied Physics Laboratory), E.J. Finnegan (Johns Hopkins University of Applied Physics Laboratory), J. Chris Garner (Naval Research Laboratory) | |
| View/Download:Presentation | Paper | |
| Abstract: This paper will provide details of the implementation of an Operational Responsive Space spacecraft bus to be used by the TacSat-4 CommX mission in a highly elliptical orbit (HEO). Through this discussion, two primary themes of the RS5 conference will be addressed: applications that lend themselves to solution by small spacecraft in HEO orbits and implementation of a critical element of the overall mission within the context of responsive capabilities. Specifically addressed will be the challenge of developing a spacecraft bus as a platform designed to a set of defined interface standards, while faced with the unique requirements of a particular payload. This will include a discussion of the driving requirements for the bus to provide operations in the HEO orbital environment and the user applications that can take advantage of such a platform given candidate payloads. The paper will provide details on design and implementation decisions that were made to accommodate standards, and places where proposed standards were not able to be addressed for the particular implementation. The technical details included will provide insights into the bus implementation well after Critical Design Review, but prior to space vehicle Integration and Test, thus system designs will be mature and near completion. | |
| | |
| Paper Number RS5-2007-5002: Minotar I Demonstration of Responsive Launch for the TacSat-2 Mission | |
| Scott Schoneman (Orbital Sciences Corporation), Lou Amorosi (Orbital Sciences Corporation), Mike Laidley (Orbital Sciences Corporation), Kevin Wilder (Orbital Sciences Corporation), Bob Huntley (Orbital Sciences Corporation) | |
| View/Download:Presentation | Paper | |
| Abstract: On 16 December 2006, a Minotaur I space launch vehicle (SLV) successfully placed the TacSat-2 and GeneSat-1 spacecraft into orbit following its launch from the Mid-Atlantic Regional Spaceport (MARS) at Wallops Island, VA. The mission was a ground breaking demonstration of ORS launch capabilities. Starting with a contract award and kick-off in late May 2006, the vehicle was ready to launch in less than seven months. Achieving this responsive capability required a dramatic compression of the normal mission integration, range interface, and field processing schedules. The final field processing schedule from the start of spacecraft mating to readiness for launch was independently monitored and timed to show the capability to launch with a call up goal of one week. The cumulative measured time for critical operations was less than 6 days of processing, fully accomplishing the ORS goal for rapid spacecraft launch. The lessons learned from the efforts to dramatically reduce the schedules will be applied to further reduce the response time of the full family of Minotaur vehicles in support of future ORS missions. In addition to being readied for launch in record time, the TacSat-2 mission also demonstrated a number of firsts. Most significantly, it was also the first launch from the MARS launch facility, which is at NASA’s Wallops Flight Facility (WFF) near Chincoteague, VA. This was the first successful ground-based space launch from Wallops Island in 21 years. The TacSat-2 vehicle was the first Minotaur I to fly a larger, 61 inch diameter fairing and was also the first time a RocketCam on board video camera was flown on a Minotaur vehicle. Moreover, the integration of the GeneSat-1 secondary pico¬spacecraft was accomplished in a compressed schedule less than four months. This paper and presentation will cover how the TacSat-2 launch was accomplished in an unprecedented responsive timeline and how this demonstration is directly applicable to support of ORS mission by Minotaur vehicles in the future, including the larger Minotaur IV and V launch vehicles. | |
| | |
| Paper Number RS5-2007-7006: Dallas EEProm Equipment Profile for Rapid Integration and System Modeling | |
| Forrest Rogers-Marcovitz (Washington University in Saint Louis), Phelps Williams (Santa Clara University) | |
| View/Download:Presentation | Paper | |
| Abstract: One definition of Responsive Space is the ability for mission-specific payloads and support systems to be rapidly integrated within a short period. However, as components are added to the spacecraft, the complex interactions between subsystems must be noted and, if possible, modeled; this process is extremely time consuming and, when done poorly (or not at all), is a major contributor to spacecraft failure. A new paradigm is needed for Rapid Integration and System Modeling. At the 2006 Conference on Small Satellites in Logan Utah, Washington University and Santa Clara University demonstrated Rapid Integration and Testing by functionally combining their respective satellites, Akoya and Onyx; both vehicles were connected via a common power and data wiring harness, allowing one spacecraft to operate any device on either vehicle. Despite possessing minimal prior knowledge about the other school’s subsystems, functional integration was achieved in less than thirty minutes. Each satellite uses a distributed computing architecture with a standardized interface and communication protocol. This architecture allows each subsystem to be developed separately and rapidly integrated into the spacecraft. The success of this experience led to an improved design for subsystem-level embedded operational intelligence. The Dallas EEProm Equipment Profile (DEEP) Architecture extends this standardized bus to include improved support for rapid integration and system modeling. DEEP is a protocol standard using the Maxim/Dallas 1-Wire bus allowing for low level control and monitoring of the spacecraft using commercially-of-the-self devices including memory and sensor devices. DEEP specifies a standard with which subsystem functionality is encoded within the subsystem itself allowing for the creation of a satellite-wide model in parallel with physical integration of the spacecraft. This allows a stockpile of flight DEEP enabled subsystems, ready to be rapidly composed into a functional spacecraft. Each subsystem includes a subsystem model, with parameters such as thermal and power characteristics, allowing an anomaly management system to identify off-nominal conditions through model-based reasoning. DEEP is currently being developed at Santa Clara University and Washington University in Saint Louis as part of the University Nanosatellite competition operated by the Air Force Research Laboratory. This paper describes the current success of both universities with rapid integration, current development of the DEEP architecture, and future advances regarding responsive space. | |
| | |
| Paper Number RS5-2007-A001: TacSat 4 Overview | |
| Tacsat Status Panel | |
| View/Download:Presentation | |
| | |
| Paper Number RS6-2008-4003: Responsive Spacecraft Bus Implementation for HEO Missions Designed to Bridge Prototype and Operational Systems | |
| P.A. Stadter (Johns Hopkins University Applied Physics Laboratory), M.T. Marley (Johns Hopkins University Applied Physics Laboratory), C.T. Apland (Johns Hopkins University Applied Physics Laboratory), C.T. Apland (Johns Hopkins University Applied Physics Laboratory), R.E. Lee (Johns Hopkins University Applied Physics Laboratory), B.D. Williams (Johns Hopkins University Applied Physics Laboratory), E.D. Schaefer (Johns Hopkins University Applied Physics Laboratory), P.D. Schwartz (Johns Hopkins University Applied Physics Laboratory), B. Kantsiper (Johns Hopkins University Applied Physics Laboratory), E. J. Finnegan (Johns Hopkins University Applied Physics Laboratory), W. Raynor (Naval Research Laboratory), G.S. Sandhoo (Naval Research Laboratory) | |
| View/Download:Presentation | Paper | |
| Abstract: This paper will provide details of the implementation, integration, and test of an Operationally Responsive Space spacecraft bus to be used by the TacSat-4 CommX mission in a highly elliptical orbit (HEO). It will provide details of near-term results of the development, integration and test, and the implementation of standard interfaces to facilitate a bridge between prototype and operational systems. The paper details the means by which the technology and system engineering inform further use for future operational systems, including specifically the work of the Integrated System Engineering Team of industry, laboratory, and government participants. Details of the qualification of the spacecraft up through completion of integration and test will be provided, as will lessons observed that specifically translate into information for future operational satellite builds. This will include a discussion of the driving requirements for the bus to provide operations in the HEO orbital environment and the user applications that can take advantage of such a platform in a timely manner given candidate payloads. Aspects of complementary analyses of how similar operationally responsive space systems can military utility will also be presented. | |
| | |
| Paper Number RS7-2009-1007: Sea-Launched TacSats for Responsive Space (STaRS) | |
| Lt. Col. Robert Carneal (US Air Force SMC/XRDP), RayMing Chang (US Air Force SMC/CDE) | |
| View/Download:Presentation | Paper | |
| Abstract: The Responsive Space community has focused on Responsive Launch as an area of improvement that would help space become more responsive. Unfortunately, developing a Responsive Launch capability is fraught with difficulties. American launch facilities (i.e., Eastern Range, Western Range, Kwajalein, etc.) have numerous logistical and physical limitations that restrict U.S ability to quickly launch a satellite, including: restricted launch fans, prior easements, launch plumes, and safety concerns. This paper proposes a possible solution that avoids many of the difficulties associated with launch systems used today: a Sea-launched TacSats for Responsive Space (STaRS) system. A Sea-based TacSat launch capability would solve many of the problems associated with limited launch pads at fixed sites, including issues with “possible” launch pad availability due to competing program priorities as opposed to having a definite launch date. Of course, STaRS systems will need to deal with issues that land-based systems do not, such as ocean environments, transportation logistics, and security concerns. Sea-launched vehicles are a proven technology. The prime example of a highly effective sea-based launch system is United Launch Alliance’s Sea-Launch. Another example is the ICBM architecture which already exists with Submarine Launched Ballistic Missiles (SLBMs) aboard ballistic missile submarines (SSBNs). Russia has been launching satellites from submarines since at least 1994. For example, in 2006, the Russian Federation successfully launched an 80 kg Compass-2 satellite from a K-84 "Ekaterinburg” submarine. The least expensive option for a sea-borne STaRS platform would be to convert a used tanker or cargo ship. Command of a STaRS ship would likely be split between the Navy and the Air Force. Cost savings could be realized by utilizing a primarily civilian crew on the STaRS ship with joint Navy and Air Force command, similar to how the Military Sealift Command's Prepositioning Program is crewed. A more expensive option would be to convert and dedicate a SSBN submarine for STaRS missions. STaRS ships/subs could be pre-positioned near the equator or incorporated into a Navy fleet. For larger payloads, the U.S. can develop systems similar to Sea Launch. A STaRS platform will likely be able to carry at least several launch vehicles on standby, if not several dozen. A STaRS platform will therefore likely have the capacity to quickly launch a constellation of TacSats which would provide more flexibility and responsiveness. The ability to quickly replenish constellations would help deter the use of ASATs by adversaries. In addition, STaRS could launch a Payload Assist Module (PAM) in order to insert a payload beyond LEO. A STaRS system has the potential to avoid many of the problems associated with land-based launch and provide a real responsive launch capability. | |
| | |
| Paper Number RS7-2009-2003: A Concept of Operations for Satellite Carriers (“SatCarriers”) | |
| RayMing Chang (United States Air Force — SMC/CDE) | |
| View/Download:Presentation | Paper | |
| Abstract: Responsive Space is too slow. Today, we cannot build a satellite overnight and we cannot launch a satellite at a moment’s notice. We can avoid many of the latencies associated with satellite manufacture and launch with the Satellite Carrier (“SatCarrier”). The basic function of the SatCarrier system will be to provide on-orbit storage of tactical satellites (“TacSats”). SatCarriers will loiter in Earth orbits carrying squadrons of TacSats. The TacSats resident on these SatCarriers will be ready to deploy on demand. SatCarrier capabilities will fall between Tier 1 and Tier 2 as defined by the Operationally Responsive Space Plan that was submitted by the Department of Defense to Congress on 20 Apr 2007. In fact, we could characterize SatCarriers as Tier-1.1 assets that are on-orbit yet held in ready reserve. This Concept of Operations (“CONOPS”) discusses the SatCarrier mission, system drivers, and system constraints. It proposes an implementation concept based upon the EELV Secondary Payload Adapter (ESPA) ring with ESPA Ring configurations ranging from 4 to 18 satellites. It also discusses other possible SatCarrier implementations. This CONOPS then discusses mission planning considerations and tradeoffs of particular orbits. In particular, this CONOPS discusses important delta-V considerations for SatCarrier mission planning. A SatCarrier will carry a squadron of identical TacSats or a mixed squadron of TacSats with different payloads (a squadron would contain somewhere between 4-20 satellites). Mission planners would have the flexibility to decide whether users in a SatCarrier’s Area of Responsibility (AOR) will require payloads that facilitate communications, battle-space characterization, space situational awareness, or a mix. TacSats stored on SatCarriers will either be dormant or be maintained on standby power. In either case, the SatCarrier will be able to power up resident TacSats as needed. TacSats that are stored on SatCarriers will be thoroughly tested prior to launch and should be operational when turned on, but planners will likely plan for capability redundancy in the squadron to mitigate infant mortality risk. SatCarrier designers could reduce infant mortality through shielding and “exercising” stored TacSats. SatCarriers will likely be developed in blocks, much like GPS. When a block of SatCarriers reach half-life, the TacSats it carries could be deployed in order to get some use out of the satellites. The services of satellites deployed at half-life could be used as overflow for military/government missions or resold to civil space. A new improved block would then be deployed to replace the previous block. A SatCarrier could also serve as a ready supply of on-orbit spares that retain more of their service life because the stored spares would rely on the SatCarrier for stationkeeping and power. SatCarriers will give the United States truly responsive space capabilities. The SatCarrier concept is realizable in the near-term. We should begin investing in and developing the SatCarrier concept now. | |
| |