Event-Driven Data Extraction Scheduling for Manufacturing Intelligence

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional manufacturing intelligence systems face inefficiencies due to rigid scheduling of data extraction, transformation, and loading processes, leading to excessive resource utilization and delayed data availability, which cannot handle unpredictable events effectively.

Innovation Solution

A server runtime environment with a scheduler process for periodic events and an on-demand process for user-requested events, synchronized by an event manager process, allowing flexible execution of data extraction, transformation, and loading tasks in manufacturing intelligence systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If object execution is scheduled frequently according to a predetermined schedule, then data availability for analysis is improved, but processor resource utilization and network bandwidth are excessively consumed

Engineering Contradiction:

Improvedata availability timeVSAvoidprocessor resource utilization

Core Design Contradiction:

Loss of timeVSUse of energy by moving object

Solution Approach 1:

The system transitions from static predetermined scheduling to dynamic event-driven scheduling. Objects are executed based on actual events occurring in the manufacturing environment rather than fixed time intervals, allowing the system to adapt execution frequency to actual needs and reduce unnecessary resource consumption.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The manufacturing intelligence system automatically detects and responds to events without requiring external scheduling commands. The system self-regulates object execution by monitoring for relevant events and triggering appropriate data extraction and transformation operations only when needed.

Inventive Principle:

Principle #25Self-service

2Use of energy by moving object

If object execution is scheduled infrequently according to a predetermined schedule, then processor resource utilization is reduced, but data is not available for analysis for extended periods

Engineering Contradiction:

Improveprocessor resource utilizationVSAvoiddata availability time

Core Design Contradiction:

Use of energy by moving objectVSLoss of time

Solution Approach 1:

The system uses dynamic event-triggered execution rather than static time-based scheduling, allowing execution frequency to automatically adjust based on actual manufacturing events, ensuring data is available when needed without continuous resource consumption.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system implements event monitoring and feedback mechanisms that detect when data extraction is actually needed based on manufacturing events, triggering execution only in response to real conditions rather than predetermined schedules.

Inventive Principle:

Principle #23Feedback

3Device complexity

If a static predetermined schedule is used for object execution, then system operation is simple and predictable, but unpredictable events such as data reconciliation and unexpected work order changes cannot be handled flexibly

Engineering Contradiction:

Improvescheduling system complexityVSAvoidhandling of unpredictable events

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The system replaces static scheduling with dynamic event-driven execution, enabling the system to automatically adapt to unpredictable manufacturing events while maintaining manageable complexity through event-based triggering rather than complex rescheduling logic.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system prepares object execution logic in advance but triggers execution based on preliminary detection of relevant events, allowing flexible response to unpredictable situations without requiring complex real-time scheduling decisions.

Inventive Principle:

Principle #10Preliminary action

4Ease of manufacture

If conventional predetermined scheduling is used, then system implementation is straightforward, but resource waste and delayed data availability occur simultaneously

Engineering Contradiction:

Improvesystem implementation easeVSAvoiddata processing efficiency

Core Design Contradiction:

Ease of manufactureVSProductivity

Solution Approach 1:

The system implements dynamic event-driven scheduling that maintains relative implementation simplicity while dramatically improving processing efficiency by executing data extraction operations only when manufacturing events indicate actual need, eliminating both resource waste and delays.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS11656904B2Coordinating event-driven object execution

Publication Date: 2023.05.23 AVEVA SOFTWARE LLC

AI summary

Coordinating scheduled events and aperiodic events to execute objects to extract, transform, and load data from source systems to a structured data store. An event manager process executing on a server runtime utilizes event suspension, consolidation, and sequencing techniques to ensure that only one event process is executed for a particular time range.