01 / Case Study
MONITORING SYSTEM - PT KERETA API INDONESIA (KAI)
KaigoFukushishi
Turning ride measurements into a clearer view of railway comfort.
A web-based assessment and analytics platform designed to organize ride quality measurements, route data, and Ride Index results into a structured interface for easier monitoring and analysis.
Role
UI/UX Designer
Context
Machvory × PT KAI
Platform
Web Dashboard
Year
2025
Read Time
7–10 Min
01 / Overview
Making ride quality easier to assess and understand.
Kaigo Fukushishi
The project
Ride Index brings railway ride quality measurements into one connected experience.
The platform supports the assessment process from recording a train measurement to reviewing its results, bringing route information, Ride Index scores, and supporting measurement data into a structured interface.
My focus was on designing an experience that keeps this flow easy to follow — helping users move between assessments, location-based results, and deeper analytics without losing context.
Project details
Role
UI/UX Designer
Timeline
2025
Platform
Web Dashboard
Tools
What I worked on
From assessment flow to the final interface.
02 / Problem & Goal
From measurement
to meaningful insight.
The challenge
The interface needed to connect each stage of the assessment, without losing the context behind the data.
Keeping data connected
Assessment results combine train information, route data, Ride Index scores, and supporting measurements that need to remain connected throughout the experience.
Overview to detail
Users need a quick view of overall results while still being able to move into individual assessments and more detailed analytics when needed.
Data needs context
Ride quality measurements become more useful when users can understand where they occurred along the route, making location an important part of how the information is presented.
The goal
Make every assessment easier to follow from start to insight.
Create a clear experience that connects assessment records, route-based measurements, Ride Index results, and analytics while keeping both overview and detailed information easy to navigate.
Follow the journey
Start with the assessment.Keep the context.Reveal the insight.
Problem → Direction
03 / Process
Designing around the assessment journey.
I started by looking at how users move from an assessment record to its measurement details and eventually into analytics, using that journey to define how information should be organized across the interface.
01 / Information
Mapping what belongs to each assessment.
Each assessment brings together different types of information — from train and route details to Ride Index results, location data, and supporting measurements. I first separated these into meaningful groups before defining how they should appear across the experience.
Raw information
Organize
Assessment Context
Train, operator, assessment time, route, and status provide the context behind each measurement.
Ride Measurement
Ride Index scores, location data, telemetry, and vibration measurements describe the recorded ride condition.
Analysis
Summaries, trends, comparisons, and detailed results help users review measurements beyond a single assessment.
Prioritize
What should users understand first?
Which assessment am I looking at?
What does the ride measurement show?
Where can I explore the result further?
02 / Structure
Connecting the assessment flow.
Once the information was grouped, I explored how users could move naturally from an assessment overview into individual results and deeper analytics without losing the context of the train or measurement they were reviewing.
Exploration / 01
Early direction
Built around the flow.
The early direction focused on establishing relationships between assessment records, detailed measurements, maps, and analytics before refining the visual treatment of each screen.
Principle
Context before detail.Overview before analysis.Keep related data connected.
03 / Refinement
From connected flows to a clearer system.
Refinement focused on making each stage of the assessment feel part of the same experience — keeping navigation, information hierarchy, status treatments, maps, and data presentation consistent across screens.
01 / Early structure
Wireframe
02 / Final direction
Interface
Keep the assessment visible.
Train, route, assessment, and status information remain easy to identify as users move between overview and detailed results.
Move from overview to depth.
Information is presented progressively, allowing users to start with summary results before exploring detailed measurements and analytics.
One system across every view.
Tables, cards, maps, status indicators, and analytics follow a consistent visual structure to make transitions between screens easier to follow.
Assesment → Context → Insight
04 / Design Solution
Bringing the system into one clear view.
The final interface brings monitoring, locomotive conditions, ground events, and operational data together in a structured experience built around the needs of Balaiyasa users.
Dashboard Overview
Everything starts with the overview.
A high-level view of locomotive status and ground event activity, giving Balaiyasa users the context they need before exploring individual locomotives or deeper analytics.
Kaigo Fukushishi / Dashboard
Design decisions
Overview
Important information comes first.
Key status summaries and ground event trends are placed at the top level, so users can understand the overall condition before moving into detailed data.
Status
Conditions are easier to recognize.
Consistent status indicators help distinguish normal, grounded, and offline locomotives without relying on numbers or detailed records alone.
Data Visualization
Trends are easier to compare.
Charts turn ground event data into visual patterns, helping users compare activity across time and locomotives without reading through rows of raw data.
02 / Monitoring
Monitoring at a glance.
The monitoring interface brings locomotive positions, operational status, and ground event information into one view, allowing users to quickly identify current conditions and move into more detailed information when needed.
Scan → Understand → Explore
03 / Data Visualization
Turning data into patterns.
Instead of showing operational data as isolated numbers, charts and summaries help reveal patterns, trends, and differences across ground events over time.
04 / Interface Details
Small decisions, consistent experience.
A consistent visual language across components keeps different parts of the monitoring system connected and predictable.
01 / Monitoring components
Detail
02 / Interface language
Detail
The result
Technical information stays visible without making the experience feel technical.
Clarity over complexity
Structure → Interface
05 / Outcome
Less about showing data. More about making it understandable.
The outcome
A clearer monitoring experience where users can understand the overall condition before diving into the details.
Information no longer competes for the same level of attention.
Hierarchy, grouping, and status guide users toward what matters first.
What I learned
Three principles I'd carry into the next product.
Clarity before decoration.
With technical information, deciding what deserves attention matters more than adding more visual elements.
Context makes data useful.
Status, hierarchy, and supporting context help users understand what the numbers actually mean.
Design the system, not just screens.
Reusable patterns and clear relationships create a more consistent experience across the product.
Reflection
Good monitoring design isn't about showing everything. It's about helping people know what to look at first.
End of case study
One project done.
A few lessons kept.
Kaigo Fukushishi
End / 03
Next / 01
Continue exploring
Another project,
another problem to solve.
Continue to the next selected project.
Project / 01
Ground Detector
2025