The present invention generally relates to the field of computer-aided design and structure fabrication. In particular, the present invention is directed to automated fabrication price quoting and fabrication ordering of computer-modeled structures.
Technical specifications and engineering drawings typically convey a variety of information about a to-be-fabricated structure, such as a part or an assembly of components. Examples of such information includes information about geometry, materials, finishes, connections, hardware, special processes, dimensions, tolerances, and others things as known in the art. The documents are prepared by engineers; however, manufacturers rely on the documents for manufacturing preparation to build the desired structure, such as a part or an assembly of multiple components. There are differing skill levels involved on both the engineering side and the manufacturing side, which has led to a gap between the two stages involved in fabricating a structure.
Various changes in engineering and manufacturing have generally driven fabrication cost estimates to be created from the hardcopies of the documents, which causes several problems and disadvantages. As an initial matter, each estimator, i.e., the person developing a price quote for a particular part or assembly, will often interpret the information in the hardcopies differently due to their level of experience and/or other factors. Thus, using hardcopies, it can be extremely difficult, if not impossible, to maintain consistent pricing. Additionally, human reviewers can overlook key features on the hardcopies such that they are not included in the finished part and/or assembly. There is also often a lengthy time period required for quoting prototypes. All of the required documents may not be available using the hardcopy approach, and fabricators can be forced to use only the information that the engineers supply, which may be incomplete. If additional information is needed, further communication between the estimator and the engineer is required. Additionally, human interaction is required, which leads to errors and discrepancies between analyses performed by different people.
Also disadvantageously, using a hardcopy approach, preparing the paperwork for information not related to the drawings is often more time-consuming than designing the structure itself. Advanced calculations are needed to determine various information, such as, a perimeter length, flat area, holes sizes, flat size, sheet usage, etc., needed to create a cost estimate when employing hardcopies. Furthermore, missing information can typically only be obtained by contacting an engineer, which is time consuming and inefficient.
In one implementation, the present disclosure is directed to a method of providing, to a user on a user computer, a firm fabrication-price quote for fabricating one or more instantiations of a structure represented in a computer model viewable on computer-modeling software, the method being executed by a price-quoting system. The method includes providing a price-quoting user interface to the user on the user computer, wherein the price-quoting user interface is integrated with the computer-modeling software; extracting, via the computer-modeling software, pricing data from the computer model so as to provide extracted pricing data; receiving, via the price-quoting user interface, non-extracted pricing data corresponding to the structure; correlating at least one of 1) the extracted pricing data and 2) the non-extracted pricing data to a set of actual fabrication resource requirements needed for fabrication; determining the firm fabrication-price quote as a function of the extracted pricing data, the non-extracted pricing data, and pricing parameter data; and displaying the firm fabrication-price quote to the user via the price-quoting user interface.
In another implementation, the present disclosure is directed to a machine-readable storage medium containing machine executable instructions for performing a method of providing, to a user on a user computer, a firm fabrication-price quote for fabricating one or more instantiations of a structure represented in a computer model viewable on computer-modeling software, said machine-executable instructions designed and configured to be executed by a price-quoting system. The machine-executable instructions include a first set of machine-executable instructions for providing a price-quoting user interface to the user on the user computer, wherein the price-quoting user interface is integrated with the computer-modeling software; a second set of machine-executable instructions for extracting, via the computer-modeling software, pricing data from the computer model so as to provide extracted pricing data; a third set of machine-executable instructions for receiving, via the price-quoting user interface, non-extracted pricing data corresponding to the structure; a fourth set of machine-executable instructions for correlating at least one of 1) the extracted pricing data and 2) the non-extracted pricing data to a set of actual fabrication resource requirements needed for fabrication; a fifth set of machine-executable instructions for determining the firm fabrication-price quote as a function of the extracted pricing data, the non-extracted pricing data, and pricing parameter data; and a sixth set of machine-executable instructions for displaying the firm fabrication-price quote to the user via the price-quoting user interface.
These and other aspects and features of non-limiting embodiments of the present invention will become apparent to those skilled in the art upon review of the following description of specific non-limiting embodiments of the invention in conjunction with the accompanying 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:
Aspects of the present invention include software tools and techniques for automatedly generating one or more price quotations for fabricating one or more instantiations of a structure that is represented in a computer model. Using various ones of these tools and techniques, precise geometries and other pricing data extracted from the computer model can be used along with appropriate non-extracted pricing data and pricing parameters from a particular fabricator to create highly precise and highly repeatable fabrication-price quotes, which are firm quotes upon which a user can place a fabrication order with the fabricator. Other aspects of the present invention include software tools and techniques for allowing a user to place an order for fabricating one or more instantiations of a computer modeled structure, such as in conjunction with the generating of the price quotation. Still other aspects of the present invention include systems for generating such price quotes and permitting such ordering. These and other aspects of the present invention will become readily apparent upon reviewing this entire disclosure. Before proceeding with describing the numerous aspects of the present invention in detail, a number of definitions of certain terms used throughout this disclosure, including the appended claims, are first presented. These terms shall have the following meanings throughout unless noted otherwise. Like terms, such as differing parts of speech, differing tenses, singulars, plurals, etc., for the same term (e.g., fabricating, fabricate, fabrication, fabrications, fabricated) shall have commensurate meanings.
Structure: A “structure” can be any physical thing that can be made by or under the control of a human and/or under the control of one or more machines. For example, a “structure” can be made by hand, using one or more tools, using one or more pieces of machinery, or any combination thereof. Examples of structures include, but are not limited to objects, parts, assemblies of components, buildings, vehicles, machines, semiconductor devices, computing devices, and electronic equipment, among many others. Fundamentally, there is no limitation on what a “structure” can be other than that it is fabricated.
Fabricate: To “fabricate” a structure is perform a step or collection of steps needed to physically instantiate the structure. In this context, fabrication includes, but is not limited to steps of cutting, machining, milling, turning, making connections, molding, in particular injection molded parts, casting, stamping, forming, bending, depositing, etching, drilling, etc. Synonyms that fall within the meaning of “fabricate” herein include, but are not limited to manufacture, erect, assemble, mold, and form, among many others.
Computer Model: A “computer model” is a virtual, for example, digital, model of a physical structure as created using appropriate computer-modeling software, such as SOLIDWORKS® software (available from Dassault Systèmes SolidWorks Corp, Waltham, Mass.), AUTOCAD® software (available from Autodesk, Inc., San Rafael, Calif.), and MICROSTATION® software (available from Bentley Systems, Inc., Exton, Pa.), among many others. A “computer model” can be of any type, such as a wireframe or solid model, among others, or any combination thereof, and can be saved in a computer file using any suitable file protocol, such as .SLDPRT, .SLDASM, .STP, and .IGS, among others. A “computer model” includes information about the geometry and/or other properties of the modeled structure.
Extracted Pricing Data: “Extracted pricing data” are input data to a system of the present disclosure that are extracted from a computer model and that influence the cost of fabricating one or more instantiations of the structure represented by the computer model. It is noted that while the term “extracted” is used herein, the process of obtaining pricing data from a computer model is more one of scraping than extraction, because the pricing data is not removed from the computer model (which would destroy its integrity) but rather scraped, i.e., copied from the computer model and processed as needed for use in the system. Examples of “extracted pricing data” include, but are not limited to, geometry (such as size, shape, dimensions, areas, configurations, numbers of components and other features, such as openings, recesses, bosses, etc.), type(s) of material (in computer models wherein materials can be specified), connection type(s) and features (in computer models wherein such information can be specified), finish type(s) (in computer models wherein finishes can be specified), and purchased or otherwise pre-fabricated parts (e.g., hardware) and subassemblies (e.g., hinges), among many others. Fundamentally, there is no limitation on the data that can constitute “extracted pricing data,” other than that they are present in a computer model and extractable therefrom and that they influence the cost of fabrication and, therefore, a firm fabrication-price quote.
Non-Extracted Pricing Data: “Non-extracted pricing data” are input data to a system of the present disclosure, other than extracted pricing data, required from a user or other source in order to generate a price quote. Examples of “non-extracted pricing data” include, but are not limited to, number of instantiation desired to be fabricated, required delivery date(s), type of delivery, type(s) of material (in computer models wherein materials cannot be specified), connection type(s) and features (in computer models wherein such information cannot be specified), finish type(s) (in computer models wherein finishes cannot be specified), among others. “Non-extracted pricing data” can be input or received in any suitable manner, such as via a user-input interface or a non-computer-model electronic document, such as a form-fillable portable document format (PDF) document, or a non-computer-model data file, among others. Fundamentally, there is no limitation on the data that can constitute “non-extracting pricing data,” other than that they are not extracted from a computer model, and that they influence the cost of fabrication and, therefore, a firm fabrication-price quote.
Pricing Parameters: “Pricing parameters” are parameters that are applied to extracted and non-extracted pricing data and that otherwise affect the cost of fabricating one or more instantiations of the structure represented in a computer model and, therefore, affect a firm fabrication-price quote. “Pricing parameters” are pricing parameters from a particular fabricator with which, if the user accepts the firm price quote(s), places a fabrication order. Examples of “pricing parameters” include, but are not limited to, material costs, fabrication costs, assembly costs, tooling/setup costs, finishing costs, connection costs, handling costs, shipping costs, expediting costs, packaging costs, markups, volume discounts, etc. Pricing parameters can be, for example, per-unit costs/prices or one-time costs/prices, depending on the particular parameter. Fundamentally, there are no limitations on the parameters that can constitute “pricing parameters” other than they can be applied to extracted and non-extracted pricing data or otherwise affect the cost of fabricating one or more instantiations of a structure represented by a computer model.
Firm Fabrication-Price Quote: A “firm fabrication-price quote” is a price at which a user can get one or more parts and/or one or more instantiations of a part fabricated by a fabricator. In other words, it is a price at which a fabricator commits to charging or otherwise honoring for a particular fabrication order. As described below in detail, a firm fabrication-price quote is determined as a function of actual fabrication resource requirements to which a fabricator is subjected.
Actual Fabrication Resource Requirements: “Actual fabrication resource requirements” are fabrication parameters and constraints that a fabricator is subjected to in fabricating the one or more instantiations of the modeled structure. General examples of actual fabrication resource requirements include: engineering/set-up time for fabrication functions such as programming, punching, cutting, molding, casting, deburring, forming, bending, joining, welding, grinding and vibrating, tapping, countersinking, hardware installation, part assembly, inspection, and finishing such as plating and silk screening; available fabricating equipment, and specialized tooling required, among many others. In a sheet-metal fabrication context, examples of actual fabrication resource requirements include sheet sizes of sheet material (e.g., sheet metal), sheet thicknesses of sheet material, number of parts that can be fit on a sheet of material, bend properties (e.g., length, inside radius, angle, count, etc.), constraints on available forming equipment, and corresponding set-up and/or engineering time, among others. In a machining fabrication context, examples of actual fabrication resource requirements include constraints on available machining cutting tools and appurtenances and on part-handling equipment, and any corresponding set-up and/or engineering time, among others. In an injection-molding fabrication context, examples of actual fabrication resource requirements include design and construction of molds, constraints on available injection-molding equipment and/or materials, and any corresponding engineering and/or set up time. In a metal-casting fabrication context, examples of actual fabrication resource requirements include design and construction of molds, constraints on available casting equipment and/or materials, and any corresponding engineering and/or set up time. In a metal-stamping fabrication context, examples of actual fabrication resource requirements include design and construction of dies, constraints on available stamping equipment and/or materials, and any corresponding engineering and/or set up time. Those skilled in the art will readily appreciate that the foregoing examples are non-limiting and that, fundamentally, there is no limit on the actual fabrication resource requirements that can be considered in generating a firm fabrication-price quote of the present disclosure.
With the foregoing terms and meanings in mind, reference is now made to
Examples of hardware 144 that can be used to implement the various steps of method 140 include, but are not limited to, web servers, desktop computers, laptop computers, tablet computers, smartphones, and Internet appliances, wearable computers (e.g., GOOGLE GLASS™ wearable computers), among others. A network of two or more of such devices can include any one or more types of networks, including, but not limited to, a global communications network (such as the Internet), a wide-area network, a local-area network, and a telecommunications network, among others. In this connection, those skilled in the art will also recognize the myriad of ways that the steps of method 140 can be implemented across a network. For example, if any steps of method 140 are implemented on one or more web-servers, they may be performed by suitable software residing on, provided by, and/or executed by such server(s). Such software can include a software application, a software module (such as a plugin to another software application, such as a computer modeling application, web browser, etc.), and/or a software code segment. In many cases, the same or similar software, or any portion thereof, can be implemented on a desktop computer, a laptop computer, and a tablet computer. As another example, various steps of method 140 can be performed by one or more mobile apps running, on, for example, a smartphone or tablet computer, and provided the ability to communicate with one or more other computing devices running software that performs one or more other steps of the method.
In a particular embodiment, all steps of method 140 can be performed by a single computing device, such as a desktop computer or a webserver accessible via a browser, running an integrated software application that performs all steps of method 140 and that may also include computer-modeling functionality as well, such as a computer-modeling software application 148. In another embodiment, some steps of method 140 can be performed on a first computing device, whereas other steps of the method are performed on a second computing device located remotely from the first computing device across a network. An example of the latter embodiment is described below in connection with
Referring now to
At step 210, in conjunction with the user making price-quotation request 152, software 136 extracts pricing data 124′ from computer model 116 to create extracted pricing data 124. As described above, extracted pricing data 124 can be any data that a price-quote-generating algorithm 156 of software 136 needs for generating firm fabrication-price quote(s) 104 and that can be found in and automatedly extracted from computer model 116. A benefit to this automated extraction is that a human user is spared the task of determining this information manually or extracting such data semi-automatedly and working with that data outside computer model 116. The more robust the particular computer-modeling software, such as computer-modeling software application 148, is, i.e., the more information about structure 112 at issue it handles, such as material types, finishes, connection details, etc., the less non-extracted pricing data is required. Depending on the way that non-extracted pricing data 128 is acquired by system 100, this can greatly simplify the process for a user in obtaining firm fabrication-price quote(s) 104 from the system. Indeed, if computer model 116 is highly robust, the only types of non-extracted pricing data 128 that a user may need to input are quantity and/or non-structure related information such as delivery criteria.
Those skilled in the art will understand that pricing data 124′ can be extracted from computer model 116 in any of a variety of ways, depending on how data-extraction code of software 136 is configured. For example, if the data-extraction code is built into computer-modeling software, such as computer-modeling software application 148, the data-extraction code may be preprogrammed to recognize pricing data 124′ within computer model 116 and utilize the internal protocols of that application to gather the that data. As another example, if the data-extraction code is implemented as an external plugin module to computer-modeling software, the code might utilize the application's plugin module protocols. As yet another example, if the data-extraction code is executed externally from the computer-modeling application but not as a plugin, the external code may utilize an application programming interface of the application. Regardless of how software 136 and the data-extraction code are configured, those skilled in the art will readily understand how to design the code.
At step 215, non-extracted pricing data 128 is received via software 136. As with extracted pricing data 124, those skilled in the art will readily understand that non-extracted data 128 can be received in any of a variety of ways, depending on how software 136 is configured in a particular instantiation. For example, software 136 may be configured to allow a user to input non-extracted pricing data 128 via a user interface, such as price-quoting user interface 150, that includes one or more data-input features of one or more differing types, such as, but not necessarily limited to, keyed-input fields, drop-down menus, radio-control selectors, hyperlinks, and other selectors, among others. Those skilled in the art will readily appreciate that the type(s) and number of data-input features can depend on the robustness of computer model 116 relative to pricing data 124′ that it contains and the variety of options available from a particular fabricator. Regarding the former, as noted above, if a version of computer model 116 includes pricing data 124′ such as material type(s), then a non-extracted-pricing-data user interface (not shown) does not necessarily need a data-input feature directed to the material type(s), since that information will be extracted from the computer model. However, for a version of computer model 116 that does not allow the user to specify materials, the non-extracted-pricing-data user interface would need one or more data-input features to allow the user to input the appropriate material(s) needed for an accurate price quote. Of course, material type is but one example of a pricing-data type that can be of either an extracted type or a non-extracted type, and other pricing data that can be of either type can be handled similarly.
A price-quoting user interface of the present disclosure, such as user interface 150, can be implemented in any of a number of ways. For example, if the software code is implemented within computer-modeling software, such as computer-modeling software application 148, then price-quoting user interface 150 may be presented as a graphical user interface of the software application. Similarly, if the software code is executed in a plug-in-type external module, then the user interface may be presented in the same manner. It is noted that such computer-modeling software can be of the type that presents its graphical user interface via an on-screen window under the control of the operating system of the computer on which the application is implemented. However, in other embodiments, the graphical user interface can be presented in another way (via a web-browser, for example) when the computer-modeling software application includes the corresponding software code and is implemented over the World-Wide Web, perhaps in a software-as-a-service model, among others, or when the software code is implemented separately from the computer-modeling software application. Regardless of how the relevant software code is implemented for receiving non-extracted pricing data 128, skilled artisans will be able to create the appropriate software code.
At optional step 220, software 136 can execute a fabricatability algorithm 160 on extracted pricing data 124 from computer model 116 to determine the ability of structure 112 to be fabricated and, therefore, for one or more instantiations 108(1) to 108(N) to be made. Just because a particular structure can be the subject of a computer model, such as structure 112 of computer model 116, does not necessarily mean that all of its features can be fabricated. For example, a certain fabricator may have various limitations on the types of fabrication processes it can perform. As an example, a fabricator may be limited in the types of finishes it can provide, and if a particular computer model specifies a certain finish that the fabricator cannot provide, this can be determined at the validation step. As another example, a particular computer model can also or alternatively be validated for compliance with one or more design requirements, such as a design code or other requirement. In either case, software 136 can notify the user about any noncompliance in any suitable manner and, depending on the noncompliance, may provide the user with an opportunity to proceed with obtaining fabrication-price quote(s) 104, which may only be an estimate if the price-quote-generating algorithms 156 of software 136 cannot properly account for the noncompliance, or to abandon the fabrication-price quotation and/or to remedy the noncompliance before proceeding with the price quotation.
At step 225, software 136 may perform a fabrication validation of computer model 116 to determine how the one or more instantiations 108(1) to 108(N) can be fabricated given a set of fabrication parameters/constraints on the fabrication of instantiations 108(1) to 108(N), i.e., give a set of actual fabrication resource requirements 130. Fabrication validation at step 225 can take any of a variety of forms. For example, in some embodiments fabrication validation at step 225 may require an analysis of virtual features and characteristics of computer model 116, and therefore the actual physical features and characteristics of structure 112, to determine precisely how the one or more instantiations 108(1) to 108(N) will be fabricated in view of the limitations at play. As another example, in other embodiments, fabrication validation at step 225 may include correlating extracted and/or non-extracted pricing data 124, 128 with the appropriate actual fabrication resource requirement(s) 130 and, therefore, with the corresponding pricing parameter(s) 132. Step 225 can be an important step because the details of how the one or more instantiations 108(1) to 108(N) are fabricated directly influence the cost of fabrication to the fabricator and, therefore, the amount of the corresponding firm fabrication-price quote 104 that the fabricator is willing to charge for the fabrication. Those skilled in the art will readily appreciate the importance of fabrication validation to be able to provide a reliable firm fabrication-price quote 104 that accurately accounts for the cost that the fabricator incurs.
In the context of system 100 of
Examples of other cost-influencing actual fabrication resource requirements that validation algorithm 164 may be designed and configured to verify against extracted pricing data 124 of computer model 116 and optionally non-extracted pricing data 128 include, but are not limited to, set-up and/or run times corresponding to finishing, silk screening, tapping, countersinking, hardware installation, assembling multiple parts, bending, rolling, welding (dependent on type, length, finish, method, etc.), and bend characteristics, such as length, radius, angle, etc. Those skilled in the art will understand how to implement a validation algorithm, such as algorithm 164, using extracted and/or non-extracted pricing data 124, 128 and actual fabrication resource requirements 130 to provide fabrication details needed to permit acceptable and reliable firm fabrication-price quotes, such as firm fabrication-price quotes 104.
At step 230, software 136 provides firm fabrication-price quote(s) 104 as a function of extracted pricing data 124 and non-extracted pricing data 128, which includes pricing results from fabrication-validation algorithm 164. Depending on the configuration of software 136 and where the various software components of the price-quoting portion of the software are physically executed, step 230 will typically include several substeps. For example, at substep 235, software 136 may generate firm fabrication-price quote(s) 104 by, for example, applying various ones of pricing parameters 132, such as unit costs, to various ones of the extracted and/or non-extracted pricing data 124 and 128, which, again, includes pricing resulting from fabrication-validation algorithm 164, adding other ones of the pricing parameters, such as fixed setup costs, and applying non-extracted data, such as a number of instantiations for multiple instantiations, to one or more subtotals for a single instantiation, among other things. The precise pricing-quote-generating algorithms 156 used in a particular embodiment will be highly dependent upon, for example, the type(s) of structure(s) 112 handled by software 136, as well as the particularities of the fabricator(s) needed to fabricate the instantiation(s). However, algorithms 156 will be readily implemented by those skilled in the art. It is noted that fabrication-price quote(s) 104 can include, for example, a price per instantiation and/or a total price for multiple instantiations.
Depending on where price-quote-generating algorithms 156 are physically executed within system 100 and where various ones of pricing parameters 132 are stored within the system, one or more of the pricing parameters may need to be obtained by one computer from another computer within the system. Ensuring the use of the most recent set of pricing parameters 132, i.e., verifying current pricing parameter data, is critical, because firm fabrication-price quote(s) 104 are firm quotes that the fabricator will charge for the requested fabrication. Software 136 can be configured in a number of ways to verify current pricing parameter data, i.e., to ensure that price-quote-generating algorithms 156 use the most up-to-date set of pricing parameters 132. For example, if price-quote-generating algorithms 156 are executed on a user computer and pricing parameters 132 are stored and updated on a server, such as a fabricator's server, before the pricing algorithms are executed, the portion of software 136 running on the user computer may request the current pricing parameters from the server. In another example in which price-quote-generating algorithms 156 are executed on a user computer, pricing parameters 132 may be downloaded to the user computer as updates are available. In yet another example wherein price-quoting algorithms 156 are executed on a server, such as fabricator's server or a software-as-a-service server, and substantially the entire price-quoting system 100 is based on that server, price-quoting parameters 132 would be locally available to price-quote-generating algorithms 156 for execution. As still another example of how, software 136 can be configured to make a validity query to the particular fabricator's pricing parameter datastore (not shown) that is maintained by the fabricator. Such a validity query can be structured in any suitable manner, such as by comparing a data set version identifier, which may be a unique code, date stamp, or combination thereof, among others. Software 136 may make this query at any suitable time, such as when the user makes fabrication price request 152. Of course, these are but a few examples of where pricing parameters 132 can be stored and updated relative to where price-quote-generating algorithms 156 can be stored and executed.
It is noted that in some embodiments in which at least some aspects of software 136 are integrated with computer-modeling software, such as computer-modeling software application 148, software 136 may be configured to update fabrication-price quote(s) 104 every time a user makes a change to computer model 116 in essentially real time. This can be accomplished, for example, by software 136 monitoring model 116 for any changes that create one or more new pieces of pricing data 124′ within model 116 and modifying one or more pieces of the pricing data in the model. Then, when software 136 detects any new and/or changed data, it can cause price-quote-generating algorithms 156 to recalculate price quote(s) 104 using the corresponding new and/or changed data. For example, as a user adds a weldment to existing structure 112 within model 116, software 136 may update price quote(s) 104 on the fly, such as when the user adds a member for the weldment and when the user adds a bolt-hole to that member. In some alternative embodiments, software 136 may be configured to allow a user working with computer-modeling software, such as computer-modeling software application 148, to select an update button or the like to cause price-quote-generating algorithms 156 to update price quote(s) after making changes to structure 112 within computer model 116. In still other embodiments, software 136 may be configured to allow a user to choose whether or not to update automatically or manually based on user input. This configuration may be desirable, for example, when continuous updating is premature (e.g., computer model 116 is far from completion) or when continuous updating requires so many computer resources that other functionality is impaired. Those skilled in the art will readily understand the wide variety of ways that updating of price quote(s) 104 can be implemented.
Step 230 may also include a substep 240 at which software 136 conveys fabrication-price quote(s) 104 to the user in any one or more of a variety of ways. For example, fabrication-price quote(s) 104 can be displayed on a display screen (not shown) of the user's computer (e.g., within price-quoting user interface 150), conveyed in an email, and/or provided in some other type of message, including regular mail, an instant message, a text message, etc. and/or as an attachment thereto, among others. Fundamentally, there are no limitations on how a fabrication-price quote can be conveyed to a user.
Step 230 may further include a substep 245 at which software 136 conveys fabrication-price quote(s) 104 to an entity other than the user. For example, the detailed example described below in connection with
At optional step 250, software 136 may receive a fabrication order request 168 in any suitable manner, such as via a user interface (e.g., price-quoting user interface 150) presented to a user on a computing device accessible to the user. In this example, software 136 may present a user-selectable soft control (not shown), such as a soft button or checkbox, that a user can select to make the request. As those skilled in the art will readily appreciate, the selection of the soft control can be effected in any suitable manner, such as by clicking on or otherwise selecting the control using a pointing device (e.g., a mouse) or by touching a touchscreen at the appropriate location to make the selection. The manner of selection will depend on the particular hardware 144 and configuration of software 136 being used on the user's computing device. As alluded to above, the user interface containing the user-selectable control can be provided application-specific software running on the user's device or a web-browser or other remote-access means that allows the user to access price-quotation software functionality remotely from the user's device.
At optional step 255, in response to receiving fabrication order request 168, software 136 provides a fabrication order 172 to the fabricator. Step 255 may be accomplished in any suitable manner, such as sending an email to the fabricator, placing a work order in a queue of a fabricator's scheduling software, among others. Fundamentally, there is no limitation on the way that fabrication order 172 may be made to the fabricator.
It is particularly emphasized that the order of performance of the foregoing steps of method 200 need not be as shown. Rather, they may be implemented in any logical order that results in one or more price quotes and/or one or more fabrication orders.
Exemplary Embodiment for Sheet Metal Fabrication
Whereas the foregoing description describes various aspects of the present invention generically while providing some examples of ways those aspects can be implemented, the following description is primarily directed to a particular detailed embodiment. While this embodiment is described in fairly extensive detail, it should be understood that it is merely illustrative and should not be considered as limiting the much broader scope of the invention. Indeed, as alluded to above, the specific instantiations of the features and software described below are merely one set of such instantiations and features, and those skilled in the art will readily understand that many variations of each individual instantiation and feature are possible, as are differing combinations of these instantiations and features and other instantiations and features.
As will become apparent from reading the following description of this detailed embodiment, the example described below includes a price-quote system and customer portal that allows a customer (i.e., a user) of a sheet-metal fabricator to get an instant firm fabrication-price quote for fabricating one or more instantiations of a structure represented in a computer model that is designed in computer-modeling software, here SOLIDWORKS software. As noted above, the firm fabrication-price quote is not simply an estimate, but rather a firm quote on which a user can place a fabrication order and that the fabricator will honor baring extenuating circumstances. In this illustrative example, the price-quoting software includes a price-quoting application that resides on a user computer as a plugin to the SOLIDWORKS software and obtains user-entered form data (i.e., non-extracted pricing data) and extracts pricing data from the computer-modeling software on the user computer to create the extracted pricing data. Examples of pricing data that can be extracted include but are not limited to, material thickness, part perimeter, flat size, formed size, tap hole types, tap hole count, countersink hole types, countersink hole count, open loops, weld types, weld length, bend angle, bend length, bend radius(ii), hole diameters, hole depths, embosses, silkscreen cuts, and hardware, among others.
In this example, the user provides data pertaining to the material, finish, and quantity for a particular structure or for multiple differing structures, such as differing parts. Once the user has selected the desired options for each part, in this example, that part can be added to a collection of saved parts. Upon successfully creating a full list of parts, in this example the user then selects a soft-button to generate an instant firm fabrication-price quote and spawn an email to the user that includes, in this particular instantiation, a portable document format (PDF) file. In this example, the PDF file includes a detailed list of parts the user has chosen for a quotation and includes a picture of each part. In this particular embodiment, the PDF quote file and computer model is also uploaded to a system file-transfer-protocol (FTP) server located remotely relative to the user computer. As such, if the customer decides to place an order, it can be processed without requiring any additional information from the customer other than a purchase order (PO) number, which is included in the PDF file.
Reference is now made to
With the general arrangement of various elements of system 300 in mind as just described, following is a description of how the system can work to implement a particular instantiation of price-quoting software illustrated in
Pricing engine 324 performs real-time “on-the-fly” pricing using various pricing parameters 344. In this embodiment, pricing engine 324 sends one or more firm fabrication-price quotes 348 via network 320 to price-quoting application 312. Price quotes 348 may include either or both of a price per part 348A and the total price 348B, which price-quoting application 312 can display to the user via user computer 304. In this example, the price-quoting application 312 also generates a PDF quote 352 that it transmits via network 320 to system server 316 so that computer model 336 and PDF quote 352 are available on the system server when the user decides to order the parts in the quote. It is noted that PDF quote 352 can be stored on system server 316 in conjunction with computer model 336 in a pending order 358. Quoting application 312 also sends quote data 356 via network 312 to customer portal 328, which as shown and described in greater detail hereinbelow, includes (or is operatively connected to) a database 360 in which the quote data 356 is stored so that it is available the user when accessing the customer portal. Interaction of the user via user computer 304 with customer portal 328 is represented by a communications link 364.
A change in non-extracted pricing data 332 at step 435 causes price-quoting application 312 to pre-quote the part at step 430.
The user can then add the part to the quote by selecting the Add Part To Quote button 532. Selection of Add Part To Quote button 532 results in the part being added to a collection-of-saved-parts region 536, which lists the parts currently included in the price quote. The user can delete a part from collection-of-saved-parts region 536 by selecting a Delete Part button 540. The price quote can be sent by selecting a Send Quote button 544, which results in the sending of PDF quote 352 and quote data 356 (
In this example, form 334 also includes various tool buttons 548, including a Settings button 552, a Questions button 556, and a “Tutorial” button 560. Tutorial button 560 directs the user to a website (not shown) in which they can view instructional and other educational videos and resources, as shown and described in greater detail herein, for example, with reference to
Reference is now made to
As noted above,
In the present exemplary instantiation, the set up price and run price comprise information that is accessed from server 316 (
The ability to provide firm fabrication-price quotes quickly is enabled by keeping the setup and run costs completely separated throughout the procedure. When run cost, finish cost, and material cost are calculated, this is only performed for a quantity of one. Then this number is later multiplied by the quantity, which enables on-the-fly pricing per steps 725 and 730.
It is noted that method 700 is shown as having its steps in a specific order for the purposes of illustration. However, the steps can be implemented in any order within ordinary skill to achieve the cost calculations shown and described herein.
Exemplary Run-Time Operational Instantiation of Sheet Metal Fabrication Embodiment
Reference is now made to
When the user selects tab 904, computer-modeling software 308 (
Screen display window 1200 of
Web-Based Interface
Referring back to
As noted above, when the user selects Support button 1708, webpage 1700 directs the user to webpage 1800 of
Customer Portal
Reference is now made to
After selecting a price quote displayed in window 2000, in this instance price quote 2008, customer portal 328 directs the user to an ordering window 2100, as shown in
Assemblies
Notably, a price-quoting system of the present disclosure can be readily adapted for quoting firm fabrication prices of assemblies. In some embodiments, such a price quoting system has the ability to combine pricing from custom designed parts and purchased components, as well as other aspects that are not readily quotable by conventional firm fabrication price quoting applications given their strict applicability to generate pricing only from custom designed parts residing within their computer-modeling software.
An assembly consists of two or more parts, or two or more instances of a part, and/or assemblies that are linked together within the CAD modeling system to form a virtual structure. A part can be one solid body or a collection of solid bodies. An assembly may consist of multiple levels of subassemblies which at some point consist of parts. Parts may include custom manufactured items designed by the user, and/or custom manufactured item models imported into the assembly, and/or existing purchased part components modeled by the user, and/or existing purchased part components imported into the assembly. “Purchased part components” structures may be parts that are already designed by a third party and can be readily purchased for example from a catalog or website. In any case, the collection of two or more parts and/or assemblies constitutes an assembly.
In a typical conventional computer-modeling software application, each part is designated its own part file and each assembly is designated its own assembly. For example, in the common SOLIDWORKS® CAD modeling software, virtual representations of parts are stored as .SLDPRT files and virtual representations of assemblies are stored as .SLDASM files, and in the common PTC CREO® CAD modeling software (available from PTC, Inc., Needham, Mass.), virtual representations of parts are stored as .PRT files and virtual representations of assemblies are stored as .ASM files. Generally, an assembly file groups part files together so that a user can arrange, copy, mirror, and pattern parts files to display a virtual representation of a structure. An assembly file can also arrange, copy, mirror, and pattern other assembly files as well. These other assembly files can be said to contain sub-assemblies, but the corresponding files use the same assembly file format. An assembly file, dependent upon the specific computer modeling system, may not contain the subcomponent part(s) and/or assembly(ies) but rather one or more pointers that link to the file(s) containing the constituent part(s) and/or assembly(ies).
An example of an assembly is a box having a base and a lid where the base is connected to the lid by a set of hinges that are fastened to the base and lid through fastening hardware, specifically in the example threaded studs and threaded nuts. The base and lid are custom manufactured parts designed by the user in the CAD modeling software, the stud and the nuts are parts that are purchase components from a third party manufacturer, such as Penn Engineering, Danboro, Pa., and the hinge is an assembly that is purchased from a third party distributor such as McMaster-Carr, Robbinsville, N.J. The hinge assembly consists of the two hinge sides and the pin, all of which are parts. The stud, nut and hinge models are imported CAD models located on the manufacturer and distributor websites. In the SOLIDWORKS® CAD modeling system, the assembly would be contained in an upper level assembly .SLDASM file consisting of individual .SLDPRT files for the base, lid, stud and nut, as well as a .SLDASM file for the hinge. In this example, the hinge assembly, virtually represented in the .SLDASM file as just mentioned, would consist of the right hinge part, left hinge part and pin, each virtually represented in its own .SLDPRT file. Regarding the costs associated with purchased parts/assemblies, here the threaded studs, nuts, and hinge assembly, these costs can be obtained in a variety of ways. For example, the cost for each part can be stored in the corresponding part file in a suitable manner, such as a designated cost item or as a text entry, depending on the format of the file. In some instances, costs for assemblies can be handled on a part-by-part basis in a similar manner, perhaps with a time-based cost of assembly being stored elsewhere, such as in an assembly file for the assembly. As another example, the cost(s) (e.g., total, including time-based assembly cost, or costs broken out individually for parts and assembly time), may be stored only in the assembly file. Those skilled in the art will readily appreciate that there are a variety of ways of handling the full costs (i.e., prices) of purchased parts/assemblies.
In conventional price quoting, if an assembly includes purchased component parts, a user must manually gather the pricing from catalogs, websites or other pricing documentation unassociated with the CAD modeling system in order to include those prices in the sum price of the assembly. In addition, conventional CAD software does not account for costs associated with creating the assembly, for example, in the hinge scenario noted above, the time-based cost to thread fasteners together to fasten the right hinge part to the base and the left hinge part to the lid, as well as the cost associated with the time to insert the pin to join the left hinge part and right hinge part.
In contrast, methodologies of the present disclosure can be implemented on assemblies with such thoroughness as to allow for a price-quoting system of the present disclosure to generate a firm fabrication-price quote for fabricating one or more instantiations of an entire assembly, including accounting for prices associated with fabricating the assembly beyond prices associated with the individual components with limited or no interaction required from the user. For example,
In the example shown, interface 2304 includes an assembly-level welding pane 2308 in which the user can specify parameter for welding, here inches of welding or the number of spot welds. Interface 2304 also includes a components pane 2312, which initially lists all components associated with the assembly, and a component-exclusion pane 2316, which lists any components that the user has elected to leave out of the calculations for the firm fabrication-price quote if for example that component has already been purchased. In this example, a user can exclude a component from the quoting process by highlighting the desired component and selecting an appropriate soft control, here, a “Do not include” soft button 2320. Of course, in other embodiments, the exclusion can occur in other manners, such as by dragging and dropping operations. Once the user has made the desired exclusions and has entered any other information pertinent to the price-quoting process (such as by providing welding information in pane 2308), the user can select a “Continue” button 2324 or other control to signal the price-quoting system to move on to another phase of the price-quoting process, such as finish selection, material selection, etc. for each of the parts of the assembly or to the firm fabrication-price quote generation. In one example, the price-quoting system may search for each component in the assembly and sort the components into groups. In addition, dashboard review and summary interface 2304 may allow the user to add purchased components (such as hinges) by providing appropriate information, such vendor name, part number, lead-time and price. Additionally, interface 2304 may allow the user to perform a search to determine availability and price through requests over a network such as the Internet to provide accurate and up-to-date quotes from different hinge manufacturers and/or distributors and then associate that information, most importantly the pricing information, with that component so that it can be automatically summed into the assembly price. In the embodiment shown, interface 2304 also includes a selected-component-information pane 2328 that displays a rendering of the component selected in components pane 2312 as well as the name of the selected component.
Providing firm fabrication-price quotes to a user based on computer models in an automated manner in response to user input using, for example, system 300 of
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 of the apparatus and method of the present invention, what has been described herein is merely illustrative of the application of the principles of the present invention. For example, specific arrangements and configurations of the various exemplary display windows have been shown for illustrative purposes. However, the layout, style and arrangement of the display windows is highly variable within ordinary skill. Additionally, although the methods herein have been illustrated as being performed in a specific order, the ordering is highly variable within ordinary skill to achieve the quoting methods, systems, and software described herein. Accordingly, this description is meant to be taken only by way of example, and not to otherwise limit the scope of this invention.
Exemplary Computing Device
As noted above aspects and embodiments described herein may be conveniently implemented using one or more machines (e.g., one or more computing devices/computer systems that are part of a fabrication price-quoting and/or ordering system, such as system 100 of
Such software may be, for example, a computer program product that employs one or more a machine-readable hardware storage mediums. 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 hardware storage medium include, but are not limited to, a magnetic disk (e.g., a conventional floppy disk, a hard drive disk), an optical disk (e.g., a compact disk “CD”, such as a readable, writeable, and/or re-writable CD; a digital video disk “DVD”, such as a readable, writeable, and/or rewritable DVD), 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 (e.g., a flash memory), 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 disks or one or more hard disk drives in combination with a computer memory. As used herein, a machine-readable storage medium does not include a signal.
Such software may also include information (e.g., data) carried as a data signal on a data carrier, such as a carrier wave. Such a data signal or carrier wave would not be considered a machine-readable hardware storage medium. 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, a computer workstation, a terminal computer, a server computer, a handheld device (e.g., tablet computer, a personal digital assistant “PDA”, a mobile telephone, 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.
Computing device 2400 can also include a memory 2408 that communicates with the one or more processors 2404, and with other components, for example, via a bus 2412. Bus 2412 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 2408 may include various components (e.g., machine-readable hardware storage media) including, but not limited to, a random access memory component (e.g., a static RAM “SRAM”, a dynamic RAM “DRAM”, etc.), a read only component, and any combinations thereof. In one example, a basic input/output system 2416 (BIOS), including basic routines that help to transfer information between elements within computing system 2400, such as during start-up, may be stored in memory 2408. Memory 2408 may also include (e.g., stored on one or more machine-readable hardware storage media) instructions (e.g., software) 2420 embodying any one or more of the aspects and/or methodologies of the present disclosure. In another example, memory 2408 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.
Computing device 2400 may also include a storage device 2424, such as, but not limited to, the machine readable hardware storage medium described above. Storage device 2424 may be connected to bus 2412 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 2424 (or one or more components thereof) may be removably interfaced with computing system 2400 (e.g., via an external port connector (not shown)). Particularly, storage device 2424 and an associated machine-readable medium 2428 may provide nonvolatile and/or volatile storage of machine-readable instructions, data structures, program modules, and/or other data for computing device 2400. In one example, software instructions 2420 may reside, completely or partially, within machine-readable hardware storage medium 2428. In another example, software instructions 2420 may reside, completely or partially, within processors 2404.
Computing device 2400 may also include an input device 2432. In one example, a user of computing system 2400 may enter commands and/or other information into computing system 2400 via one or more input devices 2432. Examples of an input device 2432 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), touch screen, and any combinations thereof. Input device(s) 2432 may be interfaced to bus 2412 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 2412, and any combinations thereof. Input device(s) 2432 may include a touch screen interface that may be a part of or separate from display(s) 2436, discussed further below. Input device(s) 2432 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 computing device 2400 via storage device 2424 (e.g., a removable disk drive, a flash drive, etc.) and/or network interface device(s) 2440. A network interface device, such as any one of network interface device(s) 2440, may be utilized for connecting computing system 2400 to one or more of a variety of networks, such as network 2444, and one or more remote devices 2448 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, a telephone network, a data network associated with a telephone/voice provider, a direct connection between two computing devices, and any combinations thereof. A network, such as network 2444, may employ a wired and/or a wireless mode of communication. In general, any network topology may be used. Information (e.g., data, software instructions 2420, etc.) may be communicated to and/or from computing system 2400 via network interface device(s) 2440.
Computing device 2400 may further include one or more video display adapter 2452 for communicating a displayable image to one or more display devices, such as display device(s) 2436. 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(s) 2452 and display device(s) 2436 may be utilized in combination with processor(s) 2404 to provide a graphical representation of a utility resource, a location of a land parcel, and/or a location of an easement to a user. In addition to a display device, computing system 2400 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 2412 via a peripheral interface 2456. Examples of a peripheral interface include, but are not limited to, a serial port, a USB connection, a FIREWIRE connection, a THUNDERBOLT connection, a parallel connection, and any combinations thereof.
Exemplary embodiments have been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present invention.
This application claims the benefit of priority of U.S. Provisional Patent Application Ser. No. 61/717,185, filed on Oct. 23, 2012, and titled “SYSTEM AND METHOD FOR GENERATING QUOTES AND ORDERING PARTS,” which is incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4495559 | Gelatt, Jr. et al. | Jan 1985 | A |
5117354 | Long | May 1992 | A |
5465221 | Merat et al. | Nov 1995 | A |
5495430 | Matsunari et al. | Feb 1996 | A |
5552995 | Sebastian | Sep 1996 | A |
5570291 | Dudle et al. | Oct 1996 | A |
5655087 | Hino et al. | Aug 1997 | A |
5758328 | Giovannoli | May 1998 | A |
5847971 | Ladner et al. | Dec 1998 | A |
5870719 | Maritzen et al. | Feb 1999 | A |
5937189 | Branson et al. | Aug 1999 | A |
6031535 | Barton | Feb 2000 | A |
6112133 | Fishman | Aug 2000 | A |
6295513 | Thackston | Sep 2001 | B1 |
6341271 | Salvo et al. | Jan 2002 | B1 |
6343285 | Tanaka et al. | Jan 2002 | B1 |
6611725 | Harrison | Aug 2003 | B1 |
6647373 | Calton-Foss | Nov 2003 | B1 |
6701200 | Lukis et al. | Mar 2004 | B1 |
6750864 | Anwar | Jun 2004 | B1 |
6834312 | Edwards et al. | Dec 2004 | B2 |
6836699 | Lukis et al. | Dec 2004 | B2 |
6859768 | Wakelam et al. | Feb 2005 | B1 |
6922701 | Ananian et al. | Jun 2005 | B1 |
6917847 | Littlejohn et al. | Jul 2005 | B2 |
7006084 | Buss et al. | Feb 2006 | B1 |
7058465 | Emori et al. | Jun 2006 | B2 |
7079990 | Haller et al. | Jul 2006 | B2 |
7085687 | Eckenwiler et al. | Aug 2006 | B2 |
7089082 | Lukis et al. | Aug 2006 | B1 |
7123986 | Lukis et al. | Oct 2006 | B2 |
7134096 | Brathwaite et al. | Nov 2006 | B2 |
7299101 | Lukis et al. | Nov 2007 | B2 |
7305367 | Hollis et al. | Dec 2007 | B1 |
7327869 | Boyer | Feb 2008 | B2 |
7343212 | Brearley et al. | Mar 2008 | B1 |
7359886 | Sakurai et al. | Apr 2008 | B2 |
7366643 | Verdura et al. | Apr 2008 | B2 |
7369970 | Shimizu et al. | May 2008 | B2 |
7418307 | Katircioglu | Aug 2008 | B2 |
7467074 | Faruque et al. | Dec 2008 | B2 |
7496487 | Wakelam et al. | Feb 2009 | B2 |
7496528 | Lukis et al. | Feb 2009 | B2 |
7499871 | McBrayer et al. | Mar 2009 | B1 |
7523411 | Carlin | Apr 2009 | B2 |
7526358 | Kawano et al. | Apr 2009 | B2 |
7529650 | Wakelam et al. | May 2009 | B2 |
7565139 | Neven, Sr. et al. | Jul 2009 | B2 |
7565223 | Moldenhauer et al. | Jul 2009 | B2 |
7567849 | Trammell et al. | Jul 2009 | B1 |
7568155 | Axe et al. | Jul 2009 | B1 |
7571166 | Davies et al. | Aug 2009 | B1 |
7574339 | Lukis et al. | Aug 2009 | B2 |
7590466 | Lukis et al. | Sep 2009 | B2 |
7590565 | Ward et al. | Sep 2009 | B2 |
7603191 | Gross | Oct 2009 | B2 |
7606628 | Azuma | Oct 2009 | B2 |
7630783 | Walls-Manning et al. | Dec 2009 | B2 |
7656402 | Abraham et al. | Feb 2010 | B2 |
7689936 | Rosel | Mar 2010 | B2 |
7733339 | Laning et al. | Jun 2010 | B2 |
7747469 | Hinman | Jun 2010 | B2 |
7748622 | Schon et al. | Jul 2010 | B2 |
7761319 | Gil et al. | Jul 2010 | B2 |
7822682 | Arnold et al. | Oct 2010 | B2 |
7836573 | Lukis et al. | Nov 2010 | B2 |
7840443 | Lukis et al. | Nov 2010 | B2 |
7908200 | Scott et al. | Mar 2011 | B2 |
7957830 | Lukis et al. | Jun 2011 | B2 |
7979313 | Baar | Jul 2011 | B1 |
7993140 | Sakezles | Aug 2011 | B2 |
8000987 | Hickey et al. | Aug 2011 | B2 |
8024207 | Ouimet | Sep 2011 | B2 |
8140401 | Lukis et al. | Mar 2012 | B2 |
8170946 | Blair et al. | May 2012 | B2 |
8175933 | Cook, Jr. et al. | May 2012 | B2 |
8180396 | Athsani et al. | May 2012 | B2 |
8209327 | Danish et al. | Jun 2012 | B2 |
8239284 | Lukis et al. | Aug 2012 | B2 |
8249329 | Silver | Aug 2012 | B2 |
8271118 | Pietsch et al. | Sep 2012 | B2 |
8275583 | Devarajan et al. | Sep 2012 | B2 |
8295971 | Krantz | Oct 2012 | B2 |
8417478 | Gintis et al. | Apr 2013 | B2 |
8441502 | Reghetti et al. | May 2013 | B2 |
8515820 | Lopez et al. | Aug 2013 | B2 |
8554250 | Linaker | Oct 2013 | B2 |
8571298 | McQueen et al. | Oct 2013 | B2 |
8595171 | Qu | Nov 2013 | B2 |
8700185 | Yucel et al. | Apr 2014 | B2 |
8706607 | Sheth et al. | Apr 2014 | B2 |
8768651 | Bhaskaran et al. | Jul 2014 | B2 |
8798324 | Conradt | Aug 2014 | B2 |
8806398 | Brathwaite et al. | Aug 2014 | B2 |
8830267 | Brackney | Sep 2014 | B2 |
8849636 | Becker et al. | Sep 2014 | B2 |
8861005 | Grosz | Oct 2014 | B2 |
8874413 | Mulligan et al. | Oct 2014 | B2 |
8923650 | Wexler | Dec 2014 | B2 |
8977558 | Nielsen et al. | Mar 2015 | B2 |
9037692 | Ferris | May 2015 | B2 |
9055120 | Firman | Jun 2015 | B1 |
9106764 | Chan et al. | Aug 2015 | B2 |
20010023418 | Suzuki et al. | Sep 2001 | A1 |
20010047251 | Kemp | Nov 2001 | A1 |
20020065790 | Oouchi | May 2002 | A1 |
20020087440 | Blair et al. | Jul 2002 | A1 |
20020099579 | Stowell et al. | Jul 2002 | A1 |
20020107673 | Haller et al. | Aug 2002 | A1 |
20020152133 | King et al. | Oct 2002 | A1 |
20030018490 | Magers et al. | Jan 2003 | A1 |
20030069824 | Menninger | Apr 2003 | A1 |
20030078846 | Burk et al. | Apr 2003 | A1 |
20030139995 | Farley | Jul 2003 | A1 |
20030149500 | Faruque et al. | Aug 2003 | A1 |
20030163212 | Smith et al. | Aug 2003 | A1 |
20030172008 | Hage et al. | Sep 2003 | A1 |
20030212610 | Duffy et al. | Nov 2003 | A1 |
20030220911 | Tompras | Nov 2003 | A1 |
20040008876 | Lure | Jan 2004 | A1 |
20040113945 | Park et al. | Jun 2004 | A1 |
20040195224 | Kanodia et al. | Oct 2004 | A1 |
20050055299 | Chambers et al. | Mar 2005 | A1 |
20050125092 | Lukis et al. | Jun 2005 | A1 |
20050144033 | Vreeke et al. | Jun 2005 | A1 |
20050171790 | Blackmon | Aug 2005 | A1 |
20050251478 | Yanavi | Nov 2005 | A1 |
20050273401 | Yeh et al. | Dec 2005 | A1 |
20060085322 | Crookshanks | Apr 2006 | A1 |
20060185275 | Yatt | Aug 2006 | A1 |
20060253214 | Gross | Nov 2006 | A1 |
20070016437 | Elmufdi et al. | Jan 2007 | A1 |
20070067146 | Devarajan et al. | Mar 2007 | A1 |
20070073593 | Perry et al. | May 2007 | A1 |
20070112635 | Loncaric | May 2007 | A1 |
20070198231 | Walch | Aug 2007 | A1 |
20080120086 | Lilley et al. | May 2008 | A1 |
20080183614 | Gujral et al. | Jul 2008 | A1 |
20080269942 | Free | Oct 2008 | A1 |
20080281678 | Keuls et al. | Nov 2008 | A1 |
20090058860 | Fong et al. | Mar 2009 | A1 |
20090208773 | DuPont | Aug 2009 | A1 |
20090299799 | Racho et al. | Dec 2009 | A1 |
20090319388 | Yuan et al. | Dec 2009 | A1 |
20110040542 | Sendhoff et al. | Feb 2011 | A1 |
20110047140 | Free | Feb 2011 | A1 |
20110209081 | Chen et al. | Aug 2011 | A1 |
20110213757 | Bhaskaran et al. | Sep 2011 | A1 |
20120016678 | Gruber et al. | Jan 2012 | A1 |
20120072299 | Sampsell | Mar 2012 | A1 |
20120230548 | Calman et al. | Sep 2012 | A1 |
20120316667 | Hartloff | Dec 2012 | A1 |
20130055126 | Jackson | Feb 2013 | A1 |
20130097259 | Li | Apr 2013 | A1 |
20130100128 | Steedly et al. | Apr 2013 | A1 |
20130138529 | Hou | May 2013 | A1 |
20130144566 | De Biswas | Jun 2013 | A1 |
20130166470 | Grala et al. | Jun 2013 | A1 |
20130218961 | Ho | Aug 2013 | A1 |
20130293580 | Spivack | Nov 2013 | A1 |
20130297320 | Buser | Nov 2013 | A1 |
20130297460 | Spivack | Nov 2013 | A1 |
20130311914 | Daily | Nov 2013 | A1 |
20130325410 | Jung et al. | Dec 2013 | A1 |
20140042136 | Daniel et al. | Feb 2014 | A1 |
20140067333 | Rodney et al. | Mar 2014 | A1 |
20140075342 | Corlett | Mar 2014 | A1 |
20140098094 | Neumann et al. | Apr 2014 | A1 |
20140157579 | Chhabra et al. | Jun 2014 | A1 |
20140207605 | Allin et al. | Jul 2014 | A1 |
20140229316 | Brandon | Aug 2014 | A1 |
20140279177 | Stump | Sep 2014 | A1 |
20140379119 | Sciacchitano et al. | Dec 2014 | A1 |
20150055085 | Fonte et al. | Feb 2015 | A1 |
20150066189 | Mulligan et al. | Mar 2015 | A1 |
20150127480 | Herrman et al. | May 2015 | A1 |
20150234377 | Mizikovsky | Aug 2015 | A1 |
Number | Date | Country |
---|---|---|
154476 | Aug 2001 | WO |
171626 | Sep 2001 | WO |
2001077781 | Oct 2001 | WO |
2006086332 | Aug 2006 | WO |
2007067248 | Jun 2007 | WO |
2011139630 | Nov 2011 | WO |
2011140646 | Nov 2011 | WO |
2011140646 | Nov 2011 | WO |
2013058764 | Apr 2013 | WO |
2014152396 | Sep 2014 | WO |
Entry |
---|
Defining Lead Time for APS Planning; http://t3.apptrix.com/syteline/Language/en-US/Other/Process/Defining_Lead_Time.htm. |
“Quartiles.” Mathisfun.com. Web. <https://www.mathsisfun.com/data/quartiles.html>. Archive. <https://web.archive.org/web/20100909011751/http://www.mathsisfun.com/data/quartiles.html>. |
Wu et al. Interactive 3D Geometric Modelers with 2D UI, 2002, State University of Campinas, www.dca.fee.unicamp.br, Sao Paulo, Brazil; 2002, 8 pages. |
“Upload Your Photos, Print a 3D Model with hypr3D.” SolidSmack. http://www.solidsmack.com/cad-design-news/hypr3d-photo-video-3d-print/; last accessed on Oct. 13, 2015. |
“123D Catch.” Autodesk. http://apps.123dapp.com/catch/. |
Rothganger et al. “3D Object Modeling and Recognition from Photographs and Image Sequences.” Toward Category-Level Object Recognition. 2006, pp. 105-126, vol. 4170 of the series Lecture Notes in Computer Science. Springer Berlin Heidelberg. |
Dealer Information Systems Corporation. “Parts Inventory.” http://dis-corp.com/content/agriculture/inventory/parts-inventory. |
eMachineShop. “Emachineshop Features.” http://www.emachineshop.com/machine-shop/Features/page518.html. |
Retrieved from:http://www.solidworks.com/sw/products/3d-cad/manufacturing-cost-estimation-quoting.htm p. 1: Automatic Manufacturing Cost Estimation Overview; Solidworks; 2015. |
Retrieved from: http://www.gom.com/fileadmin/user_upload/industries/touch_probe_fixtures_EN.pdf; Application Example: Quality Control, Online Calibration and Validation of Fixtures, Jigs and Gauges. GOM mbH, 2008. |
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.194.7785&rep=rep1&type=pdf Kim, Jin Baek, and Arie Segev. “A web services-enabled marketplace architecture for negotiation process management.” Decision Support Systems 40.1(2005): 71-87. |
Jaiswal, Ashutosh et al., “Design and Implementation of a Secure Multi-Agent Marketplace”, Elsevier Science, pp. 1-23, Jun. 3, 2004; http://magnet.cs.umn.edu/papers/Jaiswal04cera.pdf. |
http://www.computer.org/csdl/proceedings/hicss/2005/2268/01/22680038.pdf Bui, Tung, and Alexandre Gachet. “Web services for negotiation and bargaining in electronic markets: Design requirements and implementation framework.” System Sciences, 2005. HICSS'05. |
http://www.bridgelinedigital.com/File%20Library/Repository/eCommerce/Sample-eCommerce-RFP-Template_Bridgeline-Digital.pdf. Sample RFP Template: Ecommerce Platform, Bridgeline Digital, 2014. |
Matchbook, Tealbook, http://www.matchbookinc.com/ Sep. 28, 2015. |
3Diligent, Source Smarter, http://www.3diligent.com/customer.html; Sep. 28, 2015. |
Dassault Systemes, Brochure, Mar. 24, 2010: New Features Type3ToCatia http://www.type3.us/content/download/2202/405535/file/New%20Feature_Type3ToCatia_2010_US%20old.pdf. |
Xue, S., X. Y. Kou, and S. T. Tan. “Natural voice-enabled CAD: modeling via natural discourse.” Computer-Aided Design and Applications 6.1 (2009): 125-136. |
Kou, X. Y., S. K. Xue, and S. T. Tan. “Knowledge-guided inference for voice-enabled CAD.” Computer-Aided Design 42.6 (2010): 545-557. |
Sharma, Anirudh, et al. “MozArt: a multimodal interface for conceptual 3D modeling.” Proceedings of the 13th international conference on multimodal interfaces. ACM, 2011. |
Sorpas (“User Manual,”, Swanted Software and Engineering Aps, 2011 (120 pages)). |
U.S. Appl. No. 14/267,447, dated Aug. 5, 2015, Office Action. |
U.S. Appl. No. 14/197,922, dated Nov. 26, 2014, Office Action. |
U.S. Appl. No. 14/197,922, dated Apr. 27, 2015, Response to Office Action. |
U.S. Appl. No. 14/197,922, dated May 15, 2015, Office Action. |
U.S. Appl. No. 14/267,447, dated Jun. 18, 2015, Response to Office Action. |
U.S. Appl. No. 14/263,665, dated Oct. 8, 2015, Office Action. |
U.S. Appl. No. 14/053,222, dated Jan. 29, 2016, Office Action. |
U.S. Appl. No. 14/311,943, dated Apr. 27, 2016, Office Action. |
U.S. Appl. No. 14/486,550, dated May 26, 2016, Office Action. |
U.S. Appl. No. 14/060,033, dated Jun. 15, 2016, Office Action. |
U.S. Appl. No. 14/172,462, dated Jul. 6, 2016, Office Action. |
U.S. Appl. No. 14/053,222, dated Jul. 29, 2016, Response to Office Action. |
U.S. Appl. No. 14/185,204, dated Jul. 29, 2016, Office Action. |
U.S. Appl. No. 14/062,947, dated Sep. 16, 2016, Office Action. |
U.S. Appl. No. 14/060,033, filed Oct. 22, 2013. |
U.S. Appl. No. 14/053,222, filed Oct. 14, 2013. |
U.S. Appl. No. 14/172,462, filed Oct. 16, 2013. |
U.S. Appl. No. 14/062,947, filed Oct. 25, 2013. |
U.S. Appl. No. 14/172,404, filed Feb. 4, 2014. |
U.S. Appl. No. 14/303,372, filed Jun. 12, 2014. |
U.S. Appl. No. 14/185,204, filed Feb. 20, 2014. |
U.S. Appl. No. 14/195,391, filed Mar. 3, 2014. |
U.S. Appl. No. 14/246,254, filed Apr. 7, 2014. |
U.S. Appl. No. 14/229,008, filed Mar. 28, 2014. |
U.S. Appl. No. 14/197,922, filed Mar. 5, 2014. |
U.S. Appl. No. 14/263,665, filed Apr. 28, 2014. |
U.S. Appl. No. 14/267,447, filed May 1, 2014. |
U.S. Appl. No. 14/311,943, filed Jun. 23, 2014. |
Number | Date | Country | |
---|---|---|---|
61717185 | Oct 2012 | US |