Qeystone's Decentralized Data Structure

Overview of Qeystone's Decentralized Data Structure

Qeystone data fields are defined in project templates. When a new project is started from a project template, the project inherits the data fields from the project template. However, any changes you make to a project template do not affect existing projects that were started from the original project template. This is the key to understanding the implications of the decentralized data structure in Qeystone.

Implication #1: Multiple Project Templates Must Have Identical Data Fields

To ensure that the Dashboard aggregates project data values correctly, you must ensure that all project templates define data fields the same way. When you save a project as a template, Qeystone checks every data field to see if it matches a data field in any existing templates. If Qeystone finds a unique data field, it adds it to the set of data fields that are used in Dashboard reports.

Note

Qeystone does not check data fields that you add to projects; it checks only templates. Data fields that you add to projects are never added to the set of data fields that are used in Dashboard reports.

Tip

To view the set of data fields that are used in Dashboard reports, choose Settings > Select Fields to Display.

Example 1: Identifying unique data fields

Suppose the template repository contains two project templates with the following data fields:
DMAIC Project template Kaizen Event template
Hard Savings Savings (Hard)
Soft Savings Savings (Soft)
Implementation Costs Implementation Costs
Net Savings Savings (Net)
While it might seem obvious that Hard Savings in the DMAIC Project template and Savings (Hard) in the Kaizen Event project template should be combined to aggregate hard savings on the Dashboard, the Dashboard sees them as two distinct data fields.
All Data Fields
Hard Savings
Savings (Hard)
Soft Savings
Savings (Soft)
Implementation Costs
Net Savings
Savings (Net)

As a result, you cannot create a summary that displays Hard Savings across all project types because the DMAIC Project template and the Kaizen Event project template store hard savings values in different fields. Therefore, Qeystone aggregates Hard Savings separately from Savings (Hard).

Example 2: Aggregating data from similar data fields

Qeystone can only aggregate data from data fields that are identical. The following is a list of exceptions:
  • Two list fields with the exact same name, field ID, and data type, but with different sets of list values. (Shown in the following example.)
  • Two text data fields with the same name and field ID, but with different default values.
  • Two decimal data fields with the same name and field ID, but with different default, minimum, or maximum values.
  • Two integer data fields with the same name and field ID, but with different default, minimum, or maximum values.
For example, two project templates contain a list field named Current Phase.
Current Phase in the DMAIC Project template Current Phase in the Kaizen Event project template
Define Preparation
Measure Day 1 - Measure
Analyze Day 2 - Data and Analyze
Improve Day 3 - Analyze and Implement
Control Day 4 - Finish Implementation
  Day 5 - Pilot and Present
  Event Closure and Follow Up
On the Dashboard, Qeystone stores a single list field named Current Phase that includes all values from both templates.
Current Phase on the Dashboard
Define
Measure
Analyze
Improve
Control
Preparation
Day 1 - Measure
Day 2 - Data and Analyze
Day 3 - Analyze and Implement
Day 4 - Finish Implementation
Day 5 - Pilot and Present
Event Closure and Follow Up

Implication #2: Changes to Data Fields Are Not Propagated to Existing Projects

When you change a data field in a project template, any existing projects that are created from the original project template are not affected. In other words, the change is not applied to the data fields in existing projects. For example, suppose your project template initially contains only two financial data fields: Hard Savings and Soft Savings. A user starts two projects from the original project template, Project #1 and Project #2, which contain the Hard Savings and Soft Savings data fields.

A few months into the deployment, you decide to also track Implementation Costs and Net Savings. You update the project template to include the new data fields. Now, when a user starts Project #3 and Project #4 from the updated project template, they contain Hard Savings, Soft Savings, Implementation Costs, and Net Savings. However, Project #1 and Project #2 do not contain the new financial data fields because they were started from the original project template.

Two projects started from original project template:
Two projects started from the updated project template:
By using this site you agree to the use of cookies for analytics and personalized content.  Read our policy