Workflow Component Usage Tracking via Contract Association
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information processing systems lack an efficient method to associate workflows with count target contracts, leading to difficulties in tracking and billing usage history of components within these workflows.
Innovation Solution
An information processing apparatus and method that execute a predetermined workflow, transmit count target contract input screen information to a user terminal, associate the workflow with count target contract information, and count the usage history of components included in the workflow in association with the count target contract.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If workflows are executed without associating count target contracts, then operational simplicity is maintained, but usage history tracking and billing accuracy deteriorate
Solution Approach 1:
The system performs preliminary association between workflows and count target contracts before workflow execution. The count target contract input screen is transmitted to the user terminal in advance, allowing users to specify which contract should be associated with the workflow before it runs. This preliminary action ensures that usage history can be accurately tracked from the start of workflow execution without requiring complex post-processing or manual tracking interventions.
2Measurement precision
If manual tracking of component usage is implemented, then billing accuracy can be improved, but operational efficiency and time consumption worsen
Solution Approach 1:
The system implements self-service automated tracking where the information processing apparatus automatically counts and records usage history of components during workflow execution. The count target contract association enables the system to autonomously identify which contract corresponds to which workflow, and automatically tally component usage without requiring manual intervention. This self-service mechanism maintains high billing accuracy while preserving operational efficiency by eliminating manual tracking tasks.
Solution Approach 2:
The system establishes a feedback loop where usage history data is automatically collected during workflow execution and fed back to the billing system. The count target contract provides the feedback mechanism that links workflow execution data to specific billing contracts, enabling automated generation of accurate usage reports and billing information without manual compilation or intervention.
3Device complexity
If component usage history is not associated with specific contracts, then system complexity is reduced, but financial tracking and billing capability deteriorate
Solution Approach 1:
The information processing apparatus performs multiple functions through a unified structure: it executes workflows, transmits count target contract input screens, receives user specifications, associates contracts with workflows, and counts component usage. This multi-functional design allows the system to maintain relatively simple overall architecture while still achieving comprehensive contract-specific usage tracking. The count target contract acts as a universal link that connects workflow execution data to billing information without requiring separate complex tracking systems.
Data Source
AI summary
An information processing apparatus, an information processing system, and an information processing method. The information processing apparatus executes a predetermined workflow including a component whose usage history is to be counted, transmits to a user terminal through a communication network, count target contract input screen information for displaying a count target contract input screen on a display of the user terminal, the count target contract input screen associating a predetermined count target contract with the predetermined workflow, in response to an operation on the count target contract input screen displayed on the display of the user terminal based on the count target contract input screen information, associates the predetermined workflow with predetermined count target contract information indicating the predetermined count target contract, and in response to an execution of the predetermined workflow, counts the usage history of the component included in the predetermined workflow in association with the predetermined count target contract.