IP Library Granted Patent US 9,003,064
Granted Patent B2
US 9,003,064 · App. 12/878,879 · Granted Apr 7, 2015

Management of B2B communities

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,003,064
App. No.
12/878,879
Granted
Apr 7, 2015
Kind
B2
Abstract

A method for managing a B2B electronic commerce community, wherein a plurality of B2B partners interact with a hub entity via a plurality of B2B applications, includes receiving interaction information describing interactions of a B2B partner with at least one of the B2B applications. The interaction information may describe a material flow, correspondence, transactions, notices, relationships, and so forth, between the B2B partner and the hub. Based at least in part on the received interaction information, the method develops a community manager that supports a common set of community management modules in communication with each of the B2B applications and maintains a single, hub-wide view of each of the B2B partners. The modules may include, as examples, modules for new partner on-boarding, community maintenance, improvement, and networking including social network tooling.

Claims (41)

1. A non-transitory computer readable medium including stored, processor executable instructions that, when executed by a processor, cause the processor to perform operations comprising:

receiving interaction information describing communications of a business-to-business (B2B) partner including first partner communications with a first B2B application and second partner communications with a second B2B application, wherein the first B2B application interacts with a first hub application and the second B2B application interacts with a second hub application, different than the first hub application, wherein the interaction information describes at least one of: material flow, correspondence, transactions, notices, and relationships between the B2B partner and the hub;

processing the interaction information to generate a single unified view of the B2B, wherein the first hub application and the second hub application both access the single unified view of the B2B partner;

based in part on the received interaction information, developing a community manager, the community manager supporting a common set of modules in communication with each of the B2B applications; and

implementing the common set of modules to facilitate, with respect to each applicable B2B application, on-boarding of new B2B partners, establishing a single unified view of each of the B2B partners, and automated maintenance of B2B partnerships.

2. The computer readable medium of claim 1 , wherein each of the plurality of B2B applications accesses the interaction information via the single unified view of the B2B partner.

3. The computer readable medium of claim 1 , wherein the first hub application comprises a supply chain management application and the second hub application comprises either a customer relationship management application or an enterprise resource planning application.

4. The computer readable medium of claim 3 , wherein the first B2B application is an application for facilitating electronic data interchange (EDI) transactions between the hub and the B2B partner.

5. The computer readable medium of claim 1 , wherein the community manager includes an on-boarding module implementing policies to facilitate the establishment of an electronic relationship with a new B2B partner.

6. The computer readable medium of claim 5 , wherein the on-boarding module implements policies to provide self-service establishment of an electronic relationship by the new B2B partner.

7. The computer readable medium of claim 5 , wherein the on-boarding module implements policies to enable a B2B partner to test operation of a transaction.

8. The computer readable medium of claim 1 , wherein the community manager includes a maintenance module implementing procedures for maintaining an electronic relationship between the B2B partner and the hub, wherein the maintenance module is configured to monitor transactions between the B2B partner and the hub, establish criteria for generating transaction alerts, generate alerts pursuant to the established criteria, and resolve any contention between the B2B partner and the hub arising from a transaction.

9. The computer readable medium of claim 8 , wherein the maintenance module is configured to track transactions with the B2B partner for compliance with a service level agreement between the B2B partner and the hub.

10. The computer readable medium of claim 8 , wherein the community manager includes a partnership improvement module to measure statistics associated with transactions between the B2B partner and the hub, analyze the transaction statistics, and, responsive to the transaction statistics suggesting an area of concern, modify aspects of the maintenance module to address the area of concern.

11. The computer readable medium of claim 1 , wherein the community manager includes a community improvement module configured to implement policies to identify potential B2B partners and collaborate with existing B2B partners through electronic dialogue.

12. In a business-to-business (B2B) electronic commerce community, wherein a plurality of B2B partners interact with a hub via a plurality of B2B applications, a method of managing the community, the method comprising:

receiving interaction information describing communications of a B2B partner including first partner communications with a first B2B application and second partner communications with a second B2B application, wherein the first B2B application interacts with a first hub application and the second B2B application interacts with a second hub application, different than the first hub application, wherein the interaction information describes at least one of: material flow, correspondence, transactions, notices, and relationships between the B2B partner and the hub;

processing the interaction information to generate a single unified view of the B2B partner, wherein the first hub application and the second hub application both access the single unified view of the B2B partner;

based in part on the received interaction information, developing a community manager, the community manager supporting a common set of modules in communication with each of the B2B applications; and

implementing the common set of modules to facilitate, with respect to each applicable B2B application, on-boarding of new B2B partners, establishing a single unified view of each of the B2B partners, and automated maintenance of B2B partnerships.

13. The method of claim 12 , wherein the interaction information includes first interaction information indicative of the B2B partner invoking the first B2B application and second interaction information indicative of the B2B partner invoking the second B2B application and wherein the first B2B application is an application for facilitating electronic data interchange (EDI) transactions between the hub and the B2B partner.

14. The method of claim 12 , further comprising developing a community manager, including a common set of B2B community management modules, in communication with each of the B2B applications, wherein the community manager includes an on-boarding module implementing policies to facilitate the establishment of an electronic relationship with a new B2B partner.

15. The method of claim 14 , wherein the community manager further includes a maintenance module for:

monitoring transactions between the B2B partner and the hub;

establishing criteria for generating transaction alerts;

generating alerts pursuant to the established criteria;

resolving any contention between the B2B partner and the hub arising from a transaction; and

tracking transactions with the B2B partner for compliance with a service level agreement between the B2B partner and the hub.

16. The method of claim 15 , wherein the community manager further includes a partnership improvement module, wherein the improvement module to measure statistics associated with transactions between the B2B partner and the hub, analyze the transaction statistics, and, responsive to the transaction statistics suggesting an area of concern, modifying aspects of the maintenance module to address the area of concern.

17. The method of claim 14 , wherein the community manager includes a community improvement module configured to implement policies to identify potential B2B partners and collaborate with existing B2B partners through electronic dialogue.

18. The method of claim 17 , wherein the community improvement module includes a social network module configured to enable at least one of: contact linking, forums, blogs, and bulletin boards.

19. A data processing apparatus, comprising a processor, a non-transitory computer readable storage medium accessible to the processor, the computer readable storage medium including stored, processor executable instructions that, when executed by a processor, cause the processor to perform operations comprising:

receiving interaction information describing communications of a business-to-business (B2B) partner including first partner communications with a first B2B application and second partner communications with a second B2B application, wherein the first B2B application interacts with a first hub application and the second B2B application interacts with a second hub application, different than the first hub application, wherein the interaction information describes at least one of: material flow, correspondence, transactions, notices, and relationships between the B2B partner and the hub;

processing the interaction information to generate a single unified view of the B2B partner, wherein the first hub application and the second hub application both access the single unified view of the B2B partner;

based in part on the received interaction information, developing a community manager, the community manager supporting a common set of modules in communication with each of the B2B applications; and

implementing the common set of modules to facilitate, with respect to each applicable B2B application, on-boarding of new B2B partners, establishing a single unified view of each of the B2B partners, and automated maintenance of B2B partnerships.

20. The apparatus of claim 19 , wherein the community manager includes:

an on-boarding module implementing policies to facilitate the establishment of an electronic relationship with a new B2B partner;

a maintenance module for maintaining an electronic relationship between each B2B partner and the hub, wherein the maintenance module is configured to monitor transactions between B2B partners and the hub, establish criteria for generating transaction alerts, generating alerts pursuant to the established criteria, and resolving contention between the B2B partners and the hub arising from the transaction;

a partnership improvement module to measure statistics associated with transactions between the B2B partner and the hub, analyze the transaction statistics, and, responsive to the transaction statistics suggesting an area of concern, modifying aspects of the maintenance module to address the area of concern; and

a community improvement module to identify potential B2B partners and collaborate with existing B2B partners through electronic dialogue, the electronic dialogue including a social network module configured to enable at least one of: contact linking, forums, blogs, and bulletin boards.

Assignments (10)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 26, 2021
From: SOFTWARE LABS CAMPUS UNLIMITED COMPANY
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 056396/0942 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 11, 2020
From: IBM TECHNOLOGY CORPORATION
To: SOFTWARE LABS CAMPUS UNLIMITED COMPANY
Reel/Frame 053452/0537 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOULY LISTED PATENT ON THE SCHEDULE A. PATENT NUMBER 7,792,767 WAS REMOVED FROM THE SCHEDULE A. PREVIOUSLY RECORDED AT REEL: 051170 FRAME: 0255. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 19, 2020
From: IBM INTERNATIONAL GROUP B.V.
To: IBM INTERNATIONAL C.V.
Reel/Frame 052190/0394 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUSLY LISTEDPATENT ON THE SCHEDULE A. PATENT NUMBER 7,792,767WAS REMOVED FROM THE SCHEDULE A PREVIOUSLY RECORDED ON REEL 051170 FRAME 0722. ASSIGNOR(S) HEREBY CONFIRMS THE PATENTNUMBER 7,792,767 WAS ERRONEOUSLY LISTED ON THESCHEDULE A. Recorded Mar 19, 2020
From: IBM INTERNATIONAL L.P.
To: IBM TECHNOLOGY CORPORATION
Reel/Frame 052190/0464 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUS LISTED PATENT NUMBER 7,792,767 ON THE SCHEDULE A PREVIOUSLY RECORDED AT REEL: 051170 FRAME: 0745. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 19, 2020
From: IBM INTERNATIONAL C.V.
To: IBM INTERNATIONAL L.P.
Reel/Frame 052190/0986 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2019
From: IBM INTERNATIONAL GROUP B.V.
To: IBM INTERNATIONAL C.V.
Reel/Frame 051170/0255 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2019
From: IBM INTERNATIONAL L.P.
To: IBM TECHNOLOGY CORPORATION
Reel/Frame 051170/0722 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 3, 2019
From: IBM INTERNATIONAL C.V.
To: IBM INTERNATIONAL L.P.
Reel/Frame 051170/0745 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2011
From: STERLING COMMERCE, INC.
To: IBM INTERNATIONAL GROUP BV
Reel/Frame 027024/0247 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 12, 2010
From: MARGO, TODD L.; BLANKENBAKER, DIANNE K.; MIDDLEBROOK, GEORGE MICHAEL
To: STERLING COMMERCE, INC.
Reel/Frame 025128/0035 →