US20030197743A1

System and method for representing the information technology infrastructure of an organization

Claim Score by NHIP

Abstract

A computer program for representing the information technology infrastructure of an organization includes an interactive display module and an output module. The interactive display module can generate a hierarchical list of information technology elements and organizational elements in the information technology infrastructure of the organization and can generate an interactive user interface that presents the hierarchical list. The output module can generate a hierarchical graph of the information technology infrastructure of the organization. The hierarchical list and the hierarchical graph each represent the information technology infrastructure of the organization.

US20030197743A1, drawing sheet 1 — Sheet 1 of 6

Term

Term ended

Projected expiry passed 29 June 2019, 7.2 years ago.

33 claims: 3 independent, 30 dependent

1
Broadest claimClaim Score 80, broad(NHIP)Information technology infrastructure management software, embodied in a computer-readable medium and operable, when executed, to:generate a hierarchical representation of information technology elements categorized according to one or more organizational elements of a business entity with which each information technology element is associated;wherein the hierarchical representation represents the information technology infrastructure of the business entity.
11
A system for representing the information technology infrastructure of a business entity, comprising:a memory operable to store data representing information technology elements of the business entity, organizational elements of the business entity with which each information technology element is associated, and relationships between the information technology elements and the organizational elements;a processor coupled to the memory and operable to: access the data in the memory;and generate a hierarchical representation of the information technology elements categorized according to one or more organizational elements of the business entity with which each information technology element is associated;and a display device coupled to the processor, the display device operable to display the hierarchical representation, wherein the hierarchical representation represents the information technology infrastructure of the business entity.
23
A method performed on a computer for representing the information technology infrastructure of a business entity, comprising:storing data representing information technology elements of the business entity, organizational elements of the business entity with which each information technology element is associated, and relationships between the information technology elements and the organizational elements;accessing the data in a memory;generating a hierarchical representation of the information technology elements categorized according to one or more organizational elements of the business entity with which each informational technology element is associated;and displaying the hierarchical representation on a display device;wherein the hierarchical representations represents the information technology infrastructure of the business entity.

Independent claims3

56 paragraphs in 6 sections, as filed

P-0001[0001] This application is a continuation of U.S. patent application Ser. No. 09/342,481 entitled “System and Method for Representing the Information Technology Infrastructure of an Organization” filed Jun. 29, 1999.

TECHNICAL FIELD OF THE INVENTION

[0002] This invention relates to information technology, and more particularly to a system and method for representing the information technology infrastructure of an organization.

BACKGROUND OF THE INVENTION

[0003] Organizations typically have a large number and variety of information technology elements, such as software applications, subsystems, and databases, which together make up the information technology system of the organization. Moreover, many of these information technology elements are used by various elements in the organization, such as sales, accounting, and engineering departments.

[0004] Unfortunately, the relationships between the various information technology elements and their uses by different organizational elements, which together constitute the information technology infrastructure of the organization, are normally hidden from decision-makers. A time consuming review of source code may be undertaken to determine the relationships between the information technology elements and their usage in each organizational element. This review may reveal that the information technology infrastructure is quite complex and difficult to characterize or represent.

SUMMARY OF THE INVENTION

[0005] The present invention substantially reduces or eliminates at least some of the disadvantages and problems associated with representing the information technology infrastructure of an organization. To accomplish this, the present invention provides representations of the information technology infrastructure of an organization in interactive and graphical formats that are readily discernible and technically useful.

[0006] In one embodiment of the present invention, a computer program embodied in a computer readable media for representing the information technology infrastructure of an organization includes an interactive display module and an output module. The interactive display module is operable to generate a hierarchical list of information technology elements and organizational elements in the information technology infrastructure of an organization and to generate an interactive user interface that presents the hierarchical list. The output module is operable to generate a hierarchical graph of the information technology infrastructure of the organization. The hierarchical list and the hierarchical graph each represent the information technology infrastructure of the organization.

[0007] In another embodiment, a method performed on a computer for representing the information technology infrastructure of an organization includes storing data representing information technology elements of an organization, organizational elements of the organization, and relationships between the information technology elements and the organizational elements. The method also includes generating a hierarchical list of the information technology elements and the organizational elements for presentation by an interactive user interface, wherein the hierarchical list represents the information technology infrastructure of the organization. The method further includes displaying the interactive user interface that presents the hierarchical list on a display device.

[0008] The present invention has several important technical features and advantages. First, by generating the interactive user interface that presents the hierarchical list of the information technology elements and the organizational elements of the organization, the relationships between the information technology elements and the organizational elements in the information technology infrastructure are readily discernible and modifiable. Modifications can include rearranging the hierarchical order of the information technology elements in the hierarchical list, moving the information technology elements between different organizational elements in the hierarchical list, adding information technology elements to the hierarchical list, and deleting information technology elements from the hierarchical list. Second, by generating a hierarchical graph of the information technology infrastructure, the information technology infrastructure of the organization is placed in a format that is readily presentable to and usable by others.

[0009] In a particular embodiment, the hierarchical graph will include a label for each occurrence of an information technology element that occurs more than once in the hierarchical graph. Each label will locate each occurrence of the information technology element in the hierarchical graph. The hierarchical graph will also include cross-references at each occurrence of the information technology element to the other occurrences of the information technology element in the hierarchical graph. This cross-referencing allows ready identification of high dependency sectors in the information technology infrastructure of the organization, and identifying high dependency sectors assists in determining which sectors to focus on during compliance testing, upgrades and enhancements, and general flow testing.

[0010] Other technical advantages will be readily apparent to one skilled in the art from the following figures, description, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

P-0011[0011] For a more complete understanding of the present invention, and for further features and advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, where like reference numerals represent like parts, in which:

P-0012[0012]FIG. 1 provides an overview of a system for representing the information technology infrastructure of an organization;

P-0013[0013]FIG. 2 provides an example of a data file for use in the system;

P-0014[0014]FIG. 3A illustrates an interactive user interface that presents a hierarchical list of the information technology infrastructure;

P-0015[0015]FIG. 3B illustrates an entry screen for adding an information technology element or an organizational element to the interactive user interface;

P-0016[0016]FIG. 4 illustrates a hierarchical graph of the information technology infrastructure of the organization; and

P-0017[0017]FIG. 5 shows a flowchart of a method for representing the information technology infrastructure of an organization.

DETAILED DESCRIPTION OF THE INVENTION

P-0018[0018]FIG. 1 provides an overview of a system 10 for representing the information technology infrastructure of an organization. System 10 includes a display device 20, a processing device 22, and an output device 50. Processing device 22 generates a hierarchical list 62 and a hierarchical graph 54, each of which represents the information technology infrastructure of the organization, and can be a personal computer (PC), a workstation, a mainframe, an integrated circuit (IC), or any other device that can electronically process data. Display device 20 displays hierarchical list 62 and/or hierarchical graph 54 and can be a cathode ray tube (CRT) display, a liquid crystal display (LCD), a flat-panel display (FPD), or any other device that can display an electronic image. Output device 50 generates a hard copy output 52 that presents hierarchical graph 54 and can be a laser printer, an ink jet printer, a fax machine, a plotter, or any other type of device that can generate a hard copy output of an electronic image.

P-0019[0019] To generate hierarchical list 62 and hierarchical graph 54, processing device 22 includes a processor 24 and a memory 26. Memory 26 stores representations of the information technology elements of the organization, the organizational elements of the organization, and the relationships between the information technology elements and the organizational elements. The information technology elements, the organizational elements, and the relationships between them form the information technology infrastructure of the organization. Memory 26 can be random access memory (RAM), a hard drive, a diskette, a CD-ROM, another type of magnetic or optical storage device, or any other volatile or non-volatile memory.

P-0020[0020] Memory 26 includes a computer program 42 and a database 46, which processor 24 uses in generating hierarchical list 62 and hierarchical graph 54. Computer program 42, executable by processor 24, includes a data collection module 32, a data importation module 34, a data entry module 36, an interactive display module 38, and an output module 40. Database 46 includes data files 48, each of which contains data representing the information technology elements, the organizational elements, and the relationships between them for an information technology infrastructure. Database 46 can have any type, format, or arrangement of information, as described above with respect to memory 26. Also, data files 48 may be one or more flat files, relational files, or other suitable arrangement of information.

P-0021[0021] In operation, data collection module 32, data importation module 34, and/or data entry module 36 allow computer program 42 to obtain data that represents the information technology elements, the organizational elements, and the relationships between them. Once obtained, computer program 42 can store the data in database 46 as one of data files 48. Data collection module 32 performs auto-discovery of the information technology system of the organization to locate and identify the information technology elements. Data collection module 32 can perform this function autonomously and automatically by searching the information technology system for information technology elements, polling the information technology elements, and gathering information about the information technology elements. Data collection module 32 can use any network management protocol to perform this function, such as, for example, simple network management protocol (SNMP), remote monitoring (RMON) protocol, or common management information protocol (CMIP). Data importation module 34, on the other hand, imports data from a pre-existing database or data file into computer program 42. Data importation module 34 may perform this function by accessing a preformatted database or data file or by automatically parsing an unformatted database and placing the data into the proper format. Data entry module 36 accepts data directly entered by a user of computer program 42.

P-0022[0022] After computer program 42 acquires and stores the representations of the information technology elements, the organizational elements, and the relationships between them for the particular information technology infrastructure, interactive display module 38 generates hierarchical list 62 of the information technology elements and organizational elements of the organization for presentation by an interactive user interface 60 on display device 20. Interactive user interface 60 can be a graphical user interface (GUI), a command-driven user interface, a textual character-based user interface, or any other type of user interface that can present data to a user and allow the user to manipulate the data. Interactive user interface 60 allows a user of computer program 42 to modify the relationships between the information technology elements and the organizational elements, as well as the elements themselves.

P-0023[0023] Once interactive display module 38 finishes performing the modifications to hierarchical list 62 and saves any modifications of the data used to form hierarchical list 62 to one of data files 48, output module 40 can generate hierarchical graph 54 of the information technology infrastructure of the organization in memory location 44. After this, output module 40 can display hierarchical graph 54 on display device 20 and/or cooperate with output device 50 to generate hard copy output 52 that presents hierarchical graph 54.

P-0024[0024] Note, although computer program 42 is shown as having several modules, the modules may be combined or further subdivided in numerous manners while still providing the same functionality in system 10. Also, data files 48 may be one or more flat files, relational files, or other suitable arrangement of information.

P-0025[0025] As illustrated in FIG. 1, system 10 has several features and advantages. Because interactive user interface 60 can present hierarchical list 62 of the information technology elements and the organizational elements of the organization, system 10 allows ready discernment and modification of the relationships between the information technology elements and the organizational elements in the information technology infrastructure. Moreover, interactive user interface 60 allows insertion of information technology elements into and deletion of information technology elements from hierarchical list 62. In addition, because display device 20 can display and/or hard copy output 52 can present hierarchical graph 54 of the information technology infrastructure of the organization, system 10 provides a view of the information technology infrastructure of the organization that is readily discernible and usable by others.

P-0026[0026]FIG. 2 provides an example of one of data files 48 stored in database 46 for use in system 10. As illustrated, data file 48 is a text file in which the fields in each record are tab delimited. Also, data file 48 uses five levels to represent the information technology infrastructure of the organization—organization, organization function, application, subsystem, and database. The first two levels correspond to organizational elements, and the last three levels correspond to information technology elements. Thus, each level corresponds to a different element type.

P-0027[0027] The records in data file 48 are collated into four groups: an organization group 80, a properties group 85, an element group 90, and a dependency group 95. Organization group 80 includes a record that contains identification information about the organization. Properties group 85 includes records that specify labels for the different properties associated with each element type—organization, organization function, application, subsystem, and database. For example, if the number of users needs to be associated with each application, the label “NUMBER OF USERS” would be inserted in properties group 85 in the record for applications (“APPLICATION FIELDS”). Note, the first fields of the records, except for the last record, in properties group 85 define the levels used to represent the information technology infrastructure. Thus, for data file 48, there are five levels, but in other embodiments, more or fewer levels could be used to represent the information technology infrastructure. Further note, the records in properties group 85 could be in any order. Element group 90 includes records that specify the organizational elements, the information technology elements, and the relationships between them, as well as any properties of each information technology element and organizational element. The order of the records in element group 90 specifies the relationships between the organizational elements and the information technology elements, and the labels in properties group 85 define the properties that can be specified for each element type. Finally, dependency group 95 includes records that specify dependencies between information technology elements and between information technology elements and organizational elements.

P-0028[0028] In organization group 80, an organization field 81 of the record includes the title for the data, which is usually the name of the organization. Organization information fields 82 of the record of organization group 80 include additional information about the organization. As illustrated, a number and a name are in organization information fields 82, the context of which depends on the labels in properties group 85.

P-0029[0029] Properties group 85 includes records that specify labels for the different properties associated with each type of information technology element and organizational element—organization, organization function, application, subsystem, and database. Note, each element type corresponds to a level used to represent the information technology infrastructure. An element field 86 of each record in properties group 85 associates the labels with a type of information technology element or organizational element, except for the last (“UNIVERSAL FIELDS”), which can be used for all element types. For example, “ORGANIZATION FIELDS” corresponds to the element type “organization,” described in organization group 80. Label fields 87 specify the labels for the properties associated with each element type in element field 86. Label fields 87 can allow any number of labels with which to denote the properties for the information technology elements and organizational elements. Continuing with the above example, the labels for the first two fields of organization information fields 82 in organization group 80 are “YEAR” and “CEO.” The next four records in properties group 85 associate labels with organizational elements and information technology elements in element group 90. For example, the labels associated with the element type “application” are “NUMBER OF USERS” and “PLATFORM.” The last record in properties group 85 contains labels for use with any element type. Note, the records in properties group 85 could be in any order.

P-0030[0030] Element group 90 includes records that specify the information technology elements, the organizational elements, the relationships between the elements, and the properties of the elements. An element type field 91 in each record of element group 90 contains an element type—organization function, application, subsystem and database. Note, as illustrated, the element types in element type field 91 correspond with the entries in element field 86 for the second through fifth records of properties group 85. After specifying an element type in element type field 91, an element is given an element name in a name field 92. For example, the first organization function is named “ACCOUNTING.” Following the name for the element type are the properties in properties fields 93, corresponding to the labels in label fields 87 for that element type. For example, the element type “ORGANIZATION FUNCTION” in element group 90 corresponds with “ORGANIZATION FUNCTION FIELDS” in properties group 85, and thus, the property specified in properties fields 93 for an organization function is the number of employees in that organization function, forty-two for the organization function “ACCOUNTING.” In a particular embodiment, each field in properties fields 93 is unique to one of the labels in label fields 87, except for the labels for “ORGANIZATION FIELDS,” used in organization group 80.

P-0031[0031] Following the specification of an organization function in the first record of element group 90 are the information technology elements in the organization function. For example, the organization function “ACCOUNTING” may have an application that it uses to compute payroll, as illustrated by the second record in element group 90. Thus, the information technology elements in an organization function can be broken down from the more general to the more specific, which would be the database. Following the records for the information technology elements associated with the first organization function is the record for the second organization function. The process continues for that organization function.

P-0032[0032] Dependency group 95 includes records that specify dependencies between certain information technology elements and between certain information technology elements and organizational elements. By specifying dependencies between certain elements, an element that is dependent on another element will always have the other element connected to it in hierarchical list 62 and hierarchical graph 54, no matter where or how many times the dependent element occurs.

P-0033[0033] Dependency group 95 provides two ways to associate elements. The first way is by using the keyword “DEPENDENCY PAIR” in a dependency type field 96. By specifying this keyword, the name given to the higher level element, found in name field 92 of element group 90, will be the first entry in dependency fields 97. The name of the higher level element will be followed by the element type associated with the higher level element, found in element type field 91 of element group 90. The next entry in dependency fields 97 will be the name of the lower level element, found in name field 92, followed by the element type, found in element type field 91. Thus, as illustrated, the first record of dependency group 95 specifies a dependency relationship between “Subsys 5” and “File 5.” In a particular embodiment, this dependency exists because “Subsys 5” uses “File 5” to perform its functions.

P-0034[0034] A second way to associate two elements is enabled by using the keyword “DEPENDENCY” in dependency type field 96. In this case, dependency fields 98 contain the name of the organization function, the name of the application, the name of the subsystem, and/or the name of the database in the dependency chain. Inserting the names of the elements in the dependency chain in dependency fields 98 specifies the dependency. As an example, the second record of dependency group 95 shows an alternative way to create a dependency relationship between “File 5” and “Subsys 5.” Note, in other embodiments, dependency group 95 could use only one of the ways described, or a different way, to specify associated elements.

P-0035[0035] Although data file 48 is tab-delimited, data file 48 could be delimited by a comma, space, semi-colon, colon, or other suitable character. In addition, the format illustrated in example data file 48 is not rigid but merely illustrative. The records could be arranged in different orders or collated in different groups. Moreover, the information in each record could be modified. Thus, system 10 generally contemplates any organization or structure of data file 48 to specify one or more organizational elements, one or more information technology elements, and their relationships.

P-0036[0036]FIG. 3A illustrates interactive user interface 60 that presents hierarchical list 62 of the information technology elements and the organizational elements. In this illustration, interactive user interface 60 is a GUI. Interactive user interface 60 includes a section 61 and a section 71.

P-0037[0037] Section 61 presents hierarchical list 62, which is illustrated as a tree diagram. Each level in hierarchical list 62 corresponds to one of the element types of the organization—organization, organization function, application, subsystem, or database and, hence, is a level used to represent the information technology infrastructure. To assist in presenting this representation of the information technology information infrastructure, hierarchical list 62 can expand and contract at each information technology element and each organizational element. Also, if hierarchical list 62 is too large to fit within section 61, a toolbar 63 will allow scrolling through hierarchical list 62.

P-0038[0038] Interactive user interface 60, through interactive display module 38, allows modification of the relationships between the information technology elements and the organizational elements in hierarchical list 62 presented by section 61. Also, an information technology element or organizational element can be disconnected from hierarchical list 62 when one of the elements is selected and a button 64 is activated. Note, disconnecting an element from hierarchical list 62 that has elements connected below it in the hierarchy will also disconnect the elements below the disconnected element from hierarchical list 62.

P-0039[0039] Section 71 provides a listing 72 of all the information technology elements and the organizational elements specified in data file 48. Listing 72 presented by section 71 is grouped by element type and arranged alphabetically in each group. Section 71 of interactive user interface 60 can present either all or some of the information technology elements and the organizational elements based on a pull-down menu 74. For example, pull-down menu 74 can specify whether to display either a group of information technology elements, based on element type, all of the information technology elements, or all of the information technology elements and the organizational elements, as illustrated. If section 71 does not have enough space to present all of the information technology elements and/or the organizational elements, a toolbar 73 will allow scrolling through the elements in section 71. In a particular embodiment, the, properties of the information technology elements and the organizational elements may be presented to the side of each element in section 71.

P-0040[0040] There are several ways to modify listing 72 presented by section 71. Upon activation of a button 77, interactive user interface 60 will allow the deletion of one of the information technology elements or the organizational elements from listing 72. In addition, interactive user interface 60 allows modification of the properties of the information technology elements and the organizational elements already presented by section 71 upon activation of a button 78. The properties available for an information technology element or an organizational element are determined by the labels for that element type in properties group 85 in data file 48, as will be discussed with respect to FIG. 3B. Thus, for the element type “APPLICATION” named “PAYROLL,” interactive user interface 60 will allow modification of the number of users or the platform used upon activation of button 78. Upon activation of a button 76, interactive user interface 60 will allow the addition of a new information technology element or a new organizational element to section 71.

P-0041[0041]FIG. 3B illustrates an entry screen 100 for adding an information technology element or an organizational element to listing 72 presented by section 71 of interactive user interface 60. Note, entry screen 100 is itself an interactive user interface. Entry screen 100 appears when computer program 42 detects activation of button 76. A pull-down menu 102 dictates the element type to be added to listing 72. Upon selection of an element type in pull-down menu 102, computer program 42 displays a box 104 in which to input the name of the new element, which corresponds to name field 92 of data file 48, and boxes 106 in which to input the properties of the element. Note, label fields 87 for the element type specified in pull-down menu 102 determine the number of and labels for boxes 106. Computer program 42 allows departure from entry screen 100 when at least an element type and a name have been specified in pull-down menu 102 and box 104, respectively, and a button 108 is activated or when a button 109 is activated, whereby no element will be added to listing 72.

P-0042[0042] Returning to FIG. 3A, system 10 will also allow insertion of an information technology element or an organizational element presented by interactive user interface 60 in section 71 into hierarchical list 62 presented by interactive user interface 60 in section 61. This may be accomplished, for example, using a drag and drop technique with a pointing device, through keyboard commands, or through any other type of command input technique. In a particular embodiment, if the inserted element is now beneath an element in hierarchical list 62 that has multiple occurrences in hierarchical list 62, computer program 42 will copy the inserted element to each occurrence of the higher level element in hierarchical list 62.

P-0043[0043] In certain embodiments, interactive display module 38 will allow modifications to interactive user interface 60 according to click, drag, and drop techniques. For example, when computer program 42 detects a double click on one of the information technology elements or the organizational elements in hierarchical list 62, computer program 42 will contract or expand hierarchical list 62 at that element. Also, when computer program 42 detects highlighting of and a click upon one of the information technology elements presented by section 71 of interactive user interface 60, computer program 42 will copy the highlighted information technology element, illustrated by an icon 75, and show the movement of the copy in response to the movement of an input pointing device, such as a mouse. When computer program 42 detects that icon 75 is over one of the information technology elements or organizational elements in hierarchical list 62, computer program 42 will highlight the information technology element or organizational element in hierarchical list 62 if the connection is proper. The connection is complete when computer program 42 detects an unclick signal from the input device. Moreover, computer program 42 will allow the use of a similar technique to move information technology elements and organizational elements already presented by section 61 within hierarchical list 62. In addition, if computer program 42 detects a right click on one of the elements, it will present a menu of edit commands, such as for viewing the properties of the element.

P-0044[0044] In embodiments where dependencies between information technology elements are specified, if an information technology element inserted into hierarchical list 62 is dependent on any other information technology element, the other information technology element will automatically be connected to the inserted element in hierarchical list 62.

P-0045[0045] Interactive display module 38 provides shortcuts in a toolbar 66 for many of the previously mentioned operations, such as disconnecting elements in hierarchical list 62, deleting elements in listing 72, and viewing the properties of the elements. Buttons 67 and 68 allow forward and backward searches through hierarchical list 62 presented by section 61 to find multiple occurrences of an element. Interactive display module 38 will perform such a search when it detects selection of an element in hierarchical list 62 or in listing 72 and activation of button 67 or button 68. Interactive display module 38 will then find the previous or the next occurrence of that element in hierarchical list 62, respectively. It may also list (in a separate view) all dependencies for the selected element.

P-0046[0046] Once hierarchical list 62 in interactive user interface 60 accurately represents relationships between the information technology elements and the organizational elements of the organization, computer program 42 saves the data presented by interactive user interface 60 in data file 48, like the one shown in FIG. 2. Then, computer program 42 can generate hierarchical graph 54.

P-0047[0047]FIG. 4 illustrates hierarchical graph 54 of the information technology infrastructure of the organization. As illustrated, hierarchical graph 54 uses a five-level hierarchical order to represent the information technology infrastructure of the organization, corresponding to the five levels specified in data file 48 in FIG. 2. A first level 110 and a second level 120 correspond to the organizational elements of the organization—organization and organizational function, respectively. A third level 130, a fourth level 140, and a fifth level 150 correspond to the information technology elements of the organization—application, subsystem, and database, respectively.

P-0048[0048] In general, hierarchical graph 54 corresponds with hierarchical list 62 in interactive user interface 60. However, hierarchical graph 54 shows each information technology element and organizational element in the information technology infrastructure, whether visible in section 61 of interactive user interface 60 or not. Note, the names of the information technology elements and of the organizational elements in hierarchical graph 54 correspond with the names used in hierarchical list 62.

P-0049[0049] Output module 40 generates hierarchical graph 54 in memory location 44. Output module 40 can then display hierarchical graph 54 on display device 20 or cooperate with output device 50 to generate hard copy output 52, which presents hierarchical graph 54.

P-0050[0050] In certain embodiments, each occurrence of an information technology element that has multiple occurrences in hierarchical graph 54 has a unique label. In addition, each occurrence includes cross-references to the other occurrences of the information technology element in hierarchical graph 54. For example, in fifth level 150, database “File 5” is shown to occur four times in the information technology infrastructure of the organization. Each occurrence of “File 5” is identified by a label 152 at the upper left hand corner, which specifies the location of the occurrence in hierarchical graph 54 in a two-dimensional grid. In the example, each level of the information technology infrastructure corresponds to a letter and each element on that level corresponds to a number. Each occurrence of “File 5” also has cross-references 154 at the bottom to the other occurrences of “File 5.” By providing cross-references 154 between information technology elements that have multiple occurrences in the information technology infrastructure of the organization, high dependency sectors of the information technology infrastructure are readily discernible throughout the information technology infrastructure. The identification of these high dependency sectors assists in determining where to focus during compliance testing, upgrades and enhancements, and general flow testing. Note, in other embodiments, every occurrence of every element in hierarchical graph 54 has a unique label. Also in other embodiments, label 152 may locate the elements in hierarchical graph 54 by other manners than a two-dimensional grid.

P-0051[0051] In a particular embodiment, output module 40 displays hierarchical graph 54 on display device 20 in a graphics program that allows the specification of the spacing, labeling, and other display options. In addition, each element type may be given a different icon, as illustrated in FIG. 4. System 10 may then generate hard copy output 52 that presents modified hierarchical graph 54.

P-0052[0052]FIG. 5 shows a flowchart 200 of a method for representing the information technology infrastructure of an organization. At step 204, computer program 42 displays a series of options. If computer program 42 detects a termination request at step 208, computer program 42 terminates. However, if computer program 42 does not detect a termination request at step 208, computer program 42 determines whether there is a request for a new data file at step 212. If there is a request for a new data file at step 212, computer program 42 obtains new data at step 216, using data collection module 32, data importation module 34, and/or data entry module 36. Then, at step 220, computer program 42 stores this data as data file 48 in database 46. Once step 220 is complete, computer program 42 proceeds to step 232. Returning to step 212, if there is no request for a new data file, computer program 42 determines whether there is a request to access an existing data file 48 in database 46 at step 224. If there is no request to access an existing data file 48 at step 224, computer program 42 proceeds to step 204 to re-display options to the user. If, however, there is a request to access an existing data file 48 at step 224, computer program 42 accesses requested data file 48 in database 46 at step 228 and proceeds to step 232.

P-0053[0053] If computer program 42 detects a request for interactive user interface 60 at step 232, computer program 42 generates hierarchical list 62 of the information technology elements and the organizational elements of the organization, generates interactive user interface 60 that presents hierarchical list 62, and displays interactive user interface 60 at step 236. If computer program 42 then detects a request for a modification to hierarchical list 62 at step 240, such as adding elements, deleting elements, or modifying their properties and/or relationships, computer program 42 performs this modification at step 242. Computer program 42 will then re-generate and re-display hierarchical list 62 of the modified relationship between the information technology elements and the organizational elements at step 236. This may continue while the user performs modifications to hierarchical list 62. If there is no request for a modification at step 240, computer program 42 determines whether there is a request for closing interactive user interface 60 at step 244. If there is no request for closing interactive user interface 60 at step 244, computer program 42 returns to step 240. Once there is a request for closing interactive user interface 60 at step 244, computer program 42 updates accessed data file 48 at step 246 and determines whether there is a request for hierarchical graph 54 at step 248. Step 248 will also occur if there is no request for interactive user interface 60 at step 232.

P-0054[0054] At step 248, computer program 42 determines whether there is a request for hierarchical graph 54. If there is no request for hierarchical graph 54 at step 248, computer program 42 closes accessed data file 48 at step 250 and returns to step 204. If, however, there is a request for hierarchical graph 54 at step 248, computer program 42 generates hierarchical graph 54 of the information technology infrastructure of the organization at step 254. At step 258, computer program 42 displays hierarchical graph 54 on display device 20. Next, computer program 42 determines whether there is a request for hard copy output 52 that presents hierarchical graph 54 at step 262. If there is no such request, computer program 42 proceeds to step 250. However, if there is such a request, computer program 42 and output device 50 cooperate to generate hard copy output 52, which presents hierarchical graph 54, at step 266. After step 266, computer program 42 closes accessed data file 48 at step 250 and returns to step 204.

P-0055[0055] Although the information technology infrastructure of the organization has been illustrated as having five element types, each element type representing a different level of the infrastructure, system 10 can readily accommodate any number and combination of element types to represent the information technology infrastructure. For example, a new element type could be inserted under the entry type “Application” to specify subprograms of the application, thus creating six levels in the infrastructure. Therefore, system 10 contemplates any number of levels for representing the information technology infrastructure of an organization.

P-0056[0056] Although the present invention has been described with several embodiments, a myriad of changes, variations, alterations, transformations, and modifications may be suggested to one skilled in the art, and it is intended that the present invention encompass such changes, variations, alterations, transformations, and modifications as fall within the scope of the appended claims.

Contents6

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US2006156274A1	Cited by	United States of America	Pre-grant
US8028334B2	Cited by	United States of America	Applicant
US2009006427A1	Cited by	United States of America	Pre-grant
US2008059912A1	Cited by	United States of America	Pre-grant
US8121996B2	Cited by	United States of America	Applicant
US9997196B2	Cited by	United States of America	Applicant
US10067630B2	Cited by	United States of America	Search report
US7937462B2	Cited by	United States of America	Applicant
US10324605B2	Cited by	United States of America	Applicant
US2009287808A1	Cited by	United States of America	Pre-grant
US7822724B2	Cited by	United States of America	Applicant
US7568022B2	Cited by	United States of America	Search report
US9304649B2	Cited by	United States of America	Search report
US2007043674A1	Cited by	United States of America	Pre-grant
US9209996B2	Cited by	United States of America	Applicant
US2007124255A1	Cited by	United States of America	Pre-grant
US2003038836A1	Cited by	United States of America	Pre-grant
US9870802B2	Cited by	United States of America	Applicant
US7428705B2	Cited by	United States of America	Search report
US8683352B2	Cited by	United States of America	Search report
US10013420B1	Cited by	United States of America	Applicant
US2006129419A1	Cited by	United States of America	Pre-grant
WO2007021823A2	Cited by	World Intellectual Property Organization (WIPO)	Search report
US11157154B2	Cited by	United States of America	Applicant
US11487705B1	Cited by	United States of America	Applicant
US8914341B2	Cited by	United States of America	Applicant
US10318894B2	Cited by	United States of America	Applicant
US10264022B2	Cited by	United States of America	Applicant
US11477093B2	Cited by	United States of America	Applicant
US8176158B2	Cited by	United States of America	Applicant
US9742619B2	Cited by	United States of America	Applicant
US2014160979A1	Cited by	United States of America	Pre-grant
WO2007022364A3	Cited by	World Intellectual Property Organization (WIPO)	International search
US2007289008A1	Cited by	United States of America	Pre-grant
US8875025B2	Cited by	United States of America	Search report
US8140609B2	Cited by	United States of America	Applicant
US2014173523A1	Cited by	United States of America	Pre-grant
US2006080327A1	Cited by	United States of America	Pre-grant
WO2007022364A2	Cited by	World Intellectual Property Organization (WIPO)	Search report
US2006248501A1	Cited by	United States of America	Pre-grant
US9256841B2	Cited by	United States of America	Applicant
US2005278191A1	Cited by	United States of America	Pre-grant
US2008183782A1	Cited by	United States of America	Pre-grant
US2006125847A1	Cited by	United States of America	Pre-grant
US8990120B2	Cited by	United States of America	Applicant
US2008028337A1	Cited by	United States of America	Pre-grant
US7886040B2	Cited by	United States of America	Applicant
US11747972B2	Cited by	United States of America	Applicant
WO2007021823A3	Cited by	World Intellectual Property Organization (WIPO)	International search
US2006130133A1	Cited by	United States of America	Pre-grant
US8140635B2	Cited by	United States of America	Applicant
US2009204693A1	Cited by	United States of America	Pre-grant
US10795855B1	Cited by	United States of America	Applicant
US2012210231A1	Cited by	United States of America	Pre-grant
US8626887B2	Cited by	United States of America	Applicant
US2016216846A1	Cited by	United States of America	Pre-grant
US7788599B2	Cited by	United States of America	Search report
US2006150143A1	Cited by	United States of America	Pre-grant
US9530105B2	Cited by	United States of America	Search report
US2002007298A1	Cites	United States of America	Pre-grant
US2002059161A1	Cites	United States of America	Pre-grant
US2003197733A1	Cites	United States of America	Pre-grant
US2004107125A1	Cites	United States of America	Pre-grant
US2005216421A1	Cites	United States of America	Pre-grant
US2006248016A1	Cites	United States of America	Pre-grant
US5559955A	Cites	United States of America	Pre-grant
US5838965A	Cites	United States of America	Pre-grant
US5864865A	Cites	United States of America	Pre-grant
US5878258A	Cites	United States of America	Pre-grant
US6128016A	Cites	United States of America	Pre-grant
US6407761B1	Cites	United States of America	Pre-grant
US6499026B1	Cites	United States of America	Pre-grant
US6505172B1	Cites	United States of America	Pre-grant
US6836878B1	Cites	United States of America	Pre-grant
US7110983B2	Cites	United States of America	Pre-grant

2 members in 1 office; this record represents the family

This recordMember, by publication datePriority claim

Priority claims6

Priority claims
Document	Office	Kind	Date
34248199	United States of America	A	1999-06-29
34248199	United States of America	A	1999-06-29
45416003	United States of America	A	2003-06-04
09342481	–	–	–
US19990342481	–	–	–
US20030454160	–	–	–

Members2

Family members, oldest first
Document	Office	Kind
US2003197743A1	United States of America	A1	2003-10-23
US6670973B1	United States of America	B1	2003-12-30

107 transactions on the USPTO file

Abandoned after 4 non-final rejections, 4 final rejections, 1 RCE and 3 appeals.

Non-final rejections: 4
Final rejections: 4
RCEs: 1
Appeals: 3

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2014-10-09	Email NotificationEML_NTR	EML_NTR
2014-10-09	Mailing of Abandonment after Board of AppealsAbandonedMABN10	MABN10
2014-10-02	Abandonment after Board of AppealsAbandonedABN10	ABN10
2014-10-02	Case Docketed to Examiner in GAUDOCK	DOCK
2014-10-02	Case Docketed to Examiner in GAUDOCK	DOCK
2014-07-21	Electronic ReviewELC_RVW	ELC_RVW
2014-07-21	Email NotificationEML_NTF	EML_NTF
2014-07-21	Mail BPAI Decision on Appeal - AffirmedMAPDA	MAPDA
2014-07-17	BPAI Decision - Examiner AffirmedAPDA	APDA
2011-12-05	Email NotificationEML_NTR	EML_NTR
2011-12-05	Docketing Notice Mailed to AppellantAP_DK_M	AP_DK_M
2011-12-02	Email NotificationEML_NTR	EML_NTR
2011-12-02	Mail Reply Brief Noted by ExaminerMRBNE	MRBNE
2011-12-01	Assignment of Appeal NumberAPAS	APAS
2011-11-28	Appeal Awaiting BPAI DocketingAPWD	APWD
2011-11-21	Reply Brief Noted by ExaminerRBNE	RBNE
2011-11-16	Date Forwarded to ExaminerFWDX	FWDX
2011-11-15	Reply Brief FiledAPRB	APRB
2011-09-15	Electronic ReviewELC_RVW	ELC_RVW
2011-09-15	Email NotificationEML_NTF	EML_NTF
2011-09-15	Mail Examiner's AnswerMAPEA	MAPEA
2011-09-14	Exam. Ans. Review CompletePACC	PACC
2011-08-18	Examiner's Answer to Appeal BriefAPEA	APEA
2011-06-23	Case Docketed to Examiner in GAUDOCK	DOCK
2011-06-08	Date Forwarded to ExaminerFWDX	FWDX
2011-06-07	Appeal Brief Review CompleteAPBR	APBR
2011-05-27	Appeal Brief FiledAP.B	AP.B
2011-03-29	Notice of Appeal FiledN/AP	N/AP
2011-01-20	Electronic ReviewELC_RVW	ELC_RVW
2011-01-20	Email NotificationEML_NTF	EML_NTF
2011-01-20	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2011-01-18	Final RejectionFinal rejectionCTFR	CTFR
2010-09-10	Date Forwarded to ExaminerFWDX	FWDX
2010-09-08	Response after Non-Final ActionA...	A...
2010-06-09	Electronic ReviewELC_RVW	ELC_RVW
2010-06-09	Email NotificationEML_NTF	EML_NTF
2010-06-09	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2010-06-06	Non-Final RejectionNon-final rejectionCTNF	CTNF
2010-05-03	Miscellaneous Incoming LetterLET.	LET.
2010-01-28	Appeal Brief Review CompleteAPBR	APBR
2010-01-28	Date Forwarded to ExaminerFWDX	FWDX
2010-01-08	Appeal Brief FiledAP.B	AP.B
2009-11-09	Notice of Appeal FiledN/AP	N/AP
2009-11-09	Miscellaneous Incoming LetterLET.	LET.
2009-08-07	Electronic ReviewELC_RVW	ELC_RVW
2009-08-07	Email NotificationEML_NTF	EML_NTF
2009-08-07	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2009-08-03	Final RejectionFinal rejectionCTFR	CTFR
2009-05-22	Email NotificationEML_NTR	EML_NTR
2009-05-22	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2009-05-19	Date Forwarded to ExaminerFWDX	FWDX
2009-05-15	Correspondence Address ChangeC.AD	C.AD
2009-04-28	Response after Non-Final ActionA...	A...
2009-01-29	Electronic ReviewELC_RVW	ELC_RVW
2009-01-28	Email NotificationEML_NTF	EML_NTF
2009-01-28	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2009-01-21	Non-Final RejectionNon-final rejectionCTNF	CTNF
2008-10-20	Appeal Brief Review CompleteAPBR	APBR
2008-10-20	Date Forwarded to ExaminerFWDX	FWDX
2008-10-08	Appeal Brief FiledAP.B	AP.B
2008-10-08	Request for Extension of Time - GrantedXT/G	XT/G
2008-07-08	Notice of Appeal FiledN/AP	N/AP
2008-06-20	Email NotificationEML_NTR	EML_NTR
2008-06-20	Mail Advisory Action (PTOL - 303)MCTAV	MCTAV
2008-06-17	Advisory Action (PTOL-303)CTAV	CTAV
2008-06-12	Date Forwarded to ExaminerFWDX	FWDX
2008-06-09	Response after Final ActionA.NE	A.NE
2008-04-09	Electronic ReviewELC_RVW	ELC_RVW
2008-04-08	Email NotificationEML_NTF	EML_NTF
2008-04-08	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2008-03-31	Final RejectionFinal rejectionCTFR	CTFR
2008-01-26	Date Forwarded to ExaminerFWDX	FWDX
2008-01-07	Response after Non-Final ActionA...	A...
2007-10-06	Electronic ReviewELC_RVW	ELC_RVW
2007-10-05	Email NotificationEML_NTF	EML_NTF
2007-10-05	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2007-10-01	Non-Final RejectionNon-final rejectionCTNF	CTNF
2007-08-25	Date Forwarded to ExaminerFWDX	FWDX
2007-08-25	Date Forwarded to ExaminerFWDX	FWDX
2007-08-25	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2007-08-22	Request for Continued Examination (RCE)RCEX	RCEX
2007-08-22	Workflow - Request for RCE - BeginBRCE	BRCE
2007-05-24	Electronic ReviewELC_RVW	ELC_RVW
2007-05-23	Email NotificationEML_NTF	EML_NTF
2007-05-22	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2007-05-14	Final RejectionFinal rejectionCTFR	CTFR
2007-03-14	Paralegal or electronic terminal disclaimer approvedP574	P574
2007-03-10	Date Forwarded to ExaminerFWDX	FWDX
2007-03-05	Terminal Disclaimer FiledDIST	DIST
2007-03-05	Response after Non-Final ActionA...	A...
2006-12-04	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2006-11-27	Non-Final RejectionNon-final rejectionCTNF	CTNF
2006-11-15	Case Docketed to Examiner in GAUDOCK	DOCK
2006-09-29	Case Docketed to Examiner in GAUDOCK	DOCK
2005-04-15	IFW TSS Processing by Tech Center CompleteTSSCOMP	TSSCOMP
2003-07-27	Case Docketed to Examiner in GAUDOCK	DOCK
2003-07-11	Application Return from OIPEWROIPE	WROIPE
2003-07-11	Application Is Now CompleteCOMP	COMP
2003-07-11	Pre-Exam Office Action WithdrawnW/OA	W/OA
2003-07-11	Application Return TO OIPEROIPE	ROIPE

Showing 100 of 107

5 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2014-10-02	Information on status: application discontinuationABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISIONSTCB	STCB
2009-03-25	AssignmentAS	AS
2009-03-25	AssignmentAS	AS
2009-03-24	AssignmentAS	AS
2009-03-24	AssignmentAS	AS

System and method for representing the information technology infrastructure of an organization

Claim Score by NHIP

Abstract