# US 2021/0174302 A1 · Data provisioning system and method

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0174302 A1
- Document ID: US20210174302A1
- Status: Published application
- Kind: A1
- Application number: 16/702,897
- Filed: 2019-12-04
- Published: 2021-06-10
- Earliest claimed: 2019-12-04
- Assignees: Morgan Stanley Services Group Inc.
- Applicants: Morgan Stanley Services Group Inc.
- Inventors: Suryakant BRAHMBHATT; Nandakumar Rampura
- Web page: https://patentgrep.com/patent/US20210174302A1

## CPC

- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

The invention relates to a computer-implemented system and method for provisioning data to data consumers within a business or organization. The method may include the steps of: providing a user interface for the data consumers that presents them with a data catalog identifying various data sources available to the data consumer and an electronic data request form, and presenting a data owner in the organization with options for specifying access to their data. The method may also include providing a data preparation module that includes an interface to the data sources, a data entitlement module to control the types of data presented to the data consumer, and a semantic layer that replaces technical terms associated with the data sources with non-technical descriptions of the available data. The method may also include automatically provisioning the requested data to the data consumers using an auto code generation function.

## Claims

### Claim 1

A computer-implemented method for provisioning data to a plurality of data consumers in an organization, the method comprising:
providing a graphical user interface designed to: (a) present a data consumer in the organization with a data catalog comprising metadata that identifies a plurality of columns in a database available to the data consumer and identifies a data type of each of the plurality of columns without providing the data to the data consumer, wherein the data consists of values the plurality of columns are assigned in particular records, and wherein the data remains located on different data sources from different platforms and only the metadata for the data catalog is centralized; (b) present a data provider in the organization with options for specifying access of particular categories of data consumers to the data provider's data; (c) present a data steward in the organization with options to view and govern use of the data by the data consumers; and (d) receive input from the data consumer, provide the input to a data request module and present the data consumer with output from the data request module, wherein the data request module is configured to:
receive a natural language search query and a data attribute through a drag and drop feature of the user interface;
receive a modification input from the data steward, the modification input being a SQL query to optimize the search query;
identify in data sources an existing feed that has already been produced for another data consumer, wherein the existing feed matches the search query, the modification input and the data attribute; and
display to the data consumer a message indicating that the existing feed is available;
providing a data preparation module, wherein the data preparation module is programmed to (a) provide an interface to the data sources, (b) provide a data entitlement module to control the types of data presented to the data consumer, and (c) provide a semantic layer that decouples a data source data structure from a data consumer data structure by associating a business name for each column with a technical name for that column, allowing a data consumer to use a query builder to build a query that acts upon technical names of columns while only knowing business names of columns;
providing a metadata module that collects and stores metadata associated with the data sources and that updates the data catalog based on the metadata; and
providing a data publishing module that receives data from the data sources in response to the request of the data consumer and provisions data to the data consumers, wherein the data publishing module uses an auto code generation module to automatically generate code to execute the data provisioning.

### Claim 2 (depends on 1)

The method of claim 1, further comprising providing a recommendation module that is programmed to:
determine recommended metadata associated with recommended data for a data consumer, wherein the recommended metadata comprises one or more columns from the metadata, or one or more tables or data sets that comprise the one or more columns; and
present the recommended metadata to the data consumer via the user interface.

### Claim 3 (depends on 1)

The method of claim 1, wherein the data entitlement module is programmed to:
upon selection of one or more columns identified by the metadata, obtain sample data consisting of values the one or more columns are assigned in particular records,
provide the sample data to all data consumers regardless of the data consumer's access entitlement; and
provide production data and non-production data from the one or more columns to data consumers based on their individual access entitlements.

### Claim 4 (depends on 1)

The method of claim 1, wherein the semantic layer is programmed to replace each technical name for a column with the associated business name of that column when the query builder displays column names to the data consumer.

### Claim 5

(canceled)

### Claim 6 (depends on 1)

The method of claim 1, wherein the user interface is programmed to receive a request for status update from the data consumer for a data request, and to generate a status update for the data consumer regarding the data consumer's request for status update.

### Claim 7 (depends on 1)

The method of claim 1, wherein the data preparation module comprises a query builder, an SQL parser, and an SQL editor to transform a data request by a data consumer to a query for the data sources.

### Claim 8 (depends on 1)

The method of claim 1, wherein the metadata module is configured to implement a centralized organization metadata model using pre-existing metadata repositories associated with the data sources.

### Claim 9 (depends on 1)

The method of claim 1, wherein the metadata module comprises a data lineage module that collects and stores information on upstream processes and systems that generate data.

### Claim 10 (depends on 1)

The method of claim 1, further comprising a data governance module that executes a data approval process comprising detecting, based on the metadata, that underlying data is sensitive or confidential, and based on a determination of sensitivity or confidentiality, automatically creates a workflow that solicits the approval of one or more of the data stewards.

### Claim 11

A computer-implemented system for provisioning data to a plurality of data consumers in an organization, the system comprising:
an electronic memory; and
a processor that is programmed to:
present a graphical user interface programmed to: (a) present a data consumer in the organization with a data catalog comprising metadata that identifies a plurality of columns in a database available to the data consumer and identifies a data type of each of the plurality of columns without providing the data to the data consumer, wherein the data consists of values the plurality of columns are assigned in particular records, and wherein the data remains located on different data sources from different platforms and only the metadata for the data catalog is centralized: (b) present a data provider in the organization with options for specifying access of particular categories of data consumers to the data provider's data; (c) present a data steward in the organization with options to view and govern use of the data by the data consumers; and (d) receive input from the data consumer, provide the input to a data request module and present the data consumer with output from the data request module, wherein the data request module is configured to:
receive a natural language search query and a data attribute through a drag and drop feature of the user interface;
receive a modification input from the data steward, the modification input being a SQL query to optimize the search query;
identify in data sources an existing feed that has already been produced for another data consumer, Wherein the existing feed matches the search query, the modification input and the data attribute; and
display to the data consumer a message indicating that the existing feed is available;
provide a data preparation module, wherein the data preparation module is programmed to (a) provide an interface to the data sources, (b) provide a data entitlement module to control the types of data presented to the data consumer, and (c) provide a semantic layer that decouples data source data structure from a data consumer data structure by associating a business name for each column with a technical name for that column, allowing a data consumer to use a query builder to build a query that acts upon technical names of columns while only knowing business names of columns;
provide a metadata module that collects and stores metadata associated with the data sources and that updates the data catalog based on the metadata; and
provide a data publishing module that receives data from the data sources in response to the request of the data consumer and provisions data to the data consumers, wherein the data publishing module uses an auto code generation module to automatically generate code to execute the data provisioning.

### Claim 12 (depends on 11)

The system of claim 11, further comprising a recommendation module that is programmed to:
determine recommended metadata associated with recommended data for a data consumer, wherein the recommended metadata comprises one or more columns from the metadata, or one or more tables or data sets that comprise the one or more columns; and
present the recommended metadata to the data consumer via the user interface.

### Claim 13 (depends on 11)

The system of claim 11, wherein the data entitlement module is programmed to:
upon selection of one or more columns identified by the metadata, obtain sample data consisting of values the one or more columns are assigned in particular records,
provide the sample data to all data consumers regardless of the data consumer's access entitlement; and
provide production data and non-production data to data consumers based on their individual access entitlements.

### Claim 14 (depends on 11)

The system of claim 11, wherein the semantic layer is programmed to replace each technical name for a column with the associated business name of that column when the query builder displays column names to the data consumer.

### Claim 15

(canceled)

### Claim 16 (depends on 11)

The system of claim 11, wherein the user interface is programmed to receive a request for status update from the data consumer for a data request, and to generate a status update for the data consumer regarding the data consumer's request for status update.

### Claim 17 (depends on 11)

The system of claim 11, wherein the data preparation module comprises a query builder, an SQL, parser, and an SQL editor to transform a data request by a data consumer to a query for the data sources.

### Claim 18 (depends on 11)

The system of claim 11, wherein the metadata module is configured to implement a centralized organization metadata model using pre-existing metadata repositories associated with the data sources.

### Claim 19 (depends on 11)

The system of claim 11, wherein the metadata module comprises a data lineage module that collects and stores information on upstream processes and systems that generate data.

### Claim 20 (depends on 11)

The system of claim 11, further comprising a data governance module that executes a data approval process with a plurality of approval levels based on a title of the data consumer, whether the data is confidential, and whether the data is sensitive.

### Claim 21 (depends on 11)

The system of claim 11, further comprising an interactive chat hot utility to perform natural language processing on a query from a data consumer, search the metadata for possible columns satisfying the query, and provide the possible columns to the data consumer to be approved for inclusion in provisioned data.

### Claim 22 (depends on 11)

The system of claim 11, further comprising a module to offer data provisioning subscriptions in exchange for payment, track usage of the provisioned data, and provide a pay-per-use data provisioning model.

### Claim 23 (depends on 11)

The system of claim 11, wherein the system further comprises an attribute recommendation engine that uses a machine learning model to predict additional attributes of use to the data consumer based on existing attributes requested by the data consumer.

### Claim 24 (depends on 11)

The system of claim 11, wherein the system further comprises an enterprise metadata component that stores definitions of personally identifiable information (PII) data and ensures that the data steward has approved use of PII data in a feed before the data publishing module provisions the data.

### Claim 25 (depends on 11)

The system of claim 11, wherein the system further comprises a data traceability module that responds to a data consumer's identification of a downstream data issue by generating a graph of data dependencies to show processes or sources which are potential causes of the data issue.

### Claim 26 (depends on 11)

The system of claim 11, wherein the system further comprises an auto code migration module that receives a data feed created for a non-production environment and automatically generates an equivalent data feed drawing on data sources in a production environment.
