Context Based Configuration Management System

information technology and software
Context Based Configuration Management System (TOP2-176)
A hybrid tool-suite for distributed strategic planning and decision making
Overview
NASA has developed a new technology to track the status of, and changes to, enterprise level programmatic operations. Enterprise decision making and operations rely on management of non-traditional configuration management (CM) components like estimates, agreements, goals, policies, etc. Additionally, enterprise operations have unique and diverse contexts/ environments such as reviews, workshops, fire drills, Office of Management and Budget (OMB) and Congressional actions, procurements, etc. NASA's innovation Context-Based Configuration Management (CBCM) system integrates decision history and decision-map systems to commercial configuration management systems, and adds intelligence and Knowledge Management (KM) to the CM components to improve enterprise-level assessments and forecasting. This web-based interactivity allows significant and unobtrusive communications and context enhancements.

The Technology
Context Based Configuration Management (CBCM) is a hybrid tool-suite that directly supports the dynamic, distributed strategic planning and decision making environment. The CBCM system marries Decision Map technology with Commercial Off-the-Shelf (COTS) configuration management work flow (Xerox Docushare), embedded component models (events models, configuration item models, and feedback models) all on top of a web based online collaboration technology (e.g., NASA/Xerox Netmark middleware engine). CBCM drives an enterprise management configuration system with built-in analysis functions, tightly interoperable with other enterprise management systems (through middleware connections) that deliver integrated reports and enable enterprise-wide inputs on decisions/actions/events, and present context-based query-driven views on configuration management information. The theory of operation flows from the most senior level of decision making and creates a master Configuration Decision Map. This map track events, configuration objects, and contexts. Additional Configuration Decision Maps can be created independently and/or as a result of the Master Configuration Decision Map by successive organizations and/or individuals in the entire enterprise. The integrated icon-objects have intelligent triggers embedded within them configurable by the users to provide automatic analysis, forecasts, and reports. All information is stored in an object-relational database that provides robust query and reporting tools to help analyze and support past and current decisions as well as track the enterprise baseline and future potential vectors.
Big Data Analysis Logistics Management
Benefits
  • Improves enterprise level assessment and forecasting
  • Automatic analysis, forecasts, and reports
  • Robust query and reporting tools
  • Analyzes and supports past and current decisions
  • Tracks the enterprise baseline and future potential vectors
  • User friendly GUI interface
  • Customized icons/object libraries and configurable KM
  • Easy to deploy and maintain
  • Middleware connections to other enterprise systems
  • Multi-dimensional linking of hierarchy

Applications
  • Large organizations with distributive operations, and complex product deliverables
  • Budgeting program/Project management
  • Risk Management
  • Configuration management
  • Schedule Management
Technology Details

information technology and software
TOP2-176
ARC-15312-1
7,672,969
Similar Results
Centralized Data Management Platform
The technology is an adaptive data management and integration platform designed for disparate data sources. It is built to support multitenancy, manage data governance, handle heterogeneous data formats and advance data democratization using a suite of connected, independent microservices. Each service can be used within an integrated environment, or as a standalone product, with a dedicated set of functionalities, such as metadata management, data versioning, access control, data tagging, link management, and analytics, among others. The platform includes APIs to query, navigate and analyze complex interconnections between data assets. The invention provides the capability to capture and manage domain knowledge as a graph schema. The microservices architecture provides services for data tagging, managing data ownership, managing data relationships by dynamically associating data assets based on their content, metadata cataloging and handling, data discovery by searching data across domains ingested from various data sources, while tracking the datas lineage and provenance, and product lifecycle that data assets belong to. Such data management can integrate heterogeneous datasets, facilitating cross-domain Metadata Management Services (MMS), identifying and limiting unconnected data sources and other fragmented data, as well as reducing redundant data sources.
Schedule of flight departure
Flight Awareness Collaboration Tool (FACT)
The Flight Awareness Collaboration Tool (FACT) user interface is a quad design with four areas. The Primary Map View shows the US with several traffic and weather overlays. The Surface Map View displays the selected airport with information on runway conditions and other factors. The Information View has specific data from various sources about the area of interest. This view also has a built-in algorithm that predicts the impact of the forecast winter weather on airport capacity. The Communication View supports messaging within the geographically-dispersed team that is using FACT. When an airport is selected in the Primary Map View, the information presented in the Surface Map and Information Views is focused on that choice. FACT is a web-based application using Node.js and MongoDB. It receives Java messages from the Federal Aviation Administration System Wide Information Management (SWIM) data repository. Data acquired from web pages and SWIM are tailored for FACTs Information View area. FACT is designed to reside on an existing workstation monitor to be put into use as needed.
Flying drone
Unmanned Aerial Systems (UAS) Traffic Management
NASA Ames has developed an Autonomous Situational Awareness Platform system for a UAS (ASAP-U), a traffic management system to incorporate Unmanned Aerial Systems (UASs) into the National Airspace System. The Autonomous Situational Awareness Platform (ASAP) is a system that combines existing navigation technology (both aviation and maritime) with new procedures to safely integrate Unmanned Aerial Systems (UASs) with other airspace vehicles. It uses a module called ASAP-U, which includes a transmitter, receivers, and various links to other UAS systems. The module collects global positioning system GPS coordinates and time from a satellite antenna, and this data is fed to the UAS's flight management system for navigation. The ASAP-U module autonomously and continuously sends UAS information via a radio frequency (RF) antenna using Self-Organized Time Division Multiple Access (SOTDMA) to prevent signal overlap. It also receives ASAP data from other aircraft. In case of transmission overload, priority is given to closer aircraft. Additionally, the module can receive weather data, navigational aid data, terrain data, and updates to the UAS flight plan. The collected data is relayed to the flight management system, which includes various databases and a navigation computer to calculate necessary flight plan modifications based on regulations, right-of-way rules, terrain, and geofencing. Conflicts are checked against databases, and if none are found, the flight plan is implemented. If conflicts arise, modifications can be made. The ASAP-U module continuously receives and transmits data, including UAS data and data from other aircraft, to detect conflicts with other aircraft, terrain, weather, and geofencing. Based on this information, the flight management system determines the need for course adjustments and the flight control system executes them for a safe flight route.
Orbital debris
Space Traffic Management (STM) Architecture
As ever larger numbers of spacecraft seek to make use of Earth's limited orbital volume in increasingly dense orbital regimes, greater coordination becomes necessary to ensure these spacecraft are able to operate safely while avoiding physical collisions, radio-frequency interference, and other hazards. While efforts to date have focused on improving Space Situational Awareness (SSA) and enabling operator to operator coordination, there is growing recognition that a broader system for Space Traffic Management (STM) is necessary. The STM architecture forms the framework for an STM ecosystem, which enables the addition of third parties that can identify and fill niches by providing new, useful services. By making the STM functions available as services, the architecture reduces the amount of expertise that must be available internally within a particular organization, thereby reducing the barriers to operating in space and providing participants with the information necessary to behave responsibly. Operational support for collision avoidance, separation, etc., is managed through a decentralized architecture, rather than via a single centralized government-administered system. The STM system is based on the use of standardized Application Programming Interfaces (API) to allow easier interconnection and conceptual definition of roles to more easily allow suppliers with different capabilities to add value to the ecosystem. The architecture handles basic functions including registration, discovery, authentication of participants, and auditable tracking of data provenance and integrity. The technology is able to integrate data from multiple sources.
Urban Air Mobility
Near-Real Time Verification and Validation of Autonomous Flight Operations
NASA's Extensible Traffic Management (xTM) system allows for distributed management of the airspace where disparate entities collaborate to maintain a safe and accessible environment. This digital ecosystem relies on a common data generation and transfer framework enabled by well-defined data collection requirements, algorithms, protocols, and Application Programming Interfaces (APIs). The key components in this new paradigm are: Data Standardization: Defines the list of data attributes/variables that are required to inform and safely perform the intended missions and operations. Automated Real Time And/or Post-Flight Data Verification Process: Verifies system criteria, specifications, and data quality requirements using predefined, rule-based, or human-in-the-loop verification. Autonomous Evolving Real Time And/or Post-Flight Data Validation Process: Validates data integrity, quantity, and quality for audit, oversight, and optimization. The verification and validation process determines whether an operation’s performance, conformance, and compliance are within known variation. The technology can verify thousands of flight operations in near-real time or post flight in the span of a few minutes, depending on networking and computing capacity. In contrast, manual processing would have required hours, if not days, for a team of 2-3 experts to review an individual flight.
Stay up to date, follow NASA's Technology Transfer Program on:
facebook twitter linkedin youtube
Facebook Logo Twitter Logo Linkedin Logo Youtube Logo