@seedtactics/insight-client 16.4.0
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 +37 -0
- package/dist/cell-status/buffers.d.ts +36 -0
- package/dist/cell-status/buffers.js +127 -0
- package/dist/cell-status/current-status.d.ts +30 -0
- package/dist/cell-status/current-status.js +200 -0
- package/dist/cell-status/estimated-cycle-times.d.ts +41 -0
- package/dist/cell-status/estimated-cycle-times.js +257 -0
- package/dist/cell-status/inspections.d.ts +55 -0
- package/dist/cell-status/inspections.js +213 -0
- package/dist/cell-status/loading.d.ts +26 -0
- package/dist/cell-status/loading.js +112 -0
- package/dist/cell-status/material-details.d.ts +116 -0
- package/dist/cell-status/material-details.js +422 -0
- package/dist/cell-status/material-summary.d.ts +52 -0
- package/dist/cell-status/material-summary.js +312 -0
- package/dist/cell-status/names.d.ts +19 -0
- package/dist/cell-status/names.js +134 -0
- package/dist/cell-status/pallet-cycles.d.ts +24 -0
- package/dist/cell-status/pallet-cycles.js +78 -0
- package/dist/cell-status/rebookings.d.ts +30 -0
- package/dist/cell-status/rebookings.js +139 -0
- package/dist/cell-status/scheduled-jobs.d.ts +18 -0
- package/dist/cell-status/scheduled-jobs.js +94 -0
- package/dist/cell-status/sim-day-usage.d.ts +14 -0
- package/dist/cell-status/sim-day-usage.js +54 -0
- package/dist/cell-status/sim-production.d.ts +22 -0
- package/dist/cell-status/sim-production.js +91 -0
- package/dist/cell-status/sim-station-use.d.ts +25 -0
- package/dist/cell-status/sim-station-use.js +71 -0
- package/dist/cell-status/station-cycles.d.ts +34 -0
- package/dist/cell-status/station-cycles.js +145 -0
- package/dist/cell-status/tool-replacements.d.ts +44 -0
- package/dist/cell-status/tool-replacements.js +155 -0
- package/dist/cell-status/tool-usage.d.ts +25 -0
- package/dist/cell-status/tool-usage.js +95 -0
- package/dist/components/App.d.ts +15 -0
- package/dist/components/App.js +549 -0
- package/dist/components/AxisAndGrid.d.ts +51 -0
- package/dist/components/AxisAndGrid.js +47 -0
- package/dist/components/BarcodeScanning.d.ts +6 -0
- package/dist/components/BarcodeScanning.js +150 -0
- package/dist/components/ChartTooltip.d.ts +28 -0
- package/dist/components/ChartTooltip.js +95 -0
- package/dist/components/ChooseMode.d.ts +18 -0
- package/dist/components/ChooseMode.js +136 -0
- package/dist/components/ChooseOperator.d.ts +1 -0
- package/dist/components/ChooseOperator.js +93 -0
- package/dist/components/ErrorsAndLoading.d.ts +9 -0
- package/dist/components/ErrorsAndLoading.js +55 -0
- package/dist/components/LoadingIcon.d.ts +1 -0
- package/dist/components/LoadingIcon.js +48 -0
- package/dist/components/LogEntry.d.ts +16 -0
- package/dist/components/LogEntry.js +365 -0
- package/dist/components/ManualSerialEntry.d.ts +5 -0
- package/dist/components/ManualSerialEntry.js +91 -0
- package/dist/components/MonthSelect.d.ts +6 -0
- package/dist/components/MonthSelect.js +67 -0
- package/dist/components/Navigation.d.ts +23 -0
- package/dist/components/Navigation.js +120 -0
- package/dist/components/VerboseLogging.d.ts +1 -0
- package/dist/components/VerboseLogging.js +47 -0
- package/dist/components/analysis/AnalysisSelectToolbar.d.ts +1 -0
- package/dist/components/analysis/AnalysisSelectToolbar.js +55 -0
- package/dist/components/analysis/BufferChart.d.ts +1 -0
- package/dist/components/analysis/BufferChart.js +139 -0
- package/dist/components/analysis/CostPerPiece.d.ts +2 -0
- package/dist/components/analysis/CostPerPiece.js +175 -0
- package/dist/components/analysis/CycleChart.d.ts +42 -0
- package/dist/components/analysis/CycleChart.js +281 -0
- package/dist/components/analysis/DataTable.d.ts +83 -0
- package/dist/components/analysis/DataTable.js +215 -0
- package/dist/components/analysis/EfficiencyPage.d.ts +2 -0
- package/dist/components/analysis/EfficiencyPage.js +138 -0
- package/dist/components/analysis/HeatChart.d.ts +22 -0
- package/dist/components/analysis/HeatChart.js +161 -0
- package/dist/components/analysis/InspectionDataTable.d.ts +10 -0
- package/dist/components/analysis/InspectionDataTable.js +148 -0
- package/dist/components/analysis/InspectionSankey.d.ts +12 -0
- package/dist/components/analysis/InspectionSankey.js +140 -0
- package/dist/components/analysis/PalletCycleCards.d.ts +1 -0
- package/dist/components/analysis/PalletCycleCards.js +137 -0
- package/dist/components/analysis/PartCycleCards.d.ts +2 -0
- package/dist/components/analysis/PartCycleCards.js +331 -0
- package/dist/components/analysis/QualityPage.d.ts +1 -0
- package/dist/components/analysis/QualityPage.js +49 -0
- package/dist/components/analysis/ScheduleHistory.d.ts +3 -0
- package/dist/components/analysis/ScheduleHistory.js +108 -0
- package/dist/components/analysis/StationDataTable.d.ts +25 -0
- package/dist/components/analysis/StationDataTable.js +246 -0
- package/dist/components/analysis/ToolReplacements.d.ts +1 -0
- package/dist/components/analysis/ToolReplacements.js +370 -0
- package/dist/components/operations/AllMaterial.d.ts +5 -0
- package/dist/components/operations/AllMaterial.js +267 -0
- package/dist/components/operations/ChartRangeEdit.d.ts +4 -0
- package/dist/components/operations/ChartRangeEdit.js +148 -0
- package/dist/components/operations/CloseoutReport.d.ts +2 -0
- package/dist/components/operations/CloseoutReport.js +172 -0
- package/dist/components/operations/CompletedParts.d.ts +2 -0
- package/dist/components/operations/CompletedParts.js +286 -0
- package/dist/components/operations/CurrentWorkorders.d.ts +3 -0
- package/dist/components/operations/CurrentWorkorders.js +368 -0
- package/dist/components/operations/Dashboard.d.ts +2 -0
- package/dist/components/operations/Dashboard.js +90 -0
- package/dist/components/operations/OEEChart.d.ts +10 -0
- package/dist/components/operations/OEEChart.js +173 -0
- package/dist/components/operations/Outliers.d.ts +4 -0
- package/dist/components/operations/Outliers.js +69 -0
- package/dist/components/operations/ProgramHighlight.d.ts +1 -0
- package/dist/components/operations/ProgramHighlight.js +9 -0
- package/dist/components/operations/Programs.d.ts +5 -0
- package/dist/components/operations/Programs.js +363 -0
- package/dist/components/operations/Rebookings.d.ts +1 -0
- package/dist/components/operations/Rebookings.js +213 -0
- package/dist/components/operations/RecentCycleChart.d.ts +4 -0
- package/dist/components/operations/RecentCycleChart.js +240 -0
- package/dist/components/operations/RecentProduction.d.ts +2 -0
- package/dist/components/operations/RecentProduction.js +213 -0
- package/dist/components/operations/RecentSchedules.d.ts +12 -0
- package/dist/components/operations/RecentSchedules.js +180 -0
- package/dist/components/operations/RecentStationCycles.d.ts +4 -0
- package/dist/components/operations/RecentStationCycles.js +159 -0
- package/dist/components/operations/ShiftSettings.d.ts +6 -0
- package/dist/components/operations/ShiftSettings.js +134 -0
- package/dist/components/operations/SimDayUsage.d.ts +1 -0
- package/dist/components/operations/SimDayUsage.js +133 -0
- package/dist/components/operations/ToolReport.d.ts +3 -0
- package/dist/components/operations/ToolReport.js +233 -0
- package/dist/components/operations/WorkorderGantt.d.ts +1 -0
- package/dist/components/operations/WorkorderGantt.js +124 -0
- package/dist/components/quality/QualityMaterial.d.ts +2 -0
- package/dist/components/quality/QualityMaterial.js +169 -0
- package/dist/components/quality/QualityPaths.d.ts +1 -0
- package/dist/components/quality/QualityPaths.js +53 -0
- package/dist/components/quality/RecentFailedInspections.d.ts +1 -0
- package/dist/components/quality/RecentFailedInspections.js +123 -0
- package/dist/components/routes.d.ts +170 -0
- package/dist/components/routes.js +301 -0
- package/dist/components/station-monitor/BulkRawMaterial.d.ts +11 -0
- package/dist/components/station-monitor/BulkRawMaterial.js +251 -0
- package/dist/components/station-monitor/Closeout.d.ts +5 -0
- package/dist/components/station-monitor/Closeout.js +162 -0
- package/dist/components/station-monitor/CustomStationMonitorDialog.d.ts +1 -0
- package/dist/components/station-monitor/CustomStationMonitorDialog.js +55 -0
- package/dist/components/station-monitor/Inspection.d.ts +8 -0
- package/dist/components/station-monitor/Inspection.js +164 -0
- package/dist/components/station-monitor/InvalidateCycle.d.ts +33 -0
- package/dist/components/station-monitor/InvalidateCycle.js +262 -0
- package/dist/components/station-monitor/JobDetails.d.ts +7 -0
- package/dist/components/station-monitor/JobDetails.js +108 -0
- package/dist/components/station-monitor/LoadStation.d.ts +10 -0
- package/dist/components/station-monitor/LoadStation.js +450 -0
- package/dist/components/station-monitor/Material.d.ts +77 -0
- package/dist/components/station-monitor/Material.js +489 -0
- package/dist/components/station-monitor/MoveMaterialArrows.d.ts +11 -0
- package/dist/components/station-monitor/MoveMaterialArrows.js +118 -0
- package/dist/components/station-monitor/PrintedLabel.d.ts +29 -0
- package/dist/components/station-monitor/PrintedLabel.js +166 -0
- package/dist/components/station-monitor/QuarantineButton.d.ts +4 -0
- package/dist/components/station-monitor/QuarantineButton.js +184 -0
- package/dist/components/station-monitor/Queues.d.ts +23 -0
- package/dist/components/station-monitor/Queues.js +312 -0
- package/dist/components/station-monitor/QueuesAddMaterial.d.ts +30 -0
- package/dist/components/station-monitor/QueuesAddMaterial.js +248 -0
- package/dist/components/station-monitor/SelectInspType.d.ts +2 -0
- package/dist/components/station-monitor/SelectInspType.js +99 -0
- package/dist/components/station-monitor/SelectWorkorder.d.ts +4 -0
- package/dist/components/station-monitor/SelectWorkorder.js +100 -0
- package/dist/components/station-monitor/StationToolbar.d.ts +3 -0
- package/dist/components/station-monitor/StationToolbar.js +168 -0
- package/dist/components/station-monitor/SystemOverview.d.ts +46 -0
- package/dist/components/station-monitor/SystemOverview.js +439 -0
- package/dist/components/station-monitor/Whiteboard.d.ts +10 -0
- package/dist/components/station-monitor/Whiteboard.js +67 -0
- package/dist/data/all-material-bins.d.ts +45 -0
- package/dist/data/all-material-bins.js +224 -0
- package/dist/data/chart-times.d.ts +20 -0
- package/dist/data/chart-times.js +99 -0
- package/dist/data/cost-per-piece.d.ts +32 -0
- package/dist/data/cost-per-piece.js +183 -0
- package/dist/data/current-cycles.d.ts +13 -0
- package/dist/data/current-cycles.js +144 -0
- package/dist/data/inspection-sankey.d.ts +15 -0
- package/dist/data/inspection-sankey.js +147 -0
- package/dist/data/move-arrows.d.ts +48 -0
- package/dist/data/move-arrows.js +217 -0
- package/dist/data/operators.d.ts +2 -0
- package/dist/data/operators.js +44 -0
- package/dist/data/part-summary.d.ts +17 -0
- package/dist/data/part-summary.js +107 -0
- package/dist/data/path-lookup.d.ts +13 -0
- package/dist/data/path-lookup.js +107 -0
- package/dist/data/queue-material.d.ts +46 -0
- package/dist/data/queue-material.js +256 -0
- package/dist/data/results.bufferchart.d.ts +10 -0
- package/dist/data/results.bufferchart.js +90 -0
- package/dist/data/results.completed-parts.d.ts +26 -0
- package/dist/data/results.completed-parts.js +181 -0
- package/dist/data/results.cycles.d.ts +86 -0
- package/dist/data/results.cycles.js +454 -0
- package/dist/data/results.inspection.d.ts +36 -0
- package/dist/data/results.inspection.js +188 -0
- package/dist/data/results.oee.d.ts +40 -0
- package/dist/data/results.oee.js +330 -0
- package/dist/data/results.schedules.d.ts +23 -0
- package/dist/data/results.schedules.js +157 -0
- package/dist/data/tools-programs.d.ts +78 -0
- package/dist/data/tools-programs.js +376 -0
- package/dist/index.d.ts +1 -0
- package/dist/index.js +60 -0
- package/dist/network/api.d.ts +1390 -0
- package/dist/network/api.js +4971 -0
- package/dist/network/backend-mock.d.ts +11 -0
- package/dist/network/backend-mock.js +512 -0
- package/dist/network/backend.d.ts +57 -0
- package/dist/network/backend.js +77 -0
- package/dist/network/load-specific-month.d.ts +13 -0
- package/dist/network/load-specific-month.js +77 -0
- package/dist/network/server-settings.d.ts +12 -0
- package/dist/network/server-settings.js +92 -0
- package/dist/network/websocket.d.ts +4 -0
- package/dist/network/websocket.js +165 -0
- package/dist/renderer.d.ts +8 -0
- package/dist/renderer.js +55 -0
- package/dist/seedtactics-logo.d.ts +2 -0
- package/dist/seedtactics-logo.js +4 -0
- package/dist/util/chart-colors.d.ts +1 -0
- package/dist/util/chart-colors.js +116 -0
- package/dist/util/chart-helpers.d.ts +3 -0
- package/dist/util/chart-helpers.js +51 -0
- package/dist/util/parseISODuration.d.ts +4 -0
- package/dist/util/parseISODuration.js +40 -0
- package/docs/client-efficiency.md +355 -0
- package/docs/client-engineering.md +54 -0
- package/docs/client-launch.md +55 -0
- package/docs/client-operations.md +88 -0
- package/docs/client-quality.md +74 -0
- package/docs/client-sales.md +61 -0
- package/docs/client-scanners.md +41 -0
- package/docs/client-station-monitor.md +149 -0
- package/docs/client-tools-programs.md +74 -0
- package/docs/improve-fms.md +141 -0
- package/docs/makino.md +40 -0
- package/docs/material-quarantine.md +82 -0
- package/docs/material-tracking.md +236 -0
- package/docs/mazak.md +115 -0
- package/docs/niigata.md +228 -0
- package/docs/operator-procedures.md +106 -0
- package/docs/part-instructions.md +63 -0
- package/docs/screenshots/insight-all-material.png +0 -0
- package/docs/screenshots/insight-analysis-pallets.png +0 -0
- package/docs/screenshots/insight-analysis-part-completed.png +0 -0
- package/docs/screenshots/insight-analysis-sankey.png +0 -0
- package/docs/screenshots/insight-analysis-station-oee.png +0 -0
- package/docs/screenshots/insight-buffer-occupancy.png +0 -0
- package/docs/screenshots/insight-choose-analysis-month.png +0 -0
- package/docs/screenshots/insight-closeout.png +0 -0
- package/docs/screenshots/insight-cost-percentages.png +0 -0
- package/docs/screenshots/insight-dashboard.png +0 -0
- package/docs/screenshots/insight-event-custom-view.jpg +0 -0
- package/docs/screenshots/insight-event-viewer.jpg +0 -0
- package/docs/screenshots/insight-inspection.png +0 -0
- package/docs/screenshots/insight-load-station-details.png +0 -0
- package/docs/screenshots/insight-load-station.png +0 -0
- package/docs/screenshots/insight-loadcycle-graph.png +0 -0
- package/docs/screenshots/insight-loadstation-small.jpg +0 -0
- package/docs/screenshots/insight-machinecycle-graph.png +0 -0
- package/docs/screenshots/insight-machinecycle-table.png +0 -0
- package/docs/screenshots/insight-machinecycles.png +0 -0
- package/docs/screenshots/insight-machinehours.png +0 -0
- package/docs/screenshots/insight-machineoutliers.png +0 -0
- package/docs/screenshots/insight-monthly-schedules.png +0 -0
- package/docs/screenshots/insight-operations-material.png +0 -0
- package/docs/screenshots/insight-operations-overview.png +0 -0
- package/docs/screenshots/insight-operations-reports.png +0 -0
- package/docs/screenshots/insight-part-cost.png +0 -0
- package/docs/screenshots/insight-program-report.png +0 -0
- package/docs/screenshots/insight-quality-material-details.png +0 -0
- package/docs/screenshots/insight-quality-material.png +0 -0
- package/docs/screenshots/insight-quality-quarantine.png +0 -0
- package/docs/screenshots/insight-quality-sankey.png +0 -0
- package/docs/screenshots/insight-quality-similar-paths.png +0 -0
- package/docs/screenshots/insight-queue-details.png +0 -0
- package/docs/screenshots/insight-queues-jobs-table.png +0 -0
- package/docs/screenshots/insight-queues.png +0 -0
- package/docs/screenshots/insight-sim-day-usage.png +0 -0
- package/docs/screenshots/insight-station-system-overview-buttons.png +0 -0
- package/docs/screenshots/insight-station-system-overview.png +0 -0
- package/docs/screenshots/insight-system-overview.png +0 -0
- package/docs/screenshots/insight-tool-replacements.png +0 -0
- package/docs/screenshots/insight-tool-report.png +0 -0
- package/docs/screenshots/insight-toolbar-btns.png +0 -0
- package/docs/screenshots/insight-workorder-gantt.png +0 -0
- package/docs/screenshots/insight-workorders.png +0 -0
- package/docs/security.md +131 -0
- package/docs/server-config.md +56 -0
- package/docs/server-errors.md +44 -0
- package/package.json +90 -0
- package/src/index.ts +65 -0
|
@@ -0,0 +1,82 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Material Quarantine
|
|
3
|
+
nav: Procedures > Material Quarantine
|
|
4
|
+
description: >-
|
|
5
|
+
FMS Insight can help track and manage material that has been temporarily
|
|
6
|
+
removed from the FMS cell for re-machining or rework.
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Material Quarantine
|
|
10
|
+
|
|
11
|
+
FMS Insight provides an optional feature to help track and manage material
|
|
12
|
+
that has been temporarily removed from the cell for re-machining, more
|
|
13
|
+
detailed inspection, or some other rework. FMS Insight displays all the
|
|
14
|
+
material currently on hold, allows a supervisor/manager to update the status
|
|
15
|
+
of quarantined material, and finally allows the material to be re-introduced
|
|
16
|
+
to the cell or scrapped.
|
|
17
|
+
|
|
18
|
+
The implementation extends the [material tracking](material-tracking) to
|
|
19
|
+
also include whiteboard regions for quarantined material. By default, FMS
|
|
20
|
+
Insight creates whiteboard regions for each pallet, inspection stand, the
|
|
21
|
+
wash stand, and any in-process queues of material between processes. These
|
|
22
|
+
are the "active" whiteboard regions and contain material which is flowing
|
|
23
|
+
through the normal workflow. FMS Insight keeps these whiteboard regions
|
|
24
|
+
updated automatically by recording the log of automated cell activity.
|
|
25
|
+
In the [server configuration](server-config), FMS Insight allows you to
|
|
26
|
+
define a list of Queues and this list of queues must contain a queue for
|
|
27
|
+
each "active" in-process queue defined in the flexibility plan and used to
|
|
28
|
+
hold material in the normal workflow. Any queue which is listed inside
|
|
29
|
+
the flexibility plan is treated by FMS Insight as an "active" queue.
|
|
30
|
+
|
|
31
|
+
To support quarantined material, you can create extra whiteboard
|
|
32
|
+
regions/queues for the various tasks that might be performed on quarantined
|
|
33
|
+
material. To the list of queues defined in the [server configuration](server-config),
|
|
34
|
+
you can add extra queues to represent the various quarantined material tasks.
|
|
35
|
+
A queue that is not listed inside the flexibility plan is considered as a
|
|
36
|
+
quarantined material queue and FMS Insight will not update the queue
|
|
37
|
+
automatically. Instead a supervisor, manager, or engineer can manually move material
|
|
38
|
+
between the various quarantined material queues to assist with tracking the
|
|
39
|
+
material. The material can also be moved back into an "active" queue to
|
|
40
|
+
reintroduce it into the cell or removed completely if scrapped.
|
|
41
|
+
|
|
42
|
+
The [operations](client-operations#material) and [quality](client-quality#quarantine-material)
|
|
43
|
+
webpages allow supervisors, quality engineers and others to manually move
|
|
44
|
+
material between the various quarantined queues, view all the material, add
|
|
45
|
+
notes, re-introduce material to "active" queues, or scrap material. In
|
|
46
|
+
addition, the [server configuration](server-config) contains a setting
|
|
47
|
+
_QuarantineQueue_ for the initial quarantine queue. If this setting is given,
|
|
48
|
+
the [station monitor webpages](client-station-monitor) will contain a
|
|
49
|
+
button _Quarantine Material_: if pressed the material is moved out of the
|
|
50
|
+
"active" whiteboard regions/queues and into the quarantine queue specified in
|
|
51
|
+
the server configuration file.
|
|
52
|
+
|
|
53
|
+
FMS Insight allows arbitrary quarantined material queues, but we suggest you
|
|
54
|
+
follow a scheme similar to the "TODO, In-Progress, Done" Kanban task
|
|
55
|
+
management/project management technique.
|
|
56
|
+
|
|
57
|
+
- _Initial Quarantine_: We suggest a quarantine queue called _Initial Quarantine_.
|
|
58
|
+
When an operator removes material from a pallet/load station/inspection
|
|
59
|
+
stand/etc. the material is initially moved into this queue to get it out of
|
|
60
|
+
the "active" queues and allows the operator to continue with normal
|
|
61
|
+
operations. A supervisor/manager should then decide what is to be done with
|
|
62
|
+
this material and move it into a more specific quarantined material queue.
|
|
63
|
+
The _Initial Quarantine_ queue acts similarly to the TODO column on the task
|
|
64
|
+
board. Most of the time the _Initial Quarantine_ queue should be empty; if
|
|
65
|
+
there is anything in the _Initial Quarantine_ queue, it signals to the supervisor
|
|
66
|
+
that a decision on the material is required and once that decision is made,
|
|
67
|
+
the material is moved to a more specific quarantine queue, emptying the
|
|
68
|
+
_Initial Quarantine_ queue.
|
|
69
|
+
|
|
70
|
+
- In-Progress quarantine queues: each potential action on the material should have
|
|
71
|
+
a corresponding in-progress quarantined queue. For example,
|
|
72
|
+
_Rework on Standalone Machines_, _Sent to Foundry_,
|
|
73
|
+
_Waiting for Customer Inspection_, etc. FMS Insight allows notes to be attached
|
|
74
|
+
to each piece of material, so you can keep a log or status on each piece of
|
|
75
|
+
material. Material can move between one or more of these queues while it is quarantined.
|
|
76
|
+
|
|
77
|
+
- Done queues: There are no specific done queues (unlike Kanban task management);
|
|
78
|
+
instead, if the material is ready to be re-introduced into the normal workflow
|
|
79
|
+
of the automated handling system, it can be moved back into an "active" queue.
|
|
80
|
+
If instead the material is scrap, it can be removed from the quarantined queues.
|
|
81
|
+
|
|
82
|
+

|
|
@@ -0,0 +1,236 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Material Tracking
|
|
3
|
+
nav: Procedures > Material Tracking
|
|
4
|
+
description: >-
|
|
5
|
+
Tracking each piece of material by marking it with a unique serial and
|
|
6
|
+
barcode is vital by helping operators load/unload material, increase quality,
|
|
7
|
+
fill workorders, and long-term tracking of material.
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Material Tracking
|
|
11
|
+
|
|
12
|
+
Tracking each piece of material by marking it with a unique serial and
|
|
13
|
+
barcode is vital for operating a system with a mix of automated and manual
|
|
14
|
+
handling. The key design objectives and goals are as follows:
|
|
15
|
+
|
|
16
|
+
1. Assist the operators with loading and unloading by providing information about what to produce,
|
|
17
|
+
what material is available, the status of all the in-process material, and load/unload instructions.
|
|
18
|
+
|
|
19
|
+
2. Increase quality by allow the inspection operator to learn the history of the
|
|
20
|
+
exact piece of material under test (the pallet, machine, program, date and time, etc.).
|
|
21
|
+
|
|
22
|
+
3. Track unloaded material through manual processes such as final wash or any in-process work
|
|
23
|
+
between automated machine cycles.
|
|
24
|
+
|
|
25
|
+
4. Properly fill workorders, ensuring that all produced material is assigned to a workorder and that enough
|
|
26
|
+
material is produced to fill workorders on time.
|
|
27
|
+
|
|
28
|
+
5. Make it as easy as possible for the operators to keep the data in the computers matching
|
|
29
|
+
the reality of the material on the shop floor.
|
|
30
|
+
|
|
31
|
+
6. When the data in the computers no longer matches the reality on the shop floor, provide
|
|
32
|
+
an easy way of rectifying this situation by updating the data in the computers.
|
|
33
|
+
|
|
34
|
+
7. Provide long-term tracking and part identification for downstream customers.
|
|
35
|
+
|
|
36
|
+
The key challenge is in points 5 and 6; the system must make the normal,
|
|
37
|
+
everyday operator tasks easy and straightforward but also be robust to the
|
|
38
|
+
unknown.
|
|
39
|
+
|
|
40
|
+
## Sticky Notes
|
|
41
|
+
|
|
42
|
+
Consider the following method of tracking material not using a computer. On a
|
|
43
|
+
whiteboard, divide the whiteboard into regions for all the possible places
|
|
44
|
+
that material could be, so a region for each pallet, a region for each
|
|
45
|
+
in-process transfer stand, a region for material waiting to be inspected, a
|
|
46
|
+
region for material waiting to be washed, a region for in-process queues and
|
|
47
|
+
conveyors, a region for castings, a region for material sent out of the
|
|
48
|
+
factory for external work, and so on. Any place that material could be has a
|
|
49
|
+
corresponding region on the whiteboard.
|
|
50
|
+
|
|
51
|
+
Now for each piece of material, a new sticky note is used. The part name and
|
|
52
|
+
serial is written on the sticky note and on the back is written a log of
|
|
53
|
+
activity. At the start of the process, a new sticky note is created and
|
|
54
|
+
placed on the whiteboard. As the process unfolds, the sticky note moves
|
|
55
|
+
around on the whiteboard corresponding to the material moving around the
|
|
56
|
+
factory floor.
|
|
57
|
+
|
|
58
|
+
For example, a part just completed process 1 and is waiting on pallet 6 at
|
|
59
|
+
the load station to be unloaded into the transfer stand. The sticky note for
|
|
60
|
+
the material is currently on the whiteboard in the region for pallet 6. As
|
|
61
|
+
part of the unload operation, the sticky note is moved on the whiteboard from
|
|
62
|
+
the pallet 6 region to the transfer-stand region. (Also, if any material is
|
|
63
|
+
loaded, its corresponding sticky note is moved into the pallet 6 region.) The
|
|
64
|
+
fact that there is a sticky note existing in the transfer stand position on
|
|
65
|
+
the whiteboard signals to the operators that the pallet for the second
|
|
66
|
+
operation should be brought to the load station. When the pallet for the
|
|
67
|
+
second operation arrives and the material is loaded, the sticky note will
|
|
68
|
+
then move from the whiteboard region for the transfer-stand to the region of
|
|
69
|
+
the whiteboard for the pallet.
|
|
70
|
+
|
|
71
|
+
This whiteboard of sticky notes has several great features:
|
|
72
|
+
|
|
73
|
+
- By centralizing all material on a single whiteboard, it is easy to visualize the
|
|
74
|
+
entire process and make decisions about what actions to take (what material is
|
|
75
|
+
available for loading, what material needs to be inspected, what material to wash and assign to
|
|
76
|
+
a workorder, etc.).
|
|
77
|
+
|
|
78
|
+
- Operators can at a glance determine if the whiteboard matches the reality on the factory floor. If there is
|
|
79
|
+
a mismatch, the sticky notes can be moved so that the whiteboard matches reality.
|
|
80
|
+
|
|
81
|
+
- Operators at a single station can focus only on a section of the whiteboard to carry out their tasks. For example,
|
|
82
|
+
at the wash station, only the section of the whiteboard corresponding to the wash stand is relevant.
|
|
83
|
+
|
|
84
|
+
- It is straightforward to accommodate all sorts of material tasks both inside and outside of
|
|
85
|
+
automation. For example, if a part must be quarantined as potential scrap, its sticky note can be set on
|
|
86
|
+
the side of the whiteboard. Once examined, if the part is determined to be scrap the sticky note can
|
|
87
|
+
be thrown in the trash can. If the part needs some re-machining, the sticky note can be added
|
|
88
|
+
back onto the whiteboard once the re-machining has completed and the part is ready for the remainder of the
|
|
89
|
+
process.
|
|
90
|
+
|
|
91
|
+
- By using a metaphor of physical sticky notes, the design provides an intuitive understanding for users.
|
|
92
|
+
The design is motivated by Google's Material Design, whose founding idea is: "A material metaphor is the unifying
|
|
93
|
+
theory of a rationalized space and a system of motion. The material is grounded in tactile reality,
|
|
94
|
+
inspired by the study of paper and ink, yet technologically advanced and open to imagination and magic."
|
|
95
|
+
In fact, we suggest that operator training start with actual physical sticky notes on a whiteboard before
|
|
96
|
+
transitioning the training to the computers.
|
|
97
|
+
|
|
98
|
+
Of course, there is one main downside to using a physical whiteboard; it is
|
|
99
|
+
tedious for the operators. This is solved by keeping the whiteboard and
|
|
100
|
+
sticky notes in software and using software monitoring to automatically move
|
|
101
|
+
around the sticky notes. We believe that when using automation and software as
|
|
102
|
+
part of process control, you must always start with a design that could be
|
|
103
|
+
done without software. This produces a design which does not force the
|
|
104
|
+
process to conform to the software but allows the software to support the
|
|
105
|
+
process. It also eases user understanding because it provides a
|
|
106
|
+
straightforward metaphor for the user to understand how the software
|
|
107
|
+
functions. The software should exist just to support the process by removing
|
|
108
|
+
the tedious and error-prone tasks.
|
|
109
|
+
|
|
110
|
+
## Software-Based Sticky Notes
|
|
111
|
+
|
|
112
|
+

|
|
113
|
+
|
|
114
|
+
The tactile metaphor of moving around sticky notes, with one sticky note per
|
|
115
|
+
piece of material, is the basis for the FMS Insight Station Monitor page. See
|
|
116
|
+
the screenshot above, which shows the whiteboard with regions for Raw
|
|
117
|
+
Material, the two faces on Pallet 1, and Completed Material. Insight
|
|
118
|
+
allows the operator to view a section of the virtual whiteboard of material
|
|
119
|
+
sticky notes relevant to the current station, in this case the load station 1.
|
|
120
|
+
|
|
121
|
+
Insight monitors the machines and automation and moves around the material
|
|
122
|
+
sticky notes on the virtual whiteboard as parts are loaded, unloaded, and
|
|
123
|
+
machined. Also, by watching the virtual whiteboard, Insight can control the
|
|
124
|
+
pallets. For example, Insight will prevent a pallet from arriving at the load
|
|
125
|
+
station if the transfer stand queue virtual whiteboard region is empty.
|
|
126
|
+
|
|
127
|
+
Insight allows the operator to keep the virtual whiteboard in sync with the
|
|
128
|
+
material on the factory floor. Operators can remove virtual material sticky
|
|
129
|
+
notes from the whiteboard by clicking a button and add sticky notes by
|
|
130
|
+
scanning a barcode or manually entering a serial. Each queue or conveyor or
|
|
131
|
+
place where material is under manual control has a corresponding whiteboard
|
|
132
|
+
region. By placing a computer or tablet at that place in the factory, the
|
|
133
|
+
operator can at a glance see if the virtual whiteboard matches the reality on
|
|
134
|
+
the factory floor, and if not simply edit the virtual whiteboard to match.
|
|
135
|
+
|
|
136
|
+
## An Example Design
|
|
137
|
+
|
|
138
|
+
The virtual whiteboard implemented by FMS Insight is versatile and can adjust
|
|
139
|
+
to a huge variety of processes with parts moving in and out of automation and
|
|
140
|
+
manual handling.
|
|
141
|
+
|
|
142
|
+
For example, consider a process with two cells: a horizontal machining cell
|
|
143
|
+
and a lathe cell. Parts are manually loaded and unloaded and transfer between
|
|
144
|
+
cells via a conveyor. The conveyor between the cells will correspond to a
|
|
145
|
+
region on the virtual whiteboard. Also, right next to the conveyor, there is
|
|
146
|
+
a computer or mounted tablet with an attached barcode scanner. The computer
|
|
147
|
+
uses FMS Insight to display the region of the whiteboard for the conveyor. As
|
|
148
|
+
parts are unloaded from one cell, FMS Insight automatically moves the
|
|
149
|
+
corresponding material sticky note from the pallet to the conveyor region.
|
|
150
|
+
Similarly, FMS Insight is configured to monitor the virtual whiteboard region
|
|
151
|
+
for the conveyor to know when to bring pallets to the load station to load
|
|
152
|
+
material out of the conveyor.
|
|
153
|
+
|
|
154
|
+
During normal operation, the operator does not need to manually edit the
|
|
155
|
+
virtual whiteboard. As parts are completed in one cell, their sticky notes
|
|
156
|
+
are moved to the whiteboard region for the conveyor and when the material is
|
|
157
|
+
loaded into the second cell the sticky notes are removed from the whiteboard
|
|
158
|
+
region for the conveyor. The operator can at a glance see that the conveyor
|
|
159
|
+
matches the virtual whiteboard by comparing the conveyor to the computer screen.
|
|
160
|
+
|
|
161
|
+
Now consider that some parts are removed from the conveyor temporarily.
|
|
162
|
+
Perhaps the parts are inspected, a part needs some re-machining, or it must
|
|
163
|
+
travel elsewhere in the factory for a specialized operation. When the
|
|
164
|
+
material is removed from the conveyor, the operator can click a button in FMS
|
|
165
|
+
Insight to remove the sticky note from the virtual whiteboard. FMS Insight
|
|
166
|
+
will then prevent a pallet from arriving to load this missing material. The
|
|
167
|
+
material eventually returns and when it does, the operator can scan the
|
|
168
|
+
barcode on the part to add the corresponding virtual sticky note onto the
|
|
169
|
+
whiteboard. FMS Insight will then activate the pallet to load this piece of
|
|
170
|
+
material in the second cell.
|
|
171
|
+
|
|
172
|
+
## Whiteboard tracking design
|
|
173
|
+
|
|
174
|
+
FMS Insight requires that you decide on a list of virtual whiteboard regions
|
|
175
|
+
and how material will move between regions. The initial design is best done
|
|
176
|
+
by using an actual whiteboard in a conference room with real sticky notes.
|
|
177
|
+
Draw regions on the whiteboard, create some sample sticky notes, and step through
|
|
178
|
+
the proposed process, moving the sticky notes around on the whiteboard. This helps
|
|
179
|
+
design the whiteboard regions to configure in FMS Insight, but also highlights potential
|
|
180
|
+
complicated material flow which you might consider changing the process.
|
|
181
|
+
|
|
182
|
+
At the load station, use a computer or mounted tablet running Insight.
|
|
183
|
+
Insight will display the section of the virtual whiteboard for the pallet,
|
|
184
|
+
plus the region for material being loaded and the region to which material is
|
|
185
|
+
unloaded. Insight will determine based on the whiteboard which specific
|
|
186
|
+
material to load and display it with its serial. The operator should then
|
|
187
|
+
load the material with the specific serial requested by Insight. But, if the
|
|
188
|
+
serial that Insight wants to load is unavailable, the operator can just edit
|
|
189
|
+
the virtual whiteboard. Insight will automatically adjust with a new
|
|
190
|
+
instruction for the operator. (Hopefully this doesn't happen and the virtual
|
|
191
|
+
whiteboard is kept in sync, but if it does happen it is easy to correct.)
|
|
192
|
+
|
|
193
|
+
At any place where in-process material is queued outside of control of the
|
|
194
|
+
automation, create a whiteboard region. This could be conveyors between cells
|
|
195
|
+
or stands for holding parts between processes (e.g. large parts which have
|
|
196
|
+
process 1 and process 2 on different pallets). At each location, dedicate a
|
|
197
|
+
computer or mounted tablet with an attached barcode scanner to view and edit
|
|
198
|
+
the whiteboard region. Insight can be configured to automatically move the
|
|
199
|
+
virtual sticky notes during normal operations as parts are loaded and
|
|
200
|
+
unloaded into these queues, but the operator can use the computer and scanner
|
|
201
|
+
to adjust the whiteboard region as needed.
|
|
202
|
+
|
|
203
|
+
For in-process manual operations such as manual CMM stations or custom
|
|
204
|
+
processes outside the automated cell, create two whiteboard regions. One
|
|
205
|
+
region for the input to the process and one region for the output from the
|
|
206
|
+
process. For example, at an in-process CMM stand, create a whiteboard region
|
|
207
|
+
for the unloaded parts not yet measured. FMS Insight can then be configured
|
|
208
|
+
to automatically move the material sticky note from the pallet to the inbound
|
|
209
|
+
CMM region. The CMM stand then has a computer or mounted tablet showing
|
|
210
|
+
Insight; the operator can then see the material not yet measured, perform the
|
|
211
|
+
CMM measurement, and if successful, use FMS Insight to transfer the virtual
|
|
212
|
+
sticky note from the inbound region to the outbound region. FMS Insight
|
|
213
|
+
monitors the outbound region and will bring a pallet to the load station once
|
|
214
|
+
the CMM has completed. Insight will also transfer the sticky note from the
|
|
215
|
+
outbound region to the pallet as part of the load operation.
|
|
216
|
+
|
|
217
|
+
For raw material, Insight supports two options. Insight can just assume raw
|
|
218
|
+
material is always available in which case Insight will create a new virtual
|
|
219
|
+
sticky note during the initial loading. In this design, the first time a
|
|
220
|
+
sticky note appears is on the pallet. Alternatively, Insight can be configured
|
|
221
|
+
to draw initial material from a virtual whiteboard region. In this case, when
|
|
222
|
+
material arrives, an operator must scan or add the material into the initial
|
|
223
|
+
whiteboard region. Once added, FMS Insight will then activate the pallet to
|
|
224
|
+
load this material.
|
|
225
|
+
|
|
226
|
+
For completed material, Insight automatically adds the sticky notes to
|
|
227
|
+
regions for signaled inspections and final wash. Technically, these could
|
|
228
|
+
just be configured virtual whiteboard regions similar to in-process queues or
|
|
229
|
+
operations, but inspections and final wash are so common that Insight
|
|
230
|
+
automatically has special regions for them. Each configured inspection type
|
|
231
|
+
has two regions: one for completed parts signaled for inspection but not yet
|
|
232
|
+
inspected and one region for completed inspection. For final wash, Insight
|
|
233
|
+
also has two regions: one for not yet washed parts and one for washed parts.
|
|
234
|
+
A computer mounted at the inspection and wash stations can show Insight and
|
|
235
|
+
allow the operator to move the virtual sticky note as the inspection or final
|
|
236
|
+
wash is completed.
|
package/docs/mazak.md
ADDED
|
@@ -0,0 +1,115 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Mazak Palletech Integration
|
|
3
|
+
nav: FMS Insight Server > Mazak
|
|
4
|
+
description: >-
|
|
5
|
+
FMS Insight works with all Palletech cell controller versions from Mazak:
|
|
6
|
+
Version E, Web Version, and Smooth PMC. FMS Insight can read all events from
|
|
7
|
+
the cell controller and can also edit almost all the data in the cell controller.
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# FMS Insight Mazak Palletech Integration
|
|
11
|
+
|
|
12
|
+
FMS Insight works with all Palletech cell controller versions from Mazak:
|
|
13
|
+
Version E, Web Version, and Smooth PMC. FMS Insight can read all events from
|
|
14
|
+
the cell controller and can also edit almost all the data in the cell controller.
|
|
15
|
+
|
|
16
|
+
## Open Database Kit
|
|
17
|
+
|
|
18
|
+
To facilitate the communication between FMS Insight and the Mazak cell
|
|
19
|
+
controller, you must acquire a program called "Mazak Open Database Kit". This
|
|
20
|
+
is a software program developed by Mazak which allows safe access to the data
|
|
21
|
+
inside the cell controller. Please contact your Mazak representative and ask
|
|
22
|
+
to obtain "Open Database Kit" that matches the specific cell controller
|
|
23
|
+
(Version E, Web, or Smooth PMC).
|
|
24
|
+
|
|
25
|
+
## Enable Log CSV
|
|
26
|
+
|
|
27
|
+
For Mazak Web and Mazak Smooth PMC, you must enable a setting in the Mazak cell controller
|
|
28
|
+
which will cause the Mazak cell controller to create log files of all events (pallet movements,
|
|
29
|
+
machine cycles, etc.) in the `c:\Mazak\FMS\Log` directory. Once enabled, FMS Insight will
|
|
30
|
+
automatically find any log entries from this directory.
|
|
31
|
+
|
|
32
|
+
To enable, go to the `c:\Mazak\FMS` directory. Rename the file `log-parameters.ini.sample` to `log-parameters.ini` and restart the Mazak Palletech software. The `log-parameters.ini` file
|
|
33
|
+
contains settings for the path to use and how often to delete, but FMS Insight works fine with
|
|
34
|
+
the default settings. If you want, you can change the log directory in `log-parameters.ini`
|
|
35
|
+
and then specify the same folder in the FMS Insight server configuration file.
|
|
36
|
+
|
|
37
|
+
## Load Instructions
|
|
38
|
+
|
|
39
|
+
On Version E and MazakWeb, one parameter must be changed. If you are using Mazak Smooth PMC, this step can be
|
|
40
|
+
skipped! Open the Mazak Palletech software, go to the parameter
|
|
41
|
+
edit screen, select `X`, and scroll to the setting `X-31`. Set the `X-31` setting from 0 to 1.
|
|
42
|
+
This setting will cause CSV files describing the current load and unload operation at the load
|
|
43
|
+
station to be output to the `c:\Mazak\FMS\LDS` directory. FMS Insight monitors this directory
|
|
44
|
+
and uses the CSV files to display the parts being loaded and unloaded from each pallet at
|
|
45
|
+
the load station.
|
|
46
|
+
|
|
47
|
+
## Simulation Lab
|
|
48
|
+
|
|
49
|
+
The Mazak Palletech cell controller software has a great ability to be run in a
|
|
50
|
+
simulation mode without any machines or carts attached. In this mode, the
|
|
51
|
+
Mazak cell controller software has all features active but instead of sending
|
|
52
|
+
commands to the actual machines and carts, just simulates their operation.
|
|
53
|
+
|
|
54
|
+
We recommend that you set up what we call a simulation lab, which consists of
|
|
55
|
+
two computers in an office. One computer will run the Mazak cell controller
|
|
56
|
+
software in simulation mode, Open Database Kit, and the FMS Insight server.
|
|
57
|
+
The second computer will run a browser and access the FMS Insight client.
|
|
58
|
+
This mimics the actual layout in operations, where the cell controller
|
|
59
|
+
computer runs Open Database Kit and the FMS Insight server and a separate
|
|
60
|
+
computer on the factory floor or in the office runs the client views.
|
|
61
|
+
|
|
62
|
+
A simulation lab allows testing, training, and experimentation. You can set
|
|
63
|
+
up some dummy orders, create a schedule, copy the schedule into the Mazak
|
|
64
|
+
cell controller, run the schedule inside the Mazak cell controller, see the
|
|
65
|
+
assigned serial numbers, view inspection decisions, and examine efficiency
|
|
66
|
+
reports of cell operations, all without impacting the real system.
|
|
67
|
+
|
|
68
|
+
The simulation lab is also great for training before the machines are even
|
|
69
|
+
installed, testing out new scheduling or inspection signaling techniques, or
|
|
70
|
+
training new operators and managers.
|
|
71
|
+
|
|
72
|
+
## Starting Offset and Decrement Priority
|
|
73
|
+
|
|
74
|
+
The Mazak [config.ini](server-config) contains a setting `Use Starting Offset`
|
|
75
|
+
which control how new schedules are added into the cell controller.
|
|
76
|
+
|
|
77
|
+
When `Use Starting Offset` is enabled, new Mazak schedules will
|
|
78
|
+
be created with a "Due Date" and "Priority" field based on the
|
|
79
|
+
simulation's prediction of its actual start time. If disabled, a due
|
|
80
|
+
date of January 1, 2008 and priority of 91 is used for all Mazak schedules, effectively
|
|
81
|
+
disabling the use of due dates. Since Mazak uses due dates to decide which
|
|
82
|
+
part or pallet to start producing first, due dates can help smooth production
|
|
83
|
+
flow.
|
|
84
|
+
|
|
85
|
+
The main downside to using due dates and priorities is that Mazak will empty out a pallet
|
|
86
|
+
before switching schedules. For example, consider a situation where you have
|
|
87
|
+
a part PPP with two processes and a fixture which can hold one process 1
|
|
88
|
+
material and one process 2 material. Also, consider there are two schedules
|
|
89
|
+
for part PPP; a schedule AAA for today's production and a schedule BBB for
|
|
90
|
+
tomorrow's production. Say that the AAA and BBB schedules have different due
|
|
91
|
+
dates (say AAA has the earlier due date). Then Mazak will first run the
|
|
92
|
+
entire AAA schedule. In particular, the very last cycle of AAA will run with
|
|
93
|
+
a process 2 part and an empty process 1 location. Instead, if the due dates
|
|
94
|
+
of AAA and BBB are the same, Mazak will not empty out the pallet and instead
|
|
95
|
+
on the very last cycle of AAA in the process 2 location will add the very
|
|
96
|
+
first cycle of BBB in the process 1 location.
|
|
97
|
+
|
|
98
|
+
In our opinion, due dates and priorities should be enabled; the pallet
|
|
99
|
+
running empty is not typically that big of a deal. The primary goal of the
|
|
100
|
+
system is to keep the machines busy and a pallet with an empty location will
|
|
101
|
+
return to the load station after cutting just the material on the pallet (as
|
|
102
|
+
long as each process has a separate program). This increases slightly the
|
|
103
|
+
burden on the cart and load station, but these are not the bottleneck and
|
|
104
|
+
there should be enough work in the system to keep the machines busy. In
|
|
105
|
+
addition, occasionally a pallet will empty out in any case because today's
|
|
106
|
+
schedule had a limited quantity to allow a different part some time on the
|
|
107
|
+
machines. Finally, occasionally emptying out a pallet seems to help
|
|
108
|
+
tremendously with preventing traffic jams.
|
|
109
|
+
|
|
110
|
+
Finally, when FMS Insight adds a new day's schedule into the cell controller,
|
|
111
|
+
then FMS Insight will first decrement the priority on all existing
|
|
112
|
+
uncompleted schedules. Since each day a new schedule is downloaded, if
|
|
113
|
+
priorities of existing schedules are first decrement then any unfinished work
|
|
114
|
+
from the previous day gains higher priority and will finish before today's
|
|
115
|
+
schedule starts.
|
package/docs/niigata.md
ADDED
|
@@ -0,0 +1,228 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Niigata ICC Integration
|
|
3
|
+
nav: FMS Insight Server > Niigata
|
|
4
|
+
description: >-
|
|
5
|
+
FMS Insight works with the recent Niigata ICC Cell Controller
|
|
6
|
+
FMS Insight can monitor the events from the cell controller and can also set
|
|
7
|
+
routes and control each pallet.
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# FMS Insight Niigata ICC Cell Controller
|
|
11
|
+
|
|
12
|
+
FMS Insight works with a modified version of the Niigata ICC Cell Controller.
|
|
13
|
+
Contact your Niigata Sales or Support Representative to request more information
|
|
14
|
+
about using FMS Insight with the Niigata ICC Cell Controller.
|
|
15
|
+
|
|
16
|
+
## Configuration
|
|
17
|
+
|
|
18
|
+
#### Reclamp Stations
|
|
19
|
+
|
|
20
|
+
By default, all machine stops in the downloaded jobs are assumed to be machines.
|
|
21
|
+
To support reclamp stops, a specific name of the reclamp stop can be defined
|
|
22
|
+
in the FMS Insight [config.ini](server-config) file. Once defined,
|
|
23
|
+
any machine stop in the downloaded jobs which match this configured name will
|
|
24
|
+
be treated as reclamp stops.
|
|
25
|
+
|
|
26
|
+
#### Custom Machine Names
|
|
27
|
+
|
|
28
|
+
By default, ICC machine numbers are mapped to the identical machine number in
|
|
29
|
+
the downloaded jobs. That is, ICC machine 1 is mapped to MC1 in the jobs,
|
|
30
|
+
ICC machine 2 is mapped to MC2, and so on. The [config.ini](server-config) file can
|
|
31
|
+
specify an alternative job machine name and number to be assigned to each ICC machine
|
|
32
|
+
number. This allows different types of machines to be named differently in the
|
|
33
|
+
flexibility plan and jobs.
|
|
34
|
+
|
|
35
|
+
#### Machine IP Addresses
|
|
36
|
+
|
|
37
|
+
If specified, FMS Insight will use the Machine IP addresses and ports to load
|
|
38
|
+
tooling data from the machines, record it as part of the log of events, and display some
|
|
39
|
+
[summary reports](client-tools-programs) of tooling data. FMS Insight does not
|
|
40
|
+
require the IP addresses to be specified; if they are missing, no tool data is loaded
|
|
41
|
+
but all other functions of FMS Insight work (managing jobs, logging events, etc.).
|
|
42
|
+
|
|
43
|
+
#### Sized Queues
|
|
44
|
+
|
|
45
|
+
FMS Insight supports specifying a size for each queue defined in the config file.
|
|
46
|
+
FMS Insight will then hold and unhold pallets that are waiting to be unloaded so that
|
|
47
|
+
the queue does not exceed the configured size. Note that by using the
|
|
48
|
+
[queues page](client-station-monitor), an operator can manually insert more material
|
|
49
|
+
into the queue beyond the configured size. The configured size is only used for holding
|
|
50
|
+
and unholding pallets.
|
|
51
|
+
|
|
52
|
+
## Operations
|
|
53
|
+
|
|
54
|
+
FMS Insight translates the jobs into the Niigata ICC Cell Controller
|
|
55
|
+
via three mechanisms: adding programs, setting pallet master routes, and controlling
|
|
56
|
+
a few flags on the pallet tracking.
|
|
57
|
+
|
|
58
|
+
#### Programs
|
|
59
|
+
|
|
60
|
+
The jobs can optionally contain the program content for each process and machining stop.
|
|
61
|
+
If the job does not contain the program content, FMS Insight assumes the program has
|
|
62
|
+
already been manually registered with the Niigata ICC.
|
|
63
|
+
|
|
64
|
+
If the program content is included, FMS Insight will manage revisions and register
|
|
65
|
+
the program with the Niigata ICC. FMS Insight will compare the program content from
|
|
66
|
+
the newly created jobs and the already existing program. If they are the same, the
|
|
67
|
+
existing program is reused. If they are different, a new revision is created by
|
|
68
|
+
selecting a new program number and registering the new program content with the
|
|
69
|
+
Niigata ICC. This leaves the old program revision unchanged so both the old and
|
|
70
|
+
new revisions are simultaneously in the cell controller. FMS Insight tracks all
|
|
71
|
+
material and will use either the old revision or the new program revision
|
|
72
|
+
based on which material is currently loaded onto the pallet. Once the old
|
|
73
|
+
job completes, FMS Insight will remove the old program revision from the Niigata
|
|
74
|
+
ICC. Program revisions and Niigata ICC program numbers can be seen on the
|
|
75
|
+
[program report page](client-tools-programs).
|
|
76
|
+
|
|
77
|
+
#### Pallet Master
|
|
78
|
+
|
|
79
|
+
For each pallet, the Niigata ICC stores the "Pallet Master", a list of stops that
|
|
80
|
+
the pallet visits. The route starts with LD (load), has a sequence of MC (machining)
|
|
81
|
+
and RC (reclamp) stops, and ends with a UL (unload). Each load, unload, or reclamp stop
|
|
82
|
+
contains a list of load station numbers to use. Each machining stop contains the
|
|
83
|
+
machines to use plus a list of program to run.
|
|
84
|
+
|
|
85
|
+
FMS Insight sets the pallet master steps based on the data in the created jobs. For
|
|
86
|
+
each available pallet, FMS Insight sorts the jobs by date and priority and decides
|
|
87
|
+
which job should run on the pallet. FMS Insight then uses the job data to completely
|
|
88
|
+
replace the pallet master with the sequence of steps from the job. FMS Insight
|
|
89
|
+
uses the comment field to keep track of which job is currently assigned to the
|
|
90
|
+
pallet. FMS Insight continuously updates the pallet master data as jobs
|
|
91
|
+
complete and other jobs are assigned to the pallet; FMS Insight will only update
|
|
92
|
+
a pallet if it is waiting in the stocker with the "No Work" flag set (see below for
|
|
93
|
+
more information about the No Work flag).
|
|
94
|
+
|
|
95
|
+
#### Pallet Location and Status
|
|
96
|
+
|
|
97
|
+
For each pallet, the Niigata ICC stores the "Tracking Data", consisting of the current
|
|
98
|
+
pallet location, currently executing step, count of remaining pallet cycles, and a
|
|
99
|
+
couple of boolean flags.
|
|
100
|
+
|
|
101
|
+
FMS Insight reads but does NOT have write access to the current pallet location and
|
|
102
|
+
currently executing step (Before-LD, After-LD, Before-MC, etc.). The Niigata ICC
|
|
103
|
+
keeps these fields updated as the pallet moves through the route defined in the
|
|
104
|
+
pallet master. FMS Insight watches these values change and uses them to create
|
|
105
|
+
a log of what happens. The Niigata ICC does allow the user (but not FMS Insight)
|
|
106
|
+
to override the pallet location or current step, which can be used in emergencies;
|
|
107
|
+
overriding the pallet location and current step is not required during normal
|
|
108
|
+
operation. FMS Insight uses the transitions of pallet locations and currently
|
|
109
|
+
executing step to create log entries, so if they are manually edited by
|
|
110
|
+
the user, FMS Insight may miss log entries for the current cycle. FMS Insight
|
|
111
|
+
will recover once a new pallet cycle starts.
|
|
112
|
+
|
|
113
|
+
#### Pallet Cycle Count
|
|
114
|
+
|
|
115
|
+
For each pallet, the Niigata ICC tracks a count of remaining pallet cycles. The Niigata
|
|
116
|
+
ICC decrements this on the completion of the UL (unload) step. If it is greater
|
|
117
|
+
than zero and the operator presses the LOAD button, the Niigata ICC switches to the
|
|
118
|
+
After-LD (load) step and thus starts the route again. If the count is zero OR the
|
|
119
|
+
operator presses the button Niigata calls UNLOAD but might more accurately be translated
|
|
120
|
+
"NOT LOADED", the Niigata ICC places the "No Work" flag onto the pallet, which
|
|
121
|
+
causes the pallet to route to the stocker. (See below for more about the No Work flag.)
|
|
122
|
+
|
|
123
|
+
FMS Insight always keeps the cycle count at 1 and increments it when the pallet arrives
|
|
124
|
+
to be unloaded if needed. That is, consider when a pallet arrives to be unloaded. The
|
|
125
|
+
current remaining cycle count is 1. FMS Insight will check the available material in the
|
|
126
|
+
[queues](material-tracking) to determine if there is a piece of material to be loaded.
|
|
127
|
+
If no material is available, FMS Insight will do nothing; the Niigata ICC will then
|
|
128
|
+
decrement the cycle count from 1 to 0 and send the pallet to the stocker no matter if the
|
|
129
|
+
operator presses the LOAD or UNLOAD/NOT LOADED button. Instead, if there is available
|
|
130
|
+
material to be loaded, FMS Insight will increment the remaining pallet cycles to 2. When
|
|
131
|
+
the operator presses the LOAD button, the Niigata ICC will then set the status to After-LD
|
|
132
|
+
(load) and proceed to route the pallet back through the pallet master steps. If instead
|
|
133
|
+
the operator presses the UNLOAD/NOT LOADED button, the Niigata ICC will set the No Work
|
|
134
|
+
flag and route the pallet to the stocker.
|
|
135
|
+
|
|
136
|
+
The FMS Insight [load station page](client-station-monitor) will always contain the
|
|
137
|
+
expected operations to occur at the load station.
|
|
138
|
+
|
|
139
|
+
#### No Work and Skip
|
|
140
|
+
|
|
141
|
+
For each pallet, the Niigata ICC stores two boolean flags: "No Work" and "Skip".
|
|
142
|
+
|
|
143
|
+
The "Skip" flag, also called hold, causes the Niigata ICC to move the pallet to
|
|
144
|
+
the stocker and then ignore it. FMS Insight uses the "Skip" flag to implement
|
|
145
|
+
sized queues. If there is an in-process queue with a specific size, FMS Insight
|
|
146
|
+
will set the "Skip" flag on all pallets destined to be unloaded into this queue.
|
|
147
|
+
FMS Insight then removes the "Skip" flag on only a single pallet at a time and only
|
|
148
|
+
when the unload would not increase the number of parts beyond the size of the queue.
|
|
149
|
+
|
|
150
|
+
The "No Work" flag is used to override the "Remaining Pallet Cycles" count. If the
|
|
151
|
+
No Work flag is set, the Niigata ICC assumes that the pallet is empty, sends the
|
|
152
|
+
pallet to the stocker, and ignores it. While similar to Skip, Skip is used to
|
|
153
|
+
hold a pallet in the middle of the route while No Work is used to not start the
|
|
154
|
+
pallet route at all. When the remaining pallet cycle count drops to zero, the
|
|
155
|
+
Niigata ICC sets the No Work flag when the pallet is unloaded. Also, if the
|
|
156
|
+
operator presses the UNLOAD/NOT LOADED button, the No Work flag is set
|
|
157
|
+
no matter what the remaining pallet cycle count is.
|
|
158
|
+
|
|
159
|
+
FMS Insight uses the No Work flag on a pallet in the stocker to trigger its
|
|
160
|
+
check for new jobs to assign to the pallet. For each pallet in the stocker
|
|
161
|
+
with No Work set, FMS Insight will sort the available jobs by date and
|
|
162
|
+
priority. For each job, FMS Insight checks if there is available material
|
|
163
|
+
to be loaded. If a piece of material for some job is found, FMS Insight
|
|
164
|
+
will clear the No Work flag (and also optionally update the pallet master
|
|
165
|
+
data for the new job, if required).
|
|
166
|
+
|
|
167
|
+
## Operator Procedures
|
|
168
|
+
|
|
169
|
+
#### Load Station Normal Operation
|
|
170
|
+
|
|
171
|
+
FMS Insight's [load station page](client-station-monitor) will display what the Niigata ICC is
|
|
172
|
+
expecting to happen at the load station. Specifically, the page will display the material
|
|
173
|
+
to load, the material to unload, and the material to transfer between faces (if the pallet has
|
|
174
|
+
multiple faces). If the operator performs all the tasks as specified, the operator presses
|
|
175
|
+
the "LOAD" button. The Niigata ICC will then begin the route on the pallet for the material
|
|
176
|
+
that was just loaded. (Note that if the instructions specify that nothing is to be loaded,
|
|
177
|
+
the operator can press either "LOAD" or "UNLOAD/NOT LOADED", both will preform the same
|
|
178
|
+
action.)
|
|
179
|
+
|
|
180
|
+
#### Material which is unloaded must be reworked or scrapped
|
|
181
|
+
|
|
182
|
+
Consider when the operator unloads a piece of material which cannot continue with the normal
|
|
183
|
+
flow but must be set aside to be reworked or possibly scrapped. If this is on the final process,
|
|
184
|
+
nothing needs to be specified. If instead this is an in-process piece of material, it
|
|
185
|
+
can be signaled to be quarantined after the unload completes. To do so, on the
|
|
186
|
+
load station page, click the material card for the piece of material. The dialog that
|
|
187
|
+
opens will contain a "Signal For Quarantine" action. Once clicked, FMS Insight will move
|
|
188
|
+
the material to the quarantine queue once the unload finishes.
|
|
189
|
+
|
|
190
|
+
If the material has already been unloaded without clicking the "Signal for Quarantine" action,
|
|
191
|
+
FMS Insight will add the material that was unloaded
|
|
192
|
+
into the in-process queue, visible on either the
|
|
193
|
+
[load station or queues pages](client-station-monitor).
|
|
194
|
+
To remove the material, the operator must click on the material card and then
|
|
195
|
+
click either the "Remove From System" or "Quarantine Material" action
|
|
196
|
+
(depending on if [quarantine queues](material-quarantine) are configured).
|
|
197
|
+
This will either remove the material from the system completely or remove it
|
|
198
|
+
from the active FMS Insight queue and place it in a special quarantine queue.
|
|
199
|
+
In either case, once the material is no longer in the queue, FMS Insight will
|
|
200
|
+
not set pallet master or tracking data into the Niigata ICC for this material.
|
|
201
|
+
|
|
202
|
+
Note that depending on timing and pallet availability, it may be the case that a
|
|
203
|
+
pallet has already been activated by the time the operator removes the material.
|
|
204
|
+
The operator must still remove the material from the queue as specified above,
|
|
205
|
+
and then reject the load as specified in the next section.
|
|
206
|
+
|
|
207
|
+
#### Load Station Material Can't Be Loaded
|
|
208
|
+
|
|
209
|
+
Consider that a pallet arrives at the load station, the Niigata ICC is expecting something to be
|
|
210
|
+
loaded, but the material is not available to be loaded. This could be because the material was removed
|
|
211
|
+
from the queue as described in the previous section but because of the timing a pallet had already been
|
|
212
|
+
activated. It could also be because the operator forgot to remove the material from the queue, or didn't
|
|
213
|
+
notice that the material was bad until the load operation started.
|
|
214
|
+
|
|
215
|
+
In any case, the operator should first confirm that the material is removed from the FMS Insight queue
|
|
216
|
+
and then press the UNLOAD/NOT LOADED button. This will cause the Niigata ICC to route the empty pallet
|
|
217
|
+
back to the stocker and as long as there is no material in the FMS Insight queues, FMS Insight will not
|
|
218
|
+
reactivate the pallet until more material enters the queue.
|
|
219
|
+
|
|
220
|
+
#### Reworked material is ready to re-enter the flow
|
|
221
|
+
|
|
222
|
+
Consider when material was removed from the system or placed into [quarantine queues](material-quarantine)
|
|
223
|
+
as described above, and now the material has been successfully fixed and is ready to complete the remainder of
|
|
224
|
+
the process. Once the material arrives back at the load station and is ready to go, the operator adds the material
|
|
225
|
+
back into the in-process queue. To do so, the operator clicks a button on the queues page, enters
|
|
226
|
+
or scans the serial number of the material to be added, and then verifies the job and process number. The
|
|
227
|
+
material will then be placed into the queue and FMS Insight will then activate the appropriate pallets
|
|
228
|
+
in the Niigata ICC.
|