Visual Business Software Configuration for Custom Data Kiosks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional business software platforms face issues such as complex user interfaces, platform dependence, lack of mobile functionality, miscommunication between process managers and developers, difficulty in customizations, and high costs, leading to inefficiencies and incompatibilities.

Innovation Solution

A cloud-based business software system with a graphical user interface (GUI) that allows users to define and manage data collection prompts, metadata tags, and generate customizable data collection interfaces, using a business assembly language (BA) for process control and reporting, with features like self-documenting procedures and kiosk user interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional business software is used, then functionality is provided, but user interface complexity increases and usability deteriorates

Engineering Contradiction:
ImproveusabilityVSAvoiduser interface complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a visual configuration interface as an intermediary between users and the complex underlying software system. Users can define data collection processes through visual elements (forms, fields, validation rules) without directly interacting with complex code or system architecture, thereby simplifying operation while maintaining functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables users to self-configure data collection processes through intuitive visual tools. Users can independently define forms, validate data, and manage processes without requiring technical expertise or developer intervention, making the system self-sufficient and easy to operate.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If traditional business software is used, then core functions are provided, but platform dependence and incompatibility increase

Engineering Contradiction:
Improveplatform compatibilityVSAvoidsoftware compatibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent designs the software system with universal interfaces and standardized data collection processes that can operate across multiple platforms. The visual configuration system and core functionality are platform-independent, allowing the same software to function reliably on different operating systems and hardware configurations without compatibility issues.

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

3Adaptability or versatility

If traditional business software is used, then data collection is possible, but mobile functionality is reduced or fragmented

Engineering Contradiction:
Improvemobile functionalityVSAvoidmobile usability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements dynamic adaptation of the user interface based on the device type. The visual configuration system automatically adjusts forms and data collection processes to be optimized for mobile devices, tablets, or desktops, ensuring consistent and easy operation across all platforms without fragmenting functionality.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If traditional business software is used, then basic operations are supported, but customization becomes expensive and difficult to manage

Engineering Contradiction:
Improvecustomization capabilityVSAvoidcustomization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The visual configuration interface serves as an intermediary that translates business requirements into system configurations without requiring complex coding or technical expertise. Users can customize data collection processes through visual elements, making customization simple and manageable while avoiding the complexity of traditional software modification.

Inventive Principle:
Principle #24Intermediary (Mediator)

5Loss of information

If traditional business software is used, then data tracking is possible, but transparency into business logic is reduced

Engineering Contradiction:
Improvebusiness logic transparencyVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The visual configuration system provides transparent feedback by displaying the exact configuration settings and validation rules that users define. The system shows business logic through the visual interface elements themselves, making the logic transparent and auditable without requiring complex technical documentation or system introspection.

Inventive Principle:
Principle #23Feedback

6Loss of information

If traditional business software is used, then functionality is provided, but documentation becomes missing or outdated

Engineering Contradiction:
Improvedocumentation completenessVSAvoidtime for maintenance
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The visual configuration system automatically generates and maintains documentation based on the actual configuration settings. When users modify forms or validation rules, the system automatically updates associated documentation, eliminating the need for manual documentation maintenance and ensuring documentation remains complete and current without consuming additional time.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250335512A1Business software platform and kiosk
Publication Date: 2025.10.30 ELUMUS LLC
  • US20250335512A1 patent drawing
  • US20250335512A1 patent drawing
  • US20250335512A1 patent drawing

AI summary

A system includes a controller, a database controlled by the controller, and a memory including an end-user executable code and a business software management code. The controller receives a user update to modify the end-user executable code, converts the user update to a machine language input, and, in response to the machine language input, modifies one or more of the end-user executable code, the database structure, and a documentation of the end-user executable code. In response to executing the program instructions associated with the modified end-user executable code on the end-user device, the controller generates a data collection GUI according to the modified end-user executable code and stores data in the database structure according to the modified end-user executable code.