Universal knowledge information and data storage system

• US 7,698,316 B2
• Filed: 01/09/2004
• Issued: 04/13/2010
• Est. Priority Date: 01/10/2003
• Status: Active Grant

• Current Assignee: Cohesive Knowledge Solutions, Inc.
• Original Assignee: Cohesive Knowledge Solutions, Inc.
• Inventors: Song, Michael R., Burress, Timothy S.
• Primary Examiner(s): Abel-Jalil; Neveen
• Assistant Examiner(s): LIANG, VEI CHUNG
• Application Number:
  US10/541,798
• Publication Number:
  US 20060277205A1
• Time in Patent Office: 2,286 Days
• Field of Search: 709/203, 707/102, 707/103
• US Class Current: 707/608
• CPC Class Codes: G06N 5/02 Knowledge representation; Symbolic representation

Abstract

A system (100) is provided for storing knowledge, information and data (KID). The system includes a plurality of sources of KID (20), at least one receiver of KID (30) from the plurality of sources, a universal knowledge, information and data store (UKIDS 160) and an interface (150) coupling the receiver and the UKIDS. The interface provides a plurality of logical partitions (200) for storing KID within the UKIDS. In one embodiment, a first level of the logical partitions segregates information into personal and professional KID. A plurality of second personal levels under the first personal level (210) segregates KID storage into a teams of people subset (212), an activities and organization subset (214) and an organization and administration subset (216). A plurality of second professional levels under said first professional level (220) segregates KID storage into a clients subset (230), an output subset (250), a teams subset (270) and an administration subset (290).

Claims

1. A system for storing knowledge, information and data (KID), comprising:

a plurality of sources of KID;

a plurality of receivers of KID from said plurality of sources; and

a universal knowledge, information and data store (UKIDS), said UKIDS having a plurality of physical and logical levels and partitions for segregating and storing said KID in a priority-based and standardized scheme within said UKIDS, said priority based and standardized scheme includes a clustering of KID into a plurality of predefined personal and professional storage subsets for transferability between said receivers, extensibility across data store platforms within said UKIDS and scalability in understanding of said KID by each of said receivers, said predefined professional storage subsets cluster KID into said levels and partitions of an enterprise shell, a business unit shell, a division shell, departmental shell, team shell and an individual shell, said system further including rules and tools for configuring said UKIDS and for storing and accessing KID included therein;

said rules define methods for allocating KID within one of said plurality of predefined personal and professional storage subsets, for purging KID from said UKIDS, and for efficiently sharing and distributing KID between said receivers;

said tools include features and functions for presenting news and advertising of interest to said receivers, for identifying targeted storage locations within specific ones of said plurality of predefined personal and professional storage subsets, for backup and archiving KID and for securing KID in said UKIDS; and

a first one of said physical and logical levels and partitions segregates and stores KID into one of said predefined personal storage subsets and said predefined professional storage subsets, said predefined personal storage subsets segregates and stores KID into a second one of said physical and logical levels including partitions of a TEAMS OF PEOPLE storage subset, an ACTIVITIES storage subset and an ORGANIZATION AND ADMINISTRATION storage subset, and predefined professional storage subsets segregates and stores KID into a plurality of second ones of said physical and logical levels, each of said plurality of second ones of said physical and logical levels including partitions of a CLIENTS storage subset, an OUTPUT storage subset, a TEAMS storage subset and an ADMINISTRATION storage subset, and each of said plurality of second ones of said physical and logical levels is one of said enterprise shell, said business unit shell, said division shell, said departmental shell, said team shell and said individual shell for said KID;

wherein said rules for allocating KID include;

eliminating software application default storage locations such that electronic KID is stored within one of said plurality of logical levels and partitions;

implementing one storage system spanning electronic and physical storage locations;

using said priority based and standardized scheme of said plurality of physical and logical levels and partitions to break ties when KID is placeable in more than one of said plurality of predefined personal and professional storage subsets;

using a general storage subset for storing KID that properly references more than one of said plurality of logical levels and partitions;

labeling all KID so as to include at least a date and a title thereof;

employing a numerical indication of priority within a subset label for a selected storage subset when said selected storage subset contains a relatively large number of KID subsets;

maximizing availability of icons representing subsets of said physical and logical levels and partitions to highlight pathways for locating KID;

when options for searching one subset of said plurality of physical and logical levels and partitions exceeds a predetermined number of KID storage locations, re-organizing said subset through sub-categorization;

arranging physical storage locations to reflect said priority based and standardized scheme of said plurality of physical and logical levels and partitions and consistently labeling said physical storage locations;

establishing guidelines for duration of KID storage in electronic and physical UKIDS storage means; and

naming subset KID storage categories to describe content and context of the KID being stored therein.

2. The storage system of claim 1 wherein said TEAMS OF PEOPLE storage subset includes KID pertaining to family, friends, and other groups of person of interest to said receivers.

3. The storage system of claim 1 wherein said ACTIVITIES storage subset includes KID pertaining to vacations, sports, entertainment, spirituality, hobbies, and other activities.

4. The storage system of claim 1 wherein said ORGANIZATION AND ADMINISTRATION storage subset includes KID pertaining to home upkeep, bills and other financial concerns.

5. The storage system of claim 1 wherein said CLIENTS storage subset includes KID pertaining to philosophical groups of internal and external clients, customers, patrons, client projects, markets, key vendors, and sales territories.

6. The storage system of claim 1 wherein said OUTPUT storage subset includes KID pertaining to products, services, value added products and services, and any of the aforementioned offered to clients.

7. The storage system of claim 1 wherein said TEAMS storage subset includes KID pertaining to partnerships, collaborations, and any grouping of individuals that provide output to clients.

8. The storage system of claim 1 wherein said ADMINISTRATION storage subset includes KID pertaining to an operation and coordination of a business, business services, work flow and personnel, and non-core job responsibility.

9. The storage system of claim 1 wherein said plurality of physical and logical levels and partitions span a plurality of data storage platforms including electronic and hard-copy storage means.

10. The storage system of claim 9 wherein said electronic storage means includes computer hard drives, backup and recovery media and off-line storage media.

11. The storage system of claim 1 further including a graphical user interface that allows each of said receivers direct access to electronic stored KID within said logical levels and partitions of said UKIDS and to launch one or more of said tools.

12. The storage system of claim 11, wherein said graphical user interface allows each of said receivers to distribute KID to other of said receivers and to identify a targeted location for storing said KID within one of said plurality of physical and logical levels and partitions.

13. The storage system of claim 12 wherein said targeted storage location is comprised of a path for manual storage of said distributed KID within said physical and logical levels and partitions.

14. The storage system of claim 12 wherein said targeted storage location is comprised of at least a partially automated one of said tools such that, upon request, said distributed KID is automatically stored in a specified one of said physical and logical levels and partitions.

16. The storage system of claim 1, wherein said rules for purging KID include, at a predetermined time period:

separating KID into a first category of KID that is needed, a second category of KID that is not needed but retained on hand, and a third category of KID that is not needed and not retained;

purging said third category; and

placing said second category into a long term storage location.

17. The storage system of claim 1, wherein said rules for purging KID include, when an employee leaves a position, providing a copy of said plurality of personal storage subsets to said employee, moving said plurality of personal storage subsets to a long term storage location, and purging said personal storage subsets from said UKIDS.

18. The storage system of claim 1, wherein said rules for sharing and distributing KID include:

prior to when an employee leaves a position, having said employee provide a successor employee a tour of said plurality of physical and logical levels and partitions within said UKIDS and identify important KID stored therein;

identifying to a recipient receiver a targeted location for storing distributed KID within one of said plurality of physical and logical levels and partitions; and

employing quantity reduction and content quality improvement goals for reducing a volume of distributed KID.

15. A storage management system, comprising:

a universal knowledge information and data store (UKIDS), said UKIDS having a plurality of physical and logical levels and partitions for segregating and storing knowledge, information and data (KID) in a priority-based and standardized scheme within said UKIDS, said priority based and standardized scheme includes a universal clustering of KID into a plurality of predefined personal and professional storage subsets for transferability between receivers of said KID, extensibility across data store platforms within said UKIDS and scalability in understanding of said KID by each of said receivers, said predefined professional storage subsets cluster KID into said levels and partitions of an enterprise shell, a business unit shell, a division shell, departmental shell, team shell and an individual shell, said system further including rules and tools for configuring said UKIDS and for storing and accessing KID included therein;

said rules define methods for allocating KID within one of said plurality of predefined personal and professional storage subsets, for purging KID from said UKIDS, and for efficiently sharing and distributing KID between said receivers;

said tools include features and functions for presenting news and advertising of interest to said receivers, for identifying targeted storage locations within specific ones of said plurality of predefined personal and professional storage subsets, for backup and archiving KID and for securing KID in said UKIDS; and

a first one of said physical and logical levels and partitions segregates and stores KID into one of said predefined personal storage subsets and said predefined professional storage subsets, said predefined personal storage subsets segregates and stores KID into a second one of said physical and logical levels including partitions of a TEAMS OF PEOPLE storage subset, an ACTIVITIES storage subset and an ORGAN IZATION AND ADMINISTRATION storage subset, and predefined professional storage subsets segregates and stores KID into a plurality of second ones of said physical and logical levels, each of said plurality of second ones of said physical and logical levels including partitions of a CLIENTS storage subset, an OUTPUT storage subset, a TEAMS storage subset and an ADMINISTRATION storage subset, and each of said plurality of second ones of said physical and logical levels is one of said enterprise shell, said business unit shell, said division shell, said departmental shell, said team shell and said individual shell for said KID;

wherein said rules for allocating KID include;

eliminating software application default storage locations such that electronic KID is stored within one of said plurality of logical levels and partitions;

implementing one storage system spanning electronic and physical storage locations;

using said priority based and standardized scheme of said plurality of physical and logical levels and partitions to break ties when KID is placeable in more than one of said plurality of predefined personal and professional storage subsets;

using a general storage subset for storing KID that properly references more than one of said plurality of logical levels and partitions;

labeling all KID so as to include at least a date and a title thereof;

employing a numerical indication of priority within a subset label for a selected storage subset when said selected storage subset contains a relatively large number of KID subsets;

maximizing availability of icons representing subsets of said physical and logical levels and partitions to highlight pathways for locating KID;

when options for searching one subset of said plurality of physical and logical levels and partitions exceeds a predetermined number of KID storage locations, re-organizing said subset through sub-categorization;

arranging physical storage locations to reflect said priority based and standardized scheme of said plurality of physical and logical levels and partitions and consistently labeling said physical storage locations;

establishing guidelines for duration of KID storage in electronic and physical UKIDS storage means; and

naming subset KID storage categories to describe content and context of the KID being stored therein.

19. A system for storing knowledge, information and data (KID), comprising:

a plurality of sources of KID;

a plurality of receivers of KID from said plurality of sources; and

a universal knowledge, information and data store (UKIDS), said UKIDS having a plurality of physical and logical levels and partitions for segregating and storing said KID in a priority-based and standardized scheme within said UKIDS, said priority based and standardized scheme includes a clustering of KID into a plurality of predefined personal and professional storage subsets for transferability between said receivers, extensibility across data store platforms within said UKIDS and scalability in understanding of said KID by each of said receivers, said predefined professional storage subsets cluster KID into said levels and partitions of an enterprise shell, a business unit shell, a division shell, departmental shell, team shell and an individual shell, said system further including rules and tools for configuring said UKIDS and for storing and accessing KID included therein;

said rules define methods for allocating KID within one of said plurality of predefined professional storage subsets, for purging KID from said UKIDS, and for efficiently sharing and distributing KID between said receivers;

said tools include features and functions for presenting news and advertising of interest to said receivers, for identifying targeted storage locations within specific ones of said plurality of predefined professional storage subsets, for backup and archiving KID and for securing KID in said UKIDS; and

a first one of said physical and logical levels and partitions segregates and stores KID into said personal storage subset and said plurality of predefined professional storage subsets, said plurality of predefined professional storage subsets segregates and stores KID into a plurality of second ones of said physical and logical levels, each of said plurality of second ones of said physical and logical levels including partitions of a CLIENTS storage subset, an OUTPUT storage subset, a TEAMS storage subset and an ADMINISTRATION storage subset, and each of said plurality of second ones of said physical and logical levels is one of said enterprise shell, said business unit shell, said division shell, said departmental shell, said team shell and said individual shell for said KID;

wherein said rules for allocating KID include;

eliminating software application default storage locations such that electronic KID is stored within one of said plurality of logical levels and partitions;

implementing one storage system spanning electronic and physical storage locations;

using said priority based and standardized scheme of said plurality of physical and logical levels and partitions to break ties when KID is placeable in more than one of said plurality of predefined personal and professional storage subsets;

using a general storage subset for storing KID that properly references more than one of said plurality of logical levels and partitions;

labeling all KID so as to include at least a date and a title thereof;

employing a numerical indication of priority within a subset label for a selected storage subset when said selected storage subset contains a relatively large number of KID subsets;

maximizing availability of icons representing subsets of said physical and logical levels and partitions to highlight pathways for locating KID;

when options for searching one subset of said plurality of physical and logical levels and partitions exceeds a predetermined number of KID storage locations, re-organizing said subset through sub-categorization;

arranging physical storage locations to reflect said priority based and standardized scheme of said plurality of physical and logical levels and partitions and consistently labeling said physical storage locations;

establishing guidelines for duration of KID storage in electronic and physical UKIDS storage means; and

naming subset KID storage categories to describe content and context of the KID being stored therein.