Developing a Responsive Ground System Enterprise
Rico Espindola and Gayla Walden
Responsive space requires responsive ground systems. Aerospace is helping to establish a comprehensive ground system enterprise that can meet the anticipated tactical demands.
The Operationally Responsive Space (ORS) Office was established by Congress in May 2007 to spearhead development of capabilities that would enable the timely and assured application of space power to support theater operations on the ground. Some of these capabilities would derive from the redirection of current systems, and some from the development of new systems to augment and replenish capabilities.
ORS is designed to enable military planners to respond to unexpected loss or degradation of existing capabilities and provide timely availability of new or expanded capabilities. The goal is to bring new assets on line in a matter of months (Tier 3), weeks (Tier 2), and hours (Tier 1). One key element of the ORS concept is a responsive ground system enterprise that can accommodate rapid developments in the space and user segments. Individual military services and organizations have been developing their own service oriented architectures for satellite command and control, and ORS requires a ground system enterprise that can link these disparate systems. Within the ORS Office and partner organizations, Aerospace is supporting activities to establish a compatible architectural framework for satellite operations.
ORS Initiatives
The ORS ground system enterprise envisioned for 2015 will support augmentation, reconstitution, and operational demonstrations. The architecture was baselined to support intelligence, surveillance, and reconnaissance (ISR) missions. It will provide a Web-based small-satellite planning and tasking tool for joint force commanders that accesses a virtual ground station to provide all command and control and tasking for ORS systems on orbit. The data collected by an ORS spacecraft will be sent to a ground station using DOD-selected formats, protocols, and interfaces. This accommodates the use of disparate data-processing systems and limits the need for the ORS Office to develop additional user hardware and software. The data will be disseminated through the global information grid. Direct downlink of payload data to the joint force commanders or of processed information to a warfighter in the field is an end-state objective.
The operationally responsive space ground systems enterprise service layer. The setup features military satellite operations centers that can share information. |
Key capabilities for the 2015 timeframe include autonomous operations for multiple constellations of small satellites; synchronization of ORS assets with other available capabilities; payload tasking and request tracking through a simple user interface; standard vehicle maintenance; payload mission planning; standard command and control of the spacecraft through ground-based and space-based relay; collection of telemetry and mission data through ground-based and space-based relay; processing and dissemination of telemetry and mission data to joint force commanders or provision of direct downlink to a warfighter in theater; and rapid transition of spacecraft demonstrations and prototypes to operational use.
In addition, a number of ancillary needs are being considered. For example, the ground system enterprise should incorporate a modular open-system architecture to promote innovation, standardization, and nonproprietary development. It should connect to exercise and wargame engines and integrate with the global information grid. It should allow autonomous mission planning, data processing, and data distribution and support system-level testing. It should incorporate a responsive information assurance program, a responsive configuration management process, and a responsive frequency management system. It must support, at multiple levels of security, ORS missions involving electro-optical/infrared systems, nonimaging infrared systems, signal intelligence, synthetic aperture radar, space and terrestrial situational awareness, mobile communications, and blue-force tracking. Lastly, it must assign sufficient network priority to ORS missions to expedite the upload of mission tasking and the download of mission data.
Functional Elements
To achieve the envisioned ground system enterprise, the ORS Office has made investments that leverage existing initiatives and architectures. These include Air Force Space Command's Multi-Mission Satellite Operations Center (MMSOC) ground system architecture, NASA's Goddard Mission Services Evolution Center (GMSEC) message bus middleware, the Naval Research Laboratory's Virtual Mission Operations Center (VMOC), and the Distributed Common Ground System enterprise. All of these elements will be brought together for the first major mission of the ORS Office, the ORS-1 satellite.
The operationally responsive space ground system enterprise for intelligence, surveillance, and reconnaissance. The constellation includes the functions of telemetry, tracking, and command, payload data, and special tasking and processed information. It is networked through the global information grid and AFSCN. |
MMSOC Ground System Architecture
Air Force Space Command is establishing a high-level operational concept for responsive satellite command and control that aligns with the intended transformation of the satellite operations enterprise architecture. Various command and control systems are being assessed as part of this transition. One such system is the MMSOC ground system architecture, developed by the Space and Missile Systems Center (SMC) Space Development and Test Wing. SMC had been directed to replace an aging ground system with a new, open system that could support unique technology demonstration flights and respond to space operational communities using limited personnel while lowering development and sustainment costs and reducing schedule without increasing technical risk. The MMSOC ground system architecture is structured to support this mandate. It provides telemetry, tracking, and control through the use of open-system and COTS components. It accommodates the integration of newly developed command and control systems through an incremental development process.
DOD experimental and demonstration satellites are typically one-of-a-kind missions designed to last about a year. The MMSOC ground system architecture supports every aspect of such missions, including planning, training, mission preparation, launch and early orbit operation, normal operation, data collection and dissemination, and vehicle health and safety monitoring. Some missions end the experimental phase with a residual operational capability. The MMSOC ground system architecture also supports this residual activity through a collaborative environment that facilitates the efficient transfer of capability from the research arena to the operational theater. This collaborative environment, in which both the transferring and receiving organization trade and share support responsibilities, makes it easier to organize the personnel, processes, and resources necessary to develop and field one-of-a-kind missions. Moreover, the commonality inherent in the use of open systems generates efficiencies in both training and maintenance, minimizing funding requirements in these areas. Likewise, transition of missions and remote backup of operations between similar satellite operations centers becomes more straightforward.
Meeting the challenge of flexible operations at reduced cost requires more than just a materiel solution; process and business rules must also be addressed. The Responsive Satellite Command and Control Division of the SMC Space Development and Test Wing, in conjunction with its contractor team, has developed a strategy for implementing a published future architecture. The strategy employs an evolutionary model guided by an open-systems management plan with interfaces controlled by the architecture services catalog and external interface control document. The open-systems management plan, which Aerospace helped develop, was based on fundamental open-system principles: establish business and technical enabling environments; employ modular concepts; employ business and technical patterns; designate key interfaces; and use open standards for key interface certification and conformance. These principles, combined with the identification of standards (particularly for data and interface control) and the established catalog of services, will allow the program to work with a range of potential missions, reducing unique mission support requirements.
The implementation strategy breaks with the traditional acquisition paradigm in which an extended period of time elapses between the definition of requirements and the fielding of the required capability. Once proven, the MMSOC ground system architecture will be deployed into operational and support components and undergo operational acceptance testing. Operator evaluations will provide feedback for developers and lead to continual system improvements.
The MMSOC ground system architecture is not a "point" solution; continuous upgrades will be necessary to enhance cost effectiveness, ensure sustainability, and prevent system obsolescence. Aerospace helped develop a system evolution plan that will account for both technical needs and projected resources and gradually optimize the system to meet designated targets while maintaining system availability. Part of this evolution plan entails a new block upgrade each year.
The MMSOC ground system architecture has been designated as the primary satellite command and control capability for Air Force missions within the ORS Office. The Block I architecture will be used to support STPSat-2 in early 2010. It will also be installed at one of the satellite operations centers (SOC-11) at Schriever Air Force Base in Colorado Springs to support ORS-1. The Block II study phase was initiated in early 2009, in keeping with the plan for yearly block upgrades. Aerospace is also supporting the Block II study.
NASA's GMSEC framework is composed of three elements that standardize interfaces, provide a middleware infrastructure, and allow users to choose components for specific missions through an application programming interface. The ORS Office is exploring this effort as it attempts to link disparate command and control centers. |
GMSEC
Similar to the Air Force Space Command satellite operations initiative, NASA Goddard Space Flight Center has completed its own transformation and has established the GMSEC framework composed of three elements that standardize interfaces, provide a middleware infrastructure, and allow users to choose components for their specific missions through an application programming interface (API). The GMSEC ground system architecture has supported eight orbiting satellites and is being applied to several of NASA's future missions. Because the ORS Office supports all military services and various organizations, the challenge is to link disparate command and control centers while affording a common architecture across the broader enterprise. The GMSEC message-bus middleware would allow a standard communications infrastructure for compatible command and control interfaces, messaging, and data formats. This could serve as the common mission service interface across the disparate satellite operations centers to enable continuity of satellite operations between systems and communitywide ground situational awareness and space protection.
A common theme at the 2009 Ground System Architecture Workshop (GSAW) cosponsored by Aerospace was command and control across various government organizations. For example, SMC presented the MMSOC ground system architecture. NASA presented a concept for enabling rapid system configurations. The ORS Office presented the 2015 ground system enterprise. A session jointly hosted by NASA and the National Reconnaissance Office discussed the use of common command and control standards across government and industry. It quickly became apparent that all these organizations were independently working toward a common command and control framework, and their efforts would be multiplied through greater collaboration. Accordingly, these organizations formed a committee (known as the Joint SatOps Compatibility Committee, or JSCC) to help steer their efforts toward a compatible space enterprise. Aerospace has been collaborating regularly with members of the committee and continues to explore a compatible command and control framework for SMC.
For example, Aerospace recently completed the first phase of a compatible architecture study that used NASA's GMSEC framework with current command and control software and hardware. As part of this study, a flexible ground system framework was demonstrated in a laboratory testbed in the Aerospace Ground Systems Laboratory. The effort showed the viability of a compatible framework and identified shortcomings in data standards that would need to be addressed before such a system could be optimally implemented. The ORS Office and the compatibility committee are adapting the testbed for future missions and initiatives. (For more on the architecture testbed, see "A Flexible Satellite Command and Control Framework" in this issue of Crosslink.)
The Virtual Mission Operations Center (VMOC) architecture, which is managed by the Naval Research Laboratory. The ORS Office has selected the VMOC as the tasking and sensor visualization tool for its 2015 ground system enterprise. Aerospace is helping to define the objectives necessary to make this vision a reality. |
VMOC
The Virtual Mission Operations Center (VMOC) concept began in 2000 with a collaboration between NASA Glenn Research Center and a contracting partner. Between 2004 and 2007, the VMOC focus was on demonstrations supporting the standardization of spacecraft-to-ground interfaces needed to reduce cost, maximize user benefits, and allow the generation of the new procedures required to shape responsive space employment. In 2008, the efforts merged under the Naval Research Laboratory to focus on the integration of all the elements into a system of systems that could begin addressing the needs of responsive space tasking and data collection and processing. The ORS Office has selected the VMOC as the tasking and sensor visualization tool for its 2015 ground system enterprise, and Aerospace is helping define objectives for the VMOC that would help achieve this vision.
The near-term focus for the VMOC is on supporting the TacSat-4 and ORS-1 satellites. TacSat-4 is part of a series of experiments developed by the Naval Research Laboratory in support of ORS objectives. The payloads include mobile communications, blue-force tracking, and data exfiltration. For TacSat-4, the VMOC will interface with the Naval Research Laboratory's Blossom Point ground station and take advantage of that facility's highly automated mode of operations. The interface between the VMOC and the spacecraft operations center is being refined and tested for TacSat-4 and will provide the baseline for ORS-1, which will require the VMOC to interface with the MMSOC ground system architecture at Schriever Air Force Base.
To maximize the benefit on theater operations, ORS assets will need to be directly tasked, just like any other operational asset. VMOC is building a common planning, tasking, and tracking interface that will be integrated with tasking tools such as PRISM (Planning tool for Resource Integration Synchronization and Management). The automated interface between the tactical, apportionment, and mission components of the VMOC will allow scalable multimission planning with a "Fed-Ex" style capability that will allow users to track the status of their data requests.
The ORS-1 mission architecture. Scheduled to launch in 2010, ORS-1 will respond to an operational need for an ISR request from U.S. Central Command. (NASA) |
Using the tactical component of the VMOC as the tasking and sensor visualization tool in exercises and operations will greatly assist in the refinement of organizational roles and responsibilities. It will also provide insight into ORS availability and limitations, allowing operators to evaluate emerging requirements and apply the correct asset at the right time—without putting the platform at risk of being overtasked. The apportionment VMOC component provides the tools needed by the joint force commanders to model and effectively apportion space platforms and sensors for maximum effect. An integrated apportionment allows for rapid changes in the rules that the mission component uses to schedule tasks. By integrating the mission component of the VMOC with the satellite operations centers, the joint force commanders will have direct access to payload scheduling and near-real-time payload tasking using traditional command and control as well as over-the-horizon relay.
Common Data Link and Distributed Common Ground System
For more than a decade, the Common Data Link program has been the DOD standard for assured wideband communications of tactical intelligence data. Through technology insertion, this family of common hardware and software modules continues to serve on various airborne ISR platforms. These airborne assets are supported by an extensive distributed ground infrastructure for imagery-based intelligence exploitation known as the Distributed Common Ground System.
The Distributed Common Ground System processes U.S. and allied sensor data. It has been optimized for the Joint Task Force and is supporting operations in the Middle East. It is capable of posting intelligence reports within the ISR enterprise and is evolving to a net-centric capability.
Although the Common Data Link is employed on all airborne ISR platforms, it is not employed on space-based ISR platforms to enable tactical operations. Analysis of recent combat operations has identified a need to reduce the latency and increase the persistence of ISR data from space-based systems. The addition of the Common Data Link to military and commercial remote sensing platforms would enable real-time in-theater tasking, collaboration, collection, and dissemination by the warfighter using the existing ground infrastructure.
The U.S. Army, in partnership with the ORS Office, is helping to design, procure, and integrate the technologies and components needed to build a space-qualified Common Data Link payload for military satellites. The ORS Office is supporting design upgrades to miniaturize and space-qualify required Common Data Link components for ORS-1. Aerospace is supporting space qualification using the Berkeley cyclotron. Aerospace is also supporting Common Data Link spectrum analysis for downlink inside and outside the continental United States for ORS-1.
Common Data Link components were tested on TacSat-2 and are flying on TacSat-3, but have not yet flown for an operational mission. Improved link reliability testing of the Common Data Link components on TacSat-2 were not completed before the end of the mission. The Common Data Link is the primary means of downloading payload data from TacSat-3—and based on the first few weeks on orbit, the technology shows great promise in space.
Development Plans
The ORS Office will proceed through three phases—known as the "crawl," "walk," and "run" phases—in developing the envisioned ground system enterprise of 2015. The walk and run phases planned for the 2011–2013 and 2014–2015 timeframes will build upon lessons learned during the 2010 crawl phase and follow-on missions. During this time, the responsive ground system enterprise will also evolve to include other ORS mission areas outside of ISR. As the ORS Office continues to demonstrate responsive space capabilities and creates constellations of ORS assets, the ground system enterprise will have to achieve autonomy and synchronization of all available capabilities. The ORS Office will continue to use the ground system enterprise to refine concepts of operations and procedures for ORS assets and rapidly transition spacecraft demonstrations and prototypes to operational use.
The ORS Office conducts rapid assembly, integration, and test demonstrations using AFRL's plug-and-play spacecraft as pathfinding activities for the Rapid Response Space Works. The focus is on the space segment as well as the ground segment components end-to-end to achieve the ORS end-state vision. Here, the ground segment team is employing the flight and ground software for operations as the technicians build the spacecraft within "Chile Works." |
The Crawl Phase
In the 2010 crawl phase, the ORS Office will focus on two primary activities: the ORS-1 satellite and the JumpStart-2 initiative.
Scheduled to launch in 2010, ORS-1 was proposed in response to an operational need for ISR identified by U.S. Central Command and validated by U.S. Strategic Command. ORS-1 will be a "U-2 in space," a tactical electro-optical/infrared surveillance and reconnaissance satellite in a circular, inclined low Earth orbit. SMC's Responsive Space Squadron, part of the Space Development Group, will be executing the ORS-1 mission for the ORS Office under the direction of the DOD executive agent for space. The satellite will be operated by the Air Force under the direction of U.S. Strategic Command. It will make use of the MMSOC ground system architecture at Schriever Air Force Base and use the VMOC for payload mission planning. It will fly the first version of the space Common Data Link and also use the Distributed Common Ground System enterprise as part of its tasking and data management processes. Aerospace is actively involved in all phases of ORS-1.
JumpStart-2 is focused on equipping the Rapid Response Space Works (a.k.a. Chile Works) at Kirtland Air Force Base to build new spacecraft in response to urgent tactical or strategic needs. The ORS Office envisions a modular approach that would allow plug-and-play integration of "mission kits" consisting of proven bus and payload technologies. Ultimately, these mission kits will allow rapid assembly and integration of space-based solutions stemming from joint force commander needs. These kits will also have to take into consideration the ground aspects of fielding capabilities rapidly. The JumpStart-2 program will work toward the Tier 2 timeline for providing capability on orbit within days to weeks. To achieve this goal, key ground segment enabling capabilities will need to be determined. The ORS Office will take advantage of the GMSEC testbed created in the Aerospace Ground Systems Lab by including key functional elements of the ORS ground system enterprise, the MMSOC ground system architecture, and the VMOC. This ORS proof-of-concept demonstration will also involve building adapters between the GMSEC framework and the Air Force Research Laboratory's PnPSat (Plug-and-Play Satellite) and the Remote Intelligent Monitor System (RIMS) ground system. Additional tasks are underway to build an XML telemetric and command exchange (XTCE) interpreter for the PnPSat RIMS to further enable a compatible space enterprise. The ORS Office is also investigating the possibility of adapting an on-orbit spacecraft within the GMSEC construct. Future tasks will involve other member organizations from the compatibility committee formed after GSAW.
The Walk and Run Phases
During the walk and run phases, the ORS Office will expand the responsive ground system enterprise to include other responsive space mission areas such as communications and space situational awareness and continue to drive to a common ground architecture across the services and space organizations. The ORS Office will continue to apply existing initiatives and infrastructures from the broader DOD and space community and work with its investment partners to achieve the envisioned responsive ground system enterprise by 2015. This can be achieved by understanding warfighter needs, controlling the biggest drivers for innovation lead time, and using open innovation techniques.
Conclusion
The ORS Office recognizes that a responsive space system approach cannot be achieved without a responsive ground segment. Through its expertise in space system architecture and cross-program oversight, Aerospace is helping the ORS Office plan and implement an agile and innovative enterprise that can keep pace with changing technology and evolving user needs.
Acknowledgments
The authors thank James Barlow and Kris Woolley of The MITRE Corporation, Eric Miller of General Dynamics, Charles Warrender from the Space Development and Test Wing, and Omar Medina of the Naval Research Laboratory for their assistance in composing this article.
