|
|
Home RS2011 Conference (Details) Call for Papers Conference Program Registration Sponsor/Exhibit Prior Conferences ORS Reference Search Contact Info |
|
Past Conference Papers:
Lessons Learned
| Paper Number RS1-2003-1004: Heritage Schmeritage or, How to Get to Responsive Space in the Near Term and Away from Heritage Based Systems | |
| Chris McCormick | |
| View/Download:Presentation | Paper | |
| Abstract: Old techniques, old regulations, and old designs – Heritage - cannot fundamentally change from a mostly art business (sometimes Responsive in capabilities, non-responsive to cost and schedule) to an assembly line business which is responsive in cost and schedule, and still be hopefully configurable for ‘responsive requirements’. We try to mold ourselves away from the art business, to creating new space missions systems out of the heritage components and spacecraft. This is not optimal, nor is it practical. | |
| | |
| Paper Number RS1-2003-5002: Lessons Learned From Past Reusable Launch System Designs | |
| Gregory Peralta (Lockheed Martin) | |
| View/Download:Presentation | Paper | |
| Abstract: The X-33 single-stage-to-orbit (SSTO) technology demonstrator funded by the United States Government and industry provided significant data to support SSTO design. The system focused on developing a highly responsive, operational efficient SSTO that could validate the basic technology and proof-ofconcept. Recent endeavors, such as the NASA Space Launch Initiative Two-Stage-to-Orbit and SOV programs have utilized the methodology taken on the X-33. The X-33 enjoyed many design successes. Although, several set backs resulted in the premature termination of the X-33 program. In hopes of benefiting future designers of responsive, reusable launch systems, this paper will discuss the design philosophy and testing approach of the X-33 by emphasizing the lessons learned This paper will also review past programs and illustrate why future operational programs need distinctly separate developmental and operational programs. This separation must be accomplished by completely qualifying components and procedures during the development phase of a program. Flight and mission performance as well as ground system operations efficiencies can be achieved through a “design to operations” systems approach with correct implementation of updated technologies where appropriate. Government investment must be directed toward operations certification of new system technologies as much as it is on traditional flight performance qualifications. Tremendous improvements can be made in system operations, which will translate into program efficiencies and lower overall system cost from the first launch and continuing through the life of the program. | |
| | |
| Paper Number RS2-2004-2002: A Novel Approach to Responsive Space: Lessons Learned by the DoD Space Test Program | |
| Sabrina Herrin (The Aerospace Corporation), Eleni Sims (The Aerospace Corporation) | |
| View/Download:Presentation | Paper | |
| Abstract: This paper explores four Department of Defense (DoD) Space Test Program (STP) missions and identifies lessons learned in successfully achieving responsive space flight. Case studies included are NanoSat-2, Kodiak Star, MISSE 5, and SPHERES. In creating a responsive space mission, often the focus is on getting a space vehicle built and a launch vehicle procured as quickly as possible to get from a conceptual design to data from space in the least amount of time. As STP has found, there are effective responsive space techniques that may be better suited to a mission than merely building and buying components faster. The examination of the four case studies leads to several conclusions: 1) be open to a change in plans and to solutions that have never been attempted, 2) networking will create more opportunities, 3) if one wants to do something quickly, commit wholeheartedly and apply enough resources to make the project work, 4) risks and how to mitigate them should be identified in the beginning of a program, 5) prior to “starting from scratch,” investigate the utilization of existing resources and designs, 6) be prepared to take advantage of opportunities when they come along, and 7) making a project scalable, so that objectives can be accomplished piecemeal, will increase the number of manifest options. | |
| | |
| Paper Number RS2-2004-5001: Real-Time Mosaic - Rapid Response Hight Resolution Imaging from Space | |
| Alex da Silva Curiel (SSTL), Phillip Davies (SSTL), Stuart Eves (SSTL), Lee Broland (SSTL), Martin Sweeting (SSTL) | |
| View/Download:Presentation | Paper | |
| Abstract: An imaging constellation mission is proposed to provide near-continuous surveillance of regional activity. By introducing a multiple plane constellation of small Earth Observation satellites, it is possible to monitor selected parts of the entire globe several times during daylight. Using off-the-shelf microsatellites ensures the program is responsive in the deployment phase as well as in the operational phase. The paper describes the basic Disaster Monitoring Constellation programme as has been implemented, which already delivers daily imagery. It also describes the system trades of the regional imaging constellations, and outlines the scope of the performance that could be obtained from such a system. A cost model illustrates that the balance between launch and space segment costs must be reached by considering suitable replacement strategies, and that the system is highly sensitive to requirement creep. Finally, it is shown that the use of cost effective, small satellites leads to solutions previously thought to be out of reach of Earth Science and Government customers. | |
| | |
| Paper Number RS2-2004-5006: Lessons Learned From A Rapid Response Payload Development | |
| G. Murphy (Design_Net Engineering), T. Adams (Design_Net Engineering), K. Stewart (Design_Net Engineering) | |
| View/Download:Presentation | Paper | |
| Abstract: Responsive Space requires Responsive Payloads! This paper tells the story of just such a payload and examines the lessons that were learned from that development. Starting with the Space Shuttle flight 4A (Nov. 30, 2000), the International Space Station (ISS) power system employed large, high voltage, solar arrays with the negative ground tied to chassis. An intense study by a NASA sponsored Tiger Team in the early ‘90s determined that this configuration leads to the structure being at a high negative potential relative to the local plasma (approximately 140V negative without any intervention) and, that at any potential greater than around 70V negative, the anodized aluminum structure and its components will undergo destructive arcing. A set of plasma contactor units (PCUs) were deployed to provide a conductive xenon plasma path for remitting electrons collected by the arrays and thus bring the potential closer to zero and mitigate the arcing danger. In late July 2000, the ISS program office at JSC issued an engineering change notice that directed the development of some means to independently assess the performance of the PCU’s, and to have hardware available for launch on STS-97 (ISS Flight 4A) the very mission scheduled to deliver and install the first set of large Station solar arrays on November 30th. This was needed to meet safety requirements for EVA. Such a schedule allowed only 4.5 months to design, build, test, manifest, complete EVA training, and deliver for launch. This set the stage for one of the most rapid payload developments since the early days of NASA. NASA Glenn Research Center (GRC), NASA Johnson Space Center (JSC), and Design_Net Engineering (DNet) formed a unique team to try to accomplish the directive. The subject of this paper is to describe the Floating Potential Probe (FPP) and the fast-track program approach used to quickly develop this autonomous system for measuring the electrical potential between the ISS and the surrounding space plasma. At the time, most people involved with the Floating Potential Probe (FPP) project believed that there was less than a 10% chance of successfully making it onboard Flight 4A and an even lesser chance that it would work. Although there are aspects of this program unique to ISS, many of the lessons learned are being applied by DNet to rapid response payloads for ELVs. | |
| | |
| Paper Number RS3-2005-1003: On-Demand Science Missions | |
| John J. Webb, Jr. (Instarsat) | |
| View/Download:Presentation | Paper | |
| Abstract: Over the last four decades, robotic space explorers have yielded a wealth of scientific discoveries about our solar system and its origins. However, the resources required to design, develop, launch, and operate such missions is enormous. The highly prohibitive nature of established design practices and long development cycles significantly precludes responsive science investigations. Historically, robotic science missions flown in the last forty years have been highly limited in scope and capability. This paper briefly reviews the current practices in use for developing science missions, including; mission design, spacecraft design, and cost estimating. In contrast, today’s science missions must be more responsive to changing circumstances. The advances in space related technologies make ondemand science missions even more relevant and desirable. The spacecraft capabilities, capacity, and cost effectiveness are essential deterministic factors enabling successful on-demand science missions. This paper will focus on defining these factors within the context of a responsive space system. This paper discusses the emergence of new space-related technologies that will accelerate the development of on-demand science missions. This discussion includes an overview of current advances in materials, communications, propulsion, and onboard autonomous systems that can play a critical role in the successful design, development, and operation of on-demand science missions. Finally, this paper discusses an on-demand science mission life cycle scenario. | |
| | |
| Paper Number RS3-2005-3005: The Little Probe that Could: Four Months from ATP to Launch | |
| Gerald Murphy (Design_Net Engineering), Ken Center (Design_Net Engineering) | |
| View/Download:Presentation | Paper | |
| Abstract: Responsive Space requires Responsive spacecraft! Last year Design_Net discussed just such a small spacecraft and examined the programmatic lessons that were learned from that development. This was the Floating Potential Probe (FPP). Flight 4A for the ISS was to deploy a new set of high voltage solar arrays which, due to large amount of electron current collected from the LEO plasma, caused the vehicle ground to shift significantly. The potential shift could lead to destructive and dangerous (for EVA) arcing. A set of plasma contactor units (PCUs) were being deployed to provide for emission of electrons collected by the arrays thus bringing the potential closer to zero and mitigating the arcing danger, however no means was in place to verify that the PCUs were working. In late July 2000, the ISS program office at JSC issued an engineering change notice that directed the development of some means to independently assess the performance of the PCU’s, and to have hardware available for launch on STS-97 (ISS Flight 4A) the very mission scheduled to deliver and install the first set of large Station solar arrays on November 30th. Such a schedule allowed only 4.5 months to design, build, test, manifest, complete EVA training, and deliver for launch. NASA Glenn Research Center (GRC), NASA Johnson Space Center (JSC), and Design_Net Engineering (DNet) formed a unique team to try to accomplish the directive. Previous papers (1,2) have discussed in detail the design of the FPP and some of the programmatic lessons that were learned which are applicable to responsive space. In addition to these lessons, a number of engineering and technological innovations are required to support responsiveness. Design_Net has expanded the lessons from the FPP responsive bus to more generic application. In this paper will focus our attention on three key aspects from a technological point of view that support rapid response. We focus on: 1) the systems engineering process and the technologies and tools that are enablers for rapid design/configuration in the early stages of a program; 2) the interaction of configurability with requirements and; 3) the role of standards and Plug and Play (PnP) capability in achieving rapid development and integration. | |
| | |
| Paper Number RS5-2007-1003: Future Optical Surveillance Using Small Satellites | |
| Stuart Eves (Surrey Satellite Technology) | |
| View/Download:Presentation | Paper | |
| Abstract: The paper will describe the successes of the TopSat and Beijing-1 surveillance missions, and will indicate how the lessons-learned from these satellites will influence the design of the next generation of optical surveillance constellations. Specifically, the ability to collect data with multiple sensors at different resolutions over different areas allows the satellites to be used responsively in different modes, depending upon the nature of the crisis situation. The agility of small satellites allows them to use Ground Motion Compensation modes to collect data over a wider range of illumination conditions, and the paper will illustrate how this capability allows a broader range of orbits to be considered, (with consequent implications for revisit rates, and hence responsiveness). This agility can also be used to implement in-pass stereo and wide-swath imaging modes when required. With the launch of the RapidEye constellation now imminent, the paper will also describe how the design of the next generation of satellites will be specifically designed for launch as part of a constellation. | |
| | |
| Paper Number RS3-2005-5006: How Not to Design an Avionics System | |
| Jason E. Holt (Brigham Young University) | |
| View/Download:Presentation | Paper | |
| Abstract: In 1995, four Utah Universities launched a hybrid sounding rocket at the Utah Test and Training Range. In December 2003, they successfully launched a much larger successor to that rocket. We describe the design, construction, deconstruction, redesign and reconstruction of the avionics package during the 8 year period between flights, then describe the system which was actually flown. That package used COTS hardware worth less than $1000, was substantially redesigned within weeks of the launch, and was completely destroyed after an entirely successful flight upon an otherwise soft, vertical landing. Although the package met only simple requirements and used no cutting-edge hardware, we feel that the lessons we learned from both technical and social standpoints will be useful to others who wish to rapidly develop avionics systems despite severely limited resources. Furthermore, we describe a new, straightforward design for the core control system which is a result of the lessons we learned, and which we hope will be flexible enough to meet the continuing demands of our project and potentially many other projects as well. | |
| | |
| Paper Number RS4-2006-1002: Fractionated Space Architectures: A Vision for Responsive Space | |
| O. Brown (Defense Advanced Research Projects Agency), Paul Eremenko (Booz Allen Hamilton) | |
| View/Download:Presentation | Paper | |
| Abstract: The advent of the integrated circuit some four decades ago set off mankind’s insatiable thirst for computational power. The quest to quench this desire led to the development of increasingly more sophisticated computers. Microchips sprouted ever greater numbers of transistors, choking buses, and forcing memory banks to struggle to keep up. The novelty of micro- and minicomputers was quickly trumped by the sheer computational prowess of supercomputers. And so the trend continued. In a matter of two decades, however, this drive towards greater processing power culminated in mammoth mainframes whose rapidly increasing complexity, fragility, and cost quickly outpaced the capability gains. A scant few years into the second decade of the era of the integrated circuit, the availability of inexpensive, mass-produced microcomputers, and the advent of fast, seamless internetworking ensured the relegation of the large monolithic mainframes to obsolescence and obscurity. Spacecraft have followed a trajectory that is uncannily parallel (and, of course, technologically intertwined) to the history of high-end computing. Borrowing the historical analogy, we posit that the era of distributed space architectures has likewise arrived. The gargantuan monolithic systems deployed to orbit today have grown too large, too complex, too fragile, and consequently much too expensive; furthermore, these trends have not been offset by commensurately rapid growth in capability. We propose a fractionated architecture for space systems, whereby a satellite is decomposed into a heterogeneous set of components which interact wirelessly. In the extremum, the fundamental functionality of most space systems is the reflection of photons back to earth. Thus, assuming that the requisite photon collection, processing, and re-radiation can be accomplished, the spacecraft need be nothing more than a collection of free-floating “pixie dust.” In the realm of the foreseeable technological future, however, there are a handful of schema for severing and distributing the functionality of a monolithic spacecraft. Perhaps the most basic is fractionating the spacecraft along its data channels, resulting in a loose cluster of networked spacecraft modules. Somewhat more challenging is also fractionating the power system and disseminating power wirelessly among the modules. At the technological horizon is also fractionating the propulsion and stationkeeping functionality, also necessitating the wireless transmission of forces and torques. The fractionated architecture is likely to incur an aggregate mass impact versus its monolithic counterpart (although it is noteworthy that at least one massive component may shrink – the flywheels necessary to ensure payload pointing accuracy need only be responsible for stabilizing and pointing the payload module, not the entire spacecraft). The impact on overall system cost is ambiguous since the cost impact due to greater system mass is at least partially offset by learning curve and mass production effects across the multitude of modules. For a constant required level of functionality, however, the fractionated architecture dramatically outperforms its monolithic counterparts in its value proposition. It affords its user/operator greater flexibility in the form of system scalability, reconfigurability, and adaptability (including multi-payload functionality). It dramatically increases robustness and survivability. It allows the isolation of the payload for both improved security and increased pointing accuracy. It lowers possible increases in lifecycle cost and decreases schedule risk by decorrelating failure probabilities of the various component subsystems and multiple payloads. It improves responsiveness by allowing incremental capability deployment, by enabling the utilization of small launch vehicles for the emplacement of massive orbital capabilities, and by shifting the deployment decision chain from the strategic to the tactical level. Perhaps most importantly – and much like the internetworked microcomputer – it commoditizes the space industry and transforms it from an exotic boutique to a customer-driven, cost-competitive enterprise. The technologies needed to make fractionated space systems a reality are well within reach. They potentially include responsive and inexpensive small launch vehicles, highly secure ultra wideband inter-module data links (which may also provide relative navigation capabilities for the spacecraft modules), efficient radio frequency power transmission, passively stable Keplerian cluster orbits, and mass-produced, inexpensive, space-qualified satellite components (many with their legacy in the newly-emergent field of unmanned aerial vehicles). More esoteric technology options include very high frequency power beams, laser power transmission, and remote force and torque transmission through electromagnetic induction. The Defense Advanced Research Projects Agency (DARPA) has been studying the fractionated architecture concept and is poised to commence an initiative entitled F6 – short for Future Fast, Flexible, Fractionated Formation-Flying Spacecraft utilizing Information eXchange, and incidentally a tornado of unimaginable strength on the Fujitsu scale – that will mature the associated technological, architectural, and organizational advancements necessary for an onorbit demonstration of a fractionated spacecraft. A brief discussion of the vision for F6 concludes. | |
| | |
| Paper Number RS4-2006-1006: Using Proven Aircraft Avionics Principles to Support a Responsive Space Infrastructure | |
| Randy Black (Honeywell Space Applications) | |
| View/Download:Presentation | Paper | |
| Abstract: Creating an engineering environment that supports responsive space involves a variety of interrelated disciplines. Included within these disciplines is the ability to quickly re-configure systems through plug-and-play hardware and software. Plug-and-play hardware as a concept has been progressing well throughout the electronics industry. Plug-and-play software has been somewhat more challenging. While some advances have been made through object-oriented architectures and model-based autocoding, software lags behind hardware in this area. Honeywell has experienced significant success for the past ten years fielding plug-and-play software at the application level. Using a combination of time and space partitioning, table-driven operations, and robust off-line development tools, Honeywell’s Integrated Modular Avionics (IMA) has produced significant savings in development cost and schedule. More importantly, modifications to either hardware or software are quickly and easily integrated into the overall system with minimal re-certification required. During the past decade, Honeywell has produced multiple implementations of this advanced avionics technology. One lesson learned is that specific implementation details are not as important as designing to key architectural principles. This paper describes several of those principles that have a proven track record of enabling rapid reconfiguration of system architectures. Architectural principles that support plug-and-play software applications, as well as minimizing the impact of hardware modifications, provide the core of a system design that is integral to an overall responsive space infrastructure. | |
| | |
| 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 RS6-2008-6003: TopSat- Assessing the Military Utility of a Tactical ISTAR Demonstrator | |
| H.S. Jolly (Defence Science and Technology Laboratory), D. Beard (Defence Science and Technology Laboratory), T. Burt (Royal Air Force) | |
| View/Download:Presentation | Paper | |
| Abstract: Launched on 25 October 2005, TopSat is a small (<110kg) low-cost (~ $28M), electro-optical (EO) imaging satellite demonstrator designed, built and operated by a British consortium led by QinetiQ under contract to the UK Ministry of Defence (MOD) and the British National Space Centre. Despite early technical difficulties, the programme demonstrated that the UK could successfully build and operate a small, low cost, satellite that could be tasked quickly and provide very fresh imagery. It also provided potential users with insights into how a future system might be employed and also clarified potential user requirements. The military utility of TopSat was assessed by the UK MOD TopSat Users Group (TUG) through an evaluation of the performance of the satellite system during a series of experiments, trials and exercises through 2006-2007. The TUG comprised participants from Front Line Commands and other MOD organisations, and was assembled to undertake the assessment of the military utility of TopSat. This paper presents the joint assessment made by the TUG participants and includes the conclusions and lessons drawn from the programme relevant to the implementation of responsive space. | |
| | |
| Paper Number RS7-2009-3010: Nanosatellite Tracking Ships: Responsive, Seven-Month Nanosatellite Construction for a Rapid On-Orbit Automatic Identification System Experiment
| |
| Freddy Pranajaya (Space Flight Laboratory), Robert E. Zee (Space Flight Laboratory), Jeff Cain (COM DEV Limited), Richard Kolacz (COM DEV Limited) | |
| View/Download:Presentation | Paper | |
| Abstract: The Space Flight Laboratory (SFL) at the University of Toronto Institute for Aerospace Studies and COM DEV Ltd have developed a low Earth orbit nanosatellite in less than seven months to perform rapid turnaround experiments in space to detect and study Automatic Indentification System (AIS) signals transmitted by maritime vessels. The satellite, known as "Nanosatellite Tracking Ships" (NTS) leverages both SFL's CanX-2 nanosatellite technology and Generic Nanosatellite Bus (GNB) mechanical design to house a custom AIS receiver payload developed by COM DEV Ltd. NTS was developed under an extremely tight schedule, with on-orbit results required within a year from contract start. NTS have successfully met all of its mission objectives and continues to operate in orbit. This paper outlines how SFL and COM DEV were able to rapidly design, construct and deploy a custom satellite to respond to the opportunity to bring on-orbit AIS detection services to the international community. | |
| | |
| Paper Number RS7-2009-3004: A New Paradigm for Responsive Space Missions | |
| Bill Jackson (Sierra Nevada Corporation Space Systems) | |
| View/Download:Presentation | Paper | |
| Abstract: SpaceDev (a subsidiary of Sierra Nevada Corporation) built and delivered the Trailblazer microsatellite as the first Operationally Responsive Space (ORS) “Jumpstart” mission, which was intended to demonstrate rapid assembly, integration, test, and launch processes. This “Jumpstart” mission was a multi-pronged effort to fly responsive payloads on the SpaceX Falcon 1 Flight 003 launch vehicle, which launched in August 2008 from Kwajalein Atoll in the Marshall Islands. This launch opportunity became available because the original payload for this launch had been de-manifested. The spacecraft was assembled, integrated, and tested at SpaceDev’s Poway, California facility. The rapid call-up time on this mission presented a number of difficult technical problems; including the absence of several critical long-lead items, a late flight radio change, a late requirement for encryption, lack of a ground station and mission operations center, and lack of any mission operations procedures. The SpaceDev Trailblazer team adopted an extremely aggressive “skunk works” approach that used a small, empowered, multi-disciplined team to meet difficult technical and schedule challenges. The SpaceDev team was able to demonstrate unusual flexibility and responsiveness by tailoring engineering processes to meet the demanding schedule. SpaceDev not only successfully delivered the Trailblazer satellite on budget and on schedule, but also developed a Mission Operations Center in Poway, and fielded much of the Ground Station equipment on Kwajalein. The Trailblazer satellite was launched on August 2, 2008. Unfortunately, a technical problem with the Falcon second stage separation sequence resulted in catastrophic failure of the launch vehicle, and the Trailblazer satellite did not achieve orbit. Despite the unfortunate launch vehicle failure, the Trailblazer program nevertheless made a number of significant accomplishments: ? Responsive spacecraft build and test (4 months) ? Responsive spacecraft-to-launch vehicle integration (< 1 week) ? Responsive Ground Station development ? Responsive Mission Operations Center development ? Responsive contracting and administration ? Successfully demonstrated an end-to-end launch call-up within 7 months of standing up the ORS office This paper will detail some of the many technical and programmatic challenges of this fast-paced program, and will discuss how SpaceDev was able to ultimately deliver a fully-functional spacecraft to ORS in just four months. | |
| | |
| Paper Number RS7-2009-6005: Nanosatellite Tracking of Ships — Review of the First Year of Operations | |
| Franz Newland (COM DEV Ltd), Elliott Coleshill (COM DEV Ltd), Ian DSouza (COM DEV Ltd), Jeff Cain (COM DEV Ltd) | |
| View/Download:Presentation | Paper | |
| Abstract: The COM DEV Nanosatellite Tracking of Ships (NTS) mission has now been operating successfully for 7 months, exceeding its life requirement of one-month and even the goal of 6-months. The spacecraft was launched at the end of April 2008 following an unprecedented 8-month kick-off to launch cycle. NTS is still producing valuable results from its Automated Identification System (AIS) payload, designed to collect messages from maritime vessels around the globe. The mission has given COM DEV unique insight into the potential for collecting AIS signals from space and has demonstrated the superior performance of COM DEV’s AIS payload in addressing some of the difficulties of AIS message detection from space. With the success of the spacecraft, the objectives for the mission have been extended beyond the initial demonstration of the potential for collecting AIS messages from space. Even with its limited functionality, NTS payload has succeeded in collecting AIS data from all parts of the globe and is now being used to test the payload design envelope to optimise future payload design. Within the equivalent of just over 45 minutes of cumulative payload operation, NTS has collected messages from an estimated 1/7th of the world’s shipping population equipped with AIS transmitters. Having demonstrated responsive spacecraft development during the NTS design and build cycle, the past 7 months have demonstrated a number of responsive operations activities by COM DEV and its contractors, including supporting collaborative experiments with sensor suites from other missions. Results have exceeded expectations to the point that operations have been extended indefinitely, and have been enhanced through an additional low-cost ground station built in collaboration with the University of Aalborg in Denmark. This ground station allows faster data turnaround from the satellite and supplements the existing station operated by the University of Toronto Institute of Aerospace Studies’ Space Flight Laboratory (UTIAS/SFL). The development of an additional ground station for NTS within a very limited budget has been possible through university collaboration and reuse of existing assets, both important elements in commercially responsive space activities. This paper presents the results of the NTS mission to date and how the mission has been extended to meet other objectives. Having been developed as a highly responsive mission, NTS has very successfully demonstrated the operational utility and capabilities of responsive space over the past 7 months, and the operational flexibility that is still achievable with such missions. The paper also discusses the ongoing operations activities for NTS, and the impact of NTS on future AIS missions including the upcoming Defence Research and Development Canada / Canadian Space Agency (DRDC/CSA) sponsored M3MSat microsatellite mission intended for launch in 2010. | |
| | |
| 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. | |
| |