Context Object Harness for Application Data Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Employees in organizations face challenges in managing multiple, varying urgency issues within formal and informal work contexts, as existing communication systems like CRM do not effectively support informal processes or help manage issues within the organization, and require manual configuration of applications for context-specific data.

Innovation Solution

A method and system that interfaces between a context object and applications to retrieve, update, and modulate behavior based on context data, enabling features, disabling others, and populating data fields, thereby enhancing productivity and efficiency by automatically managing context-specific information across applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration is used for each application in context-specific scenarios, then application functionality is achieved, but time consumption and operational complexity increase significantly

Engineering Contradiction:
Improveapplication configurationVSAvoidtime for manual data entry
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system pre-loads context data from the context object before the application needs it. When a user activates an application in a specific context, the harness application has already retrieved relevant data (participant names, meeting reasons, etc.) and prepared it for immediate use, eliminating manual configuration time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The application automatically retrieves and configures itself with context-specific data from the context object without requiring manual user input. The system serves itself by population g data fields and enabling features based on the active context, freeing the user from repetitive data entry tasks

Inventive Principle:
Principle #25Self-service

2Productivity

If employees switch attention between multiple issues dynamically, then urgent matters are addressed promptly, but context switching overhead and memory refresh time increase

Engineering Contradiction:
Improveresponse speed to urgent issuesVSAvoidtime to refresh memory about deferred matters
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The context object serves as an intermediary that stores and maintains context data while employees switch between issues. When employees return to a deferred matter, the harness application retrieves the stored context data, allowing quick refresh of memory about the issue without requiring employees to recall details from scratch

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The context object continuously maintains and updates context data even when employees switch attention. This ensures that context information remains fresh and accessible, allowing employees to seamlessly return to any issue with up-to-date information already prepared

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If existing CRM systems are used for formal business processes, then customer relationship management is achieved, but support for informal processes and internal issue management is insufficient

Engineering Contradiction:
Improveformal process executionVSAvoidsupport for informal processes
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The context object and harness application provide a universal framework that works across both formal business processes (supported by CRM) and informal processes (not supported by CRM). The system can handle diverse contexts including customer interactions, internal meetings, and ad-hoc issues through a single unified approach

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

Solution Approach 2:

The context object acts as an intermediary layer between formal CRM systems and informal process needs. It captures and structures context data from various sources including informal communications, making this data accessible to applications for both formal and informal work contexts

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9843626B2Method, system and apparatus for controlling an application
Publication Date: 2017.12.12 MITEL CORP
  • US9843626B2 patent drawing
  • US9843626B2 patent drawing
  • US9843626B2 patent drawing

AI summary

A method, system and apparatus of controlling at least one application on an electronic device. Interfacing occurs between a context object and the at least one application. Context data is retrieved from the context object. At least one of the following further occurs: the context object is updated with new context data derived from interactions with the at least one application; the behavior of the at least one application is modulated based on the context data; and at least one data field in the application is populated with the context data.