Temp Proc - Operations Reporting

L:CELESTICADocumentsProcedures TemporaryTemp Proc - Operations Reporting.doc Page 1 of 7 23/06/2015
Process Map
(Also see: Apple Quality Report Guide Rev_D.doc)
1. Collect Data:
a) Physical Backlog count
This is a count of the number of units that are in working progress plus those that
are on hold for parts. This includes unit on Engineering hold, are in the process of
being tested or are in the End of Line inspection rack. This may also include units at
Apple Goods Outwards that have been packed but have not been shipped (No
Airway Bill). Typically this would be done between 7am and 8am on a working
morning before units are being repaired & move round the department.
b) Backlog report
This is a vital part of the tracking and checking of the units in the department, and
will be used as part of the OPC reporting process to the customer (Aging backlog
report).
c) Importing the Backlog data
The process of importing the backlog data is as follows:
From the Workflow Odments database screen, select ‘Customer’ from the side
menu.
Issued: 01/06/05 Rev: a Author: P. Rouse Signed off:
Title: Operations Reporting
(Also see Temp Proc - OPC Reporting.doc)1/7
Enter DataCollect Data Process Data
* Physical Backlog
count
* Import Backlog
data
* Import the On
Hold data
* Report formatting
* Data checking
* Aging Shipped
* Aging backlog
Enter the data
into the OPC
On-line report.
Check the data
for Delta’s
Go to the Apple
records at customer
No. 1000005065.
Select all of the
records up to the
previous working day
(Do not include new
records for the present
day).
From the menu,
select: File; Export

In the Export dialogue box, browse for:
G:Apple QualityReportsBacklogDaily Text Dumps
Set the name to: BLddmmyy.txt (where dd=day eg. 06; mm=month yy=year)
(Selecting an existing file name but changing the day can save time)
Change: ‘Save file type’ to ‘Comma separated value’.
2. Process the data:
a) Importing the Backlog data into Excel
Open Excel. Select File; Open; Browse:
G:Apple QualityReportsBacklog Backlog Template.xls
A dialogue box will ask
you if you want to enable
Macros. Select Enable
Macros.
The template needs to be
saved as a new file.
Select:
File; Save As.
At: ‘File Name’ type:
Backlog ddmmyy.txt
(where dd=day;
mm=month yy=year)
(Selecting an existing file
name but changing the
day can save time)
Change the TAB at the
bottom to the same date
as the file date.
Importing the data
Select: File; Open;
Browse to the ‘Text
Dumps’ folder &
select the ‘files of
type’ filter at the
bottom of the
dialogue box.
Select: ‘Text files’
from the pull-down
menu. Select the
Backlog file created
earlier & select: File;
Open.

The Text import wizard box will come up in Step 1. Select the ‘Choose File Type’ as
‘Delimited’ followed by Next>.
At the next dialogue box select the ‘Delimiter’ as ‘comma’, followed by ‘Finish>’.
The imported file now needs to be cleaned up. There is a tool to do this for you.
When the file has been cleaned up, it needs to be pasted into the new Backlog file.
b) Importing the On-Hold data into Excel
On Hold Data is also in Workflow, and the process for importing and storing this data is the
same as for Backlog.
This can be imported into Excel if there is a need to paste the Part number / Description
into a backlog report.
c) Checking Hold Data
This has been done by the Point of Use team or the Line Supervisor.
From the Tools menu, select
Macro. Select the macro BLClean
(at the bottom of the list).
Select the data from line
2 to the last record –
dragging the selection
from the bottom right of
the data is a way of
doing this.
Either use Edit; Copy or
CNTL-C to copy the
data, then move to the
Backlog file (position the
cursor in the top left
corner below the
headings, and either
select Edit; Paste or
CNTL-V.

d) Checking the Backlog.
Errors occur in the backlog report in workflow. This occurs for the following reasons:
Records missing from Workflow backlog
• Units have their record closed at End of line, but do not ship.
• A group of units are closed on workflow, but miss their shipping time, so are still on-
site.
Records added to Workflow Backlog
• A unit is shipped (it’s record in is the Dispatch spreadsheet), but it was not closed in
workflow.
• A record is stuck in Workflow (usually at Repair) and cannot be closed.
Ways of checking the Backlog are as follows:
Compare the backlog with either the Dispatch Spreadsheet or the Travellers (use CNTL-F
and type in last 4 digits of dispatch numbers). If a record is missing, it will probably have to
be manually typed into the Backlog report. If a record has not been closed-off, the record
will have to be closed in Workflow by the Line Supervisor or Administrator, using the same
process as an End off Line Inspector.
Use the In Vs Out Spreadsheet as both a data compiler, and also a checking mechanism.
This is a simple sum:
Yesterdays (B/L + Infeed = WIP) – Shipped = Today’s Backlog
If the number you typed into the End of the day Backlog does not match the formula the
cell turns red as above (conditional formatting).
e) Backlog data for OPC Report – Aging Backlog
In the backlog report, there are three columns to aid the compilation of Aging Backlog. Day
is the number of days the unit has been on site (Same day is day ‘0’, which is vital for the
OPC report to calculate ‘number of units received [Same Day Shipped + Same Day
Backlog]).

f) Aging Shipped compilation
There is no template for this as the data is only used to compile the OPC report.
Usually this information is compiled daily in the Notebook of the Line Supervision, and is
therefore as useful tool for checking daily TAT (Turn-around Time).
Here is an example of a practical notebook layout:
Infeed: 35 Shipped: 43 B/L: 103 Hold: 50
Age Date Distribution
SD 26th
10W
ND 25th
17W
2d 24th
9 (2N 7W)
3d 23rd
2A
4d 22nd
1W
5d 19th
0
6d 18th
2A
(Remember that days are Working days, not Weekends or Bank Holidays. You may find it
useful to use the Apple Fiscal Year Calendar to do this).
At this point you have complied and checked:
1. Aging Backlog Report
2. Part Hold Data
3. Aging Shipped data
3. OPC Report - Enter Data
Also see: Apple Quality Report Guide Rev_D.doc
The Apple OPC report is an
On-line Database accessible
over the internet.
http://depotmetrics.apple.com/
This cannot be access over ordinary
department PC’s because the
host file needs to be configured for
Firewall permissions.
You will need to enter the Apple
Week No. and Period based on
The Apple Fiscal Calendar.
Select :
OPC Report Daily Data Entry
Where:
W = WIP
A = AWP part hold
N = NTF hold
E = Engineering hold
P = Paperwork

The OPC Data Entry Screen is as follows:
The Database is filled in 3 stages, followed by a check.
Stage 1: Aging Shipped (you have compiled this information)
Stage 2: Aging Backlog (Backlog Report)
Stage 3: Part Holds (Part Hold Report (These may need to be pasted into a blank
spreadsheet and organised into part numbers for ease of counting)
There are other boxes below for Oldest Part hold & Oldest Admin hold (Eng / Paperwork /
NTF etc.).
Other things to note:
• There is a Dashboard screen for each day of the week, which is accessed from
‘Select Day of the Week’ at the top left of the screen.
• To Enter day on the Data Entry screen, Select: Edit Record
• This system is prone to Time-out’s and data loss. It is therefore suggested that you
‘Submitt’ data after filling in each section, and then wait for the screen to fully
refresh before selecting ‘Edit Record’ again.
Continued >>

Checking:
Most of the checking should have taken place already in the data compilation. The main
issue is discrepancies in ‘what came in and what went out’.
OPC uses the same checking formula as the In Vs Out Spreadsheet:
Yesterdays (B/L + Infeed = WIP) – Shipped = Today’s Backlog
Correction of Delta’s always takes place in the ‘Same Day’ column of both Shipped and
Backlog (remembering these are added together to make the total number of units
received).

Temp Proc - Operations Reporting

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (20)

Similar to Temp Proc - Operations Reporting

Similar to Temp Proc - Operations Reporting (20)

More from Paul Rouse

More from Paul Rouse (14)

Temp Proc - Operations Reporting