Workflow Server for Cross-Entity Security Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing multiple devices within a security ecosystem is time-consuming and requires in-depth knowledge of each system, leading to a burden on administrators who need to configure workflows across disparate systems to respond to security events effectively.

Innovation Solution

A system and method for implementing workflows across multiple systems using a workflow server that monitors triggers and executes actions across differing systems, including a computing device configured to execute safety workflows and interact with workstations, allowing for the comparison of events with export and import rules to initiate relevant workflows in other entities' systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If administrators configure workflows separately in each security system, then each system can be optimized for its specific functions, but the complexity of managing multiple systems increases and requires in-depth knowledge of each system

Engineering Contradiction:
Improveworkflow configuration accuracyVSAvoidsystem management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a workflow server as an intermediary component that sits between multiple security systems (video surveillance, access control, radio communication). This server receives workflow definitions from administrators and automatically configures connections between different systems, eliminating the need for administrators to directly manage complex inter-system configurations while maintaining accurate workflow implementation across all systems

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If administrators manually configure each workflow connection between systems, then customization can be achieved, but time consumption increases significantly

Engineering Contradiction:
Improveworkflow customizationVSAvoidconfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements a pre-configured workflow server that comes with predefined templates and automated connection frameworks. Administrators can select from pre-built workflow patterns (such as alarm response workflows) and customize parameters rather than configuring every connection from scratch, significantly reducing configuration time while maintaining adaptability to specific security needs

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The workflow server automatically handles the technical aspects of system integration, including protocol translation, data format conversion, and connection establishment between different security systems. This self-service capability allows administrators to define high-level workflow logic without being burdened by low-level configuration details, reducing time consumption while preserving customization options

Inventive Principle:
Principle #25Self-service

3Ease of operation

If multiple security ecosystems are implemented for different entities, then each entity can have dedicated security management, but the ability to respond to cross-entity security events is reduced

Engineering Contradiction:
Improveentity-specific security managementVSAvoidcross-entity response capability
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The workflow server is designed as a universal platform that can manage workflows for multiple different entities simultaneously. It maintains separate workflow contexts for each entity (allowing entity-specific management) while also providing mechanisms to establish cross-entity workflows through standardized interfaces and export/import rules, enabling the system to respond to security events that span multiple entities

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

4Manufacturing precision

If detailed knowledge of all security systems is required for proper workflow configuration, then configuration accuracy is improved, but the burden on administrators increases

Engineering Contradiction:
Improveworkflow configuration precisionVSAvoidadministrator workload
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The workflow server serves as an intermediary that absorbs the complexity of system-specific configuration details. It provides a simplified user interface where administrators can define workflows using high-level concepts without needing to understand the underlying technical specifics of each security system. The server handles the translation and adaptation of these high-level definitions into system-specific parameters, maintaining configuration precision while reducing administrator workload

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The workflow server incorporates automated validation and feedback mechanisms that check workflow configurations against system capabilities and constraints. It provides real-time guidance and error detection, allowing administrators to configure workflows with confidence while the system handles the technical validation details, thereby maintaining precision without increasing administrative burden

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240420265A1Security ecosystem, device and method for controlling workflows associated with different entities based on export and import rules
Publication Date: 2024.12.19 MOTOROLA SOLUTIONS INC
  • US20240420265A1 patent drawing
  • US20240420265A1 patent drawing
  • US20240420265A1 patent drawing

AI summary

A security ecosystem, device and method for controlling workflows associated with different entities based on export and import rules is provided. For example, a computing device monitors execution of a first safety workflow, associated with a first entity, comprising a first trigger and a first responsive action. The computing device compares an event, associated with the first trigger, with an export rule. In response to the event of the first safety workflow meeting the export rule, the computing device compares the event with an import rule, associated with a second entity, for initiating a second safety workflow based on the event and associated with the second entity. In response to the event meeting the import rule, the computing device initiates the second safety workflow associated with the second entity, the second safety workflow comprising a second trigger and a second responsive action, the second trigger corresponding to the event.