Workflow Database for Scalable Storage Service Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Corporate enterprises face challenges in managing data storage resources effectively due to increasing demands for bandwidth, computational power, and storage, while also needing to reduce infrastructure costs to remain competitive, leading to the adoption of outsourced service providers and complex service delivery models.
Innovation Solution
The implementation of a Service Provider Management System (SPMS) that enables customers and service providers to manage storage resources through workflow management, including generating work order requests, creating database objects, and tracking billable events, allowing for automated and manual task execution and billing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If companies scale infrastructure to meet increasing demands for bandwidth, computational power and storage, then service capability is improved, but infrastructure cost increases
Solution Approach 1:
The system enables self-service through automated workflow processing where work orders are automatically created, routed, and executed based on predefined rules and customer selections. The portal allows customers to autonomously manage storage resources by selecting from predefined work order types, eliminating the need for manual service provider intervention for routine tasks.
Solution Approach 2:
The patent introduces a portal and workflow management system as an intermediary layer between customers and the underlying storage infrastructure. This intermediary abstracts complex infrastructure management from customers while enabling efficient resource allocation, allowing companies to scale services without proportionally increasing operational overhead.
2Productivity
If companies out-source services to focus on core competencies, then operational efficiency is improved, but service management complexity increases
Solution Approach 1:
The system segments service management into discrete, standardized work order types that can be independently selected and executed. Each work order represents a specific storage management task (e.g., allocate storage, back up data, restore data), allowing customers to access only the services they need without being overwhelmed by the full complexity of the outsourced infrastructure.
Solution Approach 2:
The portal provides a universal interface that handles multiple storage management functions through a consistent workflow mechanism. Whether allocating new storage, performing backups, or restoring data, the same portal infrastructure and workflow engine handle all requests, simplifying the customer experience despite the diversity of underlying services.
3Speed
If automated workflow processing is implemented, then service delivery speed is improved, but system complexity increases
Solution Approach 1:
The system implements preliminary action by pre-defining work order types and their associated processing logic before runtime. Workflow templates, routing rules, and execution parameters are established in advance, allowing automated processing to occur without complex real-time decision-making. This upfront configuration enables fast automated execution while containing system complexity in the setup phase rather than during service delivery.
Data Source
AI summary
A method of managing workflows related to storage services provided by a service provider to a customer (via a management system) is presented. The management system includes a Web server and a workflow process. The Web server presents to a customer a task screen (or set of task screens) for a customer-selected work order request type so that the customer can prepare and submit a work order request to the management system. After receiving the work order request, the Web server uses information contained in and associated with the request to create a database object that includes some or all of the following elements: customer identifier; work order identifier, date/time of request; request state (e.g., new, open or closed); type of request; parameters or arguments to the request; and any textual description provided by the customer. The Web server stores the object in a database. The workflow process locates the new request in the database, performs the task specified by the request and closes the work order request by updating the object with the appropriate state. The workflow process generates a billable event corresponding to the work order request and enters that billable event in an account record of the customer that submitted the request. The account record can then be used to generate billing information. If the workflow process cannot complete the task successfully, an administrator of the service provider may perform the task, close the work order request and enter the billable event in the customer account record.