Configurable application integrating service request and fulfillment process

Abstract

A method and system for generating a plurality of concurrent solutions for a corresponding plurality of service requests each having one or more service types. The method comprises the steps of defining a set of said service types and a sequence of activities for each said service type; and for each said service request, configuring a workflow of said activities from said service types in each said service request. The method comprises the further steps of defining owners of said activities in each said workflow and a schedule for performing said activities whereby said owner and schedule are defined using load balancing; and performing said activities and monitoring completion of said activities and said load balancing.

1 - 15 . (canceled) 
   
   
       16 . A database configured to operate as a service request workflow engine to implement various service request workflows, wherein a service request workflow implements a sequence of activities for at least one service request type comprising on of the service request workflows, comprising:
 a repository for storing a plurality of service request type definitions, wherein each service request type definition comprises a plurality of activities required for completing workflow associated with the type;   a user interface that allows users to interface to the database to initiate a service request workflow by associating at least one service request type for the service request workflow, and interacting with the database to provide necessary parameters for the at least one service request type; and   a workflow processor that responds to an initiated service request workflow by storing the at least one service type definition comprising the user-initiated workflow, and processing the necessary parameters to execute the service request workflow.   
   
   
       17 . The database set forth in  claim 16 , wherein each service request type comprises a sequence of workflow activities. 
   
   
       18 . The database set forth in  claim 16 , wherein the user interface allows users to choose predetermine service request workflows including at least one service type and corresponding sequence of activities. 
   
   
       19 . The database set forth in  claim 16 , wherein said workflow processor coordinates the activities comprising a service type workflow comprising a service request workflow with associated electronic data systems or executable applications in communication with the database that execute one or more activities. 
   
   
       20 . The database set forth in  claim 19 , wherein the user interface and work flow processor together provide for real-time tracking of completion of activities implemented in a service request workflow. 
   
   
       21 . The database as set forth in  claim 16 , wherein the workflow processor automatically searches for and locates parameters required for a service request workflow by communicating with other databases, electronic data systems and executable applications associated with the service request workflow. 
   
   
       22 . The database as set forth in  claim 16 , wherein the database may be reconfigured as new service request workflows are required to be implemented by the database. 
   
   
       23 . The database as et forth in  claim 16 , wherein users may access and use the database for requesting services associated with service request workflow in association with a role definition for the user included in a data access control list. 
   
   
       24 . The database as set forth in  claim 23 , wherein documents are presented to users via the user interface only if the user attempting to access said documents has authorization commensurate with authorization required for the access. 
   
   
       25 . The database as set forth in  claim 16 , wherein service request types are configured as predefined forms, or workflow type definitions, and the parameters for the sequences of workflow activities are automatically associated to owners of respective activities deriving from the parameters input at initiation. 
   
   
       26 . The database as set forth in  claim 25 , wherein owners are assigned to the activities, which owners are responsible for carrying out tasks for the activities, and reporting a status of each task to the database. 
   
   
       27 . The database as set forth in  claim 16 , wherein service request workflows are approved after initiation and before execution.