Search NASA⌕ Search

SEARCH · Search NASA

Results for “Control Centers”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2

Launch Vehicle Control Center Architectures

Launch vehicles within the international community vary greatly in their configuration and processing. Each launch site has a unique processing flow based on the specific launch vehicle configuration. Launch and flight operations are managed through a set of control centers associated with each launch site. Each launch site has a control center for launch operations; however flight operations support varies from being co-located with the launch site to being shared with the space vehicle control center. There is also a nuance of some having an engineering support center which may be co-located with either the launch or flight control center, or in a separate geographical location altogether. A survey of control center architectures is presented for various launch vehicles including the NASA Space Launch System (SLS), United Launch Alliance (ULA) Atlas V and Delta IV, and the European Space Agency (ESA) Ariane 5. Each of these control center architectures shares some similarities in basic structure while differences in functional distribution also exist. The driving functions which lead to these factors are considered and a model of control center architectures is proposed which supports these commonalities and variations.

Watson, Michael D.↗

PNNL’s Building Operations Control Center

PNNL's Building Operations Control Center (BOCC) video provides an overview of the center, its capabilities, and its objectives. The BOCC was relocated to PNNL's new 3820 Systems Engineering Building in 2015. Although a key focus of the BOCC is on monitoring and improving the operations of PNNL buildings, the center's state-of-the-art computational, software and visualization resources also have provided a platform for PNNL buildings-related research projects.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Potential of Data Center Controls in Grid Services

The rapid proliferation of large data centers brings both challenges and opportunities for grid reliability. The data center resources and their potential flexibility have the potential to contribute resources to grid operations. Through capabilities like energy shifting and resource coordination, data centers can help reduce their net demand on the transmission network, as well as provide additional grid services to support reliable operation on the grid. While transient and long-term grid planning and operations are the scenarios that draw most attention, the quasi-steady state timeseries (QSTS) operation of data centers and grid bring interesting scenarios that can help evaluate the data center controls to aid grid services. This work is focused on modeling data centers for QSTS applications – incorporating the AI data center load profiles and building on the PNNL digital twin model for the thermal management loads to enable simulation studies to reveal the impact of data center controls on grid performance. This includes the integration of a QSTS battery and natural gas generator model to incorporate local resource impacts to the system. The simulation study is performed with a modified IEEE 24-Bus transmission system. Scenarios are focused on evaluating the data center load impacts on the transmission system and leveraging both data center and local generation controls to mitigate those impacts and provide additional grid services. The data center controls revealed the ability to contribute to two main kinds of grid services: preventing congestion on a weak grid by coordinating the data center resources with the collocated BESS and onsite generation; and the ability to help the grid operations during stressed times of operation like during a contingency. Leveraging these and other capabilities has the potential to help data centers become grid responsive assets, aiding in both their integration into the power system and grid reliability.

power grid simulation↗

New Mission Control Center Briefing

Live footage shows panelists, Chief Center Systems Division John Muratore, and Acting Chief, Control Center Systems Division, Linda Uljon, giving an overview of the new Mission Control Center. Muratore and Uljon talk about the changes and modernization of the new Center. The panelists mention all the new capabilities of the new Center. They emphasize the Distributed real time command and control environment, the reduction in operation costs, and even the change from coaxial cables to fiber optic cables. Uljon also tells us that the new Control Center will experience its first mission after the launch of STS-70 and its first complete mission (both launching and landing) during STS-71.

Source record↗

SAMPEX payload operation control center implementation

The Solar Anomolous and Magnetospheric Explorer (SAMPEX) satellite was launched in July 1992. It was the first in the NASA Small Explorer (SMEX) series. In building the real-time control center facility, several new mission support challenges had to be met: CCSDS telemetry and command format, 900 Kbps telemetry data, and shorter turn-around time for control center development than previous missions. The SAMPEX Payload Operations Control Ccnter (POCC) was also the first control center for a new satellite to be based on the Transportable Payload Operations Control Center (TPOCC) system architecture and methodology. This approach has both guided the implementation of the SAMPEX control center and provided some of the building blocks. By using the TPOCC architecture to build the SAMPEX POCC, the real-time operations area was miniaturized into one room, whereas previous missions needed multiple large rooms. The development cost of the SAMPEX POCC was reduced from previous missions and will provide for further cost savings in the future SMEX satellites. This paper describes the system as built and some of the enhancements in progress to create this teleoperations environment.

Mandl, Daniel↗

CPS Testbed Architectures for WAMPAC using Industrial Substation and Control Center Platforms and Attack-Defense Evaluation

Advanced persistent threats and cyberattacks can impact wide-area monitoring, protection, and control (WAMPAC) system operation. Many cyber-physical system (CPS) testbeds have been developed for attack-defense experimentation and attack-resiliency tools evaluation for WAMPAC, but they are limited to a simulation-and-emulation based environment. This paper presents a quasi-realistic CPS attack-defense testbed-based framework for WAMPAC applications using the industrial substation and control center platforms such as eTerra integrated with the hardware-in-the-loop CPS smart grid testbed available at Iowa State University. The proposed framework includes various combinations of industry-grade substation and control center platforms, communication topologies, real-time digital simulators, and a novel cyber-physical distributed intrusion-and-anomaly detection system (D-IADS) for WAMPAC applications. The D-IADS includes a master at the control center and geographically distributed sensor devices at each substation. Each D-IADS sensor deployed at a substation or control center network monitors ingress and egress traffic, detect intrusions, and dispatch alerts to the D-IADS master. The D-IADS master centrally monitors and analyze the alerts and controls D-IADS sensors. We considered an EMP60 synthetic CPS grid as a case study to demonstrate the framework and proposed D-IADS for WAMPAC applications against cyberattack vectors such as Man-in-the-Middle DNP3 attack, denial-of-service, and data-integrity attacks.

24 POWER TRANSMISSION AND DISTRIBUTION↗

SPOT4 Operational Control Center (CMP)

CNES(F) is responsible for the development of a new generation of Operational Control Center (CMP) which will operate the new heliosynchronous remote sensing satellite (SPOT4). This Operational Control Center takes large benefit from the experience of the first generation of control center and from the recent advances in computer technology and standards. The CMP is designed for operating two satellites all the same time with a reduced pool of controllers. The architecture of this CMP is simple, robust, and flexible, since it is based on powerful distributed workstations interconnected through an Ethernet LAN. The application software uses modern and formal software engineering methods, in order to improve quality and reliability, and facilitate maintenance. This software is table driven so it can be easily adapted to other operational needs. Operation tasks are automated to the maximum extent, so that it could be possible to operate the CMP automatically with very limited human interference for supervision and decision making. This paper provides an overview of the SPOTS mission and associated ground segment. It also details the CMP, its functions, and its software and hardware architecture.

Zaouche, G.↗

Beyond Control Centers

For NASA's Resource Prospector (RP) Lunar Rover Mission, we are moving away from a control center concept, to a fully distributed operation utilizing control nodes, with decision support from anywhere via mobile devices. This operations concept will utilize distributed information systems, notifications, mobile data access, and optimized mobile data display for off-console decision support. We see this concept of operations as a step in the evolution of mission operations from a central control center concept to a mission operations anywhere concept. The RP example is part of a trend, in which mission expertise for design, development and operations is distributed across countries and across the globe. Future spacecraft operations will be most cost efficient and flexible by following this distributed expertise, enabling operations from anywhere. For the RP mission we arrived at the decision to utilize a fully distributed operations team, where everyone operates from their home institution, based on evaluating the following factors: the requirement for physical proximity for near-real time command and control decisions; the cost of distributed control nodes vs. a centralized control center; the impact on training and mission preparation of flying the team to a central location. Physical proximity for operational decisions is seldom required, though certain categories of decisions, such as launch abort, or close coordination for mission or safety-critical near-real-time command and control decisions may benefit from co-location. The cost of facilities and operational infrastructure has not been found to be a driving factor for location in our studies. Mission training and preparation benefit from having all operators train and operate from home institutions.

Operations↗

System and method for transferring telemetry data between a ground station and a control center

Disclosed herein are systems, computer-implemented methods, and tangible computer-readable media for coordinating communications between a ground station, a control center, and a spacecraft. The method receives a call to a simple, unified application programmer interface implementing communications protocols related to outer space, when instruction relates to receiving a command at the control center for the ground station generate an abstract message by agreeing upon a format for each type of abstract message with the ground station and using a set of message definitions to configure the command in the agreed upon format, encode the abstract message to generate an encoded message, and transfer the encoded message to the ground station, and perform similar actions when the instruction relates to receiving a second command as a second encoded message at the ground station from the control center and when the determined instruction type relates to transmitting information to the control center.

Ray, Timothy J.↗

Common front end systems for Space Shuttle and Space Station control centers at Johnson Space Center

In the beginning of the fiscal year 1992, the development organizations of Johnson Space Center (JSC) were poised to begin two major projects: the Space Station Control Center and the refurbishment of the telemetry processing area of the Space Shuttle Mission Control Center. A study team established that a common front end concept could be used and could reduce development costs for both projects. A standard processor was defined to support most of the front end functions of both control centers and supports a consolidation of control positions which effectively reduces operations cost. This paper defines that common concept and describes the progress that has been made in development of the Consolidated Communications Facility (CCF) during the past year.

Uljon, Linda↗

Advanced technologies for Mission Control Centers

Advance technologies for Mission Control Centers are presented in the form of the viewgraphs. The following subject areas are covered: technology needs; current technology efforts at GSFC (human-machine interface development, object oriented software development, expert systems, knowledge-based software engineering environments, and high performance VLSI telemetry systems); and test beds.

Dalton, John T.↗

Development of an automated control center for the EUVE mission

The Automated Project Operations Control Center (APOCC) was developed to enable automated data acquisition, ground system management and spacecraft health and safety monitoring. The control center will be used for the Extreme Ultraviolet Explorer (EUVE) project to reduce operations staffing from three to one shift per day, while maintaining the science return and performing routine health and safety monitoring activities. The staff reduction is expected to yield a cost reduction of 250,000 dollars per year in comparison with a fully staffed, 24 hour/day operation. The APOCC infrastructure was designed to be reusable and extensible. Configurable data items are stored in data bases and spacecraft-specific information is stored in a health and safety monitoring knowledge base.

Penafiel, Catherine↗

Synergistic control center development utilizing commercial technology and industry standards

The development of the Control Center Complex (CCC), a synergistic control center supporting both the Space Station Freedom and the Space Shuttle Program, is described. To provide maximum growth and flexibility, the CCC uses commercial off-the-shelf technology and industry standards. The discussion covers the development philosophy, CCC architecture, data distribution, the software platform concept, workstation platform, commercial tools for the CCC, and benefits of synergy.

Anderson, Brian L.↗

MCCx C3I Control Center Interface Emulator

This slide presentation reviews the project to develop and demonstrate alternate Information Technologies and systems for new Mission Control Centers that will reduce the cost of facility development, maintenance and operational costs and will enable more efficient cost and effective operations concepts for ground support operations. The development of a emulator for the Control Center capability will enable the facilities to conduct the simulation requiring interactivity with the Control Center when it is off line or unavailable, and it will support testing of C3I interfaces for both command and telemetry data exchange messages (DEMs).

Mireles, James R.↗

Manned Space-laboratories Control Center (MSCC) operations concept

The initiation of the (German-) nationally funded control center for manned spaceflight operations triggered by the invitation of President Reagan to ESA, Japan, and Canada in 1984 to join the International Space Station Freedom Program is recalled. The requirements for a Manned Space-Laboratories Control Center (MSCC) as defined at the beginning of the planning and construction process in 1987 and the resulting modifications during the various programmatic scenario changes on NASA and ESA side between 1987 and now are presented. The validity of the original requirements with respect to the current scenario, which asks for a logical evolution from the execution of the D-2 mission in January 1993 via the European Columbus Precursor flights (in particular the E-1 mission) towards Columbus Attached Laboratory (APM)-operations by the end of this century are discussed. The resulting tasks of the MSCC for the various missions, the current configuration, and the ensuing operations concept leading from a more centralized concept for D-2 towards a decentralized payload operations concept for the APM and the implications with respect to European and International interfaces are presented. The planned Columbus MSCC facility architecture and its expected modifications introduced by the ESA Ministerial Conference in Munich (Nov. 1991) and follow-on discussions are briefly addressed. The last chapter outlines the planned services to be provided by the MSCC to the decentralized User (experimenter) community. Issues like decentralized mission planning on executional level, command validation, data flow coordination, archiving services, and telescience capabilities are highlighted from a MSCC point of view.

Kehr, Joachim↗

Development of Improved Graphical Displays for an Advanced Outage Control Center, Employing Human Factors Principles for Outage Schedule Management

The long-term viability of existing nuclear power plants in the United States (U.S.) is dependent upon a number of factors, including maintaining high capacity factors, maintaining nuclear safety, and reducing operating costs, particularly those associated with refueling outages. Refueling outages typically take 20-30 days, and for existing light water NPPs in the U.S., the reactor cannot be in operation during the outage. Furthermore, given that many NPPs generate between $1-1.5 million/day in revenue when in operation, there is considerable interest in shortening the length of refueling outages. Yet refueling outages are highly complex operations, involving multiple concurrent and dependent activities that are somewhat challenging to coordinate; therefore, finding ways to improve refueling outage performance, while maintaining nuclear safety has proven to be difficult. The Advanced Outage Control Center (AOCC) project is a research and development (R&D) demonstration activity under the LWRS Program. LWRS is an R&D program that works closely with industry R&D programs to establish technical foundations for the licensing and managing of long-term, safe, and economical operation of current fleet of NPPs. As such, the LWRS Advanced Outage Control Center project has the goal of improving the management of commercial NPP refueling outages. To accomplish this goal, INL is developing an advanced outage control center (OCC) that is specifically designed to maximize the usefulness of communication and collaboration technologies for outage coordination and problem resolution activities. The overall focus is on developing an AOCC with the following capabilities that enables plant and OCC staff to; Collaborate in real-time to address emergent issues; Effectively communicate outage status to all workers involved in the outage; Effectively communicate discovered conditions in the field to the OCC; Provide real-time work status; Provide automatic pending support notifications; Provide real-time requirements monitoring; Maximize their collective situational awareness to improve decision-making; and Leverage macro data to better support resource allocation. INL has partnered with several commercial NPP utilities to develop a number of advanced outage management technologies. These outage management technologies have focused on both collaborative technologies for control centers and developing mobile technologies for NPP field workers. This report describes recent efforts made in developing a suite of outage technologies to support more effective schedule management. Currently, a master outage schedule is created months in advance using the plant’s existing scheduling software (e.g., Primavera P6). Typically, during the outage, the latest version of the schedule is printed at the beginning of each shift. INL and its partners are developing technologies that will have capabilities such as Automatic Schedule Updating, Automatic Pending Support Notifications, and the ability to allocate and schedule outage support task resources on a sub-hour basis (e.g., outage Micro-Scheduling). The remaining sections of this report describe in more detail the scheduling challenges that occur during outages, how the outage scheduling technologies INL is developing helps address those challenges, and the latest developments on this task (e.g., work accomplished to date and the path forward)

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

NCC simulation model. Phase 2: Simulating the operations of the Network Control Center and NCC message manual

The network control center (NCC) provides scheduling, monitoring, and control of services to the NASA space network. The space network provides tracking and data acquisition services to many low-earth orbiting spacecraft. This report describes the second phase in the development of simulation models for the FCC. Phase one concentrated on the computer systems and interconnecting network.Phase two focuses on the implementation of the network message dialogs and the resources controlled by the NCC. Performance measures were developed along with selected indicators of the NCC's operational effectiveness.The NCC performance indicators were defined in terms of the following: (1) transfer rate, (2) network delay, (3) channel establishment time, (4) line turn around time, (5) availability, (6) reliability, (7) accuracy, (8) maintainability, and (9) security. An NCC internal and external message manual is appended to this report.

Benjamin, Norman M.↗

Operations of the reconfigured Ground Communications Facility Central Communications Terminal and the Network Operations Control Center

The ground communications facility (GCF) central communications terminal and network operations control center (NOCC) hardware was rearranged, supplemented, and modified, and software programs changed to provide an improved GCF and NOCC operational environment and capability. Control center operations section activities required to make the changeover from the old to the new GCF and NOCC configuration are addressed.

Santana, J. C.↗