Core AgileData.io Terms

AgileData.io contains a number of different terms, understanding these terms will help you get better value out of the using it.

6 Core Capability Areas

AgileData.io is made up of 6 logical areas.

Catalog

Every-time you do something with data in AgileData.io the description of that data automatically stored in the catalog for you. Whether you are collecting your data, creating rules to combine your data, rules to validate your data it or rules to make it easily consumable, everything about that data is automatically stored in the catalog for you.

The Catalog area enables you to search and find all the data stored in your organisation, understand where the data lives, what the data means and how much you can trust it.

History

When your data is collected by AgileData.io we automatically store this data in your History area. As you collect more and more data, AgileData.io will automatically store this data in the History area for you.

The History area provides an immutable organisational memory of what has happened in your data. It stores a copy of all your data over all time.

Events

When you create a change rule to align your data with the way your organisation actually works (compared to how your system of record stores the data) these Business Concepts, Business Details and Business Events are stored in the Event area.

The Event area is a bit like a commercial kitchen, the consumer doesn’t see the effort required to make the data consumable, and AgileData.io provides a bunch of recipes (rule templates) to make it easier for you to change your raw data into something that is consumable as well.

Rules

Rules are a form of natural language you use to change the way data looks or what it means. Each time new data is collected and arrives into the History area these rules are automatically triggered and change the data based on the rules you have defined.

The Rules remove the need for you to write code to change the way data looks or behaves.

Consume

Your users access data that is presented in the Consume area via their favourite tool. This could be a visualisation or reporting tool such Google Data Studio, Yellowfin, Microsoft PowerBI, Tableau, Thoughtspot or Qlik. Your internal or external systems can access this data via API’s

The Consume area allows you to present your data the way your users expect to see it, including using “pretty:names for that data rather than complex technical names.

Manage

AgileData.io automates as much as possible but there is always a need to keep an eye on how things are going, so we make that easy to.

The Manage area provides you with a view of what loaded when and who used what and when.

Key Terminology

As well as the 6 core capability areas there are a few other terms that are core to using AgileData.io.

Business Concepts

Business Concepts are the terms your organisation uses to describe things that are involved in business transactions facilitated by your organisation.

You can read more about them at Business Concepts

Business Details

Business Details holds data that describes or provide context for the Concepts your organisation uses to describe things that are involved in business transactions facilitated by your organisation.

You can read more about them at Business Details

Business Events

Business Events hold data that describes the business transactions facilitated by your organisation.

You can read more about them at Business Events

SaaS Platform

SaaS stands for Software as a Service, it describes a commercial model where we provide the software you need, plus the infrastructure (hosting) you need combined with the support your need, for a monthly subscription fee, This means you can just use AgileData.io to collect, combine and consume your data without worrying about building all the capabilities and technology yourself.

Other examples of SaaS offerings are Gmail, Google Docs, Salesforce and Xero.

Tenancy

You AgileData.io environment is what we call a tenancy.

Most customers tend to have one tenancy but you can have one or more tenancies as a customer.

For example you may have a tenancy for production and development or you may decided to have separate tenancies for different business units within your organisation.

You do not need to use separate tenancies to provide separate data access across business units. AgileData.io coarse and fine grained security capabilities will allow you to configure the security you require within a single tenancy. But if you feel more comfortable having multiple tenancies, then that is up-to you.

Just remember that each tenancy has a separate cost based on its T-shirt sizing, and at the moment each user will need a separate login for each tenancy.