+,-.-01- +2343562728293
+2343524:,93;9:6=4;63; 9=6;?,93;9:165;293
A--.110 B+--.C0,101 A--.110 B+--.C0,101
A--.110 B+--.C0,101 A--.110 B+--.C0,101
A-,-+110 A-,-+110
A-,-+110 A-,-+110
Prepared Checked
Approved
Warnoto Feriyal S
Bayu Eko P
I. BACKGROUND
II. CLARIFY THE PROBLEM
Problem To Tackle
V. ROOT CAUSE ANALYSIS
Compilation PCA FY 2006 Compilation PCA FY 2007
Each year the asset was held checks, called Physical Check Asset PCA. This activity aims to controlling assets. Material that used for PCA activity is worksheet. Worksheet is compare results between SAP data and asset map. Asset map as one of the tools in PCA to control the asset management. There are several problems in asset map, one of them is duplicated asset number as a result from PCA. This case
was happened every year in this study it has limited at 2006-2009 and it is still uncovered. Duplicated number of these assets will have an impact on checking the next PCA, and result in less accurate in asset management, and decrease performance of management handling.
There are activities that are inconsistent with the SOP on the process of tagging Compare Data
Machine Man
Material Method
People are less concerned about
1. Prefer in other job Creating an asset
number to Retagging Process
Asset map has duplicated number
Current Idea
Do GENBA and coordination meeting to validate the data eliminate duplicating asset + Redundancy number can be solved
number in PCA 2009 data result + Data compilation would be validated and can be used for database master
asset map + User can update asset map too from as an impact from this activity
+ User and related division can learning more on map maintenance - Involve people in another division to do coordination meeting Genba activity
Impact Status
No. Problem
Idea improvement
1 In preparation process, there is no
duplication checking numbers Asset map has
duplicated number
Supports companies in managing the assets owned by reducing some of the problems
ULTIMATE GOAL
IDEAL CONDITION
100 Data PCA No Duplicate
CURRENT CONDITION
85,38 Data PCA No Duplicate GAP
PROBLEM 14.62 PCA FY
2009 have duplicated asset
II. CLARIFY THE PROBLEM
VI. DEVELOP COUNTERMEASURE