MotionTracking | Ankita Nalawade 2

Motion Tracking

An enterprise asset lifecycle management system designed to streamline the acquisition, allocation, and retirement of heavy equipment across large-scale infrastructure projects, delivered through a centralized web platform for real-time visibility, control, and data-driven decision-making.

Asset Management

Enterprise UX

PROJECT DETAILS

My Role:

Duration:

Location:

Platform:

UX Designer

1 Year

Pune, India

Team:

Stakeholders

1 UX Designer (Me)
1 BA
2 QAs
2 Developers
Project Manager
Delivery Manager

Site Fleet
Site Planning (Site PS/Planner), RCM-Project In Charge, Project Manager
Site Store, BU - Fleet SPOC, SBG - Fleet Head, and F&RM Head
Allocation Team

Stakeholders:

Design System:

PROJECT SNAPSHOT

PROBLEM

Fragmented asset tracking
24 - 48 hr approval delays
No structured allocation decisions
Poor lifecycle visibility

SOLUTION

Designed a unified fleet management platform integrated with SAP systems to digitize and streamline asset lifecycle processes, enabling role-based workflows, real-time tracking, and standardized decision-making across teams.

IMPACT

Impact estimates were established through operational workflow analysis, stakeholder validation, and comparative assessment of decision-making, approval, and coordination processes

35 - 50%

Allocation Decisions

0 → 100%

End-to-end asset lifecycle visibility

~35%

Approval turnaround time

~25–40%

Operational errors and offline dependency

~40%

Cross-team coordination effort

4 -6 hrs/week

Productivity per user

BUSINESS GOALS

Improve asset utilization across projects

Reduce asset procurement and allocation cycle time

Increase end-to-end asset lifecycle visibility across system

Reduce dependency on manual co-ordination

Enable faster and consistent Buy vs Lease vs Transfer decisions

Standardize surplus and scrap management processes

PROJECT GOALS

01. Execution Layer

For Site Fleet

Create and edit asset demand and scrap requests with required project and equipment details
Track and monitor the status of submitted demand and scrap requests across workflow stages

02. Approval Layer

For Project Manager
(Asset Acquisition Demand & Transfer)

Review, approve, or reject asset demands with full contextual clarity
Maintain accountability through structured approval history and feedback

For Project Manager
(Asset Retirement: Scrape Equipment)

Evaluate scrap requests against asset condition and project context
Execute approval decisions (approve/reject/send back) to drive status updates and initiate downstream workflows

02. Decision Layer

For Allocation Team
(Asset Acquisition Demand and Transfer)

Check real-time asset availability across BU/SBU and project locations
Execute fulfillment decisions by initiating: lease extension, procurement, or asset transfer instructions

WIREFRAMES

DASHBOARD

Designed a role-based, scalable homepage that prioritises key actions, aligns with asset lifecycle workflows, and integrates seamlessly with SAP systems.

Role-Based Personalisation
Homepage adapts based on logged-in persona and permissions

Tile-based layout enables easy addition of new workflows without redesign

Tiles represent primary user actions, not just features

Asset Acquisition Demand and Transfer

Collapsible, customizable filter bar with explicit search enables efficient navigation across large datasets while optimising screen space and system performance

Serves both as a unique reference ID for cross-team communication and a direct navigation trigger, reducing friction between operational tasks and system interaction

A header-level CTA scopes creation to the list context, maintaining clarity and prominence while avoiding global UI dominance

Row-level chevrons provide a lightweight, consistent pattern to access detailed views without overloading the list interface

Colour is applied semantically to encode status, urgency, and interactivity, enabling rapid, at-a-glance decision-making across dense data views

A classic list-to-detail pattern enables efficient scanning of large datasets while preserving depth and clarity for complex record-level information

Content is partitioned into task-oriented tabs to reduce scrolling, support focused workflows, and enable quick access to relevant information

Edit is exposed as a contextual secondary action, visible only in editable states to maintain workflow integrity and prevent invalid modifications

Approval History is structured as a dense table to prioritise precision, traceability, and ease of reference over visual storytelling

Asset Acquisition Demand Creation

EXECUTION LEVEL

The Site Fleet is granted full demand lifecycle ownership, from initiating requests from scratch and retaining edit authority over any demand returned for correction ensuring the originating persona remains the single accountable actor from first submission through to resubmission, without requiring system intervention or role escalation

A two-column layout organises related fields and reduces scroll depth, optimising form completion for enterprise-scale data entry

Auto-populated, read-only fields minimise manual input, reduce errors, and accelerate form completion in operational contexts

Auto-save with visible draft status ensures data persistence and protects against interruption in long-form entry workflows

Prototype of Request Creation Flow

APPROVAL LEVEL

The flow further scales into the approval layer, where Project Managers operationalise decision-making through a structured, state-driven workflow

Approved Quantity is editable at the point of decision, collapsing approval and quantity confirmation into a single interaction to reduce workflow cycles

Scenario 1 : Approved Demand

The Approval History will be updated and will showcase the name(s) of the next person incharge of the request, to maintain transparency throughout the system

Scenario 2: Send Back

“Send Back” is designed as a lightweight modal action, allowing quick input of reason and comments while keeping users anchored to the decision context

DECISION LAYER

The flow then progresses into the allocation layer, where approved demands are converted into actionable fulfilment decisions within a structured, multi-level system

Demand Details Page

Role-driven tab defaults prioritise actionable data, surfacing the Requirements view for the Allocation Team to enable immediate decision-making while maintaining a consistent structure across personas

Requirements Details Page

Requirement-level actions are handled in a full-page layout to support complex inputs, multi-step decisions, and uninterrupted task execution within deep workflows

A fixed context header surfaces key quantity constraints across all levels, eliminating backtracking and ensuring accurate allocation decisions

Operationally intensive decisions (e.g., Transfer) trigger dedicated sub-flows to capture granular asset-level data without overloading primary workflows

Add Decision

Supports multiple decision types per requirement, enabling realistic, split allocation based on availability and operational constraints

Add Asset

A shared, template-driven form adapts to asset types (SOA/MOA), ensuring consistency while accommodating data-specific variations without duplicating interfaces