Plutora And Plutora Test’s Data Cubes

Plutora Analytics is now available for Plutora Test’s Defects and Test Plan modules.

Knowing the design and layout of Plutora and Plutora Test’s data cubes makes it easier to design worksheets in Plutora Analytics.

Release Changes cube deals with Release data related to Changes. Changes list the technical aspects of a functional change to a System, including impacts, timings, approvals, and Stakeholders. Release Changes cube should be linked to Releases cube by either Release ID or Release Name to see the Changes associated with Releases. Only Project and Independent Releases can have Changes, which need to have the same Systems in common.

Example Queries

  • Number of Changes per Release
  • Changes implemented over time
  • Changes backlog by System
  • Changes backlog by Business Value score
  • Number of new or completed Changes over time
  • Aging of Changes
  • Average time from requested status to completed status

Data Columns

Assigned to Group (Group Name):

  • Group Description
  • Group Name
  • Is Deleted (True / False)

Assigned to Group User (User assigned to the Group):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the email address of the user assigned to the group)

Assigned to User (User details):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the email address of the user assigned to the group)

Change (Change Details):

  • Assigned To
  • Change Identifier (Change ID)
  • Change Name
  • Delivery Risk
  • Expected Delivery Date UTC (this is the only one to be used)
  • Organisation Name
  • Priority
  • Raised By
  • Raised On Date UTC (this is the only one to be used)
  • Status
  • Theme
  • Type

Change Raised By (Change Raised by user details):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the email address of the user assigned to the group)

Change_Release_BRIDGE (Already linked to relative tables, can’t link to any other cubes):

  • Change ID
  • Company ID
  • Release ID
  • Release Name

Organisation

  • Organisation Name

Systems Changes cube shows Systems that are impacted by Changes.

Users should use Changes cube instead of System Changes cube if they want to see all the Changes in the subdomain, including non-impacted Systems.

Data Columns

Assigned to Group (Group Name):

  • Group Description
  • Group Name
  • Is Deleted (True / False)

Assigned to Group User (User assigned to the Group):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the full name of the user assigned to the group)

Assigned to User (User details):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the full name of the user)

Change (Change Details):

  • Assigned To
  • Assigned To Group ID
  • Assigned To User ID
  • Change Name
  • Delivery Risk
  • Expected Delivery Date UTC (this is the only one to be used)
  • Organization Name
  • Priority
  • Raised By
  • Raised On Date UTC (this is the only one to be used)
  • Status
  • Theme
  • Type

Change Raised by (Raised by details):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (Email of the user)

Change System Bridge (Linked Tables):

  • Company ID
  • Impacted System
  • System ID

Organization:

  • Organization Name

Release cube shows Release data, including Phases and Gates. Release cube should be linked to Release Activity cube via Release ID to show the Activities belonging to each Release.

Structure of the Release Cubes

Download a PDF of the Reporting Structure for Release image.

Data Columns

Organization:

  • Organization Name

Organization Director:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the email address of the user assigned to the group)

Parent Release:

  • Approval Workflow Status
  • Implementation Date UTC
  • Location
  • Organization Name
  • Plutora Release Type
  • Release Name
  • Release Owner Name
  • Release Status
  • Release Type
  • Release Identifier
  • Risk Level

Phase Gate:

  • Is Deleted (Phase Gate – True / False)
  • Phase Gate End Date UTC
  • Phase Gate Name
  • Phase Gate Start Date UTC
  • Type

Release:

  • Approval Workflow Status
  • Implementation Date UTC
  • Location
  • Organization Name
  • Parent Name
  • Plutora Release Type
  • Release Name
  • Release Owner Name
  • Release Status
  • Release Type
  • Release Identifier
  • Risk Level

Release Owner:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the email address of the user assigned to the group)

Release Owner Group:

  • Group Description
  • Group Name
  • Is Deleted (True / False)

Release Owner Group User:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the email address of the user assigned to the group)

Release_FACT (Linked Tables):

  • Company ID
  • Organization ID
  • Parent ID
  • Release ID
  • Release Package ID

Release Package:

  • Release Package Name

Release Activities cube shows the relationship between Releases and the Release Activities (both Activities and Criteria) belonging to Phases and Gates. Release Activity cube should be linked to Release cube via Release ID to show the Activities belonging to each Release.

Data Columns

Release_System:

  • System Role Dependency Type

Release_System_FACT (Linked Tables):

  • Company ID
  • Release ID
  • Release System ID
  • System Deployment ID
  • System ID

System (System Details impacted by this Release):

  • Organisation Name
  • Status
  • System Description
  • System Name
  • Vendor

System_Deployment:

  • Change Record
  • Deploying To
  • Deployment Completed Date UTC (this is the only one to be used)
  • Deployment End Date UTC (this is the only one to be used)
  • Deployment Start Date UTC (this is the only one to be used)
  • Deployment Status
  • Deployment Title

Deployment Plan cube shows all the Deployment Plans in the subdomain, along with other information, such as Organization Name, Director, Created, and Updated By.

Users need the Deployment Plan Activities cube to see Deployment Plan Activities.

Example Queries

  • Number of Deployment Plans.

Structure of the Deployment Plan Cubes

Download a PDF of the Reporting Structure for Deployment Plans.

Created By:

  • First Name
  • Full Name
  • Is Deleted (True /False)
  • Last Name
  • User Name (This is the email of the Created by User)

Deployment Plan:

  • Created By
  • Created On Date UTC
  • Current Status
  • Deployment Plan Name
  • Description
  • External Identifier
  • Organization Name
  • Updated By
  • Updated on Date UTC

Deployment_Plan_FACT (Linked Tables):

  • Company ID
  • Deployment Plan ID
  • Organization ID

Organization:

  • Organization Name

Organization Director:

  • First Name
  • Full Name
  • Is Deleted (True /False)
  • Last Name
  • User Name (This is the email of the Created by User)

Updated By:

  • First Name
  • Full Name
  • Is Deleted (True /False)
  • Last Name
  • User Name (This is the email of the Created by User)

Release Systems cube deals with data related to the Systems selected under Systems tab when adding or editing an Enterprise, Project, or Independent Release. Due to the central role played by Systems, this entity can be related to other entities such as Environments, Changes, PIRs, TEBRs, TECRs and so on.

To see impacted Systems by Release, link Release Systems cube to Releases cube by the Release ID.

Example Queries

  • Number of Systems per Release based on their Status, Vendor, Accountable Stakeholder.
  • Number of Changes per System in a Release.

Data Columns

Release_System:

  • System Role Dependency Type

Release_System_FACT (Linked Tables):

  • Company ID
  • Release ID
  • Release System ID
  • System Deployment ID
  • System ID

System (System Details Impacted by this Release):

  • Organization Name
  • Status
  • System Description
  • System Name
  • Vendor

System_Deployment:

  • Change Record
  • Deploying To
  • Deployment Completed Date UTC (this is the only one to be used)
  • Deployment End Date UTC (this is the only one to be used)
  • Deployment Start Date UTC (this is the only one to be used)
  • Deployment Status
  • Deployment Title

Environment cube shows Environment information along with Organization, Environment Manager, and linked System data, irrespective of whether the Environments are booked or unbooked.

Structure of the Environment Cubes

Download a PDF of the Reporting Structure for Environments image.

Data Columns

Environment:

  • Environment Description
  • Environment Manager
  • Environment Name
  • Environment Status
  • Environment URL
  • Environment Vendor
  • Is Shared Environment
  • Phase Usage

Environment_Analysis_FACT:

  • Company ID
  • Environment ID
  • Organisation ID
  • System ID

Organization:

  • Organization Name

System (System Details):

  • Organization Name
  • Status
  • System Description
  • System Name
  • Vendor (System)

Stakeholders represent individual Users or User Groups. Stakeholders cube deals with Stakeholder data related to Releases, that have been added under the Stakeholder tab when adding or editing an EnterpriseProject, or Independent Release.

Stakeholder cube, with Stakeholder and RACI information can be linked to the following cubes: Release, Change, Deployment Plan, Environment, Environment Group, and System. 

Example Queries

  • Number of Stakeholders per Release per RACI.
  • Number of times a Stakeholder has been assigned to Releases.
  • Releases that lack Stakeholders.

Data Columns

Group:

  • Group Description
  • Group Name
  • Is Deleted Group (True / False)

Group User:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the Email address of the user)

Stakeholder:

  • Email
  • Engagement
  • Is Accountable
  • Is Consulted
  • Is Informed
  • Is Responsible
  • Stakeholder Name
  • Stakeholder Type

Stakeholder Role

  • Role Name

Stakeholder_FACT (To be linked to other Cubes):

  • Change ID
  • Company ID
  • Deployment Plan ID
  • Environment Group ID
  • Environment ID
  • Release ID
  • Stakeholder ID
  • Stakeholder Role ID
  • System ID

User (User details):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the Email address of the user)

System cube shows all the Systems in the subdomain, including those that are active, inactive, used, and unused.

Data Columns

System (System Details):

  • Organization Name
  • Status
  • System Description
  • System Name
  • Vendor

System FACT (Linked Tables):

  • Company ID
  • Organization ID
  • System ID

Technical Specifications and Configurations cube shows Environment technical specifications and configurations. Link Technical Specifications and Configurations cube to Environment cube by Environment ID to see Environment details, such as Environment Manager, Environment Status, Environment Description, Phase Usage, URL, Vendor, and associated Systems.

Data Columns

Component:

  • Component Name
  • Component Version

Environment:

  • Environment Description
  • Environment Manager
  • Environment Name
  • Environment Status
  • Environment URL
  • Environment Vendor
  • Is Shared Environment (True / False)
  • Phase Usage

Host:

  • Host Name

Layer:

  • Layer Name

Organization:

  • Organization Name

System:

  • Organization Name (System)
  • Status
  • System Description
  • System Name
  • Vendor (System)

Tech_Spec_FACT:

  • Company ID
  • Environment ID
  • Host ID

Changes cube lists the technical aspects of a functional change to a System, including impacts, timings, approvals, and Stakeholders. Changes cube shows all changes on the subdomain, regardless of whether they have impacted Systems or are assigned to any Releases.

Example Queries

  • Number of Changes per Release
  • Changes implemented over time
  • Changes backlog by System
  • Changes backlog by Business Value score
  • Number of new or completed Changes over time
  • Aging of Changes
  • Average time from requested status to completed status

Data Columns

Assigned to Group (Group Name):

  • Group Description
  • Group Name
  • Is Deleted (True / False)

Assigned to Group User (User assigned to the Group):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (Email of the user assigned to the group)

Assigned to User (User details):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the full name of the user)

Change (Change Details):

  • Assigned To
  • Change Name
  • Delivery Risk
  • Expected Delivery Date UTC (this is the only one to be used)
  • Organization Name
  • Priority
  • Raised By
  • Raised On Date UTC (this is the only one to be used)
  • Status
  • Theme
  • Type
  • Description
  • Implementation Date (is technically “Release Implementation Date”, thus required to use Release Change Cube to link Release Cube to see the value)

Change FACT (Linked Tables):

  • Change ID
  • Company ID
  • Organization ID

Raised by User (Raised by details):

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (Email of the user)

Release Environments cube lists Environment details such as Organization, Environment Manager, Phase Usage, Environment Status, Environment Description, and linked Systems, irrespective of whether the Environment is booked or not.

Release Environments cube also lists Booking Environment and Environment Group with Approver, Status, Allocation Start and End Date.

Link Release Cube to Release Environments cube by Release ID to see what Environments and Environment Groups are booked for each Release with details such as Implementation Date, Organization, and Start and End Dates for Phases and Gates.

Data Columns

Booking:

  • Booking Approver
  • Booking Status
  • Environment Allocation End Date UTC
  • Environment Allocation Start Date UTC

Booking Approver:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the full name of the user)

Environment:

  • Environment Description
  • Environment Manager
  • Environment Name
  • Environment Status
  • Environment URL
  • Environment Vendor
  • Is Shared Environment
  • Phase Usage

Environment_Allocation_FACT:

  • Booking ID
  • Company ID
  • Environment Group ID
  • Environment ID
  • Organisation ID
  • Phase Gate ID
  • Release ID
  • Stakeholder
  • System ID

Environment Group:

  • Environment Group Is Deleted
  • Environment Group Is Auto Approved
  • Environment Group Description
  • Environment Group Name
  • Usage Work Item

Organization:

  • Organization Name

Test Plans cube contains Plutora Test Test Plan data.

Example Queries

  • Number of Test Plans, their various Statuses and Types.

Data Columns

Created By:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the full name of the user assigned to the group)

Last Updated By:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the full name of the user assigned to the group)

Resource:

  • First Name
  • Full Name
  • Is Deleted (True / False)
  • Last Name
  • User Name (This is the full name of the user assigned to the group)

Test Plan (Test Plan Details):

  • Created By
  • Created Date Local
  • Created Date UTC
  • Description
  • Last Updated By
  • Last Updated Date Local
  • Last Updated Date UTC
  • Name
  • Status
  • Test Plan Identifier – Test Plan ID in the Plutora Application
  • Test Resources
  • Type

Test_Plan_FACT

  • Release ID – to be connected to Release and other Released related Data Source / cubes
  • Test Plan ID

Back to the top arrow

Was this article helpful?

0 found this helpful.