Systems, methods, and software for generating, customizing, and automatedly e-mailing a request for quotation for fabricating a computer-modeled structure from within a CAD program

Description

RELATED APPLICATION DATA

This application claims the benefit of priority of U.S. Provisional Patent Application Ser. No. 62/134,362, filed on Mar. 17, 2015, and titled “SYSTEMS, METHODS, AND SOFTWARE FOR ASSISTING A USER IN GENERATING A REQUEST FOR PRICING FOR FABRICATING A COMPUTER-MODELED STRUCTURE WITHIN A CAD PROGRAM,” which is incorporated by reference herein in its entirety.

FIELD OF THE INVENTION

The present invention generally relates to the field of computer-aided design. In particular, the present invention is directed to systems, methods, and software for assisting a user in generating a request for pricing for fabricating a computer-modeled structure within a CAD program.

BACKGROUND

Presently, CAD (computer-aided design) programs allow users to create computer models of products to be manufactured. After a design is complete, the user typically then seeks out one or more suppliers to which they may send a request for pricing (hereinafter “RFP”) in order to obtain a price associated with fabricating the designed structure. This process of seeking out suppliers tends to create additional work and expense for a user and/or their employer, as this process requires the user or an associated agent to research individual suppliers, often relying on easily misplaced notes and personal experience to identify possible suppliers to use for a particular project or design.

SUMMARY OF THE DISCLOSURE

A method of assisting a user in generating a request for pricing (RFP) of a price for fabricating one or more instantiations of a structure represented in a computer model. The method being executed in a CAD program and including presenting to the user, in an RFP user interface, a list of suppliers that provide fabrication services; receiving from the user via the RFP user interface a selection of at least one supplier from the list of suppliers to create at least one selected supplier; generating the RFP; and automatedly sending the RFP to each of the at least one supplier for which a selection is received in conjunction with the receiving.

A machine-readable storage medium containing machine-executable instructions for performing a method assisting a user in generating a request for pricing (RFP) of a price for fabricating one or more instantiations of a structure represented in a computer model, the method being executed in a CAD program and comprising: a first set of machine-executable instructions for presenting to the user, in an RFP user interface, a list of suppliers that provide fabrication services; a second set of machine-executable instructions receiving from the user via the RFP user interface a selection of at least one supplier from the list of suppliers to create at least one selected supplier; a third set of machine-executable instructions for generating the RFP; and a fourth set of machine-executable instructions for automatedly sending the RFP to each of the at least one supplier for which a selection is received in conjunction with said receiving.

BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:

FIG. 1A is a high-level block diagram of an RFP system for assisting a user in generating an RFP for fabricating a computer-modeled structure;

FIG. 1B is a table illustrating aspects of an exemplary user database;

FIG. 1C is a table illustrating aspects of an exemplary supplier database;

FIG. 2 is a flow diagram illustrating a method for assisting a user in generating an RFP for fabricating a computer-modeled structure;

FIG. 3 is a set of representative screenshots depicting various aspects of an exemplary user interface implemented in accordance with aspects of the invention; and

FIG. 4 is a block diagram of a computing system that can be used to implement any one or more of the methodologies disclosed herein and any one or more portions thereof.

DETAILED DESCRIPTION

Aspects of the present invention include systems, methods, and software for assisting a user in generating a request for pricing (RFP) for fabricating a computer-modeled structure. Herein, an RFP may be a request for a price such as a rough estimate, a quote, a firm fixed cost, or anything in between these, among others. A structure may be an object or part having a particular geometry, while a computer model may be a virtual representation of a structure and may be created using appropriate computer-aided design programs. Examples of structures include a piece of sheet metal, a solid cube, a cylindrical pipe, an injection molded plastic toy, an article of apparel or clothing such as a shirt made from cotton, and an assembly of various parts such as a vehicle, among others. In some embodiments, software made in accordance with the present invention interfaces with a supplier database in order to provide a user with an interactive supplier list. The user may then interact with the supplier list to identify one or more preferred providers, select one or more suppliers from the supplier list, and cause the software to generate an RFP for each selected provider. One or more aspects of the present invention can be implemented in any of a wide variety of manners, such as within a single computing device or by two or more networked computing devices, among others. In some embodiments, functionalities of the system may be integrated into computer modeling programs directly via add-on software.

As would be apparent to one reasonably skilled in the art, the invention may be applied to other manufacturing types, including but not limited to the manufacture of apparel. Both sheet metal and apparel designers use CAD systems to design their products, using sheets of flat, material for manufacture. Design data, such as material choice, precise dimensions, or locations of additional features may be embedded within the digital design. Designers may choose different metals or fabrics (including non-woven materials such as leather) depending on the strength and other inherent properties of the material, which affects what manufacturing methods may be necessary to work the material. Purchased components (in some cases, identical purchased components) may be added to the design. CAD programs may be used to visualize the shape of the finished product. In both sheet metal and apparel manufacturing the sheet (metal or fabric) may be cut or stamped by a variety of methods using computerized machines. Units are moved from station to station during manufacture. Where sheet metal is connected by rivets or welding, sheet fabric is connected by stitching or gluing. Surface finishes may be applied to both; both may be painted, silk-screened, or otherwise covered with a protective substance.

Turning now to the drawings, FIG. 1A illustrates an exemplary RFP system 100 made in accordance with the present invention. In this example, RFP system 100 includes a CAD program 104 and a CAD model 108 associated with the CAD program. CAD program 104 may allow a user to design or edit computer-modeled structures, such as CAD model 108, which may be imported from another location and may be designed using another CAD program. CAD model 108 may specify desired shapes, properties, and/or other aspects of a structure that a user may request a supplier (or manufacturer) to fabricate in accordance with such information. System 100 further includes an RFP application 112, which in the embodiment shown is contained within CAD program 104. In accordance with various aspects of the invention, RFP application 112 provides a user of CAD program 104 with the ability to review supplier information efficiently and to select the best supplier based on a plurality of relevant factors. RFP application 112 may be an application included within CAD program 104, such as an add-on module or an integral (or native) part of the CAD program, capable of retrieving a list of suppliers and presenting that list to a user, preferably in an interactive form. It is noted that although FIG. 1A depicts CAD model 108 and RFP application 112 as being included within CAD program 104 in this example, it will be appreciated that, in some embodiments, the CAD model and RFP application may be provided separately from the CAD program provided that the CAD model is accessible by the CAD program and the RFP application is able to interface and/or operate in conjunction with the CAD program and CAD model.

In the example of FIG. 1A, RFP application 112 contains a number of subcomponents. For example, RFP application 112 includes a graphical user interface (GUI) 116 enabling interaction between a user and CAD program 104 and/or RFP application 112. RFP application 112 and/or CAD program 104 may cause GUI 116 to appear on a computer monitor, tablet, or mobile device, for example, and the GUI may present a user with a supplier list 120, which may include a list of suppliers and information associated therewith, as well as controls a user may manipulate to interact with the supplier list. For example, supplier list 120 may contain a list of suppliers capable of fabricating a structure specified in CAD model 108 and information associated with each supplier such as ratings and capabilities, among others.

In the present embodiment, GUI 116 further includes a sorter 124, which may be a window or set of controls that enable a user to interact with supplier list 120. For example, a user may sort supplier list 120 as a function of information included therein by manipulating a component of GUI 116 (e.g., using a mouse or other pointing device) in order to activate sorter 124. Such information may include, for example, supplier ratings and capabilities, among others. Sorter 124 may operate in a binary fashion (e.g., by sorting suppliers according to a certain capability, causing GUI 116 to list suppliers having that capability separately from suppliers that do not possess that capability) or in one or more other fashions (e.g., sorting suppliers from highest rating to lowest rating, alphabetically, and/or according to distances between the user's office and individual supplier facilities, among others).

In some embodiments, though not shown in FIG. 1A, RFP application 112 and/or sorter 124 may interface with one or more mapping, ranking, or capability-listing databases, websites, or applications, among others in order to populate supplier list 120 and/or enable a user to sort suppliers based on information received or derived therefrom. Further, sorter 124 may interface with one or more global positioning systems (not shown) in order to calculate distances, such as a distance between the user's office and individual supplier facilities, and/or to determine a location of a supplier's delivery truck. In such embodiments, sorter 124 may enable a user to sort suppliers based on particular suppliers' distances from the user, the location of a suppliers' delivery trucks, or an estimated delivery or response time sorter 124 derives from one or both, among others. GUI 116 further includes an editor 128, which may include a window or other user interface allowing a user to add or remove one or more suppliers and/or information associated with one or more suppliers in supplier list 120.

In this example, RFP application 112 further includes sorting criteria 132, which may include a data structure containing one or more rules or procedures specifying how sorter 124 should sort supplier list 120. For example, sorting criteria 132 may contain rules and/or procedures that cause sorter 124 to sort suppliers in supplier list 120 in alphabetical order and/or in order from highest to lowest rating, among others. In addition, sorter 124 may contain a set of initial sorting rules to be applied immediately to supplier list 120 once the sorter is activated. RFP application 112 may also include one or more user database 136, which may contain information associated with suppliers a designer or other user routinely uses and/or other suppliers a user indicates as being potential suppliers, either for any project or design or for a particular project or design. User database 136 may store primary keys identifying each supplier (or any type of data suitable for uniquely identifying suppliers) and user-provided information associated with suppliers such as user-defined distribution lists and notes. User database 136 may also contain data from a supplier database, which may be imported therefrom and/or periodically updated. FIG. 1B illustrates an exemplary selection of information that user database 136 may include. Such information may include one or more fields, such as primary key and/or supplier name, distribution lists to which the user has added one or more suppliers, and one or more ratings and/or comments that users have caused to be associated with one or more suppliers. User database 136 may further include fields associating one or more suppliers with one or more capabilities, geographical locations, and/or community ratings, as illustrated in FIG. 1B. Notably, although some fields are indicated as being “native” and others are indicated as being “imported” (e.g., from supplier database 140) in FIG. 1B, any of these fields may be native or imported, as desired. It is noted that although FIG. 1A depicts sorting criteria 132 and user database 136 as being included within RFP application 112 in this example, it will be appreciated that, in some embodiments, the sorting criteria and user database may be provided separately from the RFP application 112 and/or CAD program 104 provided that the CAD program and/or RFP application can access and modify the sorting criteria and user database. It is further noted that any of the databases disclosed herein may comprise two or more databases.

Further describing the present embodiment, system 100 includes a supplier database 140 by either an internal third party, such as a user company database of suppliers or an external third party data source such as mfg.com or thomasnet.com, which may be created and maintained by a user, designer, or by a third party and may be personal to a particular user. Although supplier database is shown as being separate from CAD program 104, in some embodiments supplier database 140 may be located within CAD program 104, within a supplier's project life-cycle management (PLM) system, or may be external to a user. Supplier database 140 may store information associated with one or more suppliers, which may in some embodiments be predefined by a user. Individual suppliers and/or other entities may provide such information directly or indirectly to the supplier database, and such information may be specific to a particular user, a particular type of design or structure, and/or a particular industry, though in some cases such information may apply to any user, type of design or structure, and/or any industry. For example, supplier database 140 may store primary keys identifying each supplier (or any type of data suitable for uniquely identifying suppliers such as supplier names, ratings, and information specifying processes the supplier is capable of performing). In some embodiments, a user may add suppliers from supplier database 140 to user database 136 and, optionally, provide notes or rankings associated with such added suppliers. It is noted that in this embodiment, supplier database 140 or a subset of supplier database 140 may be saved or mirrored to user database 136 and stored there. In an alternative embodiment, user database 136 may be optional, and information stored therein may be saved within supplier database 140, which may be accessed directly each time information is required instead of accessing user database 136. FIG. 1C illustrates an exemplary selection of information that supplier database 140 may include. Such information may include one or more fields that may contain information associated with suppliers, such as primary key and/or supplier name, materials workable by a given supplier, capabilities and/or processes the supplier can perform, one or more geographical locations associated with the supplier (e.g., a zip code associated with a manufacturing facility), and a rating, such as a star rating and/or community rating. It is noted that although FIG. 1A depicts supplier database 140 as separate from CAD program 104 in this example, it will be appreciated that in some embodiments it may be contained within or otherwise implemented by CAD program 104 or RFP application 112. In some embodiments, RFP application 112 or CAD program 104 may contain supplier database 140 and system 100 may implement the functionality of user database 136 and supplier database 140 using a single database or multiple networked or otherwise linked databases.

In this example, RFP system 100 further includes a plurality of suppliers 144(1) to 144(N), such as “Supplier 1” 144(1), “Supplier 2” 144(2), and up to any number of suppliers (designated by “Supplier N” 144(N)), which may include one or more suppliers and/or aggregators of supplier information. Suppliers 144(1) to 144(N) may be a supplier that can receive RFPs and provide pricing based thereon. In some embodiments, suppliers 144(1) to 144(N) may provide their name, capabilities, and any other information directly or indirectly to supplier database 140. For example, suppliers 144(1) to 144(N) may provide information to supplier database 140 indicating that the supplier is capable of working aluminum and brass with a certain amount of precision, which the supplier may indicate using, for example, a 5-star rating system (e.g., more stars indicating more precision). Alternatively or additionally, an aggregator of suppliers may provide such information, which may additionally include ratings of quality, performance, and/or attentiveness and/or other ratings drawn from other users or designers or other sources. For example, in some embodiments, an aggregator may derive ratings for individual suppliers from various sources, such as independent websites or magazines or one or more individual users' user databases, among others, and provide those ratings to a user's user database. In some cases, aggregators may provide basic information associated with suppliers (e.g., supplier capabilities) to any user free of charge while requiring a one-time or recurring (e.g., monthly) fee to receive ratings the aggregator has independently derived.

In the present embodiment, system 100 further includes an RFP 148 that CAD program 104 is operable to produce, though in other embodiments RFP application 112 may also or alternatively be operable to produce the RFP. RFP 148 may include information derived from CAD model 108 and/or information input by a user, among other information. Such information may provide details enabling fabrication of one or more structures, any necessary lead-time or other timing or scheduling details or requirements, and/or information identifying a particular designer or user who generated RFP 148 and/or who transmitted the RFP to one or more suppliers 144(1) to 144(N). CAD program 104 and/or RFP application 112 may be operable to send RFP 148 to one or more suppliers 144(1) to 144(N) via e-mail or other suitable means for communicating documents. However, in some embodiments the CAD program and/or RFP application may, optionally as a function of a user setting, only allow printing of the RFP and prevent electronic or other transfer of the RFP in an attempt to ensure that unauthorized parties cannot intercept the RFP. Such functionality may be particularly useful, for example, when an RFP contains trade secrets, government classified information, or other sensitive information.

System 100 further provides a number of data links to enable data communication between various portions thereof; system 100 may implement these links in the form of, for example, an Internet connection, a local network connection, and/or any other connection between electronic devices or portions of one or more devices. For example, system 100 provides a user data link 152, which, in this embodiment, enables communication between CAD program 104 and supplier database 140. For example, RFP application 112 may retrieve supplier information from supplier database 140 via user data link 152. Further, user database 136 and supplier database 140 may synchronize primary keys or other information via user data link 152. In some embodiments, RFP application 112 and/or CAD program 104 may derive information associated with one or more suppliers 144(1) to 144(N) from various sources, such as independent websites or magazines or one or more individual users' user databases, among others, and store those ratings in one or more users' user database 136 in association with one or more corresponding suppliers.

System 100 further provides a supplier update data link 156, which may be one or more data links between supplier database 140 and suppliers 144(1) to 144(N) that transmit information and updates from the suppliers describing their processes and capabilities, and messages from the supplier database necessary for operation the supplier database and may be, for example an internet connection, a local network connection, or any connection between electronic devices or portions of devices as are commonly known in the art. In some embodiments, more than one user data link 152 and/or supplier update data link 156 may be required, potentially along with other similar data links, particularly when, for example, user database 136 is stored in a separate location from RFP application 112 or when more than one supplier database is utilized, among other possible implementations of the invention that will become readily apparent to one of ordinary skill upon reading this disclosure in its entirety.

In operation, a user may create CAD model 108 in CAD program 104 or import a separate CAD model. When the user wishes to send an RFP to one or more suppliers 144(1) to 144(N), they may activate RFP application 112, which may send a query to supplier database 140 via user data link 152 to request information associated with one or more suppliers 144(1) to 144(N) capable of accepting an RFP. Alternatively, 112 may send a query directly to user database 136 to request information associated with one or more suppliers in user database 136 that are capable of accepting an RFP, without ever needing to access a supplier database 140. In response to the query, supplier database 140 may provide a response containing information associated with one or more suitable suppliers 144(1) to 144(N) to RFP application 112 using user data link 152. After receiving the response, RFP application 112 may populate supplier list 120 based on the contents of the response. RFP application 112 may further sort the contents of the response and/or the contents of user database 136 according to sorting criteria 132. GUI 116 may then display one or more aspects of supplier list 120 and sorter 124, such as, for example, one or more supplier names and/or ratings and user interface elements that a user can manipulate to sort one or more of the names and/or ratings. After the user has sorted desired aspects of supplier list 120 to their satisfaction, the user may select desired supplier(s) to send an RFP to, and may then manipulate GUI 116 to request that RFP application 112 produce an RFP and/or submit an RFP to one or more suppliers 144(1) to 144(N). RFP application 112 may then transmit RFP 148 to one or more user-selected suppliers 144(1) to 144(N). In some embodiments, a user may edit the contents of user database 136 using editor 128 at any time.

FIG. 2 illustrates a method 200 for assisting a user in generating an RFP that can be implemented by one or more components of system 100, such as CAD program 104 and/or RFP application 112. A user may utilize method 200 to, for example, retrieve, review, sort and select suppliers and transmit one or more RFP 148 to one or more suppliers 144(1) to 144(N). In an exemplary embodiment, method 200 starts at step 205, which involves providing CAD program 104 with CAD model 108, RFP application 112, and, optionally, default sorting criteria 132. In some embodiments, a third party or other entity may provide a user with CAD program 104, and the provided CAD program may contain CAD model 108 and/or RFP application 112. Further, RFP application 112 may contain sorting criteria 132 and/or user database 136. In one embodiment, RFP application 112 may initialize sorting criteria 132 with a default setting, such as alphabetical sorting or a preferred initial set of suppliers.

At step 210, one or more users, suppliers 144(1) to 144(N), and/or another entity or entities provides user database 136 and supplier database 140, which may contain information related to one or more suppliers 144(1) to 144(N) and their capabilities. At optional step 215, a user may edit user database 136 using editor 128. For example, a user may manipulate an aspect of editor 128 in GUI 116 to provide RFP application 112 with any desired changes to user database 136. For instance, a user may add comments to user database 136 indicating a contact person and contact phone number for a particular supplier and/or may add one or more suppliers to or otherwise manage a particular distribution list within user database 136. At step 220, CAD program 104 and/or RFP application 112 queries supplier database 140 via user data link 152 for information regarding suppliers 144(1) to 144(N) capable of accepting RFPs. In one embodiment, a user may, for example, manipulate one or more aspects of GUI 116 to cause such a query to request only information regarding suppliers that have already been assigned a particular user rating or range of ratings (e.g., 3 stars or greater) and/or that are already included in a particular distribution list. In another example, a user may manipulate one or more aspects of GUI 116 to cause such a query to request only information regarding suppliers that can work aluminum, can drill holes and bend metal, and are located within 100 miles of a user's ZIP code or GPS coordinates. Further, a user, administrator, or other entity may specify automated and/or permanent (on a per-user, per-project, per-design, per-corporation, or other suitable basis) query limitations. For example, a user may manipulate GUI 116 to specify that queries should be limited to suppliers capable of working materials contained in a given project or design. Similarly, if a user manipulates one or more aspects of GUI 116 to cause a query to, e.g., request suppliers capable of working brass materials, GUI may provide an option to the user to make that limitation permanent (on a per-user or other basis). Such automated and permanent query limitations may last indefinitely or only for a short period that a user, administrator, or other entity may specify by, for example, manipulating one or more aspects of GUI 116.

At step 225, CAD program 104 and/or RFP application 112 receives a response including information associated with suppliers from supplier database 140. For example, such a response may include ten companies listed in supplier database 140 that are capable of accepting RFPs and information associated with some or each, such as one or more primary keys, supplier names, workable materials, capabilities, available processes, and/or ratings, among others. At step 230, CAD program 104 and/or RFP application 112 populates a supplier list 120 with one or more portions of the information received from supplier database 140 and/or one or more portions of information contained in user database 136. For example, RFP application 112 may correlate the information received from supplier database 140 with information contained in user database 136 (e.g., by identifying common primary keys between the supplier database and user database) in order to identify suppliers and associated information with which to populate supplier list 120. For example, RFP application 112 may populate supplier list 120 with ten companies and information associated with some or each, such as one or more primary keys, supplier names, workable materials, available processes, ratings, associated distribution lists, and/or comments.

At optional step 235, RFP application 112 may sort one or more aspects of supplier list 120 according to sorting criteria 132. For example, a user may interact with one or more aspects of editor 128 and/or GUI 116 to cause RFP application 112 to sort suppliers in the order dictated by sorting criteria 132 (e.g., alphabetical order by supplier name). Sorting criteria 132 may contain a set of initial sorting rules which may be applied at this time. At step 240, GUI 116 displays one or more aspects of supplier list 120. At step 245, RFP application 112 offers an opportunity for a user to specify one or more custom sorting criteria. If a user wishes to specify a custom sorting criterion, method 200 proceeds to step 250; however, if a user does not wish to specify a custom sorting criterion, the method proceeds to step 270.

At step 250, a user manipulates GUI 116 or otherwise provides an indication of a desired custom sorting criterion to RFP application 112. For example, a user may indicate that sorter 124 or RFP application 112 should sort suppliers in supplier list 120 by rating in order from largest-to-smallest. Or a user may wish to search only within a pre-defined preferred group of suppliers or only within a group of suppliers newly enrolled in Supplier Database 140. At step 265, GUI 116 displays one or more aspects of supplier list 120 sorted according to sorting criteria 132. Finally, after step 265, method 200 returns to step 245, at which point RFP application 112 may offers another opportunity for a user to specify one or more custom sorting criterion.

At step 270, after a user indicates that they do not wish to specify any further custom sorting criterion at step 245, RFP application 112 receives a user selection of one or more preferred suppliers. A user may base such a selection on ratings, capabilities, and/or other information, such as information contained in supplier list 120, and may provide such a selection by manipulating GUI 116 or otherwise interacting with RFP application 112. At step 275, CAD program 104 and/or RFP application 112 output one or more RFP 148 and may optionally communicate the one or more RFP to one or more suppliers in accordance with the user selection provided at step 270.

FIG. 3 illustrates a series of screenshots depicting exemplary aspects of RFP system 100. Screenshot 300A represents GUI 116 as a user may see it during operation of RFP system 100. In this example, screenshot 300A includes five exemplary fields 304, which may include categories of information according to which a user may sort one or more aspects of supplier list 120 via sorter 124. Fields 304 may include various categories of information stored in supplier database 140 such as supplier names and one or more associated ratings, available processes (e.g., injection molding), distance between the supplier and user, and/or distribution lists (e.g., a prototype distribution list), among others. In some embodiments, a user and/or an entity operating supplier database 140, among others, may add additional fields to supplier list 120 by, for example, using editor 128. Screenshot 300A further includes data entries 308 associated with fields 304, which may include a name of a particular supplier and one or more associated ratings, available processes, distances, and/or distribution lists. Screenshot 300A further includes a select button 312, which may be, for example, a soft selection button in GUI 112. A user may utilize select button 312 by, for example, clicking it with a mouse or otherwise selecting it in order to indicate that they wish to send one or more RFP 148 to selected suppliers. Screenshot 300A also includes a cursor 316A that a user can utilize to manipulate one or more aspects of GUI 112 through, e.g., a mouse or other pointing device. Finally, screenshot 300A includes sorting buttons 320, which may be a set of soft selection buttons and/or toggles associated with in sorter 124 in GUI 112. A user may manipulate sorting buttons 320 in order to sort one or more aspects of supplier list 120 by, for example, selecting any one of the sorting buttons.

Screenshot 300B represents GUI 116 as a user may see it during operation of RFP system 100 after the user has caused sorter 124 to sort one or more aspects of supplier list 120 by descending ratings. As in screenshot 300A, screenshot 300B also includes a cursor 316B. Screenshot 300C represents GUI 116 as a user may see it during operation of RFP system 100 after the user has caused sorter 124 to additionally sort one or more aspects of supplier list 120 according to whether the individual suppliers are included in a prototype distribution list. In this example, after such additional sorting, GUI 116 no longer displays suppliers not included in the prototype distribution list. In some embodiments, users, administrators, and/or other entities can optionally specify whether to continue displaying suppliers that do not meet one or more aspects of one or more sorting criterion in the form of a global setting that applies to all sorting criterion, a setting that applies only to one or more particular criterion, a setting that applies to one or more users, or a setting that applies to one or more projects or designs, among others. In this example, as shown in screenshot 300C, after the sorter has reduced the supplier choices to only those on the Prototyper List, a user then has selected two suppliers (Supplier 1 and Supplier 4). As in screenshots 300A and 300B, screenshot 300C also includes a cursor 316C, which, in screenshot 300C, is poised to click select button 312 in order to cause RFP application 112 to generate one or more RFP 148.

It is to be noted that any one or more of the aspects and embodiments described herein may be conveniently implemented using one or more machines (e.g., one or more computing devices that are utilized as a user computing device for an electronic document, one or more server devices, such as a document server, etc.) programmed according to the teachings of the present specification, as will be apparent to those of ordinary skill in the computer art. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those of ordinary skill in the software art. Aspects and implementations discussed above employing software and/or software modules may also include appropriate hardware for assisting in the implementation of the machine executable instructions of the software and/or software module.

Such software may be a computer program product that employs a machine-readable storage medium. A machine-readable storage medium may be any medium that is capable of storing and/or encoding a sequence of instructions for execution by a machine (e.g., a computing device) and that causes the machine to perform any one of the methodologies and/or embodiments described herein. Examples of a machine-readable storage medium include, but are not limited to, a magnetic disk, an optical disc (e.g., CD, CD-R, DVD, DVD-R, etc.), a magneto-optical disk, a read-only memory “ROM” device, a random access memory “RAM” device, a magnetic card, an optical card, a solid-state memory device, an EPROM, an EEPROM, and any combinations thereof. A machine-readable medium, as used herein, is intended to include a single medium as well as a collection of physically separate media, such as, for example, a collection of compact discs or one or more hard disk drives in combination with a computer memory. As used herein, a machine-readable storage medium does not include transitory forms of signal transmission.

Such software may also include information (e.g., data) carried as a data signal on a data carrier, such as a carrier wave. For example, machine-executable information may be included as a data-carrying signal embodied in a data carrier in which the signal encodes a sequence of instruction, or portion thereof, for execution by a machine (e.g., a computing device) and any related information (e.g., data structures and data) that causes the machine to perform any one of the methodologies and/or embodiments described herein.

Examples of a computing device include, but are not limited to, an electronic book reading device, a computer workstation, a terminal computer, a server computer, a handheld device (e.g., a tablet computer, a smartphone, etc.), a web appliance, a network router, a network switch, a network bridge, any machine capable of executing a sequence of instructions that specify an action to be taken by that machine, and any combinations thereof. In one example, a computing device may include and/or be included in a kiosk.

FIG. 4 shows a diagrammatic representation of one embodiment of a computing device in the exemplary form of a computer system 400 within which a set of instructions for causing a control system, such as the RFP system of FIG. 1, to perform any one or more of the aspects and/or methodologies of the present disclosure may be executed. It is also contemplated that multiple computing devices may be utilized to implement a specially configured set of instructions for causing one or more of the devices to perform any one or more of the aspects and/or methodologies of the present disclosure. Computer system 400 includes a processor 404 and a memory 408 that communicate with each other, and with other components, via a bus 412. Bus 412 may include any of several types of bus structures including, but not limited to, a memory bus, a memory controller, a peripheral bus, a local bus, and any combinations thereof, using any of a variety of bus architectures.

Memory 408 may include various components (e.g., machine readable media) including, but not limited to, a random access memory component, a read only component, and any combinations thereof. In one example, a basic input/output system 416 (BIOS), including basic routines that help to transfer information between elements within computer system 400, such as during start-up, may be stored in memory 408. Memory 408 may also include (e.g., stored on one or more machine-readable media) instructions (e.g., software) 420 embodying any one or more of the aspects and/or methodologies of the present disclosure. In another example, memory 408 may further include any number of program modules including, but not limited to, an operating system, one or more application programs, other program modules, program data, and any combinations thereof.

Computer system 400 may also include a storage device 424. Examples of a storage device (e.g., storage device 424) include, but are not limited to, a hard disk drive, a magnetic disk drive, an optical disc drive in combination with an optical medium, a solid-state memory device, and any combinations thereof. Storage device 424 may be connected to bus 412 by an appropriate interface (not shown). Example interfaces include, but are not limited to, SCSI, advanced technology attachment (ATA), serial ATA, universal serial bus (USB), IEEE 1394 (FIREWIRE), and any combinations thereof. In one example, storage device 424 (or one or more components thereof) may be removably interfaced with computer system 400 (e.g., via an external port connector (not shown)). Particularly, storage device 424 and an associated machine-readable medium 428 may provide nonvolatile and/or volatile storage of machine-readable instructions, data structures, program modules, and/or other data for computer system 400. In one example, software 420 may reside, completely or partially, within machine-readable medium 428. In another example, software 420 may reside, completely or partially, within processor 404.

Computer system 400 may also include an input device 432. In one example, a user of computer system 400 may enter commands and/or other information into computer system 400 via input device 432. Examples of an input device 432 include, but are not limited to, an alpha-numeric input device (e.g., a keyboard), a pointing device, a joystick, a gamepad, an audio input device (e.g., a microphone, a voice response system, etc.), a cursor control device (e.g., a mouse), a touchpad, an optical scanner, a video capture device (e.g., a still camera, a video camera), a touchscreen, and any combinations thereof. Input device 432 may be interfaced to bus 412 via any of a variety of interfaces (not shown) including, but not limited to, a serial interface, a parallel interface, a game port, a USB interface, a FIREWIRE interface, a direct interface to bus 412, and any combinations thereof. Input device 432 may include a touch screen interface that may be a part of or separate from display 436, discussed further below. Input device 432 may be utilized as a user selection device for selecting one or more graphical representations in a graphical interface as described above.

A user may also input commands and/or other information to computer system 400 via storage device 424 (e.g., a removable disk drive, a flash drive, etc.) and/or network interface device 440. A network interface device, such as network interface device 440, may be utilized for connecting computer system 400 to one or more of a variety of networks, such as network 444, and one or more remote devices 448 connected thereto. Examples of a network interface device include, but are not limited to, a network interface card (e.g., a mobile network interface card, a LAN card), a modem, and any combination thereof. Examples of a network include, but are not limited to, a wide area network (e.g., the Internet, an enterprise network), a local area network (e.g., a network associated with an office, a building, a campus or other relatively small geographic space), a telephone network, a data network associated with a telephone/voice provider (e.g., a mobile communications provider data and/or voice network), a direct connection between two computing devices, and any combinations thereof. A network, such as network 444, may employ a wired and/or a wireless mode of communication. In general, any network topology may be used. Information (e.g., data, software 420, etc.) may be communicated to and/or from computer system 400 via network interface device 440.

Computer system 400 may further include a video display adapter 452 for communicating a displayable image to a display device, such as display device 436. Examples of a display device include, but are not limited to, a liquid crystal display (LCD), a cathode ray tube (CRT), a plasma display, a light emitting diode (LED) display, and any combinations thereof. Display adapter 452 and display device 436 may be utilized in combination with processor 404 to provide graphical representations of aspects of the present disclosure. In addition to a display device, computer system 400 may include one or more other peripheral output devices including, but not limited to, an audio speaker, a printer, and any combinations thereof. Such peripheral output devices may be connected to bus 412 via a peripheral interface 456. Examples of a peripheral interface include, but are not limited to, a serial port, a USB connection, a FIREWIRE connection, a parallel connection, and any combinations thereof.

The foregoing has been a detailed description of illustrative embodiments of the invention. Various modifications and additions can be made without departing from the spirit and scope of this invention. Features of each of the various embodiments described above may be combined with features of other described embodiments as appropriate in order to provide a multiplicity of feature combinations in associated new embodiments. Furthermore, while the foregoing describes a number of separate embodiments, what has been described herein is merely illustrative of the application of the principles of the present invention. Additionally, although particular methods herein may be illustrated and/or described as being performed in a specific order, the ordering is highly variable within ordinary skill to achieve methods, systems, and software according to the present disclosure. Accordingly, this description is meant to be taken only by way of example, and not to otherwise limit the scope of this invention.