TM

CEMENTYCS
MINIMUM VIABILITY PRODUCT
FINDINGS FROM THE INITIAL CUSTOMER
SURVEYS (ICS)
• Customer Survey Lists the following as the Key Parameters Impacting Timeliness
• Composition of Cement during delivery
• Mix-Ratio Matrix
• Temperature of the Mixture during delivery
• Moisture in the mixture
• Distance of plant to the site
• Total delivery Time (Movement time)
• Total Non Value added time (Wait time on road, Wait time at customer end)
• Time of delivery (Morning, Afternoon, Evening, Night)
• Daily Delivery Volume
• Seasonality of demand
• Age of the vehicle delivering the mixture
• Initial Quality Issues at the plant site
• Linearity of delivery from Plant Side
• Driver Handling the consignment
SCOPE OF MVP
QUALITATIVE

IMPROVE “TIMELINESS” IMPROVE VALUE TO CUSTOMER

1.Create a Digital Prototype to measure timeliness of 1.Help Sponsor in identifying KPIs for monitoring
“Cement Value Chain” from Plants to the Sites (Customer) 2. Enable a digital tracking and help in the overall value
2. Create a Front End Mobile App along with a backend creation for the cement industry
tool 3. Increase overall improvement of fleet management
3. Compatibility with current Production ERP

QUANTATIVE

1.Reduce Rejection due to Timeliness at Customer End (Site) by 20%

TIMELINES

1.Delivery of MVP within 10 Weeks

VALIDATION AND READINESS FOR PRODUCTION

1.Validation of Performance within 10 Weeks of delivery of MVP

 Inbound MFG Outbound
Current Process

Central Call Demand Daily Production

Central Dispatch
Centre Schedule Planning
Office (CDO)
to Plants

CUSTOMER

PLANT 1 PLANT 2 PLANT 3 PLANT 4 PLANT 5

S5 S10
S1 S10
S6
S9 S11

S4
S2

S8 Sn
S7
S3 S13
Definition of KPI (Key Performance Indicators)
KPI
Does It Contribute WHETHER VARIABLE VALUE ADDING CAN BE WHO CONTROLS CTQ
KEY FINDINGS (KEY PERFORMANCE
TImeliness OR NOT VARIABILITY? CONTROLLED IT? (Critical to Quality)
INDICATORS)
Composition of Cement during CALCIUM, POTASH, DEMAND
YES YES YES YES YES
delivery FLYASH, SILICA (CUSTOMER)
DEMAND
Mix-Ratio Matrix SAND VS CEMENT YES YES YES YES YES
(CUSTOMER)
Temperature of the Mixture during
Degrees Celcius YES YES YES YES SUPPLY (TRUCKS) YES
delivery
Moisture in the mixture at the time DEMAND
Water/CBM CEMENT YES YES YES YES YES
of delivery (CUSTOMER)
DEMAND
Distance of plant to the site KM YES NO NO NO YES
(CUSTOMER)
Total delivery Time (Movement DEMAND
MINUTES YES NO NO ? YES
time) (CUSTOMER)
Total Non Value added time (Wait
time on road, Wait time at customer MINUTES YES YES NO YES SUPPLY (TRUCKS) YES
end)
Time of delivery (Morning, DEMAND
TIME NO NO NO NO YES
Afternoon, Evening, Night) (CUSTOMER)
DEMAND
Daily Delivery Volume CUBIC CM CEMENT/DAY YES YES ? NO YES
(CUSTOMER)
CUBIC CM DEMAND
Seasonality of demand YES YES NO NO NO
CEMENT/MONTH (CUSTOMER)
Age of the vehicle delivering the
YEARS YES YES NO MAY BE SUPPLY (TRUCKS) YES
mixture

Initial Quality Issues at the plant site Quality Parameters NO YES YES YES PRODUCTION YES

Linearity of delivery from Plant Side TAKT TIME NO YES NO YES PRODUCTION YES
Driver Handling the consignment NAME NO YES NO NO SUPPLY (TRUCKS) NO
Preliminary Feature Basket

Based on KPI Matrix 4 Features can be eliminated as they do not contribute to the “timeliness”

 Time of delivery (Morning, Afternoon, Evening, Night)

 Initial Quality Issues at the plant site
 Linearity of delivery from Plant Side
 Driver Handling the consignment

No of Features after Initial Sorting= 10

4 Advanced Prioritization Tools will be used to derive a the Final Feature list for MVP in the order mentioned

1. Relative Weigh Tool

2. Mo-S-Co-W
3. Einsenhower Decision Model
4. KANO MODEL
Relative Weigh Matrix
KPI
Does It Contribute INCREASE EASE OF Priority
KEY FINDINGS (KEY PERFORMANCE CUSTOMER VALUE UNIQUENESS RANK SORT
TImeliness TIMELINESS INTEGRATION Number
INDICATORS)
Composition of Cement during CALCIUM, POTASH,
YES 5 5 3 3 225 3
delivery FLYASH, SILICA
Mix-Ratio Matrix SAND VS CEMENT YES 5 5 5 3 375 1
Temperature of the Mixture during
Degrees Celcius YES 5 5 5 3 375 1
delivery
Moisture in the mixture at the time
Water/CBM CEMENT YES 5 5 5 2 250 2
of delivery
Distance of plant to the site KM YES 5 5 3 5 375 1
Total delivery Time (Movement
MINUTES YES 5 5 1 5 125 4
time)
Total Non Value added time (Wait
time on road, Wait time at customer MINUTES YES 5 5 1 3 75 5
end)
Daily Delivery Volume CUBIC CM CEMENT/DAY YES 2 1 5 3 30 5
Seasonality of demand CUBIC CM CEMENT/MONTH YES 2 2 2 1 8 6
Age of the vehicle delivering the
YEARS YES 1 1 4 1 4 6
mixture

Based on the Relative Weigh Tool 2 Features with Rank-6 Can be eliminated
Mo-S-Co-W
• Mix-Ratio Matrix
• Temperature of the Mixture during delivery
• Moisture in the mixture at the time of delivery
• Distance of plant to the site
Must Have
• Total delivery Time (Movement time)

• Composition of Cement during delivery

• Moisture in the mixture at the time of delivery
Should Have

• Total Non Value added time (Wait time on road, Wait time at customer end)
Could • Daily Delivery Volume
Avoid

• Seasonality of demand
• Age of the vehicle delivering the mixture
Would Avoid

3 or More Greens- Must, 2 Greens-Should

Eisenhower Decision Model
  URGENT NOT URGENT

REDUCE
Mix-Ratio Matrix SCHEDULE
IMPORTANT Temperature of the Mixture during delivery Composition of Cement during delivery
Distance of plant to the site Moisture in the mixture at the time of delivery
Total delivery Time (Movement time)

EXTENSION DECLUTTER
NOT IMPORTANT Total Non Value added time (Wait time on road, Seasonality of demand
Wait time at customer end) Age of the vehicle delivering the mixture

Based on the Decision Model, Reduce and Schedule can be considered in MVP
Extension Can be taken up as feature Upgrades
Declutter should be completely avoided
KANO MODEL
ATTRACTIVE PERFORMANCE

Mix-Ratio Matrix
Temperature of the Mixture during
Total Non Value added time (Wait delivery
time on road, Wait time at Moisture in the mixture at the time of
customer end) delivery
Daily Delivery Volume Distance of plant to the site
Total delivery Time (Movement time)

However, as an attractive Feature and a high

value of “Timeliness” Score, Total NVA Time is INDIFFERENT MUST BE
requested to added in the MVA
Seasonality of demand Composition of Cement during delivery
Age of the vehicle delivering the Moisture in the mixture at the time of
mixture delivery
Finalization of Features for MVP
• Composition of Cement during delivery
• Mix-Ratio Matrix
• Temperature of the Mixture during delivery
• Moisture in the mixture
• Distance of plant to the site
• Total delivery Time (Movement time)
• Total Non Value added time (Wait time on road, Wait time at customer end)
• Time of delivery (Morning, Afternoon, Evening, Night)
• Daily Delivery Volume
• Seasonality of demand
• Age of the vehicle delivering the mixture
• Initial Quality Issues at the plant site
• Linearity of delivery from Plant Side
• Driver Handling the consignment
Delivery Mode- Constraint Analysis

Hardware API
Currently developed apps for geo-Tracking could
Since the development time is 10 days- off the shelf
be used
Hardware to be used for Chemical and Temperature
Recording New API required for Total NON Value Added time

CONSTRAINT
S

Software Requirement Analytics

New Software requirements for Chemical Current Analytics tools to be used
Composition to be checked for feasibility
Development of Hardware
FEATURES EXISTING DEVELOP BUY NEW HARDWARE DESIRED
Composition of Cement during delivery SENSOR NPK 3600
Mix-Ratio Matrix SENSOR NPK 9128
Upgrade for
Temperature of the Mixture during delivery YES recording the same
on End of Line ERP
Upgrade for
Moisture in the mixture YES recording the same
on End of Line ERP
USE CURRENT GEO-
Distance of plant to the site
LOCATION API
USE CURRENT GEO-
Total delivery Time (Movement time) A Fleet Management App
LOCATION API
is desired
If the vehicle donot
Total Non Value added time (Wait time on road, USE CURRENT GEO-
move for 5 Mins, a
Wait time at customer end) LOCATION API
record to be mapped

Note: NPK 3600/9128 are fictional. Actual Research needs to be made regarding the same
NEW API Requirement

Following New APIs Required

1. To record output of NPK 3600

2. To record output of NPK 9128
3. Geo- Tracking Apps to be integrated with Fleet Management Hardware
4. Geo- Tracking to be modified inline with Time Required to travel from Plant to Site
5. To record Chemical Composition, Temperature and Moisture during delivery at customer end
6. Non Value Added- An Algorithm needs to be develop to record delays if the standing time exceeds 5 Mins
7. A overarching API to record and push the data to cloud
Software Requirement

Upgrade current software at END OF LINE to track the Chemical Composition of the mixture and
tag it with ERP Dispatch number

Upgrade the existing ERP Software to accommodate the changes

A new GUI to record output of all sensors

 RASIC Chart
Deliverables Resposnible Accountable Supporting Informed Consulted
Presentation of Aproval Product Manager        
Approval of Proposed MVP Management/Sponsor Product Manager Program Manager Resources  
Ordering of the Hardare BACKEND 1 Product Manager PURCHASE DEPT BACKEND 2  
Raise of Purchase Request Product Manager PURCHASE DEPT   BACKEND 1 and 2  
Development of API-1,2,3 and 5 BACKEND 1 BACKEND 1   BACKEND 2 Management/Sponsor
Development of API-4, 6 BACKEND 2 BACKEND 2   BACKEND 1 Management/Sponsor
Development of API-7          
Upgradation of Software for ERP Front End 1 Front End 1 BACKEND 1 and 2 FRONT END 2  

Checking if the data is correctly pushing Front End 2   BACKEND 1 and 2 FRONT END 1  
data to cloud in desired format

Overall GUI Visual Designer Visual Designer FRONT END 1 and 2 BACKEND 1 and 2 Management/Sponsor
Analytics Business Analyst Product Manager Product Manager All team  
Prelimenary Approval of the MVP Product Manager Product Manager      
Final Approval of the MVP Management/Sponsor Product Manager     Program Manager
Deliverables Milestones
Deliverables W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 Whether Stage or Gate
Presentation of Approval 0                   Gate
Approval of Proposed MVP 0                   Stage
Ordering of the Hardare                     Stage
Raise of Purchase Request                     Gate
Availability of Hardware                     Stage
Testing of Hardware                     Stage
Go-Ahead for Hardware                     Gate
Development of API-1,2,3 and 5                     Stage
Development of API-4, 6                     Stage
Development of API-7                     Stage
Approval of All API                     Gate
Feasibility Study on Current ERP                     Stage
Upgradation of Software for ERP                     Stage

Checking if the data is correctly pushing data to cloud in desired                     Stage

format

Approval of All software updgrade                     Gate

Overall GUI Development                     Stage

Approval of GUI by Management                     Gate
Start of Analytics                     Stage
End of Analytics                     Stage
Prelimenary Approval of the MVP                     Gate
Final Approval of the MVP                     Gate
 Risk Documentation Matrix
RISK Description of Risk LIKELIHOOD CONSEQUENCE RISK RATING MITIGATION
Customer Survey Data points are
The whole
assumed. Need further inputs on
Customer Survey development Gather additional Data
whether a Qualitative or LOW HIGH
Database incorrect needs to be Sign off with Sponsor
Quantitative approach has been
scrapped
approached
Gather Online reviews,
Since Commercially available Technical Specs and
New Hardware not Validation may
hardware are being used, the LOW Medium documentation. Early
performing as wanted need more time
output data might not be optimized documentation of failure
modes
Overall
Collective time for development of Physical Testing
API performance not upto performance of
API is low. Hence confidence will LOW LOW Signoff with Sponsor If API
the mark the product can go
be gathered overtime is underperforming
down
Undertake the development
Software upgradation may impact May affect in a trough season
Software upgradation MEDIUM LOW
current production demand planning Seasonal demand analysis
to be done
Assumptions ofResources for
Overall delivery Proper Resource Planning
Resource Availability Backend and Front Processes LOW LOW
may be impacted to be ensured
going in Parallel
The Customer Survey data is
Overall
Availability of Technical highly dependent on the sponsor. Customer Visit and Deep
performance of
Knowhow about the InHouse understanding of the MEDIUM LOW Customer Understanding to
the product can go
CEMENT Industry issue may be required to deliver an be ensured
down
optimized product
How will the MVP be tested?

AESTHETICS Capture Vital “Aesthetics” points to improve usability and customer ease

Does the Product get used by the stakeholders- Production, Drivers,

USABLE Customers atleast during 50% of deliveries in Phase 1, 70% in Phase 2 and
90% in Phase 3

Uptime(>99%) and Real Time Data Capturing (~100%)

RELIABLE
All the KPIs mentioned in the feature basked satisfied and record correct
FUNCTIONAL data
UAT
Acceptance Internal
Criteria Validation Team From User Approver
• Internal Testing Team of 4
Identify 3 More
Members test the MVP as defined Aesthetics Features for Future Identify 5 More Features for
Future Roadmap
Sponsor
Roadmap
• Stakeholders inputs are taken for
Qualitative inputs (ease of use) Usable- Phase 1 50% 50% Product Manager

Usable- Phase 2 70% 70% Product Manager

• Real Time data monitoring and Usable- Phase 3 90% 90% Product Manager
uptime to be derived from System Reliable 99% 99% Reliability Head
• Overall rejection from End Real Time Data 100%   Reliability Head
Customer based on Historical data Capturing

Document Customer issue

Functional- Check if all KPIs are
Monitoring of 7 KPIs monitored real time via ORC (Open, Resolve, Product Manager
Closed) Mode

Qualitative/Quantitative data for rejection to be ensured for each delivery via daily
feedback
MVP Success Parameters
CANNOT BE
PARAMETERS L5 Performance L3 Performance
ACCEPTED
Create a Digital Prototype to measure "timeliness" of
If the Digital Product
“Cement Value Chain” from Plants to the Sites    
(Customer) is not delivered
Fully Functional with
Create a Front End Solution along with a backend Fully Functional with UI UI not getting
 
tool approval my management approved by
management
Compatibility with current Production ERP 3 or less changes in current 3-5 changes in >5 Changes in current
ERP current ERP ERP
100% Uptime for 7 95% Uptime for 7 <95% Uptime for 7
Recording and Documentation of all KPIs
Features Features Features
Reduce Rejection due to Timeliness at Customer
20% or More Than 20% 10-20% <10%
End (Site) by 20%
Approval of MVP In 2 Iterations in 2-4 Iterations > 4 Iterations
Readiness for Production in less than 10 Weeks in 7-10 Weeks > 10 Weeks
Way Forward

• After Completion of UAT and establishment of correlations, 5 Features identified

during UAT to be taken
• Reconsideration of features rejected during KANO/Eisenhower Model for final
prototype
• Reliability testing to be continued
• Creation of Feature Roadmap 1.0
• Monitor customer benefits for 6 Months (Reduce Rejection and Improve
Timeliness)
• Completion of Final Product with Improved UI in upcoming 10 Weeks and
readiness for Production
THANK YOU