@seedtactics/insight-client 16.7.2 → 16.8.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -29
- package/dist/assets/index-BGjv3-QV.js +388 -0
- package/dist/cell-status/current-status.js +4 -1
- package/dist/cell-status/estimated-cycle-times.js +2 -1
- package/dist/cell-status/inspections.js +1 -1
- package/dist/cell-status/loading.js +1 -1
- package/dist/cell-status/material-summary.js +4 -2
- package/dist/cell-status/names.js +1 -1
- package/dist/cell-status/rebookings.js +3 -1
- package/dist/cell-status/scheduled-jobs.js +1 -1
- package/dist/cell-status/sim-production.js +6 -2
- package/dist/cell-status/station-cycles.js +3 -1
- package/dist/cell-status/tool-replacements.js +21 -7
- package/dist/cell-status/tool-usage.js +7 -2
- package/dist/components/App.d.ts +2 -2
- package/dist/components/App.js +13 -5
- package/dist/components/AxisAndGrid.d.ts +6 -6
- package/dist/components/BarcodeScanning.d.ts +2 -2
- package/dist/components/BarcodeScanning.js +8 -2
- package/dist/components/ChartTooltip.d.ts +2 -2
- package/dist/components/ChooseMode.js +6 -1
- package/dist/components/ChooseOperator.d.ts +1 -1
- package/dist/components/ErrorsAndLoading.d.ts +3 -3
- package/dist/components/LoadingIcon.d.ts +1 -1
- package/dist/components/LoadingIcon.js +1 -1
- package/dist/components/LogEntry.d.ts +2 -2
- package/dist/components/LogEntry.js +10 -8
- package/dist/components/ManualSerialEntry.d.ts +2 -2
- package/dist/components/MonthSelect.d.ts +1 -1
- package/dist/components/MonthSelect.js +3 -1
- package/dist/components/Navigation.d.ts +2 -2
- package/dist/components/Navigation.js +1 -1
- package/dist/components/VerboseLogging.d.ts +1 -1
- package/dist/components/analysis/AnalysisSelectToolbar.d.ts +1 -1
- package/dist/components/analysis/BasketCycleCards.d.ts +1 -1
- package/dist/components/analysis/BasketCycleCards.js +1 -1
- package/dist/components/analysis/BufferChart.d.ts +1 -1
- package/dist/components/analysis/BufferChart.js +23 -4
- package/dist/components/analysis/CostPerPiece.d.ts +2 -2
- package/dist/components/analysis/CostPerPiece.js +2 -2
- package/dist/components/analysis/CycleChart.d.ts +1 -1
- package/dist/components/analysis/CycleChart.js +17 -4
- package/dist/components/analysis/DataTable.js +4 -2
- package/dist/components/analysis/EfficiencyPage.d.ts +2 -2
- package/dist/components/analysis/EfficiencyPage.js +1 -1
- package/dist/components/analysis/HeatChart.d.ts +1 -1
- package/dist/components/analysis/HeatChart.js +12 -3
- package/dist/components/analysis/InspectionDataTable.d.ts +1 -1
- package/dist/components/analysis/InspectionDataTable.js +6 -1
- package/dist/components/analysis/InspectionSankey.d.ts +1 -1
- package/dist/components/analysis/InspectionSankey.js +16 -6
- package/dist/components/analysis/PalletCycleCards.d.ts +1 -1
- package/dist/components/analysis/PalletCycleCards.js +5 -3
- package/dist/components/analysis/PartCycleCards.d.ts +2 -2
- package/dist/components/analysis/PartCycleCards.js +16 -6
- package/dist/components/analysis/QualityPage.d.ts +1 -1
- package/dist/components/analysis/ScheduleHistory.d.ts +1 -1
- package/dist/components/analysis/ScheduleHistory.js +1 -1
- package/dist/components/analysis/StationDataTable.d.ts +1 -1
- package/dist/components/analysis/ToolReplacements.d.ts +1 -1
- package/dist/components/analysis/ToolReplacements.js +7 -3
- package/dist/components/operations/AllMaterial.d.ts +1 -1
- package/dist/components/operations/ChartRangeEdit.d.ts +1 -1
- package/dist/components/operations/ChartRangeEdit.js +13 -4
- package/dist/components/operations/CloseoutReport.js +1 -1
- package/dist/components/operations/CompletedParts.js +2 -2
- package/dist/components/operations/CurrentWorkorders.js +2 -2
- package/dist/components/operations/Dashboard.d.ts +2 -2
- package/dist/components/operations/OEEChart.d.ts +4 -4
- package/dist/components/operations/OEEChart.js +7 -2
- package/dist/components/operations/Outliers.d.ts +1 -1
- package/dist/components/operations/Programs.js +9 -4
- package/dist/components/operations/Rebookings.d.ts +1 -1
- package/dist/components/operations/Rebookings.js +3 -1
- package/dist/components/operations/RecentCycleChart.d.ts +1 -1
- package/dist/components/operations/RecentCycleChart.js +2 -2
- package/dist/components/operations/RecentProduction.js +3 -3
- package/dist/components/operations/RecentSchedules.js +3 -1
- package/dist/components/operations/RecentStationCycles.d.ts +1 -1
- package/dist/components/operations/RecentStationCycles.js +1 -1
- package/dist/components/operations/ShiftSettings.d.ts +1 -1
- package/dist/components/operations/SimDayUsage.d.ts +1 -1
- package/dist/components/operations/ToolReport.js +17 -6
- package/dist/components/operations/WorkorderGantt.d.ts +1 -1
- package/dist/components/quality/QualityMaterial.d.ts +2 -2
- package/dist/components/quality/QualityMaterial.js +1 -1
- package/dist/components/quality/QualityPaths.d.ts +1 -1
- package/dist/components/quality/RecentFailedInspections.d.ts +1 -1
- package/dist/components/routes.d.ts +1 -1
- package/dist/components/routes.js +1 -1
- package/dist/components/station-monitor/BulkRawMaterial.d.ts +2 -2
- package/dist/components/station-monitor/BulkRawMaterial.js +11 -5
- package/dist/components/station-monitor/Closeout.js +6 -2
- package/dist/components/station-monitor/Inspection.js +3 -1
- package/dist/components/station-monitor/InvalidateCycle.d.ts +3 -3
- package/dist/components/station-monitor/InvalidateCycle.js +10 -3
- package/dist/components/station-monitor/JobDetails.js +4 -2
- package/dist/components/station-monitor/LoadStation.d.ts +1 -1
- package/dist/components/station-monitor/LoadStation.js +6 -3
- package/dist/components/station-monitor/Material.d.ts +10 -10
- package/dist/components/station-monitor/Material.js +28 -20
- package/dist/components/station-monitor/Material.test.js +1 -1
- package/dist/components/station-monitor/MoveMaterialArrows.d.ts +2 -2
- package/dist/components/station-monitor/PrintedLabel.d.ts +3 -3
- package/dist/components/station-monitor/PrintedLabel.js +9 -4
- package/dist/components/station-monitor/QuarantineButton.d.ts +1 -1
- package/dist/components/station-monitor/QuarantineButton.js +4 -2
- package/dist/components/station-monitor/Queues.d.ts +2 -2
- package/dist/components/station-monitor/Queues.js +6 -4
- package/dist/components/station-monitor/QueuesAddMaterial.d.ts +3 -3
- package/dist/components/station-monitor/QueuesAddMaterial.js +20 -7
- package/dist/components/station-monitor/SelectInspType.d.ts +2 -2
- package/dist/components/station-monitor/SelectWorkorder.d.ts +1 -1
- package/dist/components/station-monitor/StationToolbar.d.ts +1 -1
- package/dist/components/station-monitor/StationToolbar.js +13 -3
- package/dist/components/station-monitor/SystemOverview.d.ts +4 -4
- package/dist/components/station-monitor/SystemOverview.js +36 -16
- package/dist/components/station-monitor/Whiteboard.d.ts +1 -1
- package/dist/data/all-material-bins.js +2 -1
- package/dist/data/cost-per-piece.js +3 -1
- package/dist/data/move-arrows.js +3 -1
- package/dist/data/part-summary.js +1 -1
- package/dist/data/results.cycles.js +13 -4
- package/dist/data/tools-programs.js +3 -2
- package/dist/index.html +1 -1
- package/dist/network/api.d.ts +18 -0
- package/dist/network/api.js +502 -371
- package/dist/util/chart-colors.js +12 -1
- package/docs/client-efficiency.md +226 -263
- package/docs/client-engineering.md +27 -28
- package/docs/client-launch.md +32 -33
- package/docs/client-operations.md +50 -53
- package/docs/client-quality.md +39 -43
- package/docs/client-sales.md +36 -40
- package/docs/client-scanners.md +27 -27
- package/docs/client-station-monitor.md +86 -96
- package/docs/client-tools-programs.md +47 -44
- package/docs/improve-fms.md +73 -78
- package/docs/makino.md +21 -25
- package/docs/material-quarantine.md +50 -64
- package/docs/material-tracking.md +162 -195
- package/docs/mazak.md +78 -91
- package/docs/niigata.md +145 -168
- package/docs/operator-procedures.md +72 -76
- package/docs/part-instructions.md +36 -36
- package/docs/security.md +87 -81
- package/docs/server-config.md +36 -45
- package/docs/server-errors.md +21 -22
- package/package.json +25 -24
- package/dist/assets/index-BwbaiELK.js +0 -364
|
@@ -2,148 +2,138 @@
|
|
|
2
2
|
title: FMS Station Monitor
|
|
3
3
|
nav: FMS Insight Client > Stations
|
|
4
4
|
description: >-
|
|
5
|
-
The FMS Insight station monitor pages are used on the factory floor by the operators;
|
|
6
|
-
|
|
7
|
-
FMS.
|
|
5
|
+
The FMS Insight station monitor pages are used on the factory floor by the operators; these pages
|
|
6
|
+
assist with loading/unloading, washing, and inspecting material in the FMS.
|
|
8
7
|
---
|
|
9
8
|
|
|
10
9
|
# FMS Insight Station Monitor Pages
|
|
11
10
|
|
|
12
|
-
The station monitor pages are intended to be used on the shop floor by the operators;
|
|
13
|
-
|
|
14
|
-
sticky
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
in the factory, perhaps with an attached barcode scanner.
|
|
26
|
-
The computer or mounted tablet can then be configured to open the specific screen
|
|
27
|
-
for the station by either bookmarking the page or just setting the specific page
|
|
28
|
-
as the homepage for the browser.
|
|
11
|
+
The station monitor pages are intended to be used on the shop floor by the operators; these pages
|
|
12
|
+
display the [virtual whiteboard of material sticky notes](material-tracking). Each in-process piece
|
|
13
|
+
of material is represented by a virtual sticky note. On the sticky note, FMS Insight displays the
|
|
14
|
+
part name, serial, assigned workorder, and any signaled inspections. The sticky note can be clicked
|
|
15
|
+
or tapped to open a dialog with more details about the material including the log of events. The
|
|
16
|
+
dialog also allows the operator to notify Insight of changes in the material, such as completing
|
|
17
|
+
wash or assigning a workorder. Finally, the sticky note contains an identicon based on the part name
|
|
18
|
+
and the final number/letter of the serial.
|
|
19
|
+
|
|
20
|
+
We suggest that computers or mounted tablets be placed next to various stations in the factory,
|
|
21
|
+
perhaps with an attached barcode scanner. The computer or mounted tablet can then be configured to
|
|
22
|
+
open the specific screen for the station by either bookmarking the page or just setting the specific
|
|
23
|
+
page as the homepage for the browser.
|
|
29
24
|
|
|
30
25
|
## System Overview
|
|
31
26
|
|
|
32
27
|

|
|
33
28
|
|
|
34
|
-
In the top bar of every station screen, there is a collection of squares and triangles.
|
|
35
|
-
|
|
36
|
-
triangle for each load station. The colors within the squares indicate if a pallet is at the
|
|
37
|
-
or outbound position of each machine. The color within the triangle indicates if
|
|
38
|
-
The icons can be clicked to open up a dialog containing more
|
|
29
|
+
In the top bar of every station screen, there is a collection of squares and triangles. This
|
|
30
|
+
provides a quick overview of the current state of the system. There is one square for each machine
|
|
31
|
+
and one triangle for each load station. The colors within the squares indicate if a pallet is at the
|
|
32
|
+
inbound, worktable, or outbound position of each machine. The color within the triangle indicates if
|
|
33
|
+
the load station is occupied or not. The icons can be clicked to open up a dialog containing more
|
|
34
|
+
details about the system overview.
|
|
39
35
|
|
|
40
36
|

|
|
41
37
|
|
|
42
|
-
The overview shows each machine, load station and pallet in the system and the material currently on
|
|
43
|
-
The material can be hovered and clicked to open more details.
|
|
38
|
+
The overview shows each machine, load station and pallet in the system and the material currently on
|
|
39
|
+
the pallets. The material can be hovered and clicked to open more details.
|
|
44
40
|
|
|
45
41
|
## Load Station
|
|
46
42
|
|
|
47
43
|

|
|
48
44
|
|
|
49
|
-
On the top toolbar, the specific load station number is set. Insight will display
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
the queue can be displayed along with the pallet regions.
|
|
45
|
+
On the top toolbar, the specific load station number is set. Insight will display only regions
|
|
46
|
+
relevant to this specific load station, including the material region, the faces of the pallet
|
|
47
|
+
currently at the load station, and a region for completed material. Optionally, the queues dropdown
|
|
48
|
+
on the top toolbar can be used to add additional whiteboard regions to display in addition to the
|
|
49
|
+
pallet regions. Typically we suggest that in-process queues have their own computer with a dedicated
|
|
50
|
+
display, but for queues closely associated with the load station such as a transfer stand, the
|
|
51
|
+
virtual whiteboard region for the queue can be displayed along with the pallet regions.
|
|
57
52
|
|
|
58
53
|

|
|
59
54
|
|
|
60
|
-
When a material sticky note is clicked or tapped, a dialog will open with a
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
can be taken for the specific material.
|
|
55
|
+
When a material sticky note is clicked or tapped, a dialog will open with a log of events for the
|
|
56
|
+
piece of material. The dialog can also be opened by [using a scanner](client-scanners) or manually
|
|
57
|
+
entering a serial via the magnifying glass button on the toolbar. In the dialog, a variety of
|
|
58
|
+
actions can be taken for the specific material.
|
|
65
59
|
|
|
66
60
|
Finally, the lower-right hand corner of the screen contains a brown circular button which when
|
|
67
61
|
clicked will open all load instructions for all material currently being loaded or unloaded.
|
|
68
|
-
Alternatively, in the material dialog, the Instructions button can be clicked to open the
|
|
69
|
-
for only a single piece of material.
|
|
62
|
+
Alternatively, in the material dialog, the Instructions button can be clicked to open the
|
|
63
|
+
instructions for only a single piece of material.
|
|
70
64
|
|
|
71
65
|
## Queues
|
|
72
66
|
|
|
73
67
|

|
|
74
68
|
|
|
75
|
-
The queues screen shows the material currently inside one or more queues. On the top toolbar,
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
in the top-right corner.
|
|
69
|
+
The queues screen shows the material currently inside one or more queues. On the top toolbar, one or
|
|
70
|
+
more queues can be selected and the virtual whiteboard regions for the selected queues are then
|
|
71
|
+
displayed. The material in the queue can be re-ordered by clicking and dragging on the 6-dot icon on
|
|
72
|
+
the left of each piece of material. Depending on the configuration and which specific queue is
|
|
73
|
+
selected, material can be added to a queue by clicking the plus icon in the top-right corner.
|
|
81
74
|
|
|
82
|
-
On raw material queues, the list of in-process jobs and/or unfilled workorders will be displayed
|
|
83
|
-
|
|
75
|
+
On raw material queues, the list of in-process jobs and/or unfilled workorders will be displayed in
|
|
76
|
+
a table. This table can be used by the operators to decide which material to run next.
|
|
84
77
|
|
|
85
78
|

|
|
86
79
|
|
|
87
|
-
By clicking or tapping on a material sticky note, a dialog will open with
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
also be used to open the material dialog.
|
|
80
|
+
By clicking or tapping on a material sticky note, a dialog will open with details about the specific
|
|
81
|
+
piece of material. The dialog will have a variety of actions for the specific material. An attached
|
|
82
|
+
[barcode scanner](client-scanners) can also be used to open the material dialog.
|
|
91
83
|
|
|
92
84
|
## Inspection
|
|
93
85
|
|
|
94
86
|

|
|
95
87
|
|
|
96
88
|
The inspection screen shows completed material that has been marked for inspection. On the top
|
|
97
|
-
toolbar, a specific inspection type can be selected or all material for inspection can be shown.
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
When a material sticky note is clicked or tapped, a dialog will open with a
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
any part by scanned serial (even if the part is not on the screen).
|
|
89
|
+
toolbar, a specific inspection type can be selected or all material for inspection can be shown. On
|
|
90
|
+
the left is the virtual whiteboard region for completed but not yet inspected material and on the
|
|
91
|
+
right is material which has completed inspections.
|
|
92
|
+
|
|
93
|
+
When a material sticky note is clicked or tapped, a dialog will open with a log of events for the
|
|
94
|
+
piece of material. If a specific inspection type is selected, there will be buttons to mark a piece
|
|
95
|
+
of material as either successfully inspected or failed. When clicked or tapped, this will record an
|
|
96
|
+
event in the log and move the virtual sticky note from the left to the right. The top toolbar on the
|
|
97
|
+
right allows an operator name to be entered and this operator name will be attached to the created
|
|
98
|
+
inspection completed log entry. Finally, the operator can open
|
|
99
|
+
[inspection instructions](part-instructions).
|
|
100
|
+
|
|
101
|
+
An attached [barcode scanner](client-scanners) can also be used to open the material dialog. This
|
|
102
|
+
allows viewing details and marking as inspected or uninspected any part by scanned serial (even if
|
|
103
|
+
the part is not on the screen).
|
|
113
104
|
|
|
114
105
|
## Close Out
|
|
115
106
|
|
|
116
107
|

|
|
117
108
|
|
|
118
|
-
The close out screen shows completed material from the last 36 hours. On the left
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
dialog. This allows viewing details and marking as closed out
|
|
135
|
-
any part by scanned serial (even if the part is not on the screen because more than 36 hours has passed).
|
|
109
|
+
The close out screen shows completed material from the last 36 hours. On the left is the virtual
|
|
110
|
+
whiteboard region for completed but not yet closed out material and on the right is material which
|
|
111
|
+
has completed closeout. Closeout is optional but intended for any final manual process needed before
|
|
112
|
+
the part can be shipped; typically this includes a final wash or workorder assignment or other
|
|
113
|
+
tasks.
|
|
114
|
+
|
|
115
|
+
When a material sticky note is clicked or tapped, a dialog will open with a log of events for the
|
|
116
|
+
piece of material. There is a button to mark a piece of material as closed out. When clicked or
|
|
117
|
+
tapped, this will record an event in the log and move the virtual sticky note from the left to the
|
|
118
|
+
right. The top toolbar on the right allows an operator name to be entered and this operator name
|
|
119
|
+
will be attached to the created log entry. Finally, the operator can open
|
|
120
|
+
[instructions](part-instructions).
|
|
121
|
+
|
|
122
|
+
An attached [barcode scanner](client-scanners) can also be used to open the material dialog. This
|
|
123
|
+
allows viewing details and marking as closed out any part by scanned serial (even if the part is not
|
|
124
|
+
on the screen because more than 36 hours has passed).
|
|
136
125
|
|
|
137
126
|
## System Overview Page
|
|
138
127
|
|
|
139
128
|

|
|
140
129
|
|
|
141
|
-
All station screens have access to the system overview by clicking the system overview button
|
|
142
|
-
|
|
143
|
-
Alternatively, the system overview can be opened as a dedicated page itself. The intention
|
|
144
|
-
is that each tablet or computer be dedicated to a specific task or station, and thus
|
|
145
|
-
dedicated display for the system overview page. (Note, the system overview is
|
|
146
|
-
manager as part of the [Operations Screens](client-operations).)
|
|
130
|
+
All station screens have access to the system overview by clicking the system overview button (the
|
|
131
|
+
colored squares and triangles) located in the top toolbar which opens the system overview in a
|
|
132
|
+
dialog. Alternatively, the system overview can be opened as a dedicated page itself. The intention
|
|
133
|
+
of FMS Insight is that each tablet or computer be dedicated to a specific task or station, and thus
|
|
134
|
+
you may consider a dedicated display for the system overview page. (Note, the system overview is
|
|
135
|
+
also available to the operations manager as part of the [Operations Screens](client-operations).)
|
|
147
136
|
|
|
148
|
-
The system overview shows all the machines, load stations, and pallets. It also shows the material
|
|
149
|
-
The material can be clicked to bring up the details for that specific piece of
|
|
137
|
+
The system overview shows all the machines, load stations, and pallets. It also shows the material
|
|
138
|
+
on each pallet. The material can be clicked to bring up the details for that specific piece of
|
|
139
|
+
material.
|
|
@@ -2,73 +2,76 @@
|
|
|
2
2
|
title: FMS Quality Daily Monitoring
|
|
3
3
|
nav: FMS Insight Client > Tools & Programs
|
|
4
4
|
description: >-
|
|
5
|
-
The FMS Insight tools pages are used by tool room and factory floor supervisors.
|
|
6
|
-
|
|
7
|
-
|
|
5
|
+
The FMS Insight tools pages are used by tool room and factory floor supervisors. These pages
|
|
6
|
+
display information about the current tools in the machines, the tool usage of each program, and
|
|
7
|
+
an estimate of the upcoming usage for the scheduled parts.
|
|
8
8
|
---
|
|
9
9
|
|
|
10
10
|
# FMS Insight Tools & Programs Page
|
|
11
11
|
|
|
12
|
-
The tools and programs report are accessible from two different places; first, the reports are
|
|
13
|
-
on the [Operations Management Page](client-operations) so that the floor supervisor can
|
|
14
|
-
about the tools and programs along with the other metrics and data for day-to-day
|
|
15
|
-
just the tools and programs reports tables are available on a dedicated page
|
|
16
|
-
initial [launch page](client-launch). This page is intended for display in the
|
|
17
|
-
on the shop floor where tools are managed. We suggest that this page is
|
|
12
|
+
The tools and programs report are accessible from two different places; first, the reports are
|
|
13
|
+
available on the [Operations Management Page](client-operations) so that the floor supervisor can
|
|
14
|
+
view information about the tools and programs along with the other metrics and data for day-to-day
|
|
15
|
+
management. Second, just the tools and programs reports tables are available on a dedicated page
|
|
16
|
+
accessible from the initial [launch page](client-launch). This page is intended for display in the
|
|
17
|
+
tool-room or elsewhere on the shop floor where tools are managed. We suggest that this page is
|
|
18
|
+
bookmarked and directly opened.
|
|
18
19
|
|
|
19
20
|
## Tool Report
|
|
20
21
|
|
|
21
22
|

|
|
22
23
|
|
|
23
|
-
The current tool use and life from each machine is loaded by clicking the "Load Tools" button. The
|
|
24
|
-
can be refreshed by clicking the circular icon in the top bar.
|
|
24
|
+
The current tool use and life from each machine is loaded by clicking the "Load Tools" button. The
|
|
25
|
+
data can be refreshed by clicking the circular icon in the top bar.
|
|
25
26
|
|
|
26
|
-
The main table shows a summary of all tools across all machines. For each tool, the table shows
|
|
27
|
-
for:
|
|
27
|
+
The main table shows a summary of all tools across all machines. For each tool, the table shows
|
|
28
|
+
columns for:
|
|
28
29
|
|
|
29
|
-
- _Scheduled Use_: This column sums over all not-yet-machined currently scheduled parts, using the
|
|
30
|
-
tool use that is calculated for each program. (The calculated tool-use per program can
|
|
31
|
-
report.) Note that if a program is currently-executing, we don't know where
|
|
32
|
-
the _Scheduled Use_ column contains the entire calculated tool-use for the
|
|
30
|
+
- _Scheduled Use_: This column sums over all not-yet-machined currently scheduled parts, using the
|
|
31
|
+
estimated tool use that is calculated for each program. (The calculated tool-use per program can
|
|
32
|
+
be seen on the program report.) Note that if a program is currently-executing, we don't know where
|
|
33
|
+
in the program it is so the _Scheduled Use_ column contains the entire calculated tool-use for the
|
|
34
|
+
program.
|
|
33
35
|
|
|
34
36
|
- _Total Remaining Life_: This sums the remaining life of the tool over all machines.
|
|
35
37
|
|
|
36
|
-
- _Smallest Remaining Life_: These two columns show the machine and amount with the smallest
|
|
38
|
+
- _Smallest Remaining Life_: These two columns show the machine and amount with the smallest
|
|
39
|
+
remaining life.
|
|
37
40
|
|
|
38
|
-
A scheduled part might be routed to several machines so we don't know ahead of time which tool will
|
|
39
|
-
Instead, you should compare the scheduled use with the total life and the smallest
|
|
40
|
-
sense of if additional tools will be needed soon.
|
|
41
|
+
A scheduled part might be routed to several machines so we don't know ahead of time which tool will
|
|
42
|
+
be used. Instead, you should compare the scheduled use with the total life and the smallest
|
|
43
|
+
remaining life to get a sense of if additional tools will be needed soon.
|
|
41
44
|
|
|
42
|
-
For each tool, details about the individual pockets and scheduled parts are available by clicking
|
|
43
|
-
arrow at the beginning of the row. The parts table shows all scheduled parts, the program, the
|
|
44
|
-
to run, and the estimated use per program. The machines table shows the pocket
|
|
45
|
-
tool and the current use and remaining life.
|
|
45
|
+
For each tool, details about the individual pockets and scheduled parts are available by clicking
|
|
46
|
+
the arrow at the beginning of the row. The parts table shows all scheduled parts, the program, the
|
|
47
|
+
remaining quantity to run, and the estimated use per program. The machines table shows the pocket
|
|
48
|
+
number or numbers containing the tool and the current use and remaining life.
|
|
46
49
|
|
|
47
50
|
## Program Report
|
|
48
51
|
|
|
49
52
|

|
|
50
53
|
|
|
51
|
-
The current programs in the cell controller are loaded by clicking the "Load Programs" button. The
|
|
52
|
-
can be refreshed by clicking the circular icon in the top bar.
|
|
54
|
+
The current programs in the cell controller are loaded by clicking the "Load Programs" button. The
|
|
55
|
+
data can be refreshed by clicking the circular icon in the top bar.
|
|
53
56
|
|
|
54
57
|
The main table shows the following columns:
|
|
55
58
|
|
|
56
59
|
- _Program Name_
|
|
57
|
-
- _Cell Controller Program Name_: this column will only appear if the cell controller uses a name or
|
|
58
|
-
different from the program name.
|
|
60
|
+
- _Cell Controller Program Name_: this column will only appear if the cell controller uses a name or
|
|
61
|
+
number different from the program name.
|
|
59
62
|
- _Part_: the part and process number that uses this program.
|
|
60
|
-
- _Revision_: this shows the program revision, but will only appear if program revisions are used as
|
|
61
|
-
a downloaded job. If revisions are not used, this column will not appear.
|
|
62
|
-
- _Median Time and Deviation_: For the [flexibility analysis](client-efficiency), FMS Insight
|
|
63
|
-
|
|
64
|
-
program. Because times above the median (likely due to program interruptions) is a different
|
|
65
|
-
distribution to times below the median (likely due to normal Gaussian noise), we
|
|
66
|
-
of the two separately.
|
|
67
|
-
|
|
68
|
-
In addition, the buttons on the end of the row allow viewing the program content. If revisions are
|
|
69
|
-
history of old revisions of the program can also be seen.
|
|
70
|
-
|
|
71
|
-
The arrow at the beginning of the row shows the calculated tool data for this program. We take the
|
|
72
|
-
executions of the program which are within the standard deviation of the median, and from
|
|
73
|
-
calculate the average (mean) tool use. If a tool is changed during one of these
|
|
74
|
-
so that cycle is not included in the average.
|
|
63
|
+
- _Revision_: this shows the program revision, but will only appear if program revisions are used as
|
|
64
|
+
part of a downloaded job. If revisions are not used, this column will not appear.
|
|
65
|
+
- _Median Time and Deviation_: For the [flexibility analysis](client-efficiency), FMS Insight uses
|
|
66
|
+
the data from the last 30 days to calculate a statistical median and deviation running time for
|
|
67
|
+
each program. Because times above the median (likely due to program interruptions) is a different
|
|
68
|
+
probability distribution to times below the median (likely due to normal Gaussian noise), we
|
|
69
|
+
calculate deviations of the two separately.
|
|
70
|
+
|
|
71
|
+
In addition, the buttons on the end of the row allow viewing the program content. If revisions are
|
|
72
|
+
used, the history of old revisions of the program can also be seen.
|
|
73
|
+
|
|
74
|
+
The arrow at the beginning of the row shows the calculated tool data for this program. We take the
|
|
75
|
+
last 5 executions of the program which are within the standard deviation of the median, and from
|
|
76
|
+
those 5 executions, calculate the average (mean) tool use. If a tool is changed during one of these
|
|
77
|
+
cycles, we can't calculate the actual usage so that cycle is not included in the average.
|
package/docs/improve-fms.md
CHANGED
|
@@ -2,50 +2,48 @@
|
|
|
2
2
|
title: Use analytics to improve a FMS
|
|
3
3
|
nav: Procedures > Monthly Review
|
|
4
4
|
description: >-
|
|
5
|
-
Implement continuous improvement of a flexible machining system by reviewing
|
|
6
|
-
|
|
5
|
+
Implement continuous improvement of a flexible machining system by reviewing targeted metrics
|
|
6
|
+
which expose cell efficiency and cost per piece.
|
|
7
7
|
---
|
|
8
8
|
|
|
9
9
|
# Use analytics to improve a FMS
|
|
10
10
|
|
|
11
|
-
The performance of an automated flexible machining system (FMS) depends on
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
leads to understanding the entire system as a whole and actionable insights
|
|
20
|
-
for improvements and future investments in automation and process
|
|
21
|
-
improvement.
|
|
11
|
+
The performance of an automated flexible machining system (FMS) depends on the interaction between
|
|
12
|
+
scheduling, part programming, operations, engineering design, quality control, tooling, purchasing,
|
|
13
|
+
and more. This encourages a holistic view of the entire system instead of focusing on each component
|
|
14
|
+
(such as part programming) in isolation. Recent advances in big data technology make it easier than
|
|
15
|
+
ever to understand the entire manufacturing process, investigate trade-offs, and calculate metrics
|
|
16
|
+
on monthly cost-per-piece, resource utilization, and system bottlenecks. Data analytics leads to
|
|
17
|
+
understanding the entire system as a whole and actionable insights for improvements and future
|
|
18
|
+
investments in automation and process improvement.
|
|
22
19
|
|
|
23
20
|
## Actionable Insights
|
|
24
21
|
|
|
25
|
-
Data collection and analytics focuses on presenting
|
|
26
|
-
insights](https://www.forbes.com/sites/brentdykes/2016/04/26/actionable-insights-the-missing-link-between-data-and-business-value/).
|
|
22
|
+
Data collection and analytics focuses on presenting
|
|
23
|
+
[actionable insights](https://www.forbes.com/sites/brentdykes/2016/04/26/actionable-insights-the-missing-link-between-data-and-business-value/).
|
|
27
24
|
Raw data collection and information visualization can generate many metrics and insights into a
|
|
28
25
|
system, but the challenge is to produce clear, relevant, specific insights. For a FMS, in our
|
|
29
|
-
experience there are two metrics which lead to actionable insights: cost-per-piece and resource
|
|
26
|
+
experience there are two metrics which lead to actionable insights: cost-per-piece and resource
|
|
27
|
+
utilization.
|
|
30
28
|
|
|
31
29
|
Cost-per-piece is a great actionable insight because it is easy to understand, specific to the
|
|
32
30
|
ultimate purpose of the FMS, highly relevant to the business, and can be clearly presented to all
|
|
33
|
-
stakeholders. For ordering, an accurate analysis of cost-per-piece allows easy quoting of work.
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
31
|
+
stakeholders. For ordering, an accurate analysis of cost-per-piece allows easy quoting of work. For
|
|
32
|
+
accounting, cost-per-piece allows justifications for future capital investments in new machines or
|
|
33
|
+
new automation. For operational management, cost-per-piece helps understand the impact of a process
|
|
34
|
+
change. That is, management can see if a process change has improved cost-per-piece and therefore if
|
|
35
|
+
the process change should be kept or adjusted. The entire business benefits from visible and
|
|
36
|
+
accurate cost-per-piece metrics, because various departments and employees can see that even if a
|
|
37
|
+
change requires them to perform extra work, it improves the overall business value of the system.
|
|
38
|
+
The only data required from daily operations is the monthly quantity of parts produced, and it is
|
|
39
|
+
implemented on the [flexibility analysis page](client-efficiency).
|
|
42
40
|
|
|
43
41
|
While it is the ultimate goal, overall cost-per-piece is not a useful metric to improve the system.
|
|
44
|
-
Sure, a cost-per-piece breakdown will show the costs of labor, machining, and tooling but how do
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
42
|
+
Sure, a cost-per-piece breakdown will show the costs of labor, machining, and tooling but how do you
|
|
43
|
+
turn that into a plan to change something? Also, focusing on improving cost-per-piece directly risks
|
|
44
|
+
optimizing cost by sacrificing quality. Instead, the best metric for continuous improvement is the
|
|
45
|
+
bottlenecks and utilization of system resources, since the goal is to produce more stuff with the
|
|
46
|
+
same machines and quality.
|
|
49
47
|
|
|
50
48
|
Utilization and bottleneck metrics are more difficult to turn into actionable insights. Many
|
|
51
49
|
companies generate OEE (operational equipment effectiveness) data or collect machine utilization and
|
|
@@ -57,42 +55,42 @@ into actions.
|
|
|
57
55
|
|
|
58
56
|
To turn the system utilization and performance metrics into actionable insights, we suggest the
|
|
59
57
|
creation of a tactics council. The tactics council is made up of a representative from each
|
|
60
|
-
department and component of the system, and the council's job is to decide on the overall tactics
|
|
61
|
-
operation. By combining representatives from all areas of the system, the tactics council
|
|
62
|
-
produce actions (changes in how the system operates) based on the information and metrics on OEE
|
|
63
|
-
system performance. Helpful efficiency metrics and graphs are displayed in the
|
|
58
|
+
department and component of the system, and the council's job is to decide on the overall tactics
|
|
59
|
+
for system operation. By combining representatives from all areas of the system, the tactics council
|
|
60
|
+
can produce actions (changes in how the system operates) based on the information and metrics on OEE
|
|
61
|
+
and system performance. Helpful efficiency metrics and graphs are displayed in the
|
|
64
62
|
[flexibility analysis page](client-efficiency).
|
|
65
63
|
|
|
66
64
|
## Tactics Council
|
|
67
65
|
|
|
68
66
|
How can we produce actions from the various insights and information on OEE, machine utilization,
|
|
69
67
|
labor use, and system performance? Because improving a FMS requires coordination between various
|
|
70
|
-
stakeholders across several departments, a great management technique is a tactics council made up
|
|
71
|
-
part programming, operations, scheduling, tooling, quality control,
|
|
72
|
-
involved in the system. The council is the primary recipient of the
|
|
73
|
-
metrics, meets once every 6 weeks or once every two months, reviews the data,
|
|
68
|
+
stakeholders across several departments, a great management technique is a tactics council made up
|
|
69
|
+
of a representative from part programming, operations, scheduling, tooling, quality control,
|
|
70
|
+
accounting, and anyone else involved in the system. The council is the primary recipient of the
|
|
71
|
+
system performance metrics, meets once every 6 weeks or once every two months, reviews the data,
|
|
74
72
|
brainstorms improvements, and has final authority on the overall tactics for how the FMS operates.
|
|
75
73
|
|
|
76
74
|
Plan. Do. Check. Adjust. The [PDCA technique](https://en.wikipedia.org/wiki/PDCA) is an effective
|
|
77
|
-
strategy to improve the performance of an existing FMS and is ideal for the tactics council.
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
75
|
+
strategy to improve the performance of an existing FMS and is ideal for the tactics council. During
|
|
76
|
+
the tactics council meeting, the council will perform the plan and adjust phases of PDCA and in the
|
|
77
|
+
6-weeks to two months between meetings, individual departments will perform the do and check phases
|
|
78
|
+
of PDCA. The tactics council should focus on only a single or at most two improvements at once.
|
|
79
|
+
|
|
80
|
+
For example, say that an improvement idea is to implement [material tracking](material-tracking) by
|
|
81
|
+
adding a serial and barcode to each part during machining and then scanning the barcode at the
|
|
82
|
+
inspection station, allowing the inspection operator to view the pallet, machine, and time for this
|
|
83
|
+
specific part. The first step is to develop the plan, which would include the cost of purchasing a
|
|
84
|
+
barcode printer, an analysis of the extra time at the load station applying the barcode to the part,
|
|
85
|
+
a target for reducing the percentage of parts that require inspection, the cost savings from the
|
|
86
|
+
reduced inspections, and other facets such as training. This plan is presented to the tactics
|
|
87
|
+
council, the council discusses it, and say the tactics council agrees to implement this change. In
|
|
88
|
+
the 6-weeks to two months between council meetings, operations will purchase the barcode printer,
|
|
89
|
+
start barcoding parts, and start collecting data (the do and check steps of PDCA). The inspection
|
|
90
|
+
stand will start using the barcodes and importantly record data on quality improvements. The next
|
|
91
|
+
tactics council meeting can then review the data to understand the impact on overall cost-per-piece
|
|
92
|
+
and system performance. By reviewing these metrics, the council can decide on any adjustments if
|
|
93
|
+
necessary.
|
|
96
94
|
|
|
97
95
|
The tactics council is an important management technique because it encourages buy-in from everyone
|
|
98
96
|
to improve overall cost-per-piece and system performance instead of focusing on individual isolated
|
|
@@ -106,21 +104,18 @@ total system performance, one department refusing to implement a change is great
|
|
|
106
104
|
|
|
107
105
|
## Continuous Improvement
|
|
108
106
|
|
|
109
|
-
The utilization and bottleneck metrics which lead to actionable insights vary
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
jams, a problem in the part-program of a part run on pallet 5, lack of tool
|
|
122
|
-
capacity, or something else. In this case, more detailed data collection can
|
|
123
|
-
focus on pallet 5 to help identify the problem.
|
|
107
|
+
The utilization and bottleneck metrics which lead to actionable insights vary by system and part
|
|
108
|
+
mix. The overall system OEE is easy to calculate by taking the total quantity of parts produced in a
|
|
109
|
+
month, adding up their planned time, and dividing by the hours in a month. But the OEE is not an
|
|
110
|
+
actionable insight: is the OEE lowered by a pallet traffic jam, a problem in a part-program, tooling
|
|
111
|
+
capacity limitations, cart contention, load station inattention, or something else? This is where
|
|
112
|
+
the repetitive nature of the PDCA technique shines. Every two months, the tactics council meets,
|
|
113
|
+
reviews the available data, and can suggest new metrics based on what was learned from the previous
|
|
114
|
+
reports. For example, perhaps the overview of the system identifies that pallet 5 has very irregular
|
|
115
|
+
and erratic flow times. This could be caused by competition between pallets, lack of flexibility,
|
|
116
|
+
traffic jams, a problem in the part-program of a part run on pallet 5, lack of tool capacity, or
|
|
117
|
+
something else. In this case, more detailed data collection can focus on pallet 5 to help identify
|
|
118
|
+
the problem.
|
|
124
119
|
|
|
125
120
|
## Cost report
|
|
126
121
|
|
|
@@ -133,9 +128,9 @@ according to weights based on their planned use of system resources. The cost-pe
|
|
|
133
128
|
exported to the ERP and combined with order data from the ERP to calculate a cost-per-order.
|
|
134
129
|
|
|
135
130
|
The cost-per-piece is the primary metric and insight produced by the tactics council. It should be
|
|
136
|
-
broadcast to the entire business as an actionable insight for quoting work, future capital
|
|
137
|
-
and general accounting. Cost-per-piece should be produced by the tactics council itself
|
|
138
|
-
management because the council is in the best position to decide on cost trade-offs.
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
131
|
+
broadcast to the entire business as an actionable insight for quoting work, future capital
|
|
132
|
+
investment, and general accounting. Cost-per-piece should be produced by the tactics council itself
|
|
133
|
+
and not management because the council is in the best position to decide on cost trade-offs. For
|
|
134
|
+
example, there is a trade-off between quality and inspections and cost, and the council is in the
|
|
135
|
+
best position to decide on the required quality and inspections and then work to reduce costs only
|
|
136
|
+
under these constraints without sacrificing quality.
|