Policy Based Automation for a Supply Chain

Abstract

A method for managing a supply chain includes: identifying a business context for the supply chain; identifying a set of business policy rules for the business context governing the relationship between entities involved in the supply chain; creating use-case description from the set of business policy rules; creating a plurality of executable code modules corresponding to the use-case description; specifying a plurality of name / value pair for modeling the set of business policy rules; provisioning the plurality of application server computers of the computer network system with the executable code modules; and provisioning a central directory database with the plurality of name / value pairs; whereby the computer network system, in response to events in business transactions between at least two entities involved in the supply chain, is operable to dynamically deliver at least one name / value pair from the central directory database and to execute at least one code module.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS[0001]This application relates, and claims priority, to U.S. Provisional Patent Application Ser. No. 60 / 297,018 filed on Jun. 8, 2001, entitled “Supply Chain Management,” which is assigned to the present Assignee and is incorporated herein by reference. This application is related to co-filed U.S. application Ser. No. ______, entitled, “Separating Decision Logic From Action Logic In a Supply Chain Management System,” [Attorney Docket No. M-11873 US], which is assigned to the present Assignee and incorporated herein by reference in its entirety.COPYRIGHT AND TRADEMARK NOTICE[0002]A portion of the disclosure of this patent document contains material which is subject to copyright protection. The owner has no objection to the facsimile reproduction by any one of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever. Certain marks refere...

AI Technical Summary

Benefits of technology

The present invention provides a system and method for managing supply chains by separating decision logic and action logic. This separation allows for easy modification of business policies without needing to modify the action logic. The system includes a computer network system with multiple application server computers and a central directory database. The system is operable to dynamically deliver and execute code modules based on business transactions between entities involved in the supply chain. The technical effects of this invention include faster implementation, flexibility, and improved efficiency in managing supply chains.

Problems solved by technology

Previous techniques have also not been adaptable to provide a versatile system capable of supporting a wide range, and, more importantly, a dynamic range of providers of raw materials, goods and, sometimes, related services.

These components themselves may involve complex supply chains, which must be organized, not merely for production, but also for providing spare parts for servicing, supplies for product development, and ad hoc needs.

Vertical integration, however, is unfeasible for any but the largest enterprises when the product is complex and large volume.

Even for giant corporations, it is easy to be overwhelmed by ever growing complexity, expectations and sheer size not to mention an ongoing drive towards more efficiency and accountability of many operational business units.

However, outsourcing, along with globalization and system / application proliferation, has also caused an increase in administrative complexity across supply chains.

Initiatives in outsourcing and collaborative planning have exposed a critical flaw in today's extended supply chains: specifically that they are not configured for efficient execution.

Thus, managing a supply chain has become a task of near exponentially growing complexity that enterprise-focused systems cannot adequately support.

Furthermore, collaborative planning solutions, though useful, fail to coordinate execution across supply chains.

However, such computer architectures have resulted in further complexity and have failed to adequately address the need for efficiency.

Such servers may contain representations of business rules that are defined by the seller (but are subject to external constraints).

Thus, such a system meets required levels of efficiency only at the undesirable cost of inflexibility as to business rules of the participants (typically partners) and is inadequate in the present context.

Previously developed systems do not readily support diverse and dynamically evolving verification requirements and other implications of local and distant business policies, laws and so on.

In systems where the business policies and rules must be determined in advance, changing them can be inefficient and may create interruptions in service.

One prior approach is the use of client-server systems, but this too often leads to a situation of unbounded growth in the complexity of the supply chain operations.

This results in a problem of “business logic everywhere” having to be skillfully coordinated for changes—a typical result is inefficiency in operation, inefficiency in changing to accommodate evolving needs and general lack of robustness.

But such systems may be inefficient.

Furthermore, design and implementation of such systems is a highly skilled art and very complex.

Moreover in such a system there are serious problems as to proving correctness of actions for audit purposes.

Commonly, the failure of such systems to be sufficiently flexible is highlighted when there is a need to accommodate a new participant (e.g. supplier, manufacturer or customer) in a supply chain, and the new participant has its own requirements, rules and pre-existing procedures.

Images