Search NASA⌕ Search

SEARCH · Search NASA

Results for “staffing”

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 181 records · Page 10

EDOS operations concept and development approach

The Earth Observing System (EOS) Data and Operations System (EDOS) is being developed by the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) for the capture, level zero processing, distribution, and backup archiving of high speed telemetry data received from EOS spacecraft. All data received will conform to the Consultative Committee for Space Data Standards (CCSDS) recommendations. The major EDOS goals are to: (1) minimize EOS program costs to implement and operate EDOS; (2) respond effectively to EOS growth requirements; and (3) maintain compatibility with existing and enhanced versions of NASA institutional systems required to support EOS spacecraft. In order to meet these goals, the following objectives have been defined for EDOS: (1) standardize EDOS interfaces to maximize utility for future requirements; (2) emphasize life-cycle cost (LCC) considerations (rather than procurement costs) in making design decisions and meeting reliability, maintainability, availability (RMA) and upgradability requirements; (3) implement data-driven operations to the maximum extent possible to minimize staffing requirements and to maximize system responsiveness; (4) provide a system capable of simultaneously supporting multiple spacecraft, each in different phases of their life-cycles; (5) provide for technology insertion features to accommodate growth and future LCC reductions during the operations phase; and (6) provide a system that is sufficiently robust to accommodate incremental performance upgrades while supporting operations. Operations concept working group meetings were facilitated to help develop the EDOS operations concept. This provided a cohesive concept that met with approval of responsible personnel from the start. This approach not only speeded up the development process by reducing review cycles, it also provided a medium for generating good ideas that were immediately molded into feasible concepts. The operations concept was then used as a basis for the EDOS specification. When it was felt that concept elements did not support detailed requirements, the facilitator process was used to resolve discrepancies or to add new concept elements to support the specification. This method provided an ongoing revisal of the operations concept and prevented large revisions at the end of the requirement analysis phase of system development.

Knoble, G.↗

Building a COTS archive for satellite data

The goal of the NOAA/NESDIS Active Archive was to provide a method of access to an online archive of satellite data. The archive had to manage and store the data, let users interrogate the archive, and allow users to retrieve data from the archive. Practical issues of the system design such as implementation time, cost and operational support were examined in addition to the technical issues. There was a fixed window of opportunity to create an operational system, along with budget and staffing constraints. Therefore, the technical solution had to be designed and implemented subject to constraint imposed by the practical issues. The NOAA/NESDIS Active Archive came online in July of 1994, meeting all of its original objectives.

Singer, Ken↗

Flight dynamics software in a distributed network environment

As with all NASA facilities, the announcement of reduced budgets, reduced staffing, and the desire to implement smaller/quicker/cheaper missions has required the Agency's organizations to become more efficient in what they do. To accomplish these objectives, the FDD has initiated the development of the Flight Dynamics Distributed System (FDDS). The underlying philosophy of FDDS is to build an integrated system that breaks down the traditional barriers of attitude, mission planning, and navigation support software to provide a uniform approach to flight dynamics applications. Through the application of open systems concepts and state-of-the-art technologies, including object-oriented specification concepts, object-oriented software, and common user interface, communications, data management, and executive services, the FDD will reengineer most of its six million lines of code.

Jeletic, J.↗

Training augmentation device for the Air Force satellite Control Network

From the 1960's and into the early 1980's satellite operations and control were conducted by Air Force Systems Command (AFSC), now Air Force Materiel Command (AFMC), out of the Satellite Control Facility at Onizuka AFB, CA. AFSC was responsible for acquiring satellite command and control systems and conducting routine satellite operations. The daily operations, consisting of satellite health and status contacts and station keeping activities, were performed for AFSC by a Mission Control Team (MCT) staffed by civilian contractors who were responsible for providing their own technically 'qualified' personnel as satellite operators. An MCT consists of five positions: mission planner, ground controller, planner analyst, orbit analyst, and ranger controller. Most of the training consisted of On-the-Job-Training (OJT) with junior personnel apprenticed to senior personnel until they could demonstrate job proficiency. With most of the satellite operators having 15 to 25 years of experience, there was minimal risk to the mission. In the mid 1980's Air Force Space Command (AFSPACOM) assumed operational responsibility for a newly established control node at Falcon AFB (FAFB) in CO. The satellites and ground system program offices (SPO's) are organized under AFSC's Space and Missiles Systems Center (SMC) to function as a systems engineering and acquisition agency for AFSPACECOM. The collection of the satellite control nodes, ground tracking stations, computer processing equipment, and connecting communications links is referred to as the Air Force Satellite Control Network (AFSCN).

Shoates, Keith B.↗

Operations engineering: Applying hands-on experience to the development process

The concepts behind operations engineering as applied to the requirements, design, development and testing of data processing systems are presented, together with the associated benefits. The objective of operations engineering is to reduce the overall life cycle costs by integrating operations experience with the development process. To achieve this goal, operations engineering seeks to reduce the development costs by that assuring operational requirements are incorporated into the design and development process as early as possible, and reduce the operational costs by decreasing operations staffing requirements and other related costs through improved system capabilities. The areas for improved system capabilities include: system recovery; data recovery; fault isolation; system operability; system flexibility; system automation; and system reporting. It is described how operations engineering is integrated with the development process, and the difficulties and misconceptions experienced in using operations engineering are discussed.

Alcott, Gary↗

User participation in the development of the human/computer interface for control centers

Technological advances coupled with the requirements to reduce operations staffing costs led to the demand for efficient, technologically-sophisticated mission operations control centers. The control center under development for the earth observing system (EOS) is considered. The users are involved in the development of a control center in order to ensure that it is cost-efficient and flexible. A number of measures were implemented in the EOS program in order to encourage user involvement in the area of human-computer interface development. The following user participation exercises carried out in relation to the system analysis and design are described: the shadow participation of the programmers during a day of operations; the flight operations personnel interviews; and the analysis of the flight operations team tasks. The user participation in the interface prototype development, the prototype evaluation, and the system implementation are reported on. The involvement of the users early in the development process enables the requirements to be better understood and the cost to be reduced.

Broome, Richard↗

X-33 Phase 2

In response to Clause 17 of the Cooperative Agreement NCC8-115, Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. Contract award was announced on July 2, 1996 and the first milestone was hand delivered to NASA MSFC on July 17, 1996. The first year has been one of growth and progress as all team members staffed up and embarked on the technical adventure of the 20th century... the ultimate goal . . a Single Stage to Orbit (SSTO) Reuseable Launch Vehicle (RLV).

Source record↗

Aerospace Safety Advisory Panel

During 1997, the Aerospace Safety Advisory Panel (ASAP) continued its safety reviews of NASA's human space flight and aeronautics programs. Efforts were focused on those areas that the Panel believed held the greatest potential to impact safety. Continuing safe Space Shuttle operations and progress in the manufacture and testing of primary components for the International Space Station (ISS) were noteworthy. The Panel has continued to monitor the safety implications of the transition of Space Shuttle operations to the United Space Alliance (USA). One area being watched closely relates to the staffing levels and skill mix in both NASA and USA. Therefore, a section of this report is devoted to personnel and other related issues that are a result of this change in NASA's way of doing business for the Space Shuttle. Attention will continue to be paid to this important topic in subsequent reports. Even though the Panel's activities for 1997 were extensive, fewer specific recommendations were formulated than has been the case in recent years. This is indicative of the current generally good state of safety of NASA programs. The Panel does, however, have several longer term concerns that have yet to develop to the level of a specific recommendation. These are covered in the introductory material for each topic area in Section 11. In another departure from past submissions, this report does not contain individual findings and recommendations for the aeronautics programs. While the Panel devoted its usual efforts to examining NASA's aeronautic centers and programs, no specific recommendations were identified for inclusion in this report. In lieu of recommendations, a summary of the Panel's observations of NASA's safety efforts in aeronautics and future Panel areas of emphasis is provided. With profound sadness the Panel notes the passing of our Chairman, Paul M. Johnstone, on December 17, 1997, and our Staff Assistant, Ms. Patricia M. Harman, on October 5, 1997. Other changes to the Panel composition during the past year were: the resignation of Mr. Dennis E. Fitch as a Consultant; the appointment of Mr. Roger D. Schaufele as a Consultant; and the assignment of Ms. Susan M. Smith as Staff Assistant.

Source record↗

Data Quality Assessment Methods for the Eastern Range 915 MHz Wind Profiler Network

The Eastern Range installed a network of five 915 MHz Doppler Radar Wind Profilers with Radio Acoustic Sounding Systems in the Cape Canaveral Air Station/Kennedy Space Center area to provide three-dimensional wind speed and direction and virtual temperature estimates in the boundary layer. The Applied Meteorology Unit, staffed by ENSCO, Inc., was tasked by the 45th Weather Squadron, the Spaceflight Meteorology Group, and the National Weather Service in Melbourne, Florida to investigate methods which will help forecasters assess profiler network data quality when developing forecasts and warnings for critical ground, launch and landing operations. Four routines were evaluated in this study: a consensus time period check a precipitation contamination check, a median filter, and the Weber-Wuertz (WW) algorithm. No routine was able to effectively flag suspect data when used by itself. Therefore, the routines were used in different combinations. An evaluation of all possible combinations revealed two that provided the best results. The precipitation contamination and consensus time routines were used in both combinations. The median filter or WW was used as the final routine in the combinations to flag all other suspect data points.

Lambert, Winifred C.↗

Profile of Ambulance Runs at the Kennedy Space Center

The Kennedy Space Center (KSC) has four onsite ambulances staffed with Paramedics at two fire stations that respond to 911 Emergency Medical System (EMS) medical dispatches. These ambulances serve over 22,000 NASA, military, government, and contractor employees in an area of approximately 520 square miles. Included in this coverage are several public areas such as beaches, a wildlife refuge and a popular Visitor Center. Reports are filled out on each patient encountered. However. the only element tracked has been the ambulance response time. Now that reports are filed electronically, it is possible to enter them into an electronic database for analysis. Data analyses reveal trends and assist in better allocation of resources.

Scarpa, Philip J.↗

CDDIS Data Center Summary

This report summarizes the current and future plans of the Crustal Dynamics Data Information System (CDDIS) with respect to the International VLBI Service for Geodesy and Astrometry (IVS). Included are background information about the CDDIS, the computer architecture, staffing supporting the system, archive contents, and future plans for the CDDIS within the IVS.

Noll, Carey↗

New Human-Computer Interface Concepts for Mission Operations

The current climate of budget cuts has forced the space mission operations community to reconsider how it does business. Gone are the days of building one-of-kind control centers with teams of controllers working in shifts 24 hours per day, 7 days per week. Increasingly, automation is used to significantly reduce staffing needs. In some cases, missions are moving towards lights-out operations where the ground system is run semi-autonomously. On-call operators are brought in only to resolve anomalies. Some operations concepts also call for smaller operations teams to manage an entire family of spacecraft. In the not too distant future, a skeleton crew of full-time general knowledge operators will oversee the operations of large constellations of small spacecraft, while geographically distributed specialists will be assigned to emergency response teams based on their expertise. As the operations paradigms change, so too must the tools to support the mission operations team's tasks. Tools need to be built not only to automate routine tasks, but also to communicate varying types of information to the part-time, generalist, or on-call operators and specialists more effectively. Thus, the proper design of a system's user-system interface (USI) becomes even more importance than before. Also, because the users will be accessing these systems from various locations (e.g., control center, home, on the road) via different devices with varying display capabilities (e.g., workstations, home PCs, PDAS, pagers) over connections with various bandwidths (e.g., dial-up 56k, wireless 9.6k), the same software must have different USIs to support the different types of users, their equipment, and their environments. In other words, the software must now adapt to the needs of the users! This paper will focus on the needs and the challenges of designing USIs for mission operations. After providing a general discussion of these challenges, the paper will focus on the current efforts of creatin(y an effective USI for one specific suite of tools, SERS (The Spacecraft Emergency Response System), which has been built to enable lights-out operations. SERS is a Web-based collaborative environment that enables secure distributed fault management.

Fox, Jeffrey A.↗

The MAP Autonomous Mission Control System

The Microwave Anisotropy Probe (MAP) mission is the second mission in NASA's Office of Space Science low-cost, Medium-class Explorers (MIDEX) program. The Explorers Program is designed to accomplish frequent, low cost, high quality space science investigations utilizing innovative, streamlined, efficient management, design and operations approaches. The MAP spacecraft will produce an accurate full-sky map of the cosmic microwave background temperature fluctuations with high sensitivity and angular resolution. The MAP spacecraft is planned for launch in early 2001, and will be staffed by only single-shift operations. During the rest of the time the spacecraft must be operated autonomously, with personnel available only on an on-call basis. Four (4) innovations will work cooperatively to enable a significant reduction in operations costs for the MAP spacecraft. First, the use of a common ground system for Spacecraft Integration and Test (I&T) as well as Operations. Second, the use of Finite State Modeling for intelligent autonomy. Third, the integration of a graphical planning engine to drive the autonomous systems without an intermediate manual step. And fourth, the ability for distributed operations via Web and pager access.

Breed, Juile↗

CDDIS Report

The Crustal Dynamics Data Information System (CDDIS) has supported the archive and distribution of laser ranging data (both lunar and satellite) since its inception in 1982. This report summarizes the current and future plans of the CDDIS with respect to the International Laser Ranging Service (ILRS). Included here is background information about the CDDIS, its computer architecture, staffing, and archive contents, as well as future plans for the system within the ILRS.

Noll, Carey↗

CDDIS Data Center Report

This report summarizes activities for the year 2000 and future plans of the Crustal Dynamics Data Information System (CDDIS) with respect to the International Very Long Base Interferometry (VLBI) Service for Geodesy and Astrometry (IVS). Included in this report are background information about the CDDIS, the computer architecture, staffing supporting the system, archive contents, and future plans for the CDDIS within the IVS.

Noll, Carey E.↗

Satellite Ground Operations Automation: Lessons Learned and Future Approaches

Reducing spacecraft ground system operations costs is a major goal in all missions. The Fast Auroral Snapshot (FAST) flight operations team at the NASA/Goddard Spacecraft Flight Center developed in-house scripts and procedures to automate monitoring of critical spacecraft functions. The initial staffing profile of 16x7 was reduced first to 8x5 and then to 'lights out'. Operations functions became an offline review of system performance and the generation of future science plans for subsequent upload to the spacecraft. Lessons learned will be applied to the challenging Triana mission, where 24x7 contact with the spacecraft will be necessary at all times.

Catena, John↗

Goddard Earth Sciences and Technology Center (GEST)

This document summarizes the activities of the Goddard Earth Sciences and Technology Center (GEST), a consortium of scientists and engineers led by the University of Maryland, Baltimore County (UMBC), during the contract reporting period. Topics covered include: new programs, eligibility and selection criteria, Goddard Coastal Research Graduate Fellowship Program and staffing changes.

Source record↗

Advanced Thermal Emission Imaging Systems Definition and Development

Santa Barbara Remote Sensing (SBRS), Raytheon Company, is pleased to submit this quarterly progress report of the work performed in the third quarter of Year 2 of the Advanced THEMIS Project, July through September 2002. We review here progress in the proposed tasks. During July through September 2002 progress was made in two major tasks, Spectral Response Characterization and Flight Instrument Definition. Because of staffing problems and technical problems earlier in the program we have refocused the remaining time and budget on the key technical tasks. Current technical problems with a central piece of test equipment has lead us to request a 1 quarter extension to the period of performance. This request is being made through a separate letter independent of this report.

Blasius, Karl↗