Process Metadata Event Triggers for Enterprise System Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise systems face challenges in providing a secure, reliable, and scalable infrastructure that meets diverse functionality needs across various hardware, networking, and software components, especially when combining legacy and new systems, and supporting different user roles and access levels.

Innovation Solution

The system generates process metadata events and occurrences based on trigger criteria, allowing users to select, manage, and perform actions on these events, with features like event locking, notification, and document generation to ensure secure and efficient operation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If enterprise systems combine legacy and new hardware/software systems to support diverse functionality, then the system's adaptability and versatility improve, but the system's reliability and security deteriorate due to potential issues from integrating different components

Engineering Contradiction:
Improvesystem functionalityVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the enterprise system into distinct modules (legacy systems and new systems) that can be independently managed, monitored, and secured. This allows diverse functionality to be supported while maintaining reliability by isolating potential failure points and enabling targeted troubleshooting of specific components rather than the entire system.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If enterprise systems support enormously diverse functionality across different departments and users, then the system's adaptability improves, but the device complexity increases due to multiple hardware, networking, and software components

Engineering Contradiction:
Improvesystem functionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal enterprise system architecture that provides common core functionality (networking, security, data management) that serves all departments and users. This multi-functional platform reduces overall system complexity by eliminating the need for separate specialized systems for each department, while still supporting diverse functionality through configurable modules and interfaces.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If enterprise systems integrate multiple manufacturers' hardware and networking devices configured at different times and locations, then the system's adaptability improves, but the difficulty of detecting and measuring system issues increases

Engineering Contradiction:
Improvesystem functionalityVSAvoidissue detection difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements comprehensive feedback mechanisms including system-wide monitoring that tracks the state of all hardware and software components, automated logging of configuration changes, and performance metrics collection. This feedback enables centralized visibility into distributed system issues, allowing administrators to detect and measure problems across multi-manufacturer environments without increased difficulty.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9984111B2Process metadata triggers and events
Publication Date: 2018.05.29 ORACLE INT CORP
  • US9984111B2 patent drawing
  • US9984111B2 patent drawing
  • US9984111B2 patent drawing

AI summary

Embodiments of the invention provide systems and methods for implementing process metadata triggers and events. More specifically, embodiments of the present invention allow for process metadata events to be defined and generated, including the program code and interfaces that may define the triggering criteria and actions associated with the events. Certain embodiments include ongoing evaluations of triggering criteria for events, including criteria both internal and external to an enterprise system, and generating new event occurrences based on the evaluations of triggering criteria for events. Events and event occurrences may be tracked and monitored, and programmatic actions may be initiated in response to the creation or modification of an event or an event occurrence, including modification of enterprise system software, generation and transmission of targeted user notifications, the generation and customization of electronic documents, and the like.