Customer-hosted automated configuration catalog

• US 20060100889A1
• Filed: 04/11/2005
• Published: 05/11/2006
• Est. Priority Date: 06/13/2000
• Status: Abandoned Application

• Current Assignee: Theresa M. Gosko
• Original Assignee: Theresa M. Gosko
• Inventors: Gosko, Theresa M.
• Application Number:
  US11/103,158
• Publication Number:
  US 20060100889A1
• Time in Patent Office: Days
• US Class Current: 705/26
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

A system and method allows a purchaser to configure products for one or more products. The method includes receiving a data file, incorporating the data file into a procurement system of the purchaser, and configuring the products using the data file, the products including non-commodity products configurable according to business rules. The purchaser includes at least one of a customer, a third party acting on behalf of the customer, supplier and a manufacturer. The data file allows the purchaser to configure the products independent of a third party provided configuration tool by providing manipulable parameters that configure a non-commodity product or service. The manipulable parameters include upgrades, downgrades and swapping of components. The data file also includes non-manipulable parameters that contribute to the configuration of a non-commodity product or service including parent components, orphan components, child components, configuration components and optional components. The data file also includes business rules including rules for manipulating buyer-generated data including functional rules and configuration rules for integrating the data file into the procurement system. The method further includes generating a purchase requisition using the procurement system, the generating the purchase requisition using data from the data file and creating a table of a plurality of components for configuring the products, the table identifying the relationships between and among the components. The method further includes allowing the purchase to self-determine whether orders placed in the procurement system will trigger a rejection of an order due to activation of a discontinue date for discontinued product or configuration.

Claims

1-33. -33. (canceled)

34. A method for a purchaser to configure products for one or more products comprising:

receiving a data file, the data file including

manipulable parameters that contribute to the configuration of a non-commodity product or service, the manipulable parameters include upgrades, downgrades and swapping of components; and

,

non-manipulable parameters that contribute to the configuration of the non-commodity product or service, the non-manipulable parameters including parent components, orphan components, child components, configuration components and optional components;

incorporating the data file into a procurement system of the purchaser; and

configuring the products using the data file, the products including non-commodity products configurable according to business rules.

35. The method of claim 34 wherein the purchaser includes at least one of a customer, a third party acting on behalf of the customer, supplier and a manufacturer.

36. The method of claim 34 wherein the data file allows the purchaser to configure the products independent of a third party provided configuration tool.

37. The method of claim 34 wherein the procurement system is one of an asset management system, an ordering system, a world wide web-based order management system, an outsourced ordering system on behalf of the purchaser.

38. The method of claim 34 wherein the data file is incorporated into a procurement system of the purchaser, the data file providing a catalog of configurable components enabling the purchaser to configure the products.

39. The method of claim 38 wherein the data file includes business rules in a structured data format.

40. The method of claim 39 wherein the business rules including rules for manipulating buyer-generated data including functional rules and configuration rules for integrating the data file into the procurement system.

41. The method of claim 34 wherein the data file includes data shared by the purchaser and a seller.

42. The method of claim 41 wherein the seller is one of a manufacturer of products and party representing a manufacturer of products.

43. The method of claim 34 further comprising:

generating a purchase requisition using the procurement system, the generating the purchase requisition using data from the data file.

44. The method of claim 34 further comprising:

creating a table of a plurality of components for configuring the products, the table identifying the relationships between and among the components.

45. The method of claim 43 wherein the data from the data file includes a configuration identifier, a price of the configuration, type of components, custom or bundled, upgrades, downgrades and additions permitted with pricing, work flow data identifying add configurations, discontinue configuration, replace configuration, effective data, and discontinue date.

46. The method of claim 41 wherein the data file includes pricing according to predetermined agreements with the purchaser and a seller.

47. The method of claim 34 wherein the data file includes at least one of factory-installed components, non-factory-installed components, and subsystem configurations.

48. The method of claim 34 wherein the data file includes a core configuration including:

commodity and non-commodity default services; and

customer-specific integration components.

49. The method of claim 48 wherein the customer-specific integration components include customer specific software and menus, images, customer asset tag labels, and security cables.

50. The method of claim 48 wherein the customer-specific integration components include at least one of transportation industry options and transportation services.

51. The method of claim 47 wherein the factory installed, non-factory installed, customer kit and solution data includes the associated Stock Keeping Units (SKUs), including a third parties or a manufacturer generated SKUs and pricing.

52. The method of claim 34 further comprising:

acknowledging configurations within the data file.

53. The method of claim 52 wherein the acknowledging includes acknowledging each parameter of configurable products, including components, pricing, services as acceptable and not acceptable.

54. The method of claim 34 further comprising:

self-determining whether orders placed in the procurement system will trigger a rejection of an order due to activation of a discontinue date for discontinued product or configuration.

55. The method of claim 34 further comprising:

automatically activating product configuration displays within the procurement system based on effective dates within the data file.

56. The method of claim 54 wherein the self-determining allows a customer to take corrective action.

57. The method of claim 34 further comprising:

determining based on receiving an action code within the data file denoting which configurations will require replacement in the procurement system, the action code permitting the purchaser to update open orders in the procurement system prior to delivery of an order without manual interaction.

58. The method of claim 34 wherein the data file provides data shared by the purchaser'"'"'s procurement system and a seller'"'"'s invoicing system.

59. The method of claim 34 wherein the data file is an EDI format.

60. The method of claim 34 wherein the data file is in a proprietary file format.

61. The method of claim 34 wherein the electronic data file is in an SGML format.

62. A method for a purchaser to configure products for one or more products comprising:

receiving a data file, the data file including

data relating to a configuration identifier, a price of the configuration, type of components, custom or bundled, upgrades, downgrades and additions permitted with pricing, work flow data identifying add configurations, discontinue configuration, replace configuration, effective date, and discontinue date;

data relating to pricing according to predetermined agreements with the purchaser and a seller;

data relating to factory-installed components, non-factory-installed components, and subsystem configurations;

data relating to a core configuration including commodity and non-commodity default services and customer-specific integration components;

incorporating the data file into a procurement system of the purchaser; and

configuring the products using the data file, the products including non-commodity products configurable according to business rules.

63. The method of claim 62 wherein the customer-specific integration components include customer specific software and menus, images, customer asset tag labels, and security cables.

64. The method of claim 62 wherein the customer-specific integration components include at least one of transportation industry options and transportation services.

65. The method of claim 62 wherein the factory installed, non-factory installed, customer kit and solution data includes the associated Stock Keeping Units (SKUs), including a third parties or a manufacturer generated SKUs and pricing.