Business information management system

• US 20030040935A1
• Filed: 08/22/2002
• Published: 02/27/2003
• Est. Priority Date: 07/03/2000
• Status: Abandoned Application

• Current Assignee: Gerard Thomas Magee
• Original Assignee: Gerard Thomas Magee
• Inventors: Magee, Gerard Thomas
• Application Number:
  US10/204,690
• Publication Number:
  US 20030040935A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A business information management system for facilitating transactions between a business entity and a second entity, comprising a database (8) containing organisation data for the business entity, the organization data defining a hierarchical arrangement (12) of users (24,26,28,30,32,34) within the business entity; Interface means (6) to a communications system for exchanging data with the second entity (4); an engine (10) in communication with the interface (6) and arranged to exchange data with the second entity (4) regarding a transaction between the business entity and the second entity (4), and to store said data in the database (8), the engine (10) having a plurality of operations that can be performed on the data; The database (8) further containing configuration data defining business rules to control said operations, each user'"'"'s access to data in the database and which of said operations each user may perform on said data.

Claims

1. A business information management system for facilitating transactions between a business entity and a second entity, comprising:

A database containing organisation data for the business entity, the organization data defining a hierarchical arrangement of users within the business entity;

Interface means to a communications system for exchanging data with the second entity;

An engine in communication with the interface and arranged to exchange data with the second entity regarding a transaction between the business entity and the second entity, and to store said data in the database, the engine having a plurality of operations that can be performed on the data;

The database further containing configuration data defining business rules to control said operations, each user'"'"'s access to data in the database and which of said operations each user may perform on said data.

2. The system of claim 1, wherein the operations comprise commercial operations, production operations, and analysis operations.

3. The system of claim 2, wherein the commercial operations include at least one of:

transmitting or receiving request data for products and/or services and/or projects;

transmitting or receiving offer data regarding request data;

transmitting or receiving order data regarding offer data;

transmitting or receiving dispatch data regarding products and/or services and/or projects in relation to order data;

transmitting or receiving delivery data regarding products and/or services and/or projects in relation to order data;

transmitting or receiving invoice data regarding order data; and

transmitting or receiving payment data regarding invoice data.

4. The system of claim 3, wherein the production operations include at least one of:

generating a producation schedule form regarding said request data, offer data or order data;

generating a stock requirement form regarding said request data, offer data or order data;

generating a dispatch requirement form regarding said request data, offer data or order data;

generating a delivery requirement form regarding said request data, offer data or order data.

5. The system of claim 3 or 4, wherein the analysis operations include at least one of:

generating a trends form in relation to said request data, offer data, order data, dispatch data, delivery data, or invoice data.

6. The system of claim 4 or 5, wherein said forms include means for receiving form data entered from a user in said business entity, said engine being arranged to receive said form data, store it in the database and perform operations on said form data in accordance with said configuration data.

7. The system of any one of claims 1 to 6, wherein said configuration data further comprises trigger data, said engine being responsive to the trigger data and to the data to determine whether to perform an operation.

8. The system of any one of claims 1 to 7, wherein the database further contains inventory data defining a plurality of products and/or services and/or projects, said whereby said configuration data defines for each user whether that user can perform an operation to transmit or receive a request, offer, order dispatch, delivery or invoice in relation to said inventory data.

9. The system of claim 8, wherein at least one of said product and/or service and/or project in said inventory data is associated with a predetermined second entity, and whereby said engine is arranged to perform said transmit or receive operations to said predetermined second entity in relation to said product and/or service and/or project.

10. The system of any one of claims 1 to 9, wherein if a user-initiated operation exceeds a user'"'"'s access, said operation is forwarded to another user above said user in said organisation data.

11. The system of any one of claims 1 to 10, wherein the database further contains second entity data defining which second entities said engine will exchange information with.

12. The system of any one of claims 3 to 6, wherein said request data includes:

a category data field representing the type of product or service the request data relates to;

a buyer entity identifier;

at least one description data field for storing data describing the good/service the request data relates to selected from;

a desired manufacturer data field, a desired item model data field, a desired delivery date and time data field, a general description data field;

an offer closing date and time data field; and

a maximum price data field.

13. The system of claim 12, wherein the database further contains category data representing categories of goods and/or services and/or projects the business entity is interested in.

14. The system of claim 13, wherein the engine is arranged to filter said request data according to the category data.

15. The system of any one of claims 1 to 14, wherein said offer data includes price data, an earliest delivery date and time, a request data identifier, an offer bonus description data field, a description data field, and a business entity data identifier.