Welcome, Data Engineers
As a data engineer for your InterSystems TotalView™ For Asset Management solution, your task is to set up the data pipeline, a term that refers to all the infrastructure needed to make data available within the solution. This page provides an overview of that infrastructure, from start to finish.
When data is available within the system, you and data analysts can create analysis cubes and reports based on those tables.
In InterSystems TotalView For Asset Management, a data source is a named configuration item that provides all the information needed to retrieve data from an external source. A classic data source is a database, but another possibility is a financial system that provides an API via which an authenticated user can retrieve data. Yet another option is delimited files, either retrieved from a cloud location or pushed to the local file system. In all cases, the data source definition, usually configured by an administrator, contains all the information needed to retrieve structural information as well as data.
A data source can provide multiple kinds of data, each following a specific structure. The classic case is a database that contains many tables, where each table has a specific structure. Similarly, a specific API call returns data in a specific format. In InterSystems TotalView For Asset Management, each of these structures is a schema, and the goal is to create a Data Catalog that consists of the schemas that are relevant to the business (and that are ultimately needed for reports and analysis). As a data engineer, your task is to import schemas from the data sources into the Data Catalog and then refine them and categorize them in ways that are useful to your organization.
To get started with this task, see Importing Schemas.
Recipes describe how to load data from external sources into InterSystems TotalView For Asset Management. Any recipe consists of some or all of the following steps, in order:
Staging activities, each of which loads data into a generated staging table.
Transformation activities, which can clean data in various ways.
Validation activities, which can compare data to desired ranges, as an example.
Reconciliation activities, in which you specify comparisons that define a valid reconciliation of the data.
Transformation, validation, and reconciliation all update the applicable staging table, so that the processing is fully transparent. You can directly examine the staging table at any time.
Data promotion activities, which uses SQL to update a final table, based on the contents of one or more staging table or tables.
A recipe can also include custom steps at any stage in the processing.
To get started with this task, see Defining Recipes.
InterSystems TotalView For Asset Management includes InterSystems IRIS® Adaptive Analytics, a Business Intelligence tool powered by co-development with AtScale. This means that data engineers and data analysts can define cubes based on those tables, and then use those cubes for analytics. See Defining Cubes.
InterSystems TotalView For Asset Management provides an additional mechanism to support your data needs: snapshots. With snapshots, you can easily save data for later inspection by regulators; the snapshot can pull data from multiple tables as needed, writing them to a snapshot table, and the system applies a tag to the records. The product automatically stores all snapshot runs; that is, a new snapshot run does not overwrite a previous snapshot run.
When you have run a snapshot multiple times, applying a different tag each time, you can examine how that data changes over time. In particular, you can build a cube on the snapshot data, using the tag values as a dimension.
See Defining Snapshots.
The Business Scheduler provides an easy way to schedule the running of tasks: running recipes, building cubes, and performing snapshots. See Scheduling and Running Tasks.
In the initial phases of implementation, you can configure tasks to be run manually (from the Business Scheduler).
Later, when you want the tasks to be executed on a schedule, it is necessary to define the applicable calendar information and to manage dependencies among tasks. This works as follows:
To define calendar information, you define entities, each which has its own calendar. To simplify scheduling, the product supports a hierarchical system of entities, each of which can have its own business calendar but can inherit calender details from its parent. See Defining Entities.
To specify dependencies among tasks, you apply a tag to a scheduled task and define dependency expressions in other tasks, referring to that tag. Then a task can be run (on a given day) only after the dependencies are fulfilled. See Managing Task Dependencies.