A system includes a processor which has access to a representation of model of activity, which includes workspaces. Each workspace includes domain hierarchies for representing an organizational structure of the collaborating users using the system, and initiatives hierarchies representing process structures for accomplishing goals. An interface permits users to view and modify the workspaces for which the user has access. Each user can have different access permissions in different workspaces. The domain and initiative hierarchies provide two views of the workspace objects without duplicating resources. A resource is a collection of shared elements defined by the users that give users associated with the workspace access to information sources. Users can define knowledge boards for creating reports based on information fields of the resources. The knowledge board is associated with a resource template from which the resource is created.
|
26. A non-transitory computer-readable storage medium comprising instructions for implementing a collaboration network system, wherein a processor executes the instructions to:
designate first tool objects of the tool set and first role objects of the role set based on a first permission list;
designate second tool objects of the tool set and second role objects of the role set based on a second permission list,
wherein the first tool objects include at least one application providing functionality specified for the first workspace portal, the first permission list designating the at least one application as being accessible through the first workspace portal, and the second permission list designating the at least one application as being inaccessible through the second workspace portal, and
wherein the role set includes at least one role object having a level of access to the tool set, the first permission list designating the at least one role object as being available through the first workspace portal, and the second permission list designating the at least one role object as being unavailable through the second workspace portal;
access through the first workspace portal the first tool objects and the first role objects designated by the first permission list; and
access through the second workspace portal the second tool objects and the second role objects designated by the second permission list, wherein the second tool objects and the second role objects accessed through the second workspace portal differ from the first tool objects and the first role objects accessed through the first workspace portal.
23. A collaboration system accessed by client devices through a plurality of workspace portals, the collaboration system comprising at least one hardware memory to store:
system objects, comprising:
administration objects designating individuals with administrative access to a workspace object, and
database objects designating storage locations for the workspace object; and
workspace objects, comprising:
a workspace portal, and
a workspace tool set accessible to client machines through the workspace portal, comprising:
a workspace permission object set defining access level objects that allow individuals to access resource objects in a workspace;
application objects useable by individuals having access to the resource objects in the workspace, wherein an application object comprise a resource creation object, the resource creation object comprising:
resource templates defined through an administration object, the resource templates defining classes of resources, the classes of resources specifying information types associated with the resources belonging to the classes of resources defined by the resource templates, and wherein the resources are created by starting with the resource template, and
resource objects providing information sources, wherein a resource object is accessible simultaneously, without duplicating the resource object, from a first hierarchy and a second hierarchy, the first hierarchy neither containing nor contained in the second hierarchy;
a workspace resource object set defining the resource objects accessible through the workspace; and
a workspace navigation object set defining navigation objects useable by the individuals to navigate the workspace and to access the workspace through the workspace portal.
19. A processor-implemented method for providing access from client devices to a tool set of tool objects and a role set of role objects through a first workspace portal and a second workspace portal in a collaborator network system, the method comprising:
designating, by a processor, first tool objects of the tool set and first role objects of the role set based on a first permission list;
designating, by the processor, second tool objects of the tool set and second role objects of the role set based on a second permission list;
wherein the first tool objects include at least one application providing functionality specified for the first workspace portal, the first permission list designating the at least one application as being accessible through the first workspace portal, and the second permission list designating the at least one application as being inaccessible through the second workspace portal; and
wherein the role set includes at least one role object having a level of access to the tool set, the first permission list designating the at least one role object as being available through the first workspace portal, and the second permission list designating the at least one role object as being unavailable through the second workspace portal;
accessing, by the processor, through the first workspace portal the first tool objects and the first role objects designated by the first permission list; and
accessing, by the processor, through the second workspace portal the second tool objects and the second role objects designated by the second permission list, wherein the second tool objects and the second role objects accessed through the second workspace portal differ from the first tool objects and the first role objects accessed through the first workspace portal.
1. A collaborator network system accessed by client devices through a plurality of workspace portals, the collaborator network system comprising at least one hardware memory to store:
a plurality of workspace objects, each workspace object accessed through a workspace portal;
a tool set that provides a plurality of tool objects for system functionality within the collaborator network system;
a role set defining a plurality of role objects, each role object being defined by a permission set, each permission set specifying a level of access to the tool set and the workspace portals within the collaborator network system, the permission set, comprising:
a first permission list selectively designating first tool objects and first role objects for a first workspace object accessible through a first workspace portal, and
a second permission list selectively designating second tool objects and second role objects for a second workspace object accessible through a second workspace portal;
wherein the first tool objects include at least one application providing functionality specified for the first workspace portal, the first permission list designating the at least one application as being accessible through the first workspace portal, and the second permission list designating the at least one application as being inaccessible through the second workspace portal; and
wherein the role set includes at least one role object having a level of access to the tool set, the first permission list designating the at least one role object as being available through the first workspace portal, and the second permission list designating the at least one role object as being unavailable through the second workspace portal; and
a system server that accesses the first and the second tool objects and the first and the second role objects through the first workspace portal and the second workspace portal according to the first and the second permission lists.
2. The collaborator network system of
3. The collaborator network system of
4. The collaborator network system of
the role set includes a system administrator object with system administration access to the tool set and to the role set within the collaborator network system; and
the workspaces are defined by use of the system administrator object.
5. The collaborator network system of
the role set includes a workspace administrator object;
the tool set includes a workspace tool set; and
the workspace administrator object provides a workspace administrator with complete access to the workspace tool set and the role objects defined by the permission set.
6. The collaborator network system of
the role set includes role objects with limited access to applications of the first workspace object and role objects defined by the first permission list; and
the role objects comprise one or more of manager, user, and viewer role objects, wherein:
a manager role object comprises manager access objects providing full access to objects in the workspace,
a user role object comprises:
a user profile for each of a plurality of individuals assigned to a workspace object;
a user identification (ID) for each of the plurality of individuals;
a workspace object ID;
roles and permissions assigned to each of the plurality of individuals in the workspace object; and a workspace group profile for two or more of the plurality of individuals; and
a viewer role object comprises read access objects limiting object access to viewing only.
7. The collaborator network system of
the first permission list comprises individual permissions and group permissions, the individual and group permissions comprising:
no permission,
read,
read-create,
read-create-update, and
read-create-update-delete; and
access by the individual to an object in a workspace is limited by an individual or group permission designated for the individual in the workspace.
8. The collaborator network system of
9. The collaborator network system of
a user side comprising the plurality of workspaces and workspace portals; and
a system administration side, comprising system administration tool objects of the tool set to:
create workspaces for an individual user role object or a group role object,
assign workspace administration responsibility to a workspace individual, and
assign resource objects to the workspace object.
10. The collaborator network system of
11. The collaborator network system of
global navigation objects;
resource creation objects; and
the role objects.
12. The collaborator network system of
resource templates defined through the system administrator object, the resource templates defining classes of resources, the classes of resources specifying information types associated with the resources belonging to the classes of resources defined by the resource templates, wherein the resource objects are created by starting with the resource template; and
the resource objects providing information sources, wherein a resource object is accessible simultaneously, without duplicating the resource object, from a first hierarchy and a second hierarchy, the first hierarchy neither containing nor contained in the second hierarchy.
13. The collaborator network system of
14. The collaborator network system of
an alerts object that signals individuals when contents of knowledge boards change; and
an immediate update share object that makes changed contents of knowledge boards available to the individuals.
15. The collaborator network system of
a search engine object that receives query terms from user role objects and generates search results including one or more resource object links;
a knowledge board report object that includes resource object links from the search report; and
a knowledge board update object that retrieves updated resource objects based on the resource object links and populates the knowledge board object to generate an updated knowledge board report object.
16. The collaborator network system of
a first workspace storage partition storing individual and group data associated with individuals accessing the collaborator network system through the first workspace portal.
17. The collaborator network system of
shared storage accessible through the first workspace portal and storing individual and
group data associated with individuals accessing the collaborator network system through the first workspace portal.
18. The collaborator network system of
operation objects;
knowledge board objects to locate resources belonging to the class that the resource template defines;
domains;
initiatives; and
information sources.
20. The method of
receiving a user profile through the first workspace portal; and
storing the user profile within a first workspace storage partition.
21. The method of
receiving a user profile through the first workspace portal; and
storing the user profile within a shared storage accessible through the first workspace portal.
22. The method of
receiving a user profile defining a user through the first workspace portal; and
editing the user profile using information provided through the first workspace portal regarding the user.
24. The system of
a first workspace storage partition storing individual and group data associated with individuals accessing the collaboration system through a first workspace portal; and
a shared storage accessible through the first workspace portal and storing individual and
group data associated with individuals accessing the collaboration system through the first workspace portal.
25. The system of
the permission object comprises individual permissions and group permissions, the individual and group permissions comprising one or more of read, create, update and delete;
access by the individual to an object in a workspace is limited by an individual or group permission designated for the individual in the workspace; and
a group permission assigned to the individual as a member of a group overrides an individual permission assigned to the individual.
27. The computer-readable storage medium of
|
|||||||||||||||||||||||||||||||
The present application is a divisional of U.S. patent application Ser. No. 13/168,599, to Ahlgren et al., “System for Supporting Collaborative Activity,” filed Jun. 24, 2011, now pending, which is a divisional of U.S. patent application Ser. No. 11/939,250, to Ahlgren, et al, “System for Supporting Collaborative Activity,” filed Nov. 13, 2007, now U.S. Pat. No. 8,082,201, issued Dec. 20, 2011, which claims priority to U.S. provisional patent application Ser. No. 60/858,241, filed Nov. 10, 2006. These patent applications and patents are hereby incorporated by reference.
The present application is further related to U.S. patent application Ser. No. 09/312,740, “Processing Management Information,” filed May 14, 1999, now U.S. Pat. No. 8,095,413, issued Jan. 10, 2012, which claims priority to U.S. patent application Ser. No. 60/133,152 “Processing Management Information,” filed May 7, 1999; and to U.S. patent application Ser. No. 10/765,424, “System for Performing Collaborative Tasks,” filed Jan. 27, 2004, which is a continuation-in-part of U.S. patent application Ser. No. 09/312,740 and which issued as U.S. Pat. No. 7,698,160 on Apr. 13, 2010; and to U.S. patent application Ser. No. 14/297,058, “Managing Collaborative Activity,” filed Jun. 5, 2014, which is a divisional of U.S. patent application Ser. No. 13/313,658, filed Dec. 7, 2011, now pending, which is a divisional of U.S. patent application Ser. No. 09/312,740. The present application hereby incorporates U.S. application Ser. Nos. 09/312,740; 60,133,152; 10/765,424; 14/297,058; 13/313,658; and U.S. Pat. Nos. 8,095,413 and 7,698,160 by reference for all permissible purposes.
Not applicable.
Not applicable.
1. Field of the Invention
This invention relates to systems for improving communication among people who are collaborating in the performance of a task.
2. Description of Related Art
Computers coupled to networks have made collaborative work easier than ever before. At the most fundamental level, file sharing and email have eliminated the requirement that collaborators be in physical proximity to each other. The change tracking arrangements that are provided by most document processing systems further support collaborative work, as do computer-implemented scheduling and tracking systems. Integrated systems for collaborative work provide features such as file sharing, email, change tracking, scheduling, and tracking in a single package. A problem with these tools and integrated systems for collaborative work is that they are very general. It is up to the user to adapt them to his or her needs. To be sure, a skilled user of a tool such as a spreadsheet can adapt the tool to almost any purpose, but to do this, extensive programming is required. Such programming requires a specialist, and the result of the programming is often opaque to those who are not masters of the tool and of what is being represented. Indeed, a general problem with tools that require extensive programming to adapt them to a user's needs is that the programming is usually done by a specialist who understand the tools or the system, but not the nature of the collaboration, and as is usual in such situations, communication between the programming specialist and the users is usually difficult and sometimes impossible.
Another approach to collaborative work has been systems that are specialized for collaborative work in a particular special area, such as bookkeeping. For example, the Quickbooks small business accounting software provides a model of a small business as seen from the point of view of an accountant that the user of Quickbooks can customize for his or her own purposes. While the model of the small business that Quickbooks provides is very useful for accounting, it has no relevance whatever to other aspects of the business.
Another approach is described in U.S. patent application Ser. No. 10/765,424 ('424 application).
Each goal-project hierarchy 4011 has at its head a project or a goal. A goal may have other goals and projects 4015 as its children. A project 4015 may have other projects as its children, but may not have a goal as a child. Any goal, project, domain, or initiative may have one or more items of information 4017 associated with it, as indicated by arrows 4105. The information may include documents, messages, discussions, reminders, Web links, and alerts. The ability to relate information 4017 directly to any kind of hierarchy entity is particularly useful when the information is global to the entire domain or initiative.
An initiative 4109 is not a member of any domain hierarchy 4010 or goal-project hierarchy 4011, but is rather the root of an initiative hierarchy 4111 which may include sub-initiatives and a single level of goals and/or projects from any of the goal-project hierarchies. A goal or project may belong to any number of initiatives. Information may be related to an initiative in the same way that it may be related to any hierarchy entity.
Access to domains, goals, and projects is by collaborator groups 4003. A given collaborator group 4003(i) may have access to any combination of domains, goals, projects, and initiatives in model 4101. The kinds of access which a collaborator belonging to a particular group has to a particular domain, goal, project, or initiative depend on the group's group type and the permissions which the group has for the particular domain, goal, project, or initiative.
Collaborators with the proper permissions may modify not only the information 4017 associated with a goal, project, domain, or initiative, but may also modify the form of the respective hierarchy.
A limitation of the model 4101 is that it provides only one view of the hierarchies' structure. This limits the usefulness of the model to more complex processes or organizations, where multiple views of the hierarchies would be helpful.
It is thus an object of the present invention to overcome these limitations and to provide an improved system for collaborative work.
The invention provides a system for supporting arbitrary activities involving collaborating users. In one aspect, the system includes a processor which has access to a representation of model of activity, the model including a plurality of workspaces. Each workspace includes a plurality of workspace objects for representing an organizational structure of the collaborating users using the system and representing one or more process structures for accomplishing goals. The system further includes an interface to the system for the users, the interface being provided by the processor and the interface permitting the users to view and modify the workspaces. Each user has access to one or more of the workspaces, and each user can have different access permissions in different workspaces.
The workspace objects include a domain hierarchy representing the organizational structure of the users using the system and an initiatives hierarchy representing the process structures for accomplishing the goals. The domain hierarchy and the initiatives hierarchy provide the users two views of the workspace objects without a need to duplicate the workspace objects in the initiatives hierarchy.
The workspace objects include a plurality of resources associated with the domain hierarchy and the initiatives hierarchy. Each resource is a collection of shared elements defined by the users that give the users associated with the workspace access to information sources. The information sources can include a document local to a user to be uploaded into the system, a text file created by the user using a text editor of the system, links to access information or tools internally or externally to the system, RSS (Really Simple Syndication) feeds, and discussion topics.
In another aspect, the system includes a processor which has access to a representation of model of activity, the model includes a plurality of resources, each resource including a collection of shared elements defined by the user that give the other users access to information sources, and a knowledge board for creating reports based on data fields of the resources. The system further includes an interface to the system for the users, the interface being provided by the processor and the interface permitting a user to view and modify the knowledge board.
In another aspect, a processor which has access to a representation of model of activity, the model includes a plurality of resource templates, each resource template defining data fields to be created for a resource. The system further includes an interface to the system for the collaborators, the interface being provided by the processor and the interface permitting a user to view one or more resource templates and to create the resource from the resource template, the resource including a collection of shared elements defined by the user that give other users access to information sources.
Other objects and advantages will be apparent to those skilled in the arts to which the invention pertains upon perusal of the following Detailed Description and drawing, wherein:
Reference numbers in the drawing have three or more digits: the two right-hand digits are reference numbers in the drawing indicated by the remaining digits. Thus, an item with the reference number 203 first appears as item 203 in
A system for supporting collaborative activity includes a processor and an interface that is provided to collaborators by the processor. The processor has access to a representation of a model of the activity. The form of the model is defined by the collaborators and the representation of the model provides access to information related to the activity. The interface permits a collaborator to perceive and modify the model's form and to perceive and modify the information to which the representation of the model provides access. The model is implemented using workspaces from which the user may access information and perform activities having to do with the collaboration. The workspaces are provided to users as part of a shared online collaboration software platform that connects people, strategies, technology, and resources in a rapidly developed and deployable on-line workspace.
a. Overview of the System
Collaborating users can organize domains 117 and initiatives 127 into hierarchies 115 and 125. A user can associate a resource 121 with a domain, a sub-domain, or another resource associated with a domain. Resources can be presented as many times as required within the initiative, and therefore could be used in multiple scenarios, without the need to be duplicated. The domain and initiatives hierarchies thus provide users with ability to view objects of information (such as resources and/or knowledge boards (described below)) within an organization structure or an operational structure without need to duplicate the objects.
Domains, initiatives, and resources can be renamed by administrators to reflect the terminology used by their organization. For example, a domain can be renamed as an organization or an agency; an initiative can be renamed as an operation or a process; and a resource can be renamed as a record.
Resources may be organized into resource hierarchies, as shown by arrow 122, and the resource hierarchies belong to domains 117, which themselves may be hierarchically organized (115). A resource may have a domain as a parent, but a domain cannot have a resource as a parent. A given resource 121 may belong to only one domain 117. Generally, though not necessarily, the domain hierarchy reflects the organization chart of the collaboration. For example, if the collaboration is a business, there may be domains for manufacturing, engineering, sales, accounting, human resources, and corporate management, with sub-domains within the domains, for example, a sub-domain for hourly employees in human resources.
In addition to being related to a domain, a resource may also be related to an initiative 127. Initiatives may form hierarchies 125. The navigation GUI for system 101 permits the user to navigate to a resource either by means of the domain hierarchy or by means of the initiative hierarchy. Generally, though not necessarily, initiatives are created to deal with specific problems where the resources required to deal with the problem cut across domain lines. For example, if the domains are set up as described in the foregoing example and the business has a quality control problem, an initiative may be set up to deal with the quality control problem and may include resources from the manufacturing, engineering, and corporate management domains. Domains and initiatives thus give participants different perspectives on the resources needed for the collaboration.
Resource templates 124 are global objects that define classes of resources, as defined by a system administrator. They specify what types of information are associated with resources belong to the class defined by the resource template by defining the number and types of data fields associated with them. When a user creates a resource, the user begins with a resource template. The fields of the resource template are filled in by the user when the resource is created or modified, according to the domain or initiative the resource relates to.
In addition to viewing resources within a domain or initiative, the resource template can be used to locate resources belonging to the class that the template defines. This location of resources is defined by users in knowledge boards or dashboards 129. When a user creates a knowledge board, the user uses the resource template to associate resources belonging to the resource template's class with the knowledge board and to select what information from resources of the class will be displayed in the knowledge board. The relationship between the resource template and the resources created from the template are maintained in the system for the knowledge boards. A knowledge board is defined for a workspace but does not belong to any of the hierarchies. The navigation GUI lists the workspace's knowledge boards along with both the initiative and domain hierarchies. The users select the columns (data fields) in the resource template to display and filter by parameters, such as specific text, dates, etc. These data fields are used to locate resources to which the template belongs and are then displayed in the knowledge board report in a table form.
The domains, initiatives, and resources are organized into a plurality of workspaces, each of which provides a managed environment. The system gives each collaborator/user access to one or more workspaces where a user may have different roles in different workspaces. The workspaces may be configured by non-technical people. The components of a workspace include domains 117, resources 121, initiatives 127, information sources 123, and dashboards or knowledge boards 129. These are termed in the following as the workspace's objects. Preferably, the system is implemented in a client-server architecture. The system server stores the workspace and its objects, as well as global objects, such as users and resource templates. The client comprises a processor which ahs access to the system elements. Users access the system's elements through a GUI at the client. Users may have different kinds of access to the objects in a workspace. The workspace includes a navigation GUI as part of the online collaborative software platform that presents the content of its objects. A system administrator can create a unique workspace for a group of people, assign local administration responsibilities, and assign global resources from a global pool of resources. Users can be part of multiple workspaces and carry different access permissions. For example, a specific user can be a user only in one workspace and have administrator rights in another. User access permissions are described further below.
In an exemplary embodiment, information sources that can be related with a resource include documents, text files, links, RSS (Really Simple Syndication) feeds, and discussions. For documents already created and stored locally, a user can select from his workstation or from any shared drive a document to add to a resource. The document is then physically copied and loaded into the system server and will reside on its file directory system. All documents loaded on the system are maintained for the life of the system. This enables users to upload and store documents relevant to the resource. To modify the document after its association with the resource, a user “checks out” the document and downloads it from the server to the client for editing. When the editing's done, the user uploads the modified document from the client to the server.
The system also provides a simple text editor at a client of the system with which a user can create and upload a text file of the .txt type to the system server. This enables users to create a free format text file that can be created, uploaded, and opened by users without the need for a word processing application.
The system provides users the ability to relate links to the resource. Links provide quick access to information or tools. The link can be an external link or an internal link. External links provide access to an outside source, utilizing an address like an URL, or a link to a network source, utilizing a link to a shared device. This enables users to link to a shared document or other file types without the need to upload the files to the system. Other users on the network could access the same file without being part of the system. Internal links provide access to other resources within the system. When users want to use a resource that resides in a different structure of the system, they can provide a link that will launch that resource whenever it is called. This provides the flexibility to reuse resources without the need to create special initiatives for aggregation.
The system provides users the ability to relate an RSS feed to the resource RSS feeds are web feeds in XML format that enable users to receive updated news or information articles through a special reader screen. The ability to provide these connections allow users to create a link that provides new, updated article every time the link is selected and articles are presented.
The system provides users the ability to relate discussions to the resource. Discussions are on-line, asynchronous, threaded chat boards that provide users a place to exchange questions, opinions, and remarks in relation to the resource topic. Users can initiate a discussion in-context to the resource's objective and either receives answers to the discussed topic or reply to a discussion topic started by another user.
Actual access to a given object may be limited by the given user's role in the workspace. The workspace roles in an exemplary embodiment are: viewer; user; manager; and administrator. For example, a user who has a viewer role may read but not create, update, or delete objects in the workspace. Consequently, such a user will see only those objects to which the user has some kind of access by virtue either of the user's individual permissions or by virtue of the group permissions of a group to which the user belongs. Because the user has the viewer role, the user will be able to do nothing with the objects to which he or she has access but read them.
Returning to
A workspace table 113 has an entry for each workspace. Associated with the entry for the workspace are the groups that have access to the workspace, the roles these groups have, the resource templates used in the workspace (table 111), and the domains, initiatives, resources, and knowledge boards belonging to the workspace (table 109).
The system provides an internal messaging center to allow quick communication between users or whole groups of users. The message center does not rely on an email server so it can be used even when access to other systems in limited. The message center displays alerts generated by the system 101 and messages to specific users. Users can proactively select important resources within the system and let the system alert them whenever a new resource is added, changed, document are uploaded, links created, and others. This allows users to be selective as for what is important to them to be alerted of and reduce the need for users to send email messages alerting users of updates or changes to information. An email option is available for users who wish to receive the messages and/or the alerts on their email system as well. In this way, users who are away from the system can still be alerted to important information.
The system allows administrators to perform global setup of the navigation GUI. This includes the GUI for the application and the definitions of companies for which the workspaces are created. The system administrator can customize the application's logo, licensing keys, and application level administrative roles and names. The system administrator can define the companies that are sharing the GUI, including names and information of the companies, divisions, and departments.
B. Tables Implementing System
Descriptions of the tables shown in
T_ADMIN_ROLE (301): The T_ADMIN_ROLE table 301 holds the application level administrator role identifiers and names. There is an entry for each administrator. There is a code that is used to easily identify the role when adding it to a user. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
name of administrative role
CODE
varchar2(132)
code for administrative role
DESCRIPTION
varchar2(2000)
description for administrative role
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
T_APPLICATION_LICENSE (302): The T_APPLICATION_LICENSE table 302 holds the license key that enables certain features in the system. There is an entry for each license key. The fields in the table's entries are as follows:
Name
Type
Description
LICENSE_ID
varchar2(32)
license identifier
LICENSE_KEY
varchar2(400)
license key
PASS_WORD
varchar2(32)
license password
OBJ_VERSION
integer
version number
T_APPLICATION_LOGO (303): The T_APPLICATION_LOGO table 303 holds the default logo for the application. It can also store another row that contains an administrative uploaded logo. The LOGO_DATE row holds the binary data for the image file itself. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
LOGO_DATA
long raw
data for logo image file
MIMETYPE
varchar2(255)
mime type
OBJ_VERSION
integer
version number
T_DISCUSSION_TOPIC (307): The entries in the T_DISCUSSION_TOPIC table 307 relate discussion topics to a resource. There is an entry for each discussion topic. Each entry references the resource's record in the T_OBJ_RESOURCE table 329. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
discussion topic name
COMMENTS
varchar2(4000)
comments
RESOURCE_ID
varchar2(32)
record identifier from
T_OBJ_RESOURCE
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
CREATED_BY
varchar2(32)
user creating record from
T_USER_PROFILE
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_DISCUSSION_REPLY (308): The entries in the T_DISCUSSION_REPLY table 308 relate discussion replies to a discussion topic. There is one entry for each reply. Each entry references the discussion topic's record in the T_DISCUSSION_TOPIC table 307 and the parent message. The parent can be another reply in the same table. Replies can be children of other replies in order to maintain a threaded discussion. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
TOPIC_ID
varchar2(32)
record ID from
T_DISCUSSION_TOPIC
PARENT_ID
varchar2(32)
parent topic
NAME
varchar2(128)
topic name
COMMENTS
varchar2(4000)
comments
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
CREATED_BY
varchar2(32)
user creating record from
T_USER_PROFILE
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_MANAGER_PROPERTY (309): The entries in the T_MANAGER_PROPERTY table 309 stores custom property values for various system managers. There is an entry for each property value. Each manager is configured with its own default values. When a system administrator updates those values, they are stored in this table. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
MANAGER_CLASS
varchar2(255)
manager class
NAME
varchar2(128)
property name
VALUE
varchar2(2000)
property value
CREATED_DATE
date
date created
UPDATED_DATE
date
date updated
OBJ_VERSION
integer
version number
T_MD_COMPANY (310): The T_MD_COMPANY table 310 has an entry for each entity, such as a company, that a user of the system may belong to. Entries for users in the system refer to this table to indicate the companies the users belong to. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
company name
DESCRIPTION
varchar2(2000)
company description
ADDRESS1
varchar2(64)
company address
STREET
varchar2(64)
street
CITY
varchar2(64)
city
STATE
varchar2(128)
state
COUNTRY_ID
varchar2(128)
country code
POSTAL_CODE
varchar2(16)
postal code
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
archived by
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
locked by
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_MD_DIVISION (311): The T_MD_DIVISION table 311 has an entry for each division under a company. Entries for users in the system refer to this table to indicate the division the users belong to. Each entry references a company's record in the T_MD_COMPANY table 310. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
division name
COMPANY_ID
varchar2(32)
company ID from
T_MD_COMPANY
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user arching record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_MD_DEPARTMENT (312): The T_MD_DEPARTMENT table 312 has an entry for each department under a division. Entries for users in the system refer to this table to indicate the department the users belong to. Each entry references a division's record in the T_MD_DIVISION table 311. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
department name
DIVISION_ID
varchar2(32)
division ID from
T_MD_DIVISION
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_MD_COUNTRY (313): The T_MD_COUNTRY table 313 holds the names for the countries. There is an entry for each country. These are used for address fields in user profiles and company profiles. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(3)
record identifier
NAME
varchar2(128)
country name
T_MESSAGE (314): The T_MESSAGE table 314 holds messages sent by users of the system. There is an entry for each message. Each entry references the record of a workspace in which the message was sent from the T_WORKSPACE table 346 and the record of the message creator from the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
SUBJECT
varchar2(128)
message subject
BODY
varchar2(4000)
message body
WORKSPACE_ID
varchar2(32)
workspace ID from
T_WORKSPACE
ARCHIVED_DATE
date
date archived
CREATED_DATE
date
date created
CREATED_BY
varchar2(32)
user creating message
OBJ_VERSION
integer
version number
T_MESSAGE_USER (315): The entries in the T_MESSAGE_USER table 315 relate messages to the user to which they were addressed. There is an entry for each user message recipient for each message. Each entry references the message's record in the T_MESSAGE table 314 and the user's record in the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
MESSAGE_ID
varchar2(32)
message ID
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
OBJ_VERSION
integer
version number
T_MESSAGE_GROUP (316): The entries in the T_MESSAGE_GROUP table 316 relates message to the groups to which the message was addressed. There is an entry for each group message recipient for each message. Each entry references the message's record in the T-MESSAGE table 314 and the group's record from the T_WORKSPACE_GROUP table 349. The fields in the table's entries are as follows:
Name
Type
Description
MESSAGE_ID
varchar2(32)
message ID
GROUP_ID
varchar2(32)
group ID from
T_WORKSPACE_GROUP
OBJ_VERSION
integer
version number
T_MESSAGE_RECIPIENT (317): The T_MESSAGE_RECIPIENT table 317 relates messages to users the message was sent to. It breaks out users from the groups that were addressed. There is an entry for each user regardless if the user was selected from the user or group side. There is an entry for each user message recipient for each message. Each entry references the message's record in the T_MESSAGE table 314 and the user's record in THE T_USER_PROFILE table 341. When a user reads the message, it is marked here. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
MESSAGE_ID
varchar2(32)
message ID from T_MESSAGE
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
ARCHIVED_DATE
DATE
date archived
READ_DATE
DATE
date read
OBJ_VERSION
integer
version number
T_OBJ_DATA (318): The T_OBJ_DATA table 318 holds the details of the data object. It's the superclass for all other data objects (Domains, Initiatives, Dashboards and Resources). There is an entry for each data object. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
name of object
DESCRIPTION
varchar2(2000)
description of object
WORKSPACE_ID
varchar2(32)
workspace ID from
T_WORKSPACE
PARENT_ID
varchar2(32)
ID of parent object
in this table
OWNER_ID
varchar2(32)
owner ID from
T_USER_PROFILE
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
CREATED_BY
varchar2(32)
user creating record
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_OBJ_DATA_ALERT_USER (319): The entries in the T_OBJ_DATA_ALERT_USER table 319 relate alerts to users and data objects. There is an entry for each user and each data object. Each entry references the object's record in the T_OBJ_DATA table 318 and the user's record in the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
OBJECT_ID
varchar2(32)
object ID from T_OBJ_DATA
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
OBJ_VERSION
integer
version number
T_OBJ_DATA_PERM_GROUP (320): The entries in the T_OBJ_DATA_PERM_GROUP table 320 relate permissions for groups to data objects. There is an entry for each permission for a group for each data object. Each entry references the object's record in the T_OBJ_DATA table 318 and the group's record in the T_WORKSPACE_GROUP table 349. Possible permission values are:
The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
GROUP_ID
varchar2(32)
group ID from
T_WORKSPACE_GROUP
OBJECT_ID
varchar2(32)
object ID from T_OBJ_DATA
PERMISSION
number(1)
permission code
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_OBJ_DATA_PERM_USER (321): The T_OBJ_DATA_PERM_USER table 321 relates permissions for a user to data objects. There is an entry for each permission for a user for each data object. Each entry references the object's record in the T_OBJ_DATA table 318 and the user's record in the T_USER_PROFILE table 341. Possible permission values are:
The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
OBJECT_ID
varchar2(32)
object ID from T_OBJ_DATA
PERMISSION
number(1)
permission code
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_OBJ_DASHBOARD (322): The T_OBJ_DASHBOARD table 322 holds the details of a knowledge board. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
T_OBJ_DASHBOARD_RES_TMPLT (323): The entries in the T_OBJ_DASHBOARD_RES_TMPLT table 323 relates resource templates with a particular knowledge board. There is an entry for each resource template/knowledge board association. Each entry references a knowledge board's record in the T_OBJ_DASHBOARD_TABLE 322 and a resource's record in the T_OBJ_RESOURCE table 329. The fields in the table's entries are as follows.
Name
Type
Description
ID
varchar2(32)
record identifier
DASHBOARD_ID
varchar2(32)
knowledge board ID from
T_OBJ_DASHBOARD
RES_TMPLT_ID
varchar2(32)
resource ID from
T_OBJ_RESOURCE
SEQUENCE_NUM
number(4,0)
display sequence number
OBJ_VERSION
integer
version number
T_OBJ_DASHBOARD_FIELD_DEFAULT (324): The T_OBJ_DASHBOARD_FIELD_DEFAULT table 324 holds the list of default fields that should be shown on a knowledge board for a particular resource template and any filter data. There is an entry for each field. Each entry references a knowledge board's record in the T_OBJ_DASHBOARD_RES_TMPLT table 323. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
DASHBOARD_
varchar2(32)
knowledge board ID with
RES_TMPLT_ID
resource from T_OBJ_
DASHBOARD_RES_TMPLT
FIELD_NAME
varchar2(1000)
field name
FILTER_VALUE
varchar2(4000)
filter value
SEQUENCE_NUM
number(4,0)
display sequence number
OBJ_VERSION
integer
version number
T_OBJ_DASHBOARD_FIELD_TMPLT (325): The T_OBJ_DASHBOARD_FIELD_TMPLT table 325 holds the list of dynamic fields that should be shown on a knowledge board for a particular resource template and any filter data. There is an entry for each field. Each entry references a knowledge board's record in the T_OBJ_DASHBOARD_RES_TMPLT table 325 and a field's record in the T_RES_TMPLT_FIELD table 337. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
DASHBOARD_RESTMPLT_ID
varchar2(32)
knowledge board ID with resource
from T_OBJ_DASHBOARD_RES_TMPLT
FIELD_ID
varchar2(32)
field ID from T_RES_TMPLT_FIELD
FILTER_VALUE
varchar2(4000)
filter value
SEQUENCE_NUM
number(4,0)
display sequence number
OBJ_VERSION
integer
version number
T_OBJ_DOMAIN (326): The T_OBJ_DOMAIN table 326 holds the details of a domain. There is an entry for each domain. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
T_OBJ_INITIATIVE (327): The T_OBJ_INITIATIVE table 327 holds the details of an initiative. There is an entry for each initiative. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
START_DATE
date
start date
END_DATE
date
end date
T_OBJ_INITIATIVE_DATA_OBJECT (328): The entries in the T_OBJ_INITIATIVE_DATA_OBJECT table 328 relate data objects to initiatives. There is an entry for each initiative/data object association. Each entry references the initiative's record in the T_OBJ_INITIATIVE table 327 and the data object's record in the T_OBJ_DATA table 318. The initiative is related to a workspace through the Workspace_ID in the object's record. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
INITIATIVE_ID
varchar2(32)
initiative ID from
T_OBJ_INITIATIVE
DATA_OBJECT_ID
varchar2(32)
data object ID from
T_OBJ_DATA
SEQUENCE_NUM
number(4,0)
display sequence number
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_OBJ_RESOURCE (329): The T_OBJ_RESOURCE table 329 holds the details of a resource. There is an entry for each resource. Each entry references the resource template's record in the T_RES_TMPLT 335 from which the resource was created. This association is used in knowledge boards to find resources belonging to the resource template for the purpose of generating a report, as described above. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
RESOURCE_TMPLT_ID
varchar2(32)
resource template
ID from
T_RES_TMPL
T_OBJ_RESOURCE_INFORMATION (330): The entries in the T_OBJ_RESOURCE_INFORMATION table 330 relate information (documents, links & RSS feeds) to resources There is an entry for each piece of information. Each entry references the resource's record in the T_OBJ_RESOURCE table 329. The fields in the table's entries are as follows.
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
information name
DESCRIPTION
varchar2(2000)
information
description
RESOURCE_ID
varchar2(32)
resource ID from
T_OBJ_RESOURCE
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_OBJ_RESOURCE_DOCUMENT (331): The entries in the T_OBJ_RESOURCE_DOCUMENT table 331 relate documents to the information table. It subclasses the T_RESOURCE_INFORMATION table 330. There is an entry for each document. Each entry references an information's record in the T_OBJ_RESOURCE_INFORMATION table 330. The document is related to a resource through the Resource_ID in the information's record. The fields in the table's entries are as follows:
Name
Type
Description
INFORMATION_ID
varchar2(32)
information ID from
T_OBJ_RESOURCE_INFORMATION
DOCUMENT_ID
varchar2(32)
document ID
CHECKSUM
varchar2(32)
checksum value
FILE_NAME
varchar2(255)
file name
VERSION
varchar2(4)
version number
T_OBJ_RESOURCE_LINK (332): The entries in the T_OBJ_RESOURCE_LINK 332 table relate links to information. It subclasses the T_RESOURCE_INFORMATION table 330. There is an entry for each link. Each entry references an information's recording the T_OBJ_RESOURCE_INFORMATION table 330. The link is related to a resource through the Resource_ID in the information's record. The fields in the table's entries are as follows:
Name
Type
Description
INFORMATION_ID
varchar2(32)
information ID from
T_OBJ_RESOURCE_INFORMATION
URL
varchar2(512)
URL for link
INTERNAL_FLAG
char(1)
set if internal link
T_OBJ_RESOURCE_RSS (333): The entries in the T_OBJ_RESOURCE_RSS table 333 relate RSS feeds to information. It subclasses the T_RESOURCE_INFORMATION table 330. There is an entry for each RSS feed. Each entry references an information's record in the T_OBJ_RESOURCE_INFORMATION table 330. The RSS feed is related to a resource through the Resource_ID in the information's record. The fields in the table's entries are as follows:
Name
Type
Description
INFORMATION_ID
varchar2(32)
information ID from
T_OBJ_RESOURCE_INFORMATION
URL
varchar2(512)
URL for RSS feed
T_OBJ_RESOURCE_VALUE (334): The T_OBJ_RESOURCE_VALUE table 334 holds values for each field of each resource, as set by a user. There is an entry for each field of each resource. Each entry references a field's record in the T_RES_TMPLT_FIELD table 337 and a resource's record in the T_OBJ_RESOURCE table 329. The field ID's come from the resource template associated with this resource. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
VALUE
varchar2(4000)
field value
FIELD_ID
varchar2(32)
field ID from
T_RES_TMPLT_FIELD
RESOURCE_ID
varchar2(32)
resource ID from
T_OBJ_RESOURCE
OBJ_VERSION
varchar2
version number
T_RES_TMPLT (335): The T_RES_TMPLT table 335 holds the details of the resource templates. There is an entry for each resource template. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
template name
DESCRIPTION
varchar2(2000)
template description
LAYOUT
varchar2(16)
template display layout
VERSION
number(3)
version number
NEXT_VERSION_ID
varchar2(32)
next version record ID
in this table
MASTER_ID
varchar2(32)
master template record
ID in this table
PUBLISHED_DATE
date
date published
DISCUSSIONS_FLAG
char(1)
set if discussions associated
INFORMATION_FLAG
char(1)
set if information associated
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
CREATED_BY
varchar2(32)
user creating record
UPDATED_DATE
date
date updated
OBJ_VERSION
integer
version number
T_RES_TMPLT_FIELD_TYPE (336): The T_RES_TMPLT_FIELD_TYPE table 336 holds a number of different types a data field in a resource template can exist as. There is an entry for each data field type. This is used when producing a visual representation of the field. Each field type can be associated with a category. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
field name
DESCRIPTION
varchar2(2000)
field description
HTML_CLASS
varchar2(255)
HTML class
MAX_DEFAULT_OPTIONS
number(4,0)
default maximum
number of options
CATEGORY
varchar2(16)
category of field type
T_RES_TMPLT_FIELD (337): The T_RES_TMPLT_FIELD table 337 holds both global data fields that apply to multiple object types and resource template specific data fields. The difference is determined by the RES_TMPLT_ID field. If this field is null, the field is global. Global fields are used when creating a new resource template. There is an entry for each data field. The Each entry references the resource template's record in the T_RES_TMPLT table 335, and the field type's record in the T_RES_TMPLT_FIELD_TYPE table 336. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
name of data field
DESCRIPTION
varchar2(2000)
description of data field
RES_TMPLT_ID
varchar2(32)
resource template ID from
T_RES_TMPLT
FIELD_TYPE_ID
varchar2(32)
field type ID from
T_RES_TMPLT_FIELD_TYPE
MAX_LENGTH
number(10,0)
maximum text length
REQUIRED_FLAG
char(1)
set if value required for field
SEQUENCE_NUM
number(4,0)
display sequence number
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_RES_TMPLT_FIELD_OPTION (338): The T_RES_TMPLT_FIELD_OPTION table 338 holds options values for the various data fields in the resource templates. There is an entry for each option. Each entry references the field's record in the T_RES_TMPLT_FIELD table 337. For instance, a select list might contain 15 different predefined options. These can be setup for both global fields and resource template specific fields. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
name of data field
FIELD_ID
varchar2(32)
field ID from
T_RES_TMPLT_FIELD
SEQUENCE_NUM
number(4,0)
display sequence number
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date updated
OBJ_VERSION
integer
version number
T_RES_TMPLT_CATEGORY (339): The T_RES_TMPLT_CATEGORY table 339 holds the details of the resource template categories. There is an entry for each category. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
category name
DESCRIPTION
varchar2
category description
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
CREATED_BY
varchar2(32)
user creating record
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_RES_TMPLT_CATEGORY_MAP (340): The entries in the T_RES_TMPLT_CATEGORY_MAP table 340 relate categories to resource templates. There is an entry for each template/category association. Each entry references the resource template's record in the T_RES_TMPLT table 335 and the category's record in the T_RES_TMPLT_CATEGORY table 339. The fields in the table's entries are as follows:
Name
Type
Description
RES_TMPLT_ID
varchar2(32)
resource template ID from
T_RES_TMPLT
CATEGORY_ID
varchar2(32)
category ID from
T_RES_TMPLT_CATEGORY
T_USER_PROFILE (341): The T_USER_PROFILE table 341 holds the information of users in the system and relates the user to a company, division, and department. There is an entry for each user. Each entry references a company's record in the T_MD_COMPANY table 310, a division's record in the T_MD_DIVISION table 311, and a department's record in the T_MD_DEPARTMENT table 312. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
TITLE
varchar2(32)
user job title
FIRST_NAME
varchar2(32)
first name
MIDDLE_NAME
varchar2(32)
middle name
LAST_NAME
varchar2(32)
last name
SUFFIX
varchar2(32)
name suffix
EMAIL
varchar2(255)
email address
ADDRESS1
varchar2(64)
address
STREET
varchar2(64)
street
CITY
varchar2(64)
city
COUNTY
varchar2(64)
county
STATE
varchar2(128)
state
COUNTRY
varchar2(128)
country
POSTAL_CODE
varchar2(16)
postal code
PHONE
varchar2(24)
phone number
MOBILE
varchar2(24)
mobile number
PAGER
varchar2(24)
page number
FIRST_LOGIN
char(1)
whether logged in for first time
LICENSE_AGREEMENT
date
date accept license agreement
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_USER_PROFILE_WORK (354): The T_USER_PROFILE_WORK table holds the information of users in the system. There is an entry for each user, and each entry references the user's record in the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
USER_ID
varchar2(32)
user ID from
T_USR_PROFILE
JOB_TITLE
varchar2(64)
user job title
JOB_DESCRIPTION
varchar2(4000)
job description
SPECIALTIES
varchar2(4000)
user specialties
CERTIFICATIONS
varchar2(4000)
user certifications
WORK_ID
varchar2(128)
user work ID
BADGE_NUMBER
varchar2(128)
user badge number
ADDRESS1
varchar2(64)
address
STREET
varchar2(64)
street
CITY
varchar2(64)
city
COUNTY
varchar2(64)
county
STATE
varchar2(128)
state
COUNTRY
varchar2(128)
country
POSTAL_CODE
varchar2(16)
postal code
COMPANY_ID
varchar2(32)
company ID from
T_MD_COMPANY
DIVISION_ID
varchar2(32)
division ID from
T_MD_DIVISION
DEPARTMENT_ID
varchar2(32)
department ID from
T_MD_DEPARTMENT
PHONE
varchar2(24)
phone number
MOBILE
varchar2(24)
mobile number
PAGER
varchar2(24)
page number
OFFICE_BUILDING
varchar2(64)
office building
OFFICE_FLOOR
varchar2(12)
office floor
OFFICE_ROOM
varchar2(12)
office room
OFFICE_PHONE
varchar2(24)
office phone number
OBJ_VERSION
integer
version number
T_USER_LOGIN (342): The entries in the T_USER_LOGIN table 342 relate login information to users in the system, if authenticating users through the application. There is one entry for each user. Each entry references the user's record in the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
PASS_WORD
varchar2(64)
password
PASS_WORD_DATE
date
date password set
AUTO_LOCKED_DATE
date
date auto locked set
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CONNECTED_DATE
date
date connected
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_USER_LOGIN_HISTORY (343): The entries in the T_USER_LOGIN_HISTORY table 343 relate the login/logout dates/times to individual users. There is an entry for each login and each logout. Each entry references a user's record in the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
HISTORY_ID
varchar2(32)
history ID
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
LOGIN_DATE
date
date of login
LOGOUT_DATE
date
date of logout
OBJ_VERSION
integer
version number
T_USER_PREFERENCES (344): The entries in the T_USER_PREFERENCES table 344 relate preferences to individual users. There is an entry for each user. Each entry references a user's record in the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
USER_ID
varchar2(32)
user ID from
T_USER_PROFILE
DEFAULT_WORKSPACE_ID
varchar2(32)
default workspace
DEFAULT_NAVIGATOR
varchar2(16)
default navigator view
DEFAULT_LANGUAGE
varchar2(2)
default language
EMAIL_ALERTS
char(1)
set to receive email alerts
EMAIL_MESSAGES
char(1)
set to receive
email message
OBJ_VERSION
integer
version number
T_USER_ADMIN_ROLE (345): The entries in the T_USER_ADMIN_ROLE table 345 relate application level admin role assignments to users. Users can have multiple admin roles. There is an entry for each role assignment. Each entry references the role's record in the T_ADMIN_ROLE table 301 and the user's record in the T_USER_PROFILE table 341. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
ROLE_ID
varchar2(32)
role ID from T_ADMIN_ROLE
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date updated
OBJ_VERSION
integer
version number
T_WORKSPACE (346): The T_WORKSPACE table 346 holds information about workspaces. There is an entry for each workspace. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
workspace name
DESCRIPTION
varchar2(2000)
workspace description
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_WORKSPACE_ROLE (347): The T_WORKSPACE_ROLE table 347 holds the four workspace roles available: Viewer, User, Manager, and Administrator. There is an entry for each workspace role The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
role name
CODE
varchar2(32)
role code
DESCRIPTION
varchar2(2000)
role description
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_WORKSPACE_MEMBER (348): The entries in the T_WORKSPACE_MEMBER table 348 relate users to a workspace and assign their role within the workspace. Users can have different roles in different workspaces. There is an entry for each user/workspace relationship. Each entry references the user's record in the T_USER_PROFILE table 341, the workspace's record in the t-WORKSPACE table 346, and the role's record in the T_WORKSPACE_ROLE table 347. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
USER_ID
varchar2(32)
user ID from T_USER_PROFILE
WORKSPACE_ID
varchar2(32)
workspace ID from T_WORKSPACE
ROLE_ID
varchar2(32)
role ID from T_WORKSPACE_ROLE
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_WORKSPACE_GROUP (349): The entries in the T_WORKSPACE_GROUP table 349 relate groups to a workspace. Groups are just a way of grouping a number of users together for easy reference. There is an entry for each group/workspace relationship. Each entry references a workspace's record in the T_WORKSPACE table 346. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
group name
DESCRIPTION
varchar2(2000)
group description
WORKSPACE_ID
varchar2(32)
workspace ID from
T_WORKSPACE
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date updated
OBJ_VERSION
integer
version number
T_WORKSPACE_GROUP_MEMBER (350): The entries in the T_WORKSPACE_GROUP_MEMBER table 350 relate users to workspace groups. Users can belong to any number of groups. There is an entry for each user/workspace relationship. Each entry references the group's record in the T_WORKSPACE_GROUP table 349 and a member's record in the T_WORKSPACE_MEMBER table 348. The fields in the table's entries are as follows:
Name
Type
Description
GROUP_ID
varchar2(32)
group ID from
T_WORKSPACE_GROUP
MEMBER_ID
varchar2(32)
member ID from
T_WORKSPACE_MEMBER
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_WORKSPACE_QUICK_LINK (351): The entries in the T_WORKSPACE_QUICK_LINK table 351 relate links to workspaces. They can be used to quickly access information for the entire workgroup. There is an entry for each link/workspace relationship. Each entry references the workspace's record in the T_WORKSPACE table 346. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
NAME
varchar2(128)
link name
DESCRIPTION
varchar2(2000)
link description
WORKSPACE_ID
varchar2(32)
workspace ID from
T_WORKSPACE
URL
varchar2(2000)
URL for link
TARGET
varchar2(32)
target of link
SEQUENCE_NUM
number(4,0)
display sequence number
ARCHIVED_DATE
date
date archived
ARCHIVED_BY
varchar2(32)
user archiving record
LOCKED_DATE
date
date locked
LOCKED_BY
varchar2(32)
user locking record
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_WORKSPACE_RES_TMPLT (352): The entries in the T_WORKSPACE_RES_TMPLT table 352 relate resources templates to workspaces. There is an entry for each workspace/template relationship. Each entry references the workspace's record in the T_WORKSPACE table 346, and the resource template's record in the T_RES_TMPLT table 335. The fields in the table's entries are as follows:
Name
Type
Description
WORKSPACE_ID
varchar2(32)
workspace ID from T_WORKSPACE
RES_TMPLT_ID
varchar2(32)
resource template ID from
T_RES_TMPLT
CREATED_DATE
date
date created
UPDATED_DATE
date
date last updated
OBJ_VERSION
integer
version number
T_WORKSPACE_PREFERENCE (353): The T_WORKSPACE_PREFERENCE table 353 has a many-to-one relationship with T_WORKSPACE 345 and holds an array of preferences for each workspace. There is an entry for each workspace preference. Each entry references the workspace's record in the T_WORKSPACE table 346. The fields in the table's entries are as follows:
Name
Type
Description
ID
varchar2(32)
record identifier
WORKSPACE_ID
varchar2(32)
workspace ID from
T_WORKSPACE
NAME
varchar2(128)
preference name
VALUE
varchar2(2000)
preference value
OBJ_VERSION
integer
version number
C. Administrative Setup
1. Company
An administrator can further select the Archive 606 or Lock 607 options. These options provide the ability to lock or archive the system's elements or documents. These options are important in supporting the compliance aspect of the system, where any user, company or element, including any document ever put in the system, is maintained forever. Selection of the Lock option 607 provides the ability to protect an entity so that no other person can change or remove it from the system. The selection of the Archive option 606 means that the record for the company will be removed from the view on the system but will remain within the system's database and could be retrieved if needed.
As illustrated in
As illustrated in
2. Resources
The administrator can further create template categories (not shown) to which the resource template can be related. The template categories are stored in the T_RES_TMPLT_CATEGORY table 339, with the resource template/category association stored as an entry in the T_RES_TMPLT_CATEGORY_MAP table 340.
3. Workspaces
As illustrated in
If a workspace group is created (not shown), then the workspace group information is stored in the T_WORKSPACE_GROUP table 349. Users are then added as members of the workspace group by adding an entry to the T_WORKSPACE_GROUP_MEMBER table 350 with a user's Member_ID and a Group_ID for a workspace group. The Member_ID comes from the T_WORKSPACE_MEMBER table 348. This links users to the workspace group.
As illustrated in
As illustrated in
4. Users
As illustrated in
As illustrated in
As illustrated in
The administrator can assign users 1021 to each workspace. At the time of selecting a workspace, the administrator can assign to users roles and privileges. Possible roles include Workspace administrator, Manager, User, and Viewer. These assignments are stored in the T_WORKSPACE_MEMBER table 348, which includes the User_ID field from the T_USER_PROFILE table 341, and the Role_ID field from the T_WORKSPACE_ROLE table 347. Users can have different roles in different workspaces. For example, as illustrated in FIG. 10E, user Janet Alhgren is given access to the workspaces listed 1021 and assigned the roles listed 1022 in each respective workspace.
As illustrated in
D. User Experience
Once the system administrator sets up an account for a user, the user has the ability to log into the system and access the workspaces. The user is provided with a URL for accessing the workspaces, as well as a unique username and password. The user, through a web enabled application, accesses the site at the URL.
1. Login
The user launches an Internet browser application at a client and enters the URL address in the browser address field. The user enters the user name and password provided by the administrator in the logon screen, illustrated in
For first time users, a screen will display the licensing agreement and terms of use, as illustrated in
The person profile information includes the user's first name 1201 and last name 1202, address 1203, street 1204, city 1205, state 1206, country 1207, and postal code 1208, and the phone 1209, mobile phone 1210, and pager 1211 numbers.
The user preferences include the default workspace 1212, the default navigator tab 1213, and the default language 1214. The user can further choose whether or not to receive email alerts and/or email messages by selecting/deselecting the email alerts option 1215 and email messages option 1216.
Future logons by the user will bypass the licensing agreement and the personal profile setup.
2. Overview Screen
After logging on, the user is displayed the overview screen of the default workspace, an example of which is illustrated in
The workspace 1301 further includes the list of unread alerts 1304 that are in the user's Message Center, actions 1306a, quick links 1309, recently viewed list 1310, and details 1311. The alerts 1304 are stored in the T_OBJ_DATA_ALERT_USER table 319. Selecting any of the alerts will open the Message Center and the appropriate alert for reference. The Message Center will be further described later in this specification.
The actions 1306a provide direct access to respective Creates dialog where users create new structures or shareable resource element for an agency, operation, resource or message. The create dialogues are shown and described later below. The agency (domain) is stored in the T_OBJ_DOMAIN table 326. The operation (initiative) is stored in the T_OBJ_INTIATIVE table 327. The resource is stored in the T_OBJ_RESOURCE table 329. The agency, operation, and resource are associated with a workspace through the T_OBJ_DATA table 318 as illustrated in
The quick links 1309 provide quick access to general purpose information (or tools) related to the main function of a workspace. The quick links are stored in the T_WORKSPACE_LINK table 350.
The recently viewed list 1310 shows the last screens the user visited. The list is refreshed during logon. Selecting any of the presented entries will open the page in detail view. This enables a user to “jump” to recently visited pages without the need to use the navigator 1302 (
The details 1311 provide information on the date the workspace was created or modified, stored in the T_WORKSPACE table 346. Depending on the options set up by the administrator for the user, the details 1311 may provide the ability to view other workspace members and whether they are online or offline.
The resources can be renamed by an administrator to better represent their usage. They can be presented as many times as desired both the agency and operation hierarchies without duplication. This allows users to update and add information in a single place and instantly provide these upgrades to all users without replication. Here, Federal Agencies is the workspace. Under the Federal Agencies workspace are the operations (initiatives). The operation hierarchy 1505 includes sub-operations, including the Agriculture/Food Disasters, Chemical/HazMat Disasters, etc. Under the operations are the objects (hidden) associated with the operations. Selecting one of the objects displays the object's details in the workspace details view 1305. During the launching of the application, the navigator 1302 will be displayed and remain continuously on the screen.
3. Agency (Domain) Screens
Selecting any of the agencies 1503 from the navigator 1302 will display the agency information within the workspace details view.
When a user selects the create button 1607 to create a new agency entry, or selects the New Agency option 1317 (
Once created, the new entry is displayed, as illustrated in
Every change to the agency will be marked as an update and will be displayed in the details window 1606.
Users can elect to be or not be alerted of any changes to agency elements by toggling the receive alert option 1624. When toggled “on”, an alert entry will be generated within the message center. The message center is described later below. The receive alert option 1624 is transferred to all daughter domains. To send an alert to other users, the send alert option 1625 is selected. This will open a message window where groups and users are selected and a message to accompany the alert can be typed.
4. Resources
The resources are the main working elements of the application. They contain information, tools, links, and data. Resources are created from resource templates as set by the administrator and assigned to specified workspaces. How a resource template is built is described above in the administrative setup section. Each resource is “owned” by a specific user who is responsible for creating and maintaining the contents.
Once the resource template is selected, a blank resource template screen is opened, as illustrated in
Access to the resource is based on permissions. The permissions are automatically set when a resource is created and, during the creation process only, are inherited from the original parent domain/agency or resource in which it is created. At any time, users can confirm the permissions set up or make changes to users and groups by selecting the permissions option 1711. These permissions are stored in the T_OBJ_DATA_PERM_GROUP table 320 and the T_OBJ_DATA_PERM_USER table 321 and were set by the system administrator.
Once a resource is created, content can be added to the resource through the create options 1712. The create options include discussion topic 1713, link 1714, RSS feed 1715, text document 1716, and upload document 1717. These options are optional and are selected to be included with the resource template by the system administrator.
a. Discussion Topics
By selecting the discussion topic option 1713 (
The discussion topic is then shown with the original discussion 1817 and its replies 1818, as illustrated in
b. Links
To create a link, the link option 1714 (
Selection of the title 1950 opens a new window in the web browser to display the contents of the listed URL file or tools, or to launch the appropriate software application. To view details of the link, the details option 1954 is selected, and a link details dialog is displayed, as illustrated in
To change any of the link parameters, the edit tab 1920 is selected, as illustrated in
Some resource topics can benefit from an internal link connecting to another element in the workspace. A user with permission to access multiple workspaces can also link the resources across workspaces.
Selection of the details option 1974 displays the link details in a new window, as illustrated in
To change any of the link parameters, the edit tab 1947 is selected, as illustrated in
c. RSS Feeds
Some resources can benefit from regular and automatic information updates provided through RSS feeds. An RSS feed is a web feed format used to publish frequently updated content from Internet websites. RSS content is read in a special web browser window called an RSS reader. To link to an RSS feed, the user needs to define the link/address of the feed. Many news providers provide RSS feed links on their web sites.
Selection of the RSS feed title 2030 launches the web site with a full article, as illustrated in
To change any of the RSS feed parameters, the edit tab 2017 is selected, as illustrated in
d. Text Files
The option to create a text file provides users with the ability to create text and add a “.txt” file to the system without using a work processing program. A text file (.txt) can be opened with a standard text editor program provided by all computers. This is a simple and easy way to create and share written documents with other users. It is also an easy way to share and preserve emails by simply copying the email, paste it into an open text document, and storing it in a resource. The email information thereby becomes part of the resource and can be shared.
Selection of the text file title 2140 displays the text content in a text editor program, as illustrated in
The user can choose to view details of the information on the text file by selecting the details option 2144, as illustrated in
To change any of the text file parameters, the actions tab 2132 is selected, as illustrated in
To view the history of the file and changes made to it, the user selects the history tab 2133, as illustrated in
e. Documents
The system enables the loading and storing of document files in any format, such as Microsoft Word™, Excel™, PowerPoint™ files and most other multimedia formats (sound, pictures, graphics, text). For the purpose of simplicity, these file formats are referred to herein as “documents”. To share documents with other users will require those users to have the appropriate software application on their computer to launch and open the specific file format.
The adding of a document here differs from the adding of a text file above in that the documents are not in a *.txt format. The documents also exist locally to a user prior to being added to the workspace.
Selection of the document name 2250 launches the application with which the document is associated and displays the document contents in the application. The user can choose to view details of the document by selecting the details option 2254, as illustrated in
To change any of the document parameters, the action tab 2221 is selected, as illustrated in
To view the history of the file and changes made to it, the user selects the history table 222, as illustrated in
f. Updating a Resource
The owner is the original creator of a resource. When there is a need to assign a resource to a different owner due to personnel changes, new responsibilities, or any other reason, a user can select the owner option 1721 (
A resource can be deleted by selecting the delete option 1722 (
g. Alerts
Users can receive an alert message for any change made to each resource listed.
h. Resource Details
The resource details 1723 (
i. Importing Resources
The system allows users to import information from an application, such as an Excel worksheet, and automatically create multiple resources. These resources will be created within a selected organization/domain and will automatically be assigned the permission of the parent organization in which they are created.
Users can import any Excel file that contains information organized in columns and rows where the first row defines the field names and the following rows are the records of information. Each row will be imported as a single resource. The system attempts to match column names with the resource template fields. Users can manually match columns and fields as well.
The administrators who create the resource templates have the option to export an Excel file that exactly matches the fields and columns and provide it to users as a guide. This Excel template will guide users to create a data source that can be easily and directly imported into specific resources in the system. An Excel file exported directly from the resource template will have the fields of the template already posted in the first row and represent all the fields as columns. Users will fill out the Excel file with the required information in a format organized as rows of data for each resource. This will simplify the import of data from an Excel file to a resource.
When importing, the system attempts to match the field names in the resource template with the column headers, and displays the matched fields as shown in
5. Knowledge Boards
Knowledge boards enable users to create a report based on the information fields contained resource templates, and hence in the resources. Users can customize this to display specific selected columns and filter information according to specific keywords or values. The resulting display in a table in the format of columns (fields) and rows (resources) which dynamically displays a real-time data from across the workspace.
When the knowledge board is selected, a knowledge board window is displayed, as shown in
To customize the report, the configure button 2416 is selected, and a configure dialog is displayed, as shown in
Once submitted, the knowledge board with the newly added fields is displayed, as shown in
6. Operations (Initiatives)
The operations process structure enables users to bring to others at each step in the process those resources (tools and information) needed to accomplish that task. In the operations view, users can build the various structures that will provide the framework for working with the information and tools stored in the system. The operations structure enables the use of resources (shared from the agencies that created and maintained them) within one or multiple procedures to accomplish a task.
The operations structure might be a timeline listing hours or days with the information presented in steps, reports and requests for assistance. Or, additional “views” might be step-by-step plans for responding to different types of emergencies, Concept of Operations plans, a National or Regional Response Plan, a mutual aid procedure, or any other formats that may be relevant to operations of this organization or group of organizations.
The main benefit of the operations view is that the information created and maintained in the agencies view can be shared with one or multiple operations and re-used as many times as required (different operational plans) without the need to duplicate the information and struggle to keep it current. Operations enable multiple viewing, usage and organization of the same data/information by different users for different activities.
With resources and knowledge board reports being shared in the operations view, any changes, updates or additions will be immediately distributed and shared within all the processes and windows where these resources are being used, thereby eliminating the need to alert users via telecommunication or electronic mail.
When creating a new operation entry, the system will automatically set the default placement in a parent/daughter hierarchy, as shown in
Once the user completes the entry of the title and description of the parent, he may choose the create button 2511 to finish and create the new entry, the reset button 2512 to clean the fields and start again, or the cancel button 2513 to terminate the operation and return to the previous screen.
As shown in
Once created, the operation is displayed as shown in
Users can select to be alerted of any changes to the operation objects. Selecting the receive alerts option 2536 toggles the option on and off. When toggled to on, an alert entry is generated within the message center. To send an alert to other users, the send alert option 2537 is selected. This opens a message window, shown in
7. Search
A quick search function provides users with the ability to enter a keyword to be searched upon at any time. All the data and information entered into the fields in the workspace are searchable, including titles, description, data fields, and names and descriptions of uploaded files.
8. Message Center
The message center displays alerts generated by the system, and messages from other groups and/or user of the system. The message center displays alerts and messages to a specific user, generated from all workspaces. This provides each user with an awareness of activities within other workspaces to which they have access.
a. Alerts
Selecting an alert will display the message. The message includes a brief description of the nature of the alert and a link to the element. Selecting the link opens the element in the workspace window. If an alert was sent by another user, the message will contain the name of the sender and message the user typed. Each alert is stored in an entry in the T_OBJ_DATA_ALERT_USER table 319, which references the object in the Object_ID field and the user in the User_ID field.
b. Messages
As shown in
9. Permissions
User access to information in the system is based upon roles and responsibilities that are setup within the permissions. For each workspace, a user can be set up as a viewer, a user, a manager, or an administrator. These set ups are performed by a system or users' administrator. Users might be set up differently in different workspaces, and therefore will have different roles in each workspace. This set up of roles in workspaces supersedes any set up in permissions.
With the Viewer role, a user has view-only permission to see selected objects as assigned. The user cannot perform any functions, such as create, details, or delete. With the User role, a user can create new objects like agencies, operations, resources, and knowledge boards within objects as assigned. The user cannot change roles or permissions, and will not see objects created by other users that are not shared. With the Manager role, the user can see all the permissions and can assign permissions only to objects for which they have permission to change. With the Administrator role, the user can see all the permissions and can assign permissions to anyone at any level. Users who create an object are automatically granted full permission to that object. They can grant any of their permission levels to other users or groups they share.
If users can access the permission setup, by definition they have permission to assign rights to any of the groups of users or individual users that are visible to them. Permissions are assigned per object and will be automatically transferred to all sub-objects that are created later. The system does not adjust permissions when objects are repositioned to/from other parent objects. After re-positioning an object, users must view and update the permissions and attributes for the moved object(s). Available permissions include read, create, update, and delete. Read permission allows a user to view object elements, including agencies, resources, operations, and knowledge boards (data fields, documents, links, or discussions in resources) only but does not allow the user to make changes. Create permission allows a user to create domains, resources, initiatives, and knowledge boards. The user cannot change details documents or links details. Update permission allows a user to modify the objects (agency, operation, resource), as well as change details, documents, links, and owners. Delete permission allows a user to delete/archive the object, to reposition the object, and grant permissions to other users or groups.
10. Personal Setup
Users can elect to change the password for their account by selecting the Change Password 3102 (
11. Logout
To ensure that the session has terminated on the user's workstation and no other users can access the user's account, the user selects the Logout button 1320 (
12. Map Feature
When utilizing the predefined address field in resources, the system provides the option to display a map based on the address information, as shown in
E. System Management
In addition to the management of the system, as described above, a system administrator can set up a number of parameters for supporting applications, including: document management, email management, encryptions management, mapping management, search management, and security management. These functions are designed to provide enhanced services to users and administration of the system. An administrator accesses these functions through the system managers screen, shown in
1. Document Manager
The document manager provides a record of each document. As each document is uploaded into the system, the system records the time it was uploaded, the originator (person who uploads) of the document, and the time. As the system is designed to provide a full accountability and compliance with regards to the information stored within the system, the system maintains any previous version/revision of a document loaded into it as well as all archived documents. The document management provides the tools to view, archive, replace, and revive all types of documents loaded in the system.
2. Security Manager
The security manager is designed to set up the network's environment. As the server is part of a private or public network, and all users have to access it through a network, it is critical that the server cold be configured to limit the access of unauthorized users to the server. These are done by identifying the type of connections used by authorized users and limit the access of all other types of data (including random packets used by hackers) from reaching the server. This is done by opening the appropriate ports for the type of protocols used by the application. Also, the system can define if information will be encrypted while it is transferred over the network and what type of encryption to use.
3. Encryption Manager
One of the key elements of the system is the depository of files (documents, images, etc.). As every system that is networked, there is a danger of malicious penetration and removal of sensitive information. To protect from that, the stored information could be encrypted while it is stored and only be decrypted after delivery to authorized users. The administrator of the system can choose the option to encrypt and what encryption technology to use.
4. Mapping Manager
The mapping management allows the administrator to provide a link to their choice of a mapping (GIS) system. The ability to provide a tool to link to a mapping system enables users to define areas or locations by either geographical coordinates or street addresses, and let the system display a map or an aerial photograph that represent the location.
5. Email Manager
The email manager allows the administrator to set a mail server on the system and define the name and address of the administrator. The role of the mail server is to provide users with the option to send alerts and messages from the system to their preferred mail client on their PC, PDA, or cell phone. These options allow users to get updated alerts without the need to be logged into the application. Mobile users can be alerted to changes in information or operation procedures critical to their operation while they are away from their primary computer system.
6. Search Manager
The search engine of the system indexed the entries within the system as keywords. This provides users the ability to locate any type of information by inquiring the database. The inquiry results are displayed to the searching users and provide links for to the presented results. This helps users to allocate requested information without an extensive knowledge of the structure which is critical in many environments where the users may have limited training or no previous knowledge of parts of the system.
For all of the foregoing reasons, the Detailed Description is to be regarded as being in all respects exemplary and not restrictive, and the breadth of the invention disclosed herein is to be determined not from the Detailed Description, but rather from the claims as interpreted with the full breadth permitted by the patent laws.
Chang, Andy, Kelley, Kevin, Phan, Hung, Ahlgren, Janet, Palmer, Gorham, Rudolph, Stuart, Moran, Gideon, Phan, Nhat, Torchon, Robert
| Patent | Priority | Assignee | Title |
| 10331419, | Nov 30 2017 | International Business Machines Corporation | Creating composite templates for service instances |
| 10331421, | Nov 30 2017 | International Business Machines Corporation | Execution of a composite template to provision a composite of software service instances |
| 10346532, | Feb 02 2016 | Activewrite, Inc.; ACTIVEWRITE, INC | Document collaboration and consolidation tools and methods of use |
| 10585914, | Sep 14 2016 | SyncRTC Inc. | Methods and apparatus for a distributed shared memory for device synchronization |
| 10755553, | Jun 30 2016 | Carrier Corporation | Collaborative alarm monitoring system and method |
| 11055134, | Nov 30 2017 | International Business Machines Corporation | Performing an action on a composite of software instances |
| 11250209, | Feb 02 2016 | Activewrite, Inc. | Document collaboration and consolidation tools and methods of use |
| 11263588, | Dec 20 2018 | Microsoft Technology Licensing, LLC | Intelligent document management in computing systems |
| 11829951, | Mar 03 2021 | Procore Technologies, Inc. | Computer system and methods for managing data, data access, and data retention |
| 9971826, | Sep 14 2016 | SYNCRTC INC | Methods and apparatus for a distributed shared memory for device synchronization |
| Patent | Priority | Assignee | Title |
| 5220657, | Dec 02 1987 | Xerox Corporation | Updating local copy of shared data in a collaborative system |
| 5255181, | Jun 01 1990 | Freescale Semiconductor, Inc | Method of planning organizational activities |
| 5381332, | Dec 09 1991 | GENERAL DYNAMICS C4 SYSTEMS, INC | Project management system with automated schedule and cost integration |
| 5406477, | Aug 30 1991 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Multiple reasoning and result reconciliation for enterprise analysis |
| 5530861, | Aug 26 1991 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Process enaction and tool integration via a task oriented paradigm |
| 5548506, | Mar 17 1994 | Automated, electronic network based, project management server system, for managing multiple work-groups | |
| 5563994, | Mar 11 1994 | Yazaki Corporation | System for graphically generating the sequence and temporal relationship between tasks in a project |
| 5655118, | Mar 21 1994 | TTI Inventions C LLC | Methods and apparatus for managing information on activities of an enterprise |
| 5664183, | Apr 19 1994 | International Business Machines Corporation | Application of groupware to ISO 9000 registration via facilitated work sessions |
| 5671360, | Jan 20 1995 | International Business Machines Corporation | Project management tool implementing authority for a people oriented work environment tool |
| 5732200, | Apr 19 1994 | International Business Machines Corporation | Integration of groupware with quality function deployment methodology via facilitated work sessions |
| 5761063, | Mar 11 1993 | Lear Corporation | Design and engineering project management system |
| 5761674, | May 17 1991 | Shimizu Construction Co., Ltd. | Integrated construction project information management system |
| 5765038, | Apr 19 1994 | International Business Machines Corporation | Integration of groupware with the integrated quality control methodology via facilitated work sessions |
| 5765140, | Nov 17 1995 | Verizon Patent and Licensing Inc | Dynamic project management system |
| 5790847, | May 23 1994 | International Business Machines Corporation; IBM Corporation | Integration of groupware with activity based management via facilitated work sessions |
| 5999968, | Oct 24 1996 | Fujitsu Limited | System and method for presenting shared information to network user in specific order |
| 6006195, | Apr 26 1996 | Workgroup Technology Corporation | Product development system and method using integrated process and data management |
| 6023572, | May 12 1998 | GOOGLE LLC | Computer based system and method for modeling activities of people in an organization |
| 6023698, | Dec 05 1996 | International Business Machines Corporation | System and method for transparently registering and updating information over the internet |
| 6036345, | Mar 11 1993 | International Automotive Components Group North America, Inc | Design and engineering project management system |
| 6067548, | Jul 16 1998 | EGUANXI, INC | Dynamic organization model and management computing system and method therefor |
| 6073107, | Aug 26 1997 | Lockheed Martin Corporation | Parametric software forecasting system and method |
| 6098047, | Feb 13 1995 | Fujitsu Limited | Constructing method of organization activity database, analysis sheet used therein, and organization activity management system |
| 6115709, | Sep 18 1998 | Oracle International Corporation | Method and system for constructing a knowledge profile of a user having unrestricted and restricted access portions according to respective levels of confidence of content of the portions |
| 6119149, | Jun 05 1998 | JDA SOFTWARE GROUP, INC | System and process allowing collaboration within and between enterprises for optimal decision making |
| 6128016, | Dec 20 1996 | NEC Corporation | Graphic user interface for managing a server system |
| 6141694, | Sep 16 1997 | Microsoft Technology Licensing, LLC | Determining and verifying user data |
| 6163761, | Feb 15 1996 | Cognis Corporation | System for monitoring and controlling production and method therefor |
| 6202066, | Nov 19 1997 | COMMERCE, GOVENMENT OF THE UNITED STATES OF AMERICA THE, AS REPRESENTED BY THE SECRETARY OF | Implementation of role/group permission association using object access type |
| 6292657, | Jul 13 1998 | Unwired Planet, LLC | Method and architecture for managing a fleet of mobile stations over wireless data networks |
| 6292830, | Aug 08 1997 | LEMASTUS, JAMES | System for optimizing interaction among agents acting on multiple levels |
| 6304892, | Nov 02 1998 | Viavi Solutions Inc | Management system for selective data exchanges across federated environments |
| 6314408, | Jul 15 1997 | Open Text Corporation | Method and apparatus for controlling access to a product |
| 6334146, | Jun 05 1998 | JDA SOFTWARE GROUP, INC | System and method for remotely accessing data |
| 6343313, | Mar 26 1996 | PIXION, INC | Computer conferencing system with real-time multipoint, multi-speed, multi-stream scalability |
| 6356880, | Apr 27 1999 | Oracle International Corporation | Methods and systems for dynamic cost allocation through task auto assignment |
| 6357010, | Feb 17 1998 | JPMORGAN CHASE BANK, N A ; MORGAN STANLEY SENIOR FUNDING, INC | System and method for controlling access to documents stored on an internal network |
| 6397191, | Jun 05 1998 | JDA SOFTWARE GROUP, INC | Object-oriented workflow for multi-enterprise collaboration |
| 6407761, | May 10 1999 | SAP SE | System and method for the visual customization of business object interfaces |
| 6442557, | Feb 27 1998 | Northrop Grumman Systems Corporation | Evaluation of enterprise architecture model including relational database |
| 6477504, | Mar 02 1998 | INSIGHT EXPRESS, INC ; DYNAMICLOGIC LLC | Method and apparatus for automating the conduct of surveys over a network system |
| 6564246, | Feb 02 1999 | International Business Machines Corporation | Shared and independent views of shared workspace for real-time collaboration |
| 6584476, | Apr 22 2000 | ORACLE INTERNATIONAL CORPORATION OIC | System and method for enforcing referential constraints between versioned database tables |
| 6670973, | Jun 29 1999 | MICRO FOCUS LLC | System and method for representing the information technology infrastructure of an organization |
| 6732277, | Oct 08 1998 | Entrust Technologies Ltd. | Method and apparatus for dynamically accessing security credentials and related information |
| 6751622, | Jan 21 1999 | ORACLE INTERNATIONAL CORPORATION, A CORPORATION, ORGANIZED UNDER THE LAWS OF THE STATE OF DELAWARE; ORACLE INTERNATIONAL CORPORATION A CORPORATION ORGANIZED UNDER THE LAWS OF THE STATE OF CALIFORNIA | Generic hierarchical structure with hard-pegging of nodes with dependencies implemented in a relational database |
| 6804657, | May 11 2000 | ORACLE INTERNATIONAL CORPORATION A CORPORATION ORGANIZED UNDER THE LAWS OF THE STATE OF CALIFORNIA | Methods and systems for global sales forecasting |
| 7043735, | Jun 08 2000 | Hitachi Ltd | System and method to dynamically select and locate server objects based on version information of the server objects |
| 7152220, | Dec 09 2000 | SenseMaking Technologies Corp. | Collaboration engine: adding collaboration functionality to computer software |
| 7167865, | Jun 30 2003 | Oracle International Corporation | Collaborative environment for producing software products |
| 7234140, | Jul 19 2001 | OCE-Technologies B.V. | Method for creating a workflow |
| 7243143, | Mar 25 1999 | AVAYA Inc | Flow probe connectivity determination |
| 7249356, | Apr 29 1999 | Fisher-Rosemount Systems, Inc | Methods and structure for batch processing event history processing and viewing |
| 7302674, | Nov 26 2002 | GOOGLE LLC | Automating document reviews in a project management system |
| 7392100, | Aug 15 2002 | Rockwell Automation Technologies, Inc. | System and methodology that facilitate factory automation services in a distributed industrial automation environment |
| 7496886, | Sep 30 2004 | Microsoft Technology Licensing, LLC | Method and system for providing cross project commitments |
| 7519683, | Apr 26 2004 | International Business Machines Corporation | Dynamic media content for collaborators with client locations in dynamic client contexts |
| 7634735, | Nov 24 2004 | Collaborative platform | |
| 7657512, | Dec 29 2005 | SAP SE | Source-context aware object-based navigation |
| 7756820, | Jul 19 2004 | SAP SE | Activity browser |
| 7930677, | Jul 12 2005 | International Business Machines Corporation | Method, system and computer program for tracking software development |
| 7996855, | Sep 15 2006 | Oracle International Corporation | Personal messaging application programming interface for integrating an application with groupware systems |
| 8122432, | Oct 04 2006 | International Business Machines Corporation | Rule management using a configuration database |
| 8381180, | Sep 08 2006 | SAP SE | Visually exposing data services to analysts |
| 8490023, | Oct 07 2005 | International Business Machines Corporation | Navigating UML diagrams |
| 8522206, | Oct 30 2009 | International Business Machines Corporation | Selective delta validation of a shared artifact |
| 8661107, | Oct 12 2010 | SAP SE | Business network meta model |
| 8707246, | Jan 30 2011 | Microsoft Technology Licensing, LLC | Engineering project event-driven social networked collaboration |
| 20010027455, | |||
| 20020029275, | |||
| 20030009742, | |||
| 20040034846, | |||
| 20040133639, | |||
| 20040148586, | |||
| 20040237066, | |||
| 20050235251, | |||
| 20060010125, | |||
| 20070209031, | |||
| 20080115103, | |||
| 20080127052, | |||
| 20090094576, | |||
| 20100050152, | |||
| 20130104098, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Aug 29 2014 | VirtualAgility Inc. | (assignment on the face of the patent) | / |
| Date | Maintenance Fee Events |
| Oct 15 2018 | REM: Maintenance Fee Reminder Mailed. |
| Feb 24 2019 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Feb 24 2019 | M1554: Surcharge for Late Payment, Large Entity. |
| Oct 17 2022 | REM: Maintenance Fee Reminder Mailed. |
| Apr 03 2023 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
| Date | Maintenance Schedule |
| Feb 24 2018 | 4 years fee payment window open |
| Aug 24 2018 | 6 months grace period start (w surcharge) |
| Feb 24 2019 | patent expiry (for year 4) |
| Feb 24 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Feb 24 2022 | 8 years fee payment window open |
| Aug 24 2022 | 6 months grace period start (w surcharge) |
| Feb 24 2023 | patent expiry (for year 8) |
| Feb 24 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Feb 24 2026 | 12 years fee payment window open |
| Aug 24 2026 | 6 months grace period start (w surcharge) |
| Feb 24 2027 | patent expiry (for year 12) |
| Feb 24 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |