1. Technical Field of the Invention
This invention pertains to Internet services. More particularly, it relates to a system and method for managing relationships between trading network managers, suppliers and customers.
2. Background Art
The Internet provides exchange mechanisms where suppliers bring goods and services to be offered and malls for shoppers to obtain them. These exchange mechanisms are largely independent with a single company selling and an individual from another company shopping. Generally, if companies wish to partner to gain advantage either from consolidating purchase volumes to obtain better prices or from creating a complete palette of business goods and services to establish a ‘one stop shop’, many individual relations are established and managed independently. Manual integration of systems to ensure members rights and responsibilities are met increase the bureaucracy and paperwork. Should a company endeavor to participate or host multiple trading networks, the membership management becomes very difficult.
There is, therefore, a need in the art for a system establishing a base for varied relationships and a set of processes for managing them. Comprehensive support is needed for a single trading network and to facilitate business exchange for multiple trading networks. Such a system needs to combine a sales perspective with a buying perspective to support the entire business exchange, allowing for purchase of goods from a catalog, a contract, based on supplier preference for a commodity, or by way of a request for quote; it needs to support a membership fee based on straight subscription, per transaction or including agent fees, provide for automated membership term management (dropping sub-packages which expire), ensuring coverage of other sub-packages whose initial supplier has terminated its participation, and support many combinations of services, including information technology (IT) hosting alone, or combined with application management and sourcing and procurement business process management.
It is an object of the invention to provide an improved system and method for managing relationships between suppliers and customers within a trading network.
It is a further object of the invention to provide a single trading network method and system facilitating business exchanges for multiple trading networks.
It is a further object of the invention to provide a system and method for managing a trading network so as to combine sales and buying perspectives.
It is a further object of the invention to provide a system and method for managing a trading network so as to allow purchase of goods from a catalog, contract, supplier preference or request for quote.
It is a further object of the invention to provide a system and method for managing a trading network having a membership fee based on straight subscription, per transaction or including agent fees.
It is a further object of the invention to provide a system and method for managing a trading network which provides for automated membership term management (dropping sub-packages which expire), ensuring coverage of other sub-packages whose initial supplier has terminated its participation
It is a further object of the invention to provide a system and method for managing a trading network which supports many combinations of services, including information technology (IT) hosting alone, or combined with application management and sourcing and procurement business process management.
In accordance with the preferred embodiment of the method of the invention a trading network is operated by establishing supplier memberships of suppliers providing offerings to said trading network; establishing customer memberships of customers providing volume commitments; and consolidating all volume commitments for a particular commodity or service when negotiating an offering with the supplier.
In accordance with an aspect of the invention, there is provided a computer program product configured to be operable to establish supplier memberships of suppliers providing offerings to said trading network; establish customer memberships of customers providing volume commitments; and consolidate all volume commitments for a particular commodity or service when negotiating an offering with the supplier.
Other features and advantages of this invention will become apparent from the following detailed description of the presently preferred embodiment of the invention, taken in conjunction with the accompanying drawings.
In accordance with the preferred embodiments of the invention, a data model with relationship details and entity attributes establish a base for defining and managing a variety of relationships. It provides integration alternatives for a trading network corporation and for its members.
From a buy side perspective, a company becomes a member of a trading network, making commitments and obtaining advantages. Actual transactions map back to initial commitments and result in accurate member billing. Memberships can include access to publicly traded items, to general member-traded items, or to custom packaged items for this member alone.
From a sell side perspective, a supplier makes commitments and obtains advantages. Again, actual transactions map back to initial commitments to ensure equitable payment or redress for supplier commitments. Suppliers may participate with general overall discounts, volume purchase agreements or with custom catalogs or contracts either for the entire network or for a set or given member to purchase from.
Referring to
Referring to
Referring to
Referring to
In the syntax of
As illustrated in the entity relationship diagram of
While each entity is described more fully hereafter, the following examples are provided to illustrate the entity relationship diagram.
As is represented by relationship 21, a trading network 100 has available for sale at least one but possibly many TN portfolio items 148. One TN portfolio item 148 is available for sale from one trading network (TN) 100 only.
As is represented by relationship 23 to exclusive OR 170, one TN portfolio item 148 may be a purchase offering 158, or a technical offering 164, or a process business offering 174. As is represented by relationship 101, a TN portfolio item 148 pertains to zero, one or many TN commodity group members 130. As is represented by relationship 103, versions of TN portfolio item 148 are grouped under one and only one TN portfolio item master, each of which may pertain to many portfolio items 148. As is represented by line 105, a TN portfolio item 148 is a base version of zero or one TN port item master entities 146, which in turn pertain to one and only one TN portfolio item 148.
As is represented by relationship 23 and relationships 25 and 27, TN portfolio item 148 may be a purchase offering 158 and a trading network offered item 178. That is, as is represented by relationships 23 and 25, subtype XORs 170 and 176 are ANDed and one and only one of entities 158, 164 or 174 and one and only one of entities 178 and 180 must define a TN portfolio item 148. As is represented by relationship 67 in connection with XOR 172, purchase offering 158 may be a catalog offering 154, a supplier preference offering 156 or a contract offering 160.
A TN offered item 178 is a TN portfolio item 148 that is offered directly from the trading network itself, not from any of the suppliers in the network.
A TN supplier offering 180 is a trading network portfolio item 148 that is offered from one of the suppliers 102 in the network. This offering can be considered a line item within the supplier's membership agreement 104, and is defined by the following fields.
As is represented by relationship 29, identity is inherited by traversing down a solid line relationship path. For example, starting at TN 100 and going to TN package 132, a trading network 100 offers at least one and maybe many
packages 132. It is also true that package 132 is offered by one and only one network 100. A plurality of trading networks 100 exists within a system, each identified by an ID number. Inheritance of identity means, for example, that TN package 132 is identified by an ID associated with a trading network and its own ID. As is represented by relationship 31, a trading network package 132 contains at least one but maybe many TN package items 144. Similarly, as is represented by relationship 33, TN package item 144 allows use of one TN portfolio item; and in the reverse sense, TN portfolio item 148 is used in maybe none but maybe many TN package items 144.
As is represented by relationship 37, trading network 100 has one or many TN supplier membership agreements 104, and a membership agreement 104 relates to one and only one trading network 100. As is represented by relationship 39, a trading network 100 has one or many TN customer membership agreements 108, and each customer membership agreement 108 pertains to one and only one trading network 100.
Entities relating primarily to customers 204 include entities 108, 110, 120, 122, 134 and 114. Entities relating primarily to suppliers include entities 102, 104, 150, 152, 154, 156, 160, 162 and 180. Entities relating primarily to the trading network (TN) include entities 106, 112, 118, 126, 128, 130, 132, 138, 140, 158, 164, 174, 142, 144, 146, and 148.
Referring to
Trading network (TN) 100 is a legal entity including supplier members and customer members. It is not just a transient grouping of member companies, and it need not be specific to any one country. TN 100 aggregates forecasts from multiple customers for leveraging negotiations with a supplier and, conversely, can combine offerings from multiple suppliers into packages for assignment to a customer. TN 100 may offer services of its own, including hosted systems integration (allowing use of its applications and information technology infrastructure) and resale (taking title of some goods and reselling them directly to a customer). TN 100 may also do some procurement of its own, such as buy goods or services to be sold in the resale model.
Each trading network 100 has one portfolio of offerings 148 that it can sell to customer members 110. A TN portfolio item 148 is a single line item within a trading network's portfolio of services, including the following fields:
TN portfolio item master 146 is a common master from which several TN portfolio items 148 derive. The portfolio items 148 are different versions of the same master 146. This does not refer to different point-in-time snapshots of the same thing, but versions with some content difference, such as different prices, contains only a subset of the parts, different payment flow, and so forth. TN portfolio item master entity 146 is defined with reference to the following fields.
Each trading network 100 has one portfolio of offerings 148 that it can sell to customer members 110. Each portfolio item can be sourced from one supplier member, who provides the offering as a line item in its membership contract (a TN supplier offering) or directly from the TN itself (a TN offered item.) Each portfolio item 148 can be of one basic type: purchasing offering, procurement business offering, or technical offering. For a single supplier offering a Trading Network may establish a master TN portfolio item with different versions (by price, by catalog content, etc) to facilitate correlation to different TN packages (high vol committed with max discounts vs standard or minimized liability).
A purchasing offering provides access to a purchasing catalog or contracts. A single purchasing offering is specific to a defined set of commodities. One given purchasing offering might enable the use of one given catalog, but not more than one. A given catalog purchasing offering may be valid for a longer period of time than a given time version of a catalog, for example, to which it points. Thus, there is no need for a timeless catalog master to be used as the offering pointer, nor is it necessary to update the purchase offering to point to a different catalog every time an updated version is released. One given purchase offering might enable the use of one given outline agreement contract, but not more than one. A given purchase offering may allow use of a given supplier as a preferred supplier. However, all customers of the trading network do not have to have the same preferred supplier.
A procurement business offering is any value-add service that the trading network can offer for a fee.
A technical offering allows use of specific applications for a given business function and the IT infrastructure.
A TN commodity group member 130 is one of the TN commodities that is referenced by a given TN portfolio item 148. This entity 130 is defined with reference to the following fields or parameters.
A TN package 132 is a collection of TN supplier offerings that can be assigned as a benefit to a customer member(s). It may be managed or unmanaged and it may be standard or customized for one set of customers. A TN package entity 132 includes the following fields:
As is represented by relationship 93 and XOR 124, TN package 132 may be a custom TN package 126 or a standard TN package 128. As is represented by relationship 95 and XOR 136, TN package 132 may be a managed TN package 138 or an unmanaged TN package 140.
A TN package item 144 is one specific line item within a TN package. It includes the following fields:
A trading network 100 offers packages 132 made up of collections of their portfolio items 148 to its customer members. Each TN package item 144 is tied to one portfolio item 148, and the same portfolio item can be included in a plurality of packages. A TN package 132 can include TN package items 144 that come from different TN supplier members 104 or from the TN 100 directly. A TN package 132 can be assigned as a benefit 120 to a TN customer member entity 108. Customer paid fees 122 are based at the package 132 header level. TN package items 144 can be changed directly (addition or removal of TN supplier offering 180) as time goes on and offerings change, instead of continually modifying a collection of TN customer benefits 120.
A TN package 132 may be either a managed 138 or not managed 140 package. If it is a managed package 138, a purchase volume commitment is required from the customer and the TN BPM will track progress against the commitment. If a package 132 is an unmanaged package 140, there is no commitment requirement and no tracking of actual purchases (other than for fee calculation purposes).
A managed TN package 138 is managed by trading network 100 and is a subtype of the TN package entity 132 which is defined with reference to the following parameter.
An unmanaged TN package 140 is a trading network package 132 that can be used without any corresponding customer commitment. It is a subtype of the TN package entity 132. As is represented by relationship 83, managed TN package 138 requires one or many TN customer volume commitments 114, each of which pertains to zero or one package entities 138.
A TN package 132 will be either a standard package 128 or a customized package 126. If it is customized, it is set up just for a particular customer and can only be assigned as a benefit to predefined set of companies. If it is standard, then it can be assigned to any TN customer member entity 108. The TN packages 132 assigned to each customer 110 are determined by trading network 100 (not the customer).
A custom TN package 126 is a trading network package that has been customized for one given set of customer members 108. This is a subtype entity of the TN package entity 144. A standard TN package 128 is a standard or general trading network package 132 that can be assigned as a benefit 120 to any valid customer 110. This is a subtype of the TN package entity 132. As is represented by line 85, a custom TN package 126 is customized for one or many TN package group members 118, each of which pertains to one and only one custom TN package 126.
A TN package group member 118 is one of the set of customer members 108 for whom a given TN package 132 has been customized. It is defined with reference to the following parameters.
As is represented by relationship 79, a TN package group member is customized for one and only one TN customer membership entity 108, which in turn includes zero, one or more TN package group members 118.
The Customers 110
A given company 110 can become a customer member 108 of multiple trading networks 100 by entering into a contract including such provisions as duration of membership and planned billing frequency. As is represented by relationship 45, trading network 100 obtains services as one or many companies 110, and each company 110 pertains to zero or one trading networks 100. As is represented by relationship 75, company 110 participates in one or many TN customer membership contract line item entities 108, each of which pertains in turn to one and only one company 110.
The TN customer membership entity 108 is a legal agreement or contract between a trading network 100 and a participating customer company 110. Entity 108 is defined with reference to the following parameters.
As is represented by relationship 81, TN customer membership entity 108 allows use of one or many TN customer benefits 120, each of which pertains to one and only one membership entity 108.
The benefit provided to customer members by the trading network is the ability to use selected packages 132 of the trading network portfolio items 148. Each defined benefit has a validity date range. The essence of a given purchase offering 158, including prices, delivery specifics, quality, etc., are the same for all TN customer members 108 who have the right to use that offering 158 since the terms negotiated use an aggregation of multiple customer forecasts 106, assuming there is no per-order tiered pricing. As is represented by relationship 41, trading network 100 negotiates by way of zero or many TN level forecasts 106, and each forecast 106 pertains to one and only one trading network 100.
A TN customer benefit 120 is a single line item of the customer agreement 108 with the trading network 100. It identifies a TN package 132 that the customer may enjoy as part of its membership. The benefit 120 is specific to a given validity time period, and is defined with respect to the following parameters.
As is represented by relationship 87, a TN customer benefit 120 may be charged by way of zero, one or many disclosed TN fee entities 122, each of which pertains to one and only one TN customer benefit 120. As is represented by relationship 89, TN customer benefit entity 120 allows use of one and only one TN package 132, each of which pertains to zero, one or many TN customer benefit entities 120.
A TN purchase offering 158 is a TN portfolio item 148 that allows use of a given purchasing resource, such as a catalog 152 or contract 160. This offering entity 158 is defined by the following field.
A catalog offering 154 is a TN portfolio item 148 that allows use of a specific catalog 152. This entity is defined by the following field.
As is represented by relationship 65, a catalog offering 154 allows use of one and only one catalog 152, and as is represented by relationships 65 and 63, catalog 152 pertains to zero, one or many catalog offerings 154 and zero, one or many catalog parts 150. As is represented by relationship 61, catalog part 150 is represented by one and only one commodity 116, and commodity 116 pertains to one or many catalog parts 150. As is represented by relationship 111, TN commodity 112 deals in one and only one commodity 116, and commodity 116 pertains to zero, one or many TN commodities 112.
A contract offering 160 is a TN portfolio item 148 that allows use of a specific contract or outline agreement. This entity is defined by the following field.
As is represented by relationship 69, contract offering 160 allows use of one and only one contract header 162, which header 162 may pertain to zero, one or many contract offerings 160.
A supplier preference offering 156 is a TN portfolio item 148 that allows a specific TN supplier 102 to be used as the preferred supplier for a given set of commodities 112. This entity 156 is defined with reference to the following field.
As is represented by relationship 51, supplier preference offering 156 allows use of one and only one TN supplier membership contract 104, and contract entity 104 may include zero, one or many supplier preference offerings 156.
A technology offering 164 is a TN portfolio item 148 that allows use of a given technical resource, such as a procurement e-services application. This entity 164 is defined with reference to the following field.
As is represented by relationship 73, technology offering 164 allows use of one and only one application 166, which as is represented by relationship 71 refers to one and only one installed application 168. Installed application 168 pertains to one or many applications 166, each of which pertains to one or many technology offerings 164.
Procurement business offering 174 is a TN portfolio item 148 that provides access to a procurement business process service, such as a full-buyer purchasing.
TN member benefits 120 include the ability to create requisitions directly from specific TN contracts. A TN member benefit includes the ability to create requisitions directly from specific trading network contracts (outline agreements) 160 and from specific TN versions of supplier catalogs 154, including both internal external (punch-out) catalogs.
Conversely, a TN member may have to make commodity-specific volume commitments in turn for getting some of the benefits. However, a given customer need not commit all of its volumes to an one trading network, and can split purchase between several.
A trading network commodity 112 is one valid commodity with which this trading network 100 deals. Entity 112 is defined by the following fields.
As is represented by relationship 43, trading network 100 deals in one or many TN commodities 112, and each TN commodity pertains to one and only one trading network 100. As is represented by relationship 55, TN commodity 112 aggregates purchase volumes projected in zero, one or many TN level forecasts 106, and each forecast 106 pertains to one and only one TN commodity 112. As is represented by relationship 57, a TN commodity 112 belongs to zero, one or many TN commodity group member entities 130, and each member entity 130 pertains to one and only one TN commodity 112. As is represented by relationship 59, the purchase volumes of TN commodity entity 112 are projected in zero, one or many TN customer volume commitment entities 114, an each commitment entity 114 pertains to one and only one TN commodity.
A trading network level forecast 106 is determined when the TN 100 negotiates contracts with a supplier member 102. It is created by gathering together the individual customer member volume commitments 114, in conjunction with analysis of any applicable procurement history or knowledge. A given forecast 106 pertains to a specific period of time. Forecast entity 106 is defined by (that is, with reference) the following fields (or, parameters).
As is represented by relationship 49, a TN level forecast 106 is awarded to one and only one TN supplier membership contract 104, and membership contract entity 104 may include zero or many TN level forecasts 106.
A TN customer volume commitment entity 114 is a forecast of the volumes for this commodity 112 that the customer 110 expects to purchase as part of its agreement 108 with the trading network 110. The estimation is specific to a given period of time, and is defined with reference to the following parameters.
As is represented by relationship 77, TN customer membership entity forecasts zero, one or many TN customer volume commitments 114, each of which pertains to one and only one TN customer membership entity 108.
The Suppliers 102, 104, 180
By entering into a white paper contract 104, a supplier 102 can become a supplier member of one or more trading networks 100. As is represented by relationship 47, a supplier 102 participates in one or many supplier membership contracts 104, and each membership contract 104 pertains to one and only one supplier 102. As is represented by relationship 35, TN 100 offers service as one or more suppliers 102, and a supplier 102 may be part of zero or one trading networks 100. As is represented by relationship 53, a given TN supplier offering 180 represents a single line item under a TN supplier membership contract 104. As is further represented by relationship 53, a given TN supplier offering 180 is owned by only one trading network 100, and it is an item 148 in its portfolio. A given TN supplier offering 180 is committed from only one supplier 102. Undisclosed TN agent fees 142 allow any given TN supplier offering 180 to be modified to include TN fees on top of supplier prices. As there may be different levels of the same base offering, then each different level is a different offering and it is important to ensure that a given customer member does not get assigned to different versions of the same base offering.
A TN supplier membership 104 is an agreement, contract or understanding between a trading network 100 and a participating supplier 102. It is defined with reference to the following parameters.
Paying for Trading Network Value Add 134, 142, 122
The fee 134 for TN services may be disclosed to the customer or they may be undisclosed. Disclosed TN fees 122 are based at the customer benefit 120 level and are paid directly to the trading network 100 by the customer 110 on the assumption that it would be illogical to involve the supplier 102 in rebating fees that have been disclosed to the customer 110. Undisclosed fees 142 are based at the TN portfolio item 148 level. In some cases, the trading network's portion or value-add-fee will be included (hidden) in the purchase prices presented to customer 110 but fees for TN offered items 178 (those not from suppliers) are disclosed. Both disclosed and undisclosed fees may be combined on the same customer benefit 120.
A disclosed fee 122 is a trading network value-add fee that the customer will knowingly pay to the trading network 100 whenever this TN customer benefit 120 is used. It is defined with reference to the following parameters.
An undisclosed fee 142 is a trading network value-add fee that the customer will unknowingly pay to the trading network 100 whenever this TN portfolio item 148 is used. In the case of purchase offering 158, for example, this fee 142 is added onto the product prices before they are seen by the customer. When this is an item 148 whose fee is to be rebated from supplier 102, this is what has been negotiated with the supplier. This entity 142 is defined with reference to the following fields.
As is represented by relationship 99, an undisclosed TN fee is charged via one TN portfolio item 148.
There are different types of fees 134 that can be assessed. These different types of fees may be combined on the same benefit 120 or portfolio 148 item. Fee type entity 134 defines the various types of fees that can be levied by TN at the TN customer benefit 120 and TN portfolio item levels, and includes the following fields.
As is represented by relationships 91 and 95, fee type 134 defines zero or many disclosed TN fee entities 122 and zero one or many undisclosed TN fee entities 142, respectively.
A subscription fee is a flat periodic charge for a given customer benefit 120, one that is assessed whether or not the customer took advantage of the service. Such a fee involves no special calculations, would never be undisclosed, and would be based on the billing frequency defined in the customer membership agreement 108.
A TN agent fee represents a percentage of amount purchased that is paid to the trading network. This type of fee may be either disclosed or undisclosed, and must be tracked. That is, actual invoices are tracked back to their originating customer benefit 120 and/or TN supplier offering 180.
TN agent fee=invoice total*fee percentage.
A per-service unit fee is a flat amount charged for each procurement service performed, and would require the use of an accompanying service UOM definition. Such a fee type would normally not be undisclosed. It is necessary to track documents or other service instances back to their originating customer benefit 120 in order to calculate this fee.
Per-service fee=actual service count*per-service unit fee.
Similar to the per-service unit fee, a per-tech unit fee is a flat amount charged for each use of a tech offering 164. Whenever this is used, there would be an accompanying tech UOM definition specifying what is the tech unit—a web site hit, a txn, a mip; or so forth. This type of fee may be either disclosed or undisclosed. It is necessary to track actual IT usage and trace back to its corresponding customer benefit 120 and/or TN portfolio item 148 to calculate this fee.
Per-tech fee=actual tech unit count*per-tech unit fee.
Several different types of customer payment flows are based at the TN portfolio item 148 or supplier offering 180 level.
Payment for TN supplier offerings 180 can be made (1) from the customer directly to the supplier member 102, with any TN fee paid separately to the TN 100; (2) directly to the supplier member 102, with a TN 100 fee rebated from the supplier 102 to the TN 100; or (3) directly to the TN 100 with a corresponding TN 100 payment to the supplier member 102. The second payment type would be part of the TN agreement with the supplier 102, so it would not be able to vary among the TN customer members at the benefit 120 level to whom the offering 180 is assigned. Any variation in fee here would necessitate a separate TN supplier offering 180.
Payment for TN offered items 178 (those not coming from a supplier 102) are made directly to the trading network 100. Some TN services may be charged to the supplier 102, not the customer 110.
A common data administration function assures that no TN violations exist in more detailed data. Thus, if a given company 110 does not have access to a given TN portfolio item 148, such as a supplier catalog 152, then a plant within that company is not to be assigned to that catalog. An employee of a non-benefited company 110 is not to have access to an outline agreement or be able to use a given application tech service or use any other procurement services from the TN 100.
The time limitations previously described are exploded down to the detail level, so batch programs are provided to clean up administration data when packages 132 or benefits 120 expire such that a company which is an active member of a trading network 100 uses only those suppliers 102 who are active members of the same trading network(s) 100, a plant may use a catalog only if that catalog is part of an active package 132 and the plant's company 110 has an active subscription to that package, and an employee or department or company may use a contract only if that contract is part of an active package 132 and the plant's company 110 has an active subscription to the package.
It is an advantage of the invention that there is provided an improved system and method for managing relationships between suppliers and customers within a trading network.
It is a further advantage of the invention that there is provided a single trading network method and system facilitating business exchanges for multiple trading networks.
It is a further advantage of the invention that there is provided a system and method for managing a trading network so as to combine sales and buying perspectives.
It is a further advantage of the invention that there is provided a system and method for managing a trading network so as to allow purchase of goods from a catalog, contract, supplier preference or request for quote.
It is a further advantage of the invention that there is provided a system and method for managing a trading network having a membership fee based on straight subscription, per transaction or including agent fees.
It is a further advantage of the invention that there is provided a system and method for managing a trading network which provides for automated membership term management (dropping sub-packages which expire), ensuring coverage of other sub-packages whose initial supplier has terminated its participation.
It is a further advantage of the invention that there is provided a system and method for managing a trading network which supports many combinations of services, including information technology (IT) hosting alone, or combined with application management and sourcing and procurement business process management.
It will be appreciated that, although specific embodiments of the invention have been described herein for purposes of illustration, various modifications may be made without departing from the spirit and scope of the invention. In particular, it is within the scope of the invention to provide a computer program product or program element comprising executable instructions recorded on a physical storage or memory device such as a magnetic or optical tape or disc, or the like, for storing signals readable by a machine, for controlling the operation of a computer according to the method of the invention and/or to structure its components in accordance with the system of the invention.
Further, each step of the method may be executed on any general computer, such as an IBM System 390, AS/400, PC or the like and pursuant to one or more, or a part of one or more, program elements, modules or objects generated from any programming language, such as C++, Java, Pl/1, Fortran or the like. And still further, each said step, or a file or object or the like implementing each said step, may be executed by special purpose hardware or a circuit module designed for that purpose.
Accordingly, the scope of protection of this invention is limited only by the following claims and their equivalents.
This application is a divisional application claiming priority of Ser. No. 13/184,682, filed Jul. 18, 2011, now U.S. Pat. No. 8,332,280, issued Dec. 11, 2012, which is a divisional application claiming priority of Ser. No. 11/807,324, filed May 25, 2007, U.S. Pat. No. 7,983,958, issued Jul. 19, 2011, which is a divisional of Ser. No. 09/798,598, filed Mar. 2, 2001, U.S. Pat. No. 7,243,077, issued Jul. 10, 2007.
Number | Name | Date | Kind |
---|---|---|---|
4799156 | Shavit et al. | Jan 1989 | A |
4947028 | Gorog | Aug 1990 | A |
5021953 | Webber et al. | Jun 1991 | A |
5117356 | Marks | May 1992 | A |
5168444 | Cukor et al. | Dec 1992 | A |
5189608 | Lyons et al. | Feb 1993 | A |
5319542 | King et al. | Jun 1994 | A |
5335169 | Chong | Aug 1994 | A |
5361393 | Rossillo | Nov 1994 | A |
5390113 | Sampson | Feb 1995 | A |
5544298 | Kanavy et al. | Aug 1996 | A |
5640550 | Coker | Jun 1997 | A |
5666493 | Wojcik et al. | Sep 1997 | A |
5694551 | Doyle et al. | Dec 1997 | A |
5712989 | Johnson et al. | Jan 1998 | A |
5715453 | Stewart | Feb 1998 | A |
5721832 | Westrope et al. | Feb 1998 | A |
5737592 | Nguyen et al. | Apr 1998 | A |
5758327 | Gardner et al. | May 1998 | A |
5758351 | Gibson et al. | May 1998 | A |
5781908 | Williams et al. | Jul 1998 | A |
5794207 | Walker et al. | Aug 1998 | A |
5799151 | Hoffer | Aug 1998 | A |
5802518 | Karaev et al. | Sep 1998 | A |
5815829 | Zargar | Sep 1998 | A |
5838906 | Doyle et al. | Nov 1998 | A |
5838916 | Domenikos et al. | Nov 1998 | A |
5870717 | Wiecha | Feb 1999 | A |
5918017 | Attanasio et al. | Jun 1999 | A |
5963922 | Helmering | Oct 1999 | A |
5963925 | Kolling et al. | Oct 1999 | A |
5970475 | Barnes et al. | Oct 1999 | A |
5974407 | Sacks | Oct 1999 | A |
6003039 | Barry et al. | Dec 1999 | A |
6006204 | Malcolm | Dec 1999 | A |
6014134 | Bell et al. | Jan 2000 | A |
6016394 | Walker | Jan 2000 | A |
6023683 | Johnson et al. | Feb 2000 | A |
6023729 | Samuel et al. | Feb 2000 | A |
6029150 | Kravitz | Feb 2000 | A |
6032130 | Alloul et al. | Feb 2000 | A |
6032145 | Beall et al. | Feb 2000 | A |
6032150 | Nguyen | Feb 2000 | A |
6047268 | Bartoli et al. | Apr 2000 | A |
6052785 | Lin et al. | Apr 2000 | A |
6055516 | Johnson et al. | Apr 2000 | A |
6055519 | Kennedy et al. | Apr 2000 | A |
6058373 | Blinn et al. | May 2000 | A |
6058380 | Anderson et al. | May 2000 | A |
6058381 | Nelson | May 2000 | A |
6064977 | Haverstock et al. | May 2000 | A |
6094654 | Van Huben et al. | Jul 2000 | A |
6104717 | Coile et al. | Aug 2000 | A |
6112242 | Jois et al. | Aug 2000 | A |
6115690 | Wong | Sep 2000 | A |
6125363 | Buzzeo et al. | Sep 2000 | A |
6128602 | Northington et al. | Oct 2000 | A |
6144991 | England | Nov 2000 | A |
6151608 | Abrams | Nov 2000 | A |
6163805 | Silva et al. | Dec 2000 | A |
6185545 | Resnick et al. | Feb 2001 | B1 |
6199113 | Alegre et al. | Mar 2001 | B1 |
6208345 | Sheard et al. | Mar 2001 | B1 |
6219680 | Bernardo et al. | Apr 2001 | B1 |
6239797 | Hills et al. | May 2001 | B1 |
6240399 | Frank et al. | May 2001 | B1 |
6260024 | Shkedy | Jul 2001 | B1 |
6269343 | Pallakoff | Jul 2001 | B1 |
6285986 | Andrews | Sep 2001 | B1 |
6314408 | Salas et al. | Nov 2001 | B1 |
6317751 | Yeger et al. | Nov 2001 | B1 |
6330575 | Moore et al. | Dec 2001 | B1 |
6336114 | Garrison | Jan 2002 | B1 |
6343284 | Ishikawa et al. | Jan 2002 | B1 |
6343287 | Kumar et al. | Jan 2002 | B1 |
6356283 | Guedalia | Mar 2002 | B1 |
6360211 | Anderson et al. | Mar 2002 | B1 |
6381644 | Munguia et al. | Apr 2002 | B2 |
6401120 | Gamache et al. | Jun 2002 | B1 |
6418415 | Walker et al. | Jul 2002 | B1 |
6418420 | DiGiorgio et al. | Jul 2002 | B1 |
6418467 | Schweitzer et al. | Jul 2002 | B1 |
6430538 | Bacon et al. | Aug 2002 | B1 |
6449744 | Hansen | Sep 2002 | B1 |
6452609 | Katinsky et al. | Sep 2002 | B1 |
6453353 | Win et al. | Sep 2002 | B1 |
6460041 | Lloyd | Oct 2002 | B2 |
6466949 | Yang et al. | Oct 2002 | B2 |
6466980 | Lumelsky et al. | Oct 2002 | B1 |
6477510 | Johnson | Nov 2002 | B1 |
6486891 | Rice | Nov 2002 | B1 |
6499036 | Gurevich | Dec 2002 | B1 |
6507826 | Maners | Jan 2003 | B1 |
6516327 | Zondervan et al. | Feb 2003 | B1 |
6523027 | Underwood | Feb 2003 | B1 |
6535294 | Arledge, Jr. et al. | Mar 2003 | B1 |
6539396 | Bowman-Amuah | Mar 2003 | B1 |
6578068 | Bowman-Amuah | Jun 2003 | B1 |
6589290 | Maxwell et al. | Jul 2003 | B1 |
6594819 | Ciarlante et al. | Jul 2003 | B1 |
6601084 | Bhaskaran et al. | Jul 2003 | B1 |
6606643 | Emens et al. | Aug 2003 | B1 |
6611822 | Beams et al. | Aug 2003 | B1 |
6631382 | Kouchi et al. | Oct 2003 | B1 |
6631402 | Devine et al. | Oct 2003 | B1 |
6643690 | Duursma et al. | Nov 2003 | B2 |
6668253 | Thompson et al. | Dec 2003 | B1 |
6681229 | Cason et al. | Jan 2004 | B1 |
6684384 | Bickerton et al. | Jan 2004 | B1 |
6686932 | Rath et al. | Feb 2004 | B2 |
6687731 | Kavak | Feb 2004 | B1 |
6704612 | Hahn-Carlson | Mar 2004 | B1 |
6725264 | Christy | Apr 2004 | B1 |
6760775 | Anerousis et al. | Jul 2004 | B1 |
6772167 | Snavely et al. | Aug 2004 | B1 |
6785822 | Sadhwani-Tully | Aug 2004 | B1 |
6801949 | Bruck et al. | Oct 2004 | B1 |
6826542 | Virgin et al. | Nov 2004 | B1 |
6834294 | Katz | Dec 2004 | B1 |
6839680 | Liu et al. | Jan 2005 | B1 |
6847953 | Kuo | Jan 2005 | B2 |
6853630 | Manning | Feb 2005 | B1 |
6882983 | Furphy et al. | Apr 2005 | B2 |
6886134 | Cason | Apr 2005 | B1 |
6922671 | Musa et al. | Jul 2005 | B2 |
6928411 | Fox et al. | Aug 2005 | B1 |
6934690 | Van Horn et al. | Aug 2005 | B1 |
6947063 | Cirulli et al. | Sep 2005 | B1 |
6950983 | Snavely | Sep 2005 | B1 |
6965938 | Beasley et al. | Nov 2005 | B1 |
6971107 | Sjostrom et al. | Nov 2005 | B2 |
7003474 | Lidow | Feb 2006 | B2 |
7133868 | Ruest et al. | Nov 2006 | B1 |
7155403 | Cirulli et al. | Dec 2006 | B2 |
7171374 | Sheehan et al. | Jan 2007 | B1 |
7197480 | Chollon et al. | Mar 2007 | B1 |
7243077 | Broden et al. | Jul 2007 | B2 |
7266503 | Cason et al. | Sep 2007 | B2 |
7283976 | Aber et al. | Oct 2007 | B2 |
7349879 | Alsberg et al. | Mar 2008 | B2 |
7356496 | Kane et al. | Apr 2008 | B2 |
7363246 | Van Horn et al. | Apr 2008 | B1 |
7386495 | Cirulli et al. | Jun 2008 | B2 |
7835956 | Aber et al. | Nov 2010 | B2 |
7848970 | Kane et al. | Dec 2010 | B2 |
7895095 | Chollon et al. | Feb 2011 | B2 |
7983958 | Broden et al. | Jul 2011 | B2 |
8027892 | Baumann et al. | Sep 2011 | B2 |
8219460 | Mesaros | Jul 2012 | B1 |
8229814 | Baumann et al. | Jul 2012 | B2 |
20010011222 | McLauchlin et al. | Aug 2001 | A1 |
20010032162 | Aisberg et al. | Oct 2001 | A1 |
20010051913 | Vashistha et al. | Dec 2001 | A1 |
20020019740 | Matsuo et al. | Feb 2002 | A1 |
20020055878 | Burton et al. | May 2002 | A1 |
20020065736 | Willner et al. | May 2002 | A1 |
20020065885 | Buonanno et al. | May 2002 | A1 |
20020087441 | Wagner, Jr. et al. | Jul 2002 | A1 |
20020091597 | Teng | Jul 2002 | A1 |
20020093538 | Carlin | Jul 2002 | A1 |
20020103731 | Barnard et al. | Aug 2002 | A1 |
20020107890 | Gao et al. | Aug 2002 | A1 |
20020128944 | Crabtree et al. | Sep 2002 | A1 |
20020138281 | Cirulli et al. | Sep 2002 | A1 |
20020138658 | Sjostrom et al. | Sep 2002 | A1 |
20020143699 | Baumann et al. | Oct 2002 | A1 |
20020161606 | Bennett et al. | Oct 2002 | A1 |
20020161667 | Felkey et al. | Oct 2002 | A1 |
20020184111 | Swanson | Dec 2002 | A1 |
20020184125 | Cirulli et al. | Dec 2002 | A1 |
20030074580 | Knouse et al. | Apr 2003 | A1 |
20030093320 | Sullivan | May 2003 | A1 |
20030139996 | D'Antoni et al. | Jul 2003 | A1 |
20030187688 | Fey et al. | Oct 2003 | A1 |
20030220875 | Lam et al. | Nov 2003 | A1 |
20040015367 | Nicastro et al. | Jan 2004 | A1 |
20040078275 | Ismert et al. | Apr 2004 | A1 |
20050097016 | Barnard et al. | May 2005 | A1 |
20070179894 | Cirulli et al. | Aug 2007 | A1 |
20080071653 | Cirulli et al. | Mar 2008 | A1 |
Number | Date | Country |
---|---|---|
2082814A | Mar 1982 | GB |
WO 9849639 | Nov 1998 | WO |
Entry |
---|
Lotus Development Corp., an IBM Subsidiary. Lotus Domino: Application Development with Domino Designer, Rel. 5. USA, privately printed, 1998. i-vii, 425-430. |
Lotus Development Corp., an IBM Subsidiary. Lotus Domino: Domino Enterprise Integration Guide, Rel. 5. USA, privately printed, 1998. 9-20, 107-122, 444-451. |
Berners-Lee et al.,; “Uniform Resource Locators (URL)”; Request for Comments (RFC) 1738; Dec. 1994. |
Brown et al.; “Mastering Lotus Notes”; pp. 6-15, 486-483; ISBM 0782113028; 1995. |
Tewari et al.; “High Availability in Clustered Multimedia Servers”; Proceedings of the Twelfth International Conference on Data Engineering; pp. 645-654; Feb. 1996. |
Cardellini et al.; “Redirection algorthims for load sharing in distributed Web-server systems”; Proceedings. 19th IEEE International Conference on Distributed Computing Systems; pp. 528-535; May 1999. |
John D'Esposito. Proxy Pass Implementation in GWA. Undated. 13 pages. Published before Sep. 6, 2000 on the Internet at <htt;://w3.ibm.com/media/juke/presenter/gwa/proxy/proxy.html>. |
Sun Microsystems, Inc. Java 2 Enterprise Edition Technical Documentation. Copyright 1999. 1 page. |
Sun Microsystems, Inc. Java 2 Enterprise Edition Developer's Guide. Copyright 1999. Table of Contents (7 pages) and Chapter 8 “Security” (10 pages). |
Dynamic HTML in Action Written by William J. Pardi and Eric Schurmann, 1998. |
Gershenfeld, Nancy; “Client-server: What Is It and Are We There Yet?” Online. Medford: Mar. 1995, vol. 19, Iss. 2; p. 60, 6 pages. |
University of New Hampshire Financial and Administrative Procedures, 1994, 11 pages. |
Minnesota Statewide Administrative Systems webpage describing three way match, Jun. 29, 1995, 1 page. |
US Dept. of Energy, I-Manage Stars Funtional and Technical Requirements, Sep. 2000, 54 pages. |
X12 Transaction Set Index Version 3040, undated, 4 pages. |
All Open Orders for Customer, Nov. 23, 1999, Motorola. |
Elaine Marmel and Diane Koers, Peachtree 8 for Dummies, © 2000, Hungry Minds, Inc. |
David Kroenke, Database Processing, © 1983, 1977, Science Research Associates, Inc. |
Deitel & Deitel, Java How to Program, © 1998, 1997, Prentice-Hall. |
State of Texas Statewide Electronic Commerce Feasibility Study; May 15, 1998; Phoenix Planning & Evaluation, Ltd. Rockville, MD 20852.x. |
Yehuda Shiran; Sharing functions between frames, Jul. 29, 2000. |
JavaScrip and Frames, Part II—The Famous Memory Game, Apr. 5, 1999. |
Tom Negrino, JavaScript for the World Wide Web: Visual QuickStar Guide (3rd Edition), 2000. |
Baron et al.,; “Web-based E-catalog systems inB2B procurement”, Association for Computing Machinery, May 2000, vol. 43 No. 5, p. 93+. |
van Riel et al.; “Exploring consumer evaluations of e-services: a portal site”, International Journal of Service Industry Management, 2001, vol. 12 No. 3, p. 359+. |
USBI bill dated Jul. 22, 1998. two web site pages with background on USBI (www.billview.com and www.billingconcepts.com). |
Valentine, Lisa. “Banks' accounting systems showing their age.” Bank Technology News Nov. 1, 1998: Banking Information Source, ProQuest. Web. Jul. 13, 2010. |
[Annotated] www.demandonline.com. Feb. 26, 2000 to Oct. 31, 2000; 19 pages. |
Office Action (Mail Date Oct. 8, 2010) for U.S. Appl. No. 11/807,324, filed May 25, 2007, First Named Inventor Theresa W. Broden. |
Notice of Allowance (Mail Date Mar. 3, 2011) for U.S. Appl. No. 11/807,324, filed May 25, 2007. |
Notice of Allowance (Mail Date May 20, 2011) for U.S. Appl. No. 09/819,462, filed Mar. 28, 2001. |
Office Action (Mail Date Mar. 30, 2009) for U.S. Appl. No. 09/819,462, filed Mar. 28, 2001, First Named Inventor Carl Steven Baumann. |
Office Action (Mail Date Jun. 8, 2010) for U.S. Appl. No. 11/643,193, filed Dec. 21, 2006, First Named Inventor Susan Bumgardner Cirulli. |
Office Action (Mail Date Mar. 18, 2010) for U.S. Appl. No. 11/643,193, filed Dec. 21, 2006, First Named Inventor Susan Bumgardner Cirulli. |
Office Action (Mail Date Mar. 2, 2010) for U.S. Appl. No. 11/643,193, filed Dec. 21, 2006, First Named Inventor Susan Bumgardner Cirulli. |
Office Action (Mail Date Jan. 20, 2011) for U.S. Appl. No. 11/983,111, filed Nov. 6, 2007, First Named Inventor Susan Bumgardner Cirulli. |
Office Action (Mail Date Oct. 27, 2010) for U.S. Appl. No. 11/983,111, filed Nov. 6, 2007, First Named Inventor Susan Bumgardner Cirulli. |
“IBM and MarketMile Forge e-business on Demand Alliance”. Business Editors/High-Tech Writers. Business Wire. Feb 19, 2002. |
“Supply Side e-conomics”. Duey, Rhonda. Oil and Gas Investor. May 2000. |
Office Action (Mail Date Sep. 21, 2011) for U.S. Appl. No. 13/198,755, filed Aug. 5, 2011. |
Notice of Allowance (Mail Date Mar. 9, 2012) for U.S. Appl. No. 13/198,755, filed Aug. 5, 2011. |
Notice of Allowance (Mail Date Aug. 6, 2012) for U.S. Appl. No. 13/184,682, filed Jul. 18, 2011. |
Number | Date | Country | |
---|---|---|---|
20130006836 A1 | Jan 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11807324 | May 2007 | US |
Child | 13184682 | US | |
Parent | 09798598 | Mar 2001 | US |
Child | 11807324 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13184682 | Jul 2011 | US |
Child | 13611122 | US |