Eventing Infrastructure for Automated Asset Registration Workflows

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service metadata repositories rely on human users for manual review and approval processes, leading to inefficiencies and bottlenecks, as determining asset quality and ensuring correct assignment to domain experts is cumbersome and time-consuming.

Innovation Solution

Automating asset registration workflows by generating events in a metadata repository, which trigger automated workflows to assign assets to appropriate experts without human intervention, using an eventing infrastructure that filters and delivers events to business process management web service endpoints.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual review and approval processes are used by human users, then asset quality can be determined and correct assignment to domain experts can be ensured, but the process becomes cumbersome and time-consuming

Engineering Contradiction:
Improveasset quality determinationVSAvoidapproval process time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by automatically generating events when assets are submitted to the repository, triggering workflow engines to execute pre-defined approval workflows. This automation eliminates the need for manual initiation of review processes while maintaining quality determination through structured workflow steps that include expert assignment and asset evaluation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an eventing infrastructure and workflow engine as intermediaries between asset submission and human expert review. Events generated by the metadata repository are filtered and delivered to business process management endpoints, which then orchestrate the approval workflow. This intermediary layer automates routine tasks such as expert assignment and status tracking, reducing manual intervention while preserving quality control.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual processes are used for asset registration workflows, then human judgment can be applied to determine asset quality, but manual steps and human intervention create bottlenecks and delays

Engineering Contradiction:
Improveasset quality assessmentVSAvoidasset registration throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system implements self-service capabilities where the metadata repository automatically generates events for asset submission, and the workflow engine autonomously executes approval workflows without requiring manual initiation. The eventing infrastructure filters and routes events to appropriate business process endpoints, enabling the system to serve itself through automated workflow orchestration while maintaining quality assessment through structured expert review processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical processes with an automated event-driven system. Instead of manual tracking and coordination of approval workflows, the system uses event generation, filtering, and delivery mechanisms that automatically orchestrate the registration process. This substitution of manual operations with automated information processing significantly increases throughput while preserving quality control through structured workflow steps.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If automated workflows are implemented to reduce manual steps, then efficiency and speed improve, but system complexity increases

Engineering Contradiction:
Improveworkflow automation efficiencyVSAvoideventing infrastructure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments the automated workflow into distinct modular components: event generation by the metadata repository, event filtering by the eventing infrastructure, event delivery to business process management endpoints, and workflow execution by the workflow engine. This segmentation allows each component to be independently configured and managed, reducing overall system complexity despite the automation's sophistication.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The eventing infrastructure serves multiple functions within the system: it generates events from asset submissions, filters events based on predefined criteria, delivers events to appropriate business process endpoints, and coordinates workflow execution. This multi-functionality consolidates what could be separate complex systems into a unified event-driven platform, managing complexity through versatile core infrastructure.

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

Data Source

PatentUS9589250B2System and method for asset registration workflows utilizing an eventing infrastructure in a metadata repository
Publication Date: 2017.03.07 ORACLE INT CORP
  • US9589250B2 patent drawing
  • US9589250B2 patent drawing
  • US9589250B2 patent drawing

AI summary

Described herein is a system and method for automating asset workflows in a service metadata repository. A service metadata repository includes an event model for generating one or more events based on a change to one or more assets. A persistent message stores the one or more events. A subscription service provides the ability to subscribe to one or more events and register one or more subscribed web service endpoints where the one or more events will be delivered. A delivery service matches the one or more events to the one or more web service endpoint and delivers the one or more events to a notification service. A notification service notifies the one or more subscribed web service endpoints of the one or more events. One or more workflows automate asset registration based on rules configured in an XML file, wherein the one or more workflows are initiated upon receiving the one or more events at a subscribed web service endpoint.