List View Conditions History

Process Name: 

View Asset Condition History in Detailed View

Feature/User Story Name:

History Tab

Description

The History tab provides a chronological log of all changes made to an asset's Condition Index. It displays a table with details such as the date of change, the Condition Index value, the percentage change from the previous index, and an action column for further insights. This feature enables users to track the condition trends of assets over time, with color-coded indicators for improved (green) or diminished (red) Condition Index values.

Storytelling

Sanjay, a maintenance engineer at SWA, needs to monitor the historical performance of critical assets. With the History tab, Sanjay can now easily view when and how the Condition Index of an asset has changed, empowering him to make data-driven decisions for predictive maintenance and asset optimization.

Actors

• Backoffice User

User Story

As a maintenance engineer,
I want to view the historical changes to an asset's Condition Index,
so I can track trends and analyze when and why changes occurred.

Goal

To provide users with a clear and accessible history of an asset’s Condition Index, including changes over time, enabling better decision-making for maintenance and operations.

Process Flow Diagram

Major Steps Involved

1. User logs into SMART360 > AX module > Monitor > Condition Assessment.
2. User clicks the view button of the required asset.
3. User selects the "History" tab.
4. The system displays a table containing:
   • Date: The date when the Condition Index was updated.
   • Condition Index: The updated Condition Index value.
   • Change: Percentage change from the previous Condition Index value, with color coding.
     • Green: Improvement in the Condition Index.
     • Red: Decline in the Condition Index.
   • Action: Includes a "View" button that redirects to detailed information about the specific change.
5. The asset summary is displayed on the left side, fetched dynamically from the detailed view’s summary of the specific asset.

Business Rules

General Rules

1. Data Source:
   • Asset summary details are fetched from the detailed view’s summary of the specific asset.
   • Condition Index values and percentage changes are fetched from the system’s historical logs.
2. Table Rules:
   • The table must display all logged updates to the Condition Index in reverse chronological order (latest update first).
   • The "Change" column shows the percentage change from the previous Condition Index value, calculated using the formula:
     Example: If the old Condition Index is 5.0 and the new Condition Index is 6.0, the percentage change is: (new - old / old) * 100 i.e ((6-5)/5)*100 = 20%.
   • Changes are color-coded:
     • Green: Positive percentage change (improved Condition Index).
     • Red: Negative percentage change (diminished Condition Index).

Field-Level Rules

1. Condition Index:
   • Displays the value recorded after each update.
   • Range: 0 to 10 (up to 1 decimal place).
2. Change:
   • Displays the percentage change, rounded to one decimal place.
   • Shows "N/A" for the first log entry (as no previous index exists for comparison).
3. Action:
   • "View" button redirects to the detailed log entry, showing the parameters and scores used in that calculation.

Error Handling

1. If no history exists for the asset:
   • Display a message: "No history data is available for this asset."
2. If data fetching fails:
   • Display a message: "Unable to load history data. Please try again later."

Sample Data

1. Asset Name: High-Pressure Pump
2. Condition Index: 6.0 (current)
3. History Table Data:
   • Date: 12-Jan-2025
     Condition Index: 6.0
     Change: +20.0% (green)
     Action: View
   • Date: 05-Jan-2025
     Condition Index: 5.0
     Change: -10.0% (red)
     Action: View
   • Date: 01-Jan-2025
     Condition Index: 5.5
     Change: N/A
     Action: View

Acceptance Criteria

1. The History tab is accessible from the detailed view of an asset.
2. The table displays all historical updates to the Condition Index with accurate values and percentage changes.
3. Percentage changes are calculated correctly using the provided formula and displayed with appropriate color coding (green/red).
4. The "View" button in the Action column redirects to the correct detailed log entry.
5. Error messages are displayed appropriately when data is missing or unavailable.
6. UI aligns with the provided wireframe, and data is dynamically fetched for accuracy.