Abstract: A method and apparatus are disclosed for managing composite business processes that include multiple trading mechanisms, such as requests for quotes (RFQs), auctions and contracts, or repeat passes through a single trading mechanism. The independence of the individual business processes that manage each trading mechanism is maintained, while each individual business process can be connected to other business processes to form a composite business process. Each individual business process that may be followed by another business process to form a composite process must have at least one state labeled as a conversion state with a conversion transition to another business process. A conversion transition spans the gap between an end state of one business process and the start state of another subsequent business process. When a conversion state is entered by an object, a determination is made as to whether the object is being managed by a composite flow, and if so, what business process to use next.

Abstract: A system to enable a subjective and an objective evaluation of supplier performance is provided and includes a commodity/part/supplier search system, a traceability system, an aggregation system, a survey system, an evaluation system, a scoring system, and an alert system to compare the score with the target performance level of the supplier and, if the score differs from the predicted performance level by a predetermined amount, to alert the supplier of the differential.

Abstract: A method and apparatus are disclosed for managing access control for a business process that is managed using a state machine. A domain represents the various trading mechanisms that are supported by a business process. Domains are placed at the highest level in a tree structure. Within each domain, there is one or more different flow types defined, such as flow types for buyers and sellers. Within each flow type, one or more flows or business processes may be defined. A flow defines the order of the steps required to produce an object. Each flow typically begins with a mandatory “start” state, having one or more transitions to additional states. Each transition may contain an access control guard. The guards on the transitions leading from the start state can be referenced to determine the user's authorization to access the domains, flow types, and flows.

Abstract: A task schedule is enforced among multiple processes by setting process priorities based upon which tasks are running on which processes and based upon the task schedule. The task scheduling may be provided by a local or global scheduler which uses application information to prioritize tasks. The task schedule, or priority list, is provided at Local Activity Schedulers which schedule the activities for their local execution elements/nodes. Execution of activities locally are performed by any number of processes that reside in each execution element. These processes are assigned operating system priorities by the respective Local Activity Scheduler based on their assigned activities for execution and the task schedule.

Abstract: A method and apparatus are disclosed for maintaining membership lists associated with given states of a state machine. The present invention uses a state machine to represent a business process. The state machine includes a plurality of states, and at least one state includes an entry action that is executed upon entering the state. A user group list can be accessed and processed using the entry action. When an object enters a state, the corresponding entry action may be executed. The entry action will obtain the membership group name from the corresponding state definition. If the field is not null, then the business process manager queries the membership subsystem to obtain a list of individuals who belong to that membership group name for the organization which owns the object. Only those users are notified that the object is awaiting approval and are therefore designated as the preferred approvers for this object.

Abstract: A method and apparatus are disclosed for managing the versioning of business objects, such as contracts, advertisements, auction listings and RFQs. A state machine is used to represent a business process and manages the versioning of business objects associated with the business process. The present invention manages the original business object, the new version of the object, and any business objects that depend on the modified business object, if necessary. The business object remains in an active state during the modification process, until the new version of the business object is available. The new version of the business object remains in an inactive state during the modification process. The new version of the business object is transferred to an active state and the original business object is transferred to an inactive state when the modification is complete (e.g., when the modified business object is approved).

Abstract: A method and apparatus are disclosed for managing composite business processes that include multiple trading mechanisms, such as requests for quotes (RFQs), auctions and contracts, or repeat passes through a single trading mechanism. The independence of the individual business processes that manage each trading mechanism is maintained, while each individual business process can be connected to other business processes to form a composite business process. Each individual business process that may be followed by another business process to form a composite process must have at least one state labeled as a conversion state with a conversion transition to another business process. A conversion transition spans the gap between an end state of one business process and the start state of another subsequent business process. When a conversion state is entered by an object, a determination is made as to whether the object is being managed by a composite flow, and if so, what business process to use next.

Abstract: A method and apparatus are disclosed for automatically transitioning between states in a state machine that manages a business process. A state machine is used to represent a business process. The state machine includes a plurality of states, and at least one state includes an entry action that is executed upon entering the state. The present invention provides for automatic state transitions by throwing events upon state entry whenever any conditions associated with the entry action are satisfied. The entry action includes conditional logic that causes an automatic transition to another state if the conditional logic is satisfied. The present invention provides a method to implement complex decision-making logic in one place, thereby allowing the logic to be more easily and consistently defined and maintained.

Abstract: A method and apparatus are disclosed for managing access control for a business process that is managed using a state machine. A domain represents the various trading mechanisms that are supported by a business process. Domains are placed at the highest level in a tree structure. Within each domain, there is one or more different flow types defined, such as flow types for buyers and sellers. Within each flow type, one or more flows or business processes may be defined. A flow defines the order of the steps required to produce an object. Each flow typically begins with a mandatory “start” state, having one or more transitions to additional states. Each transition may contain an access control guard. The guards on the transitions leading from the start state can be referenced to determine the user's authorization to access the domains, flow types, and flows.

Abstract: A generic interface between an electronic commerce frontend and a business management backend is provided via an object oriented computer program product. In operation, the program creates one or more specific business objects from a plurality of specific business object classes. The program also provides a framework within which the business objects travel. A first framework instance is coupled to the frontend, and a second framework instance is coupled to the backend. In response to a request from the frontend or backend, the framework instance coupled to the requesting end creates a specific business object to perform the requested operation. Specific Business Objects are derived from a common class containing the methods required by the framework, a specific business object class containing the methods for performing a specific business function (e.g., order, provide production information, etc.