Patent Document ID: 9176951
Application ID: 13851168

Base Claim:
1. A method executed by one or more processors, for processing activity models, contained locally or remotely on one or more processor readable storage devices, wherein, rules called Knowledge Base Modeler (KBM) rules, which were devised to depict complex processing scenarios, are obtained by, augmenting the method of the system called Knowledge Base System (KB), for representing and processing static and dynamic information, wherein the improvement comprises: a) a new set of colors called reference colors, which are devised for augmenting reference mechanisms of entities, wherein, a type of reference color called “Data Set” color, can be assigned to terms of KBM rules, which implies, that entity references restricted to a partition or logical grouping implied by the data set color, are sought for the term of the KBM rule; and the absence of the said “Data Set” color, implies a default partition; Said entity references of the terms of KBM rules are stored in a container, capable of providing said partitions or logical groupings; b) a new set of colors called complex colors, which are used for depicting complex processing notions; c) a new set of colors called process colors, which are used for depicting effects of process structures on entities; d) a new set of colors called conceptual colors, which are used for depicting rule graphs, in an abstract form; e) new specialized structural rules called KBM Structural rules, for structuring the integration of said KBM rules; f) an enhanced Object Context (O-Context), wherein each entity type, can hold a plurality of entity references, segregated into partitions, called data sets; g) an extensible framework for creating new color types, and mapping these colors to said KBM rules; said reference colors, complex colors, process colors, and conceptual colors are collectively referred to as KBM colors; and rules of said KB system, can be further enhanced by utilizing said KBM colors; said KBM rules, are further integrated into larger process structures, by a framework called KBM “Desired Special Complex” (DSC) framework, which facilitates integration of process structures of lower order to process structures of higher order, recursively, until higher level process structures called “KBM Rule Graphs”, “KBM Gears”, and “KBM Activities” are progressively generated; said KBM activities, can be configured for execution by generic workflow engines, which comprises: h) Associating a queue called workflow queue, and a record called “Activity Failure record”, with each of said KBM activities, based on the state reached by the activity upon execution, for integration with workflow engines, and storing these associations as metadata in a file called configuration file of the activity; i) Associating a plurality of controls called “process controls”, with each of said KBM activities, and storing these associations, in the configuration files of the activities, such that an activity is invoked, using one of the configured process controls, called default process control, or re-executed with a different process control after a previous failure; such that, said KBM activities grouped into a set of sequential or concurrent activity blocks, called KBM workflow, depicts the activity flow of a complex application system or subsystem, which could be executed, to accomplish the goals of the application system or subsystem, by any generic workflow engine, specialized to process the said KBM activity meta data, in said activity configuration files, or by a pre-supplied module called KBM work flow coordinator.

---

Claim 11:
11. The method of claim 1 , further comprises of— a) Capturing a request for executing said KBM workflow, when an online or batch request is made by the end user, and recording it in a queue called KBM Workflow queue; Said request comprises of name of workflow and information regarding the key fields of the entities that participate in the processing of the workflow; b) Retrieving the request for executing the Workflow from the said KBM Workflow Queue, by KBM WorkFlow Coordinator, supplied as part of KBM runtime, and tools, which schedules and controls the execution of KBM Workflows; c) Retrieving the Workflow specification document, based on the workflow name received as input in the said KBM Workflow queue record; d) Parsing said Workflow document, and identifying the activity blocks, which are scheduled for execution; e) Scheduling the activity contained in the next block for execution if said block is enclosed in special tags called “SEQ”, which imply that the activity is to be executed in sequential order, by creating an instance of the activity module to be executed, and executing the “init” method, and subsequently the “execute” method, and creating a record in a table called KBM WorkFlow Execution status table, indicating that the activity was scheduled for execution; f) Scheduling all the activities contained in the next block for execution if said block is enclosed in special tags called “CONCUR”, which imply that the activities are to be executed in concurrent order, by repeating the process described for said single activity delimited by “SEQ” tags, for each of the activities specified in the block, delimited by the “CONCUR” tags; g) Executing the process structures of lower order contained in the current process structure recursively, by executing their init, execute and finish methods, until the current activity being executed, reaches a desired or special state; h) Updating said KBM Workflow Execution status table, when activities scheduled by workflow coordinator for the said KBM Workflow, have reached a desired or special state; i) Monitoring the Execution status of the activities already scheduled for execution by the said KBM Workflow coordinator, based on a preset timer; j) Scheduling the next workflow block of the current workflow for execution, if all the activities of the current workflow block have reached a desired state; k) Updating said KBM Workflow Execution status table, with the completion status of the workflow, when all activities scheduled by workflow coordinator for the said KBM Workflow, have reached a completion state.