Portable Software Execution Files for Remote Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies for automating software processes on remote computers are cumbersome, requiring resident applications or operating system modifications, which are time-consuming and expensive, and lack features for simple usability and reliable portability, especially for complex routines with loop nesting and variable fields.
Innovation Solution
A system and method for creating portable software execution files that can be deployed on remote computers, allowing for the creation of tasks with command line arguments executable as variables, validating and organizing nested tasks, and embedding necessary files and links for remote execution, ensuring portability and usability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If resident applications or operating system modifications are used to automate software processes on remote computers, then the automation can be executed, but the process becomes time-consuming and expensive
Solution Approach 1:
The patent creates portable executable files that copy the automation logic and dependencies to remote computers. Instead of installing resident applications, the system generates self-contained executable files that can be deployed to any computer, eliminating the need for complex installation processes and reducing deployment time significantly.
Solution Approach 2:
The automation system is segmented into portable executable units that can be independently deployed to remote computers. Each executable file contains the necessary logic and embedded dependencies, allowing selective deployment only to computers where the automation is needed, rather than installing system-wide.
2Extent of automation
If resident applications or operating system modifications are used to automate software processes on remote computers, then the automation can be executed, but the cost increases
Solution Approach 1:
The system creates portable executable files that copy automation logic to remote computers without requiring expensive resident applications or operating system modifications. The executables are self-contained and can run on standard computers, significantly reducing deployment costs.
Solution Approach 2:
The patent uses disposable portable executable files instead of expensive permanent installations. These executables can be created, deployed, and executed without leaving permanent modifications on the remote computers, reducing both initial deployment cost and ongoing maintenance expenses.
3Adaptability or versatility
If complex routines with loop nesting and variable fields are implemented, then the automation capability is enhanced, but the usability for non-skilled users decreases
Solution Approach 1:
The system automatically handles the complexity of loop nesting and variable fields by embedding the necessary logic within the portable executable files. Users simply deploy the executables without needing to manually configure complex automation routines, as the system self-manages the complexity internally.
Solution Approach 2:
The portable executable files act as intermediaries that translate complex automation logic into simple, deployable units. The executables contain embedded dependencies and logic that mediate between the user's simple deployment action and the complex automation execution, hiding the complexity from end users.
4Reliability
If portable execution files are created without embedding necessary files and links, then the file size is reduced, but the reliability of remote execution decreases
Solution Approach 1:
The patent merges the execution logic with all necessary dependency files and links into a single portable executable file. This combining ensures that when the executable is deployed to a remote computer, all required components are already included, guaranteeing reliable execution without requiring additional file associations or system configurations.
Solution Approach 2:
The system performs preliminary action by embedding all necessary files and links into the portable executable during the creation phase. This preliminary inclusion of dependencies ensures that the executable can run reliably on remote computers without requiring additional setup or configuration, as all necessary components are already prepared and integrated.
Data Source
AI summary
A portable unit is created on a first computer to be executed on one or more remote computers. The portable unit includes an execution file having one or more tasks. Additionally, data relationships between applications are identified. Users can create adapters that enable application automation processes to allow customers to define compliance boundaries and to allow for automation of upgraded applications. The applications can be updated by collecting automation information and employing an artificial intelligence engine to generate updated automation criteria. Automation can be generated based on return on investment. A dashboard is automatically generated to permit viewing of indicators regarding automation tasks.