The WI Report 3 shows the summary of activities performed by an operator within an operation and then breaks down each activity into the worksteps and part consumption. The report is broken out into two sections. No options or controls exist to allow for the sections to be run individually. Each section is formatted to run on an 8.5in x 11in paper with 0.5 inch margins.
Activity List:
Activity List
Activity Breakdown:
Activity Breakdown
Section 1: Activity List
1.The activity list is a summary of all sequenced activities at a station-operator and associated times.
2.Layout
a.The Seq, Description, and Time columns are 6.25 inches wide
b.The Line, Station, etc. columns are 5.5 inches wide with the right vertical border separating the Description and Time columns
c.The Standard Work Layout Image dimensions are 4 x 4 inches
d.The Standard Work Lauout Image, PPE, Line, Station, etc. header fields should appear on each page if the Activity List requires multiple pages
e.There is a limit of 20 activities on a single page. If more than 20, then it will require multiple pages
f.Font size within the Activity List is 14 and the font is Calibri
g.Font size within the Line, Station, etc. header is 11 and the font is Calibri
3.Fields
a.Line - Description of the parent routing.
b.Station - Operation Description in the Operation List.
c.Operator - Operator ID field (Activity List)
d.Models
i.If no model filter is used, then the list will display the model information for the first model found which is mapped to the process
ii.Models will be a comma separated list where the values will be Model-ID and Model-Alias concatenated with a '-'.
iii.If no Model-Alias, then the '-' will be dropped.
e.Generated -
i.Date representing the effective date used to filter the report.
ii.If no effective date was used, then the current date should be used.
iii.If within a line balance scenario, then the Scenario-Target Date should be used.
iv.The format will be MM/DD/YYYY
f.Generated By - Full name of the Assembly Planner user who is generating the report
g.Seq -
i.Seq field is populated with the Activity-ActSeqNo
ii.ActSeqNo should be trimmed to an integer if the decimal YY is equal to zero (ActSeqNo.YY)
iii.ActSeqNo should retain the decimal if the decimal YY is not equal to zero (ActSeqNo.YY)
h.Description - Activity-Description with 'auto-size' of font to prevent overflow.
i.Time -
i.Time units should be the global Time Unit if run from the process library (Routing, Operation, Activity)
ii.Time units should be the scenario Time Unit if run from Line Balancing
iii.The time should be trimmed to an integer if the decimal value is equal to zero
iv.The time should retain the decimal value if the decimal value is not equal to zero
v.All time fields include the frequency of the Activity when calculating.
j.Critical Characteristic -
i.If the Activity-Critical Characteristic if true, then the background color for the row will be colored yellow and the text will be bolded
ii.If any activity in the station-operator combination has a Critical Characteristic, then the alert legend will be shown underneath the activity list
iii. 
k.Total Process Time - Represents the sum of the activity times with units always converted to seconds and minutes and shown in bold
l.Takt Time -
i.Uses the Routing-Takt Time field if run from the process library (Routing, Operation, Activity)
ii.Units always converted to seconds and minutes
m.PPE Icons - PPE1-PPE6 (Operation List custom fields)
n.Standard Work Layout - Operation-LayoutImage
Section 2: Activity Breakdown (Worksteps)
1.The Activity Breakdown shows detailed information for each activity, including Worksteps and Part Consumption
2.Layout
a.The Legend (Symbol Key) section is approximately 8 inches wide
b.The Step column is 0.5 inches wide
c.The How column is 2.5 inches wide
d.The PN column is 1 inch wide
e.The Qty column is 0.5 inches wide
f.The PN Description column is 1.5 inches wide
g.The Illustration column is 4 inches wide
i.Depending on the native image resolution, the image will be proportionally stretched in the horizontal direction to fill all 4 inches
h.The Logo, Station, Generated, and Legend will appear on each page
i.LeftLogo.jpg should be displayed in the upper left hand corner.
j.If the workstep has an image, the height of the workstep will be approximately 3 inches. Only 2 worksteps with images will be shown on a page.
k.If the workstep does not have an image, the height of the workstep will be approximately 1.5 inches. Up to 4 worksteps without images will be shown on a page.
l.There is a page break between the final workstep of an activity and a new activity
m.Font size in the Activity header is 14.
n.Font size in the Workstep table is 12.
3.Fields
a.Station - Operation-Description (Operation List)
b.Generated -
i.Date representing the effective date used to filter the report.
ii.If no effective date was used then the current date should be used.
iii.If within a line balance scenario, the Scenario-TargetDate should be used.
iv.Follow the format MM/DD/YYYY .
c.Activity Header -
i.ActSeqNo -
1.Field should be populated with the Activity-ActSeqNo and bold font.
2.ActSeqNo should be trimmed to an integer if the decimal YY is equal to zero (ActSeqNo.YY)
3.ActSeqNo should retain the decimal if the decimal YY is not equal to zero (ActSeqNo.YY)
ii.Description -
1.Description field should be the Activity-Description and bold font.
2.OperatorID should be listed in the Activity Header on the right hand side
iii.Step - Step field should be populated with the Workstep-WorkstepNo
iv.How -
1.How field should be populated with the Workstep-Description
2.The description should word wrap and 'auto-size' the font to prevent overflow.
3.If the Workstep-Icon is equal to ‘CriticalCharacteristic’, then the Why field should be filled with a yellow background and all text should be in bold.
v.Why -
1.Why field should be populated with the Workstep-Reason custom field
2.The reason should word wrap and 'auto-size' the font to prevent overflow.
vi.Consumption records -
1.The ItemID, Quantity, and Item Description should be listed
2.Items not tied to a WorkStep should be added to the 'Unassigned Parts' list at the end of the activity
3.The Unassigned List should only be displayed if there are unassigned parts for that activity.
4.Items should appear in the WorkStep which they are linked via the WorkStepNo field
5.Within a WorkStepNo, the items should be listed per the Order field
vii.Icons -
1.Worksteps will have a custom field called Icon.
2.This Icon list will be tied to a list. This list will be tied to images in the global application documents folder.
3.If an icon is selected, then the image should appear in the 'Step' column and in the upper left hand corner of the illustration.
viii.Illustration - The Illustration should be populated with the Workstep-SOPImage field