Object Model Change Events for Audit Trail and Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for tracking changes to extensible object models representing operational systems are inefficient and costly, lacking a customizable and granular approach, and do not provide a complete audit trail or the ability to recover the object model from change records.
Innovation Solution
An apparatus and method for detecting changes to extensible object models, generating change events, storing them in data repositories, and transmitting them to an enterprise management system to perform monitoring and control operations, with customizable notification criteria and the ability to generate change notifications and audit reports.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional change tracking methods are used for extensible object models, then system simplicity is maintained, but tracking efficiency and cost-effectiveness deteriorate
Solution Approach 1:
The patent segments change tracking into discrete change events that are independently detected, stored, and processed. Each change event represents a specific modification to the extensible object model, allowing granular tracking without requiring complex monolithic tracking infrastructure. This segmentation enables efficient tracking by processing only relevant changes rather than entire model states.
Solution Approach 2:
The patent introduces change events as intermediary objects between the extensible object model and the enterprise management system. These change events serve as standardized mediators that carry change information, enabling decoupled communication and simplifying the overall system architecture while improving tracking efficiency.
2Loss of information
If comprehensive change tracking is implemented, then complete audit trail is achieved, but data storage and processing costs increase
Solution Approach 1:
The patent extracts only the essential change information from the extensible object model modifications and stores it as change events. Instead of tracking entire model states or all possible changes, the system extracts and stores only the specific change attributes that are relevant for auditing and recovery purposes, reducing storage requirements and processing costs while maintaining audit trail completeness.
Solution Approach 2:
The patent changes the parameter representation of changes by storing change events with specific parameters (change type, affected elements, timestamps, before/after states) rather than storing complete model snapshots. This parameterized approach to change representation achieves complete audit trails using efficient data structures that minimize storage and processing overhead.
3Adaptability or versatility
If granular change tracking is implemented, then selective response capability is improved, but system complexity increases
Solution Approach 1:
The patent implements dynamic notification criteria that can be configured and adjusted based on specific needs. The system allows users to define which types of change events should trigger notifications, enabling selective response to changes without requiring complex static routing rules. This dynamic approach improves adaptability while keeping the notification system relatively simple through flexible configuration rather than hard-coded complexity.
4Reliability
If change event storage and retrieval is implemented, then model recovery capability is achieved, but data management complexity increases
Solution Approach 1:
The patent performs preliminary action by storing change events as they occur in real-time, rather than attempting to recover models from scratch after changes. This continuous logging of change events creates a ready-to-use recovery mechanism where the extensible object model can be restored by replaying stored change events, achieving reliable model recovery without complex backup and restoration procedures.
Data Source
AI summary
An extensible object model system for maintaining extensible object models representing operational systems detects changes to the extensible object models generated by an enterprise management system and generates change events identifying and/or characterizing the detected changes, possibly based on publish events from the enterprise management system associated with particular operations that generated the detected changes. The extensible object model system generates notifications based on the change events and configurable notification criteria and provides a change event interface (e.g., UI, API) for providing change events to the enterprise management system in response to change event requests received via the change event interface. The extensible object model system generates change audit reports and/or recovered extensible object models based on the change events and/or causes the enterprise management system to generate updated operational data processing criteria based on the change events.