Scribd
Upload
50 views12 pages

Minimag 1 & 2 Performance Report

This document contains production data from three shifts (A, B, C) for a machine called Minimag 1 on January 16, 2015. It shows the target and actual production output for each hour of operation. The total target output for the day was 43.2 units but the actual output achieved was only 20.7 units. Some downtime was experienced due to issues with devices ACu 2,6 and a taper loss during one hour of the first shift.

Uploaded by

Omar Ramirez Sarmiento
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
50 views12 pages

Minimag 1 & 2 Performance Report

This document contains production data from three shifts (A, B, C) for a machine called Minimag 1 on January 16, 2015. It shows the target and actual production output for each hour of operation. The total target output for the day was 43.2 units but the actual output achieved was only 20.7 units. Some downtime was experienced due to issues with devices ACu 2,6 and a taper loss during one hour of the first shift.

Uploaded by

Omar Ramirez Sarmiento
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 12

Machine: Minimag 1 (OH443)

Friday, January 16, 2015


Batch No.: SO No.:

Per Hour Per Hour Total Total


Shif Time Target Output Rem
Target Output Per Shif Per Shif

6:00 AM - 7:00 AM 1.8 1.30


7:00 AM - 8:00 AM 1.8 1.60
8:00 AM - 9:00 AM 1.8 1.40 Device lo
9:00 AM - 10:00 AM 1.8 1.40
A 14.4 10.4
10:00 AM - 11:00 AM 1.8 1.60
11:00 AM - 12:00 PM 1.8 1.60
12:00 PM - 1:00 PM 1.8 1.60
1:00 PM - 2:00 PM 1.8 1.20

Batch No.: SO No.:


Total Total
Per Hour Per Hour Target
Shif Time Output Rem
Target Output Per Shif Per Shif

2:00 PM - 3:00 PM 1.8 1.50


3:00 PM - 4:00 PM 1.8 0.75
4:00 PM - 5:00 PM 1.8 0.26
5:00 PM - 6:00 PM 1.8 1.30
B 14.4 10.3
6:00 PM - 7:00 PM 1.8 1.60
7:00 PM - 8:00 PM 1.8 1.60
8:00 PM - 9:00 PM 1.8 1.70
9:00 PM - 10:00 PM 1.8 1.60

Batch No.: SO No.:


Total Total
Per Hour Per Hour Target
Shif Time Output Rem
Target Output Per Shif Per Shif

10:00 PM - 11:00 PM 1.8


11:00 PM - 12:00 AM 1.8
12:00 AM - 1:00 AM 1.8
1:00 AM - 2:00 AM 1.8
C 14.4 0.0
2:00 AM - 3:00 AM 1.8
3:00 AM - 4:00 AM 1.8
4:00 AM - 5:00 AM 1.8
5:00 AM - 6:00 AM 1.8

Total Target Per Day Total Output Per Day

43.2 20.7
43.2 20.7

Issues/Errors Actions Done Duration (min)


ACu 2,6 down
43)

Output (Kpcs)
Remarks
Minimag 1 Performance -
2.00
1.50
1.00
Device lost Taper
0.50
0.00

10:00 AM

11:00 AM

12:00 PM
7:00 AM

8:00 AM

9:00 AM
Date

Output (Kpcs)
Remarks
Minimag 1 Performance -
2.00
1.50
1.00
0.50
0.00

8:00 PM
3:00 PM

4:00 PM

5:00 PM

6:00 PM

7:00 PM
Date
Output (Kpcs)

Remarks
Minimag 1 Performance -
2
1.5
1
0.5
0
11:00 PM

12:00 AM

2:00 AM

5:00 AM
1:00 AM

3:00 AM

4:00 AM

Date

utput Per Day

20.7
20.7

Status (Ok/Not OK) Remarks


ok Issue/Errors: Major to Minor downtime list en
Actions Action implemented and how lon
Duration May not be the time per activity
Status Was the problem did not re-occu
formance - A-Shif

Per Hour
Output
Per Hour Ta rget
11:00 AM

12:00 PM

1:00 PM

2:00 PM

formance - B-Shif

Per Hour
Output
Per Hour Ta rget
10:00 PM
8:00 PM

9:00 PM
7:00 PM

formance - C-Shif

Per Hour
Output
Per Hour Ta rget
5:00 AM
3:00 AM

4:00 AM

6:00 AM
owntime list encountered for the particular shif
ed and how long it takes to solve the problem
me per activity but the total time until the error is fixed
did not re-occur again, and further recommendations for the issue.
Machine: Minimag 2 (OH503)
Friday, January 16, 2015
Batch No.: SO No.:

Per Hour Per Hour Total Total


Shif Time Target Output Rem
Target Output Per Shif Per Shif

6:00 AM - 7:00 AM 1.9 0.30 Only ACu1 & FTu3&4 Run


7:00 AM - 8:00 AM 1.9 0.30 Only ACu1 & FTu3&4 Run
8:00 AM - 9:00 AM 1.9 0.30 ACu 5 R
9:00 AM - 10:00 AM 1.9 0.30
A 15.2 2.3
10:00 AM - 11:00 AM 1.9 0.10 Ftu used
11:00 AM - 12:00 PM 1.9 0.00 Ftu used
12:00 PM - 1:00 PM 1.9 0.50
1:00 PM - 2:00 PM 1.9 0.50

Batch No.: SO No.:


Total Total
Per Hour Per Hour Target
Shif Time Output Rem
Target Output Per Shif Per Shif

2:00 PM - 3:00 PM 1.9 0.60


3:00 PM - 4:00 PM 1.9 0.50
4:00 PM - 5:00 PM 1.9 0.60
5:00 PM - 6:00 PM 1.9 0.50
B 15.2 4.0
6:00 PM - 7:00 PM 1.9 0.30
7:00 PM - 8:00 PM 1.9 0.50
8:00 PM - 9:00 PM 1.9 0.50
9:00 PM - 10:00 PM 1.9 0.50

Batch No.: SO No.:


Total Total
Per Hour Per Hour Target
Shif Time Output Rem
Target Output Per Shif Per Shif

10:00 PM - 11:00 PM 1.9


11:00 PM - 12:00 AM 1.9
12:00 AM - 1:00 AM 1.9
1:00 AM - 2:00 AM 1.9
C 15.2 0.0
2:00 AM - 3:00 AM 1.9
3:00 AM - 4:00 AM 1.9
4:00 AM - 5:00 AM 1.9
5:00 AM - 6:00 AM 1.9

Total Target Per Day Total Output Per Day

45.6 6.3
45.6 6.3

Issues/Errors Actions Done Duration (min)


03)

Output (Kpcs)
Remarks
Minimag 2 Performance -
2.00
ACu1 & FTu3&4 Running (Endorse by C-Shif)
1.50
ACu1 & FTu3&4 Running (Endorse by C-Shif)
1.00
ACu 5 Running
0.50
0.00
Ftu used by sir gort

12:00 PM
10:00 AM

11:00 AM
7:00 AM

8:00 AM

9:00 AM

1:00 PM
Ftu used by sir gort

Date

Output (Kpcs)
Remarks
Minimag 2 Performance -
2.00
1.50
1.00
0.50
0.00 3:00 PM

4:00 PM

5:00 PM

6:00 PM

7:00 PM

8:00 PM

9:00 PM
Date
Output (Kpcs)

Remarks
Minimag 2 Performance -
2
1.5
1
0.5
0
11:00 PM

12:00 AM

2:00 AM

5:00 AM
1:00 AM

3:00 AM

4:00 AM

Date

utput Per Day

6.3
6.3

Status (Ok/Not OK) Remarks


Issue/Errors: Major to Minor downtime list en
Actions Action implemented and how lon
Duration May not be the time per activity
Status Was the problem did not re-occu
formance - A-Shif

Per Hour
Output
Per Hour Target
12:00 PM
11:00 AM

1:00 PM

2:00 PM

formance - B-Shif

Per Hour
Output
Per Hour Target
10:00 PM
7:00 PM

8:00 PM

9:00 PM

formance - C-Shif

Per Hour
Output
Per Hour Target
5:00 AM
3:00 AM

4:00 AM

6:00 AM
owntime list encountered for the particular shif
ed and how long it takes to solve the problem
me per activity but the total time until the error is fixed
did not re-occur again, and further recommendations for the issue.

You might also like