Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “integrated planning and scheduling”

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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

The Fluids Integrated Rack and Light Microscopy Module Integrated Capabilities

The Fluids Integrated Rack (FIR), a facility class payload, and the Light Microscopy Module (LMM), a subrack payload, are scheduled to be launched in 2005. The LMM integrated into the FIR will provide a unique platform for conducting fluids and biological experiments on ISS. The FIR is a modular, multi-user scientific research facility that will fly in the U.S. laboratory module, Destiny, of the International Space Station (ISS). The first payload in the FIR will be the Light Microscopy Module (LMM). The LMM is planned as a remotely controllable, automated, on-orbit microscope subrack facility, allowing flexible scheduling and control of fluids and biology experiments within the FIR. Key diagnostic capabilities for meeting science requirements include video microscopy to observe microscopic phenomena and dynamic interactions, interferometry to make thin film measurements with nanometer resolution, laser tweezers for particle manipulation, confocal microscopy to provide enhanced three-dimensional visualization of structures, and spectrophotometry to measure photonic properties of materials. The LMM also provides experiment sample containment for frangibles and fluids. This paper will provide a description of the current FIR and LMM designs, planned capabilities and key features. In addition a brief description of the initial five experiments planned for LMM/FIR will be provided.

Motil, Susan M.↗
DOE OSTI2020

Waste Management Project Success - Regulatory Assurance Systems - 20118

Waste management (WM) and remediation projects are essential within a restorative environmental culture. Despite years of experience, challenges and obstacles associated with efficient and effective WM project execution remain. Although some obstacles are project specific, a common challenge is navigating the regulatory landscape from planning through execution, particularly with first of a kind (FOAK) and first in a while (FIAW) projects. The absence of a comprehensive regulatory assurance strategy places significant hurdles in the path of project success. To clear a path for the successful execution of increasingly complex WM projects, this paper focuses on development of a comprehensive regulatory assurance strategy and implementation plan that effectively engages stakeholders, agencies, and performers to produce project plans that fully and cost effectively integrate applicable regulatory requirements. The most reliable way to align regulatory processes and decisions needed for mission success is through a regulatory assurance system. This system establishes a healthy interface with regulatory decision makers, to work in a collaborative manner, to create a common vision for regulatory decisions on an agreed upon schedule. A regulatory assurance system consists of several elements. Although the mission may vary from cleanup to site closure to nuclear component production, the elements of a regulatory assurance system remain essentially constant and must include: 1) identifying a common vision or end state, 2) developing a long-term, integrated strategy and schedule, 3) establishing a regulatory partnering team consisting of key decision-makers, 4) regular and frequent communication with decision-makers, 5) ensuring consistent surveillance for early identification of issues and changes that may impact the project, 6) quick resolution of emerging issues to prevent schedule impact, 7) identifying core compliance functions, 8) periodically assessing progress of the project as it relates to regulatory assurance and, 9) providing constructive feedback to improve the process. A regulatory assurance system provides a living, multi-faceted approach to planning, visioning, communicating and tracking to avoid surprises and ensure smooth and timely progress to the project. The overall success measures will be whether the system produces common sense regulatory decisions supporting the vision on time without appeal. Effective regulatory frameworks rarely happen on their own. Balanced, common-sense regulatory decisions stem from teams that are trained to work together to achieve shared goals. In this paper, particular attention is placed on the importance of starting with a shared vision for a regulatory assurance and execution strategy that leverages experience to establish optimal approaches. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS1997

Thermal System Upgrade of the Space Environment Simulation Test Chamber

The paper deals with the refurbishing and upgrade of the thermal system for the existing thermal vacuum test facility, the Space Environment Simulator, at NASA's Goddard Space Flight Center. The chamber is the largest such facility at the center. This upgrade is the third phase of the long range upgrade of the chamber that has been underway for last few years. The first phase dealt with its vacuum system, the second phase involved the GHe subsystem. The paper describes the considerations of design philosophy options for the thermal system; approaches taken and methodology applied, in the evaluation of the remaining "life" in the chamber shrouds and related equipment by conducting special tests and studies; feasibility and extent of automation, using computer interfaces and Programmable Logic Controllers in the control system and finally, matching the old components to the new ones into an integrated, highly reliable and cost effective thermal system for the facility. This is a multi-year project just started and the paper deals mainly with the plans and approaches to implement the project successfully within schedule and costs.

Desai, Ashok B.↗
NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗
DOE OSTI2021

G3P3 Phase 3 Project Execution Plan. Issue 1

The National Solar Thermal Test Facility (NSTTF) at Sandia National Laboratories New Mexico (SNL/NM) developed this Project Execution Plan (PEP) to document its process for executing, monitoring, controlling and closing-out Phase 3 of the Gen 3 Particle Pilot Plant G3P3. This plan serves as a resource for stakeholders who wish to be knowledgeable of project objectives and how they will be accomplished. The plan is intended to be used by the development partners, principal investigator, and the federal project director. Project objectives are derived from the mission needs statement, and an integrated project team assists in development of the PEP. This plan is a living document and will be updated throughout the project to describe current and future processes and procedures. The scope of the PEP covers: Cost, schedule, and scope Project reporting Staffing plan Quality assurance plan Environment, safety, security, and health This document is a tailored approach for the Facilities Management and Operations Center (FMOC) to meet the project management principles of DOE Order 413.3B, Program and Project Management for the Acquisition of Capital Assets , and DOE G 413.3-15, DOE Guide for Project Execution Plans. This document will elaborate on content as knowledge of the project is gained or refined.

14 SOLAR ENERGY↗
NASA NTRSDate not supplied

Surface Systems Capability Gaps for Enabling NASA’s Sustainable Lunar Operations

This paper discusses the NASA Ground, Test, and Surface Systems Taxonomy (TX-13) related capability gaps, including details of architecture, technology, engineering, and policy gaps for enabling sustainable lunar surface operations and subsequent Mars missions. Architecture gaps include standardized architectures and interfaces, multi-element systems engineering and integration, design for supportability, and nuclear payload processing and launch approach. Technology gaps, primarily focused on uncrewed surface operations, include automated/autonomous cryogenic loading, transfer, servicing, and storage of commodities; health determination and fault management; automated/autonomous planning and scheduling; automated/autonomous inspection, maintenance and repair; logistics management and reliability; launch and landing site preparation; commodity management; and advanced umbilicals and dust tolerant interfaces. Engineering gaps include high-purity propellant production for ground and surface applications and large-scale xenon servicing capabilities. The policy gap includes nuclear propulsion acceptance testing and qualification approach. Strategically identifying human/automation roles and tasks and infusing automation and autonomy practices early in a system’s lifecycle is essential for achieving the mission objectives for a sustainable human lunar presence, improving performance and mission effectiveness, reducing operations costs and reliance on humans to perform tasks, and accommodating ground communication delays.

Surface Systems↗
NASA NTRS1977

Statement of Chester M. Lee, Director, Space Transportation Systems Operations, NASA, and Phillip E. Culbertson, Assistant Administrator of Planning and Program Integration, NASA

Payloads for the Space Transportation System 560 flights, particularly the NASA payloads, are discussed. NASA payloads will make up approximately 50% of total payloads in these flights. Proposed Spacelab experiments are listed and discussed; plans for accommodating commercial user payloads are then outlined, including price schedules.

Source record↗
NASA NTRS1981

Space Transportation System Cargo projects: inertial stage/spacecraft integration plan. Volume 1: Management plan

The Kennedy Space Center (KSC) Management System for the Inertial Upper Stage (IUS) - spacecraft processing from KSC arrival through launch is described. The roles and responsibilities of the agencies and test team organizations involved in IUS-S/C processing at KSC for non-Department of Defense missions are described. Working relationships are defined with respect to documentation preparation, coordination and approval, schedule development and maintenance, test conduct and control, configuration management, quality control and safety. The policy regarding the use of spacecraft contractor test procedures, IUS contractor detailed operating procedures and KSC operations and maintenance instructions is defined. Review and approval requirements for each documentation system are described.

Source record↗
NASA NTRS1999

Virtual Build: Low-Tech Simulations Can Be High on IPPD Content

After two years of design, component testing, and parts fabrication, the project team was within months of starting assembly on the first major elements of a new product assembly. Schedules were extremely tight and there was no room for error in the first unit build-up for test. The first draft of the assembly drawing was nearing completion and needed to be approved by key members of the Integrated Product Team (IPT) before release. Only then could the manufacturing planning be finalized and released for assembly to begin. What could we do to improve the quality of our first build effort? How could we minimize all the changes inherent in the first-time build of a complex mechanical system? Why not a dress rehearsal of the build process with all the participating players, hardware, and build documentation? A "virtual build simulation". In an organization employing integrated product teams there is no substitute for clear communication between the various cross-functional members. Despite team collocation, integrated solid modeling, and frequent coordination meetings. elements of the product-process design can still slip through the cracks and show up on the assembly floor. The virtual build exercise was designed to provide one intensive hands-on experience for all members of the design and assembly team in time to make corrections without schedule impact.

Hilscher, Rick↗
NASA NTRS1999

Lightning Mapper Sensor Lens Assembly S.O. 5459: Project Management Plan

Kaiser Electro-Optics, Inc. (KEO) has developed this Project Management Plan for the Lightning Mapper Sensor (LMS) program. KEO has integrated a team of experts in a structured program management organization to meet the needs of the LMS program. The project plan discusses KEO's approach to critical program elements including Program Management, Quality Assurance, Configuration Management, and Schedule.

Zeidler, Janet↗
NASA NTRS2001

Variable Radius Nacelle Studies

An overview of the active shape control for a variable radius nacelle leading edge program is presented. The current technical plan and schedule will be discussed. Results from the structural shape change of curved plates demonstration will be presented, as well as the NASA LaRC concept for a variable radius nacelle leading edge. Results of a Boeing systems integration study of this concept will be discussed briefly. The status of the sensors, actuators, and computational design tools tasks will also be presented.

McGowan, David M.↗
NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗
DOE OSTI2024

Hydropower Flexibility and Environmental Tradeoffs Analysis

The importance of hydropower increases as the power grid evolves with the higher variable renewable contribution. As conventional thermal power plants are retired, the importance of hydropower contribution increases to balance the variability of solar and wind generation. However, reservoir water resources are constrained by multiple constraints, and variability of water inflow to the reservoirs creates limitations to dam water releases for power grid needs. Coordinating multiple tools, including water resources, ecological, and technical and economic power grid modeling, informs dam water releases. The case study, the Columbia River Basin multipurpose reservoir project, is operated for hydropower production and many other purposes considering the aquatic habitat of the river basin. Specifically, the river basin fish population is a vital element for the tribal community of the river basin. We integrated a production cost model, a water resource model, and decades of tribal knowledge to analyze the fish-friendly way of operating Columbia hydropower scheduling and grid impacts. We measure power grid impacts for various water resources planning scenarios in terms of total system operating cost, system reliability indicators, changes in wind and solar generation and curtailments, local marginal prices, and revenue for hydropower producers. The study results inform reservoir operating rules decisions from hydropower power producers, system operators, other water users, tribes, environmentalists, and other stakeholders.

Columbia River↗
NASA NTRS2015

System-Level Experimental Validations for Supersonic Commercial Transport Aircraft Entering Service in the 2018-2020 Time Period

This report describes the work conducted under NASA funding for the Boeing N+2 Supersonic Experimental Validation project to experimentally validate the conceptual design of a supersonic airliner feasible for entry into service in the 2018 -to 2020 timeframe (NASA N+2 generation). The primary goal of the project was to develop a low-boom configuration optimized for minimum sonic boom signature (65 to 70 PLdB). This was a very aggressive goal that could be achieved only through integrated multidisciplinary optimization tools validated in relevant ground and, later, flight environments. The project was split into two phases. Phase I of the project covered the detailed aerodynamic design of a low boom airliner as well as the wind tunnel tests to validate that design (ref. 1). This report covers Phase II of the project, which continued the design methodology development of Phase I with a focus on the propulsion integration aspects as well as the testing involved to validate those designs. One of the major airplane configuration features of the Boeing N+2 low boom design was the overwing nacelle. The location of the nacelle allowed for a minimal effect on the boom signature, however, it added a level of difficulty to designing an inlet with acceptable performance in the overwing flow field. Using the Phase I work as the starting point, the goals of the Phase 2 project were to design and verify inlet performance while maintaining a low-boom signature. The Phase II project was successful in meeting all contract objectives. New modular nacelles were built for the larger Performance Model along with a propulsion rig with an electrically-actuated mass flow plug. Two new mounting struts were built for the smaller Boom Model, along with new nacelles. Propulsion integration testing was performed using an instrumented fan face and a mass flow plug, while boom signatures were measured using a wall-mounted pressure rail. A side study of testing in different wind tunnels was completed as a precursor to the selection of the facilities used for validation testing. As facility schedules allowed, the propulsion testing was done at the NASA Glenn Research Center (GRC) 8 x 6-Foot wind tunnel, while boom and force testing was done at the NASA Ames Research Center (ARC) 9 x 7-Foot wind tunnel. During boom testing, a live balance was used for gathering force data. This report is broken down into nine sections. The first technical section (Section 2) covers the general scope of the Phase II activities, goals, a description of the design and testing efforts, and the project plan and schedule. Section 3 covers the details of the propulsion system concepts and design evolution. A series of short tests to evaluate the suitability of different wind tunnels for boom, propulsion, and force testing was also performed under the Phase 2 effort, with the results covered in Section 4. The propulsion integration testing is covered in Section 5 and the boom and force testing in Section 6. CFD comparisons and analyses are included in Section 7. Section 8 includes the conclusions and lessons learned.

Magee, Todd E.↗
NASA NTRS1992

Operationally efficient propulsion system study (OEPSS) data book: Preliminary Development Plan for an Integrated Booster Propulsion Module (BPM) - Volume 9

A preliminary development plan for an integrated propulsion module (IPM) is described. The IPM, similar to the Space Transportation Main engine (STME) engine, is applicable to the Advanced Launch System (ALS) baseline vehicle. The same STME development program ground rules and time schedule were assumed for the IPM. However, the unique advantages of testing an integrated engine element, in terms of reduced number of hardware and number of system and reliability tests, compared to single standalone engine and MPTA, are highlighted. The potential ability of the IPM to meet the ALS program goals for robustness, operability and reliability is emphasized.

DiBlasi, Angelo G.↗
NASA NTRS2006

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗
DOE OSTI2020

Harvesting the low-hanging fruit of high energy savings -- Virtual Occupancy using Wi-Fi Data

Approximately 20% of primary energy consumed in the U.S. is attributed to HVAC use. Ideally, HVAC operation would be driven by actual building occupancy, but lack of reliable occupancy information often results in the use of conservative static schedules. This disparity is even more pronounced in a college campus, where the function of each space differs by building (classrooms, offices, libraries) and the class schedules change frequently -- every semester, day of week, and hour. While several research papers propose the use of counts of the Wi-Fi connections (e.g., phones, computers) as a proxy for occupancy, few real-world implementations exist. This paper describes the development and deployment of an open-source Wi-Fi-to-Occupancy software library in 65 buildings of a college campus, and the planned integration with the building energy management and control system at the building scale. Over a year of Wi-Fi data was gathered into distinct academic periods, including fall and spring semester, academic breaks, and summer sessions. Patterns such as students moving between classrooms, closing laptops before exams, etc., can be visualized from the data. Approximating occupancy from Wi-Fi data presents challenges which we address in this project -- for example, identifying static devices, or estimating the ratio of devices per person. Utilizing real-time occupancy data to inform optimal HVAC schedules and ventilation rates creates the potential to identify and reduce energy waste. Other potential applications include forecasting occupancy, and using Wi-Fi data to predict peak demands. Finally, the paper discusses how to easily scale these tools to other buildings.

Pritoni, Marco↗
NASA NTRS1994

Mission Operations Centers (MOCs): Integrating key spacecraft ground data system components

In an environment characterized by decreasing budgets, limited system development time, and user needs for increased capabilities, the Mission Operations Division (MOD) at the National Aeronautics and Space Administration Goddard Space Flight Center initiated a new, cost-effective concept in developing its spacecraft ground data systems: the Mission Operations Center (MOC). In the MOC approach, key components are integrated into a comprehensive and cohesive spacecraft planning, monitoring, command, and control system with a single, state-of-the-art graphical user interface. The MOD is currently implementing MOC's, which feature a common, reusable, and extendable system architecture, to support the X-Ray Timing Explorer (XTE), Tropical Rainfall Measuring Mission (TRMM), and Advanced Composition Explorer (ACE) missions. As a result of the MOC approach, mission operations are integrated, and users can, with a single system, perform real-time health and safety monitoring, real-time command and control, real-time attitude processing, real-time and predictive graphical spacecraft monitoring, trend analysis, mission planning and scheduling, command generation and management, network scheduling, guide star selection, and (using an expert system) spacecraft monitoring and fault isolation. The MOD is also implementing its test and training simulators under the new MOC management structure. This paper describes the MOC concept, the management approaches used in developing MOC systems, the technologies employed and the development process improvement initiatives applied in implementing MOC systems, and the expected benefits to both the user and the mission project in using the MOC approach.

Harbaugh, Randy↗