Project

General

Profile

Bug #2564

Machine Performance Metrics with Downtime & Utilization Calculation

Added by Prashant Jain about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Start date:
05/04/2026
Due date:
% Done:

0%

Estimated time:
Spent time:

Description

Description:
Implement machine performance metrics to evaluate utilization and availability by incorporating charging hours, downtime, and total hours. This will provide accurate insights into machine efficiency and operational health.

Requirements:

Data Calculation Logic
Total Hours (e.g., 24 hrs/day)
Downtime Hours (fault, offline, maintenance)
Available Hours = Total Hours − Downtime
Charging Hours (from session data)
KPIs to be Calculated
Availability () = (Available Hours / Total Hours) × 100
Utilization (
) = (Charging Hours / Available Hours) × 100
Efficiency (%) = (Charging Hours / Total Hours) × 100
Data Sources
Charging session logs
Machine status / fault logs
Uptime/downtime tracking
Backend Changes
Create aggregation logic for daily machine summary
Store results in a reporting table (e.g., machine_daily_summary)
Optimize queries for performance
API Development
New endpoint to fetch machine performance metrics
Support filters:
Date range
Machine ID
Location
Dashboard Integration
Display KPIs:
Availability %
Utilization %
Efficiency %
Provide daily/weekly trends
Edge Case Handling
Avoid division by zero
Handle missing/partial data
Consider overlapping downtime sessions

Acceptance Criteria:

KPIs are calculated correctly using downtime-inclusive logic
Data is available daily per machine
APIs return accurate and optimized results
Dashboard reflects correct values and trends
System handles edge cases without failure

Notes:

Prefer using actual uptime instead of fixed 24 hrs where applicable
Ensure downtime classification is accurate (planned vs unplanned)

#1

Updated by Shreya Agarwal about 1 month ago

Worked on implementing Machine Performance metrics API using charging sessions and downtime data . completed core logic for calculating Availability , utilization , and efficiency with filter support(today , week , month , etc.) . verified filter-based date handling (IST to UTC conversion ) for accurate data retrieval . Currently pending minor logic refinements and integration. final testing and validation are in progress . Also worked on the Station Comparison API, where a few minor fixes and improvements were identified and implemented.

#2

Updated by Shreya Agarwal about 1 month ago

worked on charger utilization API and implemented calculation logic for overall and utilization metrics . Fixed downtime duplication issue by implementing overlap-based downtime calculation .modified API to return  single - row per charger instead of separate overall and utilization records.
Added multiple filter handling and verified calculation with different data ranges.

#3

Updated by Shreya Agarwal about 1 month ago

worked on implementing and validating the this Year time Range filter in the charger utilization API, verified consistency across other filters like this month and last month. I also reviewed and validated previous updates related to machine id integration across downtime and charging session queries . I also try to analyzing the custom session report controller flow, focusing on how metadata, templates are structured, though only a basic understanding has been built so far and most logic is still under analysis.

#4

Updated by Shreya Agarwal about 1 month ago

Today I worked on implementing UTC time conversion logic for the custom session report API. I tried to understand and analyze the code that how the existing date filtering and report generation flow is working. While integrating the time zone-based conversion, I faced some issues and the UTC conversion is still not working as expected and remains under development. Along with implementation, I also spent time reviewing and try to understand the overall code structure to better understand the report logic, filtering flow, and how different components interact with each other in the custom report generation process.

#5

Updated by Shreya Agarwal about 1 month ago

Today I started learning React JS fundamental and explored the basics concepts required for frontend development . practiced JSX syntax , Components creation , props handling , use State and basic CSS styling . Also worked on understanding React project structure . Additionally I working on a Registration Form in React JS currently the form is partially completed and the remaining implementation will be continue further.

#6

Updated by Shreya Agarwal about 1 month ago

continued learning React JS through online resources and explored how implementation works in real time application . I covered several react concepts and practiced understanding component structure and functionality . Along with learning , I also started working on creating registration form in React JS for hands-on practice . Currently the form development is in progress and also I try to understand tailwind CSS in react JS .

#7

Updated by Shreya Agarwal about 1 month ago

continued working on React JS and focused on implementing a trainee registration form with real-time functionality. I successfully added form handling using use State, validation for required fields. However, some validations are still pending, and I need to improve error handling for better user experience. The delete button functionality for removing table records is also yet to be implemented. Additionally, a few UI improvements and CSS styling enhancements are still remaining to make the form more responsive and visually clean. I am continuously learning React JS through practical implementation of this registration form project and improving my understanding .

#8

Updated by Shreya Agarwal about 1 month ago

Today I continued working on the trainee registration form, improving the UI with consistent input styling, better color theme, and aligned font sizes. I implemented field-level validation with error messages displayed below each input, which improved the overall user experience. I also added a delete functionality in the data table and enhanced the table design with a cleaner layout and hover effects. Additionally, I worked on refining button styles and integrating a consistent color scheme using OKLCH values.

Also available in: Atom PDF