(v1.3.0 KMAX) The Next Leap In Reporting On Your Maximo Data

Product Releases
News
June 20, 2024

The Kurve team is always listening to your feedback and striving to deliver the features you need to make data visualization more intuitive and powerful. With the release of Kurve Maximo v1.3.0, we've packed in a slew of new functionalities and enhancements that are sure to elevate your ability to make graphs and reports you’ll actually use. Whether you are a data analyst, a business user, or a Kurve admin, there's something in this release for everyone.

Let's dive into the exciting new features that Kurve Maximo v1.3.0 brings to the table.

Click on a feature below to jump right to or scroll through and read on:

  1. Expanded ability to select fields from 2+ objects in an object structure: Kurve now supports unlimited one-to-one (1:1) relationships and one, one-to-many (1:N) relationship from an object structure
  2. Pre-filter data using Query Definitions: Maximo Query Definitions coming from Object Structures or Applications can be applied in the creation process of a Kurve graph/report to filter data when visualizing
  3. Two (2) new graph features:
    • Display Graph Totals: Enable graph totals to see a total for your selected measure column.
    • Define Dimension Axis Ranges: Define a range to display exactly what you want in your graph.
  4. Relabel Maximo field names in Kurve report columns: Navigate to the hamburger icon of any column header to easily relabel field names.
  5. Sort columns on the Kurve Overview Pages: Rearrange the list of graphs or reports by clicking on the Name, Object Structure, Created Date, or Creator column to sort the list.
  6. Set API and Cache Default Settings: Kurve Admins can now set the default SQL and Cache setting that will be applied to new graphs and reports.

1. Expanded Ability to Select Fields from 2+ Objects in an Object Structure

One of the standout features of this release is the expanded ability to select fields from two or more objects within an object structure. This enhancement significantly improves the flexibility and depth of your data analysis by supporting fields from multiple objects (primary, secondary, tertiary, etc.) in an object structure.

Imagine you need to visualize data from asset records, work orders, and location details. With this new feature, you can seamlessly pull in fields from each of these objects, creating a more comprehensive dataset for your reports and visualizations. This expanded feature supports unlimited one-to-one (1:1) relationships and/or one, one-to-many (1:N) relationship at a time, allowing you to create complex, insightful reports with ease.

A word of caution! Adding complexity to any report or graph logic, including using fields from multiple objects, can impact the runtime performance of your chart. For instance, if you’re pulling data from several large tables (e.g. work orders, assets, and job plan), you may experience slower load times. To mitigate this, ensure your queries are optimized and consider pre-filtering your data (see the next feature to learn more) to include only the most relevant records. The key is to maintain the balance between comprehensive analysis and efficient performance.

What is the difference between a 1:1 and 1:N relationship?

One-to-one (1:1): Each instance of a table (or object) A can be related with one and only one instance of table B, and vice versa.

For example:

  • Asset to Meter: Each asset can have one primary meter related with it. For example, a vehicle asset might have one primary odometer meter tracking it’s milage.
  • Location to Location Details: Each location can have one related location details record holding additional information specific to a location that doesn’t fit in the primary location table.
  • Asset to Warranty: An asset might have a specific warranty record that is unique to it, detailing terms and conditions of the warranty.

One-to-many (1:N): Each instance of table A can be related with multiple instances of table B, but each instance of table B is related with only one instance of table A.

For example:

  • Asset to Work Orders: each asset can have multiple work orders related with it. This allows tracking all maintenance activities, repairs, and inspections performed on a specific asset.
  • Location to Assets: Each location can have multiple assets assigned to it. This helps in organizing and managing assets based on their physical location.
  • Purchase Order to Line Item: Each purchase order can have multiple line items. This enables a single purchase order to include multiple items or services being procured.

How do I know if a relationship is 1:1 or 1:N?

Cardinality is a term that refers to the relationship between different database tables or objects, defining how many instances of one entity can or must be related with instance of another entity. Understanding and configuring cardinality is essential for setting up relationships between different objects such as assets, locations, work order, etc. ensuring the data structure supports the business and so that people creating object structures can empower users to properly report on their data.

To determine an object’s cardinality:

  1. Navigate to Maximo > Integration > Object Structures.
  2. Find the Object Structure you’re looking for and open it up.
  3. Select an object in the Source Objects list to open the Details.
  4. View, in the Details box, a field called ‘Cardinality.’
    • Cardinality is a pick list of values including Multiple, Single, or Undefined.

With the introduction of this feature, Object Structures using Kurve as the ‘Consumed by’ field have been updated to have a description of ‘Reporting’ rather than ‘Integration’. This change directly supports the ability for Kurve to refer to the cardinality set on the object structure so that relationships are visible and respected. In addition, object structures that we use in Kurve now need to be linked to an Application within Maximo*. The reason for this will come to light by reading the next feature – keep going!

2. Pre-filter Data with Maximo Query Definitions

The ability to pre-filter data is here! Another significant addition to v1.3.0 is the ability to pre-filter data using pre-defined Maximo Query Definitions. Query Definitions allow users to define, manage, and execute custom queries to retrieve specific data from Maximo.

This new feature for Kurve enables you to apply predefined filters to your dataset, either from existing definitions on the object structure itself or from definitions saved on the object structure’s linked Application (*this is what we were hinting at in the previous feature when we said object structures now need to be linked to an application!), when creating reports or graphs. By doing so, you can ensure that your visualizations are focused on the most relevant data, reducing unnecessary noise and improving the retrieval efficiency of your insights. This is particularly useful for users who frequently run reports on specific segments of their data, such as particular asset types, locations, or time periods.

3. New Graph Features

Graphs are a crucial part of any data visualization toolkit, and now there are two new features to make graphs even more compelling in your data storytelling:

Display Graph Totals

In v1.3.0, you can now display measure totals directly on your graphs. This feature is particularly useful for gaining a quick understanding of cumulative values at a glance. Whether you're tracking total cost, aggregate count of work orders, or any other sum-based metric, having the totals visible on the graph makes it easier to communicate the overall impact and trend of the data.

Define Dimension Axis Ranges

Precision and customization are key in effective data visualization. With the new ability to define dimension axis ranges, you can tailor your graphs to better fit the specific scope of your analysis. This user requested feature allows you to set the minimum and maximum values for your axes, ensuring that your graphs focus on the most relevant data points and provide a clearer, more accurate representation of your data.

A Kurve Client requested this feature with regards to the use case that they wanted to display the top 5 results in their graph. For example, let's say you want to see only the top 5 locations with the most work orders. In the edit graph window in the 'Graph Settings' drawer:  

  1. First, sort the dimension descending.
  2. Second, set the max dimension range to 4.

Viola!

4. Quick and Easy Field Relabeling

We understand that clarity in reporting is crucial and sometimes that is difficult when you have multiple fields with the name ‘Description’ in your report, for example. Is this the description field of an Asset or Work Order?!

With Kurve Maximo v1.3.0, you can now relabel Maximo field names in your Kurve report columns with just a few clicks. This feature simplifies the process of making your reports more understandable and tailored to your audience. Instead of using system-generated field names, or having to use the Kurve Custom Column trick to rename the column, you can now create custom labels in Kurve that make sense to your stakeholders, enhancing the readability and professionalism of your reports.

5. Improved App Overview Page with Column Sorting

Navigating through a multitude of visualizations can sometimes be overwhelming. To streamline this, we've introduced the ability to sort columns on the app overview pages. This feature allows you to easily rearrange the list of visualizations, helping you find and prioritize the most important records quickly. Whether you need to sort by name, date, or any other column, this added flexibility makes managing and accessing your visualizations more efficient than ever.

6. Default SQL and Cache Settings for New Graphs and Reports

For Kurve Admins, managing settings across multiple users and reports needs to be easy and efficient. To hold true to this, a feature has been introduced that allows admins to set default SQL and Cache settings to be applied to all new graphs and reports going forward. This ensures consistency and optimizes performance across the board. By standardizing these settings, you can reduce the setup time for new reports and ensure that all users are adhering to best practices for data retrieval and caching.

And that’s a wrap! Kurve Maximo v1.3.0 is an exciting release, a game-changer for anyone looking to elevate their data visualization and analysis capabilities. With the expanded ability to select fields from multiple objects, pre-filtering with Maximo Query Definitions, enhanced graph functionalities, quick field relabeling, improved app overview navigation, and standardized default settings for new records, this release is packed with features designed to help you make graphs and reports you will actually use.

For those who are interested, you can review the full release notes available here.

If you’d like to see these features in action or have questions when upgrading to the latest and greatest, send us an email or schedule a time to chat!

And as always, your feedback is invaluable to us. Keep sharing your thoughts and let us know how we can continue to add to Kurve to meet your needs.

MaximoWorld 2024

In a few short months Kurve will be making its way to Phoenix for MaximoWorld 2024! Whether you are there for Maximo, TRIRIGA, or both, find us at Tower #6 in the Expo Hall for live Kurve demos, lively conversation, and purple swag.

You can also catch us at a few speaker sessions for both Maximo and TRIRIGA:

  • Tuesday, August 6th (9:15-10am MST): How to Know When Your Enterprise is Ready for AI
  • Tuesday, August 6th (2:15-3pm MST): Charting the Course: General Dynamics Mission Systems Navigating Maximo Reporting with Kurve
  • Wednesday, August. 7th (4-4:45pm MST): Empowering the TRIRIGA Experience with AI

Are You Using The Right Tool? 2 Steps To Get Your Reporting Strategy On Track

Read Next

Other Resources

For more information and general inquiries
Contact Us