|
|
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:
6-Day Spacecraft
| Paper Number RS1-2003-4003: Implementing Standard Mircosatellites for Responsive Space | |
| Jeffrey L. Janicik (SpaceDev) | |
| View/Download:Presentation | Paper | |
| Abstract: Today satellites tend to be large, expensive, power-hungry, slow to assemble test and integrate, and are generally unique to each payload. In addition they often take as much as 90 days to “commission” on-orbit. This traditional way of doing things can slow the testing, demonstration and fielding of newer, smaller, higher performance payloads. The approach, articulated here, is to use the “microcomputer” way of thinking and apply it to the space industry, which has tended to be bogged down for decades in the bigger is better “mainframe” way of thinking. Because of these problems and variables, the goal is to develop high performance modular microsatellites and a corresponding microsat operating system quickly and efficiently, not custom for each mission or payload. This can be simplified if functionality becomes a goal, where capabilities like radiation hardness, shock, vibrations, etc., are simply built into the microsatellite, with the system able to perform to a certain acceptable level, relieving the payload developer from such considerations. An appropriately modular system can utilize current and future subsystem and software technology, while naturally maintaining stateof- the-art performance. In turn this can dramatically reduce the size, mass and power requirements of subsystems and will result in on-demand launch and responsive, quick onorbit commissioning. Consequently, the most performance can be put into the smallest, lightest package for payloads, and ensure the shortest time to productivity on orbit. | |
| | |
| 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 RS2-2004-3003: A Modular Design for Rapid-Response Telecons and Navigation Missions | |
| Phillip Davies (SSTL), Doug Liddle (SSTL), John Paffett (SSTL), Sir Martin Sweeting (SSTL), Alex da Silva Curiel (SSTL), Stuart Eves (SSTL) | |
| View/Download:Presentation | Paper | |
| Abstract: In order to achieve an ‘economy of scale’ with respect to payload capacity the major trend in telecommunications satellites is for larger and larger platforms. With these large platforms the level of integration between platform and payload is increasing leading to longer delivery schedules. The typical lifecycle for procurement of these large telecommunications satellites is now 3-6 years depending on the level of non-recurring engineering needed. Surrey Satellite Technology Ltd (SSTL) has designed a low-cost platform aimed at telecommunications and navigation applications. SSTL’s Geostationary Minisatellite Platform (GMP) is a new entrant addressing the lower end of the market with payloads up to 250kg requiring less than 1.5 kW power. The development of GMP was supported by the British National Space Centre through the MOSAIC Small Satellite Initiative. The main design goals for GMP are low-cost for the complete mission including launch and operations and a platform allowing flexible payload accommodation. GMP is specifically designed to allow rapid development and deployment with schedules typically between 1 and 2 years from contract signature to flight readiness. GMP achieves these aims by a modular design where the level of integration between the platform and payload is low. The modular design decomposes the satellite into three major components - the propulsion bay, the avionics bay and the payload module. Both the propulsion and avionics bays are reusable, largely unchanged, independent of the payload configuration. Such a design means that SSTL or a 3rd party manufacturer can manufacture the payload in parallel to the platform with integration taking place quite late in the schedule. In July 2003 SSTL signed a contract for ESA’s first Galileo navigation satellite known as GSTBV2/A. The satellite is based on GMP and ESA plan to launch it into a MEO orbit late in 2005. The second flight of GMP is likely to be in 2006 carrying a geostationary payload consisting of six Ku band transparent transponders. Once the platform is flight proven, SSTL will be able to offer it to commercial and institutional operators when there is an urgent need for capacity for example to introduce new services, for gap fillers, for frequency filing missions and for technology demonstration missions. | |
| | |
| Paper Number RS2-2004-5003: TacSat-1 and a Path to Tactical Space | |
| Jay Raymond (Office of Force Transformation), Greg Glaros (Office of Force Transformation), Joe Hauser (NRL), Mike Hurley (NRL) | |
| View/Download:Presentation | Paper | |
| Abstract: In May of 2003, the Office of the Secretary of Defense’s Office of Force Transformation undertook an initiative to perform Operationally Responsive Space experimentation. One year later the first experiment, TacSat-1, is nearing launch readiness and a second experiment, TacSat-2, is well into the design phase. The Naval Research Lab is the program manager responsible for the implementation of the TacSat-1 experiment. This paper discusses the TacSat-1 experiment, rationale, and status. This paper further discusses a path toward realizing an operational tactical space system. For completeness, much of the 2003 paper’s discussion on the technical, operational, and architectural issues for a tactical space capability is included. | |
| | |
| Paper Number RS2-2004-6002: Responsive Space Through Adaptive Avionics | |
| Denise Lanza (Scientific Applications International Corp.), Jim Lyke (AFRL), Paul Zetocha (AFRL), Don Fronterhouse (Scientific Simulation), Dave Melanson (Mission Research Corp.) | |
| View/Download:Presentation | Paper | |
| Abstract: This paper will review the need for an improved strategy in avionics to address responsive space objectives. General strategies will be described for achieving responsive space through reconfigurable electronics and computer-aided design. The Adaptive Avionics Experiment (AAE) is introduced as a specific embodiment of these principles, and its key elements are described. Status and future plans are discussed. | |
| | |
| Paper Number RS3-2005-3003: AeroAstro's SMARTBus™: A Low-Cost Modular Approach Enabling Responsive Space Missions | |
| Scott A McDermott (AeroAstro), Luis G. Jordan (AeroAstro) | |
| View/Download:Presentation | Paper | |
| Abstract: The long lead and cycle times currently associated with development and launch of satellite systems has established a prohibitive environment for responsive deployment of technology and tactical capability to orbit. To address these critical deficiencies in lead time and ease of space access, AeroAstro has developed and built a modular spacecraft architecture known as SMARTBus™. SMARTBus defines systemic, mechanical, electrical, and logical (software) interfaces that allow spacecraft modules to interact with each other based on their functions rather than their implementation. One attitude determination module may be implemented based on sun sensors, another based on a star tracker, another based on a GPS; each offers different attitude determination capabilities; but from an interface standpoint, they behave the same. In this way, a mission requiring a given set of capabilities may be built up from pre-existing and pre-qualified modules offering those capabilities, and all of the modules can interact with each other because that interaction is based on providing functionality rather than controlling a specific implementation. SMARTBus challenges the traditional spacecraft systems approach by incorporating a modular bus design with “smart” software architectures. Intrinsic to the design is the “Plug-and-Sense” capability that enables the SMARTBus module stack to not only detect the presence and orientation of integrated subsystem modules, but also ascertain their function and key performance parameters. Additionally, the system utilizes a heuristic, self-interrogation approach to provide a robust means of performing configuration and diagnostics activities. This capability transcends nominal housekeeping routines to include an enhanced degree of system autonomy for both initial station acquisition and checkout, as well as mission-specific operations. This flexible functionality will enable scalable multi-mission compatibility, long shelf-life, rapid call-up and field integration for launch, intelligent built-in test capability for rapid initialization on-orbit, and variable batch manufacturability. | |
| | |
| Paper Number RS3-2005-4005: Standardization to Optimize Integration and Testing | |
| Norman C. Anderson (USAF), Guy G. Robinson (Jackson & Tull), David R. Newman (MicroSat Systems) | |
| View/Download:Presentation | Paper | |
| Abstract: The Air Force Research Laboratory is involved in the evolution of space systems to a model that is more responsive to operational needs. A key tenant of the concepts for future responsive space support includes the ability to rapidly integrate missionspecific payloads into flexible spacecraft busses on a very short (a few days) timeline. Traditional spacecraft integration and test (I&T) processes require several months for even the most simplistic spacecraft. An analysis of a number of spacecraft I&T processes reveals that a large percentage of the I&T schedule is expended in verification and validation of the interfaces between subsystems. Further, there is much time and money spent in the constant reconfiguration of the test support equipment to accommodate the multitude of unique interfaces used on a typical spacecraft. While these customized interfaces may allow for the development of a spacecraft optimized for minimum mass or peak payload performance, these metrics are of secondary interest in a system intended to be rapidly integrated and deployed in response to user needs. There are design approaches for subsystem interfaces used in many other industries that have the need to minimize the time required for integration and test. The automotive industry and the developers of personal computer systems are two such environments. This paper will discuss the results of analyzing the integration and test flow of typical programs, identify candidate interfaces and the projected savings to be gained by adopting them from other industries, and propose a process flow for a responsive spacecraft based on these new interfaces. | |
| | |
| Paper Number RS3-2005-4007: Responsive Space Center of Excellence | |
| John E. Hicks (National Nuclear Security Administration) | |
| View/Download:Presentation | Paper | |
| Abstract: The objective of a Responsive Space Center of Excellence is to provide a conduit to rapidly design, build, test and field an operationally relevant microsatellite system; reduce timeliness for development, test, launch, checkout; and provide a responsive capability to the Joint Force Commander within 7-days. The National Nuclear Security Administration (NNSA) is well postured to develop and manage a Responsive Space Center of Excellence to deliver low cost satellite components and systems for Responsive Space through the application of lean manufacturing, Six Sigma tools and other business management process tools. The objective of this paper is to illustrate that the above mentioned business processes are a must for the success of Responsive Space to provide the Joint Force Commander microsatellite support in 7-days. | |
| | |
| Paper Number RS4-2006-6001: Issues and Implications of the Thermal Control System on the "Six Day Spacecraft" | |
| Andrew D. Williams (AFRL), Scott E. Palo (University of Colorado) | |
| View/Download:Presentation | Paper | |
| Abstract: The traditional approach to satellite design is a customized and highly optimized satellite bus. The primary design driver is to minimize mass but often at the expense of time and money. To meet the goals of Operationally Responsive Space (ORS), the satellite must be adaptable to different missions, changing threats, and emerging technologies. One of the subsystems that will be challenging for the development of robust and modular architectures is the Thermal Control Subsystem (TCS). To design the TCS, virtually every aspect of the mission, the satellite, and the components must be known. The overall goal of the engineer is to reduce the mass of the system by trading cost and engineering time. As a result, every design is unique and requires extensive design, modeling, analysis, and test programs. One philosophical approach to achieve the goals of responsive space in the near term is to separate the design and engineering of the payload from the bus. The bus would have a standard design providing a specific set of baseline capabilities and would have limited upgradeability. The disadvantage with most standardized bus development programs is that the bus eventually becomes obsolete and must be completely redesigned as new technologies are developed. One of the goals of the ORS program is the development of technologies that provide robust and flexible bus designs. The Space Avionics Plug-and-Play (SPA) system in development by Air Force Research Laboratory, Space Vehicles Directorate addresses the software and electrical interfaces, but other efforts are needed to address the mechanical and thermal interfaces. For responsive space, the ideal TCS would be modular and robust to accommodate the wide range of orbits, components, and payloads with minimal survival heater power. In addition, the design and assembly time must be dramatically decreased. The ultimate goal would be a TCS with an inherent plug-and-play capability. One hindrance is that the missions, payloads, and requirements for ORS are still somewhat nebulous. As a result, bus architectures and specific components have not been identified, which makes it difficult to derive even initial thermal system requirements. To provide a baseline for the TCS design and to help bound the problem for the development of thermal plug-and-play systems, the range of external and internal heat loads for small satellites are evaluated. From this analysis, the worst hot and cold cases are identified. Using these two cases, various design parameters are evaluated, and the feasibility of a one-size-fits-all approach is assessed. Finally, critical design parameters are identified and recommended figures of merit are established. | |
| | |
| Paper Number RS4-2006-6002: Java-based Plug-n-Play (Flight) Control Systems for Responsive Space | |
| Constantine Orogo (Lockheed Martin Advanced Technology Center), Michael Enoch (Lockheed Martin Advanced Technology Center), Donald Flaggs (Lockheed Martin Advanced Technology Center) | |
| View/Download:Presentation | Paper | |
| Abstract: A major challenge to achieving a usable and useful “6-day spacecraft” for Operationally Responsive Space is the ability to rapidly compose the system to perform both the needed mission- and spacecraft-oriented functionality using the available "Plug-N-Play" (PnP) spacecraft components. Physical assembly of the PnP spacecraft components is a necessary, but insufficient condition for achieving a fully realized operational system. The assembled system needs to provide the functional capabilities to support the intended mission and also needs to provide the functional capabilities to ensure the operational health and safety of the resulting spacecraft. A preliminary service-oriented spacecraft architectural model to provide a reusable infrastructure is under development as part of the AFRL Responsive Space Testbed effort. The Lockheed Martin ATC is pursuing the development of a Java-based distributed architecture environment that supports this service-oriented, reference spacecraft architectural model. This work draws on the research experience at the LM ATC since the mid-1990s directed towards the problem of performing multi-fidelity, “composable” simulations, with the ultimate objective being the ability to simulate the entire life cycle of a space system. A key component of this approach involves a simulation architecture that is based on spacecraft services, much like the service-oriented models now widely used in the consumer marketplace. It is but an evolutionary step to extend this approach from simulation to operations. To seamlessly span the entire range from simulation to operations, a single vertically integrated software architecture was needed. The Java-based distributed architecture provided such an environment with its evolution from desktop, to enterprise, to mobile devices, and now to real time systems. The Java environment addresses the complexity needed for operational simulations and ultimate deployment for integrated spacecraft flight and payload control systems. The Real Time Specification for Java (RTSJ) supports hard real time, soft real time and non-real time processes all interoperating within the same virtual machine. Initial prototyping is being done using IBM’s Real Time Java (RTJ) implementation of the RTSJ. Along with the development of the Java platform came the development of a multitude of supporting APIs, and one in particular, the JINI protocol, which supports the operation of dynamically changing networks of distributed services (and devices). Using JINI, running as a non-real time process within IBM’s RTJ, provides the rich set of Plug-N-Play capabilities needed to demonstrate both automatic configuration, as would be needed for I&T, as well as for operational fault tolerance and reconfigurability needed for on-orbit operations. | |
| | |
| Paper Number RS6-2008-2005: Rapid Assembly of Spacecraft Structures for Operationally Responsive Space | |
| Roopnarine (Honeybee Robotics Spacecraft Mechanisms Corporation), Shazad Sadick (Honeybee Robotics Spacecraft Mechanisms Corporation), Irene Yachbes (Honeybee Robotics Spacecraft Mechanisms Corporation), Brandon Arritt (Air Force Research Lab/Space Vehicles Directorate) | |
| View/Download:Presentation | Paper | |
| Abstract: A goal of the Operationally Responsive Space thrust is to enable turn-around of a tactical satellite within six days, from mission call-up to on-orbit operation. The ability to produce such a spacecraft would be a vast departure from the norm of large, complex, costly custom spacecraft that require a period of years to deploy. While progress has been made in developing shorter timescale, more modular small satellites, every aspect of the spacecraft development process needs to be reassessed in order to achieve the goals of a truly responsive tactical space program to rapidly meet the tactical needs of the warfighter. Assembly, integration and test typically account for 6 months to 2 years of the spacecraft production cycle. This process could be drastically reduced by stocking component-ready modular panels for assembly. Even with the pieces of a spacecraft bus and payload prepared for integration, the assembly of the structure itself needs to be sped from the typical process of securing panels with dozens of mixed-size fasteners and the associated verification, tooling, and documentation. Likewise, assembly of the structure also must take into consideration the need to pass electrical and thermal connections across panels of the bus. A rapid method for providing a stiff mechanical attachment across panels of a spacecraft bus while simultaneously providing electrical and thermal continuity would help to further realize the goals of ORS. It will also be crucial to demonstrate quick disassembly of bus panels in order to swap out faulty components, accommodate upgrades or support last-minute component changes to satisfy changing mission needs. In collaboration with the Air Force Research Laboratory/Space Vehicles Directorate, Honeybee Robotics Spacecraft Mechanisms Corporation has developed a fastening strategy for enabling rapid assembly of a spacecraft bus structure using our patented Quick Insertion Nut (QIN) technology. With this approach, a standard bolt can be rapidly inserted into the QIN and then about one turn is required to preload the connection, without significant support equipment or operator skill. These QINs are embedded in manifolds which reside at each edge inside the spacecraft bus (the manifold includes panel-to-panel electrical interconnects) that together comprise a skeleton for the spacecraft panels. When the panels are assembled to the manifolds, a robust structural, electrical and thermal connection for the bus is achieved. The QIN resembles a standard bolt joint typically used in aerospace applications and therefore benefits from using a similar analysis. Our approach is conducive to a quick, reliable electrical connection and passive thermal conduction between panels. While the concept is simple, when extrapolated across the multiple fasteners in a typical spacecraft bus (the time for threading of each bolt alone is eight to ten times faster), this results in a revolutionary decrease in the amount of time required for spacecraft assembly. This approach therefore represents a paradigm shift in spacecraft development, helping to enable ORS. View the video of our feasibility demonstration using a subscale prototype at: http://www.honeybeerobotics.com/roop/Assembly4.mov - a representative “corner” of three satellite panels assembled using the QIN fasteners, manifold and electrical connection. | |
| | |
| Paper Number RS6-2008-6004: Programmable Satellite Transceiver (PST) for Responsive Space | |
| Jason Phillips (Real Time Logic, Inc.), Bill Asiano (Real Time Logic, Inc.) | |
| View/Download:Presentation | Paper | |
| Abstract: As the demand increases for more responsive lower costs space operations, the leadtime for fielding space assets will need to significantly decrease. The Air Force Research Laboratory (AFRL) Operation Responsive Space (ORS) initiative is pushing the boundary of quick deployment of space assets with an objective goal of the six day satellite. To meet the goals of ORS, the satellite must be adaptable to different missions, changing threats, and emerging technologies. In order to minimize integration efforts and meet these objectives, satellite subsystems will be intelligent modules that support a plug-¬in-play interface architecture between modules and the satellite bus. The Space Plug-and-Play Avionics (SPA) system in development by AFRL Space Vehicles Directorate addresses the space craft subsystems software and electrical interfaces. Two critical subsystem modules are the S-band Command, Control, and Telemetry (CC&T) and UHF/S-Band Mission Data radios. This paper introduces the Programmable Satellite Transceiver (PST) design concept for the radios. The PST as one of many Plug and Play (PnP) components supports the Space Plug-in-Play Avionics Universal Serial Bus (SPA¬U) interface. The PST design is adaptable to be used in standard satellite configurations, but it can also support AFRL’s ORS PnP configuration architecture. A PnP component contains Self¬Defining Data Sheet (xTEDS) which has all the data products, commands, interfaces, services, telemetry, and standard commands to define that subsystem. With a comprehensive intelligent protocol for each of the subsystems, satellite integration and test is significantly reduced and simplified. Traditional single frequency radios are set at the factory to a specific frequency and modulation type. The PST provides a modular software radio designed for space operations combining frequency agility and software configured signal processing functions in a re-programmable transceiver. Radiation tolerant parts and radiation mitigation techniques are used to enable the configurable operation in a space environment. For CC&T radio applications the modulator and demodulator can be independently tuned to any SGLS or USB frequency combination under software control. As a Mission Data radio both two-way UHF is supported along with S-Band transmit for TDRS applications using staggered PSK modulation schemes. All baseband Digital Signal Processing (DSP) functions are performed by a reconfigurable Xilinx Field Programmable Gate Array (FPGA). FPGA signal processing allows future upgrade to virtually any waveform set without hardware modifications. The ORS program objectives direct the development of technologies that support robust and flexible satellite bus designs. The PST using the SPA-U interface allows for rapid integration within these designs and provides a flexible yet modular and adaptive solution for CC&T/Mission Data radio functions. The PST design concept enables the ORS to provide a cost effective approach to rapid space asset deployment, operations, and maintenance over the life cycle of DoD space missions. | |
| | |
| Paper Number RS6-2008-4004: Design and Use of a Variable Thermal Layer (VTL) for Rapid Satellite Component Intergration | |
| William Hafer (Infoscitex Corporation), Nicholas Vitale (Infoscitex Corporation), Chris Macris (Enerdyne Solutions), Robert Ebel (Enerdyne Solutions), John McCullough (Enerdyne Solutions), Andrew D. Williams (Air Force Research Laboratory, Space Vehicles Directorate) | |
| View/Download:Presentation | Paper | |
| Abstract: Operationally Responsive Space (ORS) requires the design and assembly of small tactical satellites in greatly reduced timeframes. This capability can be achieved with a generic plug-n-play satellite bus implementing modular structural, electronic and thermal interfaces for payload and supporting components. Modular thermal interfaces are particularly difficult to implement, due to the wide range of thermal characteristics of spacecraft components. To address this need, Infoscitex is developing the Variable Thermal Layer (VTL), a modular interface component for insertion between the satellite bus and a range of critical components. The VTL functions as a thermal gasket that is inserted between the bus and the component's baseplate. The thermal behavior of the VTL can be varied to allow precise control of thermal flux into or out of the component. VTL is implemented as an array of thermo-electric devices (TEDs) embedded in an otherwise insulating matrix, such as an MLI or aerogel blanket layer. Each TED can actively pump heat in either direction, either warming or cooling the component. Maximum heat loads on the VTL occur during the spacecraft hot cycle, when heat must be removed from the component down the thermal gradient and into the bus. Working with the thermal gradient allows the TEDs to operate efficiently, at a coefficient of performance (COP) of 5 or greater, meaning that the heat is removed from the component is five times the power supplied to the TEDs. By applying active thermal pumping over baseline conduction, the VTL can achieve “effective” thermal conductivities ranging from a minimum of 10 W/m2-K, up to a maximum of 700 W/m2-K. This performance range addresses many spacecraft components relevant to a tactical satellite bus. Some components whose thermal requirements exceed VTL capabilities, such as some electromagnets, can be integrated with the use of a thermal doubler or similar mechanism to spread the thermal load. The distributed nature of the TED array allows the VTL to conform to the hot-spot distribution of a given component, as well as matching the variation of the component’s thermal requirements in time due to changes in operating mode and orbital position. The footprint of the VTL (L, W) is sized specifically to each component. All other attributes of VTL are unchanged from component to component and spacecraft to spacecraft. | |
| | |
| Paper Number RS7-2009-6003: The 7-Day Solution: How ORS Will Answer The Rapid Call-up Challenge | |
| Charles J. Finley (DoD Operationally Responsive Space Office), Apoorva Bhopale (Millenium Engineering and Integration Company) | |
| View/Download:Presentation | Paper | |
| Abstract: The Operationally Responsive Space (ORS) Office leads the community in the development of enabling capabilities providing assured space power focused on the timely satisfaction of Joint Force Commanders’ needs by employing current systems and deploying or developing new systems to augment and replenish capabilities. Our efforts are focused on achieving three categories of solutions. Tier-1 solutions use or “employ” existing or on-station capabilities to provide highly responsive space effects through the employment/modification/revised application of existing, fielded space capabilities. The targeted time period for application of Tier-1 solutions is immediately-to-days from the time at which the need is established. Therefore, these solutions focus on existing ground and space systems, operations, and processes. If a Tier-1 solution is unachievable, a Tier-2 solution is considered. Tier-2 solutions rapidly call-up or utilize field-ready capabilities or “deploy” new or additional capabilities that are field-ready. The targeted timeframe for delivering usable Tier-2 solutions is days-to-weeks from the time at which the need is established. The focus of activities in Tier-2 solutions is on achieving responsive exploitation, augmentation, or reconstitution of space force enhancement or space control capabilities through rapid assembly, integration, testing, and deployment of a small, low cost satellite. Finally, when an expressed need is not be addressable through existing capabilities (Tier-1) or through the rapid deployment of field-ready capabilities (Tier-2), ORS efforts must focus on the rapid development and deployment of a new Tier-3 capability. Once developed, Tier-3 capabilities will be responsively deployed and employed in the same way as Tier-2 assets. The goal for execution 7of Tier-3 approaches is months-to-one year from established need to presentation of operational capability.2 Within the three-tiered suite of ORS responses, the Tier-2 response requires the largest paradigm shift, i.e., departure from the current space enterprise best practices and concept of operations. How do you respond to any urgent need within a week with a 100% reliable, perfectly effective solution with minimal non-recurring cost? The simple answer is, “You don’t.” The Tier-2 problem is solved as much by defining boundaries, as it is by enforcing interface standards or developing innovative technologies and techniques, more akin to an aircraft depot than a one-of-a-kind spacecraft development. This paper will start by addressing the boundaries that transform the insurmountable task referenced above into a potentially solvable problem. It will explain how these boundaries not only manage expectations, but serve to focus the ORS Office Tier-2 activities. Next, the paper will present the ORS Office’s envisioned Tier-2 End State and detail the steps the Office is taking over the next six years to achieve our vision: 1) It will explain how the ORS Office is championing interface standards as enablers to the Tier-2 vision and how it will make these standards meaningful by winning industry buy-in through ORS-funded missions that clearly demonstrate the business case; 2) It will explain how the ORS Tier-2 CONOPS is incorporating best-practices from non-space industries, which currently solve problems very similar to the Tier-2 challenge; 3) It will present analysis to show how the solution was derived from a detailed trade of schedule, cost, flexibility of the solution to meet the portfolio of anticipated urgent needs, and reliability and effectiveness of the ultimate solution; and 4) Finally, it will summarize the status and results of ongoing ORS Office Tier-2 efforts. | |
| |