Centralized Orchestration Engine for Utility Service Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for orchestrating service requests in utility companies are decentralized, leading to scattered decision-making capabilities, increased user involvement, and complex modifications for upgrades, making it difficult to manage and fulfill varied service requests efficiently.

Innovation Solution

A centralized orchestration engine that consolidates the view of all service requests, evaluates conditions at service points, and initiates both electronic command messages and field activities to fulfill requests, simplifying the process and reducing user involvement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If decentralized systems are used for orchestrating service requests, then local decision-making autonomy is maintained, but system complexity increases and user involvement increases

Engineering Contradiction:
Improveuser involvementVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines multiple decentralized orchestration systems into a single centralized orchestration engine that consolidates decision-making capabilities. This centralization reduces the number of user interactions needed across disparate systems and simplifies the overall system architecture by providing unified service request management.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized orchestration engine is designed to handle multiple types of service requests and coordinate various utility systems through a single platform. This multi-functional approach eliminates the need for separate specialized systems, thereby reducing user involvement while maintaining comprehensive service coverage.

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

2Adaptability or versatility

If decentralized systems are used for service request orchestration, then system flexibility is maintained, but modification complexity increases for upgrades

Engineering Contradiction:
Improvesystem flexibilityVSAvoidmodification complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

By merging upgrade and modification operations into a single centralized platform, the system allows for unified updates across all service request handling functions. This approach maintains system flexibility while significantly reducing the complexity of modifications and upgrades compared to coordinating changes across multiple decentralized systems.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If centralized orchestration engine is implemented, then decision-making efficiency is improved, but system centralization complexity increases

Engineering Contradiction:
Improvedecision-making efficiencyVSAvoidcentralization complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The centralized orchestration engine acts as an intermediary between service request sources and utility systems, consolidating decision-making functions in a single location. This intermediary approach improves decision-making efficiency by providing unified control while managing centralization complexity through standardized interfaces and protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9251486B2Service request orchestrator with smart meters
Publication Date: 2016.02.02 ORACLE INT CORP
  • US9251486B2 patent drawing
  • US9251486B2 patent drawing
  • US9251486B2 patent drawing

AI summary

A system for orchestrating the process of fulfilling service requests for utility services receives a first service request for utility services. The first service request references a first service point. The system evaluates conditions at the first service point. The system issues an electronic command message to fulfill the first service request based on the evaluation of conditions at the first service point. The system receives a second service request for utility services. The second service request references a second service point. The system evaluates conditions at the second service point. The system initiates a field activity to fulfill the second service request based on the evaluation of conditions at the second service point. The receiving the first service request, the evaluating conditions at the first service point, the issuing the electronic command message, the receiving the second service request, the evaluating conditions at the second service point, and the initiating the field activity are performed by a centralized orchestration engine.