Detailed History View

Process Name: 

View Asset Condition History in Detailed View

Feature/User Story Name: 

Detailed View History

Description:
The Detailed View History feature allows users to access a comprehensive history of the Condition Index for a specific asset. By clicking the eye button in the Action tab, users are redirected to the Conditions tab, where they can view the parameters like category, subcategory, weightage, and preference scores that contributed to calculating the particular Condition Index.

Storytelling:
Sanjay, a maintenance engineer at SWA, needs to understand the changes in the asset's Condition Index over time. By accessing the Detailed View History, Sanjay can click the eye button in the Action tab to trace the parameters that contributed to the Condition Index, such as categories, weightages, subcategories, and preference scores, giving him a deeper insight into the condition of the asset and its performance trends.

Actors:

• Backoffice User

User Story:
As a maintenance engineer,
I want to access the detailed history of an asset’s Condition Index,
So I can view the contributing parameters and scores used to calculate that Condition Index, helping me analyze its changes over time.

Goal:
To provide users with an accessible and clear breakdown of the parameters contributing to a specific Condition Index, enabling better insights into the asset’s historical performance and condition.

Process Flow Diagram:

Major Steps Involved:

1. User logs into SMART360 > AX module > Monitor > Condition Assessment.
2. User clicks the eye button in the Action tab for a specific asset.
3. Navigates to history tab > clicks eye button of specific instance.
4. The system redirects the user to the Conditions tab, displaying the parameters contributing to the Condition Index.
5. The table contains:
   • Category: The primary grouping of the parameter.
   • Category Weightage: Weightage assigned to the category.
   • Subcategory: Specific parameter under the category.
   • Subcategory Weightage: Weightage distributed within the category.
   • Preference Score: User-defined preference score for the subcategory.

Business Rules:

• Data Source:
  Asset summary details are fetched from the detailed view’s summary of the specific asset.
  Parameters (categories, subcategories, weightages, preference scores) are fetched from the Condition Index calculation.
• All the parameters, weightages and scores displayed here are the data used to calculate condition index on that specific date
• Display Rules:
  The table must display all active parameters contributing to the Condition Index calculation for the selected date.
  The Condition Index value must be highlighted beside the asset name.
• Field-Level Rules:
  • Category and Subcategory: Fetched dynamically based on the asset and date selected.
  • Weightages: Displayed as percentages.
    • Sum of category weightages = 1
    • Sum of subcategory weightages within a category = 1
  • Preference Score: Displays the score assigned by the user (range: 0-10).

Error Handling:

• If fetching data fails:
  Display a message: "Unable to load conditions data. Please try again later."

Sample Data:

• Asset Name: High-Pressure Pump
• Condition Index: 6.0

Table Data:

• Category: Electromechanical, Weightage: 0.5
• Subcategory: Motor Condition, Weightage: 0.3, Preference Score: 2
• Subcategory: Horsepower Efficiency, Weightage: 0.2, Preference Score: 2

Acceptance Criteria:

• Users can access the Detailed View History by clicking the eye button in the Action tab.
• The table displays the contributing parameters for the selected Condition Index with accurate values for category, subcategory, weightage, and preference scores.
• The Condition Index value matches the calculated value for that specific asset and date.
• Error messages are shown appropriately when no parameters are found or when data fetching fails.
• The UI aligns with the wireframe, and data is dynamically fetched.