WO2010021927A2 - System and method for integrated product design, manufacturing, and distribution - Google Patents

Abstract

A method and system for facilitating interactions between various parties involved in the design, development, and manufacturing of a product. A computer-based system is used to provide a single-site solution to the integration of the various parties and resources needed to carry low volume purchasers from obtaining assistance at the initial design stage all the way through to production level ordering for purposes of product manufacturing.

Description

SYSTEM AND METHOD FOR INTEGRATED PRODUCT DESIGN, MANUFACTURING, AND DISTRIBUTION

TECHNICAL FIELD

The present invention generally relates to systems and methods for facilitating interaction between purchasers and suppliers and, more particularly, to computer- implemented systems and methods for facilitating communication and transactions between purchasers and suppliers.

BACKGROUND OF THE INVENTION

For many areas of business, the Internet has changed the way individuals and companies gather information and in some cases, transact business. For example, many consumers purchase goods over the Internet through e-commerce sites rather than from brick and mortar stores. Some consumers and businesses also purchase goods and services over the Internet through brokerage sites for such things as ticket reservations and auctioned items. These sites provide consumers with the convenience of making a purchase quickly from any location.

In contrast, there are a large number of product developers who require specialized products, components, or services to meet specific needs. The product developers may not know where to obtain a specific specialized product or even whether that product exists. For high volume purchasers, it may not be difficult to find suppliers willing to provide specialized products, technical expertise, and resources necessary to meet the purchaser's needs. But for lower quantity purchasers, finding the right supplier with the necessary products, expertise, and services can be difficult.

Although various websites provide a wealth of information, the information needed for specialized products or components can be scattered and difficult to find for low volume purchasers. These purchasers may need to determine what types of specialized products already exist, who makes the products, what the attributes of the products are, how the product can work as a component in a larger product developed by the purchaser, who to test the product, how to distribute and manufacture the product, and the like. Moreover, the specialized purchaser can also want to obtain feedback from others who have used such specialized products or components and obtain the assistance of experts in that area or technology.

Likewise, it can be difficult for suppliers of specialized components, products, and services to find and support low volume purchasers. There can be dozens or even hundreds of potential low volume purchasers who have a need for a specialized product or service offered by the supplier. But finding and sorting through the specialized needs of so many purchasers can be difficult. Although various websites and Internet-based product and service resources exist, none provide a sufficiently usable integration of the complete range of product, service and resource offerings needed by smaller volume purchasers. One reason for this may be the technical difficulty of integrating various existing diverse systems such as knowledge bases, community forums, ordering and inventory control systems, as well as transactional processing systems.

Another reason relates to the nature of the marketplace sector considered herein; namely, that for lower volume purchasers, the currently-available computer- based collaborative systems do not provide the combination of technical functionalities needed to successfully address the needs of such purchasers and their suppliers. For example, transaction-centric business systems in use today typically provide the interconnectivity and features needed to carry out the ordering, inventorying, and delivery of goods while providing limited information resources, such as knowledge bases. They may not, however, provide the purchaser with complete guidance through the entire product design, development and manufacturing process. This is because larger volume purchasers already have such abilities in- house and thus only need limited supplier product information along with the transactional ability to obtain the product.

For example, in the coatings formulation industry, a paint formulator can use existing Internet resources to get information on additives and other modifications that it is considering for a particular formulation. This might be done, for example, where the formulator has a starting formulation that it wants to modify for a particular application. The additive information, although perhaps scattered if not also incomplete or difficult to find, can be obtained and used by the formulator in designing its modified product. Separately, it may be possible for the formulator to order samples, obtain testing of the modified formulation, and re-order production amounts to begin the manufacturing, all via the Internet; however, due to the above- noted technical difficulties as well as the noted market-driven problems associated with low volume purchasers, there is today an absence of any single-site solution that provides an integrated environment designed specifically to support low volume design, prototyping, testing, and production ordering.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred exemplary embodiments of the present invention will hereinafter be described in conjunction with the appended drawings, wherein like designations denote like elements, and wherein:

FIG. 1 is a block diagram of a system for integrating purchasers, suppliers, and third parties;

FIG. 2 is a schematic diagram of functions provided by various engines in the system;

FIG. 3 is a flowchart showing some steps of an embodiment of a method for facilitating interactions between purchasers and suppliers; and

FIG. 4 is a flowchart showing some of the steps of searching for products or services.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 shows an exemplary system 10 constructed in accordance with the invention as it might be used for facilitating interaction between purchasers and suppliers. Purchasers can include users of the system 10 searching for information, suppliers, and recommendations on products, components, and/or services. Purchasers can use the system 10 to assist them with designing their own product, purchasing components for their product, and obtaining services necessary for supporting their product including testing, manufacturing, marketing, and the like. Suppliers can also access system 10 as users who offer goods and services. To facilitate the needs of the purchasers and suppliers, the system 10 includes a server 12, and one or more clients 14 communicating with the server over the Internet 16. In one embodiment, clients 14 can be any type of computing device that supports a web browser and is able to communicate with servers via the Internet 16. For example, the clients 14 can be a personal computer, a handheld device such as a web-enabled personal data assistant, and the like.

The server 12 can include an integration engine, a central processing unit 20, memory 22, a web server 24, and one or more optional databases 26. The integration engine provides functionality for receiving and displaying products and services, conducting search requests, facilitating communication between two or more purchasers, suppliers, and third parties, and facilitating transactions between them. The CPU 20 can be a conventional microprocessor. The memory 22 can include random access memory (RAM) and/or read-only memory (ROM).

The server 12 can also include a web server 24, one or more optional databases 26, and the integration engine. The web server 24 enables clients 14 to connect to the integration engine over the Internet. Web server 24 can enable multiple clients 14 to connect to the integration engine at the same time and can allow the clients to be located in any location relative to the server 12. The databases 26 can store and retrieve data for the integration engine. The databases 26 can be incorporated into the computing hardware and software. Alternatively, the databases 26 can be distributed from the computing hardware and linked to the server via a local area network.

The integration engine 18 includes logic for providing an interactive environment for users and provides a user interface for client interaction. In one embodiment, the integration engine 18 provides a website that the clients interact with through a web browser. The website enables purchasers, distributors, experts, and others to communicate both publicly and privately, conduct transactions, and share resources and information with one another. The website provides the purchasers with a single resource for locating specialized products and services, customer opinions, advice, expertise, and to then obtain product samples, testing services, and ultimately ordering of production quantities. The website provides a single resource for suppliers to locate new customers, receive market data, market their products and service, and sell their products and services. To implement this functionality, the integration engine 18 (which is shown in greater detail in Fig. 2), includes a research engine 30 to assist purchasers with obtaining information, an account engine 32 for managing user accounts, a communication engine 34 for facilitating interaction between system 10 users, and a transaction engine 36 for handling transactions conducted between purchasers and suppliers.

The research engine 30 allows users to search and review news and articles relevant to a particular market or markets and search for products and services. The research engine 30 can include news, a knowledgebase, a search engine, and links to third party resources. The research engine 30 can provide news from recognized third parties. The news can be provided within the interactive environment and can be supplied by RSS feeds from third parties. The news sources can be selected based on their content, their market or technology focus, or for other similar reasons. The knowledgebase can include articles written and submitted by system 10 users. The articles can be organized according to topics and can be searchable via the search engine.

The search engine performs keyword searching for text and tags and returns results containing the keywords and/or tags requested in the search and can be used to locate relevant news, knowledgebase entries, suppliers, products and services. Search engines are known in the art and as such, the search engine can comprise common search engine technology.

Likewise, the research engine 30 can supply links to other useful third party sources of interest to the users. These resources can include links to other content sites, related manufacturers, service providers, industry consultants, publishers, academic resources, and the like. These links provide users with a single location where they can go to find other resources that can be of use to them.

The account engine 32 provides login and password authentication as well as management for user accounts. The users can register for an account through the account engine 32 to obtain access to various system 10 features. The account engine 32 can restrict some or all functionality to registered users. The account engine 32 can also maintain account information such as contact information, financial information, account security and privacy settings, and the like. The account engine 32 can also manage account preferences for an account space, a private portion of the environment dedicated to each registered users. The account engine 32 enables the account user to select and arrange content displayed in the account space. The content can include selected news topics and sources, communications sent and received through the account, projects managed by the account, order placed through the account, and the like.

The account engine 32 also provides the capability for suppliers of goods and services to promote and offer their goods and services via the system 10. The account engine 32 allows users to enter a description of the goods and services for viewing and ordering through the system 10. Users can enter information about their products such as a written description of the product, the product's contents or ingredients, pricing, availability, a list of product attributes or qualities, and the like. Suppliers can also provide information related to services such as laboratory testing, manufacturing services, marketing services, research and development services, and the like. The supplier can provide a list of tags and associate the tags with the goods or services they are posting. The tags enable users to quickly search for available products and services and sort them. Once posted, the account engine 32 allows the supplier to manage the product or service through the account space. Users can go back and edit items such as the product's description, pricing, availability, and so forth at any time.

The communication engine 34 enables users to communicate with one another to collaborate on ideas, share resources, transact business, provide expertise, feedback, market information, live help, and the like. The communication engine 34 can provide private communication and public communication. The communication engine 34 can also provide live help.

Private communication involves communication between two or more users that is not visible by other users in the environment. Private messages can be sent in a variety of ways. For example, a link can be provided anywhere account user information is listed such as on goods or services provided by a user, testimonials from a user, message board postings from a user, knowledgebase entries, and even account user listings. The link can simply be an e-mail link containing the e-mail address of the account user. In another embodiment, the link can open a pop-up window which enables the account user to type a message into a text box and send the message to a private message box of the recipient. In another embodiment an icon next to an account user listing can inform the users whether the account user is currently logged into the system 10. If the account user is currently logged into the system 10, clicking on the icon can launch a live chat window or private chat window between the account users. The private chat window can allow the account users to type messages and send and receive them in real time enabling the two users to communicate with one another in real time.

In another embodiment, users can send private messages through a message board or blog provided by the communication engine 34. Users can enter messages in private sections of the message board or blog and configure which users can view the messages.

In contrast to private communications, public communications are generally visible by all users. In one embodiment, public communications are visible only by registered users. Users can send public communications through message boards, blogs, customer testimonials, and the like. By default, messages posted on blogs and message boards are visible by the public. The customer testimonials can be posted and linked to products and services posted by other account users through the communication engine 34. The communication engine 34 allows account users viewing a given good or service to select and enter a customer testimonial regarding that good or service. The testimonial allows account users to share their experience both good and bad with the good or service in question with other account users. The customer testimonial can also include a rating of the product or service by the testimonial provider. The rating can enable other account users to quickly gauge the overall satisfaction of purchasers of that good or service. The communication engine 34 links the customer testimonial with the good or service posting so that any user who views the good or service can quickly review the testimonials provided for that good or service.

The communication engine 34 can support live help to enable account users to communicate in real time with a help desk. Live help can take any number of forms. In one embodiment an account number can activate live help by clicking on a link for live help which opens an interactive chat window. The user can enter messages into the chat window which are received in real time by the help desk. The help desk can respond by typing messages back to the user, which then appear in the live help window. In such a manner, the account user and the help desk can communicate in real time with one another through the chat window. In another embodiment, live help can consist of the user selecting a live help link and entering a telephone number into a pop-up window. The live help can then call the user at the number entered into the pop-up window.

The transaction engine 36 enables users to place orders, request samples, fulfill payment requests, and automate these processes. Once users locate a product or service of interest, they can select to place an order. The transaction engine 36 handles processing the order for the product or service supplier. The transaction engine 36 gathers the buyer account information from the account engine 32. This information can include items such as company name, address, payment information, and the like. The transaction engine 36 can also submit a purchase request to the supplier. The transaction engine 36 can handle details of the potential purchase including items such as quantity, shipping, timing and the particular products or services requested by the purchaser. The transaction engine 36 can complete payments for the transactions by obtaining and processing credit card information, banking information such as electronic checking account routing information, providing invoicing, and the like. The transaction engine 36 can receive the information from the account engine 32, or through interaction with the user.

The transaction engine 36 can conduct credit checks on users. Credit checks can be conducted when a user first registers, when the user conducts their first transaction, or when the user conducts a transaction with another user with which they have not transacted with before. In one embodiment, a user must obtain a satisfactory credit report prior to being registered. In cases where a supplier wishes to conduct a credit check on a potential purchaser, the transaction engine 36 can notify the purchaser of any information requested by the supplier that is not contained within the user's account information. The purchaser can then provide the transaction engine 36 with the necessary information required to run the credit check. In one embodiment, the transaction engine 36 conducts credit checks for purchasers who have not transacted with a given supplier prior to a current transaction request. The credit check history can be provided for purchasers who have previously conducted credit checks through the transaction engine 36.

The transaction engine 36 can further process transactions between a purchaser and a supplier by automating orders and distribution between multiple entities. For example, a purchaser can purchase a material such as a resin for paint from a supplier and the transaction engine 36 can process the transaction between the purchaser and supplier. The transaction engine 36 can automate a transaction between the resin supplier and its raw material supplier by informing the raw material supplier of the new resin order. The transaction engine 36 can provide information to the raw materials supplier such as quantity and timing of any raw materials necessary for the resin supplier to provide the resin to the purchaser. The raw material supplier can then process the request for the necessary raw materials and schedule shipment of those materials to the resin supplier. This can further simplify and automate transactions between multiple entities using the integration system 10.

The transaction engine 36 can also enable purchasers to request a sample from a supplier. Purchasers can click on an order sample request listed on products provided on the integration system 10. Once the order sample is requested, the transaction engine 36 automatically notifies the suppliers of the order request and provides information necessary for the supplier to fulfill the sample request. The transaction engine 36 provides information such as the purchaser contact information in order to facilitate communication between the purchaser and supplier and allows the supplier to provide both support and assistance to the purchaser. Moreover, communication between the purchaser and supplier can provide the supplier with useful marketing information. Through communication following a sample request, the supplier can be able to gain knowledge about specific needs required by the purchaser or the purchasers market in general.

By integrating the different services engines shown in Fig. 2 within the integration engine 18, there is provided an Internet-accessible, computer-based community and marketplace that brings together previously disjointed resources in a manner that allows low volume customers to obtain the market and technical assistance that they typically need to successful design, develop, test, produce, and market a product. Different communities related to different industries can exist and be maintained simultaneously so that, for example, a paint and coating community can exist at the same time as a plastics recycling community and the system can be designed so that both are maintained entirely separately. Alternatively, various different communities could all exist within the same workspace and be visible to each other which, although adding perhaps some complexity for the user, would allow cross-over of ideas between the different communities.

Turning now to FIG. 3, there is shown an embodiment 100 of a method for sharing information and facilitating transactions between purchasers and suppliers. According to this particular embodiment, method 100 beings by logging in or registering on the site, step 110. A user can log in by providing a username and password for their account. Users can also register to create an account on the system 10 by providing contact information and selecting a username and password. Once users have logged in, they are usually taken to their account space.

The account space provides several options for the user to view and edit their account information, navigate through the website, manage contacts, view saved histories, and edit or create projects. In the account page, users can select to manage contacts. Users can keep a list of potential buyers, suppliers, experts, third parties, and others. Users can organize the contacts into groups, add or remove contacts from their contact list or communicate with one or more selected contacts. Users can also manage privileges for the contacts. The privileges can enable the contacts to participate in private message board communications and blogs managed by the user. Users can also select and view news in their account space. Users can select from the available news sources on the website and select how they would like view and organize the news within their account space.

The account space can be used to view and save searches and transaction information. A search tool within the account space enables users to conduct searches for products, services, distributors, experts and other information within the site. The account space can enable users to view previous searches and save search histories for review at a later time. The account space can also enable users to view previous orders made through the account. Orders can include purchases and sales transacted through the account. At step 112, products and services can be offered through the system 10. The account space enables suppliers to provide products or services and offer them on the website. Suppliers can select to create a new product or service. The integration engine 18 opens a window for users to enter information regarding their products or services such as, for example, a name, description, pricing, availability, shipping, and the like. The information can also include a list and/or details of product attributes including technical features, components or ingredients, benefits, and other like information about the product. Supplier information can be automatically linked with the product through the account engine 32. The information can be stored in the database for retrieval by the website and to enable users to view the product and services. The supplier can also associate tags with the products or services to enable others to search for the product more easily.

At step 114, projects can be created and/or opened. Projects can be accessed through the account space and are used to manage and organize resources on the integration system 10 collected by a user to resolve a need. These needs can include researching and obtaining components for a product, researching and obtaining services related to the product including laboratory testing, distribution, manufacturing, marketing and the like. The project space provides several options for the project manager, that is, the user that created the project.

Project managers can add components to the project. The project manager can add news articles, knowledgebase entries, communications, and selected products and services to the project. For example, a project manager who is developing a paint can use the project to organize their research for the paint. Some components of the paint can be comprised of formulations. A formulation can comprise the amount and source of ingredients that make up a product or component. Some examples of formulations can include things such as resins, pigments, additives and the like. In this example, the paint developer can use the project space to organize formulations necessary for manufacturing the paint with the desired characteristics. As the developer finds formulations for the paint or finds ingredients necessary for the formulations, the developer can add those ingredients to their project space in order to store the information and organize the project. Thus, the project space can be used by the paint formulator to manage the individual ingredients, components, and formulations for making the paint. Likewise, the developer can add news, knowledgebase entries, and communications to their project.

At step 116, communications can be facilitated between users. Users can communicate through private and public modes such as message boards, blogs, email, private messages, live chat, and the like. One aspect of the communication engine 34 enables account users to post public or private messages from their project space.

Selecting to post a question opens a dialogue space to post a message in a message board. Within the dialogue space, the user can choose to communicate in public or in private. The message board is organized into public sections and private sections. Posting messages in a public section enables all users to view the message and respond to it. In one embodiment, users are also able to rate messages posted in the message board. The ratings can help users determine the value of a posted message.

Alternatively, users can post messages in a private section of the message board. The private section is divided into private communities. Users can create a confidential community for discussing particular topics and can limit who is able view and respond to messages in the community. The privileges are available only to registered users who are members of the private community. The community's manager, that is, the user that creates and manages the private community, determines which users are members of the private community. In one embodiment, the community manager can also provide tags for the community to make the community easy to locate and search by others.

At step 118, products and services can be searched. Users can select a search by clicking a search tool located in one or more places on the website, including the homepage. The search tool is designed to enable users to obtain search results within three steps. As shown in FIG. 4, users can begin searches by entering text into the search tool at step 130. At step 132, users can select products attributes from lists provided by the search tool. The search engine can search for keywords and/or tags similar to the text entered into the search tool. The search engine can also use the selected search criteria to obtain search results. The search criteria can include items such as lists of tags, product or service attributes, price ranges, suppliers, and the like. Once the search criteria are selected, the search engine processes the products or services in the database according to the search criteria and returns a set of results. The results can include a list of products or services that satisfy the search criteria by containing keywords, tags or associated product attributes. In one embodiment, users can sort search results based on selected criteria. The results can include the name of the product or service, a brief description of the product or service and/or search criteria found in the product or service. The user can select to add a selected product or service to their project space from the search results. Doing so allows the users to access the product or service information easily from the product rather than having to conduct the search for that product or service in the future. Moreover, the user can save the search and/or search results in their project.

At step 134, a selection from the search results opens a corresponding information page. The information page contains detailed information of the selected product or service and includes any information provided by the supplier. If the selected product is a formulation, then the formulation itself can be included in the detailed information. The formulation can include the formulation's ingredients and other product attributes. The ingredients can further include the amounts of the ingredients and their source or sources. Users can select to print, fax, or e-mail the information page to themselves or others. The detailed information can also contain user ratings of the product or service. The user ratings can include comments by users who have purchased or used the service and/or a numerical or alphabetical rating of the product or service. The information page can also contain links to purchase the product or service or request a sample.

At step 120 on FIG. 3, transactions for goods and/or services can be facilitated between users. Transactions can include purchases or requests for product samples.

Purchasers can select to purchase products or services from their information pages.

If the product page contains a formulation, the user can select to purchase the entire formulation or a single ingredient from the formulation. If the purchaser selects to purchase a good or service, the transaction engine 36 provides a screen for the user to select the quantity, address, shipping terms, and the like. In one embodiment, the account engine 32 provides this information for verification by the purchaser. The account engine 32 can obtain the information from preferences saved in the user account. Once the user has accepted the quantity, address, and shipping terms, the user can select to confirm the purchase. In one embodiment, the transaction engine 36 can conduct a credit check if the purchaser has not been approved by a previous credit check. The transaction engine 36 can generate an e-mail confirming the purchaser for delivery to the purchaser and supplier. The user can choose a payment option such as an online escrow payment or a traditional payment method such as credit cards, checks, bank account transfers, and the like.

The transaction engine 36 can process the payment and provide confirmation to both the purchaser and the supplier that the payment has been confirmed. If the purchaser selects to pay via an escrow the user can input necessary information on the page and verify information derived from the preceding purchase pages and interact with existing escrow system 10s like AIiP ay from alibaba.com. If a traditional payment is made the transaction engine 36 can process and verify the payment. If payment is to be made via an invoice, the transaction engine 36 can generate the invoice provided to the purchaser and the seller.

In one embodiment, the transaction engine 36 is also able to handle royalty payments. For example, if the supplier in the transaction is a distributor for manufacturer, the transaction system 10 can transfer a designated amount of the payment to the distributor as a royalty and the remaining amount to manufacturer or vice versa. The transaction engine 36 can also provide royalty payments to a manager of the integration engine 18. Users can agree to provide a royalty payments to the system 10 manager for transaction conducted through the system 10. The transaction engine 36 can transfer a predetermined amount or percentage of transactions to the system 10 managers as a royalty payment. The transaction engine 36 can handle processing that payment automatically upon the completion of a transaction between a purchaser and a seller.

The transaction engine 36 can also automate orders involving distributors. For example, a supplier that provides a formulation may obtain ingredients for the formulation from a third party. The transaction engine 36 can notify the third party of the purchase and provide information such as the items orders, the amounts, and dates when delivery of the items to the supplier are required. Products and services purchased through the transaction engine 36 can be automatically added to an active project. Moreover, the order information can be saved in the user space for later review. The order information can include an order number and/or tracking number for tracking shipments of any products from the supplier to the purchaser.

The transaction engine 36 can also enable the user to order a sample from a supplier. The user can select to request a sample from a product information page. In one embodiment, the account engine 32 can retrieve account information from information contained in the database. In another embodiment, the transaction engine 36 can request information needed for the transaction from the purchaser. The purchaser can verify the information and can select to sample of an entire formulation or a single ingredient of the formulation if appropriate. Once the purchaser has confirmed the information, the transaction engine 36 notifies the supplier of the request for the sample and provides the appropriate information necessary to fulfill the request. A confirmation can be sent to both the purchaser and the supplier along with information to enable the supplier and purchaser to contact one another.

While users are reviewing search results and conducting transactions, users can select to communicate with suppliers. User can communicate with suppliers by clicking on a link to the supplier on the information page. The link can provide any number of communication options such as providing an e-mail link to the supplier, providing a pop-up window for the user to enter a private message to deliver to the account mailbox of the supplier, opening a chat window to allow real-time communication between the purchaser and the supplier, and the like. As such, the integration system 10 enables communication between purchasers and one or more suppliers before during and after transactions.

In addition to enabling the various steps of FIGS. 3 and 4, the system 10 is designed to provide a single-site solution that addresses the needs of low volume purchasers by incorporating into the system a process flow that can be used for individual projects to guide the purchaser through the design and development phases leading up to final product identification and ordering. This is done using software resident on the server that defines a collection of steps that are then displayed graphically for the user. With reference back to FIG. 3, once the user has logged in and created or opened an existing project, the system presents the user with a graphical user interface that includes the various steps that are necessary and/or useful in assisting the purchaser with product design and development. This not only provides the purchaser with a roadmap through the overall process, but also provides the purchaser with the needed access to resources to carry out each step. Thus, for example, in the early stages where product information and technical assistance are most needed, the steps can include links to the software tools needed to obtain such information, such as those provided via the research engine 30 and communication engine 34 of FIG. 2. Subsequent steps represented graphically on the screen can provide access to other resources such as the transaction engine 36 so that the purchaser can, for example, select a link on the graphically-displayed process that enables them to quickly order a sample of a particular supplier's product that they have identified as being of interest.

This approach to guiding the design and development process provides a technical solution to a problem not addressed by current computer-based systems; that is, it provides a duality of functions in that it guides the low volume purchaser through a process for which they typically have little outside support that is generally delivered in a disjointed, sporadic manner, while at the same time providing a centralized tool to carry out each of the steps in a coordinated manner. This benefits both the low volume purchaser as well as the suppliers since it provides the purchasers with low-cost access to the needed technical resources in a manner that can be tied in with the suppliers' own product offerings.

As will be appreciated by those skilled in the art, the functionality described above for system 10 can be implemented using known hardware systems with suitable software programming to carry out the architectural and functional features of the system. Such programming is within the level of skill in the art.

It is to be understood that the foregoing description is not a definition of the invention, but is a description of one or more preferred exemplary embodiments of the invention. The invention is not limited to the particular embodiment(s) disclosed herein, but rather is defined solely by the claims below. Furthermore, the statements contained in the foregoing description relate to particular embodiments and are not to be construed as limitations on the scope of the invention or on the definition of terms used in the claims, except where a term or phrase is expressly defined above. Various other embodiments and various changes and modifications to the disclosed embodiment(s) will become apparent to those skilled in the art. All such other embodiments, changes, and modifications are intended to come within the scope of the appended claims.

As used in this specification and claims, the terms "for example," "for instance," and "such as," and the verbs "comprising," "having," "including," and their other verb forms, when used in conjunction with a listing of one or more components or other items, are each to be construed as open-ended, meaning that that the listing is not to be considered as excluding other, additional components or items. Other terms are to be construed using their broadest reasonable meaning unless they are used in a context that requires a different interpretation.

Claims

1. A method for facilitating interactions between product designers, suppliers, and third parties through a website, comprising the steps of: posting technical content supplied from product designers, suppliers, and third parties on the website, such that the posted content is viewable by all registered users of the website; providing private communications between two or more registered users of the website, said private communications viewable by only the two or more registered users; and conducting searches at the request of product designers for products and services offered by suppliers through the website and providing search results; facilitating purchases between the product designers and suppliers for products and services offered through the website.

2. A method for the procurement of formulations, comprising the steps of: receiving formulations and a description of attributes associated with each formulation from at least one source; receiving a request for formulations having one or more attributes selected in the request; performing a search for formulations having the selected attributes; providing search results based on the performed search, the search results including a list of formulations; and facilitating a transaction for an amount of at least one of the formulations provided in the search results.

3. A method for the procurement of formulations, comprising the steps of: receiving formulations from multiple sources and lists of attributes associated with the formulations; receiving third party feedback for the received formulations and providing the third party feedback; receiving a search request for formulations containing one or more desired attributes; performing the search request for formulations containing the selected attributes; providing search results based on the performed search request, the search results including a list formulations containing one or more of the selected attributes; and facilitating a transaction for an amount of one of the formulations provided in the search results.

4. A computer-based system for providing resources to users of the system, comprising: a plurality of client computers; at least one server accessible by the client computers via a global computer network; and an integration engine resident on the one or more servers, the integration engine including a plurality of resource engines that enable product developers via the client computers to access research information concerning a product, obtain supplier assistance and product information, carry out individual communications with interested parties, and conduct transactions for the development and production of a product.