US20120323720A1

US20120323720A1 - Managing an experience of a member organization of a collaborative commerce community through a network

Info

Publication number: US20120323720A1
Application number: US13/600,389
Authority: US
Inventors: Steve Markle; Gopal Sundaram; Kshitij Dayal; Olaf Erik Gregor Schrader; Abhishek Bhadoria
Original assignee: Ariba Inc
Current assignee: Ariba Inc
Priority date: 2011-05-22
Filing date: 2012-08-31
Publication date: 2012-12-20
Also published as: US9990634B2

Abstract

Embodiments for methods, systems and apparatuses for managing a member organization experience of a collaborative commerce community through a network are disclosed. One method includes managing buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst the buyer organizations and the seller organizations associated with the network, wherein the member organization is at least one of the plurality of seller organizations or the plurality buyer organizations. The method further includes providing unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations, determining an intra-organization link between users of the member organization based on the collaborative interactions of the member organization and a subset of the plurality of buyer organizations or a subset plurality of seller organizations.

Description

RELATED APPLICATIONS

This patent application is a continuation-in-part (CIP) of U.S. patent application Ser. No. 13/270,189, filed Oct. 10, 2011, which is a continuation-in-part (CIP) of U.S. patent application Ser. No. 13/176,020, filed Jul. 5, 2011, which claims priority to U.S. Provisional Patent Application No. 61/488,744 filed on May 22, 2011, which are all herein incorporated by reference.

FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to a supplier/buyer commerce network. More particularly, the described embodiments relate to a methods, apparatuses and systems for a managing an experience of a member organization of a collaborative commerce community of the supplier/buyer commerce network.

BACKGROUND

Commerce networks provide a means for electronically connecting buyers and suppliers. Buyers can enhance their supplier network by being electronically connected to many different suppliers. As a result, a buyer may be able to obtain better selection and pricing, and the suppliers may be able to realize additional sales.
Suppliers are able to provide information that describes the supplier online. Additionally, suppliers can port their offline (brick-and-mortar) reputations, references, and provide potential new customers with the ability to interact with those references.
Commerce networks, however, are limited in their ability to provide notices of potentially beneficial connections between users of either the buyers and/or suppliers. Such connections can be based, for example, on collaborative interactions, and/or based on general commerce information of the buyers and/or suppliers.
There is a need for systems, methods and apparatuses for a commerce network that managing a user's experience and providing introductions between users of the commerce network.

SUMMARY

An embodiment includes a computer-method of managing a member organization experience of a collaborative commerce community through a network. The method includes managing, by one or more servers, buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst the buyer organizations and the seller organizations associated with the network, and wherein the member organization is at least one of the plurality of seller organizations or the plurality buyer organizations. The method further includes providing unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations, determining an intra-organization link between users of the member organization based on the collaborative interactions of the member organization and a subset of the plurality of buyer organizations or a subset of the plurality of seller organizations, and electronically notifying at least one user of the member organization of the determined intra-organization link.
An alternate embodiment includes determining intra-organization links between users of the member organization based on the buyer company profiles and/or the seller company profiles.
Another embodiment includes a commerce community system for managing a member organization experience of a commerce community through a network. The system includes a commerce server (one or more servers) electronically connected to servers of a plurality of seller organizations and servers of a plurality of buyer organizations through the network, wherein the member organization is at least one of the plurality of seller organization or the plurality of buyer organizations. For this embodiment, the commerce server is operative to manage buyer company profiles of the plurality of buyer organizations and seller company profiles of the plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst all buyer organizations and seller organizations associated with the network. Further, the commerce server is operative to provide unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations, determine an intra-organization link between users of the member organization based on the collaborative interactions of the member organization and at least a subset of the plurality of buyer organizations or at least a subset of the plurality of seller organizations, and notify the users of the member organization of the determination of the intra-organization link.
Another embodiment includes a program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a computer-method of managing a member organization experience of a collaborative commerce community through a network. The computer-method includes managing, by one or more servers, buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst the buyer organizations and the seller organizations associated with the network, wherein the member organization is at least one of the plurality of seller organizations or the plurality buyer organizations. The method further includes providing unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations, determining an intra-organization link between users of the member organization based on the collaborative interactions of the member organization and a subset of the plurality of buyer organizations or a subset of the plurality of seller organizations, and electronically notifying at least one user of the member organization of the determined intra-organization link.
Other aspects and advantages of the described embodiments will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system that facilitates management of a member organization experience of a collaborative commerce community through a network, according to an embodiment.

FIG. 2 shows a system that facilitates management of a member organization experience of a collaborative commerce community through a network, according to a more detailed embodiment.

FIG. 3 is a flow chart that includes steps of a managing a member organization experience of a collaborative commerce community through a network.

FIG. 4 is a screen-shot of a user interface (UI) of a company profile editor, according to an embodiment.

FIG. 5 is a screen-shot of a user interface (UI) buyer relationship tab, according to an embodiment.

FIG. 6 shows a schematic illustration of one embodiment of a computer system that can perform the methods of the described embodiment, and/or can function as, for example, a supplier/buyer commerce network that electronically manages a member organization experience of a collaborative commerce community through a network.

DETAILED DESCRIPTION

The embodiments described include methods, systems and apparatuses for managing a member organization experience of a collaborative commerce community through a network. The collaborative community provides electronic inter-connections having the capability to connect many sellers with many buyers, and many buyers to many sellers. Further, electronic inter-connections of the collaborative community have the capability to manage collaborative interactions between the many sellers and many buyers. For embodiments, the collaborative interactions are related to the business processes of buy, selling, and managing cash flow in business to business (B to B) commerce. The electronic management provided by the described embodiments simplifies the collaborative process for the sellers and the buyers. Further, based on entered or collected information of each of the many sellers and many buyers, alerts or notifications can be provided to the sellers and/or buyers, thereby providing additional benefits to the sellers and buyers. In addition to notifications, at least some embodiments include meta-information that is collected about the buyer and seller participants to better facilitate more connections and hence more interactions, thereby creating a virtuous circle of more community and collaboration in a network effect.
FIG. 1 shows a system that facilitates management of a member organization experience of a collaborative commerce community through a supplier/buyer commerce network 110, according to an embodiment. The member organization can be a seller (such as supplier 114), a buyer (such as buyers 112), or both a seller and a buyer. Each of the member organizations includes one or more users. For example, as shown, the supplier (seller) 114 includes a first user 115 and a second user 116. While only a single supplier (seller) 114 that include multiple users is shown in FIG. 1, it is to be understood that any number of sellers can be electronically connected to the supplier/buyer commerce network 110. While multiple buyers 112 are shown, it is to be understood that any number of buyers can be connected to the supplier/buyer commerce network 110 (the supplier/buyer network can alternatively be referred to as a business network), wherein each of the buyers can include any number of users. It is also to be understood that while some of the described embodiments may be directed to interactions between users of the seller (supplier) 114, similar types of interactions can be implemented between users of the buyers 112 as well.
Embodiments of the buyers 112 and the supplier 114 include one or more enterprise networks that include one or more enterprise servers. That is, while not shown in FIG. 1, the buyers 112 and the suppliers 114 may each include one or more enterprise networks (which include one or more enterprise servers). The enterprise servers of the buyers 112 and the supplier 114 are network connected (through, example, the internet) to the supplier/buyer commerce network 110.
Embodiments of the supplier/buyer commerce network 110 include one or more servers (such as, S/B commerce network server 111) that support the described embodiments for management of a member organization experience of the collaborative commerce community. Embodiments of each of the servers include processors.
Exemplary processing engines that are a part of the supplier/buyer commerce network 110, and may be operable on the S/B commerce network server 111, include an intra-organization link engine 160 and an inter-organization link engine 170. The intra-organization link engine 160 identifies characteristics of users (such as, users 115, 116) of the seller (or in other embodiments, the buyer) that suggest that one or more of the users could benefit by receiving an alert of the existence of one or more other users of the seller. For example, two different users of the seller may be utilizing the supplier/buyer commerce network 110, wherein the two different users are a part of different organizations of the seller, but are physically close to each other. Due to the physical proximity of the two different users, each of the two different users may be benefited by being made aware of the existence of the other.
It is important for users (colleagues) of an organization to know if and when other colleagues (for example, other users of a buyer or seller) are part of a particular community. This knowledge can be used to lower barriers to collaboration and hence better business performance (through lower costs of getting people (users) to connect and communicate).
An embodiment includes a Recommended Account sub-feature as a part of an account hierarchy feature of the supplier/buyer commerce network 110. For example, for intra-company user, the Recommended Account sub-feature can use business information entered by a user to identify an existing account of a company of the user on the supplier/buyer commerce network 110. For an embodiment, seller profiles are matched base on, for example, an email domain, a tax ID, a DUNS, or a VAT ID. For an embodiment, the matching is on a company level and not user level, but it will bring user together once the accounts are linked.
The inter-organization links engine 170 identifies characteristics of the buyers and sellers that suggest that one or more of the buyers or sellers could benefit by receiving an alert of the existence of one or more of the other buyers or sellers. For example, a seller could benefit from an alert that indicates a buyer who probably would like to purchase what the seller is selling, and a buyer could benefit from an alert that indicates a seller who sells what the buyer is seeking to buy.
As will be described, embodiments of the intra-organization link engine 160 and the inter-organization links engine 170 utilize profile information of the suppliers and/or buyers, and/or collaboration information of the suppliers and/or buyers.
For at least some embodiments, a company profile 118 includes at least four quadrants that include at least a first quadrant (A) that includes self-reported information, a second quadrant (B) that includes community information, a third quadrant (C) that includes third party information, and a fourth quadrant (D) that includes aggregated activity information. It is to be understood that this is an exemplary list, and that other information of the suppliers and/or buyers can be used to supplement the company profiles.
For at least some embodiments, the collaboration information is based on collaborative interactions between the suppliers and the buyers. For at least some embodiments, the collaborative interactions between the plurality of sellers and the plurality of buyers includes selling, bid, quoting, contract management, product or service fulfill, invoicing, and/or collections is to be understood that this is an exemplary list, and that other collaborative interactions can be utilized as well.
Embodiments of the supplier/buyer commerce network 110 provide a useful, friendly interface for the member (suppliers and/or buyers) organizations. The many supplier to many buyer interface provided by the supplier/buyer commerce network 110 provides for better, more efficient interaction and exchange between the suppliers 114 and the buyers 112.
FIG. 2 shows a system that facilitates management of a member organization experience of a collaborative commerce community through a network, according to a more detailed embodiment. For this embodiment, the supplier/buyer commerce network 110 obtains or gleans information outside of the supplier/buyer commerce network 110 to be used, for example, to supplement the company profiles
For at least some embodiments, the buyers 112 are associated with the supplier/buyer commerce network 110 in some capacity. However, suppliers are not so limited. That is, the suppliers 112, 124 can be either associated (enabled) or not associated (not enabled) with the supplier/buyer commerce network 110. For example, as shown in FIG. 2, a first type of supplier 114 is associated with the supplier/buyer commerce network 110, while a second type of supplier 124 is not directly associated with the supplier/buyer commerce network 110, but is reached through cloud networks 120 (through, for example, the internet). After reached, the second type of supplier 124 can become associated with the supplier/buyer commerce network 110 (for example, via a directory service that manages the unique IDs for all connected Networks).
An embodiment further includes mining data of suppliers includes finding suppliers from other databases and/or reaching out, for example, through the internet to company (potential supplier) websites. That is, suppliers can be recruited that are a potential match with the buyer. The recruitment can be through the searching of databases (inside and outside of the supplier/buyer commerce network 110) and/or searching other company
Once the buyer has been matched to a set of suppliers (alternatively or additionally suppliers matched to buyers), embodiments includes electronic communication alerting the suppliers of a current interest by the buyer to acquire good and/or service that the suppliers 114, 124 provide. The electronic communication can be made, for example, by emailing the anonymously harvested information to the selected set of suppliers. Additionally, or alternatively, the electronic communication can be made to the suppliers by, faxing, phoning, tweeting, a small message system (sms), an RDF site summary (RSS) feeds, an application programming interface (API) based integration, and/or third party integrations. For at least some embodiments, the matching includes, for example, matching a buyer's interest to acquire good and/or services with suppliers offering potential, or matching vendor master data from the buyer with cloud supplier accounts.
Embodiments include the company profile 118 being adaptively updated (by, for example, the commerce network server 111) as the company associated with the company profile 118 interacts with buyers 112, 122 and/or suppliers 114, 124. The company profile 118 can advantageously be used to generate a score for the company and/or match the company with other companies associated with the supplier/buyer commerce network 110. The company profile 118 is generally stored within a database associated with the supplier/buyer commerce network 110.
While the embodiments described are directed to a single company profile 118, it is to be understood that at least some of the described embodiments include multiple company profiles. For embodiments, each company profile corresponds with a different company associated with the supplier/buyer commerce network 110. The different company profiles provide a means for contrasting (for example, scoring) the different companies. Additionally, the different company profiles can be used to proactively match companies (suppliers 114 and buyers 112) associated with the supplier/buyer commerce network 110 (as described above).
As shown, and previously described, an embodiment of the company profile 118 includes four quadrants, wherein a first quadrant (A) includes self-reported information, a second quadrant (B) includes community information, a third quadrant (C) includes third party information, and fourth quadrant (D) includes aggregated activity information. It is to be understood that for some embodiments the company profile can include a subset of these quadrants, and for other embodiments, the company profile can include information in addition to the information of these four quadrants. The company profile 118 is a collection of information pertaining to the corresponding company that is associated with the network. The company profile allows other companies (suppliers 114 and/or buyers 112) to evaluate the company associated with the company profile 118. Clearly, the company profile can include fewer or more than the four quadrants.
The self-reported information (quadrant A) can be from (suppliers 114 and/or buyers 112) includes company provided information that can be received by the supplier/buyer commerce network and incorporated into the company profile. The self-reported information can be received in different ways. For example, a company may effectively “walk up” and join the supplier/buyer commerce network, or the company information can be loaded by the supplier/buyer commerce network 110 or from another database or application. For an embodiment, the public information becomes a part of the profile.
For embodiments, pieces of the self-reported information are used to drive additional processes in the supplier/buyer commerce network. That is, for example the self-reported information can include a DUNS number field. Once the supplier/buyer commerce network has the DUNS number, the supplier/buyer commerce network can provide financial risk score information on the supplier. The DUNS number can be used to drive communication with, for example, a third party. Additionally, as will be described, a matching process engine can analyze commodities (goods & services) a supplier has selected as providing, and the sales territories of the supplier, in order to match that supplier's profile against the business opportunities.
The community information (quadrant B) includes information that pertains to the company that is provided by suppliers 114 and buyers 112 associated with the network. The community information includes, for example, ratings. The ratings allow, for example, a buyer to rate any supplier that has responded to a business opportunity on the supplier/buyer commerce network 110.
Another aspect of the community information includes references. For at least some embodiments, a reference is a quote/citation from a buyer/customer which represents or verifies the quality performance of the good or service being supplied by the supplier/seller. For at least some embodiments, references include contact information for the buyer/customer such that other buyers who are interested in the supplier for whom the reference was given. The contact information is offered for other buyers to reach out to the buyer giving a reference for additional communications/elaboration about the seller/suppliers performance. To further facilitate community and parallel real world interactions, embodiments of the supplier/buyer commerce network allows other buyers to request contact with the author of any given reference. For embodiments, the subject of the reference (the supplier) is the gatekeeper in such an interaction and may decline or accept the third party's request to speak with a reference. For embodiments, the reference itself contains a few pieces of information, for example, a text narrative, industry of the buyer, and/or length of the business relationship.
The third party information (quadrant C) includes information that pertains to the company that is provided by a third party 170 who is typically not associated directly with the network. The third party information includes, for example, a business and credit rating provided by, for example, an established rating agency (such as, Dun &. Bradstreet® (D&B)). The third party information can include financial risk information about suppliers. This can be linked or associated with the suppliers using self-reported DUNS number information. The DUNS information can be validated with D&B using an API call. The validated information can be displayed back to the supplier for their approval. Once approved, the supplier/buyer commerce network basically has the supplier linked to a risk profile on D&B.
The aggregated activity information includes, for example, transactional activity of the company. For example, the aggregated activity information can include information about suppliers and their performance on the supplier/buyer commerce network 110.
A useful piece of aggregated activity information included within the company profile is the number of transacting relationships that the company has with buyers/ suppliers 112, 114 on the supplier/buyer commerce network 110, and/or transacting relationships the company has with buyers/ suppliers 122, 124 of other commerce networks, such as cloud networks 120. This information provides a valuable picture of how many other companies the company is actively doing business with via the supplier/buyer commerce network 110, and the cloud networks 120. It is to be understood that doing business with other companies includes activities can include interactions that do not include money, good or services changing hands. If the supplier/buyer commerce network 110 is interfaced with cloud networks 120, the company profile can be made to be common (the same) between commerce network platforms. Therefore, real-time information can be utilized across the commerce and cloud network platforms 110, 120.
Examples of aggregated activity information include, but are not limited to, event invitations, invitations by revenue, transaction awards (for example, winning supplier bids), revenue ranges, and/or top bids by industry.
The interface between the supplier/buyer commerce network 110 and cloud networks 120 allows the supplier/buyer commerce network 110 to glean additional information that can be useful for enhancing the value of the company profile 118. For example, cloud network 120 can include sourcing and/or contract information and data. These embodiments determine commonality of suppliers/buyers across multiple private cloud networks. The different companies (buyer/sellers) are assigned unique identifiers by, for example, a unique ID engine 130, which allows the generation of a single view of the companies' behavior across multiple interactions (across the supplier/buyer commerce network 110 and the cloud networks 120. That is, for embodiments, one or more databases are associated with networks 110, 120 that maintain transactional activity of the company with other companies, and this transaction information for the company is identified by the unique identifier of the company.
FIG. 3 is a flow chart that includes steps of a managing a member organization experience of a collaborative commerce community through a network. A first step 310 includes managing buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, the buyer organizations and the seller organizations associated with the network, wherein the member organization is at least one of the plurality of seller organizations or the plurality buyer organizations. For an embodiment, a key element is allowing the member organization to self-manage its company profile. For an embodiment, parts of the profiles are maintained as private, and are not shared or shared only with selected, for example, active trading relationships. A second step 320 includes providing unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations. A third step 330 includes determining an intra-organization link between users of the member organization based on the collaborative interactions of the member organization and a subset of the plurality of buyer organizations or a subset of the plurality of seller organizations. A fourth step 340 includes electronically notifying at least one user of the member organization of the determined intra-organization link.
An embodiment includes determining an inter-organization link between the member organization and at least one of the plurality of buyer organizations or at least one of the plurality of seller organizations based on the collaborative interactions between the plurality of buyer organizations and the plurality of seller organizations. After establishing or determining the inter-organization link, an embodiment includes notifying the member organization of the inter-organization link between the member organization and the at least one of the plurality of buyer organizations or at least one of the plurality of seller organizations.
For at least some embodiments, managing a member organization experience includes providing at least one user of each member organization with a single login, and access to collaboration with the plurality of buyer organization and the plurality of seller organizations based on the single login. This single login and access is extremely valuable because of the seamless user experience it offers. That is, a single-login, single-click is all that is required to navigate a wealth of information about collaborative activity of the user and its organization. This eliminates inefficiencies associated with managing and maintaining multiple URLs and login accounts for each individual buyer and/or seller relationship.
The advent of cloud/network technology has obsoleted the process of 1 to 1 interactions that exist by a buyer and seller. The 1 to 1 interactions have a hidden cost because the real world works in many to many interactions and thus seller participants are burdened with maintaining individual logins, passwords, and url/website locations for each buyer they do business with. The described embodiments provide a cloud network technology that better matches how the real business world works. A seller participant can go to one location to manage the collaborative commerce interactions with all buyers they do business with just a single login password and URL.
As previously described, the profiles, such as the buyer company profiles of each buyer organizations include at least self-reported information of the buyer organization. For a specific embodiment, the self-reported information includes registration information, wherein the self-reported information of the buyer organization is utilized by the collaborative interaction between the buyer organization and the plurality of seller organizations. Additionally, as described, at least some embodiments, of the buyer company profile of each buyer organization further can include community information, third party information, and aggregated activity information. For at least some embodiments, the buyer company profile of each buyer organization is adaptively updated. The described embodiments also offers a location for company self-reported information to be automatically validated precluding the need/cost of human validation or the risk of using information that may not be accurate.
As previously described, each seller company profile includes self-reported information, community information, third party information, and aggregated activity information. For at least some embodiments, the supplier company profile of each supplier organization is adaptively updated.
For at least some embodiments, the collaborative interactions between the plurality of sellers and the plurality of buyers includes one or more of selling, bid, quoting, contract management, product or service fulfill, invoicing, and collections. The benefits provided by the many suppliers to many buyer interconnection provided by the collaborative commerce community network includes efficiency of the collaborative processes, and ease of scaling buyers and suppliers. Once in place, the cost of adding new or additional buyers and suppliers is minimal—both in cost and effort. The cost of adding new buyers and suppliers approaches zero as the number of buyers and sellers increases. Trading partner activity counts are typically higher because a single account is used across different trading partners, which additionally provides marketing advantages. Furthermore, details of the profiles of the member can be maintained with higher accuracy.
As suggested, a value of the collaborative commerce community network is identifiable in its ability to easily add buyers and suppliers and the information that collaborative commerce creates and for the benefit of the community beyond the specific buyer or seller interaction. The value of the many-to-many nctworks as have been described, is supported by Metcalfe's law, Sarnoff's law and Zuckerberg's law. Metcalfe's law states that the value of a telecommunications network is proportional to the square of the number of connected users of the system (n²). Sarnoff's law states that the value of a broadcast network is directly proportional to the number of viewers. For example, a network with 100 members is 10 times as valuable as a network with 10 members. Zuckerberg's Law states that a network members' willingness to share their information doubles every year.
For at least some embodiments the determining the intra-organization link between users of the member organization includes correlating attributes of each of the users of the member organization with attributes of other users of the member organization. For at least some embodiments, the attributes includes at least one of email domain, tax id, vat id, company name, geography, member organization groups, identified common interests, similarities in member profile information, usage of similar key words, mobile location, or business processes, wherein the business processes include at least one of buying and selling. For at least some embodiments, the attributes of each of the user of the member organization are included within a company profile and/or a user profile of the member organization. A user profile is profile information that is specific to the user member of an organization that may be inherited from the organization or different that the organization.
At least some embodiments include identifying potential links to buyer organizations or seller organizations based on the determined intra-organization link between users of the member organization. That is, the previously described intra-organization links can be utilized to identify potential inter-organization links. For example, potential links to buyer organizations can be based on determined intra-organization link between the seller organization or a members of the seller organization.
At least some embodiments include notifying one or more of the users of the member organization of the identified potential links to the buyer organizations or the seller organizations. At least some embodiments include notifying the buyer organizations or seller organizations of the identified potential links to one or more of the users of the member organization.
While the identification of infra-organization and inter-organization links have been described as utilizing collaborative interactions, the intra-organization and inter-organization links can additionally, or alternatively be identified utilizing the company profile of the member organization and the buyer company profiles of the plurality of buyer organizations, or the seller company profiles of the plurality of seller organizations.
For at least some embodiments, determining the inter-organization link between the member organization and the at least one of the plurality of buyer organizations or the plurality of seller organizations is based at least in part on a company profile of the member organization and the buyer company profiles of the plurality of buyer organizations, or the seller company profiles of the plurality of seller organizations.
For at least some embodiments, determining the inter-organization link between the member organization and the at least one of the plurality of buyer organizations or plurality of buyer organizations is based at least in part on correlating attributes of the member company profile of the member organization with attributes of the buyer company profiles of the plurality of buyer organizations and the seller company profiles of the plurality of seller organizations. Examples of attributes of the company profiles that can be matched include, for example, common commodities, common interests, common languages, common regions, common addresses, common titles, common connections, common history, or common searches.
An embodiment includes electronically notifying the member organization of the inter-organization links. That is, once the inter-organization links have been identified, the member organizations of the links are electronically notified.
For an embodiment, managing a member organization experience includes providing at least one user of each member organization with a single user interface (UI), wherein the UI provides the at least one user with a single interface access to collaborative interactions, the buyer company profiles, the seller company profiles, sharing information about workflows, and documents associated with the collaborative interactions.
The single user interface is very valuable because if the interface is intuitive enough, then no training is required. That is, for embodiments, it is intuitive enough such that untrained new users can walk up the first time and figure out how to use it. Additionally, there is no switching of the user interface between customers/buyers for whom suppliers are doing or soliciting business. At least some embodiments include a single interface across business to business commerce processes (for example, Leads, Sourcing Proposals, Contracts, Purchasing, Orders & Invoices). Therefore, there is a higher level of consistency, which again, makes the system easy to use. Embodiments of the single interface are state of the art, and consistent with technology common in web based consumer applications. The single interface includes self-guided configurations. The single interface is easily user-configurable and user-personalized, thereby providing maximum efficiency and intuitive use, less maintenance, and not requiring support or consulting.
An embodiment includes providing at least one user of a seller (supplier) of the member organization with a web browser, allowing the at least one user to navigate to specific buyer interactions and collaborative interactions. For an embodiment, the web browser includes mobile interface. For various embodiments, the specific buyer interactions can include, for example, responding to a discovery posting, creating an order confirmation, creating an invoice, providing a bid for collaboration requests, uploading a time and expense sheet, accepting an early payment, entering an invoice against contract, publishing and an RFQ, an RFP, or an auction, creating a contract, or requesting a survey response.
For at least some embodiments, the UI allows the at least one user to manage a company profile of the member organization of the at least one user, set usage preferences, administer preferences and permissions, navigate business processes.
For at least some embodiments, the unified experience for both buyer and sellers/suppliers also offers an open interface for 3^rdparty providers to integrate and augment the business processes and company profiles.
For at least some embodiments, navigating business processes includes providing tabs, wherein each UI segment (for example, aTab, section, dashboard screen) provides a window into collaborative interactions per buyer organization, seller organization, and each business process specific to that buyer/seller organization.
FIG. 4 is a screen-shot of a user interface of a company profile editor, according to an embodiment. As shown, the company profile editor provides an easy means for a member organization to update their profile. The platform exists on networking technology, and therefore, can take advantage of other networks very efficiently to make profile management easier/less costly. For example, by integrating the network of the platform with existing social networking websites for people in professional occupations to access company information versus having to type it in a screen, or, for example, integrating the network of the platform with D&B.
FIG. 5 is a screen-shot of a user interface of a buyer relationship tab, according to an embodiment. As shown, the buyer relationship tab provides an easy means for a buyer to access their relationships. Unlike any other existing technology, the described embodiments provide a place on the internet for a seller to go and see both all of their buyer relationships but also act on them/collaborate in the same interfact. That is, for example, a dashboard character on the screen can provide all the information in one place.
FIG. 6 shows a schematic illustration of one embodiment of a computer system that can perform the methods of the described embodiment, and/or can function as, for example, a supplier/buyer commerce network that electronically manages a member organization experience of a collaborative commerce community through a network. It should be noted that FIG. 6 is meant only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. FIG. 6, therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner.
The computer system 600 is shown comprising hardware elements that can be electrically coupled via a bus 605 (or may otherwise be in communication, as appropriate). The hardware elements can include one or more processors 610, communication subsystems 630, one or more input devices 615, which can include without limitation a mouse, a keyboard and/or the like; and one or more output devices 620, which can include without limitation a display device, a printer and/or the like. The computer system 600 may further include (and/or be in communication with) one or more storage devices 625. The computer system 600 also can comprise software elements, shown as being located within the working memory 635, including an operating system 640 and/or other code, such as one or more application programs 645, which may comprise computer programs of the described embodiments, and/or may be designed to implement methods of the described embodiments and/or configure systems of the embodiments as described herein.
Another embodiment includes a program storage device readable by a machine (of the supplier/buyer commerce network), tangibly embodying a program of instructions executable by the machine to perform a managing a member organization experience of a collaborative commerce community through a network, when executed, comprises the steps of managing buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst buyer organizations and seller organizations associated with the network, providing unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations, determining an intra-organization link between members of the member organization based on the collaborative interactions of the member organization and at least a subset of the plurality of buyer organizations or a subset the plurality of seller organizations, and electronically notifying at least one user of the member organization of the determined intra-organization link. Additionally, an embodiment further includes determining an inter-organization link between the member organization and at least one of the plurality of buyer organizations or one of the plurality of seller organizations based on the collaborative interactions between the plurality of buyer organizations and the plurality of buyer organizations, and notifying the member organization of the inter-organization link between the member organization and the at least one of the plurality of buyer organizations or the one of the plurality of buyer organizations.
Although specific embodiments have been described and illustrated, the embodiments are not to be limited to the specific forms or arrangements of parts so described and illustrated. What is claimed:

Claims

1. A computer-method of managing a member organization experience of a collaborative commerce community through a network, comprising:

managing, by one or more servers, buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst the buyer organizations and the seller organizations associated with the network, wherein the member organization is at least one of the plurality of seller organizations or the plurality buyer organizations;

providing unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations;

determining an intra-organization link between users of the member organization based on the collaborative interactions of the member organization and a subset of the plurality of buyer organizations or a subset of the plurality of seller organizations; and

electronically notifying at least one user of the member organization of the determined intra-organization link.

2. The computer-method of claim 1, further comprising:

determining an inter-organization link between the member organization and at least one of the plurality of buyer organizations or at least one of the plurality of seller organizations based on the collaborative interactions between the plurality of buyer organizations and the plurality of seller organizations;

notifying the member organization of the inter-organization link between the member organization and the at least one of the plurality of buyer organizations or at least one of the plurality of seller organizations.

3. The computer-method of claim 1, wherein managing a member organization experience includes providing at least one user of each member organization with a single login, and access to collaboration with the plurality of buyer organization and the plurality of seller organizations based on the single login.

4. The computer-method of claim 1, wherein each of the buyer company profiles of each buyer organizations comprises at least self-reported information of the buyer organization.

5. The computer-method of claim 4, wherein the self-reported information includes registration information, wherein the self-reported information of the buyer organization is utilized by the collaborative interaction between the buyer organization and the plurality of seller organizations.

6. The computer-method of claim 4, wherein the buyer company profile of each buyer organization further includes community information, third party information, and aggregated activity information.

7. The computer-method of claim 6, wherein the buyer company profile of each buyer organization is adaptively updated.

8. The computer-method of claim 1, wherein each seller company profile includes self-reported information, community information, third party information, and aggregated activity information.

9. The computer-method of claim 1, wherein the collaborative interactions between the plurality of sellers and the plurality of buyers includes at least one of selling, bid, quoting, contract management, product or service fulfill, invoicing, and collections.

10. The computer-method of claim 1, wherein the collaborative interactions between the plurality of sellers and the plurality of buyers includes all of selling, quoting, contract management, product or service fulfill, invoicing, and collections.

11. The computer-method of claim 1, wherein the determining the intra-organization link between users of the member organization comprises correlating attributes of each of the users of the member organization with attributes of other users of the member organization.

12. The computer-method of claim wherein the attributes includes at least one of geography, member organization groups, identified common interests, similarities in member profile information, usage of similar key words, mobile location, or business processes, wherein the business processes include at least one of buying and selling.

13. The computer-method of claim 11, wherein the attributes of each of the user of the member organization are included within a company and user profile of the member organization.

14. The computer-method of claim 11, further comprising identifying potential links to buyer organizations or seller organizations based on the determined intra-organization link between users of the member organization.

15. The computer-method of claim 14, further comprising notifying one or more of the users of the member organization of the identified potential links to the buyer organizations or the seller organizations.

16. The computer-method of claim 14, further comprising notifying the buyer organizations or seller organizations of the identified potential links to one or more of the users of the member organization.

17. The computer-method of claim 2, wherein determining the inter-organization link between the member organization and the at least one of the plurality of buyer organizations or the plurality of seller organizations is based at least in part on a company profile of the member organization and the buyer company profiles of the plurality of buyer organizations, or the seller company profiles of the plurality of seller organizations.

18. The computer-method of claim 17, wherein determining the inter-organization link between the member organization and the at least one of the plurality of buyer organizations or plurality of buyer organizations is based at least in part on correlating attributes of the member company profile of the member organization with attributes of the buyer company profiles of the plurality of buyer organizations and the seller company profiles of the plurality of seller organizations.

19. The computer-method of claim 18, further comprising electronically notifying the member organization of the inter-organization links.

20. The computer-method of claim 1, wherein managing a member organization experience includes providing at least one user of each member organization with a single user interface (UI), wherein the UI provides the at least one user with a single interface access to collaborative interactions, the buyer company profiles, the seller company profiles, sharing information about workflows, and documents associated with the collaborative interactions.

21. The computer-method of claim 20, further comprising providing at least one user of the member organization with a web browser and mobile interface, allowing the at least one user to navigate to specific buyer interactions and collaborative interactions.

22. The computer-method of claim 21, wherein the UI allows the at least one user to manage a company profile of the member organization of the at least one user, set usage preferences, administer preferences and permissions, navigate business processes.

23. The computer-method of claim 23, wherein navigating business processes includes providing tabs, wherein each UI segment provides a window into collaborative interactions with each buyer organization, each seller organization, and each business process specific to that buyer/seller organization.

24. A commerce community system for managing a member organization experience of a commerce community through a network, comprising:

a commerce server electronically connected to one or more servers of a plurality of seller organizations and to one or more servers of a plurality of buyer organizations through the network, wherein the member organization is at least one of the plurality of seller organization or the plurality of buyer organizations;

the commerce server operative to:

manage buyer company profiles of the plurality of buyer organizations and seller company profiles of the plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst all buyer organizations and seller organizations associated with the network;

provide unified management of collaborative interactions between the plurality of seller organizations and the plurality of buyer organizations;

determine an intra-organization link between users of the member organization based on the collaborative interactions of the member organization and at least a subset of the plurality of buyer organizations or at least a subset of the plurality of seller organizations;

notify the users of the member organization of the determination of the intra-organization link;

determine an inter-organization link between the member organization and at least one of the plurality of buyer organizations or the plurality of seller organizations based on the collaborative interactions between the plurality of buyer organizations and the plurality of buyer organizations; and

notify the member organization of the inter-organization link between the member organization and the at least one of the plurality of buyer organizations and the plurality of seller organizations.

25. The system of claim 24, wherein the determining the intra-organization link between users of the member organization comprises correlating attributes of each of the users of the member organization with attributes of other users of the member organization.

26. The system of claim 25, wherein the attributes includes at least one of geography, member organization groups, identified common interests, or business processes, wherein the business processes include at least one of buying and selling.

27. The system of claim 25, further comprising identifying potential links to buyer organizations or seller organizations based on the determined intra-organization link between users of the member organization.

28. The system of claim 24, wherein managing the member organization experience includes providing at least one user of each member organization with a single user interface (UI), wherein the UI provides the at least one user with a single interface access to collaborative interactions, the buyer company profiles, the seller company profiles, sharing information about workflows, and documents associated with the collaborative interactions.

29. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a computer-method of managing a member organization experience of a collaborative commerce community through a network, when executed, comprises:

managing buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst buyer organizations and seller organizations associated with the network;

determining an intra-organization link between members of the member organization based on the collaborative interactions of the member organization and at least a subset of the plurality of buyer organizations or a subset of the plurality of seller organizations;

electronically notifying at least one user of the member organization of the determined intra-organization link,

determining an inter-organization k between the member organization and at least one of the plurality of buyer organizations or at least one of the plurality of seller organizations based on the collaborative interactions between the plurality of buyer organizations and the plurality of seller organizations; and

30. A computer-method of managing a member organization experience of a collaborative commerce community through a network, comprising:

managing, by one or more servers, buyer company profiles of a plurality of buyer organizations and seller company profiles of a plurality of seller organizations, wherein the buyer company profiles and the seller company profiles are shared amongst buyer organizations and seller organizations associated with the network, wherein the member organization is at least one of the plurality of seller organizations or the plurality buyer organizations;

determining an intra-organization link between users of the member organization based on a profile of the member organization or the buyer company profiles of the plurality of buyer organizations, or the seller company profiles of the plurality of seller organizations; and

electronically notifying at least one user of the member organization of the determined intra-organization