US9280581B1 - Method and system for determination of data completeness for analytic data calculations - Google Patents
Method and system for determination of data completeness for analytic data calculations Download PDFInfo
- Publication number
- US9280581B1 US9280581B1 US13/796,132 US201313796132A US9280581B1 US 9280581 B1 US9280581 B1 US 9280581B1 US 201313796132 A US201313796132 A US 201313796132A US 9280581 B1 US9280581 B1 US 9280581B1
- Authority
- US
- United States
- Prior art keywords
- data
- completeness
- data model
- enterprise
- costs
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- G06F17/30424—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
- G06F16/212—Schema design and management with details for data modelling support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F17/10—Complex mathematical operations
- G06F17/18—Complex mathematical operations for evaluating statistical data, e.g. average values, frequency distributions, probability functions, regression analysis
-
- G06F17/30294—
Definitions
- This disclosure relates in general to modeling data, and more particularly, to determining a measure of data completeness associated with a metric of interest extracted from a data model.
- the world is comprised of a wide and varied assortment of environments and subsystems. Many environments present challenges to sufficiently accurate modeling. A microcosm of this problem occurs in many enterprise architectures. These enterprise architectures may be intended to have a wide variety of uses: disseminating information about goods and services offered through a site on the World Wide Web, achieving objectives related to a business concern, providing a programming infrastructure for development of software, or keeping track of sales and sales force information.
- the second approach is to store items of interest of an enterprise architecture in a relational database.
- Models created with a relational database are particularly susceptible to changes in the enterprise architecture itself. Adding layers, applications, dependencies, projects, geographical locations, etc., to an enterprise architecture may require changes to a table schema implementing the model, which may in turn entail revising all the SQL statements used to implement the database.
- importing data to populate such databases may be difficult, as the data may be contained in a large number of disparate and heterogeneous repositories (if, indeed, such data exists at all).
- one metric of interest may be the cost of an asset.
- the cost of an asset within an enterprise architecture may go beyond the direct cost of purchasing and maintaining that asset.
- the true cost of an asset depends on the cost of the infrastructure and other resources needed to actually support or implement that asset.
- the total cost of a single asset may include the cost of portions of other assets, and the cost of those assets may depend on still other assets. Consequently, the actual cost of an asset may encompass both direct and indirect costs.
- Embodiments disclosed herein may provide a measure of data completeness associated with an analysis of the data model such as the calculation of a metric of interest, to be calculated substantially in parallel with the analysis of the data model used to calculate the metric of interest.
- the measure of data completeness may provide a confidence as to the accuracy of the analysis.
- a request for an analysis of an enterprise may be received by a system.
- the system may include a server operable to create and populate a data model of an enterprise, such that the data model includes components representing physical and logical entities in the enterprise.
- the system may also contain a set of instructions executable to receive a request for an analysis of the data model (or some part thereof), perform the analysis of the data model, and perform an analysis of the data completeness of the model with respect to the requested analysis, such that a measure of the data completeness is returned with the analysis.
- An analysis of the data completeness may include identifying all paths that the requested analysis requires, identifying each step in each path, performing some calculation or determination associated with each step, multiplying, aggregating or otherwise determining a data completeness for each path based on the data completeness for each step, and multiplying, aggregating or otherwise determining an overall data completeness associated with the requested analysis based on the data completeness based on the paths.
- calculation of a data completeness measure may be performed at each step (incrementally) in a path or may be performed after the path has been traversed (collectively), but is generally performed in parallel with the processing of any calculations associated with the analysis of the metric of interest.
- FIG. 1 depicts a high level diagram of one embodiment of an enterprise architecture and a system for creating a data model
- FIG. 2 depicts a graphical representation of one embodiment of a component data structure
- FIG. 3 depicts a graphic representation of one embodiment of a relationship data structure
- FIG. 4 depicts a high level diagram of one embodiment of an enterprise architecture and a system for performing metric calculations
- FIG. 5 depicts a representation of one embodiment of an exemplary data model of an enterprise architecture
- FIG. 6 depicts a flow diagram of one embodiment of a methodology to calculate a cost for an asset in an enterprise architecture
- FIG. 7 depicts an example of a set of tables indicating the first level dependencies of each component in the data model of FIG. 5 ;
- FIG. 8 is a diagram illustrating one embodiment of an altered representation of the data model of FIG. 5 ;
- FIG. 9 a representation of one embodiment of the dependency map determined by a graph traversal mechanism applied with respect to the data model of representation 900 and the percentages of the example depicted in FIG. 8 ;
- FIG. 10 is a diagram illustrating one embodiment of an altered representation of the data model of FIG. 5 ;
- FIG. 11 illustrates one embodiment of a cost model for the enterprise architecture represented by the data model of FIG. 5 ;
- FIG. 12 depicts a representation of the results of the application of a cost model
- FIG. 13 depicts a diagram illustrating a one embodiment of an enterprise and system for performing data completeness analyses
- FIG. 14 depicts a flow diagram of one embodiment for determining data completeness for analytic data calculations
- FIG. 15 depicts a graph of a portion of a data model
- FIG. 16 depicts portions of the data model shown in FIG. 15 decomposed into paths
- FIG. 17 depicts the path shown in FIG. 16 decomposed into steps.
- FIGS. 18A-18F depict an exemplary data model, an exemplary query corresponding to a metric of interest for the data model, and sample output including data completeness measures corresponding to the metric of interest.
- the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” or any other variation thereof, are intended to cover a non-exclusive inclusion.
- a process, product, article, or apparatus that comprises a list of elements is not necessarily limited only those elements but may include other elements not expressly listed or inherent to such process, product, article, or apparatus.
- the term “or” as used herein is generally intended to mean “and/or” unless otherwise indicated. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
- a term preceded by “a” or “an” includes both singular and plural of such term, unless clearly indicated otherwise (i.e., that the reference “a” or “an” clearly indicates only the singular or only the plural).
- the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
- computer-executable instructions may be lines of assembly code or compiled C ++ , Java, or other language code. Other architectures may be used. Additionally, a computer program or its software components with such code may be embodied in more than one data processing system readable medium in more than one computer.
- Embodiments disclosed herein may be useful for determining a measure of data completeness for an analysis of an enterprise based on a data model. To provide context for how a measure of data completeness may be useful, a description of an exemplary analysis and data completeness calculation may be helpful.
- An enterprise may refer to any business operation that can vary from being a small company with a single employee to a conglomerate spread out globally with thousands of employees, computers and other machines via a network, etc., to market its own product or service.
- Each enterprise may be unique in terms of people, buildings and other property, equipment, assets, etc., how the enterprise functions, business rules the enterprise follows, departments, etc. While embodiments herein have been described with respect to an enterprise or an enterprise architecture it will be noted that other embodiments may be equally well applied in other contexts, and the use of an enterprise architecture to illustrate embodiments herein should not be taken as placing any restrictions on the applicability of these embodiments.
- FIG. 1 depicts a diagram illustrating one embodiment of a simplified architecture of an enterprise 50 where elements of the enterprise 50 may be coupled via network 90 to system 100 .
- Enterprise 50 may have variety of departments or other divisions.
- enterprise 50 may include an IT department 110 , a human resources department 120 , and engineering department 130 .
- Each department may further include equipment, machines, storage, etc., to support that department.
- IT department 110 may have computers 111 running applications 112 , server 113 having database 114 storing spreadsheets 115 with information about various computers located in IT department 110 , HR department 120 and engineering department 130 .
- HR department 120 may include computers 121 and employee database 122 storing information about employees working in IT department 110 , HR department 120 and engineering department 130 , as well as a physical file cabinet 123 storing employee files, government compliance records, and other data in hard copy 124 .
- Engineering department 130 may have servers 131 and computers 132 running applications 133 operable to perform research and development of products, manage supply chain contacts, and other logistics, etc.
- Data model 105 may be used to model physical and logical entities, systems, etc., in an enterprise architecture, which may allow a user at computer 150 to, for example, evaluate the effectiveness of a business project, process, division, etc. or otherwise obtain data on the architecture of enterprise 50 .
- Data model 105 may use components and relationships to model enterprise 50 .
- the term “component” is intended to mean a representation of any definable, logical or physical entity or asset.
- a component may have a group of properties.
- an entity or asset may be any portion of enterprise 50 desired to be represented, including hardware, such as servers 113 or 131 or databases 114 or 122 , applications 112 or 133 which may reside on one or more actual machines, virtual data repositories, firmware and the like.
- a network may be represented as a component
- a subnetwork of that network may be represented as a component
- a server on the subnetwork may also be represented as a component
- an application running across that server and other servers may also be represented as a component
- a table within that application may be represented as a component, etc.
- “Relationships” may be used in tandem with components to model systems and environments by representing an association or dependencies between two components.
- System 100 may be useful for modeling enterprise 50 .
- System 100 may include server 101 having CPU 102 and memory 103 having a set of instructions executable by CPU 102 to communicate via network 90 to elements of enterprise 50 coupled to the network 90 to gather data related to modeling enterprise 50 as well as data for collecting and populating into data model 105 stored in repository 104 .
- Modeling of data may be performed by data modeling module 107 operating on data modeling system 106 . Modeling may involve communicating with computers and other machines in enterprise 50 (e.g. by data collection module 108 ) to identify operating systems, applications running thereon, repositories storing information, etc.
- Data modeling module 107 may receive information about various physical and logical entities (e.g. from data collection module 108 ), instantiate components to represent these entities, and associate relationships with various components to model enterprise 50 using data model 105 , and may communicate with repository 104 to store data model 105 therein.
- FIG. 2 depicts a graphical representation of one embodiment of a component data structure capable of representing a physical or logical entity in enterprise 50 .
- Component 200 is a generic component which may be used to represent a logical or physical entity within enterprise 50 .
- Component 200 may have a set of fields 210 which contain information relating to the entity associated with component 200 .
- Fields 210 may include a field for name 220 , description 230 , properties 240 and checks 250 .
- Various other fields 210 may be included to further define component 200 .
- Name field 220 may be used to particularly associate component 220 with a specific physical or logical entity.
- Description field 230 may further identify component 200 , associate component 200 with a particular entity, or allow component 200 to be associated with a particular component type (as explained below).
- Property field 240 may be used to represent the attributes or characteristics of the physical or logical entity represented by component 200 , or with which component 200 is associated.
- Property field 240 may be associated with one or more properties, a property may consist of a property name which may be associated with a value. This value in turn may correspond to an attribute of the physical or logical entity represented by component 200 .
- a property may be a string, boolean, decimal number, date/time, or an enumerated type, which describes the category of values a particular property may have.
- a property may in turn be a data structure which has a name, a description, and a value. This data structure may then be given values based on an attribute of the entity represented by component 200 .
- Component 200 may be used to represent any object in enterprise 50 .
- name field 220 may be set to “ITDeptServer”
- description 230 may be set to “server computer”
- property field 240 may contain three properties “OSType”, “RAM”, and “FreeStorage”, which may be assigned the values corresponding to attributes 112 of server computer 110 , “Solaris”, “8 MB” and “6 MB” respectively.
- component 200 may represent IT department database 114 ; name field 220 may be set to “ITDeptDB”, description 230 may be set to “database server application”, property field 240 may contain three properties “OSType”, “Footprint”, and “Listen Port”, which may be assigned the values corresponding to attributes of database server 114 , “Solaris”, “12 MB” and “2100” respectively.
- component 200 may represent any entity, whether logical or physical equally well.
- FIG. 3 depicts a graphic representation of one embodiment of a relationship data structure.
- Relationship 300 may be used to represent an association or dependency between two or more components 200 .
- Relationship 300 may have a set of fields 310 which contain information pertinent to an association or dependency between two components.
- Fields 310 may include a field for name 320 , description 330 , property 340 , and checks 350 as described above with respect to component 200 .
- Name field 320 may be used to particularly associate relationship 300 with two or more physical or logical entities.
- the name associated with name field 320 may be built programmatically based on the relationship type name and the names of the two components it is connecting. So, a “runs on” relationship type exists between component “ITDeptDB” and “ITDeptServer”, the relationship name may be built automatically as “ITDeptDB runs on ITDeptServer”. That way, if either of the components' names changes, the relationship name may automatically change to reflect this.
- Description field 330 may further distinguish relationship 300 , associate relationship 300 with components, or allow relationship 300 to be associated with a particular relationship type (as explained below).
- Property field 340 may allow attributes of the relationships, dependencies between the relationships, or associations between the relationships, to be represented by a name and value pair.
- Checks 350 may contain one or more pieces of logic which perform operations based on certain set of conditions, as described above with respect to relationship 300 .
- fields 310 include fields 360 , 370 to identify components 200 to which relationship 300 corresponds. Various other fields 310 may be included to further define relationship 300 .
- data may be collected from the various data sources maintained by the various parts/areas of enterprise 50 and populated into data model 105 stored in repository 104 .
- data collection module 108 operating on computer 106 may communicate with enterprise 50 via network 90 (e.g., computers or other elements of enterprise architecture coupled to network 90 ) to collect data about enterprise 50 . Collection of data may be performed automatically, such as according to a predetermined event or time period, may include sending requests to various computers or machines in enterprise 50 , may include sending a request to a human user to input data, or the like. Examples and further description of how data may be collected from various sources may be found in U.S. Pat. No. 7,822,710 issued Oct. 26, 2010 to Miller et al, and is incorporated by reference herein. Data collection module 108 may further communicate with data modeling module 107 or repository 104 to populate data into data model 105 stored therein.
- data model 105 may be populated using data collected from a variety of data sources. However, data model 105 may not provide a complete representation of enterprise 50 .
- the sparseness of data model 105 e.g., incompleteness of data with respect to elements of the enterprise architecture 50
- the sparseness of data model 105 may be attributed to any number of factors, including human errors, incorrect or missing data, poor communication between computers and other network devices, etc.
- manual data entry is subject to human errors in finding the information and entering the data correctly
- automated data collection is subject to proper connectivity and interface compatibility
- sending requests for data may be subject to proper passwords or authentication.
- data model 105 of the enterprise 50 may be applied to the management and analysis of the enterprise 50 .
- the management and analysis of data may involve the calculation of a metric of interest.
- metrics may include, for example, the cost of an asset within the enterprise, the impact of asset on the functioning of an enterprise, or any other metric which can be calculated using the components and relationships of the data model.
- one particularly useful application of data model 105 is the calculation of the metric of interest of cost.
- the cost of various assets that comprise enterprise 50 can be calculated, where the calculation of the cost of any particular asset takes into account not only the direct dependencies and costs of that particular asset, but the indirect dependencies and costs of that asset as well.
- the dependency chains for one or more components of data model 105 can be discovered and a dependency map created. Using the costs associated with the components in the dependency chains of a particular component, the cost of that particular component can be calculated.
- FIG. 4 depicts a diagram illustrating one embodiment of enterprise 50 coupled via network 90 to system 100 as shown in FIG. 1 and described above, and includes metric calculation system 501 having a processor and set of instructions executable to communicate with repository 104 and network 90 , and further includes metric calculation module 505 .
- metric calculation module 505 may communicate with repository 104 to access data model 105 , may communicate with computer 101 to access data model 105 , or otherwise have access to components and relationships in data model 105 representing enterprise 50 .
- Metric calculation module 505 may utilize data model 105 to evaluate an aspect of enterprise 50 by calculating a metric of interest related to one or more components or relationships of the data model 105 . Evaluating an aspect of enterprise 50 may involve determining and assigning costs or revenues to assets of the enterprise 50 , determining the effects of a change to enterprise 50 , or the like as described above. Costs may include direct financial costs, or may be expressed in terms of man-hours, energy usage, or some other aspect. Similarly, revenues may include direct financial revenues, or may be expressed in terms of savings, investments, etc.
- FIG. 5 a representation 900 of an exemplary data model of an enterprise which will be used in conjunction with various descriptions of the embodiments of the invention is depicted.
- Components 910 and 920 represent an SAP and a PeopleSoft database respectively.
- Components 930 , 940 and 950 represent application server applications, components 960 , 970 and 980 represent hardware servers and component 990 represents the physical location of a data center.
- Relationships 912 - 918 are directional “runs on” relationships (the direction of which is indicated by the arrow). Relationship 912 represents that the SAP database represented by component 910 executes on the application server represented by component 930 .
- relationship 914 represents that the SAP database represented by component 910 executes on the application server represented by component 940
- relationship 916 represents that the PeopleSoft database represented by component 920 executes on the application server represented by component 940
- relationship 918 represents that the PeopleSoft database represented by component 920 executes on the application server represented by component 950 .
- Relationships 922 - 926 are also directional “runs on” relationships. Relationship 922 represents that the application server represented by component 930 executes on the hardware server represented by component 960 . Similarly, relationship 924 represents that the application server represented by component 940 executes on the hardware server represented by component 970 and relationship 926 represents that the application server represented by component 950 executes on the hardware server represented by component 980 .
- Relationships 932 - 936 may be directional “located in” relationships, such that relationship 932 represents that the hardware server represented by component 960 is located in the data center represented by component 990 ; relationship 934 represents that the hardware server represented by component 970 is located in the data center represented by component 990 and relationship 936 represents that the hardware server represented by component 980 is located in the data center represented by component 990 .
- determining a metric of interest such as the cost of most assets corresponding to components in a data model depends not only on the direct cost of the asset represented by that component, but also includes at least a portion of the cost of the other assets on which it depends.
- the total cost of the SAP database represented by component 910 may encompass: the direct cost of the SAP database represented by component 910 and some part of the total cost of the application servers represented by components 930 and 940 .
- the costs of the application server represented by component 930 in turn includes the direct cost of the application server represented by component 930 and some part of the cost of the server represented by component 960 .
- the costs of the application server represented by component 940 in turn includes the direct cost of the application server represented by component 940 and some part of the cost of the server represented by component 970 .
- the cost of the servers represented by components 960 and 970 likewise includes the direct cost of these servers, and some portion of the cost of the data center represented by component 990 .
- the total cost of the SAP data base represented by component 910 includes some portion of the cost of the application servers represented by components 930 and 940 , some portion of the cost of the hardware servers represented by components 960 and 970 , and some portion of the cost of the data center represented by component 990 .
- FIG. 6 presents one embodiment of a methodology for determining the dependencies and the metric of interest of cost for components of data model 105 .
- a dependency map may be generated from data model 105 .
- This dependency map may then be applied, at step 1020 , to a cost structure to generate a metric of interest (e.g., cost in this example) for a particular component of data model 105 at step 1030 .
- a metric of interest e.g., cost in this example
- data model 105 may be analyzed to generate a set of first level dependencies for one or more components in data model 105 .
- first level dependencies for a component a set of relationships associated with the component is evaluated to determine if the relationship indicates dependency on another component by analyzing the directionality of the relationship. If the relationship indicates that the component is dependent on another component, the relationship may be further analyzed to see if it is a cost conferring relationship. This analysis may be accomplished by comparing the relationship against a set of relationships which have been designated as cost conferring relationships. If the relationship is a cost conferring relationship indicating dependency on another component this dependency may be indicated in the set of first level dependencies for that component.
- each of relationships 912 and 914 is evaluated to determine if these relationships 912 , 914 indicate that component 910 is dependent on other components, and whether these are cost conferring relationships.
- relationships 912 and 914 are both directional “runs on” relationships it will be indicated that the first level dependencies of component 910 are components 930 and 940 .
- the evaluation of a data model to determine first level dependencies results in a set of tables, with the tables indicating the first level dependencies of some set or subset of the components in the data model.
- FIG. 7 depicts an example of a set of tables indicating the first level dependencies of each component in the data model of FIG. 5 . More specifically, table 1110 indicates the first level dependencies of component 910 ; table 1120 indicates the first level dependencies of component 920 ; table 1130 indicates the first level dependencies of component 930 ; table 1140 indicates the first level dependencies of component 940 ; etc.
- the total cost of a component can be apportioned among the components that depend on that component.
- each relationship associated with that component may be evaluated to determine if the relationship indicates that another component is dependent on the component by analyzing the directionality of the relationship. If the relationship indicates that another component is dependent on the component, the relationship may be further analyzed to see if it is a cost conferring relationship.
- the cost of a component is apportioned evenly between all relationships that indicate dependency on that component and are cost conferring.
- each of relationships 914 and 916 is evaluated to determine if these relationships 914 , 916 indicate that other components are dependent on component 940 , and whether these are cost conferring relationships.
- relationships 914 and 916 are both directional “runs on” relationships both of these relationships 914 , 916 fulfill that criteria, and the cost of component 940 may be apportioned evenly between relationships 914 , 916 .
- cost apportionments may be associated with cost conferring relationships in data model 105 .
- FIG. 8 depicts a representation of the above methodology applied to the data model of FIG. 5 .
- each relationship 912 , 914 , 916 , 918 , 922 , 924 , 926 , 932 , 934 and 936 has a percentage associated with it.
- This percentage which may be called an attribution percentage, indicates the proportion of the cost of a component which should be attributed to another component when calculating the cost of the other component.
- the percentage associated with relationship 934 indicates that 33% of the cost of the data center represented by component 990 should be attributed to the server represented by component 970 .
- the percentage cost of one component which should be attributed to another component may be assigned or associated with a relationship at an earlier point, such as when the relationship is instantiated. These percentages may then be used instead of proportioning the cost of a component equally between relationships associated with the component.
- This approach may be problematic, however, as enterprise architectures tend to be fluid entities. Thus, the data models that represent these enterprise architectures tend to be fluid as well. Occasionally, as a result of these changes the percentages originally associated with relationships may not account for 100% of the cost of a component. In this case, the percentages assigned to the relationships for a various component may still be used to apportion the full cost of that component, however, these percentages will be scaled to account for the full cost of the component.
- relationship 914 indicates that 30% of the cost of the server represented by component 940 should be apportioned to component 910
- relationship 916 indicates that 20% of the cost of the server represented by component 940 should be apportioned to component 920 .
- these percentages may be scaled to account for 100% of the cost.
- the percentage associated with relationship 914 may be scaled up to 60% and the percentage associated with relationship 916 may be scaled up to 40%.
- the same process may be applied to scale down percentages that account for greater than 100% of the cost of an asset.
- tables 1110 - 1190 of first level dependencies may be used to determine all the dependencies either direct or indirect for one or more of the components in the data model.
- the determination of these dependencies may be determined by running a graph traversal algorithm on the data model, or alternatively, on tables 1110 - 1190 representing the first level dependencies of components in the data model to create a dependency map for the component or the graph traversal algorithm may determine all the dependencies of one or more components.
- the graph traversal algorithm may also determine the proportion of the cost of each various components on which a component is dependent that should be apportioned to the component based on the data model.
- the graph traversal algorithm may start at a component for which it is desired to determine the cost. It can then find each component on which the component depends in the first degree by following the relationships associated with the component, and calculate the percentage cost that should be apportioned from each of those first degree components to the component. From these first degree components, components on which the component depend in the second degree may be found by following the relationships from each of the first degree components to the second degree components, and the percentage cost that should be apportioned from each of these second degree components to the component calculated. This percentage may be calculated for a second degree component by multiplying the percentage associated with the relationship linking the second degree component to a first degree component with the percentage linking the first degree component with the component itself. This graph traversal mechanism may similarly continue until every component on which the original component depends is found, and the percentage of the cost of every component on which the component depends to apportion to the original component is determined.
- the graph traversal algorithm may start at component 910 and determine that component 910 is dependent on components 930 and 940 , additionally the graph traversal algorithm may determine that 100% of the cost of component 930 should be apportioned to component 910 , while 50% of the cost of component 940 should be apportioned to component 910 .
- the graph traversal algorithm may then find the second degree dependencies of component 910 by finding the dependencies of component 930 and 940 .
- the graph traversal algorithm finds that component 930 depends on component 960 .
- component 910 depends on component 960 in the second degree.
- the graph traversal algorithm may then find the third degree dependencies of component 910 by finding the dependencies of component 960 and 970 .
- the graph traversal algorithm finds that component 960 depends on component 990 .
- component 910 depends on component 990 in the third degree.
- the graph traversal algorithm may find that component 970 depends on component 990 .
- component 910 depends on component 990 in the third degree.
- the graph traversal algorithm may attempt to find the fourth degree dependencies by finding the dependencies of component 990 , however, upon finding that component 990 has no dependencies the graph traversal algorithm may cease.
- FIG. 9 a representation of the dependency map determined by the graph traversal mechanism applied with respect to the data model of representation 900 and the percentages of the example depicted in FIG. 8 is illustrated.
- Each entry in table 1300 illustrates each of the independent cost chains originating with component 910 , and the percentage of the cost of the last component in the chain that should be attributed to component 910 when calculating the cost of the asset represented by component 910 , also known as the attributable cost.
- row 1310 indicates that 16.5% of the cost of the asset represented by component 990 (a data center) should be apportioned to the asset represented by component 910 (SAP database) when calculating the cost of the asset represented by component 910 .
- SAP database asset represented by component 910
- the cost of an asset in an enterprise 50 may be determined using the data model 105 of that enterprise 50 . It should be noted again that while cost is given as an example of a metric of interest that may be calculated, many other metric of interest may be calculated using the data model 105 . For example, a metric of interest of impact may also be calculated as described in U.S. Pat. No. 7,664,712, hereby incorporated herein fully by reference.
- relationship 942 may create a cycle such that the graph traversal algorithm may enter a loop, or may apportion the cost of various components more than once.
- the graph traversal algorithm may maintain a record of the components which have been visited during a traversal from a component, such that if a component is reached twice this may be accounted for, for example by ignoring that particular dependency chain.
- FIG. 11 illustrates one embodiment of a cost model for the enterprise represented by the data model of FIG. 5 .
- Table 1500 contains each asset, the cost of each asset and the component representing each asset. It will be understood that these costs may be determined by a variety of means, such as empirical evidence, cost projections or estimates, actual cost for hardware etc., and that these costs may be updated on a variety of time tables, and may refer to periodic costs, fixed costs etc.
- the costs in table 1500 may be applied to a dependency map generated from a data model to generate the cost for a particular asset.
- FIG. 12 represents the results of the application of the cost model of table 1500 to the dependency map for component 910 , an embodiment of which is depicted in FIG. 9 .
- the percentage of the cost of the asset represented by the last component in the dependency chain is multiplied by the cost of the asset represented by the last component.
- These attributable costs 1620 can then be summed to generate a total cost attributable to the asset represented by component 910 .
- a common problem with calculations of metrics of interest may be the data, or the lack thereof, in the data model being used to calculate such a metric of interest.
- the results shown in FIG. 12 do not reflect if the data used to calculate the cost of an asset is complete, as there may be additional components not captured in data model 105 , or some other error that reduces data completeness.
- data is not centralized but instead exists in diverse data sources and locations, for example in Tivoli and SMS applications, in spreadsheets, in diagrams, in modeling tools, etc. Much of the data in these various data sources is overlapping and frequently conflicting. Because data is stored in diverse data sources and locations, it may not be easily accessible.
- Data completeness or a data completeness measure may refer to a ratio or other measure of data that could be used to calculate a metric of interest if it was present and data that actually is present in a data model
- the process of extracting data to a central database can consume large amounts of computational resources, the process has the potential to prevent other processes, program or users from receiving computational resources adequate for their processing requirements, effectively limiting the use of the database or the computer system running the database.
- a central feature of Business Intelligence systems is the ability to generate calculated values from raw data, for example sums or other arithmetic aggregation of detailed data elements.
- raw data can be incomplete, which aggregating calculations often tolerate readily.
- DC level of data completeness
- a total cost to an attribute i.e., $760,000
- the lack of complete data undermines the reliability of the calculated result, but the result by itself does not allow the consumer to assess its reliability.
- a standard approach to this problem is to implement a supplemental calculation whose sole purpose is to evaluate DC.
- This DC calculation is developed in tandem with the calculation of interest, and must typically traverse the same raw data model performing different arithmetic. In a SQL-based system this generally requires multiple additional queries to a database.
- an end user might develop paired formulas: one to perform a calculation and another to assess the DC of that calculation. These formulas would also require separate access to the same data.
- a user may request a report on a metric of interest, and a set of calculations may be executed relative to the data, and the results of the report may be incorrect or calculated based on incomplete data, but the user might not be aware of the error lack of accuracy resulting from the incomplete data.
- reports may be run on insufficient data without the user's knowledge, or the relationships that allow the data model to be analyzed may not be established properly, or the attributes have not been populated, or there may be properties assigned to only a few components of the data model, etc. Any of these permutations or any combination may result in poor data completeness.
- a user may request a report on a metric of interest, where that report is segmented according to certain criteria. For example, a user may request a report on the cost of servers segmented according to department. Thus, a user may want a report of the cost of servers in HR, the cost of servers in IT, etc. As discussed above, because the completeness of data across an enterprise and in a data model representing that enterprise may vary widely, the completeness of data with respect to each of the segments a user desires may vary widely. Continuing with the above example the completeness of data used to calculate the cost of HR servers might be 90% while the completeness of data using to calculate the cost of servers in IT might be 25%, etc.
- 90% of the components representing servers in HR may have had a value for a cost property associated with them, while 10% of the components representing servers in HR may have had no value for the cost associated with the component. Accordingly, only the value of cost associated with 90% of the servers in HR was used to calculate the cost reported to the user.
- 25% of the components representing servers in IT may have had a value for a cost property associated with them, while 75% of the components representing servers in HR may have had no value for the cost associated with the component. Accordingly, only the value of cost associated with 25% of the servers in IT was used to calculate the cost reported to the user.
- a user's evaluation of the reliability of the cost calculated for the servers of HR and the servers of IT may be severely affected based on the data completeness measure reported for the calculation of the metric of interest of cost in this instance.
- FIG. 13 depicts a diagram illustrating the enterprise architecture 50 coupled via network 90 to system 100 including data completeness system 1301 executing a set of instructions, where data completeness system further includes data completeness module 1305 .
- Data completeness module 1305 may communicate with one or more of repository 104 , computer 101 , and metric calculation module 505 to receive information useful for performing a data completeness analysis.
- Data completeness module 1305 may evaluate data model 105 to determine a measure of the completeness (data completeness measure) of data model 105 or portions of data model 105 corresponding to a metric of interest calculation being performed by metric calculation module 505 , the completeness of any calculation based on data model 105 , or both.
- the measure of data completeness may provide a level of confidence to a user that a calculation for a metric of interest is accurate or provide the ability to evaluate the probative value of such a metric of interest.
- a user at user computer 150 may request an analysis of a metric of interest relating to an enterprise.
- Metric calculation module 505 is configured to access data model 105 and calculate such a metric of interest.
- a metric of interest may be directed to costs or to revenues.
- a metric of interest may relate to internal concerns of an enterprise, such as the cost of running business applications, manufacturing processes, etc., or to external concerns, such as how profitable certain customers are for the enterprise.
- Other metrics of interest may include impact of an asset on the enterprise, indirect costs, such as energy usage, indirect revenues, such as savings.
- Other metrics of interest may also be imagined.
- an enterprise may want to analyze their customer base to see how much revenue the enterprise is earning from each customer and assess the revenue earned against how much the customer costs the enterprise.
- an enterprise may want to perform a calculation for a metric of interest called “customer score” that takes into account information in order to allow marketing and other selling efforts to be targeted to high-value customers.
- a metric of interest might reflect how capable are they to spend more (considering household income), what is the order history, how recently have they ordered, how active are they, how profitable they have been, what is the profit margin on the products ordered, how often have orders been returned, how much expense is involved with returns to keep the customer happy, etc.
- a customer may purchase high-margin items but require a lot of assistance, or may frequently return items, etc.
- a set of calculations for a metric of interest may include determining how much revenue is earned from the customer, such as by determining the unit cost for a product, subtracting the unit cost from the sale price, and multiplying the result by the number of products purchased.
- Other calculations may be performed. For example, a summary calculation may be used for determining an average price for a repeat customer buying the same item at different times of the year in which seasonal changes in price may occur.
- Embodiments of system 100 may receive the request for the determination of a metric of interest and provide the request to metric calculation module 505 .
- Metric calculation module 505 may be configured to determine a component type in data model 105 with which to start its calculation of the metric of interest (e.g., all components representing customers). Using these root nodes, the data model 105 may be traversed or otherwise navigated by metric calculation module 505 to obtain the data needed to calculate the metric of interest (if such data is present) and the metric of interest calculated.
- Data completeness module 1305 may be configured to calculate a data completeness measure.
- data completeness module 1305 may be configured to calculate a data completeness measure corresponding to the metric of interest being calculated by metric calculation module 505 based on the data in data model. More particularly, in certain embodiments, as metric calculation module 505 traverses or otherwise navigates the data model 105 to obtain data for the calculation of the metric of interest, data completeness module 1305 may traverse the same path to determine if such data is actually present in the data model 105 (e.g., if a component is present, if a property or description of a component is present, etc.) and a data completeness measure calculated based on the presence or absence of such data.
- the additional analysis for determining data completeness may involve identifying all the unique paths through the data model that originate at the root node, decomposing each path into a set of steps, for each step determining what ratio of data points resulted in a value, determining an aggregate DC ratio for each unique path, and aggregating the ratios for all paths.
- FIG. 14 depicts a flow diagram depicting one embodiment for determining data completeness for data calculations that may calculate a metric of interest. Such steps may, for example, be performed by metric calculation module 505 , data completeness module 1305 or both.
- a request is received by system 100 , which may be part of an enterprise portfolio management (EPM) analysis system. Such a request may request the calculation of a metric of interest.
- EPM enterprise portfolio management
- the request may be in the form of a SQL request.
- a SQL query may specify “select sum of cost from customers purchase orders” to specify that the user wants to find out the total cost associated with purchase orders.
- a query may be formed in SQL or in a proprietary language.
- U.S. patent application Ser. No. 10/803,133, filed Mar. 17, 2004, by Miller et al. entitled “Method and System For Querying an Applied Data Model” is one example of a proprietary query language and is hereby incorporated by reference.
- the request may be input by a user through an interface provided at user computer 150 such as those known in the art, including web based interfaces or command line interfaces.
- Such a request may specify a metric of interest and any additional criteria.
- a request may specify that it is desired to calculate the metric of interest of customer score for customers in Texas.
- system 100 may analyze the request to identify what data may be needed to calculate the metric of interest or a measure of data completeness associated with the metric of interest.
- a root node and any paths based on the root node may be identified.
- the determination of a root node may involve identifying all possible nodes and then identifying the root node from the possible nodes, or the root node may be determined by some other criteria or process.
- determining a root node may involve identifying a component in data model 105 that could be a root node based on the metric of interest.
- a root node is generally a component type (or a subset of component type) or property of data model 105 from which navigation or traversal of data model 105 may begin when calculating a metric of interest or a data completeness measure. For example, a request to calculate a customer score for customers living in Texas may utilize the subset of the “Customer” component type that have “Texas” in the property of shipping address as a root node.
- Each path associated with the calculation of the metric of interest may be identified based on the root node.
- a path may include an ordered set of component types or properties where the first component type or property is the root node and the last component type or property of the path is a component type or property that comprises data that may be used to calculate the metric of interest, such that by navigating or traversing the data model 105 according to the path (e.g., starting at the root node, and accessing each of the component types or properties in order) the data may be obtained.
- each path identified in step 1815 may be decomposed into steps.
- Each step is an ordered pair of the component types or properties of the path. For example, if a path comprises component types or properties 1 ⁇ 2 ⁇ 3 ⁇ 4, the steps of that path would be 1 ⁇ 2, 2 ⁇ 3 and 3 ⁇ 4.
- a process for decomposing paths into steps may involve identifying a component type or property in the path, determining the next component type or property in the ordered set comprising the path and, in some cases, determining one or more relationships.
- determining relationships between component may involve determining specific relationship types.
- a component may have multiple relationships corresponding with various relationship types. For example, a customer may have been referred by another customer and might also have referred another customer.
- the component-type sequence may be customer-to-customer, but the paths or steps may differ for metric calculations and data completeness assessments.
- a data completeness ratio may be determined for each step of each path.
- This data completeness ratio for a step may be determined based on the two component types or properties comprising the step.
- Such a data completeness ratio may be a binary measure (e.g., a 1 if a later ordered component of the component type of the path is present and a 0 if it is not present); a fraction or ratio (e.g., a ratio of how many of the components of the later ordered component type of the path have a value for the desired property over how many components of the later ordered component type of the path do not have such a value); or some other ratio or measure altogether.
- system 100 may access data model 105 containing the data and begin navigating or traversing (collectively referred to as traversing) data model 105 to obtain data (e.g., associated with calculation of the requested metric of interest, or the data completeness measure).
- Data model 105 may have multiple nodes (e.g. components or component types) and relationships, such that data model 105 may, in some embodiment, resemble a form of a graph. Accordingly, an efficient traversal system and method may be beneficial to ensuring all data necessary for the analysis is gathered, but without gathering unnecessary data. For example, if a user wants to analyze purchases for customers in Texas and the data model covers a global enterprise, only data for all customers in Texas should be included.
- 7,523,128 entitled “Method and System for Discovering Relationships” is one example of a method for traversing a data structure and is hereby incorporated by reference.
- a query may be formed in a common language such as SQL or a proprietary or custom language.
- embodiments may be compatible with SparQL. Traversal of data model 105 to perform the analysis of data model 105 and a calculation of a data completeness measure corresponding to the metric of interest follow the same path(s).
- system 100 may gather and analyze data per the request. More specifically, as discussed above, each of the paths determined above may be a path that is traversed when obtaining data from the data model 105 in order to calculate the metric of interest. More specifically, as may be realized after a reading of the disclosures herein, there may be many components of a particular component type in the data model 105 , where the components of the data model 105 represent instances of an entity represented by that component type in enterprise architecture 50 . For example, enterprise architecture may have many customers. Each of those customers may be represented by a component of data model 105 which is an instance of the component type “Customer”.
- the data model 105 may include one component of type “Customer” for each customer of enterprise architecture 50 .
- each component that is an instance of the type (or subset) of the root node of the path may be determined and for each of these components the data model 105 may be traversed according to the ordered component types or properties specified in the path.
- step 1835 may be performed in parallel with step 1840 .
- system 100 may also be determining a data completeness measure, obviating the need to access the data model 105 a second time to calculate such a data completeness measure.
- data may be aggregated to form a data completeness measure.
- each of the data completeness ratios determined for each step of a path may be aggregated to form a data completeness measure for each path.
- a data completeness measure for a path may, for example, be determined by multiplying the data completeness ratios determined for each of step the path.
- the data completeness measures determined for each of the paths may then be aggregated to form a data completeness measure for the instance. While any suitable aggregation calculation may be utilized such as a minimum or weighted average, in one embodiment, an arithmetic mean of the data completeness measures for each path may be determined and this arithmetic mean used as the data completeness measure for that particular instance of the root node.
- the data completeness measure determined above is a data completeness measure determined for a component that is one instance of the component type that is the root node.
- enterprise architecture may have many customers. Each of those customers may be represented by a component of data model 105 which is an instance of the component type “Customer”.
- the data model 105 may include one component of type “Customer” for each customer of enterprise architecture 50 .
- an instance data completeness measure may be determined when traversing data model 105 according to the paths determined above starting with one instance of a “Customer” component.
- each of the instance data completeness measures determined for each instance of the root node may be aggregated (e.g., by taking a arithmetic mean, weighted average, normalization, etc.) in order determine an overall data completeness measure that is associated with a metric of interest.
- the overall data completeness measure associated with a metric of interest may be determined by accessing the data model 105 substantially in tandem with any access needed to calculate a metric of interest, but additionally, the overall data completeness measure accurately reflects the completeness of the data used to calculate that metric of interest.
- the overall metric of interest determined according to embodiments disclosed herein will be a measure of the data completeness of the data used to calculate the “Customer Score” metric that is associated with all customers of enterprise architecture.
- the overall metric of interest determined according to embodiments disclosed herein will be a measure of the data completeness of only the data used to calculate the “Customer Score” metric that is associated with customers of enterprise architecture that live in “Texas.”
- a measure of data completeness may be a powerful tool for evaluating a metric of interest (or other points of interest, such as a data model, etc.), as it may accurately reflect the very data that was used to calculate that metric of interest.
- one or more data completeness measures may be returned, and presented to a user at user computer 150 .
- This data completeness measure may, in one embodiment, be presented to a user in conjunction with the determined metric of interest such that the user has a simple method of visually (or otherwise) associating the metric of interest with the data completeness measure for that metric of interest.
- FIG. 15 depicts graph 1900 of a portion of a data model, illustrating enterprise architecture being modeled using data model 105 .
- Customer 1910 , Purchases/Orders 1920 , Order Items 1930 , Product 1940 , Support Incidents 1950 , and Online reviews 1960 are objects, and Household Income 1912 , Date 1922 , Returned 1924 , Quantity 1932 , Production Cost 1942 , Unit Price 1944 , Incident Date 1952 , Time to resolution 1954 , (Online Review) Date 1962 , and Number of Stars 1964 may be component types for representing physical or logical entities in enterprise 50 .
- Customer 1910 may be a component type such that instances of Customer 1910 may be used to represent each customer of enterprise 50
- Purchases/Orders 1920 may be a component type such that instances of Purchases/Orders 1920 may be used to represent each purchase or order made by a customer of enterprise 50
- relationship 1911 may be a relationship type such that instances of Household Income 1912 may be associated with instances of Customer 1910 .
- Other relationships are depicted as lines connecting components shown in FIG. 15
- FIG. 16 depicts portions of graph 1900 decomposed into paths 2010 - 2055 corresponding to the components and relationships illustrated in FIG. 15 , with each path having an order and a group of components.
- path 2010 includes two component types, Customer 1910 and Household Income 1912 , and a single step corresponding to relationship 1911 , namely Customer ⁇ Household Income.
- an analysis of household incomes for customers may generally start by identifying customers (i.e., instances of component type 1910 ) and traversing data model 105 according to path 2010 to gather data about household income (i.e., instances of component type 1912 ), and may determine a data completeness measure for a household income property related to customers of enterprise 50 . In this example, if there are 1000 customers but only 500 provide information about a household income, the data completeness measure may be 50% (500/1000).
- FIG. 16 depicts several paths for a metric of interest, ranging from a simple path having a single step (i.e., path 2010 ) to more complex paths having multiple steps (i.e., paths 2030 and 2035 ). More detailed paths are possible.
- component types other than component type 1910 may be selected as a root node.
- calculation of a metric of interest related to production cost may include identifying Customer type 1910 as a root node, then determining path 2030 . Determining a data completeness measure for path 2030 may further include decomposing path 2030 into multiple steps through component types 1920 (e.g., Purchases/Orders), 1930 (e.g., Order Items), 1920 (e.g., Product 1940 ) and property 1942 (e.g., Production cost).
- FIG. 17 depicts path 2030 decomposed into four steps 2030 a - 2030 d.
- Step 2030 a depicts a step from “Customer” to “Purchases/Orders”
- step 2030 b depicts a step from “Purchases/Orders”, to “Order Items”
- step 2030 c depicts a step from “Order Items” to “Product”
- step 2030 d depicts a step from “Product” to “Production Cost.”
- data may be gathered for calculating a metric of interest. For example, data may be gathered regarding purchases/orders associated with the customers, order items included in the purchases/orders, products included as part of the order items, and production costs associated with the products.
- data completeness measures may be calculated regarding how many purchases/orders were gathered in comparison with how many purchases/orders were expected (e.g., step 2030 a ), how many order items were included in the purchases/orders as compared to how many were expected (e.g., step 2030 b ), how many products were included with the order items as compared with how many were expected (e.g., step 2030 c ), and how much were the production costs as compared with an expected production cost (e.g., step 2030 d ).
- a data completeness measure may be calculated, as the data structure is being traversed and data is being gathered for the requested analysis corresponding to a metric of interest, embodiments may gather information for determining a data completeness measure corresponding to the metric of interest.
- the data in the data model may be consolidated from multiple sources, and any part of the data model may be incomplete, including data not being present in the original source, data being lost during consolidation, incorrect paths, etc.
- the request may trigger system 100 to gather sales data.
- system 100 may be expecting sales data for all 24 months.
- system 100 may be operable to determine there should be a target number (e.g., 24 months of sales data for a 24 month request) and determine a data completeness measure based on this target number.
- a target number e.g., 24 months of sales data for a 24 month request
- an expected target count may be set and each record may be assessed relative to the target count.
- a data completeness measure may be assigned. For example, if average values are used in the data analysis for the metric of interest, a statistical confidence factor may be assigned.
- data from different parts of data model 105 may be compared to determine an expected number. For example, if a receiving department record indicates 10 products were received but a shipping department record only shows 9 were shipped, a data completeness measure of 90% may be determined. Additionally, this data completeness measure may be weighted more heavily because there is additional data to confirm the accuracy.
- a data completeness measure may be expressed in various formats. In some embodiments, a data completeness measure may be expressed as a percentage or fraction between 0 and 1. In some embodiments, a data completeness measure may be predetermined to be either 0 or 1 (binary). For example, a customer who purchases 1 item and a customer who purchased 1000 items are still customers, so a data completeness ratio related to customers might have either a 0 (for not being a customer) or a 1 (for being a customer). Also, it should be noted that there is a distinction between “unknown” and “zero”. In the former case, the information about purchase history might not have been collected from a system of record. This would result in a completeness of 0% at that step for all affected records. In the latter case the data might have been collected and is therefore at 100% for this step even if there are 0 records. Other data completeness measures are possible.
- FIGS. 18A-E depict a simple data model, a query directed to the data model, a set of step results for the data analysis, and a sample output for a data completeness associated with the data analysis.
- FIG. 18A there are four major applications (i.e., App 1 , App 2 , App 3 and App 4 ).
- An example of a major application may be a SAP database, and others are possible.
- Each major application may consist of software modules.
- Application 1 may consist of Software Modules 1 - 5
- Application 2 may run Software Module 6
- Application 3 may run Software Module 7 .
- Each software module may run on a product version.
- Software Module 2 may run on Oracle 10 for one purpose and Software Module 3 may run on Oracle 11 for a different purpose.
- Each software version is a version of a product.
- Oracle 10 and Oracle 11 are both versions of Oracle.
- data for Software Modules 2 and 3 of Application 1 is complete.
- Application 1 also may include Software Module 1 .
- Software Module 1 runs on “DB2 v 98.6” but there is no data indicating which product “DB2 v 98.6” is a version of, so there is a data completeness issue.
- Application 1 may include Software Modules 4 and 5 , but nothing is known about what software these are running on, or what version they are, or what platform they are running, etc.
- Applications 2 and 3 only indicate there each is running a software module (Software Module 6 and Software Module 7 , respectively), but again do not provide information about the name of the platform, what version of the software is being used, etc.
- Application 4 has no information.
- FIG. 18B depicts an example query for a metric of interest (i.e., identify all applications on a machine and further identify how many unique products each one runs on).
- a query such as depicted in FIG. 18 b
- a set of results corresponding to the metric of interest may indicate that there are four applications running (i.e., App 1 , App 2 , App 3 and App 4 ).
- App 1 corresponds to only one product (i.e., Oracle), and App 2 , App 3 and App 4 do not have enough information to answer the query.
- FIG. 18C depicts an example output for a data completeness measure corresponding to a query such as shown in FIG. 18 b , in which column A lists all applications returned to the query, Column B lists all known product versions with a known product, and Column C provides a data completeness measure corresponding to the results shown in Column B.
- App 1 has product versions with a known product (i.e., Oracle 10 running on Oracle, and Oracle 11 running on Oracle).
- FIGS. 18D and 18E depict an example output for a data completeness measure corresponding to a query such as shown in FIG. 18 b , with the various calculations included.
- Table 1810 shows portions of the calculations associated with App 1
- Tables 1820 , 1830 and 1840 similarly show portions of the calculations associated with App 2 , App 3 and App 4 , respectively.
- results from Tables 1810 , 1820 , 1830 and 1840 may be used to identify two products (Oracle 10 and Oracle 11 ) running on Oracle, and determine that the data completeness measure for App 1 is 40%, and may further indicate that there is not enough information regarding App 2 , App 3 , or App 4 to accurately identify distinct products each one runs on.
- FIG. 18F depicts another example output for a data completeness measure corresponding to a query such as shown in FIG. 18 b , illustrating how various calculations and elapsed times needed to perform portions of the data completeness calculations may be presented.
- a data completeness measure may be calculated at the same time a query is being performed for a metric of interest (i.e., the data completeness measure is being performed in real-time along with the calculation for the metric of interest).
- elapsed times for both the metric of interest and the corresponding data completeness measure may be returned simultaneously as another parameter.
- portions of system 100 may function as stand-alone elements or may be combined with other portions of system 100 .
- embodiments may be operable to provide a data completeness score independently, which may be useful for ensuring data completeness prior to any analysis of the enterprise architecture.
- a threshold may be defined such that if an analysis does not produce a predetermined minimum score, additional information may be retrieved from additional sources, a user may be alerted, or the like until the minimum DC score is achieved.
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/796,132 US9280581B1 (en) | 2013-03-12 | 2013-03-12 | Method and system for determination of data completeness for analytic data calculations |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/796,132 US9280581B1 (en) | 2013-03-12 | 2013-03-12 | Method and system for determination of data completeness for analytic data calculations |
Publications (1)
Publication Number | Publication Date |
---|---|
US9280581B1 true US9280581B1 (en) | 2016-03-08 |
Family
ID=55410451
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/796,132 Active 2033-08-08 US9280581B1 (en) | 2013-03-12 | 2013-03-12 | Method and system for determination of data completeness for analytic data calculations |
Country Status (1)
Country | Link |
---|---|
US (1) | US9280581B1 (en) |
Cited By (135)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160275469A1 (en) * | 2015-03-20 | 2016-09-22 | Winthrop Resources Corporation | Systems and methods for providing information technology on an as-used basis |
US20160343077A1 (en) * | 2015-05-18 | 2016-11-24 | Fmr Llc | Probabilistic Analysis Trading Platform Apparatuses, Methods and Systems |
WO2019055553A1 (en) * | 2017-09-12 | 2019-03-21 | Schlumberger Technology Corporation | Dynamic representation of exploration and/or production entity relationships |
US10601636B2 (en) * | 2016-11-04 | 2020-03-24 | Crosscode, Inc. | Method and system for architecture analysis of an enterprise |
US10726158B2 (en) | 2016-06-10 | 2020-07-28 | OneTrust, LLC | Consent receipt management and automated process blocking systems and related methods |
US10740487B2 (en) | 2016-06-10 | 2020-08-11 | OneTrust, LLC | Data processing systems and methods for populating and maintaining a centralized database of personal data |
US10754981B2 (en) | 2016-06-10 | 2020-08-25 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10762236B2 (en) | 2016-06-10 | 2020-09-01 | OneTrust, LLC | Data processing user interface monitoring systems and related methods |
US10769302B2 (en) | 2016-06-10 | 2020-09-08 | OneTrust, LLC | Consent receipt management systems and related methods |
US10769303B2 (en) | 2016-06-10 | 2020-09-08 | OneTrust, LLC | Data processing systems for central consent repository and related methods |
US10769301B2 (en) | 2016-06-10 | 2020-09-08 | OneTrust, LLC | Data processing systems for webform crawling to map processing activities and related methods |
US10776515B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10776517B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Data processing systems for calculating and communicating cost of fulfilling data subject access requests and related methods |
US10776518B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Consent receipt management systems and related methods |
US10776514B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Data processing systems for the identification and deletion of personal data in computer systems |
US10783256B2 (en) | 2016-06-10 | 2020-09-22 | OneTrust, LLC | Data processing systems for data transfer risk identification and related methods |
US10791150B2 (en) | 2016-06-10 | 2020-09-29 | OneTrust, LLC | Data processing and scanning systems for generating and populating a data inventory |
US10796260B2 (en) | 2016-06-10 | 2020-10-06 | OneTrust, LLC | Privacy management systems and methods |
US10798133B2 (en) | 2016-06-10 | 2020-10-06 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US10796020B2 (en) | 2016-06-10 | 2020-10-06 | OneTrust, LLC | Consent receipt management systems and related methods |
US10803200B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems for processing and managing data subject access in a distributed environment |
US10803199B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing and communications systems and methods for the efficient implementation of privacy by design |
US10803097B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US10803202B2 (en) | 2018-09-07 | 2020-10-13 | OneTrust, LLC | Data processing systems for orphaned data identification and deletion and related methods |
US10803198B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems for use in automatically generating, populating, and submitting data subject access requests |
US10805354B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance |
US10839102B2 (en) | 2016-06-10 | 2020-11-17 | OneTrust, LLC | Data processing systems for identifying and modifying processes that are subject to data subject access requests |
US10848523B2 (en) | 2016-06-10 | 2020-11-24 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US10846261B2 (en) | 2016-06-10 | 2020-11-24 | OneTrust, LLC | Data processing systems for processing data subject access requests |
US10846433B2 (en) | 2016-06-10 | 2020-11-24 | OneTrust, LLC | Data processing consent management systems and related methods |
US10853859B2 (en) | 2016-04-01 | 2020-12-01 | OneTrust, LLC | Data processing systems and methods for operationalizing privacy compliance and assessing the risk of various respective privacy campaigns |
US10853501B2 (en) | 2016-06-10 | 2020-12-01 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US10867072B2 (en) | 2016-06-10 | 2020-12-15 | OneTrust, LLC | Data processing systems for measuring privacy maturity within an organization |
US10867007B2 (en) | 2016-06-10 | 2020-12-15 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10873606B2 (en) | 2016-06-10 | 2020-12-22 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US10878127B2 (en) | 2016-06-10 | 2020-12-29 | OneTrust, LLC | Data subject access request processing systems and related methods |
US10885485B2 (en) | 2016-06-10 | 2021-01-05 | OneTrust, LLC | Privacy management systems and methods |
US10896394B2 (en) | 2016-06-10 | 2021-01-19 | OneTrust, LLC | Privacy management systems and methods |
US10909265B2 (en) | 2016-06-10 | 2021-02-02 | OneTrust, LLC | Application privacy scanning systems and related methods |
US10909488B2 (en) | 2016-06-10 | 2021-02-02 | OneTrust, LLC | Data processing systems for assessing readiness for responding to privacy-related incidents |
US10929559B2 (en) | 2016-06-10 | 2021-02-23 | OneTrust, LLC | Data processing systems for data testing to confirm data deletion and related methods |
US10944725B2 (en) * | 2016-06-10 | 2021-03-09 | OneTrust, LLC | Data processing systems and methods for using a data model to select a target data asset in a data migration |
US10949170B2 (en) | 2016-06-10 | 2021-03-16 | OneTrust, LLC | Data processing systems for integration of consumer feedback with data subject access requests and related methods |
US10949565B2 (en) | 2016-06-10 | 2021-03-16 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US10970371B2 (en) | 2016-06-10 | 2021-04-06 | OneTrust, LLC | Consent receipt management systems and related methods |
US10970675B2 (en) | 2016-06-10 | 2021-04-06 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US10997318B2 (en) | 2016-06-10 | 2021-05-04 | OneTrust, LLC | Data processing systems for generating and populating a data inventory for processing data access requests |
US10997315B2 (en) | 2016-06-10 | 2021-05-04 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US11004125B2 (en) | 2016-04-01 | 2021-05-11 | OneTrust, LLC | Data processing systems and methods for integrating privacy information management systems with data loss prevention tools or other tools for privacy design |
US11023616B2 (en) | 2016-06-10 | 2021-06-01 | OneTrust, LLC | Data processing systems for identifying, assessing, and remediating data processing risks using data modeling techniques |
US11025675B2 (en) | 2016-06-10 | 2021-06-01 | OneTrust, LLC | Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance |
US11023842B2 (en) | 2016-06-10 | 2021-06-01 | OneTrust, LLC | Data processing systems and methods for bundled privacy policies |
US11030274B2 (en) | 2016-06-10 | 2021-06-08 | OneTrust, LLC | Data processing user interface monitoring systems and related methods |
US11038925B2 (en) | 2016-06-10 | 2021-06-15 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11057356B2 (en) | 2016-06-10 | 2021-07-06 | OneTrust, LLC | Automated data processing systems and methods for automatically processing data subject access requests using a chatbot |
US11074367B2 (en) | 2016-06-10 | 2021-07-27 | OneTrust, LLC | Data processing systems for identity validation for consumer rights requests and related methods |
US11087260B2 (en) | 2016-06-10 | 2021-08-10 | OneTrust, LLC | Data processing systems and methods for customizing privacy training |
US11100444B2 (en) | 2016-06-10 | 2021-08-24 | OneTrust, LLC | Data processing systems and methods for providing training in a vendor procurement process |
US11134086B2 (en) | 2016-06-10 | 2021-09-28 | OneTrust, LLC | Consent conversion optimization systems and related methods |
US11138242B2 (en) | 2016-06-10 | 2021-10-05 | OneTrust, LLC | Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software |
US11138299B2 (en) | 2016-06-10 | 2021-10-05 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11144622B2 (en) | 2016-06-10 | 2021-10-12 | OneTrust, LLC | Privacy management systems and methods |
US11146566B2 (en) | 2016-06-10 | 2021-10-12 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US11144675B2 (en) | 2018-09-07 | 2021-10-12 | OneTrust, LLC | Data processing systems and methods for automatically protecting sensitive data within privacy management systems |
US11151233B2 (en) | 2016-06-10 | 2021-10-19 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11157600B2 (en) | 2016-06-10 | 2021-10-26 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11188615B2 (en) | 2016-06-10 | 2021-11-30 | OneTrust, LLC | Data processing consent capture systems and related methods |
US11188862B2 (en) | 2016-06-10 | 2021-11-30 | OneTrust, LLC | Privacy management systems and methods |
US11200341B2 (en) | 2016-06-10 | 2021-12-14 | OneTrust, LLC | Consent receipt management systems and related methods |
US11210420B2 (en) | 2016-06-10 | 2021-12-28 | OneTrust, LLC | Data subject access request processing systems and related methods |
US11222142B2 (en) | 2016-06-10 | 2022-01-11 | OneTrust, LLC | Data processing systems for validating authorization for personal data collection, storage, and processing |
US11222309B2 (en) | 2016-06-10 | 2022-01-11 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US11222139B2 (en) | 2016-06-10 | 2022-01-11 | OneTrust, LLC | Data processing systems and methods for automatic discovery and assessment of mobile software development kits |
US11227247B2 (en) | 2016-06-10 | 2022-01-18 | OneTrust, LLC | Data processing systems and methods for bundled privacy policies |
US11228620B2 (en) | 2016-06-10 | 2022-01-18 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11238390B2 (en) | 2016-06-10 | 2022-02-01 | OneTrust, LLC | Privacy management systems and methods |
US11244367B2 (en) | 2016-04-01 | 2022-02-08 | OneTrust, LLC | Data processing systems and methods for integrating privacy information management systems with data loss prevention tools or other tools for privacy design |
US11277448B2 (en) | 2016-06-10 | 2022-03-15 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11294939B2 (en) | 2016-06-10 | 2022-04-05 | OneTrust, LLC | Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software |
US11295316B2 (en) | 2016-06-10 | 2022-04-05 | OneTrust, LLC | Data processing systems for identity validation for consumer rights requests and related methods |
US11301589B2 (en) | 2016-06-10 | 2022-04-12 | OneTrust, LLC | Consent receipt management systems and related methods |
US11301796B2 (en) | 2016-06-10 | 2022-04-12 | OneTrust, LLC | Data processing systems and methods for customizing privacy training |
US11308435B2 (en) | 2016-06-10 | 2022-04-19 | OneTrust, LLC | Data processing systems for identifying, assessing, and remediating data processing risks using data modeling techniques |
US11328092B2 (en) | 2016-06-10 | 2022-05-10 | OneTrust, LLC | Data processing systems for processing and managing data subject access in a distributed environment |
US11336697B2 (en) | 2016-06-10 | 2022-05-17 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11343284B2 (en) | 2016-06-10 | 2022-05-24 | OneTrust, LLC | Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance |
US11341447B2 (en) | 2016-06-10 | 2022-05-24 | OneTrust, LLC | Privacy management systems and methods |
US11354435B2 (en) | 2016-06-10 | 2022-06-07 | OneTrust, LLC | Data processing systems for data testing to confirm data deletion and related methods |
US11354434B2 (en) | 2016-06-10 | 2022-06-07 | OneTrust, LLC | Data processing systems for verification of consent and notice processing and related methods |
US11366786B2 (en) | 2016-06-10 | 2022-06-21 | OneTrust, LLC | Data processing systems for processing data subject access requests |
US11366909B2 (en) | 2016-06-10 | 2022-06-21 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11373007B2 (en) | 2017-06-16 | 2022-06-28 | OneTrust, LLC | Data processing systems for identifying whether cookies contain personally identifying information |
US11392720B2 (en) | 2016-06-10 | 2022-07-19 | OneTrust, LLC | Data processing systems for verification of consent and notice processing and related methods |
US11397819B2 (en) | 2020-11-06 | 2022-07-26 | OneTrust, LLC | Systems and methods for identifying data processing activities based on data discovery results |
US11403377B2 (en) | 2016-06-10 | 2022-08-02 | OneTrust, LLC | Privacy management systems and methods |
US11410106B2 (en) | 2016-06-10 | 2022-08-09 | OneTrust, LLC | Privacy management systems and methods |
US11416634B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Consent receipt management systems and related methods |
US11416109B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Automated data processing systems and methods for automatically processing data subject access requests using a chatbot |
US11416590B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11416798B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing systems and methods for providing training in a vendor procurement process |
US11418492B2 (en) * | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing systems and methods for using a data model to select a target data asset in a data migration |
US11416589B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11436373B2 (en) | 2020-09-15 | 2022-09-06 | OneTrust, LLC | Data processing systems and methods for detecting tools for the automatic blocking of consent requests |
US11438386B2 (en) | 2016-06-10 | 2022-09-06 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11444976B2 (en) | 2020-07-28 | 2022-09-13 | OneTrust, LLC | Systems and methods for automatically blocking the use of tracking tools |
US11442906B2 (en) | 2021-02-04 | 2022-09-13 | OneTrust, LLC | Managing custom attributes for domain objects defined within microservices |
US11461500B2 (en) | 2016-06-10 | 2022-10-04 | OneTrust, LLC | Data processing systems for cookie compliance testing with website scanning and related methods |
US11475136B2 (en) | 2016-06-10 | 2022-10-18 | OneTrust, LLC | Data processing systems for data transfer risk identification and related methods |
US11475165B2 (en) | 2020-08-06 | 2022-10-18 | OneTrust, LLC | Data processing systems and methods for automatically redacting unstructured data from a data subject access request |
US11481710B2 (en) | 2016-06-10 | 2022-10-25 | OneTrust, LLC | Privacy management systems and methods |
US11494515B2 (en) | 2021-02-08 | 2022-11-08 | OneTrust, LLC | Data processing systems and methods for anonymizing data samples in classification analysis |
US11520928B2 (en) | 2016-06-10 | 2022-12-06 | OneTrust, LLC | Data processing systems for generating personal data receipts and related methods |
US11526624B2 (en) | 2020-09-21 | 2022-12-13 | OneTrust, LLC | Data processing systems and methods for automatically detecting target data transfers and target data processing |
US11533315B2 (en) | 2021-03-08 | 2022-12-20 | OneTrust, LLC | Data transfer discovery and analysis systems and related methods |
US11544409B2 (en) | 2018-09-07 | 2023-01-03 | OneTrust, LLC | Data processing systems and methods for automatically protecting sensitive data within privacy management systems |
US11544667B2 (en) | 2016-06-10 | 2023-01-03 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US11546661B2 (en) | 2021-02-18 | 2023-01-03 | OneTrust, LLC | Selective redaction of media content |
US11562078B2 (en) | 2021-04-16 | 2023-01-24 | OneTrust, LLC | Assessing and managing computational risk involved with integrating third party computing functionality within a computing system |
US11562097B2 (en) | 2016-06-10 | 2023-01-24 | OneTrust, LLC | Data processing systems for central consent repository and related methods |
US11586700B2 (en) | 2016-06-10 | 2023-02-21 | OneTrust, LLC | Data processing systems and methods for automatically blocking the use of tracking tools |
US11586762B2 (en) | 2016-06-10 | 2023-02-21 | OneTrust, LLC | Data processing systems and methods for auditing data request compliance |
US11601464B2 (en) | 2021-02-10 | 2023-03-07 | OneTrust, LLC | Systems and methods for mitigating risks of third-party computing system functionality integration into a first-party computing system |
US11620142B1 (en) | 2022-06-03 | 2023-04-04 | OneTrust, LLC | Generating and customizing user interfaces for demonstrating functions of interactive user environments |
US11625502B2 (en) | 2016-06-10 | 2023-04-11 | OneTrust, LLC | Data processing systems for identifying and modifying processes that are subject to data subject access requests |
US11636171B2 (en) | 2016-06-10 | 2023-04-25 | OneTrust, LLC | Data processing user interface monitoring systems and related methods |
US11651104B2 (en) | 2016-06-10 | 2023-05-16 | OneTrust, LLC | Consent receipt management systems and related methods |
US11651402B2 (en) | 2016-04-01 | 2023-05-16 | OneTrust, LLC | Data processing systems and communication systems and methods for the efficient generation of risk assessments |
US11651106B2 (en) | 2016-06-10 | 2023-05-16 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US11675929B2 (en) | 2016-06-10 | 2023-06-13 | OneTrust, LLC | Data processing consent sharing systems and related methods |
US11687528B2 (en) | 2021-01-25 | 2023-06-27 | OneTrust, LLC | Systems and methods for discovery, classification, and indexing of data in a native computing system |
US11687657B2 (en) | 2020-07-08 | 2023-06-27 | Codelogic, Inc. | Systems and methods for software security analysis |
US11727141B2 (en) | 2016-06-10 | 2023-08-15 | OneTrust, LLC | Data processing systems and methods for synching privacy-related user consent across multiple computing devices |
US11748458B2 (en) | 2020-04-15 | 2023-09-05 | Codelogic, Inc. | Systems and methods for a governance engine |
US11775348B2 (en) | 2021-02-17 | 2023-10-03 | OneTrust, LLC | Managing custom workflows for domain objects defined within microservices |
US11797528B2 (en) | 2020-07-08 | 2023-10-24 | OneTrust, LLC | Systems and methods for targeted data discovery |
Citations (67)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5572732A (en) | 1992-02-14 | 1996-11-05 | Theseus Research, Inc. | Method and system for process expression and resolution including a general method of direct association |
US5845068A (en) | 1996-12-18 | 1998-12-01 | Sun Microsystems, Inc. | Multilevel security port methods, apparatuses, and computer program products |
US5968176A (en) | 1997-05-29 | 1999-10-19 | 3Com Corporation | Multilayer firewall system |
US6226792B1 (en) | 1998-10-14 | 2001-05-01 | Unisys Corporation | Object management system supporting the use of application domain knowledge mapped to technology domain knowledge |
US6292900B1 (en) | 1996-12-18 | 2001-09-18 | Sun Microsystems, Inc. | Multilevel security attribute passing methods, apparatuses, and computer program products in a stream |
US6442557B1 (en) | 1998-02-27 | 2002-08-27 | Prc Inc. | Evaluation of enterprise architecture model including relational database |
US20030009487A1 (en) | 2001-01-26 | 2003-01-09 | Senthil Prabakaran | Policy implementation |
US6509898B2 (en) | 1998-04-17 | 2003-01-21 | Xerox Corporation | Usage based methods of traversing and displaying generalized graph structures |
US6529909B1 (en) | 1999-08-31 | 2003-03-04 | Accenture Llp | Method for translating an object attribute converter in an information services patterns environment |
US20030088551A1 (en) | 2001-11-07 | 2003-05-08 | Wei Tong | Method and system for searching for drawing numbers |
US20030110253A1 (en) | 2001-12-12 | 2003-06-12 | Relicore, Inc. | Method and apparatus for managing components in an IT system |
US6611838B1 (en) | 2000-09-01 | 2003-08-26 | Cognos Incorporated | Metadata exchange |
US20030177481A1 (en) | 2001-05-25 | 2003-09-18 | Amaru Ruth M. | Enterprise information unification |
US20030187826A1 (en) | 2002-03-28 | 2003-10-02 | Ontario Corporation | Collection system database architecture |
US20030208367A1 (en) | 2002-05-02 | 2003-11-06 | International Business Machines Corporation | Flow composition model searching |
US20030212640A1 (en) | 2002-05-01 | 2003-11-13 | Hans Magnus Andresen | Universal product attribute modeler |
US6662188B1 (en) | 1999-09-03 | 2003-12-09 | Cognos Incorporated | Metadata model |
US20040002818A1 (en) | 2001-12-21 | 2004-01-01 | Affymetrix, Inc. | Method, system and computer software for providing microarray probe data |
US20040049509A1 (en) | 2002-09-11 | 2004-03-11 | International Business Machines Corporation | Methods and apparatus for managing dependencies in distributed systems |
US20040059943A1 (en) | 2002-09-23 | 2004-03-25 | Bertrand Marquet | Embedded filtering policy manager using system-on-chip |
US20040073655A1 (en) | 2002-10-09 | 2004-04-15 | Chao Kan | Packet sequence number network monitoring system |
US20040111513A1 (en) | 2002-12-04 | 2004-06-10 | Shen Simon S. | Automatic employment of resource load information with one or more policies to automatically determine whether to decrease one or more loads |
US20040225791A1 (en) | 2000-12-28 | 2004-11-11 | Keskar Dhananjay V. | System for finding data related to an example datum on two electronic devices |
US20040243835A1 (en) | 2003-05-28 | 2004-12-02 | Andreas Terzis | Multilayer access control security system |
US20040260706A1 (en) | 2002-07-20 | 2004-12-23 | Microsoft Corporation | Querying an object for properties |
US20050033762A1 (en) | 2003-04-05 | 2005-02-10 | Kasra Kasravi | System and method for quantitative assessment of organizational adaptability |
US20050138039A1 (en) | 2003-12-17 | 2005-06-23 | Hagen Robert L. | Method and system for tailoring metamodel requirements capture processing to varying users |
US20050203920A1 (en) | 2004-03-10 | 2005-09-15 | Yu Deng | Metadata-related mappings in a system |
US20060085837A1 (en) | 2004-10-14 | 2006-04-20 | Pesati Vikram R | Method and system for managing security policies for databases in a distributed system |
US20060106796A1 (en) | 2004-11-17 | 2006-05-18 | Honeywell International Inc. | Knowledge stores for interactive diagnostics |
US20060136437A1 (en) | 2004-12-21 | 2006-06-22 | Yasushi Yamasaki | System, method and program for distributed policy integration |
US7080077B2 (en) | 2000-07-10 | 2006-07-18 | Oracle International Corporation | Localized access |
US20060167927A1 (en) | 2001-05-25 | 2006-07-27 | Joseph Edelstein | Data query and location through a central ontology model |
US20060195575A1 (en) | 2000-12-22 | 2006-08-31 | Oracle International Corporation | Determining a user's groups |
US20060195460A1 (en) | 2005-02-28 | 2006-08-31 | Microsoft Corporation | Data model for object-relational data |
US7103171B1 (en) | 2001-06-29 | 2006-09-05 | Siebel Systems, Inc. | System and method for multi-channel communication queuing using routing and escalation rules |
US20060212487A1 (en) | 2005-03-21 | 2006-09-21 | Kennis Peter H | Methods and systems for monitoring transaction entity versions for policy compliance |
US7124180B1 (en) | 2000-04-27 | 2006-10-17 | Hewlett-Packard Development Company, L.P. | Internet usage data recording system and method employing a configurable rule engine for the processing and correlation of network data |
US20060253709A1 (en) | 2005-05-06 | 2006-11-09 | Pau-Chen Cheng | System and method for fuzzy multi-level security |
US20060277022A1 (en) | 2003-03-19 | 2006-12-07 | Roland Pulfer | Modelling a complex system |
US20060294148A1 (en) | 2005-06-22 | 2006-12-28 | Xavier Brunet | Network usage management system and method |
US7231661B1 (en) | 2001-06-21 | 2007-06-12 | Oracle International Corporation | Authorization services with external authentication |
US20070143604A1 (en) | 2005-12-15 | 2007-06-21 | Arroyo Diana J | Reference monitor system and method for enforcing information flow policies |
US20070180490A1 (en) | 2004-05-20 | 2007-08-02 | Renzi Silvio J | System and method for policy management |
US20070192415A1 (en) | 2001-03-31 | 2007-08-16 | Pak Wai H | Extensible interface for inter-module communication |
US20070255841A1 (en) | 2006-04-28 | 2007-11-01 | Microsoft Corporation | Authorizing service requests in multi-tiered applications |
US20070282916A1 (en) | 2006-05-09 | 2007-12-06 | Microsoft Corporation | State transition logic for a persistent object graph |
US20080120362A1 (en) | 2006-11-20 | 2008-05-22 | Microsoft Corporation | Single virtual client for multiple client access and equivalency |
US7409707B2 (en) | 2003-06-06 | 2008-08-05 | Microsoft Corporation | Method for managing network filter based policies |
US7428546B2 (en) | 2003-08-21 | 2008-09-23 | Microsoft Corporation | Systems and methods for data modeling in an item-based storage platform |
US7480798B2 (en) | 2003-06-05 | 2009-01-20 | International Business Machines Corporation | System and method for representing multiple security groups as a single data object |
US7512965B1 (en) | 2000-04-19 | 2009-03-31 | Hewlett-Packard Development Company, L.P. | Computer system security service |
US7523128B1 (en) | 2003-03-18 | 2009-04-21 | Troux Technologies | Method and system for discovering relationships |
US7533173B2 (en) | 2003-09-30 | 2009-05-12 | International Business Machines Corporation | Policy driven automation - specifying equivalent resources |
US7603547B2 (en) | 2003-10-10 | 2009-10-13 | Bea Systems, Inc. | Security control module |
US7644432B2 (en) | 2003-10-10 | 2010-01-05 | Bea Systems, Inc. | Policy inheritance through nested groups |
US7664712B1 (en) | 2005-08-05 | 2010-02-16 | Troux Technologies | Method and system for impact analysis using a data model |
US7669051B2 (en) | 2000-11-13 | 2010-02-23 | DigitalDoors, Inc. | Data security system and method with multiple independent levels of security |
US7822710B1 (en) | 2006-05-24 | 2010-10-26 | Troux Technologies | System and method for data collection |
US7890545B1 (en) | 2005-03-31 | 2011-02-15 | Troux Technologies | Method and system for a reference model for an enterprise architecture |
US8027956B1 (en) | 2007-10-30 | 2011-09-27 | Troux Technologies | System and method for planning or monitoring system transformations |
US8086615B2 (en) | 2005-03-28 | 2011-12-27 | Oracle International Corporation | Security data redaction |
US8214877B1 (en) | 2006-05-22 | 2012-07-03 | Troux Technologies | System and method for the implementation of policies |
US8234223B1 (en) | 2005-04-28 | 2012-07-31 | Troux Technologies, Inc. | Method and system for calculating cost of an asset using a data model |
US8386377B1 (en) * | 2003-05-12 | 2013-02-26 | Id Analytics, Inc. | System and method for credit scoring using an identity network connectivity |
US20130144796A1 (en) * | 2011-12-06 | 2013-06-06 | Fannie Mae | Assigning confidence values to automated property valuations by using the non-typical property characteristics of the properties |
US8635592B1 (en) | 2011-02-08 | 2014-01-21 | Troux Technologies, Inc. | Method and system for tailoring software functionality |
-
2013
- 2013-03-12 US US13/796,132 patent/US9280581B1/en active Active
Patent Citations (72)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5572732A (en) | 1992-02-14 | 1996-11-05 | Theseus Research, Inc. | Method and system for process expression and resolution including a general method of direct association |
US5845068A (en) | 1996-12-18 | 1998-12-01 | Sun Microsystems, Inc. | Multilevel security port methods, apparatuses, and computer program products |
US6292900B1 (en) | 1996-12-18 | 2001-09-18 | Sun Microsystems, Inc. | Multilevel security attribute passing methods, apparatuses, and computer program products in a stream |
US5968176A (en) | 1997-05-29 | 1999-10-19 | 3Com Corporation | Multilayer firewall system |
US6442557B1 (en) | 1998-02-27 | 2002-08-27 | Prc Inc. | Evaluation of enterprise architecture model including relational database |
US6509898B2 (en) | 1998-04-17 | 2003-01-21 | Xerox Corporation | Usage based methods of traversing and displaying generalized graph structures |
US6226792B1 (en) | 1998-10-14 | 2001-05-01 | Unisys Corporation | Object management system supporting the use of application domain knowledge mapped to technology domain knowledge |
US6529909B1 (en) | 1999-08-31 | 2003-03-04 | Accenture Llp | Method for translating an object attribute converter in an information services patterns environment |
US6662188B1 (en) | 1999-09-03 | 2003-12-09 | Cognos Incorporated | Metadata model |
US7512965B1 (en) | 2000-04-19 | 2009-03-31 | Hewlett-Packard Development Company, L.P. | Computer system security service |
US7124180B1 (en) | 2000-04-27 | 2006-10-17 | Hewlett-Packard Development Company, L.P. | Internet usage data recording system and method employing a configurable rule engine for the processing and correlation of network data |
US7080077B2 (en) | 2000-07-10 | 2006-07-18 | Oracle International Corporation | Localized access |
US6611838B1 (en) | 2000-09-01 | 2003-08-26 | Cognos Incorporated | Metadata exchange |
US7669051B2 (en) | 2000-11-13 | 2010-02-23 | DigitalDoors, Inc. | Data security system and method with multiple independent levels of security |
US20060195575A1 (en) | 2000-12-22 | 2006-08-31 | Oracle International Corporation | Determining a user's groups |
US20040225791A1 (en) | 2000-12-28 | 2004-11-11 | Keskar Dhananjay V. | System for finding data related to an example datum on two electronic devices |
US20030009487A1 (en) | 2001-01-26 | 2003-01-09 | Senthil Prabakaran | Policy implementation |
US20070192415A1 (en) | 2001-03-31 | 2007-08-16 | Pak Wai H | Extensible interface for inter-module communication |
US20030177481A1 (en) | 2001-05-25 | 2003-09-18 | Amaru Ruth M. | Enterprise information unification |
US20060167927A1 (en) | 2001-05-25 | 2006-07-27 | Joseph Edelstein | Data query and location through a central ontology model |
US7231661B1 (en) | 2001-06-21 | 2007-06-12 | Oracle International Corporation | Authorization services with external authentication |
US7103171B1 (en) | 2001-06-29 | 2006-09-05 | Siebel Systems, Inc. | System and method for multi-channel communication queuing using routing and escalation rules |
US20030088551A1 (en) | 2001-11-07 | 2003-05-08 | Wei Tong | Method and system for searching for drawing numbers |
US20030110253A1 (en) | 2001-12-12 | 2003-06-12 | Relicore, Inc. | Method and apparatus for managing components in an IT system |
US20040002818A1 (en) | 2001-12-21 | 2004-01-01 | Affymetrix, Inc. | Method, system and computer software for providing microarray probe data |
US20030187826A1 (en) | 2002-03-28 | 2003-10-02 | Ontario Corporation | Collection system database architecture |
US20030212640A1 (en) | 2002-05-01 | 2003-11-13 | Hans Magnus Andresen | Universal product attribute modeler |
US20030208367A1 (en) | 2002-05-02 | 2003-11-06 | International Business Machines Corporation | Flow composition model searching |
US20040260706A1 (en) | 2002-07-20 | 2004-12-23 | Microsoft Corporation | Querying an object for properties |
US20040049509A1 (en) | 2002-09-11 | 2004-03-11 | International Business Machines Corporation | Methods and apparatus for managing dependencies in distributed systems |
US20040059943A1 (en) | 2002-09-23 | 2004-03-25 | Bertrand Marquet | Embedded filtering policy manager using system-on-chip |
US20040073655A1 (en) | 2002-10-09 | 2004-04-15 | Chao Kan | Packet sequence number network monitoring system |
US20040111513A1 (en) | 2002-12-04 | 2004-06-10 | Shen Simon S. | Automatic employment of resource load information with one or more policies to automatically determine whether to decrease one or more loads |
US8789011B2 (en) | 2003-03-18 | 2014-07-22 | Troux Technologies, Inc. | Method and system for a generic data model |
US20100169380A1 (en) | 2003-03-18 | 2010-07-01 | Troux Technologies | Method and system for a generic data model |
US7698683B1 (en) | 2003-03-18 | 2010-04-13 | Troux Technologies | Adaptive system for dynamic object-oriented schemas |
US7558790B1 (en) | 2003-03-18 | 2009-07-07 | Troux Technologies | Method and system for querying an applied data model |
US7523128B1 (en) | 2003-03-18 | 2009-04-21 | Troux Technologies | Method and system for discovering relationships |
US20060277022A1 (en) | 2003-03-19 | 2006-12-07 | Roland Pulfer | Modelling a complex system |
US20050033762A1 (en) | 2003-04-05 | 2005-02-10 | Kasra Kasravi | System and method for quantitative assessment of organizational adaptability |
US8386377B1 (en) * | 2003-05-12 | 2013-02-26 | Id Analytics, Inc. | System and method for credit scoring using an identity network connectivity |
US20040243835A1 (en) | 2003-05-28 | 2004-12-02 | Andreas Terzis | Multilayer access control security system |
US7480798B2 (en) | 2003-06-05 | 2009-01-20 | International Business Machines Corporation | System and method for representing multiple security groups as a single data object |
US7757277B2 (en) | 2003-06-05 | 2010-07-13 | International Business Machines Corporation | System and method for representing multiple security groups as a single data object |
US7409707B2 (en) | 2003-06-06 | 2008-08-05 | Microsoft Corporation | Method for managing network filter based policies |
US7428546B2 (en) | 2003-08-21 | 2008-09-23 | Microsoft Corporation | Systems and methods for data modeling in an item-based storage platform |
US7533173B2 (en) | 2003-09-30 | 2009-05-12 | International Business Machines Corporation | Policy driven automation - specifying equivalent resources |
US7603547B2 (en) | 2003-10-10 | 2009-10-13 | Bea Systems, Inc. | Security control module |
US7644432B2 (en) | 2003-10-10 | 2010-01-05 | Bea Systems, Inc. | Policy inheritance through nested groups |
US20050138039A1 (en) | 2003-12-17 | 2005-06-23 | Hagen Robert L. | Method and system for tailoring metamodel requirements capture processing to varying users |
US20050203920A1 (en) | 2004-03-10 | 2005-09-15 | Yu Deng | Metadata-related mappings in a system |
US20070180490A1 (en) | 2004-05-20 | 2007-08-02 | Renzi Silvio J | System and method for policy management |
US20060085837A1 (en) | 2004-10-14 | 2006-04-20 | Pesati Vikram R | Method and system for managing security policies for databases in a distributed system |
US20060106796A1 (en) | 2004-11-17 | 2006-05-18 | Honeywell International Inc. | Knowledge stores for interactive diagnostics |
US20060136437A1 (en) | 2004-12-21 | 2006-06-22 | Yasushi Yamasaki | System, method and program for distributed policy integration |
US20060195460A1 (en) | 2005-02-28 | 2006-08-31 | Microsoft Corporation | Data model for object-relational data |
US20060212487A1 (en) | 2005-03-21 | 2006-09-21 | Kennis Peter H | Methods and systems for monitoring transaction entity versions for policy compliance |
US8086615B2 (en) | 2005-03-28 | 2011-12-27 | Oracle International Corporation | Security data redaction |
US7890545B1 (en) | 2005-03-31 | 2011-02-15 | Troux Technologies | Method and system for a reference model for an enterprise architecture |
US8234223B1 (en) | 2005-04-28 | 2012-07-31 | Troux Technologies, Inc. | Method and system for calculating cost of an asset using a data model |
US20060253709A1 (en) | 2005-05-06 | 2006-11-09 | Pau-Chen Cheng | System and method for fuzzy multi-level security |
US20060294148A1 (en) | 2005-06-22 | 2006-12-28 | Xavier Brunet | Network usage management system and method |
US7664712B1 (en) | 2005-08-05 | 2010-02-16 | Troux Technologies | Method and system for impact analysis using a data model |
US20070143604A1 (en) | 2005-12-15 | 2007-06-21 | Arroyo Diana J | Reference monitor system and method for enforcing information flow policies |
US20070255841A1 (en) | 2006-04-28 | 2007-11-01 | Microsoft Corporation | Authorizing service requests in multi-tiered applications |
US20070282916A1 (en) | 2006-05-09 | 2007-12-06 | Microsoft Corporation | State transition logic for a persistent object graph |
US8214877B1 (en) | 2006-05-22 | 2012-07-03 | Troux Technologies | System and method for the implementation of policies |
US7822710B1 (en) | 2006-05-24 | 2010-10-26 | Troux Technologies | System and method for data collection |
US20080120362A1 (en) | 2006-11-20 | 2008-05-22 | Microsoft Corporation | Single virtual client for multiple client access and equivalency |
US8027956B1 (en) | 2007-10-30 | 2011-09-27 | Troux Technologies | System and method for planning or monitoring system transformations |
US8635592B1 (en) | 2011-02-08 | 2014-01-21 | Troux Technologies, Inc. | Method and system for tailoring software functionality |
US20130144796A1 (en) * | 2011-12-06 | 2013-06-06 | Fannie Mae | Assigning confidence values to automated property valuations by using the non-typical property characteristics of the properties |
Non-Patent Citations (44)
Title |
---|
Cbop et al., "A UML Profile for Enterprise Distributed Object Computing-Joint Final Submission-Component Collaboration Architecture (CCA)," 169 pgs., OMG Document No. ad/Aug. 19, 2001, 2001, at http://enterprisecomponent.com/docs/EdocCCA.pdf. |
Du, W. et al., "XML Structures for Relational Data," Web Information Systems Engineering, 2001, Proceedings of the Second Int'l Conf. on (0-7965-1393-X), Dec. 3-6, 2001, vol. 1, pp. 151-160, at http://ieeexplore.ieee.org/stamp/stamp.jsp?isnumber+21506&arnumber=996476&punumber=7824. |
Gornik, D., "UML Data Modeling Profile," May 2002, Rational Software Corp., TP162, pp. i-ii, 1-11. |
Maloney, David, "E-manufacturing e'zing into factories: the potential is great for using the Internet to aid Manufacturing. Supply chain visibility, the wired plant, trading exchanges and data sharing are at the forefront," Modern Material Handling, vol. 57, n6, p. 21 (3), May 15, 2002. |
Muller, Robert, "Database Design for Smarties Using UML for Data Modeling," Morgan Kaufmann Publishers, 1999, 265 pgs. |
Notice of Allowance for U.S. Appl. No. 11/117,039, mailed Mar. 27, 2012, 15 pgs. |
Notice of Allowance for U.S. Appl. No. 11/805,002, mailed Mar. 2, 2012, 16 pgs. |
Notice of Allowance for U.S. Appl. No. 11/805,873, mailed Aug. 31, 2010, 6 pgs. |
Notice of Allowance for U.S. Appl. No. 11/929,157, mailed May 23, 2011, 17 pgs. |
Notice of Allowance for U.S. Appl. No. 13/022,778, mailed Sep. 12, 2013, 5 pgs. |
Notice of Allowance issued for U.S. Appl. No. 12/720,219, mailed Dec. 31, 2013, 6 pages. |
Office Action for U.S. Appl. No. 10/802,178 mailed Aug. 19, 2008, 9 pgs. |
Office Action for U.S. Appl. No. 10/802,178 mailed Mar. 3, 2008, 10 pgs. |
Office Action for U.S. Appl. No. 10/802,178 mailed Sep. 5, 2007, 11 pgs. |
Office Action for U.S. Appl. No. 10/802,304, mailed Aug. 4, 2009, 9 pgs. |
Office Action for U.S. Appl. No. 10/802,304, mailed Feb. 17, 2009, 12 pgs. |
Office Action for U.S. Appl. No. 10/802,304, mailed Jan. 9, 2008, 11 pgs. |
Office Action for U.S. Appl. No. 10/802,304, mailed Jun. 18, 2007, 9 pgs. |
Office Action for U.S. Appl. No. 10/802,304, mailed Jun. 30, 2008, 14 pgs. |
Office Action for U.S. Appl. No. 10/803,133 mailed May 28, 2008, 12 pgs. |
Office Action for U.S. Appl. No. 10/803,133 mailed Nov. 2, 2007, 10 pgs. |
Office Action for U.S. Appl. No. 10/803,133, mailed May 17, 2007, 11 pgs. |
Office Action for U.S. Appl. No. 10/803,133, mailed Oct. 4, 2006, 9 pgs. |
Office Action for U.S. Appl. No. 10/803,133, mailed Oct. 7, 2008, 14 pgs. |
Office Action for U.S. Appl. No. 11/095,323, mailed Aug. 10, 2007, 12 pgs. |
Office Action for U.S. Appl. No. 11/095,323, mailed Aug. 20, 2008, 13 pgs. |
Office Action for U.S. Appl. No. 11/095,323, mailed Aug. 28, 2009, 15 pgs. |
Office Action for U.S. Appl. No. 11/095,323, mailed Feb. 17, 2009, 14 pgs. |
Office Action for U.S. Appl. No. 11/095,323, mailed Mar. 1, 2010, 21 pgs. |
Office Action for U.S. Appl. No. 11/095,323, mailed Mar. 3, 2008, 16 pgs. |
Office Action for U.S. Appl. No. 11/117,039, mailed Aug. 17, 2009, 26 pgs. |
Office Action for U.S. Appl. No. 11/117,039, mailed Aug. 20, 2008, 19 pgs. |
Office Action for U.S. Appl. No. 11/117,039, mailed Feb. 12, 2009, 27 pgs. |
Office Action for U.S. Appl. No. 11/117,039, mailed Mar. 15, 2010, 28 pgs. |
Office Action for U.S. Appl. No. 11/198,649, mailed Apr. 29, 2008, 10 pgs. |
Office Action for U.S. Appl. No. 11/198,649, mailed Feb. 27, 2009, 11 pgs. |
Office Action for U.S. Appl. No. 11/805,002, mailed Feb. 2, 2011, 12 pgs. |
Office Action for U.S. Appl. No. 11/805,002, mailed Jul. 20, 2011, 18 pgs. |
Office Action for U.S. Appl. No. 11/805,873, mailed Mar. 15, 2010, 10 pgs. |
Office Action for U.S. Appl. No. 11/805,873, mailed Sep. 11, 2009, 9 pgs. |
Office Action for U.S. Appl. No. 11/929,157, mailed Jun. 6, 2010, 13 pgs. |
Office Action for U.S. Appl. No. 11/929,157, mailed Nov. 24, 2010, 12 pgs. |
Office Action for U.S. Appl. No. 12/720,219, mailed Aug. 14, 2012, 9 pgs. |
Office Action for U.S. Appl. No. 13/022,778, mailed Feb. 15, 2013, 8 pgs. |
Cited By (201)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160275469A1 (en) * | 2015-03-20 | 2016-09-22 | Winthrop Resources Corporation | Systems and methods for providing information technology on an as-used basis |
US20160343077A1 (en) * | 2015-05-18 | 2016-11-24 | Fmr Llc | Probabilistic Analysis Trading Platform Apparatuses, Methods and Systems |
US10853859B2 (en) | 2016-04-01 | 2020-12-01 | OneTrust, LLC | Data processing systems and methods for operationalizing privacy compliance and assessing the risk of various respective privacy campaigns |
US11651402B2 (en) | 2016-04-01 | 2023-05-16 | OneTrust, LLC | Data processing systems and communication systems and methods for the efficient generation of risk assessments |
US11244367B2 (en) | 2016-04-01 | 2022-02-08 | OneTrust, LLC | Data processing systems and methods for integrating privacy information management systems with data loss prevention tools or other tools for privacy design |
US11004125B2 (en) | 2016-04-01 | 2021-05-11 | OneTrust, LLC | Data processing systems and methods for integrating privacy information management systems with data loss prevention tools or other tools for privacy design |
US10956952B2 (en) | 2016-04-01 | 2021-03-23 | OneTrust, LLC | Data processing systems and communication systems and methods for the efficient generation of privacy risk assessments |
US11222309B2 (en) | 2016-06-10 | 2022-01-11 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US10848523B2 (en) | 2016-06-10 | 2020-11-24 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US10776515B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10776517B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Data processing systems for calculating and communicating cost of fulfilling data subject access requests and related methods |
US10776518B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Consent receipt management systems and related methods |
US10776514B2 (en) | 2016-06-10 | 2020-09-15 | OneTrust, LLC | Data processing systems for the identification and deletion of personal data in computer systems |
US10783256B2 (en) | 2016-06-10 | 2020-09-22 | OneTrust, LLC | Data processing systems for data transfer risk identification and related methods |
US10791150B2 (en) | 2016-06-10 | 2020-09-29 | OneTrust, LLC | Data processing and scanning systems for generating and populating a data inventory |
US10796260B2 (en) | 2016-06-10 | 2020-10-06 | OneTrust, LLC | Privacy management systems and methods |
US10798133B2 (en) | 2016-06-10 | 2020-10-06 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US10796020B2 (en) | 2016-06-10 | 2020-10-06 | OneTrust, LLC | Consent receipt management systems and related methods |
US10803200B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems for processing and managing data subject access in a distributed environment |
US10803199B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing and communications systems and methods for the efficient implementation of privacy by design |
US10803097B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US11921894B2 (en) | 2016-06-10 | 2024-03-05 | OneTrust, LLC | Data processing systems for generating and populating a data inventory for processing data access requests |
US11868507B2 (en) | 2016-06-10 | 2024-01-09 | OneTrust, LLC | Data processing systems for cookie compliance testing with website scanning and related methods |
US11847182B2 (en) | 2016-06-10 | 2023-12-19 | OneTrust, LLC | Data processing consent capture systems and related methods |
US11727141B2 (en) | 2016-06-10 | 2023-08-15 | OneTrust, LLC | Data processing systems and methods for synching privacy-related user consent across multiple computing devices |
US10803198B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems for use in automatically generating, populating, and submitting data subject access requests |
US10805354B2 (en) | 2016-06-10 | 2020-10-13 | OneTrust, LLC | Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance |
US10839102B2 (en) | 2016-06-10 | 2020-11-17 | OneTrust, LLC | Data processing systems for identifying and modifying processes that are subject to data subject access requests |
US11238390B2 (en) | 2016-06-10 | 2022-02-01 | OneTrust, LLC | Privacy management systems and methods |
US10846261B2 (en) | 2016-06-10 | 2020-11-24 | OneTrust, LLC | Data processing systems for processing data subject access requests |
US10846433B2 (en) | 2016-06-10 | 2020-11-24 | OneTrust, LLC | Data processing consent management systems and related methods |
US10769303B2 (en) | 2016-06-10 | 2020-09-08 | OneTrust, LLC | Data processing systems for central consent repository and related methods |
US10853501B2 (en) | 2016-06-10 | 2020-12-01 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US10867072B2 (en) | 2016-06-10 | 2020-12-15 | OneTrust, LLC | Data processing systems for measuring privacy maturity within an organization |
US10867007B2 (en) | 2016-06-10 | 2020-12-15 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10873606B2 (en) | 2016-06-10 | 2020-12-22 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US10878127B2 (en) | 2016-06-10 | 2020-12-29 | OneTrust, LLC | Data subject access request processing systems and related methods |
US10885485B2 (en) | 2016-06-10 | 2021-01-05 | OneTrust, LLC | Privacy management systems and methods |
US10896394B2 (en) | 2016-06-10 | 2021-01-19 | OneTrust, LLC | Privacy management systems and methods |
US10909265B2 (en) | 2016-06-10 | 2021-02-02 | OneTrust, LLC | Application privacy scanning systems and related methods |
US10909488B2 (en) | 2016-06-10 | 2021-02-02 | OneTrust, LLC | Data processing systems for assessing readiness for responding to privacy-related incidents |
US10929559B2 (en) | 2016-06-10 | 2021-02-23 | OneTrust, LLC | Data processing systems for data testing to confirm data deletion and related methods |
US10944725B2 (en) * | 2016-06-10 | 2021-03-09 | OneTrust, LLC | Data processing systems and methods for using a data model to select a target data asset in a data migration |
US10949170B2 (en) | 2016-06-10 | 2021-03-16 | OneTrust, LLC | Data processing systems for integration of consumer feedback with data subject access requests and related methods |
US10949565B2 (en) | 2016-06-10 | 2021-03-16 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US10949567B2 (en) | 2016-06-10 | 2021-03-16 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10949544B2 (en) | 2016-06-10 | 2021-03-16 | OneTrust, LLC | Data processing systems for data transfer risk identification and related methods |
US10769302B2 (en) | 2016-06-10 | 2020-09-08 | OneTrust, LLC | Consent receipt management systems and related methods |
US11675929B2 (en) | 2016-06-10 | 2023-06-13 | OneTrust, LLC | Data processing consent sharing systems and related methods |
US10970371B2 (en) | 2016-06-10 | 2021-04-06 | OneTrust, LLC | Consent receipt management systems and related methods |
US10972509B2 (en) | 2016-06-10 | 2021-04-06 | OneTrust, LLC | Data processing and scanning systems for generating and populating a data inventory |
US10970675B2 (en) | 2016-06-10 | 2021-04-06 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US10984132B2 (en) | 2016-06-10 | 2021-04-20 | OneTrust, LLC | Data processing systems and methods for populating and maintaining a centralized database of personal data |
US11240273B2 (en) | 2016-06-10 | 2022-02-01 | OneTrust, LLC | Data processing and scanning systems for generating and populating a data inventory |
US10997318B2 (en) | 2016-06-10 | 2021-05-04 | OneTrust, LLC | Data processing systems for generating and populating a data inventory for processing data access requests |
US10997315B2 (en) | 2016-06-10 | 2021-05-04 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10762236B2 (en) | 2016-06-10 | 2020-09-01 | OneTrust, LLC | Data processing user interface monitoring systems and related methods |
US11023616B2 (en) | 2016-06-10 | 2021-06-01 | OneTrust, LLC | Data processing systems for identifying, assessing, and remediating data processing risks using data modeling techniques |
US11025675B2 (en) | 2016-06-10 | 2021-06-01 | OneTrust, LLC | Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance |
US11023842B2 (en) | 2016-06-10 | 2021-06-01 | OneTrust, LLC | Data processing systems and methods for bundled privacy policies |
US11030327B2 (en) | 2016-06-10 | 2021-06-08 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11030274B2 (en) | 2016-06-10 | 2021-06-08 | OneTrust, LLC | Data processing user interface monitoring systems and related methods |
US11030563B2 (en) | 2016-06-10 | 2021-06-08 | OneTrust, LLC | Privacy management systems and methods |
US11036771B2 (en) | 2016-06-10 | 2021-06-15 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US11036674B2 (en) | 2016-06-10 | 2021-06-15 | OneTrust, LLC | Data processing systems for processing data subject access requests |
US11038925B2 (en) | 2016-06-10 | 2021-06-15 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11036882B2 (en) | 2016-06-10 | 2021-06-15 | OneTrust, LLC | Data processing systems for processing and managing data subject access in a distributed environment |
US11057356B2 (en) | 2016-06-10 | 2021-07-06 | OneTrust, LLC | Automated data processing systems and methods for automatically processing data subject access requests using a chatbot |
US11062051B2 (en) | 2016-06-10 | 2021-07-13 | OneTrust, LLC | Consent receipt management systems and related methods |
US11068618B2 (en) | 2016-06-10 | 2021-07-20 | OneTrust, LLC | Data processing systems for central consent repository and related methods |
US11070593B2 (en) | 2016-06-10 | 2021-07-20 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11074367B2 (en) | 2016-06-10 | 2021-07-27 | OneTrust, LLC | Data processing systems for identity validation for consumer rights requests and related methods |
US11087260B2 (en) | 2016-06-10 | 2021-08-10 | OneTrust, LLC | Data processing systems and methods for customizing privacy training |
US11100444B2 (en) | 2016-06-10 | 2021-08-24 | OneTrust, LLC | Data processing systems and methods for providing training in a vendor procurement process |
US11100445B2 (en) | 2016-06-10 | 2021-08-24 | OneTrust, LLC | Data processing systems for assessing readiness for responding to privacy-related incidents |
US11651106B2 (en) | 2016-06-10 | 2023-05-16 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US11113416B2 (en) | 2016-06-10 | 2021-09-07 | OneTrust, LLC | Application privacy scanning systems and related methods |
US11120161B2 (en) | 2016-06-10 | 2021-09-14 | OneTrust, LLC | Data subject access request processing systems and related methods |
US11120162B2 (en) | 2016-06-10 | 2021-09-14 | OneTrust, LLC | Data processing systems for data testing to confirm data deletion and related methods |
US11122011B2 (en) * | 2016-06-10 | 2021-09-14 | OneTrust, LLC | Data processing systems and methods for using a data model to select a target data asset in a data migration |
US11126748B2 (en) | 2016-06-10 | 2021-09-21 | OneTrust, LLC | Data processing consent management systems and related methods |
US11134086B2 (en) | 2016-06-10 | 2021-09-28 | OneTrust, LLC | Consent conversion optimization systems and related methods |
US11138318B2 (en) | 2016-06-10 | 2021-10-05 | OneTrust, LLC | Data processing systems for data transfer risk identification and related methods |
US11138336B2 (en) | 2016-06-10 | 2021-10-05 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US11138242B2 (en) | 2016-06-10 | 2021-10-05 | OneTrust, LLC | Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software |
US11138299B2 (en) | 2016-06-10 | 2021-10-05 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11144622B2 (en) | 2016-06-10 | 2021-10-12 | OneTrust, LLC | Privacy management systems and methods |
US11144670B2 (en) | 2016-06-10 | 2021-10-12 | OneTrust, LLC | Data processing systems for identifying and modifying processes that are subject to data subject access requests |
US11146566B2 (en) | 2016-06-10 | 2021-10-12 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US10726158B2 (en) | 2016-06-10 | 2020-07-28 | OneTrust, LLC | Consent receipt management and automated process blocking systems and related methods |
US11151233B2 (en) | 2016-06-10 | 2021-10-19 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11157600B2 (en) | 2016-06-10 | 2021-10-26 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11651104B2 (en) | 2016-06-10 | 2023-05-16 | OneTrust, LLC | Consent receipt management systems and related methods |
US11182501B2 (en) | 2016-06-10 | 2021-11-23 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US11188615B2 (en) | 2016-06-10 | 2021-11-30 | OneTrust, LLC | Data processing consent capture systems and related methods |
US11188862B2 (en) | 2016-06-10 | 2021-11-30 | OneTrust, LLC | Privacy management systems and methods |
US11195134B2 (en) | 2016-06-10 | 2021-12-07 | OneTrust, LLC | Privacy management systems and methods |
US11200341B2 (en) | 2016-06-10 | 2021-12-14 | OneTrust, LLC | Consent receipt management systems and related methods |
US11210420B2 (en) | 2016-06-10 | 2021-12-28 | OneTrust, LLC | Data subject access request processing systems and related methods |
US11222142B2 (en) | 2016-06-10 | 2022-01-11 | OneTrust, LLC | Data processing systems for validating authorization for personal data collection, storage, and processing |
US10754981B2 (en) | 2016-06-10 | 2020-08-25 | OneTrust, LLC | Data processing systems for fulfilling data subject access requests and related methods |
US11222139B2 (en) | 2016-06-10 | 2022-01-11 | OneTrust, LLC | Data processing systems and methods for automatic discovery and assessment of mobile software development kits |
US11227247B2 (en) | 2016-06-10 | 2022-01-18 | OneTrust, LLC | Data processing systems and methods for bundled privacy policies |
US11328092B2 (en) | 2016-06-10 | 2022-05-10 | OneTrust, LLC | Data processing systems for processing and managing data subject access in a distributed environment |
US10769301B2 (en) | 2016-06-10 | 2020-09-08 | OneTrust, LLC | Data processing systems for webform crawling to map processing activities and related methods |
US10997542B2 (en) | 2016-06-10 | 2021-05-04 | OneTrust, LLC | Privacy management systems and methods |
US11244072B2 (en) | 2016-06-10 | 2022-02-08 | OneTrust, LLC | Data processing systems for identifying, assessing, and remediating data processing risks using data modeling techniques |
US11244071B2 (en) | 2016-06-10 | 2022-02-08 | OneTrust, LLC | Data processing systems for use in automatically generating, populating, and submitting data subject access requests |
US10740487B2 (en) | 2016-06-10 | 2020-08-11 | OneTrust, LLC | Data processing systems and methods for populating and maintaining a centralized database of personal data |
US11256777B2 (en) | 2016-06-10 | 2022-02-22 | OneTrust, LLC | Data processing user interface monitoring systems and related methods |
US11277448B2 (en) | 2016-06-10 | 2022-03-15 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11294939B2 (en) | 2016-06-10 | 2022-04-05 | OneTrust, LLC | Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software |
US11295316B2 (en) | 2016-06-10 | 2022-04-05 | OneTrust, LLC | Data processing systems for identity validation for consumer rights requests and related methods |
US11301589B2 (en) | 2016-06-10 | 2022-04-12 | OneTrust, LLC | Consent receipt management systems and related methods |
US11301796B2 (en) | 2016-06-10 | 2022-04-12 | OneTrust, LLC | Data processing systems and methods for customizing privacy training |
US11308435B2 (en) | 2016-06-10 | 2022-04-19 | OneTrust, LLC | Data processing systems for identifying, assessing, and remediating data processing risks using data modeling techniques |
US11328240B2 (en) | 2016-06-10 | 2022-05-10 | OneTrust, LLC | Data processing systems for assessing readiness for responding to privacy-related incidents |
US11228620B2 (en) | 2016-06-10 | 2022-01-18 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11334682B2 (en) | 2016-06-10 | 2022-05-17 | OneTrust, LLC | Data subject access request processing systems and related methods |
US11334681B2 (en) | 2016-06-10 | 2022-05-17 | OneTrust, LLC | Application privacy scanning systems and related meihods |
US11336697B2 (en) | 2016-06-10 | 2022-05-17 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11343284B2 (en) | 2016-06-10 | 2022-05-24 | OneTrust, LLC | Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance |
US11341447B2 (en) | 2016-06-10 | 2022-05-24 | OneTrust, LLC | Privacy management systems and methods |
US11347889B2 (en) | 2016-06-10 | 2022-05-31 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US11354435B2 (en) | 2016-06-10 | 2022-06-07 | OneTrust, LLC | Data processing systems for data testing to confirm data deletion and related methods |
US11354434B2 (en) | 2016-06-10 | 2022-06-07 | OneTrust, LLC | Data processing systems for verification of consent and notice processing and related methods |
US11361057B2 (en) | 2016-06-10 | 2022-06-14 | OneTrust, LLC | Consent receipt management systems and related methods |
US11366786B2 (en) | 2016-06-10 | 2022-06-21 | OneTrust, LLC | Data processing systems for processing data subject access requests |
US11366909B2 (en) | 2016-06-10 | 2022-06-21 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11645418B2 (en) | 2016-06-10 | 2023-05-09 | OneTrust, LLC | Data processing systems for data testing to confirm data deletion and related methods |
US11392720B2 (en) | 2016-06-10 | 2022-07-19 | OneTrust, LLC | Data processing systems for verification of consent and notice processing and related methods |
US11645353B2 (en) | 2016-06-10 | 2023-05-09 | OneTrust, LLC | Data processing consent capture systems and related methods |
US11403377B2 (en) | 2016-06-10 | 2022-08-02 | OneTrust, LLC | Privacy management systems and methods |
US11409908B2 (en) | 2016-06-10 | 2022-08-09 | OneTrust, LLC | Data processing systems and methods for populating and maintaining a centralized database of personal data |
US11410106B2 (en) | 2016-06-10 | 2022-08-09 | OneTrust, LLC | Privacy management systems and methods |
US11416634B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Consent receipt management systems and related methods |
US11416636B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing consent management systems and related methods |
US11416576B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing consent capture systems and related methods |
US11416109B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Automated data processing systems and methods for automatically processing data subject access requests using a chatbot |
US11416590B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11418516B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Consent conversion optimization systems and related methods |
US11416798B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing systems and methods for providing training in a vendor procurement process |
US11418492B2 (en) * | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing systems and methods for using a data model to select a target data asset in a data migration |
US11416589B2 (en) | 2016-06-10 | 2022-08-16 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11636171B2 (en) | 2016-06-10 | 2023-04-25 | OneTrust, LLC | Data processing user interface monitoring systems and related methods |
US11438386B2 (en) | 2016-06-10 | 2022-09-06 | OneTrust, LLC | Data processing systems for data-transfer risk identification, cross-border visualization generation, and related methods |
US11625502B2 (en) | 2016-06-10 | 2023-04-11 | OneTrust, LLC | Data processing systems for identifying and modifying processes that are subject to data subject access requests |
US11609939B2 (en) | 2016-06-10 | 2023-03-21 | OneTrust, LLC | Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software |
US11449633B2 (en) | 2016-06-10 | 2022-09-20 | OneTrust, LLC | Data processing systems and methods for automatic discovery and assessment of mobile software development kits |
US11461500B2 (en) | 2016-06-10 | 2022-10-04 | OneTrust, LLC | Data processing systems for cookie compliance testing with website scanning and related methods |
US11461722B2 (en) | 2016-06-10 | 2022-10-04 | OneTrust, LLC | Questionnaire response automation for compliance management |
US11468196B2 (en) | 2016-06-10 | 2022-10-11 | OneTrust, LLC | Data processing systems for validating authorization for personal data collection, storage, and processing |
US11468386B2 (en) | 2016-06-10 | 2022-10-11 | OneTrust, LLC | Data processing systems and methods for bundled privacy policies |
US11475136B2 (en) | 2016-06-10 | 2022-10-18 | OneTrust, LLC | Data processing systems for data transfer risk identification and related methods |
US11586762B2 (en) | 2016-06-10 | 2023-02-21 | OneTrust, LLC | Data processing systems and methods for auditing data request compliance |
US11481710B2 (en) | 2016-06-10 | 2022-10-25 | OneTrust, LLC | Privacy management systems and methods |
US11488085B2 (en) | 2016-06-10 | 2022-11-01 | OneTrust, LLC | Questionnaire response automation for compliance management |
US11586700B2 (en) | 2016-06-10 | 2023-02-21 | OneTrust, LLC | Data processing systems and methods for automatically blocking the use of tracking tools |
US11520928B2 (en) | 2016-06-10 | 2022-12-06 | OneTrust, LLC | Data processing systems for generating personal data receipts and related methods |
US11562097B2 (en) | 2016-06-10 | 2023-01-24 | OneTrust, LLC | Data processing systems for central consent repository and related methods |
US11558429B2 (en) | 2016-06-10 | 2023-01-17 | OneTrust, LLC | Data processing and scanning systems for generating and populating a data inventory |
US11556672B2 (en) | 2016-06-10 | 2023-01-17 | OneTrust, LLC | Data processing systems for verification of consent and notice processing and related methods |
US11544667B2 (en) | 2016-06-10 | 2023-01-03 | OneTrust, LLC | Data processing systems for generating and populating a data inventory |
US11544405B2 (en) | 2016-06-10 | 2023-01-03 | OneTrust, LLC | Data processing systems for verification of consent and notice processing and related methods |
US11550897B2 (en) | 2016-06-10 | 2023-01-10 | OneTrust, LLC | Data processing and scanning systems for assessing vendor risk |
US11551174B2 (en) | 2016-06-10 | 2023-01-10 | OneTrust, LLC | Privacy management systems and methods |
US10601636B2 (en) * | 2016-11-04 | 2020-03-24 | Crosscode, Inc. | Method and system for architecture analysis of an enterprise |
US11757698B2 (en) | 2016-11-04 | 2023-09-12 | Codelogic, Inc. | Method and system for architecture analysis of an enterprise |
US11102052B2 (en) | 2016-11-04 | 2021-08-24 | Codelogic, Inc. | Method and system for architecture analysis of an enterprise |
US11373007B2 (en) | 2017-06-16 | 2022-06-28 | OneTrust, LLC | Data processing systems for identifying whether cookies contain personally identifying information |
US11663359B2 (en) | 2017-06-16 | 2023-05-30 | OneTrust, LLC | Data processing systems for identifying whether cookies contain personally identifying information |
US20200278471A1 (en) * | 2017-09-12 | 2020-09-03 | Schlumberger Technology Corporation | Dynamic representation of exploration and/or production entity relationships |
WO2019055553A1 (en) * | 2017-09-12 | 2019-03-21 | Schlumberger Technology Corporation | Dynamic representation of exploration and/or production entity relationships |
US11619761B2 (en) * | 2017-09-12 | 2023-04-04 | Schlumberger Technology Corporation | Dynamic representation of exploration and/or production entity relationships |
US10963591B2 (en) | 2018-09-07 | 2021-03-30 | OneTrust, LLC | Data processing systems for orphaned data identification and deletion and related methods |
US11144675B2 (en) | 2018-09-07 | 2021-10-12 | OneTrust, LLC | Data processing systems and methods for automatically protecting sensitive data within privacy management systems |
US11157654B2 (en) | 2018-09-07 | 2021-10-26 | OneTrust, LLC | Data processing systems for orphaned data identification and deletion and related methods |
US11593523B2 (en) | 2018-09-07 | 2023-02-28 | OneTrust, LLC | Data processing systems for orphaned data identification and deletion and related methods |
US10803202B2 (en) | 2018-09-07 | 2020-10-13 | OneTrust, LLC | Data processing systems for orphaned data identification and deletion and related methods |
US11544409B2 (en) | 2018-09-07 | 2023-01-03 | OneTrust, LLC | Data processing systems and methods for automatically protecting sensitive data within privacy management systems |
US11947708B2 (en) | 2018-09-07 | 2024-04-02 | OneTrust, LLC | Data processing systems and methods for automatically protecting sensitive data within privacy management systems |
US11748458B2 (en) | 2020-04-15 | 2023-09-05 | Codelogic, Inc. | Systems and methods for a governance engine |
US11687657B2 (en) | 2020-07-08 | 2023-06-27 | Codelogic, Inc. | Systems and methods for software security analysis |
US11797528B2 (en) | 2020-07-08 | 2023-10-24 | OneTrust, LLC | Systems and methods for targeted data discovery |
US11444976B2 (en) | 2020-07-28 | 2022-09-13 | OneTrust, LLC | Systems and methods for automatically blocking the use of tracking tools |
US11475165B2 (en) | 2020-08-06 | 2022-10-18 | OneTrust, LLC | Data processing systems and methods for automatically redacting unstructured data from a data subject access request |
US11436373B2 (en) | 2020-09-15 | 2022-09-06 | OneTrust, LLC | Data processing systems and methods for detecting tools for the automatic blocking of consent requests |
US11704440B2 (en) | 2020-09-15 | 2023-07-18 | OneTrust, LLC | Data processing systems and methods for preventing execution of an action documenting a consent rejection |
US11526624B2 (en) | 2020-09-21 | 2022-12-13 | OneTrust, LLC | Data processing systems and methods for automatically detecting target data transfers and target data processing |
US11615192B2 (en) | 2020-11-06 | 2023-03-28 | OneTrust, LLC | Systems and methods for identifying data processing activities based on data discovery results |
US11397819B2 (en) | 2020-11-06 | 2022-07-26 | OneTrust, LLC | Systems and methods for identifying data processing activities based on data discovery results |
US11687528B2 (en) | 2021-01-25 | 2023-06-27 | OneTrust, LLC | Systems and methods for discovery, classification, and indexing of data in a native computing system |
US11442906B2 (en) | 2021-02-04 | 2022-09-13 | OneTrust, LLC | Managing custom attributes for domain objects defined within microservices |
US11494515B2 (en) | 2021-02-08 | 2022-11-08 | OneTrust, LLC | Data processing systems and methods for anonymizing data samples in classification analysis |
US11601464B2 (en) | 2021-02-10 | 2023-03-07 | OneTrust, LLC | Systems and methods for mitigating risks of third-party computing system functionality integration into a first-party computing system |
US11775348B2 (en) | 2021-02-17 | 2023-10-03 | OneTrust, LLC | Managing custom workflows for domain objects defined within microservices |
US11546661B2 (en) | 2021-02-18 | 2023-01-03 | OneTrust, LLC | Selective redaction of media content |
US11533315B2 (en) | 2021-03-08 | 2022-12-20 | OneTrust, LLC | Data transfer discovery and analysis systems and related methods |
US11816224B2 (en) | 2021-04-16 | 2023-11-14 | OneTrust, LLC | Assessing and managing computational risk involved with integrating third party computing functionality within a computing system |
US11562078B2 (en) | 2021-04-16 | 2023-01-24 | OneTrust, LLC | Assessing and managing computational risk involved with integrating third party computing functionality within a computing system |
US11620142B1 (en) | 2022-06-03 | 2023-04-04 | OneTrust, LLC | Generating and customizing user interfaces for demonstrating functions of interactive user environments |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9280581B1 (en) | Method and system for determination of data completeness for analytic data calculations | |
US11650854B2 (en) | Executing algorithms in parallel | |
US11625387B2 (en) | Structuring data | |
Stefanovic | Proactive supply chain performance management with predictive analytics | |
US7574379B2 (en) | Method and system of using artifacts to identify elements of a component business model | |
US9898491B2 (en) | Method and system for providing business intelligence data | |
Lawton | Making business intelligence more useful | |
US10467550B1 (en) | Operational business intelligence measurement and learning system | |
US20170116307A1 (en) | Automated Refinement and Validation of Data Warehouse Star Schemas | |
CN101506804A (en) | Methods and apparatus for maintaining consistency during analysis of large data sets | |
US10599678B2 (en) | Input gathering system and method for defining, refining or validating star schema for a source database | |
US20140310034A1 (en) | Performance indicator analytical framework | |
US20140025411A1 (en) | Automatic configuration of process definition metrics | |
US7992126B2 (en) | Apparatus and method for quantitatively measuring the balance within a balanced scorecard | |
US7899776B2 (en) | Explaining changes in measures thru data mining | |
US10360239B2 (en) | Automated definition of data warehouse star schemas | |
US20230153731A1 (en) | Data Validation and Master Network Techniques | |
Kassem et al. | Matching of business data in a generic business process warehousing | |
Juan et al. | Systematic approach for the gap analysis of business processes | |
US20140149186A1 (en) | Method and system of using artifacts to identify elements of a component business model | |
Dahiya et al. | Enhancing consistency of conceptual data warehouse design | |
Khan | Business Intelligence & Data Warehousing Simplified: 500 Questions, Answers, & Tips | |
US10949410B2 (en) | Multi-threaded data analytics | |
Dahiya et al. | Effective data warehouse for information delivery: a literature survey and classification | |
US10311390B2 (en) | Database document generation based on event-based database action recognition |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TROUX TECHNOLOGIES, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GRIMES, MIKAL;WILLIAMS, DAVID K.;BALLING, JAMES, JR.;REEL/FRAME:030006/0132 Effective date: 20130311 |
|
AS | Assignment |
Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT, Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:TROUX TECHNOLOGIES INC.;REEL/FRAME:035806/0285 Effective date: 20150601 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: GUGGENHEIM CORPORATE FUNDING, LLC, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:PHNTM HOLDINGS, INC.;PLANVIEW, INC.;PLANVIEW DELAWARE, LLC;AND OTHERS;REEL/FRAME:039387/0405 Effective date: 20160809 |
|
AS | Assignment |
Owner name: ARES CAPITAL CORPORATION, AS COLLATERAL AGENT, NEW Free format text: SECURITY INTEREST;ASSIGNORS:PLANVIEW, INC.;INNOTAS;TROUX TECHNOLOGIES, INC.;REEL/FRAME:041104/0380 Effective date: 20170127 Owner name: ARES CAPITAL CORPORATION, AS COLLATERAL AGENT, NEW Free format text: SECURITY INTEREST;ASSIGNORS:PLANVIEW, INC.;INNOTAS;TROUX TECHNOLOGIES, INC.;REEL/FRAME:041104/0844 Effective date: 20170127 |
|
AS | Assignment |
Owner name: PHNTM HOLDINGS, INC., TEXAS Free format text: RELEASE OF SECURITY INTERESTS RECORDED AT REEL/FRAME 031847/0619, 035806/0285 AND 039636/0721;ASSIGNOR:WELLS FARGO BANK, N.A.;REEL/FRAME:041577/0763 Effective date: 20170127 Owner name: PLANVIEW DELAWARE, LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT 039387/0405;ASSIGNOR:GUGGENHEIM CORPORATE FUNDING, LLC;REEL/FRAME:041577/0794 Effective date: 20170127 Owner name: TROUX TECHNOLOGIES, INC,, TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT 039387/0405;ASSIGNOR:GUGGENHEIM CORPORATE FUNDING, LLC;REEL/FRAME:041577/0794 Effective date: 20170127 Owner name: PLANVIEW, INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT 039387/0405;ASSIGNOR:GUGGENHEIM CORPORATE FUNDING, LLC;REEL/FRAME:041577/0794 Effective date: 20170127 Owner name: IDITAROD MERGER SUB, INC., TEXAS Free format text: RELEASE OF SECURITY INTERESTS RECORDED AT REEL/FRAME 031847/0619, 035806/0285 AND 039636/0721;ASSIGNOR:WELLS FARGO BANK, N.A.;REEL/FRAME:041577/0763 Effective date: 20170127 Owner name: PLANVIEW, INC., TEXAS Free format text: RELEASE OF SECURITY INTERESTS RECORDED AT REEL/FRAME 031847/0619, 035806/0285 AND 039636/0721;ASSIGNOR:WELLS FARGO BANK, N.A.;REEL/FRAME:041577/0763 Effective date: 20170127 Owner name: PHNTM HOLDINGS, INC., TEXAS Free format text: RELEASE OF SECURITY INTEREST RECORDED AT 039387/0405;ASSIGNOR:GUGGENHEIM CORPORATE FUNDING, LLC;REEL/FRAME:041577/0794 Effective date: 20170127 Owner name: INNOTAS, TEXAS Free format text: RELEASE OF SECURITY INTERESTS RECORDED AT REEL/FRAME 031847/0619, 035806/0285 AND 039636/0721;ASSIGNOR:WELLS FARGO BANK, N.A.;REEL/FRAME:041577/0763 Effective date: 20170127 |
|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: INNOTAS, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ARES CAPITAL CORPORATION;REEL/FRAME:051672/0856 Effective date: 20200130 Owner name: TROUX TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ARES CAPITAL CORPORATION;REEL/FRAME:051672/0856 Effective date: 20200130 Owner name: PLANVIEW, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ARES CAPITAL CORPORATION;REEL/FRAME:051672/0856 Effective date: 20200130 |
|
AS | Assignment |
Owner name: UBS AG, STAMFORD BRANCH, CONNECTICUT Free format text: FIRST LIEN SECURITY AGREEMENT;ASSIGNORS:PLANVIEW, INC.;SPIGIT, INC.;TROUX TECHNOLOGIES, INC.;REEL/FRAME:054962/0236 Effective date: 20201217 |
|
AS | Assignment |
Owner name: UBS AG, STAMFORD BRANCH, CONNECTICUT Free format text: SECOND LIEN SECURITY AGREEMENT;ASSIGNORS:PLANVIEW, INC.;SPIGIT, INC.;TROUX TECHNOLOGIES, INC.;REEL/FRAME:054804/0543 Effective date: 20201217 |
|
AS | Assignment |
Owner name: TROUX TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ARES CAPITAL CORPORATION;REEL/FRAME:054740/0865 Effective date: 20201217 Owner name: PLANVIEW, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ARES CAPITAL CORPORATION;REEL/FRAME:054740/0865 Effective date: 20201217 Owner name: INNOTAS, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ARES CAPITAL CORPORATION;REEL/FRAME:054740/0865 Effective date: 20201217 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |